IMS Protocol Conversion Entity for Domain Interoperability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems face challenges in providing interoperability between the Internet Protocol Multimedia Subsystem (IMS) domain and non-IMS domains, particularly due to differences in session management protocols, leading to limited access for external services and increased bandwidth consumption in mobile environments.
Innovation Solution
A method is introduced to receive service invocation messages from non-IMS domains, convert non-IMS session control protocol elements into IMS protocol elements, and establish or manage IMS control sessions within the IMS domain, using a mapping scheme to facilitate communication and authentication, enabling uniform addressing and session management across domains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If protocol conversion and session management mechanisms are implemented to enable interoperability between IMS and non-IMS domains, then service accessibility and interoperability are improved, but system complexity and processing overhead increase
Solution Approach 1:
A protocol conversion entity is introduced as an intermediary component that sits between non-IMS domains and the IMS core network. This entity performs protocol translation, converting non-IMS signaling protocols into IMS-compatible protocols (such as SIP), and vice versa. By placing this intermediary at the network boundary, the patent enables interoperability without requiring modifications to the core IMS architecture or existing non-IMS systems, thus resolving the contradiction between improving adaptability and maintaining system complexity at acceptable levels.
Solution Approach 2:
The patent segments the interoperability function into distinct modular components: a protocol conversion entity, session management functions, and service access interfaces. This segmentation allows each component to be independently developed, deployed, and managed. The protocol conversion entity handles protocol translation separately from session management tasks, which are handled by IMS core components. This modular approach reduces overall system complexity while enabling comprehensive interoperability functionality.
2Adaptability or versatility
If protocol conversion entities and session management functions are added to enable external access to IMS services, then service availability is improved, but processing time and resource consumption increase
Solution Approach 1:
The patent implements preliminary session establishment and authentication mechanisms where the protocol conversion entity pre-negotiates session parameters and establishes connection contexts before actual service transactions occur. Session templates and communication patterns are pre-configured based on service type, allowing rapid session instantiation when external users access IMS services. This preliminary preparation significantly reduces processing time during actual service interactions while maintaining comprehensive service accessibility.
3Adaptability or versatility
If comprehensive protocol translation and session management is implemented, then interoperability between domains is improved, but bandwidth consumption increases due to additional signaling
Solution Approach 1:
The patent merges multiple signaling functions into consolidated message exchanges. The protocol conversion entity combines protocol translation, session management, and service routing functions into integrated signaling flows. By merging these functions, the patent reduces the number of separate signaling messages required compared to implementing each function separately. This consolidation maintains full interoperability functionality while minimizing the total bandwidth consumption associated with signaling overhead between IMS and non-IMS domains.
Data Source
AI summary
The disclosure relates to a technique for providing interoperability between an Internet protocol multimedia subsystem (IMS) domain and a non-IMS domain. A method implementation of this technique comprises the steps of receiving on a service layer a service invocation message from a non-IMS domain, analyzing the message to identify the message as a request to invoke a service within the IMS domain, converting non-IMS session control protocol elements contained in the message into IMS session control related protocol elements, and generating an outgoing IMS message to establish an IMS control session.