Delivery of network services

• US 20040127200A1
• Filed: 04/07/2003
• Published: 07/01/2004
• Est. Priority Date: 12/31/2002
• Status: Abandoned Application

• Current Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Original Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Inventors: Daly, Brian K., Sennett, DeWayne A., Shaw, Venson M., Carlson, Steven I., Leuca, Ileana A., Molchan, Andrew J.
• Application Number:
  US10/410,662
• Publication Number:
  US 20040127200A1
• Time in Patent Office: Days
• US Class Current: 455/414.1
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor
• CPC Class Codes: H04W 72/04 Wireless resource allocation
• CPC Class Codes: H04W 8/20 Transfer of user or subscriber data

Abstract

A service request is received and the source of the service request is identified as one of a subscriber, user, and terminal. Profile information for the source of the service request is accessed.

Claims

1. A method comprising:

a network storing information about actions to take in response to a service request;

upon receiving a service request, identifying actions common to responding to the service request and to at least one of actions presently underway and actions scheduled to be underway in the network (common acts);

identifying network resources common to resources needed to respond to the service request and to resources needed for at least one of actions presently underway and actions scheduled to be underway in the network (common resources); and

allocating network resources and scheduling network acts in accordance with the common acts and common resources.

2. The method of claim 1 further comprising:

identifying and establishing prerequisites to the actions to respond to the service request; and

identifying and establishing post-requisites to the actions to respond to the service request.

3. The method of claim 2 further comprising:

the network storing in a service profile information about the prerequisites, the post-requisites, and the actions to take in response to the service request.

4. The method of claim 1 further comprising:

the network storing in a service profile information about the actions to take in response to the service request and information about the network resources needed to respond to the service request.

5. The method of claim 1 further comprising:

the network storing information about the quality of service to provide in response to the service request; and

allocating network resources to provide the quality of service.

6. A method comprising:

receiving a request for a network service;

accessing a service profile for the network service;

identifying from the service profile acts common to responding to the service request and at least one of acts underway and acts scheduled to be underway in the network (common acts); and

employing the common acts in a response to the service request.

7. The method of claim 6 further comprising:

identifying from the service profile resources common to resources needed to respond to the service request and at least one of resources allocated for acts underway and acts scheduled to be underway in the network (common resources); and

employing the common resources in the response to the service request.

8. The method of claim 6 further comprising:

identifying from the service profile pre-requisites to the acts to carry out in response to the service request; and

establishing the pre-requisites prior to carrying out the acts to carry out in response to the service request.

9. The method of claim 8 further comprising:

identifying from the service profile post-requisites to the acts to carry out in response to the service request; and

establishing the post-requisites subsequent to carrying out the acts to carry out in response to the service request.

10. A network comprising:

a storage element comprising a service profile, the service profile comprising information about actions to take in response to a request for a service; and

a network element comprising logic to access the service profile and to identify acts common to responding to the service request and at least one of acts underway and acts scheduled to be underway in the network.

11. The network of claim 10, the service profile further comprising information about pre-requisites and post-requisites to the actions to take in response to the request for service;

and

the network element further comprising logic to access the service profile and to establish the pre-requisites prior to a response to the service request, and to establish the post-requisites subsequent to the response to the service request.

12. The network of claim 10, the service profile further comprising information about resources needed to respond to the service request;

and

the network element further comprising logic to access the service profile and to identify resources common to the resources needed to respond to the service request and at least one of resources allocated for acts underway and acts scheduled to be underway in the network.

13. A network element comprising:

logic to access a storage element comprising a service profile, the service profile comprising information about actions to take in response to a request for a service; and

logic to access the service profile and to identify acts common to responding to the service request and at least one of acts underway and acts scheduled to be underway in the network.

14. The network element of claim 13 further comprising:

logic to access the storage element comprising a service profile to obtain information about resources needed to respond to the service request; and

logic to identify resources common to the resources needed to respond to the service request and at least one of resources allocated for acts underway and acts scheduled to be underway in the network.

15. The network element of claim 13 further comprising:

logic to access the storage element comprising a service profile to obtain information about pre-requisites and post-requisites to the actions to take in response to the request for service; and

logic to establish the pre-requisites prior to a response to the service request, and to establish the post-requisites subsequent to the response to the service request.