IMS-HTML5 Gateway Protocol Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Extending IP Multimedia Subsystem (IMS) architecture to the HTML environment is challenging due to incompatibility of Session Initiation Protocol (SIP) with HTTP over TCP/IP and the requirement for domain expertise, making it difficult to integrate IMS network services with HTML5 applications without radical changes to the IMS model or custom extensions to the HTML platform.
Innovation Solution
A system and method that provides a communication channel between an HTML-capable application or operating system and the IMS core of a telecommunications network, using a client-side controller and network-side controller with a communications protocol to encapsulate HTTP signaling and normalize it into an internal protocol compatible with IMS, enabling seamless interaction without domain expertise.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If SIP protocol is used for IMS architecture, then telecommunication network services can be provided, but compatibility with HTML environment is poor and domain expertise is required
Solution Approach 1:
The patent introduces a gateway as an intermediary component that sits between the HTML5 application environment and the IMS core network. This gateway performs protocol translation, converting SIP signaling messages from the IMS network into HTTP-based signaling that can be understood and processed by HTML5 applications running in web browsers. The gateway mediates the interaction between these two incompatible environments, allowing HTML5 applications to access IMS services without directly implementing SIP protocol complexity.
2Reliability
If SIP protocol is used for IMS architecture, then telecommunication network services can be provided, but implementation complexity increases due to domain expertise requirements
Solution Approach 1:
The gateway acts as a mediator that absorbs and manages the complexity of SIP protocol implementation. Rather than requiring HTML5 applications to directly implement SIP signaling, the gateway handles all SIP message construction, parsing, and state management. This transfers the implementation complexity from the application layer to the network infrastructure layer, simplifying the client-side implementation while maintaining reliable IMS service delivery.
Solution Approach 2:
The patent segments the IMS architecture into distinct functional components: the HTML5 application layer, the gateway layer, and the IMS core network layer. Each layer has clearly defined responsibilities and interfaces. The gateway layer is further segmented into signaling translation functions, session management functions, and media handling functions. This segmentation allows each component to be developed, tested, and maintained independently, reducing overall system complexity.
3Adaptability or versatility
If custom extensions to HTML platform are made, then IMS integration is possible, but platform standardization is compromised
Solution Approach 1:
The gateway serves as an intermediary that enables IMS integration without requiring custom extensions to the HTML platform. By implementing the protocol translation and adaptation logic in the gateway rather than in the HTML platform itself, the solution maintains HTML platform standardization while achieving IMS integration capability. The gateway acts as a standalone component that bridges the standardized HTML environment with the IMS network.
Solution Approach 2:
The patent implements a virtual representation of SIP signaling mechanisms within the gateway using standard HTTP protocols. Rather than modifying the HTML platform to support SIP natively, the gateway creates a copied or emulated SIP signaling environment using familiar HTTP methods and message formats that web browsers can understand and process through standard JavaScript APIs.
Data Source
AI summary
The present invention provides a system and method for real-time communication signaling between HTML5 endpoints and the IMS Core of a telecommunication network. The method adapts complex signaling on the server-side into simple operations towards the Web. In an embodiment the system includes a network-side controller communicating over an Internet domain protocol with a client-side controller. The client-side controller provides a JavaScript API to encapsulate the signaling layer. The network-side controller includes session border control functionality, terminates Internet domain communications with the client-side, parses, and normalizes the Internet domain communications into an internal protocol suitable for communication with telecommunications network systems. The system thereby provides a dedicated signaling channel with session border control for applications on the client to interact with telecommunications network services.