Providing a capability list of a predefined format in a communications network

• US 8,027,265 B2
• Filed: 10/30/2006
• Issued: 09/27/2011
• Est. Priority Date: 03/19/2004
• Status: Active Grant

• Current Assignee: Ribbon Communications Operating Company, Inc. (Ribbon Communications, Inc.)
• Original Assignee: Genband US LLC (Ribbon Communications, Inc.)
• Inventors: Chu, Chung Cheung, Rabipour, Rafi
• Primary Examiner(s): Kizou; Hassan
• Assistant Examiner(s): Jiang; Charles C
• Application Number:
  US11/589,435
• Publication Number:
  US 20070104114A1
• Time in Patent Office: 1,793 Days
• Field of Search: 370/241, 370/252, 714/100, 714/1, 714/2, 714/3, 714/4, 455130-355, 455/403, 455/414.1, 375/224, 375/227, 375/242, 375/254, 379 101- 35
• US Class Current: 370/252
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/344 Out-of-band transfers

Abstract

In a communications network having plural nodes, a first node receives a capability list that has a predefined format and includes plural entries identifying corresponding data processing functions supported by one or more nodes along a communications path of a communications session involving the first node. The first node adds at least one additional entry into the capability list in response to determining that the first node supports a data processing function that is not identified in the capability list.

Claims

1. A method for use in a communications network having plural nodes, comprising:

receiving, by a first node, a capability list that has a predefined format and includes plural entries identifying corresponding data processing functions supported by one or more other nodes along a communications path of a communications session involving the first node;

the first node adding at least one additional entry into the capability list in response to determining that the first node supports a data processing function that is not identified in the capability list; and

wherein the capability list includes entries relating to at least two of the following data processing functions;

traffic data encoding and decoding, noise reduction, acoustic echo control, echo cancellation, and automatic level control.

2. The method of claim 1, further comprising:

the first node performing load balancing of data processing functions among nodes in the communications path.

3. The method of claim 2, wherein performing load balancing comprises

relocating a particular data processing function applied to traffic in the communications path from the first node to another node in the communications path.

4. The method of claim 1, wherein the received capability list is a forward capability list communicated along a direction of first traffic flow in the communications session, the method further comprising:

receiving, by the first node, a reverse capability list that has the predefined format, the reverse capability list communicated in a direction opposite to the direction of the first traffic flow.

5. The method of claim 4, wherein the communications session further includes a second traffic flow that is opposite in direction to the first traffic flow, the method further comprising:

receiving, by the first node, forward and reverse capability lists that have the predefined format for the second traffic flow.

6. The method of claim 4, further comprising:

the first node determining whether the first node is to be the node to provide a particular data processing function among nodes in the communications path based on the forward and reverse capability lists, wherein the determining is part of position-dependent activation of the particular data processing function among the nodes in the communications path.

7. The method of claim 1, wherein receiving the capability list comprises receiving the capability list in an in-band message of the communications path.

8. The method of claim 1, wherein receiving the capability list comprises receiving the capability list in an out-of-band message with respect to the communications path.

9. The method of claim 1, wherein receiving the capability list comprises receiving the capability list embedded in a payload of a message to allow for communication of the capability list across different types of transports in the communications path.

10. The method of claim 1, further comprising requesting, by the first node, re-transmission of a capability list by a second node in the communications path in response to capability list communication failure.

11. The method of claim 1, wherein receiving the capability list is responsive to one of plural triggering events, the plural triggering events including at least some of:

setup of a communications session;

update of a data processing function in a node;

a heartbeat event;

change in a topology of the communications session; and

insertion of a node into the communications path.

12. The method of claim 1 wherein the first node comprises a first media gateway and where the capability list is transmitted to the first node by a second media gateway.

22. The article of claim 1, wherein the instructions when executed cause the first node to receive the first capability list as part of a payload in a message communicated along the communications path, wherein the first capability list has been communicated through plural different types of transports of the communications path.

13. A node comprising:

a first termination point and a second termination point;

a processor; and

a coordination module executable on the processor to;

receive, at the first termination point, a first capability list containing entries identifying data processing functions supported by certain nodes in a communications path of a communications session in which the node is involved;

determine whether the received first capability list is different from a previously received capability list at the first termination point;

in response to determining that the received first capability list is different from the previously received capability list, send a second capability list previously received from the second termination point, where the second capability list is sent from the first termination point; and

wherein at least one of the received first capability list, the previously received capability list, and the second capability list includes entries for at least two of the following data processing functions;

traffic data encoding and decoding, noise reduction, acoustic echo control, echo cancellation, and automatic level control.

14. The node of claim 13, wherein the coordination module is executable to further:

in response to determining that the received first capability list is different from the previously received capability list, update the first capability list and send the updated first capability list out through the second termination point.

15. The node of claim 14, wherein the coordination module is executable to further:

in response to determining that the received first capability list is identical to the previously received capability list, perform an action to not send out any capability list from the first termination point and the second termination point.

16. The node of claim 13, wherein each of the capability lists has a predefined format and plural entries to identify corresponding data processing functions supported by certain nodes in the communications path.

17. The node of claim 13, wherein the second capability list contains entries identifying data processing functions supported by nodes in the communications path of the communications session in which the node is involved.

18. The node of claim 13 wherein the coordination module receives the first capability list from a first media gateway and wherein the node comprises a second media gateway.

19. An article comprising at least one non-transitory computer readable medium that contains instructions that when executed cause a first node to:

receive a capability list that has a predefined format and includes plural entries identifying corresponding data processing functions supported by one or more other nodes along a communications path of a communications session involving the first node;

add at least one additional entry into the capability list in response to determining that the first node supports a data processing function that is not identified in the capability list; and

wherein the capability list includes entries relating to at least two of the following data processing functions;

traffic data encoding and decoding, noise reduction, acoustic echo control, echo cancellation, and automatic level control.

20. The article of claim 19, wherein the instructions when executed cause the first node to send a pair of capability lists in different directions of the communications path in response to at least one of:

setup of the communications session;

update of a data processing function in the first node;

a heartbeat event; and

insertion of the first node into the communications path.

21. The article of claim 19, wherein the instructions when executed cause the first node to send a pair of capability lists in different directions of the communications path in response to expiration of a predefined time interval.

23. The article of claim 19 wherein the first node comprises a first media gateway and wherein the capability list is transmitted to the first node by a second media gateway.