Extensible JavaScript API for WebRTC Session Controller
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Extending the IP Multimedia Subsystem (IMS) architecture to HTML5 environments is challenging due to incompatibility with HTTP over TCP/IP and the requirement for domain expertise, making it difficult to integrate IMS 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 an extensible JavaScript Application Programming Interface (API) to enable communication between HTML-capable applications and the IMS core, using a WebRTC Session Controller to encapsulate HTTP signaling and normalize communications, allowing for simple integration without domain expertise and radical changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If SIP protocol is used for IMS communication, then real-time communication signaling is achieved, but compatibility with HTTP and ease of use in Internet domain is lost
Solution Approach 1:
The patent introduces a gateway system that acts as an intermediary between SIP-based IMS networks and HTTP-based web applications. The gateway translates SIP signaling messages into HTTP-compatible formats, allowing web applications to communicate with IMS core networks without directly implementing SIP protocol, thus resolving the compatibility conflict while maintaining reliable real-time communication signaling.
Solution Approach 2:
The patent transforms the communication protocol parameters by mapping SIP protocol elements (headers, methods, status codes) to equivalent HTTP parameters. This parameter transformation allows the same communication functionality to operate over different protocol stacks, enabling HTTP compatibility while preserving SIP-based signaling reliability through systematic parameter substitution.
2Adaptability or versatility
If SIP protocol implementation is pursued, then telecommunication network services are accessed, but domain expertise and implementation complexity are required
Solution Approach 1:
The gateway serves as an intermediary that shields web applications from SIP protocol complexity. By handling SIP message translation, session management, and signaling protocol details within the gateway, the system allows developers to access telecommunication services using simple HTTP-based APIs without requiring deep SIP domain expertise or complex implementation logic.
Solution Approach 2:
The patent creates simplified copies or abstractions of SIP functionality that operate over HTTP. Instead of requiring full SIP stack implementation, the system replicates essential SIP signaling capabilities through HTTP-based message formats that mirror SIP semantics, reducing implementation complexity while maintaining service access capability.
3Adaptability or versatility
If IMS architecture is extended to HTML5 environments, then integration with web applications is achieved, but radical changes to IMS model or custom extensions to HTML platform are required
Solution Approach 1:
The gateway acts as an intermediary layer between existing IMS architecture and HTML5 web applications without requiring modifications to either side. It translates between IMS signaling protocols and web-compatible HTTP/HTTPS protocols, enabling seamless integration while preserving the integrity of both IMS core networks and standard HTML5 application environments.
Solution Approach 2:
The gateway provides universal compatibility by supporting multiple protocol stacks (SIP, HTTP, HTTPS) and communication patterns simultaneously. This multi-functional approach allows a single gateway implementation to serve diverse web applications and IMS services without requiring custom extensions to HTML platform or radical changes to IMS model.
Data Source
AI summary
The present invention provides 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 client-side controller provides an extensible JavaScript API. The extensible JavaScript API 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 extensible JavaScript API which provides for extending the JavaScript API to facilitate development of new types of HTML5 applications without changing the code of the existing JavaScript API.