CN114650248A - Method and system for processing routing information and boundary router of autonomous system - Google Patents
Method and system for processing routing information and boundary router of autonomous system Download PDFInfo
- Publication number
- CN114650248A CN114650248A CN202011391341.8A CN202011391341A CN114650248A CN 114650248 A CN114650248 A CN 114650248A CN 202011391341 A CN202011391341 A CN 202011391341A CN 114650248 A CN114650248 A CN 114650248A
- Authority
- CN
- China
- Prior art keywords
- asbr
- evpn
- routing information
- information
- vpnv4
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/34—Source routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/52—Multiprotocol routers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The disclosure relates to a method and a system for processing routing information and an autonomous system boundary router, and relates to the field of communication. The method of the present disclosure comprises: a first Autonomous System Border Router (ASBR) receives first route publishing information sent by a second ASBR, wherein the first ASBR is an Ethernet Virtual Private Network (EVPN) ASBR, the second ASBR is a three-layer virtual private network (L3VPN) ASBR, and the first route publishing information comprises: VPNv4 or VPNv6unicast routing information of the devices in the L3 VPN; the first ASBR converts the VPNv4 or VPNv6unicast routing information of the equipment in the L3VPN into EVPN routing information and generates second routing release information; the first ASBR sends the second route distribution information to the EVPN so that the devices in the EVPN learn the route information of the devices in the L3 VPN.
Description
Technical Field
The present disclosure relates to the field of communications, and in particular, to a method and a system for processing routing information, and an autonomous system border router.
Background
With the application deployment of the new IP Network technology, it is well established that the Network protocol is further simplified, such as SRv6(Segment Routing IPv6) and EVPN (Ethernet Virtual Private Network) technologies in the industry, which further enhance the Network service opening capability, and get high attention of operators.
For a newly-built IP Network, a BGP (Border Gateway Protocol) EVPN (Layer 3Virtual Private Network) new technology deployment mode is adopted in a large scale, and an existing old IP Network only supports a traditional MPLS (Multi-Protocol Label Switching) BGP L3VPN technology deployment mode due to equipment capacity limitation. Therefore, new networks will exist for a long time to coexist with legacy networks.
Disclosure of Invention
The inventor finds that: because the traditional network and the new network coexist, the problem of intercommunication between networking services of the traditional network and the new network is faced, the existing old IP network adopts the traditional BGP L3VPN networking mode, and new technologies such as EVPN (evolution virtual private network) and the like cannot be upgraded due to the self limitation of equipment. The newly-built IP network can be deployed based on an EVPN new technology, has no relevant mature scheme and technical standard for the intercommunication scene of the new technology and the traditional technology, and has a three-layer service intercommunication problem.
One technical problem to be solved by the present disclosure is: how to implement interworking of a new network supporting EVPN and a legacy network supporting L3 VPN.
According to some embodiments of the present disclosure, a method for processing routing information is provided, including: a first Autonomous System Border Router (ASBR) receives first route publishing information sent by a second ASBR, wherein the first ASBR is an Ethernet Virtual Private Network (EVPN) ASBR, the second ASBR is a three-layer virtual private network (L3VPN) ASBR, and the first route publishing information comprises: VPNv4 or VPNv6unicast routing information of the devices in the L3 VPN; the first ASBR converts the VPNv4 or VPNv6unicast routing information of the equipment in the L3VPN into EVPN routing information and generates second routing release information; the first ASBR sends the second route distribution information to the EVPN so that the devices in the EVPN learn the route information of the devices in the L3 VPN.
In some embodiments, the method further comprises: the first ASBR receives third route release information sent by a Provider Edge (PE) in an EVPN, wherein the third route release information comprises: EVPN routing information of equipment in the EVPN; the first ASBR converts the EVPN routing information of the equipment in the EVPN into VPNv4 or VPNv6unicast routing information to generate fourth routing release information; and the first ASBR sends the fourth route release information to the second ASBR so that the second ASBR releases the fourth route release information in the L3 VPN.
In some embodiments, the first ASBR converting VPNv4 or VPNv6unicast routing information for the devices in the L3VPN to EVPN routing information comprises: the first ASBR converts VPNv4 or VPNv6unicast routing information of equipment in the L3VPN into EVPN routing information according to the format of VPNv4 or VPNv6unicast routing information in a network layer reachability message NLRI and the format of the EVPN routing information in the NLRI; or, the converting, by the first ASBR, the EVPN routing information of the device in the EVPN into VPNv4 or VPNv6unicast routing information includes: and the first ASBR converts the EVPN routing information of the equipment in the EVPN into VPNv4 or VPNv6unicast routing information according to the format of VPNv4 or VPNv6unicast routing information in the NLRI and the format of the EVPN routing information in the NLRI.
In some embodiments, the first ASBR converting the VPNv4 or VPNv6unicast routing information of the device in the L3VPN into the EVPN routing information according to a format of the VPNv4 or VPNv6unicast routing information in the NLRI and a format of the EVPN routing information in the NLRI comprises: the first ASBR converts a routing identifier RD corresponding to VPNv4 or VPNv6unicast routing information of equipment in the L3VPN in the NLRI into a corresponding RD of EVPN routing information in the NLRI; the first ASBR converts a label corresponding to VPNv4 or VPNv6unicast routing information of equipment in the L3VPN in the NLRI into a multiprotocol label switching (MPLS) label corresponding to EVPN routing information in the NLRI; the first ASBR converts the prefix corresponding to VPNv4 or VPNv6unicast routing information of equipment in the L3VPN in the NLRI into the IP prefix length and the IP prefix corresponding to the EVPN routing information in the NLRI; and the first ASBR fills 0 in the corresponding Ethernet segment identifier field, Ethernet label ID field and gateway IP address field of the EVPN routing information in the NLRI.
In some embodiments, the first ASBR converting EVPN routing information of the device in EVPN to VPNv4 or VPNv6unicast routing information according to a format of the VPNv4 or VPNv6unicast routing information in the NLRI and a format of the EVPN routing information in the NLRI comprises: the first ASBR deletes the Ethernet segment identifier field, the Ethernet label ID field and the gateway IP address field corresponding to the EVPN routing information of the equipment in the EVPN in the NLRI; the first ASBR converts the RD corresponding to the EVPN routing information of the equipment in the EVPN in the NLRI into the RD corresponding to the VPNv4 or VPNv6unicast routing information in the NLRI; the first ASBR converts the MPLS label corresponding to the EVPN routing information of the equipment in the EVPN in the NLRI into a label corresponding to VPNv4 or VPNv6unicast routing information in the NLRI; the first ASBR converts the IP prefix length and the IP prefix of the EVPN routing information of the equipment in the EVPN, which correspond to the NLRI, into the prefix of VPNv4 or VPNv6unicast routing information, which corresponds to the NLRI.
In some embodiments, generating the second routing post information comprises: the first ASBR inherits other attributes except the NLRI in the first route release information and the route conversion rule to generate second route release information; or, the generating the fourth routing issue information includes: and the first ASBR inherits other attributes except the NLRI in the third route release information and the route conversion rule to generate fourth route release information.
In some embodiments, the method further comprises: the first ASBR and the second ASBR establish an MP-BGP neighbor relation, so that the first ASBR supports a VPNv4 unicast address family or a VPNv6unicast address family; and the first ASBR establishes an MP-BGP neighbor relation with the PE in the EVPN, so that the first ASBR supports an EVPN address family.
In some embodiments, the method further comprises: under the condition that an end-to-end tunnel is formed between the PE in the EVPN and the PE in the L3VPN, the first ASBR does not change the next hop when generating the second route release information; and under the condition that an end-to-end tunnel cannot be formed between the PE in the EVPN and the PE in the L3VPN, the first ASBR changes the next hop into the first ASBR when generating the second route release information, and the multi-segment tunnel splicing is realized.
According to further embodiments of the present disclosure, there is provided an autonomous system border router, ASBR, wherein the ASBR is a first ASBR, comprising: a receiving module, configured to receive first route distribution information sent by a second ASBR, where the first ASBR is an ASBR of an ethernet virtual private network EVPN, the second ASBR is an ASBR of a three-layer virtual private network L3VPN, and the first route distribution information includes: VPNv4 or VPNv6unicast routing information of the devices in the L3 VPN; the conversion module is used for converting VPNv4 or VPNv6unicast routing information of equipment in the L3VPN into EVPN routing information and generating second routing issuing information; and the sending module is used for sending the second routing release information to the EVPN, so that the equipment in the EVPN learns the routing information of the equipment in the L3 VPN.
In some embodiments, the receiving module is further configured to receive third route release information sent by the provider edge PE in the EVPN, where the third route release information includes: EVPN routing information of equipment in the EVPN; the conversion module is also used for converting the EVPN routing information of the equipment in the EVPN into VPNv4 or VPNv6unicast routing information to generate fourth routing release information; the sending module is further configured to send the fourth route distribution information to the second ASBR, so that the second ASBR distributes the fourth route distribution information in the L3 VPN.
According to still further embodiments of the present disclosure, there is provided an autonomous system border router comprising: a processor; and a memory coupled to the processor for storing instructions that, when executed by the processor, cause the processor to perform a method of processing routing information as in any of the preceding embodiments.
According to still further embodiments of the present disclosure, there is provided a non-transitory computer-readable storage medium having stored thereon a computer program, wherein the program, when executed by a processor, implements the method of processing routing information of any of the foregoing embodiments.
According to still other embodiments of the present disclosure, a system for processing routing information is provided, which includes: the autonomous system border router, ASBR, of any of the preceding embodiments, as a first ASBR; the second ASBR is used for sending the first route release information; wherein the second ASBR is an ASBR of a three-layer virtual private network L3 VPN.
In some embodiments, the second ASBR is further configured to receive fourth route distribution information sent by the first ASBR; the first ASBR and the second ASBR establish an MP-BGP neighbor relation, so that the first ASBR supports VPNv4 or VPNv6unicast address families.
In the scheme of the disclosure, after receiving first route distribution information sent by a second ASBR arranged in an L3VPN, a first ASBR arranged in an EVPN converts VPNv4 or VPNv6unicast route information of a device in the L3VPN into EVPN route information, generates second route distribution information, and sends the second route distribution information to the EVPN. Due to the fact that conversion between the VPNv4 or VPNv6unicast routing information and the EVPN routing information is achieved, the device in the EVPN can learn the routing information of the device in the L3VPN, and further the device in the EVPN can send messages to the device in the L3VPN according to the routing information. The scheme disclosed by the invention can promote the application and deployment of the EVPN new technology, enhance the network evolution and flexible service expansion and provide technical support for ensuring the network evolution and the continuous service development.
Other features of the present disclosure and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 illustrates a flow diagram of a method of processing routing information of some embodiments of the present disclosure.
Fig. 2 shows a schematic diagram of a network architecture of some embodiments of the present disclosure.
Fig. 3 shows a flow diagram of a method of processing routing information according to further embodiments of the present disclosure.
Fig. 4A illustrates a schematic diagram of routing information forwarding of some embodiments of the present disclosure.
Fig. 4B illustrates a schematic diagram of routing information forwarding for further embodiments of the present disclosure.
Fig. 5 illustrates a structural schematic of an ASBR of some embodiments of the present disclosure.
Fig. 6 shows a schematic structural diagram of an ASBR of further embodiments of the present disclosure.
Fig. 7 shows a schematic structural diagram of an ASBR of further embodiments of the present disclosure.
Fig. 8 illustrates a block diagram of a processing system for routing information according to some embodiments of the present disclosure.
Detailed Description
The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
The disclosure provides a method for realizing intercommunication between BGP EVPN and traditional BGP L3VPN networks. Aiming at application scenes that an existing old IP network adopts an L3VPN deployment mode and a newly-built IP network adopts a BGP EVPN deployment mode, no related mature scheme and technical standard exist at present, the problems that networking services of a traditional network and a new network are intercommunicated exist, and the like, the method for intercommunicating the EVPN new technology deployment network and the L3VPN network of the traditional network is provided, routing mutual conductance conversion rules and functional requirements of the BGP L3VPN and the EVPN three layers are defined, EVPN new technology application deployment is promoted, and network evolution and service flexible expansion are enhanced. The following description is made with reference to fig. 1 to 3.
Fig. 1 is a flow chart of some embodiments of a method for processing routing information according to the present disclosure. As shown in fig. 1, the method of this embodiment includes: steps S102 to S106.
In step S102, a first ASBR (Autonomous System Boundary Router) receives first route distribution information sent by a second ASBR.
The first ASBR is the EVPN ASBR and the second ASBR is the L3VPN ASBR. In a BGP-based network, a device may publish, to a peer, routing information via a BGP message, i.e., via routing publish information, to the peer, which belongs to the prior art, so that the form and content of the first routing publish information may refer to the prior art, and the first routing publish information includes: the VPNv4 or VPNv6Unicast (Unicast) routing information of the devices in the L3VPN includes, for example, routing information of CE (Customer Edge) and PE (Provider Edge) in the L3 VPN.
In some embodiments, the first ASBR and the second ASBR establish an MP-BGP neighbor relationship such that the first ASBR supports either VPNv4 or VPNv6unicast address families; MP-BGP (Multi Protocol-BGP) neighbor relation is established between the first ASBR and PE in the EVPN, so that the first ASBR supports an EVPN address family. The second ASBR and PE in L3VPN establish MP-BGP neighbor relation, so that the second ASBR supports VPNv4 or VPNv6unicast address family. Since the second ASBR is an old network device and does not support the EVPN address family capability, and the first ASBR is a new network device, it is possible to use the old technology to support both the EVPN address family capability and the VPNv4 or VPNv6unicast address family capability, so that the MP-BGP neighbor between the first ASBR and the second ASBR enables the VPNv4 or VPNv6unicast address family capability. For example, as shown in fig. 2, the legacy network employs an L3VPN technology, the new network employs an EVPN technology, and network interworking is implemented between a first ASBR and a second ASBR using the L3VPN technology, where the first ASBR supports both the L3VPN technology and the EVPN technology.
In some embodiments, the L3VPN may be a 4G network and the EVPN may be a 5G network. Between the L3VPN network and the ABSR, private network routes are encapsulated in an address family of VPNv4 or VPNv6unicast (afi-1/2, safi-128), and are published by MP-BGP neighbor learning, and private network routes are encapsulated in an address family of EVPN (afi-25, safi-70), and are published by MP-BGP learning. In the new network, the equipment supports the EVPN technology, and two functions of supporting the traditional L3VPN and the EVPN need to be deployed in the first ASBR of the boundary equipment.
In step S104, the first ASBR converts the VPNv4 or VPNv6unicast routing information of the device in the L3VPN into EVPN routing information, and generates second route distribution information.
In some embodiments, the first ASBR converts VPNv4 or VPNv6unicast routing Information of the devices in the L3VPN into EVPN routing Information according to a format of the VPNv4 or VPNv6unicast routing Information in NLRI (Network Layer Reachability Information) and a format of the EVPN routing Information in NLRI. The first routing issue information includes NLRI, and as shown in table 1, the format of the VPNv4 or VPNv6unicast routing information in the NLRI includes: label field, occupying 3octets, RD (Route Identifier) field, occupying 8octets, Prefix field, and variable length.
TABLE 1
Label(3octets) |
RD(8octets) |
Prefix(variable) |
The second routing issue information includes NLRI, and as shown in table 2, the format of EVPN routing information (RT5) in NLRI includes: RD field, 8octets occupied, Ethernet Segment Identifier field, 10octets occupied, Ethernet Tag ID field, 4octets occupied, IP Prefix Length field, 1octet occupied, IP Prefix field, 4 or 16octets occupied, GW IP Address field, 4 or 16octets occupied, MPLS Label field, 3octets occupied.
TABLE 2
RD(8octets) |
Ethernet Segment Identifier(10octets) |
Ethernet Tag ID(4octets) |
IP Prefix Length(1octet) |
IP Prefix(4or 16octets) |
GW IP Address(4or 16octets) |
MPLS Label(3octets) |
As shown in table 1 and table 2, the EVPN route has a part of more information in NRLI than the VPNv4 or VPNv6unicast route, and mainly includes three fields of Ethernet Segment Identifier, Ethernet Tag ID, and GW IP Address. These three fields are not necessary, and are used as forwarding information in a specific scenario, and when the Ethernet Segment Identifier and the GW IP Address are both 0, the EVPN route next hop attribute is used as forwarding information, which are respectively referred to as:
l3EVPN over ESI: when the Ethernet Segment Identifier is not 0.
L3EVPN over GW-IP: when the Ethernet Segment Identifier is 0, GW IP Address is not 0.
L3EVPN over PE-IP: when Ethernet Segment Identifier and GW IP Address are both 0.
MPLS Label, RD, IP Prefix in EVPN route and VPNv4 or VPNv6unicast route are one-to-one corresponding.
In some embodiments, the first ASBR converts the RD corresponding to the VPNv4 or VPNv6unicast routing information of the device in the L3VPN in the NLRI to the RD corresponding to the EVPN routing information in the NLRI; converting a label corresponding to VPNv4 or VPNv6unicast routing information of equipment in the L3VPN in the NLRI into an MPLS label corresponding to EVPN routing information in the NLRI; converting prefixes, corresponding to VPNv4 or VPNv6unicast routing information, of equipment in the L3VPN in the NLRI into IP prefix lengths and IP prefixes, corresponding to EVPN routing information in the NLRI; and filling 0 in an Ethernet segment identifier field, an Ethernet label ID field and a gateway IP address field corresponding to the EVPN routing information in the NLRI. As shown in table 3, the manner in which unicast routes are converted to EVPN routes for VPNv4 or VPNv 6.
TABLE 3
In some embodiments, the first ASBR inherits other attributes and route conversion rules than the NLRI in the first route distribution information to generate the second route distribution information. Since forwarding information carried by the EVPN route is richer than that of a conventional VPNv4 or VPNv6unicast route, the switching operation necessarily has a constraint on the EVPN route, otherwise, information loss exists after switching. Currently, the L3EVPN over PE-IP + MPLS tunnel encapsulation type and VPNv4 or VPNv6unicast routing can be converted without loss in nature. Under the premise, other attributes of the route are inherited one by one after route conversion, and the receiving and sending rules of the route are inherited one by one. The first ASBR receives either VPNv4 or VPNv6unicast routes from the second ASBR and converts to EVPN routes, which are fully equivalent to receiving EVPN routes from the second ASBR.
In step S106, the first ASBR transmits the second route distribution information to the EVPN so that the device in the EVPN learns the route information of the device in the L3 VPN.
For example, the first ASBR converts the VPNv4 or VPNv6unicast route in the 4G network (L3VPN) to the EVPN route, and issues the EVPN route into the 5G network (EVPN).
The information depended on by the actual forwarding of the VPNv4 or VPNv6unicast route is a next hop attribute, and the information is iterated to a public network MPLS tunnel through a next hop address under the default condition. The EVPN route may also carry a tunnel encapsulation attribute explicitly indicating the public network tunnel type (e.g., Vxlan tunnel, MPLS tunnel, SRv6 tunnel, etc.).
In the method of the above embodiment, after receiving the first route distribution information sent by the second ASBR provided in the L3VPN, the first ASBR provided in the EVPN converts the VPNv4 or VPNv6unicast route information of the L3VPN into EVPN route information, generates the second route distribution information, and sends the second route distribution information to the EVPN. Due to the fact that conversion between the VPNv4 or VPNv6unicast routing information and the EVPN routing information is achieved, the device in the EVPN can learn the routing information of the device in the L3VPN, and further the device in the EVPN can send messages to the device in the L3VPN according to the routing information. The scheme of the embodiment can promote the application and deployment of the EVPN new technology, enhance the network evolution and the flexible service expansion, and provide technical support for ensuring the network evolution and the continuous service development.
A flow diagram of further embodiments of the disclosed method for processing routing information is described below in conjunction with fig. 3. As shown in fig. 3, the method of this embodiment includes: steps S302 to S306.
In step S302, the first ASBR receives the third route distribution information transmitted by the PE in the EVPN.
The third route distribution information includes: the EVPN routing information of the EVPN device includes, for example, routing information of the CE and PE in the EVPN. The form and content of the third route distribution information can be referred to the prior art.
In step S304, the first ASBR converts the EVPN routing information of the device in the EVPN into VPNv4 or VPNv6unicast routing information, and generates fourth routing advertisement information.
In some embodiments, the first ASBR converts EVPN routing information of the device in EVPN to VPNv4 or VPNv6unicast routing information according to a format of the VPNv4 or VPNv6unicast routing information in the NLRI and a format of the EVPN routing information in the NLRI.
In some embodiments, the first ASBR deletes the ethernet segment identifier field, the ethernet tag ID field, and the gateway IP address field corresponding to the EVPN routing information of the device in the EVPN in the NLRI; converting RD corresponding to EVPN routing information of equipment in the EVPN in NLRI into RD corresponding to VPNv4 or VPNv6unicast routing information in the NLRI; converting MPLS labels corresponding to EVPN routing information of equipment in the EVPN in NLRI into labels corresponding to VPNv4 or VPNv6unicast routing information in the NLRI; and converting the IP prefix length and the IP prefix corresponding to the EVPN routing information of the equipment in the EVPN in the NLRI into the prefix corresponding to the VPNv4 or VPNv6unicast routing information in the NLRI. As shown in table 4, the manner of converting EVPN routes to VPNv4 or VPNv6unicast routes.
TABLE 4
In some embodiments, the first ASBR inherits other attributes and route conversion rules than the NLRI in the third route distribution information to generate the fourth route distribution information. The first ASBR receives the EVPN route from the PE, and after the EVPN route is converted into the VPNV4/6 unified route, the EVPN route is completely equivalent to the VPNV4/6 unified route received from the PE.
In step S306, the first ASBR transmits the fourth routing information to the second ASBR, so that the second ASBR distributes the fourth routing information in the L3 VPN.
In some embodiments, in the case of an end-to-end tunnel formed between a PE in an EVPN and a PE in an L3VPN, the first ASBR does not change the next hop when generating the second route publication information; and under the condition that an end-to-end tunnel cannot be formed between the PE in the EVPN and the PE in the L3VPN, the first ASBR changes the next hop into the first ASBR when generating the second route release information, and the multi-segment tunnel splicing is realized.
For example, an end-to-end tunnel is formed between a PE in the EVPN and a PE in the L3VPN, and the ASBR device cannot change the VPN route next hop attribute when issuing the VPN route. If the first ASBR device issues the converted VPN route, the issuing rule of the route is completely inherited, if the L3VPN network and the EVPN network are in the same AS domain, the next hop of the issuing route is not changed by default, and if the L3VPN network and the EVPN network are not in the same AS domain, the next hop of the issuing route can be kept unchanged by configuring a policy.
For example, when an L3VPN and an EVPN are isolated in a public network layer and an end-to-end tunnel cannot be formed, when an ASBR device releases a VPN route, it needs to change a next hop attribute of the VPN route to itself, so as to implement multi-segment tunnel splicing. (of course, the multi-segment tunnel splicing can be realized by iterating to a BGP-LU routing mode without changing the next hop). If the default rule does not meet the requirement of changing the next hop, the next hop of the release route can be forcibly changed by configuring a policy. If the splicing of the multi-segment tunnels of different types needs to be supported, the first ASBR is required to depend on a configuration strategy and carry the attributes related to the new tunnel when the route is released.
In the method of the above embodiment, after receiving the third route distribution information sent by the PE in the EVPN, the first ASBR of the EVPN converts the EVPN route information of the device in the EVPN into VPNv4 or VPNv6unicast route information, generates fourth route distribution information, and sends the fourth route distribution information to the L3VPN by the second ASBR. Due to the fact that conversion between the EVPN routing information and VPNv4 or VPNv6unicast routing information is achieved, the equipment in the L3VPN can learn the routing information of the equipment in the EVPN, and further the equipment in the L3VPN can send messages to the equipment in the EVPN according to the routing information. The scheme of the embodiment can promote the application and deployment of the EVPN new technology, enhance the network evolution and the flexible service expansion, and provide technical support for ensuring the network evolution and the continuous service development.
The solution theoretically does not require any modification of the forwarding plane, and some application examples of the solution are shown in fig. 4A and 4B.
As shown in fig. 4A, nh represents the next hop (next hop), inlabel is the inner label, and outlabel is the outer label. The 4G network deploys L3VPN, the public network uses MPLS tunnel, the 5G network deploys EVPN, the public network uses MPLS tunnel, the 4G network and the 5G network are isolated, and the ASBR changes the next hop when announcing the route. After deployment in this manner, private network routing label table entries and forwarding flows on the PE device and the ASBR device are shown in fig. 4A, CE2 issues a route of 192.1.1.1, CE1 sends a service flow to 192.1.1.1, PE1 encapsulates an inner label 100 and then encapsulates an outer label to send to P, P performs outer label switching to forward to ASBR1 (equivalent to the second ASBR in the foregoing embodiment), ASBR1 terminates the outer label and changes the inner label to 101, sends to ASBR2 (equivalent to the first ASBR in the foregoing embodiment), ASBR2 changes the inner label 102 and encapsulates the outer label, and sends to PE2, and PE2 removes the label and sends the service flow to CE 2.
As shown in fig. 4B, the 4G network deploys L3VPN, the public network uses MPLS tunnel, the 5G network deploys EVPN, the public network uses MPLS tunnel, the 4G network and the 5G network are not isolated, and the ASBR does not change the next hop when advertising the route. After the deployment according to the mode, the PE equipment has private network routing and label table items, and only the control surface on the middle ASBR equipment has the private network routing table. When the traffic is forwarded in the public network, the label of the inner layer private network is not changed, and the traffic forwarding is realized through the label exchange of the outer layer public network. CE2 issues 192.1.1.1 routes, CE1 sends traffic flows to 192.1.1.1, PE1 encapsulates inner label 102 and encapsulates tunnel label to send to P, P forwards to ASBR1 (equivalent to the second ASBR of the previous embodiment), ASBR1 forwards information to ASBR2 (equivalent to the first ASBR of the previous embodiment), ASBR2 forwards to PE2, and PE2 de-labels sends traffic flows to CE 2.
The present disclosure also provides an autonomous system border router, described below in conjunction with fig. 5.
Fig. 5 is a block diagram of some embodiments of autonomous system border routers according to the present disclosure. As shown in fig. 5, ASBR50 of this embodiment includes, as a first ASBR: a receiving module 510, a converting module 520, and a transmitting module 530.
A receiving module 510, configured to receive first route distribution information sent by a second ASBR, where the first ASBR is an ASBR of an ethernet virtual private network EVPN, and the second ASBR is an ASBR of a three-layer virtual private network L3VPN, and the first route distribution information includes: VPNv4 or VPNv6 of devices in the L3VPN unicast routing information.
A converting module 520, configured to convert the VPNv4 or VPNv6unicast routing information of the device in the L3VPN into EVPN routing information, and generate second routing issue information.
A sending module 530, configured to send the second routing issue information to the EVPN, so that the device in the EVPN learns the routing information of the device in the L3 VPN.
In some embodiments, the receiving module 510 is further configured to receive third routing release information sent by the provider edge PE in the EVPN, where the third routing release information includes: EVPN routing information of equipment in the EVPN; the conversion module 520 is further configured to convert EVPN routing information of the device in the EVPN into VPNv4 or VPNv6unicast routing information, and generate fourth routing issue information; the sending module 530 is further configured to send the fourth route distribution information to the second ASBR, so that the second ASBR distributes the fourth route distribution information in the L3 VPN.
In some embodiments, the conversion module 520 is configured to convert VPNv4 or VPNv6unicast routing information for a device in the L3VPN into EVPN routing information according to a format of the VPNv4 or VPNv6unicast routing information in the network layer reachability message NLRI and a format of the EVPN routing information in the NLRI. Or, the converting module 520 is configured to convert the EVPN routing information of the device in the EVPN into the VPNv4 or VPNv6unicast routing information according to the format of the VPNv4 or VPNv6unicast routing information in the NLRI and the format of the EVPN routing information in the NLRI.
In some embodiments, the conversion module 520 is configured to convert the route identifier RD corresponding to the VPNv4 or VPNv6unicast routing information of the device in the L3VPN in the NLRI into the RD corresponding to the EVPN routing information in the NLRI; converting a label corresponding to VPNv4 or VPNv6unicast routing information of equipment in the L3VPN in NLRI into a multiprotocol label switching (MPLS) label corresponding to EVPN routing information in the NLRI; converting prefixes, corresponding to VPNv4 or VPNv6unicast routing information, of equipment in the L3VPN in the NLRI into IP prefix lengths and IP prefixes, corresponding to EVPN routing information in the NLRI; and filling 0 in an Ethernet segment identifier field, an Ethernet label ID field and a gateway IP address field corresponding to the EVPN routing information in the NLRI.
In some embodiments, the conversion module 520 is configured to delete the ethernet segment identifier field, the ethernet tag ID field, and the gateway IP address field corresponding to the EVPN routing information of the device in the EVPN in the NLRI; converting RD corresponding to EVPN routing information of equipment in the EVPN in the NLRI into RD corresponding to VPNv4 or VPNv6unicast routing information in the NLRI; converting MPLS labels corresponding to EVPN routing information of equipment in the EVPN in the NLRI into labels corresponding to VPNv4 or VPNv6unicast routing information in the NLRI; and converting the IP prefix length and the IP prefix corresponding to the EVPN routing information of the equipment in the EVPN in the NLRI into the prefix corresponding to the VPNv4 or VPNv6unicast routing information in the NLRI.
In some embodiments, the conversion module 520 is further configured to inherit other attributes and routing conversion rules except the NLRI in the first routing publishing information to generate second routing publishing information; alternatively, the conversion module 520 is further configured to inherit other attributes and routing conversion rules besides the NLRI in the third routing distribution information to generate fourth routing distribution information.
In some embodiments, the first ASBR and the second ASBR establish an MP-BGP neighbor relationship such that the first ASBR supports either VPNv4 or VPNv6unicast address families; and the first ASBR and the PE in the EVPN establish an MP-BGP neighbor relation, so that the first ASBR supports an EVPN address family.
In some embodiments, the conversion module 520 is further configured to, in a case where an end-to-end tunnel is formed between a PE in the EVPN and a PE in the L3VPN, not change a next hop when generating the second route publishing information; and under the condition that an end-to-end tunnel cannot be formed between the PE in the EVPN and the PE in the L3VPN, changing the next hop into a first ASBR when generating second route release information, and realizing multi-segment tunnel splicing.
Autonomous system border routers in embodiments of the present disclosure may be implemented by various computing devices or computer systems, as described below in conjunction with fig. 6 and 7.
Fig. 6 is a block diagram of some embodiments of autonomous system border routers according to the present disclosure. As shown in fig. 6, the autonomous system border router 60 of this embodiment includes: a memory 610 and a processor 620 coupled to the memory 610, the processor 620 being configured to perform a method of processing routing information in any of the embodiments of the present disclosure based on instructions stored in the memory 610.
Fig. 7 is a block diagram of alternate embodiments of an autonomous system border router according to the present disclosure. As shown in fig. 7, the autonomous system border router 70 of this embodiment includes: memory 710 and processor 720 are similar to memory 610 and processor 620, respectively. Input/output interfaces 730, network interfaces 740, storage interfaces 750, and the like may also be included. These interfaces 730, 740, 750, as well as the memory 710 and the processor 720, may be connected, for example, by a bus 760. The input/output interface 730 provides a connection interface for input/output devices such as a display, a mouse, a keyboard, and a touch screen. The network interface 740 provides a connection interface for various networking devices, such as a database server or a cloud storage server. The storage interface 750 provides a connection interface for external storage devices such as an SD card and a usb disk.
The present disclosure also provides a system for processing routing information, which is described below with reference to fig. 8.
Fig. 8 is a block diagram of some embodiments of a processing system for routing information according to the present disclosure. As shown in fig. 8, the system 8 of this embodiment includes: ASBR50/60/70 of any of the foregoing embodiments as first ASBR 50/60/70; and the second ASBR81 is used for sending the first route release information.
The second ASBR82 is further configured to receive fourth routing information sent by the first ASBR. For example, the first ASBR and the second ASBR establish an MP-BGP neighbor relationship such that the first ASBR supports either VPNv4 or VPNv6unicast address families.
In some embodiments, system 8 further comprises: EVPN and L3 VPN. The EVPN may include, in addition to the first ASBR: the first PE82, the first CE83, and the like may include, in addition to the second ASBR, in the L3 VPN: a second PE84, a second CE85, etc.
As will be appreciated by one skilled in the art, embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only exemplary of the present disclosure and is not intended to limit the present disclosure, so that any modification, equivalent replacement, or improvement made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.
Claims (14)
1. A processing method of routing information comprises the following steps:
a first Autonomous System Border Router (ASBR) receives first route distribution information sent by a second ASBR, wherein the first ASBR is an Ethernet Virtual Private Network (EVPN) ASBR, the second ASBR is a three-layer virtual private network (L3VPN) ASBR, and the first route distribution information comprises: VPNv4 or VPNv6unicast routing information of the equipment in the L3 VPN;
the first ASBR converts the VPNv4 or VPNv6unicast routing information of the equipment in the L3VPN into EVPN routing information and generates second routing release information;
and the first ASBR sends the second routing release information to the EVPN, so that the equipment in the EVPN learns the routing information of the equipment in the L3 VPN.
2. The method for processing routing information according to claim 1, further comprising:
the first ASBR receives third route release information sent by an operator edge device PE in an EVPN, wherein the third route release information comprises: EVPN routing information of equipment in the EVPN;
the first ASBR converts EVPN routing information of the equipment in the EVPN into VPNv4 or VPNv6unicast routing information and generates fourth routing release information;
and the first ASBR sends the fourth route release information to the second ASBR so that the second ASBR can release the fourth route release information in the L3 VPN.
3. The method of processing routing information of claim 2, wherein the first ASBR converting VPNv4 or VPNv6unicast routing information of the L3VPN device into EVPN routing information comprises:
the first ASBR converts VPNv4 or VPNv6unicast routing information of equipment in the L3VPN into EVPN routing information according to a format of VPNv4 or VPNv6unicast routing information in a network layer reachability message NLRI and a format of the EVPN routing information in the NLRI;
or, the converting, by the first ASBR, the EVPN routing information of the device in the EVPN into VPNv4 or VPNv6unicast routing information includes:
and the first ASBR converts the EVPN routing information of the equipment in the EVPN into VPNv4 or VPNv6unicast routing information according to the format of VPNv4 or VPNv6unicast routing information in the NLRI and the format of the EVPN routing information in the NLRI.
4. The method of processing routing information of claim 3, wherein the first ASBR converting VPNv4 or VPNv6unicast routing information of the L3VPN device into EVPN routing information according to a format of VPNv4 or VPNv6unicast routing information in NLRI and a format of EVPN routing information in NLRI comprises:
the first ASBR converts a routing identifier RD corresponding to VPNv4 or VPNv6unicast routing information of equipment in the L3VPN in NLRI into a RD corresponding to EVPN routing information in NLRI;
the first ASBR converts a label corresponding to VPNv4 or VPNv6unicast routing information of equipment in the L3VPN in NLRI into a multiprotocol label switching (MPLS) label corresponding to EVPN routing information in the NLRI;
the first ASBR converts prefixes, corresponding to VPNv4 or VPNv6unicast routing information of equipment in the L3VPN, in the NLRI into IP prefix lengths and IP prefixes, corresponding to EVPN routing information in the NLRI, of the first ASBR;
and the first ASBR fills 0 in an Ethernet segment identifier field, an Ethernet label ID field and a gateway IP address field corresponding to the EVPN routing information in the NLRI.
5. The method of processing routing information of claim 3, wherein the first ASBR converting EVPN routing information of devices in the EVPN into VPNv4 or VPNv6unicast routing information according to a format of VPNv4 or VPNv6unicast routing information in NLRI and a format of EVPN routing information in NLRI comprises:
the first ASBR deletes the Ethernet segment identifier field, the Ethernet label ID field and the gateway IP address field corresponding to the EVPN routing information of the equipment in the EVPN in the NLRI;
the first ASBR converts the RD corresponding to the EVPN routing information of the equipment in the EVPN in the NLRI into the RD corresponding to VPNv4 or VPNv6unicast routing information in the NLRI;
the first ASBR converts the MPLS label corresponding to the EVPN routing information of the equipment in the EVPN in the NLRI into the label corresponding to the VPNv4 or VPNv6unicast routing information in the NLRI;
and the first ASBR converts the IP prefix length and the IP prefix, corresponding to the EVPN routing information of the equipment in the EVPN, in the NLRI into the prefix, corresponding to the VPNv4 or VPNv6unicast routing information in the NLRI.
6. The method for processing routing information of claim 1, wherein the generating the second routing issue information comprises:
the first ASBR inherits other attributes except the NLRI in the first route release information and a route conversion rule to generate second route release information;
or, the generating the fourth routing issue information includes:
and the first ASBR inherits other attributes except the NLRI in the third route release information and the route conversion rule to generate fourth route release information.
7. The method for processing routing information according to claim 1, further comprising:
the first ASBR and the second ASBR establish an MP-BGP neighbor relation, so that the first ASBR supports VPNv4 or VPNv6unicast address families;
and establishing an MP-BGP neighbor relation between the first ASBR and the PE in the EVPN to ensure that the first ASBR supports an EVPN address family.
8. The method for processing routing information according to claim 1, further comprising:
under the condition that an end-to-end tunnel is formed between the PE in the EVPN and the PE in the L3VPN, the first ASBR does not change the next hop when generating the second route release information;
and under the condition that an end-to-end tunnel cannot be formed between the PE in the EVPN and the PE in the L3VPN, the first ASBR changes the next hop into the first ASBR when generating second route release information, and the multi-section tunnel splicing is realized.
9. An autonomous system border router, ASBR, wherein the ASBR, as a first ASBR, comprises:
a receiving module, configured to receive first route distribution information sent by a second ASBR, where the first ASBR is an ethernet virtual private network EVPN ASBR, the second ASBR is a three-layer virtual private network L3VPN ASBR, and the first route distribution information includes: VPNv4 or VPNv6unicast routing information of the devices in the L3 VPN;
a conversion module, configured to convert VPNv4 or VPNv6unicast routing information of the device in the L3VPN into EVPN routing information, and generate second route publishing information;
and the sending module is used for sending the second routing release information to the EVPN so that the equipment in the EVPN can learn the routing information of the equipment in the L3 VPN.
10. The autonomous system border router of claim 9, wherein,
the receiving module is further configured to receive third route release information sent by a provider edge PE in the EVPN, where the third route release information includes: EVPN routing information of equipment in the EVPN;
the conversion module is further configured to convert EVPN routing information of the device in the EVPN into VPNv4 or VPNv6unicast routing information, and generate fourth routing issue information;
the sending module is further configured to send the fourth route distribution information to the second ASBR, so that the second ASBR distributes the fourth route distribution information in an L3 VPN.
11. An autonomous system border router comprising:
a processor; and
a memory coupled to the processor for storing instructions that, when executed by the processor, cause the processor to perform the method of processing routing information of any of claims 1-8.
12. A non-transitory computer readable storage medium having stored thereon a computer program, wherein the program when executed by a processor implements the steps of the method of any one of claims 1-8.
13. A system for processing routing information, comprising: the autonomous system border router, ASBR, of any of claims 9-11 as a first ASBR; and
the second ASBR is used for sending the first route release information;
wherein the second ASBR is an ASBR of a three-layer virtual private network L3 VPN.
14. The system for processing routing information of claim 13,
the second ASBR is further configured to receive fourth route release information sent by the first ASBR;
the first ASBR and the second ASBR establish an MP-BGP neighbor relation, so that the first ASBR supports VPNv4 or VPNv6unicast address families.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202011391341.8A CN114650248B (en) | 2020-12-02 | 2020-12-02 | Processing method and system of routing information and autonomous system boundary router |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202011391341.8A CN114650248B (en) | 2020-12-02 | 2020-12-02 | Processing method and system of routing information and autonomous system boundary router |
Publications (2)
Publication Number | Publication Date |
---|---|
CN114650248A true CN114650248A (en) | 2022-06-21 |
CN114650248B CN114650248B (en) | 2023-07-18 |
Family
ID=81990456
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202011391341.8A Active CN114650248B (en) | 2020-12-02 | 2020-12-02 | Processing method and system of routing information and autonomous system boundary router |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN114650248B (en) |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7274704B1 (en) * | 2000-07-14 | 2007-09-25 | Nortel Networks Limited | Piggybacking VPN information in BGP for network based VPN architectures |
WO2008011818A1 (en) * | 2006-07-14 | 2008-01-31 | Huawei Technologies Co., Ltd. | Method of realizing hierarchy-virtual private lan service and network system |
CN101617305A (en) * | 2007-01-17 | 2009-12-30 | 北方电讯网络有限公司 | Use is based on the border gateway protocol procedures tunnel, that be used for MPLS and layer 2 VPN of Ethernet |
WO2013139270A1 (en) * | 2012-03-23 | 2013-09-26 | 华为技术有限公司 | Method, device, and system for implementing layer3 virtual private network |
CN104734929A (en) * | 2013-12-18 | 2015-06-24 | 华为技术有限公司 | Method and device for routing diffusion |
WO2018109536A1 (en) * | 2016-12-17 | 2018-06-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for monitoring virtual extensible local area network (vxlan) tunnel with border gateway protocol (bgp)-ethernet virtual private network (evpn) infrastructure |
CN110830352A (en) * | 2018-08-07 | 2020-02-21 | 中兴通讯股份有限公司 | Method and device for realizing VPN cross-domain and boundary node |
-
2020
- 2020-12-02 CN CN202011391341.8A patent/CN114650248B/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7274704B1 (en) * | 2000-07-14 | 2007-09-25 | Nortel Networks Limited | Piggybacking VPN information in BGP for network based VPN architectures |
WO2008011818A1 (en) * | 2006-07-14 | 2008-01-31 | Huawei Technologies Co., Ltd. | Method of realizing hierarchy-virtual private lan service and network system |
CN101617305A (en) * | 2007-01-17 | 2009-12-30 | 北方电讯网络有限公司 | Use is based on the border gateway protocol procedures tunnel, that be used for MPLS and layer 2 VPN of Ethernet |
WO2013139270A1 (en) * | 2012-03-23 | 2013-09-26 | 华为技术有限公司 | Method, device, and system for implementing layer3 virtual private network |
CN104734929A (en) * | 2013-12-18 | 2015-06-24 | 华为技术有限公司 | Method and device for routing diffusion |
WO2018109536A1 (en) * | 2016-12-17 | 2018-06-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for monitoring virtual extensible local area network (vxlan) tunnel with border gateway protocol (bgp)-ethernet virtual private network (evpn) infrastructure |
CN110830352A (en) * | 2018-08-07 | 2020-02-21 | 中兴通讯股份有限公司 | Method and device for realizing VPN cross-domain and boundary node |
Non-Patent Citations (3)
Title |
---|
A. SAJASSI; K. THIRUVENKATASAMY; S. THORIA;CISCO;A. GUPTA;VMWARE;L. JALIL; VERIZON;: "Seamless Multicast Interoperability between EVPN and MVPN PEs\n draft-ietf-bess-evpn-mvpn-seamless-interop-01", IETF * |
S. GRINGERI;J. WHITTAKER; VERIZON;C. SCHMUTZER, ED.;P. BRISSETTE; CISCO SYSTEMS, INC.;: "Private Line Emulation VPWS Signalling\ndraft-schmutzer-bess-ple-vpws-signalling-00", IETF * |
董玲,黄杨,徐塞虹: "BGP/MPLS VPN实现细节探讨", 计算机工程与应用 * |
Also Published As
Publication number | Publication date |
---|---|
CN114650248B (en) | 2023-07-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110784411B (en) | Method, device and system for establishing BIER forwarding table item | |
CN111147383B (en) | Message forwarding method, message sending device and message receiving device | |
CN111510379B (en) | EVPN message processing method, device and system | |
US8068442B1 (en) | Spanning tree protocol synchronization within virtual private networks | |
CN108574630B (en) | EVPN message processing method, device and system | |
CN112511444B (en) | Multicast traffic transmission method, device, communication node and storage medium | |
CN101505227B (en) | Method, device and system for implementing point to multi-point pseudowire | |
CN110324226A (en) | Improve the aliasing behavior of more host site flows in ether Virtual Private Network network | |
CN111670565B (en) | Method, equipment and system for controlling routing iteration | |
EP3148131B1 (en) | Address information publishing method and apparatus | |
WO2018032961A1 (en) | Information management method, apparatus and system | |
WO2018032962A1 (en) | Method, device and system for information synchronization | |
US20100118882A1 (en) | Method, Apparatus, and System For Packet Transmission | |
CN104518940A (en) | Communication method and device for NVO3 (network virtualization over layer 3) network and MPLS (multi-protocol label switching) network | |
CN112422398B (en) | Message transmission method and communication device | |
US11929923B2 (en) | Packet transmission method and apparatus | |
WO2020098611A1 (en) | Method and apparatus for acquiring routing information | |
CN115865769A (en) | Message processing method, network equipment and system | |
WO2023274083A1 (en) | Route publishing method and apparatus, packet forwarding method and apparatus, device, and storage medium | |
CN113904981B (en) | Routing information processing method and device, electronic equipment and storage medium | |
CN112910771B (en) | Connection establishment method, device, equipment and storage medium | |
CN112311645A (en) | Method, system and first GW for realizing DCI three-layer communication | |
CN114650248B (en) | Processing method and system of routing information and autonomous system boundary router | |
WO2022116615A1 (en) | Message transmission method, method for acquiring correspondence, and apparatus and system | |
CN114827057B (en) | Communication method and communication system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |