Data transmission method, apparatus and device

Abstract

The present application relates to the technical field of communications, and discloses a data transmission method, apparatus and device. The data transmission method in embodiments of the present application comprises: a first device transmits first data and second data corresponding to each target device among at least one target device, wherein a time-frequency resource used for transmitting the first data at least partially overlaps with a time-frequency resource used for transmitting the second data corresponding to the at least one target device, and a receiving object of the first data is the at least one target device; and the first device receives feedback information sent by a second device.

Description

Data transmission methods, devices and equipment

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411213514.5, filed in China on August 30, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to a data transmission method, apparatus, and device. Background Technology

[0004] Among related technologies, Rate Splitting Multiple Access (RSMA) is a novel multiple access technology primarily used for downlink transmission. It improves transmission efficiency by superimposing two types of data streams (a common stream and a private stream). The common stream is the data stream that all receiving devices need to demodulate and decode, while the private stream is the data stream transmitted for a specific receiving device. However, this technology does not address subsequent operations after the data stream is transmitted at the sending end, resulting in lower transmission reliability. Summary of the Invention

[0005] This application provides a data transmission method, apparatus, and device that can solve the problem of low transmission reliability.

[0006] Firstly, a data transmission method is provided, the method comprising:

[0007] The first device transmits first data and second data corresponding to each of the at least one target device, wherein the time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the at least one target device at least partially overlap, the first data is received by the at least one target device, and the second data is received by the corresponding target device.

[0008] The first device receives feedback information sent by the second device, and the at least one target device includes the second device;

[0009] The feedback information includes at least one of the following:

[0010] The first data transmission confirmation information;

[0011] The first data includes transmission confirmation information for at least one target device;

[0012] The second device corresponds to the transmission confirmation information of the second data;

[0013] The first indication information is used to indicate whether the reason for the failure of the second data transmission is related to the transmission of the first data;

[0014] The transmission confirmation information for the merged data corresponding to the second device, wherein the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data.

[0015] Secondly, a data transmission method is provided, the method comprising:

[0016] The second device receives first data transmitted by the first device and second data corresponding to the second device, wherein the time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the second device at least partially overlap, and the first data is received by at least one target device, the at least one target device including the second device.

[0017] The second device sends feedback information to the first device;

[0018] The feedback information includes at least one of the following:

[0019] The first data transmission confirmation information;

[0020] The first data includes transmission confirmation information for at least one target device;

[0021] The second device corresponds to the transmission confirmation information of the second data;

[0022] The first indication information is used to indicate whether the reason for the failure of the second data transmission is related to the transmission of the first data;

[0023] The transmission confirmation information for the merged data corresponding to the second device, wherein the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data.

[0024] Thirdly, a data transmission device is provided, comprising:

[0025] A transmitting module is used to transmit first data and second data corresponding to each of at least one target device, wherein the time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the at least one target device at least partially overlap, the receiving object of the first data is the at least one target device, and the receiving object of the second data is the corresponding target device.

[0026] A receiving module is used to receive feedback information sent by a second device, wherein the at least one target device includes the second device;

[0027] The feedback information includes at least one of the following:

[0028] The first data transmission confirmation information;

[0029] The first data includes transmission confirmation information for at least one target device;

[0030] The second device corresponds to the transmission confirmation information of the second data;

[0031] The first indication information is used to indicate whether the reason for the failure of the second data transmission is related to the transmission of the first data;

[0032] The transmission confirmation information for the merged data corresponding to the second device, wherein the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data.

[0033] Fourthly, a data transmission device is provided, comprising:

[0034] A receiving module is configured to receive first data transmitted by a first device and second data corresponding to a second device, wherein the time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the second device at least partially overlap, and the receiving object of the first data is at least one target device, the at least one target device including the second device;

[0035] The sending module is used to send feedback information to the first device;

[0036] The feedback information includes at least one of the following:

[0037] The first data transmission confirmation information;

[0038] The first data includes transmission confirmation information for at least one target device;

[0039] The second device corresponds to the transmission confirmation information of the second data;

[0040] The first indication information is used to indicate whether the reason for the failure of the second data transmission is related to the transmission of the first data;

[0041] The transmission confirmation information for the merged data corresponding to the second device, wherein the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data.

[0042] Fifthly, a data transmission apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0043] In a sixth aspect, a first device is provided, the first device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0044] Seventhly, a terminal is provided, including a processor and a communication interface, wherein,

[0045] A communication interface is used to transmit first data and second data corresponding to each of at least one target device, wherein the time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the at least one target device at least partially overlap, the first data is received by the at least one target device, and the second data is received by the corresponding target device.

[0046] The communication interface is also used to receive feedback information sent by the second device, wherein the at least one target device includes the second device;

[0047] The feedback information includes at least one of the following:

[0048] The first data transmission confirmation information;

[0049] The first data includes transmission confirmation information for at least one target device;

[0050] The second device corresponds to the transmission confirmation information of the second data;

[0051] The first indication information is used to indicate whether the reason for the failure of the second data transmission is related to the transmission of the first data;

[0052] The transmission confirmation information for the merged data corresponding to the second device, wherein the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data.

[0053] In an eighth aspect, a second device is provided, the second device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0054] Ninthly, a second device is provided, including a processor and a communication interface, wherein,

[0055] A communication interface is used to receive first data transmitted by a first device and second data corresponding to a second device, wherein the time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the second device at least partially overlap, and the first data is received by at least one target device, the at least one target device including the second device.

[0056] The communication interface is also used to send feedback information to the first device;

[0057] The feedback information includes at least one of the following:

[0058] The first data transmission confirmation information;

[0059] The first data includes transmission confirmation information for at least one target device;

[0060] The second device corresponds to the transmission confirmation information of the second data;

[0061] The first indication information is used to indicate whether the reason for the failure of the second data transmission is related to the transmission of the first data;

[0062] The transmission confirmation information for the merged data corresponding to the second device, wherein the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data.

[0063] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0064] Eleventhly, a wireless communication system is provided, comprising: a first device and a second device, wherein the first device is configured to perform the steps of the method as described in the first aspect, and the second device is configured to perform the steps of the method as described in the second aspect.

[0065] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0066] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0067] In this embodiment, a first device transmits first data and second data corresponding to each of at least one target device. The time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the at least one target device at least partially overlap. The first data is received by the at least one target device, and the second data is received by the corresponding target device. The first device receives feedback information sent by a second device, where the at least one target device includes the second device. The feedback information includes at least one of the following: transmission confirmation information for the first data; transmission confirmation information for the data corresponding to at least one target device in the first data; transmission confirmation information for the second data corresponding to the second device; first indication information indicating whether the reason for the failure of the second data transmission is related to the transmission of the first data; and transmission confirmation information for merged data corresponding to the second device, where the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data. In this way, the first device can know whether the data transmission was successful through the feedback information, which can improve the transmission reliability. In addition, by transmitting the first data to at least one target device, the resource overhead caused by repeated data transmission can be reduced and the resource utilization rate can be improved. Moreover, the time and frequency resources for transmitting the first data overlap at least partially with the time and frequency resources used to transmit the second data corresponding to the at least one target device, which can further reduce the resource overhead caused by transmission and improve the resource utilization rate. Attached Figure Description

[0068] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0069] Figure 2a is a flowchart of the physical transmission channel processing of NR in a related technology;

[0070] Figure 2b is a schematic diagram of a ring cache for selecting HARQ RV bits in related technologies;

[0071] Figure 2c is a schematic diagram of the receiver operation of a HARQ in related technologies;

[0072] Figure 2d is a schematic diagram of a static codebook and a dynamic codebook in a related technology when the PDCCH is lost;

[0073] Figure 3a is one of the schematic diagrams of downlink NOMA in related technologies;

[0074] Figure 3b is a second schematic diagram of a downlink NOMA in related technologies;

[0075] Figure 3c is the third schematic diagram of a downlink NOMA in related technologies;

[0076] Figure 4 is a flowchart of one of the data transmission methods provided in an embodiment of this application;

[0077] Figure 5a is one of the schematic diagrams of data transmission provided in an embodiment of this application;

[0078] Figure 5b is a second schematic diagram of data transmission provided in an embodiment of this application;

[0079] Figure 5c is a third schematic diagram of data transmission provided in an embodiment of this application;

[0080] Figure 5d is a fourth schematic diagram of data transmission provided in an embodiment of this application;

[0081] Figure 5e is a fifth schematic diagram of data transmission provided in an embodiment of this application;

[0082] Figure 5f is a sixth schematic diagram of data transmission provided in an embodiment of this application;

[0083] Figure 5g is the seventh schematic diagram of data transmission provided in an embodiment of this application;

[0084] Figure 5h is an eighth schematic diagram of data transmission provided in an embodiment of this application;

[0085] Figure 6 is a second flowchart of a data transmission method provided in an embodiment of this application;

[0086] Figure 7 is a schematic diagram of one of the structures of a data transmission device provided in an embodiment of this application;

[0087] Figure 8 is a second schematic diagram of a data transmission device provided in an embodiment of this application;

[0088] Figure 9 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0089] Figure 10 is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0090] Figure 11 is a schematic diagram of the structure of a network-side device provided in an embodiment of this application;

[0091] Figure 12 is a second schematic diagram of the structure of a network-side device provided in an embodiment of this application. Detailed Implementation

[0092] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0093] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0094] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0095] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0096] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0097] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. The core network functions include: BSF (Block Network Function), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), and Network Data Analytics Function (NWDAF). It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

[0098] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0099] For ease of understanding, the following explains some aspects of the embodiments of this application:

[0100] 1. NR physical transmission channel processing and Hybrid Automatic Repeat Request (HARQ) related processing

[0101] In the NR standard, the physical layer provides physical channel transmission services to the Medium Access Control (MAC) layer. The MAC layer delivers data to the physical layer in units of transport blocks (TBs), and the physical layer converts the received transport blocks into air interface signals and transmits them to the other end. The downlink physical channels defined by NR include: downlink shared channel, paging channel, and broadcast channel; the uplink physical channels include: uplink shared channel.

[0102] Figure 2a illustrates the specific processing flow of the physical layer for the above-mentioned channels, including the process from the MAC layer transport block to the final air interface signal, including the following processes:

[0103] (1) Add Cyclic Redundancy Check (CRC): Add CRC to the TB to verify the correctness of the TB. If the TB is long, it will be divided into multiple code blocks (CB). For ease of description, TB can also refer to CB.

[0104] (2) Channel Coding: Based on the code rate indicated by the MCS, channel coding is performed on TB+CRC, such as Low Density Parity Check (LDPC) or Polar Code. The bits after channel coding include two types: systematic bits and parity check bits. Among them, systematic bits are the original bits to be transmitted (including the CRC bits of TB), while parity check bits are redundant bits used to recover the systematic bits. Generally speaking, systematic bits are more important than parity check bits.

[0105] (3a) Rate matching: The data obtained after channel coding is processed in order to meet the code rate requirements of the modulation and coding scheme (MCS) and to meet the availability of physical resources. Specific operations of rate matching include puncturing, shortening, lengthening, etc.

[0106] (3b) HARQ: Rate-matched data is placed in a circular buffer, as shown in Figure 2b. The buffer has four starting bit positions, corresponding to four HARQ Redundancy Versions (RVs). During transmission, a specified number of bits are read from the corresponding position according to the required RV version number. It can be seen that RV0 and RV3 both contain system bits. During transmission, the sender first sends RV0. If decoding fails, it sends a feedback message to the sender, indicating that the next RV data needs to be transmitted. Generally, the order of RVs sent by the sender is 0, 2, 3, 1.

[0107] (3c) Interleaving: After selecting HARQ RV, the sender will also interleave the data, which is usually a row-by-row interleaving.

[0108] (4) Scrambling: In order to reduce interference between users and between cells, the transmitting end will further scramble the interleaved data, that is, perform bit-level multiplication with a scrambling sequence. Usually, this scrambling sequence is a pseudo-random sequence, and the generation of the sequence is related to the terminal's identifier (such as Cell Radio Network Temporary Identifier (C-RNTI)).

[0109] (5) Modulation: According to the MCS instruction, the transmitter will divide the scrambled data into units of modulation order. For example, Quadrature Phase Shift Keying (QPSK) corresponds to 2 bits, so the transmitter will map every 2 bits to 1 QPSK symbol.

[0110] (6) and (8) layer mapping and multi-antenna coding: applicable to multi-antenna multi-stream transmission, mapping the symbols to be transmitted to a "layer". Inter-layer signals may reuse the same physical resources, and the role of multi-antenna coding is to use the differences in the channel to suppress inter-layer interference.

[0111] (7) Discrete Fourier Transform (DFT) Precoding: For uplink transmission, the transmitter can choose to use DFT-extended Orthogonal Frequency Division Multiplexing (OFDM) (DFT-S-OFDM) to reduce the peak to average power ratio (PAPR).

[0112] (9) Resource mapping: Based on the available physical resources (OFDM symbols, subcarriers) of the physical channel, the modulated symbols are mapped to the corresponding physical resources.

[0113] (10) Inverse Fast Fourier Transform (IFFT): Using OFDM symbols as units, perform IFFT operation on the subcarriers of the corresponding symbols to obtain the baseband OFDM signal to be transmitted.

[0114] (11) Physical antenna mapping: The baseband OFDM signal is delivered to the corresponding radio frequency front end for transmission, including digital to analog converter (DAC), up-conversion and other operations.

[0115] For the receiving end, the operation is basically the reverse of the steps shown in Figure 2a. The received signal from the air interface is subjected to a fast Fourier transform (FFT), layer mapping, demodulation, descrambling, and deinterleaving to obtain the soft bit information (such as the log-likelihood ratio (LLR)) for each bit on the TB. The LLR is then passed to the channel decoder for decoding. A key step in this process is the processing of HARQ.

[0116] As shown in Figure 2c, assuming a TB (Data Trace) has 3 bits including the CRC (Corrective Cycle), it becomes 6 bits after channel coding. The first 3 bits are system bits, and the last 3 bits are check bits. An RV (Record Value) contains 4 bits. The receiver first receives the data from RV0. After demodulation, descrambling, and deinterleaving, it obtains the LLR (Local Level Retrieval) of the first 4 bits. At this point, the receiver does not have the last 2 check bits, so it needs to fill them with a pre-defined value (usually 0). Then, the 6-bit LLR is sent to the channel decoder to obtain an estimate of the 3 system bits. According to the CRC rules, a CRC check is performed on these three bits. If it passes, these 3 bits are submitted to the MAC layer as the data value of the TB.

[0117] Another possibility is that these three system bits fail the CRC check. In this case, the receiver will send a feedback message to the sender, instructing the sender to continue transmitting the next RV. Assume the next transmitted RV is RV2, which contains the last four bits. It can be seen that the third and fourth bits overlap with RV0. Therefore, the receiver will combine the LLR of RV2 and the LLR of RV0 according to certain rules, resulting in a new LLR for the third and fourth bits. Simultaneously, the receiver also obtains the LLRs of the fifth and sixth bits. Next, the receiver sends these six LLRs to the channel decoder to obtain a new estimate of the three system bits. Similarly, a CRC check is performed on these three bits. If it passes, these three bits are submitted to the MAC layer as the data value for this TB; otherwise, the sender is instructed to transmit the next RV, repeating the above steps until the CRC check passes or the retransmission limit is exceeded.

[0118] 2. NR's HARQ codebook design

[0119] The NR defines the HARQ feedback codebook that the User Equipment (UE) sends back to the gNB during downlink transmission. As shown in Figure 2d, HARQ feedback can be transmitted in the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH), with timing satisfying the agreed-upon K1 time slot interval between the Physical Downlink Shared Channel (PDSCH) and the feedback time slot. In other words, the HARQ feedback corresponding to a specific PDSCH is transmitted within K1 time slots after the scheduled time slot of the corresponding Physical Downlink Control Channel (PDCCH).

[0120] HARQ feedback uses one bit to represent an acknowledgment (ACK) or a negative acknowledgment (NACK), indicating whether the corresponding PDSCH transport block (TB) was successfully received and decoded. It should be noted that for longer TBs, the gNB can also instruct HARQ feedback at a finer granular level, using one bit to characterize whether the corresponding CBG was successfully received and decoded. If the PDCCH schedules a PDSCH transport greater than one TB, feedback will be sent for each TB (and its CBG). A PDCCH may schedule more than one PDSCH and more than one carrier (e.g., during carrier aggregation), in which case the above feedback operation needs to be repeated for each carrier and each PDSCH.

[0121] The protocol defines two types of HARQ feedback codebooks: Type 1 (semi-static) and Type 2 (dynamic). Type 1 codebooks are based on the maximum number of bits required for feedback within each time slot. Only successfully received Carriers, PDSCHs, TBs, and CBGs are set to ACK; all others are set to NACK. For example, in a HARQ feedback time slot, based on the received PDCCH (which has a Downlink Assignment Index (DAI) counter, indicating the sequence number of the currently scheduled PDSCH; missing PDCCHs and their number can be detected if the cDAI is discontinuous) and the timing relationship indicated therein, it is determined that this time slot may correspond to a maximum of 3 opportunities to transmit PDSCHs. If there are 2 Carriers, each PDSCH can transmit two TBs, and each TB can be divided into 2 CBGs. Therefore, each HARQ feedback codebook needs to contain 3*2*2*(1+2) bits. Here, 3 refers to the opportunity to transmit PDSCH, 1 in parentheses refers to TB-level ACK / NACK, and 2 in parentheses refers to CBG-level ACK / NACK.

[0122] Type I codebooks reserve HARQ feedback resources for the TB and CBG corresponding to all possible PDSCH transmission opportunities. The advantage is that it avoids potential misunderstandings between the gNB and UE regarding the HARQ codebook due to a missed PDCCH detection. However, it incurs significant overhead, especially since feedback bits are reserved for PDSCHs that are not scheduled at all. Therefore, Type 2 codebooks reduce feedback overhead by dynamically adjusting the codebook size.

[0123] Unlike the Type 1 codebook, the Type 2 codebook only performs HARQ feedback for scheduled PDSCHs. Its drawback is that if the UE misses a PDCCH, it will not generate the corresponding PDSCH HARQ feedback, leading to inconsistencies between the gNB and the UE's understanding of the codebook. To prevent this problem, the Type 2 codebook introduces a total DAI (tDAI) count value to indicate the number of PDCCHs that have been scheduled so far. It can be used in conjunction with cDAI to identify missed PDSCHs and their locations, allowing the UE to fill in the corresponding NACK bits.

[0124] 3. Rate Splitting Multiple Access (RSMA)

[0125] The basic idea of ​​rate splitting is to split the messages sent to different receivers at the transmitter into two parts, called the dedicated part (dedicated data stream) and the common part (common data stream). Then, all the common parts are merged into a single unit and multiplexed using downlink non-orthogonal multiple access technology, namely Multiuser Superposition Transmission (MUST). This is achieved by designing a composite constellation and allocating constellation points and bits to different users. Next, similar to traditional Multi-User MIMO (Multi-Input Multi-Output) multi-stream transmission, the common data stream and multiple dedicated data streams are transmitted using different precoding and DMRS resources within the same time-frequency resources. At the receiver, each user, in addition to decoding their own dedicated data stream, also needs to decode the common data stream, and then merge their two parts into a complete data stream. It should be noted that the receiver may need to decode information sent to other users and perform interference removal when decoding the common data stream.

[0126] Data multiplexing is equivalent to the MUST technique when all data is transmitted using a public data stream. When all data uses a private data stream, data multiplexing is equivalent to the MU-MIMO method. Therefore, to a certain extent, RSMA is a combination of the MUST and MU-MIMO methods.

[0127] 4. Downlink Non-Orthogonal Multiple Access Technology

[0128] The main idea of ​​downlink non-orthogonal multiple access (NOMA) is to use superposition coding and successive interference cancellation (SIC) to carry information of multiple users on the same resource element (RE).

[0129] The following lists three overlay encoding methods: Cat 1, Cat 2, and Cat 3. Cat 1 and Cat 2 combine multiple sub-constellations into a composite constellation, while Cat 3 directly allocates different bits to different users based on a composite constellation.

[0130] Cat1: Different sub-constellations are superimposed with an adaptive power ratio, and the mapping between the composite constellation points and bits does not conform to the Gray mapping criterion. Taking Figure 3a as an example, this is a composite constellation formed by superimposing two sub-constellations of size 4. The constellation point of the first sub-constellation is actually the center point of the clusters distributed in the four quadrants of the composite constellation. For example, the four points located in the first quadrant, although with different specific values, all represent the bit "00". The constellation point of the second sub-constellation is the constellation point of each cluster in the composite constellation. For example, the last two bits of the first constellation point located in each quadrant all represent the bit "10".

[0131] Cat2: Different sub-constellations are superimposed with an adaptive power ratio, and the mapping between points and bits in the composite constellation conforms to the Gray mapping criterion. Figure 3b is an example of a composite constellation formed by superimposing two sub-constellations of size 4 that conform to the Gray mapping criterion. Similar to Figure 3a, only the bit mapping rules are slightly different.

[0132] For Cat1 and Cat2, the composite constellation they transmit is derived from the superposition of sub-constellations, and the variable controlling how the sub-constellations are superimposed is the power ratio. For the two-user case, the transmission steps at the transmitting end are as follows: The transmitting end first determines the constellation point to be transmitted based on the information bits of the first user, and then multiplies that constellation point by the power ratio. Where α is the power ratio of the second user; then, the transmitter determines the constellation point to be transmitted based on the information bits of the second user, and then multiplies that constellation point by the power ratio. Finally, the two constellation points are vector-summed to obtain the final composite constellation point for transmission. At the receiving end, the first user only needs to determine which quadrant the constellation point is located in to obtain the required bits, while the second user needs to determine not only which quadrant the constellation point is in, but also its specific position within the quadrant. In other words, the first user only needs to demodulate 2 bits; while the second user actually needs to demodulate 4 bits and then take the last 2 bits.

[0133] Cat3: Directly divide the constellation point that conforms to the Gray mapping rule into bits. As shown in Figure 3c, the entire constellation diagram conforms to the Gray mapping rule. Then, it is agreed that the first 2 bits are the bits of the first user, and the last 2 bits are the bits of the second user.

[0134] As can be seen, the sub-constellations of Cat1 and Cat2 can be different, and the composite constellation formed by superposition may be irregular. Cat3 first defines a regular composite constellation and then divides the bits.

[0135] For downlink NOMA, fully utilizing the channel conditions of different users is key to improving overall spectral efficiency. For example, for users with poor channel conditions, such as those far from the transmitter, the resolution of constellation points is poor. They can only distinguish constellation points with large Euclidean distances, such as those in different quadrants, but cannot accurately determine constellation points within the same quadrant. On the other hand, for users with good channel conditions, such as those close to the transmitter, the resolution of constellation points is good, and they can make accurate decisions even for constellation points with small Euclidean distances. In this case, it is equivalent to being able to decode all the bits transmitted by the transmitter and then extract the bits of interest. In practical applications, directly determining composite constellation points to obtain all bits and then extracting a portion of the bits is a computationally complex method. A less complex method is SIC: first determine the sub-constellation points with large Euclidean distances (i.e., the constellation points transmitted to distant users), then remove these sub-constellation points from the received signal (vector difference), and then determine the sub-constellation points with smaller Euclidean distances.

[0136] The data transmission method, apparatus, and related equipment provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0137] Referring to Figure 4, which is a flowchart of a data transmission method provided in an embodiment of this application, the data transmission method includes the following steps:

[0138] Step 101: The first device transmits first data and second data corresponding to each of the at least one target device, wherein the time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the at least one target device at least partially overlap, the first data is received by the at least one target device, and the second data is received by the corresponding target device.

[0139] Step 102: The first device receives feedback information sent by the second device, wherein the at least one target device includes the second device;

[0140] The feedback information includes at least one of the following:

[0141] The first data transmission confirmation information;

[0142] The first data includes transmission confirmation information for at least one target device;

[0143] The second device corresponds to the transmission confirmation information of the second data;

[0144] The first indication information is used to indicate whether the reason for the failure of the second data transmission is related to the transmission of the first data;

[0145] The transmission confirmation information for the merged data corresponding to the second device, wherein the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data.

[0146] The first device can be the data sender, and can be a UE, base station, relay, TRP, or other devices. There can be one or more first devices. In the case of multiple devices, it includes, but is not limited to, scenarios such as Single Frequency Network (SFN), Coherent Joint Transmission (CJT), Non-Coherent Joint Transmission (NCJT), and Cell Free.

[0147] The second device can serve as a data receiver and can be a UE, base station, relay, TRP, or other devices. There can be one or more second devices, but usually there are more.

[0148] In addition, the time-frequency resources for the transmission of the first data and the second data at least partially overlap, wherein the target receiving device for the first data includes at least one target device, and the target receiving device for the second data is one target device; the first data may be one or more; the second data may be one or more.

[0149] It is understood that the first data and the second data in the embodiments of this application can be defined from the perspective of "data stream," that is, two data streams that can carry data. In actual transmission, the data in the data stream needs to form various data packets (such as TB at the Medium Access Control (MAC) layer), or codewords (CW) that can be transmitted at the physical layer, or physical transmission channels (such as PDSCH, PUSCH, etc.). The first data can be data in a public stream (or described as a public data stream), and the second data can be data in a private stream (or described as a private data stream).

[0150] The second data corresponding to the target device can refer to second data received by the target device. For example, the second data corresponding to the second device can refer to second data received by the second device. The data corresponding to the target device in the first data can be understood or replaced with data belonging to the target device in the first data. For example, the data corresponding to the second device in the first data can be understood or replaced with data belonging to the second device in the first data.

[0151] In one embodiment, the first device transmits first data and second data corresponding to each of the at least one target device, including: the first device transmits the first data using a public stream of RSMA, and transmits the corresponding second data to the at least one target device using a private stream of RSMA.

[0152] The transmission confirmation information of the first data may include: ACK or NACK for the entire first data; and / or ACK or NACK for the sub-data groups after the entire first data has been split.

[0153] The transmission confirmation information for at least one target device in the first data may include: ACK or NACK for data belonging to at least one target device in the first data; and / or ACK or NACK for a sub-data group belonging to at least one target device in the first data; and / or ACK or NACK for data belonging to at least one target device and its sub-data group in the first data.

[0154] In one embodiment, the transmission confirmation information for data corresponding to at least one target device in the first data may include: transmission confirmation information for data corresponding to a second device in the first data.

[0155] The transmission confirmation information for the second data corresponding to the second device may include: ACK or NACK for the second data.

[0156] The first indication information can be used to indicate whether the reason for the failure of the second data transmission is the failure of the first data transmission.

[0157] The transmission confirmation information for the merged data corresponding to the second device may include: ACK or NACK for the data belonging to the second device after merging the first data and the second data.

[0158] Understandably, RSMA is a novel multiple access technology primarily used for downlink transmission. It improves transmission efficiency by superimposing two types of data streams (a common stream and a private stream), achieving better performance than simply using MUST and MU-MIMO. Specifically, the common stream is the data stream that all receiving devices need to demodulate and decode, while the private stream is the data stream transmitted for a specific receiving device. After decoding the common stream, the receiver performs interference removal and demodulates the private stream. By flexibly utilizing both data streams, the common stream can compensate for the performance loss of MU-MIMO when the transmitter's Channel State Information (CSI) is imperfect or the receiving device's channel isolation is poor.

[0159] However, RSMA works on the premise that the common stream can be successfully transmitted or that the transmission quality of the common stream is high. If the transmission of the common stream fails or the reception quality is poor, it may in turn affect the reception of the private stream, and the performance may be worse than using MU-MIMO or MUST for transmission alone.

[0160] This application proposes a data transmission method that can improve the reliability of RSMA transmission. By receiving feedback information sent by a second device through a first device, the transmission reliability of the common stream can be improved, thereby improving the transmission reliability of RSMA.

[0161] In this embodiment, a first device transmits first data and second data corresponding to each of at least one target device. The time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the at least one target device at least partially overlap. The first data is received by the at least one target device, and the second data is received by the corresponding target device. The first device receives feedback information sent by a second device, where the at least one target device includes the second device. The feedback information includes at least one of the following: transmission confirmation information for the first data; transmission confirmation information for the data corresponding to at least one target device in the first data; transmission confirmation information for the second data corresponding to the second device; first indication information indicating whether the reason for the failure of the second data transmission is related to the transmission of the first data; and transmission confirmation information for merged data corresponding to the second device, where the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data. In this way, the first device can know whether the data transmission was successful through the feedback information, which can improve the transmission reliability. In addition, by transmitting the first data to at least one target device, the resource overhead caused by repeated data transmission can be reduced and the resource utilization rate can be improved. Moreover, the time and frequency resources for transmitting the first data overlap at least partially with the time and frequency resources used to transmit the second data corresponding to the at least one target device, which can further reduce the resource overhead caused by transmission and improve the resource utilization rate.

[0162] Optionally, the first device transmits first data, including:

[0163] The first device performs target processing on the first data to obtain the first data to be transmitted; or, the first device adds verification information to the information to be transmitted corresponding to the target device, and generates the first data to be transmitted based on the information to be transmitted after adding the verification information.

[0164] The first device transmits the first data to be transmitted;

[0165] The target processing includes at least one of the following:

[0166] Add the verification information corresponding to each target device to the data corresponding to each target device in the first data respectively;

[0167] Add verification information to the first data;

[0168] The first data is channel coded.

[0169] The verification information may include a Cyclic Redundancy Check (CRC) code.

[0170] In one implementation, adding the verification information corresponding to each target device to the data corresponding to each target device in the first data may include: adding CRC separately to the data belonging to different target devices on a per-target-device basis.

[0171] In one implementation, adding verification information to the first data may include: concatenating the data belonging to each target device in the first data together, then adding a CRC to all the data as a whole, and concatenating it at the end of the data.

[0172] In one embodiment, adding verification information to the information to be transmitted corresponding to the target device, and generating first data to be transmitted based on the information to be transmitted after adding the verification information, may include: before generating the first data and the second data, adding a CRC to the information to be transmitted corresponding to the target device (i.e., data belonging to the target device), and generating the first data to be transmitted based on the information to be transmitted after adding the CRC.

[0173] The information to be transmitted corresponding to the target device may include the data corresponding to the target device in the first data, and the second data corresponding to the target device. The information to be transmitted can be any information that needs to be transmitted; for example, the information to be transmitted can be semantic data of semantic communication.

[0174] In one implementation, channel coding of the first data may include: using the first data as input for channel coding, and using the channel-coded data as data with added CRC, without adding additional CRC.

[0175] In this embodiment, the first device performs target processing on the first data to obtain first data to be transmitted; or, the first device adds verification information to the information to be transmitted corresponding to the target device, and generates the first data to be transmitted based on the information to be transmitted after adding the verification information; the first device then transmits the first data to be transmitted. Through the above operations, verification can be added to the first data, thereby improving transmission reliability.

[0176] Optionally, the first device transmits the first data to be transmitted, including:

[0177] The first device performs channel coding on the data corresponding to each target device in the first data to be transmitted, or the first device performs channel coding on the first data to be transmitted.

[0178] The first device generates codewords based on the channel coding results and transmits the codewords.

[0179] The first device performs channel coding on the data corresponding to each target device in the first data to be transmitted, which may include: performing channel coding separately on each target device, on a unit basis, on the data belonging to different target devices in the first data to be transmitted (and CRC).

[0180] The first device performs channel coding on the first data to be transmitted, which may include: performing channel coding on the data (and their CRC) belonging to all target devices in the first data to be transmitted as a whole.

[0181] In one embodiment, the first device adds verification information corresponding to each target device to the data corresponding to each target device in the first data to obtain the first data to be transmitted; the first device performs channel coding on the data corresponding to each target device in the first data to be transmitted, or the first device performs channel coding on the first data to be transmitted.

[0182] In one embodiment, a first device adds verification information to the first data to obtain the first data to be transmitted; the first device performs channel coding on the data corresponding to each target device in the first data to be transmitted, or the first device performs channel coding on the first data to be transmitted.

[0183] Optionally, the step of performing channel coding on the data corresponding to each target device in the first data to be transmitted includes:

[0184] The data corresponding to each target device in the first data to be transmitted is divided into data groups corresponding to each device;

[0185] If the bit sequence length of a target data group is greater than the channel coding limit length, the target data group is divided into multiple sub-data groups;

[0186] Channel coding is performed on the divided data groups.

[0187] In this process, after dividing the target data group into multiple sub-data groups, a CRC belonging to that data group can be added separately to each sub-data group.

[0188] For example, payload1, payload2, ..., etc. can be data corresponding to different target devices. Payload1+CRC1, Payload2+CRC2, ..., etc. can be regarded as multiple different data groups, such as data group 1, data group 2, ..., etc.

[0189] Bit sequences belonging to different data groups can be channel-coded separately to obtain encoded bit sequences CB1, CB2, ..., etc., corresponding to data group 1, data group 2, ..., etc.

[0190] In one implementation, each data group can be interleaved separately before channel coding. The interleaving can employ row-to-row, column-to-row, or other predefined or configured interleavers.

[0191] In this embodiment, by dividing the data group according to the target device; when the bit sequence length of the target data group is greater than the channel coding limit length, the target data group is divided into multiple sub-data groups, and channel coding is performed on the divided data groups, it is possible to achieve channel coding of data belonging to different target devices separately on a target device-by-target basis.

[0192] Optionally, the generation of codewords based on the channel coding result includes any one of the following:

[0193] The code blocks obtained from channel coding are concatenated to form codewords;

[0194] Based on the bit quantity limit of the physical layer, bits are selected from the code block obtained by channel coding and concatenated to form codewords;

[0195] The code blocks obtained by channel coding are concatenated to obtain a bit sequence. According to the bit quantity limit of the physical layer, bits are selected from the bit sequence for concatenation to form a codeword.

[0196] Bits can be selected using a circular buffer. The start and end positions of the bits selected from the buffer can be determined based on the current HARQ RV and / or physical layer transmission limitations (such as the amount of available transmission resources or the highest modulation and coding scheme (MCS) level). There is no restriction on how bits are selected here.

[0197] In one implementation, data interleaving can be performed after channel coding or before codeword formation, including: interleaving bits belonging to different data groups separately, or interleaving bits belonging to multiple data groups after concatenation before codeword formation.

[0198] In this implementation, code blocks obtained from channel coding are concatenated to form codewords; according to the bit quantity limit of the physical layer, bits are selected from the code blocks obtained from channel coding and concatenated to form codewords; the code blocks obtained from channel coding are concatenated to obtain a bit sequence, and according to the bit quantity limit of the physical layer, bits are selected from the bit sequence and concatenated to form codewords. This enables codeword generation.

[0199] Optionally, the first device transmits first data, including:

[0200] The first device generates a transport block TB corresponding to the first data, the TB including multiple sub-data blocks, each sub-data block corresponding to a target device;

[0201] The first device generates codewords based on the TB and transmits the codewords.

[0202] In one implementation, when generating the TB corresponding to the first data, if the TB length (e.g., length X) plus the TB's CRC (e.g., length L1) exceeds the channel coding limit (e.g., length A), then the TB is divided into multiple sub-data blocks and channel-coded separately to generate multiple codeblocks. Before generating codeblocks, a CRC (e.g., length L2) is appended to the end of each sub-data block. The length of the sub-data block after adding the CRC is A. For the last sub-data block, if the length after adding the CRC is not equal to A, then redundant bits are padded. <null>Until the length is A.

[0203] The target length of each sub-data block is A-L2; at least one sub-data block has a target length of A-L2-L1; when the target length of each sub-data block is greater than the length of the data to be carried, for example when the data of the target device is less than the target length A-L2, agreed bits or indicated bits can be filled into the data until the total length of the data plus the filling bits is the target length; the total length of the first data TB is an integer multiple of A.

[0204] In this embodiment, the first device generates a TB corresponding to the first data, the TB comprising multiple sub-data blocks, each sub-data block corresponding to a target device; the first device generates codewords based on the TB and transmits the codewords. This enables the merging of data belonging to multiple target devices into one TB, and ensures that each sub-data block after the TB is divided corresponds to data belonging to a target device.

[0205] Optionally, the first device generates the TB corresponding to the first data, including:

[0206] The first device generates multiple sub-data blocks, each of which carries data corresponding to a target device in the first data;

[0207] The first device concatenates the multiple sub-data blocks to obtain the TB corresponding to the first data.

[0208] Optionally, the method further includes:

[0209] The first device sends a second instruction message to the at least one target device;

[0210] The second indication information is used to indicate data-related information of the first data.

[0211] In one implementation, the data-related information of the first data may include at least one of the following:

[0212] The total size of the first data, such as the number of bits or bytes;

[0213] The length of the first data sub-data block, such as the number of bits or bytes;

[0214] The length of each codeblock after the first data is channel-coded, such as the number of bits or bytes;

[0215] The HARQ RV of the sub-data blocks belonging to each target device in the first data, or the HARQ RV of each codeblock;

[0216] The overall RV of the first data set;

[0217] The first data sub-data blocks or codeblocks correspond to each target device, wherein one target device can correspond to multiple sub-data blocks or corresponding codeblocks.

[0218] In one implementation, the first device may send a second indication message to the at least one target device before the first device generates the transport block TB corresponding to the first data.

[0219] In this embodiment, the first device sends a second instruction information to the at least one target device, so that the target device can receive the first data based on the second instruction information.

[0220] Optionally, the first data is the first data retransmitted; or,

[0221] The first data includes retransmitted data; or,

[0222] The second data includes at least a portion of the retransmitted first data.

[0223] In one implementation, the first data is the retransmitted first data, so the first device achieves the retransmission of the first data by directly retransmitting all the first data.

[0224] In one implementation, the first data includes retransmitted data, thereby enabling the first device to retransmit at least a portion of the first data that needs to be retransmitted as at least a portion of the new first data.

[0225] In one implementation, the second data includes at least a portion of the first data that needs to be retransmitted, so that the first device sends the at least portion of the first data that needs to be retransmitted as at least a portion of the new second data to the second device that responded with a NACK to the first data, thereby realizing the retransmission of the first data.

[0226] Optionally, if the first data is retransmitted first data, the method further includes at least one of the following:

[0227] The first device sends first information to the second device;

[0228] The first device sends the second information to the second device;

[0229] The first information includes at least one of the following:

[0230] The retransmission or initial transmission indication of the first data; the signal format of the retransmitted first data; the data-related information of the retransmitted first data; the resources of the retransmitted first data; and the identifier of the target device for receiving the retransmitted first data.

[0231] The second information includes at least one of the following:

[0232] The signal format of the first retransmitted data; the resources of the first retransmitted data; the resources of the second data; the signal format of the second data; and the identifier of the target device for receiving the second data.

[0233] The signal format of the first retransmitted data may include CP, frame structure, MCS and / or waveform, etc.

[0234] The retransmission or initial transmission indication of the first data is used to indicate whether the first data is retransmitted or initially transmitted. For example, when the retransmission or initial transmission indication is 1, it indicates that the first data is retransmitted; when the retransmission or initial transmission indication is 0, it indicates that the first data is initially transmitted; and vice versa. In the case where the first data is retransmitted, the retransmission or initial transmission indication can indicate that the first data is retransmitted.

[0235] In this embodiment, the first device sends first information to the second device, thereby enabling the first device to schedule the retransmission of first data through the first information; and / or, the first device sends second information to the second device, thereby enabling the first device to schedule the second data to be sent simultaneously with the retransmission of the first data through the second information.

[0236] Optionally, if the first data includes retransmitted data, the method further includes at least one of the following:

[0237] The first device sends a third message to the second device;

[0238] The first device sends a fourth message to the second device;

[0239] The third information includes at least one of the following:

[0240] The first data includes: a retransmission or initial transmission indication of some data in the first data; the signal format of the first data; data-related information of the first data; resources of the first data; an identifier of the receiving object used to receive retransmitted data in the first data; an identifier of the receiving object used to receive newly transmitted data in the first data; and an identifier of the receiving object used to receive the first data.

[0241] The fourth piece of information includes at least one of the following:

[0242] The signal format of the first data; resources for retransmitted data; resources for the second data; the signal format of the second data; the identifier of the target device for receiving the second data.

[0243] The identifier of the receiving object used to receive retransmitted data in the first data can refer to the identifier (ID) of a second device or a list of devices receiving the retransmitted portion of the first data. The identifier of the receiving object used to receive newly transmitted data in the first data can refer to the ID of a second device or a list of devices receiving the newly transmitted data in the first data. The identifier of the receiving object used to receive the first data can refer to the ID of a second device or a list of devices receiving the first data.

[0244] In this embodiment, the first device sends a third message to the second device, thereby enabling the first device to schedule the retransmission of a portion of the first data through the third message; and / or, the first device sends a fourth message to the second device, thereby enabling the first device to schedule the second data to be sent simultaneously with the first data through the fourth message.

[0245] Optionally, if the second data includes at least a portion of the retransmitted first data, the method further includes:

[0246] The first device sends the fifth message to the second device;

[0247] The fifth piece of information includes at least one of the following:

[0248] The signal format of the first data; the resources of the first data; the signal format of the second data; the resources of the second data; the relevant information of the retransmitted data carried by the second data;

[0249] The retransmission data carried by the second data carrier includes at least one of the following:

[0250] Data-related information of the retransmitted data; location information of the retransmitted data within the second data; relationship between the retransmitted data and its parent first data.

[0251] Wherein, the signal format of the first data in the fifth information can refer to the signal format of the first data transmitted simultaneously with the second data. The resources of the first data can refer to the resources of the first data transmitted simultaneously with the second data. The retransmitted data carried by the second data can refer to the retransmitted data of the first data carried by the second data. The relationship between the retransmitted data and the first data to which it belongs can refer to the relationship between the retransmitted data and the retransmitted first data, such as indicating that the current retransmitted data is the Xth part of the retransmitted first data, or data belonging to the Xth target device.

[0252] In one embodiment, the data-related information of the retransmitted data may include at least one of the following: the total size of the retransmitted data, the CRC format of the retransmitted data as a whole, the size of the data belonging to each target device in the retransmitted data, the CRC format of the data belonging to each target device in the retransmitted data, the HARQ RV of the data belonging to each target device in the retransmitted data, and the RV of the retransmitted data as a whole.

[0253] In this embodiment, the first device sends fifth information to the second device, thereby enabling the first device to schedule the transmission of second data containing first data retransmission data through the fifth information.

[0254] Optionally, the data-related information includes at least one of the following:

[0255] The size of the first data; the format information of the verification information of the first data; the size of the data corresponding to each target device in the first data; the length of the sub-data block or code block corresponding to the first data; the format information of the verification information of the data corresponding to each target device in the first data; the redundancy version (RV) of the data corresponding to each target device in the first data; the RV of the first data; the correspondence between the sub-data block or code block corresponding to the first data and the target device.

[0256] Optionally, the method further includes at least one of the following:

[0257] The first device sends a first configuration to the second device, the first configuration being used to configure at least one of the resources, location and number of times the first data is repeatedly transmitted;

[0258] The first device sends a second configuration to the second device, the second configuration being configured to schedule the transmission of second data simultaneously in the event of repeated transmission of the first data.

[0259] The first configuration may include at least one of the following: resources for repeatedly transmitted first data, such as the number of repetitions, the transmission resources for each repetition, or the resources occupied by periodically occurring transmission opportunities. The first configuration may also include first information.

[0260] The second configuration may include second information, which may be a separate indication for each different repetition or a unified indication for all repetitions, for example:

[0261] If each different repetition is indicated separately, then multiple second pieces of information need to be indicated;

[0262] If a uniform instruction is provided for all repetitions, then the following can be indicated:

[0263] Case 1: Each item in the second information contains multiple values, and each value corresponds to one or more repetitions that are applied.

[0264] Case 2: Each item in the second information is a periodic configuration, corresponding to the periodic transmission opportunities of repetition.

[0265] In this embodiment, the first device sends a first configuration to the second device, and / or the first device sends a second configuration to the second device, which can realize the repetition of the first data, thereby improving the transmission reliability.

[0266] The following examples will provide further explanation:

[0267] This includes the following aspects:

[0268] When the first device sends the first data, the method of adding CRC includes at least one of the following methods:

[0269] Alt1: Add CRC to data belonging to different target devices on a per-target-device basis;

[0270] Alt2: Take the first data as a whole and add a CRC to the data belonging to all target devices;

[0271] Alt3: Add a CRC to the data belonging to the target device before generating the first and second data;

[0272] Alt4: Uses channel coding to provide verification functionality without adding an additional CRC.

[0273] When the first device sends the first data, the method for generating the CW includes at least one of the following methods:

[0274] Alt1: For each target device, the data and CRC belonging to different target devices are channel encoded separately, and the multiple encoded data are concatenated into CW;

[0275] Alt2: Channel-encode the data belonging to all target devices and their CRC as a whole, as CW;

[0276] Alt3: Generate CW using the existing CW generation mechanism.

[0277] The CRC verification method for the second device when receiving the first data and / or the second data includes at least one of the following methods:

[0278] Alt1: Verify the CRC of the first data that belongs to at least one target device data;

[0279] Alt2: Verify the CRC of the first set of data;

[0280] Alt3: Verify the CRC of the second data;

[0281] Alt4: After merging the first and second data belonging to the second device, verify the CRC of the merged data.

[0282] The second device generates HARQ feedback, including at least one of the following:

[0283] ACK or NACK for the first data;

[0284] The first data belongs to at least one target device's data ACK or NACK;

[0285] ACK or NACK for the second data;

[0286] Was the failure to receive the first data the cause of the failure to transmit the second data?

[0287] After merging the first and second data, the data belonging to the second device will be either ACK or NACK.

[0288] The methods for the first device to retransmit the first data include:

[0289] Alt1: Send at least a portion of the first data that needs to be retransmitted, as at least a portion of the new first data, to the second device that responded with NACK to the first data;

[0290] Alt2: Send at least a portion of the first data that needs to be retransmitted, as at least a portion of the new second data, to the second device that responded with NACK to the first data.

[0291] A method for the first device to repeatedly transmit the first data includes:

[0292] Configure the resources, location, and number of repetitions for the first data repetition;

[0293] Different repetitions of the first data can be overlaid and transmitted with different second data.

[0294] Example 1: CRC addition method for the first data

[0295] The first data carries data from at least one target device; therefore, adding a CRC includes at least one of the following.

[0296] Alt1: Add a CRC separately for data belonging to different target devices, on a per-target-device basis;

[0297] Alt1-1 (as shown in Figure 5a): Add the CRC of the data to the end of the data belonging to each target device, and concatenate the data of different target devices together;

[0298] Alt1-2 (as shown in Figure 5b): Data belonging to each target device is concatenated together, and after the data, the CRC of data from different target devices is continued to be concatenated according to the order in which the data is placed.

[0299] Alt2 (as shown in Figure 5c): Concatenate the data belonging to each target device in the first data, then add a CRC to all the data as a whole, and concatenate it at the end of the data.

[0300] Alt3: As shown in Figure 5d, before generating the first and second data, a CRC is added to the data belonging to the target device (i.e., the information to be transmitted).

[0301] Alt4 (as shown in Figure 5e): For the various options mentioned above, the data that needs to have CRC added (such as the first data) can also be used as the input for channel coding, and the data after channel coding can be used as the data after CRC has been added, without adding CRC separately.

[0302] Alt5: The combination of the above options, as shown in Figure 5f, is the combination of Alt1-1 and Alt2; as shown in Figure 5g, it is the combination of Alt1-2 and Alt2; as shown in Figure 5h, it is the combination of Alt1 and Alt4. Other combinations will not be described in detail.

[0303] In this example, the first data and the second data can be Service Data Units (SDUs) or Protocol Data Units (PDUs) of various protocol layers, or codewords (bit sequences transmitted over the air interface) of the physical layer. The protocol layers include, but are not limited to, Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), MAC, and the physical layer, wherein the PDU of the MAC layer or the SDU of the physical layer is a Transport Block (TB).

[0304] Example 2: CW generation method for the first data

[0305] This example primarily describes how the physical layer of the first device generates a CW, specifically including the following two methods:

[0306] Alt1: For each target device, the data (and CRC) belonging to different target devices are individually channel-coded. Based on the multiple individually encoded data, a Channel Wave (CW) is formed. Taking Alt1-1 in Example 1 as an example, the process includes the following:

[0307] (1) Treat Payload1+CRC1, Payload2+CRC2, etc. as multiple different data groups (or sub-data blocks, data blocks, bit groups, etc.), such as data group 1, data group 2, ..., etc.

[0308] Optionally, each data group is interleaved before channel coding. The interleaving can use row-to-row, column-to-row, or other predefined or configured interleavers. The explanation of interleaving is consistent below and will not be repeated.

[0309] Alternatively, for data groups generated based on Alt4 in Example 1, channel coding can be skipped here, and the data can be regarded as a bit sequence that has already been channel coded.

[0310] (2) Channel coding is performed on the bit sequences belonging to different data groups to obtain the encoded bit sequences CB1, CB2, ..., etc.; corresponding to data group 1, data group 2, ..., etc. respectively;

[0311] Optionally, if the bit sequence length of a data group exceeds the channel coding limit, the data group can be divided into more than one sub-data group and channel coded separately. Optionally, a CRC belonging to each sub-data group can also be added separately, for example:

[0312] When the length of the input bit sequence for channel coding is limited to A, and the bit sequence of the data group is b1, b2, b3, ..., b X Let X be a variable, and X > A;

[0313] Let b1, b2, b3, ..., b X Divided into b 11 ,b 12 ,...,b 1x b 21 ,b 22 ,...,b 2x Multiple subsequences, where x+l≤A, l is the CRC length of the sub-data group, and the CRC sequence of the sub-data group n is c. n1 ,c n2 ,...,c nl If no CRC is added to the sub-data group, then l = 0, and c does not exist. n1 ,c n2 ,...,c nl ;

[0314] For each sub-data set n, sequence b n1 ,b n2 ,...,b nx ,c n1 ,c n2 ,...,c nl The data is fed into the channel coding to obtain the channel-coded bit sequence of each sub-data group, i.e., CBn.

[0315] When a data set is divided into multiple sub-data sets, the subsequent initiation operations can be the same, and the multiple sub-data sets can be treated as different data sets for processing.

[0316] (3) Generate CW according to the following method:

[0317] Case 1: Connect the channel-coded CB1, CB2, ... together to form CW;

[0318] Case 2: Based on the bit limit of the physical layer, bits are selected from CB1, CB2, ..., etc., and concatenated together to form CW;

[0319] Case 3: The channel-coded CB1, CB2, ... are concatenated together. Based on the bit limit of the physical layer, some bits are selected from the concatenated bit sequence to form CW.

[0320] Alt2: Channel coding is performed on all data belonging to all target devices (and their CRCs) as a whole to form CW. Taking Alt1-1 in Example 1 as an example:

[0321] (1) Treat the data after Payload1+CRC1, Payload2+CRC2, ..., concatenated as a whole and perform channel coding to obtain the encoded CB0.

[0322] Optionally, the data can be interleaved before channel coding.

[0323] Optionally, if the length of the concatenated bit sequence exceeds the channel coding limit, the data can be divided into more than one sub-data group, and each sub-data group can be channel-coded to obtain channel-coded CB1, CB2, ..., etc. Optionally, a separate CRC can be added to each sub-data group.

[0324] (2) Generate CW according to the following method:

[0325] Case 1: The channel-coded CB0 is used to form a CW, or (for the case of packets) CB1, CB2, ..., are concatenated together to form a CW;

[0326] Case 2: Based on the bit limit of the physical layer, select bits from CB0 to form CW, or (for the case of groups) select bits from CB1, CB2, ..., etc., respectively, and concatenate them together to form CW;

[0327] Case 3: In the case of grouping, the channel-coded CB1, CB2, ... are concatenated together. Based on the bit limit of the physical layer, some bits are selected from the concatenated bit sequence to form CW.

[0328] It should be noted that the "selection of bits" can be accomplished through a circular buffer. The start and end positions of the bits selected from the buffer can be determined based on the current HARQ RV and / or physical layer transmission limitations, etc. There is no limitation on how the bits are selected here.

[0329] Optionally, after channel coding or before forming the CW, data interleaving can be performed, including: interleaving the bits of CB0, or interleaving the bits belonging to different CBs (such as CB1, CB2, ..., etc.), or concatenating the bits belonging to different CBs and then interleaving them before forming the CW.

[0330] It should be noted that the second data only contains data from the target device, and the CW generation method can follow the existing mechanism.

[0331] Example 3: Combined CRC addition and CW generation (reusing existing mechanisms)

[0332] In the existing mechanism, if the length of the data block (TB) (e.g., length X) plus the CRC of the TB (e.g., length L1) exceeds the channel coding limit (e.g., length A), the TB will be divided into multiple sub-data blocks and channel coded separately to generate multiple codeblocks. Before generating a codeblock, a CRC (e.g., length L2) will be appended to the end of each sub-data block. The length of the sub-data block after adding the CRC is A. For the last sub-data block, if the length after adding the CRC is not equal to A, redundant bits will be padded. <null>Until the length is A.

[0333] Therefore, based on existing mechanisms, data belonging to different target devices can be considered as different sub-data blocks within a single TB. During transmission, data belonging to different target devices is segmented, individually CRC-encoded, and then channel-coded. Each sub-data block generates a codeblock, and finally, a code-wise translation (CW) is generated based on the data from multiple codeblocks. The process from codeblock to CW is part of the existing mechanism and will not be elaborated here. This application's example demonstrates how to merge data belonging to multiple target devices into a single TB, ensuring that each sub-data block after the TB is segmented corresponds to data belonging to a target device.

[0334] (1) The first device instructs the second device on data-related information of the first data (or expresses it as the content format of the first data), including at least one of the following:

[0335] The total size of the first data, such as the number of bits or bytes;

[0336] The length of the first data sub-data block, such as the number of bits or bytes;

[0337] The length of each codeblock after the first data is channel-coded, such as the number of bits or bytes;

[0338] The HARQ RV of the sub-data blocks belonging to each target device in the first data, or the HARQ RV of each codeblock;

[0339] The overall RV of the first data set;

[0340] The first data sub-data blocks or codeblocks correspond to each target device, wherein one target device can correspond to multiple sub-data blocks or corresponding codeblocks.

[0341] (2) The first device generates TB of first data based on data from multiple target devices;

[0342] The first device can generate multiple sub-data blocks, each of which carries data from one target device.

[0343] Generally, the target length of each sub-data block is A-L2; at least one sub-data block has a target length of A-L2-L1; when the target length of each sub-data block is greater than the length of the data to be carried, for example when the data of the target device is less than the target length A-L2, agreed bits or indicated bits can be filled into the data until the total length of the data plus the filling bits is the target length; the total length of the first data TB is an integer multiple of A.

[0344] In addition, the first device can cascade multiple sub-data blocks as described above, for example:

[0345] The bit sequence of sub-data block 1 is a1, a2, a3, ..., a A-L2 ;

[0346] The bit sequence of sub-data block 2 is b1, b2, b3, ..., b A-L2 ;

[0347] ...;

[0348] The bit sequence of sub-data block n is z1, z2, z3, ..., z A-L2-L1 ;

[0349] The first data TB after cascading is a1, a2, a3, ..., a A-L2 ,b1,b2,b3,...,b A-L2 ,...,z1,z2,z3,...,z A-L2-L1 .

[0350] (3) The first device generates multiple codeblocks and their corresponding codeWs from the first data's TB using existing TB-to-CW generation methods and channel coding with a length limit of A. Examples of some key steps are provided below:

[0351] a. The first device adds a CRC of length L1 (e.g., x1, x2, ..., x) to the TB of the first data. L1 ), to obtain the first intermediate data a1, a2, a3, ..., a A-L2 ,b1,b2,b3,...,b A-L2 ,...,z1,z2,z3,...,z A-L2-L1 ,x1,x2,...,x L1 Its length is n*(A-L2), where n is the number of sub-data blocks;

[0352] b. The first device takes the first A-L2 bits of the first intermediate data and adds a CRC of length L2 (e.g., y1, y2, ..., y...). L2 The second intermediate data, with a length of A, is generated, which is exactly the length limit for channel coding. Channel coding is then performed to obtain the codeblock.

[0353] c. Perform step b on the remaining sub-data blocks to obtain n codeblocks;

[0354] d. The first device generates the first data CW based on n codeblocks using the existing mechanism.

[0355] Example 4: CRC Check Method

[0356] This example primarily describes how a second device verifies received data. It should be noted that this example is not limited to the physical layer, nor is it limited to the first data. Specifically, the second device verifies the first data and / or the second data using at least one of the following methods:

[0357] Alt1: Verifies the CRC of data belonging to at least one target device in the first data, applicable to Alt1 in Example 1.

[0358] The second device obtains the data belonging to different target devices in the first data and their CRC, and performs verification respectively;

[0359] If data belonging to a certain target device fails the CRC check, the data transmission of that part is considered to have failed (equivalent to, if it passes the CRC check, the data transmission of that part is considered to have succeeded, which will not be elaborated further). At the same time, if at least part of the data transmission of the first data fails, the first data as a whole can also be considered to have failed.

[0360] Corresponding to Example 2, if the first device performs data splitting during channel coding and the split sub-data groups also have CRC, then the second device can also verify each sub-data group.

[0361] Alt2: Verifies the CRC of the first set of data, applicable to Alt2 in Example 1.

[0362] The second device obtains the first data and verifies the first data as a whole;

[0363] If the data in the first data fails the CRC check, the entire first data transmission is considered to have failed.

[0364] Corresponding to Example 2, if the first device performs data splitting during channel coding and the split sub-data groups also have CRC, then the second device can also verify each sub-data group.

[0365] Alt3: Verify the CRC of the second data.

[0366] The second device obtains the second data and verifies the second data;

[0367] If the data in the second data fails the CRC check, the data transmission of the second data is considered to have failed.

[0368] If the first device also performs data splitting when channel coding the second data, such as dividing it into multiple code blocks or code block groups, and the split CB / CBG also has CRC, then the second device can also verify each CB / CBG.

[0369] Alt4: After merging the first and second data belonging to the second device, verify the CRC of the merged data, corresponding to Alt3 in Example 1.

[0370] The second device obtains the first data and the second data;

[0371] The second device extracts a portion of the first data and merges it with the second data to obtain the merged data and its CRC.

[0372] The second device performs a CRC check on the merged data;

[0373] The second device obtains the first data and verifies the first data as a whole;

[0374] If the CRC check fails, the transmission is considered to have failed.

[0375] Alt5: Corresponding to Alt4 in Example 1. If CRC is not used for verification, the characteristics of channel coding can also be used for data verification, for example:

[0376] For a linear block code, assuming the channel-coded data (received data) is b, and the parity check matrix is ​​H, if H T If b = 0, then b is correct data; otherwise, there is an error.

[0377] If b is a valid codeword that can be generated by the channel coding, then b is correct data.

[0378] It should be noted that in actual operation, the second device can also obtain the first data and the second data based on the CW of the first data and the second data through channel decoding and possible operations of higher-level protocol stacks.

[0379] Example 5: HARQ Feedback Method

[0380] Based on the CRC check result of Example 4, the second device sends at least one of the following pieces of information back to the first device:

[0381] (1) The first data set is ACK or NACK.

[0382] Case 1, corresponding to Alt2 in Example 4: indicates whether the CRC of the first data as a whole passes verification. If it passes verification, it is ACK; if it fails verification, it is NACK.

[0383] If the first device performs data splitting during channel coding and the split sub-data groups also contain CRC, all sub-data groups are verified as ACK, and at least one fails as NACK.

[0384] Case 2, corresponding to Alt1 in Example 4: indicates whether all data groups belonging to different target devices have passed verification. If all data groups have passed verification, it is ACK; if at least one has failed, it is NACK.

[0385] If the first device splits the data group belonging to a target device during channel coding and the split sub-data groups also contain CRC, then the data group of the target device is considered to have passed verification if all sub-data groups pass the verification; otherwise, it is considered to have failed verification.

[0386] In one implementation, only one ACK or NACK is fed back in any case.

[0387] (2) ACK or NACK of the sub-data groups after the first data is split.

[0388] Corresponding to Alt2 in Example 4, the first device performs data splitting during channel coding, and the split sub-data groups also contain CRC. The ACK or NACK of each sub-data group indicates whether each sub-data group has passed the verification. If it has passed the verification, it is ACK; otherwise, it is NACK.

[0389] For example, if there are X subgroups of data, then X ACKs or NACKs will be returned.

[0390] (3) ACK or NACK of the data in the first data that belongs to at least one target device.

[0391] Alt1 in Example 4 indicates whether data groups belonging to different receiving devices have passed verification. If verification is successful, it is ACK; otherwise, it is NACK.

[0392] If the first device performs data splitting during channel coding and each split sub-data group also has a CRC checksum, all sub-data groups will pass verification as ACK, and at least one will fail as NACK.

[0393] For example, if there are X target devices, then X ACKs or NACKs should be returned.

[0394] (4) ACK or NACK in the first data belonging to at least one target device's sub-data group.

[0395] Alt1 in Example 4: indicates whether the unsplit data groups belonging to different target devices have passed the verification. If they have passed the verification, it is ACK; otherwise, it is NACK. Furthermore, it provides feedback on whether the multiple sub-data groups of each split data group have passed the verification.

[0396] If the first device performs data splitting during channel coding and the split sub-data groups also contain CRC, the sub-data groups are verified as ACK if they pass the verification, and NACK if they fail.

[0397] For example, if there are X target devices and the data from Y target devices is split into Z sub-data groups, then X-Y+Y*Z ACKs or NACKs will be returned.

[0398] (5) The ACK or NACK of the first data belonging to at least one target device and its sub-data groups.

[0399] Alt1 in Example 4 indicates whether each data group belonging to different target devices has passed verification. If it has passed verification, it is ACK; otherwise, it is NACK. Furthermore, it provides feedback on whether the multiple sub-data groups that each data group has been split into have passed verification.

[0400] If the first device performs data splitting during channel coding and the split sub-data groups also contain CRC, and all sub-data groups pass verification, then the corresponding data group is returned as ACK; if at least one sub-data group fails verification, it is returned as NACK. Furthermore, it returns whether each sub-data group has passed verification; if it has passed verification, it is returned as ACK; if it has failed verification, it is returned as NACK.

[0401] For example, if there are X target devices and the data from Y devices is split into Z sub-data groups, then X+Y*Z ACKs or NACKs will be returned.

[0402] (6) ACK or NACK for the second data.

[0403] The second data only contains data from the target device. Existing feedback mechanisms can be applied, such as verifying whether the CW of the second data passes the CRC check. If it passes, an ACK is fed back; otherwise, a NACK is fed back.

[0404] In particular, the second data can also be split and transmitted, for example, into multiple code blocks or code block groups, and the feedback can be given according to CB or CBG granularity.

[0405] (7) First indication information, used to indicate whether the second data transmission failure is caused by the failure of the first data reception.

[0406] This indicates whether the failure of the second data transmission was caused by the failure of the first data transmission, for example, bit 0 indicates yes and bit 1 indicates no, or bit 1 indicates yes and bit 0 indicates no.

[0407] Furthermore, it indicates a second data transmission failure caused by a data transmission failure belonging to a certain target device in the first data, for example, bitmap 001 indicates a second data transmission failure caused by a data transmission failure of the first target device.

[0408] (8) After merging the first data and the second data, the data belonging to the second device will be either ACK or NACK.

[0409] For Alt4 in Example 4, if the merged data passes the CRC check, then ACK is returned; otherwise, NACK is returned.

[0410] The aforementioned ACK or NACK feedback information can be transmitted in various ways, such as:

[0411] (1) Represented by a bitmap, each bit in the bitmap corresponds to the object that needs to be fed back, such as the data group belonging to each target device in the first data, and the bit being 0 / 1 indicates whether the object has been successfully transmitted;

[0412] (2) Represented by sequence number + bit, for example, feedback sequence number X + bit 0 / 1 indicates that the data group belonging to the Xth target device in the first data has failed or succeeded in transmission; in particular, it can be agreed to only feedback NACK or ACK;

[0413] (3) Combine with the existing semi-static or dynamic codebook of ACK or NACK, and use each of the above objects to be fed back as CBG or TB in the existing ACK or NACK codebook for feedback.

[0414] Example 6: Retransmission and repetition of the first data

[0415] The first device can retransmit the first data using at least one of the following methods:

[0416] Alt1: Directly retransmit all initial data, including:

[0417] (1) The first device sends first information to the second device to schedule the retransmission of first data, wherein the first information includes at least one of the following:

[0418] First data retransmission or initial transmission instruction;

[0419] The signal format of the first retransmitted data (including Cyclic Prefix (CP), frame structure, MCS and / or waveform, etc.);

[0420] The data-related information (or content format) of the first retransmitted data;

[0421] The resources for the first retransmitted data;

[0422] The second device ID or list that receives the retransmitted first data.

[0423] The data-related information of the first retransmitted data includes:

[0424] The total size of the first data, such as the number of bits or bytes;

[0425] The overall CRC format of the first data: CRC position, size / length;

[0426] The first data segment contains the size of the data belonging to each target device, such as the number of bits and bytes.

[0427] The CRC format of the data belonging to each target device in the first data: CRC position, size / length;

[0428] HARQ RV of the data belonging to each target device in the first data;

[0429] The first data is the overall RV.

[0430] (2) The first device sends second information to the second device to schedule the transmission of second data (the second data can be either a retransmission or an initial transmission, which is not limited) at the same time as the retransmission of the first data. The second information includes at least one of the following:

[0431] The signal format of the first data; the resources for retransmitting the first data; the resources for the second data; the signal format of the second data; the second device ID or list for receiving the second data.

[0432] (3) The first device retransmits the first data to the second device and performs new transmission or retransmission of the second data.

[0433] Alt2: At least a portion of the first data that needs to be retransmitted will be used as at least a portion of the new first data, including:

[0434] (1) The first device sends third information to the second device to schedule the retransmission of a portion of the first data, wherein the first information includes at least one of the following:

[0435] Indications for retransmission or initial transmission of partial data in the first data (e.g., indicating retransmission of data belonging to the Xth target device and new transmission of data belonging to the Yth target device);

[0436] The signal format of the first data (including CP, frame structure, MCS and / or waveform, etc.);

[0437] The first data contains data-related information (or is presented in a content format);

[0438] First data resources;

[0439] The second device ID or list received from the retransmitted portion of the first data;

[0440] The second device ID or list that receives newly transmitted data from the first data;

[0441] The second device ID or list that receives the first data.

[0442] The data-related information of the first data includes:

[0443] The total size of the first data, such as the number of bits or bytes;

[0444] The overall CRC format of the first data: CRC position, size / length;

[0445] The first data segment contains the size of the data belonging to each target device, such as the number of bits and bytes.

[0446] The CRC format of the data belonging to each target device in the first data: CRC position, size / length;

[0447] HARQ RV of the data belonging to each target device in the first data;

[0448] The first data is the overall RV.

[0449] (2) The first device sends fourth information to the second device, scheduling the second data to be sent simultaneously with the first data (the second data can be a retransmission or the initial transmission, which is not limited), and the second information includes at least one of the following:

[0450] The signal format of the first data; the resources for retransmitting the first data; the resources for the second data; the signal format of the second data; the second device ID or list for receiving the second data.

[0451] (3) The first device sends first data containing at least some retransmitted data to the second device, and performs new transmission or retransmission of the second data.

[0452] Alt3: Send at least a portion of the first data that needs to be retransmitted, as at least a portion of the new second data, to the second device that responded with a NACK to the first data, including:

[0453] (1) The first device sends fifth information to the second device to schedule the transmission of second data containing retransmission data of the first data, wherein the fifth information includes at least one of the following:

[0454] The signal format of the first data transmitted simultaneously;

[0455] The resources for transmitting the first data simultaneously;

[0456] The signal format of the second data;

[0457] Secondary data resources;

[0458] The second data carries information related to the retransmission of the first data.

[0459] The information related to the retransmission of the first data carried by the second data includes:

[0460] The data-related information (or described as content format) of the retransmitted data includes at least one of the following: the total size of the retransmitted data, the CRC format of the retransmitted data as a whole, the size of the data belonging to each target device in the retransmitted data, the CRC format of the data belonging to each target device in the retransmitted data, the HARQ RV of the data belonging to each target device in the retransmitted data, and the RV of the retransmitted data as a whole.

[0461] The retransmitted data is located at the position of the second data;

[0462] The relationship between retransmitted data and the first data being retransmitted, for example, indicating that the current retransmitted data is the Xth part of the first data being retransmitted, or data belonging to the Xth target device.

[0463] (2) The first device sends second data containing at least some retransmitted data to the second device, and performs new transmission or retransmission of the first data.

[0464] Furthermore, based on the aforementioned Alt1, the first device can configure the repetition transmission of the first data to improve the transmission reliability of the first data. On each repetition, the first device can schedule different second data.

[0465] Specifically, add the following information to the first message of Alt1:

[0466] Resources for repeatedly transmitted first data, such as the number of repetitions, the transmission resources for each repetition, or the resources occupied by periodically occurring transmission opportunities.

[0467] The second information defined in Alt1 refers to the second data sent concurrently with the repetition of the first data. The content of the second information is largely consistent with the description in Alt1, except that it can indicate each different repetition individually or uniformly for all repetitions. For example:

[0468] If each different repetition is indicated separately, then multiple second pieces of information need to be indicated;

[0469] If a uniform instruction is provided for all repetitions, then the following can be indicated:

[0470] Case 1: Each item in the second information contains multiple values, and each value corresponds to one or more repetitions that are applied.

[0471] Case 2: Each item in the second information is a periodic configuration, corresponding to the periodic transmission opportunities of repetition.

[0472] This application proposes a data transmission method that can improve the reliability of RSMA transmission. By increasing the granularity of CRC addition, detection and feedback, the corresponding common stream codeword generation method, and / or the common stream retransmission and repeated transmission methods, the transmission reliability of the common stream can be improved, thereby improving the transmission reliability of RSMA.

[0473] Referring to Figure 6, which is a flowchart of a data transmission method provided in an embodiment of this application, the data transmission method includes the following steps:

[0474] Step 201: The second device receives first data transmitted by the first device and second data corresponding to the second device, wherein the time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the second device at least partially overlap, and the receiving object of the first data is at least one target device, the at least one target device including the second device;

[0475] Step 202: The second device sends feedback information to the first device;

[0476] The feedback information includes at least one of the following:

[0477] The first data transmission confirmation information;

[0478] The first data includes transmission confirmation information for at least one target device;

[0479] The second device corresponds to the transmission confirmation information of the second data;

[0480] The first indication information is used to indicate whether the reason for the failure of the second data transmission is related to the transmission of the first data;

[0481] The transmission confirmation information for the merged data corresponding to the second device, wherein the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data.

[0482] Optionally, before the second device sends feedback information to the first device, the method further includes at least one of the following:

[0483] The second device verifies the verification information corresponding to at least one target device in the received first data;

[0484] The second device verifies the verification information of the first data in the received first data;

[0485] The second device verifies the received second data;

[0486] The second device merges the data corresponding to the second device in the first data it receives with the second data, and verifies the merged data.

[0487] The verification information can be CRC, and the verification can refer to performing CRC verification.

[0488] In one embodiment, the second device verifies the verification information corresponding to at least one target device in the received first data, which may include: verifying the CRC of data belonging to at least one target device in the first data.

[0489] In one embodiment, the second device's verification of the verification information of the first data in the received first data may include: verifying the CRC of the first data as a whole.

[0490] In one embodiment, the second device verifying the received second data may include: verifying the CRC of the second data.

[0491] In one embodiment, the second device merging the data corresponding to the second device in the received first data with the second data and verifying the merged data may include: merging the first data and the second data belonging to the second device and then verifying the CRC of the merged data.

[0492] In one implementation, the first device can perform data verification using the characteristics of channel coding.

[0493] In this embodiment, verifying the received data using a second device can improve transmission reliability.

[0494] Optionally, the method further includes:

[0495] The second device receives the second instruction information sent by the first device;

[0496] The second indication information is used to indicate data-related information of the first data.

[0497] Optionally, the first data is the first data retransmitted; or,

[0498] The first data includes retransmitted data; or,

[0499] The second data includes at least a portion of the retransmitted first data.

[0500] Optionally, the method further includes at least one of the following:

[0501] The second device receives the first information sent by the first device;

[0502] The second device receives the second information sent by the first device;

[0503] The first information includes at least one of the following:

[0504] The retransmission or initial transmission indication of the first data; the signal format of the retransmitted first data; the data-related information of the retransmitted first data; the resources of the retransmitted first data; and the identifier of the target device for receiving the retransmitted first data.

[0505] The second information includes at least one of the following:

[0506] The signal format of the first retransmitted data; the resources of the first retransmitted data; the resources of the second data; the signal format of the second data; and the identifier of the target device for receiving the second data.

[0507] Optionally, the method further includes at least one of the following:

[0508] The second device receives the third information sent by the first device;

[0509] The second device receives the fourth information sent by the first device;

[0510] The third information includes at least one of the following:

[0511] The first data includes: a retransmission or initial transmission indication of some data in the first data; the signal format of the first data; data-related information of the first data; resources of the first data; an identifier of the receiving object used to receive retransmitted data in the first data; an identifier of the receiving object used to receive newly transmitted data in the first data; and an identifier of the receiving object used to receive the first data.

[0512] The fourth piece of information includes at least one of the following:

[0513] The signal format of the first data; resources for retransmitted data; resources for the second data; the signal format of the second data; the identifier of the target device for receiving the second data.

[0514] Optionally, the method further includes:

[0515] The second device receives the fifth message sent by the first device;

[0516] The fifth piece of information includes at least one of the following:

[0517] The signal format of the first data; the resources of the first data; the signal format of the second data; the resources of the second data; the relevant information of the retransmitted data carried by the second data;

[0518] The retransmission data carried by the second data carrier includes at least one of the following:

[0519] Data-related information of the retransmitted data; location information of the retransmitted data within the second data; relationship between the retransmitted data and its parent first data.

[0520] Optionally, the data-related information includes at least one of the following:

[0521] The size of the first data; the format information of the verification information of the first data; the size of the data corresponding to each target device in the first data; the length of the sub-data block or code block corresponding to the first data; the format information of the verification information of the data corresponding to each target device in the first data; the RV of the data corresponding to each target device in the first data; the RV of the first data; the correspondence between the sub-data block or code block corresponding to the first data and the target device.

[0522] Optionally, the method further includes at least one of the following:

[0523] The second device receives a first configuration sent by the first device, wherein the first configuration is used to configure at least one of the resources, location and number of times the first data is repeatedly transmitted;

[0524] The second device receives a second configuration sent by the first device, the second configuration being configured to schedule the transmission of second data simultaneously in the event of repeated transmission of the first data.

[0525] It should be noted that this embodiment is an implementation of the second device or target device corresponding to the embodiment shown in FIG4. The specific implementation can be found in the relevant description of the embodiment shown in FIG4. To avoid repeated description, this embodiment will not be repeated.

[0526] The data transmission method provided in this application can be executed by a data transmission device. This application uses a data transmission device executing the data transmission method as an example to illustrate the data transmission device provided in this application.

[0527] This application provides a data transmission device. As an example, the data transmission device may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0528] The data transmission device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0529] Specifically, referring to Figure 7, when the data transmission device is the first device or a component of the first device, the data transmission device 300 includes:

[0530] The transmitting module 301 is used to transmit first data and second data corresponding to each of the at least one target device, wherein the time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the at least one target device at least partially overlap, the receiving object of the first data is the at least one target device, and the receiving object of the second data is the corresponding target device.

[0531] The receiving module 302 is used to receive feedback information sent by the second device, wherein the at least one target device includes the second device;

[0532] The feedback information includes at least one of the following:

[0533] The first data transmission confirmation information;

[0534] The first data includes transmission confirmation information for at least one target device;

[0535] The second device corresponds to the transmission confirmation information of the second data;

[0536] The first indication information is used to indicate whether the reason for the failure of the second data transmission is related to the transmission of the first data;

[0537] The transmission confirmation information for the merged data corresponding to the second device, wherein the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data.

[0538] Optionally, the sending module is specifically used for:

[0539] The first data is subjected to target processing to obtain the first data to be transmitted; or, verification information is added to the information to be transmitted corresponding to the target device, and the first data to be transmitted is generated based on the information to be transmitted after adding the verification information.

[0540] Transmit the first data to be transmitted;

[0541] The target processing includes at least one of the following:

[0542] Add the verification information corresponding to each target device to the data corresponding to each target device in the first data respectively;

[0543] Add verification information to the first data;

[0544] The first data is channel coded.

[0545] Optionally, the sending module is specifically used for:

[0546] Channel coding is performed on the data corresponding to each target device in the first data to be transmitted, or the first device performs channel coding on the first data to be transmitted;

[0547] Codewords are generated based on the channel coding results, and the codewords are transmitted.

[0548] Optionally, the sending module is specifically used for:

[0549] The data corresponding to each target device in the first data to be transmitted is divided into data groups corresponding to each device;

[0550] If the bit sequence length of a target data group is greater than the channel coding limit length, the target data group is divided into multiple sub-data groups;

[0551] Channel coding is performed on the divided data groups.

[0552] Optionally, the sending module is specifically used for any of the following:

[0553] The code blocks obtained from channel coding are concatenated to form codewords;

[0554] Based on the bit quantity limit of the physical layer, bits are selected from the code block obtained by channel coding and concatenated to form codewords;

[0555] The code blocks obtained by channel coding are concatenated to obtain a bit sequence. According to the bit quantity limit of the physical layer, bits are selected from the bit sequence for concatenation to form a codeword.

[0556] Optionally, the sending module is specifically used for:

[0557] Generate a transport block TB corresponding to the first data, the TB including multiple sub-data blocks, each sub-data block corresponding to a target device;

[0558] Generate codewords based on the TB and transmit the codewords.

[0559] Optionally, the sending module is specifically used for:

[0560] Multiple sub-data blocks are generated, and each sub-data block carries data corresponding to a target device in the first data;

[0561] The multiple sub-data blocks are concatenated to obtain the TB corresponding to the first data.

[0562] Optionally, the sending module is further configured to:

[0563] Send a second instruction message to the at least one target device;

[0564] The second indication information is used to indicate data-related information of the first data.

[0565] Optionally, the first data is the first data retransmitted; or,

[0566] The first data includes retransmitted data; or,

[0567] The second data includes at least a portion of the retransmitted first data.

[0568] Optionally, when the first data is retransmitted first data, the sending module is further configured to perform at least one of the following:

[0569] Send the first information to the second device;

[0570] Send the second information to the second device;

[0571] The first information includes at least one of the following:

[0572] The retransmission or initial transmission indication of the first data; the signal format of the retransmitted first data; the data-related information of the retransmitted first data; the resources of the retransmitted first data; and the identifier of the target device for receiving the retransmitted first data.

[0573] The second information includes at least one of the following:

[0574] The signal format of the first retransmitted data; the resources of the first retransmitted data; the resources of the second data; the signal format of the second data; and the identifier of the target device for receiving the second data.

[0575] Optionally, if the first data includes retransmitted data, the sending module is further configured to perform at least one of the following:

[0576] Send the third message to the second device;

[0577] Send the fourth message to the second device;

[0578] The third information includes at least one of the following:

[0579] The first data includes: a retransmission or initial transmission indication of some data in the first data; the signal format of the first data; data-related information of the first data; resources of the first data; an identifier of the receiving object used to receive retransmitted data in the first data; an identifier of the receiving object used to receive newly transmitted data in the first data; and an identifier of the receiving object used to receive the first data.

[0580] The fourth piece of information includes at least one of the following:

[0581] The signal format of the first data; resources for retransmitted data; resources for the second data; the signal format of the second data; the identifier of the target device for receiving the second data.

[0582] Optionally, if the second data includes at least a portion of the retransmitted first data, the sending module is further configured to:

[0583] Send the fifth message to the second device;

[0584] The fifth piece of information includes at least one of the following:

[0585] The signal format of the first data; the resources of the first data; the signal format of the second data; the resources of the second data; the relevant information of the retransmitted data carried by the second data;

[0586] The retransmission data carried by the second data carrier includes at least one of the following:

[0587] Data-related information of the retransmitted data; location information of the retransmitted data within the second data; relationship between the retransmitted data and its parent first data.

[0588] Optionally, the data-related information includes at least one of the following:

[0589] The size of the first data; the format information of the verification information of the first data; the size of the data corresponding to each target device in the first data; the length of the sub-data block or code block corresponding to the first data; the format information of the verification information of the data corresponding to each target device in the first data; the redundancy version (RV) of the data corresponding to each target device in the first data; the RV of the first data; the correspondence between the sub-data block or code block corresponding to the first data and the target device.

[0590] Optionally, the sending module is further configured to include at least one of the following:

[0591] Send a first configuration to the second device, wherein the first configuration is used to configure at least one of the resources, location and number of times the first data is repeatedly transmitted;

[0592] Send a second configuration to the second device, the second configuration being used to configure the simultaneous scheduling of sending second data in the event of repeated transmission of the first data.

[0593] Referring to Figure 8, when the data transmission device is a second device or a component of the second device, the data transmission device 400 includes:

[0594] The receiving module 401 is used to receive first data transmitted by the first device and second data corresponding to the second device, wherein the time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the second device at least partially overlap, and the receiving object of the first data is at least one target device, the at least one target device including the second device.

[0595] The sending module 402 is used to send feedback information to the first device;

[0596] The feedback information includes at least one of the following:

[0597] The first data transmission confirmation information;

[0598] The first data includes transmission confirmation information for at least one target device;

[0599] The second device corresponds to the transmission confirmation information of the second data;

[0600] The first indication information is used to indicate whether the reason for the failure of the second data transmission is related to the transmission of the first data;

[0601] The transmission confirmation information for the merged data corresponding to the second device, wherein the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data.

[0602] Optionally, the device further includes a processing module for at least one of the following:

[0603] Verify the verification information corresponding to at least one target device in the received first data;

[0604] The verification information of the first data in the received first data is verified;

[0605] Verify the received second data;

[0606] The data corresponding to the second device in the first data received is merged with the second data, and the merged data is verified.

[0607] Optionally, the receiving module is further configured to:

[0608] Receive the second instruction information sent by the first device;

[0609] The second indication information is used to indicate data-related information of the first data.

[0610] Optionally, the first data is the first data retransmitted; or,

[0611] The first data includes retransmitted data; or,

[0612] The second data includes at least a portion of the retransmitted first data.

[0613] Optionally, the receiving module is further configured to include at least one of the following:

[0614] Receive the first information sent by the first device;

[0615] Receive the second information sent by the first device;

[0616] The first information includes at least one of the following:

[0617] The retransmission or initial transmission indication of the first data; the signal format of the retransmitted first data; the data-related information of the retransmitted first data; the resources of the retransmitted first data; and the identifier of the target device for receiving the retransmitted first data.

[0618] The second information includes at least one of the following:

[0619] The signal format of the first retransmitted data; the resources of the first retransmitted data; the resources of the second data; the signal format of the second data; and the identifier of the target device for receiving the second data.

[0620] Optionally, the receiving module is further configured to include at least one of the following:

[0621] Receive the third information sent by the first device;

[0622] Receive the fourth message sent by the first device;

[0623] The third information includes at least one of the following:

[0624] The first data includes: a retransmission or initial transmission indication of some data in the first data; the signal format of the first data; data-related information of the first data; resources of the first data; an identifier of the receiving object used to receive retransmitted data in the first data; an identifier of the receiving object used to receive newly transmitted data in the first data; and an identifier of the receiving object used to receive the first data.

[0625] The fourth piece of information includes at least one of the following:

[0626] The signal format of the first data; resources for retransmitted data; resources for the second data; the signal format of the second data; the identifier of the target device for receiving the second data.

[0627] Optionally, the receiving module is further configured to:

[0628] Receive the fifth message sent by the first device;

[0629] The fifth piece of information includes at least one of the following:

[0630] The signal format of the first data; the resources of the first data; the signal format of the second data; the resources of the second data; the relevant information of the retransmitted data carried by the second data;

[0631] The retransmission data carried by the second data carrier includes at least one of the following:

[0632] Data-related information of the retransmitted data; location information of the retransmitted data within the second data; relationship between the retransmitted data and its parent first data.

[0633] Optionally, the data-related information includes at least one of the following:

[0634] The size of the first data; the format information of the verification information of the first data; the size of the data corresponding to each target device in the first data; the length of the sub-data block or code block corresponding to the first data; the format information of the verification information of the data corresponding to each target device in the first data; the RV of the data corresponding to each target device in the first data; the RV of the first data; the correspondence between the sub-data block or code block corresponding to the first data and the target device.

[0635] Optionally, the receiving module is further configured to include at least one of the following:

[0636] Receive a first configuration sent by the first device, wherein the first configuration is used to configure at least one of the resources, location and number of times the first data is repeatedly transmitted;

[0637] The device receives a second configuration sent by the first device, the second configuration being configured to schedule the transmission of a second data simultaneously in the event of repeated transmission of the first data.

[0638] The data transmission device provided in this application embodiment can implement the various processes implemented in the method embodiments of FIG4 and FIG6 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0639] As shown in Figure 9, this application embodiment also provides a communication device 500, including a processor 501 and a memory 502. The memory 502 stores a program or instructions that can run on the processor 501. For example, when the communication device 500 is a first device, when the program or instructions are executed by the processor 501, they implement the various steps of the data transmission method embodiment applied to the first device described above, and achieve the same technical effect. When the communication device 500 is a second device, when the program or instructions are executed by the processor 501, they implement the various steps of the data transmission method embodiment applied to the second device described above, and achieve the same technical effect. To avoid repetition, this will not be repeated here.

[0640] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiments shown in FIG4 or FIG6. This terminal embodiment corresponds to the above-described terminal-side method embodiments, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal can be the data transmission device shown in FIG7 or FIG8. Specifically, FIG10 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0641] The terminal 600 includes, but is not limited to, at least some of the following components: radio frequency unit 601, network module 602, audio output unit 603, input unit 604, sensor 605, display unit 606, user input unit 607, interface unit 608, memory 609, and processor 610.

[0642] Those skilled in the art will understand that terminal 600 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to processor 610 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 10 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0643] It should be understood that, in this embodiment, the input unit 604 may include a graphics processor 6041 and a microphone 6042. The graphics processor 6041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 606 may include a display panel 6061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 607 includes at least one of a touch panel 6071 and other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include two parts: a touch detection device and a touch controller. Other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0644] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 601 can transmit it to the processor 610 for processing; in addition, the radio frequency unit 601 can send uplink data to the network-side device. Typically, the radio frequency unit 601 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0645] The memory 609 can be used to store software programs or instructions, as well as various data. The memory 609 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 609 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 609 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0646] Processor 610 may include one or more processing units; optionally, processor 610 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 610.

[0647] Where the terminal is the first device:

[0648] The radio frequency unit 601 is used to: transmit first data and second data corresponding to each of the at least one target devices, wherein the time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the at least one target device at least partially overlap, the first data is received by the at least one target device, and the second data is received by the corresponding target device.

[0649] The radio frequency unit 601 is also used to receive feedback information sent by the second device, wherein the at least one target device includes the second device;

[0650] The feedback information includes at least one of the following:

[0651] The first data transmission confirmation information;

[0652] The first data includes transmission confirmation information for at least one target device;

[0653] The second device corresponds to the transmission confirmation information of the second data;

[0654] The first indication information is used to indicate whether the reason for the failure of the second data transmission is related to the transmission of the first data;

[0655] The transmission confirmation information for the merged data corresponding to the second device, wherein the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data.

[0656] Optionally, the radio frequency unit 601 is specifically used for:

[0657] The first data is subjected to target processing to obtain the first data to be transmitted; or, the first device adds verification information to the information to be transmitted corresponding to the target device, and generates the first data to be transmitted based on the information to be transmitted after adding the verification information.

[0658] Transmit the first data to be transmitted;

[0659] The target processing includes at least one of the following:

[0660] Add the verification information corresponding to each target device to the data corresponding to each target device in the first data respectively;

[0661] Add verification information to the first data;

[0662] The first data is channel coded.

[0663] Optionally, the radio frequency unit 601 is specifically used for:

[0664] Channel coding is performed on the data corresponding to each target device in the first data to be transmitted, or the first device performs channel coding on the first data to be transmitted;

[0665] Codewords are generated based on the channel coding results, and the codewords are transmitted.

[0666] Optionally, the radio frequency unit 601 is specifically used for:

[0667] The data corresponding to each target device in the first data to be transmitted is divided into data groups corresponding to each device;

[0668] If the bit sequence length of a target data group is greater than the channel coding limit length, the target data group is divided into multiple sub-data groups;

[0669] Channel coding is performed on the divided data groups.

[0670] Optionally, the radio frequency unit 601 is specifically used for any of the following:

[0671] The code blocks obtained from channel coding are concatenated to form codewords;

[0672] Based on the bit quantity limit of the physical layer, bits are selected from the code block obtained by channel coding and concatenated to form codewords;

[0673] The code blocks obtained by channel coding are concatenated to obtain a bit sequence. According to the bit quantity limit of the physical layer, bits are selected from the bit sequence for concatenation to form a codeword.

[0674] Optionally, the radio frequency unit 601 is specifically used for:

[0675] Generate a transport block TB corresponding to the first data, the TB including multiple sub-data blocks, each sub-data block corresponding to a target device;

[0676] Generate codewords based on the TB and transmit the codewords.

[0677] Optionally, the radio frequency unit 601 is specifically used for:

[0678] Multiple sub-data blocks are generated, and each sub-data block carries data corresponding to a target device in the first data;

[0679] The multiple sub-data blocks are concatenated to obtain the TB corresponding to the first data.

[0680] Optionally, the radio frequency unit 601 is further configured to:

[0681] Send a second instruction message to the at least one target device;

[0682] The second indication information is used to indicate data-related information of the first data.

[0683] Optionally, the first data is the first data retransmitted; or,

[0684] The first data includes retransmitted data; or,

[0685] The second data includes at least a portion of the retransmitted first data.

[0686] Optionally, when the first data is retransmitted first data, the radio frequency unit 601 is further configured to perform at least one of the following:

[0687] Send the first information to the second device;

[0688] Send the second information to the second device;

[0689] The first information includes at least one of the following:

[0690] The retransmission or initial transmission indication of the first data; the signal format of the retransmitted first data; the data-related information of the retransmitted first data; the resources of the retransmitted first data; and the identifier of the target device for receiving the retransmitted first data.

[0691] The second information includes at least one of the following:

[0692] The signal format of the first retransmitted data; the resources of the first retransmitted data; the resources of the second data; the signal format of the second data; and the identifier of the target device for receiving the second data.

[0693] Optionally, when the first data includes retransmitted data, the radio frequency unit 601 is further configured to perform at least one of the following:

[0694] Send the third message to the second device;

[0695] Send the fourth message to the second device;

[0696] The third information includes at least one of the following:

[0697] The first data includes: a retransmission or initial transmission indication of some data in the first data; the signal format of the first data; data-related information of the first data; resources of the first data; an identifier of the receiving object used to receive retransmitted data in the first data; an identifier of the receiving object used to receive newly transmitted data in the first data; and an identifier of the receiving object used to receive the first data.

[0698] The fourth piece of information includes at least one of the following:

[0699] The signal format of the first data; resources for retransmitted data; resources for the second data; the signal format of the second data; the identifier of the target device for receiving the second data.

[0700] Optionally, if the second data includes at least a portion of the retransmitted first data, the radio frequency unit 601 is further configured to:

[0701] Send the fifth message to the second device;

[0702] The fifth piece of information includes at least one of the following:

[0703] The signal format of the first data; the resources of the first data; the signal format of the second data; the resources of the second data; the relevant information of the retransmitted data carried by the second data;

[0704] The retransmission data carried by the second data carrier includes at least one of the following:

[0705] Data-related information of the retransmitted data; location information of the retransmitted data within the second data; relationship between the retransmitted data and its parent first data.

[0706] Optionally, the data-related information includes at least one of the following:

[0707] The size of the first data; the format information of the verification information of the first data; the size of the data corresponding to each target device in the first data; the length of the sub-data block or code block corresponding to the first data; the format information of the verification information of the data corresponding to each target device in the first data; the redundancy version (RV) of the data corresponding to each target device in the first data; the RV of the first data; the correspondence between the sub-data block or code block corresponding to the first data and the target device.

[0708] Optionally, the radio frequency unit 601 is further used for at least one of the following:

[0709] Send a first configuration to the second device, wherein the first configuration is used to configure at least one of the resources, location and number of times the first data is repeatedly transmitted;

[0710] Send a second configuration to the second device, the second configuration being used to configure the simultaneous scheduling of sending second data in the event of repeated transmission of the first data.

[0711] In the case where the terminal is a second device:

[0712] Radio frequency unit 601 is used to receive first data transmitted by a first device and second data corresponding to a second device, wherein the time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the second device at least partially overlap, and the receiving object of the first data is at least one target device, the at least one target device including the second device.

[0713] Radio frequency unit 601 is used to send feedback information to the first device;

[0714] The feedback information includes at least one of the following:

[0715] The first data transmission confirmation information;

[0716] The first data includes transmission confirmation information for at least one target device;

[0717] The second device corresponds to the transmission confirmation information of the second data;

[0718] The first indication information is used to indicate whether the reason for the failure of the second data transmission is related to the transmission of the first data;

[0719] The transmission confirmation information for the merged data corresponding to the second device, wherein the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data.

[0720] Optionally, the processor 610 is used for at least one of the following:

[0721] Verify the verification information corresponding to at least one target device in the received first data;

[0722] The verification information of the first data in the received first data is verified;

[0723] Verify the received second data;

[0724] The data corresponding to the second device in the first data received is merged with the second data, and the merged data is verified.

[0725] Optionally, the radio frequency unit 601 is further configured to:

[0726] Receive the second instruction information sent by the first device;

[0727] The second indication information is used to indicate data-related information of the first data.

[0728] Optionally, the first data is the first data retransmitted; or,

[0729] The first data includes retransmitted data; or,

[0730] The second data includes at least a portion of the retransmitted first data.

[0731] Optionally, the radio frequency unit 601 is further used for at least one of the following:

[0732] Receive the first information sent by the first device;

[0733] Receive the second information sent by the first device;

[0734] The first information includes at least one of the following:

[0735] The retransmission or initial transmission indication of the first data; the signal format of the retransmitted first data; the data-related information of the retransmitted first data; the resources of the retransmitted first data; and the identifier of the target device for receiving the retransmitted first data.

[0736] The second information includes at least one of the following:

[0737] The signal format of the first retransmitted data; the resources of the first retransmitted data; the resources of the second data; the signal format of the second data; and the identifier of the target device for receiving the second data.

[0738] Optionally, the radio frequency unit 601 is further used for at least one of the following:

[0739] Receive the third information sent by the first device;

[0740] Receive the fourth message sent by the first device;

[0741] The third information includes at least one of the following:

[0742] The first data includes: a retransmission or initial transmission indication of some data in the first data; the signal format of the first data; data-related information of the first data; resources of the first data; an identifier of the receiving object used to receive retransmitted data in the first data; an identifier of the receiving object used to receive newly transmitted data in the first data; and an identifier of the receiving object used to receive the first data.

[0743] The fourth piece of information includes at least one of the following:

[0744] The signal format of the first data; resources for retransmitted data; resources for the second data; the signal format of the second data; the identifier of the target device for receiving the second data.

[0745] Optionally, the radio frequency unit 601 is further configured to:

[0746] Receive the fifth message sent by the first device;

[0747] The fifth piece of information includes at least one of the following:

[0748] The signal format of the first data; the resources of the first data; the signal format of the second data; the resources of the second data; the relevant information of the retransmitted data carried by the second data;

[0749] The retransmission data carried by the second data carrier includes at least one of the following:

[0750] Data-related information of the retransmitted data; location information of the retransmitted data within the second data; relationship between the retransmitted data and its parent first data.

[0751] Optionally, the data-related information includes at least one of the following:

[0752] The size of the first data; the format information of the verification information of the first data; the size of the data corresponding to each target device in the first data; the length of the sub-data block or code block corresponding to the first data; the format information of the verification information of the data corresponding to each target device in the first data; the RV of the data corresponding to each target device in the first data; the RV of the first data; the correspondence between the sub-data block or code block corresponding to the first data and the target device.

[0753] Optionally, the radio frequency unit 601 is further used for at least one of the following:

[0754] Receive a first configuration sent by the first device, wherein the first configuration is used to configure at least one of the resources, location and number of times the first data is repeatedly transmitted;

[0755] The device receives a second configuration sent by the first device, the second configuration being configured to schedule the transmission of a second data simultaneously in the event of repeated transmission of the first data.

[0756] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description in Figure 4 or Figure 6 of the method embodiment, and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0757] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiments shown in FIG4 or FIG6. This network-side device embodiment corresponds to the above-described first device or second device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0758] Specifically, this application embodiment also provides a network-side device, which can be the data transmission device shown in FIG. 7 or FIG. 8. As shown in FIG. 11, the network-side device 700 includes: an antenna 701, a radio frequency device 702, a baseband device 703, a processor 704, and a memory 705. The antenna 701 is connected to the radio frequency device 702. In the uplink direction, the radio frequency device 702 receives information through the antenna 701 and sends the received information to the baseband device 703 for processing. In the downlink direction, the baseband device 703 processes the information to be transmitted and sends it to the radio frequency device 702. The radio frequency device 702 processes the received information and transmits it through the antenna 701.

[0759] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 703, which includes a baseband processor.

[0760] The baseband device 703 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG11. One of the chips is, for example, a baseband processor, which is connected to the memory 705 via a bus interface to call the program in the memory 705 and execute the network device operation shown in the above method embodiment.

[0761] The network-side device may also include a network interface 706, such as a Common Public Radio Interface (CPRI).

[0762] Specifically, the network-side device 700 in this application embodiment further includes: instructions or programs stored in memory 705 and executable on processor 704. Processor 704 calls the instructions or programs in memory 705 to execute the methods executed by the modules shown in FIG7 or FIG8 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0763] Specifically, this application also provides a network-side device. As shown in FIG12, the network-side device 800 includes a processor 801, a network interface 802, and a memory 803. The network-side device may be the data transmission device shown in FIG7 or FIG8. The network interface 802 is, for example, a common public radio interface (CPRI).

[0764] Specifically, the network-side device 800 in this application embodiment further includes: instructions or programs stored in memory 803 and executable on processor 801. Processor 801 calls the instructions or programs in memory 803 to execute the methods executed by the modules shown in FIG7 or FIG8 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0765] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described data transmission method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0766] The processor mentioned above is the processor in the terminal or network-side device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0767] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above data transmission method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0768] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0769] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described data transmission method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0770] This application also provides a wireless communication system, including a first device and a second device. The first device can be used to perform the steps of the data transmission method applied to the first device as described above, and the second device can be used to perform the steps of the data transmission method applied to the second device as described above.

[0771] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one…" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0772] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0773] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.< / null> < / null>

Claims

1. A data transmission method, comprising: The first device transmits first data and second data corresponding to each of the at least one target device, wherein the time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the at least one target device at least partially overlap, the first data is received by the at least one target device, and the second data is received by the corresponding target device. The first device receives feedback information sent by the second device, and the at least one target device includes the second device; The feedback information includes at least one of the following: The first data transmission confirmation information; The first data includes transmission confirmation information for at least one target device; The second device corresponds to the transmission confirmation information of the second data; The first indication information is used to indicate whether the reason for the failure of the second data transmission is related to the transmission of the first data; The transmission confirmation information for the merged data corresponding to the second device, wherein the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data.

2. The method according to claim 1, wherein, The first device transmits first data, including: The first device performs target processing on the first data to obtain the first data to be transmitted; or, it adds verification information to the information to be transmitted corresponding to the target device, and generates the first data to be transmitted based on the information to be transmitted after adding the verification information. The first device transmits the first data to be transmitted; The target processing includes at least one of the following: Add the verification information corresponding to each target device to the data corresponding to each target device in the first data respectively; Add verification information to the first data; The first data is channel coded.

3. The method according to claim 2, wherein, The first device transmits the first data to be transmitted, including: The first device performs channel coding on the data corresponding to each target device in the first data to be transmitted, or the first device performs channel coding on the first data to be transmitted. The first device generates codewords based on the channel coding results and transmits the codewords.

4. The method according to claim 3, wherein, The step of performing channel coding on the data corresponding to each target device in the first data to be transmitted includes: The data corresponding to each target device in the first data to be transmitted is divided into data groups corresponding to each device; If the bit sequence length of a target data group is greater than the channel coding limit length, the target data group is divided into multiple sub-data groups; Channel coding is performed on the divided data groups.

5. The method according to claim 3 or 4, wherein, The generation of codewords based on channel coding results includes any one of the following: The code blocks obtained from channel coding are concatenated to form codewords; Based on the bit quantity limit of the physical layer, bits are selected from the code block obtained by channel coding and concatenated to form codewords; The code blocks obtained by channel coding are concatenated to obtain a bit sequence. According to the bit quantity limit of the physical layer, bits are selected from the bit sequence for concatenation to form a codeword.

6. The method according to claim 1, wherein, The first device transmits first data, including: The first device generates a transport block TB corresponding to the first data, the TB including multiple sub-data blocks, each sub-data block corresponding to a target device; The first device generates codewords based on the TB and transmits the codewords.

7. The method according to claim 6, wherein, The first device generates the TB corresponding to the first data, including: The first device generates multiple sub-data blocks, each of which carries data corresponding to a target device in the first data; The first device concatenates the multiple sub-data blocks to obtain the TB corresponding to the first data.

8. The method according to claim 6 or 7, further comprising: The first device sends a second instruction message to the at least one target device; The second indication information is used to indicate data-related information of the first data.

9. The method according to any one of claims 1-8, wherein, The first data is the first data retransmitted; or, The first data includes retransmitted data; or, The second data includes at least a portion of the retransmitted first data.

10. The method according to claim 9, wherein, If the first data is retransmitted first data, the method further includes at least one of the following: The first device sends first information to the second device; The first device sends the second information to the second device; The first information includes at least one of the following: The retransmission or initial transmission indication of the first data; the signal format of the retransmitted first data; the data-related information of the retransmitted first data; the resources of the retransmitted first data; and the identifier of the target device for receiving the retransmitted first data. The second information includes at least one of the following: The signal format of the first retransmitted data; the resources of the first retransmitted data; the resources of the second data; the signal format of the second data; and the identifier of the target device for receiving the second data.

11. The method according to claim 9, wherein, If the first data includes retransmitted data, the method further includes at least one of the following: The first device sends a third message to the second device; The first device sends a fourth message to the second device; The third information includes at least one of the following: The first data includes: a retransmission or initial transmission indication of some data in the first data; the signal format of the first data; data-related information of the first data; resources of the first data; an identifier of the receiving object used to receive retransmitted data in the first data; an identifier of the receiving object used to receive newly transmitted data in the first data; and an identifier of the receiving object used to receive the first data. The fourth piece of information includes at least one of the following: The signal format of the first data; resources for retransmitted data; resources for the second data; the signal format of the second data; the identifier of the target device for receiving the second data.

12. The method according to claim 9, wherein, If the second data includes at least a portion of the retransmitted first data, the method further includes: The first device sends the fifth message to the second device; The fifth piece of information includes at least one of the following: The signal format of the first data; the resources of the first data; the signal format of the second data; the resources of the second data; the relevant information of the retransmitted data carried by the second data; The retransmission data carried by the second data carrier includes at least one of the following: Data-related information of the retransmitted data; location information of the retransmitted data within the second data; relationship between the retransmitted data and the first data to which it belongs.

13. The method according to any one of claims 8, 10-12, wherein, The data-related information includes at least one of the following: The size of the first data; the format information of the verification information of the first data; the size of the data corresponding to each target device in the first data; the length of the sub-data block or code block corresponding to the first data; The format information of the verification information corresponding to each target device in the first data; the redundancy version (RV) of the data corresponding to each target device in the first data; the RV of the first data; and the correspondence between the sub-data blocks or code blocks corresponding to the first data and the target devices.

14. The method according to any one of claims 1-13, further comprising at least one of the following: The first device sends a first configuration to the second device, the first configuration being used to configure at least one of the resources, location and number of times the first data is repeatedly transmitted; The first device sends a second configuration to the second device, the second configuration being configured to schedule the transmission of second data simultaneously in the event of repeated transmission of the first data.

15. A data transmission method, comprising: The second device receives first data transmitted by the first device and second data corresponding to the second device, wherein the time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the second device at least partially overlap, and the first data is received by at least one target device, the at least one target device including the second device. The second device sends feedback information to the first device; The feedback information includes at least one of the following: The first data transmission confirmation information; The first data includes transmission confirmation information for at least one target device; The second device corresponds to the transmission confirmation information of the second data; The first indication information is used to indicate whether the reason for the failure of the second data transmission is related to the transmission of the first data; The transmission confirmation information for the merged data corresponding to the second device, wherein the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data.

16. The method according to claim 15, wherein, Before the second device sends feedback information to the first device, the method further includes at least one of the following: The second device verifies the verification information corresponding to at least one target device in the received first data; The second device verifies the verification information of the first data in the received first data; The second device verifies the received second data; The second device merges the data corresponding to the second device in the first data it receives with the second data, and verifies the merged data.

17. The method according to claim 15 or 16, further comprising: The second device receives the second instruction information sent by the first device; The second indication information is used to indicate data-related information of the first data.

18. The method according to any one of claims 15-17, wherein, The first data is the first data retransmitted; or, The first data includes retransmitted data; or, The second data includes at least a portion of the retransmitted first data.

19. The method of claim 18, further comprising at least one of the following: The second device receives the first information sent by the first device; The second device receives the second information sent by the first device; The first information includes at least one of the following: The retransmission or initial transmission indication of the first data; the signal format of the retransmitted first data; the data-related information of the retransmitted first data; the resources of the retransmitted first data; and the identifier of the target device for receiving the retransmitted first data. The second information includes at least one of the following: The signal format of the first retransmitted data; the resources of the first retransmitted data; the resources of the second data; the signal format of the second data; and the identifier of the target device for receiving the second data.

20. The method of claim 18, further comprising at least one of the following: The second device receives the third information sent by the first device; The second device receives the fourth information sent by the first device; The third information includes at least one of the following: The first data includes: a retransmission or initial transmission indication of some data in the first data; the signal format of the first data; data-related information of the first data; resources of the first data; an identifier of the receiving object used to receive retransmitted data in the first data; an identifier of the receiving object used to receive newly transmitted data in the first data; and an identifier of the receiving object used to receive the first data. The fourth piece of information includes at least one of the following: The signal format of the first data; resources for retransmitted data; resources for the second data; the signal format of the second data; the identifier of the target device for receiving the second data.

21. The method according to claim 18, further comprising: The second device receives the fifth message sent by the first device; The fifth piece of information includes at least one of the following: The signal format of the first data; the resources of the first data; the signal format of the second data; the resources of the second data; the relevant information of the retransmitted data carried by the second data; The retransmission data carried by the second data carrier includes at least one of the following: Data-related information of the retransmitted data; location information of the retransmitted data within the second data; relationship between the retransmitted data and the first data to which it belongs.

22. The method according to any one of claims 19-21, wherein, The data-related information includes at least one of the following: The size of the first data; the format information of the verification information of the first data; the size of the data corresponding to each target device in the first data; the length of the sub-data block or code block corresponding to the first data; The format information of the verification information corresponding to each target device in the first data; the RV of the data corresponding to each target device in the first data; the RV of the first data; the correspondence between the sub-data block or code block corresponding to the first data and the target device.

23. The method according to any one of claims 15-22, further comprising at least one of the following: The second device receives a first configuration sent by the first device, wherein the first configuration is used to configure at least one of the resources, location and number of times the first data is repeatedly transmitted; The second device receives a second configuration sent by the first device, the second configuration being configured to schedule the transmission of second data simultaneously in the event of repeated transmission of the first data.

24. A data transmission apparatus, comprising: A transmitting module is used to transmit first data and second data corresponding to each of at least one target device, wherein the time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the at least one target device at least partially overlap, the receiving object of the first data is the at least one target device, and the receiving object of the second data is the corresponding target device. A receiving module is used to receive feedback information sent by a second device, wherein the at least one target device includes the second device; The feedback information includes at least one of the following: The first data transmission confirmation information; The first data includes transmission confirmation information for at least one target device; The second device corresponds to the transmission confirmation information of the second data; The first indication information is used to indicate whether the reason for the failure of the second data transmission is related to the transmission of the first data; The transmission confirmation information for the merged data corresponding to the second device, wherein the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data.

25. The apparatus according to claim 24, wherein, The sending module is specifically used for: The first data is subjected to target processing to obtain the first data to be transmitted; or, verification information is added to the information to be transmitted corresponding to the target device, and the first data to be transmitted is generated based on the information to be transmitted after adding the verification information. Transmit the first data to be transmitted; The target processing includes at least one of the following: Add the verification information corresponding to each target device to the data corresponding to each target device in the first data respectively; Add verification information to the first data; The first data is channel coded.

26. The apparatus according to claim 25, wherein, The sending module is specifically used for: The data corresponding to each target device in the first data to be transmitted is divided into data groups corresponding to each device; If the bit sequence length of a target data group is greater than the channel coding limit length, the target data group is divided into multiple sub-data groups; Channel coding is performed on the divided data groups.

27. The apparatus according to any one of claims 24-26, wherein, The first data is the first data retransmitted; or, The first data includes retransmitted data; or, The second data includes at least a portion of the retransmitted first data.

28. A data transmission apparatus, comprising: A receiving module is configured to receive first data transmitted by a first device and second data corresponding to a second device, wherein the time-frequency resources used to transmit the first data and the time-frequency resources used to transmit the second data corresponding to the second device at least partially overlap, and the receiving object of the first data is at least one target device, the at least one target device including the second device; The sending module is used to send feedback information to the first device; The feedback information includes at least one of the following: The first data transmission confirmation information; The first data includes transmission confirmation information for at least one target device; The second device corresponds to the transmission confirmation information of the second data; The first indication information is used to indicate whether the reason for the failure of the second data transmission is related to the transmission of the first data; The transmission confirmation information for the merged data corresponding to the second device, wherein the merged data is the data resulting from merging the second data and the data corresponding to the second device in the first data.

29. The apparatus of claim 28, further comprising a processing module for at least one of the following: Verify the verification information corresponding to at least one target device in the received first data; The verification information of the first data in the received first data is verified; Verify the received second data; The data corresponding to the second device in the first data received is merged with the second data, and the merged data is verified.

30. A communication device comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the data transmission method as claimed in any one of claims 1-14, or implementing the steps of the data transmission method as claimed in any one of claims 15-23.

31. A readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the data transmission method as claimed in any one of claims 1-14, or implement the steps of the data transmission method as claimed in any one of claims 15-23.

32. A computer program / program product, which, when executed by at least one processor, implements the steps of the data transmission method as claimed in any one of claims 1-14, or implements the steps of the data transmission method as claimed in any one of claims 15-23.

Images