Patent Application
20240265306
The present disclosure relates generally to wireless communications, and more specifically to categories of network-user equipment (UE) collaboration to enable artificial intelligence (AI)/machine learning (ML) techniques for an air interface.
Wireless communications systems are widely deployed to provide various telecommunications services such as telephony, video, data, messaging, and broadcasts. Typical wireless communications systems may employ multiple-access technologies capable of supporting communications with multiple users by sharing available system resources (e.g., bandwidth, transmit power, and/or the like). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, orthogonal frequency-division multiple access (OFDMA) systems, single-carrier frequency-division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems. LTE/LTE-Advanced is a set of enhancements to the universal mobile telecommunications system (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP). Narrowband (NB)-Internet of things (IoT) and enhanced machine-type communications (eMTC) are a set of enhancements to LTE for machine type communications.
A wireless communications network may include a number of base stations (BSs) that can support communications for a number of user equipment (UEs). A user equipment (UE) may communicate with a base station (BS) via the downlink and uplink. The downlink (or forward link) refers to the communications link from the BS to the UE, and the uplink (or reverse link) refers to the communications link from the UE to the BS. As will be described in more detail, a BS may be referred to as a Node B, an evolved Node B (eNB), a gNB, an access point (AP), a radio head, a transmit and receive point (TRP), a new radio (NR) BS, a 5G Node B, and/or the like.
The above multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different user equipment to communicate on a municipal, national, regional, and even global level. New Radio (NR), which may also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink (DL), using CP-OFDM and/or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
Artificial neural networks may comprise interconnected groups of artificial neurons (e.g., neuron models). The artificial neural network may be a computational device or represented as a method to be performed by a computational device. Convolutional neural networks, such as deep convolutional neural networks, are a type of feed-forward artificial neural network. Convolutional neural networks may include layers of neurons that may be configured in a tiled receptive field. It would be desirable to apply neural network processing to wireless communications to achieve greater efficiencies.
In aspects of the present disclosure, a method for wireless communication by a user equipment (UE) includes collaborating with a network device in accordance with a selected network-UE collaboration level of a number of network-UE collaboration levels for machine learning operations. At least one of the network-UE collaboration levels includes a number of sub-categories.
In other aspects of the present disclosure, a method for wireless communication by a network device includes collaborating with a user equipment (UE) in accordance with a selected network-UE collaboration level of a number of network-UE collaboration levels for machine learning operations. At least one of the network-UE collaboration levels includes a number of sub-categories.
Other aspects of the present disclosure are directed to an apparatus. The apparatus has one or more memories and one or more processors coupled to the one or more memories. The processor(s) is configured to collaborate with a network device in accordance with a selected network-UE collaboration level of a number of network-UE collaboration levels for machine learning operations. At least one of the network-UE collaboration levels includes a number of sub-categories.
Other aspects of the present disclosure are directed to an apparatus. The apparatus has one or more memories and one or more processors coupled to the one or more memories. The processor(s) is configured to collaborate with a user equipment (UE) in accordance with a selected network-UE collaboration level of a number of network-UE collaboration levels for machine learning operations. At least one of the network-UE collaboration levels includes a number of sub-categories.
Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and processing system as substantially described with reference to and as illustrated by the accompanying drawings and specification.
The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed, both their organization and method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.
So that features of the present disclosure can be understood in detail, a particular description may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.
Various aspects of the disclosure are described more fully below with reference to the accompanying drawings. This disclosure may however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings, one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth. In addition, the scope of the disclosure is intended to cover such an apparatus or method, which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth. It should be understood that any aspect of the disclosure disclosed may be embodied by one or more elements of a claim.
Several aspects of telecommunications systems will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, and/or the like (collectively referred to as “elements”). These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
It should be noted that while aspects may be described using terminology commonly associated with 5G and later wireless technologies, aspects of the present disclosure can be applied in other generation-based communications systems, such as and including 3G and/or 4G technologies.
While performing artificial intelligence/machine learning (AI/ML) operations, a user equipment (UE) may collaborate with a network. For example, a UE may operate a machine learning model received from the network, or the UE may send data to the network for use with a network-based machine learning model, with the results returned to the UE. Network-UE collaboration has been defined as having three distinct levels: Level x: no collaboration, where the UE develops its own model; Level y: signaling-based collaboration without model transfer; and Level z: signaling-based collaboration with model transfer.
According to aspects of the present disclosure, network-UE collaborations associated with Levels y and z may be subcategorized. For example, the levels may be subcategorized according to a life cycle management (LCM) type and the model transfer or delivery format. LCM types may include a model identification (ID)-based LCM or a functionality-based LCM. A model ID-based LCM assigns an ID to each AI/ML model. A functionality-based LCM may correspond to use cases, such as positioning beam forming, etc. Functionality-based LCM may also correspond to procedures within a use case. Model delivery/transfer formats may include an open format (e.g., a known standardized format) or a proprietary format. In one example, Level y may be divided into sub-categories: y1 and y2. Level y1 is a functionality-based LCM. Level y2 is a model ID-based LCM. Level z may also be divided into sub-categories: z1, z2, and z3. Level z1 is for a proprietary model format. Level z2 is for an open model format. Level z3 is for a model unseen by the UE, e.g., a model developed, trained, and managed by the network.
According to aspects of the present disclosure, a UE indicates to the network a supported network-UE collaboration level among the levels: y1, y2, z1, z2, z3 for each feature. Based on the indicated level of support, the network manages the AI/ML operations at the UE. In some aspects, the UE indicates one or more supported collaborations via UE capability reporting.
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, such as defining sub-categories for artificial intelligence/machine learning network-UE collaboration may help better understand what is required to define AI/ML operations for the air interface more adequately as well as clarify the functionality.
A BS may provide communications coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown in
In some aspects, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile BS. In some aspects, the BSs may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces such as a direct physical connection, a virtual network, and/or the like using any suitable transport network.
The wireless network 100 may also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. In the example shown in
The wireless network 100 may be a heterogeneous network that includes BSs of different types, e.g., macro BSs, pico BSs, femto BSs, relay BSs, and/or the like. These different types of BSs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless network 100. For example, macro BSs may have a high transmit power level (e.g., 5 to 40 Watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 Watts).
A network controller 130 may couple to a set of BSs and may provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with one another, e.g., directly or indirectly, via a wireless or wireline backhaul.
UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile. A UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, and/or the like. A UE may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communications device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.
Some UEs may be considered machine-type communications (MTC) or evolved or enhanced machine-type communications (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, and/or the like, that may communicate with a base station, another device (e.g., remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communications link. Some UEs may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband internet of things) devices. Some UEs may be considered a customer premises equipment (CPE). UE 120 may be included inside a housing that houses components of UE 120, such as processor components, memory components, and/or the like.
In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, and/or the like. A frequency may also be referred to as a carrier, a frequency channel, and/or the like. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.
In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using a base station 110 as an intermediary to communicate with one another). For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, and/or the like), a mesh network, and/or the like. In this case, the UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere as being performed by the base station 110. For example, the base station 110 may configure a UE 120 via downlink control information (DCI), radio resource control (RRC) signaling, a media access control-control element (MAC-CE) or via system information (e.g., a system information block (SIB).
The UEs 120 may include a machine learning (ML) configuration module 140. For brevity, only one UE 120d is shown as including the machine learning (ML) configuration module 140. The ML configuration module 140 may enable collaborating with a network device in accordance with a selected network-UE collaboration level of a number of network-UE collaboration levels for machine learning operations. At least one of the network-UE collaboration levels includes a number of sub-categories.
The base stations 110 may include a machine learning (ML) configuration module 138. For brevity, only one base station 110a is shown as including the machine learning (ML) configuration module 138. The ML configuration module 138 may enable collaboration with a user equipment (UE) in accordance with a selected network-UE collaboration level of a number of network-UE collaboration levels for machine learning operations. At least one of the network-UE collaboration levels includes a number of sub-categories.
As indicated above,
At the base station 110, a transmit processor 220 may receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(s) selected for the UE, and provide data symbols for all UEs. Decreasing the MCS lowers throughput but increases reliability of the transmission. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI) and/or the like) and control information (e.g., CQI requests, grants, upper layer signaling, and/or the like) and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., the cell-specific reference signal (CRS)) and synchronization signals (e.g., the primary synchronization signal (PSS) and secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM) and/or the like) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively. According to various aspects described in more detail below, the synchronization signals can be generated with location encoding to convey additional information.
At the UE 120, antennas 252a through 252r may receive the downlink signals from the base station 110 and/or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM and/or the like) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control information and system information to a controller/processor 280. A channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), and/or the like. In some aspects, one or more components of the UE 120 may be included in a housing.
On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, CQI, and/or the like) from the controller/processor 280. Transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for discrete Fourier transform spread OFDM (DFT-s-OFDM), CP-OFDM, and/or the like), and transmitted to the base station 110. At the base station 110, the uplink signals from the UE 120 and other UEs may be received by the antennas 234, processed by the demodulators 254, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller/processor 240. The base station 110 may include communications unit 244 and communicate to the network controller 130 via the communications unit 244. The network controller 130 may include a communications unit 294, a controller/processor 290, and a memory 292.
The controller/processor 240 of the base station 110, the controller/processor 280 of the UE 120, and/or any other component(s) of
In some aspects, the UE 120 may include means for collaborating, means for transmitting, means for receiving, and means for performing. In some aspects, the base station 110 may include means for collaborating, means for receiving, means for transmitting, and means for performing. Such means may include one or more components of the UE 120 or base station 110 described in connection with
As indicated above,
In some cases, different types of devices supporting different types of applications and/or services may coexist in a cell. Examples of different types of devices include UE handsets, customer premises equipment (CPEs), vehicles, Internet of Things (IoT) devices, and/or the like. Examples of different types of applications include ultra-reliable low-latency communications (URLLC) applications, massive machine-type communications (mMTC) applications, enhanced mobile broadband (eMBB) applications, vehicle-to-anything (V2X) applications, and/or the like. Furthermore, in some cases, a single device may support different applications or services simultaneously.
Deployment of communication systems, such as 5G new radio (NR) systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS), or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, 5G NB, an access point (AP), a transmit and receive point (TRP), or a cell, etc.) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.
An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU also can be implemented as virtual units (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).
Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.
Each of the units (e.g., the CUs 310, the DUs 330, the RUs 340, as well as the near-RT RICs 325, the non-RT RICs 315, and the SMO framework 305) may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a radio frequency (RF) transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bi-directionally with the CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 310 can be implemented to communicate with the DU 330, as necessary, for network control and signaling.
The DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the Third Generation Partnership Project (3GPP). In some aspects, the DU 330 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.
Lower-layer functionality can be implemented by one or more RUs 340. In some deployments, an RU 340, controlled by a DU 330, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 340 can be implemented to handle over the air (OTA) communication with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable the DU(s) 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
The SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO Framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, and near-RT RICs 325. In some implementations, the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an O1 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with one or more RUs 340 via an O1 interface. The SMO Framework 305 also may include a non-RT RIC 315 configured to support functionality of the SMO Framework 305.
The non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence/machine learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with (such as via an A1 interface) the near-RT RIC 325. The near-RT RIC 325 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as the O-eNB 311, with the near-RT RIC 325.
In some implementations, to generate AI/ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from external servers. Such information may be utilized by the near-RT RIC 325 and may be received at the SMO Framework 305 or the non-RT RIC 315 from non-network data sources or from network functions. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 305 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies).
The SOC 400 may also include additional processing blocks tailored to specific functions, such as a GPU 404, a DSP 406, a connectivity block 410, which may include fifth generation (5G) connectivity, fourth generation long term evolution (4G LTE) connectivity, Wi-Fi connectivity, USB connectivity, Bluetooth connectivity, and the like, and a multimedia processor 412 that may for example, detect and recognize gestures. In one implementation, the NPU is implemented in the CPU, DSP, and/or GPU. The SOC 400 may also include a sensor processor 414, image signal processors (ISPs) 416, and/or navigation module 420, which may include a global positioning system.
The SOC 400 may be based on an ARM instruction set. In aspects of the present disclosure, the instructions loaded into the general-purpose processor 402 may comprise code to collaborate with a network device in accordance with a selected network-UE collaboration level of a number of network-UE collaboration levels for machine learning operations. At least one of the network-UE collaboration levels includes a number of sub-categories.
In other aspects of the present disclosure, the instructions loaded into the general-purpose processor 402 may comprise code to collaborate with a user equipment (UE) in accordance with a selected network-UE collaboration level of a number of network-UE collaboration levels for machine learning operations. At least one of the network-UE collaboration levels includes a number of sub-categories.
Deep learning architectures may perform an object recognition task by learning to represent inputs at successively higher levels of abstraction in each layer, thereby building up a useful feature representation of the input data. In this way, deep learning addresses a major bottleneck of traditional machine learning. Prior to the advent of deep learning, a machine learning approach to an object recognition problem may have relied heavily on human engineered features, perhaps in combination with a shallow classifier. A shallow classifier may be a two-class linear classifier, for example, in which a weighted sum of the feature vector components may be compared with a threshold to predict to which class the input belongs. Human engineered features may be templates or kernels tailored to a specific problem domain by engineers with domain expertise. Deep learning architectures, in contrast, may learn to represent features that are similar to what a human engineer might design, but through training. Furthermore, a deep network may learn to represent and recognize new types of features that a human might not have considered.
A deep learning architecture may learn a hierarchy of features. If presented with visual data, for example, the first layer may learn to recognize relatively simple features, such as edges, in the input stream. In another example, if presented with auditory data, the first layer may learn to recognize spectral power in specific frequencies. The second layer, taking the output of the first layer as input, may learn to recognize combinations of features, such as simple shapes for visual data or combinations of sounds for auditory data. For instance, higher layers may learn to represent complex shapes in visual data or words in auditory data. Still higher layers may learn to recognize common visual objects or spoken phrases.
Deep learning architectures may perform especially well when applied to problems that have a natural hierarchical structure. For example, the classification of motorized vehicles may benefit from first learning to recognize wheels, windshields, and other features. These features may be combined at higher layers in different ways to recognize cars, trucks, and airplanes.
Neural networks may be designed with a variety of connectivity patterns. In feed-forward networks, information is passed from lower to higher layers, with each neuron in a given layer communicating to neurons in higher layers. A hierarchical representation may be built up in successive layers of a feed-forward network, as described above. Neural networks may also have recurrent or feedback (also called top-down) connections. In a recurrent connection, the output from a neuron in a given layer may be communicated to another neuron in the same layer. A recurrent architecture may be helpful in recognizing patterns that span more than one of the input data chunks that are delivered to the neural network in a sequence. A connection from a neuron in a given layer to a neuron in a lower layer is called a feedback (or top-down) connection. A network with many feedback connections may be helpful when the recognition of a high-level concept may aid in discriminating the particular low-level features of an input.
The connections between layers of a neural network may be fully connected or locally connected.
One example of a locally connected neural network is a convolutional neural network.
One type of convolutional neural network is a deep convolutional network (DCN).
The DCN 500 may be trained with supervised learning. During training, the DCN 500 may be presented with an image, such as the image 526 of a speed limit sign, and a forward pass may then be computed to produce an output 522. The DCN 500 may include a feature extraction section and a classification section. Upon receiving the image 526, a convolutional layer 532 may apply convolutional kernels (not shown) to the image 526 to generate a first set of feature maps 518. As an example, the convolutional kernel for the convolutional layer 532 may be a 5×5 kernel that generates 28×28 feature maps. In the present example, because four different feature maps are generated in the first set of feature maps 518, four different convolutional kernels were applied to the image 526 at the convolutional layer 532. The convolutional kernels may also be referred to as filters or convolutional filters.
The first set of feature maps 518 may be subsampled by a max pooling layer (not shown) to generate a second set of feature maps 520. The max pooling layer reduces the size of the first set of feature maps 518. That is, a size of the second set of feature maps 520, such as 14×14, is less than the size of the first set of feature maps 518, such as 28×28. The reduced size provides similar information to a subsequent layer while reducing memory consumption. The second set of feature maps 520 may be further convolved via one or more subsequent convolutional layers (not shown) to generate one or more subsequent sets of feature maps (not shown).
In the example of
In the present example, the probabilities in the output 522 for “sign” and “60” are higher than the probabilities of the others of the output 522, such as “30,” “40,” “50,” “70,” “80,” “90,” and “100”. Before training, the output 522 produced by the DCN 500 likely be incorrect. Thus, an error may be calculated between the output 522 and a target output. The target output is the ground truth of the image 526 (e.g., “sign” and “60”). The weights of the DCN 500 may then be adjusted so the output 522 of the DCN 500 is more closely aligned with the target output.
To adjust the weights, a learning algorithm may compute a gradient vector for the weights. The gradient may indicate an amount that an error would increase or decrease if the weight were adjusted. At the top layer, the gradient may correspond directly to the value of a weight connecting an activated neuron in the penultimate layer and a neuron in the output layer. In lower layers, the gradient may depend on the value of the weights and on the computed error gradients of the higher layers. The weights may then be adjusted to reduce the error. This manner of adjusting the weights may be referred to as “back propagation” as it involves a “backward pass” through the neural network.
In practice, the error gradient of weights may be calculated over a small number of examples, so that the calculated gradient approximates the true error gradient. This approximation method may be referred to as stochastic gradient descent. Stochastic gradient descent may be repeated until the achievable error rate of the entire system has stopped decreasing or until the error rate has reached a target level. After learning, the DCN 500 may be presented with new images (e.g., the speed limit sign of the image 526) and a forward pass through the DCN 500 may yield an output 522 that may be considered an inference or a prediction of the DCN 500.
Deep belief networks (DBNs) are probabilistic models comprising multiple layers of hidden nodes. DBNs may be used to extract a hierarchical representation of training data sets. A DBN may be obtained by stacking up layers of Restricted Boltzmann Machines (RBMs). An RBM is a type of artificial neural network that can learn a probability distribution over a set of inputs. Because RBMs can learn a probability distribution in the absence of information about the class to which each input should be categorized, RBMs are often used in unsupervised learning. Using a hybrid unsupervised and supervised paradigm, the bottom RBMs of a DBN may be trained in an unsupervised manner and may serve as feature extractors, and the top RBM may be trained in a supervised manner (on a joint distribution of inputs from the previous layer and target classes) and may serve as a classifier.
DCNs are networks of convolutional networks, configured with additional pooling and normalization layers. DCNs have achieved state-of-the-art performance on many tasks. DCNs can be trained using supervised learning in which both the input and output targets are known for many exemplars and are used to modify the weights of the network by use of gradient descent methods.
DCNs may be feed-forward networks. In addition, as described above, the connections from a neuron in a first layer of a DCN to a group of neurons in the next higher layer are shared across the neurons in the first layer. The feed-forward and shared connections of DCNs may be exploited for fast processing. The computational burden of a DCN may be much less, for example, than that of a similarly sized neural network that comprises recurrent or feedback connections.
The processing of each layer of a convolutional network may be considered a spatially invariant template or basis projection. If the input is first decomposed into multiple channels, such as the red, green, and blue channels of a color image, then the convolutional network trained on that input may be considered three-dimensional, with two spatial dimensions along the axes of the image and a third dimension capturing color information. The outputs of the convolutional connections may be considered to form a feature map in the subsequent layer, with each element of the feature map (e.g., 520) receiving input from a range of neurons in the previous layer (e.g., feature maps 518) and from each of the multiple channels. The values in the feature map may be further processed with a non-linearity, such as a rectification, max(0, x). Values from adjacent neurons may be further pooled, which corresponds to down sampling, and may provide additional local invariance and dimensionality reduction. Normalization, which corresponds to whitening, may also be applied through lateral inhibition between neurons in the feature map.
The performance of deep learning architectures may increase as more labeled data points become available or as computational power increases. Modern deep neural networks are routinely trained with computing resources that are thousands of times greater than what was available to a typical researcher just fifteen years ago. New architectures and training paradigms may further boost the performance of deep learning. Rectified linear units may reduce a training issue known as vanishing gradients. New training techniques may reduce over-fitting and thus enable larger models to achieve better generalization. Encapsulation techniques may abstract data in a given receptive field and further boost overall performance.
The convolution layers 656 may include one or more convolutional filters, which may be applied to the input data to generate a feature map. The normalization layer 658 may normalize the output of the convolution filters. For example, the normalization layer 658 may provide whitening or lateral inhibition. The max pooling layer 660 may provide down sampling aggregation over space for local invariance and dimensionality reduction.
The parallel filter banks, for example, of a deep convolutional network may be loaded on a CPU 402 or GPU 404 of an SOC 400 (e.g.,
The deep convolutional network 650 may also include one or more fully connected layers 662 (FC1 and FC2). The deep convolutional network 650 may further include a logistic regression (LR) layer 664. Between each layer 656, 658, 660, 662, 664 of the deep convolutional network 650 are weights (not shown) that are to be updated. The output of each of the layers (e.g., 656, 658, 660, 662, 664) may serve as an input of a succeeding one of the layers (e.g., 656, 658, 660, 662, 664) in the deep convolutional network 650 to learn hierarchical feature representations from input data 652 (e.g., images, audio, video, sensor data and/or other input data) supplied at the first of the convolution blocks 654A. The output of the deep convolutional network 650 is a classification score 666 for the input data 652. The classification score 666 may be a set of probabilities, where each probability is the probability of the input data, including a feature from a set of features.
As indicated above,
During artificial intelligence/machine learning (AI/ML) operations, the UE may collaborate with the network. For example, a UE may operate a machine learning model received from the network, or the UE may send data to the network for use with a network-based machine learning model, with the results returned to the UE. Network-UE collaboration has been defined as having three distinct levels: Level x: no collaboration, where the UE develops its own model; Level y: signaling-based collaboration without model transfer; and Level z: signaling-based collaboration with model transfer. Other collaboration levels are possible. In some non-limiting examples, the other levels may consider whether model updating occurs, whether training is supported or, whether inference is supported. The Level y-z boundary may be defined based on whether model delivery is transparent to third generation partnership project (3GPP) signaling over the air interface. Procedures other than model transfer or delivery may be decoupled from collaboration levels y and z.
Level x is an implementation-based AI/ML operation without any dedicated AI/ML-specific enhancement for collaboration between the network and UE. For example, no signaling exists between the UE and the network for the AI/ML operation. Life cycle management (LCM) related signaling and reference signals are not provided for the AI/ML collaboration. The AI/ML operation may however, rely on future specifications not related to AI/ML collaboration. The AI/ML approaches may be used as a baseline for performance evaluation for future releases.
According to aspects of the present disclosure, network-UE collaborations indicated by levels y and z may be subcategorized. For example, the levels may be subcategorized according to an LCM type and the model transfer or delivery format. LCM types may include a model identification (ID)-based LCM or a functionality-based LCM. A model ID-based LCM assigns an ID to each AI/ML model. A functionality-based LCM may correspond to use cases, such as positioning, beam forming, etc. Functionality-based LCM may also correspond to procedures within a use case. Model delivery/transfer formats may include an open format (e.g., a known standardized format) or a proprietary format.
According to aspects of the present disclosure, a UE indicates to the network a supported network-UE collaboration level among the levels: y1, y2, z1, z2, z3 for each feature. Based on the indicated level of support, the network manages the AI/ML operations at the UE. In some aspects, the UE indicates a supported collaboration type via UE capability reporting.
For Level y1 support, the network is aware of the desired AI/ML functionality at the UE via UE capability reporting. That is, the UE informs the network that the UE will use AL/ML for a particular use case or procedure. Functionality may refer to a particular use case or procedure at the UE where AI/ML is expected to be used, such as AI/ML-based beam prediction, AI/ML-based positioning, etc.
For Level y1 support, the network can control AI/ML functionality for inference at the UE. For example, the network may control functionality, such as AI/ML functionality activation, functionality deactivation, and/or performance monitoring. Performance monitoring may pertain to information about AI/ML model performance. For example, the network may receive feedback from the UE and if the network determines the model/functionality efficiency to be below a threshold level, the network may deactivate the AI/ML functionality at the UE so that the UE no longer uses the AI/ML functionality.
For Level y1 support, the UE may operate one or more AI/ML models for a given functionality. The network, however, does not control which AI/ML model the UE is to use because the network may be unaware of what models are available to the UE. If needed, AI/ML models may be stored outside the 3GPP network. For example, third-party servers may store the AI/ML models and deliver the models to the UE for inference. The AI/ML models are not stored in the 3GPP network because model transfers within the 3GPP air interface are not specified for Level y1. Signaling aspects for Level y1 collaboration include UE capability reporting for AI/ML functionality support, as well as functionality activation, deactivation, and/or performance monitoring signaling from the network to the UE.
For Level y2 support, AI/ML models are registered to the 3GPP network and each model is assigned a model ID. From UE capability reporting, the network is aware of AI/ML model functionality at the UE, as well as supported model IDs for the functionality. The network can control AI/ML model inference at the UE based on the model IDs. For example, the network may control model selection, model activation, model deactivation, model switching, fallback to non-AI/ML techniques, and/or monitoring. If needed for Level y2 collaboration, AI/ML models may be stored outside the 3GPP network. For example, third-party servers may store the AI/ML models and deliver the models to the UE for inference. The AI/ML models are not stored in the 3GPP network because Level y1 specifies no model transfer within the 3GPP air interface. Signaling aspects for Level y2 collaboration include the signaling aspects described with respect to Level y1, in addition to UE capability reporting of supported model IDs for the AI/ML functionality. Also, network signaling to the UE for model ID-based inference control is included for Level y2. Model ID-based inference control may include model selection, model activation, model deactivation, model switching, fallback, and/or monitoring.
For Level z1 support, AI/ML models are registered to the 3GPP network with assigned model IDs. Similar to Level y2, the network is aware of the AI/ML model functionality at the UE and supported model IDs for the functionality, based on UE capability reporting. Also similar to Level y2, the network can control AI/ML model inference at the UE based on the model IDs. The network may control model selection, activation, deactivation, switching, fallback, and/or monitoring.
For Level z1 support, the AI/ML models are stored inside the 3GPP network and delivered to the UE for inference. The delivery is referred to as “model transfer” with respect to 3GPP networks. The AI/ML models are stored in a vendor proprietary format that can be executable at the UE. New signaling aspects for Level z1 support, in addition to the signaling for Level y2 collaboration, includes UE capability reporting indicating supported model IDs for the AI/ML functionality. The model transfer capability is also signaled for Level z1.
For aspects related to Level z2 support, AI/ML models are registered to the 3GPP network with assigned model IDs. In these aspects, the model ID may refer to a particular model structure with specific parameters, or to a particular model structure with any parameters (e.g., the network can retrain and update the parameters). Similar to Level z1 collaboration, the network is aware of AI/ML model functionality at the UE and supported model IDs for the functionality, based on UE capability reporting. Also, the network can control AI/ML model inference at the UE (e.g., model selection, activation, deactivation, switching, fallback, and/or monitoring) based on the model IDs. Moreover, the AI/ML models are stored inside the 3GPP network and delivered to the UE for inference.
For Level z2 support, the AI/ML models are stored in an open format compatible across vendors. An example of an open format is ONNX (open neural network exchange format). Once transferred to the UE with an open format, the UE may have to compile the AI/ML model into an executable form. New signaling aspects, in addition to the signaling for Level z1, include a supported model description format, for example, ONNX. For a supported model ID, the UE may also signal whether the UE supports receiving updated parameters from the network, in case the network retrains the model.
For Level z3 support, the features associated with Level z2 collaboration are included, in addition to the following features. New AI/ML model identities may be created by the network. For example, the network may create a new model structure previously unseen by the UE. In some aspects, the UE reports a formula-based AI/ML inference capability. Examples of formula-based AI/ML inference capabilities are: a maximum model size supported by the UE, a maximum number of floating point operations per second (FLOPS) supported by the UE, etc. In accordance with the formula-based AI/ML inference capability, the network may determine if the UE would be capable of running the new model. In addition to the signaling aspects for Level z2, the UE signals the formula-based AI/ML inference capability for Level z3 collaboration.
At block 802, the user equipment (UE) collaborates with a network device in accordance with a selected network-UE collaboration level of a number of network-UE collaboration levels for machine learning operations. At least one of the network-UE collaboration levels includes a number of sub-categories. For example, the UE (e.g., using the antenna 252, DEMOD/MOD 254, MIMO detector 256, receive processor 258, TX MIMO processor 266, transmit processor 264, controller/processor 280, memory 282, and/or the like) may collaborate with the network device. In some aspects, the UE transmits an indication of a level of support for the selected network-UE collaboration level. The sub-categories may correspond to a life cycle management type and a model transfer/delivery format. The UE may also receive a machine learning configuration based on the level of support. The level of support may indicates at least one machine learning functionality, and the UE may also perform an inference with at least one machine learning model associated with the at least one machine learning model functionality.
At block 902, the network device collaborates with a user equipment (UE) in accordance with a selected network-UE collaboration level of a number of network-UE collaboration levels for machine learning operations. At least one of the network-UE collaboration levels includes a number of sub-categories. For example, the base station (e.g., using the antenna 234, DEMOD/MOD 232, MIMO detector 236, receive processor 238, TX MIMO processor 230, transmit processor 220, controller/processor 240, memory 242, and/or the like) may collaborate with the UE. In some aspects, the network receives an indication of a level of support for the selected network-UE collaboration level. The sub-categories may correspond to a life cycle management type and a model transfer/delivery format. The network may transmit a machine learning configuration based on the level of support. The level of support may indicates at least one machine learning functionality, and the UE may also perform an inference with at least one machine learning model associated with the at least one machine learning model functionality.
Aspect 1: A method of wireless communication by a user equipment (UE), comprising: collaborating with a network device in accordance with a selected network-UE collaboration level of a plurality of network-UE collaboration levels for machine learning operations, at least one of the plurality of network-UE collaboration levels comprising a plurality of sub-categories.
Aspect 2: The method of Aspect 1, further comprising: transmitting an indication of a level of support for the selected network-UE collaboration level, the plurality of sub-categories corresponding to a life cycle management type and a model transfer/delivery format; and receiving a machine learning configuration based on the level of support.
Aspect 3: The method of Aspect 1 or 2, in which the level of support indicates at least one machine learning functionality, and the method further comprises performing an inference with at least one machine learning model associated with the at least one machine learning model functionality.
Aspect 4: The method of any of the preceding Aspects, further comprising receiving the at least one machine learning model from a non-third generation partnership project (3GPP) entity.
Aspect 5: The method of any of the preceding Aspects, further comprising receiving, from the network device, instructions comprising at least one of: instructions for functionality activation, instructions for functionality deactivation, or instructions for performance monitoring.
Aspect 6: The method of any of the preceding Aspects, in which the level of support indicates at least one machine learning functionality and at least one machine learning model identification (ID) for each ML functionality, and the method further comprises receiving instructions for performing an inference with at least one machine learning model associated with the at least one machine learning model ID.
Aspect 7: The method of any of the preceding Aspects, further comprising receiving the at least one machine learning model from a non-third generation partnership project (3GPP) entity.
Aspect 8: The method of any of the preceding Aspects, in which the instructions comprise at least one of: instructions for model selection, instructions for model activation, instructions for model deactivation, instructions for model switching, instructions for model fallback, or instructions for model monitoring.
Aspect 9: The method of any of the preceding Aspects, in which: the level of support indicates at least one machine learning functionality, at least one machine learning model identification (ID) for each ML functionality, and a model transfer capability of the UE for reception from a third generation partnership project (3GPP) entity, a machine learning model being stored in a proprietary format, and the method further comprises receiving instructions for performing an inference with at least one machine learning model associated with the at least one machine learning model ID.
Aspect 10: The method of any of the preceding Aspects, in which the instructions comprise at least one of: instructions for model selection, instructions for model activation, instructions for model deactivation, instructions for model switching, instructions for model fallback, or instructions for model monitoring.
Aspect 11: The method of any of the preceding Aspects, in which: the level of support indicates at least one machine learning functionality, at least one machine learning model identification (ID) for each ML functionality, and a model transfer capability of the UE including whether the UE supports receiving updated machine learning parameters from a third generation partnership project (3GPP) entity, a machine learning model being stored in an open format, and the method further comprises receiving instructions for performing an inference with at least one machine learning model associated with the at least one machine learning model ID.
Aspect 12: The method of any of the preceding Aspects, in which the instructions comprise at least one of: instructions for model selection, instructions for model activation, instructions for model deactivation, instructions for model switching, instructions for model fallback, or instructions for model monitoring.
Aspect 13: The method of any of the preceding Aspects, in which the level of support indicates at least one machine learning functionality, at least one machine learning model identification (ID) for each ML functionality, and a model transfer capability of the UE including a formula-based machine learning inference capability of the UE.
Aspect 14: A method of wireless communication by a network device, comprising: collaborating with a user equipment (UE) in accordance with a selected network-UE collaboration level of a plurality of network-UE collaboration levels for machine learning operations, at least one of the plurality of network-UE collaboration levels comprising a plurality of sub-categories.
Aspect 15: The method of Aspect 14, further comprising: receiving an indication of a level of support for the selected network-UE collaboration level, the plurality of sub-categories corresponding to a life cycle management type and a model transfer/delivery format; and transmitting a machine learning configuration based on the level of support.
Aspect 16: The method of Aspect 14 or 15, in which the level of support indicates at least one machine learning functionality, and the method further comprises performing an inference with at least one machine learning model associated with the at least one machine learning model functionality.
Aspect 17: The method of any of the Aspects 14-16, further comprising transmitting at least one machine learning model for the machine learning operations.
Aspect 18: The method of any of the Aspects 14-17, further comprising transmitting instructions comprising at least one of: instructions for functionality activation, instructions for functionality deactivation, or instructions for performance monitoring.
Aspect 19: The method of any of the Aspects 14-18, in which the level of support indicates at least one machine learning functionality and at least one machine learning model identification (ID) for each ML functionality, and the method further comprises transmitting instructions for performing an inference with at least one machine learning model associated with the at least one machine learning model ID.
Aspect 20: The method of any of the Aspects 14-19, in which the instructions comprise at least one of: instructions for model selection, instructions for model activation, instructions for model deactivation, instructions for model switching, instructions for model fallback, or instructions for model monitoring.
Aspect 21: The method of any of the Aspects 14-20, in which: the level of support indicates at least one machine learning functionality, at least one machine learning model identification (ID) for each ML functionality, and a model transfer capability of the UE for reception from a third generation partnership project (3GPP) entity, a machine learning model being stored in a proprietary format, and the method further comprises transmitting instructions for performing an inference with at least one machine learning model associated with the at least one machine learning model ID.
Aspect 22: The method of any of the Aspects 14-21, in which the instructions comprise at least one of: instructions for model selection, instructions for model activation, instructions for model deactivation, instructions for model switching, instructions for model fallback, or instructions for model monitoring.
Aspect 23: The method of any of the Aspects 14-22, in which: the level of support indicates at least one machine learning functionality, at least one machine learning model identification (ID) for each ML functionality, and a model transfer capability of the UE including whether the UE supports receiving updated machine learning parameters from a third generation partnership project (3GPP) entity, a machine learning model being stored in an open format, and the method further comprises transmitting instructions for performing an inference with at least one machine learning model associated with the at least one machine learning model ID.
Aspect 24: The method of any of the Aspects 14-23, in which the instructions comprise at least one of: instructions for model selection, instructions for model activation, instructions for model deactivation, instructions for model switching, instructions for model fallback, or instructions for model monitoring.
Aspect 25: The method of any of the Aspects 14-24, in which the level of support indicates at least one machine learning functionality, at least one machine learning model identification (ID) for each ML functionality, and a model transfer capability of the UE including a formula-based machine learning inference capability of the UE.
The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.
As used, the term “component” is intended to be broadly construed as hardware, firmware, and/or a combination of hardware and software. As used, a processor is implemented in hardware, firmware, and/or a combination of hardware and software.
Some aspects are described in connection with thresholds. As used, 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, not equal to the threshold, and/or the like.
It will be apparent that systems and/or methods described may be implemented in different forms of hardware, firmware, and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods were described without reference to specific software code—it being understood that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description.
Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. A phrase referring to “at least one 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, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).
No element, act, or instruction used should be construed as critical or essential unless explicitly described as such. Also, as used, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Furthermore, as used, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, and/or the like), and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used, the terms “has,” “have,” “having,” and/or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
The present application claims the benefit of U.S. Provisional Patent Application No. 63/443,799, filed on Feb. 7, 2023, and titled “NETWORK-USER EQUIPMENT (UE) COLLABORATION LEVELS FOR ARTIFICIAL INTELLIGENCE/MACHINE LEARNING (AI/ML) OPERATION,” the disclosure of which is expressly incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 63443799 | Feb 2023 | US |
