Decompression backup implementation method and device and electronic equipment

Abstract

The invention provides a decompression backup implementation method and device and electronic equipment. According to the embodiment of the invention, the method for backup protection between the decompression ends is realized, so that the compression end compresses the message and forwards the message to the main decompression end for decompression when the decompression capability of the main decompression end is normal; and when the decompression capability of the main decompression end is abnormal, the message which is originally decompressed by the main decompression end can be quickly switched to the standby decompression end with normal decompression capability for decompression, so that the problems such as data discarding and the like caused by the fact that the decompression end cannot decompress are avoided.

Description

Technical Field

[0001] The present application relates to network communication technology, and in particular to a method, device and electronic device for implementing decompression backup. Background Art

[0002] In specific applications, data is often transmitted between two PEs. Figure 1 In the example of PE1 transmitting data to PE2, PE1 acts as a compression end, which compresses the data to be transmitted to PE2 and transmits it to PE2. PE2 acts as a decompression end, and after receiving the compressed data transmitted from PE1, it decompresses the compressed data and processes the decompressed data, such as forwarding it.

[0003] However, in actual implementation, the decompression capability of the decompression end often fails. Once the decompression capability of the decompression end fails, many problems such as discarding data will be caused due to the inability to decompress. Summary of the invention

[0004] The present application provides a method, device and electronic device for implementing decompression backup to achieve decompression backup and avoid problems caused by failure to decompress, such as discarding data.

[0005] The embodiment of the present application provides a method for implementing decompression backup, which is applied to a PE designated as a compression end in a data center. The method includes:

[0006] When the decompression capability of the main decompression end adapted to the compression end is normal, based on the flow specification flowspec policy corresponding to the main decompression end, compress the message matching the flowspec policy to obtain a compressed message, redirect the compressed message to the interface between the compression end and the main decompression end to forward the compressed message to the main decompression end for decompression;

[0007] When the decompression capability of the main decompression end is abnormal, based on the flowspec policy corresponding to one of the backup decompression ends of the main decompression end, the message matching the flowspec policy is compressed to obtain a compressed message, and the compressed message is redirected to the interface between the compression end and the backup decompression end to forward the compressed message to the backup decompression end for decompression.

[0008] A method for implementing decompression backup is applied to a PE in a data center, wherein the PE is designated as one of the decompression ends of the adapted compression end, and the method comprises:

[0009] When the decompression end is selected by the compression end as the main decompression end,

[0010] If the decompression capability of the decompression end is normal, the message redirected by the compression end is received and decompressed; the compression end compresses the message matching the flowspec policy based on the flowspec policy corresponding to the main decompression end and redirects it to the main decompression end;

[0011] If the decompression capability of the current decompression end is abnormal, the compression end is notified so that when the decompression capability of the primary decompression end is abnormal, the compression end compresses the message matching the flowspec policy based on the flowspec policy corresponding to the backup decompression end and redirects it to the interface between the compression end and the backup decompression end to forward it to the backup decompression end for decompression.

[0012] A decompression backup implementation device, which is applied to a PE designated as a compression end in a data center, and includes:

[0013] A receiving unit, used for receiving a message;

[0014] a processing unit, configured to, when the decompression capability of the main decompression end adapted to the compression end is normal, compress the message matching the flowspec policy based on the flow specification flowspec policy corresponding to the main decompression end to obtain a compressed message, redirect the compressed message to the interface between the compression end and the main decompression end to forward the compressed message to the main decompression end for decompression; and

[0015] When the decompression capability of the main decompression end is abnormal, based on the flowspec policy corresponding to one of the backup decompression ends of the main decompression end, the message matching the flowspec policy is compressed to obtain a compressed message, and the compressed message is redirected to the interface between the compression end and the backup decompression end to forward the compressed message to the backup decompression end for decompression.

[0016] A decompression backup implementation device is applied to a PE in a data center, and the PE is designated as one of the decompression ends of the adapted compression end, and the device includes:

[0017] The decompression unit is used for, when the decompression end is selected by the compression end as the main decompression end,

[0018] If the decompression capability of the decompression end is normal, the message redirected by the compression end is received and decompressed; the compression end compresses the message matching the flowspec policy based on the flowspec policy corresponding to the main decompression end and redirects it to the main decompression end;

[0019] A notification unit is used to notify the compression end when the decompression capability of the decompression end is abnormal when the decompression capability of the decompression end is selected as the main decompression end by the compression end, so that the compression end can compress the message matching the flowspec policy based on the flowspec policy corresponding to the backup decompression end and redirect it to the interface between the compression end and the backup decompression end so as to forward it to the backup decompression end for decompression.

[0020] An electronic device, comprising: a processor and a machine-readable storage medium;

[0021] The machine-readable storage medium stores computer instructions, and when the computer instructions are executed by a processor, the steps in any of the above methods are implemented.

[0022] It can be seen from the above technical scheme that this embodiment implements a method for backup protection between decompression ends, so that when the decompression capability of the main decompression end is normal, the compression end compresses the message and forwards it to the main decompression end for decompression; when the decompression capability of the main decompression end is abnormal, the message originally decompressed by the main decompression end will be quickly switched to one of the backup decompression ends with normal decompression capability for decompression, thereby avoiding problems caused by the inability to decompress, such as discarding data. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0024] Figure 1 Schematic diagram of data transmission between PEs;

[0025] Figure 2 A flow chart of the method provided in the embodiment of the present application;

[0026] Figure 3 An application networking diagram provided for an embodiment of the present application;

[0027] Figure 4 A schematic diagram of the compressed message format provided in an embodiment of the present application;

[0028] Figure 5 A schematic diagram of another compressed message format provided in an embodiment of the present application;

[0029] Figure 6 Another method flow chart provided for an embodiment of the present application;

[0030] Figure 7 A structural diagram of a device provided in an embodiment of the present application;

[0031] Figure 8Another device structure diagram provided for an embodiment of the present application;

[0032] Fig. 9 A structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0034] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. The singular forms "a", "said" and "the" used in this application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.

[0035] In order to enable those skilled in the art to better understand the technical solutions provided by the embodiments of the present application, and to make the above-mentioned purposes, features and advantages of the embodiments of the present application more obvious and easy to understand, the technical solutions in the embodiments of the present application are further described in detail below in conjunction with the accompanying drawings.

[0036] See also Figure 2 , Figure 2 A flow chart of a method provided in an embodiment of the present application. The method is applied to a PE designated as a compression end in a data center. In this embodiment, at least two PEs are designated as decompression ends adapted to the above compression end according to actual needs. Here, the at least two decompression ends may be in the same data center.

[0037] As an embodiment, the at least two decompression ends and the compression end may be located in the same data center or in different data centers, which is not specifically limited in this embodiment.

[0038] like Figure 2 As shown, the process may include the following steps:

[0039] Step 201, when the decompression capability of the main decompression end serving as the adaptation compression end is normal, based on the flow specification policy flowspec corresponding to the main decompression end, the message matching the flowspec policy is compressed to obtain a compressed message, and the compressed message is redirected to the interface between the compression end and the main decompression end to forward the compressed message to the main decompression end for decompression.

[0040] Optionally, in this embodiment, before step 201, the method may further include: receiving flow specification (flowspec) policies respectively sent by at least two PEs; wherein the at least two PEs are designated as decompression ends adapted to the compression end.

[0041] In this embodiment, the flowspec policy sent by any decompression end is used to instruct the compression end to compress the message matching the flowspec policy and redirect it to the decompression end for decompression. An example will be described below.

[0042] In this embodiment, the compression end selects one from the at least two PEs as the main decompression end based on the flowspec policies sent by the PE ends, and the remaining PEs serve as backup decompression ends.

[0043] As an embodiment, there are many ways to select one of the at least two PEs as the main decompression end, such as selecting one of the at least two PEs as the main decompression end based on setting the selection rule of the main decompression end such as the smallest IP address, etc. This embodiment does not specifically limit it.

[0044] When one of the at least two PEs is selected as the main decompression end, the remaining PEs are considered as backup decompression ends. Based on this, as an embodiment, when the decompression capability of the main decompression end is normal, the compression end compresses the message matching the flowspec policy based on the flowspec policy sent by the main decompression end and redirects it to the interface between the compression end and the main decompression end to forward it to the main decompression end for decompression.

[0045] Step 202, when the decompression capability of the main decompression end is abnormal, based on the flowspec policy corresponding to the backup decompression end of the main decompression end, the message matching the flowspec policy is compressed to obtain a compressed message, and the compressed message is redirected to the interface between the compression end and the backup decompression end to forward the compressed message to the backup decompression end for decompression.

[0046] As an embodiment, the backup decompression end of the main decompression end may be one of the backup decompression ends of the main decompression end with normal decompression capability.

[0047] pass Figure 2It can be seen from the shown process that this embodiment implements a method for backup protection between decompression ends, so that when the decompression capability of the main decompression end is normal, the compression end compresses the message and forwards it to the main decompression end for decompression; when the decompression capability of the main decompression end is abnormal, the message originally decompressed by the main decompression end will be quickly switched to one of the backup decompression ends of the main decompression end with normal decompression capability for decompression, so as to avoid problems caused by the inability to decompress, such as discarding data.

[0048] Below Figure 2 The process shown is described in detail:

[0049] In this embodiment, IPv4 is used as an example, and IPv6 is similar. Figure 3 As shown, if the compression end is PE1, there are two decompression ends adapted to the compression end, namely PE2 and PE3.

[0050] As an embodiment, each decompression end is respectively configured with a flow-route configuration. As an embodiment, the flow-route configured at any decompression end includes: wide area application service (waas: Wide Area Application Services) configuration (also called compression configuration), redirection configuration and matching rules.

[0051] Among them, the waas configuration (also called compression configuration) includes subcard information. In this embodiment, the subcard information includes the identifier of the subcard used for compression and decompression locally, such as the slot number, or the identifier of the subcard used for decompression locally, such as the slot number, etc. For example, subslot1 and subslot2 of slot number slot4 are subcards used for compression and decompression.

[0052] In this embodiment, the redirection configuration in the flow-route sent by any decompression end includes a redirection next hop. As an embodiment, the redirection next hop included in the redirection configuration in the flow-route sent by any decompression end is used to carry in the flowspec policy subsequently forwarded by the decompression end, so that the compression end determines the decompression end based on the flowspec policy. As an embodiment, the redirection next hop here can be represented by the loopback address of the decompression end, etc. For example, the redirection next hop is 888::888color 00:1.

[0053] In this embodiment, the matching rule may include a five-tuple, such as a protocol identifier, a source IP address, a destination IP address, a source port number, and a destination port number. The protocol identifier here may not be specifically limited, such as a UDP protocol identifier 17, a TCP protocol identifier 6, etc., which is not specifically limited in this embodiment. For example, the matching rule is: destination IP address 23.0.0.0 255.0.0.0, source IP address 11.0.0.0 255.0.0.0, protocol number (protocol) 17, destination port number 1024, source port number 1.

[0054] In this embodiment, any decompression end generates a flowspec policy based on the locally configured flow-route and sends it to the compression end.

[0055] When the compressor receives the flowspec policies sent by each decompression end, it selects one decompression end as the primary decompression end and the remaining decompression ends as backup decompression ends. The specific selection method is described above.

[0056] In this embodiment, the compression end generates a flowspec route corresponding to the primary decompression end based on the flowspec policy sent by the primary decompression end and sends it to the local hardware.

[0057] Here, flowspec routing can include compression policy and redirection policy.

[0058] The compression policy has a corresponding compression operation matching rule, and the compression policy is used to instruct to perform a compression operation on a message matching the compression operation matching rule.

[0059] The redirection policy has a corresponding redirection operation matching rule; the redirection policy is used to indicate that the compressed message matching the redirection operation matching rule is redirected to the interface between the compression end and the main decompression end.

[0060] Optionally, the compression operation matching rule and the redirection operation matching rule may be different. For example, the compression operation matching rule includes at least a first protocol identifier, and the redirection operation matching rule includes at least a second protocol identifier; the first protocol identifier and the second protocol identifier are different, the second protocol identifier is an identifier of the compression protocol, such as 108, and the first protocol identifier in the compression operation matching rule is, for example, a UDP protocol identifier 17, a TCP protocol identifier 6, etc.

[0061] In this embodiment, the parameters in the compression operation matching rule and the redirection operation matching rule except the protocol identifier may be the same. For example, the parameter may be the source IP address, the destination IP address, the source port number, and the destination port number. This embodiment is not specifically limited.

[0062] like Figure 3As shown, after PE1 as the compression end receives the flowspec policies respectively sent by PE2 and PE3 as the decompression ends, one is selected from PE2 and PE3 as the main decompression end, and the remaining PEs are used as backup decompression ends.

[0063] Taking PE1 selecting PE2 as the primary decompression end and PE3 as the backup decompression end as an example, PE1 generates a flowspec route (referred to as flowspec route 1_2) based on the flowspec policy announced by PE2 and sends it to the hardware.

[0064] flowspec route 1_2 may include compression strategy and redirection strategy.

[0065] Among them, the compression operation matching rule corresponding to the compression policy in flowspec route 1_2 is as follows:

[0066] Destination IP address: 23.0.0.0 255.0.0.0;

[0067] Destination port number: 1024;

[0068] Protocol number: 17;

[0069] Source IP address: 11.0.0.0 255.0.0.0;

[0070] Source port number: 1.

[0071] For example, the redirection operation matching rules corresponding to the redirection policy in flowspec route 1_2 are:

[0072] Destination IP:23.0.0.0 255.0.0.0;

[0073] Destination port:1024;

[0074] Protocol: 108;

[0075] Source IP:11.0.0.0 255.0.0.0;

[0076] Source port: 1.

[0077] The interface to which the redirection policy in flowspec route 1_2 redirects is the interface corresponding to the following identifier: Forwarding ID: 2150629380 (redirects to the SRv6 TE policy between PE1 and PE2 to forward to PE2 for decompression).

[0078] Optionally, PE1 will also generate a corresponding flowspec route (recorded as flowspec route 1_3) based on the flowspec policy announced by PE3 and temporarily store it. In this embodiment, in the flowspec routes generated by the flowspec policies sent by different decompression ends adapted to the same compression end, the compression operation matching rules corresponding to the compression policies are the same. Optionally, in this embodiment, in the flowspec routes generated by the flowspec policies sent by different decompression ends adapted to the same compression end, the redirection operation matching rules corresponding to the redirection policies are the same.

[0079] In this embodiment, the above redirection policy may include an interface to which it is redirected, and different redirection policies redirect to different interfaces. For example, in the flowspec route corresponding to PE2, the interface to which the redirection policy redirects may be the interface corresponding to the following interface identifier: Forwarding ID is 2150629380 (redirected to the SRv6 TE policy between PE1 and PE2), and in the flowspec route corresponding to PE3, the interface to which the redirection policy redirects may be the interface corresponding to the following interface identifier: Forwarding ID is 2150629381 (redirected to the SRv6 TE policy between PE1 and PE3).

[0080] For example, the compression operation matching rule in the compression policy in the flowspec route (recorded as flowspec route 1_3) corresponding to PE3 is as follows:

[0081] Destination IP:23.0.0.0 255.0.0.0;

[0082] Destination port:1024;

[0083] Protocol: 17;

[0084] Source IP:11.0.0.0 255.0.0.0;

[0085] Source port: 1.

[0086] For example, the redirection operation matching rules in the redirection policy of flowspec route 1_3 are:

[0087] Destination IP:23.0.0.0 255.0.0.0;

[0088] Destination port:1024;

[0089] Protocol: 108;

[0090] Source IP:11.0.0.0 255.0.0.0;

[0091] Source port:1.

[0092] The interface to which the redirection policy in flowspec route 1_3 redirects can be the interface corresponding to the following interface identifier: Forwarding ID: 2150629381 (indicating redirection to the SRv6TE policy between PE1 and PE3 to forward to PE3 for decompression).

[0093] like Figure 3 As shown in FIG. 1 , when the compression end PE1 receives the IPv4 message, it finds that the IPv4 message matches the compression operation matching rule in flowspec route 1_2, and then diverts the IPv4 message to the local subcard for compression for compression. The format of the compressed message (referred to as the compressed message) is as follows: Figure 4 After that, the compressed message is sent back from the above-mentioned subcard to the network processing unit (NP) in the compression end PE1. After the compressed message reaches the NP, it is found that the compressed message matches the redirection operation matching rule in flowspec route 1_2. Based on the redirection operation, the compressed message is redirected to the SRv6 TEpolicy tunnel between PE1 and PE2, and finally sent to PE2 for decompression.

[0094] In this embodiment, when all the subcards for decompression bound to PE2 as the main decompression end fail, that is, the decompression capability of PE2 fails, PE2 will notify PE1 as the compression end. When PE1 receives the notification, it is considered that the decompression capability of the main decompression end is detected to be abnormal. Thereafter, PE1 as the compression end will select one of the backup decompression ends with normal decompression capability as the main decompression end. For example, PE1 selects PE3 as the new main decompression end. After that, PE1 quickly switches the original optimal flowspec route stored in the local hardware (that is, the flowspec route corresponding to the main decompression end with abnormal decompression capability) to the flowspec route corresponding to the newly selected main decompression end, that is, PE3. For example, PE1 sends the flowspec route corresponding to the newly selected main decompression end, that is, PE3, to the local hardware to replace the flowspec route corresponding to the original main decompression end, that is, PE2 with abnormal decompression capability. The flowspec route corresponding to PE3 is shown above.

[0095] Afterwards, if Figure 3 As shown in FIG. 1 , when the compression end PE1 receives the IPv4 message, it finds that the IPv4 message matches the compression operation matching rule in flowspec route 1_3, and then diverts the IPv4 message to the local subcard for compression for compression. The format of the compressed message (referred to as the compressed message) is as follows: Figure 4 As shown. The compressed message is then sent back from the above-mentioned subcard to the network processing unit (NP) in the compression end PE1. After the compressed message reaches the NP, it is found that the compressed message matches the redirection operation matching rule in flowspec route 1_3. Based on the redirection operation, the compressed message is redirected to the SRv6TE policy tunnel between PE1 and PE3, and finally sent to PE3 for decompression. Finally, when the decompression capability of the main decompression end is abnormal, the message originally decompressed by the main decompression end will be quickly switched to one of the backup decompression ends with normal decompression capability of the main decompression end for decompression, avoiding data discard due to decompression failure.

[0096] The following describes the format of the compressed message:

[0097] In this embodiment, the above compression of messages, such as IPv4 messages, can be implemented by using a compression protocol of the IP layer, such as the IP Payload Compression Protocol (IPComp or IPPCP for short). The compression of IPPCP is lossless, so that the message is the same as the original message after compression and decompression. At the same time, the compression of IPPCP is stateless, and the compression and decompression of each message does not depend on other messages, and does not pay attention to the disorder or loss of messages. Each message is encapsulated separately after compression.

[0098] IPPCP is an underlying compression protocol for data packets at the IP layer. The IPPCP compressed packets are different from ordinary IP packets, and the payload in the IPPCP compressed packets is compressed.

[0099] IPPCP compresses messages by inserting its own protocol header (IPPCP message header for short) and changing individual fields of messages such as IPv4 or IPv6 messages. The IPPCP message header contains the following three fields: Next Header, Flags, and Compression Parameter Index.

[0100] The following table 1 shows an example of the explanation of each field in the IPPCP message header:

[0101]

[0102] Table 1

[0103] Taking IPv4 packets as an example, the format of the compressed packets obtained by compressing IPv4 packets based on IPPCP is as follows: Figure 4 As shown. Figure 4 As shown in the figure, in addition to inserting the IPPCP header shown in Table 1 above, the values ​​of the following three fields of the original IPv4 message have also changed:

[0104] Total Length field (Total Length): refers to the length of the entire encapsulated IP datagram, including the IP header, IPPCP header and compressed payload.

[0105] Protocol field (Protocol): Set to 108, identifying the protocol type as IPPCP.

[0106] IP message header check field (Header Checksum): used to confirm whether the IP message header has changed after being transmitted to the receiving end.

[0107] Taking IPv6 packets as an example, the format of the compressed packets obtained by compressing IPv6 packets based on IPPCP is as follows: Figure 5 As shown. Figure 5 As shown in Table 1, in addition to inserting the IPPCP header shown in Table 1 above, the values ​​of the following two fields of the original IPv6 message have also changed:

[0108] Payload Length: indicates the length of the compressed payload.

[0109] Next Header field: set to 108, indicating that the protocol type is IPPCP.

[0110] The above is an embodiment of the present application described from the perspective of the compression end. The following is an embodiment of the present application described from the perspective of the decompression end:

[0111] See also Figure 6 , Figure 6 Another method flow chart provided in an embodiment of the present application. The method is applied to a PE in a data center, and the PE is designated as one of the decompression ends of the adapted compression end. The method includes:

[0112] Step 601, when the decompression end is selected by the compression end as the main decompression end, if the decompression capability of the decompression end is normal, the message redirected to the receiving compression end is decompressed; the compression end compresses the message matching the flowspec policy based on the flowspec policy corresponding to the main decompression end and redirects it to the main decompression end.

[0113] This step 601 corresponds to the above-mentioned step 201 .

[0114] Step 602, when the decompression end is selected by the compression end as the main decompression end, if the decompression capability of the decompression end is abnormal, the compression end is notified so that when the decompression capability of the main decompression end is abnormal, the compression end compresses the message matching the flowspec policy based on the flowspec policy corresponding to the backup decompression end and redirects it to the interface between the compression end and the backup decompression end to forward it to the backup decompression end for decompression.

[0115] This step 602 corresponds to step 202 .

[0116] So far, completed Figure 6 The process shown.

[0117] The method provided in the embodiment of the present application is described above. The device provided in the embodiment of the present application is described below:

[0118] See also Figure 7 , Figure 7 This is a structural diagram of a device provided in an embodiment of the present application. The device is applied to a PE designated as a compression end in a data center, and the device includes:

[0119] A receiving unit, used for receiving a message;

[0120] a processing unit, configured to compress a message matching the flowspec policy based on a flow specification policy corresponding to the main decompression end to obtain a compressed message, redirect the compressed message to an interface between the compression end and the main decompression end to forward the compressed message to the main decompression end for decompression, when the decompression capability of the main decompression end adapted to the compression end is normal; and

[0121] When the decompression capability of the main decompression end is abnormal, based on the flowspec policy corresponding to one of the backup decompression ends with normal decompression capability of the main decompression end, the message matching the flowspec policy is compressed to obtain a compressed message, and the compressed message is redirected to the interface between the compression end and the backup decompression end to forward the compressed message to the backup decompression end for decompression.

[0122] Optionally, the processing unit further selects one of the at least two PEs as a main decompression end adapted to the compression end, and the remaining PEs as backup decompression ends of the main decompression end. The at least two PEs are designated as decompression ends adapted to the compression end.

[0123] Optionally, the receiving unit further receives flow specification flowspec policies respectively sent by at least two PEs; the flowspec policy sent by any decompression end is used to instruct the compression end to compress the message matching the flowspec policy and redirect it to the decompression end for decompression;

[0124] Among them, the flowspec policy corresponding to the main decompression end is the flowspec policy sent by the main decompression end; the flowspec policy corresponding to the standby decompression end is the flowspec policy sent by the standby decompression end.

[0125] Optionally, the processing unit further includes:

[0126] Generate a flowspec route corresponding to the main decompression end based on the flowspec policy corresponding to the main decompression end and send it to the local hardware; the flowspec route is used to guide the compression end to compress the message matching the flowspec route using the flowspec route when the decompression capability of the main decompression end is normal, and redirect it to the interface between the compression end and the main decompression end to forward it to the main decompression end for decompression;

[0127] The method of compressing a message matching the flowspec policy based on the flow specification flowspec policy corresponding to the main decompression end to obtain a compressed message includes:

[0128] Based on the flowspec route corresponding to the main decompression end, the message matching the flowspec route is compressed to obtain a compressed message.

[0129] Optionally, the processing unit further includes:

[0130] Generate the flowspec route corresponding to the standby compression end based on the flowspec policy corresponding to the standby compression end.

[0131] The compressing a message matching the flowspec policy based on the flowspec policy corresponding to one of the standby decompression ends of the main decompression end to obtain a compressed message includes:

[0132] Select one of the backup decompression ends with normal decompression capability as the new primary decompression end;

[0133] Send the flowspec route corresponding to the newly selected primary decompression end to the local hardware to replace the flowspec route corresponding to the original primary decompression end with abnormal decompression capability;

[0134] Based on the flowspec route corresponding to the main decompression end, the message matching the flowspec route is compressed to obtain a compressed message.

[0135] Optionally, the flowspec route corresponding to the primary decompression end includes a compression strategy and a redirection strategy;

[0136] The compression strategy has a corresponding compression operation matching rule, and the compression strategy is used to instruct to compress the message matching the compression operation matching rule;

[0137] The redirection policy has a corresponding redirection operation matching rule; the redirection policy is used to indicate that the compressed message matching the redirection operation matching rule is redirected to the interface between the compression end and the main decompression end.

[0138] The compression operation matching rule includes at least a first protocol identifier, and the redirection operation matching rule includes at least a second protocol identifier; the first protocol identifier and the second protocol identifier are different, and the second protocol identifier is an identifier of a compression protocol.

[0139] Optionally, in the flowspec routes corresponding to different decompression ends, the compression operation matching rules are the same;

[0140] In the flowspec routes corresponding to different decompression ends, the redirection operation matching rules are the same;

[0141] The redirection strategy includes an interface to which the redirection is directed; different redirection strategies redirect to different interfaces.

[0142] Optionally, the compressing a message matching the flowspec route to obtain a compressed message based on the flowspec route corresponding to the main decompression end includes:

[0143] If the message matches the compression operation matching rule in the flowspec route corresponding to the primary decompression end, the message is compressed to obtain a compressed message;

[0144] The redirecting of the compressed message to the interface between the compression end and the main decompression end to forward the compressed message to the main decompression end for decompression includes: if the compressed message matches the redirection operation matching rule in the flowspec route corresponding to the main decompression end, then based on the redirection policy in the flowspec route corresponding to the main decompression end, redirecting the compressed message to the interface between the compression end and the main decompression end to send the compressed message to the main decompression end.

[0145] So far, completed Figure 7 Structural description of the device shown.

[0146] See also Figure 8 , Figure 8 Another device structure diagram provided in an embodiment of the present application. The device is applied to a PE in a data center, and the PE is designated as one of the decompression ends of the adapted compression end, and the device includes:

[0147] The decompression unit is used for, when the decompression end is selected by the compression end as the main decompression end,

[0148] If the decompression capability of the decompression end is normal, the message redirected by the compression end is received and decompressed; the compression end compresses the message matching the flowspec policy based on the flowspec policy corresponding to the main decompression end and redirects it to the main decompression end;

[0149] A notification unit is used to notify the compression end when the decompression capability of the decompression end is abnormal when the decompression capability of the decompression end is selected as the main decompression end by the compression end, so that the compression end can compress the message matching the flowspec policy based on the flowspec policy corresponding to the backup decompression end and redirect it to the interface between the compression end and the backup decompression end so as to forward it to the backup decompression end for decompression.

[0150] Based on the same application concept as the above method, the present application embodiment also provides Figure 7 or Figure 8 The hardware structure of the device shown in FIG. Fig. 9As shown, the hardware structure includes: a processor and a machine-readable storage medium. The machine-readable storage medium stores computer instructions, and when the computer instructions are executed by the processor, the method disclosed in the above example of this application can be implemented.

[0151] Based on the same application concept as the above method, an embodiment of the present application also provides a machine-readable storage medium, on which a number of computer instructions are stored. When the computer instructions are executed by a processor, the method disclosed in the above example of the present application can be implemented.

[0152] Exemplarily, the above-mentioned machine-readable storage medium can be any electronic, magnetic, optical or other physical storage device, which can contain or store information, such as executable instructions, messages, etc. For example, the machine-readable storage medium can be: RAM (Radom Access Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as hard disk drive), solid state drive, any type of storage disk (such as CD, DVD, etc.), or similar storage medium, or a combination thereof.

[0153] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which may be in the form of a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, a game console, a tablet computer, a wearable device or a combination of any of these devices.

[0154] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0155] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the embodiments of the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0156] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable message processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable message processing device generate instructions for implementing the process in the flowchart. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0157] Furthermore, these computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable message processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0158] These computer program instructions may also be loaded onto a computer or other programmable message processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0159] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A decompression backup implementation method, characterized in that: The method is applied to a PE designated as a compression end in a data center, and the method includes: When the decompression capability of the main decompression end adapted to the compression end is normal, based on the flow specification flowspec policy corresponding to the main decompression end, compress the message matching the flowspec policy to obtain a compressed message, redirect the compressed message to the interface between the compression end and the main decompression end to forward the compressed message to the main decompression end for decompression; When the decompression capability of the main decompression end is abnormal, based on the flowspec policy corresponding to one of the backup decompression ends of the main decompression end, the message matching the flowspec policy is compressed to obtain a compressed message, and the compressed message is redirected to the interface between the compression end and the backup decompression end to forward the compressed message to the backup decompression end for decompression.

2. The method according to claim 1, characterized in that: The method further comprises: One of the at least two PEs is selected as a main decompression end adapted to the compression end, and the remaining PEs are used as backup decompression ends of the main decompression end, and the at least two PEs are used as decompression ends adapted to the compression end.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: Receive flow specification flowspec policies respectively sent by at least two PEs; wherein the flowspec policy sent by any decompression end is used to instruct the compression end to compress the message matching the flowspec policy and redirect it to the decompression end for decompression; Among them, the flowspec policy corresponding to the main decompression end is the flowspec policy sent by the main decompression end; the flowspec policy corresponding to the standby decompression end is the flowspec policy sent by the standby decompression end.

4. The method according to claim 1, characterized in that: The method further comprises: Generate a flowspec route corresponding to the main decompression end based on the flowspec policy corresponding to the main decompression end and send it to the local hardware; the flowspec route is used to guide the compression end to compress the message matching the flowspec route using the flowspec route when the decompression capability of the main decompression end is normal, and redirect it to the interface between the compression end and the main decompression end to forward it to the main decompression end for decompression; The method of compressing a message matching the flowspec policy based on the flow specification flowspec policy corresponding to the main decompression end to obtain a compressed message includes: Based on the flowspec route corresponding to the main decompression end, the message matching the flowspec route is compressed to obtain a compressed message.

5. The method according to claim 1, characterized in that The method further comprises: Generate the flowspec route corresponding to the standby compression end based on the flowspec policy corresponding to the standby compression end; The compressing a message matching the flowspec policy based on the flowspec policy corresponding to one of the standby decompression ends of the main decompression end to obtain a compressed message includes: Select one of the backup decompression ends with normal decompression capability as the new primary decompression end; Send the flowspec route corresponding to the newly selected primary decompression end to the local hardware to replace the flowspec route corresponding to the original primary decompression end with abnormal decompression capability; Based on the flowspec route corresponding to the main decompression end, the message matching the flowspec route is compressed to obtain a compressed message.

6. The method according to claim 4 or 5, characterized in that: The flowspec route corresponding to the main decompression end includes compression strategy and redirection strategy; The compression strategy has a corresponding compression operation matching rule, and the compression strategy is used to instruct to compress the message matching the compression operation matching rule; The redirection policy has a corresponding redirection operation matching rule; the redirection policy is used to indicate that the compressed message matching the redirection operation matching rule is redirected to the interface between the compression end and the main decompression end.

7. The method according to claim 6, characterized in that The compression operation matching rule includes at least a first protocol identifier, and the redirection operation matching rule includes at least a second protocol identifier; the first protocol identifier and the second protocol identifier are different, and the second protocol identifier is an identifier of a compression protocol.

8. The method according to claim 6, characterized in that In the flowspec routes corresponding to different decompression ends, the compression operation matching rules are the same; In the flowspec routes corresponding to different decompression ends, the redirection operation matching rules are the same; The redirection strategy includes an interface to which the redirection is directed; different redirection strategies redirect to different interfaces.

9. The method according to claim 6, characterized in that The method of compressing a message matching the flowspec route based on the flowspec route corresponding to the main decompression end to obtain a compressed message includes: If the message matches the compression operation matching rule in the flowspec route corresponding to the primary decompression end, the message is compressed to obtain a compressed message; The redirecting of the compressed message to the interface between the compression end and the main decompression end to forward the compressed message to the main decompression end for decompression includes: if the compressed message matches the redirection operation matching rule in the flowspec route corresponding to the main decompression end, then based on the redirection policy in the flowspec route corresponding to the main decompression end, redirecting the compressed message to the interface between the compression end and the main decompression end to send the compressed message to the main decompression end.

10. A decompression backup implementation method, characterized in that: The method is applied to a PE in a data center, and the PE is designated as one of the decompression ends of the adapted compression end. The method comprises: When the decompression end is selected by the compression end as the main decompression end, If the decompression capability of the decompression end is normal, the message redirected by the compression end is received and decompressed; the compression end compresses the message matching the flowspec policy based on the flowspec policy corresponding to the main decompression end and redirects it to the main decompression end; If the decompression capability of the current decompression end is abnormal, the compression end is notified so that when the decompression capability of the primary decompression end is abnormal, the compression end compresses the message matching the flowspec policy based on the flowspec policy corresponding to the backup decompression end and redirects it to the interface between the compression end and the backup decompression end to forward it to the backup decompression end for decompression.

11. The method according to claim 10, characterized in that The method further comprises: A flow specification flowspec policy is sent to the compression end; the flowspec policy is used to instruct the compression end to compress the message matching the flowspec policy and redirect it to the decompression end for decompression.

12. A decompression backup implementation device, characterized in that: The device is applied to a PE designated as a compression end in a data center, and includes: A receiving unit, used for receiving a message; a processing unit, configured to, when the decompression capability of the main decompression end adapted to the compression end is normal, compress the message matching the flowspec policy based on the flow specification flowspec policy corresponding to the main decompression end to obtain a compressed message, redirect the compressed message to the interface between the compression end and the main decompression end to forward the compressed message to the main decompression end for decompression; and When the decompression capability of the main decompression end is abnormal, based on the flowspec policy corresponding to one of the backup decompression ends of the main decompression end, the message matching the flowspec policy is compressed to obtain a compressed message, and the compressed message is redirected to the interface between the compression end and the backup decompression end to forward the compressed message to the backup decompression end for decompression.

13. A decompression backup implementation device, characterized in that: The device is applied to a PE in a data center, and the PE is designated as one of the decompression ends of the adaptation compression end. The device includes: The decompression unit is used for, when the decompression end is selected by the compression end as the main decompression end, If the decompression capability of the decompression end is normal, the message redirected by the compression end is received and decompressed; the compression end compresses the message matching the flowspec policy based on the flowspec policy corresponding to the main decompression end and redirects it to the main decompression end; A notification unit is used to notify the compression end when the decompression capability of the decompression end is abnormal when the decompression capability of the decompression end is selected as the main decompression end by the compression end, so that the compression end can compress the message matching the flowspec policy based on the flowspec policy corresponding to the backup decompression end and redirect it to the interface between the compression end and the backup decompression end so as to forward it to the backup decompression end for decompression.

14. An electronic device, characterized in that: The electronic device includes: a processor and a machine-readable storage medium; The machine-readable storage medium stores computer instructions, and when the computer instructions are executed by a processor, the steps in any one of the methods of claims 1 to 11 are implemented.

Images