Hierarchical level-based internet protocol multicasting

• US 20020150094A1
• Filed: 10/26/2001
• Published: 10/17/2002
• Est. Priority Date: 10/27/2000
• Status: Abandoned Application

• Current Assignee: TTI Inventions A LLC (Intellectual Ventures LLC)
• Original Assignee: TTI Inventions A LLC (Intellectual Ventures LLC)
• Inventors: Lee, John, Cheng, Matthew, Barton, Melbourne
• Application Number:
  US10/036,032
• Publication Number:
  US 20020150094A1
• Time in Patent Office: Days
• US Class Current: 370/389
• CPC Class Codes: H04L 12/185 with management of multicast group membership
• CPC Class Codes: H04L 12/1854 with non-centralised forwarding system, e.g. chaincast
• CPC Class Codes: H04L 12/1868 Measures taken after transmission, e.g. acknowledgments
• CPC Class Codes: H04L 12/189 in combination with wireless systems selective distribution or broadcast in wireless communication networks H04W4/06
• CPC Class Codes: H04L 45/04 Interdomain routing, e.g. hierarchical routing
• CPC Class Codes: H04L 45/16 Multipoint routing
• CPC Class Codes: H04W 40/02 Communication route or path selection, e.g. power-based or shortest path routing
• CPC Class Codes: H04W 80/04 Network layer protocols, e.g. mobile IP [Internet Protocol]
• CPC Class Codes: H04W 88/005 Data network PoA devices

Abstract

Hierarchical Level-Based IP Multicasting (HLIM) is a method for the multicasting of data packets from a source to a number of receivers on a network that supports both host and network mobility. In HLIM, IP routers are assigned to hierarchical levels to become hierarchical designated routers. The hierarchical levels also are used to define a scope region in which multicast data packets are to be delivered. Each scope region is associated with a unique root identifier (RID). Scope region information and root identifiers are placed into a multicast address so that multicast packers of data will be distributed to routers and hosts within the scope region. If a host (receiver or source) or sub-network moves out of the scope region but desires to continue receiving multi-cast packets the host can request receipt of such packets from its new parent hierarchical designated router through use of the RID and associated binding point (BPT). In this manner, HLIM provides a shared and shortest-path multicast tree without using a center point like a core or rendezvous point. HLIM supports not only host mobility (movements of IP hosts) but also network mobility (movements of IP routers with/without hosts). HLIM is oriented to operate in hierarchical networks, but can be also applied to flat networks by emulating the networks into organized hierarchical networks through mechanisms such as the Private Network-to-Network Interface (“PNNI”) protocol used in ATM or multimedia support for mobile wireless networks (“MMWM”). Thus, HLIM can be implemented as long as the network nodes are connected in a hierarchy, physically or virtually.

Claims

1. A method for routing packets of data from a source to a plurality of routers and receivers in a hierarchical network comprising the steps of:

assigning each router in said network to one of a plurality of hierarchical levels;

identifying a scope region bounded by one or more of the plurality hierarchical levels in which to route said packets of data;

identifying a root identifier for the scope region;

forwarding packets of data from said source to the routers in the network wherein said packets of data contain data fields identifying the scope region and the root identifier of the scope region.

2. The method of claim 1 further comprising the steps of:

identifying each router that is capable of sending packets of data to or from a router at a higher or lower level as a hierarchical designated router;

identifying the root identifier for the scope region as the hierarchical designated router directly above the scope region.

3. The method of claim 2 further comprising the steps of:

identifying a binding point for providing a linkage between the scope region and a location for a receiver that has moved outside the scope region.

4. The method of claim 1 further comprising, prior to the forwarding step, the steps of:

receiving a packet of data at a router in the network;

determining whether the router is within the scope region specified in the data field identifying the scope region for the packet of data; and

,

discarding the data packet is the router is outside the scope region.

5. A method of joining a receiver to a multicast tree of a multicast session for receiving data packets from a source wherein the source is sending data packets to a plurality of routers in a scope region in a hierarchical network of routers for the mulitcast session having an application identifier comprising the steps of:

obtaining at the joining receiver the scope region and the application identifier of the multicast session from the source;

sending a root identifier request from the joining receiver to a first parent router to which said joining receiver is in communication wherein said root identifier request contains the scope region and the application identifier of the multicast session;

determining at the first parent router whether the first parent router is within the scope region;

if the first parent router is within the scope region, locating the root identifier for the scope region at the first parent router;

invoking a join operation at the first parent router to join the receiver to the multicast session;

and then replying from the first parent router to the receiver with a root identifier reply message once the join operation is completed.

6. The method of claim 5 wherein the step of invoking a join operation further comprises the steps of:

determining if the first parent router is part of the multicast tree;

if the first parent router is not part of the multicast tree, setting up a transient forwarding cache at the first parent router consisting of a group address and a corresponding outgoing interface for the joining receiver;

sending a join message from the first parent router to a second parent router;

receiving an acknowledge message from the second parent at the first parent router after the second parent router has joined the multicast tree.

7. The method of claim 6 further comprising:

determining at the first parent router if there is a transient forwarding cache for the group address specified in the acknowledge message;

switching the transient forwarding cache to a confirmed forwarding cache prior to replying with the root identifier to the receiver.

8. The method of claim 5 wherein the joining receiver receives the scope region and the application identifier from the source through the Internet.

9. The method of claim 5 wherein the joining receiver receives the scope region and the application identifier from the source through session announcement protocol.

10. The method of claim 5 wherein the joining receiver receives the scope region and the application identifier through session description protocol.

11. In a hierarchical network, a method for receiving at a receiver packets of data routed by routers from a source as part of a multicast session identified by a scope region having a unique root identifier and an application identifier wherein the receiver has moved from being in communication with a first router to being in communication with a second router comprising the step of:

sending a mobility report message from the mobile receiver to the second router wherein the mobility report message contains data identifying the scope region of the multicast session, the application identifier of the multicast session and the root identifier of the scope region.

12. The method of claim 11 further comprising the steps of:

receiving the mobility report message at the second router;

determining at the second router if the second router is outside the scope region; and

,

invoking a mobile join operation if the router is outside the scope region.

13. The method of claim 12 wherein the step of invoking a mobile join operation comprises the step of:

sending a mobile join message from the second router toward a third router toward the router associated with the root identifier.

14. The method of claim 13 wherein the step of sending a join message toward a router associated with the root identifier further comprises the steps of:

placing a transient entry in the forwarding cache indicating the router associated with the root identifier as source of data packets to be forwarded to the mobile receiver.

15. The method of claim 13 wherein the mobile join message is sent by the second router to all other routers with which it is in communication.

16. The method of claim 13 wherein the step of invoking the mobile join operation further comprises the steps of:

receiving the mobile join message at the third router;

determining at the third router whether the third router is the binding point for communication to the mobile receiver wherein the binding point is the router that provides a linkages between the scope region and the mobile receiver through the shortest path.

17. The method of claim 16 wherein the third router is the binding point if the address of the third router is equal to the root identifier or if the address of any ascendant router in which the third router is in communication is equal to the root identifier.

18. The method of claim 16 further comprising the steps of:

sending a mobile acknowledge message from the third router to the second router once the binding point has been determined.

19. The method of claim 18 further comprising the steps of:

sending a mobile reply message from the second router to the mobile receiver; and

,

forwarding packets of data from the multicast session to the mobile receiver through the binding point, the third router and the second router.

20. A method of forwarding packets of data from a multicast session in a network of routers arranged into a plurality of hierarchical levels comprising the step of forwarding packets of data between routers, wherein said packets of data contain data identifying a scope region containing the lower and upper hierarchical levels to which the packets will be forwarded, an application identifier for the multicast session and a unique root identifier for the scope region.