CN116349291A - Management service for load balancing optimization - Google Patents

Abstract

Apparatus and systems for providing relaxed measurement standard Load Balancing Optimization (LBO) are described, and Mobile Robustness Optimization (MRO) for distributed and centralized SON (D-SON) management functions is described. Use cases and requirements for D-SON management functions for distributed and centralized LBOs are described. The LBO gathers and analyzes load information to determine actions to take, including handover and reselection parameter adjustments.

Description

Management service for load balancing optimization

Priority statement

The present application claims priority from U.S. provisional patent application serial No. 63/110,208, filed on 5 of 11/2020, which is incorporated herein by reference in its entirety.

Technical Field

Embodiments relate to next generation wireless communications. In particular, some embodiments relate to Load Balancing Optimization (LBO) in 5G networks.

Background

The use and complexity of wireless systems, including 5 th generation (5G) networks and beginning to include 6 th generation (6G) networks, etc., has increased due to the increase in device types of User Equipment (UEs) that use network resources and the increase in the amount of data and bandwidth used by various applications (e.g., video streaming) operating on these UEs. With the substantial increase in the number and diversity of communication devices, the corresponding network environments (including routers, switches, bridges, gateways, firewalls, and load balancers) have become increasingly complex. Without this, the advent of any new technology presents a number of problems.

Drawings

In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The accompanying drawings generally illustrate by way of example, and not by way of limitation, the various embodiments discussed in the present document.

Fig. 1A illustrates an architecture of a network in accordance with some aspects.

Fig. 1B illustrates a non-roaming 5G system architecture in accordance with some aspects.

Fig. 1C illustrates a non-roaming 5G system architecture in accordance with some aspects.

Fig. 2 illustrates a block diagram of a communication device in accordance with some embodiments.

Fig. 3A illustrates a distributed LBO architecture according to some embodiments.

Fig. 3B illustrates a centralized LBO architecture according to some embodiments.

FIG. 4 illustrates a flow chart of LBO management in accordance with some aspects.

Detailed Description

The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may involve structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of others. The embodiments set forth in the claims include all available equivalents of those claims.

Fig. 1A illustrates an architecture of a network in accordance with some aspects. Network 140A includes 3GPP LTE/4G and NG network functions that may be extended to 6G functions. Thus, while reference will be made to 5G, it should be understood that this can be extended to 6G structures, systems and functions. The network functions may be implemented as discrete network elements on dedicated hardware, as software instances running on dedicated hardware, and/or as virtualized functions instantiated on an appropriate platform (e.g., dedicated hardware or cloud infrastructure).

Network 140A is shown to include User Equipment (UE) 101 and UE 102. The UEs 101 and 102 are shown as smartphones (e.g., handheld touch screen mobile computing devices connectable to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a portable (notebook) or desktop computer, wireless handset, drone, or any other computing device including a wired and/or wireless communication interface. The UEs 101 and 102 may be collectively referred to herein as UE 101, and the UE 101 may be configured to perform one or more of the techniques disclosed herein.

Any of the radio links described herein (e.g., as used in network 140A or any other illustrated network) may operate according to any of the example radio communication techniques and/or standards. Any spectrum management scheme includes, for example, private licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (e.g., licensed Shared Access (LSA) in 2.3-2.4GHz, 3.4-3.6GHz, 3.6-3.8GHz, and other frequencies, and Spectrum Access System (SAS) in 3.55-3.7GHz and other frequencies). Different single carrier or Orthogonal Frequency Domain Multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank based multi-carrier (FBMC), OFDMA, etc.), in particular 3GPP NR, may be used by allocating OFDM carrier data bit vectors to the corresponding symbol resources.

In some aspects, either of the UEs 101 and 102 may include an internet of things (IoT) UE or a cellular IoT (CIoT) UE, which may include a network access layer designed for low power IoT applications that utilize short-lived UE connections. In some aspects, either of the UEs 101 and 102 may include Narrowband (NB) IoT UEs (e.g., enhanced NB-IoT (eNB-IoT) UEs and further enhanced (FeNB-IoT) UEs). IoT UEs may exchange data with machine-to-machine (M2M) or machine-type communication (MTC) servers or devices through Public Land Mobile Networks (PLMNs), proximity-based services (ProSe) or device-to-device (D2D) communications, sensor networks, or IoT networks using technologies such as MTC. The M2M or MTC data exchange may be a machine initiated data exchange. The IoT network includes interconnected IoT UEs that may include uniquely identifiable embedded computing devices (within the internet infrastructure) with short-lived connections. The IoT UE may execute a background application (e.g., keep-alive messages, status updates, etc.) to facilitate connection of the IoT network. In some aspects, either of the UEs 101 and 102 may include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

The UEs 101 and 102 may be configured to connect (e.g., communicatively couple) with a Radio Access Network (RAN) 110. RAN 110 may be, for example, an evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), a next generation RAN (NG RAN), or other type of RAN.

The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which includes a physical communication interface or layer (discussed in further detail below); in this example, connections 103 and 104 are shown as air interfaces that enable communicative coupling, and may conform to cellular communication protocols, such as global system for mobile communications (GSM) protocols, code Division Multiple Access (CDMA) network protocols, push-to-talk (PTT) protocols, PTT Over Cellular (POC) protocols, universal Mobile Telecommunications System (UMTS) protocols, 3GPP Long Term Evolution (LTE) protocols, 5G protocols, 6G protocols, and so forth.

In one aspect, the UEs 101 and 102 may further exchange communication data directly through the ProSe interface 105. ProSe interface 105 may also be referred to as a Side Link (SL) interface that includes one or more logical channels including, but not limited to, a physical side link control channel (PSCCH), a physical side link shared channel (PSSCH), a physical side link discovery channel (PSDCH), a physical side link broadcast channel (PSBCH), and a physical side link feedback channel (PSFCH).

UE 102 is shown configured to access an Access Point (AP) 106 via a connection 107. Connection 107 may comprise a local wireless connection, e.g., a connection conforming to any IEEE 802.11 protocol, according to which AP 106 may comprise wireless fidelity

And a router. In this example, the AP 106 is shown connected to the internet and not to the core network of the wireless system (described in further detail below).

RAN 110 may include one or more access nodes that enable connections 103 and 104. These Access Nodes (ANs) may be referred to as Base Stations (BS), nodebs, evolved nodebs (enbs), next generation nodebs (gnbs), RAN nodes, etc., and may include ground stations (e.g., ground access points) or satellite stations that provide coverage within a geographic area (e.g., cell). In some aspects, communication nodes 111 and 112 may be transmission/reception points (TRP). In the case where the communication nodes 111 and 112 are nodebs (e.g., enbs or gnbs), one or more TRPs may function within the communication cell of the NodeB. RAN 110 may include one or more RAN nodes (e.g., macro RAN node 111) for providing macro cells and one or more RAN nodes (e.g., low Power (LP) RAN node 112) for providing femto cells or pico cells (e.g., cells with smaller coverage areas, smaller user capacities, or higher bandwidths than macro cells).

Either of the RAN nodes 111 and 112 may terminate (terminate) the air interface protocol and may be the first point of contact for the UEs 101 and 102. In some aspects, either of RAN nodes 111 and 112 may implement various logical functions of RAN 110 including, but not limited to, radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In an example, any of nodes 111 and/or 112 may be a gNB, eNB, or other type of RAN node.

RAN 110 is shown communicatively coupled to a Core Network (CN) 120 through an S1 interface 113. In various aspects, the CN 120 may be an Evolved Packet Core (EPC) network, a next generation packet core (NPC) network, or some other type of CN (e.g., as shown with reference to fig. 1B-1C). In this aspect, the S1 interface 113 is divided into two parts: an S1-U interface 114 that carries traffic data between RAN nodes 111 and 112 and serving gateway (S-GW) 122; and an S1 Mobility Management Entity (MME) interface 115, which is a signaling interface between RAN nodes 111 and 112 and MME 121.

In this aspect, the CN 120 includes an MME 121, an S-GW 122, a Packet Data Network (PDN) gateway (P-GW) 123, and a Home Subscriber Server (HSS) 124.MME 121 may be similar in function to the control plane of a conventional serving General Packet Radio Service (GPRS) support node (SGSN). MME 121 may manage mobility aspects in the access such as gateway selection and tracking area list management. HSS 124 may include a database of network users including subscription-related information used to support network entity handling communication sessions. The CN 120 may include one or several HSS 124 depending on the number of mobile subscribers, the capacity of the device, the organization of the network, etc. For example, the HSS 124 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, and the like.

S-GW 122 may terminate S1 interface 113 towards RAN 110 and route data packets between RAN 110 and CN 120. Furthermore, the S-GW 122 may be a local mobility anchor for inter-RAN node handover and may also provide an anchor for inter-3 GPP mobility. Other responsibilities of S-GW 122 may include lawful interception, charging, and some policy enforcement.

The P-GW 123 may terminate the SGi interface towards the PDN. The P-GW 123 may route data packets between the CN 120 and external networks, e.g., networks including an application server 184 (or referred to as an Application Function (AF)), through an Internet Protocol (IP) interface 125. The P-GW 123 may also transmit data to other external networks 131A, which other external networks 131A may include the internet, an IP multimedia Subsystem (IPs) network, and other networks. In general, the application server 184 may be an element that provides an application that uses IP bearer resources with a core network (e.g., UMTS Packet Service (PS) domain, LTE PS data service, etc.). In this aspect, P-GW 123 is shown communicatively coupled to application server 184 through IP interface 125. The application server 184 may also be configured to support one or more communication services (e.g., voice over internet protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 through the CN 120.

The P-GW 123 may also be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is a policy and charging control element of CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with an internet protocol connectivity access network (IP-CAN) session of the UE. In a roaming scenario with local traffic disruption, there may be two PCRFs associated with the IP-CAN session of the UE: a home PCRF (H-PCRF) within the HPLMN, and a visited PCRF (V-PCRF) within the Visited Public Land Mobile Network (VPLMN). PCRF 126 may be communicatively coupled to application server 184 through P-GW 123.

In some aspects, the communication network 140A may be an IoT network or a 5G or 6G network, including a 5G new radio network that uses communication in licensed (5G NR) and unlicensed (5G NR-U) spectrum. One of the current IoT implementations is the narrowband IoT (NB-IoT). Operations in the unlicensed spectrum may include Dual Connectivity (DC) operations and independent LTE systems in the unlicensed spectrum according to which LTE-based techniques operate only in the unlicensed spectrum without using "anchors" in the licensed spectrum, known as multewire. In future releases and 5G systems, it is desirable to further enhance the operation of LTE systems in licensed and unlicensed spectrum. Such enhanced operations may include techniques for side link resource allocation and UE processing behavior for NR side link V2X communications.

The NG system architecture (or 6G system architecture) may include RAN 110 and 5G core network (5 GC) 120.NG-RAN 110 may include multiple nodes, such as a gNB and NG-eNB. The CN 120 (e.g., 5G core network/5 GC) may include Access and Mobility Functions (AMFs) and/or User Plane Functions (UPFs). The AMF and UPF may be communicatively coupled to the gNB and the NG-eNB through NG interfaces. More specifically, in some aspects, the gNB and NG-eNB may connect to the AMF through a NG-C interface and to the UPF through a NG-U interface. The gNB and NG-eNB may be coupled to each other via an Xn interface.

In some aspects, the NG system architecture may use reference points between various nodes. In some aspects, each gNB and NG-eNB may be implemented as a base station, a mobile edge server, a small cell, a home eNB, or the like. In some aspects, in a 5G architecture, the gNB may be a Master Node (MN) and the NG-eNB may be a Slave Node (SN).

Fig. 1B illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, fig. 1B shows a 5G system architecture 140B, represented by a reference point, which can be extended to a 6G system architecture. More specifically, UE 102 may communicate with RAN 110 and one or more other 5GC network entities. The 5G system architecture 140B includes a plurality of Network Functions (NF), such as AMF 132, session Management Function (SMF) 136, policy Control Function (PCF) 148, application Function (AF) 150, UPF 134, network Slice Selection Function (NSSF) 142, authentication server function (AUSF) 144, and Unified Data Management (UDM)/Home Subscriber Server (HSS) 146.

The UPF 134 may provide a connection to a Data Network (DN) 152, which may include, for example, operator services, internet access, or third party services. The AMF 132 may be used to manage access control and mobility and may also include network slice selection functionality. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of access technology. The SMF 136 may be configured to set up and manage various sessions according to network policies. Thus, the SMF 136 may be responsible for session management and assignment of IP addresses to UEs. The SMF 136 may also select and control the UPF 134 for data transmission. The SMF 136 may be associated with a single session of the UE 101 or multiple sessions of the UE 101. That is, the UE 101 may have multiple 5G sessions. Each session may be assigned a different SMF. Using different SMFs may allow each session to be managed separately. Thus, the functionality of each session may be independent of the other.

The UPF 134 can be deployed in one or more configurations depending on the type of service desired and can be connected to a data network. PCF 148 may be configured to provide a policy framework (similar to PCRF in 4G communication systems) that uses network slicing, mobility management, and roaming. The UDM may be configured to store subscriber profiles and data (similar to HSS in a 4G communication system).

AF 150 may provide information about the packet flow to PCF 148 responsible for policy control to support the desired QoS. PCF 148 may set mobility and session management policies for UE 101. To this end, PCF 148 may use the packet flow information to determine an appropriate policy for the appropriate operation of AMF 132 and SMF 136. The AUSF 144 may store data for UE authentication.

In some aspects, the 5G system architecture 140B includes an IP Multimedia Subsystem (IMS) 168B and a plurality of IP multimedia core network subsystem entities, such as Call Session Control Functions (CSCFs). More specifically, the IMS 168B includes CSCFs that may act as proxy CSCF (P-CSCF) 162B, serving CSCF (S-CSCF) 164B, emergency CSCF (E-CSCF) (not shown in FIG. 1B), or interrogating CSCF (I-CSCF) 166B. P-CSCF 162B may be configured as a first point of contact for UE 102 within IM Subsystem (IMs) 168B. S-CSCF 164B may be configured to handle session states in the network and E-CSCF may be configured to handle certain aspects of emergency sessions, such as routing emergency requests to the correct emergency center or PSAP. I-CSCF 166B may be configured to act as a point of contact for all IMS connections within the operator's network that are destined for subscribers of the network operator or roaming subscribers currently located within the service area of the network operator. In some aspects, I-CSCF 166B may be connected to another IP multimedia network 170E, e.g., an IMS operated by a different network operator.

In some aspects, the UDM/HSS 146 may be coupled to an application server 160E, which application server 160E may include a Telephony Application Server (TAS) or other Application Server (AS). AS 160B may be coupled to IMS 168B through S-CSCF 164B or I-CSCF 166B.

The reference point representation shows that there may be interactions between the corresponding NF services. For example, fig. 1B shows the following reference points: n1 (between UE 102 and AMF 132), N2 (between RAN 110 and AMF 132), N3 (between RAN 110 and UPF 134), N4 (between SMF 136 and UPF 134), N5 (between PCF 148 and AF 150, not shown), N6 (between UPF 134 and DN 152), N7 (between SMF 136 and PCF 148, not shown), N8 (between UDM 146 and AMF 132, not shown), N9 (between two UPF 134, not shown), N10 (between UDM 146 and SMF 136, not shown), N11 (between AMF 132 and SMF 136), N12 (between AUSF 144 and AMF 132, not shown), N13 (between AUSF 144 and UDM 146, not shown), N14 (between PCF 148 and AMF 132 in the case of a non-roaming scenario, or between PCF 148 and AMF 132, not shown), N16 (between AMF 142 and nsf 132, not shown), N11 (between AMF 132 and nsf 132, not shown). Other reference point representations not shown in fig. 1B may also be used.

Fig. 1C shows a 5G system architecture 140C and a service-based representation. In addition to the network entities shown in fig. 1B, the system architecture 140C may also include a Network Exposure Function (NEF) 154 and a Network Repository Function (NRF) 156. In some aspects, the 5G system architecture may be service-based, and interactions between network functions may be represented by respective point-to-point reference points Ni, or as service-based interfaces.

In some aspects, as shown in fig. 1C, the service-based representation may be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this aspect, 5G system architecture 140C may include the following service-based interfaces: namf 158H (service-based interface presented by AMF 132), nsmf 158I (service-based interface presented by SMF 136), nnef 158B (service-based interface presented by NEF 154), npcf 158D (service-based interface presented by PCF 148), nudm 158E (service-based interface presented by UDM 146), naf 158F (service-based interface presented by AF 150), nnrf 158C (service-based interface presented by NRF 156), nnssf 158A (service-based interface presented by NSSF 142), nausf 158G (service-based interface presented by AUSF 144). Other service-based interfaces not shown in fig. 1C (e.g., nudr, N5g-eir, and Nudsf) may also be used.

The NR-V2X architecture may support high reliability low latency side link communications with multiple traffic patterns, including periodic and aperiodic communications with random packet arrival times and sizes. The techniques disclosed herein may be used to support high reliability in distributed communication systems with dynamic topologies, including side link NR V2X communication systems.

Fig. 2 illustrates a block diagram of a communication device in accordance with some embodiments. The communication device 200 may be a UE (e.g., a dedicated computer, a personal or notebook computer (PC), a tablet PC, or a smart phone), a dedicated network device (e.g., an eNB), server running software configuring a server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequentially or otherwise) specifying actions to be taken by the machine. For example, the communication device 200 may be implemented as one or more of the devices shown in fig. 1A-1C. Note that the communications described herein may be encoded prior to transmission by a transmitting entity (e.g., UE, gNB) for receipt by a receiving entity (e.g., gNB, UE) and decoded after receipt by the receiving entity.

Examples as described herein may include or may operate on logic or several components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) that are capable of performing specified operations and that may be configured or arranged in a manner. In an example, the circuits may be arranged as modules in a specified manner (e.g., internally or to an external entity, such as other circuits). In an example, all or part of one or more computer systems (e.g., stand-alone, client, or server computer systems) or one or more hardware processors may be configured by firmware or software (e.g., instructions, application portions, or applications) as modules that operate to perform specified operations. In an example, the software may reside on a machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

Thus, the term "module" (and "component") is understood to encompass a tangible entity, be it physically constructed, a specially configured (e.g., hardwired), or a temporarily (e.g., transient) configured (e.g., programmed) entity to operate in a specified manner or to perform some or all of any of the operations described herein. Considering the example where modules are temporarily configured, it is not necessary to instantiate each module at any one time. For example, where a module includes a general-purpose hardware processor configured with software, the general-purpose hardware processor may be configured as each of the different modules at different times. The software may accordingly configure the hardware processor to constitute one particular module at one time and another module at another time, for example.

The communication device 200 may include a hardware processor (or equivalent processing circuit) 202 (e.g., a Central Processing Unit (CPU), GPU, hardware processor core, or any combination thereof), a main memory 204, and a static memory 206, some or all of which may communicate with each other via an interconnect (e.g., bus) 208. Main memory 204 may include any or all of removable storage and non-removable storage, volatile memory, or nonvolatile memory. The communication device 200 may also include a display unit 210, such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a User Interface (UI) navigation device 214 (e.g., a mouse). In an example, display unit 210, input device 212, and UI navigation device 214 may be touch screen displays. The communication device 200 may also include a storage device (e.g., a drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a Global Positioning System (GPS) sensor, compass, accelerometer, or other sensor. The communication device 200 may also include an output controller, such as a serial (e.g., universal Serial Bus (USB)), parallel, or other wired or wireless (e.g., infrared (IR), near Field Communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., printer, card reader, etc.).

The storage device 216 may include a non-transitory machine-readable medium 222 (hereinafter machine-readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 224 may also reside, completely or at least partially, within the main memory 204, within the static memory 206, and/or within the hardware processor 202 during execution thereof by the communication device 200. While the machine-readable medium 222 is shown to be a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 224.

The term "machine-readable medium" can include any medium that can store, encode, or carry instructions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of this disclosure, or that can store, encode, or carry data structures used by or associated with such instructions. Non-limiting examples of machine readable media may include solid state memory, as well as optical and magnetic media. Specific examples of machine-readable media may include: nonvolatile memory such as semiconductor memory devices (e.g., electrically Programmable Read Only Memory (EPROM), electrically Erasable Programmable Read Only Memory (EEPROM)), and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disk; random Access Memory (RAM); CD-ROM and DVD-ROM discs.

The instructions 224 may also be transmitted or received over a communications network using a transmission medium 226 via the network interface device 220 using any of a number of Wireless Local Area Network (WLAN) transmission protocols (e.g., frame relay, internet Protocol (IP), transmission Control Protocol (TCP), user Datagram Protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a Local Area Network (LAN), a Wide Area Network (WAN), a packet data network (e.g., the internet), a mobile telephone network (e.g., a cellular network), a Plain Old Telephone (POTS) network, and a wireless data network. Communications over the network may include one or more different protocols, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards (referred to as Wi-Fi), the IEEE 802.16 family of standards (referred to as WiMax), the IEEE 802.15.4 family of standards, the Long Term Evolution (LTE) family of standards, the Universal Mobile Telecommunications System (UMTS) family of standards, point-to-point (P2P) networks, the Next Generation (NG)/fifth generation (5G) standards, and so forth. In an example, the network interface device 220 may include one or more physical jacks (e.g., ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the transmission medium 226.

Note that the term "circuitry" as used herein refers to, is part of, or includes, hardware components configured to provide the described functionality, such as electronic circuitry, logic circuitry, 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 (hcpll), a structured ASIC, or a programmable SoC), a Digital Signal Processor (DSP), or the like. In some embodiments, 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) and program code for performing the functions of the program code. In these embodiments, a combination of hardware elements and program code may be referred to as a particular type of circuit.

Thus, the term "processor circuit" or "processor" as used herein refers to, is part of, or includes the following circuitry: the circuit is capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing and/or transmitting digital data. The term "processor circuit" or "processor" may refer to one or more application processors, one or more baseband processors, a physical Central Processing Unit (CPU), a single or multi-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions (e.g., program code, software modules, and/or functional processes).

Any of the radio links described herein may operate in accordance with any one or more of the following radio communication technologies and/or standards, including, but not limited to: global system for mobile communications (GSM) radio communications technology, general Packet Radio Service (GPRS) radio communications technology, enhanced data rates for GSM evolution (EDGE) radio communications technology, and/or third generation partnership project (3 GPP) radio communications technology, such as Universal Mobile Telecommunications System (UMTS), free multimedia access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP long term evolution advanced (LTE-advanced), code division multiple access 2000 (CDMA 2000), cellular Digital Packet Data (CDPD), mobitex, third generation (3G), circuit Switched Data (CSD), high Speed Circuit Switched Data (HSCSD), universal mobile telecommunications system (third generation) (UMTS (3G)), wideband code division multiple access (universal mobile telecommunications system) (W-CDMA (UMTS)), high Speed Packet Access (HSPA), high Speed Downlink Packet Access (HSDPA), high Speed Uplink Packet Access (HSUPA), high speed packet access+ (a+), universal mobile telecommunications system time division duplex (UMTS-TDD), time division multiple access (HSPA-CDMA), time division multiple access (TD-synchronization (TD), third generation partnership project (TD-4) (3G), release 4 (release 4, release 4 (release 9.3G)), wideband code division multiple access (3 partnership project 4 (3G), 3GPP release 4 (release 9, release 4, 3.3G) 3GPP rel.11 (3 rd generation partnership project release 11), 3GPP rel.12 (3 rd generation partnership project release 12), 3GPP rel.13 (3 rd generation partnership project release 13), 3GPP rel.14 (3 rd generation partnership project release 14), 3GPP rel.15 (3 rd generation partnership project release 15), 3GPP rel.16 (3 rd generation partnership project release 16), 3GPP rel.17 (3 rd generation partnership project release 17) and subsequent releases (e.g., rel.18, rel.19, etc.), 3GPP 5G, 5G new radio (5G NR), 3GPP 5G new radio, 3GPP LTE extension, LTE advanced specialty, LTE Licensed Assisted Access (LAA), muLTEfire, UMTS Terrestrial Radio Access (UTRA), evolved UMTS terrestrial radio access (E-UTRA), long term evolution advanced (fourth generation) (LTE advanced (4G)), cdmaOne (2G), code division multiple access 2000 (third generation) (CDMA 2000 (3G)), optimized evolution data or evolution-only data (EV-DO), advanced mobile phone system (first generation) (AMPS (1G)), full access communication system/extended full access communication system (TACS/ETACS), digital AMPS (second generation) (D-AMPS (2G)), push-to-talk (PTT), mobile phone system (MTS), improved mobile phone system (IMTS), advanced mobile phone system (AMTS), norway (Offentlig Landmobil Telefoni, public land mobile phone) MTD (abbreviation of Swedish Mobiltelefonisystem D, or mobile phone system D), public automated land Mobile (Autotel/PALM), ARP (Autoloadiopuhin, "automotive radiotelephone"), NMT (Nordic Mobile telephone), a high capacity version of NTT (Japanese telecom telephone) (Hicap), cellular Digital Packet Data (CDPD), mobitex, dataTAC, integrated Digital Enhanced Network (iDEN), personal Digital Cellular (PDC), circuit Switched Data (CSD), personal handhelds phone system (PHS), broadband integrated digital enhanced network (WiDEN), iBurst, unlicensed Mobile Access (UMA), also known as 3GPP Universal Access network or GAN standard), zigbee, bluetooth (r), wireless systems operating at 10-300GHz and above, such as Wigig, IEEE 802.11ad, IEEE 802.11ay, etc.), technologies operating at 300GHz and THz bands, (reporting to other systems (e.g., systems operating in accordance with the 3GPP/LTE, IEEE 802.11, IEEE 11 or other short range communication systems (35) or other vehicles (usually by the public transport infrastructure) in accordance with the standard of 3GPP universal access network or GAN), zigbee, bluetooth (r), wireless gigabit (Wigig., IEEE 802.11ad, IEEE 802.11ay, and IEEE 2 MHz, and other vehicles (usually reporting (35) systems, 3 MHz and other communication infrastructure (35) systems, 3 MHz, 4 to the vehicle infrastructure (35) and other vehicles are usually the communication infrastructure (35) and (35) systems and the communication infrastructure (35) are generally, and the infrastructure (35I and 2 systems are generally the system and the infrastructure (2), the European style of IEEE 802.11 p-based DSRC includes ITS-G5A (i.e., ITS-G5 operated in the European ITS band dedicated to safety-related applications in the frequency range 5875GHz to 5905 GHz), ITS-G5B (i.e., operated in the European ITS band dedicated to ITS non-safety applications in the frequency range 5855GHz to 5875 GHz), ITS-G5C (i.e., ITS application operated in the frequency range 5470GHz to 5725 GHz)), DSRC in Japan in the 700MHz band (including 715MHz to 725 MHz), IEEE 802.11 bd-based systems, and so forth.

The various aspects described herein may be used in the context of any spectrum management scheme including dedicated licensed spectrum, unlicensed spectrum, licensed exempt spectrum, (licensed) shared spectrum (e.g., licensed Shared Access (LSA) in frequencies 2.3-2.4GHz, 3.4-3.6GHz, 3.6-3.8GHz and above, and Spectrum Access System (SAS)/Citizen Broadband Radio System (CBRS) in frequencies 3.55-3.7GHz and above). Suitable spectral bands include IMT (international mobile communications) spectrum and other types of spectrum/bands such as bands with national allocations (including 450-470MHz, 902-928MHz (note: e.g., allocated in US (FCC part 15)), 863-868.6MHz (note: e.g., allocated in the european union (ETSI EN 300 220)), 915.9-929.7MHz (note: e.g., allocated in japan), 917-923.5MHz (note: e.g., allocated in korea), 755-779MHz and 779-787MHz (note: e.g., allocated in china), 790-960MHz, 1710-2025MHz, 2110-2200MHz, 2300-2400MHz, 2.4-2.4835GHz (note: which is an ISM band with global availability), and which is used by the-Fi technology series (11 b/g/n/ax) and bluetooth), 2500-2690MHz, 698-790MHz, 610-790.7 MHz, 0-3600MHz, 0-3 MHz, and 3.7 MHz (note: e.g., allocated in china), and 3-2025 MHz (note: e.25.g., allocated in EU), and 775.725 (note: e.g., allocated in EU 5 i.25-5 GHz), total, and 60.725 (note: e.g., allocated in EU 25-5.g., EU 5 MHz), and 60-5.725 (see e.g., normal bands such as those in EU 25.25.25.25.25.725, 25.725, which are allocated in the whole, and 60.725 radio bands (e.g., the internet bands). The next generation Wi-Fi system is expected to include the 6GHz spectrum as the operating band, but notably, by 12 months in 2017, wi-Fi systems have not been allowed to be used in that band. The regulations are expected to be completed in 2019-2020, IMT advanced spectrum, IMT-2020 spectrum (which is expected to include 3600-3800MHz, 3800-4200MHz, 3.5GHz band, 700MHz band, 24.25-86GHz band, etc.), spectrum available under the FCC "front of spectrum" 5G initiative (including 27.5-28.35GHz, 29.1-29.25GHz, 31-31.3GHz, 37-38.6GHz, 38.6-40GHz, 42-42.5GHz, 57-64GHz, 71-76GHz, 81-86GHz, 92-94GHz, etc.), ITS (intelligent transportation system) band currently allocated to WiGig (e.g., wiGig band 1 (57.24-59.40 GHz), wiGig band 2 (59.40-61.56 GHz), and wig 3GHz (61.56-63.72 GHz), and wig band (78-96 GHz), and a total of which is allocated to the radio spectrum (e.g., 35-96 GHz) and 35GHz band (which is allocated to the future radio system) of 35.85-5.85-5.925 GHz and 63-64GHz, and the other bands (e.g., 35-64 GHz), and the other bands (which are allocated to the future radio bands (e.g., 35-96 GHz) of the future radio system) are allocated to the future radio bands (35-71 GHz and 35 GHz-96 GHz) and 35GHz (which are allocated to the future-allocated portions of the radio bands (e.g.g.g.35-71-35 GHz and 35-71 and 35 GHz-71, and 35-71-15) and the future-allocated to the future-allocated bands). Furthermore, the scheme may be used on the basis of assistance of frequency bands such as the TV white space band (typically below 790 MHz), with 400MHz and 700MHz frequency bands being promising candidate frequency bands. In addition to cellular applications, specific applications in the vertical market may also be addressed, such as PMSE (programming and special events), medical, health, surgical, automotive, low latency, drone, etc. applications.

Various aspects described herein can also enable hierarchical application of an aspect, such as by introducing hierarchical usage priorities for different types of users (e.g., low/medium/high priority, etc.) based on priority access to spectrum, such as a level 1 user having the highest priority, followed by a level 2 user, followed by a level 3 user, etc.

Various aspects described herein may also be applied to different single carriers or OFDM types (CP-OFDM, SC-FDMA, SC-OFDM, filter group based multi-carrier (FBMC), OFDMA, etc.), by allocating OFDM carrier data bit vectors to corresponding symbol resources (in particular, 3GPP NR (new radio)).

Some features in this document are defined for the network side, e.g. AP, eNB, NR, or gNB, noting that this term is commonly used in the context of 3gpp 5G and 6G communication systems, etc. Nonetheless, the UE may also play this role and act as an AP, eNB or gNB; that is, some or all of the features defined for the network device may be implemented by the UE.

As described above, the changes introduced in 5G systems include self-organizing networks (SONs) that operate based on SON algorithms. Different types of SON may be used. In centralized SON (C-SON), SON algorithms are executed in 3GPP management systems. The C-SON solution may be a cross-domain centralized SON solution (where SON algorithms are performed in a 3GPP cross-domain layer), a domain centralized SON solution (where SON algorithms are performed in a 3GPP domain layer), or a hybrid SON. In a distributed SON (D-SON) solution, SON algorithms are executed in the network function layer of the 5G system.

The SON algorithm may include: monitoring the network(s) by collecting measurement data, including data provided by a Management Data Analysis Service (MDAS); analyzing the measurement data to determine if there is a problem in the network(s) to be solved; making decisions about SON actions for solving the problem; executing SON action; and evaluating whether the problem has been solved by analyzing the management data. Thus, in a cross-domain centralized SON, the management function(s) (MnF) in the 3GPP cross-domain layer monitor the network through measurement data, analyze the measurement data, make decisions about SON actions, and perform SON actions.

In a domain-centralized SON, mnF(s) in the domain layer monitor the network through measurement data, analyze the measurement data, make decisions about SON actions, and perform SON actions. MnF(s) in the cross-domain layer are responsible for management and control of domain-centralized SON functions. Management and control may include: turning on/off the domain-centralized SON function, formulating a policy for the domain-centralized SON function, and/or evaluating performance of the domain-centralized SON function.

In D-SON, the SON algorithm is located in NF. Thus, NF monitors network events, analyzes measurement data, makes decisions about SON actions, and performs SON actions. The D-SON management function turns on/off the D-SON function and provides policies, targets, and supplemental information (e.g., scope attributes) for the D-SON function. The D-SON evaluation function evaluates whether the problem has been solved and can apply D-SON management actions.

In hybrid SON, SON algorithms are performed at two or more of NF layer, domain layer, or 3GPP cross-domain layer. The 3GPP management system (i.e., mnF(s) and NF in the domain or 3GPP cross-domain) work together in a coordinated manner to build a complete SON algorithm. The decision about SON actions may be made by the 3GPP management system and/or NF.

The SON may provide LBO functionality. One goal of LBO is to automatically allocate user traffic between neighboring cells to ensure efficient use of radio resources while providing a good end-user experience and performance. The LBO may collect and analyze load information to determine actions that the gNB will take. These actions may include UE selection (where the gNB selects and instructs one or more UEs to handover to a non-congested neighbor cell), cell reselection (where the gNB indicates that one or more UEs camp on a less congested neighbor cell), and mobility settings (where the gNB modifies handover parameters to alter the coverage of the congested cell). Fig. 3A illustrates a distributed LBO architecture according to some embodiments. Fig. 3B illustrates a centralized LBO architecture according to some embodiments. Fig. 3A and 3B illustrate two ways of implementing LBO: the distributed LBO function resides in the gNB and is managed by operations, administration, and maintenance (OAM) (fig. 3A), and the centralized LBO function resides in the OAM (fig. 3B). Use cases and requirements for D-SON management functions of distributed LBOs and centralized LBOs are provided, as well as management services and information for supporting management of distributed LBOs and centralized LBOs.

6.4 use cases

6.4.1 distributed SON management

X LBO (load-balancing optimization)

/>

6.1 requirement

6.1.1 distributed SON management 6.1.1.2LBO (load Balancing optimization)

The producer of REQ-DLBO-FUN-1 configured MnS should have the ability to allow authorized consumers to set or update targets, HO offset ranges and control parameters for LBO functions.

The REQ-DLBO-FUN-2 performance assurance MnS producer should have the ability to allow authorized consumers to collect LBO related performance measurements for assessing LBO performance.

The producer of REQ-DLBO-FUN-3 configured MnS should have the ability to notify authorized consumers of the LBO actions being performed.

6.4.2 centralized SON

X LBO (load-balancing optimization)

6.1.2 centralized SON

X LBO (load-balancing optimization)

The producer of REQ-CLBO-FUN-1 configured MnS should have the ability to allow authorized consumers to set or update HO offset ranges for LBO functions.

The REQ-CLBO-FUN-2 performance guarantees that the producer of MnS should have the ability to allow authorized consumers to collect LBO load and target related performance measurements.

7 management services for SON

7.1 management services for D-SON management

X LBO (load-balancing optimization)

Component type a of 1.1.1 mns

Table 7.1.X.1-1: D-LBO type A

Component type B definition of 1.1.2 mns

7.1.X.2.1 target information

The targets for D-LBO are shown in Table 7.1. X.2.1-1.

Table 7.1.X.2.1-1: D-LBO target

Control information 7.1.X.2.2

This parameter is used to control the LBO function.

Table 7.1.X.2.2-1: D-LBO control information

The range of parameter switching parameters to be updated is provided by the LBO management function.

Table 7.1.X.2.3-1: range of handover parameters

Component type C definition of 1.1. X.3MnS

Performance measurement of 7.1.X.3.1

Performance measurements related to LBO are recorded in table 7.1.X.3.1-1:

table 7.1.X.3.1-1: D-LBO correlation performance measurement

7.2 management services for C-SON

LBO (load balancing optimization).

Component type a of 1mns

Table 7.2.X.1-1: C-LBO type A

/>

Component type B definition of 2.2.2 mns

7.2.X.2.1 target information

The targets for C-LBO are shown in Table 7.2. X.2.1-1.

Table 7.2.X.2.1-1: C-LBO target

Control information 7.2.X.2.2

This parameter is used to control the LBO function.

Table 7.2.X.2.2-1: C-LBO control information

Parameters to be updated the table below lists the range of handover parameters.

Table 7.2.X.2.3-1: range of handover parameters

Component type C definition of 3MnS

Performance measurement of 7.2.X.3.1

Table 7.2.X.3.1-1 lists performance measurements for monitoring the load of NR cells (see item 15.5.1.2 in TS 38.300).

Table 7.2.X.3.1-1: C-LBO load performance measurement

/>

Table 7.2.X.3.1-2 lists performance measurements for monitoring LBO performance according to a target:

table 7.2.X.3.1-2: C-LBO correlation performance measurement

FIG. 4 illustrates a flow chart of LBO management in accordance with some aspects. In particular, fig. 4 depicts a process describing how the D-SON management function can manage the LBO function. Suppose that the D-SON management function has created a Performance Measurement (PM) job using a performance guarantee management service (MnS) to collect measurements related to handover.

At operation 1, the D-SON management function uses a management service for NF provisioning with a modified moiattributes operation (see clause 5.1.3 in TS 28.532) to configure a range of Handover (HO) and/or reselection parameters for LBO functions.

At operation la, mnS settings are provisioned for the range of Mobile Robustness Optimization (MRO) functions.

At operation 2, the D-SON management function configures MnS with a Network Function (NF) with a modified moiattributes operation to enable the LBO function for a given NR cell (if it is not enabled).

At operation 2a, mnS enabled LBO function is provisioned.

At operation 3, the LBO function gathers real-time load information to determine and perform actions to balance traffic load between NR cells.

At operation 4, the D-SON management function collects performance measurements related to LBO.

At operation 5, the D-SON management function analyzes the measurements to evaluate LBO performance.

At operation 6, if the LBO fails to reach the expectations, the D-SON management function updates the range of handover parameters using the provisioning MnS with the modyMOIAttributes operation.

At operation 6a, a range of MnS update HO and/or reselection parameters is provisioned. The interface between the MnS and the D-LBO functions is not subject to standardization constraints.

Although embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the disclosure. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This detailed description is, therefore, not to be taken in a limiting sense, and the scope of the various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

The subject matter may be referred to herein, individually and/or collectively, by the term "embodiment" merely for convenience and without intending to voluntarily limit the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.

In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, independent of any other instance or use of "at least one" or "one or more". In this document, the term "or" is used to refer to a non-exclusive or, such that "a or B" includes "a, but no B", "B, but no a" and "a and B", unless otherwise indicated. In this document, the terms "comprise" and "wherein" are used as plain english equivalents of the respective terms "comprising" and "wherein. In addition, in the appended claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process that includes other elements in addition to those listed after such term in a claim is still considered to fall within the scope of that claim. In addition, in the appended claims, the terms "first", "second", and "third", etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

The abstract of the disclosure is provided to conform to 37c.f.r.1.72 (b), which requires an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. The abstract was submitted under the following cleavage: it is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Furthermore, in the foregoing detailed description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.

Claims (20)

1. An apparatus for operation, administration and maintenance (OAM), the apparatus comprising:

processing circuitry configured to:

enabling a Load Balancing Optimization (LBO) function;

in response to receiving the notification, collecting measurements related to LBO performance;

determining whether LBO performance meets an LBO target for the LBO function based on an analysis of the measurement related to LBO performance; and

Taking an action in response to determining that the LBO performance does not meet the LBO target; and

a memory configured to store the LBO target.

2. The apparatus of claim 1, wherein the processing circuitry is configured to support distributed LBO (D-LBO).

3. The apparatus of claim 2, wherein the processing circuit is further configured to:

encoding a first request for transmission to a provisioning management service (MnS), the first request for setting a range of at least one of a handover parameter or a reselection parameter for a Load Balancing Optimization (LBO) function;

encoding a second request for transmission to the provisioning MnS, the second request for setting the LBO target; and

to enable the LBO function, a third request is encoded for transmission to the provisioning MnS, the third request for enabling the LBO function.

4. The apparatus of claim 3, wherein the processing circuit is further configured to:

decoding a notification from the provisioning MnS after transmitting the third request, the notification indicating that LBO actions have been performed; and

in response to receiving the notification, the measurements related to LBO performance are collected.

5. The apparatus of claim 4, wherein to take the action, the processing circuit is configured to: a fourth request is encoded for transmission to the provisioning MnS, the fourth request being for updating the target for the LBO function.

6. The apparatus of claim 3, wherein:

the first request includes a request for setting a range of the handover parameters for the LBO function, and

in order to take the action, the processing circuit is configured to encode a request for updating the range of the switching parameters for transmission to the provisioning MnS.

7. The apparatus of claim 1, wherein the processing circuitry is configured to support centralized LBO (C-LBO).

8. The apparatus of claim 7, wherein the processing circuit is further configured to:

collecting LBO load measurements from a performance assurance management service (MnS); and

based on the analysis of the LBO load measurements, a range of handover parameters is updated to optimize traffic load distribution between neighboring cells.

9. The apparatus of claim 8, wherein to take the action, the processing circuit is configured to: a fourth request is encoded for transmission to the provisioning MnS, the fourth request being for updating the target for the LBO function.

10. The apparatus of claim 1, wherein the LBO target comprises:

load-dependent Radio Resource Control (RRC) connection establishment success rate,

Load-dependent RRC connection reestablishment success rate

Load-dependent RRC connection recovery success rate.

11. The apparatus of claim 1, wherein:

the actions include updating the range of switching parameters, and

the range of the switching parameters includes:

the maximum deviation of the switching trigger is calculated,

minimum time between handover trigger changes

A timer for detecting a too early handover, a too late handover, and a handover to a wrong cell.

12. The apparatus of claim 1, wherein the measurement related to LBO performance comprises:

the number of Radio Resource Control (RRC) connection establishment attempts,

the number of successful RRC connection establishment,

the number of RRC connection re-establishment attempts,

the number of RRC connection re-establishment successes,

the number of RRC connection recovery attempts

The number of RRC connection recovery successes.

13. The apparatus of claim 1, wherein the measurement related to LBO performance comprises:

the total usage of downlink Physical Resource Blocks (PRBs),

the total usage of uplink PRBs,

the allocation of the downlink PRBs is performed,

allocation of the uplink PRBs,

the average number of downlink PRBs is set,

the average number of uplink PRBs is set,

An average number of Radio Resource Control (RRC) connections,

the maximum number of RRC connections is determined,

average number of stored inactive RRC connections

The maximum number of stored inactive RRC connections.

14. An apparatus for a 5 th generation NodeB (gNB), the apparatus comprising:

configuring at least one of a range of handover parameters or a range of reselection parameters for a distributed load balancing optimization (D-LBO) function based on a first request from operations, administration and maintenance (OAM);

after configuring the at least one of the range of switching parameters or the range of reselection parameters, enabling the D-LBO function based on a second request from the OAM; and

in response to determining by a distributed SON (D-SON) management function that a measurement related to LBO performance has not reached an LBO target for the LBO function, reconfiguring the at least one of a range of handover parameters or a range of reselection parameters; and

a memory configured to store the LBO target.

15. The apparatus of claim 14, wherein the processing circuit is configured to use a modymoiattributes operation of the D-SON management function to configure the at least one of a range of handover parameters or a range of reselection parameters, to enable the D-LBO function, and to reconfigure the at least one of a range of handover parameters or a range of reselection parameters.

16. The apparatus of claim 14, wherein the LBO target comprises:

load-dependent Radio Resource Control (RRC) connection establishment success rate,

load-dependent RRC connection reestablishment success rate

Load-dependent RRC connection recovery success rate.

17. The apparatus of claim 14, wherein:

the actions include updating the range of switching parameters, and

the range of the switching parameters includes:

the maximum deviation of the switching trigger is calculated,

minimum time between handover trigger changes

A timer for detecting a too early handover, a too late handover, and a handover to a wrong cell.

18. The apparatus of claim 14, wherein the measurement related to LBO performance comprises:

the total usage of downlink Physical Resource Blocks (PRBs),

the total usage of uplink PRBs,

the allocation of the downlink PRBs is performed,

allocation of the uplink PRBs,

the average number of downlink PRBs is set,

the average number of uplink PRBs is set,

an average number of Radio Resource Control (RRC) connections,

the maximum number of RRC connections is determined,

average number of stored inactive RRC connections

The maximum number of stored inactive RRC connections.

19. A non-transitory computer-readable storage medium storing instructions for execution by one or more processors of a distributed SON (D-SON) management function, the one or more processors configured to, when executed, configure the D-SON management function to:

using a provisioning management service (MnS) to configure a range of at least one of a handover parameter or a reselection parameter;

setting a target of LBO function using the provisioning MnS;

after the target has been set, using provisioning MnS to enable the D-LBO function;

receiving a notification from the provisioning MnS, the notification indicating that an LBO action has been performed;

collecting measurements from the performance-guaranteed MnS related to LBO performance;

analyzing the measure related to LBO performance to determine if LBO performance meets the target; and

in response to determining that the LBO performance does not meet the target, a range of the handover parameters is updated.

20. The non-transitory computer-readable storage medium of claim 19, wherein the range of handover parameters comprises:

the maximum deviation of the switching trigger is calculated,

minimum time between handover trigger changes

A timer for detecting a too early handover, a too late handover, and a handover to a wrong cell.

Images