IP Library Granted Patent US 6,859,448
Granted Patent B1
US 6,859,448 · App. 09/642,279 · Granted Feb 22, 2005

H.323 mobility protocol for terminal, user and service mobility

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 6,859,448
App. No.
09/642,279
Granted
Feb 22, 2005
Kind
B1
Abstract

The H.323 standard is extended to support mobility in a multimedia communication system with services over packet-based networks. Such mobility is supported in a transport independent way. New H.323 messages and/or message elements have been created, and extensions to existing messages provided to accommodate mobility. Messages are provided to facilitate mobility binding as the mobile entity moves from one place to another. The mobile entity periodically registers with different gatekeepers to obtain support for an H.323 communication that includes at least one of audio, video and data.

Claims (43)

1. An H.323-based mobility protocol for real-time mobile multimedia communications and conferencing over packet-based networks by a Mobile Terminal/Node/Entity having a Home Gatekeeper/Home Location Database, comprising the steps of:

upon becoming mobile and initiating by the Mobile Terminal/Node/Entity an H.323 communication that includes at least one of: audio, video and data, with respect to notification of available support services, one of the following:

providing, by at least one of a plurality of available H.323 Home/Foreign Mobility Gatekeepers, notification of H.323 mobility services availability by periodically broadcasting/multicasting/unicasting a Mobility Gatekeeper Advertisement with a multicast address; and

where the Mobile Terminal/Node/Entity lacks notification of H.323 mobility services availability, broadcasting/multicasting/unicasting/sending, by the Mobile Terminal/Node/Entity, a message to the Home Gatekeeper/Home Location Database, which notifies H.323 Home/Foreign Mobility Gatekeepers in a preselected area local to the Mobile Terminal/Node/Entity that the Mobile Terminal/Node/Entity needs H.323 mobility services and notifying, by the H.323 Home/Foreign Mobility Gatekeepers, the Mobile Terminal/Node/Entity of available H.323 Home/Foreign Mobility Gatekeepers; and thereafter

registering, by the Mobile Terminal/Node Entity, with a H.323 Home/Foreign Mobility Gatekeeper of the available H.323 Home/Foreign Mobility Gatekeepers that support H.323 mobility services in a Location Area/Cell/zone of the Mobile Terminal/Node/Entity; and

providing, for the Mobile Terminal/Node/Entity by the H.323 Home/Foreign Mobility Gatekeeper with which the Mobile Terminal/Node/Entity is registered, support for the H.323 communication that includes at least one of: audio, video and data.

2. The H.323-based mobility protocol of claim 1 wherein registering with the H.323 Home/Foreign Mobility Gatekeeper includes sending registration information for the Mobile Terminal/Node/Entity using a Base Station to Base Station Controller to Mobile Switching Center to H.323 Home/Foreign Gatekeeper system.

3. The H.323-based mobility protocol of claim 1 wherein registering with the at least one H.323 Home/Foreign Mobility Gatekeeper includes sending registration information for the Mobile Terminal/Node/Entity using a wireless/wire-line Local Area Network to Router/Switch to H.323 Home/Foreign Gatekeeper system.

4. The H.323-based mobility protocol of claim 1 wherein registering includes the steps of:

broadcasting/multicasting/unicasting/sending, by the Home Gatekeeper, a Mobility Gatekeeper Advertisement (MGA) message periodically;

broadcasting/multicasting/unicasting/sending a registration request message (RRQ) to the Home Gatekeeper by the Mobile Terminal/Node/Entity; and

sending, by the Home Gatekeeper, a registration confirmation/registration rejection (RCF/RRJ) to the Mobile Terminal/Node/Entity.

5. The H.323-based mobility protocol of claim 1 wherein registering includes the steps of:

upon determining, by the Mobile Terminal/Node/Entity, that a network point of attachment has changed/a foreign zone has been entered,

broadcasting/multicasting/unicasting/sending, by the Mobile Terminal/Node/Entity, a registration request message (RRQ) to a Foreign/Visiting Gatekeeper;

broadcasting/multicasting/unicasting/sending, by the Foreign/Visiting Gatekeeper, a binding update message (BuRQ) to the Home Gatekeeper;

broadcasting/multicasting/unicasting/sending, by the Home Gatekeeper, a binding update confirmation/rejection (BuCF/BuRJ) to the Foreign/Visiting Gatekeeper; and

broadcasting/multicasting/unicasting/sending, by the Foreign/Visiting Gatekeeper, the binding update confirmation/rejection to the Mobile Terminal/Node/entity.

6. The H.323-based mobility protocol of claim 5 wherein, where the Mobile Terminal/Node/Entity has already visited another foreign zone regulated by a Visited Gatekeeper, registering includes:

broadcasting/multicasting/unicasting/sending, by the Home Gatekeeper, a mobility unbinding message (UbRQ) to the Visited Gatekeeper; and

broadcasting/multicasting/unicasting/sending, by the Visited Gatekeeper, a mobility unbinding confirmation/rejection (UbCF/UbRJ) to the Home Gatekeeper.

7. The H.323-based mobility protocol of claim 1 wherein, where the Mobile Terminal/Node/Entity has already visited another foreign zone regulated by a Visited Gatekeeper, registering includes:

broadcasting/multicasting/unicasting/sending, by the Mobile Terminal/Node/Entity, a registration request message (RRQ) to a Foreign/Visiting Gatekeeper;

broadcasting/multicasting/unicasting/sending, by the Foreign/Visiting Gatekeeper, a mobility unbinding update message (UbRQ) to the Visited Gatekeeper;

broadcasting/multicasting/unicasting/sending, by the Visited Gatekeeper, a mobility unbinding confirmation/rejection (UbCF/UbRJ) to the Foreign/Visiting Gatekeeper;

broadcasting/multicasting/unicasting/sending, by the Foreign/Visiting Gatekeeper, a provisional registration confirmation to the Mobile Terminal/Node/Terminal and broadcasting/multicasting/unicasting/sending, by the Foreign/Visiting Gatekeeper, a binding update message (BURQ) to the Home Gatekeeper; and

broadcasting/multicasting/unicasting/sending, by the Home Gatekeeper, a binding update confirmation/rejection (BuCF/BuRJ) to the Foreign/Visiting Gatekeeper.

8. The H.323-based mobility protocol of claim 1 wherein, where the Mobile Terminal/Node/Entity has already visited another foreign zone regulated by a Visited Gatekeeper, registering includes:

broadcasting/multicasting/unicasting/sending, by the Mobile Terminal/Node/Entity, a registration request (RRQ) to a Foreign/Visiting Gatekeeper;

broadcasting/multicasting/unicasting/sending, by the Visited Gatekeeper, a mobility unbinding confirmation/rejection (UbCF/UbRJ) to the Foreign/Visiting Gatekeeper;

broadcasting/multicasting/unicasting/sending, by the Foreign/Visiting Gatekeeper, a provisional registration confirmation to the Mobile Terminal/Node/Terminal and broadcasting/multicasting/unicasting/sending, by the Foreign/Visiting Gatekeeper, a binding update message (BURQ) to the Home Gatekeeper;

broadcasting/multicasting/unicasting/sending, by the Home Gatekeeper, a binding update confirmation/rejection (BuCF/BuRJ) to the Foreign/Visiting Gatekeeper;

broadcasting/multicasting/unicasting/sending, by the Home Gatekeeper, a mobility unbinding update message (UbRQ) to the Visited Gatekeeper, and

broadcasting/multicasting/unicasting/sending, by the Visited Gatekeeper, a mobility unbinding confirmation/rejection (UbCF/UbRJ) to the Home Gatekeeper.

9. The H.323-based mobility protocol of claim 1 wherein at least one Home/Foreign Gatekeeper utilizes a combined Home/Visitor Location Database.

10. The H.323-based mobility protocol of claim 1 wherein a plurality of Home/Foreign Gatekeepers each utilize an individual Visitor Location Database and share a Home Location Database.

11. The H.323-based mobility protocol of claim 1 wherein, where the Mobile Terminal/Node/Entity is originally located in a First Administrative Domain and is moving in a Second Administrative Domain, registering includes:

broadcasting/multicasting/unicasting/sending a registration request message (RRQ), by the Mobile Terminal/Node/Entity to the Foreign/Visiting Gatekeeper;

broadcasting/multicasting/unicasting/sending, by the Foreign/Visiting Gatekeeper, a mobility unbinding (UbRQ) message to a Visited Gatekeeper;

broadcasting/multicasting/unicasting/sending, by the Visited Gatekeeper, an unbinding confirmation/rejection (UbCF/UbRJ) to the Visiting/Foreign Gatekeeper;

broadcasting/multicasting/unicasting/sending, by the Visiting Gatekeeper, a provisional registration message to the Mobile Terminal/Node/Entity;

broadcasting/multicasting/unicasting/sending, by the Foreign/Visiting Gatekeeper, a mobility binding message (BuRQ) to a Border Element of the Second Administrative Domain, which forwards the message to a Border Element of the First Administrative Domain which then forwards the message to the Home Gatekeeper; and

broadcasting/multicasting/unicasting/sending, by the Home Gatekeeper, a mobility binding confirmation/rejection (BuCF/BuRJ) message to the Border Element of the First Administrative Domain, which forwards the message to the Border Element of the Second Administrative Domain, which forwards the message to the Visiting Gatekeeper.

Assignments (6)
CORRECTIVE ASSIGNMENT TO CORRECT THE REMOVE PATENT NUMBERS 10342096;10671117; 10716375; 10716376;10795407;10795408; AND 10827591 PREVIOUSLY RECORDED AT REEL: 58314 FRAME: 657. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Feb 29, 2024
From: RAKUTEN, INC.
To: RAKUTEN GROUP, INC.
Reel/Frame 068066/0103 →
CHANGE OF NAME Recorded Dec 6, 2021
From: RAKUTEN, INC.
To: RAKUTEN GROUP, INC.
Reel/Frame 058314/0657 →
CHANGE OF ADDRESS Recorded Dec 17, 2015
From: RAKUTEN, INC.
To: RAKUTEN, INC.
Reel/Frame 037751/0006 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 26, 2012
From: AT&T INTELLECTUAL PROPERTY II, L.P.
To: RAKUTEN, INC.
Reel/Frame 029195/0519 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 4, 2012
From: AT&T PROPERTIES, LLC
To: AT&T INTELLECTUAL PROPERTY II, L.P.
Reel/Frame 028313/0451 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 1, 2012
From: AT&T CORP.
To: AT&T PROPERTIES, LLC
Reel/Frame 028304/0242 →