WebSocket JSON Protocol for IMS-HTML5 Signaling Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Extending 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.
Innovation Solution
A protocol component that enables communication between HTML-capable applications or operating systems and the IMS core, using JavaScript Object Notation (JSON) and WebSocket, to facilitate real-time communication signaling without domain expertise and radical changes, by encapsulating the HTTP signaling layer and parsing communications into internal protocols suitable for IMS systems.
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/TCP/IP and ease of operation deteriorates
Solution Approach 1:
The patent introduces a gateway device that acts as an intermediary between the HTML5 application environment and the IMS core network. The gateway performs protocol conversion, translating SIP signaling messages from the IMS network into JSON-based HTTP-compatible messages that can be processed by web browsers, thereby resolving the incompatibility between SIP and HTTP/TCP/IP while maintaining reliable real-time communication signaling.
Solution Approach 2:
The patent changes the protocol parameters from SIP-specific syntax and semantics to JSON-based representations that are natively compatible with HTTP/TCP/IP. This includes transforming SIP message structures, headers, and body formats into JSON objects that can be exchanged over standard web protocols, making the system easier to operate within HTML5 environments.
2Reliability
If SIP protocol is used for IMS communication, then real-time communication signaling is achieved, but device complexity and domain expertise requirements increase
Solution Approach 1:
The gateway device serves as an intermediary that abstracts away the complexity of SIP protocol implementation. By handling all SIP message generation, parsing, and translation internally, the gateway shields HTML5 developers from needing to understand SIP domain expertise, while still achieving reliable real-time communication signaling through the IMS network.
Solution Approach 2:
The patent creates a simplified copy of the signaling interface tailored for HTML5 environments using JSON and JavaScript APIs. Instead of requiring developers to implement full SIP stacks, the system provides a browser-friendly abstraction layer that copies only the essential communication functions in a simplified form, reducing device complexity and eliminating the need for domain expertise.
3Adaptability or versatility
If IMS architecture is extended to HTML environments with custom extensions, then compatibility improves, but implementation complexity and manufacturing precision increase
Solution Approach 1:
The gateway acts as an intermediary that enables IMS architecture extension to HTML environments without requiring custom extensions to the HTML platform itself. The gateway handles all protocol adaptation and translation, maintaining standard HTML5 compatibility while achieving IMS integration, thereby reducing implementation complexity and avoiding the need for platform modifications.
Data Source
AI summary
In accordance with an embodiment, described herein is a system for real-time communication signaling protocol for use in a telecommunication network and communication in web-only Internet. The protocol facilitates adapting complex signaling on the server-side into simple operations towards the Web. In an embodiment the protocol is used to communicate between a server-side web signaling engine and a client-side communication controller. The client-side communication controller provides a JavaScript API to encapsulate the signaling layer. The web signaling engine includes a controller which terminates communications using the protocol, and normalizes communications into an internal protocol suitable for communication with telecommunications network systems. In an embodiment, the protocol utilizes JSON and a WebSocket connection and can be defined as a WebSocket subprotocol.