SIP Message Payload Compression via Application Layer Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for compressing Session Initiation Protocol (SIP) messages, such as SIGCOMP, are limited by memory constraints in user terminals and require updates on both client and server sides, and are not widely deployed, leading to issues with legacy equipment that cannot support the latest protocols, resulting in large messages being transported uncompressed.
Innovation Solution
Compressing and decompressing SIP NOTIFY message payloads at the application layer using a well-known algorithm like gzip, allowing user terminals to indicate support for payload compression in message headers, enabling compression even with legacy terminals without requiring SIGCOMP compatibility, and ensuring headers remain uncompressed for routing through intermediate nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If SIGCOMP compression is used for SIP messages, then message size is reduced, but memory constraints in user terminals and requirement for updates on both client and server sides limit deployment
Solution Approach 1:
The patent segments the compression functionality from the SIP User Agent into a separate application layer component. This allows the compression algorithm to be implemented independently using well-known algorithms like gzip, eliminating the need for complex SIGCOMP protocol implementation and updates in the SIP UA itself. The segmentation enables legacy terminals to support compression through application layer modifications without requiring SIP protocol changes.
Solution Approach 2:
The patent introduces an intermediary application layer between the SIP UA and the network. This intermediary handles the compression and decompression of message payloads, acting as a mediator that translates between compressed and uncompressed formats. The intermediary uses standard compression algorithms that are widely available, avoiding the need for specialized SIGCOMP implementation while still achieving message size reduction.
2Quantity of substance
If compression is implemented in SIP User Agents, then message compression is achieved, but compatibility with legacy equipment is lost
Solution Approach 1:
By segmenting the compression functionality into a separate application layer component rather than integrating it into the SIP User Agent, the patent enables optional compression support. Legacy terminals that do not have the application layer modification can still communicate using uncompressed messages, while newer terminals with the application layer can compress messages. This segmentation preserves backward compatibility while enabling compression where supported.
Solution Approach 2:
The patent changes the implementation approach from protocol-level compression (SIGCOMP) to application-layer compression using standard algorithms. This parameter change in the compression strategy allows the use of widely available algorithms like gzip that can be implemented as optional libraries, enabling legacy equipment to continue operating with uncompressed messages while newer equipment can utilize compression when the application layer indicates support.
3Adaptability or versatility
If large SIP messages are sent uncompressed, then legacy terminal compatibility is maintained, but network load and latency increase
Solution Approach 1:
The patent changes the compression parameter from protocol-specific (SIGCOMP) to standard algorithm-based (gzip, deflate, etc.). This allows the compression to be implemented as an optional application layer feature rather than a mandatory protocol requirement. The application layer can indicate compression support in message headers, allowing the network to efficiently handle compressed messages when both endpoints support it, while maintaining compatibility with legacy terminals that use uncompressed messages.
Data Source
Figure 1
Figure 2~3
AI summary
A method of transporting Session Initiation Protocol messages across an IP Multimedia network between a user terminal (1) and a Session Initiation Protocol Application Server (2). The method comprising compressing message payloads within the application layer (4a, 5a) at the sending side and decompressing them at the application layer (4b, 5b) on the receiving side, compressed message payloads being passed between the application layer and a Session Initiation Protocol User Agent (3a) via an appropriate Application Programming Interface (7a).