Media Relay Session Records for Uninterrupted IP Handoffs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional media relays reject IP streams during endpoint changes in mobile telephone systems, such as handoffs, due to unrecognized source IP addresses and ports, leading to disrupted voice over IP calls, and existing solutions like SIP messages add overhead and delay.
Innovation Solution
A method and apparatus for a media relay to maintain session information records and update source IP addresses and ports in IP transmissions based on matching identifiers, allowing uninterrupted forwarding of IP communications during endpoint changes by identifying and updating caller and callee ports and addresses within the media relay system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a conventional media relay uses strict source IP address and port validation, then security and authentication are improved, but IP transmission continuity is worsened during endpoint changes
Solution Approach 1:
The media relay dynamically updates its session information records with new source IP addresses and ports when endpoint changes occur, allowing the system to adapt to changing network conditions while maintaining authentication. The validation criteria are dynamically adjusted based on whether the new endpoint belongs to the same session.
Solution Approach 2:
The system changes the validation parameters from strict static IP address and port matching to dynamic matching based on session information. When an endpoint change is detected, the media relay updates the expected source IP and port in the session record, allowing continued authentication with new parameters.
2Loss of information
If SIP messages are used to notify IP address changes, then endpoint change notification is improved, but message overhead and transmission delay are worsened
Solution Approach 1:
The patent extracts the essential endpoint change notification function from the SIP signaling protocol and implements it directly within the media relay's session information records. The media relay proactively updates its records when endpoint changes occur, eliminating the need for separate SIP notification messages.
Solution Approach 2:
The media relay acts as an intermediary that autonomously detects and responds to endpoint changes by updating its session information records. This eliminates the need for endpoints to actively notify each other via SIP messages, reducing overhead and delay.
3Adaptability or versatility
If the media relay re-configures to accept new IP addresses during handoff, then adaptability to network changes is improved, but transmission interruption occurs
Solution Approach 1:
The media relay performs preliminary actions by maintaining session information records that persist across endpoint changes. When an endpoint change is detected, the media relay already has the necessary session context and can immediately update the record without interrupting active transmissions.
Solution Approach 2:
The system ensures continuity by updating session information records in-place without closing and reopening connections. The media relay continues forwarding packets using updated source IP and port information from the same session record, maintaining transmission continuity throughout the endpoint change process.
Data Source
AI summary
Facilitating uninterrupted transmission of internet protocol (IP) transmissions during endpoint changes is disclosed. When an IP transmission is received at a first relay port or a second relay port, a call record having the first relay port identifier or the second relay port identifier matching a destination port identifier in the IP transmission is located. When the destination port identifier matches the first relay port identifier of the record, a source IP address identifier and a source port identifier from the IP transmission are set as a first entity IP address identifier and first entity port identifier, respectively, of the record when the first entity IP address identifier and first entity port identifier do not match the source IP address identifier and source port identifier respectively and a received IP session identifier in the IP transmission matches the first entity session identifier. A similar procedure is followed to set a second entity IP address identifier and port identifier.


