CN116601897A - A data transmission method and device - Google Patents

Abstract

The application discloses a data transmission method and a data transmission device, which can be used for assisting driving and automatic driving and are used for solving the problem that the reproduction of a PHY code block is wrong due to the out-of-step of a PHY clock. The method comprises the following steps: and generating and transmitting first information, wherein the first information comprises first PID synchronous information, and the first PID synchronous information is used for PID synchronization. In the embodiment of the application, the first equipment sends the PID synchronous information to the second equipment, so that the second equipment can calibrate the PID count according to the PID synchronous information, and the data receiving end can correctly indicate the error transmitted PHY code block by using the calibrated PID, thereby avoiding error retransmission. Further, the method can be applied to the Internet of vehicles, such as vehicle external connection V2X, workshop communication long-term evolution technology LTE-V, vehicle-vehicle V2V and the like.

Description

A data transmission method and device technical field

The present application relates to the technical field of communications, and in particular to a data transmission method and device.

Background technique

In high-speed wired transmission, especially some car serializer/deserializer (SerDes) transmission, due to the high bit error rate (bit error rate, BER) requirements, it is usually considered to improve the transmission chain through retransmission. road reliability.

In SerDes transmission, the originating end (the first device) sends physical layer (physical layer, PHY) code blocks sequentially, and one PHY code block is one physical layer Reed-Solomon error correction coding block (physical layer RS-FEC block, PLRB), and One PHY code block carries one physical layer content block (physical layer content block, PLCB). When the transmission of the PHY code block fails, the receiving end (the second device) sends an acknowledgment message (ACK) to the first device, and indicates the failed PHY code block through the PLRB number (PLRB Identifier, PID) information carried in the ACK. The first device encapsulates the PLCB carried by the failed PHY code block into a new PHY code block and sends it to the second device to complete the retransmission. For example, when the transmission of PHY code block 2 fails, the second device sends an ACK to the first device, and indicates that the reception of PHY code block 2 fails through the PID information carried in the ACK. The first device encapsulates the PLCB 2 carried by the PHY code block 2 into the PHY code block 5 and sends it to the second device to complete the retransmission.

In SerDes transmission, the first device and the second device implement clock synchronization of the PHY code blocks during link establishment, so as to determine the number of the PHY code blocks according to the clock count. In an interference scenario, longer duration interference can cause the PHY clock to lose synchronization. However, the out-of-synchronization of the PHY clock will lead to inaccurate counting of the PHY code blocks performed by the second device, thus resulting in errors in the retransmission of the PHY code blocks.

Contents of the invention

The present application provides a data transmission method and device, which are used to solve the problem of retransmission errors of PHY code blocks caused by PHY clock out-of-synchronization.

In a first aspect, an embodiment of the present application provides a data transmission method, including: generating and sending first information, where the first information includes first PID synchronization information, and the first PID synchronization information is used for PID synchronization.

In the embodiment of the present application, the first device sends PID synchronization information to the second device, so that the second device can calibrate the PID count according to the PID synchronization information, so that the data receiving end uses the PHY code block indicated by the PID information and the data sending end according to the PID The PHY code blocks determined by the information are consistent, thereby avoiding erroneous retransmission.

In a possible design, the PID synchronization includes PID count synchronization between the first device and the second device. In the above design, the first device and the second device can perform PID count synchronization through the PID synchronization information, so that the first device and the second device can determine the same PHY code block through the PID, thereby avoiding erroneous retransmission.

In a possible design, the first information is a synchronization symbol, and the synchronization symbol includes a time base field, and the time base field carries the first PID synchronization information. In the above design, by multiplexing the synchronization symbols sent periodically, the data receiving end can complete the PID count synchronization while restoring the PHY code block delimitation and scrambling code synchronization, so as to avoid erroneous retransmission after the link is restored.

In a possible design, the synchronization symbol further includes a time base identification field for indicating a time base number, wherein the time base number indicated by the time base identification field is a first value, and the first value indicates that the time base field carries the first PID synchronization information. In the above method, the first value is used as the synchronization symbol to carry the identification of the PID synchronization information, so that the second device can read the PID synchronization information in the time base field when the time base number indicated by the time base ID field is the first value.

In a possible design, the first PID synchronization information is used to indicate the PID of the PLRB sent before the first information; or, the first PID synchronization information is used to indicate the PID of the PLRB sent after the first information. In the above design, the first device indicates the PID of a PLRB at a specific location, so that the second device can calibrate the PID of the PLRB, thereby achieving PID count synchronization.

In a possible design, the first information is a PLRB, and the PLRB includes a physical layer content block (PLCB) payload field, and the PLCB payload field carries the first PID synchronization information. In the above embodiments, PHY control messages can be used to carry PID synchronization information, so that PID synchronization can be realized, and erroneous retransmission can be avoided.

In a possible design, the first PID synchronization information is the PID of the first information. The above design carries the PID of the first information in the first information, so that the second device can calibrate the PID count of the first information after receiving the first information.

In a possible design, the PLCB payload field includes a first field, a second field and a third field, the first field indicates that the first information carries non-data information, and the second field indicates that the type of non-data information is PID synchronization information , the third field carries the first PID synchronization information. In the above design, the PHY control information carries the first PID synchronization information, so that the second device indicates that the first information carries non-data information in the first field, and reads in the third field when the second field indicates that the type of non-data information is PID synchronization information. Get the first PID synchronization information.

In a possible design, the third field includes a first subfield, and the first subfield indicates that the first PID synchronization information is a PID synchronization response message. In the above design, the response message and the request message can be distinguished through the first subfield.

In a possible design, before generating the first information, the method further includes: receiving second information, where the second information carries second PID synchronization information, and the second PID synchronization information is used to request the first PID synchronization information. In the above design, the first information may be sent at the request of the second device.

In a possible design, the second information is a PLRB, and the PLRB includes a PLCB payload field; the PLCB payload field carries second PID synchronization information. In the above implementation manner, the PHY control message can be used to carry the second PID synchronization information, so that PID synchronization can be realized, and erroneous retransmission can be avoided.

In a possible design, the PLCB payload field includes a first field, a second field and a third field, the first field indicates that the second information carries non-data information, and the second field indicates that the type of non-data information is PID synchronization information , the third field carries the second PID synchronization information. In the above design, the PHY control information carries the second PID synchronization information, so that the second device indicates that the first information carries non-data information in the first field, and reads in the third field when the second field indicates that the type of non-data information is PID synchronization information. Get the second PID synchronization information.

In a possible design, the third field includes a first subfield, and the first subfield indicates that the second PID synchronization information is a PID synchronization request message. In the above design, the response message and the request message can be distinguished through the first subfield.

In a possible design, the third field further includes a second subfield and at least one of the following subfields: a third subfield and a fourth subfield; where the second subfield is used to carry the PID of the corresponding PLRB , the third subfield is used to indicate the transmission direction for PID synchronization; the fourth subfield is used to indicate the transmission direction of the corresponding PLRB. Through the above design, the accuracy of PID synchronization can be improved.

In the second aspect, the embodiment of the present application provides a data transmission method, including: generating and sending at least two code blocks, at least two code blocks each carrying a physical layer content block (PLCB), and at least two code blocks At least one of the first code blocks carries PLCB control information, and the PLCB control information includes PLCB identification information and corresponding indication information, and the indication information indicates that PLCB is the Nth transmission, and N is a positive integer.

In the embodiment of the present application, the PHY code block is determined by the identifier of the PLCB and the retransmission times of the PLCB, so that the second device can accurately indicate the wrong PHY code block, thereby avoiding retransmission errors. Moreover, in this way, the sending and receiving ends do not need to maintain the PID.

In a possible design, the first code block is a PLRB, and the first code block includes a PLCB control field, and the PLCB control field carries PLCB control information. In the foregoing implementation manner, the PLCB control field may be used to carry PLCB control information.

In a possible design, the method further includes: receiving a second code block, where the second code block carries retransmission information, and the retransmission information includes: identification information of the first PLCB, indication information of the first PLCB, and receiving status information, The identification information of the first PLCB is the ID of a PLCB successfully received, the indication information of the first PLCB indicates that the first PLCB is the Mth transmission, M is a positive integer, and the receiving status information indicates the receiving status of at least two code blocks; The retransmission information determines a PLCB that fails to be transmitted among the PLCBs carried by at least two code blocks. In the above design, by carrying retransmission information in the second code block, the first device can determine a PHY code block according to the retransmission information, so that the PHY code block that transmits an error can be determined according to the PHY code block.

In a possible design, the second code block is a PLRB, the second code block includes a PLCB payload field, and the PLCB payload field carries retransmission information. In the foregoing implementation manner, the PLCB payload field may be used to carry retransmission information.

In a possible design, the PLCB payload field includes a first field, a second field and a third field, the first field indicates that the second code block carries non-data information, and the second field indicates that the type of non-data information is a transmission confirmation information, and the third field carries retransmission information. In the above design, the retransmission information is carried by the PHY control information, so that the second device indicates that the second code block carries non-data information in the first field, and reads in the third field when the second field indicates that the type of non-data information is transmission confirmation information Retransmit the message.

In a possible design, the third field also indicates the type of error feedback, the type of error feedback is complete error feedback or partial error feedback, the complete error feedback indicates that the reception status indicates the second PLCB that received all errors, and the partial error feedback indicates that the second PLCB received errors The status only indicates that the second PLCB was partially received incorrectly. Through the above design, the second device can determine the feedback range.

In the third aspect, the embodiment of the present application provides a data transmission method, including: receiving the first information and performing PID synchronization according to the first PID synchronization information, the first information includes the first physical layer Reed-Solomon error correction coding block identifier PID Synchronization information, the first PID synchronization information is used for PID synchronization.

In the embodiment of the present application, the first device sends PID synchronization information to the second device, so that the second device can calibrate the PID count according to the PID synchronization information, so that the data receiving end uses the PHY code block indicated by the PID information and the data sending end according to the PID The PHY code blocks determined by the information are consistent, thereby avoiding erroneous retransmission.

In a possible design, the PID synchronization includes PID count synchronization between the first device and the second device. In the above design, the first device and the second device can perform PID count synchronization through the PID synchronization information, so that the first device and the second device can determine the same PHY code block through the PID, thereby avoiding erroneous retransmission.

In a possible design, the first information is a synchronization symbol, and the synchronization symbol includes a time base field, and the time base field carries the first PID synchronization information. In the above design, by multiplexing the synchronization symbols sent periodically, the data receiving end can complete the PID count synchronization while restoring the PHY code block delimitation and scrambling code synchronization, so as to avoid erroneous retransmission after the link is restored.

In a possible design, the synchronization symbol further includes a time base identification field for indicating a time base number, wherein the time base number indicated by the time base identification field is a first value, and the first value indicates that the time base field carries the first PID synchronization information. In the above method, the first value is used as the synchronization symbol to carry the identification of the PID synchronization information, so that the second device can read the PID synchronization information in the time base field when the time base number indicated by the time base ID field is the first value.

In a possible design, the first PID synchronization information is used to indicate the PID of the PLRB sent before the first information; or, the first PID synchronization information is used to indicate the PID of the PLRB sent after the first information. In the above design, the first device indicates the PID of a PLRB at a specific location, so that the second device can calibrate the PID of the PLRB, thereby achieving PID count synchronization.

In a possible design, the first information is a PLRB, and the PLRB includes a physical layer content block (PLCB) payload field, and the PLCB payload field carries the first PID synchronization information. In the above embodiments, PHY control messages can be used to carry PID synchronization information, so that PID synchronization can be realized, and erroneous retransmission can be avoided.

In a possible design, the first PID synchronization information is the PID of the first information. The above design carries the PID of the first information in the first information, so that the second device can calibrate the PID count of the first information after receiving the first information.

In a possible design, the PLCB payload field includes a first field, a second field and a third field, the first field indicates that the first information carries non-data information, and the second field indicates that the type of non-data information is PID synchronization information , the third field carries the first PID synchronization information. In the above design, the PHY control information carries the first PID synchronization information, so that the second device indicates that the first information carries non-data information in the first field, and reads in the third field when the second field indicates that the type of non-data information is PID synchronization information. Get the first PID synchronization information.

In a possible design, the third field includes a first subfield, and the first subfield indicates that the first PID synchronization information is a PID synchronization response message. In the above design, the response message and the request message can be distinguished through the first subfield.

In a possible design, before receiving the first information, the method further includes: sending second information, where the second information carries second PID synchronization information, and the second PID synchronization information is used to request the first PID synchronization information. In the above design, the first information may be sent at the request of the second device.

In a possible design, before generating the first information, the method further includes: receiving second information, where the second information carries second PID synchronization information. In the above implementation manner, the PHY control message can be used to carry the second PID synchronization information, so that PID synchronization can be realized, and erroneous retransmission can be avoided.

In a possible design, the PLCB payload field includes a first field, a second field and a third field, the first field indicates that the second information carries non-data information, and the second field indicates that the type of non-data information is PID synchronization information , the third field carries the second PID synchronization information. In the above design, the PHY control information carries the second PID synchronization information, so that the second device indicates that the first information carries non-data information in the first field, and reads in the third field when the second field indicates that the type of non-data information is PID synchronization information. Get the second PID synchronization information.

In a possible design, the third field includes a first subfield, and the first subfield indicates that the second PID synchronization information is a PID synchronization request message. In the above design, the response message and the request message can be distinguished through the first subfield.

In a possible design, the third field further includes a second subfield and at least one of the following subfields: a third subfield and a fourth subfield; where the second subfield is used to carry the PID of the corresponding PLRB , the third subfield is used to indicate the transmission direction for PID synchronization; the fourth subfield is used to indicate the transmission direction of the corresponding PLRB. Through the above design, the accuracy of PID synchronization can be improved.

In a fourth aspect, the embodiment of the present application provides a data transmission method, including: receiving at least two code blocks, the at least two code blocks each carry a physical layer content block PLCB, and at least one of the at least two code blocks One code block carries the control information of PLCB, the control information of PLCB includes the identification information of PLCB and the corresponding indication information, the indication information indicates that PLCB is the Nth transmission, N is a positive integer; determine the control information of at least one PLCB.

In the embodiment of the present application, the PHY code block is determined by the identifier of the PLCB and the retransmission times of the PLCB, so that the second device can accurately indicate the wrong PHY code block, thereby avoiding retransmission errors. Moreover, in this way, the sending and receiving ends do not need to maintain the PID.

In a possible design, the first code block is a PLRB, and the first code block includes a PLCB control field, and the PLCB control field carries PLCB control information. In the foregoing implementation manner, the PLCB control field may be used to carry PLCB control information.

In a possible design, the method further includes: sending a second code block, where the second code block carries retransmission information, and the retransmission information includes: identification information of the first PLCB, indication information of the first PLCB, and receiving status information, The identification information of the first PLCB is the ID of a successfully received PLCB, the indication information of the first PLCB indicates that the first PLCB is the Mth transmission, M is a positive integer, and the receiving status information indicates the receiving status of at least two code blocks. In the above design, by carrying retransmission information in the second code block, the first device can determine a PHY code block according to the retransmission information, so that the PHY code block that transmits an error can be determined according to the PHY code block.

In a possible design, the second code block is a PLRB, the second code block includes a PLCB payload field, and the PLCB payload field carries retransmission information.

In a possible design, the second code block is a PLRB, the second code block includes a PLCB payload field, and the PLCB payload field carries retransmission information. In the foregoing implementation manner, the PLCB payload field may be used to carry retransmission information.

In a possible design, the PLCB payload field includes a first field, a second field and a third field, the first field indicates that the second code block carries non-data information, and the second field indicates that the type of non-data information is a transmission confirmation information, and the third field carries retransmission information. In the above design, the retransmission information is carried by the PHY control information, so that the second device indicates that the second code block carries non-data information in the first field, and reads in the third field when the second field indicates that the type of non-data information is transmission confirmation information Retransmit the message.

In a possible design, the third field also indicates the type of error feedback, the type of error feedback is complete error feedback or partial error feedback, the complete error feedback indicates that the reception status indicates the second PLCB that received all errors, and the partial error feedback indicates that the second PLCB received errors The status only indicates that the second PLCB was partially received incorrectly. Through the above design, the second device can determine the feedback range.

In a fifth aspect, the present application provides a data transmission device, and the device may be a communication device, or a chip or a chipset in the communication device. The apparatus may include a processing unit and a transceiving unit. When the device is a communication device, the processing unit may be a processor, and the transceiver unit may be a transceiver; the device may also include a storage module, which may be a memory; the storage module is used for storing instructions, and the processing unit Execute the instructions stored in the storage module to execute the first aspect or any design in the first aspect, the second aspect or the method in any design in the second aspect. When the device is a chip or chipset in a communication device, the processing unit may be a processor, and the transceiver unit may be an input/output interface, a pin or a circuit, etc.; the processing unit executes the instructions stored in the storage module to Executing the first aspect or any design in the first aspect, the second aspect or any design method in the second aspect. The storage module may be a storage module (for example, register, cache, etc.) within the chip or chipset, or a storage module (for example, read-only memory, random access memory, etc.) located outside the chip or chipset in the communication device. access memory, etc.).

In a sixth aspect, the present application provides a data transmission device, and the device may be a communication device, or a chip or a chipset in the communication device. The apparatus may include a processing unit and a transceiving unit. When the device is a communication device, the processing unit may be a processor, and the transceiver unit may be a transceiver; the device may also include a storage module, which may be a memory; the storage module is used for storing instructions, and the processing unit Execute the instructions stored in the storage module to execute the third aspect or any design in the third aspect, the fourth aspect or the method in any design in the fourth aspect. When the device is a chip or chipset in a communication device, the processing unit may be a processor, and the transceiver unit may be an input/output interface, a pin or a circuit, etc.; the processing unit executes the instructions stored in the storage module to Executing the third aspect or any design in the third aspect, the fourth aspect or any design method in the fourth aspect. The storage module may be a storage module (for example, register, cache, etc.) within the chip or chipset, or a storage module (for example, read-only memory, random access memory, etc.) located outside the chip or chipset in the communication device. access memory, etc.).

In a seventh aspect, the present application provides a data transmission device, including: a processor, and may further include a communication interface and a memory. The communication interface is used to transfer information, and/or messages, and/or data between the device and other devices. The memory is used to store computer-executable instructions, and when the device is running, the processor executes the computer-executable instructions stored in the memory, so that the device executes the first aspect or any design in the first aspect, the second aspect Or the method of any design in the second aspect.

In an eighth aspect, the present application provides a data transmission device, including: a processor, and may further include a communication interface and a memory. The communication interface is used to transfer information, and/or messages, and/or data between the device and other devices. The memory is used to store computer-executable instructions, and when the device is running, the processor executes the computer-executable instructions stored in the memory, so that the device executes any design in the third aspect or the third aspect, the fourth aspect Or the method of any design in the fourth aspect.

In a ninth aspect, an embodiment of the present application provides a data transmission system, including the data transmission device in the fifth aspect above, and the data transmission device in the sixth aspect above.

In a tenth aspect, an embodiment of the present application provides a data transmission system, including the data transmission device in the seventh aspect above, and the data transmission device in the eighth aspect above.

In the eleventh aspect, the embodiment of the present application also provides a computer-readable storage medium, and the computer-readable storage medium stores instructions, which, when run on a computer, cause the computer to perform any of the above-mentioned first to fourth aspects. One aspect, or the method of any design in any aspect.

In the twelfth aspect, the embodiment of the present application also provides a computer program product including instructions, which, when run on a computer, causes the computer to execute any one of the above-mentioned first to fourth aspects, or any one of any of the above-mentioned aspects. A design method.

In the thirteenth aspect, the embodiment of the present application also provides a communication system, the system includes a sending node and a receiving node, wherein the sending node can execute the first aspect or any corresponding method in the first aspect, and the receiving node can Execute the above third aspect or design a corresponding method in any one of the third aspects.

In the fourteenth aspect, the embodiment of the present application also provides a communication system, the system includes a sending node and a receiving node, wherein the sending node can execute the second aspect or any corresponding method in the second aspect, and the receiving node can Execute the fourth aspect above or design a corresponding method according to any one of the fourth aspects.

In the fifteenth aspect, the embodiment of the present application provides a chip, the chip includes at least one processor and a communication interface, the processor is coupled with the memory, and is used to read the computer program stored in the memory to execute the above first to fourth aspects Any aspect in any aspect, or the method of any design in any aspect.

It should be noted that "coupling" in the embodiments of the present application means that two components are directly or indirectly combined with each other.

In a sixteenth aspect, the embodiment of the present application provides a vehicle, the vehicle includes a first device and/or a second device, the first device is used to execute the method designed in the first aspect or any one of the first aspects, and the second The device is used to execute the third aspect or the method designed in any one of the third aspects.

In the seventeenth aspect, the embodiment of the present application provides a vehicle, the vehicle includes a first device and/or a second device, the first device is used to execute the method of any one of the aforementioned second aspect or the second aspect, and the second The device is used to execute the fourth aspect or the method designed in any one of the fourth aspects.

Description of drawings

FIG. 1 is a schematic diagram of data transmission provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of a PLRB format provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of synchronous symbol transmission provided by an embodiment of the present application;

FIG. 4 is a schematic flow diagram of a data transmission method provided by an embodiment of the present application;

FIG. 5 is a schematic flow diagram of a data transmission method provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of data transmission provided by an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a data transmission device provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a data transmission device provided by an embodiment of the present application.

Detailed ways

The terms "comprising" and "having" in the description and claims of the embodiments of the present application and the accompanying drawings, as well as any variations thereof, are intended to cover non-exclusive inclusion, for example, processes and methods that include a series of steps or units The systems, products or devices are not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to the process, method, product or device.

The embodiment of the present application can be applied to wired transmission, for example, can be applied to wired point-to-point high-speed transmission, such as image and control transmission between a camera and an autopilot platform multi-domain controller (multi domain controller, MDC), vehicle camera or cockpit domain controller ( cockpit domain controller or control domain cockpit, CDC) and other on-vehicle equipment and large screen image transmission, etc.

For example, the communication device involved in the embodiment of the present application may be a device capable of sending information (such as data frame, control information, etc.) An image processing device, or an image display device such as a large screen. For another example, the communication device involved in the embodiment of the present application may also be other transmission equipment than the vehicle-mounted device.

In the embodiments of the present application, "at least one" means one or more, and "multiple" means two or more. "And/or" describes the association relationship of associated objects, indicating that there can be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist at the same time, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the contextual objects are an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one item (piece) of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or, a and b and c, wherein, a, b, c can be single or multiple.

And, unless otherwise stated, the ordinal numerals such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects, and are not used to limit the size, content, order, and timing of multiple objects , priority or importance, etc. For example, the first data packet and the second data packet are just names given for convenience of description, and these two data packets may be the same data packet, or may be different data packets.

The technical features involved in the embodiments of the present application are introduced below.

In high-speed wired transmission, especially in some vehicle-mounted SerDes transmissions, due to high BER requirements, in addition to PHY layer using error correction and error detection coding (such as Reed-Solomon forward error correction (RS-FEC), there will also be Consider improving the reliability of the transmission link through retransmission.

In SerDes transmission, usually two-way transmission is carried out simultaneously. For the convenience of description, a transmission direction is selected below, and the originating end of the transmission direction is the first device, and the receiving end is the second device.

The first device sends PHY code blocks sequentially, one PHY code block is one PLRB, and one PHY code block bears one PLCB. When the transmission of the PHY code block fails, the second device sends an ACK to the first device, and indicates the failed PHY code block through the PID information carried in the ACK. The first device encapsulates the PLCB carried by the failed PHY code block into a new PHY code block and sends it to the second device to complete the retransmission. For example, when the transmission of PHY code block 2 fails, the second device sends an ACK to the first device, and indicates that the reception of PHY code block 2 fails through the PID information carried in the ACK. The first device encapsulates the PLCB 2 carried by the PHY code block 2 into the PHY code block 5 and sends it to the second device to complete the retransmission, as shown in FIG. 1 .

In SerDes transmission, using a clock and data recovery (CDR) technology, the first device and the second device implement PHY clock synchronization during link establishment. The first device and the second device count the PHY code blocks according to the PHY clock, so that the PID of the PHY code block can be determined according to the count of the PHY code blocks.

In an interference scenario, long-lasting interference may cause the PHY clock of the second device to lose synchronization. However, the out-of-synchronization of the PHY clock will lead to inaccurate counting of the PHY code blocks performed by the second device. Since the second device uses the PID in the ACK to indicate the erroneously transmitted PHY code block, the first device is triggered to retransmit. Therefore, the out-of-synchronization of the PHY clock will cause an error in the retransmission of the PHY code block.

Based on this, the embodiments of the present application provide a data transmission method and device, which are used to solve the problem of retransmission errors of PHY code blocks caused by out-of-synchronization of PHY clocks. Among them, the method and the device are based on the same technical conception. Since the principles of the method and the equipment to solve the problem are similar, the implementation of the device and the method can be referred to each other, and the repetition will not be repeated. The embodiments of the present application provide an information transmission method and device, which can be applied to an in-vehicle network, especially an in-vehicle network of a smart car, and can also be applied to other wired transmission devices.

Hereinafter, the PHY code block in the embodiment of the present application is explained, so as to facilitate the understanding of those skilled in the art.

1) PHY code block

One PHY code block is one PLRB, and the PLRB includes the PLRB payload field and also includes the PLRB redundancy field. Wherein, the PLRB payload field includes a PLCB control field and a PLCB payload field, and may further include a cyclic redundancy check (cyclic redundancy check, CRC) field. Wherein, the PLCB control field may include a PLCB ID for uniquely identifying the PLCB.

The PLCB payload field may include one or more information blocks, and the information blocks may adopt 64/66 line encoding, 64/65 line encoding, or other encoding methods, which are not specifically limited here. Wherein, an information block includes an indicator bit and a payload field, wherein the indicator bit can indicate the type of information carried in the payload field, and the information type can be divided into data information and non-data information.

For example, taking a 2-bit indication bit as an example, the content indicated by the indication bit may be as shown in Table 1.

Table 1

indicator bit meaning 00 The payload field carries the middle fragment of the data frame 01 The payload field carries the first fragment of the data frame 10 The payload field carries the last fragment of the data frame 11 The payload field carries non-data information, such as sub-control bits, PHY control information, etc.

Taking a 1-bit indicator bit as an example, the content indicated by the indicator bit may be as shown in Table 2.

Table 2

indicator bit meaning 0 The payload field carries the data frame 1 The payload field carries non-data information, such as sub-control bits, PHY control information, etc.

If the indication bit indicates that the payload field carries non-data information, the payload field may include a sub-indication field and a content field, the sub-indication bit may indicate the type of non-data information, and the content field may carry non-data information. For example, at present, the content indicated by the sub-indication bits may be as shown in Table 3.

table 3

sub-indicator Types of non-data information 0x1e PHY Padding 0x2d PHY retransmission (ACK) 0x3c link reestablishment 0x4b interval training 0x5a sleep other reserve

The ACK in Figure 1 can be one of the non-data information carried by the PHY code block, sent by the second device to the first device, and similar to the confirmation message of the PHY code block sent by the second device to the first device, then It is carried by the PHY code block sent by the first device to the second device.

Exemplarily, the PLRB may be as shown in FIG. 2 .

It should be understood that the names, values, and corresponding relationships of indicated contents of the above fields are only exemplary descriptions.

2) Synchronization symbols

In order to achieve fast link recovery and periodically calibrate the pixel clocks at both ends of the transceiver, the SerDes transmission scheme will periodically send synchronization symbols, as shown in Figure 3. The sync symbol carries delimiter, random scrambling code and pixel clock information. Among them, the starting position of the PHY can be aligned by calibrating the pixel clock.

Exemplarily, the fields included in the synchronization symbol may be as shown in Table 4.

Table 4

It should be understood that all the fields described in Table 4 above may be included in the synchronization symbol, or only part of the fields may be included in the synchronization symbol. In addition, the synchronization symbol may also include other fields not shown in Table 4, which will not be described one by one here.

Embodiments of the present application will be described in detail below in conjunction with the accompanying drawings.

Embodiment one:

This application provides a data transmission method. As shown in Figure 4, the method includes:

S401. The first device generates first information, where the first information includes first PID synchronization information, and the first PID synchronization information is used for PID synchronization.

In an exemplary description, PID synchronization may include PID count synchronization between the first device and the second device.

S402. The first device sends the first information. Correspondingly, the second device receives the first information.

S403. The second device performs PID count synchronization according to the first PID synchronization information.

Wherein, the first device may be a data sending end, and the second device may be a data receiving end. Alternatively, the first device may also be a data receiving end, and the second device may be a data sending end. Wherein, the "data" can be understood as business data, such as image data, video data, and the like.

It can be understood that the data sender and the data receiver are only a logical distinction. In specific scenarios, the roles of the data sender and the data receiver can also be interchanged. For example, when A sends data to B, A acts as the data At the sending end, B acts as the data receiving end. When B sends data to A, B acts as the data sending end, and A acts as the data receiving end.

Reed-Solomon forward error correction (RS-FEC) can be used for both the PHY code blocks sent from the data sending end to the data receiving end and the PHY code blocks sent from the data receiving end to the data sending end. The length and base of the Reed-Solomon (reed-solomon, RS) encoding of the PHY code block sent by the data sending end to the data receiving end and the PHY code block sent by the data receiving end to the data sending end can be different, wherein the base can be understood as The unit length of symbols included in the PHY code block. For example, the PHY code block sent from the data sending end to the data receiving end can use RS-FEC (340, 312, 10), and the PHY code block sent from the data receiving end to the data sending end can use RS-FEC (76, 72, 8) , wherein, RS-FEC (340, 312, 10) can refer to that the PHY code block includes 340 symbols, wherein the number of symbols carrying valid data is 312, and the unit length of symbols is 10 bits; RS-FEC (76, 72, 8) may mean that the PHY code block includes 76 symbols, wherein the number of symbols carrying valid data is 72, and the unit length of a symbol is 8 bits. For the convenience of description, the PHY code block sent from the data sending end to the data receiving end is called forward PHY code block, and the sending from the data sending end to the data receiving end is called forward transmission. The PHY code block sent from the data receiving end to the data sending end is called a reverse PHY code block, and the sending from the data receiving end to the data sending end is called reverse transmission.

In the embodiment of the present application, the first device sends PID synchronization information to the second device, so that the second device can calibrate the PID count according to the PID synchronization information, so that the data receiving end uses the PHY code block indicated by the PID information and the data sending end according to the PID The PHY code blocks determined by the information are consistent, thereby avoiding erroneous retransmission.

In a possible implementation manner, the first information may be a synchronization symbol. The first PID synchronization information may be carried in the time base field of the synchronization symbol.

Exemplarily, taking the synchronization symbol including the fields described in Table 4 as an example, the first information may be as shown in Table 5.

table 5

It should be understood that all the fields described in Table 5 above may be included in the first information, or only part of the fields may be included in the first information. In addition, the first information may also include other fields not shown in Table 5, which will not be described one by one here.

Optionally, the time base number indicated by the time base ID field in the synchronization signal is a first value, and the first value indicates that the time base field carries the first PID synchronization information. For example, the time base number indicated by the time base ID field in the synchronization signal is 0000, and the time base number of 0000 indicates that the time base field carries the first PID synchronization information.

In the above method, the first value is used as the synchronization symbol to carry the identification of the PID synchronization information, so that the second device can read the PID synchronization information in the time base field when the time base number indicated by the time base ID field is the first value.

Exemplarily, taking the synchronization symbol including the fields described in Table 4 as an example, the first information may be as shown in Table 6.

Table 6

Exemplarily, the first PID synchronization information may be used to indicate the PID of the PLRB sent before the first information. For example, the first PID synchronization information may be used to indicate the PID of the previous PLRB of the first information. For another example, the first PID synchronization information may be used to indicate the PID of the penultimate PLRB sent before the first information, and so on.

Alternatively, the first PID synchronization information may also be used to indicate the PID of the PLRB sent after the first information. For example, the first PID synchronization information may be used to indicate the PID of the next PLRB of the first information. For another example, the first PID synchronization information may be used to indicate the PID of the second PLRB sent after the first information, and so on.

In an implementation manner, the sending frequency of the synchronization symbol carrying the PID synchronization information may be pre-configured, or may be determined through negotiation during a link establishment process between the first device and the second device. Of course, it may also be determined in other ways, which are not specifically limited here.

In the above embodiment, by multiplexing the synchronization symbols sent periodically, the data receiving end can complete the PID count synchronization while restoring the PHY code block delimitation and scrambling code synchronization, so as to avoid error retransmission after the link is restored. .

In another possible implementation manner, the first information may also be PLRB. The first synchronization information may be carried in the PLCB payload field of the PLRB.

In an exemplary description, the first PID synchronization information may be the PID of the first information.

As an example, the PLRB can carry the first synchronization information in the following form: the PLCB payload field includes a first field, a second field and a third field, the first field indicates that the first information carries non-data information, and the second field indicates that non-data information is carried in the second field. The type of data information is PID synchronization information, and the third field carries the first PID synchronization information.

Wherein, the first field may be the indicator bit shown in FIG. 2 , for details, please refer to the relevant description of the above indicator bit, which will not be repeated here.

The second field may be the sub-indicator bit shown in FIG. 2, wherein, in the embodiment of the present application, the second field may indicate that the non-data information is PID synchronization information through a value, for example, 0x69 may be used to indicate that the non-data information is PID Synchronization information. Exemplarily, the content indicated by the second field may be as shown in Table 7.

Table 7

second field Types of non-data information 0x1e PHY Padding

0x2d PHY retransmission (ACK) 0x3c link reestablishment 0x4b interval training 0x5a sleep 0x69 PID synchronization information other reserve

It should be understood that the indication content shown in Table 7 above, and the corresponding relationship between the value and the indication content, etc. are only exemplary descriptions.

The third field may be the content field shown in FIG. 2 , and in the embodiment of the present application, the third field may carry PID synchronization information.

Optionally, the first information may also include a CRC field. The CRC field can be used to ensure that in the case of a PLRB code block transmission error, the correctness of the PHY retransmission message can be confirmed through the CRC check.

The format of the third field, which can also be interpreted as the format of PID information when carrying PID synchronization information, will be described below.

The third field may include at least one of the following subfields: a first subfield, a second subfield, a third subfield, and a fourth subfield.

Wherein, the first subfield may be used to indicate whether the PID synchronization information of the PLRB is a response message or a request message. The first subfield in the first information may indicate that the first PID synchronization information is a response message.

The second subfield may be used to carry the PID of the corresponding PLRB, for example, the second subfield in the first information may carry the PID of the first information.

The third subfield may be used to indicate the transmission direction for PID synchronization.

The fourth subfield is used to indicate the transmission direction of the corresponding PLRB. For example, the fourth subfield in the first information may indicate the transmission direction of the first information.

For ease of understanding, the third field carrying PID synchronization information is illustrated below, as shown in Table 8.

Table 8

Among them, the PID synchronization of forward transmission can be understood as that the data sending end sends the PID synchronization information for PID synchronization to the data receiving end, that is, sending the PID synchronization response message, and the data receiving end receives the PID synchronization information. Perform PID count synchronization.

The PID synchronization of reverse transmission can be understood as that the data receiving end sends the PID synchronization information for PID synchronization to the data sending end, that is, sending the PID synchronization response message, and the data sending end performs PID synchronization after receiving the PID synchronization information. Counting is synchronized.

It should be understood that Table 8 is only an exemplary description, and does not specifically limit the number of bits of each subfield in the third field, the corresponding relationship between values and indication content, and the like. In addition, the third field may also include other subfields, and the subfields included in the third field are not specifically limited here.

In some embodiments, the first device may actively send the first information to the second device. For example, the first device may periodically send the first information to the second device, or may send the first information to the second device triggered by an event. Wherein, when the first device periodically sends the first information, the sending period of the first information may be pre-configured, or may be negotiated and determined during the link establishment process between the first device and the second device.

In other embodiments, the first device may send the first information at the request of the second device. For example, before the first device sends the first information, the second device sends second information to the first device, the second information carries second PID synchronization information, and the second PID synchronization information is used to request the first PID synchronization information.

Wherein, the second information may be PLRB. The format of the second information is similar to that of the first information, except that the third field of the first information carries the first PID synchronization information for PID synchronization and the PLRB information of the first information, for example, the PID of the first information , the transmission direction of the first information, etc., the third field of the second information carries the second PID synchronization information used to request the first PID synchronization information and the PLRB information of the second information, for example, the PID of the second information, the 2. The transmission direction of information, etc. Take the format of the third field shown in Table 8 as an example to illustrate the difference between the first information and the second information. The value of the first subfield of the first information is 10, indicating a response message. The first subfield of the second information A value of 00 indicates a request message. The third subfield of the first information indicates the transmission direction of the first information, and the third subfield of the second information indicates the transmission direction of the second information. The fourth subfield of the first information indicates the PID of the first information, and the fourth subfield of the second information indicates the PID of the second information.

Where the second information is the same as the first information, reference may be made to relevant descriptions of the above-mentioned first information, and details are not repeated here.

In the above embodiments, PHY control messages can be used to carry PID synchronization information, so that PID synchronization can be realized, and erroneous retransmission can be avoided.

Embodiment two:

This application provides a data transmission method. As shown in Figure 5, the method includes:

S501. The first device generates at least two code blocks.

Wherein, the at least two code blocks respectively carry a PLCB, and at least one first code block in the at least two code blocks carries the control information of the PLCB, the control information of the PLCB includes the identification information of the PLCB and the corresponding indication information, and the indication information indicates PLCB is the Nth transmission, and N is a positive integer.

S502. The first device sends at least two code blocks. Correspondingly, the second device receives at least two code blocks.

S503. The second device saves the control information of the PLCB carried by the at least one first code block.

Wherein, the first device may be a data sending end, and the second device may be a data receiving end. Alternatively, the first device may also be a data receiving end, and the second device may be a data sending end. Wherein, the "data" can be understood as business data, such as image data, video data, and the like.

It can be understood that the data sender and the data receiver are only a logical distinction. In specific scenarios, the roles of the data sender and the data receiver can also be interchanged. For example, when A sends data to B, A acts as the data At the sending end, B acts as the data receiving end. When B sends data to A, B acts as the data sending end, and A acts as the data receiving end.

In this embodiment of the present application, the PHY code block is determined by the PLCB identifier and the number of times the PLCB is retransmitted, so that the second device can accurately indicate the PHY code block that was transmitted incorrectly, thereby avoiding retransmission errors. Moreover, in this way, the sending and receiving ends do not need to maintain the PID.

In a possible implementation manner, the first code block may be a PLRB. The PLCB control information may carry the PLCB control field of the PLRB.

In an implementation manner, the PLCB control field may include a PLCB ID field and a retransmission indication field, where the retransmission indication field may indicate that the PLCB is the Nth retransmission. It should be understood that the "PLCB ID field" and "retransmission indication field" are only exemplary names, and can also be named as other fields, as long as the field has the "retransmission indication field" or "PLCB ID field" in the embodiment of this application The feature of , can be regarded as the "retransmission indication field" or "PLCB ID field" in the embodiment of the present application.

Exemplarily, the PLCB control field may be as shown in Table 9.

Table 9

It should be understood that Table 9 is only an exemplary description, and the filling indication field may be an optional field. In addition, the PLCB control field may also include other fields not shown in Table 9, and the subfields included in the PLCB control field are not included here. Make specific restrictions.

In a possible implementation manner, the second device may send a second code block to the first device, where the second code block carries retransmission information, and the retransmission information includes: identification information of the first PLCB, indication information of the first PLCB, Receiving status information, the identification information of the first PLCB is the ID of a successfully received PLCB, the indication information of the first PLCB indicates that the first PLCB is the Mth transmission, M is a positive integer, and the receiving status information indicates at least two code blocks. Receive status. The first device may determine, according to the retransmission information, a PLCB that fails to be transmitted among PLCBs carried by at least two code blocks.

Optionally, the identifier of the first PLCB may be the identifier of the last PLCB successfully received, or the identifier of the first PLCB is the identifier of a PLCB successfully received within the feedback range.

In an exemplary description, the second code block may also be a PLRB. The retransmission information may be carried in the PLCB payload field of the PLRB.

As an example, the PLRB can carry retransmission information in the following form: the PLCB payload field includes a first field, a second field and a third field, the first field indicates that the first information carries non-data information, and the second field indicates that non-data information The type of information is transmission confirmation information, and the third field carries retransmission information.

Wherein, the first field may be the indicator bit shown in FIG. 2 , for details, please refer to the relevant description of the above indicator bit, which will not be repeated here.

The second field may be the sub-indicator bit shown in FIG. 2. For details, please refer to the related description about the sub-indicator bit in the explanation of the PHY code block, or refer to the related description about the sub-indicator bit in Embodiment 1. I won't repeat it here.

The third field may be the content field shown in FIG. 2 , and in the embodiment of the present application, the third field may carry retransmission information.

The format of the third field when carrying the retransmission information is described below, which can also be understood as the format of the retransmission information.

The third field may include at least one of the following subfields: a first subfield, a second subfield, a third subfield, and a fourth subfield.

Among them, the first subfield can be used to indicate the error feedback type, the error feedback type is complete error feedback or partial error feedback, the complete error feedback indicates that the receiving status indicates all the second PLCBs receiving errors, and the partial error feedback indicates that the receiving status only indicates The second PLCB was partially received incorrectly.

The second subfield may carry the identifier of the first PLCB.

The third subfield may carry indication information of the first PLCB.

The fourth subfield may carry reception status information.

For ease of understanding, the third field carrying retransmission information is described below as an example, as shown in Table 10.

Table 10

It should be understood that Table 10 is only an exemplary description, and does not specifically limit the number of bits of each subfield in the third field, the corresponding relationship between values and indication content, and the like. In addition, the third field may also include other subfields, and the subfields included in the third field are not specifically limited here.

In order to facilitate the understanding of the solution described in the second embodiment, the following description will be made in conjunction with specific examples.

As shown in Figure 6, the first device sends PHY code blocks 1 to 3 to the second device in sequence, wherein, PHY code block 1 carries PLCB 1 and indicates that PLCB 1 is the initial transmission, and PHY code block 2 carries PLCB 2 and indicates PLCB 2 For initial transmission, PHY code block 3 carries PLCB 3 and indicates PLCB 3 is initial transmission.

After receiving PHY code blocks 1-3, the second device finds that the transmission of PHY code block 2 is wrong, and the second device can send ACK 1 to the first device, wherein the ACK 1 carries the identifier of PLCB 3 and indicates that PLCB 3 is the initial transmission, Receive status information (in order: PHY code block 2 is wrong, PHY code block 1 is correct).

After receiving the ACK 1, the first device can instruct PLCB to determine the PHY code block 3 for the initial transmission according to the identifier of PLCB1, and then use PHY code block 3 as the last PHY code block, and count 2 code blocks forward, that is, the code Blocks 1 to 3, according to the receiving status information, it can be determined that the transmission of PHY code block 2 is wrong, and the transmission of PHY code block 1 is correct.

The first device retransmits the PLCB 2 carried by the PHY code block 2 through the PHY code block 5, and instructs the PLCB 2 to retransmit for the first time.

After receiving the PHY code blocks 4-5, the second device finds that the transmission of the PHY code block 4 is wrong, and the transmission of the PHY code block 5 is correct. The second device may send ACK 2 to the first device, wherein the ACK 2 carries the identifier of PLCB 2 and indicates that PLCB 2 is retransmitting and receiving status information for the first time (in sequence: PHY code block 4 error, PHY code block 3 correct, PHY code block 2 is wrong, PHY code block 1 is correct).

After receiving the ACK 2, the first device can instruct PLCB 2 to determine PHY code block 5 for the first retransmission according to the identifier of PLCB 2, and then use PHY code block 5 as the last PHY code block, and count 4 forwards Code blocks, that is, PHY code blocks 1 to 5, according to the receiving status information, it can be determined that the receiving status of PHY code blocks 1 to 5 is correct; mistake.

The first device retransmits the PLCB 3 carried in the PHY code block 4 .

It should be noted that the identifier of the first PLCB carried by the second subfield in the ACK may be the PLCB ID carried by the last successfully received PHY code block within the feedback range, or the first successfully received PHY code block within the feedback range The carried PLCB ID.

In one implementation, the identifier of the first PLCB may be implicitly indicated as the PLCB ID carried by the last successfully received PHY code block within the feedback range, or the ID carried by the first successfully received PHY code block within the feedback range. For example, the protocol may stipulate that the identifier of the first PLCB is the PLCB ID carried by the last successfully received PHY code block within the feedback range.

In another implementation, it is also possible to indicate by displaying an indication that the identifier of the first PLCB is the PLCB ID carried by the last successfully received PHY code block within the feedback range, or the first successfully received PHY code block within the feedback range The carried PLCB ID is indicated by, for example, an unshown field in the ACK. The receiving state may use the successfully received PHY code block determined by the second subfield and the third subfield as an anchor point to indicate the receiving state of other PHY code blocks. Specifically, it may be indicated by way of bit mapping, or other indication ways, which are not specifically limited in this embodiment of the present application.

Based on the same technical concept as that of the method embodiment, the embodiment of the present application provides a data transmission device. The structure of the device may be as shown in FIG. 7 , including a processing unit 701 and a transceiver unit 702 .

In one implementation, the data transmission device can specifically be used to implement the method performed by the first device in the embodiment of FIG. 4 , and the device can be the first device itself, or a chip or chipset or chip in the first device Part of the method used to perform the function of the associated method. Wherein, the processing unit 701 is configured to generate first information, the first information includes first PID synchronization information, and the first PID synchronization information is used for PID synchronization; the transceiver unit 702 is configured to send the first information.

Exemplarily, the PID synchronization includes PID count synchronization between the first device and the second device.

Exemplarily, the first information is a synchronization symbol, and the synchronization symbol includes a time base field, and the time base field carries the first PID synchronization information.

Exemplarily, the synchronization symbol further includes a time base identification field for indicating a time base number, where the time base number indicated by the time base identification field is a first value, and the first value indicates that the time base field carries the first PID synchronization information.

Exemplarily, the first PID synchronization information is used to indicate the PID of the PLRB sent before the first information; or, the first PID synchronization information is used to indicate the PID of the PLRB sent after the first information.

Exemplarily, the first information is PLRB, and the PLRB includes a PLCB payload field, and the PLCB payload field carries the first PID synchronization information.

Exemplarily, the first PID synchronization information is the PID of the first information.

Exemplarily, the PLCB payload field includes a first field, a second field and a third field, the first field indicates that the first information carries non-data information, the second field indicates that the type of non-data information is PID synchronization information, and the third field Carry the first PID synchronization information.

Exemplarily, the third field includes a first subfield, and the first subfield indicates that the first PID synchronization information is a PID synchronization response message.

Optionally, the transceiver unit 702 is further configured to: before the processing unit 701 generates the first information, receive second information, the second information carries second PID synchronization information, and the second PID synchronization information is used to request the first PID synchronization information .

Exemplarily, the second information is PLRB, and the PLRB includes a PLCB payload field; the PLCB payload field carries second PID synchronization information.

Exemplarily, the PLCB payload field includes a first field, a second field and a third field, the first field indicates that the second information carries non-data information, the second field indicates that the type of non-data information is PID synchronization information, and the third field Carry second PID synchronization information.

Exemplarily, the third field includes a first subfield, and the first subfield indicates that the second PID synchronization information is a PID synchronization request message.

Exemplarily, the third field further includes a second subfield and at least one of the following subfields: a third subfield and a fourth subfield; wherein, the second subfield is used to carry the PID of the corresponding PLRB, and the third subfield The field is used to indicate the transmission direction for PID synchronization; the fourth subfield is used to indicate the transmission direction of the corresponding PLRB.

In another implementation manner, the data transmission device can be specifically used to implement the method performed by the first device in the embodiment of FIG. 5 , and the device can be the first device itself, or a chip or chipset or The part of a chip that performs the function of the associated method. Wherein, the processing unit 701 is configured to generate at least two code blocks, the at least two code blocks respectively carry a PLCB, and at least one first code block in the at least two code blocks carries PLCB control information, and the PLCB control information includes The identification information of the PLCB and the corresponding indication information, the indication information indicates that the PLCB is the Nth transmission, and N is a positive integer; the transceiver unit 702 is configured to send at least two code blocks.

Exemplarily, the first code block is a PLRB, and the first code block includes a PLCB control field, and the PLCB control field carries PLCB control information.

Optionally, the transceiver unit 702 is further configured to: receive a second code block, the second code block carries retransmission information, and the retransmission information includes: identification information of the first PLCB, indication information of the first PLCB, and receiving status information, The identification information of the first PLCB is the ID of a PLCB successfully received, the indication information of the first PLCB indicates that the first PLCB is the Mth transmission, M is a positive integer, and the receiving status information indicates the receiving status of at least two code blocks; processing The unit 701 is further configured to: determine, according to the retransmission information, a PLCB that fails to be transmitted among PLCBs carried by at least two code blocks.

Exemplarily, the second code block is a PLRB, the second code block includes a PLCB payload field, and the PLCB payload field carries retransmission information.

Exemplarily, the PLCB payload field includes a first field, a second field and a third field, the first field indicates that the second code block carries non-data information, the second field indicates that the type of non-data information is transmission confirmation information, and the third field carries retransmission information.

Exemplarily, the third field also indicates the error feedback type, the error feedback type is complete error feedback or partial error feedback, the complete error feedback indicates that the receiving status indicates all the second PLCBs receiving errors, and the partial error feedback indicates that the receiving status only indicates Partial reception of wrong second PLCB.

In one implementation, the data transmission device can specifically be used to implement the method performed by the second device in the embodiment of FIG. 4 , and the device can be the second device itself, or a chip or chipset or chip in the second device Part of the method used to perform the function of the associated method. Wherein, the transceiver unit 702 is configured to receive first information, the first information includes first PID synchronization information, and the first PID synchronization information is used for PID synchronization; the processing unit 701 is used for performing PID synchronization according to the first PID synchronization information.

Exemplarily, the PID synchronization includes PID count synchronization between the first device and the second device.

Exemplarily, the first information is a synchronization symbol, and the synchronization symbol includes a time base field, and the time base field carries the first PID synchronization information.

Exemplarily, the synchronization symbol further includes a time base identification field for indicating a time base number, where the time base number indicated by the time base identification field is a first value, and the first value indicates that the time base field carries the first PID synchronization information.

Exemplarily, the first PID synchronization information is used to indicate the PID of the PLRB sent before the first information; or, the first PID synchronization information is used to indicate the PID of the PLRB sent after the first information.

Exemplarily, the first information is PLRB, and the PLRB includes a PLCB payload field, and the PLCB payload field carries the first PID synchronization information.

Exemplarily, the first PID synchronization information is the PID of the first information.

Exemplarily, the PLCB payload field includes a first field, a second field and a third field, the first field indicates that the first information carries non-data information, the second field indicates that the type of non-data information is PID synchronization information, and the third field Carry the first PID synchronization information.

Exemplarily, the third field includes a first subfield, and the first subfield indicates that the first PID synchronization information is a PID synchronization response message.

Optionally, the transceiver unit 702 is further configured to: before receiving the first information, send second information, the second information carries second PID synchronization information, and the second PID synchronization information is used to request the first PID synchronization information.

Exemplarily, the second information is PLRB, and the PLRB includes a PLCB payload field; the PLCB payload field carries second PID synchronization information.

Exemplarily, the PLCB payload field includes a first field, a second field and a third field, the first field indicates that the second information carries non-data information, the second field indicates that the type of non-data information is PID synchronization information, and the third field Carry second PID synchronization information.

Exemplarily, the third field includes a first subfield, and the first subfield indicates that the second PID synchronization information is a PID synchronization request message.

Exemplarily, the third field includes the second subfield and at least one of the following subfields: the third subfield and the fourth subfield; wherein, the second subfield is used to carry the PID of the corresponding PLRB, and the third subfield It is used to indicate the transmission direction for PID synchronization; the fourth subfield is used to indicate the transmission direction of the corresponding PLRB.

In another implementation manner, the data transmission device can specifically be used to implement the method performed by the second device in the embodiment of FIG. 5 , and the device can be the second device itself, or a chip or chipset or The part of a chip that performs the function of the associated method. Wherein, the transceiver unit 702 is configured to receive at least two code blocks, at least two code blocks each carry a PLCB, and at least one first code block in the at least two code blocks carries PLCB control information, and the PLCB control information includes The identification information of the PLCB and the corresponding indication information, the indication information indicates that the PLCB is the Nth transmission, and N is a positive integer; the processing unit 701 is configured to determine the control information of at least one PLCB.

Exemplarily, the first code block is a PLRB, and the first code block includes a PLCB control field, and the PLCB control field carries PLCB control information.

Optionally, the transceiver unit 702 is further configured to: send a second code block, the second code block carries retransmission information, and the retransmission information includes: identification information of the first PLCB, indication information of the first PLCB, and receiving status information, The identification information of the first PLCB is the ID of a successfully received PLCB, the indication information of the first PLCB indicates that the first PLCB is the Mth transmission, M is a positive integer, and the receiving status information indicates the receiving status of at least two code blocks.

Exemplarily, the second code block is a PLRB, the second code block includes a PLCB payload field, and the PLCB payload field carries retransmission information.

Exemplarily, the PLCB payload field includes a first field, a second field and a third field, the first field indicates that the second code block carries non-data information, the second field indicates that the type of non-data information is transmission confirmation information, and the third field carries retransmission information.

Exemplarily, the third field also indicates the error feedback type, the error feedback type is complete error feedback or partial error feedback, the complete error feedback indicates that the receiving status indicates all the second PLCBs receiving errors, and the partial error feedback indicates that the receiving status only indicates Partial reception of wrong second PLCB.

The division of modules in the embodiments of the present application is schematic, and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present application can be integrated into a processing In the controller, it can also be physically present separately, or two or more modules can be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It can be understood that, for the function or implementation of each module in the embodiment of the present application, further reference may be made to the relevant description of the method embodiment.

In a possible manner, the data transmission apparatus may be as shown in FIG. 8 , and the apparatus may be a chip in the first device or the second device. The device may include a processor 801 , a communication interface 802 and a memory 803 . Wherein, the processing unit 701 may be the processor 801 . The transceiver unit 702 is a communication interface 802 .

The processor 801 may be a central processing unit (Central Processing Unit, CPU), or a digital processing unit or the like. The communication interface 802 may be a transceiver, or an interface circuit such as a transceiver circuit, or a transceiver chip or the like. The device also includes: a memory 803 for storing programs executed by the processor 801 . The memory 803 can be a non-volatile memory, such as a hard disk (hard disk drive, HDD) or a solid-state drive (solid-state drive, SSD), etc., and can also be a volatile memory (volatile memory), such as a random access memory (random -access memory, RAM). The memory 803 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

The processor 801 is configured to execute the program codes stored in the memory 803, and is specifically configured to execute the above-mentioned actions of the processing unit 701, which will not be repeated in this application. The communication interface 802 is specifically configured to execute the above-mentioned actions of the transceiver unit 702, which will not be repeated in this application.

In this embodiment of the present application, a specific connection medium among the communication interface 802, the processor 801, and the memory 803 is not limited. In the embodiment of the present application, in FIG. 8, the memory 803, the processor 801, and the communication interface 802 are connected through the bus 804. The bus is represented by a thick line in FIG. 8, and the connection mode between other components is only for schematic illustration. , is not limited. The bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 8 , but it does not mean that there is only one bus or one type of bus.

The embodiment of the present application also provides a communication system, including a communication device for realizing the function of the sending node in the embodiment of FIG. 4 to FIG. 5 and a communication device for realizing the function of the receiving node in the embodiment of FIG. 4 to FIG. 5 .

The embodiment of the present application also provides a computer-readable storage medium for storing computer software instructions required to execute the above-mentioned processor, which includes a program required to execute the above-mentioned processor.

An embodiment of the present application also provides a vehicle, where the vehicle includes a first device and/or a second device, and the first device and the second device are used to individually or jointly implement the data transmission method in FIG. 4 or FIG. 5 . Exemplarily, the first device and the second device may be the communication apparatus shown in FIG. 7 .

The embodiment of the present application also provides a chip, the chip includes at least one processor and a communication interface, the processor is coupled with the memory, and is used to read the computer program stored in the memory to execute the embodiment described in Figure 4 or Figure 5 Function.

The embodiment of the present application also provides a chip, including a communication interface and at least one processor, and the processor operates to execute the functions in the embodiment described in Fig. 4 or Fig. 5 .

Those skilled in the art should understand that the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the present application. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

Apparently, those skilled in the art can make various changes and modifications to this application without departing from the protection scope of this application. In this way, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Claims (87)

A data transmission method, characterized in that the method comprises: Generate first information, where the first information includes first physical layer Reed-Solomon error correction coding block identification PID synchronization information, and the first PID synchronization information is used for PID synchronization; Send the first information. The method of claim 1, wherein the PID synchronization comprises PID count synchronization between the first device and the second device. The method according to claim 2, wherein the first information is a synchronization symbol, and the synchronization symbol includes a time base field, and the time base field carries the first PID synchronization information. The method according to claim 3, wherein the synchronization symbol further includes a time base identification field for indicating a time base number, wherein the time base number indicated by the time base identification field is a first value, and the The first value indicates that the time base field carries the first PID synchronization information. The method according to claim 3 or 4, wherein the first PID synchronization information is used to indicate the PID of the physical layer Reed Solomon error correction coding block PLRB sent before the first information; Alternatively, the first PID synchronization information is used to indicate the PID of the PLRB sent after the first information. The method according to claim 2, wherein the first information is a PLRB, and the PLRB includes a physical layer content block PLCB payload field, and the PLCB payload field carries the first PID synchronization information. The method according to claim 6, wherein the first PID synchronization information is the PID of the first information. The method according to claim 6 or 7, wherein the PLCB payload field includes a first field, a second field and a third field, and the first field indicates that the first information carries non-data information, The second field indicates that the type of the non-data information is PID synchronization information, and the third field carries the first PID synchronization information. The method according to claim 8, wherein the third field includes a first subfield, and the first subfield indicates that the first PID synchronization information is a PID synchronization response message. The method according to any one of claims 6-9, wherein, before said generating the first information, said method further comprises: receiving second information, where the second information carries second PID synchronization information, and the second PID synchronization information is used to request the first PID synchronization information. The method according to claim 10, wherein the second information is a PLRB, and the PLRB includes a PLCB payload field; and the PLCB payload field carries the second PID synchronization information. The method according to claim 11, wherein the PLCB payload field includes a first field, a second field and a third field, the first field indicates that the second information carries non-data information, and the The second field indicates that the type of the non-data information is PID synchronization information, and the third field carries the second PID synchronization information. The method according to claim 12, wherein the third field includes a first subfield, and the first subfield indicates that the second PID synchronization information is a PID synchronization request message. The method according to claim 8 or 9 or 12 or 13, wherein the third field further includes a second subfield and at least one of the following subfields: a third subfield, a fourth subfield; Wherein, the second subfield is used to carry the PID of the corresponding PLRB, the third subfield is used to indicate the transmission direction for PID synchronization; the fourth subfield is used to indicate the transmission direction of the corresponding PLRB. A data transmission method, characterized in that the method comprises: Generate at least two code blocks, the at least two code blocks respectively carry a physical layer content block PLCB, and at least one first code block in the at least two code blocks carries control information of PLCB, and the control information of PLCB The information includes identification information of the PLCB and corresponding indication information, the indication information indicates that the PLCB is the Nth transmission, and the N is a positive integer; The at least two code blocks are sent. The method according to claim 15, wherein the first code block is a physical layer Reed-Solomon error correction coding block (PLRB), and the first code block includes a PLCB control field, and the PLCB control field carries the PLCB control information. The method according to claim 15 or 16, further comprising: Receiving a second code block, the second code block carrying retransmission information, the retransmission information includes: identification information of the first PLCB, indication information of the first PLCB, receiving status information, and information of the first PLCB The identification information is the identification ID of a successfully received PLCB, the indication information of the first PLCB indicates that the first PLCB is the Mth transmission, the M is a positive integer, and the receiving status information indicates that the at least two The receiving state of the code block; Determine, according to the retransmission information, a PLCB that fails to be transmitted among the PLCBs carried by the at least two code blocks. The method according to claim 17, wherein the second code block is a PLCB, the second code block includes a PLCB payload field, and the PLCB payload field carries the retransmission information. The method according to claim 18, wherein the PLCB payload field includes a first field, a second field and a third field, and the first field indicates that the second code block carries non-data information, so The second field indicates that the type of the non-data information is transmission confirmation information, and the third field carries the retransmission information. The method according to claim 19, wherein the third field further indicates an error feedback type, the error feedback type is complete error feedback or partial error feedback, and the complete error feedback indicates that the receiving status indicates For all the second PLCBs that receive errors, the partial error feedback indicates that the receiving status indicates only a portion of the second PLCBs that receive errors. A data transmission method, characterized in that the method comprises: Receive first information, where the first information includes first physical layer Reed-Solomon error correction coding block identification PID synchronization information, and the first PID synchronization information is used for PID synchronization; Perform PID synchronization according to the first PID synchronization information. The method of claim 21, wherein the PID synchronization comprises PID count synchronization between the first device and the second device. The method according to claim 22, wherein the first information is a synchronization symbol, and the synchronization symbol includes a time base field, and the time base field carries the first PID synchronization information. The method according to claim 23, wherein the synchronization symbol further includes a time base identification field for indicating a time base number, wherein the time base number indicated by the time base identification field is a first value, and the The first value indicates that the time base field carries the first PID synchronization information. The method according to claim 23 or 24, wherein the first PID synchronization information is used to indicate the PID of the physical layer Reed Solomon error correction coding block PLRB sent before the first information; Alternatively, the first PID synchronization information is used to indicate the PID of the PLRB sent after the first information. The method according to claim 22, wherein the first information is a PLRB, and the PLRB includes a physical layer content block PLCB payload field, and the PLCB payload field carries the first PID synchronization information. The method according to claim 26, wherein the first PID synchronization information is the PID of the first information. The method according to claim 26 or 27, wherein the PLCB payload field includes a first field, a second field and a third field, and the first field indicates that the first information carries non-data information, The second field indicates that the type of the non-data information is PID synchronization information, and the third field carries the first PID synchronization information. The method according to claim 28, wherein the third field includes a first subfield, and the first subfield indicates that the first PID synchronization information is a PID synchronization response message. The method according to any one of claims 26-29, wherein, before receiving the first information, the method further comprises: Sending second information, where the second information carries second PID synchronization information, and the second PID synchronization information is used to request the first PID synchronization information. The method according to claim 30, wherein the second information is a PLRB, and the PLRB includes a PLCB payload field; and the PLCB payload field carries the second PID synchronization information. The method according to claim 31, wherein the PLCB payload field includes a first field, a second field and a third field, the first field indicates that the second information carries non-data information, and the The second field indicates that the type of the non-data information is PID synchronization information, and the third field carries the second PID synchronization information. The method according to claim 32, wherein the third field includes a first subfield, and the first subfield indicates that the second PID synchronization information is a PID synchronization request message. The method according to claim 28 or 29 or 32 or 33, wherein the third field includes the second subfield and at least one of the following subfields: a third subfield, a fourth subfield; Wherein, the second subfield is used to carry the PID of the corresponding PLRB, the third subfield is used to indicate the transmission direction for PID synchronization; the fourth subfield is used to indicate the transmission direction of the corresponding PLRB. A data transmission method, characterized in that the method comprises: Receiving at least two code blocks, the at least two code blocks respectively carry a physical layer content block PLCB, and at least one first code block in the at least two code blocks carries control information of PLCB, and the control information of PLCB The information includes identification information of the PLCB and corresponding indication information, the indication information indicates that the PLCB is the Nth transmission, and the N is a positive integer; Control information for at least one PLCB is determined. The method according to claim 35, wherein the first code block is a physical layer Reed-Solomon error correction coding block (PLRB), the first code block includes a PLCB control field, and the PLCB control field carries the PLCB control information. The method according to claim 35 or 36, further comprising: Sending a second code block, where the second code block carries retransmission information, and the retransmission information includes: identification information of the first PLCB, indication information of the first PLCB, receiving status information, and information of the first PLCB The identification information is the identification ID of a successfully received PLCB, the indication information of the first PLCB indicates that the first PLCB is the Mth transmission, the M is a positive integer, and the receiving status information indicates the at least two The receive status of the code block. The method according to claim 37, wherein the second code block is a PLCB, the second code block includes a PLCB payload field, and the PLCB payload field carries the retransmission information. The method according to claim 38, wherein the PLCB payload field includes a first field, a second field and a third field, and the first field indicates that the second code block carries non-data information, so The second field indicates that the type of the non-data information is transmission confirmation information, and the third field carries the retransmission information. The method according to claim 39, wherein the third field further indicates an error feedback type, the error feedback type is complete error feedback or partial error feedback, and the complete error feedback indicates that the receiving status indicates For all the second PLCBs that receive errors, the partial error feedback indicates that the receiving status indicates only a portion of the second PLCBs that receive errors. A data transmission device, characterized in that the device comprises: A processing unit, configured to generate first information, where the first information includes first physical layer Reed-Solomon error correction coding block identification PID synchronization information, and the first PID synchronization information is used for PID synchronization; A transceiver unit, configured to send the first information. The apparatus of claim 41, wherein the PID synchronization comprises PID count synchronization between the first device and the second device. The device according to claim 42, wherein the first information is a synchronization symbol, and the synchronization symbol includes a time base field, and the time base field carries the first PID synchronization information. The device according to claim 43, wherein the synchronization symbol further includes a time base identification field for indicating a time base number, wherein the time base number indicated by the time base identification field is a first value, and the The first value indicates that the time base field carries the first PID synchronization information. The device according to claim 43 or 44, wherein the first PID synchronization information is used to indicate the PID of the physical layer Reed Solomon error correction coding block PLRB sent before the first information; Alternatively, the first PID synchronization information is used to indicate the PID of the PLRB sent after the first information. The device according to claim 42, wherein the first information is PLRB, and the PLRB includes a physical layer content block PLCB payload field, and the PLCB payload field carries the first PID synchronization information. The device according to claim 46, wherein the first PID synchronization information is the PID of the first information. The device according to claim 46 or 47, wherein the PLCB payload field includes a first field, a second field, and a third field, and the first field indicates that the first information carries non-data information, The second field indicates that the type of the non-data information is PID synchronization information, and the third field carries the first PID synchronization information. The apparatus according to claim 48, wherein the third field includes a first subfield, and the first subfield indicates that the first PID synchronization information is a PID synchronization response message. The device according to any one of claims 46-49, wherein the transceiver unit is also used for: Before the processing unit generates the first information, second information is received, the second information carries second PID synchronization information, and the second PID synchronization information is used to request the first PID synchronization information. The device according to claim 50, wherein the second information is a PLRB, and the PLRB includes a PLCB payload field; and the PLCB payload field carries the second PID synchronization information. The device according to claim 51, wherein the PLCB payload field includes a first field, a second field, and a third field, and the first field indicates that the second information carries non-data information, and the The second field indicates that the type of the non-data information is PID synchronization information, and the third field carries the second PID synchronization information. The apparatus according to claim 52, wherein the third field includes a first subfield, and the first subfield indicates that the second PID synchronization information is a PID synchronization request message. The device according to claim 48 or 49 or 52 or 53, wherein the third field further includes a second subfield and at least one of the following subfields: a third subfield, a fourth subfield; Wherein, the second subfield is used to carry the PID of the corresponding PLRB, the third subfield is used to indicate the transmission direction for PID synchronization; the fourth subfield is used to indicate the transmission direction of the corresponding PLRB. A data transmission device, characterized in that the device comprises: a processing unit, configured to generate at least two code blocks, the at least two code blocks each carry a physical layer content block PLCB, and at least one first code block of the at least two code blocks carries PLCB control information, The control information of the PLCB includes the identification information of the PLCB and corresponding indication information, the indication information indicates that the PLCB is the Nth transmission, and the N is a positive integer; A transceiver unit, configured to send the at least two code blocks. The device according to claim 55, wherein the first code block is a physical layer Reed Solomon error correction coding block (PLRB), the first code block includes a PLCB control field, and the PLCB control field carries the PLCB control information. The device according to claim 55 or 56, wherein the transceiver unit is also used for: Receiving a second code block, the second code block carrying retransmission information, the retransmission information includes: identification information of the first PLCB, indication information of the first PLCB, receiving status information, and information of the first PLCB The identification information is the identification ID of a successfully received PLCB, the indication information of the first PLCB indicates that the first PLCB is the Mth transmission, the M is a positive integer, and the receiving status information indicates that the at least two The receiving state of the code block; The processing unit is further configured to: determine, according to the retransmission information, a PLCB that fails to be transmitted among the PLCBs carried by the at least two code blocks. The device according to claim 57, wherein the second code block is a PLRB, the second code block includes a PLCB payload field, and the PLCB payload field carries the retransmission information. The device according to claim 58, wherein the PLCB payload field includes a first field, a second field and a third field, and the first field indicates that the second code block carries non-data information, so The second field indicates that the type of the non-data information is transmission confirmation information, and the third field carries the retransmission information. The device according to claim 59, wherein the third field further indicates an error feedback type, and the error feedback type is a complete error feedback or a partial error feedback, and the complete error feedback indicates that the receiving status indicates For all the second PLCBs that receive errors, the partial error feedback indicates that the receiving status indicates only a portion of the second PLCBs that receive errors. A data transmission device, characterized in that the device comprises: A transceiver unit, configured to receive first information, where the first information includes first physical layer Reed-Solomon error correction coding block identification PID synchronization information, and the first PID synchronization information is used for PID synchronization; The processing unit is configured to perform PID synchronization according to the first PID synchronization information. The apparatus of claim 61, wherein the PID synchronization comprises PID count synchronization between the first device and the second device. The device according to claim 62, wherein the first information is a synchronization symbol, and the synchronization symbol includes a time base field, and the time base field carries the first PID synchronization information. The device according to claim 63, wherein the synchronization symbol further includes a time base identification field for indicating a time base number, wherein the time base number indicated by the time base identification field is a first value, and the The first value indicates that the time base field carries the first PID synchronization information. The device according to claim 63 or 64, wherein the first PID synchronization information is used to indicate the PID of the physical layer Reed Solomon error correction coding block PLRB sent before the first information; Alternatively, the first PID synchronization information is used to indicate the PID of the PLRB sent after the first information. The device according to claim 62, wherein the first information is PLRB, and the PLRB includes a physical layer content block PLCB payload field, and the PLCB payload field carries the first PID synchronization information. The device according to claim 66, wherein the first PID synchronization information is the PID of the first information. The device according to claim 66 or 67, wherein the PLCB payload field includes a first field, a second field, and a third field, and the first field indicates that the first information carries non-data information, The second field indicates that the type of the non-data information is PID synchronization information, and the third field carries the first PID synchronization information. The apparatus according to claim 68, wherein the third field includes a first subfield, and the first subfield indicates that the first PID synchronization information is a PID synchronization response message. The device according to any one of claims 66-69, wherein the transceiver unit is further configured to: Before the first information is received, second information is sent, the second information carries second PID synchronization information, and the second PID synchronization information is used to request the first PID synchronization information. The device according to claim 70, wherein the second information is a PLRB, and the PLRB includes a PLCB payload field; and the PLCB payload field carries the second PID synchronization information. The device according to claim 71, wherein the PLCB payload field includes a first field, a second field, and a third field, and the first field indicates that the second information carries non-data information, and the The second field indicates that the type of the non-data information is PID synchronization information, and the third field carries the second PID synchronization information. The apparatus according to claim 72, wherein the third field includes a first subfield, and the first subfield indicates that the second PID synchronization information is a PID synchronization request message. The device according to claim 68 or 69 or 72 or 73, wherein the third field includes the second subfield and at least one of the following subfields: a third subfield and a fourth subfield; Wherein, the second subfield is used to carry the PID of the corresponding PLRB, the third subfield is used to indicate the transmission direction for PID synchronization; the fourth subfield is used to indicate the transmission direction of the corresponding PLRB. A data transmission device, characterized in that the device comprises: A transceiver unit, configured to receive at least two code blocks, the at least two code blocks each carry a physical layer content block PLCB, and at least one first code block in the at least two code blocks carries PLCB control information, The control information of the PLCB includes the identification information of the PLCB and corresponding indication information, the indication information indicates that the PLCB is the Nth transmission, and the N is a positive integer; A processing unit for determining control information of at least one PLCB. The device according to claim 75, wherein the first code block is a physical layer Reed Solomon error correction coding block (PLRB), the first code block includes a PLCB control field, and the PLCB control field carries the PLCB control information. The device according to claim 75 or 76, wherein the transceiver unit is also used for: Sending a second code block, where the second code block carries retransmission information, and the retransmission information includes: identification information of the first PLCB, indication information of the first PLCB, receiving status information, and information of the first PLCB The identification information is the identification ID of a successfully received PLCB, the indication information of the first PLCB indicates that the first PLCB is the Mth transmission, the M is a positive integer, and the receiving status information indicates that the at least two The receive status of the code block. The device according to claim 77, wherein the second code block is a PLCB, the second code block includes a PLCB payload field, and the PLCB payload field carries the retransmission information. The device according to claim 78, wherein the PLCB payload field includes a first field, a second field, and a third field, and the first field indicates that the second code block carries non-data information, so The second field indicates that the type of the non-data information is transmission confirmation information, and the third field carries the retransmission information. The device according to claim 79, wherein the third field further indicates an error feedback type, and the error feedback type is complete error feedback or partial error feedback, and the complete error feedback indicates that the receiving status indicates For all the second PLCBs that receive errors, the partial error feedback indicates that the receiving status indicates only a portion of the second PLCBs that receive errors. A communication device, characterized in that the device includes a processor and a communication interface, the communication interface is used to receive computer program code or instructions and transmit them to the processor; the processor runs the computer program code Or an instruction to make the device implement the method according to any one of claims 1-14 or the method according to any one of claims 15-20. A communication device, characterized in that the device includes a processor and a communication interface, the communication interface is used to receive computer program code or instructions and transmit them to the processor; the processor runs the computer program code Or an instruction to make the device implement the method according to any one of claims 21-34 or the method according to any one of claims 35-40. A computer-readable storage medium, characterized in that, the computer-readable storage medium stores programs or instructions, and when the program or the instructions are read and executed by one or more processors, claim 1- The method described in any one of claims 14, or, when the program or the instruction is read and executed by one or more processors, implements the method described in any one of claims 15-20, or, the program Or the instruction implements the method described in any one of claims 21-34 when read and executed by one or more processors, or, the program or the instruction is read by one or more processors And when executed, the method according to any one of claims 35-40 is realized. A vehicle, characterized in that the vehicle comprises a first device and/or a second device, the first device is used to execute the method according to any one of claims 1-14, and the second device uses For carrying out the method as described in any one of claims 21-34. A vehicle, characterized in that the vehicle comprises a first device and/or a second device, the first device is used to execute the method according to any one of claims 15-20, and the second device uses For carrying out the method as described in any one of claims 35-40. A data transmission system, characterized in that the system comprises the device according to any one of claims 41-54, and the device according to any one of claims 61-74. A data transmission system, characterized in that the system comprises the device according to any one of claims 55-60 and the device according to any one of claims 75-80.