Page-mode Messaging via MSRP Intermediary
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The SIP MESSAGE method for page-mode messaging is inefficient for large messages, as it can cause SIP signaling blockage and performance degradation in SIP networks, especially when using TCP transport, and is not feasible for large size messages due to fragmentation and congestion control issues.
Innovation Solution
Implementing a method that determines if a session-mode message is a page-mode message and treating it as such, using the MSRP mechanism with a page-mode indicator, allowing page-mode messages to be received and stored even when transmitted as session-mode messages, thereby avoiding SIP signaling blockage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If SIP MESSAGE method is used for large messages, then page-mode messaging is achieved, but SIP signaling is blocked and network performance deteriorates
Solution Approach 1:
The patent introduces an intermediary mechanism where the SIP MESSAGE method acts as a mediator between the messaging application and the transport network. This intermediary allows large messages to be transmitted through a dedicated channel that does not interfere with regular SIP signaling, thus resolving the conflict between maintaining page-mode messaging capability and preserving signaling throughput.
Solution Approach 2:
The patent segments the message transmission process into two independent parts: SIP signaling for session control and MSRP for actual message delivery. By separating these functions, large messages can be transmitted without blocking SIP signaling, as each operates through its own dedicated pathway.
2Reliability
If TCP transport is used for large messages, then reliable delivery is achieved, but congestion control issues arise and signaling is blocked
Solution Approach 1:
MSRP serves as an intermediary protocol between the messaging application and the transport layer. It provides reliable message delivery through its own mechanisms while acting as a mediator that does not interfere with SIP signaling, thus maintaining both reliability and signaling performance.
Solution Approach 2:
The patent segments the transport function by using MSRP for message delivery instead of direct TCP for SIP MESSAGE. This segmentation allows reliable delivery through MSRP's mechanisms while keeping SIP signaling separate and uninterrupted.
3Productivity
If UDP is used for large messages, then signaling is not blocked, but packet fragmentation occurs and order is not guaranteed
Solution Approach 1:
MSRP acts as an intermediary that sits between the application layer and the transport layer. It provides reliable message delivery through its own protocols while allowing UDP to be used for transport, thus maintaining high signaling throughput while ensuring message reliability through MSRP's mechanisms rather than relying on UDP's fragmented packets.
4Ease of operation
If large page-mode messages are transmitted through SIP proxies, then messaging is achieved, but proxy performance decreases severely
Solution Approach 1:
The patent introduces MSRP as an intermediary protocol that handles large message transmission independently of SIP proxies. This allows messaging functionality to be maintained while reducing the processing burden on SIP proxies, as MSRP manages the heavy lifting of large message transmission without requiring extensive proxy intervention.
Solution Approach 2:
The patent segments the messaging function from the signaling function. MSRP handles the actual message transmission separately from SIP signaling, which reduces the load on SIP proxies and allows them to focus on signaling tasks without being overwhelmed by large message handling.
Data Source
Figure 1~2
Figure 3~4
Figure 5A~5B
AI summary
A way to provide page-mode messaging is to send a message using a session-mode messaging mechanism with an indication indicating that the session-mode is for a pager-type message. In response to said indication, a receiver treats the message as a page-mode message although it was received in the session-mode.