Reference signal data collection for training machine learning models
The method of configuring and processing reference signals in wireless communication systems addresses data collection challenges, enhancing the training of machine learning models and improving network performance in LTE and NR systems.
Patent Information
- Application Number
- CN202280095206.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-29
- Publication Date
- 2024-12-03
AI Technical Summary
Existing wireless communication systems face challenges in efficiently collecting data for training machine learning models, particularly in integrating reference signal data collection for improved performance in LTE and NR networks.
A method and apparatus for wireless communication that involves configuring and receiving reference signals for data collection, allowing data collection based on these signals, and sending the collected data, utilizing network entities and user equipment with processors and memory to facilitate this process.
Enhances data collection for training machine learning models, improving the performance and efficiency of LTE and NR networks by leveraging reference signals for data collection and processing.
Smart Images

Figure CN119072883A_ABST
Abstract
Description
Technical Field
[0001] Aspects of the present disclosure generally relate to wireless communications and to techniques and apparatus for collecting data for training machine learning models. Background Art
[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies 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 enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).
[0003] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.
[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using 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, as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention
[0005] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving a configuration of a reference signal for data collection and / or a first message indicating that data collection based on the reference signal is allowed. The method may include receiving the reference signal. The method may include collecting data based at least in part on the reference signal. The method may include sending the collected data.
[0006] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include sending a configuration of a reference signal for data collection and / or a first message indicating that data collection based on the reference signal is allowed. The method may include sending a reference signal.
[0007] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a configuration of a reference signal for data collection and / or a first message indicating that data collection based on the reference signal is allowed. The one or more processors may be configured to receive a reference signal. The one or more processors may be configured to collect data based at least in part on the reference signal. The one or more processors may be configured to send the collected data.
[0008] Some aspects 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. The one or more processors may be configured to send a configuration of a reference signal for data collection and / or a first message indicating that data collection based on the reference signal is allowed. The one or more processors may be configured to send a reference signal.
[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a configuration of a reference signal for data collection and / or a first message indicating that data collection based on the reference signal is allowed. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive the reference signal. The instruction set, when executed by one or more processors of the UE, may cause the UE to collect data based at least in part on the reference signal. The instruction set, when executed by one or more processors of the UE, may cause the UE to send the collected data.
[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send a configuration of a reference signal for data collection and / or a first message indicating that data collection based on the reference signal is allowed. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send the reference signal.
[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a configuration of a reference signal for data collection and / or a first message indicating that data collection based on the reference signal is allowed. The apparatus may include means for receiving the reference signal. The apparatus may include means for collecting data based at least in part on the reference signal. The apparatus may include means for sending the collected data.
[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a configuration of a reference signal for data collection and / or a first message indicating that data collection based on the reference signal is allowed. The apparatus may include means for sending a reference signal.
[0013] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, UEs, base stations, network entities, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated in the drawings and description.
[0014] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.
[0015] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.
[0017] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.
[0018] Figure 2 is a diagram illustrating an example of a network entity communicating with a user equipment (UE) in a wireless network according to the present disclosure.
[0019] Figure 3 is a diagram illustrating an example of a decomposed base station according to the present disclosure.
[0020] Figure 4 is a diagram illustrating an example of a channel state information reference signal beam management procedure according to the present disclosure.
[0021] Figure 5 is a diagram illustrating an example associated with collecting data for training a machine learning model according to the present disclosure.
[0022] Figure 6is a diagram illustrating an example of collecting data for training a machine learning model according to the present disclosure.
[0023] Figure 7 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.
[0024] Figure 8 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.
[0025] Figures 9 and 10 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION
[0026] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method that is practiced using other structures, functions, or structures and functions other than the various aspects of the disclosure set forth herein or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.
[0027] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0028] Although aspects may be described herein using terminology generally associated with 5G or new radio (NR) radio access technology (RAT), aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).
[0029] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include a user equipment (UE) 120 or a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e). The wireless network 100 may also include one or more network entities, such as a base station 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. Base station 110 (sometimes referred to as BS) may include, for example, an NR base station, an LTE base station, a B node, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.
[0030] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 that has an association with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.
[0031] In some examples, the cells may not necessarily be stationary, and the geographic area of the cells may move depending on the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may interconnect with each other and / or to one or more other base stations 110 or network entities in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).
[0032] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "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 aspects, the term "base station" or "network entity" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with base station 110). In some aspects, the term "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 a plurality of different devices (which may be located in the same geographical location or in different geographical locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, 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 aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.
[0033] The wireless network 100 may include one or more relay stations. A relay station is a network entity that can receive transmissions of data from an upstream station (e.g., a network entity or UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a network entity). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown in FIG, BS 110d (eg, a relay base station) can communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. Base station 110 that relays communication may be referred to as a relay station, relay base station, relay, etc.
[0034] The wireless network 100 may be a heterogeneous network having network entities including different types of BSs, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).
[0035] The network controller 130 may be coupled to or in communication 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 also communicate directly with each other or indirectly via a wireless or wired backhaul communication link.
[0036] UE 120 can be dispersed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a car component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.
[0037] Some UEs 120 may be considered as machine type communication (MTC) 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, which may communicate with a network entity, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.
[0038] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, an air interface, etc. Frequency may be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.
[0039] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using a network entity as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., 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 examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.
[0040] The devices of the wireless network 100 can communicate using an electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc. according to frequency or wavelength. For example, the devices of the wireless network 100 can communicate using one or more operating bands. In 5GNR, two initial operating bands have been identified as frequency ranges designated 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 greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).
[0041] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz to 24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz to 71GHz), FR4 (52.6GHz to 114.25GHz) and FR5 (114.25GHz to 300GHz). Each of these higher frequency bands falls within the EHF band.
[0042] Considering the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.
[0043] In some aspects, a UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a configuration of a reference signal for data collection and / or a first message indicating that data collection based on the reference signal is allowed. The communication manager 140 may receive the reference signal and collect data based at least in part on the reference signal. The communication manager 140 may send the collected data. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.
[0044] In some aspects, a network entity (e.g., base station 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a configuration of a reference signal for data collection and / or a first message indicating that data collection based on a reference signal is allowed. The communication manager 150 may send the reference signal. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.
[0045] As indicated above, Figure 1 Other examples can be found in the Figure 1 The examples described are different.
[0046] Figure 2 2 is a diagram illustrating an example 200 of a network entity (e.g., base station 110) communicating 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).
[0047] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and 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 perform spatial processing (e.g., pre-coding) on data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The 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) (shown as antennas 234a to 234t).
[0048] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the 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) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information 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 a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.
[0049] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with network entities via the communication unit 294.
[0050] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included 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, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.
[0051] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to a network entity. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (eg, with reference to Figures 4 to 10 ).
[0052] At a network entity (e.g., base station 110), uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component of modem 232 shown as DEMOD), detected by MIMO detector 236 (where applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller / processor 240. The network entity may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. The network entity may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network entity may include a modulator and a demodulator. In some examples, the network entity includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., reference 20 to FIG. 1 ). Figures 4 to 10 ).
[0053] As described in more detail elsewhere herein, a controller / processor of a network entity (e.g., controller / processor 240 of base station 110), controller / processor 280 of UE 120, and / or Figure 2 Any other component of the processor may perform one or more techniques associated with collecting data for training a machine learning model for channel estimation or reference signal configuration. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the can perform or direct e.g. Figure 7 The process 700 Figure 8 800 and / or other processes as described herein. Memory 242 and memory 282 may store data and program codes for a network entity and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of a network entity and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), may cause one or more processors, UE 120, and / or a network entity to perform or direct, for example, Figure 7 The process 700 Figure 8 The process 800 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.
[0054] In some aspects, the UE 120 includes means for receiving a configuration of a reference signal for data collection and / or a first message indicating that data collection based on the reference signal is allowed; means for receiving the reference signal; means for collecting data based at least in part on the reference signal; and / or means for sending the collected data. The means for the UE 120 to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.
[0055] In some aspects, a network entity (e.g., base station 110) includes a means for sending a configuration of a reference signal for data collection and / or a first message indicating that data collection based on the reference signal is allowed; and / or a means for sending a reference signal. In some aspects, the means for the network entity to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.
[0056] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality 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.
[0057] As indicated above, Figure 2 Other examples can be found in the Figure 2 The examples described are different.
[0058] Figure 3 is a diagram illustrating an example of a decomposed base station 300 according to the present disclosure.
[0059] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station, or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B, an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) can be implemented as an aggregated base station (also called an independent BS or a monolithic BS) or a decomposed base station.
[0060] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).
[0061] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.
[0062] The decomposed base station 300 architecture may include one or more CUs 310 that may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links (such as an F1 interface). The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Fronthaul links, midhaul links, and backhaul links may generally be referred to as "communication links." The RU 340 may communicate with a corresponding UE 120 via one or more RF access links. In some aspects, a UE 120 may be served simultaneously by multiple RUs 340. The DU 330 and the RU 340 may also be referred to as "O-RAN DU (O-DU") and "O-RAN RU (O-RU)", respectively. The network entity may include a CU, DU, RU, or any combination of CU, DU, and RU. The network entity may include a decomposed base station or one or more components of a decomposed base station, such as a CU, DU, RU, or any combination of CU, DU, and RU. The network entity may also include one or more of a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface or service for a UE, a mobile station, a sensor / actuator, or other wireless device.
[0063] Each of these units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.
[0064] In some aspects, CU 310 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 that is configured to communicate signals with other control functions hosted by CU 310. CU 310 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 specific implementations, CU 310 may be logically split 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 may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). CU 310 may be implemented to communicate with DU 330 as needed for network control and signaling.
[0065] DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RU 340. In some aspects, DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split such as defined by 3GPP. In some aspects, DU 330 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.
[0066] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low 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, based at least in part on a functional split such as a lower layer functional split. In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.
[0067] The SMO framework 305 may be configured to support RAN deployment and configuration of non-virtualized network elements 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, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN such as an open eNB (O-eNB) 311 via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .
[0068] The non-RT RIC 315 may be configured to include logic functions that implement 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 of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that implement near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.
[0069] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).
[0070] As indicated above, Figure 3 Other examples can be found in the Figure 3 The examples described are different.
[0071] Figure 4 4 are diagrams illustrating examples 400, 410, and 420 of a channel state information (CSI) reference signal (CSI-RS) beam management procedure according to the present disclosure. Figure 4 As shown, examples 400, 410, and 420 include UE 120 communicating with base station 110 in a wireless network (e.g., wireless network 100). Figure 4 The devices shown are provided as examples, and the wireless network may support communication and beam management between other devices (e.g., between UE 120 and base station 110 or a transmit receive point (TRP), between a mobile terminal node and a control node, between an integrated access and backhaul (IAB) child node and an IAB parent node, and / or between a scheduling node and a scheduling node). In some aspects, UE 120 and base station 110 may be in a connected state (e.g., an RRC connected state).
[0072] like Figure 4 As shown, example 400 may include base station 110 and UE 120 communicating to perform beam management using CSI-RS. Example 400 depicts 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 scanning procedure, a cell search procedure, and / or a beam search procedure. Figure 4 As shown in example 400, CSI-RS may be configured to be sent from base station 110 to UE 120. CSI-RS may be configured to be periodic (e.g., using RRC signaling), semi-persistent (e.g., using medium access control (MAC) control element (MAC CE) signaling), and / or aperiodic (e.g., using downlink control information (DCI)).
[0073] The first beam management procedure may include the base station 110 performing beam scanning on multiple transmit (Tx) beams. The base station 110 may use each transmit beam to transmit a CSI-RS for beam management. In order to enable the UE 120 to perform receive (Rx) beam scanning, the base station may use the transmit beam to transmit each CSI-RS multiple times within the same RS resource set (e.g., using repetition) so that the UE 120 can scan through the receive beam in multiple transmit instances. For example, in a case where the base station 110 has a set of N transmit beams and the UE 120 has a set of M receive beams, the CSI-RS may be transmitted M times on each of the N transmit beams, so that the UE 120 can receive M instances of the CSI-RS per transmit beam. In other words, for each transmit beam of the base station 110, the UE 120 may perform beam scanning through the receive beam of the UE 120. Thus, the first beam management procedure may enable UE 120 to measure CSI-RS on different transmit beams using different receive beams to support selection of base station 110 transmit beam / UE 120 receive beam pairs. UE 120 may report the measurements to base station 110 to enable base station 110 to select one or more beam pairs for communication between base station 110 and UE 120. Although example 400 has been described in conjunction with CSI-RS, the first beam management procedure may also use synchronization signal blocks (SSBs) to perform beam management in a manner similar to that described above.
[0074] like Figure 4 As shown, example 410 may include base station 110 and UE 120 communicating to perform beam management using CSI-RS. Example 410 depicts a second beam management procedure (e.g., P2 CSI-RS beam management). The second beam management procedure may be referred to as a beam refinement procedure, a base station beam refinement procedure, a TRP beam refinement procedure, and / or a transmit beam refinement procedure. Figure 4As shown in example 410, the CSI-RS may be configured to be sent from the base station 110 to the UE 120. The CSI-RS may be configured to be non-periodic (e.g., using DCI). The second beam management procedure may include the base station 110 performing beam scanning on one or more transmit beams. The one or more transmit beams may be a subset of all transmit beams associated with the base station 110 (e.g., determined at least in part based on measurements reported by the UE 120 in conjunction with the first beam management procedure). The base station 110 may use each of the one or more transmit beams to transmit the CSI-RS for beam management. The UE 120 may measure each CSI-RS using a single (e.g., the same) receive beam (e.g., determined at least in part based on measurements performed in conjunction with the first beam management procedure). The second beam management procedure may enable the base station 110 to select the best transmit beam based at least in part on measurements of the CSI-RS reported by the UE 120 (e.g., measured by the UE 120 using a single receive beam).
[0075] like Figure 4 As shown, example 420 depicts a third beam management procedure (e.g., P3 CSI-RS beam management). The third beam management procedure may be referred to as a beam refinement procedure, a UE beam refinement procedure, and / or a receive beam refinement procedure. Figure 4 As shown in example 420, one or more CSI-RS may be configured to be sent from base station 110 to UE 120. The CSI-RS may be configured to be non-periodic (e.g., using DCI). The third beam management process may include base station 110 sending one or more CSI-RS using a single transmit beam (e.g., determined at least in part based on measurements reported by UE 120 in conjunction with the first beam management procedure and / or the second beam management procedure). In order to enable UE 120 to perform receive beam scanning, the base station may use the transmit beam to send (e.g., using repetition) CSI-RS multiple times within the same RS resource set, so that UE 120 can scan through one or more receive beams in multiple transmission instances. The one or more receive beams may be a subset of all receive beams associated with UE 120 (e.g., determined at least in part based on measurements performed in conjunction with the first beam management procedure and / or the second beam management procedure). The third beam management procedure may enable base station 110 and / or UE 120 to select the best receive beam based at least in part on reported measurements received from UE 120 (eg, measurements of the CSI-RS of the transmit beam using one or more receive beams).
[0076] The UE 120 may provide CSI feedback in a codebook that is used as a precoding matrix indicator (PMI) dictionary from which the UE 120 may report the best PMI codeword. The UE 120 may report the PMI using a bit sequence. 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 the machine learning-based CSI feedback. The CSI encoder may be similar to a PMI search algorithm, and the CSI decoder may be similar to a PMI codebook for converting CSI report bits into PMI codewords.
[0077] The CSI encoder may have a downlink channel matrix (H), a transmit covariance matrix, a downlink pre-decoder (V), an interference covariance matrix (R nn ) and / or the original and whitened downlink channels as input, and the CSI decoder can output a downlink channel matrix (H), a transmit covariance matrix, a downlink pre-decoder (V), an interference covariance matrix (R nn ) and / or original and whitened downlink channels.
[0078] For channel estimation based on optimized CSI-RS, N ports can be multiplexed on N resource elements (REs) in a time division multiplexing (TDM), code division multiplexing (CDM), and / or frequency division multiplexing (FDM) manner for each resource block (RB). The RB density can be 1 or 0.5 (sent on every two RBs). With AI-based CSI-RS optimization, N ports can be multiplexed on L REs, where L is less than N. The RB density can be reduced to below 0.5, and non-uniform RB patterns can be considered. The UE can perform channel estimation using an AI-based channel estimation module. The base station 110 can use an AI-based CSI-RS transmitter to multiplex N ports on L REs within each RB. In both cases, the channel is used for training. The machine learning model can be trained via generated synthetic data or data collected over the air (OTA). Real-world collected data involves radio frequency (RF) effects and is preferred. The network entity (e.g., gNB) may send CSI-RS with full density, and the UE may perform channel estimation and upload the data as ground truth for CSI feedback or for CSI-RS optimization and channel estimation.
[0079] However, it has not been specified how to configure reference signals for this data collection or how to trigger or activate the data collection.
[0080] As indicated above, Figure 4 is provided as an example of a beam management procedure. Other examples of beam management procedures may be related to Figure 4For example, UE 120 and base station 110 may perform the third beam management procedure before performing the second beam management procedure, and / or UE 120 and base station 110 may perform a similar beam management procedure to select a UE transmit beam.
[0081] Figure 5 is a diagram illustrating an example 500 associated with collecting data for training a machine learning model according to the present disclosure. Figure 5 As shown, a network entity 510 (eg, base station 110) and a UE 520 (eg, UE 120) may communicate with each other over a wireless network (eg, wireless network 100).
[0082] According to various aspects described herein, a UE may collect data for training a machine learning model based on a trigger or activation command indicating that data collection is allowed (the UE determines when to start) or indicating that data collection is to start (the UE is instructed to start). A reference signal dedicated to data collection may also trigger data collection. Data collection may also be started based on information in a CSI report message (e.g., a trigger, an activation command) or a change in a CSI reporting mode. Data collection may also be deactivated by another message indicating that data collection is no longer allowed. By specifying when data collection starts, the UE and the network may more efficiently use real-world data to train a machine learning model without interfering with other operations of the UE.
[0083] Example 500 illustrates the configuration and activation of reference signals for data collection. In some aspects, as shown by reference numeral 525, the network entity 510 may send the configuration of reference signals for data collection via a MAC CE, downlink control information (DCI), or an RRC message (e.g., CSI-RS-ResourceConfigDataCollection). The configuration may indicate a reference signal dedicated to data collection. 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 indicated by an ID or a tag. The UE 520 may receive reference resources according to the resource ID and cell ID, and then perform measurements. When uploading data to a data server to train a machine learning model, the UE 520 may also attach the resource ID and the cell or carrier ID. As shown in example 500, each resource may correspond to a specific antenna mapping or layout. The configuration may include a data collection ID or a metadata ID. The metadata ID may include beam information associated with transmitting a reference signal and / or an antenna configuration associated with transmitting a reference signal. The configuration may also include frequency bandwidth and time domain type. The time domain type may be periodic (with periodicity and time slot offset), semi-persistent (with periodicity and time slot offset), or aperiodic. The configuration may include reference signal pattern and / or density. The configuration may also include quasi co-location (QCL) information and / or bandwidth part (BWP) information.
[0084] In some aspects, the reference signal may be an existing reference signal, but the RRC message may be new. For example, a new RRC field may be dedicated to CSI-RS-ResouceConfigDataCollection and may include a CSI-RS resource configuration ID, a cell or carrier ID, a BWP ID, a resource mapping configuration, and / or a metadata ID. In some aspects, an RRC field may be added to the CSI-RS indication signaling. For example, a non-zero power (NZP)-CSI-RS-ResourceSet information element (IE) may add a data collection process ID or a metadata ID. In some aspects, the network entity 510 may define a new type of reference signal for training reference signals (with a new resource mapping mode different from existing reference signals) or a new ZP-CSI-RS mode for rate matching with a reference signal (with the above aspects).
[0085] As indicated by reference numeral 530, the network entity 510 may send a first message. The network entity 510 may send the first message via a MAC CE or a DCI. The first message may be a trigger or activation message indicating that data collection based on the reference signal is allowed. In some aspects, if the reference signal is a dedicated reference signal for data collection, the first message may be a trigger or activation of the reference signal, and the UE 520 may start data collection.
[0086] As indicated by reference numeral 535, in response to receiving an activation message for data collection (e.g., for a dedicated reference signal), the UE 520 may start data collection. In some aspects, if the dedicated reference signal configured for data collection is periodic, the RRC message configuring the reference signal for data collection may activate the periodic reference signal and data collection. In some aspects, if the dedicated reference signal configured for data collection is semi-persistent, the MAC CE may activate and deactivate the semi-persistent reference signal, and the MAC CE may activate and deactivate data collection based at least in part on the dedicated semi-persistent reference signal. In some aspects, the network entity 510 may use a new field in a DCI (e.g., an uplink DCI, a downlink DCI, or a group-common DCI) to trigger data collection based at least in part on a dedicated reference signal for data collection. The group-common DCI may include a list of reference signal IDs (e.g., TrainingRS-ID or CSI-RS-ResourceDataCollection-ID) to completely trigger a data collection process for a group of UEs. Individual UEs may be configured (via RRC) as to which field to read from the list, or which data collection reference signal is triggered for the respective UE. Once these reference signals are activated, data collection may be activated, as the reference signals may be dedicated to data collection.
[0087] As shown by reference numeral 540, the network entity 510 may send a reference signal. In some aspects, the UE 520 may detect that the reference signal is a dedicated reference signal configured for data collection and may start data collection. The configuration may help the UE 520 identify or detect the dedicated reference signal. The UE 520 may perform rate matching or allocate modulation bits to resources around the dedicated reference signal for data collection.
[0088] As shown by reference numeral 545, UE 520 may collect data when permitted to do so. This may include obtaining channel measurements of reference signals. As shown by reference numeral 550, UE 520 may upload data to a data server for use in training a machine learning model for channel estimation or for configuring reference signals or other reference signals. The data server may be a UE server in communication with a network entity (e.g., a model repository).
[0089] In some aspects, the network entity 510 may send a deactivation message indicating that data collection is no longer allowed, as shown by reference numeral 555. The UE 520 may stop collecting data. The UE 520 may send the collected data before or after receiving the deactivation message.
[0090] As indicated above, Figure 5 Other examples can be found in the Figure 5 The examples described are different.
[0091] Figure 6 is a diagram illustrating example 600 of collecting data for training a machine learning model according to the present disclosure.
[0092] In some aspects, data collection may be based on non-dedicated reference signals, and a data collection trigger or activation message (e.g., MAC CE, DCI) may trigger or activate data collection based on these reference signals. Example 600 shows an activation message 602 for a semi-persistent (SP) CSI-RS. The CSI-RS may be used for normal CSI reporting. Example 600 also shows a data collection activation message 604 (e.g., MAC CE), which indicates that data collection by the UE 520 based on the activated semi-persistent CSI-RS is allowed. The activation message 604 may include a cell or carrier ID of a reference signal resource (e.g., CSI-RS resource) and / or an associated reference signal resource (e.g., CSI-RS) or a resource set (indicated by a resource or resource set ID) for data collection. Each resource may correspond to a specific antenna mapping or layout (implicitly corresponding). The UE 520 may collect data from the CSI-RS. For machine learning purposes, data collection may be configured and / or the collected data may be formatted. The activation message 604 may include a metadata ID. The metadata ID may include beam information associated with the transmitted reference signal and / or antenna configuration associated with the transmitted reference signal.
[0093] In some aspects, if the reference signal has not been activated, the reference signal can be activated or deactivated along with the data collection procedure (same MAC CE). If the reference signal has been activated for other purposes, such as for CSI reporting, the UE 520 can stop the current process and start collecting data for training the machine learning model. In some aspects, if the reference signal has been used for data collection, the UE can stop data collection if aperiodic CSI reporting is triggered and the reference signal is used as a measurement resource.
[0094] In some aspects, the activation message 604 may include a bit that toggles activation or deactivation (pause) of data collection based on a corresponding reference signal associated with the activation message 604. The network entity 510 may change the antenna mapping and may instruct the UE 520 to suspend reference signal measurements for data collection. To suspend, the UE 520 may refrain from collecting data for a specified time.
[0095] In some aspects, in order to trigger or activate data collection based on a reference signal, the network entity 510 may send a group-common DCI including multiple segments. The group-common DCI may completely trigger data collection for a group of UEs. Each segment may include one or more triplets, wherein each triplet includes at least one of a cell or carrier ID, a metadata ID, or a resource or resource set ID. In some aspects, the group-common DCI may include a list of segments, including a list of cell or carrier IDs, a list of metadata IDs, and a list of resource or resource set IDs. Each entry in the list may have a one-to-one mapping on the list (cell or carrier ID to metadata ID to resource or resource set ID). In some aspects, each segment of the group-common DCI may include a data collection request that activates a trigger state from a pre-configured trigger state list (via RRC). Each trigger state may have multiple triplets, wherein each triplet includes a cell or carrier ID, a metadata ID, and / or a resource or resource set ID.
[0096] If the DCI is a group common DCI, then an individual UE (e.g., UE 520) may receive (via RRC) an indication of which segment in the DCI the UE 520 is to read. This may include which triplets to read, which components in a list to read, or which requests to read. The UE 520 may determine the triplets, components, and / or requests by the starting bit or field to read and the length of the bits or field to read. This means that each UE will know which reference signal resources, their carrier or cell IDs, and their metadata IDs will be used for data collection.
[0097] In some aspects, for the group-common DCI method, if the DCI is scrambled by a first sequence, such as a data collection activation radio network temporary identifier (RNTI), the UE 520 may be activated for data collection. If the DCI is scrambled by a second sequence, such as a data collection deactivation RNTI, the UE 520 may be deactivated for data collection. In some aspects, the group-common DCI is scrambled by the data collection RNTI, and a bit or DCI code point may be used to indicate activation or deactivation of data collection in each segment.
[0098] In some aspects, UE-specific DCI may be used to activate or deactivate data collection. Using UE-specific downlink or uplink DCI, a single triplet or a single request may be provided to each UE. The UE-specific DCI may include multiple segments. Each segment may include one or more triplets, wherein each triplet includes at least one of a cell or carrier ID, a metadata ID, or a resource or resource set ID. In some aspects, the UE-specific DCI may include a list of segments, including a list of cell or carrier IDs, a list of metadata IDs, and a list of resource or resource set IDs. Each entry in the list may have a one-to-one mapping on the list. In some aspects, each segment 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, wherein each triplet includes a cell or carrier ID, a metadata ID, and / or a resource or resource set ID. For group-common DCI or UE-specific DCI, if a non-periodic reference signal is used, a DCI or other message may be used to trigger the non-periodic reference signal.
[0099] In some aspects, the configuration of reference signal resources for data collection may configure a dedicated report (e.g., CSI report) for data collection. This may include, for example, setting the reporting amount to "none" or "data collection" (but no layer 1 reporting). This means that the CSI-RS resources associated in this CSI report are used for data collection.
[0100] In some aspects, as shown in example 610, the configuration may include a bit or mode flag indicating that the CSI report is set to data collection mode. Once in data collection mode, the CSI-RS resources associated with the CSI report are used for data collection. The trigger or activation message may trigger a CSI report dedicated to data collection or a CSI report for data collection mode. The message may indicate that the CSI feedback (CSF) mode is changed from normal CSI reporting to data collection, or to both CSI reporting and data collection. The mode change may be via DCI or MAC CE. If the UE 520 determines that the reference signal used for the CSI report is for data collection, the UE 520 may determine when to upload data.
[0101] For CSI reporting, a central processing unit (CPU) count may relate to one CPU per resource. An active resource count may relate to one CPU per resource. In some aspects, a mode flag may be included in a traditional reporting (eg, CSI reporting) configuration for dynamically changing the reporting amount.
[0102] In some aspects, from the start of the data collection activation command to its release, data collection may occupy one CPU per resource. For active resources or ports, data collection may occupy one active resource per resource and occupy P active ports, where P is the amount of ports per resource for data collection. The count may start from the start of the data collection activation command to its release. UE 520 may report UE capabilities for resource use. UE 520 may report a list of the maximum amount of ports per resource, the maximum amount of resources and / or the maximum amount of total ports per frequency band or per frequency band combination (BC), and report that UE 520 is capable of processing data collection. UE 520 may also report the amount (per frequency band and per BC report) for processing data collection simultaneously with other CSI. An alternative method for active resource and capability reporting may include the ability of UE 520 to report processing. This may include up to N resources and P total ports for data collection per time slot, the amount of resources and ports that should fulfill the configuration of the capability, and / or the amount of data collection process.
[0103] If the UE 520 uses the reference signal for data collection, a long periodicity results in inefficient data collection, while a short periodicity results in more data. The UE 520 may not be able to handle all data collection frequently, and this may be a waste of reference signal overhead. In some aspects, the configuration may specify the periodicity of the reference signal used for data collection. The UE 520 may report UE capabilities for supporting data collection, including supported periodicities. The network entity 510 may configure the periodicity of the reference signal based at least in part on the UE capabilities. In some aspects, when or at which reference signal opportunity to perform data collection may depend on the UE 520. When to upload the collected data (e.g., measured data) may depend on the UE 520.
[0104] When the network entity 510 configures the reference signal, the network entity 510 may honor the UE capabilities (i.e., not configure any periodicity less than the periodicity indicated by the UE 520). For example, if the UE 520 reports the capability to handle a reference signal periodicity of 10 milliseconds (ms), the network entity 510 may configure the reference signal with a periodicity greater than 10 ms.
[0105] As indicated above, Figure 6 Other examples can be found in the Figure 6 The examples described are different.
[0106] Figure 7 700 is a diagram illustrating an example process 700 performed, for example, by a UE according to the present disclosure. Example process 700 is an example in which a UE (e.g., UE 120, UE 520) performs operations associated with reference signal data collection for training a machine learning model.
[0107] like Figure 7 As shown, in some aspects, process 700 may include receiving a configuration of a reference signal for data collection and / or a first message indicating that data collection based on the reference signal is allowed (block 710). For example, a UE (e.g., using Fig. 9 The communication manager 908 and / or receiving component 902 depicted in FIG. 1 can receive configuration of a reference signal for data collection and / or a first message indicating that data collection based on the reference signal is allowed, as described above.
[0108] like Figure 7 As further shown, in some aspects, process 700 may include receiving a reference signal (block 720). For example, a UE (e.g., using Fig. 9 The communication manager 908 and / or receiving component 902 depicted in FIG. 9 may receive a reference signal, as described above.
[0109] like Figure 7 As further shown, in some aspects, process 700 may include collecting data based at least in part on the reference signal (block 730). Fig. 9 The communication manager 908 and / or data collection component 910 depicted in FIG. 1 may collect data based at least in part on the reference signal, as described above.
[0110] like Figure 7 As further shown, in some aspects, process 700 may include sending the collected data (block 740). For example, a UE (e.g., using Fig. 9 The communication manager 908 and / or the sending component 904 depicted in FIG. 9 may send the collected data as described above.
[0111] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.
[0112] In a first aspect, process 700 includes receiving a second message indicating that data collection is not permitted, and ceasing data collection based at least in part on the second message.
[0113] In a second aspect, alone or in combination with the first aspect, collecting data includes collecting channel measurements based on a reference signal.
[0114] In a third aspect, alone or in combination with one or more of the first and second aspects, the data is associated with machine learning for channel estimation or configuring reference signals.
[0115] In a fourth aspect, 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 collection, and collecting data includes collecting data in response to the reference signal being the dedicated reference signal.
[0116] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the first message activates a dedicated reference signal.
[0117] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the configuration specifies one or more of a cell or carrier ID, one or more reference resource IDs, a metadata ID, or a resource mapping configuration for a reference resource ID.
[0118] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the metadata ID includes one or more of beam information associated with a transmitted reference signal or an antenna configuration associated with a transmitted reference signal.
[0119] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, receiving the first message includes receiving the first message in a MAC CE or a DCI.
[0120] In a ninth aspect, either alone or in combination with one or more of aspects one to eight, the MAC CE includes one or more of a cell or carrier ID, an associated reference resource ID, a metadata ID, or a bit indicating whether the MAC CE is for activation or deactivation.
[0121] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the DCI comprises one or more triplets, each of which comprises one or more of a cell or carrier ID, a metadata ID, or a resource or resource set ID.
[0122] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the DCI includes one or more of a list of cell or carrier IDs, a list of metadata IDs, or a list of resource or resource set IDs, and there is a one-to-one mapping between the entries on the lists.
[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 including multiple triplets, each triplet including a cell or carrier ID, a metadata ID, and a resource or resource set ID.
[0124] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the DCI is an activation DCI scrambled with a data collection activation RNTI.
[0125] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the process 700 includes receiving a deactivation DCI scrambled with a data collection deactivation RNTI, and stopping collection of data in response to the deactivation DCI.
[0126] In a fifteenth aspect, either alone or in combination with one or more of aspects one to fourteen, the DCI is a group common DCI, and process 700 includes receiving a radio resource control message indicating which triplet, which entry of a list, or which trigger state is used to indicate activation or deactivation of collection of data.
[0127] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the DCI is a group common DCI, and activation or deactivation of collection of data is indicated by a bit in each segment.
[0128] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the configuration specifies CSI reporting dedicated to data collection, and the process 700 includes determining that a reference signal for CSI reporting is for data collection.
[0129] In an eighteenth aspect, either alone or in combination with one or more of the first to seventeenth aspects, the configuration specifies a CSI report and includes a bit or flag indicating that the CSI report is set to a data collection mode, and process 700 includes determining that a reference signal for the CSI report is for data collection.
[0130] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the first message activates or triggers CSI reporting dedicated to data collection or CSI reporting for a data collection mode.
[0131] In a twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, the first message indicates that a CSI feedback mode is changed to nominal CSI reporting, data collection, or both.
[0132] In a twenty-first aspect, alone or in combination with one or more of the first to twentieth aspects, process 700 includes occupying at least one processing unit per reference signal resource for collection of data.
[0133] In the twenty-second aspect, either alone or in combination with one or more of the first to twenty-first aspects, the collection of data occupies one or more of the amount of ports per reference signal resource, the amount of reference signal resources, the amount of total ports, or a combination thereof.
[0134] In the twenty-third aspect, either alone or in combination with one or more of aspects one to twenty-second, process 700 includes sending UE capabilities for supporting data collection, and the UE capabilities specify support for one or more of the periodicity of a data collection reference signal, the amount of ports per resource, the maximum amount of resources, the maximum amount of total ports, the amount of processing units, or the amount of data collection processes.
[0135] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 The blocks depicted in the process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 700. Additionally or alternatively, two or more blocks in the blocks of the process 700 may be performed in parallel.
[0136] Figure 8 800 is a diagram illustrating an example process 800 performed, for example, by a network entity in accordance with the present disclosure. Example process 800 is an example in which a network entity (e.g., network entity 510) performs operations associated with configuring reference signal data collection for training a machine learning model.
[0137] like Figure 8 As shown, in some aspects, process 800 may include sending a first message (block 810) configuring a reference signal for data collection and / or indicating that data collection based on the reference signal is allowed. For example, a network entity (e.g., using Fig.10 The communication manager 1008 and / or the sending component 1004 depicted in FIG. 1004 may send configuration of a reference signal for data collection and / or a first message indicating that data collection based on the reference signal is allowed, as described above.
[0138] like Figure 8 As further shown, in some aspects, process 800 may include sending a reference signal (block 820). For example, a network entity (e.g., using Fig.10 The communication manager 1008 and / or the transmitting component 1004 depicted in FIG. 1004 may transmit a reference signal as described above.
[0139] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.
[0140] In a first aspect, process 800 includes using data to train a machine learning model for channel estimation or reference signal configuration.
[0141] In a second aspect, alone or in combination with the first aspect, process 800 includes sending a second message indicating that data collection is not permitted.
[0142] In a third aspect, 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 collection.
[0143] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the configuration specifies one or more of a cell or carrier ID, one or more reference resource IDs, a metadata ID, or a resource mapping configuration for a reference resource ID.
[0144] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 800 includes receiving an indication of UE capabilities for supporting data collection, and the configuring is based at least in part on the UE capabilities.
[0145] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 The blocks depicted in the process 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 800. Additionally or alternatively, two or more blocks in the blocks of the process 800 may be performed in parallel.
[0146] Fig. 9 is a diagram of an example apparatus 900 for wireless communication. Apparatus 900 may be a UE (e.g., UE 120, UE 520), or a UE may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using receiving component 902 and transmitting component 904. As further shown, apparatus 900 may include a communication manager 908. Communication manager 908 may control and / or otherwise manage one or more operations of receiving component 902 and / or transmitting component 904. In some aspects, communication manager 908 may include a communication manager 908 in conjunction with receiving component 902 and / or transmitting component 904. Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the UE described herein. The communication manager 908 may be or be similar to Figure 1 and Figure 2For example, in some aspects, the communication manager 908 can be configured to perform one or more of the functions described as being performed by the communication manager 140. In some aspects, the communication manager 908 can include a receiving component 902 and / or a sending component 904. In some aspects, the communication manager 908 can include a receiving component 902 and / or a sending component 904. The communication manager 908 can include a data collection component 910, etc.
[0147] In some aspects, the apparatus 900 may be configured to perform Figures 1 to 6 Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 In some aspects, the apparatus 900 and / or Fig. 9 One or more of the components shown in the figure may include a combination of Figure 2 Additionally or alternatively, Fig. 9 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.
[0148] The receiving component 902 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 906. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on the received communications and may provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a described UE.
[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 aspects, one or more other components of the device 900 may generate communications and may provide the generated communications to the transmitting component 904 for transmission to the device 906. In some aspects, the transmitting component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 906. In some aspects, the transmitting component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.
[0150] The receiving component 902 can receive a configuration of a reference signal for data collection and / or a first message indicating that data collection based on the reference signal is allowed. The receiving component 902 can receive the reference signal. The data collecting component 910 can collect data based at least in part on the reference signal. The sending component 904 can send the collected data.
[0151] Receiving component 902 can receive a second message indicating that data collection is not permitted.Data collecting component 910 can stop data collection based at least in part on the second message.
[0152] Receiving component 902 can receive a deactivation DCI scrambled with a data collection deactivation RNTI. Data collection component 910 can stop data collection in response to the deactivation DCI. Data collection component 910 can occupy at least one processing unit per reference signal resource for data collection.
[0153] The sending component 904 may send UE capabilities for supporting data collection, wherein the UE capabilities specify support for one or more of a periodicity of a data collection reference signal, a quantity of ports per resource, a maximum quantity of resources, a maximum quantity of total ports, a quantity of processing units, or a quantity of data collection processes.
[0154] Fig. 9 The number and arrangement of components shown are provided as examples. In practice, there may be Fig. 9 The components shown may include additional components, fewer components, different components, or components arranged in a different manner. Fig. 9 Two or more components shown may be implemented in a single component, or Fig. 9 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The component collection (one or more components) shown may perform the operations described as being performed by Fig. 9 Another component shown may be a collection of components that perform one or more functions.
[0155] Fig.10 1 is a diagram of an example apparatus 1000 for wireless communication. Apparatus 1000 may be a network entity (e.g., base station 110, network entity 510), or a network entity may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using receiving component 1002 and transmitting component 1004. As further shown, apparatus 1000 may include a communication manager 1008. Communication manager 1008 may control and / or otherwise manage one or more operations of receiving component 1002 and / or transmitting component 1004. In some aspects, communication manager 1008 may include a communication manager 1008 in conjunction with receiving component 1002 and / or transmitting component 1004. Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the network entities. The communication manager 1008 may be or be similar to Figure 1 and Figure 2 For example, in some aspects, the communication manager 1008 can be configured to perform one or more of the functions described as being performed by the communication manager 150. In some aspects, the communication manager 1008 can include a receiving component 1002 and / or a sending component 1004. The communication manager 1008 can include a configuration component 1010, etc.
[0156] In some aspects, the apparatus 1000 may be configured to perform Figures 1 to 6 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 The process 800. In some aspects, Fig.10 The apparatus 1000 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.10 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.
[0157] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1006. The receiving component 1002 may provide the received communications to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on the received communications and may provide the processed signals to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described network entities.
[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 aspects, one or more other components of the device 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1006. In some aspects, the transmitting component 1004 may include in conjunction with Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network entities. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.
[0159] The sending component 1004 can send a configuration of a reference signal for data collection and / or a first message indicating that data collection based on the reference signal is allowed. The configuration component 1010 can generate a configuration based on UE capabilities, channel conditions, and / or traffic conditions. The mode component 1004 can send a reference signal.
[0160] Sending component 1004 can send a second message indicating that data collection is not permitted.Receiving component 1002 can receive an indication of UE capabilities for supporting data collection, and the configuration can be based at least in part on the UE capabilities.
[0161] Fig.10 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.10 The components shown may include additional components, fewer components, different components, or components arranged in a different manner. Fig.10Two or more components shown may be implemented in a single component, or Fig.10 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The component collection (one or more components) shown may perform the operations described as being performed by Fig.10 Another component shown may be a collection of components that perform one or more functions.
[0162] The following provides an overview of some aspects of the disclosure:
[0163] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving one or more of a configuration of a reference signal for data collection or a first message indicating that data collection based on the reference signal is allowed; receiving the reference signal; collecting data based at least in part on the reference signal; and sending the collected data.
[0164] Aspect 2: The method according to aspect 1 further includes: receiving a second message indicating that data collection is not allowed; and stopping data collection based at least in part on the second message.
[0165] Aspect 3: The method according to aspect 1 or 2, wherein collecting the data comprises collecting channel measurements based on the reference signal.
[0166] Aspect 4: The method according to any one of aspects 1 to 3, wherein the data is associated with machine learning for channel estimation or configuration of reference signals.
[0167] Aspect 5: The method according to any one of aspects 1 to 4, wherein the configuration specifies that the reference signal is a dedicated reference signal for data collection, and wherein collecting the data includes collecting the data in response to the reference signal being a dedicated reference signal.
[0168] Aspect 6: The method according to aspect 5, wherein the first message activates the dedicated reference signal.
[0169] Aspect 7: A method according to any one of Aspects 1 to 6, wherein the configuration specifies one or more of a cell or carrier identifier (ID), one or more reference resource IDs, a metadata ID, or a resource mapping configuration for the reference resource ID.
[0170] Aspect 8: The method according to aspect 7, wherein the metadata ID includes one or more of beam information associated with sending the reference signal or antenna configuration associated with sending the reference signal.
[0171] Aspect 9: The method according to any one of aspects 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).
[0172] Aspect 10: The method according to aspect 9, wherein the MAC CE includes one or more of a cell 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.
[0173] Aspect 11: The method according to aspect 9, wherein the DCI includes one or more triplets, each of which includes one or more of a cell or carrier ID, a metadata ID, a resource or resource set ID.
[0174] Aspect 12: A method according to aspect 9, wherein the DCI includes one or more of a list of cell or carrier IDs, a list of metadata IDs, or a list of resource or resource set IDs, and wherein there is a one-to-one mapping between entries on the lists.
[0175] Aspect 13: The method according to aspect 9, wherein the DCI includes a list of trigger states, each trigger state includes multiple triplets, each triplet includes a cell or carrier identifier (ID), a metadata ID, and a resource or resource set ID.
[0176] Aspect 14: The method according to aspect 9, wherein the DCI is an activation DCI scrambled with a data collection activation radio network temporary identifier (RNTI).
[0177] Aspect 15: The method according to aspect 14 further comprises: receiving a deactivation DCI scrambled with a data collection deactivation RNTI; and stopping the collection of the data in response to the deactivation DCI.
[0178] Aspect 16: A method according to Aspect 9, wherein the DCI is a group common DCI, and wherein the method includes receiving a radio resource control message, the radio resource control message indicating which triplet, which entry of a list, or which trigger state is used to indicate activation or deactivation of the collection of the data.
[0179] Aspect 17: The method according to aspect 9, wherein the DCI is a group common DCI, and wherein activation or deactivation of the collection of the data is indicated by a bit in each segment.
[0180] Aspect 18: A method according to any one of Aspects 1 to 17, wherein the configuration specifies a channel state information (CSI) report dedicated to data collection, and wherein the method includes determining that a reference signal used for the CSI report is for data collection.
[0181] Aspect 19: A method according to any one of Aspects 1 to 18, wherein the configuration specifies a channel state information (CSI) report and includes a bit or flag indicating that the CSI report is set to a data collection mode, and wherein the method includes determining that a reference signal used for the CSI report is for data collection.
[0182] Aspect 20: The method according to any one of aspects 1 to 19, wherein the first message activates or triggers a channel state information (CSI) report dedicated for data collection or a CSI report for a data collection mode.
[0183] Aspect 21: The method according to any one of aspects 1 to 20, wherein the first message indicates that a channel state information (CSI) feedback mode is changed to nominal CSI reporting, data collection, or both.
[0184] Aspect 22: The method according to any one of aspects 1 to 21, further comprising occupying at least one processing unit per reference signal resource for the collection of the data.
[0185] Aspect 23: The method according to any one of aspects 1 to 22, wherein the collection of the data occupies one or more of the amount of ports per reference signal resource, the amount of reference signal resources, the amount of total ports, or a combination thereof.
[0186] Aspect 24: The method according to any one of Aspects 1 to 23 also includes sending UE capabilities for supporting data collection, wherein the UE capabilities specify support for one or more of the periodicity of data collection reference signals, the amount of ports per resource, the maximum amount of resources, the maximum amount of total ports, the amount of processing units, or the amount of data collection processes.
[0187] Aspect 25: A method of wireless communication performed by a network entity, the method comprising: sending one or more of a configuration of a reference signal for data collection or a first message indicating that data collection based on the reference signal is allowed; sending the reference signal; and receiving data collected at least in part based on the reference signal.
[0188] Aspect 26: The method according to Aspect 25 further includes using the data to train a machine learning model for channel estimation or reference signal configuration.
[0189] Aspect 27: The method according to Aspect 25 or 26 further includes: sending a second message indicating that data collection is not allowed.
[0190] Aspect 28: The method according to any one of aspects 25 to 27, wherein the configuration specifies that the reference signal is a dedicated reference signal for data collection.
[0191] Aspect 29: A method according to any one of Aspects 25 to 28, wherein the configuration specifies one or more of a cell or carrier identifier (ID), one or more reference resource IDs, a metadata ID, or a resource mapping configuration for the reference resource ID.
[0192] Aspect 30: The method according to any one of aspects 25 to 29, further comprising receiving an indication of UE capabilities for supporting data collection, and wherein the configuration is based at least in part on the UE capabilities.
[0193] Aspect 31: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 30.
[0194] Aspect 32: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 30.
[0195] Aspect 33: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 30.
[0196] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 30.
[0197] Aspect 35: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 30.
[0198] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.
[0199] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be clear that the system or method described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code to describe the operation and behavior of the system and / or method herein, because those 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 description herein.
[0200] As used herein, "satisfying a threshold" may refer to a value being 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, not equal to a threshold, etc., depending on the context.
[0201] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically listed in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., 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 ordering of a, b and c).
[0202] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. In addition, as used herein, the articles "one" and "an" are intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the article "the" is intended to include one or more items connected to the article "the" mentioned, and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items and can be used interchangeably with "one or more". If you only want to refer to an item, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").
Claims
1. A user equipment (UE) for wireless communication, the user equipment (UE) include: Memory; and one or more processors coupled to the memory, the one or more processors configured to: receiving one or more of configuration of a reference signal for data collection or a first message indicating that data collection based on the reference signal is permitted; receiving the reference signal; collecting data based at least in part on the reference signal; as well as The collected data is transmitted.
2. The UE of claim 1, wherein the one or more processors are configured to: receiving a second message indicating that data collection is not permitted; and Data collection is stopped based at least in part on the second message. 3 . The UE of claim 1 , wherein to collect the data, the one or more processors are configured to collect channel measurements based on the reference signal.
4. The UE of claim 1, wherein the data is associated with machine learning for channel estimation or configuring a reference signal.
5. The UE of claim 1 , wherein the configuration specifies that the reference signal is a dedicated reference signal for data collection, and wherein to collect the data, the one or more processors are configured to collect the data in response to the reference signal being a dedicated reference signal. The UE according to claim 5 , wherein the first message activates the dedicated reference signal.
7. The UE of claim 1, wherein the configuration specifies one or more of a cell or carrier identifier (ID), one or more reference resource IDs, a metadata ID, or a resource mapping configuration for the reference resource IDs.
8. The UE of claim 7, wherein the metadata ID comprises one or more of beam information associated with sending the reference signal or an antenna configuration associated with sending the reference signal.
9. The UE of claim 1, wherein to receive the first message, the one or more processors are configured to receive the first message in a medium access control control element (MAC CE) or downlink control information (DCI).
10. The UE of claim 9, wherein the MAC CE comprises one or more of a cell 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 of claim 9, wherein the DCI comprises one or more triplets, each of the one or more triplets comprising one or more of a cell or carrier ID, a metadata ID, or a resource or resource set ID.
12. The UE of claim 9, wherein the DCI comprises one or more of a list of cell or carrier IDs, a list of metadata IDs, or a list of resource or resource set IDs, and wherein there is a one-to-one mapping between entries on the lists.
13. The UE according to claim 9, wherein the DCI comprises a list of trigger states, each trigger state comprises a plurality of triplets, each triplet comprises a cell or carrier identifier (ID), a metadata ID, and a resource or resource set ID.
14. The UE of claim 9, wherein the DCI is an activation DCI scrambled with a data collection activation radio network temporary identifier (RNTI).
15. The UE of claim 14, wherein the one or more processors are configured to: receiving a deactivation DCI scrambled with a data collection deactivation RNTI; and The collection of the data is stopped in response to the deactivating DCI.
16. The UE of claim 9, wherein the DCI is a group common DCI, and wherein the one or more processors are configured to receive a radio resource control message indicating which triplet, which entry of a list, or which trigger state is used to indicate activation or deactivation of the collection of the data.
17. The UE of claim 9, wherein the DCI is a group common DCI, and wherein activation or deactivation of the collection of the data is indicated by a bit in each segment.
18. The UE of claim 1, wherein the configuration specifies a channel state information (CSI) report dedicated to data collection, and wherein the one or more processors are configured to determine that a reference signal used for the CSI report is for data collection.
19. The UE of claim 1, wherein the configuration specifies a channel state information (CSI) report and includes a bit or flag indicating that the CSI report is set to a data collection mode, and wherein the one or more processors are configured to determine that a reference signal used for the CSI report is for data collection.
20. The UE of claim 1, wherein the first message activates or triggers a channel state information (CSI) report dedicated for data collection or a CSI report for a data collection mode.
21. The UE of claim 1, wherein the first message indicates that a channel state information (CSI) feedback mode is changed to nominal CSI reporting, data collection, or both.
22. The UE of claim 1, wherein the one or more processors are configured to occupy at least one processing unit per reference signal resource for the collection of the data.
23. The UE of claim 1, wherein the collection of the data occupies one or more of an amount of ports per reference signal resource, an amount of reference signal resources, an amount of total ports, or a combination thereof.
24. A UE according to claim 1, wherein the one or more processors are configured to send UE capabilities for supporting data collection, wherein the UE capabilities specify support for one or more of the periodicity of data collection reference signals, the amount of ports per resource, the maximum amount of resources, the maximum amount of total ports, the amount of processing units, or the amount of data collection processes.
25. A network entity for wireless communication, the network entity include: Memory; and one or more processors coupled to the memory, the one or more processors configured to: sending one or more of a configuration of a reference signal for data collection or a first message indicating that data collection based on the reference signal is permitted; and The reference signal is sent.
26. The network entity of claim 25, wherein the one or more processors are configured to use the data to train a machine learning model for channel estimation or reference signal configuration.
27. The network entity of claim 25, wherein the one or more processors are configured to send a second message indicating that data collection is not permitted.
28. The network entity of claim 25, wherein the configuration specifies that the reference signal is a dedicated reference signal for data collection.
29. The network entity of claim 25, wherein the configuration specifies one or more of a cell or carrier identifier (ID), one or more reference resource IDs, a metadata ID, or a resource mapping configuration for the reference resource IDs.
30. The network entity of claim 25, wherein the one or more processors are configured to receive an indication of UE capabilities for supporting data collection, and wherein the configuration is based at least in part on the UE capabilities.
Citation Information
Cited By
Communication method, communication apparatus and system
WO2026200865A1
