CN116326001A

CN116326001A - Aperiodic channel state information feedback method, user equipment and base station

Info

Publication number: CN116326001A
Application number: CN202080105314.1A
Authority: CN
Inventors: 殷晓雪; 生嘉
Original assignee: JRD Communication Shenzhen Ltd
Current assignee: JRD Communication Shenzhen Ltd
Priority date: 2020-10-14
Filing date: 2020-10-14
Publication date: 2023-06-23
Also published as: WO2022077288A1

Abstract

A method performed by a User Equipment (UE) and a base station for aperiodic channel state information (a-CSI) feedback. The UE determines an A-CSI trigger event in an A-CSI trigger 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 in response to the determined A-CSI trigger event according to the determined A-CSI reporting type, such as A-CSI reporting on a Physical Uplink Control Channel (PUCCH) or A-CSI reporting on a physical uplink shared channel (physical uplink shared channel, PUSCH). The trigger event includes at least one of Negative Acknowledgement (NACK), uplink scheduling downlink control information (UL DCI), and downlink scheduling downlink control information (DL DCI). The configuration of the different a-CSI reporting types may be configured separately, activated and deactivated, sub-selected and signaled between the UE and the base station, respectively.

Description

Aperiodic channel state information feedback method, user equipment and base station

Technical Field

The present invention relates to the field of communications systems, and in particular, to a method for aperiodic channel state information (aperiodic channel state information, a-CSI) feedback, a user equipment, and a base station.

Background

Wireless communication systems and networks have evolved towards broadband and mobile systems. In a cellular wireless communication system, a User Equipment (UE) is connected to a radio access network (radio access network, RAN) through a wireless link. The RAN includes a set of Base Stations (BSs) that provide radio links to the UEs located in cells covered by the base stations, and an interface to a Core Network (CN) that provides overall network control. It should be appreciated that the RAN and CN each perform a respective function related to the overall network. The third generation partnership project (3rd Generation Partnership Project,3GPP) has developed a so-called long term evolution (Long Term Evolution, LTE) system, i.e. an evolved universal mobile telecommunications system terrestrial radio access network (Evolved Universal Mobile Telecommunication System Territorial Radio Access Network, E-UTRAN) for mobile access networks in which base stations, or enodebs or eNB (evolved NodeB), support more macro cells. Recently, LTE is further evolving towards so-called 5G or New air-interface NR (New Radio) systems, where one or more cells are supported by a base station called a gNB.

Ultra-reliable low-latency communication (URLLC) is one of several different types of use cases supported by the above-described 5G NR standard, as specified by release 15 of 3 GPP. URLLC is a communication service that successfully transmits data packets with stringent requirements, in particular in terms of availability (avai availability), delay and reliability. URLLC was developed to support the above-mentioned emerging applications and services, such as wireless control and automation in industrial factory environments, inter-vehicle communication for improved security and efficiency, and the above-mentioned haptic internet. Therefore, URLLC is important for 5G because it supports the vertical industry to bring new services to the whole telecommunications industry.

One of the key features mentioned above is low latency, which is a key point to enable automated driving of automobiles and tele-surgery. The low latency allows the network to be optimized to handle incredibly large amounts of data with minimal latency. The quality of service (quality of service, qoS) required by URLLC is quite different from mobile broadband services.

The URLLC guaranteed delay is 1 millisecond or less. A Time sensitive network (Time-sensitive networking, TSN) is another component of the 5G URLLC described above. All devices on the URLLC connection must be synchronized on the same time basis. For example, the enabling techniques of URLLC include: integrating frame structure, incredible fast turnaround, efficient control and data resource sharing, grant-free based uplink transmission, and advanced channel coding schemes.

Technical problem

Channel state information (Channel state information, CSI) feedback enhancements may promote reliability and real-time of URLLC services. Whether or not aperiodic CSI (a-CSI) is transmitted on a physical uplink control channel (physical uplink control channel, PUCCH) is a pending problem. The a-CSI reported by the physical uplink shared channel (physical upl ink shared channel, PUSCH) can only be triggered by Uplink (UL) DCI according to the new air interface (NR) standard previously released. UL DCI, e.g., DCI format 0_0, is a format of UL scheduling DCI for scheduling PUSCH in one cell according to technical specification (technical specification, TS) 38.212, 7.3.1.1. However, the above-described conventional a-CSI triggering method cannot be applied to a partial scenario. For example, when UL data for scheduling is not transmitted in DL traffic with heavy traffic, transmitting UL DCI only for triggering a-CSI reporting is not resource efficient. Providing UL grants, e.g. UL DCI, for URLLC services should be avoided when no UL data is ongoing. Thus, a new a-CSI triggering method is required.

Disclosure of Invention

An object of the present disclosure is to propose a method, a user equipment and a base station for aperiodic channel state information (a-CSI) feedback.

A first aspect of the present disclosure provides a method for aperiodic channel state information (aperiodic channel state information, a-CSI) feedback, executable in a User Equipment (UE), comprising:

determining an A-CSI trigger event in an A-CSI trigger method;

determining an A-CSI reporting type in the A-CSI configuration; a kind of electronic device with high-pressure air-conditioning system

And responding to the determined A-CSI trigger event according to the determined A-CSI reporting type to report the A-CSI.

A second aspect of the present disclosure provides a method for aperiodic channel state information (a-CSI) feedback, executable in a base station, comprising:

determining an A-CSI configuration comprising an A-CSI reporting type;

transmitting the A-CSI configuration in a downlink channel to trigger A-CSI reporting; a kind of electronic device with high-pressure air-conditioning system

And receiving the A-CSI on the A-CSI reporting channel according to the determined A-CSI reporting type.

A third aspect of the present disclosure provides a user equipment comprising a transceiver and a processor coupled to the transceiver. The processor is configured to perform steps comprising:

determining an A-CSI trigger event in an A-CSI trigger method;

A fourth aspect of the present disclosure provides a base station comprising a transceiver and a processor coupled to the transceiver. The processor is configured to perform steps comprising:

determining an A-CSI configuration comprising an A-CSI reporting type;

The method disclosed above may be implemented in a chip. The chip may include a processor for invoking and running a computer program stored in memory to cause a device on which the chip is installed to perform the disclosed methods.

The disclosed methods may be programmed as computer-executable instructions stored in a non-transitory computer-readable medium. The non-transitory computer readable medium, when loaded into a computer, instructs the processor of the computer to perform the disclosed methods.

The non-transitory computer readable medium may include at least one of the group consisting of: hard disk, CD-ROM, optical storage, magnetic storage, read-only memory, programmable read-only memory, erasable programmable read-only memory (Erasable Programmable Read Only Memory, EPROM), electrically erasable programmable read-only memory (Electrically Erasable Programmable Read Only Memory, EEPROM), and flash memory. The disclosed methods can be programmed as a computer program product that causes a computer to perform the disclosed methods. The disclosed methods may be programmed as a computer program that causes a computer to perform the disclosed methods.

Advantageous effects

The present disclosure provides the above-described CSI feedback enhancement for URLLC and industrial internet of things (industrial internet of things, IIOT). In this disclosure, the new triggering method for a-CSI is mainly focused, because the conventional a-CSI triggering method is not applicable to all scenarios. It is not clear how to transmit a-CSI on PUCCH. The present disclosure provides several detailed embodiments of configuring a-CSI on PUCCH. The above embodiments can significantly improve the CSI feedback efficiency, meeting higher quality of service (QoS) requirements, especially for URLLC traffic.

The invention is primarily improved in at least two ways: the first is a new trigger method for a-CSI, and the second is a detailed configuration of a-CSI transmitted on PUCCH. The present invention provides several embodiments aiming at the technical problems of the two aspects. For example, one embodiment provides a detailed solution for Downlink (DL) control information (downlink control information, DCI) triggering and NACK triggering a-CSI and explains how to combine the two schemes and use the corresponding scheduling rules. In addition, seven alternative embodiments are presented to support a-CSI on PUCCH and corresponding detailed configurations for distinguishing a-CSI on PUCCH from a-CSI on PUSCH. The embodiments of the present disclosure are presented to improve the CSI resource efficiency and reduce the a-CSI feedback delay.

Drawings

In order to more clearly describe the above-described embodiments of the present invention or related arts, the following drawings will be used for description when briefly describing the above-described embodiments. It is evident that the figures are only some embodiments of the invention, from which other figures can be obtained by a person skilled in the art without this being assumed.

Fig. 1 is a schematic diagram of a telecommunications system.

Fig. 2 is a schematic diagram illustrating a CRAN with a baseband unit pool, a remote radio head, and a UE.

Fig. 3 is a schematic diagram of a method according to an embodiment of the present invention performed at a base station side.

Fig. 4 is a schematic diagram illustrating the above disclosed method performed at a User Equipment (UE) side according to one embodiment of the present disclosure.

Fig. 5 is a schematic diagram of a method with coverage indication disclosed in a first alternative embodiment of the invention.

Fig. 6 is a schematic diagram of the above disclosed method with time preference settings according to a second alternative embodiment of the present invention.

Fig. 7 is a schematic diagram of the above disclosed method with priority indication according to a third alternative embodiment of the present invention.

Fig. 8 is a schematic diagram illustrating the disclosed method with a preconfigured a-CSI configuration according to a fourth alternative embodiment of the present disclosure.

Fig. 9 is a schematic diagram of the above disclosed method with historical a-CSI configuration according to a fifth alternative embodiment of the invention.

Fig. 10 is a schematic diagram of a NACK-triggered CSI measurement and calculation preprocessing of a-CSI according to a sixth alternative embodiment of the present invention.

Fig. 11 is a schematic diagram of two-stage a-CSI reporting according to an eighth embodiment of the present invention.

Fig. 12 is a schematic diagram of co-timeslot a-CSI reporting according to a ninth alternative embodiment of the present invention.

Fig. 13 is a schematic diagram of the above disclosed method according to a tenth alternative embodiment of the present invention, wherein the a-CSI configuration is differentiated by upper layer signaling.

Fig. 14 schematically illustrates the disclosed method with priority a-CSI reporting according to an eleventh alternative embodiment of the present disclosure.

Fig. 15 schematically illustrates the disclosed method of prioritized a-CSI reporting according to a twelfth alternative embodiment of the present disclosure.

Fig. 16 is a schematic diagram illustrating the disclosed method of a UE-selected a-CSI reporting type according to a thirteenth alternative embodiment of the present disclosure.

Fig. 17 is a block diagram of a system for wireless communication according to an embodiment of the present disclosure.

Detailed Description

Technical matters, structural features, achieved objects and effects of the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. In particular, the terminology used in the described embodiments of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.

Referring to fig. 1, a telecommunication system including a group 100a of a plurality of UEs, a Base Station (BS) 200a and a network entity apparatus 300 performs the disclosed method according to an embodiment of the present disclosure. The plurality of UE groups 100a may include UEs 10a, UEs 10b, and other UEs. Fig. 1 is exemplary and not limiting, and the system may include more UEs, BSs, and CN entities. The connections between the devices and the device components are represented in the figures as lines and arrows. The connection between the devices may be achieved by a wireless connection. The connections between the device components may be made through wires, buses, traces, cables, or optical fibers. The UE 10a may include a processor 11a, a memory 12a, and a transceiver 13a. The UE 10b may include a processor 11b, a memory 12b, and a transceiver 13b. The base station 200a may include a baseband unit (BBU) 204a. The baseband unit 204a may include a processor 201a, a memory 202a, and a transceiver 203a. The network entity device 300 may comprise a processor 301, a memory 302 and a transceiver 303. Each of the

processors

11a, 11b, 201a, and 301 may be configured to implement the proposed functions, procedures, and/or methods described herein. The radio interface protocol layers may be implemented in the

processors

11a, 11b, 201a and 301. Each of the

memories

12a, 12b, 202a and 302 is operable to store various programs and information to operate the connected processors. Each of the transceivers 13a, 13b, 203a, and 303 is operatively coupled to a connected processor to transmit and/or receive radio signals or wired signals. The UE 10a may communicate with the UE 10b via a side link. The base station 200a may be one of an eNB, a gNB, or other type of radio node.

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 (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 a baseband circuit and a Radio Frequency (RF) circuit to process radio frequency signals. When the embodiments are implemented in software, the techniques may be implemented with modules, units, programs, functions, entities, etc. performing the functions. The modules may be stored in memory and executed by the processor. The memory may be implemented within the processor or external to the processor, in which case it can be communicatively coupled to the processor via various means as is known in the art.

The network entity device 300 may be a node in the CN. The CN may include an LTE CN or 5G core network (5G core network,5GC) including a user plane function (user plane function, UPF), a session management function (session management function, SMF), a mobility management function (mobility management function, AMF), unified data management (unified data management, UDM), a policy control function (pol icy control function, PCF), a control plane/user plane separation (control plane/user plane separation, cup), an authentication server (authentication server, AUSF), a network slice selection function (network sl ice selection function, NSSF), and the network exposure function (network exposure function, NEF).

Reference is made to the figures. Referring to fig. 2, a base station 200b is one embodiment of the base station 200a, including a central controller (central controller, CC) 210, access points 211-1, 211-2,. M is a positive integer. The central controller 210 may be implemented as a Central Unit (CU) and may include BBUs, such as BBU 204a, connected with the Access Points (APs) 211-1, 211-2. Each of the access points 211-1, 211-2, 211-M may be implemented as a radio node, remote Unit (RU), or remote radio head (remote radio head, RRH), and may include transmission and reception points (transmission and reception point, TRP). The access points 211-1, 211-2, 211-M may be located in different locations.

The central controller 210 receives wireless signals from a set of V User Equipments (UEs) of 100b through a set of M distributed radio nodes. V is a positive integer. The V-group user equipment comprises UE 10-1, 10-2, 10-3 and … -10-V. The UEs 10-1, 10-2, 10-3 and …, 10-V, may be located in different locations.

The technical problem considered above belongs to the field of high density connections and non-orthogonal multiple access (NOMA) in CRAN systems. In one example, the CRAN network operates in a time division duplex (time division duplex, TDD) mode in which channel estimation is performed through uplink pilot transmission.

Each coherent time slot is divided between two uplink training instances using orthogonal uplink pilot, uplink and downlink data transmissions. Embodiments of the present disclosure handle uplinks from V UEs to M single antenna Access Points (APs). Each AP independently performs uplink channel estimation at each slot.

The APs 211-1, 211-2, 211-M are distributed within the coverage area and managed by the central controller 210, which central controller 210 contains a centralized Base Band Unit (BBU) pool and handles the operation of the physical and network layers. Media access control (medium access control, MAC) layers such as data decoding and encoding, scheduling, and power allocation. The AP is linked to the central controller 210 by a high performance transmission link known as a fronthaul (fronthaul). The forwarding may be accomplished through an optical cable or a high bandwidth wireless channel. The system of fig. 2 including the base station 200b and the UE is a simplified example of a CRAN. The APs 211-1, 211-2, and 211-M perform channel estimation and the link-level transmission chain until equalized. The central controller 210 performs signal decoding, encoding, modulation, demodulation, scheduling, and MAC layer operations. The Uplink (UL) transmission of control signals or data may be a transmission operation from the UE to the base station. The Downlink (DL) transmission of the control signal or data may be a transmission operation from the base station to the UE.

Referring to fig. 3 and 4 in cross, a base station such as the base station 200a and a UE such as one of the

UEs

10a or 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 may be transmitted in the form of a control signal including UL DCI, DL DCI, radio resource control (radio resource control, RRC) parameters and a medium access control (medium access control, MAC) Control Element (CE), or in the form of a combination of the control signals.

The UE receives the a-CSI configuration (block 320). The UE determines an a-CSI triggering event in an a-CSI triggering method (block 321) and determines an a-CSI reporting type in an 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 triggering event according to the determined a-CSI reporting type (block 323). And the A-CSI is sent by the UE on an 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).

The a-CSI is triggered by DL scheduling DCI:

in one embodiment, the a-CSI reporting may be triggered by DL grant for scheduling PDSCH transmissions. The DL grant may be DL DCI of one DCI format. The DL DCI is DL scheduling DCI for scheduling PDSCH. The triggered a-CSI may be used to determine the modulation and coding scheme (modulation and coding scheme, MCS) parameters for the retransmission if the PDSCH needs to be retransmitted. In the above description, CSI and CSI reporting may be used interchangeably.

First, a new indication parameter is defined in the DL DCI format as an indication mechanism for triggering a-CSI reporting. The indication mechanism in the previous version of the NR standard can be reused. For example, a new n-bit CSI request field may be included in the DL DCI format. The DCI formats may include, for example, any combination of DCI format 1_0, DCI format 1_1, DCI format 1_2, and other DCI formats for scheduling PDSCH. And the number of "n" may be determined by an upper layer parameter, such as a Radio Resource Control (RRC) parameter reportTriggerSize. The parameter reportTriggerSize may be reused and configured for UL DCI trigger a-CSI. Alternatively, new parameters, such as reporttriggersize_dl, may be introduced to specifically indicate such DL DCI.

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

the DL DCI triggering the a-CSI may be specific to URLLC traffic:

retransmission of data after decoding failure is undesirable because the URLLC service requires higher transmission reliability and lower delay. In order to ensure that the retransmission data can be successfully decoded, the CSI reporting needs to be reported in time. However, for the eMBB traffic, the latency requirement is not strict and the network may schedule the data retransmission with information reported by periodic CSI. In this way, the CSI reporting triggered by the DL DCI provides further benefits to the URLLC traffic. The base station may specifically enable DL DCI trigger a-CSI for the type of service of URLLC.

The network may trigger the a-CSI with DL grant only when scheduling PDSCH:

the DL DCI triggering method can improve signaling efficiency. During the absence of UL data transmission, transmitting UL DCI dedicated to trigger a-CSI is not efficient control signaling. Similarly, it is also inefficient to transmit DL DCI without scheduling PDSCH to trigger a-CSI. Thus, the network may trigger the a-CSI with DL grant only when PDSCH is scheduled. The base station may trigger a-CSI by a DL grant (e.g., in the form of DL DCI) only when the DL DCI is configured to schedule a bonded physical downlink shared channel (physical downl ink shared channel, PDSCH). The UE receives the DL DCI of a scheduling PDSCH and performs A-CSI reporting in response to the DL DCI. The transmission of DL scheduling DCI is bundled with the transmission of PDSCH.

When DL DCI triggered a-CSI and UL DCI triggered a-CSI coexist, providing the following solution to the problem of coexistence of DL DCI triggered a-CSI and UL DCI triggered a-CSI described above:

-option 1: the DL DCI triggered a-CSI may cover the UL DCI triggered a-CSI because the DL DCI triggered a-CSI has higher priority and stricter low latency requirements. Reference is made to the figures. Referring to fig. 5, the base station may transmit a coverage indication to the UE, wherein the DL scheduling DCI is indicated to cover UL scheduling DCI for a-CSI reporting (block 310 a) and transmit DL DCI for triggering a-CSI and UL DCI for triggering a-CSI to the UE (block 311 a). When DL DCI for triggering a-CSI and UL DCI for triggering a-CSI are received (block 330), a UE, such as one of the

UEs

10a or 10b, may perform a-CSI reporting according to the DL DCI covering the UL DCI that the UE may receive before or after the DL DCI (block 331). The base station receives the CSI feedback (block 312 a).

-option 2: the UE may be affected by one of the earlier or later triggers. That is, the time preference setting indicates one of the earlier-received DCI or the later-received DCI as an a-CSI trigger DCI for triggering activation of a-CSI reporting. The time preference settings may be determined by a network entity, such as the base station, and sent to the UE. Alternatively, the time preference settings may be determined by the UE. Referring to fig. 6, the base station transmits an a-CSI configuration including time preference settings to the UE (block 311 b). The UE obtains the time preference settings (block 333) and performs a-CSI reporting to a base station in response to the activated a-CSI trigger DCI according to the time preference settings (block 334). The base station receives the CSI feedback (block 312 b).

-option 3: referring to fig. 7, the base station determines one of DL DCI triggered a-CSI reports or UL DCI triggered a-CSI reports as a priority a-CSI triggering method (block 340) and transmits an indication indicating the determined priority a-CSI triggering method to the UE through DCI or an upper layer parameter such as a Radio Resource Control (RRC) signal (block 341). The UE receives the indication of the determined priority a-CSI triggering method (block 342) and performs a-CSI reporting to a base station according to the priority a-CSI triggering method (block 343). The UE receives the indication indicating one of DL scheduling DCI triggered a-CSI reporting or UL scheduling DCI triggered a-CSI reporting. The UE receives a UL DCI belonging to one DCI format and a DL DCI belonging to one DCI format, wherein the DCI format of the UL DCI comprises a CSI request field for triggering A-CSI reporting, and the DCI format of the DL DCI comprises a CSI request field for triggering A-CSI reporting. And the UE responds to the UL scheduling DCI to report the A-CSI when the indication indicates that the UL scheduling DCI triggers the A-CSI to report, or responds to the DL scheduling DCI to report the A-CSI when the indication indicates that the DL scheduling DCI triggers the A-CSI to report.

Independent configuration of aperiodic triggeringoffset:

the upper layer parameter apersidiotriggeringoffset is configured in an information element IE NZP-CSI-RS-resource set and is used for triggering UL DCI by A-CSI. The parameter apeeriodictriggeringoffset represents an offset X between a time slot containing DCI triggering a set of non-periodic non-zero-power (NZP) CSI-RS resources and a time slot of the set of non-periodic non-zero-power (NZP) CSI-RS resources transmission.

The parameter for DL DCI trigger may be configured separately from the UL DCI trigger. A parameter is configured for UL scheduling DCI, representing an offset X between a time slot of UL scheduling DCI containing a set of non-periodic non-zero-power (NZP) CSI-RS resources triggered and a time slot of transmission of the set of non-periodic non-zero-power (NZP) CSI-RS resources. Similarly, another parameter, such as apeeriodictriggeringoffset_dl, may be included in IE NZP-CSI-RS-resource set for a-CSI triggered DL DCI to represent an offset X between a time slot containing DL DCI triggering a set of non-periodic non-zero-power (NZP) CSI-RS resources and a time slot of the set of non-periodic non-zero-power (NZP) CSI-RS resources transmission.

An embodiment of the present invention may utilize any combination of the above rules. Examples of the UE described herein may include one of the UE 10a or UE 10 b. Examples of the base station in the above description may include the base station 200a. The a-CSI reporting or a-CSI feedback is performed on the uplink from the UE to the base station. In the description herein, CSI reporting and CSI are used interchangeably. In addition, HARQ-ACKs represent HARQ feedback, which may include Acknowledgements (ACKs) and Negative Acknowledgements (NACKs). Downlink Control Information (DCI) in a DCI format is transmitted from a BS, such as the BS 200a, to a UE, such as the UE 10a or the UE 10 b. The radio resource control parameters include parameters carried in an RRC control signal transmitted from a BS such as the BS 200a to a UE such as the UE 10a or the UE 10 b. The term "network" may include a base station, a CN network entity, or a combination of base stations and CN network entities.

The a-CSI is triggered by NACK:

one embodiment of the present invention provides NACK-triggered a-CSI as an alternative triggering method for a-CSI reporting. The NACK triggered a-CSI reporting may include two cases: the first is NACK trigger A-CSI, DCI scheduling is not performed, and the second is NACK trigger with DCI scheduling.

For the first case described above, the a-CSI triggered by NACK without DCI scheduling needs to solve one problem: how to indicate to the UE the detailed configuration of the a-CSI reporting. According to Technical Specification (TS) 38.321, 6.1.3.13, each code point (codepoint) of the DCI field "CSI request" is associated with a trigger state configured in the RRC Information Element (IE) CSI-apeeriodics triggerstatelist. The IE CSI-AperiodicTriggerStateList is configured to provide the list of aperiodic trigger states to the UE. For each trigger state, the associted reportconfiginfoslist in the RRC information element IE CSI-apeeriodictriggerstatelist provides resource information for various types of CSI measurements. Upon receiving a value representing a code point associated with a trigger state, the UE may perform CSI reference signal (CSI reference signal, CSI-RS) measurements, CSI interference measurements (CSI interference measurement, CSI-IM) and/or synchronization signal blocks (synchronization signal block, SSB) and a-CSI reporting at L1 according to all entries in the associtreportconfigmnfolist for the received trigger state. Since the NACK-triggered a-CSI without DCI scheduling cannot provide such resource information to the UE, the UE cannot perform the a-CSI reporting.

In one embodiment of the invention, a base station indicates to the UE an a-CSI configuration for a-CSI reporting for reporting a-CSI without DCI scheduling. In a first example of the embodiment, the UE is preconfigured with the resource information and trigger information associated with a-CSI reporting. For example, a default a-CSI configuration may be pre-stored in the UE. When performing the NACK-triggered CSI reporting, the UE may perform the a-CSI reporting based on the pre-stored a-CSI configuration. In a second example of the above embodiment, the base station may indicate a default a-CSI configuration to the UE through upper layer signaling, e.g. RRC parameters. For example, the default a-CSI configuration may be configured and displayed in CSI-MeasConfig. When the a-CSI trigger DCI or CSI request field is not provided in the DCI to the UE, the default a-CSI configuration may be defined as defaultcsiriequest in the UE. The UE may report the A-CSI according to the configuration information provided by the DefaultCSIRequest.

Referring to fig. 8, the base station transmits a downlink transmission, such as a PDCCH or PDSCH, to the UE (block 350). The UE receives and decodes the downlink transmission (block 351). When the downlink transmission decoding fails, the UE generates a Negative Acknowledgement (NACK) as HARQ feedback for the downlink transmission. The UE will determine the NACK as the a-CSI triggering event in response to the downlink transmission and trigger a-CSI reporting to the base station in response to the NACK (block 352). In reporting a-CSI, the UE takes 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).

In addition, if one or more CSI requests are included in the historical DCI, the UE may obtain the default a-CSI configuration from the historical DCI. The UE may also reuse the resource information and trigger information from the historical DCI associated with an a-CSI report as the default a-CSI configuration. That is, the UE may perform the a-CSI measurement using the resource information and perform a-CSI reporting using the trigger information from the historical DCI. However, without historical DCI, the UE may use other schemes.

Referring to fig. 9, the base station transmits a downlink transmission such as a PDCCH or PDSCH to the UE (block 360). The UE receives and decodes the downlink transmission (block 361). When the downlink transmission decoding fails, the UE generates a Negative Acknowledgement (NACK) as HARQ feedback for the downlink transmission. The UE will determine that the NACK is the a-CSI triggering event in response to the downlink transmission and trigger a-CSI reporting to the base station in response to the NACK (block 362). When reporting the A-CSI, the UE acquires the A-CSI configuration from the historical A-CSI configuration to perform CSI measurement and calculation (block 363), and takes the result of the CSI measurement and calculation as the CSI feedback reported by the A-CSI. (block 364). The base station receives the CSI feedback (block 365).

One problem with NACK triggered a-CSI with DCI scheduling is: when to start the a-CSI measurement and calculation. The UE performing a-CSI measurements and calculations after identifying whether the HARQ feedback to be sent to the base station is ACK or NACK may lengthen a-CSI reporting and increase delay. Some embodiments of the invention are provided below to solve the problem.

All the time calculate a-CSI reporting for URLLC:

in order to meet the delay requirement of the URLLC service, the UE may perform a-CSI measurement and calculation in response to each CSI request indicated by DCI. Referring to fig. 10, the base station transmits a plurality of DCI signals with CSI requests to a UE (block 370). The UE receives the DCI signal 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 Acknowledgement (NACK) as HARQ feedback to the downlink transmission. The UE determines the NACK in response to the downlink transmission as the a-CSI triggering event and triggers an a-CSI report to the base station in response to the NACK (block 372). In 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).

When the A-CSI reporting method triggered by the NACK responds to the NACK to perform A-CSI reporting, the UE can send the A-CSI together with HARQ feedback of the NACK. The base station may schedule data retransmissions associated with the HARQ feedback based on the a-CSI. Alternatively, since the a-CSI report may indicate that the HARQ-ACK is NACK, the HARQ feedback may also be omitted during the a-CSI report to improve the signaling efficiency.

Simplified a-CSI reporting:

different from the above scheme, measurement and calculation of the a-CSI may be performed after the result of the HARQ-ACK is obtained. In order to report the A-CSI in time, the reported A-CSI can be simplified, for example, only a part of the A-CSI is reported. The portion of the a-CSI may be reported first, and then the remaining portion of the a-CSI may optionally be reported on available resources. Referring to fig. 11, the UE performs a-CSI reporting in response to an a-CSI triggering event (block 381). When performing the a-CSI reporting, the UE reports the first portion of the a-CSI to the base station in a first phase of the a-CSI reporting (block 383) and reports the second portion of the a-CSI to the base station in a second phase of the a-CSI reporting (block 385), thereby forming a two-phase a-CSI reporting. The base station receives the first portion of the a-CSI in a first phase (block 384) and receives the second portion of the a-CSI in a second phase (block 386). The a-CSI part reported first may have a higher priority and be reported together with the HARQ-ACK. The determination of CSI priority may follow the priority rules defined in section 5.2.5 of TS 38.214. The DCI format in the above embodiment may be UL DCI or DL DCI.

The a-CSI triggering method used by the UE may be applied to various a-CSI cases to provide flexibility for different scenarios. The A-CSI triggering method can be configured through DCI or upper layer parameters such as RRC parameters, and can be used as an indication of the A-CSI triggering method. The parameter may be acsigtermethodind. As shown in table 1, for example, the base station transmits acsigtermethod ind=0 to the UE to activate the DL DCI triggered a-CSI, ACSITriggerMethodInd =1 to activate the NACK triggered a-CSI, wherein the NACK triggered a-CSI has DCI scheduling, acsigtermethod ind=2 to activate the NACK triggered a-CSI, wherein the NACK triggered a-CSI has no DCI scheduling, and acsigtermethod ind=3 to activate one of the other a-CSI triggering methods.

TABLE 1

And the UE receives the indication of the activated A-CSI triggering method and responds to an A-CSI triggering event to report the A-CSI according to the activated A-CSI triggering method. It should be noted that the triggering method detailed above is not limited to an a-CSI reporting channel. The UE may report a-CSI on PUCCH, PUSCH, or other channels.

Detailed solution of a-CSI on PUCCH:

a-CSI reporting needs to be done on PUCCH. The a-CSI on the PUCCH may enhance scheduling flexibility of the base station and reduce signaling overhead. It is inefficient to allocate the entire PUSCH transmission for several bits of CSI. One embodiment of the present invention may provide co-slotted CSI feedback. Referring to fig. 12, the base station transmits DCI to the UE to trigger co-slotted CSI feedback (block 390). The UE receives the DCI from the base station at the beginning of one slot (block 391) and performs co-slotted CSI feedback. Upon co-slotted 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). Co-slotted CSI feedback facilitates very fast CSI feedback, which improves the accuracy of the CSI, especially in case of fast moving UEs or fast interference variations.

Configuration of a-CSI on PUCCH:

the a-CSI on the PUCCH also causes a number of technical problems to be solved, such as how to configure the above-mentioned related configuration parameters of the a-CSI on the PUCCH, whether to distinguish the a-CSI configuration parameters on the PUCCH from the a-CSI configuration parameters on the PUSCH, etc. How to coordinate the relationship between a-CSI on PUCCH and a-CSI on PUSCH, etc. Some embodiments are provided below to address these technical issues.

Separate configuration of a-CSI on PUCCH and a-CSI on PUSCH in DCI:

in one embodiment, the base station may configure a-CSI on PUCCH and a-CSI on PUSCH, respectively, and indicate the a-CSI configuration to one or more UEs. That is, all the above related configurations of a-CSI reporting may be configured for PUCCH and PUSCH, respectively.

The DCI is used to trigger the a-CSI reporting by indicating which CSI report should be reported in the CSI request field. The CSI request field is configured in the A-CSI trigger DCI. The CSI request fields in the DCI may be configured for a-CSI on PUCCH and a-CSI on PUSCH, respectively. That is, the base station configures a CSI request field for a-CSI reporting on PUCCH in the a-CSI trigger DCI, and configures a CSI request field for a-CSI reporting on PUSCH in the a-CSI trigger DCI. The base station transmits an A-CSI configuration to the UE in the form of the A-CSI trigger DCI, wherein the A-CSI configuration comprises the CSI request field for A-CSI reporting on a PUCCH and the CSI request field for A-CSI reporting on a PUSCH. And the UE receives the A-CSI configuration in the form of the A-CSI triggering DCI and reports the A-CSI according to the A-CSI configuration. For a-CSI on PUSCH, the above-described original configuration in the previous version may be preserved. For a-CSI on PUCCH, new parameters may be configured. For example, the new parameter for a-CSI on PUCCH may be referred to as one CSI request of PUCCH. The CSI request of a-CSI on PUSCH may be an n 1-bit parameter, which is determined by an upper layer parameter reportTriggerSize. Thus, the CSI request for the PUCCH may be an n 2-bit parameter determined by the upper layer parameter reporttriggersize_pucch. The values of n1 and n2 are respectively configured by the upper layer parameters reportTriggerSize and reporttriggersize_pucch, and may be the same or different.

The parameter apeeriodics triggerstatelist is an a-CSI trigger state list, and includes one or more a-CSI reporting configurations and trigger state lists of resource sets for channel and/or interference measurement. When the number of the CSI trigger states in the aperiodic trigger state list apeiiodic triggerstatelist 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 trigger state among the plurality of trigger states. The parameter apiodics triggerstatelist may be configured separately for distinguishing between a-CSI configuration on PUCCH and a-CSI configuration on PUSCH. For example, an apeeriodictriggerstatelist_for PUCCH may be introduced to indicate a trigger state list of a-CSI on the PUCCH. In addition, a new CSI reporting type 'apeeriodiconpucch' may be introduced for the upper layer parameter CSI-ReportConfig to indicate the a-CSI reporting on PUCCH, and the original 'apeeriodic' in CSI-ReportConfig represents a-CSI on PUSCH. The CSI reporting type is a mode of CSI reporting on one type of channel, such as PUCCH or PUSCH. The CSI reporting type may be referred to herein as CSI mode or CSI transmission mode.

The base station configures an A-CSI trigger state list in the A-CSI trigger DCI for reporting A-CSI on a PUCCH, and configures an A-CSI trigger state list in the A-CSI trigger DCI for reporting A-CSI on a PUSCH. The base station sends an A-CSI configuration to the UE in the form of the A-CSI trigger DCI, wherein the A-CSI configuration comprises the A-CSI trigger state list for A-CSI reporting on a PUCCH and the A-CSI trigger state list for A-CSI reporting on a PUSCH, and the UE receives the A-CSI configuration in the form of the A-CSI trigger DCI and performs A-CSI reporting according to the A-CSI configuration.

Separate RRC configuration of a-CSI on PUCCH and a-CSI on PUSCH:

unlike the above scheme, in the present embodiment, the configuration of the a-CSI on the PUCCH and the configuration of the a-CSI on the PUSCH are separated only at the upper layer, and the a-CSI triggering DCI configures only one CSI request (CSI request), thereby saving DCI signaling overhead. The configuration of the RRC parameters for the a-CSI reporting is the same as described in the previous embodiment, and the RRC parameters reportTriggerSize, aperiodicTriggerStateList, CSI-ReportConfig or other parameters related to the a-CSI reporting may be configured for a-CSI reporting on PUCCH and a-CSI reporting on PUSCH, respectively. The base station may inform the UE on which channel to report the a-CSI by a 1-bit indication. This 1-bit parameter may be configured by DCI or upper layer parameters (e.g., RRC parameters).

Referring to fig. 13, the base station transmits a common a-CSI configuration in DCI for different a-CSI reporting types and a separate a-CSI configuration in RRC signals for different a-CSI reporting types to the UE (block 400). The DCI may be UL scheduling DCI or DL scheduling DCI. The public A-CSI configuration in the DCI is shared by an A-CSI reporting type for reporting A-CSI by a PUCCH and an A-CSI reporting type for reporting A-CSI by a PUSCH. The separate a-CSI configuration in the RRC signal includes one or more RRC parameters of the a-CSI reporting type for a-CSI reporting on the PUCCH and one or more RRC parameters of the a-CSI reporting type 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 common a-CSI configuration and the separate a-CSI configuration (block 403). The base station receives the CSI feedback (block 406).

Unified configuration of a-CSI on PUCCH and a-CSI on PUSCH:

the embodiment with smaller influence on the existing protocol is to keep the existing configuration mechanism unchanged, and not configure PUCCH reporting A-CSI and PUSCH reporting A-CSI independently. That is, the two a-CSI transmission modes, a-CSI reporting on PUCCH and a-CSI reporting on PUSCH, are not co-existing, only one of the a-CSI transmission modes is enabled each time a-CSI reporting. The mode in which a-CSI is reported on one channel is called CSI mode or CSI transmission mode. If no mechanism informs the UE on which channel the current A-CSI report is transmitted, the UE cannot identify the currently enabled A-CSI transmission mode. In order to solve the above-described problems, examples are provided below.

a) Indication determined by DCI or upper layer:

in one embodiment, the a-CSI configuration includes an a-CSI reporting type indication indicating one of an a-CSI reporting type of a-CSI reporting on the PUCCH or an a-CSI reporting type of a-CSI reporting on PUSCH as the determined a-CSI reporting type. And the UE reports the A-CSI according to the A-CSI configuration and the determined A-CSI reporting type. The base station informs the UE of the A-CSI transmission mode through an A-CSI reporting type indication parameter Aperiodics IMode or an RRC parameter and other upper layer parameters in DCI. The A-CSI transmission mode indicates that A-CSI reporting is performed on an uplink channel. The new indication parameter aperiodic csimode of only 1 bit can be enough to indicate one of PUCCH or PDSCH. As shown in table 2, for example, apeeriodics csimode=0 indicates PUCCH reporting a-CSI, aperiodicCSIMode =1 indicates PUSCH reporting a-CSI.

TABLE 2

b) Differentiated by different DCI formats:

and distinguishing the A-CSI mode by a DCI format aiming at the DCI signaling overhead. For example, the base station may trigger a-CSI reporting on PUSCH using a first UL DCI format and a-CSI reporting on PUSCH using a second DL DCI format. Alternatively, the DCI formats may be classified to trigger CSI transmission modes alone. That is, each DCI format represents one a-CSI transmission mode. Each of the a-CSI reporting on PUCCH and the a-CSI reporting on PUSCH is triggered by a unique DCI format. In the example that the base station uses DL DCI to trigger a-CSI, according to a mapping relationship between a DCI format and a CSI mode, the base station may use DCI format1_0 to trigger a-CSI report on PUCCH as the determined a-CSI report type, and DCI format1_1 to trigger a-CSI report on PUSCH as the determined a-CSI report type. Alternatively, the mapping may be configurable and determined by the network entity.

c) New RNTI

The a-CSI mode may be indicated by a new radio network temporary identifier (radio network temporary identifier, RNTI). The new RNTI may include an a-CSI-PUCCH-RNTI. For reporting a-CSI on PUCCH, the base station may scramble the CSI request field in DCI with an a-CSI-PUCCH-RNTI to activate one of a plurality of trigger states of a-CSI reporting on the PUCCH. On the other hand, the base station may use the CSI request field in DCI not scrambled by an a-CSI-PUCCH-RNTI to activate one of the plurality of trigger states for a-CSI reporting on PUSCH. Similarly, this new RNTI may include an a-CSI-PUSCH-RNTI for scrambling the CSI request field in the DCI. The base station may scramble the CSI request field in DCI with an a-CSI-PUSCH-RNTI to activate one of a plurality of trigger states of a-CSI reporting on the PUSCH. On the other hand, the base station may activate one of the plurality of trigger states for a-CSI reporting on PUCCH using the CSI request field in DCI not scrambled by an a-CSI-PUSCH-RNTI.

MAC CE activates/deactivates a-CSI:

in one embodiment, the base station and the UE may distinguish the configuration of one of a-CSI on PUCCH or a-CSI on PUSCH from the other by a new media access control (medium access control, MAC) Control Element (CE). The advantage of this embodiment is that the configuration of the a-CSI on PUSCH may be the same as the current standard and the impact on the current protocol may be minimized. The new MAC CE may trigger activation and deactivation of a-CSI on PUCCH. The base station may use a new CSI reporting type "apeeriodicconconpucch" in the upper layer parameter CSI-ReportConfig to indicate the reporting type of the a-CSI reported on PUCCH.

Activation and deactivation of a-CSI reporting on PUCCH may be identified by a MAC subheader with a logical channel identifier (logic channel identifier, LCID) in the MAC CE. For example, the MAC CE is an X bit, and includes a plurality of fields, such as a serving cell ID, a bandwidth part (BWP) ID, a status indication, a reserved bit, and the like. The serving cell ID field indicates an identity of a serving cell to which the MAC CE is applicable. The BWP ID field indicates UL BWP applied by the MAC CE as a code point of the DCI BWP ID field. The status indication field indicates the activation and deactivation status of the a-CSI configuration in a list CSI-reportconfigtoadmodlist configured in CSI-MeasConfig. The list CSI-reportconfigtoadmodlist is a list of a plurality of a-CSI configurations.

The MAC CE includes a plurality of status indications. The status indication field may comprise m bits and is represented as a variable S _i To represent the code point in the field, where the value of i may be between 0 and 2 ^m -1. One code point in the status indication field indicates activation or deactivation of an entry of the a-CSI configuration list. Code point S in the field of the status indication _i Refers to an a-CSI configuration that includes PUCCH resources for a-CSI reporting in a bandwidth part (BWP) indicator and has a j-th CSI reporting configuration identifier in the list, and the reporting type in the list is set to such a-CSI reporting type of a-CSI reporting on PUCCH. The variable j is derived from i. For example, j=i+1. For example, the first code point S ₀ Refers to an A-CSI configuration, wherein the A-CSI configuration is arranged in the following wayThe indicated BWP includes PUCCH resources for A-CSI reporting and has the lowest CSI-ReportConfigId in the CSI-ReportConfigToAddModList in the list, and the CSI-ReportConfigToAddModList has the reporting type set to apidocOnPUCCH, the second code point s ₁ Refers to an a-CSI configuration, wherein the a-CSI configuration comprises PUCCH resources for a-CSI reporting in the indicated BWP and has the second lowest CSI-ReportConfigId in the list CSI-reportconfigtoadmodlist, CSI-reportconfigtoadmodlist has the reporting type set to aperionicon PUCCH, and so on. If the number of CSI configurations in the list of the APRIODICOnPUCCH for which the CSI reporting type is set in the indicated BWP is less than 2 ^m The MAC entity in the UE may ignore the field S _i And applying all the CSI configurations. The S is _i Setting the field to 1 indicates that the S should be activated by _i The corresponding a-CSI configuration i indicated by the field. The S is _ii The field is set to 0, indicating that S should be deactivated _i The corresponding a-CSI configuration i indicated by the field.

Similarly, the above configuration may also be applied to a-CSI reporting on PUSCH. For example, the MAC CE may activate and deactivate a-CSI reporting on PUSCH and a-CSI reporting on PUCCH may use the legacy configuration mechanism. The activation and deactivation of a-CSI reporting on PUSCH may be identified by a MAC subheader with a Logical Channel Identifier (LCID) in a MAC CE. For example, the MAC CE is an X bit, and includes a plurality of fields, such as a serving cell ID, a bandwidth part (BWP) ID, a status indication, a reserved bit, and the like. The serving cell ID field indicates an identity of a serving cell to which the MAC CE is applicable. The BWP ID field indicates UL BWP applied by the MAC CE as a code point of the DCI BWP ID field.

The field of the status indication indicates the activation and deactivation status of the a-CSI configuration in CSI-reportconfigtoadmodlist configured in CSI-MeasConfig. The MAC CE includes a plurality of status indications. The status indication field may comprise m bits and is represented as a variable S _i To represent the code point in the field, whereThe value of i may be between 0 and 2 ^m -1. S is S ₀ Refers to an a-CSI configuration including PUSCH resources for a-CSI reporting in the indicated BWP and having the lowest CSI-reportconfigdmodlist in the list CSI-reportconfigtoadmodlist set to apeeriodictpusch of the type described above ₁ Refers to an a-CSI configuration, wherein the a-CSI configuration comprises PUSCH resources for a-CSI reporting in the indicated BWP and has the type set to the second lowest CSI-reportconfigtoadmodlist in the list CSI-reportconfigtoadmodlist, and so on. If the CSI reporting type in the indicated BWP is set to be less than 2 in the number of CSI configurations in the list of the apidocOnPUSCH ^m The MAC entity in the UE may ignore the field S _i And applying all the CSI configurations. The S is _i A field may be set to 1 to indicate the S _i The corresponding a-CSI configuration i indicated by the field is activated. The S is _i A field set to 0 indicates the S _i The corresponding a-CSI configuration i indicated by the field is deactivated.

MAC CE for triggering state sub-selection:

the a-CSI reporting configuration on the PUCCH is different from the a-CSI reporting configuration on the PUSCH in which channel to use for transmitting a-CSI. The resource information including parameters and configurations for a-CSI measurement and calculation may be the same and reused for a-CSI measurement and calculation by the UE, regardless of whether the UE reports and transmits a-CSI on PUCCH or PUSCH. In other words, the configuration of CSI requests in DCI for a-CSI on PUSCH may be configured only once, whereas the configuration of CSI requests in DCI for a-CSI reporting on PUCCH (including the trigger state) may be a subset of the a-CSI reporting configuration on PUSCH. Therefore, a sub-selected MAC CE for a-CSI configuration is proposed, called sub-selected MAC CE.

Similar to the previous embodiment, a new CSI reporting type "apeeriodicconconpucch" in the upper layer parameter CSI-ReportConfig may indicate the reporting type of the a-CSI report on PUCCH. The sub-select MAC CE may be identified by a MAC sub-header with LCID. The MAC CE may include Y bits including several parts of serving cell ID, BWP ID, trigger status sub-selection (trigger state subselection), DCI format indication, reserved bits, etc. The serving cell ID field indicates an Identity (ID) of a serving cell to which the MAC CE is applicable. The BWP ID field indicates UL BWP applied by the MAC CE as a code point of the DCI BWP ID field. The trigger state sub-select (trigger state subselection) field represents a selected state of the aperiodic trigger state configured in the aperiodic trigger state list apeichigerstatelist. The aperiodic trigger state list apeeriodictriggerstatelist can be an A-CSI configuration for reporting A-CSI on a PUSCH or a pre-stored A-CSI configuration for reporting A-CSI on a PUCCH. The selection state of the trigger state indicates whether the indicated trigger state is selected from the plurality of trigger states in the list apeeriodictriggerstatelist. The plurality of code points (codepoints) in the trigger state sub-select (trigger state subselection) field, in turn, refer to the plurality of trigger states (trigger states) in the list aperiodicTriggerStat eList. Each code point (codepoint) in the trigger state sub-selection (trigger state subselection) field references a trigger state in the list aperiodicT riggerStateList and indicates whether the referenced trigger state is selected from a plurality of trigger states in the list aperiodic triggerstatelist.

The trigger state sub-selection field in the sub-selection MAC CE may comprise k bits and is represented as variable T _i Wherein the variable T _i Representing the code point in the trigger state sub-selection field, where the value of i may be between 0 and 2 ^k -1. Code point T in the field of the trigger state sub-selection _i Indicating that the j-th trigger state in the trigger state list is selected or not selected in the sub-selection for A-CSI reporting, wherein j=i+1. For example T ₀ Refers to a first aperiodic trigger state configured in an apiodics triggerstatelist, T ₁ Refers to the second aperiodic trigger state configured in the apiodics triggerstatelist, and so on. The T is _i A field may be set to 1 to indicate what is being indicatedThe T is _i The j-th trigger state of the association indicated by the field is selected among the sub-selections for a-CSI reporting. Said T _i A field may be set to 0 to indicate that the T is not asserted by the T _i The j-th trigger state of the association indicated by the field is not selected in the sub-selection. The variable j may be derived from i. For example, j=i+1. The aperiodic trigger state list may be an a-CSI configuration configured in one DCI format for a-CSI reporting. In addition, the sub-selection MAC CE may be applied to sub-selection of a-CSI configuration derived from a-CSI configuration for any CSI reporting type.

And the DCI format indication (DCI format indication) field indicates which a-CSI trigger status list (a-CSI trigger state list) the MAC CE refers to, as different DCI formats may correspond to different apeeriodics triggerstatelists.

Transmission of individual a-CSI:

the a-CSI on PUCCH may reduce signaling overhead and improve the feedback efficiency, especially for URLLC services. However, the base station does not necessarily need all CSI reporting to determine the modulation and coding strategy (modulation and coding scheme, MCS), especially for URLLC traffic with very high requirements for low latency and high reliability. Thus, in one embodiment, the UE may report a-CSI alone for the base station to determine MCS. Referring to fig. 14, the UE reports a-CSI in response to an a-CSI trigger event, generates a-CSI, and determines a portion of the a-CSI as a first portion having high importance to MCS determination and a portion of the a-CSI as a second portion having lower importance to MCS determination (block 411). The UE may report the first portion of the a-CSI with high importance for MCS determination on PUCCH (block 413) and optionally report the second portion of the a-CSI with low importance for MCS determination on PUSCH available resources (block 415). The base station receives the first portion of the a-CSI on the PUCCH (block 414) and determines an 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).

Referring to fig. 15, the UE reports a-CSI in response to an a-CSI trigger event, generates a-CSI, and determines a portion of the a-CSI as a first portion having a high priority and a portion of the a-CSI as a second portion having a low priority (block 421). The UE may report the first portion of the a-CSI with high priority on PUCCH (block 423) and optionally report the second portion of the a-CSI with low priority on available resources of PUSCH (block 425). The base station receives the first portion of the a-CSI on the PUCCH (block 424) and determines an 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).

The second portion of the a-CSI with lower priority may be reserved by the UE without reporting. The determination of CSI priority may follow the priority rules defined in section 5.2.5 of TS 38.214. A threshold may be defined to prioritize high and low, CSI above which may be transmitted on PUCCH, while CSI not above which may be transmitted or ignored on the available PUSCH. The embodiments described may apply separate configurations for a-CSI on PUCCH and a-CSI on PUSCH.

UE selection mode:

in one embodiment, the UE selects on which channel to send a-CSI to the base station. As shown in fig. 16, the UE selects an a-CSI reporting type as the determined a-CSI reporting type to transmit a-CSI on an a-CSI reporting channel (e.g., one of PUCCH or PUSCH) of the a-CSI reporting type (block 431). The resource information and configuration of the a-CSI may be preconfigured by the base station. The respective configurations for a-CSI on PUCCH and a-CSI on PUSCH as described above may be applied in the embodiments.

The UE may send an indication to the base station indicating the a-CSI reporting type selected by the UE for 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 may send the indication on PUCCH. If the UE does not send the indication, the base station may detect the A-CSI on both PUCCH and PUSCH.

Alternatively, the above-described embodiments may apply the following modifications and rules:

separate configuration of different DCI formats:

although the above description is mainly directed to how to distinguish the configuration of a-CSI on PUCCH and a-CSI on PUSCH, a-CSI configurations of different DCI formats may be different. For each a-CSI transmission mode, the CSI resources and a-CSI configurations may be configured separately for different DCI formats. That is, the a-CSI configuration includes different a-CSI configuration sets configured separately for different DCI formats.

a-CSI on PUCCH supporting URLLC service only:

the a-CSI on PUCCH may increase the scheduling flexibility and reduce the delay of the CSI feedback. These advantages are more advantageous for URLLC services. In one embodiment, the base station and the UE support only a-CSI on PUCCH for URLLC. Accordingly, the CSI mode of the a-CSI reported on the PUCCH may be an identification of a URLLC service type distinguishing a URLLC service and an enhanced mobile broadband (eMBB).

Fig. 17 is a block diagram of a system 700 for wireless communication, as an example, according to one embodiment of the invention. The embodiments described herein may be implemented into a system using any suitably configured hardware and/or software. Fig. 17 shows a system 700 comprising Radio Frequency (RF) circuitry 710, baseband circuitry 720, processing unit 730, memory/storage 740, display 750, camera 760, sensor 770, and input/output (I/O) interface 780 coupled to one another as shown.

The processing unit 730 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 (application processor). The processor may be coupled to the memory/storage and configured to execute instructions stored in the memory/storage to cause various applications and/or operating systems to execute on the system.

The baseband circuitry 720 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may comprise a baseband processor. The baseband circuitry may handle various radio control functions that enable communication with one or more radio networks through radio frequency circuitry. The radio control functions described above may include, but are not limited to, signal modulation, encoding, decoding, frequency modulation shifting, and the like. In some embodiments, the baseband circuitry described above may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with 5G NR, LTE, evolved universal terrestrial radio access networks (Evolved Universal Terrestrial Radio Access Network, EUTRAN) and/or other wireless metropolitan area networks (Wireless Metropolitan Area Network, WMAN), wireless local area networks (Wireless Local Area Network, WLAN), wireless personal area networks (Wireless Personal Area Network, WPAN). An embodiment in which the baseband circuitry is configured to support radio communications of more than one wireless protocol may be referred to as a multi-mode baseband circuitry. In various embodiments, the baseband circuitry 720 may include circuitry to operate signals that are not strictly considered to be baseband frequencies. For example, in some embodiments, the baseband circuitry may include circuitry that operates on signals having an intermediate frequency that is between the baseband frequency and the frequency modulation.

The radio frequency circuitry 710 described above may enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry described above may include switches, filters, amplifiers, and the like to facilitate communication with a wireless network. In various embodiments, the radio frequency circuitry 710 described above may include circuitry to operate on signals that are not strictly considered to be frequency modulated. For example, in some embodiments, the radio frequency circuit may include circuitry that operates on a signal having an intermediate frequency between the fundamental frequency and the frequency modulation.

In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to the UE, eNB, or gNB may be embodied in whole or in part in one or more of radio frequency circuitry, baseband circuitry, and/or processing units. As used herein, "circuitry" may refer to, or be part of, or include an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in or functions associated with one or more software or firmware modules. In some embodiments, some or all of the constituent components of the baseband circuitry, processing unit, and/or memory/storage may be implemented together On a System On a Chip (SOC).

The memory/storage 740 may be used to load and store data and/or instructions, for example, for the system described above. The memory/storage described above for one embodiment may include any combination of suitable volatile memory, such as dynamic random access memory (Dynamic random access memory, DRAM), and/or non-volatile memory, such as flash memory. In various embodiments, the I/O interface 780 may include one or more user interfaces intended for a user to interact with the system and/or peripheral component interfaces intended for a peripheral component to interact with the system. The user interface may include, but is not limited to, a physical keyboard or keypad, a touchpad, a speaker, a microphone, and the like. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, universal serial bus (Universal Serial Bus, USB) ports, audio jacks, and power interfaces.

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 above-described sensors may include, but are not limited to, gyroscopic sensors, accelerometers, proximity sensors, ambient light sensors, and positioning units. The positioning unit may also be part of, or interact with, a baseband circuit and/or a radio frequency circuit to communicate with components of a positioning network, such as Global Positioning System (GPS) satellites. In various embodiments, the display 750 may include one display, such as a liquid crystal display and a touch screen display. In various implementations, the system 700 described above may be a mobile computing device, such as, but not limited to, a notebook computing device, a tablet computing device, a Netbook, an Ultrabook, a smart phone, and the like. In various embodiments, the system may have more or fewer components, and/or different architectures. The methods described herein may be implemented as a computer program where appropriate. The computer program may be stored on a storage medium, such as a non-transitory storage medium.

An embodiment of the present invention is a combination of techniques/procedures that may be employed in the 3GPP specifications to create the end product. Any combination of the embodiments described above is possible.

Those of ordinary skill in the art will appreciate that each of the elements, algorithms, and steps described and disclosed in the embodiments of the invention are implemented using electronic hardware or combinations of software in a computer and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technology. Those of ordinary skill in the art may implement the functionality of each particular application in different ways without departing from the scope of the invention. It will be appreciated by those of ordinary skill in the art that, since the operating procedures of the above-described systems, devices and units are substantially identical, reference may be made to the operating procedures of the systems, devices and units in the above-described embodiments. For ease of description and simplicity, these working procedures will not be described in detail.

It is to be understood that the disclosed systems, devices, and methods in the embodiments of the present invention may be implemented in other ways. The above embodiments are merely exemplary. The division of the units mentioned above is based on the division of the logic functions only, but other manners of division are possible when implemented. It is possible that multiple units or components are combined or integrated into another system. It is also possible that some features may be omitted or skipped. On the other hand, mutual coupling, direct coupling or communicative coupling in the above description or discussion is achieved by some ports, devices or units, whether communicating indirectly or through electronic, mechanical or other kind of means.

The elements mentioned above as separate components for explanation may be physically separate or not physically separate components. The units mentioned above may be physical units or not, that is to say may be arranged in one place or distributed over a plurality of network units. Some or all of the above units may be used according to the purpose of the embodiment. Furthermore, each functional unit in each embodiment may be integrated into one processing unit, or physically separate, or integrated into one processing unit having two or more units.

If the software functional unit is implemented for use and sale as a product, it may be stored on a computer readable storage medium. Based on this understanding, the technical solution proposed by the present invention may be implemented in a basic key part or in part in the form of a software product. Alternatively, a portion of the technical program beneficial to the conventional technology may be implemented as a software product. The software product in the computer is stored in a storage medium including a plurality of commands for a computing device (e.g., a personal computer, a server, or a network device) to perform all or part of the steps disclosed in embodiments of the present invention. Storage media include USB disk, removable hard disk, read Only Memory (ROM), random Access Memory (RAM), floppy disk, or other types of media capable of storing program code.

The invention is primarily improved in at least two ways: the first is a new trigger method for a-CSI, and the second is a detailed configuration of a-CSI transmitted on PUCCH. The present invention provides several embodiments aiming at the technical problems of the two aspects.

While this invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not to be limited to the disclosed embodiment, but is intended to cover various arrangements included within the scope of the appended claims without departing from the broadest interpretation of the claims.

Claims

1. A method for aperiodic channel state information (aperiodic channel state information, a-CSI) feedback, executable in a User Equipment (UE), comprising:

determining an A-CSI trigger event in an A-CSI trigger method;

2. The a-CSI feedback method according to claim 1, further comprising:

receiving Downlink (DL) scheduling DCI belonging to one downlink control information (downlink control information, DCI) format; a kind of electronic device with high-pressure air-conditioning system

When the DCI format of the DL scheduling DCI includes a CSI request field for a-CSI reporting, determining that the DL scheduling DCI is the a-CSI trigger event, wherein a bit width of the CSI request field is configurable by a radio resource control (radio resource control, RRC) parameter.

3. The a-CSI feedback method according to claim 1, further comprising:

receiving DL scheduling DCI belonging to one DCI format; a kind of electronic device with high-pressure air-conditioning system

When the DCI format of the DL scheduling DCI includes a CSI request field for a-CSI reporting, determining that the DL scheduling DCI is the a-CSI trigger event, wherein the DL scheduling DCI is enabled to implement an ultra-reliable low latency communication (ultra reliable and low latency communication, URLLC) service type.

4. The a-CSI feedback method according to claim 1, further comprising:

When the DCI format of the DL scheduling DCI includes a CSI request field for a-CSI reporting, determining the DL scheduling DCI as the a-CSI trigger event, wherein transmission of the DL scheduling DCI is bundled with a physical downlink shared channel (physical downlink shared channel, PDSCH) transmission.

5. The a-CSI feedback method according to claim 1, further comprising:

receiving DL scheduling DCI belonging to one DCI format;

receiving Uplink (UL) scheduling Downlink Control Information (DCI) of a DCI format including a CSI request field; a kind of electronic device with high-pressure air-conditioning system

And executing the A-CSI reporting according to the DL scheduling DCI covering the UL scheduling DCI.

6. The a-CSI feedback method according to claim 1, further comprising:

obtaining a time preference setting indicating one of earlier received DCI or later received DCI as an activated a-CSI triggered DCI; a kind of electronic device with high-pressure air-conditioning system

And according to the time preference setting, responding to the activated A-CSI trigger DCI to execute the A-CSI reporting.

7. The a-CSI feedback method according to claim 1, further comprising:

receiving one of an A-CSI report indicating to be used for indicating a DCI trigger of DL scheduling or an A-CSI report indicating to be used for indicating a DCI trigger of UL scheduling as a priority A-CSI triggering method;

receiving UL scheduling DCI including a DCI format of a CSI request field for triggering a-CSI reporting and DL scheduling DCI including a DCI format of a CSI request field for triggering a-CSI reporting; a kind of electronic device with high-pressure air-conditioning system

And when the indication indicates that the UL scheduling DCI triggers A-CSI reporting as the priority A-CSI triggering method, the A-CSI reporting is executed in response to the UL scheduling DCI, or when the indication indicates that the DL scheduling DCI triggers A-CSI reporting as the priority A-CSI triggering method, the A-CSI reporting is executed in response to the DL scheduling DCI.

8. The a-CSI feedback method according to claim 1, characterized in that a parameter is configured for the DL scheduling DCI to represent an offset X between a time slot containing DL scheduling DCI triggering a set of non-periodic non-zero power NZP CSI Reference Signal (RS) resources and a time slot transmitting the set of non-periodic NZP CSI-RS resources; a kind of electronic device with high-pressure air-conditioning system

A parameter is configured for the UL scheduling DCI to represent an offset X between a time slot containing DL scheduling DCI triggering a set of aperiodic non-zero power NZP CSI-RS resources and a time slot transmitting the set of aperiodic NZP CSI-RS resources.

9. The a-CSI feedback method according to claim 1, further comprising:

receiving and decoding a downlink transmission;

determining a Negative Acknowledgement (NACK) in response to the downlink transmission as the a-CSI triggering event when the downlink transmission decoding fails;

acquiring a pre-configured A-CSI configuration to perform CSI measurement; a kind of electronic device with high-pressure air-conditioning system

And using the result of the CSI measurement for reporting the A-CSI.

10. The a-CSI feedback method according to claim 1, further comprising:

receiving and decoding a downlink transmission;

acquiring the A-CSI configuration from the historical A-CSI configuration;

performing CSI measurement by using the obtained A-CSI configuration; a kind of electronic device with high-pressure air-conditioning system

And using the result of the CSI measurement for reporting the A-CSI.

11. The a-CSI feedback method according to claim 1, further comprising:

receiving an indication of an a-CSI triggering method to activate the a-CSI triggering method, wherein the indication of the a-CSI triggering method is configurable 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.

12. The a-CSI feedback method according to claim 1, further comprising:

and performing co-slotted CSI feedback, wherein the UE receives DCI at the beginning of one slot and triggers the a-CSI report before the end of the same slot in response to the DCI received at the beginning of the same slot.

13. The a-CSI feedback method according to claim 1, wherein the a-CSI configuration includes a CSI request field of an a-CSI reporting type for a-CSI reporting on a physical uplink control channel PUCCH and a CSI request field of an a-CSI reporting type for a-CSI reporting on a physical uplink shared channel PUSCH, the a-CSI reporting being performed according to the a-CSI configuration.

14. The a-CSI feedback method according to claim 13, characterized in that the bit width of the CSI request of the a-CSI reporting type for a-CSI reporting on the physical uplink control channel PUCCH is configurable by RRC parameters.

15. The a-CSI feedback method according to claim 1, wherein the a-CSI configuration comprises an a-CSI triggered status list field of an a-CSI reporting type for a-CSI reporting on a physical uplink control channel PUCCH and an a-CSI triggered status list field of an a-CSI reporting type for a-CSI reporting on a physical uplink shared channel PUSCH, the a-CSI reporting being performed according to the a-CSI configuration.

16. The a-CSI feedback method according to claim 1, further comprising:

receiving the A-CSI configuration in a DL scheduling DCI, wherein the A-CSI configuration in the DL scheduling DCI is shared by an A-CSI reporting type for A-CSI reporting on a physical uplink control channel PUCCH and an A-CSI reporting type for A-CSI reporting on a physical uplink shared channel PUSCH;

and receiving the A-CSI configuration in an RRC signal, wherein the A-CSI configuration in the RRC signal comprises one or more RRC parameters of an A-CSI reporting type for A-CSI reporting on a physical uplink control channel PUCCH and one or more RRC parameters of an A-CSI reporting type for A-CSI reporting on a physical uplink shared channel PUSCH, and the A-CSI reporting is performed according to the A-CSI configuration.

17. The a-CSI feedback method according to claim 1, wherein the a-CSI configuration includes an a-CSI reporting type indication indicating one of an a-CSI reporting type for a-CSI reporting on a physical uplink control channel PUCCH or an a-CSI reporting type for a-CSI reporting on a physical uplink shared channel PUSCH as the determined a-CSI reporting type; and the A-CSI reporting is carried out according to the A-CSI configuration and the determined A-CSI reporting type.

18. The a-CSI feedback method according to claim 17, characterized in that the a-CSI reporting type indication is configurable through DCI signaling or radio resource control (radio resource control, RRC) signaling.

19. The a-CSI feedback method of claim 17, wherein the a-CSI reporting type indication is represented by one of a plurality of DCI formats, a first one of the plurality of DCI formats representing an a-CSI reporting type that activates a-CSI reporting on a physical uplink control channel, PUCCH, as the determined a-CSI reporting type, and a second one of the plurality of DCI formats representing an a-CSI reporting type that activates a-CSI reporting on a physical uplink shared channel, PUSCH, as the determined a-CSI reporting type.

20. The a-CSI feedback method according to claim 17, wherein the a-CSI reporting type indication is represented by a radio network temporary identifier RNTI, wherein a CSI request in DCI indicates a trigger state of an a-CSI reporting type that activates a-CSI reporting on a physical uplink control channel PUCCH when scrambled with the RNTI, and wherein the CSI request in DCI indicates a trigger state of an a-CSI reporting type that activates a-CSI reporting on a physical uplink shared channel PUSCH when not scrambled with the RNTI.

21. The a-CSI feedback method according to claim 17, characterized in that the a-CSI reporting type indication is configurable by a medium access control (medium access control, MAC) Control Element (CE).

22. The a-CSI feedback method according to claim 17, wherein the medium access control, MAC, control element, CE, comprises a status indication field, one code point in the status indication field indicating whether to activate or deactivate an entry of the a-CSI configuration list.

23. The a-CSI feedback method according to claim 22, characterized in that the code point s in the field of the status indication _i Refers to an a-CSI configuration, which includes PUCCH resources for a-CSI reporting in an indicated bandwidth part (BWP), and has a j-th CSI reporting configuration identifier in the list, where a 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.

24. The a-CSI feedback method according to claim 17, characterized in that a medium access control, MAC, control element, CE, comprises 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 indicates whether an entry of a trigger state list is selected for a-CSI reporting.

25. The a-CSI feedback method according to claim 22, wherein the code point T in the trigger state sub-selection field _i Indicating that the j-th trigger state in the trigger state list is selected in the a-CSI reporting sub-selection, where j=i+1.

26. The a-CSI feedback method according to claim 1, further comprising:

reporting a first portion of a-CSI with higher priority on PUCCH and reporting a second portion of the a-CSI with lower priority on PUSCH.

27. The a-CSI feedback method according to claim 1, further comprising:

reporting a first portion of a-CSI with higher importance for MCS determination on PUCCH and reporting a second portion of the a-CSI with lower importance for MCS determination on PUSCH.

28. The a-CSI feedback method according to claim 1, further comprising:

Selecting an A-CSI mode as the determined A-CSI reporting type so as to transmit A-CSI on an A-CSI reporting channel; a kind of electronic device with high-pressure air-conditioning system

And sending the indication of the selected A-CSI mode, wherein the indication of the selected A-CSI mode indicates the A-CSI reporting channel.

29. The a-CSI feedback method according to claim 1, wherein the a-CSI configuration comprises different a-CSI configuration sets configured separately for different DCI formats.

30. The a-CSI feedback method according to claim 1, characterized in that an a-CSI reporting type for a-CSI reporting on a physical uplink control channel PUCCH is enabled for a URLLC service type.

31. A non-periodic channel state information (aperiodic channel state information, a-CSI) feedback method performed in a base station, comprising:

determining an A-CSI configuration comprising an A-CSI reporting type;

32. The a-CSI feedback method according to claim 31, further comprising:

transmitting Downlink (DL) scheduling Downlink Control Information (DCI) of a DCI format including a CSI request field;

The bit width of the CSI request may be configured by a radio resource control (radio resource control, RRC) parameter.

33. The a-CSI feedback method according to claim 31, further comprising:

wherein the DL scheduling DCI is enabled for a service type for ultra-reliable low latency communication (ultra reliable and low latency communication, URLLC).

34. The a-CSI feedback method according to claim 31, further comprising:

the transmission of DL scheduling DCI is bundled with the transmission of a bonded physical downlink shared channel (physical downlink shared channel, PDSCH).

35. The a-CSI feedback method according to claim 31, further comprising:

downlink (DL) scheduling Downlink Control Information (DCI) of a DCI format including a CSI request field is transmitted, the DCI format including an indication to indicate that the DL scheduling DCI covers UL scheduling DCI for a-CSI reporting.

36. The a-CSI feedback method according to claim 31, further comprising:

A time preference setting is transmitted indicating one of the earlier received DCI or the later received DCI as an activated a-CSI trigger DCI.

37. The a-CSI feedback method according to claim 31, further comprising:

and sending one of the A-CSI report indicating the trigger of the DL scheduling DCI or the A-CSI report indicating the trigger of the UL scheduling DCI as a priority A-CSI triggering method.

38. The a-CSI feedback method according to claim 31, wherein a parameter is configured for the DL scheduling DCI to represent an offset X between a time slot containing DL scheduling DCI triggering a set of non-periodic non-zero power NZP CSI Reference Signal (RS) resources and a time slot transmitting the set of non-periodic NZP CSI-RS resources; and configuring a parameter for the UL scheduling DCI to represent an offset X between a time slot containing DL scheduling DCI triggering a set of aperiodic non-zero power NZP CSI-RS resources and a time slot transmitting the set of aperiodic NZP CSI-RS resources.

39. The a-CSI feedback method according to claim 31, further comprising:

an indication of an a-CSI triggering method is sent to activate the a-CSI triggering method, wherein the indication of the a-CSI triggering method is configurable 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.

40. The a-CSI feedback method according to claim 31, further comprising:

and sending DCI to trigger the same-time-slot CSI feedback, wherein the DCI triggers the A-CSI reporting before the end of the same time slot when one time slot starts.

41. The a-CSI feedback method according to claim 31, wherein the a-CSI configuration includes a CSI request field of an a-CSI reporting type for a-CSI reporting on a physical uplink control channel PUCCH and a CSI request field of an a-CSI reporting type for a-CSI reporting on a physical uplink shared channel PUSCH.

42. The a-CSI feedback method according to claim 41, wherein the bit width of the CSI request of the a-CSI reporting type for a-CSI reporting on the physical uplink control channel PUCCH is configurable by RRC parameters.

43. The a-CSI feedback method according to claim 31, wherein the a-CSI configuration includes an a-CSI triggered status list field of an a-CSI reporting type for a-CSI reporting on a physical uplink control channel PUCCH and an a-CSI triggered status list field of an a-CSI reporting type for a-CSI reporting on a physical uplink shared channel PUSCH.

44. The a-CSI feedback method according to claim 31, wherein the a-CSI configuration in the DL scheduling DCI is shared by an a-CSI reporting type that performs a-CSI reporting on a physical uplink control channel PUCCH and an a-CSI reporting type that performs a-CSI reporting on a physical uplink shared channel PUSCH;

and transmitting the A-CSI configuration in an RRC signal, wherein the A-CSI configuration in the RRC signal comprises one or more RRC parameters of an A-CSI reporting type for A-CSI reporting on a physical uplink control channel PUCCH and one or more RRC parameters of an A-CSI reporting type for A-CSI reporting on a physical uplink shared channel PUSCH.

45. The a-CSI feedback method according to claim 31, wherein the a-CSI configuration includes an a-CSI report type indication indicating one of an a-CSI report type for a-CSI report on a physical uplink control channel PUCCH or an a-CSI report type for a-CSI report on a physical uplink shared channel PUSCH as the determined a-CSI report type.

46. The a-CSI feedback method according to claim 45, wherein the a-CSI reporting type indication is configurable through DCI signaling or radio resource control (radio resource control, RRC) signaling.

47. The a-CSI feedback method of claim 45, wherein the a-CSI reporting type indication is represented by one of a plurality of DCI formats, a first one of the plurality of DCI formats representing an a-CSI reporting type that activates a-CSI reporting on a physical uplink control channel, PUCCH, as the determined a-CSI reporting type, and a second one of the plurality of DCI formats representing an a-CSI reporting type that activates a-CSI reporting on a physical uplink shared channel, PUSCH, as the determined a-CSI reporting type.

48. The A-CSI feedback method of claim 45, wherein the A-CSI reporting type indication is indicated by a radio network temporary identifier, RNTI, a CSI request in DCI indicates a trigger state of activating an A-CSI reporting type for A-CSI reporting on a physical uplink control channel, PUCCH, when scrambled by the RNTI, and the CSI request in DCI indicates a trigger state of activating an A-CSI reporting type for A-CSI reporting on a physical uplink shared channel, PUSCH, when not scrambled by the RNTI.

49. The a-CSI feedback method of claim 45, wherein the a-CSI reporting type indication is configurable by a media access control (medium access control, MAC) Control Element (CE).

50. The a-CSI feedback method according to claim 45, wherein the medium access control MAC control element CE comprises a status indication field, one code point in the status indication field indicating whether to activate or deactivate an entry of the a-CSI configuration list.

51. The a-CSI feedback method according to claim 50, wherein code point s in said field of said status indication _i Refers to an a-CSI configuration, which includes PUCCH resources for a-CSI reporting in an indicated bandwidth part (BWP), and has a j-th CSI reporting configuration identifier in the list, where a 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.

52. The a-CSI feedback method according to claim 45, wherein a medium access control, MAC, control element, CE, comprises 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 indicates whether an entry of a trigger state list is selected for a-CSI reporting.

53. The a-CSI feedback method according to claim 50, wherein code point T in the trigger state sub-selection field _i Indicating that the j-th trigger state in the trigger state list is selected in the a-CSI reporting sub-selection, where j=i+1.

54. The a-CSI feedback method according to claim 31, further comprising:

a first portion of a-CSI with higher priority is received on PUCCH and a second portion of the a-CSI with lower priority is received on PUSCH.

55. The a-CSI feedback method according to claim 31, further comprising:

a first portion of a-CSI having a higher importance for MCS determination is received on PUCCH and a second portion of the a-CSI having a lower importance for MCS determination is received on PUSCH.

56. The a-CSI feedback method according to claim 31, further comprising:

receiving an indication of an A-CSI mode selected by UE, wherein the indication is used for indicating the A-CSI reporting channel; a kind of electronic device with high-pressure air-conditioning system

And detecting the A-CSI on the A-CSI reporting channel.

57. The a-CSI feedback method according to claim 31, wherein the a-CSI configurations comprise different sets of a-CSI configurations configured separately for different DCI formats.

58. The a-CSI feedback method according to claim 31, characterized in that an a-CSI reporting type for a-CSI reporting on a physical uplink control channel PUCCH is enabled for the URLLC service type.

59. A User Equipment (UE), comprising:

a transceiver; a kind of electronic device with high-pressure air-conditioning system

A processor coupled to the transceiver and configured to perform steps comprising:

determining aperiodic channel state information (aperiodic channel state information, a-CSI) trigger events in the a-CSI triggering method;

60. The user equipment of claim 59, wherein the processor further performs:

When the DCI format of the DL scheduling DCI includes a CSI request field for a-CSI reporting, determining the DL scheduling DCI as the a-CSI trigger event, wherein a bit width of the CSI request field may be set by a radio resource control (radio resource control, RRC) parameter.

61. The user equipment of claim 59, wherein the processor further performs:

When the DCI format of the DL scheduling DCI includes a CSI request field for a-CSI reporting, determining that the DL scheduling DCI is the a-CSI trigger event, wherein the DL scheduling DCI is enabled for an ultra-reliable low latency communication (ultra reliable and low latency communication, URLLC) service type.

62. The user equipment of claim 59, wherein the processor further performs:

When the DCI format of the DL scheduling DCI includes a CSI request field for a-CSI reporting, determining the DL scheduling DCI as the a-CSI trigger event, wherein transmission of the DL scheduling DCI is bundled with transmission of a physical downlink shared channel (physical downlink shared channel, PDSCH).

63. The user equipment of claim 59, wherein the processor further performs: receiving DL scheduling DCI belonging to a DCI format including a CSI request field;

64. The user equipment of claim 59, wherein the processor further performs: obtaining a time preference setting indicating one of earlier received DCI or later received DCI as an activated a-CSI triggered DCI; a kind of electronic device with high-pressure air-conditioning system

65. The user equipment of claim 59, wherein the processor further performs: receiving one of an A-CSI report indicating to be used for indicating a DCI trigger of DL scheduling or an A-CSI report indicating to be used for indicating a DCI trigger of UL scheduling as a priority A-CSI triggering method;

66. The user equipment of claim 59 wherein a parameter is configured for the DL scheduling DCI to represent an offset X between a time slot containing DL scheduling DCI triggering a set of aperiodic non-zero power NZP CSI Reference Signal (RS) resources and a time slot transmitting the set of aperiodic NZP CSI-RS resources; a kind of electronic device with high-pressure air-conditioning system

67. The user equipment of claim 59, wherein the processor further performs:

receiving and decoding a downlink transmission;

And using the result of the CSI measurement for reporting the A-CSI.

68. The user equipment of claim 59, wherein the processor further performs:

receiving and decoding a downlink transmission;

acquiring the A-CSI configuration from the historical A-CSI configuration;

And using the result of the CSI measurement for reporting the A-CSI.

69. The user equipment of claim 59, wherein the processor further performs:

receiving and decoding a downlink transmission;

responding to each CSI request indicated by DCI, and carrying out A-CSI measurement and calculation; a kind of electronic device with high-pressure air-conditioning system

And in NACK triggered A-CSI reporting, reporting the A-CSI used by the result of the CSI measurement and calculation.

70. The user equipment of claim 59, wherein the processor further performs:

71. The user equipment of claim 59, wherein the processor further performs: and performing co-slotted CSI feedback, wherein the UE receives DCI at the beginning of one slot and triggers the a-CSI report before the end of the same slot in response to the DCI received at the beginning of the same slot.

72. The user equipment of claim 59, wherein the a-CSI configuration comprises a CSI request field of an a-CSI reporting type for a-CSI reporting on a physical uplink control channel, PUCCH, and a CSI request field of an a-CSI reporting type for a-CSI reporting on a physical uplink shared channel, PUSCH, the a-CSI reporting being according to the a-CSI configuration.

73. The user equipment of claim 72, wherein a bit width of the CSI request field of an a-CSI reporting type for a-CSI reporting on a physical uplink control channel, PUCCH, is configurable by an RRC parameter.

74. The user equipment of claim 59, wherein the a-CSI configuration comprises an a-CSI triggered status list field for an a-CSI reporting type for a-CSI reporting on a physical uplink control channel, PUCCH, and an a-CSI triggered status list field for an a-CSI reporting type for a-CSI reporting on a physical uplink shared channel, PUSCH, the a-CSI reporting being according to the a-CSI configuration.

75. The user equipment of claim 59, wherein the processor further performs: receiving the A-CSI configuration in a DL scheduling DCI, wherein the A-CSI configuration in the DL scheduling DCI is shared by an A-CSI reporting type for A-CSI reporting on a physical uplink control channel PUCCH and an A-CSI reporting type for A-CSI reporting on a physical uplink shared channel PUSCH;

76. The user equipment of claim 59, wherein the a-CSI configuration comprises an a-CSI reporting type indication indicating one of an a-CSI reporting type for a-CSI reporting on a physical uplink control channel, PUCCH, or an a-CSI reporting type for a-CSI reporting on a physical uplink shared channel, PUSCH, as the determined a-CSI reporting type; and the A-CSI reporting is carried out according to the A-CSI configuration and the determined A-CSI reporting type.

77. The user equipment of claim 76, wherein the a-CSI reporting type indication is configurable through DCI signaling or radio resource control (radio resource control, RRC) signaling.

78. The user equipment of claim 76, wherein the a-CSI reporting type indication is represented by one of a plurality of DCI formats, a first one of the plurality of DCI formats representing an a-CSI reporting type that activates a-CSI reporting on a physical uplink control channel, PUCCH, as the determined a-CSI reporting type, and a second one of the plurality of DCI formats representing an a-CSI reporting type that activates a-CSI reporting on a physical uplink shared channel, PUSCH, as the determined a-CSI reporting type.

79. The user equipment of claim 76, wherein the a-CSI reporting type indication is represented by a radio network temporary identifier, RNTI, and wherein a CSI request in DCI indicates a trigger state of an a-CSI reporting type that activates a-CSI reporting on a physical uplink control channel, PUCCH, when scrambled with the RNTI, and wherein the CSI request in DCI indicates a trigger state of an a-CSI reporting type that activates a-CSI reporting on a physical uplink shared channel, PUSCH, when not scrambled with the RNTI.

80. The user equipment of claim 76, wherein the a-CSI reporting type indication is configurable by a media access control (medium access control, MAC) Control Element (CE).

81. The user equipment of claim 76, wherein the medium access control, MAC, control element, CE, comprises a status indication field, one code point in the status indication field indicating an entry of an activate or deactivate a-CSI configuration list.

82. The user equipment of claim 81, wherein the code point s in the field of the status indication _i Refers to an a-CSI configuration, which includes PUCCH resources for a-CSI reporting in an indicated bandwidth part (BWP), and has a j-th CSI reporting configuration identifier in the list, where a 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.

83. The user equipment of claim 76, wherein a medium access control, MAC, control element, CE, comprises a trigger state sub-selection field for sub-selection of the a-CSI configuration, and wherein a code point in the trigger state sub-selection field indicates whether an entry of a trigger state list is selected for a-CSI reporting.

84. The user equipment of claim 81, wherein the trigger state sub-selection field comprises a code point T _i Indicating that the j-th trigger state in the trigger state list is selected in the a-CSI reporting sub-selection, where j=i+1.

85. The user equipment of claim 59, wherein the processor further performs:

86. The user equipment of claim 59, wherein the processor further performs:

87. The user equipment of claim 59, wherein the processor further performs:

88. The user equipment of claim 59, wherein the a-CSI configuration comprises different sets of a-CSI configurations configured separately for different DCI formats.

89. The user equipment of claim 59, wherein an a-CSI reporting type for a-CSI reporting on a physical uplink control channel, PUCCH, is enabled for a URLLC service type.

90. A base station, comprising:

determining aperiodic channel state information (aperiodic channel state information, a-CSI) configuration including an a-CSI reporting type;

91. The base station of claim 90, wherein the processor further performs:

downlink (DL) scheduling Downlink Control Information (DCI) of a DCI format including a CSI request field whose bit width is configurable by radio resource control (radio resource control, RRC) parameters is transmitted.

92. The base station of claim 90, wherein the processor further performs:

93. The base station of claim 90, wherein the processor further performs:

94. The base station of claim 90, wherein the processor further performs:

95. The base station of claim 90, wherein the processor further performs:

96. The base station of claim 90, wherein the processor further performs:

97. The base station of claim 90, wherein a parameter is configured for the DL scheduling DCI to represent an offset X between a time slot containing DL scheduling DCI triggering a set of aperiodic non-zero power NZP CSI Reference Signal (RS) resources and a time slot transmitting the set of aperiodic NZP CSI-RS resources; a kind of electronic device with high-pressure air-conditioning system

98. The base station of claim 90, wherein the processor further performs: an indication of an a-CSI triggering method is sent to activate the a-CSI triggering method, wherein the indication of the a-CSI triggering method is configurable 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.

99. The base station of claim 90, wherein the processor further performs:

100. The base station of claim 90, wherein the a-CSI configuration comprises an a-CSI reporting type CSI request field for a-CSI reporting on a physical uplink control channel, PUCCH, and an a-CSI reporting type CSI request field for a-CSI reporting on a physical uplink shared channel, PUSCH.

101. The base station of claim 49, wherein a bit width of the a-CSI report type CSI request for a-CSI reporting on a physical uplink control channel, PUCCH, is configurable by RRC parameters.

102. The base station of claim 90, wherein the a-CSI configuration comprises an a-CSI triggered status list field for an a-CSI reporting type for a-CSI reporting on a physical uplink control channel, PUCCH, and an a-CSI triggered status list field for an a-CSI reporting type for a-CSI reporting on a physical uplink shared channel, PUSCH.

103. The base station of claim 90, wherein the a-CSI configuration in the DL scheduling DCI is shared by an a-CSI reporting type that performs a-CSI reporting on a physical uplink control channel, PUCCH, and an a-CSI reporting type that performs a-CSI reporting on a physical uplink shared channel, PUSCH;

104. The base station of claim 90, wherein the a-CSI configuration includes an a-CSI report type indication indicating one of an a-CSI report type for a-CSI reporting on a physical uplink control channel, PUCCH, or an a-CSI report type for a-CSI reporting on a physical uplink shared channel, PUSCH, as the determined a-CSI report type.

105. The base station of claim 104, wherein the a-CSI reporting type indication is configurable through DCI signaling or radio resource control (radio resource control, RRC) signaling.

106. The base station of claim 104, wherein the a-CSI reporting type indication is represented by one of a plurality of DCI formats, a first one of the plurality of DCI formats representing an a-CSI reporting type that activates a-CSI reporting on a physical uplink control channel, PUCCH, as the determined a-CSI reporting type, and a second one of the plurality of DCI formats representing an a-CSI reporting type that activates a-CSI reporting on a physical uplink shared channel, PUSCH, as the determined a-CSI reporting type.

107. The base station of claim 104, wherein the indication of the a-CSI reporting type is represented by a radio network temporary identifier, RNTI, and wherein a CSI request in DCI indicates a trigger state of an a-CSI reporting type that activates a-CSI reporting on a physical uplink control channel, PUCCH, when scrambled with the RNTI, and wherein the CSI request in DCI indicates a trigger state of an a-CSI reporting type that activates a-CSI reporting on a physical uplink shared channel, PUSCH, when not scrambled with the RNTI.

108. The base station of claim 104, wherein the a-CSI report type indication is configurable by a media access control (medium access control, MAC) Control Element (CE).

109. The base station of claim 104, wherein the medium access control, MAC, control element, CE, comprises a status indication field, one code point in the status indication field indicating an entry of an activate or deactivate a-CSI configuration list.

110. The a-CSI feedback method according to claim 109, wherein code point s in said field of said status indication _i Refers to an a-CSI configuration, which includes PUCCH resources for a-CSI reporting in an indicated bandwidth part (BWP), and has a j-th CSI reporting configuration identifier in the list, where a 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.

111. The base station of claim 104, wherein a medium access control, MAC, control element, CE, comprises a trigger state sub-selection field for sub-selection of the a-CSI configuration, and wherein a code point in the trigger state sub-selection field indicates whether an entry of a trigger state list is selected for a-CSI reporting.

112. The base station of claim 58, wherein the trigger state sub-selection field includes a code point T _i Indicating that the j-th trigger state in the trigger state list is selected in the a-CSI reporting sub-selection, where j=i+1.

113. The base station of claim 90, wherein the processor further performs:

114. The base station of claim 90, wherein the processor further performs: a first portion of a-CSI having a higher importance for MCS determination is received on PUCCH and a second portion of the a-CSI having a lower importance for MCS determination is received on PUSCH.

115. The base station of claim 90, wherein the processor further performs:

And detecting the A-CSI on the A-CSI reporting channel.

116. The base station of claim 90, wherein the a-CSI configurations comprise different sets of a-CSI configurations configured separately for different DCI formats.

117. The base station of claim 90 wherein an a-CSI reporting type for a physical uplink control channel, PUCCH, reporting a-CSI is enabled for a URLLC service type.

118. A chip, comprising:

a processor for invoking and running a computer program stored in memory to cause a device on which the chip is mounted to perform the method of any of claims 1 to 30.

119. A chip, comprising:

a processor for invoking and running a computer program stored in memory to cause a device on which the chip is mounted to perform the method of any of claims 31 to 58.

120. A computer readable storage medium having stored therein a computer program, wherein the computer program causes a computer to perform the method of any one of claims 1 to 30.

121. A computer readable storage medium having stored therein a computer program, wherein the computer program causes a computer to perform the method of any one of claims 31 to 58.

122. A computer program product comprising a computer program, wherein the computer program causes a computer to perform the method of any one of claims 1 to 30.

123. A computer program product comprising a computer program, wherein the computer program causes a computer to perform any of the methods of claims 31 to 58.

124. A computer program, wherein the computer program causes a computer to perform the method of any of claims 1 to 35.

125. A computer program, wherein the computer program causes a computer to perform the method of any of claims 31 to 58.