Apparatus and method for transmitting uci on a pusch

Abstract

The transceiver is capable of receiving (210) scheduling information for at least one PUCCH and at least one PUSCH. The scheduling information is capable of scheduling the UE to transmit the at least one PUCCH and the at least one PUSCH. The at least one PUCCH is capable of time-overlapping with the at least one PUSCH. The at least one PUCCH is capable of including at least one type of UCI. The controller is capable of multiplexing (220) the at least one type of UCI in at least one actual repetition of the PUSCH of the at least one PUSCH. The transceiver is capable of transmitting (230) a PUSCH including the multiplexed at least one type of UCI. The PUSCH is capable of overlapping with the PUCCH in the at least one PUCCH. The at least one actual repetition of the PUSCH is capable of having a number of symbols not less than a predefined number of symbols.

Description

Technical Field

[0001] This disclosure relates to apparatus and method for transmitting a PUSCH for UCI. Background Technology

[0002] Currently, wireless communication devices such as UEs communicate with other communication devices using wireless signals. In 3GPP Rel-16NR, UL cancellation indications for inter-UE priority and multiplexing are specified for canceling PUSCH and SRS without considering PUSCH and SRS priorities. Due to the limited granularity of indications for time and frequency resources, some PUSCH or SRS transmissions that need protection may be canceled, and therefore, enhancements to the uplink cancellation indication may be needed. Additionally, in Rel-16PUSCH repetition type B, due to segmentation around unavailable resources, some actual repetitions may have very few REs, and details of UCI multiplexing (e.g., multiplexing timeline conditions and which repetitions reuse the UCI) need to be developed. Attached Figure Description

[0003] To describe how the advantages and features of this disclosure are obtained, the description of this disclosure is presented by reference to specific embodiments thereof shown in the accompanying drawings. These drawings depict only exemplary embodiments of this disclosure and should therefore not be considered as limiting its scope. For clarity, the drawings may have been simplified and are not necessarily drawn to scale.

[0004] Figure 1 This is an example block diagram of a system according to a possible embodiment;

[0005] Figure 2 This is an example flowchart illustrating the operation of a device according to a possible embodiment;

[0006] Figure 3 This is an example flowchart illustrating the operation of a device according to a possible embodiment; and

[0007] Figure 4 This is an example block diagram of an apparatus according to a possible embodiment. Detailed Implementation

[0008] The embodiments provide methods and apparatus for communicating over a wireless network. At least some embodiments are capable of providing apparatus and methods for transmitting a PUSCH with UCI. At least some embodiments are capable of providing uplink control information multiplexing and enhanced uplink cancellation indication in PUSCH repeats. At least some embodiments are also capable of providing apparatus and methods for selectively applying UL cancellation. At least some embodiments are capable of further providing apparatus and methods for UCI multiplexing in PUSCH repeat types A and B.

[0009] According to possible embodiments, the transceiver is capable of receiving scheduling information for at least one PUCCH and at least one PUSCH. The scheduling information is capable of scheduling the UE to transmit at least one PUCCH and at least one PUSCH. At least one PUCCH can overlap in time with at least one PUSCH. At least one PUCCH can include at least one type of UCI. The controller is capable of multiplexing at least one type of UCI in at least one actual repetition of the PUSCH of at least one PUSCH. The transceiver is capable of transmitting the PUSCH including the multiplexed at least one type of UCI. The PUSCH can overlap with the PUCCH of at least one PUCCH. At least one actual repetition of the PUSCH can have a number of symbols not less than a predefined number of symbols.

[0010] Figure 1 This is an example block diagram of system 100 according to a possible embodiment. System 100 may include UE 110, at least one network entity 120 and 125, and network 130. UE 110 may be a wireless wide area network device, user equipment, wireless terminal, portable wireless communication device, smartphone, cellular phone, flip phone, personal digital assistant, smartwatch, personal computer, tablet computer, laptop computer, selective call receiver, IoT device, or any other user equipment capable of transmitting and receiving communication signals on a wireless network. At least one network entity 120 and 125 may be a wireless wide area network base station, may be a NodeB, may be an eNB, may be a gNB, such as a 5G NodeB, may be an unlicensed network base station, may be an access point, may be a base station controller, may be a network controller, may be a TRP, may be a network entity of a different type from other network entities, and / or may be any other network entity capable of providing wireless access between the UE and the network.

[0011] Network 130 can include any type of network capable of transmitting and receiving wireless communication signals. For example, network 130 can include wireless communication networks, cellular telephone networks, TDMA-based networks, CDMA-based networks, OFDMA-based networks, LTE networks, NR networks, 3GPP-based networks, 5G networks, satellite communication networks, high-altitude platform networks, the Internet, and / or other communication networks.

[0012] In operation, UE 110 can communicate with network 130 via at least one network entity 120. For example, UE 110 can send and receive control signals on the control channel and send and receive user data signals on the data channel.

[0013] For UCI reports including HARQ-ACK feedback based on 3GPP TS 38.213V16.1.0 (2020-03), a UE procedure for reporting control information can be provided.

[0014] If the UE is configured with an SCG, the UE will apply the procedures described in this clause to both the MCG and the SCG. When the procedures are applied to the MCG, the terms "secondary cell," "multiple secondary cells," "serving cell," and "multiple serving cells" in this clause refer to the secondary cell, multiple secondary cells, serving cell, and multiple serving cells belonging to the MCG, respectively. When the procedures are applied to the SCG, the terms "secondary cell," "multiple secondary cells," "serving cell," and "multiple serving cells" in this clause refer to the secondary cell, multiple secondary cells (excluding PSCell), serving cell, and multiple serving cells belonging to the SCG, respectively. The term "primary cell" in this clause refers to the PSCell of the SCG.

[0015] If the UE is configured with a PUCCH-SCell, the UE applies the procedures described in this clause to both the primary PUCCH group and the secondary PUCCH group. When the procedures are applied to the primary PUCCH group, the terms "secondary cell," "multiple secondary cells," "serving cell," and "multiple serving cells" in this clause refer to the secondary cell, multiple secondary cells, serving cell, and multiple serving cells belonging to the primary PUCCH group, respectively. When the procedures are applied to the secondary PUCCH group, the terms "secondary cell," "multiple secondary cells," "serving cell," and "multiple serving cells" in this clause refer to the secondary cell, multiple secondary cells (excluding the PUCCH-SCell), serving cell, and multiple serving cells belonging to the secondary PUCCH group, respectively. The term "primary cell" in this clause refers to the PUCCH-SCell of the secondary PUCCH group.

[0016] If the UE is not provided with a CORESETPoolIndex, or is provided with a first CORESET value of 0 on the active DL BWP of the serving cell, and a second CORESET value of 1 on the active DL BWP of the serving cell, and is provided with ACKNACKFeedbackMode=SeparateFeedback, then the UE will apply the procedures described in Sections 9.1 and 9.2.3 to report HARQ-ACK information associated with the first CORESET on the active DL BWP of the serving cell, and to report HARQ-ACK information associated with the second CORESET on the active DL BWP of the serving cell, respectively. HARQ-ACK information reporting is associated with the CORESET through the reception of a PDCCH in a DCI format that triggers the UE to report HARQ-ACK information.

[0017] For NR-DC when both MCG and SCG are operating in FR1 or FR2, and for power margin reports transmitted on MCG or SCG, the UE calculates PH assuming that the UE does not transmit PUSCH / PUCCH in any serving cell of SCG or MCG, respectively.

[0018] If the UE is configured for NR-DC operation, it is not expected that the UE will be configured with PUCCH-SCell.

[0019] If a PUSCH or PUCCH is repeated, including duplicates, it can be a priority index of 0 or priority index 1. If no priority index is provided for the PUSCH or PUCCH, the priority index is 0. If the UE monitors the PDCCH in an active DL BWP for detecting DCI formats 0_1 and 1_1, or for detecting DCI formats 0_2 and 1_2, the priority index can be provided by the priority indicator field. If the UE indicates the ability to monitor the PDCCH in an active DL BWP for detecting DCI formats 0_1 and 1_1, and for detecting DCI formats 0_2 and 1_2, then DCI format 0_1 ​​or DCI format 0_2 can schedule PUSCH transmissions of any priority, and DCI format 1_1 or DCI format 1_2 can schedule PDSCH reception and trigger PUCCH transmissions with corresponding HARQ-ACK information of any priority. If, after resolving the overlap of PUCCH and / or PUSCH transmissions with the same priority index, the UE determines to transmit a first PUCCH with a higher priority index, a PUSCH with a lower priority index, or a second PUCCH, and the transmission of the first PUCCH will overlap with the transmission of the PUSCH or the second PUCCH in time, the UE does not transmit the PUSCH or the second PUCCH; if the transmission of the PUSCH with a higher priority index, the PUCCH with a lower priority index, and the PUSCH will overlap with the transmission of the PUCCH in time, the UE does not transmit the PUCCH; if the first PUSCH with a higher priority index on the serving cell, the second PUSCH with a lower priority index on the serving cell, and the transmission of the first PUSCH and the second PUSCH will overlap in time, the UE does not transmit the second PUSCH, wherein at least one of the two PUSCHs is not scheduled in DCI format.

[0020] In the remainder of this section, the UE reuses a UCI with the same priority index in the PUCCH or PUSCH. It is assumed that the PUCCH or PUSCH has the same priority index as the UCI reused by the UE in the PUCCH or PUSCH.

[0021] In the remainder of this clause, if the UE is provided with subslotLength-ForPUCCH, the time slots used for the associated PUCCH transmission include the number of symbols indicated by subslotLength-ForPUCCH.

[0022] If the UE will transmit a PUSCH without UL-SCH that overlaps with the PUCCH transmission containing positive SR information on the serving cell, then the UE will not transmit the PUSCH.

[0023] If the UE will transmit CSI reports on overlapping physical channels, the UE will apply the priority rules described in [6, TS 38.214] to the multiplexing of CSI reports.

[0024] If the UE has overlapping resources for PUCCH transmissions in a time slot, and at least one of the PUCCH transmissions is repeated in multiple time slots, the UE first follows the procedure described in Section 9.2.6 to resolve the overlap of PUCCH transmissions in the resources.

[0025] If the UE will multiplex UCI in a PUCCH transmission that overlaps with the PUSCH transmission, and the PUSCH and PUCCH transmissions satisfy the conditions for UCI multiplexing in clause 9.2.5, then the UE, if present, will only multiplex HARQ-ACK information from UCI in the PUSCH transmission, and if the UE multiplexes aperiodic or semi-persistent CSI reports in the PUSCH, it will not transmit the PUCCH; if present, it will only multiplex HARQ-ACK information and CSI reports from UCI in the PUSCH transmission, and if the UE does not multiplex aperiodic or semi-persistent CSI reports in the PUSCH, it will not transmit the PUCCH.

[0026] The UE does not expect to multiplex a UCI in a PUSCH transmission with SCS configuration μ1 in a single time slot, which is of the same type as the PUCCH that the UE will transmit in a PUCCH with SCS configuration μ2 (if μ1 < μ2) in a different time slot.

[0027] If each of more than one PUSCH includes a non-periodic CSI report, the UE does not expect PUCCH resources generated by multiplexing overlapping PUCCH resources (if applicable) to overlap with more than one PUSCH.

[0028] If the UE previously detected the DCI format of the scheduled PUSCH transmission in the time slot and if the UE multiplexed the HARQ-ACK information in the PUSCH transmission, the UE does not expect to detect the scheduled PDSCH reception or SPS PDSCH release and to use the corresponding HARQ-ACK information in the time slot to indicate the DCI format of the resources used for PUCCH transmission.

[0029] If the UE multiplexes the aperiodic CSI in the PUSCH, and the UE multiplexes the UCI including HARQ-ACK information in the PUCCH that overlaps with the PUSCH, and the timing conditions for overlapping PUCCH and PUSCH in clause 9.2.5 are met, then the UE only multiplexes the HARQ-ACK information in the PUSCH and does not transmit the PUCCH.

[0030] If the UE transmits multiple PUSCHs in a time slot on the corresponding serving cell, including a first PUSCH scheduled by the DCI format and a second PUSCH configured by the corresponding ConfiguredGrantConfig or semiPersistentOnPUSCH, and the UE will reuse UCI in one of the multiple PUSCHs, and the multiple PUSCHs satisfy the conditions for UCI reuse in clause 9.2.5, the UE will reuse UCI in the PUSCH from the first PUSCH.

[0031] If the UE transmits multiple PUSCHs in a time slot on the corresponding serving cell and the UE will multiplex the UCI in one of the multiple PUSCHs and the UE will not multiplex the aperiodic CSI in any of the multiple PUSCHs, then the UE will multiplex the UCI in the PUSCH of the serving cell with the smallest ServCellIndex that satisfies the conditions in clause 9.2.5 to satisfy UCI multiplexing. If the UE transmits more than one PUSCH in a time slot on the serving cell with the smallest ServCellIndex that satisfies the conditions in clause 9.2.5 for UCI multiplexing, then the UE will multiplex the UCI in the earliest PUSCH that the UE transmits in the time slot.

[0032] If the UE transmits PUSCH on multiple time slots and will transmit a PUCCH with HARQ-ACK and / or CSI information on a single time slot and in a time slot overlapping with PUSCH transmissions in one or more of the multiple time slots, and the PUSCH transmissions in one or more time slots satisfy the conditions for multiplexing HARQ-ACK and / or CSI information in section 9.2.5, then the UE multiplexes the HARQ-ACK and / or CSI information in the PUSCH transmissions in one or more time slots. If the UE does not transmit a single-slot PUCCH with HARQ-ACK and / or CSI information in a time slot in the event of a missing PUSCH transmission, then the UE does not multiplex the HARQ-ACK and / or CSI information in the PUSCH transmissions from multiple time slots.

[0033] If PUSCH transmissions on multiple time slots are scheduled by a DCI format including a DAI field, the value of the DAI field is applicable to multiplexing HARQ-ACK information in any PUSCH transmission from multiple time slots where the UE multiplexes HARQ-ACK information.

[0034] If the UE will reuse HARQ-ACK information in a PUSCH transmission configured by ConfiguredGrantConfig or in an active PUSCH transmission configured by semiPersistentOnPUSCH, and includes CG-UCI [5, TS 38.212], the UE will reuse HARQ-ACK information in the PUSCH transmission if cg-CG-UCI-Multiplexing is provided; otherwise, the UE will not transmit PUSCH and will reuse HARQ-ACK information in a PUCCH transmission or in another PUSCH transmission.

[0035] For time-domain resources with PUSCH repetitions in time-domain resource allocation from 3GPP TS 38.214 V16.1.0 (2020-03), 6.1.2.1, when the UE is scheduled to transmit a transport block and there is no CSI report, or when the UE is scheduled to transmit a transport block and CSI report on the PUSCH via DCI, the DCI's Time domain resource assignment field value m provides a row index m+1 to the allocation table. The determination of the resource allocation table used is defined in section 6.1.2.1.1. The index row definition will be applied to the slot offset K2, start and length indicator SLIV of the PUSCH transmission, or directly define the start symbol S and allocation length L, PUSCH mapping type and number of repetitions (if the number of repetitions exists in the resource allocation table).

[0036] For PUSCHs scheduled by DCI format 0_1, if PUSCHRepTypeIndicator-ForDCIFormat0_1 is set to 'pusch-RepTypeB', the UE applies the PUSCH repetition type B procedure when determining time-domain resource allocation. For PUSCHs scheduled by DCI format 0_2, if PUSCHRepTypeIndicator-ForDCIFormat0_2 is set to 'pusch-RepTypeB', the UE applies the PUSCH repetition type B procedure when determining time-domain resource allocation. Otherwise, the UE applies the PUSCH repetition type A procedure when determining the time-domain resource allocation for PUSCHs scheduled by PDCCH.

[0037] For PUSCH repetition type A, the number of start symbols S relative to the start of the time slot and the number of consecutive symbols L counted from the symbol S allocated for PUSCH are determined by the start and length indicators SLIV of the index row: if (L-1)≤7, then SLIV=14·(L-1)+S, otherwise SLIV=14·(14-L+1)+(14-1-S), where 0<L≤14-S. For PUSCH repetition type B, the number of start symbols S relative to the start of the time slot and the number of consecutive symbols L counted from the symbol S allocated for PUSCH are provided by the startSymbol of the resource allocation table and the length of the index row, respectively. For PUSCH repetition type A, the PUSCH mapping type is set to type A or type B, as defined in clause 6.4.1.1.3 of [4,TS 38.211] given by the index row. For PUSCH repetition type B, the PUSCH mapping type is set to type B. The UE should consider the S and L combinations defined in Table 6.1.2.1-1 as valid PUSCH assignments.

[0038] Table 6.1.2.1-1: Valid combinations of S and L

[0039]

[0040] For PUSCH repetition type A, when a PUSCH scheduled by DCI format 0_1 ​​or 0_2 is transmitted in the PDCCH using a CRC scrambled with C-RNTI, MCS-C-RNTI or CS-RNTI with NDI=1, the repetition number K is determined as follows: if numberofrepetitions exists in the resource allocation table, then the repetition number K is equal to numberofrepetitions; otherwise, if the UE is configured with a pusch-AggregationFactor, then the repetition number K is equal to pusch-AggregationFactor; otherwise, K=1.

[0041] For PUSCH repetition type A, when K>1, the same symbol allocation is applied across K consecutive time slots, and the PUSCH is limited to a single transport layer. The UE repeats TB across K consecutive time slots in which the same symbol allocation is applied in each time slot. The redundant version applied at the nth transmission time of TB, where n = 0, 1, ..., K-1, is determined according to Table 6.1.2.1-2.

[0042] Table 6.1.2.1-2: Redundant Versions for PUSCH Transmission

[0043]

[0044] For PUSCH repetition type A, according to the conditions in clause 11.1 of [6, TS 38.213], PUSCH transmission in the slots of multi-slot PUSCH transmission is omitted.

[0045] For PUSCH repetition type B, the number of nominal repetitions is given by `numberofrepetitions`. For the nth nominal repetition, n = 0, ..., `numberofrepetitions-1`, the time slot for the start of the nominal repetition is given by... Given, and the start symbol relative to the start of the time slot is... The time slot at which the nominal repetition ends is given; Given, and the end symbol relative to the start of the time slot is... Provided.

[0046] Here K s It is the time slot at the start of the PUSCH transmission, and N s s y lo m t b It is the number of symbols per slot as defined in clause 4.3.2 of [4,TS 38.211].

[0047] For PUSCH repetition type B, the UE determines the invalid symbols used for PUSCH repetition type B transmission as follows:

[0048] Symbols indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered invalid symbols for PUSCH repeat type B transmissions.

[0049] The UE can be configured with a higher-level parameter, InvalidSymbolPattern, which provides a symbol-level bitmap spanning one or two time slots (the higher-level parameter symbol given by InvalidSymbolPattern). A bit value of 1 in the symbol-level bitmap symbols indicates that the corresponding symbol is an invalid symbol transmitted using PUSCH repetition type B. The UE can be additionally configured with a time-domain mode (the higher-level parameter periodicityAndPattern given by InvalidSymbolPattern), where each bit of periodicityAndPattern corresponds to a unit equal to the duration of the symbol-level bitmap symbols, and a bit value of 1 indicates that the symbol-level bitmap symbols are present in the unit. The length of periodicityAndPattern can be {1, 2, 4, 5, 8, 10, 20, or 40} units, but the maximum is 40 ms. The first symbol of periodicityAndPattern every 40 ms / P period is the first symbol in the frame nf mod 4 = 0, where P is the duration of periodicityAndPattern in ms. When periodicityAndPattern is not configured, for a symbol-level bitmap spanning two time slots, the bits of the first and second time slots correspond to the even and odd number of time slots in the radio frame, respectively. For a symbol-level bitmap spanning one time slot, the bits of the time slot correspond to each time slot in the radio frame. If InvalidSymbolPattern is configured, the timing of the UE applying the invalid symbol pattern is determined as follows:

[0050] If the PUSCH is scheduled by DCI format 0_1, or corresponds to an authorization configured by Type 2 activated by DCI format 0_1, and if InvalidSymbolPatternIndicator-ForDCIFormat0_1 is configured, the UE applies the invalid symbol mode if the invalid symbol mode indicator field is set to 1; otherwise, the UE does not apply the invalid symbol mode.

[0051] If the PUSCH is scheduled by DCI format 0_2, or corresponds to a Type 2 configuration authorization activated by DCI format 0_2, and if InvalidSymbolPatternIndicator-ForDCIFormat0_2 is configured, the UE applies the invalid symbol mode if the invalid symbol mode indicator field is set to 1; otherwise, the UE does not apply the invalid symbol mode.

[0052] For PUSCH repetition type B, after determining invalid symbols for each of the K nominal repetitions for PUSCH repetition type B transmission, the remaining symbols are considered as potentially valid symbols for PUSCH repetition type B transmission. If the number of potentially valid symbols for PUSCH repetition type B transmission is greater than zero for a nominal repetition, then the nominal repetition consists of one or more actual repetitions, where each actual repetition consists of a continuous set of potentially valid symbols that can be used for PUSCH repetition type B transmission within a time slot. Actual repetitions with a single symbol are omitted except in the case where L=1. Actual repetitions are omitted according to the conditions in clause 11.1 of [6, TS 38.213]. The redundant version to be applied on the nth actual repetition (where the count includes omitted actual repetitions) is determined according to Table 6.1.2.1-2.

[0053] For the uplink cancellation indication from 3GPP TS 38.213 V16.1.0 (2020-03), the 11.2A cancellation indication, if UplinkCancellation is provided to the UE, then CI-RNTI is provided to the UE via ci-RNTI for monitoring PDCCH candidates for DCI format 2_4 [5, TS 38.212]. UplinkCancellation additionally provides the UE with a set of serving cells via ci-ConfigurationPerServingCell, which includes: a set of serving cell indices and a corresponding set of positions for fields in DCI format 2_4 via positionInDCI; if the serving cell is configured with a SUL carrier, then multiple fields of DCI format 2_4 for each serving cell for the SUL carrier via positionInDCI-forSUL; if the serving cell is configured with SUL, then for the SUL of the serving cell, the information payload size for DCI format 2_4 via dci-PayloadSize-forCI, and an indication of time-frequency resources via timeFrequencyRegion.

[0054] For a serving cell with the association field in DCI format 2_4, for the field represented by the following: N CI The number of bits provided by CI-PayloadSize, B CI The number of PRBs provided by the frequencyRegionforCI in the timeFrequencyRegion, T CIThe number of symbols, excluding those used to receive SS / PBCH blocks, and the DL symbols indicated by tdd-UL-DL-ConfigurationCommon, which are provided by timeDurationforCI in timeFrequencyRegion, G CI T provided by timeGranularityforCI in timeFrequencyRegion CI Number of partitions for the symbol.

[0055] G CI One from N CI The set of bits in a bit has the same properties as G. CI A one-to-one mapping of group symbols, where the first Each in the group includes Symbols, and the remainder Each in the group includes Symbol. The UE determines the symbol duration for the SCS configuration of the active DL BWP, where the UE monitors the PDCCH for DCI format 2_4 detection.

[0056] For a set of symbols, N comes from each bit set BI =B CI / G CI Bit has the same properties as N BI A one-to-one mapping of PRB groups, where the first Each in the group includes One PRB and the remainder Each in the group includes One PRB. This is indicated by the offset RB. start The frequency region for CI and the length L of RIV according to [6, TS 38.214] RB And through the O that indicates the SCS configuration for the active DL BWP carrier In the FrequencyInfoUL-SIB, the offsetToCarrier parameter is used by the UE to monitor the PDCCH for DCI format 2_4 detection. The UE determines the first PRB index as... And determine the number of consecutive RBs as

[0057] The indication of DCI format 2_4 for the serving cell applies to PUSCH or SRS transmissions on the serving cell. For the serving cell, the UE determines T... CI The first symbol in the set is the I symbol indicating the end of PDCCH reception in DCI format 2_4 detected by the UE. proc，2The first symbol following +d, where d is provided by XXX (where “XXX” has not yet been defined in the technical specification). T proc,2 Corresponding to the PUSCH processing capacity 2 [6, TS 38.214], its assumption d 2，1 =0, where μ is the minimum SCS configuration between the PDCCH and PUSCH transmissions or SRS transmissions on the serving cell. The UE does not expect T to occur after the last symbol of the CORESET in DCI format 2_4. proc,2 Cancel PUSCH or SRS transmission before the corresponding symbol.

[0058] If a UE cancels a PUSCH transmission in DCI format 2_4 for the serving cell, or if a PUSCH transmission has duplicates, then a duplicate of the PUSCH transmission [6, TS 38.214] is canceled, or if the following conditions are met respectively: from T CI A group of symbols has a corresponding bit value '1' in DCI format 2_4 and includes symbols for PUSCH transmissions or SRS transmissions (repeated), as well as symbols from B. CI A group of PRBs that have a corresponding bit value '1' in DCI format 2_4 and include PRBs of either PUSCH transmissions or SRS transmissions (repetitions), wherein cancellation of a PUSCH transmission (repetition) includes all symbols from the earliest symbol of the PUSCH transmission (repetition), which are located in one or more groups of symbols with a corresponding bit value '1' in DCI format 2_4; cancellation of an SRS transmission includes only symbols in one or more groups of symbols with a corresponding bit value '1' in DCI format 2_4.

[0059] At least some embodiments are able to provide enhanced UL cancellation indication. According to possible embodiments, PUSCH transmissions can be dynamically scheduled via DCI or semi-statically configured via RRC signaling.

[0060] In one implementation, if the UE receives an uplink cancellation indication for a time and frequency region that fully or partially overlaps with a scheduled PUSCH transmission (e.g., DCI format 2_4 is detected), the UE cancels the scheduled PUSCH transmission regardless of the priority of the scheduled PUSCH.

[0061] In another implementation, if the UE receives an uplink cancellation indication for a time and frequency region that fully or partially overlaps with the scheduled PUSCH transmission (e.g., DCI format 2_4 is detected) and the UE determines that the scheduled PUSCH is indicated as a low-priority channel, then the UE cancels the scheduled PUSCH transmission. If the scheduled PUSCH is indicated as a high-priority channel, then the UE does not cancel the scheduled PUSCH transmission.

[0062] In one embodiment, the UE has a multiplexed UCI (e.g., HARQ-ACK information, CSI) in the scheduled PUSCH, and receives an uplink cancellation indication in a time and frequency region that fully or partially overlaps with the scheduled PUSCH. The UE transmits symbols for at least the scheduled PUSCH, where the channel bits of the UCI are mapped. In one implementation, if the PUSCH includes HARQ-ACK information and / or a high-priority CSI report (e.g., a high-priority CSI report that can be configured for the UE or dynamically indicated to the UE), the UE transmits the entire PUSCH. In another implementation, the UE may transmit symbols for the PUSCH carrying the UCI (e.g., HARQ-ACK information and / or a high-priority CSI report). In an alternative implementation, in addition to symbols for the PUSCH carrying the UCI, the UE may also transmit symbols for PUSCHs that do not overlap with the indicated cancellation time and frequency region.

[0063] In another embodiment, the UE receives an indication from a network entity that indicates potential cancellation of a scheduled PUSCH based on an uplink cancellation indication, or that indicates an uplink cancellation indication without regard to transmissions of the scheduled PUSCH. In one embodiment, the UE may receive the indication as part of configured authorized PUSCH configuration information. In another embodiment, the UE may receive the indication in the DCI of the scheduled PUSCH. In an alternative implementation, the UE receives the indication in a group common DCI of the cancellation indication (e.g., an enhanced version of DCI format 2_4), where bit fields in the group common DCI indicate selection from options, such as bit field '00': any PUSCH or SRS overlapping with the indicated cancellation region (i.e., time and frequency resources) is cancelled; '01': any PUSCH or SRS overlapping with the indicated cancellation region and not indicated as a high-priority PUSCH or SRS is cancelled; '10': any PUSCH or SRS overlapping with the indicated cancellation region and not carrying a UCI is cancelled; and '11': reserved. An example implementation of the enhanced UL cancellation indicator DCI format 2_4x could be:

[0064] 7.3.1.3.5.x format 2_4x

[0065] DCI format 2_4x is used to notify the UE of the PRB and OFDM symbols in which the UE can cancel the corresponding UL transmission from the UE, as well as to notify the UL of the applicability information for the cancellation instruction.

[0066] The following information is transmitted using DCI format 2_4 with CRC scrambled by CI-RNTI:

[0067] Cancel Instruction 1, Applicability Instruction 1, Cancel Instruction 2, Applicability Instruction 2, ..., Cancel Instruction N, Applicability Instruction N.

[0068] According to section 11.2A of TS 38.213, the size of DCI format 2_4x can be configured up to 126 bits by the higher-layer parameter dci-PayloadSize-forCI. The number of bits for each cancellation indication can be configured by the higher-layer parameter CI-PayloadSize, and the number of bits for the applicability indication (including zero bits) can be configured by the higher-layer parameter AI-PayloadSize. For the UE, there is at most one cancellation indication with a UL carrier.

[0069] At least some embodiments are able to provide UCI multiplexing in PUSCH repetition. If one or more PUCCHs and one or more PUSCHs overlap in time, the UE can determine whether the timeline conditions for multiplexing one or more types of UCIs (e.g., HARQ-ACK information, CSI) and / or UL-SCH in an uplink channel (i.e., PUCCH or PUSCH) are met.

[0070] In one implementation, the timing condition used for determination is according to subsection 9.2.5 of TS 38.213V16.1.0. That is, the first symbol S0 of the earliest PUCCH or PUSCH in a set of overlapping PUCCHs and PUSCHs corresponds to the first symbol of the first transmission timing (for repetition type A) / actual repetition (for repetition type B) of the earliest PUCCH or PUSCH. The UE does not expect to respond to DCI format detection to any PUCCH or PUSCH that overlaps with any other PUCCH or PUSCH that does not meet the timing condition.

[0071] In another implementation, the timing condition used for determination is based on enhanced multiplexing timing conditions. Specifically, the first symbol S0 of the earliest PUCCH or PUSCH in the group of overlapping PUCCH and PUSCH transmission opportunities / actual repetitions corresponds to the first symbol of the earliest PUCCH or PUSCH transmission opportunity (for repetition type A) / actual repetition (for repetition type B) in the group of overlapping PUCCH transmission opportunities / actual repetitions and PUSCH transmission opportunities / actual repetitions. The UE does not expect to respond to DCI format detection to any PUCCH or PUSCH transmission opportunity (type A) / actual repetition (type B) that overlaps with any other PUCCH or PUSCH transmission opportunity (type A) / actual repetition (type B) that does not meet the enhanced timing conditions.

[0072] An example implementation of enhanced reuse timeline conditions could be:

[0073] If the UE transmits multiple overlapping PUCCHs or overlapping PUCCH and PUSCH transmission timings (repetition type A) / actual repetitions (repetition type B) in a time slot, and when applicable as described in Clauses 9.2.5.1 and 9.2.5.2, the UE is configured to multiplex different UCI types in a PUCCH, and at least one of the multiple overlapping PUCCHs or PUSCHs is in response to the UE's DCI format detection, then the UE multiplexes all corresponding UCI types if the following condition is met: If one of the PUCCH or PUSCH transmissions is in response to the UE's DCI format detection, the UE expects the first symbol S0 of the earliest PUCCH or PUSCH transmission timing (repetition type A) / actual repetition (repetition type B) among a set of overlapping PUCCH and PUSCH transmission timings (repetition type A) / actual repetitions (repetition type B) in the time slot to satisfy the following timeline condition.

[0074] -S0 is not following the last symbol of any corresponding PDSCH. Before the CP symbol that begins afterward, Depend on The maximum value is given, where for the i-th PDSCH with corresponding HARQ-ACK transmission on the PUCCH in the group of overlapping PUCCH and PUSCH transmission timing (repetition type A) / actual repetition (repetition type B), d 1,1N1 is selected for the i-th PDSCH following [6, TS 38.214], and is selected based on the UE PDSCH processing capability of the i-th PDSCH and SCS configuration μ, where μ corresponds to the smallest SCS configuration among all PUSCHs in the group of PDCCH (if any) used to schedule the i-th PDSCH, the i-th PDSCH, the PUCCH with corresponding HARQ-ACK transmission for the i-th PDSCH, and overlapping PUCCH and PUSCH transmission timing (repetition type A) / actual repetition (repetition type B).

[0075] -S0 does not follow the last symbol of DCI format 1_1 that has any corresponding SPS PDSCH release or indicates SCell hibernation. The symbol before the CP that begins thereafter, as described in section 10.3. Depend on The maximum value is given, where the i-th PDCCH provides the corresponding HARQ-ACK transmission for SPS PDSCH release or DCI format 1_1 on the PUCCH in the group of overlapping PUCCH and PUSCH transmission timing (repetition type A) / actual repetition (repetition type B). N is described in Section 10.2 and is selected based on the UE PDSCH processing capability of the i-th SPS PDSCH release or DCI format 1_1 and SCS configuration μ, where μ corresponds to the smallest SCS configuration among all PUSCHs in the group of PDCCH used to provide the i-th SPS PDSCH release, PUCCH with corresponding HARQ-ACK transmission for the i-th SPS PDSCH release or DCI format 1_1, and overlapping PUCCH and PUSCH transmission timing (repetition type A) / actual repetition (repetition type B).

[0076] - If there is no multiplexed aperiodic CSI report in the PUSCH transmission timing (repetition type A) / actual repetition (repetition type B) group of overlapping PUCCH and PUSCH transmission timing (repetition type A) / actual repetition (repetition type B), then S0 is not having a multiplexed aperiodic CSI report after the last symbol below. Before the CP symbol that begins after:

[0077] - Any PDCCH with DCI format scheduling overlap of PUSCH transmission timing (repetition type A) / actual repetition (repetition type B), and

[0078] - Schedule any PDCCH released from the overlapping PDCCH in the time slot that has corresponding HARQ-ACK information in the PDCCH.

[0079] If at least one PUSCH exists in the group of overlapping PUCCH and PUSCH, then Depend on The maximum value is given, where for the i-th PUSCH in a group of overlapping PUCCH and PUSCH, d 2,1 and d 2,2 The UE PUSCH processing capability of N2 is selected based on the i-th PUSCH and SCS configuration μ, which is used to schedule the i-th PUSCH (if any), the PDCCH that has a corresponding HARQ-ACK transmission on the PUCCH scheduled in the overlapping PUCCH / PUSCH group, and the smallest SCS configuration among all PUSCHs in the overlapping PUCCH and PUSCH group.

[0080] If there is no PUSCH in the group of overlapping PUCCH and PUSCH, then Depend on The maximum value is given, where for the i-th PDSCH with corresponding HARQ-ACK transmission on a PUCCH in an overlapping PUCCH group, N2 is selected based on the UE PUSCH processing capability of the PUCCH serving cell (if configured). If no PUSCH processing capability is configured for the PUCCH serving cell, N2 is selected based on the UE PUSCH processing capability of 1. μ is selected based on the minimum SCS configuration between the SCS configuration of the PDCCH (if any) used to schedule the i-th PDSCH with corresponding HARQ-ACK transmission on the PUCCH in the overlapping PUCCH group and the SCS configuration used for the PUCCH serving cell.

[0081] - If a multiplexed aperiodic CSI report exists in the PUSCH transmission timing (repetition type A) / actual repetition (repetition type B) group of overlapping PUCCH and PUSCH transmission timing (repetition type A) / actual repetition (repetition type B), then S0 does not have a multiplexed aperiodic CSI report after the last symbol below. Before the CP symbol that begins after:

[0082] - Any PDCCH with DCI format scheduling overlap of PUSCH transmission timing (repetition type A) / actual repetition (repetition type B), and

[0083] -Schedule the release of the PDSCH or SPS PDSCH, or provide any PDCCH in DCI format 1_1 with corresponding HARQ-ACK information in the overlapping PUCCH in the time slot to indicate SCell sleep.

[0084] Where μ corresponds to the minimum SCS configuration of the PDCCH, the minimum SCS configuration of the overlapping PUSCH group, and the minimum SCS configuration of the CSI-RS associated with the DCI format of the PUSCH transmission timing (repetition type A) / actual repetition (repetition type B) of the multiplexed aperiodic CSI report, and for μ=0,1, d=2, for μ=2, d=3, and for μ=3, d=4

[0085] -N1, N2, d 1，1 d 2，1 d 2，2 , and Z are defined in [6,TS 38.214], and κ and T C It is defined in [4,TS 38.211].

[0086] If the UE transmits multiple overlapping PUCCHs in a time slot or overlapping PUCCH and PUSCH transmission timing (repetition type A) / actual repetition (repetition type B) in a time slot, one of the PUCCHs includes HARQ-ACK information in response to SPS PDSCH reception, and none of the PUSCHs responds to DCI format detection, then the UE expects the first symbol S0 of the earliest PUCCH or PUSCH transmission timing (repetition type A) / actual repetition (repetition type B) to satisfy the first of the previous timeline conditions, except where the component associated with the SCS configuration of the PDCCH used to schedule the PDSCH or PUSCH is missing in the timeline conditions.

[0087] The UE does not expect to respond to DCI format detection to any PUCCH or PUSCH transmission timing (Type A) / actual repetition (Type B) that does not meet the timing conditions above.

[0088] In one embodiment, if the UE determines whether at least one applicable timeline condition for multiplexing at least one type of UCI (e.g., HARQ-ACK information, CSI, CG-UCI) in a PUSCH is met, then the UE multiplexes at least one type of UCI in at least one PUSCH transmission timing (for repetition type A) / actual repetition (for repetition type B), wherein each of the at least one PUSCH transmission timing / actual repetition has an available number of REs greater than the number of REs required for UCI multiplexing. That is, the UE does not multiplex UCI on PUSCH transmission timings / actual repetitions with fewer REs than the number of REs required for UCI multiplexing.

[0089] In another embodiment, if the UE determines whether all applicable at least one timeline conditions for multiplexing at least one type of UCI (e.g., HARQ-ACK information, CSI, CG-UCI) in the PUSCH are met, the UE multiplexes at least one type of UCI from at least one PUSCH transmission timing (for repetition type A) / actual repetition (for repetition type B), wherein each of the at least one PUSCH transmission timing / actual repetition has a number of symbols not less than a threshold, wherein the threshold is determined based on the number of symbols in the nominal repetition. In one embodiment, the threshold is configured or predefined for a given number of symbols in the nominal repetition. In another embodiment, the ratio of the threshold to the number of symbols in the nominal repetition is configured or predefined.

[0090] Figure 2 This is an example flowchart 200 illustrating the operation of a wireless communication device such as UE 110 according to a possible embodiment. At 210, scheduling information for at least one PUCCH and at least one PUSCH can be received. The scheduling information can schedule the UE to transmit at least one PUCCH and at least one PUSCH. At least one PUCCH can overlap with at least one PUSCH in time. At least one PUCCH can include at least one type of UCI.

[0091] At 220, at least one type of UCI can be multiplexed in at least one actual repetition of a PUSCH. The at least one actual repetition of a PUSCH can have a number of symbols not less than a predefined number of symbols. The predefined number of symbols can be a value of one or greater than one. At 230, a PUSCH including the multiplexed at least one type of UCI can be transmitted. The PUSCH can overlap with a PUCCH in at least one PUCCH.

[0092] According to possible embodiments, the transmitted PUSCH can include at least one actual repeat of the PUSCH. For example, at least one actual repeat of the PUSCH can be multiplexed with UCI, and the transmitted PUSCH can include additional actual repeats of the PUSCH that are not multiplexed with UCI. According to possible implementations, at least one actual repeat of the PUSCH can include a first actual repeat, and a second actual repeat of the PUSCH can be transmitted without multiplexing at least one type of UCI in the second actual repeat.

[0093] According to possible embodiments, at least one PUCCH can include multiple overlapping PUCCHs, such as mutually overlapping PUCCHs. A PUCCH for multiplexing the UCIs of multiple overlapping PUCCHs can be determined. The UCIs of multiple overlapping PUCCHs can include at least one type of UCI. For example, when the UE is to transmit multiple overlapping PUCCHs, the UE can determine the PUCCH to be transmitted, wherein the UCIs of the multiple overlapping PUCCHs can be multiplexed in the PUCCH. If the PUCCHs overlap, the UE can first determine the PUCCH for multiplexing the UCIs of the multiple overlapping PUCCHs, and then if the determined PUCCH overlaps with a PUSCH, the UE can multiplex at least a portion of the UCIs of the PUCCH into the PUSCH. If each of more than one PUSCH includes aperiodic CSI reports, the UE does not expect PUCCH resources generated by multiplexing overlapping PUCCH resources (if applicable, overlapping with more than one PUSCH).

[0094] According to possible embodiments, it is possible to determine which of the at least one PUSCHs to be transmitted by multiplexing at least one type of UCI. It is possible to determine which at least one of the determined PUSCHs is actually repeated for UCI multiplexing. Transmitting a PUSCH can include transmitting the determined PUSCH including the at least one determined actual repetition. Scheduling information does not necessarily need to be received in a single scheduling information reception instance. For example, scheduling information for PUCCHs and PUSCHs can be received in different DCIs, different higher-level communications, or otherwise. Scheduling information for different PUCCHs or different PUSCHs can also be received in different DCIs, different higher-level communications, etc. At least one PUCCH can at least partially or completely overlap with at least one PUSCH in time.

[0095] According to possible embodiments, a PUSCH can be the earliest of at least one PUSCH. For example, if the UE transmits multiple PUSCHs in a time slot on the corresponding serving cell, and the UE will multiplex UCI in one of the multiple PUSCHs, and the UE does not multiplex aperiodic CSI in any of the multiple PUSCHs, then the UE can multiplex UCI in the PUSCH of the serving cell with the smallest ServCellIndex that satisfies the conditions in clause 9.2.5 for UCI multiplexing. If the UE transmits more than one PUSCH in a time slot on the serving cell with the smallest ServCellIndex that satisfies the conditions in clause 9.2.5 for UCI multiplexing, then the UE can multiplex UCI in the earliest PUSCH transmitted by the UE in the time slot.

[0096] According to possible embodiments, at least one actual repetition of PUSCH can include the earliest actual PUSCH repetition that overlaps with PUCCH.

[0097] According to possible embodiments, the number of resource elements required to transmit at least one type of UCI can be determined based on the number of nominal repeats of the PUSCH. If a nominal repeat crosses a slot boundary or an unavailable symbol, then the nominal repeat can include multiple actual repeats. For example, an actual repeat differs from a nominal repeat in that if a nominal repeat crosses or includes a slot boundary or an unavailable symbol, it can be broken down into multiple actual repeats.

[0098] According to possible embodiments, the number of resource elements required to transmit at least one type of UCI can be determined based on the actual number of symbols repeated in the PUSCH. The UE does not expect to multiplex UCI on PUSCH transmission timings / actual repetitions with fewer REs than the number of REs required for UCI multiplexing.

[0099] According to possible embodiments, it is possible to determine whether one or more timing conditions required for multiplexing at least one type of UCI in at least one actual repetition of a PUSCH of at least one PUSCH are met. Multiplexing can include multiplexing at least one type of UCI in at least one actual repetition of a PUSCH in response to determining that one or more timing conditions are met. According to possible implementations, one or more timing conditions can be based on the position of the earliest PUSCH or the earliest symbol of the at least one PUSCH and at least one PUCCH. For example, the earliest symbol can be the first symbol S0 described above. The timing condition can be the position of the earliest symbol, such as S0, rather than preceding a specific symbol.

[0100] Figure 3This is an example flowchart 300 illustrating the operation of a wireless communication device such as network entity 120 according to a possible embodiment. At 310, transmission scheduling information for at least one PUCCH and at least one PUSCH can be transmitted. The scheduling information can schedule the UE to transmit at least one PUCCH and at least one PUSCH. At least one PUCCH can overlap with at least one PUSCH in time. At least one PUCCH can include at least one type of UCI.

[0101] At 320, a PUSCH including at least one type of UCI can be received. At least one type of UCI can be multiplexed in at least one actual repetition of the PUSCH of at least one PUSCH. A PUSCH can overlap with a PUCCH of at least one PUCCH. At least one actual repetition of the PUSCH can have a number of symbols not less than the predefined number of symbols. Other interactive operations of flowchart 200 can also be performed.

[0102] It should be understood that, although the specific steps shown in the figures are specific, various additional or different steps can be performed according to the embodiments, and one or more specific steps can be rearranged, repeated, or completely eliminated according to the embodiments. Furthermore, some of the performed steps can be repeated simultaneously with other steps being performed on an ongoing or continuous basis. In addition, different steps can be performed by different elements or in a single element of the disclosed embodiments. Additionally, network entities such as base stations, transmitting and receiving points, mobility management entities, or other network entities can perform interactions between the UE and the network entity. For example, the network entity can transmit signals received by the UE and can receive signals transmitted by the UE. The network entity can also process and manipulate the transmitted and received signals.

[0103] Figure 4 This is an example block diagram of an apparatus 400 according to possible embodiments such as UE 110, network entity 120, or any other wireless communication device disclosed herein. Apparatus 400 may include a housing 410, a controller 420 coupled to the housing 410, audio input and output circuitry 430 coupled to the controller 420, a display 440 coupled to the controller 420, a memory 450 coupled to the controller 420, a user interface 460 coupled to the controller 420, a transceiver 470 coupled to the controller 420, at least one antenna port 475, such as at least one antenna coupled to the transceiver 470, and a network interface 480 coupled to the controller 420. Apparatus 400 may not necessarily include all the elements shown for the different embodiments of this disclosure. Apparatus 400 is capable of performing the methods described in all embodiments.

[0104] Display 440 can be a viewfinder, LCD, LED display, OLED display, plasma display, projection display, touchscreen, or any other device that displays information. Transceiver 470 can be one or more transceivers that include a transmitter and / or receiver. Audio input and output circuitry 430 can include a microphone, speaker, transmitter, or any other audio input and output circuitry. User interface 460 can include a keypad, keyboard, buttons, touchpad, joystick, touchscreen display, another additional display, or any other device that provides an interface between the user and the electronic device. Network interface 480 can be a USB port, Ethernet port, infrared transmitter / receiver, IEEE 1394 port, wireless transceiver, WLAN transceiver, or any other interface that can connect the device to a network, device, and / or computer and can send and receive data communication signals. Memory 450 can include RAM, ROM, EPROM, optical memory, solid-state memory, flash memory, removable memory, hard disk drive, cache, or any other memory that can be coupled to the device.

[0105] Device 400 or controller 420 can implement any operating system, such as Microsoft. Android TM Or any other operating system. The device operating software can be written, for example, in any programming language such as C, C++, Java, or Visual Basic. The device software can also, for example, be written in, such as... frame,. The software and / or operating system can be stored in memory 450, other locations on device 400, cloud storage, and / or any other location capable of storing the software and / or operating system. For example, the code for operation can be implemented as firmware programmed into ROM. Device 400 or controller 420 can also implement the disclosed operations using hardware. For example, controller 420 can be any programmable processor. Furthermore, controller 420 can perform some or all of the disclosed operations. For example, at least some operations can be performed using cloud computing, and controller 420 can perform other operations. At least some operations can also be executed by computer-executable instructions that are executed by at least one computer processor. The disclosed embodiments can also be implemented on general-purpose or special-purpose computers, programmable microprocessors or microprocessors, peripheral integrated circuit elements, application-specific integrated circuits or other integrated circuits, hardware / electronic logic circuits such as discrete component circuits, programmable logic devices such as programmable logic arrays, field-programmable gate arrays, etc. Generally, controller 420 can be any controller or processor device or device capable of operating the device and implementing the disclosed embodiments. Some or all of the additional elements of device 400 may also perform some or all of the operations of the disclosed embodiments.

[0106] In operation, device 400 is capable of performing the methods and operations of the disclosed embodiments. Transceiver 470 is capable of transmitting and receiving signals including data signals and control signals, wherein the control signals can include corresponding data and control information. Controller 420 is capable of generating and processing the transmitted and received signals and information.

[0107] According to possible embodiments, transceiver 470 is capable of receiving scheduling information for at least one PUCCH and at least one PUSCH. The scheduling information is capable of scheduling the UE to transmit at least one PUCCH and at least one PUSCH. At least one PUCCH can overlap in time with at least one PUSCH. At least one PUCCH can include at least one type of UCI. Controller 420 is capable of multiplexing at least one type of UCI in at least one actual repetition of the PUSCH of at least one PUSCH. The PUSCH can overlap with the PUCCH of at least one PUCCH. At least one actual repetition of the PUSCH can have a number of symbols not less than a predefined number of symbols. Transceiver 470 is capable of transmitting the PUSCH including the multiplexed at least one type of UCI.

[0108] According to possible implementations, the transmitted PUSCH can include at least one actual repeat of the PUSCH. The at least one actual repeat of the PUSCH can include a first actual repeat. Transceiver 470 can transmit a second actual repeat of the PUSCH without multiplexing at least one type of UCI in the second actual repeat.

[0109] According to possible implementations, at least one PUCCH can include multiple overlapping PUCCHs. Controller 420 can determine the PUCCHs used for multiplexing the multiple overlapping PUCCHs using a UCI. The UCI of the multiple overlapping PUCCHs can include at least one type of UCI.

[0110] According to possible implementations, controller 420 is capable of determining which of the at least one PUSCHs to transmit by multiplexing at least one type of UCI. Controller 420 is capable of determining which at least one actual repeat of the determined PUSCH is used for UCI multiplexing. Transceiver 470 is capable of transmitting the determined PUSCH including the at least one actual repeat.

[0111] According to possible implementations, a PUSCH can be the earliest of at least one PUSCH. According to possible implementations, at least one actual repetition of a PUSCH can include the earliest actual PUSCH repetition that overlaps with a PUCCH.

[0112] According to a possible implementation, controller 420 can determine the number of resource elements required for transmission of at least one type of UCI based on the nominal number of repeating symbols of the PUSCH. According to a possible implementation, controller 420 can determine the number of resource elements required for transmission of at least one type of UCI based on the actual number of repeating symbols of the PUSCH.

[0113] According to a possible embodiment of the enhanced UL cancellation indication, if the UE has multiplexed the UCI (e.g., HARQ-ACK information, CSI) in the scheduled PUSCH and has received an uplink cancellation indication for a time and frequency region that fully or partially overlaps with the scheduled PUSCH, the UE transmits at least the symbols of the scheduled PUSCH in which the channel bits of the UCI are mapped.

[0114] The UE can also receive indications from network entities that indicate potential cancellation of a scheduled PUSCH based on an uplink cancellation indication, or that indicate an uplink cancellation indication that does not take into account the transmission of the PUSCH used for scheduling, such as an applicability indication in a group common DCI for cancellation indications.

[0115] According to a possible embodiment of the enhanced UCI multiplexing timing condition, the first symbol S0 of the earliest PUCCH or PUSCH in a set of overlapping PUCCH and PUSCH corresponds to the first symbol of the earliest PUCCH or PUSCH transmission timing (for repetition type A) / actual repetition (for repetition type B) in a set of overlapping PUCCH transmission timing / actual repetition and PUSCH transmission timing / actual repetition.

[0116] According to a possible embodiment of the PUSCH transmission timing / actual repetition for UCI multiplexing, the UE multiplexes at least one type of UCI in at least one PUSCH transmission timing (for repetition type A) / actual repetition (for repetition type B), wherein each transmission timing / actual repetition of at least one PUSCH transmission timing / actual repetition has an available number of REs greater than the number of REs required for UCI multiplexing.

[0117] Compared to configuring finer time and frequency granularity for cancellation indications, including an applicability indication in the enhanced UL cancellation indication DCI format allows UL cancellations to be selectively applied without significantly increasing the DCI size. Additionally, in UCI multiplexing within PUSCH repetition type B, the UE can avoid error conditions by multiplexing the UCI during PUSCH transmission timing / actual repetitions with a number of available REs greater than the number required for the UCI.

[0118] According to possible embodiments, the method in the UE can include receiving scheduling information for a physical channel, wherein the UE is scheduled to transmit the physical channel. The method can include multiplexing control information in the physical channel. The method can include receiving a cancellation indication of time and frequency resources indicating potential cancellation for transmission, wherein the physical channel at least partially overlaps with time and frequency resources. The method can include transmitting at least a subset of symbols of the physical channel, wherein the subset of symbols includes control information multiplexed in the physical channel.

[0119] According to a possible implementation of the above embodiments, the physical channel is a physical uplink shared channel, and the control information is uplink control information.

[0120] According to a possible implementation of the above embodiments, the control information includes HARQ-ACK information.

[0121] According to a possible implementation of the above embodiments, the control information includes high-priority control information. According to a possible example of this implementation, the method can include receiving an indication that the control information includes high-priority control information.

[0122] According to a possible implementation of the above embodiments, the physical channel is designated as a high-priority physical channel, and the subset of symbols transmitting at least the physical channel includes all symbols transmitting the physical channel.

[0123] According to a possible implementation of the above embodiments, a subset of symbols transmitting at least the physical channel can include symbols that transmit only the physical channel, including control information.

[0124] According to a possible implementation of the above embodiments, the method may include receiving an applicability indication of whether to follow a cancellation indication in order to determine whether to perform transmission on the physical channel.

[0125] According to a possible example of the above implementation, the physical channel is a configured authorized PUSCH, and an applicability indication is included in the configured authorized PUSCH configuration.

[0126] According to a possible example of the above implementation, the scheduling information of the physical channel is dynamically received in the downlink control information, and the applicability indication is included in the downlink control information.

[0127] According to a possible example of the above implementation, the cancellation instruction and the applicability instruction are received in the group public PDCCH.

[0128] According to possible examples of the above implementation, the applicability indication includes a choice from at least two of the following: canceling any PUSCH or SRS that overlaps with the indicated time and frequency resources; canceling any PUSCH or SRS that overlaps with the indicated time and frequency resources and is not indicated as a high-priority PUSCH or SRS; and canceling any PUSCH or SRS that overlaps with the indicated time and frequency resources and does not carry control information.

[0129] According to possible embodiments, the method at the UE can include receiving scheduling information for at least one PUCCH and at least one PUSCH, wherein the UE is scheduled to transmit at least one PUCCH and at least one PUSCH, wherein the at least one PUCCH at least partially overlaps with the at least one PUSCH in time, and wherein the at least one PUCCH includes at least one type of UCI. The method can include determining whether one or more timing conditions required to multiplex at least one type of UCI in at least one actual repetition of the first actual repetition of the first actual repetition of the first PUSCH are satisfied. The method can include multiplexing at least one type of UCI in the first actual repetition of the first actual repetition of the first PUSCH in response to determining that one or more timing conditions are satisfied. The method can include transmitting the first PUSCH. The at least one actual repetition of the first PUSCH overlaps with the first PUCCH of the at least one PUCCH, and includes the earliest actual repetition among the at least one PUSCH that overlaps with the first PUCCH, wherein the first PUCCH is the earliest PUCCH among the at least one PUCCH. The first actual repetition has a number of available resource elements equal to the number of resource elements required for the transmission of at least one type of UCI.

[0130] According to a possible implementation of the above embodiments, the method can include determining the number of resource elements required for transmission of at least one type of UCI based on the nominal number of repeated symbols for the first PUSCH.

[0131] According to a possible implementation of the above embodiments, the method can include determining the number of resource elements required for transmission of at least one type of UCI based on the actual number of repeated symbols in the first PUSCH.

[0132] According to a possible implementation of the above embodiments, the method can include, in response to determining that one or more timing conditions are met, transmitting a second actual repeat of at least one actual repeat of a first PUSCH without reusing at least one type of UCI, wherein the second actual repeat has a number of available resource elements less than the number of resource elements required for the transmission of at least one type of UCI.

[0133] At least some of the methods disclosed herein can be implemented on a programmable processor. However, the controller, flowchart, and module can also be implemented on a general-purpose or special-purpose computer, a programmable microprocessor or microcontroller and peripheral integrated circuit elements, integrated circuits, hardware electronics or logic circuits such as discrete component circuits, programmable logic devices, etc. Generally, any device residing thereon capable of implementing a finite state machine of the flowcharts shown in the figures can be used to implement the processor functions of this disclosure.

[0134] At least some embodiments improve the operation of the disclosed device. Furthermore, while this disclosure has been described using specific embodiments therein, many alternatives, modifications, and variations will be apparent to those skilled in the art. For example, various components of the embodiments may be interchanged, added, or substituted in other embodiments. Additionally, not all elements in each drawing are essential for the operation of the disclosed embodiments. For example, those skilled in the art will be able to make and use the teachings of this disclosure by simply adopting the elements of the independent claims. Therefore, the embodiments of this disclosure as set forth herein are intended to be illustrative and not restrictive. Various changes may be made without departing from the spirit and scope of this disclosure.

[0135] In this document, relational terms such as “first” and “second” may be used only to distinguish one entity or action from another, without necessarily requiring or implying any actual such relationship or order between such entities or actions. Phrases following a list such as “at least one,” “at least one selected from the group below,” or “at least one selected from the group below” are defined as indicating one, some, or all, but not necessarily all elements in the list. The terms “containing,” “including,” “comprising,” or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but may also include other elements not expressly listed or inherent to such a process, method, article, or apparatus. Without further constraints, an element beginning with “a,” “an,” etc., does not exclude the presence of the same element appended to the process, method, article, or apparatus that includes that element. Additionally, the term “another” is defined as at least a second or more. As used herein, the terms “comprising,” “having,” etc., are defined as “including.” Furthermore, the background section is not recognized as prior art, but is written as the inventor's own understanding of the context of some embodiments at the time of application, and includes the inventor's own understanding of any problems with the prior art and / or problems experienced in the inventor's own work.

[0136] List of abbreviations

[0137] ACK confirmation

[0138] A-CSI (Aperiodic CSI)

[0139] BWP bandwidth portion

[0140] CCCH SDU Common Control Channel Service Data Unit

[0141] CCE Control Channel Element

[0142] CG-UCI configuration of large uplink control information

[0143] CI-RNTI Cancel Indication of Temporary Radio Network Identifier

[0144] CRC Cyclic Redundancy Check

[0145] C-RNTI Community RNTI

[0146] CSI Channel State Information

[0147] CSI-IM Channel State Information Interference Measurement

[0148] CSS Public Search Space

[0149] DAI Downlink Specified Index

[0150] DCI Downlink Control Information

[0151] DL downlink

[0152] FR1 Frequency range 1

[0153] FR2 frequency range 2

[0154] HARQ-ACK (Hybrid Automatic Repeat Request Acknowledgment)

[0155] MAC Media Access Control

[0156] MCG Main Cell Group

[0157] MCS modulation and coding scheme

[0158] MsgA Message A

[0159] MsgB Message B

[0160] MPO MsgA PUSCH timing

[0161] NR New Radio

[0162] NR-DC New Radio - Dual Connectivity

[0163] NUL Non-Supplementary Uplink

[0164] PCell main cell

[0165] PDCCH (Physical Downlink Control Channel)

[0166] PDSCH (Physical Downlink Shared Channel)

[0167] PDU Protocol Data Unit

[0168] PRACH (Physical Random Access Channel)

[0169] PUCCH (Physical Uplink Control Channel)

[0170] PUSCH Physical Uplink Shared Channel

[0171] FDD (Frequency Division Duplex)

[0172] RE Resource Elements

[0173] RNTI (Radio Network Temporary Identifier)

[0174] RRM Radio Resource Management

[0175] RSRP reference signal received power

[0176] SCell Auxiliary Community

[0177] SCG Auxiliary Community Group

[0178] SpCell (Special Cell) (i.e., PCell for MCG or SCG)

[0179] SS / PBCH Synchronization Signal / Physical Broadcast Channel

[0180] SR scheduling request

[0181] SP-CSI Semi-Continuous CSI

[0182] SRS Detection Reference Signal

[0183] SRI SRS Resource Indicators

[0184] SUL supplements uplink

[0185] TB transfer block

[0186] TDD (Time Division Duplex)

[0187] TCI Transport Configuration Indicator

[0188] TC-RNTI Temporary Cell RNTI

[0189] UCI uplink control information

[0190] UE User Equipment

[0191] UL uplink

[0192] URLLC Ultra-Reliable Low-Latency Communication

[0193] USS UE Specific Search Space

Claims

1. A user equipment (UE), comprising: A transceiver that receives scheduling information from at least one physical uplink control channel and at least one physical uplink shared channel. The scheduling information schedules the UE to transmit the at least one physical uplink control channel and the at least one physical uplink shared channel. Wherein, the at least one physical uplink control channel and the at least one physical uplink shared channel overlap in time, and Wherein, the at least one physical uplink control channel includes at least one type of uplink control information; and A controller, coupled to the transceiver, wherein the controller multiplexes the at least one type of uplink control information in at least one actual repetition of the at least one physical uplink shared channel. The transceiver transmits the physical uplink shared channel, which includes uplink control information of at least one multiplexed type. Wherein, the physical uplink shared channel overlaps with the physical uplink control channel of the at least one physical uplink control channel, and Wherein, the at least one actual repetition of the physical uplink shared channel has a number of symbols not less than a predefined number of symbols. The at least one physical uplink control channel includes multiple overlapping physical uplink control channels. The controller determines the physical uplink control channels used to multiplex uplink control information of the plurality of overlapping physical uplink control channels, and The uplink control information of the multiple overlapping physical uplink control channels includes at least one type of uplink control information.

2. The UE according to claim 1, wherein, The transmitted physical uplink shared channel includes at least one actual repeat of the physical uplink shared channel.

3. The UE according to claim 2, in, The at least one actual repetition of the physical uplink shared channel includes a first actual repetition, and The transceiver transmits a second actual repetition of the physical uplink shared channel without multiplexing the at least one type of uplink control information in the second actual repetition.

4. The UE according to claim 1, The controller mentioned above: By multiplexing the at least one type of uplink control information, it is determined which physical uplink shared channel among the at least one physical uplink shared channels should be transmitted, and Determine which at least one of the identified physical uplink shared channels is actually reused for uplink control information multiplexing, and The transceiver transmissions include at least one determined physical uplink shared channel that is actually repeated.

5. The UE according to claim 1, wherein, The physical uplink shared channel is the earliest physical uplink shared channel among the at least one physical uplink shared channels.

6. The UE according to claim 1, wherein, The at least one actual repetition of the physical uplink shared channel includes the earliest actual physical uplink shared channel repetition that overlaps with the physical uplink control channel.

7. The UE according to claim 1, wherein, The controller determines the number of resource elements required for the transmission of the at least one type of uplink control information based on the nominal number of repeated symbols used for the physical uplink shared channel.

8. The UE according to claim 1, in, The controller determines whether one or more timing conditions required for multiplexing the at least one type of uplink control information in at least one actual repetition of the at least one physical uplink shared channel are met, and In response to determining that one or more timing conditions are met, the controller reuses the at least one type of uplink control information in the at least one actual repetition of the physical uplink shared channel.

9. A method in a user equipment (UE), the method comprising: Receive scheduling information from at least one physical uplink control channel and at least one physical uplink shared channel. The scheduling information schedules the UE to transmit the at least one physical uplink control channel and the at least one physical uplink shared channel. Wherein, the at least one physical uplink control channel and the at least one physical uplink shared channel overlap in time, and The at least one physical uplink control channel includes at least one type of uplink control information; The at least one type of uplink control information is multiplexed in at least one actual repetition of the physical uplink shared channel in the at least one physical uplink shared channel; and The physical uplink shared channel transmits uplink control information of at least one multiplexed type. Wherein, the physical uplink shared channel overlaps with the physical uplink control channel in the at least one physical uplink control channel, and Wherein, the at least one actual repetition of the physical uplink shared channel has a number of symbols not less than a predefined number of symbols. The at least one physical uplink control channel includes multiple overlapping physical uplink control channels. The method further includes determining the physical uplink control channel for multiplexing uplink control information of the plurality of overlapping physical uplink control channels, and The uplink control information of the multiple overlapping physical uplink control channels includes at least one type of uplink control information.

10. The method according to claim 9, wherein, The transmitted physical uplink shared channel includes at least one actual repeat of the physical uplink shared channel.

11. The method according to claim 10, in, The at least one actual repetition of the physical uplink shared channel includes a first actual repetition, and The method further includes transmitting a second actual repetition of the physical uplink shared channel without multiplexing the at least one type of uplink control information in the second actual repetition.

12. The method of claim 9, further comprising: By multiplexing the at least one type of uplink control information, it is determined which of the at least one physical uplink shared channels should be transmitted. as well as Determine which at least one of the identified physical uplink shared channels is actually reused for uplink control information multiplexing. The transmission includes at least one determined physical uplink shared channel that is actually repeated.

13. The method according to claim 9, wherein, The physical uplink shared channel is the earliest physical uplink shared channel among the at least one physical uplink shared channels.

14. The method according to claim 9, wherein, The at least one actual repetition of the physical uplink shared channel includes the earliest actual physical uplink shared channel repetition that overlaps with the physical uplink control channel.

15. The method of claim 9, further comprising determining the number of resource elements required for the transmission of the at least one type of uplink control information based on the nominal number of repeated symbols for the physical uplink shared channel.

16. The method of claim 9, further comprising determining the number of resource elements required for the transmission of the at least one type of uplink control information based on the actual number of repeated symbols used for the physical uplink shared channel.

17. The method of claim 9, further comprising determining whether one or more timing conditions required for multiplexing the at least one type of uplink control information in at least one actual repetition of the at least one physical uplink shared channel are met. in, Multiplexing includes, in response to determining that one or more timing conditions are met, multiplexing the at least one type of uplink control information in the at least one actual repetition of the physical uplink shared channel.

18. The method according to claim 17, wherein, The one or more timing conditions are based on the position of the earliest symbol of the earliest physical uplink shared channel or physical uplink control channel among the at least one physical uplink shared channel and the at least one physical uplink control channel.

Images