WO2023279802A1 - 协议数据传输方法、装置、网络节点及存储介质 - Google Patents

协议数据传输方法、装置、网络节点及存储介质 Download PDF

Info

Publication number
WO2023279802A1
WO2023279802A1 PCT/CN2022/087486 CN2022087486W WO2023279802A1 WO 2023279802 A1 WO2023279802 A1 WO 2023279802A1 CN 2022087486 W CN2022087486 W CN 2022087486W WO 2023279802 A1 WO2023279802 A1 WO 2023279802A1
Authority
WO
WIPO (PCT)
Prior art keywords
frame
lldp
protocol
node
transmission
Prior art date
Application number
PCT/CN2022/087486
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 WO2023279802A1 publication Critical patent/WO2023279802A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks

Definitions

  • the present application relates to the field of data communication network technology, for example, to a protocol data transmission method, device, network node and storage medium.
  • the International Standards Organization Institute of Electrical and Electronics Engineers (Institute of Electrical and Electronics Engineers, IEEE) formulates standards that specify the protocol data and protocol working mechanism of the Link Layer Discovery Protocol (LLDP).
  • LLDP protocol runs between two adjacent network nodes, and the two adjacent network nodes can send LLDP protocol frames to each other.
  • LLDP protocol data is carried in the LLDP protocol frame in the form of Type Length Value (TLV) and transmitted in a single frame.
  • TLV Type Length Value
  • the LLDP protocol frame needs to carry more and more protocol data. Since the LLDP protocol frame is a kind of Ethernet frame (Ethernet Frame), its length is limited by the maximum length of the Ethernet frame specified by IEEE, which is 1500 bytes. In most application scenarios, the amount of LLDP protocol data to be transmitted has exceeded a single The maximum length of the LLDP protocol frame and the single-frame transmission method have relatively large limitations, and the transmission efficiency is low, which cannot meet actual needs.
  • the present application provides a protocol data transmission method, device, network node and storage medium, so as to improve the transmission efficiency and flexibility of the protocol data.
  • An embodiment of the present application provides a protocol data transmission method, including: receiving a first LLDP protocol frame sent by a peer node, where the first LLDP protocol frame carries multi-frame transmission capability information of the peer node; according to the local The multi-frame transmission capability information of the node and the multi-frame transmission capability information of the peer node transmit a second LLDP protocol frame with the peer node, and the second LLDP protocol frame carries protocol data.
  • the embodiment of the present application also provides a protocol data transmission device, including: a capability information receiving module, configured to receive the first LLDP protocol frame sent by the peer node, the first LLDP protocol frame carrying the peer node Multi-frame transmission capability information; the data transmission module is configured to transmit a second LLDP protocol frame with the opposite node according to the multi-frame transmission capability information of the local node and the multi-frame transmission capability information of the opposite node, and the The second LLDP protocol frame carries protocol data.
  • a capability information receiving module configured to receive the first LLDP protocol frame sent by the peer node, the first LLDP protocol frame carrying the peer node Multi-frame transmission capability information
  • the data transmission module is configured to transmit a second LLDP protocol frame with the opposite node according to the multi-frame transmission capability information of the local node and the multi-frame transmission capability information of the opposite node, and the The second LLDP protocol frame carries protocol data.
  • the embodiment of the present application also provides a network node, including: a memory, a processor, and a computer program stored in the memory and operable on the processor.
  • a network node including: a memory, a processor, and a computer program stored in the memory and operable on the processor.
  • the processor executes the program, the above protocol data transmission method is implemented. .
  • the embodiment of the present application also provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and the above-mentioned protocol data transmission method is implemented when the program is executed by a processor.
  • Fig. 1 is a flowchart of a protocol data transmission method provided by an embodiment
  • FIG. 2 is a schematic diagram of a first LLDP protocol frame provided by an embodiment
  • FIG. 3 is a schematic diagram of a second LLDP protocol frame carrying an extended protocol data directory provided by an embodiment
  • FIG. 4 is a schematic diagram of a second LLDP protocol frame carrying an extended protocol data identifier provided by an embodiment
  • FIG. 5 is a schematic diagram of a second LLDP protocol frame carrying an extended protocol data termination indication provided by an embodiment
  • FIG. 6 is a schematic diagram of a third LLDP protocol frame provided by an embodiment
  • FIG. 7 is a schematic diagram of a third LLDP protocol frame provided by another embodiment.
  • FIG. 8 is a schematic structural diagram of a protocol data transmission device provided by an embodiment
  • Fig. 9 is a schematic diagram of a hardware structure of a network node provided by an embodiment.
  • a protocol data transmission method which transmits protocol data according to the multi-frame transmission capabilities of the local node and the peer node, and solves the problem that the amount of LLDP protocol data to be transmitted exceeds a single LLDP protocol frame
  • the problem of the maximum length limitation improves the transmission efficiency and the flexibility of transmission.
  • Fig. 1 is a flowchart of a protocol data transmission method provided by an embodiment. As shown in FIG. 1 , the method provided in this embodiment includes step 110 and step 120 .
  • step 110 the first link layer discovery protocol LLDP protocol frame sent by the peer node is received, and the first LLDP protocol frame carries the multi-frame transmission capability information of the peer node.
  • the multi-frame transmission capability information is used to indicate whether a network node supports receiving and/or sending of multi-frame LLDP.
  • the local node and the peer node are usually two adjacent network nodes, and by exchanging their respective multi-frame transmission capability information, it can be determined whether the two nodes support multi-frame transmission.
  • the local node may determine whether the peer node supports multi-frame LLDP transmission according to the multi-frame transmission capability information carried in the first LLDP protocol frame sent by the peer node.
  • the multi-frame transmission capability of two nodes affects whether the protocol data is transmitted in multi-frame or single-frame mode in different transmission directions (for example, the local node sends-peer node receives, or the peer node sends-local node receives).
  • step 120 according to the multi-frame transmission capability information of the local node and the multi-frame transmission capability information of the peer node, a second LLDP protocol frame is transmitted with the peer node, and the second LLDP protocol frame carries a protocol data.
  • the second LLDP protocol frame may be a single frame, or may include multiple frames.
  • the local node may support multi-frame LLDP reception and/or multi-frame LLDP transmission, and the peer node may also support multi-frame LLDP reception and/or multi-frame LLDP transmission. For different situations of the multi-frame transmission capabilities of the two nodes, the methods of transmitting protocol data in different transmission directions are also different.
  • the protocol data is transmitted through multi-frame LLDP, thereby increasing the amount of transmitted data and improving transmission efficiency; while in the process of sending from the local node to receiving from the peer node, the protocol data can only be transmitted through single-frame LLDP. In this case, the data is transmitted Quantity is limited.
  • the local node can also indicate the multi-frame transmission capability information of the local node to the peer node by sending LLDP protocol frames, so that the peer node can also clarify whether the transmission mode between the two nodes in different transmission directions is single frame or multiple frames.
  • the local node may serve as a sender of protocol data, or as a receiver of protocol data.
  • the multi-frame transmission capability information is indicated by the first LLDP protocol frame, and on this basis, the protocol data is transmitted in a single frame or multiple frames in the corresponding transmission direction by the second LLDP protocol frame, which improves the transmission efficiency and efficiency of the protocol data. flexibility.
  • the multi-frame transmission capability information includes at least one of the following: support multi-frame LLDP transmission; support multi-frame LLDP reception; support multi-frame LLDP transceiver; do not support multi-frame LLDP transmission; do not support multi-frame LLDP Receive; does not support multi-frame LLDP transceiver.
  • the multi-frame transmission capabilities of the local node and the peer node are mainly divided into the following three situations.
  • Case 2 One node supports multi-frame LLDP transmission, and the other node supports multi-frame LLDP reception. In this case, multi-frame transmission of protocol data can be realized in the corresponding transmission direction.
  • step 120 includes: when the local node supports multi-frame LLDP transmission and the opposite node supports multi-frame LLDP reception, sending a second LLDP protocol frame to the opposite node; wherein, the second LLDP The protocol frame includes a plurality of LLDP protocol frames.
  • multi-frame transmission can be supported in the transmission direction from local node transmission to peer node reception, that is, the second LLDP protocol frame includes multiple LLDP protocol frames, which can carry more frames than the single-frame transmission working mode. More protocol data, improve transmission efficiency.
  • the second LLDP protocol frame carries the extended protocol data directory, the extended protocol data identifier, the extended protocol data, and the extended protocol data termination indication.
  • the extended protocol data directory TLV lists all the extended protocol data transmitted in subsequent LLDP protocol frames in the form of a directory; the extended protocol data identifier is used to specifically identify the extended protocol data to be transmitted, and should be related to the extended protocol data in the extended protocol data directory Corresponding to each directory item; the extended protocol data refers to the protocol data that cannot be transmitted in the first LLDP frame in the second LLDP protocol frame and needs to be transmitted in the second and subsequent LLDP frames; the extended protocol data termination indication It is used as the end mark of extended protocol data transmission. On this basis, the transmission of the amount of data beyond the maximum length limit of a single LLDP protocol frame is realized.
  • the second LLDP protocol frame includes multiple LLDP protocol frames, wherein the first LLDP protocol frame carries part of the protocol data and the extended protocol data directory sent by the local node to the peer node, and the second and subsequent LLDP protocol frames
  • the frame carries the extended protocol data identifier and the corresponding extended protocol data
  • the last LLDP protocol frame carries the extended protocol data termination indication, indicating that the LLDP protocol frame is the last one among the multiple LLDP protocol frames in the group.
  • each LLDP protocol frame should carry as much data as possible under the premise of meeting the maximum length limit.
  • the extended protocol data directory, the extended protocol data identifier, the extended protocol data, and the extended protocol data termination instruction are transmitted through a group of multiple LLDP frames, without the peer node feeding back a data request for the directory, avoiding the Latency of multi-frame LLDP protocol data transmission.
  • the method further includes step 130 .
  • Step 130 Receive a third LLDP protocol frame sent by the peer node, where the third LLDP protocol frame carries at least one of the following: an indication of successful transmission of protocol data; an indication of failure of transmission of protocol data; an identification of failed transmission of protocol data.
  • the third LLDP protocol frame is used to reflect the transmission result of the protocol data.
  • the first LLDP protocol frame carries the extended protocol data directory
  • the second and subsequent LLDP protocol frames carry the extended protocol data identifier and the corresponding extended protocol data
  • the peer node compares whether the extended protocol data directory is consistent with the set of received extended protocol data identifiers. If they are consistent, it means that the peer node has successfully received all the extended protocol data listed in the extended protocol data directory.
  • the peer node can send the third LLDP protocol frame to the local node, which carries Protocol data transmission success indication; if inconsistent, the peer node can send a protocol data transmission failure indication through the third LLDP protocol frame, and/or list the extensions in the extension protocol data directory that have not been successfully received in the third LLDP protocol frame
  • the extended protocol data identification corresponding to the protocol data provides a basis for the retransmission of the protocol data that fails to be transmitted.
  • step 120 includes: when the local node supports multi-frame LLDP reception and the opposite node supports multi-frame LLDP transmission, receiving the second LLDP protocol frame sent by the opposite node; wherein, the second The LLDP protocol frame includes a plurality of LLDP protocol frames.
  • the second LLDP protocol frame also carries the following information: extended protocol data directory, extended protocol data identifier, extended protocol data, and extended protocol data termination indication.
  • multi-frame transmission can be supported in the transmission direction of peer node sending-local node receiving, and the second LLDP protocol frame includes multiple LLDP protocol frames, and carries the protocol sent by the peer node to the local node Data, as well as the extended protocol data directory, extended protocol data identifier, extended protocol data, and extended protocol data termination indication, can carry more protocol data than the single-frame transmission working mode, improving transmission efficiency.
  • the method further includes step 140 .
  • Step 140 Comparing the extended protocol data directory with the extended protocol data identifier to obtain the transmission result of the protocol data.
  • the local node after receiving the second LLDP protocol frame from the peer node, judges whether all protocol data is successfully received by comparing the extended protocol data directory and the extended protocol data identifier sent by the peer node, and obtains the protocol data transfer result. Transfer results include transfer success, transfer failure, and/or partial data transfer failure.
  • the method further includes step 150 .
  • Step 150 Send a fourth LLDP protocol frame to the peer node according to the transmission result of the protocol data, wherein the fourth LLDP protocol frame carries at least one of the following: a protocol data transmission success indication; a protocol data transmission failure indication ;Identifier of the protocol data that failed to be transmitted.
  • the local node sends the fourth LLDP protocol frame to the peer node according to the transmission result of the protocol data, to indicate whether the protocol data is successfully transmitted, and may also indicate the protocol data identifier of the failed transmission, which is the protocol data of the failed transmission provides a basis for the retransmission.
  • the extended protocol data is identified as a subset of the extended protocol data directory.
  • the extended protocol data carried in the second LLDP protocol frame is identified as a subset of the extended protocol data directory. If the relationship is not satisfied, it means that the transmission of the protocol data is wrong.
  • step 120 includes: when the local node does not support multi-frame LLDP transmission, or the opposite node does not support multi-frame LLDP reception, sending a second LLDP protocol frame to the opposite node, the second LLDP Protocol frames consist of a single LLDP protocol frame.
  • multi-frame transmission is not supported in the transmission direction from the local node to the peer node, and the second LLDP protocol frame sent by the local node includes a single LLDP protocol frame.
  • the amount of transmitted data is limited, due to The two nodes exchange multi-frame transmission capability information in advance, and can flexibly determine the transmission mode in the transmission direction, thereby ensuring the reliability of the protocol data between the two nodes.
  • step 120 includes: when the local node does not support multi-frame LLDP reception, or the peer node does not support multi-frame LLDP transmission, receiving the second LLDP protocol frame sent by the peer node, the second LLDP protocol frames consist of a single LLDP protocol frame.
  • multi-frame transmission is not supported in the transmission direction from the peer node to the local node.
  • the second LLDP protocol frame received by the local node includes a single LLDP protocol frame. Since the two nodes have exchanged multi-frame transmission in advance The capability information can flexibly determine the transmission mode in the transmission direction, so as to ensure the reliability of the protocol data between the two nodes.
  • step 120 includes: when the local node and the peer node do not support multi-frame LLDP reception, or when the local node and the peer node do not support multi-frame LLDP transmission, communicating with the peer The node transmits a second LLDP protocol frame, the second LLDP protocol frame comprising a single LLDP protocol frame.
  • the second LLDP protocol frame includes a single LLDP protocol frame.
  • the working mode of single frame transmission realizes the protocol data transmission between two nodes.
  • the protocol data transmission method of this embodiment is applicable to network nodes with any multi-frame transmission capability, even if there are network nodes that do not support the reception and/or transmission of multi-frame LLDP, the validity of the protocol data can be guaranteed transmission.
  • the protocol data transmission method is illustrated below through a specific example.
  • Two adjacent network nodes both support the transmission and reception of multi-frame LLDP, the data to be transmitted in both transmission directions exceeds the length limit of a single LLDP protocol frame, and both require 3 LLDP The protocol frame completes the transmission.
  • node A sends the first LLDP protocol frame to node B, which carries the multi-frame transmission capability information of node A.
  • Node B also sends a first LLDP protocol frame to Node A, which carries the multi-frame transmission capability information of Node B.
  • Fig. 2 is a schematic diagram of a first LLDP protocol frame provided by an embodiment. As shown in FIG. 2 , the peer node is notified of its ability to support multi-frame transmission by carrying the multi-frame LLDP transmission capability (that is, multi-frame transmission capability information) TLV in the first LLDP protocol frame.
  • node A sends the second LLDP protocol frame to node B
  • the second LLDP protocol frame includes three LLDP protocol frames, wherein, the first LLDP protocol frame carries the extended protocol data directory, and the second and third LLDP protocol frames The extended protocol data identifier and corresponding extended protocol data are carried, and the third LLDP protocol frame also carries an extended protocol data termination indication.
  • Fig. 3 is a schematic diagram of an extended protocol data directory carried in a second LLDP protocol frame provided by an embodiment.
  • the extended protocol data that needs to be transmitted is notified to the peer node by carrying the extended protocol data directory TLV in the LLDP protocol frame, that is, in addition to the protocol data carried in this LLDP protocol frame, other LLDP protocol frames need to be passed
  • the transmitted protocol data and the extended protocol data directory can be specifically represented by the identifiers of all the extended protocol data.
  • the format of the first LLDP protocol frame sent by node B to node A is consistent with that in FIG. 3 , except that it is protocol data and extended protocol data for different transmission directions.
  • FIG. 4 is a schematic diagram of a second LLDP protocol frame carrying an extended protocol data identifier provided by an embodiment. As shown in FIG. 4 , the extended protocol data transmitted by the LLDP protocol frame is notified to the peer node by carrying the extended protocol data identifier TLV in the LLDP protocol frame, that is, which extended data is carried by the LLDP protocol frame.
  • the format of the second LLDP protocol frame sent by node B to node A is consistent with that in Figure 4.
  • FIG. 5 is a schematic diagram of a second LLDP protocol frame carrying an extended protocol data termination indication provided by an embodiment.
  • the TLV notifies the peer node that the LLDP protocol frame is the last one in the group of LLDP protocol frames by carrying the extended protocol data termination instruction in the LLDP protocol frame.
  • the format of the third LLDP protocol frame sent by node B to node A is consistent with FIG. 5 .
  • Node B After Node B receives the three LLDP protocol frames sent by Node A, it compares the extended protocol data catalog carried in the first LLDP protocol frame with the extended protocol data identifiers carried in the second and third LLDP protocol frames, and judges whether All protocol data is successfully received, and a third LLDP protocol frame for indicating the protocol data transmission result is sent to node A. In addition, after receiving the second LLDP protocol frame sent by the node B, the node A may also send the fourth LLDP protocol frame to the node B according to the protocol data transmission result.
  • Fig. 6 is a schematic diagram of a third LLDP protocol frame provided by an embodiment. As shown in FIG. 6 , the node B is notified of successful reception of all protocol data through the extended protocol data reception success indication (ie protocol data transmission success indication) TLV carried in the LLDP protocol frame. In addition, if node A judges that the transmission result is that all protocol data of node B has been successfully received, the format of the fourth LLDP protocol frame is consistent with FIG. 6 .
  • Fig. 7 is a schematic diagram of a third LLDP protocol frame provided by another embodiment. As shown in Figure 7, through the extended protocol data reception failure indication carried in the LLDP protocol frame (that is, the protocol data transmission failure indication) TLV notification node B has not successfully received all the protocol data, and lists the unsuccessfully received data in the extended protocol data directory. The extended protocol data identifier of the received extended protocol data. In addition, if node A judges that the transmission result is that all protocol data of node B has not been successfully received, the format of the fourth LLDP protocol frame is consistent with FIG. 7 .
  • node A and node B Two adjacent network nodes (node A and node B), node A only supports multi-frame LLDP transmission, node B only supports multi-frame LLDP reception.
  • the protocol data to be transmitted exceeds the length limit of a single LLDP protocol frame, and two LLDP protocol frames are required for transmission; the protocol data to be transmitted in the direction from node B to node A The length limit of a single LLDP protocol frame is not exceeded.
  • node A sends the first LLDP protocol frame to node B, which carries node A's multi-frame LLDP transmission capability (that is, multi-frame transmission capability information: only supports multi-frame LLDP transmission, does not support multi-frame LLDP reception) TLV.
  • Node B sends the first LLDP protocol frame to node A, which carries Node B's multi-frame LLDP transmission capability (ie, multi-frame transmission capability information: only supports multi-frame LLDP reception, does not support multi-frame LLDP transmission) TLV.
  • node A sends the second LLDP protocol frame to node B, including two LLDP protocol frames, wherein the first LLDP protocol frame carries the extended protocol data directory, and the second LLDP protocol frame carries the extended protocol data identifier and the corresponding extended protocol data, and also carries the extended protocol data termination indication.
  • the second LLDP protocol frame sent by node B to node A includes a single LLDP protocol frame, carrying protocol data to be transmitted and a protocol data termination indication.
  • Node B After Node B receives the two LLDP protocol frames sent by Node A, it compares the extended protocol data directory carried in the first LLDP protocol frame with the extended protocol data identifier carried in the second LLDP protocol frame, and judges whether all protocols are successfully received. data, and send a third LLDP protocol frame for indicating the transmission result to node A according to the transmission result. After node A receives a single LLDP protocol frame sent by node B, it takes out the protocol data and saves it in the local database.
  • node A supports sending and receiving multi-frame LLDP
  • node B does not support sending and receiving multi-frame LLDP.
  • node A sends the first LLDP protocol frame to node B, which carries a multi-frame LLDP transmission capability (ie, multi-frame transmission capability information: supports multi-frame LLDP transmission and reception) TLV.
  • the node B sends the LLDP protocol frame to the node A, which does not carry the multi-frame LLDP capability TLV, indicating that the node B only supports the sending and receiving of the single-frame LLDP, but does not support the sending and receiving of the multi-frame LLDP.
  • the second LLDP protocol frame is transmitted between node A and node B, and the protocol data is transmitted through a single LLDP protocol frame during this process. Because node B does not support the sending and receiving of multi-frame LLDP, even if node A supports multi-frame LLDP sending and receiving, multi-frame LLDP will not be transmitted between the two nodes, and only single-frame transmission can be used.
  • the second LLDP protocol frame can also carry LLDP destination Media Access Control (Media Access Control, MAC) address, LLDP source MAC address, LLDP ether type, rack identifier, port identifier, information such as survival time.
  • Media Access Control Media Access Control
  • Fig. 8 is a schematic structural diagram of a protocol data transmission device provided by an embodiment. As shown in FIG. 8 , the protocol data transmission device includes a capability information receiving module 210 and a data transmission module 220 .
  • the capability information receiving module 210 is configured to receive the first LLDP protocol frame sent by the peer node, where the first LLDP protocol frame carries multi-frame transmission capability information of the peer node.
  • the data transmission module 220 is configured to transmit a second LLDP protocol frame with the peer node according to the multi-frame transmission capability information of the local node and the multi-frame transmission capability information of the peer node, and the second LLDP protocol frame Carry protocol data.
  • the protocol data transmission device of this embodiment indicates multi-frame transmission capability information through the first LLDP protocol frame, and on this basis, transmits the protocol data in a single frame or multiple frames in the corresponding transmission direction through the second LLDP protocol frame, which solves the problem of The problem that the amount of LLDP protocol data to be transmitted exceeds the maximum length limit of a single LLDP protocol frame improves transmission efficiency and transmission flexibility.
  • the multi-frame transmission capability information includes at least one of the following: support multi-frame LLDP transmission; or support multi-frame LLDP reception; or support multi-frame LLDP transceiver; or do not support multi-frame LLDP transmission; or do not support multi-frame LLDP reception; or does not support multi-frame LLDP transmission and reception.
  • the data transmission module 220 is specifically configured to: when the local node supports multi-frame LLDP transmission and the opposite node supports multi-frame LLDP reception, send the first Two LLDP protocol frames.
  • the second LLDP protocol frame includes multiple LLDP protocol frames.
  • the second LLDP protocol frame also carries the following information: extended protocol data directory, extended protocol data identifier, extended protocol data, and extended protocol data termination indication.
  • the device further includes a transmission result receiving module.
  • the transmission result receiving module is configured to receive the third LLDP protocol frame sent by the peer node, and the third LLDP protocol frame carries at least one of the following: protocol data transmission success indication; or protocol data transmission failure indication; or transmission failure The protocol data identifier for .
  • the data transmission module 220 is specifically configured to: receive the message sent by the peer node when the local node supports multi-frame LLDP reception and the peer node supports multi-frame LLDP transmission The second LLDP protocol frame.
  • the second LLDP protocol frame includes multiple LLDP protocol frames.
  • the second LLDP protocol frame also carries the following information: extended protocol data directory, extended protocol data identifier, extended protocol data, and extended protocol data termination indication.
  • the device further includes a comparison module.
  • the comparison module is configured to compare the extended protocol data directory with the extended protocol data identifier to obtain the transmission result of the protocol data.
  • the device further includes a transmission result sending module.
  • the transmission result sending module is configured to send a fourth LLDP protocol frame to the peer node according to the transmission result of the protocol data, wherein the fourth LLDP protocol frame carries at least one of the following: an indication of successful protocol data transmission; or An indication of protocol data transmission failure; or an identification of protocol data transmission failure.
  • the extended protocol data identifier is a subset of the extended protocol data directory.
  • the data transmission module 220 is specifically configured to: when the local node does not support multi-frame LLDP transmission, or the opposite node does not support multi-frame LLDP reception, send a message to the opposite node Sending a second LLDP protocol frame, where the second LLDP protocol frame includes a single LLDP protocol frame.
  • the data transmission module 220 is specifically configured to: when the local node does not support multi-frame LLDP reception, or the peer node does not support multi-frame LLDP transmission, receive the peer node A second LLDP protocol frame to be sent, where the second LLDP protocol frame includes a single LLDP protocol frame.
  • the data transmission module 220 is specifically configured to: when the local node and the peer node do not support multi-frame LLDP reception, or the local node and the peer node do not In the case of supporting multi-frame LLDP sending, transmit a second LLDP protocol frame with the peer node, where the second LLDP protocol frame includes a single LLDP protocol frame.
  • protocol data transmission device proposed in this embodiment and the protocol data transmission method proposed in the above embodiments belong to the same inventive concept, and the technical details that are not described in detail in this embodiment can be referred to any of the above embodiments, and this embodiment has an implementation protocol
  • the beneficial effect of the data transmission method is the same.
  • FIG. 9 is a schematic diagram of the hardware structure of a network node provided in an embodiment.
  • the network node provided in the present application includes a memory 32, a processor 31 and A computer program stored in the memory and operable on the processor. When the processor 31 executes the program, the above-mentioned protocol data transmission method is realized.
  • the network node can also include a memory 32; there can be one or more processors 31 in the network node, and one processor 31 is taken as an example in FIG. 9; the memory 32 is used to store one or more programs; the one or more A program is executed by the one or more processors 31, so that the one or more processors 31 implement the protocol data transmission method described in the embodiment of the present application.
  • the network node also includes: communication means 33 , input means 34 and output means 35 .
  • the processor 31, the memory 32, the communication device 33, the input device 34 and the output device 35 in the network node may be connected through a bus or in other ways.
  • connection through a bus is taken as an example.
  • the input device 34 can be used to receive input numbers or character information, and generate key signal input related to user settings and function control of the network node.
  • the output device 35 may include a display device such as a display screen.
  • the communication device 33 may include a receiver and a transmitter.
  • the communication device 33 is configured to perform information sending and receiving communication according to the control of the processor 31 .
  • the memory 32 can be configured to store software programs, computer-executable programs and modules, such as the program instructions/modules corresponding to the protocol data transmission method described in the embodiment of the present application (for example, in the protocol data transmission device) Capability information receiving module 210 and data transmission module 220).
  • the memory 32 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application required by a function; the data storage area may store data created according to the use of network nodes, and the like.
  • the memory 32 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage devices.
  • the memory 32 may further include a memory that is remotely located relative to the processor 31, and these remote memories may be connected to a network node through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the embodiment of the present application further provides a storage medium, the storage medium stores a computer program, and when the computer program is executed by a processor, the protocol data transmission method described in any one of the embodiments of the present application is implemented.
  • the method includes: receiving the first LLDP protocol frame sent by the peer node, the first LLDP protocol frame carrying the multi-frame transmission capability information of the peer node; according to the multi-frame transmission capability information of the local node and the The multi-frame transmission capability information of the opposite node, and the second LLDP protocol frame is transmitted with the opposite node, and the second LLDP protocol frame carries protocol data.
  • the computer storage medium in the embodiments of the present application may use any combination of one or more computer-readable media.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer-readable storage medium may be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination thereof. More specific examples (non-exhaustive list) of computer-readable storage media include: electrical connections with one or more conductors, portable computer disks, hard disks, Random Access Memory (RAM), read-only memory (Read Only Memory, ROM), Erasable Programmable Read Only Memory (EPROM), flash memory, optical fiber, portable CD-ROM, optical storage device, magnetic storage device, or any suitable combination of the above .
  • a computer readable storage medium may be any tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device.
  • a computer readable signal medium may include a data signal carrying computer readable program code in baseband or as part of a carrier wave. Such propagated data signals may take many forms, including but not limited to: electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • a computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. .
  • Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wires, optical cables, radio frequency (Radio Frequency, RF), etc., or any suitable combination of the above.
  • any appropriate medium including but not limited to: wireless, wires, optical cables, radio frequency (Radio Frequency, RF), etc., or any suitable combination of the above.
  • Computer program codes for performing the operations of the present application may be written in one or more programming languages or combinations thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional A procedural programming language, such as the "C" language or similar programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer can be connected to the user computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (such as through the Internet using an Internet service provider). connect).
  • LAN local area network
  • WAN wide area network
  • connect such as AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.
  • user terminal covers any suitable type of wired or wireless user equipment, such as a computer, mobile phone, portable data processing device, portable web browser or vehicle-mounted mobile station.
  • the various embodiments of the present application can be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
  • Computer program instructions may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages source or object code.
  • ISA Instruction Set Architecture
  • Any logic flow block diagrams in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules and functions, or may represent a combination of program steps and logic circuits, modules and functions.
  • Computer programs can be stored on memory.
  • the memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as but not limited to Read-Only Memory (ROM), Random Access Memory (RAM), Optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD), etc.
  • Computer-readable media may include non-transitory storage media.
  • Data processors may be any Types, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application-specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic devices (Field-Programmable Gate Array , FGPA) and processors based on multi-core processor architectures.
  • DSP Digital Signal Processing
  • ASIC Application Specific Integrated Circuit
  • FGPA programmable logic devices
  • processors based on multi-core processor architectures.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Communication Control (AREA)

Abstract

一种协议数据传输方法、装置、网络节点及存储介质。该方法接收对端节点发送的第一链路层发现协议LLDP协议帧，所述第一LLDP协议帧中携带所述对端节点的多帧传输能力信息(110)；根据本端节点的多帧传输能力信息和所述对端节点的多帧传输能力信息，与所述对端节点传输第二LLDP协议帧，所述第二LLDP协议帧携带协议数据(120)。

Description

协议数据传输方法、装置、网络节点及存储介质
相关申请的交叉引用
本申请基于申请号为202110756336.0，申请日为2021年07月05日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及数据通信网络技术领域，例如涉及一种协议数据传输方法、装置、网络节点及存储介质。
背景技术
国际标准组织电气与电子工程师协会(Institute of Electrical and Electronics Engineers，IEEE)制定标准规定了链路层发现协议(Link Layer Discovery Protocol，LLDP)的协议数据和协议工作机制。根据规定，LLDP协议运行于相邻的两个网络节点之间，且这两个相邻的网络节点可相互发送LLDP协议帧。LLDP协议数据以类型长度取值(Type Length Value，TLV)的形式携带在LLDP协议帧当中，并且以单帧的方式传输。
然而，随着LLDP协议的应用越来越广泛，LLDP协议帧需要携带的协议数据也越来越多。由于LLDP协议帧是一种以太帧(Ethernet Frame)，它的长度受限于IEEE规定的以太帧最大长度即1500字节，在大部分应用场景中，需要传输的LLDP协议数据量已经超出了单个LLDP协议帧的最大长度，单帧传输的方式具有较大的局限性，传输效率偏低，不能满足实际需求。
发明内容
本申请提供一种协议数据传输方法、装置、网络节点及存储介质，以提高协议数据的传输效率和灵活性。
本申请实施例提供一种协议数据传输方法，包括：接收对端节点发送的第一LLDP协议帧，所述第一LLDP协议帧中携带所述对端节点的多帧传输能力信息；根据本端节点的多帧传输能力信息和所述对端节点的多帧传输能力信息，与所述对端节点传输第二LLDP协议帧，所述第二LLDP协议帧携带协议数据。
本申请实施例还提供了一种协议数据传输装置，包括：能力信息接收模块，设置为接收对端节点发送的第一LLDP协议帧，所述第一LLDP协议帧中携带所述对端节点的多帧传输能力信息；数据传输模块，设置为根据本端节点的多帧传输能力信息和所述对端节点的多帧传输能力信息，与所述对端节点传输第二LLDP协议帧，所述第二LLDP协议帧携带协议数据。
本申请实施例还提供了一种网络节点，包括：存储器、处理器以及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现上述的协议数据传输方法。
本申请实施例还提供了一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该程序被处理器执行时实现上述的协议数据传输方法。
附图说明
图1为一实施例提供的一种协议数据传输方法的流程图；
图2为一实施例提供的第一LLDP协议帧的示意图；
图3为一实施例提供的第二LLDP协议帧携带扩展协议数据目录的示意图；
图4为一实施例提供的第二LLDP协议帧携带扩展协议数据标识的示意图；
图5为一实施例提供的第二LLDP协议帧携带扩展协议数据终结指示的示意图；
图6为一实施例提供的第三LLDP协议帧的示意图；
图7为另一实施例提供的第三LLDP协议帧的示意图；
图8为一实施例提供的一种协议数据传输装置的结构示意图；
图9为一实施例提供的一种网络节点的硬件结构示意图。
具体实施方式
下面结合附图和实施例对本申请进行说明。可以理解的是，此处所描述的具体实施例仅仅用于解释本申请，而非对本申请的限定。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。另外还需要说明的是，为了便于描述，附图中仅示出了与本申请相关的部分而非全部结构。
在本申请实施例中，提出了一种协议数据传输方法，根据本端节点和对端节点的多帧传输能力传输协议数据，解决了需要传输的LLDP协议数据的数据量超出单个LLDP协议帧的最大长度限制的问题，提高了传输效率以及传输的灵活性。
图1为一实施例提供的一种协议数据传输方法的流程图。如图1所示，本实施例提供的方法包括步骤110和步骤120。
在步骤110中，接收对端节点发送的第一链路层发现协议LLDP协议帧，所述第一LLDP协议帧中携带所述对端节点的多帧传输能力信息。
本实施例中，多帧传输能力信息用于表示一个网络节点是否支持多帧LLDP的接收和/或发送。本端节点和对端节点通常为两个相邻的网络节点，通过交互各自的多帧传输能力信息，可以确定两节点之间是否支持多帧传输。以本端节点为例，本端节点可以根据对端节点发送的第一LLDP协议帧所携带的多帧传输能力信息，确定对端节点是否支持多帧LLDP传输。两节点的多帧传输能力影响到在不同传输方向(例如本端节点发送-对端节点接收，或者对端节点发送-本端节点接收)协议数据是以多帧还是单帧的方式传输。
在步骤120中，根据本端节点的多帧传输能力信息和所述对端节点的多帧传输能力信息，与所述对端节点传输第二LLDP协议帧，所述第二LLDP协议帧携带协议数据。
本实施例中，第二LLDP协议帧可能为单帧，也可能包括多帧。本端节点可能支持多帧LLDP接收和/或多帧LLDP发送，对端节点也可能支持多帧LLDP接收和/或多帧LLDP发送。对于两节点多帧传输能力的不同情况，在不同传输方向传输协议数据的方式也不同。例如，本端节点支持多帧LLDP接收、不支持多帧LLDP发送，对端节点支持多帧LLDP发送、不支持多帧LLDP接收，则在对端节点发送-本端节点接收的过程中，可以通过多帧LLDP传输协议数据，从而提高传输数据量、提高传输效率；而在本端节点发送-对端节点接收的过程中，则只能通过单帧LLDP传输协议数据，这种情况下传输数据量受到限制。
此外，本端节点也可以通过发送LLDP协议帧向对端节点指示本端节点的多帧传输能力 信息，以使对端节点也能够明确两节点之间在不同传输方向的传输方式是单帧还是多帧。
在传输第二LLDP协议帧的过程中，本端节点可以作为协议数据的发送端，也可以作为协议数据的接收端。
本实施例通过第一LLDP协议帧指示多帧传输能力信息，在此基础上通过第二LLDP协议帧在相应传输方向以单帧或多帧的方式传输协议数据，提高了协议数据的传输效率和灵活性。
在一实施例中，步骤110，多帧传输能力信息包括以下至少之一：支持多帧LLDP发送；支持多帧LLDP接收；支持多帧LLDP收发；不支持多帧LLDP发送；不支持多帧LLDP接收；不支持多帧LLDP收发。
本实施例中，本端节点与对端节点的多帧传输能力主要分为以下三种情况。
情况一：两个节点都既支持多帧LLDP发送，又支持多帧LLDP接收(也可以理解为两个节点都支持多帧LLDP收发)，这种情况下，在各传输方向上都可以实现协议数据的多帧传输。
情况二：一个节点支持多帧LLDP发送，另一个节点支持多帧LLDP接收，这种情况下，在相应的传输方向上可以实现协议数据的多帧传输。
情况三：两个节点都不支持多帧LLDP发送，和/或两个节点都不支持多帧LLDP接收(包括两个节点都不支持多帧LLDP收发的情况)，这种情况下，在各传输方向上都只能采用已有的单帧LLDP工作模式，对协议数据进行单帧传输。
在一实施例中，步骤120，包括：在本端节点支持多帧LLDP发送、且对端节点支持多帧LLDP接收的情况下，向对端节点发送第二LLDP协议帧；其中，第二LLDP协议帧包括多个LLDP协议帧。
本实施例中，在本端节点发送-对端节点接收的传输方向上可以支持多帧传输，即第二LLDP协议帧包括多个LLDP协议帧，相比于单帧传输的工作模式可以携带更多的协议数据，提高传输效率。
本实施例中，第二LLDP协议帧携带扩展协议数据目录、扩展协议数据标识、扩展协议数据以及扩展协议数据终结指示。其中，扩展协议数据目录TLV通过目录的形式列出所有在后续的LLDP协议帧中传输的扩展协议数据；扩展协议数据标识用于具体标识待传输的扩展协议数据，且应与扩展协议数据目录中的各目录项对应；扩展协议数据指的是在第二LLDP协议帧中的第一个LLDP帧中未能传输、需要利用第二个及之后的LLDP帧传输的协议数据；扩展协议数据终结指示作为扩展协议数据传输的结束标志。在此基础上实现了超出单个LLDP协议帧最大长度限制的数据量的传输。
例如，第二LLDP协议帧包括多个LLDP协议帧，其中第一个LLDP协议帧携带了部分本端节点发送给对端节点的协议数据以及扩展协议数据目录，第二个及其之后的LLDP协议帧携带了扩展协议数据标识以及相应的扩展协议数据，最后一个LLDP协议帧携带扩展协议数据终结指示，表明该LLDP协议帧为本组多个LLDP协议帧中的最后一个。为了利用尽可能少的LLDP协议帧完成所有协议数据的传输，每个LLDP协议帧在满足最大长度限制的前提下，都应携带尽可能多的数据。
需要说明的是，本实施例通过将扩展协议数据目录、扩展协议数据标识、扩展协议数据以及扩展协议数据终结指示通过一组多个LLDP帧传输，无需对端节点针对目录反馈数据请求，避免了多帧LLDP协议数据传输的滞后性。
在一实施例中，该方法还包括步骤130。
步骤130：接收所述对端节点发送的第三LLDP协议帧，所述第三LLDP协议帧携带以下至少之一：协议数据传输成功指示；协议数据传输失败指示；传输失败的协议数据标识。
本实施例中，第三LLDP协议帧用于反映协议数据的传输结果。例如，对端节点接收到的第二LLDP协议帧中第一个LLDP协议帧携带扩展协议数据目录，第二个及其之后的LLDP协议帧携带扩展协议数据标识及相应的扩展协议数据，在此基础上，对端节点对比扩展协议数据目录与接收到的扩展协议数据标识的集合是否一致，如果一致，说明对端节点已成功接收到扩展协议数据目录列出的所有扩展协议数据，这些扩展协议数据与第二LLDP协议帧中第一个LLDP协议帧中的协议数据即为所有需要传输的协议数据，这种情况下，对端节点则可向本端节点发送第三LLDP协议帧，其中携带协议数据传输成功指示；如果不一致，则对端节点可通过第三LLDP协议帧发送协议数据传输失败指示，和/或在第三LLDP协议帧中列出扩展协议数据目录中未被成功接收的扩展协议数据对应的扩展协议数据标识，为传输失败的协议数据的重传提供依据。
在一实施例中，步骤120，包括：在本端节点支持多帧LLDP接收、且对端节点支持多帧LLDP发送的情况下，接收对端节点发送的第二LLDP协议帧；其中，第二LLDP协议帧包括多个LLDP协议帧。
第二LLDP协议帧还携带以下信息：扩展协议数据目录、扩展协议数据标识、扩展协议数据以及扩展协议数据终结指示。
本实施例中，在对端节点发送-本端节点接收的传输方向上可以支持多帧传输，第二LLDP协议帧包括多个LLDP协议帧，并且携带了对端节点发送给本端节点的协议数据，以及扩展协议数据目录、扩展协议数据标识、扩展协议数据以及扩展协议数据终结指示，相比于单帧传输的工作模式可以携带更多的协议数据，提高传输效率。
在一实施例中，该方法还包括步骤140。
步骤140：对比扩展协议数据目录与扩展协议数据标识，得到协议数据的传输结果。
本实施例中，本端节点在接收到对端节点的第二LLDP协议帧后，通过对比对端节点发送的扩展协议数据目录及扩展协议数据标识，判断是否成功接收所有协议数据，得到协议数据的传输结果。传输结果包括传输成功、传输失败和/或部分数据传输失败。
在一实施例中，该方法还包括步骤150。
步骤150：根据所述协议数据的传输结果向所述对端节点发送第四LLDP协议帧，其中，所述第四LLDP协议帧携带以下至少之一：协议数据传输成功指示；协议数据传输失败指示；传输失败的协议数据标识。
本实施例中，本端节点根据协议数据的传输结果，向对端节点发送第四LLDP协议帧，以指示协议数据是否传输成功，还可以指示传输失败的协议数据标识，为传输失败的协议数据的重传提供依据。
在一实施例中，扩展协议数据标识为扩展协议数据目录的子集。
本实施例中，第二LLDP协议帧中携带的扩展协议数据标识为扩展协议数据目录的子集。如果不满足该关系，说明协议数据的传输有误。
在一实施例中，步骤120，包括：在本端节点不支持多帧LLDP发送、或对端节点不支持多帧LLDP接收的情况下，向对端节点发送第二LLDP协议帧，第二LLDP协议帧包括单个LLDP协议帧。
本实施例中，在本端节点发送-对端节点接收的传输方向上不支持多帧传输，本端节点发送的第二LLDP协议帧包括单个LLDP协议帧，虽然传输数据量受到限制，但由于两节点预先交互了多帧传输能力信息，能够灵活确定在该传输方向上的传输方式，从而保证两节点之间协议数据的可靠性。
在一实施例中，步骤120，包括：在本端节点不支持多帧LLDP接收、或对端节点不支持多帧LLDP发送的情况下，接收对端节点发送的第二LLDP协议帧，第二LLDP协议帧包括单个LLDP协议帧。
本实施例中，在对端节点发送-本端节点接收的传输方向上不支持多帧传输，本端节点接收的第二LLDP协议帧包括单个LLDP协议帧，由于两节点预先交互了多帧传输能力信息，能够灵活确定在该传输方向上的传输方式，从而保证两节点之间协议数据的可靠性。
在一实施例中，步骤120，包括：在本端节点和对端节点不支持多帧LLDP接收的情况下，或者本端节点和对端节点不支持多帧LLDP发送的情况下，与对端节点传输第二LLDP协议帧，第二LLDP协议帧包括单个LLDP协议帧。
本实施例中，在本端节点发送-对端节点接收、以及对端节点发送-本端节点接收的传输方向上均不支持多帧传输，则第二LLDP协议帧包括单个LLDP协议帧，以单帧传输的工作模式实现两节点之间协议数据传输。
本实施例的协议数据传输方法，可适用于具有任意多帧传输能力的网络节点，即便是在有网络节点不支持多帧LLDP的接收和/或发送的情况下，也可以保证协议数据的有效传输。
以下通过具体示例对协议数据传输方法进行举例说明。
示例一
两个相邻的网络节点(节点A和节点B)都支持多帧LLDP的发送和接收，两个传输方向上待传输的数据都超过了单个LLDP协议帧的长度限制，且都需要3个LLDP协议帧完成传输。
首先，节点A向节点B发送第一LLDP协议帧，其中携带节点A的多帧传输能力信息。此外，节点B也向节点A发送一个第一LLDP协议帧，其中携带节点B的多帧传输能力信息。图2为一实施例提供的第一LLDP协议帧的示意图。如图2所示，通过在第一LLDP协议帧中携带多帧LLDP传输能力(即多帧传输能力信息)TLV以通知对端节点自身对多帧传输的支持能力。
其次，节点A向节点B发送第二LLDP协议帧，第二LLDP协议帧包括三个LLDP协议帧，其中，第一个LLDP协议帧携带扩展协议数据目录，第二个及第三个LLDP协议帧携带扩展协议数据标识及相应的扩展协议数据，第三个LLDP协议帧还携带扩展协议数据终结指示。图3为一实施例提供的第二LLDP协议帧携带扩展协议数据目录的示意图。如图3所示，通过在LLDP协议帧中携带扩展协议数据目录TLV向对端节点通告需要传输的扩展协议数据，也即除本LLDP协议帧携带的协议数据之外还需要通过其他LLDP协议帧传输的协议数据，扩展协议数据目录具体可通过所有扩展协议数据的标识来表示。此外，节点B向节点A发送的第一个LLDP协议帧格式与图3一致，区别在于是针对不同传输方向的协议数据和扩展协议数据。
然后，节点A向节点B发送的第二个LLDP协议帧携带扩展协议数据标识。图4为一实施例提供的第二LLDP协议帧携带扩展协议数据标识的示意图。如图4所示，通过在LLDP协议帧中携带扩展协议数据标识TLV向对端节点通告该LLDP协议帧传输的扩展协议数据，也即有哪些扩展数据是由本LLDP协议帧携带的。节点B向节点A发送的第二个LLDP协议帧格 式与图4一致。
再然后，节点A向节点B发送的第三个LLDP协议帧携带了扩展协议数据终结指示。图5为一实施例提供的第二LLDP协议帧携带扩展协议数据终结指示的示意图。如图5所示，通过在LLDP协议帧中携带扩展协议数据终结指示TLV向对端节点通告该LLDP协议帧是本组LLDP协议帧中的最后一个。此外，节点B向节点A发送的第三个LLDP协议帧格式与图5一致。
最后，节点B接收到节点A发送的三个LLDP协议帧后，对比第一个LLDP协议帧携带的扩展协议数据目录及第二个和第三个LLDP协议帧携带的扩展协议数据标识，判断是否成功接收所有协议数据，并向节点A发送用于指示协议数据传输结果的第三LLDP协议帧。此外，节点A在接收到节点B发送的第二LLDP协议帧后，也可以根据协议数据传输结果向节点B发送第四LLDP协议帧。
如果节点B判断传输结果为成功接收所有协议数据，则向节点A发送携带协议数据传输成功指示的第三LLDP协议帧。图6为一实施例提供的第三LLDP协议帧的示意图。如图6所示，通过在LLDP协议帧中携带的扩展协议数据接收成功指示(即协议数据传输成功指示)TLV通告节点B成功接收所有协议数据。此外，如果节点A判断传输结果为成功接收节点B的所有协议数据，则第四LLDP协议帧的格式与图6一致。
如果节点B判断传输结果为未成功接收所有协议数据，则向节点A发送携带协议数据传输失败指示的第三LLDP协议帧。图7为另一实施例提供的第三LLDP协议帧的示意图。如图7所示，通过在LLDP协议帧中携带的扩展协议数据接收失败指示(即协议数据传输失败指示)TLV通告节点B未成功接收所有协议数据，并列出扩展协议数据目录中未被成功接收的扩展协议数据的扩展协议数据标识。此外，如果节点A判断传输结果为未成功接收节点B的所有协议数据，则第四LLDP协议帧的格式与图7一致。
示例二
两个相邻网络节点(节点A和节点B)，节点A只支持多帧LLDP发送，节点B只支持多帧LLDP接收。在节点A发送给节点B的传输方向上，待传输的协议数据超过了单个LLDP协议帧的长度限制，需要2个LLDP协议帧进行传输；在节点B往节点A的方向上待传输的协议数据未超过单个LLDP协议帧的长度限制。
首先，节点A向节点B发送第一LLDP协议帧，其中携带节点A的多帧LLDP传输能力(即多帧传输能力信息：只支持多帧LLDP发送，不支持多帧LLDP接收)TLV。节点B向节点A发送第一LLDP协议帧，其中携带节点B的多帧LLDP传输能力(即多帧传输能力信息：只支持多帧LLDP接收，不支持多帧LLDP发送)TLV。
其次，节点A向节点B发送第二LLDP协议帧，包括两个LLDP协议帧，其中第一个LLDP协议帧携带扩展协议数据目录，第二个LLDP协议帧携带扩展协议数据标识及相应的扩展协议数据，同时还携带扩展协议数据终结指示。节点B向节点A发送的第二LLDP协议帧，包括单个LLDP协议帧，携带了待传输的协议数据及协议数据终结指示。
然后，节点B接收到节点A发送的两个LLDP协议帧后，对比第一个LLDP协议帧携带的扩展协议数据目录及第二个LLDP协议帧携带的扩展协议数据标识，判断是否成功接收所有协议数据，并根据传输结果向节点A发送用于指示传输结果的第三LLDP协议帧。节点A接收到节点B发送的单个LLDP协议帧后，取出协议数据保存到本地数据库。
示例三
两个相邻网络节点(节点A和节点B)中，节点A支持多帧LLDP发送和接收，节点B不支持多帧LLDP的发送和接收。
首先，节点A向节点B发送第一LLDP协议帧，其中携带多帧LLDP传输能力(即多帧传输能力信息：支持多帧LLDP收发)TLV。节点B向节点A发送LLDP协议帧，其中不携带多帧LLDP能力TLV，表明节点B只支持单帧LLDP的发送和接收，而不支持多帧LLDP的发送和接收。
然后，节点A与节点B之间传输第二LLDP协议帧，此过程中通过单个LLDP协议帧传输协议数据。由于节点B不支持多帧LLDP的发送和接收，即使节点A支持多帧LLDP收发，两节点之间也不会传输多帧LLDP，只能采用单帧传输的方式。
在上述示例中，参见图2至图7，第二LLDP协议帧还可以携带LLDP目的介质访问控制(Media Access Control，MAC)地址、LLDP源MAC地址、LLDP以太类型、机架标识、端口标识、生存时间等信息。
本申请实施例还提供一种协议数据传输装置。图8为一实施例提供的一种协议数据传输装置的结构示意图。如图8所示，所述协议数据传输装置包括能力信息接收模块210和数据传输模块220。
能力信息接收模块210，设置为接收对端节点发送的第一LLDP协议帧，所述第一LLDP协议帧中携带所述对端节点的多帧传输能力信息。
数据传输模块220，设置为根据本端节点的多帧传输能力信息和所述对端节点的多帧传输能力信息，与所述对端节点传输第二LLDP协议帧，所述第二LLDP协议帧携带协议数据。
本实施例的协议数据传输装置，通过第一LLDP协议帧指示多帧传输能力信息，在此基础上通过第二LLDP协议帧在相应传输方向以单帧或多帧的方式传输协议数据，解决了需要传输的LLDP协议数据的数据量超出单个LLDP协议帧的最大长度限制的问题，提高了传输效率以及传输的灵活性。
在一实施例中，多帧传输能力信息包括以下至少之一：支持多帧LLDP发送；或支持多帧LLDP接收；或支持多帧LLDP收发；或不支持多帧LLDP发送；或不支持多帧LLDP接收；或不支持多帧LLDP收发。
在一实施例中，数据传输模块220，具体设置为：在所述本端节点支持多帧LLDP发送、且所述对端节点支持多帧LLDP接收的情况下，向所述对端节点发送第二LLDP协议帧。
其中，所述第二LLDP协议帧包括多个LLDP协议帧。
所述第二LLDP协议帧还携带以下信息：扩展协议数据目录、扩展协议数据标识、扩展协议数据以及扩展协议数据终结指示。
在一实施例中，该装置还包括传输结果接收模块。
传输结果接收模块，设置为接收所述对端节点发送的第三LLDP协议帧，所述第三LLDP协议帧携带以下至少之一：协议数据传输成功指示；或协议数据传输失败指示；或传输失败的协议数据标识。
在一实施例中，数据传输模块220，具体设置为：在所述本端节点支持多帧LLDP接收、且所述对端节点支持多帧LLDP发送的情况下，接收所述对端节点发送的第二LLDP协议帧。
其中，所述第二LLDP协议帧包括多个LLDP协议帧。
所述第二LLDP协议帧还携带以下信息：扩展协议数据目录、扩展协议数据标识、扩展协议数据以及扩展协议数据终结指示。
在一实施例中，该装置还包括对比模块。
对比模块，设置为对比所述扩展协议数据目录与所述扩展协议数据标识，得到所述协议数据的传输结果。
在一实施例中，该装置还包括传输结果发送模块。
传输结果发送模块，设置为根据所述协议数据的传输结果向所述对端节点发送第四LLDP协议帧，其中，所述第四LLDP协议帧携带以下至少之一：协议数据传输成功指示；或协议数据传输失败指示；或传输失败的协议数据标识。
在一实施例中，扩展协议数据标识为所述扩展协议数据目录的子集。
在一实施例中，数据传输模块220，具体设置为：在所述本端节点不支持多帧LLDP发送、或所述对端节点不支持多帧LLDP接收的情况下，向所述对端节点发送第二LLDP协议帧，所述第二LLDP协议帧包括单个LLDP协议帧。
在一实施例中，数据传输模块220，具体设置为：在所述本端节点不支持多帧LLDP接收、或所述对端节点不支持多帧LLDP发送的情况下，接收所述对端节点发送的第二LLDP协议帧，所述第二LLDP协议帧包括单个LLDP协议帧。
在一实施例中，数据传输模块220，具体设置为：在所述本端节点和所述对端节点不支持多帧LLDP接收的情况下，或者所述本端节点和所述对端节点不支持多帧LLDP发送的情况下，与所述对端节点传输第二LLDP协议帧，所述第二LLDP协议帧包括单个LLDP协议帧。
本实施例提出的协议数据传输装置与上述实施例提出的协议数据传输方法属于同一发明构思，未在本实施例中详尽描述的技术细节可参见上述任意实施例，并且本实施例具备与执行协议数据传输方法相同的有益效果。
本申请实施例还提供了一种网络节点，图9为一实施例提供的一种网络节点的硬件结构示意图，如图9所示，本申请提供的网络节点，包括存储器32、处理器31以及存储在存储器上并可在处理器上运行的计算机程序，处理器31执行所述程序时实现上述的协议数据传输方法。
网络节点还可以包括存储器32；该网络节点中的处理器31可以是一个或多个，图9中以一个处理器31为例；存储器32用于存储一个或多个程序；所述一个或多个程序被所述一个或多个处理器31执行，使得所述一个或多个处理器31实现如本申请实施例中所述的协议数据传输方法。
网络节点还包括：通信装置33、输入装置34和输出装置35。
网络节点中的处理器31、存储器32、通信装置33、输入装置34和输出装置35可以通过总线或其他方式连接，图9中以通过总线连接为例。
输入装置34可用于接收输入的数字或字符信息，以及产生与网络节点的用户设置以及功能控制有关的按键信号输入。输出装置35可包括显示屏等显示设备。
通信装置33可以包括接收器和发送器。通信装置33设置为根据处理器31的控制进行信息收发通信。
存储器32作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请实施例所述协议数据传输方法对应的程序指令/模块(例如，协议数据 传输装置中的能力信息接收模块210和数据传输模块220)。存储器32可包括存储程序区和存储数据区，其中，存储程序区可存储操作***、至少一个功能所需的应用程序；存储数据区可存储根据网络节点的使用所创建的数据等。此外，存储器32可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器32可进一步包括相对于处理器31远程设置的存储器，这些远程存储器可以通过网络连接至网络节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
本申请实施例还提供一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现本申请实施例中任一所述的协议数据传输方法。该方法，包括：接收对端节点发送的第一LLDP协议帧，所述第一LLDP协议帧中携带所述对端节点的多帧传输能力信息；根据本端节点的多帧传输能力信息和所述对端节点的多帧传输能力信息，与所述对端节点传输第二LLDP协议帧，所述第二LLDP协议帧携带协议数据。
本申请实施例的计算机存储介质，可以采用一个或多个计算机可读的介质的任意组合。计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质。计算机可读存储介质例如可以是，但不限于：电、磁、光、电磁、红外线、或半导体的***、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子(非穷举的列表)包括：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机存取存储器(Random Access Memory，RAM)、只读存储器(Read Only Memory，ROM)、可擦式可编程只读存储器(Erasable Programmable Read Only Memory，EPROM)、闪存、光纤、便携式CD-ROM、光存储器件、磁存储器件、或者上述的任意合适的组合。计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行***、装置或者器件使用或者与其结合使用。
计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于：电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行***、装置或者器件使用或者与其结合使用的程序。
计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于：无线、电线、光缆、无线电频率(Radio Frequency，RF)等等，或者上述的任意合适的组合。
可以以一种或多种程序设计语言或其组合来编写用于执行本申请操作的计算机程序代码，所述程序设计语言包括面向对象的程序设计语言，诸如Java、Smalltalk、C++，还包括常规的过程式程序设计语言，诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中，远程计算机可以通过任意种类的网络，包括局域网(LAN)或广域网(WAN)，连接到用户计算机，或者，可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。
以上所述，仅为本申请的若干实施例而已，并非用于限定本申请的保护范围。
本领域内的技术人员应明白，术语用户终端涵盖任何适合类型的有线或无线用户设备，例如计算机、移动电话、便携数据处理装置、便携网络浏览器或车载移动台。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(Read-Only Memory，ROM)、随机访问存储器(Random Access Memory，RAM)、光存储器装置和***(数码多功能光碟(Digital Video Disc，DVD)或光盘(Compact Disk，CD)等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field-Programmable Gate Array，FGPA)以及基于多核处理器架构的处理器。
通过若干非限制性的示例，上文已提供了对本申请的若干实施例的详细描述。但结合附图和权利要求来考虑，对以上实施例的多种修改和调整对本领域技术人员来说是显而易见的，但不偏离本申请的范围。因此，本申请的恰当范围将根据权利要求确定。

Claims (14)

  1. 一种协议数据传输方法，包括：
    接收对端节点发送的第一链路层发现协议LLDP协议帧，所述第一LLDP协议帧中携带所述对端节点的多帧传输能力信息；
    根据本端节点的多帧传输能力信息和所述对端节点的多帧传输能力信息，与所述对端节点传输第二LLDP协议帧，所述第二LLDP协议帧携带协议数据。
  2. 根据权利要求1所述的方法，其中，多帧传输能力信息包括以下至少之一：
    支持多帧LLDP发送；或支持多帧LLDP接收；或支持多帧LLDP收发；或不支持多帧LLDP发送；或不支持多帧LLDP接收；或不支持多帧LLDP收发。
  3. 根据权利要求2所述的方法，其中，根据本端节点的多帧传输能力信息和所述对端节点的多帧传输能力信息，与所述对端节点传输第二LLDP协议帧，包括：
    在所述本端节点支持多帧LLDP发送、且所述对端节点支持多帧LLDP接收的情况下，向所述对端节点发送第二LLDP协议帧；
    其中，所述第二LLDP协议帧包括多个LLDP协议帧；
    所述第二LLDP协议帧还携带以下信息：扩展协议数据目录、扩展协议数据标识、扩展协议数据以及扩展协议数据终结指示。
  4. 根据权利要求3所述的方法，还包括：
    接收所述对端节点发送的第三LLDP协议帧，所述第三LLDP协议帧携带以下至少之一：
    协议数据传输成功指示；或协议数据传输失败指示；或传输失败的协议数据标识。
  5. 根据权利要求2所述的方法，其中，根据本端节点的多帧传输能力信息和所述对端节点的多帧传输能力信息，与所述对端节点传输第二LLDP协议帧，包括：
    在所述本端节点支持多帧LLDP接收、且所述对端节点支持多帧LLDP发送的情况下，接收所述对端节点发送的第二LLDP协议帧；
    其中，所述第二LLDP协议帧包括多个LLDP协议帧；
    所述第二LLDP协议帧还携带以下信息：扩展协议数据目录、扩展协议数据标识、扩展协议数据以及扩展协议数据终结指示。
  6. 根据权利要求5所述的方法，还包括：
    对比所述扩展协议数据目录与所述扩展协议数据标识，得到所述协议数据的传输结果。
  7. 根据权利要求6所述的方法，还包括：
    根据所述协议数据的传输结果向所述对端节点发送第四LLDP协议帧，其中，所述第四LLDP协议帧携带以下至少之一：协议数据传输成功指示；或协议数据传输失败指示；或传输失败的协议数据标识。
  8. 根据权利要求3或5所述的方法，其中，
    所述扩展协议数据标识为所述扩展协议数据目录的子集。
  9. 根据权利要求2所述的方法，其中，根据本端节点的多帧传输能力信息和所述对端节点的多帧传输能力信息，与所述对端节点传输第二LLDP协议帧，包括：
    在所述本端节点不支持多帧LLDP发送、或所述对端节点不支持多帧LLDP接收的情况下，向所述对端节点发送第二LLDP协议帧，所述第二LLDP协议帧包括单个LLDP协议帧。
  10. 根据权利要求2所述的方法，其中，根据本端节点的多帧传输能力信息和所述对端节点的多帧传输能力信息，与所述对端节点传输第二LLDP协议帧，包括：
    在所述本端节点不支持多帧LLDP接收、或所述对端节点不支持多帧LLDP发送的情况下，接收所述对端节点发送的第二LLDP协议帧，所述第二LLDP协议帧包括单个LLDP协议帧。
  11. 根据权利要求2所述的方法，其中，根据本端节点的多帧传输能力信息和所述对端节点的多帧传输能力信息，与所述对端节点传输第二LLDP协议帧，包括：
    在所述本端节点和所述对端节点不支持多帧LLDP接收的情况下，或者所述本端节点和所述对端节点不支持多帧LLDP发送的情况下，与所述对端节点传输第二LLDP协议帧，所述第二LLDP协议帧包括单个LLDP协议帧。
  12. 一种协议数据传输装置，包括：
    能力信息接收模块，设置为接收对端节点发送的第一链路层发现协议LLDP协议帧，所述第一LLDP协议帧中携带所述对端节点的多帧传输能力信息；
    数据传输模块，设置为根据本端节点的多帧传输能力信息和所述对端节点的多帧传输能力信息，与所述对端节点传输第二LLDP协议帧，所述第二LLDP协议帧携带协议数据。
  13. 一种网络节点，包括存储器、处理器以及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述程序时实现如权利要求1-11中任一项所述的协议数据传输方法。
  14. 一种计算机可读存储介质，其上存储有计算机程序，其中，该程序被处理器执行时实现如权利要求1-11中任一项所述的协议数据传输方法。
PCT/CN2022/087486 2021-07-05 2022-04-18 协议数据传输方法、装置、网络节点及存储介质 WO2023279802A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110756336.0 2021-07-05
CN202110756336.0A CN115589363A (zh) 2021-07-05 2021-07-05 协议数据传输方法、装置、网络节点及存储介质

Publications (1)

Publication Number Publication Date
WO2023279802A1 true WO2023279802A1 (zh) 2023-01-12

Family

ID=84771067

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/087486 WO2023279802A1 (zh) 2021-07-05 2022-04-18 协议数据传输方法、装置、网络节点及存储介质

Country Status (2)

Country Link
CN (1) CN115589363A (zh)
WO (1) WO2023279802A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1340945A (zh) * 2000-08-30 2002-03-20 美国阿尔卡塔尔资源有限合伙公司 利用实时承载协议传输承载业务的***和方法
US20090207860A1 (en) * 2006-12-30 2009-08-20 Liu Guoman Method, apparatus and system for transferring data
CN102971991A (zh) * 2010-04-23 2013-03-13 瑞典爱立信有限公司 通过分组交换网络在分组伪线上传送的分组的有效封装
IN201621009401A (zh) * 2016-03-17 2017-09-22 Tata Consultancy Services Limited
US20200159603A1 (en) * 2018-11-21 2020-05-21 Cisco Technology, Inc. Return and replacement protocol (rrp)
CN111953585A (zh) * 2019-05-14 2020-11-17 现代自动车株式会社 网关装置及其控制方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1340945A (zh) * 2000-08-30 2002-03-20 美国阿尔卡塔尔资源有限合伙公司 利用实时承载协议传输承载业务的***和方法
US20090207860A1 (en) * 2006-12-30 2009-08-20 Liu Guoman Method, apparatus and system for transferring data
CN102971991A (zh) * 2010-04-23 2013-03-13 瑞典爱立信有限公司 通过分组交换网络在分组伪线上传送的分组的有效封装
IN201621009401A (zh) * 2016-03-17 2017-09-22 Tata Consultancy Services Limited
US20200159603A1 (en) * 2018-11-21 2020-05-21 Cisco Technology, Inc. Return and replacement protocol (rrp)
CN111953585A (zh) * 2019-05-14 2020-11-17 现代自动车株式会社 网关装置及其控制方法

Also Published As

Publication number Publication date
CN115589363A (zh) 2023-01-10

Similar Documents

Publication Publication Date Title
JP7323696B2 (ja) マルチリンク通信方法および関連するデバイス
US20220060416A1 (en) Routing Rule Management Method and Communications Apparatus
US11812496B2 (en) User group session management method and apparatus
WO2019019906A1 (zh) 一种通信方法、设备及存储介质
US11838846B2 (en) Configuration method and controller
US20230261795A1 (en) Method for Retransmitting Data and Apparatus
WO2023124098A1 (zh) 用于在ieee 802.15.4网络中生成和发送应答帧的方法及通信装置
CN112422485B (zh) 一种传输控制协议的通信方法及装置
WO2019201127A1 (zh) 数据传输方法及装置
WO2020214469A1 (en) Efficient message transmission and loop avoidance in an rpl network
WO2022068744A1 (zh) 获取报文头信息、生成报文的方法、设备及存储介质
WO2020147081A1 (zh) 一种数据传输方法、相关设备及计算机存储介质
WO2021244262A1 (zh) 一种报文处理方法、设备及***
WO2016015606A1 (zh) 一种用于定位端口连接错误的方法和相关设备
WO2020177642A1 (zh) 一种以太网报文的传输方法、装置及***
WO2023279802A1 (zh) 协议数据传输方法、装置、网络节点及存储介质
CN116010130B (zh) Dpu虚拟口的跨卡链路聚合方法、装置、设备及介质
JP2011229093A (ja) ネットワーク装置
WO2023173876A1 (zh) 数据通信方法、装置、设备和介质
US20220217093A1 (en) Sequence Number Synchronization Method and Apparatus
CN111385069A (zh) 数据传输方法及计算机设备
CN114201311A (zh) 数据处理方法及装置
WO2019062555A1 (zh) 一种数据传输方法及装置
WO2021036621A1 (zh) 信息交互方法及相关设备
JP2023517081A (ja) 通信方法および装置

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: 22836561

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE