WebRTC Session Establishment via URL Invitation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current WebRTC communication methods require users to be connected to an application server and have a permanent web browser running, leading to resource consumption and complexity in establishing real-time communications between web browsers, especially on mobile devices, and involve tedious steps for users to initiate video chats.
Innovation Solution
A method that detects user interaction to establish a WebRTC communication session by generating a unique session identifier and URL address, allowing users to send a message with the URL to the recipient, which triggers the opening of a web page for communication, enabling WebRTC communication without the need for a permanent browser connection and simplifying the process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If users connect to an application server to establish WebRTC communication, then real-time communication can be established between browsers, but resource consumption increases and the process becomes more complex
Solution Approach 1:
The patent extracts the server connection requirement from the WebRTC establishment process. By using a URL-based invitation system where the inviter's browser address is shared directly, the mandatory server connection step is removed. Users can establish peer-to-peer WebRTC connections through direct browser interaction without needing to connect to an application server first, thereby reducing complexity while maintaining communication reliability
Solution Approach 2:
The patent segments the communication establishment process into independent phases: URL generation by the inviter, URL transmission through any communication channel, and URL activation by the invitee. This segmentation allows each phase to be handled independently without requiring continuous server connection, reducing overall system complexity while ensuring reliable communication establishment
2Reliability
If a permanent web browser connection is maintained for WebRTC communication, then real-time communication can be established, but resource consumption increases
Solution Approach 1:
Instead of maintaining a permanent browser connection, the patent uses periodic action through URL-based invitation. The browser is activated only when needed - when the inviter generates and sends a URL, and when the invitee receives and activates the URL. This on-demand activation pattern dramatically reduces resource consumption while maintaining communication availability when required
Solution Approach 2:
The patent applies preliminary action by pre-generating a URL that contains all necessary connection information. This URL serves as a persistent invitation that can be stored and transmitted without active browser connection. When the URL is activated, the browser connection is established automatically, eliminating the need for permanent connection maintenance while ensuring communication availability
3Reliability
If users follow the standard WebRTC process to initiate video chat, then communication can be established, but the process becomes tedious and complex
Solution Approach 1:
The patent uses copying by generating a URL that replicates the inviter's browser connection information. Instead of requiring users to manually configure complex WebRTC parameters or follow multi-step connection procedures, the system creates a copy of the connection state in URL form. This copied URL can be shared through any communication channel and automatically restores the connection context, dramatically simplifying user operation while ensuring reliable communication establishment
Solution Approach 2:
The patent applies universality by making the URL-based invitation system work across multiple communication channels and platforms. The same URL mechanism can be shared through messaging apps, email, social media, or any other communication medium. This universal approach eliminates the need for channel-specific connection procedures, reducing operational complexity while maintaining reliable communication establishment across different platforms
Data Source
AI summary
A method for establishing a web communication between a web browser running on a first terminal and a web browser running on a second terminal, distinct from a communication via a web browser being previously established between the first and second terminals. Following detection, by the first terminal, of a user interaction requesting establishment of a web communication with the second terminal, the first terminal creates a session identifier including at least one identifier of the first terminal, and generates a URL address including the created session identifier. The URL address makes it possible to access a web page to establish the requested web communication, via a server. The URL address is inserted into a message sent to the second terminal, which triggers opening by the browser of the first terminal of a web page downloaded from the server based on the URL address.