EVPN/BGP Signaling for Non-Ethernet Service Establishment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Ethernet Virtual Private Network (EVPN) technologies do not support non-Ethernet services like Time Division Multiplexing (TDM) and Asynchronous Transfer Mode (ATM), requiring separate protocols and configurations, leading to high service establishment costs and inflexible negotiation.
Innovation Solution
Reusing existing EVPN routing information, such as EVPN NLRI and extended communities, to negotiate and establish non-Ethernet services by indicating service types and parameters, reducing the need for additional signaling and protocol changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate protocols are used for Ethernet services and non-Ethernet services, then service functionality is supported, but service establishment costs increase and negotiation flexibility decreases
Solution Approach 1:
The patent applies universality by enabling the EVPN protocol to handle both Ethernet services and non-Ethernet services (such as TDM and ATM) through a unified control plane. The BGP extension allows the same protocol framework to negotiate and establish different service types by incorporating service type identification fields and appropriate route types, eliminating the need for separate protocol stacks for different service categories.
Solution Approach 2:
The patent uses parameter changes by extending the BGP EVPN protocol with new parameters and fields to support non-Ethernet services. Specifically, it introduces service type indication parameters in the BGP message and modifies the EVPN routing information structure to accommodate different service types, allowing the protocol to adapt its behavior based on the service being established without requiring a completely separate protocol.
2Adaptability or versatility
If separate protocols are used for Ethernet services and non-Ethernet services, then service functionality is supported, but service establishment costs increase
Solution Approach 1:
By making the EVPN protocol universal, the patent eliminates the need to deploy and maintain separate protocol stacks for Ethernet and non-Ethernet services. This reduces service establishment costs by leveraging existing EVPN infrastructure, control planes, and network device capabilities already in place for Ethernet services, thereby avoiding duplicate investment in separate protocol implementation and operation.
Solution Approach 2:
The patent merges the control planes for Ethernet services and non-Ethernet services into a unified EVPN framework. By combining these previously separate protocols into a single extended protocol, the patent reduces the overall cost of service establishment through protocol consolidation, shared control plane resources, and simplified network device configurations.
3Adaptability or versatility
If separate protocols are used for Ethernet services and non-Ethernet services, then service functionality is supported, but negotiation flexibility decreases
Solution Approach 1:
The patent introduces dynamics by enabling the EVPN protocol to adapt its negotiation process based on the service type being established. The protocol can dynamically adjust its behavior, message structure, and parameters depending on whether it is establishing an Ethernet service, TDM service, or ATM service, providing flexible and customized negotiation for each service type within a unified framework.
Solution Approach 2:
Through parameter changes, the patent enables flexible negotiation by allowing the BGP EVPN protocol to modify its parameters and fields based on the service type. The service type indication parameters allow negotiating entities to dynamically adjust the negotiation process, route types, and attribute structures to match the specific requirements of different service types, thereby maintaining high negotiation flexibility.
Data Source
Figure 1~2
Figure 3~5
Figure 6~7
AI summary
This application provides a method for establishing a non-Ethernet service and a network device. The method includes: A first network device receives a border gateway protocol BGP message sent by a second network device to establish a non-Ethernet service. In other words, in the method, the non-Ethernet service is established by using a protocol of an Ethernet service. In this way, a network device in a system can support establishment of the non-Ethernet service when only the related protocol supporting the Ethernet service is configured. Therefore, the foregoing technical solutions can reduce service establishment costs, and implement flexible establishment of the non-Ethernet service.