Unicast RTP Repair for Multicast Stream Joining

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The Real-time Transport Protocol (RTP) and its related standards face limitations when used for unicast repair of multicast media streams and quickly switching among different multicast media streams, particularly in Internet Protocol (IP) media transmissions, such as streaming video, as they cannot efficiently perform unicast repair or rapidly switch streams without data loss.

Innovation Solution

A unicast repair scheme for RTP multicast streams is developed, where a retransmission system caches and retransmits media packets, using Negative ACKnowledgment (NACK) packets to identify lost packets and send unicast media repair packets, and employs IP anycast addressing for adaptive routing and load sharing, allowing for high availability and scalability in media stream repair and fast channel joining.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If RTP protocol is used for multicast media stream transmission, then media streaming capability is provided, but unicast repair of lost packets and fast switching among different multicast streams cannot be performed efficiently

Engineering Contradiction:
Improvemedia stream delivery reliabilityVSAvoidstream repair and switching capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system segments media stream handling into two independent paths: multicast distribution for efficient delivery and unicast repair for reliability. The retransmission server separates the functions of receiving multicast streams and providing repair packets to clients, allowing each function to be optimized independently.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The retransmission server acts as an intermediary between the multicast stream source and clients. It receives multicast streams, caches repair packets, and provides unicast repair packets to clients upon request, enabling both multicast efficiency and unicast reliability without requiring the original RTP protocol to be modified.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If a retransmission system is implemented to provide unicast repair, then stream repair capability is improved, but system complexity and workload increase

Engineering Contradiction:
Improvepacket loss recoveryVSAvoidretransmission system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The retransmission server performs preliminary actions by caching repair packets in advance while receiving the multicast stream. This preparation work is done proactively before clients need repair packets, reducing the complexity of real-time packet recovery operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Clients autonomously detect packet loss and send NACK requests for repair without requiring complex server-side error detection mechanisms. The server simply responds to client requests with the appropriate repair packets, making the system self-service oriented and reducing overall complexity.

Inventive Principle:
Principle #25Self-service

3Speed

If multiple multicast streams need to be switched among quickly, then stream switching capability is required, but data loss occurs during switching

Engineering Contradiction:
Improvestream switching speedVSAvoiddata loss during switching
Core Design Contradiction:
SpeedVSLoss of information

Solution Approach 1:

The retransmission server caches repair packets from multiple different multicast streams in advance. When a client needs to switch streams, the repair packets for the new stream are already available in the cache, enabling fast switching without data loss.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The retransmission server provides universal repair service for multiple different multicast streams through a single system. It can handle repair requests for any cached stream, eliminating the need for separate repair systems for each stream and enabling efficient switching.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Measurement precision

If unicast repair packets are sent to each client, then packet recovery accuracy is improved, but network bandwidth and server workload increase

Engineering Contradiction:
Improvepacket recovery accuracyVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The system sends unicast repair packets only when and where needed, based on client-specific loss patterns indicated by NACK requests. This partial action approach sends exactly the right amount of repair data to each client without unnecessary bandwidth consumption.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9083585B2Retransmission-based stream repair and stream join
Publication Date: 2015.07.14 CISCO TECHNOLOGY INC
  • US9083585B2 patent drawing
  • US9083585B2 patent drawing
  • US9083585B2 patent drawing

AI summary

The Real-time Transport Protocol (RTP) and its related standards define a retransmission packet format and a way to give feedback via Negative ACKnowledge (NACK) packets for data that has been lost. In one embodiment, a unicast RTP repair session is associated with a main Source Specific Multicast (SSM) multicast session. Real-time Transport Control Protocol (RTCP) NACK packets are then used for feedback to a SSM feedback target address. This dynamically instantiates unicast RTP repair for multicast sessions. The repair scheme can be used for repairing multicast channels or joining new multicast channels. In another embodiment, a media transmission device shares an IP address with one or more other media transmission devices. The shared IP address can also be used to route multiple identical multicast media streams to different media stream receivers.