SIP URI End-to-End Transfer via Nomapping Parameter
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing SIP technologies face challenges in transferring a direct contact address of a user or service end-to-end, particularly when using Back-to-Back User Agents (B2BUA) like Session Border Controllers (SBC) or Application Servers, which modify the Contact header, preventing third parties from joining sessions such as conferences.
Innovation Solution
Introducing a 'nomapping' URI parameter, a 'P-Unique-Address' SIP header, or including the URI in the message body to prevent modification by B2BUA, ensuring the URI is not changed or replaced, allowing direct routing to the intended recipient.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If B2BUA modifies the Contact header to hide topology and identity, then security and privacy are improved, but end-to-end address transfer capability deteriorates
Solution Approach 1:
The patent segments the Contact header into two distinct parts: a public Contact header that B2BUA can modify for topology hiding, and a private Contact header (or alternative header field) that preserves the original end-to-end address. This segmentation allows both security functions and address transfer capabilities to coexist without interference.
Solution Approach 2:
The patent introduces an intermediary mechanism (such as a private header field or URI parameter) that acts as a mediator between the B2BUA's security requirements and the end-to-end address transfer needs. This intermediary carries the original address information through the B2BUA without being modified, while the public Contact header undergoes normal B2BUA processing.
2Ease of operation
If Contact header is mapped to B2BUA address, then routing control is improved, but direct contact address transfer to third party deteriorates
Solution Approach 1:
The patent applies preliminary action by preserving the original contact address in advance (in a private header or alternative field) before B2BUA mapping occurs. This ensures that the direct address information is captured and protected prior to any routing modifications, enabling subsequent end-to-end address transfer without loss.
3Adaptability or versatility
If inverse mapping is required at intermediate nodes, then routing flexibility is improved, but message path dependency increases
Solution Approach 1:
The patent extracts the original end-to-end address from the Contact header and places it in a separate private header field or alternative location. This extraction eliminates the need for inverse mapping at intermediate nodes, as the original address is directly available in the private header without requiring path-dependent reconstruction.
Data Source
AI summary
According to a first aspect of the present invention there is provided a method of facilitating the end-to-end transfer of a URI between a plurality of SIP entities. The method comprising generating a SIP message and including the URI to be transferred in a Contact header of the message and including in the Contact header a parameter indicating to a back-to-back user agent that this URI is not to be changed or replaced.


