IP Library › Granted Patent US 7,089,316

Granted Patent B2

US 7,089,316 · App. 10/160,909 · Granted Aug 8, 2006

System and method for service development over content-specific sessions

Assignee: International Business Machines Corporation

View Patent ↗

Loading inventors, assignments & file history…

Monitor This Case

Get email alerts when status or documents change.

Order Certified Copies

Most orders are placed with the USPTO same day — all within 24 business hours.

Order via The Patent Place →

Pre-filled with this patent's details

Quick Facts

Patent No.: US 7,089,316
App. No.: 10/160,909
Granted: Aug 8, 2006
Kind: B2

External Links

USPTO Patent Center↗ Full Patent PDF↗

Abstract

A system and method for deploying a resource over a content-specific session is provided. A client requests a resource from a service provider, such as an ISP. The service provider provisions the order and records the order in a data store. A service login identifier is created with attributes, such as bandwidth, that correspond to the requested resource, such as a movie or network accessible storage. The client logs into the service provider using the service login identifier and the client's normal password. The service login is authenticated and a session is established using the attributes that correspond to the requested resource. The client is directed to the requested resource by using a resource URL that was provided by the service provider, such as a URL to a requested movie or network accessible storage.

Claims (181)

1. A computer-implemented method for providing a resource to a client connecting to a service provider, said method comprising:

receiving a resource request from the client over a first session;

creating a service login identifier in response to the resource request;

in response to the creating, storing one or more session attributes corresponding to the service login identifier, wherein the session attributes include a resource URL corresponding to the location of the requested resource;

returning the service login identifier to the client over the first session;

receiving a session request from the client, wherein the session request includes the service login identifier and a password;

establishing a second session between the service provider and the client in response to the session request;

providing the resource URL to the client over the second session;

receiving a connection request from the client, the connection request including the service login identifier and the resource URL;

establishing a connection with the client based upon the resource URL; and

using the connection to provide the requested resource to the client.

2. The method as described in claim 1 further comprising:

in response to receiving the connection request, retrieving the stored session attributes; and

wherein the connection is a content-specific connection that has properties based upon at least one of the retrieved session attributes that are selected from the group consisting of a bandwidth amount, a session duration, and a packet size.

3. The method as described in claim 1 further comprising:

receiving an order from the client, the order corresponding to the requested resource;

identifying a price for the requested resource;

billing the price of the resource to an account corresponding to the client;

creating an order identifier for the order; and

storing the order identifier and order details corresponding to the order in a data store.

4. The method as described in claim 1 further comprising:

identifying an order identifier corresponding to the client's resource request, wherein the service login identifier includes a component derived from the order identifier.

5. The method as described in claim 1 further comprising:

identifying a resource identifier corresponding to the requested resource, wherein the service login identifier includes a component derived from the resource identifier.

6. The method as described in claim 1 further comprising:

determining that the requested resource is a client-specific resource;

retrieving client-specific resource request data included in the resource request;

provisioning the client-specific resource based upon the client-specific resource request data; and

assigning a resource identifier to the provisioned client-specific resource, wherein the resource URL is derived from the resource identifier.

7. The method as described in claim 1 further comprising:

identifying a normal login identifier corresponding to the client, the identifying including:

locating an order corresponding to the service login identifier;

retrieving the normal login identifier from the located order;

retrieving a stored password that corresponds to the normal login identifier; and

authenticating the password by comparing the password to the stored password.

8. An information handling system comprising:

one or more processors;

a memory accessible by the processors;

a network interface connecting the information handling system to a client through a computer network; and

a resource deployment tool for providing a resource to the client over a content-specific network session, the resource deployment tool including:

receiving logic for receiving a resource request from the client over a first session;

identifier generation logic for creating a service login identifier in response to the resource request;

storage logic for storing one or more session attributes corresponding to the service login identifier in response to creating the service login identifier, wherein the session attributes include a resource URL corresponding to the location of the requested resource;

transmission logic for returning the service login identifier to the client over the first session;

request handling logic for receiving a session request from the client, wherein the session request includes the service login identifier and a password;

session logic for establishing a second session between the service provider and the client in response to the session request;

the transmission logic for providing the resource URL to the client over the second session;

the session logic for receiving a connection request from the client, the connection request including the service login identifier and the resource URL;

connection logic for establishing a connection with the client based upon the resource URL; and

deployment logic for providing the requested resource to the client over the connection.

9. The information handling system as described in claim 8 further comprising:

in response to receiving the connection request, retrieval logic for retrieving the stored session attributes; and

10. The information handling system as described in claim 8 further comprising:

order receiving logic for receiving an order from the client, the order corresponding to the requested resource;

price identification logic for identifying a price for the requested resource;

invoice logic for billing the price of the resource to an account corresponding to the client;

order generation logic for creating an order identifier for the order; and

storage logic for storing the order identifier and order details corresponding to the order in a data store.

11. The information handling system as described in claim 8 further comprising:

order identification logic for identifying an order identifier corresponding to the client's resource request, wherein the service login identifier includes a component derived from the order identifier.

12. The information handling system as described in claim 8 further comprising:

resource identification logic for identifying a resource identifier corresponding to the requested resource, wherein the service login identifier includes a component derived from the resource identifier.

13. The information handling system as described in claim 8 further comprising:

determination logic for determining that the requested resource is a client-specific resource;

retrieval logic for retrieving client-specific resource request data included in the resource request;

provisioning logic for provisioning the client-specific resource based upon the client-specific resource request data; and

assignment logic for assigning a resource identifier to the provisioned client-specific resource, wherein the resource URL is derived from the resource identifier.

14. The information handling system as described in claim 8 further comprising:

identification logic for identifying a normal login identifier corresponding to the client, the identification logic including:

search logic for locating an order corresponding to the service login identifier;

retrieval logic for retrieving the normal login identifier from the located order;

retrieval logic for retrieving a stored password that corresponds to the normal login identifier; and

authentication logic for authenticating the password by comparing the password to the stored password.

15. A computer program product stored in a computer operable media, the computer operable media containing instructions for execution by a computer, which, when executed by the computer, cause the computer to implement a method for providing a resource to a client connecting to a service provider, the method comprising: