SIP Application Server Dialog Association in IMS Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In IMS networks, when an Application Server (AS) acts as a Back-to-Back User Agent (B2BUA), existing protocols fail to correctly associate new SIP dialogs with original dialogs, leading to confusion in service logic processing due to differences in dialog identifiers, which can result in incorrect processing of SIP requests.
Innovation Solution
The AS generates a second SIP request by deciding whether to associate it with the first SIP request based on service logic, modifying the Route header by removing its URI and copying the rest of the Route header, or regenerating it in originating UA behavior mode, ensuring correct association and processing by the S-CSCF.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the AS serves as B2BUA and generates a new dialog, then the service logic can be flexibly implemented, but the S-CSCF cannot correctly associate the new dialog with the original dialog due to different dialog identifiers
Solution Approach 1:
The patent introduces an intermediary mechanism (custom SIP request parameters or header fields) to carry dialog association information between the AS and S-CSCF. This intermediary transports the necessary linkage data without relying on standard SIP dialog identifiers, thereby resolving the association problem while maintaining B2BUA functionality.
Solution Approach 2:
The patent segments the dialog identification mechanism into multiple components: standard SIP dialog identifiers for the AS-User interaction, and separate association identifiers (carried in custom parameters or headers) for the S-CSCF to track the original dialog. This segmentation allows each component to serve its specific purpose without conflict.
2Reliability
If the AS modifies the Route header to remove its URI, then the S-CSCF can process the request correctly, but the AS cannot maintain control over request routing
Solution Approach 1:
The patent applies preliminary action by having the AS embed routing control information (such as preferred next-hop indicators or routing preferences) into the SIP request before forwarding it to the S-CSCF. This allows the S-CSCF to make informed routing decisions while still respecting the AS's intended path, balancing automated processing with AS control.
Solution Approach 2:
The patent implements a feedback mechanism where the S-CSCF acknowledges received requests with routing status information, and the AS can adjust subsequent routing based on this feedback. This creates a closed-loop control system that maintains AS routing authority while ensuring reliable S-CSCF processing.
3Device complexity
If the S-CSCF uses standard SIP dialog identifiers, then the dialog management is simplified, but the association between new and original dialogs cannot be established when AS acts as B2BUA
Solution Approach 1:
The patent adds another dimension to dialog identification by introducing association identifiers that operate parallel to standard SIP dialog identifiers. Instead of replacing the standard mechanism, it layers an additional identification dimension on top, allowing the S-CSCF to distinguish between dialog lifecycle management (handled by standard identifiers) and dialog association tracking (handled by the new dimension).
Data Source
AI summary
A method for processing SIP requests in an IMS network includes: an AS in the IMS network receiving a first SIP request forwarded by a S-CSCF entity, generating a second SIP request and deciding whether it is needed to associate the second SIP request with the first SIP request in terms of service logic at the S-CSCF entity, if it is needed to associate two requests, removing the URI of the AS from the Route header of the first SIP request; otherwise, regenerating the Route header of the second SIP request in the originating UA behavior mode and sending the second SIP request to the S-CSCF entity. Also disclosed is a system for processing SIP requests in an IMS network, including an AS and a S-CSCF entity. Also disclosed is an AS for processing SIP requests in an IMS network and a network entity for service control.