WebRTC Gateway for RCS Push Delivery

Solution Overview

Problem

Existing communication systems that provide Rich Communications Suite (RCS) features through periodic polling of web servers are inefficient, consuming excessive processing power and network resources for minimal data transfer.

Innovation Solution

Implementing a WebRTC data connection between a WebRTC-enabled browser and a WebRTC-IMS gateway, which allows for 'push' delivery of RCS data, reducing the need for periodic polling and optimizing resource usage by using lightweight WebRTC protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If periodic polling of web servers is used to provide RCS features, then RCS functionality can be delivered to users, but excessive processing power and network resources are consumed

Engineering Contradiction:

ImproveRCS feature delivery efficiencyVSAvoidprocessing power consumption

Core Design Contradiction:

ProductivityVSUse of energy by moving object

Solution Approach 1:

The patent replaces the traditional HTTP polling mechanism with a WebRTC data channel connection. This substitution eliminates the need for periodic HTTP requests and responses, creating a persistent bidirectional communication channel that delivers RCS data efficiently without the overhead of repeated connection establishment and protocol handling.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The WebRTC data channel establishes a continuous, persistent connection between the web browser and the web server. This allows RCS data to be delivered in real-time as it becomes available, rather than waiting for periodic polling intervals, thereby maintaining continuous useful action and eliminating wasted polling cycles when no data is available.

Inventive Principle:

Principle #20Continuity of useful action

2Productivity

If periodic polling of web servers is used to provide RCS features, then RCS functionality can be delivered to users, but excessive network resources are consumed

Engineering Contradiction:

ImproveRCS feature delivery efficiencyVSAvoidnetwork resource consumption

Core Design Contradiction:

ProductivityVSLoss of energy

Solution Approach 1:

The patent replaces the traditional HTTP polling mechanism with a WebRTC data channel connection. This substitution eliminates the need for periodic HTTP requests and responses, creating a persistent bidirectional communication channel that delivers RCS data efficiently without the overhead of repeated connection establishment and protocol handling.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The WebRTC data channel establishes a continuous, persistent connection between the web browser and the web server. This allows RCS data to be delivered in real-time as it becomes available, rather than waiting for periodic polling intervals, thereby maintaining continuous useful action and eliminating wasted polling cycles when no data is available.

Inventive Principle:

Principle #20Continuity of useful action

3Use of energy by moving object

If WebRTC data connection is implemented, then resource usage is optimized and control signaling is streamlined, but system complexity increases due to WebRTC protocol integration

Engineering Contradiction:

Improveprocessing power consumptionVSAvoidsystem complexity

Core Design Contradiction:

Use of energy by moving objectVSDevice complexity

Solution Approach 1:

The patent introduces a WebRTC gateway as an intermediary component that mediates between the WebRTC data channel and the existing RCS infrastructure. This gateway handles the complexity of WebRTC protocol integration, protocol translation, and data routing, thereby isolating the complexity from the core RCS system while enabling efficient WebRTC-based communication.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS9781167B2WebRTC data channel facilitating IMS support of RCS features

Publication Date: 2017.10.03 VERIZON PATENT & LICENSING INC

AI summary

A gateway may be configured to establish a first data connection between the gateway device and a client device. The first data connection may be based on a Web Real-Time Communication application programming interface. The gateway may establish a second data connection between the gateway device and an Internet Protocol (“IP”) Multimedia Subsystem (“IMS”) core; and facilitate communications, that are based on a Rich Communication Services (“RCS”) standard, between the client device and the IMS core. Facilitating the communications may include outputting communications, that are based on communications received from the client device via the first data connection, to the IMS core via the second data connection, and outputting communications, that are based on communications received from the IMS core via the second data connection, to the client device via the first data connection.