WO2022028491A1

WO2022028491A1 - Apparatus and method for aperiodic channel state information transmission

Info

Publication number: WO2022028491A1
Application number: PCT/CN2021/110629
Authority: WO
Inventors: Haihan Wang
Original assignee: FG Innovation Company Limited
Priority date: 2020-08-07
Filing date: 2021-08-04
Publication date: 2022-02-10

Abstract

An apparatus and a method for Aperiodic Channel State Information (A-CSI) transmission are provided. The method includes receiving, from a base station, Downlink Control Information (DCI) including a downlink assignment that schedules a Physical Downlink Shared Channel (PDSCH) and a first Physical Uplink Control Channel (PUCCH) corresponding to the PDSCH; and reporting A-CSI to the base station through the first PUCCH.

Description

APPARATUS AND METHOD FOR APERIODIC CHANNEL STATE INFORMATION TRANSMISSION

CROSS-REFERENCE TO RELATED APPLICATION (S)

The present application claims the benefit of and priority to provisional U.S. Patent Application Serial No. 63/062,712 (hereafter referred to as “the ‘712 provisional” ) , filed on August 7, 2020, entitled “METHOD AND APPARATUS FOR SCHEDULING A-CSI ON A PUCCH, ” and provisional U.S. Patent Application Serial No. 63/062,722 (hereafter referred to as “the ‘722 provisional” ) , filed on August 7, 2020, entitled “METHOD AND APPARATUS FOR MULTIPLEXING AND OVERRIDING A-CSI PUCCH. ” The contents of the ‘712 provisional and the ‘722 provisional are fully incorporated herein by reference for all purposes.

FIELD

The present disclosure generally relates to wireless communications, and more particularly, to an apparatus and a method for Aperiodic Channel State Information (A-CSI) transmission.

BACKGROUND

With the tremendous growth in the number of connected devices and the rapid increase in user/network traffic volume, various efforts have been made to improve different aspects of wireless communication for the next-generation wireless communication system, such as the fifth-generation (5G) New Radio (NR) , by improving data rate, latency, reliability, and mobility.

The 5G NR system is designed to provide flexibility and configurability to optimize the network services and types, accommodating various use cases such as enhanced Mobile Broadband (eMBB) , massive Machine-Type Communication (mMTC) , and Ultra-Reliable and Low-Latency Communication (URLLC) .

However, as the demand for radio access continues to increase, there is a need for further improvements in wireless communication for the next-generation wireless communication system.

SUMMARY

The present disclosure is directed to an apparatus and a method for A-CSI transmission.

According to an aspect of the present disclosure, a method performed by a user equipment (UE) for A-CSI transmission is provided. The method includes receiving, from a base station, Downlink Control Information (DCI) including a downlink assignment that schedules a Physical Downlink Shared Channel (PDSCH) and a first Physical Uplink Control Channel (PUCCH) corresponding to the PDSCH; and reporting A-CSI to the base station through the first PUCCH.

In some implementations, the first PUCCH is scheduled for transmitting a Hybrid Automatic Repeat reQuest (HARQ) Acknowledgement (ACK) feedback for the PDSCH.

In some implementations, the downlink assignment further schedules a second PUCCH for transmitting a Hybrid Automatic Repeat reQuest (HARQ) Acknowledgement (ACK) feedback for the PDSCH. The first PUCCH is scheduled for transmitting the A-CSI and not for transmitting the HARQ ACK feedback for the PDSCH.

In some implementations, the DCI includes an indicator that indicates an A-CSI trigger state for reporting the A-CSI. The A-CSI trigger state is associated with a reporting configuration that indicates a resource allocation of the first PUCCH.

In some implementations, reporting the A-CSI is triggered by a CSI request included in the DCI.

According to another aspect of the present disclosure, a UE for A-CSI transmission is provided. The UE includes a memory and a processing circuitry coupled to the memory. The processing circuitry is configured to receive, from a base station, Downlink Control Information (DCI) including a downlink assignment that schedules a Physical Downlink Shared Channel (PDSCH) and a first Physical Uplink Control Channel (PUCCH) corresponding to the PDSCH; and report A-CSI to the base station through the first PUCCH.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the example disclosure are best understood from the following detailed description when read with the accompanying figures. Various features are not drawn to scale. Dimensions of various features may be arbitrarily increased or reduced for clarity of discussion.

Figure 1 illustrates a flowchart for a method performed by a UE for A-CSI transmission, according to an implementation of the present disclosure.

Figure 2 is a schematic diagram illustrating a PDSCH and a PUCCH scheduled by a downlink assignment included in DCI received on a Physical Downlink Control Channel (PDCCH) , according to an example implementation of the present disclosure.

Figure 3 is a schematic diagram illustrating a PDSCH and two separate PUCCHs scheduled by a downlink assignment included in DCI received on a PDCCH, according to an example implementation of the present disclosure.

Figure 4 is a diagram illustrating Information Elements (IEs) contained in an IE CSI-ReportConfig, according to an example implementation of the present disclosure.

Figure 5 is a diagram illustrating IEs contained in an IE CSI-AperiodicTriggerState, according to an example implementation of the present disclosure.

Figure 6 is a block diagram illustrating a node for wireless communication according to an implementation of the present disclosure.

DETAILED DESCRIPTION

The following contains specific information related to implementations of the present disclosure. The drawings and their accompanying detailed description are merely directed to implementations. However, the present disclosure is not limited to these implementations. Other variations and implementations of the present disclosure will be obvious to those skilled in the art.

Unless noted otherwise, like or corresponding elements among the drawings may be indicated by like or corresponding reference numerals. Moreover, the drawings and illustrations in the present disclosure are generally not to scale and are not intended to correspond to actual relative dimensions.

For the purpose of consistency and ease of understanding, like features may be identified (although, in some examples, not illustrated) by the same numerals in the drawings. However, the features in different implementations may differ in other respects and shall not be narrowly confined to what is illustrated in the drawings.

The phrases “In some implementations, ” or “in some implementations, ” may each refer to one or more of the same or different implementations. The term “coupled” is defined as connected whether directly or indirectly via intervening components and is not necessarily limited to physical connections. The term “comprising” means “including, but not necessarily limited to” and specifically indicates open-ended inclusion or membership in the disclosed combination, group, series or equivalent. The expression “at least one of A, B and C” or “at least one of the following: A, B and C” means “only A, or only B, or only C, or any combination of A, B and C. ”

The terms “system” and “network” may be used interchangeably. The term “and/or” is only an association relationship for disclosing associated objects and represents that three relationships may exist such that A and/or B may indicate that A exists alone, A and B exist at the same time, or B exists alone. “A and/or B and/or C” may represent that at least one of A, B, and C exists. The character “/” generally represents that the associated objects are in an “or” relationship.

For the purposes of explanation and non-limitation, specific details such as functional entities, techniques, protocols, standards, and the like, are set forth for providing an understanding of the disclosed technology. In other examples, detailed disclosures of well-known methods, technologies, systems, architectures, and the like are omitted so as not to obscure the present disclosure with unnecessary details.

Persons skilled in the art will immediately recognize that any disclosed network function (s) or algorithm (s) may be implemented by hardware, software or a combination of software and hardware. Disclosed functions may correspond to modules which may be software, hardware, firmware, or any combination thereof.

A software implementation may include computer-executable instructions stored on a computer-readable medium such as memory or other type of storage devices. One or more microprocessors or general-purpose computers with communication processing capability may be programmed with corresponding computer-executable instructions and perform the disclosed network function (s) or algorithm (s) .

The microprocessors or general-purpose computers may include Applications Specific Integrated Circuitry (ASIC) , programmable logic arrays, and/or using one or more Digital Signal Processors (DSPs) . Although some of the disclosed implementations are oriented to software installed and executing on computer hardware, alternative implementations implemented as firmware or as hardware or as a combination of hardware and software are well within the scope of the present disclosure. The computer-readable medium may include, but is not limited to, Random Access Memory (RAM) , Read-Only Memory (ROM) , Erasable Programmable Read-Only Memory (EPROM) , Electrically Erasable Programmable Read-Only Memory (EEPROM) , flash memory, Compact Disc Read-Only Memory (CD-ROM) , magnetic cassettes, magnetic tape, magnetic disk storage, or any other equivalent medium capable of storing computer-readable instructions.

A radio communication network architecture such as a Long Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Pro system, or a 5G NR Radio Access Network (RAN) may typically include at least one base station (BS) , at least one UE, and one or more optional network elements that provide connection within a network. The UE may communicate with the network such as a Core Network (CN) , an Evolved Packet Core (EPC) network, an Evolved Universal Terrestrial RAN (E-UTRAN) , a Next-Generation Core (NGC) , a 5G Core (5GC) , or an internet via a RAN established by one or more BSs.

A UE may include, but is not limited to, a mobile station, a mobile terminal or device, or a user communication radio terminal. The UE may be a portable radio equipment that includes, but is not limited to, a mobile phone, a tablet, a wearable device, a sensor, a vehicle, or a Personal Digital Assistant (PDA) with wireless communication capability. The UE may be configured to receive and transmit signals over an air interface to one or more cells in a RAN.

The BS may be configured to provide communication services according to at least a Radio Access Technology (RAT) such as Worldwide Interoperability for Microwave Access (WiMAX) , Global System for Mobile communications (GSM) that is often referred to as 2G, GSM Enhanced Data rates for GSM Evolution (EDGE) RAN (GERAN) , General Packet Radio Service (GPRS) , Universal Mobile Telecommunication System (UMTS) that is often referred to as 3G based on basic Wideband-Code Division Multiple Access (W-CDMA) , High-Speed Packet Access (HSPA) , LTE, LTE-A, evolved/enhanced LTE (eLTE) that is LTE connected to 5GC, NR (often referred to as 5G) , and/or LTE-APro. However, the scope of the present disclosure is not limited to these protocols.

The BS may include, but is not limited to, a node B (NB) in the UMTS, an evolved node B (eNB) in LTE or LTE-A, a radio network controller (RNC) in UMTS, a BS controller (BSC) in the GSM/GERAN, a next-generation eNB (ng-eNB) in an Evolved Universal Terrestrial Radio Access (E-UTRA) BS in connection with 5GC, a next-generation Node B (gNB) in the 5G-RAN (or in the 5G Access Network (5G-AN) ) , or any other apparatus capable of controlling radio communication and managing radio resources within a cell. The BS may serve one or more UEs via a radio interface.

The BS may provide radio coverage to a specific geographical area using a plurality of cells included in the RAN. The BS may support the operations of the cells. Each cell may be operable to provide services to at least one UE within its radio coverage.

Each cell (often referred to as a serving cell) may provide services to serve one or more UEs within its radio coverage such that each cell schedules the downlink (DL) and optionally uplink (UL) resources to at least one UE within its radio coverage for DL and optionally UL packet transmissions. The BS may communicate with one or more UEs in the radio communication system via the plurality of cells.

A cell may allocate Sidelink (SL) resources for supporting Proximity Service (ProSe) , LTE SL services, and/or LTE/NR Vehicle-to-Everything (V2X) services. Each cell may have overlapped coverage areas with other cells.

In NR system, multiple types of services are supported, each with different latency and reliability requirements, including eMBB and URLLC. To support URLLC traffics, gNB needs to ensure the stringent requirements of latency and reliability are met. gNB may rely on Channel State Information (CSI) feedback to adjust the resource allocation and Modulation Coding Scheme (MCS) for the downlink (DL) transmissions to meet the requirements. However, since URLLC traffic may be sporadic, the periodic CSI report may not reflect the channel condition timely for scheduling the URLLC traffic. Consequently, gNB may need to schedule the URLLC transmission with conservative resource allocation and MCS, which is robust enough to meet the requirements. Although Aperiodic Channel State Information (A-CSI) on Physical Uplink Shared Channel (PUSCH) can provide timelier channel condition, but it may unnecessarily waste Physical Downlink Control Channel (PDCCH) resource, since there may not be UL data to transmit. To acquire timelier CSI feedback without wasting of PDCCH resource, A-CSI on Physical Uplink Control Channel (PUCCH) triggered by DL assignment may be needed.

The time and frequency resources that can be used by the UE to report CSI may be controlled by the gNB. CSI may include at least one of Channel Quality Indicator (CQI) , precoding matrix indicator (PMI) , CSI-RS resource indicator (CRI) , SS/PBCH Block Resource indicator (SSBRI) , layer indicator (LI) , rank indicator (RI) , L1-RSRP or L1-SINR.

For CQI, PMI, CRI, SSBRI, LI, RI, and/or L1-RSRP, a UE may be configured by higher layers with N≥1 CSI-ReportConfig Reporting Settings, M≥1 CSI-ResourceConfig Resource Settings, and one or two list (s) of trigger states (given by the higher layer parameters CSI-AperiodicTriggerStateList and CSI-SemiPersistentOnPUSCH-TriggerStateList) .

Each trigger state in the CSI-AperiodicTriggerStateList may contain a list of associated CSI-ReportConfigs indicating the Resource Set IDs for channel and optionally for interference. Each trigger state in CSI-SemiPersistentOnPUSCH-TriggerStateList contains one associated CSI-ReportConfig.

Regarding the A-CSI triggering mechanism, a trigger state may be initiated using the CSI request field in DCI. For example, when all the bits of CSI request field in DCI are set to zero, no CSI is requested. When the number of configured CSI triggering states in CSI-AperiodicTriggerStateList is greater than

where N _TS is the number of bits in the DCI CSI request field, the UE may receive a subselection indication, as described in clause 6.1.3.13 of TS 38.321, used to map up to

trigger states to the codepoints of the CSI request field in DCI. N _TS is configured by the higher layer parameter reportTriggerSize. When the number of CSI triggering states in CSI-AperiodicTriggerStateList is less than or equal to

the CSI request field in DCI directly indicates the triggering state.

When aperiodic CSI-RS is used with aperiodic reporting, the CSI-RS offset is configured per resource set by the higher layer parameter aperiodicTriggeringOffset, including the case that the UE is not configured with a parameter [minimumSchedulingOffset] for any DL or UL BWP and all the associated trigger states do not have the higher layer parameter qcl-Type set to 'QCL-TypeD' in the corresponding TCI states. The CSI-RS triggering offset has the values of {0, 1, 2, 3, 4, 16, 24} slots. If the UE is not configured with the parameter [minimumSchedulingOffset] for any DL or UL BWP and if all the associated trigger states do not have the higher layer parameter qcl-Type set to 'QCL-TypeD' in the corresponding TCI states, the CSI-RS triggering offset is fixed to zero. The aperiodic triggering offset of the CSI-IM follows offset of the associated NZP CSI-RS for channel measurement.

The PUSCH resource for A-CSI may be indicated by the DCI triggering the A-CSI. The PRBs for the PUSCH may be indicated in the frequency domain resource assignment (FDRA) field of the DCI and the symbols for the PUSCH is indicated by the time domain resource assignment (TDRA) field of the DCI. UL-SCH indicator field in the DCI indicates if the A-CSI is multiplexed with UL-SCH. When UL-SCH indicator field is set to ‘1’ , A-CSI is multiplexed with UL-SCH, and the number of REs for A-CSI may be calculated as specified in TS 38.212, and the slot n+K2 in which the PUSCH is transmitted may be determined by the entry for K2 value in the row of the TDRA table, which is indicated by the TDRA field of the DCI transmitted in slot n. Otherwise, when UL-SCH indicator field is set to ‘0’ , A-CSI may be mapped on the Resource Elements (REs) allocated for the PUSCH, and the slot in which the PUSCH is transmitted is determined by the TDRA field value m of the DCI transmitted in slot n, and the K ₂ value is determined as

where Y _j, j=0, ..., N _Rep-1 are the corresponding list entries of the higher layer parameter reportSlotOffsetList in CSI-ReportConfig for the N _Rep triggered CSI Reporting Settings and Y _j (m+1) is the (m+1) th entry of Y _j.

The slot where the UE shall transmit the PUSCH is determined by K ₂ as

where n is the slot with the scheduling DCI, K ₂ is based on the numerology of PUSCH, and μ _PUSCH and μ _PDCCH are the subcarrier spacing configurations for PUSCH and PDCCH, respectively,

On the other hand, in Rel-16, a PUSCH transmission can be of low priority or high priority. When a low priority PUSCH overlaps with a high priority PUCCH, the low priority PUSCH may be cancelled. Alternatively, when a high priority PUSCH overlaps with a low priority PUCCH, the low priority PUCCH may be cancelled. The priority of a PUSCH with A-CSI may be determined by the priority indication of the scheduling DCI.

In some aspects of the present implementations, to enable a UE to transmit A-CSI on a PUCCH, the PUCCH resource scheduled for HARQ-ACK may reused for A-CSI transmission. In other words, A-CSI may be triggered by a DL assignment scheduling a PDSCH and the A-CSI is multiplexed on the PUCCH for the HARQ-ACK of the scheduled PDSCH.

In some implementations, a separate PUCCH resource may be indicated by a DL assignment scheduling a PDSCH, considering different timeline requirement of Hybrid Automatic Repeat reQuest (HARQ) -Acknowledgement (ACK) and A-CSI. The timeline requirement to transmit HARQ-ACK, e.g., PDSCH processing procedure time T _proc, 1, after the end of the corresponding PDSCH may be defined as T _proc, 1= (N ₁+d _1, 1) (2048+144) ·κ2 ^-μ·T _C, where N ₁ depends on the Demodulation Reference Signal (DMRS) configuration and Subcarrier Spacing (SCS) of the PDCCH scheduling the PDCCH, PDSCH and the PUCCH for the HARQ-ACK transmission, and d _1, 1 depends on the PDSCH duration and the overlapping condition of PDSCH and PDCCH. N ₁ for UE processing capability 2 is shown in the Table 1.

Table 1: PDSCH processing time for PDSCH processing capability 2

The timeline requirement for UE to report A-CSI, e.g., CSI computation time T _proc, CSI, after the end of the PDCCH triggering the A-CSI may be defined as T _proc, CSI= (Z) (2048+144) ·κ2 ^-μ·T _C. In addition, T′ _proc, CSI= (Z′) (2048+144) ·κ2 ^-μ·T _C may be defined as the timeline requirement for a UE to update the n-th triggered CSI report after the end of the last symbol in time of the latest of: aperiodic CSI-Reference Signal (CSI-RS) resource for channel measurements, aperiodic CSI-Interference Measurement (CSI-IM) used for interference measurements, and the aperiodic Non-Zero Power (NZP) CSI-RS for interference measurement, when aperiodic CSI-RS is used for channel measurement for the n-th triggered CSI report. Z, Z' and μ are defined as:

and

where M is the number of updated CSI report (s) according to Clause 5.2.1.6 in 3GPP Technical Specification (TS) 38.214. (Z (m) , Z′ (m) ) may correspond to the m-th updated CSI report and be defined as:

(Z ₁, Z′ ₁) of the Table 2 if the CSI is triggered without a PUSCH with either transport block or HARQ-ACK or both when L = 0 CPUs are occupied (according to Clause 5.2.1.6 in TS 38.214) and the CSI to be transmitted is a single CSI and corresponds to wideband frequency-granularity where the CSI corresponds to at most 4 CSI-RS ports in a single resource without CRI report and where CodebookType is set to 'typeI-SinglePanel' or where reportQuantity is set to 'cri-RI-CQI' , or

(Z ₁, Z′ ₁) of the Table 3 if the CSI to be transmitted corresponds to wideband frequency-granularity where the CSI corresponds to at most 4 CSI-RS ports in a single resource without CRI report and where CodebookType is set to 'typeI-SinglePanel' or where reportQuantity is set to 'cri-RI-CQI' , or

(Z ₁, Z′ ₁) of the Table 3 if the CSI to be transmitted corresponds to wideband frequency-granularity where the reportQuantity is set to 'ssb-Index-SINR' , or reportQuantity is set to 'cri- SINR' , or

(Z ₃, Z′ ₃) of the Table 3 if reportQuantity is set to 'cri-RSRP' or 'ssb-Index-RSRP' , where Xμ is according to UE reported capability beamReportTiming and KB _l is according to UE reported capability beamSwitchTiming as defined in TS 38.306, or

(Z ₂, Z′ ₂) of Table 3 otherwise.

μ of Table 2 and Table 3 corresponds to the min (μ _PDCCH, μ _CSI-RS, μ _UL) where the μ _PDCCH corresponds to the subcarrier spacing of the PDCCH with which the DCI was transmitted and μ _UL corresponds to the subcarrier spacing of the PUSCH with which the CSI report is to be transmitted and μ _CSI-RS corresponds to the minimum subcarrier spacing of the aperiodic CSI-RS triggered by the DCI.

Table 2: CSI computation delay requirement 1

Table 3: CSI computation delay requirement 2

Take 30 Kilohertz (kHz) SCS for example, assuming PDCCH is not overlapping with a scheduled PDSCH with duration of 2 symbols, then T _proc, 1= (4.5+0) (2048+144) ·κ2 ^-μ·T _C. The time duration required for UE to transmit HARQ-ACK after the end of the PDCCH is then equal to the time duration of 6.5 symbols for this case. Assuming the DCI scheduling the PDSCH is used to trigger an A-CSI report, and the conditions for using (Z ₁, Z′ ₁) of Table 2 are satisfied, then the first symbol of the channel to carry the A-CSI report is at least 13 symbols after the end of the DCI, which is 2 times of the time duration required for HARQ-ACK feedback.

From the above example, it can be seen that if the A-CSI is multiplexed in the PUCCH for HARQ-ACK, the HARQ-ACK will have to be delayed, which may reduce the time budget for retransmission.

In some aspects of the present implementations, indicating a separate PUCCH resource for A-CSI in a DL assignment scheduling a PDSCH seems beneficial. To achieve this target, the issues of configuration and indication of the PUCCH for A-CSI need to be addressed.

On the other hand, if a PUCCH resource for HARQ-ACK is used for transmission of A-CSI, it is more flexible to also support triggering A-CSI without scheduling a PDSCH. How to signal that there is no scheduled PDSCH and handling of HARQ-ACK codebook when no PDSCH is scheduled may need to be addressed.

For a PUCCH specifically used for A-CSI transmission, a physical layer priority may be needed to handle intra-UE prioritization when the PUCCH overlaps with another PUSCH or PUCCH.

In Release 16 (Rel-16) Enhanced URLLC (eURLLC) scenarios, subslot-based PUCCH is provided to reduce the latency for PUCCH transmission for HARQ-ACK. For a PUCCH specifically used for A-CSI transmission, it is also beneficial to support subslot based PUCCH transmission. A mechanism to configure and schedule subslot-based PUCCH for A-CSI may be required.

A PUCCH specifically used for A-CSI transmission may overlap a PUSCH or a PUCCH. An overlapping PUSCH may or may not be triggered with A-CSI, and an overlapping PUCCH may be a PUCCH for HARQ-ACK, CSI, or SR. A mechanism to determine the PUSCH or PUCCH for transmission of the UCIs and whether and how to perform dropping of UCIs for each overlapping case may be needed.

For the case that PUCCH resource for HARQ-ACK is used for A-CSI transmission, it is possible that a PUCCH resource scheduled by a DCI is overridden by another DCI. That is, after receiving a first DCI scheduling a HARQ-ACK codebook on a first PUCCH, a UE may receive a second DCI updating the HARQ-ACK codebook on a second PUCCH, if the end of the second DCI is N3 symbols before the start of the first PUCCH, where N3 is defined in TS 38.213, and the second PUCCH may be the same as or different from the first PUCCH. In this case, a mechanism to handle A-CSI transmission in response to the multiple DCI receptions may be needed.

In some aspects of the present implementations, once A-CSI reporting is triggered, A- CSI may be transmitted on a PUCCH.

In some implementations, a list (e.g., CSI-AperiodicTriggerStateList) that indicates the trigger state (s) of A-CSI transmission on a PUCCH may be configured in a cell with a PUCCH resource. A CSI request field may be added to a specific DCI format (e.g., DCI format 1_1 or DCI format 1_2) for indication of a trigger state (e.g., CSI-AperiodicTriggerState) in the CSI-AperiodicTriggerStateList in the cell in which PUCCH transmission is performed.

In some implementations, a single CSI-AperiodicTriggerStateList may be configured to a UE for transmitting A-CSI on a PUCCH and A-CSI on a PUSCH in a cell configured with the PUCCH. In some implementations, whether A-CSI triggered by DCI format 0_1 or DCI format 0_2 is to be transmitted on a PUCCH or PUSCH in the cell is determined by a parameter (e.g., reportConfigType) included in the configuration (e.g., CSI-ReportConfig) identified by the identifier (e.g., reportConfigId) included in the triggered CSI-AperiodicTriggerState. If the reportConfigType is set to a first value (e.g., aperiodicOnPUCCH) , the triggered A-CSI is transmitted on a PUCCH. If the reportConfigType is set to a second value (e.g., aperiodic) , the triggered A-CSI is transmitted on PUSCH. In some implementations, A-CSI is transmitted on a PUCCH if a PUCCH resource is indicated by the DCI.

In some implementations, a list (e.g., CSIOnPUCCH-AperiodicTriggerStateList) for A-CSI transmission on a PUCCH may be configured separately from another list (e.g., CSI-AperiodicTriggerStateList) for A-CSI transmission on a PUSCH. In some implementations, if A-CSI triggering DCI indicates a PUCCH resource for A-CSI transmission, the CSI request field in the DCI may indicate a CSI-AperiodicTriggerState from the CSIOnPUCCH-AperiodicTriggerStateList. Otherwise, the CSI request field may indicate a CSI-AperiodicTriggerState from the CSI-AperiodicTriggerStateList.

In some implementations, the CSI-AperiodicTriggerStateList in which a CSI-AperiodicTriggerState is indicated by DCI format 1_1 or DCI format 1_2 is different from the CSI-AperiodicTriggerStateList in which a CSI-AperiodicTriggerState is indicated by DCI format 0_1 or DCI format 0_2.

In some implementations, the carrier (s) configured in the CSI-ReportConfig identified by the reportConfigId included in the one or more CSI-AssociatedReportConfigInfo included in the one or more CSI-AperiodicTriggerState included in a CSI-AperiodicTriggerStateList should be associated with the cell in which the CSI-AperiodicTriggerStateList is configured. In some implementations, a carrier is associated with a cell if the parameter pucch-Cell in the configuration PDSCH-ServingCellConfig of the carrier is set to the cell.

In some implementations, when multiple UL carriers are configured to the UE and two UL carriers are configured with PUCCH, e.g., Primary Cell (PCell) /Special Cell (SpCell) and PUCCH SCell, A-CSI triggered by a DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 is transmitted on PCell/SpCell if the triggering DCI is received on a cell with PUCCH cell configured as PCell/SpCell, and it is transmitted on PUCCH SCell if the triggering DCI is received on a cell with PUCCH cell configured as PUCCH SCell. In some implementations, the Information Element (IE) pucch-Cell in the configuration PDSCH-ServingCellConfig is used to configure the PUCCH cell.

In some implementations, when multiple UL carriers are configured to the UE and two UL carriers are configured with PUCCH, i.e., PCell/SpCell and PUCCH SCell, A-CSI triggered by a DCI format 1_1, or DCI format 1_2 is transmitted on PCell/SpCell if the triggering DCI schedules a PDSCH with corresponding HARQ-ACK to be transmitted on PCell/SpCell, and it is transmitted on PUCCH SCell if the triggering DCI schedules a PDSCH with corresponding HARQ-ACK to be transmitted on PUCCH SCell.

In some aspects of the present implementations, a mechanism that supports a PUCCH resource specifically used for A-CSI transmission is provided.

In some implementations, a dedicated set (s) of PUCCH resources for A-CSI transmission may be configured to a UE. The mechanism for indication of the PUCCH resource for a triggered A-CSI may be implemented by one or more of the following approaches 1 to 8:

1. Using a new field in DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2.

2. Using a CSI request field in DCI format 1_1, or DCI format 1_2.

3. Using a PUCCH resource indicator field in DCI format 1_1, or DCI format 1_2.

4. Re-interpreting or reusing existing field (s) in DCI format 1_1 or DCI format 1_2 as an being an indication of the PUCCH resource for the triggered A-CSI.

5. Using PUCCH resource (s) configured in PUCCH-Config.

6. Using PUCCH resource (s) indicated in the CSI-ReportConfig identified by the reportConfigId included in the triggered CSI-AperiodicTriggerState.

7. Using PUCCH resource (s) indicated in CSI-AssociatedReportConfigInfo in the triggered CSI-AperiodicTriggerState.

8. Using PUCCH resource (s) indicated in the triggered CSI-AperiodicTriggerState.

In some implementations, one or more PUCCH resources are configured in a PUCCH configuration (e.g., PUCCH-Config) for A-CSI transmission, and a new field in DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 is used for indicating a PUCCH resource from the one or more PUCCH resources configured for A-CSI transmission in PUCCH-Config. In some implementations, one or more PUCCH resource sets are configured in PUCCH-Config for A-CSI transmission, and a new field in DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 is used for indicating a PUCCH resource from the PUCCH resources in a PUCCH resource set configured in PUCCH-Config. The PUCCH resource set is determined from the payload size of the triggered A-CSI and the overlapping PUCCH, including PUCCH for HARQ-ACK, periodic CSI, SR, etc. Threshold values of payload size may be configured for determination of PUCCH resource set. For example, when three PUCCH resource sets are configured, two threshold values will be configured, where a first threshold value is smaller than a second threshold value. If the total payload size is less than or equal to the first threshold value, the first PUCCH resource set will be used. If the total payload size is greater than the first threshold value but less than or equal to the second threshold value, the second PUCCH resource set will be used. If the total payload size is less than or equal to 1706, the third PUCCH resource set will be used.

In some implementations, one or more PUCCH resources are configured in PUCCH-Config for A-CSI, and some bits in CSI request field in DCI format 1_1 or DCI format 1_2 are used for indicating a PUCCH resource from the one or more PUCCH resources configured for A-CSI in PUCCH-Config.

In some implementations, one or more PUCCH resources are configured in PUCCH-Config for A-CSI, and PUCCH resource indicator field in DCI format 1_1, or DCI format 1_2 is used for indicating a PUCCH resource from the one or more PUCCH resources configured for A-CSI in PUCCH-Config when the triggering DCI does not schedule a PDSCH. In some implementations, PDSCH is not scheduled when all bits of frequency domain resource assignment are set to 0 for resource allocation type 0 or set to 1 for resource allocation type 1. In some implementations, time domain resource assignment field is used for indicating a PUCCH resource when the triggering DCI does not schedule a PDSCH.

In some implementations, one or more PUCCH resources are indicated by an IE, e.g., pucch-CSI-ResourceList, included in the IE reportConfigType in the IE CSI-ReportConfig identified by the identifier reportConfigId included in the triggered CSI-AperiodicTriggerState. In some implementations, a new field in DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 is used for selecting a PUCCH resource from the one or more PUCCH resources. In some implementations, when more than one IE CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the one or more PUCCH resources indicated by the CSI-ReportConfig identified by the reportConfigId with smallest value among the reportConfigId in the more than one CSI-AssociatedReportConfigInfo are used. In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the one or more PUCCH resources indicated by the CSI-ReportConfig identified by the reportConfigId included in the first CSI-AssociatedReportConfigInfo are used.

In some implementations, one or more PUCCH resources are indicated by an IE, e.g., pucch-CSI-ResourceList, included in reportConfigType in the CSI-ReportConfig identified by the reportConfigId included in the triggered CSI-AperiodicTriggerState. In some implementations, an IE, e.g., pucch-CSI-Resource, in a CSI-AssociatedReportConfigInfo in the triggered CSI-AperiodicTriggerState for selecting a PUCCH resource from the one or more PUCCH resources. In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the PUCCH resource selecting from the one or more PUCCH resources indicated by the CSI-ReportConfig identified by the reportConfigId with smallest value among the reportConfigId in the more than one CSI-AssociatedReportConfigInfo are used. In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the PUCCH resource selecting from the one or more PUCCH resources indicated by the CSI-ReportConfig identified by the reportConfigId included in the first CSI-AssociatedReportConfigInfo are used. In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, only one CSI-AssociatedReportConfigInfo includes pucch-CSI-Resource.

In some implementations, one or more PUCCH resources are indicated by an IE, e.g., pucch-CSI-ResourceList, included in reportConfigType in the CSI-ReportConfig identified by the reportConfigId included in the triggered CSI-AperiodicTriggerState. In some implementations, an IE, e.g., pucch-CSI-Resource, is included in the triggered CSI-AperiodicTriggerState for selecting a PUCCH resource from the one or more PUCCH resources. In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the one or more PUCCH resources indicated by the CSI-ReportConfig identified by the reportConfigId with smallest value among the reportConfigId in the more than one CSI-AssociatedReportConfigInfo are used for selection of PUCCH resource. In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the one or more PUCCH resources indicated by the CSI-ReportConfig identified by the reportConfigId included in the first CSI-AssociatedReportConfigInfo are used for selection of PUCCH resource.

In some implementations, the one or more PUCCH resources indicated by an IE, e.g., pucch-CSI-ResourceList, included in reportConfigType in a CSI-ReportConfig described above includes multiple PUCCH resource set, and UE first determines the PUCCH resource set by the total payload size of A-CSI and overlapping UCI to be multiplexed on the PUCCH resource for A-CSI, then UE selects a PUCCH resource from the determined PUCCH resource set based on the mechanism (s) described above.

In some aspects of the present implementations, a mechanism for indication of the slot offset for the PUCCH resource for a triggered A-CSI may be implemented according to one or more of the following approaches1 to 8:

2. Using CSI request field in DCI format 1_1, or DCI format 1_2.

3. Using PDSCH-to-HARQ_feedback timing indicator field in DCI format 1_1, or DCI format 1_2.

4. Re-interpreting or reusing existing field (s) in DCI format 1_1, or DCI format 1_2 an being the indication.

5. Using a list (e.g., IE reportSlotOffsetList) configured in the PUCCH configuration (e.g., IE PUCCH-Config) .

6. Using a list (e.g., IE reportSlotOffsetList) configured in the configuration (e.g., IE CSI-ReportConfig) identified by the identifier (e.g., reportConfigId) included in the triggered A-CSI trigger state (e.g., CSI-AperiodicTriggerState) .

7. Using a list (e.g., IE reportSlotOffsetList) configured in the parameter CSI-AssociatedReportConfigInfo in the triggered CSI-AperiodicTriggerState.

8. Using a list (e.g., IE reportSlotOffsetList) configured in the triggered CSI-AperiodicTriggerState.

In some implementations, the reportSlotOffsetList is configured in PUCCH-Config for A-CSI, and a new field in DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 is used for indicating the offset to the slot in which PUCCH resource for A-CSI is transmitted from the slot in which the A-CSI triggering DCI is received.

In some implementations, the reportSlotOffsetList is configured in PUCCH-Config for A-CSI, and some bits in CSI request field in DCI format 1_1 or DCI format 1_2 are used for indicating the offset to the slot in which PUCCH resource for A-CSI is transmitted from the slot in which the A-CSI triggering DCI is received.

In some implementations, the reportSlotOffsetList is configured in PUCCH-Config for A-CSI, and a PDSCH-to-HARQ_feedback timing indicator field in DCI format 1_1, or DCI format 1_2 is used for indicating the offset to the slot in which PUCCH resource for A-CSI is transmitted from the slot in which the A-CSI triggering DCI is received when the triggering DCI does not schedule a PDSCH. In some implementations, PDSCH is not scheduled when all bits of frequency domain resource assignment are set to 0 for resource allocation type 0 or set to 1 for resource allocation type 1. In some implementations, time domain resource assignment field is used for indicating the offset to the slot in which PUCCH resource for A-CSI is transmitted from the slot in which the A-CSI triggering DCI is received when the triggering DCI does not schedule a PDSCH.

In some implementations, the reportSlotOffsetList is included in reportConfigType in the CSI-ReportConfig identified by the reportConfigId included in the triggered CSI-AperiodicTriggerState. In some implementations, a new field in DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 is used for selecting a slot offset from the reportSlotOffsetList. In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the reportSlotOffsetList included in the CSI-ReportConfig identified by the reportConfigId with smallest value among the reportConfigId in the more than one CSI-AssociatedReportConfigInfo is used for selection of the slot offset. In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the reportSlotOffsetList included in the CSI-ReportConfig identified by the reportConfigId included in the first CSI-AssociatedReportConfigInfo is used for selection of the slot offset. In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the reportSlotOffsetList included in the CSI-ReportConfig, in which the PUCCH resource used for the triggered A-CSI is indicated, is used for selection of the slot offset. In some implementations, when more than one IE CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the one or more reportSlotOffsetList included in the CSI-ReportConfig identified by the one or more reportConfigId included in the one or more CSI-AssociatedReportConfigInfo are all used for selection of a slot offset, and the slot offset of the PUCCH resource is determined by selecting the maximum value of the offsets selecting from each reportSlotOffsetList.

In some implementations, the reportSlotOffsetList is included in reportConfigType in the CSI-ReportConfig identified by the reportConfigId included in the triggered CSI-AperiodicTriggerState. In some implementations, an IE, e.g., reportSlotOffset, is included in a CSI-AssociatedReportConfigInfo in the triggered CSI-AperiodicTriggerState for selecting a slot offset from the reportSlotOffsetList. In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the slot offset selecting from the reportSlotOffsetList included in the CSI-ReportConfig identified by the reportConfigId with smallest value among the reportConfigId in the more than one CSI-AssociatedReportConfigInfo is used. In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the slot offset selecting from the reportSlotOffsetList included in the CSI-ReportConfig identified by the reportConfigId included in the first CSI-AssociatedReportConfigInfo is used. In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, only one CSI-AssociatedReportConfigInfo includes reportSlotOffset. In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the slot offset with largest value of the slot offsets, each selecting from each reportSlotOffsetList included in each CSI-ReportConfig identified by each reportConfigId in each of the more than one CSI-AssociatedReportConfigInfo, is used.

In some implementations, the reportSlotOffsetList is included in reportConfigType in the CSI-ReportConfig identified by the reportConfigId included in the triggered CSI- AperiodicTriggerState. In some implementations, an IE, e.g., reportSlotOffset, is included in the triggered CSI-AperiodicTriggerState for selecting a slot offset from the reportSlotOffsetList. In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the reportSlotOffsetList included in the CSI-ReportConfig identified by the reportConfigId with smallest value among the reportConfigId in the more than one CSI-AssociatedReportConfigInfo are used for selection of the slot offset. In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the reportSlotOffsetList included in the CSI-ReportConfig identified by the reportConfigId included in the first CSI-AssociatedReportConfigInfo are used for selection of the slot offset.

In some aspects of the present implementations, a mechanism that supports using PUCCH for HARQ-ACK for A-CSI transmission is provided.

For example, the total number of bits of HARQ-ACK and triggered A-CSI is used for determination of the PUCCH resource set from which the PUCCH resource is selected based on PUCCH resource indicator in the DCI triggering the A-CSI.

In some implementations, a triggered A-CSI is multiplexed on a PUCCH for HARQ-ACK when the PUCCH format configuration is configured with simultaneousHARQ-ACK-CSI and set to true. Otherwise, the triggered A-CSI is not multiplexed on the PUCCH for HARQ-ACK.

In some implementations, a triggered A-CSI is multiplexed on a PUCCH for HARQ-ACK when the payload size of HARQ-ACK, Scheduling Request (SR) and A-CSI for transmission on the selected PUCCH resource results in a code rate lower than or equal to the maxCodeRate of the PUCCH format configuration. Otherwise, the triggered A-CSI is not multiplexed on the PUCCH for HARQ-ACK.

In order to reduce the size of Type-1 HARQ-ACK codebook when no PDSCH or SPS PDSCH release, or only a PDSCH or a SPS PDSCH release is received within M _A, c occasions for a PUCCH on which A-CSI is multiplexed, the following method may be used.

In some implementations, no PDSCH or SPS PDSCH release is received within M _A, c occasions for a PUCCH when only the A-CSI triggering DCI schedules PUCCH transmission in a slot/sub-slot and the A-CSI triggering DCI does not schedule a PDSCH. Only a PDSCH or a SPS PDSCH release is received within M _A, c occasions for a PUCCH when only the A-CSI triggering DCI schedules PUCCH transmission in a slot/sub-slot and the A-CSI triggering DCI schedules a PDSCH.

In some implementations, in case no PDSCH or SPS PDSCH release, or only a PDSCH or a SPS PDSCH release is received within M _A, c occasions for a PUCCH transmission for A-CSI, a Downlink Assignment Index (DAI) field may be included in DCI format 1_1 and used as a counter DAI if UE is enabled to transmit A-CSI on PUCCH for HARQ-ACK with Type-1 HARQ-ACK codebook. In some implementations, DAIForDCI-Format1-1 is included in PDSCH-Config to configure whether DAI is included in DCI format 1_1 when Type-1 HARQ-ACK codebook is used.

In some implementations, when no PDSCH or SPS PDSCH release is received within M _A, c occasions for a PUCCH, the counter DAI value may be set to 1, and UE does not multiplex the HARQ-ACK codebook on the PUCCH. In other words, UE only multiplex A-CSI and other overlapping UCI, if any, on the scheduled PUCCH.

In some implementations, when only a PDSCH or a SPS PDSCH release is received within M _A, c occasions for a PUCCH, the counter DAI value may be set to 1, and UE multiplexes only the HARQ-ACK bit for the PDSCH or for the SPS PDSCH release and the triggered A-CSI on the PUCCH.

In some aspects of the present implementations, a mechanism that supports triggering A-CSI transmission on PUCCH for Type-2 HARQ-ACK codebook without scheduling a PDSCH is provided.

For example, the DAI value in a first DCI triggering A-CSI on a first PUCCH without scheduling a PDSCH in a first monitoring occasion is set to the largest value of the DAI value in a second DCI scheduling a PDSCH with corresponding HARQ-ACK on the first PUCCH in the first monitoring occasion. In some implementations, when no DCI schedules a PDSCH in the same monitoring occasion as the first DCI, DAI value in the first DCI is set to the largest value of the DAI value in a second DCI scheduling a PDSCH with corresponding HARQ-ACK on the first PUCCH in a previous monitoring occasion closest to the first monitoring occasion. In some implementations, when no DCI schedules a PDSCH with corresponding HARQ-ACK on the first PUCCH, DAI value in the first DCI is set to 2 if DAI consists of 1 bit, and set to 4 if DAI consists of 2 bits.

In some implementations, the DAI value in a first DCI triggering A-CSI on a first PUCCH without scheduling a PDSCH in a first monitoring occasion is incremented based on the largest value of the DAI value in a second DCI scheduling a PDSCH with corresponding HARQ-ACK on the first PUCCH in the first monitoring occasion, and UE generates ACK in a Type-2 HARQ-ACK codebook for the first DCI. In some implementations, when no DCI schedules a PDSCH in the same monitoring occasion as the first DCI, DAI value in the first DCI is incremented based on the largest value of the DAI value in a second DCI scheduling a PDSCH with corresponding HARQ-ACK on the first PUCCH in a previous monitoring occasion closest to the first monitoring occasion. In some implementations, DAI value in the first DCI is incremented based on the largest value of the DAI value in a second DCI scheduling a PDSCH with corresponding HARQ-ACK on the first PUCCH in a previous monitoring occasion closest to the first monitoring occasion, regardless of other DCI in the first monitoring occasion. In some implementations, when no DCI schedules a PDSCH with corresponding HARQ-ACK on the first PUCCH in monitoring occasions earlier than the first monitoring occasion, DAI value in the first DCI is set to 1. In some implementations, when no DCI schedules a PDSCH with corresponding HARQ-ACK on the first PUCCH, DAI value in the first DCI is set to 1.

In some implementations, the DAI value in DCI that does not schedule a PDSCH is not considered by the UE for Type-2 HARQ-ACK construction.

In some aspects of the present implementations, for a PUCCH resource specifically used for A-CSI transmission, a priority indication may be based on the priority indicator field in the DCI triggering A-CSI. In the present disclosure, triggering A-CSI may mean that an A-CSI reporting process is triggered. Once the A-CSI reporting process is triggered, the UE may start A-CSI reporting by transmitting A-CSI on specific UL resource (s) .

In some implementations, one or more PUCCH resources for A-CSI are configured in both the first PUCCH-Config and the second PUCCH-Config, and a new field in DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 is used for indicating a PUCCH resource from the one or more PUCCH resources configured for A-CSI in the first PUCCH-Config if priority indication in the DCI indicates 0, and is used for indicating a PUCCH resource from the one or more PUCCH resources configured for A-CSI in the second PUCCH-Config if priority indication in the DCI indicates 1.

In some implementations, priority of a PUCCH transmission is determined by the PUCCH-Config in which the PUCCH is configured. For example, one or more PUCCH resources are indicated by an IE, e.g., pucch-CSI-ResourceList, included in reportConfigType in the CSI- ReportConfig identified by the reportConfigId included in the triggered CSI-AperiodicTriggerState, and an IE, e.g., pucch-CSI-Resource, in a CSI-AssociatedReportConfigInfo in the triggered CSI-AperiodicTriggerState is used to select a PUCCH resource from the one or more PUCCH resources. If the selected PUCCH resource is in the first PUCCH-Config, the PUCCH transmission is of priority 0, and if the selected PUCCH resource is in the second PUCCH-Config, the PUCCH transmission is of priority 1.

In some implementations, priority of a PUCCH transmission is determined by an explicit parameter of the PUCCH resource configuration. For example, one or more PUCCH resources are indicated by an IE, e.g., pucch-CSI-ResourceList, included in reportConfigType in the CSI-ReportConfig identified by the reportConfigId included in the triggered CSI-AperiodicTriggerState, and an IE, e.g., pucch-CSI-Resource, in a CSI-AssociatedReportConfigInfo in the triggered CSI-AperiodicTriggerState is used to select a PUCCH resource from the one or more PUCCH resources. If the selected PUCCH resource is configured with priority index 0, the PUCCH transmission is of priority 0, and if the selected PUCCH resource is configured with priority index 1, the PUCCH transmission is of priority 1.

In some implementations, priority of a PUCCH transmission is determined by the triggered state configuration. For example, phy-PriorityIndex may be configured in a CSI-AperiodicTriggerState. In some implementations, the PUCCH resource indicated by DCI or by the triggered CSI-AperiodicTriggerState should be within a sub-slot if the PUCCH-Config corresponding to the HARQ-ACK codebook of the same priority as the priority of the triggered A-CSI indicated by phy-PriorityIndex is configured with subslotLengthForPUCCH-r16. In some implementations, phy-PriorityIndex may be configured in CSI-AssociatedReportConfigInfo. Then if more than one CSI-AssociatedReportConfigInfo is included in a CSI-AperiodicTriggerState, the phy-PriorityIndex in the more than one CSI-AssociatedReportConfigInfo should be configured to be the same.

In some implementations, priority of a PUCCH transmission is determined by an explicit parameter, e.g., phy-PriorityIndex, included in reportConfigType in the CSI-ReportConfig identified by the reportConfigId included in the triggered CSI-AperiodicTriggerState. In some implementations, one or more PUCCH resources for A-CSI are configured in both the first PUCCH-Config and the second PUCCH-Config, and a new field in DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 is used for indicating a PUCCH resource from the one or more PUCCH resources with low physical layer priority configured for A-CSI in the first PUCCH-Config if phy-PriorityIndex indicates 0, and is used for indicating a PUCCH resource from the one or more PUCCH resources with high physical layer priority configured for A-CSI in the second PUCCH-Config if phy-PriorityIndex indicates 1. In some implementations, one or more PUCCH resources for A-CSI are configured in only a PUCCH-Config, e.g., the first PUCCH-Config, and a new field in DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 is used for indicating a PUCCH resource from the one or more PUCCH resources with low physical layer priority configured for A-CSI in the first PUCCH-Config if phy-PriorityIndex indicates 0, and is used for indicating a PUCCH resource from the one or more PUCCH resources with high physical layer priority configured for A-CSI in the first PUCCH-Config if phy-PriorityIndex indicates 1. In some implementations, when more than one CSI-AssociatedReportConfigInfo is included in a CSI-AperiodicTriggerState, the all phy-PriorityIndex in each CSI-ReportConfig identified by each reportConfigId included in each CSI-AssociatedReportConfigInfo should be configured to be the same. In some implementations, one or more PUCCH resources are indicated by an IE, e.g., pucch-CSI-ResourceList, included in reportConfigType in the CSI-ReportConfig identified by the reportConfigId included in the triggered CSI-AperiodicTriggerState, and an IE, e.g., pucch-CSI-Resource, in a CSI-AssociatedReportConfigInfo in the triggered CSI-AperiodicTriggerState is used to select a PUCCH resource from the one or more PUCCH resources. In some implementations, one or more PUCCH resources for A-CSI are configured in only a PUCCH-Config, e.g., the first PUCCH-Config, and pucch-CSI-Resource is used for indicating a PUCCH resource from the one or more PUCCH resources with low physical layer priority configured for A-CSI in the first PUCCH-Config if phy-PriorityIndex indicates 0, and is used for indicating a PUCCH resource from the one or more PUCCH resources with high physical layer priority configured for A-CSI in the first PUCCH-Config if phy-PriorityIndex indicates 1. In some implementations, the PUCCH resource indicated by DCI or by the triggered CSI-AperiodicTriggerState should be within a sub-slot if the PUCCH-Config corresponding to the HARQ-ACK codebook of the same priority as the priority of the triggered A-CSI indicated by phy-PriorityIndex is configured with the IE subslotLengthForPUCCH-r16.

In some implementations, both of the CSI-HighAperiodicTriggerStateList and the CSI-LowAperiodicTriggerStateList are configured to a UE, and the priority of a PUCCH transmission is of priority index 0 if the PUCCH is indicated by CSI-LowAperiodicTriggerStateList, and the priority of a PUCCH transmission is of priority index 1 if the PUCCH is indicated by CSI-HighAperiodicTriggerStateList. In some implementations, if priority indication in the DCI indicates 0, a triggered state contained in CSI-LowAperiodicTriggerStateList is indicated by CSI request field, and if priority indication in the DCI indicates 1, a triggered state contained in CSI-HighAperiodicTriggerStateList is indicated by CSI request field. In some implementations, different subsets of codepoint in CSI request field may be mapped to trigger state in either CSI-HighAperiodicTriggerStateList or CSI-LowAperiodicTriggerStateList. In some implementations, mapping of the codepoints in CSI request field to the trigger states in the two lists may be updated by Medium Access Control (MAC) Control Element (CE) .

In some implementations, the IE reportSubslotOffsetList may be included in reportConfigType in the CSI-ReportConfig identified by the reportConfigId included in the triggered CSI-AperiodicTriggerState. When PUCCH-Config corresponding to the HARQ-ACK codebook of high priority (with priority index 1) is configured with subslotLengthForPUCCH-r16, if reportSubslotOffsetList is included in reportConfigType in the CSI-ReportConfig identified by the reportConfigId included in the triggered CSI-AperiodicTriggerState, the PUCCH resource indicated by DCI or by the triggered CSI-AperiodicTriggerState is with priority index 1. Otherwise, the PUCCH resource is with priority index 0.

In some aspects of the present implementations, for a PUCCH resource specifically used for A-CSI transmission, the subslot in which the PUCCH is located may be derived by an offset from the subslot overlapping with the end of the DCI triggering the A-CSI, where the offset is in unit of subslots and the value of the offset may be indicated by an index to a list of offsets, e.g., reportSlotOffsetList.

In some implementations, the reportSubslotOffsetList may be included in reportConfigType in the CSI-ReportConfig identified by the reportConfigId included in the triggered CSI-AperiodicTriggerState. If reportSubslotOffsetList is included in reportConfigType in the CSI-ReportConfig identified by the reportConfigId included in the triggered CSI-AperiodicTriggerState, the A-CSI triggering DCI indicates an offset value from reportSubslotOffsetList and the indicated offset is in unit of subslots. Otherwise, the A-CSI triggering DCI indicates an offset value from reportslotOffsetList included in reportConfigType in the CSI-ReportConfig identified by the reportConfigId included in the triggered CSI-AperiodicTriggerState, and the indicated offset is in unit of slots. In some implementations, when more than one CSI-AssociatedReportConfigInfo is included in a CSI-AperiodicTriggerState, reportSubslotOffsetList should be included in all CSI-ReportConfig identified by all reportConfigId included in every CSI-AssociatedReportConfigInfo if any one of the CSI-ReportConfig includes reportSubslotOffsetList. In some implementations, when all CSI-ReportConfig identified by all reportConfigId included in every CSI-AssociatedReportConfigInfo include reportSubslotOffsetList, the DCI indicates an offset value from reportSubslotOffsetList and the indicated offset is in unit of subslots. Otherwise, the A-CSI triggering DCI indicates an offset value from reportslotOffsetList and the indicated offset is in unit of slots. In some implementations, the length of a sub-slot is the same as the subslotLengthForPUCCH-r16 configured in the first PUCCH-Config. In some implementations, the length of a sub-slot is the same as the subslotLengthForPUCCH-r16 configured in the second PUCCH-Config.

In some implementations, reportSubslotOffsetList may be included in reportConfigType in the CSI-ReportConfig identified by the reportConfigId included in the triggered CSI-AperiodicTriggerState. When the PUCCH-Config corresponding to the HARQ-ACK codebook of high priority (with priority index 1) is configured with subslotLengthForPUCCH-r16, if A-CSI triggering DCI or the trigger state indicates a PUCCH transmission with priority 1, the A-CSI triggering DCI indicates an offset value from reportSubslotOffsetList and the indicated offset is in unit of subslots. Otherwise, the A-CSI triggering DCI indicates an offset value from reportslotOffsetList and the indicated offset is in unit of slots.

In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the offset with largest value of the offsets, each selecting from each reportSubSlotOffsetList included in each CSI-ReportConfig identified by each reportConfigId in each of the more than one CSI-AssociatedReportConfigInfo, is used, and the offset is in unit of sub-slots. In some implementations, when more than one CSI-AssociatedReportConfigInfo are included in the triggered CSI-AperiodicTriggerState, the offset with largest duration of the offsets, each in unit of slots if selecting from each reportSlotOffsetList or in unit of sub-slots if selecting from reportSubSlotOffsetList included in each CSI-ReportConfig identified by each reportConfigId in each of the more than one IE CSI- AssociatedReportConfigInfo, is used.

In some aspects of the present implementations, for a PUCCH resource used for A-CSI transmission, when overlapping with another PUCCH or PUSCH with the same physical layer priority, the mechanisms described below may be used for multiplexing overlapping channels with the same physical layer priority.

For example, when an A-CSI PUCCH overlaps with a periodic CSI or semi-persistent CSI on PUCCH, the periodic CSI or semi-persistent CSI on PUCCH is multiplexed on the A-CSI PUCCH.

For example, when an A-CSI PUCCH overlaps with more than one CSI reports on PUCCH resource configured by multi-CSI-PUCCH-ResourceList, the more than one CSI reports are multiplexed on the A-CSI PUCCH.

For example, when an A-CSI PUCCH overlaps with a SPS HARQ-ACK PUCCH, the SPS HARQ-ACK is multiplexed on the A-CSI PUCCH.

For example, when an A-CSI PUCCH overlaps with a SR PUCCH, the SR is multiplexed on the A-CSI PUCCH.

Resource determination for a PUCCH for A-CSI (or an “A-CSI PUCCH” ) in the above scenarios may be the following. For example, one or more PUCCH resource sets are configured in PUCCH-Config for A-CSI, and a new field in DCI format 1_1, DCI format 0_1, DCI format 1_2, or DCI format 0_2 is used for indicating a PUCCH resource from the PUCCH resources in a PUCCH resource set configured in PUCCH-Config. The PUCCH resource set may be determined from the payload size of the triggered A-CSI and the overlapping PUCCH. Threshold values of payload size may be configured for determination of PUCCH resource set. For example, when three PUCCH resource sets are configured, two threshold values will be configured, where a first threshold value is smaller than a second threshold value. If the total payload size is less than or equal to the first threshold value, the first PUCCH resource set will be used. If the total payload size is greater than the first threshold value but less than or equal to the second threshold value, the second PUCCH resource set will be used. If the total payload size is less than or equal to 1706, the third PUCCH resource set will be used. In some implementations, a UE may determine the number of Physical Resource Blocks (PRBs) for the A-CSI PUCCH and the number of CSI reports to be multiplexed on A-CSI PUCCH with corresponding PUCCH overlapping with A-CSI PUCCH.

For example, if

the UE may transmit the SR and CSI reports bits by selecting the minimum number

of the

PRBs satisfying

as described in Clauses 9.2.3 and 9.2.5.1 in TS 38.213. Otherwise, the UE may select

CSI report (s) , from the

CSI reports, for transmission together with HARQ-ACK and SR in ascending priority value as specified in TS 38.214, where the value of

satisfies

and

where O _{CRC, CSI-part1, N} is a number of CRC bits corresponding to

UCI bits, and O _{CRC, CSI-part1, N+1} is a number of CRC bits corresponding to

UCI bits. In some implementations, the A-CSI report (s) triggered for transmission of PUCCH is selected regardless of the priority, and other overlapping CSI is selected as described above.

In some implementations, if an A-CSI PUCCH overlaps with a periodic CSI or a semi-persistent CSI on PUCCH, the periodic CSI or the semi-persistent CSI is not transmitted.

In some implementations, when a periodic CSI or semi-persistent CSI on PUCCH overlaps with an A-CSI PUCCH and a HARQ-ACK PUCCH, and the A-CSI PUCCH and the HARQ-ACK PUCCH are not overlapping with each other, the periodic CSI or semi-persistent CSI is multiplexed on the HARQ-ACK PUCCH. In some implementations, the periodic CSI or semi-persistent CSI is multiplexed on the A-CSI PUCCH. In some implementations, UE is not expected to be scheduled with an A-CSI PUCCH and a HARQ-ACK PUCCH not overlapping with each other but overlapping with a periodic CSI or semi-persistent CSI on PUCCH.

In some implementations, when a SPS HARQ-ACK PUCCH overlaps with an A-CSI PUCCH and a HARQ-ACK PUCCH, and the A-CSI PUCCH and the HARQ-ACK PUCCH are not overlapping with each other, the SPS HARQ-ACK is multiplexed on the HARQ-ACK PUCCH. In some implementations, the SPS HARQ-ACK is multiplexed on the A-CSI PUCCH. In some implementations, UE is not expected to be scheduled with an A-CSI PUCCH and a HARQ-ACK PUCCH not overlapping with each other but overlapping with a SPS HARQ-ACK PUCCH.

In some implementations, when an SR PUCCH overlaps with an A-CSI PUCCH and a HARQ-ACK PUCCH, and the A-CSI PUCCH and the HARQ-ACK PUCCH are not overlapping with each other, the SR is multiplexed on the HARQ-ACK PUCCH. In some implementations, the SR is multiplexed on the A-CSI PUCCH. In some implementations, UE is not expected to be scheduled with an A-CSI PUCCH and a HARQ-ACK PUCCH not overlapping with each other but overlapping with a SR PUCCH.

In some implementations, when an A-CSI PUCCH scheduled by first DCI overlaps with a HARQ-ACK PUCCH scheduled by second DCI, the A-CSI is multiplexed on the HARQ-ACK PUCCH. In some implementations, the HARQ-ACK is multiplexed on A-CSI PUCCH. In some implementations, the A-CSI is multiplexed on the HARQ-ACK PUCCH if the second DCI ends later than the first DCI, and the HARQ-ACK is multiplexed on A-CSI PUCCH if the first DCI ends later than the second DCI.

In some implementations, when there is a group of overlapping PUCCHs in a slot including configured PUCCH resources for HARQ-ACK, configured PUCCH resources for A-CSI, and configured PUCCH resources for other UCI, e.g., periodic CSI, PUCCH resource, and a DCI scheduling a PUCCH in the slot for HARQ-ACK and a DCI triggering A-CSI on a PUCCH in the slot are received, PUCCH resource determination for A-CSI is performed first assuming no overlapping HARQ-ACK PUCCH. In other words, UE determines PUCCH resource set for A-CSI considering the total payload size of A-CSI and the overlapping PUCCH for periodic CSI. After UE selected a PUCCH resource for A-CSI and the overlapping PUCCH for periodic CSI, a new group of overlapping PUCCHs is determined from the group of overlapping PUCCHs, by excluding the overlapping PUCCHs that is multiplexed on A-CSI PUCCH (PUCCH for periodic CSI in this example) , and the configured PUCCH resources for A-CSI that are not selected. The UE then determines PUCCH resource set for HARQ-ACK considering the total payload size of HARQ-ACK, other overlapping PUCCH, and the A-CSI and the periodic CSI multiplexed with it, if the selected PUCCH for A-CSI is overlapping with the configured PUCCH resources for HARQ-ACK, and UE selects HARQ-ACK resource based on the scheduling DCI. Otherwise, the A-CSI and the periodic CSI multiplexed with it are not considered for PUCCH resource set determination for HARQ-ACK, and UE transmits HARQ-ACK PUCCH and A-CSI PUCCH separately.

In some implementations, PUCCH resource determination for A-CSI is performed first without considering the overlapping PUCCH for periodic CSI when there is configured HARQ-ACK PUCCH resources in the group, or when there is configured HARQ-ACK PUCCH resources in the group overlapping with PUCCH for periodic CSI. After UE selected a PUCCH resource for A-CSI, a new group of overlapping PUCCHs is determined from the group of overlapping PUCCHs, by excluding the configured PUCCH resources for A-CSI that are not selected. The UE then determines PUCCH resource set for HARQ-ACK considering the total payload size of HARQ-ACK, other overlapping PUCCH (periodic CSI in this example) , and the A-CSI, if the selected PUCCH for A-CSI is overlapping with the configured PUCCH resources for HARQ-ACK. Otherwise, the A-CSI is not considered for PUCCH resource set determination for HARQ-ACK, and UE selects a HARQ-ACK PUCCH for transmission considering only the overlapping periodic CSI based on the scheduling DCI, and transmit A-CSI PUCCH separately. If the selected HARQ-ACK PUCCH resource is not overlapping with the PUCCH resource for periodic CSI, the periodic CSI is multiplexed on the selected A-CSI PUCCH, if they are overlapping with each other, and the overlapping PUCCH (periodic CSI) is dropped if multiplexing on A-CSI PUCCH would result in a code rate larger than maxCodeRate of the A-CSI PUCCH.

In some implementations, PUCCH resource determination for HARQ-ACK is performed first considering the overlapping PUCCH for periodic CSI and the configured A-CSI PUCCH resources in the PUCCH resource set (s) for A-CSI that can contain the payload size of the triggered A-CSI. In other words, PUCCH resource set is determined considering the total payload size of HARQ-ACK, other overlapping PUCCH (periodic CSI in this example) , and triggered A-CSI, if any of the PUCCH resources in the PUCCH resource set (s) for A-CSI that can contain the payload size of the triggered A-CSI is overlapping with the configured HARQ-ACK PUCCH resources. UE then selects a HARQ-ACK PUCCH resource from the determined HARQ-ACK PUCCH resource set based on the scheduling DCI. If UE selects a HARQ-ACK PUCCH resource overlapping with a configured PUCCH resource in the PUCCH resource set (s) for A-CSI that can contain the payload size of the triggered A-CSI, the A-CSI is multiplexed on the HARQ-ACK PUCCH. Otherwise, after UE selected a PUCCH resource for HARQ-ACK, a new group of overlapping PUCCHs is determined from the group of overlapping PUCCHs, by excluding the overlapping PUCCHs that is multiplexed on HARQ-ACK PUCCH (PUCCH for periodic CSI in this example) , and the configured PUCCH resources for HARQ-ACK PUCCH that are not selected. The UE then determines PUCCH resource set for A-CSI considering the total payload size of A- CSI, other overlapping PUCCH, if any. PUCCH resource is then selected based on the A-CSI triggering DCI for A-CSI and other overlapping PUCCH in the new group of overlapping PUCCHs.

In some implementations, PUCCH resource determination for HARQ-ACK is performed first considering the overlapping PUCCH for periodic CSI and the configured A-CSI PUCCH resources in the PUCCH resource set (s) for A-CSI that can contain the payload size of the triggered A-CSI. In other words, PUCCH resource set is determined considering the total payload size of HARQ-ACK, other overlapping PUCCH (periodic CSI in this example) , and triggered A-CSI, if any of the PUCCH resources in the PUCCH resource set (s) for A-CSI that can contain the payload size of the triggered A-CSI is overlapping with the configured HARQ-ACK PUCCH resources. UE then selects a HARQ-ACK PUCCH resource from the determined HARQ-ACK PUCCH resource set based on the scheduling DCI for multiplexing HARQ-ACK PUCCH and other overlapping PUCCH (periodic CSI in this example) . After UE selected a PUCCH resource for HARQ-ACK, a new group of overlapping PUCCHs is determined from the group of overlapping PUCCHs, by excluding the configured PUCCH resources for HARQ-ACK that are not selected and other UCI multiplexed on the HARQ-ACK PUCCH (periodic CSI in this example) . The UE then determines PUCCH resource set for A-CSI considering the total payload size of A-CSI, other overlapping PUCCH other than the selected HARQ-ACK PUCCH, if any. UE then select a PUCCH resource for A-CSI from the PUCCH resources in the determined PUCCH resource set based on the A-CSI triggering DCI. If the selected A-CSI PUCCH resource is overlapping with the PUCCH resource for HARQ-ACK, the A-CSI and the multiplexed UCI, if any, is multiplexed on PUCCH resource for HARQ-ACK. Otherwise, A-CSI PUCCH and HARQ-ACK PUCCH are separately transmitted.

In some implementations, a group of overlapping PUCCHs is constructed by selecting a PUCCH resource A with earliest starting symbol and longest duration among the PUCCH resources with the same earliest starting symbol, and selecting the PUCCH resources overlapping with PUCCH resource A. Multiplexing procedure within a slot is performed from the start of a slot. UE constructs a first group of overlapping PUCCH resources and determines a one or more PUCCH resources for transmission as in the above-described implementations, and if the determined PUCCH resource (s) overlaps with other PUCCH resources not in the group of overlapping PUCCH resources, UE constructs a second group of overlapping PUCCH resources including the determined PUCCH resource (s) from the first group of overlapping PUCCH resources, and UE determines PUCCH resources for transmission for the second group of overlapping PUCCH resources, and the procedure goes on until no PUCCH resource overlaps with the determined PUCCH resource (s) from a group of overlapping PUCCHs.

In some implementations, when an A-CSI PUCCH overlaps with a semi-persistent CSI on PUSCH, the A-CSI PUCCH is transmitted and the semi-persistent CSI on PUSCH is dropped. In some implementations, when an A-CSI PUCCH overlaps with a PUSCH without A-CSI, the A-CSI is multiplexed on the PUSCH. In some implementations, when a first A-CSI PUCCH overlaps with a PUSCH with a second A-CSI, the first A-CSI is multiplexed on the PUSCH and the second A-CSI is dropped. In some implementations, the A-CSI PUCCH is transmitted and the PUSCH is dropped if the PUSCH is without UL-SCH. In some implementations, the A-CSI PUCCH is transmitted and the A-CSI triggered on PUSCH is multiplexed on the PUCCH. In some implementations, the first A-CSI is dropped. In some implementations, the first A-CSI is dropped if a first DCI triggering the first A-CSI ends earlier than a second DCI triggering the second A-CSI. In some implementations, the first A-CSI is multiplexed on the PUSCH and the second A-CSI is dropped if a first DCI triggering the first A-CSI ends later than a second DCI triggering the second A-CSI. In some implementations, the first A-CSI is multiplexed with the second A-CSI on the PUSCH if a first DCI triggering the first A-CSI ends later than a second DCI triggering the second A-CSI.

In some implementations, UE is not expected to be triggered with A-CSI on a PUCCH if UE is triggered with A-CSI on a PUSCH, and the PUSCH overlaps with the PUCCH, and UE is not expected to be triggered with A-CSI on a PUSCH if UE is triggered with A-CSI on a PUCCH, and the PUSCH overlaps with the PUCCH.

In some implementations, the first A-CSI is dropped if the first A-CSI has lower priority than the second A-CSI, while the first A-CSI is multiplexed on the PUSCH and the second A-CSI is dropped if the first A-CSI has higher priority than the second A-CSI. If the first A-CSI has equal priority as the second A-CSI, the above-described implementations may be used.

In some implementations, the first A-CSI is dropped if the first A-CSI has lower priority than the second A-CSI, while the first A-CSI is transmitted on the PUCCH and the second A-CSI is dropped if the first A-CSI has higher priority than the second A-CSI. If the first A-CSI has equal priority as the second A-CSI, the above-described implementations may be used.

In some implementations, the priority (value) of a CSI may be determined as the following:

CSI reports may be associated with a priority value Pri _iCCS (y, k, c, s) =2·N _cells·M _s·y+N _cells·M _s·k+M _s·c+s where

y=0 for aperiodic CSI reports to be carried on PUSCH or PUCCH, y=1 for semi-persistent CSI reports to be carried on PUSCH, y=2 for semi-persistent CSI reports to be carried on PUCCH and y=3 for periodic CSI reports to be carried on PUCCH;

k=0 for CSI reports carrying L1-RSRP or L1-SINR and k=1 for CSI reports not carrying L1-RSRP or L1-SINR;

c is the serving cell index and N _cells is the value of the higher layer parameter maxNrofServingCells;

s is the reportConfigID and M _s is the value of the higher layer parameter maxNrofCSI-ReportConfigurations.

A first CSI report is said to have priority over second CSI report if the associated Pri _iCSI (y, k, c, s) value is lower for the first report than for the second report.

In some implementations, the priority of a CSI may be determined similar as above, with definition of y value as the following:

y=0 for aperiodic CSI reports to be carried on PUCCH, y=1 for aperiodic CSI reports to be carried on PUSCH, y=2 for semi-persistent CSI reports to be carried on PUSCH, y=3 for semi-persistent CSI reports to be carried on PUCCH and y=4 for periodic CSI reports to be carried on PUCCH.

In some other implementations, the priority of a CSI may be determined similar as above, with definition of y value as the following:

y=0 for aperiodic CSI reports to be carried on PUSCH, y=1 for aperiodic CSI reports to be carried on PUCCH, y=2 for semi-persistent CSI reports to be carried on PUSCH, y=3 for semi-persistent CSI reports to be carried on PUCCH and y=4 for periodic CSI reports to be carried on PUCCH.

In some aspects of the present implementations, a mechanism that supports using PUCCH for HARQ-ACK for transmission of A-CSI is provided.

For example, when a first DCI schedules a first PDSCH and a first PUCCH in a slot or a sub-slot for the corresponding HARQ-ACK in a HARQ-ACK codebook and the first DCI triggers A-CSI on the first PUCCH, and a second DCI schedules a second PDSCH and a second PUCCH in the slot or the sub-slot for corresponding HARQ-ACK in the same HARQ-ACK codebook, UE may multiplex A-CSI on the second PUCCH, and the second PUCCH may be selected by the UE based on a PUCCH resource indicator in the second DCI from the PUCCH resource set determined based on the total payload size of the A-CSI and the HARQ-ACK codebook, where the first PUCCH and the second PUCCH may be the same or different, and the second DCI ends no earlier than the first DCI.

In some implementations, when a first DCI triggers A-CSI on a first PUCCH in a slot or a sub-slot, and a second DCI schedules a first PDSCH and a second PUCCH in the slot or the sub-slot for corresponding HARQ-ACK in a HARQ-ACK codebook, UE may multiplex A-CSI on the second PUCCH, and the second PUCCH may be selected based on a PUCCH resource indicator in the second DCI from the PUCCH resource set determined based on the total payload size of the A-CSI and the HARQ-ACK codebook, where the first PUCCH and the second PUCCH may be the same or different, and the second DCI ends no earlier than the first DCI. In some implementations, UE is not expected to receive the second DCI after receiving the first DCI.

In some implementations, when a first DCI schedules a first PDSCH and a first PUCCH in a slot or a sub-slot for the corresponding HARQ-ACK in a HARQ-ACK codebook and the first DCI triggers A-CSI on the first PUCCH, and a second DCI schedules a second PDSCH and a second PUCCH in the slot or the sub-slot for corresponding HARQ-ACK in the same HARQ-ACK codebook, the second DCI includes the same A-CSI triggering information as in the first DCI, where the first PUCCH and the second PUCCH may be the same or different, and the second DCI ends no earlier than the first DCI.

In some implementations, when a first DCI triggers A-CSI on a first PUCCH in a slot or a sub-slot, and a second DCI schedules a first PDSCH and a second PUCCH in the slot or the sub-slot for corresponding HARQ-ACK in a HARQ-ACK codebook, the second DCI includes the same A-CSI triggering information as in the first DCI, where the first PUCCH and the second PUCCH may be the same or different, and the second DCI ends no earlier than the first DCI.

In some implementations, when UE receives DCIs with A-CSI triggering information for transmission on PUCCH in a slot, UE is not required to provide a valid CSI report or update the CSI report if the time duration from the end of the first DCI UE receives which triggers A-CSI transmission on PUCCH in a slot to the start of the PUCCH is smaller than CSI computation time.

Figure 1 illustrates a flowchart for a method 100 performed by a UE for A-CSI transmission, according to an implementation of the present disclosure. Although

actions

102 and 104 are illustrated as separate actions represented as independent blocks in Figure 1, these separately illustrated actions should not be construed as necessarily order dependent. The order in which the actions are performed in Figure 1 is not intended to be construed as a limitation, and any number of the disclosed blocks may be combined in any order to implement the method, or an alternate method. Moreover, each of

actions

102 and 104 may be performed independent of other actions and can be omitted in some implementations of the present disclosure.

In action 102, UE may receive, from a base station, Downlink Control Information (DCI) including a downlink assignment that schedules a PDSCH and a first PUCCH corresponding to the PDSCH.

In action 104, the UE may report A-CSI to the base station through the first PUCCH.

In some implementations, the first PUCCH is scheduled for transmitting a HARQ-ACK feedback for the PDSCH, as illustrated in Figure 2.

Method 100 may be advantageous to the UE for reducing latency and increasing reliability of downlink data transmission because the gNB can request the UE to provide the latest CSI for the gNB via a DCI scheduling a downlink data transmission such that the gNB can properly set the transmission configurations for a later downlink data (re) transmission. The method can also reduce the PDCCH blocking probability and enhance the spectral efficiency because A-CSI can be triggered without transmitting an uplink grant by the gNB and without transmitting a PUSCH by the UE.

Figure 2 is a schematic diagram illustrating a PDSCH 204 and a PUCCH 206 scheduled by a downlink assignment included in DCI received on a PDCCH 202, according to an example implementation of the present disclosure. The PUCCH 206 is scheduled for transmitting a HAQR-ACK feedback for the PDSCH 204 to indicate to the network that the data reception on the PDSCH 204 is successful or not. In the present implementation, the PUCCH 206 is also used to transmit A-CSI. For example, the A-CSI may be included in the HARQ-ACK feedback. In another example, the A-CSI and the HARQ-ACK feedback may be transmitted separately through the PUCCH 206.

In some other implementations, the downlink assignment further schedules a second PUCCH for transmitting a HARQ-ACK feedback for the PDSCH, and the first PUCCH is scheduled for transmitting the A-CSI and not for transmitting the HARQ ACK feedback for the PDSCH, as illustrated in Figure 3.

Figure 3 is a schematic diagram illustrating a PDSCH 304 and two

separate PUCCHs

306 and 308 scheduled by a downlink assignment included in DCI received on a PDCCH 302, according to an example implementation of the present disclosure. The PUCCH 306 is scheduled for transmitting a HAQR-ACK feedback for the PDSCH 304 to indicate to the network that the data reception on the PDSCH 304 is successful or not. In the present implementation, A-CSI is transmitted on the PUCCH 308 different from the PUCCH 306.

In some implementations, the DCI may include an indicator that indicates an A-CSI trigger state for reporting the A-CSI, where the A-CSI trigger state is associated with a reporting configuration that indicates a resource allocation of the first PUCCH. For example, the reporting configuration may be indicated by the identifier reportConfigId described in the present disclosure. In some implementations, an A-CSI trigger state may be (or correspond to) the IE CSI-AperiodicTriggerState illustrated in Figure 5.

In some implementations, reporting the A-CSI (as illustrated in action 104) is triggered by a CSI request included in the DCI.

Figure 4 is a diagram illustrating IEs (partially listed) contained in an IE CSI-ReportConfig, according to an example implementation of the present disclosure. Details of the IEs are described as follows:

carrier: Indicates in which serving cell the CSI-ResourceConfig indicated below are to be found. If the field is absent, the resources are on the same serving cell as this report configuration.

codebookConfig: Codebook configuration for Type-1 or Type-2 including codebook subset restriction. If the field codebookConfig-r16 is present, UE shall ignore the codebookConfig (without suffix) .

cqi-Table: Which CQI table to use for CQI calculation (see TS 38.214 [19] , clause 5.2.2.1) .

csi-IM-ResourcesForInterference: CSI IM resources for interference measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only CSI-IM resources. The bwp-Id in that CSI-ResourceConfig is the same value as the bwp-Id in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement.

nzp-CSI-RS-ResourcesForInterference: NZP CSI RS resources for interference measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only NZP-CSI-RS resources. The bwp-Id in that CSI-ResourceConfig is the same value as the bwp-Id in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement.

pucch-CSI-ResourceList: Indicates which PUCCH resource to use for reporting on PUCCH.

reportConfigType: Time domain behavior of reporting configuration.

reportFreqConfiguration: Reporting configuration in the frequency domain. (see TS 38.214 [19] , clause 5.2.1.4) .

reportQuantity: The CSI related quantities to report. see TS 38.214 [19] , clause 5.2.1. If the field reportQuantity-r16 is present, UE shall ignore reportQuantity (without suffix) .

reportSlotConfig: Periodicity and slot offset (see TS 38.214 [19] , clause 5.2.1.4) . If the field reportSlotConfig-v1530 is present, the UE shall ignore the value provided in reportSlotConfig (without suffix) .

reportSlotOffsetList, reportSlotOffsetListForDCI-Format0-1, reportSlotOffsetListForDCI-Format0-2: Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config. A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity.

Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config. A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19] , clause 6.1.2.1) . The field reportSlotOffsetList refers to DCI format 0_0, the field reportSlotOffsetListForDCI-Format0-1 refers to DCI format 0_1 and the field reportSlotOffsetListForDCI-Format0-2 refers to DCI format 0_2, respectively (see TS 38.214 [19] , clause 6.1.2.1) .

resourcesForChannelMeasurement: Resources for channel measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only NZP-CSI-RS resources and/or SSB resources. This CSI-ReportConfig is associated with the DL BWP indicated by bwp-Id in that CSI-ResourceConfig.

Figure 5 is a diagram illustrating IEs (partially listed) contained in an IE CSI-AperiodicTriggerState, according to an example implementation of the present disclosure. Details of the IEs are described as follows:

csi-IM-ResourcesForInterference: CSI-IM-ResourceSet for interference measurement. Entry number in csi-IM-ResourceSetList in the CSI-ResourceConfig indicated by csi-IM-ResourcesForInterference in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on) . The indicated CSI-IM-ResourceSet should have exactly the same number of resources like the NZP-CSI-RS-ResourceSet indicated in nzp-CSI-RS-ResourcesforChannel.

csi-SSB-ResourceSet: CSI-SSB-ResourceSet for channel measurements. Entry number in csi-SSB-ResourceSetList in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on) .

nzp-CSI-RS-ResourcesForInterference: NZP-CSI-RS-ResourceSet for interference measurement. Entry number in nzp-CSI-RS-ResourceSetList in the CSI-ResourceConfig indicated by nzp-CSI-RS-ResourcesForInterference in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on) .

qcl-info: List of references to TCI-States for providing the QCL source and QCL type for each NZP-CSI-RS-Resource listed in nzp-CSI-RS-Resources of the NZP-CSI-RS-ResourceSet indicated by nzp-CSI-RS-ResourcesforChannel. Each TCI-StateId refers to the TCI-State which has this value for tci-StateId and is defined in tci-StatesToAddModList in the PDSCH-Config included in the BWP-Downlink corresponding to the serving cell and to the DL BWP to which the resourcesForChannelMeasurement (in the CSI-ReportConfig indicated by reportConfigId above) belong to. First entry in qcl-info-forChannel corresponds to first entry in nzp-CSI-RS-Resources of that NZP-CSI-RS-ResourceSet, second entry in qcl-info-forChannel corresponds to second entry in nzp-CSI-RS-Resources, and so on (see TS 38.214 [19] , clause 5.2.1.5.1)

reportConfigId: The reportConfigId of one of the CSI-ReportConfigToAddMod configured in CSI-MeasConfig.

resourceSet: NZP-CSI-RS-ResourceSet for channel measurements. Entry number in nzp-CSI-RS-ResourceSetList in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to thesecond entry, and so on) .

It should be noted that the text “choice” in Figures 4 and 5 refers to a data type defined in Abstract Syntax Notation One (ASN. 1) that indicates a union of one or more alternatives. Taking Figure 4 as an example, the value of the IE reportConfigType with the choice type can be one of the following: periodic, semiPersistentOnPUCCH, semiPersistentOnPUSCH and aperiodic.

The following may be used to further disclose terms, examples, embodiments, implementations, actions, and/or behaviors:

BWP: A subset of the total cell bandwidth of a cell is referred to as a Bandwidth Part (BWP) and beamwidth part adaptation is achieved by configuring the UE with BWP (s) and telling the UE which of the configured BWPs is currently the active one. To enable Bandwidth Adaptation (BA) on the PCell, the gNB configures the UE with UL and DL BWP (s) . To enable BA on SCells in case of CA, the gNB configures the UE with DL BWP (s) at least (i.e. there may be none in the UL) . For the PCell, the initial BWP is the BWP used for initial access. For the SCell (s) , the initial BWP is the BWP configured for the UE to first operate at SCell activation. UE may be configured with a first active uplink BWP by a firstActiveUplinkBWP IE. If the first active uplink BWP is configured for an SpCell, the firstActiveUplinkBWP IE field contains the ID of the UL BWP to be activated upon performing the RRC (re-) configuration. If the field is absent, the RRC (re-) configuration does not impose a BWP switch. If the first active uplink BWP is configured for an SCell, the firstActiveUplinkBWP IE field contains the ID of the uplink bandwidth part to be used upon MAC-activation of an SCell.

PCell: When CA is configured, the UE only has one RRC connection with the network. At RRC connection establishment/re-establishment/handover, one serving cell provides the NAS mobility information, and at RRC connection re-establishment/handover, one serving cell provides the security input. This cell is referred to as the Primary Cell (PCell) .

PUCCH SCell: When CA is configured, UE may be configured with a cell other than PCell on which PUCCH resource is configured. This cell is referred to as the PUCCH SCell.

Figure 6 is a block diagram illustrating a node 600 for wireless communication according to an implementation of the present disclosure. As illustrated in Figure 6, a node 600 may include a transceiver 620, a processor 628, a memory 634, one or more presentation components 638, and at least one antenna 636. The node 600 may also include a radio frequency (RF) spectrum band module, a BS communications module, a network communications module, and a system communications management module, Input /Output (I/O) ports, I/O components, and a power supply (not illustrated in Figure 6) .

Each of the components may directly or indirectly communicate with each other over one or more buses 640. The node 600 may be a UE or a BS that performs various functions disclosed with reference to Figures 1 through 5.

The transceiver 620 has a transmitter 622 (e.g., transmitting/transmission circuitry) and a receiver 624 (e.g., receiving/reception circuitry) and may be configured to transmit and/or receive time and/or frequency resource partitioning information. The transceiver 620 may be configured to transmit in different types of subframes and slots including but not limited to usable, non-usable and flexibly usable subframes and slot formats. The transceiver 620 may be configured to receive data and control channels.

The node 600 may include a variety of computer-readable media. Computer-readable media may be any available media that may be accessed by the node 600 and include volatile (and/or non-volatile) media and removable (and/or non-removable) media.

The computer-readable media may include computer-storage media and communication media. Computer-storage media may include both volatile (and/or non-volatile media) , and removable (and/or non-removable) media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or data.

Computer-storage media may include RAM, ROM, EPROM, EEPROM, flash memory (or other memory technology) , CD-ROM, Digital Versatile Disks (DVD) (or other optical disk storage) , magnetic cassettes, magnetic tape, magnetic disk storage (or other magnetic storage devices) , etc. Computer-storage media may not include a propagated data signal. Communication media may typically embody computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanisms and include any information delivery media.

The term “modulated data signal” may mean a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. Communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the previously listed components should also be included within the scope of computer-readable media.

The memory 634 may include computer-storage media in the form of volatile and/or non-volatile memory. The memory 634 may be removable, non-removable, or a combination thereof. Example memory may include solid-state memory, hard drives, optical-disc drives, etc. As illustrated in Figure 6, the memory 634 may store a computer-readable and/or computer-executable program 632 (e.g., software codes or a set of instructions) that are configured to, when executed, cause the processor 628 to perform various functions disclosed herein, for example, with reference to Figures 1 through 5. Alternatively, the program 632 may not be directly executable by the processor 628 but may be configured to cause the node 600 (e.g., when compiled and executed) to perform various functions disclosed herein.

The processor 628 (e.g., having processing circuitry) may include an intelligent hardware device, e.g., a Central Processing Unit (CPU) , a microcontroller, an ASIC, etc. The processor 628 may include memory. The processor 628 may process the data 630 and the program 632 received from the memory 634, and information transmitted and received via the transceiver 620, the base band communications module, and/or the network communications module. The processor 628 may also process information to send to the transceiver 620 for transmission via the antenna 636 to the network communications module for transmission to a CN.

One or more presentation components 638 may present data indications to a person or another device. Examples of presentation components 638 may include a display device, a speaker, a printing component, a vibrating component, etc.

In view of the present disclosure, it is obvious that various techniques may be used for implementing the disclosed concepts without departing from the scope of those concepts. Moreover, while the concepts have been disclosed with specific reference to certain implementations, a person of ordinary skill in the art may recognize that changes may be made in form and detail without departing from the scope of those concepts. As such, the disclosed implementations are considered in all respects as illustrative and not restrictive. It should also be understood that the present disclosure is not limited to the specific implementations disclosed. Still, many rearrangements, modifications, and substitutions are possible without departing from the scope of the present disclosure.

Claims

A method performed by a user equipment (UE) for Aperiodic Channel State Information (A-CSI) transmission, the method comprising:

receiving, from a base station, Downlink Control Information (DCI) including a downlink assignment that schedules a Physical Downlink Shared Channel (PDSCH) and a first Physical Uplink Control Channel (PUCCH) corresponding to the PDSCH; and

reporting A-CSI to the base station through the first PUCCH.
The method according to claim 1, wherein the first PUCCH is scheduled for transmitting a Hybrid Automatic Repeat reQuest (HARQ) -Acknowledgement (ACK) feedback for the PDSCH.
The method according to claim 1, wherein:

the downlink assignment further schedules a second PUCCH for transmitting a Hybrid Automatic Repeat reQuest (HARQ) -Acknowledgement (ACK) feedback for the PDSCH, and

the first PUCCH is scheduled for transmitting the A-CSI and not for transmitting the HARQ ACK feedback for the PDSCH.
The method according to claim 1, wherein:

the DCI includes an indicator that indicates an A-CSI trigger state for reporting the A-CSI, and

the A-CSI trigger state is associated with a reporting configuration that indicates a resource allocation of the first PUCCH.
The method according to claim 1, wherein reporting the A-CSI is triggered by a CSI request included in the DCI.
A user equipment (UE) for Aperiodic Channel State Information (A-CSI) transmission, the UE comprising:

a memory; and

a processing circuity coupled to the memory and configured to:

receive, from a base station, Downlink Control Information (DCI) including a downlink assignment that schedules a Physical Downlink Shared Channel (PDSCH) and a first Physical Uplink Control Channel (PUCCH) corresponding to the PDSCH; and

report A-CSI to the base station through the first PUCCH.
The UE according to claim 6, wherein the first PUCCH is scheduled for transmitting a Hybrid Automatic Repeat reQuest (HARQ) -Acknowledgement (ACK) feedback for the PDSCH.
The UE according to claim 6, wherein:

the downlink assignment further schedules a second PUCCH for transmitting a Hybrid Automatic Repeat reQuest (HARQ) -Acknowledgement (ACK) feedback for the PDSCH, and

the first PUCCH is scheduled for transmitting the A-CSI and not for transmitting the HARQ ACK feedback for the PDSCH.
The UE according to claim 6, wherein:

the DCI includes an indicator that indicates an A-CSI trigger state for reporting the A-CSI, and

the A-CSI trigger state is associated with a reporting configuration that indicates a resource allocation of the first PUCCH.
The UE according to claim 6, wherein reporting the A-CSI is triggered by a CSI request included in the DCI.