Common mobility management protocol for multimedia applications, systems and services

• US 7,551,608 B1
• Filed: 06/29/2005
• Issued: 06/23/2009
• Est. Priority Date: 04/25/2001
• Status: Expired due to Term

• Current Assignee: AT&T Intellectual Property II LP (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property II LP (AT&T, Inc.)
• Inventors: Roy, Radhika R.
• Primary Examiner(s): D AGOSTA, STEPHEN M
• Application Number:
  US11/169,538
• Time in Patent Office: 1,455 Days
• Field of Search: 370/328, 370/352, 455/418, 455/419, 455/433, 455/432.3, 709/201, 709/230
• US Class Current: 370/352
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1106 Call signalling protocols; H.323 and related
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04M 3/42348 Location-based services which utilize the location information of a target
• CPC Class Codes: H04M 7/0078 Security; Fraud detection; Fraud prevention
• CPC Class Codes: H04M 7/128 Details of addressing, directories or routing tables
• CPC Class Codes: H04W 40/36 due to handover
• CPC Class Codes: H04W 8/02 Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
• CPC Class Codes: H04W 8/12 between location registers or mobility servers

Abstract

A framework of a common mobility management protocol for Q.5/16 (Mobility for Multimedia Systems/Applications and Services) comprises a high level protocol for performing the functions of address resolution, routing, location update and authentication. The common mobility management protocol can be used by all existent and future multimedia applications (MA'"'"'s) to support mobility management for messaging among mobility management authentication function (AuF), home location function (HLF) and visitor location function (VLF) databases/servers, and the corresponding multimedia application functional entities (MAFEs) of the multimedia applications (MA'"'"'s). The common mobility management protocol may replace, act in concert with or in sequence with existent interworking protocols for the various multimedia applications. Reference point architectures, functional characteristics, features, and capabilities of the protocol are described including call flows and message syntax. In addition, the scope of Q.5/16 and how H.MMS.1 (H.323 Mobility), H.MMS.2 (Global Mobility), and H.MMS.3 (Presence/Instant Messaging Mobility) can be a part of the same common mobility management protocol have also been presented.

Claims

1. A computer processing device or data server that facilitates communication between a first multimedia application and a second multimedia application, the computer processing device or data server comprising:

a common mobility management protocol shared by the first and second multimedia applications, the common mobility management protocol further comprising;

an address template for defining a set of address identifiers and profile information for completing a communication between the first multimedia application to the second multimedia application; and

a descriptor for carrying address information, the descriptor comprising a unique identifier for the descriptor that includes a time the descriptor last changed, at least one address template having a template life field and a functional entity identifier indicating an associated functional entity of the descriptor, and wherein the common mobility management protocol further comprises a visitor location function and a home location function.

2. The module of claim 1, wherein the common mobility management protocol enables communication between a first mobility management functional entity associated with the first multimedia application and a second mobility management functional entity associated with the second multimedia application.

3. The module of claim 1, wherein the communication is a message.

4. The module of claim 1, wherein the common mobility management protocol further comprises a home location function.

5. The module of claim 1, wherein the common mobility management protocol further comprises an authentication function.

6. The module of claim 5, wherein the common mobility management protocol further comprises at least one of a home location function and a visitor location function.

7. The module of claim 1, wherein the common mobility management protocol further comprises a descriptor update message to update an address template before a life of the address template expires.

8. The module of claim 1, wherein the common mobility management protocol further comprises:

a descriptor request message; and

a descriptor confirmation message that identifies all address templates conforming to a specified descriptor and that is sent in response to receiving the descriptor request message.

9. The module of claim 1, wherein the communication from the first multimedia application to the second multimedia application further comprises a communication to an identified address.

10. The module of claim 1, wherein the module supports a plurality of different multimedia communications protocols and applications associated with at least one of the first or second multimedia application, each first and second multimedia application having at least one multimedia application functional entity.

11. The module of claim 10, wherein the common mobility management protocol further enables messaging between a given multimedia application functional entity and a mobility management functional entity, including one of an authentication function, a home location function or a visitor location function for mobility management, and for messaging between two mobility management functional entities.

12. The module of claim 11, wherein a message comprises common fields and message-specific data and the common mobility management protocol further comprises:

a service request message comprising an identity of an element and a domain requesting service, supported security and a suggested lifetime for a service relationship.

13. The module of claim 1, wherein the template comprises an address string including a Boolean flag indicator as a wild card.

14. A method performed by a computer processing device for messaging between a first application and a second application according to a common mobility management protocol, the method comprising:

receiving a descriptor request message at a descriptor owning functional entity, the descriptor comprising a unique identifier for the descriptor that includes a time the descriptor last changed, at least one address template having a template life field and a functional entity identifier indicating an associated functional entity of the descriptor;

matching the descriptor request message with a plurality of templates; and

transmitting a descriptor confirmation message with all matching templates, wherein the descriptor comprises a group of at least one template, the template defining one of a set of at least one address identifier and service profile data, and wherein the common mobility management protocol further comprises a visitor location function and a home location function.

15. The method of claim 14, wherein the first application further comprises a management application functional entity and a mobility management functional entity.

16. The method of claim 15, wherein the second application further comprises a mobility management functional entity.