WO2017000464A1

WO2017000464A1 - Method and apparatus for sending keepalive message

Info

Publication number: WO2017000464A1
Application number: PCT/CN2015/094033
Authority: WO
Inventors: 沈琴
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-06-30
Filing date: 2015-11-06
Publication date: 2017-01-05
Also published as: CN106330696A

Abstract

Disclosed are a method and apparatus for sending a keepalive message. The method comprises: a keepalive base receives and stores instance information sent by a Border Gateway Protocol (BGP), the instance information being used for indicating a rule of sending, by the keepalive base, a keepalive message; and the keepalive base periodically sends the received keepalive message according to the instance information. The present invention resolves the technical problems in the related art of keepalive timeout and neighbor link breakage caused by the fact that a keepalive message cannot be sent in time due to heavy system traffic.

Description

Method and device for transmitting keep-alive message

Technical field

The present invention relates to the field of communications, and in particular to a method and apparatus for transmitting keep-alive messages.

Background technique

KEEPALIVE is a periodic message exchanged between routing devices to maintain neighbor relationships between devices. The hold time is the maximum time that can elapse between receiving successive KEEPALIVE or UPDATE messages. The keep-alive message is sent in a period of 1/3 of the hold time.

In the related art, the keep-alive message sending method is originally configured by the border gateway protocol itself to construct a keep-alive message, so that when the service is busy, the keep-alive message cannot be sent in time, which may easily lead to the phenomenon of keep-alive timeout neighbors being broken. appear.

In the related art, when the system service is busy, the keep-alive message cannot be sent in time, and the problem of the keep-alive timeout neighbor is broken, and no effective solution has been proposed yet.

Summary of the invention

The embodiment of the present invention provides a method for transmitting a keep-alive message and a device to solve at least the technical problem that the keep-alive message cannot be sent in time due to the busy system service, causing the keep-alive timeout neighbor to be broken.

According to an aspect of the embodiments of the present invention, a method for sending a keep-alive message is provided, including: the keep-alive library receives and stores instance information sent by a Border Gateway Protocol (BGP), where The instance information is used to instruct the keep-alive database to send the keep-alive message. The keep-alive library periodically sends the received keep-alive message according to the instance information.

Optionally, the instance information includes at least one of the following: a sending period of the keep-alive message, a keep-alive type of the keep-alive message, and a packet length of the keep-alive message.

Optionally, after the keep-alive database periodically sends the received keep-alive message according to the instance information, the method further includes: the keep-alive library receiving the changed instance sent by the border gateway protocol Information; the keep-alive library updates the locally saved embodiment information based on the changed instance information.

Optionally, after the keep-alive database periodically sends the received keep-alive message according to the instance information, the method further includes: receiving, by the keep-alive library, the gateway sent by the border gateway protocol for deleting The indication information of the instance information; the keep-alive library deletes the locally saved instance information according to the indication information, and stops sending the insurance Live message.

Optionally, after the keep-alive database periodically sends the received keep-alive message according to the instance information, the method further includes: the keep-alive library receiving the sent by the border gateway protocol for querying The query information of the number of keep-alive messages is sent, and the keep-alive database queries the number of keep-alive messages that have been sent according to the query information, and reports the number of keep-alive messages that have been sent.

According to another aspect of the present invention, a device for transmitting a keep-alive message is provided, including: a processing module, configured to receive and save instance information sent by a border gateway protocol, where the instance information is used to indicate The keep-alive library sends the keep-alive message rule; the sending module is configured to periodically send the received keep-alive message according to the instance information.

Optionally, the apparatus further includes: a first receiving module, configured to receive the changed instance information sent by the border gateway protocol; and an updating module, configured to update the locally saved embodiment information according to the changed instance information.

Optionally, the device further includes: a second receiving module, configured to receive the indication information that is sent by the border gateway protocol to delete the instance information; and the deleting module is configured to delete the locally saved according to the indication information. Instance information, and stop sending the keep-alive message.

Optionally, the device further includes: a third receiving module, configured to receive query information sent by the border gateway protocol for querying the number of sent keepalive messages; and a query module, configured to query according to the query information The number of keep-alive messages sent and the number of keep-alive messages sent.

In the embodiment of the present invention, the keep-alive database receives and saves instance information sent by the border gateway protocol for instructing the keep-alive library to send the keep-alive message, and then the keep-alive library is saved according to the saved location. The manner in which the instance information periodically sends the received keep-alive message, and sends the keep-alive message according to the example information that has been created and saved in the keep-alive database, and only needs to construct a keep-alive message and an example. The information can continue to send the keep-alive message for the purpose of reducing the burden of the service process and saving the system resources, thereby solving the problem that the keep-alive message is not sent in time due to the busy service of the system in the related art. Technical problems with broken links.

DRAWINGS

The accompanying drawings, which are incorporated in the claims In the drawing:

1 is a flowchart of a method for transmitting a keep-alive message according to an embodiment of the present invention;

2 is a structural block diagram of a device for transmitting a keep-alive message according to an embodiment of the present invention;

3 is a block diagram 1 of an optional structure of a device for transmitting a keep-alive message according to an embodiment of the present invention;

4 is a block diagram 2 of an optional structure of a device for transmitting a keep-alive message according to an embodiment of the present invention;

FIG. 5 is a block diagram 3 of an optional structure of a sending apparatus for a keep-alive message according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of an interaction process of a keep-alive library according to an alternative embodiment of the present invention.

detailed description

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

It is to be understood that the terms "first", "second" and the like in the specification and claims of the present invention are used to distinguish similar objects, and are not necessarily used to describe a particular order or order.

According to an embodiment of the present invention, a method for transmitting a keep-alive message is provided, and FIG. 1 is a flowchart of a method for transmitting a keep-alive message according to an embodiment of the present invention. As shown in Figure 1, the steps of the method include:

Step S102: The keep-alive library receives and saves instance information sent by the border gateway protocol BGP.

Step S104: The keep-alive library periodically sends the received keep-alive message according to the instance information.

Optionally, the protection library periodically sends the keep-alive packet according to the sending rule, and the keep-alive packet may first save the keep-alive packet, and then retrieve the keep-alive packet. The keep-alive message sends the keep-alive message according to the sending rule.

In this embodiment, the keepalive database receives and saves the instance information sent by the border gateway protocol for instructing the keep-alive library to send the keep-alive message, and then the keep-alive library periodically sends the instance information according to the saved information. The manner of receiving the keep-alive message is as follows: by saving the keep-alive message according to the example information that has been created and saved in the keep-alive library, it is only necessary to construct the keep-alive message and the sample information to continue. The purpose of sending a keep-alive message is to achieve the technical effect of reducing the burden of the service process and saving the system resources, and the technology of the keep-alive timeout neighbor disconnection caused by the keep-alive message being sent in time due to the busy system service in the related art is solved. problem.

Optionally, the instance information involved in the embodiment includes: a sending period of the keep-alive packet, a keep-alive type of the keep-alive packet, and a packet length of the keep-alive packet. Optionally, the keepalive type is a protocol type of the keepalive message, such as a BGP border gateway protocol, and the packet length may be a frame length of the keepalive packet. The example information may also include the encapsulation mode of the keep-alive message, the sending manner, the carrying method, and the like, which are merely illustrative and do not limit the present invention.

In an optional implementation manner of the embodiment, the keep-alive embodiment may be further updated. After the keep-alive database periodically sends the received keep-alive message according to the foregoing instance information, the method further includes: S21 - step S22, wherein

Step S21: The keep-alive library receives the changed instance information sent by the foregoing border gateway protocol;

Optionally, after the BGP creates and sends keep-alive packets for the first time, you may need to change the instance information and keep-alive packets.

In step S22, the keep-alive library updates the locally saved embodiment information according to the changed instance information.

After receiving the new instance information, the keep-alive library first compares the new instance information with the sample information in the keep-alive library. If the corresponding instance information already exists in the keep-alive library, the old instance information is updated. Then, the keep-alive message is periodically sent according to the new instance information.

In an optional implementation manner of this embodiment, the example information in the keep-alive database may be deleted, and after the keep-alive database periodically sends the received keep-alive message according to the foregoing instance information, the method in this embodiment further The method includes: step S31 - step S32, wherein

Step S31: The keep-alive library receives the indication information sent by the foregoing border gateway protocol for deleting the instance information.

Optionally, when BGP does not need to maintain a keepalive relationship, that is, when the keep-alive packet is not required to be sent, the BGP sends an indication to the keep-alive database to delete the instance information.

Step S32: The keep-alive library deletes the locally saved instance information according to the indication information, and stops sending the keep-alive message.

In an optional implementation manner of this embodiment, the number of times the keep-alive message is sent may be queried, and after the keep-alive database periodically sends the received keep-alive message according to the instance information, the method in this embodiment The method may further include: step S41 - step S42, wherein

In step S41, the keep-alive database receives the query information sent by the border gateway protocol for querying the number of keep-alive packets sent;

In step S42, the keep-alive library queries the number of the keep-alive messages that have been sent according to the query information, and reports the number of keep-alive messages that have been sent.

Optionally, in order to monitor or manage keep-alive messages, BGP may also query the keep-alive database for the number of keep-alive messages sent.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present invention in essence or the contribution to the related art can be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, CD-ROM). The instructions include a plurality of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the above-described methods of various embodiments of the present invention.

In this embodiment, a device for transmitting keep-alive messages is provided, which is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

2 is a structural block diagram of a device for transmitting a keep-alive message according to an embodiment of the present invention. As shown in FIG. 2, the device includes: a processing module 20, and a sending module 22, where

The processing module 20 is configured to receive and save instance information sent by the border gateway protocol;

The sending module 22 is coupled to the processing module 20 and configured to periodically send the received keep-alive message according to the instance information.

Optionally, the sending module 22 processes the keep-alive packet and the instance information received by the module 20, and periodically sends the keep-alive packet according to the sending rule, and the sending module 22 may also save the keep-alive packet first, and then the policy is saved. The keep-alive message in the live library sends the keep-alive message according to the sending rule.

In this embodiment, the processing module 20 receives and saves the instance information sent by the border gateway protocol for instructing the keep-alive library to send the keep-alive packet, and then the sending module 22 periodically sends the instance information according to the saved instance information. The method of receiving the keep-alive message is to send the keep-alive message according to the example information that has been created and saved in the keep-alive library, so that only one keep-alive message and the sample information can be constructed to continue to send the message. The purpose of the live message is to achieve the technical effect of reducing the burden of the service process and saving system resources, thereby solving the technical problem that the keep-alive timeout neighbor is broken due to the inability of the keep-alive message to be sent in time due to the busy system service.

Optionally, the instance information involved in the embodiment may include: a sending period of the keep-alive message, a keep-alive type of the keep-alive message, and a packet length of the keep-alive message. Optionally, the keepalive type is a protocol type of the keep-alive packet, such as the border gateway protocol BGP, and the packet length may be a frame length of the keep-alive packet, and the instance information may further include a manner of encapsulating the keep-alive packet. It is to be noted that the present invention is not limited to the present invention.

3 is a block diagram 1 of an optional structure of a device for transmitting a keep-alive message according to an embodiment of the present invention, as shown in FIG. The device processing processing module 20 and the sending module 22 include: a first receiving module 30, an updating module 32, wherein

The first receiving module 30 is configured to receive the changed instance information sent by the border gateway protocol;

The update module 32 is coupled to the first receiving module 30 and the transmitting module 22 and is configured to update the locally saved embodiment information according to the changed instance information.

FIG. 4 is a block diagram of an optional structure of a device for transmitting a keep-alive message according to an embodiment of the present invention. As shown in FIG. 4, the device processing module 20 and the sending module 22 include: a second receiving module 40, Deleting module 42, wherein

The second receiving module 40 is configured to receive the indication information that is sent by the foregoing border gateway protocol and used to delete the instance information.

Optionally, when the BGP does not need to maintain a keepalive relationship with the neighboring device, that is, when the keepalive packet does not need to be sent, the BGP sends the indication information of deleting the instance information to the keep-alive database.

The deleting module 42 is configured to delete the locally saved instance information according to the foregoing indication information, and stop sending the keep-alive message.

5 is a block diagram 3 of an optional structure of a device for transmitting keep-alive messages according to an embodiment of the present invention. As shown in FIG. 5, the device processing module 20 and the sending module 22 include: a third receiving module 50, Query module 52, wherein

The third receiving module 50 is configured to receive the query information sent by the foregoing border gateway protocol for querying the number of sent keepalive messages;

The querying module 52 is configured to query the number of the keep-alive messages that have been sent according to the query information, and report the number of keep-alive messages that have been sent.

It should be noted that each of the foregoing modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; Don't be in multiple processors.

The invention will now be described in connection with an alternative embodiment of the embodiment.

The optional embodiment provides a method for implementing BGP keepalive message transmission based on the keep-alive library. In this alternative embodiment, BGP only needs to construct a keep-alive message once and send it once, which can effectively reduce the service. The burden of the process saves the system resources; the subsequent delivery of keep-alive packets by the keep-alive library avoids the phenomenon that the keep-alive timeout neighbors are broken due to busy traffic, which enhances the stability of the service.

In this optional embodiment, if the negotiated keep-alive time is greater than 0, the BGP will provide the keep-alive packet format and the sending interval to be sent to the keep-alive database, and the keep-alive library will copy the keep-alive packets. Send it, and BGP itself does not need to send it again. If the negotiated keep-alive time is equal to 0, the keep-alive message is not sent. The number of keep-alive packets sent, based on the neighbor group that BGP needs to query, constructs a message and performs bulk query to the keep-alive library.

FIG. 6 is a schematic diagram of an interaction process of a keep-alive library according to an alternative embodiment of the present invention. As shown in FIG. 6, the steps of the interaction process include:

Step S602, the BGP creates a keepalive instance corresponding to the neighbor, and the client (Client) synchronizes the keepalive instance information to the server (Server) of the keep-alive library.

The keep-alive instance includes an interval for sending packets, a keep-alive type, and a packet length.

Step S604, the BGP invokes the keep-alive interface to send the keep-alive message, and the client synchronizes the keep-alive message to the server of the keep-alive library, and the keep-alive message is sent by the keep-alive database periodically;

In step S606, the instance information is changed. After the BGP changes the instance information, the keepalive interface is re-invoked, and the instance information and the keep-alive message information are synchronized to the keep-alive database.

In step S608, when the BGP needs to query the number of the keep-alive packets, the keepalive instance corresponding to the neighbor to be queried is packaged into a group, and the client synchronizes the query information to the keep-alive server to query and obtain the query result. After the server synchronizes to the client, BGP asynchronously obtains the required query result;

In step S610, for the link that does not need to re-send the keep-alive message or the link that needs to be disconnected, the BGP deletes the keep-alive instance corresponding to the neighbor, and the client synchronizes to the server, notifying the keep-alive database that the keep-alive message is no longer sent.

The service process periodically sends the keep-alive message, and the original process needs to periodically exchange with the sending and receiving packet process. In this embodiment, only one message needs to be constructed once, which can greatly save system resources, and the scheduled keep-alive message is handed over. The completion of the keep-alive database ensures that the periodic keep-alive message transmission is not affected by the busy traffic, which can effectively enhance the stability of the service.

Embodiments of the present invention also provide a storage medium. Optionally, in the embodiment, the foregoing storage medium may be configured to store program code for performing the following steps:

S1. The instance information sent by the border gateway protocol is received and saved, where the instance information is used to indicate that the keep-alive database sends the keep-alive message.

S2. The received keep-alive message is periodically sent according to the foregoing instance information.

Optionally, in this embodiment, the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory. A variety of media that can store program code, such as a disc or a disc.

For example, the specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above is only an alternative embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

Claims

A method for sending keep-alive messages, including:

The keep-alive database receives and saves the instance information sent by the border gateway protocol BGP, where the instance information is used to instruct the keep-alive database to send the keep-alive message rule;

The keep-alive library periodically sends the received keep-alive message according to the instance information.
The method of claim 1, wherein the instance information comprises at least one of the following:

The transmission period of the keep-alive message, the keep-alive type of the keep-alive message, and the packet length of the keep-alive message.
The method according to claim 1, wherein after the keep-alive library periodically sends the received keep-alive message according to the instance information, the method further includes:

The keep-alive library receives the changed instance information sent by the border gateway protocol;

The keep-alive library updates the locally saved embodiment information according to the changed instance information.
The method according to claim 1 or 3, wherein after the keep-alive library periodically sends the received keep-alive message according to the instance information, the method further includes:

The keep-alive library receives the indication information sent by the border gateway protocol for deleting the instance information;

The keep-alive library deletes the locally saved instance information according to the indication information, and stops sending the keep-alive message.
The method according to claim 1, wherein after the keep-alive library periodically sends the received keep-alive message according to the instance information, the method further includes:

The keep-alive library receives the query information sent by the border gateway protocol for querying the number of sent keep-alive messages;

The keep-alive database queries the number of keep-alive messages that have been sent according to the query information, and reports the number of keep-alive messages that have been sent.
A device for transmitting keep-alive messages, comprising:

a processing module, configured to receive and save instance information sent by the border gateway protocol, where the instance information is used to instruct the keep-alive database to send the keep-alive message rule;

The sending module is configured to periodically send the received keep-alive message according to the instance information.
The apparatus of claim 6, wherein the instance information comprises at least one of the following:

The transmission period of the keep-alive message, the keep-alive type of the keep-alive message, and the packet length of the keep-alive message.
The apparatus of claim 6 wherein said apparatus further comprises:

a first receiving module, configured to receive the changed instance information sent by the border gateway protocol;

The update module is set to update locally saved embodiment information based on the changed instance information.
The device according to claim 6 or 8, wherein the device further comprises:

a second receiving module, configured to receive indication information that is sent by the border gateway protocol to delete the instance information;

The deleting module is configured to delete the locally saved instance information according to the indication information, and stop sending the keep-alive message.
The apparatus of claim 6 wherein said apparatus further comprises:

a third receiving module, configured to receive the query information sent by the border gateway protocol for querying the number of keep-alive messages sent;

The query module is configured to query the number of keep-alive messages that have been sent according to the query information, and report the number of keep-alive messages that have been sent.