H.323 user, service and service provider mobility framework for the multimedia intelligent networking

• US 7,346,022 B1
• Filed: 08/18/2000
• Issued: 03/18/2008
• Est. Priority Date: 09/28/1999
• Status: Expired due to Fees

• Current Assignee: AT&T Corporation (AT&T, Inc.)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: Roy, Radhika R.
• Primary Examiner(s): NGUYEN, BRIAN D
• Application Number:
  US09/642,980
• Time in Patent Office: 2,769 Days
• Field of Search: 370/313, 370/328, 370/331, 370/338, 370/401, 370/352, 370/329, 370/465, 370/466, 455/432.1, 455/433, 455/435.1, 455/436, 455/445, 379/91.01, 379/93.12, 379/93.22, 379/100.04, 379/114.01, 379/114.02, 379/114.03, 379/114.25
• US Class Current: 370/328
• CPC Class Codes: H04L 2101/30 Types of network names
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/2596 Translation of addresses of the same type other than IP, e.g. translation from MAC to MAC addresses
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/301 Name conversion
• CPC Class Codes: H04L 61/4547 for personal communications, i.e. using a personal identifier
• CPC Class Codes: H04L 61/4588 containing mobile subscriber information, e.g. home subscriber server [HSS]
• 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 9/40 Network security protocols

Abstract

The present invention provides a method and system for assuring H.323 alias address portability to an H.323 user in real-time H.323 multimedia communications where the H.323 user is registered with a home gatekeeper for the home zone of the H.323 user. Alias address portability may be obtained using a central database that is known to the administrative zones and is used for alias address mapping, or alternatively, may be obtained by using a distributed database. The method may be implemented by: sending, by the H.323 user, a message with a called H.323 entity'"'"'s alias address, to the home gatekeeper to originate a call to the called H.323 entity; confirming that the alias address, services, and service providers are portable; converting the alias address to a called routable alias address for the called H.323 entity and sending the alias address to the H.323 user; and placing the call to the called H.323 entity.

Claims

1. A method comprising:

at a gatekeeper of a first domain, the gatekeeper associated with a location database, the location database comprising home user location information and visiting user location information;

receiving, from a calling H.323 entity registered with the gatekeeper and located in the first domain, a message comprising an alias address of a called H.323 entity, the message originating a call to the called H.323 entity, the called H.323 entity registered as a home entity in a second domain, the called H.323 entity registered as a visitor in a third domain;

receiving a called routable alias address for the called H.323 entity, the called routable alias address associated with the alias address of the called H.323 entity, the called routable alias address received from a non-gatekeeper database external to the fist domain, the second domain, and the third domain; and

sending the called routable alias address to the calling H.323 entity.

2. The method of claim 1, further comprising:

registering the calling H.323 entity with the gatekeeper.

3. The method of claim 1, further comprising:

providing location information related to the calling H.323 entity to the non-gatekeeper database.

4. The method of claim 1, further comprising:

notifying the calling H.323 entity of an approximation of a cost of making the call.

5. The method of claim 1, further comprising:

determining that the calling H.323 entity is visiting the first domain.

6. The method of claim 1, further comprising:

accessing a multimedia call forwarding service for the call based upon information about the calling H.323 entity obtained from the non-gatekeeper database.

7. The method of claim 1, further comprising:

accessing a multimedia call transfer service for the call based upon information about the calling H.323 entity obtained from the non-gatekeeper database.

9. The method of claim 1, further comprising:

determining a service quality for the call based upon information about the calling H.323 entity obtained from the non-gatekeeper database.

10. The method of claim 1, further comprising:

determining a network reliability for the call based upon information about the calling H.323 entity obtained from the non-gatekeeper database.

11. The method of claim 1, further comprising:

storing the called routable alias address in a gatekeeper cache memory.

12. The method of claim 1, wherein an alias address assigned to an H.323 user is kept fixed as the user moves from one physical place to another.

13. The method of claim 1, wherein an alias address assigned to an H.323 user is kept fixed as the user moves from one logical place to another.

14. The method of claim 1, wherein an alias address assigned to an H.323 user is kept fixed as the user moves from one domain to another.

15. The method of claim 1, wherein a first content portion of the call is routed via a different communication path from a second content portion of the call.

16. The method of claim 1, wherein audio content of the call is routed via a different communication path from non-audio content of the call.

17. The method of claim 1, wherein video content of the call is routed via a different communication path from non-video content of the call.

18. The method of claim 1, wherein the call is routed via multiple carriers.

19. The method of claim 1, wherein the called H.323 entity is associated with a common terminal in the second domain and in the third domain.

20. The method of claim 1, wherein the call is a point-to-multipoint call placed to a plurality of called H.323 entities.

21. The method of claim 1, wherein the call is a multipoint-to-multipoint call placed between a plurality of calling H.323 entities to a plurality of called H.323 entities.

22. The method of claim 1, wherein the alias address is an E.164 number.

23. The method of claim 1, wherein the alias address is a transport address.

8. The method of claim , further comprising:

determining that the calling H.323 entity is visiting the first domain and associated with a first H.323 service provider; and

placing the call via a second H.323 service provider.