USRE42920EExpiredUtility
System and method for inter-domain mobility management
Est. expiryMay 2, 2020(expired)· nominal 20-yr term from priority
Inventors:Radhika R. Roy
H04L 65/1106H04L 65/1101H04L 9/40H04M 3/42272H04W 80/10H04L 65/1043H04M 7/006
52
PatentIndex Score
0
Cited by
47
References
40
Claims
Abstract
The present invention relates to a method and apparatus for inter-domain mobility management for a telephony network. The present invention also relates generally to the H.323 standard for transmitting audio and video data streams, and more particularly to extending the H.323 standard to support mobility in a multimedia communication system with services over packet-based networks.
Claims
exact text as granted — not AI-modified1. An inter-domain mobility management method, comprising:
(a) a mobile H.323. entity communicating sending information related to the mobile entity with to a first gatekeeper in a first administration administrative domain;
(b) said first gatekeeper being unable to verify said information on related to said mobile H.323 entity and sending information to accessing a first border element within said first administration administrative domain to resolve said information related to the mobile entity;
(c) said first border element communicating information with accessing a second border element in a second administrative domain to resolve said information related to the mobile entity;
(d) said second border element communicates sending back with to said first border element with information to resolve information that resolves said information related to the mobile entity; and
(e) said second first border element accepting said resolved information related to the mobile entity and communicates said information with sending to said mobile H.323 entity via said first gatekeeper a reply to the information related to the mobile entity sent by said mobile H.323 entity.
2. The method of claim 1 wherein said information received by related to the mobile entity sent to said first gatekeeper is transferred via said second border element to a second gatekeeper within said first second administrative domain.
3. The method of claim 1 wherein said second administrative domain is the a home administrative domain for said mobile H.323 entity.
4. The method of claim 1 wherein said first administrative domain is a serving, visiting, visited or foreign administrative domain for said mobile H.323 entity.
5. The method of claim 1 wherein said first gatekeeper requests receives said information related to the mobile entity to register, authenticate, verify, resolve, or allocate resources to said mobile H.323 entity.
6. An inter-domain mobility management method, comprising:
(a) a mobile H.323 entity communicating sending information related to the mobile entity with to a first gatekeeper in a first administrative domain having a first backend services;
(b) said first gatekeeper being unable to verify said information on related to said mobile H.323 entity and sending information to accessing a first border element within said first administrative domain to resolve said information related to the mobile entity;
(c) said first border element communicating information with accessing a second border element in a second administrative domain to resolve said information related to the mobile entity;
(d) said second border element obtains information obtaining from a second backend services in said second administrative domain information that resolves said information related to the mobile entity and communicates sending back with to said first border element with information to resolve said information related to the mobile entity the information obtained from said second border element; and
(e) said second first border element accepting said resolved information related to the mobile entity and communicates said information with sending to said mobile H.323 entity via said first gatekeeper a reply to the information related to the mobile entity sent by said mobile H.323 entity.
7. The method of claim 6 wherein said information received by related to the mobile entity sent to said first gatekeeper is transferred via said second border element to a second gatekeeper within said first second administrative domain.
8. The method of claim 6 wherein said second administrative domain is the a home administrative domain for said mobile H.323 entity.
9. The method of claim 6 wherein said first administrative domain is a serving, visiting, visited or foreign administrative domain for said mobile H.323 entity.
10. The method of claim 6 wherein said first gatekeeper requests receives said information related to the mobile entity to register, authenticate, verify, resolve, or allocate resources to said mobile H.323 entity.
11. The method of claim 6 , wherein the information obtained by said second border element from said second backend services is stored within said first backend services.
12. The method of claim 6 wherein the information obtained by said second border element from said second backend services is stored within said first backend services and wherein subsequently said first backend services provides home location functions.
13. The method of claim 6 wherein the information obtained by said second border element from said second backend services is stored within said first backend services and wherein subsequently said first backend services provides home location functions, and wherein said home location functions provides at least one services selected from a group consisting of address, registration, verification, resolution, allocation and authentication.
14. An inter-domain mobility management method, comprising:
(a) a mobile H.323. entity communicating sending information related to the mobile entity with to a first gatekeeper in a first administration administrative domain having a first backend services;
(b) said first gatekeeper being unable to verify said information on related to said mobile H.323 entity and sending information to accessing a first border element within said first administration administrative domain to resolve said information related to the mobile entity;
(c) said first border element communicating information with accessing a first backend services to resolve said information related to the mobile entity, wherein said first backend services is shared with both by said first administrative domain and a second administrative domain;
(d) said second first border element obtains information obtaining from said first backend services in said first and said second administrative domain information that resolves said information related to the mobile entity, and communicates sending it back to said first border element with information to resolve said information related to the mobile entity; and
(e) said second first border element accepting said resolved information related to the mobile entity and communicates said information with sending to said mobile H.323 entity via said first gatekeeper a reply to the information related to the mobile entity sent by said mobile H.323 entity.
15. The method of claim 14 wherein said information received by related to the mobile entity sent to said first gatekeeper is transferred via said second border element to a second gatekeeper within said first second administrative domain.
16. The method of claim 14 wherein said second administrative domain is the a home administrative domain for said mobile H.323 entity.
17. The method of claim 14 wherein said first administrative domain is a serving, visiting, visited or foreign administrative domain for said mobile H.323 entity.
18. The method of claim 14 wherein said first gatekeeper requests receives said information related to the mobile entity to register, authenticate, verify, resolve, or allocate resources to said mobile H.323 entity.
19. The method of claim 14 wherein a the mobile H.323 entity in said first administrative domain communicates with said first backend services.
20. An inter-domain mobility management method, comprising:
(a) a mobile H.323. entity communicating sending information related to the mobile entity with to a first gatekeeper in a first administration administrative domain having a first backend services;
(b) said first gatekeeper being unable to verify said information on related to said mobile H.323 entity and sending information to accessing a first border element within said first administration administrative domain to resolve said information related to the mobile entity;
(c) said first border element communicating information with accessing a second border element in a second administrative domain to resolve said information related to the mobile entity;
(d) said second border element obtains obtaining information from a second backend services in said second administrative domain via at least one a second gatekeeper in said second administrative domain and communicates back with sending back to said first border element with information to resolve said information related to the mobile entity the information obtained from the second backend service; and
(e) said second first border element accepting said resolved information related to the mobile entity and communicates said information with sending to said mobile H.323 entity via said first gatekeeper a reply to the information related to the mobile entity sent by said mobile H.323 entity.
21. The method of claim 20 wherein said information received by related to the mobile entity sent to said first gatekeeper is transferred via said second border element to a second gatekeeper within said first second administrative domain.
22. The method of claim 20 wherein said second administrative domain is the a home administrative domain for said mobile H.323 entity.
23. The method of claim 20 wherein said first administrative domain is a serving, visiting, visited or foreign administrative domain for said mobile H.323 entity.
24. The method of claim 20 wherein said first gatekeeper requests receives said information related to the mobile entity to register, authenticate, verify, resolve, or allocate resources to said mobile H.323 entity.
25. An inter-domain mobility management method, comprising:
(a) a mobile H.323. entity communicating sending information related to the mobile entity with to a first gatekeeper in a first administration administrative domain having a first location function;
(b) said first gatekeeper being unable to verify said information on related to said mobile H.323 entity and sending information to accessing a first border element within said first administration administrative domain to resolve said information related to the mobile entity;
(c) said first border element communicating information with accessing a second border element in a second administrative domain to resolve said information related to the mobile entity;
(d) said second border element obtains obtaining information from a second home location function in said second administrative domain and communicates sending back with to said first border element with information to resolve said information related to the mobile entity the information obtained from said second location function; and
(e) said second first border element accepting said resolved information related to the mobile entity and communicates said information with sending to said mobile H.323 entity via said first gatekeeper a reply to the information related to the mobile entity sent by said mobile H.323 entity.
26. The method of claim 25 wherein said information received by related to the mobile entity sent to said first gatekeeper is transferred via said second border element to a second gatekeeper within said first second administrative domain.
27. The method of claim 25 wherein said second administrative domain is the a home administrative domain for said mobile H.323 entity.
28. The method of claim 25 wherein said first administrative domain is a serving, visiting, visited or foreign administrative domain for said mobile H.323 entity.
29. The method of claim 25 wherein said first gatekeeper requests receives said information related to the mobile entity to register, authenticate, verify, resolve, or allocate resources to said mobile H.323 entity.
30. The method of claim 25 wherein the information obtained by said second border element from said second home location function is stored within said first home location function.
31. The method of claim 25 wherein the information obtained by said second border element from said second home location function is stored within said first home location function and wherein subsequently said first home location function provides home location functions.
32. The method of claim 25 wherein the information obtained by said second border element from said second home location function is stored within said first home location function and wherein subsequently said first home location function provides home location functions, and wherein said home location functions provides at least one services selected from a group consisting of address, registration, verification, resolution, allocation and authentication.
33. An inter-domain mobility management method, comprising:
(a) a mobile H.323. entity communicating sending information related to the mobile entity with to a first gatekeeper in a first administration administrative domain having a first location function;
(b) said first gatekeeper being unable to verify said information on related to said mobile H.323 entity and sending information to accessing a first border element within said first administration administrative domain to resolve said information related to the mobile entity;
(c) said first border element communicating information with accessing a second border element in a second administrative domain to resolve said information related to the mobile entity;
(d) said second border element obtains obtaining information from a second home location function in said second administrative domain via at least one a second gatekeeper in said second administrative domain and communicates sending back with to said first border with information to resolve said information related to the mobile entity element the information obtained from said second location function; and
(e) said second first border element accepting said resolved information related to the mobile entity and communicates said information with sending to said mobile H.323 entity via said first gatekeeper a reply to the information related to the mobile entity sent by said mobile H.323 entity.
34. The method of claim 33 wherein said information received by related to the mobile entity sent to said first gatekeeper is transferred via said second border element to a second gatekeeper within said first second administrative domain.
35. The method of claim 33 wherein said second administrative domain is the a home administrative domain for said mobile H.323 entity.
36. The method of claim 33 wherein said first administrative domain is a serving, visiting, visited or foreign administrative domain for said mobile H.323 entity.
37. The method of claim 33 wherein said first gatekeeper requests receives said information related to the mobile entity to o register, authenticate, verify, resolve, or allocate resources to said mobile H.323 entity.
38. The method of claim 33 wherein the information obtained by said second border element from said second home location function is stored within said first home location function.
39. The method of claim 33 wherein the information obtained by said second border element from said second home location function is stored within said first home location function and wherein subsequently said first home location function provides home location functions.
40. The method of claim 33 wherein the information obtained by said second border element from said second home location function is stored within said first home location function and wherein subsequently said first home location function provides home location functions, and wherein said home location functions provides at least one services selected from a group consisting of address, registration, verification, resolution, allocation and authentication.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.