JavaScript API for WebRTC IMS Signaling Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Extending the IP Multimedia Subsystem (IMS) architecture to HTML environments is challenging due to incompatibility between Session Initiation Protocol (SIP) and HTTP over TCP/IP, requiring domain expertise and radical changes to the IMS model or custom extensions to the HTML platform, making it difficult to provide real-time communication services effectively.
Innovation Solution
A system and method that utilize a JavaScript Application Programming Interface (API) to create a communication channel between HTML-capable applications or operating systems and the IMS core, encapsulating the HTTP signaling layer and normalizing communications to be compatible with IMS, thereby enabling seamless interaction with telecommunications network services without domain expertise or radical changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If SIP protocol is used for IMS architecture, then real-time communication services can be provided, but compatibility with HTTP/TCP/IP and ease of implementation in HTML environments deteriorates
Solution Approach 1:
The patent introduces a gateway as an intermediary component that sits between the SIP-based IMS core network and the HTML/JavaScript environment. This gateway translates SIP signaling messages into JavaScript-compatible formats, allowing HTML5 applications to communicate with the IMS network without directly implementing SIP protocol, thus resolving the compatibility issue while maintaining real-time communication capabilities
Solution Approach 2:
The patent transforms the protocol parameters and communication patterns from SIP-based signaling to JavaScript-based asynchronous event handling. By changing the interaction model from request-response SIP messages to JavaScript events and callbacks, the system maintains the underlying SIP communication for reliability while presenting an easier-to-use interface for HTML environments
2Adaptability or versatility
If custom extensions to HTML platform or radical changes to IMS model are made, then compatibility between SIP and HTTP is improved, but system complexity and development difficulty increase
Solution Approach 1:
Rather than modifying the HTML platform or IMS model, the patent introduces a gateway intermediary that handles all protocol translation and adaptation logic. This approach achieves SIP-HTTP compatibility without requiring changes to either the client-side HTML environment or the server-side IMS architecture, thereby avoiding increased system complexity
Solution Approach 2:
The patent segments the system into distinct layers: the HTML/JavaScript application layer, the gateway translation layer, and the SIP/IMS core network layer. Each layer operates independently with well-defined interfaces, allowing compatibility to be achieved through the gateway layer without complicating the other layers or requiring radical changes to existing systems
3Reliability
If domain expertise in SIP protocol is required, then proper IMS integration is achieved, but ease of implementation and accessibility to developers deteriorates
Solution Approach 1:
The gateway serves as an intermediary that shields developers from SIP protocol complexity. By handling all SIP message construction, parsing, and translation internally, the gateway allows developers to work with simple JavaScript APIs while ensuring proper IMS integration through the gateway's expert SIP implementation
Solution Approach 2:
The patent creates a JavaScript-based representation layer that mirrors the essential functionality needed for real-time communication without replicating the full SIP protocol stack. This simplified copying of necessary functions in JavaScript allows developers to implement IMS integration using familiar web technologies rather than requiring deep SIP domain expertise
Data Source
AI summary
In accordance with an embodiment, described herein is a system and method for real-time communication signaling between HTML5 endpoints and between HTML5 endpoints and the IMS Core of a telecommunication network. In an embodiment the system includes a WebRTC Session Controller (WSC) communicating over an Internet domain protocol with a client-side controller. The WSC terminates web communications with the client-side, parses, and normalizes the Web communications into an internal protocol suitable for communication with telecommunications network systems. The client-side controller provides a JavaScript API that encapsulates the signaling aspect of a communication session of the HTML5 application, including gathering media description, establishing signaling channels, and exchanging media descriptions with the WSC, populating the relevant WebRTC objects, managing the call after it has been established. The JavaScript API thereby simplifies development and implementation of real-time communication in Web applications.