BIER-over-IPv6 Encapsulation for Reliable Packet Recognition

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies have not effectively optimized Bit Index Explicit Replication (BIER) packets for use in Internet Protocol Version 6 (IPv6) packets, leading to issues with nodes unable to recognize Ethernet packets and causing black holes.

Innovation Solution

The method involves copying the Entropy field from the BIER packet header to the Flow Label field of an outer IPv6 packet and setting the Proto field in the BIER packet header to indicate the data packet type, while also potentially changing the Differentiated Services Code Point (DSCP) field, thereby encapsulating the BIER packet within an IPv6 packet.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If BIER packet is transmitted in Ethernet packet form, then nodes that support direct Ethernet packet recognition can process it, but nodes that cannot recognize Ethernet packets will discard it as black holes

Engineering Contradiction:
Improvepacket recognition reliabilityVSAvoidnode compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces IPv6 packet as an intermediary encapsulation layer between the BIER packet and the network infrastructure. The BIER packet is encapsulated within an IPv6 packet, which serves as a universal intermediary format that all IPv6-capable nodes can recognize and process, eliminating the black hole problem for nodes that cannot directly handle Ethernet packets.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the packet format parameter from raw Ethernet packet to IPv6 encapsulated packet. By modifying the outer packet header from Ethernet to IPv6 format, the packet becomes compatible with a broader range of nodes that support IPv6 but may not support direct Ethernet packet processing, thus improving node compatibility.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If BIER packet is encapsulated in IPv6 packet, then node compatibility is improved, but the packet structure becomes more complex

Engineering Contradiction:
Improvenode compatibilityVSAvoidpacket structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies nested encapsulation where the BIER packet is nested inside the IPv6 packet. The IPv6 packet header contains the BIER packet as its payload, creating a nested structure. This allows the simpler BIER packet format to be contained within the more versatile IPv6 packet, achieving compatibility without requiring complete redesign of the BIER protocol.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The IPv6 packet serves as a universal container that can carry multiple types of payloads, including BIER packets. By using IPv6 as the outer encapsulation layer, the system achieves multi-functionality where a single packet format can serve both as standard IPv6 traffic and as encapsulated BIER multicast traffic, simplifying the overall system architecture.

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

3Productivity

If field definition change is applied (Copying Entropy to Flow Label), then encapsulation efficiency is improved, but compatibility with nodes not supporting the change is reduced

Engineering Contradiction:
Improveencapsulation efficiencyVSAvoidprotocol compatibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic field mapping where the Entropy field from the BIER packet is dynamically copied to the Flow Label field of the IPv6 packet. This dynamic repositioning of fields allows for more efficient encapsulation and processing by leveraging the Flow Label field's capabilities for fast packet classification and routing, while maintaining the ability to adapt to different node capabilities.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the semantic meaning and position of packet fields by copying the Entropy field to the Flow Label field. This parameter change optimizes the encapsulation process by utilizing the Flow Label field's optimized processing path, improving encapsulation efficiency while the changes are applied selectively based on node capability support.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP4191966B1Method and system for processing data message and storage medium
Publication Date: 2026.03.11 ZTE CORP
  • EP4191966B1 patent drawingFigure 1~2
  • EP4191966B1 patent drawingFigure 3~4
  • EP4191966B1 patent drawingFigure 5~6

AI summary

Provided in the embodiments of the present disclosure are a method and device for processing a data packet, a storage medium, and an electronic device. The method includes: in a case where a Bit-Forwarding Ingress Router (BFIR) performs Bit Index Explicit Replication (BIER) packet encapsulation and outer Internet Protocol Version 6 (IPv6) packet encapsulation on a data packet, copying an Entropy field in a BIER packet header to a position of a Flow Label field of an outer IPv6 packet, and placing a label value allocated for Virtual Private Network (VPN) data in a position of the original Entropy field in the BIER packet header; and setting a data packet after the BIER packet header, and setting a Proto field in the BIER packet header to a corresponding value indicating a data packet type of the data packet, wherein the data packet type at least includes one of: an Internet Protocol Version 4 (IPv4) packet, an IPv6 packet, an Ethernet packet, a Multi-Protocol Label Switching (MPLS) packet and an Operation Administration and Maintenance (OAM) packet. By virtue of the described solution, the problem in the related art concerning how to optimize a BIER packet in an IPv6 packet is solved.