NETWORK ASSISTED INFORMATION

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for user equipment reception of network assisted information.

BACKGROUND

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, 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, and Long Term Evolution (LTE). 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).

A wireless network may include one or more base stations that support communication for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. “Downlink” (or “DL”) refers to a communication link from the base station to the UE, and “uplink” (or “UL”) refers to a communication link from the UE to the base station.

The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate on a municipal, national, regional, and/or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the 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, using CP-OFDM and/or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful.

SUMMARY

Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include transmitting, to a network node, a request for network assisted information associated with one or more of a machine learning (ML) model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE. The method may include receiving, from the network node, one or more of the ML model or the analytics.

Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include receiving, from a UE, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE. The method may include transmitting, to the UE, one or more of the ML model or the analytics.

Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit, to a network node, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE. The one or more processors may be configured to receive, from the network node, one or more of the ML model or the analytics.

Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive, from a UE, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE. The one or more processors may be configured to provide, to the UE, one or more of the ML model or the analytics.

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 transmit, to a network node, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive, from the network node, one or more of the ML model or the analytics.

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 receive, from a UE, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE. The set of instructions, when executed by one or more processors of the network node, may cause the network node to provide, to the UE, one or more of the ML model or the analytics.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, to a network node, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE. The apparatus may include means for receiving, from the network node, one or more of the ML model or the analytics.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from a UE, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE. The apparatus may include means for transmitting, to the UE, one or more of the ML model or the analytics.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the 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 hereinafter. 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 herein, 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.

While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios. Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements. For example, some aspects may be implemented via integrated chip embodiments or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, and/or artificial intelligence devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and/or system-level components. Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or summers). It is intended that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and/or end-user devices of varying size, shape, and constitution.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, 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 typical 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.

FIG. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

FIG. 2 is a diagram illustrating an example of a base station in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.

FIG. 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.

FIG. 4 is a diagram illustrating an example of generation of machine learning models and/or analytics, in accordance with the present disclosure.

FIG. 5 is a diagram illustrating an example associated with UE reception of network assisted information, in accordance with the present disclosure.

FIGS. 6-7 are diagrams illustrating example processes associated with UE reception of network assisted information, in accordance with the present disclosure.

FIGS. 8-9 are diagrams of example apparatuses for wireless communication, in accordance with the present disclosure.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafter 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. One skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, 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 herein. 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 herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

Several aspects of telecommunication 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, 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.

While aspects may be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G).

FIG. 1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more base stations 110 (shown as a BS 110a, a BS 110b, a BS 110c, and a BS 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e), and/or other network entities. A base station 110 is an entity that communicates with UEs 120. A base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and/or a transmission reception point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” can refer to a coverage area of a base station 110 and/or a base station subsystem serving this coverage area, depending on the context in which the term is used.

A base station 110 may provide communication 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 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having association with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or an in-home base station. In the example shown in FIG. 1, the BS 110a may be a macro base station for a macro cell 102a, the BS 110b may be a pico base station for a pico cell 102b, and the BS 110c may be a femto base station for a femto cell 102c. A base station may support one or multiple (e.g., three) cells.

In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a base station 110 that is mobile (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected to one another and/or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as a direct physical connection or a virtual network, using any suitable transport network.

The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a base station 110 or a UE 120) and send a transmission of the data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. In the example shown in FIG. 1, the BS 110d (e.g., a relay base station) may communicate with the BS 110a (e.g., a macro base station) and the UE 120d in order to facilitate communication between the BS 110a and the UE 120d. A base station 110 that relays communications may be referred to as a relay station, a relay base station, a relay, or the like.

The wireless network 100 may be a heterogeneous network that includes base stations 110 of different types, such as macro base stations, pico base stations, femto base stations, relay base stations, or the like. These different types of base stations 110 may have different transmit power levels, different coverage areas, and/or different impacts on interference in the wireless network 100. For example, macro base stations may have a high transmit power level (e.g., 5 to 40 watts) whereas pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1 to 2 watts).

A network controller 130 may couple to or communicate with a set of base stations 110 and may provide coordination and control for these base stations 110. The network controller 130 may communicate with the base stations 110 via a backhaul communication link. The base stations 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link.

The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. A UE 120 may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit. A UE 120 may be a cellular phone (e.g., 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 gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and/or a satellite radio), a vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, and/or any other suitable device that is configured to communicate via a wireless medium.

Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. An MTC UE and/or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and/or a location tag, that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered a Customer Premises Equipment. A UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and/or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.

In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, an air interface, or the like. A frequency may be referred to as a carrier, a frequency channel, 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 examples, 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, or a vehicle-to-pedestrian (V2P) protocol), and/or a mesh network. In such examples, a UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station 110.

Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

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

With the above examples in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and/or FR5) may be modified, and techniques described herein are applicable to those modified frequency ranges.

In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may transmit, to a network node, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE; and receive, from the network node, one or more of the ML model or the analytics. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

In some aspects, the network node may include a communication manager 150. In some aspects, the network node may include, or may be included in, a network device that is associated with the base station 110. For example, the network node may be part of a core network associated with the base station and/or may communicate with the UE 120 via the base station. As described in more detail elsewhere herein, the communication manager 150 may receive, from a UE, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE; and transmit, to the UE, one or more of the ML model or the analytics. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.

In some aspects, the term “base station” (e.g., the base station 110) or “network node” or “network entity” may refer to an aggregated base station, a disaggregated base station (e.g., described in connection with FIG. 9), an integrated access and backhaul (IAB) node, a relay node, and/or one or more components thereof. For example, in some aspects, “base station,” “network node,” or “network entity” may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, or a combination thereof. In some aspects, the term “base station,” “network node,” or “network entity” may refer to one device configured to perform one or more functions, such as those described herein in connection with the base station 110. In some aspects, the term “base station,” “network node,” or “network entity” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the term “base station,” “network node,” or “network entity” may refer to any one or more of those different devices. In some aspects, the term “base station,” “network node,” or “network entity” may refer to one or more virtual base stations and/or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term “base station,” “network node,” or “network entity” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.

As indicated above, FIG. 1 is provided as an example. Other examples may differ from what is described with regard to FIG. 1.

FIG. 2 is a diagram illustrating an example 200 of a base station 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure. The base station 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R≥1).

At the base station 110, a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120). The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS(s) selected for the UE 120 and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a 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 a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a through 232t. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232. Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas), shown as antennas 234a through 234t.

At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive the downlink signals from the base station 110 and/or other base stations 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems), shown as modems 254a through 254r. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller/processor 280. The term “controller/processor” may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and/or a CQI parameter, among other examples. In some examples, one or more components of the UE 120 may be included in a housing 284.

The network controller 130 may include a communication unit 294, a controller/processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

One or more antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252r) may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and/or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of FIG. 2.

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 that include RSRP, RSSI, RSRQ, and/or CQI) from the controller/processor 280. The transmit processor 264 may 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 the modems 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and/or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller/processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to FIGS. 5-9).

At the base station 110, the uplink signals from UE 120 and/or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232), 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 provide the decoded control information to the controller/processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of the antenna(s) 234, the modem(s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and/or the TX MIMO processor 230. The transceiver may be used by a processor (e.g., the controller/processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to FIGS. 5-9).

The processor 920 (of FIG. 9) of a network node, the controller/processor 280 of the UE 120, and/or any other component(s) of FIG. 2 may perform one or more techniques associated with UE reception of network assisted information, as described in more detail elsewhere herein. For example, the processor 920 of the network node, the controller/processor 280 of the UE 120, and/or any other component(s) of FIG. 2 may perform or direct operations of, for example, process 600 of FIG. 6, process 700 of FIG. 7, and/or other processes as described herein. The memory 930 and the memory 282 may store data and program codes for the network node and the UE 120, respectively. In some examples, the memory 930 and/or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the network node and/or the UE 120, may cause the one or more processors, the UE 120, and/or the network node to perform or direct operations of, for example, process 600 of FIG. 6, process 700 of FIG. 7, and/or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

In some aspects, the UE includes means for transmitting, to a network node, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE; and/or means for receiving, from the network node, one or more of the ML model or the analytics. The means for the UE to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.

In some aspects, the network node includes means for receiving, from a UE, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE; and/or means for transmitting, to the UE, one or more of the ML model or the analytics. In some aspects, the means for the network node to perform operations described herein may include, for example, one or more of a processor 920, memory 930, input component 940, output component 950, and/or communication component 960.

While blocks in FIG. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and/or the TX MIMO processor 266 may be performed by or under the control of the controller/processor 280.

As indicated above, FIG. 2 is provided as an example. Other examples may differ from what is described with regard to FIG. 2.

FIG. 3 is a diagram illustrating an example 300 disaggregated base station architecture, in accordance with the present disclosure.

Deployment of communication systems, such as 5G 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 RAN node, a core network node, a network element, or a network equipment, such as a base station (BS, e.g., base station 110), 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), eNB, NR BS, 5G NB, access point (AP), a TRP, a cell, or the like) 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, i.e., a virtual centralized 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 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.

The disaggregated base station architecture shown in FIG. 3 may include one or more CUs 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 325 via an E2 link, or a Non-Real Time (Non-RT) RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both). A CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as an F1 interface. The DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. The RUs 340 may communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some implementations, the UE 120 may be simultaneously served by multiple RUs 340.

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 an 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 bidirectionally 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 3rd 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 an O-eNB, 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 01) or via creation of RAN management policies (such as A1 policies).

As indicated above, FIG. 3 is provided as an example. Other examples may differ from what is described with regard to FIG. 3.

FIG. 4 is a diagram illustrating an example 400 of generation of machine learning models and/or analytics, in accordance with the present disclosure. As shown in FIG. 4, a UE may communicate via a network node of a wireless network. The UE may communicate with an application server via the network node to transmit and/or receive data associated with an application. The network node may provide data for ML and analytics to an additional network node that is configured to train and/or use ML models associated with network performance.

As shown by reference number 405, the UE may establish a service level agreement (SLA) for communication with the application server. For example, the UE may establish the SLA with the network node and/or the application server to support communication between the UE and the application server.

As shown by reference number 410, the UE may communicate with the application server via the network node. For example, the UE may receive a data stream from the application server, communicate in real-time with the application server, and/or communicate with another UE via the application server, among other examples. The UE may communicate with the application server via an application layer communication.

As shown by reference number 415, the network node may provide data for ML and analytics to the additional network node based at least in part on authorization. For example, the network node may be authorized to provide anonymized information associated with measured communication parameters for communication between the UE and the application server.

As shown by reference number 420, the additional network node may generate and/or train an ML model and/or generate analytics associated with one or more communication links supported by the network node. For example, the additional network node may train an ML model based at least in part on past performance of communications and may use the ML model to determine whether the network node supports an SLA of a new communication link.

In some networks, the additional network node may include a network data analytics function (NWDAF) that receives the data for ML and analytics via a data connection application function (DCAF). The DCAF may be operated by a network operator associated with the network nodes and may communicate with the UE via the network node (e.g., a base station), which communicates with the UE via a wireless connection. The NWDAF may communicate with the DCAF via one or more wireless and/or wired links and the DCAF may communicate with the network node via one or more wireless and/or wired links. In some networks, the DCAF and the NWDAF may be part of a core network associated with the network node. The core network may include multiple NWDAFs, with each NWDAF being associated with communications via one or more network nodes (e.g., base stations).

The SLA may be configured between the network operator and an application service provider (ASP) associated with the application server. The SLA may indicate, for each application identification in use by the ASP, an application function (AF) of the ASP (e.g., the DCAF) with which a UE application is to communicate, information that the UE application shares with the AF (e.g., subject to user consent), authentication information that enables the AF to verify authenticity of the UE application that provides data, and/or possible data anonymization, aggregation, or normalization algorithms for providing the data for ML and analytics, among other examples.

The UE application may be configured by the ASP with the application identification to use in communication with the AF. The UE application may be configured per application identification with an address of the AF to contact, parameters that the UE application is authorized to provide to the AF, and/or the authenticity information that enables the AF to verify authenticity of the AF that requests data.

The DCAF may generate ML models and/or analytics that benefit the network, and the ML model and/or analytics may also benefit the UE. However, the DCAF may have sensitive data that should not be released to unauthorized UEs. Therefore, networks may not release the ML models and/or analytics to prevent unauthorized access to the sensitive information. In this way, the UE may not have access to information that may have otherwise been used to make informed connection decisions and to conserve communication, network, power, and/or computing resources that may instead be used to attempt to communicate with an application server with inefficient or degraded communication parameters and/or via an inefficient communication link.

In some aspects described herein, a UE may request the ML models and/or the analytics from a network node (e.g., an NWDAF or a data collection coordination function (DCCF), among other examples). The UE may, in particular, request ML models and/or the analytics that indicate local analytics in the UE. For example, the UE may request that the network node provides a trained ML model for the local analytics or the UE may request that the network node provides network slice instance load statistics and/or service experience prediction. The UE may receive a response via an application client in the UE and may use the response for application layer analytics.

The UE may send the request via a DCAF, with the request including an analytics identification, an ML model identification, and/or an area of interest. The DCAF may select the network node (e.g., the NWDAF or the DCCF) based at least in part on the request. For example, the DCAF may have access to multiple network nodes that have ML models and/or analytics associated with different UEs and/or different parts of an associated network. The NWDAF or the DCCF may provide the ML model and/or the analytics to the UE via the DCAF based at least in part on the request.

For example, the UE may transmit the request using hypertext transfer protocol (HTTP) signaling via a user plane connection (e.g., with the DCAF). If the request indicates a request for an ML model, the request may indicate an associated ML model identification in the HTTP signaling. If the request indicates analytics (e.g., an analytics result), the request may indicate an analytics identification in the HTTP signaling. Additionally, or alternatively, the request may indicate a registration area identification, a slide identification, an event filter (e.g., indicate a report threshold, report frequency, report time interval, and/or report expiration time, among other example information).

The DCAF may select the NWDAF or DCCF to support the UE request. For example, the DCAF may identify the NWDAF or DCCF from a set of candidate NWDAFs or DCCFs based at least in part on an indication from a network repository function (NRF). For example, the DCAF may provide the ML model identification, analytics identification, registration area, and/or slide identification to the NRF. The NRF may reply by providing an indication of the NWDAF identification or the DCCF identification to the DCAF.

In some aspects, a UE internet protocol (IP) address of the UE is mapped to a subscription permanent identifier (SUPI) to match the UE to the ML model and/or the analytics. In some aspects, the DCAF may identify a mapping of the UE IP address to the SUPI in local storage, or the DCAF may request the mapping from an additional network node (e.g., a bootstrapping service function (BSF). The DCAF may provide the SUPI to the NWDAF along with the request for the ML model and/or the analytics. In some aspects, the DCAF may indicate the UE IP address in the request for the ML model and/or the analytics, and the NWDAF or the DCCF may perform the mapping. For example, the NWDAF or the DCCF may identify the mapping of the UE IP address to the SUPI in local storage, or the NWDAF or the DCCF may request the mapping from the additional network node (e.g., a bootstrapping service function (BSF)).

In some aspects, the NWDAF or the DCCF may check a user consent for delivery of the ML model or the analytics. For example, the NWDAF or the DCCF may request permissions or validate consent with a unified data management (UDM) entity.

Based at least in part on the NWDAF or the DCCF identifying the ML model or the analytics and/or verifying user consent to deliver the ML model or the analytics, the NWDAF or the DCCF may provide the ML model or the analytics to the UE via the network node (e.g., a base station). The NWDAF or the DCCF may provide the ML model or the analytics via a user plane communication to the UE.

Based at least in part on the DCAF obtaining the ML model or the analytics from the NWDAF or the DCCF, the DCAF may provide the UE with network assisted information (e.g., the ML model or the analytics) associated with network performance. The UE may use the network assisted information to make informed connection decisions and to conserve communication, network, power, and/or computing resources that may have otherwise been used to attempt to communicate with an application server with inefficient or degraded communication parameters and/or via an inefficient communication link.

FIG. 5 is a diagram illustrating an example 500 associated with UE reception of network assisted information, in accordance with the present disclosure. As shown in FIG. 5, network nodes of a wireless network (e.g., wireless network 100) may communicate with a UE (e.g., UE 120). In some aspects, the network nodes may include an RF network node (e.g., a base station 110), a first network node (e.g., a DCAF), a second network node (e.g., an NWDAF or a DCCF), a third network node (e.g., an NRF), a fourth network node (e.g., a BSF), and/or a fifth network node (e.g., a UDM). The UE may have established a connection prior to operations shown in FIG. 5. For example, the UE may have established a bearer to carry data between the UE and an application server via the network node. The UE may communicate directly with the RF network node and indirectly with the first network node and/or one or more additional network nodes. As used herein, a sending device (e.g., a network node or the UE) may provide information and/or a communication to a receiving device (e.g., another network node or the UE) directly or indirectly (e.g., via a network node shown in FIG. 5 or via one or more additional network nodes).

As shown by reference number 505, the UE may provide, and the first network node may receive, a request for an ML model and/or analytics. For example, the UE may transmit, to the RF network node, the request for the ML model and/or analytics. The RF network node may provide the request for the ML model and/or the analytics to the first network node. In this way, the UE may provide the request for the ML model and/or the analytics to the first network node via the RF network node.

The ML model and/or the analytics may be associated with an application layer communication that is associated with the UE. For example, the ML model and/or the analytics may be associated with an ongoing communication with an application server. In some aspects, the UE may provide the request for the ML model and/or the analytics via a user plane (e.g., a user plane connection with the UE) and/or via HTTP signaling.

In some aspects, the request for the ML model and/or the analytics may indicate one or more parameters and/or information elements associated with the ML model and/or the analytics. In this way, the first network node may identify a requested ML model or the analytics, verify that the UE is allowed access to the ML model and/or the analytics, and/or identify an amount of information requested. For example, the request for the ML model and/or the analytics may indicate an ML model identification, an analytics identification, an area of interest associated with the ML model or the analytics, a registration area identification, a slice identification associated with the ML model, an event filter, a report threshold, a report frequency, a report time interval, and/or a report expiration time.

As shown by reference number 510, the first network node may provide, and the third network node may receive, an NWDAF discovery request. For example, the first network node (e.g., a DCAF) may transmit the NWDAF discovery request to the third network node (e.g., NRF) to request an indication of an NWDAF (e.g., the second network node) that has access to the ML model and/or the analytics as indicated in the request for the ML model and/or the analytics received from the UE. In some aspects, the NWDAF discovery request may indicate an NWDAF identification and/or an analytics identification, and/or a slice identification for the third network node to use to identify the second network node.

As shown by reference number 515 the third network node may provide, and the first network node may receive, an NWDAF discovery response. For example, the NWDAF may indicate that the second network node is associated with (e.g., has or has access to) the ML model and/or the analytics requested by the UE.

As shown by reference number 520, the first network node may map the UE identification (ID). For example, the first network node may map a UE IP address (e.g., indicated with the request for ML model and/or analytics) to a SUPI of the UE within the wireless network. In some aspects, the first network node may map the UE identification based at least in part on identifying a mapping with local storage accessible to the first network node.

In some aspects, the first network node may map the UE identification based at least in part on providing one or more parameters to the fourth network node (e.g., a BSF and/or a SUPI mapping entity) and receiving an indication of a SUPI that maps to the UE IP address. The one or more parameters may include an IP address of the UE, a data network name (DNN) associated with the UE and/or the RF network node, and/or single-network slice selection assistance information (S-NSSAI). The fourth network node may provide an indication of the mapping of the UE to the SUPI based at least in part on the one or more parameters.

As shown by reference number 525, the first network node may provide, to the second network node, a request for an ML model and/or analytics. For example, the first network node (e.g., a DCAF) may provide the request for the ML model and/or analytics as received from the UE, or the first network node may provide the request for the ML model and/or analytics with modifications to the ML model and/or analytics as received from the UE. For example, the first network node may provide one or more additional parameters and/or information elements (e.g., an indication of the SUPI) and/or one or more fewer parameters and/or information elements (e.g., a UE IP address) to the second network node (e.g., an NWDAF or a DCCF).

As shown by reference number 530, the second network node may map the UE identification. For example, the second network node may map a UE IP address (e.g., indicated with the request for ML model and/or analytics as received from the first network node) to a SUPI of the UE within the wireless network. In some aspects, the second network node may map the UE identification based at least in part on identifying a mapping with local storage accessible to the second network node.

In some aspects, the second network node may map the UE identification based at least in part on providing one or more parameters to the fourth network node (e.g., a BSF and/or a SUPI mapping entity) and receiving an indication of the SUPI that maps to the UE IP address. The one or more parameters may include an IP address of the UE, a DNN associated with the UE and/or the RF network node, and/or S-NSSAI. The fourth network node may provide an indication of the mapping of the UE to the SUPI based at least in part on the one or more parameters.

As shown by reference number 535, the second network node may check user consent to deliver and/or expose the ML model and/or the analytics to the UE. For example, the second network node may provide the SUPI to the fifth network node (e.g., a UDM) to verify that the UE has given consent for the second network node to use UE information to train and/or generate an ML model associated with communications involving the UE. In some aspects, the fifth network node may receive an indication of the UE consent via an application server associated with the ML model and/or the analytics.

As shown by reference number 540, the second network node may train the ML model and/or generate an ML inference (e.g., consisting of or including the analytics). In some aspects, the second network node may use an ML model training operation, such as measuring inputs and corresponding outputs based at least in part on previous communications. The second network node may use inputs and corresponding outputs from communications involving the UE, the RF network node, and/or the application server, among other devices.

As shown by reference number 545, the second network node may provide, and the first network node may receive, the ML model and/or the analytics. The second network node may provide the ML model and/or the analytics directly or indirectly (e.g., via one or more additional network nodes).

As shown by reference number 550, the first network node may provide, and the UE may receive, the ML model and/or the analytics. In some aspects, the first network node may provide the ML model and/or the analytics via a user plane (e.g., a user plane connection with the UE). The RF network node may recive a user plane communication from the first network node (e.g., directly or indirectly) and may transmit the user plane communication to the UE.

As shown by reference number 555, the UE may perform application layer analytics. For example, the UE may perform application layer analytics based at least in part on the ML model and/or the analytics received from the first network node. In some aspects, the application layer analytics may include analyzing one or more communication links and/or a likelihood of satisfying an SLA associated with an application layer communication.

As indicated above, FIG. 5 is provided as an example. Other examples may differ from what is described with regard to FIG. 5.

FIG. 6 is a diagram illustrating an example process 600 performed, for example, by a UE, in accordance with the present disclosure. Example process 600 is an example where the UE (e.g., UE 120) performs operations associated with network assisted information.

As shown in FIG. 6, in some aspects, process 600 may include transmitting, to a network node, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE (block 610). For example, the UE (e.g., using communication manager 140 and/or transmission component 804, depicted in FIG. 8) may transmit, to a network node, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE, as described above.

As further shown in FIG. 6, in some aspects, process 600 may include receiving, from the network node, one or more of the ML model or the analytics (block 620). For example, the UE (e.g., using communication manager 140 and/or reception component 802, depicted in FIG. 8) may receive, from the network node, one or more of the ML model or the analytics, as described above.

Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, the network node comprises a data connection application function.

In a second aspect, alone or in combination with the first aspect, receiving the one or more of the ML model or the analytics comprises receiving the one or more of the ML model or the analytics via a user plane connection with the network node.

In a third aspect, alone or in combination with one or more of the first and second aspects, transmitting the request comprises one or more of transmitting the request via one or more additional network nodes, transmitting the request via HTTP signaling, or transmitting the request via a user plane connection with the network node.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the request comprises one or more of an ML model identification, an analytics identification, an area of interest associated with the ML model or the analytics, a registration area identification, a slice identification associated with the ML model, an event filter, a report threshold, a report frequency, a report time interval, or a report expiration time.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, process 600 includes performing application layer analytics based at least in part on the one or more of the ML model or the analytics.

Although FIG. 6 shows example blocks of process 600, in some aspects, process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 6. Additionally, or alternatively, two or more of the blocks of process 600 may be performed in parallel.

FIG. 7 is a diagram illustrating an example process 700 performed, for example, by a network node, in accordance with the present disclosure. Example process 700 is an example where the network node (e.g., the first network node) performs operations associated with network assisted information.

As shown in FIG. 7, in some aspects, process 700 may include receiving, from a UE, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE (block 710). For example, the network node (e.g., using input component 940 and/or communication component 960, depicted in FIG. 9) may receive, from a UE, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE, as described above.

As further shown in FIG. 7, in some aspects, process 700 may include providing, to the UE, one or more of the ML model or the analytics (block 720). For example, the network node (e.g., using output component 950 and/or communication component 960, depicted in FIG. 9) may provide, to the UE, one or more of the ML model or the analytics, as described above.

Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, the network node comprises a data connection application function.

In a second aspect, alone or in combination with the first aspect, process 700 includes transmitting, to an additional network node, a request for the ML model or the analytics, and receiving, from the additional network node, the ML model or the analytics.

In a third aspect, alone or in combination with one or more of the first and second aspects, the additional network node comprises an NWDAF or a data collection coordination function (DCCF).

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, process 700 includes transmitting, to a first additional network node, an indication of one or more elements of the request, and receiving, from the first additional network node, an indication of an identification of a second additional network node that has access to the ML model or the analytics.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process 700 includes one or more of mapping a UE to a SUPI and transmitting, to an additional network node that has access to the ML model or the analytics, an indication of the SUPI with a request for the ML model or the analytics, or transmitting, to the additional network node and with the request for the ML model or the analytics, an indication of a UE IP address associated with the UE.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, mapping the UE to the SUPI comprises identifying a mapping of the UE to the SUPI in local storage, or transmitting, to a SUPI mapping entity, an indication of one or more of the UE IP address, a DNN, or S-NSSAI, and receiving, from the SUPI mapping entity, an indication of the mapping of the UE to the SUPI.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, transmitting the one or more of the ML model or the analytics comprises transmitting the one or more of the ML model or the analytics via a user plane connection with the network node.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, receiving the request comprises one or more of receiving the request via one or more additional network nodes, receiving the request via HTTP signaling, or receiving the request via a user plane connection with the UE.

Although FIG. 7 shows example blocks of process 700, in some aspects, process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 7. Additionally, or alternatively, two or more of the blocks of process 700 may be performed in parallel.

FIG. 8 is a diagram of an example apparatus 800 for wireless communication. The apparatus 800 may be a UE, or a UE may include the apparatus 800. In some aspects, the apparatus 800 includes a reception component 802 and a transmission component 804, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus 800 may communicate with another apparatus 806 (such as a UE, a base station, or another wireless communication device) using the reception component 802 and the transmission component 804. As further shown, the apparatus 800 may include a communication manager 808 (e.g., the communication manager 140).

In some aspects, the apparatus 800 may be configured to perform one or more operations described herein in connection with FIG. 5. Additionally, or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as process 600 of FIG. 6. In some aspects, the apparatus 800 and/or one or more components shown in FIG. 8 may include one or more components of the UE described in connection with FIG. 2. Additionally, or alternatively, one or more components shown in FIG. 8 may be implemented within one or more components described in connection with FIG. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. 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 a controller or a processor to perform the functions or operations of the component.

The reception component 802 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 806. The reception component 802 may provide received communications to one or more other components of the apparatus 800. In some aspects, the reception component 802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 800. In some aspects, the reception component 802 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with FIG. 2.

The transmission component 804 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 806. In some aspects, one or more other components of the apparatus 800 may generate communications and may provide the generated communications to the transmission component 804 for transmission to the apparatus 806. In some aspects, the transmission component 804 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 806. In some aspects, the transmission component 804 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with FIG. 2. In some aspects, the transmission component 804 may be co-located with the reception component 802 in a transceiver.

The transmission component 804 may transmit, to a network node, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE. The reception component 802 may receive, from the network node, one or more of the ML model or the analytics.

The communication manager 808 may perform application layer analytics based at least in part on the one or more of the ML model or the analytics.

The number and arrangement of components shown in FIG. 8 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. 8. Furthermore, two or more components shown in FIG. 8 may be implemented within a single component, or a single component shown in FIG. 8 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in FIG. 8 may perform one or more functions described as being performed by another set of components shown in FIG. 8.

FIG. 9 is a diagram of example components of a device 900, which may correspond to the first network node, the second network node, the third network node, the fourth network node, and/or the fifth network node of FIG. 5. In some implementations, the first network node, the second network node, the third network node, the fourth network node, and/or the fifth network node of FIG. 5. include one or more devices 900 and/or one or more components of device 900. As shown in FIG. 9, device 900 may include a bus 910, a processor 920, a memory 930, an input component 940, an output component 950, and a communication component 960.

Bus 910 includes one or more components that enable wired and/or wireless communication among the components of device 900. Bus 910 may couple together two or more components of FIG. 9, such as via operative coupling, communicative coupling, electronic coupling, and/or electric coupling. Processor 920 includes a central processing unit, a graphics processing unit, a microprocessor, a controller, a microcontroller, a digital signal processor, a field-programmable gate array, an application-specific integrated circuit, and/or another type of processing component. Processor 920 is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, processor 920 includes one or more processors capable of being programmed to perform one or more operations or processes described elsewhere herein.

Memory 930 includes volatile and/or nonvolatile memory. For example, memory 930 may include random access memory (RAM), read only memory (ROM), a hard disk drive, and/or another type of memory (e.g., a flash memory, a magnetic memory, and/or an optical memory). Memory 930 may include internal memory (e.g., RAM, ROM, or a hard disk drive) and/or removable memory (e.g., removable via a universal serial bus connection). Memory 930 may be a non-transitory computer-readable medium. Memory 930 stores information, instructions, and/or software (e.g., one or more software applications) related to the operation of device 900. In some implementations, memory 930 includes one or more memories that are coupled to one or more processors (e.g., processor 920), such as via bus 910.

Input component 940 enables device 900 to receive input, such as user input and/or sensed input. For example, input component 940 may include a touch screen, a keyboard, a keypad, a mouse, a button, a microphone, a switch, a sensor, a global positioning system sensor, an accelerometer, a gyroscope, and/or an actuator. Output component 950 enables device 900 to provide output, such as via a display, a speaker, and/or a light-emitting diode. Communication component 960 enables device 900 to communicate with other devices via a wired connection and/or a wireless connection. For example, communication component 960 may include a receiver, a transmitter, a transceiver, a modem, a network interface card, and/or an antenna.

Device 900 may perform one or more operations or processes described herein. For example, a non-transitory computer-readable medium (e.g., memory 930) may store a set of instructions (e.g., one or more instructions or code) for execution by processor 920. Processor 920 may execute the set of instructions to perform one or more operations or processes described herein. In some implementations, execution of the set of instructions, by one or more processors 920, causes the one or more processors 920 and/or the device 900 to perform one or more operations or processes described herein. In some implementations, hardwired circuitry is used instead of or in combination with the instructions to perform one or more operations or processes described herein. Additionally, or alternatively, processor 920 may be configured to perform one or more operations or processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.

The number and arrangement of components shown in FIG. 9 are provided as an example. Device 900 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 9. Additionally, or alternatively, a set of components (e.g., one or more components) of device 900 may perform one or more functions described as being performed by another set of components of device 900.

The input component 940 and/or communication component 960 may receive, from a UE, a request for network assisted information associated with one or more of an ML model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE. The transmission component 804 may transmit, to the UE, one or more of the ML model or the analytics.

The output component 950 and/or communication component 960 may transmit, to an additional network node, a request for the ML model or the analytics.

The input component 940 and/or communication component 960 may receive, from the additional network node, the ML model or the analytics.

The output component 950 and/or communication component 960 may transmit, to a first additional network node, an indication of one or more elements of the request.

The input component 940 and/or communication component 960 may receive, from the first additional network node, an indication of an identification of a second additional network node that has access to the ML model or the analytics.

The following provides an overview of some Aspects of the present disclosure:

Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: transmitting, to a network node, a request for network assisted information associated with one or more of a machine learning (ML) model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE; and receiving, from the network node, one or more of the ML model or the analytics.

Aspect 2: The method of Aspect 1, wherein the network node comprises a data connection application function.

Aspect 3: The method of any of Aspects 1-2, wherein receiving the one or more of the ML model or the analytics comprises: receiving the one or more of the ML model or the analytics via a user plane connection with the network node.

Aspect 4: The method of any of Aspects 1-3, wherein transmitting the request comprises one or more of: transmitting the request via one or more additional network nodes, transmitting the request via hypertext transfer protocol (HTTP) signaling, or transmitting the request via a user plane connection with the network node.

Aspect 5: The method of any of Aspects 1-4, wherein the request comprises one or more of: an ML model identification, an analytics identification, an area of interest associated with the ML model or the analytics, a registration area identification, a slice identification associated with the ML model, an event filter, a report threshold, a report frequency, a report time interval, or a report expiration time.

Aspect 6: The method of any of Aspects 1-5, further comprising: performing application layer analytics based at least in part on the one or more of the ML model or the analytics.

Aspect 7: A method of wireless communication performed by a network node, comprising: receiving, from a user equipment (UE), a request for network assisted information associated with one or more of a machine learning (ML) model or analytics, the ML model or the analytics being associated with an application layer communication that is associated with the UE; and transmitting, to the UE, one or more of the ML model or the analytics.

Aspect 8: The method of Aspect 7, wherein the network node comprises a data connection application function.

Aspect 9: The method of any of Aspects 7-8, further comprising: transmitting, to an additional network node, a request for the ML model or the analytics, and receiving, from the additional network node, the ML model or the analytics.

Aspect 10: The method of Aspect 9, wherein the additional network node comprises a network data analytics function (NWDAF) or a data collection coordination function (DCCF).

Aspect 11: The method of any of Aspects 7-10, wherein the request comprises one or more of: an ML model identification, an analytics identification, an area of interest associated with the ML model or the analytics, a registration area identification, a slice identification associated with the ML model, an event filter, a report threshold, a report frequency, a report time interval, or a report expiration time.

Aspect 12: The method of any of Aspects 7-11, further comprising: transmitting, to a first additional network node, an indication of one or more elements of the request; and receiving, from the first additional network node, an indication of an identification of a second additional network node that has access to the ML model or the analytics.

Aspect 13: The method of any of Aspects 7-12, further comprising one or more of: mapping a UE to a subscription permanent identifier (SUPI) and transmitting, to an additional network node that has access to the ML model or the analytics, an indication of the SUPI with a request for the ML model or the analytics; or transmitting, to the additional network node and with the request for the ML model or the analytics, an indication of a UE internet protocol (IP) address associated with the UE.

Aspect 14: The method of Aspect 13, wherein mapping the UE to the SUPI comprises: identifying a mapping of the UE to the SUPI in local storage, or transmitting, to a SUPI mapping entity, an indication of one or more of: the UE IP address, a data network name (DNN), or single-network slice selection assistance information (S-NSSAI), and receiving, from the SUPI mapping entity, an indication of the mapping of the UE to the SUPI.

Aspect 15: The method of any of Aspects 7-14, wherein transmitting the one or more of the ML model or the analytics comprises: transmitting the one or more of the ML model or the analytics via a user plane connection with the network node.

Aspect 16: The method of any of Aspects 7-15, wherein receiving the request comprises one or more of: receiving the request via one or more additional network nodes, receiving the request via hypertext transfer protocol (HTTP) signaling, or receiving the request via a user plane connection with the UE.

Aspect 17: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-16.

Aspect 18: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-16.

Aspect 19: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-16.

Aspect 20: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-16.

Aspect 21: 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-16.

The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and 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, and/or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware and/or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware 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 are described herein without reference to specific software code, since those skilled in the art will understand that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein.

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, not equal to the threshold, or the like.

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. Many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, 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 herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items 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 herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of”).

NETWORK ASSISTED INFORMATION

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

PCT Information