WAN (wide area network) data compression method, device, equipment, medium and program product

Abstract

The invention provides a wide area network data compression method, device and equipment, a medium and a program product, which can be applied to the field of big data and the field of financial science and technology. The method comprises the following steps: guiding the service flow of a data center to a compression pool through a preset link establishment mode; wherein the preset link establishment mode is a many-to-many link establishment networking mode established based on border gateway protocol flow specification routing and a routing reflector; based on a load balancing mechanism, a redirection flow load sharing strategy is adopted, the service flow is distributed to compression equipment of a compression pool, and target compression equipment is determined; and based on the logic layering model and the compression fault switching strategy, compressing the distributed service flow through the target compression device, wherein the compression failover strategy comprises an intra-group failover strategy and a cross-plane failover strategy.

Description

Technical Field

[0001] This application relates to the fields of big data and fintech, and more specifically to a wide area network data compression method, apparatus, device, medium, and program product. Background Technology

[0002] With the accelerated digital transformation of finance and increasingly stringent business continuity regulations, the financial industry's requirements for the reliability, timeliness, and data integrity of disaster recovery systems continue to rise. Wide area network (WAN) data compression systems play a crucial role in ensuring the efficiency of disaster recovery data replication, and WAN data compression is a core supporting technology for ensuring business continuity in financial technology. However, current WAN traffic data compression systems suffer from insufficient high availability. When compression equipment fails, it leads to an expansion of disaster recovery traffic bandwidth, thereby affecting the timeliness of disaster recovery replication.

[0003] Traditional WAN data compression technology relies on classic compression algorithms and fixed patterns, which leads to problems such as slow equipment failure takeover and inability to take over plane failures, making it difficult to meet the needs of continuous compression for disaster recovery data in data center WANs. Summary of the Invention

[0004] In view of the above problems, this application provides a method, apparatus, device, medium and program product for improving the continuity of compression for wide area networks.

[0005] According to a first aspect of this application, a wide area network (WAN) data compression method is provided, comprising: diverting data center service traffic to a compression pool through a preset link establishment method; wherein the preset link establishment method is a many-to-many link establishment networking method based on border gateway protocol flow specification routing and route reflector; allocating the service traffic to compression devices in the compression pool based on a load balancing mechanism and a redirection traffic load sharing strategy, and determining target compression devices; and compressing the allocated service traffic through the target compression devices based on a logical layering model and a compression fault switching strategy; wherein the compression fault switching strategy includes an intra-group fault switching strategy and a cross-plane fault switching strategy.

[0006] According to an embodiment of this application, the preset chain establishment method includes: deploying a route reflector corresponding to the compression pool in the data center; publishing the same Border Gateway Protocol (BGP) flow specification route to the route reflector through all devices in the compression pool; and transmitting the BGP flow specification route to the edge devices in the data center through the route reflector.

[0007] According to embodiments of this application, the load balancing mechanism includes an equal-cost multi-path load balancing mechanism and / or an unequal-cost multi-path load balancing mechanism; the redirection traffic load sharing strategy includes: configuring all devices in the compression pool with the same loopback address; configuring the static equal-cost route of the edge device of the data center to point to the loopback address, and configuring the policy route of the edge device to redirect the service traffic to the loopback address; in a homogeneous device scenario, distributing the service traffic evenly among the compression devices in the compression pool based on the equal-cost multi-path load balancing mechanism; and in a heterogeneous device scenario, configuring the bandwidth weight of the compression device through the unequal-cost multi-path load balancing mechanism, and distributing the service traffic based on the bandwidth weight.

[0008] According to an embodiment of this application, the logical layering model includes: grouping devices into pairs based on the model of the compression device to determine a remote backup service group, wherein the compression devices in the remote backup service group are interconnected via a two-line three-layer interconnection; constructing the compression pool according to the remote backup service group; and dividing the compression pool into network planes to obtain a first plane compression pool and a second plane compression pool.

[0009] According to an embodiment of this application, the intra-group fault switching strategy includes: real-time monitoring of the compression status information of the target compression device in the remote backup service group to determine the intra-group status; when the intra-group status is normal, compressing and processing the allocated service traffic in parallel through the target compression device in the remote backup service group; and when the intra-group status is abnormal, taking over and processing the service traffic of the abnormal device through the normal compression device in the remote backup service group based on the interconnection line.

[0010] According to an embodiment of this application, the cross-plane fault handover strategy includes: real-time monitoring of the compression status information of target compression devices in the first and second plane compression pools to determine the plane status; when the plane status is normal, switching the decompression strategy routing to the primary next hop, wherein the primary next hop points to the same plane compression pool; compressing and processing the allocated service traffic through the target compression devices in the first plane compression pool; and when the plane status is abnormal, switching the decompression strategy routing to the backup next hop, wherein the backup next hop points to a crosslink; and, based on the decompression strategy routing, taking over and processing the service traffic of the abnormal plane compression pool through the target compression devices in the normal plane compression pool via the crosslink.

[0011] According to an embodiment of this application, the method further includes: periodically detecting the compression instance status of the target compression device by operating a plane script; closing the associated physical port of the target compression device when the compression instance status meets the periodic abnormality condition; and opening the associated physical port of the target compression device when the compression instance status meets the recovery compression condition.

[0012] A second aspect of this application provides a wide area network (WAN) data compression device, comprising: a traffic redirection module for redirecting service traffic from a data center to a compression pool via a preset link establishment method; wherein the preset link establishment method is a many-to-many link establishment networking method based on border gateway protocol flow specification routing and route reflectors; a load balancing module for allocating the service traffic to compression devices in the compression pool based on a load balancing mechanism and a redirected traffic load sharing strategy, and determining the target compression device; and a compression fault switching module for compressing and processing the allocated service traffic through the target compression device based on a logical layering model and a compression fault switching strategy; wherein the compression fault switching strategy includes an intra-group fault switching strategy and a cross-plane fault switching strategy.

[0013] A third aspect of this application provides an electronic device comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the method described above.

[0014] A fourth aspect of this application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a processor, implement the steps of the above-described method.

[0015] The fifth aspect of this application also provides a computer program product, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described method.

[0016] In the embodiments of this application, stable traffic diversion is ensured through many-to-many link building networking, and load balancing adopts a redirection traffic load sharing strategy to achieve efficient utilization of equipment resources. Based on a logical layering model and a dual fault switching strategy, equipment and cross-plane faults are quickly resolved, ensuring the high availability of the WAN traffic compression system. This achieves the goals of high reliability, easy operation and maintenance, easy capacity expansion, and decoupling from the backbone network of the compression system, avoiding the expansion of disaster recovery traffic bandwidth caused by WAN compression failure, ensuring continuous compression of disaster recovery data, and significantly improving the timeliness of disaster recovery data replication. Attached Figure Description

[0017] The above-mentioned contents, other objects, features and advantages of this application will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0018] Figure 1 The illustration schematically depicts application scenarios of a wide area network data compression method, apparatus, device, medium, and program product according to embodiments of this application;

[0019] Figure 2 A flowchart illustrating a wide area network data compression method according to an embodiment of this application is shown schematically.

[0020] Figure 3 This schematically illustrates another flowchart of a wide area network data compression method according to an embodiment of the present application;

[0021] Figure 4 This schematic diagram illustrates the structure of a wide area network data compression system according to an embodiment of this application.

[0022] Figure 5 This illustration schematically shows the operation of a wide area network data compression system according to an embodiment of this application;

[0023] Figure 6 A schematic diagram illustrating the structure of a wide area network data compression apparatus according to an embodiment of this application is shown; and

[0024] Figure 7 A block diagram illustrating an electronic device suitable for implementing a wide area network data compression method according to an embodiment of this application is shown schematically. Detailed Implementation

[0025] The embodiments of this application will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of this application. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of this application for ease of explanation. However, it will be apparent that one or more embodiments may be implemented without these specific details. Furthermore, descriptions of well-known structures and technologies are omitted in the following description to avoid unnecessarily obscuring the concepts of this application.

[0026] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of this application. The terms “comprising,” “including,” etc., as used herein indicate the presence of features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0027] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0028] When using expressions such as "at least one of A, B and C", they should generally be interpreted in accordance with the meaning that is commonly understood by those skilled in the art (e.g., "a system having at least one of A, B and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B and C, etc.).

[0029] Against the backdrop of deepening digital transformation in the financial sector, high-frequency transaction data and sensitive customer information require real-time backup across geographical regions. However, the contradiction between limited WAN bandwidth and the timeliness requirements of disaster recovery is becoming increasingly prominent. WAN data compression reduces data volume through advanced algorithms, saving bandwidth costs and improving the speed of disaster recovery data transmission. However, the insufficient availability of WAN data compression directly affects the stability of the disaster recovery system, and bandwidth expansion during failures may lead to business interruption risks.

[0030] Current wide area network (WAN) data compression systems have significant shortcomings. When equipment fails, the takeover response is slow, and in the case of planar failures, effective takeover cannot be achieved, resulting in interruption of disaster recovery traffic compression. This makes it difficult to meet the high reliability requirements of continuous data compression in data center WAN disaster recovery scenarios.

[0031] It should be noted that the wide area network data compression method and apparatus of this application can be used in the fields of big data and fintech, as well as in any other field. The application fields of the wide area network data compression method and apparatus of this application are not limited.

[0032] This application provides a wide area network (WAN) data compression method. It redirects data center traffic to a compression pool using a preset link establishment method. The preset link establishment method is a many-to-many link establishment networking method based on border gateway protocol flow specification routing and route reflectors. Based on a load balancing mechanism, a redirected traffic load sharing strategy is adopted to allocate traffic to compression devices in the compression pool, identifying the target compression devices. Furthermore, based on a logical layering model and a compression fault switching strategy, the allocated traffic is compressed and processed by the target compression devices. The compression fault switching strategy includes intra-group fault switching and cross-plane fault switching strategies.

[0033] Figure 1 The illustration schematically depicts application scenarios of a wide area network data compression method, apparatus, device, medium, and program product according to embodiments of this application.

[0034] like Figure 1As shown, the application scenario according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 serves as a medium for providing a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0035] Users can use the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 via the network 104 to receive or send messages, etc. Various communication client applications can be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0036] The first terminal device 101, the second terminal device 102, and the third terminal device 103 can be various electronic devices with displays and support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0037] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103 (this is just an example). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0038] It should be noted that the WAN data compression method provided in this application embodiment can generally be executed by server 105. Correspondingly, the WAN data compression device provided in this application embodiment can generally be located in server 105. The WAN data compression method provided in this application embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105. Correspondingly, the WAN data compression device provided in this application embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105.

[0039] It should be understood that Figure 1The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0040] The following will be based on Figure 1 The described scene, through Figures 2-5 A wide area network data compression method according to embodiments of this application will be described in detail.

[0041] Figure 2 A flowchart illustrating a wide area network data compression method according to an embodiment of this application is shown schematically.

[0042] like Figure 2 As shown, the wide area network (WAN) data compression method of this embodiment includes operations S210 to S230. This WAN data compression method does not limit the specific executing entity. The executing entity can be any electronic device, such as a terminal device or a server device, etc. The executing entity can also be any software application or client.

[0043] When operating S210, the data center's business traffic is diverted to the compression pool through a preset chain establishment method. The preset chain establishment method is a many-to-many chain establishment networking method based on border gateway protocol flow specification routing and route reflector.

[0044] Border Gateway Protocol (BGP) is the core external gateway protocol of the Internet, which exchanges routing information between different autonomous systems, allowing data to find the optimal transmission path across networks.

[0045] The Border Gateway Protocol-Flow Specification (BGP FS) is a BGP extension used for traffic engineering and traffic control. It defines matching rules for network traffic, such as Internet Protocol (IP) addresses, ports, and protocol types, and transmits these rules through the BGP protocol to enable rapid identification, classification, redirection, or control of specific traffic. In WAN compression systems, it is often used to stabilize traffic and ensure that traffic requiring compression accurately enters the compression pool for processing.

[0046] A route reflector (RR) is a route forwarding optimization device in a BGP network. It is used to reduce the requirements of full connectivity, centrally reflect routing information, and simplify the networking and management of large-scale BGP networks.

[0047] The WAN data compression process can be divided into five stages: traffic introduction, load distribution, compression processing, fault switching, and status monitoring. Each stage relies closely on the system's logical layering model, remote backup service (RBS), border gateway protocol flow specification (BGP FS), and other technical architectures to achieve efficient and highly available WAN data compression.

[0048] During the traffic inbound phase, BGP FS-based many-to-many link establishment establishes a stable transmission channel for compressed traffic. Once service traffic enters the data center, edge devices, guided by BGP FS routing, identify the traffic requiring compression and redirect it to the compression pool, laying the foundation for subsequent compression processing. This many-to-many link establishment design significantly improves the flexibility and reliability of traffic redirection, avoiding the bottlenecks and failure risks associated with single-point link establishment.

[0049] When edge devices identify traffic that needs compression, they can filter the traffic to be compressed through policy routing. Based on preset rules, they can identify packets carrying specific identifiers and forward them to the compression resource pool. Policy routing ensures that only target traffic enters the compression process by matching the source and destination addresses, port numbers, and other information of the packets, thus preventing irrelevant data from consuming resources.

[0050] When operating S220, based on the load balancing mechanism, a redirection traffic load sharing strategy is adopted to distribute business traffic to the compression devices in the compression pool and determine the target compression device.

[0051] During traffic allocation, firstly, all compression devices within the compression pool are configured with the same loopback address. Then, the static equal-cost routes of the data center edge devices are directed to this loopback address, and policy-based routes are configured to redirect service traffic to this loopback address. Secondly, the appropriate load balancing mechanism is selected based on the device scenario: in homogeneous device scenarios, an equal-cost multi-path load balancing mechanism can be used to evenly distribute service traffic among the compression devices; in heterogeneous device scenarios, a non-equal-cost multi-path load balancing mechanism can be used to configure the bandwidth weight of each compression device and allocate traffic according to the weight. Finally, after redirection and load balancing, the compression device that receives the traffic becomes the target compression device.

[0052] It is worth noting that the load balancing mechanism is also deeply integrated with the logical layering model. The compression pool composed of multiple RBS groups provides horizontally scalable compression capabilities, ensuring that the equal-cost multi-path load balancing mechanism / non-equal-cost multi-path load balancing mechanism has sufficient device resources for traffic scheduling. The cross-plane compression pool architecture (first plane and second plane) reserves space for subsequent cross-plane load migration, ensuring that cross-plane scheduling can be achieved when the load pressure on a single plane is too high.

[0053] In operation S230, based on the logical layering model and the compression fault switching strategy, the allocated service traffic is compressed and processed through the target compression device; the compression fault switching strategy includes intra-group fault switching strategy and cross-plane fault switching strategy.

[0054] After traffic is allocated to specific target compression devices, it enters the compression processing stage under the high availability protection of the RBS group. During compression processing, reliability is ensured by combining fault-by-fault strategies. The group monitors the device status in real time to implement the fault-by-fault strategy within the group. When normal, traffic is processed in parallel; when abnormal, normal devices within the group take over through interconnection lines. The plane-level device status is monitored to implement a cross-plane fault-by-fault strategy. When normal, the primary next hop (within the same plane) is used for processing; when abnormal, it switches to the backup next hop (cross-link), and is taken over by normal plane devices. At the same time, the operation plane script periodically checks the compression instance status. When abnormal, the associated ports are closed, and they are opened after recovery to ensure that the target devices can stably compress and process traffic.

[0055] Compression devices are grouped into pairs according to their model numbers to form remote backup service groups (with devices within each group interconnected in a dual-line, three-layer manner). Based on this, compression pools are determined and divided into first and second plane compression pools, constructing a logical hierarchical model. The logical hierarchical model is the architectural foundation for intra-group and cross-plane fault switching strategies. Through the hierarchical design of device grouping, group formation into pools, and pool division into planes, the logical hierarchical model clarifies the operational boundaries and hierarchical objects for fault switching.

[0056] The intra-group failover strategy corresponds to the device grouping hierarchy of the model. For devices within the same remote backup service group, it leverages the dual-line interconnection feature within the group to achieve traffic takeover for abnormal devices. The cross-plane failover strategy corresponds to the plane partitioning hierarchy of the model. For two plane compression pools, it achieves overall traffic takeover for the abnormal plane through cross-links and primary / backup next-hop switching.

[0057] The compression failover strategy also includes an intra-plane failover strategy. Specifically, the intra-plane failover strategy works as follows: if the intra-group failover strategy fails (no normal device can take over), the system immediately reports a local anomaly in the plane to which that service group belongs. Prioritizes searching for other available remote backup service groups within the same plane, and temporarily diverts traffic from the abnormal group to these normal groups using the intra-plane load balancing mechanism. If no available service group is available within the same plane (or the traffic cannot be carried even after diversion), a cross-plane failover strategy is triggered, switching the decompression strategy routing to the backup next hop (crosslink). Traffic is then diverted to a remote backup service group in another normal plane via the crosslink, where it takes over compression processing. Simultaneously, the operation plane script continuously monitors the abnormal device, and gradually returns traffic after recovery.

[0058] The logical layered model establishes a hierarchical framework of group-pool-plane, while the three fault-switching strategies utilize the interconnection relationships within the framework (dual lines within the group and horizontal connections between planes) at the two levels of intra-group and inter-plane to achieve precise fault handling and jointly ensure the continuity of compressed services.

[0059] In the embodiments of this application, a multi-to-multi link-based network is used to establish and redirect traffic, and a redirected traffic load balancing strategy is used to distribute service traffic. A compression fault-switching strategy is used to compress and process service traffic. The beneficial effects are that the multi-to-multi link-based network ensures stable traffic redirection, the load balancing adopts a redirected traffic load balancing strategy to achieve efficient utilization of equipment resources, and the logical layering model and dual fault-switching strategy quickly resolve equipment and cross-plane faults, ensuring the high availability of the WAN traffic compression system. This achieves the goals of high reliability, easy operation and maintenance, easy capacity expansion, and decoupling from the backbone network of the compression system, avoids the expansion of disaster recovery traffic bandwidth caused by WAN compression failure, ensures continuous compression of disaster recovery data, and significantly improves the timeliness of disaster recovery data replication.

[0060] According to an embodiment of this application, the preset chain establishment method includes: deploying a route reflector corresponding to a compression pool in a data center; publishing the same Border Gateway Protocol (BGP) flow specification route to the route reflector through all devices in the compression pool; and transmitting the BGP flow specification route to edge devices in the data center through the route reflector.

[0061] First, each compression pool independently deploys a Route Reflector (RR) in each data center. Leveraging the RR's reflection capabilities, BGP FS routes are transmitted via the RR reflector, transforming the traditional one-to-one BGP connection establishment into a many-to-many networking approach. All compression devices advertise the same BGP FS routes to the RR, ensuring the compression protocol remains continuously online. BGP FS employs a multi-point to multi-point connection establishment method, using route reflectors to ensure all compression devices advertise the same routes, guaranteeing the compression protocol's continuous online operation. This allows incoming service traffic to be accurately identified and directed to the compression pool, laying the foundation for subsequent load balancing and compression processing, while simultaneously improving the stability and flexibility of traffic redirection.

[0062] The core of BGP FS routing is routing information containing traffic characteristics (such as source and destination IPs, ports, etc.) and forwarding rules (such as directing matching traffic to the compression pool). In a WAN compression system, the transmission process of this type of route is as follows: Route advertising source: All compression devices within the compression pool act as publishers of BGP FS routes, advertising the same BGP FS routes (containing the characteristics of the traffic to be compressed and processing rules) to the RR reflector in their respective data centers. The role of the RR reflector: As an intermediate node, the RR receives the BGP FS routes advertised by the compression devices and, without establishing full direct connection sessions with other devices, directly reflects these routes to the client devices under its jurisdiction (without repeatedly transmitting them to each device), significantly simplifying network topology and reducing session maintenance costs. Transmission target (receiver): Primarily edge devices within the data center, such as DC-CE (data center customer-side edge devices). These DC-CE devices, acting as clients of the RR, obtain BGP FS routes by establishing a single BGP session with the RR, thereby accurately identifying and guiding the service traffic requiring compression into the compression pool for processing based on the rules contained in the routes. As a "relay station" for BGP FS routing, RR efficiently transmits compression-related traffic rules to edge devices in the data center, ensuring that these devices can uniformly and accurately execute traffic redirection strategies.

[0063] In the embodiments of this application, by deploying a route reflector and compression device to uniformly publish the border gateway protocol flow specification route and pass it to the edge device, a stable many-to-many chain is built, which enables the accurate diversion of business traffic to the compression pool, ensures the reliability and flexibility of the chain, lays the foundation for subsequent load sharing and fault switching, and improves the stability of disaster recovery data compression transmission.

[0064] According to embodiments of this application, the load balancing mechanism includes an equal-cost multi-path load balancing mechanism and / or an unequal-cost multi-path load balancing mechanism; the redirection traffic load sharing strategy includes: configuring all devices in the compression pool with the same loopback address; configuring static equal-cost routes for edge devices in the data center to point to the loopback address, and configuring policy routes for edge devices to redirect service traffic to the loopback address; in a homogeneous device scenario, distributing service traffic evenly among compression devices in the compression pool based on the equal-cost multi-path load balancing mechanism; and in a heterogeneous device scenario, configuring the bandwidth weight of compression devices through an unequal-cost multi-path load balancing mechanism, and distributing service traffic based on the bandwidth weight.

[0065] Equal Cost Multi Path (ECMP) load balancing refers to the distribution of traffic evenly across multiple paths with identical bandwidth, latency, and other attributes to achieve load sharing.

[0066] The Unequal Cost Multi Path (UCMP) load balancing mechanism supports different path attributes and can allocate traffic according to strategies such as bandwidth weight, adapting to heterogeneous network scenarios.

[0067] Policy-based routing (PBR) enables devices to forward data based on various elements such as the logical addresses, physical addresses, port numbers, and VLAN identifiers of packets.

[0068] After traffic enters the compression pool, it is intelligently allocated through traffic load balancing based on equal-cost multipath load balancing (ECMP) / unequal-cost multipath load balancing (UCMP) (corresponding to S104). All devices in the compression resource pool are configured with a unified loopback address. Edge devices distribute traffic through equal-cost or unequal-cost multipath load balancing mechanisms. In scenarios with the same type of device, equal-cost routing distributes traffic evenly to each device. If there are differences in device performance, unequal-cost routing is used to distribute traffic according to bandwidth weight, allowing high-performance devices to bear more load and improving overall compression efficiency. At the same time, the compression pool, composed of multiple remote backup service groups, supports horizontal scaling and can dynamically add devices according to traffic growth.

[0069] Traffic redirection load balancing strategy: Configure the same IP (Internet Protocol) address for the loopback interface of all devices in the compression pool. Configure multiple static equal-cost routes on the data center edge devices to point to this IP address to form a basic load balancing link. At the same time, configure policy routes to redirect business traffic to this IP address. In the case of homogeneous devices, ECMP is used to achieve balanced distribution of traffic among the devices in the compression pool. In the case of heterogeneous devices, traffic is allocated according to bandwidth weight based on UCMP. Different bandwidth weights are configured through UCMP to distribute traffic according to the performance ratio of the devices. For example, high-performance devices can handle more traffic to make full use of hardware capabilities.

[0070] In the embodiments of this application, by using a unified loopback address, static equal-cost routing, and policy routing, combined with two load balancing mechanisms, it adapts to homogeneous / heterogeneous device scenarios, achieving reasonable allocation of service traffic, improving device utilization, and ensuring efficient and stable compression processing. Through a many-to-many link-based networking method combined with redirected traffic load balancing, it achieves rapid convergence in the event of a two-point failure. When a two-point failure occurs, traffic redistribution can be completed within minutes, restoring compression capabilities.

[0071] According to an embodiment of this application, the logical layering model includes: grouping devices into pairs based on the model of the compression device to determine a remote backup service group, wherein the compression devices in the remote backup service group are interconnected through a two-line three-layer interconnection; constructing a compression pool based on the remote backup service group; and dividing the compression pool into network planes to obtain a first plane compression pool and a second plane compression pool.

[0072] Remote Backup Service (RBS) refers to a high-availability service group consisting of two devices connected via a two-wire Layer 3 interconnect.

[0073] The logical layered model constructs a highly redundant and easily managed compression service foundation through a three-layer architecture of device grouping, pooling integration, and plane partitioning. Each layer can be designed around reliability and scalability.

[0074] When constructing the logical layered model, firstly, remote backup service groups are formed by pairing compression device models to ensure consistent device performance and interoperability within the group. The two devices within a group are interconnected using a dual-line, layer 3 architecture, with two links deployed independently (using different physical lines, virtual LANs, or ports). This ensures communication redundancy while supporting parallel traffic forwarding and rapid takeover.

[0075] Secondly, multiple remote backup service groups are integrated into a compression pool. Devices within the pool share a unified access identifier (such as the same loopback address), achieving network-wide reachability through routing protocols. As a logical resource cluster, the compression pool masks the differences between individual devices, facilitating traffic scheduling based on overall computing power.

[0076] Finally, the compression pool is divided into a first-plane compression pool and a second-plane compression pool. The two planes are physically isolated but logically interconnected, and a backup channel is established through cross-links. The plane division achieves risk isolation, and the failure of one plane does not affect the operation of the other plane, providing architectural support for cross-plane disaster recovery, and ultimately forming a three-level redundancy system of devices, groups, and planes.

[0077] In the embodiments of this application, based on a logical layered model, the horizontal scaling capability of the compression pool is enhanced, supporting expansion at the granular level of remote backup service groups, and the compression capacity can be flexibly expanded according to traffic demand. Furthermore, grouping devices of the same model supports the mixed deployment of different models of compression devices in the compression pool, enabling heterogeneous device deployment. Combined with non-equivalent multi-path load balancing, traffic is allocated based on performance, improving traffic allocation efficiency.

[0078] According to an embodiment of this application, the intra-group fault switching strategy includes: real-time monitoring of the compression status information of the target compression device in the remote backup service group to determine the intra-group status; when the intra-group status is normal, compressing and processing the allocated service traffic in parallel through the target compression device in the remote backup service group; and when the intra-group status is abnormal, taking over the processing of the abnormal device's service traffic through the normal compression device in the remote backup service group based on the interconnection line.

[0079] Once traffic enters the RBS group, the two devices within the group synchronize their compression status in real time via a two-wire interconnection, and under normal circumstances, they collaboratively handle compression tasks. Each device compresses the received traffic in real time before transmitting it through the backbone network; if the compression function of a single device fails, the other device will automatically take over its traffic through the interconnection line, ensuring uninterrupted compression. Cross-plane redundancy design comes into play at this stage, with the compression pools of the two planes operating independently and serving as backups for each other.

[0080] Each pair of compression devices forms an RBS high-availability group, achieving tight physical and logical linkage through dual-line Layer 3 interconnection. The two devices within the group periodically exchange compression status information and collaboratively complete data compression tasks. Under normal conditions, the two devices process traffic in parallel, utilizing the resources of the RBS group to achieve efficient utilization of compression capacity. This dual-machine collaborative mode not only improves the compression throughput of a single RBS group but also prepares for failover.

[0081] In the embodiments of this application, the device status in the remote backup service group is monitored in real time. In the event of a failure, the single point of failure can be recovered in seconds. By designing a highly available remote backup service group, when the compression capacity of a single compression device fails, traffic takeover can be achieved within a few seconds to avoid bandwidth expansion.

[0082] According to an embodiment of this application, the cross-plane fault handover strategy includes: real-time monitoring of the compression status information of target compression devices in the first and second plane compression pools to determine the plane status; when the plane status is normal, switching the decompression strategy routing to the primary next hop, wherein the primary next hop points to the same plane compression pool; compressing and processing the allocated service traffic through the target compression devices in the first plane compression pool; and when the plane status is abnormal, switching the decompression strategy routing to the backup next hop, wherein the backup next hop points to the crosslink; and, based on the decompression strategy routing, taking over and processing the service traffic of the abnormal plane compression pool through the target compression devices in the normal plane compression pool via the crosslink.

[0083] When a complete failure of the current plane compression pool is detected, the decompression policy routing will trigger a multi-next-hop handover mechanism, redirecting traffic to a compression pool in another plane via crosslinks between edge devices (such as DC-CE), thus achieving cross-plane takeover. Dual-line interconnection within the remote backup service group further enhances reliability and avoids handover failures caused by single-link failures.

[0084] For example, when a compression pool in one plane fails, service migration is achieved through a cross-plane takeover mechanism isolated by the compression pool. The decompression PBR of the crosslink between DC-CE is configured in a multi-next-hop manner, with two next hops: the primary next hop points to the resource pool in the same plane, and the backup next hop points to the DC-CE crosslink. When the primary plane compression pool fails, the PBR automatically switches to the backup next hop, forwarding traffic to the compression pool in the other plane via the crosslink, where the compression pool in the other plane takes over the decompression service. This mechanism deeply integrates the cross-plane redundancy design of the logical layered model, achieving cross-plane service redundancy protection through a two-plane compression pool architecture.

[0085] In the embodiments of this application, by real-time monitoring of plane status, combined with cross-plane routing switching and crosslink redundancy, the failure of the entire plane can be quickly handled to ensure uninterrupted service traffic. In the event of a single plane failure, another normal plane takes over. Through compression pool plane isolation, a cross-plane takeover mechanism is realized. When a single plane fails, switching can be achieved in a short time to restore compression capabilities, which greatly improves the availability and continuity of the disaster recovery compression system.

[0086] Figure 3 Another flowchart of a wide area network data compression method according to an embodiment of this application is illustrated.

[0087] like Figure 3 As shown, the wide area network (WAN) data compression method of this embodiment includes operations S310 to S340. This WAN data compression method does not limit the specific executing entity. The executing entity can be any electronic device, such as a terminal device or a server device, etc. The executing entity can also be any software application or client.

[0088] When operating the S310, the data center's business traffic is diverted to the compression pool through a preset link establishment method. The preset link establishment method is a many-to-many link establishment networking method based on the border gateway protocol flow specification routing and route reflector.

[0089] When operating S320, based on the load balancing mechanism, a redirection traffic load sharing strategy is adopted to distribute business traffic to the compression devices in the compression pool and determine the target compression device.

[0090] When operating S330, based on the logical layering model and the compression fault switching strategy, the allocated service traffic is compressed and processed through the target compression device; the compression fault switching strategy includes intra-group fault switching strategy and cross-plane fault switching strategy.

[0091] When operating S340, the target compression device's compression instance status is periodically checked via the operation plane script; if the compression instance status meets the periodic abnormal conditions, the associated physical port of the target compression device is closed; and if the compression instance status meets the recovery compression conditions, the associated physical port of the target compression device is opened.

[0092] Operation Plane Script (OPS) is an automated execution script for the network device operation plane. It is used for device status monitoring and automated operation. Through preset instruction sets, it automates operations such as device configuration distribution, status monitoring, and fault handling, reducing manual intervention.

[0093] To ensure the stable operation of the compression system, OPS scripts are used to link compression and PBR (Policy-Based Routing) for real-time monitoring and automated operation of device status. The OPS scripts deployed on the compression devices periodically (every minute) check the compression instance status. When a periodic anomaly condition is detected—such as the compression instance status changing from up (working state, the instance is running normally and can receive and process business traffic) to down (non-working state, the instance has unexpectedly stopped, crashed, or is unresponsive and can no longer process any compression tasks)—and this is confirmed for several consecutive cycles (e.g., 3), the relevant physical ports are automatically shut down. When a compression recovery condition is detected—such as the compression instance status changing from down to up—the port status is automatically restored. This achieves automatic isolation within minutes of a compression failure, preventing policy-based routing (PBR) traffic from continuing to flow to the faulty device.

[0094] In summary, the WAN data compression process is based on a logical layered model as its core architecture. It achieves many-to-many traffic redirection through BGP FS, completes intelligent traffic allocation with the help of ECMP / UCMP, ensures compression continuity under single device failure through RBS groups, realizes service migration for whole-plane failures through cross-plane takeover mechanisms, and finally achieves automated status monitoring and fault isolation through OPS scripts. These five stages are interconnected and work together to build an efficient and highly available WAN data compression system.

[0095] In the embodiments of this application, by periodically detecting the status of the compression instance, shutting down the physical port when abnormal and opening it when recovering, instance failures can be quickly handled, backbone network decoupling can be achieved, and version upgrades and changes of compression devices will not affect the operation of the backbone network, reducing operation and maintenance risks and achieving a high degree of automation. Furthermore, the automatic linkage between compression status and policy routing can be achieved through operation plane scripts, reducing manual intervention and improving fault handling efficiency.

[0096] For example, a wide area network (WAN) data compression method is implemented based on a WAN data compression system. Figure 4 This schematic diagram illustrates the structure of a wide area network data compression system according to an embodiment of this application. Figure 5 The diagram illustrates the operation of a wide area network data compression system according to an embodiment of this application.

[0097] like Figure 4 As shown, the wide area network data compression system includes an RBS high availability group construction platform 100, a BGP FS multi-point link establishment platform 200, an RBS inter-frame protection platform 300, a load sharing platform 400, a compression pool isolation and takeover platform 500, and a compression status linkage platform 600.

[0098] The RBS high availability group construction platform 100 is responsible for pairing compression devices into RBS high availability groups to achieve inter-frame redundancy protection.

[0099] The BGP FS multi-point chain building platform 200 is responsible for building the RR reflector, realizing the BGP FS multi-point to multi-point chain building method, and enhancing the reliability of the protocol.

[0100] The RBS Inter-Frame Protection Platform 300 is responsible for synchronizing the compression status and forwarding fault traffic between two devices within the RBS group.

[0101] The load balancing platform 400 is responsible for configuring equal-cost / non-equal-cost routes for the compression pool, enabling traffic distribution based on device performance.

[0102] The Compression Pool Isolation and Takeover Platform 500 is responsible for enabling cross-plane takeover capability in the event of a single-plane failure.

[0103] The compression status linkage platform 600 is responsible for monitoring the compression status and automatically linking the PBR strategy to achieve rapid isolation of faulty equipment.

[0104] like Figure 5As shown, through layered preparation, precise fault identification, and differentiated fault handling, the system can ultimately operate without interruption. During the initial infrastructure construction, a logical layered model is built, and compression devices are grouped (compression devices are paired into RBS high-availability groups, each group containing two devices of the same model, interconnected through dual-line three-layer interconnection), compression pools are built (multiple RBS groups constitute a compression pool to achieve horizontal expansion of compression capacity), and cross-plane redundancy is implemented (according to the backbone network plane division, compression pools of plane 1 and plane 2 are built to achieve cross-plane redundancy), so that the compression devices are organized.

[0105] Establish RBS high-availability groups and build BGP FS neighbors: Establish a BGP FS multi-point to multi-point link building method, pair devices and establish communication mechanisms to ensure that devices can sense and communicate with each other. Each compression pool independently establishes an RR reflector in each data center, and transmits BGP FS routes through the RR reflector, changing from the traditional one-to-one link building to a many-to-many link building networking method; all compression devices publish the same BGP FS routes to the route reflector RR reflector to achieve continuous online operation of the compression protocol.

[0106] Configure ECMP / UCMP-based traffic redirection load balancing: First, configure the loopback interface of all devices in the compression pool with the same IP address, allowing data center edge devices to redirect traffic to the compression pool through this unified IP address. This, combined with a load balancing mechanism, enables reasonable traffic distribution among multiple devices. Second, configure multiple static equal-cost routes on the data center customer edge device (DataCenter - Customer Edge, DC-CE) pointing to this loopback interface IP, forming load balancing. Finally, configure the DC-CE with a policy-based routing (PBR) policy to redirect service traffic to the loopback interface IP. This ECMP-based load balancing ensures that traffic is evenly distributed across the devices in the compression pool, preventing overload of any single device.

[0107] Configure the primary and backup next-hop for the decompression PBR: Configure the decompression PBR on the cross link between DC-CE, carrying 108-field traffic to the compression pool for processing. The decompression PBR is set to multi-next-hop mode, with two next hops: the primary next hop points to the same-plane resource pool, and the backup next hop points to the DC-CE cross link. When the primary plane compression pool fails, it automatically switches to the backup next hop, achieving cross-plane takeover of the compression pool.

[0108] The system continuously monitors and determines whether a fault is a single device compression failure or a single-plane compression failure, employing different handling procedures for each type. When a single device compression failure occurs, the RBS group interconnection is triggered to forward traffic. The faulty device forwards traffic to another healthy device in the same group via its paired interconnection. Specifically, the two devices in the RBS group periodically exchange compression status information. When one device detects a compression failure, it automatically forwards traffic to another device in the same RBS group via the interconnection. The RBS interconnection uses a dual-wire connection for protection. Ultimately, the backup device takes over the decompression service, achieving zero service interruption in the event of a single device failure, improving reliability, and achieving high availability protection between RBS groups. When a single-plane compression failure occurs, the decompression PBR is configured with a multi-next-hop mode. When the primary plane compression pool fails, it automatically switches to the backup next hop, and traffic is forwarded to the RBS group in another plane via the backup path. This achieves a compression pool isolation cross-plane takeover mechanism, ensuring seamless takeover by the other plane in the event of a single-plane failure. Regardless of the type of failure, the WAN compression system ultimately achieves high availability, improves data compression efficiency, and ensures uninterrupted service and continuous data compression effectiveness.

[0109] Based on the above-described wide area network (WAN) data compression method, this application also provides a WAN data compression apparatus. The following will be combined with... Figure 6 The device is described in detail.

[0110] Figure 6 A schematic block diagram of a wide area network data compression apparatus according to an embodiment of this application is shown.

[0111] like Figure 6 As shown, the wide area network data compression device 800 of this embodiment includes a traffic diversion module 810, a load balancing module 820, and a compression fault switching module 830.

[0112] The traffic redirection module 810 is used to redirect the service traffic of the data center to the compression pool through a preset link establishment method; wherein, the preset link establishment method is a many-to-many link establishment networking method based on the border gateway protocol flow specification routing and route reflector. In one embodiment, the traffic redirection module 810 can be used to perform the operation S210 described above, which will not be repeated here.

[0113] The load balancing module 820 is used to distribute the service traffic to the compression devices in the compression pool based on a load balancing mechanism and a redirected traffic load sharing strategy, and to determine the target compression devices. In one embodiment, the load balancing module 820 can be used to perform the operation S220 described above, which will not be repeated here.

[0114] The compression fault switching module 830 is used to compress and process allocated service traffic through the target compression device based on a logical layering model and a compression fault switching strategy; wherein, the compression fault switching strategy includes an intra-group fault switching strategy and a cross-plane fault switching strategy. In one embodiment, the compression fault switching module 830 can be used to perform the operation S230 described above, which will not be repeated here.

[0115] According to an embodiment of this application, the traffic redirection module 810 includes a link building unit, which is used to deploy a route reflector corresponding to the compression pool in the data center; publish the same Border Gateway Protocol (BGP) flow specification route to the route reflector through all devices in the compression pool; and transmit the BGP flow specification route to the edge devices in the data center through the route reflector.

[0116] According to embodiments of this application, the load balancing mechanism includes an equal-cost multi-path load balancing mechanism and / or an unequal-cost multi-path load balancing mechanism; the load balancing module 820 includes a load sharing unit, which is used to configure all devices in the compression pool with the same loopback address; configure the static equal-cost route of the edge device of the data center to point to the loopback address, and configure the policy route of the edge device to redirect the service traffic to the loopback address; in a homogeneous device scenario, the service traffic is evenly distributed among the compression devices in the compression pool based on the equal-cost multi-path load balancing mechanism; and in a heterogeneous device scenario, the bandwidth weight of the compression device is configured through the unequal-cost multi-path load balancing mechanism, and the service traffic is distributed based on the bandwidth weight.

[0117] According to an embodiment of this application, the compression fault switching module 830 includes a logical layering unit, which is used to group devices into pairs based on the model of the compression devices, determine a remote backup service group, wherein the compression devices in the remote backup service group are interconnected through a two-line three-layer interconnection; construct the compression pool according to the remote backup service group; and divide the compression pool into network planes to obtain a first plane compression pool and a second plane compression pool.

[0118] According to an embodiment of this application, the compression fault switching module 830 further includes an intra-group fault switching unit, which is used to monitor the compression status information of the target compression device in the remote backup service group in real time and determine the intra-group status; when the intra-group status is normal, the allocated service traffic is compressed and processed in parallel by the target compression device in the remote backup service group; and when the intra-group status is abnormal, the service traffic of the abnormal device is taken over and processed by the normal compression device in the remote backup service group based on the interconnection line.

[0119] According to an embodiment of this application, the compression fault switching module 830 further includes a plane fault switching unit. The plane fault switching unit is used to monitor the compression status information of target compression devices in the first plane compression pool and the second plane compression pool in real time to determine the plane status. When the plane status is normal, the decompression strategy routing is switched to the primary next hop, wherein the primary next hop points to the same plane compression pool; the allocated service traffic is compressed and processed by the target compression device in the first plane compression pool; and when the plane status is abnormal, the decompression strategy routing is switched to the backup next hop, wherein the backup next hop points to a crosslink; according to the decompression strategy routing, the service traffic of the abnormal plane compression pool is taken over and processed by the target compression device in the normal plane compression pool based on the crosslink.

[0120] According to an embodiment of this application, the device 800 further includes a physical isolation module, which is used to periodically detect the compression instance status of the target compression device through an operation plane script; close the associated physical port of the target compression device when the compression instance status meets the periodic abnormal conditions; and open the associated physical port of the target compression device when the compression instance status meets the recovery compression conditions.

[0121] According to embodiments of this application, any multiple modules among the traffic diversion module 810, load balancing module 820, compression failover module 830, and physical isolation module can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least some of the functions of one or more of these modules can be combined with at least some of the functions of other modules and implemented in one module. According to embodiments of this application, at least one of the traffic diversion module 810, load balancing module 820, compression failover module 830, and physical isolation module can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging the circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, at least one of the traffic redirection module 810, load balancing module 820, compression failover module 830, and physical isolation module can be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is run.

[0122] Figure 7 A block diagram schematically illustrates an electronic device suitable for implementing a wide area network data compression method according to an embodiment of this application.

[0123] like Figure 7 As shown, an electronic device 900 according to an embodiment of this application includes a processor 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage portion 908 into a random access memory (RAM) 903. The processor 901 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 901 may also include onboard memory for caching purposes. The processor 901 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of this application.

[0124] RAM 903 stores various programs and data required for the operation of electronic device 900. Processor 901, ROM 902, and RAM 903 are interconnected via bus 904. Processor 901 executes various operations of the method flow according to embodiments of this application by executing programs in ROM 902 and / or RAM 903. It should be noted that the programs may also be stored in one or more memories other than ROM 902 and RAM 903. Processor 901 may also execute various operations of the method flow according to embodiments of this application by executing programs stored in said one or more memories.

[0125] According to embodiments of this application, the electronic device 900 may further include an input / output (I / O) interface 905, which is also connected to a bus 904. The electronic device 900 may also include one or more of the following components connected to the input / output (I / O) interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the input / output (I / O) interface 905 as needed. A removable medium 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 910 as needed so that computer programs read from it can be installed into the storage section 908 as needed.

[0126] This application also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs, which, when executed, implement the method according to the embodiments of this application.

[0127] According to embodiments of this application, the computer-readable storage medium can be a non-volatile computer-readable storage medium, such as including but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this application, the computer-readable storage medium may include ROM 902 and / or RAM 903 and / or one or more memories other than ROM 902 and RAM 903 described above.

[0128] Embodiments of this application also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code enables the computer system to implement the wide area network data compression method provided in the embodiments of this application.

[0129] When the computer program is executed by the processor 901, it performs the functions defined in the system / apparatus of this application embodiment. According to the embodiments of this application, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0130] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via the communication section 909, and / or installed from a removable medium 911. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0131] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 909, and / or installed from the removable medium 911. When the computer program is executed by the processor 901, it performs the functions defined in the system of this application embodiment. According to the embodiments of this application, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0132] According to embodiments of this application, program code for executing the computer programs provided in the embodiments of this application can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can be executed entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0133] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0134] Those skilled in the art will understand that the features described in the various embodiments of this application can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in this application. In particular, the features described in the various embodiments of this application can be combined and / or combined in various ways without departing from the spirit and teachings of this application. All such combinations and / or combinations fall within the scope of this application.

Claims

1. A wide area network data compression method, characterized in that, The method includes: The data center's business traffic is diverted to the compression pool through a preset chain establishment method; wherein, the preset chain establishment method is a many-to-many chain establishment networking method based on border gateway protocol flow specification routing and route reflector; Based on a load balancing mechanism, a redirected traffic load balancing strategy is adopted to distribute the service traffic to the compression devices in the compression pool, and the target compression devices are determined; and Based on the logical layering model and the compression fault switching strategy, the allocated service traffic is compressed and processed through the target compression device; wherein, the compression fault switching strategy includes intra-group fault switching strategy and cross-plane fault switching strategy.

2. The method according to claim 1, characterized in that, The preset chain establishment methods include: Deploy the route reflector corresponding to the compression pool in the data center; All devices within the compression pool publish the same Border Gateway Protocol (BGP) flow specification route to the route reflector; and The border gateway protocol flow specification is routed to the edge device within the data center via the route reflector.

3. The method according to claim 1, characterized in that, The load balancing mechanism includes an equal-cost multi-path load balancing mechanism and / or an unequal-cost multi-path load balancing mechanism; the redirected traffic load sharing strategy includes: Configure all devices in the compression pool with the same loopback address; Configure the static equivalent-cost route of the edge device in the data center to point to the loopback address, and configure the policy route of the edge device to redirect the service traffic to the loopback address; In a homogeneous device scenario, based on the aforementioned equal-cost multi-path load balancing mechanism, the service traffic is evenly distributed among the compression devices in the compression pool; and In heterogeneous device scenarios, the bandwidth weight of the compression device is configured through the non-equivalent multipath load balancing mechanism, and the service traffic is allocated based on the bandwidth weight.

4. The method according to claim 1, characterized in that, The logical hierarchical model includes: Based on the model of the compression equipment, the equipment is paired and grouped to determine the remote backup service group, wherein the compression equipment in the remote backup service group is interconnected through a two-line three-layer interconnection. The compression pool is constructed based on the remote backup service group; and The compression pool is divided into network planes to obtain a first planar compression pool and a second planar compression pool.

5. The method according to claim 4, characterized in that, The intra-group failover strategy includes: Real-time monitoring of the compression status information of the target compression devices in the remote backup service group to determine the status within the group; When the group is in a normal state, the allocated service traffic is compressed and processed in parallel by the target compression device in the remote backup service group; and In the event of an abnormal status within the group, the normal compression device in the remote backup service group takes over and processes the service traffic of the abnormal device based on the interconnection line.

6. The method according to claim 4, characterized in that, The cross-plane fault switching strategy includes: Real-time monitoring of the compression status information of the target compression devices in the first and second planar compression pools to determine the planar status; When the plane status is normal, the decompression strategy routing is switched to the primary next hop, wherein the primary next hop points to the same plane compression pool; the allocated service traffic is compressed and processed by the target compression device in the first plane compression pool; and In the event that the plane state is abnormal, the decompression strategy routing is switched to the backup next hop, wherein the backup next hop points to the crosslink; according to the decompression strategy routing, the target compression device of the normal plane compression pool takes over the processing of the service traffic of the abnormal plane compression pool based on the crosslink.

7. The method according to claim 1, characterized in that, The method further includes: The target compression device's compression instance status is periodically checked by manipulating the plane script; If the compression instance status meets the periodic abnormality condition, shut down the associated physical port of the target compression device; and If the compression instance status meets the conditions for resuming compression, open the associated physical port of the target compression device.

8. A wide area network data compression device, characterized in that, The device includes: The traffic diversion module is used to divert the business traffic of the data center to the compression pool through a preset link establishment method; wherein, the preset link establishment method is a many-to-many link establishment networking method based on the border gateway protocol flow specification routing and route reflector. The load balancing module is used to distribute the service traffic to the compression devices in the compression pool based on a load balancing mechanism and a redirected traffic load balancing strategy, and to determine the target compression devices; and The compression fault switching module is used to compress and process the allocated service traffic through the target compression device based on the logical layering model and the compression fault switching strategy; wherein, the compression fault switching strategy includes intra-group fault switching strategy and cross-plane fault switching strategy.

9. An electronic device, comprising: One or more processors; Memory, used to store one or more computer programs. The characteristic feature is that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7.

11. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7.

Images