WO2026031032A1 - Rapport de faisceau entraîné par un événement pour la surveillance de performances de modèles de prédiction de faisceau - Google Patents

Rapport de faisceau entraîné par un événement pour la surveillance de performances de modèles de prédiction de faisceau

Info

Publication number
WO2026031032A1
WO2026031032A1 PCT/CN2024/110576 CN2024110576W WO2026031032A1 WO 2026031032 A1 WO2026031032 A1 WO 2026031032A1 CN 2024110576 W CN2024110576 W CN 2024110576W WO 2026031032 A1 WO2026031032 A1 WO 2026031032A1
Authority
WO
WIPO (PCT)
Prior art keywords
performance monitoring
measurement values
beams
transmit
actual measurement
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/110576
Other languages
English (en)
Inventor
Hamed Pezeshki
Qiaoyu Li
Mahmoud Taherzadeh Boroujeni
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2024/110576 priority Critical patent/WO2026031032A1/fr
Publication of WO2026031032A1 publication Critical patent/WO2026031032A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B17/00—Monitoring; Testing
    • H04B17/30—Monitoring; Testing of propagation channels
    • H04B17/373—Predicting channel quality or other radio frequency [RF] parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports

Definitions

  • the following relates to wireless communications, including event-driven beam reporting for performance monitoring of beam prediction models.
  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the 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-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems.
  • 4G systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems
  • 5G systems which may be referred to as New Radio (NR) systems.
  • a wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .
  • UE user equipment
  • a method for wireless communications by a user equipment may include generating a set of multiple predicted measurement values for a set of multiple beams, receiving a set of multiple reference signals via the set of multiple beams, and transmitting a performance monitoring report in association with satisfaction of a triggering event, the satisfaction of the triggering event based on the set of multiple predicted measurement values and a set of multiple actual measurement values for the set of multiple beams, the set of multiple actual measurement values based on the set of multiple reference signals.
  • the apparatus may one or more processors.
  • the apparatus may include instructions stored in one or more memories and executable by the one or more processors, individually or collectively, to cause the apparatus to generate a set of multiple predicted measurement values for a set of multiple beams, receive a set of multiple reference signals via the set of multiple beams, and transmit a performance monitoring report in association with satisfaction of a triggering event, the satisfaction of the triggering event based on the set of multiple predicted measurement values and a set of multiple actual measurement values for the set of multiple beams, the set of multiple actual measurement values based on the set of multiple reference signals.
  • the UE may include means for generating a set of multiple predicted measurement values for a set of multiple beams, means for receiving a set of multiple reference signals via the set of multiple beams, and means for transmitting a performance monitoring report in association with satisfaction of a triggering event, the satisfaction of the triggering event based on the set of multiple predicted measurement values and a set of multiple actual measurement values for the set of multiple beams, the set of multiple actual measurement values based on the set of multiple reference signals.
  • a non-transitory computer-readable medium storing code for wireless communications is described.
  • the code may include instructions executable by one or more processors to generate a set of multiple predicted measurement values for a set of multiple beams, receive a set of multiple reference signals via the set of multiple beams, and transmit a performance monitoring report in association with satisfaction of a triggering event, the satisfaction of the triggering event based on the set of multiple predicted measurement values and a set of multiple actual measurement values for the set of multiple beams, the set of multiple actual measurement values based on the set of multiple reference signals.
  • transmitting the performance monitoring report may include operations, features, means, or instructions for transmitting the performance monitoring report in response to the satisfaction of the triggering event including a first beam corresponding to a highest actual measurement value of the set of multiple actual measurement values being excluded from a subset of beams of the set of multiple beams, where the subset of beams may be associated with a subset of highest predicted measurement values of the set of multiple predicted measurement values.
  • transmitting the performance monitoring report may include operations, features, means, or instructions for transmitting the performance monitoring report in response to the satisfaction of the triggering event including a first beam corresponding to a highest predicted measurement value of the set of multiple predicted measurement values being excluded from a subset of beams of the set of multiple beams, where the subset of beams may be associated with a subset of highest actual measurement values of the set of multiple actual measurement values.
  • transmitting the performance monitoring report may include operations, features, means, or instructions for transmitting the performance monitoring report in response to the satisfaction of the triggering event including an actual measurement value of the set of multiple actual measurement values being different by at least a threshold from a highest actual measurement value of the set of multiple actual measurement values, where the actual measurement value corresponds to a beam of the set of multiple beams associated with a highest predicted measurement value of the set of multiple predicted measurement values.
  • transmitting the performance monitoring report may include operations, features, means, or instructions for transmitting the performance monitoring report in response to the satisfaction of the triggering event including a first highest actual measurement value from among a subset of actual measurement values of the set of multiple actual measurement values being different by at least a threshold from a second highest actual measurement value of the set of multiple actual measurement values, where the subset of actual measurement values corresponds to a subset of beams of the set of multiple beams associated with a subset of highest predicted measurement values of the set of multiple predicted measurement values.
  • transmitting the performance monitoring report may include operations, features, means, or instructions for transmitting the performance monitoring report in response to the satisfaction of the triggering event including a highest predicted measurement value of the set of multiple predicted measurement values being different by at least a threshold from a highest actual measurement value of the set of multiple actual measurement values.
  • transmitting the performance monitoring report may include operations, features, means, or instructions for transmitting the performance monitoring report in response to the satisfaction of the triggering event including a highest actual measurement value of the set of multiple actual measurement values being different by at least a threshold from each of a subset of highest predicted measurement values of the set of multiple predicted measurement values.
  • transmitting the performance monitoring report may include operations, features, means, or instructions for transmitting the performance monitoring report in response to the satisfaction of the triggering event including a highest predicted measurement value of the set of multiple predicted measurement values being different by at least a threshold from an actual measurement value of the set of multiple actual measurement values, where the highest predicted measurement value and the actual measurement value correspond to a same beam of the set of multiple beams.
  • transmitting the performance monitoring report may include operations, features, means, or instructions for transmitting the performance monitoring report based on a set of multiple triggering events associated with the set of multiple actual measurement values being satisfied exceeding a threshold quantity of triggering events, the set of multiple triggering events including the triggering event.
  • transmitting the performance monitoring report may include operations, features, means, or instructions for transmitting the performance monitoring report based on a set of multiple triggering events being satisfied within a time window exceeding a threshold quantity of triggering events, the set of multiple triggering events including the triggering event.
  • Some examples of the method, apparatuses, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving scheduling information for a set of multiple resources associated with transmission of performance monitoring reports and transmitting the performance monitoring report via a resource of the set of multiple resources.
  • Some examples of the method, apparatuses, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving scheduling information for a set of multiple resources associated with transmission of performance monitoring reports, transmitting an indication that the UE will transmit the performance monitoring report via a resource of the set of multiple resources, and transmitting the performance monitoring report via the resource of the set of multiple resources in accordance with the indication.
  • Some examples of the method, apparatuses, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting a beam prediction report that indicates one or more of the set of multiple predicted measurement values, where the beam prediction report includes the indication that the UE will transmit the performance monitoring report.
  • Some examples of the method, apparatuses, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, in association with the satisfaction of the triggering event, a request for a resource for the performance monitoring report, receiving, in response to the request, a grant for the resource, and transmitting the performance monitoring report via the resource in accordance with the grant.
  • Some examples of the method, apparatuses, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting a beam prediction report that indicates one or more of the set of multiple predicted measurement values, where the beam prediction report includes the request for the resource.
  • Some examples of the method, apparatuses, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting the performance monitoring report via a medium access control (MAC) control element via a physical uplink shared channel resource.
  • MAC medium access control
  • transmitting the performance monitoring report may include operations, features, means, or instructions for transmitting an indication of one or more of the set of multiple actual measurement values.
  • transmitting the performance monitoring report may include operations, features, means, or instructions for transmitting an indication of the triggering event.
  • Some examples of the method, apparatuses, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting a beam prediction report that indicates one or more of the set of multiple predicted measurement values, where the beam prediction report includes an indication of the satisfaction of the triggering event.
  • FIG. 1 shows an example of a wireless communications system that supports event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • FIG. 2 shows examples of beam prediction timelines that supports event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • FIG. 3 shows an example of a wireless communications system that supports event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • FIG. 4 shows an example of a process flow that supports event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • FIG. 5 shows an example of a machine learning process that supports event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • FIGs. 6 and 7 show block diagrams of devices that support event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • FIG. 8 shows a block diagram of a communications manager that supports event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • FIG. 9 shows a diagram of a system including a device that supports event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • FIG. 10 shows a flowchart illustrating methods that support event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • a user equipment may support artificial intelligence (AI) and/or machine learning (ML) -based models and/or functionalities, such as for beam prediction.
  • AI artificial intelligence
  • ML machine learning
  • Such a UE may collect data measurements (e.g., reference signal received power (RSRP) measurements, signal-to-interference-plus-noise-ratio (SINR) measurements, channel impulse response (CIR) measurements, or the like) for one or more directional beams based on measurements of reference signals (e.g., synchronization system blocks (SSBs) , channel state information (CSI) reference signals (CSI-RSs) , or other reference signals) .
  • reference signals e.g., synchronization system blocks (SSBs) , channel state information (CSI) reference signals (CSI-RSs) , or other reference signals
  • a UE may measure signals (e.g., SSBs or CSI-RSs) received via directional beams.
  • the UE may train a given AI/ML model/functionality using measurements of a first set of beams of a network entity to predict measurements for a set of second, future beams of the network entity.
  • a trained AI/ML model/functionality may use measurements of a third set of beams to predict measurements for a fourth set of beams, which may be a process referred to as beam inference.
  • inference may refer to one or more processes of inputting data to a trained AI/ML model to make predictions.
  • the beams of the network entity whose measurements are predicted or output from the AI/ML model may be referred to as a set A beams and the beams of the network entity whose measurements are input to the AI/ML model (e.g., the second set of beams or the fourth set of beams, which may correspond to the same set of beams) may be referred to as set B beams.
  • the UE may use an AI or ML model to determine which beam of the Set A beams is most likely (e.g., has the highest probability) to have a best (e.g., highest) Layer 1 RSRP (L1-RSRP) value.
  • a Layer 1 beam measurement may refer to the measurement of a beam in the physical layer (e.g., layer 1) .
  • a layer 1 beam measurement may be a measured RSRP, SINR, or CIR of a reference signal received via a given beam.
  • a layer 1 beam prediction may refer to a layer 1 measurement value predicted for a beam (e.g., a set A beam) based on actual measurements of one or more beams (e.g., Set B beams) .
  • the Set A beam predicted measurement values may be made for different beams (e.g., spatial predictions) than the Set B beams or for future measurements (e.g., future temporal predictions) .
  • the UE may transmit a beam prediction report to a network entity which may indicate the predicted beam measurement values.
  • the network entity may determine to communicate with the UE via one or more beams based on the report (e.g., based on respective predicted beam measurement values being above or below a threshold) .
  • the UE may train a given AI/ML model using measurements of reference signals, but channel conditions may change over time. Due to changing channel conditions, the accuracy of the AI/ML predicted measurements may change over time. For example, the network may deactivate beam prediction if the accuracy of the beam predictions falls below a performance metric. To determine the accuracy of the beam predictions, the UE may generate measurements of reference signals received via the Set A beams for comparison to the predicted measurements for the Set A beams.
  • the performance monitoring report may include the generated measurements of the reference signals received via the Set A beams, which the network entity may compare to reported predicted measurements for the Set A beams.
  • the performance monitoring report may include UE determined performance metrics (e.g., the UE may compare the generated measurements of the reference signals received via the Set A beams to the UE generated predicted measurements for the Set A beams) .
  • Defining the events that trigger performance monitoring reporting may reduce signaling overhead and/or interference by limiting transmission of performance monitoring reports to scenarios where the AI/ML model performance for beam prediction is not favorable (e.g., is inaccurate, indicating the AI/ML model should be switched, retrained, or deactivated) .
  • triggering events may be based on beam prediction accuracy, the differences between actual measurements of the reference signals received via the Set A beams, or the differences between actual measurements of the reference signals received via the Set A beams and the predicted measurements of the Set A beams.
  • performance monitoring reporting may be triggered by the occurrence of multiple triggering events (e.g., in a same set of reference signals or over time) .
  • aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to beam prediction timelines, process flows, machine learning processes, apparatus diagrams, system diagrams, and flowcharts that relate to event-driven beam reporting for performance monitoring of beam prediction models.
  • FIG. 1 shows an example of a wireless communications system 100 that supports event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • the wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network entities 105) , one or more UEs 115, and a core network 130.
  • the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-A Pro
  • NR New Radio
  • the network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities.
  • a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature.
  • network entities 105 and UEs 115 may wirelessly communicate via communication link (s) 125 (e.g., a radio frequency (RF) access link) .
  • a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link (s) 125.
  • the coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .
  • RATs radio access technologies
  • the UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times.
  • the UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1.
  • the UEs 115 described herein may be capable of supporting communications with various types of devices in the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network entities 105) , as shown in FIG. 1.
  • a node of the wireless communications system 100 which may be referred to as a network node, or a 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, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein.
  • a node may be a UE 115.
  • a node may be a network entity 105.
  • a first node may be configured to communicate with a second node or a third node.
  • the first node may be a UE 115
  • the second node may be a network entity 105
  • the third node may be a UE 115.
  • the first node may be a UE 115
  • the second node may be a network entity 105
  • the third node may be a network entity 105.
  • the first, second, and third nodes may be different relative to these examples.
  • reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node.
  • disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.
  • network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof.
  • the backhaul communication link (s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof.
  • a UE 115 may communicate with the core network 130 via a communication link 155.
  • One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) .
  • a base station 140 e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred
  • a network entity 105 may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network entity (e.g., a network entity 105 or a single RAN node, such as a base station 140) .
  • a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105) , such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) .
  • a disaggregated architecture e.g., a disaggregated base station architecture, a disaggregated RAN architecture
  • a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105) , such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by
  • a network entity 105 may include one or more of a central unit (CU) , such as a CU 160, a distributed unit (DU) , such as a DU 165, a radio unit (RU) , such as an RU 170, a RAN Intelligent Controller (RIC) , such as an RIC 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, such as an SMO system 180, or any combination thereof.
  • a central unit such as a CU 160
  • DU distributed unit
  • RU such as an RU 170
  • a RAN Intelligent Controller (RIC) such as an RIC 175
  • a Near-Real Time RIC Near-RT RIC
  • Non-RT RIC Non-Real Time RIC
  • SMO Service Management and Orchestration
  • An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) .
  • One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) .
  • one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • the split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof
  • a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack.
  • the CU 160 may host upper protocol layer (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaptation protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) .
  • RRC Radio Resource Control
  • SDAP service data adaptation protocol
  • PDCP Packet Data Convergence Protocol
  • the CU 160 may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs) , or some combination thereof, and the DUs 165, RUs 170, or both may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access control (MAC) layer
  • RLC radio link control
  • MAC medium access control
  • a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack.
  • the DU 165 may support one or multiple different cells (e.g., via one or multiple different RUs, such as an RU 170) .
  • a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) .
  • a CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
  • CU-CP CU control plane
  • CU-UP CU user plane
  • a CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) .
  • a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.
  • infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130) .
  • IAB network architecture e.g., to a core network 130
  • one or more of the network entities 105 may be partially controlled by each other.
  • the IAB node (s) 104 may be referred to as a donor entity or an IAB donor.
  • a DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network entity 105 or base station 140 (such as a donor network entity or a donor base station) .
  • the one or more donor entities may be in communication with one or more additional devices (e.g., IAB node (s) 104) via supported access and backhaul links (e.g., backhaul communication link (s) 120) .
  • IAB node (s) 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DUs 165) of a coupled IAB donor.
  • IAB-MT IAB mobile termination
  • An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node (s) 104 used for access via the DU 165 of the IAB node (s) 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) .
  • the IAB node (s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node (s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) .
  • one or more components of the disaggregated RAN architecture e.g., the IAB node (s) 104 or components of the IAB node (s) 104) may be configured to operate according to the techniques described herein.
  • one or more components of the disaggregated RAN architecture may be configured to support test as described herein.
  • some operations described as being performed by a UE 115 or a network entity 105 may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180) .
  • a UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples.
  • a UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer.
  • PDA personal digital assistant
  • a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.
  • WLL wireless local loop
  • IoT Internet of Things
  • IoE Internet of Everything
  • MTC machine type communications
  • the UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • devices such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • the UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link (s) 125 (e.g., one or more access links) using resources associated with one or more carriers.
  • the term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link (s) 125.
  • a carrier used for the communication link (s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR) .
  • 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 that coordinates operation for the carrier, user data, or other signaling.
  • the wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation.
  • a UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration.
  • Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.
  • Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105.
  • the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105 may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network entities 105) .
  • a network entity 105 e.g., a base station 140, a CU 160, a DU 165, a RU 170
  • another device e.g., directly or via one or more other network entities, such as one or more of the network entities 105
  • a carrier may have acquisition signaling or control signaling that coordinates operations for other carriers.
  • a carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN) ) and may be identified according to a channel raster for discovery by the UEs 115.
  • E-UTRA evolved universal mobile telecommunication system terrestrial radio access
  • a carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different RAT) .
  • the communication link (s) 125 of the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions.
  • Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
  • a carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100.
  • the carrier bandwidth may be one of a set of bandwidths for carriers of a particular RAT (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) .
  • Devices of the wireless communications system 100 e.g., the network entities 105, the UEs 115, or both
  • the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths.
  • each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
  • Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) .
  • MCM multi-carrier modulation
  • OFDM orthogonal frequency division multiplexing
  • DFT-S-OFDM discrete Fourier transform spread OFDM
  • a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related.
  • the quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication.
  • a wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.
  • One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing ( ⁇ f) and a cyclic prefix.
  • a carrier may be divided into one or more BWPs having the same or different numerologies.
  • a UE 115 may be configured with multiple BWPs.
  • a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
  • Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) .
  • Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .
  • SFN system frame number
  • Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration.
  • a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots.
  • each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing.
  • Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) .
  • a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f ) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
  • a subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) .
  • TTI duration e.g., a quantity of symbol periods in a TTI
  • the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
  • Physical channels may be multiplexed for communication using a carrier according to various techniques.
  • a physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.
  • a control region e.g., a control resource set (CORESET)
  • CORESET control resource set
  • One or more control regions may be configured for a set of the UEs 115.
  • one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner.
  • An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size.
  • Search space sets may include common search space sets configured for sending control information to UEs 115 (e.g., one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (e.g., a specific UE) .
  • a network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof.
  • the term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) ) .
  • a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates.
  • Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105.
  • a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.
  • a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell.
  • a small cell may be associated with a network entity 105 operating with lower power (e.g., a base station 140 operating with lower power) relative to a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells.
  • Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) .
  • a network entity 105 may support one or more cells and may also support communications via the one or more cells using one or multiple component carriers.
  • a network entity 105 may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110.
  • coverage areas 110 e.g., different coverage areas
  • coverage areas 110 may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., a network entity 105) .
  • overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network entities 105) .
  • the wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.
  • the wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof.
  • the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) .
  • the UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions.
  • Ultra-reliable communications may include private communication 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 prioritization of services, and such services may be used for public safety or general commercial applications.
  • the terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
  • a UE 115 may be configured to support communicating directly with other UEs (e.g., one or more of the UEs 115) via a device-to-device (D2D) communication link, such as a D2D communication link 135 (e.g., in accordance with a peer-to-peer (P2P) , D2D, or sidelink protocol) .
  • D2D device-to-device
  • P2P peer-to-peer
  • one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105.
  • one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105.
  • groups of the UEs 115 communicating via D2D communications may support a one-to-many (1: M) system in which each UE 115 transmits to one or more of the UEs 115 in the group.
  • a network entity 105 may facilitate the scheduling of resources for D2D communications.
  • D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.
  • the core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions.
  • the core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management function
  • S-GW serving gateway
  • PDN Packet Data Network gateway
  • UPF user plane function
  • the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130.
  • NAS non-access stratum
  • User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions.
  • the user plane entity may be connected to IP services 150 for one or more network operators.
  • the IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
  • IMS IP Multimedia Subsystem
  • the wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) .
  • the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from 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 the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
  • HF high frequency
  • VHF very high frequency
  • the wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands.
  • the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • LAA License Assisted Access
  • LTE-U LTE-Unlicensed
  • NR NR technology
  • an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance.
  • operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA) .
  • Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
  • a network entity 105 e.g., a base station 140, an RU 170
  • a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming.
  • the antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming.
  • one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower.
  • antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations.
  • a network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115.
  • a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations.
  • an antenna panel may support RF beamforming for a signal transmitted via an antenna port.
  • the network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers.
  • Such techniques may be referred to as spatial multiplexing.
  • the multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas.
  • Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords) .
  • Different spatial layers may be associated with different antenna ports used for channel measurement and reporting.
  • MIMO techniques include single-user MIMO (SU-MIMO) , for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) , for which multiple spatial layers are transmitted to multiple devices.
  • SU-MIMO single-user MIMO
  • Beamforming which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device.
  • Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference.
  • the adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device.
  • the adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
  • a network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations.
  • a network entity 105 e.g., a base station 140, an RU 170
  • Some signals e.g., synchronization signals, reference signals, beam selection signals, or other control signals
  • the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission.
  • Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.
  • a transmitting device such as a network entity 105
  • a receiving device such as a UE 115
  • Some signals may be transmitted by a transmitting device (e.g., a network entity 105 or a UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as another network entity 105 or UE 115) .
  • a transmitting device e.g., a network entity 105 or a UE 115
  • a single beam direction e.g., a direction associated with the receiving device, such as another network entity 105 or UE 115
  • the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions.
  • a UE 115 may receive one or more of the signals transmitted by the network entity 105 along different directions and may report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.
  • transmissions by a device may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115) .
  • the UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands.
  • the network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS) , a CSI-RS) , which may be precoded or unprecoded.
  • a reference signal e.g., a cell-specific reference signal (CRS) , a CSI-RS
  • the UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook) .
  • PMI precoding matrix indicator
  • codebook-based feedback e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook
  • these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170)
  • a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device) .
  • a receiving device may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a transmitting device (e.g., a network entity 105) , such as synchronization signals, reference signals, beam selection signals, or other control signals.
  • a transmitting device e.g., a network entity 105
  • a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions.
  • a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal) .
  • the single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions) .
  • receive configuration directions e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions
  • the wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack.
  • communications at the bearer or PDCP layer may be IP-based.
  • An RLC layer may perform packet segmentation and reassembly to communicate via logical channels.
  • a MAC layer may perform priority handling and multiplexing of logical channels into transport channels.
  • the MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency.
  • an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data.
  • a PHY layer may map transport channels to physical channels.
  • a UE 115 may measure a first set of beams ( “Set B beams) and may use measurements of the first set of beams to predict characteristics of a second set of beams ( “Set A beams” ) .
  • a UE 115 may predict which beam of a first set of beams, referred to as set A beams, is a best beam for communicating messages with a network entity 105, where the beam being the best beam may refer to the beam being associated with a channel characteristic (e.g., L1-RSRP) that maximizes or minimizes a metric relative to the other beams of the first set of beams.
  • a channel characteristic e.g., L1-RSRP
  • the UE 115 may measure one or more first channel characteristics of a second set of beams, referred to as set B beams, and may 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 instance, the UE 115 may measure L1-RSRPs of a first set of one or more reference signals received over the second set of beams and may use an ML model to predict L1-RSRPs of the set A beams.
  • a UE 115 and/or a network entity 105 may perform spatial downlink beam prediction for Set A beams using an AI or ML model based on measurement results of Set B beams.
  • the Set B beams may be wide beams (such as SSB beams) while the Set A beams may be narrow beams (such as CSI-RS beams) .
  • the Set B beams may be narrow beams (such as CSI-RS beams) while the Set A beams may be wide beams (such as SSB beams) .
  • a UE 115 may perform temporal downlink beam prediction for Set A beams using an ML model based on historic measurement results of Set B beams.
  • the Set A beams and the Set B beams may be the same beams at different times (e.g., pure temporal beam predictions) .
  • the Set A beams and the Set B beams may be different beams at different times (e.g., temporal and spatial beam predictions) .
  • the UE 115 may transmit a beam prediction report to a network entity 105 which may indicate the predicted beam measurement values.
  • the network entity 105 may determine to communicate with the UE 115 via one or more beams based on the report (e.g., based on respective predicted beam measurement values being above or below a threshold) .
  • the UE 115 may train a given AI/ML model using measurements of reference signals, but channel conditions may change over time. Due to changing channel conditions, the accuracy of the AI/ML predicted measurements may change over time. For example, the network entity 105 may deactivate beam prediction if the accuracy of the beam predictions falls below a performance metric. To determine the accuracy of the beam predictions, the UE 115 may generate measurements of reference signals received via the Set A beams for comparison to the predicted measurements for the Set A beams.
  • Type 1 performance monitoring may involve configuration/signaling from the network entity 105 to the UE 115 for measurement and/or reporting.
  • the UE 115 may send reports to the network entity 105 that indicate measurements generated by the UE 115, and the network entity 105 may calculate performance metrics based on the indicated measurements.
  • the UE 115 in a second option (UE-assisted performance monitoring) the UE 115 may calculate performance metrics and may either report the performance metrics or may report events to the network entity 105 based on the calculated performance metrics.
  • the network entity 105 may indicate life cycle management (LCM) commands to the UE 115 for beam predictions (e.g., whether to deactivate or retrain the AI/ML model) based on the performance metrics and/or events.
  • LCM life cycle management
  • the UE 115 may indicate, request, or report to the network entity 105 for performance monitoring of the beam prediction.
  • the network entity 105 may provide configuration/signaling to the UE 115 for performance monitoring and/or reporting.
  • the UE 115 may make LCM decisions such as AI/ML model selection, AI/ML model activation, AI/ML model deactivation, AI/ML model switching, or AI/ML model fallback (to a default AI/ML model or set of parameters) .
  • the UE 115 may transmit capability signaling to the network entity 105 that indicates that the UE 115 has an AI/ML model capability (e.g., to perform beam prediction using the AI/ML model) .
  • the UE 115 may request dedicated reference signals for performance monitoring of beam predictions at the UE 115.
  • the network entity 105 may transmit dedicated reference signals for beam prediction performance monitoring based on the request from the UE 115.
  • the dedicated reference signals for beam prediction performance monitoring may be periodic, semi-periodic, or aperiodic.
  • the UE 115 may compute monitoring key performance indicators (KPIs) based on the dedicated reference signals and the AI/ML inferences generated by the UE 115 (e.g., the AI/ML inference outcome for Set A beams based on measurements of Set B beams) .
  • KPIs key performance indicators
  • the UE 115 may send information about the monitoring KPIs to the network entity 105.
  • the network entity 105 may send information about LCM operation for the UE-side AI/ML model.
  • the UE 115 may subsequently perform LCM operations (e.g., AI/ML model selection/activation/deactivation/switching/fallback) based on the information provided by the network entity 105.
  • the UE 115 may subsequently transmit information to the network entity 105 about the executed LCM operation at the UE 115.
  • the UE 115 may transmit a measurement report to the network entity 105 based on the dedicated reference signals for beam prediction performance monitoring.
  • the network entity 105 may evaluate the AI/ML model performance based on the measurement report.
  • the network entity 105 may evaluate the AI/ML model by comparing the actual measurements of the dedicated reference signals in the measurement report to predicted measurements reported by the UE 115 in a beam prediction report.
  • the measurement report may indicate L1-RSRP and/or reference signal indices for the dedicated reference signals.
  • the measurement report may be configured or triggered by the network entity 105.
  • the network entity 105 may send information about LCM operation for the UE-side AI/ML model.
  • the UE 115 may subsequently perform LCM operations (e.g., AI/ML model selection/activation/deactivation/switching/fallback) based on the information provided by the network entity 105.
  • LCM operations e.g., AI/ML model selection/activation/deactivation/switching/fallback
  • the UE 115 may subsequently transmit information to the network entity 105 about the executed LCM operation at the UE 115.
  • the UE 115 may compute monitoring KPIs or may determine the occurrence of triggering events based on the dedicated reference signals and the AI/ML inferences generated by the UE 115 (e.g., the AI/ML inference outcome for Set A beams based on measurements of Set B beams) .
  • the UE 115 may send information about the monitoring KPIs or the triggering event occurrences to the network entity 105 in a beam prediction performance monitoring report.
  • the network entity 105 may evaluate the AI/ML model performance based on the beam prediction performance monitoring report. Based on the evaluated performance of the AI/ML model, the network entity 105 may send information about LCM operation for the UE-side AI/ML model.
  • the UE 115 may subsequently perform LCM operations (e.g., AI/ML model selection/activation/deactivation/switching/fallback) based on the information provided by the network entity 105.
  • LCM operations e.g., AI/ML model selection/activation/deactivation/switching/fallback
  • the UE 115 may subsequently transmit information to the network entity 105 about the executed LCM operation at the UE 115.
  • a common aspect may be that the UE 115 sends a beam prediction performance monitoring report to the network entity 105.
  • the beam prediction performance monitoring report may include raw measurements for the set A beams (e.g., L1-RSRP and/or reference signal indices) .
  • the contents of the beam prediction performance monitoring report may depend on the performance monitoring metric that is computed at the UE-side (e.g., an L1-RSRP difference) .
  • the UE 115 may send a performance monitoring report (e.g., a beam prediction performance monitoring report) to the network entity 105 based on the occurrence of a triggering event (or multiple triggering events) .
  • a triggering event (or multiple triggering events) may be standardized or may be configured by the network entity 105 to the UE 115 (e.g., via control signaling such as RRC signaling) .
  • the triggering events may be based on performance monitoring metrics.
  • the framework of UE-initiated event-driven beam reporting may be leveraged for the purpose of beam prediction performance monitoring, in which the performance monitoring reports may be transmitted in scenarios where the AI/ML model performance for beam prediction is not favorable (e.g., is inaccurate, indicating the AI/ML model should be switched, retrained, or deactivated) .
  • FIG. 2 shows an example of a beam prediction timeline 200 and a beam prediction timeline 220 that support event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • the beam prediction timeline 200 and the beam prediction timeline 220 may implement or may be implemented by aspects of the wireless communications system 100.
  • a UE 115 may generate predicted measurement values 210 for set A beams (e.g., a predicted measurement value 210-a for a first set A beam, a predicted measurement value 210-b for a second set A beam, a predicted measurement value 210-c for a third set A beam, a predicted measurement value 210-d for a fourth set A beam, and a predicted measurement value 210-e for a fifth set A beam) based on measurement values 205 of reference signals received via set B beams (e.g., a measurement value 205-a for a first set B beam, a measurement value 205-b for a second set B beam, a measurement value 205-c for a third set B beam, a measurement value 205-d for a fourth set B beam, and a measurement value 205-e for a fifth set B beam) .
  • predicted measurement values 210 for set A beams e.g., a predicted measurement value 210-a for a first set A beam, a predicted measurement
  • the UE 115 may receive beam prediction management (BPM) reference signals (BPM-RSs) transmitted via the set A beams and may generate measurement values 215 (e.g., a measurement value 215-a for a first set A beam, a measurement value 215-b for a second set A beam, a measurement value 215-c for a third set A beam, a measurement value 215-d for a fourth set A beam, and a measurement value 215-e for a fifth set A beam) based on the received BPM-RSs to monitor the accuracy of the predicted measurement values 210.
  • BPM beam prediction management
  • BPM-RSs beam prediction management reference signals
  • the UE 115 may compare the predicted measurement values 210 for the set A beams to the measurement values 215 based on measurements of the BPM-RSs received via the set A beams.
  • the BPM-RSs may be periodically configured (e.g., at time t-2, time t-2, time t+1, and time t+2) and/or the UE 115 may generate periodic predicted measurement values (e.g., for time t-3, time t, and time t+3) .
  • a UE 115 may perform spatial downlink beam prediction for Set A beams using an AI or ML model based on measurement results of Set B beams.
  • the Set B beams may be wide beams (such as SSB beams) while the Set A beams may be narrow beams (such as CSI-RS beams) .
  • the UE 115 may generate predicted measurement values 230 for set A beams (e.g., a predicted measurement value 230-a for a first set A beam, a predicted measurement value 230-b for a second set A beam, a predicted measurement value 230-c for a third set A beam, a predicted measurement value 230-d for a fourth set A beam, and a predicted measurement value 230-e for a fifth set A beam) based on measurement values 225 of reference signals received via set B beams (e.g., a measurement value 225-a for a first set B beam, a measurement value 225-b for a second set B beam, and a measurement value 225-c for a third set B beam) .
  • predicted measurement values 230 for set A beams e.g., a predicted measurement value 230-a for a first set A beam, a predicted measurement value 230-b for a second set A beam, and a measurement value 225-c for a third set B beam
  • the set A beams may be narrower than the set B beams.
  • the UE 115 may receive BPM-RSs transmitted via the set A beams and may generate measurement values 235 (e.g., a measurement value 235-a for a first set A beam, a measurement value 235-b for a second set A beam, a measurement value 235-c for a third set A beam, a measurement value 235-d for a fourth set A beam, and a measurement value 205-e for a fifth set A beam) based on the received BPM-RSs to monitor the accuracy of the predicted measurement values 230.
  • the UE 115 may compare the predicted measurement values 230 for the set A beams to the measurement values 235 based on measurements of the BPM-RSs received via the set A beams.
  • FIG. 3 shows an example of a wireless communications system 300 that supports event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • the wireless communications system 300 may implement or may be implemented by aspects of the wireless communications system 100, the beam prediction timeline 200, or the beam prediction timeline 220.
  • the wireless communications system 300 may include a UE 115-a, which may be an example of a UE 115 as described herein.
  • the wireless communications system 300 may include a network entity 105-a, which may be an example of a network entity 105 as described herein.
  • the UE 115-a may communicate with the network entity 105-a using a communication link 125-a.
  • the communication link 125-a may be an example of an NR or LTE link between the UE 115-a and the network entity 105-a.
  • the communication link 125-a may include a bi-directional link that enable both uplink and downlink communications.
  • the UE 115-a may transmit uplink signals 305 (e.g., uplink transmissions) , such as uplink control signals or uplink data signals, to the network entity 105-a using the communication link 125-a and the network entity 105-a may transmit downlink signals 310 (e.g., downlink transmissions) , such as downlink control signals or downlink data signals, to the UE 115-a using the communication link 125-a.
  • uplink signals 305 e.g., uplink transmissions
  • downlink signals 310 e.g., downlink transmissions
  • the network entity 105-a may transmit a set of reference signals 315 (e.g., CSI-RSs or SSBs) to the UE 115-a.
  • the network entity 105-a may use beamforming techniques to transmit the set of reference signals 315 via a set of transmit beams 375 (e.g., a beam 375-a, a beam 375-b, and a beam 375-c as shown in FIG. 3) .
  • the UE 115-a may receive the set of reference signals 315 via a set of receive beams 380 (e.g., a beam 380-a, a beam 380-b, and a beam 380-c as shown in FIG.
  • the UE 115-a may perform measurements on the set of reference signals 315 to obtain measurement values 320 for the set B beams (e.g., for the set of receive beams 380) .
  • the UE 115-a may generate, for example, using a beam prediction AI/ML model 325, predicted measurement values 330 for the set A beams (e.g., the set of receive beams 380 at a future time, or a set of narrower beams) based on the measurement values 320.
  • the UE 115-a may transmit a predicted beam report 335 to the network entity 105 which may indicate the predicted measurement values 330 for the set A beams.
  • the network entity 105-a may determine to communicate with the UE 115-a via one or more beams of the set of transmit beams 375 based on the predicted beam report 335 (e.g., based on respective predicted beam measurement values being above or below a threshold) .
  • the UE 115-a may train the AI/ML model 325 using measurements of reference signals, but channel conditions may change over time. Due to changing channel conditions, the accuracy of the predicted measurements generated by the AI/ML model 325 may change over time. Accordingly, the UE 115-a may transmit performance monitoring reports 345 to the network entity 105-a for the AI/ML model 325 based on triggering events related to monitoring of the accuracy of the predicted measurement values 330.
  • the network entity 105-a may transmit BPM-RSs 340 via the set A beams.
  • the UE 115-a may perform measurements on the BPM-RSs 340 to obtain measurement values 370 for the set A beams.
  • the UE 115-a may compare the measurement values 370 for the set A beams to the predicted measurement values for the set A beams to determine whether one or more triggering events occurred for transmission of a performance monitoring report 345.
  • triggering events may be based on beam prediction accuracy.
  • a triggering event type 1 may be that the top-1 measured beam (e.g., the set A beam with the highest measurement value 370 based on the BPM-RSs 340) is not among the top-K predicted beams (e.g., the K set A beams with the highest predicted measurement values 330) .
  • a triggering event type 2 may be that the top-1 predicted beam (e.g., the set A beam with the highest predicted measurement value 330) is not among the top-K measured beams (e.g., the K set A beams with the highest measurement values 370 based on the BPM-RSs 340) .
  • the network entity 105-a may configure the quantity K for triggering event type 1 and/or triggering event type 2 in control signaling 350 (e.g., RRC signaling or downlink control information (DCI) ) .
  • control signaling 350 e.g., RRC signaling or downlink control information (DCI)
  • triggering events may be based on the difference of L1-RSRPs.
  • a triggering event type 3 may be that the L1-RSRP of the top-1 predicted beam (e.g., the measured L1-RSRP that corresponds to the beam that had the highest predicted measurement value 330, where the measurement values 370 are L1-RSRPs based on the BPM-RSs 340) is NOT within x 3 dB of the Top-1 measured L1-RSRP (e.g., the L1-RSRP that is the highest among the L1-RSRPs of the measurement values 370 based on the BPM-RSs 340) .
  • a triggering event type 4 may be that the highest measured L1-RSRP of the Top-K predicted beams (e.g., the highest measured L1-RSRP from among the K set A beams having the highest predicted measurement values 330, where the measurement values 370 are L1-RSRPs) is NOT within x 4 dB of the Top-1 measured L1-RSRP (e.g., the L1-RSRP that is the highest among the L1-RSRPs of the measurement values 370 based on the BPM-RSs 340, where the measurement values 370 are L1-RSRPs) .
  • triggering events may be based on the difference of measured and predicted L1-RSRPs.
  • a triggering event type 5 may be that the predicted L1-RSRP of the Top-1 predicted beam (e.g., the L1-RSRP that is the highest among the L1-RSRPs of the predicted measurement values 330, where the predicted measurement values 330 are L1-RSRPs) is NOT within x 5 dB of the Top-1 measured L1-RSRP (e.g., the L1-RSRP that is the highest among the L1-RSRPs of the measurement values 370 based on the BPM-RSs 340, where the measurement values 370 are L1-RSRPs) .
  • a triggering event type 6 may be that highest predicted L1-RSRP of Top-K predicted beams (e.g., the predicted highest K L1-RSRPs of the predicted measurement values 330, where the predicted measurement values 330 are L1-RSRPs) are NOT within x 6 dB of the Top-1 measured L1-RSRP (e.g., the L1-RSRP that is the highest among the L1-RSRPs of the measurement values 370 based on the BPM-RSs 340, where the measurement values 370 are L1-RSRPs) .
  • a triggering event type 7 may be that the predicted L1-RSRP of the Top-1 predicted beam (e.g., the L1-RSRP that is the highest among the L1-RSRPs of the predicted measurement values 330, where the predicted measurement values 330 are L1-RSRPs) is NOT within x 7 dB of the measured L1-RSRP of the Top-1 predicted beam (e.g., the measured L1-RSRP that corresponds to the beam that had the highest predicted measurement value 330, where the measurement values 370 are L1-RSRPs based on the BPM-RSs 340) .
  • 4, 5, 6, and 7, x 3 , x 4 , x 5 , x 6 , and x 7 may be configured by the network entity 105-a (for example, via the control signaling 350) .
  • 4, 5, 6, and 7, x 3 , x 4 , x 5 , x 6 , and x 7 may be functions of the Top-1 (e.g., the highest) L1-RSRP from among the measurement values 370.
  • the UE 115-a may be triggered to transmit a performance monitoring report 345 based on a single occurrence of a triggering event (e.g., any one of the triggering event types 1, 2, 3, 4, 5, 6, or 7) .
  • the UE 115-a may be triggered to transmit a performance monitoring report 345 based on the occurrence of at least two of the triggering events (e.g., two or more of the triggering event types 1, 2, 3, 4, 5, 6, or 7) .
  • triggering events other than the triggering event types 1, 2, 3, 4, 5, 6, or 7 may be defined (e.g., based on predicted or measured SINRs or other predicted or actual measurements) .
  • UE 115-a may be triggered to transmit a performance monitoring report 345 for each performance monitoring instance if a defined triggering event (e.g., one or more of the triggering event types 1, 2, 3, 4, 5, 6, or 7) occurs in that monitoring instance.
  • a performance monitoring instance may be the reception of a set of the BPM-RSs 340 via the set A beams.
  • UE 115-a may be triggered to transmit a performance monitoring report 345 if within a (configurable) time window, the quantity of occurrences of a defined triggering event (e.g., one or more of the triggering event types 1, 2, 3, 4, 5, 6, or 7) exceeds a threshold quantity N.
  • the network entity 105-a may configure the threshold quantity N (for example, via the control signaling 350) .
  • performance monitoring reports 345 may be conveyed via preconfigured uplink control information (UCI) resources on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) .
  • UCI uplink control information
  • the network entity 105-a may configure and/or activate periodic or semi-persistent resources for CSI reporting (e.g., via the control signaling 350) .
  • the UE 115-a may skip transmission of a performance monitoring report 345 in the corresponding periodic or semi-persistent resource for that performance monitoring instance or duration.
  • the UE 115-a may not transmit a scheduling request for a resource for a performance monitoring report 345 as the resources may be periodically or semi-persistently scheduled.
  • Option 0 may save power at the UE 115-a due to skipping uplink transmissions and may reduce interference via reduced signaling.
  • Option 0 may increase resource overhead as the network entity 105 may be unable to reallocate resources when the UE 115-a skips transmission of a performance monitoring report 345 in the corresponding periodic or semi-persistent resource. Further, option 0 may demand the network entity 105-a to reserve CSI reporting resources for performance monitoring reports 345 and may demand the network entity 105-a to blindly detect the presence of a performance monitoring report 345 in a given allocated resource.
  • the performance monitoring report 345 is multiplexed by another report (e.g., a report of inference results for spatial beam prediction) , then skipping the performance monitoring reports 345 in some instances may be challenging and rules may be defined regarding how to interpret the multiplexed report as the data corresponding to the performance monitoring reports 345 may be skipped.
  • another report e.g., a report of inference results for spatial beam prediction
  • performance monitoring reports 345 may be conveyed via an indication 365 in addition to preconfigured UCI resources.
  • the UE 115-a may transmit an indication 365 (e.g., via a first PUCCH, and the indication 365 may be a one-bit or multi-bit indication) that notifies the network entity 105-a whether a second uplink channel (e.g., a PUCCH or PUSCH) will convey the performance monitoring report 345 (e.g., based on the occurrence of a triggering event) .
  • a second uplink channel e.g., a PUCCH or PUSCH
  • a multi-bit indication for the indication 365 may be utilized to differentiate between multiple events (e.g., which type of triggering event occurred) and/or which type of performance monitoring is used (e.g., network-side or UE-assisted) and accordingly, the type of contents of the performance monitoring report 345.
  • the UE 115-a may transmit the performance monitoring report 345 in the corresponding uplink channel (e.g., a PUCCH or PUSCH) , where the resources for the corresponding uplink channel may be periodically or semi-persistently configured.
  • the network entity 105-a may reallocate the corresponding uplink resources to another UE 115 or for another uplink communication by the UE 115-a. Further, the network entity 105-a may avoid blindly decoding an uplink channel for a performance monitoring report 345 if the network entity 105-a does not receive the indication 365.
  • performance monitoring reports 345 may be conveyed via dynamically scheduled UCI resources.
  • the UE 115-a may transmit a scheduling request 355 (e.g., via a one-bit or multi-bit indication in a PUCCH) to request a resource for a second uplink channel to convey a performance monitoring report 345.
  • a multi-bit indication for the indication 365 may be utilized to differentiate between multiple events (e.g., which type of triggering event occurred) and/or which type of performance monitoring is used (e.g., network-side or UE-assisted) and accordingly, the type of contents of the performance monitoring report 345.
  • the network entity 105-a may transmit a grant 360 (e.g., via a DCI) that schedules the uplink resource for the UE 115-a to transmit the performance monitoring report 345.
  • the UE 115-a may transmit the performance monitoring reports 345 using the scheduled uplink resource (e.g., via UCI on a dynamically granted PUCCH or a dynamically granted PUSCH) .
  • Option 2 may not involve dedicated periodic or semi-persistent resources for transmission of performance monitoring reports 345, and accordingly may involve reduced resource overhead as compared to options 0 and 1.
  • Option 2 may involve additional signaling overhead (e.g., for transmission of the scheduling request 355 and the grant 360) .
  • performance monitoring reports 345 may be conveyed via an uplink MAC control element (MAC-CE) transmitted in a PUSCH.
  • MAC-CE uplink MAC control element
  • the UE 115-a may convey the performance monitoring report 345 via the MAC-CE on a PUSCH.
  • an uplink shared channel resource e.g., a PUSCH
  • the UE 115-a may transmit a scheduling request 355 for uplink shared channel resources if a triggering event occurs.
  • the UE 115-a may receive a grant 360 (e.g., via a DCI) that schedules the uplink shared channel resources for the UE 115-a.
  • the UE 115-a may transmit the performance monitoring report 345 via a MAC-CE on a PUSCH transmission in an uplink shared channel resource scheduled by the grant 360.
  • Option 3 may not involve dedicated periodic or semi-persistent resources for transmission of performance monitoring reports 345, and accordingly may involve reduced resource overhead as compared to options 0 and 1.
  • the UE 115-a may indicate whether the UE 115-a will transmit a performance monitoring report 345 in a predicted beam report 335 (e.g., an inference report) .
  • a predicted beam report 335 e.g., an inference report
  • such an indication may be a single bit in the predicted beam report 335. If there are no monitoring reference signals (e.g., BPM-RSs 340) for a given predicted beam report 335, in some examples, the given predicted beam report 335 may not include the single bit to indicate whether the UE 115-a will transmit a performance monitoring report 345.
  • the payload of the predicted beam report 335 may still include such a single bit, but the value of the bit-point the UE 115-a should report may not matter as the bit may be present to maintain a fixed UCI payload size. In such cases where the single bit is present but no monitoring reference signals were present for a given predicted beam report 335. the single bit may be used for additional purposes.
  • the UE 115-a may continue to send “1” in the single bit in the predicted beam reports 335 where no monitoring instances were scheduled to indicate that the UE 115-a has a performance monitoring report 345 from a prior monitoring instance to transmit (e.g., in normal operation a “1” value may refer to the most recent prediction performance monitoring instance with respect to the predicted beam report 335) .
  • the one-bit or multi-bit indication (e.g., the indication 365) may be carried as part of the predicted beam report 335 (e.g., for spatial beam prediction in which case there may be monitoring reference signals for a given prediction performance monitoring instance) .
  • the one-bit or multi-bit indication (e.g., the indication 365) may also be carried as part of the predicted beam report 335 (e.g., for spatial beam prediction in which case there may be monitoring reference signals for a given prediction performance monitoring instance) .
  • a second uplink channel e.g., an aperiodic CSI report
  • the linked second channel for transmission of the performance monitoring report 345 may be reserved (e.g., may not be used by other UEs) .
  • the content of the performance monitoring report 345 may be dependent upon whether the UE 115-a and the network entity 105-a perform network-side performance monitoring or UE-assisted performance monitoring.
  • the performance monitoring report 345 may include measurement results from the resource set for monitoring (e.g., L1-RSRPs and/or reference signal indices for the BPM-RSs 340) .
  • the payload associated with the performance monitoring report 345 may be fixed or variable in size depending on the criterion for determining the quantity of beams to be reported.
  • the Top-1 measured beam already being among the Top-K predicted beams, from the performance monitoring set may indicates that the AI/ML model 325 is performing well, and the UE 115-a may not report the L1-RSRPs and/or reference signal indices (e.g., which may lead to noticeable savings on the uplink payload) .
  • the content of the performance monitoring report 345 may be dependent on the metrics defined for performance monitoring.
  • the L1-RSRP difference may be included in the performance monitoring report 345 for a triggering event type 3 accompanied by the reference signal index and the corresponding L1-RSRP of the Top-1 measured beam from the performance monitoring set.
  • FIG. 4 shows an example of a process flow 400 that supports event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • the process flow 400 may implement or may be implemented by aspects of the wireless communications system 100, the beam prediction timeline 200, the beam prediction timeline 220, or the wireless communications system 300.
  • the process flow 400 may include a UE 115-b, which may be an example of a UE 115 as described herein.
  • the process flow 400 may also include a network entity 105-b, which may be an example of a network entity 105 as described herein.
  • the communications between the network entity 105-b and the UE 115-b may be transmitted in a different order than the example order shown, or the operations performed by the network entity 105-b and the UE 115-b may be performed in different orders or at different times. Some operations may also be omitted from the process flow 400, and other operations may be added to the process flow 400.
  • the UE 115-b may generate a set of multiple predicted measurement values for a set of multiple beams.
  • the UE 115-b may receive a set of multiple reference signals via the set of multiple beams.
  • the UE 115-b may transmit a performance monitoring report in association with satisfaction of a triggering event.
  • the satisfaction of the triggering event may be based on the set of multiple predicted measurement values and a set of multiple actual measurement values for the set of multiple beams, and the set of multiple actual measurement values may be based on reception of the set of multiple reference signals at 410.
  • the UE 115-b may transmit the performance monitoring report in response to the satisfaction of the triggering event being a first beam corresponding to a highest actual measurement value of the set of multiple actual measurement values being excluded from a subset of beams of the set of multiple beams, where the subset of beams are associated with a subset of highest predicted measurement values of the set of multiple predicted measurement values.
  • the satisfied triggering event may be a triggering event type 1.
  • the UE 115-b may transmit the performance monitoring report in response to the satisfaction of the triggering event being a first beam corresponding to a highest predicted measurement value of the set of multiple predicted measurement values being excluded from a subset of beams of the set of multiple beams, where the subset of beams are associated with a subset of highest actual measurement values of the set of multiple actual measurement values.
  • the satisfied triggering event may be a triggering event type 2.
  • the UE 115-b may transmit the performance monitoring report in response to the satisfaction of the triggering event being an actual measurement value of the set of multiple actual measurement values being different by at least a threshold from a highest actual measurement value of the set of multiple actual measurement values, where the actual measurement value corresponds to a beam of the set of multiple beams associated with a highest predicted measurement value of the set of multiple predicted measurement values.
  • the satisfied triggering event may be a triggering event type 3.
  • the UE 115-b may transmit the performance monitoring report in response to the satisfaction of the triggering event being a first highest actual measurement value from among a subset of actual measurement values of the set of multiple actual measurement values being different by at least a threshold from a second highest actual measurement value of the set of multiple actual measurement values, where the subset of actual measurement values corresponds to a subset of beams of the set of multiple beams associated with a subset of highest predicted measurement values of the set of multiple predicted measurement values.
  • the satisfied triggering event may be a triggering event type 4.
  • the UE 115-b may transmit the performance monitoring report in response to the satisfaction of the triggering event being a highest predicted measurement value of the set of multiple predicted measurement values being different by at least a threshold from a highest actual measurement value of the set of multiple actual measurement values.
  • the satisfied triggering event may be a triggering event type 5.
  • the UE 115-b may transmit the performance monitoring report in response to the satisfaction of the triggering event being a highest actual measurement value of the set of multiple actual measurement values being different by at least a threshold from each of a subset of highest predicted measurement values of the set of multiple predicted measurement values.
  • the satisfied triggering event may be a triggering event type 6.
  • the UE 115-b may transmit the performance monitoring report in response to the satisfaction of the triggering event being a highest predicted measurement value of the set of multiple predicted measurement values being different by at least a threshold from an actual measurement value of the set of multiple actual measurement values, where the highest predicted measurement value and the actual measurement value correspond to a same beam of the set of multiple beams.
  • the satisfied triggering event may be a triggering event type 7.
  • the UE 115-b may transmit the performance monitoring report based on a set of multiple triggering events associated with the set of multiple actual measurement values being satisfied exceeding a threshold quantity of triggering events, the set of multiple triggering events comprising the triggering event.
  • the UE 115-b may transmit the performance monitoring report based on a set of multiple triggering events being satisfied within a time window exceeding a threshold quantity of triggering events, the set of multiple triggering events including the triggering event.
  • the UE 115-b may receive scheduling information for a set of multiple resources associated with transmission of performance monitoring reports.
  • the UE 115-b may transmit the performance monitoring report via a resource of the set of multiple resources.
  • the UE 115-b may receive scheduling information for a set of multiple resources associated with transmission of performance monitoring reports.
  • the UE 115-b may transmit an indication that the UE 115-b will transmit the performance monitoring report via a resource of the set of multiple resources.
  • the UE 115-b may transmit the performance monitoring report via the resource of the set of multiple resources in accordance with the indication.
  • the UE 115-b may transmit a beam prediction report that indicates one or more of the set of multiple predicted measurement values, and the beam prediction report may include the indication that the UE 115-b will transmit the performance monitoring report.
  • the UE 115-b may transmit, in association with the satisfaction of the triggering event, a request for a resource for the performance monitoring report.
  • the UE 115-b may receive, in response to the request, a grant for the resource.
  • the UE 115-b may transmit the performance monitoring report via the resource in accordance with the grant.
  • the UE 115-b may transmit a beam prediction report that indicates one or more of the set of multiple predicted measurement values, and the beam prediction report may include the request for the resource.
  • the UE 115-b may transmit the performance monitoring report via a MAC-CE via a PUCCH resource.
  • the UE 115-b may include an indication of one or more of the set of multiple actual measurement values in the performance monitoring report at 415.
  • the UE 115-b may include an indication of the triggering event in the performance monitoring report at 415.
  • the UE 115-b may transmit beam prediction report that indicates one or more of the set of multiple predicted measurement values, and the beam prediction report may include an indication of the triggering event (e.g., an indication that the UE 115-b may transmit the performance monitoring report at 415 based on the occurrence of the triggering event.
  • the triggering event e.g., an indication that the UE 115-b may transmit the performance monitoring report at 415 based on the occurrence of the triggering event.
  • FIG. 5 shows an example of an ML process 500 that supports event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • the ML process 500 may be implemented at a network entity 105, or a UE 115, or both as described with reference to FIGs. 1 through 4.
  • the ML process 500 may include an ML algorithm 510.
  • the ML algorithm 510 may be an example of a neural network, such as a feed forward (FF) or deep feed forward (DFF) neural network, a recurrent neural network (RNN) , a long/short term memory (LSTM) neural network, or any other type of neural network.
  • FF feed forward
  • DFF deep feed forward
  • RNN recurrent neural network
  • LSTM long/short term memory
  • any other ML algorithms may be supported.
  • the ML algorithm 510 may implement a nearest neighbor algorithm, a linear regression algorithm, a Bayes algorithm, a random forest algorithm, or any other ML algorithm.
  • the ML process 500 may involve supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, or any combination thereof.
  • the ML algorithm 510 may include an input layer 515, one or more hidden layers 520, and an output layer 525.
  • each hidden layer node 535 may receive a value from each input layer node 530 as input, where each input may be weighted. These neural network weights may be based on a cost function that is revised during training of the ML algorithm 510.
  • each output layer node 540 may receive a value from each hidden layer node 535 as input, where the inputs are weighted. If post-deployment training (e.g., online training) is supported, memory may be allocated to store errors and/or gradients for reverse matrix multiplication.
  • Training the ML algorithm 510 may support computation of the weights (e.g., connecting the input layer nodes 530 to the hidden layer nodes 535 and the hidden layer nodes 535 to the output layer nodes 540) to map an input pattern to a desired output outcome. This training may result in a device-specific ML algorithm 510 based on the historic application data and data transfer for a network entity 105 or UE 115.
  • input values 505 may be sent to the ML algorithm 510 for processing.
  • preprocessing may be performed according to a sequence of operations on the input values 505 such that the input values 505 may be in a format that is compatible with the ML algorithm 510.
  • the input values 505 may be converted into a set of k input layer nodes 530 at the input layer 515.
  • different measurements may be input at different input layer nodes 530 of the input layer 515.
  • Some input layer nodes 530 may be assigned default values (e.g., values of 0) if the quantity of input layer nodes 530 exceeds the quantity of inputs corresponding to the input values 505.
  • the input layer 515 may include three input layer nodes 530-a, 530-b, and 530-c. However, it is to be understood that the input layer 515 may include any quantity of input layer nodes 530 (e.g., 20 input nodes) .
  • the ML algorithm 510 may convert the input layer 515 to a hidden layer 520 based on a quantity of input-to-hidden weights between the k input layer nodes 530 and the n hidden layer nodes 535.
  • the ML algorithm 510 may include any quantity of hidden layers 520 as intermediate steps between the input layer 515 and the output layer 525. Additionally, each hidden layer 520 may include any quantity of nodes. For example, as illustrated, the hidden layer 520 may include four hidden layer nodes 535-a, 535-b, 535-c, and 535-d. However, it is to be understood that the hidden layer 520 may include any quantity of hidden layer nodes 535 (e.g., 10 input nodes) .
  • each node in a layer may be based on each node in the previous layer.
  • the value of hidden layer node 535-a may be based on the values of input layer nodes 530-a, 530-b, and 530-c (e.g., with different weights applied to each node value) .
  • the ML algorithm 510 may 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) .
  • beam measurements e.g., RSPR, SINR, or CIR
  • FIG. 6 shows a block diagram 600 of a device 605 that supports event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • the device 605 may be an example of aspects of a UE 115 as described herein.
  • the device 605 may include a receiver 610, a transmitter 615, and a communications manager 620.
  • the device 605, or one or more components of the device 605 may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to event-driven beam reporting for performance monitoring of beam prediction models) . Information may be passed on to other components of the device 605.
  • the receiver 610 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 615 may provide a means for transmitting signals generated by other components of the device 605.
  • the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to event-driven beam reporting for performance monitoring of beam prediction models) .
  • the transmitter 615 may be co-located with a receiver 610 in a transceiver module.
  • the transmitter 615 may utilize a single antenna or a set of multiple antennas.
  • the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be examples of means for performing various aspects of event-driven beam reporting for performance monitoring of beam prediction models as described herein.
  • the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be capable of performing one or more of the functions described herein.
  • the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include at least one of a processor, a digital signal processor (DSP) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure.
  • DSP digital signal processor
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • microcontroller discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure.
  • At least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .
  • the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .
  • a general-purpose processor e.g., a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions
  • the communications manager 620 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both.
  • the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 620 may support wireless communications in accordance with examples as disclosed herein.
  • the communications manager 620 is capable of, configured to, or operable to support a means for generating a set of multiple predicted measurement values for a set of multiple beams.
  • the communications manager 620 is capable of, configured to, or operable to support a means for receiving a set of multiple reference signals via the set of multiple beams.
  • the communications manager 620 is capable of, configured to, or operable to support a means for transmitting a performance monitoring report in association with satisfaction of a triggering event, the satisfaction of the triggering event based on the set of multiple predicted measurement values and a set of multiple actual measurement values for the set of multiple beams, the set of multiple actual measurement values based on the set of multiple reference signals.
  • the device 605 e.g., at least one processor controlling or otherwise coupled with the receiver 610, the transmitter 615, the communications manager 620, or a combination thereof
  • the device 605 may support techniques for reduced processing, reduced power consumption, and more efficient utilization of communication resources.
  • FIG. 7 shows a block diagram 700 of a device 705 that supports event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • the device 705 may be an example of aspects of a device 605 or a UE 115 as described herein.
  • the device 705 may include a receiver 710, a transmitter 715, and a communications manager 720.
  • the device 705, or one or more components of the device 705 e.g., the receiver 710, the transmitter 715, the communications manager 720
  • Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 710 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to event-driven beam reporting for performance monitoring of beam prediction models) . Information may be passed on to other components of the device 705.
  • the receiver 710 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 715 may provide a means for transmitting signals generated by other components of the device 705.
  • the transmitter 715 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to event-driven beam reporting for performance monitoring of beam prediction models) .
  • the transmitter 715 may be co-located with a receiver 710 in a transceiver module.
  • the transmitter 715 may utilize a single antenna or a set of multiple antennas.
  • the communications manager 720 may support wireless communications in accordance with examples as disclosed herein.
  • the beam measurement prediction manager 725 is capable of, configured to, or operable to support a means for generating a set of multiple predicted measurement values for a set of multiple beams.
  • the reference signal reception manager 730 is capable of, configured to, or operable to support a means for receiving a set of multiple reference signals via the set of multiple beams.
  • the performance monitoring report manager 735 is capable of, configured to, or operable to support a means for transmitting a performance monitoring report in association with satisfaction of a triggering event, the satisfaction of the triggering event based on the set of multiple predicted measurement values and a set of multiple actual measurement values for the set of multiple beams, the set of multiple actual measurement values based on the set of multiple reference signals.
  • FIG. 8 shows a block diagram 800 of a communications manager 820 that supports event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • the communications manager 820 may be an example of aspects of a communications manager 620, a communications manager 720, or both, as described herein.
  • the communications manager 820, or various components thereof, may be an example of means for performing various aspects of event-driven beam reporting for performance monitoring of beam prediction models as described herein.
  • the communications manager 820 may include a beam measurement prediction manager 825, a reference signal reception manager 830, a performance monitoring report manager 835, a performance monitoring report triggering event manager 840, a triggering event threshold manager 845, a performance monitoring report resource manager 850, a performance monitoring report indication manager 855, or any combination thereof.
  • Each of these components, or components or subcomponents thereof e.g., one or more processors, one or more memories
  • the communications manager 820 may support wireless communications in accordance with examples as disclosed herein.
  • the beam measurement prediction manager 825 is capable of, configured to, or operable to support a means for generating a set of multiple predicted measurement values for a set of multiple beams.
  • the reference signal reception manager 830 is capable of, configured to, or operable to support a means for receiving a set of multiple reference signals via the set of multiple beams.
  • the performance monitoring report manager 835 is capable of, configured to, or operable to support a means for transmitting a performance monitoring report in association with satisfaction of a triggering event, the satisfaction of the triggering event based on the set of multiple predicted measurement values and a set of multiple actual measurement values for the set of multiple beams, the set of multiple actual measurement values based on the set of multiple reference signals.
  • the performance monitoring report triggering event manager 840 is capable of, configured to, or operable to support a means for transmitting the performance monitoring report in response to the satisfaction of the triggering event including a first beam corresponding to a highest actual measurement value of the set of multiple actual measurement values being excluded from a subset of beams of the set of multiple beams, where the subset of beams are associated with a subset of highest predicted measurement values of the set of multiple predicted measurement values.
  • the performance monitoring report triggering event manager 840 is capable of, configured to, or operable to support a means for transmitting the performance monitoring report in response to the satisfaction of the triggering event including a first beam corresponding to a highest predicted measurement value of the set of multiple predicted measurement values being excluded from a subset of beams of the set of multiple beams, where the subset of beams are associated with a subset of highest actual measurement values of the set of multiple actual measurement values.
  • the performance monitoring report triggering event manager 840 is capable of, configured to, or operable to support a means for transmitting the performance monitoring report in response to the satisfaction of the triggering event including an actual measurement value of the set of multiple actual measurement values being different by at least a threshold from a highest actual measurement value of the set of multiple actual measurement values, where the actual measurement value corresponds to a beam of the set of multiple beams associated with a highest predicted measurement value of the set of multiple predicted measurement values.
  • the performance monitoring report triggering event manager 840 is capable of, configured to, or operable to support a means for transmitting the performance monitoring report in response to the satisfaction of the triggering event including a first highest actual measurement value from among a subset of actual measurement values of the set of multiple actual measurement values being different by at least a threshold from a second highest actual measurement value of the set of multiple actual measurement values, where the subset of actual measurement values corresponds to a subset of beams of the set of multiple beams associated with a subset of highest predicted measurement values of the set of multiple predicted measurement values.
  • the performance monitoring report triggering event manager 840 is capable of, configured to, or operable to support a means for transmitting the performance monitoring report in response to the satisfaction of the triggering event including a highest predicted measurement value of the set of multiple predicted measurement values being different by at least a threshold from a highest actual measurement value of the set of multiple actual measurement values.
  • the performance monitoring report triggering event manager 840 is capable of, configured to, or operable to support a means for transmitting the performance monitoring report in response to the satisfaction of the triggering event including a highest actual measurement value of the set of multiple actual measurement values being different by at least a threshold from each of a subset of highest predicted measurement values of the set of multiple predicted measurement values.
  • the performance monitoring report triggering event manager 840 is capable of, configured to, or operable to support a means for transmitting the performance monitoring report in response to the satisfaction of the triggering event including a highest predicted measurement value of the set of multiple predicted measurement values being different by at least a threshold from an actual measurement value of the set of multiple actual measurement values, where the highest predicted measurement value and the actual measurement value correspond to a same beam of the set of multiple beams.
  • the triggering event threshold manager 845 is capable of, configured to, or operable to support a means for transmitting the performance monitoring report based on a set of multiple triggering events associated with the set of multiple actual measurement values being satisfied exceeding a threshold quantity of triggering events, the set of multiple triggering events including the triggering event.
  • the triggering event threshold manager 845 is capable of, configured to, or operable to support a means for transmitting the performance monitoring report based on a set of multiple triggering events being satisfied within a time window exceeding a threshold quantity of triggering events, the set of multiple triggering events including the triggering event.
  • the performance monitoring report resource manager 850 is capable of, configured to, or operable to support a means for receiving scheduling information for a set of multiple resources associated with transmission of performance monitoring reports. In some examples, the performance monitoring report manager 835 is capable of, configured to, or operable to support a means for transmitting the performance monitoring report via a resource of the set of multiple resources.
  • the performance monitoring report triggering event manager 840 is capable of, configured to, or operable to support a means for receiving scheduling information for a set of multiple resources associated with transmission of performance monitoring reports.
  • the performance monitoring report indication manager 855 is capable of, configured to, or operable to support a means for transmitting an indication that the UE will transmit the performance monitoring report via a resource of the set of multiple resources.
  • the performance monitoring report manager 835 is capable of, configured to, or operable to support a means for transmitting the performance monitoring report via the resource of the set of multiple resources in accordance with the indication.
  • the performance monitoring report manager 835 is capable of, configured to, or operable to support a means for transmitting a beam prediction report that indicates one or more of the set of multiple predicted measurement values, where the beam prediction report includes the indication that the UE will transmit the performance monitoring report.
  • the performance monitoring report resource manager 850 is capable of, configured to, or operable to support a means for transmitting, in association with the satisfaction of the triggering event, a request for a resource for the performance monitoring report. In some examples, the performance monitoring report resource manager 850 is capable of, configured to, or operable to support a means for receiving, in response to the request, a grant for the resource. In some examples, the performance monitoring report manager 835 is capable of, configured to, or operable to support a means for transmitting the performance monitoring report via the resource in accordance with the grant.
  • the performance monitoring report manager 835 is capable of, configured to, or operable to support a means for transmitting a beam prediction report that indicates one or more of the set of multiple predicted measurement values, where the beam prediction report includes the request for the resource.
  • the performance monitoring report manager 835 is capable of, configured to, or operable to support a means for transmitting the performance monitoring report via a MAC-CE via a PUSCH resource.
  • the performance monitoring report manager 835 is capable of, configured to, or operable to support a means for transmitting an indication of one or more of the set of multiple actual measurement values.
  • the performance monitoring report manager 835 is capable of, configured to, or operable to support a means for transmitting an indication of the triggering event.
  • the performance monitoring report manager 835 is capable of, configured to, or operable to support a means for transmitting a beam prediction report that indicates one or more of the set of multiple predicted measurement values, where the beam prediction report includes an indication of the satisfaction of the triggering event.
  • FIG. 9 shows a diagram of a system 900 including a device 905 that supports event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • the device 905 may be an example of or include components of a device 605, a device 705, or a UE 115 as described herein.
  • the device 905 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof) .
  • the device 905 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 920, an input/output (I/O) controller, such as an 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 be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 945) .
  • buses e.g., a bus 945
  • the I/O controller 910 may manage input and output signals for the device 905.
  • the I/O controller 910 may also manage peripherals not integrated into the device 905.
  • the I/O controller 910 may represent a physical connection or port to an external peripheral.
  • the I/O controller 910 may utilize an operating system such as or another known operating system.
  • the I/O controller 910 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
  • the I/O controller 910 may be implemented as part of one or more processors, such as the at least one processor 940.
  • 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.
  • the device 905 may include a single antenna. However, in some other cases, the device 905 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 915 may communicate bi-directionally via the one or more antennas 925 using wired or wireless links as described herein.
  • the transceiver 915 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 915 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 925 for transmission, and to demodulate packets received from the one or more antennas 925.
  • the transceiver 915 may be an example of a transmitter 615, a transmitter 715, a receiver 610, a receiver 710, or any combination thereof or component thereof, as described herein.
  • the at least one memory 930 may include random access memory (RAM) and read-only memory (ROM) .
  • the at least one memory 930 may store computer-readable, computer-executable, or processor-executable code, such as the code 935.
  • the code 935 may include instructions that, when executed by the at least one processor 940, cause the device 905 to perform various functions described herein.
  • the code 935 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code 935 may not be directly executable by the at least one processor 940 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the at least one memory 930 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the 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, one or more discrete hardware components, or any combination thereof) .
  • the at least one processor 940 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 940.
  • the at least one processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks supporting event-driven beam reporting for performance monitoring of beam prediction models) .
  • the device 905 or a component of the device 905 may include at least one processor 940 and at least one memory 930 coupled with or to the at least one processor 940, the at least one processor 940 and the at least one memory 930 configured to perform various functions described herein.
  • the at least one processor 940 may include multiple processors and the at least one memory 930 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein.
  • the at least one processor 940 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 940) and memory circuitry (which may include the at least one memory 930) ) , or components, that receives or obtains inputs and processes the inputs 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.
  • the at least one processor 940 or a processing system including the at least one processor 940 may be configured to, configurable to, or operable to cause the device 905 to perform one or more of the functions described herein.
  • being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 935 (e.g., processor-executable code) stored in the at least one memory 930 or otherwise, to perform one or more of the functions described herein.
  • the communications manager 920 may support wireless communications in accordance with examples as disclosed herein.
  • the communications manager 920 is capable of, configured to, or operable to support a means for generating a set of multiple predicted measurement values for a set of multiple beams.
  • the communications manager 920 is capable of, configured to, or operable to support a means for receiving a set of multiple reference signals via the set of multiple beams.
  • the communications manager 920 is capable of, configured to, or operable to support a means for transmitting a performance monitoring report in association with satisfaction of a triggering event, the satisfaction of the triggering event based on the set of multiple predicted measurement values and a set of multiple actual measurement values for the set of multiple beams, the set of multiple actual measurement values based on the set of multiple reference signals.
  • the device 905 may support techniques for improved communication reliability, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, and improved utilization of processing capability.
  • the communications manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 915, the one or more antennas 925, or any combination thereof.
  • the communications manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 920 may be supported by or performed by the at least one processor 940, the at least one memory 930, the code 935, or any combination thereof.
  • the code 935 may include instructions executable by the at least one processor 940 to cause the device 905 to perform various aspects of event-driven beam reporting for performance monitoring of beam prediction models as described herein, or the at least one processor 940 and the at least one memory 930 may be otherwise configured to, individually or collectively, perform or support such operations.
  • FIG. 10 shows a flowchart illustrating a method 1000 that supports event-driven beam reporting for performance monitoring of beam prediction models in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1000 may be implemented by a UE or its components as described herein.
  • the operations of the method 1000 may be performed by a UE 115 as described with reference to FIGs. 1 through 9.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include generating a set of multiple predicted measurement values for a set of multiple beams.
  • the operations of 1005 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1005 may be performed by a beam measurement prediction manager 825 as described with reference to FIG. 8.
  • the method may include receiving a set of multiple reference signals via the set of multiple beams.
  • the operations of 1010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1010 may be performed by a reference signal reception manager 830 as described with reference to FIG. 8.
  • the method may include transmitting a performance monitoring report in association with satisfaction of a triggering event, the satisfaction of the triggering event based on the set of multiple predicted measurement values and a set of multiple actual measurement values for the set of multiple beams, the set of multiple actual measurement values based on the set of multiple reference signals.
  • the operations of 1015 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1015 may be performed by a performance monitoring report manager 835 as described with reference to FIG. 8.
  • a method for wireless communications at a UE comprising: generating a plurality of predicted measurement values for a plurality of beams; receiving a plurality of reference signals via the plurality of beams; and transmitting a performance monitoring report in association with satisfaction of a triggering event, the satisfaction of the triggering event based at least in part on the plurality of predicted measurement values and a plurality of actual measurement values for the plurality of beams, the plurality of actual measurement values based at least in part on the plurality of reference signals.
  • Aspect 2 The method of aspect 1, wherein transmitting the performance monitoring report comprises: transmitting the performance monitoring report in response to the satisfaction of the triggering event comprising a first beam corresponding to a highest actual measurement value of the plurality of actual measurement values being excluded from a subset of beams of the plurality of beams, wherein the subset of beams are associated with a subset of highest predicted measurement values of the plurality of predicted measurement values.
  • Aspect 3 The method of any of aspects 1 through 2, wherein transmitting the performance monitoring report comprises: transmitting the performance monitoring report in response to the satisfaction of the triggering event comprising a first beam corresponding to a highest predicted measurement value of the plurality of predicted measurement values being excluded from a subset of beams of the plurality of beams, wherein the subset of beams are associated with a subset of highest actual measurement values of the plurality of actual measurement values.
  • Aspect 4 The method of any of aspects 1 through 3, wherein transmitting the performance monitoring report comprises: transmitting the performance monitoring report in response to the satisfaction of the triggering event comprising an actual measurement value of the plurality of actual measurement values being different by at least a threshold from a highest actual measurement value of the plurality of actual measurement values, wherein the actual measurement value corresponds to a beam of the plurality of beams associated with a highest predicted measurement value of the plurality of predicted measurement values.
  • Aspect 5 The method of any of aspects 1 through 4, wherein transmitting the performance monitoring report comprises: transmitting the performance monitoring report in response to the satisfaction of the triggering event comprising a first highest actual measurement value from among a subset of actual measurement values of the plurality of actual measurement values being different by at least a threshold from a second highest actual measurement value of the plurality of actual measurement values, wherein the subset of actual measurement values corresponds to a subset of beams of the plurality of beams associated with a subset of highest predicted measurement values of the plurality of predicted measurement values.
  • Aspect 6 The method of any of aspects 1 through 5, wherein transmitting the performance monitoring report comprises: transmitting the performance monitoring report in response to the satisfaction of the triggering event comprising a highest predicted measurement value of the plurality of predicted measurement values being different by at least a threshold from a highest actual measurement value of the plurality of actual measurement values.
  • Aspect 7 The method of any of aspects 1 through 6, wherein transmitting the performance monitoring report comprises: transmitting the performance monitoring report in response to the satisfaction of the triggering event comprising a highest actual measurement value of the plurality of actual measurement values being different by at least a threshold from each of a subset of highest predicted measurement values of the plurality of predicted measurement values.
  • Aspect 8 The method of any of aspects 1 through 7, wherein transmitting the performance monitoring report comprises: transmitting the performance monitoring report in response to the satisfaction of the triggering event comprising a highest predicted measurement value of the plurality of predicted measurement values being different by at least a threshold from an actual measurement value of the plurality of actual measurement values, wherein the highest predicted measurement value and the actual measurement value correspond to a same beam of the plurality of beams.
  • Aspect 9 The method of any of aspects 1 through 8, wherein transmitting the performance monitoring report comprises: transmitting the performance monitoring report based at least in part on a plurality of triggering events associated with the plurality of actual measurement values being satisfied exceeding a threshold quantity of triggering events, the plurality of triggering events comprising the triggering event.
  • Aspect 10 The method of any of aspects 1 through 9, wherein transmitting the performance monitoring report comprises: transmitting the performance monitoring report based at least in part on a plurality of triggering events being satisfied within a time window exceeding a threshold quantity of triggering events, the plurality of triggering events comprising the triggering event.
  • Aspect 11 The method of any of aspects 1 through 10, further comprising: receiving scheduling information for a plurality of resources associated with transmission of performance monitoring reports; and transmitting the performance monitoring report via a resource of the plurality of resources.
  • Aspect 12 The method of any of aspects 1 through 11, further comprising: receiving scheduling information for a plurality of resources associated with transmission of performance monitoring reports; transmitting an indication that the UE will transmit the performance monitoring report via a resource of the plurality of resources; and transmitting the performance monitoring report via the resource of the plurality of resources in accordance with the indication.
  • Aspect 13 The method of aspect 12, further comprising: transmitting a beam prediction report that indicates one or more of the plurality of predicted measurement values, wherein the beam prediction report includes the indication that the UE will transmit the performance monitoring report.
  • Aspect 14 The method of any of aspects 1 through 10, further comprising: transmitting, in association with the satisfaction of the triggering event, a request for a resource for the performance monitoring report; receiving, in response to the request, a grant for the resource; and transmitting the performance monitoring report via the resource in accordance with the grant.
  • Aspect 15 The method of aspect 14, further comprising: transmitting a beam prediction report that indicates one or more of the plurality of predicted measurement values, wherein the beam prediction report includes the request for the resource.
  • Aspect 16 The method of any of aspects 1 through 15, further comprising: transmitting the performance monitoring report via a MAC-CE via a PUSCH resource.
  • Aspect 17 The method of any of aspects 1 through 16, wherein transmitting the performance monitoring report comprises: transmitting an indication of one or more of the plurality of actual measurement values.
  • Aspect 18 The method of any of aspects 1 through 17, wherein transmitting the performance monitoring report comprises: transmitting an indication of the triggering event.
  • Aspect 19 The method of any of aspects 1 through 18, further comprising: transmitting a beam prediction report that indicates one or more of the plurality of predicted measurement values, wherein the beam prediction report includes an indication of the satisfaction of the triggering event.
  • Aspect 20 An apparatus for wireless communications at a UE, comprising one or more processors; and instructions stored in one or more memories and executable by the one or more processors, individually or collectively, to cause the apparatus to perform a method of any of aspects 1 through 19.
  • a UE for wireless communications comprising at least one means for performing a method of any of aspects 1 through 19.
  • Aspect 22 A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 19.
  • LTE, LTE-A, LTE-A Pro, or NR may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks.
  • the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
  • UMB Ultra Mobile Broadband
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Institute of Electrical and Electronics Engineers
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • a general-purpose processor may be a microprocessor but, in the alternative, the 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 in conjunction with a DSP core, or any other such configuration) . Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.
  • the functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.
  • the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns.
  • the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable.
  • a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components.
  • the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function.
  • a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components.
  • a component introduced with the article “a” may be understood to mean “one or more components, ” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.
  • subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components.
  • referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ”
  • determining encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data structure) , ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) , and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Sont divulgués des procédés, des systèmes, et des dispositifs destinés aux communications sans fil. Un équipement utilisateur (UE) peut mesurer un premier ensemble de faisceaux (« faisceaux de l'ensemble B ») et peut utiliser des mesures sur le premier ensemble de faisceaux pour prédire des caractéristiques d'un second ensemble de faisceaux (« faisceaux de l'ensemble A ») par l'intermédiaire d'un modèle d'intelligence artificielle (AI) ou d'apprentissage automatique (ML) entraîné. En raison du changement de conditions de canal, la précision des mesures prédites par AI/ML peut changer au fil du temps. Le réseau peut désactiver la prédiction de faisceau ou peut réentraîner le modèle AI/ML si la précision de prédiction de faisceau tombe en dessous d'une métrique de performances. L'UE peut générer des mesures de signaux de référence reçus par l'intermédiaire des faisceaux de l'ensemble A pour une comparaison avec les mesures prédites pour les faisceaux de l'ensemble A pour une surveillance de précision de prédictions de faisceau. L'UE peut transmettre un rapport de surveillance de performances au réseau pour les prédictions de faisceau basées sur l'AI/ML sur la base d'un ou de plusieurs événements de déclenchement définis.
PCT/CN2024/110576 2024-08-08 2024-08-08 Rapport de faisceau entraîné par un événement pour la surveillance de performances de modèles de prédiction de faisceau Pending WO2026031032A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/110576 WO2026031032A1 (fr) 2024-08-08 2024-08-08 Rapport de faisceau entraîné par un événement pour la surveillance de performances de modèles de prédiction de faisceau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/110576 WO2026031032A1 (fr) 2024-08-08 2024-08-08 Rapport de faisceau entraîné par un événement pour la surveillance de performances de modèles de prédiction de faisceau

Publications (1)

Publication Number Publication Date
WO2026031032A1 true WO2026031032A1 (fr) 2026-02-12

Family

ID=98734468

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/110576 Pending WO2026031032A1 (fr) 2024-08-08 2024-08-08 Rapport de faisceau entraîné par un événement pour la surveillance de performances de modèles de prédiction de faisceau

Country Status (1)

Country Link
WO (1) WO2026031032A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117546512A (zh) * 2023-09-22 2024-02-09 北京小米移动软件有限公司 通信方法、终端、网络设备以及通信系统
CN117581581A (zh) * 2023-08-30 2024-02-20 北京小米移动软件有限公司 通信方法、终端、网络设备、以及通信系统
US20240107347A1 (en) * 2022-09-23 2024-03-28 Nokia Technologies Oy Machine learning model selection for beam prediction for wireless networks
WO2024091046A1 (fr) * 2022-10-26 2024-05-02 Samsung Electronics Co., Ltd. Procédé et appareil pour réaliser une gestion de faisceau dans des systèmes cellulaires
US20240196242A1 (en) * 2022-12-07 2024-06-13 Mediatek Inc. Method and apparatus for ai/ml based beam management

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240107347A1 (en) * 2022-09-23 2024-03-28 Nokia Technologies Oy Machine learning model selection for beam prediction for wireless networks
WO2024091046A1 (fr) * 2022-10-26 2024-05-02 Samsung Electronics Co., Ltd. Procédé et appareil pour réaliser une gestion de faisceau dans des systèmes cellulaires
US20240196242A1 (en) * 2022-12-07 2024-06-13 Mediatek Inc. Method and apparatus for ai/ml based beam management
CN117581581A (zh) * 2023-08-30 2024-02-20 北京小米移动软件有限公司 通信方法、终端、网络设备、以及通信系统
CN117546512A (zh) * 2023-09-22 2024-02-09 北京小米移动软件有限公司 通信方法、终端、网络设备以及通信系统

Similar Documents

Publication Publication Date Title
US20250105929A1 (en) Machine learning models for predictive resource management
WO2024065372A1 (fr) Procédés et appareils de rapport de prédiction csi pour un ensemble de faisceaux
WO2023206114A1 (fr) Retour d'informations d'erreur d'inférence pour des inférences basées sur l'apprentissage automatique
WO2024020911A1 (fr) Techniques de mesure de canal avec gestion prédictive de faisceau
WO2024050655A1 (fr) Rapport de prédiction d'évitement de faisceau déclenché par un événement
WO2025235628A1 (fr) Signalisation pour prédictions de défaillance de liaison radio sur la base, au moins en partie, d'un modèle d'intelligence artificielle
WO2025227415A1 (fr) Mesure, prédiction et rapport hybrides
US20250048131A1 (en) Indicating causes for life cycle management operations
WO2024168808A1 (fr) Rapport de mesure de faisceau déclenché par dispositif
WO2024168791A1 (fr) Indication d'identifiant de faisceau dans un rapport de prédiction de faisceau
WO2026031032A1 (fr) Rapport de faisceau entraîné par un événement pour la surveillance de performances de modèles de prédiction de faisceau
WO2026073392A1 (fr) Association temporelle entre des instances de signal de référence de surveillance et des instances de prédiction de faisceau
WO2026031141A1 (fr) Procédés de rapport pour surveillance de performance
WO2026076629A1 (fr) Identifiant associé et attribution de faisceau pour communications sans fil
WO2025184852A1 (fr) Demande de ressource basée sur la prédiction pour la gestion de la mobilité
US20250351026A1 (en) Signaling for radio link failure predictions
WO2025227356A1 (fr) Prédiction simultanée de faisceau sur l'ensemble de multiples cellules
WO2026073369A1 (fr) Signalisation de capacité dans des systèmes de communication sans fil
US20260128960A1 (en) Updating training reference signal configurations
WO2026006969A1 (fr) Identification de signaux de référence de mesure pour rapport de faisceau initié par un équipement utilisateur
WO2026073465A1 (fr) Techniques d'inférence et de surveillance tenant compte de restrictions de planification de réseau sur un ensemble de cibles de prédiction
WO2025208556A1 (fr) Rapport de faisceau initié par un équipement utilisateur (ue) pour la gestion de faisceau
WO2025231681A1 (fr) Signalisation de capacité et informations d'assistance pour surveillance de performance de prédiction de faisceau
US20250310016A1 (en) Performance monitoring of layer-3 (l3) measurement predictions
WO2026073436A1 (fr) Rapport de surveillance de performances initié par un équipement utilisateur (ue) et commandé par un événement pour des ensembles de surveillance à performances limitées

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24950092

Country of ref document: EP

Kind code of ref document: A1