CN111866920B

CN111866920B - Physical uplink shared channel sending method and equipment

Info

Publication number: CN111866920B
Application number: CN201910364621.0A
Authority: CN
Inventors: 闫志宇
Original assignee: China Academy of Information and Communications Technology CAICT
Current assignee: China Academy of Information and Communications Technology CAICT
Priority date: 2019-04-30
Filing date: 2019-04-30
Publication date: 2022-03-29
Anticipated expiration: 2039-04-30
Also published as: CN111866920A; WO2020220753A1

Abstract

The application discloses a method and equipment for sending a physical uplink shared channel, wherein the method comprises the following steps: n nominal PUSCHs for repeatedly transmitting a target transport block correspond to M actual PUSCHs, M > N, wherein at least one nominal PUSCH is divided into a plurality of actual PUSCHs; a redundancy version index is allocated for each actual PUSCH. The application also comprises terminal equipment, network equipment and a system for realizing the method. The scheme of the application can solve the problem that the prior art can not determine the redundancy version index of the actual PUSCH.

Description

Physical uplink shared channel sending method and equipment

Technical Field

The present application relates to the field of mobile communications technologies, and in particular, to a method and a device for sending a physical uplink shared channel.

Background

The NR system of rel.16 will support URLLC (Ultra-relay and Low Latency communication) traffic with reliability requirements of 1 x 10-6 and delay requirements below 0.5ms at the minimum. By using repeated transmission of the PUSCH, on one hand, the transmission reliability can be improved, and on the other hand, the requirement that the receiving equipment acquires the PUSCH initial demodulation result as early as possible can be met.

In order to meet the requirements of high reliability and low time delay of the URLLC, one uplink scheduling grant indicates that the same TB is repeatedly transmitted by multiple PUSCH, two or more PUSCH repetitions may be transmitted within one slot for the same TB, or multiple PUSCH repetitions may cross a slot boundary between adjacent slots.

If a target transport block is to be transmitted by N PUSCHs (referred to as "nominal PUSCHs"), if one "nominal PUSCH" crosses a slot boundary, then the "nominal PUSCH" is divided into two "actual PUSCHs" bounded by the slot boundary when actually transmitted; or, one "nominal PUSCH" is divided into two or more "actual PUSCHs" with the symbol indicated as downlink as boundary, and this "nominal PUSCH" corresponds to at least two "actual PUSCHs", and the prior art cannot determine what redundancy version index is respectively used when the "actual PUSCH" is used for carrying the target transport block. Thus, the repeated transmission mode of the PUSCH cannot be used to meet the requirements of reliability and time delay of the URLLC service.

Disclosure of Invention

The invention provides a method and equipment for sending a physical uplink shared channel (PUCCH), which solve the problem of how to determine a redundancy version used for transmitting a target transmission block in an actual Physical Uplink Shared Channel (PUSCH) because the target transmission block corresponds to N nominal PUSCHs, and at least one of the N nominal PUSCHs is divided into at least two actual PUSCHs.

In a first aspect, an embodiment of the present application provides a method for sending a physical uplink shared channel, where the method is used for a terminal device, and includes the following steps:

n nominal PUSCHs for repeatedly transmitting a target transport block correspond to M actual PUSCHs, M > N, wherein at least one nominal PUSCH is divided into a plurality of actual PUSCHs, and N is greater than or equal to 1;

determining each actual PUSCH allocation redundancy version index;

and transmitting the M actual PUSCHs.

As an embodiment of the present disclosure, a redundancy version index of each actual PUSCH is determined according to indication information in a scheduling signaling, where the indication information is used to indicate a preset redundancy version index sequence; each redundancy version index in the sequence corresponds to the M actual PUSCHs in order.

Further preferably, the indication information is used to indicate a first sequence of redundancy version indices, and the redundancy versions of the M actual PUSCHs respectively correspond to the first sequence of redundancy version indices in sequence.

As another embodiment of the present disclosure, a redundancy version index of each actual PUSCH is determined according to indication information in a scheduling signaling, where the indication information is used to indicate a preset redundancy version index sequence; each redundancy version index in the sequence is sequentially allocated to the nominal PUSCH.

Further preferably, the indication information in the scheduling signaling is used to indicate a second sequence of redundancy version indices, and the redundancy versions of the N nominal PUSCHs respectively correspond to the second sequence of redundancy version indices in sequence.

In at least one embodiment of the present application, the redundancy version index of the actual PUSCH is the same as the redundancy version index of the corresponding nominal PUSCH.

In at least one embodiment of the present application, the redundancy version indices are the same for multiple actual PUSCHs corresponding to the same nominal PUSCH.

As another embodiment of the optimization of the present application, a redundancy version index of a nominal PUSCH is used as the second indication information; and the second indication information is used for indicating a preset redundancy version index sequence, wherein each redundancy version index is sequentially allocated to the actual PUSCH corresponding to the nominal PUSCH.

Further preferably, the second indication information is configured to indicate a preset third sequence of redundancy version indexes, and each redundancy version index in the third sequence is sequentially allocated to an actual PUSCH corresponding to the jth nominal PUSCH.

In an embodiment of the present application, the jth nominal PUSCH is divided into a plurality of actual PUSCHs.

In at least one embodiment of the present application, the redundancy version index is 0 for multiple actual PUSCHs corresponding to the same nominal PUSCH.

In a second aspect, an embodiment of the present application further provides a method for sending a physical uplink shared channel, where the method is used for a network device, and includes the following steps:

sending indication information, wherein the indication information is used for indicating N nominal PUSCHs of a repeated transmission target transmission block, and N is more than or equal to 1; wherein at least one nominal PUSCH is divided into a plurality of actual PUSCHs, M actual PUSCHs corresponding to the N nominal PUSCHs, M > N;

determining a redundancy version index of each actual PUSCH;

receiving the M actual PUSCHs.

As a further optimized embodiment of the method, the indication information is further used to indicate a preset redundancy version index sequence, and each redundancy version index in the sequence sequentially corresponds to the M actual PUSCHs.

As another embodiment of further optimization of the method, the indication information is further used for indicating a preset redundancy version index sequence; each redundancy version index in the sequence corresponds to the N nominal PUSCHs in order.

Preferably, the indication information is used to indicate a second sequence of redundancy version indexes, and the redundancy version sequences of the N nominal PUSCHs respectively correspond to the second sequence of redundancy version indexes in sequence.

Further preferably, the redundancy version index of the actual PUSCH is the same as the redundancy version index of the corresponding nominal PUSCH.

As another embodiment of further optimization of the present application, a redundancy version index of a nominal PUSCH is used as the second indication information; and the second indication information is used for indicating a preset redundancy version index sequence, wherein each redundancy version index is sequentially allocated to the actual PUSCH corresponding to the nominal PUSCH.

Preferably, the second indication information is configured to indicate a preset third sequence of redundancy version indexes, and each redundancy version index in the third sequence is sequentially allocated to an actual PUSCH corresponding to the jth nominal PUSCH.

In a third aspect, an embodiment of the present application further provides a terminal device, which is used in the method in any one of the embodiments of the first aspect of the present application. The terminal device is configured to determine that each actual PUSCH allocates a redundancy version index, and send the M actual PUSCHs, where N nominal PUSCHs for repeatedly transmitting a target transport block correspond to the M actual PUSCHs, where M > N, where at least one nominal PUSCH is divided into multiple actual PUSCHs, and N is greater than or equal to 1.

In a fourth aspect, an embodiment of the present application further provides a network device, which is used in the method in any one of the embodiments of the second aspect of the present application. The network equipment is used for sending indication information, wherein the indication information is used for indicating N nominal PUSCHs for repeatedly transmitting a target transmission block, and N is more than or equal to 1; wherein at least one nominal PUSCH is divided into a plurality of actual PUSCHs, M actual PUSCHs corresponding to the N nominal PUSCHs, M > N; the network device is further configured to determine a redundancy version index of each actual PUSCH and receive the M actual PUSCHs.

In a fifth aspect, an embodiment of the present application further provides a mobile communication system, including the terminal device according to any embodiment of the present application and/or the network device according to any embodiment of the present application.

The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects: according to the scheme, the problem that the redundancy version index of the actual PUSCH cannot be determined in the prior art can be solved, and the requirements of URLLC service reliability and time delay are met.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

FIG. 1 is a schematic diagram of a redundancy version index and coded bit circular buffer;

fig. 2 is a schematic diagram of a correspondence between a nominal PUSCH and an actual PUSCH;

fig. 3 is a flowchart of a method for transmitting a physical uplink shared channel according to the present invention;

fig. 4 is a flowchart of another embodiment of a method for transmitting a physical uplink shared channel according to the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Determining a redundancy version index used for transmitting the target transmission block in the actual PUSCH according to the redundancy version index of the target transmission block corresponding to the nominal PUSCH, wherein the redundancy version index of the actual PUSCH is the same as the redundancy version index of the corresponding nominal PUSCH; or determining the redundancy version index of the actual PUSCH according to the sequence of the actual PUSCH in an actual PUSCH set, wherein the actual PUSCH set consists of M actual PUSCHs corresponding to the N nominal PUSCHs; or determining the redundancy version index of the actual PUSCH according to a preset redundancy version index.

The term "PUSCH redundancy version index" in this document refers to a redundancy version index corresponding to a target transport block carried by the PUSCH.

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

Fig. 1 is a schematic diagram of redundancy version index and coded bit circular buffer.

The 5G NR realizes HARQ and rate matching through cyclic storage: and storing the coded bits in a circular cache, and sequentially reading the coded bits from the circular cache according to the index number of the redundancy version during each transmission to realize rate matching. For each transmission, the read position for rate matching is determined by the redundancy version index (RV index). The interleaving scheme for coded bits specified in the 5G NR standard realizes a scheme in which systematic bits with RV index of 0 are prioritized.

According to 3GPP TS 38.214.vf.4.0, if the terminal device is configured with parameter pusch-aggregation factor ═ X, Transport Blocks (TBs) scheduled by PDCCH scrambled with C-RNTI, MCS-C-RNTI are repeatedly transmitted in X consecutive slots. In the X consecutive slots, the symbol positions occupied by the PUSCHs are the same. The PDCCH further includes 2 bits of information for indicating redundancy version indexes, and according to the 2 bits of redundancy version index indication information, the terminal device may determine a redundancy version index sequence. The redundancy version index used for the nth transmission in the above-mentioned X times of repeated transmissions is determined by the redundancy version index sequence, and the specific method is shown in the following table. If the redundancy version index indication information is '0', the redundancy version index sequence is represented as {0,2,3,1 }; if the redundancy version index indication information is "2", the redundancy version index sequence is represented as {2,3,1,0 }; if the redundancy version index indication information is '3', the redundancy version index sequence is represented as {3,1,0,2 }; if the redundancy version index indication information is "1", it represents that the redundancy version index sequence is {1,0,2,3 }.

TABLE 1 redundancy index version indication information and redundancy version index sequence

(for nth transmission)

Fig. 2 is a schematic diagram of a correspondence between a nominal PUSCH and an actual PUSCH.

The network device repeatedly transmits one TB by scheduling indication N times of 'nominal PUSCH', and the scheduling information also comprises the symbol position and the symbol number occupied by the 'nominal PUSCH' in time. Optionally, the scheduling information includes a symbol position and a symbol number occupied in time by a first of the plurality of nominal PUSCHs, and according to the symbol position and the symbol number occupied in time by the first nominal PUSCH and the nominal repetition number, the symbol position and the symbol number occupied in time by each of the plurality of nominal PUSCHs can be determined.

If the nominal PUSCH crosses the slot boundary once, the nominal PUSCH is divided into two actual PUSCHs by taking the slot boundary as the boundary during actual transmission; and or, if a "nominal PUSCH" includes a symbol indicated as downlink, the "nominal PUSCH" is divided into two "actual PUSCHs" bounded by the symbol indicated as downlink. In the same way, if a nominal PUSCH crosses multiple slot boundaries, the nominal PUSCH is divided into multiple actual PUSCHs with the slot boundaries as boundaries during actual transmission; and or, if a "nominal PUSCH" includes symbols or symbol segments indicated as being downlink by a plurality of non-consecutive, the "nominal PUSCH" is divided into a plurality of "actual PUSCHs" bounded by a plurality of non-consecutive symbols or symbol segments indicated as being downlink. As shown in the following figure, the network device indicates that the "nominal number of repetitions" is 3, the first "nominal PUSCH" being temporally located from the 5 th symbol to the 12 th symbol in slot # n. Based on this, the terminal device can determine that the second time "nominal PUSCH" is located from the 13 th symbol in slot # n to the 6 th symbol in slot # n +1 in time, and the third time "nominal PUSCH" is located from the 7 th symbol in slot # n +1 to the 14 th symbol in slot # n +1 in time. Since the second time "nominal PUSCH" crosses the slot boundary between slot # n and slot # n +1 in time, the second time "nominal PUSCH" is divided into two times "actual PUSCH" with the slot boundary as a boundary, and is respectively located from the 13 th symbol in slot # n to the 14 th symbol in slot # n, and from the 1 st symbol in slot # n +1 to the 6 th symbol in slot # n + 1. Thus, the terminal device transmits the same TB at the first time of "actual PUSCH", the second time of "actual PUSCH", the third time of "actual PUSCH", and the fourth time of "actual PUSCH", respectively.

Fig. 3 is a flowchart of a method for transmitting a physical uplink shared channel according to the present invention.

The embodiment of the application provides a method for sending a physical uplink shared channel, which is used for terminal equipment and comprises the following steps of 10-30:

step 10, N nominal PUSCHs for repeatedly transmitting a target transmission block correspond to M actual PUSCHs, wherein M > N, at least one nominal PUSCH is divided into a plurality of actual PUSCHs, and N is more than or equal to 1;

in step 10, determining N nominal PUSCHs corresponding to a target transport block, wherein the N nominal PUSCHs comprise at least one characteristic PUSCH, the characteristic PUSCHs are divided into at least two actual PUSCHs, the at least two actual PUSCHs are used for respectively transmitting the target transport block, and N is greater than or equal to 1;

PUSCH is divided into two types: one is that downlink control information DCI sent by a network device schedules a PUSCH sent by a terminal device, and is dynamic grant scheduling. The other is that the network device semi-statically configures the PUSCH transmitted by the terminal device, that is, the network device instructs the terminal device to transmit the PUSCH in an authorization-free scheduling manner, and the PUSCH is Configured grant PUSCH. The "ConfiguredGrantConfig" is used to configure uplink transmission free from dynamic uplink scheduling grant. When the Configured granted grant PUSCH resources are of type 1, the terminal device may transmit uplink data on these resources according to the Configured RRC signaling. When the Configured scheduled PUSCH resources are of type 2, the terminal device may transmit uplink data on these resources if the PDCCH receiving the CS-RNTI scrambled CRC check bits activates these resources after receiving the Configured RRC signaling.

The determination by the terminal device of the N nominal PUSCHs corresponding to the target transport block in this embodiment may be, for example, by receiving a dynamic scheduling grant, which is used to schedule the terminal device to repeatedly transmit the target transport block in the N nominal PUSCHs, or to activate a preconfigured PUSCH configuration resource of type 2. The first information may also be, for example, higher layer signaling, for configuring PUSCH configuration resources of type 1.

The terminal equipment determines that N nominal PUSCHs correspond to a target transmission block, the size of the target transmission block is S₁A bit. Wherein the N nominal PUSCHs may comprise one or more characteristic PUSCHs. The characteristic PUSCH refers to an actual PUSCH that may be split into two or more due to crossing slot boundaries, due to collision with an indicated downlink symbol, or for other reasons.

Step 20, determining each actual PUSCH allocation redundancy version index;

in step 20, redundancy version indexes used for transmitting the target transport block in the at least two actual PUSCHs corresponding to the characteristic PUSCH are determined, and the at least two actual PUSCHs are sent.

And the terminal equipment sends the target transmission block on M actual PUSCHs corresponding to the N nominal PUSCHs. The M actual PUSCHs include actual PUSCHs corresponding to the one or more characteristic PUSCHs described in step 10. Assuming that there are L (L ≧ 2) actual PUSCHs corresponding to the first characteristic PUSCH, the redundancy version indexes used by the terminal device to transmit the target transport block on the L actual PUSCHs are RV _1, RV _2, …, and RV _ L, respectively. With respect to how RV _1, RV _2, …, RV _ L are determined, one of the following ways may be used:

in a first mode, a further optimized embodiment provided by the present application determines a redundancy version index of each actual PUSCH according to indication information in a scheduling signaling, where the indication information is used to indicate a preset redundancy version index sequence; each redundancy version index in the sequence corresponds to the actual PUSCH in order.

In particular, the indication information is used to indicate a first sequence of redundancy version indices, and the redundancy versions of the M actual PUSCHs respectively correspond to the first sequence of redundancy version indices in sequence.

TABLE 2 redundancy index version indication information and redundancy version index sequence

(for actual PUSCH)

And determining redundancy version indexes used for transmitting the target transmission block in the at least two actual PUSCHs according to the sequence of the at least two actual PUSCHs in an actual PUSCH set, wherein the actual PUSCH set consists of M actual PUSCHs corresponding to the N nominal PUSCHs.

The actual PUSCHs corresponding to the first characteristic PUSCHs are L (L is more than or equal to 2), and the N nominal PUSCHs may also have other one or more characteristic PUSCHs, for example, the actual PUSCHs corresponding to the second characteristic PUSCHs are J (J is more than or equal to 2). Meanwhile, a nominal PUSCH in the N nominal PUSCHs corresponds to an actual PUSCH. And assuming that N nominal PUSCHs correspond to Y PUSCHs, Y is larger than or equal to N, and the Y actual PUSCHs form an actual PUSCH set. And determining the redundancy version indexes used when the Y actual PUSCHs are transmitted to the target transmission block according to the sequence of the Y actual PUSCHs in the actual PUSCH set. For example, in the manner of table 2, the reference redundancy version index is determined according to the configuration information for indicating the reference redundancy version index in the dynamic scheduling grant for scheduling the repeated transmission target transport block in the N nominal PUSCHs or for configuring the repeated transmission target transport block in the N nominal PUSCHs, and the redundancy version index used when the respective target transport block is transmitted by the Y actual PUSCHs is determined according to the reference redundancy version index and the respective order of the Y actual PUSCHs in the actual PUSCH set.

As shown in fig. 2, for example, if the redundancy version index indication information is "0", which represents that the first sequence of redundancy version indexes is {0,2,3,1}, the redundancy versions of the first, second, third, and fourth actual PUSCHs are 0,2,3, and 1, respectively.

By adopting the method to determine RV _1, RV _2, … and RV _ L, Y actual PUSCHs corresponding to N nominal PUSCHs can be ensured to use cyclic redundancy version indexes sequentially according to a preset rule, and the performance of a target transmission block is ensured to meet the requirements of URLLC service reliability and time delay.

The second mode, the present application also provides another embodiment of further optimization, determining a redundancy version index of each actual PUSCH according to indication information in a scheduling signaling, where the indication information is used to indicate a preset redundancy version index sequence; each redundancy version index in the sequence is sequentially allocated to the nominal PUSCH.

In particular, the indication information in the scheduling signaling is used for indicating the second sequence of redundancy version indexes, and the redundancy versions of the N nominal PUSCHs respectively correspond to the second sequence of redundancy version indexes in sequence.

Optionally, the redundancy version indexes are the same for a plurality of actual PUSCHs corresponding to the same nominal PUSCH.

Preferably, in the present embodiment, the redundancy version index of the actual PUSCH is the same as the redundancy version index of the corresponding nominal PUSCH.

And determining redundancy version indexes used for transmitting the target transmission block in the at least two actual PUSCHs according to the redundancy version indexes of the target transmission block corresponding to the characteristic PUSCHs.

TABLE 3 redundancy index version indication information and redundancy version index sequence

(for nominal PUSCH)

The N nominal PUSCHs have respective corresponding redundancy version indexes, the characteristic PUSCH is taken as one of the N nominal PUSCHs, and the characteristic PUSCH also has a corresponding redundancy version index. For example: the redundancy version index corresponding to each of the N nominal PUSCHs is determined by information used for indicating the redundancy version index in a dynamic scheduling authorization used for scheduling repeated transmission of the target transport block in the N nominal PUSCHs or configuration information used for configuring repeated transmission of the target transport block in the N nominal PUSCHs. Taking the determination of the information for indicating the redundancy version index in the dynamic scheduling grant as an example, the terminal device may determine the redundancy version index used by the nth (N ≦ N) nominal PUSCH in the N nominal PUSCHs according to the information. Preferably, the redundancy version index of the actual PUSCH is the same as the redundancy version index of the corresponding nominal PUSCH. That is, the redundancy version of the target transport block transmitted in the at least two actual PUSCHs is the same as the redundancy version index of the target transport block corresponding to the characteristic PUSCH.

In this embodiment, the redundancy version index used for transmitting the target transport block in the at least two actual PUSCHs is determined according to the redundancy version index of the target transport block corresponding to the characteristic PUSCH. For example, the redundancy version indexes RV _1, RV _2, …, RV _ L used for transmitting the target transport block on the L actual PUSCHs corresponding to the first characteristic PUSCH are all the same as the redundancy version corresponding to the first characteristic PUSCH. By adopting the method to determine RV _1, RV _2, … and RV _ L, the redundancy version indexes used by L actual PUSCHs corresponding to the first characteristic PUSCHs for transmitting the target transmission block are the same as the redundancy version index of the first characteristic PUSCH, the first characteristic PUSCH is ensured to provide the performance corresponding to the redundancy version index of the first characteristic PUSCH indicated by the dynamic scheduling authorization or the scheduling configuration information, the coding information corresponding to the redundancy version index indicated by the dynamic scheduling authorization or the scheduling configuration information is ensured to be provided by the first characteristic PUSCH and other nominal PUSCHs respectively, and the performance of the target transmission block is ensured to meet the requirements of URLLC service reliability and time delay.

In a third mode, in the further optimized embodiment of the present application, on the basis of the second mode, a redundancy version index of a nominal PUSCH is used as second indication information; and the second indication information is used for indicating a preset redundancy version index sequence, wherein each redundancy version index is sequentially allocated to the actual PUSCH corresponding to the nominal PUSCH.

In particular, the jth redundancy version index of the N nominal PUSCHs is used as indication information for indicating a preset redundancy version index third sequence, and each redundancy version index in the third sequence is sequentially allocated to an actual PUSCH corresponding to the jth nominal PUSCH. The jth nominal PUSCH is divided into a plurality of actual PUSCHs.

(for nominal PUSCH)

As shown in fig. 2, for example, if the redundancy version index indication information is "0", which represents that the second sequence of the redundancy version index is {0,2,3,1}, the redundancy versions of the first, second, and third nominal PUSCHs are 0,2, and 3, respectively. Wherein the second-time nominal PUSCH is divided into a second-time actual PUSCH and a third-time actual PUSCH. Namely, the second actual PUSCH corresponds to the third actual PUSCH and the second nominal PUSCH. According to the redundancy version index 2 of the second time nominal PUSCH. Referring to table 3, it may be determined that the preset redundancy version index has a third sequence of {2,3,1,0}, and it is determined that the redundancy versions of the second-time actual PUSCH and the third-time actual PUSCH are 2 and 3, respectively.

By adopting the method to determine RV _1, RV _2, … and RV _ L, the redundancy version indexes used by the transmission target transmission blocks on L actual PUSCHs corresponding to the first characteristic PUSCHs can be transmitted according to the preset redundancy version index sequence, the first characteristic PUSCHs and other nominal PUSCHs are ensured to respectively provide dynamic scheduling authorization or coding information corresponding to the redundancy version indexes indicated by the scheduling configuration information, and the performance of the target transmission blocks is ensured to meet the requirements of URLLC service reliability and time delay.

In at least one embodiment of the present application, the redundancy version indexes are the same for a plurality of actual PUSCHs corresponding to the same nominal PUSCH. Further preferably, the redundancy version index is 0 for a plurality of actual PUSCHs corresponding to the same nominal PUSCH.

And determining redundancy version indexes used for transmitting the target transmission block in the at least two actual PUSCHs according to preset redundancy version indexes. Optionally, the preset redundancy version index is RV ═ 0; or the preset redundancy version index is RV ═ 2.

If the preset redundancy version index is RV ═ X, the redundancy version indexes used for transmitting the target transport block on the L actual PUSCHs corresponding to the first characteristic PUSCH are RV _1, RV _2, … and RV _ L all use RV ═ X. Particularly optionally, the redundancy version index is RV ═ 0; or the preset redundancy version index is RV ═ 2. Since the first characteristic PUSCH is divided into L actual PUSCHs, the number of resource elements included in each of the L actual PUSCHs is smaller than the number of resource elements included in the first characteristic PUSCH. Thus, when the L actual PUSCH transmission target transport blocks are transmitted, the actual coding rate and the coding rate corresponding to the first characteristic PUSCH are both high. If a preset redundancy version is adopted on the L actual PUSCHs. For example, by using the redundancy version index 0, the preset redundancy version can provide the characteristics of more system information bits, and can ensure the performance of transmitting the target transport block on the L actual PUSCHs to a certain extent, and ensure that the performance of the target transport block meets the requirements of reliability and delay of the URLLC service.

And step 30, sending the M actual PUSCHs.

After respective redundancy version indexes of the M actual PUSCHs are determined, the coding information of the target transmission block can be determined according to the respective redundancy version indexes, and the M actual PUSCHs are sent.

Fig. 4 is a flowchart of another embodiment of a method for transmitting a physical uplink shared channel according to the present invention. Corresponding to the above steps 10 to 30, an embodiment of the present application further provides a physical uplink shared channel sending method, which is used for a network device, and includes the following steps 40 to 60:

step 40, sending indication information, wherein the indication information is used for indicating N nominal PUSCHs of the repeated transmission target transmission block, and N is more than or equal to 1; wherein at least one nominal PUSCH is divided into a plurality of actual PUSCHs, M actual PUSCHs corresponding to the N nominal PUSCHs, M > N;

step 50, determining the redundancy version index of each actual PUSCH;

and step 60, receiving the M actual PUSCHs.

Preferably, the indication information in the scheduling signaling is used to indicate a second sequence of redundancy version indexes, and the redundancy version sequences of the N nominal PUSCHs respectively correspond to the second sequence of redundancy version indexes in sequence.

In at least one embodiment of the present application, the redundancy version index is 0, or 2, corresponding to multiple actual PUSCHs of the same nominal PUSCH.

The embodiment of the application also provides a terminal device, which is configured to determine that each actual PUSCH allocates a redundancy version index and send the M actual PUSCHs, where N nominal PUSCHs for repeatedly transmitting a target transmission block correspond to the M actual PUSCHs, M > N, where at least one nominal PUSCH is divided into multiple actual PUSCHs, and N is greater than or equal to 1. When the terminal device works, the method for implementing steps 10 to 30 in this specification may include all or part of the technical features of steps 10 to 30, and thus a plurality of embodiments are formed, which are not described herein again.

The embodiment of the application also provides a network device, which is used for sending indication information, wherein the indication information is used for indicating N nominal PUSCHs for repeatedly transmitting the target transmission block, and N is more than or equal to 1; wherein at least one nominal PUSCH is divided into a plurality of actual PUSCHs, M actual PUSCHs corresponding to the N nominal PUSCHs, M > N; the network device is further configured to determine a redundancy version index of each actual PUSCH and receive the M actual PUSCHs. When the network device works, the method for implementing steps 40 to 60 in this specification may include all or part of the technical features of steps 40 to 60, and thus a plurality of embodiments are formed, and are not described herein again.

The embodiment of the present application further provides a mobile communication system, which includes the terminal device and/or the network device according to any embodiment of the present application.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A method for sending a physical uplink shared channel (PUCCH) is characterized by comprising the following steps:

determining the redundancy version index of each actual PUSCH according to the indication information in the scheduling signaling, wherein the method comprises at least 1 mode:

the indication information is used for indicating a redundancy version index first sequence, and the redundancy versions of the M actual PUSCHs respectively correspond to the redundancy version index first sequence according to the respective orders in the actual PUSCH set;

the indication information is used for indicating a redundancy version index second sequence, and the redundancy versions of the N nominal PUSCHs respectively correspond to the redundancy version index second sequence in sequence; the N nominal PUSCHs comprise at least one characteristic PUSCH, the characteristic PUSCH is divided into at least two actual PUSCHs, and redundancy version indexes used for transmitting the target transmission block in the at least two actual PUSCHs are determined according to redundancy version indexes corresponding to the characteristic PUSCHs;

and transmitting the M actual PUSCHs.

2. The method of claim 1,

the indication information is used for indicating a preset redundancy version index sequence; each redundancy version index in the sequence corresponds to the M actual PUSCHs in order.

3. The method of claim 1,

the indication information is used for indicating a preset redundancy version index sequence; each redundancy version index in the sequence is sequentially allocated to the nominal PUSCH.

4. The method of claim 1,

taking the redundant version index of the nominal PUSCH as second indication information; and the second indication information is used for indicating a preset redundancy version index sequence, wherein each redundancy version index is sequentially allocated to the actual PUSCH corresponding to the nominal PUSCH.

5. The method of claim 1,

and taking the jth redundancy version index in the N nominal PUSCHs as indication information for indicating a preset redundancy version index third sequence, wherein each redundancy version index in the third sequence is sequentially distributed to an actual PUSCH corresponding to the jth nominal PUSCH.

6. The method of claim 5,

the jth nominal PUSCH is divided into a plurality of actual PUSCHs.

7. The method of claim 1,

the redundancy version of the target transmission block transmitted in the at least two actual PUSCHs is the same as the redundancy version index of the target transmission block corresponding to the characteristic PUSCH, or,

the redundancy version index is 0 for multiple actual PUSCHs corresponding to the same nominal PUSCH.

8. A method for sending a physical uplink shared channel (PUCCH) is characterized by comprising the following steps:

determining the redundancy version index of each actual PUSCH, wherein the method comprises at least 1 mode as follows:

receiving the M actual PUSCHs.

9. The method of claim 8,

the indication information is further used for indicating a preset redundancy version index sequence, and each redundancy version index in the sequence sequentially corresponds to the M actual PUSCHs.

10. The method of claim 8,

the indication information is also used for indicating a preset redundancy version index sequence; each redundancy version index in the sequence corresponds to the N nominal PUSCHs in order.

11. The method of claim 8,

12. The method of claim 8,

and taking the jth redundancy version index in the N nominal PUSCHs as second indication information for indicating a preset redundancy version index third sequence, wherein each redundancy version index in the third sequence is sequentially distributed to an actual PUSCH corresponding to the jth nominal PUSCH.

13. The method of claim 12,

the jth nominal PUSCH is divided into a plurality of actual PUSCHs.

14. The method of claim 8,

15. A terminal device, for use in the method of any one of claims 1 to 7, wherein the terminal device is configured to determine each actual PUSCH to allocate redundancy version index, and transmit the M actual PUSCHs, wherein N nominal PUSCHs for repeatedly transmitting a target transport block correspond to M actual PUSCHs, M > N, and wherein at least one nominal PUSCH is divided into a plurality of actual PUSCHs, and N ≧ 1.

16. A network device for use in the method of any one of claims 8 to 14,

the network equipment is used for sending indication information, wherein the indication information is used for indicating N nominal PUSCHs for repeatedly transmitting a target transmission block, and N is more than or equal to 1; wherein at least one nominal PUSCH is divided into a plurality of actual PUSCHs, M actual PUSCHs corresponding to the N nominal PUSCHs, M > N;

the network device is further configured to determine a redundancy version index of each actual PUSCH and receive the M actual PUSCHs.

17. A mobile communication system comprising any terminal device of claim 15 and/or any network device of claim 16.