A system and method for realizing coordinated disaster recovery of IPv6 Internet dedicated lines

Abstract

The present application provides a system and method for implementing coordinated disaster recovery for an IPv6 Internet dedicated line. The coordinated IPv6 disaster recovery implementation process in the uplink direction includes: BAS1 or BAS2 sends an IPv6 address acquisition request to a policy BAS via a Layer 2 EVPN domain; the policy BAS sends a bound IPv6 prefix to BAS1 or BAS2; the CE uses the ND prefix for the CE uplink port and the PD prefix for the CE downlink port; the CE sends the uplink message to BAS1 or BAS2 using the default equal-cost routing method according to the HASH load balancing algorithm; BAS1 or BAS2 sends the uplink message to the policy BAS via a Layer 2 EVPN domain, so that the policy BAS sends the uplink message to the guest BAS according to the IPv6 routing table. The present application can effectively implement disaster recovery protection for IPv6 Internet dedicated lines and data center customers.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a system and method for realizing coordinated disaster recovery of an IPv6 Internet dedicated line. Background Art

[0002] Currently, operators can deploy dedicated internet lines based on broadband metropolitan area networks (MANs) or intelligent metropolitan area networks (IMANs) to provide dedicated internet access services to government, enterprise, and data center customers. However, due to the lack of effective protection measures for dedicated internet lines, single-point failures (SPOFs) such as fiber optic cable outages, access line outages, access layer device downtime, aggregation switch downtime, broadband access servers, and service routers can impact services for government, enterprise, and data center customers, leading to communication interruptions for upper-layer applications.

[0003] So far, there is no suitable large-scale deployment method or device to achieve service protection, disaster recovery collaboration, IP address roaming, and seamless migration of government and enterprise customers' Internet dedicated lines and data centers.

[0004] Therefore, how to achieve coordinated disaster recovery of IPv6 Internet dedicated lines has become a breakthrough point for improving the network's digital transformation capabilities. Summary of the Invention

[0005] The technical problem to be solved by this application is to provide an IPv6 Internet dedicated line disaster recovery collaborative implementation system and method to solve the problems existing in the prior art in view of the above-mentioned deficiencies in the prior art.

[0006] In a first aspect, the present application provides an IPv6 Internet dedicated line disaster recovery collaborative implementation system, the system comprising: a customer terminal, a customer edge device CE, an access network, an aggregation switch SW, a broadband access server BAS, a core router CR, a guest BAS, and a policy BAS;

[0007] The client terminal is provided with three layers of CE, and the BAS includes BAS1 and BAS2. The system is used to implement the coordinated disaster recovery process of the IPv6 Internet dedicated line in the uplink direction, wherein:

[0008] In response to the CE sending an IPv6 prefix request message to BAS1 or BAS2 using the IPv6 address autoconfiguration method, BAS1 or BAS2 binds the downstream Layer 2 interface to the Layer 2 VLAN corresponding to the customer, associates the downstream Layer 2 interface to the Layer 2 Ethernet virtual private network (EVPN) domain, and sends the IPv6 address acquisition request to the policy BAS through the Layer 2 EVPN domain.

[0009] Based on whether the policy BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2. BAS1 or BAS2 then uses the Dynamic Host Configuration Protocol (DHCPv6) Neighbor Discovery (ND) and DHCPv6 Prefix Delegation (PD) message to send the IPv6 prefix to the CE via the Layer 2 VLAN domain.

[0010] The CE uses the ND prefix for the CE uplink port and the PD prefix for the CE downlink port. This allows the client terminal to obtain an IPv6 prefix from the CE through DHCPv6, generate an IPv6 address, and construct an uplink message to send to the CE.

[0011] In response to receiving an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 using the default equal-cost routing method according to the HASH load balancing algorithm;

[0012] In response to receiving the uplink message, BAS1 or BAS2 sends the uplink message to the policy BAS through the Layer 2 EVPN domain, so that the policy BAS sends the uplink message to the guest BAS according to the IPv6 routing table.

[0013] In some embodiments, based on whether the policy BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix as a judgment condition, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2, specifically including:

[0014] If it has been bound, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2;

[0015] If not, the policy BAS binds the IPv6 prefixes of the corresponding number of hosts according to the Layer 2 EVPN domain corresponding to the customer, and sends the bound IPv6 prefixes to BAS1 or BAS2.

[0016] In some embodiments, the system is further configured to implement a coordinated disaster recovery implementation process for an IPv6 Internet dedicated line in the downstream direction, wherein:

[0017] In response to receiving the response message from the visitor, the guest BAS searches the IPv6 routing table and sends the response message to the policy BAS;

[0018] The policy BAS verifies based on the IPv6 adjacency table whether the client MAC address was accessed from BAS1 or learned from BAS2;

[0019] Based on whether the client MAC address is learned from BAS1 or BAS2, the system sends a response message to the CE.

[0020] In response to receiving the response message, the CE forwards the response message to the client terminal.

[0021] In some embodiments, based on whether the client MAC address is learned from BAS1 or BAS2, a response message is sent to the CE, specifically including:

[0022] If learned from BAS1, BAS1 sends a response message to CE along the left path;

[0023] If learned from BAS2, BAS2 sends a response message to CE along the right path.

[0024] In a second aspect, the present application provides an IPv6 Internet dedicated line disaster recovery collaborative implementation system, the system comprising: a customer terminal, a customer edge device CE, an access network, an aggregation switch SW, a broadband access server BAS, a core router CR, a guest BAS, and a policy BAS;

[0025] The client terminal is provided with a layer 2 CE, and the BAS includes BAS1 and BAS2. The system is used to implement a coordinated disaster recovery process of an IPv6 Internet dedicated line in the uplink direction, wherein:

[0026] In response to the client terminal sending an IPv6 prefix request message to BAS1 or BAS2 through DHCPv6 or stateless address autoconfiguration (SLAAC), BAS1 or BAS2 binds the downstream Layer 2 interface to the Layer 2 VLAN corresponding to the client, associates the downstream Layer 2 interface to the Layer 2 Ethernet virtual private network (EVPN) domain, and sends the IPv6 address acquisition request to the policy BAS through the Layer 2 EVPN domain;

[0027] Based on whether the policy BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2, so that BAS1 or BAS2 sends the IPv6 prefix to the client terminal through the Layer 2 VLAN domain using a Dynamic Host Configuration Protocol (DHCPv6) Neighbor Discovery (ND) or SLAAC message.

[0028] The client terminal generates an IPv6 address using the extended unique identifier (64-bit EUI64) + prefix + DHCP ND or EUI64 + prefix + SLAAC, and constructs an uplink message to send to the CE.

[0029] In response to receiving an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 according to the HASH load balancing algorithm;

[0030] In response to receiving the uplink message, BAS1 or BAS2 sends the uplink message to the policy BAS through the Layer 2 EVPN domain, so that the policy BAS sends the uplink message to the guest BAS according to the IPv6 routing table.

[0031] In some embodiments, based on whether the policy BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix as a judgment condition, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2, specifically including:

[0032] If it has been bound, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2;

[0033] If not, the policy BAS binds the IPv6 prefixes of the corresponding number of hosts according to the Layer 2 EVPN domain corresponding to the customer, and sends the bound IPv6 prefixes to BAS1 or BAS2.

[0034] In some embodiments, the system is further configured to implement a coordinated disaster recovery implementation process for an IPv6 Internet dedicated line in the downstream direction, wherein:

[0035] In response to receiving the response message from the visitor, the guest BAS sends the response message to the policy BAS by searching the IPv6 routing table;

[0036] The policy BAS verifies based on the IPv6 adjacency table whether the client MAC address was accessed from BAS1 or learned from BAS2;

[0037] Based on whether the client MAC address is learned from BAS1 or BAS2, the system sends a response message to the CE.

[0038] In response to receiving the response message, the CE forwards the response message to the client terminal.

[0039] In some embodiments, based on whether the client MAC address is learned from BAS1 or BAS2, a response message is sent to the CE, specifically including:

[0040] If learned from BAS1, BAS1 sends a response message to CE along the left path;

[0041] If learned from BAS2, BAS2 sends a response message to CE along the right path.

[0042] In a third aspect, the present application provides a method for implementing disaster recovery collaboration for an IPv6 Internet dedicated line, wherein a client terminal is provided with a three-layer CE. The method is used to implement a disaster recovery collaboration implementation process for an IPv6 Internet dedicated line in the uplink direction, and the method includes:

[0043] In response to the CE sending an IPv6 prefix request message to BAS1 or BAS2 using the IPv6 address autoconfiguration method, BAS1 or BAS2 binds the downstream Layer 2 interface to the Layer 2 VLAN corresponding to the customer, associates the downstream Layer 2 interface to the Layer 2 Ethernet virtual private network (EVPN) domain, and sends the IPv6 address acquisition request to the policy BAS through the Layer 2 EVPN domain.

[0044] Based on whether the policy BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2. BAS1 or BAS2 then uses the Dynamic Host Configuration Protocol (DHCPv6) Neighbor Discovery (ND) and DHCPv6 Prefix Delegation (PD) message to send the IPv6 prefix to the CE via the Layer 2 VLAN domain.

[0045] The CE uses the ND prefix for the CE uplink port and the PD prefix for the CE downlink port. This allows the client terminal to obtain an IPv6 prefix from the CE through DHCPv6, generate an IPv6 address, and construct an uplink message to send to the CE.

[0046] In response to receiving an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 using the default equal-cost routing method according to the HASH load balancing algorithm;

[0047] In response to receiving the uplink message, BAS1 or BAS2 sends the uplink message to the policy BAS through the Layer 2 EVPN domain, so that the policy BAS sends the uplink message to the guest BAS according to the IPv6 routing table.

[0048] In some embodiments, the method is further used to implement a coordinated disaster recovery implementation process for an IPv6 Internet dedicated line in the downlink direction, and the method further includes:

[0049] In response to receiving the response message from the visitor, the guest BAS searches the IPv6 routing table and sends the response message to the policy BAS;

[0050] The policy BAS verifies based on the IPv6 adjacency table whether the client MAC address was accessed from BAS1 or learned from BAS2;

[0051] Based on whether the client MAC address is learned from BAS1 or BAS2, the system sends a response message to the CE.

[0052] In response to receiving the response message, the CE forwards the response message to the client terminal.

[0053] In a fourth aspect, the present application provides a method for implementing disaster recovery collaboration for an IPv6 Internet dedicated line, wherein a client terminal is provided with a Layer 2 CE. The method is used to implement a disaster recovery collaboration process for an IPv6 Internet dedicated line in the uplink direction, and the method comprises:

[0054] In response to the client terminal sending an IPv6 prefix request message to BAS1 or BAS2 through DHCPv6 or stateless address autoconfiguration (SLAAC), BAS1 or BAS2 binds the downstream Layer 2 interface to the Layer 2 VLAN corresponding to the client, associates the downstream Layer 2 interface to the Layer 2 Ethernet virtual private network (EVPN) domain, and sends the IPv6 address acquisition request to the policy BAS through the Layer 2 EVPN domain;

[0055] Based on whether the policy BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2, so that BAS1 or BAS2 sends the IPv6 prefix to the client terminal through the Layer 2 VLAN domain using a Dynamic Host Configuration Protocol (DHCPv6) Neighbor Discovery (ND) or SLAAC message.

[0056] The client terminal generates an IPv6 address using the extended unique identifier (64-bit EUI64) + prefix + DHCP ND or EUI64 + prefix + SLAAC, and constructs an uplink message to send to the CE.

[0057] In response to receiving an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 according to the HASH load balancing algorithm;

[0058] In response to receiving the uplink message, BAS1 or BAS2 sends the uplink message to the policy BAS through the Layer 2 EVPN domain, so that the policy BAS sends the uplink message to the guest BAS according to the IPv6 routing table.

[0059] In some embodiments, the method is further used to implement a coordinated disaster recovery implementation process for an IPv6 Internet dedicated line in the downlink direction, and the method further includes:

[0060] In response to receiving the response message from the visitor, the guest BAS sends the response message to the policy BAS by searching the IPv6 routing table;

[0061] The policy BAS verifies based on the IPv6 adjacency table whether the client MAC address was accessed from BAS1 or learned from BAS2;

[0062] Based on whether the client MAC address is learned from BAS1 or BAS2, the system sends a response message to the CE.

[0063] In response to receiving the response message, the CE forwards the response message to the client terminal.

[0064] The present application provides an IPv6 Internet dedicated line disaster recovery collaborative implementation system and method, the system includes: a customer terminal, a customer edge device CE, an access network, a convergence switch SW, a broadband access server BAS, a core router CR, a visitor BAS, and a policy BAS; wherein, the customer terminal is provided with a three-layer CE, and the BAS includes BAS1 and BAS2, and the system is used to implement an IPv6 Internet dedicated line disaster recovery collaborative implementation process in the uplink direction, wherein: in response to CE using an IPv6 address automatic configuration method to send an application for an IPv6 prefix message to BAS1 or BAS2, the downlink layer 2 interface of BAS1 or BAS2 is bound to the layer 2 VLAN corresponding to the customer, the downlink layer 2 interface is associated with the layer 2 Ethernet virtual private network EVPN domain, and the IPv6 address acquisition application is sent to the policy BAS through the layer 2 EVPN domain; the judgment condition is based on whether the policy BAS is bound to the layer 2 EVPN domain and the IPv6 prefix. The policy BAS sends the bound IPv6 prefix to BAS1 or BAS2, so that BAS1 or BAS2 sends the IPv6 prefix to CE through the Layer 2 VLAN domain using the Dynamic Host Configuration Protocol DHCPv6 Neighbor Discovery ND+DHCPv6 Prefix Delegation PD message; the CE uses the ND prefix for the CE uplink port and the PD prefix for the CE downlink port, so that the client terminal obtains the IPv6 prefix from the CE through DHCPv6, generates an IPv6 address, and constructs an uplink message to send to the CE; in response to receiving the uplink message from the client terminal, the CE sends the uplink message to BAS1 or BAS2 through the default equal-cost routing method according to the HASH load balancing algorithm; in response to receiving the uplink message, BAS1 or BAS2 sends the uplink message to the policy BAS through the Layer 2 EVPN domain, so that the policy BAS sends the uplink message to the guest BAS according to the IPv6 routing table. This application provides a system and method for implementing coordinated disaster recovery for dedicated internet lines. For client-side Layer 3 CE scenarios, this system can achieve bidirectional IPv6 load balancing between the access and aggregation layers. For client-side Layer 2 CE scenarios, this system can achieve bidirectional IPv6 load balancing between the access and aggregation layers. This application effectively implements disaster recovery for IPv6 dedicated internet lines and data center customers. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0066] Figure 1 A schematic diagram of a single convergence layer load sharing IPv4 / v6 method in the prior art;

[0067] Figure 2 Schematic diagram of three access layer protection modes in the prior art;

[0068] Figure 3 This is a schematic diagram of IPv4 / v6 in a dual-aggregation layer active / standby scenario in the prior art;

[0069] Figure 4 Schematic diagram of a client-side three-layer CE IPv6 Internet dedicated line disaster recovery collaborative implementation system provided in an embodiment of the present application;

[0070] Figure 5 A schematic diagram of the uplink flow of the system for implementing IPv6 Internet dedicated line disaster recovery collaboration on the client side of a three-layer CE provided in an embodiment of the present application;

[0071] Figure 6 Another schematic diagram of the uplink process of the system for implementing IPv6 Internet dedicated line disaster recovery collaboration on the client side three-layer CE provided in an embodiment of the present application;

[0072] Figure 7 A schematic diagram of the downlink process of the client-side three-layer CE IPv6 Internet dedicated line disaster recovery collaborative implementation system provided in an embodiment of the present application;

[0073] Figure 8 Another schematic diagram of the downlink process of the system for implementing disaster recovery collaboration of IPv6 Internet dedicated lines on the client side of the three-layer CE provided in the embodiment of the present application;

[0074] Figure 9 Schematic diagram of a client-side Layer 2 CE IPv6 Internet dedicated line disaster recovery collaborative implementation system provided in an embodiment of the present application;

[0075] Figure 10 A schematic diagram of the uplink flow of the system for implementing IPv6 Internet dedicated line disaster recovery collaboration on the client side Layer 2 CE provided in an embodiment of the present application;

[0076] Figure 11 Another schematic diagram of the uplink process of the system for implementing IPv6 Internet dedicated line disaster recovery collaboration for a client-side Layer 2 CE provided in an embodiment of the present application;

[0077] Figure 12 A schematic diagram of the downlink process of the IPv6 Internet dedicated line disaster recovery collaborative implementation system for the client-side Layer 2 CE provided in an embodiment of the present application;

[0078] Figure 13 Another schematic diagram of the downlink process of the IPv6 Internet dedicated line disaster recovery collaborative implementation system for the client-side Layer 2 CE provided in an embodiment of the present application.

[0079] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0080] In order to enable those skilled in the art to better understand the technical solution of the present application, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0081] It should be understood that the specific embodiments and drawings described herein are only used to explain the present application, rather than to limit the present application.

[0082] It can be understood that, in the absence of conflict, the various embodiments and features in the embodiments of the present application can be combined with each other.

[0083] It will be understood that, for the sake of ease of description, the drawings of this application only show the parts related to this application, while the parts not related to this application are not shown in the drawings.

[0084] It can be understood that each unit and module involved in the embodiments of the present application may correspond to only one physical structure, or may be composed of multiple physical structures, or multiple units and modules may be integrated into one physical structure.

[0085] It can be understood that the terms "first", "second", etc. in the embodiments of the present application are used to distinguish different objects, or to distinguish different processing of the same object, rather than to describe a specific order of objects.

[0086] It is understandable that, in the absence of conflict, the functions and steps marked in the flowcharts and block diagrams of the present application may occur in an order different from that marked in the drawings.

[0087] It is understood that the flowcharts and block diagrams of the present application illustrate the possible architectures, functions, and operations of the systems, devices, equipment, and methods according to the various embodiments of the present application. Each box in the flowchart or block diagram may represent a unit, module, program segment, or code, which contains executable instructions for implementing the specified functions. Moreover, each box or combination of boxes in the block diagram and flowchart may be implemented by a hardware-based system that implements the specified functions, or by a combination of hardware and computer instructions.

[0088] It can be understood that the units and modules involved in the embodiments of the present application can be implemented by software or hardware, for example, the units and modules can be located in a processor.

[0089] Before describing the embodiments of the present application, the English abbreviations involved in the embodiments of the present application are explained:

[0090] IPv4 (Internet Protocol Version 4): A network layer protocol for packet switching, widely used to transmit data on the Internet.

[0091] IPv6 (Internet Protocol Version 6): The next generation version of the Internet Protocol, designed to solve the problem of IPv4 address exhaustion and provide a larger address space and enhanced functions.

[0092] CE (Customer Edge): A device located between the user network and the service provider network, used to connect the enterprise network to the service provider's network.

[0093] SW (Switch): A network device used to connect network segments within a local area network and forward data based on the MAC address of the data packet.

[0094] BAS (Broadband Access Server): A network device used to manage user access and traffic on a broadband network.

[0095] SR (Service Router): A network router designed specifically to provide value-added services such as QoS and security.

[0096] VLAN (Virtual Local Area Network): A local area network that is logically divided on a physical network through a switch, which can isolate broadcast domains.

[0097] BGP (Border Gateway Protocol): A protocol used to exchange routing information between autonomous systems on the Internet.

[0098] RR (Route Reflector): A BGP route reflector used to propagate routing information in networks that do not fully conform to BGP peer connectivity.

[0099] Ethernet VPN (EVPN): A VPN technology used to provide Ethernet services on Layer 2 and Layer 3 networks.

[0100] VRRP (Virtual Router Redundancy Protocol): A selection and failover protocol for high availability of routers.

[0101] ARP (Address Resolution Protocol) table entries: used to store the correspondence between IP addresses and MAC addresses in the network.

[0102] MAC address (Media Access Control Address): A MAC address is the physical address of a device and is used to identify a network interface controller. Each device has a unique MAC address.

[0103] IP address (Internet Protocol Address): An IP address is a logical address used by a device to communicate on a network and is used to identify the device on the network.

[0104] EUI64 (Extended Unique Identifier 64-bit): used to generate a globally unique network interface identifier.

[0105] DHCP (Dynamic Host Configuration Protocol): A network protocol used to automatically assign IP addresses and network configuration parameters to devices on a network.

[0106] ND (Neighbor Discovery): Part of the IPv6 protocol, used for node discovery and automatic configuration.

[0107] PD (Prefix Delegation): A mechanism in IPv6 used to delegate network prefixes from an upper-level router to a lower-level router.

[0108] SLAAC (Stateless Address Auto Configuration): An address configuration method in IPv6 that allows nodes to automatically configure addresses without external assistance.

[0109] CR (Core Router): Located at the core of the network, it is mainly used for data packet routing and forwarding.

[0110] Furthermore, in communications networks, CE devices are typically responsible for connecting an enterprise or individual's internal network to a service provider's PE (Provider Edge) device. Depending on the network design and requirements, CE devices can be either Layer 3 or Layer 2 devices.

[0111] The following is a detailed explanation of Layer 3 CE and Layer 2 CE:

[0112] (1) Layer 3 CE (Layer 3 equipment):

[0113] (1.1) Definition: Layer 3 CE refers to client-side equipment that has Layer 3 network functions (network layer functions in the OSI model), typically used for routing data packets.

[0114] (1.2) Features:

[0115] Routing function: Layer 3 CE can run routing protocols (such as OSPF, BGP, and EIGRP) and can exchange dynamic routes with service provider equipment (PE, Provider Edge).

[0116] Independent IP management: Customers can manage their own IP address allocation and network routing.

[0117] Multiple WAN connections: Layer 3 CEs are typically connected to multiple WAN interfaces for redundancy and load balancing.

[0118] Typical equipment: router or layer 3 switch with routing function.

[0119] (1.3) Applicable scenarios:

[0120] Large enterprise networks where customers require higher autonomy and complex network configurations.

[0121] When using services such as MPLS VPN, customer devices need to participate in routing protocols.

[0122] (2) Layer 2 CE (Layer 2 equipment):

[0123] (2.1) Definition: Layer 2 CE refers to client-side equipment that only works at Layer 2 (the data link layer in the OSI model) and is primarily used for Ethernet switching and frame forwarding.

[0124] (2.2) Features:

[0125] Switching function: Layer 2 CE is only responsible for forwarding frames and does not need to run routing protocols.

[0126] Transparent transmission: The Layer 2 CE forwards traffic to the service provider's network (usually a PE device), which is responsible for routing.

[0127] Simple configuration: Layer 2 CE configuration is simple. You don’t need to worry about IP routing. You only need to set up VLAN or port mapping.

[0128] Typical equipment: Layer 2 switch or Ethernet bridge.

[0129] (2.3) Applicable scenarios:

[0130] Small and medium-sized enterprise networks or branch offices only need to implement a simple Layer 2 connection through the operator.

[0131] Point-to-point or point-to-multipoint Layer 2 VPN (such as VPLS and E-LAN).

[0132] The following table summarizes the main differences between Layer 3 CE and Layer 2 CE:

[0133]

[0134] In the existing technology, there are two main methods for coordinating disaster recovery between Internet dedicated lines and data center customers.

[0135] (1) The first method: using a single convergence layer load sharing IPv4 / v6 method.

[0136] Figure 1 This is a schematic diagram of the single convergence layer load sharing IPv4 / v6 method in the existing technology, as shown in FIG. Figure 1 As shown, the method is divided into IPv4 application scenario and IPv6 application scenario.

[0137] In IPv4 applications, dedicated internet lines and data center customer CE devices converge via two (or more) access network paths to the same aggregation switch (SW) and the same broadband access server (BAS) / service router (SR). For downstream traffic, the BAS uses two sub-interfaces to point the customer's service IPv4 address to different interconnected IPv4 addresses through static or dynamic routing, meeting the customer's internet access needs.

[0138] In addition to the above protection mode, there are three modes at the access network level: Figure 2 Schematic diagram of three access layer protection modes in the prior art, such as Figure 2 As shown, the details are as follows:

[0139] (1) The customer SW is connected to different access layer devices through two different links, and then connected to the aggregation switch through the same VLAN transparent transmission + the same service address, and then connected to the same BAS / SR.

[0140] (2) The customer CE (can be a router / switch / firewall) is connected to the same access layer device through two links, then connected to the aggregation switch, and then connected to the same BAS / SR.

[0141] (3) The customer CE (can be a router / switch / firewall) is connected to different access layer devices through two links, then connected to the aggregation switch, and then connected to the same BAS / SR.

[0142] In addition, in IPv6 application scenarios, the specific protection method is similar to IPv4. The Internet dedicated line and data center customer CE equipment are converged to the same aggregation switch SW and broadband access server BAS / service router SR through two (or more) access network paths. In the downstream traffic, BAS uses two sub-interfaces to point the customer's business IPv6 address to different interconnected IPv6 addresses through static routing or dynamic routing, realizing the customer's need to access the Internet.

[0143] In summary, although the first type of solution can partially solve customer services at the access layer, there is a single point of failure risk in the aggregation layer switches, broadband access servers BAS / service routers SR, and end-to-end protection of Internet dedicated lines and data center customer services cannot be guaranteed.

[0144] (2) The second method: using dual-aggregation layer active / standby IPv4 / v6 scenarios.

[0145] Figure 3 This is a schematic diagram of IPv4 / v6 in a dual-aggregation layer active / standby scenario in the prior art. Figure 3 As shown, the method is divided into IPv4 application scenario and IPv6 application scenario.

[0146] In IPv4 applications, dedicated internet lines and data center customer CE devices converge via two (or more) access network paths to different aggregation switches (SWs), broadband access servers (BASs), and service routers (SRs). For downstream traffic, the BAS uses two sub-interfaces to direct the customer's service IPv4 address to different interconnected IPv4 addresses through static or dynamic routing, enabling customer internet access.

[0147] Furthermore, in IPv6 application scenarios, the specific protection methods are similar to those for IPv4. This architecture employs an internet dedicated line and data center customer CE devices, each traversing two (or more) access network paths, before converging to different aggregation switches (SW) and broadband access servers (BAS) / service routers (SR). For downstream traffic, the BAS uses two sub-interfaces to direct the customer's service IPv6 address to different interconnected IPv6 addresses through static or dynamic routing, enabling customer internet access.

[0148] In summary, in the second type of solution, although disaster recovery protection can be implemented at the access layer and aggregation layer, when the BAS / SR publishes service routes, under the BGP+RR architecture, the visitor can only choose the path corresponding to one of the BAS / SRs, that is, only the active-standby protection effect can be achieved, and the service load sharing effect, IP address roaming, and seamless migration cannot be achieved.

[0149] Therefore, both the first and second methods have very obvious common defects, which are specifically reflected in the following four aspects:

[0150] (1) In a single-aggregation layer load-sharing IPv4 / 6 scenario, the aggregation layer switches (SW), broadband access servers (BAS), and service routers (SR) present single-point risks. If a failure or downtime occurs or a cutover or upgrade occurs, all services will be blocked.

[0151] (2) In the dual-aggregation layer active / standby scenario, IPv4 / v6 can only achieve active / standby, not load balancing;

[0152] (3) In addition to issues 1 and 2, IPv6 addresses need to be manually configured. Since IPv6 addresses have a large number of bits (128 bits in binary, 32 bits in hexadecimal, and abbreviations exist for various situations), in large-scale deployment of Internet dedicated lines and data centers, there are risks such as high workload, easy errors, and complex reading and writing.

[0153] (4) In addition to issues 1 and 2, there is also the lack of IP address roaming and seamless migration.

[0154] These issues are particularly prominent in the areas of dedicated internet lines and data center customers, and existing solutions cannot fully address them. The market needs to address these current challenges by providing customers with disaster recovery and collaborative network services that offer higher reliability and more secure business operations.

[0155] To address the above shortcomings, this application proposes a system and method for implementing disaster recovery collaboration on an IPv6 dedicated line. The system includes two IPv6 solutions: one with three-layer CE on the client side and one with two-layer CE on the client side. Specifically, the system includes:

[0156] (1) A system and method for bidirectional load balancing IPv6 at dual aggregation layers of a client-side three-layer CE. Client-side upstream traffic is connected to different aggregation switches SW, different broadband access servers BAS, and service routers SR via an equal-cost default routing path from different access layers (load balancing), and then connected to a centralized or distributed policy BAS device via a Layer 2 EVPN domain to automatically obtain an IPv6 address. The CE's uplink port automatically obtains a fixed IPv6 prefix and generates an IPv6 address via the "EUI64+prefix+DHCP ND method." The CE's downstream terminal automatically obtains a fixed IPv6 prefix and generates an IPv6 address via the "EUI64+prefix+DHCP PD method." Internet-side downstream traffic passes through a centralized or distributed policy BAS, penetrates the Layer 2 EVPN domain, returns to the corresponding different access servers BAS and service routers SR (load balancing), and continues to enter different aggregation switches SW. Through different access layers, the traffic is then transferred downstream to the client side. Bidirectional load balancing IPv6 effects can be achieved at the access and aggregation layers.

[0157] (2) A system and method for bidirectional load balancing IPv6 at dual aggregation layers of client-side Layer 2 CE. Client-side upstream traffic is connected to different aggregation switches SW, different broadband access servers BAS, and service routers SR from different access layers (load balancing) through the "EUI64+prefix+DHCP ND" or "EUI64+prefix+SLAAC" method, and then connected to the centralized or distributed policy BAS device through the Layer 2 EVPN domain to automatically obtain an IPv6 address. Internet-side downstream traffic passes through the centralized or distributed policy BAS, penetrates the Layer 2 EVPN domain, returns to the corresponding different access servers BAS and service routers SR (load balancing), and continues to enter different aggregation switches SW. Through different access layers, the traffic is downstream to the client side. This can achieve a bidirectional load balancing IPv6 effect at the access layer and aggregation layer.

[0158] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0159] Figure 4 Schematic diagram of the client-side three-layer CE IPv6 Internet dedicated line disaster recovery collaborative implementation system provided in the embodiment of the present application, Figure 5 The schematic diagram of the uplink flow of the client-side three-layer CE IPv6 Internet dedicated line disaster recovery collaborative implementation system provided in the embodiment of the present application is as follows: Figure 4 as well as Figure 5As shown, the present application provides an IPv6 Internet dedicated line disaster recovery collaborative implementation system, the system comprising: a customer terminal, a customer edge device CE, an access network, an aggregation switch SW, a broadband access server BAS, a core router CR, a guest BAS, and a policy BAS;

[0160] The client terminal is provided with three layers of CE, and the BAS includes BAS1 and BAS2. The system is used to implement the coordinated disaster recovery process of the IPv6 Internet dedicated line in the uplink direction, wherein:

[0161] In response to the CE sending an IPv6 prefix request message to BAS1 or BAS2 using the IPv6 address autoconfiguration method, BAS1 or BAS2 binds the downstream Layer 2 interface to the Layer 2 VLAN corresponding to the customer, associates the downstream Layer 2 interface to the Layer 2 Ethernet virtual private network (EVPN) domain, and sends the IPv6 address acquisition request to the policy BAS through the Layer 2 EVPN domain.

[0162] Based on whether the policy BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2. BAS1 or BAS2 then uses the Dynamic Host Configuration Protocol (DHCPv6) Neighbor Discovery (ND) and DHCPv6 Prefix Delegation (PD) message to send the IPv6 prefix to the CE via the Layer 2 VLAN domain.

[0163] The CE uses the ND prefix for the CE uplink port and the PD prefix for the CE downlink port. This allows the client terminal to obtain an IPv6 prefix from the CE through DHCPv6, generate an IPv6 address, and construct an uplink message to send to the CE.

[0164] In response to receiving an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 using the default equal-cost routing method according to the HASH load balancing algorithm;

[0165] In response to receiving the uplink message, BAS1 or BAS2 sends the uplink message to the policy BAS through the Layer 2 EVPN domain, so that the policy BAS sends the uplink message to the guest BAS according to the IPv6 routing table.

[0166] In some embodiments, based on whether the policy BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix as a judgment condition, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2, specifically including:

[0167] If it has been bound, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2;

[0168] If not, the policy BAS binds the IPv6 prefixes of the corresponding number of hosts according to the Layer 2 EVPN domain corresponding to the customer, and sends the bound IPv6 prefixes to BAS1 or BAS2.

[0169] Specifically, Figure 6 Another schematic diagram of the uplink process of the client-side three-layer CE IPv6 Internet dedicated line disaster recovery collaborative implementation system provided in the embodiment of the present application is as follows Figure 6 As shown in Figure 1, the packet processing flow for an IPv6 customer dedicated line (Layer 3 CE) in the upstream direction includes:

[0170] Step 501: The client CE uses the IPv6 address automatic configuration method to send an IPv6 prefix application message to BAS1 or BAS2.

[0171] Step 502: BAS1 or BAS2 binds the Layer 2 interface downlink to the client's corresponding Layer 2 VLAN (single or double VLAN).

[0172] Step 503: BAS1 or BAS2 associates the downlink Layer 2 interface with the Layer 2 EVPN domain.

[0173] Step 504: BAS1 or BAS2 receives the IPv6 address acquisition request from the customer CE and sends the request to the policy BAS via the Layer 2 EVPN domain.

[0174] Step 505: Whether the BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix is ​​determined based on the policy. If so, proceed to step 508. If not, proceed to step 506.

[0175] Step 506: Bind the IPv6 prefixes corresponding to the number of hosts in the Layer 2 EVPN domain corresponding to each customer and publish them through a routing announcement message.

[0176] Step 507, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2;

[0177] Step 508: BAS1 or BAS2 sends the IPv6 prefix to the customer CE via the Layer 2 VLAN domain using a DHCPv6 ND+DHCPv6 PD message.

[0178] Step 509: After receiving the DHCPv6 message, the client CE uses the ND prefix for the CE uplink port and the PD prefix for the CE downlink port.

[0179] Step 510: The client terminal obtains an IPv6 prefix from the CE via DHCPv6.

[0180] Step 511: The client terminal automatically generates a fixed IPv6 address using EUI64+prefix and constructs an uplink message. The gateway is on the policy BAS.

[0181] Step 512: Customer CE receives the uplink message and sends it to BAS1 and BAS2 using the default equal-cost routing method according to the HASH load balancing algorithm.

[0182] Step 513: BAS1 or BAS2 receives the uplink message and sends the uplink message to the policy BAS via the Layer 2 EVPN domain.

[0183] Step 514: The policy BAS sends the uplink message to the visitor BAS according to the IPv6 routing table;

[0184] Step 515: The visitor receives the customer service message.

[0185] In some embodiments, the system is also used to implement a coordinated disaster recovery process for an IPv6 Internet dedicated line in the downstream direction.

[0186] Figure 7 A schematic diagram of the downlink process of the client-side three-layer CE IPv6 Internet dedicated line disaster recovery collaborative implementation system provided in the embodiment of the present application is shown as follows: Figure 7 As shown, where:

[0187] In response to receiving the response message from the visitor, the guest BAS searches the IPv6 routing table and sends the response message to the policy BAS;

[0188] The policy BAS verifies based on the IPv6 adjacency table whether the client MAC address was accessed from BAS1 or learned from BAS2;

[0189] Based on whether the client MAC address is learned from BAS1 or BAS2, the system sends a response message to the CE.

[0190] In response to receiving the response message, the CE forwards the response message to the client terminal.

[0191] In some embodiments, based on whether the client MAC address is learned from BAS1 or BAS2, a response message is sent to the CE, specifically including:

[0192] If learned from BAS1, BAS1 sends a response message to CE along the left path;

[0193] If learned from BAS2, BAS2 sends a response message to CE along the right path.

[0194] Specifically, Figure 8Another schematic diagram of the downlink process of the client-side three-layer CE IPv6 Internet dedicated line disaster recovery collaborative implementation system provided in the embodiment of the present application is as follows Figure 8 As shown, specifically including:

[0195] Step 601: The visitor sends a response message to the dedicated line customer;

[0196] Step 602: The visitor BAS receives the response message;

[0197] Step 603: The guest BAS searches the IPv6 routing table and sends a response message to the policy BAS.

[0198] Step 604: The policy BAS checks the IPv6 adjacency table to confirm whether the client MAC address was accessed from BAS1 or learned from BAS2.

[0199] Step 605: Based on whether the client MAC address is learned from BAS1 or BAS2, if it is learned from BAS1, proceed to step 607. If it is learned from BAS2, proceed to step 606.

[0200] Step 606: BAS2 sends the downlink message to the customer CE along the right path;

[0201] Step 607: BAS1 sends the downlink message to the customer CE along the left path;

[0202] Step 608: The client CE receives the downlink message.

[0203] Step 609: The client CE sends the downlink message to the client terminal;

[0204] Step 610: The client terminal receives a downlink message.

[0205] Figure 9 Schematic diagram of the client-side Layer 2 CE IPv6 Internet dedicated line disaster recovery collaborative implementation system provided in the embodiment of the present application, Figure 10 The schematic diagram of the uplink flow of the IPv6 Internet dedicated line disaster recovery collaborative implementation system for the client-side Layer 2 CE provided in the embodiment of the present application is as follows: Figure 9 as well as Figure 10 As shown, the present application provides an IPv6 Internet dedicated line disaster recovery collaborative implementation system, the system comprising: a customer terminal, a customer edge device CE, an access network, an aggregation switch SW, a broadband access server BAS, a core router CR, a guest BAS, and a policy BAS;

[0206] The client terminal is provided with a layer 2 CE, and the BAS includes BAS1 and BAS2. The system is used to implement a coordinated disaster recovery process of an IPv6 Internet dedicated line in the uplink direction, wherein:

[0207] In response to the client terminal sending an IPv6 prefix request message to BAS1 or BAS2 through DHCPv6 or stateless address autoconfiguration (SLAAC), BAS1 or BAS2 binds the downstream Layer 2 interface to the Layer 2 VLAN corresponding to the client, associates the downstream Layer 2 interface to the Layer 2 Ethernet virtual private network (EVPN) domain, and sends the IPv6 address acquisition request to the policy BAS through the Layer 2 EVPN domain;

[0208] Based on whether the policy BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2, so that BAS1 or BAS2 sends the IPv6 prefix to the client terminal through the Layer 2 VLAN domain using a Dynamic Host Configuration Protocol (DHCPv6) Neighbor Discovery (ND) or SLAAC message.

[0209] The client terminal generates an IPv6 address using the extended unique identifier (64-bit EUI64) + prefix + DHCP ND or EUI64 + prefix + SLAAC, and constructs an uplink message to send to the CE.

[0210] In response to receiving an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 according to the HASH load balancing algorithm;

[0211] In response to receiving the uplink message, BAS1 or BAS2 sends the uplink message to the policy BAS through the Layer 2 EVPN domain, so that the policy BAS sends the uplink message to the guest BAS according to the IPv6 routing table.

[0212] In some embodiments, based on whether the policy BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix as a judgment condition, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2, specifically including:

[0213] If it has been bound, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2;

[0214] If not, the policy BAS binds the IPv6 prefixes of the corresponding number of hosts according to the Layer 2 EVPN domain corresponding to the customer, and sends the bound IPv6 prefixes to BAS1 or BAS2.

[0215] Specifically, Figure 11 Another schematic diagram of the uplink process of the IPv6 Internet dedicated line disaster recovery collaborative implementation system for the client-side Layer 2 CE provided in the embodiment of the present application is as follows Figure 11 As shown in Figure 2, the packet processing flow for the IPv6 customer dedicated line (Layer 2 CE) in the uplink direction specifically includes:

[0216] Step 701: The client terminal sends an IPv6 prefix request message to BAS1 or BAS2 via DHCPv6 or SLAAC.

[0217] Step 702: BAS1 or BAS2 binds the Layer 2 interface downlink to the client's corresponding Layer 2 VLAN (single or double VLAN).

[0218] Step 703 , BAS1 or BAS2 associates the downlink Layer 2 interface to the Layer 2 EVPN domain;

[0219] Step 704 : BAS1 or BAS2 receives the IPv6 address acquisition request from the client terminal and sends the request to the policy BAS via the Layer 2 EVPN domain.

[0220] Step 705: Whether the BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix is ​​determined based on the policy. If so, proceed to step 708. If not, proceed to step 706.

[0221] Step 706: Bind the IPv6 prefixes corresponding to the number of hosts in the Layer 2 EVPN domain corresponding to each customer and publish them through a routing announcement message.

[0222] Step 707, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2;

[0223] Step 708 , BAS1 or BAS2 sends the IPv6 prefix to the client terminal via a DHCPv6 ND or SLAAC message through the Layer 2 VLAN domain;

[0224] Step 709: After receiving the IPv6 prefix, the client terminal automatically generates an IPv6 address according to the EUI64+prefix+DHCP ND or EUI64+prefix+SLAAC method;

[0225] Step 710: The client terminal constructs an uplink message, and the gateway sends it to the client's Layer 2 CE on the policy BAS.

[0226] Step 711: The client's Layer 2 CE receives the uplink message and sends it to BAS1 or BAS2 according to the HASH load balancing algorithm.

[0227] Step 712: BAS1 or BAS2 receives the uplink message and sends the uplink message to the policy BAS via the Layer 2 EVPN domain.

[0228] Step 713: The policy BAS sends the uplink message to the visitor BAS according to the IPv6 routing table.

[0229] Step 714: The visitor receives the customer service message.

[0230] In some embodiments, the system is also used to implement a coordinated disaster recovery process for an IPv6 Internet dedicated line in the downstream direction.

[0231] Figure 12 A schematic diagram of the downlink process of the IPv6 Internet dedicated line disaster recovery collaborative implementation system for the client-side Layer 2 CE provided in the embodiment of the present application is shown as follows: Figure 12 As shown, where:

[0232] In response to receiving the response message from the visitor, the guest BAS sends the response message to the policy BAS by searching the IPv6 routing table;

[0233] The policy BAS verifies based on the IPv6 adjacency table whether the client MAC address was accessed from BAS1 or learned from BAS2;

[0234] Based on whether the client MAC address is learned from BAS1 or BAS2, the system sends a response message to the CE.

[0235] In response to receiving the response message, the CE forwards the response message to the client terminal.

[0236] In some embodiments, based on whether the client MAC address is learned from BAS1 or BAS2, a response message is sent to the CE, specifically including:

[0237] If learned from BAS1, BAS1 sends a response message to CE along the left path;

[0238] If learned from BAS2, BAS2 sends a response message to CE along the right path.

[0239] Specifically, Figure 13 Another schematic diagram of the downlink process of the IPv6 Internet dedicated line disaster recovery collaborative implementation system for the client-side Layer 2 CE provided in the embodiment of the present application is as follows Figure 13 As shown, specifically including:

[0240] Step 801: The visitor sends a response message to the dedicated line customer;

[0241] Step 802: The visitor BAS receives the response message;

[0242] Step 803: The guest BAS searches the IPv6 routing table and sends a response message to the policy BAS.

[0243] Step 804: The policy BAS checks the IPv6 adjacency table to confirm whether the client MAC address was accessed from BAS1 or learned from BAS2.

[0244] Step 805: Based on whether the client MAC address is learned from BAS1 or BAS2, if it is learned from BAS1, proceed to step 807. If it is learned from BAS2, proceed to step 806.

[0245] Step 806: BAS2 sends the downlink message to the customer CE along the right path;

[0246] Step 807: BAS1 sends the downlink message to the customer CE along the left path;

[0247] Step 808: The client CE receives the downlink message.

[0248] Step 809: The client CE sends the downlink message to the client terminal;

[0249] Step 810: The client terminal receives a downlink message.

[0250] Based on the above system, the present application provides a method for implementing disaster recovery collaboration for an IPv6 Internet dedicated line. The client terminal is provided with three layers of CE. The method is used to implement a disaster recovery collaboration process for an IPv6 Internet dedicated line in the uplink direction. The method includes:

[0251] In response to the CE sending an IPv6 prefix request message to BAS1 or BAS2 using the IPv6 address autoconfiguration method, BAS1 or BAS2 binds the downstream Layer 2 interface to the Layer 2 VLAN corresponding to the customer, associates the downstream Layer 2 interface to the Layer 2 Ethernet virtual private network (EVPN) domain, and sends the IPv6 address acquisition request to the policy BAS through the Layer 2 EVPN domain.

[0252] Based on whether the policy BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2. BAS1 or BAS2 then uses the Dynamic Host Configuration Protocol (DHCPv6) Neighbor Discovery (ND) and DHCPv6 Prefix Delegation (PD) message to send the IPv6 prefix to the CE via the Layer 2 VLAN domain.

[0253] The CE uses the ND prefix for the CE uplink port and the PD prefix for the CE downlink port. This allows the client terminal to obtain an IPv6 prefix from the CE through DHCPv6, generate an IPv6 address, and construct an uplink message to send to the CE.

[0254] In response to receiving an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 using the default equal-cost routing method according to the HASH load balancing algorithm;

[0255] In response to receiving the uplink message, BAS1 or BAS2 sends the uplink message to the policy BAS through the Layer 2 EVPN domain, so that the policy BAS sends the uplink message to the guest BAS according to the IPv6 routing table.

[0256] In some embodiments, the method is further used to implement a coordinated disaster recovery implementation process for an IPv6 Internet dedicated line in the downlink direction, and the method further includes:

[0257] In response to receiving the response message from the visitor, the guest BAS searches the IPv6 routing table and sends the response message to the policy BAS;

[0258] The policy BAS verifies based on the IPv6 adjacency table whether the client MAC address was accessed from BAS1 or learned from BAS2;

[0259] Based on whether the client MAC address is learned from BAS1 or BAS2, the system sends a response message to the CE.

[0260] In response to receiving the response message, the CE forwards the response message to the client terminal.

[0261] Based on the above system, the present application provides a method for implementing disaster recovery collaboration for an IPv6 Internet dedicated line. The client terminal is provided with a Layer 2 CE. The method is used to implement a disaster recovery collaboration process for an IPv6 Internet dedicated line in the uplink direction. The method includes:

[0262] In response to the client terminal sending an IPv6 prefix request message to BAS1 or BAS2 through DHCPv6 or stateless address autoconfiguration (SLAAC), BAS1 or BAS2 binds the downstream Layer 2 interface to the Layer 2 VLAN corresponding to the client, associates the downstream Layer 2 interface to the Layer 2 Ethernet virtual private network (EVPN) domain, and sends the IPv6 address acquisition request to the policy BAS through the Layer 2 EVPN domain;

[0263] Based on whether the policy BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2, so that BAS1 or BAS2 sends the IPv6 prefix to the client terminal through the Layer 2 VLAN domain using a Dynamic Host Configuration Protocol (DHCPv6) Neighbor Discovery (ND) or SLAAC message.

[0264] The client terminal generates an IPv6 address using the extended unique identifier (64-bit EUI64) + prefix + DHCP ND or EUI64 + prefix + SLAAC, and constructs an uplink message to send to the CE.

[0265] In response to receiving an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 according to the HASH load balancing algorithm;

[0266] In response to receiving the uplink message, BAS1 or BAS2 sends the uplink message to the policy BAS through the Layer 2 EVPN domain, so that the policy BAS sends the uplink message to the guest BAS according to the IPv6 routing table.

[0267] In some embodiments, the method is further used to implement a coordinated disaster recovery implementation process for an IPv6 Internet dedicated line in the downlink direction, and the method further includes:

[0268] In response to receiving the response message from the visitor, the guest BAS sends the response message to the policy BAS by searching the IPv6 routing table;

[0269] The policy BAS verifies based on the IPv6 adjacency table whether the client MAC address was accessed from BAS1 or learned from BAS2;

[0270] Based on whether the client MAC address is learned from BAS1 or BAS2, the system sends a response message to the CE.

[0271] In response to receiving the response message, the CE forwards the response message to the client terminal.

[0272] This application provides a system and method for implementing coordinated disaster recovery for dedicated internet lines. For client-side Layer 3 CE scenarios, this system can achieve bidirectional IPv6 load balancing between the access and aggregation layers. For client-side Layer 2 CE scenarios, this system can achieve bidirectional IPv6 load balancing between the access and aggregation layers. This application effectively implements disaster recovery for IPv6 dedicated internet lines and data center customers.

[0273] It should be understood that, although the various steps in the flowcharts of the above embodiments are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they may be performed in other orders. Moreover, at least a portion of the steps in the figure may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but may be performed at different times, and their execution order is not necessarily sequential, but may be performed in turn or alternately with other steps or at least a portion of sub-steps or stages of other steps.

[0274] It is understood that the above embodiments are merely exemplary embodiments for illustrating the principles of the present application, and the present application is not limited thereto. Those skilled in the art may make various modifications and improvements without departing from the spirit and substance of the present application, and such modifications and improvements are also considered to be within the scope of protection of the present application.

Claims

1. An IPv6 Internet dedicated line disaster recovery collaborative implementation system, characterized in that: The system includes: a customer terminal, a customer edge device CE, an access network, an aggregation switch SW, a broadband access server BAS, a core router CR, a visitor BAS, and a policy BAS; The client terminal is provided with three layers of CE, and the BAS includes BAS1 and BAS2. The system is used to implement the coordinated disaster recovery process of the IPv6 Internet dedicated line in the uplink direction, wherein: In response to the CE sending an IPv6 prefix request message to BAS1 or BAS2 using the IPv6 address autoconfiguration method, BAS1 or BAS2 binds the downstream Layer 2 interface to the Layer 2 VLAN corresponding to the customer, associates the downstream Layer 2 interface to the Layer 2 Ethernet virtual private network (EVPN) domain, and sends the IPv6 address acquisition request to the policy BAS through the Layer 2 EVPN domain. Based on whether the policy BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2. BAS1 or BAS2 then uses the Dynamic Host Configuration Protocol (DHCPv6) Neighbor Discovery (ND) and DHCPv6 Prefix Delegation (PD) message to send the IPv6 prefix to the CE via the Layer 2 VLAN domain. The CE uses the ND prefix for the CE uplink port and the PD prefix for the CE downlink port. This allows the client terminal to obtain an IPv6 prefix from the CE through DHCPv6, generate an IPv6 address, and construct an uplink message to send to the CE. In response to receiving an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 using the default equal-cost routing method according to the HASH load balancing algorithm; In response to receiving the uplink message, BAS1 or BAS2 sends the uplink message to the policy BAS through the Layer 2 EVPN domain, so that the policy BAS sends the uplink message to the guest BAS according to the IPv6 routing table.

2. The IPv6 Internet dedicated line disaster recovery collaborative implementation system according to claim 1, characterized in that: Based on whether the policy BAS is bound to a Layer 2 EVPN domain and an IPv6 prefix, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2. The following steps are performed: If it has been bound, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2; If not, the policy BAS binds the IPv6 prefixes of the corresponding number of hosts according to the Layer 2 EVPN domain corresponding to the customer, and sends the bound IPv6 prefixes to BAS1 or BAS2.

3. The IPv6 Internet dedicated line disaster recovery collaborative implementation system according to claim 1, characterized in that: The system is also used to implement a coordinated disaster recovery process for an IPv6 Internet dedicated line in the downstream direction, wherein: In response to receiving the response message from the visitor, the guest BAS searches the IPv6 routing table and sends the response message to the policy BAS; The policy BAS verifies based on the IPv6 adjacency table whether the client MAC address was accessed from BAS1 or learned from BAS2; Based on whether the client MAC address is learned from BAS1 or BAS2, the system sends a response message to the CE. In response to receiving the response message, the CE forwards the response message to the client terminal.

4. The IPv6 Internet dedicated line disaster recovery collaborative implementation system according to claim 3, characterized in that: Based on whether the client MAC address is learned from BAS1 or BAS2, a response message is sent to the CE. The details include: If learned from BAS1, BAS1 sends a response message to CE along the left path; If learned from BAS2, BAS2 sends a response message to CE along the right path.

5. An IPv6 Internet dedicated line disaster recovery collaborative implementation system, characterized in that: The system includes: a customer terminal, a customer edge device CE, an access network, an aggregation switch SW, a broadband access server BAS, a core router CR, a visitor BAS, and a policy BAS; The client terminal is provided with a layer 2 CE, and the BAS includes BAS1 and BAS2. The system is used to implement a coordinated disaster recovery process of an IPv6 Internet dedicated line in the uplink direction, wherein: In response to the client terminal sending an IPv6 prefix request message to BAS1 or BAS2 through DHCPv6 or stateless address autoconfiguration (SLAAC), BAS1 or BAS2 binds the downstream Layer 2 interface to the Layer 2 VLAN corresponding to the client, associates the downstream Layer 2 interface to the Layer 2 Ethernet virtual private network (EVPN) domain, and sends the IPv6 address acquisition request to the policy BAS through the Layer 2 EVPN domain; Based on whether the policy BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2, so that BAS1 or BAS2 sends the IPv6 prefix to the client terminal through the Layer 2 VLAN domain using a Dynamic Host Configuration Protocol (DHCPv6) Neighbor Discovery (ND) or SLAAC message. The client terminal generates an IPv6 address using the extended unique identifier (64-bit EUI64) + prefix + DHCP ND or EUI64 + prefix + SLAAC, and constructs an uplink message to send to the CE. In response to receiving an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 according to the HASH load balancing algorithm; In response to receiving the uplink message, BAS1 or BAS2 sends the uplink message to the policy BAS through the Layer 2 EVPN domain, so that the policy BAS sends the uplink message to the guest BAS according to the IPv6 routing table.

6. The IPv6 Internet dedicated line disaster recovery collaborative implementation system according to claim 5, characterized in that: Based on whether the policy BAS is bound to a Layer 2 EVPN domain and an IPv6 prefix, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2. The following steps are performed: If it has been bound, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2; If not, the policy BAS binds the IPv6 prefixes of the corresponding number of hosts according to the Layer 2 EVPN domain corresponding to the customer, and sends the bound IPv6 prefixes to BAS1 or BAS2.

7. The IPv6 Internet dedicated line disaster recovery collaborative implementation system according to claim 5, characterized in that: The system is also used to implement a coordinated disaster recovery process for an IPv6 Internet dedicated line in the downstream direction, wherein: In response to receiving the response message from the visitor, the guest BAS sends the response message to the policy BAS by searching the IPv6 routing table; The policy BAS verifies based on the IPv6 adjacency table whether the client MAC address was accessed from BAS1 or learned from BAS2; Based on whether the client MAC address is learned from BAS1 or BAS2, the system sends a response message to the CE. In response to receiving the response message, the CE forwards the response message to the client terminal.

8. The IPv6 Internet dedicated line disaster recovery collaborative implementation system according to claim 7, characterized in that: Based on whether the client MAC address is learned from BAS1 or BAS2, a response message is sent to the CE. The details include: If learned from BAS1, BAS1 sends a response message to CE along the left path; If learned from BAS2, BAS2 sends a response message to CE along the right path.

9. A method for realizing coordinated disaster recovery of an IPv6 Internet dedicated line, characterized in that: The client terminal is provided with three layers of CE. The method is used to implement a coordinated disaster recovery process of an IPv6 Internet dedicated line in the uplink direction. The method includes: In response to the CE sending an IPv6 prefix request message to BAS1 or BAS2 using the IPv6 address autoconfiguration method, BAS1 or BAS2 binds the downstream Layer 2 interface to the Layer 2 VLAN corresponding to the customer, associates the downstream Layer 2 interface to the Layer 2 Ethernet virtual private network (EVPN) domain, and sends the IPv6 address acquisition request to the policy BAS through the Layer 2 EVPN domain. Based on whether the policy BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2. BAS1 or BAS2 then uses the Dynamic Host Configuration Protocol (DHCPv6) Neighbor Discovery (ND) and DHCPv6 Prefix Delegation (PD) message to send the IPv6 prefix to the CE via the Layer 2 VLAN domain. The CE uses the ND prefix for the CE uplink port and the PD prefix for the CE downlink port. This allows the client terminal to obtain an IPv6 prefix from the CE through DHCPv6, generate an IPv6 address, and construct an uplink message to send to the CE. In response to receiving an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 using the default equal-cost routing method according to the HASH load balancing algorithm; In response to receiving the uplink message, BAS1 or BAS2 sends the uplink message to the policy BAS through the Layer 2 EVPN domain, so that the policy BAS sends the uplink message to the guest BAS according to the IPv6 routing table.

10. The method for realizing IPv6 Internet dedicated line disaster recovery collaboration according to claim 9, characterized in that: The method is also used to implement a coordinated disaster recovery process for an IPv6 Internet dedicated line in the downlink direction, and the method further comprises: In response to receiving the response message from the visitor, the guest BAS searches the IPv6 routing table and sends the response message to the policy BAS; The policy BAS verifies based on the IPv6 adjacency table whether the client MAC address was accessed from BAS1 or learned from BAS2; Based on whether the client MAC address is learned from BAS1 or BAS2, the system sends a response message to the CE. In response to receiving the response message, the CE forwards the response message to the client terminal.

11. A method for realizing coordinated disaster recovery of an IPv6 Internet dedicated line, characterized in that: The client terminal is provided with a Layer 2 CE. The method is used to implement a coordinated disaster recovery process of an IPv6 Internet dedicated line in the uplink direction. The method includes: In response to the client terminal sending an IPv6 prefix request message to BAS1 or BAS2 through DHCPv6 or stateless address autoconfiguration (SLAAC), BAS1 or BAS2 binds the downstream Layer 2 interface to the Layer 2 VLAN corresponding to the client, associates the downstream Layer 2 interface to the Layer 2 Ethernet virtual private network (EVPN) domain, and sends the IPv6 address acquisition request to the policy BAS through the Layer 2 EVPN domain; Based on whether the policy BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2, so that BAS1 or BAS2 sends the IPv6 prefix to the client terminal through the Layer 2 VLAN domain using a Dynamic Host Configuration Protocol (DHCPv6) Neighbor Discovery (ND) or SLAAC message. The client terminal generates an IPv6 address using the extended unique identifier (64-bit EUI64) + prefix + DHCP ND or EUI64 + prefix + SLAAC, and constructs an uplink message to send to the CE. In response to receiving an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 according to the HASH load balancing algorithm; In response to receiving the uplink message, BAS1 or BAS2 sends the uplink message to the policy BAS through the Layer 2 EVPN domain, so that the policy BAS sends the uplink message to the guest BAS according to the IPv6 routing table.

12. The method for realizing IPv6 Internet dedicated line disaster recovery collaboration according to claim 11, characterized in that: The method is also used to implement a coordinated disaster recovery process for an IPv6 Internet dedicated line in the downlink direction, and the method further comprises: In response to receiving the response message from the visitor, the guest BAS sends the response message to the policy BAS by searching the IPv6 routing table; The policy BAS verifies based on the IPv6 adjacency table whether the client MAC address was accessed from BAS1 or learned from BAS2; Based on whether the client MAC address is learned from BAS1 or BAS2, the system sends a response message to the CE. In response to receiving the response message, the CE forwards the response message to the client terminal.

Images