IP Library Granted Patent US 6,931,005
Granted Patent B1
US 6,931,005 · App. 09/648,610 · Granted Aug 16, 2005

IP multicast services over ATM multicast

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,931,005
App. No.
09/648,610
Granted
Aug 16, 2005
Kind
B1
Abstract

A method and apparatus for reducing bandwidth usage in an ATM switching network by controlling bandwidth used for IP multicasting through the switching network. Bandwidth usage is controlled by modifying ingress and access modules, such as IP service gateways and access modules that terminate branches of a multicast tree. If a join request is received at an IP service gateway from a sink node served by an access module, the IP service gateway instructs the access module to graft a leaf to the branch to join the sink node to the tree and to merge the multicast packets with other IP packets for the sink node. Consequently, only one connection carrying the multicast traffic is required between the IP service gateway and the access module. Bandwidth usage in the ATM switching network is thereby controlled, and bandwidth usage in service access trunks connecting the access modules to the ATM switching network is reduced.

Claims (91)

1. A method of setting up a connection through an Asynchronous Transfer Mode (ATM) switching network between a sink node and a multicast tree, the multicast tree being coupled to the ATM switching network via an ingress node, and the sink node being coupled to the ATM switching network via an access module, the method comprising the steps of:

a) identifying the access module through which the sink node is coupled to the ATM switching network;

b) sending a message to the access module requesting that the sink node be connected to the multicast tree;

c) grafting a leaf to the multicast tree at the access module to connect the sink node to the multicast tree; and

d) merging multicast packets into an existing service connection for the sink node.

2. A method as claimed in claim 1 , wherein the step of identifying is performed by the ingress node, which is a service gateway to an Internet Protocol (IP) network and am associated multicast service access point.

3. A method as claimed in claim 2 , wherein the step of identifying comprises a step of examining a virtual channel (VC) on which a join request message was received from the sink node to identify the access module and the sink node.

4. A method as claimed in claim 3 , wherein the access module is one of a digital subscriber line access multiplexer (DSLAM); cable headend; wireless headend; satellite base station; ATM side of customer premise equipment; and optical line termination.

5. A method as claimed in claim 1 , wherein the step of merging the multicast packets into the existing service connection further comprises a step of performing a virtual channel (VC) merge, to merge the multicast packets with other IP packet traffic for the sink node.

6. A method as claimed in claim 5 , wherein the step of performing the VC merge is performed by the access module.

7. A method as claimed in claim 1 , wherein if the identified access module is not branched to the multicast tree, the method further comprises a step of connecting the access module to the multicast tree.

8. A method as claimed in claim 7 , wherein the step of connecting the access module to the multicast tree comprises steps of:

a) establishing a switched virtual circuit (SVC) connection between the access module and the ingress node through the ATM switching network, if required;

b) grafting a leaf to the multi-cast tree for the sink node; and

c) performing a VC merge, to merge the multicast packets with other IP packet traffic for the sink node.

9. A system for setting up a connection through an Asynchronous Transfer Mode (ATM) switching network between a sink node and a multicast tree, the multicast tree being coupled to the ATM switching network via an ingress node, and the sink node being coupled to the ATM switching network via a respective one of a plurality of access modules, the system comprising:

a) means for identifying an access module through which the sink node is coupled to the ATM switching network;

b) means for determining whether the identified access module is already part of the multicast tree;

c) means for grafting a leaf to the multicast tree at the identified access module when the identified access module is connected to the multicast tree; and

d) means for merging multicast packets with other IP traffic on an existing service channel for the sink node.

10. A system as claimed in claim 9 , wherein the ingress node is a Internet Protocol Service Gateway (IPS GWY).

11. A system as claimed in claim 10 , wherein the means for identifying the access module and the sink node comprises means for relating a virtual channel (VC) on which a join request is received from the sink node with an access module that supports the virtual channel.

12. A system as claimed in claim 9 , wherein the means for determining whether the identified access module is part of the multicast tree comprises:

a) a multicast session identifier sent from the ingress node to the access module, the multicast session identifier uniquely identifying the multicast session; and

b) means for using the multicast session identifier at the access module to determine whether multicast traffic associated with the multicast session identifier is being received at the access module.

13. A system as claimed in claim 10 , further comprising means for performing a VC merge at the access module.

14. A system as clawed in claim 9 , further comprising means for grafting a branch to the multicast tree from the ingress node to the access module, if the access module is not branched to the multicast tree.

15. A system as claimed in claim 14 , wherein the means for grafting the branch to the multicast tree at the access module comprises:

a) means for establishing a virtual circuit (VC) connection between the ingress node and the access module through the ATM switching network;

b) means for grafting the leaf to the branch of the multicast tree; and

c) means for performing a VC merge to merge multicast packets with other IP packets arriving for the sink node.

16. An Internet Protocol Service Gateway (IPS GWY) adapted to reduce duplication of multicast traffic through an Asynchronous Transfer Mode (ATM) switching network the IPS GWY comprising:

a) means for identifying an access module through which a sink node that requested a join to a multicast tree is coupled to the ATM switching network;

b) means for requesting the access module to join the sink node to the multicast tree; and

c) means for sag up a virtual connection to the access module to connect the access module to the multicast tree.

17. An IPS GWY as claimed in claim 16 , wherein the means for identifying the access module and the sink node comprises a table that relates a virtual channel (VC) on which a join request was received with a network address of the access module and the sink node.

18. An IPS GWY as claimed in claim 16 , wherein the means for requesting the access module to join the sink node to the multicast tree comprises means for formulating a signaling message to request the join and for sending the signaling message to the access module.

19. An IPS GWY as claimed in claim 16 wherein the IPS GWY controls an associated multicast service access point (multicast SAP) that supplies multicast packets to the access module.

20. An IPS GWY as claimed in claim 19 wherein the multicast SAP is co-located with the IPS GWY.

21. An IPS GWY as claimed in claim 19 wherein the multicast SAP is remote from the IPS GWY and controlled by at least one IPS GWY.

22. An access module for an Asynchronous Transfer Mode (ATM) switching network adapted to enable grafting of a connection between a sink node and a multicast tree, the access module being coupled to the ATM switching network and the sink node, the access module comprising means for grafting a leaf to the multicast tree to connect the sink node to the multicast tree, and the access module comprises any one of a digital subscriber line access multiplexer (DSLAM); cable headend; wireless headend; satellite base station; ATM side of customer premise equipment; and optical line termination.

23. An access module as claimed in claim 22 , wherein the means for grafting comprises:

a) means for receiving a signaling message from an ingress node through which the sink node internet protocol (EP) virtual circuit (VC) enters the ATM switching network, the signaling message requesting that the access module connect the sink node to the multicast tree; and

b) means for performing a virtual channel (VC) merge to merge the multicast packets with other IP traffic for the sink node.

24. An access module as claimed in claim 23 further comprising:

means for receiving a further signaling message from the ingress node, the further sing message instructing that the sink node be disconnected from the multicast tree.

25. An access module as claimed in claim 24 , further comprising means for disconnecting the sink node from the multicast tree and ending the VC merge.

26. An access module as claimed in claim 25 further comprising means for disconnecting from the multicast tree after all sink nodes are disconnected from the multicast tree.

27. A method of providing multicast service delivery to an end-user of ATM access services served by an access module connected to an asynchronous transfer mode (ATM) switching network, comprising steps of:

a) setting up a separate connection between an access module serving a plurality of the end-users and a gateway for delivering multicast packets from a source network, to permit the multicast packets to be transferred across the ATM switching network independently of any end-user virtual channel (VC) supported by the access module; and

b) merging the multicast packets with other Internet Protocol (IP) traffic on the end-user VC at the access module, to deliver the multicast packets to the end-user.

28. The method as claimed in claim 27 wherein the separate connection is used to provide the multicast service to each of the plurality of end-users who request to join the multicast session.

29. The method as claimed in claim 28 wherein the gateway instructs the access module to merge the multicast packets with the other IP traffic on the end-user VC.

30. The method as claimed in claim 29 wherein the gateway instructs the access module to end merging the multicast packets with the other IP traffic on the end-user VC when the gateway receives an indication on the end-user VC that the end-user wishes to disconnect from the multicast tree.

31. The method as claimed in claim 28 wherein the separate connection has an associated quality of service guarantee across the ATM switching network.

32. A method of setting up a connection through a connection-oriented network between a sink node and a multicast tree, the multicast tree being coupled to the connection-oriented network via an ingree node, and the sink node being coupled to the connection-oriented network via an access module, the method comprising the steps of:

a) identifying the access module through which the sink node is coupled to the connection-oriented network;

b) sending a message to the access module requesting that the sink node be connected to the multicast tree;

c) grafting a leaf to the multicast tree at the access module to connect the sink node to the multicast tree; and

d) merging multicast packets into an existing service connection for the sink node.

33. The method as claimed in claim 32 , wherein the step of identifying comprises a step of examining a virtual channel (VC) on which a join request message was received from the sink node to identify the access module and the sink node.

34. The method as claimed in claim 32 , wherein the step of merging the multicast packets into the existing service connection further comprises a step of performing a virtual channel (VC) merge, to merge the multicast packets with other IP packet traffic for the sink node.

35. The system for setting up a connection through connection oriented network between a sink node and a multicast tree, the multicast tree being coupled to the connection oriented network via an ingress node, and the sink node being coupled to the connection oriented network via a respective one of a plurality of access modules, the system comprising:

a) means for identifying an access module through which the sink node is coupled to the connection oriented network;

b) means for determining whether the identified access module is already part of the multicast tree;

c) means for grafting a leaf to the multicast tree at the indentified access module when the identified access module is connected to the multicast tree; and

d) means for merging multicast packets with other IP traffic on an existing service channel for the sink node.

36. The system as claimed in claim 35 , wherein the means for identifying the access module and the sink node comprises means for relating a virtual channel (VC) on which a join request is received from the sink node with an access module that supports the virtual channel.

37. The system as claimed in claim 35 , wherein the means for determining whether the identified access module is part of the multicast tree comprises:

a) a multicast session identifier sent from the ingress node to the access module, the multicast session identifier uniquely identifying the multicast session; and

b) means for using the multicast session identifier at the access module to determine whether multicast traffic associated with the multicast session identifier is being received at the access module.

38. The system as claimed in claim 35 , further comprising means for performing a VC merge at the access module.

39. The system as claimed in claim 35 , further comprising means for grafting a branch to the multicast tree from the ingree node to the access module, if the access module is not branched to the multicast tree.

40. An Internet Protocol Service Gateway (IPS GWY) adapted to reduce duplication of multicast traffic through a connection oriented network, the IPS GWY comprising:

a) means for identifying an access module through which a sink node that requested a join to a multicast tree is coupled to the connection oriented network;

b) means for requesting the access module to join the sink node to the multicast tree; and

c) means for setting up a virtual connection to the access module to connect the access module to the multicast tree.

41. The IPS GWY as claimed in claim 40 , wherein the means for identifying the access module and the sink node comprises a table that relates a virtual channel (VC) on which a join request was received with a network address of the access module and the sink node.

42. The IPS GWY as claimed in claim 40 , wherein the means for requesting the access module to join the sink node to the multicast tree comprises means for formulating a signaling message to request the join and for sending the signaling message to the access module.

43. The IPS GWY as claimed in claim 40 , wherein the IPS GWY controls an associated multicast service access point (multicast SAP) that supplies multicast packets to the access module.

44. An access module for a connection oriented network adapted to enable grafting of a connection between a sink node and a multicast tree, the access module being coupled to the connection oriented network and the sink node, the access module comprising means for grafting a leaf to the multicast tree to connect the sink node to the multicast tree, and the access module comprises any one of a digital subscriber line access multiplexer (DSLAM); cable headend; wireless headend; satellite base station; network side of customer premise equipment; and optical line termination.

45. The access module as claimed in claim 44 , wherein the means for grafting comprises:

a) means for receiving a signaling message from an ingress node through which the sink node internet protocol (IP) virtual circuit (VC) enters the connection oriented network, the signaling message requesting that the access module connect the sink node to the multicast tree; and

b) means for performing a virtual channel (VC) merge to merge the multicast packets with other IP traffic for the sink node.

46. A method of providing multicast service delivery to an end-user of connection oriented access services served by an access module connected to a connection oriented network, comprising steps of:

a) setting up a separate connection between an access module serving a plurality of the end-users and a gateway for delivering multicast packets from a source network, to permit the multicast packets to be transferred across the connection oriented network independently of any end-user virtual channel (VC) supported by the access module; and

b) merging the multicast packets with other Internet Protocol (IP) traffic on the end-user VC at the access module, to deliver the multicast packets to the end-user.

47. The method as claimed in claim 46 wherein the separate connection is used to provide the multicast service to each of the plurality of end-users who request to join the multicast session.

48. The method as claimed in claim 47 wherein the gateway instructs the access module to merge the multicast packets with the other IP traffic on the end-user VC.

49. The method as claimed in claim 48 wherein the gateway instructs the access module to end merging the multicast packets with the other IP traffic on the end-user VC when the gateway receives an indication on the end-user VC that the end-user wishes to disconnect from the multicast tree.

50. The method as claimed in claim 47 wherein the separate connection has an associated quality of service guarantee across the connection oriented network.

Assignments (16)
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 61087/0386) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063690/0359 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; HYPERQUALITY, INC.; HYPERQUALITY II, LLC; CAAS TECHNOLOGIES, LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 063779/0622 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 53955/0436) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063705/0023 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026 Recorded Apr 26, 2023
From: CITIBANK, N.A., AS COLLATERAL AGENT
To: AVAYA HOLDINGS CORP.; AVAYA INC.; AVAYA MANAGEMENT L.P.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063457/0001 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Aug 5, 2022
From: AVAYA INC.; INTELLISIST, INC.; AVAYA MANAGEMENT L.P.; AVAYA CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 061087/0386 →
SECURITY INTEREST Recorded Sep 25, 2020
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 053955/0436 →
SECURITY INTEREST Recorded Jan 23, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 045124/0026 →
RELEASE OF SECURITY INTEREST Recorded Jan 11, 2018
From: CITICORP USA, INC.
To: AVAYA, INC.; SIERRA HOLDINGS CORP.
Reel/Frame 045045/0564 →
SECURITY INTEREST Recorded Jan 10, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 045034/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001 Recorded Dec 15, 2017
From: CITIBANK, N.A.
To: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION); VPNET TECHNOLOGIES, INC.
Reel/Frame 044893/0531 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 023892/0500 Recorded Dec 15, 2017
From: CITIBANK, N.A.
To: AVAYA INC.
Reel/Frame 044891/0564 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 025863/0535 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST, NA
To: AVAYA INC.
Reel/Frame 044892/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 030083/0639 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 045012/0666 →
SECURITY INTEREST Recorded Jan 27, 2017
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS CORPORATION; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 041576/0001 →
SECURITY AGREEMENT Recorded Feb 5, 2010
From: AVAYA INC.
To: CITICORP USA, INC., AS ADMINISTRATIVE AGENT
Reel/Frame 023905/0001 →
SECURITY AGREEMENT Recorded Feb 4, 2010
From: AVAYA INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 023892/0500 →