SIP Header Modification via Application Policy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Session Initiation Protocol (SIP) messages in IMS networks are verbose, leading to excessive data transmission and resource usage due to unnecessary optional and routing headers, which are often discarded by user equipment, causing inefficiencies in network and device performance.
Innovation Solution
Implementing an application policy mechanism to modify SIP message headers by removing, adding, or modifying optional and routing headers based on specific criteria, thereby optimizing SIP message structure and reducing unnecessary data transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If SIP messages include all mandatory and optional headers to ensure complete information transmission and future extensibility, then the protocol's adaptability and information completeness are improved, but the message size and data transmission overhead increase significantly
Solution Approach 1:
The patent segments SIP headers into mandatory headers (always included) and optional headers (conditionally included). The optional headers are further divided into service-specific headers that are only included when the receiving UA supports the corresponding service. This segmentation allows the protocol to maintain extensibility while reducing message size by excluding unnecessary headers.
Solution Approach 2:
The patent implements dynamic header inclusion based on UA capability negotiation. During the SIP dialog establishment, UAs exchange capability information, and subsequent messages dynamically include or exclude optional headers based on mutual capability matching. This dynamic approach allows the message structure to adapt to the specific communication context, improving efficiency while maintaining versatility.
2Adaptability or versatility
If applications insert multiple optional headers into SIP messages assuming peer support, then service functionality is enhanced, but network resource waste increases when peers do not support the service
Solution Approach 1:
The patent applies preliminary capability negotiation through SIP OPTIONS exchanges or capability tags in SDP bodies before actual service activation. Applications perform preliminary actions to determine peer support for optional services, and only then include service-specific optional headers in subsequent messages. This preliminary capability verification prevents network resource waste by avoiding transmission of unsupported service information.
3Loss of information
If SIP messages include substantial information in mandatory and optional headers to ensure complete communication context, then the protocol's information completeness is improved, but processing overhead and device resource consumption increase
Solution Approach 1:
The patent applies local quality by making header inclusion context-dependent rather than uniform. Mandatory headers provide essential communication context for all SIP messages. Optional headers provide additional context only when locally relevant—that is, when both sending and receiving UAs support the corresponding service. This local quality approach ensures information completeness where needed while improving processing efficiency by eliminating redundant information.
Data Source
AI summary
A user agent (UA) for communicating with a communications network implementing an internet protocol (IP) multimedia subsystem (IMS) is presented. The UA is configured to send and receive session initiation protocol (SIP) messages. The UA includes a processor configured to send a message to the network. The message identifies an application policy. The application policy defines at least one of a SIP message header field to include, a SIP message header field to remove, a SIP message header field to allow, and a SIP message header field to modify. The processor is configured to receive a SIP message from the network. The SIP message includes a set of SIP message header fields. The set of SIP message header fields are modified in accordance with the application policy.