DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
SYSTEMS AND METHODS FOR PROVIDING LOAD BALANCING
2. APPLICANT(S)
Name Nationality Address
JIO PLATFORMS LIMITED INDIAN Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
3. PREAMBLE TO THE DESCRIPTION
The following specification particularly describes the invention and the manner in which it is to be performed.

RESERVATION OF RIGHTS
[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and/or trade dress protection, belonging to JIO PLATFORMS LIMITED or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.
FIELD OF THE DISCLOSURE
[0002] The present disclosure generally relates to the field of wireless telecommunications network. More particularly, the present disclosure relates to systems and methods for providing load balancing in a radio access network.
DEFINITION
[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.
[0004] The expression ‘gNodeB (gNB)’ used hereinafter in the specification refers to a next-generation Node B in a 5G network, responsible for managing radio resources and serving the User Equipments (UEs) within a particular cell.
[0005] The expression ‘Load balancing’ used hereinafter in the specification refers to a process of distributing network traffic and workloads across multiple small cell gNBs or other network units to ensure that no single unit is overloaded.
[0006] The expression ‘Collocated cells’ used hereinafter in the specification refers to multiple cells deployed in the same geographical location but operating on different frequency bands. These collocated cells serve the same area and direction but are distinguished by the frequencies they utilize.
[0007] The expression “Fixed Wireless Access (FWA)” used hereinafter in the specification refers to a technology that provides internet connectivity to homes or businesses using wireless signals. In FWA, a fixed antenna or receiver is installed at the customer's location, communicating with a nearby wireless base station.
[0008] The expression ‘Xn interface’ used hereinafter in the specification refers to an interface that exists between the base stations viz. between Next Generation Node B (gNB)- Next Generation Node B (gNB), between Next Generation Node B (gNB)- Next Generation Evolved Node B (ng-eNB) and between Next Generation Evolved Node B (ng-eNB)- Next Generation Evolved Node B (ng-eNB). Xn is the network interface between Next Generation-Random Access Network (NG-RAN) nodes. Xn-U stands for Xn User Plane interface, and Xn-C stands for Xn Control Plane interface.
[0009] The expression ‘Xn application protocol (XnAP)’ used hereinafter in the specification refers to a control protocol used for communication and coordination between the gNBs, particularly for exchanging resource status updates and handover management. The XnAP enables the gNBs to perform load balancing and traffic distribution. The XnAP is used between the gNBs to support a variety of RAN related procedures, such as establishing dual connectivity, coordination of Xn based handovers, data forwarding and RAN Paging. During the handover process, the source gNB will provide the target gNB with all the necessary information it needs to handle the subscriber, including security and User Plane connectivity information. For dual connectivity, a master gNB may use the XnAP to set up a secondary gNB, with each gNB serving the user simultaneously.
[0010] The expression ‘resource status request/update’ used hereinafter in the specification refers to the signaling messages exchanged between the gNBs to request and provide updates on the current utilization of network resources. These messages contain various information elements, such as radio resource status and capacity indicators, to assist in load balancing decisions.
[0011] The expression ‘information elements (IEs)’ used hereinafter in the specification refers to specific data contained within signaling messages, such as Resource Status Updates. These elements include metrics like radio resource status, transport network layer (TNL) capacity indicator, composite available capacity, and others used to assess and manage the load between network units.
[0012] The expression ‘offloading’ used hereinafter in the specification refers to transferring the users or traffic from an overloaded cell to an available, less-loaded cell. This process helps balance network load and optimize the use of resources across multiple cells.
[0013] The expression ‘small cell’ used hereinafter in the specification refers to a low-power wireless access point within a larger cellular network. Small cells provide increased coverage and capacity in localized areas, improving the performance of high-frequency networks such as the FR2 in the 5G.
[0014] The expression ‘Composite Available Capacity’ used hereinafter in the specification refers to the total available network capacity across multiple slices, indicating the combined resource availability of the gNB or network unit to serve different user groups or applications.
[0015] The expression ‘transport network layer (TNL) Capacity Indicator’ used hereinafter in the specification refers to a metric that indicates the available capacity of the transport network, which connects the gNBs to the core network.
[0016] The expression ‘Slice Available Capacity’ used hereinafter in the specification refers to the available capacity for a specific network slice within the 5G network. Network slicing allows the allocation of dedicated resources for different services or users, and this term measures the available capacity for each slice.
[0017] The expression ‘radio resource control (RRC) connections’ used hereinafter in the specification refers to the signaling connections established between the User Equipment (UE) and the gNB. The RRC connections manage the radio resources, including handovers, bearer setup, and UE connectivity.
BACKGROUND
[0018] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0019] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog technology that offered only voice services. Further, when the second-generation (2G) technology was introduced, text messaging and data services became possible. The 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, improved network coverage, and security. Currently, the fifth-generation (5G) technology is being deployed, with even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. The sixth generation (6G) technology promises to build upon these advancements, pushing the boundaries of wireless communication even further. While the 5G technology is still being rolled out globally, research and development into the 6G are rapidly progressing, with the aim of revolutionizing the way we connect and interact with technology.
[0020] The use of smartphones and information and communication technologies is rapidly increasing, leading to a greater demand for mobile broadband services with higher data rates and improved quality of service (QoS). Small cells are essential for the 5G network, as they can support the predicted data demand and enhance network capacity. Small cells are low-power, cost-effective radio access points that cover small areas ranging from ten to several hundred meters. While the primary goal of small cells was to extend coverage within macro-cells, they can also be deployed in high-density configurations to increase the capacity of wireless networks significantly. As a result, small cells are expected to play a key role in future networks as they strive to meet the ever-increasing demand for data services.
[0021] The deployment of small cells, both residential and non-residential, is growing rapidly. Depending on the policy of the service provider, this deployment can either be planned or unplanned. Unlike macro networks, small cells are relatively low-cost and encourage subscribers to install them without network planning or specific configuration settings. As a result, a significant number of small cells in the network are randomly distributed. When the UEs move around in a small cell network with low service area cells, it can cause load imbalances across the cells in the network. This leads to degraded network performance in terms of capacity and handover success rate. Overloaded small cells can lead to poor QoS and increased handover failure rates when the UEs try to enter those cells even though lightly loaded neighboring cells are available. This can result in the unutilized resources of the lightly loaded cells, while some overloaded neighboring cells cannot meet the QoS requirements. Therefore, the network needs proper configuration and management mechanisms to improve QoS. Existing networks adjust system parameters manually to achieve high levels of operational performance. However, with the fast evolution of networks, such manual tuning is becoming increasingly difficult.
[0022] Self-organized networks (SONs) were introduced to decrease operational complexity by configuring, optimizing, and healing automatically in long-term evolution (LTE). The SONs are categorized into centralized, distributed, and hybrid. The SONs have several components, such as Mobility Load Balancing (MLB), Frequent Handover Mitigation (FHM), Mobility Robustness Optimization (MRO), and Interference Management (IM), which help small cells deliver carrier-grade performance.
[0023] The MLB distributes the load among small cells to enhance QoS and increase system capacity. It utilizes cell load information to optimize cell boundaries to offload the UEs. The SONs use mobility/handover parameters for load balancing. By adjusting the mobility parameters (i.e., handover parameters) according to their load statuses, the MLB distributes the load among the small cells. To shift candidate UEs, the cell individual offsets (CIO) of the serving and neighboring cells are adjusted based on reported measurements. However, improper handover decisions and offloading sequences for overloaded cells in the MLB cause inefficient resource usage or degrade service.
[0024] Existing approaches for load balancing in small cell networks often rely on static configurations or simple load-sharing mechanisms. These methods may not be sufficient to address the dynamic nature of traffic patterns and the varying demands of different user applications.
[0025] Hence, there is a need for a system and a method that can balance and distribute traffic in real-time among multiple cells.
SUMMARY OF THE DISCLOSURE
[0026] In an exemplary embodiment, the present disclosure relates to a system for performing load balancing over a plurality of units serving a plurality of cells in a network. The system includes a communication unit configured to establish a connection between a first unit serving a first cell (C1) and a second unit serving a second cell (C2), exchanging one or more requests between the first unit and the second unit over the established connection, a processing engine coupled to the communication unit and configured to derive load conditions of each of the second unit and the first unit based on the exchanged one or more requests, identify an unbalanced unit experiencing an unbalanced load and an available unit based on the derived load conditions, upon identifying the unbalanced load, select a number of inactive user equipments (UEs) connected with the unbalanced unit by determining at least one parameter associated with one or more UEs connected with the unbalanced unit and perform load balancing by initializing an offloading by redirecting the selected numbers of inactive UEs from the unbalanced unit towards the available unit
[0027] In an embodiment, the first unit and the second unit are connected via an Xn interface.
[0028] In an embodiment, the at least one resource status update is obtained from the first unit and the second unit, wherein the at least one resource status update includes a plurality of information elements (IEs).
[0029] In an embodiment, generate, by each of the first unit and the second unit, at least one resource status update by processing the exchanged at least one resource status request.
[0030] In an embodiment, the exchanged at least one resource status request includes at least one of an identification element, a registration request, report characteristics, a cell to report, and a reporting periodicity.
[0031] In an embodiment, the at least one parameter is an inactivity timer associated with each UE in the network.
[0032] In an embodiment, a radio resource control (RRC) transmits release request by the unbalanced unit to the selected user equipments (UEs) (104) upon selecting the one or more UEs (104).
[0033] In an embodiment, the RRC release request includes at least one absolute radio frequency channel number (ARFCN) of the available unit.
[0034] In an embodiment, the plurality of information elements (IEs) includes a radio resource status, a transport network layer (TNL) capacity indicator, a composite available capacity, a slice available capacity, a number of active UEs, and a number of RRC connections.
[0035] In an exemplary embodiment, the present disclosure relates to a method for performing load balancing over a plurality of units serving a plurality of cells in a network. The method comprising establishing, by a communication unit a connection between a first unit serving a first cell (C1) and a second unit serving a second cell (C2), exchanging by a communication unit, one or more requests between the first unit and the second unit over the established connection, deriving by a processing engine, load conditions of each of the first unit and the second unit based on the exchanged one or more requests, identifying by the processing engine, an unbalanced unit experiencing an unbalanced load, and an available unit based on the derived load conditions, upon identifying the unbalanced load, selecting by the processing engine, a number of inactive user equipments (UEs) connected with the unbalanced unit by determining at least one parameter associated with one or more UEs connected with the unbalanced unit and performing by the processing engine, load balancing by initializing an offloading by redirecting the selected numbers of inactive UEs from the unbalanced unit towards the available unit.
[0036] In an exemplary embodiment, the present disclosure relates to a user equipment (UE) communicatively coupled with a network. The coupling includes steps of establishing, by a communication unit a connection between a first unit serving a first cell (C1) and a second unit serving a second cell (C2), exchanging by a communication unit, one or more requests between the first unit and the second unit over the established connection, deriving by a processing engine, load conditions of each of the first unit and the second unit based on the exchanged one or more requests, identifying by the processing engine, an unbalanced unit experiencing an unbalanced load, and an available unit based on the derived load conditions, upon identifying the unbalanced load, selecting by the processing engine, a number of inactive user equipments (UEs) connected with the unbalanced unit by determining at least one parameter associated with one or more UEs connected with the unbalanced unit and performing by the processing engine, load balancing by initializing an offloading by redirecting the selected numbers of inactive UEs from the unbalanced unit towards the available unit.
[0037] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.
OBJECTIVES OF THE DISCLOSURE
[0038] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:
[0039] An objective of the present disclosure is to provide a system and a method for ensuring that traffic conditions are exchanged and balanced between a plurality of cells in real-time.
[0040] Another objective of the present disclosure is to provide the system and the method for providing load balancing that enhances communication network performance and improves inter-cell offloading.
[0041] Yet another objective of the present disclosure is to provide the system and the method for providing load balancing that supports rapidly changing traffic patterns and maximizes the utilization of radio resources.
[0042] Other objectives and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.
BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING
[0043] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0044] FIG. 1A illustrates an exemplary network architecture for implementing a system for performing load balancing over a plurality of units serving a plurality of cells in a network, in accordance with an embodiment of the present disclosure.
[0045] FIG. 1B illustrates an exemplary block diagram of the system for performing load balancing over the plurality of units serving the plurality of cells in the network, in accordance with an embodiment of the present disclosure.
[0046] FIG. 1C illustrates an exemplary network architecture of the system, in accordance with an embodiment of the present disclosure.
[0047] FIG. 2 illustrates an exemplary flow diagram for performing load balancing over the plurality of units serving the plurality of cells in the network, in accordance with an embodiment of the present disclosure.
[0048] FIG. 3 illustrates an exemplary flow diagram of a method for performing load balancing over the plurality of units serving the plurality of cells in the network, in accordance with an embodiment of the present disclosure.
[0049] FIG. 4 illustrates a computer system in which or with which the embodiments of the present disclosure may be implemented.
[0050] The foregoing shall be more apparent from the following detailed description of the disclosure.
LIST OF REFERENCE NUMERALS
100A - Network Architecture
102-1, 102-2…102-N – Plurality of Users
104-1, 104-2…104-N – Plurality of User Equipments
106 – Network
108 – System
100B - System architecture
122 - First Unit
124 - A Plurality of First Network Elements
126 - Second Unit
128 – A Plurality of Second Network Elements
100C – Block Diagram
110 – Processing Engine
112 - Memory
114 – Plurality of Interfaces
118 – Communication unit
120 – Database
200, 300 - Flow Diagram
400 - Computer System
410 - External Storage Device
420 - Bus
430 - Main Memory
440 - Read-Only Memory
450 - Mass Storage Device
460 - Communication Ports
470 – Processor
DETAILED DESCRIPTION
[0051] In the following description, for the purposes of explanation, various specific details are set forth to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
[0052] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0053] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail to avoid obscuring the embodiments.
[0054] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
[0055] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive like the term “comprising” as an open transition word without precluding any additional or other elements.
[0056] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0057] The terminology used herein is to describe embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a” “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.
[0058] As used herein, an “electronic device” or “portable electronic device” or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical, and computing device. The user device can receive and/or transmitting one or parameters, performing function/s, communicating with other user devices, and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery, and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
[0059] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.
[0060] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data transfer are also expected to evolve and replace the older generations of technologies. In the field of wireless data communications, the dynamic advancement of various generations of cellular technology are also seen. The development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G), and now sixth generation (6G) and more such generations are expected to continue in the forthcoming time.
[0061] Radio Access Technology (RAT) refers to the technology used by mobile devices/ user equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with base stations, which are responsible for providing the wireless connection. Further, each RAT has its own set of protocols and standards for communication, which define the frequency bands, modulation techniques, and other parameters used for transmitting and receiving data. Examples of RATs include GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System), LTE (Long-Term Evolution), and 5G. The choice of RAT depends on a variety of factors, including the network infrastructure, the available spectrum, and the mobile device's/device's capabilities. Mobile devices often support multiple RATs, allowing them to connect to several types of networks and provide optimal performance based on the available network resources.
[0062] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.
[0063] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog technology that offered only voice services. Further, when the second-generation (2G) technology was introduced, text messaging and data services became possible. The third-generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Currently, the fifth-generation (5G) technology is being deployed, with even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. The sixth generation (6G) technology promises to build upon these advancements, pushing the boundaries of wireless communication even further. While the 5G technology is still being rolled out globally, research and development into the 6G are rapidly progressing, with the aim of revolutionizing the way of connecting and interacting with technology.
[0064] With the development of heterogeneous networks, small cell is introduced into Long Term Evolution Advanced (LTE-A) networks to cater to various traffic demands from the user equipments (UEs). Due to the exponentially growing number of mobile users and nodes, current cellular systems require manual configuration and maintenance of small cells, which is expensive, time-consuming, and prone to error. This leads to the introduction of self-organizing capabilities for network management with minimum human involvement. Self-organized cellular networks incorporate a collection of functions for automatic configuration, optimization, and maintenance of cellular networks. As mobile end users continue to use network resources while moving from one cell boundary to another, traffic load within the single cell does not remain constant. To avoid the burden on the single cell in the network, load balancing was introduced, which involves the transfer of load from overloaded cells to the neighboring cells with free resources for more balanced load distribution to maintain appropriate end-user experience and network performance. However, the conventional load balancing schemes have become unsuitable due to the presence of small cells and multi-traffic UEs in the current LTE-A network. To address this issue of significant network capacity demand and shortage of spectrum resources, algorithms are being developed that reconfigure handover thresholds based on cell load. However, these algorithms are usually designed to handle a single traffic type and may not be efficient in scenarios where there is a non-uniform traffic distribution in small cells.
[0065] Effective management of resources and allocation based on real-time traffic is crucial in a multi-cell and multi-node architecture. Accordingly, there is a need for systems and methods that perform load balancing between a plurality of nodes. The present disclosure aims to address the issues mentioned above and other problems in this field of technology by performing load balancing in a network in real-time.
[0066] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
[0067] FIG. 1A illustrates an exemplary network architecture (100A) for implementing a system (108) for performing load balancing over a plurality of units serving a plurality of cells in a network (106), in accordance with an embodiment of the present disclosure.
[0068] As illustrated in FIG. 1A, the network architecture (100A) may include one or more user equipments (UEs) (104-1, 104-2…104-N) associated with one or more users (102-1, 102-2…102-N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2…102-N) may collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more UEs (104-1, 104-2…104-N) may be collectively referred to as the UE (104). Although only three UEs (104) are depicted in FIG. 1A, however, any number of the UE (104) may be included without departing from the scope of the ongoing description.
[0069] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, an Internet of Things (IoT) system. In such an embodiment, the UE (104) may include but is not limited to, smartphones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the users (102) and/or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE (104) may include, but is not limited to, intelligent, multi-sensing, network-connected devices, which may integrate seamlessly with each other and/or with a central server or a cloud-computing system or any other device that is network-connected.
[0070] Additionally, in some embodiments, the UE (104) may include, but not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and/or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE (104) may include, but is not limited to, any electrical, electronic, electromechanical, or equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein the UE (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or the entity such as touchpad, touch-enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.
[0071] Referring to FIG. 1A, the UE (104) may communicate with the system (108) through the network (106) to send or receive various types of data. In an embodiment, the network (106) may include at least one of a 5G network, 6G network, new generation radio access network (NG-RAN), or the like. The NG-RAN includes one or more NG-eNodeBs and gNodeBs. The eNodeB denotes a Long-Term Evolution (LTE) base station accessing the 5G core network, and the gNodeB denotes a 5G base station accessing the 5G core network. The NG-eNodeB and the gNodeB, or the two ng-eNodeBs, or the two gNodeBs communicate through an Xn interface. The Xn interface may also be referred to as the XnAP interface. The network (106) may enable the UE (104) to communicate with other devices in the network architecture (100A) and/or with the system (108). The network (106) may include a wireless card or another transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.
[0072] In an embodiment, the network (106) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network (106) may also include, by way of example but not limitation, one or more of a radio access network (RAN), a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.
[0073] In an embodiment, the UE (104) is communicatively coupled with the network (106). The network (106) may receive a connection request from the UE (104). The network (106) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request.
[0074] Although FIG. 1A shows exemplary components of the network architecture (100A), in other embodiments, the network architecture (100A) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1A. Additionally, or alternatively, one or more components of the network architecture (100A) may perform functions described as being performed by one or more other components of the network architecture (100A).
[0075] FIG. 1B illustrates an exemplary system architecture (100B) for performing load balancing over the plurality of units serving the plurality of cells in the network (106), in accordance with an embodiment of the present disclosure. In the network, a cell refers to a specific geographic area served by a base station (such as a gNB) that provides wireless communication coverage. Each cell typically operates on a distinct set of frequencies and can handle a certain number of users and data traffic. The plurality of cells allows for efficient frequency reuse and enables mobile devices to connect to the network while on the move. In 5G networks, the plurality of cells may vary in size and type, including macro cells for wide coverage and small cells for dense urban areas, each designed to optimize connectivity, capacity, and performance based on user demand and environmental conditions.
[0076] Referring to FIG. 1B, the system (108) includes a first unit (122) and a second unit (126). In an aspect, the system (108) includes the plurality of units (122, 126). However, only two units (the first unit (122) and the second unit (126)) are shown in FIG. 1B for the sake of brevity.
[0077] In an aspect, the first unit (122) and the second unit (126) is a next-generation NodeB (gNB) or an outdoor small cell (ODSC). For example, the first unit (122) and the second unit (126) is a 5G mm wave ODSC. The ODSC is configured to provide enhanced throughput. In an embodiment, each of the first unit (122) and the second unit (126) comprises a central unit (CU), a distributed unit (DU), a remote unit (RU), a memory module, a processing module, and a communication unit. The central unit (CU) performs higher-layer control and management functions. The distributed unit (DU) is responsible for real-time processing and coordination with the remote unit (RU), which handles the radio access interface with the UE (104). The memory module stores operational data and software, the processing module executes computational tasks required for network operations, and the communication unit facilitates communication between network elements and external networks.
[0078] The RU is a radio hardware unit that converts radio signals sent to and from the communication unit (antenna) into a digital signal for transmission over packet networks. The RU incorporates a digital front end, which is responsible for the conversion of analog RF signals into digital signals and vice versa. This functionality ensures accurate signal processing and efficient data handling within the digital domain. The RU manages the lower layers of the physical layer (PHY) of the communication protocol stack. This includes the essential processes for modulation and demodulation of signals, as well as error correction and synchronization, thereby facilitating robust and reliable wireless communication. The RU is equipped with digital beamforming capabilities, which involve the manipulation of digital signal processing techniques to direct and shape the radio beams transmitted and received by the antenna.
[0079] The DU is deployed close to the RU on-site and is configured to handle the Radio Link Control (RLC) layer, the Medium Access Control (MAC) layer, and portions of the Physical (PHY) layer. The DU is equipped to support measurement operations for connected and active UE, enabling accurate assessment of radio conditions and network performance. Furthermore, the DU is designed to facilitate the handover procedure, ensuring a seamless transition of the UE (104) connectivity between different cells or sectors and to manage the Radio Resource Control (RRC) release procedure to steer traffic and optimize resource allocation effectively.
[0080] The CU further includes RRC, service data adaption protocol (SDAP), and protocol description control protocol (PDCP protocol) layers and is configured to provide non-real-time RRC and PDCP protocol stack functions. The SDAP layer is configured to manage Quality of Service (QoS) and service data adaptation. The PDCP layer handles data compression, encryption, and packet reordering. In one aspect, the CU is configured to enable the XnAP interface, relevant procedures, and at least one (static) NRT framework. The CU is configured to support elementary procedure messages with all supported IEs (resource status request, resource status response, resource status failure, and resource status update). The resource status request allows network elements, like gNodeBs, to query the availability of specific resources. The resource status response provides detailed information about resource status, including utilization rates and availability timelines. In cases where resource information cannot be retrieved, the resource status failure message communicates the failure, offering error codes and reasons for the unavailability. Additionally, the resource status update serves as a notification mechanism, informing stakeholders of any changes in resource status in real time. In addition, the CU is configured to support the handover procedure for blind handover and support counters and alarms for Xn connection loss. Furthermore, the CU is configured to perform load condition evaluation, UE selection traffic steering decision, and the RRC support for release message generation with redirect carrier information.
[0081] In an aspect, the system (108) is configured to provide enhanced support for operation and management (OAM) by offering advanced configuration and management capabilities. The system (108) facilitates gNB pairing options and configuration support for collocated small cells (ODSCs) and manages the Xn connections, ensuring efficient integration and communication between a plurality of first network elements (124) and a plurality of second network elements (128). The system (108) also manages the neighbor relation table (NRT), which is essential for maintaining seamless connectivity between cells. The NRT is a data structure used in mobile networks to store information about neighboring cell towers (such as gNodeBs or eNodeBs). The NRT includes details like neighbor cell identifiers, signal strength metrics, handover parameters, load information, and cell types. The NRT facilitates efficient handover management and supports network optimization by providing real-time data on neighboring cell conditions. The system (108) also allows operators to enable or disable configurable parameters and timers related to load balancing, offering flexibility in network management. Moreover, the system (108) supports relevant counters and alarms, enabling real-time monitoring of network performance and alerting operators to potential issues. These features collectively enhance OAM by providing improved control, operational efficiency, and proactive management of network resources.
[0082] The first unit (122) is configured to serve a first cell C1. As shown in FIG. 1, the first unit (122) is configured to connect with a plurality of first network elements (124) in the first cell C1.
[0083] The second unit (126) is configured to serve a second cell C2. As shown in FIG. 1B, the second unit (126) is configured to connect with a plurality of second network elements (128) in the second cell C2.
[0084] In an example, the plurality of network elements (including the plurality of first and second network elements (124, 128)) is a logical entity or a physical entity within the network that is being managed or controlled. For example, the logical entity may include network functions virtualization (NFV) components. On the other hand, the physical entity may include tangible devices such as base stations (e.g., gNB in 5G networks or eNodeB in LTE), routers, switches, and data centers. These physical components are directly involved in the transmission, routing, and processing of data across the network. The plurality of first and second network elements (124, 128) is preferably designed with built-in instrumentation, which allows for the collection of relevant information, which is subsequently used to determine control actions to be applied to the plurality of first and second network elements (124, 128). In the system (108) of FIG. 1B, the plurality of first and second network elements (124, 128) is any hardware or software component that has a measurable parameter that can be reported. Examples of the plurality of first and second network elements (124, 128) include routers, switches, hosts, modems, terminals, dial access servers, gateways, ports, channels, interfaces, circuits, processes, drivers, protocols, services, applications, etc. In an aspect of the present disclosure, the plurality of first and second network elements (124, 128) is customer premises equipment (CPE). The CPE refers to the hardware and devices located at the end user’s location, which are used to connect to a service provider's network. The CPE enables communication between the user network and the service provider network. The CPE facilitates connectivity and access to the network services offered by the service provider. By interfacing with the service provider’s network, CPE facilitates the delivery of internet, voice, and video services, supporting the connectivity and operation of user devices within the premises.
[0085] The first unit (122) and the second unit (126) are configured to send a connection establishment request to each other over a network. In an aspect, the network includes a plurality of cells (C1, C2). In an aspect, the network is a 5G cloud RAN, a next generation RAN (NG-RAN), long-term evolution (LTE) RAN, a cellular network, a wireless local area network (WLAN), etc.).
[0086] In an operative aspect, to perform load balancing between two collocated ODSCs (the first unit (122) and the second unit (126)), during initial deployment/integration, the two collocated ODSCs are coupled with each other to establish Xn connectivity by performing Class-1 elementary XnAP procedure.
[0087] To perform the load balancing feature on both ODSCs, a resource status reporting initiation (Class-1 elementary XnAP procedure) is configured. The XnAP is a control protocol used between gNBs to support a variety of RAN-related procedures, such as establishing dual connectivity, coordination of Xn-based handovers, data forwarding, and RAN paging.
[0088] The first unit (122) and the second unit (126) are configured to exchange at least one resource status request with each other. Each unit (the first unit (122) and the second unit (126)) is configured to receive and process the received at least one resource status request. For example, the first unit (122) is configured to transmit the resource status request to the second unit (126). In an example, the resource status request includes various information such as an identification element, including an id-NGRAN-Node1-Measurement-ID, an id-NGRAN-Node2-Measurement-ID, a registration request, report characteristics, a cell to report, a reporting periodicity, etc.
[0089] The second unit (126) is configured to receive and process at least one resource status request. After processing the received resource status request, the second unit (126) is configured to generate a resource status response. In an example, the resource status response may include id-NGRAN-Node1-Measurement-ID and id-NGRAN-Node2-Measurement-ID. For example, in ‘resource status response,’ the XnAP message(s) is exchanged to pair both nodes.
[0090] Both paired ODSCs (the first unit (122) and the second unit (126)) are configured to start sharing status reporting with each other using at least one resource status update. In an exemplary aspect, the second unit (126) is configured to transmit the at least one resource status update to the first unit (122). The resource status update includes a plurality of information elements (IEs), as shown in Table 1. In an example, the plurality of information elements (cell measurement result) includes a radio resource status, a transport network layer (TNL) capacity indicator, a composite available capacity group, a slice available capacity, a number of the UEs (104) that are active, and a number of the RRC connections. The resource status refers to the current state of available radio resources for user connections, including metrics on bandwidth, signal quality, and capacity, which are crucial for managing network performance. The TNL capacity indicator assesses the available capacity in the transport layer that supports data transmission between the core network and base stations, ensuring efficient data flow. The slice available capacity pertains to the resources allocated to a specific network slice, which is a tailored virtual network segment designed to meet the requirements of different services or applications. The number of active UEs indicates how many devices are currently connected and using the network, providing insights into demand and usage patterns. The number of RRC connections reflects the count of established RRC connections, which are critical for managing communication between UEs (104) and the network, including signaling for connection establishment, maintenance, and release. Together, these metrics help network operators monitor and optimize resource allocation, ensuring reliable service delivery in a dynamic environment.
[0091] In an aspect, the system (108) considers only the number of active UEs (104) and the RRC connections to maintain UE distribution.
Table 1: Cell measurement results
IE Name Description
Radio Resource Status Indicates DL and UL Physical Resource Block (PRB) Usage per SSB beam
TNL Capacity indicator Indicates DL and UL Tunnel offered and available capacity
Composite Available Capacity Indicates the number of resources per cell and SSB area that are available relative to the total NG-RAN resources

Slice Available Capacity Indicates the number of resources per network slice that are available per cell

Number of Active UEs Indicates the mean number of active UEs
RRC Connections Indicates the overall status of RRC connections per cell
[0092] The first unit (122) and the second unit (126) are configured to monitor their resource usage and compare it with the resource usage of a corresponding paired ODSC. The difference (delta) between the resource utilization of each unit and the paired ODSC is calculated. The first unit (122) and the second unit (126) are configured to identify an unbalanced unit (or an unbalanced cell) experiencing an unbalanced load and an available unit based on the plurality of IEs. The first unit (122) and the second unit (126) are configured to compare the number of active UEs and the number of RRC connections with a predefined threshold value fetched from the memory (112). In an aspect, the first unit (122) and the second unit (126) are configured to use one or multiple combinations of available information elements from Table 1 by actively monitoring for detecting overload conditions and offloading UEs to paired gNB (units).
[0093] After identifying the unbalanced unit, the system (108) is configured to initialize an offloading from the unbalanced unit toward the available unit. The offloading includes load balancing handover without measuring the target available unit.
[0094] The system (108) determines inactivity by monitoring various network parameters associated with the UE (104) connected to the unbalanced unit. The system (108) may track key indicators such as the absence of data transmission or reception over a predefined period, which suggests the UE (104) is no longer actively engaged. The system (108) may determine the UE inactivity based on several factors. One key indicator is the absence of data transmission between the UE (104) and the network (106) over a specified period. Additionally, the transition of the UE (104) from active to idle mode suggests reduced activity. Another factor is session timeout, where the session timers expire without further communication from the UE (104). Finally, the system (108) monitors signalling activity and a noticeable reduction or absence of signaling messages can indicate inactivity. These factors may enable the system (108) to detect inactivity and optimize network resource usage effectively. The system (108) is configured to provide minimal impact on user experience as the lossless transition of the UEs (104) is achieved. Further, the system (108), having the load balancing handover approach, is configured to minimize data interruption time and achieve controlled transition with the help of carrier aggregation control (CAC) functionality to prevent over-utilization.
[0095] FIG. 1C illustrates an exemplary block diagram (100C) of the system (108) for performing load balancing over the plurality of units serving the plurality of cells in the network (106), in accordance with an embodiment of the present disclosure.
[0096] Referring to FIG. 1C, in an embodiment, the system (108) may include a processing engine (110), a memory (112), a plurality of interface(s) (114), a communication unit (118), and a database (120).
[0097] In an embodiment, the interface(s) (114) may include a variety of interfaces, for example, interfaces for data input and output devices (I/O), storage devices, and the like. The interface(s) (114) may facilitate communication through the system (108). The interface(s) (114) may also provide a communication pathway for one or more components of the system (108). Examples of such components include, but are not limited to, the processing engine (110) and the database (120).
[0098] The processing engine (110) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine (110). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine (110) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine (110) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine (110). In such examples, the system (108) may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (108) and the processing resource. In other examples, the processing engine (110) may be implemented by electronic circuitry. In an embodiment, the database (120) includes data that may be either stored or generated as a result of functionalities implemented by the processing engine (110).
[0099] In an embodiment, the receiving unit (116) is configured to receive a first connection establishment request from the first unit (122) via signalling protocols such as the Xn application protocol (XnAP). The Xn interface XnAP procedures are divided into two modules as follows:
1. XnAP Basic Mobility Procedures module; and
2. XnAP Global Procedures module.
[00100] The XnAP Basic Mobility Procedures module contains procedures used to handle UE mobility within NG-RAN. The Global Procedures module contains procedures that are not related to a specific UE. These procedures are in contrast to the procedures in the XnAP Basic Mobility Procedures based module, which involves two peer NG-RAN nodes.
[00101] In an embodiment, the memory (112) is configured to store the received data (requests). The memory (112) is configured to store the predefined threshold value. The program instructions include a program that implements a method for providing load balancing between the plurality of cells in real time, in accordance with embodiments of the present disclosure and may implement other embodiments described in this specification. The memory (112) may include any non-transitory storage device including, for example, volatile memory such as random-access memory (RAM), or non-volatile memory such as erasable programmable read only memory (EPROM), flash memory, and the like.
[00102] In an embodiment, the processing engine (110) is configured to fetch and execute computer-readable instructions stored in the memory (112). The processing engine (110) is configured to execute a sequence of instructions of the method to provide load balancing between the plurality of cells, embodied in a program or software. The instructions can be directed to the processing engine (110), which may subsequently program or otherwise be configured to implement the methods of the present disclosure. In some examples, the processing engine (110) is configured to control and/or communicate with large databases, perform high-volume transaction processing, and generate reports from large databases. The processing engine (110) is implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions.
[00103] In an embodiment, the communication unit (118) is configured to provide a connectivity between various units serving different cells. The communication unit (118) is configured to provide the connectivity between the first unit (122) and the second unit (126) and the plurality of first and second network elements (124, 128). The communication unit (118) has at least one antenna for transmitting and receiving signals/packets. In some examples, at least one antenna is a near-field antenna, a WiFi antenna, and a radio frequency antenna. The communication unit (118) may include a wireless-frequency transceiver having a variable gain amplifier that generates radio-frequency signals for transmission. A wireless amplifier circuit is used to amplify the radio-frequency signals at the output of the variable gain amplifier for transmission through a plurality of antennas. In an aspect, the first unit (122) and the second unit (126) are connected via the XN interface. The Xn interface is a standardized protocol used in modern 4G and 5G networks to facilitate inter-gNB communication and enables the exchange of resource information between units. The Xn interface allows for coordination between the first unit (122) and the second unit (126), enabling the first unit (122) and the second unit (126) to share relevant data, such as load conditions and resource updates, which is crucial for performing load balancing effectively.
[00104] In an embodiment, the communication unit (118) is configured to exchange, by the first unit (122) and the second unit (126), one or more requests with each other. Once the first unit (122) and the second unit (126) are connected, the processing engine (110) facilitates the exchange of the one or more requests between the first and the second units (122, 126). The one or more requests request comprises critical information elements such as the identification element, reporting characteristics, and the reporting periodicity. The identification element refers to a unique identifier used to distinguish the source unit sending the one or more requests, ensuring accurate tracking of the origin of the one or more requests within the network (106). Reporting characteristics define the specific type and granularity of the information being reported, such as the type of resources, thresholds, or performance metrics relevant to the load balancing process. The reporting periodicity specifies the frequency at which resource status updates are sent between units, ensuring timely monitoring and adjustment of load conditions to maintain optimal performance. The one or more requests help both the first unit (122), and the second unit (126) assess operational status, resource availability, and current load conditions. In an aspect, the system (108) is configured to obtain at least one resource status update from both the first unit (122) and the second unit (126). The at least one resource status update may include detailed information about the current resource utilization, available capacity, and other performance indicators. The at least one resource status update is critical for load balancing function of the system (108), as it provide real-time insights into the operational status of each unit, helping the system (108) to decide when and how to offload the UEs (104) effectively.
[00105] In an embodiment, the processing engine (110) is configured to derive load conditions of each of the second unit (126) and the first unit (122) based on the exchanged data. After receiving information via the communication link, the processing engine (110) processes resource status updates and analyzes the load distribution across the first unit (122) and the second unit (126). The derived load conditions may include details about resource utilization, traffic congestion, and the availability of network resources such as spectrum and processing capacity. By interpreting this data, the system (108) can determine the relative load on the first unit (122) and the second unit (126) and use this information to optimize the distribution of the UEs (104) across cells. The processing includes analyzing the current network load, resource availability, and active connections. This processing enables both the first unit (122) and the second unit (126) to understand the load conditions of each other, paving the way for the decision-making process regarding load balancing. In an aspect, the processing engine (110) is configured to generate at least one resource status update by processing the exchanged at least one resource status request. Each of the first unit (122) and the second unit (126) periodically generates and sends its resource status update in response to a resource status request from the other unit. This information exchange allows for continuous monitoring of network conditions, ensuring that the load balancing decisions are made based on up-to-date data. In an aspect, the resource status request includes at least one of the identification element, the registration request, the report characteristics, the cell to report, and the reporting periodicity. These elements define the specific parameters for the resource status updates, including which resources should be reported, the frequency of reports, and any relevant identification or registration data needed for communication between units. In an example, consider the first unit (122), which handles traffic for a local area network. Over a 10-minute period, the total data transmitted is 120 MB, resulting in an average data rate of approximately 200 KB/s. The first unit (122) processes about 10,000 packets, averaging 16.67 packets per second. Resource utilization shows a CPU usage of 75% and memory utilization at 75% of its 8 GB capacity, indicating the first unit (122) is nearing its limits. At peak, there are 150 active connections, close to its maximum capacity of around 200 connections. Additionally, the average response time for requests is 200 milliseconds. This data suggests that while the first unit (122) managing a moderate load, it is approaching critical thresholds, and continuous monitoring is essential to ensure optimal performance and to determine when scaling or optimization may be necessary.
[00106] In an aspect, the first unit (122) and the second unit (126) (referred to as nodes) are configured to activate the load balancing function, which shall trigger Resource Status Reporting Initiation after both cells are up. ‘Resource Status Request’ followed by ‘Resource Status Response’ XnAP messages exchanged to pair both nodes.
[00107] In an aspect, in the Resource Status Reporting Initiation, the first unit (122) (For example, NG-RAN node1) initiates the procedure by sending the RESOURCE STATUS REQUEST message to the second unit (126) (For example, NG-RAN node2) to start a measurement, stop a measurement or add cells to report for a measurement. Upon receipt, NG-RAN node2:
• shall initiate the requested measurement according to the parameters given in the request in case the Registration Request IE set to "start"; or
• shall stop all cells measurements and terminate the reporting in case the Registration Request IE is set to "stop"; or
• shall add cells indicated in the Cell To Report List IE to the measurements initiated before for the given measurement IDs, in case the Registration Request IE is set to "add". If measurements are already initiated for a cell indicated in the Cell To Report List IE, this information shall be ignored.
If the Registration Request IE is set to "start" in the RESOURCE STATUS REQUEST message and the Report Characteristics IE indicates cell specific measurements, the Cell To Report List IE shall be included.
If Registration Request IE is set to "add" in the RESOURCE STATUS REQUEST message, the Cell To Report List IE shall be included.
If NG-RAN node2 is capable to provide all requested resource status information, it shall initiate the measurement as requested by NG-RAN node1 and respond with the RESOURCE STATUS RESPONSE message.
[00108] Once paired both nodes shall start sharing status reporting using ‘Resource Status Update’ each other. This exchange can be done with predefined periodicity. NG-RAN node2 shall report the results of the admitted measurements in RESOURCE STATUS UPDATE message. The admitted measurements are the measurements that were successfully initiated during the preceding Resource Status Reporting Initiation procedure (procedure is initiated by an NG-RAN node to report the result of measurements admitted by the NG-RAN node following a successful Resource Status Reporting Initiation procedure).
[00109] Both nodes may use all available IEs for exchanging and deriving load conditions of each other. Available options are Radio Resource Status, TNL Capacity Indicator, Composite Available Capacity, Slice Available Capacity, Number of Active UEs, and RRC Connections.
[00110] When starting a measurement, the Report Characteristics IE in the RESOURCE STATUS REQUEST indicates the type of objects NG-RAN node2 shall perform measurements on. For each cell, NG-RAN node2 shall include in the RESOURCE STATUS UPDATE message:
• the Radio Resource Status IE, if the first bit, "PRB Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to "1". If NG-RAN node2 is a gNB and if the cell for which Radio Resource Status IE is requested to be reported supports more than one SSB, the Radio Resource Status IE for such cell shall include the SSB Area Radio Resource Status Item IE for all SSB areas supported by the cell. If the SSB To Report List IE is included for a cell, the Radio Resource Status IE for such cell shall include the requested SSB Area Radio Resource Status List IE; If the cell for which Radio Resource Status IE is requested to be reported supports more than one slice, and if the Slice To Report List IE is included for a cell, the Radio Resource Status IE for such cell shall, if supported, include the requested Slice Radio Resource Status Item IE;
• the TNL Capacity Indicator IE, if the second bit, "TNL Capacity Ind Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to "1". The received TNL Capacity Indicator IE represents the lowest TNL capacity available for the cell, only taking into account interfaces providing user plane transport;
• the Composite Available Capacity Group IE, if the third bit, "Composite Available Capacity Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to "1". If the Cell Capacity Class Value IE is included within the Composite Available Capacity Group IE, this IE is used to assign weights to the available capacity indicated in the Capacity Value IE. If NG-RAN node2 is a gNB and if the cell for which Composite Available Capacity Group IE is requested to be reported supports more than one SSB, the Composite Available Capacity Group IE for such cell shall include the SSB Area Capacity Value List for all SSB areas supported by the cell, providing the SSB area capacity with respect to the Cell Capacity Class Value. If the SSB To Report List IE is included for a cell, the Composite Available Capacity Group IE for such cell shall include the requested SSB Area Capacity Value List IE.
• If the cell for which Composite Available Capacity Group IE is requested to be reported supports more than one slice, and if the Slice To Report List IE is included for a cell, the Slice Available Capacity IE for such cell shall include the requested Slice Available Capacity Value Downlink IE and Slice Available Capacity Value Uplink IE, providing the slice capacity with respect to the Cell Capacity Class Value.
• the Number of Active UEs IE, if the fourth bit, "Number of Active UEs" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to "1";
• the RRC Connections IE, if the fifth bit, "RRC Connections" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to "1".
• the NR-U Channel List IE, if the sixth bit, "NR-U Channel List" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to "1".
[00111] If the Reporting Periodicity IE in the RESOURCE STATUS REQUEST is present, this indicates the periodicity for the reporting of periodic measurements. the NG-RAN node2 shall report only once, unless otherwise requested within the Reporting Periodicity IE.
[00112] In an embodiment, the processing engine (110) is configured to identify an unbalanced unit experiencing an unbalanced load and an available unit based on the derived load conditions. The system (108) compares the load conditions of both the first unit (122) and the second unit (126), determining which unit is overloaded and which unit has available resources. This identification process is crucial for triggering the load balancing mechanism. The ability to differentiate between the unbalanced unit (which may be experiencing congestion or over-utilization) and the available unit (which has spare capacity) allows the system (108) to make targeted and efficient offloading decisions.
[00113] In an aspect, the processing engine (110) monitors the load conditions of various units within the network. The processing engine (110) detects that the first unit (122) has a CPU usage of 90% and memory utilization of 85%, indicating the first unit (122) is operating under a heavy load. The second unit (126) shows a CPU usage of only 40% and memory utilization of 30%, signifying that it has significant available resources. Upon analyzing these conditions, the processing engine identifies the first unit (122) as the unbalanced unit due to its high resource consumption, which suggests it may be experiencing congestion or over-utilization. Conversely, the second unit (126) is recognized as the available unit, as the second unit (126) has a large capacity to accommodate additional tasks.
[00114] In an aspect, the processing engine (110) is configured to select a number of inactive user equipments (UEs) connected with the unbalanced unit by determining at least one parameter associated with each UE (104) connected to it. The processing engine (110) may use various parameters, such as inactivity timers, data transfer rates, or session durations, to identify the number of inactive UEs. Each UE (104) has an associated inactivity timer that tracks the duration of inactivity since its last data transmission or interaction with the network. By setting a predefined threshold, the processing engine may flag UEs that have exceeded this limit, indicating they have not engaged in any active sessions for a certain period. This helps prioritize which of the UEs (104) are most suitable for offloading. The processing engine monitors the data transfer rates of connected UEs. The UEs (104) experiencing very low or negligible data transfer rates can be classified as inactive. By assessing the average data rates over a specific time frame, the system (108) can identify the UEs (104) that are not contributing significantly to the network load. The duration of active sessions for each UE is another important parameter. The UEs (104) that have been in a session for a short time or have recently completed their data sessions may indicate lower engagement with the network. By analyzing session durations, the processing engine can pinpoint the UEs (104) that are less active and, therefore, more suitable for load redistribution. By integrating these parameters, the processing engine can create a comprehensive profile of each of the UEs (104) activity levels. The UEs (104) that have remained idle for a specific period demonstrated low data transfer rates or have short session durations are identified as prime candidates for load redistribution. This method ensures that the load balancing mechanism selectively targets the UEs (104) with minimal impact on overall network performance, preserving the quality of service for users engaged in high-demand activities.
[00115] In an overall aspect the UEs (104) idle for a certain period or consuming minimal resources become candidates for load redistribution. This selective process ensures that the load balancing mechanism does not affect active users with ongoing high-demand sessions but focuses on redirecting the UEs (104), which will have minimal impact on the user experience. In an aspect, the inactivity timer in the network (106) is one of the parameters used to identify the number of inactive UEs. The inactivity timer measures the period of inactivity for each UE (104), and the UEs (104) that have been inactive for a predefined duration can be flagged for offloading. This ensures that the processing engine (110) prioritizes the UEs (104) with lower resource demands when redistributing load, thus minimizing the impact on active users.
[00116] In an aspect, the processing engine (110) is configured to perform load balancing by initializing an offloading process to redirect the selected number of inactive UEs from the unbalanced unit toward the available unit. This process involves the reallocation of radio resources for the selected UEs, essentially steering them from the overburdened unit to a unit with greater capacity. The offloading can be performed seamlessly, with minimal interruption to the network connections of the UE (104). By redistributing the UEs (104) to the available unit, the processing engine (110) optimizes the load across the network, ensuring that no single unit is overwhelmed, thus maintaining high-quality service and network efficiency.
[00117] FIG. 2 illustrates an exemplary flow diagram (200) for providing load balancing between the plurality of units, in accordance with an embodiment of the present disclosure. In an example, FIG. 2 illustrates a method (200) for providing load balancing between two units for the sake of brevity.
[00118] Step (202) includes sending, by the first unit (122) serving the first cell, the connection establishment request to the second unit (126) serving the second cell. In an example, the first unit (122) is a next-generation NodeB (gNB)or an outdoor small cell-1 (ODSC-1) (as shown in FIG. 2). In an example, the second unit (126) is a next-generation NodeB (gNB), or an outdoor small cell -2 (ODSC-2). In an aspect, the first unit (122) and the second unit (126) are connected via the Xn connection (Xn is a network interface between NG-RAN nodes).
[00119] Step (204) includes exchanging the at least one resource status request with each other. During step (204), the first unit (122) transmits the at least one resource status request to the second unit (126). In an aspect, step (204) includes receiving and processing the at least one received resource status request.
[00120] Step (206) includes transmitting, by the second unit (126), the at least one resource status response to the first unit (122). In an example, the resource status response may include id-NGRAN-Node1-Measurement-ID and id-NGRAN-Node2-Measurement-ID.
[00121] Step (208) includes transmitting, by the second unit (126), the at least one resource status update. In an aspect, the at least one resource status update includes a plurality of information elements (IEs). In an example, the plurality of information elements (cell measurement result) includes the radio resource status, the transport network layer (TNL) capacity indicator, the composite available capacity group, the slice available capacity, the number of active UEs, and the number of RRC connections.
[00122] In an aspect, the first unit (122) and the second unit (126) are configured to exchange the at least one resource status update after a predefined time. For example, the predefined time is 10 seconds.
[00123] In an aspect, each of the first unit (122) and the second unit (126) is configured to estimate load conditions of each other based on the received plurality of information elements (IEs).
[00124] Step (210) includes transmitting, by the first unit (122), the at least one resource status update to the second unit (126).
[00125] Step (212) includes transmitting the at least one resource status update to the first unit (122) by the second unit (126).
[00126] Step (214) includes transmitting, by the first unit (122), the at least one resource status request to the second unit (126).
[00127] After analyzing the received at least one resource status update, the first unit (122) and the second unit (126) are configured to identify an unbalanced unit experiencing an unbalanced load and an available unit.
[00128] After identifying the unbalanced unit, step (216) includes initializing offloading from the unbalanced unit towards the available unit. In an aspect, the offloading includes load balancing handover without measuring the target available unit. For example, as shown in FIG. 2, it is found that the first unit (122) is unbalanced, then the upcoming network join request will be diverted to the second unit (126).
[00129] Step (218) includes transmitting a radio resource control (RRC) release request having an absolute radio frequency channel number (ARFCN) of the at least one available unit to the number of inactive user equipments (UEs). The ARFCN is a unique identifier used in mobile communication systems, particularly in GSM (Global System for Mobile Communications) and UMTS (Universal Mobile Telecommunications System), to specify radio frequency channels. Each ARFCN corresponds to a specific frequency used by the available unit for communication between mobile devices and base stations. As shown in FIG. 2, the RRC Release request with ARFCN is transmitted by the first unit (122) towards the inactive UEs to join network element (CPE 2) of the second unit (126) (ODSC- 2).
[00130] FIG. 3 illustrates another exemplary flow diagram of the method (300) for performing load balancing over the plurality of units serving the plurality of cells in the network (106), in accordance with an embodiment of the present disclosure.
[00131] At step 302, the method (300) includes establishing a communication link between the first unit (122) and the second unit (126). This communication link enables the exchange of information and coordination between the first unit (122) and the second unit (126) for effective load balancing. The communication link ensures the first unit (122), and the second unit (126) can share their respective load and resource statuses, facilitating real-time decision-making. In an embodiment, the first unit (122) and the second unit (126) are connected via the Xn interface. The Xn is a standard interface for signaling and data exchange between the plurality of first and second network elements (124, 128) in 5G and other cellular systems.
[00132] At step 304, the method (300) includes exchanging the one or more requests between the first unit (122) and the second unit (126) over the established communication link. The one or more requests may include data such as resource status updates, current load information, or other operational data that the first unit (122) and the second unit (126) require to make informed decisions about load management. By continuously sharing this information, the method (300) keeps each unit updated on the state of each other, ensuring that any load imbalances can be identified and addressed promptly. In an aspect, the exchange involves sending requests with key network parameters, such as identification elements, report characteristics, and reporting periodicity. This information allows the first and second units (122, 126) to determine their current operational state, including available resources and network load conditions.
[00133] At step 306, the method (300) includes deriving load conditions of both the first unit (122) and the second unit (126) based on the information exchanged via the communication link by the processing engine (110). The processing involves evaluating the current load and resource availability of the network (106). By examining metrics like resource utilization and traffic patterns, the processing engine can determine whether any imbalances exist in the load distribution between the two units.
[00134] At step 308, the method (300) includes identifying the unbalanced unit that is experiencing an unbalanced load and the available unit with spare capacity, based on the derived load conditions. This identification process involves comparing the load conditions of both the first unit (122) and the second unit (126) to evaluate which unit between the first unit (122) and the second unit (126) is overburdened and which has enough capacity to accommodate additional traffic, enabling the method (300) to initiate load-balancing measures. The method (300) is configured to transmit, by the first unit (122) and the second unit (126), at least one resource status update based on the processed at least one resource status request. The at least one resource status update includes a plurality of information elements (IEs). Following the processing of resource status requests, the first unit (122) and the second unit (126) send resource status updates that contain detailed network metrics. These updates include IEs such as radio resource status, TNL capacity indicator, composite available capacity group, slice available capacity, number of active UEs, and RRC connections. These IEs give a clear picture of the load conditions on the first unit (122) and the second unit (126), which will later be used to determine if load balancing is necessary.
[00135] At step 310, the method (300) includes selecting upon identifying the unbalanced load, a number of inactive user equipments (UEs) connected with the unbalanced unit by determining at least one parameter associated with each of the UE (104) connected with the unbalanced unit. To determine which of the UEs (104) are suitable for offloading, the method (300) may analyze certain parameters such as inactivity timers, data transfer rates, or other relevant criteria that indicate the level of activity of the UE (104). The UEs (104) that have been inactive for a specific duration, as measured by the inactivity timer, may be prime candidates for being redirected to the available unit to alleviate the load on the unbalanced unit.
[00136] At step 312, the method (300) includes performing load balancing by initializing an offloading process to redirect the selected inactive UEs from the unbalanced unit to the available unit. This step involves updating the radio resource configurations of the UE (104) to facilitate their seamless transition to the available unit. By redirecting the UEs (104), the method (300) ensures that the unbalanced unit's load is reduced, preventing performance degradation while maximizing the efficiency of the available unit.
[00137] FIG. 4 illustrates a computer system (400) in which or with which the embodiments of the present disclosure may be implemented.
[00138] As shown in FIG. 4, the computer system (400) may include an external storage device (410), a bus (420), a main memory (430), a read-only memory (440), a mass storage device (450), communication port(s) (460), and a processor (470). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (470) may include various modules associated with embodiments of the present disclosure. The communication port(s) (460) may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) (460) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.
[00139] The main memory (430) may be random access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (440) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input/Output System (BIOS) instructions for the processor (470). The mass storage device (450) may be any current or future mass storage solution which can be used to store information and/or instructions. Exemplary mass storage device (450) includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.
[00140] The bus (420) communicatively couples the processor (470) with the other memory, storage, and communication blocks. The bus (420) may be, e.g., a Peripheral Component Interconnect / Peripheral Component Interconnect Extended bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (470) to the computer system.
[00141] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (420) to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (460). The components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.
[00142] In an exemplary embodiment, the present disclosure relates to a user equipment (UE) communicatively coupled with a network. The coupling includes steps of establishing, by a communication unit a connection between a first unit serving a first cell (C1) and a second unit serving a second cell (C2), exchanging by a communication unit, one or more requests between the first unit and the second unit over the established connection, deriving by a processing engine, load conditions of each of the first unit and the second unit based on the exchanged one or more requests, identifying by the processing engine, an unbalanced unit experiencing an unbalanced load, and an available unit based on the derived load conditions, upon identifying the unbalanced load, selecting by the processing engine, a number of inactive user equipments (UEs) connected with the unbalanced unit by determining at least one parameter associated with one or more UEs connected with the unbalanced unit and performing by the processing engine, load balancing by initializing an offloading by redirecting the selected numbers of inactive UEs from the unbalanced unit towards the available unit.
[00143] The present disclosure provides technical advancement related to load balancing over a plurality of units serving a plurality of cells in a network. This advancement addresses the limitations of existing solutions by introducing a method that dynamically balances load between units based on real-time data. The present disclosure involves the identification of unbalanced units, selecting inactive UEs for offloading, and efficiently redirecting the UEs to available units, significantly improving network efficiency and resource allocation. By implementing inactivity-based offloading, the present disclosure enhances network reliability and service continuity, resulting in optimized resource use and reduced service disruptions.
[00144] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.
TECHNICAL ADVANTAGES
[00145] The present disclosure described herein above has several technical advantages including, but not limited to, the realization of a system and a method for providing load balancing that:
• dynamically balances load between units, optimizing resource use and preventing network congestion.
• enhances communication network performance and improves inter-cell offloading.
• supports rapidly changing traffic patterns and maximizes the utilization of radio resources; and
• reduces service disruptions by smoothly managing network load, resulting in better user experience and consistent performance. ,CLAIMS:CLAIMS
We Claim:
1. A system (108) for performing load balancing over a plurality of units serving a plurality of cells in a network, the system (108) comprising:
a communication unit (118) configured to:
establish a connection between a first unit (122) serving a first cell (C1) and a second unit (126) serving a second cell (C2);
exchanging one or more requests between the first unit (122) and the second unit (126) over the established connection;
a processing engine (110) coupled to the communication unit (118) and configured to:
derive load conditions of each of the second unit (126) and the first unit (122) based on the exchanged one or more requests;
identify an unbalanced unit experiencing an unbalanced load and an available unit based on the derived load conditions;
upon identifying the unbalanced load, select a number of inactive user equipments (UEs) connected with the unbalanced unit by determining at least one parameter associated with one or more UEs (104) connected with the unbalanced unit; and
perform load balancing by initializing an offloading by redirecting the selected numbers of inactive UEs from the unbalanced unit towards the available unit.
2. The system (100) as claimed in claim 1, wherein the first unit (122) and the second unit (126) are connected via an Xn interface.
3. The system (100) as claimed in claim 1, is further configured to obtain at least one resource status update from the first unit (122) and the second unit (126), wherein the at least one resource status update includes a plurality of information elements (IEs).
4. The system as claimed in claim 3, is further configured to generate, by each of the first unit (122) and the second unit (126), at least one resource status update by processing the exchanged at least one resource status request.
5. The system (100) as claimed in claim 4, wherein the exchanged at least one resource status request includes at least one of an identification element, a registration request, report characteristics, a cell to report, and a reporting periodicity.
6. The system (100) as claimed in claim 1, wherein the at least one parameter is an inactivity timer associated with each UE (104) in the network (106).
7. The system (108) as claimed in claim 1, is further configured to transmit a radio resource control (RRC) release request by the unbalanced unit to the selected user equipments (UEs) (104) upon selecting the one or more UEs (104).
8. The system (100) as claimed in claim 7, wherein the RRC release request includes at least one absolute radio frequency channel number (ARFCN) of the available unit.
9. The system (100) as claimed in claim 3, wherein the plurality of information elements (IEs) includes a radio resource status, a transport network layer (TNL) capacity indicator, a composite available capacity, a slice available capacity, a number of active user equipments (UEs), and a number of RRC connections.
10. A method (300) for performing load balancing over a plurality of units serving a plurality of cells in a network (106), the method (300) comprising:
establishing (302), by a communication unit (118), a connection between a first unit (122) serving a first cell (C1) and a second unit (126) serving a second cell (C2);
exchanging (304), by a communication unit (118), one or more requests between the first unit (122) and the second unit (126) over the established connection;
deriving (306), by a processing engine (110), load conditions of each of the first unit (122) and the second unit (126) based on the exchanged one or more requests;
identifying (308), by the processing engine (110), an unbalanced unit experiencing an unbalanced load, and an available unit based on the derived load conditions;
upon identifying the unbalanced load, selecting (310) by the processing engine (110), a number of inactive user equipments (UEs) connected with the unbalanced unit by determining at least one parameter associated with one or more UEs (104) connected with the unbalanced unit; and
performing (312), by the processing engine (110), load balancing by initializing an offloading by redirecting the selected numbers of inactive UEs from the unbalanced unit towards the available unit.
11. The method (300) as claimed in claim 10, wherein the first unit (122) and the second unit (126) are connected via an Xn interface.
12. The method (300) as claimed in claim 10, further comprising obtaining at least one resource status update from the first unit (122) and the second unit (126), wherein the at least one resource status update includes a plurality of information elements (IEs).
13. The method (300) as claimed in claim 12, further comprising generating, by each of the first unit (122) and the second unit (126), at least one resource status update by processing the exchanged at least one resource status request.
14. The method (300) as claimed in claim 13, wherein the exchanged at least one resource status request includes at least one of an identification element, a registration request, report characteristics, a cell to report, and a reporting periodicity.
15. The method (300) as claimed in claim 10, wherein the at least one parameter is an inactivity timer associated with each UE (104) in the network (106).
16. The method (300) as claimed in claim 10, further comprising: upon selecting the one or more UEs (104), transmitting, by the unbalanced unit, a radio resource control (RRC) release request to the selected user equipments (UEs) (104).
17. The method (300) as claimed in claim 16, wherein the RRC release request includes at least one absolute radio frequency channel number (ARFCN) of the available unit.
18. The method (300) as claimed in claim 12, wherein the plurality of information elements (IEs) includes a radio resource status, a transport network layer (TNL) capacity indicator, a composite available capacity, a slice available capacity, a number of active UEs, and a number of RRC connections.
19. A user equipment (UE) (104) communicatively coupled to a network (106), the coupling comprises steps of:
receiving, by the network (106), a connection request from the UE (104);
sending, by the network (106), an acknowledgment of the connection request to the UE (104); and
transmitting a plurality of signals in response to the connection request, wherein the UE (104) is configured to establish a connection with each of a first unit (122) serving a first cell and a second unit (126) serving a second cell and load balancing is performed in the network (106) by a method (300) as claimed in claim 10.