Interworking Function for SIP Endpoint Interoperability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Telecommunications networks face challenges in achieving endpoint interoperability across different vendors due to proprietary and incompatible conventions in Session Initiation Protocol (SIP) messages, particularly in Next-Generation Network (NGN) and IP Multimedia Subsystem (IMS) architectures, where endpoints with varying characteristics require specific handling to ensure seamless communication.
Innovation Solution
A network entity with interworking function is introduced between endpoints and registrars, which identifies endpoint characteristics from received messages and applies appropriate processing actions or interworking manipulation profiles to ensure compatibility, supporting dynamic registration and forking processes while adhering to architectural principles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If different SIP INVITE messages are used to support interoperability between endpoints from different vendors, then endpoint interoperability is improved, but message processing complexity increases
Solution Approach 1:
The patent introduces an interworking function as an intermediary component that sits between the endpoint and the registrar. This interworking function receives messages from endpoints with different vendor characteristics, identifies the endpoint type, and applies appropriate processing actions to convert messages into a standardized format for the registrar. By placing this intermediary layer in the network, the system achieves endpoint interoperability without requiring the registrar to handle all the complexity of different endpoint formats directly.
Solution Approach 2:
The patent applies parameter changes by modifying message parameters based on endpoint characteristics. The interworking function changes specific parameters in SIP messages (such as Alert-Info header field values) according to the identified endpoint vendor or type. This allows the same base message structure to be adapted to different endpoint requirements by transforming specific parameters, thereby achieving interoperability while maintaining a relatively simple base message format.
2Adaptability or versatility
If proprietary and incompatible conventions are used for Alert-Info header field content, then endpoint vendor specificity is improved, but communication compatibility deteriorates
Solution Approach 1:
The patent segments the communication function into separate components: the interworking function that handles vendor-specific conventions and the registrar that handles standardized communication. By segmenting this way, each component can optimize for its specific requirements - the interworking function maintains vendor specificity while the registrar maintains communication compatibility through standardization.
Solution Approach 2:
The interworking function acts as a mediator that translates between proprietary vendor-specific Alert-Info header field conventions and a standardized internal representation. It receives the proprietary format from the endpoint, converts it to a standardized format, and ensures compatible communication with the registrar, thereby resolving the compatibility issue while preserving vendor specificity at the endpoint level.
3Adaptability or versatility
If dynamic registration is supported for endpoints with varying characteristics, then network flexibility is improved, but processing requirements increase
Solution Approach 1:
The patent applies preliminary action by having the interworking function identify and classify endpoint characteristics early in the registration process. When an endpoint registers dynamically, the interworking function immediately identifies the endpoint type and determines the appropriate processing actions in advance. This preliminary classification allows subsequent message processing to be more efficient, as the system already knows which processing rules to apply, thereby supporting dynamic registration without proportionally increasing processing requirements.
Data Source
AI summary
A network entity comprises an interworking function. The network entity is between an endpoint and a registrar in a telecommunications network. A message is received for the registrar from the endpoint, the message comprising data identifying an endpoint characteristic of the endpoint. A message is received for the endpoint. A processing action to be used to process the received message for the endpoint is determined based on the data identifying the endpoint characteristic of the endpoint comprised in the received message for the registrar from the endpoint. The received message for the endpoint is processed in accordance with the determined processing action.


