EVPN Packet Control via Extended Flowspec NLRI
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Flowspec technology lacks the ability to identify and control Ethernet Virtual Private Network (EVPN) type traffic, limiting its application in future network scenarios.
Innovation Solution
The solution involves redesigning the Flowspec NLRI to include specific match fields and traffic control actions for EVPN type traffic, using a TLV structure to encapsulate traffic matches and actions, and defining match priorities to identify and control EVPN packets effectively.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional Flowspec technology is used, then network layer reachability information can be controlled through BGP message passing, but EVPN type traffic cannot be identified or controlled
Solution Approach 1:
The patent extends the Flowspec NLRI data structure by adding new parameters specifically for EVPN traffic. It introduces EVPN-specific match fields (outer/inner destination MAC addresses, EVPN instance ID, VLAN ID) and action fields (redirect to EVPN instance, swap/pop/insert EVPN label) to the existing BGP Flowspec framework, enabling the system to identify and control EVPN traffic while maintaining backward compatibility with traditional Flowspec functionality
Solution Approach 2:
The patent segments the Flowspec NLRI structure into distinct components for different traffic types. It creates separate match fields and action fields specifically for EVPN traffic (outer MAC, inner MAC, EVPN instance, VLAN) that can be independently configured and matched, allowing precise EVPN traffic control without affecting other traffic types controlled by traditional Flowspec
2Adaptability or versatility
If Flowspec NLRI is extended to support EVPN traffic control, then device-side traffic control for EVPN packets can be realized, but the complexity of the data structure increases
Solution Approach 1:
The patent designs the extended Flowspec NLRI structure to serve multiple functions simultaneously. The same extended data structure can match and control different types of traffic (traditional IP traffic, EVPN traffic with outer/inner MAC addresses, VLAN-tagged traffic) using a unified framework, reducing the need for separate complex control mechanisms for each traffic type
Solution Approach 2:
The patent implements a nested structure where EVPN-specific parameters (inner destination MAC, outer destination MAC, EVPN instance ID, VLAN ID) are organized hierarchically within the Flowspec NLRI framework. This nested organization allows the system to handle both traditional and EVPN traffic through a single unified structure, managing complexity through hierarchical arrangement rather than separate parallel structures
3Measurement precision
If match fields for EVPN traffic are added to Flowspec NLRI, then EVPN packets can be accurately identified, but the processing overhead increases
Solution Approach 1:
The patent performs preliminary classification by adding an EVPN instance ID match field that can be used to pre-identify EVPN traffic before deeper inspection of MAC addresses and VLAN tags. This preliminary matching allows the system to quickly route EVPN packets through appropriate processing paths, reducing the average processing overhead while maintaining high identification accuracy for all packet types
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
The present application provides a packet transmission method and apparatus for EVPN, a device, and a medium. The method is applied to a routing device and includes: obtaining (S102) at least one piece of flow specification network layer reachability information (Flowspec NLRI), wherein each Flowspec NLRI contains a matching field and a flow control action field specifically configured for an EVPN type flow; matching (S104), after receiving a target packet, the target packet with the matching field of the EVPN type traffic corresponding to the at least one piece of Flowspec NLRI, and determining target Flowspec NLRI; and determining (S106), on the basis of a traffic control action field corresponding to the target Flowspec NLRI, a target port corresponding to the target packet, and sending the target packet through the target port.