Network Node SDP Payload Mapping for Codec Collision Avoidance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In communication networks, the limited payload type number space for codecs can lead to codec collisions when connecting communication sessions, especially with the introduction of new codecs and the involvement of multiple intermediate network nodes.
Innovation Solution
A network node initiates an SDP exchange by requesting and receiving mappings of payload type numbers to codecs, selecting a suggested mapping to avoid conflicts, and proposing this mapping to entities, ensuring compatible codec usage across all involved nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the limited payload type number space (96-127) is used for dynamic mapping, then codec compatibility can be negotiated, but the risk of codec collision increases considerably
Solution Approach 1:
The patent applies preliminary action by requesting and receiving mappings of payload type numbers to codecs from all intermediate network nodes before establishing the communication session. This allows the network node to proactively identify and avoid collisions by selecting a suitable mapping in advance, rather than dealing with conflicts after they occur.
Solution Approach 2:
The network node acts as an intermediary between the two communication sessions, collecting mapping information from all intermediate nodes, selecting a collision-free payload type number mapping, and proposing it to the entities. This mediator role resolves the contradiction by coordinating the limited payload type space across multiple sessions to prevent collisions while maintaining codec compatibility.
2Adaptability or versatility
If multiple intermediate network nodes are involved in connecting communication sessions, then session connectivity is improved, but the chance of codec collision increases
Solution Approach 1:
The patent requests mapping information from all intermediate network nodes before establishing the session connection. This preliminary collection of mapping data from every node in the path allows the system to identify potential collisions in advance and select a safe mapping, enabling multiple intermediaries to be involved without increasing collision risk.
Solution Approach 2:
The network node receives feedback from each intermediate network node about their payload type number mappings, uses this feedback to select a collision-free mapping, and proposes the selected mapping back to the entities. This feedback loop ensures that the presence of multiple intermediate nodes does not increase collision probability, as each node's constraints are taken into account.
Data Source
AI summary
A method performed by a network node for handling a communication session in a communication network using a session description protocol, SDP, for communication sessions is provided. The network node sends, on one or both established communication sessions, a request with an indication. The indication indicates a request of one or more mappings of a payload type number to a codec associated to the communication session. The network node receives a response including one or more response indications. A response indication indicates one or more mappings of a payload type number to a codec associated to the communication session. The network node further sends a request indication indicating a mapping of a payload type number to a codec suggested to use in an offer message generated by the at least one entity. The mapping is selected based on the one or more response indications in the received response.