Stateless Multicast Packet Forwarding via Encoded Headers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current communication systems face challenges in efficiently supporting multicasting of packets due to the need for maintaining stateful multicast forwarding, which is costly and unscalable.

Innovation Solution

The implementation of an apparatus with a processor and memory configured to receive packets with encoded multicast headers, which include link tuples containing link identifiers and headers for forwarding packets downstream, allowing for stateless multicasting by encoding multicast path information within the packets.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If stateful multicast forwarding is used to support multicasting of packets, then multicast communication can be established, but the system incurs high costs and poor scalability due to the need to maintain forwarding state in nodes

Engineering Contradiction:
Improvemulticast communication capabilityVSAvoidforwarding state maintenance
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the forwarding state information from the network nodes and embeds it directly into the packet headers. Specifically, the multicast path information is encoded in the packet header as the packet traverses the network, allowing nodes to forward packets based on header information rather than maintaining state in their forwarding tables. This transfers the state management burden from the network infrastructure to the packet itself.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The packet carries its own routing information in the header, enabling it to self-identify its destination and path requirements. Each node examines the packet header to determine forwarding actions without needing to query or maintain state about the packet's intended destination. The packet essentially serves its own routing needs through the information encoded in its header.

Inventive Principle:
Principle #25Self-service

2Ease of operation

If forwarding state is maintained in nodes to enable packet forwarding, then packets can be routed correctly, but security is compromised as nodes can forward packets without proper authorization

Engineering Contradiction:
Improvepacket forwarding capabilityVSAvoidunauthorized forwarding prevention
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The authorization information is extracted from the network state and embedded directly into the packet header. The header contains encoded information about the packet's origin, destination, and authorized path, which nodes verify before forwarding. This ensures that only packets with valid authorization encoded in their headers can be forwarded, preventing unauthorized routing.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The packet header contains feedback information about the packet's journey through the network, including verification data that allows nodes to confirm the packet's legitimacy. This feedback mechanism enables nodes to make informed forwarding decisions based on the packet's own information rather than relying on potentially compromised state in their forwarding tables.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12301445B2Stateless and secure packet forwarding
Publication Date: 2025.05.13 NOKIA SOLUTIONS & NETWORKS OY
  • US12301445B2 patent drawing
  • US12301445B2 patent drawing
  • US12301445B2 patent drawing

AI summary

Various example embodiments for supporting multicast are presented herein. Various example embodiments for supporting stateless multicast may be configured to support stateless multicasting of packets based on encoding of multicast path information within the packets. Various example embodiments for supporting stateless multicasting of packets based on encoding of multicast path information within the packets may be configured to use a recursive scheme of encoding the multicast path information within the packets such that the header that arrives at each node of the multicast path informs the node of the outgoing links over which the packet is to be sent and the headers to be sent on the outgoing links (e.g., each node of the multicast tree is able to recognize each of its outgoing links from the received header and send the appropriate subtree encoding down each of its outgoing links).