IPv4 Internet private line disaster recovery collaborative implementation system and method

Abstract

The invention provides an IPv4 Internet private line disaster recovery cooperation realization system and method, and the method comprises the steps: a CE responds to an uplink message received from a client terminal, carries out the load sharing uplink through equivalent default, and an access network and a convergence switch carry out the uplink of the uplink message through a two-layer VLAN; in response to the received uplink message, the BAS1 and the BAS2 release a border gateway protocol (BGP) route carrying a load sharing characteristic to the CR according to a judgment condition that whether the load sharing characteristic is deployed when the BAS releases the route; the CR responds to the received BGP route and issues a customer service route to other BASs in the network; the visitor BAS responds to the received customer service route, two equivalent routes matched with the BAS1 and the BS2 are placed in the routing table, and the visitor BAS is used for forwarding the service message to the network where the visitor is located. According to the invention, disaster recovery protection of IPv4 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 IPv4 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 IPv4 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 a system and method for realizing disaster recovery collaboration of an IPv4 Internet dedicated line 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 IPv4 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, and a visitor 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 IPv4 Internet dedicated line in the uplink direction, wherein:

[0008] In response to receiving the uplink message from the client terminal, the CE performs load sharing uplink by equal-cost default, and the access network and aggregation switch transmit the uplink message uplink through the Layer 2 VLAN;

[0009] In response to receiving the uplink message, BAS1 and BAS2 publish Border Gateway Protocol (BGP) routes carrying the load balancing feature to CR based on whether the load balancing feature is deployed when the BAS publishes the route as a judgment condition;

[0010] In response to receiving the BGP route, the CR publishes the customer service route to other BASs in the network;

[0011] In response to receiving the customer service route, the visitor BAS places two equal-cost routes matching BAS1 and BS2 in the routing table. The visitor BAS is used to forward the service message to the visitor's network.

[0012] In some embodiments, in response to receiving an uplink message, BAS1 and BAS2 publish a Border Gateway Protocol (BGP) route carrying a load balancing feature to the CR based on whether the load balancing feature is deployed when the BAS publishes the route as a judgment condition, specifically including:

[0013] If the load balancing feature is deployed, Border Gateway Protocol (BGP) routes carrying the load balancing feature are advertised to the CR.

[0014] If the load balancing feature is not deployed, the BAS creates an access control list to match the IPv4 range of the customer dedicated line, writes a route publishing policy, and publishes Border Gateway Protocol (BGP) routes with the load balancing feature to the CR.

[0015] In some embodiments, the system is also used to implement a coordinated disaster recovery implementation process of an IPv4 Internet dedicated line in the downstream direction, wherein:

[0016] In response to receiving the response message from the visitor, the visitor BAS forwards the response message to BAS1 or BAS2 via CR according to the HASH distribution algorithm, based on the target IP address of the customer or the source address of the visitor, in accordance with the load sharing method;

[0017] In response to receiving the response message, BAS1 or BAS2 sends the response message to the corresponding uplink port of CE according to the static / dynamic routing mode;

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

[0019] In a second aspect, the present application provides an IPv4 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, and a visitor BAS;

[0020] 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 IPv4 Internet dedicated line in the uplink direction, wherein:

[0021] In response to the client terminal sending an uplink message, the downlink service sub-interfaces of BAS1 and BAS2 belong to the same Layer 2 Ethernet virtual private network EVPN domain, and BAS1 and BAS2 run the virtual router redundancy protocol VRRP heartbeat through the Layer 2 EVPN domain;

[0022] Based on whether the BAS is the primary one, VRRP is used as a judgment condition to send the uplink message to the corresponding BAS;

[0023] Advertise Border Gateway Protocol (BGP) routes carrying the load balancing feature to the CR based on whether the load balancing feature is deployed when the BAS advertises routes.

[0024] In response to receiving the BGP route, the CR publishes the customer service route to other BASs in the network;

[0025] In response to receiving the customer service route, the visitor BAS places two equal-cost routes matching BAS1 and BS2 in the routing table. The visitor BAS is used to forward the service message to the visitor's network.

[0026] In some embodiments, based on whether the BAS is the primary VRRP as a judgment condition, an uplink message is sent to the corresponding BAS, specifically including:

[0027] If BAS1 is the active VRRP, the uplink message is sent to BAS1 through the left link;

[0028] If BAS2 is the active VRRP, the uplink message is sent to BAS2 through the right link.

[0029] In some embodiments, based on whether the load balancing feature is deployed when the BAS publishes the route as a judgment condition, publishing the Border Gateway Protocol BGP route carrying the load balancing feature to the CR specifically includes:

[0030] If the load balancing feature is deployed, Border Gateway Protocol (BGP) routes carrying the load balancing feature are advertised to the CR.

[0031] If the load balancing feature is not deployed, the BAS creates an access control list to match the IPv4 range of the customer dedicated line, writes a route publishing policy, and publishes Border Gateway Protocol (BGP) routes with the load balancing feature to the CR.

[0032] In some embodiments, the system is also used to implement a coordinated disaster recovery implementation process of an IPv4 Internet dedicated line in the downstream direction, wherein:

[0033] In response to receiving the response message from the visitor, the visitor BAS forwards the response message to BAS1 or BAS2 via CR according to the HASH distribution algorithm, based on the target IP address of the customer or the source address of the visitor, in accordance with the load sharing method;

[0034] Based on whether the visitor BAS sends the response message to BAS1 or BAS2 as a judgment condition, the response message is sent to the client terminal through the corresponding BAS.

[0035] In some embodiments, according to whether the visitor BAS sends the response message to BAS1 or BAS2 as a judgment condition, sending the response message to the client terminal through the corresponding BAS specifically includes:

[0036] If the visitor BAS sends a response message to BAS1, BAS1 sends a downlink message to the client terminal according to the address resolution protocol ARP table entry;

[0037] If the visitor BAS sends a response message to BAS2, BAS2 sends an ARP probe message to the client terminal; in response to receiving the terminal media access control MAC address and Internet Protocol IP address returned by the client terminal based on the ARP probe message, BAS2 establishes a corresponding ARP table entry and sends a downlink message to the client terminal according to the ARP table entry.

[0038] In a third aspect, the present application provides a method for realizing disaster recovery collaboration of an IPv4 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 process of an IPv4 Internet dedicated line in an uplink direction, and the method comprises:

[0039] In response to receiving the uplink message from the client terminal, the CE performs load sharing uplink by equal-cost default, and the access network and aggregation switch transmit the uplink message uplink through the Layer 2 VLAN;

[0040] In response to receiving the uplink message, BAS1 and BAS2 publish Border Gateway Protocol (BGP) routes carrying the load balancing feature to CR based on whether the load balancing feature is deployed when the BAS publishes the route as a judgment condition;

[0041] In response to receiving the BGP route, the CR publishes the customer service route to other BASs in the network;

[0042] In response to receiving the customer service route, the visitor BAS places two equal-cost routes matching BAS1 and BS2 in the routing table. The visitor BAS is used to forward the service message to the visitor's network.

[0043] In some embodiments, the method is also used to implement a coordinated implementation process of IPv4 Internet dedicated line disaster recovery in the downstream direction, and the method further includes:

[0044] In response to receiving the response message from the visitor, the visitor BAS forwards the response message to BAS1 or BAS2 via CR according to the HASH distribution algorithm, based on the target IP address of the customer or the source address of the visitor, in accordance with the load sharing method;

[0045] In response to receiving the response message, BAS1 or BAS2 sends the response message to the corresponding uplink port of CE according to the static / dynamic routing mode;

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

[0047] In a fourth aspect, the present application provides a method for realizing disaster recovery collaboration of an IPv4 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 IPv4 Internet dedicated line in an uplink direction, and the method comprises:

[0048] In response to the client terminal sending an uplink message, the downlink service sub-interfaces of BAS1 and BAS2 belong to the same Layer 2 Ethernet virtual private network EVPN domain, and BAS1 and BAS2 run the virtual router redundancy protocol VRRP heartbeat through the Layer 2 EVPN domain;

[0049] Based on whether the BAS is the primary one, VRRP is used as a judgment condition to send the uplink message to the corresponding BAS;

[0050] Advertise Border Gateway Protocol (BGP) routes carrying the load balancing feature to the CR based on whether the load balancing feature is deployed when the BAS advertises routes.

[0051] In response to receiving the BGP route, the CR publishes the customer service route to other BASs in the network;

[0052] In response to receiving the customer service route, the visitor BAS places two equal-cost routes matching BAS1 and BS2 in the routing table. The visitor BAS is used to forward the service message to the visitor's network.

[0053] In some embodiments, the method is also used to implement a coordinated implementation process of IPv4 Internet dedicated line disaster recovery in the downstream direction, and the method further includes:

[0054] In response to receiving the response message from the visitor, the visitor BAS forwards the response message to BAS1 or BAS2 via CR according to the HASH distribution algorithm, based on the target IP address of the customer or the source address of the visitor, in accordance with the load sharing method;

[0055] Based on whether the visitor BAS sends the response message to BAS1 or BAS2 as a judgment condition, the response message is sent to the client terminal through the corresponding BAS.

[0056] The present application provides a system and method for realizing disaster recovery collaboration of IPv4 Internet dedicated lines, 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, and a visitor 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 the disaster recovery collaboration realization process of IPv4 Internet dedicated lines in the upstream direction, wherein: CE responds to receiving an upstream message from the customer terminal, and performs load sharing upstream by equal default, and the access network and the aggregation switch upstream the upstream message through the second-layer VLAN; BAS1 and BAS2 respond to receiving the upstream message, and according to whether the load sharing feature is deployed when the BAS publishes the route as a judgment condition, publish the Border Gateway Protocol BGP route carrying the load sharing feature to the CR; CR responds to receiving the BGP route, and publishes the customer service route to other BAS in the network; the visitor BAS responds to receiving the customer service route, and places two equal-cost routes matching BAS1 and BS2 in the routing table, and the visitor BAS is used to forward the service message to the visitor's network. The present application provides a system and method for realizing disaster recovery coordination of IPv4 Internet dedicated lines. For the three-layer CE scenario on the client side, the two-way load sharing IPv4 effect of access layer and aggregation layer can be realized. For the two-layer CE scenario on the client side, the upstream traffic primary and backup disaster recovery and the downstream traffic load sharing IPv4 effect can be realized. The present application can effectively realize disaster recovery protection for IPv4 Internet dedicated lines and data center customers. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0060] Figure 3 A schematic diagram of IPv4 / v6 in a dual aggregation layer active / standby scenario in the prior art;

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

[0062] Figure 5 A schematic diagram of the uplink direction flow of the IPv4 Internet dedicated line disaster recovery collaborative implementation system for the client-side three-layer CE provided in the embodiment of the present application;

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

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

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

[0066] Fig. 9 A schematic diagram of a system for implementing disaster recovery collaboration of IPv4 Internet dedicated lines for Layer 2 CE on the client side provided in an embodiment of the present application;

[0067] Fig.10 A schematic diagram of the uplink direction flow of the IPv4 Internet dedicated line disaster recovery collaborative implementation system for the client-side Layer 2 CE provided in an embodiment of the present application;

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

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

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

[0071] 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0091] EVPN (Ethernet VPN, Ethernet Virtual Private Network): A VPN technology used to provide Ethernet services on Layer 2 and Layer 3 networks.

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

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

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

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

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

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

[0098] ND (Neighbor Discovery): A part of the IPv6 protocol used for node discovery and automatic configuration.

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

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

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

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

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

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

[0105] (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.

[0106] (1.2) Features:

[0107] 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).

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

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

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

[0111] (1.3) Applicable scenarios:

[0112] Large enterprise networks, customers require higher autonomy and complex network configuration.

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

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

[0115] (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.

[0116] (2.2) Features:

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

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

[0119] · Simple configuration: Layer 2 CE configuration is simple, no need to worry about IP routing, only need to set VLAN or port mapping.

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

[0121] (2.3) Applicable scenarios:

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

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

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

[0125]

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

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

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

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

[0130] 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:

[0131] (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.

[0132] (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.

[0133] (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.

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

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

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

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

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

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

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

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

[0142] (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.

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

[0144] (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;

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

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

[0147] Based on the above defects, this application proposes an IPv4 Internet dedicated line disaster recovery collaborative implementation system and method, which is divided into two IPv4 solutions: a three-layer CE on the client side and a two-layer CE on the client side, specifically including:

[0148] (1) A system and method for dual-aggregation layer bidirectional load sharing IPv4 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 or service routers SR from different access layers through an equal-cost default routing path. The Internet-side downstream traffic enters different aggregation switches SW through different broadband access servers BAS and service routers SR (load sharing), and then flows downstream to the client side through different access layers. The bidirectional load sharing IPv4 effect of the access layer and the aggregation layer can be achieved.

[0149] (2) A system and method for unidirectional load sharing IPv4 at dual aggregation layers of Layer 2 CE on the client side. The client-side upstream traffic enters the primary access layer through the default gateway in a unidirectional disaster recovery manner, and then connects to the primary aggregation switch SW, the primary broadband access server BAS, and the service router SR. The Internet-side downstream traffic enters different aggregation switches SW through different broadband access servers BAS and service routers SR (load sharing), and then flows downstream to the client side through different access layers. The upstream traffic primary-secondary disaster recovery and downstream traffic load sharing IPv4 effects can be achieved.

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

[0151] Figure 4 A schematic diagram of a client-side three-layer CE IPv4 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 of the system for realizing IPv4 Internet dedicated line disaster recovery collaboration of the client-side three-layer CE provided in the embodiment of the present application is as follows: Figure 4 as well as Figure 5 As shown, the present application provides an IPv4 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, and a visitor BAS;

[0152] 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 IPv4 Internet dedicated line in the uplink direction, wherein:

[0153] In response to receiving the uplink message from the client terminal, the CE performs load sharing uplink by equal-cost default, and the access network and aggregation switch transmit the uplink message uplink through the Layer 2 VLAN;

[0154] In response to receiving the uplink message, BAS1 and BAS2 publish Border Gateway Protocol (BGP) routes carrying the load balancing feature to CR based on whether the load balancing feature is deployed when the BAS publishes the route as a judgment condition;

[0155] In response to receiving the BGP route, the CR publishes the customer service route to other BASs in the network;

[0156] In response to receiving the customer service route, the visitor BAS places two equal-cost routes matching BAS1 and BS2 in the routing table. The visitor BAS is used to forward the service message to the visitor's network.

[0157] In some embodiments, in response to receiving an uplink message, BAS1 and BAS2 publish a Border Gateway Protocol (BGP) route carrying a load balancing feature to the CR based on whether the load balancing feature is deployed when the BAS publishes the route as a judgment condition, specifically including:

[0158] If the load balancing feature is deployed, Border Gateway Protocol (BGP) routes carrying the load balancing feature are advertised to the CR.

[0159] If the load balancing feature is not deployed, the BAS creates an access control list to match the IPv4 range of the customer dedicated line, writes a route publishing policy, and publishes Border Gateway Protocol (BGP) routes with the load balancing feature to the CR.

[0160] Specifically, Figure 6 Another schematic diagram of the uplink process of the IPv4 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 IPv4 customer dedicated line (Layer 3 CE) in the upstream direction specifically includes:

[0161] Step 101, the client terminal configures the service IPv4 and gateway, and sends an uplink message;

[0162] Step 102: CE receives the message and performs load sharing uplink by equal-cost default.

[0163] Step 103, the access network and the aggregation switch send the message uplink via the Layer 2 VLAN;

[0164] Step 104, BAS1 and BAS2 receive the uplink message;

[0165] Step 105, using whether the load balancing feature is deployed when the BAS publishes the route as a judgment condition, if the load balancing feature is deployed, proceed to step 109. If the load balancing feature is not deployed, proceed to step 106;

[0166] Step 106, BAS creates an access control list to match the IPv4 range of the customer dedicated line

[0167] Step 107, compile a routing publishing policy;

[0168] Step 108, BAS publishes BGP routes carrying load sharing features;

[0169] Step 109, CR receives the corresponding BGP route;

[0170] Step 110, the CR simultaneously publishes two customer service routes to other BASs in the network;

[0171] Step 111, the visitor BAS receives and places two equal-cost routes matching BAS1 and BS2 in the routing table;

[0172] Step 112, the visitor BAS forwards the service message to the visitor's network;

[0173] Step 113: The visitor receives the customer service message.

[0174] In some embodiments, the system is also used to implement the IPv4 Internet dedicated line disaster recovery collaborative implementation process in the downstream direction.

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

[0176] In response to receiving the response message from the visitor, the visitor BAS forwards the response message to BAS1 or BAS2 via CR according to the HASH distribution algorithm, based on the target IP address of the customer or the source address of the visitor, in accordance with the load sharing method;

[0177] In response to receiving the response message, BAS1 or BAS2 sends the response message to the corresponding uplink port of CE according to the static / dynamic routing mode;

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

[0179] Specifically, Figure 8 Another schematic diagram of the downlink process of the IPv4 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:

[0180] Step 201, the visitor sends a response message to the dedicated line customer;

[0181] Step 202: The visitor BAS receives a response message.

[0182] Step 203, the visitor BAS forwards the message to BAS1 or BAS2 via CR according to the HASH distribution algorithm, based on the target IP address of the customer or the source address of the visitor, in accordance with the load sharing method;

[0183] Step 204, BAS1 or BAS2 sends the message to the uplink port corresponding to the customer CE according to the static / dynamic routing mode;

[0184] Step 205, after receiving the message, the client CE forwards the message to the client terminal;

[0185] Step 206: The client terminal receives the downlink message.

[0186] Fig. 9 A schematic diagram of a system for implementing disaster recovery collaboration of IPv4 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 flow of the IPv4 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. 9 as well as Fig.10As shown, the present application provides an IPv4 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, and a visitor BAS;

[0187] 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 IPv4 Internet dedicated line in the uplink direction, wherein:

[0188] In response to the client terminal sending an uplink message, the downlink service sub-interfaces of BAS1 and BAS2 belong to the same Layer 2 Ethernet virtual private network EVPN domain, and BAS1 and BAS2 run the virtual router redundancy protocol VRRP heartbeat through the Layer 2 EVPN domain;

[0189] Based on whether the BAS is the primary one, VRRP is used as a judgment condition to send the uplink message to the corresponding BAS;

[0190] Advertise Border Gateway Protocol (BGP) routes carrying the load balancing feature to the CR based on whether the load balancing feature is deployed when the BAS advertises routes.

[0191] In response to receiving the BGP route, the CR publishes the customer service route to other BASs in the network;

[0192] In response to receiving the customer service route, the visitor BAS places two equal-cost routes matching BAS1 and BS2 in the routing table. The visitor BAS is used to forward the service message to the visitor's network.

[0193] In some embodiments, based on whether the BAS is the primary VRRP as a judgment condition, an uplink message is sent to the corresponding BAS, specifically including:

[0194] If BAS1 is the active VRRP, the uplink message is sent to BAS1 through the left link;

[0195] If BAS2 is the active VRRP, the uplink message is sent to BAS2 through the right link.

[0196] In some embodiments, based on whether the load balancing feature is deployed when the BAS publishes the route as a judgment condition, publishing the Border Gateway Protocol BGP route carrying the load balancing feature to the CR specifically includes:

[0197] If the load balancing feature is deployed, Border Gateway Protocol (BGP) routes carrying the load balancing feature are advertised to the CR.

[0198] If the load balancing feature is not deployed, the BAS creates an access control list to match the IPv4 range of the customer dedicated line, writes a route publishing policy, and publishes Border Gateway Protocol (BGP) routes with the load balancing feature to the CR.

[0199] Specifically, Fig.11 Another schematic diagram of the uplink process of the IPv4 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 IPv4 customer dedicated line (Layer 2 CE) in the upstream direction specifically includes:

[0200] Step 301, the customer manually configures the service IPv4 and gateway, and sends an uplink message;

[0201] Step 302, the downlink service sub-interfaces of BAS1 and BAS2 belong to the same Layer 2 EVPN domain;

[0202] Step 303, BAS1 and BAS2 run VRRP heartbeat through the Layer 2 EVPN domain;

[0203] Step 304, based on whether BAS is the primary VRRP, if BAS1 is the primary VRRP, then go to step 306, and the client uplink message is sent to BAS1 via the left link. If BAS2 is the primary VRRP, then go to step 305, and the client uplink message is sent to BAS2 via the right link;

[0204] Step 305, the client uplink message is sent to BAS2 via the right link;

[0205] Step 306, the client uplink message is sent to BAS1 via the left link;

[0206] Step 307, based on whether the load balancing feature is deployed when the BAS publishes the route, if the load balancing feature is deployed, proceed to step 311. If the load balancing feature is not deployed, proceed to step 308;

[0207] Step 308, BAS creates an access control list to match the IPv4 range of the customer dedicated line

[0208] Step 309, compile a routing publishing policy;

[0209] Step 310, BAS publishes BGP routes carrying load sharing features;

[0210] Step 311, CR receives corresponding BGP route;

[0211] Step 312, the CR simultaneously publishes two customer service routes to other BASs in the network;

[0212] Step 313, the visitor BAS receives and places two equal-cost routes matching BAS1 and BS2 in the routing table;

[0213] Step 314, the visitor BAS forwards the service message to the visitor's network;

[0214] Step 315: The visitor receives the customer service message.

[0215] In some embodiments, the system is also used to implement the IPv4 Internet dedicated line disaster recovery collaborative implementation process in the downstream direction.

[0216] Fig.12 A schematic diagram of the downlink process of the IPv4 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:

[0217] In response to receiving the response message from the visitor, the visitor BAS forwards the response message to BAS1 or BAS2 via CR according to the HASH distribution algorithm, based on the target IP address of the customer or the source address of the visitor, in accordance with the load sharing method;

[0218] Based on whether the visitor BAS sends the response message to BAS1 or BAS2 as a judgment condition, the response message is sent to the client terminal through the corresponding BAS.

[0219] In some embodiments, according to whether the visitor BAS sends the response message to BAS1 or BAS2 as a judgment condition, sending the response message to the client terminal through the corresponding BAS specifically includes:

[0220] If the visitor BAS sends a response message to BAS1, BAS1 sends a downlink message to the client terminal according to the address resolution protocol ARP table entry;

[0221] If the visitor BAS sends a response message to BAS2, BAS2 sends an ARP probe message to the client terminal; in response to receiving the terminal media access control MAC address and Internet Protocol IP address returned by the client terminal based on the ARP probe message, BAS2 establishes a corresponding ARP table entry and sends a downlink message to the client terminal according to the ARP table entry.

[0222] Specifically, Fig.13 Another schematic diagram of the downlink process of the IPv4 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:

[0223] Step 401, the visitor sends a response message to the dedicated line customer;

[0224] Step 402, the visitor BAS receives the response message;

[0225] Step 403, the visitor BAS forwards the message to BAS1 or BAS2 via CR according to the HASH distribution algorithm, based on the target IP address of the customer or the source address of the visitor, in accordance with the load sharing method;

[0226] Step 404, based on whether the visitor BAS sends the downlink message to BAS1 or BAS2 as a judgment condition, if it is sent to BAS1, then go to step 409. If it is sent to BAS2, then go to step 405;

[0227] Step 405, BAS2 actively sends an ARP detection message to the client terminal;

[0228] Step 406, the client terminal responds to the detection message and returns the terminal MAC and IP;

[0229] Step 407, BAS2 creates a corresponding ARP entry;

[0230] Step 408, BAS2 sends a downlink message to the client terminal according to the ARP table entry;

[0231] Step 409, BAS1 sends a downlink message to the client terminal according to the ARP table entry;

[0232] Step 410: The client terminal receives a downlink message.

[0233] Based on the above system, the present application provides a method for realizing disaster recovery collaboration of an IPv4 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 IPv4 Internet dedicated line in the uplink direction, and the method comprises:

[0234] In response to receiving the uplink message from the client terminal, the CE performs load sharing uplink by equal-cost default, and the access network and aggregation switch transmit the uplink message uplink through the Layer 2 VLAN;

[0235] In response to receiving the uplink message, BAS1 and BAS2 publish Border Gateway Protocol (BGP) routes carrying the load balancing feature to CR based on whether the load balancing feature is deployed when the BAS publishes the route as a judgment condition;

[0236] In response to receiving the BGP route, the CR publishes the customer service route to other BASs in the network;

[0237] In response to receiving the customer service route, the visitor BAS places two equal-cost routes matching BAS1 and BS2 in the routing table. The visitor BAS is used to forward the service message to the visitor's network.

[0238] In some embodiments, the method is also used to implement a coordinated implementation process of IPv4 Internet dedicated line disaster recovery in the downstream direction, and the method further includes:

[0239] In response to receiving the response message from the visitor, the visitor BAS forwards the response message to BAS1 or BAS2 via CR according to the HASH distribution algorithm, based on the target IP address of the customer or the source address of the visitor, in accordance with the load sharing method;

[0240] In response to receiving the response message, BAS1 or BAS2 sends the response message to the corresponding uplink port of CE according to the static / dynamic routing mode;

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

[0242] Based on the above system, the present application provides a method for realizing disaster recovery collaboration of an IPv4 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 IPv4 Internet dedicated line in an uplink direction, and the method comprises:

[0243] In response to the client terminal sending an uplink message, the downlink service sub-interfaces of BAS1 and BAS2 belong to the same Layer 2 Ethernet virtual private network EVPN domain, and BAS1 and BAS2 run the virtual router redundancy protocol VRRP heartbeat through the Layer 2 EVPN domain;

[0244] Based on whether the BAS is the primary one, VRRP is used as a judgment condition to send the uplink message to the corresponding BAS;

[0245] Advertise Border Gateway Protocol (BGP) routes carrying the load balancing feature to the CR based on whether the load balancing feature is deployed when the BAS advertises routes.

[0246] In response to receiving the BGP route, the CR publishes the customer service route to other BASs in the network;

[0247] In response to receiving the customer service route, the visitor BAS places two equal-cost routes matching BAS1 and BS2 in the routing table. The visitor BAS is used to forward the service message to the visitor's network.

[0248] In some embodiments, the method is also used to implement a coordinated implementation process of IPv4 Internet dedicated line disaster recovery in the downstream direction, and the method further includes:

[0249] In response to receiving the response message from the visitor, the visitor BAS forwards the response message to BAS1 or BAS2 via CR according to the HASH distribution algorithm, based on the target IP address of the customer or the source address of the visitor, in accordance with the load sharing method;

[0250] Based on whether the visitor BAS sends the response message to BAS1 or BAS2 as a judgment condition, the response message is sent to the client terminal through the corresponding BAS.

[0251] The present application provides a system and method for realizing disaster recovery coordination of IPv4 Internet dedicated lines. For the three-layer CE scenario on the client side, the two-way load sharing IPv4 effect of access layer and aggregation layer can be realized. For the two-layer CE scenario on the client side, the upstream traffic primary and backup disaster recovery and the downstream traffic load sharing IPv4 effect can be realized. The present application can effectively realize disaster recovery protection for IPv4 Internet dedicated lines and data center customers.

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

[0253] 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 IPv4 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, and a visitor 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 IPv4 Internet dedicated line in the uplink direction, wherein: In response to receiving the uplink message from the client terminal, the CE performs load sharing uplink by equal-cost default, and the access network and aggregation switch transmit the uplink message uplink through the Layer 2 VLAN; In response to receiving the uplink message, BAS1 and BAS2 publish Border Gateway Protocol (BGP) routes carrying the load balancing feature to CR based on whether the load balancing feature is deployed when the BAS publishes the route as a judgment condition; In response to receiving the BGP route, the CR publishes the customer service route to other BASs in the network; In response to receiving the customer service route, the visitor BAS places two equal-cost routes matching BAS1 and BS2 in the routing table. The visitor BAS is used to forward the service message to the visitor's network.

2. The IPv4 Internet dedicated line disaster recovery collaborative implementation system according to claim 1, characterized in that: In response to receiving the uplink message, BAS1 and BAS2 publish the Border Gateway Protocol (BGP) route carrying the load balancing feature to the CR based on whether the load balancing feature is deployed when the BAS publishes the route as a judgment condition, including: If the load balancing feature is deployed, Border Gateway Protocol (BGP) routes carrying the load balancing feature are advertised to the CR. If the load balancing feature is not deployed, the BAS creates an access control list to match the IPv4 range of the customer dedicated line, writes a route publishing policy, and publishes Border Gateway Protocol (BGP) routes with the load balancing feature to the CR.

3. The IPv4 Internet dedicated line disaster recovery collaborative implementation system according to claim 1, characterized in that: The system is also used to implement the IPv4 Internet dedicated line disaster recovery collaborative implementation process in the downstream direction, wherein: In response to receiving the response message from the visitor, the visitor BAS forwards the response message to BAS1 or BAS2 via CR according to the HASH distribution algorithm, based on the target IP address of the customer or the source address of the visitor, in accordance with the load sharing method; In response to receiving the response message, BAS1 or BAS2 sends the response message to the corresponding uplink port of CE according to the static / dynamic routing mode; In response to receiving the response message, the CE forwards the response message to the client terminal.

4. An IPv4 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, and a visitor 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 IPv4 Internet dedicated line in the uplink direction, wherein: In response to the client terminal sending an uplink message, the downlink service sub-interfaces of BAS1 and BAS2 belong to the same Layer 2 Ethernet virtual private network EVPN domain, and BAS1 and BAS2 run the virtual router redundancy protocol VRRP heartbeat through the Layer 2 EVPN domain; Based on whether the BAS is the primary one, VRRP is used as a judgment condition to send the uplink message to the corresponding BAS; Advertise Border Gateway Protocol (BGP) routes carrying the load balancing feature to the CR based on whether the load balancing feature is deployed when the BAS advertises routes. In response to receiving the BGP route, the CR publishes the customer service route to other BASs in the network; In response to receiving the customer service route, the visitor BAS places two equal-cost routes matching BAS1 and BS2 in the routing table. The visitor BAS is used to forward the service message to the visitor's network.

5. The IPv4 Internet dedicated line disaster recovery collaborative implementation system according to claim 4, characterized in that: Based on whether the BAS is the primary VRRP, the upstream message is sent to the corresponding BAS, including: If BAS1 is the active VRRP, the uplink message is sent to BAS1 through the left link; If BAS2 is the active VRRP, the uplink message is sent to BAS2 through the right link.

6. The IPv4 Internet dedicated line disaster recovery collaborative implementation system according to claim 4, characterized in that: Based on whether the load balancing feature is deployed when the BAS advertises routes, the BGP routes carrying the load balancing feature are advertised to the CR. Specifically, the following are performed: If the load balancing feature is deployed, Border Gateway Protocol (BGP) routes carrying the load balancing feature are advertised to the CR. If the load balancing feature is not deployed, the BAS creates an access control list to match the IPv4 range of the customer dedicated line, writes a route publishing policy, and publishes Border Gateway Protocol (BGP) routes with the load balancing feature to the CR.

7. The IPv4 Internet dedicated line disaster recovery collaborative implementation system according to claim 4, characterized in that: The system is also used to implement the IPv4 Internet dedicated line disaster recovery collaborative implementation process in the downstream direction, wherein: In response to receiving the response message from the visitor, the visitor BAS forwards the response message to BAS1 or BAS2 via CR according to the HASH distribution algorithm, based on the target IP address of the customer or the source address of the visitor, in accordance with the load sharing method; Based on whether the visitor BAS sends the response message to BAS1 or BAS2 as a judgment condition, the response message is sent to the client terminal through the corresponding BAS.

8. The IPv4 Internet dedicated line disaster recovery collaborative implementation system according to claim 7, characterized in that: According to whether the visitor BAS sends the response message to BAS1 or BAS2 as a judgment condition, the response message is sent to the client terminal through the corresponding BAS, specifically including: If the visitor BAS sends a response message to BAS1, BAS1 sends a downlink message to the client terminal according to the address resolution protocol ARP table entry; If the visitor BAS sends a response message to BAS2, BAS2 sends an ARP probe message to the client terminal; in response to receiving the terminal media access control MAC address and Internet Protocol IP address returned by the client terminal based on the ARP probe message, BAS2 establishes a corresponding ARP table entry and sends a downlink message to the client terminal according to the ARP table entry.

9. A method for realizing coordinated disaster recovery of IPv4 Internet dedicated lines, 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 IPv4 Internet dedicated lines in the uplink direction, and the method includes: In response to receiving the uplink message from the client terminal, the CE performs load sharing uplink by equal-cost default, and the access network and aggregation switch transmit the uplink message uplink through the Layer 2 VLAN; In response to receiving the uplink message, BAS1 and BAS2 publish Border Gateway Protocol (BGP) routes carrying the load balancing feature to CR based on whether the load balancing feature is deployed when the BAS publishes the route as a judgment condition; In response to receiving the BGP route, the CR publishes the customer service route to other BASs in the network; In response to receiving the customer service route, the visitor BAS places two equal-cost routes matching BAS1 and BS2 in the routing table. The visitor BAS is used to forward the service message to the visitor's network.

10. The method for realizing IPv4 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 IPv4 Internet dedicated line in a downstream direction, and the method further comprises: In response to receiving the response message from the visitor, the visitor BAS forwards the response message to BAS1 or BAS2 via CR according to the HASH distribution algorithm, based on the target IP address of the customer or the source address of the visitor, in accordance with the load sharing method; In response to receiving the response message, BAS1 or BAS2 sends the response message to the corresponding uplink port of CE according to the static / dynamic routing mode; In response to receiving the response message, the CE forwards the response message to the client terminal.

11. A method for realizing disaster recovery collaboration of an IPv4 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 disaster recovery implementation process of an IPv4 Internet dedicated line in the uplink direction, and the method comprises: In response to the client terminal sending an uplink message, the downlink service sub-interfaces of BAS1 and BAS2 belong to the same Layer 2 Ethernet virtual private network EVPN domain, and BAS1 and BAS2 run the virtual router redundancy protocol VRRP heartbeat through the Layer 2 EVPN domain; Based on whether the BAS is the primary one, VRRP is used as a judgment condition to send the uplink message to the corresponding BAS; Advertise Border Gateway Protocol (BGP) routes carrying the load balancing feature to the CR based on whether the load balancing feature is deployed when the BAS advertises routes. In response to receiving the BGP route, the CR publishes the customer service route to other BASs in the network; In response to receiving the customer service route, the visitor BAS places two equal-cost routes matching BAS1 and BS2 in the routing table. The visitor BAS is used to forward the service message to the visitor's network.

12. The method for realizing IPv4 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 IPv4 Internet dedicated line in a downstream direction, and the method further comprises: In response to receiving the response message from the visitor, the visitor BAS forwards the response message to BAS1 or BAS2 via CR according to the HASH distribution algorithm, based on the target IP address of the customer or the source address of the visitor, in accordance with the load sharing method; Based on whether the visitor BAS sends the response message to BAS1 or BAS2 as a judgment condition, the response message is sent to the client terminal through the corresponding BAS.

Images