A data transmission method and apparatus

Abstract

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

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a data transmission method and apparatus. Background Technology

[0002] In high-speed wired transmission, especially in some vehicle-mounted serializer / deserializer (SerDes) transmissions, due to the high requirements for bit error rate (BER), retransmission is usually considered to improve the reliability of the transmission link.

[0003] In SerDes transmission, the transmitting end (first device) sequentially sends physical layer (PHY) code blocks. Each PHY code block is a physical layer Reed-Solomon error correction block (PLRB), and each PHY code block carries a physical layer content block (PLCB). When a PHY code block transmission fails, the receiving end (second device) sends an acknowledgment message (ACK) to the first device, indicating the failed PHY code block using the 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, completing the retransmission. For example, when PHY code block 2 fails to transmit, the second device sends an ACK to the first device, indicating the failure to receive PHY code block 2 using the PID information carried in the ACK. The first device encapsulates the PLCB 2 carried by PHY code block 2 into PHY code block 5 and sends it to the second device, completing the retransmission.

[0004] In SerDes transmission, the first and second devices synchronize the PHY code blocks' clocks during link establishment, thereby determining the PHY code block number based on clock counts. In interference scenarios, prolonged interference can cause the PHY clock to lose synchronization. This PHY clock loss leads to inaccurate PHY code block counting by the second device, resulting in errors during PHY code block retransmission. Summary of the Invention

[0005] This application provides a data transmission method and apparatus to solve the problem of errors occurring during the retransmission of PHY code blocks due to PHY clock out-of-sync.

[0006] In a first aspect, embodiments of this application provide a data transmission method, including: generating first information and sending it, the first information including first PID synchronization information, the first PID synchronization information being used for PID synchronization.

[0007] In this embodiment, the first device sends PID synchronization information to the second device, enabling the second device to calibrate the PID count based on the PID synchronization information. This ensures that the PHY code block indicated by the PID information at the data receiving end is consistent with the PHY code block determined by the data sending end based on the PID information, thereby avoiding erroneous retransmissions.

[0008] In one possible design, PID synchronization includes PID count synchronization between the first device and the second device. In this design, the first and second devices can synchronize PID counts using PID synchronization information, allowing them to identify the same PHY code block and thus avoiding erroneous retransmissions.

[0009] In one possible design, the first information is a synchronization symbol, which includes a time base field carrying the first PID synchronization information. In this design, by multiplexing the periodically transmitted synchronization symbols, the data receiver can simultaneously restore PHY code block delimitation and scrambling code synchronization while simultaneously synchronizing PID counting, thus avoiding erroneous retransmissions after link recovery.

[0010] In one possible design, the synchronization symbol also includes a time base identifier field for indicating a time base number, wherein the time base identifier field indicates a first value, and the first value indicates that the time base field carries first PID synchronization information. In the above method, using the first value as an identifier for the PID synchronization information carried by the synchronization symbol allows the second device to read the PID synchronization information from the time base field when the time base number indicated by the time base ID field is the first value.

[0011] In one possible design, the first PID synchronization information is used to indicate the PID of a PLRB sent before the first information; or, the first PID synchronization information is used to indicate the PID of a PLRB sent after the first information. In this design, the first device indicates the PID of a PLRB at a specific location, enabling the second device to calibrate the PID of that PLRB, thereby achieving PID counting synchronization.

[0012] In one possible design, the first information is the PLRB, which includes a Physical Layer Content Block (PLCB) payload field. The PLCB payload field carries the first PID synchronization information. In the above implementation, the PHY control message can be used to carry the PID synchronization information, thereby achieving PID synchronization and avoiding erroneous retransmissions.

[0013] In one possible design, the first PID synchronization information is the PID of the first information. This design, by carrying the PID of the first information in the first information, allows the second device to calibrate the PID count of the first information upon receiving it.

[0014] In one 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, the second field indicates that the type of non-data information is PID synchronization information, and the third field carries the first PID synchronization information. In this design, the first PID synchronization information is carried by the PHY control information, so that when 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 second device reads the first PID synchronization information from the third field.

[0015] In one possible design, the third field includes a first subfield, which indicates that the first PID synchronization information is a PID synchronization response message. In the above design, the first subfield can be used to distinguish between response messages and request messages.

[0016] In one possible design, before generating the first information, the method further includes: receiving second information, the second information carrying second PID synchronization information, the second PID synchronization information being used to request the first PID synchronization information. In the above design, the first information can be sent upon request from the second device.

[0017] In one possible design, the second information is PLRB, which includes a PLCB payload field; the PLCB payload field carries the second PID synchronization information. In the above implementation, the second PID synchronization information can be carried using the PHY control message, thereby achieving PID synchronization and preventing erroneous retransmissions.

[0018] In one 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, the second field indicates that the type of non-data information is PID synchronization information, and the third field carries the second PID synchronization information. In this design, the second PID synchronization information is carried by the PHY control information, so that when 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 second device reads the second PID synchronization information from the third field.

[0019] In one possible design, the third field includes a first subfield, which indicates that the second PID synchronization information is a PID synchronization request message. In the above design, the first subfield can be used to distinguish between response messages and request messages.

[0020] In one 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; 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, and the fourth subfield is used to indicate the transmission direction of the corresponding PLRB. This design improves the accuracy of PID synchronization.

[0021] Secondly, embodiments of this application provide a data transmission method, including: generating at least two code blocks and transmitting them, wherein each of the at least two code blocks carries a physical layer content block (PLCB), and at least one of the at least two code blocks carries control information of the PLCB, wherein the control information of the PLCB includes identification information of the PLCB and corresponding indication information, wherein the indication information indicates that the PLCB is the Nth transmission, and N is a positive integer.

[0022] In this embodiment, the PHY code block is determined by the identifier of the PLCB and the number of times the PLCB has been retransmitted, enabling the second device to accurately indicate the PHY code block that has been transmitted incorrectly, thereby avoiding retransmission errors. Furthermore, in this way, both the transmitting and receiving ends no longer need to maintain a PID.

[0023] In one possible design, the first code block is a PLRB, which includes a PLCB control field that carries the control information of the PLCB. In the above embodiment, the PLCB control field can be used to carry the control information of the PLCB.

[0024] In one possible design, the method further includes: receiving a second code block carrying retransmission information, the retransmission information including: identification information of a first PLCB, indication information of a first PLCB, and reception 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, where M is a positive integer, and the reception status information indicates the reception status of at least two code blocks; and determining the PLCB that failed to transmit among the PLCBs carried in the at least two code blocks based on the retransmission information. In the above design, by carrying retransmission information in the second code block, the first device can determine a PHY code block based on the retransmission information, and thus determine the PHY code block with transmission errors based on the PHY code block.

[0025] In one possible design, the second code block is a PLRB, which includes a PLCB payload field that carries retransmission information. In the above implementation, the PLCB payload field can be used to carry retransmission information.

[0026] In one 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, the second field indicates that the type of non-data information is transmission acknowledgment information, and the third field carries retransmission information. In this design, retransmission information is carried through PHY control information, allowing the second device to read the retransmission information from the third field when 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 transmission acknowledgment information.

[0027] In one possible design, the third field also indicates the error feedback type, which can be either complete error feedback or partial error feedback. Complete error feedback indicates that the second PLCB indicates all received errors in the reception status, while partial error feedback indicates that the second PLCB only indicates a partial reception error. This design allows the second device to determine the feedback range.

[0028] Thirdly, embodiments of this application provide a data transmission method, including: receiving first information and performing PID synchronization according to first PID synchronization information, wherein the first information includes first physical layer Reed-Solomon error correction coding block identifier PID synchronization information, and the first PID synchronization information is used for PID synchronization.

[0029] In this embodiment, the first device sends PID synchronization information to the second device, enabling the second device to calibrate the PID count based on the PID synchronization information. This ensures that the PHY code block indicated by the PID information at the data receiving end is consistent with the PHY code block determined by the data sending end based on the PID information, thereby avoiding erroneous retransmissions.

[0030] In one possible design, PID synchronization includes PID count synchronization between the first device and the second device. In this design, the first and second devices can synchronize PID counts using PID synchronization information, allowing them to identify the same PHY code block and thus avoiding erroneous retransmissions.

[0031] In one possible design, the first information is a synchronization symbol, which includes a time base field carrying the first PID synchronization information. In this design, by multiplexing the periodically transmitted synchronization symbols, the data receiver can simultaneously restore PHY code block delimitation and scrambling code synchronization while simultaneously synchronizing PID counting, thus avoiding erroneous retransmissions after link recovery.

[0032] In one possible design, the synchronization symbol also includes a time base identifier field for indicating a time base number, wherein the time base identifier field indicates a first value, and the first value indicates that the time base field carries first PID synchronization information. In the above method, using the first value as an identifier for the PID synchronization information carried by the synchronization symbol allows the second device to read the PID synchronization information from the time base field when the time base number indicated by the time base ID field is the first value.

[0033] In one possible design, the first PID synchronization information is used to indicate the PID of a PLRB sent before the first information; or, the first PID synchronization information is used to indicate the PID of a PLRB sent after the first information. In this design, the first device indicates the PID of a PLRB at a specific location, enabling the second device to calibrate the PID of that PLRB, thereby achieving PID counting synchronization.

[0034] In one possible design, the first information is the PLRB, which includes a Physical Layer Content Block (PLCB) payload field. The PLCB payload field carries the first PID synchronization information. In the above implementation, the PHY control message can be used to carry the PID synchronization information, thereby achieving PID synchronization and avoiding erroneous retransmissions.

[0035] In one possible design, the first PID synchronization information is the PID of the first information. This design, by carrying the PID of the first information in the first information, allows the second device to calibrate the PID count of the first information upon receiving it.

[0036] In one 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, the second field indicates that the type of non-data information is PID synchronization information, and the third field carries the first PID synchronization information. In this design, the first PID synchronization information is carried by the PHY control information, so that when 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 second device reads the first PID synchronization information from the third field.

[0037] In one possible design, the third field includes a first subfield, which indicates that the first PID synchronization information is a PID synchronization response message. In the above design, the first subfield can be used to distinguish between response messages and request messages.

[0038] In one possible design, before receiving the first information, the method further includes: sending second information, the second information carrying second PID synchronization information, the second PID synchronization information being used to request the first PID synchronization information. In the above design, the first information can be sent upon request from the second device.

[0039] In one possible design, before generating the first information, the method further includes receiving second information, the second information carrying second PID synchronization information. In the above implementation, the second PID synchronization information can be carried using PHY control messages, thereby achieving PID synchronization and avoiding erroneous retransmissions.

[0040] In one 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, the second field indicates that the type of non-data information is PID synchronization information, and the third field carries the second PID synchronization information. In this design, the second PID synchronization information is carried by the PHY control information, so that when 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 second device reads the second PID synchronization information from the third field.

[0041] In one possible design, the third field includes a first subfield, which indicates that the second PID synchronization information is a PID synchronization request message. In the above design, the first subfield can be used to distinguish between response messages and request messages.

[0042] In one 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; 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, and the fourth subfield is used to indicate the transmission direction of the corresponding PLRB. This design improves the accuracy of PID synchronization.

[0043] Fourthly, embodiments of this application provide a data transmission method, comprising: receiving at least two code blocks, each of the at least two code blocks carrying a physical layer content block (PLCB), and at least one of the at least two code blocks carrying control information of the PLCB, wherein the control information of the PLCB includes identification information of the PLCB and corresponding indication information, wherein the indication information indicates that the PLCB is the Nth transmission, and N is a positive integer; and determining control information of at least one PLCB.

[0044] In this embodiment, the PHY code block is determined by the identifier of the PLCB and the number of times the PLCB has been retransmitted, enabling the second device to accurately indicate the PHY code block that has been transmitted incorrectly, thereby avoiding retransmission errors. Furthermore, in this way, both the transmitting and receiving ends no longer need to maintain a PID.

[0045] In one possible design, the first code block is a PLRB, which includes a PLCB control field that carries the control information of the PLCB. In the above embodiment, the PLCB control field can be used to carry the control information of the PLCB.

[0046] In one possible design, the method further includes: sending a second code block carrying retransmission information, which includes: identification information of the first PLCB, indication information of the first PLCB, and reception 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 transmitting for the Mth time, where M is a positive integer, and the reception status information indicates the reception 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 based on the retransmission information, and thus determine the PHY code block that was transmitted incorrectly based on the PHY code block.

[0047] In one possible design, the second code block is a PLRB, which includes a PLCB payload field that carries retransmission information.

[0048] In one possible design, the second code block is a PLRB, which includes a PLCB payload field that carries retransmission information. In the above implementation, the PLCB payload field can be used to carry retransmission information.

[0049] In one 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, the second field indicates that the type of non-data information is transmission acknowledgment information, and the third field carries retransmission information. In this design, retransmission information is carried through PHY control information, allowing the second device to read the retransmission information from the third field when 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 transmission acknowledgment information.

[0050] In one possible design, the third field also indicates the error feedback type, which can be either complete error feedback or partial error feedback. Complete error feedback indicates that the second PLCB indicates all received errors in the reception status, while partial error feedback indicates that the second PLCB only indicates a partial reception error. This design allows the second device to determine the feedback range.

[0051] Fifthly, this application provides a data transmission apparatus, which may be a communication device or a chip or chipset within a communication device. The apparatus may include a processing unit and a transceiver unit. When the apparatus is a communication device, the processing unit may be a processor, and the transceiver unit may be a transceiver; the apparatus may also include a storage module, which may be a memory; the storage module is used to store instructions, and the processing unit executes the instructions stored in the storage module to perform the methods of the first aspect or any design in the first aspect, or the second aspect or any design in the second aspect. When the apparatus is a chip or chipset within a communication device, the processing unit may be a processor, and the transceiver unit may be an input / output interface, pin, or circuit, etc.; the processing unit executes the instructions stored in the storage module to perform the methods of the first aspect or any design in the first aspect, or the second aspect or any design in the second aspect. The storage module may be a storage module within the chip or chipset (e.g., a register, cache, etc.), or a storage module located outside the chip or chipset within the communication device (e.g., a read-only memory, random access memory, etc.).

[0052] Sixthly, this application provides a data transmission apparatus, which may be a communication device or a chip or chipset within a communication device. The apparatus may include a processing unit and a transceiver unit. When the apparatus is a communication device, the processing unit may be a processor, and the transceiver unit may be a transceiver; the apparatus may further include a storage module, which may be a memory; the storage module is used to store instructions, and the processing unit executes the instructions stored in the storage module to perform the methods of the third aspect or any of the designs in the third aspect, or the fourth aspect, as described above. When the apparatus is a chip or chipset within a communication device, the processing unit may be a processor, and the transceiver unit may be an input / output interface, pin, or circuit, etc.; the processing unit executes the instructions stored in the storage module to perform the methods of the third aspect or any of the designs in the third aspect, or the fourth aspect, as described above. The storage module may be a storage module within the chip or chipset (e.g., a register, cache, etc.), or a storage module located outside the chip or chipset within the communication device (e.g., a read-only memory, random access memory, etc.).

[0053] In a seventh aspect, this application provides a data transmission apparatus, including: a processor, and may further include a communication interface and a memory. The communication interface is used for transmitting information, and / or messages, and / or data between the apparatus and other apparatuses. The memory is used to store computer-executable instructions, and when the apparatus is running, the processor executes the computer-executable instructions stored in the memory to cause the apparatus to perform the methods as described in the first aspect or any design in the first aspect, the second aspect or any design in the second aspect.

[0054] Eighthly, this application provides a data transmission apparatus, including: a processor, and may further include a communication interface and a memory. The communication interface is used for transmitting information, and / or messages, and / or data between the apparatus and other devices. The memory is used to store computer-executable instructions, and when the apparatus is running, the processor executes the computer-executable instructions stored in the memory to cause the apparatus to perform the methods as described in the third aspect or any of the designs in the third aspect, the fourth aspect or any of the designs in the fourth aspect.

[0055] Ninthly, embodiments of this application provide a data transmission system, including the data transmission apparatus of the fifth aspect and the data transmission apparatus of the sixth aspect.

[0056] In a tenth aspect, embodiments of this application provide a data transmission system, including the data transmission apparatus of the seventh aspect and the data transmission apparatus of the eighth aspect.

[0057] Eleventhly, embodiments of this application also provide a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform any one of the first to fourth aspects, or any one of the methods designed in any one aspect.

[0058] In a twelfth aspect, embodiments of this application also provide a computer program product including instructions that, when run on a computer, cause the computer to perform any one of the first to fourth aspects, or any one of the methods designed in any one aspect.

[0059] In a thirteenth aspect, embodiments of this application also provide a communication system, which includes a transmitting node and a receiving node, wherein the transmitting node can execute the methods corresponding to the first aspect or any design in the first aspect, and the receiving node can execute the methods corresponding to the third aspect or any design in the third aspect.

[0060] In a fourteenth aspect, embodiments of this application also provide a communication system, which includes a transmitting node and a receiving node, wherein the transmitting node can execute the methods corresponding to the second aspect or any design in the second aspect described above, and the receiving node can execute the methods corresponding to the fourth aspect or any design in the fourth aspect described above.

[0061] In a fifteenth aspect, an embodiment of this application provides a chip including at least one processor and a communication interface. The processor is coupled to a memory and is used to read a computer program stored in the memory to execute any one of the first to fourth aspects, or any one of the methods designed in any one aspect.

[0062] It should be noted that in the embodiments of this application, "coupling" refers to two components being directly or indirectly combined with each other.

[0063] In a sixteenth aspect, embodiments of this application provide a vehicle including a first device and / or a second device, the first device being used to perform the method of the first aspect or any of the designs in the first aspect, and the second device being used to perform the method of the third aspect or any of the designs in the third aspect.

[0064] In a seventeenth aspect, embodiments of this application provide a vehicle including a first device and / or a second device, the first device being used to perform the method of the aforementioned second aspect or any of the designs in the second aspect, and the second device being used to perform the method of the aforementioned fourth aspect or any of the designs in the fourth aspect. Attached Figure Description

[0065] Figure 1 A data transmission schematic diagram provided for an embodiment of this application;

[0066] Figure 2 A schematic diagram of a PLRB format provided for an embodiment of this application;

[0067] Figure 3 A schematic diagram of synchronous symbol transmission provided in an embodiment of this application;

[0068] Figure 4 A flowchart illustrating a data transmission method provided in an embodiment of this application;

[0069] Figure 5 A flowchart illustrating a data transmission method provided in an embodiment of this application;

[0070] Figure 6 A data transmission schematic diagram provided for an embodiment of this application;

[0071] Figure 7 This is a schematic diagram of the structure of a data transmission device provided in an embodiment of this application;

[0072] Figure 8 This is a schematic diagram of a data transmission device provided in an embodiment of this application. Detailed Implementation

[0073] The terms “comprising” and “having”, and any variations thereof, in the specification, claims, and drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such process, method, product, or device.

[0074] The embodiments of this application can be applied to wired transmission, such as wired point-to-point high-speed transmission, like image and control transmission between a camera and a multi-domain controller (MDC) of an autonomous driving platform, or image transmission between in-vehicle devices such as in-vehicle cameras or cockpit domain controllers (or control domain cockpits, CDC) and large screens.

[0075] For example, the communication device involved in the embodiments of this application can be a device capable of sending information (such as data frames, control information, etc.) to other devices, such as a vehicle-mounted image sensor like a camera or LiDAR, or an image processing device like an MDC or CDC, or an image display device like a large screen. As another example, the communication device involved in the embodiments of this application can also be other transmission devices besides vehicle-mounted devices.

[0076] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in 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 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, where a, b, and c can be single or multiple.

[0077] Furthermore, unless otherwise stated, the ordinal numbers 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, timing, priority, or importance of multiple objects. For example, "first data packet" and "second data packet" are names given only for ease of description; these two data packets may be the same data packet or they may be different data packets.

[0078] The technical features involved in the embodiments of this application are described below.

[0079] In high-speed wired transmission, especially in some vehicle-mounted SerDes transmissions, due to the high BER requirements, in addition to using error correction and detection coding (such as Reed-Solomon forward error correction (RS-FEC)) at the PHY layer, retransmission is also considered to improve the reliability of the transmission link.

[0080] In SerDes transmission, bidirectional transmission usually occurs simultaneously. For ease of description, we will select a transmission direction below, with the sending end being the first device and the receiving end being the second device.

[0081] The first device sequentially transmits PHY code blocks, each PHY code block representing one PLRB, and each PHY code block carries one PLCB. When a PHY code block transmission fails, the second device sends an ACK to the first device, indicating 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, completing the retransmission. For example, when PHY code block 2 fails to transmit, the second device sends an ACK to the first device, indicating the failed reception of PHY code block 2 through the PID information carried in the ACK. The first device encapsulates PLCB 2 carried by PHY code block 2 into PHY code block 5 and sends it to the second device, completing the retransmission. Figure 1 As shown.

[0082] In SerDes transmission, clock and data recovery (CDR) technology is used to synchronize the PHY clock between the first and second devices during link establishment. The first and second devices count PHY code blocks based on the PHY clock, thereby determining the PID of the PHY code block based on the count.

[0083] In interference scenarios, prolonged interference can cause the PHY clock of the second device to lose synchronization. This PHY clock loss leads to inaccurate counting of PHY blocks by the second device. Since the second device uses a PID indicator in its ACK to indicate erroneously transmitted PHY blocks, it triggers a retransmission by the first device. Therefore, PHY clock loss can cause errors in the retransmission of PHY blocks.

[0084] Based on this, embodiments of this application provide a data transmission method and apparatus to solve the problem of PHY code block retransmission errors caused by PHY clock out-of-sync. The method and apparatus are based on the same technical concept. Since the principles of the method and apparatus in solving the problem are similar, the implementation of the apparatus and method can be referred to each other, and repeated details will not be repeated. Embodiments of this application provide an information transmission method and apparatus that can be applied to in-vehicle networks, especially intelligent vehicle in-vehicle networks, and can also be applied to other wired transmission devices.

[0085] The PHY code blocks in the embodiments of this application will be explained below to facilitate understanding by those skilled in the art.

[0086] 1) PHY code block

[0087] A PHY code block is a PLRB, which includes a PLRB payload field and a PLRB redundancy field. The PLRB payload field includes a PLCB control field and a PLCB payload field, and may also include a cyclic redundancy check (CRC) field. The PLCB control field may include a PLCB ID for uniquely identifying the PLCB.

[0088] The PLCB payload field can include one or more information blocks. These information blocks can use 64 / 66 line encoding, 64 / 65 line encoding, or other encoding methods; no specific limitation is made here. Each information block includes an indicator bit and a load field. The indicator bit indicates the type of information carried by the load field, which can be either data information or non-data information.

[0089] For example, taking a 2-bit indicator bit as an example, the content indicated by the indicator bit can be as shown in Table 1.

[0090] Table 1

[0091] Indicator bit meaning 00 The payload field carries the intermediate fragments 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 load field carries non-data information, such as sub-control bits and PHY control information.

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

[0093] Table 2

[0094] Indicator bit meaning 0 The payload field carries data frames. 1 The load field carries non-data information, such as sub-control bits and PHY control information.

[0095] If the indicator bit indicates that the load field carries non-data information, the load field may include a sub-indicator field and a content field. The sub-indicator bit can indicate the type of non-data information, and the content field can carry non-data information. For example, currently, the content indicated by the sub-indicator bit can be as shown in Table 3.

[0096] Table 3

[0097] Sub-indicator bit Types of non-data information 0x1e PHY Padding 0x2d PHY retransmission (ACK) 0x3c Link Reconstruction 0x4b Interval training 0x5a hibernation other Reserved

[0098] Figure 1 The ACK in the PHY block can be a type of non-data information, carried by the PHY block and sent by the second device to the first device. Similarly, the acknowledgment message of the PHY block sent by the second device to the first device is carried by the PHY block sent by the first device to the second device.

[0099] For example, PLRB can be as follows Figure 2 As shown.

[0100] It should be understood that the naming, values, and correspondence of the above fields are merely illustrative examples.

[0101] 2) Synchronization symbols

[0102] To achieve fast link recovery and periodically calibrate the pixel clocks at both ends of the transmission, the SerDes transmission scheme periodically sends synchronization symbols, such as... Figure 3 As shown, the synchronization symbol carries a delimiter, a random scrambling code, and pixel clock information. The starting position of the PHY can be aligned by calibrating the pixel clock.

[0103] For example, the fields included in a synchronization symbol may be as shown in Table 4.

[0104] Table 4

[0105]

[0106] It should be understood that all fields described in Table 4 above may be included in the synchronization symbol, or only some 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 in detail here.

[0107] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0108] Example 1:

[0109] This application provides a data transmission method. For example... Figure 4 As shown, the method includes:

[0110] S401, the first device generates first information, the first information including first PID synchronization information, the first PID synchronization information being used for PID synchronization.

[0111] In one exemplary embodiment, PID synchronization may include PID count synchronization between a first device and a second device.

[0112] S402, the first device sends the first information. Correspondingly, the second device receives the first information.

[0113] S403, the second device performs PID counting synchronization based on the first PID synchronization information.

[0114] In this configuration, the first device can be a data transmitter and the second device can be a data receiver. Alternatively, the first device can also be a data receiver and the second device can be a data transmitter. The term "data" can be understood as business data, such as image data or video data.

[0115] Understandably, the distinction between data sender and data receiver is merely logical. In specific scenarios, the roles of data sender and data receiver can be interchanged. For example, when A sends data to B, A acts as the data sender and B acts as the data receiver. When B sends data to A, B acts as the data sender and A acts as the data receiver.

[0116] Both the PHY code blocks sent from the data transmitter to the data receiver and the PHY code blocks sent from the data receiver to the data transmitter can use Reed-Solomon forward error correction (RS-FEC). The length and basis of the Reed-Solomon (RS) encoding of the PHY code blocks sent from the data transmitter to the data receiver and the PHY code blocks sent from the data receiver to the data transmitter can be different. The basis can be understood as the unit length of the code elements included in the PHY code block. For example, the PHY code block sent from the data transmitter to the data receiver can use RS-FEC(340, 312, 10), and the PHY code block sent from the data receiver to the data transmitter can use RS-FEC(76, 72, 8). RS-FEC(340, 312, 10) indicates that the PHY code block includes 340 symbols, of which 312 carry valid data, and the unit length of each symbol is 10 bits. RS-FEC(76, 72, 8) indicates that the PHY code block includes 76 symbols, of which 72 carry valid data, and the unit length of each symbol is 8 bits. For ease of description, the PHY code block sent from the data transmitter to the data receiver is called the forward PHY code block, and the transmission from the data transmitter to the data receiver is called forward transmission. The PHY code block sent from the data receiver to the data transmitter is called the reverse PHY code block, and the transmission from the data receiver to the data transmitter is called reverse transmission.

[0117] In this embodiment, the first device sends PID synchronization information to the second device, enabling the second device to calibrate the PID count based on the PID synchronization information. This ensures that the PHY code block indicated by the PID information at the data receiving end is consistent with the PHY code block determined by the data sending end based on the PID information, thereby avoiding erroneous retransmissions.

[0118] In one possible implementation, the first information can be a synchronization symbol. The first PID synchronization information can be carried in the time base field of the synchronization symbol.

[0119] For example, taking the synchronization symbol as an example including the fields described in Table 4, the first information can be as shown in Table 5.

[0120] Table 5

[0121]

[0122] It should be understood that all fields described in Table 5 above may be included in the first information, or only some fields may be included in the first information. Furthermore, the first information may also include other fields not shown in Table 5, which will not be described in detail here.

[0123] Optionally, the time base ID field in the synchronization signal indicates a first value, which indicates that the time base field carries first PID synchronization information. For example, the time base ID field in the synchronization signal indicates a time base number of 0000, and this time base number of 0000 indicates that the time base field carries first PID synchronization information.

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

[0125] For example, taking the synchronization symbol as an example including the fields described in Table 4, the first information can be as shown in Table 6.

[0126] Table 6

[0127]

[0128] For example, the first PID synchronization information can be used to indicate the PID of the PLRB that was sent before the first message. For instance, the first PID synchronization information can be used to indicate the PID of the PLRB preceding the first message. Or, for another example, the first PID synchronization information can be used to indicate the PID of the second-to-last PLRB that was sent before the first message, and so on.

[0129] Alternatively, the first PID synchronization information can also be used to indicate the PID of the PLRB sent after the first message. For example, the first PID synchronization information can be used to indicate the PID of the PLRB following the first message. Or, for another example, the first PID synchronization information can be used to indicate the PID of the second PLRB sent after the first message, and so on.

[0130] In one implementation, the transmission frequency of the synchronization symbol carrying PID synchronization information can be pre-configured or determined through negotiation during the link establishment process between the first and second devices. Of course, other methods can also be used to determine it; no specific limitations are made here.

[0131] In the above implementation, by reusing the periodically transmitted synchronization symbols, the data receiving end can complete the PID counting synchronization while restoring PHY code block delimitation and scrambling code synchronization, thereby avoiding erroneous retransmissions after link recovery.

[0132] In another possible implementation, the first information can also be a PLRB. The first synchronization information can be carried in the PLCB payload field of the PLRB.

[0133] In one exemplary embodiment, the first PID synchronization information can be the PID of the first information.

[0134] As an example, the PLRB can carry the first synchronization information in the following form: the PLRB 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 carries the first PID synchronization information.

[0135] The first field can be Figure 2 For details on the indicator bits shown, please refer to the relevant descriptions of the indicator bits mentioned above; they will not be repeated here.

[0136] The second field can be Figure 2 The sub-indicator bit shown in this embodiment allows the second field to indicate that non-data information is PID synchronization information through a single value. For example, 0x69 can indicate that non-data information is PID synchronization information. Exemplary examples show that the content indicated by the second field can be as shown in Table 7.

[0137] Table 7

[0138] Second field Types of non-data information 0x1e PHY Padding

[0139] 0x2d PHY retransmission (ACK) 0x3c Link Reconstruction 0x4b Interval training 0x5a hibernation 0x69 PID synchronization information other Reserved

[0140] It should be understood that the indications shown in Table 7 above, as well as the correspondence between values ​​and indications, are merely illustrative examples.

[0141] The third field can be Figure 2 As shown in the content fields, in this embodiment of the application, the third field may carry PID synchronization information.

[0142] Optionally, the first information may also include a CRC field. The CRC field ensures that, in the event of a PLRB code block transmission error, the correctness of the PHY retransmission message can be verified through CRC check.

[0143] The following explains the format of the third field when carrying PID synchronization information, which can also be understood as the format of PID information.

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

[0145] The first subfield can be used to indicate whether the PLRB is a response message or a request message for PID synchronization information. The first subfield in the first information can indicate that the first PID synchronization information is a response message.

[0146] The second subfield can be used to carry the PID of the corresponding PLRB. For example, the second subfield in the first information can carry the PID of the first information.

[0147] The third subfield can be used to indicate the transmission direction for PID synchronization.

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

[0149] To facilitate understanding, the third field carrying PID synchronization information is illustrated below with an example, as shown in Table 8.

[0150] Table 8

[0151]

[0152] In this context, forward transmission of PID synchronization can be understood as the data sending end sending PID synchronization information to the data receiving end for PID synchronization, which is to say, sending a PID synchronization response message. After receiving the PID synchronization information, the data receiving end performs PID counting synchronization.

[0153] Reverse transmission PID synchronization can be understood as the data receiving end sending PID synchronization information to the data sending end for PID synchronization, that is, sending a PID synchronization response message. After receiving the PID synchronization information, the data sending end performs PID counting synchronization.

[0154] It should be understood that Table 8 is merely an illustrative example and does not specifically limit the number of bits, values, and correspondence between the various subfields in the third field and the indicated content. Furthermore, the third field may include other subfields; however, no specific limitations are made here regarding the subfields included in the third field.

[0155] 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 it may send the first information to the second device upon triggering an event. When the first device periodically sends the first information, the sending period of the first information may be pre-configured or determined through negotiation during the establishment of a link between the first device and the second device.

[0156] 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 a second information to the first device, the second information carrying second PID synchronization information, which is used to request the first PID synchronization information.

[0157] The second information can be a 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 and the PLRB information used for PID synchronization, such as the PID and transmission direction of the first information. 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, such as the PID and transmission direction of the second information. Taking the format of the third field shown in Table 8 as an example, the difference between the first and second information is illustrated. The first subfield of the first information has a value of 10, indicating a response message; the first subfield of the second information has a value of 00, indicating 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.

[0158] For details on the similarities between the second and first pieces of information, please refer to the relevant description of the first piece of information above; these details will not be repeated here.

[0159] In the above implementation, PHY control messages can be used to carry PID synchronization information, thereby achieving PID synchronization and avoiding erroneous retransmissions.

[0160] Example 2:

[0161] This application provides a data transmission method. For example... Figure 5 As shown, the method includes:

[0162] S501, the first device generates at least two code blocks.

[0163] In this configuration, at least two code blocks each carry a PLCB, and at least one of the first 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. The indication information indicates that the PLCB is the Nth transmission, where N is a positive integer.

[0164] S502, the first device transmits at least two code blocks. Correspondingly, the second device receives at least two code blocks.

[0165] S503, the second device stores the control information of the PLCB carried in at least one of the first code blocks.

[0166] In this configuration, the first device can be a data transmitter and the second device can be a data receiver. Alternatively, the first device can also be a data receiver and the second device can be a data transmitter. The term "data" can be understood as business data, such as image data or video data.

[0167] Understandably, the distinction between data sender and data receiver is merely logical. In specific scenarios, the roles of data sender and data receiver can be interchanged. For example, when A sends data to B, A acts as the data sender and B acts as the data receiver. When B sends data to A, B acts as the data sender and A acts as the data receiver.

[0168] In this embodiment, the PHY code block is determined by the identifier of the PLCB and the number of times the PLCB has been retransmitted, enabling the second device to accurately indicate the PHY code block that has been transmitted incorrectly, thereby avoiding retransmission errors. Furthermore, in this way, both the transmitting and receiving ends no longer need to maintain a PID.

[0169] In one possible implementation, the first code block can be a PLRB. The control information of the PLRB can carry the PLRB's PLCB control field.

[0170] In one implementation, the PLCB control field may include a PLCB ID field and a retransmission indication field, wherein the retransmission indication field may indicate that the PLCB is retransmitting for the Nth time. It should be understood that "PLCB ID field" and "retransmission indication field" are merely exemplary names, and may also be named other fields, as long as the field has the characteristics of "retransmission indication field" or "PLCB ID field" in the embodiments of this application, it can be considered as "retransmission indication field" or "PLCB ID field" in the embodiments of this application.

[0171] For example, the PLCB control fields can be as shown in Table 9.

[0172] Table 9

[0173]

[0174] It should be understood that Table 9 is only an illustrative example. The fill instruction field may be an optional field. In addition, the PLCB control field may also include other fields not shown in Table 9. No specific limitation is made here on the subfields included in the PLCB control field.

[0175] In one possible implementation, the second device can send a second code block to the first device. The second code block carries retransmission information, including: identification information of the first PLCB, indication information of the first PLCB, and reception 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 being transmitted for the Mth time, where M is a positive integer. The reception status information indicates the reception status of at least two code blocks. The first device can determine the PLCBs that failed to transmit from among the PLCBs carried in the at least two code blocks based on the retransmission information.

[0176] Optionally, the identifier of the first PLCB can be the identifier of the last PLCB that was successfully received, or the identifier of the first PLCB can be the identifier of a PLCB that was successfully received within the feedback range.

[0177] In one exemplary embodiment, the second code block can also be a PLRB. Retransmission information can be carried in the PLCB payload field of the PLRB.

[0178] As an example, the PLRB can carry retransmission information in the following form: the PLRB payload field includes a first field, a second field, and a third field, the first field indicating that the first information carries non-data information, the second field indicating that the type of non-data information is transmission acknowledgment information, and the third field carrying retransmission information.

[0179] The first field can be Figure 2 For details on the indicator bits shown, please refer to the relevant descriptions of the indicator bits mentioned above; they will not be repeated here.

[0180] The second field can be Figure 2 For details regarding the sub-indicator bits shown, please refer to the relevant descriptions of the sub-indicator bits in the explanation of the PHY code block, or refer to the relevant descriptions of the sub-indicator bits in Embodiment 1. They will not be repeated here.

[0181] The third field can be Figure 2 As shown in the content fields, in this embodiment of the application, the third field can carry retransmission information.

[0182] The following explains the format of the third field when carrying retransmission information, which can also be understood as the format of retransmission information.

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

[0184] The first subfield can be used to indicate the error feedback type, which can be either a complete error feedback or a partial error feedback. A complete error feedback indicates that the second PLCB indicates all received errors in the reception status, while a partial error feedback indicates that the second PLCB only indicates a partial received error in the reception status.

[0185] The second subfield can carry the identifier of the first PLCB.

[0186] The third subfield can carry indication information for the first PLCB.

[0187] The fourth subfield can carry the receiving status information.

[0188] To facilitate understanding, the third field carrying retransmission information is illustrated below with examples, as shown in Table 10.

[0189] Table 10

[0190]

[0191] It should be understood that Table 10 is merely an illustrative example and does not specifically limit the number of bits, values, and correspondence between the various subfields in the third field and the indicated content. Furthermore, the third field may include other subfields; however, no specific limitations are made here regarding the subfields included in the third field.

[0192] To facilitate understanding of the scheme described in Embodiment 2, specific examples will be used for illustration below.

[0193] like Figure 6 As shown, the first device sequentially sends PHY code blocks 1 to 3 to the second device. Among them, PHY code block 1 carries PLCB1 and indicates that PLCB1 is the initial transmission, PHY code block 2 carries PLCB2 and indicates that PLCB2 is the initial transmission, and PHY code block 3 carries PLCB3 and indicates that PLCB3 is the initial transmission.

[0194] After receiving PHY code blocks 1 to 3, the second device finds that PHY code block 2 is transmitted incorrectly. The second device can send ACK 1 to the first device. The ACK 1 carries the identifier of PLCB 3 and indicates that PLCB 3 is in the initial transmission and reception status information (in order: PHY code block 2 is incorrect, PHY code block 1 is correct).

[0195] After receiving ACK 1, the first device can determine PHY code block 3 for the initial transmission based on the identifier of PLCB1 and instruct PLCB. Then, taking PHY code block 3 as the last PHY code block, it counts back two code blocks, i.e. code blocks 1 to 3. Based on the received status information, it can be determined that PHY code block 2 was transmitted incorrectly and PHY code block 1 was transmitted correctly.

[0196] The first device retransmits PLCB 2, which is carried by PHY code block 2, through PHY code block 5, and indicates that PLCB 2 is the first retransmission.

[0197] After receiving PHY code blocks 4 and 5, the second device finds that PHY code block 4 is transmitted incorrectly, while PHY code block 5 is transmitted correctly. The second device can send ACK 2 to the first device, where ACK 2 carries the identifier of PLCB 2 and indicates that PLCB 2 is in the first retransmission and the reception status information (in order: PHY code block 4 error, PHY code block 3 correct, PHY code block 2 error, PHY code block 1 correct).

[0198] After receiving ACK 2, the first device can determine PHY code block 5 based on the identifier of PLCB 2 and instruct PLCB 2 to determine PHY code block 5 as the first retransmission. Then, taking PHY code block 5 as the last PHY code block, counting back 4 code blocks, namely PHY code blocks 1 to 5, the reception status of PHY code blocks 1 to 5 can be determined according to the reception status information as correct; error; correct; error; correct. Thus, the first device can determine that PHY code block 4 is transmitted incorrectly.

[0199] The first device will retransmit PLCB 3 carried by PHY code block 4.

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

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

[0202] In another implementation, the identifier of the first PLCB can be indicated by display, either as the PLCB ID carried by the last successfully received PHY code block within the feedback range, or as the PLCB ID carried by the first successfully received PHY code block within the feedback range, for example, through a field not shown in the ACK. The reception status can be anchored to the successfully received PHY code block determined by the second and third subfields, indicating the reception status of other PHY code blocks. Specifically, it can be indicated by bit mapping or other indication methods; this application embodiment does not specifically limit this.

[0203] Based on the same technical concept as the method embodiments, this application provides a data transmission apparatus. The structure of the apparatus can be as follows: Figure 7 As shown, it includes a processing unit 701 and a transceiver unit 702.

[0204] In one implementation, the data transmission device can specifically be used to implement... Figure 4 In the embodiments, the method executed by the first device can be the first device itself, or a chip or chipset within the first device, or a part of the chip used to perform the relevant method function. Specifically, the processing unit 701 is used to generate first information, which includes first PID synchronization information used for PID synchronization; the transceiver unit 702 is used to send the first information.

[0205] For example, PID synchronization includes PID count synchronization between a first device and a second device.

[0206] For example, the first information is a synchronization symbol, which includes a time base field that carries the first PID synchronization information.

[0207] For example, the synchronization symbol also includes a time base identifier field for indicating a time base number, wherein the time base identifier field indicates a first value, and the first value indicates that the time base field carries first PID synchronization information.

[0208] For example, 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.

[0209] For example, the first information is PLRB, which includes a PLCB payload field that carries first PID synchronization information.

[0210] For example, the first PID synchronization information is the PID of the first information.

[0211] For example, 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 carries the first PID synchronization information.

[0212] For example, the third field includes a first subfield that indicates that the first PID synchronization information is a PID synchronization response message.

[0213] Optionally, the transceiver unit 702 is further configured to: receive second information before the processing unit 701 generates the first information, the second information carrying second PID synchronization information, the second PID synchronization information being used to request the first PID synchronization information.

[0214] For example, the second information is PLRB, which includes the PLCB payload field; the PLCB payload field carries the second PID synchronization information.

[0215] For example, 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 carries the second PID synchronization information.

[0216] For example, the third field includes a first subfield that indicates that the second PID synchronization information is a PID synchronization request message.

[0217] For example, the third field also 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, the third subfield is used to indicate the transmission direction for PID synchronization, and the fourth subfield is used to indicate the transmission direction of the corresponding PLRB.

[0218] In another implementation, the data transmission device can specifically be used to implement... Figure 5 In the embodiments, the method executed by the first device can be the first device itself, or a chip or chipset within the first device, or a part of the chip used to perform the relevant method functions. Specifically, the processing unit 701 is used to generate at least two code blocks, each carrying a PLCB, and at least one of the at least two code blocks carries control information for the PLCB. The control information for the PLCB includes identification information and corresponding indication information, where the indication information indicates that the PLCB is being transmitted for the Nth time, and N is a positive integer. The transceiver unit 702 is used to transmit at least two code blocks.

[0219] For example, the first code block is a PLRB, which includes a PLCB control field that carries the control information of the PLCB.

[0220] Optionally, the transceiver unit 702 is further configured to: receive a second code block, the second code block carrying retransmission information, the retransmission information including: identification information of the first PLCB, indication information of the first PLCB, and reception status information, the identification information of the first PLCB being the ID of a successfully received PLCB, the indication information of the first PLCB indicating that the first PLCB is the Mth transmission, where M is a positive integer, and the reception status information indicating the reception status of at least two code blocks; the processing unit 701 is further configured to: determine, based on the retransmission information, the PLCBs among the PLCBs carried in at least two code blocks that failed to transmit.

[0221] For example, the second code block is a PLRB, which includes a PLCB payload field that carries retransmission information.

[0222] For example, 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.

[0223] For example, the third field also indicates the error feedback type, which is either a complete error feedback or a partial error feedback. A complete error feedback indicates that the reception status indicates a second PLCB with all reception errors, while a partial error feedback indicates that the reception status indicates a second PLCB with only some reception errors.

[0224] In one implementation, the data transmission device can specifically be used to implement... Figure 4 In the embodiments, the method executed by the second device can be the second device itself, or a chip or chipset within the second device, or a part of the chip that performs the relevant method function. Specifically, the transceiver unit 702 is used to receive first information, which includes first PID synchronization information used for PID synchronization; the processing unit 701 is used to perform PID synchronization based on the first PID synchronization information.

[0225] For example, PID synchronization includes PID count synchronization between a first device and a second device.

[0226] For example, the first information is a synchronization symbol, which includes a time base field that carries the first PID synchronization information.

[0227] For example, the synchronization symbol also includes a time base identifier field for indicating a time base number, wherein the time base identifier field indicates a first value, and the first value indicates that the time base field carries first PID synchronization information.

[0228] For example, 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.

[0229] For example, the first information is PLRB, which includes a PLCB payload field that carries first PID synchronization information.

[0230] For example, the first PID synchronization information is the PID of the first information.

[0231] For example, 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 carries the first PID synchronization information.

[0232] For example, the third field includes a first subfield that indicates that the first PID synchronization information is a PID synchronization response message.

[0233] Optionally, the transceiver unit 702 is further configured to: send second information before receiving the first information, the second information carrying second PID synchronization information, the second PID synchronization information being used to request the first PID synchronization information.

[0234] For example, the second information is PLRB, which includes the PLCB payload field; the PLCB payload field carries the second PID synchronization information.

[0235] For example, 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 carries the second PID synchronization information.

[0236] For example, the third field includes a first subfield that indicates that the second PID synchronization information is a PID synchronization request message.

[0237] For example, the third field 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, the third subfield is used to indicate the transmission direction for PID synchronization, and the fourth subfield is used to indicate the transmission direction of the corresponding PLRB.

[0238] In another implementation, the data transmission device can specifically be used to implement... Figure 5In the embodiments, the method executed by the second device can be the second device itself, or a chip or chipset within the second device, or a part of the chip used to perform the relevant method function. Specifically, the transceiver unit 702 is used to receive at least two code blocks, each carrying a PLCB, and at least one of the at least two code blocks carrying control information for the PLCB. The control information for the PLCB includes identification information and corresponding indication information, where the indication information indicates that the PLCB is being transmitted for the Nth time, and N is a positive integer. The processing unit 701 is used to determine the control information for at least one PLCB.

[0239] For example, the first code block is a PLRB, which includes a PLCB control field that carries the control information of the PLCB.

[0240] Optionally, the transceiver unit 702 is further configured to: send a second code block, the second code block carrying retransmission information, the retransmission information including: identification information of the first PLCB, indication information of the first PLCB, and reception status information, the identification information of the first PLCB being the ID of a successfully received PLCB, the indication information of the first PLCB indicating that the first PLCB is the Mth transmission, where M is a positive integer, and the reception status information indicating the reception status of at least two code blocks.

[0241] For example, the second code block is a PLRB, which includes a PLCB payload field that carries retransmission information.

[0242] For example, 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.

[0243] For example, the third field also indicates the error feedback type, which is either a complete error feedback or a partial error feedback. A complete error feedback indicates that the reception status indicates a second PLCB with all reception errors, while a partial error feedback indicates that the reception status indicates a second PLCB with only some reception errors.

[0244] The module division in this application embodiment is illustrative and represents only one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules. It is understood that the functions or implementations of the modules in the embodiments of this application can be further described in the relevant descriptions of the method embodiments.

[0245] In one possible approach, the data transmission device can be as follows: Figure 8 As shown, the device can be a chip in either the first or second device. The device may include a processor 801, a communication interface 802, and a memory 803. The processing unit 701 can be the processor 801. The transceiver unit 702 is the communication interface 802.

[0246] The processor 801 can be a Central Processing Unit (CPU), a digital processing unit, or something similar. The communication interface 802 can be a transceiver, an interface circuit such as a transceiver circuit, or a transceiver chip, etc. The device also includes a memory 803 for storing programs executed by the processor 801. The memory 803 can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). The memory 803 can be any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited to these.

[0247] The processor 801 is used to execute the program code stored in the memory 803, specifically to perform the actions of the processing unit 701 described above, which will not be described in detail here. The communication interface 802 is specifically used to perform the actions of the transceiver unit 702 described above, which will not be described in detail here.

[0248] This application embodiment does not limit the specific connection medium between the communication interface 802, processor 801, and memory 803. This application embodiment... Figure 8 The memory 803, processor 801, and communication interface 802 are connected via a bus 804. Figure 8 The connections between other components are shown in bold lines only and are not intended to be limiting. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, Figure 8 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0249] This application also provides a communication system, including methods for implementing... Figures 4 to 5 In the embodiments, a communication device for transmitting node functions and for implementing Figures 4 to 5 The embodiment is a communication device that receives node functions.

[0250] This application also provides a computer-readable storage medium for storing computer software instructions required to execute the processor, including a program required to execute the processor.

[0251] This application also provides a vehicle, which includes a first device and / or a second device, wherein the first device and the second device are used individually or jointly to achieve [the desired functionality]. Figure 4 or Figure 5 The data transmission method in the example. For instance, the first device and the second device can be... Figure 7 The communication device shown.

[0252] This application also provides a chip, which includes at least one processor and a communication interface. The processor is coupled to a memory and is used to read a computer program stored in the memory to execute it. Figure 4 or Figure 5 The functions described in the embodiments.

[0253] This application also provides a chip, including a communication interface and at least one processor, the processor running to execute... Figure 4 or Figure 5 The functions described in the embodiments.

[0254] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can 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.) containing computer-usable program code.

[0255] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0256] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0257] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0258] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of protection of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A data transmission method, characterized in that, The method includes: At least two code blocks are generated, each of the at least two code blocks carrying a physical layer content block (PLCB), and at least one of the at least two code blocks carries control information of the PLCB. The control information of the PLCB includes the identification information of the PLCB and corresponding indication information, wherein the indication information indicates that the PLCB is the Nth transmission, and N is a positive integer. Send the at least two code blocks.

2. The method as described in claim 1, characterized in that, The method further includes: Receive a second code block, the second code block carrying retransmission information, the retransmission information including: identification information of the first PLCB, indication information of the first PLCB, and reception status information, the identification information of the first PLCB is the identifier ID of a PLCB that has been successfully received, the indication information of the first PLCB indicates that the first PLCB is the Mth transmission, where M is a positive integer, and the reception status information indicates the reception status of the at least two code blocks. The PLCBs that failed to transmit are determined from the PLCBs carried by the at least two code blocks based on the retransmission information.

3. The method as described in claim 2, characterized in that, 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 the non-data information is transmission confirmation information, and the third field carries the retransmission information.

4. The method as described in claim 3, characterized in that, The third field also indicates the error feedback type, which is either a complete error feedback or a partial error feedback. The complete error feedback indicates that the reception status indicates a second PLCB with all reception errors, while the partial error feedback indicates that the reception status indicates a second PLCB with only some reception errors.

5. A data transmission method, characterized in that, The method includes: Receive at least two code blocks, each of the at least two code blocks carrying a physical layer content block (PLCB), and at least one of the at least two code blocks carrying control information of the PLCB, wherein the control information of the PLCB includes identification information of the PLCB and corresponding indication information, wherein the indication information indicates that the PLCB is the Nth transmission, and N is a positive integer; Determine the control information of at least one PLCB.

6. The method as described in claim 5, characterized in that, The method further includes: A second code block is sent, the second code block carrying retransmission information, the retransmission information including: identification information of the first PLCB, indication information of the first PLCB, and reception status information, the identification information of the first PLCB is the identifier ID of a PLCB that has been successfully received, the indication information of the first PLCB indicates that the first PLCB is the Mth transmission, where M is a positive integer, and the reception status information indicates the reception status of the at least two code blocks.

7. The method as described in claim 6, characterized in that, 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 the non-data information is transmission confirmation information, and the third field carries the retransmission information.

8. The method as described in claim 7, characterized in that, The third field also indicates the error feedback type, which is either a complete error feedback or a partial error feedback. The complete error feedback indicates that the reception status indicates a second PLCB with all reception errors, while the partial error feedback indicates that the reception status indicates a second PLCB with only some reception errors.

9. A data transmission device, characterized in that, The device includes: A processing unit is configured to generate at least two code blocks, each of which carries a physical layer content block (PLCB), and at least one of the at least two code blocks carries control information of the PLCB. The control information of the PLCB includes identification information of the PLCB and corresponding indication information, wherein the indication information indicates that the PLCB is the Nth transmission, and N is a positive integer. A transceiver unit is used to transmit the at least two code blocks.

10. The apparatus as claimed in claim 9, characterized in that, The transceiver unit is further configured to: Receive a second code block, the second code block carrying retransmission information, the retransmission information including: identification information of the first PLCB, indication information of the first PLCB, and reception status information, the identification information of the first PLCB is the identifier ID of a PLCB that has been successfully received, the indication information of the first PLCB indicates that the first PLCB is the Mth transmission, where M is a positive integer, and the reception status information indicates the reception status of the at least two code blocks. The processing unit is further configured to: determine, based on the retransmission information, the PLCB that failed to transmit among the PLCBs carried by the at least two code blocks.

11. The apparatus as claimed in claim 10, characterized in that, 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 the non-data information is transmission confirmation information, and the third field carries the retransmission information.

12. The apparatus as claimed in claim 11, characterized in that, The third field also indicates the error feedback type, which is either a complete error feedback or a partial error feedback. The complete error feedback indicates that the reception status indicates a second PLCB with all reception errors, while the partial error feedback indicates that the reception status indicates a second PLCB with only some reception errors.

13. A data transmission device, characterized in that, The device includes: A transceiver unit is configured to receive at least two code blocks, each of which carries a physical layer content block (PLCB), and at least one of the at least two code blocks carries control information of the PLCB. The control information of the PLCB includes identification information of the PLCB and corresponding indication information, wherein the indication information indicates that the PLCB is being transmitted for the Nth time, and N is a positive integer. A processing unit is used to determine control information for at least one PLCB.

14. The apparatus as claimed in claim 13, characterized in that, The transceiver unit is further configured to: A second code block is sent, the second code block carrying retransmission information, the retransmission information including: identification information of the first PLCB, indication information of the first PLCB, and reception status information, the identification information of the first PLCB is the identifier ID of a PLCB that has been successfully received, the indication information of the first PLCB indicates that the first PLCB is the Mth transmission, where M is a positive integer, and the reception status information indicates the reception status of the at least two code blocks.

15. The apparatus as claimed in claim 14, characterized in that, 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 the non-data information is transmission confirmation information, and the third field carries the retransmission information.

16. The apparatus as claimed in claim 15, characterized in that, The third field also indicates the error feedback type, which is either a complete error feedback or a partial error feedback. The complete error feedback indicates that the reception status indicates a second PLCB with all reception errors, while the partial error feedback indicates that the reception status indicates a second PLCB with only some reception errors.

17. A communication device, characterized in that, The device includes a processor and a communication interface, the communication interface being used to receive computer program code or instructions and transmit them to the processor; the processor executes the computer program code or instructions to cause the device to implement the method as described in any one of claims 1-4.

18. A communication device, characterized in that, The device includes a processor and a communication interface, the communication interface being used to receive computer program code or instructions and transmit them to the processor; the processor executes the computer program code or instructions to cause the device to implement the method as described in any one of claims 5-8.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a program or instructions that, when read and executed by one or more processors, implement the method of any one of claims 1-4, or, when read and executed by one or more processors, implement the method of any one of claims 5-8.

20. A vehicle, characterized in that, The vehicle includes a first device and / or a second device, the first device being configured to perform the method as described in any one of claims 1-4, and the second device being configured to perform the method as described in any one of claims 5-8.

21. A data transmission system, characterized in that, The system includes the apparatus as described in any one of claims 9-12, and the apparatus as described in any one of claims 13-16.

Images