WO2023049345A1 - Optimisation d'équilibrage de charge (lbo) pour systèmes 5g - Google Patents

Optimisation d'équilibrage de charge (lbo) pour systèmes 5g Download PDF

Info

Publication number
WO2023049345A1
WO2023049345A1 PCT/US2022/044536 US2022044536W WO2023049345A1 WO 2023049345 A1 WO2023049345 A1 WO 2023049345A1 US 2022044536 W US2022044536 W US 2022044536W WO 2023049345 A1 WO2023049345 A1 WO 2023049345A1
Authority
WO
WIPO (PCT)
Prior art keywords
lbo
function
handover trigger
lbo function
mns
Prior art date
Application number
PCT/US2022/044536
Other languages
English (en)
Inventor
Joey Chou
Yizhi Yao
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Priority to CN202280037594.6A priority Critical patent/CN117378182A/zh
Publication of WO2023049345A1 publication Critical patent/WO2023049345A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/22—Performing reselection for specific purposes for handling the traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/249—Reselection being triggered by specific parameters according to timing information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/16—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using machine learning or artificial intelligence

Definitions

  • This disclosure generally relates to systems and methods for wireless communications and, more particularly, to load balancing optimization for 5G systems.
  • PCF policy control function
  • NF control plane network functions
  • FIG. 1 depicts an illustrative schematic diagram for load balancing optimization, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 2 depicts an illustrative schematic diagram for load balancing optimization, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 3 depicts an illustrative schematic diagram for load balancing optimization, in accordance with one or more example embodiments of the present disclosure.
  • FIGs. 4A-4B depict illustrative schematic diagrams for load balancing optimization, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 5 depicts an illustrative schematic diagram for load balancing optimization, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 6 depicts an illustrative schematic diagram for load balancing optimization, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 7 illustrates a flow diagram of illustrative process for an illustrative load balancing optimization system, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 8 illustrates an example network architecture, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 9 schematically illustrates a wireless network, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 10 illustrates components of a computing device, in accordance with one or more example embodiments of the present disclosure.
  • LBO Load Balancing Optimization
  • Example embodiments of the present disclosure relate to systems, methods, and devices for load balancing optimization for 5G systems.
  • embodiments of the present disclosure are directed to Load Balancing Optimization (LBO) and Mobility Robustness Optimization (MRO).
  • LBO Load Balancing Optimization
  • MRO Mobility Robustness Optimization
  • this disclosure provides the following new features for 5 G LBO: 1) Self-Organizing Networks (SON) procedures to support D-LBO and C-LBO; 2) The definition of DLBOFunction Information Object Class (IOC) that include the control of LBO function and ranges of handover (HO) and/or reselection parameters to support LBO actions; 3) Enhancement to notification message to report which SON function is generating the notification; 4) Revise MRO and PCI configuration procedures to use sonFunction attribute to indicate the SON function generating the notification.
  • SON Self-Organizing Networks
  • IOC DLBOFunction Information Object Class
  • Enhancement to notification message to report which SON function is generating the notification
  • Revise MRO and PCI configuration procedures to use sonFunction attribute to indicate the
  • FIG. 1 depicts an illustrative schematic diagram for load balancing optimization, in accordance with one or more example embodiments of the present disclosure.
  • the objective of Load Balancing Optimization is to automatically distribute user traffic among neighboring cells to ensure the radio resources are efficiently used, while providing quality end-user experience and performance.
  • LBO Load Balancing Optimization
  • D-LBO Distributed LBO
  • C-LBO Centralized LBO
  • the LBO management system configure the ranges of HO and/or reselection parameters at the D-LBO function in gNB that would collect and anallOe the load information to determine the actions that may include 1) UE selection where the gNB selects and commands some UE(s) to handover to non-congested neighboring cells, 2) cell reselection where the gNB directs some UE(s) to camp on less congested neighboring cells, and 3) mobility setting where the gNB modifies the handover parameters to change the coverage of a congested cell.
  • the C-LBO function in 0AM would collect and anallOe the LBO related measurements to determine the actions to balance traffic loads among NR cells.
  • the actions are to configure the ranges of HO and/or reselection parameters at gNB.
  • FIG. 2 depicts an illustrative schematic diagram for load balancing optimization, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 2 depicts a procedure that describes how Distributed Self-Organizing Networks (D-SON) management function can manage the LBO function. It is assumed that the D-SON management function has consumed the performance assurance MnS to create performance measurement (PM) jobs to collect handover related measurements.
  • D-SON Distributed Self-Organizing Networks
  • the D-SON management function consumes the management service for network function (NF) provisioning with modify MOI Attributes operation to configure the ranges of HO and/or reselection parameters for the LBO function.
  • the MnS of provisioning sets the ranges for MRO function (NOTE).
  • the D-SON management function consumes the NF provisioning MnS with modify MOI Attributes operation to enable the LBO function for a given NR cell if it is not enabled.
  • the provisioning MnS enables the LBO function.
  • the LBO function performs actions to balance the traffic loads among NR cells.
  • the LBO function indicates that LBO actions have been performed.
  • D- SON management function collects LBO related performance measurements. The D-SON management function analyses the measurements to evaluate the LBO performance.
  • the D- SON management function consumes the MnS of provisioning with modify MOI Attributes operation to update the ranges of HO and/or reselection parameters if the LBO failed to meet expections.
  • the MnS of provisioning updates the ranges of handover parameters. It should be noted that the interface between provisioning MnS and D-LBO function is not subject to standardization.
  • FIG. 3 depicts an illustrative schematic diagram for load balancing optimization, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 3 depicts a procedure to describe how C-LBO function performs load balancing among NR cells. It is assumed that PM jobs have been created to collect LBO related measurements.
  • the C-LBO function collects LBO related performance measurements.
  • the C-LBO function analyses the measurements to evaluate the LO performance.
  • the D-SON management function performs the following actions when the LBO performance failed to meet expections:
  • the MnS of provisioning updates the ranges of handover parameters (NOTE).
  • FIGs. 4A-4B depict illustrative schematic diagrams for load balancing optimization, in accordance with one or more example embodiments of the present disclosure.
  • a load balancing optimization system may facilitate the definition of DLBOFunction Information Object Class (IOC).
  • FIG. 4A shows an NRM fragment for DLBO Management.
  • FIG. 4B shows the inheritance hierarchy.
  • a load balancing optimization system may define a DLBOFunction IOC.
  • This IOC contains attributes to support the D-SON function of LBO.
  • the DLBO MOI at the lower level overrides the DLBO MOIs at the higher level(s) of the same containment tree.
  • the DLBOFunction IOC includes attributes inherited from Top IOC having the following attributes in Table 1:
  • a load balancing optimization system may facilitate the following Ranges of HO and/or reselection parameters as shown in Table 3:
  • a load balancing optimization system may provide enhancement to the notification message (adding sonFunction attribute) to report which SON function is generating the notification.
  • the notification notify MOI Attribute ValueChange notifies the subscribed consumers that changes of one or several attributes of a Managed Object Instance in the NRM.
  • a load balancing optimization system may revise MRO and PCI configuration procedures to use sonFunction attribute to indicate the SON function generating the notification as shown in Table 5:
  • the producer of provisioning MnS should have the capability to notify the authorized consumer that the action haven taken to mitigate the handover issues.
  • FIG. 5 depicts an illustrative schematic diagram for load balancing optimization, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 5 there is shown an MRO procedure that describes how D-SON management function can manage the MRO function. It is assumed that the D-SON management function has consumed the performance assurance MnS to create PM jobs to collect handover-related measurements.
  • the D-SON management function consumes the provisioning MnS with modifyMOIAttributes operation to configure targets for the MRO function.
  • the provisioning MnS sets the targets for MRO function (NOTE).
  • the D-SON management function consumes the management service for NF provisioning with modifyMOIAttributes operation to configure the ranges of handover parameters.
  • the MnS of provisioning sets the ranges for MRO function (NOTE).
  • the D-SON management function consumes the management service for NF provisioning with modifyMOIAttributes operation to configure the MRO control parameters (e.g. Maximum deviation of Handover Trigger, Minimum time between Handover Trigger changes).
  • the MnS of provisioning sets the MRO control parameters for MRO function (NOTE).
  • the D-SON management function consumes the NF provisioning MnS with modifyMOIAttributes operation to enable the MRO function for a given NR cell if it is not enabled.
  • the provisioning MnS enables the MRO function (NOTE).
  • the MRO function receives MRO information reports from UE(s), and analyses them to determine the actions to optimize the MRO performance. If the performance does not meet the targets, it updates the handover parameters.
  • the MRO function indicates that MRO actions have been taken (NOTE).
  • the D-SON management function collects MRO related performance measurements.
  • the D-SON management function analyses the measurements to evaluate the MRO performance.
  • the D-SON management function performs one of the following actions when the MRO performance does not meet the
  • provisioning MnS and MRO function is not subject to standardization.
  • FIG. 6 depicts an illustrative schematic diagram for load balancing optimization, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 6 there is shown a PCI re-configuration procedure that describes how the PCI configuration function when detecting a PCI collision or confusion, re-configures the PCI of the cell based on the PCI list, and notifies the D-SON management consumer.
  • the PCI configuration (D-SON) function detects and corrects the PCI collision or PCI confusion problem for a NR cell.
  • the PCI configuration (D-SON) function indicates the attribute change to the Producer of provisioning MnS. (NOTE).
  • the interface between the Producer of provisioning MnS and PCI configuration (D-SON) function is not subject to standardization.
  • the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of FIGs. 8-10, or some other figure herein may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in FIG. 7.
  • the process may include, at 702, creating a D-EBO function Management Object Instance (MOI) to model the D-LBO function.
  • MOI D-EBO function Management Object Instance
  • the process further includes, at 704, sending a message to a provisioning management service (MnS) to modify attributes of the D-LBO function MOI to set one or more ranges associated with the D-LBO function.
  • MnS provisioning management service
  • the process further includes, at 706, identifying a response from the provisioning MnS indicating that the D-LBO function MOI has been modified.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • FIGs. 8-10 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • FIG. 8 illustrates an example network architecture 800 according to various embodiments.
  • the network 800 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
  • 3GPP technical specifications for LTE or 5G/NR systems 3GPP technical specifications for LTE or 5G/NR systems.
  • the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.
  • the network 800 includes a UE 802, which is any mobile or non-mobile computing device designed to communicate with a RAN 804 via an over-the-air connection.
  • the UE 802 is communicatively coupled with the RAN 804 by a Uu interface, which may be applicable to both LTE and NR systems.
  • Examples of the UE 802 include, but are not limited to, a smartphone, tablet computer, wearable computer, desktop computer, laptop computer, in- vehicle infotainment system, in-car entertainment system, instrument cluster, head-up display (HUD) device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, machine-to-machine (M2M), device-to-device (D2D), machine-type communication (MTC) device, Internet of Things (loT) device, and/or the like.
  • HUD head-up display
  • the network 800 may include a plurality of UEs 802 coupled directly with one another via a D2D, ProSe, PC5, and/or sidelink (SL) interface.
  • UEs 802 may be M2M/D2D/MTC/IoT devices and/or vehicular systems that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
  • the UE 802 may perform blind decoding attempts of SL channels/links according to the various embodiments herein.
  • the UE 802 may additionally communicate with an AP 806 via an over-the-air (OTA) connection.
  • the AP 806 manages a WLAN connection, which may serve to offload some/all network traffic from the RAN 804.
  • the connection between the UE 802 and the AP 806 may be consistent with any IEEE 802.11 protocol.
  • the UE 802, RAN 804, and AP 806 may utilize cellular- WLAN aggregation/integration (e.g., LWA/LWIP).
  • Cellular- WLAN aggregation may involve the UE 802 being configured by the RAN 804 to utilize both cellular radio resources and WLAN resources.
  • the RAN 804 includes one or more access network nodes (ANs) 808.
  • the ANs 808 terminate air-interface(s) for the UE 802 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and PHY/L1 protocols. In this manner, the AN 808 enables data/voice connectivity between CN 820 and the UE 802.
  • the ANs 808 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells; or some combination thereof.
  • an AN 808 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, etc.
  • One example implementation is a “CU/DU split” architecture where the ANs 808 are embodied as a gNB -Central Unit (CU) that is communicatively coupled with one or more gNB- Distributed Units (DUs), where each DU may be communicatively coupled with one or more Radio Units (RUs) (also referred to as RRHs, RRUs, or the like) (see e.g., 3GPP TS 38.401 vl6.1.0 (2020-03)).
  • RUs Radio Units
  • the one or more RUs may be individual RSUs.
  • the CU/DU split may include an ng-eNB-CU and one or more ng- eNB-DUs instead of, or in addition to, the gNB-CU and gNB-DUs, respectively.
  • the ANs 808 employed as the CU may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network including a virtual Base Band Unit (BBU) or BBU pool, cloud RAN (CRAN), Radio Equipment Controller (REC), Radio Cloud Center (RCC), centralized RAN (C-RAN), virtualized RAN (vRAN), and/or the like (although these terms may refer to different implementation concepts). Any other type of architectures, arrangements, and/or configurations can be used.
  • BBU Virtual Base Band Unit
  • CRAN cloud RAN
  • REC Radio Equipment Controller
  • RRCC Radio Cloud Center
  • C-RAN centralized RAN
  • vRAN virtualized RAN
  • the plurality of ANs may be coupled with one another via an X2 interface (if the RAN 804 is an LTE RAN or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 810) or an Xn interface (if the RAN 804 is a NG-RAN 814).
  • the X2/Xn interfaces which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
  • the ANs of the RAN 804 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 802 with an air interface for network access.
  • the UE 802 may be simultaneously connected with a plurality of cells provided by the same or different ANs 808 of the RAN 804.
  • the UE 802 and RAN 804 may use carrier aggregation to allow the UE 802 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell.
  • a first AN 808 may be a master node that provides an MCG and a second AN 808 may be secondary node that provides an SCG.
  • the first/second ANs 808 may be any combination of eNB, gNB, ng-eNB, etc.
  • the RAN 804 may provide the air interface over a licensed spectrum or an unlicensed spectrum.
  • the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells.
  • the nodes Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the UE 802 or AN 808 may be or act as a roadside unit (RSU), which may refer to any transportation infrastructure entity used for V2X communications.
  • RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE.
  • An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB -type RSU”; a gNB may be referred to as a “gNB -type RSU”; and the like.
  • an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs.
  • the RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
  • the RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services.
  • the components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
  • the RAN 804 may be an E-UTRAN 810 with one or more eNBs 812.
  • the an E-UTRAN 810 provides an LTE air interface (Uu) with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc.
  • the LTE air interface may rely on CSI- RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE.
  • the LTE air interface may operating on sub-6 GHz bands.
  • the RAN 804 may be an next generation (NG)-RAN 814 with one or more gNB 816 and/or on or more ng-eNB 818.
  • the gNB 816 connects with 5G-enabled UEs 802 using a 5G NR interface.
  • the gNB 816 connects with a 5GC 840 through an NG interface, which includes an N2 interface or an N3 interface.
  • the ng-eNB 818 also connects with the 5GC 840 through an NG interface, but may connect with a UE 802 via the Uu interface.
  • the gNB 816 and the ng-eNB 818 may connect with each other over an Xn interface.
  • the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 814 and a UPF 848 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN 814 and an AMF 844 (e.g., N2 interface).
  • NG-U NG user plane
  • N-C NG control plane
  • the NG-RAN 814 may provide a 5G-NR air interface (which may also be referred to as a Uu interface) with the following characteristics: variable SCS; CP-OFDM for DL, CP- OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data.
  • the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface.
  • the 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking.
  • the 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz.
  • the 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
  • the 5G-NR air interface may utilize BWPs for various purposes.
  • BWP can be used for dynamic adaptation of the SCS.
  • the UE 802 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 802, the SCS of the transmission is changed as well.
  • Another use case example of BWP is related to power saving.
  • multiple BWPs can be configured for the UE 802 with different amount of frequency resources (e.g., PRBs) to support data transmission under different traffic loading scenarios.
  • a BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 802 and in some cases at the gNB 816.
  • a BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
  • the RAN 804 is communicatively coupled to CN 820 that includes network elements and/or network functions (NFs) to provide various functions to support data and telecommunications services to customers/subscribers (e.g., UE 802).
  • the components of the CN 820 may be implemented in one physical node or separate physical nodes.
  • NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 820 onto physical compute/storage resources in servers, switches, etc.
  • a logical instantiation of the CN 820 may be referred to as a network slice, and a logical instantiation of a portion of the CN 820 may be referred to as a network sub-slice.
  • the CN 820 may be an LTE CN 822 (also referred to as an Evolved Packet Core (EPC) 822).
  • the EPC 822 may include MME 824, SGW 826, SGSN 828, HSS 830, PGW 832, and PCRF 834 coupled with one another over interfaces (or “reference points”) as shown.
  • the NFs in the EPC 822 are briefly introduced as follows.
  • the MME 824 implements mobility management functions to track a current location of the UE 802 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 826 terminates an SI interface toward the RAN 810 and routes data packets between the RAN 810 and the EPC 822.
  • the SGW 826 may be a local mobility anchor point for inter- RAN node handovers and also may provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the SGSN 828 tracks a location of the UE 802 and performs security functions and access control.
  • the SGSN 828 also performs inter- EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 824; MME 824 selection for handovers; etc.
  • the S3 reference point between the MME 824 and the SGSN 828 enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.
  • the HSS 830 includes a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
  • the HSS 830 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 830 and the MME 824 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the EPC 820.
  • the PGW 832 may terminate an SGi interface toward a data network (DN) 836 that may include an application (app)/content server 838.
  • the PGW 832 routes data packets between the EPC 822 and the data network 836.
  • the PGW 832 is communicatively coupled with the SGW 826 by an S5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 832 may further include a node for policy enforcement and charging data collection (e.g., PCEF).
  • the SGi reference point may communicatively couple the PGW 832 with the same or different data network 836.
  • the PGW 832 may be communicatively coupled with a PCRF 834 via a Gx reference point.
  • the PCRF 834 is the policy and charging control element of the EPC 822.
  • the PCRF 834 is communicatively coupled to the app/content server 838 to determine appropriate QoS and charging parameters for service flows.
  • the PCRF 832 also provisions associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
  • the CN 820 may be a 5GC 840 including an AUSF 842, AMF 844, SMF 846, UPF 848, NSSF 850, NEF 852, NRF 854, PCF 856, UDM 858, and AF 860 coupled with one another over various interfaces as shown.
  • the NFs in the 5GC 840 are briefly introduced as follows.
  • the AUSF 842 stores data for authentication of UE 802 and handle authentication- related functionality.
  • the AUSF 842 may facilitate a common authentication framework for various access types.
  • the AMF 844 allows other functions of the 5GC 840 to communicate with the UE 802 and the RAN 804 and to subscribe to notifications about mobility events with respect to the UE 802.
  • the AMF 844 is also responsible for registration management (e.g., for registering UE 802), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 844 provides transport for SM messages between the UE 802 and the SMF 846, and acts as a transparent pro7 for routing SM messages.
  • AMF 844 also provides transport for SMS messages between UE 802 and an SMSF.
  • AMF 844 interacts with the AUSF 842 and the UE 802 to perform various security anchor and context management functions.
  • AMF 844 is a termination point of a RAN-CP interface, which includes the N2 reference point between the RAN 804 and the AMF 844.
  • the AMF 844 is also a termination point of NAS (Nl) signaling, and performs NAS ciphering and integrity protection.
  • AMF 844 also supports NAS signaling with the UE 802 over an N3IWF interface.
  • the N3IWF provides access to untrusted entities.
  • N3IWF may be a termination point for the N2 interface between the (R)AN 804 and the AMF 844 for the control plane, and may be a termination point for the N3 reference point between the (R)AN 814 and the 848 for the user plane.
  • the AMF 844 handles N2 signalling from the SMF 846 and the AMF 844 for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunnelling, marks N3 user-plane packets in the uplink, and enforces QoS corresponding to N3 packet marking taking into account QoS requirements associated with such marking received over N2.
  • N3IWF may also relay UE and DE control-plane NAS signalling between the UE 802 and AMF 844 via an Nl reference point between the UE 802 and the AMF 844, and relay uplink and downlink user-plane packets between the UE 802 and UPF 848.
  • the N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 802.
  • the AMF 844 may exhibit an Namf servicebased interface, and may be a termination point for an N14 reference point between two AMFs 844 and an N17 reference point between the AMF 844 and a 5G-EIR (not shown by FIG. 8).
  • the SMF 846 is responsible for SM (e.g., session establishment, tunnel management between UPF 848 and AN 808); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 848 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to FI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 844 over N2 to AN 808; and determining SSC mode of a session.
  • SM refers to management of a PDU session
  • a PDU session or “session” refers to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 802 and the DN 836.
  • the UPF 848 acts as an anchor point for intra-RAT and inter- RAT mobility, an external PDU session point of interconnect to data network 836, and a branching point to support multihomed PDU session.
  • the UPF 848 also performs packet routing and forwarding, packet inspection, enforces user plane part of policy rules, lawfully intercept packets (UP collection), performs traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UE/DL rate enforcement), performs uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and performs downlink packet buffering and downlink data notification triggering.
  • UPF 848 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 850 selects a set of network slice instances serving the UE 802.
  • the NSSF 850 also determines allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed.
  • the NSSF 850 also determines an AMF set to be used to serve the UE 802, or a list of candidate AMFs 844 based on a suitable configuration and possibly by querying the NRF 854.
  • the selection of a set of network slice instances for the UE 802 may be triggered by the AMF 844 with which the UE 802 is registered by interacting with the NSSF 850; this may lead to a change of AMF 844.
  • the NSSF 850 interacts with the AMF 844 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown).
  • the NEF 852 securely exposes services and capabilities provided by 3GPP NFs for third party, internal exposure/re-exposure, AFs 860, edge computing or fog computing systems (e.g., edge compute node, etc.
  • the NEF 852 may authenticate, authorize, or throttle the AFs.
  • NEF 852 may also translate information exchanged with the AF 860 and information exchanged with internal network functions. For example, the NEF 852 may translate between an AF-Service-Identifier and an internal 5GC information.
  • NEF 852 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 852 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 852 to other NFs and AFs, or used for other purposes such as analytics.
  • the NRF 854 supports service discovery functions, receives NF discovery requests from NF instances, and provides information of the discovered NF instances to the requesting NF instances. NRF 854 also maintains information of available NF instances and their supported services. The NRF 854 also supports service discovery functions, wherein the NRF 854 receives NF Discovery Request from NF instance or an SCP (not shown), and provides information of the discovered NF instances to the NF instance or SCP.
  • the PCF 856 provides policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior.
  • the PCF 856 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 858.
  • the PCF 856 exhibit an Npcf service-based interface.
  • the UDM 858 handles subscription-related information to support the network entities’ handling of communication sessions, and stores subscription data of UE 802. For example, subscription data may be communicated via an N8 reference point between the UDM 858 and the AMF 844.
  • the UDM 858 may include two parts, an application front end and a UDR.
  • the UDR may store subscription data and policy data for the UDM 858 and the PCF 856, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 802) for the NEF 852.
  • the Nudr servicebased interface may be exhibited by the UDR 221 to allow the UDM 858, PCF 856, and NEF 852 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR.
  • the UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
  • the UDM 858 may exhibit the Nudm service-based interface.
  • AF 860 provides application influence on traffic routing, provide access to NEF 852, and interact with the policy framework for policy control.
  • the AF 860 may influence UPF 848 (re)selection and traffic routing. Based on operator deployment, when AF 860 is considered to be a trusted entity, the network operator may permit AF 860 to interact directly with relevant NFs. Additionally, the AF 860 may be used for edge computing implementations,
  • the 5GC 840 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 802 is attached to the network. This may reduce latency and load on the network.
  • the 5GC 840 may select a UPF 848 close to the UE 802 and execute traffic steering from the UPF 848 to DN 836 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 860, which allows the AF 860 to influence UPF (re)selection and traffic routing.
  • the data network (DN) 836 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application (app)/content server 838.
  • the DN 836 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services.
  • the app server 838 can be coupled to an IMS via an S-CSCF or the I-CSCF.
  • the DN 836 may represent one or more local area DNs (LADNs), which are DNs 836 (or DN names (DNNs)) that is/are accessible by a UE 802 in one or more specific areas. Outside of these specific areas, the UE 802 is not able to access the LADN/DN 836.
  • LADNs local area DNs
  • DNNs DN names
  • the DN 836 may be an Edge DN 836, which is a (local) Data Network that supports the architecture for enabling edge applications.
  • the app server 838 may represent the physical hardware systems/devices providing app server functionality and/or the application software resident in the cloud or at an edge compute node that performs server function(s).
  • the app/content server 838 provides an edge hosting environment that provides support required for Edge Application Server’s execution.
  • the 5GS can use one or more edge compute nodes to provide an interface and offload processing of wireless communication traffic.
  • the edge compute nodes may be included in, or co-located with one or more RAN810, 814.
  • the edge compute nodes can provide a connection between the RAN 814 and UPF 848 in the 5GC 840.
  • the edge compute nodes can use one or more NFV instances instantiated on virtualization infrastructure within the edge compute nodes to process wireless connections to and from the RAN 814 and UPF 848.
  • the interfaces of the 5GC 840 include reference points and service-based itnterfaces.
  • the reference points include: N1 (between the UE 802 and the AMF 844), N2 (between RAN 814 and AMF 844), N3 (between RAN 814 and UPF 848), N4 (between the SMF 846 and UPF 848), N5 (between PCF 856 and AF 860), N6 (between UPF 848 and DN 836), N7 (between SMF 846 and PCF 856), N8 (between UDM 858 and AMF 844), N9 (between two UPFs 848), N10 (between the UDM 858 and the SMF 846), Nil (between the AMF 844 and the SMF 846), N12 (between AUSF 842 and AMF 844), N13 (between AUSF 842 and UDM 858), N14 (between two AMFs 844; not shown), N15 (between PCF 856 and AMF 844 in case of a nonroaming
  • the service-based representation of FIG. 8 represents NFs within the control plane that enable other authorized NFs to access their services.
  • the service-based interfaces include: Namf (SBI exhibited by AMF 844), Nsmf (SBI exhibited by SMF 846), Nnef (SBI exhibited by NEF 852), Npcf (SBI exhibited by PCF 856), Nudm (SBI exhibited by the UDM 858), Naf (SBI exhibited by AF 860), Nnrf (SBI exhibited by NRF 854), Nnssf (SBI exhibited by NSSF 850), Nausf (SBI exhibited by AUSF 842).
  • NEF 852 can provide an interface to edge compute nodes 836x, which can be used to process wireless connections with the RAN 814.
  • the system 800 may include an SMSF, which is responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE 802 to/from other entities, such as an SMS-GMSC/IWMSC/SMS-router.
  • the SMS may also interact with AMF 842 and UDM 858 for a notification procedure that the UE 802 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 858 when UE 802 is available for SMS).
  • the 5GS may also include an SCP (or individual instances of the SCP) that supports indirect communication (see e.g., 3GPP TS 23.501 section 7.1.1); delegated discovery (see e.g., 3GPP TS 23.501 section 7.1.1); message forwarding and routing to destination NF/NF service(s), communication security (e.g., authorization of the NF Service Consumer to access the NF Service Producer API) (see e.g., 3GPP TS 33.501), load balancing, monitoring, overload control, etc.; and discovery and selection functionality for UDM(s), AUSF(s), UDR(s), PCF(s) with access to subscription data stored in the UDR based on UE's SUPI, SUCI or GPSI (see e.g., 3GPP TS 23.501 section 6.3).
  • SCP or individual instances of the SCP
  • indirect communication see e.g., 3GPP TS 23.501 section 7.1.1
  • delegated discovery see e.g.,
  • Load balancing, monitoring, overload control functionality provided by the SCP may be implementation specific.
  • the SCP may be deployed in a distributed manner. More than one SCP can be present in the communication path between various NF Services.
  • the SCP although not an NF instance, can also be deployed distributed, redundant, and scalable.
  • FIG. 9 schematically illustrates a wireless network 900 in accordance with various embodiments.
  • the wireless network 900 may include a UE 902 in wireless communication with an AN 904.
  • the UE 902 and AN 904 may be similar to, and substantially interchangeable with, like-named components described with respect to FIG. 8.
  • the UE 902 may be communicatively coupled with the AN 904 via connection 906.
  • the connection 906 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.
  • the UE 902 may include a host platform 908 coupled with a modem platform 910.
  • the host platform 908 may include application processing circuitry 912, which may be coupled with protocol processing circuitry 914 of the modem platform 910.
  • the application processing circuitry 912 may run various applications for the UE 902 that source/sink application data.
  • the application processing circuitry 912 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
  • the protocol processing circuitry 914 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 906.
  • the layer operations implemented by the protocol processing circuitry 914 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
  • the modem platform 910 may further include digital baseband circuitry 916 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 914 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ acknowledgement (ACK) functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.
  • PHY operations including one or more of HARQ acknowledgement (ACK) functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding
  • the modem platform 910 may further include transmit circuitry 918, receive circuitry 920, RF circuitry 922, and RF front end (RFFE) 924, which may include or connect to one or more antenna panels 926.
  • the transmit circuitry 918 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive circuitry 920 may include an analog-to-digital converter, mixer, IF components, etc.
  • the RF circuitry 922 may include a low- noise amplifier, a power amplifier, power tracking components, etc.
  • RFFE 924 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
  • transmit/receive components may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc.
  • the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
  • the protocol processing circuitry 914 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
  • a UE 902 reception may be established by and via the antenna panels 926, RFFE 924, RF circuitry 922, receive circuitry 920, digital baseband circuitry 916, and protocol processing circuitry 914.
  • the antenna panels 926 may receive a transmission from the AN 904 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 926.
  • a UE 902 transmission may be established by and via the protocol processing circuitry 914, digital baseband circuitry 916, transmit circuitry 918, RF circuitry 922, RFFE 924, and antenna panels 926.
  • the transmit components of the UE 904 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 926.
  • the AN 904 may include a host platform 928 coupled with a modem platform 930.
  • the host platform 928 may include application processing circuitry 932 coupled with protocol processing circuitry 934 of the modem platform 930.
  • the modem platform may further include digital baseband circuitry 936, transmit circuitry 938, receive circuitry 940, RF circuitry 942, RFFE circuitry 944, and antenna panels 946.
  • the components of the AN 904 may be similar to and substantially interchangeable with like-named components of the UE 902.
  • the components of the AN 908 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
  • FIG. 10 illustrates components of a computing device 1000 according to some example embodiments, able to read instructions from a machine -readable or computer-readable medium (e.g., a non- transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • FIG. 10 shows a diagrammatic representation of hardware resources 1000 including one or more processors (or processor cores) 1010, one or more memory/storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040 or other interface circuitry.
  • a hypervisor 1002 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1000.
  • the processors 1010 include, for example, processor 1012 and processor 1014.
  • the processors 1010 include circuitry such as, but not limited to one or more processor cores and one or more of cache memory, low drop-out voltage regulators (EDOs), interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface circuit, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose I/O, memory card controllers such as secure digital/multi-media card (SD/MMC) or similar, interfaces, mobile industry processor interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports.
  • SD/MMC secure digital/multi-media card
  • MIPI mobile industry processor interface
  • JTAG Joint Test Access Group
  • the processors 1010 may be, for example, a central processing unit (CPU), reduced instruction set computing (RISC) processors, Acorn RISC Machine (ARM) processors, complex instruction set computing (CISC) processors, graphics processing units (GPUs), one or more Digital Signal Processors (DSPs) such as a baseband processor, Application-Specific Integrated Circuits (ASICs), an Field-Programmable Gate Array (FPGA), a radio-frequency integrated circuit (RFIC), one or more microprocessors or controllers, another processor (including those discussed herein), or any suitable combination thereof.
  • the processor circuitry 1010 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices (e.g., FPGA, complex programmable logic devices (CPUDs), etc.), or the like.
  • the memory/storage devices 1020 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 1020 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as random access memory (RAM), dynamic RAM (DRAM), static RAM (SRAM), synchronous DRAM (SDRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, phase change RAM (PRAM), resistive memory such as magnetoresistive random access memory (MRAM), etc., and may incorporate three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.
  • the memory/storage devices 1020 may also comprise persistent storage devices, which may be temporal and/or persistent storage of any type, including, but not limited to, non-volatile memory, optical, magnetic, and/or solid state mass storage, and so forth.
  • the communication resources 1030 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1004 or one or more databases 1006 or other network elements via a network 1008.
  • the communication resources 1030 may include wired communication components (e.g., for coupling via USB, Ethernet, Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), Ethernet over USB, Controller Area Network (CAN), Local Interconnect Network (LIN), DeviceNet, ControlNet, Data Highway-i-, PROFIBUS, or PROFINET, among many others), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, WiFi® components, and other communication components.
  • wired communication components e.g., for coupling via USB, Ethernet, Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), Ethernet over USB, Controller Area Network (CAN), Local Interconnect Network (LIN), DeviceNet, ControlNet, Data Highway-i-, PROFIBUS, or PROFINET, among many others
  • Network connectivity may be provided to/from the computing device 1000 via the communication resources 1030 using a physical connection, which may be electrical (e.g., a “copper interconnect”) or optical.
  • the physical connection also includes suitable input connectors (e.g., ports, receptacles, sockets, etc.) and output connectors (e.g., plugs, pins, etc.).
  • the communication resources 1030 may include one or more dedicated processors and/or FPGAs to communicate using one or more of the aforementioned network interface protocols.
  • Instructions 1050 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1010 to perform any one or more of the methodologies discussed herein.
  • the instructions 1050 may reside, completely or partially, within at least one of the processors 1010 (e.g., within the processor’s cache memory), the memory/storage devices 1020, or any suitable combination thereof.
  • any portion of the instructions 1050 may be transferred to the hardware resources 1000 from any combination of the peripheral devices 1004 or the databases 1006. Accordingly, the memory of processors 1010, the memory/storage devices 1020, the peripheral devices 1004, and the databases 1006 are examples of computer-readable and machine-readable media.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • Example 1 may include a device comprising processing circuitry coupled to storage, the processing circuitry configured to: create a D-LBO function using a D-LBO function management object instance; cause to send a message to a prosvisioning management service (MnS) to modify attributes of the distributed load-balancing optimization function to set one or more ranges associated with the distributed load-balancing optimization function; and identify a response from the provisioning MnS indicating that the D-LBO function has been modified.
  • MnS prosvisioning management service
  • Example 2 may include the device of example 1 and/or some other example herein, wherein the D-LBO function may be associated with configuring attributes of ranges of handover (HO) or reselection parameters.
  • Example 3 may include the device of example 2 and/or some other example herein, wherein the ranges of HO or reselection parameters include a maximum deviation of handover trigger attribute or a minimum time between handover trigger changes attribute.
  • Example 4 may include the device of example 1 and/or some other example herein, wherein the processing circuitry may be further configured to collect LBO performance related measurements from a producer of performance assurance MnS.
  • Example 5 may include the device of example 1 and/or some other example herein, wherein the D-SON management function configures the following attributes to enable or disable the D-LBO function.
  • Example 6 may include the device of example 1 and/or some other example herein, wherein the D-SON management function configures a DLBOControl attribute to enable or disable the D-LBO function.
  • Example 7 may include the device of example 1 and/or some other example herein, wherein the D-LBO function management object instance may be created based on a D-LBO function information object class (IOC).
  • IOC D-LBO function information object class
  • Example 8 may include the device of example 1 and/or some other example herein, wherein the maximum deviation of handover trigger attribute defines a maximum allowed absolute deviation of a Handover Trigger from a default point of operation.
  • Example 9 may include the device of example 1 and/or some other example herein, wherein the minimum time between handover trigger changes attribute defines a minimum allowed time interval between two Handover Trigger change performed by Mobility Robustness Optimisation (MRO).
  • MRO Mobility Robustness Optimisation
  • Example 10 may include a non-transitory computer-readable medium storing computer-executable instructions which when executed by one or more processors result in performing operations comprising: creating a D-LBO function using a D-LBO function management object instance; causing to send a message to a prosvisioning management service (MnS) to modify attributes of the distributed load-balancing optimization function to set one or more ranges associated with the distributed load-balancing optimization function; and identifying a response from the provisioning MnS indicating that the D-LBO function has been modified.
  • MnS prosvisioning management service
  • Example 11 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the D-LBO function may be associated with configuring attributes of ranges of handover (HO) or reselection parameters.
  • Example 12 may include the non-transitory computer-readable medium of example 11 and/or some other example herein, wherein the ranges of HO or reselection parameters include a maximum deviation of handover trigger attribute or a minimum time between handover trigger changes attribute.
  • Example 13 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the operations further comprise collect LBO performance related measurements from a producer of performance assurance MnS.
  • Example 14 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the D-SON management function configures the following attributes to enable or disable the D-LBO function.
  • Example 15 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the D-SON management function configures a DLBOControl attribute to enable or disable the D-LBO function.
  • Example 16 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the D-LBO function management object instance may be created based on a D-LBO function information object class (IOC).
  • IOC D-LBO function information object class
  • Example 17 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the maximum deviation of handover trigger attribute defines a maximum allowed absolute deviation of a Handover Trigger from a default point of operation.
  • Example 18 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the minimum time between handover trigger changes attribute defines a minimum allowed time interval between two Handover Trigger change performed by Mobility Robustness Optimisation (MRO).
  • MRO Mobility Robustness Optimisation
  • Example 19 may include a method comprising: creating a D-LBO function using a D- LBO function management object instance; causing to send a message to a prosvisioning management service (MnS) to modify attributes of the distributed load-balancing optimization function to set one or more ranges associated with the distributed load-balancing optimization function; and identifying a response from the provisioning MnS indicating that the D-LBO function has been modified.
  • MnS prosvisioning management service
  • Example 20 may include the method of example 19 and/or some other example herein, wherein the D-LBO function may be associated with configuring attributes of ranges of handover (HO) or reselection parameters.
  • Example 21 may include the method of example 20 and/or some other example herein, wherein the ranges of HO or reselection parameters include a maximum deviation of handover trigger attribute or a minimum time between handover trigger changes attribute.
  • Example 22 may include the method of example 19 and/or some other example herein, further comprising collect LBO performance related measurements from a producer of performance assurance MnS.
  • Example 23 may include the method of example 19 and/or some other example herein, wherein the D-SON management function configures the following attributes to enable or disable the D-LBO function.
  • Example 24 may include the method of example 19 and/or some other example herein, wherein the D-SON management function configures a DLBOControl attribute to enable or disable the D-LBO function.
  • Example 25 may include the method of example 19 and/or some other example herein, wherein the D-LBO function management object instance may be created based on a D-LBO function information object class (IOC).
  • IOC D-LBO function information object class
  • Example 26 may include the method of example 19 and/or some other example herein, wherein the maximum deviation of handover trigger attribute defines a maximum allowed absolute deviation of a Handover Trigger from a default point of operation.
  • Example 27 may include the method of example 19 and/or some other example herein, wherein the minimum time between handover trigger changes attribute defines a minimum allowed time interval between two Handover Trigger change performed by Mobility Robustness Optimisation (MRO).
  • MRO Mobility Robustness Optimisation
  • Example 28 may include an apparatus comprising means for: creating a D-LBO function using a D-LBO function management object instance; causing to send a message to a prosvisioning management service (MnS) to modify attributes of the distributed load-balancing optimization function to set one or more ranges associated with the distributed load-balancing optimization function; and identifying a response from the provisioning MnS indicating that the D-LBO function has been modified.
  • MnS prosvisioning management service
  • Example 29 may include the apparatus of example 28 and/or some other example herein, wherein the D-LBO function may be associated with configuring attributes of ranges of handover (HO) or reselection parameters.
  • HO handover
  • Example 30 may include the apparatus of example 29 and/or some other example herein, wherein the ranges of HO or reselection parameters include a maximum deviation of handover trigger attribute or a minimum time between handover trigger changes attribute.
  • Example 31 may include the apparatus of example 28 and/or some other example herein, further comprising collect LBO performance related measurements from a producer of performance assurance MnS.
  • Example 32 may include the apparatus of example 28 and/or some other example herein, wherein the D-SON management function configures the following attributes to enable or disable the D-LBO function.
  • Example 33 may include the apparatus of example 28 and/or some other example herein, wherein the D-SON management function configures a DLBOControl attribute to enable or disable the D-LBO function.
  • Example 34 may include the apparatus of example 28 and/or some other example herein, wherein the D-LBO function management object instance may be created based on a D-LBO function information object class (IOC).
  • IOC D-LBO function information object class
  • Example 35 may include the apparatus of example 28 and/or some other example herein, wherein the maximum deviation of handover trigger attribute defines a maximum allowed absolute deviation of a Handover Trigger from a default point of operation.
  • Example 36 may include the apparatus of example 28 and/or some other example herein, wherein the minimum time between handover trigger changes attribute defines a minimum allowed time interval between two Handover Trigger change performed by Mobility Robustness Optimisation (MRO).
  • MRO Mobility Robustness Optimisation
  • Example 37 may include an apparatus comprising means for performing any of the methods of examples 1-36.
  • Example 38 may include a network node comprising a communication interface and processing circuitry connected thereto and configured to perform the methods of examples 1- 36.
  • Example 39 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-36, or any other method or process described herein.
  • Example 40 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-36, or any other method or process described herein.
  • Example 41 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-36, or any other method or process described herein.
  • Example 42 may include a method, technique, or process as described in or related to any of examples 1-36, or portions or parts thereof.
  • Example 43 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-36, or portions thereof.
  • Example 44 may include a signal as described in or related to any of examples 1-36, or portions or parts thereof.
  • Example 45 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-36, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example 46 may include a signal encoded with data as described in or related to any of examples 1-36, or portions or parts thereof, or otherwise described in the present disclosure.
  • Example 47 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-36, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example 48 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-36, or portions thereof.
  • Example 49 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-36, or portions thereof.
  • Example 50 may include a signal in a wireless network as shown and described herein.
  • Example 51 may include a method of communicating in a wireless network as shown and described herein.
  • Example 52 may include a system for providing wireless communication as shown and described herein.
  • Example 53 may include a device for providing wireless communication as shown and described herein.
  • An example implementation is an edge computing system, including respective edge processing devices and nodes to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is a client endpoint node, operable to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an aggregation node, network hub node, gateway node, or core data processing node, within or coupled to an edge computing system, operable to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an access point, base station, road-side unit, street-side unit, or on-premise unit, within or coupled to an edge computing system, operable to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an edge provisioning node, service orchestration node, application orchestration node, or multi-tenant management node, within or coupled to an edge computing system, operable to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an edge node operating an edge provisioning service, application or service orchestration service, virtual machine deployment, container deployment, function deployment, and compute management, within or coupled to an edge computing system, operable to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an edge computing system operable as an edge mesh, as an edge mesh with side car loading, or with mesh-to-mesh communications, operable to invoke or perform the operations of the examples above, or other subject matter described herein.
  • Another example implementation is an edge computing system including aspects of network functions, acceleration functions, acceleration hardware, storage hardware, or computation hardware resources, operable to invoke or perform the use cases discussed herein, with use of the examples above, or other subject matter described herein.
  • Another example implementation is an edge computing system adapted for supporting client mobility, vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), or vehicle-to-infrastructure (V2I) scenarios, and optionally operating according to ETSI MEC specifications, operable to invoke or perform the use cases discussed herein, with use of the examples above, or other subject matter described herein.
  • V2V vehicle-to-vehicle
  • V2X vehicle-to-everything
  • V2I vehicle-to-infrastructure
  • Another example implementation is an edge computing system adapted for mobile wireless communications, including configurations according to an 3GPP 4G/LTE or 5G network capabilities, operable to invoke or perform the use cases discussed herein, with use of the examples above, or other subject matter described herein.
  • Another example implementation is a computing system adapted for network communications, including configurations according to an O-RAN capabilities, operable to invoke or perform the use cases discussed herein, with use of the examples above, or other subject matter described
  • the phrase “A and/or B” means (A), (B), or (A and B).
  • the phrase “A, B, and/or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C).
  • the description may use the phrases “in an embodiment,” or “In some embodiments,” which may each refer to one or more of the same or different embodiments.
  • the terms “comprising,” “including,” “having,” and the like, as used with respect to embodiments of the present disclosure are synonymous.
  • Coupled may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other.
  • directly coupled may mean that two or more elements are in direct contact with one another.
  • communicatively coupled may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or ink, and/or the like.
  • circuitry refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality.
  • FPD field-programmable device
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • CPLD complex PLD
  • HPLD high-capacity PLD
  • DSPs digital signal processors
  • the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality.
  • the term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
  • processor circuitry refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data.
  • Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information.
  • processor circuitry may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes.
  • Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like.
  • the one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators.
  • CV computer vision
  • DL deep learning
  • application circuitry and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”
  • memory and/or “memory circuitry” as used herein refers to one or more hardware devices for storing data, including RAM, MRAM, PRAM, DRAM, and/or SDRAM, core memory, ROM, magnetic disk storage mediums, optical storage mediums, flash memory devices or other machine readable mediums for storing data.
  • computer-readable medium may include, but is not limited to, memory, portable or fixed storage devices, optical storage devices, and various other mediums capable of storing, containing or carrying instructions or data.
  • interface circuitry refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices.
  • interface circuitry may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.
  • user equipment refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network.
  • the term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc.
  • the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
  • network element refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services.
  • network element may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.
  • computer system refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.
  • appliance refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource.
  • a “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.
  • element refers to a unit that is indivisible at a given level of abstraction and has a clearly defined boundary, wherein an element may be any type of entity including, for example, one or more devices, systems, controllers, network elements, modules, etc., or combinations thereof.
  • device refers to a physical entity embedded inside, or attached to, another physical entity in its vicinity, with capabilities to convey digital information from or to that physical entity.
  • entity refers to a distinct component of an architecture or device, or information transferred as a payload.
  • controller refers to an element or entity that has the capability to affect a physical entity, such as by changing its state or causing the physical entity to move.
  • cloud computing refers to a paradigm for enabling network access to a scalable and elastic pool of shareable computing resources with self-service provisioning and administration on-demand and without active management by users.
  • Cloud computing provides cloud computing services (or cloud services), which are one or more capabilities offered via cloud computing that are invoked using a defined interface (e.g., an API or the like).
  • computing resource or simply “resource” refers to any physical or virtual component, or usage of such components, of limited availability within a computer system or network.
  • Examples of computing resources include usage/access to, for a period of time, servers, processor(s), storage equipment, memory devices, memory areas, networks, electrical power, input/output (peripheral) devices, mechanical devices, network connections (e.g., channels/links, ports, network sockets, etc.), operating systems, virtual machines (VMs), software/applications, computer files, and/or the like.
  • a “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s).
  • a “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc.
  • the term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network.
  • system resources may refer to any kind of shared entities to provide services, and may include computing and/or network resources.
  • System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
  • cloud service provider or CSP indicates an organization which operates typically large-scale “cloud” resources comprised of centralized, regional, and edge data centers (e.g., as used in the context of the public cloud).
  • a CSP may also be referred to as a Cloud Service Operator (CSO).
  • CSO Cloud Service Operator
  • references to “cloud computing” generally refer to computing resources and services offered by a CSP or a CSO, at remote locations with at least some increased latency, distance, or constraints relative to edge computing.
  • the term “data center” refers to a purpose-designed structure that is intended to house multiple high-performance compute and data storage nodes such that a large amount of compute, data storage and network resources are present at a single location. This often entails specialized rack and enclosure systems, suitable heating, cooling, ventilation, security, fire suppression, and power delivery systems.
  • the term may also refer to a compute and data storage node in some contexts.
  • a data center may vary in scale between a centralized or cloud data center (e.g., largest), regional data center, and edge data center (e.g., smallest).
  • edge computing refers to the implementation, coordination, and use of computing and resources at locations closer to the “edge” or collection of “edges” of a network. Deploying computing resources at the network’ s edge may reduce application and network latency, reduce network backhaul traffic and associated energy consumption, improve service capabilities, improve compliance with security or data privacy requirements (especially as compared to conventional cloud computing), and improve total cost of ownership).
  • edge compute node refers to a real-world, logical, or virtualized implementation of a compute-capable element in the form of a device, gateway, bridge, system or subsystem, component, whether operating in a server, client, endpoint, or peer mode, and whether located at an “edge” of an network or at a connected location further within the network.
  • references to a “node” used herein are generally interchangeable with a “device”, “component”, and “sub-system”; however, references to an “edge computing system” or “edge computing network” generally refer to a distributed architecture, organization, or collection of multiple nodes and devices, and which is organized to accomplish or offer some aspect of services or resources in an edge computing setting.
  • the term “Edge Computing” refers to a concept, as described in [6], that enables operator and 3rd party services to be hosted close to the UE's access point of attachment, to achieve an efficient service delivery through the reduced end-to- end latency and load on the transport network.
  • the term “Edge Computing Service Provider” refers to a mobile network operator or a 3rd party service provider offering Edge Computing service.
  • the term “Edge Data Network” refers to a local Data Network (DN) that supports the architecture for enabling edge applications.
  • the term “Edge Hosting Environment” refers to an environment providing support required for Edge Application Server's execution.
  • the term “Application Server” refers to application software resident in the cloud performing the server function.
  • loT Internet of Things
  • loT devices are usually low-power devices without heavy compute or storage capabilities.
  • “Edge loT devices” may be any kind of loT devices deployed at a network’s edge.
  • cluster refers to a set or grouping of entities as part of an edge computing system (or systems), in the form of physical entities (e.g., different computing systems, networks or network groups), logical entities (e.g., applications, functions, security constructs, containers), and the like.
  • a “cluster” is also referred to as a “group” or a “domain”.
  • the membership of cluster may be modified or affected based on conditions or functions, including from dynamic or property-based membership, from network or system management scenarios, or from various example techniques discussed below which may add, modify, or remove an entity in a cluster.
  • Clusters may also include or be associated with multiple layers, levels, or properties, including variations in security features and results based on such layers, levels, or properties.
  • the term “application” may refer to a complete and deployable package, environment to achieve a certain function in an operational environment.
  • AI/ML application or the like may be an application that contains some AI/ML models and application-level descriptions.
  • machine learning or “ML” refers to the use of computer systems implementing algorithms and/or statistical models to perform specific task(s) without using explicit instructions, but instead relying on patterns and inferences.
  • ML algorithms build or estimate mathematical model(s) (referred to as “ML models” or the like) based on sample data (referred to as “training data,” “model training information,” or the like) in order to make predictions or decisions without being explicitly programmed to perform such tasks.
  • an ML algorithm is a computer program that learns from experience with respect to some task and some performance measure
  • an ML model may be any object or data structure created after an ML algorithm is trained with one or more training datasets. After training, an ML model may be used to make predictions on new datasets.
  • ML algorithm refers to different concepts than the term “ML model,” these terms as discussed herein may be used interchangeably for the purposes of the present disclosure.
  • machine learning model may also refer to ML methods and concepts used by an ML-assisted solution.
  • An “ML-assisted solution” is a solution that addresses a specific use case using ML algorithms during operation.
  • ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.) unsupervised learning (e.g., K-means clustering, principle component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), neural networks, and the like.
  • An “ML pipeline” is a set of functionalities, functions, or functional entities specific for an ML-assisted solution; an ML pipeline may include one or several data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and an actor.
  • the “actor” is an entity that hosts an ML assisted solution using the output of the ML model inference).
  • ML training host refers to an entity, such as a network function, that hosts the training of the model.
  • ML inference host refers to an entity, such as a network function, that hosts model during inference mode (which includes both the model execution as well as any online learning if applicable).
  • the ML-host informs the actor about the output of the ML algorithm, and the actor takes a decision for an action (an “action” is performed by an actor as a result of the output of an ML assisted solution).
  • model inference information refers to information used as an input to the ML model for determining inference(s); the data used to train an ML model and the data used to determine inferences may overlap, however, “training data” and “inference data” refer to different concepts.
  • instantiate refers to the creation of an instance.
  • An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
  • information element refers to a structural element containing one or more fields.
  • field refers to individual contents of an information element, or a data element that contains content.
  • a “database object”, “data structure”, or the like may refer to any representation of information that is in the form of an object, attribute-value pair (A VP), key-value pair (KVP), tuple, etc., and may include variables, data structures, functions, methods, classes, database records, database fields, database entities, associations between data and/or database entities (also referred to as a “relation”), blocks and links between blocks in block chain implementations, and/or the like.
  • An “information object,” as used herein, refers to a collection of structured data and/or any representation of information, and may include, for example electronic documents (or “documents”), database objects, data structures, files, audio data, video data, raw data, archive files, application packages, and/or any other like representation of information.
  • electronic document or “document,” may refer to a data structure, computer file, or resource used to record data, and includes various file types and/or data formats such as word processing documents, spreadsheets, slide presentations, multimedia items, webpage and/or source code documents, and/or the like.
  • the information objects may include markup and/or source code documents such as HTML, XML, JSON, Apex®, CSS, JSP, MessagePackTM, Apache® ThriftTM, ASN.l, Google® Protocol Buffers (protobuf), or some other document(s)/format(s) such as those discussed herein.
  • An information object may have both a logical and a physical structure. Physically, an information object comprises one or more units called entities. An entity is a unit of storage that contains content and is identified by a name. An entity may refer to other entities to cause their inclusion in the information object. An information object begins in a document entity, which is also referred to as a root element (or "root"). Logically, an information object comprises one or more declarations, elements, comments, character references, and processing instructions, all of which are indicated in the information object (e.g., using markup).
  • data item refers to an atomic state of a particular object with at least one specific property at a certain point in time.
  • Such an object is usually identified by an object name or object identifier, and properties of such an object are usually defined as database objects (e.g., fields, records, etc.), object instances, or data elements (e.g., mark-up language elements/tags, etc.).
  • database objects e.g., fields, records, etc.
  • object instances e.g., mark-up language elements/tags, etc.
  • data elements e.g., mark-up language elements/tags, etc.
  • data item may refer to data elements and/or content items, although these terms may refer to difference concepts.
  • data element or “element” as used herein refers to a unit that is indivisible at a given level of abstraction and has a clearly defined boundary.
  • a data element is a logical component of an information object (e.g., electronic document) that may begin with a start tag (e.g., “ ⁇ element>”) and end with a matching end tag (e.g., “ ⁇ /element>”), or only has an empty element tag (e.g., “ ⁇ element />”). Any characters between the start tag and end tag, if any, are the element’s content (referred to herein as “content items” or the like).
  • the content of an entity may include one or more content items, each of which has an associated datatype representation.
  • a content item may include, for example, attribute values, character values, URIs, qualified names (qnames), parameters, and the like.
  • a qname is a fully qualified name of an element, attribute, or identifier in an information object.
  • a qname associates a URI of a namespace with a local name of an element, attribute, or identifier in that namespace. To make this association, the qname assigns a prefix to the local name that corresponds to its namespace.
  • the qname comprises a URI of the namespace, the prefix, and the local name. Namespaces are used to provide uniquely named elements and attributes in information objects.
  • child elements e.g., “ ⁇ elementlxelement2>content item ⁇ /element2x/elementl>”.
  • An “attribute” may refer to a markup construct including a name-value pair that exists within a start tag or empty element tag. Attributes contain data related to its element and/or control the element’s behavior.
  • channel refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream.
  • channel may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated.
  • link refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.
  • radio technology refers to technology for wireless transmission and/or reception of electromagnetic radiation for information transfer.
  • radio access technology refers to the technology used for the underlying physical connection to a radio based communication network.
  • communication protocol refers to a set of standardized rules or instructions implemented by a communication device and/or system to communicate with other devices and/or systems, including instructions for packetizing/depacketizing data, modulating/demodulating signals, implementation of protocols stacks, and/or the like.
  • radio technology refers to technology for wireless transmission and/or reception of electromagnetic radiation for information transfer.
  • radio access technology or “RAT” refers to the technology used for the underlying physical connection to a radio based communication network.
  • communication protocol (either wired or wireless) refers to a set of standardized rules or instructions implemented by a communication device and/or system to communicate with other devices and/or systems, including instructions for packetizing/depacketizing data, modulating/demodulating signals, implementation of protocols stacks, and/or the like.
  • Examples of wireless communications protocols may be used in various embodiments include a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3GPP) radio communication technology including, for example, 3GPP Fifth Generation (5G) or New Radio (NR), Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), Long Term Evolution (LTE), LTE- Advanced (LTE Advanced), LTE Extra, LTE-A Pro, cdmaOne (2G), Code Division Multiple Access 2000 (CDMA 2000), Cellular Digital Packet Data (CDPD), Mobitex, Circuit Switched Data (CSD), High-Speed CSD (HSCSD), Universal Mobile Telecommunications System (UMTS), Wideband Code Division Multiple Access (W-CDM), High Speed Packet Access (HSPA), HSPA Plus (HSPA+), Time Division-Code Division Multiple Access (TD-CDMA), Time Division-Sy
  • any number of satellite uplink technologies may be used for purposes of the present disclosure including, for example, radios compliant with standards issued by the International Telecommunication Union (ITU), or the European Telecommunications Standards Institute (ETSI), among others.
  • ITU International Telecommunication Union
  • ETSI European Telecommunications Standards Institute
  • the examples provided herein are thus understood as being applicable to various other communication technologies, both existing and not yet formulated.
  • access network refers to any network, using any combination of radio technologies, RATs, and/or communication protocols, used to connect user devices and service providers.
  • an “access network” is an IEEE 802 local area network (LAN) or metropolitan area network (MAN) between terminals and access routers connecting to provider services.
  • LAN local area network
  • MAN metropolitan area network
  • access router refers to router that terminates a medium access control (MAC) service from terminals and forwards user traffic to information servers according to Internet Protocol (IP) addresses.
  • MAC medium access control
  • SMTC refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.
  • SSB refers to a synchronization signal/Physical Broadcast Channel (SS/PBCH) block, which includes a Primary Syncrhonization Signal (PSS), a Secondary Syncrhonization Signal (SSS), and a PBCH.
  • PSS Primary Syncrhonization Signal
  • SSS Secondary Syncrhonization Signal
  • PBCH Physical Broadcast Channel
  • a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.
  • Primary SCG Cell refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.
  • Secondary Cell refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.
  • Secondary Cell Group refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.
  • Serving Cell refers to the primary cell for a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.
  • serving cell refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA.
  • Special Cell refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.
  • Al policy refers to a type of declarative policies expressed using formal statements that enable the non-RT RIC function in the SMO to guide the near-RT RIC function, and hence the RAN, towards better fulfilment of the RAN intent.
  • Al Enrichment information refers to information utilized by near-RT RIC that is collected or derived at SMO/non-RT RIC either from non-network data sources or from network functions themselves.
  • Al-Policy Based Traffic Steering Process Mode refers to an operational mode in which the Near-RT RIC is configured through Al Policy to use Traffic Steering Actions to ensure a more specific notion of network performance (for example, applying to smaller groups of E2 Nodes and UEs in the RAN) than that which it ensures in the Background Traffic Steering.
  • Background Traffic Steering Processing Mode refers to an operational mode in which the Near-RT RIC is configured through 01 to use Traffic Steering Actions to ensure a general background network performance which applies broadly across E2 Nodes and UEs in the RAN.
  • Baseline RAN Behavior refers to the default RAN behavior as configured at the E2 Nodes by SMO
  • E2 refers to an interface connecting the Near-RT RIC and one or more O- CU-CPs, one or more O-CU-UPs, one or more O-DUs, and one or more O-eNBs.
  • E2 Node refers to a logical node terminating E2 interface.
  • ORAN nodes terminating E2 interface are: for NR access: O-CU-CP, O- CU-UP, 0-DU or any combination; and for E-UTRA access: O-eNB.
  • Intents in the context of 0-RAN systems/implementations, refers to declarative policy to steer or guide the behavior of RAN functions, allowing the RAN function to calculate the optimal result to achieve stated objective.
  • non-RT RIC refers to a logical function that enables non-real-time control and optimization of RAN elements and resources, AI/ML workflow including model training and updates, and policy-based guidance of applications/features in Near-RT RIC.
  • Near-RT RIC or “0-RAN near-real-time RAN Intelligent Controller” refers to a logical function that enables near-real-time control and optimization of RAN elements and resources via fine-grained (e.g., UE basis, Cell basis) data collection and actions over E2 interface.
  • fine-grained e.g., UE basis, Cell basis
  • 0-RAN Central Unit or “O-CU” refers to a logical node hosting RRC, SDAP and PDCP protocols.
  • 0-RAN Central Unit - Control Plane or “O-CU-CP” refers to a logical node hosting the RRC and the control plane part of the PDCP protocol.
  • 0-RAN Central Unit - User Plane or “O-CU-UP” refers to a logical node hosting the user plane part of the PDCP protocol and the SDAP protocol.
  • 0-RAN Distributed Unit or “0-DU” refers to a logical node hosting RLC/MAC/High-PHY layers based on a lower layer functional split.
  • O-RAN eNB or “O-eNB” refers to an eNB or ng-eNB that supports E2 interface.
  • O-RAN Radio Unit refers to a logical node hosting Low-PHY layer and RF processing based on a lower layer functional split. This is similar to 3GPP’s “TRP” or “RRH” but more specific in including the Low-PHY layer (FFT/iFFT, PRACH extraction).
  • the term “01” refers to an interface between orchestration & management entities (Orchestration/NMS) and O-RAN managed elements, for operation and management, by which FCAPS management, Software management, File management and other similar functions shall be achieved.
  • RAN UE Group refers to an aggregations of UEs whose grouping is set in the E2 nodes through E2 procedures also based on the scope of Al policies. These groups can then be the target of E2 CONTROL or POLICY messages.
  • Traffic Steering Action refers to the use of a mechanism to alter RAN behavior. Such actions include E2 procedures such as CONTROL and POLICY.
  • Traffic Steering Inner Loop refers to the part of the Traffic Steering processing, triggered by the arrival of periodic TS related KPM (Key Performance Measurement) from E2 Node, which includes UE grouping, setting additional data collection from the RAN, as well as selection and execution of one or more optimization actions to enforce Traffic Steering policies.
  • KPM Key Performance Measurement
  • Traffic Steering Outer Loop refers to the part of the Traffic Steering processing, triggered by the near-RT RIC setting up or updating Traffic Steering aware resource optimization procedure based on information from Al Policy setup or update, Al Enrichment Information (El) and/or outcome of Near-RT RIC evaluation, which includes the initial configuration (preconditions) and injection of related Al policies, Triggering conditions for TS changes.
  • Al Policy setup or update Al Enrichment Information (El) and/or outcome of Near-RT RIC evaluation, which includes the initial configuration (preconditions) and injection of related Al policies, Triggering conditions for TS changes.
  • El Al Enrichment Information
  • Triggering conditions for TS changes Triggering conditions for TS changes.
  • Traffic Steering Processing Mode refers to an operational mode in which either the RAN or the Near-RT RIC is configured to ensure a particular network performance. This performance includes such aspects as cell load and throughput, and can apply differently to different E2 nodes and UEs. Throughout this process, Traffic Steering Actions are used to fulfill the requirements of this configuration.
  • Traffic Steering Target refers to the intended performance result that is desired from the network, which is configured to Near-RT RIC over 01.
  • any of the disclosed embodiments and example implementations can be embodied in the form of various types of hardware, software, firmware, middleware, or combinations thereof, including in the form of control logic, and using such hardware or software in a modular or integrated manner.
  • any of the software components or functions described herein can be implemented as software, program code, script, instructions, etc., operable to be executed by processor circuitry.
  • the software code can be stored as a computer- or processorexecutable instructions or commands on a physical non-transitory computer-readable medium.
  • suitable media include RAM, ROM, magnetic media such as a hard-drive or a floppy disk, or an optical medium such as a compact disk (CD) or DVD (digital versatile disk), flash memory, and the like, or any combination of such storage or transmission devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne des systèmes, des procédés, et des dispositifs relatifs à l'optimisation d'équilibrage de charge. Un dispositif peut créer une instance d'objet de gestion (MOI) de fonction D-LBO afin de modéliser la fonction D-LBO. Le dispositif peut envoyer un message à un service de gestion d'approvisionnement (MnS) pour modifier des attributs de la MOI de fonction D-LBO afin de définir une ou plusieurs plages associées à la fonction D-LBO. Le dispositif peut identifier une réponse à partir du MnS d'approvisionnement indiquant que la MOI de fonction D-LBO a été modifiée.
PCT/US2022/044536 2021-09-24 2022-09-23 Optimisation d'équilibrage de charge (lbo) pour systèmes 5g WO2023049345A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202280037594.6A CN117378182A (zh) 2021-09-24 2022-09-23 5g系统的负载均衡优化

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163248299P 2021-09-24 2021-09-24
US63/248,299 2021-09-24

Publications (1)

Publication Number Publication Date
WO2023049345A1 true WO2023049345A1 (fr) 2023-03-30

Family

ID=85721168

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/044536 WO2023049345A1 (fr) 2021-09-24 2022-09-23 Optimisation d'équilibrage de charge (lbo) pour systèmes 5g

Country Status (2)

Country Link
CN (1) CN117378182A (fr)
WO (1) WO2023049345A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150044974A1 (en) * 2012-03-15 2015-02-12 Nec Corporation Radio communication system, radio station, network operation management apparatus, and network optimization method

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150044974A1 (en) * 2012-03-15 2015-02-12 Nec Corporation Radio communication system, radio station, network operation management apparatus, and network optimization method

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3 (Release 17 )", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 28.541, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. V17.3.0, 24 June 2021 (2021-06-24), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 27, XP052029623 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; Self-Organizing Networks (SON) for 5G networks (Release 17)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 28.313, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V17.2.0, 23 September 2021 (2021-09-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 54, XP052056593 *
HUAWEI: "CR TS 28.313 MLB procedure", 3GPP DRAFT; S5-213227, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. Online; 20210510 - 20210519, 30 April 2021 (2021-04-30), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051998896 *
INTEL: "Add LBO use cases, requirements, and related information", 3GPP DRAFT; S5-211128, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. e-Meeting; 20210125 - 20210203, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052181501 *

Also Published As

Publication number Publication date
CN117378182A (zh) 2024-01-09

Similar Documents

Publication Publication Date Title
EP4233419A1 (fr) Attribution de ressources pour un service de diffusion/multidiffusion en nouvelle radio
WO2022087474A1 (fr) Hiérarchisation d'équipements intra-utilisateur pour gérer un chevauchement de canaux de commande montants et de données de liaison montante
EP4150951A1 (fr) Techniques pour un processus et un service d'analyse de données de gestion (mda)
WO2022031553A1 (fr) Plan de données pour mégadonnées et données en tant que service dans des réseaux cellulaires de nouvelle génération
WO2022221495A1 (fr) Support d'apprentissage automatique pour services de gestion et services d'analyse de données de gestion
WO2022221260A1 (fr) Support de service de gestion de cycle de vie o-cloud
WO2022125296A1 (fr) Mécanismes pour permettre des services informatiques en réseau
WO2022087489A1 (fr) Indication de faisceau basée sur des informations de commande de liaison descendante (dci) pour une nouvelle radio (nr)
WO2023049345A1 (fr) Optimisation d'équilibrage de charge (lbo) pour systèmes 5g
WO2023122037A1 (fr) Mesures et données de localisation prenant en charge une analyse de données de gestion (mda) pour analyse de problème de couverture
WO2022232038A1 (fr) Mesures de performances pour un référentiel de données unifié (udr)
WO2024026515A1 (fr) Test d'entité d'intelligence artificielle et d'apprentissage machine
US20240155393A1 (en) Measurement reporting efficiency enhancement
WO2022261028A1 (fr) Fonctions de données et procédures dans un contrôleur intelligent de réseau d'accès radio non temps réel
WO2024015747A1 (fr) Sélection de fonction de gestion de session dans des réseaux cellulaires prenant en charge une strate de non-accès distribuée entre un dispositif et des fonctions de réseau
WO2024076852A1 (fr) Structure de fonction de coordination de collecte de données et de fonction d'analyse de données de réseau pour détection de services dans des réseaux cellulaires de prochaine génération
WO2024081642A1 (fr) Services de traitement en pipeline dans des réseaux cellulaires de prochaine génération
WO2023014745A1 (fr) Mesures de performance pour fonction d'exposition de réseau
WO2024092132A1 (fr) Chargement d'entité d'intelligence artificielle et d'apprentissage automatique dans des réseaux cellulaires
WO2024020519A1 (fr) Systèmes et procédés de partage de services d'une fonction de stockage de données non structurées
WO2023069750A1 (fr) Bons critères de qualité cellulaire
WO2023055852A1 (fr) Mesures de performance pour l'autorisation des politiques et l'exposition des événements pour les fonctions d'exposition du réseau
WO2024091970A1 (fr) Évaluation de performances pour inférence d'intelligence artificielle/apprentissage automatique
WO2023122043A1 (fr) Mesures de performance pour une fonction de gestion d'emplacement sur une gestion d'emplacement
WO2022240850A1 (fr) Restriction de domaine temporel pour une configuration de signal de référence d'informations d'état de canal

Legal Events

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

Ref document number: 22873632

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202280037594.6

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2022873632

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022873632

Country of ref document: EP

Effective date: 20240424