WO2020220753A1

WO2020220753A1 - Physical uplink shared channel sending method and device

Info

Publication number: WO2020220753A1
Application number: PCT/CN2020/071580
Authority: WO
Inventors: 闫志宇
Original assignee: 中国信息通信研究院
Priority date: 2019-04-30
Filing date: 2020-01-11
Publication date: 2020-11-05
Also published as: CN111866920A; CN111866920B

Abstract

Disclosed are a physical uplink shared channel sending method and device. The method comprises the following steps: making N nominal PUSCHs for repeatedly transmitting a target transport block correspond to M actual PUSCHs, wherein M>N, and at least one of the nominal PUSCHs is divided into a plurality of actual PUSCHs; and allocating a redundancy version index to each actual PUSCH. The present application further includes a terminal device, a network device and a system for implementing the method. According to the solution of the present application, the problem in the prior art of being unable to determine the redundancy version index of an actual PUSCH can be solved.

Description

Method and equipment for sending physical uplink shared channel

This application claims the priority of a Chinese patent application filed with the State Intellectual Property Office of China, the application number is 201910364621.0, and the invention title is "a physical uplink shared channel transmission method and equipment" on April 30, 2019. The entire content is incorporated into this application by reference.

Technical field

This application relates to the field of mobile communication technology, and in particular to a method and device for sending a physical uplink shared channel.

Background technique

Rel.16's NR system will support URLLC (Ultra-reliable and Low Latency communication) services with a reliability requirement of 1×10 ^-6 and a minimum delay requirement of 0.5 ms. Using PUSCH repeated transmission, on the one hand, can improve the transmission reliability, on the other hand, it can meet the requirements of receiving devices to obtain the initial PUSCH demodulation result as soon as possible.

In order to meet the high reliability and low latency requirements of URLLC, an uplink scheduling authorization indicates multiple PUSCH repeated transmissions of the same TB. There can be two or more PUSCH repeated transmissions of the same TB in a time slot, or more Secondary PUSCH repetitions can cross slot boundaries between adjacent slots.

If the target transport block is to be transmitted by N PUSCHs (called "nominal PUSCH"), if a "nominal PUSCH" crosses the slot boundary, in actual transmission, the "nominal PUSCH" is divided into two based on the slot boundary. “Actual PUSCH”; or, a “Nominal PUSCH” is divided into two or more “Actual PUSCHs” by the symbol indicated as downlink, then this “Nominal PUSCH” corresponds to at least two “Actual PUSCHs”. There are technologies that cannot determine the redundancy version index used when the "actual PUSCH" is used to carry the target transport block. In this way, it is impossible to use this PUSCH repeated transmission mode to meet the requirements of URLLC service reliability and delay.

Summary of the invention

The present invention provides a physical uplink shared channel transmission method and device, which solves that 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. How to determine the actual PUSCH transmission The problem of the redundancy version used by the target transmission block.

In the first aspect, an embodiment of the present application proposes a physical uplink shared channel transmission method for terminal equipment, including the following steps:

N nominal PUSCHs used to repeatedly transmit the target transport block correspond to M actual PUSCHs, M>N, where at least one nominal PUSCH is divided into multiple actual PUSCHs, N≥1;

Determine each actual PUSCH allocation redundancy version index;

Send the M actual PUSCHs.

As an optimized embodiment of this application, the redundancy version index of each actual PUSCH is determined according to the indication information in the 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 sequence.

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

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

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

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, multiple actual PUSCHs corresponding to the same nominal PUSCH have the same redundancy version index.

As another optimized embodiment of the present application, the redundancy version index of the nominal PUSCH is used as the second indication information; the second indication information is used to indicate a preset redundancy version index sequence, each of which is redundant The version index is sequentially allocated to the actual PUSCH corresponding to the nominal PUSCH.

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

In the embodiment of the present application, the j-th nominal PUSCH is divided into multiple actual PUSCHs.

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

In the second aspect, an embodiment of the present application also proposes a physical uplink shared channel transmission method for network equipment, including the following steps:

Send indication information, the indication information is used to indicate the repeated transmission of N nominal PUSCHs of the target transport block, N≥1; wherein, at least one nominal PUSCH is divided into multiple actual PUSCHs, and M corresponding to the N nominal PUSCHs Actual PUSCH, M>N;

Determine the redundancy version index of each actual PUSCH;

The M actual PUSCHs are received.

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

As another optimized embodiment of the method, the indication information is also used to indicate a preset redundancy version index sequence; each redundancy version index in the sequence corresponds to the N nominal PUSCH.

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

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 optimized embodiment of the present application, the redundancy version index of the nominal PUSCH is used as the second indication information; the second indication information is used to indicate a preset redundancy version index sequence, each of which is redundant The remaining version indexes are allocated to the actual PUSCH corresponding to the nominal PUSCH in order.

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

In the third aspect, an embodiment of the present application also proposes a terminal device for use in the method described in any one of the embodiments of the first aspect of the present application. The terminal device is configured to determine the redundancy version index for each actual PUSCH allocation and send the M actual PUSCHs, where the N nominal PUSCHs used to repeatedly transmit the target transport block correspond to the M actual PUSCHs, M>N, Among them, at least one nominal PUSCH is divided into multiple actual PUSCHs, and N≥1.

In the fourth aspect, an embodiment of the present application also proposes a network device for use in the method described in any one of the embodiments of the second aspect of the present application. The network device is configured to send indication information, the indication information is used to indicate that N nominal PUSCHs of the target transport block are repeatedly transmitted, where N≥1; wherein at least one nominal PUSCH is divided into multiple actual PUSCHs, and the N M actual PUSCHs corresponding to each nominal PUSCH, M>N; the network device is also used to determine the redundancy version index of each actual PUSCH, and receive the M actual PUSCHs.

In a fifth aspect, an embodiment of the present application also proposes a mobile communication system, which includes the terminal device described in any embodiment of the present application and or the network device described in any embodiment of the present application.

The above-mentioned at least one technical solution adopted in the embodiment of this application can achieve the following beneficial effects: the solution of this application can solve the problem that the existing technology cannot determine the redundant version index of the actual PUSCH, and meet the reliability and delay of URLLC services. demand.

Description of the drawings

The drawings described here are used to provide a further understanding of the application and constitute a part of the application. The exemplary embodiments and descriptions of the application are used to explain the application and do not constitute an improper limitation of the application. In the attached picture:

Figure 1 is a schematic diagram of redundant version index and coded bit circular buffering;

Figure 2 is a schematic diagram of the correspondence between nominal PUSCH and 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 ways

In order to make the purpose, technical solutions, and advantages of the present application clearer, the technical solutions of the present application will be described clearly and completely in conjunction with specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

According to the redundancy version index of the target transmission block corresponding to the nominal PUSCH, the redundancy version index used for transmitting the target transmission block in the actual PUSCH is determined, wherein the redundancy version index of the actual PUSCH and the corresponding The redundancy version index of the nominal PUSCH is the same; or, the redundancy version index of the actual PUSCH is determined according to the order of the actual PUSCH in the actual PUSCH set, and the actual PUSCH set consists of M corresponding to the N nominal PUSCHs. Or, determine the redundancy version index of the actual PUSCH according to the preset redundancy version index.

The "PUSCH redundancy version index" in this application file refers to the redundancy version index corresponding to the target transport block carried by the PUSCH.

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

Figure 1 is a schematic diagram of redundant version index and coded bit circular buffering.

5G NR realizes HARQ and rate matching through cyclic storage: the encoded bits are stored in the cyclic buffer, and read sequentially from the cyclic storage according to the redundant version index number during each transmission to achieve rate matching. For each transmission, the read position for rate matching is determined by the redundancy version index (RV index). The coded bit interleaving method specified in the 5G NR standard realizes the system bit priority mode with RV index=0.

According to 3GPP TS 38.214.Vf.4.0, if the terminal equipment is configured with the parameter pusch-AggregationFactor=X, the transport block (TB, Transport Block) scheduled by the PDCCH scrambled with C-RNTI and MCS-C-RNTI is in X consecutive time slots are repeatedly sent. In the X consecutive time slots, the symbol positions occupied by each PUSCH are the same. The PDCCH also includes 2 bits of information for indicating a redundancy version index, and according to the 2 bits of redundancy version index indication information, the terminal device can determine a redundancy version index sequence. The redundancy version index used for the nth transmission in the TB repeatedly sent for the above X times is determined by the redundancy version index sequence, and the specific method is shown in the following table. If the redundant version index indication information is "0", it means the redundant version index sequence is {0,2,3,1}; if the redundant version index indication information is "2", it means the redundant version index sequence is {2 ,3,1,0}; if the redundant version index indication information is "3", it means the redundant version index sequence is {3,1,0,2}; if the redundant version index indication information is "1", it means The redundant version index sequence is {1,0,2,3}.

Table 1. Redundant index version indication information and redundant version index sequence

(For the nth transmission)

Figure 2 is a schematic diagram of the correspondence between nominal PUSCH and actual PUSCH.

The network device instructs N times of "nominal PUSCH" to repeatedly transmit one TB through scheduling, and the scheduling information also includes the symbol position and the number of symbols occupied by the "nominal PUSCH" in time. Optionally, the scheduling information includes the first symbol position and the number of symbols occupied in time among multiple "nominal PUSCH", and the symbol position and the number of symbols occupied by the first "nominal PUSCH" in time And "Nominal Repetition Times" can determine the symbol position and number of symbols occupied by multiple "Nominal PUSCH" each in time.

If a "nominal PUSCH" crosses the slot boundary, in actual transmission, the "nominal PUSCH" is divided into two "actual PUSCH" based on the slot boundary; and or, if a "nominal PUSCH" includes being indicated as For downlink symbols, the “nominal PUSCH” is divided into two “actual PUSCHs” based on the symbol indicated as downlink. In the same way, if a "nominal PUSCH" crosses multiple time slot boundaries, in actual transmission, the "nominal PUSCH" is divided into multiple "actual PUSCH" based on these time slot boundaries; and or if one time "Nominal PUSCH" includes multiple non-consecutive symbols or symbol segments indicated as downlink, then the "nominal PUSCH" is divided into multiple "actual PUSCHs" based on the multiple non-contiguous symbols or symbol segments indicated as downlink. ". As shown in Figure 2, the network device indicates that the "nominal number of repetitions" is 3 times, and the first "nominal PUSCH" is located in time from the 5th symbol to the 12th symbol in the time slot #n. Based on this, the terminal device can determine that the second "nominal PUSCH" is located in time from the 13th symbol in slot #n to the 6th symbol in slot #n+1, and the third "nominal PUSCH" is in time. It is located from the 7th symbol in slot #n+1 to the 14th symbol in slot #n+1. Since the second "nominal PUSCH" crosses the slot boundary between slot #n and slot #n+1 in time, the second "nominal PUSCH" is divided into two based on the slot boundary. The second "real PUSCH" is located from the 13th symbol in slot #n to the 14th symbol in slot #n, and the first symbol in slot #n+1 to the 6th symbol in slot #n+1 symbol. In this way, the terminal device transmits the same TB in the first "actual PUSCH", the second "actual PUSCH", the third "actual PUSCH", and the fourth "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 present application provides a physical uplink shared channel transmission method for terminal equipment, including the following steps 10-30:

Step 10. The N nominal PUSCHs used to repeatedly transmit the target transport block correspond to M actual PUSCHs, and M>N, where at least one nominal PUSCH is divided into multiple actual PUSCHs, N≥1;

In step 10, it is determined that the N nominal PUSCHs corresponding to the target transport block include at least one characteristic PUSCH, and the characteristic PUSCH is divided into at least two actual PUSCHs, and the at least two actual PUSCHs are used for Send the target transmission block separately, N≥1;

PUSCH is divided into two types: one is the downlink control information sent by the network device DCI scheduling the PUSCH sent by the terminal device, which is dynamic authorized scheduling. One is that the network device semi-statically configures the PUSCH sent by the terminal device, that is, the network device instructs the terminal device to send the PUSCH through an authorization-free scheduling method, which is Configured grant PUSCH. "ConfiguredGrantConfig" is used to configure uplink transmission without dynamic uplink scheduling authorization. When the configured configured grant PUSCH resource is type 1, the terminal device can transmit uplink data on these resources according to the configured RRC signaling. When the configured Granted PUSCH resource is type 2, after receiving the configured RRC signaling, the terminal device can transmit uplink on these resources if it receives the PDCCH with the CS-RNTI scrambled CRC check bit to activate these resources data.

In this embodiment, the terminal device determines the N nominal PUSCHs corresponding to the target transmission block, for example, by receiving a dynamic scheduling grant, which is used to schedule the terminal device to repeatedly send the target transmission block in the N nominal PUSCHs, or to activate Pre-configured type 2 PUSCH configuration resources. The first information may also be, for example, high-level signaling, which is used to configure type 1 PUSCH configuration resources.

The terminal device determines that the N nominal PUSCHs correspond to the target transmission block, and the size of the target transmission block is, for example, S ₁ bit. Among them, the N nominal PUSCHs may include one or more characteristic PUSCHs. The characteristic PUSCH refers to the fact that it may be divided into two or more actual PUSCHs due to crossing the slot boundary, due to collision with the indicated downlink symbol, or due to other reasons.

Step 20: Determine each actual PUSCH allocation redundancy version index;

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

The terminal device sends the target transport block on the M actual PUSCHs corresponding to the N nominal PUSCHs. The M actual PUSCHs include actual PUSCHs corresponding to each of 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,..., RV_L. Regarding how to determine RV_1, RV_2,..., RV_L, one of the following methods can be used:

Manner 1. In the further optimized embodiment proposed by this application, the redundancy version index of each actual PUSCH is determined according to the indication information in the 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 the first sequence of the redundancy version index, and the redundancy versions of the M actual PUSCHs respectively correspond to the first sequence of the redundancy version index in order.

Table 2. Redundant index version indication information and redundant version index sequence

(For actual PUSCH)

Determine the redundancy version index used to transmit the target transport block in the at least two actual PUSCHs according to the order of the at least two actual PUSCHs in the actual PUSCH set, where the actual PUSCH set corresponds to the N nominal PUSCHs Is composed of M actual PUSCHs.

There are L (L≥2) actual PUSCHs corresponding to the first characteristic PUSCH, and there may be one or more other characteristic PUSCHs in the N nominal PUSCHs. For example, there are J (J≥2) actual PUSCHs corresponding to the second characteristic PUSCH. . At the same time, some of the N nominal PUSCHs correspond to one actual PUSCH. Assuming that N nominal PUSCHs correspond to Y PUSCHs, Y≥N, the Y actual PUSCHs form an actual PUSCH set. The redundancy version index used when the respective Y actual PUSCHs are transmitted in the actual PUSCH set is determined according to the order of each of the Y actual PUSCHs in the actual PUSCH set. For example, using the method of Table 2, according to the dynamic scheduling grant used to schedule the repetitive transmission target transmission block in N nominal PUSCHs, it is used to indicate the reference redundancy version index, or it is used to configure the retransmission target transmission block in the N nominal PUSCH. The reference redundancy version index is determined according to the configuration information of, and the redundancy version index used when each of the Y actual PUSCHs transmits the target transmission block is determined according to the reference redundancy version index and the order of the Y actual PUSCHs in the actual PUSCH set.

For example, as shown in Figure 2, if the redundant version index indication information is "0", it means that the first sequence of the redundant version index is {0,2,3,1}, then the first, second, third, and fourth actual PUSCH The redundant versions are 0, 2, 3, and 1.

Using this method to determine RV_1, RV_2,..., RV_L can ensure that the Y actual PUSCHs corresponding to the N nominal PUSCHs use the cyclic redundancy version index in sequence according to the preset rules to ensure that the performance of the target transport block meets the reliability of the URLLC service And latency requirements.

Manner 2: This application also proposes another embodiment for further optimization. The redundancy version index of each actual PUSCH is determined according to the indication information in the scheduling signaling. The indication information is used to indicate a preset redundancy version. The remaining version index sequence; each redundant version index in the sequence is allocated to the nominal PUSCH in order.

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

Optionally, multiple actual PUSCHs corresponding to the same nominal PUSCH have the same redundancy version index.

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

According to the redundancy version index of the target transmission block corresponding to the characteristic PUSCH, a redundancy version index used for transmitting the target transmission block in the at least two actual PUSCHs is determined.

Table 3. Redundant index version indication information and redundant version index sequence

(For nominal PUSCH)

The N nominal PUSCHs have respective redundancy version indexes, and the characteristic PUSCH as one of the N nominal PUSCHs also has a redundancy version index corresponding to it. For example: the redundancy version index corresponding to each of the N nominal PUSCHs is determined by the information used to indicate the redundancy version index in the dynamic scheduling grant used to schedule the repeated transmission of the target transport block in the N nominal PUSCH, or is used for configuration The configuration information of the target transport block is repeatedly sent in N nominal PUSCHs. Taking the determination of the information indicating the redundancy version index in the dynamic scheduling grant as an example, the terminal device can determine the redundancy version index used by the nth (n≤N) nominal PUSCH among 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, according to the redundancy version index of the target transmission block corresponding to the characteristic PUSCH, the redundancy version index used for transmitting the target transmission block in the at least two actual PUSCHs is determined. 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 . Using this method to determine RV_1, RV_2,..., RV_L can ensure that the redundancy version index used by the transmission target transmission blocks on the L actual PUSCHs corresponding to the first characteristic PUSCH is the same as the redundancy version index of the first characteristic PUSCH , To ensure that the first feature PUSCH provides the performance corresponding to the redundancy version index of the first feature PUSCH indicated by the dynamic scheduling grant or scheduling configuration information, and to ensure that it and other nominal PUSCHs each provide the dynamic scheduling grant or the redundancy indicated by the scheduling configuration information The encoding information corresponding to the version index ensures that the performance of the target transmission block meets the requirements of URLLC service reliability and delay.

Manner Three. In a further optimized embodiment of the present application, on the basis of Manner Two, the redundancy version index of the nominal PUSCH is used as the second indication information; the second indication information is used to indicate a preset redundancy version index Sequence, in which each redundancy version index is sequentially assigned to the actual PUSCH corresponding to the nominal PUSCH.

In particular, the j-th redundancy version index in the N nominal PUSCHs is used as indication information to indicate a preset third sequence of redundancy version indexes, and each redundancy version index in the third sequence is The actual PUSCH corresponding to the jth nominal PUSCH is sequentially allocated. The j-th nominal PUSCH is divided into multiple actual PUSCHs.

(For nominal PUSCH)

For example, as shown in Figure 2, if the redundant version index indication information is "0", it means that the second sequence of the redundant version index is {0,2,3,1}, then the first, second, and third nominal PUSCH redundancy The versions are 0, 2, and 3. Among them, the second nominal PUSCH is divided into the second actual PUSCH and the third actual PUSCH. That is, the second actual PUSCH and the third actual PUSCH correspond to the second nominal PUSCH. According to the second nominal PUSCH redundancy version index 2. Referring to Table 3, it can be determined that the preset third sequence of the redundancy version index is {2, 3, 1, 0}, and then the redundancy versions of the second actual PUSCH and the third actual PUSCH are determined to be 2 and 3, respectively.

Using this method to determine RV_1, RV_2,..., RV_L can ensure that the redundancy version indexes used for the transmission target transmission blocks on the L actual PUSCHs corresponding to the first characteristic PUSCH are transmitted in the order of the preset redundancy version indexes. The first feature PUSCH and other nominal PUSCHs each provide dynamic scheduling authorization or encoding information corresponding to the redundancy version index indicated by the scheduling configuration information, ensuring that the performance of the target transport block meets the requirements of URLLC service reliability and delay.

Manner 4: In at least one embodiment of the present application, multiple actual PUSCHs corresponding to the same nominal PUSCH have the same redundancy version index. Further preferably, for multiple actual PUSCHs corresponding to the same nominal PUSCH, the redundancy version index=0.

According to the preset redundancy version index, the redundancy version index used for transmitting the target transmission block in the at least two actual PUSCHs is determined. 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 to transmit the target transport block on the L actual PUSCHs corresponding to the first characteristic PUSCH are RV_1, RV_2,..., 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 units included in each of the L actual PUSCHs is smaller than the number of resource units included in the first characteristic PUSCH. In this way, when the L actual PUSCHs send the target transport block, the actual coding rate and the coding rate corresponding to the first characteristic PUSCH are both high. If the preset redundancy version is used on the L actual PUSCHs. For example, using the redundancy version index 0, with the help of the preset redundancy version, more system information bit characteristics can be provided, and the performance of the respective transmission target transmission blocks on the L actual PUSCHs can be guaranteed to a certain extent, and the target transmission block can be guaranteed The performance meets the requirements of URLLC service reliability and delay.

Step 30: Send the M actual PUSCHs.

After determining the respective redundancy version indexes of the M actual PUSCHs, the coding information of the target transport 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-30, an embodiment of the present application also proposes a physical uplink shared channel sending method for network equipment, including the following steps 40-60:

Step 40: Send indication information, the indication information is used to indicate the repeated transmission of N nominal PUSCHs of the target transport block, N≥1; wherein at least one nominal PUSCH is divided into multiple actual PUSCHs, and the N nominal PUSCHs correspond to M actual PUSCH, M>N;

Step 50: Determine the redundancy version index of each actual PUSCH;

Step 60: Receive the M actual PUSCHs.

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

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

The embodiment of the present application also proposes a terminal device, the terminal device is used to determine the redundancy version index of each actual PUSCH allocation, and send the M actual PUSCHs, where N nominal values of the target transport block are repeatedly transmitted. The PUSCH corresponds to M actual PUSCHs, M>N, where at least one nominal PUSCH is divided into multiple actual PUSCHs, N≥1. The terminal device, when it is working, implements the method of steps 10 to 30 of this specification, which may include all or part of the technical features of steps 10 to 30, and constitute multiple embodiments, which will not be repeated here.

The embodiment of the application also proposes a network device, the network device is used to send indication information, the indication information is used to indicate the repeated transmission of N nominal PUSCHs of the target transport block, N≥1; wherein, at least one nominal PUSCH Is divided into multiple actual PUSCHs, the M actual PUSCHs corresponding to the N nominal PUSCHs, M>N; the network device is also used to determine the redundancy version index of each actual PUSCH, and receive the M actual PUSCHs PUSCH. The network device, when working, implements the method of steps 40 to 60 of this specification, may include all or part of the technical features of steps 40 to 60, and constitute multiple embodiments, which will not be repeated here.

An embodiment of the application also proposes a mobile communication system, which includes the terminal device described in any embodiment of the application and or the network device described in any embodiment of the application.

It should also be noted that the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, product or equipment including a series of elements not only includes those elements, but also includes Other elements that are not explicitly listed, or include elements inherent to this process, method, commodity, or equipment. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, commodity, or equipment that includes the element.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation. the way. Based on this understanding, the technical solution of the present invention essentially or the part that contributes to the prior art can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions to make a A terminal device (which may be a mobile phone, a personal computer, a server, or a network device, etc.) executes the method described in each embodiment of the present invention.

The above are only the preferred embodiments of the present invention. It should be pointed out that for those of ordinary skill in the art, without departing from the principle of the present invention, several improvements and modifications can be made, and these improvements and modifications are also The protection scope of the present invention should be considered.

Claims

A method for sending a physical uplink shared channel is characterized by comprising the following steps:

N nominal PUSCHs used to repeatedly transmit the target transport block correspond to M actual PUSCHs, M>N, where at least one nominal PUSCH is divided into multiple actual PUSCHs, N≥1;

Determine each actual PUSCH allocation redundancy version index;

Send the M actual PUSCHs.
The method of claim 1, wherein:

Determine the redundancy version index of each actual PUSCH according to the indication information in the scheduling signaling, where the indication information is used to indicate a preset redundancy version index sequence; each redundancy version in the sequence The index corresponds to the M actual PUSCHs in order.
The method of claim 2, wherein:

The indication information is used to indicate the first sequence of the redundancy version index, and the redundancy versions of the M actual PUSCHs respectively correspond to the first sequence of the redundancy version index in order.
The method of claim 1, wherein:

Determine the redundancy version index of each actual PUSCH according to the indication information in the scheduling signaling, where the indication information is used to indicate a preset redundancy version index sequence; each redundancy version in the sequence Indexes are assigned to the nominal PUSCH in order.
The method of claim 4, wherein:

The indication information in the scheduling signaling is used to indicate the second sequence of the redundancy version index, and the redundancy versions of the N nominal PUSCHs respectively correspond to the second sequence of the redundancy version index in order.
The method according to claim 4 or 5, wherein:

The redundancy version index of the actual PUSCH is the same as the redundancy version index of the corresponding nominal PUSCH.
The method of claim 1 or 4, wherein:

Multiple actual PUSCHs corresponding to the same nominal PUSCH have the same redundancy version index.
The method of claim 4, wherein:

The redundancy version index of the nominal PUSCH is used as the second indication information; the second indication information is used to indicate a preset redundancy version index sequence, and each redundancy version index is allocated to the nominal PUSCH in sequence The corresponding actual PUSCH.
The method of claim 8, wherein:

The second indication information is used to indicate a preset third sequence of redundancy version indexes, and each redundancy version index in the third sequence is sequentially allocated to the actual PUSCH corresponding to the jth nominal PUSCH.
The method of claim 9, wherein:

The jth nominal PUSCH is divided into multiple actual PUSCHs.
The method of claim 7, wherein:

For multiple actual PUSCHs corresponding to the same nominal PUSCH, the redundancy version index=0.
A method for sending a physical uplink shared channel is characterized by comprising the following steps:

Send indication information, the indication information is used to indicate the repeated transmission of N nominal PUSCHs of the target transport block, N≥1; wherein, at least one nominal PUSCH is divided into multiple actual PUSCHs, and M corresponding to the N nominal PUSCHs Actual PUSCH, M>N;

Determine the redundancy version index of each actual PUSCH;

The M actual PUSCHs are received.
The method of claim 12, wherein:

The indication information is also used to indicate a preset redundancy version index sequence, and each redundancy version index in the sequence corresponds to the M actual PUSCHs in sequence.
The method of claim 13, wherein:

The indication information is used to indicate the first sequence of the redundancy version index, and the redundancy versions of the M actual PUSCHs respectively correspond to the first sequence of the redundancy version index in order.
The method of claim 12, wherein:

The indication information is also used to indicate a preset redundancy version index sequence; each redundancy version index in the sequence corresponds to the N nominal PUSCHs in order.
The method of claim 15, wherein:

The indication information is used to indicate the second sequence of the redundancy version index, and the redundancy version sequences of the N nominal PUSCHs respectively correspond to the second sequence of the redundancy version index in order.
The method according to claim 15 or 16, wherein:

The redundancy version index of the actual PUSCH is the same as the redundancy version index of the corresponding nominal PUSCH.
The method according to claim 12 or 15, wherein:

Multiple actual PUSCHs corresponding to the same nominal PUSCH have the same redundancy version index.
The method of claim 15, wherein:

The redundancy version index of the nominal PUSCH is used as the second indication information; the second indication information is used to indicate a preset redundancy version index sequence, and each redundancy version index is allocated to the nominal PUSCH in sequence The corresponding actual PUSCH.
The method of claim 19, wherein:

The second indication information is used to indicate a preset third sequence of redundancy version indexes, and each redundancy version index in the third sequence is sequentially allocated to the actual PUSCH corresponding to the jth nominal PUSCH.
The method of claim 20, wherein:

The jth nominal PUSCH is divided into multiple actual PUSCHs.
The method of claim 18, wherein:

For multiple actual PUSCHs corresponding to the same nominal PUSCH, the redundancy version index=0.
A terminal device, wherein the terminal device is used to determine the redundancy version index of each actual PUSCH allocation and send the M actual PUSCHs, wherein the N nominal PUSCHs used to repeatedly transmit the target transmission block correspond to M actual PUSCHs, M>N, where at least one nominal PUSCH is divided into multiple actual PUSCHs, N≥1.
The terminal device according to claim 23, wherein:

Determine the redundancy version index of each actual PUSCH according to the indication information in the scheduling signaling, where the indication information is used to indicate a preset redundancy version index sequence; each redundancy version in the sequence The index corresponds to the M actual PUSCHs in order.
The terminal device of claim 24, wherein:

The indication information is used to indicate the first sequence of the redundancy version index, and the redundancy versions of the M actual PUSCHs respectively correspond to the first sequence of the redundancy version index in order.
The terminal device according to claim 23, wherein:

Determine the redundancy version index of each actual PUSCH according to the indication information in the scheduling signaling, where the indication information is used to indicate a preset redundancy version index sequence; each redundancy version in the sequence Indexes are assigned to the nominal PUSCH in order.
The terminal device of claim 26, wherein:

The indication information in the scheduling signaling is used to indicate the second sequence of the redundancy version index, and the redundancy versions of the N nominal PUSCHs respectively correspond to the second sequence of the redundancy version index in order.
The terminal device according to claim 26 or 27, wherein:

The redundancy version index of the actual PUSCH is the same as the redundancy version index of the corresponding nominal PUSCH.
The terminal device according to claim 23 or 26, wherein:

Multiple actual PUSCHs corresponding to the same nominal PUSCH have the same redundancy version index.
The terminal device of claim 26, wherein:

The redundancy version index of the nominal PUSCH is used as the second indication information; the second indication information is used to indicate a preset redundancy version index sequence, and each redundancy version index is allocated to the nominal PUSCH in sequence The corresponding actual PUSCH.
The terminal device according to claim 30, wherein:

The second indication information is used to indicate a preset third sequence of redundancy version indexes, and each redundancy version index in the third sequence is sequentially allocated to the actual PUSCH corresponding to the jth nominal PUSCH.
The terminal device of claim 31, wherein:

The jth nominal PUSCH is divided into multiple actual PUSCHs.
The terminal device according to claim 29, wherein:

For multiple actual PUSCHs corresponding to the same nominal PUSCH, the redundancy version index=0.
A network device, characterized in that:

The network device is configured to send indication information, the indication information is used to indicate that N nominal PUSCHs of the target transport block are repeatedly transmitted, where N≥1; wherein at least one nominal PUSCH is divided into multiple actual PUSCHs, and the N M actual PUSCHs corresponding to each nominal PUSCH, M>N;

The network device is also used to determine the redundancy version index of each actual PUSCH, and receive the M actual PUSCHs.
The network device of claim 34, wherein:

The indication information is also used to indicate a preset redundancy version index sequence, and each redundancy version index in the sequence corresponds to the M actual PUSCHs in sequence.
The network device of claim 35, wherein:

The indication information is used to indicate the first sequence of the redundancy version index, and the redundancy versions of the M actual PUSCHs respectively correspond to the first sequence of the redundancy version index in order.
The network device of claim 34, wherein:

The indication information is also used to indicate a preset redundancy version index sequence; each redundancy version index in the sequence corresponds to the N nominal PUSCHs in order.
The network device of claim 37, wherein:

The indication information is used to indicate the second sequence of the redundancy version index, and the redundancy version sequences of the N nominal PUSCHs respectively correspond to the second sequence of the redundancy version index in order.
The network device according to claim 37 or 38, wherein:

The redundancy version index of the actual PUSCH is the same as the redundancy version index of the corresponding nominal PUSCH.
The network device according to claim 34 or 37, wherein:

Multiple actual PUSCHs corresponding to the same nominal PUSCH have the same redundancy version index.
The network device of claim 37, wherein:

The redundancy version index of the nominal PUSCH is used as the second indication information; the second indication information is used to indicate a preset redundancy version index sequence, and each redundancy version index is allocated to the nominal PUSCH in sequence The corresponding actual PUSCH.
The network device according to claim 41, wherein:

The second indication information is used to indicate a preset third sequence of redundancy version indexes, and each redundancy version index in the third sequence is sequentially allocated to the actual PUSCH corresponding to the jth nominal PUSCH.
The network device of claim 42, wherein:

The jth nominal PUSCH is divided into multiple actual PUSCHs.
The network device of claim 40, wherein:

For multiple actual PUSCHs corresponding to the same nominal PUSCH, the redundancy version index=0.
A mobile communication system characterized by comprising the terminal device according to any one of claims 23 to 33 and or the network device according to any one of claims 34 to 44.