Collection of reference signal data for training machine learning models

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a User Equipment (UE) may receive a first message indicating a configuration for a reference signal to be used for data collection and / or that data collection based on the reference signal is permitted. The UE may receive the reference signal. The UE may collect data based at least in part on the reference signal. The UE may transmit the collected data. Numerous other aspects are described.

Description

Technical Field

[0001]

[0001] Aspect of the present disclosure generally relates to wireless communication and techniques and apparatus for collecting data for training a machine learning model.

Background Art

[0002]

[0002] Wireless communication systems have been widely deployed to provide various telecommunication services such as telephone, video, data, messaging, and broadcast. A typical wireless communication system may employ a multiple access technology that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standards published by the Third Generation Partnership Project (3GPP).

[0003]

[0003] The wireless network may include one or more base stations that support communication relating to one or more User Equipment (UEs). The UEs may communicate with the base stations via downlink and uplink communications. "Downlink" (or "DL") refers to the communication link from the base station to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the base station.

[0004]

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, national, regional, and / or global scales. New Radio (NR), sometimes referred to as 5G, is a set of extensions to the LTE mobile standard published by 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, enhancing service, utilizing new spectra, and by using orthogonal frequency division multiplexing (OFDM) with cyclic prefixes (CP) (CP-OFDM) on the downlink, CP-OFDM and / or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM, DFT-s-OFDM) on the uplink, and by better integrating with other open standards that support beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies remain valuable. [Overview of the Initiative]

[0005]

[0005] Some aspects described herein relate to methods of wireless communication performed by User Equipment (UE). The method may include configuring a reference signal to be used for data acquisition and / or receiving a first message indicating that data acquisition based on the reference signal is permitted. The method may include receiving the reference signal. The method may include acquiring data based at least in part on the reference signal. The method may include transmitting the acquired data.

[0006]

[0006] Some aspects described herein relate to methods of wireless communication performed by a network entity. The method may include configuring a reference signal to be used for data acquisition and / or transmitting a first message indicating that data acquisition based on the reference signal is permitted. The method may also include transmitting a reference signal.

[0007]

[0007] Some embodiments described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. One or more processors may be configured to receive a configuration for a reference signal used for data acquisition and / or a first message indicating that data acquisition based on the reference signal is permitted. One or more processors may be configured to receive the reference signal. One or more processors may be configured to acquire data based at least in part on the reference signal. One or more processors may be configured to transmit the acquired data.

[0008]

[0008] Some embodiments described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. One or more processors may be configured for a reference signal used for data acquisition and / or for transmitting a first message indicating that data acquisition based on the reference signal is permitted. One or more processors may be configured for transmitting the reference signal.

[0009]

[0009] Some embodiments described herein relate to a non-temporary computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions may, when executed by one or more processors of the UE, cause the UE to receive a first message indicating that it is authorized to configure a reference signal to be used for data acquisition and / or to acquire data based on the reference signal. The set of instructions may, when executed by one or more processors of the UE, cause the UE to receive a reference signal. The set of instructions may, when executed by one or more processors of the UE, cause the UE to acquire data based at least in part on the reference signal. The set of instructions may, when executed by one or more processors of the UE, cause the UE to transmit the acquired data.

[0010]

[0010] Some embodiments described herein relate to a non-temporary computer-readable medium for storing a set of instructions for wireless communication by a network entity. The set of instructions may, when executed by one or more processors of the network entity, cause the network entity to transmit a configuration for a reference signal to be used for data acquisition, and / or a first message indicating that data acquisition based on the reference signal is permitted. The set of instructions may, when executed by one or more processors of the network entity, cause the network entity to transmit a reference signal.

[0011]

[0011] Some embodiments described herein relate to devices for wireless communication. The device may include a configuration for a reference signal used for data acquisition, and / or means for receiving a first message indicating that data acquisition based on the reference signal is permitted. The device may include means for receiving the reference signal. The device may include means for acquiring data based at least in part on the reference signal. The device may include means for transmitting the acquired data.

[0012]

[0012] Some embodiments described herein relate to devices for wireless communication. The devices may include a configuration for a reference signal used for data acquisition, and / or means for transmitting a first message indicating that data acquisition based on the reference signal is permitted. The devices may also include means for transmitting the reference signal.

[0013]

[0013] Embodiments generally include methods, apparatus, systems, computer program products, non-temporary computer-readable media, UEs, base stations, network entities, wireless communication devices, and / or processing systems substantially described herein, with reference to and as shown by the drawings and specification.

[0014]

[0014] The preceding paragraphs have provided a fairly broad overview of the features and technical advantages of the embodiments of this disclosure in order to better understand the following "Modes for Carrying Out the Invention". Additional features and advantages are described below. The concepts and specific examples disclosed can be readily used as a basis for modifying or designing other structures to accomplish the same objectives of this disclosure. Such equivalent structures will not deviate from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their mechanisms and methods of operation, will be better understood from the following description, along with the relevant advantages, when considered together with the accompanying figures. Each of the figures is provided for illustrative and explanatory purposes only, and not as a definition of the limitations of the claims.

[0015]

[0015] While embodiments are described in this disclosure by illustrating several examples, those skilled in the art will understand that such embodiments may be implemented in many different configurations and scenarios. The technologies described herein may be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some embodiments may be implemented via integrated chip embodiments or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence-enabled devices). Embodiments may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the embodiments and features described may include additional components and features for the claims and implementation forms and practices of the embodiments described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital applications (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The embodiments described herein are intended to be applicable to a wide variety of devices, components, systems, distributed configurations, and / or end-user devices of various sizes, shapes, and structures. [Brief explanation of the drawing]

[0016]

[0016] Some of the features listed above in this disclosure may be better understood by referring to the embodiments shown in the accompanying drawings, which may provide a more detailed description of the features briefly summarized above. However, it should be noted that the accompanying drawings only illustrate certain typical embodiments of this disclosure and should not be considered to limit the scope of this disclosure, as other similarly effective embodiments may be recognized in this description. The same reference numerals in different drawings may identify the same or similar elements. [Figure 1]

[0017] This figure shows one embodiment of a wireless network according to the present disclosure. [Figure 2]

[0018] This figure illustrates one embodiment of a network entity communicating with a user device (UE) within a wireless network, as disclosed herein. [Figure 3]

[0019] This figure shows one embodiment of a non-aggregated base station according to the present disclosure. [Figure 4]

[0020] This figure illustrates an example of a channel state information reference signal beam management procedure according to this disclosure. [Figure 5]

[0021] This figure illustrates one embodiment related to data collection for training a machine learning model, as described herein. [Figure 6]

[0022] This figure illustrates an example of data collection for training a machine learning model according to the present disclosure. [Figure 7]

[0023] This figure illustrates, for example, an exemplary process performed by a UE as described in this disclosure. [Figure 8]

[0024] This figure illustrates an exemplary process performed, for example, by a network entity, as disclosed herein. [Figure 9]

[0025] This is a diagram of an exemplary apparatus for wireless communication as described herein. [Figure 10]A diagram of an exemplary apparatus for wireless communication according to the present disclosure. **DETAILED DESCRIPTION**

[0017]

[0026] Various aspects of the present disclosure are described more fully hereinafter with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. It is to be understood that the scope of the present disclosure is intended to encompass any other aspect of the present disclosure, whether implemented independently of or combined with any other aspect of the present disclosure, including any and all aspects of the present disclosure disclosed herein. For example, the apparatus may be implemented or the method may be practiced using any number of the aspects described herein. It is also intended that the scope of the present disclosure include such apparatus or methods practiced using other structures, functions, or structures and functions in addition to or other than those described herein. It should be understood by those skilled in the art that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of the claims.

[0018]

[0027] Next, some aspects of a telecommunications system are presented while referring to various apparatuses and techniques. These apparatuses and techniques are described in the following "Detailed Description" and are shown in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or as software depends on the specific application and design constraints imposed on the overall system.

[0019]

[0028] Aspects may be described herein using terms commonly associated with 5G or New Radio (NR) radio access technology (RAT), but aspects of the present disclosure may be applicable to other RATs such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0020]

[0029] FIG. 1 is a diagram showing an example of a wireless network 100 according to the present disclosure. The wireless network 100 can be, among other examples, a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements thereof. The wireless network 100 may include one user equipment (UE) 120 or multiple UEs 120 (shown as UE120a, UE120b, UE120c, UE120d, and UE120e). The wireless network 100 may include one or more network entities such as base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), and / or other network entities. The base station 110 is a network entity that communicates with the UE 120. The base station 110 (which may sometimes be referred to as a BS (Base Station)) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a Transmission Reception Point (TRP). Each base station 110 may provide communication coverage to a specific geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of the base station 110 and / or the base station subsystem providing services to this coverage area, depending on the context in which the term is used.

[0021]

[0030] Base station 110 may provide communication coverage to macrocells, picocells, femtocells, and / or other types of cells. Macrocells may cover relatively large geographical areas (e.g., a radius of several kilometers) and may allow unrestricted access by UEs 120 subscribing to the service. Picocells may cover relatively small geographical areas and may allow unrestricted access by UEs 120 subscribing to the service. Femtocells may cover relatively small geographical areas (e.g., a home) and may allow restricted access by UEs 120 associated with a femtocell (e.g., UEs 120 within a Closed Subscriber Group, CSG). Base station 110 for macrocells may be referred to as a macro base station. Base station 110 for picocells may be referred to as a pico base station. Base station 110 for femtocells may be referred to as a femto base station or home base station. In the example shown in Figure 1, BS110a may be a macro base station for macrocell 102a, BS110b may be a pico base station for picocell 102b, and BS110c may be a femto base station for femtocell 102c. A base station may support one or more (e.g., three) cells.

[0022]

[0031] In some embodiments, the cells do not necessarily have to be fixed, and the geographical area of ​​the cells may move according to the location of mobile base stations 110 (e.g., mobile base stations). In some embodiments, the base stations 110 may interconnect with each other and / or with one or more other base stations 110 or network entities in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0023]

[0032] In some embodiments, the terms “the base station” (e.g., base station 110) or “network entity” may refer to aggregated base stations, unaggregated base stations, Integrated Access and Backhaul (IAB) nodes, relay nodes, and / or one or more components thereof. For example, in some embodiments, “base station” or “network entity” may refer to a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, or a combination thereof. In some embodiments, the terms “base station” or “network entity” may refer to a single device configured to perform one or more functions, such as the functions described herein with respect to base station 110. In some embodiments, the terms “base station” or “network entity” may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of several different devices (which may be located in the same or different geographical locations) may be configured to perform at least a portion of a function or to replicate the operation of at least a portion of a function, but the term “base station” or “network entity” may refer to any one or more of those different devices. In some embodiments, the term “base station” or “network entity” may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some embodiments, two or more base station functions may be instantiated on a single device. In some embodiments, the term “base station” or “network entity” may refer to one of the base station functions and not another base station function.In this way, a single device may include two or more base stations.

[0024]

[0033] The wireless network 100 may include one or more relay stations. A relay station is a network entity that can receive data transmissions from upstream stations (e.g., network entities or UE120) and send data transmissions to downstream stations (e.g., UE120 or network entities). A relay station may also be a UE120 that can relay transmissions to other UE120s. In the example shown in Figure 1, BS110d (e.g., a relay base station) may communicate with BS110a (e.g., a macro base station) and UE120d to facilitate communication between BS110a and UE120d. The base station 110 that relays communications may be referred to as a relay station, relay base station, repeater, etc.

[0025]

[0034] The wireless network 100 may be a heterogeneous network having network entities including different types of base stations (BS), such as macro base stations, pico base stations, femto base stations, and relay base stations. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different effects on interference within the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 to 40 watts), while pico base stations, femto base stations, and relay base stations may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0026]

[0035] The network controller 130 may be coupled to or communicate with a set of network entities and may provide coordination and control for these network entities. The network controller 130 may communicate with the base station 110 via a backhaul communication link. The network entities may communicate with each other directly or indirectly via wireless or wireline backhaul communication links.

[0027]

[0036] UE120 may be distributed across the entire wireless network 100, and each UE120 may be fixed or mobile. UE120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE120 may also include cellular telephones (e.g., smartphones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablets, cameras, game devices, netbooks, smartbooks, ultrabooks, medical devices, biometric devices, wearable devices (e.g., smartwatches, smart clothes, smart glasses, smart wristbands, smart jewelry (e.g., smart rings or smart bracelets)), entertainment devices (e.g., music devices, video devices, and / or satellite radios), vehicle components or sensors, smart meters / sensors, industrial manufacturing equipment, global positioning system devices, and / or any other suitable devices configured to communicate via a wireless medium.

[0028]

[0037] Some UE120s may be considered Machine-Type Communication (MTC) UEs, or evolved or enhanced Machine-Type Communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with network entities, other devices (e.g., remote devices), or any other entities. Some UE120s may be considered Internet-of-Things (IoT) devices and / or implemented as NB-IoT (narrowband IoT) devices. Some UE120s may be considered customer premises equipment. A UE120 may be contained within a housing that accommodates components of the UE120, such as processor components and / or memory components. In some embodiments, the processor components and memory components may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0029]

[0038] In general, any number of wireless networks 100 may be deployed in a given geographical area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as wireless technology, air interface, etc. Frequency may be referred to as carrier, frequency channel, etc. To avoid interference between wireless networks of different RATs, each frequency may support a single RAT in a given geographical area. In some cases, an NR network or a 5G RAT network may be deployed.

[0030]

[0039] In some embodiments, two or more UE120s (for example, shown as UE120a and UE120e) may communicate directly using one or more sidelink channels (for example, without using network entities as intermediaries for communication with each other). For example, UE120s may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such embodiments, UE120s may perform scheduling operations, resource selection operations, and / or other operations as described elsewhere in this specification as performed by base station 110s.

[0031]

[0040] Devices in wireless network 100 may communicate using the electromagnetic spectrum, which can be subdivided into various classes, bands, channels, etc., depending on the frequency or wavelength. For example, devices in wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands are identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although a portion of FR1 is higher than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. A similar nomenclature issue may arise with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) which is identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0032]

[0041] The frequencies between FR1 and FR2 are often referred to as intermediate band frequencies. In recent 5G NR research, the operating band for these intermediate band frequencies is identified as frequency range designation FR3 (7.125 GHz to 24.25 GHz). The frequency bands included within FR3 may inherit the characteristics of FR1 and / or FR2, and therefore, in effect, the characteristics of FR1 and / or FR2 may be extended to the intermediate band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0033]

[0042] With the above examples in mind, please understand that, unless otherwise specified, terms such as “sub-6 GHz” may broadly refer to frequencies that are less than 6 GHz, may be within FR1, or may include intermediate band frequencies, as used herein. Furthermore, please understand that, unless otherwise specified, terms such as “millimeter wave” may broadly refer to frequencies that may include intermediate band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band, as used herein. The frequencies included within these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the technologies described herein are intended to be applicable to those modified frequency ranges.

[0034]

[0043] In some embodiments, the UE (e.g., UE120) may include a communications manager 140. As described in more detail elsewhere in this specification, the communications manager 140 may receive a configuration for a reference signal to be used for data acquisition, and / or a first message indicating that data acquisition based on the reference signal is permitted. The communications manager 140 may receive the reference signal and acquire data based at least in part on the reference signal. The communications manager 140 may transmit the acquired data. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0035]

[0044] In some embodiments, a network entity (e.g., base station 110) may include a communications manager 150. As described in more detail elsewhere in this specification, the communications manager 150 may transmit a configuration for a reference signal to be used for data acquisition, and / or a first message indicating that data acquisition based on the reference signal is permitted. The communications manager 150 may transmit a reference signal. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0036]

[0045] As shown above, Figure 1 is provided as one embodiment. Other embodiments may differ from those described with respect to Figure 1.

[0037]

[0046] Figure 2 shows an embodiment 200 of a network entity (e.g., base station 110) that communicates with UE 120 in a wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≧1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≧1).

[0038]

[0047] At base station 110, the transmitting processor 220 may receive data destined for UE 120 (or a set of UE 120s) from data source 212. The transmitting processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120, at least in part, based on one or more channel quality indicators (CQIs) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120, at least in part, based on the MCS(mCS) selected for the UE 120, and may provide data symbols to the UE 120. The transmitting processor 220 may process system information and control information (e.g., CQI requests, authorizations, and / or upper-layer signaling) (e.g., related to semi-static resource partitioning information, SRPI), and may provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may, where applicable, perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, and may provide a set of output symbol streams (e.g., T output symbol streams) to a set of corresponding modems 232 (e.g., T modems), indicated as modems 232a to 232t. For example, each output symbol stream may be provided to a modulator component (indicated as MOD) of a modem 232.Each modem 232 may process its respective output symbol stream using its respective modulator component (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may further process the output sample stream using its respective modulator component (e.g., convert to analog, amplify, filter, and / or upconvert) to obtain a downlink signal. Modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) indicated as antennas 234a to 234t.

[0039]

[0048] In UE120, a set of antennas 252 (indicated as antennas 252a to 252r) may receive downlink signals from base station 110 and / or other base stations 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) indicated as modems 254a to 254r. For example, each received signal may be provided to a demodulator component of a modem 254 (indicated as DEMOD). Each modem 254 may use its respective demodulator component to process the received signal (e.g., filter, amplify, downconvert, and / or digitize) to obtain an input sample. Each modem 254 may further process the input sample (e.g., for OFDM) using its demodulator component to obtain a received symbol. A MIMO detector 256 may obtain a received symbol from a modem 254, perform MIMO detection on the received symbol where applicable, and provide the detected symbol. The receiving processor 258 may process the detected symbols (e.g., demodulate and decode), provide the decoded data about UE120 to the data sink 260, and provide the decoded control and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine, among other examples, the Reference Signal Received Power (RSRP) parameter, the Received Signal Strength Indicator (RSSI) parameter, the Reference Signal Received Quality (RSRQ) parameter, and / or the CQI parameter. In some embodiments, one or more components of UE120 may be contained within the housing 284.

[0040]

[0049] The network controller 130 may include a communication unit 294, a controller / processor 290, and memory 292. The network controller 130 may include, for example, one or more devices in the core network. The network controller 130 may communicate with network entities via the communication unit 294.

[0041]

[0050] One or more antennas (e.g., antennas 234a-234t and / or antennas 252a-252r) may include, or be contained within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements, a set of coplanar antenna elements, a set of non-coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmitting and / or receiving components, such as one or more components in Figure 2 (in a single housing or multiple housings).

[0042]

[0051] On the uplink, in UE120, the transmit processor 264 may receive and process data from data source 262 and control information (for reporting, including RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may, where applicable, be precoded by the TX MIMO processor 266, further processed by the modem 254 (for DFT-s-OFDM or CP-OFDM), and transmitted to the network entity. In some embodiments, the modem 254 of UE120 may include a modulator and a demodulator. In some embodiments, UE120 includes a transceiver. The transceiver may include any combination of antennas 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform any of the methods described herein (for example, with reference to Figures 4 to 10).

[0043]

[0052] In a network entity (e.g., base station 110), uplink signals from UE 120 and / or other UEs are received by antenna 234, processed by modem 232 (e.g., the demodulator component of modem 232, indicated as DEMOD), detected by MIMO detector 236 where applicable, and further processed by receiving processor 238 to obtain decoded data and control information sent by UE 120. The receiving processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. The network entity may include a communication unit 244, which may communicate with network controller 130 via the communication unit 244. The network entity may include a scheduler 246 for scheduling one or more UE 120 for downlink and / or uplink communication. In some embodiments, the modem 232 of the network entity may include a modulator and a demodulator. In some embodiments, the network entity includes a transceiver. The transceiver may include any combination of antennas 234, modems 232, MIMO detectors 236, receiving processors 238, transmitting processors 220, and / or TX MIMO processors 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform any aspect of the methods described herein (referring, for example, to Figures 4 to 10).

[0044]

[0053] The controller / processor of the network entity (e.g., the controller / processor 240 of base station 110), the controller / processor 280 of UE 120, and / or any other component(s) in Figure 2 may perform one or more techniques associated with data acquisition for training machine learning models for channel estimation or reference signal configuration, as described in more detail elsewhere in this specification. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other component(s) in Figure 2 may perform or direct the operation of, for example, process 700 in Figure 7, process 800 in Figure 8, and / or other processes as described herein. Memories 242 and 282 may store data and program code for the network entity and UE 120, respectively. In some embodiments, memories 242 and / or 282 may include a non-temporary computer-readable medium for storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, if one or more instructions are executed by one or more processors of the network entity and / or UE120 (for example, directly or after compiling, translating, and / or interpreting), one or more processors, UE120, and / or the network entity may be instructed to execute or perform other processes, such as process 700 in Figure 7, process 800 in Figure 8, and / or other processes as described herein. In some embodiments, executing an instruction may include, among other examples, executing the instruction, translating the instruction, compiling the instruction, and / or interpreting the instruction.

[0045]

[0054] In some embodiments, the UE120 includes means for receiving a configuration for a reference signal used for data acquisition, and / or a first message indicating that data acquisition based on the reference signal is permitted; means for receiving the reference signal; means for acquiring data based at least in part on the reference signal; and / or means for transmitting the acquired data. The means by which the UE120 performs the operations described herein may include, for example, one or more of the following: a communications manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receiving processor 258, a transmitting processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0046]

[0055] In some embodiments, a network entity (e.g., base station 110) includes a configuration for a reference signal used for data acquisition, and / or means for transmitting a first message indicating that data acquisition based on the reference signal is permitted, and / or means for transmitting the reference signal. In some embodiments, the means by which the network entity performs the operations described herein may include, for example, one or more of the following: a communications manager 150, a transmitting processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receiving processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0047]

[0056] Although the blocks in Figure 2 are shown as individual components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination of components, or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0048]

[0057] As shown above, Figure 2 is provided as one embodiment. Other embodiments may differ from those described with respect to Figure 2.

[0049]

[0058] Figure 3 is a diagram showing one embodiment of the non-aggregated base station 300 according to the present disclosure.

[0050]

[0059] The deployment of communication systems such as 5G NR systems may be configured in multiple ways using various components or parts. In a 5G NR system or network, network equipment such as network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements, or base stations, or one or more units (or one or more components) that perform base station functionality, may be implemented in an aggregated or unaggregated architecture. For example, a BS (e.g., node B, evolutionary NB (eNB), NR BS, 5G NB, access point (AP), TRP, or cell) may be implemented as an aggregated or unaggregated base station (also known as a standalone BS or monolithic BS).

[0051]

[0060] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A non-aggregated base station may be configured to utilize a protocol stack that is physically or logically distributed across two or more units (e.g., one or more CUs, one or more DUs, or one or more RUs). In some embodiments, the CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, geographically or virtually distributed across one or more other RAN nodes. The DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit (e.g., a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU)).

[0052]

[0061] The operation or network design of a base station type may take into account the aggregation characteristics of the base station function. For example, non-aggregated base stations may be used in virtualized radio access networks (vRAN), also known as IAB networks, Open Radio Access Networks (O-RAN, such as network configurations operated by the O-RAN Alliance), or Cloud Radio Access Networks (C-RAN). Non-aggregation may include distributing functions across two or more units in various physical locations, as well as virtually distributing functions for at least one unit, which can allow for flexibility in network design. Various units of a non-aggregated base station, or a non-aggregated RAN architecture, may be configured for wired or wireless communication with at least one other unit.

[0053]

[0062] The non-aggregated base station 300 architecture may include one or more CU310s that can communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more non-aggregated base station units (such as a quasi-RT RIC325 via an E2 link, or a non-RT RIC315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CU310s may communicate with one or more DU330s via their respective midhaul links, such as an F1 interface. The DU330s may communicate with one or more RU340s via their respective fronthaul links. The fronthaul links, midhaul links, and backhaul links may generally be referred to as “communication links”. The RU340s may communicate with their respective UE120s via one or more RF access links. In some embodiments, the UE120s may be serviced simultaneously by multiple RU340s. DU330 and RU340 may also be referred to as "O-RAN DU (O-DUs)" and "O-RAN RU (O-RUs)," respectively. A network entity may include a CU, DU, RU, or any combination of CU, DU, and RU. A network entity may include a non-aggregated base station, or one or more components of a non-aggregated base station, such as a CU, DU, RU, or any combination of CU, DU, and RU. A network entity may also include one or more of the following components that provide or can service a network interface for a TRP, relay station, passive device, intelligent reflective surface (IRS), or UE, mobile station, sensor / actuator, or other wireless device.

[0054]

[0063] Each unit (e.g., CU310, DU330, RU340, and quasi-RT RIC325, non-RT RIC315, and SMO framework 305) includes, or may be coupled to, one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each unit, or an associated processor or controller providing instructions to a unit's communication interface, may be configured to communicate with one or more other units via a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more other units via a wired transmission medium. A unit may also include a wireless interface which may include a receiver, transmitter, or transceiver (such as an RF transceiver), configured to receive or transmit signals, or both, to one or more other units via a wireless transmission medium.

[0055]

[0064] In some embodiments, the CU310 may host one or more higher-layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by the CU310. The CU310 may be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface such as the E1 interface. The CU310 may be implemented to communicate with the DU330 as needed for network control and signaling.

[0056]

[0065] The DU330 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU340s. In some embodiments, the DU330 may host one or more of the following, at least in part, a functional decomposition such as that defined by 3GPP: a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) coding and decoding, scrambling, modulation, demodulation, etc.). In some embodiments, the DU330 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU330, or with control functions hosted by the CU310.

[0057]

[0066] Lower-layer functions may be implemented by one or more RU340s. In some deployments, RU340s controlled by DU330s may correspond to logical nodes hosting RF processing functions, or lower PHY layer functions (such as performing Fast Fourier Transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, at least partially based on functional partitioning such as lower-layer functional partitioning. In such architectures, RU340s may be implemented to handle over-the-air (OTA) communication with one or more UE120s. In some implementations, real-time and non-real-time modes of control plane and user plane communication with RU340s may be controlled by the corresponding DU330s. In some scenarios, this configuration could allow the DU(or CU)330 and CU310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0058]

[0067] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that can be managed via an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 390) and perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU310, DU330, RU340, and quasi-RT RIC325. In some implementations, the SMO framework 305 may communicate with 4G RAN hardware embodiments such as the Open eNB (O-eNB) 311 via the O1 interface. Additionally, in some implementations, the SMO framework 305 may communicate directly with one or more RU340s via the O1 interface. The SMO framework 305 may also include a non-RT RIC315 configured to support the functionality of the SMO framework 305.

[0059]

[0068] Non-RT RIC315 may be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance for applications / features in quasi-RT RIC325. Non-RT RIC315 may be coupled to quasi-RT RIC325 or communicate with quasi-RT RIC325 (e.g., via the A1 interface). Quasi-RT RIC325 may be configured to include logical functions that enable quasi-real-time control and optimization of RAN elements and resources through data acquisition and actions via an interface connecting to quasi-RT RIC325 (e.g., via the E2 interface) using one or more CU310s, one or more DU330s, or both, and O-eNBs.

[0060]

[0069] In some implementations, the non-RT RIC315 may receive parameters or external enrichment information from an external server to generate an AI / ML model that will be deployed to the quasi-RT RIC325. Such information may be used by the quasi-RT RIC325 and may be received from a non-network data source or from a network function in the SMO framework 305 or the non-RT RIC315. In some embodiments, the non-RT RIC315 or quasi-RT RIC325 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC315 may monitor long-term trends and patterns in performance and employ an AI / ML model to take corrective action through the SMO framework 305 (e.g., reconfiguration via O1) or through the creation of a RAN management policy (e.g., an A1 policy).

[0061]

[0070] As shown above, Figure 3 is provided as one embodiment. Other embodiments may differ from those described with respect to Figure 3.

[0062]

[0071] Figure 4 shows embodiments 400, 410, and 420 of the Channel State Information (CSI) Reference Signal (CSI-RS) beam management procedure according to the present disclosure. As shown in Figure 4, embodiments 400, 410, and 420 include a UE 120 communicating with a base station 110 in a wireless network (e.g., wireless network 100). However, the devices shown in Figure 4 are provided as examples, and the wireless network may support communication and beam management between other devices (e.g., between the UE 120 and the base station 110 or a Transmit Receive Point (TRP), between a mobile termination node and a control node, between an integrated access and backhaul (IAB) child node and an IAB parent node, and / or between a scheduled node and a scheduling node). In some embodiments, the UE 120 and the base station 110 may be in a connected state (e.g., an RRC connected state).

[0063]

[0072] As shown in Figure 4, Embodiment 400 may include a base station 110 and a UE 120 that communicate to perform beam management using CSI-RS. Embodiment 400 describes a first beam management procedure (e.g., P1 CSI-RS beam management). The first beam management procedure may be referred to as a beam selection procedure, an initial beam acquisition procedure, a beam sweep procedure, a cell search procedure, and / or a beam search procedure. As shown in Figure 4 and Embodiment 400, the CSI-RS may be configured to be transmitted from the base station 110 to the UE 120. The CSI-RS may be configured to be periodic (e.g., using RRC signaling), semi-persistent (e.g., using Media Access Control (MAC) Control Element (MAC CE) signaling), and / or aperiodic (e.g., using Downlink Control Information (DCI)).

[0064]

[0073] The first beam management procedure may include the base station 110 performing a beam sweep across multiple transmit (Tx) beams. The base station 110 may use each transmit beam to transmit a CSI-RS for beam management. To enable the UE 120 to perform a receive (Rx) beam sweep, the base station may use the transmit beams to transmit each CSI-RS multiple times (e.g., using iterations) within the same RS resource set so that the UE 120 can sweep through the receive beams in multiple transmit instances. For example, if the base station 110 has N sets of transmit beams and the UE 120 has M sets of receive beams, the CSI-RS may be transmitted M times in each of the N transmit beams so that the UE 120 can receive M instances of the CSI-RS for each transmit beam. In other words, for each transmit beam of the base station 110, the UE 120 may perform a beam sweep through the receive beam of the UE 120. As a result, the first beam management procedure may allow UE120 to measure CSI-RS on different transmit beams using different receive beams to support the selection of beam pairs(s) of base station 110 transmit beam / UE120 receive beam(s). UE120 may report the measurements to base station 110 to enable base station 110 to select one or more beam pairs(s) for communication between base station 110 and UE120. Although Embodiment 400 is described in relation to CSI-RS, the first beam management process may also use Synchronization Signal Blocks (SSBs) for beam management in a manner similar to that described above.

[0065]

[0074] As shown in Figure 4, Embodiment 410 may include a base station 110 and a UE 120 that communicate to perform beam management using CSI-RS. Embodiment 410 describes a second beam management procedure (e.g., P2 CSI-RS beam management). The second beam management procedure may be referred to as a beam fine-tuning procedure, a base station beam fine-tuning procedure, a TRP beam fine-tuning procedure, and / or a transmit beam fine-tuning procedure. As shown in Figure 4 and Embodiment 410, the CSI-RS may be configured to be transmitted from base station 110 to UE 120. The CSI-RS may be configured to be aperiodic (e.g., using DCI). The second beam management procedure may include base station 110 performing a beam sweep over one or more transmit beams. The one or more transmit beams may be a subset of all transmit beams associated with base station 110 (determined, for example, on at least in part, measurements reported by UE 120 in connection with the first beam management procedure). The base station 110 may transmit CSI-RS using each of one or more transmit beams for beam management. The UE 120 may measure each CSI-RS using a single (e.g., the same) receive beam (determined, for example, at least in part, on measurements performed with respect to the first beam management procedure). The second beam management procedure may enable the base station 110 to select the best transmit beam, at least in part, on the CSI-RS measurements reported by the UE 120 (e.g., measured by the UE 120 using a single receive beam).

[0066]

[0075] As shown in Figure 4, Embodiment 420 describes a third beam management procedure (e.g., P3 CSI-RS beam management). The third beam management procedure may be referred to as a beam fine-tuning procedure, a UE beam fine-tuning procedure, and / or a receive beam fine-tuning procedure. As shown in Figure 4 and Embodiment 420, one or more CSI-RSs may be configured to be transmitted from base station 110 to UE 120. The CSI-RSs may be configured to be aperiodic (e.g., using DCI). The third beam management process may include base station 110 transmitting one or more CSI-RSs using a single transmit beam (determined, for example, on at least in part, measurements reported by UE 120 in relation to the first and / or second beam management procedures). To enable UE120 to perform a receive beam sweep, the base station may transmit the CSI-RS multiple times (e.g., using iterations) using the transmit beam within the same RS resource set, so that UE120 can sweep through one or more receive beams in multiple transmit instances. One or more receive beams may be a subset of all receive beams associated with UE120 (determined, for example, on at least partly based on measurements performed in connection with a first beam management procedure and / or a second beam management procedure). A third beam management procedure may enable base station 110 and / or UE120 to select the best receive beam (e.g., of the CSI-RS of the transmit beam using one or more receive beams) on at least partly based on reported measurements received from UE120.

[0067]

[0076] The UE120 may provide CSI feedback in a codebook used as a Precoding Matrix Indicator (PMI) dictionary, which allows the UE120 to report the best PMI (Precoding Matrix Indicator) codeword. The UE120 may use a bit sequence to report the PMI. Machine learning (e.g., Artificial Intelligence, AI) may be used to generate the CSI feedback, and the CSI encoder and / or CSI decoder may replace the codebook with machine learning-based CSI feedback. The CSI encoder may be analogous to a PMI search algorithm, and the CSI decoder may be analogous to a PMI codebook used to translate the CSI reporting bits into PMI codewords.

[0068]

[0077] The CSI encoder uses the downlink channel matrix (H), transmit covariance matrix, downlink precoder (V), and interference covariance matrix (R). nn The CSI decoder may have raw vs. whitened downlink channels as inputs, and / or output them.

[0069]

[0078] For optimized CSI-RS-based channel estimation, N ports may be multiplexed in N resource elements (REs) for each resource block (RB) using time division multiplexing (TDM), code division multiplexing (CDM), and / or frequency division multiplexing (FDM). The RB density may be 1 or 0.5 (transmitted every two RBs). Using AI-based CSI-RS optimization, the N ports may be multiplexed in L REs, where L is less than N. The RB density may be reduced to less than 0.5, and non-uniform RB patterns may be considered. The UE may use an AI-based channel estimation module to perform channel estimation. The base station 110 may use an AI-based CSI-RS transmitter to multiplex the N ports in L REs within each RB. In both cases, the channels are used for training. Machine learning models may be trained on generated synthetic data or data collected over the radio (OTA). Real-world collected data is preferred as it includes the effects of radio frequency (RF). Network entities (e.g., gNBs) may transmit CSI-RS with full density, and UEs may perform channel estimation and upload the data as ground truth for CSI feedback or for CSI-RS optimization and channel estimation.

[0070]

[0079] However, it is not specified how the reference signal is configured for this data acquisition, or how the data acquisition is triggered or activated.

[0071]

[0080] As shown above, Figure 4 is provided as one embodiment of the beam management procedure. An embodiment of the beam management procedure may differ from that described with respect to Figure 4. For example, UE120 and base station 110 may perform a third beam management procedure before performing a second beam management procedure, and / or UE120 and base station 110 may perform a similar beam management procedure to select the UE transmit beam.

[0072]

[0081] Figure 5 is a diagram illustrating one embodiment 500 associated with data collection for training a machine learning model according to the present disclosure. As shown in Figure 5, network entities 510 (e.g., base station 110) and UE 520 (e.g., UE 120) may communicate with each other in a wireless network (e.g., wireless network 100).

[0073]

[0082] According to various embodiments described herein, a UE may collect data for training a machine learning model based on a trigger or activation command that indicates data collection is permitted (determining when the UE should start) or that data collection should be started (the UE is commanded to start). A reference signal dedicated to data collection may also trigger data collection. Data collection may also be initiated based on information in a CSI reporting message (e.g., a trigger, an activation command) or a change in the CSI reporting mode. Data collection may also be deactivated by another message indicating that data collection is no longer permitted. By specifying when data collection should start, the UE and network may use real-world data more efficiently to train a machine learning model without interfering with other operations of the UE.

[0074]

[0083] Example 500 illustrates the configuration and activation of a reference signal for data acquisition. In some embodiments, as shown by reference no. 525, the network entity 510 may transmit a configuration for a reference signal used for data acquisition via MAC CE, Downlink Control Information (DCI), or RRC messages (e.g., CSI-RS-ResourceConfigDataCollection). The configuration may specify a reference signal dedicated to data acquisition. The configuration may include or specify a list of cell or carrier identifiers (IDs) and / or resources or reference signals (e.g., CSI-RS), where each resource is identified by an ID or tag. UE520 may receive a reference resource for each resource ID and cell ID and then perform measurements. UE520 may also append the resource ID and cell ID or carrier ID when uploading data to a data server to train a machine learning model. As shown by Example 500, each resource may correspond to a specific antenna mapping or antenna layout. The configuration may include a data acquisition ID or metadata ID. The metadata ID may include beam information associated with transmitting a reference signal and / or antenna configuration associated with transmitting a reference signal. The configuration may also include a frequency bandwidth type and a time domain type. The time domain type may be periodic (with periodicity and slot offset), semi-permanent (with periodicity and slot offset), or aperiodic. The configuration may include a reference signal pattern and / or reference signal density. The configuration may also include quasi-co-location (QCL) information and / or bandwidth part (BWP) information.

[0075]

[0084] In some embodiments, the reference signal may be an existing reference signal, but the RRC message may be new. For example, a new RRC field may be exclusive to the CSI-RS-ResourceConfigDataCollection and may include a CSI-RS resource configuration ID, cell ID or carrier ID, BWP ID, resource mapping configuration, and / or metadata ID. In some embodiments, the RRC field may be added to the CSI-RS instruction signaling. For example, a Non-Zero Power (NZP)-CSI-RS-ResourceSet Information Element (IE) may add a data acquisition process ID or metadata ID. In some embodiments, the network entity 510 may define a new type of reference signal for training a reference signal (having a new resource mapping pattern different from an existing reference signal), or a new ZP-CSI-RS pattern for rate matching a reference signal (having the embodiments described above).

[0076]

[0085] As indicated by reference number 530, network entity 510 may transmit a first message. Network entity 510 may transmit the first message via MAC CE or DCI. The first message may be a trigger or activation message indicating that data acquisition based on a reference signal is permitted. In some embodiments, if the reference signal is a dedicated reference signal for data acquisition, the first message may be a trigger or activation of the reference signal, and UE 520 may start data acquisition.

[0077]

[0086] As indicated by reference number 535, upon receiving an activation message for data acquisition (e.g., for a dedicated reference signal), UE 520 may initiate data acquisition. In some embodiments, if the dedicated reference signal configured for data acquisition is periodic, the RRC message constituting the reference signal for data acquisition may activate the periodic reference signal and data acquisition. In some embodiments, if the dedicated reference signal configured for data acquisition is semi-persistent, MAC CE may activate and deactivate the semi-persistent reference signal, and MAC CE may activate and deactivate data acquisition based at least partially on the dedicated semi-persistent reference signal. In some embodiments, network entity 510 may use a new field in the DCI (e.g., uplink DCI, downlink DCI, or group common DCI) to trigger data acquisition based at least partially on the dedicated reference signal for data acquisition. A group-wide DCI may include a list of reference signal IDs (e.g., TrainingRS-ID or CSI-RS-ResourceDataCollection-ID) to trigger the data acquisition process for a group of UEs as a whole. Individual UEs may be configured (via RRC) with respect to which fields are read from the list or which data acquisition reference signals are triggered for their respective UEs. When these reference signals are activated, data acquisition can be activated, as the reference signals may be dedicated to data acquisition.

[0078]

[0087] As indicated by reference number 540, the network entity 510 may transmit a reference signal. In some embodiments, the UE 520 may detect that the reference signal is a dedicated reference signal configured for data acquisition and may initiate data acquisition. Configuration may assist the UE 520 in identifying or detecting the dedicated reference signal. The UE 520 may rate match or assign modulated bits to resources around the dedicated reference signal for data acquisition.

[0079]

[0088] As indicated by reference number 545, UE520 may collect data if it is permitted to collect data. This may include obtaining channel measurements of a reference signal. As indicated by reference number 550, UE520 may upload data to a data server for use in training a machine learning model for channel estimation or to construct a reference signal or other reference signals. The data server may be a UE server that communicates with a network entity (e.g., a model repository).

[0080]

[0089] In some embodiments, as indicated by reference no. 555, the network entity 510 may send a deactivation message indicating that data collection is no longer permitted. The UE 520 may stop collecting data. The UE 520 may send the collected data before or after receiving the deactivation message.

[0081]

[0090] As shown above, Figure 5 is provided as one embodiment. Other embodiments may differ from those described with respect to Figure 5.

[0082]

[0091] Figure 6 shows one example 600 of data collection for training a machine learning model according to the present disclosure.

[0083]

[0092] In some embodiments, data acquisition may be based on non-dedicated reference signals, and data acquisition trigger or activation messages (e.g., MAC CE, DCI) may trigger or activate data acquisition based on these reference signals. Example 600 shows an activation message 602 for semi-persistent (SP) CSI-RS. CSI-RS may be used for normal CSI reporting. Example 600 also shows a data acquisition activation message 604 (e.g., MAC CE) indicating that data acquisition based on already activated semi-persistent CSI-RS is permitted by UE520. Activation message 604 may include the cell ID or carrier ID of a reference signal resource (e.g., CSI-RS resource) and / or related reference signal resource (e.g., CSI-RS), or a resource set for data acquisition (indicated by a resource ID or resource set ID). Each resource may correspond to a specific antenna mapping or antenna layout (implicit communication). The UE520 may collect data from the CSI-RS. Data collection may be configured for machine learning purposes, and / or the collected data may be formatted. Activation message 604 may include a metadata ID. The metadata ID may include beam information associated with transmitting the reference signal, and / or antenna configuration associated with transmitting the reference signal.

[0084]

[0093] In some embodiments, if the reference signal has not yet been activated, the reference signal may be activated or deactivated along with the data acquisition procedure (same MAC CE). If the reference signal has already been activated for other purposes, such as for CSI reporting, the UE520 may stop the current process and begin collecting data to train a machine learning model. In some embodiments, if the reference signal has already been used for data acquisition, the UE may stop data acquisition if a non-periodic CSI reporting is triggered and this reference signal is used as a measurement resource.

[0085]

[0094] In some embodiments, the activation message 604 may include bits for toggling the activation or deactivation (suspension) of data acquisition based on the respective reference signals associated with the activation message 604. The network entity 510 may change the antenna mapping to indicate that the UE 520 will suspend the reference signal measurement for data acquisition. In the event of suspension, the UE 520 may refrain from acquiring data for a specified period of time.

[0086]

[0095] In some embodiments, to trigger or activate data acquisition based on a reference signal, the network entity 510 may transmit a group common DCI including multiple segments. The group common DCI may trigger data acquisition globally for a group of UEs. Each segment may include one or more triplets, each triplet including at least one of a cell ID or carrier ID, a metadata ID, or a resource ID or resource set ID. In some embodiments, the group common DCI may include a list of segments, including a list of cell IDs or carrier IDs, a list of metadata IDs, and a list of resource IDs or resource set IDs. Each entry in the list may have a one-to-one-to-one mapping across the list (cell ID or carrier ID vs. metadata ID vs. resource ID or resource set ID). In some embodiments, each segment of the group common DCI may include a data acquisition request that activates a trigger state from a pre-configured trigger state list (via RRC). Each trigger state may have multiple triplets, each triplet including a cell ID or carrier ID, a metadata ID, and / or a resource ID or resource set ID.

[0087]

[0096] When the DCI is a group-wide DCI, individual UEs (e.g., UE520) may receive instructions (via RRC) on which segmentation in the DCI the UE520 should read. This may include which triplets to read, which components in a list to read, or which requests to read. The UE520 may determine the triplets, components, and / or requests by the starting bit or field to read and the length of the bit or field to read. This means that each UE will know which reference signal resources, their carrier IDs or cell IDs, and their metadata IDs should be used for data acquisition.

[0088]

[0097] In some embodiments, in the case of a group-common DCI scheme, the UE520 may be activated for data acquisition if the DCI is scrambled by a first sequence such as a data acquisition-activating radio network temporary identifier (RNTI). The UE520 may be deactivated for data acquisition if the DCI is scrambled by a second sequence such as a data acquisition-deactivating RNTI. In some embodiments, the group-common DCI is scrambled by a data acquisition RNTI, and bits or DCI code points may be used to indicate the activation or deactivation of data acquisition in each segmentation.

[0089]

[0098] In some embodiments, a UE-specific DCI may be used to activate or deactivate data collection. Each UE may provide a single triplet or a single request via a UE-specific downlink DCI or a UE-specific uplink DCI. A UE-specific DCI may include multiple segmentations. Each segmentation may include one or more triplets, each triplet including at least one of a cell ID or carrier ID, a metadata ID, or a resource ID or resource set ID. In some embodiments, a UE-specific DCI may include a list of segmentations, which may include a list of cell IDs or carrier IDs, a list of metadata IDs, and a list of resource IDs or resource set IDs. Each entry in the list may have a one-to-one-to-one mapping across the entire list. In some embodiments, each segmentation may include a data collection request that activates a trigger state from a pre-configured trigger state list. Each trigger state may have multiple triplets, each triplet including a cell ID or carrier ID, a metadata ID, and / or a resource ID or resource set ID. When an aperiodic reference signal is used for either a group common DCI or a UE-specific DCI, the aperiodic reference signal may be triggered using a DCI or other message.

[0090]

[0099] In some embodiments, the configuration of the reference signal resource for data collection may also constitute a dedicated report for data collection (e.g., a CSI report). This may include, for example, setting the reporting amount to "none" or "data-collection" (but without Layer 1 reporting). This means that the CSI-RS resource associated with this CSI report is used for data collection.

[0091]

[0100] In some embodiments, as shown in Example 610, the configuration may include a bit or mode flag indicating that the CSI report is set to data acquisition mode. When in data acquisition mode, the CSI-RS resource associated with this CSI report is used for data acquisition. A trigger or activation message may trigger a CSI report dedicated to data acquisition or a CSI report for data acquisition mode. The message may indicate that the CSI feedback (CSF) mode is being changed from normal CSI reporting to data acquisition, or both CSI reporting and data acquisition. The mode change may be via DCI or MAC CE. If the UE520 determines that the reference signal for the CSI report is for data acquisition, the UE520 may determine when to upload the data.

[0092]

[0101] In the case of CSI reporting, the Central Process Unit (CPU) count may be one CPU per resource. The active resource count may be one CPU per resource. In some embodiments, a mode flag may be included in the legacy reporting (e.g., CSI reporting) configuration to dynamically change the amount of reporting.

[0093]

[0102] In some embodiments, data acquisition may occupy one CPU per resource from the start of the data acquisition activation instruction until its release. For active resources or ports, data acquisition may occupy one active resource per resource and P active ports, where P is the number of ports per resource for data acquisition. Counting may begin from the start of the data acquisition activation instruction until its release. The UE520 may report the UE's capacity for resource use. The UE520 may report a list of the number of ports per resource, the maximum number of resources, and / or the maximum total number of ports per bandwidth or band combination (BC), and report that the UE520 is capable of handling data acquisition. The UE520 may further report the quantity for simultaneous processing of data acquisition with other CSIs (for each bandwidth and BC report). An alternative approach for active resource reporting and capacity reporting may include the UE520 reporting its processing capacity. This may include a maximum of N resources and P total ports for data collection per slot, the number of configured resources and ports that must comply with this capability, and / or the amount of data collection process.

[0094]

[0103] When the UE520 uses a reference signal for data acquisition, long periodicity leads to inefficient data acquisition, while short periodicity leads to more data. The UE520 may not be able to handle all data acquisitions frequently, which could be a waste of reference signal overhead. In some embodiments, the configuration may specify the periodicity of the reference signal for data acquisition. The UE520 may report its UE capability to support data acquisition, including the supported periodicities. The network entity 510 may configure the periodicity of the reference signal based at least in part on the UE capability. In some embodiments, it may be up to the UE520 when or on which reference signal occasions data acquisition should be performed. It may also be up to the UE520 when the acquired data (e.g., measured data) is uploaded.

[0095]

[0104] When network entity 510 constitutes a reference signal, network entity 510 may adhere to the UE capability (i.e., not constitute any periodicity smaller than that indicated by UE 520). For example, if UE 520 reports the capability to handle a reference signal periodicity of 10 milliseconds (ms), network entity 510 may constitute a reference signal with a periodicity greater than 10 milliseconds.

[0096]

[0105] As shown above, Figure 6 is provided as one embodiment. Other embodiments may differ from those described with respect to Figure 6.

[0097]

[0106] Figure 7 shows an exemplary process 700 performed by, for example, a UE according to the present disclosure. The exemplary process 700 is an embodiment in which a UE (e.g., UE120, UE520) performs operations associated with acquiring reference signal data for training a machine learning model.

[0098]

[0107] As shown in Figure 7, in some embodiments, process 700 may include receiving a first message indicating that a configuration for a reference signal to be used for data acquisition and / or data acquisition based on the reference signal is permitted (block 710). For example, a UE (using, for example, the communication manager 908 and / or receiving component 902 depicted in Figure 9) may receive a first message indicating that a configuration for a reference signal to be used for data acquisition and / or data acquisition based on the reference signal is permitted, as described above.

[0099]

[0108] As further shown in Figure 7, in some embodiments, process 700 may include receiving a reference signal (block 720). For example, the UE may receive the reference signal (for example, using the communication manager 908 and / or receiving component 902 depicted in Figure 9) as described above.

[0100]

[0109] As further shown in Figure 7, in some embodiments, process 700 may include collecting data based at least partially on a reference signal (block 730). For example, the UE (using, for example, the communication manager 908 and / or data acquisition component 910 depicted in Figure 9) may collect data based at least partially on a reference signal, as described above.

[0101]

[0110] As further shown in Figure 7, in some embodiments, process 700 may include transmitting the collected data (block 740). For example, the UE may transmit the collected data (using, for example, the communication manager 908 and / or transmission component 904 depicted in Figure 9) as described above.

[0102]

[0111] Process 700 may include additional embodiments, such as any single embodiment or any combination of embodiments described below with respect to one or more other processes described elsewhere in this Specification.

[0103]

[0112] In the first aspect, process 700 includes receiving a second message indicating that data collection is not permitted, and stopping data collection at least in part based on the second message.

[0104]

[0113] In the second embodiment, data collection, either alone or in combination with the first embodiment, includes collecting channel measurements based on a reference signal.

[0105]

[0114] In the third embodiment, the data is associated with machine learning for channel estimation or reference signal construction, either alone or in combination with one or more of the first and second embodiments.

[0106]

[0115] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the configuration specifies that the reference signal is a dedicated reference signal for data acquisition, and the acquisition of data includes acquiring data in accordance with the fact that the reference signal is a dedicated reference signal.

[0107]

[0116] In the fifth aspect, the first message activates a dedicated reference signal, either alone or in combination with one or more of the first to fourth aspects.

[0108]

[0117] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the configuration specifies one or more of the following: a cell ID or carrier ID, one or more reference resource IDs, a metadata ID, or a resource mapping configuration for a reference resource ID.

[0109]

[0118] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the metadata ID includes beam information associated with transmitting a reference signal, or one or more antenna configurations associated with transmitting a reference signal.

[0110]

[0119] In the eighth aspect, receiving the first message, either alone or in combination with one or more of the first to seventh aspects, includes receiving the first message within MAC CE or DCI.

[0111]

[0120] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the MAC CE includes one or more of the following: a cell ID or carrier ID, an associated reference resource ID, a metadata ID, or bits indicating whether the MAC CE is for activation or deactivation.

[0112]

[0121] In the tenth aspect, the DCI includes, either alone or in combination with one or more of the first to ninth aspects, one or more triplets, each containing one or more of a cell ID or carrier ID, a metadata ID, or a resource ID or resource set ID.

[0113]

[0122] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the DCI includes one or more of the following: a list of cell IDs or carrier IDs, a list of metadata IDs, or a list of resource IDs or resource set IDs, with a one-to-one mapping between entries across the lists.

[0114]

[0123] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the DCI includes a list of trigger states, each trigger state includes a plurality of triplets, each triplet includes a cell ID or carrier ID, a metadata ID, and a resource ID or resource set ID.

[0115]

[0124] In the 13th aspect, the DCI is either alone or in combination with one or more of the first to 12th aspects, comprising a data acquisition activated RNTI and a scrambled activated DCI.

[0116]

[0125] In the 14th aspect, either alone or in combination with one or more of the first to 13th aspects, the process 700 includes receiving a deactivated DCI scrambled by a data acquisition deactivation RNTI, and stopping data acquisition in response to the deactivated DCI.

[0117]

[0126] In the 15th aspect, either alone or in combination with one or more of the first to 14th aspects, the DCI is a group common DCI, and process 700 receives a radio resource control message indicating which triplet, which entry in a list, or which trigger state is used to indicate the activation or deactivation of data collection.

[0118]

[0127] In the sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, the DCI is a group-common DCI, and the activation or deactivation of data collection is indicated by bits in each segment.

[0119]

[0128] In the 17th aspect, either alone or in combination with one or more of the first to 16th aspects, the configuration designates a CSI report dedicated to data acquisition, and process 700 determines that the reference signal for the CSI report is for data acquisition.

[0120]

[0129] In the 18th aspect, either alone or in combination with one or more of the first to 17th aspects, the configuration includes a bit or flag that designates a CSI report and indicates that the CSI report is set to data acquisition mode, and the process 700 includes determining that the reference signal for the CSI report is for data acquisition.

[0121]

[0130] In the 19th aspect, the first message activates or triggers a CSI report dedicated to data collection or a CSI report for a data collection mode, either alone or in combination with one or more of the first to 18th aspects.

[0122]

[0131] In the 20th aspect, either alone or in combination with one or more of the first to 19th aspects, the first message indicates that the CSI feedback mode is being changed to nominal CSI reporting, data collection, or both.

[0123]

[0132] In the 21st aspect, the process 700 includes, either alone or in combination with one or more of the first to 20th aspects, occupying at least one processing unit for each reference signal resource to collect data.

[0124]

[0133] In the 22nd aspect, collecting data, either alone or in combination with one or more of the first to 21st aspects, occupies one or more of the number of ports per reference signal resource, the amount of reference signal resources, the total number of ports, or any combination thereof.

[0125]

[0134] In the 23rd aspect, either alone or in combination with one or more of the first to 22nd aspects, process 700 includes transmitting UE capabilities to support data acquisition, the UE capabilities specifying support for one or more of the periodicity of the data acquisition reference signal, the number of ports per resource, the maximum amount of resources, the maximum total number of ports, the number of processing units, or the number of data acquisition processes.

[0126]

[0135] Figure 7 shows an exemplary block of process 700, but in some embodiments, process 700 may include additional blocks, fewer blocks, different blocks, or blocks configured differently from those shown in Figure 7. Additionally or alternatively, two or more blocks of process 700 may be executed in parallel.

[0127]

[0136] Figure 8 is a diagram illustrating an exemplary process 800 performed by, for example, a network entity according to the present disclosure. The exemplary process 800 is an embodiment in which a network entity (e.g., network entity 510) performs operations associated with collecting reference signal configuration data for training a machine learning model.

[0128]

[0137] As shown in Figure 8, in some embodiments, process 800 may include sending a first message indicating that a configuration for a reference signal to be used for data acquisition and / or data acquisition based on the reference signal is permitted (block 810). For example, a network entity (for example, using the communication manager 1008 and / or the transmission component 1004 depicted in Figure 10) may send a first message indicating that a configuration for a reference signal to be used for data acquisition and / or data acquisition based on the reference signal is permitted, as described above.

[0129]

[0138] As further shown in Figure 8, in some embodiments, process 800 may include transmitting a reference signal (block 820). For example, a network entity (for example, using the communication manager 1008 and / or transmitting component 1004 depicted in Figure 10) may transmit a reference signal as described above.

[0130]

[0139] Process 800 may include additional embodiments, such as any single embodiment or any combination of embodiments, described below with respect to one or more other processes described elsewhere in this Specification.

[0131]

[0140] In the first aspect, process 800 includes using data to train a machine learning model for channel estimation or reference signal construction.

[0132]

[0141] In a second embodiment, process 800 includes sending a second message indicating that data collection is not permitted, either alone or in combination with the first embodiment.

[0133]

[0142] In the third aspect, either alone or in combination with one or more of the first and second aspects, the configuration specifies that the reference signal is a dedicated reference signal for data acquisition.

[0134]

[0143] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the configuration specifies one or more of the following: a cell ID or carrier ID, one or more reference resource IDs, a metadata ID, or a resource mapping configuration for a reference resource ID.

[0135]

[0144] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 800 includes receiving instructions for UE capabilities to support data collection, and the configuration is at least partially based on UE capabilities.

[0136]

[0145] Figure 8 shows an exemplary block of process 800, but in some embodiments, process 800 may include additional blocks, fewer blocks, different blocks, or blocks configured differently from those depicted in Figure 8. Additionally or alternatively, two or more blocks of process 800 may be executed in parallel.

[0137]

[0146] Figure 9 illustrates an exemplary device 900 for wireless communication. The device 900 may be a UE (e.g., UE120, UE520), or a UE may include the device 900. In some embodiments, the device 900 includes a receiving component 902 and a transmitting component 904 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the device 900 may use the receiving component 902 and the transmitting component 904 to communicate with another device 906 (such as a UE, a base station, or another wireless communication device). As further shown, the device 900 may include a communications manager 908. The communications manager 908 may control and / or manage the operation of one or more of the receiving component 902 and / or the transmitting component 904. In some embodiments, the communication manager 908 may include one or more antennas, modems, controllers / processors, memory, or combinations thereof of the UE described in relation to Figure 2. The communication manager 908 may be the communication manager 140 depicted in Figures 1 and 2, or similar. For example, in some embodiments, the communication manager 908 may be configured to perform one or more of the functions described as being performed by the communication manager 140. In some embodiments, the communication manager 908 may include a receiving component 902 and / or a transmitting component 904. In some embodiments, the communication manager 908 may include a data acquisition component 910, among other examples.

[0138]

[0147] In some embodiments, the device 900 may be configured to perform one or more operations described herein with respect to Figures 1 to 6. Additionally or alternatively, the device 900 may be configured to perform one or more processes described herein, such as process 700 in Figure 7. In some embodiments, the device 900 and / or one or more components shown in Figure 9 may include one or more components of the UE described in relation to Figure 2. Additionally or alternatively, one or more components shown in Figure 9 may be implemented within one or more components described in relation to Figure 2. Additionally or alternatively, one or more components of a set of components may be implemented at least partially as software stored in memory. For example, a component (or part of a component) may be implemented as instructions or code stored in a non-temporary computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0139]

[0148] The receiving component 902 may receive communications from the device 906, such as reference signals, control information, data communications, or a combination thereof. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some embodiments, the receiving component 902 may perform signal processing on the received communications (among other examples, filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and provide the processed signals to one or more other components of the device 900. In some embodiments, the receiving component 902 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memory, or a combination thereof, of the UE described in relation to Figure 2.

[0140]

[0149] The transmitting component 904 may transmit communications such as reference signals, control information, data communications, or combinations thereof to the device 906. In some embodiments, one or more other components of the device 900 may generate communications and provide the generated communications to the transmitting component 904 for transmission to the device 906. In some embodiments, the transmitting component 904 may perform signal processing on the generated communications (among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding) and transmit the processed signals to the device 906. In some embodiments, the transmitting component 904 may include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memory, or combinations thereof of the UE described with respect to Figure 2. In some embodiments, the transmitting component 904 may collate with the receiving component 902 in the transceiver.

[0141]

[0150] The receiving component 902 may receive a first message indicating that it is configured for a reference signal to be used for data acquisition, and / or that data acquisition based on the reference signal is permitted. The receiving component 902 may receive the reference signal. The data acquisition component 910 may acquire data based at least in part on the reference signal. The transmitting component 904 may transmit the acquired data.

[0142]

[0151] The receiving component 902 may receive a second message indicating that data collection is not permitted. The data collection component 910 may stop data collection based at least in part on the second message.

[0143]

[0152] The receiving component 902 may receive a deactivated DCI scrambled by a data acquisition deactivation RNTI. The data acquisition component 910 may stop data acquisition in response to the deactivated DCI. The data acquisition component 910 may occupy at least one processing unit for each reference signal resource for data acquisition.

[0144]

[0153] The transmitting component 904 may transmit UE capabilities to support data acquisition, where the UE capabilities specify support for one or more of the following: periodicity of the data acquisition reference signal, number of ports per resource, maximum amount of resources, maximum total number of ports, number of processing units, or number of data acquisition processes.

[0145]

[0154] The number and arrangement of components shown in Figure 9 are provided as an embodiment. In practice, additional components, fewer components, different components, or components arranged differently from those shown in Figure 9 may exist. Furthermore, two or more components shown in Figure 9 may be implemented within a single component, or a single component shown in Figure 9 may be implemented as multiple distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 9 may perform one or more functions described as being performed by another set of components shown in Figure 9.

[0146]

[0155] Figure 10 is a diagram of an exemplary device 1000 for wireless communication. The device 1000 may be a network entity (e.g., base station 110, network entity 510), or a network entity may include the device 1000. In some embodiments, the device 1000 includes a receiving component 1002 and a transmitting component 1004 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the device 1000 may use the receiving component 1002 and the transmitting component 1004 to communicate with another device 1006 (such as a UE, base station, or another wireless communication device). As further shown, the device 1000 may include a communications manager 1008. The communications manager 1008 may control and / or manage the operation of one or more of the receiving component 1002 and / or the transmitting component 1004. In some embodiments, the communication manager 1008 may include one or more antennas, modems, controllers / processors, memory, or combinations thereof of the network entities described in relation to Figure 2. The communication manager 1008 may be the communication manager 150 depicted in Figures 1 and 2, or similar thereto. For example, in some embodiments, the communication manager 1008 may be configured to perform one or more of the functions described as being performed by the communication manager 150. In some embodiments, the communication manager 1008 may include a receiving component 1002 and / or a transmitting component 1004. The communication manager 1008 may also include a configuration component 1010, among other examples.

[0147]

[0156] In some embodiments, the device 1000 may be configured to perform one or more operations described herein with respect to Figures 1 to 6. Additionally or alternatively, the device 1000 may be configured to perform one or more processes described herein, such as process 800 in Figure 8. In some embodiments, the device 1000, and / or one or more components shown in Figure 10, may include one or more components of the network entity described in relation to Figure 2. Additionally or alternatively, one or more components shown in Figure 10 may be implemented within one or more components described in relation to Figure 2. Additionally or alternatively, one or more components of a set of components may be implemented at least partially as software stored in memory. For example, a component (or part of a component) may be implemented as instructions or code stored in a non-temporary computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0148]

[0157] The receiving component 1002 may receive communications from the device 1006, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some embodiments, the receiving component 1002 may perform signal processing on the received communications (among other examples, filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and provide the processed signals to one or more other components of the device 1000. In some embodiments, the receiving component 1002 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memory, or a combination thereof of the network entities described with respect to Figure 2.

[0149]

[0158] The transmitting component 1004 may transmit communications such as reference signals, control information, data communications, or combinations thereof to the device 1006. In some embodiments, one or more other components of the device 1000 may generate communications and provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some embodiments, the transmitting component 1004 may perform signal processing on the generated communications (among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding) and transmit the processed signals to the device 1006. In some embodiments, the transmitting component 1004 may include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memory, or combinations thereof of the network entities described with respect to Figure 2. In some embodiments, the transmitting component 1004 may collate with the receiving component 1002 in a transceiver.

[0150]

[0159] The transmitting component 1004 may transmit a configuration for a reference signal used for data acquisition, and / or a first message indicating that data acquisition based on the reference signal is permitted. The structural component 1010 may generate a configuration based on UE capabilities, channel status, and / or traffic status. The transmitting component 1004 may transmit a reference signal.

[0151]

[0160] The transmitting component 1004 may transmit a second message indicating that data collection is not permitted. The receiving component 1002 may receive instructions for UE capability to support data collection, and the configuration may be at least partially based on UE capability.

[0152]

[0161] The number and arrangement of components shown in Figure 10 are provided as an embodiment. In practice, additional components, fewer components, different components, or components arranged differently from those shown in Figure 10 may exist. Furthermore, two or more components shown in Figure 10 may be implemented within a single component, or a single component shown in Figure 10 may be implemented as multiple distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 10 may perform one or more functions described as being performed by another set of components shown in Figure 10.

[0153]

[0162] The following provides an overview of some aspects of this disclosure.

[0163] Embodiment 1: A method of wireless communication performed by User Equipment (UE), the method comprising: receiving one or more of a configuration for a reference signal to be used for data acquisition, or a first message indicating that data acquisition based on such reference signal is permitted; receiving such reference signal; acquiring data at least in part based on such reference signal; and transmitting the acquired data.

[0154]

[0164] Embodiment 2: The method according to Embodiment 1, further comprising receiving a second message indicating that data collection is not permitted, and stopping data collection at least in part based on the second message.

[0155]

[0165] Embodiment 3: The method according to Embodiment 1 or 2, wherein collecting the data includes collecting channel measurements based on the reference signal.

[0156]

[0166] Embodiment 4: The method according to any one of Embodiments 1 to 3, wherein the data is associated with machine learning for channel estimation or reference signal construction.

[0157]

[0167] Embodiment 5: The method according to any one of Embodiments 1 to 4, wherein the configuration specifies that the reference signal is a dedicated reference signal for data acquisition, and the acquisition of said data includes acquiring said data in accordance with the fact that the reference signal is a dedicated reference signal.

[0158]

[0168] Embodiment 6: The method according to Embodiment 5, wherein the first message activates the dedicated reference signal.

[0159]

[0169] Embodiment 7: The method according to any one of Embodiments 1 to 6, wherein the configuration specifies one or more of the following: a cell identifier (ID) or a carrier identifier (ID), one or more reference resource IDs, metadata IDs, or a resource mapping configuration for a reference resource ID.

[0160]

[0170] Embodiment 8: The method according to Embodiment 7, wherein the metadata ID includes one or more of the following: beam information associated with transmitting the reference signal, or an antenna configuration associated with transmitting the reference signal.

[0161]

[0171] Embodiment 9: The method according to any one of Embodiments 1 to 8, wherein receiving the first message includes receiving the first message in a Medium Access Control Control Element (MAC CE) or Downlink Control Information (DCI).

[0162]

[0172] Embodiment 10: The method according to Embodiment 9, wherein the MAC CE includes one or more bits indicating whether the MAC CE is for activation or deactivation, such as a cell identifier (ID) or carrier identifier (ID), an associated reference resource ID, a metadata ID, or a bit indicating whether the MAC CE is for activation or deactivation.

[0163]

[0173] Embodiment 11: The method according to Embodiment 9, wherein the DCI comprises one or more triplets, each containing one or more of the following: a cell ID or carrier ID, a metadata ID, a resource ID, or a resource set ID.

[0164]

[0174] Embodiment 12: The method according to Embodiment 9, wherein the DCI includes one or more of the following: a list of cell IDs or carrier IDs, a list of metadata IDs, or a list of resource IDs or resource set IDs, and there is a one-to-one mapping between entries across the lists.

[0165]

[0175] Embodiment 13: The method according to Embodiment 9, wherein the DCI includes a list of trigger states, each trigger state includes a plurality of triplets, and each triplet includes a cell identifier (ID) or carrier identifier (ID), a metadata ID, and a resource ID or resource set ID.

[0166]

[0176] Embodiment 14: The method according to Embodiment 9, wherein the DCI is an activated DCI that has been scrambled by a Radio Network Temporary Identifier (RNTI).

[0167]

[0177] Embodiment 15: The method of Embodiment 14, further comprising receiving a deactivated DCI scrambled by a data collection deactivation RNTI, and stopping the collection of such data in response to the deactivated DCI.

[0168]

[0178] Embodiment 16: The method of Embodiment 9, wherein the DCI is a group-common DCI, and the method includes receiving a radio resource control message indicating which triplet, which entry in a list, or which trigger state is used to indicate the activation or deactivation of the collection of such data.

[0169]

[0179] Embodiment 17: The method according to Embodiment 9, wherein the DCI is a group-common DCI, and the activation or deactivation of the collection of the data is indicated by bits in each segment.

[0170]

[0180] Embodiment 18: The method according to any one of Embodiments 1 to 17, wherein the configuration specifies a channel state information (CSI) report dedicated to data acquisition, and the method includes determining that a reference signal for the CSI report is for data acquisition.

[0171]

[0181] Embodiment 19: The method according to any one of Embodiments 1 to 18, wherein the configuration includes a bit or flag indicating that the CSI report is set to data acquisition mode, and the method includes determining that the reference signal for the CSI report is for data acquisition.

[0172]

[0182] Embodiment 20: The method according to any one of embodiments 1 to 19, wherein the first message activates or triggers a channel status information (CSI) report dedicated to data acquisition or a CSI report for a data acquisition mode.

[0173]

[0183] Embodiment 21: The method according to any one of Embodiments 1 to 20, wherein the first message indicates that the channel status information (CSI) feedback mode is changed to nominal CSI reporting, data collection, or both.

[0174]

[0184] Embodiment 22: The method according to any one of embodiments 1 to 21, further comprising occupying at least one processing unit for each reference signal resource in order to collect the data.

[0175]

[0185] Embodiment 23: The method according to any one of Embodiments 1 to 22, wherein the collection of said data occupies one or more of the number of ports per reference signal resource, the amount of reference signal resources, the total number of ports, or a combination thereof.

[0176]

[0186] Embodiment 24: The method according to any one of embodiments 1 to 23, further comprising transmitting UE capabilities to support data acquisition, wherein the UE capabilities specify support for one or more of the following: periodicity of a data acquisition reference signal, number of ports per resource, maximum amount of resources, maximum total number of ports, number of processing units, or number of data acquisition processes.

[0177]

[0187] Embodiment 25: A method of wireless communication performed by a network entity, the method comprising: transmitting one or more of a configuration for a reference signal used for data acquisition, or a first message indicating that data acquisition based on such reference signal is permitted; transmitting such reference signal; and receiving data acquired at least in part based on such reference signal.

[0178]

[0188] Embodiment 26: The method according to Embodiment 25, further comprising using the data to train a machine learning model for channel estimation or reference signal construction.

[0179]

[0189] Embodiment 27: The method according to Embodiment 25 or 26, further comprising sending a second message indicating that data collection is not permitted.

[0180]

[0190] Embodiment 28: The method according to any one of Embodiments 25 to 27, wherein the configuration specifies that the reference signal is a dedicated reference signal for data acquisition.

[0181]

[0191] Embodiment 29: The method according to any one of Embodiments 25 to 28, wherein the configuration specifies one or more of the following: a cell identifier (ID) or a carrier identifier (ID), one or more reference resource IDs, metadata IDs, or a resource mapping configuration for a reference resource ID.

[0182]

[0192] Embodiment 30: The method according to any one of Embodiments 25 to 29, further comprising receiving instructions for UE capabilities to support data collection, wherein the configuration is at least partially based on such UE capabilities.

[0183]

[0193] Embodiment 31: A device for wireless communication in a device, the device comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, which are executable by the processor to cause the device to perform one or more of the methods of Embodiments 1 to 30.

[0184]

[0194] Embodiment 32: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, wherein the one or more processors are configured to perform one or more of the methods of Embodiments 1 to 30.

[0185]

[0195] Embodiment 33: A device for wireless communication, wherein the device comprises at least one means for performing one or more methods from Embodiments 1 to 30.

[0186]

[0196] Embodiment 34: A non-temporary computer-readable medium for storing code for wireless communication, wherein the code includes instructions that can be executed by a processor to perform one or more of the methods of Embodiments 1 to 30.

[0187]

[0197] Embodiment 35: A non-temporary computer-readable medium for storing a set of instructions for wireless communication, wherein the set of instructions comprises one or more instructions, and when the one or more instructions are executed by one or more processors of the device, the device causes the device to perform one or more of the methods of Embodiments 1 to 30.

[0188]

[0198] The above disclosures are illustrative and explanatory, but are not intended to be exhaustive or to limit the manner in which the manner is disclosed to the exact form. Modified and altered forms may be added in light of the above disclosures or derived from the practice of various manners.

[0189]

[0199] As used herein, the term “component” is intended to be broadly interpreted as hardware and / or combinations of hardware and software. “Software” is broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, “processor” is implemented in hardware and / or combinations of hardware and software. It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware and / or combinations of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limited to these embodiments. Therefore, a person skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the descriptions herein, so the operation and behavior of the system and / or method are described herein without reference to specific software code.

[0190]

[0200] As used herein, "satisfying a threshold" may, depending on the context, mean that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, or not equal to a threshold.

[0191]

[0201] Even if certain combinations of features are enumerated in the claims and / or disclosed herein, these combinations are not intended to limit the disclosure of various embodiments. Many of these features may be combined in ways not specifically enumerated in the claims and / or disclosed herein. The disclosure of various embodiments includes each dependent claim combined with any other claims in the set of claims. As used herein, the phrase “at least one of” an enumeration of items refers to any combination of those items, including a single member. As an embodiment, “at least one of: a, b, or c” shall encompass a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other order of a, b, and c).

[0192]

[0202] None of the elements, actions, or commands used herein should be construed as important or essential unless expressly stated herein. Furthermore, as used herein, the articles “a” and “an” refer to one or more items and may be used interchangeably with “one or more.” Additionally, as used herein, the article “the” refers to one or more items with respect to the article “the” and may be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” refer to one or more items and may be used interchangeably with “one or more.” When only one item is intended, the phrase “only one” or similar words should be used. Also, as used herein, terms such as “has,” “have,” and “having” are open-ended terms that do not limit the elements they modify (for example, an element that “has” A may also have B). Furthermore, unless otherwise specified, the phrase "based on" is intended to mean "based, at least in part, on." Also, as used herein, the term "or" is inclusive when used consecutively and may be used interchangeably with "and / or" unless otherwise specified (for example, when used in combination with "either" or "only one of"). The invention described in the original claims of this application is listed below. [C1] User equipment (UE) for wireless communication, Memory and The system comprises one or more processors coupled to the memory, and the one or more processors Receiving one or more of the following: a configuration for a reference signal used for data acquisition, or a first message indicating that data acquisition based on the reference signal is permitted. The aforementioned reference signal is received, Based at least partially on the aforementioned reference signal, data is collected, A UE configured to transmit the collected data. [C2] The one or more processors described above I received a second message indicating that data collection was not permitted. The UE described in C1 is configured to stop data collection based at least in part on the second message. [C3] The UE according to C1, wherein one or more processors are configured to collect channel measurements based on the reference signal in order to collect the data. [C4] The UE described in C1, wherein the data is associated with machine learning for channel estimation or reference signal construction. [C5] The UE according to C1, wherein the configuration specifies that the reference signal is a dedicated reference signal for data acquisition, and the one or more processors for acquiring the data acquire the data in accordance with the fact that the reference signal is a dedicated reference signal. [C6] The UE described in C5, wherein the first message activates the dedicated reference signal. [C7] The UE described in C1, wherein the configuration specifies one or more of the following: a cell identifier (ID) or a carrier identifier (ID), one or more reference resource IDs, metadata IDs, or a resource mapping configuration for the reference resource ID. [C8] The UE according to C7, wherein the metadata ID includes one or more of the following: beam information associated with transmitting the reference signal, or an antenna configuration associated with transmitting the reference signal. [C9] The UE according to C1, wherein one or more processors for receiving the first message are configured to receive the first message in a Medium Access Control Control Element (MAC CE) or Downlink Control Information (DCI). [C10] The UE described in C9, wherein the MAC CE includes one or more bits of a cell identifier (ID) or carrier identifier (ID), an associated reference resource ID, a metadata ID, or a bit indicating whether the MAC CE is for activation or deactivation. [C11] The UE described in C9, wherein the DCI comprises one or more triplets, each containing one or more of the following: cell ID or carrier ID, metadata ID, resource ID or resource set ID. [C12] The UE described in C9, wherein the DCI includes one or more of the following: a list of cell IDs or carrier IDs, a list of metadata IDs, or a list of resource IDs or resource set IDs, and there exists a one-to-one-to-one mapping between entries across the lists. [C13] The UE described in C9, wherein the DCI includes a list of trigger states, each trigger state includes a plurality of triplets, each triplet includes a cell identifier (ID) or carrier identifier (ID), a metadata ID, and a resource ID or resource set ID. [C14] The UE described in C9, wherein the DCI is an activated DCI, which has been scrambled with a data acquisition-activated radio network temporary identifier (RNTI). [C15] The one or more processors The deactivated DCI, scrambled by the data acquisition deactivated RNTI, is received. The UE described in C14 is configured to stop the collection of the data in response to the deactivation of the DCI. [C16] The UE according to C9, wherein the DCI is a group common DCI, and the one or more processors are configured to receive a radio resource control message indicating which triplet, which entry in a list, or which trigger state is used to indicate the activation or deactivation of the collection of the data. [C17] The UE according to C9, wherein the DCI is a group-common DCI, and the activation or deactivation of the collection of the data is indicated by bits in each segmentation. [C18] The UE according to C1, wherein the configuration specifies a channel state information (CSI) report dedicated to data acquisition, and the one or more processors are configured to determine that a reference signal for the CSI report is for data acquisition. [C19] The UE according to C1, wherein the configuration includes a bit or flag that specifies a channel status information (CSI) report and indicates that the CSI report is set to data acquisition mode, and the one or more processors are configured to determine that the reference signal for the CSI report is for data acquisition. [C20] The UE described in C1, wherein the first message activates or triggers a channel status information (CSI) report dedicated to data acquisition or a CSI report for a data acquisition mode. [C21] The first message indicates that the Channel Status Information (CSI) feedback mode is changed to nominal CSI reporting, data acquisition, or both, as described in C1. [C22] The UE according to C1, wherein one or more processors are configured to occupy at least one processing unit for each reference signal resource in order to collect the data. [C23] The UE described in C1, wherein collecting the aforementioned data occupies one or more of the following: the number of ports per reference signal resource, the amount of reference signal resources, the total number of ports, or a combination thereof. [C24] The UE described in C1, wherein one or more processors are configured to transmit UE capabilities to support data acquisition, the UE capabilities specifying support for one or more of the following: periodicity of data acquisition reference signals, number of ports per resource, maximum amount of resources, maximum total number of ports, number of processing units, or number of data acquisition processes. [C25] A network entity for wireless communications, Memory and The system comprises one or more processors coupled to the memory, and the one or more processors Send one or more of the following: a configuration for a reference signal used for data acquisition, or a first message indicating that data acquisition based on the reference signal is permitted. A network entity for wireless communication configured to transmit the aforementioned reference signal. [C26] The network entity according to C25, wherein one or more processors are configured to use the data to train a machine learning model for channel estimation or reference signal configuration. [C27] The network entity described in C25, wherein one or more processors are configured to send a second message indicating that data collection is not permitted. [C28] The network entity according to C25, wherein the configuration specifies that the reference signal is a dedicated reference signal for data acquisition. [C29] The network entity described in C25, wherein the configuration specifies one or more of the following: a cell identifier (ID) or a carrier identifier (ID), one or more reference resource IDs, a metadata ID, or a resource mapping configuration for the reference resource ID. [C30] The network entity described in C25, wherein one or more of the processors are configured to receive instructions for UE capabilities to support data acquisition, and the configuration is at least partially based on the UE capabilities.

Claims

1. User equipment (UE) for wireless communication, Memory and The system comprises one or more processors coupled to the memory, and the one or more processors Receiving one or more of the following: a configuration for a reference signal used for data acquisition, or a first message indicating that data acquisition based on the reference signal is permitted. The aforementioned reference signal is received, Based at least partially on the aforementioned reference signal, data is collected, It is configured to transmit the collected data, The configuration includes a bit or flag that specifies a channel status information (CSI) report and indicates that the CSI report is set to data acquisition mode, and the one or more processors are configured to determine that the reference signal for the CSI report is for data acquisition.

2. The aforementioned one or more processors Upon receiving a second message indicating that data collection was not permitted, The UE according to claim 1, configured to stop data collection based at least in part on the second message.

3. The UE according to claim 1, wherein one or more processors are configured to collect channel measurements based on the reference signal in order to collect the data.

4. The UE according to claim 1, wherein the data is associated with machine learning for channel estimation or reference signal construction.

5. The UE according to claim 1, wherein the configuration specifies that the reference signal is a dedicated reference signal for data acquisition, and the one or more processors for acquiring the data acquire the data in accordance with the fact that the reference signal is a dedicated reference signal.

6. The UE according to claim 5, wherein the first message activates the dedicated reference signal.

7. The UE according to claim 1, wherein the configuration specifies one or more of the following: a cell identifier (ID) or a carrier identifier (ID), one or more reference resource IDs, a metadata ID, or a resource mapping configuration for the reference resource ID.

8. The UE according to claim 7, wherein the metadata ID includes one or more of the following: beam information associated with transmitting the reference signal, or an antenna configuration associated with transmitting the reference signal.

9. The UE according to claim 1, wherein one or more processors for receiving the first message are configured to receive the first message in a Medium Access Control Control Element (MAC CE) or Downlink Control Information (DCI).

10. The UE according to claim 9, wherein the MAC CE includes one or more bits indicating whether the MAC CE is for activation or deactivation, such as a cell identifier (ID) or carrier identifier (ID), an associated reference resource ID, a metadata ID, or a bit indicating whether the MAC CE is for activation or deactivation.

11. The UE according to claim 9, wherein the DCI comprises one or more triplets, each containing one or more of the following: a cell ID or carrier ID, a metadata ID, a resource ID, or a resource set ID.

12. The UE according to claim 9, wherein the DCI includes one or more of the following: a list of cell IDs or carrier IDs, a list of metadata IDs, or a list of resource IDs or resource set IDs, and there exists a one-to-one-to-one mapping between entries across the lists.

13. The UE according to claim 9, wherein the DCI includes a list of trigger states, each trigger state includes a plurality of triplets, each triplet includes a cell identifier (ID) or carrier identifier (ID), a metadata ID, and a resource ID or resource set ID.

14. The UE according to claim 9, wherein the DCI is an activated DCI, which has been scrambled by a Radio Network Temporary Identifier (RNTI).

15. The aforementioned one or more processors The deactivated DCI, scrambled by the data acquisition deactivation RNTI, is received. The UE according to claim 14, which is configured to stop the collection of the data in response to the deactivation of the DCI.

16. The UE according to claim 9, wherein the DCI is a group-common DCI, and the one or more processors are configured to receive a radio resource control message indicating which triplet, which entry in a list, or which trigger state is used to indicate the activation or deactivation of the collection of the data.

17. The UE according to claim 9, wherein the DCI is a group-common DCI, and the activation or deactivation of the data collection is indicated by bits in each segmentation.

18. The UE according to claim 1, wherein the configuration specifies a channel state information (CSI) report dedicated to data acquisition, and the one or more processors are configured to determine that a reference signal for the CSI report is for data acquisition.

19. The UE according to claim 1, wherein the first message activates or triggers a channel status information (CSI) report dedicated to data acquisition or a CSI report for a data acquisition mode.

20. The UE according to claim 1, wherein the first message indicates that the channel status information (CSI) feedback mode is changed to nominal CSI reporting, data acquisition, or both.

21. The UE according to claim 1, wherein one or more processors are configured to occupy at least one processing unit for each reference signal resource in order to collect the data.

22. The UE according to claim 1, wherein collecting the aforementioned data occupies one or more of the following: the number of ports per reference signal resource, the amount of reference signal resources, the total number of ports, or a combination thereof.

23. The UE according to claim 1, wherein the one or more processors are configured to transmit UE capabilities to support data acquisition, and the UE capabilities specify support for one or more of the following: periodicity of a data acquisition reference signal, number of ports per resource, maximum amount of resources, maximum total number of ports, number of processing units, or number of data acquisition processes.

24. A network entity for wireless communication, Memory and The system comprises one or more processors coupled to the memory, and the one or more processors Transmit one or more of the following: a configuration for a reference signal used for data acquisition, or a first message indicating that data acquisition based on the reference signal is permitted. It is configured to transmit the aforementioned reference signal, A network entity for wireless communications, wherein the configuration includes a bit or flag indicating that the CSI report is set to data acquisition mode, and specifies a channel status information (CSI) report.

25. The network entity according to claim 24, wherein one or more processors are configured to use the data to train a machine learning model for channel estimation or reference signal configuration.

26. The network entity according to claim 24, wherein one or more processors are configured to send a second message indicating that data collection is not permitted.

27. The network entity according to claim 24, wherein the configuration specifies that the reference signal is a dedicated reference signal for data acquisition.

28. The network entity according to claim 24, wherein the configuration specifies one or more of the following: a cell identifier (ID) or a carrier identifier (ID), one or more reference resource IDs, a metadata ID, or a resource mapping configuration for the reference resource ID.

29. The network entity according to claim 24, wherein one or more of the processors are configured to receive instructions for UE capabilities to support data acquisition, and the configuration is at least partially based on the UE capabilities.

Images