IMS Session Merging via Service Identifier Matching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing network entities struggle to correctly route communication sessions across different access technologies and services, leading to issues in maintaining seamless multimedia session continuity, especially when sessions need to be split and merged during access transfers, without disturbing the end-user experience.
Innovation Solution
A session handling entity, implemented in a multimedia session continuity application server or a session split and merge function, uses IMS Communication Service Identifiers (ICSI) and Open Mobile Alliance feature tags to determine if sessions belong to the same service, allowing them to be merged into a single session by re-negotiating the SIP session using re-INVITE or UPDATE requests, ensuring correct routing and maintaining session continuity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple communication sessions are maintained separately for different access technologies, then session routing and service delivery are simplified, but session continuity and user experience are degraded during access transfers
Solution Approach 1:
The patent merges multiple communication sessions (CS domain session and PS domain session) into a single unified session during access transfers. The session handling entity consolidates session state information from both domains, allowing seamless continuity without requiring separate session management for each access technology, thus resolving the contradiction between reliability and complexity
Solution Approach 2:
The session handling entity acts as an intermediary between the CS domain and PS domain session management. It receives session state information from both domains, determines whether sessions should be merged based on service identifiers, and coordinates the merging process, thereby simplifying overall session management while ensuring continuous service delivery
2Productivity
If sessions are merged automatically during access transfers, then session continuity is improved, but incorrect merging of sessions from different services may occur
Solution Approach 1:
The session handling entity performs preliminary checks by comparing service identifiers (ICSI, feature tags) before merging sessions. This preliminary verification ensures that only sessions belonging to the same service are merged, preventing incorrect merging while maintaining efficient session transfer, thus resolving the contradiction between productivity and precision
Solution Approach 2:
The system uses service identifiers as feedback mechanisms to verify whether sessions should be merged. By continuously monitoring and comparing service identifiers during session establishment and transfer, the system ensures accurate merging decisions, preventing incorrect associations while maintaining transfer efficiency
3Adaptability or versatility
If session state information is maintained in multiple network entities, then service flexibility is improved, but routing correctness and session management are degraded
Solution Approach 1:
The patent extracts and centralizes session state information management in a dedicated session handling entity. By taking out the session state information from distributed network entities and consolidating it in one location, the system maintains service flexibility through the entity's ability to handle both CS and PS domains while ensuring routing correctness through centralized control, resolving the contradiction between adaptability and reliability
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present invention relates to a session merging entity in a communication system IMS. The merging entity is handling communication of the first user; the communication comprises a first session and a second session. The first session and the second session are merged into a single session towards the second user, if the same IMS communication service identifier has been indicated for the first session and the second session. The merging entity may also be located at the terminal device of the second user.