WebRTC Gateway Identity Mapping for SIP Interworking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing WebRTC communications face authentication issues when interfacing with SIP networks due to differences in authentication technologies and databases, limiting seamless interworking between web-based and SIP-based systems.
Innovation Solution
A WebRTC gateway system that decouples security providers from identity mapping functionality, using a Groovy script to perform flexible web-SIP identity mapping, allowing access to different resources such as databases or REST servers, thereby enabling comprehensive authentication interworking between web and IMS systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If WebRTC applications use typical web authentication technologies, then web-based communications are authenticated successfully, but authentication interworking with SIP networks fails due to different authentication technologies and databases
Solution Approach 1:
The patent introduces an identity mapping mechanism as an intermediary layer between web authentication systems and SIP network authentication systems. This mapping translates web authentication identities into SIP-compatible identities, enabling communication between the two different authentication domains without requiring changes to either system's core authentication technology.
Solution Approach 2:
The authentication process is segmented into distinct functional components: web authentication module, identity mapping module, and SIP authentication module. This segmentation allows each component to operate independently with its own authentication technology while maintaining overall system interoperability through defined interfaces.
2Ease of operation
If security providers are coupled with identity mapping functionality, then authentication processing is simplified, but flexibility and adaptability to different authentication methods are reduced
Solution Approach 1:
The patent divides the security provider functionality into separate components: the core security provider handling authentication and the identity mapping functionality as a distinct module. This segmentation maintains operational simplicity while enabling flexible configuration of different authentication methods through the modular identity mapping component.
Solution Approach 2:
The identity mapping mechanism is designed as a dynamic, configurable component that can adapt to different authentication methods and database types. This dynamic nature allows the system to flexibly support multiple authentication schemes without requiring changes to the core security provider, maintaining simplicity while enhancing versatility.
3Device complexity
If a single resource is used for both web authentication and identity mapping, then system complexity is reduced, but access to different databases and REST servers is limited
Solution Approach 1:
The identity mapping mechanism is designed as a universal interface that can access multiple types of resources including different databases and REST servers. This multi-functional capability allows the system to support various authentication data sources without increasing overall system complexity, as the identity mapping layer abstracts the diversity of resource types.
Data Source
AI summary
A system performs authentication for real-time communications (RTC). The system receives a request from a browser application for web authentication of a user. The system then performs the web authentication by a security provider by reaching a first resource, where the security provider determines a security principal for the user. Subsequently, the system executes a security Groovy script to obtain an identity mapping from a second resource different than the first resource, where the identity mapping maps the security principal to an Internet Protocol (IP) Multimedia Subsystem (IMS) identity. The system then provides the identity mapping to a runtime Groovy script.