Web Browser Real-Time Communication Redirection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current real-time communication technologies between web browsers, such as WebRTC, do not inform users when the recipient is unavailable, leading to unsuccessful communication attempts without providing reasons for the failure.
Innovation Solution
Implementing a method where a first web browser automatically redirects the user to a messaging service when the called user is unavailable, providing a message indicating the status and allowing the user to leave a message, which is then notified to the recipient through various channels like SMS or email.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If real-time communication is implemented between web browsers using WebRTC, then communication functionality is provided, but users are not informed when the recipient is unavailable
Solution Approach 1:
The patent implements a feedback mechanism where the system automatically checks the availability status of the recipient and provides information back to the caller. When a user initiates a real-time communication, the system queries the recipient's availability through the application server and displays the status (available, unavailable, or busy) to the caller, enabling informed communication decisions.
Solution Approach 2:
The patent introduces an intermediary availability checking mechanism between the caller and recipient. The application server acts as a mediator that receives availability requests from the caller's browser, queries the recipient's status, and returns the availability information without requiring direct interaction between the caller and recipient.
2Adaptability or versatility
If automatic redirection to messaging service is implemented, then users can leave messages when recipient is unavailable, but system complexity increases
Solution Approach 1:
The patent implements a universal communication system where a single real-time communication platform supports multiple communication modes. The system can automatically switch between real-time communication (when recipient is available) and asynchronous messaging (when recipient is unavailable), providing multi-functionality through a unified interface without requiring separate systems.
Solution Approach 2:
The application server acts as an intermediary that coordinates between real-time communication and messaging services. When the recipient is unavailable, the server automatically redirects the communication attempt to the messaging service, managing the transition between different communication modes without increasing client-side complexity.
3Reliability
If presence information checking is implemented, then communication failures can be detected, but additional information processing is required
Solution Approach 1:
The patent implements preliminary action by checking the recipient's availability status before initiating the actual real-time communication. The system queries the presence information in advance, allowing the caller to know whether the recipient is available before attempting to establish a connection, thereby avoiding unnecessary communication failures.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The invention relates to a method for real-time communication using RTC web technology, between web browsers in an internet communication network, including: preliminary loading (S20), by a first web browser of a first terminal associated with a first user, of a web application provided by an application server, the web application providing real-time communication functionalities between web browsers; sending (S21), by the first browser via said web application to the application server, a call establishment request including an identifier of a user receiving the call, referred to as second user; said method being characterised by also comprising steps of: determining (S22, S23, S24) a state of the availability of the second user to answer the call establishment request; and automatic redirection (S25) to a web address of a messaging service associated with the second user, when the second user is in the unavailable state.