Source Routing Multicast Packets via Embedded State Headers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing digital communication networks face inefficiencies in multicast routing, particularly in large service provider backbones, due to the overhead of maintaining separate multicast state entries for each source device and the tradeoff between routing efficiency and state information management, which affects bandwidth and routing optimality.

Innovation Solution

The solution involves including part or all multicast state entries in data packets instead of storing them in forwarding devices, allowing network devices to locally maintain forwarding state information and reduce the need for extensive multicast state management in the network core, thereby optimizing routing and bandwidth usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If multicast state entries are stored in forwarding devices, then routing decisions can be made locally, but the overhead of maintaining multicast state entries increases significantly

Engineering Contradiction:
Improvelocal routing decision capabilityVSAvoidmulticast state management overhead
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts multicast state information from forwarding devices and embeds it directly into data packets. This allows routing decisions to be made based on packet-contained state information rather than device-stored state, reducing the multicast state management overhead in forwarding devices while preserving local routing decision capability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The data packet serves as an intermediary carrier that transports multicast state information through the network. Instead of forwarding devices maintaining state, the state travels with the data packets themselves, allowing devices to make routing decisions based on the embedded state information without bearing the burden of state management.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If separate multicast state entries are maintained for each source device, then routing optimality is improved, but bandwidth efficiency deteriorates due to increased state information

Engineering Contradiction:
Improverouting optimalityVSAvoidstate information volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges multicast state information for multiple source devices into a unified format that travels within data packets. This consolidation reduces the total volume of state information needed while preserving the ability to make optimal routing decisions for each source by embedding source-specific state within the packet structure.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent changes the representation parameters of multicast state information by encoding it compactly within packet headers rather than maintaining separate device-state structures. This parameter transformation reduces the quantity of state information while maintaining the granularity needed for source-specific routing optimality.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If extensive multicast state information is managed in the network core, then routing accuracy is improved, but network overhead increases

Engineering Contradiction:
Improverouting accuracyVSAvoidnetwork overhead
Core Design Contradiction:
Measurement precisionVSLoss of energy

Solution Approach 1:

The patent inverts the traditional approach by not managing multicast state in the network core, but instead embedding it directly in data packets that traverse the network. This inversion shifts the state management burden from core devices to the packet stream itself, maintaining routing accuracy through packet-contained state while dramatically reducing network overhead.

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

Data Source

PatentUS9237025B2Source routing in multicast transmissions
Publication Date: 2016.01.12 VERIZON PATENT & LICENSING INC
  • US9237025B2 patent drawing
  • US9237025B2 patent drawing
  • US9237025B2 patent drawing

AI summary

The subject technology provides configurations for receiving, at a first network device, a multicast packet of a multicast transmission from a multicast source. A header is inserted including one or more fields of information for a multicast distribution tree into the multicast packet in which the fields of information include a root level node field indicating a root node of the multicast distribution tree and one or more second level fields indicating one or more child nodes of the root node of the multicast distribution tree. In one example, the fields of information are not duplicative of routing information, stored by the first network device, corresponding to the one or more child nodes. The subject technology then forwards the multicast packet including the inserted header to respective network devices corresponding to the one or more child nodes based on the one or more fields of information from the inserted header.