Method and apparatus for transmitting logical layer management message

Abstract

The present application relates to the field of communications, and provides a method and apparatus for transmitting a logical layer management message, improving the bandwidth utilization rate for service data transmission. The method comprises: packaging a logical layer management message into a logical layer management packet, wherein the logical layer management packet comprises a logical layer packet type (LLPT) domain, and the LLPT domain is assigned a first value to indicate that the current data packet type is the logical layer management packet; and filling a logical block with the logic layer management packet, wherein the logical block is further configured to be filled with a logical layer data packet in which transmission layer data is packaged, the logical layer data packet comprises an LLPT domain, and the LLPT domain is assigned a second value to indicate that the current data packet type is the logical layer data packet.

Description

A method and device for transmitting logical layer management messages Technical Field

[0001] The present application relates to the field of communications, and in particular to a method and device for transmitting logical layer management messages. Background Art

[0002] With the rapid development of communication technology, in addition to transmitting business data, interconnected devices also need to transmit management data to manage the link between them.

[0003] Currently, during service data transmission, each data unit occupies a fixed number of bytes to be used to fill the management message of the management link. However, if the management message occupies the fixed transmission space of service data, the bandwidth utilization rate of the service data transmission is low.

[0004] Summary of the Invention

[0005] The method and device for transmitting logical layer management messages provided in the present application solve the problem of transmission bandwidth being occupied by sending management messages, thereby improving bandwidth utilization for transmitting business data.

[0006] To achieve the above objectives, the present invention adopts the following technical solutions:

[0007] In a first aspect, a method for transmitting logical layer management messages is provided, which may include: encapsulating the logical layer management message into a logical layer management message, the logical layer management message including a logical layer packet type (Logical Layer Packet Type, LLPT) field, the LLPT field being assigned a first value to indicate that the current data message type is a logical layer management message; filling the logical layer management message into a logical block, the logical block being further used to fill a logical layer data message encapsulating transport layer data, the logical layer data message including an LLPT field, the LLPT field being assigned a second value to indicate that the current data message type is a logical layer data message.

[0008] The solution provided by this application configures a logical layer message type field in logical layer management messages, which indicates the message type. This field is used to identify different types of data messages, facilitating data decapsulation and recovery at the receiving end. This allows logical layer management messages to be dynamically inserted into logical blocks only when they are needed, based on link management requirements. This avoids reserving space for sending management data when none exists, and improves bandwidth utilization for service data transmission on inter-device links.

[0009] In a possible implementation, a single logic block includes at most two logic layer management messages.

[0010] In another possible implementation, after the logical layer management message is inserted into the logical block, the method provided by the present application further includes inserting the logical layer data message into the logical block. This ensures that the logical layer management message is inserted first in the logical block, allowing the receiving end to parse and obtain the logical layer management message in a timely manner, thereby ensuring timely link management.

[0011] In another possible implementation, a single logic block includes a logic layer data message.

[0012] In another possible implementation, the first value may be 0xF0, and the second value may be 0x0F.

[0013] In another possible implementation, the logical layer management message is a logical layer main link management message (Logical Layer Main Link Management Packet, LLMMP), and the length of the logical layer management message is 8 bytes. The logical layer management message consists of a logical layer packet header (Logical Layer Packet Header, LLPH), a logical layer packet payload (Logical Layer Packet Payload, LLPP) and a cyclic redundancy check (Cyclic Redundancy Check, CRC) code. The length of LLPH is 2 bytes, and LLPH includes an LLPT field. LLPH also includes a logical layer management message type (Logical Layer Management Message Type, LLMMT) field. The LLMMT field indicates the message type (type of management message) carried by the current LLMMP. The length of LLPP is 4 bytes; the length of the CRC code is 2 bytes. The CRC code is used to fill in the verification information of all parameters of the reserved field, LLMMT field and LLPP field of the current data message.

[0014] In another possible implementation, when forward error correction (FEC) is enabled, the above-mentioned logical block includes a block body and a block tail, the block body is filled with a logical layer management message and a logical layer data message, and the block tail corresponds to the FEC-encoded check information.

[0015] In another possible implementation, the method provided in the present application may further include: after filling the logical layer management message and the logical layer data message into the logical block, performing FEC encoding on the logical block.

[0016] In another possible implementation, the length of the logical block is 240 bytes, the block body is 230 bytes, and the block trailer is 10 bytes; alternatively, the length of the logical block is 480 bytes, the block body is 460 bytes, and the block trailer is 20 bytes. Specifically, when a logical block is populated with one logical layer management message, the first 8 bytes in the block body are populated with the logical layer management message; alternatively, when a logical block is populated with two logical layer management messages, the first 16 bytes in the block body are populated with the logical layer management message; alternatively, when a logical block is not populated with a logical layer management message, no bytes in the block body are populated with the logical layer management message.

[0017] In another possible implementation, when FEC is disabled, the logical block includes a block body, and the length of the block body is 240 bytes or 480 bytes. Specifically, when the logical block is populated with one logical layer management message, the first 8 bytes of the block body are populated with the logical layer management message; or, when the logical block is populated with two logical layer management messages, the first 16 bytes of the block body are populated with the logical layer management message; or, when the logical block is not populated with a logical layer management message, no bytes of the block body are populated with the logical layer management message.

[0018] In another possible implementation, the logical layer management message includes one or more of the following:

[0019] Link Training Start Message (TSM), the LLMMT field of TSM is configured to 0x11.

[0020] Alternatively, the clock lock feedback message (CLFM), the LLMMT field of the CLFM is configured to 0x12.

[0021] Alternatively, the clock lock feedback response message CLFM_ACK, the LLMMT field of CLFM_ACK is configured to 0x02.

[0022] Alternatively, in an Equilibrium Feedback Message (EQFM), the LLMMT field of the EQFM is configured to be 0x13.

[0023] Alternatively, the equalization feedback response message EQFM_ACK, the LLMMT field of EQFM_ACK is configured to 0x03.

[0024] Alternatively, the Lane Lock Feedback Message (LLFM), the LLMMT field of the LLFM is configured to 0x14.

[0025] Alternatively, in a low power request message (LPRM), the LLMMT field of the LPRM is configured to be 0x21.

[0026] Alternatively, in a Link Width Adjust Message (LWAM), the LLMMT field of the LPRM is configured to be 0x22.

[0027] Alternatively, in a Lane Direction Adjust Messsage (LDAM), the LLMMT field of the LDAM is configured to be 0x23.

[0028] Alternatively, the control frame sends location information (CF Send Location Message, CFSLM), and the LLMMT field of CFSLM is configured to 0x24.

[0029] Alternatively, the timestamp message (TM), the LLMMT field of the TM is configured to 0x25.

[0030] Alternatively, in the response message (Ack / Nack Message, Ack / Nack), the LLMMT field of Ack / Nack is configured to 0x2A.

[0031] Alternatively, the LLMMT field of the Error Report Message (ERR_RM) is configured to be 0x2B.

[0032] In another possible implementation, different logical layer management messages have different packet priorities. Logical layer management messages used for exception reporting and control frame transmission location messages have higher priority than other logical layer management messages. Other logical layer management messages include: link training start message, clock lock feedback message, equalization feedback message, channel lock feedback message, low power request message, link width adjustment message, channel direction adjustment message, and response message.

[0033] In another possible implementation, filling the to-be-transmitted messages into the logic block includes: filling the logic layer management messages into the logic block in descending order of packet priority.

[0034] On the second aspect, another method for transmitting logical layer management messages is provided, which may include: receiving a logical block; deblocking the logical block and identifying whether the logical block contains a logical layer management message; if it is identified that the logical block contains a logical layer management message, unpacking the logical layer management message.

[0035] The solution provided by this application first identifies and unpacks logical layer management messages after receiving a logical block to obtain logical layer management messages for link management. In a solution that distinguishes between logical layer management messages and logical layer data messages, logical layer management messages can be dynamically inserted into logical blocks only when logical layer management messages need to be transmitted, based on link management requirements. This avoids reserving space for sending management data when none exists, thereby improving bandwidth utilization for link transmission of service data between devices.

[0036] In another possible implementation, the logic block is deblocked to identify whether the logic block contains a logic layer management message, including: detecting the first byte of the logic block; if the first byte indicates a logic layer data message, then there is no logic layer management message in the logic block; if the first byte indicates a logic layer management message, detecting the ninth byte of the logic block; if the ninth byte indicates a logic layer data message, then the logic block contains one logic layer management message; if the ninth byte indicates a logic layer management message, then the logic block contains two logic layer management messages.

[0037] The first byte and the ninth byte of the logic block indicate the location of the LLPT field of the logic layer management message when the logic layer management message is filled in the logic block.

[0038] In another possible implementation, when FEC is enabled, the method provided in this application further includes: if the logical block contains a logical layer management message and there is no CRC error when the logical layer management message is unpacked, after FEC decoding, discarding the first 8 bytes of data when deblocking the logical block. If the logical block contains a logical layer management message and there is a CRC error when the logical layer management message is unpacked, after FEC decoding, deblocking the logical block starting from the first byte. If the logical block contains two logical layer management messages and there is no CRC error when the logical layer management messages are unpacked, discarding the first 16 bytes of data when deblocking the logical block after FEC decoding. If the logical block contains two logical layer management messages and there is no CRC error when the logical layer management messages are unpacked, the first logical layer management message has no CRC error and the second logical layer management message has a CRC error when the logical block is deblocked, discarding the first 8 bytes of data when deblocking the logical block after FEC decoding. If a logical block contains two logical layer management messages and the first logical layer management message has a CRC error when the logical layer management messages are depacketized, the logical block is depacketized starting from the first byte after FEC decoding.

[0039] To ensure the timeliness of logical layer management functions, when FEC is enabled, identified logical layer management messages are first depacketized during FEC decoding. After FEC decoding, the logical blocks must be deblocked again to identify the data messages populated within them. This deblocking process not only identifies unpacked logical layer data messages but also performs error correction and verification on logical layer management messages that contain CRC errors during depacketization, thereby improving the accuracy of logical layer management message transmission.

[0040] In another possible implementation, when FEC is not enabled, the method provided in the present application further includes: unpacking the logical layer data message for data other than the logical layer management message in the logical block.

[0041] In another possible implementation, a single logic block includes at most two logic layer management messages.

[0042] In another possible implementation, a logical layer data message is encapsulated in a single logical block.

[0043] In another possible implementation, the logical layer management message is an LLMMP, which is 8 bytes long. It consists of an LLPH, LLPP, and a CRC code. The LLPH is 2 bytes long and includes the LLPT field, which is assigned a value of 0xF0. The LLPH also includes the LLMMT field, which indicates the message type carried by the LLMMP. The LLPP is 4 bytes long, and the CRC is 2 bytes long. The CRC code is used to verify all parameters in the reserved field, LLMMT field, and LLPP field of the current data message.

[0044] In another possible implementation, when FEC is enabled, the logic block includes a block body and a block tail, the block body is filled with a logic layer management message and a logic layer data message, and the block tail corresponds to the FEC-coded check information.

[0045] The block tail corresponds to the FEC-coded check information, which refers to the check data obtained by filling the block tail with the FEC code.

[0046] In another possible implementation, the method provided in the present application may further include: after unpacking the logical layer management message, performing FEC decoding on the logical block.

[0047] In another possible implementation, the length of the logical block is 240 bytes, the block body is 230 bytes, and the block trailer is 10 bytes; alternatively, the length of the logical block is 480 bytes, the block body is 460 bytes, and the block trailer is 20 bytes. Specifically, when a logical block is populated with one logical layer management message, the first 8 bytes in the block body are populated with the logical layer management message; alternatively, when a logical block is populated with two logical layer management messages, the first 16 bytes in the block body are populated with the logical layer management message; alternatively, when a logical block is not populated with a logical layer management message, no bytes in the block body are populated with the logical layer management message.

[0048] In another possible implementation, when FEC is disabled, the logical block includes a block body, and the length of the block body is 240 bytes or 480 bytes. Specifically, when the logical block is populated with one logical layer management message, the first 8 bytes of the block body are populated with the logical layer management message; or, when the logical block is populated with two logical layer management messages, the first 16 bytes of the block body are populated with the logical layer management message; or, when the logical block is not populated with a logical layer management message, no bytes of the block body are populated with the logical layer management message.

[0049] In another possible implementation, the logical layer management message includes one or more of the following:

[0050] TSM, the LLMMT field of TSM is configured to 0x11.

[0051] Alternatively, CLFM, the LLMMT field of CLFM is configured to 0x12.

[0052] Alternatively, CLFM_ACK, the LLMMT field of CLFM_ACK is configured to 0x02.

[0053] Alternatively, EQFM, the LLMMT field of EQFM is configured to 0x13.

[0054] Alternatively, EQFM_ACK, the LLMMT field of EQFM_ACK is configured to 0x03.

[0055] Alternatively, LLFM, the LLMMT field of LLFM is configured to 0x14.

[0056] Alternatively, LPRM, the LLMMT field of LPRM is configured to 0x21.

[0057] Alternatively, the LLMMT field of LWAM and LPRM is configured to 0x22.

[0058] Alternatively, LDAM, the LLMMT field of LDAM is configured to 0x23.

[0059] Alternatively, CFSLM, the LLMMT field of CFSLM is configured to 0x24.

[0060] Alternatively, the TM, TM's LLMMT field is configured to 0x25.

[0061] Alternatively, Ack / Nack, the LLMMT field of Ack / Nack is configured to 0x2A.

[0062] Alternatively, ERR_RM, the LLMMT field of ERR_RM is configured to 0x2B.

[0063] In another possible implementation, the method provided in the present application may further include: if the logic block does not contain a logic layer management message, unpacking the logic block according to the logic layer data message.

[0064] It should be noted that the method for transmitting logical layer management messages provided by the second aspect is a receiving end method corresponding to the method provided by the above-mentioned first aspect or any possible implementation method. Its specific implementation can refer to the first aspect or any possible implementation method of the first aspect, and will not be repeated here.

[0065] In a third aspect, a device for transmitting a logical layer management message is provided, which may include: an encapsulation unit and a filling unit.

[0066] The encapsulation unit is used to encapsulate the logical layer management message into a logical layer management message, which includes an LLPT field. The LLPT field is assigned a first value to indicate that the current data message type is a logical layer management message.

[0067] The filling unit is used to fill the logical layer management message into the logical block. The logical block is also used to fill the logical layer data message that encapsulates the transport layer data. The logical layer data message includes the LLPT field. The LLPT field is assigned the second value to indicate that the current data message type is a logical layer data message.

[0068] In a possible implementation, a single logic block includes at most two logic layer management messages.

[0069] In another possible implementation, after the logical layer management message is inserted into the logical block, the filling unit is further configured to insert the logical layer data message into the logical block. This ensures that the logical layer management message is inserted first in the logical block, allowing the receiving end to parse and obtain the logical layer management message in a timely manner, thereby ensuring timely link management.

[0070] In another possible implementation, a single logic block includes a logic layer data message.

[0071] In another possible implementation, the first value may be 0xF0, and the second value may be 0x0F.

[0072] In another possible implementation, the logical layer management message is an LLMMP, which is 8 bytes long. It consists of an LLPH, LLPP, and a CRC code. The LLPH is 2 bytes long and includes the LLPT field. The LLPH also includes an LLMMT field, which indicates the type of message (management message type) carried by the current LLMMP. The LLPP is 4 bytes long, and the CRC is 2 bytes long. The CRC code is used to fill in the verification information for all parameters in the reserved field, LLMMT field, and LLPP field of the current data message.

[0073] In another possible implementation, when FEC is enabled, the above-mentioned logical block includes a block body and a block tail, the block body is filled with a logical layer management message and a logical layer data message, and the block tail corresponds to the FEC-coded check information.

[0074] In another possible implementation, the device further includes an encoding unit configured to: after the logical layer management message and the logical layer data message are filled into the logical block, perform FEC encoding on the logical block.

[0075] In another possible implementation, the length of the logical block is 240 bytes, the block body is 230 bytes, and the block trailer is 10 bytes; alternatively, the length of the logical block is 480 bytes, the block body is 460 bytes, and the block trailer is 20 bytes. Specifically, when a logical block is populated with one logical layer management message, the first 8 bytes in the block body are populated with the logical layer management message; alternatively, when a logical block is populated with two logical layer management messages, the first 16 bytes in the block body are populated with the logical layer management message; alternatively, when a logical block is not populated with a logical layer management message, no bytes in the block body are populated with the logical layer management message.

[0076] In another possible implementation, when FEC is disabled, the logical block includes a block body, and the length of the block body is 240 bytes or 480 bytes. Specifically, when the logical block is populated with one logical layer management message, the first 8 bytes of the block body are populated with the logical layer management message; or, when the logical block is populated with two logical layer management messages, the first 16 bytes of the block body are populated with the logical layer management message; or, when the logical block is not populated with a logical layer management message, no bytes of the block body are populated with the logical layer management message.

[0077] In another possible implementation, the logical layer management message includes one or more of the following:

[0078] TSM, the LLMMT field of TSM is configured to 0x11.

[0079] Alternatively, CLFM, the LLMMT field of CLFM is configured to 0x12.

[0080] Alternatively, CLFM_ACK, the LLMMT field of CLFM_ACK is configured to 0x02.

[0081] Alternatively, EQFM, the LLMMT field of EQFM is configured to 0x13.

[0082] Alternatively, EQFM_ACK, the LLMMT field of EQFM_ACK is configured to 0x03.

[0083] Alternatively, LLFM, the LLMMT field of LLFM is configured to 0x14.

[0084] Alternatively, LPRM, the LLMMT field of LPRM is configured to 0x21.

[0085] Alternatively, the LLMMT field of LWAM and LPRM is configured to 0x22.

[0086] Alternatively, LDAM, the LLMMT field of LDAM is configured to 0x23.

[0087] Alternatively, CFSLM, the LLMMT field of CFSLM is configured to 0x24.

[0088] Alternatively, the TM, TM's LLMMT field is configured to 0x25.

[0089] Alternatively, Ack / Nack, the LLMMT field of Ack / Nack is configured to 0x2A.

[0090] Alternatively, ERR_RM, the LLMMT field of ERR_RM is configured to 0x2B.

[0091] In another possible implementation, different logical layer management messages have different packet priorities. Logical layer management messages used for exception reporting and control frame transmission location messages have higher priority than other logical layer management messages. Other logical layer management messages include: link training start message, clock lock feedback message, equalization feedback message, channel lock feedback message, low power request message, link width adjustment message, channel direction adjustment message, and response message.

[0092] In another possible implementation, the filling unit is specifically configured to fill the logical layer management message into the logical block in descending order of packet priority.

[0093] It should be noted that the device for transmitting logical layer management messages provided by the third aspect is used to implement the method for transmitting logical layer management messages provided by the above-mentioned first aspect or any possible implementation method. Its specific implementation can refer to the first aspect or any possible implementation method of the first aspect, and will not be repeated here.

[0094] In a fourth aspect, another apparatus for transmitting a logical layer management message is provided, which may include a receiving unit, a deblocking unit, and a depacketizing unit.

[0095] The receiving unit is used to receive the logic block.

[0096] The deblocking unit is used to deblock the logic block and identify whether the logic block contains the logic layer management message.

[0097] The unpacking unit is configured to unpack the logical layer management message if the deblocking unit identifies that the logical block contains the logical layer management message.

[0098] In another possible implementation, the deblocking unit is specifically used to: detect the first byte of the logical block; if the first byte indicates a logical layer data message, there is no logical layer management message in the logical block; if the first byte indicates a logical layer management message, detect the ninth byte of the logical block; if the ninth byte indicates a logical layer data message, the logical block contains one logical layer management message; if the ninth byte indicates a logical layer management message, the logical block contains two logical layer management messages.

[0099] The first byte and the ninth byte of the logic block indicate the location of the LLPT field of the logic layer management message when the logic layer management message is filled in the logic block.

[0100] In another possible implementation, when FEC is enabled, the deblocking unit is further configured to: if the logical block contains a logical layer management message and there is no CRC error when the logical layer management message is depacketized, discard the first 8 bytes of data when deblocking the logical block after FEC decoding. If the logical block contains a logical layer management message and there is a CRC error when the logical layer management message is depacketized, deblock the logical block starting from the first byte after FEC decoding. If the logical block contains two logical layer management messages and there is no CRC error when the logical layer management messages are depacketized, discard the first 16 bytes of data when deblocking the logical block after FEC decoding. If the logical block contains two logical layer management messages and there is no CRC error when the logical layer management messages are depacketized, discard the first 8 bytes of data when deblocking the logical block after FEC decoding. If a logical block contains two logical layer management messages and the first logical layer management message has a CRC error when the logical layer management messages are depacketized, the logical block is depacketized starting from the first byte after FEC decoding.

[0101] To ensure the timeliness of logical layer management functions, when FEC is enabled, identified logical layer management messages are first depacketized during FEC decoding. After FEC decoding, the logical blocks must be deblocked again to identify the data messages populated within them. This deblocking process not only identifies unpacked logical layer data messages but also performs error correction and verification on logical layer management messages that contain CRC errors during depacketization, thereby improving the accuracy of logical layer management message transmission.

[0102] In another possible implementation, when FEC is not enabled, the depacketizing unit is further configured to: depacketize the logical layer data message for data other than the logical layer management message in the logical block.

[0103] In another possible implementation, a single logic block includes at most two logic layer management messages.

[0104] In another possible implementation, a logical layer data message is encapsulated in a single logical block.

[0105] In another possible implementation, the logical layer management message is an LLMMP, which is 8 bytes long. It consists of an LLPH, LLPP, and a CRC code. The LLPH is 2 bytes long and includes the LLPT field, which is assigned a value of 0xF0. The LLPH also includes the LLMMT field, which indicates the message type carried by the LLMMP. The LLPP is 4 bytes long, and the CRC is 2 bytes long. The CRC code is used to verify all parameters in the reserved field, LLMMT field, and LLPP field of the current data message.

[0106] In another possible implementation, when FEC is enabled, the logic block includes a block body and a block tail, the block body is filled with a logic layer management message and a logic layer data message, and the block tail corresponds to the FEC-coded check information.

[0107] The block tail corresponds to the FEC-coded check information, which refers to the check data obtained by filling the block tail with the FEC code.

[0108] In another possible implementation, the device further includes a decoding unit configured to: after unpacking the logical layer management message, perform FEC decoding on the logical block.

[0109] In another possible implementation, the length of the logical block is 240 bytes, the block body is 230 bytes, and the block trailer is 10 bytes; alternatively, the length of the logical block is 480 bytes, the block body is 460 bytes, and the block trailer is 20 bytes. Specifically, when a logical block is populated with one logical layer management message, the first 8 bytes in the block body are populated with the logical layer management message; alternatively, when a logical block is populated with two logical layer management messages, the first 16 bytes in the block body are populated with the logical layer management message; alternatively, when a logical block is not populated with a logical layer management message, no bytes in the block body are populated with the logical layer management message.

[0110] In another possible implementation, when FEC is disabled, the logical block includes a block body, and the length of the block body is 240 bytes or 480 bytes. Specifically, when the logical block is populated with one logical layer management message, the first 8 bytes of the block body are populated with the logical layer management message; or, when the logical block is populated with two logical layer management messages, the first 16 bytes of the block body are populated with the logical layer management message; or, when the logical block is not populated with a logical layer management message, no bytes of the block body are populated with the logical layer management message.

[0111] In another possible implementation, the logical layer management message includes one or more of the following:

[0112] TSM, the LLMMT field of TSM is configured to 0x11.

[0113] Alternatively, CLFM, the LLMMT field of CLFM is configured to 0x12.

[0114] Alternatively, CLFM_ACK, the LLMMT field of CLFM_ACK is configured to 0x02.

[0115] Alternatively, EQFM, the LLMMT field of EQFM is configured to 0x13.

[0116] Alternatively, EQFM_ACK, the LLMMT field of EQFM_ACK is configured to 0x03.

[0117] Alternatively, LLFM, the LLMMT field of LLFM is configured to 0x14.

[0118] Alternatively, LPRM, the LLMMT field of LPRM is configured to 0x21.

[0119] Alternatively, the LLMMT field of LWAM and LPRM is configured to 0x22.

[0120] Alternatively, LDAM, the LLMMT field of LDAM is configured to 0x23.

[0121] Alternatively, CFSLM, the LLMMT field of CFSLM is configured to 0x24.

[0122] Alternatively, the TM, TM's LLMMT field is configured to 0x25.

[0123] Alternatively, Ack / Nack, the LLMMT field of Ack / Nack is configured to 0x2A.

[0124] Alternatively, ERR_RM, the LLMMT field of ERR_RM is configured to 0x2B.

[0125] In another possible implementation, the unpacking unit is further configured to: if the logic block does not contain the logic layer management message, unpack the logic block according to the logic layer data message.

[0126] It should be noted that the device for transmitting logical layer management messages provided in the fourth aspect is used to implement the method for transmitting logical layer management messages provided in the above-mentioned second aspect or any possible implementation method. Its specific implementation can refer to the second aspect or any possible implementation method of the second aspect, and will not be repeated here.

[0127] In a fifth aspect, a computing device is provided, which includes a memory and at least one processor, the memory being used to store a set of computer instructions; when the processor executes this set of computer instructions, the operations of the method described in the first aspect or the second aspect or any possible implementation method are performed.

[0128] In a sixth aspect, a data transmission system is provided, comprising a data sending device and / or a data receiving device. The data sending device is used to execute the method for transmitting logical layer management messages described in the first aspect or any possible implementation of the first aspect, and the data receiving device is used to execute the method for transmitting logical layer management messages described in the second aspect or any possible implementation of the first aspect. Alternatively, the data sending device includes the device for transmitting logical layer management messages described in the third aspect or any possible implementation of the third aspect, and the data receiving device includes the device for transmitting logical layer management messages described in the fourth aspect or any possible implementation of the fourth aspect.

[0129] In a seventh aspect, a chip is provided, comprising one or more interface circuits and one or more processors; the interface circuits are configured to receive signals from a memory of an electronic device and transmit the received signals to the processors, the signals comprising computer instructions stored in the memory. When the processors execute the computer instructions, the electronic device performs the steps of the method described in the first aspect, the second aspect, or any possible implementation.

[0130] In an eighth aspect, a computer-readable storage medium is provided, comprising: computer software instructions; when the computer software instructions are executed in a computer, the computer executes the operations of the method described in the first aspect or the second aspect or any possible implementation method.

[0131] In a ninth aspect, a computer program product, when running on a computer, enables the computer to execute the operating steps of the method described in the first aspect or the second aspect or any possible implementation method.

[0132] In a tenth aspect, a chip system is provided, which includes a processor and may also include a memory, for implementing the functions in the above method. The chip system can be composed of a chip or include a chip and other discrete devices.

[0133] The solutions provided in the third to tenth aspects are used to implement the methods provided in the first or second aspects, and therefore can achieve the same beneficial effects as the first or second aspects, and will not be repeated here.

[0134] It should be noted that various possible implementations of any of the above aspects can be combined under the premise that the solutions are not contradictory. BRIEF DESCRIPTION OF THE DRAWINGS

[0135] FIG1 is a schematic diagram of the architecture of a multimedia data transmission system provided in an embodiment of the present application;

[0136] FIG2 is a schematic diagram of the architecture of another multimedia data transmission system provided in an embodiment of the present application;

[0137] FIG3 is a schematic diagram of the structure of a computing device provided in an embodiment of the present application;

[0138] FIG4 is a flow chart of a method for transmitting a logical layer management message according to an embodiment of the present application;

[0139] FIG5 is a schematic diagram of an LLMMP message format provided in an embodiment of the present application;

[0140] FIG6 is a flow chart of another method for transmitting logical layer management messages provided in an embodiment of the present application;

[0141] FIG7 is a schematic diagram of an LLDP message format provided in an embodiment of the present application;

[0142] FIG8a is a schematic diagram of a mapping relationship between TLP and LLDP provided in an embodiment of the present application;

[0143] FIG8b is a schematic diagram of an LLSMP message format provided in an embodiment of the present application;

[0144] FIG9 is a schematic diagram of the structure of a logic block provided in an embodiment of the present application;

[0145] FIG10 is a schematic diagram of the structure of another logic block provided in an embodiment of the present application;

[0146] FIG11 is a schematic diagram of a sending and receiving sequence of a logic block provided in an embodiment of the present application;

[0147] FIG12 is a schematic diagram of a unified multimedia interconnection interface logical layer main link architecture provided in an embodiment of the present application;

[0148] FIG13 is a schematic diagram of the structure of another logic block provided in an embodiment of the present application;

[0149] FIG14 is a schematic diagram of the structure of another logic block provided in an embodiment of the present application;

[0150] FIG15 is a schematic diagram of the structure of another logic block provided in an embodiment of the present application;

[0151] FIG16 is a schematic diagram of the structure of another logic block provided in an embodiment of the present application;

[0152] FIG17a is a schematic structural diagram of an apparatus for transmitting logical layer management messages provided in an embodiment of the present application;

[0153] FIG17b is a schematic structural diagram of another apparatus for transmitting logical layer management messages provided in an embodiment of the present application;

[0154] FIG18a is a schematic structural diagram of another apparatus for transmitting logical layer management messages provided in an embodiment of the present application;

[0155] FIG18b is a schematic structural diagram of another apparatus for transmitting logical layer management messages provided in an embodiment of the present application;

[0156] Figure 19 is a structural diagram of another device for transmitting logical layer management messages provided in an embodiment of the present application. DETAILED DESCRIPTION

[0157] In the embodiments of the present application, in order to clearly describe the technical solutions of the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity or execution order, and words such as "first" and "second" do not necessarily mean different. There is no order of precedence or priority between the technical features described by "first" and "second".

[0158] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0159] In the embodiments of the present application, at least one can also be described as one or more, and multiple can be two, three, four or more, which is not limited in this application.

[0160] In addition, the network architecture and scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0161] To facilitate understanding, the terms involved in the embodiments of this application are first explained.

[0162] Logical Layer Block (LLB) is the basic unit of data transmission.

[0163] Transport layer data is the business data that is passed from the transport layer to the logic layer during the process of sending business data to the other end.

[0164] Logical layer management messages are used to transmit information such as link management and channel training. Logical layer management messages are sent from the upper layer of the logical layer (transport layer or adapter) to the logical layer.

[0165] The solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0166] FIG1 illustrates a multimedia data transmission system. As shown in FIG1 , the multimedia data transmission system may include a source device 101 and a sink device 102 .

[0167] The source device 101 and the sink device 102 may be connected directly or through a routing device (this scenario is not shown in FIG. 1 ).

[0168] In the multimedia data transmission system shown in FIG1 , a source device 101 transmits multimedia data to a sink device 102 .

[0169] In one scenario, source device 101 and sink device 102 are unified multimedia interconnect devices that deploy a unified multimedia interconnect interface. The multimedia data transmission system illustrated in Figure 1 implements data exchange between unified multimedia interconnect devices. For example, high-speed signal transmission between unified multimedia interconnect devices enables bidirectional audio and video transmission, meeting the audio and video transmission needs of devices such as televisions, computers, and mobile phones.

[0170] In one scenario, either the source device 101 or the sink device 102 is a unified multimedia interconnection device deployed with a unified multimedia interconnection interface, and the other is a third-party protocol device merged with the unified multimedia interconnection, realizing data interaction between the third-party protocol device and the unified multimedia interconnection device.

[0171] In one scenario, the source device 101 may be a set-top box device. The sink device 102 may be a device with a screen. For example, the set-top box device may obtain multimedia data from a data server via a network through a router, a switch, or other network device.

[0172] Exemplarily, the set-top box device may also be called a digital video converter box (set top box, STB), or set-top box, or other. The set-top box device is a device that connects a multimedia player device and an external signal source. This application does not limit the specific product form of the set-top box device.

[0173] The sink device 102 may be a smart TV, tablet, smart screen, or other device for receiving and playing multimedia data. This application does not limit the specific product form of the sink device 102.

[0174] In one possible implementation, the internal architecture of the multimedia data transmission system shown in FIG1 may be as shown in FIG2 . As shown in FIG2 , the source device 101 and the sink device 102 include a router and a transceiver, and the router includes an adapter and a port.

[0175] The router uses the adapter to encapsulate the data generated by the external component into a unified multimedia interconnection message, forming a unified multimedia interconnection service flow and forwarding it to the port. The port then sends it to the router of the peer device. The peer device's router obtains the unified multimedia interconnection service flow restored by the port and forwards it to the adapter for processing. The adapter converts it into data and sends it to the external component.

[0176] For example, when the end device is a third-party protocol device, the adapter in the router can be a third-party protocol adapter. The third-party protocol adapter receives third-party protocol data from the third-party protocol component, encapsulates it into a tunnel message (specifically, a unified multimedia interconnection protocol message), forms a service flow, and sends it to the corresponding port, which then forwards it to the router of the opposite device. The router of the opposite device obtains the service flow restored by the port (such as the unified multimedia interconnection service flow) and forwards it to the corresponding third-party protocol adapter for processing. The third-party protocol adapter processes it into third-party protocol data and sends it to the third-party protocol component.

[0177] In one aspect, an embodiment of the present application provides a schematic structural diagram of a computing device 30. The computing device 30 can implement the functions of the source device 101 or the sink device 102 shown in FIG. 1 or FIG. 2 .

[0178] Exemplarily, the computing device 30 may implement the functions of the source device 101 or the sink device 102 illustrated in FIG. 1 or FIG. 2 at the logic layer.

[0179] 3 , the computing device 30 may include a processor 3010 , a bus 3020 , a memory 3030 , and a communication interface 3040 . The processor 3010 , the memory 3030 , and the communication interface 3040 are connected via the bus 3020 .

[0180] It should be understood that in this embodiment, the processor 3010 may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0181] The processor 3010 may also be a graphics processing unit (GPU), a neural network processing unit (NPU), a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of the program of the present application.

[0182] The communication interface 3040 is used to implement communication between the computing device 30 and external devices or components.

[0183] The bus 3020 may include a path for transmitting information between the above-mentioned components (such as the processor 3010 and the memory 3030). In addition to the data bus, the bus 3020 may also include a power bus, a control bus, and a status signal bus. However, for the sake of clarity, various buses are labeled as bus 3020 in the figure. The bus 3020 may be a peripheral component interconnect express (PCIe) bus, an extended industry standard architecture (EISA) bus, a unified bus (Ubus or UB), a computer express link (CXL), a cache coherent interconnect for accelerators (CCIX), etc. The bus 3020 can be divided into an address bus, a data bus, a control bus, etc.

[0184] As an example, computing device 30 may include multiple processors. The processor may be a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and / or computing units for processing data (e.g., computer program instructions).

[0185] It is worth noting that FIG3 only takes the computing device 30 including 1 processor 3010 and 1 memory 3030 as an example. Here, the processor 3010 and the memory 3030 are respectively used to indicate a type of device or equipment. In a specific embodiment, the number of each type of device or equipment can be determined according to business requirements.

[0186] Memory 3030 may be a volatile memory pool or a non-volatile memory pool, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0187] For example, the processor 3010 may perform the following functions by running or executing the software programs and / or modules stored in the memory 3030:

[0188] The logical layer management message is encapsulated into a logical layer management message, which includes an LLPT field. The LLPT field is assigned a first value to indicate that the current data message type is a logical layer management message; the logical layer management message is filled into a logical block, which is also used to fill a logical layer data message that encapsulates transport layer data. The logical layer data message includes an LLPT field. The LLPT field is assigned a second value to indicate that the current data message type is a logical layer data message.

[0189] For example, the processor 3010 may perform the following functions by running or executing the software programs and / or modules stored in the memory 3030:

[0190] Receive a logic block; deblock the logic block and identify whether the logic block contains a logic layer management message; if it is identified that the logic block contains a logic layer management message, depacketize the logic layer management message.

[0191] On the other hand, embodiments of the present application provide a method for transmitting logical layer management messages, which is applied to a source device 101 or a sink device 102 in the multimedia data transmission system illustrated in FIG1 or 2 , or a chip in the source device 101, or a chip in the sink device 102, to implement logical layer transmission of logical layer management messages. The transmitting device described below may be the source device 101 or a chip therein, and the receiving device may be the sink device 102 or a chip therein.

[0192] As shown in FIG4 , the method for transmitting a logical layer management message provided in this application may include:

[0193] S401. Encapsulate a logical layer management message into a logical layer management message. The logical layer management message includes an LLPT field. The LLPT field is assigned a first value, indicating that the current data message type is a logical layer management message.

[0194] Specifically, the logic layer management message needs to be encapsulated into a data message structure, and the management message is distinguished from other types of data messages (such as the logic layer data message encapsulating the transport layer data) through the data message type.

[0195] For example, the first value may be 0xF0. Of course, the specific value of the first value may be configured according to actual needs, as long as the LLPT field is assigned different values ​​to indicate different types of data packets.

[0196] Specifically, in S401, the logical layer management message can be encapsulated into a logical layer management message according to the format of the logical layer management message. The format of the logical layer management message can be configured according to actual needs, and the embodiment of the present application is not limited to this.

[0197] Exemplarily, the logical layer management message is LLMMP, which is transmitted through the main link (ML) between two devices. Figure 5 illustrates the message format of LLMMP. As shown in Figure 5, the length of the logical layer management message is 8 bytes; the logical layer management message consists of LLPH, LLPP and CRC code. The length of LLPH is 2 bytes, and LLPH includes an LLPT field. LLPH also includes an LLMMT field. The LLMMT field indicates the message type carried by the current LLMMP (i.e., the type of logical layer management message). The length of LLPP is 4 bytes; the length of the CRC code is 2 bytes, and the CRC code is used to fill in the verification information of all parameters of the reserved field, LLMMT field and LLPP field of the current data message. The embodiment of the present application does not elaborate on the generation process of the CRC code.

[0198] In FIG5 , the CRC LS byte represents the least significant (LS), and the CRC MS byte represents the most significant (MS).

[0199] Specifically, different types of management messages can be indicated in LLMMP by assigning different values ​​to the LLMMT field. The following examples illustrate the assignment of values ​​to the LLMMT field for different types of management messages:

[0200] Logical layer management messages include: TSM, which is used to start link training. The LLMMT field of TSM can be configured to 0x11.

[0201] Logical layer management messages include CLFM, which is a combination of clock lock result flags and Swing update request messages. CLFM contains the clock lock results and Swing update requests for all receive channels on the current port. The LLMMT field of CLFM can be configured to 0x12.

[0202] Logical layer management messages include: CLFM_ACK, which is the CLFM response message. The LLMMT field of CLFM_ACK can be configured to 0x02.

[0203] Logical layer management messages include: EQFM, which is a combination of equalization result flag and feed-forward equalizer (FFE) parameter update request message. The LLMMT field of EQFM can be configured to 0x13.

[0204] Logical layer management messages include: EQFM_ACK, which is the EQFM response message. The LLMMT field of EQFM_ACK can be configured to 0x03.

[0205] Logical layer management messages include: LLFM, which is a collection of channel lock result flags. The LLMMT field of LLFM can be configured to 0x14.

[0206] Logical layer management messages include: LPRM, which is a set of low power request parameters. The LLMMT field of LPRM can be configured to 0x21.

[0207] Logical layer management messages include: LWAM, which is a set of link width adjustment request parameters. The LLMMT field of LPRM can be configured to 0x22.

[0208] Logical layer management messages include: LDAM, which is a set of channel direction adjustment request parameters. The LLMMT field of LDAM can be configured to 0x23.

[0209] Logical layer management messages include: CFSLM, which is an information parameter indicating the location of subsequent CF transmission. The LLMMT field of CFSLM can be configured to 0x24.

[0210] Logical layer management messages include: TM, which is used to synchronize time between the transmitter and receiver. The LLMMT field of TM can be configured to 0x25.

[0211] Logical layer management messages include Ack / Nack, which are responses to management messages. The LLMMT field of Ack / Nack can be configured to 0x2A.

[0212] Logical layer management messages include: ERR_RM, which is a collection of abnormal messages that require recovery or retraining. The LLMMT field of ERR_RM can be configured to 0x2B.

[0213] It should be noted that the above examples are merely illustrative of the types of management messages and the thresholds of the LLMMT domain, and do not constitute specific limitations.

[0214] S402. Fill the logical layer management message into the logical block. The logical block is also used to fill the logical layer data message that encapsulates the transport layer data. The logical layer data message includes an LLPT field. The LLPT field is assigned a second value to indicate that the current data message type is a logical layer data message.

[0215] Specifically, in S402 , the encapsulated logical layer management message may be filled into the logical block byte by byte according to the block encapsulation rule (filling rule) and the byte order, and may be filled into the body of the logical block.

[0216] Furthermore, different logical layer management messages may have different packet priorities.

[0217] Exemplarily, the priority of the logical layer management message used for abnormal reporting and the control frame sending location message is higher than that of other logical layer management messages; the other logical layer management messages include: link training start message, clock lock feedback message, equalization feedback message, channel lock feedback message, low power request message, link width adjustment message, channel direction adjustment message, and response message.

[0218] Correspondingly, when there are multiple logical layer management messages, filling the to-be-transmitted messages into the logical block in S402 includes: filling the logical layer management messages into the logical block in descending order of packet priority.

[0219] Exemplarily, the above-mentioned block blocking rule (filling rule) may include: a single logic block includes at most two logic layer management messages.

[0220] It should be noted that when a logical layer management message needs to be sent, operations S401 and S402 can be performed to dynamically insert a logical layer management message into the logical block. When a logical layer management message is not needed, the logical block is filled with only logical layer data messages. Because the logical layer management message is configured with a logical layer message type field that indicates the message type, the peer end can accurately parse the logical layer management message even if it is dynamically inserted.

[0221] The solution provided by this application configures a logical layer message type field in logical layer management messages, which indicates the message type. This field is used to identify different types of data messages, facilitating data decapsulation and recovery at the receiving end. This allows logical layer management messages to be dynamically inserted into logical blocks only when they are needed, based on link management requirements. This avoids reserving space for sending management data when none exists, and improves bandwidth utilization for service data transmission on inter-device links.

[0222] Furthermore, the logic block is filled with logic layer management messages and logic layer data messages. Therefore, while executing S401 and S402, it is also necessary to encapsulate the transport layer data into logic layer data messages. After S402, as shown in FIG6 , the method provided by the present application may further include S403.

[0223] S403: Fill the logic layer data message into the logic block.

[0224] Specifically, transport layer data needs to be encapsulated into a data message structure, and the LLPT field is used to distinguish logical layer data messages from other types of data messages (such as those encapsulating logical layer management messages). Therefore, the logical layer data message includes an LLPT field, and the LLPT field is assigned a second value to indicate that the current data message type is a logical layer data message. The second value is different from the first value described above.

[0225] For example, the second value may be 0x0F. Of course, the specific value of the second value may be configured according to actual needs, as long as the LLPT field is assigned different values ​​to indicate different types of data packets.

[0226] Specifically, the transport layer data may be encapsulated into a logical layer data message in accordance with the format of the logical layer data message. The format of the logical layer data message may be configured according to actual needs, and the embodiment of the present application does not limit this.

[0227] Furthermore, the encapsulated logical layer data message can be filled into the logical block byte by byte according to the block encapsulation rule (filling rule) and the byte order, and can be filled into the block body of the logical block.

[0228] Exemplarily, the above-mentioned block blocking rule (filling rule) may include: a single logic block includes one logic layer data message.

[0229] In one possible implementation, after the logical layer management message is filled, S403 is executed to fill the logical layer data message. That is, S402 is executed first, and then S403 is executed. In this way, the logical layer management message is filled first in the logical block, and the logical layer data message is filled later.

[0230] Furthermore, the structure of the logic block can be configured according to actual needs. The following are several examples of the structure of the logic block, but they do not constitute a specific limitation.

[0231] In one possible implementation, when FEC is enabled, a logical block may include a block body and a block trailer. The block body is populated by logical layer management messages and logical layer data messages, and the block trailer corresponds to the FEC-encoded check information. In other words, the block trailer is used to fill in the check data generated by the FEC encoding.

[0232] Accordingly, when FEC is enabled, the method provided in the embodiment of the present application may further include: after filling the logical layer management message and the logical layer data message into the logical block, performing FEC encoding on the logical block. The embodiment of the present application does not limit the specific scheme of FEC encoding, and it can be configured according to actual needs.

[0233] In one possible implementation, the length of the logical block is 240 bytes, the block body is 230 bytes, and the block trailer is 10 bytes. For example, in TYPE-C mode with FEC enabled, the length of the logical block is 240 bytes, the block body is 230 bytes, and the block trailer is 10 bytes.

[0234] In another possible implementation, the length of the logical block is 480 bytes, the block body is 460 bytes, and the block trailer is 20 bytes. For example, in TYPE-C mode with FEC enabled, the length of the logical block is 480 bytes, the block body is 460 bytes, and the block trailer is 20 bytes.

[0235] For example, when the length of a logical layer management message is 8 bytes, the logical layer management message is preferentially filled into the logical block. When one logical layer management message is filled into the logical block, the first 8 bytes in the block body of the logical block are filled with the logical layer management message. Alternatively, when two logical layer management messages are filled into the logical block, the first 16 bytes in the block body of the logical block are filled with the logical layer management message. Alternatively, when no logical layer management message is filled into the logical block, no bytes in the block body of the logical block are filled with the logical layer management message.

[0236] In another possible implementation, when FEC is not enabled, the logical block includes a block body, the length of the block body is 240 bytes or 480 bytes, and all bytes of the logical block are the block body.

[0237] For example, in TYPE-C mode, when FEC is disabled, the logical block length is 240 bytes, and the block body is 240 bytes. In TYPE-B mode, when FEC is disabled, the logical block length is 480 bytes, and the block body is 480 bytes.

[0238] Furthermore, after the transmitting device executes S401 and S402 above, and after filling and constructing the logical block, it transmits the logical block in the link. When it is transmitted to the receiving end, the receiving end device parses it and obtains the logical layer management message therein. As shown in Figure 6, the method for transmitting logical layer management messages provided by this application can also include S404 to S406.

[0239] S404: Receive a logic block.

[0240] It should be noted that the logic block received in S404 may be a logic block constructed using S401, S402 and S403, and the structure and content of the logic block will not be described in detail here.

[0241] S405: Deblock the logic block and identify whether the logic block contains a logic layer management message.

[0242] Specifically, deblocking the logic block in S405 is a process of identifying the position of the LLPT field filled with the logical layer management message in the logic block, so as to determine whether the logic block contains the logical layer management message.

[0243] For example, assuming that the logical layer management message is 8 bytes long and a single logical block is filled with a maximum of N logical layer management messages, the position of the LLPT field filled with the logical layer management message in the logical block can be the 8i+1th byte, where i traverses from 0 to N-1, and N is greater than or equal to 1.

[0244] For example, assuming that the logical layer management message is 8 bytes long and a single logical block can be filled with a maximum of 2 logical layer management messages, the position of the LLPT field filled with the logical layer management message in the logical block can be the 1st byte and the 9th byte.

[0245] The determination of whether the logic block contains the logic layer management message may include: determining whether the value of the position of the LLPT field filled with the logic layer management message in the logic block indicates the logic layer management message.

[0246] In one possible implementation, S404 can be specifically implemented as follows: detecting the first byte of the logic block; if the first byte indicates a logical layer data message, there is no logical layer management message in the logic block; if the first byte indicates a logical layer management message, detecting the ninth byte of the logic block; if the ninth byte indicates a logical layer data message, the logic block contains one logical layer management message; if the ninth byte indicates a logical layer management message, the logic block contains two logical layer management messages.

[0247] S406: If it is identified that the logic block contains a logic layer management message, the logic layer management message is unpacked.

[0248] Specifically, in S406, the identified logical layer management message may be sent to the depacketization layer, which depacketizes the message according to the format of the logical layer management message to obtain the logical layer management message encapsulated in the logical layer management message to implement the logical layer management function.

[0249] The identified logical layer management message means that if a logical block is identified to contain one logical layer management message, the first X bytes of the logical block are the identified logical layer management message; if a logical block is identified to contain two logical layer management messages, the first 2X bytes of the logical block are the identified logical layer management message, where X is the byte length of a logical layer management message.

[0250] The solution provided by this application first identifies and unpacks logical layer management messages after receiving a logical block to obtain logical layer management messages for link management. In a solution that distinguishes between logical layer management messages and logical layer data messages, logical layer management messages can be dynamically inserted into logical blocks only when logical layer management messages need to be transmitted, based on link management requirements. This avoids reserving space for sending management data when none exists, thereby improving bandwidth utilization for link transmission of service data between devices.

[0251] Furthermore, in S406, if no CRC error occurs when the depacketization layer depackets the logical layer management message, the depacketization layer successfully depackets the logical layer management message. If a CRC error occurs when the depacketization layer depackets the logical layer management message, and FEC is not enabled, the depacketization layer cannot depacketize the logical layer management message and discards the logical layer management message. If a CRC error occurs when the depacketization layer depackets the logical layer management message, and FEC is enabled, FEC error correction can be performed on the CRC error when the logical block is deblocked again after FEC decoding.

[0252] Furthermore, since the logic block is also filled with logic layer data messages, after S406 , the logic layer data messages need to be unpacked.

[0253] In one possible implementation, when FEC is not enabled, after S406, the data other than the logical layer management message in the logical block is depacketized into a logical layer data message. That is, the data other than the logical layer management message in the logical block is depacketized according to the format of the logical layer data message to obtain the transport layer data encapsulated therein.

[0254] In another possible implementation, when FEC is enabled, after S406 , as shown in FIG6 , the method provided in the present application may further include S407 .

[0255] S407: Perform FEC decoding on the logical block.

[0256] It should be noted that the FEC decoding scheme is not limited or elaborated in this embodiment of the application.

[0257] After S407, the logic block needs to be deblocked again to obtain the logic layer data message filled in the logic block, and to correct the logic layer management message with CRC error when depacketizing. As shown in Figure 6, the method provided by the present application may also include S408.

[0258] S408: Deblock the logic block again.

[0259] Specifically, when deblocking again in S408, the bytes successfully depacketized in S406 can be discarded to improve deblocking efficiency; the bytes that failed to be depacketized in S406 are deblocked to perform error correction to improve the transmission quality of the logical layer management message.

[0260] For example, when deblocking again in S408, one or more of the following rules may be referred to:

[0261] 1) If the logical block contains a logical layer management message and there is no CRC error when unpacking the logical layer management message, the first 8 bytes of data are discarded when unblocking the LLB after FEC decoding;

[0262] 2. If the logical block contains a logical layer management message and there is a CRC error when unpacking the logical layer management message, after FEC decoding, the logical block is deblocked starting from the first byte;

[0263] 3) If the logical block contains two logical layer management messages and there is no CRC error when unpacking the logical layer management messages, after FEC decoding, the first 16 bytes of data are discarded when unblocking the LLB;

[0264] 4) If the logical block contains two logical layer management messages, and the first logical layer management message has no CRC error when the logical layer management message is unpacked, and the second logical layer management message has a CRC error, after FEC decoding, the first 8 bytes of data are discarded when the LLB is deblocked.

[0265] 5) If the logical block contains two logical layer management messages, and the first logical layer management message has a CRC error when the logical layer management message is unpacked, the logical block is unpacked starting from the first byte after FEC decoding.

[0266] The above embodiment describes the process of transmitting the logical layer management message. The following examples illustrate the contents involved in the above embodiment, but do not constitute specific limitations.

[0267] The links established between devices configured with the unified multimedia interconnection interface can include the main link (ML) and the sideband link (SL). The transmission rate of the ML is higher than that of the SL.

[0268] First, let's take a look at the Logical Layer Data Packet (LLDP) example:

[0269] LLDP implements packet processing for transport layer data. LLDP can only be transmitted over the ML (Main Link). Figure 7 illustrates an LLDP message structure. As shown in Figure 7, a complete LLDP structure is described. The entire data message consists of the LLPH and LLPP structures. The LLPH is a fixed 2-byte field. The LLPT field in the LLDP field indicates the current data message type. The LLPT field is fixed to 0x0F and occupies 1 byte. The Rsv field is a reserved field, fixed to 0x0 and occupies 1 byte. The LLPP field is filled with transport layer data, and its length depends on the length of the logical block.

[0270] The mapping relationship between the Transaction Layer Packet (TLP) and LLDP is shown in Figure 8a. The following mapping scenarios exist:

[0271] (1) LLPPx is equal to LLPP0, and LLDP starts filling TLP data from the first byte.

[0272] (2) LLPPx is not equal to LLPP0. LLDP starts filling TLP data from the middle. The data filled before LLPPx is the TLP data before the current TLP.

[0273] (3) LLPPy is not the last byte of the current LLDP, and Bz is the last byte of TLP, that is, the TLP data is filled in the current LLDP, and the data filled after LLPPy is the TLP data after the current TLP.

[0274] (4) LLPPy is the last byte of the current LLDP, and Bz is the last byte of TLP, that is, the TLP data is just filled in the current LLDP.

[0275] (5) LLPPy is the last byte of the current LLDP, and Bz is not the last byte of TLP. That is, the current LLDP has not completed filling all the data of the current TLP. The remaining data of the current TLP will be filled starting from LLPP0 of the next LLDP.

[0276] Specifically, TLP is mapped to LLDP. When mapping TLP to LLDP, TLP is mapped to the available bytes in the LLDP payload in byte order. For example, when filling a certain TLP (current TLP) into the current LLDP, assuming that the first available byte in the current LLDP payload is LLPPx (any byte in the LLDP payload), the current TLP is filled from LLPPx to LLPPy, and LLPPy fills the Bz position in the current TLP data. The mapping relationship between TLP and LLDP is shown in Figure 8a. The following mapping scenarios exist:

[0277] 1) LLPPx is the first byte of the LLDP payload (LLPP0). LLDP starts filling the current TLP data from the first byte.

[0278] 2) LLPPx is not the first byte of the LLDP payload (LLPP0). LLDP starts filling the current TLP data from the middle, and the data filled before LLPPx is the TLP data before the current TLP.

[0279] 3) LLPPy is not the last byte of the current LLDP, and Bz is the last byte of the current TLP. That is, the current TLP data is filled in the current LLDP, and the data filled after LLPPy is the TLP data after the current TLP.

[0280] 4) LLPPy is the last byte of the current LLDP, and Bz is the last byte of the current TLP, that is, the current TLP data is just filled in the current LLDP.

[0281] 5) LLPPy is the last byte of the current LLDP, and Bz is not the last byte of the current TLP. That is, the current LLDP has not completed filling all the data of the current TLP. The remaining data of the current TLP (the data after Bz) starts filling from LLPP0 of the next LLDP.

[0282] The following is an example of the logical layer management message:

[0283] Logical layer management messages, including the Logical Layer Main Link Management Packet (LLMMP) and the Logical Layer Sideband Link Management Packet (LLSMP), are encapsulated and processed for logical layer management messages. LLMMP is transmitted over the ML, while LLSMP is transmitted over the SL. In scenarios where ML exists, ML is recommended for transmitting logical layer management messages.

[0284] As shown in Figure 5 above, a complete LLMMP structure is described. The entire data message is 8 bytes long and consists of the LLPH, LLPP, and CRC code structures. The LLPH is fixed at 2 bytes in length, where the LLPT field indicates the current data message type, and the LLMMP is fixed at 0xF0. The Rsv field is a reserved field and is fixed at 0x0. The LLMMT field indicates the type of message (management message) carried by the current LLMMP. The LLPP is fixed at 4 bytes in length, and its content is determined by the logical layer management message to be transmitted. If the message length is less than 4 bytes, it is padded with reserved parameters, which are fixed at 0x0. The CRC is fixed at 2 bytes and is filled with verification information for all parameters in the Rsv, LLMMT, and LLPP fields of the current data message.

[0285] Among them, the generating polynomial corresponding to CRC is: g(x)=x 16 +x 12 +x 5 +1.

[0286] Figure 8b depicts a complete LLSMP structure. The entire data message has a variable length and consists of the LLPH, LLPP, and CRC structures. The LLPH is fixed at 2 bytes, with the Rsv and LLMMT fields consistent with the LLMMP. The Logical Layer Packet Length (LLPL) field indicates the current LLSMP message payload length. The LLPP length and content are determined by the logical layer management message being transmitted. The CRC is fixed at 2 bytes and contains checksum information for all parameters in the data message except the CRC field.

[0287] The logical layer management information supported by the logical layer of the unified multimedia interconnection interface can be summarized as shown in Table 1.

[0288] Table 1

[0289] The following is an example of an exception reporting message (a logical layer management message).

[0290] Error Report Messages (ERR_RM) are a collection of exception messages that require recovery or retraining. For more information about exception messages, refer to the following exception handling mechanism.

[0291] ERR_RM is used when a link exception occurs, requiring recovery or retraining. It reports the exception detected by the current port to the peer port. Based on the type of exception at the logical layer, the current port constructs and sends an ERR_RM message, then enters the recovery or INIT state. After receiving and parsing the ERR_RM message, the peer port enters the recovery or INIT state. Retraining is initiated after entering the INIT state.

[0292] ERR_RM requires a response. The receiver receives ERR_RM and enters the recovery or INIT state, then responds with an Ack. For more information about responses, see Error! Reference source not found.

[0293] ERR_RM supports both ML and SL transmission. The LLMMP format for ML transmission is shown in Table 2. The LLSMP format for SL transmission is shown in Table 3.

[0294] Table 2

[0295] Table 3

[0296] The following describes the exceptions and handling mechanisms involved in the logic layer.

[0297] The exception definitions, detection mechanisms, response mechanisms, and reporting mechanisms related to the logic layer are shown in Table 4. When the corresponding exceptions in the table occur at the logic layer, they must be handled according to the mechanisms shown in Table 4.

[0298] Table 4

[0299] Next, we will illustrate the logic blocks with examples:

[0300] The logical layer uses LLB as the basic unit of data transmission.

[0301] In TYPE-C mode, an LLB consists of 240 bytes, as shown in Figure 9. When FEC is disabled, the entire 240 bytes within the LLB constitute the LLB block body. When FEC is enabled, the first 230 bytes constitute the LLB block body, and the remaining 10 bytes constitute the LLB block trailer. The LLB block body is populated by LLDP and Logical Layer Management Messages (LLMMPs), and the LLB block trailer corresponds to the FEC-encoded check bytes. It should be noted that in the figures of the embodiments of this application, B represents a byte.

[0302] In TYPE-B mode, an LLB consists of 480 bytes, as shown in Figure 10. When FEC is disabled, the entire 480 bytes in the LLB constitute the LLB body. When FEC is enabled, the first 460 bytes constitute the LLB body, and the remaining 20 bytes constitute the LLB trailer. The LLB body is padded with LLDP and LLMMP, and the LLB trailer corresponds to the FEC-encoded check bytes.

[0303] At the electrical layer, data transmission within an LLB is sent and received byte by byte according to the LLB arrangement. By default, a single byte is sent and received starting with the lowest bit. The LLB send and receive sequence in Type-C mode is shown in Figure 11. Byte-by-byte transmission and reception begins at bit B0. Within a single byte, transmission and reception begins at bit 0 by default. The LLB send and receive sequence in Type-B mode is similar to that in Type-C mode.

[0304] The main link architecture of the unified multimedia interconnection interface logical layer is described below.

[0305] As shown in Figure 12, the unified multimedia interconnection interface logical layer main link architecture, at the sending end, the logical layer is responsible for multiplexing and encoding, FEC encoding, channel distribution, scrambling and precoding the data passed to this layer by the transport layer, and then passing it to the electrical layer; at the receiving end, the logical layer is responsible for de-precoding, descrambling, channel combination, FEC decoding and error correction, and multiplexing decoding of the data passed to this layer by the electrical layer, and then passing the data to the transport layer. The details are as follows:

[0306] Multiplexing and demultiplexing: Implements the encapsulation and parsing functions of LLDP and LLMMP, and the conversion between data packets and LLB.

[0307] FEC encoding and decoding: Implements the conversion function between LLB and FEC encoding and decoding workspaces, and implements data encoding and decoding functions in the FEC encoding and decoding workspaces.

[0308] Channel distribution and combination: Based on the enabled channel configuration, the data distribution and combination functions on each channel are realized.

[0309] Scrambling and descrambling: Each channel independently implements data scrambling and descrambling functions.

[0310] Precoding and de-precoding: Each channel independently implements data precoding and de-precoding functions.

[0311] The following is an example to illustrate multiplexing and demultiplexing.

[0312] The multiplexing layer and demultiplexing layer interact with the transport layer to process logical layer data and management messages.

[0313] The multiplexing layer multiplexes transport layer data, encapsulating the multiplexed transport layer data into LLBs and inserting logical layer management messages into the LLBs based on link management requirements. Specifically, the multiplexing layer can implement the method illustrated in Figure 4 to encapsulate the multiplexed transport layer data into LLBs and insert logical layer management messages into the LLBs based on link management requirements. During this process, logical layer management messages are inserted into the LLBs when logical layer management messages are required to be transmitted; otherwise, logical layer management messages are not inserted.

[0314] The demultiplexing layer implements the parsing of the LLB. According to the LLPH in the LLB (specifically, according to the LLPT in the LLPH), the LLB is parsed into LLDP and LLMMP, and then the data message and management message are parsed.

[0315] Specifically, the multiplexing layer may include a packet layer, which implements the packet processing of the logical layer management information and the transport layer data. The packetization method refers to the definition of the data message. Based on the functions corresponding to different management messages, the logical layer management messages can have different packet priorities. For the packet priority, refer to the relevant description in S402.

[0316] The multiplexing layer performs block encapsulation while encapsulating the packets. The specific process is as follows: while encapsulating the packets, the multiplexing layer fills the encapsulated data message into the LLB block byte by byte in byte order. The size of the encapsulated LLB is related to the port type.

[0317] On a Type-C port, when FEC is enabled, the 230-byte LLB block is used to fill data packets (LLDP, or LLDP and LLMMP). The last 10 bytes of the LLB block are fixedly filled with a 10-byte placeholder (for example, 0x00 data). After FEC encoding is completed, the last 10 bytes are replaced with the parity data generated by the FEC encoding. When FEC is disabled, the entire 240-byte LLB block is used to fill data packets (LLDP, or LLDP and LLMMP).

[0318] On a Type-B port, the LLB construction method is similar to that of a Type-C port. When FEC is enabled, the 460-byte LLB block is used to fill data packets. The last 20 bytes of the LLB block are fixedly filled with a 20-byte placeholder (for example, 0x00 data), which is replaced with a check codeword after subsequent FEC encoding is completed. When FEC is not enabled, the entire 480-byte LLB block is used to fill data packets.

[0319] LLB population must meet the following requirements: a single LLB can contain a maximum of two logical layer management messages; a single LLB can contain a fixed number of LLDP messages; and LLMMP is first populated into the LLB. LLDP is then populated after LLMMP is populated.

[0320] In TYPE-C mode, with FEC enabled and one LLMMP filled, the LLB structure corresponding to the LLMMP is shown in Figure 13. In this LLB structure, the first 8 bytes of the block are LLMMP, the remaining bytes are LLDP, and the 10-byte block trailer corresponds to the RS parameters.

[0321] Figure 14 shows the LLB structure corresponding to TYPE-C mode, FEC enabled, and no LLMMP padding. In this LLB structure, all bytes in the block body are LLDP, and the 10-byte block trailer corresponds to RS parameters.

[0322] In TYPE-C mode, FEC is disabled. The LLB structure is similar to the two structures described above (shown in Figures 13 and 14), but without an LLB trailer. The RS parameters must be replaced with the LLDP message payload data, and the corresponding LLDP message length is increased by 10.

[0323] In TYPE-B mode, with FEC enabled and two LLMMPs filled, the LLB structure corresponding to the block is shown in Figure 15. In this LLB structure, the first 16 bytes of the block are LLMMPs, the remaining bytes of the block are LLDP, and the 20-byte block trailer corresponds to the RS parameters.

[0324] Figure 16 shows the LLB structure corresponding to TYPE-B mode, FEC enabled, and no LLMMP padding. In this LLB structure, all bytes in the block body are LLDP, and the 20-byte block trailer corresponds to RS parameters.

[0325] In TYPE-B mode, FEC is disabled. The LLB structure is similar to the two preceding structures, but without an LLB block trailer. The RS parameters must be replaced with the LLDP packet payload data, and the corresponding LLDP packet length increases by 20.

[0326] The demultiplexing process is described as follows. The demultiplexing process includes deblocking and then depacketizing.

[0327] The deblocking layer in the demultiplexing layer splits the data in the LLB into LLMMP and LLDP. Specifically, it distinguishes LLMMP and LLDP based on the LLPT in the LLPH of the data packet. It then splits the LLB into data packets based on the LLMMP and LLDP packet lengths. The depacketization layer then depackets the data packets to obtain their specific content.

[0328] When FEC is not enabled, the deblocking layer directly identifies whether the LLB contains LLMMP, unpacks the identified LLMMP bytes according to the LLMMP message structure, and obtains the logical layer management message; unpacks the remaining bytes according to the LLDP message structure to obtain the transport layer data.

[0329] When FEC is enabled, FEC decoding is required first. To ensure timely logical layer management, during FEC decoding, deblocking is performed to identify whether the LLB contains an LLMMP. If an LLMMP is present, the LLMMP (corresponding bytes) identified in the LLB are sent to the depacketization layer for parsing while FEC decoding is in progress.

[0330] The rules for the deblocking layer to identify whether an LLB contains an LLMMP are as follows:

[0331] The first byte of the LLB is checked. If it indicates LLDP, the current LLB does not have an LLMMP. If it indicates LLMMP, the current LLB contains LLMMP0. If LLMMP0 is confirmed to exist, the ninth byte of the LLB is checked. If it indicates LLDP, the current LLB does not have LLMMP1. If it indicates LLMMP, the current LLB contains LLMMP1.

[0332] If FEC is enabled, the LLB needs to be deblocked again after FEC decoding. The specific rules for this deblocking are as follows:

[0333] If LLMMP0 is identified during FEC decoding and there are no CRC errors, the first 8 bytes of the LLB are discarded during deblocking after FEC decoding. If LLMMP0 is identified during FEC decoding and there is a CRC error, deblocking of the LLB begins at byte 1 after FEC decoding. If both LLMMP0 and LLMMP1 are identified during FEC decoding and there are no CRC errors, the first 16 bytes of the LLB are discarded during deblocking after FEC decoding. If LLMMP0 and LLMMP1 are identified during FEC decoding, and LLMMP0 has no CRC error but LLMMP1 has a CRC error, the first 8 bytes of the LLB are discarded during deblocking after FEC decoding, and deblocking begins at byte 9 of the LLB. If LLMMP0 and LLMMP1 are identified during FEC decoding and there is a CRC error in LLMMP0, LLMMP1 is no longer parsed, and deblocking begins at byte 1 of the LLB after FEC decoding.

[0334] After the deblocking layer parses the LLB to obtain LLDP and LLMMP, the deblocking layer processes all data packets in the LLB and performs different processing based on the data packet type.

[0335] For LLDP, after completing header verification, the depacketization layer directly discards the header data and sends the payload data to the transport layer. For LLMMP, after completing data packet verification, the depacketization layer obtains the logical layer management message parameters to implement logical layer management functions.

[0336] The above mainly introduces the solution provided by the embodiment of the present invention from the perspective of the working principle of the device. It can be understood that in order to realize the above functions, the computing device, etc. includes hardware structures and / or software modules corresponding to the execution of each function. It should be easy for those skilled in the art to realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0337] In the embodiments of the present invention, computing devices, etc., can be divided into functional modules according to the above-described method examples. For example, functional modules can be divided according to respective functions, or two or more functions can be integrated into a single processing module. The above-described integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the module division in the embodiments of the present invention is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used.

[0338] In the case of dividing each functional module according to each function, Figure 17a illustrates a device 170 for transmitting a logical layer management message provided in an embodiment of the present application. The device 170 for transmitting a logical layer management message is used to implement the functions in the above-mentioned method embodiment. As shown in Figure 17a, the device 170 for transmitting a logical layer management message may include: an encapsulation unit 1701 and a filling unit 1702. The encapsulation unit 1701 is used to execute process S401 in Figure 4, and the filling unit 1702 is used to execute process S402 in Figure 4. Among them, all relevant content of each step involved in the above-mentioned method embodiment can be referenced to the functional description of the corresponding functional module and will not be repeated here.

[0339] In another possible implementation, after filling the logical layer management message into the logical block, the filling unit 1702 is further configured to fill the logical layer data message into the logical block.

[0340] In another possible implementation, as shown in FIG17b , the apparatus 170 for transmitting logical layer management messages further includes an encoding unit 1703 for performing FEC encoding on the logical block after filling the logical layer management message and the logical layer data message into the logical block.

[0341] In another possible implementation, the length of the logical block is 240 bytes, the block body is 230 bytes, and the block trailer is 10 bytes; alternatively, the length of the logical block is 480 bytes, the block body is 460 bytes, and the block trailer is 20 bytes. Specifically, when a logical block is populated with one logical layer management message, the first 8 bytes in the block body are populated with the logical layer management message; alternatively, when a logical block is populated with two logical layer management messages, the first 16 bytes in the block body are populated with the logical layer management message; alternatively, when a logical block is not populated with a logical layer management message, no bytes in the block body are populated with the logical layer management message.

[0342] In another possible implementation, when FEC is disabled, the logical block includes a block body, and the length of the block body is 240 bytes or 480 bytes. Specifically, when the logical block is populated with one logical layer management message, the first 8 bytes of the block body are populated with the logical layer management message; or, when the logical block is populated with two logical layer management messages, the first 16 bytes of the block body are populated with the logical layer management message; or, when the logical block is not populated with a logical layer management message, no bytes of the block body are populated with the logical layer management message.

[0343] In another possible implementation, different logical layer management messages have different packet priorities. Logical layer management messages used for exception reporting and control frame transmission location messages have higher priority than other logical layer management messages. Other logical layer management messages include: link training start message, clock lock feedback message, equalization feedback message, channel lock feedback message, low power request message, link width adjustment message, channel direction adjustment message, and response message.

[0344] In another possible implementation, the filling unit 1702 is specifically configured to fill the logical layer management message into the logical block in descending order of packet priority.

[0345] In the case of dividing each functional module according to each function, Figure 18a illustrates another device 180 for transmitting logical layer management messages provided in an embodiment of the present application. The device 180 for transmitting logical layer management messages is used to implement the functions of the receiving device in the above-mentioned method embodiment. As shown in Figure 18a, the device 180 for transmitting logical layer management messages may include: a receiving unit 1801, a deblocking unit 1802 and an unpacking unit 1803. The receiving unit 1801 is used to execute the process S404 in Figure 4; the deblocking unit 1802 is used to execute the process S405 in Figure 4; and the unpacking unit 1803 is used to execute the process S406 in Figure 4. Among them, all relevant contents of each step involved in the above-mentioned method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0346] In another possible implementation, the deblocking unit 1802 is specifically used to: detect the first byte of the logical block; if the first byte indicates a logical layer data message, there is no logical layer management message in the logical block; if the first byte indicates a logical layer management message, detect the ninth byte of the logical block; if the ninth byte indicates a logical layer data message, the logical block contains one logical layer management message; if the ninth byte indicates a logical layer management message, the logical block contains two logical layer management messages.

[0347] In another possible implementation, when FEC is enabled, the deblocking unit 1802 is further configured to: if the logical block contains one logical layer management message and there is no CRC error when depacketizing the logical layer management message, discard the first 8 bytes of data when deblocking the logical block after FEC decoding. If the logical block contains one logical layer management message and there is a CRC error when depacketizing the logical layer management message, deblock the logical block starting from the first byte after FEC decoding. If the logical block contains two logical layer management messages and there is no CRC error when depacketizing the logical layer management messages, discard the first 16 bytes of data when deblocking the logical block after FEC decoding. If the logical block contains two logical layer management messages and there is no CRC error when depacketizing the logical layer management messages, while the first logical layer management message has no CRC error and the second logical layer management message has a CRC error when depacketizing the logical layer management messages, discard the first 8 bytes of data when deblocking the logical block after FEC decoding. If a logical block contains two logical layer management messages and the first logical layer management message has a CRC error when the logical layer management messages are depacketized, the logical block is depacketized starting from the first byte after FEC decoding.

[0348] In another possible implementation, when FEC is not enabled, the depacketizing unit 1803 is further configured to: depacketize the logical layer data message for the data other than the logical layer management message in the logical block.

[0349] In another possible implementation, as shown in FIG18b , the apparatus 180 for transmitting a logical layer management message further includes a decoding unit 1804 configured to perform FEC decoding on the logical block after unpacking the logical layer management message.

[0350] In another possible implementation, the unpacking unit 1803 is further configured to: if the logic block does not contain the logic layer management message, unpack the logic block according to the logic layer data message.

[0351] In the case of adopting an integrated unit, as shown in Figure 19, another device 190 for transmitting logical layer management messages provided in an embodiment of the present application is used to implement the functions of the computing device or receiving device in the above-mentioned embodiment. The device 190 for transmitting logical layer management messages includes a processing module 1901 and a communication module 1902. The processing module 1901 is used to control and manage the actions of the device 190 for transmitting logical layer management messages, and the communication module 1902 is used to communicate with other devices. For example, the processing module 1901 is used to execute any of the processes S401-S406 in Figure 4; the communication module 1902 is used for the device 190 for transmitting logical layer management messages to interact with other devices. The device 190 for transmitting logical layer management messages may also include a storage module 1903 for storing program code and data of the device 190 for transmitting logical layer management messages.

[0352] The processing module 1901 may be the processor 3010 in the physical structure of the computing device 30 shown in FIG3 , and may be a processor or controller. For example, it may be a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processing module 1901 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on. The communication module 1902 may be the communication interface 3040 in the physical structure of the computing device 30 shown in FIG3 . The communication module 1902 may be a communication port, or may be a transceiver, a transceiver circuit, or a communication interface. Alternatively, the communication interface may enable communication with other devices through the aforementioned transceiver components. The transceiver components may be implemented by antennas and / or radio frequency devices. The storage module 1903 may be the memory 3030 in the physical structure of the computing device 30 shown in FIG3 .

[0353] As mentioned above, the apparatus 170 for transmitting logical layer management messages, the apparatus 180 for transmitting logical layer management messages, and the apparatus 190 for transmitting logical layer management messages provided in the embodiments of the present application can be used to implement the functions of the computing device or the receiving end device in the above-mentioned embodiments of the present application. For ease of explanation, only the parts related to the embodiments of the present application are shown. For specific technical details not disclosed, please refer to the embodiments of the present application.

[0354] On the other hand, an embodiment of the present application provides a system for transmitting logical layer management messages, including the above-mentioned device 170 for transmitting control frames or the device 180 for transmitting control frames.

[0355] As another form of this embodiment, a computer-readable storage medium is provided, on which instructions are stored. When the instructions are executed, the method for transmitting logical layer management messages in the above method embodiment is executed.

[0356] As another form of this embodiment, a computer program product containing instructions is provided. When the computer program product is run on a computer, the computer is caused to execute the method for transmitting logical layer management messages in the above method embodiment.

[0357] As another form of this embodiment, a chip is provided, comprising one or more interface circuits and one or more processors. The interface circuits are configured to receive signals from a memory of an electronic device and transmit the received signals to the processors, the signals comprising computer instructions stored in the memory. When the processors execute the computer instructions, the electronic device performs the operational steps of the method described in the first aspect or any possible implementation.

[0358] The embodiment of the present application further provides a chip system, which includes a processor for implementing the technical method of the embodiment of the present application. In one possible design, the chip system also includes a memory for storing the necessary program instructions and / or data of the embodiment of the present invention. In one possible design, the chip system also includes a memory for the processor to call the application code stored in the memory. The chip system can be composed of one or more chips, or can include chips and other discrete devices, which is not specifically limited in the embodiment of the present application.

[0359] Those skilled in the art will readily appreciate that, in conjunction with the various exemplary units and method steps described in the embodiments disclosed herein, this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a hardware-driven manner by computer software depends on the specific application scenario and design constraints of the technical solution.

[0360] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded or executed on a computer, the process or function described in the embodiment of the present application of the present invention is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be an SSD.

[0361] The above is only a specific embodiment of the present application, but the scope of protection of this application is not limited to this. Any changes or substitutions within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for transmitting logical layer management messages, characterized in that, the method includes: Encapsulating the logical layer management message into a logical layer management packet, where the logical layer management packet includes a logical layer packet type LLPT field, and the LLPT field is assigned a first value indicating that the current data packet type is a logical layer management packet; Filling the logical layer management packet into a logical block, where the logical block is also used to fill a logical layer data packet encapsulating transport layer data, and the logical layer data packet includes the LLPT field, and the LLPT field is assigned a second value indicating that the current data packet type is a logical layer data packet.

2. The method according to claim 1, characterized in that, At most two logical layer management packets are included in a single logical block.

3. The method according to claim 1 or 2, characterized in that, After filling the logical layer management packet into the logical block, the method further includes: filling the logical layer data packet in the logical block.

4. The method according to any one of claims 1-3, characterized in that, A single logical block includes one logical layer data packet.

5. The method according to any one of claims 1-4, characterized in that, The first value is 0xF0, and the second value is 0x0F.

6. The method according to any one of claims 1-5, characterized in that, The logical layer management packet is a logical layer main link management packet LLMMP, and the length of the logical layer management packet is 8 bytes; The logical layer management packet is composed of a logical layer packet header LLPH, a logical layer packet payload LLPP, and a cyclic redundancy check CRC code; The length of the LLPH is 2 bytes, the LLPH includes the LLPT field, and the LLPH also includes a logical layer management message type LLMMT field, and the LLMMT field represents the message type carried by the current LLMMP; The length of the LLPP is 4 bytes; The length of the CRC code is 2 bytes, and the CRC code is used to fill the check information of all parameters in the reserved field, LLMMT field, and LLPP field of the current data packet.

7. The method according to any one of claims 1-6, characterized in that, When forward error correction FEC is enabled, the logical block includes a block body and a block tail, the block body is filled with the logical layer management packet and the logical layer data packet, and the block tail corresponds to the check information of the FEC encoding.

8. The method according to claim 7, characterized in that, The method further includes: After filling the logical layer management packet and the logical layer data packet into the logical block, performing FEC encoding on the logical block.

9. The method according to claim 7 or 8, characterized in that, The length of the logical block is 240 bytes, the block body is 230 bytes, and the block tail is 10 bytes; or, the length of the logical block is 480 bytes, the block body is 460 bytes, and the block tail is 20 bytes; Wherein, when filling one logical layer management packet in the logical block, the first 8 bytes in the block body are filled with the logical layer management packet; Alternatively, when filling two logical layer management messages in the logical block, the first 16 bytes in the block body are filled with the logical layer management message. Alternatively, when not filling the logical layer management message in the logical block, there are no bytes in the block body filled with the logical layer management message.

10. The method according to any one of claims 1-9, characterized in that when FEC is not enabled, the logical block includes a block body, and the length of the block body is 240 bytes or 480 bytes; wherein, when filling one logical layer management message in the logical block, the first 8 bytes in the block body are filled with the logical layer management message; Alternatively, when filling two logical layer management messages in the logical block, the first 16 bytes in the block body are filled with the logical layer management message; Alternatively, when not filling the logical layer management message in the logical block, there are no bytes in the block body filled with the logical layer management message.

11. The method according to claim 6, characterized in that the logical layer management message includes one or more of the following: Link Training Start Message TSM, the LLMMT field of the TSM is configured as 0x11; or, Clock Lock Feedback Message CLFM, the LLMMT field of the CLFM is configured as 0x12; or, Clock Lock Feedback Acknowledgment Message CLFM_ACK, the LLMMT field of the CLFM_ACK is configured as 0x02; or, Equalization Feedback Message EQFM, the LLMMT field of the EQFM is configured as 0x13; or, Equalization Feedback Acknowledgment Message EQFM_ACK, the LLMMT field of the EQFM_ACK is configured as 0x03; or, Channel Lock Feedback Message LLFM, the LLMMT field of the LLFM is configured as 0x14; or, Low Power Request Message LPRM, the LLMMT field of the LPRM is configured as 0x21; or, Link Width Adjustment Message LWAM, the LLMMT field of the LPRM is configured as 0x22; or, Channel Direction Adjustment Message LDAM, the LLMMT field of the LDAM is configured as 0x23; or, Control Frame Transmission Location Information CFSLM, the LLMMT field of the CFSLM is configured as 0x24; or, Timestamp Message TM, the LLMMT field of the TM is configured as 0x25; or, Acknowledgment Message Ack / Nack, the LLMMT field of the Ack / Nack is configured as 0x2A; or, Exception Report Message ERR_RM, the LLMMT field of the ERR_RM is configured as 0x2B.

12. The method according to any one of claims 1-11, characterized in that different logical layer management messages have different packet priorities; the priorities of the logical layer management messages for exception reporting and the control frame transmission location message are higher than those of other logical layer management messages; the other logical layer management messages include: Link Training Start Message, Clock Lock Feedback Message, Equalization Feedback Message, Channel Lock Feedback Message, Low Power Request Message, Link Width Adjustment Message, Channel Direction Adjustment Message, Acknowledgment Message.

13. The method according to claim 12, wherein, said filling the message to be transmitted into the logical block includes: filling the logical layer management message into the logical block in the order from the highest packet priority to the lowest packet priority.

14. A method for transmitting a logical layer management message, wherein, the method includes: receiving a logical block; deblocking the logical block to identify whether the logical block contains a logical layer management message; if it is identified that the logical block contains the logical layer management message, unpacking the logical layer management message.

15. The method according to claim 14, wherein, said deblocking the logical block to identify whether the logical block contains a logical layer management message includes: detecting the first byte of the logical block; if the first byte indicates a logical layer data message, there is no logical layer management message in the logical block; if the first byte indicates a logical layer management message, detecting the ninth byte of the logical block; if the ninth byte indicates a logical layer data message, the logical block contains one logical layer management message; if the ninth byte indicates a logical layer management message, the logical block contains two logical layer management messages.

16. The method according to claim 14 or 15, wherein, when forward error correction (FEC) is enabled, the method further includes: if the logical block contains one logical layer management message and there is no CRC error when unpacking the logical layer management message, discarding the first 8 bytes of data when deblocking the logical block after FEC decoding; if the logical block contains one logical layer management message and there is a CRC error when unpacking the logical layer management message, deblocking the logical block starting from the first byte after FEC decoding; if the logical block contains two logical layer management messages and there is no CRC error when unpacking the logical layer management message, discarding the first 16 bytes of data when deblocking the logical block after FEC decoding; if the logical block contains two logical layer management messages and there is no CRC error for the first logical layer management message and there is a CRC error for the second logical layer management message when unpacking the logical layer management message, discarding the first 8 bytes of data when deblocking the logical block after FEC decoding; if the logical block contains two logical layer management messages and there is a CRC error for the first logical layer management message when unpacking the logical layer management message, deblocking the logical block starting from the first byte after FEC decoding.

17. The method according to any one of claims 14-16, wherein, when FEC is not enabled, the method further includes: unpacking the logical layer data message for the data other than the logical layer management message in the logical block.

18. The method according to any one of claims 14-17, wherein, at most two logical layer management messages are included in a single logical block.

19. The method according to any one of claims 14-18, wherein, Encapsulate a logical layer data packet in a single said logical block.

20. The method according to any one of claims 14-19, wherein, the logical layer management packet is a logical layer main link management packet LLMMP, and the length of the logical layer management packet is 8 bytes; the logical layer management packet is composed of a logical layer packet header LLPH, a logical layer packet payload LLPP, and a cyclic redundancy check CRC code; the length of the LLPH is 2 bytes, and the LLPH includes a logical layer packet type LLPT field, and the LLPT field is assigned 0xF0; the LLPH also includes a logical layer management message type LLMMT field, and the LLMMT field represents the message type carried by the current LLMMP; the length of the LLPP is 4 bytes; the length of the CRC code is 2 bytes, and the CRC code is used to fill the check information of all parameters in the reserved field, LLMMT field, and LLPP field of the current data packet.

21. The method according to any one of claims 14-20, wherein, when FEC is enabled, the logical block includes a block body and a block tail, the block body is filled with the logical layer management packet and the logical layer data packet, and the block tail corresponds to the check information of the FEC encoding.

22. The method according to claim 21, wherein, the method further includes: after unpacking the logical layer management packet, perform FEC decoding on the logical block.

23. The method according to claim 21 or 22, wherein, the length of the logical block is 240 bytes, the block body is 230 bytes, and the block tail is 10 bytes; or, the length of the logical block is 480 bytes, the block body is 460 bytes, and the block tail is 20 bytes; wherein, when filling one logical layer management packet in the logical block, the first 8 bytes in the block body are filled with the logical layer management packet; or, when filling two logical layer management packets in the logical block, the first 16 bytes in the block body are filled with the logical layer management packet; or, when not filling the logical layer management packet in the logical block, there are no bytes in the block body filled with the logical layer management packet.

24. The method according to any one of claims 14-23, wherein, when FEC is not enabled, the length of the logical block is 480 bytes, and all 240 bytes in the logical block are the block body, or, the length of the logical block is 480 bytes, and all 480 bytes in the logical block are the block body; wherein, when filling one logical layer management packet in the logical block, the first 8 bytes in the block body are filled with the logical layer management packet; or, when filling two logical layer management packets in the logical block, the first 16 bytes in the block body are filled with the logical layer management packet; or, when not filling the logical layer management packet in the logical block, there are no bytes in the block body filled with the logical layer management packet.

25. The method according to claim 20, wherein, the logical layer management message includes one or more of the following: Link training start message TSM, the LLMMT field of the TSM is configured as 0x11; or, Clock lock feedback message CLFM, the LLMMT field of the CLFM is configured as 0x12; or, Clock lock feedback acknowledgment message CLFM_ACK, the LLMMT field of the CLFM_ACK is configured as 0x02; or, Equalization feedback message EQFM, the LLMMT field of the EQFM is configured as 0x13; or, Equalization feedback acknowledgment message EQFM_ACK, the LLMMT field of the EQFM_ACK is configured as 0x03; or, Channel lock feedback message LLFM, the LLMMT field of the LLFM is configured as 0x14; or, Low power request message LPRM, the LLMMT field of the LPRM is configured as 0x21; or, Link width adjustment message LWAM, the LLMMT field of the LPRM is configured as 0x22; or, Channel direction adjustment message LDAM, the LDAM's LLMMT field is configured as 0x23; or, Control frame transmission position information CFSLM, the LLMMT field of the CFSLM is configured as 0x24; or, Timestamp message TM, the LLMMT field of the TM is configured as 0x25; or, Response message Ack / Nack, the LLMMT field of the Ack / Nack is configured as 0x2A; or, Exception reporting message ERR_RM, the LLMMT field of the ERR_RM is configured as 0x2B.

26. The method according to any one of claims 14-25, wherein, the method further includes: If the logical block does not contain a logical layer management message, unpack the logical block according to the logical layer data message.

27. A device for transmitting logical layer management messages, wherein, the device includes: An encapsulation unit for encapsulating the logical layer management message into a logical layer management message, and the logical layer management message includes a logical layer message type LLPT field, and the LLPT field is assigned a first value indicating that the current data message type is a logical layer management message; A filling unit for filling the logical layer management message into a logical block, and the logical block is also used to fill the logical layer data message encapsulating the transport layer data, and the logical layer data message includes the LLPT field, and the LLPT field is assigned a second value indicating that the current data message type is a logical layer data message.

28. The device according to claim 27, wherein, At most two logical layer management messages are included in a single logical block.

29. The device according to claim 27 or 28, wherein, The filling unit is further configured to: after filling the logical layer management message into the logical block, fill the logical layer data message in the logical block.

30. The device according to any one of claims 27-29, wherein, A single logical block includes one logical layer data message.

31. The device according to any one of claims 27-30, wherein, The first value is 0xF0 and the second value is 0x0F.

32. The device according to any one of claims 27-31, wherein, the logical layer management message is a logical layer main link management message LLMMP, and the length of the logical layer management message is 8 bytes; the logical layer management message is composed of a logical layer message header LLPH, a logical layer message payload LLPP, and a cyclic redundancy check CRC code; the length of the LLPH is 2 bytes, the LLPT field is included in the LLPH, and a logical layer management message type LLMMT field is also included in the LLPH, and the LLMMT field represents the message type carried by the current LLMMP; the length of the LLPP is 4 bytes; the length of the CRC code is 2 bytes, and the CRC code is used to fill the check information of all parameters in the reserved field, LLMMT field, and LLPP field of the current data message.

33. The device according to any one of claims 27-32, wherein, when forward error correction FEC is enabled, the logical block includes a block body and a block tail. The block body is filled with the logical layer management message and the logical layer data message, and the block tail corresponds to the check information of the FEC encoding.

34. The device according to claim 33, wherein, the device further includes an encoding unit for performing FEC encoding on the logical block after filling the logical layer management message and the logical layer data message into the logical block.

35. The device according to claim 33 or 34, wherein, the length of the logical block is 240 bytes, the block body is 230 bytes, and the block tail is 10 bytes; or the length of the logical block is 480 bytes, the block body is 460 bytes, and the block tail is 20 bytes; wherein, when filling one logical layer management message in the logical block, the first 8 bytes in the block body are filled with the logical layer management message; or, when filling two logical layer management messages in the logical block, the first 16 bytes in the block body are filled with the logical layer management message; or, when not filling the logical layer management message in the logical block, there are no bytes in the block body filled with the logical layer management message.

36. The device according to any one of claims 27-35, wherein, when FEC is not enabled, the logical block includes a block body, and the length of the block body is 240 bytes or 480 bytes; wherein, when filling one logical layer management message in the logical block, the first 8 bytes in the block body are filled with the logical layer management message; or, when filling two logical layer management messages in the logical block, the first 16 bytes in the block body are filled with the logical layer management message; or, when not filling the logical layer management message in the logical block, there are no bytes in the block body filled with the logical layer management message.

37. The device according to claim 32, wherein, the logical layer management message includes one or more of the following: a link training start message TSM, and the LLMMT field of the TSM is configured to 0x11; or, Clock Locking Feedback Message CLFM, where the LLMMT field of the CLFM is configured as 0x12; or, Clock Locking Feedback Acknowledgment Message CLFM_ACK, where the LLMMT field of the CLFM_ACK is configured as 0x02; or, Equalization Feedback Message EQFM, where the LLMMT field of the EQFM is configured as 0x13; or, Equalization Feedback Acknowledgment Message EQFM_ACK, where the LLMMT field of the EQFM_ACK is configured as 0x03; or, Link Locking Feedback Message LLFM, where the LLMMT field of the LLFM is configured as 0x14; or, Low Power Request Message LPRM, where the LLMMT field of the LPRM is configured as 0x21; or, Link Width Adjustment Message LWAM, where the LLMMT field of the LPRM is configured as 0x22; or, Link Direction Adjustment Message LDAM, where the LLMMT field of the LDAM is configured as 0x23; or, Control Frame Sending Location Message CFSLM, where the LLMMT field of the CFSLM is configured as 0x24; or, Timestamp Message TM, where the LLMMT field of the TM is configured as 0x25; or, Acknowledgment / Negative Acknowledgment Message Ack / Nack, where the LLMMT field of the Ack / Nack is configured as 0x2A; or, Exception Reporting Message ERR_RM, where the LLMMT field of the ERR_RM is configured as 0x2B.

38. The apparatus according to any one of claims 27 - 37, characterized in that different logical layer management messages have different packet priorities; the priorities of the logical layer management messages for exception reporting and the control frame sending location message are higher than those of other logical layer management messages; the other logical layer management messages include: Link Training Start Message, Clock Locking Feedback Message, Equalization Feedback Message, Link Locking Feedback Message, Low Power Request Message, Link Width Adjustment Message, Link Direction Adjustment Message, Acknowledgment Message.

39. The apparatus according to claim 38, characterized in that the filling unit is specifically configured to: fill the logical layer management packets into the logical block in the order from the highest to the lowest packet priority.

40. An apparatus for transmitting logical layer management messages, characterized in that the apparatus includes: a receiving unit, configured to receive a logical block; a deblocking unit, configured to deblock the logical block and identify whether the logical block contains a logical layer management packet; a depacketizing unit, configured to, if the deblocking unit identifies that the logical block contains the logical layer management packet, depacketize the logical layer management packet.

41. The apparatus according to claim 40, characterized in that the deblocking unit is specifically configured to: detect the first byte of the logical block; if the first byte indicates a logical layer data packet, there is no logical layer management packet in the logical block; if the first byte indicates a logical layer management packet, detect the ninth byte of the logical block; if the ninth byte indicates a logical layer data packet, the logical block contains one logical layer management packet; If the 9th byte indicates a logical layer management message, then there are two logical layer management messages in the logical block.

42. The apparatus according to claim 40 or 41, wherein, when forward error correction (FEC) is enabled, the deblocking unit is further configured to: if there is one logical layer management message in the logical block and there is no CRC error when unpacking the logical layer management message, when deblocking the logical block after FEC decoding, discard the first 8 bytes of data; if there is one logical layer management message in the logical block and there is a CRC error when unpacking the logical layer management message, when deblocking the logical block after FEC decoding, start deblocking the logical block from the 1st byte; if there are two logical layer management messages in the logical block and there is no CRC error when unpacking the logical layer management messages, when deblocking the logical block after FEC decoding, discard the first 16 bytes of data; if there are two logical layer management messages in the logical block and there is no CRC error in the first logical layer management message and there is a CRC error in the second logical layer management message when unpacking the logical layer management messages, when deblocking the logical block after FEC decoding, discard the first 8 bytes of data; if there are two logical layer management messages in the logical block and there is a CRC error in the first logical layer management message when unpacking the logical layer management messages, when deblocking the logical block after FEC decoding, start deblocking the logical block from the 1st byte.

43. The apparatus according to any one of claims 40 - 42, wherein, when FEC is not enabled, the unpacking unit is further configured to: unpack the logical layer data messages for the data other than the logical layer management message in the logical block.

44. The apparatus according to any one of claims 40 - 43, wherein, at most two logical layer management messages are included in a single logical block.

45. The apparatus according to any one of claims 40 - 44, wherein, a single logical block encapsulates one logical layer data message.

46. The apparatus according to any one of claims 40 - 45, wherein, the logical layer management message is a logical layer main link management message (LLMMP), and the length of the logical layer management message is 8 bytes; the logical layer management message consists of a logical layer message header (LLPH), a logical layer message payload (LLPP), and a cyclic redundancy check (CRC) code; the length of the LLPH is 2 bytes, the LLPH includes a logical layer message type (LLPT) field, and the value of the LLPT field is 0xF0; the LLPH also includes a logical layer management message type (LLMMT) field, and the LLMMT field represents the message type carried by the current LLMMP; the length of the LLPP is 4 bytes; the length of the CRC code is 2 bytes, and the CRC code is used to fill the check information of all parameters in the reserved field, the LLMMT field, and the LLPP field of the current data message.

47. The apparatus according to any one of claims 40 - 46, wherein, When FEC is enabled, the logic block includes a block body and a block tail. The block body is filled with the logic layer management message and the logic layer data message, and the block tail corresponds to the check information of FEC encoding.

48. The device according to claim 47, wherein, the device further includes a decoding unit for: after unpacking the logic layer management message, performing FEC decoding on the logic block.

49. The device according to claim 47 or 48, wherein, the length of the logic block is 240 bytes, the block body is 230 bytes, and the block tail is 10 bytes; or, the length of the logic block is 480 bytes, the block body is 460 bytes, and the block tail is 20 bytes; wherein, when filling one logic layer management message in the logic block, the first 8 bytes in the block body are filled with the logic layer management message; or, when filling two logic layer management messages in the logic block, the first 16 bytes in the block body are filled with the logic layer management message; or, when not filling the logic layer management message in the logic block, there are no bytes in the block body filled with the logic layer management message.

50. The device according to any one of claims 40-49, wherein, when FEC is not enabled, the length of the logic block is 480 bytes, and all 240 bytes in the logic block are the block body, or, the length of the logic block is 480 bytes, and all 480 bytes in the logic block are the block body; wherein, when filling one logic layer management message in the logic block, the first 8 bytes in the block body are filled with the logic layer management message; or, when filling two logic layer management messages in the logic block, the first 16 bytes in the block body are filled with the logic layer management message; or, when not filling the logic layer management message in the logic block, there are no bytes in the block body filled with the logic layer management message.

51. The device according to claim 46, wherein, the logic layer management message includes one or more of the following: Link Training Start Message TSM, and the LLMMT field of the TSM is configured as 0x11; or, Clock Lock Feedback Message CLFM, and the LLMMT field of the CLFM is configured as 0x12; or, Clock Lock Feedback Acknowledgment Message CLFM_ACK, and the LLMMT field of the CLFM_ACK is configured as 0x02; or, Equalization Feedback Message EQFM, and the LLMMT field of the EQFM is configured as 0x13; or, Equalization Feedback Acknowledgment Message EQFM_ACK, and the LLMMT field of the EQFM_ACK is configured as 0x03; or, Link Lock Feedback Message LLFM, and the LLMMT field of the LLFM is configured as 0x14; or, Low Power Request Message LPRM, and the LLMMT field of the LPRM is configured as 0x21; or, Link Width Adjustment Message LWAM, and the LLMMT field of the LPRM is configured as 0x22; or, Link Direction Adjustment Message LDAM, and the LLMMT field of the LDAM is configured as 0x23; or, Control Frame Transmission Location Information CFSLM, the LLMMT field of the CFSLM is configured as 0x24; or, Timestamp Message TM, the LLMMT field of the TM is configured as 0x25; or, Acknowledge Message Ack / Nack, the LLMMT field of the Ack / Nack is configured as 0x2A; or, Exception Report Message ERR_RM, the LLMMT field of the ERR_RM is configured as 0x2B.

52. The apparatus according to any one of claims 40-51, wherein, the unpacking unit is further configured to: if the deblocking unit identifies that the logical block does not contain a logical layer management message, unpack the logical block according to a logical layer data message.

53. A computing device, wherein, the computing device includes a memory and at least one processor, the memory is used to store a set of computer instructions; when the processor executes the set of computer instructions, perform the operation steps of the method according to any one of claims 1-26 above.

54. A data transmission system, wherein, the data transmission system includes a data sending device and / or a data receiving device, the data sending device is used to execute the method of transmitting a logical layer management message according to any one of claims 1-13, and the data receiving device is used to execute the method of transmitting a logical layer management message according to any one of claims 14-26.

55. A chip, wherein, includes one or more interface circuits and one or more processors; the interface circuit is used to receive a signal from the memory of the electronic device and send the signal to the processor, the signal includes computer instructions stored in the memory; when the processor executes the computer instructions, the electronic device is caused to perform the operations of the method according to any one of claims 1-26.

56. A computer-readable storage medium, wherein, includes: computer software instructions; when the computer software instructions run on a computer, the computer is caused to perform the operation steps of the method according to any one of claims 1-26 above.

57. A computer program product, wherein, the computer program product contains a software program, when the software program is executed by a computer or a processor, the computer or the processor is caused to perform the operation steps of the method according to any one of claims 1-26 above.

Images