Signaling aspects of aperiodic CSI reporting triggered by downlink grants

Abstract

Various aspects of the present disclosure provide techniques for configuring and triggering aperiodic channel state information (A-CSI) reporting via downlink grants. As will be described in more detail below, A-CSI reports may be transmitted via a physical uplink control channel (PUCCH).

Description

Technical Field

[0001] Aspects of the present disclosure relate to wireless communications and, more particularly, to techniques for configuring and triggering aperiodic channel state information (A-CSI) reporting. Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, etc. These wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access systems include 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, Advanced LTE (LTE-A) systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, to name a few.

[0003] In some examples, a wireless multiple access communication network may include multiple base stations (BSs), each of which is capable of simultaneously supporting communications for multiple communication devices (also referred to as user equipment (UE)). In an LTE or LTE-A network, a set of one or more base stations may define an evolved Node B (eNB). In other examples (e.g., in a next generation, new radio (NR) or 5G network), a wireless multiple access communication system may include multiple distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmit receive points (TRPs), etc.) communicating with multiple central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), wherein a set of one or more DUs communicating with a CU may define an access node (e.g., which may be referred to as a BS, a next generation Node B (gNB or gNodeB), a TRP, etc.). A BS or DU may communicate with a set of UEs on a downlink channel (e.g., for transmission from a BS or DU to a UE) and an uplink channel (e.g., for transmission from a UE to a BS or DU).

[0004] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at municipal, national, regional and even global levels. New radio (e.g., 5G NR) is an example of an emerging telecommunication standard. NR is a collection of enhancements to the LTE mobile standard released by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, reducing costs, improving services, utilizing new spectrum, and using OFDMA with cyclic prefix (CP) on downlink (DL) and uplink (UL) to better integrate with other open standards. To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0005] As the demand for mobile broadband access continues to increase, there is a need for further improvements to NR and LTE technologies. Preferably, these improvements should be applicable to other multiple access technologies and the telecommunication standards that employ these technologies. Summary of the invention

[0006] The systems, methods, and devices of the present disclosure each have several aspects, no single aspect of which is solely responsible for its desirable attributes. Without limiting the scope of the present disclosure as expressed by the claims that follow, some features will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled "Detailed Description," those skilled in the art will understand how the features of the present disclosure provide advantages including improved utilization of transmission resources.

[0007] Certain aspects provide a method for wireless communications by a user equipment. The method generally includes: obtaining information about a set of one or more configurations for aperiodic channel state information (A-CSI) reporting on a physical uplink control channel (PUCCH); receiving downlink control information (DCI) for a downlink grant, the downlink control information (DCI) including at least one field for triggering an A-CSI report on the PUCCH; generating an A-CSI report based on one of the set of A-CSI report configurations selected based on a field in the DCI; and sending the CSI report on the PUCCH.

[0008] Certain aspects provide a method for wireless communications by a network entity. The method generally includes: sending information about a set of one or more configurations for aperiodic channel state information (A-CSI) reporting on a physical uplink control channel (PUCCH) to a UE; sending first downlink control information (DCI) for a downlink grant to the UE, the first downlink control information (DCI) including at least one field for triggering an A-CSI report on the PUCCH; and receiving a PUCCH from the UE carrying an A-CSI report, the A-CSI report being generated based on one of the set of A-CSI reporting configurations selected based on a field in the DCI.

[0009] Aspects of the present disclosure provide components, apparatuses, processors, and computer-readable media for performing the methods described herein.

[0010] To achieve the foregoing and related ends, one or more aspects include features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] A more particular description of what has been briefly summarized above may be obtained by reference to the various aspects of some of them shown in the accompanying drawings, so that the manner in which the above-mentioned features of the present disclosure are understood in detail. It should be noted, however, that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered limiting of its scope, as the description may admit of other equally effective aspects.

[0012] Figure 1 is a block diagram conceptually illustrating an example telecommunications system in which certain aspects of the present disclosure may be implemented.

[0013] Figure 2 is a block diagram conceptually illustrating designs of example base stations (BSs) and user equipment (UEs) in which certain aspects of the present disclosure may be implemented.

[0014] Figure 3 An example CSI reporting configuration is shown.

[0015] Figure 4 is a diagram illustrating example resources for A-CSI transmission.

[0016] Figure 5 Example operations for wireless communications by a user equipment are shown in accordance with various aspects of the present disclosure.

[0017] Figure 6Example operations for wireless communications by a network entity are shown in accordance with various aspects of the present disclosure.

[0018] Figure 7 is a diagram illustrating example resources for A-CSI transmission in accordance with various aspects of the present disclosure.

[0019] Figures 8 to 10 Examples of transmit power control (TPC) for A-CSI reporting in accordance with various aspects of the present disclosure are shown.

[0020] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized on other aspects without specific recitation. DETAILED DESCRIPTION

[0021] Various aspects of the present disclosure provide techniques for configuring and triggering aperiodic channel state information (A-CSI) reporting via downlink grants. As will be described in more detail below, A-CSI reports may be transmitted via a physical uplink control channel (PUCCH), which may enable faster A-CSI reporting than A-CSI reports sent on a physical uplink shared channel (PUSCH). This may provide more up-to-date CSI information to a network entity (e.g., a base station), which in turn may help optimize DL scheduling.

[0022] The following description provides examples, but does not limit the scope, applicability or examples set forth in the claims. The functions and arrangements of the elements discussed may be changed without departing from the scope of the present disclosure. Various examples may omit, replace or add various processes or components as appropriate. For example, the described method may be performed in an order different from the order described, and individual steps may be added, omitted or combined. In addition, the features described in some examples may be combined in certain other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functions, or structures and functions other than the various aspects of the present disclosure set forth herein or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be implemented by one or more elements of the claims. The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" in this article is not necessarily interpreted as preferred or more advantageous than other aspects.

[0023] Typically, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific radio access technology (RAT) and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, subcarrier, frequency channel, tone, subband, etc. Each frequency can support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, 5G NR RAT networks can be deployed.

[0024] Figure 1 An example wireless communication network 100 is shown in which aspects of the present disclosure may be performed. For example, one or more UEs 120 in the network 100 may be configured to perform Figure 5 Operation 500 to generate an A-CSI report triggered by a downlink grant and sent on the PUCCH. Similarly, the base station 110 (e.g., gNB) in the network 100 can be configured to perform Figure 6 Operation 600 of the embodiment may be used to configure and trigger the UE 120 (performing operation 500) to generate an A-CSI report and send the A-CSI report on the PUCCH.

[0025] like Figure 1 As shown, the wireless communication network 100 may include several base stations (BSs) 110a-z (each also individually referred to herein as BS 110 or collectively referred to as BS 110) and other network entities. BS 110 may provide communication coverage for a particular geographic area, which is sometimes referred to as a "cell", which may be stationary or may move depending on the location of the mobile BS 110. In some examples, BS 110 may be interconnected to each other and / or to one or more other BSs or network nodes (not shown) in the wireless communication network 100 through various types of backhaul interfaces (e.g., direct physical connections, wireless connections, virtual networks, etc.) using any suitable transport network. Figure 1 In the example shown, BSs 110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x may be a pico BS for pico cell 102x. BSs 110y and 110z may be femto BSs for femto cells 102y and 102z, respectively. A BS may support one or more cells. BS 110 communicates with user equipment (UE) 120a-y (each also individually referred to herein as UE 120 or collectively referred to as UE 120) in wireless communication network 100. UE 120 (e.g., 120x, 120y, etc.) may be dispersed throughout wireless communication network 100, and each UE 120 may be stationary or mobile.

[0026] The wireless communication network 100 may also include a relay station (e.g., relay station 110r) (also referred to as a relay, etc.) that receives transmissions of data and / or other information from an upstream station (e.g., BS 110a or UE 120r) and sends transmissions of the data and / or other information to a downstream station (e.g., UE 120 or BS 110), or which relays transmissions between UEs 120 to facilitate communication between devices.

[0027] A network controller 130 may couple to a set of BSs 110 and provide coordination and control for these BSs 110. The network controller 130 may communicate with the BSs 110 via a backhaul. The BSs 110 may also communicate with each other (eg, directly or indirectly) via a wireless or wired backhaul.

[0028] Figure 2 It is shown (for example, Figure 1 1 and 120 in the wireless communication network 100 of the present invention, which can be used to implement various aspects of the present disclosure. For example, the antenna 252, the processor 266, 258, 264 and / or the controller / processor 280 of the UE 120 can be configured to perform Figure 5 Similarly, antenna 234, processors 220, 230, 238 and / or controller / processor 240 of BS 110 may be configured to perform Figure 6 Operation 600.

[0029] At BS 110, a transmit processor 220 may receive data from a data source 212 and control information from a controller / processor 240. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GCPDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. The processor 220 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor 220 may also generate reference symbols, such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS). If applicable, a transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols, and may provide output symbol streams to modulators (MODs) 232a-232t. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a-232t may be transmitted via antennas 234a-234t, respectively.

[0030] At UE 120, antennas 252a-252r can receive downlink signals from BS 110 or parent IAB nodes, or child IAB nodes can receive downlink signals from parent IAB nodes, and can provide received signals to demodulators (DEMODs) in transceivers 254a-254r, respectively. Each demodulator 254 can adjust (e.g., filter, amplify, downconvert, and digitize) the corresponding received signal to obtain input samples. Each demodulator can further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 can obtain received symbols from all demodulators 254a-254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. Receive processor 258 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control information to controller / processor 280.

[0031] On the uplink, at the UE 120 or child IAB node, the transmit processor 264 may receive and process data from the data source 262 (e.g., for a physical uplink shared channel (PUSCH) or PSSCH) and control information from the controller / processor 280 (e.g., for a physical uplink control channel (PUCCH) or PSSCH). The transmit processor 264 may also generate reference symbols for reference signals (e.g., for a sounding reference signal (SRS)). The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266 (if applicable), further processed by the demodulators in the transceivers 254a-254r (e.g., for SC-FDM, etc.), and transmitted to the BS 110 or parent IAB node.

[0032] At BS 110 or a parent IAB node, uplink signals from UE 120 may be received by antenna 234, processed by modulator 232, detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 may provide decoded data to a data sink 239 and decoded control information to controller / processor 240.

[0033] Controllers / processors 240 and 280 may direct the operation at BS 110 and UE 120, respectively. Controller / processor 240 and / or other processors and modules at BS 110 may perform or direct the execution of processes for the techniques described herein. Controller / processor 280 and / or other processors and modules at UE 120 may perform or direct the execution of processes for the techniques described herein. Memories 242 and 282 may store data and program codes for BS 110a and UE 120a, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink and / or uplink.

[0034] Example signaling aspects of A-CSI triggered by DL grant

[0035] In a new radio (NR) deployment, a UE may support communications (traffic) with various service types. For example, a NR UE may support enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or more), millimeter wave (mmW) targeting high carrier frequency (e.g., 25 GHz or more), massive machine type communications MTC (mMTC) targeting non-backward compatible MTC technology, and / or mission critical communications targeting ultra-reliable low latency communications (URLLC).

[0036] The general goal of CSI reporting by the UE is to help ensure that the gNB has current information about channel conditions. In some cases, the UE may need to report CSI information as quickly as possible to ensure that the gNB has the latest information. In order to better serve different types of services, the UE may have some specific configurations for CSI reporting. For example, in NR (Release 15 and 16), the base station may schedule the UE to send aperiodic CSI reports (A-CSI) on the PUSCH using UL grants to provide current CSI information.

[0037] Figure 3 An example of an aperiodic CSI reporting configuration is shown. The CSI reporting configuration may have different parameters, for example, to implement the various types of restrictions discussed above with respect to URLLC CSI reporting.

[0038] like Figure 3 As shown, the UE may be configured with a set of (N1) CSI reporting configurations. In some cases, the UE may receive (via RRC signaling) a CSI-AperiodicTriggerStateList that identifies the CSI reporting configuration. Each CSI reporting configuration may be associated with one or more (e.g., up to 3) of the M CSI resource configurations. The CSI resources may be in one or more of the K bandwidth parts (BWPs).

[0039] As shown in the figure, the uplink DCI (UL grant) received by the UE can trigger A-CSI reporting on PUSCH according to one of N1 CSI reporting configurations (CSI-Reportconfig). The code point in the UL DCI can select which of the N1 CSI reporting configurations is selected.

[0040] Figure 4 is a diagram showing example resources for A-CSI transmission. As shown, one or more parameters may indicate the timing for CSI-RS resources and corresponding PUSCH to carry A-CSI reports (as uplink control information UCI). For example, a first scheduling offset X may indicate the gap (in terms of time slots) between the PDCCH carrying the DCI triggering the A-CSI report and the CSI-RS. A second scheduling offset Y may indicate the gap between the PDCCH and the A-CSI report (UCI) on the PUSCH.

[0041] Scheduling offset X may be RRC configured, while scheduling offset Y may be signaled by reusing the time domain resource allocation (TDRA) field in the UL grant for the corresponding PUSCH transmission. The frequency domain resources for A-CSI sent on PUSCH may also be indicated in the UL grant, for example, via the frequency domain resource allocation (FDRA) field.

[0042] As described above, in some cases, aspects of the present disclosure may allow DL grants to trigger aperiodic CSI reporting on PUCCH. As described above, this may enable faster A-CSI reporting than A-CSI reporting on PUSCH, providing the base station with more up-to-date CSI information to assist in DL scheduling.

[0043] The following description provides an example signaling mechanism for configuring CSI triggering status for A-CSI reporting on PUCCH, indicating CSI-RS resources for measurement, time and frequency resources for sending A-CSI on PUCCH.

[0044] Figure 5 Example operations 500 for wireless communications by a user equipment (UE) are shown in accordance with aspects of the present disclosure. For example, operations 500 may be performed by Figure 1 and Figure 2 The UE 120 shown in FIG. 1 performs to generate an A-CSI report triggered by a DL grant and to send the A-CSI report on the PUCCH.

[0045] Operations 500 begin at 502 by obtaining information about a set of one or more configurations for aperiodic channel state information (A-CSI) reporting on a physical uplink control channel (PUCCH). At 504, the UE receives downlink control information (DCI) for a downlink grant, which includes at least one field for triggering an A-CSI report on the PUCCH. At 506, the UE generates an A-CSI report based on one A-CSI reporting configuration from the set of A-CSI reporting configurations, selected based on a field in the DCI. At 508, the UE sends the CSI report on the PUCCH.

[0046] Figure 6 600 are shown for wireless communications by a network entity in accordance with aspects of the present disclosure. For example, operations 600 may be performed by Figure 1 and Figure 2 BS 110 (e.g., gNB) shown in FIG. 1 performs to trigger UE 120 (perform Figure 5 Operation 500) generates an A-CSI report and sends the A-CSI report on the PUCCH.

[0047] Operations 600 begin at 602 by sending information about a set of one or more configurations for aperiodic channel state information (A-CSI) reporting on a physical uplink control channel (PUCCH) to a UE. At 604, first downlink control information (DCI) for a downlink grant is sent to the UE, which includes at least one field for triggering an A-CSI report on the PUCCH. At 606, a PUCCH carrying an A-CSI report is received from the UE, the A-CSI report being generated based on one of the set of A-CSI reporting configurations selected based on a field in the DCI.

[0048] Figure 7 is a diagram illustrating an example of A-CSI reporting triggered by a DL grant (DL scheduling DCI) sent on a PUCCH according to various aspects of the present disclosure.

[0049] In some cases, the DL grant may also include a bit indicating whether the DCI actually also schedules DL data transmission. In other words, the DCI may only be used to trigger A-CSI reporting without scheduling downlink data transmission. In this case, the base station may set this bit to zero to indicate that no data is to be scheduled by the DL grant.

[0050] In some cases, the A-CSI request field may be provided in a DL grant to trigger an A-CSI report on the PUCCH. The UE may be configured with a list of CSI report configurations per DL serving cell (or per DL BWP). Each code point of the A-CSI request field (except the all-zero code point) may indicate a specific A-CSI report configuration for one or more CSI resources included in the corresponding DL serving cell or DL ​​BWP. For example, in the case where A-CSI is triggered by a UL grant, the all-zero code point may indicate that no A-CSI report is requested by the DL grant.

[0051] In case of configuring the list of CSI report configurations per serving cell, the UE may not expect to be triggered with a CSI report corresponding to a CSI resource of an inactive BWP for the serving cell. In other words, the CSI resources for A-CSI reports triggered by DL grants should be on the same BWP as the corresponding PDSCH data. In case of cross-carrier DL scheduling, codepoints (except all-zero codepoints) may be associated with CSI resources on the scheduled cell (on which data transmission is scheduled).

[0052] In NR (Release 15 or 16), an RRC parameter "reportConfigType" is configured for each CSI reporting configuration, which takes one of the following types: Periodic, SemiPersistentOnPUSCH, SemiPersistentOnPUCCH, or Aperiodic. Various aspects of the present disclosure propose a new CSI reporting configuration type (e.g., which may be referred to as AperiodicOnPUCCH) to indicate that the current CSI reporting configuration is for aperiodic CSI reporting on PUCCH (triggered by DL grant).

[0053] For a CSI reporting configuration configured with a new CSI reporting configuration type, the following new RRC parameters may be configured:

[0054] A-CSI reporting offset (i.e., Figure 7 The scheduling offset Y in ; and

[0055] PUCCH resources per UL BWP.

[0056] When the DCI selects a CSI reporting configuration with a new CSI reporting configuration type, the UE will use the "A-CSI reporting offset" parameter to determine in which timeslot the PUCCH carrying the A-CSI report is to be sent. The UE will also use the PUCCH resources configured for the active UL BWP as the PUCCH resources to send the PUCCH carrying the A-CSI report in the determined timeslot. In some cases, the CSI reporting configuration setting with this new configuration type (AperiodicOnPUCCH) can only be triggered by a DL grant (not by a UL grant).

[0057] In some cases, one CSI resource setting may be associated with both UL grant and DL grant. In this case, the trigger offset ( Figure 7 A new RRC parameter (scheduling offset X) is introduced, which is used when the CSI resources are triggered by a DL grant (for example, the parameter can be called aperiodicTriggeringOffsetByDL_DCI (aperiodic triggering offset by DL_DCI)).

[0058] In some cases, one or more parameters may be indicated dynamically. For example, a DL grant may contain one or more of the following fields for indicating the PUCCH for HARQ-ACK feedback:

[0059] PUCCH Resource Indication (PRI), which indicates the PUCCH resources used to send HARQ-ACK feedback; and

[0060] PDSCH-to-HARQ_Feedback timing indicator (eg, K1 indicator) indicating the PUCCH on which to send HARQ-ACK (eg, Figure 7 shown) time slot.

[0061] As an alternative to using RRC configured parameters, the base station may dynamically indicate to the UE the A-CSI reporting slot and / or PUCCH resources for carrying A-CSI.

[0062] For example, for the reporting slot ( Figure 7 In some cases, a separate set of Y values ​​may be configured for each CSI report configuration. Alternatively, the same set of Y values ​​may be configured for all CSI report configurations. Another option is that the base station reuses some other existing fields in the DCI format to indicate the scheduling offset Y (e.g., the TDRA or FDRA field). The method of signaling a value set (whether the same set is configured for all CSI report configurations or a separate set is configured for each CSI report configuration) and selecting a value in the set via RRC signaling may also be applied to other options discussed herein for indicating a timeslot offset (e.g., adding a new field in the DCI, reusing the K1 field, or reusing other fields such as the TDRA or FDRA).

[0063] For the PUCCH resources used to send A-CSI reports, the base station can reuse the PUCCH resource indicator (PRI) field for PUCCH of HARQ-ACK when HARQ-ACK and A-CSI reports are sent in different time slots. Another option is that the base station uses a new PRI field to indicate the PUCCH resources used for A-CSI reports. Yet another option is that the base station reuses another other existing field in the DCI format to indicate the PUCCH resources (e.g., FDRA or TDRA).

[0064] Figures 8 to 10 An example of transmit power control (TPC) for A-CSI reporting according to various aspects of the present disclosure is shown. Figures 8 to 10In the formula, g(L), L=0, 1, 2, ..., represents a closed-loop power control adjustment state for a PUCCH transmission opportunity L. The adjustment state is determined based on a TPC command received in one or more DCIs. And the total transmit power of the PUCCH is determined at least in part based on the closed-loop power control adjustment state.

[0065] DL grants typically contain a 2-bit TPC field, which is used to indicate the transmit power of the PUCCH used to carry HARQ-ACK feedback. In some cases, when A-CSI reporting on PUCCH is also triggered by DL grants, the same (existing) TPC field (δ 1 ) can be applied to PUCCH transmission for HARQ-ACK and PUCCH transmission for A-CSI reporting (such as Figure 8 Both as shown in option 1).

[0066] As an alternative, Figure 8 As shown in Option 2 in FIG. 1 , separate TPC fields can be configured for power control for HARQ-ACK and A-CSI. As shown in the figure, compared with HARQ-ACK, the power control for A-CSI (δ 2 ) can be interpreted as the additional power (δ 1 +δ 2 the sum of ).

[0067] like Fig. 9 As shown, in NR (Release 15 / 16), when the UE calculates the closed-loop power control adjustment state for PUCCH transmissions scheduled by DCI, it only accumulates the TPC received before the last symbol corresponding to the DL grant. In the example shown, for the first HARQ-ACK transmission, although the PUCCH carrying the second TPC command δ is received before sending the PUCCH carrying the first HARQ-ACK transmission 2 DL authorization, but the second TPC command δ is not applied 2 (Although the UE applies the TPC received in the current DL grant).

[0068] One consideration for A-CSI triggered by DL grant is whether the UE should accumulate TPC commands received after the DL grant. Fig.10 As shown in , one option (shown as option a) is that the UE only applies the TPC command received before the last symbol of the DL grant scheduling A-CSI. In this case, the closed power control adjustment state g(3) for the PUCCH transmission carrying the A-CSI report does not include the TPC command due to the second TPC command δ 2Another option (shown as option b) is for the UE to apply the TPC command received up to K OFDM symbols before sending A-CSI on the PUCCH. For example, K can be set to:

[0069]

[0070] Where K 2,min represents the minimum k2 value configured for the active UL BWP of the serving cell, and Indicates the number of symbols per time slot. Fig.10 In the example shown in FIG. 1 , according to option b, since the second TPCδ 2 The UE receives more than K symbols before the PUCCH carrying the A-CSI report is sent, so the UE includes / adds δ in the closed-loop power control adjustment state. 2 .

[0071] In NR, the base station can use the group-common DCI format 2_2 scrambled with TPC-PUCCH-RNTI to signal the power control for PUCCH transmission. The group-common DCI can contain multiple power control fields in the following form:

[0072] Block number 1, block number 2, block number 3, ..., block number N,

[0073] Where each block number corresponds to a TPC command for a specific UE. Each UE may be configured with a block number index via RRC signaling and will use the block number index to determine its TPC command in the received group-common DCI in order to perform power control for the PUCCH.

[0074] When supporting A-CSI on PUCCH triggered by DL DCI as proposed herein, the UE may expect that the same TPC-PUCCH-RNTI and the same TPC block number index will apply for power control for A-CSI on PUCCH. Fig.10 , the UE may receive a second TPC command (δ 2 ). In this case, according to option b, the UE may include the power δ in g(3) based on the group common TPC received K symbols before the A-CSI is sent on the PUCCH. 2 According to option a, the UE will receive the group common TPC after determining the DL grant for scheduling A-CSI on PUCCH, excluding the power δ in g(3). 2 .

[0075] In some cases, the UE may be configured with a new RNTI (e.g., TPC-A-CSI-PUCCH-RNTI) and / or a separate block number index for determining the TPC specifically used for power control for A-CSI on PUCCH from the group-common DCI. In other words, in this case, the UE applies power control from the group-common DCI only when the DCI is scrambled with the new RNTI, and applies the TPC corresponding to the new block number index for this purpose.

[0076] As described herein, allowing DL grants to trigger aperiodic CSI reporting on the PUCCH can enable faster A-CSI reporting than A-CSI reporting on the PUSCH. Providing more up-to-date CSI information to the base station in this way can help the base station optimize DL scheduling.

[0077] The techniques described herein may be used for various wireless communication technologies, such as 3GPP Long Term Evolution (LTE), Advanced LTE (LTE-A), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), and other networks. The terms "network" and "system" are often used interchangeably.

[0078] CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95, and IS-856 standards. TDMA networks can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS). LTE and LTE-A are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called "3rd Generation Partnership Project" (3GPP). cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).

[0079] The technology described herein can be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For the sake of clarity, although this document may use terms commonly associated with 3G, 4G and / or 5G wireless technologies to describe various aspects, various aspects of the present disclosure may be applied to communication systems based on other generations.

[0080] New Radio (NR) is an emerging wireless communication technology under development in conjunction with the 5G Technology Forum (5GTF). NR access (e.g., 5G NR) can support a variety of wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80MHz or more), millimeter wave (mmW) targeting high carrier frequency (e.g., 25GHz or more), large-scale MTC (mMTC) targeting non-backward compatible MTC technology, and / or mission critical services targeting ultra-reliable low-latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet corresponding quality of service (QoS) requirements. In addition, these services can coexist in the same subframe.

[0081] In 3GPP, the term "cell" can refer to the coverage area of ​​a Node B and / or a NB subsystem serving the coverage area, depending on the context in which the term is used. In NR systems, the terms "cell" and BS, next generation Node B (gNB or gNodeB), access point (AP), distribution unit (DU), carrier, or transmit receive point (TRP) can be used interchangeably. BS can provide communication coverage for macro cells, pico cells, femto cells and / or other types of cells. Macro cells can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UEs with service subscriptions. Pico cells can cover relatively small geographic areas and can allow unrestricted access by UEs with service subscriptions. Femto cells can cover relatively small geographic areas (e.g., residential) and can allow restricted access by UEs associated with the femto cells (e.g., UEs in a closed subscriber group (CSG), UEs for users in residential areas, etc.). BSs for macro cells can be referred to as macro BSs. BSs for pico cells can be referred to as pico BSs. A BS for a femto cell may be called a femto BS or a home BS.

[0082] UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smart phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet device, camera, gaming device, netbook, smartbook, ultrabook, medical device or medical apparatus, biometric sensor / device, wearable device (such as smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), entertainment device (e.g., music device, video device, satellite radio unit, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate via wireless or wired medium. Some UEs may be considered as evolved or machine type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a BS, another device (e.g., a remote device), or some other entity. A wireless node can provide, for example, a connection to a network (e.g., a wide area network such as the Internet or a cellular network) or to a network via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

[0083] Some wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often referred to as frequency tones, bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15kHz, and the minimum resource allocation (called a "resource block") can be 12 subcarriers (or 180kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal FFT size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband may cover 1.08 MHz (ie, 6 RBs), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.In LTE, the basic transmission time interval (TTI) or packet duration is a 1 ms subframe.

[0084] NR can utilize OFDM with CP on the uplink and downlink and includes support for half-duplex operation using TDD. In NR, a subframe is still 1ms, but the basic TTI is called a time slot. A subframe contains a variable number of time slots (e.g., 1, 2, 4, 8, 16, ... time slots), depending on the subcarrier spacing. NR RB is 12 continuous frequency subcarriers. NR can support a base subcarrier spacing of 15KHz, and other subcarrier spacings can be defined relative to the base subcarrier spacing, such as 30kHz, 60kHz, 120kHz, 240kHz, etc. The symbol and time slot lengths scale with the subcarrier spacing. The CP length also depends on the subcarrier spacing. Beamforming can be supported and the beam direction can be dynamically configured. MIMO transmission with precoding can also be supported. In some examples, the MIMO configuration in DL can support up to 8 transmit antennas, with up to 8 streams of multi-layer DL transmission and up to 2 streams per UE. In some examples, multi-layer transmission of up to 2 streams per UE can be supported. Up to 8 serving cells may be used to support aggregation of multiple cells.

[0085] In some examples, access to the air interface may be scheduled. A scheduling entity (e.g., BS) allocates resources for communication between some or all devices and equipment within its service area or cell. A scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, subordinate entities utilize resources allocated by the scheduling entity. BS is not the only entity that can act as a scheduling entity. In some examples, a UE may act as a scheduling entity, and resources for one or more subordinate entities (e.g., one or more other UEs) may be scheduled, and other UEs utilize resources scheduled by the UE for wireless communication. A UE may act as a scheduling entity in a peer-to-peer (P2P) network and / or in a mesh network. In a mesh network example, UEs may communicate directly with each other in addition to communicating with a scheduling entity.

[0086] In some examples, two or more subordinate entities (e.g., UEs) can use side link signals to communicate with each other. Real-world applications of such side link communications may include public safety, proximity services, UE-to-network relays, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh networks, and / or various other suitable applications. In general, a side link signal may refer to a signal that is communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., UE or BS), even if the scheduling entity may be used for scheduling and / or control purposes. In some examples, side link signals may be communicated using licensed spectrum (unlike wireless local area networks, which typically use unlicensed spectrum).

[0087] The methods disclosed herein include one or more steps or actions for implementing these methods. These method steps and / or actions may be interchangeable with each other without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.

[0088] As used herein, a phrase referring to "at least one" of a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiples of the same elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0089] As used herein, the term "determine" includes various actions. For example, "determine" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, a database, or another data structure), determining, etc. In addition, "determine" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. In addition, "determine" may include solving, selecting, choosing, establishing, etc.

[0090] The above description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but are consistent with the entire scope of protection of the language of the claims, wherein, unless otherwise specified, reference to an element in the singular is not intended to mean "one and only one", but "one or more". Unless otherwise specifically specified, the term "some" refers to one or more. All structures and functions equivalent to the elements of the various aspects described throughout this disclosure that are known or to be known to those of ordinary skill in the art are hereby expressly incorporated herein by reference, and are intended to be covered by the claims. In addition, none of the contents disclosed herein are intended to be dedicated to the public, regardless of whether the disclosure is explicitly recorded in the claims. Unless the phrase "parts for ..." is used to explicitly record the claim element, or the phrase "step for ..." is used to record the claim element in the case of a method claim, the claim element shall not be interpreted according to the provisions of 35 U.S.C. §112 (f).

[0091] The various operations of the above method can be performed by any suitable components capable of performing the corresponding functions. These components may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors. Generally, where there are operations shown in the accompanying drawings, those operations may have corresponding paired components plus functional components with similar reference numerals.

[0092] The various illustrative logic blocks, modules and circuits described in conjunction with the present disclosure may be implemented or executed using a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may also be any commercially available processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.

[0093] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. The bus may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system. The bus may link various circuits together, including a processor, a machine-readable medium, and a bus interface. The bus interface may be used to connect a network adapter and other devices to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In the user terminal 120 (see Figure 1 ), a user interface (e.g., buttons, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, etc., which are well known in the art and will not be described in detail. The processor may be implemented using one or more general-purpose processors and / or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits that can execute software. Those skilled in the art will recognize that how to best implement the described functionality for the processing system depends on the specific application and the overall design constraints imposed on the entire system. For example, in some cases, such as Figure 2 The processors shown in FIG. 1 may be configured to perform Figure 5 Operation 500 and / or Figure 6 Operation 600.

[0094] If implemented in software, the functions may be stored on a computer-readable medium or transmitted via a computer-readable medium as one or more instructions or codes. Software should be broadly interpreted as instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or other. Computer-readable media include both computer storage media and communication media, and communication media include any media that facilitates the transmission of a computer program from one location to another. The processor may be responsible for managing the bus and general processing, including the execution of software modules stored on a machine-readable storage medium. A computer-readable storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Alternatively, a storage medium may be integrated into a processor. For example, a machine-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium having instructions stored thereon separated from a wireless node, all of which may be accessed by a processor via a bus interface. Alternatively, or additionally, a machine-readable medium or any portion thereof may be integrated into a processor, such as a situation that may be associated with a cache and / or a general register file. Examples of machine-readable storage media may include, for example, RAM (random access memory), flash memory, ROM (read only memory), PROM (programmable read only memory), EPROM (erasable programmable read only memory), EEPROM (electrically erasable programmable read only memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage media or any combination thereof. The machine-readable medium may be implemented in a computer program product.

[0095] A software module may include a single instruction, or many instructions, and may be distributed across multiple different code segments, between different programs, and across multiple storage media. A computer-readable medium may include multiple software modules. A software module includes instructions that, when executed by a device such as a processor, cause a processing system to perform various functions. A software module may include a sending module and a receiving module. Each software module may exist in a single storage device or may be distributed across multiple storage devices. For example, when a triggering event occurs, a software module may be loaded from a hard drive into a RAM. During the execution of a software module, a processor may load some of the instructions into a cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by a processor. When referring to the functions of the following software modules, it should be understood that such functions are implemented by the processor when executing instructions from the software module.

[0096] Furthermore, any connection may properly be referred to as a computer-readable medium. For example, if the software is transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared (IR), radio and microwave), then the definition of medium includes the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio and microwave). As used herein, disc and disk include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Disks, where magnetic disks typically reproduce data magnetically, and optical disks reproduce data optically with lasers. Thus, in some aspects, computer readable media may include non-transitory computer readable media (e.g., tangible media). Additionally, for other aspects, computer readable media may include transitory computer readable media (e.g., signals). Combinations of the above should also be included within the scope of computer readable media.

[0097] Thus, certain aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having instructions stored (and / or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein, for example, for performing the operations described herein and Figures 5 and 6 Instructions for the operations shown.

[0098] In addition, it should be appreciated that, when appropriate, the module and / or other suitable components for performing the methods and techniques described herein can be downloaded and / or otherwise obtained by a user terminal and / or a base station. For example, such a device can be coupled to a server to facilitate the transmission of the components for performing the methods described herein. Alternatively, the various methods described herein can be provided via a storage component (e.g., RAM, ROM, a physical storage medium such as a compact disk (CD) or a floppy disk, etc.), so that when being coupled to the device or providing the storage component to the device, the user terminal and / or the base station can obtain the various methods. In addition, any other suitable technology for providing the methods and techniques described herein to the device can be utilized.

[0099] It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. A method for wireless communication by a user equipment, comprising: Obtaining information about a set of one or more configurations for aperiodic channel state information (A-CSI) reporting on a physical uplink control channel (PUCCH), wherein the set of one or more configurations comprises a list of A-CSI reporting configurations per downlink serving cell, and each A-CSI reporting configuration comprises one or more CSI resources in a corresponding downlink serving cell; receiving downlink control information DCI for a downlink grant, the downlink control information DCI comprising at least one field for triggering an A-CSI report on the PUCCH; generating the A-CSI report based on one A-CSI reporting configuration selected based on the field in the DCI from a set of A-CSI reporting configurations, wherein CSI resources for the A-CSI report triggered by the DCI are on the same bandwidth part BWP as corresponding physical downlink shared channel PDSCH data scheduled by the downlink grant; as well as A CSI report is sent on the PUCCH.

2. The method of claim 1, wherein: The DCI includes a bit indicating whether the DCI also schedules downlink data transmission.

3. The method of claim 1, wherein: Different values ​​of the code point of the field indicate different A-CSI reporting configurations.

4. The method of claim 3, wherein: One value of the codepoint indicates that no A-CSI report is requested.

5. The method of claim 1, wherein: The A-CSI report is triggered by a code point of the field.

6. The method of claim 1, wherein: In case the DCI is received in a first carrier and schedules downlink transmission in a second carrier, the code point of the field is associated with a CSI resource on the second carrier.

7. The method of claim 1, wherein: The set of one or more configurations is a defined type indicating that the configuration is used for A-CSI reporting on the PUCCH and can only be used for A-CSI reporting on the PUCCH; and The method further includes receiving radio resource control (RRC) signaling to be used for determining time and frequency resources of a PUCCH for the A-CSI reporting.

8. The method of claim 7, wherein: The parameters include at least one of the following: an A-CSI reporting offset relative to the end of the DCI of the PUCCH used to send the A-CSI report; or PUCCH resources per uplink bandwidth part BWP.

9. The method of claim 8, wherein: The parameters are configured for each of the one or more configurations.

10. The method of claim 1, wherein: The A-CSI report is generated based on at least one CSI resource setting associated with both an uplink grant and a downlink grant; If triggered by an uplink grant, a first CSI reporting offset is associated with said CSI resource setting for sending a CSI report; as well as If triggered by a downlink grant, the second CSI reporting offset is associated with the CSI resource setting used to send the CSI report.

11. The method of claim 1, wherein: The DCI also indicates one or more parameters to be used to determine time and frequency resources of the PUCCH used for the A-CSI reporting.

12. The method of claim 11, wherein: The parameters include at least one of the following: a first field indicating an A-CSI reporting offset relative to an end of the DCI of the PUCCH used to send the A-CSI report; or A second field having a code point value that maps to a set of radio resource control (RRC) configuration values ​​for an A-CSI reporting offset relative to an end of the DCI for a PUCCH used to send the A-CSI report.

13. The method of claim 12, wherein: At least one of the first field or the second field includes at least one of the following: A field that can be used to indicate a scheduling delay for confirming a downlink transmission scheduled by a downlink DCI; A field that can be used to indicate time domain resources used for downlink transmission scheduled by a downlink DCI; or A field that can be used to indicate frequency domain resources used for downlink transmission scheduled by the downlink DCI.

14. The method of claim 11, wherein: The parameters include at least one of the following: an existing PUCCH resource indicator (PRI) field, the existing PUCCH resource indicator (PRI) field being reused to indicate a resource of a PUCCH used to send the A-CSI report; or a new PRI field, wherein the new PRI field is used to indicate resources of the PUCCH used to send the A-CSI report; or Another existing DCI field is reused to indicate a resource of the PUCCH for sending the A-CSI report.

15. The method of claim 1, wherein: The DCI further includes at least a first transmit power control TPC field of a PUCCH for carrying confirmation feedback, and: The UE applies the first TPC field to both the PUCCH carrying the confirmation feedback and the PUCCH carrying the A-CSI report; or The UE applies the first TPC field to a PUCCH carrying the confirmation feedback and applies the second TPC field to a PUCCH carrying the A-CSI report.

16. The method of claim 15, further comprising: receiving another DCI having a second TPC field, and: When calculating the cumulative power, only the TPC field received before the last symbol of the DCI is applied, or both the first TPC field and the second TPC field are applied; or A TPC field received up to a number of symbols before sending the PUCCH carrying the A-CSI report is applied.

17. The method of claim 1, further comprising: receiving a group common DCI having a plurality of transmit power control (TPC) fields, including a TPC field for the UE; and The TPC field for the UE is applied to the PUCCH carrying the A-CSI report.

18. A method for wireless communication by a network entity, comprising: Sending information about a set of one or more configurations for aperiodic channel state information (A-CSI) reporting on a physical uplink control channel (PUCCH) to a UE, wherein the set of one or more configurations includes a list of A-CSI reporting configurations per downlink serving cell, and each A-CSI reporting configuration includes one or more CSI resources in a corresponding downlink serving cell; Sending first downlink control information DCI for a downlink grant to the UE, the first downlink control information DCI comprising at least one field for triggering an A-CSI report on the PUCCH, wherein CSI resources for the A-CSI report triggered by the DCI are on the same bandwidth part BWP as corresponding physical downlink shared channel PDSCH data scheduled by the downlink grant; as well as A PUCCH carrying the A-CSI report is received from the UE, the A-CSI report being generated based on one of the set of A-CSI reporting configurations selected based on the field in the DCI.

19. The method of claim 18, wherein: The DCI includes a bit indicating whether the DCI also schedules downlink data transmission.

20. The method of claim 18, wherein: Different values ​​of the code point of the field indicate different A-CSI reporting configurations.

21. The method of claim 20, wherein: One value of the codepoint indicates that no A-CSI report is requested.

22. The method of claim 18, wherein: The A-CSI report is triggered by a code point of the field.

23. The method of claim 18, wherein: In case the DCI is received in a first carrier and schedules downlink transmission in a second carrier, the code point of the field is associated with a CSI resource on another cell.

24. The method of claim 18, wherein: The set of one or more configurations is a defined type indicating that the configuration is used for A-CSI reporting on the PUCCH and can only be used for A-CSI reporting on the PUCCH; and The method further includes receiving radio resource control (RRC) signaling to be used for determining time and frequency resources of a PUCCH for the A-CSI reporting.

25. The method of claim 24, wherein: The parameters include at least one of the following: an A-CSI reporting offset relative to the end of the DCI of the PUCCH used to send the A-CSI report; or PUCCH resources per uplink bandwidth part BWP.

26. The method of claim 25, wherein: The parameters are configured for each of the one or more configurations.

27. The method of claim 18, wherein: The A-CSI report is generated based on at least one CSI resource setting associated with both an uplink grant and a downlink grant; If triggered by an uplink grant, a first CSI reporting offset is associated with said CSI resource setting for sending a CSI report; as well as If triggered by a downlink grant, the second CSI reporting offset is associated with the CSI resource setting used to send the CSI report.

28. The method of claim 18, wherein: The DCI also indicates one or more parameters to be used to determine time and frequency resources of the PUCCH used for the A-CSI reporting.

29. The method of claim 28, wherein: The parameters include at least one of the following: a first field indicating an A-CSI reporting offset relative to an end of the DCI of the PUCCH used to send the A-CSI report; or A second field having a code point value that maps to a set of radio resource control, RRC, configuration values ​​for an A-CSI reporting offset relative to an end of the DCI for a PUCCH for sending the A-CSI report.

30. The method of claim 29, wherein: At least one of the first field or the second field includes at least one of the following: A field that can be used to indicate a scheduling delay for confirming a downlink transmission scheduled by a downlink DCI; A field that can be used to indicate time domain resources used for downlink transmission scheduled by a downlink DCI; or A field that can be used to indicate frequency domain resources used for downlink transmission scheduled by the downlink DCI.

31. The method of claim 29, wherein: The parameters include at least one of the following: an existing PUCCH resource indicator PRI field, wherein the existing PUCCH resource indicator PRI field is reused to indicate a resource of a PUCCH for sending the A-CSI report; or a new PRI field, wherein the new PRI field is used to indicate resources of the PUCCH used to send the A-CSI report; or Another existing DCI field is reused to indicate a resource of the PUCCH for sending the A-CSI report.

32. The method of claim 18, wherein: The DCI also includes: A first transmit power control TPC field for a PUCCH carrying acknowledgement feedback; and A second TPC field of the PUCCH is used to carry the A-CSI report.

33. The method of claim 18, further comprising: A group common DCI having a plurality of transmit power control (TPC) fields is transmitted, including one TPC field for the UE, to be applied to the PUCCH carrying the A-CSI report.

Images