Web-Enabled Session Border Controller for HTML5 to IMS Protocol Translation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Extending the IP Multimedia Subsystem (IMS) architecture to HTML environments is challenging due to incompatibility with HTTP over TCP/IP and the need for domain expertise, making it difficult to provide network services from IMS to HTML5 applications without radical changes to the IMS model or custom extensions to the HTML platform.

Innovation Solution

A system and method that uses an integrated web-enabled session border controller (WSBC) to create a communication channel between HTML-capable applications and the IMS core, employing a client-side JavaScript API to encapsulate the HTTP signaling layer and a network-side controller to normalize communications, allowing for seamless interaction without domain expertise.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If SIP protocol is used for IMS architecture, then network service capability is improved, but compatibility with HTTP and ease of operation deteriorates

Engineering Contradiction:
Improvenetwork service capabilityVSAvoidcompatibility with HTTP
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a Session Border Controller (SBC) as an intermediary component that translates between SIP protocol used in IMS architecture and HTTP protocol used in web environments. The SBC acts as a gateway that mediates communication between these two incompatible protocols, allowing HTML5 applications to access IMS network services without directly implementing SIP, thus maintaining both network service capability and HTTP compatibility

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If SIP protocol implementation is used, then network service capability is improved, but device complexity and domain expertise requirements increase

Engineering Contradiction:
Improvenetwork service capabilityVSAvoidimplementation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The Session Border Controller serves as a complexity-absorbing intermediary that handles all SIP protocol implementation details, state machine management, and signaling logic. This shields developers from SIP complexity while maintaining access to advanced network services, effectively decoupling service capability from implementation complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The SBC autonomously manages SIP session state, protocol translation, and signaling operations without requiring external control logic. It self-services the complexity of SIP implementation by encapsulating all protocol-specific logic within the gateway component, freeing the application layer from these concerns

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If custom extensions to HTML platform are made, then adaptability to IMS is improved, but ease of manufacture and standardization deteriorate

Engineering Contradiction:
Improveadaptability to IMSVSAvoidstandardization
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

Rather than extending the HTML platform with custom SIP implementations, the patent uses the SBC as an intermediary that speaks both SIP and HTTP. This approach maintains HTML5 standardization while achieving IMS adaptability through protocol translation at the network gateway level, avoiding the need for non-standard browser or application extensions

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9509745B2Java API for programming web real-time communication applications
Publication Date: 2016.11.29 ORACLE INT CORP
  • US9509745B2 patent drawing
  • US9509745B2 patent drawing
  • US9509745B2 patent drawing

AI summary

In accordance with an embodiment, described herein is a system and method for programming server-side real-time web communication applications. A JAVA application programming interface (API) is provided for web application developers to write JAVA applications on a server to control, manage, and mediate HTML5 endpoints that communicate with the JAVA applications. Each JAVA application can be a JAVA component that are annotated with a plurality of JAVA objects provided by the JAVA API, wherein the plurality of JAVA objects can also establish communication between HTML5 applications endpoints, and holding the state of the communication. The container can integrate with other enterprise technologies such as JMS and enable the JAVA applications to integrate with applications and services exposed by other providers, e.g., FACEBOOK. The JAVA API can be used to write applications that can connect with legacy IMS systems and services using existing JAVA APIs such as SIP servlet.