BIER Packet RPF Check via Target Label Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In BIER communication networks, edge nodes that do not support BIER packet forwarding face challenges in performing reverse path forwarding (RPF) checks due to the reliance on BIER header information, leading to issues with large encapsulation overheads and inefficient label usage.
Innovation Solution
A method where a first network device updates a received BIER packet to a second BIER packet that includes a target label for RPF checking, without the original BIER header, allowing edge nodes without BIER forwarding capabilities to perform RPF checks based on the target label.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If edge nodes rely on BIER header information for RPF checks, then RPF check functionality is maintained, but encapsulation overhead increases and label usage becomes inefficient
Solution Approach 1:
The patent extracts the RPF check functionality from dependence on BIER header information by introducing a dedicated target label. This label is specifically designed to trigger RPF checks at edge nodes without BIER forwarding capabilities, separating the RPF check mechanism from the BIER header structure and reducing encapsulation overhead.
Solution Approach 2:
The patent changes the parameter used for RPF checks from BIER header information to a target label. This parameter change allows edge nodes to perform RPF checks using a more efficient label-based mechanism rather than relying on the larger BIER header structure, thereby reducing encapsulation overhead while maintaining check reliability.
2Reliability
If BIER header information is used for RPF checks at edge nodes, then check functionality is preserved, but network efficiency decreases due to large encapsulation overhead
Solution Approach 1:
The patent extracts the essential RPF check trigger from the BIER header structure by implementing a dedicated target label. This extraction allows edge nodes to perform RPF checks using only the label information without processing the entire BIER header, thereby improving network efficiency while preserving check functionality.
Solution Approach 2:
Instead of having edge nodes perform RPF checks by parsing BIER header information (the conventional approach), the patent inverts the approach by having the network provide a specific target label that triggers the RPF check. This inversion simplifies the edge node processing and improves overall network efficiency.
3Reliability
If multiple labels are used to support RPF checks without BIER header, then RPF check reliability improves, but label management complexity increases
Solution Approach 1:
The patent makes the target label multi-functional by designing it to simultaneously serve as both a forwarding label and an RPF check trigger. This universality eliminates the need for separate labels for different functions, reducing label management complexity while maintaining RPF check reliability through the efficient use of a single dedicated label.
Data Source
AI summary
A packet processing method includes a first network device receiving a first Bit Index Explicit Replication (BIER) packet including a first BIER header. When the first BIER packet is a packet sent to a second network device, and in response to determining that the second network device is an edge node device in a BIER communication network and does not support BIER packet forwarding, the first network device determines a target label used for a reverse path forwarding (RPF) check, updates the first BIER packet to obtain a second BIER packet, where the second BIER packet includes the target label but does not include the first BIER header, and sends the second BIER packet to the second network device.