WO2016161784A1 - 一种降低链路管理协议中消息拥塞的方法及装置 - Google Patents

一种降低链路管理协议中消息拥塞的方法及装置 Download PDF

Info

Publication number
WO2016161784A1
WO2016161784A1 PCT/CN2015/090949 CN2015090949W WO2016161784A1 WO 2016161784 A1 WO2016161784 A1 WO 2016161784A1 CN 2015090949 W CN2015090949 W CN 2015090949W WO 2016161784 A1 WO2016161784 A1 WO 2016161784A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
node
retransmission
resendintervalconfig
retransmission interval
Prior art date
Application number
PCT/CN2015/090949
Other languages
English (en)
French (fr)
Inventor
吴海生
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016161784A1 publication Critical patent/WO2016161784A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/08Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems

Definitions

  • the present invention relates to the field of data network communications, and in particular, to a method and apparatus for reducing message congestion in a link management protocol.
  • LMP Link Management Protocol
  • IPCC IP Control
  • 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.
  • TE Traffic Engineering
  • the messages in the LMP protocol are all UDP (User Datagram Protocol) messages, and there is a possibility of packet loss. Therefore, it is also specified in RFC4204: after the message of confirming Ack (Acknowledgement) is sent.
  • the retransmission setting of the message needs to be set, that is, the message retransmission interval and the number of retransmissions are set, and the message retransmission needs to be continuously performed before the retransmission number expires.
  • a node in the LMP may have multiple neighbors.
  • the message that needs to be retransmitted is more than the received retransmission message, and the amount of message interaction is relatively large. Because the number of messages is too large, the Ack message sent to the neighbor or the message responding to the neighbor is not processed in time. If the neighbor neighbor does not receive the Ack message, the retransmission message will be sent periodically, so that the message of the node is sent. Further, it has almost doubled, cycled back and forth, resulting in a vicious circle, causing congestion on the network, and the control message is not refreshed in time, which causes the control plane to oscillate and affect the stability of the entire network.
  • An object of the embodiments of the present invention is to provide a message for reducing message congestion in a link management protocol.
  • the method and the device can determine the retransmission interval and the number of retransmissions when the message is transmitted between the nodes, reduce the risk of message congestion on the node, and improve the stability of the network transmission.
  • the embodiment of the invention provides a method for reducing message congestion in a link management protocol, which is applied to a first node side, and the method includes:
  • the method before the sending, by the second node, the link management protocol configuration Config message that carries the retransmission interval configuration parameter ResendIntervalConfig, the method further includes:
  • the retransmission interval configuration parameter ResendIntervalConfig is set, and the retransmission interval configuration parameter ResendIntervalConfig includes at least: a retransmission interval R and a retransmission number C.
  • the method further includes:
  • Determining a message type of the response message when the response message is a configuration confirmation ConfigAck message, determining that the response message is a negotiation confirmation message of the second node; and when the response message is a configuration negative ConfigNack message, extracting The parameter in the response message is decoded.
  • the decoded parameter includes the rewritten retransmission interval configuration parameter ResendIntervalConfig, it is determined that the response message is a negotiation failure message of the second node.
  • the response message is a ConfigNack message
  • the parameter in the response message is extracted for decoding.
  • the decoded parameter includes an error code Error_Code object, it is determined that the second node does not support retransmission mechanism negotiation.
  • the embodiment of the invention further provides a method for reducing message congestion in a link management protocol, which is applied to a second node side, and the method includes:
  • the retransmission interval configuration parameter ResendIntervalConfig is saved, and a negotiation confirmation message is sent to the first node; or a negotiation failure message including a preset retransmission interval configuration parameter ResendIntervalConfig is sent to the first node.
  • the step of saving a retransmission interval configuration parameter ResendIntervalConfig, and sending a negotiation confirmation message to the first node includes:
  • the step of sending a negotiation fail message including the preset retransmission interval configuration parameter ResendInterval Config to the first node includes:
  • a negotiation fail message including a preset retransmission interval configuration parameter ResendIntervalConfig is sent to the first node.
  • the method After the step of receiving the link management protocol configuration Config message that is sent by the first node and carrying the retransmission interval configuration parameter ResendIntervalConfig, the method also includes:
  • the embodiment of the invention further provides an apparatus for reducing message congestion in a link management protocol, which is applied to a first node side, and the apparatus includes:
  • the first sending module is configured to send, to the second node, a link management protocol configuration Config message carrying a retransmission interval configuration parameter ResendIntervalConfig;
  • a first processing module configured to receive a response message fed back by the second node, and when the response message is a negotiation confirmation message of the second node, configure a weight set in the Config message by using the link management protocol
  • the transmission interval configuration parameter is a standard for sending a message to the second node; when the response message is a negotiation failure message of the second node, the parameter ResendIntervalConfig is configured by using a retransmission interval set in the negotiation failure message. Sending a message to the second node is based on the negotiation being successful.
  • the device further includes:
  • the setting module is set to set a retransmission interval configuration parameter ResendIntervalConfig, where the retransmission interval configuration parameter ResendIntervalConfig includes at least: a retransmission interval R and a retransmission number C.
  • the first processing module is further configured to:
  • Determining a message type of the response message when the response message is a configuration confirmation ConfigAck message, determining that the response message is a negotiation confirmation message of the second node; and when the response message is a configuration negative ConfigNack message, extracting The parameter in the response message is decoded.
  • the decoded parameter includes the rewritten retransmission interval configuration parameter ResendIntervalConfig, it is determined that the response message is a negotiation failure message of the second node.
  • the first processing module is further configured to: after determining that the response message is a ConfigNack message, extract a parameter in the response message for decoding, when the decoded parameter includes an error code Error_Code object, Then determining that the second node does not support retransmission mechanism negotiation.
  • the embodiment of the present invention further provides a device for reducing message congestion in a link management protocol, which is applied to a second node side, and the device includes:
  • the first receiving module is configured to receive the carrying retransmission interval configuration parameter sent by the first node ResendIntervalConfig link management protocol configuration Config message;
  • a second processing module configured to save a retransmission interval configuration parameter ResendIntervalConfig, and send a negotiation confirmation message to the first node; or send a negotiation failure to the first node that includes a preset retransmission interval configuration parameter ResendIntervalConfig Message.
  • the second processing module includes:
  • a first extracting unit configured to extract a first retransmission interval R1 and a first retransmission number C1 set in a retransmission interval configuration parameter ResendIntervalConfig sent by the first node;
  • the first comparing unit is configured to set the second retransmission interval R2 and the second retransmission number C2 in the preset retransmission interval configuration parameter ResendIntervalConfig with the retransmission interval configuration parameter ResendIntervalConfig of the first node.
  • the variation value of the interval fluctuation coefficient, ⁇ n represents the variation value of the fluctuation coefficient of the number of retransmissions, and the range of ⁇ m and ⁇ n is between [0 to 50%);
  • the first saving unit is configured to save the first retransmission interval R1 and the first retransmission number C1 set in the retransmission interval configuration parameter ResendIntervalConfig sent by the first node;
  • the first sending unit is configured to send a negotiation confirmation message to the first node.
  • the second processing module further includes:
  • a second extracting unit configured to extract a first retransmission interval R1 and a first retransmission number C1 set in a retransmission interval configuration parameter ResendIntervalConfig sent by the first node;
  • the second comparing unit is configured to set the second retransmission interval R2 and the second retransmission number C2 in the preset retransmission interval configuration parameter ResendIntervalConfig with the retransmission interval configuration parameter ResendIntervalConfig of the first node.
  • the second sending unit is configured to send, to the first node, a negotiation fail message including a preset retransmission interval configuration parameter ResendIntervalConfig.
  • the device further includes: a third processing module, configured to: after receiving the link management protocol configuration Config message that is sent by the first node and carrying the retransmission interval configuration parameter ResendIntervalConfig, replying to the first node The error message of the error code object, through the error The code object indicates to the first node that the second node does not support retransmission mechanism negotiation.
  • a third processing module configured to: after receiving the link management protocol configuration Config message that is sent by the first node and carrying the retransmission interval configuration parameter ResendIntervalConfig, replying to the first node The error message of the error code object, through the error The code object indicates to the first node that the second node does not support retransmission mechanism negotiation.
  • the beneficial effects of the embodiment of the present invention are: determining the retransmission interval and the number of retransmissions of the message transmission between the nodes by negotiating the message between the nodes, and determining the standard retransmission interval and the number of retransmissions.
  • the transmission of the message in order to better control the transmission of the message, reduce the risk of message congestion on the node and improve the stability of the network transmission within a controllable range.
  • the embodiment of the present invention further provides a simple network authentication method, that is, performing simple network authentication by supporting retransmission mechanism negotiation, without adding a complex authentication object and an authentication policy algorithm.
  • FIG. 1 is a flow chart showing the steps of a method for reducing message congestion in a link reduction protocol applied to a first node side according to an embodiment of the present invention
  • FIG. 2 is a flowchart showing an overall method for reducing message congestion in a link management protocol applied to a first node side according to an embodiment of the present invention
  • FIG. 3 is a flow chart showing the steps of a method for reducing message congestion in a link management protocol applied to a second node side according to an embodiment of the present invention
  • FIG. 4 is a flow chart showing the steps of sending a negotiation confirmation message in a method for reducing message congestion in a link management protocol on a second node side according to an embodiment of the present invention
  • FIG. 5 is a flow chart showing the steps of sending a negotiation fail message in a method for reducing message congestion in a link management protocol according to an embodiment of the present invention
  • FIG. 6 is a flowchart showing an overall method for reducing message congestion in a link management protocol applied to a second node side according to an embodiment of the present invention
  • FIG. 7 is a topological diagram showing a message transmitted by a first node and a second node on a control channel according to an embodiment of the present invention
  • FIG. 8 is a block diagram of an apparatus for reducing message congestion in a link reduction protocol applied to a first node side according to an embodiment of the present invention
  • FIG. 9 is a block diagram showing an apparatus for reducing message congestion in a link reduction protocol applied to a second node side according to an embodiment of the present invention.
  • FIG. 10 is a block diagram 1 of a second processing module in an apparatus for reducing message congestion in a link management protocol on a second node side according to an embodiment of the present invention
  • FIG. 11 is a block diagram 2 showing a second processing module in an apparatus for reducing message congestion in a link management protocol according to an embodiment of the present invention.
  • an embodiment of the present invention provides a method for reducing message congestion in a link management protocol, which is applied to a first node side, and the method includes:
  • Step S100 Send a link management protocol configuration Config message carrying a retransmission interval configuration parameter ResendIntervalConfig to the second node.
  • Step S200 Receive a response message fed back by the second node, and when the response message is a negotiation confirmation message of the second node, configure a retransmission interval configuration parameter set in the Config message by using the link management protocol. Sending a message to the second node as a standard; when the response message is a negotiation failure message of the second node, using the retransmission interval configuration parameter ResendIntervalConfig set in the negotiation failure message as a basis The second node sends a message until the negotiation is successful.
  • the link management protocol configuration Config message carrying the retransmission interval configuration parameter ResendIntervalConfig is sent to the second node. It should be noted that sending the link management protocol configuration Config message to the second node increases the retransmission interval configuration parameter ResendIntervalConfig compared to the original Config message.
  • the format is as follows:
  • the response message sent back by the second node is received.
  • the response message is the negotiation confirmation message of the second node, it indicates that the retransmission interval configuration parameter ResendIntervalConfig carried in the sent link management protocol configuration Config message meets the requirements of the second node.
  • the negotiation with the second node is successful.
  • the parameters carried by the second node are all The successful retransmission interval configuration parameter ResendIntervalConfig.
  • the response message is the negotiation failure message of the second node, it indicates that the retransmission interval configuration parameter ResendIntervalConfig carried in the sent link management protocol configuration Config message does not meet the requirements of the second node, and the negotiation with the second node is unsuccessful. .
  • the method before the sending, by the second node, the link management protocol configuration Config message carrying the retransmission interval configuration parameter ResendIntervalConfig, the method further includes:
  • the retransmission interval configuration parameter ResendIntervalConfig is set, and the retransmission interval configuration parameter ResendIntervalConfig includes at least: a retransmission interval R and a retransmission number C.
  • the ResendIntervalConfig parameter includes the retransmission interval ResendInterval of the message and the number of retransmissions of the message ResendNumber.
  • the format is as follows:
  • ResendInterval 16bits. (>0)
  • the retransmission interval identifies the interval at which the message is retransmitted on the node.
  • ResendNumber 16bits. (>0)
  • the number of retransmissions identifies how many times the message can be retransmitted on the node.
  • the retransmission negotiation function on the first node can be turned on or off. When re-transmission negotiation with other nodes is required, this function is enabled. When the retransmission negotiation is not required, the function is disabled. Before sending the link management protocol configuration Config message, you need to configure the control channel. Set to ensure the transmission stability of the control channel.
  • the method further includes:
  • Determining a message type of the response message when the response message is a ConfigAck message, determining that the response message is a negotiation confirmation message of the second node; and when the response message is a ConfigNack message, extracting the response message
  • the parameter in the decoding is performed.
  • the decoded parameter includes the rewritten retransmission interval configuration parameter ResendIntervalConfig, it is determined that the response message is a negotiation failure message of the second node.
  • the response message After receiving the response message fed back by the second node, it is necessary to distinguish the categories of the response message to determine what operations will be performed below.
  • the response message is a ConfigAck message, it indicates that the response message is a negotiation confirmation message of the second node, and the negotiation with the second node succeeds.
  • the type of the response message is a ConfigNack message, the parameter in the response message needs to be extracted for decoding.
  • the decoded parameter includes the rewritten retransmission interval configuration parameter ResendIntervalConfig
  • the response message indicates that the second node does not negotiate. Through the message, the negotiation with the second node fails, and the second node feeds back the suggested retransmission interval configuration parameter ResendIntervalConfig.
  • the re-transmission interval configuration parameter ResendIntervalConfig or the error code Error_Code object is added to the ConfigNack message replied by the second node. Its format is as follows:
  • the step of determining the message type of the response message when the response message is a ConfigNack message, extracting parameters in the response message for decoding, when the decoded parameter includes an error code
  • the Error_Code object is determined, it is determined that the second node does not support retransmission mechanism negotiation.
  • the parameter in the response message needs to be extracted for decoding.
  • the decoded parameter includes only an error code Error_Code object, it indicates that the second node does not support the negotiation of the retransmission mechanism. The secondary negotiation fails and the control channel cannot take effect. Its
  • FIG. 2 it is a flowchart of the overall steps of a method for reducing message congestion in a link management protocol on a first node side according to an embodiment of the present invention:
  • Step S101 Start a retransmission function.
  • Step S102 Set a retransmission interval configuration parameter ResendIntervalConfig.
  • Step S103 Send a link management protocol configuration Config message carrying the retransmission interval configuration parameter ResendIntervalConfig to the second node.
  • Step S104 Receive a response message, determine whether the response message is a ConfigAck message, and if it is a ConfigAck message, the retransmission interval configuration parameter ResendIntervalConfig of the subsequent message is the configured transmission interval configuration parameter ResendIntervalConfig, if not, proceed to the next step. .
  • Step S105 Determine whether the response message is a ConfigNACK message, if not, process according to a normal protocol, and if yes, proceed to the next step.
  • Step S106 Determine whether the ConfigNACK message includes an error code Error_Code object. If it is included, it indicates that the second node does not support the retransmission mechanism negotiation, and performs processing according to the normal protocol. If not, the next step is performed.
  • Step S107 Determine whether the re-transmission interval configuration parameter ResendIntervalConfig is included in the ConfigNACK message. If not, the processing is performed according to the normal protocol. If yes, the process returns to step S102 to set the retransmission interval configuration parameter ResendIntervalConfig. It should be noted that the retransmission interval configuration parameter ResendIntervalConfig set at this time is a retransmission retransmission. The interval configuration parameter ResendIntervalConfig is then sent to the second node.
  • the embodiment of the present invention further provides a method for reducing message congestion in a link management protocol, which is applied to a second node side. As shown in FIG. 3, the method includes:
  • Step S300 Receive a link management protocol configuration Config message that is sent by the first node and carries a retransmission interval configuration parameter ResendIntervalConfig.
  • Step S400 Save a retransmission interval configuration parameter ResendIntervalConfig, and send a negotiation confirmation message to the first node; or send a negotiation failure message including a preset retransmission interval configuration parameter ResendIntervalConfig to the first node.
  • the link management protocol configuration Config message of the retransmission interval configuration parameter ResendIntervalConfig sent by the first node is received, and the retransmission interval configuration parameter ResendIntervalConfig is negotiated. After the negotiation succeeds, the link management protocol configuration Config message sent by the first node is saved. The retransmission interval configuration parameter ResendIntervalConfig is included, and a message of negotiation confirmation is sent to the first node. If the negotiation is unsuccessful, the negotiation fails to send a negotiation failure message to the first node, where the negotiation failure message includes the retransmission interval configuration parameter preset by the second node, and the second node preset retransmission interval configuration The parameter is sent to the first node as a suggested value.
  • the step of saving the retransmission interval configuration parameter ResendIntervalConfig in the step S400, and sending a negotiation confirmation message to the first node, as shown in FIG. 4, includes:
  • Step S401 extracting a first retransmission interval R1 and a first retransmission number C1 set in a retransmission interval configuration parameter ResendIntervalConfig sent by the first node;
  • Step S402 the first retransmission interval R2 and the second retransmission number C2 in the preset retransmission interval configuration parameter ResendIntervalConfig are the first retransmission set in the retransmission interval configuration parameter ResendIntervalConfig of the first node.
  • the interval R1 is compared with the first number of retransmissions C1.
  • a change value indicating a change value of a fluctuation coefficient of the ⁇ n retransmission times, and a range of ⁇ m and ⁇ n is between [0 to 50%);
  • Step S403 saving the first retransmission interval R1 and the first retransmission number C1 set in the retransmission interval configuration parameter ResendIntervalConfig sent by the first node;
  • Step S404 sending a negotiation confirmation message to the first node.
  • the first retransmission interval R1 and the first retransmission number C1 set in the retransmission interval configuration parameter ResendIntervalConfig sent by the first node are obtained, and then the first retransmission interval R1 and the first weight are obtained.
  • ⁇ m and ⁇ n are pre-configured default values, and the variation values of the fluctuation coefficients selected within the receivable range coefficients.
  • the step of transmitting a negotiation failure message including the preset retransmission interval configuration parameter ResendIntervalConfig to the first node in step S400, as shown in FIG. 5, includes:
  • Step S405 extracting the first retransmission interval R1 and the first retransmission number C1 set in the retransmission interval configuration parameter ResendIntervalConfig sent by the first node;
  • Step S406 the first retransmission interval R2 and the second retransmission number C2 in the preset retransmission interval configuration parameter ResendIntervalConfig and the first retransmission set in the retransmission interval configuration parameter ResendIntervalConfig of the first node
  • Step S407 Send a negotiation failure message including a preset retransmission interval configuration parameter ResendIntervalConfig to the first node.
  • the method further includes:
  • a response message containing an error code object is sent to the first node.
  • the retransmission interval configuration parameter ResendIntervalConfig in the link management protocol configuration Config message may not be processed, and the first node does not receive the response message fed back by the node within a certain period of time. Then it is determined that the node does not support retransmission mechanism negotiation.
  • FIG. 6 it is a flowchart of the overall steps of a method for reducing message congestion in a link management protocol on a second node side according to an embodiment of the present invention:
  • Step S201 Receive a link management protocol configuration Config message, and determine whether the retransmission interval configuration parameter ResendIntervalConfig is carried in the message. If not, the processing is performed according to a normal protocol, and if it is carried, the next step is performed.
  • Step S202 Determine whether the node supports retransmission mechanism negotiation. If not, proceed to step S203. If yes, proceed to step S204.
  • Step S203 Determine whether to ignore the processing of configuring the Config message for the link management protocol, and if so, ignore the retransmission interval configuration parameter ResendIntervalConfig; if not, reply with the ConfigNack message containing the Error_Code object.
  • Step S204 Obtain a first retransmission interval R1 and a first retransmission number C1 in the retransmission interval configuration parameter ResendIntervalConfig.
  • Step S206 replying to the ConfigAck message, indicating that the negotiation is successful.
  • Step S207 replying to the ConfigNack message, indicating that the negotiation fails, carrying the retransmission interval Set the parameter ResendIntervalConfig to write the recommended value of the retransmission parameter of this node.
  • monitoring management is set on the control channel for sending and receiving messages.
  • the link management protocol configuration Config message sent by the first node and the received response message exceed the set threshold on the control channel CC1.
  • the embodiment of the present invention further provides an apparatus for reducing message congestion in a link management protocol, which is applied to a first node side.
  • the apparatus includes:
  • the first sending module 20 is configured to send, to the second node, a link management protocol configuration Config message carrying a retransmission interval configuration parameter ResendIntervalConfig;
  • the first processing module 30 is configured to receive a response message fed back by the second node, and when the response message is a negotiation confirmation message of the second node, configure the Config message in the link management protocol.
  • the retransmission interval configuration parameter is a standard for sending a message to the second node; when the response message is a negotiation failure message of the second node, configuring parameters by using a retransmission interval set in the negotiation failure message ResendIntervalConfig is based on sending a message to the second node until the negotiation is successful.
  • the device further includes:
  • the setting module 10 is configured to set a retransmission interval configuration parameter ResendIntervalConfig, where the retransmission interval configuration parameter ResendIntervalConfig includes at least: a retransmission interval R and a retransmission number C.
  • the first processing module 30 is optionally set to:
  • Determining a message type of the response message when the response message is a ConfigAck message, determining that the response message is a negotiation confirmation message of the second node; when the response message is The ConfigNack message is used to extract the parameters in the response message for decoding.
  • the decoded parameter includes the rewritten retransmission interval configuration parameter ResendIntervalConfig
  • the response message is determined to be the negotiation failure message of the second node.
  • the first processing module 30 is further configured to:
  • the parameter in the response message is extracted for decoding.
  • the decoded parameter includes an error code Error_Code object, it is determined that the second node does not support retransmission mechanism negotiation.
  • the embodiment of the present invention further provides a device for reducing message congestion in a link management protocol, which is applied to a second node side.
  • the device includes:
  • the first receiving module 40 is configured to receive a link management protocol configuration Config message that is sent by the first node and that carries a retransmission interval configuration parameter ResendIntervalConfig.
  • the second processing module 50 is configured to save the retransmission interval configuration parameter ResendIntervalConfig, and send a negotiation confirmation message to the first node; or send a negotiation including the preset retransmission interval configuration parameter ResendIntervalConfig to the first node. Through the message.
  • the second processing module 50 includes:
  • the first extracting unit 51 is configured to extract the first retransmission interval R1 and the first retransmission number C1 set in the retransmission interval configuration parameter ResendIntervalConfig sent by the first node;
  • the first comparing unit 52 is configured to set the second retransmission interval R2 and the second retransmission number C2 in the preset retransmission interval configuration parameter ResendIntervalConfig and the retransmission interval configuration parameter ResendIntervalConfig of the first node.
  • the first retransmission interval R1 is compared with the first retransmission number C1.
  • the first saving unit 53 is configured to save the first retransmission interval R1 and the first retransmission number C1 set in the retransmission interval configuration parameter ResendIntervalConfig sent by the first node;
  • the first sending unit 54 is configured to send a negotiation confirmation message to the first node.
  • the second processing module 50 further includes:
  • the second extracting unit 55 is configured to extract the first retransmission interval R1 and the first retransmission interval C1 set in the retransmission interval configuration parameter ResendIntervalConfig sent by the first node;
  • the second comparison unit 56 is configured to set the second retransmission interval R2 and the second retransmission number C2 in the preset retransmission interval configuration parameter ResendIntervalConfig and the retransmission interval configuration parameter ResendIntervalConfig of the first node.
  • the second sending unit 57 is configured to send a negotiation fail message including the preset retransmission interval configuration parameter ResendIntervalConfig to the first node.
  • the device after receiving the link management protocol configuration Config message of the retransmission interval configuration parameter ResendIntervalConfig sent by the first node, as shown in FIG. 9, the device further includes:
  • the third processing module 60 is configured to reply to the first node with a response message including an error code object, and indicate, by the error code object, the first node that the second node does not support retransmission mechanism negotiation.
  • the retransmission interval and the number of retransmissions of the message transmission between the nodes are determined through negotiation of the message between the nodes to determine the standard retransmission interval. And the number of retransmissions is used as the basis for message transmission, so as to better control the transmission of the message, reduce the risk of message congestion on the node and improve the stability of the network transmission within a controllable range.
  • the message retransmission is adjusted when the node will be congested, further reducing the risk of message congestion.
  • a simple network authentication method is provided, that is, simple network authentication is performed by whether or not the retransmission mechanism is supported, and no complicated authentication object and authentication policy algorithm need to be added.
  • the apparatus for reducing message congestion in the link management protocol provided by the embodiment of the present invention is a device applying the foregoing method, and all embodiments of the foregoing method are applicable to the device, and both can achieve the same or similar benefits. effect.
  • all or part of the steps of the above embodiments may also be implemented using an integrated circuit.
  • the steps may be separately fabricated into individual integrated circuit modules, or a plurality of modules or steps may be fabricated into a single integrated circuit module.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • each device/function module/functional unit in the above embodiment When each device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the retransmission interval and the number of retransmissions of the message transmission between the nodes are determined through negotiation of the message between the nodes, and the message is transmitted according to the standard retransmission interval and the number of retransmissions. It can better control the transmission of packets, reduce the risk of message congestion on the nodes and improve the stability of network transmission within a controllable range.
  • the embodiment of the present invention further provides a simple network authentication method, that is, performing simple network authentication by supporting retransmission mechanism negotiation, without adding a complex authentication object and an authentication policy algorithm.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Communication Control (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种降低链路管理协议中消息拥塞的方法及装置,其中应用于第一节点侧的降低链路管理协议中消息拥塞的方法包括:向第二节点发送携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息;接收第二节点反馈的回应消息,当回应消息为第二节点的协商确认消息时,以链路管理协议配置Config消息中设定的重传间隔配置参数为标准向第二节点发送消息;当回应消息为第二节点的协商不通过消息时,以协商不通过消息中设定的重传间隔配置参数ResendIntervalConfig为依据向第二节点发送消息,直至协商成功。通过确定消息在节点之间传递时的重传间隔和重传次数,在可控的范围内,降低节点上消息拥塞的风险,提高网络传输的稳定性。

Description

一种降低链路管理协议中消息拥塞的方法及装置 技术领域
本发明涉及数据网络通讯领域,尤其涉及一种降低链路管理协议中消息拥塞的方法及装置。
背景技术
在当前GMPLS协议族(Generalized multi-protocol label switching,通用多协议标记交互协议)中,LMP(Link Management Protocol,链路管理协议)用来管理节点之间的链路以及控制通道(IPCC:IP Control Channel)管理。
LMP的功能包括控制通道管理、链路属性关联、链路连通性验证和故障管理。其中前两项用于管理流量工程(TE:Traffic Engineering),是链路必备的核心功能;后两项是可选的扩展功能,用于应对控制通道与数据通道分离的情况。
LMP协议中的消息都是UDP(User Datagram Protocol,用户数据报协议)消息,存在丢包的可能性,因此RFC4204中也作了规定:当需要进行确认Ack(Acknowledgement,确认字符)的消息发送之后,需要对该消息进行重传设置,即设置消息重传间隔以及重传次数,在重传次数到期之前,需要不停的进行消息重传。
LMP中的节点可能存在多个邻居,需要重传的消息和收到的重传消息比较多,消息交互量比较大。由于消息比较多,导致发向邻居的Ack消息或者响应邻居的消息得不到及时处理,那么周围邻居由于收不到Ack消息,会周期性的发送重传消息过来,这样一来本节点的消息又进一步的几乎加大了一倍,循环往复,导致恶性循环,造成网络上消息的拥塞,控制报文得不到及时的刷新,进而使得控制平面发生震荡,影响整个网络的稳定。
发明内容
本发明实施例的目的在于提供一种降低链路管理协议中消息拥塞的 方法及装置,可以确定消息在节点之间传递时的重传间隔和重传次数,降低节点上消息拥塞的风险,提高网络传输的稳定性。
本发明实施例提供一种降低链路管理协议中消息拥塞的方法,应用于第一节点侧,所述方法包括:
向第二节点发送携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息;
接收所述第二节点反馈的回应消息,当所述回应消息为所述第二节点的协商确认消息时,以所述链路管理协议配置Config消息中设定的重传间隔配置参数为标准向所述第二节点发送消息;当所述回应消息为所述第二节点的协商不通过消息时,以所述协商不通过消息中设定的重传间隔配置参数ResendIntervalConfig为依据向所述第二节点发送消息,直至协商成功。
可选地,所述向第二节点发送携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息之前,所述方法还包括:
设定重传间隔配置参数ResendIntervalConfig,其中重传间隔配置参数ResendIntervalConfig中至少包括:重传间隔R和重传次数C。
可选地,所述接收所述第二节点反馈的回应消息之后,所述方法还包括:
判断所述回应消息的消息类型,当所述回应消息为配置确认ConfigAck消息时,则确定所述回应消息为所述第二节点的协商确认消息;当所述回应消息为配置否定ConfigNack消息,提取所述回应消息中的参数进行解码,当解码后的参数包括重新写入的重传间隔配置参数ResendIntervalConfig时,则确定所述回应消息为所述第二节点的协商不通过消息。
可选地,在判断所述回应消息的消息类型的步骤中:
当所述回应消息为ConfigNack消息,提取所述回应消息中的参数进行解码,当解码后的参数包括一错误代码Error_Code对象时,则确定所述第二节点不支持重传机制协商。
本发明实施例还提供一种降低链路管理协议中消息拥塞的方法,应用于第二节点侧,所述方法包括:
接收第一节点发送的携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息;
保存重传间隔配置参数ResendIntervalConfig,并向所述第一节点发送协商确认消息;或者向所述第一节点发送包括预先设定的重传间隔配置参数ResendIntervalConfig的协商不通过消息。
可选地,所述保存重传间隔配置参数ResendIntervalConfig,并向所述第一节点发送协商确认消息的步骤,包括:
提取所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
将预先设定的重传间隔配置参数ResendIntervalConfig中的第二重传间隔R2和第二重传次数C2与所述第一节点的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1进行比较,当满足R1>=R2×(1-Δm)并且C1<=C2×(1+Δn)时,表明协商通过,其中Δm表示重传间隔波动系数的变化值,Δn表示重传次数波动系数的变化值,且Δm和Δn的范围在[0~50%)之间;
保存所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
向所述第一节点发送协商确认消息。
可选地,所述向所述第一节点发送包括预先设定的重传间隔配置参数ResendInterval Config的协商不通过消息的步骤,包括:
提取所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
将预先设定的重传间隔配置参数ResendIntervalConfig中的第二重传间隔R2和第二重传次数C2与所述第一节点的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1进行比较,当R1>=R2×(1-Δm)、C1<=C2×(1+Δn)两式中的任一个不满足时,表明协商不通过;
向所述第一节点发送包括预先设定的重传间隔配置参数ResendIntervalConfig的协商不通过消息。
可选地,所述接收第一节点发送的携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息的步骤之后,所述方法 还包括:
向所述第一节点回复包含错误代码对象的回应消息,通过所述错误代码对象向所述第一节点表明所述第二节点不支持重传机制协商。
本发明实施例还提供一种降低链路管理协议中消息拥塞的装置,应用于第一节点侧,所述装置包括:
第一发送模块,设置为向第二节点发送携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息;
第一处理模块,设置为接收所述第二节点反馈的回应消息,当所述回应消息为所述第二节点的协商确认消息时,以所述链路管理协议配置Config消息中设定的重传间隔配置参数为标准向所述第二节点发送消息;当所述回应消息为所述第二节点的协商不通过消息时,以所述协商不通过消息中设定的重传间隔配置参数ResendIntervalConfig为依据向所述第二节点发送消息,直至协商成功。
可选地,所述装置还包括:
设置模块,设置为设定重传间隔配置参数ResendIntervalConfig,其中重传间隔配置参数ResendIntervalConfig中至少包括:重传间隔R和重传次数C。
可选地,所述第一处理模块还设置为:
判断所述回应消息的消息类型,当所述回应消息为配置确认ConfigAck消息时,则确定所述回应消息为所述第二节点的协商确认消息;当所述回应消息为配置否定ConfigNack消息,提取所述回应消息中的参数进行解码,当解码后的参数包括重新写入的重传间隔配置参数ResendIntervalConfig时,则确定所述回应消息为所述第二节点的协商不通过消息。
可选地,所述第一处理模块还设置为:在判断出所述回应消息为ConfigNack消息后,提取所述回应消息中的参数进行解码,当解码后的参数包括一错误代码Error_Code对象时,则确定所述第二节点不支持重传机制协商。
本发明实施例还提供了一种降低链路管理协议中消息拥塞的装置,应用于第二节点侧,所述装置包括:
第一接收模块,设置为接收第一节点发送的携带重传间隔配置参数 ResendIntervalConfig的链路管理协议配置Config消息;
第二处理模块,设置为保存重传间隔配置参数ResendIntervalConfig,并向所述第一节点发送协商确认消息;或者向所述第一节点发送包括预先设定的重传间隔配置参数ResendIntervalConfig的协商不通过消息。
可选地,所述第二处理模块包括:
第一提取单元,设置为提取所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
第一比较单元,设置为将预先设定的重传间隔配置参数ResendIntervalConfig中的第二重传间隔R2和第二重传次数C2与所述第一节点的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1进行比较,当满足R1>=R2×(1-Δm)并且C1<=C2×(1+Δn)时,表明协商通过,其中Δm表示重传间隔波动系数的变化值,Δn表示重传次数波动系数的变化值,且Δm和Δn的范围在[0~50%)之间;
第一保存单元,设置为保存所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
第一发送单元,设置为向所述第一节点发送协商确认消息。
可选地,所述第二处理模块还包括:
第二提取单元,设置为提取所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
第二比较单元,设置为将预先设定的重传间隔配置参数ResendIntervalConfig中的第二重传间隔R2和第二重传次数C2与所述第一节点的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1进行比较,当R1>=R2×(1-Δm)、C1<=C2×(1+Δn)两式中的任一个不满足时,表明协商不通过;
第二发送单元,设置为向所述第一节点发送包括预先设定的重传间隔配置参数ResendIntervalConfig的协商不通过消息。
可选地,所述装置还包括:第三处理模块,设置为:在接收第一节点发送的携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息后,向所述第一节点回复包含错误代码对象的回应消息,通过所述错误 代码对象向所述第一节点表明所述第二节点不支持重传机制协商。
本发明实施例的有益效果是:通过节点之间往来消息的协商来确定节点之间消息传送的重传间隔和重传次数,以确定后的标准的重传间隔和重传次数为依据来进行消息的传送,以便能够更好的控制报文的发送,在可控的范围内,降低节点上消息拥塞的风险,提高网络传输的稳定性。
可选的,本发明实施例还提供了一套简单的网络认证方法,即通过是否支持重传机制协商来进行简单的网络认证,无需添加复杂的认证对象和认证策略算法。
附图概述
图1表示本发明实施例应用于第一节点侧的降低链路管理协议中消息拥塞的方法步骤流程图;
图2表示本发明实施例应用于第一节点侧的降低链路管理协议中消息拥塞的方法整体流程图;
图3表示本发明实施例应用于第二节点侧的降低链路管理协议中消息拥塞的方法步骤流程图;
图4表示本发明实施例应用于第二节点侧的降低链路管理协议中消息拥塞的方法中发送协商确认消息的步骤流程图;
图5表示本发明实施例应用于第二节点侧的降低链路管理协议中消息拥塞的方法中发送协商不通过消息的步骤流程图;
图6表示本发明实施例应用于第二节点侧的降低链路管理协议中消息拥塞的方法整体流程图;
图7表示本发明实施例第一节点和第二节点在控制通道上传输消息的拓扑图;
图8表示本发明实施例应用于第一节点侧的降低链路管理协议中消息拥塞的装置框图;
图9表示本发明实施例应用于第二节点侧的降低链路管理协议中消息拥塞的装置框图;
图10表示本发明实施例应用于第二节点侧的降低链路管理协议中消息拥塞的装置中第二处理模块的框图一;
图11表示本发明实施例应用于第二节点侧的降低链路管理协议中消息拥塞的装置中第二处理模块的框图二。
本发明的较佳实施方式
下面将结合附图及实施例对本发明进行详细描述。
如图1所示,本发明实施例提供一种降低链路管理协议中消息拥塞的方法,应用于第一节点侧,所述方法包括:
步骤S100、向第二节点发送携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息;
步骤S200、接收所述第二节点反馈的回应消息,当所述回应消息为所述第二节点的协商确认消息时,以所述链路管理协议配置Config消息中设定的重传间隔配置参数为标准向所述第二节点发送消息;当所述回应消息为所述第二节点的协商不通过消息时,以所述协商不通过消息中设定的重传间隔配置参数ResendIntervalConfig为依据向所述第二节点发送消息,直至协商成功。
首先向第二节点发送携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息。需要说明的是,与原有的Config消息相比,向第二节点发送链路管理协议配置Config消息增加了重传间隔配置参数ResendIntervalConfig。格式如下:
Config消息:
<Config Message>::=<Common Header> <LOCAL_CCID> <MESSAGE_ID>
                 <LOCAL_NODE_ID> <CONFIG>[<RESEND_INTERVAL_CONFIG>]
然后接收第二节点反馈回来的回应消息,当回应消息为第二节点的协商确认消息时,则表示发送的链路管理协议配置Config消息中携带的重传间隔配置参数ResendIntervalConfig符合第二节点的要求,与第二节点的协商成功。此后向第二节点发送链路管理协议配置Config消息时携带的参数均为协 商成功的重传间隔配置参数ResendIntervalConfig。当回应消息为第二节点的协商不通过消息时,则表明发送的链路管理协议配置Config消息中携带的重传间隔配置参数ResendIntervalConfig不符合第二节点的要求,与第二节点的协商不成功。接收协商不通过消息中设定的重传间隔配置参数ResendIntervalConfig,并以此为依据重新构造链路管理协议配置Config消息向第二节点发送,直至协商成功为止。
在本发明上述实施例中,所述向第二节点发送携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息之前,所述方法还包括:
设定重传间隔配置参数ResendIntervalConfig,其中重传间隔配置参数ResendIntervalConfig中至少包括:重传间隔R和重传次数C。
在进行发送携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息之前,还需要对重传间隔配置参数ResendIntervalConfig进行设定。ResendIntervalConfig参数中包括了消息的重传间隔ResendInterval和消息的重传次数ResendNumber。格式如下所示:
Class=6.
C-Type=2,ResendIntervalConfig
Figure PCTCN2015090949-appb-000001
ResendInterval:16bits.(>0)
重传间隔标识节点上消息重传的间隔。
ResendNumber:16bits.(>0)
重传次数标识节点上消息可以重传多少次。
需要说明的是,第一节点上的重传协商功能可以打开或关闭,当需要与其他节点进行重传协商时,打开此功能,当不需要进行重传协商时,关闭此功能。在发送链路管理协议配置Config消息之前,还需要对控制通道进行配 置,以确保控制通道的传输稳定性。
在本发明上述实施例中,所述接收所述第二节点反馈的回应消息之后,所述方法还包括:
判断所述回应消息的消息类型,当所述回应消息为ConfigAck消息时,则确定所述回应消息为所述第二节点的协商确认消息;当所述回应消息为ConfigNack消息,提取所述回应消息中的参数进行解码,当解码后的参数包括重新写入的重传间隔配置参数ResendIntervalConfig时,则确定所述回应消息为所述第二节点的协商不通过消息。
接收第二节点反馈的回应消息后,需要对回应消息的类别进行区分,以确定下面将执行哪些操作。当回应消息为ConfigAck消息时,则表明回应消息为第二节点的协商确认消息,与第二节点的协商成功。当回应消息的类型为ConfigNack消息时,则需要提取回应消息中的参数进行解码,当解码后的参数包括重新写入的重传间隔配置参数ResendIntervalConfig时,则表明回应消息为第二节点的协商不通过消息,与第二节点的协商失败,第二节点反馈了建议的重传间隔配置参数ResendIntervalConfig。需要说明的是,与原有的ConfigNack消息相比,第二节点回复的ConfigNack消息中增加了重新写入的重传间隔配置参数ResendIntervalConfig或者错误代码Error_Code对象。其格式如下:
<ConfigNack Message>::=<Common Header> <LOCAL_CCID>
                     <LOCAL_NODE_ID> <REMOTE_CCID>
                     <MESSAGE_ID_ACK> <REMOTE_NODE_ID> <CONFIG>
                     [<RESEND_INTERVAL_CONFIG>] [ERROR_CODE]
在本发明上述实施例中,在判断所述回应消息的消息类型的步骤中:当所述回应消息为ConfigNack消息,提取所述回应消息中的参数进行解码,当解码后的参数包括一错误代码Error_Code对象时,则确定所述第二节点不支持重传机制协商。
在确定了回应消息的类型为ConfigNack消息时,需要提取回应消息中的参数进行解码,当解码后的参数仅包括一错误代码Error_Code对象时,则表明第二节点不支持重传机制的协商,本次协商失败,控制通道不能生效。其 中,错误代码Error_Code对象增加了C-Type=0x40这个类型,其格式如下所示:
Class=20
C-Type=0x40,RESEND_INTERVAL_ERROR
Figure PCTCN2015090949-appb-000002
如图2所示,为本发明实施例第一节点侧降低链路管理协议中消息拥塞的方法的整体步骤流程图:
步骤S101、启动重传功能。
步骤S102、设定重传间隔配置参数ResendIntervalConfig。
步骤S103、向第二节点发送携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息。
步骤S104、接收回应消息,判断回应消息是否是ConfigAck消息,若是ConfigAck消息,则后续消息的重传发间隔配置参数ResendIntervalConfig均为已设定的发间隔配置参数ResendIntervalConfig,如果不是,则进行下一步骤。
步骤S105、判断回应消息是否是ConfigNACK消息,如果不是则按正常协议进行处理,如果是则进行下一步骤。
步骤S106、判断ConfigNACK消息中是否包含错误代码Error_Code对象,如果包含则表明第二节点不支持重传机制协商,按正常协议进行处理,如果不包含则进行下一步骤。
步骤S107、判断ConfigNACK消息中是否包含重新写入的重传间隔配置参数ResendIntervalConfig,如果不包括则按正常协议进行处理,如果包括则返回到步骤S102,设定重传间隔配置参数ResendIntervalConfig。需要说明的是,此时设定的重传间隔配置参数ResendIntervalConfig即为重新写入的重传 间隔配置参数ResendIntervalConfig,然后向第二节点发送。
本发明实施例还提供了一种降低链路管理协议中消息拥塞的方法,应用于第二节点侧,如图3所示,所述方法包括:
步骤S300、接收第一节点发送的携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息;
步骤S400、保存重传间隔配置参数ResendIntervalConfig,并向所述第一节点发送协商确认消息;或者向所述第一节点发送包括预先设定的重传间隔配置参数ResendIntervalConfig的协商不通过消息。
接收第一节点发送的携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息进行重传间隔配置参数ResendIntervalConfig的协商,当协商成功后,保存第一节点发送的链路管理协议配置Config消息中包含的重传间隔配置参数ResendIntervalConfig,并向第一节点发送协商确认的消息。若协商不成功时,则需要向第一节点发送协商不通过消息,其中协商不通过消息中包含了第二节点预先设定的重传间隔配置参数,第二节点预先设定的重传间隔配置参数作为一个建议值发送至第一节点。
在本发明上述实施例中,步骤S400中所述保存重传间隔配置参数ResendIntervalConfig,并向所述第一节点发送协商确认消息的步骤,如图4所示,包括:
步骤S401、提取所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
步骤S402、将预先设定的重传间隔配置参数ResendIntervalConfig中的第二重传间隔R2和第二重传次数C2与所述第一节点的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1进行比较,当满足R1>=R2×(1-Δm)并且C1<=C2×(1+Δn)时,表明协商通过,其中Δm表示重传间隔波动系数的变化值,表示Δn重传次数波动系数的变化值,且Δm和Δn的范围在[0~50%)之间;
步骤S403、保存所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
步骤S404、向所述第一节点发送协商确认消息。
判断协商是否成功时,首先需要获得第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1,然后将第一重传间隔R1和第一重传次数C1与本节点中预先设定的重传间隔配置参数ResendIntervalConfig中的第二重传间隔R2和第二重传次数C2进行比较,当第一重传间隔R1、第一重传次数C1、第二重传间隔R2和第二重传次数C2同时满足式一:R1>=R2×(1-Δm)和式二:C1<=C2×(1+Δn)时,表明协商成功,本节点将第一重传间隔R1和第一重传次数C1进行保存,最后向第一节点发送协商确认消息,此次协商成功的流程结束。需要说明的是,Δm和Δn是预先配置的默认值,在可接收范围系数内选择的波动系数的变化值。
在本发明上述实施例中,步骤S400中所述向所述第一节点发送包括预先设定的重传间隔配置参数ResendIntervalConfig的协商不通过消息的步骤,如图5所示,包括:
步骤S405、提取所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
步骤S406、将预先设定的重传间隔配置参数ResendIntervalConfig中的第二重传间隔R2和第二重传次数C2与所述第一节点的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1进行比较,当R1>=R2×(1-Δm)、C1<=C2×(1+Δn)两式中的任一个不满足时,表明协商不通过;
步骤S407、向所述第一节点发送包括预先设定的重传间隔配置参数ResendIntervalConfig的协商不通过消息。
获取第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1,然后将第一重传间隔R1和第一重传次数C1与本节点中预先设定的重传间隔配置参数ResendIntervalConfig中的第二重传间隔R2和第二重传次数C2进行比较,当第一重传间隔R1、第一重传次数C1、第二重传间隔R2和第二重传次数C2这四个参数之间的关系对于式一:R1>=R2×(1-Δm)和式二:C1<=C2×(1+Δn)中的任一个不满足时,表明协商失败,本节点向第一节点发送协商不通过消息,协商不通 过消息中包含本节点预先设定的重传间隔配置参数ResendIntervalConfig。
在本发明上述实施例中,所述接收第一节点发送的携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息的步骤之后,所述方法还包括:
向所述第一节点回复包含错误代码对象的回应消息,通过所述错误代码对象向所述第一节点表明所述第二节点不支持重传机制协商。
当本节点不支持重传机制协商时,则向第一节点发送包含错误代码对象的回应消息。同时当本节点不支持重传机制协商时,也可以不对链路管理协议配置Config消息中的重传间隔配置参数ResendIntervalConfig进行处理,第一节点在一定时间内接收不到本节点反馈的回应消息,则确定本节点不支持重传机制协商。
如图6所示,为本发明实施例第二节点侧降低链路管理协议中消息拥塞的方法的整体步骤流程图:
步骤S201、接收链路管理协议配置Config消息,判断该消息中是否携带重传间隔配置参数ResendIntervalConfig,如果不携带则按照正常协议进行处理,如果携带则进行下一步骤。
步骤S202、判断本节点是否支持重传机制协商,如果不支持,则进行步骤S203,如果支持,则进行步骤S204。
步骤S203、判断是否忽略对链路管理协议配置Config消息的处理,如果是,则忽略重传间隔配置参数ResendIntervalConfig;如果不是则回复包含Error_Code对象的ConfigNack消息。
步骤S204、获得重传间隔配置参数ResendIntervalConfig中的第一重传间隔R1和第一重传次数C1。
步骤S205、将第一重传间隔R1和第一重传次数C1与本节点中预先设定的第二重传间隔R2和第二重传次数C2进行比较,判断是否满足R1>=R2×(1-Δm)并且C1<=C2×(1+Δn),若满足执行步骤S206,若不满足执行步骤S207。
步骤S206、回复ConfigAck消息,表示此次协商成功。
步骤S207、回复ConfigNack消息,表示此次协商失败,携带重传间隔配 置参数ResendIntervalConfig,写入本节点对重传参数的建议值。
如图7所示,在控制通道上对消息发送和接收设置了监控管理,第一节点发送的链路管理协议配置Config消息、接收的回应消息在控制通道CC1上超过设定的阈值后,可以动态增大第一重传间隔R1、减小第一重传次数C1,进一步降低了消息拥塞的风险。这个可以不用再次进行协商,因为按照上文中的算法,R1>=R2×(1-Δm)、C1<=C2×(1+Δn)这个变动肯定是满足的。
第二节点接收的链路管理协议配置Config消息、发送的回应消息在控制通道CC2上超过设定的阈值后,可以动态减小第二重传间隔R2、增大第二重传次数C2,进一步降低了消息拥塞的风险。这个可以不用再次进行协商,因为按照上文中的算法,R1>=R2×(1-Δm)、C1<=C2×(1+Δn)这个变动肯定是满足的。
本发明实施例还提供一种降低链路管理协议中消息拥塞的装置,应用于第一节点侧,如图8所示,所述装置包括:
第一发送模块20,设置为向第二节点发送携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息;
第一处理模块30,设置为接收所述第二节点反馈的回应消息,当所述回应消息为所述第二节点的协商确认消息时,以所述链路管理协议配置Config消息中设定的重传间隔配置参数为标准向所述第二节点发送消息;当所述回应消息为所述第二节点的协商不通过消息时,以所述协商不通过消息中设定的重传间隔配置参数ResendIntervalConfig为依据向所述第二节点发送消息,直至协商成功。
在本发明上述实施例中,如图8所示,所述装置还包括:
设置模块10,设置为设定重传间隔配置参数ResendIntervalConfig,其中重传间隔配置参数ResendIntervalConfig中至少包括:重传间隔R和重传次数C。
在本发明上述实施例中,所述第一处理模块30可选设置为:
判断所述回应消息的消息类型,当所述回应消息为ConfigAck消息时,则确定所述回应消息为所述第二节点的协商确认消息;当所述回应消息为 ConfigNack消息,提取所述回应消息中的参数进行解码,当解码后的参数包括重新写入的重传间隔配置参数ResendIntervalConfig时,则确定所述回应消息为所述第二节点的协商不通过消息。
在本发明上述实施例中,所述第一处理模块30在判断出所述回应消息为ConfigNack消息后,还设置为:
提取所述回应消息中的参数进行解码,当解码后的参数包括一错误代码Error_Code对象时,则确定所述第二节点不支持重传机制协商。
本发明实施例还提供了一种降低链路管理协议中消息拥塞的装置,应用于第二节点侧,如图9所示,所述装置包括:
第一接收模块40,设置为接收第一节点发送的携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息;
第二处理模块50,设置为保存重传间隔配置参数ResendIntervalConfig,并向所述第一节点发送协商确认消息;或者向所述第一节点发送包括预先设定的重传间隔配置参数ResendIntervalConfig的协商不通过消息。
在本发明上述实施例中,如图10所示,所述第二处理模块50包括:
第一提取单元51,设置为提取所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
第一比较单元52,设置为将预先设定的重传间隔配置参数ResendIntervalConfig中的第二重传间隔R2和第二重传次数C2与所述第一节点的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1进行比较,当满足R1>=R2×(1-Δm)并且C1<=C2×(1+Δn)时,表明协商通过,其中Δm表示重传间隔波动系数的变化值,Δn表示重传次数波动系数的变化值,且Δm和Δn的范围在[0~50%)之间;
第一保存单元53,设置为保存所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
第一发送单元54,设置为向所述第一节点发送协商确认消息。
在本发明上述实施例中,如图11所示,所述第二处理模块50还包括:
第二提取单元55,设置为提取所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
第二比较单元56,设置为将预先设定的重传间隔配置参数ResendIntervalConfig中的第二重传间隔R2和第二重传次数C2与所述第一节点的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1进行比较,当R1>=R2×(1-Δm)、C1<=C2×(1+Δn)两式中的任一个不满足时,表明协商不通过;
第二发送单元57,设置为向所述第一节点发送包括预先设定的重传间隔配置参数ResendIntervalConfig的协商不通过消息。
在本发明上述实施例中,在接收第一节点发送的携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息后,如图9所示,所述装置还包括:
第三处理模块60,设置为向所述第一节点回复包含错误代码对象的回应消息,通过所述错误代码对象向所述第一节点表明所述第二节点不支持重传机制协商。
本发明实施例的降低链路管理协议中消息拥塞的方法中,通过节点之间往来消息的协商来确定节点之间消息传送的重传间隔和重传次数,以确定后的标准的重传间隔和重传次数为依据来进行消息的传送,以便能够更好的控制报文的发送,在可控的范围内,降低节点上消息拥塞的风险,提高网络传输的稳定性。可选的,通过动态调整,在节点将出现拥塞时对消息重传进行调整,进一步降低了消息拥塞的风险。通过重传机制协商,提供了一套简单的网络认证方法,即通过是否支持重传机制协商来进行简单的网络认证,无需添加复杂的认证对象和认证策略算法。
需要说明的是,本发明实施例提供的降低链路管理协议中消息拥塞的装置是应用上述方法的装置,则上述方法的所有实施例均适用于该装置,且均能达到相同或相似的有益效果。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现,所述计算机程序可以存储于一计算机可读存储介质中,所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件等)执行,在执行时,包括方法实施例的步骤之一或其组合。
可选地,上述实施例的全部或部分步骤也可以使用集成电路来实现,这 些步骤可以被分别制作成一个个集成电路模块,或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
上述实施例中的各装置/功能模块/功能单元可以采用通用的计算装置来实现,它们可以集中在单个的计算装置上,也可以分布在多个计算装置所组成的网络上。
上述实施例中的各装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器,磁盘或光盘等。
工业实用性
本发明实施例通过节点之间往来消息的协商来确定节点之间消息传送的重传间隔和重传次数,以确定后的标准的重传间隔和重传次数为依据来进行消息的传送,以便能够更好的控制报文的发送,在可控的范围内,降低节点上消息拥塞的风险,提高网络传输的稳定性。可选的,本发明实施例还提供了一套简单的网络认证方法,即通过是否支持重传机制协商来进行简单的网络认证,无需添加复杂的认证对象和认证策略算法。

Claims (16)

  1. 一种降低链路管理协议中消息拥塞的方法,应用于第一节点侧,所述方法包括:
    向第二节点发送携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息;
    接收所述第二节点反馈的回应消息,当所述回应消息为所述第二节点的协商确认消息时,以所述链路管理协议配置Config消息中设定的重传间隔配置参数为标准向所述第二节点发送消息;当所述回应消息为所述第二节点的协商不通过消息时,以所述协商不通过消息中设定的重传间隔配置参数ResendIntervalConfig为依据向所述第二节点发送消息,直至协商成功。
  2. 如权利要求1所述的降低链路管理协议中消息拥塞的方法,所述向第二节点发送携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息之前,所述方法还包括:
    设定重传间隔配置参数ResendIntervalConfig,其中重传间隔配置参数ResendIntervalConfig中至少包括:重传间隔R和重传次数C。
  3. 如权利要求1所述的降低链路管理协议中消息拥塞的方法,所述接收所述第二节点反馈的回应消息之后,所述方法还包括:
    判断所述回应消息的消息类型,当所述回应消息为配置确认ConfigAck消息时,则确定所述回应消息为所述第二节点的协商确认消息;当所述回应消息为配置否定ConfigNack消息,提取所述回应消息中的参数进行解码,当解码后的参数包括重新写入的重传间隔配置参数ResendIntervalConfig时,则确定所述回应消息为所述第二节点的协商不通过消息。
  4. 如权利要求3所述的降低链路管理协议中消息拥塞的方法,其中,在判断所述回应消息的消息类型的步骤中:
    当所述回应消息为ConfigNack消息,提取所述回应消息中的参数进行解码,当解码后的参数包括一错误代码Error_Code对象时,则确定所述第二节点不支持重传机制协商。
  5. 一种降低链路管理协议中消息拥塞的方法,应用于第二节点侧,所述 方法包括:
    接收第一节点发送的携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息;
    保存重传间隔配置参数ResendIntervalConfig,并向所述第一节点发送协商确认消息;或者向所述第一节点发送包括预先设定的重传间隔配置参数ResendIntervalConfig的协商不通过消息。
  6. 如权利要求5所述的降低链路管理协议中消息拥塞的方法,其中,所述保存重传间隔配置参数ResendIntervalConfig,并向所述第一节点发送协商确认消息的步骤,包括:
    提取所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
    将预先设定的重传间隔配置参数ResendIntervalConfig中的第二重传间隔R2和第二重传次数C2与所述第一节点的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1进行比较,当满足R1>=R2×(1-Δm)并且C1<=C2×(1+Δn)时,表明协商通过,其中Δm表示重传间隔波动系数的变化值,表示Δn重传次数波动系数的变化值,且Δm和Δn的范围在[0~50%)之间;
    保存所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
    向所述第一节点发送协商确认消息。
  7. 如权利要求5所述的降低链路管理协议中消息拥塞的方法,其中,所述向所述第一节点发送包括预先设定的重传间隔配置参数ResendInterval Config的协商不通过消息的步骤,包括:
    提取所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
    将预先设定的重传间隔配置参数ResendIntervalConfig中的第二重传间隔R2和第二重传次数C2与所述第一节点的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1进行比较,当R1>=R2×(1-Δm)、C1<=C2×(1+Δn)两式中的任一个不满足时, 表明协商不通过;其中Δm表示重传间隔波动系数的变化值,Δn表示重传次数波动系数的变化值,且Δm和Δn的范围在[0~50%)之间;
    向所述第一节点发送包括预先设定的重传间隔配置参数ResendIntervalConfig的协商不通过消息。
  8. 如权利要求5所述的降低链路管理协议中消息拥塞的方法,所述接收第一节点发送的携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息的步骤之后,所述方法还包括:
    向所述第一节点回复包含错误代码对象的回应消息,通过所述错误代码对象向所述第一节点表明所述第二节点不支持重传机制协商。
  9. 一种降低链路管理协议中消息拥塞的装置,应用于第一节点侧,所述装置包括:
    第一发送模块,设置为向第二节点发送携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息;
    第一处理模块,设置为接收所述第二节点反馈的回应消息,当所述回应消息为所述第二节点的协商确认消息时,以所述链路管理协议配置Config消息中设定的重传间隔配置参数为标准向所述第二节点发送消息;当所述回应消息为所述第二节点的协商不通过消息时,以所述协商不通过消息中设定的重传间隔配置参数ResendIntervalConfig为依据向所述第二节点发送消息,直至协商成功。
  10. 如权利要求9所述的降低链路管理协议中消息拥塞的装置,所述装置还包括:
    设置模块,设置为设定重传间隔配置参数ResendIntervalConfig,其中重传间隔配置参数ResendIntervalConfig中至少包括:重传间隔R和重传次数C。
  11. 如权利要求9所述的降低链路管理协议中消息拥塞的装置,其中,所述第一处理模块还设置为:
    判断所述回应消息的消息类型,当所述回应消息为配置确认ConfigAck消息时,则确定所述回应消息为所述第二节点的协商确认消息;当所述回应消息为配置否定ConfigNack消息,提取所述回应消息中的参数进行解码,当解码后的参数包括重新写入的重传间隔配置参数ResendIntervalConfig时,则 确定所述回应消息为所述第二节点的协商不通过消息。
  12. 如权利要求11所述的降低链路管理协议中消息拥塞的装置,其中,
    所述第一处理模块还设置为:在判断出所述回应消息为ConfigNack消息后,提取所述回应消息中的参数进行解码,当解码后的参数包括一错误代码Error_Code对象时,则确定所述第二节点不支持重传机制协商。
  13. 一种降低链路管理协议中消息拥塞的装置,应用于第二节点侧,所述装置包括:
    第一接收模块,设置为接收第一节点发送的携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息;
    第二处理模块,设置为保存重传间隔配置参数ResendIntervalConfig,并向所述第一节点发送协商确认消息;或者向所述第一节点发送包括预先设定的重传间隔配置参数ResendIntervalConfig的协商不通过消息。
  14. 如权利要求13所述的降低链路管理协议中消息拥塞的装置,其中,所述第二处理模块包括:
    第一提取单元,设置为提取所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
    第一比较单元,设置为将预先设定的重传间隔配置参数ResendIntervalConfig中的第二重传间隔R2和第二重传次数C2与所述第一节点的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1进行比较,当满足R1>=R2×(1-Δm)并且C1<=C2×(1+Δn)时,表明协商通过,其中Δm表示重传间隔波动系数的变化值,Δn表示重传次数波动系数的变化值,且Δm和Δn的范围在[0~50%)之间;
    第一保存单元,设置为保存所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
    第一发送单元,设置为向所述第一节点发送协商确认消息。
  15. 如权利要求13所述的降低链路管理协议中消息拥塞的装置,其中,所述第二处理模块还包括:
    第二提取单元,设置为提取所述第一节点发送的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1;
    第二比较单元,设置为将预先设定的重传间隔配置参数ResendIntervalConfig中的第二重传间隔R2和第二重传次数C2与所述第一节点的重传间隔配置参数ResendIntervalConfig中设定的第一重传间隔R1和第一重传次数C1进行比较,当R1>=R2×(1-Δm)、C1<=C2×(1+Δn)两式中的任一个不满足时,表明协商不通过;其中Δm表示重传间隔波动系数的变化值,Δn表示重传次数波动系数的变化值,且Δm和Δn的范围在[0~50%)之间;
    第二发送单元,设置为向所述第一节点发送包括预先设定的重传间隔配置参数ResendIntervalConfig的协商不通过消息。
  16. 如权利要求13所述的降低链路管理协议中消息拥塞的装置,还包括第三处理模块,设置为:
    在所述第一接收模块接收第一节点发送的携带重传间隔配置参数ResendIntervalConfig的链路管理协议配置Config消息后,向所述第一节点回复包含错误代码对象的回应消息,通过所述错误代码对象向所述第一节点表明所述第二节点不支持重传机制协商。
PCT/CN2015/090949 2015-04-10 2015-09-28 一种降低链路管理协议中消息拥塞的方法及装置 WO2016161784A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510167528.2 2015-04-10
CN201510167528.2A CN106161278A (zh) 2015-04-10 2015-04-10 一种降低链路管理协议中消息拥塞的方法及装置

Publications (1)

Publication Number Publication Date
WO2016161784A1 true WO2016161784A1 (zh) 2016-10-13

Family

ID=57072171

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/090949 WO2016161784A1 (zh) 2015-04-10 2015-09-28 一种降低链路管理协议中消息拥塞的方法及装置

Country Status (2)

Country Link
CN (1) CN106161278A (zh)
WO (1) WO2016161784A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114124314A (zh) * 2020-08-27 2022-03-01 华为技术有限公司 控制客户端上线的方法、网络设备及客户端

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070291646A1 (en) * 2006-06-20 2007-12-20 Fujitsu Limited Retransmission control method and device
CN101237270A (zh) * 2007-02-01 2008-08-06 中兴通讯股份有限公司 一种节点b获得重传间隔控制信息的方法
CN101741524A (zh) * 2008-11-21 2010-06-16 大唐移动通信设备有限公司 一种确定最小重传时间间隔的方法、系统和装置
JP2011061829A (ja) * 2010-10-25 2011-03-24 Kyocera Corp データ再送制御方法、システム及びデータ再送制御装置
CN102035632A (zh) * 2009-09-25 2011-04-27 中兴通讯股份有限公司 一种无线中继场景下的数据传输方法和系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7237261B1 (en) * 1999-09-07 2007-06-26 Swisscom Ag Method, system and gateway allowing secured end-to-end access to WAP services
CN1943201B (zh) * 2004-04-28 2010-11-10 诺基亚公司 协议参数协商
CN101217338B (zh) * 2007-01-06 2012-04-25 华为技术有限公司 一种检测消息的传送方法、网元设备
CN101651608B (zh) * 2008-08-14 2013-10-09 华为技术有限公司 链路管理方法及相应管理实体、执行节点和移动通信系统
US8331273B2 (en) * 2009-08-28 2012-12-11 Mediatek Inc. Communication methods employed in communication system associated with programmable communication protocols, and related transmitting methods, receiving methods and communication device
CN103036904B (zh) * 2012-12-27 2015-10-21 东方通信股份有限公司 一种在通信网络中使用udp协议进行数据可靠传输的方法
CN103957079A (zh) * 2014-04-30 2014-07-30 杭州华三通信技术有限公司 一种hdlc网络中的协商方法和设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070291646A1 (en) * 2006-06-20 2007-12-20 Fujitsu Limited Retransmission control method and device
CN101237270A (zh) * 2007-02-01 2008-08-06 中兴通讯股份有限公司 一种节点b获得重传间隔控制信息的方法
CN101741524A (zh) * 2008-11-21 2010-06-16 大唐移动通信设备有限公司 一种确定最小重传时间间隔的方法、系统和装置
CN102035632A (zh) * 2009-09-25 2011-04-27 中兴通讯股份有限公司 一种无线中继场景下的数据传输方法和系统
JP2011061829A (ja) * 2010-10-25 2011-03-24 Kyocera Corp データ再送制御方法、システム及びデータ再送制御装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LANG, J.E. ET AL.: "Link Management Protocol (LMP", NETWORK WORKING GROUP, 31 October 2005 (2005-10-31), XP055318951 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114124314A (zh) * 2020-08-27 2022-03-01 华为技术有限公司 控制客户端上线的方法、网络设备及客户端
CN114124314B (zh) * 2020-08-27 2023-08-25 华为技术有限公司 控制客户端上线的方法、网络设备及客户端

Also Published As

Publication number Publication date
CN106161278A (zh) 2016-11-23

Similar Documents

Publication Publication Date Title
JP4972304B2 (ja) ウェブサービス環境用の信頼できるメッセージング内の接続生存性の検証および維持
US9647945B2 (en) Mechanisms to improve the transmission control protocol performance in wireless networks
JP5867188B2 (ja) 情報処理装置、輻輳制御方法および輻輳制御プログラム
KR101610715B1 (ko) 단방향 데이터 송수신 시스템 및 방법
JP2014524092A (ja) 単一ソケットポイントツーマルチポイント性能による高信頼性仮想双方向データストリーム通信のためのシステムおよび方法
WO2014147774A1 (ja) 通信方法、通信装置、および、通信プログラム
JPWO2007052764A1 (ja) セッション中継装置およびセッション中継方法
JP2017028589A (ja) 通信装置、無線通信装置、および通信方法
US10057178B2 (en) System and method for reducing bandwidth usage of a network
US20150256441A1 (en) Neighbor relationship processing method and routing device
US9949300B2 (en) Packet transmission method and system, and station
JP6403556B2 (ja) ゲートウェイ装置、スマートメータおよび無線メッシュネットワーク
CN103825822A (zh) 一种网络设备的状态信息传输方法和装置
CN110771117B (zh) 一种采用面向id的网络的会话层通信
WO2016161784A1 (zh) 一种降低链路管理协议中消息拥塞的方法及装置
EP3410637B1 (en) Information transmission method, gateway, and controller
US9219801B2 (en) Implementing a protocol adaptation layer over an internet protocol
JP7128288B2 (ja) トランスポートプロトコル上でのポイント・ツー・ポイント・データベース同期
US9544249B2 (en) Apparatus and method for aligning order of received packets
WO2014205819A1 (zh) 一种建立链路的方法、节点及装置
CN102281194A (zh) 报文的传输方法及网络设备
JP2019114947A (ja) 通信装置、通信装置の制御方法およびプログラム
WO2021018150A1 (zh) 一种链路检测的方法和装置
WO2012155703A1 (zh) 基于hdlc协议的链路参数自协商方法、终端及系统
US9338016B2 (en) Method and apparatus for exchanging messages

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15888336

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15888336

Country of ref document: EP

Kind code of ref document: A1