Flexible processing unit occupation for inference
Flexible processing unit occupation techniques using reason codes and concurrency reporting address inefficiencies in UE resource reporting, enabling optimal resource allocation and improved communication efficiency by dynamically indicating supported configurations and available units.
Patent Information
- Application Number
- PCT/CN2025/093728
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems face inefficiencies in resource allocation due to UE reporting a conservative maximum of AI/ML processing units, leading to underutilization of computing resources and suboptimal network configuration.
Implementing flexible processing unit occupation techniques, including the use of reason codes and concurrency reporting to dynamically indicate supported inference configurations and available processing units, allowing networks to optimize resource allocation based on actual UE capabilities.
Enables more efficient use of computing resources by allowing networks to configure UEs with additional inference reports, thereby optimizing resource allocation and improving communication efficiency.
Smart Images

Figure CN2025093728_12112026_PF_FP_ABST
Abstract
Description
FLEXIBLE PROCESSING UNIT OCCUPATION FOR INFERENCEFIELD OF THE DISCLOSURE
[0001] Aspects of the present disclosure generally relate to wireless communication and specifically relate to techniques, apparatuses, and methods associated with flexible processing unit occupation for inference. DESCRIPTION OF THE RELATED TECHNOLOGY
[0002] Wireless communication systems are widely deployed to provide various services, which may involve carrying or supporting voice, text, other messaging, video, data, or other traffic. Typical wireless communication systems may employ multiple-access radio access technologies (RATs) capable of supporting communication among multiple wireless communication devices including user devices or other devices by sharing the available system resources (for example, time domain resources, frequency domain resources, spatial domain resources, or device transmit power, among other examples) . Such multiple-access RATs are supported by technological advancements that have been adopted in various telecommunication standards, which define common protocols that enable different wireless communication devices to communicate on a local, municipal, national, regional, or global level. An example telecommunication standard is New Radio (NR) . NR, which also may be referred to as 5G, is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) . As the demand for connectivity continues to increase, further improvements in NR may be implemented, and other RATs, such as 6G and beyond, may be introduced to enable new applications and facilitate new use cases.
[0003] In a wireless network, a user equipment (UE) may apply models for beam prediction. For example, the UE may use measurements from a first set of beams to predict measurements for a second set of beams. The UE may predict measurements across space (e.g., the first set of beams being wider than the second set of beams) or across time (e.g., predicting future measurements for the second set of beams using historic measurements of the first set of beams) .SUMMARY
[0004] The systems, methods, and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.
[0005] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE) . The method may include receiving a reconfiguration message indicating a set of inference configuration candidates for beam management. The method may include transmitting an indication of which inference configuration candidates in the set are supported by the UE and which inference configuration candidates in the set are unsupported by the UE, where each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code indicating a combination of inference reports unsupported by the UE.
[0006] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving an indication of a set of report configurations. The method may include transmitting an indication of which report configurations in the set can be supported concurrently.
[0007] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving an indication of a set of reporting configurations. The method may include transmitting an indication of available processing units based at least in part on the set of reporting configurations.
[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting a reconfiguration message indicating a set of inference configuration candidates for beam management. The method may include receiving an indication of which inference configuration candidates in the set are supported by a UE and which inference configuration candidates in the set are unsupported by the UE, where each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code indicating a combination of inference reports unsupported by the UE.
[0009] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting an indication of a set of report configurations. The method may include receiving an indication of which report configurations in the set can be supported concurrently.
[0010] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting an indication of a set of reporting configurations. The method may include receiving an indication of available processing units based at least in part on the set of reporting configurations.
[0011] Some aspects described herein relate to a UE. The UE may include a processing system. The processing system may include one or more processors and one or more code-storing memories coupled with the one or more processors. The processing system may be configured to cause the UE to receive a reconfiguration message indicating a set of inference configuration candidates for beam management. The processing system may be configured to cause the UE to transmit an indication of which inference configuration candidates in the set are supported by the UE and which inference configuration candidates in the set are unsupported by the UE, where each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code indicating a combination of inference reports unsupported by the UE.
[0012] Some aspects described herein relate to a UE. The UE may include a processing system. The processing system may include one or more processors and one or more code-storing memories coupled with the one or more processors. The processing system may be configured to cause the UE to receive an indication of a set of report configurations. The processing system may be configured to cause the UE to transmit an indication of which report configurations in the set can be supported concurrently.
[0013] Some aspects described herein relate to a UE. The UE may include a processing system. The processing system may include one or more processors and one or more code-storing memories coupled with the one or more processors. The processing system may be configured to cause the UE to receive an indication of a set of reporting configurations. The processing system may be configured to cause the UE to transmit an indication of available processing units based at least in part on the set of reporting configurations.
[0014] Some aspects described herein relate to a network node. The network node may include a processing system. The processing system may include one or more processors and one or more code-storing memories coupled with the one or more processors. The processing system may be configured to cause the network node to transmit a reconfiguration message indicating a set of inference configuration candidates for beam management. The processing system may be configured to cause the network node to receive an indication of which inference configuration candidates in the set are supported by a UE and which inference configuration candidates in the set are unsupported by the UE, where each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code indicating a combination of inference reports unsupported by the UE.
[0015] Some aspects described herein relate to a network node. The network node may include a processing system. The processing system may include one or more processors and one or more code-storing memories coupled with the one or more processors. The processing system may be configured to cause the network node to transmit an indication of a set of report configurations. The processing system may be configured to cause the network node to receive an indication of which report configurations in the set can be supported concurrently.
[0016] Some aspects described herein relate to a network node. The network node may include a processing system. The processing system may include one or more processors and one or more code-storing memories coupled with the one or more processors. The processing system may be configured to cause the network node to transmit an indication of a set of reporting configurations. The processing system may be configured to cause the network node to receive an indication of available processing units based at least in part on the set of reporting configurations.
[0017] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a reconfiguration message indicating a set of inference configuration candidates for beam management. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit an indication of which inference configuration candidates in the set are supported by the UE and which inference configuration candidates in the set are unsupported by the UE, where each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code indicating a combination of inference reports unsupported by the UE.
[0018] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive an indication of a set of report configurations. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit an indication of which report configurations in the set can be supported concurrently.
[0019] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive an indication of a set of reporting configurations. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit an indication of available processing units based at least in part on the set of reporting configurations.
[0020] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit a reconfiguration message indicating a set of inference configuration candidates for beam management. The set of instructions, when executed by one or more processors of the network node, may cause the network node to receive an indication of which inference configuration candidates in the set are supported by a UE and which inference configuration candidates in the set are unsupported by the UE, where each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code indicating a combination of inference reports unsupported by the UE.
[0021] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit an indication of a set of report configurations. The set of instructions, when executed by one or more processors of the network node, may cause the network node to receive an indication of which report configurations in the set can be supported concurrently.
[0022] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit an indication of a set of reporting configurations. The set of instructions, when executed by one or more processors of the network node, may cause the network node to receive an indication of available processing units based at least in part on the set of reporting configurations.
[0023] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a reconfiguration message indicating a set of inference configuration candidates for beam management. The apparatus may include means for transmitting an indication of which inference configuration candidates in the set are supported by the apparatus and which inference configuration candidates in the set are unsupported by the apparatus, where each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code indicating a combination of inference reports unsupported by the UE.
[0024] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication of a set of report configurations. The apparatus may include means for transmitting an indication of which report configurations in the set can be supported concurrently.
[0025] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication of a set of reporting configurations. The apparatus may include means for transmitting an indication of available processing units based at least in part on the set of reporting configurations.
[0026] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting a reconfiguration message indicating a set of inference configuration candidates for beam management. The apparatus may include means for receiving an indication of which inference configuration candidates in the set are supported by a UE and which inference configuration candidates in the set are unsupported by the UE, where each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code indicating a combination of inference reports unsupported by the UE.
[0027] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting an indication of a set of report configurations. The apparatus may include means for receiving an indication of which report configurations in the set can be supported concurrently.
[0028] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting an indication of a set of reporting configurations. The apparatus may include means for receiving an indication of available processing units based at least in part on the set of reporting configurations.
[0029] Aspects of the present disclosure may generally be implemented by or as a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, network node, wireless communication device, or processing system as substantially described in the Detailed Description with reference to, and as illustrated by, the accompanying drawings. Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims. Note that the relative dimensions of the following figures may not be drawn to scale.BRIEF DESCRIPTION OF THE DRAWINGS
[0030] Fig. 1 is a diagram illustrating an example of a wireless communication network.
[0031] Fig. 2 is a diagram illustrating an example of artificial intelligence or machine learning based beam management.
[0032] Fig. 3 is a diagram of an example associated with reason codes for reporting inference capabilities.
[0033] Fig. 4 is a diagram of an example associated with flexible processing unit occupation for inference using concurrency reporting.
[0034] Figs. 5 and 6 are diagrams of examples associated with concurrency reporting.
[0035] Fig. 7 is a diagram of an example associated with flexible processing unit occupation for inference using dynamic negotiation.
[0036] Fig. 8 is a diagram of examples associated with dropping inference reports for flexible processing unit occupation.
[0037] Fig. 9 is a diagram of an example associated with reports to consider for flexible processing unit occupation.
[0038] Figs. 10, 11, and 12 are diagrams illustrating example processes performed, for example, by a user equipment.
[0039] Figs. 13, 14, and 15 are diagrams illustrating example processes performed, for example, by a network node.
[0040] Figs. 16 and 17 are diagrams of example apparatuses for wireless communication.DETAILED DESCRIPTION
[0041] In a wireless network, a user equipment (UE) may apply models for beam prediction. For example, the UE may use measurements from a first set of beams (also referred to as “Set B” beams) to predict measurements for a second set of beams (also referred to as “Set A” beams) . The UE may perform spatial beam prediction (e.g., using measurements of the first set of beams, which are wider, to predict measurements for the second set of beams, which are narrower) or temporal beam prediction (e.g., predicting future measurements for the second set of beams using historic measurements of the first set of beams) .
[0042] During an inference phase, a network may instruct the UE to generate predicted results (e.g., for the Set A beams) using historic measurements (e.g., of the Set B beams) and an artificial intelligence or machine learning (AI / ML) model. During measurement and reporting, the UE may occupy AI / ML processing units (APUs) , channel state information (CSI) processing units (CPUs) , or a combination thereof. Generally, the UE reports a maximum quantity of CPUs to the network and may drop measurements and reports that would cause the UE to occupy more than the maximum quantity of CPUs. However, because memory, processing, and other hardware requirements may vary across AI / ML models, using a static maximum for APUs (and optionally for CPUs as well) may result in under-utilization of computing resources at the UE. In particular, the UE may report a conservative maximum to account for most intensive AI / ML models, which may result in the network being able to configure the UE with fewer inference reports than the UE could actually handle. As a result, the network may allocate resources for communication between the UE and the network less optimally than if the UE were to be configured with additional inference reports.
[0043] Various aspects relate generally to using reason codes to allow a network to determine combinations of inference reports that are supported by a UE. Some aspects more specifically relate to the UE responding to a radio resource control (RRC) reconfiguration message, indicating a set of inference configuration candidates, with an indication of which candidates are supported and an indication of which candidates are unsupported along with a reason code. Additionally, or alternatively, various aspects relate generally to using concurrency reporting to allow a network to determine combinations of inference reports that are supported by a UE. Some aspects more specifically relate to the UE indicating which report configurations, in a set of report configurations, can be supported concurrently. As used herein, reports are supported “concurrently” when APU (and optionally CPU) occupation for both reports may overlap in time, at least in part, without exceeding capabilities of the UE. Alternatively, various aspects relate generally to dynamic indication of available APUs (and optionally available CPUs) by a UE. Some aspects further relate to indicating APU occupation (and optionally CPU occupation) per report configuration.
[0044] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, the described techniques can be used to allow a network to configure a UE with more inference reports than if the UE were to report a static maximum number of APUs (and CPUs) that can be occupied. As a result, the network may allocate resources for communication between the UE and the network more optimally than if the UE were to be configured with fewer inference reports.
[0045] 5G New Radio (NR) may support enhanced mobile broadband (eMBB) access, Internet of Things (IoT) networks or reduced capability (RedCap) device deployments, ultra-reliable low-latency communication (URLLC) applications, or massive machine-type communication (mMTC) , among other examples. To support these and other target verticals, a wireless communication system may be designed to implement a modularized functional infrastructure, a disaggregated and service-based network architecture, network function virtualization, network slicing, multi-access edge computing, millimeter wave (mmWave) technologies including massive multiple-input multiple-output (MIMO) , beamforming, IoT device or RedCap device connectivity and management, industrial connectivity, licensed and unlicensed spectrum access, sidelink and other device-to-device direct communication (for example, cellular vehicle-to-everything (CV2X) communication) , frequency spectrum expansion, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, device aggregation, advanced duplex communication (for example, sub-band full-duplex (SBFD) ) , multiple-subscriber implementations, high-precision positioning, radio frequency (RF) sensing, network energy savings (NES) , low-power signaling and radios, or artificial intelligence or machine learning (AI / ML) , among other examples.
[0046] The foregoing and other technological improvements may support use cases, such as wireless fronthauls, wireless midhauls, wireless backhauls, wireless data centers, extended reality (XR) and metaverse applications, meta services for supporting vehicle connectivity, holographic and mixed reality communication, autonomous and collaborative robots, vehicle platooning and cooperative maneuvering, sensing networks, gesture monitoring, human-brain interfacing, digital twin applications, asset management, and universal coverage applications using non-terrestrial or aerial platforms, among other examples.
[0047] The methods, operations, apparatuses, and techniques described herein may enable one or more of the foregoing technologies or new technologies or support one or more of the foregoing use cases or new use cases.
[0048] Fig. 1 is a diagram illustrating an example of a wireless communication network 100. The wireless communication network 100 may be or may include elements of a 5G network or a 6G network, among other examples. The wireless communication network 100 may include multiple network nodes 110. For example, in Fig. 1, the wireless communication network 100 includes multiple network nodes 110, including a network node 110a and a network node 110b (each of which also may be referred to herein simply as a “network node 110” ) . The network nodes 110 may support communications with multiple UEs 120. For example, in Fig. 1, the network nodes 110 support communication with a UE 120a, a UE 120b, and a UE 120c (each of which also may be referred to herein simply as a “UE 120” ) . In some examples, a UE 120 also may communicate with other UEs 120 and a network node 110 also may communicate with a core network and with other network nodes 110.
[0049] The network nodes 110 and the UEs 120 of the wireless communication network 100 communicate using the electromagnetic spectrum, which may be subdivided into various licensed or unlicensed operating bands, frequency ranges, component carriers, or channels that define associated frequencies available for communications. In some examples, each of the network nodes 110 and the UEs 120 may communicate using one or multiple component carriers in one or more operating bands or ranges. Typically, various operating bands are defined as frequency range designations FR1 (410 MHz through 7.125 GHz) , FR2 (24.25 GHz through 52.6 GHz) , FR3 (7.125 GHz through 24.25 GHz) , FR4a or FR4-1 (52.6 GHz through 71 GHz) , FR4 (52.6 GHz through 114.25 GHz) , and FR5 (114.25 GHz through 300 GHz) . Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in some documents and articles. Similarly, FR2 is often referred to (interchangeably) as a “millimeter wave” band in some documents and articles.
[0050] A network node 110 or a UE 120 may include one or more devices, components, or systems that enable communication with other devices, components, or systems of the wireless communication network 100. For example, a UE 120 and a network node 110 may each include one or more chips, system-on-chips (SoCs) , chipsets, packages, or devices that individually or collectively constitute or comprise a processing system. As shown in Fig. 1, each UE 120 includes a processing system 140 and each network node 110 includes a processing system 145. A processing system (for example, the processing system 140 or the processing system 145) includes processor (or “processing” ) circuitry in the form of one or multiple processors, microprocessors, processing units (such as central processing units, graphics processing units (GPUs) , neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , or digital signal processors (DSPs) ) , processing blocks, application-specific integrated circuits (ASICs) , programmable logic devices (PLDs) , or other discrete gate or transistor logic or circuitry (any one or more of which may be generally referred to herein individually as a “processor” or collectively as “the processor” or “the processor circuitry” ) . Such processors may be individually or collectively configurable or configured to perform various functions or operations described herein. A group of processors collectively configurable or configured to perform a set of functions may include a first processor configurable or configured to perform a first function of the set and a second processor configurable or configured to perform a second function of the set. In some other examples, each of a group of processors may be configurable or configured to perform a same set of functions.
[0051] The processing system 140 and the processing system 145 may each include memory circuitry in the form of one or multiple memory devices, memory blocks, memory elements, or other discrete gate or transistor logic or circuitry, each of which may include or implement tangible storage media, such as random-access memory, or read-only memory, or combinations thereof (any one or more of which may be generally referred to herein individually as a “memory” or collectively as “the memory” or “the memory circuitry” ) . One or more of the memories may be coupled (for example, operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) with one or more of the processors. One or more of the memories may individually or collectively store processor-executable code or instructions (such as software) (for example, which may be referred to as “one or more code-storing memories” or “code-storing memory circuitry” ) . For example, “code-storing memory” or “code-storing memory circuitry” refers to memory (or memory circuitry) that is configured to store processor-executable code or instructions. The processor-executable code or instructions, when executed by one or more of the processors, may configure one or more of the processors (or processing circuitry) to perform various functions or operations described herein. Additionally, or alternatively, in some examples, one or more of the processors may be configured to perform various functions or operations described herein without requiring configuration by software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0052] The processing system 140 and the processing system 145 may each include or be coupled with one or more modems (such as a cellular (for example, a 5G or 6G compliant) modem) . In some examples, one or more processors of the processing system 140 or the processing system 145 may include or implement one or more of the modems. The processing system 140 and the processing system 145 also may include or be coupled with multiple radios (collectively “the radio” ) , multiple RF chains, or multiple transceivers, each of which may in turn be coupled with one or more of multiple antennas. In some examples, one or more processors of the processing system 140 or the processing system 145 may include or implement one or more of the radios, RF chains, or transceivers. An RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs) , or other devices that convert between an analog signal (such as for transmission or reception via an air interface) and a digital signal (such as for processing by the processing system 140 or by the processing system 145) .
[0053] A network node 110 and a UE 120 may each include one or multiple antennas or antenna arrays. Typical network nodes 110 and UEs 120 may include multiple antennas, which may be organized or structured into one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. As used herein, the term “antenna” can refer to one or more antennas, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays. The term “antenna panel” can refer to a group of antennas (such as antenna elements) arranged in an array or panel, which may facilitate beamforming by manipulating parameters associated with the group of antennas. The term “antenna module” may refer to circuitry including one or more antennas as well as one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device, such as the network node 110 and the UE 120.
[0054] A network node 110 may be, may include, or also may be referred to as an NR network node, a 5G network node, a 6G network node, a Node B, a gNB, an access point (AP) , a transmission reception point (TRP) , a network entity, a network element, a network equipment, or another type of device, component, or system included in a radio access network (RAN) . In various deployments, a network node 110 may be implemented as a single physical node (for example, a single physical structure) or may be implemented as two or more physical nodes (for example, two or more distinct physical structures) . For example, a network node 110 may be a device or system that implements a part of a radio protocol stack, a device or system that implements a full radio protocol stack (such as a full gNB protocol stack) , or a collection of devices or systems that collectively implement the full radio protocol stack. For example, and as shown, a network node 110 may be an aggregated network node having an aggregated architecture, meaning that the network node 110 may implement a full radio protocol stack that is physically and logically integrated within a single physical structure in the wireless communication network 100. For example, an aggregated network node 110 may include a single standalone base station or a single TRP that operates with a full radio protocol stack to enable or facilitate communication between a UE 120 and a core network of the wireless communication network 100.
[0055] Alternatively, a network node 110 may be a disaggregated network node 110 (sometimes referred to as a disaggregated base station) , having a disaggregated architecture, meaning that the network node 110 may operate with a radio protocol stack that is physically distributed or logically distributed among two or more nodes in the same geographic location or in different geographic locations. In some deployments, disaggregated network nodes 110 may be used in an integrated access and backhaul (IAB) network, in an open radio access network (O-RAN) (such as a network configuration in compliance with the O-RAN Alliance) , or in a virtualized radio access network (vRAN) , also known as a cloud radio access network (C-RAN) , to facilitate scaling by separating network functionality into multiple units or modules that can be individually deployed.
[0056] The disaggregated network nodes 110 of the wireless communication network 100 may include one or more central units (CUs) , one or more distributed units (DUs) , and one or more radio units (RUs) . A CU may host one or more higher layers, such as an RRC layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer, among other examples. A CU can communicate with a core network either directly (for example, via a backhaul link) or indirectly (for example, via one or more disaggregated control units, such as a non-real-time (Non-RT) RAN intelligent controller (RIC) associated with a Service Management and Orchestration (SMO) framework or a near-real-time (Near-RT) RIC) . A DU may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, or one or more higher physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some examples, a DU also may host a lower PHY layer that is configured to perform functions, such as a fast Fourier transform (FFT) , an inverse FFT (IFFT) , beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. An RU may perform RF processing functions or lower PHY layer functions, such as an FFT, an IFFT, beamforming, or PRACH extraction and filtering, among other examples, according to a functional split, such as a lower layer split (LLS) . In such an architecture, each RU can be operated to handle over the air (OTA) communication with one or more UEs 120. A CU may communicate with one or more DUs via respective midhaul links, such as via F1 interfaces. Each of the DUs may communicate with one or more RUs via respective fronthaul links. Each of the RUs may communicate with one or more UEs 120 via respective RF access links. In some deployments, a UE 120 may be simultaneously served by multiple RUs.
[0057] In some examples, a single network node 110 may include a combination of one or more CUs, one or more DUs, or one or more RUs. In some examples, a CU, a DU, or an RU may be implemented as a virtual unit, such as a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) , among other examples, which may be implemented as a virtual network function, such as in a cloud deployment (for example, an open cloud (O-Cloud) platform) . An SMO framework may support RAN deployment and provisioning of non-virtualized and virtualized network elements.
[0058] In some examples, the wireless communication network 100 may be a heterogeneous network that includes network nodes 110 of various types. Different types of network nodes 110 may generally operate on the same or different operating bands, transmit at different power levels, or serve different coverage areas, each of which may be referred to as or associated with a particular cell 130 (for example, a cell 130a and a cell 130b) .
[0059] The UEs 120 may be physically dispersed throughout the coverage area of the wireless communication network 100, and each UE 120 may be stationary or mobile. A UE 120 may be, may include, or also may be referred to as an access terminal, a mobile station, a client device, or a subscriber unit. A UE 120 may be, include, or be coupled with a cellular phone (for example, a smart phone) , a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (for example, a smart watch, smart clothing, smart glasses, a smart wristband, or smart jewelry) , a gaming device, an entertainment device (for example, a music device, a video device, or a satellite radio) , an XR device, a vehicular component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device) , an artificially intelligent robot or other device implementing artificial intelligence, a UE function of a network node, or any other suitable device or function that may communicate in the wireless communication network 100.
[0060] Some UEs 120 may be classified according to different categories in association with different complexities or different capabilities. UEs 120 in a first category may be associated with relatively low complexity or cost such as NB-IoT devices or eMTC UEs. UEs 120 in a second category may include higher complexity or cost devices, such as mission-critical IoT devices, baseline UEs, high-tier UEs, advanced UEs, full-capability UEs, or premium UEs that are capable of URLLC, eMBB, or precise positioning in the wireless communication network 100. A third category of UEs 120 may have mid-tier complexity or capabilities (for example, capabilities between that of the UEs 120 of the first category and the UEs 120 of the second category) . A UE 120 of the third category may be referred to as a reduced capability UE ( “RedCap UE” ) , a mid-tier UE, an NR-Light UE, or an NR-Lite UE, among other examples.
[0061] In some examples, a network node 110 may be, may include, or may operate as an RU, a TRP, or a base station that communicates with one or more UEs 120 via a radio access link (which may be referred to as a “Uu” link) . The radio access link may include a downlink and an uplink. “Downlink” (or “DL” ) refers to a communication direction from a network node 110 to a UE 120, and “uplink” (or “UL” ) refers to a communication direction from a UE 120 to a network node 110. Downlink and uplink resources may include time domain resources (for example, frames, subframes, slots, and symbols) , frequency domain resources (for example, frequency bands, component carriers (CCs) , subcarriers, resource blocks, and resource elements) , and spatial domain resources (for example, particular transmit directions or beams) .
[0062] Frequency domain resources may be subdivided into bandwidth parts (BWPs) . A BWP may be a block of frequency domain resources (for example, a continuous set of resource blocks (RBs) within a full component carrier bandwidth) that may be configured at a UE-specific level. A UE 120 may be configured with both an uplink BWP and a downlink BWP (which may be the same or different) . Each BWP may be associated with its own numerology (indicating a sub-carrier spacing (SCS) and cyclic prefix (CP) ) . A BWP may be dynamically configured or activated (for example, by a network node 110 transmitting a downlink control information (DCI) configuration to the one or more UEs 120) or reconfigured (for example, in real-time or near-real-time) according to changing network conditions in the wireless communication network 100 or specific requirements of one or more UEs 120. An active BWP defines the operating bandwidth of the UE 120 within the operating bandwidth of the serving cell.
[0063] As used herein, a downlink signal may be or include a reference signal, control information, or data. For example, downlink reference signals include a primary synchronization signal (PSS) , a secondary SS (SSS) , an SS block (SSB) (for example, that includes a PSS, an SSS, and a physical broadcast channel (PBCH) ) , a demodulation reference signal (DMRS) , a phase tracking reference signal (PTRS) , a tracking reference signal (TRS) , and a channel state information (CSI) reference signal (CSI-RS) , among other examples. A downlink signal carrying control information or data may be transmitted via a downlink channel. Downlink channels may include one or more control channels for transmitting control information and one or more data channels for transmitting data. Downlink reference signals may be transmitted in addition to, or multiplexed with, downlink control channel communications or downlink data channel communications. A downlink control channel may be specifically used to transmit DCI from a network node 110 to a UE 120. DCI generally contains the information the UE 120 needs to identify RBs in a subsequent subframe and how to decode them, including a modulation and coding scheme (MCS) or redundancy version parameters. Different DCI formats carry different information, such as scheduling information in the form of downlink or uplink grants, slot format indicators (SFIs) , preemption indicators (PIs) , transmit power control (TPC) commands, hybrid automatic repeat request (HARQ) information, new data indicators (NDIs) , among other examples. A downlink data channel may be used to transmit downlink data (for example, user data associated with a UE 120) from a network node 110 to a UE 120. Downlink control channels may include physical downlink control channels (PDCCHs) , and downlink data channels may include physical downlink shared channels (PDSCHs) . Control information or data communications may be transmitted on a PDCCH and PDSCH, respectively. For example, a PDCCH can carry DCI, while a PDSCH can carry a MAC control element (MAC-CE) , an RRC message, or user data, among other examples. Each PDSCH may carry one or more transport blocks (TBs) of data.
[0064] As used herein, an uplink signal may include a reference signal, control information, or data. For example, uplink reference signals include a sounding reference signal (SRS) , a PTRS, and a DMRS, among other examples. An uplink signal carrying control information or data may be transmitted via an uplink channel. An uplink channel may include one or more control channels for transmitting control information and one or more data channels for transmitting data. Uplink reference signals may be transmitted in addition to, or multiplexed with, uplink control channel communications or uplink data channel communications. An uplink control channel may be specifically used to transmit uplink control information (UCI) from a UE 120 to a network node 110. An uplink data channel may be used to transmit uplink data (for example, user data associated with a UE 120) from a UE 120 to a network node 110. Uplink control channels may include physical uplink control channels (PUCCHs) , and uplink data channels may include physical uplink shared channels (PUSCHs) . Control information or data communications may be transmitted on a PUCCH and PUSCH, respectively. For example, a PUCCH can carry UCI, while a PUSCH can carry a MAC-CE, an RRC message, or user data, among other examples. UCI can include a scheduling request (SR) , HARQ feedback information (for example, a HARQ acknowledgement (ACK) indication or a HARQ negative acknowledgement (NACK) indication) , uplink power control information (for example, an uplink TPC parameter) , or CSI, among other examples. CSI can include a channel quality indicator (CQI) (indicative of downlink channel conditions to facilitate selection of transmission parameters, such as an MCS, by a network node 110) , a precoding matrix indicator (PMI) , a CSI-RS resource indicator (CRI) (for example, indicative of a beam used to transmit a CSI-RS) , an SS / PBCH resource block indicator (SSBRI) (for example, indicative of a beam used to transmit an SSB) , a layer indicator (LI) , a rank indicator (RI) , or measurement information (for example, a layer 1 (L1) -reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, among other examples) which can be used for beam management, among other examples. Each PUSCH may carry one or more TBs of data.
[0065] The information (for example, data, control information, or reference signal information) transmitted by a network node 110 to a UE 120, or vice versa, may be represented as a sequence of binary bits that are mapped (for example, modulated) to an analog signal waveform (for example, a discrete Fourier transform (DFT) -spread-orthogonal frequency division multiplexing (OFDM) (DFT-s-OFDM) waveform or a CP-OFDM waveform) that is transmitted by the network node 110 or UE 120 over a wireless communication channel. In some examples, the network node 110 or the UE 120 (for example, using the processing system 145 or the processing system 140, respectively) may select an MCS (for example, an order of quadrature amplitude modulation (QAM) , such as 64-QAM, 128-QAM, or 256-QAM, among other examples) for a downlink signal or an uplink signal. For example, the network node 110 may select an MCS for a downlink signal in accordance with UCI received from the UE 120 or may transmit, to the UE 120, an indication of an MCS to be applied for an uplink signal.
[0066] A network node 110 or a UE 120 (such as by using the processing system 145 or the processing system 140, respectively, or one or more coupled modems) may perform signal processing on the information (such as filtering, amplification, modulation, digital-to-analog conversion, an IFFT operation, multiplexing, interleaving, mapping, or encoding, among other examples) to generate a processed signal in accordance with the selected MCS. In some examples, the network node 110 or the UE 120 (for example, using the processing system 145 or the processing system 140, respectively, or one or more coupled encoders or modems) may perform a channel coding operation or a forward error correction (FEC) operation to control errors in transmitted information. For example, the network node 110 or the UE 120 may perform an encoding operation to generate encoded information (such as by selectively introducing redundancy into the information, typically using an error correction code (ECC) , such as a polar code or a low-density parity-check (LDPC) code) . The network node 110 or the UE 120 (for example, using the processing system 145 or one or more modems) may further perform spatial processing (for example, precoding) on the encoded information to generate one or more processed or precoded signals for downlink or uplink transmission, respectively. In some examples, the network node 110a or the UE 120a may perform codebook-based precoding or non-codebook-based precoding. Codebook-based precoding may involve selecting a precoder (for example, a precoding matrix) using a codebook. For example, the network node 110a may provide precoding information indicating which precoder, defined by the codebook, is to be used by the UE 120a. Non-codebook-based precoding may involve selecting or deriving a precoder based on, or otherwise associated with, one or more downlink or uplink signal measurements. The network node 110a or the UE 120a may transmit the processed downlink or uplink signals, respectively, via one or more antennas.
[0067] The network node 110a or the UE 120a may receive uplink signals or downlink signals, respectively, via one or more antennas. The network node 110a or the UE 120a (for example, using the processing system 145 or the processing system 140, respectively, or one or more coupled modems) may perform signal processing (for example, in accordance with the MCS) on the received uplink or downlink signals, respectively (such as filtering, amplification, demodulation, analog-to-digital conversion, an FFT operation, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , to map the received signal (s) to a sequence of binary bits (for example, received information) that estimates the information transmitted by the network node 110 or the UE 120 via the downlink or uplink signals. The network node 110a or the UE 120a (for example, using the processing system 145 or the processing system 140, respectively, or a coupled decoder or one or more modems) may decode the received information (such as by using an ECC, a decoding operation, or an FEC operation) to detect errors or correct bit errors in the received information to generate decoded information. The decoded information may estimate the information transmitted via the downlink or uplink signals.
[0068] In some examples, a UE 120 and a network node 110 may perform MIMO communication. MIMO communication generally refers to transmitting or receiving multiple signals (such as multiple layers or multiple data streams) simultaneously over the same time and frequency resources. A network node 110 or a UE 120 may communicate using single-user MIMO or multi-user MIMO (MU-MIMO) , the latter of which being used by a network node 110 to simultaneously transmit signals to multiple UEs 120. MIMO techniques may involve spatial multiplexing (multi-layer transmission) or beamforming. To implement beamforming, the amplitudes or phases of signals transmitted via antenna elements may be modulated and shifted relative to each other (such as by manipulating a phase shift, a phase offset, or an amplitude) to generate one or more beams. For example, a network node 110 may generate one or more beams 160a, and a UE 120 may generate one or more beams 160b. The term “beam” may refer to a directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction, a directional reception of a wireless signal from a transmitting device or otherwise in a desired direction, a direction associated with such a directional transmission or directional reception, a set of directional resources associated with a signal transmission or signal reception (for example, an angle of arrival, a horizontal direction, or a vertical direction) , or a set of parameters or resources associated with one or more aspects of a directional signal, among other examples.
[0069] In some examples, a network node 110 or a UE 120 may implement massive MIMO, which may be associated with an increased (for example, “massive” ) quantity of antennas at the network node 110 or at the UE 120, such as in a network implementing mmWave technology, which enables more precise beamforming or reduced interference. In some examples, the wireless communication network 100 may implement multi-TRP (mTRP) operation (including redundant transmission or reception on multiple TRPs) or non-coherent joint transmission (NC-JT) .
[0070] The network node 110 and the UE 120 may establish a communication link or beam pair, and otherwise increase reliability, throughput, signal strength, or other signal properties for MIMO communications, by performing beam management operations, such as an initial beam acquisition operation, a beam refinement operation, or a beam recovery operation. For example, an initial beam acquisition operation may involve the network node 110 transmitting signals (for example, SSBs or other signals) via respective beams (for example, of the beams 160 of the network node 110) and the UE 120 receiving and measuring the signal (s) via respective beams of multiple beams (for example, from the beams 160 of the UE 120) to identify a best beam (or beam pair) for communication between the UE 120 and the network node 110. A beam refinement operation may involve a first device (for example, the UE 120 or the network node 110) transmitting signal (s) via a subset of beams (for example, identified based on, or otherwise associated with, measurements reported as part of one or more other beam management operations) . A second device (for example, the network node 110 or the UE 120) may receive the signal (s) via a single beam (for example, to identify the best beam for communication from the subset of beams) . The beam (s) may be identified or defined via one or more spatial parameters, such as a transmission configuration indicator (TCI) state or a quasi co-location (QCL) parameter, among other examples.
[0071] Some aspects and techniques as described herein may be implemented, at least in part, using an artificial intelligence (AI) program (for example, referred to herein as an “AI / ML model” ) , such as a program that includes a machine learning (ML) model or an artificial neural network (ANN) model. The AI / ML model may be deployed at one or more devices 165 (for example, one or more network nodes 110, one or more UEs 120, one or more servers, or one or more components of a cloud computing network, among other examples) . For example, in a deployment in which AI / ML functionality is performed independently at a device 165, sometimes referred to as “overlay AI / ML, ” the AI / ML model (or an instance or portion of the AI / ML model) may be deployed at a UE 120 (for example, by the processing system 140) , a network node 110 (for example, by the processing system 145) , one or more servers, or one or more components of a cloud computing network, among other examples. Additionally, or alternatively, in a deployment where AI / ML functionality is coordinated between different devices 165, sometimes referred to as “coordinated AI / ML, ” or performed at all device and network layers, sometimes referred to as “native AI / ML, ” the AI / ML model (or an instance of the AI / ML model) may be deployed at multiple devices 165 (for example, a first portion of the AI / ML model may be deployed at a UE 120 and a second portion of the AI / ML model may be deployed at a network node 110) . In other examples of coordinated AI / ML or native AI / ML, a first AI / ML model may be deployed at a UE 120 and a second AI / ML model may be deployed at a network node 110. The AI / ML model (s) may be configured to enhance various aspects of the wireless communication network 100 (for example, to increase privacy, reliability, or efficient use of network bandwidth, or to reduce latency, among other examples) . For example, the AI / ML model (s) may be trained to identify patterns or relationships in data corresponding to the wireless communication network 100, a device, or an air interface, among other examples. The AI / ML model (s) may support operational decisions relating to one or more aspects associated with wireless communications devices, networks, or services.
[0072] Accordingly, in some examples, the AI / ML model (s) may enable AI-as-a-Service (for example, an end-to-end AI / ML service via a user plane) for use cases, such as a self-organizing network (SON) , minimization of drive test (MDT) , quality of experience (QoE) , positioning, sensing, predictive mobility, or traffic prediction, among other examples. In some examples, AI-as-a-Service use cases may include measurement collection reporting by a UE 120, device selection criteria (for example, according to a geographical area where measurements are to be collected or UE capabilities to be used to collected measurements) , or reporting configurations (for example, reporting parameters such as location, time, or sensor information, among other examples) . Additionally, or alternatively, the AI / ML model (s) may enable AI / ML procedures (for example, RAN-triggered service establishment, configuration, inferencing using UE-side or network-side models, performance monitoring or management, or capability signaling, among other examples) . Additionally, or alternatively, the AI / ML model (s) may enable RAN-based AI / ML services via one or more application program interfaces (APIs) or management interfaces for use cases, such as beam management, radio resource monitoring (RRM) relaxation, mobility prediction, load prediction, network energy savings, or coverage and capacity improvements, among other examples) .
[0073] In some aspects, the UE 120 may include a processing system 140 with a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a reconfiguration message indicating a set of inference configuration candidates and may transmit an indication of which inference configuration candidates in the set are supported by the UE and which inference configuration candidates in the set are unsupported by the UE, where each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code. Additionally, or alternatively, as described in more detail elsewhere herein, the communication manager 150 may receive an indication of a set of report configurations and may transmit an indication of which report configurations in the set can be supported concurrently. Alternatively, as described in more detail elsewhere herein, the communication manager 150 may receive an indication of a set of reporting configurations and may transmit an indication of available processing units based at least in part on the set of reporting configurations. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.
[0074] In some aspects, the network node 110 may include a processing system 145 with a communication manager 155. As described in more detail elsewhere herein, the communication manager 155 may transmit a reconfiguration message indicating a set of inference configuration candidates and may receive an indication of which inference configuration candidates in the set are supported by the UE 120 and which inference configuration candidates in the set are unsupported by the UE 120, where each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code. Additionally, or alternatively, as described in more detail elsewhere herein, the communication manager 155 may transmit an indication of a set of report configurations and may receive an indication of which report configurations in the set can be supported concurrently. Alternatively, as described in more detail elsewhere herein, the communication manager 155 may transmit an indication of a set of reporting configurations and may receive an indication of available processing units based at least in part on the set of reporting configurations. Additionally, or alternatively, the communication manager 155 may perform one or more other operations described herein.
[0075] The network node 110, the processing system 145 of the network node 110, the UE 120, the processing system 140 of the UE 120, or any other component (s) of Fig. 1 may implement one or more techniques or perform one or more operations associated with flexible processing unit occupation for inference, as described in more detail elsewhere herein. For example, the processing system 145 of the network node 110, or the processing system 140 of the UE 120 may perform or direct operations of, for example, process 1000 of Fig. 10, process 1100 of Fig. 11, process 1200 of Fig. 12, process 1300 of Fig. 13, process 1400 of Fig. 14, process 1500 of Fig. 15, or other processes as described herein (alone or in conjunction with one or more other processors) . Memory of the network node 110 may store data and program code (or instructions) for the network node 110. In some examples, the memory of the network node 110 may store data relating to a UE 120, such as RRC state information or a UE context. Memory of a UE 120 may store data and program code (or instructions) for the UE 120, such as context information. In some examples, the memory of the UE 120 or the memory of the network node 110 may include a non-transitory computer-readable medium storing a set of instructions for wireless communication. For example, the set of instructions, when executed by one or more processors (for example, of the processing system 145 or the processing system 140) of the network node 110, or the UE 120, may cause the one or more processors to perform process 1000 of Fig. 10, process 1100 of Fig. 11, process 1200 of Fig. 12, process 1300 of Fig. 13, process 1400 of Fig. 14, process 1500 of Fig. 15, or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, or interpreting the instructions, among other examples.
[0076] In some aspects, a UE (e.g., the UE 120 or apparatus 1600 of Fig. 16) may include means for receiving a reconfiguration message indicating a set of inference configuration candidates; and means for transmitting an indication of which inference configuration candidates in the set are supported by the UE and which inference configuration candidates in the set are unsupported by the UE, where each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code. Additionally, or alternatively, the UE may include means for receiving an indication of a set of report configurations; and means for transmitting an indication of which report configurations in the set can be supported concurrently. Alternatively, the UE may include means for receiving an indication of a set of reporting configurations; and means for transmitting an indication of available processing units based at least in part on the set of reporting configurations. In some aspects, the means for the UE to perform operations described herein may include, for example, one or more of communication manager 150, processing system 140, a radio, one or more RF chains, one or more transceivers, one or more antennas, one or more modems, a reception component (for example, reception component 1602 depicted and described in connection with Fig. 16) , or a transmission component (for example, transmission component 1604 depicted and described in connection with Fig. 16) , among other examples.
[0077] In some aspects, a network node (e.g., the network node 110, an RU, a DU, a CU, or apparatus 1700 of Fig. 17) may include means for transmitting a reconfiguration message indicating a set of inference configuration candidates; and means for receiving an indication of which inference configuration candidates in the set are supported by a UE and which inference configuration candidates in the set are unsupported by the UE, where each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code. Additionally, or alternatively, the network node may include means for transmitting an indication of a set of report configurations; and means for receiving an indication of which report configurations in the set can be supported concurrently. Alternatively, the network node may include means for transmitting an indication of a set of reporting configurations; or means for receiving an indication of available processing units based at least in part on the set of reporting configurations. In some aspects, the means for the network node to perform operations described herein may include, for example, one or more of communication manager 155, processing system 145, a radio, one or more RF chains, one or more transceivers, one or more antennas, one or more modems, a reception component (for example, reception component 1702 depicted and described in connection with Fig. 17) , or a transmission component (for example, transmission component 1704 depicted and described in connection with Fig. 17) , among other examples.
[0078] Fig. 2 is a diagram illustrating an example 200 of AI / ML based beam management. As shown in Fig. 2, an AI / ML model 210 may be deployed at or on a UE 120. For example, a model inference host (such as a model inference host) may be deployed at, or on, a UE 120. The AI / ML model 210 may enable the UE 120 to determine one or more inferences or predictions based on data input to the AI / ML model 210.
[0079] For example, as shown by reference number 215, an input to the AI / ML model 210 may include measurements associated with a first set of beams. For example, a network node 110 may transmit one or more signals using respective beams from the first set of beams. The UE 120 may perform measurements (e.g., L1 RSRP measurements or other measurements) of the first set of beams to obtain a first set of measurements. For example, each beam, from the first set of beams, may be associated with one or more measurements performed by the UE 120. The UE 120 may input the first set of measurements (e.g., L1 RSRP measurement values) into the AI / ML model 210 along with information associated with the first set of beams or a second set of beams, such as a beam direction (e.g., spatial direction) , beam width, beam shape, or other characteristics of the respective beams from the first set of beams or the second set of beams.
[0080] As shown by reference number 220, the AI / ML model 210 may output one or more predictions. The one or more predictions may include predicted measurement values (e.g., predicted L1 RSRP measurement values) associated with the second set of beams. This may reduce a quantity of beam measurements that are performed by the UE 120, thereby conversing power of the UE 120 and network resources that would have otherwise been used to measure all beams included in the first set of beams and the second set of beams. This type of prediction may be referred to as a codebook based spatial domain selection or prediction.
[0081] As another example, an output of the AI / ML model 210 may include a point-direction, an angle of departure (AoD) , and / or an angle of arrival (AoA) of a beam included in the second set of beams. This type of prediction may be referred to as a non-codebook based spatial domain selection or prediction. As another example, multiple measurement report or values, collected at different points in time, may be input to the AI / ML model 210. This may enable the AI / ML model 210 to output codebook based or non-codebook based predictions for a measurement value, an AoD, and / or an AoA, among other examples, of a beam at a future time. The output (s) of the AI / ML model 210, as described herein, may facilitate initial access procedures, secondary cell group (SCG) setup procedures, beam refinement procedures (e.g., a P2 beam management procedure or a P3 beam management procedure) , link quality or interference adaptation procedure, beam failure and / or beam blockage predictions, or radio link failure predictions, among other examples.
[0082] In some examples, the first set of beams may be referred to as Set B beams and the second set of beams may be referred to as Set A beams. In some examples, the first set of beams (e.g., the Set B beams) may be a subset of the second set of beams (e.g., the Set A beams) . In some other examples, the first set of beams and the second set of beams may be different beams or may be mutually exclusive sets. For example, the first set of beams (e.g., the Set B beams) may include wide beams (e.g., unrefined beams or beams having a beam width that satisfies a first threshold) and the second set of beams (e.g., the Set A beams) may include narrow beams (e.g., refined beams or beams having a beam width that satisfies a second threshold) . In one example, the AI / ML model 210 may perform spatial-domain beam predictions for beams included in the Set A beams based on measurement results of beams included in the Set B beams. As another example, the AI / ML model 210 may perform temporal beam prediction for beams included in the Set A beams based on historic measurement results of beams included in the Set B beams.
[0083] Typically, the UE 120 may have limitations related to beam prediction (e.g., due to hardware constraints, software constraints, or a combination thereof) . Therefore, the UE 120 will generally reject a configuration from the network, associated with beam prediction, if the configuration exceeds a capability of the UE 120. In some aspects described herein, the UE 120 may transmit a capability message, associated with beam prediction, to the network node 110. Therefore, the network node 110 may only provide configurations, associated with the beam prediction, that are within a capability of the UE 120. As a result, power, processing resources, and network resources are conserved that otherwise would have been wasted if the network node 110 were to provide an unsupported configuration for beam prediction to the UE 120.
[0084] As indicated above, Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.
[0085] Fig. 3 is a diagram of an example 300 associated with reason codes for reporting inference capabilities. As shown in Fig. 3, a network node 110 (e.g., a base station, a CU, a DU, or an RU) may communicate with a UE 120. In some aspects, the network node 110 and the UE 120 may be part of a wireless network (e.g., the wireless communication network 100) . The UE 120 and the network node 110 may have established a wireless connection prior to operations shown in Fig. 3. Fig. 3 depicts an example sequence of operations associated with the UE 120 reporting reasons why one or more inference configurations are unsupported.
[0086] In some aspects, as shown by reference number 305, the UE 120 may transmit, and the network node 110 may receive, capability information. The capability information may be included in a capability report (e.g., a UECapabilityInformation report, as defined in 3GPP specifications) . The UE 120 may transmit the capability information via an uplink communication, such as a UE assistance information (UAI) communication, among other examples. The capability information may indicate supported functionalities at the UE 120, such as an ability to perform inference (e.g., temporal prediction, spatial prediction, or a combination thereof, using one or more AI / ML models) .
[0087] In some aspects, as shown by reference number 310, the network node 110 may transmit, and the UE 120 may receive, a reconfiguration message. For example, the reconfiguration message may be an RRC reconfiguration message. The reconfiguration message may indicate a set of inference configuration candidates. In some aspects, the set of inference configuration candidates may be indicated using a set of report configurations. For example, the reconfiguration message may include a set of CSI-ReportConfig information elements (IEs) that define the set of inference configuration candidates. Additionally, or alternatively, the set of inference configuration candidates may be indicated using sets of inference parameters. For example, each set of inference parameters (e.g., a type of input reference signal, a quantity of input measurements, a type of output, or a quantity of output occasions, among other examples) may be mapped (e.g., by the UE 120) to a corresponding report configuration representing an inference configuration candidate.
[0088] In some aspects, as shown by reference number 315, the UE 120 may determine which inference configuration candidates in the set are supported by the UE 120 and which inference configuration candidates in the set are unsupported. Additionally, the UE 120 may determine why an inference configuration candidate is unsupported (e.g., the UE 120 lacks an AI / ML model for the inference configuration candidate locally, or computational resources for the inference configuration candidate exceed a capability of the UE 120, among other examples) .
[0089] In some aspects, as shown by reference number 320, the UE 120 may transmit, and the network node 110 may receive, an indication of which inference configuration candidates in the set are supported and which inference configuration candidates in the set are unsupported. In some aspects, the indication may include identifiers associated with respective report configurations. For example, each report configuration may include an identifier (e.g., a CSI-ReportConfigId, as defined in 3GPP specifications) , such that the UE 120 may indicate which report configurations are supported and which are unsupported using corresponding identifiers. Additionally, or alternatively, the indication may include identifiers associated with respective sets of inference parameters. For example, each set of inference parameters may include an identifier, such that the UE 120 may indicate which sets of inference parameters are supported and which are unsupported using corresponding identifiers.
[0090] The indication may further include, for each inference configuration candidate in the set that is unsupported, a reason code. The reason code may indicate why the inference configuration candidate is unsupported. Accordingly, the reason code may, explicitly or implicitly, indicate a combination of inference reports unsupported by the UE 120. For example, the reason code may explicitly indicate that the inference configuration candidate is unsupported due to a concurrency restriction with other inference configuration candidates, as described in greater detail below. In another example, the reason code may implicitly indicate that the UE 120 does not support any combinations of inference reports that include the inference configuration candidate, whether temporarily or permanently, as described in greater detail below.
[0091] The reason code may indicate whether a corresponding model is temporarily unavailable or permanently unavailable. For example, an inference configuration candidate may be associated with an AI / ML model that is available remotely, such that the UE 120 could download the AI / ML model in order to support the inference configuration candidate. The inference configuration candidate may be associated with the AI / ML model via an “associated ID” that links the configuration candidate to the model. In another example, an inference configuration candidate may be associated with an AI / ML model that is unavailable to the UE 120, such that the UE 120 cannot support the inference configuration candidate.
[0092] Additionally, or alternatively, the reason code may indicate that the UE 120 lacks computational resources. In some aspects, the UE 120 may lack hardware or software resources to perform inference, according to an inference configuration candidate, even if maximal resources are available. Alternatively, the UE 120 may temporarily lack hardware or software resources to perform inference according to an inference configuration candidate. For example, the reason code may indicate that the computational resources will be available if a concurrency restriction is resolved. Accordingly, the UE 120 may indicate that, if a different unsupported inference configuration candidate is discarded, the UE 120 may support the inference configuration candidate. Additionally, or alternatively, the reason code may indicate that the computational resources will be available if an inference parameter restriction is resolved. Accordingly, the UE 120 may indicate that, if the inference configuration candidate is adjusted (e.g., by changing a number of future occasions to predict, a number of Set A beams, a number of Set B beams, a type of CSI prediction, a type of Set A beams, a type of Set B beams, or a QCL relationship between Set A beams and Set B beams, among other examples) , the UE 120 may support the inference configuration candidate as adjusted.
[0093] In some aspects, the indication may further indicate combinations of inference configuration candidates in the set that are unsupported for concurrency. For example, the UE 120 might report that some combinations of inference configuration candidates may be supported concurrently while other combinations of inference configuration candidates are not supported concurrently (e.g., due to hardware or software constraints at the UE 120) . The indication may include tuples, or other combinations, of CSI-ReportConfigIds (or other identifiers) associated with the inference configuration candidates.
[0094] In some aspects, as shown by reference number 325, the network node 110 may transmit, and the UE 120 may receive, a reconfiguration message. For example, the reconfiguration message may be an RRC message. The reconfiguration message may indicate which inference configurations, from the set of inference configurations, are to be activated. Accordingly, the network node 110 may configure the UE 120 to perform inference according to the reason codes from the UE 120. For example, the network node 110 may activate inference configurations that are supported, discard inference configurations that were conflicted out by concurrency, or request the UE 120 to download an AI / ML model for unsupported inference configurations, among other examples.
[0095] In some aspects, as shown by reference number 330, the UE 120 may transmit, and the network node 110 may receive, assistance information. The UE 120 may transmit the capability information via an uplink communication, such as a UAI communication, among other examples. The assistance information may include an update of which inference configuration candidates in the set are supported and which inference configuration candidates in the set are unsupported. For example, the UE 120 may have downloaded an AI / ML model such that a previously unsupported inference configuration is now supported. In another example, the network node 110 may have modified a previously unsupported inference configuration such that the updated configuration is now supported. In another example, the UE 120 may have more hardware or software resources available such that a previously unsupported inference configuration is now supported.
[0096] By using techniques as described in connection with Fig. 3, the network node 110 may use the reason codes from the UE 120 to activate some (and refrain from activating other) inference configurations. As a result, the network node 110 may improve resource allocation for the UE 120 by using inference without exceeding capabilities of the UE 120.
[0097] As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.
[0098] Fig. 4 is a diagram of an example 400 associated with flexible processing unit occupation for inference using concurrency reporting. As shown in Fig. 4, a network node 110 (e.g., a base station, a CU, a DU, or an RU) may communicate with a UE 120. In some aspects, the network node 110 and the UE 120 may be part of a wireless network (e.g., the wireless communication network 100) . The UE 120 and the network node 110 may have established a wireless connection prior to operations shown in Fig. 4. Fig. 4 depicts an example sequence of operations associated with the UE 120 negotiating, with the network node 110, report configurations that can be supported concurrently.
[0099] In some aspects, as shown by reference number 405, the UE 120 may transmit, and the network node 110 may receive, capability information. The capability information may be included in a capability report (e.g., a UECapabilityInformation report, as defined in 3GPP specifications) . The UE 120 may transmit the capability information via an uplink communication, such as a UAI communication, among other examples. The capability information may indicate supported functionalities at the UE 120, such as an ability to perform inference (e.g., temporal prediction, spatial prediction, or a combination thereof, using one or more AI / ML models) .
[0100] In some aspects, as shown by reference number 410, the network node 110 may transmit, and the UE 120 may receive, an indication of a set of report configurations from a network node. For example, the indication may be included in a reconfiguration message, such as an RRC reconfiguration message. In some aspects, the set of report configurations may include at least one inactive semi-persistent or aperiodic report configuration. Additionally, or alternatively, the set of report configurations may include at least one inactive report configuration associated with an applicable functionality inquiry. For example, the set of report configurations may include at least one “dummy” configuration (e.g., a CSI-ReportConfig IE, as defined in 3GPP specifications, that is not active) . The network node 110 may use dummy configurations to inquire regarding capabilities of the UE 120 before activating configurations for the UE 120. In some aspects, the set of report configurations may include at least one aperiodic trigger state that is inactive before the UE 120 indicates which report configurations in the set can be supported concurrently. For example, the aperiodic trigger state (s) may be inactive (or otherwise untriggered) at least before (and optionally during) a slot in which the UE 120 indicates which report configurations in the set can be supported concurrently.
[0101] The UE 120 and the network node 110 may dynamically negotiate which report configurations can be activated concurrently. For example, as shown by reference number 415, the UE 120 may transmit, and the network node 110 may receive, an indication of which report configurations in the set can be supported concurrently. The UE 120 may transmit the indication via an uplink communication, such as a UAI communication or a different RRC message, among other examples. Alternatively, the UE 120 may transmit the indication via a control element, such as a MAC-CE. Alternatively, the UE 120 may transmit the indication via control information, such as UCI.
[0102] In some aspects, the UE 120 may report that some combinations of report configurations can be processed concurrently without exceeding hardware or software constraints of the UE 120. Additionally, or alternatively, the UE 120 may report that some combinations of report configurations cannot be processed concurrently without exceeding hardware or software constraints of the UE 120. Both supported and unsupported concurrency reporting is depicted in connection with Fig. 5. In some aspects, the UE 120 may use a rule (e.g., stored in a memory of, or otherwise programmed into, the UE 120) to determine whether to report supported or unsupported combinations. Alternatively, the network node 110 may indicate whether to report supported or unsupported combinations. Alternatively, the UE 120 may determine whether to report supported or unsupported combinations (e.g., by selecting in order to reduce overhead) , such that the indication further indicates whether reported combinations are supported ones or unsupported ones.
[0103] In some aspects, the set of report configurations may be associated with inference. Accordingly, the UE 120 and the network node 110 may negotiate for report configurations that use inference but not for report configurations that do not use inference. For example, the network node 110 may transmit, and the UE 120 may receive, at least one report configuration unassociated with inference, such that the UE 120 omits the at least one report configuration from the indication of which report configurations in the set can be supported concurrently.
[0104] In some aspects, the indication of which report configurations in the set can be supported concurrently may be included in a set of payloads corresponding to the set of report configurations. For example, the UE 120 may transmit a payload for each report configuration in the set, and each payload may include at least one bit indicating whether the report configuration is updated. Therefore, a bit indicating “No” for a report configuration indicates that the report configuration is not supported for concurrency with other report configurations in the set. In some aspects, the indication may further indicate a duration of time after which a supported report configuration in the set is expected to be unsupported. For example, the UE 120 may anticipate that hardware or software resources allocated to the supported report configuration may be re-allocated to a different operation in the future. Additionally, or alternatively, the indication may further indicate a duration of time after which an unsupported report configuration in the set is expected to be supported. For example, the UE 120 may project that hardware or software resources will become free in the future for allocation to the unsupported report configuration.
[0105] In some aspects, the indication may further include at least one reason code associated with an unsupported report configuration in the set. The reason code may be as described above in connection with Fig. 3.
[0106] As described below in connection with Fig. 5, one or more unsupported report configurations in the set, indicated using the indication, may be associated with lower priorities relative to one or more supported report configurations in the set. For example, the UE 120 may rank the report configurations (e.g., according to priorities determined per 3GPP specifications, among other examples) . Accordingly, only lowest ranked report configurations may be indicated as unsupported (e.g., in corresponding payloads) . In other words, a first report configuration ranked lower than a second report configuration may not be indicated as supported if the second report configuration is indicated as unsupported.
[0107] By using techniques as described in connection with Fig. 4, the network node 110 may use the indication from the UE 120 to activate some (and refrain from activating other) inference configurations. As a result, the network node 110 may improve resource allocation for the UE 120 by using inference without exceeding capabilities of the UE 120.
[0108] As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with regard to Fig. 4.
[0109] Fig. 5 is a diagram of an example 500 associated with concurrency reporting. As shown in Fig. 5, a UE 120 may receive an indication of a set 503 of report configurations 501a through 501i. For example, the set 503 may include an inactive semi-persistent report, an inactive aperiodic report, an inactive report configuration associated with an applicable functionality inquiry, an aperiodic trigger state that is inactive, or a combination thereof.
[0110] As further shown in Fig. 5, the UE 120 may use a first reporting option indicated by reference number 505a. Accordingly, the UE 120 may report supported concurrency combinations 507a and 507b. Each supported concurrency combination 507 may include a subset of report configurations 501 (from the set 503) . Additionally, or alternatively, the UE 120 may use a second reporting option indicated by reference number 505b. Accordingly, the UE 120 may report unsupported concurrency combinations 509a and 509b. Each unsupported concurrency combination 509 may include a subset of report configurations 501 (from the set 503) . The UE 120 may indicate supported combinations, unsupported combinations, or a combination thereof, in RRC signaling, control elements, or control information, among other examples.
[0111] As indicated above, Fig. 5 is provided as an example. Other examples may differ from what is described with regard to Fig. 5.
[0112] Fig. 6 is a diagram of an example 600 associated with concurrency reporting. As shown in Fig. 6, a UE 120 may receive an indication of a set 603 of report configurations 601a through 601i. For example, the set 603 may include an inactive semi-persistent report, an inactive aperiodic report, an inactive report configuration associated with an applicable functionality inquiry, an aperiodic trigger state that is inactive, or a combination thereof.
[0113] As further shown in Fig. 6, the UE 120 may rank the report configurations 601 (e.g., according to priorities determined per 3GPP specifications, among other examples) . Accordingly, the UE 120 may report supported report configurations 605a and unsupported report configurations 605b. The unsupported report configurations (e.g., configurations 601e, 601i, and 601h in the example 600) may be associated with lower priorities relative to the supported report configurations (e.g., configurations 601a, 601c, 601g, 601b, 601d, and 601f in the example 600) .
[0114] As indicated above, Fig. 6 is provided as an example. Other examples may differ from what is described with regard to Fig. 6.
[0115] Fig. 7 is a diagram of an example 700 associated with flexible processing unit occupation for inference using dynamic negotiation. As shown in Fig. 7, a network node 110 (e.g., a base station, a CU, a DU, or an RU) may communicate with a UE 120. In some aspects, the network node 110 and the UE 120 may be part of a wireless network (e.g., the wireless communication network 100) . The UE 120 and the network node 110 may have established a wireless connection prior to operations shown in Fig. 7. Fig. 7 depicts an example sequence of operations associated with the UE 120 dynamically indicating how many APUs (and optionally CPUs) are available.
[0116] In some aspects, as shown by reference number 705, the UE 120 may transmit, and the network node 110 may receive, capability information. The capability information may be included in a capability report (e.g., a UECapabilityInformation report, as defined in 3GPP specifications) . The UE 120 may transmit the capability information via an uplink communication, such as a UAI communication, among other examples. The capability information may indicate supported functionalities at the UE 120, such as an ability to perform inference (e.g., temporal prediction, spatial prediction, or a combination thereof, using one or more AI / ML models) .
[0117] In some aspects, as shown by reference number 710, the network node 110 may transmit, and the UE 120 may receive, an indication of a set of report configurations from a network node. For example, the indication may be included in a reconfiguration message, such as an RRC reconfiguration message
[0118] In some aspects, as shown by reference number 715, the UE 120 may transmit, and the network node 110 may receive, an indication of available processing units based at least in part on the set of reporting configurations. In some aspects, the indication of available processing units may be for APUs. Accordingly, the UE 120 may report a static maximum number of CPUs and a dynamic number of available APUs. Alternatively, the indication of available processing units may be for CPUs. Accordingly, the UE 120 may report a static maximum number of APUs and a dynamic number of available CPUs. Alternatively, the indication of available processing units may be for both CPUs and APUs.
[0119] The UE 120 may transmit the indication via an uplink communication, such as a UAI communication or a different RRC message, among other examples. Alternatively, the UE 120 may transmit the indication via a control element, such as a MAC-CE. Alternatively, the UE 120 may transmit the indication via control information, such as UCI.
[0120] The indication may be on a per-CC-basis or a cross-CC-basis. For example, the UE 120 may report an available number of APUs (and optionally CPUs) on a single CC. Additionally, or alternatively, the UE 120 may report an available number of APUs (and optionally CPUs) across all (active) CCs.
[0121] Additional, or alternatively, as shown by reference number 720, the UE 120 may transmit, and the network node 110 may receive, an indication of how many processing units are occupied by each report configuration in the set. For example, the UE 120 may report that a first report configuration will occupy 2 APUs and 1 CPU, that a second report configuration will occupy 2 CPUs, and that a third report configuration will occupy 3 APUs, among other examples. In some aspects, the set of report configurations may be associated with inference. Accordingly, the UE 120 may indicate available APUs for report configurations that use inference but not indicate available CPUs for report configurations that do not use inference (e.g., as described below in connection with Fig. 9) . For example, the network node 110 may transmit, and the UE 120 may receive, at least one report configuration unassociated with inference, such that the UE 120 omits the at least one report configuration from the indication of how many processing units are occupied by each report configuration in the set.
[0122] In some aspects, as shown by reference number 725, the UE 120 may refrain from updating a report, associated with a report configuration in the set, in response to a lack of available processing units. For example, the UE 120 may determine a lowest priority report configuration (e.g., according to 3GPP specifications) to drop. As described below in connection with Fig. 8, the UE 120 may consider all report configurations associated with inference, report configurations unassociated with inference, or all report configurations in determining which report configuration to drop.
[0123] By using techniques as described in connection with Fig. 7, the network node 110 may use the indication from the UE 120 to activate some (and refrain from activating other) report configurations. As a result, the network node 110 may improve resource allocation for the UE 120 by using inference without exceeding capabilities of the UE 120.
[0124] As indicated above, Fig. 7 is provided as an example. Other examples may differ from what is described with regard to Fig. 7.
[0125] Fig. 8 is a diagram of examples associated with dropping inference reports for flexible processing unit occupation. In example 800 of Fig. 8, a number of CPUs 801 exceeds a number of available CPUs at the UE 120 while a number of APUs 803 does not exceed a number of available APUs at the UE 120. Accordingly, the UE 120 will only consider report configurations that occupy CPUs when determining which report configurations to drop. In other words, report configuration 805 will continue to be updated because the report configuration 805 only occupies APUs.
[0126] In example 830 of Fig. 8, a number of CPUs 831 does not exceed the number of available CPUs at the UE 120 while a number of APUs 833 does exceed the number of available APUs at the UE 120. Accordingly, the UE 120 will only consider report configurations that occupy APUs when determining which report configurations to drop. In other words, report configuration 835 will continue to be updated because the report configuration 835 only occupies CPUs.
[0127] In example 860 of Fig. 8, a number of CPUs 861 does exceed the number of available CPUs at the UE 120 while a number of APUs 863 also exceeds the number of available APUs at the UE 120. Accordingly, the UE 120 will consider all report configurations when determining which report configurations to drop.
[0128] The report configurations considered may be within a single CC or across all CCs. For example, the UE 120 may consider report configurations for dropping within a single CC (e.g., when the number of available processing units that is exceeded is also associated with the single CC) . Additionally, or alternatively, the UE 120 may consider report configurations for dropping across all CCs (e.g., when the number of available processing units that is exceeded is also associated with all CCs) .
[0129] As indicated above, Fig. 8 is provided as an example. Other examples may differ from what is described with regard to Fig. 8.
[0130] Fig. 9 is a diagram of an example 900 associated with reports to consider for flexible processing unit occupation. As shown in Fig. 9, a UE 120 may be configured with a set of report configurations. In indicating an available number of APUs, the UE 120 may ignore report configuration 901 because the report configuration 901 only occupies CPUs. In other words, the report configuration 901 may be unassociated with inference and therefore omitted from an indication of how many APUs are available (or will be occupied by the set of report configurations) .
[0131] As indicated above, Fig. 9 is provided as an example. Other examples may differ from what is described with regard to Fig. 9.
[0132] Fig. 10 is a diagram illustrating an example process 1000 performed, for example, at a UE or an apparatus of a UE. Example process 1000 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with reason codes for reporting inference capabilities.
[0133] As shown in Fig. 10, in some aspects, process 1000 may include receiving a reconfiguration message indicating a set of inference configuration candidates (block 1010) . For example, the UE (e.g., using reception component 1602 or communication manager 1606, depicted in Fig. 16) may receive a reconfiguration message indicating a set of inference configuration candidates, as described above in connection with reference number 310 of Fig. 3. In some aspects, the set of inference configuration candidates may be for beam management.
[0134] As further shown in Fig. 10, in some aspects, process 1000 may include transmitting an indication of which inference configuration candidates in the set are supported and which inference configuration candidates in the set are unsupported, where each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code (block 1020) . For example, the UE (e.g., using transmission component 1604 or communication manager 1606, depicted in Fig. 16) may transmit an indication of which inference configuration candidates in the set are supported and which inference configuration candidates in the set are unsupported, where each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code, as described above in connection with reference number 320 of Fig. 3. The reason code may indicate a combination of inference reports unsupported by the UE.
[0135] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.
[0136] In a first aspect, the set of inference configuration candidates are indicated using a set of report configurations.
[0137] In a second aspect, alone or in combination with the first aspect, the indication includes identifiers associated with respective report configurations.
[0138] In a third aspect, alone or in combination with one or more of the first and second aspects, the set of inference configuration candidates are indicated using sets of inference parameters.
[0139] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the indication includes identifiers associated with respective sets of inference parameters.
[0140] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the reason code indicates whether a corresponding model is temporarily unavailable or permanently unavailable.
[0141] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the reason code indicates that the UE lacks computational resources.
[0142] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the reason code indicates that the computational resources will be available if a concurrency restriction is resolved.
[0143] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the reason code indicates that the computational resources will be available if an inference parameter restriction is resolved.
[0144] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the indication further indicates combinations of inference configuration candidates in the set that are unsupported for concurrency.
[0145] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process 1000 includes transmitting (e.g., using transmission component 1604 or communication manager 1606) assistance information that updates the indication of which inference configuration candidates in the set are supported and which inference configuration candidates in the set are unsupported, as described above in connection with reference number 330 of Fig. 3.
[0146] Although Fig. 10 shows example blocks of process 1000, in some aspects, process 1000 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 10. Additionally, or alternatively, two or more of the blocks of process 1000 may be performed in parallel.
[0147] Fig. 11 is a diagram illustrating an example process 1100 performed, for example, at a UE or an apparatus of a UE. Example process 1100 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with flexible processing unit occupation for inference using concurrency reporting.
[0148] As shown in Fig. 11, in some aspects, process 1100 may include receiving an indication of a set of report configurations (block 1110) . For example, the UE (e.g., using reception component 1602 or communication manager 1606, depicted in Fig. 16) may receive an indication of a set of report configurations, as described above in connection with reference number 410 of Fig. 4.
[0149] As further shown in Fig. 11, in some aspects, process 1100 may include transmitting an indication of which report configurations in the set can be supported concurrently (block 1120) . For example, the UE (e.g., using transmission component 1604 or communication manager 1606, depicted in Fig. 16) may transmit an indication of which report configurations in the set can be supported concurrently, as described above in connection with reference number 415 of Fig. 4.
[0150] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.
[0151] In a first aspect, the set of report configurations includes at least one inactive semi-persistent or aperiodic report configuration.
[0152] In a second aspect, alone or in combination with the first aspect, the set of report configurations includes at least one inactive report configuration associated with an applicable functionality inquiry.
[0153] In a third aspect, alone or in combination with one or more of the first and second aspects, the set of report configurations includes at least one aperiodic trigger state that is inactive before the UE indicates which report configurations in the set can be supported concurrently.
[0154] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the set of report configurations are associated with inference, and process 1100 includes receiving (e.g., using reception component 1602 or communication manager 1606) at least one report configuration unassociated with inference, where the at least one report configuration is omitted from the indication of which report configurations in the set can be supported concurrently, as described above in connection with Fig. 4.
[0155] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the indication of which report configurations in the set can be supported concurrently indicates combinations of report configurations that are supported.
[0156] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the indication of which report configurations in the set can be supported concurrently indicates combinations of report configurations that are unsupported.
[0157] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the indication of which report configurations in the set can be supported concurrently is included in assistance information.
[0158] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the indication of which report configurations in the set can be supported concurrently is included in an RRC message.
[0159] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the indication of which report configurations in the set can be supported concurrently is included in a control element.
[0160] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the indication of which report configurations in the set can be supported concurrently is included in UCI.
[0161] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the indication of which report configurations in the set can be supported concurrently is included in a set of payloads corresponding to the set of report configurations.
[0162] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the indication further indicates a duration of time after which a supported report configuration in the set is expected to be unsupported.
[0163] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the indication further indicates a duration of time after which an unsupported report configuration in the set is expected to be supported.
[0164] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the indication further includes at least one reason code associated with an unsupported report configuration in the set.
[0165] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, one or more unsupported report configurations in the set, indicated using the indication, are associated with lower priorities relative to one or more supported report configurations in the set.
[0166] Although Fig. 11 shows example blocks of process 1100, in some aspects, process 1100 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 11. Additionally, or alternatively, two or more of the blocks of process 1100 may be performed in parallel.
[0167] Fig. 12 is a diagram illustrating an example process 1200 performed, for example, at a UE or an apparatus of a UE. Example process 1200 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with flexible processing unit occupation for inference using dynamic negotiation.
[0168] As shown in Fig. 12, in some aspects, process 1200 may include receiving an indication of a set of reporting configurations (block 1210) . For example, the UE (e.g., using reception component 1602 or communication manager 1606, depicted in Fig. 16) may receive an indication of a set of reporting configurations, as described above in connection with reference number 710 of Fig. 7.
[0169] As further shown in Fig. 12, in some aspects, process 1200 may include transmitting an indication of available processing units based at least in part on the set of reporting configurations (block 1220) . For example, the UE (e.g., using transmission component 1604 or communication manager 1606, depicted in Fig. 16) may transmit an indication of available processing units based at least in part on the set of reporting configurations, as described above in connection with reference number 715 of Fig. 7.
[0170] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.
[0171] In a first aspect, the indication of available processing units is for APUs.
[0172] In a second aspect, alone or in combination with the first aspect, process 1200 includes transmitting (e.g., using transmission component 1604 or communication manager 1606) a capability message indicating a fixed number of available CPUs, as described above in connection with Fig. 7.
[0173] In a third aspect, alone or in combination with one or more of the first and second aspects, the indication of available processing units is for CPUs.
[0174] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the indication of available processing units is included in assistance information.
[0175] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the indication of available processing units is included in an RRC message.
[0176] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the indication of available processing units is included in a control element.
[0177] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the indication of available processing units is included in UCI.
[0178] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, process 1200 includes refraining from updating (e.g., using communication manager 1606) a report, associated with a report configuration in the set, in response to a lack of available processing units, as described above in connection with reference number 725 of Fig. 7.
[0179] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, process 1200 includes transmitting (e.g., using transmission component 1604 or communication manager 1606) an indication of how many processing units are occupied by each report configuration in the set, as described above in connection with reference number 720 of Fig. 7.
[0180] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the set of report configurations are associated with inference, and process 1200 includes receiving (e.g., using reception component 1602 or communication manager 1606) at least one report configuration unassociated with inference, where the at least one report configuration is omitted from the indication of how many processing units are occupied by each report configuration in the set, as described above in connection with Fig. 7.
[0181] Although Fig. 12 shows example blocks of process 1200, in some aspects, process 1200 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 12. Additionally, or alternatively, two or more of the blocks of process 1200 may be performed in parallel.
[0182] Fig. 13 is a diagram illustrating an example process 1300 performed, for example, at a network node or an apparatus of a network node. Example process 1300 is an example where the apparatus or the network node (e.g., network node 110) performs operations associated with reason codes for reporting inference capabilities.
[0183] As shown in Fig. 13, in some aspects, process 1300 may include transmitting a reconfiguration message indicating a set of inference configuration candidates (block 1310) . For example, the network node (e.g., using transmission component 1704 or communication manager 1706, depicted in Fig. 17) may transmit a reconfiguration message indicating a set of inference configuration candidates, as described above in connection with reference number 310 of Fig. 3. In some aspects, the set of inference configuration candidates may be for beam management.
[0184] As further shown in Fig. 13, in some aspects, process 1300 may include receiving an indication of which inference configuration candidates in the set are supported by a UE and which inference configuration candidates in the set are unsupported by the UE, where each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code (block 1320) . For example, the network node (e.g., using reception component 1702 or communication manager 1706, depicted in Fig. 17) may receive an indication of which inference configuration candidates in the set are supported by a UE and which inference configuration candidates in the set are unsupported by the UE, where each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code, as described above in connection with reference number 320 of Fig. 3. The reason code may indicate a combination of inference reports unsupported by the UE.
[0185] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.
[0186] In a first aspect, the set of inference configuration candidates are indicated using a set of report configurations.
[0187] In a second aspect, alone or in combination with the first aspect, the indication includes identifiers associated with respective report configurations.
[0188] In a third aspect, alone or in combination with one or more of the first and second aspects, the set of inference configuration candidates are indicated using sets of inference parameters.
[0189] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the indication includes identifiers associated with respective sets of inference parameters.
[0190] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the reason code indicates whether a corresponding model is temporarily unavailable or permanently unavailable.
[0191] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the reason code indicates that the UE lacks computational resources.
[0192] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the reason code indicates that the computational resources will be available if a concurrency restriction is resolved.
[0193] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the reason code indicates that the computational resources will be available if an inference parameter restriction is resolved.
[0194] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the indication further indicates combinations of inference configuration candidates in the set that are unsupported for concurrency.
[0195] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process 1300 includes receiving (e.g., using reception component 1702 or communication manager 1706) assistance information that updates the indication of which inference configuration candidates in the set are supported and which inference configuration candidates in the set are unsupported, as described above in connection with reference number 330 of Fig. 3.
[0196] Although Fig. 13 shows example blocks of process 1300, in some aspects, process 1300 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 13. Additionally, or alternatively, two or more of the blocks of process 1300 may be performed in parallel.
[0197] Fig. 14 is a diagram illustrating an example process 1400 performed, for example, at a network node or an apparatus of a network node. Example process 1400 is an example where the apparatus or the network node (e.g., network node 110) performs operations associated with flexible processing unit occupation for inference using concurrency reporting.
[0198] As shown in Fig. 14, in some aspects, process 1400 may include transmitting an indication of a set of report configurations (block 1410) . For example, the network node (e.g., using transmission component 1704 or communication manager 1706, depicted in Fig. 17) may transmit an indication of a set of report configurations, as described above in connection with reference number 410 of Fig. 4.
[0199] As further shown in Fig. 14, in some aspects, process 1400 may include receiving an indication of which report configurations in the set can be supported concurrently (block 1420) . For example, the network node (e.g., using reception component 1702 or communication manager 1706, depicted in Fig. 17) may receive an indication of which report configurations in the set can be supported concurrently, as described above in connection with reference number 415 of Fig. 4.
[0200] Process 1400 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.
[0201] In a first aspect, the set of report configurations includes at least one inactive semi-persistent or aperiodic report configuration.
[0202] In a second aspect, alone or in combination with the first aspect, the set of report configurations includes at least one inactive report configuration associated with an applicable functionality inquiry.
[0203] In a third aspect, alone or in combination with one or more of the first and second aspects, the set of report configurations includes at least one aperiodic trigger state that is inactive before a UE indicates which report configurations in the set can be supported concurrently.
[0204] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the set of report configurations are associated with inference, and process 1400 includes transmitting (e.g., using transmission component 1704 or communication manager 1706) at least one report configuration unassociated with inference, where the at least one report configuration is omitted from the indication of which report configurations in the set can be supported concurrently, as described above in connection with Fig. 4.
[0205] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the indication of which report configurations in the set can be supported concurrently indicates combinations of report configurations that are supported.
[0206] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the indication of which report configurations in the set can be supported concurrently indicates combinations of report configurations that are unsupported.
[0207] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the indication of which report configurations in the set can be supported concurrently is included in assistance information.
[0208] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the indication of which report configurations in the set can be supported concurrently is included in an RRC message.
[0209] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the indication of which report configurations in the set can be supported concurrently is included in a control element.
[0210] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the indication of which report configurations in the set can be supported concurrently is included in UCI.
[0211] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the indication of which report configurations in the set can be supported concurrently is included in a set of payloads corresponding to the set of report configurations.
[0212] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the indication further indicates a duration of time after which a supported report configuration in the set is expected to be unsupported.
[0213] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the indication further indicates a duration of time after which an unsupported report configuration in the set is expected to be supported.
[0214] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the indication further includes at least one reason code associated with an unsupported report configuration in the set.
[0215] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, one or more unsupported report configurations in the set, indicated using the indication, are associated with lower priorities relative to one or more supported report configurations in the set.
[0216] Although Fig. 14 shows example blocks of process 1400, in some aspects, process 1400 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 14. Additionally, or alternatively, two or more of the blocks of process 1400 may be performed in parallel.
[0217] Fig. 15 is a diagram illustrating an example process 1500 performed, for example, at a network node or an apparatus of a network node. Example process 1500 is an example where the apparatus or the network node (e.g., network node 110) performs operations associated with flexible processing unit occupation for inference using dynamic negotiation.
[0218] As shown in Fig. 15, in some aspects, process 1500 may include transmitting an indication of a set of reporting configurations (block 1510) . For example, the network node (e.g., using transmission component 1704 or communication manager 1706, depicted in Fig. 17) may transmit an indication of a set of reporting configurations, as described above in connection with reference number 710 of Fig. 7.
[0219] As further shown in Fig. 15, in some aspects, process 1500 may include receiving an indication of available processing units based at least in part on the set of reporting configurations (block 1520) . For example, the network node (e.g., using reception component 1702 or communication manager 1706, depicted in Fig. 17) may receive an indication of available processing units based at least in part on the set of reporting configurations, as described above in connection with reference number 715 of Fig. 7.
[0220] Process 1500 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.
[0221] In a first aspect, the indication of available processing units is for APUs.
[0222] In a second aspect, alone or in combination with the first aspect, process 1500 includes receiving a capability message indicating a fixed number of available CPUs, as described above in connection with Fig. 7.
[0223] In a third aspect, alone or in combination with one or more of the first and second aspects, the indication of available processing units is for CPUs.
[0224] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the indication of available processing units is included in assistance information.
[0225] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the indication of available processing units is included in an RRC message.
[0226] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the indication of available processing units is included in a control element.
[0227] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the indication of available processing units is included in UCI.
[0228] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, process 1500 includes receiving (e.g., using reception component 1702 or communication manager 1706) an indication of how many processing units are occupied by each report configuration in the set, as described above in connection with reference number 720 of Fig. 7.
[0229] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the set of report configurations are associated with inference, and process 1500 includes transmitting (e.g., using transmission component 1704 or communication manager 1706) at least one report configuration unassociated with inference, where the at least one report configuration is omitted from the indication of how many processing units are occupied by each report configuration in the set, as described above in connection with Fig. 7.
[0230] Although Fig. 15 shows example blocks of process 1500, in some aspects, process 1500 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 15. Additionally, or alternatively, two or more of the blocks of process 1500 may be performed in parallel.
[0231] Fig. 16 is a diagram of an example apparatus 1600 for wireless communication. The apparatus 1600 may be a UE, or a UE may include the apparatus 1600. In some aspects, the apparatus 1600 includes a reception component 1602, a transmission component 1604, or a communication manager 1606, which may be in communication with one another (for example, via one or more buses or one or more other components) . In some aspects, the communication manager 1606 is the communication manager 150 described in connection with Fig. 1. As shown, the apparatus 1600 may communicate with another apparatus 1608, such as a UE or a network node (such as a CU, a DU, an RU, or a base station) , using the reception component 1602 and the transmission component 1604. The communication manager 1606 may be included in, or implemented via, a processing system (for example, the processing system 140 described in connection with Fig. 1) of the UE.
[0232] In some aspects, the apparatus 1600 may be configured to perform one or more operations described herein in connection with Figs. 3-9. Additionally, or alternatively, the apparatus 1600 may be configured to perform one or more processes described herein, such as process 1000 of Fig. 10, process 1100 of Fig. 11, process 1200 of Fig. 12, or a combination thereof. In some aspects, the apparatus 1600 or one or more components shown in Fig. 16 may include one or more components of the UE described in connection with Fig. 1. Additionally, or alternatively, one or more components shown in Fig. 16 may be implemented within one or more components described in connection with Fig. 1. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.
[0233] The reception component 1602 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1608. The reception component 1602 may provide received communications to one or more other components of the apparatus 1600. In some aspects, the reception component 1602 may perform signal processing on the received communications, and may provide the processed signals to the one or more other components of the apparatus 1600. In some aspects, the reception component 1602 may include one or more components of the UE described above in connection with Fig. 1, such as a radio, one or more RF chains, one or more transceivers, or one or more modems, each of which may in turn be coupled with one or more antennas of the UE.
[0234] The transmission component 1604 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1608. In some aspects, one or more other components of the apparatus 1600 may generate communications and may provide the generated communications to the transmission component 1604 for transmission to the apparatus 1608. In some aspects, the transmission component 1604 may perform signal processing on the generated communications, and may transmit the processed signals to the apparatus 1608. In some aspects, the transmission component 1604 may include one or more components of the UE described above in connection with Fig. 1, such as a radio, one or more RF chains, one or more transceivers, or one or more modems, each of which may in turn be coupled with one or more antennas of the UE described in connection with Fig. 1. In some aspects, the transmission component 1604 may be co-located with the reception component 1602.
[0235] The communication manager 1606 may support operations of the reception component 1602 or the transmission component 1604. For example, the communication manager 1606 may receive information associated with configuring reception of communications by the reception component 1602 or transmission of communications by the transmission component 1604. Additionally, or alternatively, the communication manager 1606 may generate or provide control information to the reception component 1602 or the transmission component 1604 to control reception or transmission of communications.
[0236] In some aspects, the reception component 1602 may receive a reconfiguration message indicating a set of inference configuration candidates. Accordingly, the transmission component 1604 may transmit an indication of which inference configuration candidates in the set are supported and which inference configuration candidates in the set are unsupported, where each inference configuration candidate in the set that is unsupported is associated with a reason code. In some aspects, the transmission component 1604 may transmit assistance information that updates the indication of which inference configuration candidates in the set are supported and which inference configuration candidates in the set are unsupported.
[0237] Additionally, or alternatively, the reception component 1602 may receive an indication of a set of report configurations. Accordingly, the transmission component 1604 may transmit an indication of which report configurations in the set can be supported concurrently. Alternatively, the transmission component 1604 may transmit an indication of available processing units based at least in part on the set of reporting configurations. In some aspects, the transmission component 1604 may also transmit a capability message indicating a fixed number of available CPUs. Additionally, or alternatively, the transmission component 1604 may transmit an indication of how many processing units are occupied by each report configuration in the set. The communication manager 1606 may refrain from updating a report, associated with a report configuration in the set, in response to a lack of available processing units.
[0238] The number and arrangement of components shown in Fig. 16 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 16. Furthermore, two or more components shown in Fig. 16 may be implemented within a single component, or a single component shown in Fig. 16 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 16 may perform one or more functions described as being performed by another set of components shown in Fig. 16.
[0239] Fig. 17 is a diagram of an example apparatus 1700 for wireless communication. The apparatus 1700 may be a network node, or a network node may include the apparatus 1700. In some aspects, the apparatus 1700 includes a reception component 1702, a transmission component 1704, or a communication manager 1706, which may be in communication with one another (for example, via one or more buses or one or more other components) . In some aspects, the communication manager 1706 is the communication manager 155 described in connection with Fig. 1. As shown, the apparatus 1700 may communicate with another apparatus 1708, such as a UE or a network node (such as a CU, a DU, an RU, or a base station) , using the reception component 1702 and the transmission component 1704. The communication manager 1706 may be included in, or implemented via, a processing system (for example, the processing system 145 described in connection with Fig. 1) of the network node.
[0240] In some aspects, the apparatus 1700 may be configured to perform one or more operations described herein in connection with Figs. 2-9. Additionally, or alternatively, the apparatus 1700 may be configured to perform one or more processes described herein, such as process 1300 of Fig. 13, process 1400 of Fig. 14, process 1500 of Fig. 15, or a combination thereof. In some aspects, the apparatus 1700 or one or more components shown in Fig. 17 may include one or more components of the network node described in connection with Fig. 1. Additionally, or alternatively, one or more components shown in Fig. 17 may be implemented within one or more components described in connection with Fig. 1. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.
[0241] The reception component 1702 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1708. The reception component 1702 may provide received communications to one or more other components of the apparatus 1700. In some aspects, the reception component 1702 may perform signal processing on the received communications, and may provide the processed signals to the one or more other components of the apparatus 1700. In some aspects, the reception component 1702 may include one or more components of the network node described above in connection with Fig. 1, such as a radio, one or more RF chains, one or more transceivers, or one or more modems, each of which may in turn be coupled with one or more antennas of the network node. In some aspects, the reception component 1702 or the transmission component 1704 may include or may be included in a network interface. The network interface may be configured to obtain or output signals for the apparatus 1700 via one or more communications links, such as a backhaul link, a midhaul link, or a fronthaul link.
[0242] The transmission component 1704 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1708. In some aspects, one or more other components of the apparatus 1700 may generate communications and may provide the generated communications to the transmission component 1704 for transmission to the apparatus 1708. In some aspects, the transmission component 1704 may perform signal processing on the generated communications, and may transmit the processed signals to the apparatus 1708. In some aspects, the transmission component 1704 may include one or more components of the network node described above in connection with Fig. 1, such as a radio, one or more RF chains, one or more transceivers, or one or more modems, each of which may in turn be coupled with one or more antennas of the network node described in connection with Fig. 1. In some aspects, the transmission component 1704 may be co-located with the reception component 1702.
[0243] The communication manager 1706 may support operations of the reception component 1702 or the transmission component 1704. For example, the communication manager 1706 may receive information associated with configuring reception of communications by the reception component 1702 or transmission of communications by the transmission component 1704. Additionally, or alternatively, the communication manager 1706 may generate or provide control information to the reception component 1702 or the transmission component 1704 to control reception or transmission of communications.
[0244] In some aspects, the transmission component 1704 may transmit a reconfiguration message indicating a set of inference configuration candidates. Accordingly, the reception component 1702 may receive an indication of which inference configuration candidates in the set are supported by the apparatus 1708 and which inference configuration candidates in the set are unsupported by the apparatus 1708, where each inference configuration candidate in the set that is unsupported is associated with a reason code. In some aspects, the reception component 1702 may receive assistance information that updates the indication of which inference configuration candidates in the set are supported and which inference configuration candidates in the set are unsupported.
[0245] Additionally, or alternatively, the transmission component 1704 may transmit an indication of a set of report configurations. Accordingly, the reception component 1702 may receive an indication of which report configurations in the set can be supported concurrently. Alternatively, the reception component 1702 may receive an indication of available processing units based at least in part on the set of reporting configurations. In some aspects, the reception component 1702 may also receive a capability message indicating a fixed number of available CPUs. Additionally, or alternatively, the reception component 1702 may receive an indication of how many processing units are occupied by each report configuration in the set.
[0246] The number and arrangement of components shown in Fig. 17 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 17. Furthermore, two or more components shown in Fig. 17 may be implemented within a single component, or a single component shown in Fig. 17 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 17 may perform one or more functions described as being performed by another set of components shown in Fig. 17.
[0247] The following provides an overview of some Aspects of the present disclosure:
[0248] Aspect 1: A method of wireless communication performed by a user equipment (UE) , comprising: receiving a reconfiguration message indicating a set of inference configuration candidates for beam management; and transmitting an indication of which inference configuration candidates in the set are supported by the UE and which inference configuration candidates in the set are unsupported by the UE, wherein each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code indicating a combination of inference reports unsupported by the UE.
[0249] Aspect 2: The method of Aspect 1, wherein the set of inference configuration candidates are indicated using a set of report configurations.
[0250] Aspect 3: The method of Aspect 2, wherein the indication includes identifiers associated with respective report configurations.
[0251] Aspect 4: The method of Aspect 1, wherein the set of inference configuration candidates are indicated using sets of inference parameters.
[0252] Aspect 5: The method of Aspect 4, wherein the indication includes identifiers associated with respective sets of inference parameters.
[0253] Aspect 6: The method of any of Aspects 1-5, wherein the reason code indicates whether a corresponding model is temporarily unavailable or permanently unavailable.
[0254] Aspect 7: The method of any of Aspects 1-6, wherein the reason code indicates that the UE lacks computational resources.
[0255] Aspect 8: The method of Aspect 7, wherein the reason code indicates that the computational resources will be available if a concurrency restriction is resolved.
[0256] Aspect 9: The method of any of Aspects 7-8, wherein the reason code indicates that the computational resources will be available if an inference parameter restriction is resolved.
[0257] Aspect 10: The method of any of Aspects 1-9, wherein the indication further indicates combinations of inference configuration candidates in the set that are unsupported for concurrency.
[0258] Aspect 11: The method of any of Aspects 1-10, further comprising: transmitting assistance information that updates the indication of which inference configuration candidates in the set are supported and which inference configuration candidates in the set are unsupported.
[0259] Aspect 12: A method of wireless communication performed by a user equipment (UE) , comprising: receiving an indication of a set of report configurations; and transmitting an indication of which report configurations in the set can be supported concurrently.
[0260] Aspect 13: The method of Aspect 12, wherein the set of report configurations includes at least one inactive semi-persistent or aperiodic report configuration.
[0261] Aspect 14: The method of any of Aspects 12-13, wherein the set of report configurations includes at least one inactive report configuration associated with an applicable functionality inquiry.
[0262] Aspect 15: The method of any of Aspects 12-14, wherein the set of report configurations includes at least one aperiodic trigger state that is inactive before the UE indicates which report configurations in the set can be supported concurrently.
[0263] Aspect 16: The method of any of Aspects 12-15, wherein the set of report configurations are associated with inference, and the method further comprises: receiving at least one report configuration unassociated with inference, wherein the at least one report configuration is omitted from the indication of which report configurations in the set can be supported concurrently.
[0264] Aspect 17: The method of any of Aspects 12-16, wherein the indication of which report configurations in the set can be supported concurrently indicates combinations of report configurations that are supported.
[0265] Aspect 18: The method of any of Aspects 12-17, wherein the indication of which report configurations in the set can be supported concurrently indicates combinations of report configurations that are unsupported.
[0266] Aspect 19: The method of any of Aspects 12-18, wherein the indication of which report configurations in the set can be supported concurrently is included in assistance information.
[0267] Aspect 20: The method of any of Aspects 12-19, wherein the indication of which report configurations in the set can be supported concurrently is included in a radio resource control message.
[0268] Aspect 21: The method of any of Aspects 12-18, wherein the indication of which report configurations in the set can be supported concurrently is included in a control element.
[0269] Aspect 22: The method of any of Aspects 12-18, wherein the indication of which report configurations in the set can be supported concurrently is included in uplink control information.
[0270] Aspect 23: The method of any of Aspects 12-22, wherein the indication of which report configurations in the set can be supported concurrently is included in a set of payloads corresponding to the set of report configurations.
[0271] Aspect 24: The method of any of Aspects 12-23, wherein the indication further indicates a duration of time after which a supported report configuration in the set is expected to be unsupported.
[0272] Aspect 25: The method of any of Aspects 12-24, wherein the indication further indicates a duration of time after which an unsupported report configuration in the set is expected to be supported.
[0273] Aspect 26: The method of any of Aspects 12-25, wherein the indication further includes at least one reason code associated with an unsupported report configuration in the set.
[0274] Aspect 27: The method of any of Aspects 12-26, wherein one or more unsupported report configurations in the set, indicated using the indication, are associated with lower priorities relative to one or more supported report configurations in the set.
[0275] Aspect 28: A method of wireless communication performed by a user equipment (UE) , comprising: receiving an indication of a set of reporting configurations; and transmitting an indication of available processing units based at least in part on the set of reporting configurations.
[0276] Aspect 29: The method of Aspect 28, wherein the indication of available processing units is for artificial intelligence or machine learning processing units (APUs) .
[0277] Aspect 30: The method of Aspect 29, further comprising: transmitting a capability message indicating a fixed number of available channel state information processing units (CPUs) .
[0278] Aspect 31: The method of any of Aspects 28-30, wherein the indication of available processing units is for channel state information processing units (CPUs) .
[0279] Aspect 32: The method of any of Aspects 28-31, wherein the indication of available processing units is included in assistance information.
[0280] Aspect 33: The method of any of Aspects 28-32, wherein the indication of available processing units is included in a radio resource control message.
[0281] Aspect 34: The method of any of Aspects 28-31, wherein the indication of available processing units is included in a control element.
[0282] Aspect 35: The method of any of Aspects 28-31, wherein the indication of available processing units is included in uplink control information.
[0283] Aspect 36: The method of any of Aspects 28-35, further comprising: refraining from updating a report, associated with a report configuration in the set, in response to a lack of available processing units.
[0284] Aspect 37: The method of any of Aspects 28-36, further comprising: transmitting an indication of how many processing units are occupied by each report configuration in the set.
[0285] Aspect 38: The method of Aspect 37, wherein the set of report configurations are associated with inference, and the method further comprises: receiving at least one report configuration unassociated with inference, wherein the at least one report configuration is omitted from the indication of how many processing units are occupied by each report configuration in the set.
[0286] Aspect 39: A method of wireless communication performed by a network node, comprising: transmitting a reconfiguration message indicating a set of inference configuration candidates for beam management; and receiving an indication of which inference configuration candidates in the set are supported by a user equipment (UE) and which inference configuration candidates in the set are unsupported by the UE, wherein each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code indicating a combination of inference reports unsupported by the UE.
[0287] Aspect 40: The method of Aspect 39, wherein the set of inference configuration candidates are indicated using a set of report configurations.
[0288] Aspect 41: The method of Aspect 40, wherein the indication includes identifiers associated with respective report configurations.
[0289] Aspect 42: The method of Aspect 39, wherein the set of inference configuration candidates are indicated using sets of inference parameters.
[0290] Aspect 43: The method of Aspect 42, wherein the indication includes identifiers associated with respective sets of inference parameters.
[0291] Aspect 44: The method of any of Aspects 39-43, wherein the reason code indicates whether a corresponding model is temporarily unavailable or permanently unavailable.
[0292] Aspect 45: The method of any of Aspects 39-44, wherein the reason code indicates that the UE lacks computational resources.
[0293] Aspect 46: The method of any of Aspects 39-45, wherein the reason code indicates that the computational resources will be available if a concurrency restriction is resolved.
[0294] Aspect 47: The method of any of Aspects 39-46, wherein the reason code indicates that the computational resources will be available if an inference parameter restriction is resolved.
[0295] Aspect 48: The method of any of Aspects 39-47, wherein the indication further indicates combinations of inference configuration candidates in the set that are unsupported for concurrency.
[0296] Aspect 49: The method of any of Aspects 39-48, further comprising: receiving assistance information that updates the indication of which inference configuration candidates in the set are supported and which inference configuration candidates in the set are unsupported.
[0297] Aspect 50: A method of wireless communication performed by a network node, comprising: transmitting an indication of a set of report configurations; and receiving an indication of which report configurations in the set can be supported concurrently.
[0298] Aspect 51: The method of Aspect 50, wherein the set of report configurations includes at least one inactive semi-persistent or aperiodic report configuration.
[0299] Aspect 52: The method of any of Aspects 50-51, wherein the set of report configurations includes at least one inactive report configuration associated with an applicable functionality inquiry.
[0300] Aspect 53: The method of any of Aspects 50-52, wherein the set of report configurations includes at least one aperiodic trigger state that is inactive before a user equipment (UE) indicates which report configurations in the set can be supported concurrently.
[0301] Aspect 54: The method of any of Aspects 50-53, wherein the set of report configurations are associated with inference, and the method further comprises: transmitting at least one report configuration unassociated with inference, wherein the at least one report configuration is omitted from the indication of which report configurations in the set can be supported concurrently.
[0302] Aspect 55: The method of any of Aspects 50-54, wherein the indication of which report configurations in the set can be supported concurrently indicates combinations of report configurations that are supported.
[0303] Aspect 56: The method of any of Aspects 50-55, wherein the indication of which report configurations in the set can be supported concurrently indicates combinations of report configurations that are unsupported.
[0304] Aspect 57: The method of any of Aspects 50-56, wherein the indication of which report configurations in the set can be supported concurrently is included in assistance information.
[0305] Aspect 58: The method of any of Aspects 50-57, wherein the indication of which report configurations in the set can be supported concurrently is included in a radio resource control message.
[0306] Aspect 59: The method of any of Aspects 50-56, wherein the indication of which report configurations in the set can be supported concurrently is included in a control element.
[0307] Aspect 60: The method of any of Aspects 50-56, wherein the indication of which report configurations in the set can be supported concurrently is included in uplink control information.
[0308] Aspect 61: The method of any of Aspects 50-60, wherein the indication of which report configurations in the set can be supported concurrently is included in a set of payloads corresponding to the set of report configurations.
[0309] Aspect 62: The method of any of Aspects 50-61, wherein the indication further indicates a duration of time after which a supported report configuration in the set is expected to be unsupported.
[0310] Aspect 63: The method of any of Aspects 50-62, wherein the indication further indicates a duration of time after which an unsupported report configuration in the set is expected to be supported.
[0311] Aspect 64: The method of any of Aspects 50-63, wherein the indication further includes at least one reason code associated with an unsupported report configuration in the set.
[0312] Aspect 65: The method of any of Aspects 50-64, wherein one or more unsupported report configurations in the set, indicated using the indication, are associated with lower priorities relative to one or more supported report configurations in the set.
[0313] Aspect 66: A method of wireless communication performed by a network node, comprising: transmitting an indication of a set of reporting configurations; and receiving an indication of available processing units based at least in part on the set of reporting configurations.
[0314] Aspect 67: The method of Aspect 66, wherein the indication of available processing units is for artificial intelligence or machine learning processing units (APUs) .
[0315] Aspect 68: The method of Aspect 67, further comprising: receiving a capability message indicating a fixed number of available channel state information processing units (CPUs) .
[0316] Aspect 69: The method of any of Aspects 66-68, wherein the indication of available processing units is for channel state information processing units (CPUs) .
[0317] Aspect 70: The method of any of Aspects 66-69, wherein the indication of available processing units is included in assistance information.
[0318] Aspect 71: The method of any of Aspects 66-70, wherein the indication of available processing units is included in a radio resource control message.
[0319] Aspect 72: The method of any of Aspects 66-69, wherein the indication of available processing units is included in a control element.
[0320] Aspect 73: The method of any of Aspects 66-69, wherein the indication of available processing units is included in uplink control information.
[0321] Aspect 74: The method of any of Aspects 66-73, further comprising: receiving an indication of how many processing units are occupied by each report configuration in the set.
[0322] Aspect 75: The method of any of Aspects 66-74, wherein the set of report configurations are associated with inference, and the method further comprises: transmitting at least one report configuration unassociated with inference, wherein the at least one report configuration is omitted from the indication of how many processing units are occupied by each report configuration in the set.
[0323] Aspect 76: An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method of one or more of Aspects 1-75.
[0324] Aspect 77: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform the method of one or more of Aspects 1-75.
[0325] Aspect 78: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-75.
[0326] Aspect 79: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method of one or more of Aspects 1-75.
[0327] Aspect 80: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-75.
[0328] Aspect 81: A device for wireless communication, the device comprising a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-75.
[0329] Aspect 82: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the device to perform the method of one or more of Aspects 1-75.
[0330] Aspect 83: A device comprising a processing system that includes one or more processors and one or more code-storing memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-75.
[0331] Aspect 84: A device comprising a processing system that includes processor circuitry and code-storing memory circuitry, the processing system configured to cause the device to perform the method of one or more of Aspects 1-75.
[0332] It will be apparent that systems or methods described herein may be implemented in different forms of hardware or a combination of hardware and software. A component being configured to perform a function means that the component has a capability to perform the function, and does not require the function to be actually performed by the component, unless noted otherwise.
[0333] As used herein, the term “determine” or “determining” can encompass one or more of a wide variety of actions. For example, “determining” can include one or more of calculating, computing, processing, deriving, detecting, estimating, investigating, looking up, inferring, ascertaining, measuring, resolving, selecting, choosing, obtaining, identifying, interpreting, demodulating, decoding, reading, establishing, forming or generating, among other examples. In some such examples, determining can involve a processor performing some type of calculating, computing, deriving, estimating, inferring, ascertaining, resolving, predicting or other processing to obtain one or more numerical values, sets, elements or other information or results. In some other such examples, determining can involve a processor identifying, looking up, investigating or otherwise obtaining some type of value, set, element or other information or result from a table, a data structure, a database or other memory device or location. In some other such examples, determining can involve a processor identifying, interpreting, demodulating, decoding, detecting, reading or otherwise obtaining some type of value, set, element or other information or result signaled in, for example, a received wireless packet. In some other such examples, determining can involve a processor selecting or choosing one or more values, sets, elements or other information or results from a larger set of values, sets elements or other information or results. In some other such examples, determining can involve a processor performing a measurement, such as on a received signal.
[0334] As used herein, the articles “a” and “an” are intended to refer to one or more items and may be used interchangeably with “one or more” or “at least one. ” As used herein, a phrase referring to “at least one of” or “one or more of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover: a, b, c, a-b, a-c, b-c, and a-b-c. Additionally, as used herein, a phrase referring to “a” or “an” element refers to one or more of such elements acting individually or collectively to perform the recited function (s) . Additionally, as used herein, a “set” can refer to one or more items, and a “subset” can refer to a whole set or less than the whole set, but not an empty set. “Set, ” “group, ” and similar terms are intended to include one or more items and may be used interchangeably with “one or more. ” Furthermore, as used herein, the term “or” is intended to be interpreted in the inclusive sense (such as when referring to a series) and may be used interchangeably with “and / or, ” unless otherwise explicitly indicated (for example, if used in conjunction with “either” or “only one of” ) . For example, “A or B” may include A only, B only, or a combination of A and B. Also, as used herein, the terms “has, ” “have, ” “having, ” “comprise, ” “comprising, ” “include” and “including, ” and derivatives thereof or similar terms are intended to be open-ended terms that do not limit an element that they modify (for example, an element “having” A also may have B) .
[0335] As used herein, the phrase “associated with” is intended to be interpreted in the inclusive sense, unless otherwise explicitly indicated. For example, the phrase “associated with” is not to be construed as a reference to a closed set of conditions, factors, criteria, elements, components, or actions, among other examples. Specifically, unless a phrase refers to “associated with only ‘a, ’ ” or the equivalent in context, whatever it is that is “associated with ‘a, ’ ” may be associated with “a” alone or associated with a combination of “a” and one or more other conditions, factors, criteria, elements, components, or actions, among other examples.
[0336] As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold, among other examples.
[0337] Even though particular combinations of features are recited in the claims or disclosed in the specification, these combinations are not intended to limit the scope of all aspects described herein. Many of these features may be combined in ways not specifically recited in the claims or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set.
Claims
1.A user equipment (UE) , comprising:a processing system that includes one or more processors and one or more code-storing memories coupled with the one or more processors, the processing system configured to cause the UE to:receive a reconfiguration message indicating a set of inference configuration candidates for beam management; andtransmit an indication of which inference configuration candidates in the set are supported by the UE and which inference configuration candidates in the set are unsupported by the UE,wherein each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code indicating a combination of inference reports unsupported by the UE.2.The UE of claim 1, wherein the set of inference configuration candidates are indicated using a set of report configurations.3.The UE of claim 2, wherein the indication includes identifiers associated with respective report configurations.4.The UE of claim 1, wherein the set of inference configuration candidates are indicated using sets of inference parameters.5.The UE of claim 4, wherein the indication includes identifiers associated with respective sets of inference parameters.6.The UE of claim 1, wherein the reason code indicates whether a corresponding model is temporarily unavailable or permanently unavailable.7.The UE of claim 1, wherein the reason code indicates that the UE lacks computational resources.8.The UE of claim 7, wherein the reason code indicates that the computational resources will be available if a concurrency restriction is resolved.9.The UE of claim 7, wherein the reason code indicates that the computational resources will be available if an inference parameter restriction is resolved.10.The UE of claim 1, wherein the indication further indicates combinations of inference configuration candidates in the set that are unsupported for concurrency.11.The UE of claim 1, wherein the processing system is configured to cause the UE to:transmit assistance information that updates the indication of which inference configuration candidates in the set are supported and which inference configuration candidates in the set are unsupported.12.A user equipment (UE) , comprising:a processing system that includes one or more processors and one or more code-storing memories coupled with the one or more processors, the processing system configured to cause the UE to:receive an indication of a set of report configurations; andtransmit an indication of which report configurations in the set can be supported concurrently.13.The UE of claim 12, wherein the set of report configurations includes at least one inactive semi-persistent or aperiodic report configuration or at least one inactive report configuration associated with an applicable functionality inquiry.14.The UE of claim 12, wherein the set of report configurations includes at least one aperiodic trigger state that is inactive before the UE indicates which report configurations in the set can be supported concurrently.15.The UE of claim 12, wherein the set of report configurations are associated with inference, and the processing system is configured to cause the UE to:receive at least one report configuration unassociated with inference,wherein the at least one report configuration is omitted from the indication of which report configurations in the set can be supported concurrently.16.The UE of claim 12, wherein the indication of which report configurations in the set can be supported concurrently indicates combinations of report configurations that are supported.17.The UE of claim 12, wherein the indication of which report configurations in the set can be supported concurrently indicates combinations of report configurations that are unsupported.18.The UE of claim 12, wherein the indication of which report configurations in the set can be supported concurrently is included in a set of payloads corresponding to the set of report configurations.19.The UE of claim 12, wherein one or more unsupported report configurations in the set, indicated using the indication, are associated with lower priorities relative to one or more supported report configurations in the set.20.A method of wireless communication performed by a user equipment (UE) , comprising:receiving a reconfiguration message indicating a set of inference configuration candidates for beam management; andtransmitting an indication of which inference configuration candidates in the set are supported by the UE and which inference configuration candidates in the set are unsupported by the UE,wherein each inference configuration candidate in the set that is unsupported is matched with a corresponding reason code indicating a combination of inference reports unsupported by the UE.
