IP Library Granted Patent US 9,680,880
Granted Patent B2
US 9,680,880 · App. 11/456,607 · Granted Jun 13, 2017

Method and apparatus for supporting IP multicast

Inventor: Dennis Bijwaard (Enschede, NL)
Assignee: Alcatel-Lucent USA Inc.
H04L65/1006H04L12/18H04L41/08H04L41/0853H04L65/4076
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 9,680,880
App. No.
11/456,607
Filed
Jul 11, 2006
Granted
Jun 13, 2017
Kind
B2
Art Unit
2445
USPC
709/227
Abstract

The invention includes a method and apparatus for configuring legacy nodes to support multicast functions. The method includes determining, in response to a request for a first user device to join a multicast group, whether any node in a multicast path between the first user device and a second user device comprises a legacy node and forming, in response to a determination that a node in the multicast path is a legacy node, a message adapted for configuring the legacy node to start forwarding multicast traffic from a first interface to a second interface of the legacy node. The legacy node may be configured to stop forwarding multicast traffic from the first interface of the legacy node to the second interface of the legacy node. The legacy node may be configured to start/stop forwarding traffic from one or more input interfaces to one or more output interfaces.

Claims (47)

1. A method for enabling configuration of a legacy node to support multicasting of traffic of a multicast group from a first user device to a second user device, the method comprising:

using a processor for:

detecting, at the first user device, a request for the second user device to join the multicast group;

determining, at the first user device, whether any node in a multicast path between the first user device and the second user device is a legacy node, wherein a legacy node is a node without Internet Protocol (IP) multicast functionality; and

in response to a determination that a node in the multicast path is a legacy node, generating a configuration message at the first user device, wherein the configuration message is adapted for use in configuring the legacy node to forward multicast traffic of the multicast group from a first interface of the legacy node to a second interface of the legacy node.

2. The method of claim 1 , further comprising one of:

transmitting the configuration message toward the legacy node; and

transmitting the configuration message toward a multicast manager, wherein the multicast manager is configured to forward the configuration message toward the legacy node.

3. The method of claim 1 , wherein the request for the second user device to join the multicast group is initiated by one of the first user device, the second user device, and a multicast manager.

4. The method of claim 1 , wherein the request for the second user device to join the multicast group is conveyed using one of Session Initiation Protocol (SIP) signaling and Hypertext Transfer Protocol (HTTP) signaling.

5. The method of claim 1 , wherein determining whether any node in the multicast path is a legacy node comprises:

identifying each node in the multicast path between the first user device and the second user device; and

determining, for each node in the multicast path, whether the node is a legacy node.

6. The method of claim 1 , wherein the legacy node comprises one of a legacy router and a legacy web server.

7. The method of claim 1 , further comprising:

in response to a request for the second user device to leave the multicast group, generating a second configuration message at the first user device, wherein the second configuration message is adapted for use in configuring the legacy node to stop forwarding multicast traffic of the multicast group from the first interface of the legacy node to the second interface of the legacy node.

8. The method of claim 1 , wherein the configuration message is further adapted for use in configuring the legacy node to forward the multicast traffic from the second interface to the first interface.

9. An apparatus for enabling configuration of a legacy node to support multicasting of traffic of a multicast group from a first user device to a second user device, the apparatus comprising:

a processor and a memory, the processor configured to:

detect, at the first user device, a request for the second user device to join the multicast group;

determine, at the first user device, whether any node in a multicast path between the first user device and the second user device is a legacy node, wherein a legacy node is a node without Internet Protocol (IP) multicast functionality; and

in response to a determination that a node in the multicast path is a legacy node, generate a configuration message at the first user device, wherein the configuration message is adapted for use in configuring the legacy node to forward multicast traffic of the multicast group from a first interface of the legacy node to a second interface of the legacy node.

10. The apparatus of claim 9 , wherein the processor is further configured to:

transmit the configuration message toward the legacy node; or

transmit the configuration message toward a multicast manager, wherein the multicast manager is configured to forward the configuration message toward the legacy node.

11. The apparatus of claim 9 , wherein the request for the second user device to join the multicast group is initiated by one of the first user device, the second user device, and a multicast manager.

12. The apparatus of claim 9 , wherein the request for the second user device to join the multicast group is conveyed using one of Session Initiation Protocol (SIP) signaling and Hypertext Transfer Protocol (HTTP) signaling.

13. The apparatus of claim 9 , wherein determining whether any node in the multicast path is a legacy node comprises:

identifying each node in the multicast path between the first user device and the second user device; and

determining, for each node in the multicast path, whether the node is a legacy node.

14. The apparatus of claim 9 , wherein the legacy node comprises one of a legacy router and a legacy web server.

15. The apparatus of claim 9 , wherein the processor is further configured to:

transmit a second configuration message toward the node in response to a request for the second user device to leave the multicast group, wherein the second configuration message is adapted for use in configuring the legacy node to stop forwarding multicast traffic of the multicast group from the first interface of the legacy node to the second interface of the legacy node.

16. The apparatus of claim 9 , wherein the configuration message is further adapted for use in configuring the legacy node to forward the multicast traffic from the second interface to the first interface.

17. A method for enabling configuration of a legacy node to support multicasting of traffic of a multicast group from a first user device to a second user device, the method comprising:

using a processor for:

detecting, at a multicast manager, an indication that the second user device has joined the multicast group, wherein the indication is detected based on signaling associated with the first user device;

determining, at the multicast manager, whether any node in a multicast path between the first user device and the second user device is a legacy node, wherein a legacy node is a node without Internet Protocol (IP) multicast functionality; and

in response to a determination that a node in the multicast path is a legacy node, generating a configuration message at the multicast manager, wherein the configuration message is adapted for use in configuring the legacy node to forward multicast traffic of the multicast group from a first interface of the legacy node to a second interface of the legacy node.

18. The method of claim 17 , wherein the signaling associated with the first user device is Session Initiation Protocol (SIP) signaling.

19. The method of claim 18 , wherein the multicast manager is configured as a SIP Application Server, wherein the signaling associated with the first user device is detected by the multicast manager based on signaling between the first user device and the second user device.

20. The method of claim 18 , wherein the signaling associated with the first user device is directed from the first user device to the multicast manager.

21. An apparatus for enabling configuration of a legacy node to support multicasting of traffic of a multicast group from a first user device to a second user device, the apparatus comprising:

a processor and a memory, the processor configured to:

detect, at a multicast manager, an indication that the second user device has joined the multicast group, wherein the indication is detected based on signaling associated with the first user device;

determine, at the multicast manager, whether any node in a multicast path between the first user device and the second user device is a legacy node, wherein a legacy node is a node without Internet Protocol (IP) multicast functionality; and

in response to a determination that a node in the multicast path is a legacy node, generate a configuration message at the multicast manager, wherein the configuration message is adapted for use in configuring the legacy node to forward multicast traffic of the multicast group from a first interface of the legacy node to a second interface of the legacy node.

Assignments (14)
PATENT SECURITY AGREEMENT Recorded Aug 6, 2024
From: RPX CORPORATION; RPX CLEARINGHOUSE LLC
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 068328/0674 →
RELEASE OF LIEN ON PATENTS Recorded Aug 5, 2024
From: BARINGS FINANCE LLC
To: RPX CORPORATION
Reel/Frame 068328/0278 →
PATENT SECURITY AGREEMENT Recorded Apr 22, 2023
From: RPX CORPORATION
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 063429/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 28, 2021
From: PROVENANCE ASSET GROUP LLC
To: RPX CORPORATION
Reel/Frame 059352/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: NOKIA US HOLDINGS INC.
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058363/0723 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: CORTLAND CAPITAL MARKETS SERVICES LLC
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058983/0104 →
ASSIGNMENT AND ASSUMPTION AGREEMENT Recorded Feb 14, 2019
From: NOKIA USA INC.
To: NOKIA US HOLDINGS INC.
Reel/Frame 048370/0682 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP LLC
To: NOKIA USA INC.
Reel/Frame 043879/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP, LLC
To: CORTLAND CAPITAL MARKET SERVICES, LLC
Reel/Frame 043967/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 13, 2017
From: NOKIA TECHNOLOGIES OY; NOKIA SOLUTIONS AND NETWORKS BV; ALCATEL LUCENT SAS
To: PROVENANCE ASSET GROUP LLC
Reel/Frame 043877/0001 →
MERGER AND CHANGE OF NAME Recorded May 9, 2017
From: LUCENT TECHNOLOGIES INC.; ALCATEL USA MARKETING, INC.; ALCATEL USA SOURCING, INC.; LUCENT TECHNOLOGIES INC.
To: ALCATEL-LUCENT USA INC.
Reel/Frame 042310/0485 →
RELEASE OF SECURITY INTEREST Recorded Oct 9, 2014
From: CREDIT SUISSE AG
To: ALCATEL-LUCENT USA INC.
Reel/Frame 033949/0016 →
SECURITY INTEREST Recorded Mar 7, 2013
From: ALCATEL-LUCENT USA INC.
To: CREDIT SUISSE AG
Reel/Frame 030510/0627 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 11, 2006
From: BIJWAARD, DENNIS
To: LUCENT TECHNOLOGIES INC.
Reel/Frame 017908/0838 →
Continuity (1)
Related Publication 20080016191A1 · Jan 17, 2008