EP4728659A1

EP4728659A1 - User-equipment data collection for machine learning-based channel state information compression and prediction

Info

Publication number: EP4728659A1
Application number: EP23755011.6A
Authority: EP
Inventors: Yushu Zhang
Original assignee: Google LLC
Current assignee: Google LLC
Priority date: 2023-07-13
Filing date: 2023-07-13
Publication date: 2026-04-22
Also published as: CN121511562A; WO2025010731A1

Abstract

This disclosure provides systems, devices, apparatus, and methods, including computer programs encoded on storage media, for UE data collection for machine learning based CSI compression and prediction. A UE receives (604, 704), from a network entity (104), a configuration for a CSI resource, the CSI resource being configured for collection of data associated with at least one of CSI compression or CSI prediction. The UE receives (610), from the network entity (104), a CSI-RS on the CSI resource. The UE generates (613) the data based on the CSI-RS.

Description

USER-EQUIPMENT DATA COLLECTION FOR MACHINE LEARNING-BASED CHANNEL STATE INFORMATION COMPRESSION AND PREDICTION

TECHNICAL FIELD

The present disclosure relates generally to wireless communication, and more particularly, to user equipment (UE) data collection for machine learning (ML) -based channel state information (CSI) compression and prediction.

BACKGROUND

The Third Generation Partnership Project (3GPP) specifies a radio interface referred to as fifth generation (5G) new radio (NR) (5G NR) . An architecture for a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN) , a user equipment (UE) , etc. The 5G NR architecture seeks to provide increased data rates, decreased latency, and/or increased capacity compared to prior generation cellular communication systems.
Wireless communication systems, in general, provide various telecommunication services (e.g., telephony, video, data, messaging, broadcasts, etc. ) based on multiple-access technologies, such as orthogonal frequency division multiple access (OFDMA) technologies, that support communication with multiple UEs. Improvements in mobile broadband continue the progression of such wireless communication technologies. For example, the accuracy of a channel state information (CSI) report is associated with the data collection process, which can affect the quality of the training data used for the machine learning (ML) system. The accuracy of the CSI report depends on several factors including a control signaling mechanism and CSI report content. Furthermore, UE complexity-related aspects including CSI processing unit (CPU) occupancy rules and a minimum processing delay for the CSI report may affect the accuracy of the CSI report.
BRIEF SUMMARY
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
To reduce the size of a channel state information (CSI) report, a user equipment (UE) can compress a channel estimate array using a machine learning (ML) model and feed the compressed estimate back to a network entity. The network entity then decompresses, using another ML model, the channel estimate array and uses the decompressed estimate to determine downlink transmission parameters. This compression and decompression using the ML system eliminates the need for a quantized codebook and can improve overall system performance. The performance of the ML system depends on the performance of an ML model trained by the training data collected during a data collection process. Additionally, the performance may depend on the data collected for refining the ML model as well as for monitoring the ML model.
The accuracy of a CSI report is associated with the data collection process, which can affect the quality of the training data used for the ML system. The accuracy of the CSI report depends on several factors including a control signaling mechanism between the UE and the network entity. In particular, the network entity has no information on a UE preferred configuration for channel state information-reference signal (CSI-RS) measurement instances associated with the data collection. Furthermore, the lack of understanding between the network entity and UE regarding the transmission properties for the CSI-RS associated with the data collection may affect the accuracy of the CSI report.
Aspects of the present disclosure address the above-noted and other deficiencies by implementing a configuration procedure for the UE to communicate with the network entity. In one example, the UE may transmit, to the network entity, a UE preferred configuration that indicates a set of parameters including a minimum number of the CSI-RS measurement instances and a UE-preferred time offset between two CSI-RSs for the data collection. In another example, the UE receives, from the network entity, the CSI report configuration, which configures at least one transmission properties parameters. The configuration procedure may provide improved accuracy for the CSI report to the network entity.
According to some aspects, the UE receives, from the network entity, a configuration for a CSI resource. The CSI resource is for collection of data associated with at least one of CSI compression or CSI prediction. The UE receives, from the network entity, a CSI-RS on the CSI resource configured for the collection of the data, the data being stored at the UE.
According to some aspects, the network entity transmits, to the UE, a configuration for a CSI resource. The CSI resource is associated with collection of data for at least one of CSI compression or CSI prediction. The network entity transmits, to the UE, a CSI-RS on the CSI resource. The network entity receives, from the UE, a CSI report including the at least one of the CSI compression or the CSI prediction associated with the collection of the data.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a diagram of a wireless communications system that includes a plurality of user equipments (UEs) and network entities in communication over one or more cells according to an embodiment.
FIG. 2 is a channel state information (CSI) compression technique according to an embodiment.
FIG. 3 illustrates an example of a CSI prediction technique according to an embodiment.
FIG. 4 illustrates an example for the configuration mismatch for channel state information-reference signal (CSI-RS) for data collection according to an embodiment.
FIG. 5 illustrates an example for the CSI-RS configuration specific machine learning (ML) models according to an embodiment.
FIG. 6 is a signaling diagram illustrating communications between a UE and a network entity for performing report content configuration and report procedure according to an embodiment.
FIG. 7 is a signaling diagram illustrating communications between a UE and a network entity for performing report content configuration and report procedure according to an embodiment.
FIG. 8 illustrates an example for the UE request CSI-RS for data collection according to an embodiment.
FIG. 9 illustrates an example for the data collection procedure based on the network configuration according to an embodiment.
FIG. 10 illustrates an example for the UE report timing for data collection according to an embodiment.
FIG. 11 illustrates an example for the CSI processing unit (CPU) occupancy time for CSI-RS for data collection according to an embodiment.
FIG. 12 is a flowchart of a method of wireless communication at a UE according to an embodiment.
FIG. 13 is a flowchart of a method of wireless communication at a network entity according to an embodiment.
FIG. 14 is a diagram illustrating a hardware implementation for an example UE apparatus according to some embodiments.
FIG. 15 is a diagram illustrating a hardware implementation for one or more example network entities according to some embodiments.

DETAILED DESCRIPTION

FIG. 1 illustrates a diagram 100 of a wireless communications system associated with a plurality of cells 190. The wireless communications system includes user equipments (UEs) 102 and base stations/network entities 104. Some base stations may include an aggregated base station architecture and other base stations may include a disaggregated base station architecture. The aggregated base station architecture utilizes a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node. A disaggregated base station architecture utilizes a protocol stack that is physically or logically distributed among two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110) . For example, a CU 110 is implemented within a RAN node, and one or more DUs 108 may be co-located with the CU 110, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs 108 may be implemented to communicate with one or more Rus 106. Any of the RU 106, the DU 108 and the CU 110 can be implemented as virtual units, such as a virtual radio unit (VRU) , a virtual distributed unit (VDU) , or a virtual central unit (VCU) . The base station/network entity 104 (e.g., an aggregated base station or disaggregated units of the base station, such as the RU 106 or the DU 108) , may be referred to as a transmission reception point (TRP) .
Operations of the base station 104 and/or network designs may be based on aggregation characteristics of base station functionality. For example, disaggregated base station architectures are utilized in an integrated access backhaul (IAB) network, an open-radio access network (O-RAN) network, or a virtualized radio access network (vRAN) , which may also be referred to a cloud radio access network (C-RAN) . Disaggregation may include distributing functionality across the two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network designs. The various units of the disaggregated base station architecture, or the disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit. For example, the base stations 104d, 104e and/or the Rus 106a, 106b, 106c, 106d may communicate with the UEs 102a, 102b, 102c, 102d, and/or 102s via one or more radio frequency (RF) access links based on a Uu interface. In examples, multiple Rus 106 and/or base stations 104 may simultaneously serve the UEs 102, such as by intra-cell and/or inter-cell access links between the UEs 102 and the Rus 106/base stations 104.
The RU 106, the DU 108, and the CU 110 may include (or may be coupled to) one or more interfaces configured to transmit or receive information/signals via a wired or wireless transmission medium. For example, a wired interface can be configured to transmit or receive the information/signals over a wired transmission medium, such as via the fronthaul link 160 between the RU 106d and the baseband unit (BBU) 112 of the base station 104d associated with the cell 190d. The BBU 112 includes a DU 108 and a CU 110, which may also have a wired interface (e.g., midhaul link) configured between the DU 108 and the CU 110 to transmit or receive the information/signals between the DU 108 and the CU 110. In further examples, a wireless interface, which may include a receiver, a transmitter, or a transceiver, such as an RF transceiver, configured to transmit and/or receive the information/signals via the wireless transmission medium, such as for information communicated between the RU 106a of the cell 190a and the base station 104e of the cell 190e via cross-cell communication beams 136-138 of the RU 106a and the base station 104e.
The Rus 106 may be configured to implement lower layer functionality. For example, the RU 106 is controlled by the DU 108 and may correspond to a logical node that hosts RF processing functions, or lower layer PHY functionality, such as execution of fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, etc. The functionality of the RU 106 may be based on the functional split, such as a functional split of lower layers.
The Rus 106 may transmit or receive over-the-air (OTA) communication with one or more UEs 102. For example, the RU 106b of the cell 190b communicates with the UE 102b of the cell 190b via a first set of communication beams 132 of the RU 106b and a second set of communication beams 134b of the UE 102b, which may correspond to inter-cell communication beams or, in some examples, cross-cell communication beams. For instance, the UE 102b of the cell 190b may communicate with the RU 106a of the cell 190a via a third set of communication beams 134a of the UE 102b and a fourth set of communication beams 136 of the RU 106a. DUs 108 can control both real-time and non-real-time features of control plane and user plane communications of the Rus 106.
Any combination of the RU 106, the DU 108, and the CU 110, or reference thereto individually, may correspond to a base station 104. Thus, the base station 104 may include at least one of the RU 106, the DU 108, or the CU 110. The base stations 104 provide the UEs 102 with access to a core network. The base stations 104 may relay communications between the UEs 102 and the core network (not shown) . The base stations 104 may be associated with macrocells for higher-power cellular base stations and/or small cells for lower-power cellular base stations. For example, the cell 190e may correspond to a macrocell, whereas the cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network that includes at least one macrocell and at least one small cell may be referred to as a “heterogeneous network. ”
Transmissions from a UE 102 to a base station 104/RU 106 are referred to as uplink (UL) transmissions, whereas transmissions from the base station 104/RU 106 to the UE 102 are referred to as downlink (DL) transmissions. Uplink transmissions may also be referred to as reverse link transmissions and downlink transmissions may also be referred to as forward link transmissions. For example, the RU 106d utilizes antennas of the base station 104d of cell 190d to transmit a downlink/forward link communication to the UE 102d or receive an uplink/reverse link communication from the UE 102d based on the Uu interface associated with the access link between the UE 102d and the base station 104d/RU 106d.
Communication links between the UEs 102 and the base stations 104/Rus 106 may be based on multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be associated with one or more carriers. The UEs 102 and the base stations 104/Rus 106 may utilize a spectrum bandwidth of Y MHz (e.g., 5, 10, 15, 20, 100, 400, 800, 1600, 2000, etc. MHz) per carrier allocated in a carrier aggregation of up to a total of Yx MHz, where x component carriers (CCs) are used for communication in each of the uplink and downlink directions. The carriers may or may not be adjacent to each other along a frequency spectrum. In examples, uplink and downlink carriers may be allocated in an asymmetric manner, with more or fewer carriers allocated to either the uplink or the downlink. A primary component carrier and one or more secondary component carriers may be included in the component carriers. The primary component carrier may be associated with a primary cell (Pcell) and a secondary component carrier may be associated with a secondary cell (Scell) .
Some UEs 102, such as the UEs 102a and 102s, may perform device-to-device (D2D) communications over sidelink. For example, a sidelink communication/D2D link utilizes a spectrum for a wireless wide area network (WWAN) associated with uplink and downlink communications. Such sidelink/D2D communication may be performed through various wireless communications systems, such as wireless fidelity (Wi-Fi) systems, Bluetooth systems, Long Term Evolution (LTE) systems, New Radio (NR) systems, etc.
The UEs 102 and the base stations 104/Rus 106 may each include a plurality of antennas. The plurality of antennas may correspond to antenna elements, antenna panels, and/or antenna arrays that may facilitate beamforming operations. For example, the RU 106b transmits a downlink beamformed signal based on a first set of communication beams 132 to the UE 102b in one or more transmit directions of the RU 106b. The UE 102b may receive the downlink beamformed signal based on a second set of communication beams 134b from the RU 106b in one or more receive directions of the UE 102b. In a further example, the UE 102b may also transmit an uplink beamformed signal (e.g., sounding reference signal (SRS) ) to the RU 106b based on the second set of communication beams 134b in one or more transmit directions of the UE 102b. The RU 106b may receive the uplink beamformed signal from the UE 102b in one or more receive directions of the RU 106b. The UE 102b may perform beam training to determine the best receive and transmit directions for the beamformed signals. The transmit and receive directions for the UEs 102 and the base stations 104/Rus 106 may or may not be the same.
In further examples, beamformed signals may be communicated between a first base station/RU 106a and a second base station 104e. For instance, the base station 104e of the cell 190e may transmit a beamformed signal to the RU 106a based on the communication beams 138 in one or more transmit directions of the base station 104e. The RU 106a may receive the beamformed signal from the base station 104e of the cell 190e based on the RU communication beams 136 in one or more receive directions of the RU 106a. In further examples, the base station 104e transmits a downlink beamformed signal to the UE 102e based on the communication beams 138 in one or more transmit directions of the base station 104e. The UE 102e receives the downlink beamformed signal from the base station 104e based on UE communication beams 130 in one or more receive directions of the UE 102e. The UE 102e may also transmit an uplink beamformed signal to the base station 104e based on the UE communication beams 130 in one or more transmit directions of the UE 102e, such that the base station 104e may receive the uplink beamformed signal from the UE 102e in one or more receive directions of the base station 104e.
The base station 104 may include and/or be referred to as a network entity. That is, “network entity” may refer to the base station 104 or at least one unit of the base station 104, such as the RU 106, the DU 108, and/or the CU 110. The base station 104 may also include and/or be referred to as a next generation evolved Node B (ng-eNB) , a next generation NB (gNB) , an evolved NB (eNB) , an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a TRP, a network node, network equipment, or other related terminology. The base station 104 or an entity at the base station 104 can be implemented as an IAB node, a relay node, a sidelink node, an aggregated (monolithic) base station, or a disaggregated base station including one or more RUs 106, DUs 108, and/or CUs 110. A set of aggregated or disaggregated base stations may be referred to as a next generation-radio access network (NG-RAN) . In some examples, the UE 102a operates in dual connectivity (DC) with the base station 104e and the base station/RU 106a. In such cases, the base station 104e can be a master node and the base station/RU 160a can be a secondary node.
Still referring to FIG. 1, in certain aspects, any of the UEs 102 may include a report component 140 configured to receive, from a network entity 104, a configuration for a channel state information (CSI) resource, the CSI resource being configured for collection of data associated with at least one of CSI compression or CSI prediction; receive, from the network entity 104, a channel state information-reference signal (CSI-RS) on the CSI resource; and generate the data based on the CSI-RS.
In certain aspects, any of the base stations 104 or a network entity of the base stations 104 may include a configuration component 150 configured to transmit, to a UE 102, a configuration for a CSI resource, the CSI resource being associated with collection of data for at least one of CSI compression or CSI prediction; transmit, to the UE 102, a CSI-RS on the CSI resource; and receive, from the UE 102, a CSI report based on the at least one of the CSI compression or the CSI prediction.
Accordingly, FIG. 1 describes a wireless communication system that may be implemented in connection with aspects of one or more other figures described herein. Further, although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as 5G-Advanced and future versions, LTE, LTE-advanced (LTE-A) , and other wireless technologies, such as 6G.
FIG. 2 illustrates a diagram 200 of a CSI compression technique based on a machine learning (ML) model for CSI compression. For the CSI compression, the UE 102 measures the CSI based on a CSI-RS, and the UE 102 can compress the CSI with the ML model 216 for the CSI compression. Then, the UE 102 transmits the compressed CSI 218 to the network entity 104. The network entity 104 uses another ML model 220 to reconstruct the CSI 222 based on the received compressed CSI 218. Referring to FIG. 2, C_x, y, z 214 indicates a coefficient for the measured CSI for a subband x, CSI-RS antenna port y, and layer or UE antenna port z. D_x 218 indicates the xth coefficients for the compressed CSI, and C’_x, y, z 222 indicates the coefficient for the recovered CSI for subband x, CSI-RS antenna port y, and layer or UE antenna port z.
FIG. 3 illustrates an example 300 of CSI prediction technique based on the ML CSI prediction model. The UE 102 can predict the CSI in future slot (s) based on the received CSI measurement. The UE 102 can transmit, to the network entity 104, the predicted CSIs. Referring to FIG. 3, the UE 102 may perform CSI measurements at slot (s) 324A-324C and the CSI measurements/reports are the inputs to the ML based CSI prediction model 326 to predict the CSIs (e.g., 328A-328B) in future slot (s) . The UE 102 transmits, to the network entity 104, the predicted CSIs (e.g., 328A-328B) . The network entity 102 may schedule downlink transmissions based on the predicted CSIs (e.g., 328A-328B) . Thus, FIG. 4 illustrates a signaling diagram of an example scenario in which UE 102 and network entity 104 exchanges messages and implement procedures for performing report content configuration and report procedure.
FIG. 4 illustrates an example 400 of a UE and network entity configuration mismatch for CSI-RS for data collection according to an embodiment. The network entity 104 has no information on the UE-preferred configuration for the CSI-RS instances for the data collection. The UE-preferred configuration may indicate the minimum number of CSI-RS instances and the UE-preferred time offset between every two CSI-RS instances for the data collection. Referring to FIG. 4, the network entity 104 may transmit the CSI-RS for the data collection based on a different configuration from what the UE 102 prefers. For example, the UE-preferred configuration for the CSI-RS instances may include 4 CSI-RS instances (e.g., 440A-440D) with X1 time symbols offset 442A. The network entity 104 may transmit a different configuration than the UE-preferred configuration for the CSI-RS instances. In this example, the network entity 104 transmits 3 CSI-RS (e.g., 440A-440C) instances with X2 time symbols offset 442B.
FIG. 5 illustrates an example 500 for the CSI-RS configuration specific ML model according to an embodiment. The network entity 104 may apply an antenna virtualization to transmit the CSI-RS. For example, the network entity 104 may apply an analog beamforming to transmit the CSI-RS. The network entity 104 may transmit the CSI-RS from different antenna port configurations, for example, different number of horizontal and vertical antenna ports. Referring to FIG. 5, the UE 102 may apply different ML models for different CSI-RS configurations. For example, antenna port configuration 502 may have number of horizontal antenna ports N1 = 4 and number of vertical antenna ports N2 = 4; antenna port configuration 504 may have number of horizontal antenna ports N1 = 8 and number of vertical antenna ports N2 = 4. For both antenna port configuration 502 and 504, CSI-RS may be transmitted from 32 antenna ports with two polarizations. It is noted that the antenna port configurations of FIG. 5 are mere examples, and that other antenna port configurations with a different number of horizontal and vertical antenna ports as well as polarizations may be implemented for CSI-RS transmission.
FIG. 6 illustrates a signaling diagram 600 of an example scenario in which UE 102 and network entity 104 exchanges messages and implement procedures for performing report content configuration and report procedure, according to some embodiments. The network entity 104 may correspond to the base station or an entity at the base station, such as the RU 106, the DU 108, the CU 110, etc.
In some examples, initially, the UE 102 may transmit 602, to the network entity 104, (and the network entity 104 may receive 602 from the UE 102) a UE capability on supported or preferred configurations for the CSI-RS for data collection. The UE preferred configuration may include at least one of: a supported or preferred number of CSI-RS instances; a minimum number of the CSI-RS instances; preferred offset between two consecutive CSI-RS instances; a maximum offset between two consecutive CSI-RS instances; a minimum offset between two consecutive CSI-RS instances; a supported or preferred periodicity for the CSI-RS; a maximum periodicity for the CSI-RS; a minimum periodicity for the CSI-RS; a supported or preferred bandwidth; a minimum bandwidth for the CSI-RS; or a supported or preferred time-domain behavior for the CSI-RS.
The UE 102 receives 604, from a network entity 104, (and the network entity 104 transmits 604 to the UE 102) a control signaling configuring at least a CSI report configuration including at least one CSI-RS resource for CSI acquisition, and optionally configuring timing information or report of the timing information for data collection based on the configured CSI-RS. Based on the UE capability 602, the network entity 104 may configure at least one CSI-RS resource for data collection by Radio Resource Control (RRC) signaling, such as, RRCReconfiguration. The network entity 104 may further configure the parameters for the transmission properties for the CSI-RS, such as, number of horizontal ports, number of vertical ports, and antenna virtualization weights. In some implementations, the network entity 104 may transmit the CSI-RS for data collection periodically. In some other implementations, the network entity 104 may transmit the CSI-RS for data collection in a semi-persistent or aperiodic manner. The network entity 104 may further configure the parameters for the UE request CSI-RS for data collection.
The UE 102 may transmit 606, to the network entity 104, (and the network entity 104 may receive 606 from the UE 102) a UE request of the CSI-RS for data collection.
The UE 102 may receive 608, from the network entity 104, (and the network entity 104 may transmit 608 to the UE 102) MAC CE or DCI triggering the configured at least one CSI-RS resource for data collection and optionally indicating the transmission property for the CSI-RS.
The UE 102 receives 610, from the network entity 104, (and the network entity 104 transmits 610 to the UE 102) at least one CSI-RS resource for data collection. Then, the UE 102 can perform data collection based on the measurement of the triggered CSI-RS resource (s) .
The UE 102 generates 613 the data based on the at least CSI-RS resource for data collection. In some aspects, the data may include input data of a machine learning model. In some other aspects, the data may include output data of a machine learning model. In other aspects, the data may be used for machine learning model training, machine learning model refinement, machine learning model monitoring, etc. In some aspects, the data collection may be used for a machine learning based CSI compression and/or a machine learning based CSI prediction.
The UE 102 may transmit 614, to the network entity 104, (and the network entity 104 may receive from the UE 102) a CSI report for the configured or triggered at least one CSI-RS resource. In some aspects, the CSI report may include CSI compression based on the machine learning model. In some other aspects, the CSI report may include CSI prediction based on the machine learning model.
FIG. 7 illustrates a signaling diagram 700 of an example scenario in which UE 102 and network entity 104 exchanges messages and implement procedures for performing report content configuration and report procedure, according to some embodiments. The network entity 104 may correspond to the base station or an entity at the base station, such as the RU 106, the DU 108, the CU 110, etc. The procedures 602, 613 of FIG. 7 are similar to procedures 602, 613 of FIG. 6.
The UE 102 receives 704, from the network entity (and the network entity 104 transmits 704 to the UE 102) a control signaling configuring at least a CSI-RS resource for data collection, and optionally configuring the transmission property for the CSI-RS and/or parameters for the UE 102 to request the CSI-RS for data collection.
The UE 102 may transmit 706, to the network entity 104, (and the network entity may receive 706 from the UE 102) a UE report of the timing information on the data collection based on the configured CSI-RS.
The UE 102 may receive 708, from the network entity 104, (and the network entity 104 may transmit 708 to the UE 102) a MAC CE or DCI triggering the configured CSI report based on the configured at least one CSI report configuration and/or the configured at least one CSI-RS resource.
The UE 102 determines 710 the CSI measurement and report scheme based on the occupied CPUs and processing delay for CSI report and data collection.
The UE 102 may receive 712, from the network entity 104, (and the network entity 104 may transmit 712 to the UE 102) the at least one CSI-RS resource.
The UE 102 may transmit 714, to the network entity 104, (and the network entity 104 may receive 714 from the UE 102) a CSI report for the configured or triggered CSI report configuration.
In this disclosure, unless specified, a RRC signaling may indicate a RRC reconfiguration message from the network entity to UE, or a system information block (SIB) , where the SIB can be an existing SIB (e.g., SIB1) or a new SIB (e.g., SIB J, where J is an integer above 21) transmitted by the network entity. In some implementations, the network entity receives the UE capability from a core network (e.g., Access and Mobility Management Function (AMF) ) . In yet some other implementations, the network entity receives the UE capability from another network entity (e.g., gNB or eNB) .
In an embodiment, the UE 102 reports the preferred configuration for the CSI-RS for the data collection, including at least one of the following parameters: supported or preferred number of CSI-RS instances for the data collection; a minimum number of CSI-RS instances for the data collection; preferred offset (s) between two consecutive instances for the CSI-RS for the data collection; a maximum offset between two consecutive instances for the CSI-RS for the data collection; a minimum offset between two consecutive instances for the CSI-RS for the data collection; a supported or preferred periodicity for the CSI-RS for the data collection; a maximum periodicity for the CSI-RS for the data collection; a minimum periodicity for the CSI-RS for the data collection; supported or preferred bandwidth (s) for the CSI-RS for the data collection; a minimum bandwidth for the CSI-RS for the data collection; or a supported or preferred time-domain behavior (e.g., periodic, semi-persistent, or aperiodic) for the CSI-RS for the data collection.
In some implementations, the UE 102 transmits the UE preferred configuration by UE capability report. In some other implementations, the UE 102 transmits the UE preferred configuration by a dedicated RRC message for data collection. In some other implementations, the UE 102 transmits the UE preferred configuration by new parameters in the existing RRC message, e.g., UEAssistantInformation. In some other implementations, the UE 102 may transmit some of the parameters for UE preferred configuration, for example, preferred number of CSI-RS instances and preferred offset between two CSI-RS instances for data collection, by MAC CE.
In an embodiment, the network entity 104 configures the transmission properties for the CSI-RS for data collection, including at least one of the following parameters: number of horizontal antenna ports; number of vertical antenna ports; an antenna virtualization weight; an associated physical cell identifier (PCI) ; or an antenna radiation pattern.
In some implementations, the network entity 104 configures the antenna virtualization weight for the CSI-RS for data collection explicitly. In some other implementations, the network entity 104 configures the antenna virtualization weight for the CSI-RS for data collection by indicating the antenna quasi-co-location (QCL) source reference signal, e.g., a synchronization signal block (SSB) .
In some implementations, the network entity 104 configures the antenna radiation pattern explicitly. In some other implementations, the network entity 104 configures the antenna radiation pattern type based on the pre-defined or pre-configured list of antenna radiation patterns. In one example, the network entity 104 configures whether the CSI-RS for data collection is based on omni-directional antenna or directional antenna. For directional antenna, the network entity 104 may further configure the at least one of the parameters: vertical cut of the radiation power pattern, horizontal cut of the radiation power pattern, 3-dimension (3D) radiation power pattern, or maximum directional gain of an antenna element.
In some implementations, the network entity 104 configures some of or all the transmission properties by RRC signaling. In some other implementations, the network entity 104 configures some of or all the transmission properties by MAC CE or DCI triggering the CSI-RS.
In some implementations, the network entity 104 may configure an RRC parameter for the CSI-RS resource indicating the CSI-RS is for the data collection.
In some implementations, the CSI-RS for data collection is a CSI-RS for CSI acquisition, for example, the CSI-RS is configured in a CSI-RS resource set without TRS-Info configured and without repetition configured.
FIG. 8 illustrates an example 800 of the UE request for the CSI-RS for the data collection. Referring to FIG. 8, the UE 102 transmits a scheduling request (SR) 852 for requesting CSI-RS for the data collection. The network entity 104 may transmit an uplink grant 854 in response to the SR 852. The UE 102 may transmit a request 856 for the CSI-RS for the data collection using the uplink grant 854. The UE 102 may receive a response 858 to the request 856 for the CSI-RS for the data collection. Then, the UE 102 may receive CSI-RS instances (e.g., 840A, 840B, ... 840C) for the data collection.
In an embodiment, the network entity 104 may configure at least one of the parameters for UE-request CSI-RS for the data collection procedure: an uplink resource for the UE request; a maximum number of retransmissions of the request; a duration of the monitoring window for the response to the request; a duration of the prohibit timer for the request; a downlink resource for the response to the request; or a list of candidate CSI-RS resource (s) for the UE to request. In some implementations, some of the parameters for the UE-request CSI-RS for the data collection procedure above may be predefined.
In an embodiment, the UE 102 can transmit a request for CSI-RS for data collection if the prohibit timer expires. The UE 102 may restart or reset the prohibit timer if one of the following event occurs: the UE 102 receives a CSI-RS for the data collection or the MAC CE or DCI triggering the CSI-RS for data collection; the UE 102 switches to a different physical cell after a handover procedure or a low-layer triggered mobility procedure; the UE 102 activates a secondary cell (SCell) , where the SCell may correspond to a new frequency band or band combination; the UE 102 adds a primary secondary serving cell (PSCell) , where the PSCell may correspond to a new frequency band or band combination.
In some implementations, the UE 102 may transmit the request if the prohibit timer expires and the channel quality, for example, layer 1 reference signal received power (L1-RSRP) for a SSB or CSI-RS, layer 1 signal-to-interference plus noise ratio (L1-SINR) for a SSB or CSI-RS, layer 3 reference signal received power (L3-RSRP) , layer 3 signal-to-interference plus noise ratio (L3-SINR) , reference signal received quality (RSRQ) , is above a threshold. The threshold may be predefined or configured by the network entity 104 via RRC signaling, MAC CE, or DCI. In some implementations, the UE 102 may measure the L1-RSRP or L1-SINR from the SSB or CSI-RS indicated in one the of active Transmission Configuration Indication (TCI) state, for example, the first TCI state. In some other implementations, the UE 102 may measure the L1-RSRP or L1-SINR from the SSB or CSI-RS indicated in one TCI state configured or indicated by the network entity 104.
In an embodiment, in the request for the CSI-RS for the data collection, the UE 102 may transmit at least one of the following information: a serving cell index for the CSI-RS for the data collection; a bandwidth part index for the CSI-RS for the data collection; requested CSI-RS resource index (es) or CSI-RS resource set index (es) ; a subset of or all the parameters for the preferred configurations for the requested CSI-RS for the data collection; or a subset of or all the parameters in the transmission properties for the requested CSI-RS for the data collection.
In some implementations, the UE 102 may transmit the request by physical uplink control channel (PUCCH) . The network entity 104 may configure at least one PUCCH resource for the request for the CSI-RS for the data collection by RRC signaling. In some other implementations, the UE 102 may transmit the request by MAC CE. The UE 102 may transmit a scheduling request (SR) by PUCCH or PRACH if the UE 102 did not receive an uplink grant for the physical uplink shared channel (PUSCH) , where the SR may be configured by the network entity 104 via RRC signaling. In some other implementations, the UE 102 may transmit the request by RRC message. In some other implementations, the UE 102 may transmit the request by PRACH, where the UE 102 may be configured with different PRACH resources corresponding to different content of the request, for example, different PRACH resource corresponding to different CSI-RS resource for data collection.
In an embodiment, after X slots or symbols after the UE 102 transmits the first or last symbol of the request, the UE 102 starts to monitor the network entity’s response to the request, where X may be predefined, for example, X=0 or X=4, or configured by the network entity 104 via RRC signaling. The UE 102 starts or resets a monitoring timer after the UE 102 starts to monitor the response. If the UE 102 detects a response to the request, the UE 102 stops or resets the timer. After the timer expires, the UE 102 can retransmit the request if the number of retransmissions of the request is smaller than the maximum number of retransmissions of the request.
In some implementations, the network entity 104 transmits the response via a physical downlink control channel (PDCCH) . In one example, the network entity 104 transmits the response as a PDCCH in a dedicated search space or control resource set configured by the network entity 104. In another example, the network entity 104 transmits the response as a PDCCH scheduling the downlink reference signals for data collection. In another example, the network entity 104 transmits the response as a PDCCH associated with a radio network temporary identifier (RNTI) configured by the network entity 104 or predefined. In another example, the network entity 104 transmits the response as a PDCCH scheduling a new transmission for the same hybrid automatic repeat request (HARQ) process as the PUSCH with the MAC CE for data collection request.
In some other implementations, the network entity 104 transmits the response via MAC CE. In one example, the network entity 104 transmits the response as a MAC CE activating or triggering the CSI-RS for data collection. In another example, the network entity 104 transmits the response as a dedicated MAC CE for response to request of CSI-RS data collection.
FIG. 9 illustrates an example 900 for the data collection procedure based on the network configuration.
In an embodiment, the network entity 104 configures the timing for the data collection for the CSI-RS in a CSI report configuration by RRC signaling, MAC CE, or DCI, which includes at least one of the following parameters: periodicity for the data collection; timing for the first CSI-RS instance for the data collection, for example, frame, subframe, slot and/or symbol index; number of CSI-RS instances for each data collection period; or interval of CSI-RS instances for data collection for each data collection period, for example, number of CSI-RS periodicities for the CSI-RS instances for data collection for each data collection period.
Referring to FIG. 9, the periodicity for data collection 946 is 80 slots, the timing for the first CSI-RS instance for data collection is slot 1 (e.g., 944A or 944C) , the number of CSI-RS resources for each data collection period is 2 (e.g., 944A/944B; 944C/944D) and the interval of CSI-RS instances for data collection for each data collection period is 1.
In some implementations, for a periodic CSI-RS, the network entity 104 may provide some of or all the parameters above for data collection by RRC signaling. For a semi-persistent CSI-RS, the network entity 104 may provide some of or all the parameters above for data collection by MAC CE activating the CSI-RS. For aperiodic CSI-RS, the network entity 104 may provide some of or all the parameters above for data collection by the DCI triggering the CSI-RS. In one example, different triggering states indicated in DCI may correspond to different value of the parameters for data collection.
FIG. 10 illustrates an example 1000 for the UE report timing for data collection. In an embodiment, the UE 102 reports the timing for the data collection, including at least one of the following parameters: periodicity for data collection, starting time for the data collection, duration for each data collection, number of CSI-RS instance (s) for data collection, CSI-RS resource index (es) , CSI-RS resource set index (es) , and/or CSI-RS instance (es) for data collection. Referring to FIG. 10, the slot with the CSI-RS (e.g., 1044A, 1044B, 1044C) are for the data collection. The slot with the CSI report (e.g., 1048A, 1048B, 1048C) are for the data collection for the next CSI-RS instance.
In some implementations, the UE 102 transmits the report by a MAC CE. In some other implementations, the UE 102 transmits the report by uplink control information in PUCCH or PUSCH. In some other implementations, the UE 102 transmits the report by an RRC message.
In one example, the UE 102 transmits an indicator in an uplink control information (UCI) , for example, a CSI report, indicating whether the UE 102 will start data collection for the next CSI-RS instance for the same CSI report configuration or for a CSI report configuration indicated by the indicator in UCI, where one state of the indicator may indicate the UE 102 will not perform data collection for the next CSI-RS instance.
FIG. 11 illustrates an example 1100 for the CPU occupancy time for CSI-RS for the data collection. In an embodiment, for the CSI-RS instance for data collection (e.g., 1140A-1140C) , O₁ CPUs are occupied within S symbols (e.g., 1160) , which starts from the first symbol or last symbol of the CSI-RS instance or the MAC CE or DCI triggering the CSI-RS. The value of S may be predefined, for example, 42 symbols, or determined based on the number of antenna ports for the CSI-RS, or reported by the UE via UE capability report. In another example, the value of S may be determined based on the periodicity of the CSI-RS, e.g., S is the same as the periodicity of the CSI-RS for data collection. Thus, O₁ CPUs are always occupied starting from the first CSI-RS instance until the last CSI-RS instance. The value of O₁ may be predefined, for example, O₁=1, or reported by the UE 102 via UE capability report.
In some implementations, if the CSI-RS is configured for both CSI acquisition and data collection, the UE 102 determines additional O₂ CPUs are occupied within a set of symbols, which starts from the first symbol or last symbol of the CSI-RS instance or the MAC CE or DCI triggering the CSI-RS until the first or last symbol of the CSI report. The value of O₂ may be predefined, for example, O₂=1, or reported by the UE 102 via UE capability report.
In an embodiment, the network entity 104 may refrain from scheduling the CSI report (s) and CSI-RS for data collection that requires a greater number of CPUs than the maximum number of CPUs the UE 102 reports via UE capability. In some implementations, if the number of CPUs for the scheduled CSI report (s) exceeds the maximum number of CPUs the UE 102 supports, the UE 102 may refrain from transmitting the CSI report (s) with lower priority. The UE 102 determines the priority for the CSI report based on the time domain behavior for the report, report content, serving cell index and CSI report configuration identification (ID) . In some other implementations, if the number of CPUs for the scheduled CSI report (s) exceeds the maximum number of CPUs the UE 102 supports, the UE 102 may transmit the outdated CSI for the CSI report (s) with lower priority. In some other implementations, if the number of CPUs for the scheduled CSI report (s) exceeds the maximum number of CPUs the UE 102 supports, the UE may refrain from performing data collection.
In an embodiment, if a CSI-RS instance for the CSI report is also configured for data collection, the UE 102 may determine additional minimum processing delay for the CSI report should be applied, where the additional minimum processing delay may be predefined or reported by the UE 102 via UE capability report.
In one example, if a CSI-RS instance for the CSI report is also configured for data collection, the minimum processing delay for the CSI report is Z+r and Z’ +r, where Z and Z’ are the minimum processing delay for the CSI report when the CSI-RS is for CSI acquisition only, which are defined in 3GPP TS 38.214 section 5.4, and r indicates the additional processing delay for data collection, which may be predefined or reported by the UE capability.
In an embodiment, the network entity 104 may refrain from scheduling the CSI report (s) for CSI acquisition and data collection with smaller scheduling offset than the minimum processing delay. In some implementations, if the scheduling offset is smaller than the minimum processing delay, the UE 102 may refrain from transmitting the CSI report (s) . In some other implementations, if the scheduling offset is smaller than the minimum processing delay, the UE 102 may transmit the outdated CSI for the CSI report (s) . In some other implementations, if the scheduling offset is smaller than the minimum processing delay, the UE 102 may refrain from performing data collection.
FIGs. 12-13 show methods for implementing one or more aspects of FIGs. 6-11. In particular, FIG. 12 shows an implementation by the UE 102 of the one or more aspects of FIGs. 6-11. FIG. 13 shows an implementation by the network entity 104 of the one or more aspects of FIGs. 6-11.
FIG. 12 illustrates a flowchart 1200 of a method of wireless communication at a UE. With reference to FIGs. 1-11 and 14, the method may be performed by the UE 102, the UE apparatus 1402, etc., which may include the memory 1426′, 1406′, 1416, and which may correspond to the entire UE 102 or the entire UE apparatus 1402, or a component of the UE 102 or the UE apparatus 1402, such as the wireless baseband processor 1426 and/or the application processor 1406.
The UE 102 may transmit 1202, to the network entity 104, a UE capability report indicating at least one of: a capability of the UE 102 for CSI reporting based on the CSI-RS for data collection; or a UE preferred configuration for the CSI-RS configured for the collection of the data. In some aspects, the UE preferred configuration includes at least one of: a supported or preferred number of CSI-RS instances, a minimum number of the CSI-RS instances, preferred offset between two consecutive CSI-RS instances, a maximum offset between two consecutive CSI-RS instances, a minimum offset between two consecutive CSI-RS instances, a supported or preferred periodicity for the CSI-RS, a maximum periodicity for the CSI-RS, a minimum periodicity for the CSI-RS, a supported or preferred bandwidth, a minimum bandwidth for the CSI-RS, or a supported or preferred time-domain behavior for the CSI-RS. For example, referring to FIGs. 6-7, the UE 102 transmits 602, to the network entity 104, (and the network entity 104 may receive 602 from the UE 102) a UE capability on supported or preferred configurations for the CSI-RS for data collection.
The UE 102 receives 1204, from the network entity 104, a configuration for a channel state information (CSI) resource, the CSI resource being configured for collection of data associated with at least one of CSI compression or CSI prediction. For example, referring to FIG. 6, the UE 102 receives 604, from a network entity 104, (and the network entity 104 transmits 604 to the UE 102) a control signaling configuring at least a CSI report configuration including at least one CSI-RS resource for CSI acquisition, and optionally configuring timing information or report of the timing information for data collection based on the configured CSI-RS.
The UE 102 may transmit 1206, to the network entity 104, a request for the CSI-RS configured for the collection of the data. For example, referring to FIG. 6, The UE 102 may transmit 606, to the network entity 104, (and the network entity 104 may receive 606 from the UE 102) a UE request of the CSI-RS for data collection.
The UE 102 may receive 1208, from the network entity, a triggering indication that at least one of: triggers the CSI RS resource, triggers the CSI report, or indicates the transmission property for the CSI-RS. For example, referring to FIG. 6, the UE 102 may receive 608, from the network entity 104, (and the network entity 104 may transmit 608 to the UE 102) MAC CE or DCI triggering the configured at least one CSI-RS resource for data collection and optionally indicating the transmission property for the CSI-RS.
The UE 102 receives 1210, from the network entity 104, a CSI-RS on the CSI resource. For example, referring to FIG. 6, the UE 102 receives 610, from the network entity 104, (and the network entity 104 transmits 610 to the UE 102) at least one CSI-RS resource for data collection. Then, the UE 102 can perform data collection based on the measurement of the triggered CSI-RS resource (s) .
The UE 102 generates 1213 the data based on the CSI-RS. For example, referring to FIGs. 6-7, the UE 102 generates the data based on the CSI-RS.
The UE 102 may transmit 1214, to the network entity 104, the CSI report based on the at least one of the CSI compression or the CSI prediction. For example, referring to FIG. 6, the UE 102 transmits 614, to the network entity 104, (and the network entity 104 may receive from the UE 102) a CSI report for the configured or triggered at least one CSI-RS resource.
FIG. 12 describes a method from a UE-side of a wireless communication link, whereas FIG. 13 describes a method from a network-side of the wireless communication link.
FIG. 13 is a flowchart 1300 of a method of wireless communication at a network entity. With reference to FIGs. 1-11 and 15, the method may be performed by one or more network entities 104, which may correspond to a base station or a unit of the base station, such as the RU 106, the DU 108, the CU 110, an RU processor 1506, a DU processor 1526, a CU processor 1546, etc. The one or more network entities 104 may include memory 1506’/1526’/1546’ , which may correspond to an entirety of the one or more network entities 104, or a component of the one or more network entities 104, such as the RU processor 1506, the DU processor 1526, or the CU processor 1546. A UE apparatus 1402, as described in FIG. 14, may perform the method of flowchart 700. The one or more network entities 104, as described in FIG. 15, may perform the method of flowchart 1300.
The network entity 104 may receive 1302, from the UE 102, a UE capability report indicating at least one of: a capability of the UE for CSI reporting based on the CSI-RS for data collection; or a UE preferred configuration for the CSI-RS configured for the collection of the data. For example, referring to FIGs. 6-7, the UE 102 transmits 602, to the network entity 104, (and the network entity 104 may receive 602 from the UE 102) a UE capability on supported or preferred configurations for the CSI-RS for data collection.
The network entity 104 transmits 1304, to the UE 102, a configuration for a CS resource, the CSI resource being configured for collection of data associated with at least one of CSI compression or CSI prediction. For example, referring to FIG. 6, the UE 102 receives 604, from a network entity 104, (and the network entity 104 transmits 604 to the UE 102) a control signaling configuring at least a CSI report configuration including at least one CSI-RS resource for CSI acquisition, and optionally configuring timing information or report of the timing information for data collection based on the configured CSI-RS.
The network entity 104 may receive 1306, from the UE 102, a request for the CSI-RS configured for the collection of the data. For example, referring to FIG. 6, The UE 102 may transmit 606, to the network entity 104, (and the network entity 104 may receive 606 from the UE 102) a UE request of the CSI-RS for data collection.
The network entity 104 may transmit 1308, to the UE 102, a triggering indication that at least one of: triggers the CSI RS resource, triggers the CSI report, or indicates the transmission property for the CSI-RS. For example, referring to FIG. 6, the UE 102 may receive 608, from the network entity 104, (and the network entity 104 may transmit 608 to the UE 102) MAC CE or DCI triggering the configured at least one CSI-RS resource for data collection and optionally indicating the transmission property for the CSI-RS.
The network entity 104 transmits 1310, to the UE, a CSI-RS on the CSI resource. For example, referring to FIG. 6, the UE 102 receives 610, from the network entity 104, (and the network entity 104 transmits 610 to the UE 102) at least one CSI-RS resource for data collection. Then, the UE 102 can perform data collection based on the measurement of the triggered CSI-RS resource (s) .
The network entity 104 may receive 1314, from the UE 102, the CSI report based on the at least one of the CSI compression or the CSI prediction. For example, referring to FIG. 6, the UE 102 transmits 614, to the network entity 104, (and the network entity 104 may receive from the UE 102) a CSI report for the configured or triggered at least one CSI-RS resource.
FIG. 14 is a diagram 1400 illustrating an example of a hardware implementation for a UE apparatus 1402. The UE apparatus 1402 may be the UE 102, a component of the UE 102, or may implement UE functionality. The UE apparatus 1402 may include an application processor 1406, which may have on-chip memory 1406’ . In examples, the application processor 1406 may be coupled to a secure digital (SD) card 1408 and/or a display 1410. The application processor 1406 may also be coupled to a sensor (s) module 1412, a power supply 1414, an additional module of memory 1416, a camera 1418, and/or other related components. For example, the sensor (s) module 1412 may control a barometric pressure sensor/altimeter, a motion sensor such as an inertial management unit (IMU) , a gyroscope, accelerometer (s) , a light detection and ranging (LIDAR) device, a radio-assisted detection and ranging (RADAR) device, a sound navigation and ranging (SONAR) device, a magnetometer, an audio device, and/or other technologies used for positioning.
The UE apparatus 1402 may further include a wireless baseband processor 1426, which may be referred to as a modem. The wireless baseband processor 1426 may have on-chip memory 1426′. Along with, and similar to, the application processor 1406, the wireless baseband processor 1426 may also be coupled to the sensor (s) module 1412, the power supply 1414, the additional module of memory 1416, the camera 1418, and/or other related components. The wireless baseband processor 1426 may be additionally coupled to one or more subscriber identity module (SIM) card (s) 1420 and/or one or more transceivers 1430 (e.g., wireless RF transceivers) .
Within the one or more transceivers 1430, the UE apparatus 1402 may include a Bluetooth module 1432, a WLAN module 1434, an SPS module 1436 (e.g., GNSS module) , and/or a cellular module 1438. The Bluetooth module 1432, the WLAN module 1434, the SPS module 1436, and the cellular module 1438 may each include an on-chip transceiver (TRX) , or in some cases, just a transmitter (TX) or just a receiver (RX) . The Bluetooth module 1432, the WLAN module 1434, the SPS module 1436, and the cellular module 1438 may each include dedicated antennas and/or utilize antennas 1440 for communication with one or more other nodes. For example, the UE apparatus 1402 can communicate through the transceiver (s) 1430 via the antennas 1440 with another UE (e.g., sidelink communication) and/or with a network entity 104 (e.g., uplink/downlink communication) , where the network entity 104 may correspond to a base station or a unit of the base station, such as the RU 106, the DU 108, or the CU 110.
The wireless baseband processor 1426 and the application processor 1406 may each include a computer-readable medium/memory 1426′, 1406′, respectively. The additional module of memory 1416 may also be considered a computer-readable medium/memory. Each computer-readable medium/memory 1426′, 1406′, 1416 may be non-transitory. The wireless baseband processor 1426 and the application processor 1406 may each be responsible for general processing, including execution of software stored on the computer-readable medium/memory 1426′, 1406′, 1416. The software, when executed by the wireless baseband processor 1426/application processor 1406, causes the wireless baseband processor 1426/application processor 1406 to perform the various functions described herein. The computer-readable medium/memory may also be used for storing data that is manipulated by the wireless baseband processor 1426/application processor 1406 when executing the software. The wireless baseband processor 1426/application processor 1406 may be a component of the UE 102. The UE apparatus 1402 may be a processor chip (e.g., modem and/or application) and include just the wireless baseband processor 1426 and/or the application processor 1406. In other examples, the UE apparatus 1402 may be the entire UE 102 and include the additional modules of the apparatus 1402.
As discussed in FIG. 1 and implemented with respect to FIG. 12, the report component 140 configured to receive from a network entity 104, a configuration for a CSI resource, the CSI resource being configured for collection of data associated with at least one of CSI compression or CSI prediction; receive, from the network entity 104, a CSI-RS on the CSI resource; and generate the data based on the CSI-RS.
The report component 140 may be within the application processor 1406 (e.g., at 140a) , the wireless baseband processor 1426 (e.g., at 140b) , or both the application processor 1406 and the wireless baseband processor 1426. The report component 140a-140b may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by the one or more processors, or a combination thereof.
FIG. 15 is a diagram 1500 illustrating an example of a hardware implementation for one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functionality. The one or more network entities 104 may include, or may correspond to, at least one of the RU 106, the DU, 108, or the CU 110. The CU 110 may include a CU processor 1546, which may have on-chip memory 1546′. In some aspects, the CU 110 may further include an additional module of memory 1556 and/or a communications interface 1548, both of which may be coupled to the CU processor 1546. The CU 110 can communicate with the DU 108 through a midhaul link 162, such as an F1 interface between the communications interface 1548 of the CU 110 and a communications interface 1528 of the DU 108.
The DU 108 may include a DU processor 1526, which may have on-chip memory 1526′. In some aspects, the DU 108 may further include an additional module of memory 1536 and/or the communications interface 1528, both of which may be coupled to the DU processor 1526. The DU 108 can communicate with the RU 106 through a fronthaul link 160 between the communications interface 1528 of the DU 108 and a communications interface 1508 of the RU 106.
The RU 106 may include an RU processor 1506, which may have on-chip memory 1506′. In some aspects, the RU 106 may further include an additional module of memory 1516, the communications interface 1508, and one or more transceivers 1530, all of which may be coupled to the RU processor 1506. The RU 106 may further include antennas 1540, which may be coupled to the one or more transceivers 1530, such that the RU 106 can communicate through the one or more transceivers 1530 via the antennas 1540 with the UE 102.
The on-chip memory 1506′, 1526′, 1546′and the additional modules of memory 1516, 1536, 1556 may each be considered a computer-readable medium/memory. Each computer-readable medium/memory may be non-transitory. Each of the processors 1506, 1526, 1546 is responsible for general processing, including execution of software stored on the computer-readable medium/memory. The software, when executed by the corresponding processor (s) 1506, 1526, 1546 causes the processor (s) 1506, 1526, 1546 to perform the various functions described herein. The computer-readable medium/memory may also be used for storing data that is manipulated by the processor (s) 1506, 1526, 1546 when executing the software. In examples, the configuration component 150 may sit at any of the one or more network entities 104, such as at the CU 110; both the CU 110 and the DU 108; each of the CU 110, the DU 108, and the RU 106; the DU 108; both the DU 108 and the RU 106; or the RU 106.
As discussed in FIG. 1 and implemented with respect to FIG. 13 the configuration component 150 is configured to transmit, to a UE 102, a configuration for a CSI resource, the CSI resource being associated with collection of data for at least one of CSI compression or CSI prediction; transmit, to the UE 102, a CSI-RS on the CSI resource; and receive, from the UE 102, a CSI report based on the at least one of the CSI compression or the CSI prediction.
The configuration component 150 may be within one or more processors of the one or more network entities 104, such as the RU processor 1506 (e.g., at 150a) , the DU processor 1526 (e.g., at 150b) , and/or the CU processor 1546 (e.g., at 150c) . The configuration component 150a-150c may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors 1506, 1526, 1546 configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by the one or more processors 1506, 1526, 1546, or a combination thereof.
The specific order or hierarchy of blocks in the processes and flowcharts disclosed herein is an illustration of example approaches. Hence, the specific order or hierarchy of blocks in the processes and flowcharts may be rearranged. Some blocks may also be combined or deleted. Dashed lines may indicate optional elements of the diagrams. The accompanying method claims present elements of the various blocks in an example order, and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.
The detailed description set forth herein describes various configurations in connection with the drawings and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough explanation of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.
Aspects of wireless communication systems, such as telecommunication systems, are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, call flows, systems, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
An element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units, application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems-on-chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software, which may be referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.
If the functionality described herein is implemented in software, the functions may be stored on, or encoded as, one or more instructions or code on a computer-readable medium, such as a non-transitory computer-readable storage medium. Computer-readable media includes computer storage media and can include a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer. Storage media may be any available media that can be accessed by a computer.
Aspects, implementations, and/or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, implementations, and/or use cases may come about via integrated chip implementations and other non-module-component based devices, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI) -enabled devices, machine learning (ML) -enabled devices, etc. The aspects, implementations, and/or use cases may range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques described herein.
Devices incorporating the aspects and features described herein may also include additional components and features for the implementation and practice of the claimed and described aspects and features. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes, such as hardware components, antennas, RF-chains, power amplifiers, modulators, buffers, processor (s) , interleavers, adders/summers, etc. Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of varying configurations.
The description herein is provided to enable a person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be interpreted in view of the full scope of the present disclosure consistent with the language of the claims.
Reference to an element in the singular does not mean “one and only one” unless specifically stated, but rather “one or more. ” Terms such as “if, ” “when, ” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when, ” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The terms “may” , “might” , and “can” , as used in this disclosure, often carry certain connotations. For example, “may” refers to a permissible feature that may or may not occur, “might” refers to a feature that probably occurs, and “can” refers to a capability (e.g., capable of) . The phrase “For example” often carries a similar connotation to “may” and, therefore, “may” is sometimes excluded from sentences that include “for example” or other similar phrases.
Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C” or “one or more of A, B, or C” include any combination of A, B, and/or C, such as A and B, A and C, B and C, or A and B and C, and may include multiples of A, multiples of B, and/or multiples of C, or may include A only, B only, or C only. Sets should be interpreted as a set of elements where the elements number one or more.
Unless otherwise specifically indicated, ordinal terms such as “first” and “second” do not necessarily imply an order in time, sequence, numerical value, etc., but are used to distinguish between different instances of a term or phrase that follows each ordinal term. Reference numbers, as used in the specification and figures, are sometimes cross-referenced among drawings to denote same or similar features. A feature that is exactly the same in multiple drawings may be labeled with the same reference number in the multiple drawings. A feature that is similar among the multiple drawings, but not exactly the same, may be labeled with reference numbers that have different leading numbers, but have one or more of the same trailing numbers (e.g., 206, 306, 406, etc., may refer to similar features in the drawings) . Sometimes an “X” is used to universally denote multiple variations of a feature. For instance, “X06” can universally refer to all reference numbers that end in “06” (e.g., 206, 306, 406, etc. ) .
Structural and functional equivalents to elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ” As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” , where “A” may be information, a condition, a factor, or the like, shall be construed as “based at least on A” unless specifically recited differently.
The following examples are illustrative only and may be combined with other examples or teachings described herein, without limitation.
Example 1 is a method of wireless communication at a UE, including: receiving, from a network entity, a configuration for a CSI resource, the CSI resource being configured for collection of data associated with at least one of CSI compression or CSI prediction; receiving, from the network entity, a CSI-RS on the CSI resource; and generating the data based on the CSI-RS.
Example 2 may be combined with Example 1 and further includes that the receiving the configuration further includes receiving, from the network entity, timing information for the collection of the data based on the CSI-RS.
Example 3 may be combined with Example 2 and further includes that the timing information comprises at least one of: a periodicity for the collection of the data, a timing for the CSI-RS for the collection of the data, a number of the CSI-RS for a period associated with the collection of the data, or an interval of the CSI-RS for the collection of the data for each period.
Example 4 may be combined with any of Examples 1-3 and further includes transmitting, to the network entity, a request for the CSI-RS configured for the collection of the data.
Example 5 may be combined with Example 4 and further includes that the transmitting, to the network entity, the request for the CSI-RS is based on an expiration of a timer.
Example 6 may be combined with any of Examples 4-5 and further includes that the request for the CSI-RS includes at least one of: a serving cell index for the CSI-RS; a bandwidth part (BWP) index for the CSI-RS; a CSI-RS resource index; a parameter for a UE preferred configuration for the CSI-RS; or an indication of a transmission property for the CSI-RS.
Example 7 may be combined with any of Examples 4-6 and further includes monitoring for a response to the request after a first symbol or a last symbol of the transmitting the request for the CSI-RS.
Example 8 may be combined with any of Examples 1-7 and further includes that the receiving the configuration further includes receiving, from the network entity, at least one of: an indication of a transmission property for the CSI-RS, or a parameter for the UE to request the CSI-RS.
Example 9 may be combined with Example 8 and further includes that the transmission property for the CSI-RS includes at least one of: a number of horizontal antenna ports, a number of vertical antenna ports, an antenna virtualization weight, an associated PCI, or an antenna radiation pattern.
Example 10 may be combined with Example 9 and further includes transmitting, to the network entity, a report including timing information for the CSI-RS configured for the collection of the data.
Example 11 may be combined with any of Examples 1-10 and further includes transmitting, to the network entity, a UE capability report indicating at least one of: a capability of the UE for CSI reporting based on the CSI-RS for data collection; or a UE preferred configuration for the CSI-RS configured for the collection of the data, wherein the UE preferred configuration comprises at least one of:a supported or preferred number of CSI-RS instances, a minimum number of the CSI-RS instances, preferred offset between two consecutive CSI-RS instances, a maximum offset between two consecutive CSI-RS instances, a minimum offset between two consecutive CSI-RS instances, a supported or preferred periodicity for the CSI-RS, a maximum periodicity for the CSI-RS, a minimum periodicity for the CSI-RS, a supported or preferred bandwidth, or a minimum bandwidth for the CSI-RS, a supported or preferred time-domain behavior for the CSI-RS.
Example 12 may be combined with Example 11 and further includes that the UE preferred configuration for the CSI-RS is based on at least one of: a CSI processing unit (CPU) occupancy duration for the CSI-RS, or a minimum processing delay for a CSI report.
Example 13 may be combined with any Examples 1-12 and further includes receiving, from the network entity, a triggering indication that at least one of:triggers the CSI-RS resource, triggers the CSI report, or indicates the transmission property for the CSI-RS.
Example 14 may be combined with any Examples 1-13 and further includes transmitting, to the network entity, the CSI report based on the at least one of the CSI compression or the CSI prediction.
Example 15 is a method of wireless communication at a network entity, including: transmitting, to a UE, a configuration for a CSI resource, the CSI resource being associated with collection of data for at least one of CSI compression or CSI prediction; transmitting, to the UE, a CSI-RS on the CSI resource; and receiving, from the UE, a CSI report based on the at least one of the CSI compression or the CSI prediction.
Example 16 may be combined with Example 15 and further includes that the transmitting the configuration further includes transmitting, to the UE, timing information for the collection of the data based on the CSI-RS.
Example 17 may be combined with Example 16 and further includes that the timing information comprises at least one of: a periodicity for the collection of the data, a timing for the CSI-RS for the collection of the data, a number of the CSI-RS for a period associated with the collection of the data, or an interval of the CSI-RS for the collection of the data for each period.
Example 18 may be combined with any of Examples 15-17 and further includes receiving, from the UE, a request for the CSI-RS configured for the collection of the data.
Example 19 may be combined with Example 18 and further includes that the receiving, from the UE, the request for the CSI-RS is based on an expiration of a timer.
Example 20 may be combined with any of Examples 18-19 and further includes that the request for the CSI-RS includes at least one of: a serving cell index for the CSI-RS; a bandwidth part (BWP) index for the CSI-RS; a CSI-RS resource index; a parameter for a UE preferred configuration for the CSI-RS; or an indication of a transmission property for the CSI-RS.
Example 21 may be combined with any of Examples 15-20 and further includes that the transmitting the configuration further includes transmitting, to the UE, at least one of: an indication of a transmission property for the CSI-RS, or a parameter for the UE to request the CSI-RS.
Example 22 may be combined with Example 21 and further includes that the transmission property for the CSI-RS includes at least one of: a number of horizontal antenna ports, a number of vertical antenna ports, an antenna virtualization weight, an associated PCI, or an antenna radiation pattern.
Example 23 may be combined with Example 22 and further includes receiving, from the UE, a report including timing information for the CSI-RS configured for the collection of the data.
Example 24 may be combined with any of Examples 15-23 and further includes receiving, from the UE, a UE capability report indicating at least one of: a capability of the UE for CSI reporting based on the CSI-RS for data collection; or a UE preferred configuration for the CSI-RS configured for the collection of the data, wherein the UE preferred configuration comprises at least one of: a supported or preferred number of CSI-RS instances, a minimum number of the CSI-RS instances, preferred offset between two consecutive CSI-RS instances, a maximum offset between two consecutive CSI-RS instances, a minimum offset between two consecutive CSI-RS instances, a supported or preferred periodicity for the CSI-RS, a maximum periodicity for the CSI-RS, a minimum periodicity for the CSI-RS, a supported or preferred bandwidth, a minimum bandwidth for the CSI-RS, or a supported or preferred time-domain behavior for the CSI-RS.
Example 25 may be combined with Example 24 and further includes that the UE preferred configuration for the CSI-RS is based on at least one of: a CSI processing unit (CPU) occupancy duration for the CSI-RS, or a minimum processing delay for a CSI report.
Example 26 may be combined with any Examples 15-25 and further includes receiving, from the network entity, a triggering indication that at least one of:triggers the CSI-RS resource, triggers the CSI report, or indicates the transmission property for the CSI-RS.
Example 27 may be combined with any Examples 15-26 and further includes receiving, from the UE, the CSI report based on the at least one of the CSI compression or the CSI prediction.
Example 28 is an apparatus for wireless communication for implementing a method as in any of examples 1-27.
Example 29 is an apparatus for wireless communication including means for implementing a method as in any of examples 1-27.
Example 30 is a non-transitory computer-readable medium storing computer executable code, the code when executed by a processor causes the processor to implement a method as in any of examples 1-27.

Claims

A method of wireless communication at a user equipment (UE) (102) , comprising:

receiving (604, 704) , from a network entity (104) , a configuration for a channel state information (CSI) resource, the CSI resource being configured for collection of data associated with at least one of CSI compression or CSI prediction;

receiving (610) , from the network entity (104) , a channel state information-reference signal (CSI-RS) on the CSI resource; and

generating (613) the data based on the CSI-RS.
The method of claim 1, wherein the receiving (604) the configuration further comprises:

receiving (604) , from the network entity (104) , timing information for the collection of the data based on the CSI-RS.
The method of claim 2, wherein the timing information comprises at least one of:

a periodicity for the collection of the data,

a timing for the CSI-RS for the collection of the data,

a number of the CSI-RS for a period associated with the collection of the data, or

an interval of the CSI-RS for the collection of the data for each period.
The method of any claims 1-3, further comprising:

transmitting (606) , to the network entity (104) , a request for the CSI-RS configured for the collection of the data.
The method of claim 4, wherein the transmitting (606) , to the network entity (104) , the request for the CSI-RS is based on an expiration of a timer.
The method of any of claims 4-5, wherein the request for the CSI-RS comprises at least one of:

a serving cell index for the CSI-RS;

a bandwidth part (BWP) index for the CSI-RS;

a CSI-RS resource index;

a parameter for a UE preferred configuration for the CSI-RS; or

an indication of a transmission property for the CSI-RS.
The method of any of claims 4-6, further comprising:

monitoring for a response to the request after a first symbol or a last symbol of the transmitting (606) the request for the CSI-RS.
The method of any of claims 1-7, wherein the receiving (704) the configuration further comprises:

receiving (704) , from the network entity (104) , at least one of:

an indication of a transmission property for the CSI-RS, or

a parameter for the UE (102) to request the CSI-RS.
The method of claim 8, wherein the transmission property for the CSI-RS comprises at least one of:

a number of horizontal antenna ports,

a number of vertical antenna ports,

an antenna virtualization weight,

an associated physical cell identifier (PCI) , or

an antenna radiation pattern.
The method of claim 9, further comprising:

transmitting (706) , to the network entity (104) , a report including timing information for the CSI-RS configured for the collection of the data.
The method of any of claims 1-10, further comprising:

transmitting (602) , to the network entity (104) , a UE capability report indicating at least one of:

a capability of the UE (102) for CSI reporting based on the CSI-RS for data collection; or

a UE preferred configuration for the CSI-RS configured for the collection of the data, wherein the UE preferred configuration comprises at least one of:

a supported or preferred number of CSI-RS instances,

a minimum number of the CSI-RS instances,

preferred offset between two consecutive CSI-RS instances,

a maximum offset between two consecutive CSI-RS instances,

a minimum offset between two consecutive CSI-RS instances,

a supported or preferred periodicity for the CSI-RS,

a maximum periodicity for the CSI-RS,

a minimum periodicity for the CSI-RS,

a supported or preferred bandwidth,

a minimum bandwidth for the CSI-RS, or

a supported or preferred time-domain behavior for the CSI-RS.
The method of claim 11, wherein the UE preferred configuration for the CSI-RS is based on at least one of:

a CSI processing unit (CPU) occupancy duration for the CSI-RS, or

a minimum processing delay for a CSI report.
The method of any of claims 1-12, further comprising:

receiving (608, 708) , from the network entity (104) , a triggering indication that at least one of:

triggers the CSI-RS resource,

triggers the CSI report, or

indicates the transmission property for the CSI-RS.
The method of any of claims 1-13, further comprising:

transmitting (614, 714) , to the network entity (104) , the CSI report based on the at least one of the CSI compression or the CSI prediction.
A method of wireless communication at a network entity (104) , comprising:

transmitting (604, 704) , to a user equipment (UE) (102) , a configuration for a channel state information (CSI) resource, the CSI resource being associated with collection of data for at least one of CSI compression or CSI prediction;

transmitting (610) , to the UE (102) , a channel state information-reference signal (CSI-RS) on the CSI resource; and

receiving (614, 714) , from the UE (102) , a CSI report based on the at least one of the CSI compression or the CSI prediction.
The method of claim 15, wherein the transmitting (604) the configuration further comprises:

transmitting (604) , to the UE (102) , timing information for the collection of the data based on the CSI-RS.
The method of claim 15, wherein the transmitting (704) the configuration further comprises:

transmitting (704) , to the UE (102) , at least one of:

an indication of a transmission property for the CSI-RS, or

a parameter for the UE (102) to request the CSI-RS.
The method of any of claims 15-17, further comprising:

receiving (602) , from the UE (102) , a UE capability report indicating at least one of:

a capability of the UE (102) for CSI reporting; or

a UE preferred configuration for the CSI-RS configured for the collection of the data, wherein the UE preferred configuration comprises at least one of:

a supported or preferred number of CSI-RS instances,

a minimum number of the CSI-RS instances,

preferred offset between two consecutive CSI-RS instances,

a maximum offset between two consecutive CSI-RS instances,

a minimum offset between two consecutive CSI-RS instances,

a supported or preferred periodicity for the CSI-RS,

a maximum periodicity for the CSI-RS,

a minimum periodicity for the CSI-RS,

a supported or preferred bandwidth,

a minimum bandwidth for the CSI-RS, or

a supported or preferred time-domain behavior for the CSI-RS.
An apparatus for wireless communication comprising a memory, a transceiver, and a processor coupled to the memory and the transceiver, the apparatus being configured to implement a method as in any of claims 1-18.