Stateless SIP Cluster Mapping via Embedded Headers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In SIP contexts, session border controllers maintain stateful mappings of contact address information, which requires resource-intensive synchronization between cluster nodes, leading to potential transaction failures when stateful mapping information is not shared correctly.
Innovation Solution
Generating and using statelessly reversible representations of SIP information by SIP cluster entities, allowing for algorithmic conversion without storing state information, thus eliminating the need for synchronization between cluster nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If session border controllers maintain stateful mappings of contact address information, then the original SIP information can be recovered, but resource-intensive synchronization between cluster nodes is required
Solution Approach 1:
The patent extracts the mapping information from the SIP messages themselves and embeds it directly in the message headers (via, record-route, service-route). This eliminates the need for external stateful storage and synchronization between cluster nodes, as each node can independently access the mapping information from the message headers when needed.
Solution Approach 2:
The SIP messages carry their own mapping information through header fields, making them self-sufficient. Cluster nodes do not need to query external databases or synchronize state with each other, as all necessary mapping data is embedded within the messages themselves, enabling independent processing.
2Reliability
If stateful mapping information is synchronized between cluster nodes, then failover capability is improved, but network bandwidth and cluster node resources are consumed
Solution Approach 1:
The mapping information is extracted from external stateful storage and embedded directly in the SIP message headers. This eliminates the need for continuous synchronization traffic between cluster nodes, reducing network bandwidth consumption and node resource usage while maintaining failover capability.
Solution Approach 2:
The mapping information is prepared and embedded in the SIP messages before they are routed through the cluster. This preliminary action ensures that all necessary information is already present in the messages, eliminating the need for real-time synchronization during failover events.
3Reliability
If contact address information is mapped to another value for privacy, then security is improved, but the mapping must be stored statefully to maintain reversibility
Solution Approach 1:
The mapping relationship is extracted from external stateful databases and embedded directly in the SIP message headers. This allows privacy protection through address mapping while eliminating the need for stateful storage, as the mapping information travels with the message itself.
Solution Approach 2:
The SIP message headers act as an intermediary carrier that transports the mapping information between the original contact address and the mapped address. This intermediary mechanism enables privacy protection without requiring persistent stateful storage at any node.
Data Source
AI summary
The subject matter described herein relates to methods, systems, and computer readable media for generating and using statelessly reversible representations of SIP information by SIP cluster entities. One method includes, at a first SIP cluster entity, receiving a first SIP message including SIP information. The method further includes generating a second SIP message including a statelessly reversible representation of the SIP information. The method further includes transmitting, to a SIP entity that is not a member of the cluster to which the first SIP entity belongs, the second SIP message with the statelessly reversible representation and information for reaching the cluster.