Application of dynamic profiles to the allocation and configuration of network resources

• US 20040158618A1
• Filed: 06/16/2003
• Published: 08/12/2004
• Est. Priority Date: 02/10/2003
• Status: Active Grant

• Current Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Original Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Inventors: Shaw, Venson M.
• Granted Patent: US 7,802,292 B2
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor
• CPC Class Codes: H04W 72/53 based on regulatory allocation policies
• CPC Class Codes: H04W 8/18 Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Abstract

A service request is received and associated with a subscriber id. Profile information is accessed for the source of the service request. A copy of the profile information is stored in a network element employed by the source of the service request to access the network.

Claims

1. A method comprising:

accessing profile information of a subscriber to identify services to which the subscriber has access;

verifying that the subscriber is authorized to access a requested service;

comparing requirements for delivering the service with available network resources; and

when sufficient network resources are available to deliver the service, allocating network resources in accordance with the requirements for delivering the service.

2. The method of claim 1 further comprising:

when sufficient network resources are not available to deliver the service, determining a less resource demanding manner of delivering the service.

3. The method of claim 1 further comprising:

configuring a terminal device to receive the service, in accordance with the service requirements.

4. The method of claim 1 further comprising:

identifying a service provider to provide the requested service; and

identifying network elements having sufficient resources available to provide the service.

5. A network comprising:

an HLR comprising profile information for subscribers of the network; and

an MSC comprising logic to access the profile information upon receiving a service request, and to identify a subscriber that is the source of the service request, and to access the profile information to verify that the subscriber is authorized to receive a requested service, and to access from the HLR a service profile for the requested service and to allocate network resources according to the service profile to deliver the service to a terminal of the subscriber.

6. The network of claim 5 wherein the HLR further comprises:

a network profile comprising information about at least one of currently available network resources, expected demand for network resources, and currently allocated network resources.

7. The network of claim 5 wherein the MSC further comprises:

copies of profile information for subscribers accessing the network via the MSC.

8. The network of claim 5 wherein the MSC further comprises:

logic to update the copies of the profile information according to usage of the network by the subscribers and to cause the updates to the profile information to be stored in the HLR.

9. A method comprising:

detecting an error condition on a terminal device;

accessing terminal information for the terminal device; and

applying the terminal information to remove the error condition.

10. The method of claim 9 further comprising:

the terminal information stored by an HLR.

11. The method of claim 9 further comprising:

accessing a copy of the terminal information, the copy stored by an MSC, a master copy of the terminal information stored by an HLR.

12. The method of claim 9 further comprising:

accessing a copy of the terminal information, the copy stored by a BSC, a master copy of the terminal information stored by an HLR.

13. A method comprising:

receiving a service request;

associating a subscriber id with the service request;

accessing profile information for the source of the service request; and

allocating network resources according to profile information for the source of the service request and profile information of the service requested.

14. A network element comprising:

a router to route communications in a communication network; and

logic access a service profile in response to a service request and to allocate network resources to fulfill the service request according to service requirements of the service profile.

15. The network element of claim 14 further comprising:

logic to negotiate a less resource demanding manner of delivering the service when sufficient network resources are unavailable to deliver the service.

16. The network element of claim 14 further comprising:

logic to configure a terminal device to receive the service, in accordance with the service requirements.