Communication method and device of multi-link network redundancy communication protocol

Abstract

The invention discloses a communication method and device of a multi-link network redundant communication protocol, the method comprises a protocol construction step and a communication step based on the protocol, and the technical problem that the reliability and availability of network communication are difficult to guarantee when a physical link fails in the prior art can be solved.

Description

Technical Field

[0001] The present invention relates to the field of network technology, and in particular to a communication method and device for a multi-link network redundant communication protocol. Background Art

[0002] Network communication reliability and availability involve multiple levels and aspects. For example, when a physical link fails, the reliability of network data communication will be affected, resulting in problems such as packet loss and delayed switching.

[0003] With respect to the technical problem in the above-mentioned related technologies that when a physical link fails, the reliability and availability of network communications are difficult to ensure, no effective solution has been proposed so far. Summary of the invention

[0004] The purpose of the present invention is to overcome the above technical deficiencies and provide a communication method and device for a multi-link network redundant communication protocol to solve the technical problem in the related art that when a physical link fails, the reliability and availability of network communication are difficult to ensure.

[0005] In order to achieve the above technical objectives, the present invention adopts the following technical solutions:

[0006] According to one aspect of the present invention, a communication method of a multi-link network redundant communication protocol is provided, comprising a protocol construction step and a communication step based on the protocol, wherein the protocol construction step comprises:

[0007] A redundant communication protocol layer is added between the network layer and the transport layer. The protocol format of the redundant communication protocol layer includes:

[0008] A signature code used to identify redundant communication protocols;

[0009] Version number, used to define the protocol version;

[0010] The protocol header length is used to define the total length of the redundant communication protocol layer header;

[0011] Link number, used to identify the numbers of both ends of the communication;

[0012] Data packet number, used to store the number of the communication data packet;

[0013] Data packet length, used to store the length of the data area above this protocol layer;

[0014] Message type, used to indicate handshake message, data message or end message;

[0015] Option area, used to expand options;

[0016] CRC checksum, used to check the content area of ​​this protocol header;

[0017] The communication step includes a handshake process, the handshake process includes dynamic negotiation, and the dynamic negotiation includes:

[0018] The initiator of the communication randomly generates a set of values, which are all available to the initiator of the redundant communication;

[0019] After receiving the value, the receiver compares it with the list of redundant communication numbers that are already in use, selects a number that is not used by itself from the group of values, and then returns it to the initiator;

[0020] After the initiator receives the number, the subsequent redundant communication with the receiver uses the number and then sends a data packet, which is the verification packet;

[0021] After the receiver receives the verification package and confirms that it is correct, it also returns the content of the verification package.

[0022] Optionally, the handshake process further includes static configuration, and the static configuration includes:

[0023] Select a code that is not used by both parties on the sending and receiving sides, configure it in the configuration files of both parties, and configure the corresponding relationship between the IP addresses of both parties;

[0024] The sender and receiver are each configured with a random value for verification.

[0025] Optionally, the communication step further includes a data sending process and a data receiving process, and the data sending process and the data receiving process specifically include:

[0026] After the data packet at the data transmission layer is packaged, before it is passed down to the network layer, the corresponding protocol field is filled in according to the redundant communication protocol. After the redundant communication protocol layer header area is constructed, it is handed over to the network layer for further processing, and the maintained data packet number increases accordingly;

[0027] When data is submitted from the network layer to the transport layer, if it is judged to be a redundant protocol, the redundant protocol header area is first parsed to extract the corresponding data packet number to confirm whether it has been processed. If it has been processed, it can be discarded directly. If it has not been processed, the header area is removed, and the subsequent transport layer data is submitted to the transport layer for processing, and the processed data packet number is updated.

[0028] Optionally, the communication step also includes an ending process, and the ending process includes: the sending end sends an ending message data packet with a redundant protocol header, indicating the end of redundant communication between the sending and receiving ends.

[0029] According to another aspect of the present invention, there is provided a communication device for a multi-link network redundant communication protocol, comprising:

[0030] The method comprises a protocol construction unit and a communication unit based on the protocol, wherein the protocol construction unit is used to:

[0031] A redundant communication protocol layer is added between the network layer and the transport layer. The protocol format of the redundant communication protocol layer includes:

[0032] A signature code used to identify redundant communication protocols;

[0033] Version number, used to define the protocol version;

[0034] The protocol header length is used to define the total length of the redundant communication protocol layer header;

[0035] Link number, used to identify the numbers of both ends of the communication;

[0036] Data packet number, used to store the number of the communication data packet;

[0037] Data packet length, used to store the length of the data area above this protocol layer;

[0038] Message type, used to indicate handshake message, data message or end message;

[0039] Option area, used to expand options;

[0040] CRC checksum, used to check the content area of ​​this protocol header;

[0041] The communication unit is used for a handshake process, wherein the handshake process includes dynamic negotiation, and the dynamic negotiation includes:

[0042] The initiator of the communication randomly generates a set of values, which are all available to the initiator of the redundant communication;

[0043] After receiving the value, the receiver compares it with the list of redundant communication numbers that are already in use, selects a number that is not used by itself from the group of values, and then returns it to the initiator;

[0044] After the initiator receives the number, the subsequent redundant communication with the receiver uses the number and then sends a data packet, which is the verification packet;

[0045] After the receiver receives the verification package and confirms that it is correct, it also returns the content of the verification package.

[0046] Optionally, the handshake process further includes static configuration, and the static configuration includes:

[0047] Select a code that is not used by both parties on the sending and receiving sides, configure it in the configuration files of both parties, and configure the corresponding relationship between the IP addresses of both parties;

[0048] The sender and receiver are each configured with a random value for verification.

[0049] Optionally, the communication unit is also used for a data sending process and a data receiving process, and the data sending process and the data receiving process specifically include:

[0050] After the data packet at the data transmission layer is packaged, before it is passed down to the network layer, the corresponding protocol field is filled in according to the redundant communication protocol. After the redundant communication protocol layer header area is constructed, it is handed over to the network layer for further processing, and the maintained data packet number increases accordingly;

[0051] When data is submitted from the network layer to the transport layer, if it is judged to be a redundant protocol, the redundant protocol header area is first parsed to extract the corresponding data packet number to confirm whether it has been processed. If it has been processed, it can be discarded directly. If it has not been processed, the header area is removed, and the subsequent transport layer data is submitted to the transport layer for processing, and the processed data packet number is updated.

[0052] Optionally, the communication unit is also used for an ending process, and the ending process includes: the sending end sends an ending message data packet with a redundant protocol header, indicating the end of redundant communication between the sending and receiving ends.

[0053] According to another aspect of the present invention, there is also provided an electronic device, comprising: a processor and a memory;

[0054] The memory stores a computer-readable program executable by the processor;

[0055] When the processor executes the computer-readable program, the steps in the above method are implemented.

[0056] According to another aspect of the present invention, a computer-readable storage medium is provided, which stores one or more programs. The one or more programs can be executed by one or more processors to implement the steps in the above method.

[0057] The present invention provides a communication method and device for a multi-link network redundant communication protocol. Based on the IP protocol, a redundant communication protocol layer is added between the IP and TCP / UDP layers. The reliability of network data communication in a multi-link environment is ensured through the protocol design and definition of the redundant communication protocol layer. When any physical link fails, as long as one link is ensured to be normal, the availability of network communication can be guaranteed, and zero packet loss and zero delay switching can be achieved. The technical problem that the reliability and availability of network communication are difficult to ensure when a physical link fails in the related technology can be solved. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Figure 1A flow chart of a communication method of a multi-link network redundant communication protocol provided by an embodiment of the present invention;

[0059] Figure 2 A schematic diagram of the structure of a communication device for a multi-link network redundant communication protocol is provided for an embodiment of the present invention;

[0060] Figure 3 It is a structural block diagram of a terminal that can implement the communication method of the multi-link network redundant communication protocol of the embodiment of the present invention;

[0061] Figure 4 It is a format diagram of redundant communication protocol;

[0062] Figure 5 A system architecture diagram of a communication method for a multi-link network redundant communication protocol provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0063] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0064] In the related art, when a physical link fails, the reliability and availability of network communication are difficult to ensure. Currently, there is no better solution.

[0065] Based on the above problems, the present invention proposes a communication method and device for a multi-link network redundant communication protocol to solve the above technical problems in the related art.

[0066] Combination Figure 1 , 4 5. A communication method of a multi-link network redundant communication protocol provided by an embodiment of the present invention includes a protocol construction step S101 and a communication step S103. Specifically:

[0067] In step S101, for a system architecture including an application layer, a transport layer, a network layer and a data link layer, a redundant communication protocol layer is added between the transport layer and the network layer.

[0068] As an example, the redundant communication protocol layer protocol format is defined as follows.

[0069] (0) Feature code, 2 bytes in length, with a fixed content of 0x1912, used to identify redundant protocols.

[0070] (1) Version number, 4 bits in length, in low byte order, used to define the protocol version, currently 1.

[0071] (2) Protocol header length: 12 bits in length, in low byte order, used to define the total length of the redundant communication protocol layer header.

[0072] (3) Link number, 16 bits in length, which can be negotiated by both ends of the communication or statically configured. It is a unique number used to identify both ends of the communication.

[0073] (4) Data packet number, 32 bits in length, in low byte order, storing the data packet number of the communication. The number starts from 1 and starts from 0 after exceeding the maximum length.

[0074] (5) Data packet length, 24 bits in length, in low byte order, storing the length of the data area above this protocol layer, in bytes.

[0075] (6) Message type, length 1 byte, 1 represents a handshake message, 2 represents a data message, and 3 represents an end message.

[0076] (7) Option area, the length becomes longer, used to expand options, the length of the option area is the length of the protocol header minus 17. If the length of the protocol header is 17, it means that the option area is not included, and the longest option area length is 16384-17=16367.

[0077] (8) CRC checksum, 4 bytes in length, is used to check the content area of ​​this protocol header. The CRC algorithm is used and this area is 0 during calculation.

[0078] In step S103, the communication process is as follows:

[0079] Step S1031, handshake process:

[0080] The two parties using redundant communication must first have at least two communication links, such as two independent networks, which can complete communication independently. There are two types of redundant communication methods for link number usage: dynamic negotiation at both ends and static configuration. In the case of dynamic negotiation, the two parties need to negotiate based on the existing communication link. The negotiation process is as follows: (a) The initiator of the communication randomly generates a group of (64) 16-bit values, which are all available to the initiator of redundant communication. (b) After receiving the numbers, the receiver compares the list of redundant communication numbers in use, selects a number that is not used by itself from the group, and then returns it to the initiator. (c) After the initiator receives the number, the subsequent redundant communication to the receiver uses the number. Then a data packet is sent, which is a check packet. The check packet contains a 32-byte random value + CRC32 check code. (d) After the receiver receives the check packet and confirms that the check value is correct, it also returns the random value + CRC32 check code. (e) The dynamic negotiation of link coding is completed.

[0081] The steps for static configuration are as follows: (1) Select a code that is not used by both parties on the sender and receiver, configure it in the configuration files of both parties, and configure the corresponding relationship between the IP addresses of both parties. (2) The sender and receiver are respectively configured with a 32-byte random value for verification.

[0082] Step S1033, data sending process:

[0083] After the data packet is packaged in the data transmission layer, before it is passed down to the IP layer, the corresponding protocol field is filled in according to the redundant communication protocol, and after the redundant communication protocol layer header area is constructed, it is handed over to the IP layer for further processing. The maintained data packet number increases accordingly.

[0084] Step S1035, data receiving process:

[0085] When data is submitted from the IP layer to the transport layer, if it is judged to be a redundant protocol, the redundant protocol header area is first parsed to extract the corresponding data packet number to confirm whether it has been processed. If it has been processed, it can be discarded directly. If it has not been processed, the header area is removed, and the subsequent transport layer data is submitted to the transport layer for processing, and the processed data packet number is updated.

[0086] Step S1037, end the process:

[0087] The sender sends an end message data packet with a redundant protocol header, indicating the end of redundant communication between the sender and the receiver.

[0088] The redundant communication protocol designed in the present invention does not affect the existing network communication. While performing redundant communication, non-redundant communication can also be performed. It is compatible with existing network equipment and can support redundant communication of two or more physical links.

[0089] According to an embodiment of the present invention, a communication device of a multi-link network redundant communication protocol is provided, Figure 2 , the device comprises:

[0090] The protocol construction unit 21 and the communication unit 23. The protocol construction unit 21 is used to execute step S101 and its sub-steps described in the above embodiment, and the communication unit 23 is used to execute step S103 and its sub-steps described in the above embodiment.

[0091] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment will not be described in detail here.

[0092] It should be noted that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiments. It should be noted that the above modules, as part of the device, can be run in a corresponding hardware environment, can be implemented by software, and can also be implemented by hardware, wherein the hardware environment includes a network environment.

[0093] Figure 3 is a structural block diagram of a terminal according to an embodiment of the present application, such as Figure 3 As shown, the terminal may include: one or more (only one is shown) processors 101, a memory 103, and a transmission device 105, such as Figure 3 As shown, the terminal may also include an input and output device 107 .

[0094] Among them, the memory 103 can be used to store software programs and modules, such as program instructions / modules corresponding to the methods and devices in the embodiments of the present application. The processor 101 executes various functional applications and data processing by running the software programs and modules stored in the memory 103, that is, implementing the above-mentioned method. The memory 103 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 103 may further include a memory remotely arranged relative to the processor 101, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0095] The transmission device 105 is used to receive or send data via a network, and can also be used for data transmission between a processor and a memory. Specific examples of the above-mentioned network may include a wired network and a wireless network. In one example, the transmission device 105 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices and routers via a network cable so as to communicate with the Internet or a local area network. In one example, the transmission device 105 is a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0096] Specifically, the memory 103 is used to store application programs.

[0097] The processor 101 may call the application program stored in the memory 103 through the transmission device 105 to execute the method of the above embodiment.

[0098] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment will not be described in detail here.

[0099] Those skilled in the art will appreciate that the above terminal structures are for illustration only, and the terminals may be smart phones (such as Android phones, iOS phones, etc.), tablet computers, PDAs, mobile Internet devices (MID), PADs, and other terminal devices. Figure 3 It does not limit the structure of the above electronic device. For example, the terminal may also include Figure 3 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Figure 3 Different configurations shown.

[0100] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0101] The embodiment of the present application further provides a storage medium. Optionally, in this embodiment, the storage medium can be used to execute the program code of the above method.

[0102] Optionally, in this embodiment, the storage medium may be located on at least one network device among a plurality of network devices in the network shown in the above embodiment.

[0103] Optionally, in this embodiment, the storage medium is configured to store program codes for executing the above method.

[0104] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment will not be described in detail here.

[0105] Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store program codes.

[0106] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0107] If the integrated units in the above embodiments are implemented in the form of software functional units and sold or used as independent products, they can be stored in the above computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling one or more computer devices (which may be personal computers, servers, or network devices, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.

[0108] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0109] In several embodiments provided in this application, the device embodiments described are only schematic, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, for example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection of units or modules, which may be electrical or other forms.

[0110] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0111] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0112] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A communication method for a multi-link network redundant communication protocol, characterized in that: The method comprises a protocol construction step and a communication step based on the protocol, wherein the protocol construction step comprises: A redundant communication protocol layer is added between the network layer and the transport layer. The protocol format of the redundant communication protocol layer includes: A signature code used to identify redundant communication protocols; Version number, used to define the protocol version; The protocol header length is used to define the total length of the redundant communication protocol layer header; Link number, used to identify the numbers of both ends of the communication; Data packet number, used to store the number of the communication data packet; Data packet length, used to store the length of the data area above this protocol layer; Message type, used to indicate handshake message, data message or end message; Option area, used to expand options; CRC checksum, used to check the content area of ​​this protocol header; The communication step includes a handshake process, the handshake process includes dynamic negotiation, and the dynamic negotiation includes: The initiator of the communication randomly generates a set of values, which are all available to the initiator of the redundant communication; After receiving the value, the receiver compares it with the list of redundant communication numbers that are already in use, selects a number that is not used by itself from the group of values, and then returns it to the initiator; After the initiator receives the number, the subsequent redundant communication with the receiver uses the number and then sends a data packet, which is the verification packet; After the receiver receives the verification package and confirms that it is correct, it also returns the content of the verification package.

2. The communication method of the multi-link network redundant communication protocol according to claim 1, characterized in that: The handshake process also includes static configuration, and the static configuration includes: Select a code that is not used by both parties on the sending and receiving sides, configure it in the configuration files of both parties, and configure the corresponding relationship between the IP addresses of both parties; The sender and receiver are each configured with a random value for verification.

3. The communication method of the multi-link network redundant communication protocol according to claim 1, characterized in that: The communication step also includes a data sending process and a data receiving process, and the data sending process and the data receiving process specifically include: After the data packet at the data transmission layer is packaged, before it is passed down to the network layer, the corresponding protocol field is filled in according to the redundant communication protocol. After the redundant communication protocol layer header area is constructed, it is handed over to the network layer for further processing, and the maintained data packet number increases accordingly; When data is submitted from the network layer to the transport layer, if it is judged to be a redundant protocol, the redundant protocol header area is first parsed to extract the corresponding data packet number to confirm whether it has been processed. If it has been processed, it can be discarded directly. If it has not been processed, the header area is removed, and the subsequent transport layer data is submitted to the transport layer for processing, and the processed data packet number is updated.

4. The communication method of the multi-link network redundant communication protocol according to claim 1, characterized in that: The communication step also includes an ending process, and the ending process includes: the sending end sends an ending message data packet with a redundant protocol header, indicating the end of redundant communication between the sending and receiving ends.

5. A communication device for a multi-link network redundant communication protocol, characterized in that: include: The method comprises a protocol construction unit and a communication unit based on the protocol, wherein the protocol construction unit is used to: A redundant communication protocol layer is added between the network layer and the transport layer. The protocol format of the redundant communication protocol layer includes: A signature code used to identify redundant communication protocols; Version number, used to define the protocol version; The protocol header length is used to define the total length of the redundant communication protocol layer header; Link number, used to identify the numbers of both ends of the communication; Data packet number, used to store the number of the communication data packet; Data packet length, used to store the length of the data area above this protocol layer; Message type, used to indicate handshake message, data message or end message; Option area, used to expand options; CRC checksum, used to check the content area of ​​this protocol header; The communication unit is used for a handshake process, wherein the handshake process includes dynamic negotiation, and the dynamic negotiation includes: The initiator of the communication randomly generates a set of values, which are all available to the initiator of the redundant communication; After receiving the value, the receiver compares it with the list of redundant communication numbers that are already in use, selects a number that is not used by itself from the group of values, and then returns it to the initiator; After the initiator receives the number, the subsequent redundant communication with the receiver uses the number and then sends a data packet, which is the verification packet; After the receiver receives the verification package and confirms that it is correct, it also returns the content of the verification package.

6. The communication device of the multi-link network redundant communication protocol according to claim 5, characterized in that: The handshake process also includes static configuration, and the static configuration includes: Select a code that is not used by both parties on the sending and receiving sides, configure it in the configuration files of both parties, and configure the corresponding relationship between the IP addresses of both parties; The sender and receiver are each configured with a random value for verification.

7. The communication device of the multi-link network redundant communication protocol according to claim 5, characterized in that: The communication unit is also used for data sending process and data receiving process, and the data sending process and data receiving process specifically include: After the data packet at the data transmission layer is packaged, before it is passed down to the network layer, the corresponding protocol field is filled in according to the redundant communication protocol. After the redundant communication protocol layer header area is constructed, it is handed over to the network layer for further processing, and the maintained data packet number increases accordingly; When data is submitted from the network layer to the transport layer, if it is judged to be a redundant protocol, the redundant protocol header area is first parsed to extract the corresponding data packet number to confirm whether it has been processed. If it has been processed, it can be discarded directly. If it has not been processed, the header area is removed, and the subsequent transport layer data is submitted to the transport layer for processing, and the processed data packet number is updated.

8. The communication device of the multi-link network redundant communication protocol according to claim 6, characterized in that: The communication unit is also used for an ending process, which includes: the sending end sends an ending message data packet with a redundant protocol header, indicating the end of redundant communication between the sending and receiving ends.

9. An electronic device, characterized in that: include: Processor and memory; The memory stores a computer-readable program executable by the processor; When the processor executes the computer-readable program, the steps in the method according to any one of claims 1 to 4 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps in the method according to any one of claims 1 to 4.

Images