Aperiodic channel state information for ultra-reliable low-latency communications

Abstract

A method and apparatus are provided in which a downlink (DL) grant is received (902) that triggers aperiodic channel state information (ACSI) reporting and schedules a physical downlink shared channel (PDSCH) transmission. A first physical uplink control channel (PUCCH) resource for ACSI transmission and a second PUCCH resource for hybrid automatic repeat request (HARQ) acknowledgement (ACK) transmission corresponding to the scheduled PDSCH are determined (904). Based on downlink control information (DCI) of the DL grant, a first PUCCH transmission power for ACSI transmission using the first PUCCH resource and a second transmission power for HARQ ACK transmission using the second PUCCH resource are determined (906).

Description

Technical Field

[0001] The present disclosure relates to triggering and scheduling of aperiodic channel state information reports, including examples involving ultra-reliable low-latency communications. Background Art

[0002] Currently, user equipment such as wireless communication devices use wireless signals to communicate with other communication devices, such as within a network environment that can include one or more cells, within which various communication connections with the network and other devices operating within the network can be supported. The network environment generally involves one or more sets of standards, each of which defines various aspects of any communication connection made when using a corresponding standard within the network environment. Examples of developing and / or existing standards include new radio access technology (NR), evolved universal terrestrial radio access (E-UTRA), long term evolution (LTE), universal mobile telecommunication service (UMTS), global system for mobile communications (GSM), and / or enhanced data GSM environment (EDGE).

[0003] To better support applications that can have more time-sensitive communications, where both reliability and latency are issues, there is growing interest in a type of communication identified as Ultra-Reliable Low-Latency Communications (URLLC). Traditionally, however, data reliability and latency can be traded off to better support one or the other. Increasingly, applications are looking to improve performance related to both factors simultaneously.

[0004] Correspondingly, some more traditional ways of handling some control signaling need to be reconsidered. For example, channel state information (CSI) corresponds to known or determined channel properties of a communication link from the perspective of a receiver. The transmitter of the expected information can use this information to adjust the settings and parameters to be used when conveying information to the receiver. Over time, the channel state information can change, so refreshing the information can help enhance the reliability of subsequent communications. Therefore, enhanced timing, which can include delays and frequencies with which CSI can be updated, can be beneficial, which in turn allows the transmitter to better adapt to current channel conditions, such as in cases involving URLLC, where the reliability of the relevant message delivery being conveyed can be important. Non-periodic CSI can be used to request CSI reports at times that may not be otherwise scheduled and / or at times separated from other communications, such as during expected or planned hybrid automatic repeat request (HARQ) confirmation (ACK).

[0005] The inventors have recognized that it may be possible and beneficial to determine multiple physical uplink control channel transmissions for alternatingly transmitting ACSI reports and HARQ ACKs in response to receiving a downlink grant trigger and scheduling non-periodic channel state information reports, which in turn may allow faster transmission of ACSI reports, and which in turn may allow separate transmission powers to be determined for each of these events, which in turn may allow enhanced reliability of message delivery supporting the URLLC mode of operation. Summary of the invention

[0006] The present application provides a method in a user equipment. The method includes receiving a downlink (DL) grant that triggers a non-periodic channel state information (ACSI) report and schedules a physical downlink shared channel (PDSCH) transmission. Determine a first physical uplink control channel (PUCCH) resource for ACSI transmission corresponding to the scheduled PDSCH and a second PUCCH resource for hybrid automatic repeat request (HARQ) acknowledgement (ACK) transmission. Based on downlink control information (DCI) of the DL grant, determine a first PUCCH transmission power for ACSI transmission using the first PUCCH resource and determine a second transmission power for HARQ ACK transmission using the second PUCCH resource.

[0007] According to another possible embodiment, a user equipment is provided. The user equipment includes a transceiver that receives a downlink (DL) grant that triggers a non-periodic channel state information (ACSI) report and schedules a physical downlink shared channel (PDSCH) transmission. The user equipment further includes a controller that determines a first physical uplink control channel (PUCCH) resource for ACSI transmission corresponding to the scheduled PDSCH and a second PUCCH resource for hybrid automatic repeat request (HARQ) acknowledgement (ACK) transmission. Based on downlink control information (DCI) of the DL grant, a first PUCCH transmission power for ACSI transmission using the first PUCCH resource is determined by the controller, and a second transmission power for HARQ ACK transmission using the second PUCCH resource is determined by the controller.

[0008] According to another possible embodiment, a method in a network entity is provided. The method includes transmitting a downlink (DL) grant that triggers a non-periodic channel state information (ACSI) report and schedules a physical downlink shared channel (PDSCH) transmission to a specific user equipment. Then, the ACSI transmission is received via a determined first physical uplink control channel (PUCCH) resource and a hybrid automatic repeat request (HARQ) acknowledgement (ACK) transmission is received via a determined second PUCCH resource, each corresponding to the scheduled PDSCH, wherein, based on downlink control information (DCI) of the DL grant, a first PUCCH transmission power for ACSI transmission using the first PUCCH resource is determined, and a second transmission power for HARQ ACK transmission using the second PUCCH resource is determined.

[0009] According to another possible embodiment, a network entity is provided. The network entity includes a controller and a transceiver, the transceiver transmitting a downlink (DL) grant that triggers a non-periodic channel state information (ACSI) report and schedules a physical downlink shared channel (PDSCH) transmission to a specific user equipment. The transceiver further receives the ACSI transmission via a determined first physical uplink control channel (PUCCH) resource and receives a hybrid automatic repeat request (HARQ) acknowledgement (ACK) transmission via a determined second PUCCH resource, each corresponding to the scheduled PDSCH, wherein, based on downlink control information (DCI) of the DL grant, a first PUCCH transmission power for ACSI transmission using the first PUCCH resource is determined, and a second transmission power for HARQ ACK transmission using the second PUCCH resource is determined.

[0010] These and other features and advantages of the present application will be apparent from the following description of one or more preferred embodiments with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 is a block diagram of an exemplary network environment in which the present invention is adapted to operate;

[0012] Figure 2 is a timing diagram illustrating an exemplary triggering of ACSI reporting according to at least one embodiment;

[0013] Figure 3 is a timing diagram illustrating an exemplary scheduling of multiple PUSCH transmissions and scheduling of triggered ACSI;

[0014] Figure 4 is a timing diagram illustrating an exemplary scheduling of ACSI reporting and HARQ ACK transmission;

[0015] Figure 5 is a timing diagram illustrating another exemplary scheduling of ACSI reporting and HARQ ACK transmission via multiple uplink carriers;

[0016] Figure 6 is a timing diagram illustrating yet another exemplary scheduling of ACSI reporting and HARQ ACK transmission;

[0017] Figure 7 is a mapping table of a transmit power command (TPC) field of an exemplary DCI format;

[0018] Figure 8 is a mapping table for a TPC field of another exemplary DCI format;

[0019] Fig. 9 is a flow chart for triggering and scheduling transmission of ACSI reports in a user equipment;

[0020] Fig.10 is a flow chart for triggering and scheduling the reception of ACSI reports in a network entity; and

[0021] Fig.11 is an exemplary block diagram of an apparatus according to a possible embodiment. DETAILED DESCRIPTION

[0022] While the present disclosure is susceptible of being embodied in various forms, there is shown in the drawings and will be described below a presently preferred embodiment, it being understood that this disclosure is to be considered as illustrative of the invention and is not intended to limit the invention to the particular embodiment illustrated.

[0023] Embodiments provide various methods and apparatus, including mechanisms to achieve low-latency aperiodic channel state information. These mechanisms can involve aperiodic channel state information transmitted on a physical uplink control channel.

[0024] Figure 1 is an exemplary block diagram of a system 100 according to a possible embodiment. The system 100 can include a wireless communication device 110, such as a user equipment (UE), a base station 120, such as an enhanced Node B (eNB) or a next generation Node B (gNB), and a network 130. The wireless communication device 110 can be a wireless terminal, a portable wireless communication device, a smart phone, a cellular phone, a flip phone, a personal digital assistant, a personal computer, a selective call receiver, a tablet computer, a laptop computer, or any other device capable of sending and receiving communication signals over a wireless network.

[0025] The network 130 can include any type of network capable of sending and receiving wireless communication signals. For example, the network 130 can include a wireless communication network, a cellular telephone network, a time division multiple access (TDMA)-based network, a code division multiple access (CDMA)-based network, an orthogonal frequency division multiple access (OFDMA)-based network, a long term evolution (LTE) network, a fifth generation (5G) network, a third generation partnership project (3GPP)-based network, a satellite communication network, a high altitude platform network, the Internet, and / or other communication networks.

[0026] Aperiodic CSI can be important for URLLC operation to provide timely feedback to adjust transmission parameters.So far, ACSI can only be triggered by UL grant and will be transmitted on the Physical Uplink Shared Channel (PUSCH) scheduled by the uplink (UL) grant.

[0027] It has been proposed to use DL grants to trigger CSI (to be transmitted on PUCCH) to save control overhead in DL heavy operation (eg, when no PUSCH is scheduled).

[0028] If the UL grant schedules a PUSCH with repetitions via a dynamic PUSCH repetition indication via a UL granted DCI or via slot aggregation (fixed / configured number of repetitions), and / or if the UL grant triggers an ACSI report for URLLC operation, such as if the DCI / radio resource control (RRC) configuration indicates a high priority CSI report, such as by having a field in the DCI that triggers the CSI report or in the RRC configuration for the CSI report, the CSI report may need to be sent in a short time, and performing a PUSCH with multiple repetitions may not meet the time when the CSI report needs to be sent.

[0029] In the case of unlicensed operation, where DCI is able to schedule multiple transport blocks (TBs) using different PUSCHs (possibly in different overlapping / non-overlapping time spans), CSI is sent on the second PUSCH / penultimate scheduled PUSCH. However, such transmission may not meet the timeline requirements of CSI for URLLC operation.

[0030] The present disclosure provides mechanisms for determining:

[0031] the transmit power of the first and second PUCCH transmissions corresponding to the HARQ ACK of the scheduled PDSCH and the ACSI triggered by the DL grant,

[0032] PUCCH resources when UL grant is used for ACSI transmission,

[0033] PUSCH resources when UL grant is used for ACSI transmission,

[0034] The PUCCH format that carries ACSI, and

[0035] The priority level that triggers the CSI report.

[0036] Aperiodic CSI

[0037] Channel State Information (CSI) is feedback that a device can send to the network, which can help the network select communication (such as scheduling) parameters for the device. Aperiodic CSI (A-CSI / ACSI) is feedback provided by the device in response to a triggering event. A-CSI can be triggered by DCI (control signal) sent by the network.

[0038] The procedure for aperiodic CSI reporting is described in detail in TS 38.213, 38.214, 38.321 and 38.331.

[0039] CSI may consist of one or more of the following: (a) channel quality indicator (CQI), (b) precoding matrix indicator (PMI), (c) CSI reference signal (RS) resource indicator (CRI), (d) synchronization signal (SS) / physical broadcast channel (PBCH) block resource indicator (SSBRI), (e) layer indicator (LI), (f) rank indicator (RI), (8) L1-RSRP or (9) L1-SINR.

[0040] The UE can be configured by higher layers with N≥1 CSI report configurations (CSIReportConfig report settings), M≥1 CSI resource configurations (CSI-ResourceConfig resource settings), and at least one A-CSI trigger state list (such as CSI-AperiodicTriggerStateList). Each configured trigger state (such as using a higher layer parameter CSI-AperiodicTriggerState) is associated with one or more CSI report configurations (CSI-ReportConfig), where each CSI-ReportConfig is linked to (multiple) periodic, semi-persistent or aperiodic resource settings.

[0041] Once CSI reporting is triggered, e.g., via DCI,

[0042] The aperiodic resource offset is determined based on the resource offset configured for the resource set associated with the triggered CSI report (e.g., aperiodicTriggeringOffset of NZP-CSI-RS-ResourceSet [38.331])

[0043] Determine the timing offset by selecting a value from the configured offset value set of the triggered CSI reporting configuration (e.g., reportSlotOffsetList from CSI-ReportConfig) based on the DCI

[0044] The UE generates a CSI report based on the triggered CSI reporting configuration(s) and sends it in PUSCH (UL shared channel, such as PUSCH scheduled by the DCI that triggered the CSI report(s). The parameters in the CSI reporting configuration indicate the parameters that the UE should include in the CSI report (e.g., the reportQuantity parameter can indicate the CRI, rank indicator (RI), and channel quality indicator (CQI) that should be reported).

[0045] Each CSI reporting setting / configuration can be associated with a single bandwidth part (BWP) used for channel measurement and contains parameter(s) for one CSI reporting band.

[0046] Currently, ACSI can be triggered by a UL grant scheduling PUSCH with or without a UL shared channel (SCH) in PUSCH (e.g., uplink data / UL transport block). According to TS 38.214:

[0047] When the UE is scheduled to transmit a transport block and no CSI report, or the UE is scheduled by DCI to transmit a transport block and (multiple) CSI reports on PUSCH, the time domain resource assignment field value m of the DCI provides a row index m+1 to the allocation table. The determination of the resource allocation table used is defined in clause 6.1.2.1.1 of TS 38.214. The index row defines the time slot offset K2 to be applied for PUSCH transmission, the start and length indicator SLIV, or directly defines the start symbol S and the allocation length L, the PUSCH mapping type and the number of repetitions (if present in the resource allocation table).

[0048] When a UE is scheduled to send PUSCH without transport blocks and with (multiple) CSI reports via the CSI request field on the DCI, the time domain resource assignment field value m of the DCI provides an index m+1 to an allocation table row defined by the pusch-TimeDomainAllocationList of the higher layer configuration in pusch-Config. The index row defines the start and length indicator SLIV, as well as the PUSCH mapping type to be applied in the PUSCH transmission and the K2 value is determined as where Y j , j = 0, ..., N Rcp-1 is the corresponding list entry of the higher layer parameter -[reportSlotOffsetList-r16-ForDCIFormat0_2, if PUSCH is scheduled by DCI format 02; -reportSlotOffsetList-r16-ForDCIFormat0_1, if PUSCH is scheduled by DCI format 0_1 ​​and reportSlotOffsetList-r16-ForDCIFormat0_1 is configured]; -reportSlotOffsetList, [otherwise;] used for NRe in CSI-ReportConfig p Triggered CSI report setting, and Y j (m+1) is Y j The (m+1)th entry of .

[0049] The UE determines the offset X between the time slot containing the DCI triggering the aperiodic NZP CSI-RS resource set and the time slot in which the CSI-RS resource set is transmitted based on the aperiodicTriggeringOffset associated with the triggered ACSI report.

[0050] Throughout this disclosure, A-CSI is generally associated with low-latency operation unless specifically distinguished (e.g., low-latency CSI for CSI with a short CSI timeline (such as CSI calculation and transmission time) and non-low-latency CSI with a larger CSI timeline compared to the low-latency CSI timeline).

[0051] CSI reporting using PUCCH scheduled by UL grant

[0052] Embodiment 1 (PUCCH indication on UL grant)

[0053] In an embodiment, the UE receives an UL grant that triggers an aperiodic CSI report and schedules a PUSCH transmission, the UL grant indicating at least one of the following:

[0054] a) Whether to transmit CSI reports on PUSCH or PUCCH

[0055] b) PUCCH resources where CSI reports are sent

[0056] a. In the example, the PUCCH resource index is indicated in the UL grant, and the PUCCH timing is also indicated (how many symbols / subslots (such as PUCCH subslots) / slots after the last symbol of the UL grant, the PUCCH occurs)

[0057] i. There may be some processing time (processing time requirements are similar to Tproc1 or Tproc2 or Tproc,CSI defined in TS38.214): for example, the first symbol of PUCCH should not appear before a certain time after the end of reception of the last symbol of PDCCH carrying DCI scheduling PUSCH (or PDSCH, if DL assignment triggers CSI reporting and schedules the PDSCH).

[0058] In a related embodiment, the UE receives an UL grant that triggers an aperiodic CSI report and schedules a PUSCH transmission; the UE determines to use PUCCH resources instead of PUSCH if at least one of the following occurs:

[0059] The PUSCH length (including the number of PUCCH symbols for which the PUSCH is repeated; possibly also DL / non-UL symbols) is longer than a determined period (such as the time after which a CSI report needs to be sent, which can be, for example, a value configured in the CSI reporting configuration, or can be related to / derived from the processing timeline).

[0060] The triggered CSI quantity / type to be reported is a specific quantity / type (e.g., CQI reporting only)

[0061] The triggered CSI report size is less than a certain number of bits.

[0062] PUCCH resources appear / end earlier than PUSCH

[0063] In the example, Figure 2 As illustrated, PUCCH is transmitted / scheduled on a first component carrier and PUSCH is transmitted / scheduled on a second component carrier.

[0064] Figure 2 A timing diagram 200 is shown. Figure 2 In the UL DCI, PUCCH transmission for triggered ACSI reporting and PUSCH transmission for UL data transmission and / or triggered / semi-persistent CSI reporting are scheduled.

[0065] The number of REs required for CSI reporting is greater than the number of data REs that can be transmitted on PUSCH

[0066] In a related embodiment, if configured by the network, CSI reporting triggered by UL grant can be sent via PUCCH; otherwise, CSI reporting triggered by UL grant should follow the rules of previous 3GPP releases (eg, ACSI is to be sent on PUSCH scheduled by UL grant).

[0067] In a related embodiment, for a PUCCH scheduled by an UL grant, the PUCCH transmission time is determined based on a DCI field in the UL grant. In an example, the field selects a value from a configured value / offset set. In an example, a value set configured for PDSCH to HARQ_feedback timing can be used as a value for a configuration value / offset set for CSI PUCCH timing (e.g., a PDSCH to HARQ_feedback timing value can be used directly or a function of those PDSCH to HARQ_feedback timing values ​​can be used). In an example, the PUCCH transmission time is determined based on a maximum indication offset value from a value set (e.g., reportSlotOffsetList) configured for each CSI report corresponding to a triggered CSI state. The indication indicates setting an element index and can be based on a DCI field (e.g., a TDRA field value). For UL grants that trigger CSI on PUCCH and UL grants that trigger CSI on PUSCH, reportSlotOffsetList may be different.

[0068] In one example, the PUCCH transmission time is determined based on at least the PUSCH transmission time (e.g., the start PUSCH symbol) minus an offset value (e.g., the PUCCH starts "X" symbols before the start of PUSCH transmission). In one example, "X" is a positive or non-negative number, and in another example, "X" is a negative number.

[0069] In one example, the triggered CSI state includes multiple CSI report configurations, and the PUCCH transmission time for carrying the triggered CSI report is determined based on a maximum offset value in an offset value set, wherein the offset values ​​of the offset value set correspond to an offset list configured for a CSI report configuration of multiple CSI report configurations (e.g., reportSlotOffsetList as described in TS 38.331), and the DCI indicates / determines the offset value of the configured offset list associated with each CSI report configuration. In one example, the UE is configured with a maximum number of repetitions of CSI on PUSCH with repetition or slot aggregation. In another example, the UE is indicated with a repetition number of CSI on PUSCH with repetition based on a DCI field in an UL grant, which can be less than the PUSCH repetition number.

[0070] In one example, the number of resources (e.g., REs) with CSI on repeated PUSCH can be based on the total number of repetitions of PUSCH and the number of repetitions of CSI. In one example, an offset term can be added to the beta-offset value of CSI (e.g., adjusting the beta-offset value) (where the beta-offset value can be beta-offsetACK, betaOffsetCSI-Part1, betaOffsetCSI-Part2, e.g., as defined in TS 38.213 / TS 38.331), where the offset term can be based on the total number of repetitions of PUSCH and the number of repetitions of CSI. This may occur when the CSI report is for at least one but not all repetitions of PUSCH (e.g., indicated by a UL grant) (e.g., the UL grant schedules a PUSCH with repetitions).

[0071] In one embodiment, when the CSI report is about at least one repetition of the PUSCH but not all repetitions (e.g., indicated by the UL grant) (e.g., the UL grant schedules the PUSCH with repetitions), the CSI punctures at least a portion of the data REs (e.g., excluding DMRS REs) on the at least one repetition. In one example, puncturing means that the channel coded symbols of the coded PUSCH TB are mapped to at least a portion of the data REs but skipped from the transmission, and instead the CSI REs are transmitted on at least a portion of the data REs.

[0072] CSI reporting using PUSCH scheduled by UL grant

[0073] According to 38.214:

[0074] When DCI format 0_1 ​​schedules two PUSCH allocations, the aperiodic CSI report is carried on the second scheduled PUSCH. When DCI format 0_1 ​​schedules more than two PUSCH allocations, the aperiodic CSI report is carried on the penultimate scheduled PUSCH.

[0075] Embodiment 2 (PUSCH index indication carrying ACSI in multiple PUSCH assignments such as in NRU)

[0076] In one embodiment, when a DCI format schedules two or more PUSCH allocations (e.g., corresponding to different transport blocks or to the same transport block), the aperiodic CSI report is carried on the indicated scheduled PUSCHs (the DCI indicates which of those scheduled PUSCHs should carry the ACSI report).

[0077] The motivation for this embodiment may be the case of unlicensed operation, where the DCI can schedule multiple transport blocks (TBs) using different PUSCHs (possibly in different overlapping / non-overlapping time spans).Depending on when CSI is needed, the network can indicate which PUSCHs carry CSI reports.

[0078] In one example, the CSI report can be carried on the earliest PUSCH that meets the processing timeline requirements, for example, the first symbol of the PUSCH should not appear before a certain time offset after the end of reception of the last symbol of the PDCCH carrying the DCI that schedules the PUSCH (and triggers the ACSI report). In one example, the time offset used to determine the PUSCH carrying the CSI transmission is based on the maximum indicated offset value in the value set (e.g., reportSlotOffsetList) configured for each CSI report corresponding to the triggered CSI state. The indication indicates the setting element index and can be based on the DCI field (e.g., TDRA field value).

[0079] Figure 3 An example of a timing diagram 300 is shown, which includes determining PUSCH resources / transmission opportunities / instances for CSI transmission among multiple scheduled PUSCHs by DCI. In another example, multiple PUSCHs are associated with configured grant(s) and DCI triggers ACSI reporting.

[0080] More specifically, in Figure 3 In the example, DCI schedules 4 PUSCHs (carrying different TBs); DCI also triggers ACSI reporting. In the illustrated example, the ACSI report is transmitted on the second PUSCH. The CSI transmission timeline requires that the CSI report transmission cannot start earlier than T1 time (e.g., symbol / subslot / timeslot) after the end of the PDCCH carrying the DCI, and cannot be completed later than T2 time (e.g., symbol / subslot / timeslot) after the end of the PDCCH carrying the DCI.

[0081] CSI reporting using PUCCH scheduled by DL grant

[0082] At least one motivation for implementing ACSI on PUCCH scheduled by DL assignment / grant can be to avoid sending UL grants that trigger ACSI when there is no UL data (TB) to be scheduled.

[0083] In 38.213, the PUCCH transmission power is determined according to the following formula, where the different elements of the formula are described in TS 38.213:

[0084]

[0085] Embodiment 3 (CSI PUCCH power control)

[0086] In an embodiment, the UE receives a DL grant / assignment that triggers aperiodic CSI reporting and schedules PDSCH transmission.The UE determines a first PUCCH resource for ACSI transmission and a second PUCCH resource for HARQ-ACK transmission corresponding to the scheduled PDSCH.

[0087] • The UE determines a first PUCCH transmission power for a first PUCCH transmission and a second transmission power for a second PUCCH transmission based on the DCI of the DL grant / assignment.

[0088] Figure 4-6 Some examples are depicted in .

[0089] Figure 4 A timing diagram 400 is shown. Figure 4 In the present invention, the first PUCCH (for ACSI) and the second PUCCH (for HARQ ACK) can have different transmission powers.

[0090] Figure 5 Another timing diagram 500 is shown. Figure 5 In the DCI, the first PUCCH (used for ACSI) and the second PUCCH (used for HARQ ACK) can have different transmission powers. The DCI carries at least a TPC command.

[0091] Figure 6 Another timing diagram 600 is shown. Figure 6 In , the first PUCCH (for ACSI) and the second PUCCH (for HARQ ACK) can have different transmission powers; DCI schedules PDSCH, and some UL resources appear somewhere in the middle of the DL symbol group of PDSCH.

[0092] In a related embodiment, the UE determines the first and second PUCCH transmission powers based on a single field in the DCI (e.g., a 2-bit TPC command for a scheduled PUCCH used in DCI format 1-1), e.g., the same TPC command is applied to both PUCCHs (the first PUCCH and the second PUCCH).

[0093] In a related embodiment, the PUCCH power control adjustment state is the same for two PUCCHs (the first PUCCH and the second PUCCH).

[0094] In a related embodiment, the transmission power of the first PUCCH is derived based on the TPC command and an offset to at least one parameter that determines the transmission power of the second PUCCH: for example, Δ F PUCCH(F) is derived as follows: When two PUCCHs use the same PUCCH format, Δ for the second PUCCH F PUCCH (F) plus an offset "D". In an example, "D" is configured by higher layers. In at least one example, "D" is configured by higher layers for each PUCCH format.

[0095] In a related embodiment, the transmission power of the first PUCCH is derived based on an offset term added to the Po_PUCCH. The offset term may be configured by a higher layer. The Po_PUCCH without any offset is used for the second PUCCH.

[0096] In an embodiment, the UE receives an UL grant / assignment that triggers aperiodic CSI reporting and schedules PUSCH transmission (e.g., PUSCH includes UL TB and / or non-low-latency CSI (CSI that expires later than low-latency CSI); both low-latency and non-low-latency CSI are triggered by the UL grant). The UE determines PUCCH resources for ACSI transmission.

[0097] • The UE determines the PUCCH transmission power for PUCCH transmission based on the UL grant / assigned DCI.

[0098] o In one example, a first field in the DCI indicates a TPC command for PUSCH, and a second field in the DCI indicates a TPC command for PUCCH.

[0099] In an example, a single TPC field indicates TPC commands for the first and second PUCCHs. For example, the most significant bits of the first number of the field are used for the second PUCCH TPC, and the remaining bits (the second number of bits) are used for the first PUCCH TPC. In an example, one or both of the first number of bits and the second number of bits are configured.

[0100] In a related embodiment, the UE determines the PUSCH transmit power and the PUCCH transmit power based on a single field in the DCI (e.g., a 2-bit TPC command for scheduled PUSCH, as used in, e.g., DCI format 2-0), e.g., the same TPC command is applied to both PUSCH and PUCCH, or alternatively, the TPC command applicable to PUCCH is derived from a TPC command signaled in the DCI: e.g., because the transmit power update of the TPC command is derived based on the PUSCH and PUCCH resource allocations (e.g., the number of RBs).

[0101] In the example, if the UE is not configured with TPC accumulation for PUSCH transmission (TPC commands are never accumulated, e.g. Table 7.1.1-1 in TS 38.213), this is reproduced herein as Figure 7, the TPC command applicable to PUCCH is derived from the TPC command for PUSCH by using the same TPC command field index, but mapping it to the cumulative TPC command value in dB. For example, if the TPC command field is "0" (the first entry of Table 7.1.1-1 in TS 38.213, the TPC command for PUCCH will be -1dB, while the TPC command for PUSCH will be -4dB).

[0102] More specifically, corresponding to Table 7.1.1-1 in TS 38.213 Figure 7 Table 700 is illustrated, which includes a DCI format for scheduling PUSCH transmission, or DCI format 2_2 with a CRC scrambled by TPC-PUSCH-RNTI, or the TPC command field of DCI format 2_3 to absolute and cumulative delta PUSCH,b,f,c Value or δ SRS,b,f,c Alternatively, the value corresponding to Table 7.2.1-1 in TS 38.213 Figure 8 800, which includes the accumulated delta from the TPC command field of DCI format 1_0 or DCI format 1_1 or DCI format 2_2 with a CRC scrambled by TPC-PUCCH-RNTI PUCCH,b,f,c A map of values.

[0103] In a related embodiment, the PUCCH power control adjustment state is the same for PUCCH and PUSCH.

[0104] CSI multiplexing / priority rules between PUCCH and PUSCH / PUCCH

[0105] In an embodiment, when a DL grant triggers ACSI and schedules PDSCH transmission, the UE multiplexes the HARQ-ACK corresponding to the PDSCH and the CSI report corresponding to the triggered ACSI onto the PUCCH resources indicated by the DL grant when the following conditions are met:

[0106] Condition 1: The first symbol of the PUCCH resource is not at a time after the last symbol of the PDSCH (e.g., as defined in 3GPP TS 38.213). ) before, and

[0107] • Condition 2: The last symbol of the PUCCH resource is not after a certain time (eg, CSI timeline / delay requirement).

[0108] In a related embodiment, if the above conditions are not met, the UE determines a second PUCCH resource and transmits a HARQ-ACK corresponding to the PDSCH and a report corresponding to the triggered ACSI on the second PUCCH resource on the first PUCCH.

[0109] ·If the CSI delay timeline / requirement is not met (e.g., the second bullet point in the above embodiment ("Condition 2" above)); determine a second PUCCH resource because the HARQ-ACK PUCCH resource is not suitable for ACSI reporting. The second PUCCH resource can be indicated by RRC signaling in the associated CSI reporting configuration. In this case, depending on the PUCCH resource configuration, there may be an overlap between the two PUCCH resources. Alternatively, in the case where the first PUCCH resource does not meet the CSI delay requirement, as described in Example 3a below, the UE is not expected to indicate the first PUCCH resource overlapping with the second PUCCH resource in the DCI.

[0110] o In a related embodiment, if the first and second PUCCH resources overlap in time for the same carrier, the UE transmits one of the first PUCCH or the second PUCCH, for example, via an RRC configuration (the RRC configuration determines which PUCCH resource (HARQ ACK PUCCH or CSI PUCCH) is prioritized).

[0111] In one example, a PUCCH resource indicator in the DCI may indicate a pair of (first, second) PUCCH resources (e.g., indicating an element of a PUCCH resource list associated with two values ​​of a PUCCH resource ID). In another example, the first PUCCH resource is indicated by a PUCCH resource indicator value (an index within a PUCCH resource list configured by a higher layer). The second PUCCH resource is determined as the next (e.g., PUCCH resource indicator value + 1 modulo the maximum number of PUCCH resources in a PUCCH resource set) PUCCH resource in the PUCCH resource list configured by the higher layer. In another example, the second PUCCH resource is determined as a configured / fixed number "b" (e.g., PUCCH resource indicator value + "b" modulo the maximum number of PUCCH resources in a PUCCH resource set) PUCCH resources in the PUCCH resource list configured by the higher layer.

[0112] Example 3a: In an embodiment, when a DL grant triggers ACSI and schedules PDSCH transmission, in the case where different PUCCH resources are used for HARQ-ACK transmission corresponding to PDSCH and for triggered ACSI transmission, the UE is not expected to receive / determine overlapping PUCCH resources corresponding to HARQ-ACK and triggered CSI in a timely manner. In the example, the indicated K1 value (PDSCH to HARQ_feedback timing indicator) and the determined / indicated KCSI value (e.g., PDDCH / PDSCH to CSI feedback timing) are not expected to result in overlapping PUCCHs in the time domain on the same carrier.

[0113] In an embodiment, when UL grant / assignment triggers ACSI and schedules PUSCH transmission, the UE is not expected to be allocated overlapping PUCCH and PUSCH resources in time when PUCCH resources are determined to convey ACSI and PUSCH resources / transmission opportunities are allocated for UL data transmission.

[0114] • Alternatively, ACSI shall be transmitted on PUSCH.

[0115] In an embodiment, when a DL grant triggers ACSI and schedules PDSCH transmission (with multiple repetitions of PDSCH, for example, scheduled by a single DL grant), the UE determines a first PUCCH resource and a second PUCCH resource, and transmits a HARQ-ACK transmission corresponding to the PDSCH on the first PUCCH resource, and transmits a CSI report corresponding to the triggered ACSI on the second PUCCH resource.

[0116] • In an embodiment, if the PDSCH has less than a threshold number of repetitions / symbols, the first and second PUCCH resources are the same. Otherwise, the first and second PUCCH resources are different.

[0117] o For HARQ-ACK transmission on PUCCH / PUSCH, the UE has to wait until the end of all PDSCH repetitions (if all repetitions are scheduled by a single DCI); while for CSI, the UE does not need to wait until the end of the PDSCH symbol / repetition.

[0118] In an embodiment, the first PUCCH resource and the second PUCCH resource are on different serving cells / carriers.

[0119] Other embodiments

[0120] Embodiment a

[0121] In an embodiment, the ACSI transmitted on the PUCCH is restricted to use certain PUCCH formats (e.g., PUCCH format 0 or PUCCH format 2; e.g., depending on the PUCCH payload size). The PUCCH format to be used can also be configured as part of the CSI report configuration, or can be indicated by the DCI scheduling the PUCCH. Although for UCI multiplexing purposes (multiplexing multiple UCIs, e.g., HARQ ACK / SR / CSI or multiplexing different UCIs of different component carriers / BWPs), it is better to determine the PUCCH format to be used.

[0122] Other embodiments

[0123] In an embodiment, ACSI triggered by DL assignment has the same / similar priority as HARQ ACK (PUCCH for HARQ ACK).

[0124] In an embodiment, the ACSI triggered by the UL grant / assignment has the same / similar priority as the PUSCH scheduled (via the UL grant / assignment).

[0125] In an embodiment, ACSI triggered by DL assignment has the same / similar priority as aperiodic CSI reporting to be carried on PUSCH.

[0126] In an embodiment, ACSI triggered by a DL / UL grant is transmitted on the PUCCH of the supplementary carrier (the normal / non-supplementary carrier and the supplementary carrier are associated with a single downlink carrier).

[0127] In an embodiment, CSI reporting configurations associated with A-CSI triggering states have the same priority (e.g., in terms of low latency CSI vs. non-low latency CSI). In another embodiment, low latency CSI can be triggered by certain DCI formats / DL DCI. In another embodiment, a priority index is configured for each CSI reporting configuration.

[0128] In an embodiment, ACSI can be triggered via DL DCI with DCI format if DCI is received in a predetermined subset of the search space / CORESET.

[0129] In an embodiment, if DCI is received in a predetermined subset of search spaces / CORESETs, ACSI can be triggered via DL / UL DCI with a DCI format that determines / indicates PUCCH resources. For example, if DCI format 1-2 is received in search space / CORESET A, there is a field in the DCI to indicate the PUCCH resources used for ACSI transmission, and if DCI format 1-2 is received in search space / CORESET B, ACSI cannot be triggered by DCI format 1-2. In another example, if DCI format 0-2 is received in search space / CORESET A, there is a field in the DCI to indicate the PUCCH resources used for ACSI transmission, and if DCI format 0-2 is received in search space / CORESET B (and PUSCH is scheduled), the triggered ACSI is transmitted on the scheduled PUSCH.

[0130] In an embodiment, the UE is not expected to be triggered by an ACSI report with an associated PUCCH more than once within a time period (eg, within a time slot or slots configured by RRC or based on capability signaling) for ACSI report transmission.

[0131] • This embodiment can be used to minimize processing / collision situations (eg, collision between PUCCH and PUSCH) since simultaneous PUSCH and PUCCH are not supported and there are DMRS symbols for PUCCH.

[0132] In an embodiment, the UE indicates in the PUCCH resource associated with the triggered ACSI report whether the ACSI report is included in the PUCCH. One motivation for this embodiment is that the gNB wants to check if a major update to the scheduling is needed by triggering the ACSI report and if so, what is a good MCS / CQI. Sometimes the most recently used MCS can be good to use, especially considering transmitting transport blocks with small size and low BLER target for URLLC operation.

[0133] In an embodiment, the triggered CSI state includes a maximum of "M" CSI report configurations, and "M" is the UE capability (higher layer signal) for low latency / high priority operation (wherein high priority CSI reports are compared to CSI with low priority reports; where the priority (high vs. low) can be used to decide which CSI report to discard in the event of a conflict between different CSI reports associated with different priorities (high vs. low, and the CSI report associated with the low priority can be discarded). In an example, the priority (high vs. low or, for example, priority index "1" vs. priority index "0") is configured as part of the CSI report configuration.

[0134] • In one example, a collision between two CSI reports is defined as a collision between the transmissions of the two CSI reports.

[0135] In another example, in the case where (multiple) low priority CSI reports are already using / occupying one or more CSI processing units (CPUs), a conflict between two CSI reports is defined (e.g., as defined in Section 5.2.1.6 of TS 38.214), and a high priority CSI report is triggered. In this case, in one example, one or more low priority CSI reports occupying the CPU are discarded to allow processing of the CSI report with the high priority.

[0136] o In a related example, the latest low priority CSI report that starts to occupy the CPU is discarded to make room for processing the triggered high priority CSI report.

[0137] o In a related example, a partial CSI report of one or more low priority CSI reports is omitted to allow the CPU to process a triggered high priority CSI report.

[0138] In another example, the priority of the CSI report is derived based on at least an RRC parameter of the CSI report configuration (e.g., a priority index configured for the CSI report configuration) and a priority rule similar to that defined in Section 5.2.5 of TS 38.214. In one example, a CSI report with a high priority indication (RRC parameter of the CSI report configuration (e.g., a priority index configured for the CSI report configuration)) has a higher priority than those CSI reports with a low priority indication (RRC parameter of the CSI report configuration (e.g., a priority index configured for the CSI report configuration)) or those CSI reports without a priority indication (no priority index configured for the CSI report configuration); and within the high priority CSI report, a priority rule similar to that defined in Section 5.2.5 of TS 38.214 applies; and within the low priority CSI report, a priority rule similar to that defined in Section 5.2.5 of TS 38.214 applies.

[0139] In one example, instead of ACSI in the described embodiments, semi-persistent CSI (eg, triggered by DL DCI) can be used.

[0140] According to at least some embodiments, one or more of the following can be supported:

[0141] 1. Determine the transmit power of the first and second PUCCH transmissions corresponding to the HARQ ACK of the scheduled PDSCH, and trigger the ACSI by the DL grant;

[0142] 2. When UL grant is used for ACSI transmission, determine PUCCH resources;

[0143] 3. When UL grant is used for ACSI transmission, PUSCH resources / timings are determined, and multiple PUSCH resources / timings are scheduled by the UL grant;

[0144] 4. Determine the PUCCH format that carries ACSI.

[0145] Fig. 9 Flowchart 900 for triggering and scheduling transmission of ACSI reports in a user equipment is illustrated. According to at least one embodiment, the method can include receiving 902 a downlink (DL) grant that triggers an aperiodic channel state information (ACSI) report and schedules a physical downlink shared channel (PDSCH) transmission. A first physical uplink control channel (PUCCH) resource for ACSI transmission and a second PUCCH resource for hybrid automatic repeat request (HARQ) acknowledgement (ACK) transmission corresponding to the scheduled PDSCH can be determined 904. A first PUCCH transmission power for ACSI transmission using the first PUCCH resource and a second transmission power for HARQ ACK transmission using the second PUCCH resource can be determined 906 based on downlink control information (DCI) of the DL grant.

[0146] In some examples, the first PUCCH resource can end earlier than the second PUCCH resource.

[0147] In some examples, the first PUCCH resource can be transmitted on a different carrier than the carrier on which the second PUCCH resource is transmitted.

[0148] In some instances, ACSI transmissions using the first PUCCH resources and HARQ ACK transmissions using the second PUCCH resources may not overlap in time. In some of these instances, ACSI transmissions using the first PUCCH resources can be scheduled on a supplementary carrier, and HARQ ACK transmissions using the second PUCCH resources can be scheduled on a non-supplementary carrier of the serving cell.

[0149] In some examples, ACSI reporting and corresponding determination of the first PUCCH resource for ACSI transmission can be triggered without an uplink grant.

[0150] In some instances, the DCI can include at least a transmit power command (TPC). In some of these instances, the same TPC of the DCI can be applied to both the first and second PUCCH resources. In other instances, one of the first PUCCH transmission power and the second PUCCH transmission power can be derived based on the TPC, and wherein the other of the first PUCCH transmission power and the second PUCCH transmission power can be derived based on an adjusted TPC, wherein the adjusted TPC can include a value to which a predetermined offset has been applied to at least one parameter of the TPC. In some of these instances, the at least one parameter can include a Po_PUCCH parameter, wherein the predetermined offset can be applied to the value of the parameter to derive the first PUCCH transmission power.

[0151] In some instances, the first PUCCH resource can be selected to become the second PUCCH resource when the first symbol of the second PUCCH resource is at least a predetermined amount of time after the last symbol of the PDSCH and the last symbol of the second PUCCH is before a predetermined delay requirement for ACSI reporting expires.

[0152] In some examples, the start of the first PUCCH resource can occur before the end of the PDSCH transmission.

[0153] In some examples, the PDSCH can include multiple PDSCH repetitions, and the start of the first PUCCH resource can occur before the end of a last one of the multiple PDSCH repetitions.

[0154] Fig.10 A flow chart 1000 for triggering and scheduling reception of ACSI reports in a network entity is illustrated. According to at least one embodiment, the method can include transmitting 1002 a downlink (DL) grant to a specific user equipment that triggers an aperiodic channel state information (ACSI) report and schedules a physical downlink shared channel (PDSCH) transmission. The ACSI transmission can then be received 1004 via a determined first physical uplink control channel (PUCCH) resource and a hybrid automatic repeat request (HARQ) acknowledgement (ACK) transmission can be received 1004 via a determined second PUCCH resource, each corresponding to the scheduled PDSCH, wherein based on downlink control information (DCI) of the DL grant, a first PUCCH transmission power for ACSI transmission using the first PUCCH resource can be determined 1006, and a second transmission power for HARQ ACK transmission using the second PUCCH resource can be determined 1006.

[0155] Another embodiment can include a method in a user equipment (UE), wherein the method can include receiving an uplink (UL) grant that triggers an aperiodic channel state information (ACSI) report and schedules a physical uplink shared channel (PUSCH) transmission. The UL grant can indicate at least one of: a) whether to transmit the ACSI report on the PUSCH or on a physical uplink control channel (PUCCH), and b) when the ACSI report is to be sent on the PUCCH, a specific PUCCH resource on which the ACSI report is to be sent.

[0156] Yet another embodiment can include a method in a user equipment, wherein the method can include receiving an uplink (UL) grant that triggers an aperiodic channel state information (ACSI) report and schedules at least two physical uplink shared channel (PUSCH) transmissions. Downlink control information (DCI) can indicate which of the at least two PUSCH transmissions should carry the ACSI report.

[0157] It should be understood that, despite the specific steps shown in the figures, multiple additional or different steps can be performed depending on the embodiment, and one or more specific steps can be rearranged, repeated, or completely eliminated depending on the embodiment. In addition, some steps performed can be repeated on an ongoing or continuous basis while other steps are performed. In addition, different steps can be performed by different elements or in a single element of the disclosed embodiments.

[0158] Fig.11 is an example block diagram of an apparatus 1100, such as a wireless communication device 110, according to a possible embodiment. The apparatus 1100 can include a housing 1110, a controller 1120 within the housing 1110, audio input and output circuitry 1130 coupled to the controller 1120, a display 1140 coupled to the controller 1120, a transceiver 1150 coupled to the controller 1120, an antenna 1155 coupled to the transceiver 1150, a user interface 1160 coupled to the controller 1120, a memory 1170 coupled to the controller 1120, and a network interface 1180 coupled to the controller 1120. The apparatus 1100 can perform the methods described in all embodiments.

[0159] Display 1140 can be a viewfinder, a liquid crystal display (LCD), a light emitting diode (LED) display, a plasma display, a projection display, a touch screen or any other device that displays information. Transceiver 1150 can include a transmitter and / or a receiver. Audio input and output circuit 1130 can include a microphone, a speaker, a transducer or any other audio input and output circuit. User interface 1160 can include a keypad, a keyboard, a button, a touch pad, a joystick, a touch screen display, another additional display or any other device that can be used to provide an interface between a user and an electronic device. Network interface 1180 can be a universal serial bus (USB) port, an Ethernet port, an infrared transmitter / receiver, an IEEE 1394 port, a WLAN transceiver or any other computer that can connect the device to a network, a device or can transmit and receive data communication signals. Memory 1170 can include random access memory, read-only memory, optical memory, solid-state memory, flash memory, removable memory, a hard drive, a cache or any other memory that can be coupled to the device.

[0160] Device 1100 or controller 1120 may implement any operating system, such as Microsoft or Android TM Or any other operating system. The device operating software can be written in any programming language, such as C, C++, Java or Visual Basic. The device software can also run on an application framework, such as, for example, frame, Framework or any other application framework. Software and / or operating system can be stored in memory 1170 or elsewhere in device 1100. Device 1100 or controller 1120 can also use hardware to implement the disclosed operations. For example, controller 1120 can be any programmable processor. The disclosed embodiments can also be implemented on general or special-purpose computers, programmed microprocessors or microcontrollers, 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. In general, controller 1120 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 1100 can also perform some or all of the operations of the disclosed embodiments.

[0161] The method of the present disclosure can be implemented on a programmed processor. However, the controller, flow chart and module can also be implemented on a general or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit components, an integrated circuit, a hardware electronic or logic circuit such as a discrete component circuit, a programmable logic device, etc. In general, any device on which a finite state machine capable of implementing the flow chart shown in the figure resides can be used to implement the processor function of the present disclosure.

[0162] Although the present disclosure has been described by its specific embodiments, it is apparent that many substitutions, modifications and variations will be apparent to those skilled in the art. For example, the various components of the embodiments may be interchanged, added or replaced in other embodiments. In addition, all elements of each of the accompanying drawings are not necessary for the operation of the disclosed embodiments. For example, a person of ordinary skill in the art of the disclosed embodiments will be able to make and use the teachings of the present disclosure by simply adopting the elements of the independent claims. Therefore, the embodiments of the present disclosure as set forth herein are intended to be illustrative, rather than restrictive. Various changes may be made without departing from the spirit and scope of the present disclosure.

[0163] In this document, relational terms such as "first", "second", etc. can be used only to distinguish one entity or action from another entity or action, without necessarily requiring or implying any actual such relationship or order between such entities or actions. The phrases "at least one", "at least one selected from the following group", or "at least one selected from" followed by a list are defined to represent one, some or all, but not necessarily all elements in the list. The terms "include", "comprises", or any other variant thereof are intended to cover non-exclusive inclusions, so that the process, method, article, or device including the list of elements does not include only these elements, but may include other elements not explicitly listed or elements inherent to such processes, methods, articles, or devices. In the absence of more constraints, elements starting with "one", "an", etc. do not exclude the presence of other identical elements in the process, method, article, or device including the element. In addition, the term "another" is defined as at least the second or more. As used herein, the terms "include", "have", etc. are defined as "include". In addition, the background section is written as the inventor's understanding of the context of some embodiments at the time of application, and includes the inventor's own recognition of any problems of the prior art and / or problems encountered in the inventor's own work.

Claims

1. A method in a user equipment, the method comprising: receiving a downlink (DL) grant that triggers an aperiodic channel state information (ACSI) report and schedules a physical downlink shared channel (PDSCH) transmission; determining a first physical uplink control channel (PUCCH) resource for ACSI transmission and a second PUCCH resource for hybrid automatic repeat request (HARQ) acknowledgement (ACK) transmission corresponding to the scheduled PDSCH; and Based on downlink control information (DCI) of the DL grant, a first PUCCH transmission power for the ACSI transmission using the first PUCCH resource is determined and a second transmission power for the HARQ ACK transmission using the second PUCCH resource is determined.

2. The method according to claim 1, wherein: The first PUCCH resource ends earlier than the second PUCCH resource.

3. The method according to claim 1, wherein: The first PUCCH resources are transmitted on a different carrier than a carrier on which the second PUCCH resources are transmitted.

4. The method according to claim 1, wherein: The ACSI transmission using the first PUCCH resource and the HARQ ACK transmission using the second PUCCH resource do not overlap in time.

5. The method according to claim 4, wherein: The ACSI transmission using the first PUCCH resources is scheduled on a supplementary carrier, and the HARQ ACK transmission using the second PUCCH resources is scheduled on a non-supplementary carrier of a serving cell.

6. The method according to claim 1, wherein: The ACSI report and the corresponding determination of the first PUCCH resource for ACSI transmission are triggered without an uplink grant.

7. The method according to claim 1, wherein: The DCI includes at least a transmit power command (TPC).

8. The method according to claim 7, wherein: The same TPC of the DCI is applied for use with both the first PUCCH resource and the second PUCCH resource.

9. The method according to claim 7, wherein: One of the first PUCCH transmission power and the second PUCCH transmission power is derived based on the TPC, and wherein the other of the first PUCCH transmission power and the second PUCCH transmission power is derived based on the adjusted TPC, wherein the adjusted TPC includes a value to which a predetermined offset has been applied to at least one parameter of the TPC.

10. The method according to claim 9, wherein: The at least one parameter comprises a Po_PUCCH parameter, wherein the predetermined offset is applied to the value of the parameter when deriving the first PUCCH transmission power.

11. The method according to claim 1, wherein: The first PUCCH resource is selected to become the second PUCCH resource when a first symbol of the second PUCCH resource is at least a predetermined amount of time after a last symbol of the PDSCH and a last symbol of the second PUCCH is before a predetermined delay requirement for ACSI reporting expires.

12. The method according to claim 1, wherein: The start of the first PUCCH resource occurs before the end of the PDSCH transmission.

13. The method according to claim 1, wherein: The PDSCH includes a plurality of PDSCH repetitions, and a start of the first PUCCH resource occurs before an end of a last one of the plurality of PDSCH repetitions.

14. A user equipment, comprising: a transceiver that receives a downlink (DL) grant that triggers an aperiodic channel state information (ACSI) report and schedules a physical downlink shared channel (PDSCH) transmission; and a controller that determines a first physical uplink control channel (PUCCH) resource for ACSI transmission and a second PUCCH resource for hybrid automatic repeat request (HARQ) acknowledgement (ACK) transmission corresponding to the scheduled PDSCH; and Wherein, based on the downlink control information (DCI) of the DL grant, the controller determines a first PUCCH transmission power for the ACSI transmission using the first PUCCH resource, and the controller determines a second transmission power for the HARQ ACK transmission using the second PUCCH resource.

15. The user equipment according to claim 14, wherein: The first PUCCH resource ends earlier than the second PUCCH resource.

16. The user equipment according to claim 14, wherein: The first PUCCH resources are transmitted via the transceiver on a carrier different from a carrier on which the second PUCCH resources are transmitted.

17. The user equipment according to claim 14, wherein: The ACSI transmission using the first PUCCH resource and the HARQ ACK transmission using the second PUCCH resource do not overlap in time.

18. The user equipment according to claim 14, wherein: The DCI includes at least a transmit power command (TPC).

19. The user equipment according to claim 14, wherein: The first PUCCH resource is selected to become the second PUCCH resource when a first symbol of the second PUCCH resource is at least a predetermined amount of time after a last symbol of the PDSCH and a last symbol of the second PUCCH is before a predetermined delay requirement for ACSI reporting expires.

20. The user equipment according to claim 14, wherein: The start of the first PUCCH resource occurs before the end of the PDSCH transmission.

Images