WebRTC Media Server Stream Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current WebRTC technology is inefficient and non-scalable for managing complex real-time multimedia streams, requiring multiple WebSocket/PeerConnection pairs for each source and destination, leading to high bandwidth consumption and limited seamless handling of multiple streams.

Innovation Solution

A WebRTC Media Server acts as an intermediary between Web client applications, managing multiple streams through a stream manager, enabling transcoding, resizing, and seamless switching, decoupling data and negotiation mechanisms to optimize communication and reduce client-side load.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If WebRTC technology is used for one-to-one real-time communication, then communication quality is ensured through dedicated control plane and peer connection, but managing complex multi-stream scenarios requires creating and managing multiple WebSocket/PeerConnection pairs at client side which increases device complexity and reduces scalability

Engineering Contradiction:
Improvecommunication qualityVSAvoidclient-side connection management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a server as an intermediary component that manages multiple WebSocket/PeerConnection pairs centrally. Instead of each client managing multiple connections to multiple peers, the server acts as a hub that routes streams between clients. This mediator approach maintains reliable peer-to-peer communication quality while centralizing connection management complexity on the server side, thereby reducing client-side device complexity and improving scalability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If each web client application directly sends streams to every peer in multi-stream communication, then real-time communication is achieved, but bandwidth consumption increases significantly and stream adaptation impacts sending device performance

Engineering Contradiction:
Improvereal-time communication speedVSAvoidbandwidth consumption
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

The patent merges multiple stream transmissions into a single centralized stream management system. Instead of each client sending duplicate streams to multiple peers (one-to-many duplication), the server consolidates stream handling, receiving each stream once and redistributing it to multiple clients. This combining approach maintains real-time communication speed while significantly reducing total bandwidth consumption, as the stream is transmitted over the network only once per source rather than once per recipient.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The server creates optimized copies of streams for distribution to multiple clients. Rather than forcing the original sending client to maintain multiple active transmissions, the server receives the original stream and generates necessary copies for distribution to multiple peers. This copying mechanism at the server side preserves real-time delivery to all recipients while reducing the sending device's processing load and bandwidth consumption.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If receiving web client applications handle multiple real-time streams simultaneously, then multi-stream communication is achieved, but performance is limited by available bandwidth and handling becomes non-transparent

Engineering Contradiction:
Improvemulti-stream handling capabilityVSAvoidstream processing efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The server acts as an intermediary that handles the complexity of multi-stream management, receiving streams from multiple sources and distributing them to multiple clients. This centralizes the burden of managing multiple simultaneous streams, allowing receiving clients to handle streams transparently without being overwhelmed by bandwidth management complexity. The mediator absorbs the processing efficiency challenges while maintaining adaptability for various multi-stream scenarios.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2833595B1Multimedia streams in web applications
Publication Date: 2018.10.31 ALCATEL LUCENT SA
  • EP2833595B1 patent drawingFigure 1~2
  • EP2833595B1 patent drawingFigure 3~4

AI summary

Network component comprising an input interface for receiving a media stream from a web client application, an output interface for transmitting a requested media stream to a further web client application, a stream manager adapted for storing information about media streams, a controller connected to the input and output interface, adapted to register incoming streams, and adapted to register requested media streams in the stream manager, and a processor for transferring a registered incoming stream from an input interface to an output interface requesting the registered incoming stream.