WebRTC Communication Encapsulation in Web Pages
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
WebRTC technology limits users to a dedicated communication page, preventing them from performing other tasks or navigating away without interrupting audio/video streams, which is impractical for applications like technical support and hinders its deployment in existing websites.
Innovation Solution
A method that dynamically modifies the web page structure using a communication library to encapsulate data within an iFrame, allowing navigation during WebRTC communications without interrupting the stream, by moving page content into an encapsulation structure and reloading it when necessary.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the user stays on a dedicated WebRTC communication page, then the audio/video stream remains stable, but the user cannot perform other tasks or navigate away
Solution Approach 1:
The web page is segmented into two independent parts: the WebRTC communication interface and the original page content. This is achieved by creating an iframe element that hosts the communication application, while the parent page retains its original content and navigation capabilities. Both segments can function independently without interfering with each other.
Solution Approach 2:
The WebRTC communication application is nested within an iframe element that is embedded in the parent web page. This nested structure allows the communication interface to exist within the context of the original page, enabling users to access both the communication features and the parent page content simultaneously without leaving the parent page.
2Adaptability or versatility
If the user navigates away from the WebRTC page, then the user can perform other tasks, but the WebRTC communication is interrupted
Solution Approach 1:
By separating the WebRTC communication interface into a distinct iframe element, the communication session is isolated from the parent page's navigation events. This segmentation ensures that navigation actions on the parent page do not affect the communication continuity within the iframe.
Solution Approach 2:
The iframe element acts as an intermediary container that shields the WebRTC communication from the parent page's navigation events. The iframe creates a separate document context that prevents navigation actions outside the iframe from interrupting the communication stream.
3Adaptability or versatility
If the entire web page is modified to support WebRTC, then WebRTC functionality is fully integrated, but the modification cost and complexity increase significantly
Solution Approach 1:
The solution segments the WebRTC integration into a separate, self-contained iframe module rather than modifying the entire page structure. This allows existing web pages to maintain their original architecture while adding WebRTC functionality through a standardized iframe embedding approach.
Solution Approach 2:
The iframe-based approach provides a universal integration method that can be applied to any existing web page without requiring page-specific modifications. The same iframe embedding technique works across different page structures and content types, reducing overall system complexity.
4Reliability
If a dedicated WebRTC page is created, then communication functionality is ensured, but the user experience of multitasking is degraded
Solution Approach 1:
The user interface is segmented into independent functional areas: the parent page for general tasks and the iframe for communication. This segmentation allows users to interact with both functions simultaneously in a single view, eliminating the need to switch between separate pages or applications.
Solution Approach 2:
The solution merges the WebRTC communication interface with the parent web page into a unified viewing experience. Both the communication interface and the original page content are displayed simultaneously within the same browser window, allowing users to multitask without leaving either function.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
The invention relates to a method for processing, by a device capable of implementing a display of data resulting from the transmission, by this device, of a request following the HTTP protocol, this transmission delivering an HTTP response comprising a display data structure (StructA) representative of a page (P) to be displayed and comprising data to be displayed (DA). According to the invention, such a method comprises: - a step of obtaining (50), by means of an indicator (Ind), information representative of a communication to be established according to the WebRTC protocol using a communication application (AppC); - a step of creating (60) an encapsulation data structure (Encaps) within the display data structure (StructA); - a step of moving (70) at least a part of the data to be displayed (DA) by said page (P) within said encapsulation data structure (Encaps);- an establishment step (80) by said communication application (AppC) of said communication to be established according to the WebRTC protocol.;