Event-driven beam reporting for lower layer triggered mobility

Abstract

Methods, systems, and devices for wireless communication are described. For example, a user equipment (UE) can monitor signal strengths of one or more beams, including beams within a serving cell and beams within a candidate cell. The UE can detect a triggering event for a beam report, which can be based on a change in the signal strengths of the one or more beams. Based on detecting the triggering event, the UE can transmit a beam report. In some examples, a network entity associated with the serving cell can obtain the beam report from the UE and adjust parameters associated with the beams based on the beam report. For example, the network entity can determine that a beam within the candidate cell has a stronger signal strength than a beam within the serving cell and output a command for the UE to handover to a second serving cell.

Description

Technical Field

[0001] The following content relates to wireless communications, including event-driven beam reporting for mobility triggered at lower layers. Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE).

[0003] Some wireless communication systems can support UE mobility for cell handover. However, they may not support UE mobility for communication via lower-layer signaling. Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses for supporting event-driven beam reporting for lower-layer triggered mobility (LTM). For example, the described technology provides a user equipment (UE) for monitoring the signal strength of one or more beams, which may include a first beam within a serving cell and a second beam within one or more candidate cells. The UE can detect a trigger event for beam reporting, which may be based on a change in the signal strength of the one or more beams. Based on the detection of the trigger event, the UE can send a beam report. In some examples, a network entity associated with the serving cell can obtain the beam report from the UE and adjust parameters associated with the beam based on the beam report. For example, the network entity can determine that the signal strength of the second beam within a candidate cell is stronger than that of the first beam within the serving cell and output a control message for the UE to hand over to the second serving cell (e.g., perform an LTM procedure).

[0005] A method for wireless communication by a UE is described. The method may include: monitoring the corresponding signal strength of a set of multiple beams, wherein the set of multiple beams includes one or more first beams in a serving cell for the UE and one or more second beams in one or more candidate cells associated with an LTM procedure for the UE; detecting a trigger event for a beam report associated with the LTM procedure for the UE, wherein the trigger event is associated with a change in the signal strength of one or more beams from the set of multiple beams; and transmitting a beam report based on the detection of the trigger event.

[0006] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; a transceiver; and one or more processors coupled to the one or more memories and the transceiver. The one or more processors may be able to operate individually or jointly to execute code that causes the UE to: monitor the corresponding signal strength of a set of multiple beams, wherein the set of multiple beams includes one or more first beams within the serving cell for the UE and one or more second beams within one or more candidate cells associated with an LTM procedure for the UE; detect a trigger event for a beam report associated with the LTM procedure for the UE, wherein the trigger event is associated with a change in the signal strength of one or more beams from the set of multiple beams; and transmit the beam report via the transceiver based on the detection of the trigger event.

[0007] Another UE for wireless communication is described. The UE may include: components for monitoring the signal strength of a set of multiple beams, wherein the set of multiple beams includes one or more first beams within the serving cell of the UE and one or more second beams within one or more candidate cells associated with an LTM procedure for the UE; components for detecting a trigger event for a beam report associated with an LTM procedure for the UE, wherein the trigger event is associated with a change in the signal strength of one or more beams from the set of multiple beams; and components for transmitting a beam report based on the detection of the trigger event.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: monitor the corresponding signal strength of a set of multiple beams, wherein the set of multiple beams includes one or more first beams in a serving cell for a UE and one or more second beams in one or more candidate cells associated with an LTM procedure for the UE; detect a trigger event for a beam report associated with an LTM procedure for the UE, wherein the trigger event is associated with a change in the signal strength of one or more beams from the set of multiple beams; and transmit the beam report based on the detection of the trigger event.

[0009] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for performing an LTM procedure based on transmitting a beam report; and for communicating with a second serving cell based on performing an LTM procedure, wherein the second serving cell includes candidate cells from one or more candidate cells.

[0010] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, detecting a triggering event for a beam report may include operations, features, components, or instructions for detecting that one or more signal strengths associated with a set of multiple beams may be below a threshold. In some examples of the methods, UEs, and nontransitory computer-readable media described herein, one or more signal strengths may be associated with a serving cell or at least one candidate cell from one or more candidate cells.

[0011] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, detecting a triggering event for beam reporting may include operations, features, components, or instructions for detecting that the signal strength associated with one or more second beams exceeds a threshold.

[0012] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the threshold may be associated with the signal strength of a subset of one or more second beams. In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the threshold may be associated with an offset from the signal strength of a subset of one or more first beams.

[0013] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, detecting a triggering event for a beam report may include operations, features, components, or instructions for detecting a decrease in signal strength associated with one or more first beams, the triggering event being based on a combination of a signal strength associated with one or more second beams exceeding a threshold and a decrease in signal strength associated with one or more first beams.

[0014] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, detecting a triggering event for beam reporting may include operations, features, components, or instructions for detecting a change in relative signal strength associated with at least two of the one or more second beams, wherein the at least two second beams may each be in the same candidate cell in one or more candidate cells, or wherein the at least two second beams may be in one or more candidate cells.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, detecting triggering events for beam reporting may include operations, features, components, or instructions for detecting changes associated with the ranking of one or more candidate cells, the ranking being based on a corresponding signal quality metric for the one or more candidate cells, which may be based on the corresponding signal strength of a set of multiple beams.

[0016] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, beam reports indicate the number of cells whose information is included in the beam report, the number of reference signals whose information is included in the beam report, or any combination thereof.

[0017] In some examples of the methods described herein, UEs, and nontransitory computer-readable media, the beam report indicates, for each cell whose information is included in the beam report, a corresponding cell identifier, a corresponding number of reference signals, a corresponding reference signal index for each reference signal included in the corresponding number of reference signals, a corresponding reference signal metric for each reference signal included in the corresponding number of reference signals, or any combination thereof.

[0018] In some examples of the methods described herein, UEs, and nontransitory computer-readable media, beam reporting includes a first value associated with a first reference signal metric and a second value associated with a second reference signal metric, and the second value may be relative to the first value.

[0019] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, transmitting a beam report may include operations, features, components, or instructions for: transmitting a first portion of the beam report, the first portion indicating the number of reference signals whose information is included in the beam report, the number of cells whose information is included in the beam report, or both; and transmitting a second portion of the beam report, the second portion indicating a corresponding reference signal index, a corresponding reference signal metric, or both for each reference signal whose information is included in the beam report, wherein transmitting the first and second portions may be based on the beam report being transmitted via one or more uplink control information messages.

[0020] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for receiving control signaling that allocates one or more uplink transmission resources for the UE to use for transmitting beam reports.

[0021] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for sending a request to transmit beam reports, wherein control signaling for allocating one or more uplink transmission resources for the UE to use for transmitting beam reports may be received on a request basis.

[0022] A method for wireless communication by a network entity is described. The method may include: obtaining a beam report from a UE, wherein the beam report is associated with an LTM procedure for the UE and is based on a triggering event associated with changes in the signal strength of one or more beams from a set of multiple beams, the set of multiple beams including one or more first beams in the serving cell for the UE and one or more second beams in one or more candidate cells associated with the LTM procedure for the UE; and adjusting one or more parameters associated with the one or more beams based on the beam report.

[0023] A network entity for wireless communication is described. The network entity may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to enable the network entity to: obtain a beam report from a UE, wherein the beam report is associated with an LTM procedure for the UE and based on a triggering event associated with changes in the signal strength of one or more beams from a set of multiple beams, the set of multiple beams including one or more first beams in the serving cell for the UE and one or more second beams in one or more candidate cells associated with the LTM procedure for the UE; and adjust one or more parameters associated with the one or more beams based on the beam report.

[0024] Another network entity for wireless communication is described. This network entity may include: components for obtaining beam reports from a UE, wherein the beam reports are associated with an LTM procedure for the UE and based on a triggering event associated with changes in the signal strength of one or more beams from a set of multiple beams, the set of multiple beams including one or more first beams in the serving cell for the UE and one or more second beams in one or more candidate cells associated with the LTM procedure for the UE; and components for adjusting one or more parameters associated with the one or more beams based on the beam reports.

[0025] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: obtain a beam report from a UE, wherein the beam report is associated with an LTM procedure for the UE and based on a triggering event associated with changes in the signal strength of one or more beams from a set of multiple beams, the set of multiple beams including one or more first beams within the serving cell for the UE and one or more second beams within one or more candidate cells associated with the LTM procedure for the UE; and adjust one or more parameters associated with the one or more beams based on the beam report.

[0026] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: determining, based on adjusting one or more parameters, that the signal strength of at least one second beam from one or more candidate cells may be stronger than the signal strength of at least one first beam from one or more first beams in the serving cell; and based on this determination, outputting a control message instructing the UE to hand over to a second serving cell via an LTM procedure, wherein the second serving cell may be associated with at least one second beam and includes candidate cells from one or more candidate cells.

[0027] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, adjusting one or more parameters may include operations, features, components, or instructions for: updating the ordering associated with a set of multiple beams, updating the ordering associated with one or more candidate cells, activating or deactivating a transmit configuration indication state associated with at least one beam from the set of multiple beams, or any combination thereof. Attached Figure Description

[0028] Figure 1 and Figure 2 An example of a wireless communication system supporting event-driven beam reporting for lower-layer triggered mobility (LTM) is shown, according to one or more aspects of this disclosure.

[0029] Figure 3 An example of a process flow supporting event-driven beam reporting for LTM is shown, according to one or more aspects of this disclosure.

[0030] Figure 4 and Figure 5 A block diagram of an apparatus supporting event-driven beam reporting for LTM is shown, according to one or more aspects of this disclosure.

[0031] Figure 6A block diagram of a communication manager supporting event-driven beam reporting for LTM, according to one or more aspects of this disclosure, is shown.

[0032] Figure 7 A diagram of a system including a device supporting event-driven beam reporting for LTM, according to one or more aspects of this disclosure, is shown.

[0033] Figure 8 and Figure 9 A block diagram of an apparatus supporting event-driven beam reporting for LTM is shown, according to one or more aspects of this disclosure.

[0034] Figure 10 A block diagram of a communication manager supporting event-driven beam reporting for LTM, according to one or more aspects of this disclosure, is shown.

[0035] Figure 11 A diagram of a system including a device supporting event-driven beam reporting for LTM, according to one or more aspects of this disclosure, is shown.

[0036] Figures 12 to 14 A flowchart illustrating a method for supporting event-driven beam reporting for LTM according to one or more aspects of this disclosure is shown. Detailed Implementation

[0037] Some wireless communication systems can support inter-cell mobility, allowing user equipment (UE) to switch from a serving cell to a candidate cell, for example, as the UE moves or as the beam strength associated with the cell changes. In some cases, this cell handover (e.g., cell transfer) can be supported by communication via higher-layer signaling such as Layer 3 (L3) signaling. Extending cell handover facilitated by lower-layer signaling such as Layer 1 (L1) and / or Layer 2 (L2) signaling can reduce mobility latency. Lower-layer triggered mobility (LTM) procedures may include serving cell updates or changes to the downlink beam received by the UE. However, a mechanism for the UE to provide UE-initiated beam reports or beam management requests based on one or more events observed or detected by the UE may not exist.

[0038] The techniques described herein enable a UE to detect events (such as changes in the signal strength of one or more beams in the serving cell, one or more candidate cells, or both) and send beam reports to the serving cell. For example, the UE can send beam reports based on one or more beams in the serving cell or one or more candidate cells becoming worse than a threshold difference, or one or more beams in one or more candidate cells becoming better than one or more beams in the serving cell by an offset. The UE can also send beam reports based on changes in the strength order of one or more beams in the corresponding candidate cells, changes in the strength order of beams in all candidate cells, or changes in the order of the candidate cells themselves.

[0039] In some examples, the payload of a beam report can be flexible and include various types of information. For example, a beam report may indicate the total number of reported cells, the total number of reported reference signals (e.g., reference signals may correspond to beam pairs of cells), or both. For each reported cell, the beam report may indicate the cell identifier, the number of reported reference signals, the reference signal index, and the reference signal metric for each reported reference signal. In some examples, the UE may transmit a beam report in two parts. The first part may include an indication of the total number of reported reference signals, the total number of reported cells, or both. The second part may include the reference signal index and reference signal metric for each reported reference signal. Additionally, the network entity associated with the serving cell may send control signaling to the UE instructing uplink signaling to be used for transmitting the beam report. In some cases, the UE may send a beam report request, receive uplink signaling, and transmit the beam report based on the received response. In other cases, the UE may send beam reports in the uplink control information (UCI) or media access control-control element (MAC-CE).

[0040] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are further illustrated and described by way of process flow. The aspects of this disclosure are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to event-driven beam reporting for lower-layer triggered mobility, and are further described by way of these apparatus diagrams, system diagrams, and flowcharts.

[0041] Figure 1An example of a wireless communication system 100 supporting event-driven beam reporting for lower-layer triggered mobility, according to one or more aspects of this disclosure, is illustrated. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 105), one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0042] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0043] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Examples of UE 115 are illustrated herein. The UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including UE 115 or network entity 105), such as... Figure 1 As shown.

[0044] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0045] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via backhaul communication link 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof, or may include one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with the core network 130 via communication link 155.

[0046] One or more of the network entities 105 or network equipment described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, Node B, evolved Node B (eNB), next-generation Node B or gigabit Node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home Node B, home evolved Node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0047] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across multiple network entities (e.g., network entity 105), such as integrated access and backhaul (IAB) networks, open RAN (O-RAN) (e.g., network configurations sponsored by the O-RAN Alliance), or virtualized RAN (vRAN) (e.g., cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a central unit (CU) such as CU 160, a distributed unit (DU) such as DU 165, a radio unit (RU) such as RU 170, a RAN intelligent controller (RIC) such as RIC 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) system such as SMO system 180, or any combination thereof. RU170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0048] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) may connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or a combination thereof, and DU 165, RU 170, or both may host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and may each be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split may be employed between DU 165 and RU 170, such that DU 165 may support one or more layers of the protocol stack, and RU 170 may support one or more different layers of the protocol stack. DU 165 may (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by a different one of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) that communicate via such communication links.

[0049] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities in network entity 105 (e.g., network entity 105 or IAB node 104) may be partially controlled by each other. IAB node 104 may be referred to as a donor entity or IAB donor. DU 165 or RU 170 may be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor entities (e.g., IAB donors) may communicate with one or more additional devices (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DU 165) of a coupled IAB donor. The IAB-MT may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include one or more DUs (e.g., DU 165) that support communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., IAB node 104, or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0050] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180).

[0051] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances, vehicles, or meters.

[0052] The UE 115 described herein may be able to communicate with various types of devices, such as the UE 115 which may sometimes operate as a relay, and network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0053] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to utilize multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “transmit,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).

[0054] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0055] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, while The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0056] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems (such as wireless communication system 100), time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0057] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0058] Depending on the technology, carriers can be used to multiplex physical channels for communication. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to transmit control information to UE 115 (e.g., one or more UEs), or it may include a UE-specific search space set configured to transmit control information to UE 115 (e.g., a particular UE).

[0059] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, etc., or may include buildings, subsets of buildings, or external space between or overlapping coverage areas, etc.

[0060] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with network entities 105 operating at lower power (e.g., base station 140 operating at lower power) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0061] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0062] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas (such as coverage area 110). In some examples, coverage areas 110 associated with different technologies (e.g., different coverage areas) may overlap, but coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., network entity 105). In some other examples, overlapping coverage areas (such as coverage area 110) associated with different technologies may be supported by different network entities (e.g., network entity 105). The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different RATs to support communication for coverage area 110 (e.g., different coverage areas).

[0063] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0064] In some examples, UE 115 may be configured to support direct communication with other UEs (e.g., one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as D2D communication link 135) (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group performing D2D communication may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, in which each UE 115 transmits to one or more UEs in the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

[0065] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities can connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0066] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).

[0067] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0068] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0069] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0070] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 in different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

[0071] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., network entity 105 or UE 115) along a single beam direction (e.g., a direction associated with a receiving device such as another network entity 105 or UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 in different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0072] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a configured set of beams across the system bandwidth or one or more subbands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) in one or more directions, UE 115 may use similar techniques to transmit signals multiple times in different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0073] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different directional listening weight sets); or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0074] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0075] In some examples, at least the serving cell can be updated via L1 / L2 signaling based on L1 measurements. L1 / L2-based inter-cell mobility for mobility latency reduction can include configuration and maintenance for multiple candidate cells to allow for the application of candidate cell configurations. In some cases, dynamic handover mechanisms between candidate serving cells (including serving and secondary cells) can be used based on L1 / L2 signaling. L1 enhancements for inter-cell beam management (including L1 measurements and reporting, and beam indication) can be implemented herein. In some examples, advance timing management and CU-DU interface signaling can support L1 / L2 mobility. The L1 / L2-based inter-cell mobility process can be applied to various scenarios, such as standalone, intra-DU, and intra-CU / inter-DU scenarios, both intra-frequency and inter-frequency, both FR1 and FR2, and the source and target cells can be synchronous or asynchronous. In some examples, measurement-related enhancements supporting LTM can be supported. For example, UE 115 can support event-triggered L1 measurement reporting. Additionally or alternatively, it may include support for CSI-RS measurements used in the LTM process, and implementation of CSI-RS-based beam management, and / or support for other physical layer operations of candidate cells prior to LTM.

[0076] Some wireless communication systems (e.g., wireless communication system 100) can support inter-cell mobility, allowing UE 115 to switch from a serving cell to a candidate cell, for example, as UE 115 moves or as the beam strength associated with the cell changes. In some cases, such cell handover (e.g., cell transfer) can be supported by communication via higher-layer signaling such as L3 signaling. Extending cell handover facilitated by lower-layer signaling such as L1 and / or L2 signaling can reduce mobility latency. The LTM procedure may include serving cell updates or changes to the downlink beam received at UE 115. However, a mechanism for UE 115 to provide UE-initiated beam reports or beam management requests based on one or more events observed or detected by UE 115 may not exist.

[0077] The techniques described herein enable UE 115 to detect events such as changes in the signal strength of one or more beams in the serving cell, one or more candidate cells, or both, and to send beam reports to the serving cell. For example, UE 115 can send beam reports based on one or more beams in the serving cell or one or more candidate cells becoming worse than a threshold difference, or one or more beams in one or more candidate cells becoming better than one or more beams in the serving cell by an offset. UE 115 can also send beam reports based on changes in the strength order of one or more beams in the corresponding candidate cells, changes in the strength order of beams in all candidate cells, or changes in the order of the candidate cells themselves.

[0078] In some examples, the payload of a beam report can be flexible. For example, a beam report can indicate the total number of reported cells, the total number of reported reference signals (e.g., reference signals may correspond to beam pairs of cells), or both. For each reported cell, the beam report can indicate the cell identifier, the number of reported reference signals, the reference signal index, and the reference signal metric for each reported reference signal. In some examples, UE 115 can transmit a beam report in two parts. The first part may include an indication of the total number of reported reference signals, the total number of reported cells, or both. The second part may include the reference signal index and reference signal metric for each reported reference signal. Additionally, the network entity associated with the serving cell can send control signaling to UE 115 instructing it to use uplink signaling for transmitting the beam report. In some cases, UE 115 can send a beam report request, receive uplink signaling, and transmit the beam report based on the received response. In other cases, UE 115 can send beam reports directly in UCI or MAC-CE messages.

[0079] Figure 2 An example of a wireless communication system 200 supporting event-driven beam reporting for LTM, according to one or more aspects of this disclosure, is shown. The wireless communication system 200 may implement as referenced... Figure 1 The described aspects of the wireless communication system 100 may be implemented by or by aspects of the wireless communication system. For example, the wireless communication system 200 may include network entity 105 and UE 115-a, which may be, as referenced herein, Figure 1 Examples of the corresponding devices described.

[0080] The wireless communication system 200 supports communication between UE 115-a and network entity 105. Figure 2In the example, network entity 105-a may be associated with cell 205 (e.g., serving that cell), which is associated with a coverage area (e.g., coverage area 110) supported by network entity 105-a. Cell 205 may be an example of the serving cell of UE 115-a.

[0081] UE 115-a can also be within the coverage area of ​​one or more cells 210 supported by one or more other network entities 105. For example, wireless communication system 200 may include network entities 105-b, 105-c, and 105-d that respectively support cells 210-a, 210-b, and 210-c. Cell 210 may be an example of a candidate cell that UE 115-a can hand over to serve as the serving cell of UE 115-a. For example, UE 115-a may perform a handover procedure (e.g., LTM procedure) to candidate cell 210 for various reasons, such as to obtain better service for UE 115-a relative to serving cell 205, to alleviate excessive load on serving cell 205, based on UE 115-a moving 245 to the appropriate coverage area of ​​candidate cell 210, or a combination thereof.

[0082] Wireless communication system 200 can support L1 / L2 supported (e.g., triggered) mobility for UE 115-a. That is, UE 115-a can hand over to candidate cell 210 based on communication of L1 and / or L2 signaling (e.g., rather than higher-layer signaling, such as Layer 3 (L3) signaling). In some examples, UE 115-a can hand over to candidate cell 210 based on signaling received from serving cell 205 (e.g., control signaling). In some examples, network entity 105-a can transmit signaling based on the signal strength of one or more active beams 215, one or more inactive beams 220, or any combination thereof. In some examples, active beam 215 can refer to a beam with an Active Transmit Configuration Indication (TCI) state. Additionally or alternatively, active beam 215 can refer to any beam that can be used by UE 115-a for communication. For example, active beam 215 may be known to network entity 105-a (e.g., active beam 215 is included in the list of beams at network entity 105-a). In some examples, inactive beam 220 may refer to a beam with an inactive TCI state or a beam unknown to network entity 105-a (e.g., inactive beam 220-a).

[0083] In some examples, serving cell 205 and each candidate cell 210 may include one or more active beams 215 and one or more inactive beams 220. The beam strength of one or more active beams 215 or one or more inactive beams 220 may change due to events. For example, UE 115-a may perform a movement 245, causing a relative change in the signal strength of one or more active beams 215 or one or more inactive beams 220. However, UE 115-a may not report the event until it receives a request for beam reporting from network entity 105-a, which may result in increased latency for improving communication conditions.

[0084] The techniques described herein enable UE 115-a to detect events and send beam reports to network entity 105-a. For example, UE 115-a may detect that the active beam 215-a in serving cell 205 has become worse than (e.g., degraded) an absolute threshold. UE 115-a may send beam report 240 based on the detected event. In some examples, UE 115-a may receive control signaling 225 that allocates uplink signaling to UE 115-a to send beam report 240. In such examples, UE 115-a may send beam report 240 via uplink signaling. In some examples, UE 115-a may send a request 230 for uplink signaling to send beam report 240, and network entity 105-a may send control signaling 225 based on receiving request 230. Additionally or alternatively, UE 115-a may transmit beam report 240 in UCI or MAC-CE. For example, UCI may include resources for transmitting beam report 240, and UE 115-a may transmit MAC-CE in any Physical Uplink Shared Channel (PUSCH).

[0085] For reference Figure 3 In further detail, beam reports 240 may indicate the reported cell identifier, the number of reports of reference signals, the reference signal index of each reported reference signal, the reference signal metric of each reported reference signal, or any combination thereof. Based on the received reports, network entity 105-a may update the ordering of cells 205 and 210, activate or deactivate one or more beams within serving cell 205 or one or more candidate cells 210, send a cell handover command based on the updated ordering or activation, or any combination thereof.

[0086] In some examples, network entity 105-a can update the ordering of active beams 215 and inactive beams 220 associated with cells included in beam report 240. For example, UE 115-a can detect changes in the intensity order of one or more active beams 215 or one or more inactive beams 220 in a corresponding candidate cell 210 (e.g., the intensity of active beam 215-d may decrease in candidate cell 210-c). Based on the detected change in intensity order in the corresponding candidate cell 210, UE 115-a can send beam report 240. Network entity 105-a can update the ordering of one or more active beams 215 and one or more inactive beams 220 based on beam report 240 (e.g., network entity 105-a may reconsider the optimal beam for candidate cell 210).

[0087] Additionally or alternatively, UE 115-a may detect changes in the strength order of one or more active beams 215 or one or more inactive beams 220 across any candidate cell 210 (e.g., the signal strength of active beam 215-d may increase, and the signal strength of active beam 215-c may decrease), and send a beam report 240. Network entity 105-a may update the beam strength order based on the LTM beam report 240 (e.g., network entity 105-a may reconsider the new beam report for all candidate cells). Additionally or alternatively, network entity 105-a may activate one or more inactive beams 220 or deactivate one or more active beams 215 based on the beam report 240. For example, beam report 240 may indicate that inactive beam 220-c has a higher signal strength than active beam 215-c (e.g., or inactive beam 220-d has a higher signal strength than active beam 215-d). Network entity 105-a can activate inactive beam 220-c and deactivate active beam 215-c based on beam report 240.

[0088] In some examples, network entity 105-a may send cell handover command 235 based on updating the order of active beam 215 and inactive beam 220 or updating the activation status of beams (e.g., activating or deactivating one or more beams). Cell handover command 235 may instruct UE 115-a to hand over from serving cell 205 to one of the candidate cells in candidate cells 210 (e.g., 210-a, 210-b, or 210-c). For example, active beam 215-b and inactive beam 220-b in cell 210-b may have the highest strength among the other candidate cells 210 and serving cell 205. Therefore, for UE 115-a, handover from serving cell 205 to cell 210-b via cell handover using lower-layer signaling (e.g., LTM procedure) may be advantageous.

[0089] Figure 3 An example of a process flow 300 supporting event-driven beam reporting for LTM according to one or more aspects of this disclosure is shown. Process flow 300 can be implemented by aspects of wireless communication systems 100 and 200. For example, UE 115-b and network entity 105-e can perform aspects of process flow 300; the UE and network entity can be examples of UE 115 or network entity 105 as described herein. In the following description of process flow 300, the operations performed by UE 115-b and network entity 105-e may be performed in a different order than shown. Some operations may be omitted from process flow 300, and other operations may be added to process flow 300. Furthermore, although some operations or signaling are shown to occur at different times for discussion purposes, these operations may occur simultaneously.

[0090] In some examples, at 305, UE 115-b may send a request to send a beam report (e.g., UE 115-b may request resources for sending a beam report). In some examples, this request is a scheduling request. For example, a scheduling request may be included in the UCI of the Physical Uplink Control Channel (PUCCH), PUSCH, or both. Additionally or alternatively, the scheduling request may be included in a MAC-CE message. In some examples (e.g., for a UCI-based request), UE 115-b may indicate a bitmap, where each bit may correspond to a request for an event. UE 115-b may also indicate that no event was detected. In some examples, UE 115-b may send a beam report in response to a send request.

[0091] At 310, UE 115-b can receive uplink signaling for sending beam reports to network entity 105-e in the serving cell (e.g., for L1 measurements in candidate cells). For example, the uplink signaling can allocate one or more uplink transmission resources for UE 115-b to use for sending beam reports. In some examples, UE 115-b can receive uplink signaling in response to a request for reporting resources. UE 115-b can send beam reports in UCI or MAC-CE messages. For example, network entity 105-e can allocate UCI resources, and UE 115-b can send MAC-CE messages in any PUSCH (e.g., including Data Group (DG) or Configuration Grant (CG) PUSCH).

[0092] At 315, UE 115-b can monitor the corresponding signal strengths of multiple beams. These multiple beams may include a subset of one or more active beams and a subset of one or more inactive beams, as further referenced. Figure 2As described. Multiple beams may include one or more first beams within the serving cell for UE 115-b (e.g., associated with network entity 105-e) and one or more second beams within one or more candidate cells associated with the LTM procedure for UE 115-b (e.g., associated with network entity 105-e or another network entity 105). For example, UE 115-b may monitor multiple beams in response to a triggering event.

[0093] At 320, UE 115-b can detect one or more triggering events described herein. Triggering events may include one or more beams in a cell (e.g., a serving cell or a candidate cell) whose strength has decreased. For example, the beam strength of one or more active beams in the serving cell may decrease below a threshold (e.g., an absolute threshold). Additionally or alternatively, UE 115-a can detect the beam strength of one or more active beams in a candidate cell decreasing below a threshold (e.g., the same threshold as or a different threshold than the beam strength of one or more beams in the serving cell). In some examples, triggering events may include the signal strength of one or more inactive beams in the candidate cell exceeding a threshold, exceeding the signal strength of one or more active beams in the candidate cell, or both.

[0094] The triggering event may also include the signal strength of one or more active beams or one or more inactive beams in the candidate cell becoming better than the beam strength of one or more active beams in the serving cell by an offset. For example, the signal strength of one or more active beams in the candidate cell may increase by a relative amount compared to the signal strength of one or more active beams in the serving cell. In some examples, the triggering event may include the signal strength of one or more active beams in the candidate cell becoming better than the signal strength of one or more inactive beams in the serving cell by an offset. Additionally or alternatively, the triggering event may include the signal strength of one or more beams in the candidate cell increasing when the signal strength of one or more beams in the serving cell decreases.

[0095] In some examples, a triggering event may include a change in the order of strength (e.g., Reference Signal Received Power (RSRP)) of one or more beams in a candidate cell. For example, the relative signal strength associated with at least two beams associated with a corresponding candidate cell may change. In such examples, network entity 105-e may reconsider the beams of candidate cells in a TCI indication via a cell handover command. Additionally or alternatively, a triggering event may include a change in the order of strength of one or more beams in one or more candidate cells. Network entity 105-e may reconsider beam reports for candidate cells. Additionally or alternatively, event triggering may include a change in the order of candidate cells (e.g., the ranking of candidate cells). For example, a cell-level metric may rank the candidate cells. In such examples, network entity 105-e may reconsider candidate cells for LTM handover. The triggering events described herein are illustrative examples and not a comprehensive list. For example, UE 115-b may detect triggering events for any change in the signal strength of any of multiple beams.

[0096] At 325, UE 115-b can send a beam report based on the detection of a triggering event. For example, UE 115-b can initiate a beam report for candidate cells in LTM. In some examples, the payload of the beam report can be flexible, with additional indications in the report. For example, UE 115-b can indicate the number of cells whose information is included in the beam report (e.g., the total number). The indicated number of cells can be based on configuration (e.g., the number can be counted for both serving cells and LTM candidate cells, or candidate cells). Additionally or alternatively, UE 115-b can indicate the number of reference signals whose information is included in the beam report (e.g., the total number).

[0097] For each reported cell, UE 115-b may indicate a corresponding cell identifier, a corresponding number of reference signals, a corresponding reference signal index for each reported reference signal, a corresponding reference signal metric for each reported reference signal, or any combination thereof. If a reference signal is associated with a cell identifier, the cell identifier indication may be optional. Additionally or alternatively, if the number of reference signals is fixed for a cell, the reported number of reference signals may be optional. In some examples, UE 115-b may report a first reference signal metric having a first value (e.g., a full value, such as 7 bits for L1-RSRP or L1 Signal-to-Noise Ratio (SINR)), and UE 115-b may report any remaining reference signals having a second value relative to the first value (e.g., 4 bits for L1-RSRP or L1-SINR).

[0098] In some examples, UE 115-b may transmit beam reports in two parts (e.g., for UCI-based beam reports). For example, at 330, UE 115-b may transmit a first part of the beam report. The first part of the beam report may indicate the total number of reference signals whose information is included in the beam report, the total number of cells whose information is included in the beam report, or the number of reported cells in the beam report and the number of reported reference signals for each reported cell. In some examples, at 335, UE 115-b may transmit a second part of the beam report. The second part of the beam report may include a corresponding reference signal index, a corresponding reference signal metric, or both for each reference signal whose information is included in the beam report. In some examples, the reference signal index may be associated with a serving cell identifier or candidate cell identifier and a synchronization signal block (SSB) or CSI-RS identifier (e.g., based on the indication of the total number of reported reference signals in the first part of the beam report). In some other examples, the information included in the reported number of reference signals in each cell may be fixed (e.g., the total number of reported cells is indicated based on the first part of the beam report).

[0099] At 340, network entity 105-e can adjust one or more parameters associated with one or more beams based on beam reports. For example, network entity 105-e can update the ordering associated with multiple beams, update the ordering associated with one or more candidate cells, activate or deactivate the TCI state associated with at least one beam from multiple beams, or any combination thereof. For example, network entity 105-e can use cell handover commands to reconsider the beams of candidate cells in the TCI indication (e.g., the beam with the highest signal strength), reconsider new beam reports for candidate cells, or reconsider candidate cells (e.g., the best candidate cell for LTM handover), and so on.

[0100] At point 345, network entity 105-e may send a control message instructing UE 115-b to hand over to a second serving cell via an LTM procedure. For example, network entity 105-e may determine, based on adjusting one or more parameters, that the signal strength of at least one beam in one or more candidate cells is stronger than the signal strength of at least one beam from the serving cell. In some examples, the second serving cell may include a candidate cell among one or more candidate cells. At point 350, UE 115-b may perform an LTM procedure. In some examples, at point 355, UE 115-b may communicate with the second serving cell based on performing an LTM procedure.

[0101] Figure 4A block diagram 400 illustrates a device 405 supporting event-driven beam reporting for LTM according to one or more aspects of this disclosure. Device 405 may be an example of various aspects of UE 115 as described herein. Device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. Device 405, or one or more components of device 405 (e.g., receiver 410, transmitter 415, communication manager 420), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0102] Receiver 410 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to event-driven beam reporting for LTM). The information may be passed to other components of device 405. Receiver 410 may utilize a single antenna or a collection of antennas.

[0103] Transmitter 415 may provide components for transmitting signals generated by other components of device 405. For example, transmitter 415 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with event-driven beamforming for LTM). In some examples, transmitter 415 may be co-located with receiver 410 in a transceiver module. Transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0104] The communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be examples of components used to perform various aspects of event-driven beam reporting for LTM as described herein. For example, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0105] In some examples, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0106] Additionally or alternatively, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) (e.g., referred to as processor executable code) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be executed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, to support components for performing the functions described in this disclosure).

[0107] In some examples, the communication manager 420 may be configured to use or otherwise cooperate with the receiver 410, transmitter 415, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 420 may receive information from the receiver 410, transmit information to the transmitter 415, or be integrated with the receiver 410, transmitter 415, or both to acquire information, output information, or perform various other operations as described herein.

[0108] The communication manager 420 may support wireless communication according to examples disclosed herein. For example, the communication manager 420 may be capable of, configured to, or operable to support components for monitoring the corresponding signal strength of a set of multiple beams, wherein the set of multiple beams includes one or more first beams within the serving cell for the UE and one or more second beams within one or more candidate cells associated with an LTM procedure for the UE. The communication manager 420 may be capable of, configured to, or operable to support components for detecting trigger events for beam reports associated with an LTM procedure for the UE, wherein the trigger event is associated with a change in signal strength from one or more beams in the set of multiple beams. The communication manager 420 may be capable of, configured to, or operable to support components for transmitting beam reports based on the detection of a trigger event.

[0109] By including or configuring a communication manager 420 according to an example as described herein, device 405 (e.g., at least one processor that controls or otherwise couples to receiver 410, transmitter 415, communication manager 420, or a combination thereof) can, for example, support techniques for reducing processing and utilizing communication resources more efficiently by supporting event-driven beam reporting for L1 / L2 mobility.

[0110] Figure 5 A block diagram 500 is shown of a device 505 supporting event-driven beam reporting for LTM according to one or more aspects of this disclosure. Device 505 may be an example of aspects of device 405 or UE 115 as described herein. Device 505 may include receiver 510, transmitter 515, and communication manager 520. Device 505 or one or more components of device 505 (e.g., receiver 510, transmitter 515, communication manager 520) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0111] Receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to event-driven beam reporting for LTM). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0112] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to event-driven beam reporting for LTM). In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0113] Device 505 or its various components may be examples of parts for performing various aspects of event-driven beam reporting for LTM as described herein. For example, communication manager 520 may include signal monitoring component 525, triggering component 530, beam reporting component 535, or any combination thereof. Communication manager 520 may be examples of aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to use or otherwise cooperate with receiver 510, transmitter 515, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in combination with receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0114] Communication manager 520 may support wireless communication according to examples disclosed herein. Signal monitoring component 525 is capable of, configured to, or operable to support components for monitoring the corresponding signal strength of a set of multiple beams, wherein the set of multiple beams includes one or more first beams in the serving cell for the UE and one or more second beams in one or more candidate cells associated with an LTM procedure for the UE. Triggering component 530 is capable of, configured to, or operable to support components for detecting trigger events for beam reports associated with an LTM procedure for the UE, wherein the trigger event is associated with a change in signal strength from one or more beams in the set of multiple beams. Beam reporting component 535 is capable of, configured to, or operable to support components for sending beam reports based on the detection of a trigger event.

[0115] Figure 6A block diagram 600 is shown of a communication manager 620 supporting event-driven beam reporting for LTM according to one or more aspects of this disclosure. The communication manager 620 may be an example of a communication manager 420, a communication manager 520, or aspects thereof as described herein. The communication manager 620 or its various components may be examples of parts for performing various aspects of event-driven beam reporting for LTM as described herein. For example, the communication manager 620 may include a signal monitoring component 625, a triggering component 630, a beam reporting component 635, an LTM component 640, a cell handover component 645, a first reporting portion component 650, a second reporting portion component 655, an uplink allocation component 660, a beam reporting request component 665, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0116] The communication manager 620 may support wireless communication according to examples disclosed herein. The signal monitoring component 625 is capable of, configured to, or operable to support components for monitoring the corresponding signal strength of a set of multiple beams, wherein the set of multiple beams includes one or more first beams within the serving cell for the UE and one or more second beams within one or more candidate cells associated with an LTM procedure for the UE. The triggering component 630 is capable of, configured to, or operable to support components for detecting trigger events for beam reports associated with an LTM procedure for the UE, wherein the trigger event is associated with a change in signal strength from one or more beams in the set of multiple beams. The beam reporting component 635 is capable of, configured to, or operable to support components for sending beam reports based on the detection of a trigger event.

[0117] In some examples, LTM component 640 is capable of, configured to, or operable to support components for performing an LTM procedure based on transmitted beam reports. In some examples, cell handover component 645 is capable of, configured to, or operable to support components for communicating with a second serving cell based on performing an LTM procedure, wherein the second serving cell includes candidate cells from one or more candidate cells.

[0118] In some examples, to support the detection of trigger events for beam reporting, triggering component 630 is capable of, configured to, or operable to support the detection of one or more signal strengths associated with a set of multiple beams that are below a threshold. In some examples, one or more signal strengths are associated with a serving cell or at least one candidate cell from one or more candidate cells.

[0119] In some examples, to support the detection of trigger events for beam reporting, triggering component 630 is capable of, configured to, or operable to support components for detecting signal strengths associated with one or more second beams exceeding a threshold. In some examples, the threshold is associated with the signal strength of a subset of one or more second beams. In some examples, the threshold is associated with an offset from the signal strength of a subset of one or more first beams.

[0120] In some examples, to support the detection of trigger events for beam reporting, trigger component 630 is capable of, configured to, or operable to support components for detecting a decrease in signal strength associated with one or more first beams, the trigger event being based on a combination of a signal strength associated with one or more second beams exceeding a threshold and a decrease in signal strength associated with one or more first beams.

[0121] In some examples, to support the detection of trigger events for beam reporting, triggering component 630 is capable of, configured to, or operable to support components for detecting changes in relative signal strength associated with at least two of the one or more second beams, wherein the at least two second beams are each in the same candidate cell in one or more candidate cells, or wherein the at least two second beams are in one or more candidate cells.

[0122] In some examples, to support the detection of trigger events for beam reports, triggering component 630 is capable of, configured to, or operable to support components for detecting changes associated with the ranking of one or more candidate cells, the ranking being based on a corresponding signal quality metric for the one or more candidate cells, the corresponding signal quality metric being based on the corresponding signal strength of a set of multiple beams.

[0123] In some examples, the beam report indicates the number of cells whose information is included in the beam report, the number of reference signals whose information is included in the beam report, or any combination thereof.

[0124] In some examples, the beam report indicates, for each cell whose information is included in the beam report, the corresponding cell identifier, the corresponding number of reference signals, the corresponding reference signal index of each reference signal included in the corresponding number of reference signals, the corresponding reference signal metric of each reference signal included in the corresponding number of reference signals, or any combination thereof.

[0125] In some examples, beam reporting includes a first value associated with a first reference signal metric and a second value associated with a second reference signal metric. In some examples, the second value is relative to the first value.

[0126] In some examples, to support the transmission of beam reports, the first report portion component 650 is capable of, configured to, or operable to support components for transmitting a first portion of the beam report, which indicates the number of reference signals whose information is included in the beam report, the number of cells whose information is included in the beam report, or both. In some examples, to support the transmission of beam reports, the second report portion component 655 is capable of, configured to, or operable to support components for transmitting a second portion of the beam report, which indicates the corresponding reference signal index, corresponding reference signal metric, or both for each reference signal whose information is included in the beam report, wherein the transmission of the first and second portions is based on the beam report being transmitted via one or more uplink control information messages.

[0127] In some examples, the uplink allocation component 660 is capable of, configured to, or operable to support components for receiving control signaling that allocates one or more uplink transmission resources for the UE to transmit beam reports. In some examples, the beam report request component 665 is capable of, configured to, or operable to support components for transmitting a request to transmit beam reports, wherein the control signaling that allocates one or more uplink transmission resources for the UE to transmit beam reports is received on a request basis.

[0128] Figure 7 A diagram of a system 700 including device 705 supporting event-driven beam reporting for LTM, according to one or more aspects of this disclosure, is shown. Device 705 may be an example of device 405, device 505, or UE 115 as described herein, or may include components thereof. Device 705 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof). Device 705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 720, an input / output (I / O) controller (e.g., I / O controller 710), a transceiver 715, one or more antennas 725, at least one memory 730, code 735, and at least one processor 740. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 745).

[0129] I / O controller 710 manages the input and output signals of device 705. I / O controller 710 can also manage peripheral devices not integrated into device 705. In some cases, I / O controller 710 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 710 may utilize an operating system such as iOS. ®ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 710 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 710 may be implemented as part of one or more processors, such as at least one processor 740. In some cases, a user may interact with the device 705 via the I / O controller 710 or via hardware components controlled by the I / O controller 710.

[0130] In some cases, device 705 may include a single antenna. However, in other cases, device 705 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 715 may communicate bidirectionally via one or more antennas 725 using a wired or wireless link as described herein. For example, transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 715 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 725 for transmission; and demodulating packets received from one or more antennas 725. Transceiver 715, or transceiver 715 and one or more antennas 725, may be an example of transmitter 415, transmitter 515, receiver 410, receiver 510, or any combination thereof or components thereof as described herein.

[0131] At least one memory 730 may include random access memory (RAM) and read-only memory (ROM). At least one memory 730 may store computer-readable code, computer-executable code, or processor-executable code, such as code 735. Code 735 may include instructions that, when executed by at least one processor 740, cause device 705 to perform the various functions described herein. Code 735 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 735 may not be directly executable by at least one processor 740, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, at least one memory 730 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0132] At least one processor 740 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 740 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 740. At least one processor 740 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 730) to cause device 705 to perform various functions (e.g., functions or tasks supporting event-driven beam reporting for LTM). For example, device 705 or components of device 705 may include at least one processor 740 and at least one memory 730 coupled to or coupled to at least one processor 740, the at least one processor 740 and the at least one memory 730 being configured to perform the various functions described herein. In some examples, at least one processor 740 may include multiple processors, and at least one memory 730 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 740 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 740) and memory circuitry (which may include at least one memory 730)) or components that receive or obtain input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 740 or a processing system including at least one processor 740 may be configured, capable of being configured, or operable to cause device 705 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code 735 (e.g., processor-executable code) stored in at least one memory 730 or otherwise executing the code.

[0133] The communication manager 720 may support wireless communication according to examples disclosed herein. For example, the communication manager 720 may be capable of, configured to, or operable to support components for monitoring the signal strength of a set of multiple beams, wherein the set of multiple beams includes one or more first beams within the serving cell for the UE and one or more second beams within one or more candidate cells associated with an LTM procedure for the UE. The communication manager 720 may be capable of, configured to, or operable to support components for detecting trigger events for beam reports associated with an LTM procedure for the UE, wherein the trigger event is associated with a change in the signal strength of one or more beams from the set of multiple beams. The communication manager 720 may be capable of, configured to, or operable to support components for transmitting beam reports based on the detection of a trigger event.

[0134] By including or configuring a communication manager 720 according to an example as described herein, device 705 can support technologies for cell mobility via L1 and / or L2 signaling, reduced latency, improved user experience associated with reduced processing, more efficient use of communication resources, and improved coordination between devices, etc.

[0135] In some examples, the communication manager 720 may be configured to use or otherwise coordinate with the transceiver 715, one or more antennas 725, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). For example, the communication manager 720 may be configured to receive or transmit messages or other signaling described herein via the transceiver 715. Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or performed by at least one processor 740, at least one memory 730, code 735, or any combination thereof. For example, code 735 may include instructions that can be executed by at least one processor 740 to cause the device 705 to perform various aspects of event-driven beam reporting for LTM as described herein, or at least one processor 740 and at least one memory 730 may be otherwise configured to perform or support such operations individually or jointly.

[0136] Figure 8A block diagram 800 illustrates a device 805 supporting event-driven beam reporting for LTM according to one or more aspects of this disclosure. Device 805 may be an example of aspects of network entity 105 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805, or one or more components of device 805 (e.g., receiver 810, transmitter 815, communication manager 820), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0137] Receiver 810 may provide components for acquiring (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 805. In some examples, receiver 810 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 810 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0138] Transmitter 815 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 805. For example, transmitter 815 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 815 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 815 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 815 and receiver 810 may be co-located in a transceiver, which may include or be coupled to a modem.

[0139] The communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be examples of components used to perform various aspects of event-driven beam reporting for LTM as described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0140] In some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0141] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor (e.g., referred to as processor executable code). If implemented in code executed by at least one processor, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, to support components for performing the functions described herein).

[0142] In some examples, the communication manager 820 may be configured to use or otherwise cooperate with the receiver 810, transmitter 815, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0143] The communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for obtaining beam reports from a UE, wherein the beam reports are associated with an LTM procedure for the UE and are based on triggering events associated with changes in the signal strength of one or more beams from a set of multiple beams, including one or more first beams in the serving cell for the UE and one or more second beams in one or more candidate cells associated with the LTM procedure for the UE. The communication manager 820 may be capable of, configured to, or operable to support components for adjusting one or more parameters associated with one or more beams based on the beam reports.

[0144] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., at least one processor that controls or otherwise couples to receiver 810, transmitter 815, communication manager 820, or a combination thereof) can, for example, support techniques for reducing processing and utilizing communication resources more efficiently by supporting event-triggered beam reporting for L1 / L2 mobility.

[0145] Figure 9 A block diagram 900 illustrates a device 905 supporting event-driven beam reporting for LTM according to one or more aspects of this disclosure. Device 905 may be an example of aspects of device 805 or network entity 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905 or one or more components of device 905 (e.g., receiver 910, transmitter 915, communication manager 920) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0146] Receiver 910 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 905. In some examples, receiver 910 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 910 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0147] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 905. For example, transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 915 and receiver 910 may be co-located in a transceiver, which may include or be coupled to a modem.

[0148] Device 905 or its various components may be examples of parts used to perform various aspects of event-driven beam reporting for LTM as described herein. For example, communication manager 920 may include beam reporting component 925, parameter adjustment component 930, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use or otherwise cooperate with receiver 910, transmitter 915, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or be integrated in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0149] The communication manager 920 may support wireless communication according to examples disclosed herein. The beam reporting component 925 is capable of, configured to, or operable to support components for obtaining beam reports from the UE, wherein the beam reports are associated with an LTM procedure for the UE and are based on triggering events associated with changes in the signal strength of one or more beams from a set of multiple beams, including one or more first beams in the serving cell for the UE and one or more second beams in one or more candidate cells associated with the LTM procedure for the UE. The parameter adjustment component 930 is capable of, configured to, or operable to support components for adjusting one or more parameters associated with one or more beams based on the beam reports.

[0150] Figure 10A block diagram 1000 is shown of a communication manager 1020 supporting event-driven beam reporting for LTM according to one or more aspects of this disclosure. The communication manager 1020 may be an example of a communication manager 820, a communication manager 920, or aspects thereof as described herein. The communication manager 1020 or its various components may be examples of parts for performing various aspects of event-driven beam reporting for LTM as described herein. For example, the communication manager 1020 may include a beam reporting component 1025, a parameter adjustment component 1030, a candidate cell determination component 1035, a cell handover command component 1040, an update parameter component 1045, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses). Communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of the protocol stack, within a device, component, or virtualization component associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0151] The communication manager 1020 may support wireless communication according to examples disclosed herein. The beam reporting component 1025 is capable of, configured to, or operable to support components for obtaining beam reports from the UE, wherein the beam reports are associated with an LTM procedure for the UE and are based on triggering events associated with changes in the signal strength of one or more beams from a set of multiple beams, including one or more first beams in the serving cell for the UE and one or more second beams in one or more candidate cells associated with the LTM procedure for the UE. The parameter adjustment component 1030 is capable of, configured to, or operable to support components for adjusting one or more parameters associated with one or more beams based on beam reports.

[0152] In some examples, the candidate cell determination component 1035 is capable of, configured to, or operable to support components for determining, based on adjusting one or more parameters, that the signal strength of at least one second beam from one or more candidate cells is stronger than the signal strength of at least one first beam from one or more first beams in the serving cell. In some examples, the cell handover command component 1040 is capable of, configured to, or operable to support components for outputting, based on a determination, a control message instructing the UE to hand over to a second serving cell via an LTM procedure, wherein the second serving cell is associated with at least one second beam and includes candidate cells from one or more candidate cells.

[0153] In some examples, to support the adjustment of one or more parameters, the update parameter component 1045 can be, configured, or operated to support components for updating the order associated with a set of multiple beams, components for updating the order associated with one or more candidate cells, components for activating or deactivating the transmit configuration indication status associated with at least one beam from the set of multiple beams, or any combination thereof.

[0154] Figure 11 A diagram of a system 1100 including device 1105 supporting event-driven beamforming for LTM, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, or network entity 105 as described herein, or may include components thereof. Device 1105 may communicate with other network devices or network equipment, such as network entity 105, UE 115, or any combination thereof. Communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1105 may include components that support output and enable communication, such as a communication manager 1120, a transceiver 1110, one or more antennas 1115, at least one memory 1125, code 1130, and at least one processor 1135. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1140).

[0155] Transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, transceiver 1110 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1110 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1105 may include one or more antennas 1115 that are capable of transmitting or receiving wireless transmissions (e.g., concurrently). Transceiver 1110 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1115, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1115, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1110 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1115 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1115 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1110 may include one or more processors or one or more memory components or be configured to couple to said one or more processors or one or more memory components, said one or more processors or one or more memory components being operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1110, or transceiver 1110 and one or more antennas 1115, or transceiver 1110 and one or more antennas 1115 and one or more processors or one or more memory components (e.g., at least one processor 1135, at least one memory 1125, or both) may be included in a chip or chip assembly mounted in device 1105. In some examples, transceiver 1110 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0156] At least one memory 1125 may include RAM, ROM, or any combination thereof. At least one memory 1125 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1130. Code 1130 may include instructions that, when executed by one or more of the at least one processor 1135, cause the device 1105 to perform the various functions described herein. Code 1130 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1130 may not be directly executable by one of the at least one processor 1135, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1125 may include a BIOS, etc., which controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0157] At least one processor 1135 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1135 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1135. At least one processor 1135 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1125) to cause device 1105 to perform various functions (e.g., functions or tasks supporting event-driven beam reporting for LTM). For example, device 1105 or components thereof may include at least one processor 1135 and at least one memory 1125 coupled to one or more of the at least one processor 1135, the at least one processor 1135 and the at least one memory 1125 configured to perform the various functions described herein. The at least one processor 1135 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that may (e.g., by executing code 1130) host functions for performing the functions of device 1105. The at least one processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1105 (such as within one or more memories of at least one memory 1125). In some examples, the at least one processor 1135 may include multiple processors, and the at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1135 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1135) and memory circuitry (which may include at least one memory 1125)) or components that receive or obtain input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein.For example, at least one processor 1135 or a processing system including at least one processor 1135 may be configured, configured to, or operated to cause device 1105 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “configurable to,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1125 or otherwise.

[0158] In some examples, bus 1140 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1140 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1105, or communication performed between different components of device 1105 that are co-addressable or may be located in different locations (e.g., where device 1105 may refer to a system in which one or more of the following are located: communication manager 1120, transceiver 1110, at least one memory 1125, code 1130, and at least one processor 1135 may be located in one of the different components or partitioned between the different components).

[0159] In some examples, the communication manager 1120 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1120 can manage the transfer of data communication with client devices, such as one or more UEs 115. In some examples, the communication manager 1120 can manage communication with one or more other network entities 105 and may include a controller or scheduler for (e.g., cooperating with one or more other network devices) controlling communication with UE 115. In some examples, the communication manager 1120 may support the X2 interface in LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0160] The communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for obtaining beam reports from a UE, wherein the beam reports are associated with an LTM procedure for the UE and are based on triggering events associated with changes in the signal strength of one or more beams from a set of multiple beams, including one or more first beams in the serving cell for the UE and one or more second beams in one or more candidate cells associated with the LTM procedure for the UE. The communication manager 1120 may be capable of, configured to, or operable to support components for adjusting one or more parameters associated with one or more beams based on the beam reports.

[0161] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 can support technologies for cell mobility via L1 and / or L2 signaling, reduced latency, improved user experience associated with reduced processing, more efficient utilization of communication resources, improved coordination between devices, and so on.

[0162] In some examples, the communication manager 1120 may be configured to use or otherwise coordinate with the transceiver 1110, one or more antennas 1115 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1120 may be configured to receive or transmit messages or other signaling described herein via the transceiver 1110. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the transceiver 1110, one or more processors in at least one processor 1135, one or more memories in at least one memory 1125, code 1130, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1135, at least one memory 1125, code 1130, or any combination thereof). For example, code 1130 may include instructions that can be executed by one or more of at least one processor 1135 to cause device 1105 to perform various aspects of event-driven beam reporting for LTM as described herein, or at least one processor 1135 and at least one memory 1125 may be otherwise configured to perform or support such operations individually or jointly.

[0163] Figure 12 A flowchart illustrating a method 1200 for supporting event-driven beam reporting for LTM according to one or more aspects of this disclosure is shown. Operation of method 1200 may be implemented by a UE or its components as described herein. For example, operation of method 1200 may be performed by, as referenced... Figures 1 to 7 The UE 115 described herein performs the following: In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0164] At 1205, the method may include: monitoring the corresponding signal strength of a set of multiple beams, wherein the set of multiple beams includes one or more first beams within the serving cell for the UE and one or more second beams within one or more candidate cells associated with an LTM procedure for the UE. Operation of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1205 may be provided by reference to [reference needed]. Figure 6 The described signal monitoring component 625 performs this function. Additionally or alternatively, components for performing the operation of 1205 at UE 115 may include, for example, one or more antennas 725, transceiver 715, communication manager 720, one or more memories 730 (e.g., including code 735), one or more processors 740, one or more buses 745, or any combination thereof.

[0165] At 1210, the method may include: detecting a trigger event for a beam report associated with an LTM procedure for the UE, wherein the trigger event is associated with a change in the signal strength of one or more beams from a set of multiple beams. Operation of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1210 may be provided by reference to [reference needed]. Figure 6 The described triggering component 630 is used to perform the operation. Additionally or alternatively, the components used to perform the operation of 1210 at UE 115 may include, for example, one or more antennas 725, transceiver 715, communication manager 720, one or more memories 730 (e.g., including code 735), one or more processors 740, one or more buses 745, or any combination thereof.

[0166] At 1215, the method may include: sending a beam report based on the detection of a trigger event. The operation of 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1215 may be provided by reference to [reference needed]. Figure 6 The described beam reporting component 635 performs the operation. Additionally or alternatively, components for performing the operation of 1215 at UE 115 may include, for example, one or more antennas 725, transceiver 715, communication manager 720, one or more memories 730 (e.g., including code 735), one or more processors 740, one or more buses 745, or any combination thereof.

[0167] Figure 13 A flowchart illustrating a method 1300 for supporting event-driven beam reporting for LTM according to one or more aspects of this disclosure is shown. Operation of method 1300 may be implemented by a UE or its components as described herein. For example, operation of method 1300 may be performed by, as referenced... Figures 1 to 7The UE 115 described herein performs the following: In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0168] At 1305, the method may include: monitoring the corresponding signal strength of a set of multiple beams, wherein the set of multiple beams includes one or more first beams within the serving cell for the UE and one or more second beams within one or more candidate cells associated with an LTM procedure for the UE. Operation of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1305 may be provided by reference to [reference needed]. Figure 6 The described signal monitoring component 625 performs this function. Additionally or alternatively, components for performing the operation 1305 at UE 115 may include, for example, one or more antennas 725, transceiver 715, communication manager 720, one or more memories 730 (e.g., including code 735), one or more processors 740, one or more buses 745, or any combination thereof.

[0169] At 1310, the method may include: detecting a trigger event for a beam report associated with an LTM procedure for the UE, wherein the trigger event is associated with a change in the signal strength of one or more beams from a set of multiple beams. Operation of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1310 may be provided by reference to [reference needed]. Figure 6 The described triggering component 630 is used to perform this action. Additionally or alternatively, components for performing the operation of 1310 at UE 115 may include, for example, one or more antennas 725, transceiver 715, communication manager 720, one or more memories 730 (e.g., including code 735), one or more processors 740, one or more buses 745, or any combination thereof.

[0170] At 1315, the method may include: sending a beam report based on the detection of a trigger event. The operation of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1315 may be provided by reference to [reference needed]. Figure 6 The described beam reporting component 635 performs the operation. Additionally or alternatively, components for performing the operation of 1315 at UE 115 may include, for example, one or more antennas 725, transceiver 715, communication manager 720, one or more memories 730 (e.g., including code 735), one or more processors 740, one or more buses 745, or any combination thereof.

[0171] At 1320, the method may include performing an LTM procedure based on a transmitted beam report. The operation of 1320 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1320 may be provided by reference to [reference needed]. Figure 6 The LTM component 640 described herein performs the operation. Additionally or alternatively, components for performing the operation of 1320 at UE 115 may include, for example, one or more antennas 725, transceiver 715, communication manager 720, one or more memories 730 (e.g., including code 735), one or more processors 740, one or more buses 745, or any combination thereof.

[0172] At 1325, the method may include: communicating with a second serving cell based on performing an LTM procedure, wherein the second serving cell includes candidate cells from one or more candidate cells. The operation of 1325 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1325 may be derived from references... Figure 6 The described cell handover component 645 performs the operation. Additionally or alternatively, components for performing the operation 1325 at UE 115 may include, for example, one or more antennas 725, transceiver 715, communication manager 720, one or more memories 730 (e.g., including code 735), one or more processors 740, one or more buses 745, or any combination thereof.

[0173] Figure 14 A flowchart illustrating a method 1400 for supporting event-driven beam reporting for LTM according to one or more aspects of this disclosure is shown. Operation of method 1400 may be implemented by a network entity or its components as described herein. For example, operation of method 1400 may be implemented by, as referenced... Figures 1 to 3 as well as Figures 8 to 11 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0174] At 1405, the method may include: obtaining a beam report from the UE, wherein the beam report is associated with an LTM procedure for the UE and is based on a triggering event associated with a change in the signal strength of one or more beams from a set of multiple beams, the set of multiple beams including one or more first beams in the serving cell for the UE and one or more second beams in one or more candidate cells associated with the LTM procedure for the UE. Operation of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1405 may be provided by reference to [reference needed]. Figure 10The described beam reporting component 1025 performs this function. Additionally or alternatively, components for performing the operation of 1405 at network entity 105 may include, for example, one or more antennas 1115, transceiver 1110, communication manager 1120, one or more memories 1125 (e.g., including code 1130), one or more processors 1135, one or more buses 1140, or any combination thereof.

[0175] At 1410, the method may include: adjusting one or more parameters associated with one or more beams based on beam reports. The operation of 1410 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1410 may be provided by reference to... Figure 10 The described parameter adjustment component 1030 performs the operation. Additionally or alternatively, components for performing the operation of 1410 at network entity 105 may include, for example, one or more antennas 1115, transceiver 1110, communication manager 1120, one or more memories 1125 (e.g., including code 1130), one or more processors 1135, one or more buses 1140, or any combination thereof.

[0176] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at a UE, the method comprising: monitoring the corresponding signal strengths of a plurality of beams, wherein the plurality of beams includes one or more first beams in a serving cell for the UE and one or more second beams in one or more candidate cells associated with an LTM procedure for the UE; detecting a trigger event for a beam report associated with the LTM procedure for the UE, wherein the trigger event is associated with a change in signal strength from one or more of the plurality of beams; and transmitting the beam report at least in part based on the detection of the trigger event.

[0177] Aspect 2: According to the method of aspect 1, the method further includes: performing the LTM procedure at least in part based on sending the beam report; and communicating with a second serving cell at least in part based on performing the LTM procedure, wherein the second serving cell includes a candidate cell from the one or more candidate cells.

[0178] Aspect 3: The method according to any one of Aspects 1 to 2, wherein detecting the triggering event reported for the beam comprises: detecting that one or more signal strengths associated with the plurality of beams are below a threshold.

[0179] Aspect 4: According to the method of aspect 3, wherein the one or more signal strengths are associated with the serving cell or at least one of the one or more candidate cells.

[0180] Aspect 5: The method according to any one of Aspects 1 to 4, wherein detecting the triggering event reported for the beam comprises: detecting that the signal strength associated with the one or more second beams exceeds a threshold.

[0181] Aspect 6: According to the method of aspect 5, wherein the threshold is associated with the signal strength of a subset of the one or more second beams.

[0182] Aspect 7: The method according to any one of Aspects 5 to 6, wherein the threshold is associated with a shift in signal strength relative to a subset of the one or more first beams.

[0183] Aspect 8: The method according to any one of Aspects 5 to 7, wherein detecting the triggering event reported for the beam further comprises: detecting a decrease in signal strength associated with the one or more first beams, the triggering event being based at least in part on a combination of the signal strength associated with the one or more second beams exceeding the threshold and the decrease in signal strength associated with the one or more first beams.

[0184] Aspect 9: The method according to any one of Aspects 1 to 8, wherein detecting the triggering event reported for the beam comprises: detecting a change in relative signal strength associated with at least two of the one or more second beams, wherein the at least two second beams are each in the same candidate cell in the one or more candidate cells, or wherein the at least two second beams are in the one or more candidate cells.

[0185] Aspect 10: The method according to any one of Aspects 1 to 9, wherein detecting the triggering event for the beam report comprises: detecting a change associated with the ranking of the one or more candidate cells, the ranking being at least partially based on a corresponding signal quality metric for the one or more candidate cells, the corresponding signal quality metric being at least partially based on the corresponding signal strength of the plurality of beams.

[0186] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the beam report indicates the number of cells whose information is included in the beam report, the number of reference signals whose information is included in the beam report, or any combination thereof.

[0187] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the beam report indicates, for each cell whose information is included in the beam report, a corresponding cell identifier, a corresponding number of reference signals, a corresponding reference signal index for each reference signal included in the corresponding number of reference signals, a corresponding reference signal metric for each reference signal included in the corresponding number of reference signals, or any combination thereof.

[0188] Aspect 13: According to the method of aspect 12, the beam report includes a first value associated with a first reference signal metric and a second value associated with a second reference signal metric, and the second value is relative to the first value.

[0189] Aspect 14: The method according to any one of Aspects 1 to 13, wherein transmitting the beam report comprises: transmitting a first portion of the beam report, the first portion indicating the number of reference signals whose information is included in the beam report, the number of cells whose information is included in the beam report, or both; and transmitting a second portion of the beam report, the second portion indicating a corresponding reference signal index, a corresponding reference signal metric, or both, for each reference signal whose information is included in the beam report, wherein transmitting the first portion and the second portion is at least in part based on the beam report being transmitted via one or more UCI messages.

[0190] Aspect 15: The method according to any one of Aspects 1 to 14, the method further comprising: receiving control signaling, the control signaling allocating one or more uplink transmission resources for the UE to transmit the beam report.

[0191] Aspect 16: The method according to aspect 15, the method further comprising: sending a request to send the beam report, wherein the control signaling for allocating the one or more uplink transmission resources for the UE to send the beam report is received at least in part based on the request.

[0192] Aspect 17: A method for wireless communication at a network entity, the method comprising: obtaining a beam report from a UE, wherein the beam report is associated with an LTM procedure for the UE and is based at least in part on a triggering event associated with a change in signal strength from one or more of a plurality of beams, the plurality of beams including one or more first beams in a serving cell for the UE and one or more second beams in one or more candidate cells associated with the LTM procedure for the UE; and adjusting one or more parameters associated with the one or more beams based at least in part on the beam report.

[0193] Aspect 18: The method according to aspect 17, the method further comprising: determining, at least in part, based on adjusting the one or more parameters, that the signal strength of at least one second beam from the one or more candidate cells is stronger than the signal strength of at least one first beam from the one or more first beams in the serving cell; and at least in part based on the determination, outputting a control message instructing the UE to hand over to a second serving cell via the LTM procedure, wherein the second serving cell is associated with the at least one second beam and includes candidate cells from the one or more candidate cells.

[0194] Aspect 19: The method according to any one of Aspects 17 to 18, wherein adjusting the one or more parameters comprises: updating the ordering associated with the plurality of beams, updating the ordering associated with the one or more candidate cells, activating or deactivating the TCI state associated with at least one of the plurality of beams, or any combination thereof.

[0195] Aspect 20: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; a transceiver; and one or more processors coupled to the one or more memories and the transceiver, the one or more processors being operable individually or jointly to execute the code to cause the UE to perform a method according to any one of Aspects 1 to 16.

[0196] Aspect 21: A UE for wireless communication, the UE including at least one component for performing the method according to any one of aspects 1 to 16.

[0197] Aspect 22: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 16.

[0198] Aspect 23: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of Aspects 17 to 19.

[0199] Aspect 24: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 17 to 19.

[0200] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 17 to 19.

[0201] It should be noted that the methods described herein describe possible specific implementations. Operations and steps may be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods may be combined.

[0202] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0203] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0204] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, graphics processing unit (GPU), neural processing unit (NPU), FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor can be performed by multiple processors capable of performing the described function or operation individually or jointly.

[0205] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0206] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0207] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0208] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0209] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0210] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate between similar components. If only the first reference numeral is used in the description, the description applies to any of the similar components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0211] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some of the drawings, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0212] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; transceiver; and One or more processors, coupled to one or more memories and the transceiver, wherein the one or more processors are capable of operating individually or jointly to execute the code to enable the UE: Monitor the corresponding signal strength of multiple beams, wherein the multiple beams include one or more first beams in the serving cell for the UE and one or more second beams in one or more candidate cells associated with a lower-layer triggered mobility procedure for the UE; Detect trigger events for beam reports associated with mobility procedures triggered by the lower layer for the UE, wherein the trigger events are associated with changes in signal strength from one or more of the plurality of beams; as well as The beam report is transmitted via the transceiver based at least in part on the detection of the triggering event.

2. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The lower-layer triggered mobility procedure is performed at least in part based on sending the beam report; and The communication with the second serving cell is based at least in part on the execution of the lower-layer triggered mobility process, wherein the second serving cell includes candidate cells from the one or more candidate cells.

3. The UE of claim 1, wherein, in order to detect the triggering event for the beam report, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The strength of one or more signals associated with the plurality of beams is detected to be below a threshold.

4. The UE of claim 3, wherein the one or more signal strengths are associated with the serving cell or at least one of the one or more candidate cells.

5. The UE of claim 1, wherein, in order to detect the triggering event for the beam report, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The signal strength associated with the one or more second beams is detected to exceed a threshold.

6. The UE of claim 5, wherein the threshold is associated with the signal strength of a subset of the one or more second beams.

7. The UE of claim 5, wherein the threshold is associated with an offset of signal strength relative to a subset of the one or more first beams.

8. The UE of claim 5, wherein, in order to detect the triggering event for the beam report, the one or more processors are capable of further operating individually or jointly to execute the code to cause the UE to: The triggering event is based at least in part on a combination of the signal strength associated with the one or more second beams exceeding the threshold and the signal strength associated with the one or more first beams decreasing.

9. The UE of claim 1, wherein, in order to detect the triggering event for the beam report, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: Detect changes in relative signal strength associated with at least two of the one or more second beams.

10. The UE of claim 1, wherein, in order to detect the triggering event for the beam report, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: Detect changes associated with the ranking of the one or more candidate cells, the ranking being based at least in part on a corresponding signal quality metric for the one or more candidate cells, the corresponding signal quality metric being based at least in part on the corresponding signal strength of the plurality of beams.

11. The UE of claim 1, wherein the beam report indicates the number of cells whose information is included in the beam report, the number of reference signals whose information is included in the beam report, or any combination thereof.

12. The UE of claim 1, wherein the beam report indicates, for each cell whose information is included in the beam report, a corresponding cell identifier, a corresponding number of reference signals, a corresponding reference signal index for each reference signal included in the corresponding number of reference signals, a corresponding reference signal metric for each reference signal included in the corresponding number of reference signals, or any combination thereof.

13. The UE according to claim 12, wherein: The beam report includes a first value associated with a first reference signal metric and a second value associated with a second reference signal metric, wherein the second value is relative to the first value.

14. The UE of claim 1, wherein, in order to transmit the beam report, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: Sending a first portion of the beam report, the first portion indicating the number of reference signals whose information is included in the beam report, the number of cells whose information is included in the beam report, or both; and Send a second portion of the beam report, the second portion indicating that its information is included in the corresponding reference signal index, corresponding reference signal metric, or both for each reference signal in the beam report, wherein sending the first portion and the second portion is at least in part based on the beam report being sent via one or more uplink control information messages.

15. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The UE receives control signaling that allocates one or more uplink transmission resources for transmitting the beam report.

16. The UE of claim 15, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Sending a request to send the beam report, wherein the control signaling for allocating the one or more uplink transmission resources for the UE to send the beam report is received at least in part based on the request.

17. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: A beam report is obtained from a user equipment (UE), wherein the beam report is associated with a lower-layer triggered mobility procedure for the UE and is based at least in part on a triggering event associated with a change in signal strength from one or more of a plurality of beams, including one or more first beams in the serving cell for the UE and one or more second beams in one or more candidate cells associated with the lower-layer triggered mobility procedure for the UE. as well as One or more parameters associated with the one or more beams are adjusted, at least in part, based on the beam reports.

18. The network entity of claim 17, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: The signal strength of at least one second beam from one or more second beams within one or more candidate cells is determined to be stronger than the signal strength of at least one first beam from one or more first beams within the serving cell, at least in part, based on adjustments to one or more parameters; and The control message is output at least in part based on the determination, instructing the UE to switch to a second serving cell via a mobility procedure triggered by the lower layer, wherein the second serving cell is associated with the at least one second beam and includes candidate cells from the one or more candidate cells.

19. The network entity of claim 17, wherein, in order to adjust the one or more parameters, the one or more processors are capable of operating individually or jointly to execute the code to cause the network entity to: Update the ordering associated with the plurality of beams, update the ordering associated with the one or more candidate cells, activate or deactivate the transmit configuration indication state associated with at least one of the plurality of beams, or any combination thereof.

20. A method for conducting wireless communication at a user equipment (UE), the method comprising: Monitor the corresponding signal strength of multiple beams, wherein the multiple beams include one or more first beams in the serving cell for the UE and one or more second beams in one or more candidate cells associated with a lower-layer triggered mobility procedure for the UE; Detect trigger events for beam reports associated with mobility procedures triggered by the lower layer for the UE, wherein the trigger events are associated with changes in signal strength from one or more of the plurality of beams; as well as The beam report is sent based at least in part on the detection of the triggering event.

Images