Media Gateway RTP Multiplexing Adaptation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Media gateways face difficulties in communicating RTP multiplexed packets across various networks and interfaces, such as femtocell, UMTS, IMS core, and wireline networks, due to unsupported or undefined RTP multiplexing configurations.
Innovation Solution
A media gateway system that supports multiple RTP multiplexing enablement methods, including per IP interface type, global RTCP negotiation, and per IP realm methods, by using a media gateway controller to determine the appropriate multiplexing approach based on interface types and configuration data, and exchanging RTCP Application packets to negotiate and enable RTP multiplexing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If RTP multiplexing is enabled to reduce bandwidth overhead, then bandwidth efficiency is improved, but compatibility with networks that do not support RTP multiplexing deteriorates
Solution Approach 1:
The media gateway dynamically adapts its RTP multiplexing behavior based on the capabilities of the peer network. It can switch between multiplexed and non-multiplexed modes depending on whether the remote network supports RTP multiplexing, allowing optimal bandwidth utilization while maintaining compatibility across different network types.
Solution Approach 2:
The system changes the multiplexing parameter (enabled/disabled) based on network detection results. When a network is detected to not support RTP multiplexing, the gateway changes the multiplexing parameter from enabled to disabled for that specific connection, thereby maintaining compatibility while preserving bandwidth efficiency on supported networks.
2Device complexity
If a single RTP multiplexing method is implemented, then system complexity is reduced, but adaptability to different network types deteriorates
Solution Approach 1:
The media gateway segments its RTP multiplexing implementation into multiple independent methods (RTCP Application packet negotiation method and IP realm identifier method). Each method can be independently selected and executed based on the specific network type, allowing the system to handle diverse network interfaces without increasing overall complexity.
Solution Approach 2:
The gateway implements a universal multi-method framework that can handle multiple network types (GSM, UMTS, femtocell, wireline, etc.) through different RTP multiplexing approaches. This multi-functional design allows a single gateway to adapt to various network interfaces while maintaining a unified control architecture.
Data Source
AI summary
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.