IPv6 (Internet Protocol Version 6) Internet private line disaster recovery collaborative implementation system and method

Abstract

The invention provides an IPv6 (Internet Protocol Version 6) Internet private line disaster recovery cooperation realization system and method, and the IPv6 disaster recovery cooperation realization process in the uplink direction comprises the steps: BAS1 or BAS2 sends an IPv6 address acquisition application to a strategy BAS through a two-layer EVPN domain; the strategy BAS sends the bound IPv6 prefix to the BAS1 or the BAS2; the CE uses the ND prefix for a CE uplink port, and uses the PD prefix for a CE downlink port; the CE sends the uplink message to the BAS1 or BAS2 in a default equivalent routing mode according to a HASH load sharing algorithm; and the BAS1 or BAS2 sends the uplink message to the policy BAS through the two-layer EVPN domain, so that the policy BAS sends the uplink message to the visitor BAS according to the IPv6 routing table. According to the invention, disaster recovery protection of IPv6 Internet private lines and data center clients can be effectively realized.

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 Internet dedicated lines based on broadband metropolitan area networks or intelligent metropolitan area networks to provide dedicated line services for accessing the Internet to government and enterprise industry customers or data centers. However, due to the lack of effective protection measures for Internet dedicated lines, when single-point failures occur in scenarios such as optical cable interruption, access line interruption, access layer equipment downtime, aggregation switch downtime, broadband access server, and service router, the services of government and enterprise industry customers and data center customers are affected and the communication of upper-layer applications is blocked.

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

[0004] Therefore, how to achieve disaster recovery coordination 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 the present application is to provide an IPv6 Internet dedicated line disaster recovery collaborative implementation system and method in view of the above-mentioned deficiencies in the prior art, so as to solve the problems existing 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 visitor BAS, and a policy BAS;

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

[0008] In response to CE sending an IPv6 prefix application message to BAS1 or BAS2 in an IPv6 address automatic configuration mode, BAS1 or BAS2 binds a Layer 2 VLAN corresponding to the customer to the Layer 2 interface, associates the Layer 2 interface to the Layer 2 Ethernet virtual private network EVPN domain, and sends an IPv6 address acquisition application 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 as a judgment condition, 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;

[0010] 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.

[0011] In response to receiving an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 through a default equal-cost routing method according to a HASH load sharing 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 is bound, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2;

[0015] If not bound, 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 also used to implement a coordinated implementation process of IPv6 Internet dedicated line disaster recovery in the downstream direction, wherein:

[0017] 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;

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

[0019] The response message is sent to the CE based on whether the customer MAC address is learned from BAS1 or BAS2.

[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 as a judgment condition, 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, a convergence switch SW, a broadband access server BAS, a core router CR, a visitor BAS, and a policy BAS;

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

[0026] In response to the client terminal sending an IPv6 prefix application 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 application to the policy BAS through the Layer 2 EVPN domain;

[0027] According to 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, so that BAS1 or BAS2 sends the IPv6 prefix to the client terminal through the Layer 2 VLAN domain through the Dynamic Host Configuration Protocol DHCPv6 Neighbor Discovery ND or SLAAC message;

[0028] The client terminal generates an IPv6 address according to the extended unique identifier 64-bit EUI64+prefix+DHCP ND or EUI64+prefix+SLAAC method, 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 sharing 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 is bound, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2;

[0033] If not bound, 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 also used to implement a coordinated implementation process of IPv6 Internet dedicated line disaster recovery 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 confirms based on the IPv6 adjacency table whether the client MAC address is accessed from BAS1 or learned from BAS2;

[0037] The response message is sent to the CE based on whether the customer MAC address is learned from BAS1 or BAS2.

[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 as a judgment condition, 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 realizing disaster recovery collaboration of an IPv6 Internet dedicated line, wherein a client terminal is provided with a three-layer CE, and the method is used to realize a disaster recovery collaboration realization process of an IPv6 Internet dedicated line in an uplink direction, and the method comprises:

[0043] In response to CE sending an IPv6 prefix application message to BAS1 or BAS2 in an IPv6 address automatic configuration mode, BAS1 or BAS2 binds a Layer 2 VLAN corresponding to the customer to the Layer 2 interface, associates the Layer 2 interface to the Layer 2 Ethernet virtual private network EVPN domain, and sends an IPv6 address acquisition application 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 as a judgment condition, 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;

[0045] 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.

[0046] In response to receiving an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 through a default equal-cost routing method according to a HASH load sharing 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 also used to implement a coordinated implementation process of IPv6 Internet dedicated line disaster recovery in the downstream direction, and the method further includes:

[0049] 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;

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

[0051] The response message is sent to the CE based on whether the customer MAC address is learned from BAS1 or BAS2.

[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 realizing disaster recovery collaboration of an IPv6 Internet dedicated line, wherein a client terminal is provided with a layer 2 CE, and the method is used to realize a disaster recovery collaboration realization process of an IPv6 Internet dedicated line in an uplink direction, and the method comprises:

[0054] In response to the client terminal sending an IPv6 prefix application 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 application to the policy BAS through the Layer 2 EVPN domain;

[0055] According to 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, so that BAS1 or BAS2 sends the IPv6 prefix to the client terminal through the Layer 2 VLAN domain through the Dynamic Host Configuration Protocol DHCPv6 Neighbor Discovery ND or SLAAC message;

[0056] The client terminal generates an IPv6 address according to the extended unique identifier 64-bit EUI64+prefix+DHCP ND or EUI64+prefix+SLAAC method, 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 sharing 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 also used to implement a coordinated implementation process of IPv6 Internet dedicated line disaster recovery in the downstream 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 confirms based on the IPv6 adjacency table whether the client MAC address is accessed from BAS1 or learned from BAS2;

[0062] The response message is sent to the CE based on whether the customer MAC address is learned from BAS1 or BAS2.

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

[0064] The present application provides a system and method for realizing disaster recovery collaboration of an IPv6 Internet dedicated line, the system comprising: 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 comprises BAS1 and BAS2, and the system is used to realize a disaster recovery collaboration process of an IPv6 Internet dedicated line in the upstream direction, wherein: in response to CE sending an application for an IPv6 prefix message to BAS1 or BAS2 in an automatic configuration mode of an IPv6 address, a downstream layer 2 interface of BAS1 or BAS2 is bound to a layer 2 VLAN corresponding to the customer, the downstream layer 2 interface is associated with a layer 2 Ethernet virtual private network EVPN domain, and an IPv6 address acquisition application is sent to the policy BAS through the layer 2 EVPN domain; a judgment condition is determined 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 through the Dynamic Host Configuration Protocol DHCPv6 Neighbor Discovery ND+DHCPv6 Prefix Delegation PD message; 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 CE through DHCPv6, generates an IPv6 address, and constructs an uplink message to send to CE; in response to receiving the uplink message from the client terminal, 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. The present application provides a system and method for realizing coordinated disaster recovery of Internet dedicated lines. For the three-layer CE scenario on the client side, the IPv6 effect of bidirectional load sharing between the access layer and the aggregation layer can be realized. For the two-layer CE scenario on the client side, the IPv6 effect of bidirectional load sharing between the access layer and the aggregation layer can be realized. The present application can effectively realize disaster recovery protection for IPv6 Internet dedicated 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 A schematic diagram of IPv4 / v6 in a dual aggregation layer active / standby scenario in the prior art;

[0069] Figure 4 A 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 direction flow of the IPv6 Internet dedicated line disaster recovery collaborative implementation system for the client-side three-layer CE provided in the embodiment of the present application;

[0071] Figure 6 Another schematic diagram of the uplink direction process of the IPv6 Internet dedicated line disaster recovery collaborative implementation system of the client-side three-layer CE provided in the embodiment of the present application;

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

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

[0074] Fig. 9 A schematic diagram of a system for implementing disaster recovery collaboration of an IPv6 Internet dedicated line for a layer 2 CE on the client side provided in an embodiment of the present application;

[0075] Fig.10 A schematic diagram of the uplink direction 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;

[0076] Fig.11 Another schematic diagram of the uplink direction process of the IPv6 Internet dedicated line disaster recovery collaborative implementation system of the client-side Layer 2 CE provided in the embodiment of the present application;

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

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

[0079] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring 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 mode 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 in the present application and the various features in the embodiments can be combined with each other.

[0083] It can be understood that, for the convenience of description, the drawings of the present application only show the parts related to the present application, while the parts unrelated to the present 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. Among them, each box in the flowchart or block diagram may represent a unit, module, program segment, 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) is 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 a network that does not fully conform to the fully connected BGP peers.

[0099] EVPN (Ethernet VPN, Ethernet Virtual Private Network): 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 entry: used to store the correspondence between IP addresses and MAC addresses in the network.

[0102] MAC address (Media Access Control Address): MAC address is the physical address of a device, used to identify a network interface controller. The MAC address of each device is unique.

[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 the network.

[0106] ND (Neighbor Discovery): A 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] In addition, in a communication network, CE devices are usually responsible for connecting the internal network of an enterprise or individual to the PE (Provider Edge) device of a service provider. Depending on the design and requirements of the network, CE devices can be either Layer 3 devices 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), which are usually used to route data packets.

[0114] (1.2) Features:

[0115] Routing function: Layer 3 CE can run routing protocols (such as OSPF, BGP, EIGRP) and can exchange dynamic routes with the service provider's 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 usually 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, customers require higher autonomy and complex network configuration.

[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 on the Layer 2 network (the data link layer in the OSI model), mainly 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: Layer 2 CE forwards traffic to the service provider's network (usually PE equipment), which is responsible for routing.

[0127] ·Simple configuration: Layer 2 CE configuration is simple, no need to worry about IP routing, only need to set 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, E-LAN).

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

[0133]

[0134] In the prior art, methods for solving disaster recovery coordination between Internet dedicated lines and data center customers are mainly divided into two categories.

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

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

[0137] Among them, in the IPv4 application scenario, the Internet dedicated line and the data center customer CE equipment are converged to the same aggregation switch SW and the same 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 IPv4 address to different interconnected IPv4 addresses through static routing or dynamic routing to meet the customer's needs for accessing the Internet.

[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 method, 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 to meet the customer's need to access the Internet.

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

[0144] (II) The second method: using dual aggregation layer active / standby scenario IPv4 / v6.

[0145] Figure 3 Schematic diagram of IPv4 / v6 using dual convergence layer active / standby scenario in the prior art, as shown in FIG. Figure 3 As shown, the method is divided into an IPv4 application scenario and an IPv6 application scenario.

[0146] Among them, in the IPv4 application scenario, the Internet dedicated line and the data center customer CE equipment are converged to different aggregation switches SW, different broadband access servers BAS / service routers SR through two (or more) access network paths. In the downstream traffic, BAS uses two sub-interfaces to point the customer's business IPv4 address to different interconnected IPv4 addresses through static routing or dynamic routing to meet the customer's need to access the Internet.

[0147] In addition, in the IPv6 application scenario, the specific protection method is similar to that of IPv4. The Internet dedicated line and the data center customer CE equipment are respectively converged to different aggregation switches SW and broadband access servers BAS / service routers 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 to meet the customer's need to access the Internet.

[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 the single-aggregation layer load sharing IPV4 / 6 scenario, the aggregation layer switch SW, broadband access server BAS, and service router SR have single point risks. If a failure occurs or the service is cut off or upgraded, all services will be blocked.

[0151] (2) In the dual aggregation layer active / standby scenario, IPv4 / v6 can only achieve active / standby, but not load sharing.

[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), there are risks such as large workload, easy errors, and complex reading and writing when deploying a large number of Internet dedicated lines and data centers;

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

[0154] In the field of Internet private lines and data center customers, the above problems are prominent, and the existing solutions cannot completely solve the above problems. The market needs to provide customers with disaster recovery and collaborative network services with higher reliability and more secure business operations to solve these problems at this stage.

[0155] Based on the above defects, this application proposes an IPv6 Internet dedicated line disaster recovery collaborative implementation system and method, which is divided into two IPv6 solutions: one with three-layer CE on the client side and the other with two-layer CE on the client side. Specifically, it includes:

[0156] (1) A system and method for bidirectional load balancing IPv6 at dual aggregation layers of three-layer CE on the client side. The client-side upstream traffic is connected to different aggregation switches SW, different broadband access servers BAS and service routers SR from different access layers through an equal-cost default routing path, and then connected to a centralized or distributed policy BAS device through 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 through the "EUI64+prefix+DHCP ND method", and the CE's downstream terminal automatically obtains a fixed IPv6 prefix and generates an IPv6 address through the "EUI64+prefix+DHCP PD method". The 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, and through different access layers, the traffic is downstream to the client side. The bidirectional load balancing IPv6 effect of the access layer and the aggregation layer can be achieved.

[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 "EUI64+prefix+DHCP ND" or "EUI64+prefix+SLAAC", and then connected to the centrally or distributedly deployed policy BAS device through the Layer 2 EVPN domain to automatically obtain an IPv6 address. Internet-side downstream traffic passes through the centrally or distributedly deployed 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, and through different access layers, the traffic is downstream to the client side. The bidirectional load balancing IPv6 effect of the access layer and the aggregation layer can be achieved.

[0158] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. 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 A 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, Figure 5 The schematic diagram of the uplink direction flow of the IPv6 Internet dedicated line disaster recovery collaborative implementation system of the client-side three-layer CE 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 visitor BAS, and a policy BAS;

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

[0161] In response to CE sending an IPv6 prefix application message to BAS1 or BAS2 in an IPv6 address automatic configuration mode, BAS1 or BAS2 binds a Layer 2 VLAN corresponding to the customer to the Layer 2 interface, associates the Layer 2 interface to the Layer 2 Ethernet virtual private network EVPN domain, and sends an IPv6 address acquisition application 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 as a judgment condition, 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;

[0163] 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.

[0164] In response to receiving an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 through a default equal-cost routing method according to a HASH load sharing 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 is bound, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2;

[0168] If not bound, 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 IPv6 Internet dedicated line disaster recovery collaborative implementation system of the client-side three-layer CE provided in the embodiment of the present application is as follows Figure 6 As shown in the figure, the packet processing flow of the IPv6 customer dedicated line (Layer 3 CE) in the upstream direction specifically includes:

[0170] Step 501, the client CE uses the IPv6 address automatic configuration mode to send an IPv6 prefix application message to BAS1 or BAS2;

[0171] Step 502, the Layer 2 interface of BAS1 or BAS2 is bound to the Layer 2 VLAN (single or double VLAN) corresponding to the customer;

[0172] Step 503, BAS1 or BAS2 associates the downlink Layer 2 interface to 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 through the Layer 2 EVPN domain;

[0174] Step 505, whether the BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix is ​​used as a judgment condition according to the policy. If it is bound, go to step 508. If it is not bound, go to step 506;

[0175] Step 506, according to the Layer 2 EVPN domain corresponding to each customer, bind the IPv6 prefixes of the corresponding number of hosts 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 via 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 uses EUI64+prefix mode to automatically generate a fixed IPv6 address and construct an uplink message, and the gateway is on the policy BAS;

[0181] Step 512, the customer CE receives the uplink message and sends the uplink message to BAS1 and BAS2 through the default equal-cost routing method according to the HASH load sharing algorithm;

[0182] Step 513, BAS1 or BAS2 receives the uplink message and sends the uplink message to the policy BAS through 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 the IPv6 Internet dedicated line disaster recovery collaborative implementation process in the downstream direction.

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

[0187] 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;

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

[0189] The response message is sent to the CE based on whether the customer MAC address is learned from BAS1 or BAS2.

[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 as a judgment condition, 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 IPv6 Internet dedicated line disaster recovery collaborative implementation system of the client-side three-layer CE 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 is accessed from BAS1 or learned from BAS2;

[0199] Step 605, based on whether the client MAC 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] Fig. 9 A schematic diagram of a system for implementing disaster recovery collaboration of IPv6 Internet dedicated lines on the client side Layer 2 CE provided in an embodiment of the present application, Fig.10 The schematic diagram of the uplink direction 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: Fig. 9 as well as Fig.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 visitor BAS, and a policy BAS;

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

[0207] In response to the client terminal sending an IPv6 prefix application 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 application to the policy BAS through the Layer 2 EVPN domain;

[0208] According to 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, so that BAS1 or BAS2 sends the IPv6 prefix to the client terminal through the Layer 2 VLAN domain through the Dynamic Host Configuration Protocol DHCPv6 Neighbor Discovery ND or SLAAC message;

[0209] The client terminal generates an IPv6 address according to the extended unique identifier 64-bit EUI64+prefix+DHCP ND or EUI64+prefix+SLAAC method, 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 sharing 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 is bound, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2;

[0214] If not bound, 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, Fig.11 Another schematic diagram of the uplink process of the IPv6 Internet dedicated line disaster recovery collaborative implementation system of the client-side Layer 2 CE provided in the embodiment of the present application is as follows Fig.11 As shown in the figure, the packet processing flow of the IPv6 customer dedicated line (Layer 2 CE) in the uplink direction specifically includes:

[0216] Step 701, the client terminal sends an IPv6 prefix application message to BAS1 or BAS2 through DHCPv6 or SLAAC;

[0217] Step 702, the Layer 2 interface of BAS1 or BAS2 is bound to the Layer 2 VLAN (single or double VLAN) corresponding to the customer;

[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 through the Layer 2 EVPN domain;

[0220] Step 705, whether the BAS is bound to the Layer 2 EVPN domain and the IPv6 prefix is ​​used as a judgment condition according to the policy. If it is bound, go to step 708. If it is not bound, go to step 706;

[0221] Step 706: Bind the IPv6 prefixes of the corresponding number of hosts according to 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 through the Layer 2 VLAN domain via a DHCPv6 ND or SLAAC message;

[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 customer's Layer 2 CE receives the uplink message and sends it to BAS1 or BAS2 according to the HASH load sharing algorithm;

[0227] Step 712, BAS1 or BAS2 receives the uplink message and sends the uplink message to the policy BAS through 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 the IPv6 Internet dedicated line disaster recovery collaborative implementation process in the downstream direction.

[0231] Fig.12 A schematic diagram of the downlink process of the IPv6 Internet dedicated line disaster recovery collaborative implementation system of the client-side Layer 2 CE provided in the embodiment of the present application is shown in FIG. Fig.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 confirms based on the IPv6 adjacency table whether the client MAC address is accessed from BAS1 or learned from BAS2;

[0234] The response message is sent to the CE based on whether the customer MAC address is learned from BAS1 or BAS2.

[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 as a judgment condition, 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, Fig.13 Another schematic diagram of the downlink process of the IPv6 Internet dedicated line disaster recovery collaborative implementation system of the client-side Layer 2 CE provided in the embodiment of the present application is as follows Fig.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 is accessed from BAS1 or learned from BAS2;

[0244] Step 805, based on whether the client MAC is learned from BAS1 or BAS2 as a judgment condition, if it is learned from BAS1, then go to step 807. If it is learned from BAS2, then go 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 an IPv6 Internet dedicated line disaster recovery collaborative implementation method, the client terminal is provided with a three-layer CE, the method is used to implement the IPv6 Internet dedicated line disaster recovery collaborative implementation process in the uplink direction, the method includes:

[0251] In response to CE sending an IPv6 prefix application message to BAS1 or BAS2 in an IPv6 address automatic configuration mode, BAS1 or BAS2 binds a Layer 2 VLAN corresponding to the customer to the Layer 2 interface, associates the Layer 2 interface to the Layer 2 Ethernet virtual private network EVPN domain, and sends an IPv6 address acquisition application 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 as a judgment condition, 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;

[0253] 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.

[0254] In response to receiving an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 through a default equal-cost routing method according to a HASH load sharing 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 also used to implement a coordinated implementation process of IPv6 Internet dedicated line disaster recovery in the downstream direction, and the method further includes:

[0257] 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;

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

[0259] The response message is sent to the CE based on whether the customer MAC address is learned from BAS1 or BAS2.

[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 an IPv6 Internet dedicated line disaster recovery collaborative implementation method, the client terminal is provided with a second layer CE, the method is used to implement the IPv6 Internet dedicated line disaster recovery collaborative implementation process in the uplink direction, the method includes:

[0262] In response to the client terminal sending an IPv6 prefix application 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 application to the policy BAS through the Layer 2 EVPN domain;

[0263] According to 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, so that BAS1 or BAS2 sends the IPv6 prefix to the client terminal through the Layer 2 VLAN domain through the Dynamic Host Configuration Protocol DHCPv6 Neighbor Discovery ND or SLAAC message;

[0264] The client terminal generates an IPv6 address according to the extended unique identifier 64-bit EUI64+prefix+DHCP ND or EUI64+prefix+SLAAC method, 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 sharing 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 also used to implement a coordinated implementation process of IPv6 Internet dedicated line disaster recovery in the downstream 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 confirms based on the IPv6 adjacency table whether the client MAC address is accessed from BAS1 or learned from BAS2;

[0270] The response message is sent to the CE based on whether the customer MAC address is learned from BAS1 or BAS2.

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

[0272] The present application provides a system and method for realizing coordinated disaster recovery of Internet dedicated lines. For the three-layer CE scenario on the client side, the IPv6 effect of bidirectional load sharing between the access layer and the aggregation layer can be realized. For the two-layer CE scenario on the client side, the IPv6 effect of bidirectional load sharing between the access layer and the aggregation layer can be realized. The present application can effectively realize disaster recovery protection for IPv6 Internet dedicated lines and data center customers.

[0273] It should be understood that, although the various steps in the flowcharts in the above-described embodiments are sequentially displayed according to the indications of the arrows, these steps are not necessarily executed sequentially in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and they can be executed in other orders. Moreover, at least a portion of the steps in the figure may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily to be carried out sequentially, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0274] It is to be understood that the above embodiments are merely exemplary embodiments used to illustrate the principles of the present application, but the present application is not limited thereto. For those skilled in the art, various modifications and improvements can be made without departing from the spirit and substance of the present application, and these 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 comprises: 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, the BAS includes BAS1 and BAS2, and the system is used to implement the coordinated disaster recovery implementation process of the IPv6 Internet dedicated line in the uplink direction, wherein: In response to CE sending an IPv6 prefix application message to BAS1 or BAS2 in an IPv6 address automatic configuration mode, BAS1 or BAS2 binds a Layer 2 VLAN corresponding to the customer to the Layer 2 interface, associates the Layer 2 interface to the Layer 2 Ethernet virtual private network EVPN domain, and sends an IPv6 address acquisition application 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 as a judgment condition, 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; 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 an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 through a default equal-cost routing method according to a HASH load sharing 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 the Layer 2 EVPN domain and the IPv6 prefix, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2. Specifically, the following steps are performed: If it is bound, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2; If not bound, 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 the IPv6 Internet dedicated line disaster recovery collaborative implementation process 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 confirms based on the IPv6 adjacency table whether the client MAC address is accessed from BAS1 or learned from BAS2; The response message is sent to the CE based on whether the customer MAC address is learned from BAS1 or BAS2. 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. Specifically, the following steps are performed: 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 comprises: 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, the BAS includes BAS1 and BAS2, and the system is used to implement the coordinated disaster recovery implementation process of the IPv6 Internet dedicated line in the uplink direction, wherein: In response to the client terminal sending an IPv6 prefix application 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 application to the policy BAS through the Layer 2 EVPN domain; According to 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, so that BAS1 or BAS2 sends the IPv6 prefix to the client terminal through the Layer 2 VLAN domain through the Dynamic Host Configuration Protocol DHCPv6 Neighbor Discovery ND or SLAAC message; The client terminal generates an IPv6 address according to the extended unique identifier 64-bit EUI64+prefix+DHCP ND or EUI64+prefix+SLAAC method, 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 sharing 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 the Layer 2 EVPN domain and the IPv6 prefix, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2. Specifically, the following steps are performed: If it is bound, the policy BAS sends the bound IPv6 prefix to BAS1 or BAS2; If not bound, 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 the IPv6 Internet dedicated line disaster recovery collaborative implementation process 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 confirms based on the IPv6 adjacency table whether the client MAC address is accessed from BAS1 or learned from BAS2; The response message is sent to the CE based on whether the customer MAC address is learned from BAS1 or BAS2. 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. Specifically, the following steps are performed: 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, and the method is used to implement the coordinated implementation process of disaster recovery of IPv6 Internet dedicated lines in the uplink direction, and the method includes: In response to CE sending an IPv6 prefix application message to BAS1 or BAS2 in an IPv6 address automatic configuration mode, BAS1 or BAS2 binds a Layer 2 VLAN corresponding to the customer to the Layer 2 interface, associates the Layer 2 interface to the Layer 2 Ethernet virtual private network EVPN domain, and sends an IPv6 address acquisition application 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 as a judgment condition, 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; 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 an uplink message from a client terminal, the CE sends the uplink message to BAS1 or BAS2 through a default equal-cost routing method according to a HASH load sharing 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 implementation process of an IPv6 Internet dedicated line in a downstream 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 confirms based on the IPv6 adjacency table whether the client MAC address is accessed from BAS1 or learned from BAS2; The response message is sent to the CE based on whether the customer MAC address is learned from BAS1 or BAS2. 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, and the method is used to implement the coordinated implementation process of disaster recovery of an IPv6 Internet dedicated line in the uplink direction, and the method comprises: In response to the client terminal sending an IPv6 prefix application 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 application to the policy BAS through the Layer 2 EVPN domain; According to 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, so that BAS1 or BAS2 sends the IPv6 prefix to the client terminal through the Layer 2 VLAN domain through the Dynamic Host Configuration Protocol DHCPv6 Neighbor Discovery ND or SLAAC message; The client terminal generates an IPv6 address according to the extended unique identifier 64-bit EUI64+prefix+DHCP ND or EUI64+prefix+SLAAC method, 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 sharing 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 implementation process of an IPv6 Internet dedicated line in a downstream 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 confirms based on the IPv6 adjacency table whether the client MAC address is accessed from BAS1 or learned from BAS2; The response message is sent to the CE based on whether the customer MAC address is learned from BAS1 or BAS2. In response to receiving the response message, the CE forwards the response message to the client terminal.

Images