WO2023221968A1

WO2023221968A1 - Message transmission method, and network device and communication system

Info

Publication number: WO2023221968A1
Application number: PCT/CN2023/094468
Authority: WO
Inventors: 戈军; 王海波; 王丽丽; 许福太
Original assignee: 华为技术有限公司
Priority date: 2022-05-17
Filing date: 2023-05-16
Publication date: 2023-11-23
Also published as: CN117118912A

Abstract

Disclosed in the embodiments of the present application are a message transmission method and a network device, which are used for transmitting a keep-alive message by means of a first stream carried by a first transmission layer protocol, and for transmitting a first routing protocol update message by means of a second stream carried by a second transmission layer protocol, wherein the priority of a network device receiving and transmitting the keep-alive message is higher than the priority of the network device receiving and transmitting the first routing protocol update message. Therefore, the interruption of a BGP service, which results from a failure to process a keep-alive message in a timely manner due to a network device receiving and transmitting a routing protocol update message, may be reduced.

Description

Message transmission method, network equipment and communication system

This application requests the priority of the Chinese patent application submitted to the China Patent Office on May 17, 2022, with the application number 202210540416.7 and the invention title "A method, equipment and system for solving massive neighbors using BGP Over Quic technology", and , the priority of a Chinese patent application submitted to the State Intellectual Property Office of China on August 17, 2022, with application number 202210988619.2 and the invention name "Message transmission method, network equipment and communication system", the entire content of which is incorporated by reference in in this application.

Technical field

The present application relates to the field of communication technology, and in particular, to a message transmission method, network equipment and communication system.

Background technique

Border gateway protocol (BGP) is a routing protocol that implements route exchange within or between autonomous systems (AS). Two network devices that exchange BGP messages are called BGP peers or BGP neighbors.

A route reflector (RR) based on the BGP protocol can connect multiple BGP devices (i.e. neighbors). BGP protocol messages include keep alive (KA) messages used to maintain BGP connections and BGP update (Update) messages. Various BGP protocol messages are based on first input first output (FIFO). Queued for sending.

Due to the large number of various BGP protocol messages transmitted through the RR, if the keep-alive messages are not transmitted in time, the BGP connection between the RR and the neighbor will be disconnected, causing BGP service interruption. Furthermore, since two network devices need to be reconnected after being disconnected, the network devices are constantly disconnected and reconnected, which will cause BGP route flapping.

Contents of the invention

This application provides a message transmission method that transmits keep-alive messages through the first stream carried by the higher-priority first transport layer protocol, which reduces BGP connection disconnections caused by untimely sending and receiving of keep-alive messages, and can improve Stability of BGP services and reduction of route flapping.

The first aspect of the present application provides a message transmission method, including: a first network device sends a first keep-alive message to a second network device through a first flow carried by a first transport layer protocol; the first network device A first routing protocol update message is sent to the second network device through the second flow carried by the second transport layer protocol, and the first keepalive message and the first routing protocol update message both correspond to the first route session, the priority of the first network device sending the first keepalive message through the first flow is higher than the priority of the first network device sending the first routing protocol update message through the second flow. priority. It should be noted that the first transport layer protocol and the second transport layer protocol may or may not be the same.

This application provides a message transmission method, because the first network device sends the first keepalive message and the first routing protocol corresponding to the same routing session to the second network device respectively through two streams carried by the transport layer protocol. Update message, and the keep-alive message sent through the first flow carried by the first transport layer protocol has a higher priority. Therefore, it is guaranteed that the first keep-alive message and the first routing protocol update message exist in the same routing session. When the first keep-alive message is sent first, the first keep-alive message is sent first, thereby reducing the BGP service interruption caused by the failure of the first keep-alive message to be sent on time due to the first network device sending the first routing protocol update message, and reducing the continuous disconnection between neighbors. and route flapping caused by reconnection.

In a possible implementation of the first aspect, the first network device sends the first keepalive message through the first flow with a higher priority than all routing protocol update messages sent by the first network device. priority of the document.

The first network device can establish a connection with a plurality of second network devices. The connection between the first network device and each second network device is The established connections can be maintained through keep-alive messages respectively. In the message transmission method provided by this application, the priority of the first keep-alive message sent by the first network device is higher than the priority of all routing protocol update messages, and also That is to say, when multiple second network devices need to send and receive routing protocol update messages due to route changes, the first network device sends the first keep-alive message with the highest priority, and will not cause problems due to sending multiple routing protocol update messages. BGP service interruption caused by the failure of the first keep-alive message to be sent on time reduces route flapping caused by continuous disconnection and reconnection between neighbors.

In a possible implementation of the first aspect, the first transport layer protocol includes the Fast User Datagram Protocol Internet Connection QUIC protocol, the second transport layer protocol includes the QUIC protocol, and the first flow identifier of the first flow The second stream identifier is different from the second stream identifier.

In a possible implementation of the message transmission method provided by this application, the first network device sends a first keep-alive message based on the first flow carried by the QUIC protocol, and sends the first route based on the second flow carried by the QUIC protocol. The protocol update message makes the solution applicable to BGP scenarios carried on the QUIC protocol.

In a possible implementation of the first aspect, the first transport layer protocol includes muilti-TCP or user datagram protocol UDP, and the second transport layer protocol includes muilti-TCP or UDP, so The first destination port number of the first flow is different from the second destination port number of the second flow.

In a possible implementation of the message transmission method provided by this application, the first transport layer protocol carrying the first flow is the muilti-TCP protocol, and the second transport layer protocol carrying the second flow is the muilti-TCP protocol; in In another possible implementation, the first transport layer protocol carrying the first stream and the second transport layer protocol carrying the second stream are UDP protocols; in another possible implementation, the first transport layer carrying the first stream The first layer protocol is the TCP protocol, and the second transport layer protocol carrying the second stream is the UDP protocol; in another possible implementation, the first transport layer protocol carrying the first stream is the UDP protocol, and the second transport layer protocol carrying the second stream is the UDP protocol. The transport layer protocol is TCP protocol. In practical applications, the transport layer protocol corresponding to the solution can be flexibly selected based on needs, so that the method of this application can be applied to BGP scenarios carried on TCP protocol, BGP scenarios carried on UDP protocol, or BGP scenarios carried on mixed transmission of TCP and UDP. middle.

In a possible implementation manner of the first aspect, the first routing protocol update message includes a BGP update message.

In a possible implementation of the first aspect, the first keep-alive message and the first routing protocol update message correspond to the same routing session, including: the first keep-alive message and the first routing protocol update message. The first BGP update protocol message corresponds to the same BGP session.

In a possible implementation of the first aspect, the first network device includes a backup board; the first network device backs up the first routing protocol update message in the backup board; the first network device backs up the first routing protocol update message in the backup board; The network device does not back up the first keep-alive message in the backup board.

The message transmission method provided by this application, in the scenario where the same network device has a main board and a backup board, the first network device does not back up the keep-alive messages in the backup board, which can reduce the waste of network device processing resources and improve the processing capability of the network device. .

In a possible implementation manner of the first aspect, the first network device creates a keep-alive channel after the active/standby switchover, and the keep-alive channel is used to transmit the first keep-alive message.

In the message transmission method provided by this application, the first network device has a main board and a backup board. After the main board and the backup board are switched, the routing protocol update message can be transmitted based on the original channel, and the first network device will be created to transmit the first keep-alive message. For the keep-alive channel, the first keep-alive message is sent first.

A second aspect of the present application provides a message transmission method, including: a second network device receiving a first keep-alive message sent by a first network device through a first stream carried by a first transport layer protocol; the second network device The device communicates through the second transport layer The second flow carried by the protocol receives the first routing protocol update message sent by the first network device, and the first keep-alive message and the first routing protocol update message both correspond to the first routing session, so The priority of the second network device in processing the first keep-alive message received through the first flow is higher than the priority of the second network device in processing the first routing protocol update message.

This application provides a message transmission method. The second network device receives the first keep-alive message and the first routing protocol sent by the first network device corresponding to the same routing session through two streams carried by the transport layer protocol. update message, and the priority of processing the keep-alive message received through the first flow is higher. Therefore, it can be guaranteed that when the first keep-alive message and the first routing protocol update message exist in the same routing session, the first one will be processed first. keep-alive messages, thereby reducing BGP service interruption caused by the failure of the first keep-alive message to be received on time due to the second network device processing routing protocol update messages, and reducing route flapping caused by continuous disconnection and reconnection between neighbors.

In a possible implementation of the second aspect, the second network device processes the first keepalive message received through the first flow with a higher priority than the second network device through the third stream. The priority of the routing protocol update message received by the second stream.

The second network device can establish connections with multiple first network devices, and the connections established by the second network device and each first network device can be maintained through keep-alive messages respectively. In the message transmission method provided by this application, The priority of the second network device receiving and processing the first keepalive message is higher than the priority of all routing protocol update messages. That is to say, when multiple first network devices send routing protocols to the second network device due to route changes, When updating the message, the second network device has the highest priority in processing the first keep-alive message. It will not interrupt the BGP service due to the failure of the first keep-alive message to be sent on time due to receiving multiple routing protocol update messages, and reduce the BGP service interruption caused by the failure to send the first keep-alive message on time. Route flapping caused by constant disconnection and reconnection between neighbors.

In a possible implementation of the second aspect, the first transport layer protocol includes the Fast User Datagram Protocol Internet Connection QUIC protocol, the second transport layer protocol includes the QUIC protocol, and the first flow identifier of the first flow The second stream identifier is different from the second stream identifier.

This application provides a message transmission method. In a possible implementation manner, the second network device receives the first keep-alive message based on the first flow under the QUIC protocol, and receives the third keep-alive message based on the second flow under the QUIC protocol. A routing protocol update message makes the solution applicable to BGP scenarios carried on the QUIC protocol.

In a possible implementation of the second aspect, the first transport layer protocol includes muilti-TCP or user datagram protocol UDP, and the second transport layer protocol includes muilti-TCP or UDP, so The first destination port number of the first flow is different from the second destination port number of the second flow.

In a possible implementation of a message transmission method provided by this application, the first transport layer protocol carrying the first flow is the muilti-TCP protocol, and the second transport layer protocol carrying the second flow is the muilti-TCP protocol. ; In another possible implementation, the first transport layer protocol carrying the first stream and the second transport layer protocol carrying the second stream are UDP protocols; in another possible implementation, the third transport layer protocol carrying the first stream The first transport layer protocol is the TCP protocol, and the second transport layer protocol carrying the second stream is the UDP protocol. In practical applications, the transport layer protocol corresponding to the specific implementation method of the solution can be flexibly selected based on needs, so that the method of this application can be applied to BGP scenarios carried on the TCP protocol, BGP scenarios carried on the UDP protocol, or carried on mixed transmission of TCP and UDP. In the BGP scenario.

In a possible implementation of the second aspect, the first routing protocol update message includes a BGP update message.

In a possible implementation manner of the second aspect, the first keep-alive message and the first BGP update protocol message correspond to the same BGP session.

In the message transmission method provided by this application, the second network device sends messages based on the BGP protocol. The first keep-alive message and the first BGP update protocol message both correspond to the same BGP session. The BGP session passes the first keep-alive message. The message is maintained.

In a possible implementation of the second aspect, the second network device includes a backup board; the second network device backs up the first routing protocol update message in the backup board; the second The network device does not back up the first keep-alive message in the backup board.

The message transmission method provided by this application can reduce the waste of network device processing resources and improve the processing capabilities of network devices in a scenario where the same network device has a main board and a backup board. The second network device does not back up the keep-alive messages on the backup board.

In a possible implementation manner of the second aspect, the second network device creates a keep-alive channel after the active/standby switchover, and the keep-alive channel is used to transmit the first keep-alive message.

In the message transmission method provided by this application, the second network device has a main board and a backup board. After the main board and the backup board are switched, the routing protocol update message can be transmitted based on the original channel, and the second network device will be created to transmit the first keep-alive message. The keep-alive channel gives priority to the first keep-alive message.

A third aspect of the present application provides a first network device, including: a transceiver module, configured to send a first keep-alive message to a second network device through a first flow carried by a first transport layer protocol; the transceiver module further For sending a first routing protocol update message to the second network device through the second flow carried by the second transport layer protocol, where the first keep-alive message and the first routing protocol update message both correspond to the first routing protocol update message. A routing session, the first network device sending the first keepalive message through the first flow has a higher priority than the first network device sending the first routing protocol update message through the second flow. priority of the document.

In a possible implementation manner of the third aspect, the priority of the first network device sending the first keep-alive message through the first flow is higher than that of the first network device sending the first keep-alive message through the second flow. The priority for sending routing protocol update messages.

In a possible implementation of the third aspect, the first transport layer protocol includes the Fast User Datagram Protocol Internet Connection QUIC protocol, the second transport layer protocol includes the QUIC protocol, and the first flow identifier of the first flow The second stream identifier is different from the second stream identifier.

In a possible implementation of the third aspect, the first transport layer protocol includes muilti-TCP or user datagram protocol UDP, and the second transport layer protocol includes muilti-TCP or UDP, so The first destination port number of the first flow is different from the second destination port number of the second flow.

In a possible implementation manner of the third aspect, the first routing protocol update message includes a BGP update message.

In a possible implementation manner of the third aspect, the first keep-alive message and the first BGP update protocol message correspond to the same BGP session.

In a possible implementation of the third aspect, the first network device includes a backup board; the first network device further includes: a backup module for backing up the first routing protocol in the backup board Update message; the backup module is also configured for the first network device not to back up the first keep-alive message in the backup board.

In a possible implementation of the third aspect, the first network device further includes: a processing module configured to create a keep-alive channel after the active/standby switchover, and the keep-alive channel is used to transmit the first Keep alive message.

A fourth aspect of the present application provides a second network device, including: a transceiver module configured to receive a first keep-alive message sent by the first network device through a first stream carried by the first transport layer protocol; the transceiver module , further configured to receive the first routing protocol update message sent by the first network device through the second stream carried by the second transport layer protocol, the first keep-alive message and the first routing protocol update message are corresponding to the first routing session, the second network device processes the The priority of the first keep-alive message received by the first flow is higher than the priority of the second network device processing the first routing protocol update message.

In a possible implementation of the fourth aspect, the second network device processes the first keepalive message received through the first flow with a higher priority than the second network device through the third stream. The priority of the routing protocol update message received by the second stream.

In a possible implementation of the fourth aspect, the first transport layer protocol includes the Fast User Datagram Protocol Internet Connection QUIC protocol, the second transport layer protocol includes the QUIC protocol, and the first flow identifier of the first flow The second stream identifier is different from the second stream identifier.

In a possible implementation of the fourth aspect, the first transport layer protocol includes muilti-TCP or user datagram protocol UDP, and the second transport layer protocol includes muilti-TCP or UDP, so The first destination port number of the first flow is different from the second destination port number of the second flow.

In a possible implementation of the fourth aspect, the first routing protocol update message includes a BGP update message.

In a possible implementation manner of the fourth aspect, the first keep-alive message and the first BGP update protocol message correspond to the same BGP session.

In a possible implementation of the fourth aspect, the second network device includes a backup board; the second network device further includes: a backup module for backing up the first routing protocol in the backup board Update message; the backup module is also configured not to back up the first keep-alive message in the backup board.

In a possible implementation of the fourth aspect, the first network device further includes: a processing module configured to create a keep-alive channel after the active/standby switchover, the keep-alive channel being used to transmit the first Keep alive message.

The fifth aspect of the present application provides a network device, including: a memory, computer-readable instructions are stored in the memory; and a processor connected to the memory, when the computer-readable instructions are executed by the processor, The network device is caused to implement the method described in any one of the above first aspect, the second aspect, and various possible implementation manners.

A sixth aspect of the present application provides a computer program product, which includes computer-readable instructions. When the computer-readable instructions are run on a computer, the computer is caused to perform the above-mentioned first aspect, second aspect, and various possibilities. The method described in any of the implementation methods.

A seventh aspect of the present application provides a computer-readable storage medium, characterized in that instructions are stored in the computer-readable storage medium, and when the instructions are run on a computer, they cause the computer to execute the above-mentioned first aspect, The method described in any one of the second aspect and various possible implementations.

An eighth aspect of this application provides a chip including a processor. The processor is configured to read and execute the computer program stored in the memory to perform the method described in any one of the above first aspect, the second aspect, and various possible implementations. Optionally, the chip should include a memory, and the memory and the processor are connected to the memory through circuits or wires. Further optionally, the chip also includes a communication interface, and the processor is connected to the communication interface. The communication interface is used to receive data and/or information that needs to be processed. The processor obtains the data and/or information from the communication interface, processes the data and/or information, and outputs the processing results through the communication interface. The communication interface may be an input-output interface.

A ninth aspect of the present application provides a communication system, including a first network device and a second network device, wherein the first network device sends a first flow carried by a first transport layer protocol to the second network device. A keep-alive message; the second network device receives the first keep-alive message through the first stream; the first network device sends the second stream to the second network device through the second stream carried by the second transport layer protocol Send a first routing protocol update message; the second network device passes The second flow receives the first routing protocol update message, the first keep-alive message and the first routing protocol update message both correspond to the first routing session, and the first keep-alive message Both the first routing protocol update message and the first routing protocol update message correspond to the first routing session, and the first network device sends the first keepalive message through the first flow with a higher priority than the first network device sends through the first flow. The second flow sends the first routing protocol update message with a priority, and the second network device processes the first keepalive message received through the first flow with a higher priority than the second The network device processes the priority of the first routing protocol update message.

In a possible implementation of the ninth aspect, the first network device is also configured to perform the method described in any one of the above first aspect and various possible implementations, and the second network device is further For performing the method described in any one of the above second aspect and various possible implementations.

Among them, the technical effects brought about by the second aspect, the third aspect, the fourth aspect, the fifth aspect, the sixth aspect, the seventh aspect, the eighth aspect or the ninth aspect and any of the implementation methods can be found in the first aspect. The technical effects brought about by the corresponding implementation methods in the first aspect and the second aspect will not be described again here.

In the message transmission method provided by this application, the network device transmits the first keep-alive message and the first routing protocol update message respectively through two streams, in which the priority of sending and receiving the first keep-alive message is higher than the first routing protocol update The priority of the message, therefore, can ensure that when the first keep-alive message and the first routing protocol update message exist in the same routing session, the first keep-alive message will be transmitted first, reducing the delay of the first keep-alive message. BGP service interruption caused by sending and receiving can reduce route flapping caused by continuous disconnection, reconnection and disconnection between neighbors.

Description of the drawings

Figure 1 is an application scenario architecture diagram of the message transmission method provided by the embodiment of the present application;

Figure 2 is a schematic diagram of an embodiment of the message transmission method in the embodiment of the present application;

Figure 3a is a schematic diagram of a packet sent by a network device in an embodiment of the present application;

Figure 3b is a schematic diagram of a network device receiving a message in an embodiment of the present application;

Figure 4 is a schematic diagram of another embodiment of the message transmission method in the embodiment of the present application;

Figure 5 is a schematic diagram of packet transmission within a network device in an embodiment of the present application;

Figure 6 is a schematic diagram of the message sending process in the active and standby scenarios in the embodiment of the present application;

Figure 7 is a schematic diagram of the message receiving process in the active and standby scenarios in the embodiment of the present application;

Figure 8 is a schematic diagram of a network device in an embodiment of the present application;

Figure 9 is a schematic diagram of another embodiment of the network device in the embodiment of the present application;

Figure 10 is a schematic diagram of another embodiment of the network device in the embodiment of the present application.

Detailed ways

The embodiment of the present application provides a message transmission method for transmitting keep-alive messages and routing protocol update messages through two streams respectively, and the keep-alive messages are transmitted with priority, thus reducing the delay of keep-alive messages on time. BGP service interruption caused by sending and receiving.

The embodiments of the present application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Persons of ordinary skill in the art know that with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

The terms "first", "second", etc. in the description and claims of this application and the above-mentioned drawings are used to distinguish similar objects and not necessarily used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments described herein can be practiced in sequences other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or modules and need not be limited to those explicitly listed. Those steps or modules may instead include other steps or modules not expressly listed or inherent to the processes, methods, products or devices. The naming or numbering of steps in this application does not mean that the steps in the method flow must be executed in the time/logical sequence indicated by the naming or numbering. The process steps that have been named or numbered can be implemented according to the purpose to be achieved. The order of execution can be changed for technical purposes, as long as the same or similar technical effect can be achieved.

For ease of understanding, some technical terms involved in the embodiments of this application are briefly introduced below:

1. Border gateway protocol (BGP)

BGP is a routing protocol that implements route exchange between network devices within an autonomous system (AS) or between ASs. Two network devices running BGP can call each other neighbors. After establishing a neighbor relationship, they can exchange routing information. Usually, complete information is only exchanged once at startup. Subsequently, only triggered updates are required to notify network changes.

2. BGP messages

BGP defines four message types in order to realize its functions:

(1) Open (OPEN) message

When two BGP neighbors establish a transport layer protocol connection, they each send an open message to declare their respective autonomous system numbers and determine other operating parameters.

When a network device receives an OPEN message from a neighbor, it will send a keep alive (KA) message. Before exchanging routing information between network devices, both parties must send an OPEN message and receive a KEEPALIVE message. The KEEPALIVE message can be used as a confirmation of the OPEN message.

(2)Update (UPDATE) message

After BGP neighbors have established a transport layer protocol connection and successfully received the KEEPALIVE confirmation message for the OPEN message, the BGP neighbors can use UPDATE messages to advertise network reachability information. The content of the announcement can be a new reachable destination network, or it can be an announcement to revoke the reachability of some original destination networks.

(3)Keep alive (KEEP ALIVE) message

Keep-alive messages are used to regularly test network connectivity between two BGP neighbors and confirm that the BGP neighbor device sending the keep-alive messages is working normally. If the transport layer protocol that carries the connection is the TCP protocol, since the TCP protocol itself does not provide an automatic connection status notification mechanism, regular exchange of keep-alive messages between BGP neighbors can enable BGP neighbor devices to detect whether the TCP connection is working properly.

(4) NOTIFICATION message

When a BGP device detects an error (or needs to take control), it can use notification messages to notify its BGP neighbors. Once an error is detected, the BGP device will send a notification message to the BGP neighbor, and then disconnect and terminate the communication.

3. Route reflector (RR)

BGP running between two or more BGP devices in the same autonomous system (AS) is called IBGP (Internal/Interior BGP). BGP running between BGP devices belonging to different ASs is called EBGP (External/Exterior BGP). Within an AS, one network device acts as a route reflector, and other network devices act as clients to establish IBGP connections with the route reflector. Route reflectors pass between network devices (Reflect) routing information, so that there is no need to establish BGP connections between network devices, and only need to establish connections with route reflectors, reducing the number of connections.

4. QUIC (Quick UDP Internet Connection)

It is a low-latency Internet transport layer protocol based on UDP.

5. flow

Within a period of time, a unidirectional flow of packets transmitted between a source IP address and a destination IP address. All packets in the same flow have the same source port number, destination port number, protocol number, and source and destination IP addresses, that is, The contents of the quintuple are the same.

The application scenario architecture of the message transmission method in the embodiment of the present application is introduced below. Please refer to Figure 1, which is an application scenario architecture diagram of the message transmission method in the embodiment of the present application.

The application scenario architecture diagram includes a network device 1 and multiple network devices 2 (including network devices 2a to 2n). Network device 1 and multiple network devices 2 belong to network devices in the same autonomous system. Multiple network devices 2 are respectively connected to network device 1 for communication. Network device 1 is a router or switch. In a typical implementation, , network device 1 serves as a route reflector, hereinafter referred to as a reflector. In a possible implementation, network device 1 and network device 2 communicate through the BGP protocol, and network device 1 and network device 2 are peers or neighbors of each other. In different application scenarios, the network device 2 may be different devices. For example, in a software defined wide area network (SD-WAN), the network device 2 may be the same as the enterprise branch client device ( customer premises equipment (CPE); in the backbone network or metropolitan area network, the network device 2 can be a router, specifically a provider edge equipment (provider edge, PE).

Usually, the BGP protocol is based on the transport layer TCP protocol to send and receive BGP messages. After the TCP connection is established, the BGP messages are transmitted based on the TCP connection. Generally speaking, in BGP messages, except for keep-alive messages that need to be sent periodically, the rest of the BGP messages are sent in a triggered manner. Various BGP messages are queued for transmission based on the first input first output (FIFO) method.

In some application scenarios, network device 1 has a large number of neighbors (that is, it establishes BGP connections with a large number of network devices 2, and network device 1 and network device 2 can send and receive messages based on the BGP protocol). For example, network device 1 is connected to 1,000 network devices 2. If some of the second network devices cause routing updates due to network changes or other reasons, the first network device needs to send 1,000 BGP update messages to 1,000 network devices 2 respectively. At the same time, keep-alive messages need to be sent regularly between each pair of the first network device and the second network device, and BGP update messages and keep-alive messages are queued in a FIFO manner through a unique message sending queue. sending, it may cause some keep-alive messages to be queued after 1000 BGP update messages, causing BGP connections to be disconnected between network devices due to untimely transmission, resulting in BGP service interruption. Furthermore, due to repeated disconnections between network devices And reconnecting will cause route flapping.

In some application scenarios, because the keep-alive time and protection period between network devices are short (for example, the keep-alive period is 1 second and the keep-alive time is 3 seconds), the timeliness requirements for the transmission of keep-alive messages are higher. . In this scenario, if keepalive messages are not transmitted in time, network devices will be disconnected, causing BGP service interruption. Repeated disconnection and reconnection between network devices will cause route flapping.

In view of this, embodiments of the present application provide a message transmission method and network device. Please refer to Figure 2. The first network device uses a first flow carried by a first transport layer protocol and a second flow carried by a second transport layer protocol. Send keep-alive messages and routing protocol update messages respectively, where the keep-alive messages sent through the first flow have a higher priority. Sending keep-alive messages first through offloading can reduce the delay in sending keep-alive messages in time. The resulting BGP service interruption and route flapping.

The following is a detailed introduction to the message transmission method provided by the embodiment of the present application. Please refer to Figure 3a and Figure 3b to introduce respectively the message sending method 310 and the message receiving method 320 in the message transmission method of the embodiment of the present application. The message sending method and the message receiving method can be applied to the scenario shown in Figure 1, where the first network device is equivalent to the network device 1 in the application scenario shown in Figure 1. It should be noted that the second network device The device can be any network device 2 in the application scenario shown in Figure 1 (including network device 2a-network device 2n). The message sending method 310 includes steps S311-S312:

S311. The first network device sends the first keepalive message to the second network device through the first flow carried by the first transport layer protocol;

Before the first network device sends a message to the second network device, the first network device needs to establish a first routing session with the second network device.

In a possible implementation manner, the routing session is specifically a BGP session. In addition, the routing session can also be a BGP Monitoring Protocol (BGP Monitoring Protocol, BMP) session, a BGP link state BGP-LS (BGP Link-state) protocol session, a flow rule (BGP Flow Specification, Flowspec) session, which are not specified here. Make limitations.

It should be understood that in this embodiment of the present application, when a BGP session (sometimes also referred to as a BGP connection) is established between the first network device and the second network device, the first network device and the second network device communicate through the established BGP session. The session sends or receives BGP messages. For other protocol sessions, refer to the description of BGP sessions, which are not listed here.

The BGP session is established based on the transport layer connection. Generally, TCP is used as the transport layer protocol, and the TCP port number is 179. After the TCP session is established, BGP messages are transmitted and reliability is guaranteed based on the TCP session. The first network device and the second network device first establish a TCP session, and then confirm the neighbor relationship by sending and receiving open messages, and establish the first routing session.

Generally, BGP messages corresponding to a BGP session are transmitted through a TCP session, that is, carried in a TCP stream.

In the embodiment of this application, corresponding to the same BGP session, two TCP sessions need to be established, that is, two TCP flows. The first flow is used to transmit keep-alive messages, and the second flow is used to transmit routing update messages. Through all The keep-alive message transmitted by the first stream and the route update message transmitted by the second stream both correspond to the first routing session, and the first transport layer protocol carrying the first stream and the transport layer protocol carrying the second stream There are many possible implementations of protocol types.

As an example, the first transport layer protocol and the second transport layer protocol are both QUIC protocols. The first network device sends keep-alive messages and route update messages in offload based on the QUIC protocol. The first stream identifier of the first stream is the same as the first stream identifier of the second stream. The second stream identifier is different and is suitable for BGP over QUIC scenarios.

As another example, the first transport layer protocol and the second transport layer protocol are muilti-TCP, the two flows correspond to different five-tuples, and the first destination port number of the first flow is the same as the first destination port number of the second flow. The second destination port number is different. Specifically, the first network device sends a first keep-alive message to the second network device through the first port, and the destination port number carried in the keep-alive message corresponds to the second port of the second network device; the first network device sends the first keep-alive message to the second network device through the first port. The three ports send a first routing protocol update message to the second network device, and the destination port number carried in the first routing protocol update message corresponds to the fourth port of the second network device.

As another example, the first transport layer protocol is UDP and the second transport layer protocol is TCP. The keep-alive message is sent based on the UDP protocol, and the routing protocol update message is sent based on the TCP protocol. The first network device sends the first keep-alive message to the second network device through the first port; the destination port number carried in the keep-alive message corresponds to At the second port of the second network device; the first network device sends a first routing protocol update message to the second network device through the first port based on the user datagram protocol.

Subsequently, the first network device needs to send keep-alive messages periodically to maintain the BGP neighbor connection. Similarly, the second network The device will also periodically send keepalive messages to the first network device to maintain the BGP neighbor connection.

S312. The first network device sends a first routing protocol update message to the second network device through the second flow carried by the second transport layer protocol. The first keepalive message corresponds to the first routing protocol update message. In the first routing session, the first network device sends the first keepalive message through the first flow with a higher priority than the first network device sends the first routing protocol through the second flow. Update the priority of the message;

Generally, the first routing protocol update message is triggered by an event and is sent. For example, when the network equipment network of the autonomous system changes and the route needs to be updated, the first network equipment will send the first routing protocol update message to the second network equipment through the second flow. Routing protocol update message, the second network device receives the first routing protocol update message sent by the first network device through the second stream. In a possible implementation, the first network device and the second network device establish a connection based on the BGP protocol, the first routing protocol update message is a BGP update message, and the first keepalive message is the first BGP update protocol message. The documents correspond to the same BGP session.

It should be noted that both the first keepalive message and the first routing protocol update message correspond to the first routing session between the first network device and the second network device. Since the priority of sending the first keepalive message through the first stream is higher, step S311 is executed before step S312.

Optionally, in the first network device, the first keep-alive message is queued and sent in the first queue through the first channel, and the first routing protocol update message is queued and sent in the second queue through the second channel. It should be noted that, There are many queue scheduling methods for the first network device. As a specific example, the first network device sends messages based on the queue scheduling algorithm of strict priority (strict priority, SP), in which the keep-alive messages of the first queue are given priority. Send, when there is no keep-alive message to be sent in the first queue, send the first routing protocol update message in the second queue. As another specific example, the first network device sends a keep-alive message of the first queue and a first routing protocol update message of the second queue based on a weighted round robin (WRR) algorithm, where the first queue The weight of the keep-alive packet is higher than the weight of the first routing protocol update packet in the second queue.

It should be noted that, as shown in the application scenario architecture diagram of Figure 1, the first network device may be connected to multiple second network devices. When the route is updated, the first network device may need to send the first route to multiple second network devices. Protocol update message, at this time, the priority of the first network device sending the first keep-alive message through the first flow is higher than the priority of the first network device sending the routing protocol update message through the second flow.

In the message transmission method in the embodiment of the present application, the keep-alive message and the first routing protocol update message are respectively sent through the first flow and the second flow, and the keep-alive message is sent based on a higher priority, so that Reduce BGP service interruption due to the failure of the first keepalive message to be sent on time due to the first network device sending the first routing protocol update message, and reduce route flapping caused by continuous disconnection and reconnection between neighbors.

It is understandable that in a short timeout scenario, since the keep-alive time and protection period are both short, the timeliness of keep-alive message transmission is required to be higher. In the message transmission method provided by the embodiment of the present application, the priority of the first network device sending the keep-alive message to the second network device through the first flow is higher than the priority of sending the routing protocol update message through the second flow. Higher, it can ensure that when the first keep-alive message and the first routing protocol update message exist in the same routing session, the first keep-alive message will be sent first, thus ensuring the timeliness of sending keep-alive messages and reducing BGP Service interruption reduces route flapping caused by continuous disconnection and reconnection between neighbors.

In a massive neighbor scenario, the first network device is connected to a large number of second network devices, and the first network device needs to transmit a large number of packets. If some second network devices cause routing updates due to network changes or other reasons, the first network device The device needs to send multiple routing protocol update messages. In the message transmission method provided by the embodiment of this application, the first network device passes all The priority of the keep-alive message sent by the first flow to the second network device is higher than the priority of the first routing protocol update message sent by the second flow. Therefore, the timeliness of sending the keep-alive message can be guaranteed. Reduce BGP service interruption and reduce route flapping caused by continuous disconnection and reconnection between neighbors.

Next, a message receiving method provided by an embodiment of the present application is introduced. The message receiving method 320 includes steps S321-S322:

S321. The second network device receives the first keep-alive message sent by the first network device through the first flow carried by the first transport layer protocol;

First, the second network device needs to establish a first routing session with the first network device. In a possible implementation, the routing session is specifically a BGP session. In addition, the routing session can also be a BGP Monitoring Protocol (BGP Monitoring Protocol, BMP) session, a BGP link state BGP-LS (BGP Link-state) protocol session, a flow rule (BGP Flow Specification, Flowspec) session, which are not specified here. Make limitations.

It should be understood that in this embodiment of the present application, when a BGP session (sometimes also referred to as a BGP connection) is established between the first network device and the second network device, the BGP session established between the first network device and the second network device is The session sends or receives BGP messages. For other protocol sessions, refer to the description of BGP sessions, which are not listed here.

The BGP session is established based on the transport layer connection. Generally, TCP is used as the transport layer protocol, and the TCP port number is 179. After the TCP session is established, BGP messages are transmitted and reliability is guaranteed based on the TCP session. The second network device first establishes a TCP session with the first network device, and then confirms the neighbor relationship by sending and receiving open messages, and establishes the first routing session.

As an example, the first transport layer protocol and the second transport layer protocol are both QUIC protocols. The second network device offloads the keep-alive messages and routing update messages based on the QUIC protocol. The first flow identifier of the first flow is the same as the first flow identifier of the second flow. The second stream identifier is different and is suitable for BGP over QUIC scenarios.

As another example, the first transport layer protocol and the second transport layer protocol are muilti-TCP, the two flows correspond to different five-tuples, and the first destination port number of the first flow is the same as the first destination port number of the second flow. The second destination port number is different. Specifically, the second network device receives the first keepalive message sent by the first network device through the second port; the second network device receives the first routing protocol update message sent by the first network device through the fourth port.

As another example, the first transport layer protocol is UDP and the second transport layer protocol is TCP. The keep-alive message is sent based on the UDP protocol, and the routing protocol update message is sent based on the TCP protocol. The second network device receives the keep-alive message sent by the first network device through the first port; the second network device receives the keep-alive message based on the user datagram protocol through the first port. The first port receives a first routing protocol update message sent by the first network device.

Subsequently, the second network device needs to send keep-alive messages periodically to maintain the BGP neighbor connection. Similarly, the first network device will also periodically send keepalive messages to the second network device to maintain the BGP neighbor connection.

S322. The second network device receives the first path sent by the first network device through the second stream carried by the second transport layer protocol. The first keepalive message and the first routing protocol update message both correspond to a first routing session, and the second network device processes the first message received through the first flow. The priority of the keep-alive message is higher than the priority of the second network device in processing the first routing protocol update message;

Generally, the first routing protocol update message is triggered by an event and is sent. For example, when the network device network of the autonomous system changes and the route needs to be updated, the first network device sends the first routing protocol update message to the second network device. The second network device receives the first routing protocol update message sent by the first network device through the second stream. In a possible implementation, the second network device establishes a connection with the first network device based on the BGP protocol, the first routing protocol update message is a BGP update message, and the first keepalive message is the first BGP update protocol message. The documents correspond to the same BGP session.

It should be noted that both the first keepalive message and the first routing protocol update message correspond to the first routing session between the second network device and the first network device. Since the priority of sending the first keepalive message through the first stream is higher, step S321 is executed before step S322.

It should be noted that there are many queue scheduling methods for the second network device. As a specific example, the second network device receives messages based on a strict priority (strict priority, SP) queue scheduling algorithm, in which the first queue Keep-alive messages are received with priority. When the first stream has no keep-alive messages to be received, the first routing protocol update message transmitted by the second stream is received. As another specific example, the second network device receives a keep-alive message based on the first stream transmission and receives a first routing protocol update message based on the second stream transmission based on a weighted round robin (WRR) algorithm, where , the weight of the keep-alive message based on the first stream transmission is higher than the weight of the first routing protocol update message based on the second stream transmission.

It should be noted that, as shown in the application scenario architecture diagram of Figure 1, the first network device may be connected to multiple second network devices. When the route is updated, the first network device may need to send the first route to multiple second network devices. Protocol update message, at this time, the priority of the first network device sending the first keep-alive message through the first flow is higher than the priority of the first network device sending the routing protocol update message through the second flow. The priority of the second network device receiving the first keep-alive message through the first flow is higher than the priority of the second network device receiving the routing protocol update message.

Please refer to Figure 4 below. This embodiment of the present application proposes a message transmission method. This method can be applied to the scenario shown in Figure 1, where network device 1 is equivalent to network device 1 in the application scenario shown in Figure 1, and network device 2 and network device 3 can be network device 1 in the application scenario shown in Figure 1. For any two network devices 2 (including network device 2a-network device 2n), the method 400 includes:

S401. Network device 1 and network device 2 establish a first routing session;

S402. Network device 1 and network device 3 establish a second routing session;

For step S401 and step S402, reference may be made to step S311 in the embodiment corresponding to Figure 3a, which will not be described again here.

S403. Network device 1 sends the first keepalive message to network device 2 through the first flow carried by the first transport layer protocol;

For the specific implementation method of step S403, reference can be made to step S311 in the embodiment corresponding to Figure 3a, which will not be described again here.

S404. Network device 2 receives the first keep-alive message sent by network device 1 through the first flow 1 carried by the first transport layer protocol;

For the specific implementation method of step S404, reference can be made to step S321 in the embodiment corresponding to Figure 3b, which will not be described again here.

S405. Network device 1 sends the second keepalive message to network device 3 through the second flow carried by the first transport layer protocol;

For the specific implementation method of step S405, reference can be made to step S311 in the embodiment corresponding to Figure 3a, which will not be described again here.

Network device 1 sends a first keep-alive message to network device 2 through the first flow according to the keep-alive cycle, and network device 1 sends a second keep-alive message to network device 3 through the second flow. It can be understood that steps S403 and S405 The execution sequence is not limited here. Step S403 may be executed first, and then step S405 may be executed, or step S405 may be executed first and then step S403.

S406. Network device 2 receives the second keep-alive message sent by network device 1 through the second stream carried by the first transport layer protocol;

For the specific implementation method of step S406, reference can be made to step S321 in the embodiment corresponding to Figure 3b, which will not be described again here.

It can be understood that the network device 1 can generate and send the first keep-alive message and the second keep-alive message through the first queue through the same channel.

S407. Network device 1 sends the first routing protocol update message to network device 2 through the third flow carried by the second transport layer protocol;

When the sending of the first routing protocol update message is triggered, the network device 1 sends the first routing protocol update message to the network device 2 through the third flow. For the specific implementation method, refer to step S312 in the embodiment corresponding to Figure 3a, where No longer.

S408. Network device 2 receives the first routing protocol update message sent by network device 1 through the third stream carried by the second transport layer protocol;

For the specific implementation method of step S408, reference can be made to step S322 in the embodiment corresponding to Figure 3b, which will not be described again here.

S409. Network device 1 sends a second routing protocol update message to network device 3 through the fourth flow carried by the second transport layer protocol;

When the sending of the second routing protocol update message is triggered, the network device 1 sends the second routing protocol update message to the network device 3 through the fourth flow. For the specific implementation method, please refer to step S322 in the corresponding embodiment of Figure 3b, where No longer.

S410. Network device 3 receives the second routing protocol update message sent by network device 1 through the fourth stream carried by the second transport layer protocol;

For the specific implementation method of step S410, reference can be made to step S322 in the embodiment corresponding to Figure 3b, which will not be described again here.

It should be noted that since network device 1 has a higher priority for sending keep-alive messages, if there are a first keep-alive message, a second first keep-alive message, a first routing protocol update message and a first keep-alive message in the sending queue, When two routing protocol update messages are sent, the first keep-alive message is sent prior to the first routing protocol update message and the second routing protocol update message. Similarly, the second routing protocol update message is also sent prior to the first routing protocol update message. message and the second routing protocol update message are sent. In another possible implementation, the keep-alive message is sent with priority over all routing protocol update messages. That is to say, in this embodiment, the first keep-alive message has priority over the first routing protocol update message and the first routing protocol update message. The second routing protocol message is sent, and the second keepalive message takes precedence over the first routing protocol update message and the second routing protocol message.

It can be understood that the execution order of step S407 and step S409 is not limited here. Step S407 may be executed first and then step S409, or step S409 may be executed first and then step S407.

The message transmission process within the network device is introduced below. Please refer to Figure 5. The method 500 can correspond to any network device in the scenario shown in Figure 1.

In a possible implementation, the network device transmits messages based on the TCP/IP protocol and the BGP protocol. The network device processes messages through two channels, where the first channel is used to process keep-alive messages, and the second channel is used to process keep-alive messages. The channel is used to process routing protocol update messages. Keep-alive messages in the first channel are sent and received through the first stream carried by the first transport layer protocol. Routing protocol update messages in the second channel are sent and received through the third stream carried by the second transport layer protocol. Second-stream transmission and reception, the keep-alive message and the routing protocol update message correspond to the same routing session, where the first channel has a higher priority.

In some possible implementations, the first network device has a main board and a backup board, and the main board of the network device is used to pass all Describing the packets received by the second stream, in the existing technology, before sending the packet, all packets need to be backed up by the backup board. After the network device receives the packet, all packets also need to be backed up by the backup board and then processed. . Since all messages sent and received by the first network device need to be backed up by the backup board, when the number of messages is large, congestion is prone to occur, affecting the timeliness of sending and receiving keep-alive messages, which may lead to network failure caused by delayed sending and receiving of keep-alive messages. The connection between devices is disconnected, causing business interruption. Please refer to Figure 6 and Figure 7, which respectively show the process of sending packets and receiving packets by network devices in the active and backup scenarios.

As shown in Figure 6, Figure 6 is a method 600 of active and backup transmission in a first network device. The first network device sends a keep-alive message through the first channel through the first flow carried by the first transport layer protocol, and through the second channel , back up the routing protocol update message to the backup board (601), and then send it through the second stream carried by the second transport layer protocol. It is understandable that keep-alive messages do not need to be backed up by the standby board and can be sent directly, which can improve the efficiency of sending keep-alive messages. It should be noted that after the first network device performs active/standby switching, the first network device will create a keep-alive channel, and the keep-alive channel is used to transmit the keep-alive message.

As shown in Figure 7, Figure 7 is a method 700 for active and backup transmission in a second network device. The second network device receives the keep-alive message through the first stream carried by the first transport layer protocol, and transmits it through the first channel in the device; The network device receives the routing protocol update message through the second stream carried by the second transport layer protocol, transmits the routing protocol update message through the second channel within the device, and backs up the routing protocol update message to the backup board (701). It is understandable that keep-alive messages do not need to be backed up by the standby board and can be processed directly, which improves the processing efficiency of keep-alive messages. It should be noted that after the second network device performs active/standby switching, the second network device will create a keep-alive channel, and the keep-alive channel is used to transmit the keep-alive message.

Since keep-alive messages can be transmitted without being backed up by the standby board, the efficiency of keep-alive message processing can be improved and network devices can be reduced from disconnecting BGP connections due to delayed sending and receiving of keep-alive messages, thus reducing BGP service interruptions.

The message transmission method provided by the present application has been introduced above. The first network device and the second network device that implement the message transmission method will be introduced below. Please refer to Figure 8, which shows the first network device in the embodiment of the present application. Schematic diagram of an embodiment.

The first network device 800 may be used to perform method 310, method 400, method 500, and method 600 in the above embodiments. When the first network device 800 is used to perform the method 310 in the above embodiment, the first network device 800 is equivalent to the first network device in the method 310. When the first network device 800 is used to execute the method 400 in the above embodiment, the first network device 800 is equivalent to the network device 1 in the method 400, and the first network device 800 can be applied to the application scenario shown in Figure 1, For example, it can be the network device 1 in the scenario shown in Figure 1 . It includes: a transceiver module 801, configured to send a first keep-alive message to a second network device through a first stream carried by a first transport layer protocol; the transceiver module 801 is also configured to transmit a second stream carried by a second transport layer protocol. The flow sends a first routing protocol update message to the second network device, the first keep-alive message and the first routing protocol update message both correspond to the first routing session, and the first network device passes the The priority of the first keepalive message sent by the first flow is higher than the priority of the first routing protocol update message sent by the first network device through the second flow.

In a possible implementation, the first network device sends the first keepalive message through the first flow with a higher priority than the first network device sends the routing protocol update through the second flow. The priority of the message.

In a possible implementation, the first transport layer protocol includes the Quick User Datagram Protocol Internet Connection QUIC protocol, the second transport layer protocol includes the QUIC protocol, and the first flow identifier of the first flow is the same as the first flow identifier of the first flow. The second-rate logo is different for the second-rate.

In a possible implementation, the first transport layer protocol includes multiple transmission control protocol muilti-TCP or user Datagram protocol UDP, the second transport layer protocol includes muilti-TCP or UDP, and the first destination port number of the first flow is different from the second destination port number of the second flow.

In a possible implementation manner, the first routing protocol update message includes a BGP update message.

In a possible implementation manner, the first keepalive message and the first BGP update protocol message correspond to the same BGP session.

In a possible implementation, the first network device includes a backup board; the first network device further includes: a backup module 802 for backing up the first routing protocol update message in the backup board ; The backup module 802 is also configured for the first network device not to back up the first keep-alive message in the backup board.

In a possible implementation, the first network device further includes: a processing module 803, configured to create a keep-alive channel after the active/standby switchover, and the keep-alive channel is used to transmit the first keep-alive report. arts.

Please refer to FIG. 9 , which is a schematic diagram of a second network device in an embodiment of the present application.

The second network device 900 may be used to perform method 320, method 400, method 500 or method 700 in the above embodiments. When the second network device 900 is used to perform the method 320 in the above embodiment, the second network device 900 is equivalent to the second network device in the method 320. When the second network device 900 is used to perform the method 400 in the above embodiment, the second network device 900 is equivalent to the network device 2 or the network device 3 in the method 400, and the second network device 900 can be applied to the network device shown in Figure 1 In the application scenario, it may be, for example, the network device 2a in the scenario shown in Figure 1 . It includes: a transceiver module 901, configured to receive the first keep-alive message sent by the first network device through the first flow carried by the first transport layer protocol; the transceiver module 901 is also used for receiving the first keep-alive message carried by the second transport layer protocol. The second stream receives the first routing protocol update message sent by the first network device. Both the first keepalive message and the first routing protocol update message correspond to the first routing session. The second network The priority of the device in processing the first keep-alive message received through the first flow is higher than the priority of the second network device in processing the first routing protocol update message.

In a possible implementation, the second network device processes the first keepalive message received through the first flow with a higher priority than the second network device receives through the second flow. The priority of routing protocol update packets.

In a possible implementation, the first transport layer protocol includes muilti-TCP or user datagram protocol UDP, the second transport layer protocol includes muilti-TCP or UDP, and the first flow The first destination port number is different from the second destination port number of the second flow.

In a possible implementation, the second network device includes a backup board; the second network device further includes: a backup module configured to back up the first routing protocol update message in the backup board; The backup module 902 is also configured not to back up the first keep-alive message in the backup board.

In a possible implementation, the first network device further includes: a processing module 903, configured to create a keep-alive channel after the active/standby switchover, and the keep-alive channel is used to transmit the first keep-alive report. arts.

It should be understood that the above division of various modules of the first network device or the second network device is only a division of logical functions. In actual implementation, it can be fully or partially integrated into a physical entity, or it can be physically separated. And these modules can all be implemented in the form of software calling through processing elements; they can also all be implemented in the form of hardware; some modules can also be implemented in the form of software calling through processing elements, and some modules can be implemented in the form of hardware. For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as: one or more application specific integrated circuits (ASICs), or one or more microprocessors (digital signal processor, DSP), or one or more field programmable gate arrays (field programmable gate array, FPGA), etc. For another example, when one of the above modules is implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processors that can call programs. For another example, these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).

Please refer to Figure 10, which is a schematic diagram of another embodiment of the network device in the embodiment of the present application;

The network device 1000 provided in this embodiment may be a switch, a router, or other network device, and the specific device form is not limited in the embodiment of this application.

The network device 1000 can be used to perform method 310, method 320, method 400, method 500, method 600 or method 700 in the above embodiments. When the network device 1000 is used to perform the method 320 in the above embodiment, the network device 1000 is equivalent to the second network device in the method 320. When the network device 1000 is used to perform the method 400 in the above embodiment, the network device 1000 is equivalent to the network device 1, network device 2 or network device 3 in the method 400. The network device 1000 can be applied to the application shown in Figure 1 In the scenario, it may be, for example, the network device 2a in the scenario shown in Figure 1 . There may be relatively large differences due to different configurations or performance, and may include one or more processors 1001 and memory 1002, with programs or data stored in the memory 1002.

Among them, the memory 1002 can be volatile storage or non-volatile storage. Optionally, the processor 1001 is one or more central processing units (CPUs), which may be single-core CPUs or multi-core CPUs. The processor 1001 can communicate with the memory 1002 to execute a series of instructions in the memory 1002 on the network device 1000 .

The network device 1000 also includes one or more wired or wireless network interfaces 1003, such as an Ethernet interface.

Optionally, although not shown in Figure 10, the network device 1000 may also include one or more power supplies; one or more input and output interfaces, which may be used to connect a monitor, mouse, keyboard, touch screen device or sensor. Equipment, etc., input and output interfaces are optional components, which may or may not exist, and are not limited here.

In this embodiment, the process executed by the processor 1001 in the network device 1000 may refer to the method process described in the foregoing method embodiment, and will not be described again here.

For content not described in detail in FIGS. 8 to 10 , please refer to the description of the relevant parts of the method embodiment.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. In another point, the coupling or direct coupling or communication connection between each other shown or discussed may be an indirect coupling or communication through some interfaces, devices or units. Connection may be electrical, mechanical or other forms.

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 they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

As mentioned above, the above embodiments are only used to illustrate the technical solution of the present application, but not to limit it. Although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still make the foregoing technical solutions. The technical solutions described in each embodiment may be modified, or some of the technical features may be equivalently replaced; however, these modifications or substitutions do not cause the essence of the corresponding technical solutions to depart from the scope of the technical solutions in each embodiment of the present application.

Claims

A message transmission method, characterized by including:

The first network device sends a first keep-alive message to the second network device through the first flow carried by the first transport layer protocol;

The first network device sends a first routing protocol update message to the second network device through the second flow carried by the second transport layer protocol, and the first keepalive message and the first routing protocol update message Both correspond to the first routing session, and the priority of the first network device sending the first keep-alive message through the first flow is higher than that of the first network device sending the first keep-alive message through the second flow. The priority of routing protocol update packets.
The method according to claim 1, characterized in that the priority of the first network device sending the first keep-alive message through the first flow is higher than that of the first network device sending the first keep-alive message through the second flow. The priority for sending routing protocol update messages.
The method according to claim 1 or 2, characterized in that the first transport layer protocol includes the Fast User Datagram Protocol Internet Connection QUIC protocol, the second transport layer protocol includes the QUIC protocol, and the first stream of the first stream The first-stream identifier is different from the second-stream identifier of the second stream.
The method according to claim 3, wherein the first transport layer protocol includes muilti-TCP or user datagram protocol UDP, and the second transport layer protocol includes muilti-TCP or UDP, so The first destination port number of the first flow is different from the second destination port number of the second flow.
The method according to any one of claims 1 to 4, characterized in that the first routing protocol update message includes a Border Gateway Protocol BGP update message.
The method of claim 5, wherein the first keepalive message and the first routing protocol update message correspond to the same routing session, including:

The first keep-alive message and the first BGP update protocol message correspond to the same BGP session.
The method according to any one of claims 1 to 6, characterized in that the first network device includes a backup board;

The first network device backs up the first routing protocol update message in the backup board;

The first network device does not back up the first keep-alive message in the backup board.
The method according to any one of claims 1 to 7, characterized in that the first network device creates a keep-alive channel after the active/standby switchover, and the keep-alive channel is used to transmit the first keep-alive channel. message.
A message transmission method, characterized by including:

The second network device receives the first keep-alive message sent by the first network device through the first flow carried by the first transport layer protocol;

The second network device receives the first routing protocol update message sent by the first network device through the second stream carried by the second transport layer protocol, and the first keep-alive message is consistent with the first routing protocol update message. The messages all correspond to the first routing session, and the second network device processes the first keepalive message received through the first flow with a higher priority than the second network device processes the first routing protocol. Update the priority of the message.
The method according to claim 9, characterized in that the second network device processes the first keep-alive message received through the first flow with a higher priority than the second network device through the third stream. The priority of the routing protocol update message received by the second stream.
The method according to claim 9 or 10, characterized in that the first transport layer protocol includes the Fast User Datagram Protocol Internet Connection QUIC protocol, the second transport layer protocol includes the QUIC protocol, and the first stream of the first stream The first-stream identifier is different from the second-stream identifier of the second stream.
The method according to claim 11, wherein the first transport layer protocol includes muilti-TCP or user datagram protocol UDP, and the second transport layer protocol includes muilti-TCP or UDP, so The first destination port number of the first flow is different from the second destination port number of the second flow.
The method according to any one of claims 9 to 12, characterized in that the first routing protocol update message includes a Border Gateway Protocol BGP update message.
The method according to claim 13, wherein the first keep-alive message and the first BGP update protocol message correspond to the same BGP session.
The method according to any one of claims 9 to 14, characterized in that the second network device includes a backup board;

The second network device backs up the first routing protocol update message in the backup board;

The second network device does not back up the first keep-alive message in the backup board.
The method according to any one of claims 9 to 15, characterized in that the second network device creates a keep-alive channel after the active/standby switchover, and the keep-alive channel is used to transmit the first keep-alive channel. message.
A first network device, characterized by including:

A transceiver module configured to send the first keepalive message to the second network device through the first flow carried by the first transport layer protocol;

The transceiver module is also configured to send a first routing protocol update message to the second network device through the second flow carried by the second transport layer protocol. The first keep-alive message is consistent with the first routing protocol update message. The messages all correspond to the first routing session, and the first network device sends the first keepalive message through the first flow with a higher priority than the first network device sends the first keepalive message through the second flow. The priority of the first routing protocol update message.
The first network device according to claim 17, wherein the priority of the first network device sending the first keep-alive message through the first flow is higher than that of the first network device sending the first keep-alive message through the first flow. The second stream sends the priority of the routing protocol update message.
The first network device according to claim 17 or 18, wherein the first transport layer protocol includes the Quick User Datagram Protocol Internet Connection QUIC protocol, the second transport layer protocol includes the QUIC protocol, and the third The first stream identifier of a stream is different from the second stream identifier of said second stream.
The first network device according to claim 19, characterized in that the first transport layer protocol includes muilti-TCP or user datagram protocol UDP, and the second transport layer protocol includes muilti-TCP or UDP, the first destination port number of the first flow is different from the second destination port number of the second flow.
The first network device according to any one of claims 17 to 20, characterized in that the first routing protocol update message includes a BGP update message.
The first network device according to claim 21, wherein the first keep-alive message and the first BGP update protocol message correspond to the same BGP session.
The first network device according to any one of claims 17 to 22, characterized in that the first network device includes a backup board;

The first network device also includes:

A backup module, configured to back up the first routing protocol update message in the backup board;

The backup module is also configured for the first network device not to back up the first keep-alive message in the backup board.
The first network device according to any one of claims 17 to 23, characterized in that the first network device Preparation also includes:

A processing module, configured to create a keep-alive channel after the active/standby switchover, and the keep-alive channel is used to transmit the first keep-alive message.
A second network device, characterized by including:

A transceiver module configured to receive the first keep-alive message sent by the first network device through the first flow carried by the first transport layer protocol;

The transceiver module is also configured to receive the first routing protocol update message sent by the first network device through the second stream carried by the second transport layer protocol, and the first keep-alive message is consistent with the first routing message. The protocol update messages all correspond to the first routing session, and the second network device processes the first keep-alive message received through the first flow with a higher priority than the second network device processes the first The priority of routing protocol update packets.
The second network device according to claim 25, characterized in that the second network device processes the first keep-alive message received through the first flow with a higher priority than the second network device through which the first keep-alive message is received. The priority of the routing protocol update message received by the second flow.
The second network device according to claim 25 or 26, wherein the first transport layer protocol includes the Quick User Datagram Protocol Internet Connection QUIC protocol, the second transport layer protocol includes the QUIC protocol, and the third The first stream identifier of a stream is different from the second stream identifier of said second stream.
The second network device according to claim 27, wherein the first transport layer protocol includes muilti-TCP or user datagram protocol UDP, and the second transport layer protocol includes muilti-TCP or UDP, the first destination port number of the first flow is different from the second destination port number of the second flow.
The second network device according to any one of claims 25 to 28, characterized in that the first routing protocol update message includes a BGP update message.
The second network device according to claim 29, wherein the first keep-alive message and the first BGP update protocol message correspond to the same BGP session.
The second network device according to any one of claims 25 to 30, characterized in that the second network device includes a backup board;

The second network device also includes:

A backup module, configured to back up the first routing protocol update message in the backup board;

The backup module is also configured not to back up the first keep-alive message in the backup board.
The second network device according to any one of claims 25 to 31, characterized in that the first network device further includes:

A processing module, configured to create a keep-alive channel after the active/standby switchover, and the keep-alive channel is used to transmit the first keep-alive message.
A network device, characterized by including:

A memory having computer readable instructions stored therein;

A processor is connected to the memory. When the computer readable instructions are executed by the processor, the network device implements the method according to any one of claims 1 to 16.
A computer program product, characterized in that it includes computer-readable instructions. When the computer-readable instructions are run on a processor, the method according to any one of claims 1 to 16 is implemented.
A computer-readable storage medium, characterized in that instructions are stored in the computer-readable storage medium, and when the instructions are run on a processor, the method according to any one of claims 1 to 16 is implemented. .
A communication system, characterized by including a first network device and a second network device, wherein,

The first network device sends a first keep-alive message to the second network device through the first flow carried by the first transport layer protocol;

The second network device receives the first keep-alive message through the first stream;

The first network device sends a first routing protocol update message to the second network device through the second flow carried by the second transport layer protocol;

The second network device receives the first routing protocol update message through the second stream, and the first keepalive message and the first routing protocol update message both correspond to the first routing session, so The priority of the first network device sending the first keep-alive message through the first flow is higher than the priority of the first network device sending the first routing protocol update message through the second flow, The priority of the second network device in processing the first keep-alive message received through the first flow is higher than the priority of the second network device in processing the first routing protocol update message.
The communication system according to claim 36, the first network device is further configured to perform the method as claimed in any one of claims 2 to 8, and the second network device is further configured to perform the method as claimed in any one of claims 10 to 8. The method described in any one of 16.