WebRTC Session Token Conversion via SIP Engine
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise networks face challenges in applying enterprise-specific policies and features to WebRTC interactive sessions across network boundaries, as existing solutions require a separate engine, which can be technically and financially burdensome.
Innovation Solution
Utilizing an enterprise Session Initiation Protocol (SIP) engine to apply policies to WebRTC sessions by converting WebRTC session description tokens into SIP request messages, allowing the existing SIP engine to enforce policies without the need for a dedicated WebRTC engine.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a separate WebRTC engine is implemented to apply enterprise policies to WebRTC sessions, then policy enforcement capability is improved, but device complexity and implementation cost increase
Solution Approach 1:
The patent merges the WebRTC session processing functionality with the existing enterprise SIP engine. The session token converter acts as an intermediary that translates WebRTC session description tokens into SIP request messages, allowing the single SIP engine to handle both traditional SIP sessions and WebRTC sessions. This consolidation eliminates the need for a separate WebRTC engine while maintaining policy enforcement capabilities.
Solution Approach 2:
The enterprise SIP engine is extended to perform multiple functions: handling traditional SIP sessions, processing WebRTC session tokens through the converter, and enforcing enterprise policies across both session types. This multi-functional approach allows one engine to serve multiple purposes, reducing overall system complexity while improving policy enforcement coverage.
2Reliability
If a dedicated WebRTC engine is implemented for policy application, then policy control is improved, but implementation cost increases
Solution Approach 1:
The system leverages the existing enterprise SIP engine's inherent policy enforcement capabilities to serve the additional function of WebRTC policy control. Rather than building a new engine from scratch, the system repurposes the existing infrastructure, allowing it to serve itself for multiple protocol types. This self-service approach reduces implementation costs while maintaining policy control effectiveness.
Solution Approach 2:
The session token converter creates a functional copy or translation layer that adapts WebRTC session tokens into SIP request messages. This copying mechanism allows the existing SIP engine logic to be reused for WebRTC sessions without requiring duplicate engine implementation, thereby reducing development and maintenance costs while preserving policy control functionality.
3Device complexity
If WebRTC sessions are processed without policy enforcement, then system simplicity is maintained, but enterprise security and compliance requirements are not met
Solution Approach 1:
The session token converter serves as an intermediary component between WebRTC session tokens and the enterprise SIP engine. This mediator translates WebRTC tokens into SIP request messages that the existing policy enforcement mechanisms can process. By introducing this intermediary layer, the system maintains relative simplicity while effectively integrating security and compliance controls into WebRTC session handling.
Data Source
AI summary
Application of enterprise policies to Web Real-Time Communications (WebRTC) interactive sessions using an enterprise Session Initiation Protocol (SIP) engine, and related methods, systems, and computer-readable media are disclosed. In one embodiment, a method comprises receiving, by session token converter of enterprise device, an incoming WebRTC session description token. The method comprises generating, by session token converter, outgoing SIP request message. The method comprises sending, by session token converter, outgoing SIP request message to enterprise SIP engine and applying, by enterprise SIP engine, enterprise policies based on outgoing SIP request message. The method comprises, responsive to applying enterprise policies, sending incoming SIP request message to enterprise device. The method comprises converting, by session token converter, incoming SIP request message into outgoing WebRTC session description token, and sending outgoing WebRTC session description token to a target device.