WO2019080904A1

WO2019080904A1 - Method and device for negotiation fragmentation of link management protocol

Info

Publication number: WO2019080904A1
Application number: PCT/CN2018/111929
Authority: WO
Inventors: 吴海生
Original assignee: 中兴通讯股份有限公司
Priority date: 2017-10-27
Filing date: 2018-10-25
Publication date: 2019-05-02
Also published as: CN109729039A; CN109729039B

Abstract

A method for the negotiation fragmentation of a link management protocol, comprising: a first node sending a configuration message to a second node, the configuration message carrying a first packet negotiation length value (S201); when the first node receives a configuration pass message that is sent by the second node, the first node packaging a pre-determined packet according to the first packet negotiation length value, and sending the packaged pre-determined packet to the second node (S202).

Description

Negotiation fragmentation method and device for link management protocol

Technical field

The present invention relates to the field of data network communication, and in particular to a negotiation fragmentation method and apparatus for a Link Management Protocol (LMP).

Background technique

In the current generalized multi-protocol label switching (GMPLS) protocol family, the LMP is used to manage links between nodes and IP Control Channels (IPCCs). LMP features include control channel management, link attribute association, link connectivity verification, and fault management. The first two are used to manage traffic engineering (TE, Traffic Engineering), which is the core function of the link. The latter two are optional extension functions for dealing with the separation of control channels and data channels.

The message in the LMP protocol is a User Datagram Protocol (UDP) message. When the LMP packet is too large (more than the maximum transmission unit length (MTU) that the link layer can bear), the message is sent. When the UDP is sent, the LMP packet is fragmented at the IP layer, and the packet is divided into several slices, so that each slice is smaller than the MTU value, and the receiver IP layer needs to reassemble the LMP packet. However, due to the characteristics of UDP (that is, for connectionless, the message transmission is unreliable), when a certain packet is lost in transmission, the reception is convenient to reassemble the packet, resulting in discarding the entire LMP datagram.

One of the functions of the LMP protocol is link attribute association, which is used to aggregate multiple data links (Data-Link) into one TE link (TE-Link) and to synchronize each feature of TE-Link, such as As shown in FIG. 1, there is one TE-Link between the LMP node A and the LMP node B, and the TE-Link includes three Data-Links. The packets transmitted in the TE-Link may include a link summary message (LinkSummary), a link summary response message (LinkSummaryAck), and a link summary failure response message (LinkSummaryNack), among which three types of messages are included in the LinkSummary message and the LinksummaryNack message. A large amount of Data-Link information can be carried. Therefore, the length of the two types of messages is unknown. When there are many data links on the device, the length of the LinkSummary message and the LinksummaryNack message is too large, which may exceed the MTU value of the link layer. Therefore, LinkSummary The message and the LinksummaryNack message are frequently fragmented during the IP transmission process, which increases the probability of packet loss after fragmentation. In severe cases, the transmission channel is blocked, which affects network stability and performance.

Summary of invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiments of the present invention provide a method and a device for negotiating fragmentation of a link management protocol, which can reduce the number of packets after fragmentation, reduce the probability of packet loss after fragmentation, and improve network stability and performance.

In one aspect, a method for negotiating a link management protocol according to an embodiment of the present invention includes: a first node sending a configuration message (Config) to a second node, where the configuration message carries a first message negotiation. a length value; when the first node receives the configuration pass message (ConfigAck) sent by the second node, the first node packages the predetermined packet according to the first packet negotiation length value, And transmitting the packaged predetermined message to the second node.

On the other hand, the embodiment of the present invention further provides a negotiation fragmentation method of a link management protocol, including: receiving, by a second node, a configuration message sent by a first node, where the configuration message carries a first packet negotiation length value The second node determines whether the first packet negotiation length value is within a second preset range; and in a case where the first packet negotiation length value is within a second preset range, to the first A node sends a configuration through message.

On the other hand, the embodiment of the present invention further provides a negotiation fragmentation device of a link management protocol, which includes: a configuration message sending module, configured to send a configuration message to a second node, where the configuration message carries a first report And the first receiving module is configured to: when receiving the configuration passing message sent by the second node, packetizing the predetermined packet according to the first packet negotiation length value; the first sending module And configured to send the packaged predetermined message to the second node.

In another aspect, the embodiment of the present invention further provides a negotiation fragmentation device of a link management protocol, including: a configuration message receiving module, configured to receive a configuration message sent by the first node, where the configuration message has a first a packet negotiation length value; the second judging module is configured to determine whether the first packet negotiation length value is within a second preset range; and the second sending module is configured to negotiate a length value in the first packet In the case of the second preset range, a configuration pass message is sent to the first node.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

1 is a schematic diagram of a TE link and a Data-Link of an LMP protocol;

2 is a flowchart of a method for negotiating fragmentation of an LMP according to an embodiment of the present invention;

3 is a flowchart of a method for negotiating fragmentation of another LMP according to an embodiment of the present invention;

4 is a schematic structural diagram of a LAMP negotiation fragmentation apparatus according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of another LMP negotiation fragmentation apparatus according to an embodiment of the present invention; FIG.

FIG. 6 is a schematic structural diagram of an apparatus according to an embodiment of the present invention.

Detailed

The method and device for negotiating fragmentation of a link management protocol are provided in this embodiment of the present invention, because the packet is frequently fragmented during transmission, and the probability of packet loss after fragmentation is increased, which affects the stability and performance of the network. The embodiments of the present invention are further described in detail below with reference to the accompanying drawings. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

An embodiment of the present invention provides a method for negotiating fragmentation of an LMP, and a flowchart thereof is shown in FIG. 2, including steps S201 and S202:

S201: The first node sends a configuration message to the second node, where the configuration message carries a first packet negotiation length value.

S202. If the first node receives the configuration pass message sent by the second node, the first node packages the predetermined message according to the first packet negotiation length value, and sends the packaged predetermined message to the second message. node.

In the LMP protocol, in order to initiate an LMP connection between two nodes, the control channel between the two nodes must be activated, and the activation of the control channel transfers the configuration message, the configuration through message, and the configuration failure message through the nodes. To implement the negotiation fragmentation, determine the maximum packet length that can be used between the two nodes. When the first node sends the Config message to the second node, the first packet is added to the existing Config message object. The object of the length value, the value represented by the object is the maximum message length (MDL, Max Data Len) approved by the first node, and the class of the object is Class=1, and the attribute ctype=2, which may also be called an MDL-Config object. . The first node sends a Config message carrying the first packet negotiation length value to the second node, and waits for the message that the second node responds.

When receiving the message that the second node responds, the first node first determines whether the message is a ConfigAck message or a ConfigNack message. When the message received by the first node is a ConfigAck message, it is proved that the second node has passed the negotiation of the fragmentation parameter. At this time, the first node determines whether the ConfigAck message includes the second packet negotiation configured by the second node. The object of the length value, the class of the object is also 1. The ctype is also 2, and if the ConfigAck message sent by the second node does not include the second packet negotiation length value, it is proved that the second node recognizes the first configuration of the first node. The packet length value is in a range receivable by the second node, and when the first node sends a packet to the second node, the first packet is fragmented and packaged according to the first packet negotiation length value, and is packaged. The subsequent scheduled message is sent to the second node. It should be understood that the predetermined message may be any message sent between two nodes after the control channel is activated. As an implementation manner, the predetermined message is a LinkSummary message and a LinksummaryNack message carrying a large amount of Data-Link information. If the ConfigAck message sent by the second node includes the second packet negotiation length value, the first node, when sending the packet to the second node, performs fragmentation and packaging on the predetermined packet to be sent according to the second packet length value. And sending the packaged scheduled message to the second node.

When the message received by the first node is a ConfigNack message, the second node does not support the negotiation fragmentation, or the second node does not recognize the first packet negotiation length value configured by the first node. When the ConfigNack message received by the first node includes the Error_Code object of ctype=0x40, it is proved that the second node does not support the negotiation fragmentation, the negotiation fails, and the control channel cannot be activated. When the ConfigNack message received by the first node includes the object of the third packet length value, the object has Class=1 and ctype=2, that is, the second node does not recognize the first packet negotiation length value configured by the first node, The third packet negotiation length value in the ConfigNack message indicates the maximum packet length that the second node approves and can receive itself. The first node determines whether the third packet negotiation length value is the first pre-receivable value. Set within the scope. When the third packet negotiation length value is in the first preset range, the first node sends a configuration message to the second node to perform a new round of negotiation fragmentation. At this time, the configuration message carries the third packet. Negotiating the length value, and waiting for the negotiation result of the second packet negotiation length value of the second node; if the third packet negotiation length value is not within the first preset range, the first node performs an alarm, and it should be understood that The method for the first node to perform the alarm may be prompted to the user of the first node by using a pop-up window, etc., to notify the user to actively modify the first preset range, and ensure the negotiation between the first node and the second node as much as possible.

In order to reduce the number of negotiation between the two nodes, before the first node sends the Config message, it is necessary to determine an optimal maximum packet length, that is, the first packet negotiation length value, for the current network condition and device condition. The user of the first node can first set an MDL value according to the user experience (that is, the maximum test packet length), and then package the test packet according to the preset maximum packet length, and send the packaged test packet. To the second node; the first node also needs to monitor the sending success rate of the test packet, and adjust the size of the MDL value according to the sending success rate until the first node performs the testing of the packet according to the current MDL value, and then tests The current MDL value is the optimal maximum packet length in the current network state and device condition, and the current MDL value is used as the first packet negotiation length value. The Config message is sent to the second node, and the number of negotiation between the two nodes can be reduced as much as possible while reducing the number of times of fragmentation and reducing the rate of packet loss. It should be understood that, when performing the optimal MDL value confirmation, the first node may also use the packet loss rate of the test packet, the transmission failure rate, and the like as a criterion, and is not limited to using the transmission success rate.

In this embodiment, the maximum packet length that can be sent is negotiated before the packet is transmitted, so that when the data link is too long, the packet needs to be fragmented, and the fragmentation may be performed according to the maximum packet length after negotiation. The number of packets after fragmentation is reduced, and the probability of packet loss after fragmentation is reduced, which improves the stability and performance of the network.

The embodiment of the present invention further provides a negotiation fragmentation method of another LMP, and the flowchart thereof is as shown in FIG. 3, including steps S301 and S303:

S301. The second node receives a configuration message sent by the first node, where the configuration message carries a first packet negotiation length value.

S302. The second node determines whether the first packet negotiation length value is within a second preset range.

S303. The second node sends a configuration pass message to the first node if the first packet negotiation length value is within the second preset range.

After receiving the Config message carrying the first packet negotiation length value sent by the first node, the second node first determines whether it can support the negotiation fragmentation mechanism. It should be understood that whether the node supports the negotiation fragmentation should be the The user of the node actively sets the setting, and the setting principle can be adjusted according to factors such as the device used by the node and the current network status. When the second node does not support the negotiation fragment, the second node may ignore the object of the first packet negotiation length value carried in the Config message, and only process other objects in the Config message until the reply does not carry the second packet. The ConfigAck message of the negotiated length value is sent to the first node. At this time, the first node performs fragmentation and packetization processing on the predetermined packet according to the first packet negotiation length value. When the second node does not support the negotiation fragmentation, the second node may also reply to the ConfigNack message containing the Error_Code object of ctype=0x40 to indicate to the first node that it does not support the negotiation fragmentation.

In this embodiment, when the second node supports the negotiation fragmentation, it is first determined whether the first packet negotiation length value is within the second preset range that can be received, and the first packet negotiation length value is in the second pre- In the case of the range, the second node sends a ConfigAck message to the first node, where the second message negotiation length value may be included. It should be understood that the second packet negotiation length value should be the smaller one of the first packet negotiation length value and the second packet optimal packet length value, for example, the first packet length value is M1. The second packet has a predetermined optimal message length value of M2, the second preset range is [X2, Y2], and if X2 ≤ M1 ≤ Y2, the second packet length value is min{M1, M2}. And if the first packet negotiation length value is not in the second preset range, sending a ConfigNack message to the first node, where the ConfigNack message includes a third packet negotiation length value. It should be understood that if M1 < X2, the third message negotiation length value is X2, and if M1>Y2, the third message negotiation length value is Y2. After receiving the third packet negotiation length value ConfigNack message, the first node determines whether the third packet negotiation length value is within the first preset range, and determines, according to the determination result, that the third packet negotiation length value is required. Re-send the Config message or perform an alarm.

In this embodiment, the second node negotiates the length of the first packet negotiation with the preset range of the first packet, and when the condition is met, receives the packet that is sent by the first node and is packaged according to the negotiated packet length value. The message not only reduces the number of times the first node is fragmented, but also reduces the number of times the second node reassembles at the time of receiving, avoiding frequent fragmentation of packets when transmitting, and reducing the number of fragments after fragmentation. The probability of loss of text improves the stability and performance of the network.

The embodiment of the present invention further provides a LMP negotiation fragmentation apparatus. The schematic diagram of the structure is as shown in FIG. 4, which mainly includes: a configuration message sending module 401, a first receiving module 402, and a first sending module 403. The configuration message sending module 401 is configured to send a configuration message to the second node, where the configuration message carries a first packet negotiation length value; the first receiving module 402 is configured to receive the configuration through the second node. In the case, the predetermined message is packaged according to the first packet negotiation length value; the first sending module 403 is configured to send the packaged predetermined message to the second node.

The negotiating fragmentation apparatus provided in this embodiment may be installed in a device used by the first node. Before the first node needs to perform packet transmission to the second node, the control channel between the two nodes must be activated first. In order to implement the negotiation fragmentation, the maximum packet length that can be used between the two nodes is determined, and the configuration message is sent. The module 401 is configured to: when the Config message is sent to the second node, add an object of the first packet negotiation length value based on the existing Config message object, where the value represented by the object is an MDL value approved by the first node, The negotiation fragmentation device sends a Config message carrying the first message negotiation length value to the second node, and waits for the message that the second node responds.

The first receiving module 402 is configured to first determine, by using the first determining unit 4021 in the first receiving module 402, whether the second packet negotiation length value is included in the ConfigAck message when the ConfigAck message is received by the second node, and The determination result notification packetizing unit 4022, if the ConfigAck message does not include the second packet negotiation length value, the packaging unit 4022 is configured to package the predetermined packet according to the first packet negotiation length value, and package the packet by the first sending unit 403. The subsequent scheduled message is sent to the second node; if the ConfigAck message includes the second packet negotiation length value, the packing unit 4022 is configured to package the predetermined packet according to the second packet negotiation length value, and pass the first sending unit. 403 sends the packaged scheduled message to the second node.

The negotiation fragmentation apparatus of this embodiment further includes a second receiving module configured to receive the ConfigNack message sent by the second node, to prove that the second node does not support the negotiation fragmentation, or the second node does not recognize the first packet length value. When the ConfigNack message received by the second receiving module includes the Error_Code object of ctype=0x40, it is proved that the second node does not support the negotiation fragmentation, the negotiation fails, and the control channel cannot be activated. When the ConfigNack message received by the second receiving module includes the third packet negotiation length value, that is, the second node does not approve the first packet negotiation length value, the third packet negotiation length value in the ConfigNack message indicates the second node. The acknowledged fragmentation apparatus of the present embodiment further includes a first judging module configured to determine whether the third packet negotiation length value is the first one that can be received. Within the preset range. When the third packet negotiation length value is in the first preset range, the configuration message sending module 401 is configured to resend the Config message to the second node to perform a new round of negotiation fragmentation. At this time, the Config message carries The third packet negotiates the length value, and waits for the negotiation result of the second packet negotiation length value of the second node; the negotiation fragmentation device of this embodiment further includes an alarm module, where the third packet negotiation length value is not in the first pre- In the case of the range, the alarm module is set to perform the alarm. It should be understood that the alarm module can set the alarm mode to prompt the user of the first node through the pop-up window to notify the user to actively modify the first The preset range ensures that the negotiation between the first node and the second node is as successful as possible.

In order to reduce the number of negotiation between the two nodes, before the configuration message sending module 401 sends the Config message, it is necessary to determine an optimal maximum packet length, that is, the first packet negotiation length value, for the current network condition and the device situation. The user of the first node can first set an MDL value according to the user experience (that is, preset the maximum packet length), and then the monitoring module set by the embodiment of the present invention packages the test packet according to the preset maximum packet length. And sending the packaged test packet to the second node; the monitoring module is further configured to monitor the sending success rate of the test packet, and adjust the size of the MDL value according to the sending success rate until the first node follows the current MDL value. When the test packet is packaged, the success rate of the test packet is greater than the preset transmission success rate. At this time, the current MDL value is the optimal maximum packet length in the current network state and device condition, and the current MDL is The value is used as the first packet negotiation length value, and is sent to the second node by the configuration message sending module 401. The number of times of negotiation between the two nodes can be reduced as much as possible while reducing the number of times of fragmentation and reducing the packet loss rate. It should be understood that, when performing the optimal MDL value confirmation, the monitoring module can also use the packet loss rate of the test packet, the transmission failure rate, and the like as a criterion, and is not limited to the use of the transmission success rate.

It should be understood that when the two nodes perform packet transmission, congestion may occur due to the influence of other devices on the network. At this time, the monitoring module can continuously monitor the transmission success rate of the packet, and when the transmission success rate is reduced to After a certain value, the MDL value is re-determined to ensure that the packet is sent with reduced packet loss.

In this embodiment, the maximum packet length that can be sent is negotiated before the packet is transmitted, so that when the data link is too long, the packet needs to be fragmented, and the fragmentation may be performed according to the maximum packet length after negotiation. Reduce the number of packets after fragmentation, reduce the probability of packet loss after fragmentation, avoid frequent fragmentation of packets when sending packets, reduce the probability of packet loss after fragmentation, and improve network stability and performance.

The embodiment of the present invention further provides a negotiation fragmentation device of another LMP. The schematic diagram of the structure is as shown in FIG. 5, and mainly includes a configuration message receiving module 501, a second determining module 502, and a second sending module 503. The configuration message receiving module 501 is configured to receive the configuration message sent by the first node, where the configuration message has a first packet negotiation length value, and the second determining module 502 is configured to determine whether the first packet negotiation length value is in the first The second sending module 503 is configured to send a configuration pass message to the first node if the first packet negotiation length value is within the second preset range.

The negotiating fragmentation apparatus in this embodiment may be installed in a device used by the second node. The configuration message receiving module 501 is configured to first determine whether it can support the negotiation fragmentation mechanism after receiving the Config message carrying the first packet negotiation length value sent by the first node. When the negotiation fragmentation device does not support the negotiation fragmentation, the configuration message receiving module 501 can ignore the object of the first packet negotiation length value carried in the Config message, and only process other objects in the Config message until the second sending module. 503 replies to the ConfigAck message that does not carry the second packet negotiation length value to the first node. At this time, the first node performs fragmentation and packetization processing on the predetermined packet according to the first packet negotiation length value. When the negotiation fragmentation device does not support the negotiation fragmentation, the second sending module 503 may also be configured to reply to the ConfigNack message containing the Error_Code object of ctype=0x40 to indicate to the first node that it does not support the negotiation fragmentation.

In this embodiment, when the negotiation fragmentation device supports the negotiation fragmentation, the second determination module 502 first determines whether the first packet negotiation length value is within the second preset range that can be received, in the first packet. In the case that the negotiation length value is within the second preset range, the second sending module 503 is configured to send a ConfigAck message to the first node, where the second message negotiation length value may be included. It should be understood that the second packet negotiation length value should be the smaller one of the first packet negotiation length value and the second packet optimal length negotiated length value, for example, the first packet negotiation length value. For M1, the optimal message negotiation length value of the second node is M2, the second preset range is [X2, Y2], and if X2 ≤ M1 ≤ Y2, the second message negotiation length value is min{M1, M2}. If the first packet negotiation length value is not in the second preset range, the second sending module 503 is configured to send a ConfigNack message to the first node, where the ConfigNack message includes a third packet negotiation length value. It should be understood that if M1 < X2, the third message negotiation length value is X2, and if M1>Y2, the third message negotiation length value is Y2. After receiving the third packet negotiation length value ConfigNack message, the first node determines whether the third packet negotiation length value is within the first preset range, and determines, according to the determination result, that the third packet negotiation length value is required. Re-send the Config message or perform an alarm.

In this embodiment, the negotiation fragmentation apparatus negotiates the length of the first packet negotiation length with the preset range of the first packet, and when the condition is met, the packet received by the first node is packaged according to the negotiated packet length value. The scheduled message reduces the number of fragments of the first node at the time of transmission, and also reduces the number of reassembly of the second node at the time of receiving, thereby avoiding frequent fragmentation of the message when it is transmitted, and reducing the fragmentation. The probability of packet loss increases the stability and performance of the network.

A fifth embodiment of the present invention provides a device that supports a negotiation fragmentation apparatus, and can perform operations such as activation of a control channel and transmission of a Data-Link as a node in the LMP, and supports a negotiation fragmentation mechanism. . The device will be described below in conjunction with FIG. 6.

As shown in FIG. 6 , the device provided by the embodiment of the present invention mainly includes: a configuration unit 601 and a message codec unit 602 (corresponding to the configuration message sending module 401, the packaging unit 4022, and the first sending module 403 in the foregoing embodiment of the present invention. And the second receiving module and the partial functions of the configuration message receiving module 501 and the second sending module 503 of the foregoing embodiment of the present invention, the monitoring unit 603 (corresponding to some functions of the monitoring module of the foregoing embodiment of the present invention), and the policy unit 604 ( It is equivalent to the first function of the first determining unit 4021, the first determining module, and the monitoring module of the foregoing embodiment of the present invention, and the partial functions of the second determining module 502 and the second sending module 503 of the foregoing embodiment of the present invention. The configuration unit 601 is mainly configured to perform the configuration of the MDL value when the packet is fragmented, and the configuration includes the user setting an optimal MDL value in advance, and is also configured to perform an alarm (corresponding to the alarm in the foregoing embodiment of the present invention). The module codec unit 602 is configured to receive and send an lmp message (including all messages sent in the LMP protocol, such as a Config message, a ConfigAck message, a ConfigNack message, a LinkSummary message, a LinksummaryAck message, and a LinksummaryNack message), and decode from the lmp message. The parameters of the related object are sent out by the policy unit 604, and the coded and packetized message is sent. The monitoring unit 603 is configured to monitor the sending and receiving of the message, calculate the success rate of the packet sending, and the packet loss rate. The policy unit 604 performs the adjustment of the MDL value; the policy unit 604 is configured to perform the negotiation according to the relevant parameters decoded by the message codec unit 602, determine the appropriate MDL value, and dynamically adjust the MDL value according to the monitoring result of the monitoring unit 603. To ensure that the current MDL value can reduce the number of fragments of the packet and reduce the packet loss rate of the packet.

The embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, which when executed by the processor, implement the link management protocol applied to the first node as described above Negotiate the fragmentation method.

The embodiment of the present invention further provides a computer readable storage medium storing computer executable instructions, which when executed by a processor, implement the link management protocol applied to the second node as described above. Negotiate the fragmentation method.

Although alternative embodiments of the invention have been disclosed for illustrative purposes, those skilled in the art will appreciate that various modifications, additions and substitutions are also possible, and thus the scope of the invention should not be limited to the embodiments described above.

At the end of the embodiment, a set of phrases is added, for example, "It is understood by those skilled in the art that all or some of the steps, systems, and functional modules/units in the methods disclosed above may be implemented as software, firmware, hardware, and a suitable combination thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical units; for example, one physical component may have multiple functions, or one function or The steps may be performed cooperatively by a number of physical components. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as ASIC. Such software may be distributed on a computer readable medium, which may include computer storage media (or non-transitory media) and communication media (or transitory media), as is known to those of ordinary skill in the art. The term computer storage medium includes storage for information (such as computer readable reference) Volatile and non-volatile, removable and non-removable media implemented in any method or technology, data structure, program module or other data. Computer storage media including, but not limited to, RAM, ROM, EEPROM, flash memory Or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic box, magnetic tape, magnetic disk storage or other magnetic storage device, or any other that can be used to store desired information and can be accessed by a computer Further, it is well known to those skilled in the art that communication media typically includes computer readable instructions, data structures, program modules or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and can include any information. Delivery medium.

Claims

A negotiation fragmentation method for a link management protocol, including:

The first node sends a configuration message to the second node, where the configuration message carries a first packet negotiation length value (S201);

When the first node receives the configuration pass message sent by the second node, the first node packages the predetermined packet according to the first packet negotiation length value, and the packaged device is packaged. The predetermined message is sent to the second node (S202).
The negotiation fragmentation method according to claim 1, wherein, in the case that the first node receives the configuration pass message sent by the second node, the first node negotiates the length according to the first packet. The value is used to package the predetermined message, and the packaged predetermined message is sent to the second node (S202), including:

When the first node receives the configuration pass message sent by the second node, the first node determines whether the second message negotiation length value is included in the configuration pass message;

When the configuration pass message does not include the second packet negotiation length value, the first node packages the predetermined packet according to the first packet negotiation length value, and the packetized the predetermined request Sending a message to the second node;

When the configuration pass message includes the second packet negotiation length value, the first node packages the predetermined packet according to the second packet negotiation length value, and the packaged A predetermined message is sent to the second node.
The method for negotiating fragmentation according to claim 1, further comprising:

After the first node sends the configuration message to the second node, the first node receives the configuration fail message sent by the second node;

If the third packet negotiation length value is included in the configuration fail message, the first node determines whether the third packet negotiation length value is within a first preset range;

When the third packet negotiation length value is in the first preset range, the first node sends a configuration message to the second node, where the configuration message carries the third packet. Negotiate the length value;

The first node performs an alarm if the third message negotiation length value is not within the first preset range.
The method for negotiating fragmentation according to any one of claims 1 to 3, further comprising:

Before the first node sends the configuration message to the second node, the first node packages the test packet according to the maximum test packet length, and sends the packaged test packet to the second node.

The first node monitors a sending success rate of the test packet;

Receiving, by the first node, the preset maximum packet length according to the transmission success rate, until the sending success rate of the test packet is greater than a preset sending success rate;

The first node uses the current maximum test packet length as the first packet negotiation length value.
A negotiation fragmentation method for a link management protocol, including:

The second node receives the configuration message sent by the first node, where the configuration message carries the first packet negotiation length value (S301);

Determining, by the second node, whether the first packet negotiation length value is within a second preset range (S302);

And if the first packet negotiation length value is within the second preset range, sending a configuration pass message to the first node (S303).
The negotiation fragmentation method according to claim 5, wherein the configuration pass message includes a second message negotiation length value.
The method for negotiating fragmentation according to claim 5 or 6, further comprising:

After the second node determines whether the first packet negotiation length value is within the second preset range, if the first packet negotiation length value is not within the second preset range, the second node The first node sends a configuration fail message, where the configuration fail message includes a third packet negotiation length value.
A negotiation fragmentation device for a link management protocol, comprising:

The configuration message sending module (401) is configured to send a configuration message to the second node, where the configuration message carries a first packet negotiation length value;

The first receiving module (402) is configured to: when receiving the configuration passing message sent by the second node, packing the predetermined packet according to the first packet negotiation length value;

The first sending module (403) is configured to send the packaged predetermined message to the second node.
The negotiation fragmentation apparatus of claim 8, wherein the first receiving module (402) comprises:

The first determining unit (4021) is configured to determine, when the configuration pass message sent by the second node is received, whether the second message negotiation length value is included in the configuration pass message;

The packetizing unit (4022) is configured to: when the configuration packet passing message does not include the second packet negotiation length value, packetizing the predetermined packet according to the first packet negotiation length value; If the message includes the second packet negotiation length value, the predetermined packet is encapsulated according to the second packet negotiation length value.
The negotiated sharding apparatus of claim 8 further comprising:

a second receiving module, configured to receive a configuration fail message sent by the second node;

The first judging module is configured to determine whether the third packet negotiation length value is within the first preset range if the third packet negotiation length value is included in the configuration fail message;

The alarm module is configured to perform an alarm if the third message negotiation length value is not within the first preset range;

The configuration message sending module (401) is further configured to send a configuration message to the second node if the third packet negotiation length value is within the first preset range, where The configuration message carries a third packet negotiation length value.
The device for negotiating a slice according to any one of claims 8 to 10, further comprising:

The monitoring module is configured to package the test packet according to the maximum test packet length, and send the packaged test packet to the second node;

Monitoring a success rate of sending the test message;

Receiving, according to the transmission success rate, the preset test maximum packet length, until the sending success rate of the test packet is greater than a preset transmission success rate;

The current preset maximum test packet length is used as the first packet negotiation length value.
A negotiation fragmentation device for a link management protocol, comprising:

The configuration message receiving module (501) is configured to receive a configuration message sent by the first node, where the configuration message has a first packet negotiation length value;

The second determining module (502) is configured to determine whether the first packet negotiation length value is within a second preset range;

The second sending module (503) is configured to send a configuration pass message to the first node if the first packet negotiation length value is within a second preset range.
The negotiation fragmentation apparatus of claim 12, wherein the configuration pass message includes a second message negotiation length value.
A negotiation sharding apparatus according to claim 12 or 13, wherein

The second sending module (503) is further configured to send a configuration fail message to the first node if the first packet negotiation length value is not in the second preset range, where The third packet negotiation length value is included in the configuration fail message.
A computer readable storage medium storing computer executable instructions that, when executed by a processor, implement a negotiated fragmentation method of the link management protocol of any one of claims 1 to 4.
A computer readable storage medium storing computer executable instructions that, when executed by a processor, implement a negotiated fragmentation method of the link management protocol of any one of claims 5-7.