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

• US 7,317,703 B2
• Filed: 10/17/2005
• Issued: 01/08/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:
  US11/251,672
• Publication Number:
  US 20060039324A1
• Time in Patent Office: 813 Days
• Field of Search: 370/328, 370/331, 370/338, 455/432.1, 455/433, 455/435.1, 455/436
• 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:

receiving a request for a first routable address associated with an alias address of a first called H.323 entity at a non-gatekeeper database external to a first domain in which the first called H.323 entity is located, the non-gatekeeper database external to a second domain in which a calling H.323 entity is located; and

providing the first routable address to a cache at a gatekeeper associated with the calling H.323 entity, the gatekeeper configured to remove a second routable address associated with a second called H.323 entity responsive to a cache policy and responsive to receiving the first routable address.

2. The method of claim 1, wherein the calling H.323 entity is visiting the second domain.

3. The method of claim 1, wherein the first called H.323 entity is visiting the first domain.

4. The method of claim 1, further comprising:

placing a call comprising multimedia communications responsive to receiving the first routable address.

5. The method of claim 1, further comprising:

registering the calling H.323 entity with the gatekeeper.

6. The method of claim 1, further comprising:

registering the calling H.323 entity in a home zone of a gatekeeper database.

7. The method of claim 1, further comprising:

registering the calling H.323 entity in a visitor zone of a gatekeeper database.

8. The method of claim 1, further comprising:

updating a home zone of a gatekeeper database associated the calling H.323 entity with information indicative of a location of the calling H.323 entity.

9. The method of claim 1, further comprising:

updating a home zone of a gatekeeper database associated the first called H.323 entity with information indicative of a location of the first called H.323 entity.

10. The method of claim 1, further comprising:

synchronizing the non-gatekeeper database with at least one other network database.

11. The method of claim 1, further comprising:

querying the non-gatekeeper database to obtain a current location of the first called H.323 entity.

12. The method of claim 1, further comprising:

caching the first routable address and the alias address of the first called H.323 entity at the gatekeeper associated with the calling H.323 entity.

13. The method of claim 1, further comprising:

caching the first routable address and the alias address of the first called H.323 entity at the gatekeeper associated with the calling H.323 entity responsive to the cache policy.

14. The method of claim 1, further comprising:

establishing the cache policy when the cache at the gatekeeper associated with the calling H.323 entity is full; and

caching the first routable address and the alias address of the first called H.323 entity in the cache responsive to the cache policy.

15. The method of claim 1, further comprising:

confirming that the alias address of the first called H.323 entity is portable.

16. The method of claim 1, further comprising:

responsive to a routable alias address, providing a billing rate to the calling H.323 entity for a multimedia communication.

17. The method of claim 1, further comprising:

determining a quality of service associated with the calling H.323 entity.

18. The method of claim 1, further comprising:

determining a quality of service associated with the calling H.323 entity; and

placing a multimedia call to the first routable address responsive to the quality of service associated with the calling H.323 entity.