PUSCH transmission method, terminal, base station and storage medium

Abstract

Disclosed are a PUSCH transmission method, a terminal, a base station and a storage medium, the method comprising: a terminal receiving a first DCI and a second DCI; wherein the first DCI is used for scheduling transmission of a first PUSCH (Physical Uplink Shared Channel); the second DCI is used for scheduling transmission of a second PUSCH; the starting moment of the first PUSCH transmission is earlier than the starting moment of the second PUSCH transmission; the HARQ process ID indicated by the first DCI and the HARQ process ID indicated by the second DCI are the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one same first TB.

Description

Technical Field

[0001] The present application relates to the field of wireless technology, and in particular to a physical uplink shared channel (PUSCH) transmission method, terminal, base station and storage medium. Background Art

[0002] At present, PUSCH repeated transmission behavior uses the same set of scheduling parameters, such as the same resource allocation, modulation and coding strategy (MCS) indication, power control parameters, etc. In flexible time division duplex (TDD) networks and subband non-overlapping full duplex (SBFD) networks, there are significant differences in uplink interference between different symbols, which makes it difficult for the same set of scheduling parameters used for PUSCH repeated transmission in flexible TDD networks and SBFD networks to effectively adapt to the differentiated uplink interference between different symbols, thereby failing to effectively improve uplink coverage performance. Summary of the invention

[0003] To solve the related technical problems, the embodiments of the present application provide a PUSCH transmission method, a terminal, a base station and a storage medium.

[0004] The technical solution of the embodiment of the present application is implemented as follows:

[0005] The embodiment of the present application provides a PUSCH transmission method, which is applied to a terminal, including:

[0006] Receive first downlink control information (DCI) and second DCI; wherein,

[0007] The first DCI is used to schedule the transmission of a first PUSCH; the second DCI is used to schedule the transmission of a second PUSCH; the starting time of the first PUSCH transmission is earlier than the starting time of the second PUSCH transmission; the hybrid automatic repeat request (HARQ) process identifier (ID, Identify) indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first transport block (TB, Transport Block).

[0008] Among them, in the above scheme, the time domains of the first PUSCH and the second PUSCH do not overlap.

[0009] In the above solution, the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one same first TB, including:

[0010] The transmission of the first PUSCH and the transmission of the second PUSCH are associated with N identical first TBs; wherein N is greater than or equal to 1; or,

[0011] The transmission of the first PUSCH is associated with M1 TBs, the transmission of the second PUSCH is associated with M2 TBs, and there is at least one identical first TB between the M1 TBs associated with the transmission of the first PUSCH and the M2 TBs associated with the transmission of the second PUSCH; M1 and M2 are both greater than or equal to 1, and at least one of M1 and M2 is greater than or equal to 2.

[0012] In the above scheme, the reception of the second DCI is earlier than the end time of the first PUSCH transmission.

[0013] In the above solution, the first DCI and the second DCI are associated with the same control resource set (CORESET, Control-Resource Set); and / or,

[0014] The aggregation level control channel element (CCE) of the candidate physical downlink control channel (PDCCH) associated with the first DCI and the second DCI is the same; and / or,

[0015] The first DCI and the second DCI are scrambled by the same Radio Network Temporary Identifier (RNTI); and / or,

[0016] The first DCI and the second DCI are located in the same time slot, or the first DCI and the second DCI are located in the same time slot configuration period; or the candidate PDCCHs associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain; and / or,

[0017] The candidate PDCCHs associated with the first DCI and the second DCI are associated with the same search space set; and / or,

[0018] The monitoring timings of the search space set associated with the candidate PDCCH associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain.

[0019] In the above scheme, the HARQ process IDs indicated by the first DCI and the second DCI belong to the first HARQ process set.

[0020] In the above scheme, the transmission of the first PUSCH and / or the transmission of the second PUSCH includes L time slots, L transmission opportunities or L actual repetitions; and L is greater than or equal to 1.

[0021] In the above solution, the New Data Indicator (NDI) field associated with the first TB in the second DCI is not flipped or has the first value; or,

[0022] The terminal does not expect the NDI field associated with the first TB in the second DCI to flip, or the terminal does not expect the NDI field associated with the first TB in the second DCI to be other than the first value.

[0023] In the above scheme, according to the redundancy version (RV, RedundancyVersion) field associated with the first TB in the first DCI, the n1th transmission opportunity or the actual repeated RV applied to the first TB is determined; wherein the count of n1 only considers the transmission opportunity associated with the first PUSCH; and / or,

[0024] According to the RV field associated with the first TB in the second DCI, determine the n2th transmission machine or actual repeated RV applied to the first TB; wherein the n2 count only considers the transmission opportunities associated with the second PUSCH.

[0025] In the above scheme, the RV applied to the nth transmission opportunity or actual repetition of the first TB is determined according to the RV field associated with the first TB in the first DCI; wherein the count of n takes into account the transmission opportunities or actual repetitions associated with the first PUSCH and the second PUSCH.

[0026] In the above solution, the RV field associated with the first TB in the second DCI is a second value; or,

[0027] The terminal does not expect that the RV field associated with the first TB in the second DCI is not the second value.

[0028] In the above solution, a value of at least one of the following fields in the second DCI is the same as a value of a corresponding field in the first DCI or is a preset value:

[0029] Downlink allocation index;

[0030] Sounding Reference Signal (SRS) request;

[0031] SRS offset indication;

[0032] Channel State Information (CSI) request.

[0033] In the above solution, the transmission resources of the first PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the second PUSCH completely do not overlap with the first time-frequency resource set in the time domain; or,

[0034] The transmission resources of the second PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the first PUSCH completely do not overlap with the first time-frequency resource set in the time domain.

[0035] In the above solution, the first time-frequency resource set includes an uplink sub-band or an SBFD sub-band or a unified duplex (UDD, Unified Division Duplex) sub-band.

[0036] The embodiment of the present application further provides a PUSCH transmission method, which is applied to a base station, including:

[0037] Send a first DCI and a second DCI; wherein,

[0038] The first DCI is used to schedule the transmission of a first PUSCH; the second DCI is used to schedule the transmission of a second PUSCH; the starting time of the first PUSCH transmission is earlier than the starting time of the second PUSCH transmission; the HARQ process ID indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB.

[0039] Among them, in the above scheme, the time domains of the first PUSCH and the second PUSCH do not overlap.

[0040] In the above solution, the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one same first TB, including one of the following:

[0041] The transmission of the first PUSCH and the transmission of the second PUSCH are associated with N identical first TBs; wherein N is greater than or equal to 1; or,

[0042] The transmission of the first PUSCH is associated with M1 TBs, and the transmission of the second PUSCH is associated with M TBs, and there is at least one identical first TB among the M1 TBs associated with the transmission of the first PUSCH and the M2 TBs associated with the transmission of the second PUSCH; M1 and M2 are both greater than or equal to 1, and at least one of M1 and M2 is greater than or equal to 2.

[0043] In the above scheme, the reception of the second DCI is earlier than the end time of the first PUSCH transmission.

[0044] In the above solution, the first DCI and the second DCI are associated with the same CORESET; and / or,

[0045] The aggregation level CCE of the candidate PDCCH associated with the first DCI and the second DCI is the same; and / or,

[0046] The first DCI and the second DCI are scrambled by the same RNTI; and / or,

[0047] The first DCI and the second DCI are located in the same time slot, or the first DCI and the second DCI are located in the same time slot configuration period; or the candidate PDCCHs associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain; and / or,

[0048] The candidate PDCCHs associated with the first DCI and the second DCI are associated with the same search space set; and / or,

[0049] The monitoring timings of the search space set associated with the candidate PDCCH associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain.

[0050] In the above scheme, the HARQ process IDs indicated by the first DCI and the second DCI belong to the first HARQ process set.

[0051] In the above scheme, the transmission of the first PUSCH and / or the transmission of the second PUSCH includes L time slots, L transmission opportunities or L actual repetitions; and L is greater than or equal to 1.

[0052] In the above solution, the NDI field associated with the first TB in the second DCI is not flipped or takes the first value; or,

[0053] The terminal does not expect the NDI field associated with the first TB in the second DCI to flip, or the terminal does not expect the NDI field associated with the first TB in the second DCI to be other than the first value.

[0054] In the above scheme, according to the RV field associated with the first TB in the first DCI, the RV applied to the first TB for the n1th transmission opportunity or the actual repetition is determined; wherein the count of n1 only considers the transmission opportunity associated with the first PUSCH; and / or,

[0055] According to the RV field associated with the first TB in the second DCI, determine the n2th transmission machine or actual repeated RV applied to the first TB; wherein the n2 count only considers the transmission opportunities associated with the second PUSCH.

[0056] In the above scheme, the RV applied to the nth transmission opportunity or actual repetition of the first TB is determined according to the RV field associated with the first TB in the first DCI; wherein the count of n takes into account the transmission opportunities or actual repetitions associated with the first PUSCH and the second PUSCH.

[0057] In the above solution, the RV field associated with the first TB in the second DCI is a second value; or,

[0058] The terminal does not expect that the RV field associated with the first TB in the second DCI is not the second value.

[0059] In the above solution, a value of at least one of the following fields in the second DCI is the same as a value of a corresponding field in the first DCI or is a preset value:

[0060] Downlink allocation index;

[0061] SRS request;

[0062] SRS offset indication;

[0063] CSI request.

[0064] In the above solution, the transmission resources of the first PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the second PUSCH completely do not overlap with the first time-frequency resource set in the time domain; or,

[0065] The transmission resources of the second PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the first PUSCH completely do not overlap with the first time-frequency resource set in the time domain.

[0066] In the above scheme, the first time-frequency resource set includes an uplink subband or a subband BFD subband or a UDD subband.

[0067] The embodiment of the present application further provides a PUSCH transmission device, including:

[0068] A receiving unit, configured to receive a first DCI and a second DCI; wherein,

[0069] The first DCI is used to schedule the transmission of a first PUSCH; the second DCI is used to schedule the transmission of a second PUSCH; the starting time of the first PUSCH transmission is earlier than the starting time of the second PUSCH transmission; the HARQ process ID indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB.

[0070] The embodiment of the present application further provides a PUSCH transmission device, including:

[0071] A sending unit, configured to send a first DCI and a second DCI; wherein,

[0072] The first DCI is used to schedule the transmission of a first PUSCH; the second DCI is used to schedule the transmission of a second PUSCH; the starting time of the first PUSCH transmission is earlier than the starting time of the second PUSCH transmission; the HARQ process ID indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB.

[0073] The embodiment of the present application further provides a terminal, comprising: a first processor and a first communication interface; wherein,

[0074] The first communication interface is used to receive the first DCI and the second DCI; wherein,

[0075] The first DCI is used to schedule the transmission of a first PUSCH; the second DCI is used to schedule the transmission of a second PUSCH; the starting time of the first PUSCH transmission is earlier than the starting time of the second PUSCH transmission; the HARQ process ID indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB.

[0076] The embodiment of the present application further provides a base station, comprising: a second processor and a second communication interface; wherein,

[0077] The second communication interface is used to send the first DCI and the second DCI; wherein,

[0078] The first DCI is used to schedule the transmission of a first PUSCH; the second DCI is used to schedule the transmission of a second PUSCH; the starting time of the first PUSCH transmission is earlier than the starting time of the second PUSCH transmission; the HARQ process ID indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB.

[0079] The embodiment of the present application further provides a terminal, comprising: a first processor and a first memory for storing a computer program that can be run on the processor,

[0080] Wherein, the first processor is used to execute the steps of any of the above-mentioned terminal side methods when running the computer program.

[0081] The embodiment of the present application further provides a base station, comprising: a second processor and a second memory for storing a computer program that can be run on the processor,

[0082] Wherein, the second processor is used to execute the steps of any of the above-mentioned base station side methods when running the computer program.

[0083] An embodiment of the present application also provides a storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned terminal side methods are implemented, or the steps of any of the above-mentioned base station side methods are implemented.

[0084] The PUSCH transmission method, terminal, base station and storage medium provided in the embodiment of the present application are configured such that the terminal receives the first DCI and the second DCI sent by the base station, wherein the HARQ process ID indicated by the first DCI and the second DCI are the same, the start time of the first PUSCH transmission scheduled by the first DCI is earlier than the start time of the second PUSCH transmission scheduled by the second DCI, and the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB. In the above scheme, the transmission or repeated transmission of the PUSCH scheduled by two different DCIs are associated, and multiple DCIs schedule the PUSCH of the same TB, thereby improving the uplink coverage performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0085] Figure 1 A schematic diagram of a flexible TDD network communication scenario for related technologies;

[0086] Figure 2 It is a schematic diagram of the SBFD network communication scenario of the related technology;

[0087] Figure 3 This is a schematic diagram of a PUSCH transmission method flow in an embodiment of the present application;

[0088] Figure 4 This is an example diagram of a PUSCH transmission method according to an embodiment of the present application;

[0089] Figure 5 This is an example diagram of another PUSCH transmission method according to an embodiment of the present application;

[0090] Figure 6 This is an example diagram of the third PUSCH transmission method in an embodiment of the present application;

[0091] Figure 7 This is an example diagram of the fourth PUSCH transmission method according to an embodiment of the present application;

[0092] Figure 8 This is an example diagram of the fifth PUSCH transmission method according to an embodiment of the present application;

[0093] Fig. 9 This is a flow chart of another PUSCH transmission method according to an embodiment of the present application;

[0094] Fig.10 This is a schematic diagram of the structure of a PUSCH transmission device according to an embodiment of the present application;

[0095] Fig.11 This is a schematic diagram of another structure of a PUSCH transmission device according to an embodiment of the present application;

[0096] Fig.12 This is a schematic diagram of the terminal structure of an embodiment of the present application;

[0097] Fig.13 This is a schematic diagram of the base station structure of an embodiment of the present application. DETAILED DESCRIPTION

[0098] Figure 1 FIG. 4 shows a schematic diagram of a flexible TDD network communication scenario, in which, for a base station (gNB, gNode B) 1, in time slot #4, it is only subject to interference from the traditional “terminal-gNB” I UE-gNB In time slots #2 and #3, in addition to the interference I UE-gNB gNB1 will also be affected by the cross-link interference I between base stations. gNB-gNB impact. Figure 2 The schematic diagram of the SBFD network communication scenario is shown. In the SBFD frame structure, a symbol in a TDD carrier has both uplink and downlink transmissions. Figure 1 Compared with the TDD frame structure shown in Figure 1, SBFD introduces more uplink and downlink transmission opportunities. On the one hand, from the perspective of the base station, there is a significant difference in the uplink interference situation between the SBFD symbol (denoted as "X") and the full UL symbol (denoted as "U"). Figure 2In the example, gNB1 and gNB2 are both SBFD base stations with the same SBFD subband configuration. In time slot #4, all bandwidth is used for uplink transmission, which is a traditional UL only time slot. At this time, uplink transmission is only subject to interference from "terminal-gNB". UE-gNB In time slots #1, #2 and #3, the base station performs uplink transmission in the uplink subband and downlink transmission in the downlink subband at the same time. At this time, the uplink transmission is affected by the following interferences: UE-gNB , the self-interference (self-interference) caused by the downlink transmission of base station gNB1 to the uplink transmission of base station gNB1 itself SI , and the inter-base station interference I caused by the downlink transmission of other base stations to the uplink transmission of base station gNB1 gNB-gNB On the other hand, the QCL relationship between the SBFD symbol (denoted as “X”) and the full UL symbol (denoted as “U”) may also be significantly different.

[0099] At present, PUSCH repeated transmission behavior uses the same set of scheduling parameters, such as the same resource allocation, MCS indication, power control parameters, etc. Figure 1 and Figure 2 It can be seen that in flexible TDD networks, there are significant differences in uplink interference between different symbols. In SBFD networks, there are significant differences in uplink interference between SBFD symbols and full uplink (UL) symbols, quasi co-location (QCL) relationships, and UL bandwidth. In the above two network situations, the same set of scheduling parameters used for repeated PUSCH transmissions is difficult to effectively adapt to the differentiated uplink interference on different symbols, and thus cannot improve uplink coverage.

[0100] Based on this, in each embodiment of the present application, the terminal receives the first DCI and the second DCI sent by the base station, and the transmission or repeated transmission of the PUSCH scheduled by the two DCIs is associated, for example, if two PUSCHs are associated with the same TB, and the two DCIs are allowed to adopt differentiated scheduling parameters, such as different resource allocation, MCS indication, power control parameters, etc. Therefore, it is possible to accurately adapt to the differentiated uplink interference conditions on different symbols in the flexible TDD network and the SBFD network, thereby effectively improving the uplink coverage performance. Among them, the HARQ process IDs indicated by the first DCI and the second DCI are the same, the start time of the first PUSCH transmission scheduled by the first DCI is earlier than the start time of the second PUSCH transmission scheduled by the second DCI, and the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB.

[0101] The present application is further described in detail below in conjunction with the accompanying drawings and embodiments.

[0102] The embodiment of the present application provides a PUSCH transmission method, which is applied to a terminal, such as Figure 3 As shown, the method includes:

[0103] Step 301: Receive a first DCI and a second DCI.

[0104] Among them, the first DCI is used to schedule the transmission of the first PUSCH; the second DCI is used to schedule the transmission of the second PUSCH; the starting time of the first PUSCH transmission is earlier than the starting time of the second PUSCH transmission; the HARQ process ID indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB.

[0105] Here, the HARQ process ID is sometimes referred to as the HARQ process number or the HARQ process number (HARQ process number).

[0106] Here, the first DCI and the second DCI schedule different PUSCHs respectively, and the start time of the first PUSCH transmission scheduled by the first DCI is earlier than the start time of the second PUSCH transmission scheduled by the second DCI.

[0107] In at least one embodiment of the present application, the HARQ process ID indicated by the first DCI and the second DCI is the same, the first PUSCH and the second PUSCH are located on the same carrier, and the time domains of the first PUSCH and the second PUSCH do not overlap.

[0108] The transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB, which can also be expressed as: the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB. In one embodiment, the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB, including:

[0109] The transmission of the first PUSCH and the transmission of the second PUSCH are associated with N identical first TBs; wherein N is greater than or equal to 1; or,

[0110] The transmission of the first PUSCH is associated with M1 TBs, the transmission of the second PUSCH is associated with M2 TBs, and there is at least one identical first TB between the M1 TBs associated with the transmission of the first PUSCH and the M2 TBs associated with the transmission of the second PUSCH; M1 and M2 are both greater than or equal to 1, and at least one of M1 and M2 is greater than or equal to 2.

[0111] Here, the transmission of the first PUSCH and the transmission of the second PUSCH are associated with N identical first TBs, which can be understood as the number of TBs associated with the transmission of the first PUSCH and the transmission of the second PUSCH is the same, and the TBs associated with the transmission of the first PUSCH and the transmission of the second PUSCH are the same.

[0112] Alternatively, the number of TBs associated with the transmission of the first PUSCH and the number of TBs associated with the transmission of the second PUSCH are different, but there is at least one identical first TB between the TBs associated with the transmission of the first PUSCH and the TBs associated with the transmission of the second PUSCH. Here, at least one of the transmission of the first PUSCH and the transmission of the second PUSCH is associated with multiple TBs.

[0113] In the above solution, it is only limited that the number of TBs associated with the transmission of the first PUSCH and the transmission of the second PUSCH may be the same or different, and the number of associated TBs is not specifically limited.

[0114] In actual application, based on the above scheme, the PUSCH transmission or repeated transmission of PUSCH scheduled by two different DCIs is associated, and multiple DCIs schedule multiple PUSCH transmissions of the same TB, thereby improving the uplink coverage performance of the associated TB.

[0115] In one embodiment, the reception of the second DCI is earlier than the end time of the first PUSCH transmission.

[0116] That is to say, before the first PUSCH scheduled by the first DCI is transmitted, the terminal can receive the second PUSCH scheduled by the second DCI, wherein the second DCI has the same HARQ process ID as the first DCI to indicate the scheduling of the transmission of a new PUSCH with the same HARQ process. In the related art, for a given HARQ process ID, only one PUSCH is supported to exist at the same time, but multiple PUSCHs are not supported to exist at the same time, that is, for a given HARQ process ID, before the first PUSCH is transmitted, the terminal does not expect to receive a new DCI indication with the same HARQ process ID. Therefore, in the related art, before the first PUSCH scheduled by the first DCI is transmitted, the terminal does not expect to receive the second DCI with the same HARQ process ID. It can be seen that the solution of the embodiment of the present application breaks through the limitations and constraints of the related art to adapt to the differentiated uplink interference conditions on different symbols in specific scenarios.

[0117] Here, it should be noted that the terminal involved in the relevant embodiments of the present application does not expect a certain condition, the terminal does not expect a certain scenario, or other situations that the terminal does not expect can be understood or equivalently expressed as follows according to the communication protocol or the common expression habits in the communication field:

[0118] The terminal expects that the following situations will not occur, including: a certain condition or a certain scenario; or,

[0119] The behavior of the terminal under certain conditions or scenarios is undefined; or,

[0120] No constraints are imposed on terminal behavior under certain conditions or scenarios; or,

[0121] If a certain condition or scenario is met, the terminal will ignore or not execute the corresponding configuration or instruction of the network; or,

[0122] It is recommended that the base station not configure or indicate a certain condition or a certain scenario.

[0123] At present, in special scenarios such as SBFD, a symbol in a TDD carrier has both uplink and downlink transmissions, and it is difficult to implement all symbol types using a set of configuration parameters corresponding to a DCI. In response to the above problem, this case allows the terminal to receive the first DCI and the second DCI sent by the base station, and the transmission or repeated transmission of the PUSCH scheduled by the two DCIs is associated, and the two DCIs are allowed to use differentiated scheduling parameters.

[0124] Since some terminal behaviors in this case are different from related technologies, in order to avoid ambiguity in terminal behaviors, that is, to make the terminal clear under what conditions to adopt the solution in the related technology and under what circumstances to adopt the new terminal behaviors protected in this case, in some embodiments, this case sets some explicit or implicit rules for "enabling" the new terminal behaviors in this case, including but not limited to: the following restrictions on the first DCI and the second DCI:

[0125] The first DCI and the second DCI are associated with the same CORESET; and / or,

[0126] The aggregation level control channel element (CCE) of the candidate physical downlink control channel (PDCCH) associated with the first DCI and the second DCI is the same; and / or,

[0127] The first DCI and the second DCI are scrambled by the same Radio Network Temporary Identifier (RNTI); and / or,

[0128] The first DCI and the second DCI are located in the same time slot, or the first DCI and the second DCI are located in the same time slot configuration period; or the candidate PDCCHs associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain; and / or,

[0129] The candidate PDCCHs associated with the first DCI and the second DCI are associated with the same search space set; and / or,

[0130] The monitoring timings of the search space set associated with the candidate PDCCH associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain.

[0131] For example, taking the SBFD scenario as an example, refer to Figure 4 , the base station sends two DCIs in slot n: DCI 1 and DCI 2, where DCI 1 schedules the terminal to transmit PUSCH 1 on 3X, and DCI 2 schedules the terminal to transmit PUSCH 2 on 1U, where "X" represents SBFD symbols and "U" represents full UL symbols. In this way, the base station schedules PUSCH transmission of different symbols on a time slot through two DCIs.

[0132] The rule also includes: in one embodiment, the HARQ process IDs indicated by the first DCI and the second DCI belong to a first HARQ process set.

[0133] Here, a limiting condition is proposed for the terminal behavior, that is, when the HARQ process IDs indicated by the first DCI and the second DCI belong to the same HARQ process set, it is allowed to schedule different PUSCHs on the same TB through two DCIs, that is, the transmission behaviors of the PUSCHs scheduled by the two DCIs are allowed to be associated.

[0134] In actual application, the first HARQ process set may be indicated to the terminal through high-level signaling, such as radio resource control (RRC, Radio Resource Control) signaling.

[0135] In one embodiment, the transmission of the first PUSCH and / or the transmission of the second PUSCH includes L time slots, L transmission opportunities or L actual repetitions; and L is greater than or equal to 1.

[0136] Here, when L is equal to 1, transmission of the first PUSCH and / or transmission of the second PUSCH supports single-slot transmission, and when L is greater than 1, transmission of the first PUSCH and / or transmission of the second PUSCH supports multi-slot transmission.

[0137] Among them, multi-slot transmission includes but is not limited to: any one of PUSCH repetition transmission type A (PUSCH repetition Type A), PUSCH repetition transmission type B (PUSCH repetition Type B), and multi-slot transmission block (TBoMS, TB processing over multiple slots). For PUSCH repetition transmission type A, PUSCH includes multiple transmission occasions (transmission occasions), and for PUSCH repetition transmission type B, PUSCH includes actual repetition (actual repetition).

[0138] In related technologies, the NDI field in the DCI is only related to whether the TB in the current transmission is a new transmission or a retransmission. In this case, since the first PUSCH and the second PUSCH are associated with at least one identical first TB, the NDI fields of the first DCI and the second DCI may have a certain correlation. Based on this correlation, a certain performance gain can be obtained through system design.

[0139] Preferably, for the case where the transmission of the first PUSCH and the transmission of the second PUSCH are both associated with only one TB, and the TBs associated with the two are the same, the NDI fields in the first DCI and the second DCI are both associated with the first TB. Based on this, in one embodiment, the NDI field associated with the first TB in the second DCI is not flipped or is the first value; or, the terminal does not expect the NDI field associated with the first TB in the second DCI to be flipped or the terminal does not expect the NDI field associated with the first TB in the second DCI to be not the first value.

[0140] Specifically, when the multi-slot transmission is PUSCH repetition transmission type A or PUSCH repetition transmission type B, for a given first TB, the PUSCH occasions in the first PUSCH and the second PUSCH are different RV versions of the TB. Figure 5 For example, the role of DCI 2 is just to expand the PUSCH transmission resources indicated by DCI 1, which is an alternative indication method for repeated PUSCH transmission. Since PUSCH 1 indicated by DCI 1 is transmitted first, and PUSCH 2 indicated by DCI 2 is transmitted later, the second PUSCH should be a retransmission of the first PUSCH, not a new transmission.

[0141] Based on the above understanding, there are two specific indication methods for the NDI field in the second DCI:

[0142] Indication mode 1: indicates that the NDI field associated with the first TB in the second DCI is not toggled, that is, indicates that the second PUSCH scheduled by the second DCI is a retransmission. In actual application, indication mode 1 can also be described as: the terminal does not expect the NDI field in the second DCI associated with the first TB to be toggled;

[0143] Indication method 2: Indicates that the NDI field in the second DCI is the first value. Here, the first value is a preset value, for example, let NDI = 0. In actual application, indication method 2 can also be described as: the terminal does not expect the NDI field in the second DCI to be other than the first value, for example, when the first value is 0, that is, NDI = 0, the terminal does not expect NDI = 1 in the second DCI.

[0144] Based on the above indication, the terminal can understand that the NDI field in the second DCI is a placeholder and does not carry additional information, which can improve the robustness of the encoding and decoding.

[0145] In the related art, the RV field in the DCI is used to indicate the redundancy version configuration determined for one or more PUSCH transmission opportunities currently scheduled. If a similar design idea is adopted, for the case where the transmission of the first PUSCH and the transmission of the second PUSCH are both associated with only one TB, and the TBs associated with the two are the same, the RV fields in the first DCI and the second DCI are both associated with the first TB. Based on this, Figure 6 As shown, in one embodiment, based on the RV field associated with the first TB in the first DCI, the n1th transmission opportunity or the actual repetition RV applied to the first TB is determined; wherein the count of the n1 only considers the transmission opportunities associated with the first PUSCH; and / or, based on the RV field associated with the first TB in the second DCI, the n2th transmission machine or the actual repetition RV applied to the first TB is determined; wherein the count of the n2 only considers the transmission opportunities associated with the second PUSCH.

[0146] In the related art, an index value is determined according to the RV field indicated in the DCI, and a corresponding RV value is further determined based on the determined index value. Figure 6 Example, Figure 6In the example, PUSCH 1 and PUSCH 2 do not have overlapping time spans, or DCI 1 and DCI 2 do not have overlapping time spans, that is, the time interval from the first PUSCH transmission opportunity or the start of the actual repetition of PUSCH 1 to the last PUSCH transmission opportunity or the end of the actual repetition of PUSCH 1, and the time interval from the first PUSCH transmission opportunity or the start of the actual repetition of PUSCH 2 to the last PUSCH transmission opportunity or the end of the actual repetition of PUSCH 2, the two time intervals do not overlap, then, based on the above RV value determination method, the RVs of multiple transmission opportunities or actual repetitions of the first PUSCH and the second PUSCH can be determined respectively, so that the first PUSCH and the second PUSCH jointly obtain an optimal RV repetition pattern, such as Figure 6 {RV0, RV2, RV3, RV1, …} are shown.

[0147] However, in actual application, when the time spans of the first PUSCH and the second PUSCH overlap in whole or in part, if the design idea similar to the aforementioned and related technologies is still adopted, "according to the RV field associated with the first TB in the first DCI, determine the n1th transmission opportunity or the actual repeated RV applied to the first TB; wherein the count of the n1 only considers the transmission opportunity associated with the first PUSCH; and / or, according to the RV field associated with the first TB in the second DCI, determine the n2th transmission machine or the actual repeated RV applied to the first TB; wherein the count of the n2 only considers the transmission opportunity associated with the second PUSCH", that is, "if the RV values ​​of multiple transmission opportunities or actual repetitions of the first PUSCH and the second PUSCH are determined respectively", then it may be as follows Figure 7 As shown, the last symbol "U" of the first TDD frame structure and the first symbol "X" of the second TDD frame structure both use RV1, making it impossible to ensure that the first PUSCH and the second PUSCH jointly implement the optimal RV repetition mode.

[0148] In response to the above problems, this case proposes a new RV determination method, including: determining the RV applied to the nth transmission opportunity or actual repetition of the first TB according to the RV field associated with the first TB in the first DCI; wherein the count of n takes into account the transmission opportunities or actual repetitions associated with the first PUSCH and the second PUSCH.

[0149] The above method can obtain the optimal RV repeat pattern. Figure 8As shown, the transmission opportunities or actual repetitions associated with the first PUSCH and the second PUSCH are jointly counted, and finally the first PUSCH and the second PUSCH jointly obtain the optimal RV repetition pattern {RV0, RV2, RV3, RV1, ...}.

[0150] In addition, considering that the first PUSCH and the second PUSCH are associated with at least one same first TB, the RV fields of the first DCI and the second DCI may have a certain correlation. Based on this correlation, a certain performance gain can be obtained through system design.

[0151] Preferably, when the multi-slot transmission process is a multi-slot transmission block, the first PUSCH and the second PUSCH together constitute the same RV version of 1 TB, so for the second DCI, the indicated RV field is useless. Therefore, the RV field associated with the first TB in the second DCI is the second value; or, the terminal does not expect the RV field associated with the first TB in the second DCI to be other than the second value. Based on the above indication, the terminal can understand that the RV field in the second DCI is a placeholder and does not carry additional information, so that the robustness of the encoding and decoding can be improved.

[0152] In one embodiment, a value of at least one of the following fields in the second DCI is the same as a value of a corresponding field in the first DCI or is a preset value:

[0153] Downlink allocation index;

[0154] SRS request;

[0155] SRS offset indication;

[0156] CSI request.

[0157] In actual application, the above-mentioned field in the uplink grant DCI (UL grant DCI) is not related to the currently scheduled PUSCH transmission, but is used to indicate other information. Therefore, if the above-mentioned field exists in the first DCI and the second DCI for indicating information, then the information indicated in the above-mentioned field in the first DCI and the second DCI should remain the same to avoid ambiguity in the terminal; alternatively, for the above-mentioned field, only the field indication information of the first DCI can be used, and the above-mentioned field in the second DCI can be set to a preset placeholder, for example, set to all 0s, so as to improve the robustness of the encoding and decoding of the second DCI.

[0158] In addition, it should be noted that some fields in the UL grant DCI are related to the currently scheduled PUSCH transmission. In this case, it is not recommended to use the configuration scheme for the domain instruction information of the first DCI and the second DCI mentioned above. Among them, the fields related to the currently scheduled PUSCH transmission include but are not limited to: Frequency domain resource assignment, Timedomain resource assignment, Frequency hopping flag, Modulation and coding scheme, TPC command for scheduled PUSCH, SRS resource set indicator, SRSresource indicator, Precoding information and number of layers, Antenna ports, CBG transmission information (CBGTI), PTRS-DMRS association, etc.

[0159] In one embodiment, the transmission resources of the first PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the second PUSCH completely do not overlap with the first time-frequency resource set in the time domain; or,

[0160] The transmission resources of the second PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the first PUSCH completely do not overlap with the first time-frequency resource set in the time domain.

[0161] The first time-frequency resource set includes an uplink subband or an SBFD subband or an UDD subband.

[0162] In actual application, in the SBFD scenario, the first time-frequency resource set is also referred to as a subband, or a SBFD subband, or a UDD subband. Furthermore, the first time-frequency resource set can be an uplink subband, or a SBFD subband, or a UDD subband. In a flexible / dynamic TDD scenario, the first time-frequency resource set is a time-frequency resource set with cross link interference (CLI, cross link interference), or a time-frequency resource set with different uplink and downlink transmission directions of adjacent base stations. That is, for the first time-frequency resource set, the uplink and downlink transmission directions of adjacent base stations are different. In actual application, the terminal can determine the first time-frequency resource set based on high-level signaling and / or DCI indications.

[0163] Corresponding to the PUSCH repeated transmission method on the terminal side, the embodiment of the present application also provides a PUSCH transmission method, which is applied to the base station, such as Fig. 9 As shown, the method includes:

[0164] Step 901: Send a first DCI and a second DCI.

[0165] Among them, the first DCI is used to schedule the transmission of the first PUSCH; the second DCI is used to schedule the transmission of the second PUSCH; the starting time of the first PUSCH transmission is earlier than the starting time of the second PUSCH transmission; the HARQ process ID indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB.

[0166] In one embodiment, the time domains of the first PUSCH and the second PUSCH do not overlap.

[0167] In one embodiment, the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one same first TB, including one of the following:

[0168] The transmission of the first PUSCH and the transmission of the second PUSCH are associated with N identical first TBs; wherein N is greater than or equal to 1; or,

[0169] The transmission of the first PUSCH is associated with M1 TBs, the transmission of the second PUSCH is associated with M2 TBs, and there is at least one identical first TB between the M1 TBs associated with the transmission of the first PUSCH and the M2 TBs associated with the transmission of the second PUSCH; M1 and M2 are both greater than or equal to 1, and at least one of M1 and M2 is greater than or equal to 2.

[0170] In one embodiment, the reception of the second DCI is earlier than the end time of the first PUSCH transmission.

[0171] In one embodiment, the first DCI and the second DCI are associated with the same CORESET; and / or,

[0172] The aggregation level CCE of the candidate PDCCH associated with the first DCI and the second DCI is the same; and / or,

[0173] The first DCI and the second DCI are scrambled by the same RNTI; and / or,

[0174] The first DCI and the second DCI are located in the same time slot, or the first DCI and the second DCI are located in the same time slot configuration period; or the candidate PDCCHs associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain; and / or,

[0175] The candidate PDCCHs associated with the first DCI and the second DCI are associated with the same search space set; and / or,

[0176] The monitoring timings of the search space set associated with the candidate PDCCH associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain.

[0177] In one embodiment, the HARQ process IDs indicated by the first DCI and the second DCI belong to a first HARQ process set.

[0178] In one embodiment, the transmission of the first PUSCH and / or the transmission of the second PUSCH includes L time slots, L transmission opportunities or L actual repetitions; and L is greater than or equal to 1.

[0179] In one embodiment, the NDI field associated with the first TB in the second DCI is not flipped or takes the first value; or,

[0180] The terminal does not expect the NDI field associated with the first TB in the second DCI to flip, or the terminal does not expect the NDI field associated with the first TB in the second DCI to be other than the first value.

[0181] In one embodiment, the RV applied to the n1th transmission opportunity or actual repetition of the first TB is determined according to the RV field associated with the first TB in the first DCI; wherein the count of n1 only considers the transmission opportunity associated with the first PUSCH; and / or,

[0182] According to the RV field associated with the first TB in the second DCI, determine the n2th transmission machine or actual repeated RV applied to the first TB; wherein the n2 count only considers the transmission opportunities associated with the second PUSCH.

[0183] In one embodiment, the RV applied to the nth transmission opportunity or actual repetition of the first TB is determined based on the RV field associated with the first TB in the first DCI; wherein the count of n takes into account the transmission opportunities or actual repetitions associated with the first PUSCH and the second PUSCH.

[0184] In one embodiment, the RV field associated with the first TB in the second DCI is a second value; or,

[0185] The terminal does not expect that the RV field associated with the first TB in the second DCI is not the second value.

[0186] In one embodiment, a value of at least one of the following fields in the second DCI is the same as a value of a corresponding field in the first DCI or is a preset value:

[0187] Downlink allocation index;

[0188] SRS request;

[0189] SRS offset indication;

[0190] CSI request.

[0191] In one embodiment, the transmission resources of the first PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the second PUSCH completely do not overlap with the first time-frequency resource set in the time domain; or,

[0192] The transmission resources of the second PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the first PUSCH completely do not overlap with the first time-frequency resource set in the time domain.

[0193] In one embodiment, the first time-frequency resource set includes an uplink subband or a subband BFD subband or a UDD subband.

[0194] The specific implementation of the PUSCH transmission method on the base station side can refer to the above-mentioned embodiment of the PUSCH transmission method on the terminal side, which will not be repeated here.

[0195] In the embodiment of the present application, multiple DCIs schedule the PUSCH of the same TB. Specifically, two DCIs respectively use appropriate configuration parameters to schedule the PUSCH transmission or repeated transmission of different symbol types on the same TB, and the PUSCH transmission or repeated transmission scheduled by these two DCIs are associated, together constituting repeated transmission across different symbol types of a TB. Compared with the situation in the related art where the UL grant DCI can only include one set of parameter configurations, the embodiment of the present application can effectively adapt to the problems of different interference situations, uplink bandwidth differences and / or QCL relationship differences between different symbols in flexible TDD and SBFD networks, thereby improving the uplink coverage performance.

[0196] In order to implement the PUSCH transmission method on the terminal side of the embodiment of the present application, the embodiment of the present application also provides a PUSCH transmission device, which is arranged on the terminal, such as Fig.10 As shown, the device comprises:

[0197] The receiving unit 1001 is configured to receive a first DCI and a second DCI.

[0198] At the same time, in order to implement the PUSCH transmission method on the base station side of the embodiment of the present application, the embodiment of the present application also provides a PUSCH transmission device, which is set on the base station, such as Fig.11 As shown, the device comprises:

[0199] The sending unit 1101 is configured to send a first DCI and a second DCI.

[0200] exist Fig.10 and Fig.11 In an embodiment, the first DCI is used to schedule the transmission of a first PUSCH; the second DCI is used to schedule the transmission of a second PUSCH; the start time of the first PUSCH transmission is earlier than the start time of the second PUSCH transmission; the HARQ process ID indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB.

[0201] In addition, in one embodiment, the time domains of the first PUSCH and the second PUSCH do not overlap.

[0202] In one embodiment, the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one same first TB, including:

[0203] The transmission of the first PUSCH and the transmission of the second PUSCH are associated with N identical first TBs; wherein N is greater than or equal to 1; or,

[0204] The transmission of the first PUSCH is associated with M1 TBs, the transmission of the second PUSCH is associated with M2 TBs, and there is at least one identical first TB between the M1 TBs associated with the transmission of the first PUSCH and the M2 TBs associated with the transmission of the second PUSCH; M1 and M2 are both greater than or equal to 1, and at least one of M1 and M2 is greater than or equal to 2.

[0205] In one embodiment, the reception of the second DCI is earlier than the end time of the first PUSCH transmission.

[0206] In one embodiment, the first DCI and the second DCI are associated with the same CORESET; and / or,

[0207] The aggregation level CCE of the candidate PDCCH associated with the first DCI and the second DCI is the same; and / or,

[0208] The first DCI and the second DCI are scrambled by the same RNTI; and / or,

[0209] The first DCI and the second DCI are located in the same time slot, or the first DCI and the second DCI are located in the same time slot configuration period; or the candidate PDCCHs associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain; and / or,

[0210] The candidate PDCCHs associated with the first DCI and the second DCI are associated with the same search space set; and / or,

[0211] The monitoring timings of the search space set associated with the candidate PDCCH associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain.

[0212] In one embodiment, the HARQ process IDs indicated by the first DCI and the second DCI belong to a first HARQ process set.

[0213] In one embodiment, the transmission of the first PUSCH and / or the transmission of the second PUSCH includes L time slots, L transmission opportunities or L actual repetitions; and L is greater than or equal to 1.

[0214] In one embodiment, the NDI field associated with the first TB in the second DCI is not flipped or takes the first value; or,

[0215] The terminal does not expect the NDI field associated with the first TB in the second DCI to flip, or the terminal does not expect the NDI field associated with the first TB in the second DCI to be other than the first value.

[0216] In one embodiment, the RV applied to the n1th transmission opportunity or actual repetition of the first TB is determined according to the RV field associated with the first TB in the first DCI; wherein the count of n1 only considers the transmission opportunity associated with the first PUSCH; and / or,

[0217] According to the RV field associated with the first TB in the second DCI, determine the n2th transmission machine or actual repeated RV applied to the first TB; wherein the n2 count only considers the transmission opportunities associated with the second PUSCH.

[0218] In one embodiment, the RV applied to the nth transmission opportunity or actual repetition of the first TB is determined based on the RV field associated with the first TB in the first DCI; wherein the count of n takes into account the transmission opportunities or actual repetitions associated with the first PUSCH and the second PUSCH.

[0219] In one embodiment, the RV field associated with the first TB in the second DCI is a second value; or,

[0220] The terminal does not expect that the RV field associated with the first TB in the second DCI is not the second value.

[0221] In one embodiment, a value of at least one of the following fields in the second DCI is the same as a value of a corresponding field in the first DCI or is a preset value:

[0222] Downlink allocation index;

[0223] SRS request;

[0224] SRS offset indication;

[0225] CSI request.

[0226] In one embodiment, the transmission resources of the first PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the second PUSCH completely do not overlap with the first time-frequency resource set in the time domain; or,

[0227] The transmission resources of the second PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the first PUSCH completely do not overlap with the first time-frequency resource set in the time domain.

[0228] In one embodiment, the first time-frequency resource set includes an uplink subband or a SBFD subband or a UDD subband.

[0229] In actual application, the receiving unit 1001 may be implemented by a communication interface in a PUSCH transmission device at the terminal side; and the sending unit 1101 may be implemented by a communication interface in a PUSCH transmission device at the base station side.

[0230] It should be noted that: the above embodiment provides a PUSCH transmission device, and only uses the division of the above program modules as an example when performing PUSCH transmission. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the above-described processing. In addition, the PUSCH transmission device and the PUSCH transmission method embodiment provided in the above embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0231] Based on the hardware implementation of the above program modules, and in order to implement the method on the terminal side of the embodiment of the present application, the embodiment of the present application also provides a terminal, such as Fig.12 As shown, the terminal 1200 includes:

[0232] The first communication interface 1201 is capable of exchanging information with other network nodes;

[0233] The first processor 1202 is connected to the first communication interface 1201 to implement information exchange with other network nodes, and is used to execute the method provided by one or more technical solutions of the terminal side when running a computer program. The computer program is stored in the first memory 1203.

[0234] Specifically, the first communication interface 1201 is used to receive the first DCI and the second DCI.

[0235] Among them, the first DCI is used to schedule the transmission of the first PUSCH; the second DCI is used to schedule the transmission of the second PUSCH; the starting time of the first PUSCH transmission is earlier than the starting time of the second PUSCH transmission; the HARQ process ID indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB.

[0236] In one embodiment, the time domains of the first PUSCH and the second PUSCH do not overlap.

[0237] In one embodiment, the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one same first TB, including:

[0238] The transmission of the first PUSCH and the transmission of the second PUSCH are associated with N identical first TBs; wherein N is greater than or equal to 1; or,

[0239] The transmission of the first PUSCH is associated with M1 TBs, the transmission of the second PUSCH is associated with M2 TBs, and there is at least one identical first TB between the M1 TBs associated with the transmission of the first PUSCH and the M2 TBs associated with the transmission of the second PUSCH; M1 and M2 are both greater than or equal to 1, and at least one of M1 and M2 is greater than or equal to 2.

[0240] In one embodiment, the reception of the second DCI is earlier than the end time of the first PUSCH transmission.

[0241] In one embodiment, the first DCI and the second DCI are associated with the same CORESET; and / or,

[0242] The aggregation level CCE of the candidate PDCCH associated with the first DCI and the second DCI is the same; and / or,

[0243] The first DCI and the second DCI are scrambled by the same RNTI; and / or,

[0244] The first DCI and the second DCI are located in the same time slot, or the first DCI and the second DCI are located in the same time slot configuration period; or the candidate PDCCHs associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain; and / or,

[0245] The candidate PDCCHs associated with the first DCI and the second DCI are associated with the same search space set; and / or,

[0246] The monitoring timings of the search space set associated with the candidate PDCCH associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain.

[0247] In one embodiment, the HARQ process IDs indicated by the first DCI and the second DCI belong to a first HARQ process set.

[0248] In one embodiment, the transmission of the first PUSCH and / or the transmission of the second PUSCH includes L time slots, L transmission opportunities or L actual repetitions; and L is greater than or equal to 1.

[0249] In one embodiment, the NDI field associated with the first TB in the second DCI is not flipped or takes the first value; or,

[0250] The terminal does not expect the NDI field associated with the first TB in the second DCI to flip, or the terminal does not expect the NDI field associated with the first TB in the second DCI to be other than the first value.

[0251] In one embodiment, the RV applied to the n1th transmission opportunity or actual repetition of the first TB is determined according to the RV field associated with the first TB in the first DCI; wherein the count of n1 only considers the transmission opportunity associated with the first PUSCH; and / or,

[0252] According to the RV field associated with the first TB in the second DCI, determine the n2th transmission machine or actual repeated RV applied to the first TB; wherein the n2 count only considers the transmission opportunities associated with the second PUSCH.

[0253] In one embodiment, the RV applied to the nth transmission opportunity or actual repetition of the first TB is determined based on the RV field associated with the first TB in the first DCI; wherein the count of n takes into account the transmission opportunities or actual repetitions associated with the first PUSCH and the second PUSCH.

[0254] In one embodiment, the RV field associated with the first TB in the second DCI is a second value; or,

[0255] The terminal does not expect that the RV field associated with the first TB in the second DCI is not the second value.

[0256] In one embodiment, a value of at least one of the following fields in the second DCI is the same as a value of a corresponding field in the first DCI or is a preset value:

[0257] Downlink allocation index;

[0258] SRS request;

[0259] SRS offset indication;

[0260] CSI request.

[0261] In one embodiment, the transmission resources of the first PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the second PUSCH completely do not overlap with the first time-frequency resource set in the time domain; or,

[0262] The transmission resources of the second PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the first PUSCH completely do not overlap with the first time-frequency resource set in the time domain.

[0263] In one embodiment, the first time-frequency resource set includes an uplink subband or a SBFD subband or a UDD subband.

[0264] It should be noted that the specific processing process of the first processor 1202 and the first communication interface 1201 can be understood by referring to the above method.

[0265] Of course, in actual application, the various components in the terminal 1200 are coupled together through the bus system 1204. It can be understood that the bus system 1204 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1204 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig.12 Various buses are labeled as bus system 1204.

[0266] The first memory 1203 in the embodiment of the present application is used to store various types of data to support the operation of the terminal 1200. Examples of such data include: any computer program used to operate on the terminal 1200.

[0267] The method disclosed in the above embodiment of the present application can be applied to the first processor 1202, or implemented by the first processor 1202. The first processor 1202 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of the hardware in the first processor 1202 or an instruction in the form of software. The above-mentioned first processor 1202 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The first processor 1202 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, which is located in the first memory 1203, and the first processor 1202 reads the information in the first memory 1203 and completes the steps of the above method in combination with its hardware.

[0268] In an exemplary embodiment, terminal 1200 may be implemented by one or more application specific integrated circuits (ASIC), DSP, programmable logic device (PLD), complex programmable logic device (CPLD), field programmable gate array (FPGA), general processor, controller, microcontroller (MCU), microprocessor, or other electronic components to execute the aforementioned method.

[0269] Based on the hardware implementation of the above program modules, and in order to implement the method on the base station side of the embodiment of the present application, the embodiment of the present application also provides a base station, such as Fig.13 As shown, the base station 1300 includes:

[0270] The second communication interface 1301 is capable of exchanging information with other network nodes;

[0271] The second processor 1302 is connected to the second communication interface 1301 to implement information exchange with other network nodes, and is used to execute the method provided by one or more technical solutions of the base station side when running a computer program. The computer program is stored in the second memory 1303.

[0272] Specifically, the second communication interface 1301 is used to send the first DCI and the second DCI.

[0273] Among them, the first DCI is used to schedule the transmission of the first PUSCH; the second DCI is used to schedule the transmission of the second PUSCH; the starting time of the first PUSCH transmission is earlier than the starting time of the second PUSCH transmission; the HARQ process ID indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB.

[0274] In one embodiment, the time domains of the first PUSCH and the second PUSCH do not overlap.

[0275] In one embodiment, the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one same first TB, including:

[0276] The transmission of the first PUSCH and the transmission of the second PUSCH are associated with N identical first TBs; wherein N is greater than or equal to 1; or,

[0277] The transmission of the first PUSCH is associated with M1 TBs, the transmission of the second PUSCH is associated with M2 TBs, and there is at least one identical first TB between the M1 TBs associated with the transmission of the first PUSCH and the M2 TBs associated with the transmission of the second PUSCH; M1 and M2 are both greater than or equal to 1, and at least one of M1 and M2 is greater than or equal to 2.

[0278] In one embodiment, the reception of the second DCI is earlier than the end time of the first PUSCH transmission.

[0279] In one embodiment, the first DCI and the second DCI are associated with the same CORESET; and / or,

[0280] The aggregation level CCE of the candidate PDCCH associated with the first DCI and the second DCI is the same; and / or,

[0281] The first DCI and the second DCI are scrambled by the same RNTI; and / or,

[0282] The first DCI and the second DCI are located in the same time slot, or the first DCI and the second DCI are located in the same time slot configuration period; or the candidate PDCCHs associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain; and / or,

[0283] The candidate PDCCHs associated with the first DCI and the second DCI are associated with the same search space set; and / or,

[0284] The monitoring timings of the search space set associated with the candidate PDCCH associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain.

[0285] In one embodiment, the HARQ process IDs indicated by the first DCI and the second DCI belong to a first HARQ process set.

[0286] In one embodiment, the transmission of the first PUSCH and / or the transmission of the second PUSCH includes L time slots, L transmission opportunities or L actual repetitions; and L is greater than or equal to 1.

[0287] In one embodiment, the NDI field associated with the first TB in the second DCI is not flipped or takes the first value; or,

[0288] The terminal does not expect the NDI field associated with the first TB in the second DCI to flip, or the terminal does not expect the NDI field associated with the first TB in the second DCI to be other than the first value.

[0289] In one embodiment, the RV applied to the n1th transmission opportunity or actual repetition of the first TB is determined according to the RV field associated with the first TB in the first DCI; wherein the count of n1 only considers the transmission opportunity associated with the first PUSCH; and / or,

[0290] According to the RV field associated with the first TB in the second DCI, determine the n2th transmission machine or actual repeated RV applied to the first TB; wherein the n2 count only considers the transmission opportunities associated with the second PUSCH.

[0291] In one embodiment, the RV applied to the nth transmission opportunity or actual repetition of the first TB is determined based on the RV field associated with the first TB in the first DCI; wherein the count of n takes into account the transmission opportunities or actual repetitions associated with the first PUSCH and the second PUSCH.

[0292] In one embodiment, the RV field associated with the first TB in the second DCI is a second value; or,

[0293] The terminal does not expect that the RV field associated with the first TB in the second DCI is not the second value.

[0294] In one embodiment, a value of at least one of the following fields in the second DCI is the same as a value of a corresponding field in the first DCI or is a preset value:

[0295] Downlink allocation index;

[0296] SRS request;

[0297] SRS offset indication;

[0298] CSI request.

[0299] In one embodiment, the transmission resources of the first PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the second PUSCH completely do not overlap with the first time-frequency resource set in the time domain; or,

[0300] The transmission resources of the second PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the first PUSCH completely do not overlap with the first time-frequency resource set in the time domain.

[0301] In one embodiment, the first time-frequency resource set includes an uplink subband or a SBFD subband or a UDD subband.

[0302] It should be noted that the specific processing process of the second processor 1302 and the second communication interface 1301 can be understood by referring to the above method.

[0303] Of course, in actual application, the various components in the base station 1300 are coupled together through the bus system 1304. It can be understood that the bus system 1304 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1304 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig.13 Various buses are labeled as bus system 1304.

[0304] The second memory 1303 in the embodiment of the present application is used to store various types of data to support the operation of the base station 1300. Examples of such data include: any computer program used to operate on the base station 1300.

[0305] The method disclosed in the above embodiment of the present application can be applied to the second processor 1302, or implemented by the second processor 1302. The second processor 1302 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit or software instructions in the second processor 1302. The above-mentioned second processor 1302 may be a general-purpose processor, DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The second processor 1302 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, which is located in the second memory 1303, and the second processor 1302 reads the information in the second memory 1303 and completes the steps of the above method in combination with its hardware.

[0306] In an exemplary embodiment, the base station 1300 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general purpose processors, controllers, MCUs, Microprocessors, or other electronic components to perform the aforementioned methods.

[0307] It can be understood that the memory (first memory 1203, second memory 1303) of the embodiment of the present application can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a ferromagnetic random access memory, a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and direct RAM bus random access memory (DRRAM, Direct Rambus Random Access Memory).The memories described in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0308] In an exemplary embodiment, the embodiment of the present application further provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, for example, including a first memory 1203 storing a computer program, and the computer program can be executed by the first processor 1202 of the first network node 1200 to complete the steps of the aforementioned first network node side method. For another example, including a second memory 1303 storing a computer program, the computer program can be executed by the second processor 1302 of the third network node 1300 to complete the steps of the aforementioned third network node side method. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface storage, optical disk, or CD-ROM.

[0309] It should be noted that: "first", "second", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. The term "and / or" herein is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the term "at least one" herein represents any combination of at least two of any one or more of a plurality of. For example, including at least one of A, B, and C, may represent any one or more elements selected from the set consisting of A, B, and C. In addition, the technical solutions described in the embodiments of the present application may be arbitrarily combined without conflict. The above is only a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application.

Claims

1. A physical uplink shared channel PUSCH transmission method, characterized in that: Applied to terminals, including: Receive first downlink control information DCI and second DCI; wherein, The first DCI is used to schedule the transmission of a first PUSCH; the second DCI is used to schedule the transmission of a second PUSCH; the starting time of the first PUSCH transmission is earlier than the starting time of the second PUSCH transmission; the hybrid automatic repeat request HARQ process identifier ID indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first transmission block TB.

2. The method according to claim 1, characterized in that The time domains of the first PUSCH and the second PUSCH do not overlap.

3. The method according to claim 1, characterized in that The transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one same first TB, including: The transmission of the first PUSCH and the transmission of the second PUSCH are associated with N identical first TBs; wherein N is greater than or equal to 1; or, The transmission of the first PUSCH is associated with M1 TBs, the transmission of the second PUSCH is associated with M2 TBs, and there is at least one identical first TB between the M1 TBs associated with the transmission of the first PUSCH and the M2 TBs associated with the transmission of the second PUSCH; M1 and M2 are both greater than or equal to 1, and at least one of M1 and M2 is greater than or equal to 2.

4. The method according to claim 1, characterized in that: The reception of the second DCI is earlier than the end time of the first PUSCH transmission.

5. The method according to claim 1, characterized in that The first DCI and the second DCI are associated with the same control resource set CORESET; and / or, The aggregation level control channel elements CCE of the candidate physical downlink control channel PDCCH associated with the first DCI and the second DCI are the same; and / or, The first DCI and the second DCI are scrambled by the same radio network temporary identifier RNTI; and / or, The first DCI and the second DCI are located in the same time slot, or the first DCI and the second DCI are located in the same time slot configuration period; or the candidate PDCCHs associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain; and / or, The candidate PDCCHs associated with the first DCI and the second DCI are associated with the same search space set; and / or, The monitoring timings of the search space set associated with the candidate PDCCH associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain.

6. The method according to claim 1, characterized in that The HARQ process IDs indicated by the first DCI and the second DCI belong to a first HARQ process set.

7. The method according to claim 1, characterized in that The transmission of the first PUSCH and / or the transmission of the second PUSCH includes L time slots, L transmission opportunities or L actual repetitions; and L is greater than or equal to 1.

8. The method according to claim 1, characterized in that The new data indication NDI field associated with the first TB in the second DCI is not flipped or takes the first value; or, The terminal does not expect the NDI field associated with the first TB in the second DCI to flip, or the terminal does not expect the NDI field associated with the first TB in the second DCI to be other than the first value.

9. The method according to claim 1, characterized in that: Determine, according to the redundant version RV field associated with the first TB in the first DCI, the RV applied to the n1th transmission opportunity or the actual repetition of the first TB; wherein the count of n1 only considers the transmission opportunity associated with the first PUSCH; and / or, According to the RV field associated with the first TB in the second DCI, determine the n2th transmission machine or actual repeated RV applied to the first TB; wherein the n2 count only considers the transmission opportunities associated with the second PUSCH.

10. The method according to claim 1, characterized in that Determine, based on the RV field associated with the first TB in the first DCI, the RV applied to the nth transmission opportunity or actual repetition of the first TB; wherein the count of n takes into account the transmission opportunities or actual repetitions associated with the first PUSCH and the second PUSCH.

11. The method according to claim 10, characterized in that The RV field associated with the first TB in the second DCI is a second value; or, The terminal does not expect that the RV field associated with the first TB in the second DCI is not the second value.

12. The method according to claim 1, characterized in that A value of at least one of the following fields in the second DCI is the same as a value of a corresponding field in the first DCI or is a preset value: Downlink allocation index; Sounding reference signal SRS request; SRS offset indication; Channel state information CSI request.

13. The method according to claim 1, characterized in that The transmission resources of the first PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the second PUSCH completely do not overlap with the first time-frequency resource set in the time domain; or, The transmission resources of the second PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the first PUSCH completely do not overlap with the first time-frequency resource set in the time domain.

14. The method according to claim 13, characterized in that The first time-frequency resource set includes an uplink subband or a non-overlapping full-duplex SBFD subband or a unified duplex UDD subband.

15. A PUSCH repeated transmission method, characterized in that: Applied to base stations, including: Send a first DCI and a second DCI; wherein, The first DCI is used to schedule the transmission of a first PUSCH; the second DCI is used to schedule the transmission of a second PUSCH; the starting time of the first PUSCH transmission is earlier than the starting time of the second PUSCH transmission; the HARQ process ID indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB.

16. The method according to claim 15, characterized in that The time domains of the first PUSCH and the second PUSCH do not overlap.

17. The method according to claim 15, characterized in that The transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one same first TB, including one of the following: The transmission of the first PUSCH and the transmission of the second PUSCH are associated with N identical first TBs; wherein N is greater than or equal to 1; or, The transmission of the first PUSCH is associated with M1 TBs, the transmission of the second PUSCH is associated with M2 TBs, and there is at least one identical first TB between the M1 TBs associated with the transmission of the first PUSCH and the M2 TBs associated with the transmission of the second PUSCH; M1 and M2 are both greater than or equal to 1, and at least one of M1 and M2 is greater than or equal to 2.

18. The method according to claim 15, characterized in that The reception of the second DCI is earlier than the end time of the first PUSCH transmission.

19. The method according to claim 15, characterized in that The first DCI and the second DCI are associated with the same CORESET; and / or, The aggregation level CCE of the candidate PDCCH associated with the first DCI and the second DCI is the same; and / or, The first DCI and the second DCI are scrambled by the same RNTI; and / or, The first DCI and the second DCI are located in the same time slot, or the first DCI and the second DCI are located in the same time slot configuration period; or the candidate PDCCHs associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain; and / or, The candidate PDCCHs associated with the first DCI and the second DCI are associated with the same search space set; and / or, The monitoring timings of the search space set associated with the candidate PDCCH associated with the first DCI and the second DCI partially overlap or completely overlap in the time domain.

20. The method according to claim 15, characterized in that The HARQ process IDs indicated by the first DCI and the second DCI belong to a first HARQ process set.

21. The method according to claim 15, characterized in that The transmission of the first PUSCH and / or the transmission of the second PUSCH includes L time slots, L transmission opportunities or L actual repetitions; and L is greater than or equal to 1.

22. The method according to claim 15, characterized in that The NDI field associated with the first TB in the second DCI is not flipped or takes the first value; or, The terminal does not expect the NDI field associated with the first TB in the second DCI to flip, or the terminal does not expect the NDI field associated with the first TB in the second DCI to be other than the first value.

23. The method according to claim 15, characterized in that Determine, according to the RV field associated with the first TB in the first DCI, an RV applied to the n1th transmission opportunity or actual repetition of the first TB; wherein the count of n1 only considers the transmission opportunity associated with the first PUSCH; and / or, According to the RV field associated with the first TB in the second DCI, determine the n2th transmission machine or actual repeated RV applied to the first TB; wherein the n2 count only considers the transmission opportunities associated with the second PUSCH.

24. The method according to claim 15, characterized in that Determine, based on the RV field associated with the first TB in the first DCI, the RV applied to the nth transmission opportunity or actual repetition of the first TB; wherein the count of n takes into account the transmission opportunities or actual repetitions associated with the first PUSCH and the second PUSCH.

25. The method according to claim 24, characterized in that The RV field associated with the first TB in the second DCI is a second value; or, The terminal does not expect that the RV field associated with the first TB in the second DCI is not the second value.

26. The method according to claim 15, characterized in that A value of at least one of the following fields in the second DCI is the same as a value of a corresponding field in the first DCI or is a preset value: Downlink allocation index; SRS request; SRS offset indication; CSI request.

27. The method according to claim 15, characterized in that The transmission resources of the first PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the second PUSCH completely do not overlap with the first time-frequency resource set in the time domain; or, The transmission resources of the second PUSCH completely overlap or partially overlap with the first time-frequency resource set in the time domain; the transmission resources of the first PUSCH completely do not overlap with the first time-frequency resource set in the time domain.

28. The method according to claim 27, characterized in that The first time-frequency resource set includes an uplink subband or a subband BFD subband or a UDD subband.

29. A PUSCH transmission device, characterized in that: include: A receiving unit, configured to receive a first DCI and a second DCI; wherein, The first DCI is used to schedule the transmission of a first PUSCH; the second DCI is used to schedule the transmission of a second PUSCH; the starting time of the first PUSCH transmission is earlier than the starting time of the second PUSCH transmission; the HARQ process ID indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB.

30. A PUSCH transmission device, characterized in that: include: A sending unit, configured to send a first DCI and a second DCI; wherein, The first DCI is used to schedule the transmission of a first PUSCH; the second DCI is used to schedule the transmission of a second PUSCH; the starting time of the first PUSCH transmission is earlier than the starting time of the second PUSCH transmission; the HARQ process ID indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB.

31. A terminal, characterized in that: include: A first processor and a first communication interface; wherein, The first communication interface is used to receive the first DCI and the second DCI; wherein, The first DCI is used to schedule the transmission of a first PUSCH; the second DCI is used to schedule the transmission of a second PUSCH; the starting time of the first PUSCH transmission is earlier than the starting time of the second PUSCH transmission; the HARQ process ID indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB.

32. A base station, characterized in that: include: A second processor and a second communication interface; wherein, The second communication interface is used to send the first DCI and the second DCI; wherein, The first DCI is used to schedule the transmission of a first PUSCH; the second DCI is used to schedule the transmission of a second PUSCH; the starting time of the first PUSCH transmission is earlier than the starting time of the second PUSCH transmission; the HARQ process ID indicated by the first DCI and the second DCI is the same; the transmission of the first PUSCH and the transmission of the second PUSCH are associated with at least one identical first TB.

33. A terminal, characterized in that: include: a first processor and a first memory for storing a computer program executable on the processor, Wherein, when the first processor is used to run the computer program, the steps of the method described in any one of claims 1 to 15 are executed.

34. A base station, characterized in that: include: a second processor and a second memory for storing a computer program executable on the processor, Wherein, when the second processor is used to run the computer program, it executes the steps of the method described in any one of claims 15 to 28.

35. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 14, or implements the steps of the method according to any one of claims 15 to 28.

Images