Event-based layer 1 measurement reporting

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may measure a Layer 1 (L1) metric in a candidate cell associated with Layer 1 or Layer 2 triggered Mobility (LTM). The UE may determine that the L1 metric in the candidate cell satisfies a trigger event condition. The UE may send an L1 measurement report to the network node based at least in part on the L1 metric in the candidate cell satisfying a trigger event condition. Numerous other aspects are described.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 174,130, filed on February 24, 2023, entitled “EVENT-BASED LAYER 1 MEASUREMENT REPORTING,” which is assigned to the assignee of the present application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Technical Field

[0002] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for event-based Layer 1 (L1) measurement reporting. Background Art

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems employ multiple-access technologies capable of supporting 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), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), time division synchronous code division multiple access (TD-SCDMA), and long-term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0004] 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 a network node via downlink and uplink communications. A "downlink" (or "DL") refers to the communication link from a network node to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at a city, national, regional, and / or global level. New Radio (NR), also known as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, reducing costs, improving services, leveraging new spectrum, and integrating better with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink and CP-OFDM and / or single-carrier frequency division multiplexing (SC-FDM), also known as discrete Fourier transform-spread OFDM (DFT-s-OFDM), on the uplink. Furthermore, it supports beamforming, multiple-input, multiple-output (MIMO) antenna technology, and carrier aggregation. As demand for mobile broadband access continues to increase, further improvements to LTE, NR, and other radio access technologies remain essential. Summary of the Invention

[0006] Some aspects described herein relate to an apparatus for wireless communication at a user equipment (UE). The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to measure a Layer 1 (L1) metric in a candidate cell associated with Layer 1 or Layer 2 triggered mobility (LTM). The one or more processors may be configured to determine that the L1 metric in the candidate cell satisfies a triggering event condition. The one or more processors may be configured to send an L1 measurement report to a network node based at least in part on the L1 metric in the candidate cell satisfying the triggering event condition.

[0007] Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send an L1 measurement report configuration to a UE. The one or more processors may be configured to receive an L1 measurement report from the UE based at least in part on an L1 metric in a candidate cell satisfying a triggering event condition and based at least in part on the L1 measurement report configuration, the L1 metric in the candidate cell being associated with an LTM.

[0008] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include measuring an L1 metric in a candidate cell associated with an LTM. The method may include determining that the L1 metric in the candidate cell satisfies a triggering event condition. The method may include sending an L1 measurement report to a network node based at least in part on the L1 metric in the candidate cell satisfying the triggering event condition.

[0009] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include sending an L1 measurement report configuration to a UE. The method may include receiving an L1 measurement report from the UE based at least in part on an L1 metric in a candidate cell satisfying a triggering event condition and based at least in part on the L1 measurement report configuration, the L1 metric in the candidate cell being associated with an LTM.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to measure an L1 metric in a candidate cell associated with an LTM. The instruction set, when executed by one or more processors of the UE, may cause the UE to determine that the L1 metric in the candidate cell satisfies a triggering event condition. The instruction set, when executed by the one or more processors of the UE, may cause the UE to send an L1 measurement report to a network node based at least in part on the L1 metric in the candidate cell satisfying the triggering event condition.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to send an L1 measurement report configuration to a UE. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive an L1 measurement report from the UE based at least in part on an L1 metric in a candidate cell satisfying a triggering event condition and based at least in part on the L1 measurement report configuration, the L1 metric in the candidate cell being associated with an LTM.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for measuring an L1 metric in a candidate cell associated with an LTM. The apparatus may include means for determining that the L1 metric in the candidate cell satisfies a triggering event condition. The apparatus may include means for sending an L1 measurement report to a network node based at least in part on the L1 metric in the candidate cell satisfying the triggering event condition.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending an L1 measurement report configuration to a UE. The apparatus may include means for receiving an L1 measurement report from the UE based at least in part on an L1 metric in a candidate cell satisfying a triggering event condition and based at least in part on the L1 measurement report configuration, the L1 metric in the candidate cell being associated with an LTM.

[0014] The various aspects collectively include 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 as illustrated in the accompanying drawings and description.

[0015] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described below. The concepts and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for achieving the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, as well as the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0016] While various aspects are described in this disclosure through illustration of certain examples, those skilled in the art will appreciate 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 packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other non-module-based devices (e.g., end-user devices, vehicles, communications devices, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. 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 various aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order that the above-described features of the present disclosure may be fully understood, a more particular description of the invention briefly summarized above may be obtained by reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are not therefore to be considered limiting of its scope, as the description may admit to other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

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

[0019] Figure 2 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.

[0020] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0021] Figure 4 is a diagram illustrating an example of Layer 1 (L1) or Layer 2 (L2) (L1 / L2) triggered mobility (LTM) according to the present disclosure.

[0022] Figures 5 to 7 is a diagram illustrating an example of cell update in LTM according to the present disclosure.

[0023] Figure 8 is a diagram illustrating an example associated with event-based L1 measurement reporting according to the present disclosure.

[0024] Figures 9 and 10 is a diagram illustrating an example procedure associated with event-based L1 measurement reporting according to the present disclosure.

[0025] Figures 11 to 12 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0026] In Layer 1 (L1) or Layer 2 (L2) (L1 / L2) triggered mobility (LTM), a user equipment (UE) may perform L1 measurements on one or more candidate cells. One or more candidate cells may be configured as LTM candidate target cells. The UE may send an L1 measurement report to a network node indicating the L1 measurements on the one or more candidate cells. The UE may send the L1 measurement report periodically, but this approach may waste resources when the UE sends the L1 measurement report even when it is not needed.

[0027] The UE may send event-based L1 measurement reports instead of periodic L1 measurement reports to save resources. In this case, the UE may send the L1 measurement report when a specific event occurs and is detected by the UE. However, for LTM, the triggering events and start / stop conditions for sending event-based L1 measurement reports may not be defined. In other words, the UE may not be correctly configured to detect the triggering events associated with the L1 measurement reports. In addition, the UE may not be correctly configured to determine the start / stop conditions associated with the L1 measurement reports. Therefore, event-based L1 measurement reporting by the UE may be associated with inefficiency. The UE may not correctly detect the events and therefore may not send the L1 measurement reports to the network node even when the network node requires them, which may reduce the performance of the UE. In addition, the UE may send an excessive number of L1 measurement reports because the start / stop conditions may not be correctly defined, resulting in excessive signaling and power consumption at the UE.

[0028] In some aspects described herein, a UE may measure an L1 metric in a candidate cell associated with an LTM. The L1 metric may be an RSRP measurement of a beam associated with the candidate cell. The UE may measure multiple L1 metrics in multiple candidate cells. The UE may determine that the L1 metric in the candidate cell meets a trigger event condition. For example, the UE may determine that the L1 metric in the candidate cell meets the trigger event condition based at least in part on: a comparison of the L1 metric in the candidate cell with a serving cell metric, a comparison of the L1 metric in the candidate cell with a threshold, a change in the L1 metric compared to a previously measured L1 metric that meets the threshold, a change in a ranking associated with the L1 metric in the candidate cell, and / or a number of beams associated with the candidate cell that meet the condition. The UE may send an L1 measurement report to the network node based at least in part on the L1 metric in the candidate cell meeting the trigger event condition. The UE may send an L1 measurement report based at least in part on an L1 measurement report configuration received from a network node. The L1 measurement report configuration may indicate start and stop conditions for sending the L1 measurement report, as well as whether to send the L1 measurement report a single time or multiple times until the stop condition is met. Thus, the UE may be appropriately configured to send event-based L1 measurement reports, thereby improving UE performance. The UE may be able to send event-based L1 measurement reports without excessive signaling and power consumption, which may improve UE performance.

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

[0030] Several aspects of telecommunications systems will now be presented with reference to various devices and techniques. These devices and techniques are described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

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

[0032] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. Wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. Wireless network 100 may include one or more network nodes 110 (illustrated as network node 110a, network node 110b, network node 110c, and network node 110d), one or more UEs 120 (illustrated 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 in the figure, network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, meaning that the converged 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, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between 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)).

[0033] In some examples, network node 110 is or includes a network node (such as a RU) that communicates with UE 120 via a radio access link. In some examples, network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or with a core network via a backhaul link. In some examples, network node 110 (such as a converged network node 110 or a disaggregated 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, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

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

[0035] In some aspects, the term "base station" or "network node" may refer to a converged base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, DU, RU, a near real-time (near-RT) RAN intelligent controller (RIC), 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 or different geographic locations) may be configured to perform at least a portion of a function, or to perform at least a portion of the function repeatedly, 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 may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

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

[0037] The wireless network 100 may be a heterogeneous network that includes 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 impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

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

[0039] UEs 120 may be dispersed throughout wireless network 100, and each UE 120 may be stationary or mobile. UEs 120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UEs 120 may be cellular phones (e.g., smartphones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablet computers, cameras, gaming devices, netbooks, smartbooks, ultrabooks, medical devices, biometric devices, wearable devices (e.g., smart watches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings or smart bracelets)), entertainment devices (e.g., music devices, video devices, and / or satellite radios), vehicle components or sensors, smart meters / sensors, industrial manufacturing equipment, global positioning system equipment, UE functionality of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0040] 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, which may communicate with a network node, 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. UE 120 may be included within a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0041] Generally speaking, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. 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 may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0042] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more sidelink channels. For example, UE 120 can 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 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0043] Devices of wireless network 100 can communicate using an electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices of wireless network 100 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz–300 GHz), which is identified as a "millimeter wave" band by the International Telecommunication Union (ITU).

[0044] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, 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 bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz–71 GHz), FR4 (52.6 GHz–114.25 GHz), and FR5 (114.25 GHz–300 GHz). Each of these higher frequency bands falls within the EHF band.

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

[0046] In some aspects, a UE (e.g., UE 120) may include a communications manager 140. As described in greater detail elsewhere herein, the communications manager 140 may measure an L1 metric in a candidate cell associated with an LTM; determine that the L1 metric in the candidate cell satisfies a triggering event condition; and send an L1 measurement report to a network node based at least in part on the L1 metric in the candidate cell satisfying the triggering event condition. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0047] In some aspects, a network node (e.g., network node 110) may include a communications manager 150. As described in greater detail elsewhere herein, the communications manager 150 may send an L1 measurement report configuration to a UE; and receive an L1 measurement report from the UE based at least in part on an L1 metric in a candidate cell satisfying a triggering event condition, the L1 metric in the candidate cell being associated with an LTM, and based at least in part on the L1 measurement report configuration. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0048] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0049] Figure 2 2 is a diagram illustrating example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components, such as one or more CUs or one or more DUs, that facilitate direct communication with the UE 120.

[0050] At network node 110, transmit processor 220 may receive data intended for UE 120 (or a group of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCSs) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may 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. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input, multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, as applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or frequency upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).

[0051] At UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use the demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, perform MIMO detection on the received symbols where applicable, and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine, among other things, a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter. In some examples, one or more components of the UE 120 may be included in a housing 284.

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

[0053] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more groups of antenna elements, and / or one or more antenna arrays, etc. An antenna panel, antenna group, group of antenna elements, and / or antenna array may include one or more antenna elements (within a single housing or multiple housings), a group of coplanar antenna elements, a group of non-coplanar antenna elements, and / or be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0054] On the uplink, at UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from a controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by a TX MIMO processor 266, as applicable, further processed by a modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 may include a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to execute the instructions herein (eg, reference Figures 8 to 12 ) any aspects of any of the methods described.

[0055] 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., a demodulator component (shown as DEMOD) of modem 232), detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide decoded data to a data sink 239 and decoded control information to controller / processor 240. Network node 110 may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, modem 232 of network node 110 may include a modulator and a demodulator. In some examples, network node 110 may include a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions herein (e.g., reference 242). Figures 8 to 12 ) any aspects of any of the methods described.

[0056] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or the like may perform one or more techniques associated with event-based L1 measurement reporting, as described in more detail elsewhere herein. Figure 2 Any other component of the may perform or direct e.g. Figure 9 The process of 900 Figure 10 1000 and / or other processes as described herein. Memory 242 and memory 282 may store data and program codes 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, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 9 The process of 900 Figure 10 The operations of process 1000 and / or other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, among others.

[0057] In some aspects, a UE (e.g., UE 120) includes means for measuring an L1 metric in a candidate cell associated with an LTM; means for determining that the L1 metric in the candidate cell satisfies a triggering event condition; and / or means for sending an L1 measurement report to a network node based at least in part on the L1 metric in the candidate cell satisfying the triggering event condition. Means for the UE to perform the operations described herein may include, for example, one or more of the following: the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0058] In some aspects, a network node (e.g., network node 110) includes means for sending an L1 measurement report configuration to a UE; and / or means for receiving an L1 measurement report from the UE based at least in part on an L1 metric in a candidate cell satisfying a triggering event condition and based at least in part on the L1 measurement report configuration, the L1 metric in the candidate cell being associated with an LTM. Means for the network node to perform the operations described herein may include, for example, one or more of the following: the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

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

[0060] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0061] The deployment of a communication system, such as a 5G NR system, can be arranged in a variety of ways using various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a RAN node, a core network node, a network element, a base station, or network equipment can be implemented in a converged architecture or a decomposed architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP, or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as a converged base station (also known as a standalone base station or a single-chip 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 a combination thereof).

[0062] A converged base station (e.g., a converged network node) 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 unit). A decomposed base station (e.g., a decomposed network node) can be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU can be implemented within a network node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually spread across one or more other network nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among others.

[0063] Base station type operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as the network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scalability of the communication system by separating base station functionality into one or more independently deployable units. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Various units of the disaggregated base station may be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0064] Figure 3 FIG2 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. Decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). CU 310 may communicate with one or more DUs 330 via corresponding midhaul links (such as via an F1 interface). Each of DUs 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Each of RUs 340 may communicate with one or more UEs 120 via corresponding radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

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

[0066] In some aspects, the CU 310 may host one or more higher-layer 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, among others. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface, such as the E1 interface. As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0067] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, a DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers, at least in part according to a functional split (such as that defined by 3GPP). In some aspects, the one or more higher PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, and the like. In some aspects, a DU 330 may also host one or more lower 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. 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.

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

[0069] 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 an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of the 4G RAN (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 the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0070] The non-RT RIC 315 can be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or in communication with the near-RT RIC 325 (e.g., via an A1 interface). The near-RT RIC 325 can be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions via an interface (e.g., via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0071] 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. Such information may be utilized by the near-RT RIC 325 and may be received from non-network data sources or from 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 execute corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or through the creation of RAN management policies (such as A1 interface policies).

[0072] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0073] Figure 4 is a diagram illustrating an example 400 of an LTM according to the present disclosure.

[0074] In LTM, the UE can be in RRC connected state. Figure 4 As shown by reference numeral 402, the UE may send a measurement report to the network node. The UE may send the measurement report via RRC signaling. The network node may determine to use LTM based at least in part on the measurement report and may initiate candidate LTM cell preparation. As shown by reference numeral 404, the network node may send an RRC reconfiguration message to the UE. The RRC reconfiguration message may indicate a candidate LTM cell configuration, which may indicate a configuration of one or more candidate LTM target cells. The UE may store the candidate LTM cell configuration. As shown by reference numeral 406, the UE may send an RRC reconfiguration complete message to the network node. The measurement report, the RRC reconfiguration message, and the RRC reconfiguration complete message may be part of the LTM preparation phase.

[0075] As indicated by reference numeral 408, the UE may perform downlink / uplink synchronization and timing advance (TA) acquisition with a candidate target cell. This may occur before receiving an LTM cell handover command. Downlink / uplink synchronization and TA acquisition may be associated with an early synchronization phase. The UE may perform L1 measurements on one or more configured candidate LTM target cells. As indicated by reference numeral 410, the UE may send an L1 measurement report to the network node, which may indicate the L1 measurements for the one or more configured candidate LTM target cells. The network node may determine to perform an LTM cell handover to the target cell, which may be based at least in part on the L1 measurement report. As indicated by reference numeral 412, the network node may send a MAC Control Element (MAC-CE) triggering an LTM cell handover to the UE, where the MAC-CE may indicate a candidate configuration index for the target cell. The UE may detach from the source cell. The UE may apply the candidate configuration index for the target cell. In other words, the UE may switch to the configuration of the candidate LTM target cell. As part of the LTM execution phase, the UE may detach from the source cell and attach to the target cell.

[0076] As shown at reference numeral 414, the UE may perform a random access channel (RACH) procedure with the target cell (e.g., when the TA is unavailable). As shown at reference numeral 416, the UE may send an indication to the target cell of the successful completion of the LTM cell handover to the target cell. The indication of the successful completion of the LTM cell handover may be part of the LTM completion phase.

[0077] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0078] L1 / L2-based inter-cell mobility can be defined to achieve reduced mobility latency. Multiple candidate cells can be configured and maintained to allow relatively quick application of candidate cell configurations. Dynamic switching between candidate serving cells can be based at least in part on L1 / L2 signaling. L1 / L2 signaling can be associated with serving cell changes for LTM. In other words, changing from one serving cell to another can be based at least in part on L1 / L2 signaling. Candidate serving cells can include special cells (SpCells) and / or secondary cells (SCells). In addition, L1 enhancements for inter-cell beam management can be defined, which can include L1 measurements and reporting and beam indications.

[0079] Cell updates in LTM may be based at least in part on individual cell selection. Individual cell selection may involve separate signaling for primary cell (PCell) changes and SCell changes in carrier aggregation scenarios, respectively. PCell selection may be based at least in part on beam indication. SCell selection may be based at least in part on L1 / L2 signaling, which may include downlink control information (DCI) or medium access control elements (MAC-CE). A single PCell without carrier aggregation or dual connectivity may be selected from a preconfigured set of candidate PCells. PCell changes may be based at least in part on swapping PCells and SCells from a preconfigured set of candidate PCells. Cell updates in LTM may be based at least in part on cell group-based selection. In carrier aggregation scenarios, SpCells and SCells may be switched together. Cell group switch signaling may be based at least in part on an extension of the signaling used for individual cell selection.

[0080] Figure 5 is a diagram illustrating an example 500 of cell updating in LTM according to the present disclosure.

[0081] like Figure 5 As shown, in a single PCell change without carrier aggregation, the UE may switch from the old PCell to the new PCell based at least in part on LTM. The new PCell may be selected from a preconfigured set of candidate PCells.

[0082] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0083] Figure 6 is a diagram illustrating an example 600 of cell updating in LTM according to the present disclosure.

[0084] like Figure 6 As shown, in a separate PCell / SCell change in carrier aggregation, the UE can switch between PCells based at least in part on LTM. The old PCell can become the new SCell, and vice versa. The new PCell can be selected from a preconfigured set of candidate PCells. The preconfigured set of candidate PCells can include multiple SCells (e.g., SCell 1, SCell 2, and the old SCell).

[0085] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0086] Figure 7is a diagram illustrating an example 700 of cell updating in LTM according to the present disclosure.

[0087] like Figure 7 As shown, in a cell group change in carrier aggregation, the UE may switch from the old cell group to the new cell group based at least in part on LTM. The new cell group may be selected from a preconfigured set of candidate cell groups.

[0088] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0089] UE event-triggered L1 measurement reporting for LTM may be supported. UE events may be defined (e.g., triggering event definitions). UE event-triggered L1 measurement reporting may be associated with a reporting container. UE event-triggered L1 measurement reporting may be associated with resource allocations or assignments. Conditions may be defined to start and stop UE event-triggered L1 measurement reporting. The network node may indicate the conditions to the UE. In other words, the network node may define when a UE event is met. UE event-triggered L1 measurement reporting may be associated with a reporting format. UE event-triggered L1 measurement reporting may include filtered L1 measurement results. UE event-triggered L1 measurement reporting may coexist with periodic, semi-persistent, or periodic L1 measurement reporting. UE event-triggered L1 measurement reporting may be sent to a serving cell and / or one or more candidate cells.

[0090] In LTM, the UE may perform L1 measurements on one or more candidate cells. The one or more candidate cells may be configured LTM candidate target cells. The UE may send an L1 measurement report to the network node indicating the L1 measurements on the one or more candidate cells. The UE may send the L1 measurement report periodically, but such an approach may waste resources when the L1 measurement report is not needed but the UE still sends the L1 measurement report. The UE may send event-based L1 measurement reports instead of periodic L1 measurement reports to save resources. In this case, the UE may send the L1 measurement report when a specific event occurs and is detected by the UE. However, for LTM, the triggering events and start / stop conditions for sending event-based L1 measurement reports may not be defined. In other words, the UE may not be correctly configured to detect the triggering events associated with the L1 measurement report. In addition, the UE may not be correctly configured to determine the start / stop conditions associated with the L1 measurement report. Therefore, event-based L1 measurement reporting by the UE may be associated with inefficiency. The UE may not detect the event correctly and therefore may not send the L1 measurement report to the network node even when the network node requires it, which may degrade the performance of the UE. In addition, the UE may send an excessive number of L1 measurement reports because the start / stop conditions may not be defined correctly, thereby resulting in excessive signaling and power consumption at the UE.

[0091] In various aspects of the techniques and apparatus described herein, a UE may measure an L1 metric in a candidate cell associated with an LTM. The L1 metric may be an RSRP measurement of a beam associated with the candidate cell. The UE may measure multiple L1 metrics in multiple candidate cells. The UE may determine that the L1 metric in the candidate cell meets a trigger event condition. For example, the UE may determine that the L1 metric in the candidate cell meets the trigger event condition based at least in part on: a comparison of the L1 metric in the candidate cell with a serving cell metric, a comparison of the L1 metric in the candidate cell with a threshold, a change in the L1 metric compared to a previously measured L1 metric that meets the threshold, a change in a ranking associated with the L1 metric in the candidate cell, and / or a number of beams associated with the candidate cell that meet the condition. The UE may send an L1 measurement report to the network node based at least in part on the L1 metric in the candidate cell meeting the trigger event condition. The UE may send an L1 measurement report based at least in part on an L1 measurement report configuration received from a network node. The L1 measurement report configuration may indicate start and stop conditions for sending the L1 measurement report, as well as whether to send the L1 measurement report a single time or multiple times until the stop condition is met. Thus, the UE may be appropriately configured to send event-based L1 measurement reports, thereby improving UE performance. The UE may be able to send event-based L1 measurement reports without excessive signaling and power consumption, which may improve UE performance.

[0092] Figure 8 is a diagram illustrating an example 800 associated with event-based L1 measurement reporting according to the present disclosure. Figure 8 As shown, example 800 includes communications between a UE (eg, UE 120) and a network node (eg, network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100).

[0093] As indicated by reference numeral 802, a UE may receive an L1 measurement report configuration from a network node. The L1 measurement report configuration may configure the UE to send an L1 measurement report. The L1 measurement report configuration may indicate whether the L1 measurement report is to be sent once or multiple times. The L1 measurement report configuration may indicate start conditions and / or stop conditions associated with the L1 measurement report.

[0094] As indicated by reference numeral 804, the UE may measure an L1 metric in a candidate cell associated with the LTM. The L1 metric may be an RSRP measurement of a beam associated with the candidate cell. The L1 metric may be a filtered L1 metric, where the L1 metric may be filtered based at least in part on a standard predefined or an indication from a network node. The L1 metric may be a spatially or temporally filtered L1 measurement. The candidate cell may be a candidate target cell.

[0095] As indicated by reference numeral 806, the UE may determine that an L1 metric in a candidate cell satisfies a trigger event condition. The UE may determine that the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on comparing the L1 metric in the candidate cell with a serving cell metric. The UE may determine that the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on comparing the L1 metric in the candidate cell with a threshold. The UE may determine that the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a change in the L1 metric compared to a previously measured L1 metric that satisfies the threshold. The UE may determine that the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a change in ranking associated with the L1 metric in the candidate cell. The UE may determine that the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a number of beams associated with the candidate cell that meet the condition. Furthermore, the trigger event condition may be defined at least in part based on: a time instant, an average value within a time period, a maximum value within the time period, a minimum value within the time period, and / or a number of occurrences within the time period. The start of the time period may be defined after the first occurrence of a predefined event.

[0096] In some aspects, trigger events may be associated with various trigger event types. A first trigger event type may be based at least in part on comparing beam metrics in a candidate cell with serving cell metrics. For example, the UE may determine whether the RSRP of the candidate cell beam is greater than or worse than the best or average RSRP measured for the serving cell beam, which may satisfy the trigger event condition. A second trigger event type may be based at least in part on comparing beam metrics in a candidate cell with an absolute threshold. For example, the UE may determine whether the RSRP of the candidate cell beam is greater than or worse than the absolute threshold (plus a defined offset), which may satisfy the trigger event condition. A third trigger event type may be based at least in part on a change in beam metrics in a candidate cell. For example, the UE may determine whether the RSRP of the candidate cell increases or decreases by X dB since the last measurement, which may satisfy the trigger event condition. A fourth trigger event type may be based at least in part on a change in the ranking of metrics in the candidate cells. For example, the UE may determine whether a change occurs in the top N good candidate beams or cell identifiers, which may satisfy the trigger event condition. A good beam may be one associated with an RSRP that meets a defined threshold. A fifth trigger event type may be based at least in part on the number of beams meeting a threshold. For example, the UE may determine whether the number of good beams in a candidate cell is greater than N (e.g., the RSRP of the good beams may be greater than a defined threshold), which may satisfy the trigger event condition. The trigger event condition may be satisfied based at least in part on the occurrence of any of the trigger event types.

[0097] In some aspects, the beam metric may be L1 or a spatially / temporally filtered L1 measurement, such as an L1-RSRP measurement or an L1 signal-to-interference-plus-noise ratio (SINR) measurement. In some aspects, a trigger event condition may be defined at least in part based on a moment in time. The trigger event condition may be defined at least in part based on an average, maximum, or minimum value over a time period. The trigger event condition may be defined at least in part based on a number of occurrences within a predefined time period. For example, the trigger event condition may be satisfied when a specific number of events are detected before a timer expires.

[0098] As an example, a trigger event condition may be satisfied (e.g., an event may be detected) when the best beam among multiple beams (e.g., all beams) or a subset of beams (e.g., the subset of beams may be indicated by a network node) of a measured candidate cell is greater than or less than an absolute threshold, or greater than or less than the best beam of a serving cell plus an offset. As another example, a trigger event condition may be satisfied when the best beam among multiple beams or a subset of beams of a measured candidate cell is greater than or less than an absolute threshold, or the best beam of a serving cell plus an offset, and when the best beam identifier in the candidate cell has changed since the last measurement. As yet another example, a trigger event condition may be satisfied when the order of candidate cell identifiers associated with good beams has changed since a previous time. Good beams may be defined as the top K beams with RSRP measurements that meet a threshold. For example, at a first time, the top K beams may correspond to cell identifiers 4, 5, 5, and 7, which may correspond to RSRP values ​​of -100 dB, -112 dB, -120 dB, and -140 dB, respectively, and at a second time, the top K beams may correspond to cell identifiers 4, 7, 5, and 7, which may correspond to RSRP values ​​of -102 dB, -114 dB, -120 dB, and -144 dB, respectively, which may satisfy the trigger event condition. In these examples, based at least in part on satisfying the trigger event condition, the UE may send an L1 measurement report.

[0099] As indicated by reference numeral 808, the UE may transmit an L1 measurement report to a network node based at least in part on an L1 metric in a candidate cell satisfying a triggering event condition and based at least in part on an L1 measurement report configuration. The UE may transmit the L1 measurement report based on a start condition and / or a stop condition. The UE may transmit one instance of the L1 measurement report, or alternatively, the UE may transmit the L1 measurement report multiple times (e.g., until a stop condition is satisfied). The stop condition may be based at least in part on a maximum number of L1 measurement reports to be transmitted. The presence or absence of a stop condition may be based at least in part on a triggering event condition. Additionally, the UE may transmit the L1 measurement report in uplink control information (UCI) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). Alternatively, the UE may transmit the L1 measurement report in a MAC-CE via the PUSCH.

[0100] In some aspects, a UE may send an event-triggered report of an L1 measurement of a candidate cell to a network node. The UE may measure an L1 measurement in the candidate cell. The L1 measurement may be an RSRP measurement of a beam associated with the candidate cell. The UE may send the L1 measurement report based at least in part on satisfying a triggering event condition. The L1 measurement report may be associated with a reporting container. The reporting container may be UCI in a PUCCH or PUSCH, or the reporting container may be a MAC-CE in a PUSCH. In other words, the UE may send the L1 measurement report in the UCI via the PUCCH or PUSCH, or the UE may send the L1 measurement report in a MAC-CE via the PUSCH. The UE may send a scheduling request (SR) to the network node to request resources for sending the MAC-CE via the PUSCH. Alternatively, the UE may use available uplink resources (e.g., any available uplink resources) to send the MAC-CE via the PUSCH. The SR may be associated with dedicated resources.

[0101] In some aspects, a UE may send an L1 measurement report based at least in part on a triggering event. The triggering event may be defined at least in part based on a Layer 3 (L3) event. The triggering event may be based at least in part on an L1 metric. The L1 metric may or may not be a filtered L1 metric. The filtered L1 metric may differ from a cell-level metric defined for legacy L3 events (e.g., filtering only in the time domain). The L1 metric may be filtered based at least in part on a standard pre-defined basis or based at least in part on an indication from a network node. Compared to L3 metrics, L1 metrics may involve less computational complexity and may better capture short-term channel variations.

[0102] In some aspects, an L1 measurement report may be associated with a start condition and a stop condition. A trigger event type (e.g., all types of events) may be associated with a start condition for triggering an L1 measurement report. Some trigger event types may not require a stop condition (e.g., not all types of events require a stop condition). For example, a one-time L1 measurement report may be sufficient for some types of trigger events (e.g., a change in the order of cells in the RSRP measurement ranking). Alternatively, multiple L1 measurement reports may be required for some types of trigger events.

[0103] In some aspects, the network node may configure the UE to report one instance of an L1 measurement report, or the network node may configure the UE to periodically send L1 measurement reports until a stopping condition is met. The stopping condition may depend on a maximum number of L1 measurement reports before stopping the L1 measurement report. For example, the UE may continue sending L1 measurement reports until the maximum number is met. When no stopping condition is configured, the UE may send one instance of the L1 measurement report. A flag in the RRC configuration associated with the triggering event type may indicate whether the L1 measurement report associated with the triggering event type is a single-instance L1 measurement report or a continuous L1 measurement report. For example, the network node may send an RRC configuration to the UE including a flag that may indicate whether the UE is to send a single instance of the L1 measurement report or whether the UE is to send multiple instances of the L1 measurement report. The multiple instances of the L1 measurement report may be the same L1 measurement report each time, or different L1 measurement reports each time. Furthermore, when a stopping condition is required for some triggering event types (e.g., a stopping condition is always required for a certain type of event), the network may configure a trivial stopping condition that is generally met so that the UE sends a single-instance L1 measurement report.

[0104] As an example, a trigger event condition may be met when the RSRP measurement of a candidate beam is greater than a predefined threshold. The UE may send an L1 measurement report based at least in part on meeting the trigger event. The start condition for the triggered L1 measurement report may define that the L1 measurement report is triggered when the beam in the candidate cell is greater than a first threshold by AdB. The stop condition for the triggered L1 measurement report may define that the L1 measurement report is deactivated when all candidate beams in the candidate cell drop below BdB from a second threshold and when the L1 measurement report does not exceed X times. The network node may configure a second threshold that is not practically feasible or X=1 so that the stop condition may always be met after sending one L1 measurement report.

[0105] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 The examples described are different.

[0106] Figure 9 is a diagram illustrating an example process 900, performed, for example, by a UE, in accordance with the present disclosure. Example process 900 is an example in which a UE (eg, UE 120) performs operations associated with event-based L1 measurement reporting.

[0107] like Figure 9 As shown, in some aspects, process 900 may include measuring L1 metrics in candidate cells associated with LTM (block 910). For example, a UE (e.g., using Figure 11The depicted communications manager 1106) may measure L1 metrics in candidate cells associated with the LTM, as described above.

[0108] like Figure 9 As further shown in FIG. 9 , in some aspects, process 900 may determine that an L1 metric in a candidate cell satisfies a triggering event condition (block 920). For example, a UE (e.g., using Figure 11 The communication manager 1106 depicted in FIG. 1104 may determine that the L1 metric in the candidate cell satisfies the trigger event condition, as described above.

[0109] like Figure 9 As further shown, in some aspects, process 900 may include sending an L1 measurement report to a network node based at least in part on an L1 metric in a candidate cell satisfying a triggering event condition (block 930). For example, a UE (e.g., using Figure 11 The sending component 1104 and / or the communication manager 1106 depicted in FIG may send an L1 measurement report to the network node based at least in part on the L1 metric in the candidate cell satisfying the triggering event condition, as described above.

[0110] Process 900 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.

[0111] In a first aspect, the L1 metric is an RSRP measurement or an SINR measurement of a beam associated with the candidate cell.

[0112] In a second aspect, alone or in combination with the first aspect, process 900 includes sending the L1 measurement report in UCI via PUCCH or PUSCH, or sending the L1 measurement report in MAC-CE via the PUSCH.

[0113] In a third aspect, alone or in combination with one or more of the first and second aspects, the L1 metric is a filtered L1 metric, and the L1 metric is filtered based at least in part on a standard predefinition or an indication from the network node.

[0114] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 900 includes determining that the L1 metric in the candidate cell meets the trigger event condition based at least in part on comparing the L1 metric in the candidate cell with a serving cell metric.

[0115] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 900 includes determining that the L1 metric in the candidate cell meets the trigger event condition based at least in part on comparing the L1 metric in the candidate cell to a threshold.

[0116] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 900 includes determining that the L1 metric in the candidate cell meets the trigger event condition based at least in part on a change in the L1 metric compared to a previously measured L1 metric that meets a threshold.

[0117] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 900 includes determining that the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a ranking change associated with the L1 metric in the candidate cell.

[0118] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 900 includes determining that the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a number of beams associated with the candidate cell that satisfy the condition.

[0119] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the L1 metric is a spatially or temporally filtered L1 measurement.

[0120] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the trigger event condition is defined at least in part based on one or more of the following: a moment, an average value over a certain time period, a maximum value over the time period, a minimum value over the time period, or a number of occurrences over the time period.

[0121] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 900 comprises sending the L1 measurement report based at least in part on one or more of a start condition or a stop condition.

[0122] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the presence of the stop condition is based at least in part on the trigger event condition.

[0123] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, process 900 includes receiving an L1 measurement report configuration from the network node, the L1 measurement report configuration indicating that the L1 measurement report is to be sent a single time or that the L1 measurement report is to be sent multiple times until the stopping condition is met, wherein the stopping condition is based at least in part on a maximum number of L1 measurement reports.

[0124] although Figure 9 Example blocks of process 900 are shown, but in some aspects, process 900 may include Figure 9900. In some embodiments, the process 900 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 900 may be executed in parallel.

[0125] Figure 10 is a diagram illustrating an example process 1000, performed, for example, by a network node, in accordance with the present disclosure. Example process 1000 is an example in which a network node (eg, network node 110) performs operations associated with event-based L1 measurement reporting.

[0126] like Figure 10 As shown, in some aspects, process 1000 may include sending an L1 measurement report configuration to a UE (block 1010). For example, a network node (e.g., using Figure 12 The transmitting component 1204 and / or the communication manager 1206 depicted in FIG. 12 may transmit the L1 measurement report configuration to the UE, as described above.

[0127] like Figure 10 As further shown in FIG. 1 , in some aspects, process 1000 may include receiving an L1 measurement report from a UE based at least in part on an L1 measurement in a candidate cell satisfying a triggering event condition and based at least in part on an L1 measurement report configuration, the L1 measurement in the candidate cell being associated with an LTM (block 1020). For example, a network node (e.g., using Figure 12 The receiving component 1202 and / or the communication manager 1206 depicted in can receive an L1 measurement report from the UE and based at least in part on the L1 measurement report configuration based at least in part on the L1 measurement in the candidate cell satisfying the trigger event condition, the L1 measurement in the candidate cell being associated with the LTM, as described above.

[0128] Process 1000 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.

[0129] In a first aspect, the L1 metric is an RSRP measurement or an SINR measurement of a beam associated with the candidate cell.

[0130] In a second aspect, alone or in combination with the first aspect, process 1000 includes receiving the L1 measurement report in UCI via PUCCH or PUSCH, or receiving the L1 measurement report in MAC-CE via the PUSCH.

[0131] In a third aspect, alone or in combination with one or more of the first and second aspects, the L1 metric is a filtered L1 metric, and the L1 metric is filtered based at least in part on a standard predefinition or an indication from the network node.

[0132] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a comparison of the L1 metric in the candidate cell with a serving cell metric.

[0133] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a comparison of the L1 metric in the candidate cell with a threshold.

[0134] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the L1 metric in the candidate cell satisfies the trigger event condition at least in part based on a change in the L1 metric compared to a previously measured L1 metric that satisfies a threshold.

[0135] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a ranking change associated with the L1 metric in the candidate cell.

[0136] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a conditionally satisfying number of beams associated with the candidate cell.

[0137] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the L1 metric is a spatially or temporally filtered L1 measurement.

[0138] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the trigger event condition is defined at least in part based on one or more of the following: a moment, an average value over a certain time period, a maximum value over the time period, a minimum value over the time period, or a number of occurrences over the time period.

[0139] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the L1 measurement report is based at least in part on one or more of a start condition or a stop condition.

[0140] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the presence of the stop condition is based at least in part on the trigger event condition.

[0141] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the L1 measurement report configuration indicates that the L1 measurement report is to be sent once or multiple times until the stopping condition is met, wherein the stopping condition is at least partially based on the maximum number of L1 measurement reports.

[0142] although Figure 10 Example blocks of process 1000 are shown, but in some aspects, process 1000 may include Figure 10 1000. In some embodiments, the process 1000 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1000 may be executed in parallel.

[0143] Figure 11 1 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 may be a UE, or a UE may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102, a sending component 1104, and / or a communication manager 1106, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1106 is a communication manager that is configured to communicate with one another. Figure 1 The depicted communication manager 140. As shown, the device 1100 can utilize a receiving component 1102 and a sending component 1104 to communicate with another device 1108, such as a UE or a network node such as a CU, DU, RU, or base station.

[0144] In some aspects, the apparatus 1100 may be configured to perform Figure 8 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more of the processes described herein, such as Figure 9 The process 900. In some aspects, Figure 11 The device 1100 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, one or more components of the UE described. Figure 11 One or more of the components shown may be combined Figure 2 In one or more components described herein, the present invention may be implemented in a manner that is at least partially implemented as software stored in a memory. Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and that can be executed by a controller or processor to perform the functions or operations of the component.

[0145] The receiving component 1102 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 1108. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include processing in conjunction with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0146] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 1108. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1108. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1108. In some aspects, the transmitting component 1104 may include a combination of Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmitting component 1104 can be co-located with the receiving component 1102 in a transceiver.

[0147] The communications manager 1106 can support the operation of the receiving component 1102 and / or the sending component 1104. For example, the communications manager 1106 can receive information associated with configuring the receipt of communications by the receiving component 1102 and / or the sending of communications by the sending component 1104. Additionally or alternatively, the communications manager 1106 can generate and / or provide control information to the receiving component 1102 and / or the sending component 1104 to control the receipt and / or sending of communications.

[0148] The communication manager 1106 can measure the L1 metric in the candidate cell associated with the LTM. The communication manager 1106 can determine that the L1 metric in the candidate cell meets the trigger event condition. The sending component 1104 can send an L1 measurement report to the network node based at least in part on the L1 metric in the candidate cell meeting the trigger event condition.

[0149] The communications manager 1106 may determine that the L1 metric in the candidate cell meets the trigger event condition based at least in part on comparing the L1 metric in the candidate cell with the serving cell metric. The communications manager 1106 may determine that the L1 metric in the candidate cell meets the trigger event condition based at least in part on comparing the L1 metric in the candidate cell with a threshold. The communications manager 1106 may determine that the L1 metric in the candidate cell meets the trigger event condition based at least in part on a change in the L1 metric compared to a previously measured L1 metric that meets the threshold. The communications manager 1106 may determine that the L1 metric in the candidate cell meets the trigger event condition based at least in part on a change in a ranking associated with the L1 metric in the candidate cell. The communications manager 1106 may determine that the L1 metric in the candidate cell meets the trigger event condition based at least in part on a number of beams associated with the candidate cell that meet the condition.

[0150] Transmitting component 1104 may transmit the L1 measurement report in the UCI via the PUCCH or the PUSCH. Transmitting component 1104 may transmit the L1 measurement report in the MAC-CE via the PUSCH. Transmitting component 1104 may transmit the L1 measurement report based at least in part on one or more of a start condition or a stop condition. Receiving component 1102 may receive an L1 measurement report configuration from a network node, the L1 measurement report configuration indicating that the L1 measurement report is to be transmitted a single time or multiple times until a stop condition is met, wherein the stop condition is based at least in part on a maximum number of L1 measurement reports.

[0151] Figure 11 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 11 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 11 Two or more components shown may be implemented in a single component, or Figure 11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 11 The illustrated set of component(s) executable is described as consisting of Figure 11 Another collection of components shown performs one or more functions.

[0152] Figure 121 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a network node, or a network node may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202, a sending component 1204, and / or a communication manager 1206, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1206 is a communication manager that is configured to communicate with one another. Figure 1 The described communication manager 150. As shown, the device 1200 can communicate with another device 1208, such as a UE or a network node (such as a CU, DU, RU, or base station), using a receiving component 1202 and a sending component 1204.

[0153] In some aspects, the apparatus 1200 may be configured to perform Figure 8 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more of the processes described herein, such as Figure 10 The process 1000. In some aspects, Figure 12 The device 1200 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, one or more components of the described network node. Figure 12 One or more of the components shown may be combined Figure 2 In one or more components described herein, the present invention may be implemented in a manner that is at least partially implemented as software stored in a memory. Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and that can be executed by a controller or processor to perform the functions or operations of the component.

[0154] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 1208. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include processing the received communications in conjunction with Figure 2One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes. In some aspects, the receiving component 1202 and / or the transmitting component 1204 may comprise or be included in a network interface. The network interface may be configured to obtain and / or output signals for the apparatus 1200 via one or more communication links (such as a backhaul link, a midhaul link, and / or a fronthaul link).

[0155] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1208. In some aspects, one or more other components of the apparatus 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the apparatus 1208. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the apparatus 1208. In some aspects, the transmitting component 1204 may include a combination of Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmitting component 1204 can be co-located with the receiving component 1202 in a transceiver.

[0156] The communications manager 1206 can support the operation of the receiving component 1202 and / or the sending component 1204. For example, the communications manager 1206 can receive information associated with configuring the receipt of communications by the receiving component 1202 and / or the sending of communications by the sending component 1204. Additionally or alternatively, the communications manager 1206 can generate and / or provide control information to the receiving component 1202 and / or the sending component 1204 to control the receipt and / or sending of communications.

[0157] The transmitting component 1204 can transmit the L1 measurement report configuration to the UE. The receiving component 1202 can receive the L1 measurement report from the UE based at least in part on the L1 measurement in the candidate cell satisfying the triggering event condition and based at least in part on the L1 measurement report configuration, the L1 measurement in the candidate cell being associated with the LTM.

[0158] Figure 12 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 12 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 12 Two or more components shown may be implemented in a single component, or Figure 12The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 12 The illustrated set of component(s) executable is described as consisting of Figure 12 Another collection of components shown performs one or more functions.

[0159] The following provides an overview of some aspects of the disclosure:

[0160] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: measuring a layer 1 (L1) metric in a candidate cell associated with layer 1 or layer 2 triggered mobility (LTM); determining that the L1 metric in the candidate cell satisfies a trigger event condition; and sending an L1 measurement report to a network node based at least in part on the L1 metric in the candidate cell satisfying the trigger event condition.

[0161] Aspect 2: The method according to aspect 1, wherein the L1 metric is one or more of a reference signal received power (RSRP) measurement or a signal to interference plus noise ratio (SINR) measurement of a beam associated with the candidate cell.

[0162] Aspect 3: The method according to any one of aspects 1 to 2, wherein sending the L1 measurement report includes: sending the L1 measurement report in uplink control information (UCI) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH); or sending the L1 measurement report in a medium access control element (MAC-CE) via the PUSCH.

[0163] Aspect 4: The method according to any one of aspects 1 to 3, wherein the L1 metric is a filtered L1 metric, and wherein the L1 metric is filtered based at least in part on a standard pre-definition or an indication from the network node.

[0164] Aspect 5: The method according to any one of aspects 1 to 4, wherein determining that the L1 metric in the candidate cell meets the trigger event condition is at least partially based on comparing the L1 metric in the candidate cell with a serving cell metric.

[0165] Aspect 6: The method according to any one of aspects 1 to 5, wherein determining that the L1 metric in the candidate cell meets the trigger event condition is at least partially based on comparing the L1 metric in the candidate cell with a threshold.

[0166] Aspect 7: A method according to any one of aspects 1 to 6, wherein determining that the L1 metric in the candidate cell meets the trigger event condition is at least partially based on a change in the L1 metric compared to a previously measured L1 metric that meets a threshold.

[0167] Aspect 8: The method according to any one of aspects 1 to 7, wherein determining that the L1 metric in the candidate cell satisfies the trigger event condition is based at least in part on a ranking change associated with the L1 metric in the candidate cell.

[0168] Aspect 9: The method according to any one of aspects 1 to 8, wherein determining that the L1 metric in the candidate cell satisfies the trigger event condition is at least partially based on the number of beams associated with the candidate cell that meet the condition.

[0169] Aspect 10: The method according to any one of aspects 1 to 9, wherein the L1 metric is a spatially or temporally filtered L1 measurement.

[0170] Aspect 11: A method according to any one of Aspects 1 to 10, wherein the trigger event condition is defined at least in part based on one or more of: a moment, an average value within a certain time period, a maximum value within the time period, a minimum value within the time period, or a number of occurrences within the time period.

[0171] Aspect 12: The method according to any one of aspects 1 to 11, wherein sending the L1 measurement report is based at least in part on one or more of a start condition or a stop condition.

[0172] Aspect 13: The method of aspect 12, wherein the presence of the stop condition is based at least in part on the trigger event condition.

[0173] Aspect 14: The method according to aspect 12 further includes: receiving an L1 measurement report configuration from the network node, the L1 measurement report configuration indicating that the L1 measurement report is to be sent once or multiple times until the stop condition is met, wherein the stop condition is at least partially based on the maximum number of L1 measurement reports.

[0174] Aspect 15: A method of wireless communication performed by a network node, the method comprising: sending a layer 1 (L1) measurement report configuration to a user equipment (UE); and receiving an L1 measurement report from the UE and based at least in part on the L1 measurement report configuration, based at least in part on an L1 metric in a candidate cell satisfying a triggering event condition, the L1 metric in the candidate cell being associated with layer 1 or layer 2 triggered mobility (LTM).

[0175] Aspect 16: The method of aspect 15, wherein the L1 metric is one or more of a reference signal received power (RSRP) measurement or a signal to interference plus noise ratio (SINR) measurement of a beam associated with the candidate cell.

[0176] Aspect 17: The method according to any one of aspects 15 to 16, wherein receiving the L1 measurement report includes: receiving the L1 measurement report in uplink control information (UCI) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH); or receiving the L1 measurement report in a medium access control element (MAC-CE) via the PUSCH.

[0177] Aspect 18: The method according to any one of aspects 15 to 17, wherein the L1 metric is a filtered L1 metric, and wherein the L1 metric is filtered based at least in part on a standard pre-definition or an indication from the network node.

[0178] Aspect 19: The method according to any one of aspects 15 to 18, wherein the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a comparison of the L1 metric in the candidate cell with a serving cell metric.

[0179] Aspect 20: The method according to any one of aspects 15 to 19, wherein the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a comparison of the L1 metric in the candidate cell with a threshold.

[0180] Aspect 21: The method according to any one of aspects 15 to 20, wherein the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a change in the L1 metric compared to a previously measured L1 metric that satisfies a threshold.

[0181] Aspect 22: The method according to any one of aspects 15 to 21, wherein the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a ranking change associated with the L1 metric in the candidate cell.

[0182] Aspect 23: The method according to any one of aspects 15 to 22, wherein the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on the number of beams associated with the candidate cell that satisfies the condition.

[0183] Aspect 24: The method according to any one of aspects 15 to 23, wherein the L1 metric is a spatially or temporally filtered L1 measurement.

[0184] Aspect 25: A method according to any one of Aspects 15 to 24, wherein the trigger event condition is defined at least in part based on one or more of: a moment, an average value within a certain time period, a maximum value within the time period, a minimum value within the time period, or a number of occurrences within the time period.

[0185] Aspect 26: The method according to any one of aspects 15 to 25, wherein the L1 measurement report is based at least in part on one or more of a start condition or a stop condition.

[0186] Aspect 27: The method according to aspect 26, wherein the existence of the stop condition is based at least in part on the trigger event condition.

[0187] Aspect 28: The method according to aspect 26, wherein the L1 measurement report configuration indicates that the L1 measurement report is to be sent once or multiple times until the stopping condition is met, wherein the stopping condition is based at least in part on a maximum number of L1 measurement reports.

[0188] 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 one or more of the methods described in aspects 1 to 14.

[0189] 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 configured to perform the method according to one or more of aspects 1 to 14.

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

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

[0192] Aspect 33: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 14.

[0193] 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 one or more of the methods described in aspects 15 to 28.

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

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

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

[0197] Aspect 38: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 15 to 28.

[0198] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

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

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

[0201] Although specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. The disclosure of the various aspects includes each dependent claim in conjunction with every other claim in the claim set. As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items (including single members). By way of example, “at least one of a, b, or c” is intended to encompass a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination of multiples 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).

[0202] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly described as such. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects connected with the article "said" and can be used interchangeably with "one or more". In addition, as used herein, the terms "group" and "cluster" are intended to include one or more projects and can be used interchangeably with "one or more". If only one project is intended to be referred to, the phrase "only one" or similar terms are used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms that do not limit the elements they modify (for example, an element "having" A can also have B). In addition, the phrase "based on" is intended to represent "at least partially based on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; as well as one or more processors coupled to the memory and configured to: Measuring Layer 1 (L1) metrics in candidate cells associated with Layer 1 or Layer 2 Triggered Mobility (LTM); Determining that the L1 metric in the candidate cell meets a trigger event condition; as well as An L1 measurement report is sent to a network node based at least in part on the L1 metric in the candidate cell satisfying the triggering event condition.

2. The apparatus of claim 1, wherein the L1 metric is one or more of a reference signal received power (RSRP) measurement or a signal to interference plus noise ratio (SINR) measurement of a beam associated with the candidate cell.

3. The apparatus of claim 1 , wherein to send the L1 measurement report, the one or more processors are configured to: sending the L1 measurement report in uplink control information (UCI) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH); or The L1 measurement report is sent in a Medium Access Control Element (MAC-CE) via the PUSCH. 4 . The apparatus of claim 1 , wherein the L1 metric is a filtered L1 metric, and wherein the L1 metric is filtered based at least in part on a standard pre-definition or an indication from the network node. 5 . The apparatus of claim 1 , wherein the one or more processors are configured to determine that the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on comparing the L1 metric in the candidate cell with a serving cell metric. 6 . The apparatus of claim 1 , wherein the one or more processors are configured to determine that the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on comparing the L1 metric in the candidate cell to a threshold.

7. The apparatus of claim 1 , wherein the one or more processors are configured to determine that the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a change in the L1 metric compared to a previously measured L1 metric that satisfies a threshold. 8 . The apparatus of claim 1 , wherein the one or more processors are configured to determine that the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a ranking change associated with the L1 metric in the candidate cell.

9. The apparatus of claim 1, wherein the one or more processors are configured to determine that the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a number of beams associated with the candidate cell that satisfies the condition.

10. The apparatus of claim 1, wherein the L1 metric is a spatially or temporally filtered L1 measurement.

11. An apparatus according to claim 1, wherein the trigger event condition is defined at least in part based on one or more of the following: a moment, an average value within a certain time period, a maximum value within the time period, a minimum value within the time period, or a number of occurrences within the time period.

12. The apparatus of claim 1, wherein the one or more processors are configured to send the L1 measurement report based at least in part on one or more of a start condition or a stop condition.

13. The apparatus of claim 12, wherein the presence of the stop condition is based at least in part on the trigger event condition.

14. The apparatus of claim 12, wherein the one or more processors are further configured to: An L1 measurement report configuration is received from the network node, the L1 measurement report configuration indicating that the L1 measurement report is to be sent once or multiple times until the stopping condition is met, wherein the stopping condition is based at least in part on a maximum number of L1 measurement reports.

15. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; as well as one or more processors coupled to the memory and configured to: Sending layer 1 (L1) measurement report configuration to user equipment (UE); as well as An L1 measurement report is received from the UE based at least in part on an L1 metric in a candidate cell satisfying a triggering event condition and based at least in part on the L1 measurement reporting configuration, the L1 metric in the candidate cell being associated with layer 1 or layer 2 triggered mobility (LTM).

16. The apparatus of claim 15, wherein the L1 metric is one or more of a reference signal received power (RSRP) measurement or a signal to interference plus noise ratio (SINR) measurement of a beam associated with the candidate cell.

17. The apparatus of claim 15, wherein to receive the L1 measurement report, the one or more processors are configured to: receiving the L1 measurement report in uplink control information (UCI) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH); or The L1 measurement report is received in a Medium Access Control Element (MAC-CE) via the PUSCH.

18. The apparatus of claim 15, wherein the L1 metric is a filtered L1 metric, and wherein the L1 metric is filtered based at least in part on a standard pre-definition or an indication from the network node.

19. The apparatus of claim 15, wherein the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a comparison of the L1 metric in the candidate cell with a serving cell metric.

20. The apparatus of claim 15, wherein the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a comparison of the L1 metric in the candidate cell with a threshold.

21. The apparatus of claim 15, wherein the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a change in the L1 metric compared to a previously measured L1 metric that satisfies a threshold.

22. The apparatus of claim 15, wherein the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a ranking change associated with the L1 metric in the candidate cell.

23. The apparatus of claim 15, wherein the L1 metric in the candidate cell satisfies the trigger event condition based at least in part on a number of beams associated with the candidate cell that satisfies a condition.

24. The apparatus of claim 15, wherein the L1 metric is a spatially or temporally filtered L1 measurement.

25. An apparatus according to claim 15, wherein the trigger event condition is defined at least in part based on one or more of: a moment in time, an average value within a certain time period, a maximum value within the time period, a minimum value within the time period, or a number of occurrences within the time period.

26. The apparatus of claim 15, wherein the L1 measurement report is based at least in part on one or more of a start condition or a stop condition.

27. The apparatus of claim 26, wherein the presence of the stop condition is based at least in part on the triggering event condition.

28. The apparatus of claim 26, wherein the L1 measurement report configuration indicates that the L1 measurement report is to be sent a single time or is to be sent multiple times until the stopping condition is met, wherein the stopping condition is based at least in part on a maximum number of L1 measurement reports.

29. A method of wireless communication performed by a user equipment (UE), the method comprising: Measuring Layer 1 (L1) metrics in candidate cells associated with Layer 1 or Layer 2 Triggered Mobility (LTM); Determining that the L1 metric in the candidate cell meets a trigger event condition; as well as An L1 measurement report is sent to a network node based at least in part on the L1 metric in the candidate cell satisfying the triggering event condition.

30. A method of wireless communication performed by a network node, the method comprising: Sending layer 1 (L1) measurement report configuration to user equipment (UE); as well as An L1 measurement report is received from the UE based at least in part on an L1 metric in a candidate cell satisfying a triggering event condition and based at least in part on the L1 measurement reporting configuration, the L1 metric in the candidate cell being associated with layer 1 or layer 2 triggered mobility (LTM).

Images