WebRTC Gateway URI Validation for Secure Private Network Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing WebRTC systems face challenges in preventing denial-of-service events and accurately tracking and billing WebRTC calls, especially when toll-free customers lack account numbers and passwords, and when calls overwhelm customer service networks.
Innovation Solution
Implementing a system that includes a WebRTC gateway with authorization interfaces, a validation proxy, and a backend system to validate URIs, manage call session data, and route calls through a private provider network, enabling secure connections and accurate billing by using URIs to direct calls to contact center services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If direct WebRTC connection is provided from user's browser application to customer representative, then ease of operation is improved, but reliability deteriorates due to vulnerability to denial-of-service events
Solution Approach 1:
The patent introduces an access server as an intermediary component between the user's browser application and the customer representative. This access server receives WebRTC connection requests, validates them against a backend system, and manages the connection establishment. By inserting this intermediary layer, the system maintains ease of operation for users while protecting against denial-of-service attacks, as the access server can filter and control incoming connections without requiring changes to the user interface or browser application.
2Reliability
If authorization interface is added to prevent denial-of-service events, then reliability is improved, but device complexity increases
Solution Approach 1:
The patent combines multiple functions into the access server component: it handles WebRTC connection requests, performs authorization validation by communicating with the backend system, manages URI validation, and controls connection routing. By merging these authorization and validation functions into a single access server rather than distributing them across multiple separate components, the system improves reliability through centralized control while minimizing the increase in overall device complexity.
3Measurement precision
If validation proxy and backend system are implemented to track and bill WebRTC calls, then measurement precision is improved, but device complexity increases
Solution Approach 1:
The access server is designed with multi-functionality, handling not only connection authorization but also call tracking and billing information collection. By making the access server universal and capable of performing multiple functions (authorization, validation, tracking, and billing support), the system achieves precise measurement of call metrics without requiring separate dedicated components for each function, thereby improving measurement precision while limiting the increase in device complexity.
Data Source
AI summary
A system may include a Web Real-Time Communication (WebRTC) backend server configured to receive a request for a Uniform Resource Identifier (URI) for a WebRTC call session requested by a browser application and generate the URI for the WebRTC call session; and a validation proxy configured to receive the URI from a WebRTC gateway and validate the URI with the WebRTC backend server. The WebRTC backend server may be receive a request to validate the URI from the validation proxy, determine whether the URI corresponds to a valid URI, and send a validation message to the validation proxy, if the received URI is valid. The validation proxy may generate a Session Initiation Protocol (SIP) message based on the received validation message and send the generated SIP message to a contact center services system to initiate a real-time call between the contact center services system and the browser application.