Method, user equipment and base station for aperiodic channel state information feedback

Abstract

A method for aperiodic channel state information (A-CSI) feedback performed by a user equipment (UE) and a base station. The UE determines an A-CSI triggering event in an A-CSI triggering method, receives an A-CSI configuration from the base station, and determines an A-CSI reporting type in the A-CSI configuration. The UE performs A-CSI reporting, such as A-CSI reporting on a physical uplink control channel (PUCCH) or A-CSI reporting on a physical uplink shared channel (PUSCH), in response to the determined A-CSI triggering event according to the determined A-CSI reporting type. The triggering event includes at least one of a negative acknowledgement (NACK), an uplink scheduling downlink control information (UL DCI), a downlink scheduling downlink control information (DL DCI). The configuration of different A-CSI reporting types can be separately configured, activated and deactivated, sub-selected, and signaled between the UE and the base station.

Description

Technical Field

[0001] This invention relates to the field of communication systems, and more particularly to an aperiodic channel state information (A-CSI) feedback method, user equipment, and base station. Background Technology

[0002] Wireless communication systems and networks have evolved towards broadband and mobile systems. In cellular wireless communication systems, user equipment (UE) connects to a radio access network (RAN) via a radio link. The RAN includes a set of base stations (BS) that provide radio links to the UE located in cells covered by the base stations, and provide an interface to the core network (CN), which provides overall network control. It should be understood that the RAN and CN each perform their respective functions related to the entire network. The 3rd Generation Partnership Project (3GPP) has developed the so-called Long Term Evolution (LTE) system, namely the Evolved Universal Mobile Telecommunication System Territorial Radio Access Network (E-UTRAN), for mobile access networks, where a base station, also called an eNodeB or eNB (evolved NodeB), supports more macro cells. Recently, LTE is further evolving towards the so-called 5G or New Radio (NR) system, where one or more cells are supported by base stations called gNBs.

[0003] Ultra-reliable low-latency communication (URLLC) is one of several different use cases supported by the aforementioned 5G NR standard, specified in 3GPP Release 15. URLLC is a communication service that successfully delivers data packets with stringent requirements, particularly in terms of availability, latency, and reliability. URLLC was developed to support these emerging applications and services, such as wireless control and automation in industrial plant environments, vehicle-to-vehicle communication for improved safety and efficiency, and the aforementioned tactile internet. Therefore, URLLC is important for 5G because it supports vertical industries in bringing new services to the entire telecommunications industry.

[0004] One of the key characteristics mentioned above is low latency, a crucial factor enabling autonomous vehicles and remote surgery. Low latency allows for network optimization to process incredibly large amounts of data with minimal delay or latency. The quality of service (QoS) required by URLLC is entirely different from that of mobile broadband services.

[0005] URLLC guarantees latency of 1 millisecond or less. Time-sensitive networking (TSN) is another component of the aforementioned 5G URLLC. All devices on a URLLC connection must be synchronized on a time-to-time basis. Enablement technologies for URLLC include: integrated frame structures, incredibly fast turnaround times, efficient control and data resource sharing, unlicensed uplink transmission, and advanced channel coding schemes.

[0006] Technical issues

[0007] Enhanced Channel State Information (CSI) feedback can improve the reliability and real-time performance of URLLC services. Whether to transmit aperiodic CSI (A-CSI) on the Physical Uplink Control Channel (PUCCH) remains an open question. According to the previously released New Radio (NR) standard, A-CSI reported on the Physical Uplink Shared Channel (PUSCH) can only be triggered by the Uplink (UL) DCI. The UL DCI, for example, in DCI format 0_0, is the format of the UL scheduling DCI used for scheduling PUSCH within a cell, according to Section 7.3.1.1 of the technical specification (TS) 38.212. However, the existing A-CSI triggering method described above cannot be applied to certain scenarios. For example, when there is no UL data for scheduling being transmitted in busy DL traffic, transmitting a UL DCI solely for triggering A-CSI reporting is not a resource-efficient practice. When no UL data is being processed, UL authorization, such as UL DCI, should be avoided for URLLC services. Therefore, a new A-CSI triggering method is needed. Summary of the Invention

[0008] The purpose of this disclosure is to provide a method, user equipment, and base station for aperiodic channel state information (A-CSI) feedback.

[0009] A first aspect of this disclosure provides a method for aperiodic channel state information (A-CSI) feedback that can be executed in user equipment (UE), comprising:

[0010] Identify the A-CSI triggering event in the A-CSI triggering method;

[0011] Determine the A-CSI reporting type in the A-CSI configuration; and

[0012] A-CSI reporting is performed in response to the determined A-CSI triggering event according to the determined A-CSI reporting type.

[0013] A second aspect of this disclosure provides a method for aperiodic channel state information (A-CSI) feedback that can be performed in a base station, comprising:

[0014] Determine the A-CSI configuration, including the A-CSI reporting type;

[0015] Transmit the A-CSI configuration in the downlink channel to trigger A-CSI reporting; and

[0016] Receive A-CSI on the A-CSI reporting channel according to the determined A-CSI reporting type.

[0017] A third aspect of this disclosure provides a user equipment including a transceiver and a processor connected to the transceiver. The processor is configured to perform the following steps:

[0018] Identify the A-CSI triggering event in the A-CSI triggering method;

[0019] Determine the A-CSI reporting type in the A-CSI configuration; and

[0020] A-CSI reporting is performed in response to the determined A-CSI triggering event according to the determined A-CSI reporting type.

[0021] A fourth aspect of this disclosure provides a base station including a transceiver and a processor connected to the transceiver. The processor is configured to perform the following steps:

[0022] Determine the A-CSI configuration, including the A-CSI reporting type;

[0023] Transmit the A-CSI configuration in the downlink channel to trigger A-CSI reporting; and

[0024] Receive A-CSI on the A-CSI reporting channel according to the determined A-CSI reporting type.

[0025] The disclosed method can be implemented in a chip. The chip may include a processor for calling and running a computer program stored in memory, so that a device on which the chip is installed performs the disclosed method.

[0026] The disclosed methods can be programmed as computer-executable instructions stored on a non-transitory computer-readable medium. When loaded onto a computer, the non-transitory computer-readable medium instructs the computer's processor to execute the disclosed methods.

[0027] Non-transitory computer-readable media may include at least one of the following groups: hard disk, CD-ROM, optical storage device, magnetic storage device, read-only memory, programmable read-only memory, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory. The disclosed methods can be programmed into a computer program product that causes a computer to perform the disclosed methods. The disclosed methods can also be programmed into a computer program that causes a computer to perform the disclosed methods.

[0028] Beneficial effects

[0029] This disclosure provides the aforementioned CSI feedback enhancements for URLLC and the Industrial Internet of Things (IIOT). This disclosure primarily focuses on the novel triggering method for A-CSI, as the conventional A-CSI triggering method is not suitable for all scenarios. It is currently unclear how A-CSI is transmitted on the PUCCH. This disclosure provides several detailed embodiments for configuring A-CSI on the PUCCH. These embodiments can significantly improve CSI feedback efficiency and meet higher Quality of Service (QoS) requirements, especially for URLLC services.

[0030] This invention primarily improves upon A-CSI in at least two aspects: first, a novel triggering method for A-CSI; and second, detailed configuration of A-CSI transmitted on the PUCCH. To address the technical problems in these two aspects, this invention provides several embodiments. For example, one embodiment provides a detailed solution for triggering A-CSI using downlink (DL) control information (DCI) and NACK, and explains how to combine these two schemes and use the corresponding scheduling rules. Furthermore, seven alternative embodiments are proposed to support A-CSI on the PUCCH, along with corresponding detailed configurations for distinguishing between A-CSI on the PUCCH and A-CSI on the PUSCH. The embodiments of this disclosure are proposed to improve CSI resource efficiency and reduce A-CSI feedback latency. Attached Figure Description

[0031] To more clearly illustrate the above embodiments or related technologies of the present invention, the following drawings will be used in the brief description of the above embodiments. Obviously, the drawings are merely some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without any preconditions.

[0032] Figure 1 This is a schematic diagram of a telecommunications system.

[0033] Figure 2 This is a schematic diagram showing a CRAN with a baseband unit pool, a remote radio head unit, and a UE.

[0034] Figure 3 This is a schematic diagram illustrating the execution of the disclosed method according to an embodiment of the present invention on the base station side.

[0035] Figure 4 This is a schematic diagram illustrating the disclosed method performed on the user equipment (UE) side according to an embodiment of the present disclosure.

[0036] Figure 5 This is a schematic diagram of a method with a coverage indication disclosed in the first alternative embodiment of the present invention.

[0037] Figure 6 This is a schematic diagram of the disclosed method with time preference settings according to a second optional embodiment of the present invention.

[0038] Figure 7 This is a schematic diagram of the disclosed method with priority indication according to a third optional embodiment of the present invention.

[0039] Figure 8This is a schematic diagram illustrating the disclosed method with a pre-configured A-CSI configuration according to a fourth alternative embodiment of the present disclosure.

[0040] Figure 9 This is a schematic diagram of the disclosed method with a historical A-CSI configuration according to a fifth optional embodiment of the present invention.

[0041] Figure 10 This is a schematic diagram of CSI measurement and calculation preprocessing for NACK-triggered A-CSI according to the sixth optional embodiment of the present invention.

[0042] Figure 11 This is a schematic diagram of the two-stage A-CSI reporting in the eighth embodiment of the present invention.

[0043] Figure 12 This is a schematic diagram of simultaneous A-CSI reporting provided in the ninth optional embodiment of the present invention.

[0044] Figure 13 This is a schematic diagram of the disclosed method according to the tenth optional embodiment of the present invention, wherein the A-CSI configuration is distinguished by upper-layer signaling.

[0045] Figure 14 The schematic diagram illustrates the disclosed method with priority A-CSI reporting according to the eleventh optional embodiment of this disclosure.

[0046] Figure 15 The schematic diagram illustrates the disclosed method of prioritizing A-CSI reporting according to a twelfth alternative embodiment of this disclosure.

[0047] Figure 16 This is a schematic diagram illustrating the disclosed method for selecting an A-CSI reporting type by a UE according to a thirteenth alternative embodiment of this disclosure.

[0048] Figure 17 This is a block diagram of a system for wireless communication according to an embodiment of the present disclosure. Detailed Implementation

[0049] The technical aspects, structural features, achieved objectives, and effects of the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Specifically, the terminology used in the embodiments of the present invention is merely used to describe the purpose of specific embodiments and is not intended to limit the present invention.

[0050] Reference Figure 1 A telecommunications system comprising a group 100a of multiple UEs, a base station (BS) 200a, and a network entity device 300 performs the disclosed method according to embodiments of the present disclosure. The group 100a of multiple UEs may include UE 10a, UE 10b, and other UEs. Figure 1This is exemplary and not limiting; the system may include more UE, BS, and CN entities. Connections between devices and device components are represented by lines and arrows in the figures. Connections between devices can be achieved wirelessly. Connections between device components can be achieved via wired lines, buses, traces, cables, or optical fibers. UE 10a may include processor 11a, memory 12a, and transceiver 13a. UE 10b may include processor 11b, memory 12b, and transceiver 13b. Base station 200a may include baseband unit (BBU) 204a. Baseband unit 204a may include processor 201a, memory 202a, and transceiver 203a. Network entity device 300 may include processor 301, memory 302, and transceiver 303. Each of processors 11a, 11b, 201a, and 301 may be configured to implement the proposed functions, procedures, and / or methods described herein. The radio interface protocol layer can be implemented in the processors 11a, 11b, 201a, and 301. Each of the memories 12a, 12b, 202a, and 302 operably stores various programs and information to operate the connected processor. Each of the transceivers 13a, 13b, 203a, and 303 is operably coupled to the connected processor to transmit and / or receive radio signals or wired signals. The UE 10a can communicate with the UE 10b via a sidelink. The base station 200a can be one of an eNB, gNB, or other types of radio nodes.

[0051] Each of the processors 11a, 11b, 201a, and 301 may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, and / or data processing devices. Each of the memories 12a, 12b, 202a, and 302 may include a read-only memory (ROM), a random access memory (RAM), a flash memory, a memory card, a storage medium, and / or other storage devices. Each of the transceivers 13a, 13b, 203a, and 303 may include baseband circuitry and radio frequency (RF) circuitry to process radio frequency signals. When the embodiments are implemented in software, the technology can be implemented using modules, units, programs, functions, entities, etc., to perform the functions. The modules may be stored in memory and executed by the processor. The memories may be implemented within a processor or external to the processor, wherein those may be communicatively coupled to the processor by various means, as is known in the art.

[0052] The network entity device 300 may be a node in a CN. The CN may include an LTE CN or a 5G core network (5GC), which includes user plane function (UPF), session management function (SMF), mobility management function (AMF), unified data management (UDM), policy control function (PCF), control plane / user plane separation (CUPS), authentication server (AUSF), network slice selection function (NSSF), and network exposure function (NEF).

[0053] See Figure 2Base station 200b is an embodiment of base station 200a, including a central controller (CC) 210 and access points 211-1, 211-2, ..., and 211-M. M is a positive integer. The central controller 210 may be implemented as a central unit (CU) and may include a BBU, such as BBU 204a, connected to the access points (APs) 211-1, 211-2, ..., and 211-M. Each of the access points 211-1, 211-2, ..., and 211-M may be implemented as a radio node, a remote unit (RU), or a remote radio head (RRH), and may include a transmission and reception point (TRP). The access points 211-1, 211-2, ..., and 211-M may be located in different locations.

[0054] The central controller 210 receives radio signals from a group of V user equipments (UEs) of 100b through a group of M distributed radio nodes. V is a positive integer. The V group of UEs includes UE 10-1, 10-2, 10-3, ... 10-V. The UEs 10-1, 10-2, 10-3, and ... 10-V can be located in different locations.

[0055] The technical issues considered above fall under the category of high-density connectivity and non-orthogonal multiple access (NOMA) in CRAN systems. In one example, the CRAN network operates in time-division duplex (TDD) mode, where channel estimation is performed via uplink pilot transmission.

[0056] Each coherent time slot is divided between two uplink training instances using orthogonal uplink pilots, uplink, and downlink data transmission. Embodiments of this disclosure handle uplinks from V UEs to M single-antenna access points (APs). In each time slot, each AP performs uplink channel estimation independently.

[0057] The APs 211-1, 211-2, ..., and 211-M are distributed within the coverage area and managed by the central controller 210. The central controller 210 contains a centralized baseband unit (BBU) pool and handles physical and network layer operations, including medium access control (MAC) layer operations such as data decoding and encoding, scheduling, and power allocation. The APs are linked to the central controller 210 via a high-performance transmission link called fronthaul. Fronthaul can be implemented via fiber optic cable or a high-bandwidth wireless channel. Figure 2 The system comprising the base station 200b and the UE is a simplified example of CRAN. The APs 211-1, 211-2, ..., 211-M perform channel estimation and link-level transmission chaining until equalization. The central controller 210 performs signal decoding, encoding, modulation, demodulation, scheduling, and MAC layer operations. Uplink (UL) transmission of control signals or data can be a transmission operation from the UE to the base station. Downlink (DL) transmission of control signals or data can be a transmission operation from the base station to the UE.

[0058] Cross-reference Figure 3 and Figure 4 A base station, such as base station 200a, and a UE, such as UE 10a or UE 10b, perform a method for aperiodic channel state information (A-CSI) feedback. The base station determines an A-CSI configuration, including an A-CSI reporting type, for A-CSI reporting (block 310) and transmits the A-CSI configuration in a downlink channel to trigger A-CSI reporting (block 311). The A-CSI configuration can be transmitted in the form of control signals including UL DCI, DL DCI, radio resource control (RRC) parameters, and medium access control (MAC) control elements (CE), or a combination of these control signals.

[0059] The UE receives the A-CSI configuration (block 320). The UE determines an A-CSI trigger event in the A-CSI triggering method (block 321) and determines an A-CSI reporting type in the A-CSI configuration (block 322). The A-CSI reporting type indicates an A-CSI reporting channel. The UE performs A-CSI reporting in response to the determined A-CSI trigger event according to the determined A-CSI reporting type (block 323). The A-CSI is transmitted by the UE on the A-CSI reporting channel indicated by the A-CSI reporting type. The base station receives the A-CSI on the A-CSI reporting channel according to the determined A-CSI reporting type (block 312).

[0060] A-CSI is triggered by DL scheduling DCI:

[0061] In one embodiment, A-CSI reporting can be triggered by a DL grant used to schedule PDSCH transmissions. The DL grant can be a DL DCI in a DCI format. The DL DCI is a DL scheduling DCI used to schedule PDSCH. If retransmission of the PDSCH is required, the triggered A-CSI can be used to determine the modulation and coding scheme (MCS) parameters for the retransmission. In the above description, CSI and CSI reporting are used interchangeably.

[0062] First, a new indication parameter is defined in the DL DCI format as an indication mechanism for triggering A-CSI reporting. Indication mechanisms from previous versions of the NR standard can be reused. For example, a new n-bit CSI request field can be included in the DDL DCI format. The DCI format can include, for example, any combination of DCI format 1_0, DCI format 1_1, DCI format 1_2, and other DCI formats used for scheduling PDSCH. The number of "n" can be determined by upper-layer parameters, such as the Radio Resource Control (RRC) parameter `reportTriggerSize`. The `reportTriggerSize` parameter can be reused and configured for UL DCI triggering A-CSI. Alternatively, a new parameter, such as `reportTriggerSize_DL`, can be introduced to specifically indicate this DL DCI.

[0063] In addition, for the coexistence of A-CSI triggered by DL DCI and A-CSI triggered by UL DCI, some scheduling rules need to be defined:

[0064] • The DL DCI that triggers A-CSI can be specifically designed for URLLC services:

[0065] Because URLLC services require higher transmission reliability and lower latency, data retransmission after decoding failure is undesirable. To ensure successful decoding of the retransmitted data, timely CSI reporting is necessary. However, for eMBB services, the latency requirement is not strict, and the network can utilize periodic CSI reporting information to schedule data retransmission. Thus, CSI reporting triggered by the DL DCI brings more benefits to the URLLC service. The base station can specifically enable DL DCI-triggered A-CSI for the URLLC service type. The network can also trigger A-CSI only through DL authorization when scheduling PDSCH.

[0066] The DL DCI triggering method described above can improve signaling efficiency. During periods without UL data transmission, transmission...

[0067] A UL DCI dedicated to triggering A-CSI is not valid control signaling. Similarly, transmitting a DL DCI to trigger A-CSI without scheduling a PDSCH is inefficient. Therefore, the network can trigger A-CSI only via DL grant when scheduling a PDSCH. The base station can trigger A-CSI via DL grant (e.g., in the form of a DL DCI) only when the DL DCI is configured to be scheduled to bind to the physical downlink shared channel (PDSCH). The UE receives the DL DCI that schedules the PDSCH and performs A-CSI reporting in response to the DL DCI. The transmission of the DL scheduling DCI is bundled with the transmission of the PDSCH.

[0068] When both DL DCI-triggered A-CSI and UL DCI-triggered A-CSI coexist, the following solution is provided to address the issue of their simultaneous occurrence:

[0069] Option 1: Because DL DCI-triggered A-CSI has higher priority and stricter low-latency requirements, DL DCI-triggered A-CSI can cover UL DCI-triggered A-CSI. (See reference...) Figure 5The base station can send a coverage indication to the UE, wherein the DL scheduling DCI covers the UL scheduling DCI used for A-CSI reporting (block 310a) and sends a DL DCI and a UL DCI for triggering A-CSI to the UE (block 311a). When the DL DCI and the UL DCI for triggering A-CSI are received (block 330), a UE, such as one of the UEs 10a or 10b, can perform A-CSI reporting according to the DL DCI, which covers the UL DCI that the UE may have received before or after the DL DCI (block 331). The base station receives the CSI feedback (block 312a).

[0070] Option 2: The UE may be affected by either an earlier or later trigger signal. That is, the timing preference setting instructs either the earlier or later received DCI to be the active A-CSI trigger DCI used to trigger A-CSI reporting. This timing preference setting can be determined by a network entity, such as the base station, and sent to the UE. Alternatively, the timing preference setting can be determined by the UE. (See reference...) Figure 6 The base station sends an A-CSI configuration (block 311b) including time preference settings to the UE. The UE obtains the time preference settings (block 311b).

[0071] 333) and in response to the activated A-CSI, the DCI is triggered to perform A-CSI reporting to the base station according to the time preference setting (block 334). The base station receives the CSI feedback (block 312b).

[0072] -Option 3: Refer to Figure 7The base station determines either DL DCI-triggered A-CSI reporting or UL DCI-triggered A-CSI reporting as the preferred A-CSI triggering method (block 340) and sends an indication of the determined preferred A-CSI triggering method to the UE via DCI or upper-layer parameters such as Radio Resource Control (RRC) signals (block 341). The UE receives the indication of the determined preferred A-CSI triggering method (block 342) and performs A-CSI reporting to the base station according to the preferred A-CSI triggering method (block 343). The UE receives the indication for indicating either DL-scheduling DCI-triggered A-CSI reporting or UL-scheduling DCI-triggered A-CSI reporting. The UE receives a UL DCI of one DCI format and a DL DCI of one DCI format, wherein the UL DCI format includes a CSI request field for triggering A-CSI reporting, and the DL DCI format includes a CSI request field for triggering A-CSI reporting. The UE shall respond to the UL scheduling DCI to report the A-CSI when the indication indicates that the UL scheduling DCI triggers the A-CSI report, or respond to the DL scheduling DCI to report the A-CSI when the indication indicates that the DL scheduling DCI triggers the A-CSI report.

[0073] • Independent configuration of aperiodicTriggeringOffset:

[0074] The upper-level parameter aperiodicTriggeringOffset is in the information element IE

[0075] Configured in NZP-CSI-RS-ResourceSet for triggering UL DCI via A-CSI. The parameters...

[0076] aperiodicTriggeringOffset indicates that it contains a set of non-periodic non-zero power triggers.

[0077] The offset X between the time slot of the DCI of the (non-zero-power, NZP)CSI-RS resource and the time slot of the transmission of that group of aperiodic non-zero-power (non-zero-power, NZP)CSI-RS resources.

[0078] The parameters used for DL ​​DCI triggering can be configured separately from the UL DCI triggering. A parameter is configured for UL-scheduled DCI to indicate that it includes triggering a set of non-periodic non-zero power.

[0079] The offset X between the time slot of the UL scheduling DCI for (non-zero-power, NZP) CSI-RS resources and the time slot of the transmission of that group of aperiodic non-zero-power (non-zero-power, NZP) CSI-RS resources. Similarly, the offset X can be found in the IE of the DL DCI used for A-CSI triggering.

[0080] The NZP-CSI-RS-ResourceSet includes another parameter, for example...

[0081] aperiodicTriggeringOffset_DL represents the offset X between the time slot of the DL DCI that triggers a set of non-zero-power (NZP) CSI-RS resources and the time slot of the transmission of that set of non-zero-power (NZP) CSI-RS resources.

[0082] An embodiment of the present invention may utilize any combination of the above rules. Examples of UEs described herein may include either UE 10a or UE 10b. Examples of base stations described above may include base station 200a. A-CSI reporting or A-CSI feedback is performed on the uplink from the UE to the base station. In this description, CSI reporting and CSI are used interchangeably. Additionally, HARQ-ACK represents HARQ feedback, which may include an ACK and a NACK. Downlink control information (DCI) in DCI format is transmitted from a BS such as BS 200a to a UE such as UE 10a or UE 10b. Radio resource control parameters include parameters carried in RRC control signals transmitted from a BS such as BS 200a to a UE such as UE 10a or UE 10b. The term "network" may include a base station, a CN network entity, or a combination of a base station and a CN network entity.

[0083] A-CSI is triggered by NACK:

[0084] One embodiment of the present invention provides A-CSI triggered by NACK as an alternative triggering method for A-CSI reporting. The NACK-triggered A-CSI reporting can include two cases: the first case is NACK-triggered A-CSI without DCI scheduling, and the second case is NACK-triggered with DCI scheduling.

[0085] For the first scenario described above, A-CSI triggered by NACK without DCI scheduling needs to address one issue: how to indicate the detailed configuration of the A-CSI report to the UE. According to Section 6.1.3.13 of Technical Specification (TS) 38.321, each codepoint in the DCI field “CSI Request” is associated with a trigger state configured in the RRC Information Element (IE) CSI-AperiodicTriggerStateList. The IE CSI-AperiodicTriggerStateList is configured to provide the UE with a list of aperiodic trigger states. For each trigger state, the associatedReportConfigInfoList in the RRC Information Element IE CSI-AperiodicTriggerStateList provides resource information for various types of CSI measurements. Upon receiving a value representing a code point associated with a trigger state, the UE can, for the received trigger state, perform CSI reference signal (CSI-RS) measurement, CSI interference measurement (CSI-IM) and / or synchronization signal block (SSB) and A-CSI reporting in L1, based on all entries in the associatedReportConfigInfoList. Since A-CSI triggered by a NACK without DCI scheduling cannot provide such resource information to the UE, the UE cannot perform the A-CSI reporting.

[0086] In one embodiment of the present invention, the base station indicates an A-CSI configuration for A-CSI reporting to the UE, for reporting A-CSI in the absence of DCI scheduling. In a first example of the embodiment, the UE is pre-configured with resource information and triggering information associated with A-CSI reporting. For example, a default A-CSI configuration can be pre-stored in the UE. When performing NACK-triggered CSI reporting, the UE can perform A-CSI reporting based on the pre-stored A-CSI configuration. In a second example of the above embodiment, the base station can indicate a default A-CSI configuration to the UE via upper-layer signaling, such as RRC parameters. For example, the default A-CSI configuration can be configured and displayed in CSI-MeasConfig. When the DCI does not provide an A-CSI triggering DCI or CSI request field to the UE, the default A-CSI configuration can be defined as DefaultCSIRequest in the UE. The UE can perform A-CSI reporting based on the configuration information provided by DefaultCSIRequest.

[0087] Reference Figure 8 The base station sends a downlink transmission, such as PDCCH or PDSCH, to the UE (block 350). The UE receives and decodes the downlink transmission (block 351). When decoding of the downlink transmission fails, the UE generates a negative acknowledgment (NACK) as HARQ feedback for the downlink transmission. The UE determines the NACK as the A-CSI trigger event in response to the downlink transmission and triggers A-CSI reporting to the base station in response to the NACK (block 352). When reporting A-CSI, the UE obtains a pre-configured A-CSI configuration to perform CSI measurement and calculation (block 353) and uses the result of the CSI measurement and calculation as CSI feedback for the A-CSI reporting (block 354). The base station receives the CSI feedback (block 355).

[0088] Additionally, if the historical DCI contains one or more CSI requests, the UE can obtain the default A-CSI configuration from the historical DCI. The UE can also reuse the resource information and triggering information from the historical DCI associated with A-CSI reporting as the default A-CSI configuration. That is, the UE can use the resource information to perform the A-CSI measurement and use the triggering information from the historical DCI to perform A-CSI reporting. However, in the absence of a historical DCI, the UE can use other schemes.

[0089] Reference Figure 9The base station sends a downlink transmission, such as PDCCH or PDSCH, to the UE (block 360). The UE receives and decodes the downlink transmission (block 361). When decoding of the downlink transmission fails, the UE generates a negative acknowledgment (NACK) as HARQ feedback for the downlink transmission. The UE determines the NACK as the A-CSI trigger event in response to the downlink transmission and triggers A-CSI reporting to the base station in response to the NACK (block 362). When reporting A-CSI, the UE obtains the A-CSI configuration from the historical A-CSI configuration, performs CSI measurement and calculation (block 363), and uses the result of the CSI measurement and calculation as the CSI feedback for the A-CSI reporting (block 364). The base station receives the CSI feedback (block 365).

[0090] A problem exists with NACK-triggered A-CSI with DCI scheduling: when to start the A-CSI measurement and calculation. If the UE performs A-CSI measurement and calculation after identifying whether the HARQ feedback to be sent to the base station is ACK or NACK, it may prolong A-CSI reporting and increase latency. Some embodiments of the present invention are provided below to address this problem.

[0091] Always calculate A-CSI reports for URLLC:

[0092] To meet the latency requirements of the aforementioned URLLC service, the UE can perform A-CSI measurement and calculation in response to each CSI request indicated by the DCI. (Refer to...) Figure 10 The base station sends multiple DCI signals with CSI requests to the UE (block 370). The UE receives the DCI signals with CSI requests and performs A-CSI measurements and calculations in response to each CSI request indicated by the DCI (block 371). When the downlink transmission decoding fails, the UE generates a negative acknowledgment (NACK) as HARQ feedback to the downlink transmission. The UE determines the NACK in response to the downlink transmission as the A-CSI trigger event and triggers A-CSI reporting to the base station in response to the NACK (block 372). When reporting A-CSI, the UE uses the results of the CSI measurements and calculations as CSI feedback for the A-CSI reporting (block 374). The base station receives the CSI feedback (block 375).

[0093] When the UE performs A-CSI reporting in response to NACK according to the A-CSI-triggered reporting method, the UE may send the A-CSI together with the HARQ feedback of the NACK. The base station may schedule data retransmission associated with the HARQ feedback based on the A-CSI. Alternatively, since the A-CSI reporting can indicate that the HARQ-ACK is NACK, the HARQ feedback may be omitted during the A-CSI reporting to improve signaling efficiency.

[0094] Simplified A-CSI reporting:

[0095] Unlike the above approach, A-CSI measurement and calculation can be performed after obtaining the HARQ-ACK results. To ensure timely reporting of A-CSI, the reported A-CSI can be simplified, for example, reporting only a portion of the A-CSI. The aforementioned portion of the A-CSI can be reported first, and then optionally, the remaining portion can be reported using available resources. (Refer to...) Figure 11 The UE responds to an A-CSI trigger event by performing A-CSI reporting (block 381). During A-CSI reporting, the UE reports a first portion of the A-CSI to the base station in the first phase (block 383) and a second portion of the A-CSI to the base station in the second phase (block 385), thus forming a two-phase A-CSI reporting. The base station receives the first portion of the A-CSI in the first phase (block 384) and the second portion of the A-CSI in the second phase (block 386). The first reported portion of the A-CSI may have a higher priority and be reported together with the HARQ-ACK. The determination of the CSI priority may follow the priority rules defined in Section 5.2.5 of TS 38.214. The DCI format in the above embodiments may be UL DCI or DL ​​DCI.

[0096] The A-CSI triggering method used by the UE can be applied to various A-CSI use cases to provide flexibility for different scenarios. The A-CSI triggering method can be configured via DCI or upper-layer parameters such as RRC parameters as an indication of the A-CSI triggering method. This parameter may be ACSITigerMethodInd. As shown in Table 1, for example, the base station sends ACSITigerMethodInd=0 to the UE to activate the A-CSI triggered by the DL DCI, ACSITigerMethodInd=1 to activate the A-CSI triggered by the NACK (where the A-CSI triggered by the NACK has DCI scheduling), ACSITigerMethodInd=2 to activate the A-CSI triggered by the NACK (where the A-CSI triggered by the NACK has no DCI scheduling), and ACSITigerMethodInd=3 to activate one of the other A-CSI triggering methods.

[0097] Table 1

[0098]

[0099] The UE receives the indication of the activated A-CSI triggering method and responds to the A-CSI triggering event by reporting A-CSI according to the activated A-CSI triggering method. It should be noted that the triggering methods detailed above are not limited to a single A-CSI reporting channel. The UE can report A-CSI via PUCCH, PUSCH, or other channels.

[0100] Detailed A-CSI solution on PUCCH:

[0101] A-CSI reporting is required on the PUCCH. A-CSI on the PUCCH can enhance the scheduling flexibility of the base station and reduce signaling overhead. Allocating the entire PUCCH transmission for a few bits of CSI is inefficient. One embodiment of the invention can provide simultaneous slotted CSI feedback. (See also...) Figure 12The base station sends a DCI to the UE to trigger simultaneous slot CSI feedback (block 390). The UE receives the DCI from the base station at the beginning of a slot (block 391) and performs simultaneous slot CSI feedback. During simultaneous slot CSI feedback, the UE triggers a short PUCCH carrying A-CSI to the base station before the end of the same slot in response to the DCI received at the beginning of the same slot (block 392). The base station receives the A-CSI in the short PUCCH (block 395). Simultaneous slot CSI feedback facilitates very fast CSI feedback, which improves the accuracy of the CSI, especially in the case of fast-moving UEs or rapid changes in interference.

[0102] A-CSI configuration on PUCCH:

[0103] The A-CSI on the PUCCH also raises many technical issues that need to be addressed, such as how to configure the aforementioned configuration parameters of the A-CSI on the PUCCH, whether to distinguish between the A-CSI configuration parameters on the PUCCH and the A-CSI configuration parameters on the PUSCH, and how to coordinate the relationship between the A-CSI on the PUCCH and the A-CSI on the PUSCH. Some embodiments are provided below to address these technical issues.

[0104] Separate configuration of A-CSI on PUCCH and A-CSI on PUSCH in DCI:

[0105] In one embodiment, the base station can configure A-CSI on the PUCCH and A-CSI on the PUSCH respectively, and indicate the A-CSI configuration to one or more UEs. That is, all the above-mentioned A-CSI reporting configurations can be configured separately for the PUCCH and PUSCH.

[0106] A-CSI reporting is triggered using a DCI by indicating in the CSI request field which CSI should be reported. The CSI request field is configured in the A-CSI triggering DCI. The CSI request field in the DCI can be configured separately for A-CSI on PUCCH and A-CSI on PUSCH. That is, the base station configures a CSI request field for A-CSI reporting on PUCCH and a CSI request field for A-CSI reporting on PUSCH in the A-CSI triggering DCI. The base station sends the A-CSI configuration to the UE in the form of the A-CSI triggering DCI, the A-CSI configuration including the CSI request field for A-CSI reporting on PUCCH and the CSI request field for A-CSI reporting on PUSCH. The UE receives the A-CSI configuration in the form of the A-CSI triggering DCI and performs A-CSI reporting according to the A-CSI configuration. For A-CSI on PUSCH, the original configuration from previous versions can be retained. For A-CSI on PUCCH, new parameters can be configured. For example, the new parameter for A-CSI on PUCCH can be referred to as a CSI request for PUCCH. The CSI request for A-CSI on PUSCH can be an n1-bit parameter, determined by the upper-layer parameter reportTriggerSize. Therefore, the CSI request for PUCCH can be an n2-bit parameter determined by the upper-layer parameter reportTriggerSize_PUCCH. The values ​​of n1 and n2 are configured by the upper-layer parameters reportTriggerSize and reportTriggerSize_PUCCH respectively, and they can be the same or different.

[0107] The parameter `aperiodicTriggerStateList` is an A-CSI trigger state list, including a list of trigger states for one or more A-CSI reporting configurations and resource sets used for channel and / or interference measurements. When the number of CSI trigger states in the aperiodicTriggerStateList is less than or equal to the number of code points in the CSI request, the CSI request field in the A-CSI trigger DCI directly indicates one of the multiple trigger states. The parameter `aperiodicTriggerStateList` can be configured separately to distinguish between A-CSI configurations on the PUCCH and A-CSI configurations on the PUSCH. For example, `aperiodicTriggerStateList_forPUCCH` can be introduced to indicate the A-CSI trigger state list on the PUCCH. Additionally, a new CSI reporting type 'aperiodicOnPUCCH' can be introduced for the upper-layer parameter CSI-ReportConfig to indicate A-CSI reporting on PUCCH, and the original 'aperiodic' in CSI-ReportConfig represents A-CSI on PUSCH. A CSI reporting type is a mode for CSI reporting on a type of channel, such as PUCCH or PUSCH. In this description, the CSI reporting type may be referred to as a CSI mode or CSI transmission mode.

[0108] The base station configures an A-CSI triggering state list in the A-CSI triggering DCI for reporting A-CSI on the PUCCH, and also configures an A-CSI triggering state list in the A-CSI triggering DCI for reporting A-CSI on the PUSCH. The base station sends A-CSI configuration to the UE in the form of the A-CSI triggering DCI. The A-CSI configuration includes the A-CSI triggering state list for reporting A-CSI on the PUCCH and the A-CSI triggering state list for reporting A-CSI on the PUSCH. The UE receives the A-CSI configuration in the form of the A-CSI triggering DCI and performs A-CSI reporting according to the A-CSI configuration.

[0109] Separate RRC configurations for A-CSI on PUCCH and A-CSI on PUSCH:

[0110] Unlike the above scheme, in this embodiment, the configuration of A-CSI on PUCCH and A-CSI on PUSCH is separated only at the upper layer, and A-CSI triggering DCI only requires configuring one CSI request, thereby saving DCI signaling overhead. The configuration of the RRC parameters for A-CSI reporting is the same as described in the previous embodiment, while the RRC parameters reportTriggerSize, aperiodicTriggerStateList, CSI-ReportConfig, or other parameters related to A-CSI reporting can be configured separately for A-CSI reporting on PUCCH and A-CSI reporting on PUSCH. The base station can use a 1-bit indication to notify the UE on which channel to perform the A-CSI reporting. This 1-bit parameter can be configured by DCI or upper-layer parameters (e.g., RRC parameters).

[0111] Reference Figure 13 The base station sends to the UE a common A-CSI configuration in a DCI for different A-CSI reporting types and a separate A-CSI configuration in an RRC signal for different A-CSI reporting types (block 400). The DCI can be a UL-scheduled DCI or a DL-scheduled DCI. The common A-CSI configuration in the DCI is shared by the A-CSI reporting types for PUCCH and PUSCH. The separate A-CSI configuration in the RRC signal includes one or more RRC parameters for the A-CSI reporting type used for A-CSI reporting on the PUCCH and one or more RRC parameters for the A-CSI reporting type used for A-CSI reporting on the PUSCH. The UE receives the common A-CSI configuration in the DCI and the separate A-CSI configuration in the RRC signal (block 401). The UE performs A-CSI reporting to send CSI feedback according to the public A-CSI configuration and the individual A-CSI configuration (block 403). The base station receives the CSI feedback (block 406).

[0112] Unified configuration of A-CSI on PUCCH and A-CSI on PUSCH:

[0113] An embodiment with minimal impact on existing protocols maintains the existing configuration mechanism unchanged, without independently configuring A-CSI reporting via PUCCH and A-CSI reporting via PUSCH. That is, the two A-CSI transmission modes, A-CSI reporting via PUCCH and A-CSI reporting via PUSCH, do not coexist; only one A-CSI transmission mode is enabled for each A-CSI report. The mode in which A-CSI is reported on a single channel is called the CSI mode or CSI transmission mode. Without a mechanism to notify the UE which channel the current A-CSI report is transmitted on, the UE cannot identify the currently enabled A-CSI transmission mode. To address the above problem, an embodiment is provided below.

[0114] a) Instructions determined by DCI or higher levels:

[0115] In one embodiment, the A-CSI configuration includes an A-CSI reporting type indication, indicating either the A-CSI reporting type on the PUCCH or the A-CSI reporting type on the PUSCH, as a determined A-CSI reporting type. The UE performs A-CSI reporting using this determined A-CSI reporting type according to the A-CSI configuration. The base station notifies the UE of the A-CSI transmission mode via upper-layer parameters such as the A-CSI reporting type indication parameter AperiodicCSIMode or RRC parameters in the DCI. The A-CSI transmission mode indicates that A-CSI reporting is performed on an uplink channel. The new 1-bit indication parameter AperiodicCSIMode is sufficient to indicate either the PUCCH or PDSCH. As shown in Table 2, for example, AperiodicCSIMode = 0 indicates A-CSI reporting via PUCCH, and AperiodicCSIMode = 1 indicates A-CSI reporting via PUSCH.

[0116] Table 2

[0117]

[0118] b) Differentiated by different DCI formats:

[0119] Regarding the DCI signaling overhead, the A-CSI mode is distinguished by the DCI format. For example, the base station can use a first UL DCI format to trigger A-CSI reporting on the PUSCH, and a second DL DCI format to trigger A-CSI reporting on the PUSCH. Alternatively, the DCI formats can be categorized to trigger CSI transmission modes individually. That is, each DCI format represents an A-CSI transmission mode. Each of the A-CSI reporting on the PUCCH and the A-CSI reporting on the PUSCH is triggered by a unique DCI format. In the example where the base station uses DL DCI to trigger A-CSI, according to the mapping relationship between DCI format and CSI mode, the base station can use DCI format1_0 to trigger A-CSI reporting on the PUCCH as the determined A-CSI reporting type, and DCI format1_1 to trigger A-CSI reporting on the PUSCH as the determined A-CSI reporting type. Optionally, this mapping relationship can be configurable and determined by the network entity.

[0120] c) New RNTI

[0121] The A-CSI mode can be indicated by a new radio network temporary identifier (RNTI). This new RNTI can include A-CSI-PUCCH-RNTI. For A-CSI reporting on the PUCCH, the base station can scramble the CSI request field in the DCI using A-CSI-PUCCH-RNTI to activate one of the multiple trigger states for A-CSI reporting on the PUCCH. Alternatively, the base station can use the CSI request field in the DCI that is not scrambled by A-CSI-PUCCH-RNTI to activate one of the multiple trigger states for A-CSI reporting on the PUSCH. Similarly, this new RNTI can include A-CSI-PUSCH-RNTI to scramble the CSI request field in the DCI. The base station can use A-CSI-PUSCH-RNTI to scramble the CSI request field in the DCI to activate one of the multiple trigger states for A-CSI reporting on the PUSCH. On the other hand, the base station can use the CSI request in the DCI that is not scrambled by A-CSI-PUSCH-RNTI.

[0122] This field activates one of the multiple trigger states used for A-CSI reporting on the PUCCH. MAC CE activates / deactivates A-CSI:

[0123] In one embodiment, the base station and the UE can distinguish between the configurations of A-CSI on the PUCCH and A-CSI on the PUSCH through a new medium access control (MAC) control element (CE). The advantage of this embodiment is that the configuration of A-CSI on the PUSCH can be the same as the current standard, and the impact on the current protocol can be minimized. The new MAC CE can trigger the activation and deactivation of A-CSI on the PUCCH. The base station can use the new CSI reporting type "aperiodicOnPUCCH" in the upper-layer parameter CSI-ReportConfig to indicate the reporting type of A-CSI on the PUCCH.

[0124] Activation and deactivation of A-CSI reporting on the PUCCH can be identified by the MAC sub-header in the MAC CE containing a logical channel identifier (LCID). For example, the MAC CE is X bits long and includes multiple fields such as serving cell ID, bandwidth part (BWP) ID, status indication, and reserved bits. The serving cell ID field indicates the identifier of the serving cell to which the MAC CE applies. The BWP ID field indicates that the UL BWP applied by the MAC CE is the code point of the DCI BWP ID field. The status indication field indicates the activation and deactivation status of the A-CSI configuration in the list csi-ReportConfigToAddModList configured in CSI-MeasConfig. The list csi-ReportConfigToAddModList is a list of multiple A-CSI configurations.

[0125] The MAC CE includes multiple status indicators. The status indicator field may include m bits and is represented as a variable S. i Let i represent the code point in the field, where the value of i may be between 0 and 2. m The range is -1. A code point in the status indication field indicates the activation or deactivation of an entry in the A-CSI configuration list. Code point S in the status indication field... iThis refers to the A-CSI configuration, which includes PUCCH resources for A-CSI reporting in the bandwidth part (BWP) and has a j-th CSI reporting configuration identifier in the list, where the reporting type is set to the A-CSI reporting type on the PUCCH. The variable j is derived from i. For example, j = i + 1. For example, the first code point S0 refers to an A-CSI configuration that includes PUCCH resources for A-CSI reporting in the indicated BWP and has the lowest CSI-ReportConfigId in the csi-ReportConfigToAddModList of the above list, where csi-ReportConfigToAddModList has a reporting type set to aperiodicOnPUCCH. The second code point S1 refers to an A-CSI configuration that includes PUCCH resources for A-CSI reporting in the indicated BWP and has the second lowest CSI-ReportConfigId in the csi-ReportConfigToAddModList of the above list, where csi-ReportConfigToAddModList has a reporting type set to aperiodicOnPUCCH, and so on. If the number of CSI configurations in the list with the CSI reporting type set to aperiodicOnPUCCH in the indicated BWP is less than 2... m Then the MAC entity in the UE can ignore the S field. i Apply all the aforementioned CSI configurations. The S i Setting the field to 1 indicates that the S should be activated. i The field refers to the corresponding A-CSI configuration i. The S ii Setting the field to 0 indicates that the S should be deactivated. i The field refers to the corresponding A-CSI configuration i.

[0126] Similarly, the above configuration can also be applied to A-CSI reporting on the PUSCH. For example, the MAC CE can activate and deactivate A-CSI reporting on the PUSCH, and A-CSI reporting on the PUSCH can use the traditional configuration mechanism described above. Activation and deactivation of A-CSI reporting on the PUSCH can be identified by a MAC sub-header with a Logical Channel Identifier (LCID) in the MAC CE. For example, the MAC CE is X bits and includes multiple fields, such as Serving Cell ID, Bandwidth Part (BWP) ID, Status Indicator, Reserved Bits, etc. The Serving Cell ID field indicates the identifier of the serving cell to which the MAC CE applies. The BWP ID field indicates that the UL BWP applied by the MAC CE is the code point of the DCI BWPID field.

[0127] The status indicator field indicates the activation and deactivation status of the A-CSI configuration in the csi-ReportConfigToAddModList configured in CSI-MeasConfig. The MAC CE includes multiple status indicators. The status indicator field may include m bits and is represented as a variable S. i The code point in the field is represented by the value of i, which can be between 0 and 2. m The range is -1. S0 refers to an A-CSI configuration that includes PUSCH resources for A-CSI reporting in the indicated BWP and has the lowest CSI-ReportConfigId in the list csi-ReportConfigToAddModList with the type set to aperiodicOnPUSCH. S1 refers to an A-CSI configuration that includes PUSCH resources for A-CSI reporting in the indicated BWP and has the second lowest CSI-ReportConfigId in the list csi-ReportConfigToAddModList with the type set to aperiodicOnPUSCH, and so on. If the number of CSI configurations in the list with the CSI reporting type set to aperiodicOnPUSCH in the indicated BWP is less than 2... m Then the MAC entity in the UE can ignore the S field. i Apply all the aforementioned CSI configurations. The S i The field can be set to 1 to indicate the S i The corresponding A-CSI configuration i pointed to by the field is activated. The S i Setting the field to 0 indicates that the Si The corresponding A-CSI configuration i referred to by the field is deactivated.

[0128] MAC CE used to trigger state sub-selection:

[0129] The difference between the A-CSI reporting configuration on PUCCH and the A-CSI reporting configuration on PUSCH lies in which channel is used to transmit A-CSI. The resource information, including the parameters and configurations used for A-CSI measurement and calculation, can be the same and reused by the UE for A-CSI measurement and calculation, regardless of whether the UE reports and sends A-CSI on PUCCH or PUSCH. In other words, the configuration for the CSI request in the DCI for A-CSI on PUSCH can be configured only once, while the configuration for the CSI request in the DCI for A-CSI reporting on PUCCH (including the trigger state) can be a subset of the A-CSI reporting configuration on PUSCH. Therefore, a sub-selection MAC CE for A-CSI configuration is proposed, called the Sub-Selection MAC CE.

[0130] Similar to the aforementioned embodiments, the new CSI reporting type "aperiodicOnPUCCH" in the upper-layer parameter CSI-ReportConfig can indicate the reporting type of the A-CSI report on the PUCCH. The sub-selection MAC CE can be identified by a MAC sub-header with LCID. The MAC CE may include Y bits, including several parts such as serving cell ID, BWP ID, trigger state subselection, DCI format indication, and reserved bits. The serving cell ID field indicates the identity (ID) of the serving cell to which the MAC CE applies. The BWP ID field indicates that the UL BWP applied by the MAC CE is the code point of the DCI BWP ID field. The trigger state subselection field indicates the selected state of the aperiodic trigger state configured in the aperiodic trigger state list aperiodicTriggerStateList. The aperiodicTriggerStateList can be an A-CSI configuration reported on the PUSCH or a pre-stored A-CSI configuration reported on the PUCCH. The selected trigger state indicates whether the referred trigger state is selected from the multiple trigger states in the aperiodicTriggerStateList. The multiple codepoints in the trigger state subselection field sequentially refer to multiple trigger states in the aperiodicTriggerStateList. Each codepoint in the trigger state subselection field references a trigger state in the aperiodicTriggerStateList and indicates whether the referred trigger state is selected from the multiple trigger states in the aperiodicTriggerStateList.

[0131] The trigger state sub-selection field in the sub-selection MAC CE may include k bits and is represented as a variable T. i , where variable T i This represents the code point in the trigger state sub-selection field, where the value of i can be between 0 and 2. k The range is -1. The code point T in the field selected by the trigger state sub-selection. iThis indicates whether the j-th trigger state in the trigger state list is selected or not selected in the sub-selection for A-CSI reporting, where j = i + 1. For example, T0 refers to the first aperiodic trigger state configured in aperiodicTriggerStateList, T1 refers to the second aperiodic trigger state configured in aperiodicTriggerStateList, and so on. The T... i The field can be set to 1 to indicate the T i The j-th trigger state associated with the field is selected in the sub-selection used for A-CSI reporting. The T mentioned... i The field can be set to 0 to indicate that it was created by the T i The j-th associated trigger state indicated by the field is not selected in the sub-selection. The variable j can be derived from i. For example, j = i + 1. The list of aperiodic trigger states can be an A-CSI configuration configured in a DCI format for A-CSI reporting. Additionally, the sub-selection MAC CE can be applied to sub-selections of the A-CSI configuration, where the A-CSI configuration is derived from an A-CSI configuration used for any CSI reporting type.

[0132] The DCI format indication field indicates which A-CSI trigger state list the MAC CE references, because different DCI formats may correspond to different aperiodicTriggerStateLists.

[0133] A-CSI transmission alone:

[0134] A-CSI on the PUCCH can reduce signaling overhead and improve feedback efficiency, especially for URLLC services. However, the base station does not necessarily need all CSI reports to determine the modulation and coding scheme (MCS), especially for URLLC services with very high requirements for low latency and high reliability. Therefore, in one embodiment, the UE can report A-CSI individually for the base station to determine the MCS. See also Figure 14The UE, in response to an A-CSI trigger event, reports an A-CSI, generates an A-CSI, and identifies a portion of the A-CSI as a first portion of high importance for MCS determination, and a portion of the A-CSI as a second portion of low importance for MCS determination (block 411). The UE may report the first portion of the A-CSI of high importance for MCS determination on the PUCCH (block 413), and optionally, report the second portion of the A-CSI of low importance for MCS determination on available PUSCH resources (block 415). The base station receives the first portion of the A-CSI on the PUCCH (block 414) and determines the MCS based on the first portion of the A-CSI (block 416). The base station receives the second portion of the A-CSI on the PUSCH (block 418).

[0135] See Figure 15 The UE, in response to an A-CSI trigger event, reports an A-CSI, generates an A-CSI, and identifies a portion of the A-CSI as a first portion with high priority and a portion of the A-CSI as a second portion with low priority (block 421). The UE may report the first portion of the A-CSI with high priority on the PUCCH (block 423), and optionally, report the second portion of the A-CSI with low priority on available resources of the PUSCH (block 425). The base station receives the first portion of the A-CSI on the PUCCH (block 424) and determines the MCS based on the first portion of the A-CSI (block 426). The base station receives the second portion of the A-CSI on the PUSCH (block 428).

[0136] The second portion of the A-CSI with lower priority can be retained by the UE without being reported. The determination of CSI priority can follow the priority rules defined in Section 5.2.5 of TS 38.214. A threshold can be defined to distinguish between high and low priorities; CSIs with a priority higher than this threshold can be transmitted on the PUCCH, while CSIs with a priority no higher than this threshold can be transmitted on the available PUSCH or ignored. In the described embodiment, separate configurations can be applied for A-CSI on the PUCCH and A-CSI on the PUSCH.

[0137] UE selection mode:

[0138] In one embodiment, the UE selects on which channel it sends A-CSI to the base station. For example... Figure 16As shown, the UE selects an A-CSI reporting type as the determined A-CSI reporting type to transmit A-CSI on the A-CSI reporting channel of that A-CSI reporting type (e.g., one of PUCCH or PUSCH) (block 431). The resource information and configuration of the A-CSI can be pre-configured by the base station. In this embodiment, the separate configurations for A-CSI on PUCCH and A-CSI on PUSCH as described above can be applied.

[0139] The UE can send an indication to the base station of the A-CSI reporting type selected by the UE on the A-CSI reporting channel (block 433). The base station receives the indication of the A-CSI reporting type selected by the UE (block 434) and detects A-CSI on the A-CSI reporting channel (e.g., one of PUCCH or PUSCH) (block 436). The UE can send the indication on the PUCCH. If the UE does not send the indication, the base station can detect the A-CSI on both the PUCCH and PUSCH.

[0140] Alternatively, the following modifications and rules can be applied to the above embodiments:

[0141] • Separate configurations for different DCI formats:

[0142] While the above description primarily addresses how to differentiate between A-CSI configurations on PUCCH and PUSCH, the A-CSI configurations may differ for different DCI formats. For each A-CSI transmission mode, the CSI resources and A-CSI configurations can be configured separately for different DCI formats. That is, the A-CSI configuration includes different sets of A-CSI configurations configured for different DCI formats.

[0143] • A-CSI on PUCCH only supports URLLC services:

[0144] A-CSI on the PUCCH can increase scheduling flexibility and reduce the latency of CSI feedback. These advantages are more favorable for URLLC services. In one embodiment, the base station and the UE only support A-CSI on the PUCCH for URLLC. Accordingly, the CSI mode of the A-CSI reported on the PUCCH can be an identifier that distinguishes URLLC services from enhanced mobile broadband (eMBB) URLLC service types.

[0145] Figure 17This is a block diagram of a system 700 for wireless communication, as an example, according to one embodiment of the present invention. The embodiments described herein can be implemented into the system using any suitably configured hardware and / or software. Figure 17 The system 700 is shown, including a radio frequency (RF) circuit 710, a baseband circuit 720, a processing unit 730, a memory / storage unit 740, a display 750, a camera 760, a sensor 770, and an input / output (I / O) interface 780, which are interconnected as shown.

[0146] The processing unit 730 described above may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose and special-purpose processors, such as a graphics processor and an application processor. The processor may be coupled to memory / storage and configured to execute instructions stored in memory / storage to enable various applications and / or operating systems to run on the system.

[0147] The baseband circuit 720 described above may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processor may include a baseband processor. The baseband circuitry can handle various radio control functions, enabling it to communicate with one or more radio networks via radio frequency circuitry. These radio control functions may include, but are not limited to, signal modulation, encoding, decoding, frequency modulation transfer, etc. In some embodiments, the baseband circuitry can provide communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry can support communication with 5G NR, LTE, Evolved Universal Terrestrial Radio Access Network (EUTRAN) and / or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), and Wireless Personal Area Networks (WPAN). Implementations of the baseband circuitry configured to support radio communication using more than one radio protocol may be referred to as multi-mode baseband circuitry. In various embodiments, the baseband circuitry 720 may include circuitry to operate signals that are not strictly considered to be at a baseband frequency. For example, in some implementations, the baseband circuit may include circuitry that operates on a signal having an intermediate frequency between the baseband frequency and the frequency modulation frequency.

[0148] The aforementioned radio frequency (RF) circuit 710 enables communication with wireless networks using modulated electromagnetic radiation transmitted through a non-solid-state medium. In various embodiments, the RF circuit may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. In various embodiments, the RF circuit 710 may include circuitry for operating signals that are not strictly considered to be frequency-modulated. For example, in some embodiments, the RF circuitry may include circuitry for operating signals with an intermediate frequency between the fundamental frequency and frequency modulation.

[0149] In various implementations, the transmitter, control, or receiver circuitry discussed above for the UE, eNB, or gNB may be wholly or partially embodied in one or more of the radio frequency circuitry, baseband circuitry, and / or processing unit. As used herein, "circuit" may refer to, be part of, or include an application-specific integrated circuit (ASIC), electronic circuitry, a processor (shared, dedicated, or combined), and / or memory (shared, dedicated, or combined) executing one or more software or firmware programs, combinational logic circuitry, and / or other suitable hardware components providing said functionality. In some implementations, the electronic device circuitry may be implemented in one or more software or firmware modules, or the circuitry-related functionality may be implemented by one or more software or firmware modules. In some implementations, some or all of the components of the baseband circuitry, processing unit, and / or memory / storage may be implemented together on a system on a single chip (SOC).

[0150] The memory / storage unit 740 described above can be used to load and store data and / or instructions, for example, for the system described above. The memory / storage unit used in one embodiment may include any combination of suitable volatile memory, such as Dynamic Random Access Memory (DRAM), and / or non-volatile memory, such as flash memory. In various embodiments, the I / O interface 780 described above may include one or more user interfaces designed to allow users to interact with the system and / or peripheral component interfaces designed to allow peripheral components to interact with the system. User interfaces may include, but are not limited to, physical keyboards or keypads, touchpads, speakers, microphones, etc. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, Universal Serial Bus (USB) ports, audio jacks, and power interfaces.

[0151] In various embodiments, the sensor 770 may include one or more sensing devices to determine environmental conditions and / or location information related to the system. In some embodiments, the sensor may include, but is not limited to, a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, baseband and / or radio frequency circuitry to communicate with components of a positioning network, such as Global Positioning System (GPS) satellites. In various embodiments, the display 750 may include a display, such as a liquid crystal display (LCD) or a touchscreen display. In various embodiments, the system 700 may be a mobile computing device, such as, but not limited to, a laptop computer, a tablet computer, a netbook, an ultrabook, a smartphone, etc. In various embodiments, the system may have more or fewer components and / or different architectures. Where appropriate, the methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-temporary storage medium.

[0152] The embodiments of the present invention are combinations of technologies / processes that can be employed in 3GPP specifications to create a final product. Any combination of the above embodiments is possible.

[0153] Those skilled in the art will understand that each unit, algorithm, and step described and disclosed in the embodiments of the present invention is implemented using electronic hardware or a combination of computer and electronic hardware in software. Whether these functions are executed in hardware or software depends on the application conditions and the design requirements of the technical solution. Those skilled in the art can implement the functions of each specific application in different ways, and such implementation should not exceed the scope of the present invention. Those skilled in the art will understand that since the working procedures of the above-described systems, devices, and units are substantially the same, the working procedures of the systems, devices, and units in the above embodiments can be referred to. For ease of description and simplification, these working procedures will not be described in detail.

[0154] It is understood that the systems, apparatuses, and methods disclosed in the embodiments of the present invention can be implemented in other ways. The above embodiments are merely illustrative examples. The division of the units mentioned above is based solely on logical function, and other division methods may exist in implementation. It is possible that multiple units or components are combined or integrated into another system. It is also possible that some features are omitted or omitted. On the other hand, the mutual coupling, direct coupling, or communication coupling described or discussed above is achieved through some ports, devices, or units, whether indirectly or through electronic, mechanical, or other forms of communication.

[0155] The units mentioned above, used as separate components for explanation, may be physically separate or not. These units may be physical units or not, meaning they may be located in one place or distributed across multiple network units. Some or all of the aforementioned units may be used depending on the purpose of the implementation. Furthermore, each functional unit in each implementation may be integrated into a processing unit, or physically independent, or integrated into a processing unit having two or more units.

[0156] If software functional units are implemented as products for use and sale, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions proposed in this invention can be implemented substantially, in key parts or in part, as software products. Alternatively, a portion of a technical plan beneficial to conventional technology can be implemented as a software product. Software products in a computer are stored in storage media and include multiple commands for a computing device (such as a personal computer, server, or network device) to execute all or part of the steps disclosed in the embodiments of this invention. Storage media include USB drives, portable hard drives, read-only memory (ROM), random access memory (RAM), floppy disks, or other types of media capable of storing program code.

[0157] This invention mainly improves upon at least two aspects: first, a new triggering method for A-CSI; and second, detailed configuration of A-CSI transmitted on the PUCCH. Several embodiments are provided to address the aforementioned technical problems.

[0158] While the present invention has been described in conjunction with what are considered to be the most practical and preferred embodiments, it should be understood that the present invention is not limited to the disclosed embodiments, but is intended to cover various arrangements made without departing from the broadest interpretation of the appended claims.

Claims

1. A method for aperiodic channel state information (A-CSI) feedback, executable in user equipment (UE), characterized in that, include: Identify the A-CSI triggering event in the A-CSI triggering method; Determine the A-CSI reporting type in the A-CSI configuration; and A-CSI reporting is performed in response to the determined A-CSI triggering event according to the determined A-CSI reporting type; The A-CSI configuration includes different A-CSI configuration sets configured separately for different DCI formats. For each A-CSI transmission mode, CSI resources and A-CSI configurations are configured separately for different DCI formats. The A-CSI transmission modes include A-CSI reporting on PUCCH and A-CSI reporting on PUSCH. The method further includes: Obtain a time preference setting that indicates either an earlier or later received DCI as the active A-CSI trigger for the DCI; and In response to the activated A-CSI, the DCI is triggered to perform the A-CSI reporting based on the time preference settings.

2. The A-CSI feedback method according to claim 1, characterized in that, Also includes: Receive downlink (DL) scheduling DCI in a downlink control information (DCI) format; and When the DCI format of the DL scheduling DCI includes a CSI request field for A-CSI reporting, the DL scheduling DCI is determined to be the A-CSI trigger event, wherein the bit width of the CSI request field can be configured by radio resource control (RRC) parameters.

3. The A-CSI feedback method according to claim 1, characterized in that, Also includes: Receive DL scheduling DCI belonging to a DCI format; and When the DCI format of the DL scheduling DCI includes a CSI request field for A-CSI reporting, the DL scheduling DCI is determined to be the A-CSI trigger event, wherein the DL scheduling DCI is enabled to implement the ultra-reliable and low latency communication (URLLC) service type.

4. The A-CSI feedback method according to claim 1, characterized in that, Also includes: Receive DL scheduling DCI belonging to a DCI format; and When the DCI format of the DL scheduling DCI includes a CSI request field for A-CSI reporting, the DL scheduling DCI is determined to be the A-CSI trigger event, wherein the transmission of the DL scheduling DCI is bundled with the transmission of the physical downlink shared channel (PDSCH).

5. The A-CSI feedback method according to claim 1, characterized in that, Also includes: Receive DL scheduling DCI belonging to a DCI format; Receive uplink (UL) scheduling downlink control information (DCI) in DCI format, including a CSI request field; and The A-CSI reporting is performed according to the DL scheduling DCI that covers the UL scheduling DCI.

6. The A-CSI feedback method according to claim 1, characterized in that, Also includes: Receive an indication for either an A-CSI report triggered by DL scheduling DCI or an A-CSI report triggered by UL scheduling DCI as the preferred A-CSI triggering method; Receive UL scheduling DCI in DCI format including CSI request field for triggering A-CSI reporting and DL scheduling DCI in DCI format including CSI request field for triggering A-CSI reporting; and When the indication specifies that the UL scheduling DCI triggers A-CSI reporting as the preferred A-CSI triggering method, the A-CSI reporting is performed in response to the UL scheduling DCI; or when the indication specifies that the DL scheduling DCI triggers A-CSI reporting as the preferred A-CSI triggering method, the A-CSI reporting is performed in response to the DL scheduling DCI.

7. The A-CSI feedback method according to claim 6, characterized in that, Configure a parameter for the DL-Scheduled DCI to represent an offset X, which is between the time slot of the DL-Scheduled DCI containing a set of aperiodic non-zero power NZP CSI reference signal (RS) resources and the time slot for transmitting that set of aperiodic NZP CSI-RS resources; and Configure a parameter for the UL scheduling DCI to represent an offset X, which is between the time slot of the DL scheduling DCI that triggers a set of aperiodic non-zero power NZP CSI-RS resources and the time slot for transmitting the set of aperiodic NZP CSI-RS resources.

8. The A-CSI feedback method according to claim 1, characterized in that, Also includes: Receive and decode downlink transmissions; When the downlink transmission decoding fails, the negative acknowledgment (NACK) response to the downlink transmission will be determined as the A-CSI trigger event; Obtain a pre-configured A-CSI setup to perform CSI measurements; and The results of the CSI measurement are used for the A-CSI reporting.

9. The A-CSI feedback method according to claim 1, characterized in that, Also includes: Receive and decode downlink transmissions; When the downlink transmission decoding fails, the negative acknowledgment (NACK) response to the downlink transmission will be determined as the A-CSI trigger event; Obtain the A-CSI configuration from the historical A-CSI configuration; Perform CSI measurements using the obtained A-CSI configuration; and The results of the CSI measurement are used for the A-CSI reporting.

10. The A-CSI feedback method according to claim 1, characterized in that, Also includes: Receive an instruction for an A-CSI triggering method to activate the A-CSI triggering method, wherein the instruction for the A-CSI triggering method can be configured to activate A-CSI triggered by DL scheduling DCI, A-CSI triggered by NACK with DCI scheduling, and A-CSI triggered by NACK without DCI scheduling.

11. The A-CSI feedback method according to claim 1, characterized in that, Also includes: Perform simultaneous slot CSI feedback, wherein the UE receives a DCI at the start of a slot and triggers the A-CSI report before the end of the slot in response to the DCI received at the start of the simultaneous slot.

12. The A-CSI feedback method according to claim 1, characterized in that, The A-CSI configuration includes a CSI request field for A-CSI reporting type when A-CSI reporting is performed on the Physical Uplink Control Channel (PUCCH) and a CSI request field for A-CSI reporting type when A-CSI reporting is performed on the Physical Uplink Shared Channel (PUSCH). The A-CSI reporting is performed according to the A-CSI configuration.

13. The A-CSI feedback method according to claim 12, characterized in that, The bit width of the CSI request of the A-CSI reporting type, which is reported on the Physical Uplink Control Channel (PUCCH), can be configured by the RRC parameter.

14. The A-CSI feedback method according to claim 1, characterized in that, The A-CSI configuration includes an A-CSI trigger status list field for A-CSI reporting types on the Physical Uplink Control Channel (PUCCH) and an A-CSI trigger status list field for A-CSI reporting types on the Physical Uplink Shared Channel (PUSCH), wherein the A-CSI reporting is performed according to the A-CSI configuration.

15. The A-CSI feedback method according to claim 1, characterized in that, Also includes: The A-CSI configuration in the DL scheduling DCI is received, wherein the A-CSI configuration in the DL scheduling DCI is shared by the A-CSI reporting type for A-CSI reporting on the physical uplink control channel PUCCH and the A-CSI reporting type for A-CSI reporting on the physical uplink shared channel PUSCH. The A-CSI configuration is received in an RRC signal, wherein the A-CSI configuration in the RRC signal includes one or more RRC parameters for an A-CSI reporting type for A-CSI reporting on the Physical Uplink Control Channel PUCCH and one or more RRC parameters for an A-CSI reporting type for A-CSI reporting on the Physical Uplink Shared Channel PUSCH, and the A-CSI reporting is performed according to the A-CSI configuration.

16. The A-CSI feedback method according to claim 1, characterized in that, The A-CSI configuration includes an A-CSI reporting type indication, indicating either an A-CSI reporting type for A-CSI reporting on the Physical Uplink Control Channel (PUCCH) or an A-CSI reporting type for A-CSI reporting on the Physical Uplink Shared Channel (PUSCH), as the determined A-CSI reporting type; the A-CSI reporting is performed according to the A-CSI configuration using the determined A-CSI reporting type.

17. The A-CSI feedback method according to claim 16, characterized in that, The A-CSI reporting type indication can be configured via DCI signaling or radio resource control (RRC) signaling.

18. The A-CSI feedback method according to claim 16, characterized in that, The A-CSI reporting type indication is represented by one of a plurality of DCI formats, wherein the first DCI format among the plurality of DCI formats indicates that the A-CSI reporting type activated for A-CSI reporting on the Physical Uplink Control Channel (PUCCH) is the determined A-CSI reporting type, and the second DCI format among the plurality of DCI formats indicates that the A-CSI reporting type activated for A-CSI reporting on the Physical Uplink Shared Channel (PUSCH) is the determined A-CSI reporting type.

19. The A-CSI feedback method according to claim 16, characterized in that, The A-CSI reporting type indication is represented by the Radio Network Temporary Identifier (RNTI). When the CSI request in the DCI is scrambled with the RNTI, it indicates that the trigger state of the A-CSI reporting type for A-CSI reporting on the Physical Uplink Control Channel (PUCCH) is activated. When the CSI request in the DCI is not scrambled with the RNTI, it indicates that the trigger state of the A-CSI reporting type for A-CSI reporting on the Physical Uplink Shared Channel (PUSCH) is activated.

20. The A-CSI feedback method according to claim 16, characterized in that, The A-CSI reporting type indication can be configured by the medium access control (MAC) control element (CE).

21. The A-CSI feedback method according to claim 16, characterized in that, The Media Access Control (MAC) control element CE includes a status indication field, in which a code point indicates whether an entry in the A-CSI configuration list is activated or deactivated.

22. The A-CSI feedback method according to claim 21, characterized in that, The code points in the field indicated by the status This refers to an A-CSI configuration that includes PUCCH resources for A-CSI reporting in the indicated bandwidth part (BWP) and has the j-th CSI reporting configuration identifier in the list, whose reporting type is set to the A-CSI reporting type for A-CSI reporting on the Physical Uplink Control Channel (PUCCH), where j = i + 1.

23. The A-CSI feedback method according to claim 16, characterized in that, The Media Access Control (MAC) control element CE includes a trigger state sub-selection field for sub-selection of the A-CSI configuration, and a code point in the trigger state sub-selection field indicating whether an entry in the trigger state list is selected for A-CSI reporting.

24. The A-CSI feedback method according to claim 23, characterized in that, The code point in the trigger state sub-selection field T i This indicates that the j-th trigger state in the trigger state list was selected in the A-CSI reporting sub-selection, where j = i + 1.

25. The A-CSI feedback method according to claim 1, characterized in that, Also includes: The first part of the A-CSI with higher priority is reported on PUCCH, and the second part of the A-CSI with lower priority is reported on PUSCH.

26. The A-CSI feedback method according to claim 1, characterized in that, Also includes: The first part of the A-CSI that is of higher importance for determining the MCS is reported on PUCCH, and the second part of the A-CSI that is of lower importance for determining the MCS is reported on PUSCH.

27. The A-CSI feedback method according to claim 1, characterized in that, Also includes: Select an A-CSI mode as the determined A-CSI reporting type to transmit A-CSI on the A-CSI reporting channel; and Send an indication of the selected A-CSI mode, which instructs the A-CSI reporting channel.

28. The A-CSI feedback method according to claim 1, characterized in that, Enables the A-CSI reporting type for URLLC service type, which performs A-CSI reporting on the Physical Uplink Control Channel (PUCCH).

29. A method for aperiodic channel state information (A-CSI) feedback, executed in a base station, characterized in that, include: Determine the A-CSI configuration, including the A-CSI reporting type; The A-CSI configuration is transmitted in the downlink channel to trigger A-CSI reporting; and Receive A-CSI on the A-CSI reporting channel according to the determined A-CSI reporting type; The A-CSI configuration includes different A-CSI configuration sets configured separately for different DCI formats. For each A-CSI transmission mode, CSI resources and A-CSI configurations are configured separately for different DCI formats. The A-CSI transmission modes include A-CSI reporting on PUCCH and A-CSI reporting on PUSCH. The method further includes: Transmission timing preference settings indicate that either the earlier or later received DCI is used as the active A-CSI trigger for the DCI.

30. The A-CSI feedback method according to claim 29, characterized in that, Also includes: Send downlink (DL) scheduling downlink control information (DCI) in DCI format, including the CSI request field; The bit width of the CSI request can be configured by radio resource control (RRC) parameters.

31. The A-CSI feedback method according to claim 29, characterized in that, Also includes: Send downlink (DL) scheduling downlink control information (DCI) in DCI format, including the CSI request field; The DL scheduling DCI is enabled for the service type of ultra-reliable and low-latency communication (URLLC).

32. The A-CSI feedback method according to claim 29, characterized in that, Also includes: Send downlink (DL) scheduling downlink control information (DCI) in DCI format, including the CSI request field; The transmission of the DL-scheduled DCI is bundled with the transmission of the physical downlink shared channel (PDSCH).

33. The A-CSI feedback method according to claim 29, characterized in that, Also includes: The transmission includes downlink (DL) scheduling downlink control information (DCI) in DCI format, which includes a CSI request field. The DCI format contains an indication that the DL scheduling DCI overwrites the UL scheduling DCI for A-CSI reporting.

34. The A-CSI feedback method according to claim 29, characterized in that, Also includes: Send an indication to indicate either an A-CSI report triggered by DL scheduling DCI or an A-CSI report triggered by UL scheduling DCI as the preferred A-CSI triggering method.

35. The A-CSI feedback method according to claim 34, characterized in that, Configure a parameter for the DL-Scheduled DCI to represent an offset X, which is between the time slot of the DL-Scheduled DCI containing a set of aperiodic non-zero power NZP CSI reference signal (RS) resources and the time slot for transmitting that set of aperiodic NZP CSI-RS resources; and Configure a parameter for the UL scheduling DCI to represent an offset X, which is between the time slot of the DL scheduling DCI that triggers a set of aperiodic non-zero power NZP CSI-RS resources and the time slot for transmitting the set of aperiodic NZP CSI-RS resources.

36. The A-CSI feedback method according to claim 29, characterized in that, Also includes: Send an indication of an A-CSI triggering method to activate the A-CSI triggering method, wherein the indication of the A-CSI triggering method can be configured to activate A-CSI triggered by DL scheduling DCI, A-CSI triggered by NACK with DCI scheduling, and A-CSI triggered by NACK without DCI scheduling.

37. The A-CSI feedback method according to claim 29, characterized in that, Also includes: A DCI is sent to trigger a simultaneous slot CSI feedback, wherein the DCI triggers the A-CSI reporting at the beginning of a slot before the end of the slot.

38. The A-CSI feedback method according to claim 29, characterized in that, The A-CSI configuration includes a CSI request field for A-CSI reporting type when A-CSI reporting is performed on the Physical Uplink Control Channel (PUCCH) and a CSI request field for A-CSI reporting type when A-CSI reporting is performed on the Physical Uplink Shared Channel (PUSCH).

39. The A-CSI feedback method according to claim 38, characterized in that, The bit width of the CSI request of the A-CSI reporting type, which is reported on the Physical Uplink Control Channel (PUCCH), can be configured by the RRC parameter.

40. The A-CSI feedback method according to claim 29, characterized in that, The A-CSI configuration includes an A-CSI trigger status list field for A-CSI reporting types when A-CSI reporting is performed on the Physical Uplink Control Channel (PUCCH), and an A-CSI trigger status list field for A-CSI reporting types when A-CSI reporting is performed on the Physical Uplink Shared Channel (PUSCH).

41. The A-CSI feedback method according to claim 29, characterized in that, The A-CSI configuration is transmitted in the DL scheduling DCI, and the A-CSI configuration in the DL scheduling DCI is shared by the A-CSI reporting type that reports A-CSI on the physical uplink control channel PUCCH and the A-CSI reporting type that reports A-CSI on the physical uplink shared channel PUSCH. The A-CSI configuration is transmitted in the RRC signal, wherein the A-CSI configuration in the RRC signal includes one or more RRC parameters for an A-CSI reporting type for A-CSI reporting on the Physical Uplink Control Channel PUCCH and one or more RRC parameters for an A-CSI reporting type for A-CSI reporting on the Physical Uplink Shared Channel PUSCH.

42. The A-CSI feedback method according to claim 29, characterized in that, The A-CSI configuration includes an A-CSI reporting type indication, which indicates either the A-CSI reporting type performed on the Physical Uplink Control Channel (PUCCH) or the A-CSI reporting type performed on the Physical Uplink Shared Channel (PUSCH), as the determined A-CSI reporting type.

43. The A-CSI feedback method according to claim 42, characterized in that, The A-CSI reporting type indication can be configured via DCI signaling or radio resource control (RRC) signaling.

44. The A-CSI feedback method according to claim 42, characterized in that, The A-CSI reporting type indication is represented by one of a plurality of DCI formats, wherein the first DCI format among the plurality of DCI formats indicates that the A-CSI reporting type activated for A-CSI reporting on the Physical Uplink Control Channel (PUCCH) is the determined A-CSI reporting type, and the second DCI format among the plurality of DCI formats indicates that the A-CSI reporting type activated for A-CSI reporting on the Physical Uplink Shared Channel (PUSCH) is the determined A-CSI reporting type.

45. The A-CSI feedback method according to claim 42, characterized in that, The A-CSI reporting type indication is represented by the Radio Network Temporary Identifier (RNTI). When the CSI request in the DCI is scrambled with the RNTI, it indicates that the trigger state of the A-CSI reporting type for A-CSI reporting on the Physical Uplink Control Channel (PUCCH) is activated. When the CSI request in the DCI is not scrambled with the RNTI, it indicates that the trigger state of the A-CSI reporting type for A-CSI reporting on the Physical Uplink Shared Channel (PUSCH) is activated.

46. ​​The A-CSI feedback method according to claim 42, characterized in that, The A-CSI reporting type indication can be configured by the medium access control (MAC) control element (CE).

47. The A-CSI feedback method according to claim 42, characterized in that, The Media Access Control (MAC) control element CE includes a status indication field, in which a code point indicates whether an entry in the A-CSI configuration list is activated or deactivated.

48. The A-CSI feedback method according to claim 47, characterized in that, The code points in the field indicated by the status This refers to an A-CSI configuration that includes PUCCH resources for A-CSI reporting in the indicated bandwidth part (BWP) and has the j-th CSI reporting configuration identifier in the list, whose reporting type is set to the A-CSI reporting type for A-CSI reporting on the Physical Uplink Control Channel (PUCCH), where j = i + 1.

49. The A-CSI feedback method according to claim 42, characterized in that, The Media Access Control (MAC) control element CE includes a trigger state sub-selection field for sub-selection of the A-CSI configuration, and a code point in the trigger state sub-selection field indicating whether an entry in the trigger state list is selected for A-CSI reporting.

50. The A-CSI feedback method according to claim 49, characterized in that, The code point in the trigger state sub-selection field T i This indicates that the j-th trigger state in the trigger state list was selected in the A-CSI reporting sub-selection, where j = i + 1.

51. The A-CSI feedback method according to claim 29, characterized in that, Also includes: Receive the first part of the A-CSI with higher priority on the PUCCH and the second part of the A-CSI with lower priority on the PUSCH.

52. The A-CSI feedback method according to claim 29, characterized in that, Also includes: Receive the first part of the A-CSI that is of higher importance for MCS determination on the PUCCH and the second part of the A-CSI that is of lower importance for MCS determination on the PUSCH.

53. The A-CSI feedback method according to claim 29, characterized in that, Also includes: Receive an indication of the A-CSI mode selected by the UE, which is used to instruct the A-CSI reporting channel; and A-CSI is detected on the A-CSI reporting channel.

54. The A-CSI feedback method according to claim 29, characterized in that, Enables the A-CSI reporting type for URLLC service type, which performs A-CSI reporting on the Physical Uplink Control Channel (PUCCH).

55. A user equipment (UE), comprising: transceiver; and A processor, connected to the transceiver and configured to perform the following steps, including: Identify the aperiodic channel state information (A-CSI) triggering event in the A-CSI triggering method; Determine the A-CSI reporting type in the A-CSI configuration; and A-CSI reporting is performed in response to the determined A-CSI triggering event according to the determined A-CSI reporting type; The A-CSI configuration includes different A-CSI configuration sets configured separately for different DCI formats. For each A-CSI transmission mode, CSI resources and A-CSI configurations are configured separately for different DCI formats. The A-CSI transmission modes include A-CSI reporting on PUCCH and A-CSI reporting on PUSCH. The steps performed by the processor further include: Obtain a time preference setting that indicates either an earlier or later received DCI as the active A-CSI trigger for the DCI; and In response to the activated A-CSI, the DCI is triggered to perform the A-CSI reporting based on the time preference settings.

56. A base station includes: transceiver; and A processor, connected to the transceiver and configured to perform the following steps, including: Determine the configuration of aperiodic channel state information (A-CSI) including the type of A-CSI reporting; Transmit the A-CSI configuration in the downlink channel to trigger A-CSI reporting; and Receive A-CSI on the A-CSI reporting channel according to the determined A-CSI reporting type; The A-CSI configuration includes different A-CSI configuration sets configured separately for different DCI formats. For each A-CSI transmission mode, CSI resources and A-CSI configurations are configured separately for different DCI formats. The A-CSI transmission modes include A-CSI reporting on PUCCH and A-CSI reporting on PUSCH. The steps performed by the processor further include: Transmission timing preference settings indicate that either the earlier or later received DCI is used as the active A-CSI trigger for the DCI.

57. A chip, comprising: A processor for calling and running a computer program stored in memory, causing a device on which the chip is mounted to perform the method of any one of claims 29 to 54.

58. A computer-readable storage medium storing a computer program, wherein the computer program causes a computer to perform the method of any one of claims 1 to 28.

59. A computer-readable storage medium storing a computer program, wherein, The computer program causes the computer to perform the method according to any one of claims 29 to 54.

Images