Multicast Replicating Node Bandwidth Reporting for Traffic Scheduling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current traffic scheduling in communication networks for concurrent unicast and multicast services is sub-optimal due to high processing requirements and complex correlation processes, especially in multi-BNG scenarios, leading to potential congestion or underutilization of resources without accurate bandwidth awareness.

Innovation Solution

Implementing a dedicated Layer 2 control mechanism where multicast replicating nodes report bandwidth usage changes to traffic scheduling nodes, using protocols like GSMP, to minimize processing requirements and ensure optimal traffic scheduling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If IGMP correlation is performed at the BNG using transparent snooping in multicast replicating nodes, then the traffic scheduling process can stay in sync with bandwidth usage, but the BNG experiences high processing requirements and high IGMP traffic load

Engineering Contradiction:
Improvetraffic scheduling synchronizationVSAvoidprocessing requirements at BNG
Core Design Contradiction:
ReliabilityVSPower

Solution Approach 1:

The patent extracts the bandwidth information reporting function from the BNG and implements it at the multicast replicating nodes. The replicating nodes now actively report bandwidth consumption to the BNG, removing the burden of IGMP message processing and correlation from the BNG while maintaining accurate traffic scheduling synchronization.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a new intermediary reporting mechanism where multicast replicating nodes act as intermediaries that actively communicate bandwidth information to the BNG. This replaces the passive IGMP correlation approach where the BNG had to intercept and process all IGMP messages, reducing the processing load at the BNG.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If IGMP correlation at BNG uses transparent snooping to determine access loop identifiers, then bandwidth information can be obtained, but the correlation process between MAC/IP addresses and loop identifiers complicates the decision process at BNG

Engineering Contradiction:
Improvebandwidth information availabilityVSAvoidcorrelation process complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

Instead of the BNG performing complex correlation of MAC and IP addresses with access loop identifiers, the patent inverts the approach by having multicast replicating nodes directly report bandwidth information to the BNG. This eliminates the need for the BNG to perform address correlation and simplifies the decision process at the BNG.

Inventive Principle:
Principle #13The other way round (Inversion)

3Adaptability or versatility

If distributed precedence and scheduling is used for QoS awareness, then fairness between service classes is achieved, but fairness amongst users within the same class cannot be established

Engineering Contradiction:
ImproveQoS awarenessVSAvoiduser fairness within class
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent applies local quality by providing differentiated bandwidth information at the user level. Each multicast replicating node reports bandwidth consumption specific to its connected users, enabling the BNG to make fine-grained scheduling decisions that ensure fairness amongst individual users within the same service class, while maintaining overall QoS awareness.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8467388B2Reporting multicast bandwidth consumption between a multicast replicating node and a traffic scheduling node
Publication Date: 2013.06.18 ALCATEL-LUCENT USA LNC
  • US8467388B2 patent drawing
  • US8467388B2 patent drawing

AI summary

A multicast replicating network node (203) according to the present invention reports to a traffic scheduling network node (205) information (231) indicative for the bandwidth consumed by multicast services or indicative for the bandwidth available for unicast services on a line coupled to the multicast replicating network node (203). The traffic scheduling network node (205) this way stays aware of the multicast bandwidth occupancy on different subscriber lines and access node uplinks without serious impact on its processing requirements.