Patent Application
20240284240
Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for non-binding analytics-based information for a wireless link.
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 network nodes that support communication for wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. “Downlink” (or “DL”) refers to a communication link from the network node to the UE, and “uplink” (or “UL”) refers to a communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and/or a wireless personal area network (WPAN) link, among other examples).
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.
Some aspects described herein relate to a method of wireless communication performed by a first network node. The method may include receiving link information associated with a wireless link between a second network node and a user equipment (UE). The method may include providing non-binding analytics-based information associated with the wireless link.
Some aspects described herein relate to a method of wireless communication performed by a radio access network (RAN) node. The method may include receiving non-binding analytics-based information associated with a wireless link between the RAN node and a UE. The method may include communicating with the UE using a radio resource management (RRM) configuration that is based at least in part on the non-binding analytics-based information.
Some aspects described herein relate to a first network node for wireless communication. The first 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 link information associated with a wireless link between a second network node and a UE. The one or more processors may be configured to provide non-binding analytics-based information associated with the wireless link.
Some aspects described herein relate to a RAN node for wireless communication. The radio access network may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive non-binding analytics-based information associated with a wireless link between the RAN node and a UE. The one or more processors may be configured to communicate with the UE using an RRM configuration that is based at least in part on the non-binding analytics-based information.
Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a first network node. The set of instructions, when executed by one or more processors of the first network node, may cause the first network node to receive link information associated with a wireless link between a second network node and a UE. The set of instructions, when executed by one or more processors of the first network node, may cause the first network node to provide non-binding analytics-based information associated with the wireless link.
Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a RAN node. The set of instructions, when executed by one or more processors of the RAN, may cause the RAN node to receive non-binding analytics-based information associated with a wireless link between the RAN node and a UE. The set of instructions, when executed by one or more processors of the RAN, may cause the RAN node to communicate with the UE using an RRM configuration that is based at least in part on the non-binding analytics-based information.
Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving link information associated with a wireless link between a second network node and a UE. The apparatus may include means for providing non-binding analytics-based information associated with the wireless link.
Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving non-binding analytics-based information associated with a wireless link between the RAN node and a UE. The apparatus may include means for communicating with the UE using an RRM configuration that is based at least in part on the non-binding analytics-based information.
Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network entity, network node, 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.
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.
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).
In some examples, a network node 110 is or includes a network node that communicates with UEs 120 via a radio access link, such as an RU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or a core network via a backhaul link, such as a CU. In some examples, a network node 110 (such as an aggregated network node 110 or a disaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and/or one or more DUs. A network node 110 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, a transmission reception point (TRP), a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 in the wireless network 100 through various types of fronthaul, midhaul, and/or backhaul interfaces, such as a direct physical connection, an air interface, or a virtual network, using any suitable transport network.
In some examples, a network node 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 network node 110 and/or a network node subsystem serving this coverage area, depending on the context in which the term is used. A network node 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 subscriptions. 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 network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In the example shown in
In some aspects, the terms “base station” or “network node” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, “base station” or “network node” may refer to a CU, a DU, an 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 terms “base station” or “network node” may refer to one device configured to perform one or more functions, such as those described herein in connection with the network node 110. In some aspects, the terms “base station” or “network node” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a quantity 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 terms “base station” or “network node” may refer to any one or more of those different devices. In some aspects, the terms “base station” or “network node” may refer to one or more virtual base stations 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 terms “base station” or “network node” 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.
The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (e.g., a network node 110 or a UE 120) and send a transmission of the data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. In the example shown in
The wireless network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, or the like. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and/or different impacts on interference in the wireless network 100. For example, macro network nodes may have a high transmit power level (e.g., 5 to 40 watts) whereas pico network nodes, femto network nodes, and relay network nodes 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 network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.
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, a UE function of a network node, and/or any other suitable device that is configured to communicate via a wireless or wired 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 network node, 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 network node 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 network node 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 network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive link information associated with a wireless link between a second network node and a UE; and provide non-binding analytics-based information associated with the wireless link. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.
In some aspects, the RAN node may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive non-binding analytics-based information associated with a wireless link between the RAN node and a UE; and communicate with the UE using a radio resource management (RRM) configuration that is based at least in part on the non-binding analytics-based information. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.
As indicated above,
At the network node 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 network node 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 network node 110 and/or other network nodes 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 network node 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
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 network node 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
At the network node 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 network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 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 network node 110 may include a modulator and a demodulator. In some examples, the network node 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
The controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other component(s) of
In some aspects, the first network node includes means for receiving link information associated with a wireless link between a second network node and a UE; and/or means for providing non-binding analytics-based information associated with the wireless link. The means for the first network node to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.
In some aspects, the RAN node includes means for receiving non-binding analytics-based information associated with a wireless link between the RAN node and a UE; and/or means for communicating with the UE using an RRM configuration that is based at least in part on the non-binding analytics-based information. In some aspects, the means for the RAN node to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.
While blocks in
As indicated above,
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, a base station, or a network equipment may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP, or a cell, among other examples), or one or more units (or one or more components) performing base station functionality, may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station. “Network entity” or “network node” may refer to a disaggregated base station, or to one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).
An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A disaggregated base station (e.g., a disaggregated network node) may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network 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 network 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, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.
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 IAB network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of communication systems by separating base station functionality into one or more units that can be individually deployed. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.
Each of the units, including 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 with 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 one or multiple communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of 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, and 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) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples. 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 (for example, Central Unit-User Plane (CU-UP) functionality), control plane functionality (for example, Central Unit-Control Plane (CU-CP) functionality), 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. A CU-UP unit can communicate bidirectionally with a 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 a DU 330, as necessary, for network control and signaling.
Each 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 depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples. In some aspects, the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT), an inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which also may be referred to as a 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.
Each RU 340 may implement lower-layer functionality. 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 an FFT, performing an iFFT, digital beamforming, or PRACH extraction and filtering, among other examples, based on a functional split (for example, a functional split defined by the 3GPP), such as a lower layer functional split. In such an architecture, each RU 340 can be operated 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 each DU 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) platform 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, non-RT RICs 315, 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 each of one or more RUs 340 via a respective 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 an O1 interface) or via creation of RAN management policies (such as A1 interface policies).
As indicated above,
The near-RT RIC may provide indications to the RAN node to control and assist in RRM of the RAN node in providing one or more Uu interfaces to one or more UEs. The near-RT RIC may generate control and assistance information based at least in part on one or more metrics provided by the UE, the RAN node, and/or an application server to which the UE is connected (e.g., via the RAN node). The near-RT RIC and the RAN node may communicate via an E2 protocol.
As shown in
As shown by reference number 410, the RAN node may forward the information to a core network (CN). As shown by reference number 415, the CN may forward the information via the internet to the near-RT RIC. Alternatively, as shown by reference number 420, the CN may forward the information to an application server in communication with the UE. As shown by reference number 425, the application server may forward the information via the internet to the near-RT RIC.
As shown by reference number 430, the near-RT RIC may generate a control request or policy for the RAN node based at least in part on the information. In some aspects, the control request or policy may be based at least in part on occurrence of a particular event or a trigger condition, among other examples. The control request or policy may include a RIC subscription procedure (e.g., used to send a policy to the RAN node), a RIC control procedure (e.g., used to send control commands to the RAN node), or a RIC query procedure (e.g., used to request information from the RAN). An example policy may indicate a number of UEs that the RAN node is to allow to connect. An example control procedure may indicate to handover a UE to another RAN node. An example RIC query may include a request for a UE identifier for the UE in communication with the RAN node.
As shown by reference number 435, the near-RT RIC may send a control request or policy to the RAN node. The RAN node may be compelled to comply with the control request or policy.
Additional information may be beneficial to the RAN node for performing RRM actions. For example, the additional information may be useful to a communication manager of the RAN node for setting scheduling for the UE. However, the near-RT RIC may not have sufficient information to provide a control request or policy. In this case, the near-RT RIC may be unable to provide the additional information to the RAN node. In this way, the RAN node may operate with reduced spectral efficiency by providing an inefficient allocation of resources to the UE, and/or may operate with an unnecessarily high amount of overhead that is consumed by scheduling network resources to the UE with dynamic scheduling and/or with periodic resources that are often modified.
As indicated above,
In some aspects described herein, a near-RT RIC may provide assistance information to the RAN node, without the assistance information compelling the RAN node to perform a requested task or set an indicated policy. This assistance information may be used by the RAN node to perform one or more RRM actions which is not controlled by RIC. Such assistance information may include information which is not supported by 3GPP protocols. For example, the assistance information may include information about the UE communication behavior that is not reportable via the Uu interface (e.g., the information is reportable via an application plane that is not read by the RAN node). In this case, the information may be sent to the near-RT RIC via an O-RAN method, and the near-RT RIC may send the information to the RAN node as assistance information. The assistance information to prioritize certain downlink or uplink streams of data may be indicated to the MAC scheduler as a recommendation.
Some examples of the assistance information may include information regarding UE behavior to a MAC scheduler of the RAN node. In some aspects, the information may assist in scheduling periodic and time sensitive uplink grants. For example, a camera device may want to upload ‘x’ bytes of data at ‘y’ intervals starting at a time and with ‘z’ duration. In this case, this information is not supported by RRC communications. However, the UE may provide this information to the near-RT RIC, and the near-RT RIC may provide this information as assistance info to the RAN node.
The assistance information may be referred to as Class 2 Assistance Information and/or non-binding analytics-based information. A procedure to deliver the non-binding analytics-based information may be referred to as a RIC Assistance Information from Near-RT RIC to RAN in the E2 application protocol (E2AP). This message (e.g., a Class 2 message) may carry an E2 service management (E2SM) container that provides additional, non-binding information to the RAN node. Information elements of the container may be encoded via respective E2SMs using different message formats. E2AP is an extensible authentication protocol (EAP) protocol over an application layer. An E2SM is a component of the E2AP message.
In some aspects, an E2AP RIC assistance information message structure may include fields for IE/group names, a presence indicator, a range, an information element (IE) type and reference, a semantics description, an indication of criticality, and/or an indication of assigned criticality. IE/group names associated with the non-binding analytics-based information may include a RIC assistance information header and/or a RIC assistance information definition, with each defined in respective E2SMs. An IE type and reference may be indicated with an octet string. A semantics description may be defined in a RAN function specific E2 service model.
Based at least in part on the near-RT RIC being able to provide non-binding analytics-based information to the RAN node, the RAN node may improve scheduling and other RRM functions. For example, the near-RT RIC may operate with improved spectral efficiency by providing an efficient allocation of resources to the UE, and/or may operate with a reduced amount of overhead that may have otherwise been consumed by scheduling network resources to the UE with dynamic scheduling and/or with periodic resources that are often modified.
As shown by reference number 505, the UE or application server may obtain link information associated with a link between the UE and the second network node. The link information may be associated with a wireless link between the second network node and the UE. For example, the UE may measure one or more parameters of the Uu interface, may predict an amount, periodicity, priority, and/or duration of expected communications. For example, the UE may expect to communicate using downlink communications with a periodicity that is based at least in part on a refresh rate of a stream of data received by the UE. Similarly, the UE may expect to communicate using uplink communications with a periodicity that is based at least in part on a refresh rate of a stream of data transmitted by the UE.
The UE may provide the link information to the application server via an application layer communication. In some aspects, the link information includes application layer information. In some aspects, the link information is associated with UE uplink communications and/or UE downlink communications. For example, the link information may be associated with an uplink stream of data or a downlink stream of data, or both.
In some aspects, the application server may be associated with the core network, or an edge network associated with the RAN node. Alternatively, the application server may be outside of the core network and edge network (e.g., a third party application server).
As shown by reference number 510, the first network node may receive the link information from the UE or application server. In some aspects, the first network node may receive the link information from the UE via the application server.
As shown by reference number 515, the first network node may identify non-binding analytics-based information for the second network node based at least in part on the link information. In some aspects, the non-binding analytics-based information includes a recommendation for a configuration for the wireless link between the second network node and the UE.
In some aspects, the non-binding analytics-based information may include an expected payload for communications between the UE and the second network node, a payload size (typically communicated by the UE to the RAN node as a buffer status report (BSR)), an expected communication interval for the communications, an expected duration of the communications, and/or prioritization information for the communications, among other examples. In this way, the second network node may configure resources to accommodate parameters of communications of the UE based at least in part on the non-binding analytics-based information.
As shown by reference number 520, the first network node may provide the non-binding analytics-based information to the second network node. In some aspects, the first network may provide the non-binding analytics-based information to the second network node via a an E2 connection.
In some aspects, the first network node may provide the non-binding analytics-based information to the second node directly or as a hop to an end node. For example, the first network node may provide the non-binding analytics-based information to a CU associated with the second network node, a DU associated with the network node, a gNB, an eNB, or a base station.
As shown by reference number 525, the second network node may configure communications with the UE based at least in part on the non-binding analytics-based information. For example, the second network node may use the non-binding analytics-based information to configure an efficient communication schedule with the UE, among other RRM operations.
Additionally, or alternatively, the second network node may schedule or offload one or more additional UEs based at least in part on the non-binding analytics-based information. For example, based at least in part on an amount of traffic and/or characteristics of the traffic associated with the UE, the second network node may schedule periodic communications with other UEs to avoid scheduling collision and/or may handover one or more other UEs to a neighbor cell based at least in part on an expected load on the second network node.
As shown by reference number 530, the second network node may communicate with the UE (e.g., using the Uu interface) based at least in part on the non-binding analytics-based information.
Based at least in part on the near-RT RIC being able to provide non-binding analytics-based information to the RAN node, the RAN node may improve scheduling and other RRM functions. For example, the near-RT RIC may operate with improved spectral efficiency by providing an efficient allocation of resources to the UE, and/or may operate with a reduced amount of overhead that may have otherwise been consumed by scheduling network resources to the UE with dynamic scheduling and/or with periodic resources that are often modified.
As indicated above,
As shown in
As further shown in
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 non-binding analytics-based information comprises a recommendation for a configuration for the wireless link between the second network node and the UE.
In a second aspect, alone or in combination with the first aspect, the link information comprises application layer information.
In a third aspect, alone or in combination with one or more of the first and second aspects, the first network node comprises an RIC.
In a fourth aspect, alone or in combination with one or more of the first through third aspects, providing the non-binding analytics-based information comprises providing the non-binding analytics-based information via an E2 connection.
In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, providing the non-binding analytics-based information comprises providing the non-binding analytics-based information to one or more of the second network node, a CU associated with the second network node, or a DU associated with the second network node.
In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the information associated with the wireless link is associated with one or more of UE uplink communications, or UE downlink communications.
In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, receiving the link information associated with the wireless link comprises receiving the link information from the UE via an application server.
In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the non-binding analytics-based information comprises one or more of an expected payload for communications between the UE and the second network node, an expected communication interval for the communications, an expected duration of the communications, or information for the communications.
Although
As shown in
As further shown in
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 non-binding analytics-based information comprises a recommendation for a configuration for the wireless link between the RAN node and the UE.
In a second aspect, alone or in combination with the first aspect, communicating with the UE using RRM that is based at least in part on the non-binding analytics-based information comprises complying with the recommendation, not complying with the recommendation based at least in part on one or more RRM parameters at the RAN node, or complying with a modification to the recommendation.
In a third aspect, alone or in combination with one or more of the first and second aspects, the non-binding analytics-based information is based at least in part on link information associated with the wireless link between the RAN node and the UE.
In a fourth aspect, alone or in combination with one or more of the first through third aspects, receiving the non-binding analytics-based information comprises receiving the non-binding analytics-based information via a RIC.
In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, receiving the non-binding analytics-based information comprises receiving the non-binding analytics-based information via an E2 connection.
In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the information associated with the wireless link is associated with one or more of UE uplink communications, or UE downlink communications.
In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the non-binding analytics-based information comprises one or more of an expected payload for communications between the UE and the RAN node, an expected communication interval for the communications, an expected duration of the communications, or information for the communications.
In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, communicating with the UE using radio resource management that is based at least in part on the non-binding analytics-based information comprises communicating based at least in part on the non-binding analytics-based information and one or more of communications between the RAN node and one or more additional UEs, a frequency bandwidth of the RAN node, a capacity of over-the-air communications associated with the RAN node, available computing resources of the RAN node, available backhaul capacity between the RAN node and a core network, or available power resources of the RAN node.
Although
In some aspects, the apparatus 800 may be configured to perform one or more operations described herein in connection with
The reception component 802 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 808. 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 first network node described in connection with
The transmission component 804 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 808. 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 808. 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 808. 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 first network node described in connection with
The communication manager 806 may support operations of the reception component 802 and/or the transmission component 804. For example, the communication manager 806 may receive information associated with configuring reception of communications by the reception component 802 and/or transmission of communications by the transmission component 804. Additionally, or alternatively, the communication manager 806 may generate and/or provide control information to the reception component 802 and/or the transmission component 804 to control reception and/or transmission of communications.
The reception component 802 may receive link information associated with a wireless link between a second network node and a UE. The communication manager 806 may provide non-binding analytics-based information associated with the wireless link.
The number and arrangement of components shown in
In some aspects, the apparatus 900 may be configured to perform one or more operations described herein in connection with
The reception component 902 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 908. The reception component 902 may provide received communications to one or more other components of the apparatus 900. In some aspects, the reception component 902 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 900. In some aspects, the reception component 902 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 RAN node described in connection with
The transmission component 904 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 908. In some aspects, one or more other components of the apparatus 900 may generate communications and may provide the generated communications to the transmission component 904 for transmission to the apparatus 908. In some aspects, the transmission component 904 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 908. In some aspects, the transmission component 904 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 RAN node described in connection with
The communication manager 906 may support operations of the reception component 902 and/or the transmission component 904. For example, the communication manager 906 may receive information associated with configuring reception of communications by the reception component 902 and/or transmission of communications by the transmission component 904. Additionally, or alternatively, the communication manager 906 may generate and/or provide control information to the reception component 902 and/or the transmission component 904 to control reception and/or transmission of communications.
The number and arrangement of components shown in
The following provides an overview of some Aspects of the present disclosure:
Aspect 1: A method of wireless communication performed by a first network node, comprising: receiving link information associated with a wireless link between a second network node and a user equipment (UE); and providing non-binding analytics-based information associated with the wireless link.
Aspect 2: The method of Aspect 1, wherein the non-binding analytics-based information comprises a recommendation for a configuration for the wireless link between the second network node and the UE.
Aspect 3: The method of any of Aspects 1-2, wherein the link information comprises application layer information.
Aspect 4: The method of any of Aspects 1-3, wherein the first network node comprises a radio access network (RAN) intelligent controller (RIC).
Aspect 5: The method of any of Aspects 1-4, wherein providing the non-binding analytics-based information comprises providing the non-binding analytics-based information via an E2 connection.
Aspect 6: The method of any of Aspects 1-5, wherein providing the non-binding analytics-based information comprises providing the non-binding analytics-based information to one or more of: the second network node, a CU associated with the second network node, or a DU associated with the second network node.
Aspect 7: The method of any of Aspects 1-6, wherein the information associated with the wireless link is associated with one or more of: UE uplink communications, or UE downlink communications.
Aspect 8: The method of any of Aspects 1-7, wherein receiving the link information associated with the wireless link comprises receiving the link information from the UE via an application server.
Aspect 9: The method of any of Aspects 1-8, wherein the non-binding analytics-based information comprises one or more of: an expected payload for communications between the UE and the second network node, an expected communication interval for the communications, an expected duration of the communications, or prioritization information for the communications.
Aspect 10: A method of wireless communication performed by a radio access network (RAN) network node, comprising: receiving non-binding analytics-based information associated with a wireless link between the RAN node and a user equipment (UE); and communicating with the UE using a radio resource management (RRM) configuration that is based at least in part on the non-binding analytics-based information.
Aspect 11: The method of Aspect 10, wherein the non-binding analytics-based information comprises a recommendation for a configuration for the wireless link between the RAN node and the UE.
Aspect 12: The method of Aspect 11, wherein communicating with the UE using RRM that is based at least in part on the non-binding analytics-based information comprises: complying with the recommendation, not complying with the recommendation based at least in part on one or more RRM parameters at the RAN node, or complying with a modification to the recommendation.
Aspect 13: The method of any of Aspects 10-12, wherein the non-binding analytics-based information is based at least in part on link information associated with the wireless link between the RAN node and the UE.
Aspect 14: The method of any of Aspects 10-13, wherein receiving the non-binding analytics-based information comprises: receiving the non-binding analytics-based information via a radio access network (RAN) intelligent controller (RIC).
Aspect 15: The method of any of Aspects 10-14, wherein receiving the non-binding analytics-based information comprises receiving the non-binding analytics-based information via an E2 connection.
Aspect 16: The method of any of Aspects 10-15, wherein the information associated with the wireless link is associated with one or more of: UE uplink communications, or UE downlink communications.
Aspect 17: The method of any of Aspects 10-16, wherein the non-binding analytics-based information comprises one or more of: an expected payload for communications between the UE and the RAN node, an expected communication interval for the communications, an expected duration of the communications, or prioritization information for the communications.
Aspect 18: The method of any of Aspects 10-17, wherein communicating with the UE using radio resource management that is based at least in part on the non-binding analytics-based information comprises communicating based at least in part on the non-binding analytics-based information and one or more of: communications between the RAN node and one or more additional UEs, a frequency bandwidth of the RAN node, a capacity of over-the-air communications associated with the RAN node, available computing resources of the RAN node, available backhaul capacity between the RAN node and a core network, or available power resources of the RAN node.
Aspect 19: 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-18.
Aspect 20: 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-18.
Aspect 21: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-18.
Aspect 22: 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-18.
Aspect 23: 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-18.
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”).
