BIER OAM Detection via IP Encapsulation for BIERv6
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing BIER OAM detection methods are not applicable to all BIER encapsulation scenarios, particularly in BIERv6 encapsulation where the BIER OAM packet is not encapsulated, leading to limitations in identifying the BIER OAM packet and implementing detection.
Innovation Solution
The proposed method encapsulates the BIER OAM packet or uses an original BIER OAM packet, allowing for IP or UDP encapsulation, which enables detection in various BIER encapsulation scenarios by including a bit string in the packet header to identify the BFERs and facilitate detection request and reply packets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If BIER OAM packet is not encapsulated (original format), then the packet structure is simple, but the detection cannot be implemented in BIER encapsulation scenarios
Solution Approach 1:
The BIER OAM packet is nested within an IP or UDP encapsulation structure. The original BIER OAM packet is placed inside an IP header (IPv4 or IPv6) and optionally within a UDP header, creating a nested packet structure that enables the packet to be properly routed and identified in BIER encapsulation scenarios while preserving the original BIER OAM functionality
Solution Approach 2:
An IP header (and optionally UDP header) is introduced as an intermediary structure between the outer BIER header and the inner BIER OAM packet. This intermediary encapsulation layer provides the necessary addressing and protocol identification capabilities to enable detection in BIER encapsulation scenarios without modifying the original BIER OAM packet format
2Reliability
If BIER OAM packet is encapsulated in IP/UDP, then detection can be implemented in various BIER scenarios, but the packet header becomes more complex
Solution Approach 1:
The IP encapsulation structure serves multiple functions simultaneously: it provides network layer addressing for routing, enables protocol identification through the IP protocol field, supports UDP port-based identification when applicable, and maintains compatibility with existing IP network infrastructure. This multi-functionality enables reliable detection across diverse BIER encapsulation scenarios using a standardized approach
3Measurement precision
If bit string is included in packet header to identify BFERs, then detection accuracy is improved, but the packet header size increases
Solution Approach 1:
The bit string identification mechanism is extracted from the BIER header and placed within the IP/UDP encapsulation structure. This separation allows the bit string to be processed as part of the IP options or UDP data field, enabling precise BFER identification while managing header size through efficient bit-level encoding rather than requiring separate identification fields
Data Source
AI summary
A bit index explicit replication (BIER) operations, administration, and maintenance (OAM) detection method includes a bit forwarding ingress router (BFIR) obtaining a detection request packet based on a first BIER OAM packet, and sending the detection request packet to at least one bit forwarding egress router BFER. The detection request packet includes a first packet and a first packet header. The first packet is a packet obtained by encapsulating the first BIER OAM packet. The first packet header includes a bit string, and the bit string indicates the at least one bit forwarding egress router BFER that is to be measured.