Measurement reporting using lookup tables

By introducing lookup tables (LUTs) into wireless communication systems for L1 RSRP/SINR measurement reporting, the problem of excessive bit requirements in existing technologies is solved, thereby reducing signaling overhead and improving network performance.

CN120898379APending Publication Date: 2025-11-04QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480018179.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-03-17
Filing Date
2024-02-16
Publication Date
2025-11-04

AI Technical Summary

Technical Problem

Existing wireless communication systems suffer from excessive bit requirements when measuring Report Layer 1 Reference Signal Received Power (RSRP) and Signal-to-Interference-plus-Noise Ratio (SINR), leading to increased signaling overhead and network congestion, especially when monitoring multiple cells and beam prediction are required.

Method used

A lookup table (LUT) is used to reduce the number of bits. By reporting L1 RSRP/SINR measurements between the user equipment (UE) and the network node, the UE determines the corresponding entry based on the received reference signal and the LUT search, and sends a report indicating the entry to the network node.

Benefits of technology

By using LUTs, the number of bits required for L1 RSRP/SINR measurement reports is reduced, signaling overhead is decreased, the performance of UEs and network nodes is improved, and network congestion is reduced.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120898379A_ABST
    Figure CN120898379A_ABST
Patent Text Reader

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a reference signal associated with beam management from a network node. The UE may perform a Layer 1 (L1) Reference Signal Received Power (RSRP) or L1 Signal to Interference plus Noise Ratio (SINR) (RSRP / SINR) measurement based at least in part on the reference signal. The UE may determine an entry in a lookup table (LUT) corresponding to the L1 RSRP / SINR measurement based at least in part on a search for the LUT. The UE may send, to the network node, an L1 RSRP / SINR measurement report indicating the entry in the LUT. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 185,940, filed March 17, 2023, entitled “MEASUREMENT REPORTING USING A LOOKUP TABLE”, which is assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0003] All aspects of this disclosure relate to wireless communication, and to techniques and apparatus for measurement reporting using lookup tables (LUTs). Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable 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 issued by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with network nodes via downlink and uplink communication. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via local links (e.g., sidelinks (SL), wireless local area network (WLAN) links, and / or wireless personal area network (WPAN) links, etc.).

[0006] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, and / or global levels. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband internet access by: improving spectrum efficiency; reducing costs; improving service; utilizing new spectrum; and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink; and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technologies and carrier aggregation. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to increase. Summary of the Invention

[0007] In some implementations, an apparatus for wireless communication at a user equipment (UE) includes: a memory and one or more processors coupled to the memory and configured to: receive a reference signal associated with beam management from a network node; perform a Layer 1 (L1) reference signal received power (RSRP) or L1 signal-to-interference-plus-noise ratio (SINR) (RSRP / SINR) measurement based at least in part on the reference signal; determine, at least in part on a search of a lookup table (LUT), an entry in the LUT corresponding to the L1 RSRP / SINR measurement; and send an L1 RSRP / SINR measurement report to the network node indicating the entry in the LUT.

[0008] In some specific implementations, an apparatus for wireless communication at a network node includes: a memory and one or more processors coupled to the memory and configured to: transmit a reference signal associated with beam management to a UE; and receive from the UE an L1 RSRP / SINR measurement report at least in part based on the reference signal, wherein the L1 RSRP / SINR measurement report indicates an entry in a LUT corresponding to an L1 RSRP / SINR measurement.

[0009] In some specific implementations, a method of wireless communication performed by a UE includes: receiving a reference signal associated with beam management from a network node; performing an L1 RSRP / SINR measurement based at least in part on the reference signal; determining, at least in part on a search of a LUT, an entry in the LUT corresponding to the L1 RSRP / SINR measurement; and sending an L1 RSRP / SINR measurement report indicating the entry in the LUT to the network node.

[0010] In some specific implementations, a method of wireless communication performed by a network node includes: transmitting a reference signal associated with beam management to a UE; and receiving from the UE an L1 RSRP / SINR measurement report based at least in part on the reference signal, wherein the L1 RSRP / SINR measurement report indicates an entry in a LUT corresponding to an L1 RSRP / SINR measurement.

[0011] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive a reference signal associated with beam management from a network node; perform an L1 RSRP / SINR measurement based at least in part on the reference signal; determine, at least in part on a search of a LUT, an entry in the LUT corresponding to the L1 RSRP / SINR measurement; and send an L1 RSRP / SINR measurement report to the network node indicating the entry in the LUT.

[0012] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: send a reference signal associated with beam management to a UE; and receive from the UE an L1 RSRP / SINR measurement report at least in part based on the reference signal, wherein the L1 RSRP / SINR measurement report indicates an entry in a LUT corresponding to an L1 RSRP / SINR measurement.

[0013] In some specific implementations, an apparatus for wireless communication includes: components for receiving a reference signal associated with beam management from a network node; components for performing an L1 RSRP / SINR measurement based at least in part on the reference signal; components for determining, at least in part on a search of a LUT, an entry in the LUT corresponding to the L1 RSRP / SINR measurement; and components for sending an L1 RSRP / SINR measurement report to the network node indicating the entry in the LUT.

[0014] In some specific implementations, an apparatus for wireless communication includes: components for transmitting a reference signal associated with beam management to a UE; and components for receiving from the UE an L1 RSRP / SINR measurement report at least in part based on the reference signal, wherein the L1 RSRP / SINR measurement report indicates an entry in a LUT corresponding to an L1 RSRP / SINR measurement.

[0015] The entirety of the terms includes methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the accompanying drawings and description and illustrated as illustrated in the drawings and description.

[0016] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily utilized as the basis for modifying or designing other structures for achieving the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the drawings provided is for illustrative and descriptive purposes and not as a definition of limitation of the claims.

[0017] While aspects are described herein by way of example, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). 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. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user equipment of various sizes, shapes, and configurations. Attached Figure Description

[0018] To gain a full understanding of the foregoing features of this disclosure, a more specific description of the invention, briefly outlined above, can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered as limiting its scope, as the description acknowledges other equally valid aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 This is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 This is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0022] Figure 4 This is a diagram illustrating an example of a beam management process according to this disclosure.

[0023] Figure 5 This is a diagram illustrating an example of a measurement report associated with the use of a lookup table (LUT) according to this disclosure.

[0024] Figures 6 to 7 This is a diagram illustrating an example process associated with measurement reporting using a LUT according to this disclosure.

[0025] Figures 8 to 9 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0026] Layer 1 (L1) Reference Signal Received Power (RSRP) or L1 Signal-to-Interference-plus-Noise Ratio (SINR) (RSRP / SINR) measurement reports can use a specific number of bits to indicate a specific RSRP / SINR value. For example, 40 to 50 bits can be used to report four RSRP / SINR values ​​in an L1 RSRP / SINR measurement report. However, for some applications, it may be necessary to report additional RSRP / SINR values. For example, when monitoring Synchronization Signal Blocks (SSBs) of multiple cells, the UE may need to report 40 bits or more for each cell, which can be a considerable payload. Furthermore, for some applications, the differential RSRP / SINR values ​​of four beams may not be sufficient. For example, for beam prediction using Artificial Intelligence (AI) or Machine Learning (ML), eight or 16 beams may be needed to predict the RSRP / SINR value of the Narrow Channel State Information Reference Signal (CSI-RS) beam based on the measured RSRP / SINR values ​​of the SSB beams. Therefore, for some applications, it may be necessary to reduce or compress the number of bits used to report L1 RSRP / SINR values ​​to network nodes.

[0027] In some aspects described herein, the UE may receive a reference signal associated with beam management from a network node. The UE may perform L1 RSRP / SINR measurements based at least in part on this reference signal. The UE may determine the entry in a lookup table (LUT) corresponding to the L1 RSRP / SINR measurement based at least in part on a search of the LUT. In other words, the UE may search the LUT, which may be locally stored at the UE, for the entry matching the L1 RSRP / SINR measurement. The entry in the LUT may correspond to a beam index associated with the L1 RSRP / SINR measurement and / or an RSRP / SINR value associated with the L1 RSRP / SINR measurement. The UE may send an L1 RSRP / SINR measurement report to the network node indicating the entry in the LUT. In some aspects, the UE may use the LUT to reduce the number of bits required for the L1 RSRP / SINR measurement report. This L1 RSRP / SINR measurement report uses fewer bits, which can be useful for certain applications that require additional RSRP / SINR values ​​(e.g., AI / ML-based beam prediction). The reduced signaling overhead resulting from this L1 RSRP / SINR measurement report can improve the performance of the UE and / or the network node, and reduce network congestion.

[0028] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or method of practice. Furthermore, the scope of this disclosure is intended to cover such apparatus or methods practiced using structures, functions, or structures and functions other than or different from the aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of these claims.

[0029] Various devices and techniques will now be used to illustrate several aspects of a telecommunications system. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may 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 system as a whole.

[0030] Although terms generally associated with 5G or New Radio (NR) Radio Access Technology (RAT) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or 5G and later (e.g., 6G) RATs.

[0031] Figure 1This 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., LTE) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. Network node 110 is a network node that communicates with UE 120. As shown, network node 110 may include one or more network nodes. For example, network node 110 can be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0032] In some examples, network node 110 is or includes network nodes (such as RUs) that communicate with UE 120 via a radio access link. In some examples, network node 110 is or includes network nodes (such as DUs) that communicate with other network nodes 110 via a fronthaul or midhaul link. In some examples, network node 110 is or includes network nodes (such as CUs) that communicate with other network nodes 110 via a midhaul link or with the core network via a backhaul link. In some examples, network node 110 (such as aggregated network node 110 or decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, Transmit / Receive Points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, network nodes 110 can interconnect with each other or with one or more other network nodes 110 in the wireless network 100 using any suitable transport network through various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0033] In some examples, network node 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term "cell" may refer to the coverage area of ​​network node 110 and / or the network node subsystem serving that coverage area. Network node 110 may provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). Network node 110 used for macrocells may be referred to as a macro network node. Network node 110 used for picocells may be referred to as a pico network node. The network node 110 used for femtocells can be referred to as a femtocell network node or a home network node. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 102a, network node 110b can be a pico network node for pico cell 102b, and network node 110c can be a femto network node for femto cell 102c. Network nodes can support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0034] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, "base station" or "network node" may refer to a CU, DU, 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 node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of that function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions can be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function rather than another. In this way, a single device can include more than one base station.

[0035] Wireless network 100 may include one or more relay stations. A relay station is a network node that can receive data transmissions from upstream nodes (e.g., network node 110 or UE 120) and transmit data to downstream nodes (e.g., UE 120 or network node 110). A relay station may be a UE 120 that can relay transmissions for other UE 120s. Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. The network node 110 for relay communication may be referred to as a relay station, relay base station, relay network node, relay node, relay, etc.

[0036] Wireless network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different effects on interference in wireless network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0037] Network controller 130 may be coupled to or communicate with a group of network nodes 110, and may provide coordination and control for these network nodes 110. Network controller 130 may communicate with network nodes 110 via a backhaul or midhaul link. Network nodes 110 may also communicate directly with each other, or indirectly via a wireless or wired backhaul link. In some aspects, network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

[0038] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 may be a cellular phone (e.g., a smartphone), 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 smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, a UE function of a network node, and / or any other suitable device configured to communicate via wireless or wired media.

[0039] Some UEs 120 may be considered 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 that can communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UEs 120 may be included within a housing that houses the components of the UE 120, such as processor components and / or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

[0041] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary device to communicate with each other). 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 network node 110.

[0042] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although this is different from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0043] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been identified as the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0044] Considering the examples above, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" is used herein, it can broadly refer to frequencies below 6 GHz, within FR1, or including intermediate frequency bands. Furthermore, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" is used herein, it can broadly refer to frequencies that can include intermediate frequency bands, within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or within the EHF band. Modifications to frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) are contemplated, and the techniques described herein are applicable to those modified frequency ranges.

[0045] In some aspects, the 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 reference signal associated with beam management from a network node; perform an L1 RSRP / SINR measurement based at least in part on the reference signal; determine, at least in part on a search of a LUT, an entry in the LUT corresponding to the L1 RSRP / SINR measurement; and send an L1 RSRP / SINR measurement report to the network node indicating the entry in the LUT. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0046] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may transmit a reference signal associated with beam management to the UE; and receive from the UE an L1 RSRP / SINR measurement report at least in part based on the reference signal, wherein the L1 RSRP / SINR measurement report indicates an entry in the LUT corresponding to the L1 RSRP / SINR measurement. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0047] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0048] Figure 2 This is a diagram illustrating example 200 of communication between network node 110 and UE 120 in a wireless network 100 according to this disclosure. Network node 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). Network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and modems 232. In some examples, network node 110 may include an interface, communication components, or another component facilitating communication with UE 120 or another network node. Some network nodes 110 may not include radio frequency components facilitating direct communication with UE 120, such as one or more CUs or one or more DUs.

[0049] At network node 110, transmitting processor 220 can receive data from data source 212 intended for use by UE 120 (or a group of UEs 120). Transmitting processor 220 can select one or more modulation and decoding schemes (MCS) for UE 120, at least in part, based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 can process (e.g., encode and modulate) the data for UE 120, at least in part, based on the MCS selected for UE 120, and can provide data symbols for UE 120. Transmitting processor 220 can process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper-layer signaling), and provide overhead symbols and control symbols. Transmitting processor 220 can 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 signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide a set of output symbol streams (e.g., T output symbol streams) to a set of corresponding modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream can be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can also use a corresponding modulator component to process the output sample stream (e.g., convert to analog, amplify, filter, and / or up-convert) to obtain a downlink signal. Modems 232a to 232t can transmit a set of downlink signals (e.g., T downlink signals) via a set of corresponding antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0050] At UE 120, a set of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 and / or other network nodes 110 and can 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 can be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain an input sample. Each modem 254 can use the demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from modem 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. The receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine RSRP parameters, Received Signal Strength Indicator (RSSI) parameters, Reference Signal Received Quality (RSRQ) parameters, and / or CQI parameters, etc. In some examples, one or more components of UE 120 may be included in housing 284.

[0051] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, for example, in a core network. Network controller 130 may communicate with network node 110 via communication unit 294.

[0052] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include 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., or may 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 (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements and / or be coupled to one or more transmitting and / or receiving components (such as...). Figure 2 One or more antenna elements (one or more components in a )

[0053] On the uplink, at UE 120, the transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 can generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 can 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 transmitted to network node 110. In some examples, the modem 254 of UE 120 may include a modulator and demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to execute this document (e.g., reference). Figures 5 to 9 ( ) any aspect of the methods described in the method.

[0054] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., 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 the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communication. In some examples, modem 232 of network node 110 may include modulator and demodulator. In some examples, network node 110 includes 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 execute this document (e.g., reference). Figures 5 to 9 ( ) any aspect of the methods described in the method.

[0055] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120 and / or Figure 2Any other component may perform one or more techniques associated with measurement reporting using the LUT, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component that can execute or direct, for example Figure 6 Process 600 Figure 7 The operation of process 700 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 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 may, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, transformation, and / or interpretation), cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example... Figure 6 Process 600 Figure 7 The operation of process 700 and / or other processes as described herein. In some examples, the execution instructions may include run instructions, transformation instructions, compilation instructions, and / or interpretation instructions, etc.

[0056] In some aspects, the UE (e.g., UE 120) includes: components for receiving a reference signal associated with beam management from a network node; components for performing L1 RSRP / SINR measurements based at least in part on the reference signal; components for determining, at least in part on a search of a LUT, an entry in the LUT corresponding to the L1 RSRP / SINR measurement; and / or components for sending an L1 RSRP / SINR measurement report to the network node indicating the entry in the LUT. Components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0057] In some aspects, a network node (e.g., network node 110) includes: components for transmitting a reference signal associated with beam management to the UE; and / or components for receiving from the UE an L1 RSRP / SINR measurement report at least partially based on the reference signal, wherein the L1 RSRP / SINR measurement report indicates an entry in the LUT corresponding to an L1 RSRP / SINR measurement. Components for the network node to perform the operations described herein may include one or more of, for example, a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0058] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0059] As indicated above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The examples described are different.

[0060] The deployment of communication systems (such as 5G NR systems) can involve various components or parts arranged in a variety of ways. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in either a converged or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or components) performing base station functionality can be implemented as a converged base station (also known as a standalone base station or monolithic base station) or a decomposed base station. A "network entity" or "network node" can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or combinations thereof).

[0061] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0062] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed independently. Decomposed base stations can include functionality implemented by two or more units across various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. The various units of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0063] Figure 3 This is an illustration of an example disaggregated base station architecture 300 according to this disclosure. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more disaggregated control units (such as 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 a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0064] Each unit in the clusters (including CU 310, DU 330, RU 340), as well as the near-RT RIC 325, non-RT RIC 315, and SMO frame 305, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the cluster, or an associated processor or controller providing instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more units in other clusters via transmission media. In some examples, each unit in the cluster may include a wired interface and a wireless interface configured to receive signals via a wired transmission media or transmit signals to one or more units in other clusters, and the wireless interface may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals via a wireless transmission media or transmit signals to one or more units in other clusters, or both.

[0065] In some aspects, the CU 310 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, or Service Data Adaptation Protocol (SDAP) functions, etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP) functions), control plane functions (e.g., Central Unit-Control Plane (CU-CP) functions), or combinations thereof. In some implementations, the CU 310 can 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 units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be implemented to communicate with the DU 330 for network control and signaling purposes, as needed.

[0066] Each DU 330 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, the DU 330 may host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to functional splits (such as those defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as those implemented by one or more modules for Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0067] Each RU 340 can implement low-level functionality. In some deployments, an RU 340 controlled by a DU 330 can correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, based on function splitting (e.g., function splitting defined by 3GPP) (such as low-level function splitting). In this architecture, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UE 120s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration allows each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0068] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 305 can be configured to interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTTRIC 325. In some specific implementations, the SMO framework 305 may communicate with 4G RAN hardware aspects such as the Open eNB (O-eNB) 311 via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0069] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325, such as via an A1 interface. The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

[0070] In some implementations, to generate AI / ML models 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. This information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or network functions 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 in performance and employ AI / ML models to perform corrective actions via the SMO framework 305 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0071] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0072] Figure 4 These are illustrations of examples 400, 410, and 420 illustrating beam management processes according to this disclosure. Figure 4 As shown, Examples 400, 410, and 420 include UE 120 communicating with network node 110 in a wireless network (e.g., wireless network 100). However, Figure 4 The device shown is provided as an example, and the wireless network can support communication and beam management between other devices (e.g., between UE 120 and network node 110 or TRP, between mobile terminal node and control node, between IAB child node and IAB parent node, and / or between scheduled node and scheduling node). In some aspects, UE 120 and network node 110 may be in a connected state (e.g., RRC connected state).

[0073] like Figure 4 As shown, Example 400 may include a network node 110 (e.g., one or more network node devices such as RU, DU, and / or CU) communicating with UE 120 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 4As shown in Example 400, CSI-RS can be configured to be transmitted from network node 110 to UE 120. CSI-RS can be configured to be periodic (e.g., using RRC signaling), semi-persistent (e.g., using Media Access Control (MAC) Control Element (MAC-CE) signaling), and / or non-periodic (e.g., using Downlink Control Information (DCI)).

[0074] The first beam management process may include network node 110 performing beam scanning on multiple transmit (Tx) beams. Network node 110 may use each transmit beam for beam management to transmit CSI-RS. To enable UE 120 to perform receive (Rx) beam scanning, the network node may use the transmit beams to transmit (e.g., with repetition) each CSI-RS multiple times within the same RS resource set, allowing UE 120 to scan the receive beams in multiple transmit instances. For example, if network node 110 has a set of N transmit beams and UE 120 has a set of M receive beams, then CSI-RS may be transmitted M times on each of the N transmit beams, allowing UE 120 to receive M instances of CSI-RS per transmit beam. In other words, for each transmit beam of network node 110, UE 120 may perform beam scanning of UE 120's receive beams. Therefore, the first beam management procedure enables UE 120 to measure CSI-RS on different transmit beams using different receive beams to support the selection of beam pairs for the transmit beam of network node 110 / receive beam of UE 120. UE 120 may report the measurements to network node 110 so that network node 110 can select one or more beam pairs for communication between network node 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 similar manner as described above.

[0075] like Figure 4 As shown, Example 410 may include network node 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). This second beam management procedure may be referred to as a beam refinement procedure, a network node beam refinement procedure, a TRP beam refinement procedure, and / or a transmit beam refinement procedure. Figure 4As shown in Example 410, CSI-RS can be configured to be transmitted from network node 110 to UE 120. The CSI-RS can be configured to be aperiodic (e.g., using DCI). A second beam management procedure may include network node 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 network node 110 (e.g., determined at least in part based on measurements reported by UE 120 in conjunction with the first beam management procedure). Network node 110 may transmit CSI-RS using each of the one or more transmit beams used for beam management. 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). This second beam management procedure enables network node 110 to select the optimal transmit beam at least in part based on (e.g., measurements taken by UE 120 using a single receive beam) the measurements of CSI-RS reported by UE 120.

[0076] like Figure 4 As shown, Example 420 depicts a third beam management process (e.g., P3 CSI-RS beam management). This third beam management process may be referred to as a beam refinement process, a UE beam refinement process, and / or a receive beam refinement process. Figure 4 As shown in Example 420, one or more CSI-RS can be configured to be transmitted from network node 110 to UE 120. The CSI-RS can be configured to be non-periodic (e.g., using DCI). The third beam management procedure may include network node 110 transmitting 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). To enable UE 120 to perform receive beam scanning, the network node may transmit (e.g., with repetition) CSI-RS multiple times within the same RS resource set using the transmit beam, allowing UE 120 to scan 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). This third beam management process enables network node 110 and / or UE 120 to select the optimal receive beam based at least in part on reported measurements received from UE 120 (e.g., reported measurements of the CSI-RS of the transmit beam using one or more receive beams).

[0077] As indicated above, Figure 4This is provided as an example of a beam management process. Other examples of beam management processes may be provided relative to... Figure 4 The examples described are different. For example, UE 120 and network node 110 may perform the third beam management procedure before performing the second beam management procedure, and / or UE 120 and network node 110 may perform a similar beam management procedure to select the UE transmit beam.

[0078] During beam management, a network node may transmit multiple reference signals associated with different beams. As part of beam scanning, the network node may transmit these multiple reference signals. The UE may perform measurements on these multiple reference signals. The UE may prepare a measurement report based at least in part on these measurements. The UE may send this measurement report to the network node. This measurement report may be an L1 RSRP measurement report or an L1 SINR measurement report. The L1 RSRP / SINR measurement report may indicate the beam index, RSRP / SINR value, and differential RSRP / SINR value. The beam index may be encoded using six or seven bits. Among the reported RSRP / SINR values, the strongest RSRP / SINR value (e.g., from -140 dBm to -45 dBm, with a resolution of 1 dB) may be reported using seven bits, and the remaining RSRP / SINR values ​​(e.g., from 0 dBm to -30 dB, with a resolution of 2 dB) may be reported using four bits, at least in part, based on the differential RSRP / SINR.

[0079] As an example, the L1 RSRP / SINR measurement report can indicate four RSRP / SINR measurements. For 64 SSBs, 7 + (4 × 3) bits (19 bits) can be used to report the strongest RSRP / SINR value, and (6 × 4) bits (24 bits) can be used to report the differential RSRP / SINR values, for a total of 43 bits. To report four RSRP / SINR measurements out of 128 CSI-RS, 47 bits can be used.

[0080] The CSI-RS Resource Indicator (CRI) can be associated with a defined bit width. The SSB Resource Indicator (SSBRI) can be associated with a defined bit width. The RSRP / SINR value can be associated with a bit width of seven. The differential RSRP / SINR value can be associated with a bit width of four. Channel State Information (CSI) reports may include multiple CSI fields. For example, a CSI report may indicate CRI or SSBRI#1, CRI or SSBRI#2, CRI or SSBRI#3, CRI or SSBRI#4, RSRP / SINR#1, differential RSRP / SINR#2, differential RSRP / SINR#3, and / or differential RSRP / SINR#4.

[0081] Four RSRP / SINR values ​​can be reported in the L1 RSRP / SINR measurement report using 40 to 50 bits, which can be at least partially based on the beam index, RSRP / SINR value, and differential RSRP / SINR value indicated in the L1 RSRP / SINR measurement report. However, as mentioned above, for some applications, it may be necessary to report additional RSRP / SINR values. For example, when monitoring SSBs of multiple cells, the UE may need to report 40 bits or more for each cell, which can be a considerable payload. Furthermore, for some applications, the differential RSRP / SINR values ​​for four beams may not be sufficient. For example, for beam prediction using AI / ML, eight or 16 beams may be needed to predict the RSRP / SINR value of the narrow CSI-RS beam based on the measured RSRP / SINR values ​​of the SSB beam. Therefore, for some applications, it may be necessary to reduce or compress the number of bits used to report the L1 RSRP / SINR value to the network node.

[0082] In various aspects of the technologies and apparatus described herein, the UE can receive a reference signal associated with beam management from a network node. The UE can perform L1 RSRP / SINR measurements at least in part based on this reference signal. The UE can determine, at least in part, the entry in a LUT corresponding to the L1 RSRP / SINR measurement based on a search of the LUT. In other words, the UE can search the LUT, which may be locally stored at the UE, for an entry matching the L1 RSRP / SINR measurement. The entry in the LUT may correspond to a beam index associated with the L1 RSRP / SINR measurement and / or an RSRP / SINR value associated with the L1 RSRP / SINR measurement. The UE can send an L1 RSRP / SINR measurement report indicating the entry in the LUT to the network node.

[0083] In some respects, the UE can use the LUT for the L1 RSRP / SINR measurement report. The UE can use the LUT to reduce the number of bits required for the L1 RSRP / SINR measurement report. The LUT can be built online, used alone for the UE, or used in conjunction with multiple UEs. The LUT can be updated when a new L1 RSRP / SINR measurement is not represented by an entry in the LUT. The LUT can be compressed, which further reduces the number of bits required for the L1 RSRP / SINR measurement report. The LUT can be configured using an L1 RSRP / SINR configuration message, which can be sent over the air from the network node to the UE. The UE can report entries from the LUT indicating the L1 RSRP / SINR measurement to the network node. The UE can report this entry using an L1 RSRP / SINR reporting format. Therefore, the L1 RSRP / SINR measurement report can use fewer bits, which may be useful for certain applications that require appended RSRP / SINR values ​​(e.g., AI / ML-based beam prediction). The reduction in signaling overhead resulting from the L1RSRP / SINR measurement report can improve the performance of the UE and / or the network node, and can reduce network congestion.

[0084] Figure 5 This is a diagram illustrating example 500 associated with a measurement report using a LUT according to this disclosure. Figure 5 As shown, Example 500 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100).

[0085] As shown by reference numeral 502 in the attached figure, the UE can receive a reference signal associated with beam management from the network node. This reference signal can be associated with a beam. The reference signal can be one of multiple reference signals associated with different beams. As part of a beam scan, the network node can transmit these multiple reference signals. These reference signals can be CSI-RS or SSB.

[0086] As indicated by reference numeral 504, the UE can perform L1 RSRP / SINR measurements at least in part based on the reference signal. In other words, the UE can measure the L1 RSRP / SINR value associated with the reference signal received from the network node.

[0087] As shown by reference numeral 506 in the accompanying drawings, the UE can determine, at least in part, the entry in the LUT corresponding to the L1 RSRP / SINR measurement based on a search of the LUT. The UE can search the LUT for the entry corresponding to the L1 RSRP / SINR measurement. The entry in the LUT may correspond to a beam index associated with the L1 RSRP / SINR measurement and / or an RSRP / SINR value associated with the L1 RSRP / SINR measurement. In some aspects, the LUT may include a first LUT and a second LUT, wherein the first LUT may include a beam index associated with the L1 RSRP / SINR measurement, and the second LUT may include an RSRP / SINR value associated with the L1 RSRP / SINR measurement. The UE can search the first LUT for entries matching the beam index associated with the L1 RSRP / SINR measurement. The UE can search the second LUT for entries matching the RSRP / SINR value associated with the L1 RSRP / SINR measurement. In some respects, the LUT can be a single LUT that includes a beam index and an RSRP / SINR value associated with the L1 RSRP / SINR measurement. The UE can search for the LUT against an index that matches both the beam index associated with the L1 RSRP / SINR measurement and the RSRP / SINR value associated with the L1 RSRP / SINR measurement.

[0088] In some respects, the entry in the LUT corresponding to the L1 RSRP / SINR measurement may be the closest entry in the LUT corresponding to the L1 RSRP / SINR measurement. The UE may determine, at least in part, based on a search of the LUT, that no existing entry in the LUT matches the L1 RSRP / SINR measurement. In other words, the UE may not find a beam index and / or RSRP / SINR value associated with the L1 RSRP / SINR measurement in the LUT, but the UE may find another beam index and / or RSRP / SINR value that is relatively close to the L1 RSRP / SINR measurement in the LUT. The difference between the beam index and / or RSRP / SINR value may be within a threshold. The UE may select an entry in the LUT associated with a relatively close beam index and / or RSRP / SINR value.

[0089] As an example, to report four L1 RSRP / SINR values ​​from 64 RSRP / SINR measurements, the number of all possible beam indices is 64 × 63 × 62 × 61 = 15,249,024, and the number of all possible RSRP / SINR values ​​is 95 × 16 × 16 × 16 = 389,120, but not all combinations will occur. In some aspects, in LUT-based schemes, the LUT can be constructed using beam indices and / or RSRP / SINR values ​​that occur relatively frequently in the environment. The UE can perform new measurements, and the UE may need to report the corresponding beam indices and RSRP / SINR values. When a corresponding beam index and / or RSRP / SINR value is indicated in the LUT, the UE can report the entry for that beam index and / or RSRP / SINR value in the LUT. In other words, the UE may not report the beam index and / or RSRP / SINR value itself, but instead report the entry from the LUT corresponding to that beam index and / or RSRP / SINR value. When the UE performs a new measurement and the corresponding beam index and / or RSRP / SINR value is not in the LUT, the UE may report the closest entry in the LUT. For example, the UE may report the beam index and / or RSRP / SINR value in the LUT that is relatively close to the new measurement's corresponding beam index and / or RSRP / SINR value. The closest entry in the LUT may be based at least in part on bitstream distance (which may be based at least in part on Hamming distance associated with the beam) and sorted by the beam's RSRP / SINR value.

[0090] In some aspects, the UE may receive from the network node the LUT comprising multiple entries corresponding to possible L1 RSRP / SINR measurements. The UE may store the LUT in its memory. When an entry corresponding to an L1 RSRP / SINR measurement is determined in the LUT, the UE may access the LUT, which may be locally stored on the UE. The LUT may be locally stored by both the network node and the UE. In some aspects, the LUT may be an ordered LUT based at least in part on the natural order of the bit stream stored in the LUT. The beam index and / or RSRP / SINR values ​​may be represented by a bit stream, and the bit stream may be arranged in a specific order (e.g., from lowest to highest value), which allows the UE to search the LUT for entries in the LUT with low complexity.

[0091] In some respects, the LUT can be a UE-specific LUT. In other words, the LUT can be dedicated to that UE. In other respects, the LUT can be a public LUT shared by multiple UEs. In this case, the network node can send the same LUT to multiple UEs.

[0092] In some aspects, the network node can construct a LUT. The network node can send the LUT to the UE. The LUT can be stored locally at both the network node and the UE. In other aspects, the network node can construct different LUTs for different UEs. The network node can send different LUTs to different UEs separately. In some aspects, multiple UEs can share the same LUT. When the LUTs of different UEs have a relatively large amount of overlap, the network node can construct a common LUT by taking the union of the LUTs of different UEs. The network node can broadcast or multicast the common LUT to different UEs. Furthermore, the sharing of a common LUT can be at least partially based on location. For example, the network node can share the common LUT only with UEs within a specific distance from the network node.

[0093] In some aspects, for L1 measurements, the UE can generate a bitstream for beam indexing and RSRP / SINR values. When the bitstream is not currently represented by a LUT, entries for the bitstream can be added to that LUT. The network node can construct a LUT for RSRP / SINR values ​​(e.g., a first LUT for RSRP / SINR values). For example, the network node can construct a LUT for the RSRP / SINR value bitstream. In some cases, the network node can construct a LUT at least partially based on the RSRP / SINR values ​​and differential RSRP / SINR values. In this case, the strongest RSRP / SINR value can be reported separately, and the network node can construct a LUT at least partially based on the quantized differential RSRP / SINR value of the separately reported strongest RSRP / SINR value. The network node can construct a LUT for beam indexing (e.g., a second LUT for beam indexing). For example, the network node can construct a LUT for the beam index bitstream. In some cases, the network node can construct a LUT at least partially based on the beam index and differential beam index. In this scenario, the strongest beam index can be reported separately, and the network node can construct the LUT at least in part based on the differential beam indices of the other reported beams (e.g., beam indices minus the strongest beam index).

[0094] In some respects, the LUT can be an ordered table. The order can be the natural order of the bit stream stored in the LUT. Therefore, it is easier to search the LUT to identify entries corresponding to a specific beam index and RSRP / SINR value. In some respects, the network node can build separate LUTs for the RSRP / SINR value and for the beam index. In other words, separate LUTs can be built for the RSRP / SINR value and the beam index. Alternatively, the network node can build a common LUT for the beam index and the RSRP / SINR value.

[0095] As a first example, with 256 antennas and 64 beams, the UE can report four optimal beams. Compared to using a conventional method to report four optimal beams, the UE can use fewer bits when using a LUT-based method to report these four optimal beams. The conventional method may include a first beam index, another beam index, a first RSRP / SINR value, and a differential value. The conventional method may require a total of 43 bits, but the LUT-based method may require fewer than 43 bits (e.g., 34 to 40 bits, depending on whether differential RSRP / SINR values ​​and / or differential beam index values ​​are used in the LUT).

[0096] As a second example, for 128 antennas and 64 beams, the UE can report four optimal beams. Compared to using a conventional method to report four optimal beams, the UE can use fewer bits when using a LUT-based method to report these four optimal beams. The conventional method may include a first beam index, another beam index, a first RSRP / SINR value, and a differential value. The conventional method may require a total of 43 bits, but the LUT-based method may require fewer than 43 bits (e.g., 35 to 38 bits, depending on whether differential RSRP / SINR values ​​and / or differential beam index values ​​are used in the LUT).

[0097] In some aspects, the L1 RSRP / SINR measurement may be a first L1 RSRP / SINR measurement, and the reference signal may be a first reference signal. The UE may perform a second L1 RSRP / SINR measurement, which may be based at least in part on a second reference signal associated with beam management. The UE may determine, at least in part, based on an additional search of the LUT, that no entry in the LUT corresponds to the second L1 RSRP / SINR measurement. The UE may send an indication of the second L1 RSRP / SINR measurement to the network node. In this case, since the UE does not find a corresponding entry in the LUT, the UE may send the second L1 RSRP / SINR measurement itself. The UE may send an indication to the network node of the beam index and / or RSRP / SINR value associated with the second L1 RSRP / SINR measurement that is not currently in the LUT.

[0098] In some respects, the UE may report missing entries in the LUT to the network node. When a UE measurement does not match the corresponding beam index and / or RSRP / SINR value in the LUT, the UE may send the UE measurement to the network node. The UE may send the UE measurement based at least in part on an L1 measurement report. Alternatively, the UE may send a Media Access Control (MAC-CE) element to the network node, which may transmit beam indexes and / or RSRP / SINR values ​​that are not currently in the LUT.

[0099] In some respects, the LUT can be an initial LUT. The UE can send UE feedback to the network node. The UE feedback can indicate L1 RSRP / SINR measurements not in the initial LUT. For example, the UE feedback can indicate beam index and / or RSRP / SINR values ​​not in the initial LUT. The network node can generate an updated LUT based at least in part on the UE feedback. The UE can receive the updated LUT from the network node. The updated LUT can include new entries for beam index and / or RSRP / SINR values. Entries in the initial LUT can be deleted in the updated LUT. For example, the updated LUT can include fewer entries and / or different entries compared to the initial LUT. The updated LUT can be associated with a version number. The UE can delete the initial LUT. The UE can begin using the updated LUT.

[0100] In some respects, the network node can maintain the LUT. The network node can update the LUT at least in part based on UE feedback. For example, the network node can update the LUT at least in part based on UE measurements and / or MAC-CE received from the UE. The network node can expand the LUT by incorporating new beam indices and / or RSRP / SINR values ​​that were not previously in the LUT. The network node can create new entries in the LUT for new beam indices and / or RSRP / SINR values. An expanded LUT may potentially result in more bits required for L1 RSRP / SINR reporting. The network node can delete the least frequent entries. The network node can delete entries that have not appeared for a relatively long period of time. For example, when a specific entry is not indicated for a period exceeding a time threshold, the network node can delete that entry from the LUT. The network node can maintain a database tracking the frequency and last indicated time of each entry in the LUT, which allows the network node to delete specific entries. The network node can send the updated LUT to the UE. The updated LUT can indicate the version number, which allows the UE to continuously track different LUTs and remove outdated LUTs from the UE's memory.

[0101] In some respects, the UE may send UE feedback to the network node. This UE feedback may indicate L1RSRP / SINR measurements not in the LUT. The UE may receive, from the network node and at least in part, instructions for one or more entries to be inserted into or removed from the LUT. The UE may update the LUT based at least in part on these instructions received from the network node. In this case, instead of receiving a completely new LUT, the UE receives instructions for certain entries, which the UE can then use to update the LUT already stored on the UE.

[0102] In some respects, the UE may receive a LUT (e.g., an initial LUT) from the network node. The LUT used for beam indexing may include 2... 16 The LUT used for RSRP / SINR values ​​can include 2 entries. 14 L1 measurement reporting using a LUT may involve searching within an ordered table. For example, the UE may search the LUT for an entry, which can then be reported to the network node. Updating a LUT may involve inserting or deleting entries in an ordered manner, which may occur on the LUT stored at the network node. The network node may send the entry to be inserted or deleted to the UE, allowing the UE to update the LUT already stored there. In other words, the UE may maintain the same LUT and may not need to receive the entire LUT from the network node again. In some cases, the LUT can be compressed to have fewer entries, which can further reduce the bits required for L1 measurement reporting.

[0103] In some respects, entries in a LUT may be associated with a counter indicating how many times the entry has been reported. Entries in a LUT may also be associated with a timestamp indicating when the entry was last reported. Entries can be retained in or deleted from a LUT based at least in part on the counter and the timestamp. Thus, only the most recent entries in the LUT and / or the most frequently used entries in the LUT can be retained.

[0104] In some aspects, to compress the LUT, each entry in the LUT can be associated with a counter and a timestamp. The counter indicates the total number of times the entry has been reported. The timestamp indicates the time the entry was last reported. Entries that have been reported more than k times and / or those used in the past t seconds can be retained in the LUT, and the remaining entries can be discarded. In this case, k and t can be adjusted based on the number of bits required to encode the entries in the LUT. In some aspects, to compress the LUT, entries that are relatively close neighbors in the LUT can be removed. When relatively close neighbors are used instead of the removed entries, the beam index and / or RSRP / SINR value error may be less than a threshold.

[0105] As an example, the number of bits required to report four beams after removing less frequent entries may be less than the number of bits required to report four beams without removing less frequent entries. The amount of less frequent entries removed can be related to the number of bits required to report four beams. For example, removing a larger number of less frequent entries from the LUT can reduce the required number of bits by 1 to 3 bits.

[0106] In some respects, the UE may receive an L1 RSRP / SINR configuration message from the network node. The UE may download the LUT from the network node based at least in part on the L1 RSRP / SINR configuration message. The UE may send an L1 RSRP / SINR measurement report indicating the entry in the LUT based at least in part on the L1 RSRP / SINR configuration message. In other words, the network node may send an L1 RSRP / SINR configuration message to the UE, configuring the UE to download the LUT and send the L1 RSRP / SINR measurement report.

[0107] In some respects, the LUT can be an initial LUT. The UE can receive a broadcast message from the network node indicating that a new LUT is available. The broadcast message can indicate a version number associated with the new LUT. The UE can determine that the initial LUT is associated with a previous version compared to the new LUT. The UE can send a request for the new LUT to the network node. The UE can receive the new LUT from the network node, at least in part, based on the request. The UE can replace the initial LUT with the new LUT.

[0108] As shown by reference numeral 508 in the attached figure, the UE may send an L1 RSRP / SINR measurement report to the network node indicating the entry in the LUT. This entry may correspond to an L1 RSRP / SINR measured by the UE. The L1 RSRP / SINR measurement report may include a bit indicating the L1 RSRP / SINR report format. This L1 RSRP / SINR report format may indicate that the L1 RSRP / SINR measurement report is at least partially based on the LUT. Alternatively, the L1 RSRP / SINR report format may indicate that the L1 RSRP / SINR measurement report is at least partially based on a non-LUT scheme.

[0109] In some aspects, the UE can perform L1 RSRP / SINR measurement reporting, and the network node can construct a LUT (Local Underlying Technology) based at least in part on the L1 RSRP / SINR measurement report. After the network node determines that the LUT has been constructed, the network node can configure the UE to download the LUT. The network node can determine that the LUT has been constructed based at least in part on the network node's specific implementation. The network node can determine that the LUT has been constructed based at least in part on the fact that the LUT has not been updated within a certain period of time or at least in part on the fact that the number of updates is less than a threshold. The network node can configure the UE via an L1 RSRP / SINR configuration message to use the LUT to report L1 RSRP / SINR measurements. For example, the network node can configure the UE to look up an entry in the LUT corresponding to an L1 RSRP / SINR measurement and then report that entry to the network node. The network node can configure the UE to use RRC signaling, MAC-CE, or DCI, and use the LUT to report L1 RSRP / SINR measurements. The network node can broadcast a message indicating that the LUT is ready, along with the current version number of the LUT. The network node can then send the LUT to the UE, at least in part, based on a UE request. When the UE does not have the latest LUT (which the UE can determine, at least in part, based on the current version number of the LUT indicated in the broadcast message), the UE can request the LUT from the network node.

[0110] In some aspects, the UE may send L1 RSRP / SINR measurement reports to the network node at least partially based on the L1 RSRP / SINR report format. In other aspects, the UE may add a bit to the L1 RSRP / SINR measurement report to indicate the L1 RSRP / SINR report format. For example, the bit may indicate that the L1 RSRP / SINR measurement report is a LUT-based L1 RSRP / SINR measurement report, or the bit may indicate that the L1 RSRP / SINR measurement report is a non-LUT-based L1 RSRP / SINR measurement report. Even when the network node configures the UE to perform LUT-based L1 RSRP / SINR measurement reports, the UE may still utilize non-LUT-based L1 RSRP / SINR measurement reports if the UE does not have an up-to-date LUT, or if the L1 RSRP / SINR measurement is not in the LUT.

[0111] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0112] Figure 6 This is a diagram illustrating an example procedure 600 performed by a UE according to this disclosure. Example procedure 600 is an example in which a UE (e.g., UE 120) performs operations associated with a measurement report using a LUT.

[0113] like Figure 6 As shown, in some aspects, process 600 may include: receiving a reference signal associated with beam management from a network node (block 610). For example, the UE (e.g., using...) Figure 8 The receiving component 802 and / or communication manager 806 depicted herein can receive reference signals associated with beam management from network nodes, as described above.

[0114] like Figure 6 As further shown, in some aspects, process 600 may include: performing an L1 RSRP / SINR measurement (block 620) at least in part based on the reference signal. For example, the UE (e.g., using...) Figure 8 The communication manager 806 depicted herein can perform L1 RSRP / SINR measurements, at least in part, based on the reference signal, as described above.

[0115] like Figure 6 Further shown, in some aspects, process 600 may include: determining, at least in part, an entry in the LUT corresponding to the L1 RSRP / SINR measurement based on a search of the LUT (box 630). For example, the UE (e.g., using...) Figure 8The communication manager 806 depicted above can determine the entry in the LUT corresponding to the L1 RSRP / SINR measurement based at least in part on a search of the LUT, as described above.

[0116] like Figure 6 Further shown, in some aspects, process 600 may include: sending an L1 RSRP / SINR measurement report (box 640) to the network node indicating the entry in the LUT. For example, the UE (e.g., using...) Figure 8 The transmitting component 804 and / or the communication manager 806 depicted herein may send an L1 RSRP / SINR measurement report to the network node indicating the entry in the LUT, as described above.

[0117] Process 600 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.

[0118] In the first aspect, the entry in the LUT corresponding to the L1 RSRP / SINR measurement is the closest entry in the LUT corresponding to the L1 RSRP / SINR measurement.

[0119] In the second aspect, either alone or in combination with the first aspect, the LUT is a UE-specific LUT, or the LUT is a common LUT shared by multiple UEs.

[0120] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 600 includes: receiving from the network node the LUT comprising a plurality of entries corresponding to possible L1 RSRP / SINR measurements; and storing the LUT in the memory of the UE.

[0121] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the entry in the LUT corresponds to one or more of the beam index associated with the L1 RSRP / SINR measurement or the RSRP / SINR value associated with the L1 RSRP / SINR measurement.

[0122] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the LUT includes a first LUT and a second LUT, the first LUT including a beam index associated with the L1 RSRP / SINR measurement, and the second LUT including an RSRP / SINR value associated with the L1 RSRP / SINR measurement.

[0123] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the LUT is a single LUT comprising the beam index and RSRP / SINR value associated with the L1 RSRP / SINR measurement.

[0124] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the L1 RSRP / SINR measurement is a first L1 RSRP / SINR measurement, and process 600 includes: performing a second L1 RSRP / SINR measurement; determining, at least in part, based on an additional search of the LUT, that no entry in the LUT corresponds to the second L1 RSRP / SINR measurement; and sending to the network node an indication of the second L1 RSRP / SINR measurement, or an indication of one or more of a beam index or RSRP / SINR value currently not in the LUT associated with the second L1 RSRP / SINR measurement.

[0125] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, the LUT is an initial LUT, and process 600 includes: sending UE feedback to the network node; receiving an updated LUT from the network node and at least in part based on the UE feedback, wherein the updated LUT includes new entries for one or more of the beam index or RSRP / SINR value, wherein entries in the initial LUT are deleted in the updated LUT, and the updated LUT is associated with a version number; and deleting the initial LUT.

[0126] In the ninth aspect, alone or in combination with one or more aspects from the first to the eighth aspects, process 600 includes: sending UE feedback to the network node; receiving from the network node and at least in part based on the UE feedback an indication for one or more entries to be inserted into or deleted from the LUT; and updating the LUT at least in part based on the indication received from the network node.

[0127] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the entry in the LUT is associated with a counter indicating the number of times the entry has been reported, wherein the entry in the LUT is associated with a timestamp indicating the time when the entry was last reported, and wherein the entry is kept in or deleted from the LUT based at least in part on the counter and the timestamp.

[0128] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 600 includes: receiving an L1 RSRP / SINR configuration message from the network node; and downloading the LUT from the network node based at least in part on the L1 RSRP / SINR configuration message, wherein the L1 RSRP / SINR measurement report indicating the entry in the LUT is sent based at least in part on the L1 RSRP / SINR configuration message.

[0129] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the LUT is an initial LUT, and process 600 includes: receiving from the network node a broadcast message indicating that a new LUT is available, wherein the broadcast message indicates a version number associated with the new LUT; determining that the initial LUT is associated with a previous version compared to the new LUT; sending a request for the new LUT to the network node; receiving from the network node the new LUT at least in part based on the request; and replacing the initial LUT with the new LUT.

[0130] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the L1 RSRP / SINR measurement report includes a bit for indicating the L1 RSRP / SINR report format, and the L1 RSRP / SINR report format indicates that the L1 RSRP / SINR measurement report is at least partially based on the LUT.

[0131] although Figure 6 An example box of process 600 is shown, but in some respects, process 600 may include... Figure 6 The boxes depicted in the diagram may be compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Alternatively, two or more boxes in the process 600 may be executed in parallel.

[0132] Figure 7 This is a diagram illustrating an example process 700 performed by a network node, for example, according to this disclosure. Example process 700 is an example in which a network node (e.g., network node 110) performs operations associated with measurement reporting using a LUT.

[0133] like Figure 7 As shown, in some aspects, process 700 may include: sending a reference signal associated with beam management to the UE (block 710). For example, a network node (e.g., using...) Figure 9 The transmitting component 904 and / or the communication manager 906 depicted herein may transmit reference signals associated with beam management to the UE, as described above.

[0134] like Figure 7Further shown, in some aspects, process 700 may include: receiving from the UE an L1 RSRP / SINR measurement report at least partially based on the reference signal, wherein the L1 RSRP / SINR measurement report indicates an entry in the LUT corresponding to the L1 RSRP / SINR measurement (box 720). For example, a network node (e.g., using...) Figure 9 The receiving component 902 and / or communication manager 906 depicted herein may receive from the UE an L1 RSRP / SINR measurement report based at least in part on the reference signal, wherein the L1 RSRP / SINR measurement report indicates an entry in the LUT corresponding to the L1 RSRP / SINR measurement, as described above.

[0135] 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.

[0136] In the first aspect, the entry in the LUT corresponding to the L1 RSRP / SINR measurement is the closest entry in the LUT corresponding to the L1 RSRP / SINR measurement.

[0137] In the second aspect, either alone or in combination with the first aspect, the LUT is a UE-specific LUT, or the LUT is a common LUT shared by multiple UEs.

[0138] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 700 includes sending the LUT to the UE, which includes a plurality of entries corresponding to possible L1 RSRP / SINR measurements, wherein the LUT is locally stored by both the network node and the UE.

[0139] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the entry in the LUT corresponds to one or more of the beam index associated with the L1 RSRP / SINR measurement or the RSRP / SINR value associated with the L1 RSRP / SINR measurement.

[0140] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the LUT includes a first LUT and a second LUT, the first LUT including a beam index associated with the L1 RSRP / SINR measurement, and the second LUT including an RSRP / SINR value associated with the L1 RSRP / SINR measurement.

[0141] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the LUT is a single LUT comprising the beam index and RSRP / SINR value associated with the L1 RSRP / SINR measurement.

[0142] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the L1 RSRP / SINR measurement is a first L1 RSRP / SINR measurement, and process 700 includes: receiving from the UE an indication of a second L1 RSRP / SINR measurement, or an indication of one or more of a beam index or RSRP / SINR value that is not currently in the LUT and is associated with the second L1 RSRP / SINR measurement.

[0143] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, the LUT is an initial LUT, and process 700 includes: receiving UE feedback from the UE; and sending an updated LUT to the UE and at least in part based on the UE feedback, wherein the updated LUT includes new entries for one or more of the beam index or RSRP / SINR values, wherein entries in the initial LUT are deleted in the updated LUT, and the updated LUT is associated with a version number.

[0144] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, process 700 includes: receiving UE feedback from the UE; and sending an instruction to the UE, and at least in part based on the UE feedback, for one or more entries to be inserted into or removed from the LUT.

[0145] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the entry in the LUT is associated with a counter indicating the number of times the entry has been reported, wherein the entry in the LUT is associated with a timestamp indicating the time when the entry was last reported, and the entry is kept in or deleted from the LUT based at least in part on the counter and the timestamp.

[0146] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 700 includes: sending an L1 RSRP / SINR configuration message to the UE, the L1 RSRP / SINR configuration message configuring the UE to download the LUT and send the L1 RSRP / SINR measurement report.

[0147] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the LUT is an initial LUT, and the process 700 includes: sending a broadcast message to the UE indicating that the new LUT is available, wherein the broadcast message indicates a version number associated with the new LUT; receiving a request for the new LUT from the UE and at least in part based on the broadcast message; and sending the new LUT to the UE at least in part based on the request.

[0148] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the L1 RSRP / SINR measurement report includes a bit for indicating the L1 RSRP / SINR report format, and the L1 RSRP / SINR report format indicates that the L1 RSRP / SINR measurement report is at least partially based on the LUT.

[0149] although Figure 7 An example box of process 700 is shown, but in some respects, process 700 may include... Figure 7 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Alternatively, two or more boxes in the process 700 may be executed in parallel.

[0150] Figure 8 This is a diagram illustrating an example device 800 for wireless communication according to the present disclosure. Device 800 may be a UE, or a UE may include device 800. In some aspects, device 800 includes a receiving component 802, a transmitting component 804, and / or a communication manager 806, which can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 806 is combined with... Figure 1 The described communication manager 140. As shown, device 800 can communicate with another device 808 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 802 and transmitting component 804.

[0151] In some respects, device 800 can be configured to perform the functions described herein. Figure 5 The described one or more operations. Additionally or alternatively, the device 800 may be configured to perform one or more processes described herein, such as Figure 6 The process is 600. In some respects, Figure 8 The illustrated device 800 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 8 One or more components shown can be combined Figure 2Implemented within one or more of the described components. Alternatively or additionally, one or more of the components in a set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0152] Receiver 802 may receive communications from device 808, such as reference signals, control information, data communications, or combinations thereof. Receiver 802 may provide the received communications to one or more other components of device 800. In some aspects, receiver 802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 800. In some aspects, receiver 802 may include combinations of... Figure 2 The described UE includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0153] Transmitting component 804 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 808. In some aspects, one or more other components of device 800 may generate communications and provide the generated communications to transmitting component 804 for transmission to device 808. In some aspects, transmitting component 804 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 device 808. In some aspects, transmitting component 804 may include combinations of... Figure 2 The described UE includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 804 may be co-located with the receive component 802 in a transceiver.

[0154] The communication manager 806 may support the operation of the receiving component 802 and / or the transmitting component 804. For example, the communication manager 806 may receive information associated with configuring the reception of communications by the receiving component 802 and / or the transmission of communications by the transmitting component 804. Additionally or alternatively, the communication manager 806 may generate control information and / or provide control information to the receiving component 802 and / or the transmitting component 804 to control the reception and / or transmission of communications.

[0155] The receiving component 802 can receive a reference signal associated with beam management from the network node. The communication manager 806 can perform an L1 RSRP / SINR measurement based at least in part on the reference signal. The communication manager 806 can determine the entry in the LUT corresponding to the L1 RSRP / SINR measurement based at least in part on a search of the LUT. The transmitting component 804 can send an L1 RSRP / SINR measurement report indicating the entry in the LUT to the network node.

[0156] The receiving component 802 can receive the LUT, which includes multiple entries corresponding to possible L1 RSRP / SINR measurements, from the network node. The communication manager 806 can store the LUT in the memory of the UE.

[0157] The communication manager 806 can perform a second L1 RSRP / SINR measurement. The communication manager 806 can determine, at least in part, based on an additional search of the LUT, that no entry in the LUT corresponds to the second L1 RSRP / SINR measurement. The transmitting component 804 can send to the network node an indication of the second L1 RSRP / SINR measurement, or an indication of one or more of the beam index or RSRP / SINR value associated with the second L1 RSRP / SINR measurement that is not currently in the LUT.

[0158] The transmitting component 804 can send UE feedback to the network node. The receiving component 802 can receive an updated LUT from the network node and at least in part based on the UE feedback, wherein the updated LUT includes new entries for one or more of the beam index or RSRP / SINR values, wherein entries in the initial LUT are deleted in the updated LUT, and wherein the updated LUT is associated with a version number. The communication manager 806 can delete the initial LUT.

[0159] The transmitting component 804 can send UE feedback to the network node. The receiving component 802 can receive, from the network node and at least in part, an instruction for inserting or deleting one or more entries from the LUT. The communication manager 806 can update the LUT based at least in part on the instruction received from the network node.

[0160] The receiving component 802 can receive L1 RSRP / SINR configuration messages from the network node. The communication manager 806 can download the LUT from the network node based at least in part on the L1 RSRP / SINR configuration messages.

[0161] The receiving component 802 may receive from the network node a broadcast message indicating that a new LUT is available, wherein the broadcast message indicates a version number associated with the new LUT. The communication manager 806 may determine that the initial LUT is associated with a previous version compared to the new LUT. The sending component 804 may send a request for the new LUT to the network node. The receiving component 802 may receive the new LUT from the network node, at least in part, based on the request. The communication manager 806 may replace the initial LUT with the new LUT.

[0162] Figure 8 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 8 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 8 The two or more components shown can be implemented within a single component, or Figure 8 The single component shown can be implemented as multiple distributed components. Alternatively, Figure 8 The set (one or more) components shown are executable and described as being composed of Figure 8 The other set of components shown performs one or more functions.

[0163] Figure 9 This is a diagram illustrating an example device 900 for wireless communication according to the present disclosure. Device 900 may be a network node, or a network node may include device 900. In some aspects, device 900 includes a receiving component 902, a transmitting component 904, and / or a communication manager 906, which can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 906 is combined with... Figure 1 The described communication manager 150. As shown, device 900 can communicate with another device 908 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 902 and transmitting component 904.

[0164] In some respects, device 900 can be configured to perform the functions described herein. Figure 5 The described one or more operations. Additionally or alternatively, the device 900 may be configured to perform one or more processes described herein, such as Figure 7 The process is 700. In some respects, Figure 9 The illustrated device 900 and / or one or more components may include a combination Figure 2 One or more components of the described network node. Alternatively or concurrently, Figure 9 One or more components shown can be combined Figure 2Implemented within one or more of the described components. Alternatively or additionally, one or more of the components in a set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0165] Receiver 902 may receive communications from device 908, such as reference signals, control information, data communications, or combinations thereof. Receiver 902 may provide the received communications to one or more other components of device 900. In some aspects, receiver 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 900. In some aspects, receiver 902 may include combinations of... Figure 2 The described network node includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof. In some aspects, receiver component 902 and / or transmitter component 904 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals for device 900 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0166] Transmitting component 904 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 908. In some aspects, one or more other components of device 900 can generate communications and provide the generated communications to transmitting component 904 for transmission to device 908. In some aspects, transmitting component 904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 908. In some aspects, transmitting component 904 may include combinations of... Figure 2 The described network node includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 904 may be co-located with the receive component 902 in a transceiver.

[0167] The communication manager 906 may support the operation of the receiving component 902 and / or the transmitting component 904. For example, the communication manager 906 may receive information associated with configuring the reception of communication by the receiving component 902 and / or the transmission of communication by the transmitting component 904. Additionally or alternatively, the communication manager 906 may generate control information and / or provide control information to the receiving component 902 and / or the transmitting component 904 to control the reception and / or transmission of communication.

[0168] The transmitting component 904 can transmit a reference signal associated with beam management to the UE. The receiving component 902 can receive from the UE an L1 RSRP / SINR measurement report based at least in part on the reference signal, wherein the L1 RSRP / SINR measurement report indicates an entry in the LUT corresponding to the L1 RSRP / SINR measurement.

[0169] The transmitting component 904 may transmit to the UE the LUT comprising multiple entries corresponding to possible L1 RSRP / SINR measurements, wherein the LUT is locally stored by both the network node and the UE. The receiving component 902 may receive from the UE an indication of a second L1 RSRP / SINR measurement, or an indication of one or more of a beam index or RSRP / SINR value associated with the second L1 RSRP / SINR measurement that is not currently in the LUT.

[0170] The receiving component 902 can receive UE feedback from the UE. The transmitting component 904 can transmit an updated LUT to the UE and at least in part based on the UE feedback, wherein the updated LUT includes new entries for one or more of the beam index or RSRP / SINR values, wherein entries in the initial LUT are deleted in the updated LUT, and wherein the updated LUT is associated with a version number.

[0171] The receiving component 902 can receive UE feedback from the UE. The transmitting component 904 can send an instruction to the UE, and at least in part based on the UE feedback, for one or more entries to be inserted into or removed from the LUT. The transmitting component 904 can send an L1 RSRP / SINR configuration message to the UE, which configures the UE to download the LUT and send the L1 RSRP / SINR measurement report.

[0172] Transmitting component 904 may send a broadcast message to the UE indicating that a new LUT is available, wherein the broadcast message indicates a version number associated with the new LUT. Receiving component 902 may receive a request for the new LUT from the UE, and at least in part based on the broadcast message. Transmitting component 904 may send the new LUT to the UE, at least in part based on the request.

[0173] Figure 9 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 9 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 9 The two or more components shown can be implemented within a single component, or Figure 9 The single component shown can be implemented as multiple distributed components. Alternatively, Figure 9 The set (one or more) components shown are executable and described as being composed of Figure 9 The other set of components shown performs one or more functions.

[0174] The following provides an overview of some aspects of this disclosure:

[0175] Aspect 1: A method for wireless communication performed by a user equipment (UE), the method comprising: receiving a reference signal associated with beam management from a network node; performing a Layer 1 (L1) reference signal received power (RSRP) or an L1 signal-to-interference-plus-noise ratio (SINR) (RSRP / SINR) measurement based at least in part on the reference signal; determining, at least in part on a search of a lookup table (LUT), an entry in the LUT corresponding to the L1 RSRP / SINR measurement; and sending an L1 RSRP / SINR measurement report to the network node indicating the entry in the LUT.

[0176] Aspect 2: According to the method of aspect 1, wherein the entry in the LUT corresponding to the L1 RSRP / SINR measurement is the closest entry in the LUT corresponding to the L1 RSRP / SINR measurement.

[0177] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the LUT is a UE-specific LUT, or the LUT is a common LUT shared by multiple UEs.

[0178] Aspect 4: The method according to any one of aspects 1 to 3, the method further comprising: receiving from the network node the LUT including a plurality of entries corresponding to possible L1 RSRP / SINR measurements; and storing the LUT in the memory of the UE.

[0179] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the entry in the LUT corresponds to one or more of a beam index associated with the L1 RSRP / SINR measurement or an RSRP / SINR value associated with the L1 RSRP / SINR measurement.

[0180] Aspect 6: The method according to any one of aspects 1 to 5, wherein the LUT includes a first LUT and a second LUT, wherein the first LUT includes a beam index associated with an L1 RSRP / SINR measurement, and wherein the second LUT includes an RSRP / SINR value associated with an L1 RSRP / SINR measurement.

[0181] Aspect 7: The method according to any one of aspects 1 to 6, wherein the LUT is a single LUT comprising a beam index and an RSRP / SINR value associated with the L1 RSRP / SINR measurement.

[0182] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the L1 RSRP / SINR measurement is a first L1 RSRP / SINR measurement, and the method further includes: performing a second L1 RSRP / SINR measurement; determining, at least in part, based on an additional search of the LUT, that no entry in the LUT corresponds to the second L1 RSRP / SINR measurement; and sending to the network node an indication of the second L1 RSRP / SINR measurement, or an indication of one or more of a beam index or RSRP / SINR value currently not in the LUT associated with the second L1 RSRP / SINR measurement.

[0183] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the LUT is an initial LUT, and the method further comprises: sending UE feedback to the network node; receiving an updated LUT from the network node and at least in part based on the UE feedback, wherein the updated LUT includes new entries for one or more of a beam index or an RSRP / SINR value, wherein entries in the initial LUT are deleted in the updated LUT, and wherein the updated LUT is associated with a version number; and deleting the initial LUT.

[0184] Aspect 10: The method according to any one of aspects 1 to 9, the method further comprising: sending UE feedback to the network node; receiving from the network node and at least in part based on the UE feedback an indication for one or more entries to be inserted into or deleted from the LUT; and updating the LUT at least in part based on the indication received from the network node.

[0185] Aspect 11: The method according to any one of aspects 1 to 10, wherein the entry in the LUT is associated with a counter indicating the number of times the entry has been reported, wherein the entry in the LUT is associated with a timestamp indicating the time when the entry was last reported, and wherein the entry is kept in or deleted from the LUT based at least in part on the counter and the timestamp.

[0186] Aspect 12: The method according to any one of aspects 1 to 11, the method further comprising: receiving an L1 RSRP / SINR configuration message from the network node; and downloading the LUT from the network node based at least in part on the L1 RSRP / SINR configuration message, wherein the L1 RSRP / SINR measurement report indicating the entry in the LUT is sent based at least in part on the L1 RSRP / SINR configuration message.

[0187] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the LUT is an initial LUT, and the method further includes: receiving from the network node a broadcast message indicating that a new LUT is available, wherein the broadcast message indicates a version number associated with the new LUT; determining that the initial LUT is associated with a previous version compared to the new LUT; sending a request for the new LUT to the network node; receiving from the network node the new LUT at least in part based on the request; and replacing the initial LUT with the new LUT.

[0188] Aspect 14: The method according to any one of aspects 1 to 13, wherein the L1 RSRP / SINR measurement report includes a bit for indicating the L1 RSRP / SINR report format, and wherein the L1 RSRP / SINR report format indicates that the L1 RSRP / SINR measurement report is at least partially based on the LUT.

[0189] Aspect 15: A method for wireless communication performed by a network node, the method comprising: transmitting a reference signal associated with beam management to a user equipment (UE); and receiving from the UE a Layer 1 (L1) reference signal received power (RSRP) or L1 signal-to-interference-plus-noise ratio (SINR) (RSRP / SINR) measurement report at least in part based on the reference signal, wherein the L1 RSRP / SINR measurement report indicates an entry in a lookup table (LUT) corresponding to an L1 RSRP / SINR measurement.

[0190] Aspect 16: According to the method of aspect 15, wherein the entry in the LUT corresponding to the L1 RSRP / SINR measurement is the closest entry in the LUT corresponding to the L1 RSRP / SINR measurement.

[0191] Aspect 17: The method according to any one of Aspects 15 to 16, wherein the LUT is a UE-specific LUT, or the LUT is a common LUT shared by multiple UEs.

[0192] Aspect 18: The method according to any one of aspects 15 to 17, the method further comprising: sending to the UE the LUT comprising a plurality of entries corresponding to possible L1 RSRP / SINR measurements, wherein the LUT is locally stored by both the network node and the UE.

[0193] Aspect 19: The method according to any one of aspects 15 to 18, wherein the entry in the LUT corresponds to one or more of a beam index associated with the L1 RSRP / SINR measurement or an RSRP / SINR value associated with the L1 RSRP / SINR measurement.

[0194] Aspect 20: The method according to any one of aspects 15 to 19, wherein the LUT comprises a first LUT and a second LUT, wherein the first LUT comprises a beam index associated with an L1 RSRP / SINR measurement, and wherein the second LUT comprises an RSRP / SINR value associated with an L1 RSRP / SINR measurement.

[0195] Aspect 21: The method according to any one of aspects 15 to 20, wherein the LUT is a single LUT comprising a beam index and an RSRP / SINR value associated with an L1 RSRP / SINR measurement.

[0196] Aspect 22: The method according to any one of aspects 15 to 21, wherein the L1 RSRP / SINR measurement is a first L1 RSRP / SINR measurement, and the method further includes: receiving from the UE an indication of a second L1 RSRP / SINR measurement, or an indication of one or more of a beam index or RSRP / SINR value currently not in the LUT that is associated with the second L1 RSRP / SINR measurement.

[0197] Aspect 23: The method according to any one of Aspects 15 to 22, wherein the LUT is an initial LUT, and the method further includes: receiving UE feedback from the UE; and sending an updated LUT to the UE and at least in part based on the UE feedback, wherein the updated LUT includes new entries for one or more of the beam index or RSRP / SINR value, wherein entries in the initial LUT are deleted in the updated LUT, and wherein the updated LUT is associated with a version number.

[0198] Aspect 24: The method according to any one of aspects 15 to 23, the method further comprising: receiving UE feedback from the UE; and sending an instruction to the UE and at least in part based on the UE feedback for one or more entries to be inserted into or deleted from the LUT.

[0199] Aspect 25: The method according to any one of aspects 15 to 24, wherein the entry in the LUT is associated with a counter indicating the number of times the entry has been reported, wherein the entry in the LUT is associated with a timestamp indicating the time when the entry was last reported, and wherein the entry is kept in or deleted from the LUT based at least in part on the counter and the timestamp.

[0200] Aspect 26: The method according to any one of aspects 15 to 25, the method further comprising: sending an L1 RSRP / SINR configuration message to the UE, the L1 RSRP / SINR configuration message configuring the UE to download the LUT and send the L1 RSRP / SINR measurement report.

[0201] Aspect 27: The method according to any one of aspects 15 to 26, wherein the LUT is an initial LUT, and the method further includes: sending a broadcast message to the UE indicating that a new LUT is available, wherein the broadcast message indicates a version number associated with the new LUT; receiving a request for the new LUT from the UE and at least in part based on the broadcast message; and sending the new LUT to the UE at least in part based on the request.

[0202] Aspect 28: The method according to any one of aspects 15 to 27, wherein the L1 RSRP / SINR measurement report includes a bit for indicating the L1 RSRP / SINR report format, and wherein the L1 RSRP / SINR report format indicates that the L1 RSRP / SINR measurement report is at least partially based on the LUT.

[0203] Aspect 29: An apparatus for wireless communication 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 the method according to one or more of aspects 1 to 14.

[0204] Aspect 30: A device for wireless communication, the device comprising: a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more of aspects 1 to 14.

[0205] Aspect 31: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 14.

[0206] Aspect 32: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to one or more of aspects 1 to 14.

[0207] Aspect 33: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more aspects of aspects 1 to 14.

[0208] Aspect 34: An apparatus for wireless communication 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 the method according to one or more of aspects 15 to 28.

[0209] Aspect 35: An apparatus for wireless communication, the apparatus comprising: a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more aspects of aspects 15 to 28.

[0210] Aspect 36: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 15 to 28.

[0211] Aspect 37: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the methods according to one or more of aspects 15 to 28.

[0212] Aspect 38: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more aspects of aspects 15 to 28.

[0213] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit aspects to the precise forms disclosed. Modifications and variations may be made based on the foregoing disclosure, or from practice of these aspects.

[0214] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, "software" should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent to those skilled in the art that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting in any way. Therefore, no specific software code is referenced herein to describe the operation and behavior of the systems and / or methods, as those skilled in the art will understand that the software and hardware can be designed, at least in part, based on the descriptions herein, to implement the systems and / or methods.

[0215] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0216] Although specific combinations of features are 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 may be combined in ways not specifically set forth in the claims and / or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other claim in the set of claims. As used herein, the phrase referring to “at least one of” the list of entries means any combination of these entries (including 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, as well as any combination with multiple of the same element (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).

[0217] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more.” Furthermore, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more items and are interchangeable with “one or more.” If only one item is desired, the phrase “only one” or similar terminology is used. Furthermore, as used herein, the terms “have,” “possess,” “have,” etc., are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be open-ended when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one”).

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and One or more processors, said one or more processors being coupled to the memory and configured to: Receive reference signals associated with beam management from network nodes; The Layer 1 (L1) reference signal received power (RSRP) or L1 signal to interference plus noise ratio (SINR) (RSRP / SINR) measurement is performed at least in part based on the reference signal. The entry in the LUT corresponding to the L1 RSRP / SINR measurement is determined at least in part based on a search of the lookup table (LUT); and Send an L1 RSRP / SINR measurement report indicating the entry in the LUT to the network node.

2. The apparatus of claim 1, wherein the entry in the LUT corresponding to the L1 RSRP / SINR measurement is the closest entry in the LUT corresponding to the L1 RSRP / SINR measurement.

3. The apparatus of claim 1, wherein the LUT is a UE-specific LUT, or the LUT is a public LUT shared by multiple UEs.

4. The apparatus of claim 1, wherein the one or more processors are further configured to: Receive the LUT from the network node, comprising multiple entries corresponding to possible L1 RSRP / SINR measurements; and The LUT is stored in the memory of the UE, wherein the LUT is an ordered LUT based at least in part on the natural order of the bit stream stored in the LUT.

5. The apparatus of claim 1, wherein the entry in the LUT corresponds to one or more of a beam index associated with the L1 RSRP / SINR measurement or an RSRP / SINR value associated with the L1 RSRP / SINR measurement.

6. The apparatus of claim 1, wherein the LUT comprises a first LUT and a second LUT, wherein the first LUT comprises a beam index associated with an L1 RSRP / SINR measurement, and wherein the second LUT comprises an RSRP / SINR value associated with an L1 RSRP / SINR measurement.

7. The apparatus of claim 1, wherein the LUT is a single LUT comprising a beam index and an RSRP / SINR value associated with an L1 RSRP / SINR measurement.

8. The apparatus of claim 1, wherein the L1 RSRP / SINR measurement is a first L1 RSRP / SINR measurement, and wherein the one or more processors are further configured to: Perform the second L1 RSRP / SINR measurement; The determination is based at least in part on an additional search of the LUT to determine that no entry in the LUT corresponds to the second L1RSRP / SINR measurement; and Send to the network node an indication of the second L1 RSRP / SINR measurement, or an indication of one or more of the beam index or RSRP / SINR value that is not currently associated with the second L1 RSRP / SINR measurement in the LUT.

9. The apparatus of claim 1, wherein the LUT is an initial LUT, and wherein the one or more processors are further configured to: Send UE feedback to the network node; An updated LUT is received from the network node and at least in part based on the UE feedback, wherein the updated LUT includes new entries for one or more of the beam index or RSRP / SINR values, wherein entries in the initial LUT are deleted in the updated LUT, and wherein the updated LUT is associated with a version number; and Delete the initial LUT.

10. The apparatus of claim 1, wherein the one or more processors are further configured to: Send UE feedback to the network node; Receive, from the network node and at least in part based on the UE feedback, an instruction to insert or delete one or more entries into or from the LUT; and The LUT is updated at least in part based on the instruction received from the network node.

11. The apparatus of claim 1, wherein the entry in the LUT is associated with a counter indicating the number of times the entry has been reported, wherein the entry in the LUT is associated with a timestamp indicating the time when the entry was last reported, and wherein the entry is kept in or deleted from the LUT based at least in part on the counter and the timestamp.

12. The apparatus of claim 1, wherein the one or more processors are further configured to: Receive L1 RSRP / SINR configuration messages from the network node; and The LUT is downloaded from the network node based at least in part on the L1 RSRP / SINR configuration message. The L1 RSRP / SINR measurement report indicating the entry in the LUT is sent at least in part based on the L1 RSRP / SINR configuration message.

13. The apparatus of claim 1, wherein the LUT is an initial LUT, and wherein the one or more processors are further configured to: Receive a broadcast message from the network node indicating that a new LUT is available, wherein the broadcast message indicates a version number associated with the new LUT; It is determined that the initial LUT is associated with a previous version compared to the new LUT; Send a request for the new LUT to the network node; Receive the new LUT from the network node, at least in part, based on the request; as well as Replace the initial LUT with the new LUT.

14. The apparatus of claim 1, wherein the L1 RSRP / SINR measurement report includes a bit for indicating the L1 RSRP / SINR report format, and wherein the L1 RSRP / SINR report format indicates that the L1 RSRP / SINR measurement report is at least partially based on the LUT.

15. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; and One or more processors, said one or more processors being coupled to the memory and configured to: Send reference signals associated with beam management to user equipment (UE); as well as The UE receives a Layer 1 (L1) reference signal received power (RSRP) or L1 signal-to-interference-plus-noise ratio (SINR) (RSRP / SINR) measurement report based at least in part on the reference signal, wherein the L1 RSRP / SINR measurement report indicates an entry in a lookup table (LUT) corresponding to the L1 RSRP / SINR measurement.

16. The apparatus of claim 15, wherein the entry in the LUT corresponding to the L1 RSRP / SINR measurement is the closest entry in the LUT corresponding to the L1 RSRP / SINR measurement.

17. The apparatus of claim 15, wherein the LUT is a UE-specific LUT, or the LUT is a public LUT shared by multiple UEs.

18. The apparatus of claim 15, wherein the one or more processors are further configured to: The LUT, which includes multiple entries corresponding to possible L1 RSRP / SINR measurements, is sent to the UE, wherein the LUT is stored locally by both the network node and the UE.

19. The apparatus of claim 15, wherein the entry in the LUT corresponds to one or more of a beam index associated with the L1 RSRP / SINR measurement or an RSRP / SINR value associated with the L1 RSRP / SINR measurement.

20. The apparatus of claim 15, wherein the LUT comprises a first LUT and a second LUT, wherein the first LUT comprises a beam index associated with an L1 RSRP / SINR measurement, and wherein the second LUT comprises an RSRP / SINR value associated with an L1 RSRP / SINR measurement.

21. The apparatus of claim 15, wherein the LUT is a single LUT comprising a beam index and an RSRP / SINR value associated with an L1 RSRP / SINR measurement.

22. The apparatus of claim 15, wherein the L1 RSRP / SINR measurement is a first L1 RSRP / SINR measurement, and wherein the one or more processors are further configured to: The UE receives an indication of a second L1 RSRP / SINR measurement, or an indication of one or more of a beam index or RSRP / SINR value that is not currently associated with the second L1 RSRP / SINR measurement in the LUT.

23. The apparatus of claim 15, wherein the LUT is an initial LUT, and wherein the one or more processors are further configured to: Receive UE feedback from the UE; and An updated LUT is sent to the UE and at least in part based on feedback from the UE, wherein the updated LUT includes new entries for one or more of the beam index or RSRP / SINR values, wherein entries in the initial LUT are deleted in the updated LUT, and wherein the updated LUT is associated with a version number.

24. The apparatus of claim 15, wherein the one or more processors are further configured to: Receive UE feedback from the UE; and Instructions are sent to the UE, and at least in part based on feedback from the UE, to indicate one or more entries to be inserted into or removed from the LUT.

25. The apparatus of claim 15, wherein the entry in the LUT is associated with a counter indicating the number of times the entry has been reported, wherein the entry in the LUT is associated with a timestamp indicating the time when the entry was last reported, and wherein the entry is kept in or deleted from the LUT based at least in part on the counter and the timestamp.

26. The apparatus of claim 15, wherein the one or more processors are further configured to: The L1 RSRP / SINR configuration message is sent to the UE, which configures the UE to download the LUT and send the L1 RSRP / SINR measurement report.

27. The apparatus of claim 15, wherein the LUT is an initial LUT, and wherein the one or more processors are further configured to: Send a broadcast message to the UE indicating that the new LUT is available, wherein the broadcast message indicates the version number associated with the new LUT; Receive a request for the new LUT from the UE and at least in part based on the broadcast message; and The new LUT is sent to the UE at least in part based on the request.

28. The apparatus of claim 15, wherein the L1 RSRP / SINR measurement report includes a bit for indicating the L1 RSRP / SINR report format, and wherein the L1 RSRP / SINR report format indicates that the L1 RSRP / SINR measurement report is at least partially based on the LUT.

29. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive reference signals associated with beam management from network nodes; The Layer 1 (L1) reference signal received power (RSRP) or L1 signal to interference plus noise ratio (SINR) (RSRP / SINR) measurement is performed at least in part based on the reference signal. The entry in the LUT corresponding to the L1 RSRP / SINR measurement is determined at least in part based on a search of the lookup table (LUT); and Send an L1 RSRP / SINR measurement report indicating the entry in the LUT to the network node.

30. A method for wireless communication performed by a network node, the method comprising: Send reference signals associated with beam management to user equipment (UE); as well as The UE receives a Layer 1 (L1) reference signal received power (RSRP) or L1 signal-to-interference-plus-noise ratio (SINR) (RSRP / SINR) measurement report based at least in part on the reference signal, wherein the L1 RSRP / SINR measurement report indicates an entry in a lookup table (LUT) corresponding to the L1 RSRP / SINR measurement.