User equipment (UE) and network actions based on layer 3 (L3) cell and beam prediction

Abstract

Methods, systems, and devices are described for wireless communication. A user equipment (UE) can support predicting candidate cells and / or beams associated with candidate cells using artificial intelligence (AI) / machine learning (ML) models / functionality. For example, the UE can transmit, to a serving network entity, an indication of predicted candidate cells / beams. The indication can also include a request for one or more reference signal configurations associated with the predicted candidate cells. Upon receiving the request from the UE, the network entity can forward the request to one or more candidate cells (e.g., one or more network entities associated with the one or more candidate cells), which can in turn provide the requested reference signal configurations. The serving network entity can provide the requested reference signal configurations to the UE, and as a result, the UE can provide one or more layer 3 measurements based on the reference signal configurations.

Description

Cross-referencing

[0001] This patent application claims priority to U.S. Patent Application No. 19 / 093,048, filed March 27, 2025, entitled “USER EQUIPMENT (UE) AND NETWORK ACTIONS BASED ON LAYER 3 (L3) CELL AND BEAM PREDICTIONS”, and U.S. Provisional Patent Application No. 63 / 572,792, filed April 1, 2024, entitled “USER EQUIPMENT (UE) AND NETWORK ACTIONS BASED ON LAYER 3 (L3) CELL AND BEAM PREDICTIONS”, each of which is assigned to the assignee of this application and each of which is expressly incorporated herein by reference. Background Technology

[0002] The following discussion relates to wireless communications, including cell management and / or beam prediction.

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. 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 for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses for supporting Layer 3 (L3) cell and beam prediction and corresponding actions performed by UEs and network entities.

[0005] A method for wireless communication by a UE is described. The method may include: sending a request message to a network entity associated with one or more serving cells, the request message indicating one or more candidate cells predicted by the UE based on one or more artificial intelligence (AI) based functionalities or models, wherein the request message indicates a request for configuration of one or more reference signals corresponding to the one or more candidate cells; receiving a first control message from the network entity, the first control message indicating a reference signal configuration of one or more reference signals associated with one or more beams, the one or more beams being associated with the one or more candidate cells predicted by the UE; and sending a measurement report indicating a set of measurements of one or more L3 beams, wherein the set of measurements of one or more L3 beams is based on the reference signal configuration of one or more reference signals received via the one or more beams.

[0006] A UE for wireless communication is described. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the UE to: send a request message to a network entity associated with one or more serving cells, the request message indicating one or more candidate cells predicted by the UE based on one or more AI-based functionalities or models, wherein the request message indicates a request for one or more reference signal configurations corresponding to the one or more candidate cells; receive a first control message from the network entity, the first control message indicating a reference signal configuration of one or more reference signals associated with one or more beams, the one or more beams being associated with the one or more candidate cells predicted by the UE; and send a measurement report indicating a set of one or more L3 beam measurements, wherein the set of one or more L3 beam measurements is based on the reference signal configuration of one or more reference signals received via the one or more beams.

[0007] Another UE for wireless communication is described. The UE may include: components for sending a request message to a network entity associated with one or more serving cells, the request message indicating one or more candidate cells predicted by the UE based on one or more AI-based functionalities or models, wherein the request message indicates a request for one or more reference signal configurations corresponding to the one or more candidate cells; components for receiving a first control message from the network entity, the first control message indicating a reference signal configuration of one or more reference signals associated with one or more beams, the one or more beams being associated with the one or more candidate cells predicted by the UE; and components for sending a measurement report indicating a set of one or more L3 beam measurements, wherein the set of one or more L3 beam measurements is based on a reference signal configuration of one or more reference signals received via the one or more beams.

[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: send a request message to a network entity associated with one or more serving cells, the request message indicating one or more candidate cells predicted by a UE based on one or more AI-based functionalities or models, wherein the request message indicates a request for one or more reference signal configurations corresponding to the one or more candidate cells; receive a first control message from the network entity, the first control message indicating a reference signal configuration of one or more reference signals associated with one or more beams, the one or more beams being associated with the one or more candidate cells predicted by the UE; and send a measurement report indicating a set of measurements of one or more L3 beams, wherein the set of one or more L3 beam measurements is based on the reference signal configuration of one or more reference signals received via the one or more beams.

[0009] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for: determining a set of beams that can be associated with one or more candidate cells predicted by the UE, wherein the set of beams can be predicted by the UE at least in part based on one or more AI-based functionalities or models; and sending a request to activate the set of beams, a request to configure measurements for the set of beams, or both, via a request message, wherein the set of beams includes one or more beams associated with one or more candidate cells, and wherein a set of one or more L3 beam measurements can be based on the request message.

[0010] The methods described herein, some examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for receiving a second control message from a network entity, the second control message indicating a request to send a request to activate a beam set, a request to configure measurements for the beam set, or both, wherein the request message may be sent according to the request configuration.

[0011] The methods described herein, some examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for receiving a third control message from a network entity indicating that a beam set may have been activated, wherein the third control message may be received in response to a request message, and wherein a set of one or more L3 beam measurements may be based on the activation of the beam set.

[0012] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, request messages may be sent via radio resource control signaling.

[0013] In the methods described herein, and in some examples of UEs and non-transitory computer-readable media, the request message may be sent via a Media Access Control (MAC) control element (MAC-CE).

[0014] In the methods described herein, and in some examples of UEs and non-transitory computer-readable media, the request message may be sent via uplink control information.

[0015] A method for wireless communication performed by a first network entity is described. The method may include: outputting a first request message including a request for a reference signal configuration of one or more reference signals associated with one or more beams of at least one of one or more candidate cells; outputting a message indicating the reference signal configuration of the one or more reference signals based on the first request message; and obtaining a measurement report indicating a set of L3 beam measurements, wherein the set of L3 beam measurements is based on the reference signal configuration of the one or more reference signals.

[0016] A first network entity for wireless communication is described. The first network entity may include: one or more memories; and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the first network entity to: output a first request message including a request for a reference signal configuration of one or more reference signals associated with one or more beams of at least one of the candidate cells; output a message indicating the reference signal configuration of the one or more reference signals based on the first request message; and obtain a measurement report indicating a set of L3 beam measurements, wherein the set of L3 beam measurements is based on the reference signal configuration of the one or more reference signals.

[0017] Another first network entity for wireless communication is described. The first network entity may include: components for outputting a first request message including a request for a reference signal configuration of one or more reference signals associated with one or more beams of at least one of the candidate cells; components for outputting a message indicating the reference signal configuration of the one or more reference signals based on the first request message; and components for obtaining a measurement report indicating a set of L3 beam measurements, wherein the set of L3 beam measurements is based on the reference signal configuration of the one or more reference signals.

[0018] 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: output a first request message including a request for a reference signal configuration of one or more reference signals associated with one or more beams of at least one of one or more candidate cells; output a message indicating the reference signal configuration of the one or more reference signals based on the first request message; and obtain a measurement report indicating a set of L3 beam measurements, wherein the set of L3 beam measurements is based on the reference signal configuration of the one or more reference signals.

[0019] The methods described herein, examples of the first network entity, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for obtaining a second request message that indicates one or more candidate cells, wherein the second request message indicates a request for configuration of one or more reference signals corresponding to the one or more candidate cells, and wherein the first request message may be based on the second request message.

[0020] The methods described herein, examples of the first network entity, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for: obtaining a request via a second request message to activate a beam set that may be associated with one or more candidate cells, a request to configure measurements for the beam set, or both, wherein the beam set includes one or more beams associated with one or more candidate cells, and wherein the set of L3 beam measurements may be based on the second request message; and outputting a message indicating that the beam set may have been activated, wherein the set of L3 beam measurements may be based on the activation of the beam set.

[0021] In some examples of the methods described herein, the first network entity, and the non-transitory computer-readable medium, the first request message includes a handover command message.

[0022] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the first request message includes a signal associated with the F1 interface, a signal associated with the Xn interface, a signal associated with the NG interface, or any combination thereof.

[0023] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the first request message includes a cell group configuration message, or signaling associated with the F1 interface, or any combination thereof.

[0024] In some examples of the methods described herein, the first network entity, and non-transitory computer-readable media, the message includes a handover preparation message.

[0025] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the message includes signaling associated with the Xn interface, signaling associated with the NG interface, or any combination thereof.

[0026] In some examples of the methods described herein, the first network entity, and non-transitory computer-readable media, the message includes a cell group configuration message, or signaling associated with the F1 interface, or any combination thereof. Attached Figure Description

[0027] Figure 1 Examples of wireless communication systems supporting UE and network actions based on L3 cell and beam prediction, according to one or more aspects of this disclosure, are shown.

[0028] Figure 2 An example of a network architecture supporting UE and network actions based on L3 cell and beam prediction, according to one or more aspects of this disclosure, is shown.

[0029] Figure 3Examples of wireless communication systems supporting UE and network actions based on L3 cell and beam prediction, according to one or more aspects of this disclosure, are shown.

[0030] Figure 4 Examples of machine learning processes supporting L3 cell and beam prediction of UE and network actions are shown, according to one or more aspects of this disclosure.

[0031] Figure 5 An example of a process flow supporting UE and network actions based on L3 cell and beam prediction, according to one or more aspects of this disclosure, is shown.

[0032] Figure 6 and Figure 7 A block diagram is shown of an apparatus that supports UE and network actions based on L3 cell and beam prediction, according to one or more aspects of this disclosure.

[0033] Figure 8 A block diagram is shown of a communication manager that supports UE and network actions based on L3 cell and beam prediction, according to one or more aspects of this disclosure.

[0034] Figure 9 A diagram is shown of a system including devices supporting UE and network actions based on L3 cell and beam prediction, according to one or more aspects of this disclosure.

[0035] Figure 10 and Figure 11 A block diagram is shown of an apparatus that supports UE and network actions based on L3 cell and beam prediction, according to one or more aspects of this disclosure.

[0036] Figure 12 A block diagram is shown of a communication manager that supports UE and network actions based on L3 cell and beam prediction, according to one or more aspects of this disclosure.

[0037] Figure 13 A diagram is shown of a system including devices supporting UE and network actions based on L3 cell and beam prediction, according to one or more aspects of this disclosure.

[0038] Figure 14 and Figure 15 A flowchart illustrating a method for supporting UE and network actions based on L3 cell and beam prediction according to one or more aspects of this disclosure is shown. Detailed Implementation

[0039] In some wireless communication systems, user equipment (UE) can support models and / or functionalities based on artificial intelligence (AI) and / or machine learning (ML), such as those used for beam prediction. Such a UE can collect data measurements (e.g., Reference Signal Received Power (RSRP) measurement, Signal-to-Interference-plus-Noise Ratio (SINR) measurement, Channel Impulse Response (CIR) measurement, etc.) for one or more directional beams based on measurements of reference signals (e.g., Synchronous System Block (SSB), Channel State Information (CSI) Reference Signal (CSI-RS), or other reference signals). For example, the UE can measure directional beams transmitted / received via the SSB and / or signals received using directional beams transmitted / received via the CSI-RS. The UE can use measurements of a first set of beams of a network entity to train a given AI / ML model / functionality to predict measurements of a second set of future beams of the network entity. Furthermore, the trained AI / ML model / functionality can use measurements of a third set of beams to predict measurements of a fourth set of beams; this can be a process known as beam inference. AI / ML-based models and / or functionalities can refer to a process or processing framework that utilizes one or more AI / ML algorithms to perform a given task (such as predicting one or more outputs based on one or more inputs). For example, AI / ML-based models and / or functionalities can be employed to predict at least one outcome using one or more algorithms applied to a given input pattern. Thus, AI / ML-based models or functionalities can support pattern recognition and prediction generation using input data. In some cases, inference can refer to one or more processes of inputting data into a trained AI / ML model for prediction. The measurements of beams of network entities predicted or output from the AI / ML model (e.g., a first set of beams or a third set of beams, which may correspond to the same set of beams) can be referred to as set A beams, and the measurements of beams of network entities input into the AI / ML model (e.g., a second set of beams or a fourth set of beams, which may correspond to the same set of beams) can be referred to as set B beams. In some examples, predictive measurements may include calculating the values ​​of the measurements of the beam sets without relying on the actual measurements performed by the UE against the beam sets.

[0040] The UE can use AI / ML models and / or functionality to determine which beam in set A is most likely to have the optimal Layer 1 (L1) RSRP (L1-RSRP) value. For example, the UE can pass input values ​​(e.g., beam measurements for set B) to an ML algorithm for processing. The ML algorithm can predict beam measurements (e.g., RSRP, SINR, or CIR) for set A based on measurements for set B. L1 beam measurements can refer to measurements of beams in the physical layer (e.g., L1). For example, an L1 beam measurement can be the RSRP, SINR, or CIR of one or more reference signals received via a given beam. L1 beam prediction can refer to the predicted L1 measurement value for a beam (e.g., set A) based on actual measurements of one or more beams (e.g., set B). L1 beam prediction can be performed for beams different from set B (e.g., spatial prediction) or for future measurements (e.g., temporal prediction). L1 beam measurements can be used to generate L3 beam and / or cell measurements by filtering L1 beam measurements. L3 beam measurements for a beam can refer to measurements of the beam at a network layer (e.g., L3) by filtering one or more L1 beam measurements for the beam, for example, to remove the effects of fast fading and / or help reduce short-term variations in the L1 beam measurements. Therefore, L3 beam measurements can provide a longer-term beam measurement view than L3 measurements, and L3 beam measurements can be used for radio resource management (RRM), such as triggering handover procedures.

[0041] To obtain L3 measurements, the network entity associated with the serving cell (e.g., serving network entity, serving gNB, serving central unit (CU), serving distributed unit (DU)) can provide the UE with one or more control messages (e.g., including measurement configuration, reference signal configuration) indicating the configuration (e.g., measurement configuration, reference signal configuration). measConfig Radio Resource Control (RRC) messages in the Information Element (IE). In some cases, the serving cell may correspond to or include a primary cell and one or more secondary cells configured for communication between the UE and network entities. Measurement configuration may indicate the measurements that the UE can perform (e.g., the measurement object). measObject This can include one or more measurements of one or more neighboring cells. The one or more neighboring cells may additionally or alternatively be referred to as one or more candidate cells, one or more target cells, etc. Therefore, measurements can be applied to intra-frequency, inter-frequency, and inter-RAT mobility, and the measurement configuration can also include a configuration of one or more measurement gaps. In some examples, this can be achieved via... RRCReconfiguration information, RRCResumeMessages, or any combination thereof, are used to signal measurement configuration. In some cases, one or more fields may be used to configure measurements for SSB, CSI-RS, or both, and may also indicate which measurement resource type to use to perform the measurement. In any case, the UE may receive from the serving cell an indication of one or more reference signals (e.g., the serving cell provides information on which / when to measure SSB / CSI-RS resources), as well as additional measurement parameters for deriving the measurements (e.g., L1 measurement, L3 measurement).

[0042] However, in some cases, network entities associated with the source cell can configure a relatively large number of reference signals for measurements (e.g., SSB / CSI-RS resources), which may lead to excessive power consumption by the UE. Furthermore, while predicting the SSB / CSI-RS resources and associated L1 / L3 measurements of neighboring cells can reduce the number of measurement targets, such predictions may be impractical because any prediction of when the UE's SSB / CSI-RS will be available for neighboring cells can be difficult (e.g., in the absence of measurement configurations for one or more neighboring cells). In addition, inaccurate measurement predictions can lead to relatively frequent handovers and may further result in increased lower-layer triggered mobility (LTM) failures, beamouts, and ping-pong effects. As an example, LTM (which can also be referred to as L1 / L2-based mobility) can be associated with changes in the serving cell via L1 / L2 signaling, where the configurations of other layers (e.g., upper layers) can remain unchanged. Therefore, LTM failure can refer to a failure in the L1 / L2-based mobility process, such as when one or more timers expire before the LTM process is completed, or when one or more links associated with the LTM process fail. That is, due to the relative complexity of such predictions, predicting the reference signal resources and / or measurements to be performed for one or more neighboring cells may be impractical.

[0043] As described herein, AI / ML-based technologies can be used to minimize the measurement objectives of a UE while enabling efficient handover and LTM procedures. For example, the described technologies can enable a UE to use AI / ML models / functionality to predict candidate cells and / or beams associated with one or more candidate cells, and the UE can send indications of the predicted candidate cells / beams to serving network entities (e.g., serving CU, serving DU). The indications from the UE can be included in a request message, which may also include a request for one or more reference signal configurations associated with the predicted candidate cells. Upon receiving the request from the UE, the serving CU / DU can forward the request to one or more candidate CU / DUs, which can then provide the requested reference signal configurations. The reference signal configurations may include, for example, signaling and indicating via RRC message transmission. ReferenceSignalConfig The measurement configuration of the field can indicate the configuration of reference signals associated with set A beams and / or set B beams. The network entity associated with the serving cell can provide the requested reference signal configuration to the UE via control messages such as RRC messages. Therefore, the UE can provide a measurement report including measurements of one or more L3 beams based on the reference signal configuration of the candidate cell.

[0044] By implementing techniques for managing L3 beam and / or cell measurements, the UE can measure one or more neighboring cells (e.g., candidate cells, target cells), thereby improving mobility-based processes. For example, because the UE can predict one or more beams and / or cells that can be used for mobility purposes (e.g., when the UE is moving), the number of measurements performed by the UE can be reduced when the UE sends a request for corresponding measurement configurations for neighboring cells and / or beams. That is, based on the UE's prediction of the cells / beams to be measured and subsequent requests to the network, the UE can receive measurement configurations for neighboring cell measurements (e.g., without utilizing a relatively large amount of reference signal resources for configuration). Thus, the UE can save power by performing measurements only on the predicted cells / beams (e.g., because the number of measurement targets can be reduced).

[0045] The aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated and described with reference to ML procedures, process flows, apparatus diagrams, system diagrams, and flowcharts relating to UE and network actions based on L3 cell and beam prediction.

[0046] Figure 1Examples of a wireless communication system 100 supporting UE and network actions based on L3 cell and beam prediction according to one or more aspects of this disclosure are shown. 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 an LTE network, an LTE-A network, an LTE-A Pro network, an NR network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not expressly mentioned herein.

[0047] 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).

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

[0049] As described herein, a node in 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.

[0050] 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. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be 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 can communicate with core network 130 via communication link 155.

[0051] One or more network entities or network equipment in network entity 105 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, eNodeB (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 eNodeB 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 that is physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0052] 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 among multiple network entities (e.g., network entity 105), such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration advocated by O-RAN), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: CU such as CU 160, DU such as DU 165, radio unit (RU) such as RU 170, RAN intelligent controller (RIC) such as RIC 175 (e.g., near real-time RIC (near RT RIC), non-real-time RIC (non-RT RIC)), service management and orchestration (SMO) system such as SMO system 180, or any combination thereof. RU 170 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)).

[0053] 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., RRC, Service 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 some 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, Media Access Control (MAC) layer) functionality and signaling, and may each be at least partially controlled by CU 160. Additionally or alternatively, a functional split of the protocol stack 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.

[0054] 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 IAB mobile terminals (IAB-MTs) 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.

[0055] For example, the access network (AN) or RAN may include an access node (e.g., an IAB donor), communication between IAB node 104 and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include one or more of CU 160, DU 165, and RU 170, in which case CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, CU 160 may communicate with core network 130 via an interface (which may be part of a backhaul link) and may communicate with other CUs (e.g., including CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be another part of a backhaul link).

[0056] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay for UE transmissions via other IAB nodes 104). Additionally or alternatively, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104, depending on the AN's relay chain or configuration. The IAB-MT entity of IAB node 104 can provide a Uu interface to the child IAB node (e.g., IAB node 104) to receive signaling from the parent IAB node (e.g., IAB node 104), and the DU interface (e.g., DU 165) can provide a Uu interface to the parent IAB node to send signaling notifications to the child IAB node or UE 115.

[0057] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, an IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. An IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to UE 115) via one or more DUs (e.g., DU 165). In other words, data can be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104 (e.g., other IAB nodes). Communication with IAB node 104 can be scheduled by the IAB donor or by DU 165 of IAB node 104.

[0058] 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).

[0059] As described herein, a node, which may be referred to as a node, network node, network entity, or wireless node, can be a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, and / or another suitable processing entity configured to perform any of the techniques described herein. For example, a network node can be a UE. As another example, a network node can be a base station. As yet another example, a first network node can be configured to communicate with a second or third network node. In one aspect of this example, the first network node can be a UE, the second network node can be a base station, and the third network node can be a UE. In another aspect of this example, the first network node can be a UE, the second network node can be a base station, and the third network node can be a base station. In still other aspects of this example, the first network node, the second network node, and the third network node can be different from these examples. Similarly, references to UE, base station, apparatus, device, computing system, etc., can include disclosures of UE, base station, apparatus, device, computing system, etc., as network nodes. For example, the disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., the disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example can be interpreted in reverse, but in a broad, open-ended manner. In the above example where the disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node can refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first or more components, a first processing entity, etc., configured to receive information; and the second network node can refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second or more components, a second processing entity, etc.

[0060] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network node.

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

[0062] The UE 115 described herein can communicate with various types of devices, such as the UE 115 which sometimes operates as a relay, as well as 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.

[0063] In some examples, UE 115 may support AI and / or ML models and / or functionalities, which UE 115 may use to perform various wireless communication procedures (e.g., CSI prediction, beam selection, or beam prediction, etc.). In this case, UE 115 may use one or more AI / ML models / functionalities to generate inference data. Additionally or alternatively, UE 115 may perform lifecycle management (LCM) operations (e.g., model or functionality selection, activation, deactivation, switching, and rollback, etc.) based on one or more AI / ML models / functionalities. In some aspects, LCM can be a model-based or function-based LCM procedure. As described herein, an AI functionality or AI model may be referred to as an ML functionality or ML model, and vice versa. That is, in some examples, the terms “AI” and “ML” are used interchangeably to refer to similar technologies, models, functionalities, algorithms, or any combination thereof. Similarly, the terms “model” and “functionality” are used interchangeably. In some examples, ML operations may be considered a subset of AI operations. In any case, aspects of the features described herein may be referred to as AI functionality, AI function, AI model, AI service, AI operation, etc., and such features may similarly apply to ML functionality, ML function, ML model, ML service, ML operation, or any combination thereof. Therefore, references to “ML” or “AI” may refer to ML, AI, or both, and the terms “AI” or “ML” should not be considered as limiting the scope of the claims or this disclosure.

[0064] 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 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured using 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 “send,” “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, CU 160, 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).

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

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

[0067] In light of the foregoing, unless otherwise specifically stated, it should be understood that, if used herein, the term "below 6 GHz" and the like can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that, if used herein, the term "millimeter wave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1 and / or FR5, or within the EHF band.

[0068] In some examples, such as in carrier aggregation configurations, a carrier may have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., of the same or different RATs) are used to anchor the connection.

[0069] The communication link 125 of the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. The carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0070] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a specific RAT (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0071] The signal waveform transmitted via a carrier can be composed of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or DFT-S-OFDM). In a system employing MCM, a resource element can 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 can be inversely related. The number of bits carried by each resource element can 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 can 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 can increase the data rate or data integrity used for communication with UE 115.

[0072] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, UE 115 can be configured to utilize multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and communication for UE 115 can be constrained to one or more active BWPs.

[0073] The time interval of network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, which can be, for example, a multiple of a basic time unit. The sampling period is seconds, where It can represent the supported subcarrier spacing, and The supported Discrete Fourier Transform (DFT) size can be represented. The time interval for organizing communication resources can be based on 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).

[0074] 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 also be 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.

[0075] 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)).

[0076] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, 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 UE115 (e.g., one or more UEs), or it may include a UE-specific search space set for transmitting control information to UE115.

[0077] Network entity 105 may provide communication coverage via one or more cells (such as 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.

[0078] 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 to macro cells, 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.

[0079] 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)).

[0080] 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).

[0081] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timing, and transmissions from different network entities (e.g., different network entities within network entity 105) can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities (e.g., different network entities within network entity 105) may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0082] Some UE 115 devices (such as MTC or IoT devices) can be relatively low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or instruments to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based service charging.

[0083] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115 may include: entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

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

[0085] 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 this 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.

[0086] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may signal information related to traffic conditions, signaling, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

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

[0088] 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).

[0089] The wireless communication system 100 can also operate in the Ultra High Frequency (SHF) band (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the Extremely High Frequency (EHF) band (e.g., 30 GHz to 300 GHz) (also known as the millimeter band) using the spectrum. In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the network entity 105 (e.g., base station 140, RU170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmission, EHF transmission may experience even greater attenuation and a shorter range. The techniques disclosed herein can be adopted for transmission across one or more different frequency bands, and the frequency band usage specified across these frequency bands may vary by country or regulatory authority.

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

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

[0092] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0093] 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).

[0094] 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 along 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.

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

[0096] 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 the pre-decoding weights of 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 that can be pre-decoded or undecoded (e.g., cell-specific reference signals (CRS), CSI-RS). UE 115 may provide feedback on beam selection, which may be a pre-decoded 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).

[0097] 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).

[0098] 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 implement error detection, error correction, or both to support retransmission and 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.

[0099] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under relatively poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0100] In some cases, UE 115 can measure a first set of beams (“set B beams”) and use the measurements on the first set of beams to predict the characteristics of a second set of beams (“set A beams”). For example, UE 115 can predict which beam in the first set of beams (referred to as set A beams) is the best beam for communicating messages with network entity 105, where the best beam can refer to the beam associated with a channel characteristic (e.g., L1-RSRP) that maximizes or minimizes the metric relative to other beams in the first set of beams. To determine which beam in the first set of beams is the best beam, UE 115 can measure one or more first channel characteristics of the second set of beams (referred to as set B beams) and use the measurements from the second set of beams and an ML model to generate one or more predicted channel characteristics of the first set of beams. For example, UE 115 can measure the L1-RSRP of a first set of one or more reference signals received on the second set of beams and use an ML model to predict the L1-RSRP of set A beams.

[0101] In some examples, UE 115 and / or network entity 105 may perform spatial downlink beam prediction for set A beams using AI or ML models based on measurements of set B beams. For example, set B beams may be relatively wide beams (such as SSB beams), while set A beams may be relatively narrow beams (such as CSI-RS beams). As another example, set B beams may be narrow beams (such as CSI-RS beams), while set A beams may be wide beams (such as SSB beams). In some examples, UE 115 may perform temporal downlink beam prediction for set A beams using ML models based on historical measurements of set B beams. For example, set A beams and set B beams may be the same beams at different times (e.g., purely temporal beam prediction). As another example, set A beams and set B beams may be different beams at different times (e.g., temporal and spatial beam prediction). In some cases, beam prediction may be performed by one or more UEs 115, one or more network entities 105, or any combination thereof. In some cases, beam prediction can be performed for single-cell scenarios.

[0102] For example, for UE mobility and other scenarios, L3 measurement predictions (e.g., beam and cell-level L3 measurement predictions) can be obtained. In some cases, cell-level measurement predictions may include intra-frequency and inter-frequency measurement predictions (e.g., in UE-side and network-side models). In some cases, inter-cell beam-level measurement predictions may be used for L3 mobility (e.g., in UE-side and network-side models). L1 beam measurements can be used to generate L3 beam measurements by filtering L3 beam measurements. L3 beam measurements can provide a longer-term beam measurement view than Layer 1 measurements. Therefore, L3 beam measurements can be used for RRM-type decisions and procedures. In some examples, L1 beam measurements and L1 beam predictions can be used to generate L3 beam measurements.

[0103] One or more UEs 115 may include a UE communication manager 101 that can support wireless communication according to examples disclosed herein. For example, the UE communication manager 101 may be capable of, configured to, or operable to support components for sending a request message to a network entity associated with one or more serving cells, the request message indicating one or more candidate cells predicted by the UE based on one or more AI / ML-based functionalities or models, wherein the request message indicates a request for one or more reference signal configurations corresponding to the one or more candidate cells. The UE communication manager 101 may be capable of, configured to, or operable to support components for receiving a first control message from a network entity, the first control message indicating a reference signal configuration for one or more reference signals associated with one or more beams, the one or more beams being associated with one or more candidate cells predicted by the UE. The UE communication manager 101 may be capable of, configured to, or operable to support components for sending a measurement report indicating a set of one or more L3 beam measurements, wherein the set of one or more L3 beam measurements is based on a reference signal configuration of one or more reference signals received via one or more beams.

[0104] One or more network entities 105 may include a network entity communication manager 102 that can support wireless communication according to examples disclosed herein. For example, the network entity communication manager 102 may be capable of, configured to, or operable to support components for outputting a first request message including a request for a reference signal configuration of one or more reference signals associated with one or more beams of at least one of the candidate cells. The network entity communication manager 102 may be capable of, configured to, or operable to support components for outputting a message indicating the reference signal configuration of one or more reference signals in response to the first request message. The network entity communication manager 102 may be capable of, configured to, or operable to support components for obtaining a measurement report indicating a set of L3 beam measurements, wherein the set of L3 beam measurements is based on the reference signal configuration of one or more reference signals.

[0105] Wireless communication system 100 can support the use of AI / ML models / functionality to predict candidate cells and / or beams associated with candidate cells. For example, UE 115 can send an indication of the predicted candidate cell / beam to serving network entity 105 (e.g., serving CU, serving DU). The indication from UE 115 may also include a request for one or more reference signal configurations associated with the predicted candidate cell. After receiving the request from UE 115, the serving CU / DU can forward the request to one or more candidate CU / DUs, which can then provide the requested reference signal configuration. Serving network entity 105 can provide the requested reference signal configuration to UE 115, and therefore, UE 115 can provide one or more L3 beam measurements via a measurement report based on the reference signal configuration.

[0106] Figure 2 An example of a network architecture 200 (e.g., a decomposed base station architecture, a decomposed RAN architecture) supporting UE and network actions based on L3 cell and beam prediction according to one or more aspects of this disclosure is shown. Network architecture 200 may exemplify examples for implementing one or more aspects of wireless communication system 100. Network architecture 200 may include one or more CUs 160-a that can communicate directly with core network 130-a via backhaul communication link 120-a, or indirectly with core network 130-a via one or more decomposed network entities 105 (e.g., near-RT RIC 175-b via an E2 link or a non-RT RIC 175-a associated with SMO 180-a (e.g., an SMO framework) or both). CUs 160-a may communicate with one or more DUs 165-a via a corresponding midhaul communication link 162-a (e.g., an F1 interface). DUs 165-a may communicate with one or more RUs 170-a via a corresponding fronthaul communication link 168-a. RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with UE 115-a via one or more communication links 125-a. In some implementations, UE 115-a may be served by multiple RU 170-a simultaneously.

[0107] Each network entity in network entity 105 of network architecture 200 (e.g., CU 160-a, DU 165-a, RU170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, Open Cloud (O-Cloud) 205, Open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or transmit signals (e.g., data, information) via wired or wireless transmission media. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to the interfaces of network entity 105 may be configured to communicate with one or more network entities in other network entities 105 via transmission media. For example, these network entities 105 may include wired interfaces configured to receive signals or transmit signals to one or more network entities in other network entities 105 via wired transmission media. Additionally or alternatively, network entity 105 may include a wireless interface that may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals via a wireless transmission medium or to transmit signals to one or more other network entities in network entity 105, or both.

[0108] In some examples, the CU 160-a can host one or more higher-level control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 160-a. The CU 160-a can be configured to handle user plane functionalities (e.g., CU-UP), control plane functionalities (e.g., CU-CP), or combinations thereof. In some examples, the CU 160-a can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 160-a can be implemented to communicate with the DU 165-a for network control and signaling purposes, as needed.

[0109] DU 165-a may correspond to a logic unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RU 170-a. In some examples, DU 165-a may at least partially host one or more aspects of the RLC layer, MAC layer, and PHY layer (e.g., high PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on the functional partitioning, such as those defined by the 3rd Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface configured to communicate with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0110] In some examples, lower-layer functionality may be implemented by one or more RU 170-a units. For example, an RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (e.g., performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both) based at least in part on functional decomposition (such as lower-layer functional decomposition). In this architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UE 115-a units. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a unit. In some examples, such configurations enable the DU 165-a and CU 160-a units to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0111] The SMO 180-a can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (e.g., the O1 interface). For virtualized network entities 105, the SMO 180-a can be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., the O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a can communicate with components configured according to the 4G RAN (e.g., via the O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RU 170-a via the O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0112] The non-RT RIC 175-a can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, AI or ML workflows (including model training and updates), or policy-based guidance of applications / features in the near-RT RIC 175-b. The non-RT RIC 175-a can be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions through interfaces (e.g., via an E2 interface) connected to the near-RT RIC 175-b by one or more CU 160-a, one or more DU 165-a, or both, and an O-eNB 210.

[0113] In some examples, to generate AI / ML models to be deployed in a near-RT RIC 175-b, a non-RT RIC 175-a may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 175-b and can be received from non-network data sources or network functions at the SMO 180-a or non-RT RIC 175-a. In some examples, a non-RT RIC 175-a or near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, a non-RT RIC 175-a may monitor long-term trends and patterns in performance and use AI or ML models to perform corrective actions via the SMO 180-a (e.g., via O1 reconfiguration) or via RAN management policies (e.g., A1 policies).

[0114] Network architecture 200 can support the use of AI / ML models / functionality to predict candidate cells and / or beams associated with candidate cells. For example, UE 115 can send an indication of the predicted candidate cell / beam to serving network entity 105 (e.g., serving CU, serving DU). The indication from UE 115 may also include a request for one or more reference signal configurations associated with the predicted candidate cell. After receiving the request from UE 115, the serving CU / DU can forward the request to one or more candidate CU / DUs, which can then provide the requested reference signal configuration. Serving network entity 105 can provide the requested reference signal configuration to UE 115, and therefore, UE 115 can provide one or more L3 beam measurements via a measurement report based on the reference signal configuration.

[0115] Figure 3 An example of a wireless communication system 300 supporting UE and network actions based on L3 cell and beam prediction, according to one or more aspects of this disclosure, is shown. The wireless communication system 300 can be implemented as described in the reference... Figure 1 and Figure 2 The aspects of the described wireless communication system 100 and network architecture 200 may be implemented by the wireless communication system and the network architecture. For example, the wireless communication system 300 may include UE 115-b, which may be an example of UE 115 as described herein. The wireless communication system 300 may include network entities 105-a and 105-b, which may be corresponding examples of network entity 105 as described herein.

[0116] UE 115-b can communicate with network entity 105-a using communication link 125-a. Communication link 125-a can be an example of an NR or LTE link between UE 115-b and network entity 105-a. Communication link 125-a can include a bidirectional link that enables both uplink and downlink communication. For example, UE 115-b can use communication link 125-a to send uplink signals 305 (e.g., uplink transmissions), such as uplink control signals or uplink data signals, to network entity 105-a, and network entity 105-a can use communication link 125-a to send downlink signals 310 (e.g., downlink transmissions), such as downlink control signals or downlink data signals, to UE 115-b.

[0117] In the wireless communication system 300, UE 115-b can support AI and / or ML-based models and / or functionalities, such as those used for beam prediction. UE 115-b can collect data measurements (e.g., RSRP measurements, SINR measurements, CIR measurements, etc.) for one or more directional beams based on measurements of reference signals (e.g., SSB, CSI-RS, or other reference signals). For example, UE 115-b can measure signals received via directional beams traversed by transmitting / receiving SSBs and / or via directional beams traversed by transmitting / receiving CSI-RS. UE 115-b can use measurements of a first set of beams of a network entity to train a given AI / ML model / functionality 350 to predict measurements of a second set of beams (e.g., different sets of beams, future sets of beams) for the network entity. Furthermore, the trained AI / ML model / functionality can use measurements of a third set of beams to predict measurements of a fourth set of beams, which can be a process referred to as beam inference. In some cases, inference can refer to one or more processes of inputting data into a trained AI / ML model for prediction. The measurements of beams of network entity 105 predicted or output by the AI / ML model (e.g., a first set of beams or a third set of beams, which may correspond to the same set of beams) can be referred to as set A beams, and the measurements of beams of network entities input into the AI / ML model / functionality 350 (e.g., a second set of beams or a fourth set of beams, which may correspond to the same set of beams) can be referred to as set B beams. In some examples, predicting measurements may include calculating the values ​​of the measurements for the beam sets without relying on the actual measurements performed by UE 115-b for the beam sets.

[0118] UE 115-b can use an AI / ML model and / or functionality 350 to determine which beam in set A beams is most likely to have the best L1-RSRP value. L1 beam measurement can refer to a measurement of a beam in the physical layer (e.g., L1). For example, an L1 beam measurement can be the RSRP, SINR, or CIR measured by one or more reference signals received via a given beam. L1 beam prediction can refer to the predicted L1 measurement value for a beam (e.g., set A beams) based on actual measurements of one or more beams (e.g., set B beams). L1 beam prediction can be performed for beams different from set B beams (e.g., spatial prediction) or for future measurements (e.g., temporal prediction). L1 beam measurements can be used to generate L3 beams and / or cell measurements by filtering the L1 beam measurements. L3 beam measurement for a beam can refer to the measurement of the beam at a network layer (e.g., L3) by filtering one or more L1 beam measurements for the beam, for example, to remove the effects of fast fading and / or help reduce short-term variations in the L1 beam measurement. Therefore, L3 beam measurement can provide a longer-term beam measurement view than L3 measurements, and L3 beam measurement can be used for RRM, such as triggering the handover process.

[0119] To obtain L3 measurements, a network entity 105-a (e.g., serving network entity, serving gNB, serving CU, serving DU) associated with the serving cell can provide UE 115-b with one or more control messages (e.g., including...) indicating the configuration (e.g., measurement configuration). measConfig (IE's RRC message). Measurement configuration can indicate the measurements to be performed by the UE 115-b (e.g., the measurement object). measObject This can include one or more measurements of one or more neighboring cells. The one or more neighboring cells can be referred to as one or more candidate cells, one or more target cells, etc. For example, measurements can be applied to intra-frequency, inter-frequency, and inter-RAT mobility, as well as the configuration of one or more measurement gaps. In some examples, this can be achieved via... RRCReconfiguration information, RRCResume Messages, or any combination thereof, are used to signal measurement configurations. In some cases, fields (e.g., each) measObjectNR within ReferenceSignalConfig The field can be configured for measurements of SSB, CSI-RS, or both. Another field (e.g., reportConfig within rsTypeThe field can indicate which type of measurement resource to use to perform the measurement. Thus, UE 115-b can receive instructions from the serving cell on one or more reference signals (e.g., the serving cell provides which / when SSB / CSI-RS resources should be measured), as well as other measurement parameters for deriving the measurement (e.g., L1 measurement, L3 measurement).

[0120] However, in some cases, network entities associated with the source cell can be configured with a relatively large number of reference signals (e.g., SSB / CSI-RS resources), which may lead to excessive power consumption by the UE. Furthermore, while predicting the SSB / CSI-RS resources and associated L1 / L3 measurements of neighboring cells can reduce the number of measurement targets, such predictions may be impractical because any prediction of when the UE's SSB / CSI-RS will be available for neighboring cells can be difficult (e.g., in the absence of measurement configurations for one or more neighboring cells). In addition, inaccurate measurement predictions can lead to problems such as relatively frequent handovers, increased LTM failures, beam failures, and ping-pong effects. As an example, LTM (which can also be referred to as L1 / L2-based mobility) can be associated with changes in the serving cell via L1 / L2 signaling, where the configurations of other layers (e.g., upper layers) can remain unchanged. Therefore, an LTM failure can refer to a failure during the L1 / L2-based mobility process, such as when one or more timers expire before the LTM process is completed or when one or more links associated with the LTM process fail. In some cases, such as in AI / ML-based processes, identifying which parameters can be accurately predicted and the impact of inaccurate predictions may be important. Furthermore, for some AI / ML use cases (e.g., Channel State Information (CSI), Beam Management (BM), and positioning), incorrect or inaccurate predictions can degrade system performance. For example, for UE mobility, inaccurate predictions can lead to issues such as Radio Link Failure (RLF), Handover Failure (HoF), Beam Failure, and significant outages. Due to the relative complexity of such predictions, predicting the reference signal resources and / or measurements to be performed for one or more neighboring cells may be impractical.

[0121] As described herein, AI / ML-based technologies can be used to minimize the measurement objectives of UE 115-b while also enabling efficient handover and LTM procedures. For example, the described technologies enable UE 115-b to use an AI / ML model / functionality 350 to predict candidate cells and / or beams associated with one or more candidate cells (e.g., one or more candidate cells associated with network entity 105-b, one or more beams associated with network entity 105-b, including beams 330-a, 330-b, 330-c), and UE 115-b can send indications of the predicted candidate cells / beams to network entity 105-a (e.g., serving CU, serving DU). As an example, network entity 105-b (e.g., associated with a neighboring cell) can use beamforming technology to transmit a set of reference signals via a set of transmit beams 330 (e.g., beams 330-a, 330-b, and 330-c), and the beams 330 can be predicted by UE 115-b.

[0122] UE 115-b can be configured to send an indication of the predicted cell / beam, for example, via control message 315. The indication from UE 115-b can be included in request message 320, which may also include a request for one or more reference signal configurations associated with the predicted candidate cell and / or beam. Upon receiving the request from UE 115-b, the serving CU / DU can forward the request to one or more candidate CU / DUs, which can then provide the requested reference signal configuration. The reference signal configuration may include, for example, signaling and indicating via RRC message transmission. ReferenceSignalConfig The measurement configuration of the field can indicate the configuration of reference signals associated with set A beams and / or set B beams. Request message 320 may also include a request to activate one or more beams. Network entity 105-a (e.g., associated with the serving cell) can provide the requested reference signal configuration to UE 115-b via control message 340 (such as an RRC message). UE 115-b can receive reference signals from network entity 105-b and perform measurements for reporting L3 measurement results. For example, UE 115-b can use a set of reference signals received via a set of receiving beams 335 (e.g., beams 335-a, 335-b, and 335-c) to perform a set of L1 beam measurements. Therefore, UE 115-b can provide a measurement report including one or more L3 beam measurements based on the reference signal configuration of the candidate cell.

[0123] like Figure 3As shown, based on predictions from the AI / ML model / functionality 350, UE 115-b and one or more network entities 105 can perform one or more actions for managing L3 beam / cell measurements. For example, UE 115-b can predict target / candidate cells, and network entity 105-a can, in response to an indication of the predicted target / candidate cell, request a candidate cell (e.g., network entity 105-b) to provide [the cell with the desired information]. measConfig (For example, the reference signal configuration of each predicted set B of target / candidate cells). In some aspects, UE 115-b can predict one or more beams (e.g., beams 330-a, 330-b, 330-c, or other beams, such as those associated with network entity 105-a). In this case, network entity 105-a can request one or more cells to activate the beam at the target / candidate cell (e.g., associated with network entity 105-b) for UE 115-b to measure.

[0124] In some aspects, when UE 115-b predicts target / candidate cells, UE 115-b can report the target / candidate cells to the serving cell. In this case, uplink signaling (e.g., via the Uu interface) can be used to indicate the target / candidate cells to the serving cell. In the downlink (e.g., via the Uu interface), the serving cell can provide (e.g., via control message 340) the measurement configurations for the reported target / candidate cells (e.g., reference signal configurations for sets B and A of each predicted target / candidate cell). In some aspects, UE 115-b can predict one or more beams, and UE 115-b can request beam activation for the predicted target / candidate cells (e.g., request activation of SSB / CSI-RS resources for the beams). In this case, uplink signaling can include a request for beam activation. In the downlink, the serving cell can indicate (e.g., via control message 340) beam activation and provide the associated reference signal configurations.

[0125] For one or more network entities 105, one or more messages 325 may be exchanged between network entities (e.g., including serving CU, one or more serving DU, candidate / target / neighboring CU, one or more candidate / target / neighboring DU) to obtain information requested by UE 115-b. For example, the serving cell may use a handover command message, Xn signaling, NG signaling, or any combination thereof to transmit a request to the candidate / target cell for providing set A and set B reference signals. The serving cell may request the target / candidate primary node (MN) / secondary node (SN) to provide set A and / or set B reference signal configurations. In some examples, this request may be transmitted via an F1 message using a cell group (CG) configuration message (e.g., CG-config), where the target / candidate MN / SN may request its DUs to provide set A and set B reference signal configurations (e.g., as requested by UE 115-b). Furthermore, when a response is provided to the serving cell, the target / candidate cell may provide reference signal configurations (e.g., set A and set B reference signal configurations) in response, and may use a handover preparation message (e.g., handoverPreparationInformation ), Xn message, NG message, CG message (e.g., CG-ConfigInfo ), F1 messages, or any combination thereof, are sent.

[0126] As an illustrative example, UE 115-b may provide a prediction of a target / candidate cell to the serving CU (e.g., the CU of network entity 105-a), which may be sent via request message 320 to request the configuration of reference signals for sets A and B of candidate / target cells. Request message 320 may be transmitted using RRC signaling. In some examples, if UE 115-b is able to predict the beam at the target / candidate cell, UE 115-b sends request message 320 to the serving CU to request activation of the predicted beam (at the serving / candidate cell) or the reference signal configuration for the predicted beam. Here, this request may be transmitted via RRC signaling, via a MAC control element (MAC-CE), via uplink control information, or any combination thereof.

[0127] In response, the serving CU sends message 325 to the candidate CU (e.g., via AMF if no direct interface exists), which requests the beam set A / set B reference signal configuration at the candidate CU (and the candidate CU's DU) and / or the activation request or reference signal configuration for the predicted beam (at the serving CU (and the candidate CU's DU)).

[0128] In some cases, the candidate CU may then request the candidate CU's DU to provide a set A / set B reference signal configuration for the beams at the candidate DU. In some cases, the candidate CU may request activation of a predicted beam (at the candidate cell) or a reference signal configuration for that predicted beam. The candidate DU may provide the candidate CU with a set A / set B reference signal configuration for the beams at the candidate DU and / or an activation indication for a predicted beam (at the serving / candidate cell) or a reference signal configuration for that predicted beam. In some examples, the candidate CU may provide the serving CU (e.g., via AMF if no direct interface exists) with a set A / set B reference signal configuration for the beams at the candidate CU (and the candidate CU's DU). In some examples, the candidate CU may provide the serving CU with an activation indication or reference signal configuration for a predicted beam (at the candidate cell and / or the DU).

[0129] In some cases, the serving CU may request its serving DU to provide the serving CU with the reference signal configuration for beam set A / set B at the serving CU's serving DU. In some cases, the serving CU may request activation of a predicted beam (at the serving / candidate cell) or the reference signal configuration for that predicted beam. In some examples, the serving CU's serving DU may provide the serving CU with the reference signal configuration for beam set A / set B at the serving DU. In some examples, the serving DU may provide the serving CU with an activation indication for a predicted beam (at the serving / candidate cell) or the reference signal configuration for that predicted beam.

[0130] The Serving CU or Serving DU can provide the UE 115-b with requested configurations or instructions. Therefore, the UE 115-b can send a measurement report 345 that includes measurements of the configured / activated beams.

[0131] By implementing techniques for managing L3 beam and / or cell measurements, UE 115-b can measure one or more neighboring cells (e.g., candidate cells, target cells), thereby improving mobility-based processes. For example, because UE 115-b can predict measurements for one or more beams and / or cells that can be used for mobility purposes (e.g., when UE 115-b is mobile), the number of measurements performed by UE 115-b can be reduced when UE 115-b sends a request for corresponding measurement configurations for neighboring cells and / or beams. That is, based on UE measurement predictions for cells or beams and subsequent requests to the network, UE 115-b can receive measurement configurations for neighboring cell measurements (e.g., without utilizing a relatively large amount of reference signal resources for configuration). Consequently, UE 115-b can save power by performing measurements on predicted cells or beams (e.g., because the number of measurement targets can be reduced).

[0132] Figure 4 An example of an ML procedure 400 supporting UE and network actions based on L3 cell and beam prediction, according to one or more aspects of this disclosure, is shown. The ML procedure 400 may be implemented at network entity 105 or UE 115, or both, as referenced. Figures 1 to 4 As described.

[0133] ML process 400 may include ML algorithm 410. As illustrated, ML algorithm 410 may be an example of a neural network, such as a feedforward (FF) or deep feedforward (DFF) neural network, a recurrent neural network (RNN), a long / short-term memory (LSTM) neural network, or any other type of neural network. However, any other ML algorithm may be supported. For example, ML algorithm 410 may implement the nearest neighbor algorithm, linear regression algorithm, Naive Bayes algorithm, random forest algorithm, or any other ML algorithm. Furthermore, ML process 400 may involve supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, or any combination thereof.

[0134] The ML algorithm 410 may include an input layer 415, one or more hidden layers 420, and an output layer 425. In a fully connected neural network with one hidden layer 420, each hidden layer node 435 may receive values ​​as input from each input layer node 430, where each input may be weighted. These neural network weights may be based on a cost function modified during the training of the ML algorithm 410. Similarly, each output layer node 440 may receive values ​​as input from each hidden layer node 435, where the inputs are weighted. If post-deployment training is supported (e.g., online training), memory may be allocated to store the errors and / or gradients of the inverse matrix multiplication. These errors and / or gradients may support updating the ML algorithm 410 based on output feedback. Training the ML algorithm 410 may support the computation of weights (e.g., connecting input layer nodes 430 to hidden layer nodes 435 and connecting hidden layer nodes 435 to output layer nodes 440) to map input patterns to desired output results. The training can generate device-specific ML algorithms 410 based on historical application data and data transfers of a specific network entity 105 or UE 115.

[0135] In some examples, input value 405 can be passed to ML algorithm 410 for processing. In some examples, input value 405 can be preprocessed according to the operation sequence so that input value 405 is in a format compatible with ML algorithm 410. Input value 405 can be transformed at input layer 415. A set of input layer nodes 430. In some cases, different measurements may be input at different input layer nodes 430 of input layer 415. If the number of input layer nodes 430 exceeds the number of inputs corresponding to input value 405, default values ​​(e.g., value 0) may be assigned to some input layer nodes 430. As illustrated, input layer 415 may include three input layer nodes 430-a, 430-b, and 430-c. However, it should be understood that input layer 415 may include any number of input layer nodes 430 (e.g., 20 input nodes).

[0136] ML algorithm 410 can be based on 430 input layer nodes and The number of input-to-hidden weights between hidden layer nodes 435 transforms input layer 415 into hidden layer 420. ML algorithm 410 may include any number of hidden layers 420 as an intermediate step between input layer 415 and output layer 425. Additionally, each hidden layer 420 may include any number of nodes. For example, as illustrated, hidden layer 420 may include four hidden layer nodes 435-a, 435-b, 435-c, and 435-d. However, it should be understood that hidden layer 420 may include any number of hidden layer nodes 435 (e.g., 10 input nodes). In a fully connected neural network, each node in a layer may be based on each node in the previous layer. For example, the value of hidden layer node 435-a may be based on the values ​​of input layer nodes 430-a, 430-b, and 430-c (e.g., applying different weights to each node value).

[0137] ML algorithm 410 can determine the value of output layer node 440 of output layer 425 after one or more hidden layers 420. For example, ML algorithm 410 can be based on Hidden layer node 435 and The number of hidden-to-output weights between each output layer node 440 determines how hidden layer 420 is transformed into output layer 425. In some cases, Each output layer node 440 can correspond to a different output value 445 of the ML algorithm 410. As illustrated, the ML algorithm 410 may include three output layer nodes 440-a, 440-b, and 440-c, which support three different thresholds. However, it should be understood that the output layer 425 may include any number of output layer nodes 440. In some examples, the output value 445 may be post-processed according to a sequence of operations so that the output value 445 is in a format compatible with the reported output value 445.

[0138] In some examples, ML algorithm 410 can be used to predict beam measurements (e.g., RSPR, SINR, or CIR) for a first set of beams (set A) based on measurements (e.g., RSPR, SINR, or CIR) for a second set of beams (set B). In some examples, ML algorithm 410 can be used to generate L3 beam measurements based on layer 1 beam measurements.

[0139] UE 115, implementing one or more ML algorithms 410, can support the prediction of candidate cells and / or beams associated with candidate cells. For example, UE 115 can use ML algorithm 410 to predict one or more beams and / or cells, and UE 115 can send an indication of the predicted candidate cell / beam to serving network entity 105 (e.g., serving CU, serving DU). The indication from UE 115 may also include a request for one or more reference signal configurations associated with the predicted candidate cell. Upon receiving a request from UE 115, the serving CU / DU can forward the request to one or more candidate CU / DUs, which can then provide the requested reference signal configuration. Serving network entity 105 can provide the requested reference signal configuration to UE 115, and therefore, UE 115 can provide one or more L3 beam measurements via a measurement report based on the reference signal configuration.

[0140] Figure 5 Examples of a process flow 500 supporting UE and network actions based on L3 cell and beam prediction according to one or more aspects of this disclosure are shown. Process flow 500 may implement, or be implemented by, aspects of wireless communication system 100, network architecture 200, wireless communication system 300, or ML process 400. For example, process flow 500 may include UE 115-c, which may be an example of UE 115 as described herein. Process flow 500 may also include serving CU 505-a, serving DU 505-b, candidate CU 505-c, and candidate DU 505-d, each of which may be an example of network entity 105 as described herein. In the following description of process flow 500, information output / received between UE 115-c, serving CU 505-a, serving DU 505-b, candidate CU 505-c, and candidate DU 505-d may be sent in a different order than the example order shown, or operations performed by UE 115-c, serving CU 505-a, serving DU 505-b, candidate CU 505-c, and candidate DU 505-d may be performed in a different order or at different times. Some operations may also be omitted from process flow 500, and other operations may be added to process flow 500.

[0141] At 520, UE 115-c may receive control messages (e.g., second control messages) from serving CU 505-a or from one or more serving DU 505-b, indicating a request to send a request for activating a beam set, a request to configure measurements for the beam set, or both, wherein the request message is sent according to the request configuration. For example, UE 115-c may be configured by a serving network entity (e.g., serving gNB, serving CU 505-a, serving DU 505-b) to provide target / candidate cell prediction or to send request messages (e.g., an activation request indicating beam measurement for the UE and / or a request for one or more beams). measConfig ).

[0142] At 525, UE 115-c may send a request message to serving CU 505-a or one or more serving DU 505-b (e.g., network entities associated with one or more serving cells), indicating one or more candidate cells predicted by the UE based on one or more AI / ML-based functional and / or models. The request message may indicate a request for configuration of one or more reference signals corresponding to the one or more candidate cells. In some examples, UE 115-c may determine a beam set associated with one or more candidate cells predicted by UE 115-c. In some cases, UE 115-c predicts the beam set based on one or more AI / ML-based functional and / or models. In some cases, UE 115-c may send a request via the request message to activate the beam set, to configure measurements for the beam set, or both. In some cases, the beam set includes one or more beams associated with one or more candidate cells, and a set of one or more L3 beam measurements is based on the request message. In some cases, a UE request message (e.g., a UE prediction / beam activation request) may include target / candidate cell beam prediction. The request message may include instructions for enabling (e.g., activating) one or more beams to perform measurements and / or requesting one or more beams of candidate cells based on the prediction. measConfig Activation request.

[0143] At 530, serving CU 505-a may, in response to a request message from UE 115-c, output a first request message to serving DU 505-b, wherein the first request message may include a request for reference signal configuration of one or more reference signals associated with one or more beams of at least one of the candidate cells. In some examples, the first request message may be as CG configuration signaling (e.g., CG-ConfigThe first request message may be transmitted via signaling associated with the F1 interface, and may be transmitted from service CU 505-a to service DU 505-b to request reference signal configuration (e.g., set A / set B beam configuration). Additionally or alternatively, the first request message may include a request to activate one or more beams. Additionally or alternatively, the first request message may include a request for measurement configuration for one or more beams.

[0144] Additionally or alternatively, at 530, serving CU 505-a may, in response to a request message from UE 115-c, output a first request message to candidate CU 505-c, wherein the first request message may include a request for reference signal configuration of one or more reference signals associated with one or more beams of at least one of the candidate cells. In some examples, the first request message may be transmitted as a handover command or via signaling associated with the Xn interface or via signaling associated with the NG interface, and may be transmitted from serving CU 505-a to candidate CU 505-c to request reference signal configuration (e.g., set A / set B beam configuration). Additionally or alternatively, the first request message may include a request to activate one or more beams. Additionally or alternatively, the first request message may include a request for measurement configuration for one or more beams.

[0145] At 535, candidate CU 505-c may output a message requesting reference signal configuration for one or more reference signals in response to a first request message. In some cases, the message may be output from candidate CU 505-c to one or more candidate DU 505-d, and the message may be transmitted as CG configuration signaling (e.g., CG-Config) or via signaling associated with the F1 interface. Messages requesting reference signal configuration (e.g., set A / set B beam configuration) may be transmitted. Additionally or alternatively, the first request message may include a request to activate one or more beams. Additionally or alternatively, the first request message may include a request for measurement configuration for one or more beams.

[0146] At 540, candidate DU 505-d may respond to the first request message by outputting a message indicating the reference signal configuration of one or more reference signals. In some cases, this message may be output from candidate DU 505-d to candidate CU 505-c, and this message may serve as CG configuration signaling (e.g., CG-ConfigInfo The message may be transmitted via signaling associated with the F1 interface. The message may include an indication of a reference signal configuration (e.g., set A / set B beam configuration). Additionally or alternatively, the message may include an indication that one or more beams have been activated (e.g., via an activation indication).

[0147] At 545, candidate CU 505-c can output a message indicating the reference signal configuration of one or more reference signals. In some cases, this message can be output from candidate CU 505-c to serving CU 505-a or to one or more serving DU 505-b via the F1 interface, and this message can serve as a handover preparation message (e.g., HandoverPreparationInformation The message may be transmitted via signaling associated with the Xn interface and / or via signaling associated with the NG interface. The message may include an indication of a reference signal configuration (e.g., set A / set B beam configuration). Additionally or alternatively, the message may include an indication that one or more beams have been activated (e.g., via an activation indication).

[0148] At 550, UE 115-c may receive a first control message from service CU 505-a or from one or more service DU 505-b, the first control message indicating a reference signal configuration for one or more reference signals associated with one or more beams, which are associated with one or more candidate cells predicted by UE 115-c.

[0149] At 555, UE 115-c can determine one or more L3 measurements for one or more candidate cells based on the reference signal configuration.

[0150] At 560, UE 115-c can send a measurement report indicating a set of one or more L3 beam measurements, wherein the set of one or more L3 beam measurements is based on a reference signal configuration of one or more reference signals received via one or more beams.

[0151] At 565, serving CU 505-a can output a message indicating one or more L3 measurement results received from UE 115-c. In some respects, this message can be transmitted from serving CU 505-a to one or more serving DU 505-b, or to candidate CU 505-c, or any combination thereof.

[0152] At 570, candidate CU 505-c can output a message indicating one or more L3 measurement results from UE 115-c. In some aspects, this message can be transmitted from candidate CU 505-c to one or more candidate DU 505-d. In some aspects, one or more mobility procedures can be performed based on one or more L3 measurement results (e.g., based on measurement reports).

[0153] Figure 6A block diagram 600 illustrates a device 605 supporting L3 cell and beam prediction-based UE and network actions according to one or more aspects of this disclosure. Device 605 may be an example of various aspects of UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a UE communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, UE communication manager 620), 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).

[0154] Receiver 610 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 UE and network actions based on L3 cell and beam prediction). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0155] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to UE and network actions based on L3 cell and beam prediction, including packets, user data, control information, or any combination thereof. In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0156] The UE communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be examples of components used to perform various aspects of UE and network actions based on L3 cell and beam prediction as described herein. For example, the UE communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0157] In some examples, the UE communication manager 620, receiver 610, transmitter 615, 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).

[0158] Additionally or alternatively, the UE communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in code (e.g., referred to as processor executable code) executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the UE communication manager 620, receiver 610, transmitter 615, 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, as components for performing the functions described in this disclosure).

[0159] In some examples, the UE communication manager 620 can be configured to use a receiver 610, a transmitter 615, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the UE communication manager 620 can receive information from the receiver 610, transmit information to the transmitter 615, or integrate with the receiver 610, the transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0160] The UE communication manager 620 can support wireless communication according to examples disclosed herein. For example, the UE communication manager 620 can be configured or operated to support components for sending a request message to a network entity associated with one or more serving cells, the request message indicating one or more candidate cells predicted by the UE based on one or more AI-based functionalities or models, wherein the request message indicates a request for one or more reference signal configurations corresponding to the one or more candidate cells. The UE communication manager 620 can be configured or operated to support components for receiving a first control message from a network entity, the first control message indicating a reference signal configuration for one or more reference signals associated with one or more beams, which are associated with one or more candidate cells predicted by the UE. The UE communication manager 620 can be configured or operated to support components for sending a measurement report indicating a set of one or more L3 beam measurements, wherein the set of one or more L3 beam measurements is based on a reference signal configuration of one or more reference signals received via one or more beams.

[0161] By including or configuring a UE communication manager 620 according to the examples described herein, device 605 (e.g., controlling receiver 610, transmitter 615, UE communication manager 620, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for predicting one or more target / candidate cells and predicting beams associated with the target / candidate cells, thereby enabling efficient measurements of neighboring cells and also achieving power savings at device 605. For example, the described techniques implemented by device 605 can reduce the set of measurement objects because device 605 can measure only the cells / beams based on AI / ML-based predictions made by device 605.

[0162] Figure 7 A block diagram 700 illustrates a device 705 supporting L3 cell and beam prediction-based UE and network actions according to one or more aspects of this disclosure. Device 705 may be an example of aspects of device 605 or UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a UE communication manager 720. Device 705 or one or more components of device 705 (e.g., receiver 710, transmitter 715, UE communication manager 720) 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).

[0163] Receiver 710 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 UE and network actions based on L3 cell and beam prediction). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0164] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to UE and network actions based on L3 cell and beam prediction, including packets, user data, control information, or any combination thereof. In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0165] Device 705 or its various components may be examples of parts used to perform various aspects of UE and network actions based on L3 cell and beam prediction as described herein. For example, UE communication manager 720 may include request component 725, reference signal configuration component 730, measurement reporting component 735, or any combination thereof. UE communication manager 720 may be examples of aspects of UE communication manager 620 as described herein. In some examples, UE communication manager 720 or its various components may be configured to use receiver 710, transmitter 715, or both, or otherwise cooperate with them to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, UE communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or integrate with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0166] The UE communication manager 720 can support wireless communication according to examples disclosed herein. The request component 725 is capable of, configured to, or operable to support components for sending a request message to a network entity associated with one or more serving cells, the request message indicating one or more candidate cells predicted by the UE based on one or more AI-based functionalities or models, wherein the request message indicates a request for one or more reference signal configurations corresponding to the one or more candidate cells. The reference signal configuration component 730 is capable of, configured to, or operable to support components for receiving a first control message from a network entity, the first control message indicating a reference signal configuration for one or more reference signals associated with one or more beams, which are associated with one or more candidate cells predicted by the UE. The measurement report component 735 is capable of, configured to, or operable to support components for sending a measurement report indicating a set of one or more L3 beam measurements, wherein the set of one or more L3 beam measurements is based on a reference signal configuration of one or more reference signals received via one or more beams.

[0167] Figure 8 A block diagram 800 is shown of a UE communication manager 820 supporting L3 cell and beam prediction-based UE and network actions according to one or more aspects of this disclosure. The UE communication manager 820 may be an example of aspects of the UE communication manager 620, UE communication manager 720, or both as described herein. The UE communication manager 820 or its various components may be examples of parts for performing various aspects of L3 cell and beam prediction-based UE and network actions as described herein. For example, the UE communication manager 820 may include a request component 825, a reference signal configuration component 830, a measurement reporting component 835, a beam component 840, a request configuration component 845, 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).

[0168] The UE communication manager 820 can support wireless communication according to examples disclosed herein. The request component 825 is capable of, configured to, or operable to support components for sending a request message to a network entity associated with one or more serving cells, the request message indicating one or more candidate cells predicted by the UE based on one or more AI-based functionalities or models, wherein the request message indicates a request for one or more reference signal configurations corresponding to the one or more candidate cells. The reference signal configuration component 830 is capable of, configured to, or operable to support components for receiving a first control message from a network entity, the first control message indicating a reference signal configuration for one or more reference signals associated with one or more beams, which are associated with one or more candidate cells predicted by the UE. The measurement report component 835 is capable of, configured to, or operable to support components for sending a measurement report indicating a set of one or more L3 beam measurements, wherein the set of one or more L3 beam measurements is based on a reference signal configuration of one or more reference signals received via one or more beams.

[0169] In some examples, beamforming component 840 is capable of, configured to, or operable to support components for determining a set of beams associated with one or more candidate cells predicted by the UE, wherein the set of beams is predicted by the UE at least in part based on one or more AI-based functionalities or models. In some examples, request component 825 is capable of, configured to, or operable to support components for sending a request for activating a set of beams, a request for configuring measurements for the set of beams, or both, via a request message, wherein the set of beams includes one or more beams associated with one or more candidate cells, and wherein a set of one or more L3 beam measurements is based on the request message.

[0170] In some examples, the request configuration component 845 is capable of, configured to, or able to operate to support components for receiving a second control message from a network entity, the second control message indicating a request to send a request to activate a beam set, a request to configure measurements for the beam set, or both, wherein the request message is sent according to the request configuration.

[0171] In some examples, beamforming component 840 is capable of, configured to, or operable to support components for receiving a third control message from a network entity, the third control message indicating that a beam set has been activated, wherein the third control message is received in response to a request message, and wherein a set of one or more L3 beam measurements is based on the activation of the beam set.

[0172] In some examples, the request message is sent via RRC signaling. In some examples, the request message is sent via MAC-CE. In some examples, the request message is sent via uplink control information.

[0173] Figure 9 A diagram is shown of a system 900 including device 905 supporting UE and network actions based on L3 cell and beam prediction, according to one or more aspects of this disclosure. Device 905 may be an example of device 605, device 705, or UE 115 as described herein, or may include components thereof. Device 905 may (e.g., wirelessly) communicate with one or more other devices (e.g., network entity 105, UE 115, or any combination thereof). Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a UE communication manager 920, an input / output (I / O) controller (such as I / O controller 910), a transceiver 915, one or more antennas 925, at least one memory 930, code 935, and at least one processor 940. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 945).

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

[0175] In some cases, device 905 may include a single antenna. However, in other cases, device 905 may have more than one antenna, which can concurrently transmit or receive multiple wireless transmissions. Transceiver 915 may use a wired or wireless link to communicate bidirectionally via one or more antennas 925, as described herein. For example, transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 915 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. Transceiver 915, or transceiver 915 and one or more antennas 925, may be an example of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof or components thereof as described herein.

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

[0177] At least one processor 940 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more 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 940 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 940. At least one processor 940 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 930) to cause device 905 to perform various functions (e.g., functions or tasks supporting UE and network actions based on L3 cell and beam prediction). For example, device 905 or components of device 905 may include at least one processor 940 and at least one memory 930 coupled to or coupled to at least one processor 940, the at least one processor 940 and the at least one memory 930 being configured to perform the various functions described herein.

[0178] In some examples, at least one processor 940 may include multiple processors, and at least one memory 930 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 940 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 940) and memory circuitry (which may include at least one memory 930)) 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 940 or a processing system including at least one processor 940 may be configured, capable of being configured, or operable to cause device 905 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” can be used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code 935 (e.g., processor-executable code) stored in at least one memory 930 or otherwise.

[0179] The UE communication manager 920 can support wireless communication according to examples disclosed herein. For example, the UE communication manager 920 can be configured or operated to support components for sending a request message to a network entity associated with one or more serving cells, the request message indicating one or more candidate cells predicted by the UE based on one or more AI-based functionalities or models, wherein the request message indicates a request for one or more reference signal configurations corresponding to the one or more candidate cells. The UE communication manager 920 can be configured or operated to support components for receiving a first control message from a network entity, the first control message indicating a reference signal configuration for one or more reference signals associated with one or more beams, which are associated with one or more candidate cells predicted by the UE. The UE communication manager 920 can be configured or operated to support components for sending a measurement report indicating a set of one or more L3 beam measurements, wherein the set of one or more L3 beam measurements is based on a reference signal configuration of one or more reference signals received via one or more beams.

[0180] By including or configuring a UE communication manager 920 according to an example as described herein, device 905 can support techniques for predicting one or more target / candidate cells and predicting beams associated with the target / candidate cells, thereby enabling efficient measurement of neighboring cells and power savings at device 905. For example, the described techniques implemented by device 905 can reduce the set of measurement objects because device 905 can measure only the cells / beams predicted based on device 905's AI / ML. Therefore, the described techniques implemented by device 905 can lead to improved communication reliability, reduced latency, improved user experience associated with reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, and / or improved utilization of processing power.

[0181] In some examples, the UE communication manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 915, one or more antennas 925, or any combination thereof, or otherwise cooperating with them. Although the UE communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the UE communication manager 920 may be supported or executed by at least one processor 940, at least one memory 930, code 935, or any combination thereof. For example, code 935 may include instructions that can be executed by at least one processor 940 to cause device 905 to perform various aspects of UE and network actions based on L3 cell and beam prediction as described herein, or at least one processor 940 and at least one memory 930 may be otherwise configured to perform or support such operations individually or jointly.

[0182] Figure 10 A block diagram 1000 of a device 1005 supporting L3 cell and beam prediction-based UE and network actions according to one or more aspects of this disclosure is shown. Device 1005 may be an example of aspects of network entity 105 as described herein. Device 1005 may include a receiver 1010, a transmitter 1015, and a network entity communication manager 1020. Device 1005, or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, network entity communication manager 1020), 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).

[0183] Receiver 1010 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 1005. In some examples, receiver 1010 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0184] Transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, transmitter 1015 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 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 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 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0185] The network entity communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be examples of components used to perform various aspects of UE and network actions based on L3 cell and beam prediction as described herein. For example, the network entity communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0186] In some examples, the network entity communication manager 1020, receiver 1010, transmitter 1015, 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).

[0187] Additionally or alternatively, the network entity communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented in code (e.g., referred to as processor executable code) executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the network entity communication manager 1020, receiver 1010, transmitter 1015, 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, as components for performing the functions described herein).

[0188] In some examples, the network entity communication manager 1020 can be configured to use a receiver 1010, a transmitter 1015, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, sending). For example, the network entity communication manager 1020 can receive information from the receiver 1010, transmit information to the transmitter 1015, or integrate with the receiver 1010, the transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0189] The network entity communication manager 1020 may support wireless communication according to examples disclosed herein. For example, the network entity communication manager 1020 may be capable of, configured to, or operable to support components for outputting a first request message including a request for a reference signal configuration of one or more reference signals associated with one or more beams of at least one of one or more candidate cells. The network entity communication manager 1020 may be capable of, configured to, or operable to support components for outputting a message indicating a reference signal configuration of one or more reference signals, at least in part based on the first request message. The network entity communication manager 1020 may be capable of, configured to, or operable to support components for obtaining a measurement report indicating a set of L3 beam measurements, wherein the set of L3 beam measurements is based on the reference signal configuration of one or more reference signals.

[0190] By including or configuring a network entity communication manager 1020 according to an example as described herein, device 1005 (e.g., controlling receiver 1010, transmitter 1015, network entity communication manager 1020 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for requesting measurement configurations based on predictions of one or more target / candidate cells and predictions of beams associated with the target / candidate cells, thereby enabling efficient measurements of neighboring cells and robust mobility processes (e.g., based on L3 measurements).

[0191] Figure 11 A block diagram 1100 of device 1105 supporting L3 cell and beam prediction-based UE and network actions according to one or more aspects of this disclosure is shown. Device 1105 may be an example of aspects of device 1005 or network entity 105 as described herein. Device 1105 may include receiver 1110, transmitter 1115, and network entity communication manager 1120. Device 1105 or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, network entity communication manager 1120) 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).

[0192] Receiver 1110 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 1105. In some examples, receiver 1110 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0193] Transmitter 1115 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, transmitter 1115 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 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1115 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 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0194] Device 1105 or its various components may be examples of parts used to perform various aspects of UE and network actions based on L3 cell and beam prediction as described herein. For example, network entity communication manager 1120 may include request manager 1125, reference signal configuration manager 1130, measurement report manager 1135, or any combination thereof. Network entity communication manager 1120 may be examples of aspects of network entity communication manager 1020 as described herein. In some examples, network entity communication manager 1120 or its various components may be configured to use receiver 1110, transmitter 1115, or both, or otherwise cooperate with them to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, network entity communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or integrate in combination with receiver 1110, transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0195] Network entity communication manager 1120 may support wireless communication according to examples disclosed herein. Request manager 1125 is capable of, configured to, or operable to support components for outputting a first request message including a request for reference signal configuration of one or more reference signals associated with one or more beams of at least one of the candidate cells. Reference signal configuration manager 1130 is capable of, configured to, or operable to support components for outputting a message indicating the reference signal configuration of one or more reference signals, at least in part based on the first request message. Measurement report manager 1135 is capable of, configured to, or operable to support components for obtaining a measurement report indicating a set of L3 beam measurements, wherein the set of L3 beam measurements is based on the reference signal configuration of one or more reference signals.

[0196] Figure 12 A block diagram 1200 is shown of a network entity communication manager 1220 supporting L3 cell and beam prediction-based UE and network actions according to one or more aspects of this disclosure. The network entity communication manager 1220 may be an example of a network entity communication manager 1020, a network entity communication manager 1120, or aspects thereof as described herein. The network entity communication manager 1220 or its various components may be examples of components for performing various aspects of L3 cell and beam prediction-based UE and network actions as described herein. For example, the network entity communication manager 1220 may include a request manager 1225, a reference signal configuration manager 1230, a measurement report manager 1235, a beam activation manager 1240, 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). The communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components or virtualization components associated with network entity 105, between devices, components or virtualization components associated with network entity 105), or any combination thereof.

[0197] Network entity communication manager 1220 may support wireless communication according to examples disclosed herein. Request manager 1225 is capable of, configured to, or operable to support components for outputting a first request message including a request for reference signal configuration of one or more reference signals associated with one or more beams of at least one of the candidate cells. Reference signal configuration manager 1230 is capable of, configured to, or operable to support components for outputting a message indicating the reference signal configuration of one or more reference signals, at least in part based on the first request message. Measurement report manager 1235 is capable of, configured to, or operable to support components for obtaining a measurement report indicating a set of L3 beam measurements, wherein the set of L3 beam measurements is based on the reference signal configuration of one or more reference signals.

[0198] In some examples, the request manager 1225 is capable of, configured to, or operable to support components for obtaining a second request message indicating one or more candidate cells, wherein the second request message indicates a request for one or more reference signal configurations corresponding to the one or more candidate cells, and wherein the first request message is based on the second request message.

[0199] In some examples, the beam activation manager 1240 is capable of, configured to, or operable to support components for obtaining a request via a second request message for activating a beam set associated with one or more candidate cells, a request for configuring measurements for the beam set, or both, wherein the beam set includes one or more beams associated with one or more candidate cells, and wherein the set of L3 beam measurements is based on the second request message. In some examples, the beam activation manager 1240 is capable of, configured to, or operable to support components for outputting a message indicating that the beam set has been activated, wherein the set of L3 beam measurements is based on the activation of the beam set.

[0200] In some examples, the first request message includes a handover command message.

[0201] In some examples, the first request message includes signaling associated with the F1 interface, signaling associated with the Xn interface, signaling associated with the NG interface, or any combination thereof.

[0202] In some examples, the first request message includes a cell group configuration message, or signaling associated with the F1 interface, or any combination thereof.

[0203] In some examples, the message includes a handover preparation message.

[0204] In some examples, the message includes signaling associated with the Xn interface, signaling associated with the NG interface, or any combination thereof.

[0205] In some examples, the message includes a cell group configuration message, or signaling associated with the F1 interface, or any combination thereof.

[0206] Figure 13 A diagram of a system 1300 including device 1305 supporting UE and network actions based on L3 cell and beam prediction, according to one or more aspects of this disclosure, is shown. Device 1305 may be an example of device 1005, device 1105, or network entity 105 as described herein, or may include components thereof. Device 1305 may communicate with other network devices or network equipment, such as network entity 105, UE 115, or any combination thereof. This communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1305 may include components supporting output and acquisition of communication, such as network entity communication manager 1320, transceiver 1310, one or more antennas 1315, at least one memory 1325, code 1330, and at least one processor 1335. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1340).

[0207] Transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1310 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1310 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1305 may include one or more antennas 1315 that may be capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1310 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1315, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1315, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1310 may include one or more processors or one or more memory components, or be configured to couple to one or more processors or one or more memory components capable of operating 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 1310, or transceiver 1310 and one or more antennas 1315, or transceiver 1310 and one or more antennas 1315, and one or more processors or one or more memory components (e.g., at least one processor 1335, at least one memory 1325, or both), may be included in a chip or chip assembly mounted in device 1305. In some examples, transceiver 1310 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, and fronthaul communication link 168).

[0208] At least one memory 1325 may include RAM, ROM, or any combination thereof. At least one memory 1325 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1330. Code 1330 may include instructions that, when executed by one or more processors in at least one processor 1335, cause device 1305 to perform the various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by a processor in at least one processor 1335, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1325 may include a BIOS, etc., that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1335 may include multiple processors, and at least one memory 1325 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).

[0209] At least one processor 1335 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more 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 1335 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 1335. At least one processor 1335 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1325) to cause device 1305 to perform various functions (e.g., functions or tasks supporting UE and network actions based on L3 cell and beam prediction). For example, device 1305 or components thereof may include at least one processor 1335 and at least one memory 1325 coupled to one or more processors in at least one processor 1335, the at least one processor 1335 and the at least one memory 1325 being configured to perform the various functions described herein. At least one processor 1335 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 1330) host functions for performing the functions of device 1305. At least one processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1305 (such as within one or more memories of at least one memory 1325).

[0210] In some examples, at least one processor 1335 may include multiple processors, and at least one memory 1325 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 1335 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1335) and memory circuitry (which may include at least one memory 1325)) or components that receive or receive 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 1335 or a processing system including at least one processor 1335 may be configured, capable of being configured, or operable to cause device 1305 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 stored in at least one memory 1325 or otherwise.

[0211] In some examples, bus 1340 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1340 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 1305, or communication performed between different co-addressable or potentially disparate components of device 1305 (e.g., where device 1305 may refer to a system in which one or more of network entity communication manager 1320, transceiver 1310, at least one memory 1325, code 1330, and at least one processor 1335 may be located within one of the different components or partitioned between the different components).

[0212] In some examples, the network entity communication manager 1320 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 network entity communication manager 1320 can manage the delivery of data communications by client devices (such as one or more UEs 115). In some examples, the network entity communication manager 1320 can manage communication with one or more other network entities 105 and may include a controller or scheduler for (e.g., coordinating one or more other network devices) controlling communication with UE 115. In some examples, the network entity communication manager 1320 may support the X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0213] The network entity communication manager 1320 may support wireless communication according to examples disclosed herein. For example, the network entity communication manager 1320 may be capable of, configured to, or operable to support components for outputting a first request message including a request for a reference signal configuration of one or more reference signals associated with one or more beams of at least one of one or more candidate cells. The network entity communication manager 1320 may be capable of, configured to, or operable to support components for outputting a message indicating a reference signal configuration of one or more reference signals, at least in part based on the first request message. The network entity communication manager 1320 may be capable of, configured to, or operable to support components for obtaining a measurement report indicating a set of L3 beam measurements, wherein the set of L3 beam measurements is based on the reference signal configuration of one or more reference signals.

[0214] By including or configuring a network entity communication manager 1320 according to an example as described herein, device 1305 can support techniques for requesting measurement configurations based on predictions of one or more target / candidate cells and predictions of beams associated with the target / candidate cells, thereby enabling efficient measurement of neighboring cells and robust mobility processes (e.g., based on L3 measurements). For example, the described techniques implemented by device 1305 can limit the set of measurement objects used for L3 cell / beam measurements. Therefore, the described techniques implemented by device 1305 can lead to improved communication reliability, reduced latency, improved user experience associated with reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, and / or improved utilization of processing power.

[0215] In some examples, the network entity communication manager 1320 may be configured to use or otherwise coordinate with transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receive, acquire, monitor, output, transmit). Although the network entity communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the network entity communication manager 1320 may be supported or performed by transceiver 1310, one or more processors in at least one processor 1335, one or more memories in at least one memory 1325, code 1330, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1335, at least one memory 1325, code 1330, or any combination thereof). For example, code 1330 may include instructions that can be executed by one or more processors of at least one processor 1335 to cause device 1305 to perform various aspects of UE and network actions based on L3 cell and beam prediction as described herein, or at least one processor 1335 and at least one memory 1325 may be otherwise configured to perform or support such operations individually or jointly.

[0216] Figure 14 A flowchart illustrating a method 1400 for supporting UE and network actions based on L3 cell and beam prediction according to one or more aspects of this disclosure is shown. Operation of method 1400 can be implemented by a UE or its components as described herein. For example, operation of method 1400 can be performed by, as referenced... Figures 1 to 9 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0217] At 1405, the method may include: sending a request message to a network entity associated with one or more serving cells, the request message indicating one or more candidate cells predicted by the UE based on one or more AI-based functionalities or models, wherein the request message indicates a request for configuration of one or more reference signals corresponding to the one or more candidate cells. The operation of 1405 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1405 may be provided by reference to... Figure 8 The requested component 825 is used to execute the request.

[0218] At 1410, the method may include: receiving a first control message from a network entity, the first control message indicating a reference signal configuration for one or more reference signals associated with one or more beams, the one or more beams being associated with one or more candidate cells predicted by the UE. Operation of 1410 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 1410 may be provided by reference to... Figure 8 The reference signal configuration component 830 described herein is executed.

[0219] At 1415, the method may include: sending a measurement report indicating a set of one or more L3 beam measurements, wherein the set of one or more L3 beam measurements is configured based on a reference signal configuration of one or more reference signals received via one or more beams. Operation of 1415 may be performed according to the examples disclosed herein. In some examples, aspects of operation of 1415 may be provided by reference to... Figure 8 The described measurement reporting component 835 performs this function.

[0220] Figure 15 A flowchart illustrating a method 1500 for supporting UE and network actions based on L3 cell and beam prediction according to one or more aspects of this disclosure is shown. The operation of method 1500 may be implemented by a network entity or its components as described herein. For example, the operation of method 1500 may be implemented by, as referenced... Figures 1 to 5 and Figures 10 to 13 The described network entity performs the functions. 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 functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0221] At 1505, the method may include: outputting a first request message, the first request message including a request for reference signal configuration of one or more reference signals associated with one or more beams of at least one of the candidate cells. The operation of 1505 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to... Figure 12 The described request manager 1225 is executed.

[0222] At 1510, the method may include: outputting a message indicating a reference signal configuration for one or more reference signals, at least in part based on a first request message. The operation of 1510 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1510 may be determined by reference to... Figure 12 The reference signal configuration manager 1230 described herein shall be executed.

[0223] At 1515, the method may include: obtaining a measurement report indicating a set of L3 beam measurements, wherein the set of L3 beam measurements is based on a reference signal configuration of one or more reference signals. The operation of 1515 can be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1515 may be determined by reference to... Figure 12 The described measurement report manager 1235 is used to perform this.

[0224] The following provides an overview of the various aspects of this disclosure.

[0225] Aspect 1: A method for wireless communication at a UE, the method comprising: sending a request message to a network entity associated with one or more serving cells, the request message indicating one or more candidate cells predicted by the UE at least in part based on one or more AI-based functionalities or models, wherein the request message indicates a request for configuration of one or more reference signals corresponding to the one or more candidate cells; receiving from the network entity a first control message indicating a reference signal configuration of one or more reference signals associated with one or more beams, the one or more beams being associated with the one or more candidate cells predicted by the UE; and sending a measurement report indicating a set of measurements of one or more L3 beams, wherein the set of measurements of the one or more L3 beams is at least in part based on the reference signal configuration of the one or more reference signals received via the one or more beams.

[0226] Aspect 2: The method according to aspect 1, the method further comprising: determining a beam set associated with one or more candidate cells predicted by the UE, wherein the beam set is predicted by the UE at least in part based on one or more AI-based functionalities or models; and sending a request to activate the beam set, a request to configure measurements for the beam set, or both, via the request message.

[0227] Aspect 3: According to the method of aspect 2, wherein the beam set includes the one or more beams associated with the one or more candidate cells, and wherein the set of measurements of the one or more L3 beams is based at least in part on the request message.

[0228] Aspect 4: The method according to any one of Aspects 2 and 3, the method further comprising: receiving a second control message from the network entity, the second control message indicating a request to send a request to activate the beam set, a request to configure measurements for the beam set, or a request configuration for both, wherein the request message is sent according to the request configuration.

[0229] Aspect 5: The method according to any one of Aspects 2 to 4, the method further comprising: receiving a third control message from the network entity, the third control message indicating that the beam set has been activated, wherein the third control message is received in response to the request message, and wherein the set of one or more L3 beam measurements is based at least in part on the activation of the beam set.

[0230] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the request message is sent via RRC signaling.

[0231] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the request message is sent via MAC-CE.

[0232] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the request message is sent via uplink control information.

[0233] Aspect 9: A method for wireless communication at a first network entity, the method comprising: outputting a first request message including a request for a reference signal configuration of one or more reference signals associated with one or more beams of at least one of one or more candidate cells; outputting a message indicating the reference signal configuration of the one or more reference signals based at least in part on the first request message; and obtaining a measurement report indicating a set of L3 beam measurements, wherein the set of L3 beam measurements is based at least in part on the reference signal configuration of the one or more reference signals.

[0234] Aspect 10: The method according to aspect 9, the method further comprising: obtaining a second request message, the second request message indicating the one or more candidate cells, wherein the second request message indicates a request for configuration of one or more reference signals corresponding to the one or more candidate cells, and wherein the first request message is at least partially based on the second request message.

[0235] Aspect 11: The method according to aspect 10, the method further comprising: obtaining, via the second request message, a request to activate a beam set associated with the one or more candidate cells, a request to configure measurements for the beam set, or both, wherein the beam set includes the one or more beams associated with the one or more candidate cells, and wherein the set of L3 beam measurements is based at least in part on the second request message; and outputting a message indicating that the beam set has been activated, wherein the set of L3 beam measurements is based at least in part on the activation of the beam set.

[0236] Aspect 12: The method according to any one of Aspects 9 to 11, wherein the first request message includes a handover command message.

[0237] Aspect 13: The method according to any one of Aspects 9 to 11, wherein the first request message includes a signal associated with the F1 interface, a signal associated with the Xn interface, a signal associated with the NG interface, or any combination thereof.

[0238] Aspect 14: The method according to any one of Aspects 9 to 11, wherein the first request message includes a cell group configuration message, or signaling associated with the F1 interface, or any combination thereof.

[0239] Aspect 15: The method according to any one of Aspects 9 to 14, wherein the message includes a handover preparation message.

[0240] Aspect 16: The method according to any one of Aspects 9 to 14, wherein the message includes a signal associated with the Xn interface, a signal associated with the NG interface, or any combination thereof.

[0241] Aspect 17: The method according to any one of Aspects 9 to 15, wherein the message includes a cell group configuration message, or signaling associated with the F1 interface, or any combination thereof.

[0242] Aspect 18: A UE for wireless communication, the UE 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 UE to perform a method according to any one of Aspects 1 to 8.

[0243] Aspect 19: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 1 to 8.

[0244] Aspect 20: 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 8.

[0245] Aspect 21: A first network entity for wireless communication, the first 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, so that the first network entity performs a method according to any one of aspects 9 to 17.

[0246] Aspect 22: A first network entity for wireless communication, the first network entity comprising at least one component for performing the method according to any one of aspects 9 to 17.

[0247] Aspect 23: 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 9 to 17.

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

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

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

[0251] 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 combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

[0252] 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 portions distributed such that the functions are implemented in different physical locations.

[0253] 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 multifunction 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.

[0254] 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".

[0255] 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".

[0256] The term "determine" encompasses a wide range 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.

[0257] 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 numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

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

[0259] 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. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories and configured to cause the UE to: Send a request message to a network entity associated with one or more serving cells, the request message indicating one or more candidate cells, the one or more candidate cells being predicted by the UE at least in part based on one or more AI-based functionalities or models, wherein the request message indicates a request for configuration of one or more reference signals corresponding to the one or more candidate cells; The network entity receives a first control message, the first control message indicating a reference signal configuration for one or more reference signals associated with one or more beams, the one or more beams being associated with one or more candidate cells predicted by the UE; as well as A measurement report is sent, the measurement report indicating a set of one or more layer 3 beam measurements, wherein the set of one or more layer 3 beam measurements is at least in part based on the reference signal configuration of the one or more reference signals received via the one or more beams.

2. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: Determine a set of beams associated with the one or more candidate cells predicted by the UE, wherein the set of beams is predicted by the UE at least in part based on the one or more AI-based functionalities or models; and The request message is sent to request activation of the beam set, to request configuration of measurements for the beam set, or both, wherein the beam set includes one or more beams associated with the one or more candidate cells, and wherein the set of one or more layer 3 beam measurements is based at least in part on the request message.

3. The apparatus of claim 2, wherein the one or more processors are further configured to cause the UE to: A second control message is received from the network entity, the second control message indicating a request to activate the beam set, a request to configure measurements for the beam set, or both, wherein the request message is sent according to the request configuration.

4. The apparatus of claim 2, wherein the one or more processors are further configured to cause the UE to: A third control message is received from the network entity, the third control message indicating that the beam set has been activated, wherein the third control message is received in response to the request message, and wherein the set of one or more layer 3 beam measurements is based at least in part on the activation of the beam set.

5. The apparatus of claim 1, wherein the request message is transmitted via a radio resource control signal.

6. The apparatus of claim 1, wherein the request message is sent via a Media Access Control (MAC) control element.

7. The apparatus of claim 1, wherein the request message is sent via uplink control information.

8. An apparatus for wireless communication at a network entity, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors being coupled to said one or more memories and configured to cause the network entity to: Output a first request message, the first request message including a request for reference signal configuration of one or more reference signals associated with one or more beams of at least one candidate cell in one or more candidate cells; At least in part based on the first request message, output a message indicating the reference signal configuration of the one or more reference signals; as well as A measurement report is obtained, which indicates a set of layer 3 beam measurements, wherein the set of layer 3 beam measurements is at least partially based on the reference signal configuration of the one or more reference signals.

9. The apparatus of claim 8, wherein the one or more processors are further configured to cause the network entity to: A second request message is obtained, the second request message indicating the one or more candidate cells, wherein the second request message indicates a request for configuration of one or more reference signals corresponding to the one or more candidate cells, and wherein the first request message is at least partially based on the second request message.

10. The apparatus of claim 9, wherein the one or more processors are further configured to cause the network entity to: The request is obtained via the second request message for activating a beam set associated with the one or more candidate cells, for configuring measurements for the beam set, or both, wherein the beam set includes the one or more beams associated with the one or more candidate cells, and wherein the set of layer 3 beam measurements is based at least in part on the second request message; and The output indicates that the beam set has been activated, wherein the layer 3 beam measurement of the set is at least partially based on the activation of the beam set.

11. The apparatus of claim 8, wherein the first request message includes a transfer command message.

12. The apparatus of claim 8, wherein the first request message includes a signal associated with the F1 interface, a signal associated with the Xn interface, a signal associated with the NG interface, or any combination thereof.

13. The apparatus of claim 8, wherein the first request message includes a cell group configuration message, or a signal associated with the F1 interface, or any combination thereof.

14. The apparatus of claim 8, wherein the message includes a handover preparation message.

15. The apparatus of claim 8, wherein the message includes a signal associated with the Xn interface, a signal associated with the NG interface, or any combination thereof.

16. The apparatus of claim 8, wherein the message includes a cell group configuration message, or a signal associated with the F1 interface, or any combination thereof.

17. A method for conducting wireless communication at a user equipment (UE), the method comprising: Send a request message to a network entity associated with one or more serving cells, the request message indicating one or more candidate cells, the one or more candidate cells being predicted by the UE at least in part based on one or more AI-based functionalities or models, wherein the request message indicates a request for configuration of one or more reference signals corresponding to the one or more candidate cells; The network entity receives a first control message, the first control message indicating a reference signal configuration for one or more reference signals associated with one or more beams, the one or more beams being associated with one or more candidate cells predicted by the UE; as well as A measurement report is sent, the measurement report indicating a set of one or more layer 3 beam measurements, wherein the set of one or more layer 3 beam measurements is at least in part based on the reference signal configuration of the one or more reference signals received via the one or more beams.

18. The method of claim 17, further comprising: Determine a set of beams associated with one or more candidate cells predicted by the UE, wherein the set of beams is predicted by the UE at least in part based on one or more AI-based functionalities or models; as well as The request message is sent to request activation of the beam set, to request configuration of measurements for the beam set, or both, wherein the beam set includes one or more beams associated with the one or more candidate cells, and wherein the set of one or more layer 3 beam measurements is based at least in part on the request message.

19. The method according to claim 18, further comprising: A second control message is received from the network entity, the second control message indicating a request to send a request to activate the beam set, a request to configure measurements for the beam set, or both, wherein the request message is sent according to the request configuration.

20. The method according to claim 18, further comprising: A third control message is received from the network entity, the third control message indicating that the beam set has been activated, wherein the third control message is received in response to the request message, and wherein the set of one or more layer 3 beam measurements is based at least in part on the activation of the beam set.

Images