SIP Message Parsing via Binary SOE Structure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
SIP servers face performance bottlenecks due to computation-intensive operations like token parsing and security processing, which are not efficiently addressed by existing methods such as ASN.1 or fixed-position token allocation, leading to inefficient processing and storage of SIP messages.
Innovation Solution
A method and system that parse SIP messages to create a binary SOE message structure with a header part, token type part, and token content part, allowing for efficient transformation and processing by grouping token types and contents, reducing server load and improving processing efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If text-based SIP messages are processed directly by the server, then the server can handle security processing and token parsing, but the CPU cycles are heavily consumed leading to performance bottlenecks
Solution Approach 1:
The patent extracts the computation-intensive token parsing function from the SIP server to a dedicated front-end component. The front-end parses SIP messages and generates binarized representations, while the server focuses on upper-layer application processing. This extraction resolves the contradiction by maintaining security processing capability while eliminating the CPU bottleneck that limited processing throughput.
Solution Approach 2:
The patent introduces a binarized message format as an intermediary representation between the text-based SIP protocol and the server's internal processing. This intermediate binary format enables efficient processing by the server without requiring it to parse text tokens, thus maintaining reliability while improving productivity.
2Adaptability or versatility
If ASN.1 TLV approach is used to binarize SIP messages, then token information can be accommodated, but the parser must go through the whole message to get needed information reducing efficiency
Solution Approach 1:
The patent segments the binarized message into distinct fields with predetermined positions, including message header fields and body fields. Each field has a specific location in the binary structure, allowing the parser to directly access needed information without traversing the entire message. This segmentation maintains adaptability for various token types while dramatically improving parsing efficiency.
3Ease of operation
If fixed position allocation is used for each token, then processing can be simplified, but storage efficiency is affected due to waste space between tokens of different lengths
Solution Approach 1:
The patent applies local quality by using fixed positions for message-level fields (header and body) while using variable-length encoding for the body content itself. The message header and body have predetermined positions that simplify processing, while the body field can accommodate tokens of different lengths efficiently through compact binary representation, thus achieving both processing simplicity and storage efficiency.
4Reliability
If the server processes all SIP messages completely, then all operations are performed, but CPU cycles are occupied by computation-intensive operations
Solution Approach 1:
The patent extracts computation-intensive token parsing operations from the server to a front-end component. The front-end performs complete message processing including token parsing and generates binarized representations, while the server processes only the compact binary format. This extraction maintains complete processing reliability while significantly reducing CPU cycle utilization on the server.
Data Source
AI summary
A method and system for processing session initiation protocol messages including receiving a session initiation protocol message by a front end, parsing the session initiation protocol message by the front end, grouping the token types and the token contents in the session initiation protocol message respectively, and setting up corresponding links between the token types and the token contents, wherein the session initiation protocol message, after parsing, is transformed to the session initiation protocol offload engine message with a session initiation protocol offload engine message header part, for storing message level information, a token type part, for storing token type information, wherein it comprises a plurality of fixed-length entries, and a token content part for storing token contents, wherein it comprises a plurality of variable-length entries, and processing the transformed session initiation protocol offload engine message at the server end.


