The present disclosure relates to a wireless communication system, and more specifically relates to a method for identifying user equipment (UE) for real-time handover trigger in an open-radio access network (O-RAN) environment.
BACKGROUND
[0002] When a user equipment (UE) is moved from a service area defined by "X" cell into that defined by "Y" cell, the UE must disconnect with "X" base station and connect with "Y" base station (i.e., establish a new connection). This operation is known as handover (HO) or a cell reselection. A network congestion is a growing problem for wireless network operators. For example, for some UEs, the cell offering the strongest radio reception may also be the most heavily loaded with other UEs who are currently being served. Handing over of still more UEs into that cell shall aggravate the congestion that may already exist. This may result in degraded quality of service, dropping of calls, denial of service, and the like. All of these may result in loss of reputation of the wireless network operators and loss of revenue for the wireless network operators.
[0003] Although the need of HO, the unnecessarily switching of the serving cell and in case of switching to a loaded cell, in both these cases, causes wastage of radio resources and decrease in system efficiency. Hence, in order to effectively manage the HO operation, it is vital to monitor and consider the parameters, including the variation therein, constituting the HO in consideration with load balancing of the cells. The parameters may include, but not limited to, signal strength (RSRF7RSRQ), cell load values, cell individual offset (CIO), hysteresis loss, and the like. Especially, considering the current expansion in the wireless communication networks are becoming increasingly complex and due to introduction of new standards and protocols (such as 4G/5G standards), the monitoring of these parameters in order to effectively utilize the radio resources, is at utmost priority. Some of the prior art references are given below:
[0004] WO2018005089A1 discloses a method which performs a set of checks for verifying that a mobile terminal supports interference cancellation. A

handover-offset value is determined to change a handover threshold to trigger handover of a wireless connection of the mobile terminal from first cell to second cell with the handover-offset value being determined based on a resource-utilization level of the second cell. A control message is transmitted to cause the mobile terminal to change the handover threshold, where the control message is transmitted in response to the checks to be passed.
[0005] US9560560B2 discloses a user equipment (UE) which has a hardware processing circuit to receive a measurement report configuration message that includes multiple measurement events to be determined at UE, from an Evolved Node-B (eNB), and transmits the measurement report when combined measurement event occurs. The combined measurement event is triggered when all of the multiple measurement events occur. The measurement events are related to signal measurements performed on one or more signals received at UE from cells configured for operation in the network.
[0006] While the prior arts cover various approaches to overcome the above stated drawbacks, there are no significant considerations to counter drawbacks associated with identification of UEs by checking quality indicator of UEs in serving cell, and identifying the UEs to which CIO values (handover parameters) is to be transmitted. In light of the above-stated discussion, there is a need to overcome the above stated disadvantages.
OBJECT OF THE DISCLOSURE
[0007] A primary object of the present disclosure is to provide a method for identifying a user equipment (UE) for real-time handover trigger in open-radio access network (O-RAN) environment.
[0008] Another object of the present disclosure is to identify the UEs by checking quality indicator of UEs in serving cell.
[0009] Yet another object of the present disclosure is to identify the UEs to which CIO values (handover parameters) is to be transmitted.

[0010] Yet another object of the present disclosure is to achieve improved load balancing across different cells in 4G/LTE and 5G networks, even after the HO operation.
SUMMARY
[0011] The present disclosure provides a method for identifying at least one user equipment positioned in a serving cell, for real-time handover trigger by a Radio access network (RAN) controller in an open RAN (O-RAN) environment. The O-RAN environment has a virtualized network architecture having at least one RAN controller. The RAN controller is connected with a plurality of E2 nodes. The plurality of E2 nodes is connected with a plurality of user equipment positioned in the serving cell. The serving cell covers a location for serving the plurality of user equipment. The serving cell is adjacent to a plurality of neighbour cells. The method includes a first step to obtain a serving cell handover parameter with respect to a neighbour cell handover parameter associated with at least one neighbour cell of the plurality of neighbour cells. The method includes a second step to determine one or more user equipment from the plurality of user equipment positioned in the serving cell. Each of one or more determined user equipment has a channel quality index (CQI) less than a predetermined threshold lower CQI. The method includes a third step to identify the at least one user equipment from the one or more determined user equipment positioned in the serving cell. At least one identified user equipment has a throughput value more than a predetermined threshold throughput. The method includes a fourth step to transmit the serving cell handover parameter with respect to the neighbour cell handover parameter associated with the at least one neighbour cell of the plurality of neighbour cells to the at least one identified user equipment.
[0012] These and other aspects of the invention herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred examples and numerous specific details thereof, are given by way of illustration and not of limitation. Many

changes and modifications may be made within the scope of the invention herein without departing from the spirit thereof, and the invention herein include all such modification.
BRIEF DESCRIPTION OF FIGURES
[0013] The method and system are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various drawings. The invention herein will be better understood from the following description with reference to the drawings, in which:
[0014] FIG. 1 illustrates an example radio access network (RAN).
[0015] FIG. 2 illustrates an Open-Radio access network (O-RAN) architecture.
[0016] FIG. 3 is a flow chart illustrating a method for a flow chart (600) for efficiently updating a handover Parameters.

DETAILED DESCRIPTION
[0017] In the following detailed description of the invention, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be obvious to a person skilled in the art that the invention may be practiced with or without these specific details. In other instances, well known methods, procedures and components have not been described in details so as not to unnecessarily obscure aspects of the invention.
[0018] Furthermore, it will be clear that the invention is not limited to these implementations only. Numerous modifications, changes, variations, substitutions and equivalents will be apparent to those skilled in the art, without parting from the scope of the invention.
[0019] The accompanying drawings are used to help easily understand various technical features and it should be understood that the implementations presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another.
[0020] Standard Networking Terms and Abbreviation: New RAN: A Radio Access Network which can support either NR/E-UTRA or both and have capabilities to interface with Next Generation Core Network (NG-CN). NG-C/U is a Control/User Plane interface towards NG-CN.
[0021] gNB: New Radio (NR) Base stations which have capability to interface with 5G Core named as NG-CN over NG-C/U (NG2/NG3) interface as well as 4G Core known as Evolved Packet Core (EPC) over Sl-C/U interface.
[0022] LTE eNB: An LTE eNB is evolved eNodeB that can support connectivity to EPC as well as NG-CN.
[0023] Non-standalone NR: It is a 5G Network deployment configuration, where a gNB needs an LTE eNodeB as an anchor for control plane connectivity to 4G EPC or LTE eNB as anchor for control plane connectivity to NG-CN.

[0024] Standalone NR: It is a 5G Network deployment configuration where gNB does not need any assistance for connectivity to core Network, it can connect by its own to NG-CN over NG2 and NG3 interfaces.
[0025] Non-standalone E-UTRA: It is a 5G Network deployment configuration where the LTE eNB requires a gNB as anchor for control plane connectivity to NG-CN.
[0026] Standalone E-UTRA: It is a typical 4G network deployment where a 4G LTE eNB connects to EPC.
[0027] Xn Interface: It is a logical interface which interconnects the New RAN nodes i.e., it interconnects gNB to gNB and LTE eNB to gNB and vice versa.
[0028] Referring now to the drawings, and more particularly to FIGS. 1 through 3.
[0029] FIG. 1 illustrates an example radio access network (RAN) (100) that comprises a plurality of user equipment (UEs) such as (112a, 112b, 112c, 112d, and 112e) connected to a serving base station (104) position in a serving cell (110). Further, the RAN (100) comprises a plurality of neighbour base stations (106a and 106b) positioned in respective neighbour cells (108a and 108b). The radio access network (RAN) is a part of a telecommunications system which may connect individual devices to other parts of a network through radio connections. Further, RAN may provide a connection of user equipment such as mobile phone or computer with the core network of the telecommunication systems. Furthermore, RAN may be an essential part of access layer in the telecommunication systems which utilize base stations (such as eNB and gNB) for establishing radio connections.
[0030] In some example, the RAN (100) comprises a RAN controller (102). The RAN (100), in one example, is implemented in a virtualized network architecture (such as for example, open-radio access network (O-RAN)) and comprises at least one RAN controller (102). In some example, the RAN controller (102) is configured to perform operations related to handover of the plurality of UEs (112a-e). In some example, the RAN controller (102) may be implemented via

a virtualized application that is xApps i.e., xApp-3 that are configured to virtually perform the operations of the RAN controller (102).
[0031] In some example, the RAN controller (102) is an individual controller, which is separate from the RAN (100). In this situation, the RAN controller (102) is connected with the RAN (100) by means of a network connection such as radio connections.
[0032] The RAN controller (102) may be configured to communicate with a core network (not shown) comprising an evolved packet core (EPC) using an "SI" interface. More particularly, the RAN controller (102) may communicate with the core network (not shown) comprising Mobility Management Entity (MME) and a User plane entity (UPE) identified as Serving Gateway (S-GW) using Sl-C and Si¬ll for control plane and user plane, respectively.
[0033] All of the plurality of UE (112a-e) periodically measure received signal strengths/qualities from all base stations (104, 106a and 106b) and construct signal strength/quality indicators such as reference signal received power (RSRP) and reference signal received quality (RSRQ) values as defined in the 3GPP standards. Then using the criteria as defined in the 3GPP standards, when an A3 event triggers, these measurement results are reported to the serving base station (104). The invention is not limited to the A3 event (for example, subscription of multiple events such as A1-A6 and the measurements and handover parameters defined therein. Any future standards are expected to have equivalent handover events and equivalent measurements and parameters associated with such handover events. For those standards, when such equivalent events trigger, said equivalent measurements are reported (1). The measurements in the form of measurement reports (MRs).
[0034] Further, the MRs first sent (2) to the RAN controller (102). The RAN controller (102) then executes a real-time handover trigger and target cell selection, according to the proposed invention. Additionally, base station loads, in terms of number of UEs served, total computational, energy, memory, wireless resource usage levels of the base station, etc., are also made available, by the RAN controller (102). Further, for example, the HO parameters of each cell are also provided to the

RAN controller (102). The HO parameters such as, for example, offset parameters (i.e., cell indication offset (CIO)), hysteresis parameter and time to trigger parameter defined therein, or equivalent parameters of future standards. In some example, the MRs may also include signal strength metrics that is RSRP and/or RSRQ values.
[0035] In some example, when the RAN controller (102) receives the MRs and/or HO parameters, it triggers a first HO process and a second HO process. The first HO process and second HO process is performed parallelly on the serving cell (110) and on all the neighbour cells (108a and 108b). In some example, the first HO process and second HO process is triggered simultaneously in parallel. That is, multiple HO of the UEs can be performed accurately in that the RAN controller (102) can be configured to perform, parallelly on all the identified target neighbour cells (108a and 108b), the HO process (first and second) from the serving cell (110) to the identified target neighbour cells (108a and 108b).
[0036] The base stations (104, 106a and 106b) (may include, for example, an access node such as e.g. a Radio Base Station (RBS), also referred to as e.g., evolved Node B ("eNB"), "eNodeB", "NodeB", "B node", gNB, or BTS (Base Transceiver Station), depending on the technology and terminology used. The base stations (104, 106a and 106b) may be a logical node that handles transmission and reception of signals associated with either the serving cell (110) and the neighbour cells (108a and 108b). The serving cell (110) and the neighbour cells (108a and 108b) may connect to each other via "Xn" interface. The base station (104) and the neighbour base stations (106a and 106b) may connect to one or more antennas, such as the antenna, thus respective base stations may be responsible for the serving cell (110) and the neighbour cells (108a and 108b). In some example, the base station (104) can be configured to broadcast the HO parameters or the updated HO parameters to the plurality of UE (112a-e) served by the base station (104). The HO parameters, in one example, may also be communicated to the neighbour base stations (106a and 106b) using the "Xn" interface.
[0037] The plurality of UE (112a-e) may be the devices used to initiate a communication, such as a computer, a personal digital assistant (PDA), a laptop or

electronic notebook, a cellular telephone, or any other device, component, element, or object capable of initiating voice, audio, video, media, or data exchanges within the RAN (100).
[0038] Further, the components of the RAN controller (102) may be implemented using one or more application-specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware. Alternatively, the functions may be performed by one or more other processing units (or cores), on one or more integrated circuits. In other examples, other types of integrated circuits may be used (e.g., Structured/Platform ASICs, Field Programmable Gate Arrays (FPGAs), and other Semi-Custom ICs), which may be programmed in any manner known in the art. The functions of each unit may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application-specific processors.
[0039] Referring to FIG. 2 in conjunction with FIG. 1, an Open-Radio Access Network (O-RAN) architecture (200) includes a Service Management and Orchestration (SMO) framework (202) and a radio access network (RAN) intelligent controller (RIC) (208) connected to the RAN (100).
[0040] The Open-Radio Access Network (O-RAN) architecture (200) utilizes an Open-Radio Access Network (O-RAN), which is an evolved version of prior radio access networks, makes the prior radio access networks more open and smarter than previous generations. The O-RAN provides real-time analytics that drive embedded machine learning systems and artificial intelligence back end modules to empower network intelligence. Further, the O-RAN includes virtualized network elements with open and standardized interfaces. The open interfaces are essential to enable smaller vendors and operators to quickly introduce their own services, or enables operators to customize the network to suit their own unique needs. Open interfaces also enable multivendor deployments, enabling a more competitive and vibrant supplier ecosystem. Similarly, open source software and hardware reference designs enable faster, more democratic and permission-less innovation. Further, the O-RAN introduces a self-driving network by utilizing new learning based technologies to automate operational network functions. These

learning based technologies make the O-RAN intelligent. Embedded intelligence, applied at both component and network levels, enables dynamic local radio resource allocation and optimizes network wide efficiency. In combination with O-RAN's open interfaces, Al-optimized closed-loop automation is a new era for network operations.
[0041] The SMO (202) is configured to provide SMO functions/services such as data collection and provisioning services of the RAN (100). The RAN (100), herein, is implemented in the O-RAN computing architecture (200). The RAN (100) may implement a single radio access technology (RAT) (4G/5G) or multiple RATs (4G and 5G) using the base stations (104, 106a, 106b, 106c... 106n) located in the RAN (100). The data collection of the SMO framework (202) may include, for example, data related to a bandwidth of a wireless communication network and at least one of the pluralities of UEs (112a-e).
[0042] The base stations (104, 106a, 106b, 106c... 106n) may be for e.g., a Radio Base Station (RBS), also referred to as e.g., evolved Node B ("eNB"), "eNodeB", "NodeB", "B node", gNB, or BTS (Base Transceiver Station), depending on the technology and terminology used. In some example, the base stations (104, 106a, 106b, 106c... 106n) may be a logical node that handles transmission and reception of signals associated with the plurality of cells. The base station (104) may connect to each other i.e., with the neighbour base stations (106a, 106b.. 106n) via "Xn" interface either in a same network or to a network node of another network (intra-network). Each base station (104, 106a, 106b, 106c... 106n) may connect to one or more antennas.
[0043] Referring back to FIG. 2, the RIC (208) can be a non-real-time-radio intelligent controller (Non-RT-RIC) (204) and a near-real-time-radio intelligent controller (Near-RT-RIC) (206). Generally, the near real time RAN Intelligent Controller (near RT RIC) is a logical function that enables near-real-time control and optimization of O-RAN elements and resources via fine-grained data collection and actions over E2 interface. The Non-Real Time Radio Intelligent Controller (non-RT-RIC) is a logical function that enables non-real-time control and optimization of RAN elements and resources, AI/ML workflow including model

training and updates, and policy based guidance of applications/features in near-RT RIC. It is a part of the Service Management and Orchestration Framework and communicates to the near-RT RIC using an Al interface. Non-RT control functionality (> Is) and near-Real Time (near-RT) control functions (< Is) are decoupled in the RIC. The Non-RT functions include service and policy management, RAN analytics and model-training for some of the near-RT RIC functionality, and non-RT RIC optimization. Further, O-CU is O-RAN Central Unit, which is a logical node hosting RRC (Radio Resource Control) protocol, SDAP (Service Data Adaptation Protocol) and PDCP (Packet Data Convergence Protocol). O-CU-CP is O-RAN Central Unit - Control Plane, which is a logical node hosting the RRC and the control plane part of the PDCP protocol. The O-CU-UP is O-RAN Central Unit - User Plane, which is a logical node hosting the user plane part of the PDCP protocol and the SDAP protocol. The O-DU is O-RAN Distributed Unit, which is a logical node hosting RLC/MAC/High-PHY layers based on a lower layer functional split. The O-RU is O-RAN Radio Unit, which is a logical node hosting Low-PHY layer and RF processing based on a lower layer functional split. This is similar to 3GPP's "TRP" or "RRH" but more specific in including the Low-PHY layer (FFT/iFFT, PRACH extraction). An 01 interface is an interface between management entities in Service Management and Orchestration Framework and O-RAN managed elements, for operation and management, by which FCAPS (fault, configuration, accounting, performance, security) management, Software management, File management shall be achieved. The xAPP is an independent software plug-in to the Near-RT RIC platform to provide functional extensibility to the RAN by third parties. The near-RT RIC controller can be provided different functionalities by using programmable modules as xAPPs, from different operators and vendors.
[0044] The Non-RT-RIC (204) may be configured to support intelligent RAN optimization in non-real-time. Further, the Non-RT-RIC (204) can be configured to leverage the SMO services and may be a part of the SMO (202). One such advantage of configuring the RAN (100) within the O-RAN computing environment and/or O-RAN architecture (200) is leveraging the intellectualization

("Artificial intelligence (AI)/Machine Learning (ML)) of the Non-RT-RIC (204) and the Near-RT-RIC (206).
[0045] The Near-RT-RIC (206) may host plurality of xApps. The xApps (at the Near-RT-RIC (206)) uses an "E2" interface to collect near real-time RAN (100) information and to provide value added services using these primitives, guided by the policies/configuration and the enrichment data provided by the "Al" interface from the xApps at the Non-RT-RIC (204). An "01" interface collects data for training in the Non-RT RIC (204) (integrated with SMO (202).
[0046] In one example, the "E2" and "Al" interface may be used to collect control messages, subscription messages (i.e., subscription to RSRP/RSRQ reports and Limited-time subscription for A3 events and A3 RSRP/RSRQ Reports), policy trigger messages, indication messages, machine learning (ML) management and enrichment information types of messages, and the like. The real-time measurements comprising RSRP/RSRQ measurements, channel quality measurements and the like. The subscription messages such as, for example, RSRP/RSRP event messages, A3 events messages, limited-time based A3 event messages, and the like. The policy trigger messages, for example, spectrum allocation policies, radio assignment policies, and the like. The O-RAN architecture (200) comprises a virtualized network architecture having at least one RAN controller (102) that is configured to perform the operations as detailed above.
[0047] The present disclosure aims to identify at least one user equipment positioned in the serving cell (110) for real-time handover trigger by the Radio access network (RAN) controller (102) in the open RAN (O-RAN) environment (200). The O-RAN environment (200) has a virtualized network architecture having the at least one RAN controller (102). The RAN controller (102) is connected with a plurality of E2 nodes. The plurality of E2 nodes is connected with the plurality of user equipment (112a-e) positioned in the serving cell (110). Further, the serving cell (110) covers a location for serving the plurality of user equipment (112a-e). Furthermore, the serving cell (110) is adjacent to the plurality of neighbour cells (108a, 108b).

[0048] In an example, the parameters used by xApp-3 includes LCQI (Lower CQI Threshold) = 4 (Default), HCQI (Higher CQI Threshold) = 6 (Default), THPT (UE Throughput Threshold) = 50 Kbps (Default), NMEAS (Number of individual measurements) used or throughput computation = 8 (Default), A (Inter-measurement interval) = 128 ms (Default), and N (Threshold for # of UEs = 8 (Default).
[0049] In an implementation, a serving cell handover parameter is obtained with respect to a neighbour cell handover parameter associated with at least one neighbour cell of the plurality of neighbour cells (108a, 108b). In another example, handover parameter may be alternatively used for handover parameter. In another example, handover parameter or handover parameter may be cell individual offset value. The cell handover parameter is a comparative load value of the serving cell with respect to the neighbour cell. Further, one or more user equipment is determined from the plurality of user equipment (112a-e) positioned in the serving cell. Each of one or more determined user equipment has a channel quality index (CQI) less than a predetermined threshold lower CQI. The at least one user equipment is identified from the one or more determined user equipment positioned in the serving cell. The at least one identified user equipment has a throughput value more than a predetermined threshold throughput. Further, the serving cell handover parameter with respect to the neighbour cell handover parameter associated with the at least one neighbour cell of the plurality of neighbour cells (108a, 108b) is transmitted to the at least one identified user equipment.
[0050] In another example, when a UE starts measuring the neighbour cells, there may be several other measurement configuration parameters that specify the triggering of handover measurement reports from the UE. One of such and most common triggered criteria includes "Event A3": Neighbour cells becomes better than an offset relative to the serving cell. The offset values are known as cell individual offset (CIO) defined by the network for each cell and communicated to the UE as one of the measurement configuration parameters (also referred as load parameter, handover parameters or handover parameters, herein) along with signal strength metrics (Reference Signals Received Power (RSRP)/Reference Signal

Received Quality (RSRQ)), hysteresis metrics, and the like. For clarity, handover parameters, load parameters and handover load parameters may be used alternatively in the draft.
[0051] Further, a count of the at least one identified user equipment is checked if it is more than or equal to a predetermined user equipment threshold for the serving cell or below the predetermined user equipment threshold for the serving cell. In case, if the count of the at least one identified user equipment is below the predetermined user equipment threshold for the serving cell, the identification of the at least one user equipment is terminated. Alternatively, if the count of the at least one identified user equipment is below the predetermined user equipment threshold for the serving cell, the predetermined threshold lower CQI is increased.
[0052] Further, one or more second user equipment positioned in the serving cell is determined. Each of the one or more determined second user equipment has the channel quality index (CQI) less than increased predetermined threshold lower CQI. In other words, xCQI < HCQI. At least one second user equipment is identified from the one or more determined second user equipment positioned in the serving cell. The at least one identified second user equipment has the throughput value more than the predetermined threshold throughput. The serving cell handover parameter with respect to the neighbour cell handover parameter associated with the at least one neighbour cell of the plurality of neighbour cells (108a, 108b) is transmitted to the at least one identified second user equipment.
[0053] In an example, it is checked if the serving cell handover parameter with respect to the neighbour cell handover parameter associated with the at least one neighbour cell of the plurality of neighbour cells (108a, 108b) is new. The one or more user equipment positioned in the serving cell, having the channel quality index (CQI) parameter less than the predetermined threshold lower CQI is determined when the serving cell handover parameter with respect to the neighbour cell handover parameter associated with the at least one neighbour cell of the plurality of neighbour cells (108a, 108b) is new.

[0054] Further, a second neighbour cell is identified when the serving cell handover parameter with respect to the neighbour cell handover parameter associated with the at least one neighbour cell of the plurality of neighbour cells (108a, 108b) is pre-used for the identification of the at least one user equipment. The present disclosure minimizes count of unicast transmission of the serving handover parameter with respect to the neighbour cell handover parameter to the plurality of user equipment (112a-e) positioned in the serving cell.
[0055] Referring to FIG. 3 that illustrates a flow chart (300) for efficiently updating the handover Parameters (xApp-3). In an example, the flow chart (300) is executed for the serving cell. In an implementation, the flow chart (300) may include a step (302) to pick one of the neighbors of the serving cell. In an example, at least one such neighbour exists. Further, this neighbour is designated as cell t. The flow chart (300) may include another step (304) to retrieve CIOs,t value from a radio network information base (KNTB) (114) and check if this value has been updated by xApp-1 since the last time it was checked by xApp-3. The KNTB (114) may be, in one example, a storage unit for old/existing/new CIOs. If this is not a new value, execution moves to the next neighbour, if one exists, at step (306). The flow chart (300) may include yet another step (308) in which if the CIOs,t value is new, xApp-3 needs to identify the UEs which are possibly at the cell edge. In addition, it is approximated by identifying the UEs which have relatively low CQI indices. For this purpose, the variable xCQI is set to the parameter LCQI.
[0056] The flow chart (300) may include yet another step (310) in which all of the plurality of UE (112a-e) with CQI index no higher than LCQI are identified. Among such UEs, the list of UEs is further narrowed by identifying the UEs that have recent throughput at least as large as the parameter TUPT. Recent throughput for the plurality of UE (112a-e) is obtained by summing the total number of bits transferred by the UE in the DL and UL directions over the last NMEAS measurement intervals and dividing the sum by NMEAS*A. Further, this last task is designed to limit sending the CIO updated to only those UEs that are currently contributing in a significant way to the loading in the serving cell. For ease of

execution, it may be desirable to execute sequentially the two sub-steps of limiting UEs by their CQI indices and limiting UEs by their recent throughput levels.
[0057] The flow chart (300) may include yet another step (314) in which the total number of UEs identified so far for CIO update is stored in the variable xUEs. The flow chart (300) may include yet another step (316) to check if the number of UEs identified for CIO update is below the threshold N, another parameter for xApp-3. If the number of such UEs has reached the value N, no more UEs will be identified for CIO update for the cell pair (s, t). The cell pair (s, t) are the selected serving cell and target cell. The flow chart (300) may include yet another step (320) in which if the number of UEs identified for CIO update is below the threshold N, the current CQI threshold (xCQI) used for designating UEs as the cell edge UEs (and hence getting identified for CIO update) is increased by one.
[0058] The flow chart (300) may include yet another step (322) to check if xCQI threshold is still no larger than the HCQI parameter. If xCQI threshold exceeds HCQI, no more UEs will be identified for CIO update for the cell pair (s, t). The flow chart (300) may include yet another step (312) in which if the updated CQI threshold is still no larger than the HCQI parameter, all UEs with CQI indices equal to the new CQI threshold (current xCQI) are identified as the additional UEs that may potentially receive the CIOs,t update. Among such UEs, the list of UEs is further narrowed by identifying the UEs that have recent throughput at least as large as the parameter THPT. As described earlier, for ease of operation, it may be desirable to execute sequentially the two sub-steps of limiting UEs by their CQI indices and limiting UEs by their recent throughput levels.
[0059] The flow chart (300) may include yet another step in which identification is done for the UEs that should be sent to CIOs,t. Hence, the "new" flag associated with CIOs,t is reset at step (318). The flow chart (300) may include yet another step to look for another neighbour t of cell s. If no additional neighbour exists, xApp-3 execution for the serving cell can be ended. The flow chart (300) may include yet another step that can stop the execution of the method for the serving cell. In an example, the method in the flow chart (300) requires low processing for identification of handover requirement. In another example, the

method in the flow chart (300) is optimized for selecting the plurality of UE (112a-e) which are actually active and requires handover. In yet another example, the method in the flow chart (300) minimizes the required unicast transmissions to the plurality of UE (112a-e) without reducing the MLB efficacy. In yet another example, the method in the flow chart (300) updates only the UEs that are likely to be at the cell edge (based on the available CQI information). In yet another example, the method in the flow chart (300) updates only the UEs that are likely to be contributing to the cell loading (based on the throughput information for the individual UEs).
[0060] Hence, the present disclosure aims at providing the real-time handover based on the real-time monitoring and considering the cell load values and adjusting the CIO values accordingly in a cyclic manner.
[0061] The various actions, acts, blocks, steps, or the like in the flow chart (300) may be performed in the order presented, in a different order or simultaneously. Further, in some examples, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention.
[0062] The implementation disclosed herein can be implemented using at least one software program running on at least one hardware device and performing network management functions to control the elements.
[0063] It will be apparent to those skilled in the art that other implementations of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention. While the foregoing written description of the invention enables one of ordinary skill to make and use what is considered presently to be the best mode thereof, those of ordinary skill will understand and appreciate the existence of variations, combinations, and equivalents of the specific implementation, method, and examples herein. The invention should therefore not be limited by the above-described implementation, method, and examples, but by all implementations and methods within the scope of the invention. It is intended that the specification and examples be considered as exemplary, with the true scope of the invention being indicated by the claims.

[0064] The methods and processes described herein may have fewer or additional steps or states and the steps or states may be performed in a different order. Not all steps or states need to be reached. The methods and processes described herein may be embodied in, and fully or partially automated via, software code modules executed by one or more general purpose computers. The code modules may be stored in any type of computer-readable medium or other computer storage device. Some or all of the methods may alternatively be embodied in whole or in part in specialized computer hardware.
[0065] The results of the disclosed methods may be stored in any type of computer data repository, such as relational databases and flat file systems that use volatile and/or non-volatile memory (e.g., magnetic disk storage, optical storage, EEPROM and/or solid-state RAM).
[0066] The various illustrative logical blocks, modules, routines, and algorithm steps described in connection with the implementations disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.
[0067] Moreover, the various illustrative logical blocks and modules described in connection with the implementations disclosed herein can be implemented or performed by a machine, such as a general purpose processor device, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components or any combination thereof designed to perform the functions described herein. A general-purpose processor device can be a microprocessor, but in the alternative, the

processor device can be a controller, microcontroller, or state machine, combinations of the same, or the like. A processor device can include electrical circuitry configured to process computer-executable instructions. In another example, a processor device includes an FPGA or other programmable device that performs logic operations without processing computer-executable instructions. A processor device can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Although described herein primarily with respect to digital technology, a processor device may also include primarily analog components. A computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.
[0068] The elements of a method, process, routine, or algorithm described in connection with the implementations disclosed herein can be embodied directly in hardware, in a software module executed by a processor device, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of a non-transitory computer-readable storage medium. An exemplary storage medium can be coupled to the processor device such that the processor device can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor device. The processor device and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor device and the storage medium can reside as discrete components in a user terminal.
[0069] Conditional language used herein, such as, among others, "can," "may," "might," "may," "e.g.," and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain examples include, while other examples do not include, certain features,

elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more examples or that one or more examples necessarily include logic for deciding, with or without other input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular example. The terms "comprising," "including," "having," and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term "or" is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term "or" means one, some, or all of the elements in the list.
[0070] Disjunctive language such as the phrase "at least one of X, Y, Z," unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain implementations require at least one of X, at least one of Y, or at least one of Z to each be present.
[0071] While the above detailed description has shown, described, and pointed out novel features as applied to various implementations, it can be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the scope of the disclosure. As can be recognized, certain implementations described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others.
[0072] The foregoing description of the specific implementations will so fully reveal the general nature of the implementations herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific implementations without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed implementations. It is to be understood that the phraseology or terminology

employed herein is for the purpose of description and not of limitation. Therefore, while the implementations herein have been described in terms of preferred implementations, those skilled in the art will recognize that the implementations herein can be practiced with modification within the spirit and scope of the invention as described herein.

CLAIMS
We Claim:

1. A method for identifying at least one user equipment positioned in a serving
cell (110), for real-time handover trigger by a Radio access network (RAN)
controller (102) in an open RAN (O-RAN) environment (200), the O-RAN
environment (200) has a virtualized network architecture having at least one RAN
controller (102), the RAN controller (102) is connected with a plurality of E2 nodes,
the plurality of E2 nodes is connected with a plurality of user equipment (112a,
112b, 112c, 112d, and 112e) positioned in the serving cell (110), the serving cell
(110) covers a location for serving the plurality of user equipment (112a-e), the
serving cell (110) is adjacent to a plurality of neighbour cells (108a, 108b), the
method comprising:
obtaining a serving cell handover parameter with respect to a neighbour cell handover parameter associated with at least one neighbour cell of the plurality of neighbour cells (108a, 108b);
determining one or more user equipment from the plurality of user equipment (112a-e) positioned in the serving cell, wherein each of one or more determined user equipment has a channel quality index (CQI) less than a predetermined threshold lower CQI;
identifying the at least one user equipment from the one or more determined user equipment positioned in the serving cell, wherein at least one identified user equipment has a throughput value more than a predetermined threshold throughput; and
transmitting the serving cell handover parameter with respect to the neighbour cell handover parameter associated with the at least one neighbour cell of the plurality of neighbour cells (108a, 108b) to the at least one identified user equipment.
2. The method as recited in claim 1, further comprising:

checking if a count of the at least one identified user equipment is more than or equal to a predetermined user equipment threshold for the serving cell; and
terminating the identification of the at least one user equipment when the count of the at least one identified user equipment is below the predetermined user equipment threshold for the serving cell.
3. The method as recited in claim 1, further comprising:
checking if a count of the at least one identified user equipment is below a predetermined user equipment threshold for the serving cell; and increasing the predetermined threshold lower CQI.
4. The method as recited in claim 1, further comprising:
checking if a count of the at least one identified user equipment is below a predetermined user equipment threshold for the serving cell;
increasing the predetermined threshold lower CQI;
determining one or more second user equipment positioned in the serving cell, wherein each of one or more determined second user equipment has the channel quality index (CQI) less than increased predetermined threshold lower CQI;
identifying at least one second user equipment from the one or more determined second user equipment positioned in the serving cell, wherein at least one identified second user equipment has the throughput value more than the predetermined threshold throughput; and
transmitting the serving cell handover parameter with respect to the neighbour cell handover parameter associated with the at least one neighbour cell of the plurality of neighbour cells (108a, 108b) to the at least one identified second user equipment.
5. The method as recited in claim 1, further comprising checking if the serving
cell handover parameter with respect to the neighbour cell handover parameter

associated with the at least one neighbour cell of the plurality of neighbour cells (108a, 108b) is new, wherein the one or more user equipment positioned in the serving cell, having the channel quality index (CQI) parameter less than the predetermined threshold lower CQI is determined when the serving cell handover parameter with respect to the neighbour cell handover parameter associated with the at least one neighbour cell of the plurality of neighbour cells (108a, 108b) is new.
6. The method as recited in claim 1, further comprising identifying a second neighbour cell when the serving cell handover parameter with respect to the neighbour cell handover parameter associated with the at least one neighbour cell of the plurality of neighbour cells (108a, 108b) is pre-used for the identification of the at least one user equipment.
7. The method as recited in claim 1, wherein the method minimizes count of unicast transmission of the serving handover parameter with respect to the neighbour cell handover parameter to the plurality of user equipment (112a-e) positioned in the serving cell.