Anchoring Network Device Codec Interoperation via Request Modification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current telecommunications systems face limitations in enabling communication between devices with different media capabilities, such as codecs, leading to restricted communication due to the inability to transcode or select compatible codecs, resulting in potential loss of audio quality and increased network overhead.
Innovation Solution
An anchoring network device modifies the initiation request to include EVS ChAw mode as a preferred codec, allowing communication even if the originating terminal does not support it, and a network gateway transcodes between EVS ChAw and the originating terminal's codec, maintaining audio quality and reducing network overhead.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional codec selection methods are used where only codecs supported by both terminals are selected, then device compatibility is maintained, but communication versatility and audio quality are restricted
Solution Approach 1:
The network device acts as an intermediary that modifies initiation requests to include EVS ChAw mode codec offerings. When a calling terminal initiates a session, the network device intercepts the request, adds the EVS ChAw mode codec to the codec list, and forwards the modified request to the called terminal, enabling advanced codec usage without requiring the calling terminal to natively support it
Solution Approach 2:
The network device performs preliminary modification of the initiation request before the session is established, adding the EVS ChAw mode codec to the offered codecs list. This preliminary action allows the called terminal to select and use the advanced codec without the calling terminal needing to have been pre-configured with support for it
2Adaptability or versatility
If transcoding is performed between different codecs to enable interoperation, then communication between incompatible devices is enabled, but computational cost and processing time increase
Solution Approach 1:
The network device serves as a mediator that enables codec interoperability through request modification rather than traditional transcoding. By adding EVS ChAw mode to the offered codecs in the initiation request, it allows direct communication between terminals using different codec capabilities without requiring real-time transcoding operations
Solution Approach 2:
The system changes the codec parameters offered in the session initiation by adding EVS ChAw mode to the codec list. This parameter modification at the signaling level enables advanced audio quality without requiring actual parameter transformation or transcoding of the audio streams themselves
3Manufacturing precision
If advanced codecs like EVS ChAw mode are强制 imposed on terminals that do not support them, then audio quality improves, but device compatibility and session establishment fail
Solution Approach 1:
The network device acts as a mediator that intelligently modifies the initiation request to include EVS ChAw mode in the offered codecs list. This allows the called terminal to select the advanced codec if it supports it, maintaining session establishment reliability while enabling improved audio quality when compatible
Solution Approach 2:
The system dynamically adjusts the offered codecs based on the called terminal's capabilities. The network device adds EVS ChAw mode to the initiation request, and the called terminal autonomously selects from the offered codecs based on its own support, creating a dynamic adaptation that ensures both compatibility and quality
Data Source
AI summary
An anchoring network device of a telecommunications network can receive a first initiation request of a communication session and determine a second request indicating a different media capability than the first request. A network gateway can modify packets of the session, e.g., by transcoding between the capabilities. In some examples, the anchoring device can determine that a codec list of the initiation request corresponds to a rewrite rule. The device can apply the rewrite rule to the request to provide a second request listing a second, different codec. In some examples, the anchoring device can determine if there is a common media capability between the first initiation request and a predetermined exclusion list. If not, the second request can include at least one capability not in the first request, e.g., an Enhanced Voice Services (EVS) Channel-Aware-mode (ChAw) codec.