Application services infrastructure for next generation networks

• US 7,505,482 B2
• Filed: 11/15/2004
• Issued: 03/17/2009
• Est. Priority Date: 11/15/2004
• Status: Active Grant

• Current Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Patterson, Gregory, Nguyen, Hong, Adamczyk, Maria, Huslak, Nicholas Steven, Modarressi, Abdi, Johnson, Myranda, Denny, Michael
• Primary Examiner(s): Backer; Firmin
• Assistant Examiner(s): NG, CHRISTINE Y
• Application Number:
  US10/989,036
• Publication Number:
  US 20060104306A1
• Time in Patent Office: 1,583 Days
• Field of Search: 370/252, 370/401, 370/465, 370/466, 370/469
• US Class Current: 370/469
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/321 Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
• CPC Class Codes: H04L 69/327 in the session layer [OSI layer 5]

Abstract

Support of a plurality of different applications utilizing a next generation network having a network layer is provided by an application services middle layer between the applications and the network layer that includes a plurality of common infrastructure elements usable by the different applications. The common infrastructure elements provide services associated with use of the network and services that are not associated with use of the network. The common infrastructure elements may provide a common infrastructure element to an end user such that use of the service by the end user is accessible to each of the different applications utilizing the at least one common infrastructure element. A common infrastructure element may be accessible by an end user so as to provide a common infrastructure element to the end user for the different applications. The different applications may include both third party applications and network service provider applications.

Claims

1. A method of providing services for an application middle layer between a plurality of different applications and a network layer of a next generation network, comprising:

determining common services used by the plurality of different applications irrespective of whether the common services are associated with use of the next generation network;

abstracting the common services to provide a common interface to the services to the plurality of different applications; and

incorporating the abstracted common services into the application middleware as common infrastructure elements;

wherein the steps of determining common services, abstracting the common services and incorporating the abstracted common services comprises;

scoping the middleware layer;

modeling the middleware services;

modeling domains for the middleware services; and

generating services provided by the middleware layer based on results of scoping the middleware layer, modeling the middleware services and modeling domains for the middleware services;

wherein scoping the middleware layer comprises;

identifying functionality and services provided to the applications;

identifying a set of services supported by the middleware layer; and

identifying a set of domains resident in the middleware layer;

wherein modeling the middleware services layer comprises;

modeling each of the identified services supported by the middleware layer;

developing a domain chart;

developing an activity diagram; and

wherein modeling domains comprises;

identifying domains needed for each identified service provided to the applications;

determining a union of the identified domains to identify a list of domains need for the middleware layer;

developing a mission statement for each domain; and

developing a class specification for each domain in the union.