Common mobility management protocol for multimedia applications, systems and services

• US 10,178,543 B2
• Filed: 09/29/2014
• Issued: 01/08/2019
• Est. Priority Date: 04/25/2001
• Status: Expired due to Term

• Current Assignee: AT&T Corporation (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property II LP (AT&T, Inc.)
• Inventors: Roy, Radhika R.
• Primary Examiner(s): Kading, Joshua
• Application Number:
  US14/499,913
• Publication Number:
  US 20150016422A1
• Time in Patent Office: 1,562 Days
• 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, from a requesting descriptor functional entity, a descriptor request message at a descriptor owning functional entity, wherein;

the descriptor owning functional entity comprises one of a mobility management functional entity or a multimedia application functional entity;

a descriptor at the descriptor owning functional entity comprises one of address data having a wildcard character, routing data and service profile data; and

the descriptor is used for grouping together templates for completing calls to addresses;

receiving, at the descriptor owning functional entity, a request to resolve an alias address;

matching, via a processor of a computing device and based on the request, the descriptor request message with a template from a plurality of templates to yield a matched template, wherein the matched template comprises a common mobility management protocol that defines a set of address identifiers and profile information for completing an attempted communication to an identified address and the descriptor for carrying address information;

transmitting, via the processor of the computing device, a descriptor confirmation message with the matched template from the descriptor owning functional entity to the requesting descriptor functional entity; and

routing communications between a wireless node and the mobile terminal based on alias address identifiers within the matched template.

2. The method of claim 1, wherein the requesting descriptor functional entity comprises a management application 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, wherein the template further comprises a template life field.

5. The method of claim 4, further comprising:

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

6. A system comprising:

a processor; and

a memory having instructions stored which, when executed by the processor, cause the processor to perform operations comprising;

receiving, from a requesting descriptor functional entity, a descriptor request message at a descriptor owning functional entity, wherein;

the descriptor owning functional entity comprises one of a mobility management functional entity or a multimedia application functional entity;

a descriptor at the descriptor owning functional entity comprises one of address data having a wildcard character, routing data and service profile data; and

the descriptor is used for grouping together templates for completing calls to addresses;

receiving, at the descriptor owning functional entity, a request to resolve an alias address;

matching, based on the request, the descriptor request message with a template from a plurality of templates to yield a matched template, wherein the matched template comprises a common mobility management protocol that defines a set of address identifiers and profile information for completing an attempted communication to an identified address and the descriptor for carrying address information;

transmitting a descriptor confirmation message with the matched template from the descriptor owning functional entity to the requesting descriptor functional entity; and

routing communications between a wireless node and the mobile terminal based on alias address identifiers within the matched template.

7. The system of claim 6, wherein the requesting descriptor functional entity comprises a management application functional entity.

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

9. The system of claim 6, wherein the template further comprises a template life field.

10. The system of claim 9, the memory 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.

11. A memory having instructions stored which, when executed by a computing device, cause the computing device to perform operations comprising:

receiving, from a requesting descriptor functional entity, a descriptor request message at a descriptor owning functional entity, wherein;

the descriptor owning functional entity comprises one of a mobility management functional entity or a multimedia application functional entity;

a descriptor at the descriptor owning functional entity comprises one of address data having a wildcard character, routing data and service profile data; and

the descriptor is used for grouping together templates for completing calls to addresses;

receiving, at the descriptor owning functional entity, a request to resolve an alias address;

matching, based on the request, the descriptor request message with a template from a plurality of templates to yield a matched template, wherein the matched template comprises a common mobility management protocol that defines a set of address identifiers and profile information for completing an attempted communication to an identified address and the descriptor for carrying address information;

transmitting a descriptor confirmation message with the matched template from the descriptor owning functional entity to the requesting descriptor functional entity; and

routing communications between a wireless node and the mobile terminal based on alias address identifiers within the matched template.

12. The memory of claim 11, wherein the requesting descriptor functional entity comprises a management application functional entity.

13. The memory of claim 12, wherein the mobility management functional entity comprises one of an authentication function, a home location function, and a visitor location function for mobility management.

14. The memory of claim 11, wherein the template further comprises a template life field.