Multicast Route Switching Based on Receiver Count

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional VPN arrangements, such as those defined by RFC 4364 and RFC 6513, are inefficient and resource-wasteful as they send multicast traffic to all provider edge elements, even if they haven't joined the multicast, leading to difficulties in tracking multicast receivers.

Innovation Solution

A network device is configured to determine the number of multicast receivers and control traffic switching between selective and inclusive routes based on bandwidth thresholds and receiver counts, using explicit tracking to avoid unnecessary traffic distribution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If an inclusive route is used to send multicast traffic to all provider edge elements, then multicast receivers can receive traffic reliably, but network resources are wasted and receiver tracking becomes difficult

Engineering Contradiction:
Improvemulticast delivery reliabilityVSAvoidnetwork resource waste
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent implements dynamic route switching between inclusive and selective routes based on real-time multicast receiver status. The system continuously monitors receiver presence and automatically transitions from inclusive route (sending to all PE elements) to selective route (sending only to active receivers) when receivers are identified, thereby adapting the traffic distribution strategy to current network conditions and eliminating waste of network resources on inactive receivers while maintaining reliable delivery to active ones

Inventive Principle:
Principle #15Dynamics

2Ease of operation

If an inclusive route is used to send multicast traffic to all provider edge elements, then multicast delivery is simplified, but receiver tracking becomes difficult and inefficient

Engineering Contradiction:
Improvemulticast delivery simplicityVSAvoidreceiver tracking difficulty
Core Design Contradiction:
Ease of operationVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements a feedback mechanism where provider edge elements send join messages back to the multicast router when they need to receive multicast traffic. This feedback allows the router to automatically identify which PE elements are actual receivers and switch from inclusive route to selective route accordingly. The feedback loop enables automatic receiver tracking without manual intervention, resolving the tracking difficulty while maintaining operational simplicity through automated control

Inventive Principle:
Principle #23Feedback

3Loss of energy

If selective route is used to send multicast traffic only to joined receivers, then network resources are conserved, but route establishment becomes more complex

Engineering Contradiction:
Improvenetwork resource efficiencyVSAvoidroute establishment complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The patent implements self-service where provider edge elements automatically initiate join messages to the multicast router when they need to receive multicast traffic. This eliminates the need for the router to manually establish selective routes or maintain complex tracking databases. The PE elements serve themselves by autonomously signaling their receiver status, which simplifies the overall system complexity while enabling efficient selective routing that conserves network resources by sending traffic only to active receivers

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10833880B2Controlled switching of multicast traffic between selective and inclusive routes based on number of multicast receivers
Publication Date: 2020.11.10 NOKIA TECHNOLOGIES OY
  • US10833880B2 patent drawing
  • US10833880B2 patent drawing
  • US10833880B2 patent drawing

AI summary

A first network device adapted for communication with one or more other network devices is configured to determine a number of receivers of a multicast, and to control switching of traffic between selective and inclusive routes for the multicast based at least in part on the determined number of receivers. For example, in some embodiments the first network device is configured to control switching of traffic between the selective and inclusive routes for the multicast by utilizing a selective route for the multicast responsive to a determination that traffic for the multicast is at or above a bandwidth threshold and the number of receivers is below an add threshold, and utilizing an inclusive route for the multicast responsive to a determination that traffic for the multicast is below the bandwidth threshold or the number of receivers is above a delete threshold.