COMMON MOBILITY MANAGEMENT PROTOCOL FOR MULTIMEDIA APPLICATIONS, SYSTEMS AND SERVICES

• US 20150016422A1
• Filed: 09/29/2014
• Published: 01/15/2015
• Est. Priority Date: 04/25/2001
• Status: Active Grant

• Current Assignee: AT&T Corporation (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Roy, Radhika R.
• Granted Patent: US 10,178,543 B2
• Time in Patent Office: Days
• US Class Current: 370/331
• 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 includes 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 existing 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. The disclosure presents 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.

Claims

1. A method comprising:

receiving a descriptor request message at a descriptor owning functional entity;

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

transmitting a descriptor confirmation message with all matching templates.

2. The method of claim 1, wherein the descriptor request message is received from a management application functional entity and transmitted to a mobility management functional entity.

3. The method of claim 2, wherein the mobility management functional entity comprises one of an authentication function, a home location function, and a visitor location function for mobility management.

4. The method of claim 1, further comprising resolving mobile terminal conflicts responsive to receipt of a descriptor, wherein a descriptor owning functional entity owns the descriptor.

5. The method of claim 1, wherein the descriptor comprises address data, routing data and service profile data.

6. The method of claim 1, wherein the template further comprises a template life field.

7. The method of claim 6, further comprising:

caching a copy of the template for a period of time specified by the template life field.

8. A system comprising:

a processor; and

a computer-readable storage medium having instructions stored which, when executed by the processor, cause the processor to perform operations comprising;

receiving a descriptor request message at a descriptor owning functional entity;

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

transmitting a descriptor confirmation message with all matching templates.

9. The system of claim 8, wherein the descriptor request message is received from a management application functional entity and transmitted to a mobility management functional entity.

10. The system of claim 9, wherein the mobility management functional entity comprises one of an authentication function, a home location function, and a visitor location function for mobility management.

11. The system of claim 8, the computer-readable storage medium having additional instructions stored which, when executed by the processor, result in operations comprising resolving mobile terminal conflicts responsive to receipt of a descriptor, wherein a descriptor owning functional entity owns the descriptor.

12. The system of claim 8, wherein the descriptor comprises address data, routing data and service profile data.

13. The system of claim 8, wherein the template further comprises a template life field.

14. The system of claim 13, the computer-readable storage medium having additional instructions stored which, when executed by the processor, result in operations comprising:

caching a copy of the template for a period of time specified by the template life field.

15. A computer-readable storage device having instructions stored which, when executed by a computing device, cause the computing device to perform operations comprising:

receiving a descriptor request message at a descriptor owning functional entity;

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

transmitting a descriptor confirmation message with all matching templates.

16. The computer-readable storage device of claim 15, wherein the descriptor request message is received from a management application functional entity and transmitted to a mobility management functional entity.

17. The computer-readable storage device of claim 16, wherein the mobility management functional entity comprises one of an authentication function, a home location function, and a visitor location function for mobility management.

18. The computer-readable storage device of claim 15, having additional instructions stored which, when executed by the computing device, result in operations comprising resolving mobile terminal conflicts responsive to receipt of a descriptor, wherein a descriptor owning functional entity owns the descriptor.

19. The computer-readable storage device of claim 15, wherein the descriptor comprises address data, routing data and service profile data.

20. The computer-readable storage device of claim 15, wherein the template further comprises a template life field.