Hybrid Information-Centric Networking RTC Transport

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current real-time communication (RTC) technologies face challenges in scaling due to stringent latency requirements, leading to increased network resource usage and latency introduction, especially when dealing with passive participants in communication sessions, and require server-based encoding and decoding that adds computational and network load.

Innovation Solution

Implementing a Hybrid Information-Centric Networking (hICN)-RTC architecture that distinguishes between active and passive participants, using different transport mechanisms to manage latency and resource allocation, ensuring low latency for active participants while relaxing synchronization constraints for passive participants, thus optimizing network resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If current RTC protocols forward content to all end users including passive participants, then content distribution is achieved, but network resource usage increases and latency is introduced

Engineering Contradiction:
Improvecontent distributionVSAvoidlatency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies local quality by differentiating transport mechanisms based on participant type: active participants receive content via RTP with latency guarantees, while passive participants receive content via HTTP fluency streaming without latency guarantees. This localized adaptation of transport quality resolves the contradiction by optimizing resource usage for each participant category while maintaining their respective content distribution needs.

Inventive Principle:
Principle #3Local quality

2Adaptability or versatility

If RTC scales with increasing participating devices, then broader communication coverage is achieved, but network resource usage increases due to latency requirements

Engineering Contradiction:
Improvecommunication coverageVSAvoidnetwork resource usage
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent changes the transport parameter (latency guarantee) based on participant role. Active participants use RTP with strict latency parameters, while passive participants use HTTP streaming with relaxed latency parameters. This parameter differentiation enables the system to scale to more devices without proportionally increasing network resource consumption, as passive participants consume fewer resources.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If server-based audio/video encoding or decoding is implemented, then content format distribution is achieved, but computational load and network load increase

Engineering Contradiction:
Improvecontent format distributionVSAvoidcomputational load
Core Design Contradiction:
Adaptability or versatilityVSPower

Solution Approach 1:

The patent extracts the encoding/decoding requirement from the server function and relocates it to the client devices. Each participant device performs its own encoding and decoding operations, eliminating the need for server-based media processing. This extraction resolves the contradiction by maintaining content format adaptability at the client level while removing the computational and network burden from the server.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11546398B1Real-time transport (RTC) with low latency and high scalability
Publication Date: 2023.01.03 CISCO TECHNOLOGY INC
  • US11546398B1 patent drawing
  • US11546398B1 patent drawing
  • US11546398B1 patent drawing

AI summary

In one embodiment, a device obtains traffic for an application to be sent to a plurality of hybrid Information-Centric Networking clients. The device divides the plurality of hybrid Information-Centric Networking clients into active hybrid Information-Centric Networking clients and passive hybrid Information-Centric Networking clients, based in part on whether a given hybrid Information-Centric Networking client is sharing content with the plurality of hybrid Information-Centric Networking clients via the application. The device sends, to the active hybrid Information-Centric Networking clients, the traffic using a first transport mechanism that guarantees a level of end-to-end latency between the device and the active hybrid Information-Centric Networking clients. The device sends, to the passive hybrid Information-Centric Networking clients, the traffic using a second transport mechanism that does not guarantee the level of end-to-end latency between the device and the passive hybrid Information-Centric Networking clients.