Communication Protocol Interoperability via Asynchronous Capability Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The interoperability between session initiation protocol (SIP) and H.323 protocols is challenging due to differences in feature negotiation and information flow, leading to deadlocks when endpoints wait for each other to transmit capabilities.
Innovation Solution
A method and system that initiate a timer to receive capabilities from endpoints, allowing for the establishment of communication sessions using common capabilities, and optionally creating intermediate sessions via a transcoder to prevent deadlocks and ensure communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If endpoints use different communication protocols (SIP and H.323) with independent feature negotiation, then protocol-specific functionality is maintained, but interoperability fails due to deadlocks when endpoints wait for each other to transmit capabilities
Solution Approach 1:
The gateway acts as an intermediary between SIP and H.323 endpoints, translating capability negotiation messages between the two protocols. When a SIP endpoint and H.323 endpoint attempt to establish a session, the gateway receives capability requests from one protocol, translates them into the other protocol's format, and forwards them to the appropriate endpoint, thereby preventing deadlocks and enabling interoperability
Solution Approach 2:
The system changes the parameter of capability transmission timing by implementing asymmetric negotiation where one endpoint transmits capabilities first based on protocol-specific rules. The gateway modifies the negotiation sequence by sending capabilities proactively rather than waiting for reciprocal transmission, resolving the deadlock condition where both endpoints wait for the other
2Loss of information
If endpoints wait for each other to transmit capabilities before establishing communication, then complete capability information is available for session setup, but communication establishment is delayed or blocked due to mutual waiting
Solution Approach 1:
The gateway performs preliminary capability transmission by sending capability information proactively before the reciprocal waiting condition occurs. Instead of both endpoints waiting for each other, the gateway pre-transmits capabilities on behalf of one endpoint, ensuring capability information is available while eliminating the mutual waiting delay
3Adaptability or versatility
If a gateway attempts to map information flows between SIP and H.323 protocols, then protocol interoperability is enabled, but complexity increases due to differences in timing and content of information flow
Solution Approach 1:
The gateway segments the protocol mapping function into distinct modules handling specific message types and negotiation phases separately. By dividing the complex information flow mapping into manageable segments for different protocol elements, the gateway reduces overall complexity while maintaining comprehensive interoperability support
Data Source
Figure 1~2
Figure 3
AI summary
A method for providing communication ' protocol interoperability may include receiving a request from a first endpoint to establish a communication session with a second endpoint, the request uses a first communication protocol. The method also includes receiving a first response from the second endpoint, the first response uses a second communication protocol different than the first communication protocol. The method may also include initiating a timer for receiving a set of capabilities from the second endpoint and establishing the communication session between the first endpoint and the second endpoint.