Methods, systems and computer readable media for supporting a plurality of real-time transport protocol (RTP) multiplexing enablement methods in a media gateway

• US 8,971,311 B2
• Filed: 12/01/2010
• Issued: 03/03/2015
• Est. Priority Date: 09/23/2010
• Status: Active Grant

• Current Assignee: Ribbon Communications Operating Company, Inc. (Ribbon Communications, Inc.)
• Original Assignee: Genband US LLC (Ribbon Communications, Inc.)
• Inventors: Bianconi, Richard J.
• Primary Examiner(s): Jagannathan, Melanie
• Assistant Examiner(s): Ansari, Najeebuddin
• Application Number:
  US12/958,270
• Publication Number:
  US 20120076131A1
• Time in Patent Office: 1,553 Days
• Field of Search: 370351-356, 370/392, 370/401, 370/465, 370/252, 370/466, 370/235, 370/236
• US Class Current: 370/352
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/65 Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04L 65/70 Media network packetisation
• CPC Class Codes: H04L 65/765 intermediate
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC

Abstract

Methods, systems, and computer readable media for supporting a plurality of RTP multiplexing enablement methods in a media gateway are disclosed. According to one aspect, a system includes a media gateway controller configured to receive a signaling message to establish a call from a peer node in a first network, an a media gateway configured to perform a first and second RTP multiplexing enablement process on the media portion of the call, wherein the first RTP multiplexing enablement process includes sending a real-time transport control protocol (RTCP) Application packet to the peer node, refraining from performing RTP multiplexing on packets sent to the peer node until a reply RTCP Application packet is received from the peer node, and receiving RTP multiplexed packets from the peer node, and wherein the second RTP multiplexing enablement process includes obtaining an Internet protocol (IP) realm identifier that identifies the first network, accessing configuration data in the media gateway using the IP realm identifier to determine a predefined multiplexing enablement action for packets destined for the first network, and executing the determined predefined multiplexing enablement action on packets sent to the peer node in the first network.

Claims

1. A system for enabling real-time transport protocol (RTP) multiplexing in a media gateway, the system comprising:

a media gateway controller configured to receive a signaling message to establish a call from a peer node in a first network and to determine, if possible, an interface type used by the peer node to communicate a media portion of the call and to transmit a call control message that includes the interface type to a media gateway; and

the media gateway comprising an Internet protocol (IP) realm database and configured to perform a first and second RTP multiplexing enablement process on the media portion of the call where determining the interface type is not possible;

wherein the first RTP multiplexing enablement process includes sending a real-time transport control protocol (RTCP) Application packet to the peer node, refraining from performing RTP multiplexing on packets sent to the peer node until a reply RTCP Application packet is received from the peer node, and receiving RTP multiplexed packets from the peer node; and

wherein the second RTP multiplexing enablement process includes obtaining an IP realm identifier that identifies the first network, accessing the IP realm database using the IP realm identifier to determine a predefined multiplexing enablement action for packets destined for the first network, and executing the determined predefined multiplexing enablement action on packets sent to the peer node in the first network.

2. The system of claim 1 wherein the media gateway is further configured to receive the call control message from the media gateway controller and to perform a third RTP multiplexing enablement process that includes performing a negotiation procedure if the interface type is either an Nb interface or an AoIP interface.

3. The system of claim 1 wherein determining the IP realm identifier includes at least one of receiving the IP realm identifier from the media gateway controller in an H.248 ADD command message or using a default IP realm identifier stored in media gateway configuration data.

4. The system of claim 3 wherein the configuration data is either stored locally within the media gateway or in a network node communicatively connected to the media gateway.

5. The system of claim 1 wherein the media gateway controller is configured to send via out-of-band signaling, to the peer node, UDP multiplexing port information associated with the media gateway after determining that the interface type is an Iuh interface type.

6. The system of claim 1 wherein the predefined multiplexing enablement action is negotiated, non-negotiated, or disabled.

7. The system of claim 1 wherein the first RTP multiplexing process includes receiving the reply RTCP Application packet from the peer node, wherein the peer node is 3GPP 29.414 compliant.

8. The system of claim 1 wherein the first RTP multiplexing process includes receiving RTP multiplexed packets from the peer node that ignores the RTCP Application packet sent from the media gateway, wherein the peer node is 3GPP 25.444 compliant and receives UDP multiplexing port information associated with the media gateway from a signaling message from the media gateway.

9. The system of claim 1 wherein the peer node includes at least one of a media gateway, an IP-based GSM base station controller, a media resource function processor (MRFP), border gateway function (BGF), or a femtocell.

10. The system of claim 2 wherein the interface type includes an AoIP interface, an IuCS Over IP interface, an Iuh interface, an Nb interface, and an Mb interface.

11. A method for enabling real-time transport protocol (RTP) multiplexing in a media gateway, the method comprising:

receiving, at a media gateway controller, a signaling message to establish a call from a peer node in a first network;

determining, at the media gateway controller, if possible, an interface type used by the peer node to communicate a media portion of the call;

transmitting, by the media gateway controller to a media gateway comprising an Internet protocol (IP) realm database, a call control message that includes the interface type;

performing, at the media gateway, at least one of a first and second RTP multiplexing enablement process on a media portion of the call where determining the interface type is not possible;

wherein the first RTP multiplexing enablement process includes sending an real-time transport control protocol (RTCP) Application packet to the peer node, refraining from performing RTP multiplexing on packets sent to the peer node until a reply RTCP Application packet is received from the peer node, and receiving RTP multiplexed packets from the peer node; and

wherein the second RTP multiplexing enablement process includes obtaining an IP realm identifier that identifies the first network, accessing the IP realm database using the IP realm identifier to determine a predefined multiplexing enablement action for packets destined for the first network, and executing the determined predefined multiplexing enablement action on packets sent to the peer node in the first network.

12. The method of claim 11 wherein the media gateway is further configured to to receive the call control message from the media gateway controller and to perform a third RTP multiplexing enablement process that includes performing a negotiation procedure if the interface type is either an Nb interface or an AoIP interface.

13. The method of claim 11 wherein determining the IP realm identifier includes at least one of receiving the IP realm identifier from the media gateway controller in an H.248 ADD command message or using a default IP realm identifier stored in media gateway configuration data.

14. The method of claim 13 wherein the configuration data is either stored locally within the media gateway or in a network node communicatively connected to the media gateway.

15. The method of claim 11 wherein the media gateway controller is configured to send via out-of-band signaling, to the peer node, UDP multiplexing port information associated with the media gateway after determining that the interface type is an Iuh interface type.

16. The method of claim 11 wherein the predefined multiplexing enablement action is negotiated, non-negotiated, or disabled.

17. The method of claim 11 wherein the first RTP multiplexing process includes receiving the reply RTCP Application packet from the peer node, wherein the peer node is 3GPP 29.414 compliant.

18. The method of claim 11 wherein the first RTP multiplexing process includes receiving RTP multiplexed packets from the peer node that ignores the RTCP Application packet sent from the media gateway, wherein the peer node is 3GPP 25.444 compliant and receives UDP multiplexing port information associated with the media gateway from a signaling message from the media gateway.

19. The method of claim 11 wherein the peer node includes at least one of a media gateway, an IP-based GSM base station controller, a media resource function processor (MRFP), border gateway function (BGF), or a femtocell.

20. The method of claim 11 wherein the interface type includes an AoIP interface, an IuCS Over IP interface, an Iuh interface, an Nb interface, and an Mb interface.

21. A non-transitory computer readable medium having stored thereon executable instructions that when executed by the processor of a computer control the computer to perform steps comprising:

receiving, at a media gateway controller, a signaling message to establish a call from a peer node in a first network;

determining, at the media gateway controller, if possible, an interface type used by the peer node to communicate a media portion of the call;

transmitting, by the media gateway controller to a media gateway comprising an Internet protocol (IP) realm database, a call control message that includes the interface type;

performing, at the media gateway, at least one of a first and second RTP multiplexing enablement process on a media portion of the call where determining the interface type is not possible;

wherein the first RTP multiplexing enablement process includes sending an real-time transport control protocol (RTCP) Application packet to the peer node, refraining from performing RTP multiplexing on packets sent to the peer node until a reply RTCP Application packet is received from the peer node, and receiving RTP multiplexed packets from the peer node; and

wherein the second RTP multiplexing enablement process includes obtaining an IP realm identifier that identifies the first network, accessing the IP realm database using the IP realm identifier to determine a predefined multiplexing enablement action for packets destined for the first network, and executing the determined predefined multiplexing enablement action on packets sent to the peer node in the first network.

22. The computer readable medium of claim 21 wherein the media gateway is further configured to receive the call control message from the media gateway controller and to perform a third RTP multiplexing enablement process that includes performing a negotiation procedure if the interface type is either an Nb interface or an AoIP interface.