Patent Description:
Presently, user equipment, such as wireless communication devices, communicate with other communication devices using wireless signals, 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. Network environments often involve one or more sets of standards, which each define various aspects of any communication connection being made when using the 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 Telecommunications Service (UMTS), Global System for Mobile Communication (GSM), and/or Enhanced Data GSM Environment (EDGE).

In order to better support applications that can have more time sensitive communication, where both reliability and latency are an issue, there has been an increasing focus on a type of communication identified as ultra-reliable low-latency communications (URLLC). While traditionally, data reliability and latency could be traded off, so as to better support one or the other. Increasingly, applications are desiring that performance relative to both factors be simultaneously enhanced.

Correspondingly, some of the more traditional ways of handling some of the control signaling needs to be rethought. For example, channel state information (CSI) corresponds to known or determined channel properties of a communication link from the perspective of the receiver. The information can be used by the anticipated transmitter of information to adjust the setting and parameters that are to be used in communicating information to a recipient. Over time channel state information can change, so refreshing the information can be beneficial for enhancing the reliability of subsequent communications. Consequently, enhancing the timing, which can include the latency and the frequency with which the CSI can be updated can be beneficial, which in turn allows a transmitter to better adapt to the current channel conditions, such as in instances involving URLLC where the reliability of the related messaging being communicated can be important. An aperiodic CSI can be used to request a CSI report at a time that might not have been otherwise scheduled, and/or at a time that is separate from other communications, such as during an anticipated or planned hybrid automatic repeat request (HARQ) acknowledgement (ACK).

The present inventors have recognized that by triggering and scheduling an aperiodic channel state information report in response to receiving a downlink grant, it may be possible and beneficial to determine multiple physical uplink control channel transmissions for alternatively transmitting the ACSI report and the HARQ ACK, which in turn may allow for the ACSI report to be transmitted sooner, and which in turn could allow a separate transmission power to be determined for each of these events, which in turn may allow for the reliability of the messaging in support of an URLLC mode of operation to be enhanced.

The prior art document <CIT> describes a terminal that determines channel condition information associated with an aperiodic CSI feedback in response to a received aperiodic CSI trigger, wherein the terminal reports the A-CSI feedback using a PUCCH. The prior art document.

<CIT> describes a terminal that receives a communication over a PDCCH transmitted using a DCI format. When a TDD cell is the primary cell, a first uplink reference UL-DL configuration used for determining an interval between reception of the PDCCH indicating transmission of a PUSCH and the transmission of the PUSCH is configured for the TDD cell. Further, a second uplink reference UL-DL configuration is used for determining whether or not to use DAI included in the DCI format of the PDCCH indicating the transmission of the PUSCH is configured for the FDD cell.

Claim <NUM> defines a method in a user equipment and claim <NUM> defines a user equipment. In the following, any method and/or apparatus referred to as embodiments but nevertheless do not fall within the scope of the appended claims are to be understood as examples helpful in understanding the invention.

The present application provides a method in a user equipment. The method includes receiving a downlink (DL) grant triggering an aperiodic channel state information (ACSI) report and scheduling 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) acknowledgment (ACK) transmission corresponding to the scheduled PDSCH are determined. A first PUCCH transmission power for the ACSI transmission using the first PUCCH resource and a second transmission power for the HARQ ACK transmission using the second PUCCH resource are determined based on downlink control information (DCI) of the DL grant.

According to another possible embodiment, a user equipment is provided. The user equipment includes a transceiver that receives a downlink (DL) grant triggering an aperiodic channel state information (ACSI) report and scheduling 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 and a second PUCCH resource for hybrid automatic repeat request (HARQ) acknowledgment (ACK) transmission corresponding to the scheduled PDSCH. A first PUCCH transmission power for the ACSI transmission is determined by the controller using the first PUCCH resource and a second transmission power for the HARQ ACK transmission is determined by the controller using the second PUCCH resource based on downlink control information (DCI) of the DL grant.

According to a further possible embodiment, a method in a network entity is provided. The method includes transmitting a downlink (DL) grant to a particular user equipment triggering an aperiodic channel state information (ACSI) report and scheduling a physical downlink shared channel (PDSCH) transmission. An ACSI transmission via a determined first physical uplink control channel (PUCCH) resource and a hybrid automatic repeat request (HARQ) acknowledgment (ACK) transmission via a determined second PUCCH resource, which each correspond to the scheduled PDSCH are then received, where a first PUCCH transmission power for the ACSI transmission was determined using the first PUCCH resource and a second transmission power for the HARQ ACK transmission was determined using the second PUCCH resource based on downlink control information (DCI) of the DL grant.

According to a still further possible embodiment, a network entity is provided. The network entity includes a controller, and a transceiver that transmits a downlink (DL) grant to a particular user equipment triggering an aperiodic channel state information (ACSI) report and scheduling a physical downlink shared channel (PDSCH) transmission. The transceiver further receives an ACSI transmission via a determined first physical uplink control channel (PUCCH) resource and a hybrid automatic repeat request (HARQ) acknowledgment (ACK) transmission via a determined second PUCCH resource, which each correspond to the scheduled PDSCH, where a first PUCCH transmission power for the ACSI transmission was determined using the first PUCCH resource and a second transmission power for the HARQ ACK transmission was determined using the second PUCCH resource based on downlink control information (DCI) of the DL grant.

These and other features, and advantages of the present application are evident from the following description of one or more preferred embodiments, with reference to the accompanying drawings.

While the present disclosure is susceptible of embodiment in various forms, there is shown in the drawings and will hereinafter be described presently preferred embodiments with the understanding that the present disclosure is to be considered an exemplification of the invention and is not intended to limit the invention to the specific embodiments illustrated.

Embodiments provide for various methods and apparatus including mechanisms to enable low latency aperiodic channel state information. The mechanisms can involve aperiodic channel state information transmitted on a physical uplink control channel.

<FIG> is an exemplary block diagram of a system <NUM> according to a possible embodiment. The system <NUM> can include a wireless communication device <NUM>, such as User Equipment (UE), a base station <NUM>, such as an enhanced NodeB (eNB) or next generation NodeB (gNB), and a network <NUM>. The wireless communication device <NUM> can be a wireless terminal, a portable wireless communication device, a smartphone, a cellular telephone, a flip phone, a personal digital assistant, a personal computer, a selective call receiver, a tablet computer, a laptop computer, or any other device that is capable of sending and receiving communication signals on a wireless network.

The network <NUM> can include any type of network that is capable of sending and receiving wireless communication signals. For example, the network <NUM> 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 5th generation (<NUM>) network, a 3rd Generation Partnership Project (3GPP)-based network, a satellite communications network, a high altitude platform network, the Internet, and/or other communications networks.

Aperiodic CSI can be important for URLLC operation to provide timely feedback to adjust transmission parameters. As of now, ACSI can be triggered only by UL grant and would be transmitted on the physical uplink shared channel (PUSCH) scheduled by uplink (UL) grant.

It has been proposed to use DL grant to trigger CSI (to be transmitted on a PUCCH) to save control overhead in DL heavy operation (e.g., in case no PUSCH is to be scheduled).

If an UL grant schedules a PUSCH with repetitions, either via dynamic PUSCH repetition indication via the DCI of the UL grant 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 triggering the CSI report or in RRC configuration of the CSI report, the CSI report may need to be sent in a short time, and carrying on the PUSCH with multiple repetition may not satisfy the time the CSI report needs to be sent.

In the case of unlicensed operation, wherein a DCI can schedule multiple transport blocks (TBs) using different PUSCHs (possibly in different overlapping/non overlapping time spans), the CSI is sent on a second PUSCH/penultimate scheduled PUSCH. However, such transmission may not satisfy the timeline requirements of CSI for URLLC operation.

The present disclosure provides mechanisms to determine:.

Channel state information (CSI) is a feedback that a device can send to the network, which could help the network with selecting communication (such as scheduling) parameters for the device. Aperiodic CSI (A-CSI/ACSI) is a feedback provided by the device in response to a triggering event. A-CSI can be triggered by a DCI (control signal) sent by the network.

The procedures for aperiodic CSI reporting are described in details in TS <NUM>, <NUM>, <NUM>, and <NUM>.

CSI may consist one or more of (a) Channel Quality Indicator (CQI), (b) precoding matrix indicator (PMI), (c) CSI-reference signal (RS) resource indicator (CRI), (d) synchronization signals (SS)/physical broadcast channel (PBCH) Block Resource indicator (SSBRI), (e) layer indicator (LI), (f) rank indicator (RI), (<NUM>) L1-RSRP or (<NUM>) L1-SINR.

A UE can be configured by higher layers with N≥<NUM> CSI report configurations (CSIReportConfig Reporting Settings), M≥<NUM> CSI resource configurations (CSI-ResourceConfig Resource Settings), and at least one list of A-CSI trigger states (such as CSI-AperiodicTriggerStateList). Each configured trigger state (such as using the higher layer parameter CSI-AperiodicTriggerState) is associated with one or multiple CSI report configurations (CSI-ReportConfig) where each CSI-ReportConfig is linked to periodic, or semipersistent, or aperiodic resource setting(s).

Once a CSI report is triggered e.g., via a DCI,.

The UE, based on the triggered CSI report configuration(s) generates a CSI report, and sends it in a PUSCH (UL shared channel, such as the PUSCH scheduled by the DCI triggering the CSI report(s)). A parameter in the CSI report configuration indicates the parameters the UE is supposed to include in the CSI report (e.g., reportQuantity parameter can indicate CRI, rank indicators (RI), and channel quality indicators (CQI) should be reported).

Each CSI report setting/configuration can be associated with a single bandwidth part (BWP) for channel measurement, and contains the parameter(s) for one CSI reporting band.

Currently, ACSI can be triggered via an UL grant scheduling a PUSCH, with or without an UL-shared channel (SCH) (e.g., uplink data/UL transport block) in the PUSCH.

When the UE is scheduled to transmit a transport block and no CSI report, or the UE is scheduled to transmit a transport block and a CSI report(s) on PUSCH by a DCI, the Time domain resource assignment field value m of the DCI provides a row index m + <NUM> to an allocated table. The determination of the used resource allocation table is defined in Clause <NUM>. <NUM> of TS <NUM>. The indexed row defines the slot offset K2, the start and length indicator SLIV, or directly the start symbol S and the allocation length L, the PUSCH mapping type, and the number of repetitions (if numberofrepetitions is present in the resource allocation table) to be applied in the PUSCH transmission.

When the UE is scheduled to transmit a PUSCH with no transport block and with a CSI report(s) by a CSI request field on a DCI, the Time domain resource assignment field value m of the DCI provides a row index m + <NUM> to an allocated table which is defined by the higher layer configured pusch-TimeDomainAllocationList in pusch-Config. The indexed row defines the start and length indicator SLIV, and the PUSCH mapping type to be applied in the PUSCH transmission and the K2 value is determined as <MAT> where Yj, j = <NUM>,. ,NRep -<NUM> are the corresponding list entries of the higher layer parameter.

The UE determines the Offset X between the slot containing the DCI that triggers a set of aperiodic NZP CSI-RS resources and the slot in which the CSI-RS resource set is transmitted based on the aperiodicTriggeringOffset associated with the triggered ACSI report.

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

In an embodiment, the UE receives an UL grant triggering an aperiodic CSI report and scheduling a PUSCH transmission, the UL grant indicates at least one of the following:.

In a related embodiment, the UE receives an UL grant triggering an aperiodic CSI report and scheduling a PUSCH transmission; the UE determines to use a PUCCH resource instead of the PUSCH in case of occurrences of at least one of the following.

In a related embodiment, the CSI report triggered by an UL grant can be sent via a PUCCH if configured by the network; otherwise, the CSI report triggered by the UL grant should follow rules of previous 3GPP releases (e.g., ACSI to be sent on the PUSCH scheduled by the UL grant).

In a related embodiment, for the PUCCH scheduled by the UL grant, the PUCCH transmission time is determined based on a DCI field in the UL grant. In an example, the field chooses one value from a set of configured values/offsets. In an example, the set of values configured for PDSCH-to-HARQ_feedback timing can be used as the values for the set of configured values/offsets for CSI PUCCH timing (e.g., PDSCH-to-HARQ_feedback timing values can be directly used or a function of those PDSCH-to-HARQ_feedback timing values can be used). In one example, the PUCCH transmission time is determined based on the largest indicated offset value from a set of values (e.g., reportSlotOffsetList) configured for each CSI report corresponding to the triggered CSI state. The indication indicates the set element index and may be based on a DCI field (e.g., TDRA field value). The reportSlotOffsetList may be different for UL grant triggering CSI on PUCCH and UL grant triggering CSI on PUSCH.

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

In one example, the triggered CSI state comprises multiple CSI report configurations, and the PUCCH transmission time for carrying the triggered CSI report is determined based on the largest offset value from a set of offset values, wherein an offset value of the set of offset values corresponds to the configured offset list (e.g., reportSlotOffsetList as described in TS <NUM>) for the CSI report configuration of the multiple CSI report configurations, 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 for CSI on PUSCH with repetitions or slot aggregation. In another example, the UE is indicated based on a DCI field in the UL grant the number of repetitions for CSI on PUSCH with repetitions which can be less than the number of PUSCH repetitions.

In one example, the number of resources (e.g., REs) for CSI on PUSCH with repetitions may be based on the total number of repetitions for PUSCH and the number of repetitions for CSI. In one example, an offset term may be added to the beta-offset values (e.g., adjustment to the beta-offset values) for CSI (wherein beta-offset values can be beta-offsetACK, betaOffsetCSI-Part1, betaOffsetCSI-Part2 e.g., as defined in TS <NUM>/TS <NUM>) where the offset term may be based on the total number of repetitions for PUSCH and the number of repetitions for CSI. This may occur when the CSI report is on at least one but not all repetition (e.g., indicated by UL grant) of a PUSCH (e.g., UL grant schedules a PUSCH with repetitions).

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

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

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

A motivation for this embodiment could be the case of unlicensed operation, wherein a 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 PUSCH(s) to carry the CSI report.

In one example, the CSI report may be carried on the earliest PUSCH that meets the processing timeline requirements, e.g., the first symbol of the PUSCH should not occur before a certain time offset after the end of the reception of the last symbol of the PDCCH carrying the DCI scheduling the PUSCH (and triggering the ACSI report). In one example, the time offset for determining the PUSCH carrying CSI transmission is based on the largest indicated offset value from a set of values (e.g., reportSlotOffsetList) configured for each CSI report corresponding to the triggered CSI state. The indication indicates the set element index and may be based on a DCI field (e.g., TDRA field value).

<FIG> shows an example of a timing diagram <NUM>, which includes determining a PUSCH resource/transmission occasion/instance for CSI transmission amongst multiple scheduled PUSCHs by the DCI. In another example, the multiple PUSCHs are associated with a configured grant(s) and the DCI triggers the ACSI report.

More specifically, in <FIG> DCI schedules <NUM> PUSCHs (carrying different TBs); the DCI also triggers an ACSI report. In the illustrated example, the ACSI report is transmitted on the <NUM>nd PUSCH. CSI transmission time line requirement: CSI report transmission cannot be started earlier than T1 time (e.g., symbols/subslots/slots) after the end of the PDCCH carrying the DCI and cannot be finished later than T2 time (e.g., symbols/subslots/slots) after the end of the PDCCH carrying the DCI.

At least one motivation for enabling ACSI on a PUCCH scheduled by a DL assignment/grant can be to avoid sending an UL grant triggering ACSI when there is no UL data (TB) to be scheduled.

In <NUM>, the PUCCH transmit power is determined according to the following formula wherein different elements of the formula are described in TS <NUM>:
<MAT>.

In an embodiment, the UE receives a DL grant/assignment triggering an aperiodic CSI report and scheduling a 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.

<FIG> illustrates a timing diagram <NUM>. In <FIG>, 1st PUCCH (for ACSI) and 2nd PUCCH (for HARQ ACK) can have different transmission powers.

<FIG> illustrates a further timing diagram <NUM>. In <FIG>, <FIG>st PUCCH (for ACSI) and <NUM>nd PUCCH (for HARQ ACK) can have different transmission powers. The DCI carries at least TPC command.

<FIG> illustrates a still further timing diagram <NUM>. In <FIG>, 1st PUCCH (for ACSI) and 2nd PUCCH (for HARQ ACK) can have different transmission powers; DCI schedules PDSCH, and some UL resources occur somewhere in the middle of the group of DL symbols for the PDSCH.

In a related embodiment, the UE determines the first and the second PUCCH transmission powers based on a single field in the DCI (e.g., <NUM>-bit TPC command for scheduled PUCCH as used in DCI format <NUM>-<NUM>) e.g., the same TPC command is applied to both PUCCHs (<NUM>st PUCCH and <NUM>nd PUCCH).

In a related embodiment, the PUCCH power control adjustment state is the same for both PUCCHs (<NUM>st PUCCH and <NUM>nd PUCCH).

In a related embodiment, the transmit power of the first PUCCH is derived based on the TPC command and an offset to at least one parameter determining the transmit power of the second PUCCH: e.g., ΔF PUCCH (F) for the first PUCCH is derived as follows: ΔF PUCCH (F)for the second PUCCH plus an offset 'D' when both PUCCHs use the same PUCCH format. In an example, 'D' is configured by higher layers. In at least one example, 'D' is configured by higher layers for each PUCCH format.

In a related embodiment, the transmit power of the first PUCCH is derived based on an offset term added to the Po_PUCCH. The offset term may be configured by higher layers. Po ΔF PUCCH without any offset is used for the second PUCCH.

In an embodiment, the UE receives an UL grant/assignment triggering an aperiodic CSI report and scheduling a PUSCH transmission (e.g., the PUSCH includes UL TB and/or non-low latency CSI (a CSI that is due later than the low-latency CSI); both low-latency and non-low-latency CSIs are triggered by the UL grant). The UE determines a PUCCH resource for ACSI transmission.

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

More specifically, <FIG> corresponding to table <NUM>. <NUM>-<NUM> in TS <NUM> illustrates a table <NUM>, which includes a mapping of TPC Command Field in a DCI format scheduling a PUSCH transmission, or in DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, or in DCI format 2_3 to absolute and accumulated δPUSCH,b,f,c values or δSRS,b,f,c values. Alternatively, <FIG> corresponding to table <NUM>. <NUM>-<NUM> in TS <NUM> illustrates a table <NUM>, which includes a mapping of TPC Command Field in DCI format 1_0 or DCI format 1_1 or DCI format 2_2 with CRC scrambled by TPC-PUCCH-RNTI to accumulated δPUCCH,b,f,c values.

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

In an embodiment, when a DL grant triggers ACSI and schedules a PDSCH transmission, the UE multiplexes the HARQ-ACK corresponding to the PDSCH and the CSI report corresponding to the triggered ACSI onto a PUCCH resource indicated by the DL grant when.

In a related embodiment, if the above condition is not satisfied, the UE determines a second PUCCH resource, and transmits the HARQ-ACK corresponding to the PDSCH on the first PUCCH and the report corresponding to the triggered ACSI on the second PUCCH resource.

In one example, the PUCCH resource indicator in the DCI may indicate a pair (first, second) of PUCCH resources (e.g., indicates an element of PUCCH resource list associated with two values of PUCCH resource ID). In another example, the first PUCCH resource is indicated by the PUCCH resource indicator value (index within the higher layer configured PUCCH resource list). The second PUCCH resource is determined as the next (e.g., PUCCH resource indicator value+<NUM> modulo max number of PUCCH resources in PUCCH resource set) PUCCH resource in the PUCCH resource list configured by higher layers. In another example, the second PUCCH resource is determined as a configured/fixed number 'b' (e.g., PUCCH resource indicator value+'b' modulo max number of PUCCH resources in PUCCH resource set) PUCCH resource in the PUCCH resource list configured by higher layers. Embodiment 3a: In an embodiment, when a DL grant triggers ACSI and schedules a PDSCH transmission, in case different PUCCH resources are used for HARQ-ACK transmission corresponding to the PDSCH and for the triggered ACSI transmission, the UE is not expected to receive/determine overlapping PUCCH resources in time corresponding to the HARQ-ACK and the triggered CSI. In an example, the indicated K1 value (PDSCH-to-HARQ_feedback timing indicator) and the determined/indicated KCSI value (e.g., a PDDCH/PDSCH-to-CSI feedback timing) are not expected to result in overlapping PUCCHs in time domain on the same carrier.

In an embodiment, when an UL grant/assignment triggers ACSI and schedules a PUSCH transmission, in case a PUCCH resource is determined to convey the ACSI and a PUSCH resource/transmission occasion is allocated for UL data transmission, the UE is not expected to be allocated overlapping PUCCH and PUSCH resources in time.

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

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

In an embodiment, ACSI transmitted on PUCCH is restricted to use certain PUCCH formats (e.g., PUCCH format <NUM> or PUCCH format <NUM>; e.g., depending on the PUCCH payload size). The PUCCH format to use 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 purpose (multiplexing multiple UCIs e.g., HARQ ACK/SR/CSI or multiplexing different UCIs of different component carriers/BWPs), it may be better to determine the PUCCH format to be used.

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

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

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

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

In an embodiment, CSI report configurations associated with an A-CSI trigger state 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 report configuration.

In an embodiment, ACSI can be triggered via DL DCI with a DCI format if the DCI is received in a predetermined subset of search spaces/CORESETs.

In an embodiment, ACSI can be triggered via DL/UL DCI with a DCI format with a determined/indicated PUCCH resource if the DCI is received in a predetermined subset of search spaces/CORESETs. For instance, if DCI format <NUM>-<NUM> is received in search space/CORESET A, there is a field in the DCI to indicate the PUCCH resource for ACSI transmission, and if DCI format <NUM>-<NUM> is received in search space/CORESET B, ACSI cannot be triggered by DCI format <NUM>-<NUM>. In another example, if DCI format <NUM>-<NUM> is received in search space/CORESET A, there is a field in the DCI to indicate the PUCCH resource for ACSI transmission, and if DCI format <NUM>-<NUM> is received in search space/CORESET B (and scheduling a PUSCH), the triggered ACSI is transmitted on the scheduled PUSCH.

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

In an embodiment, the UE indicates in a PUCCH resource associated with the triggered ACSI report, whether the ACSI report is included in the PUCCH or not. One motivation of this embodiment is that the gNB by triggering the ACSI report wants to check if a significant update to scheduling is needed, and if so what would be a good MCS/CQI. Sometimes the most recently used MCS is fine to use, especially given transmission of a transport block with small size and with low BLER target for URLLC operation.

In an embodiment, a triggered CSI state comprises at most 'M' CSI report configurations, and 'M' is a UE capability (higher layer signal) for low latency/high priority operation (wherein high priority CSI report is in comparison to a CSI report with low priority; wherein the priority (high vs. low) can be used to decide which CSI report to be dropped in case of collision of different CSI reports associated with different priorities (high vs. low, and the CSI report associated with low priority can be dropped)). In an example, the priority (high vs. low or e.g., priority index '<NUM>' vs. priority index '<NUM>') is configured as part of the CSI report configuration.

In another example, the priority for a CSI report is derived at least based on an RRC parameter of the CSI report configuration (e.g., a priority index configured for the CSI report configuration) and priority rules similar to those defined in section <NUM>. <NUM> of TS <NUM>. In one example, CSI reports with high priority indication (RRC parameter of the CSI report configuration (e.g., a priority index configured for the CSI report configuration)) have higher priority compared to those CSI reports with 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 priority indication (no priority index configured for the CSI report configuration); and within high priority CSI reports, priority rules similar to those defined in section <NUM>. <NUM> of TS <NUM> are applicable; and within low priority CSI reports, priority rules similar to those defined in section <NUM>. <NUM> of TS <NUM> are applicable.

In one example, instead of ACSI in the embodiments described, semipersistent CSI can be used (e.g., triggered by DL DCI).

In accordance with at least some of the embodiments, one or more of the following can be supported:.

<FIG> illustrates a flow diagram <NUM> in a user equipment for triggering and scheduling the transmission of an ACSI report. In accordance with at least one embodiment, the method can include receiving <NUM> a downlink (DL) grant triggering an aperiodic channel state information (ACSI) report and scheduling 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) acknowledgment (ACK) transmission corresponding to the scheduled PDSCH can be determined <NUM>. A first PUCCH transmission power for the ACSI transmission using the first PUCCH resource and a second transmission power for the HARQ ACK transmission using the second PUCCH resource can be determined <NUM> based on downlink control information (DCI) of the DL grant.

In some instances, the first PUCCH resource can end earlier than the second PUCCH resource.

In some instances, the first PUCCH resource can be transmitted on a carrier that is different than a carrier on which the second PUCCH resource is transmitted.

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

In some instances, the ACSI report and corresponding determination of the first PUCCH resource for ACSI transmission can be triggered in absence of an uplink grant.

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 for use with 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 one of the first PUCCH transmission power and the second PUCCH transmission power can be derived based on an adjusted TPC, where the adjusted TPC can include a value in which at least one parameter of the TPC has had a predetermined offset applied. In some of these instances, the at least one parameter can include a Po_PUCCH parameter, where the predetermined offset can be applied to the value of the parameter in deriving the first PUCCH transmission power.

In some instances, the first PUCCH resource can be selected to be 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 an expiration of a predetermined latency requirement for the ACSI report.

In some instances, a start of the first PUCCH resource can occur before the end of the PDSCH transmission.

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

<FIG> illustrates a flow diagram <NUM> in a network entity for triggering and scheduling the reception of an ACSI report. In accordance with at least one embodiment, the method can include transmitting <NUM> a downlink (DL) grant to a particular user equipment triggering an aperiodic channel state information (ACSI) report and scheduling a physical downlink shared channel (PDSCH) transmission. An ACSI transmission via a determined first physical uplink control channel (PUCCH) resource and a hybrid automatic repeat request (HARQ) acknowledgment (ACK) transmission via a determined second PUCCH resource, which each correspond to the scheduled PDSCH can then be received <NUM>, where a first PUCCH transmission power for the ACSI transmission can be determined using the first PUCCH resource and a second transmission power for the HARQ ACK transmission can be determined using the second PUCCH resource based on downlink control information (DCI) of the DL grant <NUM>.

A Further embodiment can include a method in the user equipment (UE), where the method can include receiving an uplink (UL) grant triggering an aperiodic channel state information (ACSI) report and scheduling 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) a particular PUCCH resource upon which the ACSI report is to be sent when the ACSI report is to be sent on the PUCCH.

A still further embodiment can include a method in the user equipment, where the method can include receiving an uplink (UL) grant triggering an aperiodic channel state information (ACSI) report and scheduling at least two physical uplink shared channel (PUSCH) transmissions. Downlink control information (DCI) can indicate on which one of the at least two PUSCH transmissions, the ACSI report should be carried.

<FIG> is an example block diagram of an apparatus <NUM>, such as the wireless communication device <NUM>, according to a possible embodiment. The apparatus <NUM> can include a housing <NUM>, a controller <NUM> within the housing <NUM>, audio input and output circuitry <NUM> coupled to the controller <NUM>, a display <NUM> coupled to the controller <NUM>, a transceiver <NUM> coupled to the controller <NUM>, an antenna <NUM> coupled to the transceiver <NUM>, a user interface <NUM> coupled to the controller <NUM>, a memory <NUM> coupled to the controller <NUM>, and a network interface <NUM> coupled to the controller <NUM>. The apparatus <NUM> can perform the methods described in all the embodiments.

The display <NUM> 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. The transceiver <NUM> can include a transmitter and/or a receiver. The audio input and output circuitry <NUM> can include a microphone, a speaker, a transducer, or any other audio input and output circuitry. The user interface <NUM> can include a keypad, a keyboard, buttons, a touch pad, a joystick, a touch screen display, another additional display, or any other device useful for providing an interface between a user and an electronic device. The network interface <NUM> can be a Universal Serial Bus (USB) port, an Ethernet port, an infrared transmitter/receiver, an IEEE <NUM> port, a WLAN transceiver, or any other interface that can connect an apparatus to a network, device, or computer and that can transmit and receive data communication signals. The memory <NUM> can include a random access memory, a read only memory, an optical memory, a solid state memory, a flash memory, a removable memory, a hard drive, a cache, or any other memory that can be coupled to an apparatus.

The apparatus <NUM> or the controller <NUM> may implement any operating system, such as Microsoft Windows®, UNIX®, or LINUX®, Android™, or any other operating system. Apparatus operation software may be written in any programming language, such as C, C++, Java or Visual Basic, for example. Apparatus software may also run on an application framework, such as, for example, a Java® framework, a. NET® framework, or any other application framework. The software and/or the operating system may be stored in the memory <NUM> or elsewhere on the apparatus <NUM>. The apparatus <NUM> or the controller <NUM> may also use hardware to implement disclosed operations. For example, the controller <NUM> may be any programmable processor. Disclosed embodiments may also be implemented on a general-purpose or a special purpose computer, a programmed microprocessor or microcontroller, peripheral integrated circuit elements, an application-specific integrated circuit or other integrated circuits, hardware/electronic logic circuits, such as a discrete element circuit, a programmable logic device, such as a programmable logic array, field programmable gate-array, or the like. In general, the controller <NUM> may be any controller or processor device or devices capable of operating an apparatus and implementing the disclosed embodiments. Some or all of the additional elements of the apparatus <NUM> can also perform some or all of the operations of the disclosed embodiments.

While this disclosure has been described with specific embodiments thereof, it is evident that 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 the other embodiments. Also, all of the elements of each figure are not necessary for operation of the disclosed embodiments. For example, one of ordinary skill in the art of the disclosed embodiments would be enabled to make and use the teachings of the disclosure by simply employing the elements of the independent claims. Accordingly, embodiments of the disclosure as set forth herein are intended to be illustrative, not limiting.

Claim 1:
A method (<NUM>) in a user equipment, the method (<NUM>) comprising:
receiving (<NUM>) a downlink grant triggering an aperiodic channel state information, ACSI, report and scheduling a physical downlink shared channel, PDSCH, transmission;
determining (<NUM>) a first physical uplink control channel, PUCCH, resource for ACSI transmission and a second PUCCH resource for hybrid automatic repeat request, HARQ, acknowledgment, ACK, transmission corresponding to the scheduled PDSCH; and
determining (<NUM>) a first PUCCH transmission power for the ACSI transmission using the first PUCCH resource and a second transmission power for the HARQ ACK transmission using the second PUCCH resource based on downlink control information, DCI, of the downlink grant.