WebRTC Gateway Architecture for Seamless Telephony Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current WebRTC-based communication systems face challenges in providing a cost-effective, modular, and expandable infrastructure for various communication scenarios, including seamless connectivity between different end devices and infrastructures, with limitations in API compatibility, media transcoding, and user agent functionality.
Innovation Solution
The ComX architecture addresses these challenges by using connectors for modular network connections, a cloud-based user agent for call acceptance and switching, and an intelligent media gateway for efficient transcoding, decoupling web developers from platform changes and providing a consistent API, along with device connectors that handle end-device properties.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If WebRTC-based communication systems use direct peer-to-peer connections between browsers, then communication simplicity and platform independence are improved, but infrastructure flexibility and adaptability to different communication scenarios deteriorate
Solution Approach 1:
The patent introduces a Session Border Controller (SBC) as an intermediary component that mediates between peer-to-peer WebRTC connections and traditional telephony networks. The SBC provides protocol translation, network address translation, and signaling functions, enabling seamless integration between modern WebRTC browsers and legacy telephony infrastructure while maintaining the simplicity of direct browser-based communication.
Solution Approach 2:
The system architecture is segmented into distinct functional components: WebRTC peer-to-peer communication layer, Session Border Controller layer, and traditional telephony network layer. This segmentation allows each layer to operate independently with well-defined interfaces, providing flexibility to adapt different layers to various communication scenarios without affecting the entire system.
2Adaptability or versatility
If WebRTC gateways provide comprehensive communication functionality, then communication capability is improved, but system complexity and cost increase
Solution Approach 1:
The Session Border Controller is designed as a universal platform that performs multiple functions including protocol translation, media relay, signaling management, and network address translation. By consolidating these diverse functions into a single multi-functional component, the system achieves comprehensive communication capability without proportionally increasing overall system complexity.
Solution Approach 2:
The SBC automatically performs protocol translation and network configuration tasks without requiring manual intervention. It self-adapts to different communication scenarios by dynamically selecting appropriate translation rules and protocols, reducing operational complexity while maintaining versatile communication capabilities.
3Adaptability or versatility
If WebRTC systems support multiple communication scenarios, then versatility is improved, but API compatibility and developer ease of use worsen
Solution Approach 1:
The Session Border Controller acts as an intermediary that handles scenario-specific logic and protocol variations, allowing the WebRTC browser API to remain consistent and simple. Different communication scenarios (voice calls, video conferences, instant messaging) are supported through the SBC's ability to translate various protocols while presenting a unified WebRTC interface to developers.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
Method and device for controlling web-based communication comprising: a gateway that provides an API for integration with a web browser, preferably according to the WebRTC standard, including pluggable connectors for connecting further platform elements such as IP multimedia subsystem, PBX SIP proxy, telephone system, simple conference with group call, voicemail systems.The process comprises the following steps: - Establishing a communication connection from the web browser to the gateway via the API, - Checking the communication target by the gateway and establishing a communication connection between the API and a connector associated with a platform element, - Establishing a communication connection between the connector and the platform element, - Transmitting communication information between the web browser and the platform element via the API, the gateway and the connector, whereby the communication information is adapted by the connector.