WebRTC Gateway Server for Charging Session Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

WebRTC technology lacks tools for implementing charging solutions in customer service interactions, making it difficult to determine and manage connection costs between service providers and customers.

Innovation Solution

A method and communication system that utilize WebRTC technology to establish communication sessions, including generating charging data records through the public switched telephone network, and using a connection management server to associate and manage identifiers for voice and data connections, enabling the carriage of real-time video, video files, and chat application data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If WebRTC technology is used for direct peer-to-peer communication, then ease of operation and user experience are improved, but the ability to implement charging solutions deteriorates

Engineering Contradiction:
Improveuser experienceVSAvoidcharging capability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent introduces a server as an intermediary between WebRTC peers to enable charging functionality. The server receives charging requests from either peer, generates charging data records, and manages the charging process without disrupting the direct peer-to-peer media flow. This mediator approach allows WebRTC to maintain its simplicity while gaining enterprise-grade charging capabilities through the server's coordination.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If direct peer-to-peer WebRTC communication is implemented, then device complexity is reduced, but the ability to manage and authenticate connections deteriorates

Engineering Contradiction:
Improveapplication complexityVSAvoidconnection management
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The server acts as a trusted intermediary that handles authentication, authorization, and connection management tasks. It verifies user credentials, manages session states, and coordinates charging processes, thereby providing reliable connection management without increasing the complexity of peer devices. The server centralizes these control functions while peers maintain simple WebRTC client implementations.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If WebRTC enables simplified communication establishment, then productivity is improved, but the ability to generate charging data deteriorates

Engineering Contradiction:
Improveconnection establishment speedVSAvoidcharging data
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The system performs preliminary actions by establishing the WebRTC connection quickly for immediate communication, while simultaneously or subsequently initiating charging data generation through the server. The server collects necessary charging information (duration, data volume, participant identifiers) during and after the communication session, ensuring charging data is captured without delaying the productive peer-to-peer connection establishment.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3550794B1Solution for establishing a communication session
Publication Date: 2021.06.09 TELIASONERA AB
  • EP3550794B1 patent drawingFigure 1~3
  • EP3550794B1 patent drawingFigure 2
  • EP3550794B1 patent drawingFigure 4~5

AI summary

The present invention relates to a method for establishing a communication session. First, the communication session is initiated by a server (100). Next, a first connection request (215) is generated for a voice call between a first WebRTC device (105) and a second WebRTC device (110) over a WebRTC gateway device (115). A second connection request (220) comprising an identifier of first WebRTC device (105) is generated towards a connection management server (120). Next, an inquiry to the connection management server (120) by the second WebRTC device (110) is generated for determining (235) if a connection request is received from the first WebRTC device (105), and in that case the communication session comprising both the first connection for the voice call and a second connection is established.