The present disclosure relates to a wireless communication system, and more specifically relates to a method for identifying user equipment for handover and target cell selection in an open-radio access network (O-RAN) environment.
BACKGROUND
[0002] For a continuum of cellular telecommunication, handover (HO) or a cell reselection is performed, in which, when a user equipment (UE) is moved from a service area defined by "A" cell into that defined by "B" cell, the UE must disconnect with "A" base station and connect with "B" base station (i.e., establish a new connection). In addition, 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, identification of UEs for HO requirement, selection of target cells for the identified UEs. 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] CN106031292B discloses a method which involves sending radio resource management (RRM) measurement results to an evolved node B (eNB) by a user equipment (UE). A procedure toward a second eNB is initiated by the first eNB for configuring the UE with dual connectivity mode of operation over a X2 interface with a first serving frequency to be served by the second eNB based on RRM measurement results for a configured frequency received from the UE apart from a second serving frequency served by the first eNB.
[0005] WO2018005089A1 discloses a method which involves performing a set of checks for verifying that a mobile terminal (102) 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.
[0006] EP3251406A1 discloses a method which involves receiving data from a cell in a network, where the data comprises information regarding handover such that the cell in the network from which the data is received defines a predetermined target cell to which a user equipment (UE) performs handover. Handover configuration data is provided to the UE, where the handover data comprises event triggering condition. Context information associated with the UE for preparing the target cell for handover procedure initiated by the UE is provided to the predetermined target cell.
[0007] 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 based on CQI values for handover requirement and selection of target cells for the identified UEs. In light of the above-stated discussion, there is a need to overcome the above stated disadvantages.

OBJECT OF THE DISCLOSURE
[0008] A primary object of the present disclosure is to provide a method to identify user equipment (UE) for real-time handover in open-radio access network (O-RAN) environment.
[0009] Another object of the present disclosure is to provide the method to select target cell for identified user equipment (UE) in the open-radio access network (O-RAN) environment.
[0010] Yet another object of the present disclosure is to provide the method to enable efficient utilization of cell load parameters to perform the real-time handover.
SUMMARY
[0011] In an aspect, the present disclosure provides a method to identify at least one user equipment for real-time handover and select a target cell by a Radio access network (RAN) controller in an open RAN (O-RAN) environment. The O-RAN environment has a virtualized network architecture having the RAN controller. The RAN controller is connected with a plurality of user equipments positioned in a serving cell. The serving cell covers a location for serving the plurality of user equipments. The serving cell is adjacent to a plurality of neighbour cells. The method includes a first step to obtain a serving cell load parameter with respect to a neighbour cell load parameter associated with at least one neighbour cell of the plurality of neighbour cells. The serving cell load parameter corresponds to a comparative load value of the serving cell with respect to the at least one neighbour cell of the plurality of neighbour cells. In addition, the method includes a second step to identify the at least one user equipment positioned in the serving cell based on a channel quality index (CQI) and a throughput value. Further, the method includes a third step to transmit the serving cell load parameter with respect to the neighbour cell load parameter associated with the at least one neighbour cell of the plurality of neighbour cells to at least one identified user equipment. Furthermore, the method includes a fourth step to select the target cell from the plurality of neighbour cells for the at least one identified user equipment. The

identification of the at least one user equipment positioned in the serving cell includes determining one or more user equipment from the plurality of user equipments positioned in the serving cell. Each of one or more determined user equipment has the channel quality index (CQI) less than a predetermined threshold lower CQI. The at least one identified user equipment has the throughput value more than a predetermined threshold throughput. The method further includes repeating the identification of the at least one user equipment positioned in the serving cell based on the channel quality index after a pre-determined time interval. The selection of the target cell for the at least one identified user equipment includes obtaining at least one quality of service (QoS) class identifier (QCI) level associated with at least one active bearer in the at least one identified user equipment. The at least one QCI level corresponds to a QoS value required by the at least one active bearer in the at least one identified user equipment to provide a service. The at least one active bearer corresponds to connections between the at least one identified user equipment and a packet data network gateway to provide the service. In addition, the selection of the target cell for the at least one identified user equipment includes obtaining a received signal strength value, a first load value and a plurality of second load values for each of the plurality of neighbour cells. The received signal strength value includes one of Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ). The first load value includes average physical resource block (PRB) values of each of the plurality of neighbour cells. The plurality of second load values includes average PRB values by the at least one QCI level for each of the plurality of neighbour cells. Further, the selection of the target cell includes selecting the target cell based on the at least one QCI level and the received signal strength value, the first load value and the plurality of second load values.
[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 a sequence diagram illustrating a method for performing real-time handover.
[0016] FIG. 3 illustrates an Open-Radio access network (O-RAN) environment.
[0017] FIG. 4 illustrates a flow chart of a method to identify at least one user equipment for real-time handover and select a target cell in the open RAN (O-RAN) environment.

DETAILED DESCRIPTION
[0018] 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.
[0019] 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.
[0020] 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.
[0021] Standard networking terms and abbreviation: RAN: a RAN may stand for radio access network. The radio access network (RAN) may be a part of a telecommunications system which may connect individual devices to other parts of a network through radio connections. The RAN may provide a connection of user equipment (UE) such as mobile phone or computer with the core network of the telecommunication systems. The RAN may be an essential part of access layer in the telecommunication systems which utilize base stations (such as e node B, g node B) for establishing radio connections.
[0022] Active bearer: An active bearer corresponds to tunnel connections between the UE and a packet data network gateway to provide a service.
[0023] O-RAN: O-RAN 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.
[0024] QoS Class identifier (QCI): QCI level corresponds to a QoS value required by the active bearer in the UE to provide the service.
[0025] Near real time RAN Intelligent Controller (Near-RT RIC): 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.
[0026] Non-Real Time Radio Intelligent Controller (Non-RT-RIC): 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 the Al interface. Non-RT control functionality (> Is) and near-Real Time (near-RT) control functions (< Is) are decoupled in the RIC. 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.

[0027] O-CU is O-RAN Central Unit, which is a logical node hosting RRC, SDAP and PDCP protocols.
[0028] 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.
[0029] 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.
[0030] 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.
[0031] 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).
[0032] 01 interface is an interface between management entities in a Service Management and Orchestration (SMO) Framework and O-RAN managed elements, for operation and management, by which FCAPS management, Software management, File management shall be achieved.
[0033] 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.
[0034] 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.
[0035] LTE eNB: An LTE eNB is evolved eNodeB that can support connectivity to EPC as well as NG-CN.
[0036] 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.

[0037] Standalone NR: It is a 5GNetwork 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.
[0038] 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.
[0039] Standalone E-UTRA: It is a typical 4G network deployment where a 4G LTE eNB connects to EPC.
[0040] 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.
[0041] Reference signal received power (RSRP): RSRP may be defined as the linear average over the power contributions (in [W]) of the resource elements that carry cell-specific reference signals within the considered measurement frequency bandwidth." RSRP may be the power of the LTE Reference Signals spread over the full bandwidth and narrowband.
[0042] Referring now to the drawings, and more particularly to FIGS. 1 through 4.
[0043] FIG. 1 illustrates an example radio access network (RAN) 100 that includes a plurality of user equipments (UEs) such as 112a, 112b, 112c, 112d, and 112e connected to a serving base station 104 position in a serving cell 110. Further, the example radio access network 100 includes a plurality of neighbour base stations 106a and 106b positioned in respective neighbour cells 108a and 108b.
[0044] In some examples, the RAN 100 includes 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 includes at least one RAN controller 102. In some examples, the RAN controller 102 is configured to perform operations related to real-time handover of the plurality of UEs 112a-e. In some examples, the RAN controller 102 may be implemented via a virtualized application that is xApps i.e., xApp-3 and xApp-4 that are configured to virtually perform the operations of the RAN controller 102.

[0045] In an implementation, one or more parameters used by the xApp-4 may include, but not limited to, minimum RSRP/RSRQ Threshold = THo = -114 dBm (for RSRP) or -13 dB (for RSRQ) (Default), RSRP/RSRQ band threshold-1 = THi = -103 dBm (for RSRP) or -9 dB (for RSRQ) (Default), RSRP/RSRQ band threshold-2 = TH2 = -85 dBm (for RSRP) or -5 dB (for RSRQ) (Default), "Average" load threshold-1 = PRBTHI = 0.6 (Default), "Average" load threshold-2 = PRBim = 0.7 (Default), QTHPT (UE per QCI/5QI Throughput Threshold) = 1 Kbps (Default), NMEAS (Number of individual measurements) used or throughput computation = 8 (Default), and A (Inter-measurement interval) = 128 ms (Default).
[0046] The RAN controller 102 may be configured to communicate with a core network (not illustrated in the Figures) including an evolved packet core (EPC) using an "SI" interface. More particularly, the RAN controller 102 may communicate with the core network (not illustrated in the Figures) including Mobility Management Entity (MME) and a User plane entity (UPE) identified as Serving Gateway (S-GW) using Sl-C and Sl-U for control plane and user plane, respectively.
[0047] Each of the plurality of UEs 112a-e periodically measures received signal strengths/qualities from each of the 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 disclosure 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. The measurements in the form of measurement reports (MRs).
[0048] Further, the MRs are sent 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 examples, the MRs may also include signal strength metrics that is the RSRP and/or the RSRQ values.
[0049] In some examples, when the RAN controller 102 receives the MRs and/or the 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 examples, the first HO process and the second HO process are triggered simultaneously in parallel. That is, multiple HO of the UEs can be performed accurately in that the RAN controller 102 may 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.
[0050] 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 plurality of neighbour cells 108a and 108b. The serving cell 110 and the plurality of neighbour cells 108a and 108b may connect to each other via "Xn" interface. The base station 104 and the plurality of 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 plurality of neighbour cells 108a and 108b. In some examples, the base station 104 may be configured to broadcast the HO parameters or the updated HO parameters to the plurality of UEs 112a-e served by the base

station 104. The HO parameters, in one example, may also be communicated to the plurality of neighbour base stations 106a and 106b using the "Xn" interface.
[0051] The plurality of UEs 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.
[0052] 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.
[0053] The RAN controller 102 obtains a serving cell load parameter with respect to a neighbour cell load parameter associated with at least one neighbour cell of the plurality of neighbour cells 108a, 108b. The serving cell load parameter corresponds to a comparative load value of the serving cell 110 with respect to the at least one neighbour cell of the plurality of neighbour cells 108a, 108b.
[0054] The RAN controller 102 identifies the at least one user equipment positioned in the serving cell 110 based on a channel quality index (CQI) and a throughput value. Additionally, the RAN controller 102 transmits the serving cell load parameter with respect to the neighbour cell load parameter associated with the at least one neighbour cell of the plurality of neighbour cells 108a, 108b to at least one identified user equipment. The RAN controller 102 selects the target cell from the plurality of neighbour cells 108a, 108b for the at least one identified user equipment.

[0055] The identification of the at least one user equipment positioned in the serving cell 110 may include determining one or more user equipment from the plurality of user equipments 112a-e positioned in the serving cell 110. Each of one or more determined user equipment has the channel quality index (CQI) less than a predetermined threshold lower CQI. Additionally, the identification of the at least one user equipment positioned in the serving cell 110 may include identifying the at least one user equipment from the one or more determined user equipment positioned in the serving cell 110. The at least one identified user equipment has the throughput value more than a predetermined threshold throughput.
[0056] The selection of the target cell for the at least one identified user equipment may include obtaining at least one quality of service (QoS) class identifier (QCI) level associated with at least one active bearer in the at least one identified user equipment. The at least one QCI level corresponds to a QoS value required by the at least one active bearer in the at least one identified user equipment to provide a service. The at least one active bearer corresponds to connections between the at least one identified user equipment and a packet data network gateway to provide the service.
[0057] Additionally, the selection of the target cell for the at least one identified user equipment may include obtaining a received signal strength value, a first load value and a plurality of second load values for each of the plurality of neighbour cells 108a, 108b. The received signal strength value includes one of the Reference Signal Received Power (RSRP) and the Reference Signal Received Quality (RSRQ). The first load value includes average physical resource block (PRB) values of each of the plurality of neighbour cells 108a, 108b. The plurality of second load values includes average PRB values by the at least one QCI level for each of the plurality of neighbour cells 108a, 108b.
[0058] Additionally, the selection of the target cell for the at least one identified user equipment may include selecting the target cell from the plurality of neighbour cells 108a, 108b based on the at least one QCI level in the at least one identified user equipment and the received signal strength value, the first load value and the plurality of second load values for each the plurality of neighbour cells

108a, 108b. The selection of the target cell from the plurality of neighbour cells 108a, 108b for the at least one identified user equipment is executed when load of the serving cell 110 is greater than load of the at least one neighbour cell of the plurality of neighbour cells 108a, 108b. The selection of the target cell for the at least one identified user equipment further includes receiving at least one A3 event report from the at least one identified user equipment positioned in the serving cell 110.
[0059] The RAN controller 102 may include repeating the identification of the at least one user equipment positioned in the serving cell 110 based on the channel quality index (CQI) after a pre-determined time interval. The identification of the at least one user equipment positioned in the serving cell 110 based on the channel quality index (CQI) is executed when a new value of the serving cell load parameter with respect to the neighbour cell load parameter is identified.
[0060] FIG. 2 illustrates a sequence diagram 200 illustrating a method to perform the real-time handover, herein is implemented through xApp-3 and x-App-4. The xApp-3 and x-App-4 may be enabled to perform the operations (virtually) of identification of at least one user equipment (xApp-3) and selecting a target cell (xApp-4). Unlike conventional mechanism, the RAN controller 102 may be configured to execute two processing threads, each of the two processing threads is executed in parallel. The RAN controller 102 may also be configured to obtain data associated with applications executed at the plurality of UEs 112a-e virtually implemented using a utility xApp.
[0061] The utility xApp may be configured to receive a cell utilization key performance indicator (KPIs) from the serving cell 110 and the plurality of neighbour cells 108a and 108b. In one example, the KPIs indicate current requirements and estimated requirement of bandwidth i.e., indicate a bandwidth of a cell, in each of the 4G and 5G network systems, and the plurality of UEs 112a-e connected to the serving cell 110 and the plurality of neighbour cells 108a and 108b.
[0062] The utility xApp obtains various KPIs and an active bearer information by the plurality of UEs 112a-e. Additionally, the utility xApp processes the various KPIs and the active bearer information (e.g., for averaging or

aggregating) over a pre-determined time interval. The utility xApp stores the various KPIs and the active bearer information in a radio network information base (RNIB) 114 for consumption by the xApps. The functions performed by the Utility xApp may be incorporated with the xApps that makes use of the processed information.
[0063] As shown in FIG. 2, xApp-1 obtains the average Cell Load information and current values of the CIOs from the RNIB and update the CIOs for each serving cell with respect to each of corresponding neighbour, and vice versa, based on the relative loading at the cells 110, 108a and 108b. The updated CIO values are stored back in the RNIB. For each pair of the serving cell 110 and corresponding neighbour cell (any of the 108a or 108b), there will only be one CIO value in the RNIB, and it would be marked as new until its consumed by the xApp-3.
[0064] The xApp-3 identifies the at least one user equipment to send the CIO updates. For identification of the at least one user equipment, the xApp-3 utilizes averaged values of the CQI obtained from the plurality of UEs 112a-e and the throughput value for the plurality of UEs 112a-e indicating level of loading contributed by each UE. Additionally, execution of the xApp-3 for the serving cell 110 is scheduled after the pre-determined time interval following last execution. Furthermore, while the execution, if the xApp-3 finds a CIO value for a neighbour marked as new (i.e., it has not been consumed by the xApp-3 previously), the xApp-3 is relayed to each UE served by the serving cell 110 under consideration with the CQI below the predetermined threshold lower CQI (xApp-3 parameter). The RAN controller 102 may adjust the predetermined threshold lower CQI between a range of prescribed CQI levels (also specified by different xApp-3 parameters) such that the number of the plurality of UEs 112a-e to which the CIO updates are sent is kept below a desired number (xApp-3 parameter).
[0065] The xApp-3 utilized one or more handover parameters to identify the at least one user equipment. The one or more handover parameters include, but not limited to, a lower CQI threshold, a higher CQI threshold, UE throughput

threshold, number of the plurality of UEs, an inter measurement interval and throughput computation.
[0066] The xApp-4 recommends the target cell for the real-time handover for the at least one identified UE that has reported the at least one A3 event. Additionally, the xApp-4 subscribes to the at least one A3 event and RSRP/RSRQ reports when the CIOs are updated by the xApp-1 making the at least one A3 event more likely. The xApp-4 utilized one or more parameters to recommend the target cell for the real-time handover for the at least one identified UE. The one or more parameters include a minimum RSRP/RSRQ threshold, a first RSRP/RSRQ band threshold, a second RSRP/RSRQ band threshold, a first average load threshold, a second average load threshold, UE per QCI throughput threshold and an inter measurement interval.
[0067] FIG. 3 in conjunction with the FIG. 1 illustrates a wireless communication system. The wireless communication system may consist of various network components connected via wireless networks. The wireless networks may comprise of any wireless connectivity technology such as radio links, millimeter wave, etc. In the present disclosure, the wireless communication system may include one or more controller connected with radio access networks, which are further connected with a plurality of user equipments. That is, the wireless communication system includes the Open-Radio access network (O-RAN) environment 300. The Open-Radio Access Network (O-RAN) environment 300 includes a Service Management and Orchestration (SMO) framework 302 and a radio access network (RAN) intelligent controller (RIC) 308 connected to the RAN (100). The SMO 302 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 environment 300. 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 302 may include, for example, data related to a bandwidth of a wireless communication network and at least one of the plurality of UEs 112a-e.

[0068] 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 examples, 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 plurality of 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 of the base stations 104, 106a, 106b, 106c... 106n may connect to one or more antennas.
[0069] Referring back to FIG. 3, the RIC 308 may be a non-real-time-radio intelligent controller (Non-RT-RIC) 304 and a near-real-time-radio intelligent controller (Near-RT-RIC) 306. 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.
[0070] The Non-RT-RIC 304 may be configured to support intelligent RAN optimization in non-real-time. Further, the Non-RT-RIC 304 may be configured to leverage the SMO services and may be a part of the SMO 302. One such advantage of configuring the RAN 100 within the O-RAN environment 300 is leveraging the intellectualization ("Artificial intelligence (AI)/Machine Learning (ML)) of the Non-RT-RIC 304 and the Near-RT-RIC 306.
[0071] The Near-RT-RIC 306 may host plurality of xApps. The xApps (at the Near-RT-RIC 306) 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 304. An "01" interface collects data for training in the Non-RT RIC 304 integrated with the SMO 302.
[0072] 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 the at least one A3 event 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 environment 300 includes the virtualized network architecture having at least one RAN controller 102 that is configured to perform the operations as detailed above.
[0073] FIG. 4 illustrates a flow chart 400 of a method to identify the at least one user equipment for the real-time handover and select the target cell in the open RAN (O-RAN) environment 300. It may be noted that in order to explain the method steps of the flow chart 400, references will be made to the elements explained in FIG. 1 and FIG. 3. The flow chart 400 starts at step 402. At step 404, the method includes obtaining the serving cell load parameter with respect to the neighbour cell load parameter associated with the at least one neighbour cell of the plurality of neighbour cells 108a, 108b. At step 406, the method includes identifying the at least one user equipment positioned in the serving cell 110 based on the channel quality index (CQI) and the throughput value. At step 408, the method includes transmitting the serving cell load parameter with respect to the neighbour cell load parameter associated with the at least one neighbour cell to the at least one identified user equipment. At step 410, the method includes selecting the target cell from the plurality of neighbour cells 108a, 108b for the at least one identified user equipment.
[0074] The flow chart 400 terminates at step 412. It may be noted that the flow chart 400 is explained to have above stated process steps; however, those skilled in the art would appreciate that the flow chart 400 may have more/less number of process steps which may enable all the above stated implementations of the present disclosure.
[0075] The various actions, acts, blocks, steps, or the like in the flow chart 400 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.

[0076] 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.
[0077] 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.
[0078] 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.
[0079] 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).
[0080] 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.
[0081] 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.
[0082] 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.
[0083] 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.
[0084] 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.

[0085] 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.
[0086] 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 for real-time handover
and selecting a target cell by a Radio access network (RAN) controller (102) in an
open RAN (O-RAN) environment (300), the O-RAN environment (300) has a
virtualized network architecture comprising the RAN controller (102), the RAN
controller (102) is connected with a plurality of user equipments (112a, 112b, 112c,
112d and 112e) positioned in a serving cell (110), the serving cell (110) covers a
location for serving the plurality of user equipments (112a-e), the serving cell (110)
is adjacent to a plurality of neighbour cells (108a, 108b), the method comprising:
obtaining a serving cell load parameter with respect to a neighbour cell load parameter associated with at least one neighbour cell of the plurality of neighbour cells (108a, 108b), wherein the serving cell load parameter corresponds to a comparative load value of the serving cell (110) with respect to the at least one neighbour cell of the plurality of neighbour cells (108a, 108b);
identifying the at least one user equipment positioned in the serving cell (110) based on a channel quality index (CQI) and a throughput value;
transmitting the serving cell load parameter with respect to the neighbour cell load parameter associated with the at least one neighbour cell of the plurality of neighbour cells (108a, 108b) to at least one identified user equipment; and
selecting the target cell from the plurality of neighbour cells (108a, 108b) for the at least one identified user equipment.
2. The method as recited in claim 1, wherein the identification of the at least
one user equipment positioned in the serving cell (110) further comprising:
determining one or more user equipment from the plurality of user equipments (112a-e) positioned in the serving cell (110), wherein each of one or more determined user equipment has the channel quality index (CQI) less than a predetermined threshold lower CQI; and

identifying the at least one user equipment from the one or more determined user equipment positioned in the serving cell (110), wherein the at least one identified user equipment has the throughput value more than a predetermined threshold throughput.
3. The method as recited in claim 1, further comprising repeating the identification of the at least one user equipment positioned in the serving cell (110) based on the channel quality index after a pre-determined time interval.
4. The method as recited in claim 1, wherein the selection of the target cell from the plurality of neighbour cells (108a, 108b) for the at least one identified user equipment further comprising:
obtaining at least one quality of service (QoS) class identifier (QCI) level associated with at least one active bearer in the at least one identified user equipment, wherein the at least one QCI level corresponds to a QoS value required by the at least one active bearer in the at least one identified user equipment to provide a service, wherein the at least one active bearer corresponds to connections between the at least one identified user equipment and a packet data network gateway to provide the service;
obtaining a received signal strength value, a first load value and a plurality of second load values for each of the plurality of neighbour cells (108a, 108b), wherein the received signal strength value comprises one of Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ), wherein the first load value comprises average physical resource block (PRB) values of each of the plurality of neighbour cells (108a, 108b), wherein the plurality of second load values comprises average PRB values by the at least one QCI level for each of the plurality of neighbour cells (108a, 108b); and
selecting the target cell from the plurality of neighbour cells (108a, 108b) based on the at least one QCI level in the at least one identified user equipment and the received signal strength value, the first load value and

the plurality of second load values for each the plurality of neighbour cells (108a, 108b).
5. The method as recited in claim 1, wherein the identification of the at least one user equipment positioned in the serving cell (110) based on the channel quality index (CQI) is executed when a new value of the serving cell load parameter with respect to the neighbour cell load parameter is identified.
6. The method as recited in claim 1, wherein the selection of the target cell from the plurality of neighbour cells (108a, 108b) for the at least one identified user equipment is executed when load of the serving cell (110) is greater than load of the at least one neighbour cell of the plurality of neighbour cells (108a, 108b).
7. The method as recited in claim 1, wherein the selection of the target cell from the plurality of neighbour cells (108a, 108b) for the at least one identified user equipment further comprising:
receiving at least one A3 event report from the at least one identified user equipment positioned in the serving cell (110).