WO2022170993A1

WO2022170993A1 - Data transmission method and apparatus

Info

Publication number: WO2022170993A1
Application number: PCT/CN2022/074370
Authority: WO
Inventors: 汪少波; 刘荣宽; 张鹏; 周国华
Original assignee: 华为技术有限公司
Priority date: 2021-02-10
Filing date: 2022-01-27
Publication date: 2022-08-18
Also published as: CN114915369A

Abstract

Provided are a data transmission method and apparatus. The method comprises: receiving a TB from a first terminal device, wherein the TB is used for carrying uplink data of the first terminal device; receiving first scheduling information from a network device, wherein the first scheduling information indicates that a second terminal device initially transmits a portion of the TB; and sending Z code block groups (CBGs) to the network device, wherein the TB comprises M CBGs, the Z CBGs are a portion of the M CBGs, Z is an integer greater than 0 and less than M, and M is an integer greater than 1. In the method, uplink data of a first terminal device can be sent to a network device by means of a second terminal device, and insofar as resources of the first terminal device are not consumed, the transmission rate of the uplink data of the first terminal device can be improved when the transmission rate of the first terminal device is affected by factors such as an uplink bandwidth and an antenna capability, such that the first terminal device can meet the rate requirements of a large uplink capacity.

Description

A data transmission method and device

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the priority of the Chinese patent application with the application number of 202110184899.7 and the application title of "A method and device for data transmission" filed with the China Patent Office on February 10, 2021, the entire contents of which are incorporated into this application by reference .

technical field

The present application relates to the field of communication technologies, and in particular, to a data transmission method and apparatus.

Background technique

The uplink data sent by the terminal equipment can be transmitted in two ways. Mode 1: Uplink data transmission based on transport block (TB), where TB is the form in which the media access control layer (MAC) sends data to the physical layer, and the TB will be transmitted in a transmission time interval (transmission time interval (transmission time interval). time interval, TTI). A TB is composed of code blocks (CBs), and a TB can be composed of one or more CBs. The second method is uplink data transmission based on a code block group (CBG). Wherein, a CBG may be composed of one or more CBs, and one or more CBGs may constitute a TB.

The transmission rate of uplink data sent by a terminal device is affected by factors such as uplink bandwidth and antenna capability, which limits the data transmission capability of the terminal device, thus failing to meet the rate requirement for large uplink capacity.

SUMMARY OF THE INVENTION

The present application provides a data transmission method and device for improving the transmission rate of uplink data.

In a first aspect, the present application provides a data transmission method. The execution body of the method is a terminal device or a module in the terminal device. Here, the terminal device is used as the execution body as an example for description. The method includes: receiving a transport block TB from a first terminal device; the TB is used to carry uplink data of the first terminal device; and receiving first scheduling information from a network device, where the first scheduling information indicates the initial transmission of the TB by the second terminal device Part; send Z coded block groups CBG to the network device; wherein, TB includes M CBGs, Z CBGs are part of M CBGs, Z is an integer greater than 0 and less than M, and M is an integer greater than 1.

By implementing the method described in the first aspect, the uplink data of the first terminal device can be sent to the network device through the second terminal device, and the transmission rate of the first terminal device can be set at the transmission rate of the first terminal device without consuming the resources of the first terminal device. When affected by factors such as uplink bandwidth and antenna capability, the transmission rate of uplink data of the first terminal device is increased, so that the first terminal device can meet the rate requirement of large uplink capacity. At the same time, the data transmission delay of the first terminal device can also be reduced.

In a possible implementation manner of the first aspect, the first scheduling information includes first information, where the first information indicates indexes of the Z CBGs in the M CBGs; or, receiving a first message from a network device, the first The message indicates the index of the Z CBGs among the M CBGs.

If the transmission of a part of the CBGs in the TB is dynamically instructed through the first scheduling information, for different TBs, the transmission of CBGs in different positions or indices can be instructed each time, which is more flexible to implement.

If the first message is statically instructed to transmit a part of the CBG in the TB, the effective time of the first message is relatively long, and the CBG of the corresponding index or position can be transmitted according to the instruction of the first message for a long period of time, that is, The network device does not need to indicate the CBG to be transmitted by the second terminal device every time the transmission of the second terminal device is scheduled, so that the resource overhead can be reduced.

In a possible implementation manner of the first aspect, the indices of the Z CBGs indicated by the first scheduling information are some or all of the H indices; the H indices are configured by the network device, and H is greater than or equal to Z the integer.

By semi-statically instructing the second terminal device to transmit a part of the CBG in the TB through the network device configuration and the first scheduling information, resource overhead can be reduced while maintaining flexibility.

In a possible implementation manner of the first aspect, the method further includes: receiving first indication information from the first terminal device, where the first indication information indicates the maximum number of CBGs included in the TB.

In a possible implementation manner of the first aspect, the first scheduling information includes a first process identifier, and the first process identifier is an identifier of a HARQ process for sending a hybrid automatic repeat request of a CBG in the TB.

In a possible implementation manner of the first aspect, the first process identifier and the second process identifier satisfy a mapping relationship, and the second process identifier is the identifier of the HARQ process of the TB sent by the first terminal device to the second terminal device.

Through a given mapping relationship, one identifier can be used to infer another identifier. In sideline and uplink data (including TB and CBG), SUE, CUE, and network equipment can align their understanding of the data to be transmitted to avoid confusion in data transmission. Or there was an error in the network device merging the data.

In a possible implementation manner of the first aspect, the mapping relationship is configured by a network device.

In a second aspect, the present application provides a data transmission method. The execution body of the method is a terminal device or a module in the terminal device. Here, the terminal device is used as the execution body as an example for description. The method includes: generating a transport block TB for carrying uplink data; the TB includes M coding block groups CBG, where M is an integer greater than 1; receiving second scheduling information from a network device, where the second scheduling information indicates a first terminal device A part of the TB is initially transmitted; X CBGs are sent to the network device according to the second scheduling information; wherein the X CBGs are a part of the M CBGs, and X is an integer greater than 0 and less than M.

In a possible implementation manner of the second aspect, the second scheduling information includes second information, where the second information indicates indices of the X CBGs in the M CBGs; or, receiving a second message from the network device, the second The message indicates the index of the X CBGs among the M CBGs.

In a possible implementation manner of the second aspect, the indices of the X CBGs indicated by the second scheduling information are some or all of the Y indices, the Y indices are configured by the network device, and Y is greater than or equal to X the integer.

In a possible implementation manner of the second aspect, the second scheduling information includes a first process identifier, and the first process identifier is an identifier of a HARQ process for sending a hybrid automatic repeat request of a CBG in the TB.

In a possible implementation manner of the second aspect, before sending X CBGs to the network device, the method further includes: receiving third scheduling information from the network device; the third scheduling information instructs the first terminal device to send to the second terminal device TB; send TB to the second terminal device.

In a possible implementation manner of the second aspect, the third scheduling information includes a second process identifier, and the second process identifier is an identifier of the HARQ process that sends the TB to the second terminal device.

In a possible implementation manner of the second aspect, the identifiers of the HARQ processes that send X CBGs to the network device are the first process identifiers; the first process identifiers and the second process identifiers satisfy a mapping relationship, and the mapping relationship is the network device configuration of.

In a possible implementation manner of the second aspect, the method further includes: receiving a first feedback message from the second terminal device, where the first feedback message indicates that the M CBGs included in the TB are correctly received by the second terminal device the CBG and/or the CBG not correctly received by the second terminal device.

In a possible implementation manner of the second aspect, the method further includes: sending a second feedback message to the network device, where the second feedback message indicates that among the M CBGs included in the TB, the CBG and CBG correctly received by the second terminal device /or CBG not correctly received by the second terminal device.

In a possible implementation manner of the second aspect, receiving the second scheduling information from the network device includes: receiving a Uu interface grant from the network device in a multicast manner, where the Uu interface grant includes the second scheduling information.

In a possible implementation manner of the second aspect, the Uu interface authorization adopts a group RNTI for scrambling, and the group RNTI is configured by the network device.

In a third aspect, the present application provides a data transmission method. The execution body of the method is a network device or a module in the network device. Here, the network device is used as the execution body as an example for description. The method includes: sending third scheduling information to the first terminal device; the third scheduling information instructs the first terminal device to send a transport block TB to the second terminal device; the TB includes M coding block groups CBG, where M is an integer greater than 1; The TB is used to carry the uplink data of the first terminal device; the first scheduling information is sent to at least one second terminal device; the first scheduling information indicates that the second terminal device initially transmits a part of the TB; L CBGs are received; A second terminal device; the TB is determined according to the L CBGs; wherein the L CBGs are the CBGs in the TB, and L is an integer greater than 0.

In a possible implementation manner of the third aspect, the method further includes: sending second scheduling information to the first terminal device; the second scheduling information indicates that the first terminal device initially transmits a part of the TB; receiving information from the first terminal device X CBGs; X CBGs are part of M CBGs, and X is an integer greater than 0.

In a possible implementation manner of the third aspect, X+L is greater than or equal to M; determining the TB according to the L CBGs includes: determining the TB according to the L CBGs and the X CBGs.

In a possible implementation manner of the third aspect, the second scheduling information includes second information, and the second information indicates indices of the X CBGs in the M CBGs.

In a possible implementation manner of the third aspect, the number of CBGs received from a second terminal device is Z, and Z is an integer greater than 0 and less than L; the first scheduling information includes first information, the first The information indicates the indices of the Z CBGs in the M CBGs.

In a possible implementation manner of the third aspect, before sending the third scheduling information to the first terminal device, the method further includes: sending a second message to the first terminal device, where the second message indicates that the X CBGs are within the M CBGs index in;

Send a first message to the second terminal device, where the first message indicates the indices of the Z CBGs in the M CBGs.

In a possible implementation manner of the third aspect, the indices of the X CBGs indicated by the second scheduling information are some or all of the Y indices; the Y indices are configured by the network device, and Y is greater than or equal to X the integer.

In a possible implementation manner of the third aspect, the indices of the Z CBGs indicated by the first scheduling information are some or all of the H indices; the H indices are configured by the network device, and H is greater than or equal to Z the integer.

In a possible implementation manner of the third aspect, the third scheduling information includes a second process identifier, and the second process identifier is an identifier of a hybrid automatic repeat request HARQ process used for sending the TB.

In a possible implementation manner of the third aspect, the first scheduling information includes a first process identifier, and the first process identifier is an identifier of the HARQ process that sends the CBG in the TB; wherein the first process identifier and the second process identifier The mapping relationship is satisfied, and the mapping relationship is configured by the network device.

In a possible implementation manner of the third aspect, the method further includes: receiving a second feedback message from the first terminal device, where the second feedback message indicates that the M CBGs included in the TB are correctly received by the second terminal device the CBG and/or the CBG not correctly received by the second terminal device.

In a possible implementation manner of the third aspect, the first scheduling information and the third scheduling information are carried in the multicast Uu interface authorization.

In a possible implementation manner of the third aspect, the Uu interface authorization uses the group wireless network temporary identifier RNTI for scrambling, and the group RNTI is configured by the network device.

In a fourth aspect, the present application further provides a communication device having any of the methods provided in any one of the first to third aspects above. The communication device may be implemented by hardware, or by executing corresponding software by hardware. The hardware or software includes one or more units or modules corresponding to the above functions.

In a possible implementation manner, the communication apparatus includes: a processor, and the processor is configured to support the communication apparatus to perform the corresponding functions of the terminal device or the network device in the above-described method. The communication device may also include a memory, which may be coupled to the processor, which holds program instructions and data necessary for the communication device. Optionally, the communication device further includes a communication interface for supporting communication of the communication device.

In a possible implementation manner, the communication device includes corresponding functional modules, which are respectively used to implement the steps in the above method. The functions can be implemented by hardware, or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions.

In a possible implementation manner, the structure of the communication device includes a processing unit and a communication unit, and these units can perform the corresponding functions in the foregoing method examples. For details, refer to the method provided in any one of the first to third aspects. description, which will not be repeated here.

The apparatus may be a base station, a gNB or a TRP, etc., and the communication unit may be a transceiver or an interface circuit. Optionally, the transceiver may also be an input/output circuit or an interface.

The apparatus may be a smart terminal or a wearable device, etc., and the communication unit may be a transceiver or an interface circuit. Optionally, the transceiver may also be an input/output circuit or an interface.

In a fifth aspect, a communication device is provided, comprising a processor and an interface circuit, the interface circuit is configured to receive signals from other communication devices other than the communication device and transmit to the processor or send signals from the processor For other communication devices other than the communication device, the processor is used to implement the method in the first aspect or any possible implementation manner of any of the foregoing aspects through logic circuits or executing code instructions.

In a sixth aspect, a communication device is provided, comprising a processor and an interface circuit, the interface circuit is configured to receive signals from other communication devices other than the communication device and transmit to the processor or send signals from the processor For other communication devices other than the communication device, the processor is used to implement the functional modules of the method in the second aspect and any possible implementation manner of the second aspect through logic circuits or executing code instructions.

In a seventh aspect, a communication device is provided, comprising a processor and an interface circuit, the interface circuit is configured to receive signals from other communication devices other than the communication device and transmit to the processor or send signals from the processor For other communication devices other than the communication device, the processor is used to implement the functional modules of the third aspect and the method in any possible implementation manner of the third aspect through logic circuits or executing code instructions.

In an eighth aspect, a computer-readable storage medium is provided, and a computer program or instruction is stored in the computer-readable storage medium. When the computer program or instruction is executed by a processor, the aforementioned first to third aspects are implemented. A method in any possible implementation of any aspect.

In a ninth aspect, there is provided a computer program product comprising instructions that, when executed by a processor, implement the method in any possible implementation manner of any of the foregoing first to third aspects.

In a tenth aspect, a chip is provided, the chip includes a processor, and may further include a memory, for implementing the method in any possible implementation manner of any one of the foregoing first to third aspects. The chip may consist of chips, or may contain chips and other discrete devices.

In an eleventh aspect, a communication system is provided, the system comprising the apparatus of the fifth aspect (eg, the second terminal device), the apparatus of the sixth aspect (eg, the first terminal device), and the seventh aspect devices (such as network equipment).

Description of drawings

FIG. 1 is a schematic diagram of a network architecture applicable to an embodiment of the present application;

2 is a schematic flowchart of a data transmission method provided by an embodiment of the present application;

3 is a schematic flowchart of a data transmission method according to an embodiment of the present application;

4 is a schematic flowchart of a data transmission method provided by an embodiment of the present application;

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

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

FIG. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Detailed ways

The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as long term evolution (long term evolution, LTE) systems, new radio (new radio, NR) systems, and next-generation communication systems, etc., which are not limited here.

In this embodiment of the present application, the terminal device may be a device with a wireless transceiver function or a chip that may be provided in any device, and may also be called user equipment (user equipment, UE), access terminal, or other names. The terminal device in the embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal, a wireless terminal in a smart grid (smart grid), Wireless terminals in transportation safety, etc. The terminal device may support at least one of a device-to-device (D2D) technology, a vehicle-to-vehicle (V2V) technology, and a vehicle-to-Everything (V2X) technology.

The network equipment may refer to access network equipment, for example, it may be a next generation base station (next Generation node B, gNB) in an NR system, or an evolved base station (evolutional node B, eNB) in an LTE system, etc.

As shown in FIG. 1 , it is a schematic diagram of a network architecture applicable to the embodiment of the present application. The network device in FIG. 1 may provide communication services for multiple terminal devices, and FIG. 1 takes three terminal devices (respectively, terminal device 1 to terminal device 3 ) as an example for description. Data can be sent directly between two terminal devices without forwarding through network devices, thereby reducing data delay. It should be noted that, in the D2D and V2X technologies, the communication interface between the terminal device and the terminal device is called a PC5 interface (interface), and the corresponding link is called a sidelink (SL). Correspondingly, the communication interface between the terminal device and the network device is called a Uu interface.

The embodiments of the present application can be applied to various transmission scenarios. For example, in a possible scenario, the uplink transmission of the Uu interface is based on CBG, and the sidelink transmission of the PC5 interface is based on TB. That is to say, the data transmission between the terminal device and the terminal device is based on the TB granularity; the data transmission between the terminal device and the network device is based on the CBG granularity.

It should be noted that when the terminal device sends uplink data to the network device, the process for the terminal device to group CBs into CBGs is as follows:

When the received high-level parameter code block group transmission (code block group transmission) is configured as CBG-based transmission, the terminal device uses the following formula to determine the number of CBGs transmitted on a physical uplink shared channel (PUSCH) M, that is, to determine the number of CBGs included in a TB:

M=min(N, C)...(1);

Among them, min represents the operation of taking the minimum value, and N is the maximum number of CBGs in each TB, which is configured through the radio resource control (RRC) message. Specifically, the maximum coding block group can be transmitted through the high-level parameter in the RRC message. Block (maxCodeBlockGroupsPerTransportBlock) configuration; C is the number of CBs to be transmitted in the PUSCH, and the terminal device can determine the value of C according to the actual amount of data to be transmitted. The RRC message of configuration N may be a PUSCH-ServingCellConfig message.

The CBG-based transmission of the terminal device is as follows:

When the terminal device determines to be configured for CBG-based transmission according to the received high-level parameters, for the initial transmission TB, the terminal device expects to receive the CBG transmission indication (CBG transmission) in the downlink control information (DCI). information, CBGTI) field indicates that all the CBGs of the TB will be transmitted, and the transmission of the terminal device should include all the CBGs of the TB, wherein the initial transmission of the TB is indicated by the new data indicator (NDI) field of the DCI. That is, for the initial transmission, the terminal device needs to transmit the entire TB. For retransmission of TB, the transmission of the terminal device should only include the CBG indicated by the CBGTI field, where the retransmission of the TB is indicated by the NDI field of the DCI.

Because the terminal equipment is affected by factors such as uplink bandwidth and antenna capability, the ability of the terminal equipment to transmit uplink data is limited and cannot meet the rate requirement of large uplink capacity. In the embodiment of the present application, through coordinated transmission of multiple terminal devices, the rate of uplink large capacity can be increased and the delay can be reduced. Taking FIG. 1 as an example, the terminal device 1 can send the uplink data to the terminal device 2 and the terminal device 3 through the side link, and the terminal device 2 and the terminal device 3 then forward the uplink data to the network device. Among them, terminal equipment 1 is the source of data, which can be called source user equipment (source UE, SUE), and SUE can also have other names, such as source UE or originating UE, etc.; terminal equipment 2 and terminal equipment 3 are used to assist The SUE performs data transmission, which may be called cooperative user equipment (cooperative UE, CUE). CUE may also have other names, such as auxiliary UE or relay UE. The embodiments of this application do not limit the names of SUE and CUE. The above process will be described in detail below.

The network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. The evolution of the architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

In the following Embodiments 1 to 7, two CUEs (respectively the first CUE and the second CUE) assist the SUE to send the uplink data of the SUE to the network device as an example for description. In practical applications, the number of CUEs may be greater than 2, or less than 2, which is not limited in this embodiment of the present application.

It should be noted that each of the embodiments described in the embodiments of the present application may be independent solutions, or may be combined according to internal logic, and these solutions all fall within the protection scope of the present application.

Example 1:

In the first embodiment, the network device dynamically instructs the CUE and the CBG that the SUE needs to send through the Uu authorization (grant), and the Uu grant can be understood as control information or scheduling information sent by the network device, such as a kind of downlink control information DCI) format. It will be described in detail below.

As shown in FIG. 2 , a schematic flowchart of a data transmission method provided by an embodiment of the present application is shown. In the flow of FIG. 2 , the SUE needs to send the first TB to the network device as an example for description, and the first TB carries the uplink data that the SUE needs to send to the network device.

Optionally, S201: the network device sends a first RRC message to the SUE.

The first RRC message includes coded block group transmission information and maximum coded block group information, the coded block group transmission information indicates uplink transmission based on CBG granularity, and the maximum coded block group information indicates the maximum number of CBGs included in a TB. Wherein, the uplink transmission is performed based on the granularity of CBG, which may mean that the minimum granularity of uplink transmission is CBG.

It should be noted that the name of the first RRC message is not limited. For example, it can be a PUSCH serving cell configuration (PUSCH ServingCellConfig) message. At this time, the coding block group transmission information can be the parameter codeBlockGroupTransmission in PUSCH ServingCellConfig, and the maximum coding block group information can be It is the parameter maxCodeBlockGroupsPerTransportBlock in PUSCH ServingCellConfig.

In the embodiment of the present application, when the SUE sends the TB to the CUE through the sidelink, the SL hybrid automatic repeat request (HARQ) process may be used, and the SUE may use the Uu HARQ process when sending the TB to the network device through the Uu. Both the SL HARQ process and the Uu HARQ process correspond to an identifier, which is used to identify different data or HARQ processes corresponding to different data. The identifier of the SL HARQ process is the sidelink hybrid automatic repeat request process identifier (SL HARQ process identity, SL HPID), the identifier of the Uu HARQ process is the Uu interface hybrid automatic repeat request process identifier (Uu HARQ process ID, Uu HPID).

The network device may configure the mapping relationship between the SL HPID and the Uu HPID to the SUE. For example, the first RRC message includes mapping relationship information, where the mapping relationship information indicates the mapping relationship. Alternatively, the mapping relationship between the SL HPID and the Uu HPID is pre-configured for the SUE, and similar to the CUE, the mapping relationship can also be pre-configured for the CUE.

The SL HPID and Uu HPID in the mapping relationship correspond to the same TB, that is, the SL HPID of the SL HARQ process used by the SUE to send the TB to the CUE is the same as the SL HPID of the SL HARQ process used by the SUE to send the TB (or the TB in the TB) to the network device. There is a mapping relationship between the Uu HPID of the Uu HARQ process used when part of the CBG).

In the embodiment of the present application, the specific form of the mapping relationship is not limited, as long as another identification can be determined from one identification in the SL HPID and the Uu HPID according to the mapping relationship. For example, the mapping relationship is: SL HPID is equal to Uu HPID; for another example, the mapping relationship is: Uu HPID=15-SL HPID.

For example, SUE needs to send the first TB, SUE has 16 SL HARQ processes, SL HPID is x, x=0,1,...,15, SUE has 16 Uu HARQ processes, Uu HPID is y, y=0 ,1,…,15. Assuming that the mapping relationship is y=x, that is, the SL HPID of the SL HARQ process used by the SUE to send the TB to the CUE, and the Uu HPID of the Uu HARQ process used by the SUE to send the TB (or part of the CBG in the TB) to the network device equal. When the SL HPID used by the SUE to transmit the first TB in the SL is 0, then the Uu HPID of the SUE transmitting the first TB in the Uu is 0; when the SL HPID used by the SUE when transmitting the first TB in the SL is 12, then the SUE The Uu HPID of the first TB transmitted by Uu is 12, and other cases will not be illustrated one by one.

Assuming that the mapping relationship is y=15-x, when the SL HPID used by the SUE to transmit the first TB in the SL is 0, the Uu HPID of the first TB transmitted by the SUE in the Uu is 15=15-0; The SL HPID used in the first TB is 12, then the Uu HPID of the SUE transmitting the first TB in the Uu is 3=15-12, and other cases will not be illustrated one by one.

It should be noted that the network device may indicate the mapping relationship between the SL HPID and the Uu HPID through the first RRC message, and may also indicate the mapping relationship through other messages, which is not limited in this embodiment of the present application.

Optionally, S202: the network device sends a second RRC message to the first CUE, and sends a third RRC message to the second CUE.

It should be noted that the role and information carried by the second RRC message are similar to the role and information carried by the third RRC message. The following will take the second RRC message as an example for description. For the specific content of the third RRC message, please refer to Description of the second RRC message. In Embodiment 1, two CUEs are used as an example for description. In practical applications, the number of CUEs is not limited. Therefore, the number of actually sent RRC messages is not limited, and can be understood as being related to the number of CUEs and SUEs.

The second RRC message includes mapping relationship information, where the mapping relationship information indicates the mapping relationship between the SL HPID and the Uu HPID. The SL HPID and Uu HPID in the mapping relationship correspond to the same TB, that is to say, the SL HPID of the SL HARQ process used by the SUE to send the TB to the CUE is the same as the SUE sending the TB (or the CBG in the TB) to the network device. There is a mapping relationship between the Uu HPID of the Uu HARQ process used at the time.

Optionally, the second RRC message may include coded block group transmission information and maximum coded block group information, the coded block group transmission information in the second RRC message indicates that uplink transmission is performed based on the granularity of the CBG, and the maximum coded block group in the second RRC message. The coding block group information indicates the maximum number of CBGs included in one TB.

The maximum number of CBGs included in one TB indicated by the network device to the SUE is equal to the maximum number of CBGs included in one TB indicated to the CUE (including the first CUE and the second CUE), both being N.

It should be noted that the name of the second RRC message is not limited. For example, it can be a PUSCH serving cell configuration (PUSCH ServingCellConfig) message. In this case, the coding block group transmission information can be the parameter codeBlockGroupTransmission in PUSCH ServingCellConfig, and the maximum coding block group information can be It is the parameter maxCodeBlockGroupsPerTransportBlock in PUSCH ServingCellConfig.

Optionally, in another possible implementation manner, the SUE sends a PC5 RRC message to the first CUE, where the PC5 RRC message includes first indication information and second indication information, and the first indication information is used to indicate the maximum number of CBGs included in a TB. , and the second indication information is used to indicate uplink transmission based on CBG granularity. Similarly, the SUE indicates to the second CUE through the PC5 RRC message to perform uplink transmission based on CBG granularity, and indicates the maximum number of CBGs included in one TB.

It should be noted that the execution order of S201 and S202 is not limited, and may be executed sequentially or simultaneously.

Optionally, S203: the SUE sends a sidelink buffer status report (SL BSR) to the network device, where the SL BSR is used to request the network device to allocate SL resources.

The SL resource requested by the SL BSR is used to transmit the uplink data of the SUE to the CUE. It should be noted that, unless otherwise specified, the CUE refers to the UE that assists the SUE in transmitting uplink data, including the first CUE and the second CUE.

In the embodiment of the present application, since the data transmission of the sidelink is based on TB, the SUE actually transmits the uplink data to the CUE through the SL resource in the TB manner. That is to say, the SL resource requested by the SL BSR is used for The TB is transmitted to the CUE. For convenience of description, in the following description, the TB to be transmitted by the SUE is referred to as the first TB.

The specific implementation manner of the SL BSR is not limited in this embodiment of the present application, and will not be repeated here.

S204: The network device sends an SL grant (grant) to the SUE, and the SL grant instructs the SUE to send the first TB to the CUE.

Specifically, the SL grant may indicate the SL resource, and the SUE may send the TB to the CUE through the SL resource indicated by the SL grant.

The SL grant also includes at least one of the first SL HPID and the first Uu HPID, and the first SL HPID and the first Uu HPID satisfy a mapping relationship, and the mapping relationship is indicated by the mapping relationship information in S202. The first SL HPID is the identifier of the SL HARQ process of the first TB sent by the SUE to the CUE through the SL resource; the first Uu HPID is the identifier of the Uu HARQ process that the SUE sends the first TB or the CBG in the first TB on the Uu .

It should be noted that when the SUE and the CUE respectively send the first TB or the CBG in the first TB to the network device, the identifiers of the Uu HARQ processes used are the same, which are the first Uu HPID.

S205: The SUE sends the first TB to the CUE.

Specifically, the SUE may send the first TB to the first CUE and the second CUE through the SL resource indicated by the SL grant.

In a possible manner, the SUE sends the first TB to the first CUE and the second CUE respectively in a unicast manner.

In another possible manner, the SUE sends the first TB to the first CUE and the second CUE in a multicast manner. Wherein, the SL HPID of the first TB sent by the SUE on the SL resource is indicated by the SL grant.

It should be noted that the first CUE can determine the first Uu HPID used when the SUE sends the first data TB to the network device according to the mapping relationship between the SL HPID and the Uu HPID, and the first SL HPID indicated by the SL grant. For example, when the SL HPID is x, the UL HPID is y, the mapping relationship between the SL HPID and the UL HPID is y=15-x, and the first SL HPID indicated by the SL grant is 6, the first CUE can use the mapping relationship with the SL grant Indicate, determine that the first Uu HPID is 9. Similarly, the second CUE can also determine the first Uu HPID, which is not repeated here.

Optionally, S206: The network device sends a first Uu interface grant (Ugrant) to the SUE, where the first Uu grant instructs the SUE to initially transmit a part of the first TB.

Wherein, a part of the first TB is transmitted through the PUSCH, and the network device, the SUE, and the CUE can determine the number of CBGs obtained when the first TB is divided into CBGs through the foregoing formula (1). For the convenience of description, the following description will be given by taking dividing the first TB into M CBGs as an example, where M is an integer greater than 1.

The first Uu grant may include the first Uu HPID. The SUE may determine the Uu HARQ process to use according to the first Uu HPID, and determine that the first TB needs to be transmitted. For example, the SUE determines the first SL HPID according to the first Uu HPID and the mapping relationship between the SL HPID and the Uu HPID; the SUE determines the TB sent to the CUE using the SL HARQ process corresponding to the first SL HPID as the first SL to be transmitted. TB.

The first Uugrant may also include the NDI domain and the CBGTI domain. The NDI field indicates that the SUE performs initial transmission; the CBGTI field indicates the number X of CBGs transmitted by the SUE, and the indices or positions of the X CBGs in the M CBGs included in the first TB, where X is an integer greater than 0 and less than M. That is, even for Uu initial transmission, the CBG transmitted by the SUE may only include a part of the CBG of the first TB.

In the embodiment of the present application, the SUE is dynamically instructed to transmit a part of the CBG in the first TB through the first Uugrant. For different TBs, the transmission of CBGs in different locations or indices can be instructed each time, which is more flexible to implement.

Optionally, the CBGTI field can be indicated by a bitmap. A bit in the bitmap corresponds to a CBG in the first TB. When the value of a bit in the bitmap is the first value, it means The CBG corresponding to this bit will be sent; when a bit in the bitmap takes the second value, it means that the CBG corresponding to this bit will not be sent. The first value and the second value can be determined according to specific conditions. For example, the first TB includes 3 CBGs with a first value of 1 and a second value of 0. When the CBGTI field is 100, it means that the first Uugrant instructs the SUE to send the first CBG in the first TB, but not the second and third CBGs.

The first Uugrant may also include other information, for example, may also include time-frequency resources and modulation and coding scheme (modulation and coding scheme, MCS) indication information used to instruct the SUE to transmit the CBG, etc., which will not be repeated here.

Optionally, the first Uugrant and the SL grant may be one signaling or two signaling. When the first Uu grant and the SL grant are one signaling, a signaling sent by the network device may include the first Uu grant and the SL grant at the same time.

S207, the network device sends the second Uugrant to the first CUE, and sends the third Uugrant to the second CUE.

Wherein, the second Uugrant is used to instruct the first CUE to initially transmit a part of the first TB, and the third Uugrant is used to instruct the second CUE to initially transmit a part of the first TB. The information included in the second Uugrant and the third Uugrant is similar. The following takes the second Uugrant as an example for description. For the information included in the third Uugrant, refer to the description of the second Uugrant, which will not be repeated here.

The second Uu grant includes the first Uu HPID for indicating the identity of the Uu HARQ process in which the first CUE transmits a part of the first TB. The first CUE may determine the CBG to be transmitted according to the first Uu HPID and the mapping relationship between the SL HPID and the Uu HPID. For example, the first CUE determines the first SL HPID according to the first Uu HPID and the mapping relationship between the SL HPID and the Uu HPID; the first CUE determines, among the received TBs, the TB corresponding to the first SL HPID as the one that needs to be initially transmitted First TB. Wherein, the TB corresponding to the first SL HPID may mean that the TB is sent to the first CUE by the SUE through the SL HARQ process corresponding to the first SL HPID.

In this embodiment of the present application, the second Uugrant may further include an NDI field, and the NDI field instructs the first CUE to perform Uu initial transmission. That is, even for Uu initial transmission, the CBG transmitted by the first CUE may only include a part of the CBG of the first TB.

The second Uugrant may further include a CBGTI field, where the CBGTI field indicates the number Z of CBGs transmitted by the first CUE, and the indices or positions of the Z CBGs in the M CBGs included in the first TB, where Z is greater than 0 and less than M the integer.

In the embodiment of the present application, the second Uugrant dynamically instructs the first CUE to transmit a part of the CBG in the first TB. For different TBs, the transmission of CBGs in different locations or indexes can be instructed each time, which is more flexible to implement.

Optionally, the CBGTI field can be indicated in the form of a bitmap. A bit in the bitmap corresponds to a CBG in the first TB. When the value of a bit in the bitmap is the first value, it indicates that the bitmap corresponds to the bitmap. The corresponding CBG will be sent; when the value of a bit in the bitmap is the second value, it indicates that the CBG corresponding to the bit will not be sent. The first value and the second value can be determined according to specific conditions. For example, the first TB includes 3 CBGs with a first value of 1 and a second value of 0. When the CBGTI field in the second Uugrant is 010, it indicates that the second Uugrant instructs the first CUE to send the second CBG in the first TB, but not the first CBG and the third CBG.

The second Uugrant may also include other information, for example, may also include indication information indicating the time-frequency resource and MCS used by the first CUE to transmit the CBG, and the like, which will not be repeated here.

Optionally, in S208, the SUE sends X CBGs to the network device.

S209: The first CUE sends Z CBGs to the network device.

S210: The second CUE sends Z CBGs to the network device.

The execution order of S208 to S210 is not limited, and may be executed sequentially or simultaneously, which is not limited herein.

It should be noted that X+2Z is greater than or equal to M. Here, the first CUE and the second CUE send the same number of CBGs as an example for description. In practical applications, the number of CBGs sent by the first CUE to the network device may be different from the number of CBGs sent by the second CUE to the network device. Specifically, it is determined according to the actual situation, which is not limited in this application.

Finally, the network device can obtain the first TB according to the received X+2Z CBGs. For example, the first TB includes CBG0, CBG1, and CBG2; after the network device receives X+2Z CBGs, it can obtain CBG0, CBG1, and CBG2 from the X+2Z CBGs, so as to recover through CBG0, CBG1, and CBG2 The first TB is the first TB.

It should be noted that the flow in FIG. 2 is just an example. In practical applications, some steps are optional and do not necessarily need to be executed. For example, steps such as S206 and S208 can be selectively executed.

According to the previous process, the previous process is described below through a specific example:

(1) The network device instructs the SUE, the first CUE, and the second CUE to perform uplink transmission based on CBG granularity through an RRC message, and configures a maximum number of CBGs included in one TB to be 3. The network device configures the SUE, the first CUE, and the second CUE to configure the mapping relationship between the SL HPID and the Uu HPID as y=15-x, where the SL HPID is x and the Uu HPID is y.

(2) The SUE sends the SL BSR to the network device to request the network device to allocate SL resources.

It is assumed that the uplink data to be transmitted by the SUE is carried in the first TB.

(3) The network device sends the SL grant to the SUE, the SL grant instructs the SUE to send data on the SL resource allocated by the network device, and the SL grant indicates that the SL HPID is 6.

(4) The SUE sends the first TB to the first CUE and the second CUE on the SL resource.

The SL HPID of the SL HARQ process used when the SUE sends the first TB is 6.

The first CUE and the second CUE can determine that the Uu HPID mapped with the SL HPID is 9 according to the mapping relationship between the SL HPID and the Uu HPID, and determine that the Uu HARQ process corresponding to the Uu HPID is 9 corresponds to the first TB.

(5) The network device sends the first Uugrant to the SUE, and the first Uugrant indicates that the Uu HPID is 9.

According to the Uu HPID and the mapping relationship between the SL HPID and the Uu HPID, the SUE may determine that the CBG in the first TB needs to be initially transmitted.

It is assumed that the network device, the SUE and the CUE can divide the first TB into CBGs, which are CBG0 , CBG1 , and CBG2 respectively, according to the maximum number of CBGs included in a TB 3 and the preceding formula (1).

The first Uugrant also includes a CBGTI field, and the CBGTI field is 100. The SUE may determine, according to the CBGTI field, the first CBG that sends the first TB, that is, CBG0.

Similarly, the network device sends a second Uugrant to the first CUE, the second Uugrant indicates that the Uu HPID is 9, and the CBGTI field in the second Uugrant is 010. The first CUE may determine, according to the second Uugrant, that the second CBG in the first TB, that is, CBG1, needs to be initially transmitted.

Similarly, the network device sends a third Uugrant to the second CUE, the third Uugrant indicates that the Uu HPID is 9, and the CBGTI field in the third Uugrant is 001. The second CUE may determine, according to the third Uu grant, that the third CBG in the first TB, that is, CBG2, needs to be initially transmitted.

(6) The SUE sends the CBG0 in the first TB to the network device according to the instruction of the first Uugrant, the first CUE sends the CBG1 in the first TB to the network device according to the instruction of the second Uugrant, and the second CUE sends the CBG1 in the first TB according to the third Uu grant The indication of the grant sends the CBG2 in the first TB to the network device.

Finally, when the network device correctly receives CBG0, CBG1, and CBG2, the first TB including the uplink data of the SUE can be obtained.

Through the above process, the SUE completely sends the first TB to at least one CUE at the SL. The SUE and at least one CUE can respectively determine which TB of the SUE is transmitted by the Uu transmission based on the CBG through the mapping relationship between the SL HPID and the Uu HPID, and divide the TB to obtain multiple CBGs. The network device can dynamically indicate the CBG that each UE needs to transmit through Uu grant, and can realize the uplink coordination of CBG granularity even in the initial transmission of Uu. In uplink cooperative transmission, SUE and at least one CUE transmit based on CBG granularity during initial transmission, which can overcome the problems of limited antenna and bandwidth of SUE, meet the transmission rate requirement of large uplink capacity, and reduce data delay.

Embodiment 2:

The main difference from the first embodiment is that in the second embodiment, the network device indicates the CUE and the CBG to be sent by the SUE through an RRC message, which will be described in detail below.

As shown in FIG. 3 , a schematic flowchart of a data transmission method provided by an embodiment of the present application is shown. In the process of FIG. 3 , description is made by taking the SUE needing to send the first TB to the network device as an example, and the first TB carries the uplink data of the SUE.

S301: The network device sends a first RRC message to the SUE.

The first RRC message may instruct the SUE to perform uplink transmission based on the granularity of the CBG, and the maximum coding block group information indicates the maximum number N of CBGs included in one TB. The first RRC message may also indicate the mapping relationship between the SL HPID and the Uu HPID, and the like. For the specific content of the first RRC message, reference may be made to the description in S201, which will not be repeated here.

The number of CBGs included in the first TB may be determined according to N, and specifically, the number M of CBGs included in the first TB may be determined by the foregoing formula (1).

In Embodiment 2, the network device may also send a fourth RRC message to the SUE, where the fourth RRC message indicates the number X of CBGs sent by the SUE, and the indices or positions of the X CBGs in the M CBGs included in the first TB .

In the embodiment of the present application, the SUE is statically instructed to transmit a part of the CBG in the first TB through the RRC message, and the RRC message takes effect for a long time. CBG, that is to say, the network device does not need to indicate the CBG that the SUE needs to transmit every time the SUE is scheduled to transmit, so that the resource overhead can be reduced.

It should be noted that, in FIG. 3 , the fourth RRC message and the first RRC message are the same message as an example for illustration. The fourth RRC message and the first RRC message may be the same message, or may be two different messages, which are not limited in this application.

Optionally, the fourth RRC message may include a CBGTI field, and the CBGTI field may indicate the number X of CBGs sent by the SUE, and the indices or positions of the X CBGs in the M CBGs included in the first TB. For example, the CBGTI field is a bitmap, a bit in the bitmap corresponds to a CBG in the first TB, and when the value of a bit in the bitmap is the first value, it means that the CBG corresponding to the bit will be sent; When the value of a bit in the bitmap is the second value, it indicates that the CBG corresponding to the bit will not be sent. The first value and the second value can be determined according to specific conditions. For example, the first TB includes 3 CBGs with a first value of 1 and a second value of 0. When the CBGTI field is 100, it indicates that the SUE is instructed to send the first CBG in the first TB, but not the second and third CBGs.

S302: The network device sends a second RRC message to the first CUE, and sends a third RRC message to the second CUE.

It should be noted that the function and information carried by the second RRC message are similar to the function and information carried by the third RRC message.

Optionally, the second RRC message may include encoding block group transmission information and maximum encoding block group information, for details, please refer to the description in S202, and details are not repeated here.

Optionally, in another possible implementation manner, the SUE sends a PC5 RRC message to the first CUE, and the PC5 RRC message includes the first indication information and the second indication information. For details, please refer to the description in S202, which will not be repeated here.

In Embodiment 2, the network device may also send a fifth RRC message to the first CUE, where the fifth RRC message indicates the number Z of CBGs sent by the first CUE, and the Z CBGs are among the M CBGs included in the first TB index or location. Similarly, the network device may also indicate to the second CUE the number Z of CBGs to be sent, and the indices or positions of the Z CBGs in the M CBGs included in the first TB, which will not be repeated here.

It should be noted that, in FIG. 3 , the fifth RRC message and the second RRC message are the same message as an example for illustration. The fifth RRC message and the second RRC message may be the same message, or may be two different messages, which are not limited in this application.

Optionally, the fifth RRC message may include a CBGTI field, and the CBGTI field may indicate the number Z of CBGs sent by the first CUE, and the indices or positions of the Z CBGs in the H CBGs included in the first TB. For details, please refer to The description in the fourth RRC message will not be repeated here.

In the embodiment of the present application, the CUE is statically instructed to transmit a part of the CBG in the first TB through the RRC message. The RRC message takes effect for a long time, and the CUE can transmit the corresponding index or location according to the instruction of the RRC message for a long period of time. CBG, that is to say, the network device does not need to indicate the CBG that the CUE needs to transmit every time the CUE is scheduled to transmit, so that the resource overhead can be reduced.

It should be noted that the execution order of S301 and S302 is not limited, and may be executed sequentially or simultaneously.

S303: The SUE sends an SL BSR to the network device, where the SL BSR is used to request the network device to allocate SL resources.

The SL resource requested by the SL BSR is used to transmit the uplink data of the SUE to the CUE.

S304: The network device sends the SL grant to the SUE, and the SL grant instructs the SUE to send the first TB to the CUE.

For the specific content of the SL grant, refer to the description in S204, which will not be repeated here.

S305: The SUE sends the first TB to the CUE.

For the specific content of this step, reference may be made to the description in S205, which will not be repeated here.

S306: The network device sends the first Uugrant to the SUE, and the first Uugrant instructs the SUE to initially transmit a part of the first TB.

It should be noted that the part of the first TB here refers to the X CBGs indicated by the fourth RRC message.

For example, the bitmap included in the fourth RRC message is 100. At this time, the first Uugrant instructs the SUE to initially transmit a part of the first TB, which means that the SUE needs to initially transmit the first CBG in the first TB, and does not send the second A CBG and a third CBG.

The first Uu grant includes the first Uu HPID and the NDI field, and the NDI field instructs the SUE to perform Uu initial transmission. The first Uugrant may also include other information, for example, may also include indication information of the time-frequency resource and MCS used by the SUE to transmit the CBG, and the like. For details, refer to the description in S206, which will not be repeated here.

Optionally, the first Uugrant and the SL grant may be one signaling or two signaling.

S307, the network device sends the second Uugrant to the first CUE, and sends the third Uugrant to the second CUE.

Wherein, the second Uugrant is used to instruct the first CUE to transmit a part of the first TB, and the third Uugrant is used to instruct the second CUE to transmit a part of the first TB initially. The information included in the second Uugrant and the third Uugrant is similar. The second Uugrant is used as an example for description below. For the information included in the third Uugrant, reference may be made to the description of the second Uugrant, which will not be repeated here.

For the first CUE, the part of the first TB here refers to the Z CBGs indicated by the fifth RRC message. For example, the bitmap included in the fifth RRC message is 010, and the second Uugrant indicates that the first CUE initially transmits a part of the first TB, which means that the first CUE needs to initially transmit the second CBG in the first TB, The first CBG and the third CBG are not sent.

The second Uu grant includes the first Uu HPID and the NDI field, and the NDI field instructs the first CUE to perform Uu initial transmission. The second Uugrant may also include other information, for example, may also include indication information indicating the time-frequency resource and MCS used by the first CUE to transmit the CBG, and the like, which will not be repeated here.

S308, the SUE sends X CBGs to the network device.

S309: The first CUE sends Z CBGs to the network device.

S310: The second CUE sends Z CBGs to the network device.

Finally, the network device obtains the first TB according to the received X+2Z CBGs.

It should be noted that the flow in FIG. 3 is just an example. In practical applications, some steps are optional and do not necessarily need to be performed. For example, steps such as S306 and S308 can be selectively performed.

Through the above process, the SUE completely sends the first TB to at least one CUE at the SL. The SUE and at least one CUE can respectively determine which TB of the SUE is transmitted by the Uu transmission based on the CBG through the mapping relationship between the SL HPID and the Uu HPID, and divide the TB to obtain multiple CBGs. The network device statically indicates the CBG that each UE needs to transmit through RRC, and even in the initial transmission of Uu, uplink coordination of CBG granularity can be realized. In uplink cooperative transmission, SUE and at least one CUE transmit based on CBG granularity during initial transmission, which can overcome the problems of limited antenna and bandwidth of SUE, meet the transmission rate requirement of large uplink capacity, and reduce data delay.

Embodiment three:

The main difference from the first embodiment is that in the third embodiment, the network device jointly instructs the CUE and the CBG to be sent by the SUE through the RRC message and the Uugrant, and the network device semi-statically instructs the CUE and the SUE transmission through the RRC message and the Uugrant. A part of the CBG in the first TB can reduce resource overhead while maintaining flexibility, which will be described in detail below.

As shown in FIG. 4 , a schematic flowchart of a data transmission method provided by an embodiment of the present application is shown. In the flow of FIG. 4 , the SUE needs to send the first TB to the network device as an example for description, and the first TB carries the uplink data of the SUE.

S401: The network device sends a first RRC message to the SUE.

In Embodiment 3, the network device may also send a sixth RRC message to the SUE, where the sixth RRC message indicates the maximum value Y of the number of CBGs sent by the SUE, and the number of the Y CBGs in the M CBGs included in the first TB. Index or position, Y is an integer greater than 0 and less than or equal to M.

It should be noted that the sixth RRC message and the first RRC message may be the same message, or may be two different messages, which are not limited in the present application.

Optionally, the sixth RRC message may include first transmission indication information, and the first transmission indication information may indicate the maximum value Y of the number of CBGs sent by the SUE, and the number of the Y CBGs in the M CBGs included in the first TB. index or location. For example, the first transmission indication information is a bitmap, a bit in the bitmap corresponds to a CBG in the first TB, and when a bit in the bitmap takes the value of the first value, it indicates that the CBG corresponding to the bit may be will be sent; when the value of a bit in the bitmap is the second value, it indicates that the CBG corresponding to the bit will not be sent. The first value and the second value can be determined according to specific conditions. For example, the first TB includes 3 CBGs with a first value of 1 and a second value of 0. When the first transmission indication information is 011, it indicates that the SUE may be required to send at least one of the first CBG and the second CBG in the first TB, and the third CBG is not sent.

S402: The network device sends a second RRC message to the first CUE, and sends a third RRC message to the second CUE.

In Embodiment 3, the network device may also send a seventh RRC message to the first CUE, where the seventh RRC message indicates the maximum value H of the number of CBGs sent by the first CUE, and the M of the H CBGs included in the first TB An index or position in the CBG, where H is an integer greater than 0 and less than or equal to M. Similarly, the network device may also indicate to the second CUE the maximum value H of the number of CBGs to be sent, and the indices or positions of the H CBGs in the M CBGs included in the first TB, which will not be repeated here.

It should be noted that, the seventh RRC message and the second RRC message may be the same message, or may be two different messages, which are not limited in this application.

Optionally, the seventh RRC message may include second transmission indication information, and the second transmission indication information may indicate the maximum value H of the number of CBGs sent by the SUE, and the number of the H CBGs in the M CBGs included in the first TB. index or location. For example, the second transmission indication information is a bitmap, a bit in the bitmap corresponds to a CBG in the first TB, and when a bit in the bitmap takes the value of the first value, it indicates that the CBG corresponding to the bit may be will be sent; when the value of a bit in the bitmap is the second value, it indicates that the CBG corresponding to the bit will not be sent. The first value and the second value can be determined according to specific conditions. For example, the first TB includes 3 CBGs with a first value of 1 and a second value of 0. When the second transmission indication information is 101, it indicates that the first CUE may be required to send at least one of the first CBG and the third CBG in the first TB, and the second CBG is not sent.

It should be noted that the execution order of S401 and S402 is not limited, and may be executed sequentially or simultaneously.

S403: The SUE sends an SL BSR to the network device, where the SL BSR is used to request the network device to allocate SL resources.

S404: The network device sends the SL grant to the SUE, and the SL grant instructs the SUE to send the first TB to the CUE.

S405: The SUE sends the first TB to the CUE.

S406: The network device sends the first Uugrant to the SUE, and the first Uugrant instructs the SUE to initially transmit a part of the first TB.

The first Uugrant may include a CBGTI field, where the CBGTI field indicates the number X of CBGs transmitted by the SUE, and the indices or positions of the X CBGs in the Y CBGs, where X is an integer greater than 0 and less than Y.

Optionally, in a possible implementation manner, the CBGTI field may be indicated by means of a bitmap. A bit in the bitmap corresponds to one CBG in the Y CBGs. When the value of a bit in the bitmap is the first value, it indicates that the CBG corresponding to the bit will be sent; the value of a bit in the bitmap is When the value is the second value, it indicates that the CBG corresponding to this bit will not be sent.

For example, when the first transmission indication information in the sixth RRC message is 110, and the CBGTI field in the first Uugrant is 10, it indicates that the SUE is instructed to initially transmit the first CBG in the first TB (the first CBG in the Y CBGs). CBG); when the CBGTI field in the first Uugrant is 01, it indicates that the SUE is instructed to initially transmit the third CBG in the first TB (the second CBG in the Y CBGs).

In another possible implementation manner, the CBGTI field may include at least one bit. The value corresponding to the at least one bit indicates the index or position of the CBG to be sent among the Y CBGs.

For example, when the first transmission indication information in the sixth RRC message is 110, and the CBGTI field in the first Uugrant is 0, it indicates that the SUE is instructed to initially transmit the first CBG in the first TB (the first CBG in the Y CBGs). CBG); when the CBGTI field in the first Uugrant is 1, it indicates that the SUE is instructed to initially transmit the third CBG in the first TB (the second CBG in the Y CBGs).

For other contents included in the first Uugrant, reference may be made to the description in S206, which will not be repeated here.

S407, the network device sends the second Uugrant to the first CUE, and sends the third Uugrant to the second CUE.

Wherein, the second Uugrant is used to instruct the first CUE to transmit a part of the first TB, and the third Uugrant is used to instruct the second CUE to transmit a part of the first TB initially. The information included in the second Uugrant and the third Uugrant is similar. The following takes the second Uugrant as an example for description. For the information included in the third Uugrant, refer to the description of the second Uugrant, which will not be repeated here.

For the first CUE, the second Uugrant may include a CBGTI field, where the CBGTI field indicates the number Z of CBGs transmitted by the first CUE, and the indices or positions of the Z CBGs in the H CBGs, where Z is greater than 0 and less than Integer of H.

Optionally, in a possible implementation manner, the CBGTI field in the second Uugrant can be indicated by means of a bitmap, one bit in the bitmap corresponds to one CBG in the H CBGs, and one bit in the bitmap corresponds to one CBG in the H CBGs. When the value of the bit is the first value, it indicates that the CBG corresponding to the bit will be sent; when the value of a bit in the bitmap is the second value, it indicates that the CBG corresponding to the bit will not be sent.

For example, when the second transmission indication information in the seventh RRC message is 011, and the CBGTI field in the second Uugrant is 10, it indicates that the SUE is instructed to initially transmit the first CBG in the first TB (the first CBG in the Y CBGs). CBG); when the CBGTI field in the first Uugrant is 01, it indicates that the SUE is instructed to initially transmit the third CBG in the first TB (the second CBG in the Y CBGs).

It should be noted that, the CBGTI domain in the second Uugrant may also have other implementation manners, which will not be repeated here.

For other content included in the second Uugrant, reference may be made to the description in S207, and details are not repeated here.

S408, the SUE sends X CBGs to the network device.

S409: The first CUE sends Z CBGs to the network device.

S410: The second CUE sends Z CBGs to the network device.

It should be noted that the flow in FIG. 4 is just an example. In practical applications, some steps are optional and do not necessarily need to be executed. For example, steps such as S406 and S408 can be selectively executed.

Through the above process, the SUE completely sends the first TB to at least one CUE at the SL. The SUE and at least one CUE can respectively determine which TB of the SUE is transmitted by the Uu transmission based on the CBG through the mapping relationship between the SL HPID and the Uu HPID, and divide the TB to obtain multiple CBGs. Through RRC and Uu grant, the network device can semi-statically indicate the CBG that each UE needs to transmit. Even in the initial transmission of Uu, uplink coordination of CBG granularity can be realized. In uplink cooperative transmission, SUE and at least one CUE transmit based on CBG granularity during initial transmission, which can overcome the problems of limited antenna and bandwidth of SUE, meet the transmission rate requirement of large uplink capacity, and reduce data delay.

It should be noted that, in Embodiments 1 to 3, the network device may not instruct the SUE to initially transmit a part of the first TB, that is, the network device may not send the first Uugrant to the SUE, but only indicate the initial transmission to at least one CUE. part of the first terabyte. In this implementation manner, one CUE can transmit Z CBGs in the first TB to the network device, and at least one CUE can transmit L total CBGs to the network device, so that the network device can determine the first TB according to the L CBGs, where L is An integer greater than or equal to M. Of course, the number of CBGs sent by different CUEs to the network device may also be different, which is specifically determined according to the actual situation.

Embodiment 4:

Most of the processes of the fourth embodiment are the same as those of the first embodiment. In the first embodiment, the network device unicasts the Uugrant to the SUE and the CUE respectively. In the fourth embodiment, the network device can multicast the Uugrant to the SUE and the CUE, that is, Say, S206 and S207 can be replaced with the following optional steps:

Optional step: the network device multicasts the fourth Uugrant to the SUE, the first CUE, and the second CUE, and the fourth Uugrant indicates that the SUE, the first CUE, and the second CUE initially transmit a part of the first TB.

Wherein, the fourth Uu grant may be scrambled by using a group (group) wireless network temporary identity (radio network temporary identity, RNTI). The group RNTI is configured by the network device, and the specific configuration is not limited in this application. For example, the network device may configure the group RNTI to the SUE, the first CUE and the second CUE respectively through an RRC message.

The fourth Uugrant may include an NDI field and a CBGTI field, where the NDI field indicates that the SUE, the first CUE, and the second CUE perform initial transmission; the CBGTI field indicates the indices of the X CBGs that the SUE needs to transmit among the M CBGs included in the first TB. or position, indicating the index or position of the Z CBGs that the first CUE needs to transmit among the M CBGs included in the first TB, and the index or position indicating the Z CBGs that the second CUE needs to transmit among the M CBGs included in the first TB. index or location.

In the fourth embodiment, in a possible implementation manner, the CBGTI field may be indicated in the form of a bitmap, some bits included in the CBGTI field indicate X CBGs that the SUE needs to transmit, and some bits indicate the Z CBGs that the first CUE needs to transmit. CBGs, and some bits indicate the Z CBGs that the second CUE needs to transmit. In addition, a bit in the bitmap corresponds to a CBG in the first TB, and when a bit in the bitmap takes the first value, it indicates that the CBG corresponding to the bit will be sent; a bit in the bitmap When the value of is the second value, it indicates that the CBG corresponding to this bit will not be sent. The first value and the second value can be determined according to specific conditions. For example, the first TB includes 3 CBGs with a first value of 1 and a second value of 0. The CBGTI indication field in the fourth Uugrant is 100 010 001, wherein the first 3 bits of the CBGTI field are 100, instructing the SUE to send the first CBG in the first TB; the middle 3 bits of the CBGTI field are 010, indicating the first CUE Send the second CBG in the first TB; the last 3 bits of the CBGTI field are 001, instructing the second CUE to send the third CBG in the first TB. The correspondence between the bits in the UE and the CBGTI may be configured by the network device, or may be pre-agreed, which is not limited in this embodiment of the present application.

The fourth Uugrant may also include the first Uu HPID; the fourth Uugrant may also include information such as the indication information indicating the SUE, the first CUE, and the second CUE to send the CBG and MCS, which will not be repeated here. . It should be noted that the fourth Uu grant and the SL grant may be one signaling or two signaling.

Embodiment 5:

Most of the processes in Embodiment 5 and Embodiment 2 are the same, except that in Embodiment 5, the network device can multicast Uugrant to SUE and CUE, that is, S306 and S307 can be replaced with the following optional steps:

For the specific implementation of the fourth Uugrant, refer to the description in the fourth embodiment. The main difference is that in the fifth embodiment, the fourth Uugrant may not include the CBGTI domain, that is, the fourth Uugrant in the fifth embodiment does not require Indicate which CBGs in the first TB are initially transmitted by the SUE, the first CUE, and the second CUE.

Which CBGs in the first TB are initially transmitted by the SUE, the first CUE, and the second CUE may be indicated by the network device through an RRC message. For details, refer to the description in Embodiment 2, which will not be repeated here.

Embodiment 6:

Most of the processes in Embodiment 6 and Embodiment 3 are the same, except that in Embodiment 6, the network device can multicast Uugrant to SUE and CUE, that is, S406 and S407 can be replaced with the following optional steps:

For the specific implementation of the fourth Uugrant, refer to the description in Embodiment 4. The main difference is that in Embodiment 6, the CBGTI field in the fourth Uugrant indicates that the X CBGs that the SUE needs to transmit are in the Y CBGs. The index or position indicates the index or position of the Z CBGs that the first CUE needs to transmit among the H CBGs, and the index or position of the H CBGs that indicates the Z CBGs that the second CUE needs to transmit.

The indices or positions of the Y CBGs and the indices or positions of the H CBGs may be indicated by the network device through an RRC message. For details, refer to the description in Embodiment 3, which will not be repeated here.

For example, the first TB includes 3 CBGs, the network device may need to send at least one of the first CBG and the second CBG in the first TB to configure the SUE through the RRC message, and to configure the first CUE may need to send the first CBG. At least one of the first CBG and the third CBG in the TB, configuring the second CUE may require sending at least one of the second CBG and the third CBG in the first TB. According to the above configuration, Y=2, H=2.

When the value of the bit in the CBGTI field is 0, it indicates that the CBG corresponding to the bit will be sent; when the value of the bit in the CBGTI field is 1, it indicates that the CBG corresponding to the bit will not be sent. If the CBGTI field in the fourth Uugrant is 10 10 01, the first 2 bits of the CBGTI field are 100, instructing the SUE to send the first CBG in the Y CBGs, that is, the first CBG in the first TB; The middle 2 bits are 10, instructing the first CUE to send the first CBG of the H CBGs, that is, the second CBG in the first TB; the last 2 bits of the CBGTI field are 01, instructing the second CUE to send the H CBGs The second CBG in the first TB is the third CBG in the first TB. The correspondence between the bits in the UE and the CBGTI, and the correspondence between the bits in the CBG and the CBGTI may be configured by the network device, or may be pre-agreed, which is not limited in the embodiment of the present application.

Embodiment 7:

The present application also provides a method, which can be applied to Embodiments 1 to 6, so as to improve the efficiency of CBG-based cooperative transmission. Specifically, after the SUE sends the first TB to the first CUE and the second CUE, the data receiving state based on the CBG granularity may be fed back on the Uu, which will be described in detail below.

As shown in FIG. 5 , a schematic flowchart of a data transmission method provided by an embodiment of the present application is shown. In the flow of FIG. 5 , the SUE needs to send the first TB to the network device as an example for description, and the first TB carries the uplink data of the SUE.

S501: The SUE sends the first TB to the first CUE and the second CUE, respectively.

Specifically how the SUE sends the first TB, reference may be made to the descriptions in Embodiments 1 to 6, and details are not repeated here.

Optionally, S502: The first CUE sends a first feedback message to the SUE.

Optionally, S503: the second CUE sends the first feedback message to the SUE.

The first feedback message sent by the first CUE indicates that among the M CBGs included in the first TB, CBGs that are correctly received by the first CUE and/or CBGs that are not correctly received by the first CUE. The first feedback message sent by the second CUE indicates that among the M CBGs included in the first TB, CBGs that are correctly received by the second CUE and/or CBGs that are not correctly received by the second CUE.

This application can provide at least two ways of feedback.

Feedback mode 1 is based on CBG-based acknowledgement (acknowledge, ACK)/negative acknowledgement (negative acknowledgement, NACK) feedback. The CUE feeds back the correct/incorrect reception status of each CBG based on the CBG granularity, the correctly received CBG feeds back ACK, and the incorrectly (or incorrectly) received CBG feeds back NACK.

For example, the first TB includes 3 CBGs, namely CBG0, CBG1, and CBG2. Correct reception is represented by 0, and incorrect reception is represented by 1. If the first CUE correctly receives CBG0 and CBG1 but does not correctly receive CBG2, the information carried by the first CUE through the first feedback message may be 001. The corresponding relationship between the CBG and the bit may be configured by a network device, or may be pre-agreed, which is not limited in this embodiment of the present application.

Feedback mode 2, based on CBG-based NACK-Only feedback, the CUE based on CBG granularity feeds back the incorrectly (or incorrectly) received CBG, and does not feed back the correctly received CBG.

For example, the first TB includes 3 CBGs, namely CBG0, CBG1, and CBG2. The CUE will feed back the erroneous reception status of each CBG, and the erroneous reception is represented by 1. If the first CUE correctly receives CBG0, CBG1, and CBG2, it does not send the first feedback message to the SUE.

It should be noted that, if only one of the above feedback modes is supported, the feedback mode is predefined and determined by the protocol.

If multiple feedback modes including the above feedback modes are supported, the specific feedback mode used can be configured through signaling, for example, it can be configured through an RRC message, or a PC5 RRC message configuration.

Optionally, the feedback resource bearing the first feedback message may be indicated by the SL grant, and the feedback resource bearing the first feedback message may be the SL resource, that is, the SL grant includes the first CUE and the second CUE on the SL for feeding back the SL. Time-frequency resources for the receive state. The SUE indicates the feedback resource indicated by the SL grant to the first CUE and the second CUE, and the specific process will not be repeated.

S504: The SUE sends the second feedback message to the network device.

The second feedback message may indicate the data reception status of the CUE. Specifically, the second feedback message may indicate that among the M CBGs included in the first TB, the CBGs that are correctly received by the first CUE and/or are not CBGs correctly received by a CUE; and/or may indicate CBGs correctly received by the second CUE and/or CBGs not correctly received by the second CUE among the M CBGs included in the first TB.

Optionally, the feedback resource bearing the second feedback message may be indicated by the SL grant, and the feedback resource bearing the second feedback message may be a Uu resource, that is, the SL grant includes the time-frequency used by the SUE to feed back the second feedback message on the Uu. resource. The SUE indicates the feedback resource indicated by the SL grant to the SUE, and the specific process will not be repeated.

It should be noted that, after determining the data receiving state of each CUE, the SUE may indicate the data receiving state of the multiple CUEs to the network device through a second feedback message. Alternatively, the SUE may send multiple second feedback messages to the network device according to the granularity of the CUE, that is, each time the SUE receives a first feedback message, it sends a second feedback message to the network device, thereby indicating to the network device respectively. Data reception status for each CUE.

The network device may determine, according to the second feedback message, the reception status of each CUE receiving the first TB on the SL, and the granularity of the reception status is based on the CBG granularity. The network device can thus schedule the CUE to send the correctly received CBG to the network device, and no longer schedule the CUE to send the incorrectly received CBG to the network device, which can avoid the mismatch between the scheduling and the receiving state, thereby improving CBG-based collaboration. transmission efficiency. For example, the network device schedules the first CUE to send the CBG0, but if the first CUE does not receive the CBG0 correctly, the scheduling will fail, so that the network device cannot obtain the first TB.

Embodiment 8:

With reference to the foregoing Embodiments 1 to 7, as shown in FIG. 6 , a schematic flowchart of a data transmission method provided by an embodiment of the present application is shown. In FIG. 6, the interaction between the network device and the terminal device is used as an example for illustration. The operations performed by the network device can also be performed by a chip or module inside the network device, and the operation performed by the terminal device can also be performed by the internal chip or module of the terminal device. implement.

The method shown in FIG. 6 can specifically implement the methods shown in Embodiments 1 to 7. For example, the first terminal device in the process of FIG. 6 may perform the steps performed by the SUE in Embodiments 1 to 7, and the second terminal device in the process of FIG. 6 may perform the CUE (the first CUE or Steps performed by the second CUE), the network device in the flowchart of FIG. 6 may perform the steps performed by the network device in Embodiment 1 to Embodiment 7.

Before S601, the network device may further instruct the first terminal device to perform uplink transmission based on the granularity of CBG, and indicate the maximum number of CBGs included in one TB. Specifically, the network device may send the first RRC message to the first terminal device. For details, reference may be made to the description in steps such as S201, and details are not repeated here.

S601: The first terminal device generates a TB for carrying uplink data.

The TB includes M CBGs, where M is an integer greater than 1. The number M of CBGs included in the TB can be determined in various ways, for example, it can be determined according to the foregoing formula (1).

How the first terminal device specifically generates the TB is not limited in this embodiment of the present application, and details are not described herein again.

S602: The network device sends third scheduling information to the first terminal device.

The third scheduling information instructs the first terminal device to send a TB to the second terminal device; the TB includes M CBGs, where M is an integer greater than 1.

The third scheduling information may be equivalent to the SL grant in Embodiment 1 to Embodiment 7. That is to say, the third scheduling information may indicate the SL resource for sending the TB, and further include at least one of the first process identifier and the second process identifier.

The first process identifier is equivalent to the first Uu HPID in Embodiment 1 to Embodiment 7, and is the identifier of the Uu HARQ process that sends the TB or the CBG in the TB; the second process identifier is equivalent to Embodiment 1 to Embodiment 7 The first SL HPID in , is the identifier of the SL HARQ process that sends the TB. The first process identifier and the second process identifier have a mapping relationship, and the mapping relationship is equivalent to the mapping relationship between the SL HPID and the Uu HPID in Embodiments 1 to 7, and the network device can configure the first process identifier and the first process identifier to the first terminal device. The mapping relationship of the two process identifiers can be specifically referred to the configuration process of the mapping relationship between the SL HPID and the Uu HPID in the above-mentioned embodiment, which will not be repeated here.

S603: The first terminal device sends the TB to at least one second terminal device, and correspondingly, the at least one second terminal device receives the TB from the first terminal device.

For the specific content of this step, reference may be made to the description in steps such as S205, and details are not repeated here.

Optionally, S604: the network device sends the second scheduling information to the first terminal device, and the first terminal device receives the second scheduling information from the network device, and sends X CBGs to the network device according to the second scheduling information .

The second scheduling information indicates that the first terminal device initially transmits a part of the TB. The second scheduling information may be equivalent to the first Ugrant in Embodiments 1 to 7. The second scheduling information includes information such as a first process identifier.

The X CBGs are a part of the M CBGs, and X is an integer greater than 0 and less than M.

S605: The network device sends the first scheduling information to the at least one second terminal device. Correspondingly, the at least one second terminal device receives the first scheduling information from the network device, and one of the at least one second terminal device sends the first scheduling information to the at least one second terminal device. The network device sends Z CBGs.

Wherein, the first scheduling information indicates that the second terminal device initially transmits a part of the TB; the first scheduling information may be equivalent to the second Uugrant or the third Uugrant in Embodiments 1 to 7. The first scheduling information includes information such as a first process identifier.

The Z CBGs are a part of the M CBGs, and Z is an integer greater than 0 and less than M. At least one second terminal device may send a total of L CBGs to the network device, where the L CBGs are CBGs in the TB, and L is an integer greater than 0.

Regarding how the network device specifically instructs the first terminal device and the second terminal device to perform initial transmission in S604 and S605, there may be various implementation manners. Implementation Mode 1, corresponding to Embodiment 1 or 4, the first scheduling information includes first information, and the first information indicates the index or position of the Z CBGs sent by the second terminal device in the M CBGs, The first information is equivalent to the CBGTI field in the second Uugrant; the first scheduling information may also include third information, and the third information may be equivalent to the NDI field in the second Uugrant, instructing the second terminal device to perform initial transmission. The first scheduling information may further include indication information such as time-frequency resources and MCS used for instructing the second terminal device to transmit the CBG, and details are not described herein again.

The second scheduling information includes second information, where the second information indicates the indices or positions of the X CBGs sent by the first terminal device in the M CBGs, and the second information is equivalent to the CBGTI field in the first Uugrant. The second scheduling information may also include fourth information, and the fourth information may be equivalent to the NDI field in the first Uugrant, and instruct the first terminal device to perform initial transmission. The second scheduling information may further include indication information such as time-frequency resources and MCS used to instruct the first terminal device to transmit the CBG, which will not be repeated here.

Implementation Mode 2, corresponding to Embodiment 2 or 5, the first scheduling information does not include the first information, and the second scheduling information does not include the second information. In this implementation manner, the network device may send a second message to the first terminal device, where the second message indicates the indices or positions of the X CBGs in the M CBGs. The second message may be equivalent to the fourth RRC message in the second or fifth embodiment, and the specific content of the second message may refer to the description in the second or fifth embodiment, which will not be repeated here.

The network device may send a first message to the second terminal device, where the first message indicates an index or position of the Z CBGs in the M CBGs. The first message may be equivalent to the fifth RRC message in the second or fifth embodiment, and the specific content of the fifth message may refer to the description in the second or fifth embodiment, which will not be repeated here.

In this implementation manner, the first scheduling information may include third information, and include indication information that instructs the second terminal device to transmit the time-frequency resource and MCS used by the CBG, and the second scheduling information may include fourth information and include indication The first terminal device transmits the time-frequency resources used by the CBG and the indication information of the MCS, etc., which will not be repeated here.

Implementation mode 3, corresponding to Embodiment 3 or 6, in this implementation mode, the network device may send a second message to the first terminal device, where the second message indicates the index of Y CBGs in the M CBGs or Location. The second message may be equivalent to the sixth RRC message in the third or sixth embodiment. For specific content of the second message, reference may be made to the description in the third or sixth embodiment, which is not repeated here.

The network device may send a first message to the second terminal device, where the first message indicates the indices or positions of the H CBGs in the M CBGs. The first message may be equivalent to the seventh RRC message in the third or sixth embodiment, and the specific content of the seventh message may refer to the description in the third or sixth embodiment, which will not be repeated here.

The first scheduling information may be equivalent to the second Uugrant in the third or sixth embodiment; the first information included in the first scheduling information may be equivalent to the CBGTI field in the second Uugrant, used to indicate that the Z CBGs are in H index or position in the CBG. The second scheduling information may be equivalent to the first Uugrant in the third or sixth embodiment; the second information included in the second scheduling information may be equivalent to the CBGTI field in the first Uugrant, and is used to indicate that X CBGs are in Y index or position in the CBG.

The first scheduling information and the second scheduling information may also include other information. For details, reference may be made to the descriptions in the second Uugrant and the first Uugrant in the third or sixth embodiment, which will not be repeated here.

S606: The network device receives L CBGs, and determines the TB according to the L CBGs.

In an implementation manner, the network device does not send the second scheduling information to the first terminal device, and in this case, L may be an integer greater than or equal to M. The network device may determine the TB based on the L CBGs.

In another implementation manner, the network device sends the second scheduling information to the first terminal device, and at this time, L+X may be an integer greater than or equal to M. The network device may determine the TB based on the L CBGs and the X CBGs.

The second terminal device may also send the first feedback message to the first terminal device. For the specific content of the first feedback message, reference may be made to the description of the first feedback message in Embodiment 7, which will not be repeated here.

The first terminal device may also send a second feedback message to the network device. For the specific content of the second feedback message, reference may be made to the description of the second feedback message in Embodiment 7, and details are not repeated here.

In addition, the first scheduling information and the third scheduling information are carried in a multicast Uu interface grant, and the Uu interface grant is scrambled by a group RNTI configured by the network device. The multicast Uu interface authorization may be equivalent to the fourth Uugrant in Embodiments 4 to 6, and the specific content can refer to the previous description, which will not be repeated here.

The various embodiments described herein can be independent solutions, and can also be combined according to internal logic, and these solutions all fall within the protection scope of the present application.

In the above embodiments provided by the present application, the methods provided by the embodiments of the present application are respectively introduced from the perspective of interaction between various devices. In order to implement the functions in the methods provided by the above embodiments of the present application, the network device or the terminal device may include a hardware structure and/or a software module, and implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module . Whether one of the above functions is performed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

The division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation. In addition, each functional module in each embodiment of the present application may be integrated into one processor, or may exist physically alone, or two or more modules may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules.

Similar to the above concept, as shown in FIG. 7 , an embodiment of the present application further provides an apparatus 700 for implementing the functions of the network device or the terminal device in the above method. For example, the apparatus may be a software module or a system-on-chip. In this embodiment of the present application, the chip system may be composed of chips, or may include chips and other discrete devices. The apparatus 700 may include: a processing unit 701 and a communication unit 702 .

In this embodiment of the present application, the communication unit may also be referred to as a transceiver unit, and may include a sending unit and/or a receiving unit, which are respectively configured to perform the sending and receiving steps of the network device or the terminal device in the above method embodiments.

Hereinafter, the communication apparatus provided by the embodiments of the present application will be described in detail with reference to FIG. 7 to FIG. 8 . It should be understood that the description of the apparatus embodiment corresponds to the description of the method embodiment. Therefore, for the content not described in detail, reference may be made to the above method embodiment, which is not repeated here for brevity.

A communication unit may also be referred to as a transceiver, transceiver, transceiver, or the like. The processing unit may also be referred to as a processor, a processing single board, a processing module, a processing device, and the like. Optionally, the device for implementing the receiving function in the communication unit 702 may be regarded as a receiving unit, and the device for implementing the transmitting function in the communication unit 702 may be regarded as a transmitting unit, that is, the communication unit 702 includes a receiving unit and a transmitting unit. A communication unit may also sometimes be referred to as a transceiver, transceiver, or interface circuit, or the like. The receiving unit may also sometimes be referred to as a receiver, receiver, or receiving circuit, or the like. The transmitting unit may also sometimes be referred to as a transmitter, a transmitter, or a transmitting circuit, or the like.

When the communication apparatus 700 performs the function of the second terminal device or the CUE in any of the processes shown in FIGS. 2 to 6 in the above embodiment:

a processing unit, configured to receive a transport block TB from a first terminal device through a communication unit; the TB is used to carry uplink data of the first terminal device; receive first scheduling information from a network device, the first scheduling The information indicates that the second terminal device initially transmits a part of the TB;

the processing unit, configured to send the Z coding block groups CBG to the network device through the communication unit;

The TB includes M CBGs, the Z CBGs are a part of the M CBGs, Z is an integer greater than 0 and less than M, and M is an integer greater than 1.

When the communication apparatus 700 performs the function of the first terminal device or the SUE in any of the processes shown in FIGS. 2 to 6 in the above embodiment:

a processing unit, configured to generate a transport block TB for carrying uplink data; the TB includes M coding block groups CBG, where M is an integer greater than 1;

A communication unit, configured to receive second scheduling information from a network device, where the second scheduling information indicates that the first terminal device initially transmits a part of the TB; and sends X CBGs to the network device according to the second scheduling information ;

When the communication apparatus 700 performs the function of the network device in any of the processes shown in FIGS. 2 to 6 in the above embodiment:

a communication unit, configured to send third scheduling information to the first terminal device; the third scheduling information instructs the first terminal device to send a transport block TB to the second terminal device; the TB includes M coding block groups CBG, M is an integer greater than 1; the TB is used to carry the uplink data of the first terminal device; the first scheduling information is sent to at least one second terminal device; the first scheduling information indicates that the second terminal device initially transmit a part of the TB; receive L CBGs; the L CBGs are from the at least one second terminal device;

a processing unit, configured to determine the TB according to the L CBGs;

Wherein, the L CBGs are CBGs in the TB, and L is an integer greater than 0.

The above are just examples, and the processing unit 701 and the communication unit 702 may also perform other functions. For more detailed descriptions, reference may be made to the method embodiments shown in FIGS. 3 to 6 or related descriptions in other method embodiments, which will not be repeated here.

FIG. 8 shows an apparatus 800 provided by an embodiment of the present application, and the apparatus shown in FIG. 8 may be an implementation manner of a hardware circuit of the apparatus shown in FIG. 7 . The communication apparatus can be applied to the flow chart shown above to perform the functions of the terminal device or the network device in the above method embodiments. For convenience of explanation, FIG. 8 only shows the main components of the communication device.

As shown in FIG. 8 , the communication apparatus 800 includes a processor 810 and an interface circuit 820 . The processor 810 and the interface circuit 820 are coupled to each other. It can be understood that the interface circuit 820 can be a transceiver or an input-output interface. Optionally, the communication apparatus 800 may further include a memory 830 for storing instructions executed by the processor 810 or input data required by the processor 810 to execute the instructions or data generated after the processor 810 executes the instructions.

When the communication apparatus 800 is used to implement the methods shown in FIGS. 3 to 6 , the processor 810 is used to implement the functions of the above-mentioned processing unit 701 , and the interface circuit 820 is used to implement the functions of the above-mentioned communication unit 702 .

When the above communication device is a chip applied to a terminal device, the terminal device chip implements the functions of the terminal device in the above method embodiments. The terminal device chip receives information from other modules (such as a radio frequency module or an antenna) in the terminal device, and the information is sent by the network device to the terminal device; or, the terminal device chip sends information to other modules (such as a radio frequency module or an antenna) in the terminal device antenna) to send information, the information is sent by the terminal equipment to the network equipment.

When the above communication device is a chip applied to a network device, the network device chip implements the functions of the network device in the above method embodiments. The network device chip receives information from other modules (such as a radio frequency module or an antenna) in the network device, and the information is sent by the terminal device to the network device; or, the network device chip sends information to other modules in the network device (such as a radio frequency module or an antenna). antenna) to send information, the information is sent by the network equipment to the terminal equipment.

It can be understood that the processor in the embodiments of the present application may be a central processing unit (Central Processing Unit, CPU), and may also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application-specific integrated circuits (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

In the embodiment of the present application, the processor may be a random access memory (Random Access Memory, RAM), a flash memory, a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable memory In addition to programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), registers, hard disk, removable hard disk, CD-ROM or any other form of storage medium known in the art middle. An exemplary storage medium is coupled to the processor, such that the processor can read information from, and write information to, the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium may reside in an ASIC. Alternatively, the ASIC may reside in a network device or end device. Of course, the processor and the storage medium may also exist in the network device or the terminal device as discrete components.

As will be appreciated by those skilled in the art, the embodiments of the present application may be provided as a method, a system, or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the present application. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions The apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

A data transmission method, comprising:

receiving a transport block TB from a first terminal device; the TB is used to carry uplink data of the first terminal device;

receiving first scheduling information from a network device, where the first scheduling information instructs the second terminal device to initially transmit a part of the TB;

sending Z coded block groups CBG to the network device;

The TB includes M CBGs, the Z CBGs are a part of the M CBGs, Z is an integer greater than 0 and less than M, and M is an integer greater than 1.
The method according to claim 1, wherein the first scheduling information comprises first information, and the first information indicates an index of the Z CBGs in the M CBGs;

Alternatively, a first message from the network device is received, the first message indicating an index of the Z CBGs among the M CBGs.
The method according to any one of claims 1 to 2, wherein the first scheduling information includes a first process identifier, and the first process identifier is to send a hybrid automatic repeat request (HARQ) of a CBG in the TB The ID of the process.
The method according to any one of claims 1 to 3, wherein the first process identifier and the second process identifier satisfy a mapping relationship, and the second process identifier is the relationship between the first terminal device and the second terminal device. The identification of the HARQ process of the TB is sent.
A data transmission method, comprising:

generating a transport block TB for carrying uplink data; the TB includes M coding block groups CBG, where M is an integer greater than 1;

receiving second scheduling information from the network device, where the second scheduling information indicates that the first terminal device initially transmits a part of the TB;

sending X CBGs to the network device according to the second scheduling information;

The X CBGs are a part of the M CBGs, and X is an integer greater than 0 and less than M.
The method according to claim 5, wherein the second scheduling information comprises second information, and the second information indicates an index of the X CBGs in the M CBGs;

Alternatively, a second message is received from the network device, the second message indicating the indices of the X CBGs among the M CBGs.
The method according to any one of claims 5 to 6, wherein the second scheduling information includes a first process identifier, and the first process identifier is to send a hybrid automatic repeat request (HARQ) of a CBG in the TB The ID of the process.
The method according to any one of claims 5 to 7, wherein the identifiers of the HARQ processes of the X CBGs sent to the network device are the first process identifiers; the first process identifiers and the second process identifiers A mapping relationship is satisfied, the mapping relationship is configured by the network device, and the second process identifier is an identifier of the HARQ process of the TB sent to the second terminal device.
The method according to any one of claims 5 to 8, wherein the method further comprises:

Receive a first feedback message from the second terminal device, where the first feedback message indicates that among the M CBGs included in the TB, the CBGs that are correctly received by the second terminal device and/or are not The CBG correctly received by the second terminal device.
The method according to claim 9, wherein the method further comprises:

Send a second feedback message to the network device, where the second feedback message indicates that among the M CBGs included in the TB, the CBGs correctly received by the second terminal device and/or the CBGs not received by the second terminal device The CBG correctly received by the second terminal device.
A data transmission method, comprising:

Send third scheduling information to the first terminal device; the third scheduling information instructs the first terminal device to send a transport block TB to the second terminal device; the TB includes M coding block groups CBG, where M is greater than 1 Integer; the TB is used to carry the uplink data of the first terminal device;

sending first scheduling information to at least one second terminal device; the first scheduling information instructs the second terminal device to initially transmit a part of the TB;

receiving L CBGs; the L CBGs are from the at least one second terminal device;

determining the TB according to the L CBGs;

Wherein, the L CBGs are CBGs in the TB, and L is an integer greater than 0.
The method according to claim 11, wherein the method further comprises:

sending second scheduling information to the first terminal device; the second scheduling information instructs the first terminal device to initially transmit a part of the TB;

Receive X CBGs from the first terminal device; the X CBGs are a part of the M CBGs, and X is an integer greater than 0.
The method according to claim 12, wherein X+L is greater than or equal to M; and the determining the TB according to the L CBGs comprises:

The TB is determined from the L CBGs and the X CBGs.
The method according to claim 12, wherein the second scheduling information comprises second information, and the second information indicates an index of the X CBGs among the M CBGs.
The method according to any one of claims 11 to 14, wherein the number of CBGs received from a second terminal device is Z, and Z is an integer greater than 0 and less than L;

The first scheduling information includes first information indicating indexes of the Z CBGs among the M CBGs.
The method according to any one of claims 11 to 15, wherein before the sending the third scheduling information to the first terminal device, the method further comprises:

sending a second message to the first terminal device, the second message indicating the indices of the X CBGs in the M CBGs;

Send a first message to the second terminal device, the first message indicating the indices of the Z CBGs in the M CBGs.
The method according to any one of claims 11 to 16, wherein,

The third scheduling information includes a second process identifier, where the second process identifier is an identifier of a HARQ process for sending the HARQ process of the TB;

The first scheduling information includes a first process identifier, and the first process identifier is an identifier of the HARQ process that sends the CBG in the TB;

Wherein, the first process identifier and the second process identifier satisfy a mapping relationship, and the mapping relationship is configured by the network device.
A communication device, comprising:

a processing unit, configured to receive a transport block TB from a first terminal device through a communication unit; the TB is used to carry uplink data of the first terminal device; receive first scheduling information from a network device, the first scheduling The information indicates that the second terminal device initially transmits a part of the TB;

the processing unit, configured to send the Z coding block groups CBG to the network device through the communication unit;

The TB includes M CBGs, the Z CBGs are a part of the M CBGs, Z is an integer greater than 0 and less than M, and M is an integer greater than 1.
The apparatus according to claim 18, wherein the first scheduling information comprises first information, and the first information indicates an index of the Z CBGs in the M CBGs;

Alternatively, the communication unit receives a first message from the network device, the first message indicating an index of the Z CBGs among the M CBGs.
The apparatus according to any one of claims 18 to 19, wherein the first scheduling information includes a first process identifier, and the first process identifier is to send a hybrid automatic repeat request (HARQ) of a CBG in the TB The ID of the process.
The apparatus according to any one of claims 18 to 20, wherein the first process identifier and the second process identifier satisfy a mapping relationship, and the second process identifier is the relationship between the first terminal device and the second terminal device. The identification of the HARQ process of the TB is sent.
A communication device, comprising:

a processing unit, configured to generate a transport block TB for carrying uplink data; the TB includes M coding block groups CBG, where M is an integer greater than 1;

A communication unit, configured to receive second scheduling information from a network device, where the second scheduling information indicates that the first terminal device initially transmits a part of the TB; and sends X CBGs to the network device according to the second scheduling information ;

The X CBGs are a part of the M CBGs, and X is an integer greater than 0 and less than M.
The apparatus according to claim 22, wherein the second scheduling information comprises second information, the second information indicating an index of the X CBGs in the M CBGs;

Alternatively, a second message is received from the network device, the second message indicating the indices of the X CBGs among the M CBGs.
The apparatus according to any one of claims 22 to 23, wherein the second scheduling information includes a first process identifier, and the first process identifier is to send a hybrid automatic repeat request (HARQ) of a CBG in the TB The ID of the process.
The apparatus according to any one of claims 22 to 24, wherein the identifiers of the HARQ processes of the X CBGs sent to the network device are the first process identifiers; the first process identifiers and the second process identifiers A mapping relationship is satisfied, where the mapping relationship is configured by the network device, and the second process identifier is an identifier of the HARQ process of the TB sent to the second terminal device.
A communication device, comprising:

a communication unit, configured to send third scheduling information to the first terminal device; the third scheduling information instructs the first terminal device to send a transport block TB to the second terminal device; the TB includes M coding block groups CBG, M is an integer greater than 1; the TB is used to carry the uplink data of the first terminal equipment; the first scheduling information is sent to at least one second terminal equipment; the first scheduling information indicates that the second terminal equipment initially transmit a part of the TB; receive L CBGs; the L CBGs are from the at least one second terminal device;

a processing unit, configured to determine the TB according to the L CBGs;

Wherein, the L CBGs are CBGs in the TB, and L is an integer greater than 0.
The apparatus according to claim 26, wherein the communication unit is further configured to:

sending second scheduling information to the first terminal device; the second scheduling information instructs the first terminal device to initially transmit a part of the TB;

Receive X CBGs from the first terminal device; the X CBGs are a part of the M CBGs, and X is an integer greater than 0.
The device according to claim 27, wherein X+L is greater than or equal to M; the processing unit is specifically used for:

The TB is determined from the L CBGs and the X CBGs.
The apparatus according to claim 27, wherein the second scheduling information comprises second information, and the second information indicates an index of the X CBGs in the M CBGs.
The apparatus according to any one of claims 26 to 29, wherein the number of CBGs received from a second terminal device is Z, and Z is an integer greater than 0 and less than L;

The first scheduling information includes first information indicating indexes of the Z CBGs among the M CBGs.
The apparatus according to any one of claims 26 to 30, wherein before the sending the third scheduling information to the first terminal device, the communication unit is further configured to:

sending a second message to the first terminal device, the second message indicating the indices of the X CBGs in the M CBGs;

Send a first message to the second terminal device, the first message indicating the indices of the Z CBGs in the M CBGs.
The apparatus according to any one of claims 26 to 31, wherein the third scheduling information includes a second process identifier, and the second process identifier is a hybrid automatic repeat request (HARQ) process for sending the TB 's identification;

The first scheduling information includes a first process identifier, and the first process identifier is an identifier of the HARQ process that sends the CBG in the TB;

Wherein, the first process identifier and the second process identifier satisfy a mapping relationship, and the mapping relationship is configured by the network device.
A readable storage medium, characterized in that it comprises a computer program or instruction, when the computer program or instruction is executed, the computer is made to execute the method according to any one of claims 1 to 4, or as claimed in claim 1. The method of any one of claims 5 to 10, or the method of any one of claims 11 to 17.
A communication device, comprising a processor, a transceiver, and a memory;

the processor for executing the computer program or instructions stored in the memory, and when executing the computer program or instructions, causes the communication device to implement the method of any one of claims 1 to 4, or A method as claimed in any one of claims 5 to 10.
A communication device, comprising a processor, a transceiver, and a memory;

The processor is configured to execute the computer program or instruction stored in the memory, and when the computer program or instruction is executed, the communication device can implement the method of any one of claims 11 to 17 .
A computer program product, characterized in that it includes computer-readable instructions, which when a communication device reads and executes the computer-readable instructions, cause the communication device to perform the method according to any one of claims 1 to 4 , or the method of any one of claims 5 to 10 , or the method of any one of claims 11 to 17 .