EVPN Host Routed Bridging With Cloud-Native Virtual Routers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional EVPN data centers face challenges in scalability and infrastructure expansion due to their monolithic network design, which is difficult to scale horizontally and accommodate varying traffic demands.
Innovation Solution
Implementing EVPN Host Routed Bridging (HRB) architecture that enables L2 and L3 connectivity directly on host servers, using cloud-native virtual routers with containerized routing protocol processes, allowing for dynamic deployment and auto-provisioning based on user intent through a Container Network Interface (CNI) software interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If EVPN data center uses monolithic network design with tightly coupled software and hardware, then network stability and reliability are improved, but scalability and ability to accommodate traffic growth deteriorate
Solution Approach 1:
The patent segments the monolithic EVPN data center into modular components: virtual network routers (VNRs) as independent software modules, physical network infrastructure as separate hardware layers, and containerized network functions. This segmentation allows each component to be scaled, updated, and managed independently, resolving the contradiction between stability (maintained through proven monolithic EVPN protocols) and scalability (achieved through modular deployment of VNRs and containers).
Solution Approach 2:
The patent introduces dynamic orchestration capabilities that allow the network architecture to adapt to changing traffic demands. VNRs can be dynamically instantiated, configured, and scaled based on real-time requirements, while maintaining the stable EVPN overlay network. This dynamic approach enables the system to preserve reliability through established protocols while achieving scalability through flexible resource allocation.
2Reliability
If EVPN data center infrastructure is physically deployed and pre-provisioned for peak capacity, then network reliability and performance are improved, but infrastructure cost and complexity increase
Solution Approach 1:
The patent implements self-service capabilities through automated orchestration systems that dynamically provision and scale VNRs based on actual traffic demands. Instead of pre-provisioning infrastructure for peak capacity, the system automatically allocates resources as needed, reducing infrastructure complexity and cost while maintaining reliable performance through on-demand resource availability.
Solution Approach 2:
The patent enables dynamic adjustment of network parameters such as VNR instantiation, container resource allocation, and bandwidth provisioning based on real-time traffic conditions. This allows the system to maintain optimal performance by adjusting parameters dynamically rather than being locked into static peak-capacity provisioning, thereby reducing overall infrastructure complexity.
3Ease of operation
If EVPN data center uses traditional VLAN-based networking, then ease of operation and management are improved, but scalability and flexibility deteriorate
Solution Approach 1:
The patent introduces VNRs as intermediary components between traditional VLAN-based networking and modern containerized applications. VNRs provide a abstraction layer that maintains the simplicity of VLAN management while enabling scalable EVPN overlay networks. This intermediary approach preserves ease of operation through familiar VLAN concepts while achieving scalability through EVPN's advanced capabilities.
Solution Approach 2:
The patent makes the network infrastructure universal by designing VNRs that can serve multiple functions: traditional VLAN bridging, EVPN overlay routing, container network functions, and dynamic service insertion. This multi-functionality allows a single infrastructure to support both simple VLAN-based operations and complex scalable EVPN deployments, resolving the contradiction between ease of operation and scalability.
4Adaptability or versatility
If EVPN data center deploys cloud-native virtual routers with containerized routing processes, then scalability and adaptability are improved, but software-hardware coupling complexity increases
Solution Approach 1:
The patent extracts the routing functionality into separate containerized VNR processes that run independently from the underlying hardware infrastructure. This extraction allows routing logic to be developed, deployed, and scaled independently from hardware constraints, achieving scalability while managing software-hardware integration complexity through clear separation of concerns and standardized interfaces.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Techniques for EVPN Host Routed Bridging (HRB) and EVPN cloud-native data center with Host Routed Bridging (HRB) are described. A host computing device of a data center includes one or more containerized user-level applications. A cloud native virtual router is configured for dynamic deployment by the data center application orchestration engine and operable in a user space of the host computing device. Processing circuitry is configured for execution of the containerized user-level applications and the cloud native virtual router. The cloud native virtual router comprises a containerized routing protocol process configured to operate as a control plane, and a data plane for the containerized router. The data plane is configured to operate an ethernet virtual private network (EVPN) encapsulation / decapsulation data path of an overlay network for communicating layer two (L2) network traffic of the containerized user applications over a switch fabric of the data center.