Methods to avoid repetitive handover oscillations at a known geographical location

Abstract

A method, system and apparatus are disclosed. A method in a network node configured to communicate at least with a wireless device (WD) of a plurality of WDs using at least one of a first cell and a second cell is described. The method includes determining, using one or more artificial intelligence (AI) models, whether a forth and back handover (FBHO) event associated with the WD can occur at a location. The FBHO event includes at least a first handover (HO) of the WD from the first cell to the second cell and a second HO of the WD from the second cell to the first cell. The method further includes avoiding triggering at least one HO based on the determination that the FBHO event can occur.

Description

[0001] METHODS TO AVOID REPETITIVE HANDOVER OSCILLATIONS AT A KNOWN GEOGRAPHICAL LOCATION

[0002] TECHNICAL FIELD

[0003] The present disclosure relates to wireless communications, and in particular, to management of handovers between wireless communication cells.

[0004] BACKGROUND

[0005] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD) (e.g., user equipment (UE)), as well as communication between network nodes and between WDs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0006] Typically, the size of the area covered by a cell in a mobile wireless network depends on many factors. The following are example factors.

[0007] Example 1 : The hardware capacity of a Radio Unit (RU).

[0008] A cell may be a software entity and may is equipped with a set of hardware components like an antenna, a RU which is a hardware card, a digital unit (DU) which is another hardware card, the cabling between these components, etc. One of the roles of the RU is to amplify the outgoing analog signal and send it to the antennas which amplifies it further before transmitting it over the air interface. The RU may be a hardware unit having a maximum transmitting power capacity such as 100 Watts (W), 120 W, 160 W, etc. The higher the power capacity of the RU, the more expensive it may be to buy for the operator. However, higher power capacity may add radio coverage for the cell to which it is attached.

[0009] Example 2: The software capacity of a RU or a DU (licensing)

[0010] Even though the operator might have installed a RU of 160 W, the operator may use and pay only for a portion such as use and pay only for 100 W out of the 160 W. The reduced use may be determined by a licensing agreement.

[0011] Example 3: Radio configurations An operator may optimize and / or control a network by remotely adjusting any parameters, e.g. antenna tilt and power of the transmitted radio signal, etc. In one example, the operator may change the value of the tilt of the antennas, which affects the size of the radio coverage of the cell. For low values of antenna tilt, the size of coverage may be enlarged, while high values of antenna tilt may cause the size of the cell to be reduced. Once the operator has optimized the border of the cells in the network, then handover procedures may be triggered at the border of the cells. However, in practice, the handover procedures are triggered not only at the border cells but also on any other location of the cell, which may be due to any of the following factors.

[0012] • Nature of the radio signal: Based on the physics of the radio signal, the higher the frequency that is used to carry a radio signal, the less the radio signal penetrates indoor locations.

[0013] • Obstacle and the distance between an indoor / outdoor location and the antennas of a cell: the more obstacles there are and / or the more distant the WD is from the antennas of the cell, then the weaker the radio signal is.

[0014] • Building a new network takes time: In order to provide radio coverage of a Radio Access Technology (RAT), e.g. 5G, in a geographical area, typically a few weeks and / or months are needed. While the 5G coverage is being brought in one area of the city, another part of the city may not have 5G coverage yet, which may create a border line between 5G cells and 4G cells in some areas.

[0015] • Outage of the cell: Any cell and / or radio node in the network may go into a temporary outage due to many factors, e.g. a hardware or a software issue. During that period of the temporary outage, a high number of forth and back handovers may be triggered.

[0016] That is, handovers are not only triggered at the border of the cells, but as different radio signals coming from different cells reach the same WD, handover procedures may be triggered repetitively at any location inside the cell. Further, at any location in the cell and within a period of time, a WD may experience multiple handover oscillations between two cells. Conventional radio features may attempt avoidance of such oscillations, but not without problems. For example, a WD in connected mode and being served by a first cell, e.g. 5G cell, performs continuously radio measurement of the radio conditions received from the first cell, e.g., the serving cell, and from at least one neighboring cell, i.e., a second cell. Neighboring cells may be of the same or of different RAT as of a first cell.

[0017] When a radio measurement event is validated at the WD side towards a second cell (e.g., neighbor cell), it sends a Radio Resource Control (RRC) MeasurementReport to the cell and a handover is triggered for that WD from the first cell to the second cell. The radio measurement events may be defined in 3GPP Technical Specification (TS) specification 38.331 vl6.13.0. The following are some examples of the definition of radio measurement event:

[0018] • Event Al (Serving becomes better than threshold)

[0019] • Event A2 (Serving becomes worse than threshold)

[0020] • Event A3 (Neighbor becomes offset better than a Special Cell (SpCell))

[0021] • Event B2 (Primary Cell (PCell) becomes worse than threshold 1 and inter RAT neighbor becomes better than threshold2)

[0022] Below is an example of event A3, where the parameters in the formula below are described in the RRC specification 3GPP TS 38.331 vl6.13.0.

[0023] Mn + Ofn + Ocn - Hys > Mp + Ofp + Ocp + Off

[0024] Typically, the value of Ofn, Ocn, Ofp and Ocp are equal to 0, so that in its simplest format, event A3 is validated when Mn - Hys > Mp + Off. That is, when the radio conditions at neighbour cell (Mn), e.g., a second cell, are better than the WD radio conditions at serving cell (Ms), e.g., a first cell, by a certain margin that could be calculated as the sum of Hys + Off. The parameters may be configurable and optimized individually in the network.

[0025] Referring again to the radio features, there are radio features that attempt avoiding the occurrences of handover oscillations in the wireless network, also called ping pong handovers. Some of these features take into consideration the time spent by the WD on last cell and on the current cell. FIG. 1 shows an example process that attempts to avoid oscillations. At time tl, the WD makes a first handover from a first cell towards a second cell. The WD stays a certain time on the second cell, e.g., T lastcell, and then a second handover is triggered at time t2 from the second cell towards the first cell. During the handover procedure the value of T lastcell is communicated from the second cell to the first cell via one dedicated signalling message, e.g., if Xn handover is executed from the second cell to the first cell, then the value of T lastcell may be included in Information Element (IE), UE History Information, that is included in an XnAP HANDOVER REQUEST message. While back on the first cell, if, at time t3, a radio measurement event, e.g., event A3, is validated by the WD that includes a potential handover from the first cell to the second cell. The conventional radio features include measuring the period of time, e.g., T current, on the first cell, comparing T lastcell and T current with some predefined threshold, and making determining whether to reject the potential handover or to allow that potential handover. The following are two examples of decisions made by an existing algorithm:

[0026] • In case 200 ms < T current < 2000 ms and T lastcell < 2000 ms, then an extra 2 dB margin is applied in order to prevent a fast handover from the first cell to the second cell; or

[0027] • if T current is > 5 seconds then a handover is allowed from the first cell to the second cell.

[0028] There are at least two concerns with this conventional radio feature. The network and / or operator is not aware of whether such oscillations are repeated at the same location. In addition, a first handover is allowed from the first cell to the second cell, then a second handover is also allowed from the second cell to the first cell, where avoidance of a third potential handover may be prevented. In other words, even though the oscillations may be repeated each time at the same location and the radio conditions on the first cell may be still acceptable, the WD is performing undesirable handovers.

[0029] SUMMARY

[0030] Some embodiments advantageously provide methods, systems, and apparatuses for avoiding handover oscillations at location associated with a wireless device, a network node, and / or one or more cells.

[0031] According to one aspect, a method in a network node configured to communicate at least with a wireless device (WD) of a plurality of WDs using at least one of a first cell and a second cell is described. The method includes determining, using one or more artificial intelligence (Al) models, whether a forth and back handover (FBHO) event associated with the WD can occur at a location. The FBHO event includes at least a first handover (HO) of the WD from the first cell to the second cell and a second HO of the WD from the second cell to the first cell. The method further includes avoiding triggering at least one HO based on the determination that the FBHO event can occur. In some embodiments, the method further includes storing location information associated with the location of the WD at least once the WD experiences, at a first time, tO, the FBHO event within a first predetermined period of time (T).

[0032] In some other embodiments, the method further includes obtaining radio frequency (RF) metrics samples from the plurality of WDs and training at least one Al model of the one or more Al models using the RF metrics samples to predict whether an HO can be associated with the FBHO event.

[0033] In some embodiments, the method further includes receiving, via the first cell, at second time (tl) a measurement report including a radio measurement event towards the second cell and avoiding the at least one HO by postponing an HO triggering for a second predetermined period of time (Tl).

[0034] In some other embodiments, the measurement report is a radio resource control measurement report.

[0035] In some embodiments, the method further includes, at the expiry of Tl, transmitting an HO command to the WD requesting the WD to communicate using the second cell or avoiding transmission of the HO command to the WD if the WD stops reporting additional measurements reports to the network node.

[0036] In some other embodiments, the method further includes triggering the WD to ignore contents of the HO command at a third time equal to the sum of tl and Tl when HO conditions are not fulfilled and receiving an indication indicating that the HO command was ignored by the WD.

[0037] In some embodiments, the indication includes an FBHO occurrence value (e.g., value of forth&back HO occur ence) .

[0038] In some other embodiments, the method further includes triggering the WD to perform an action based on the contents of the HO command at the third time when the HO conditions are fulfilled.

[0039] In some embodiments, the action corresponds to the triggering of the at least one HO and includes causing the WD to communicate using the second cell.

[0040] In some other embodiments, the method further includes triggering the at least one HO based on the determination that the FBHO event will not occur.

[0041] According to another aspect, a network node configured to communicate at least with a wireless device (WD) of a plurality of WDs using at least one of a first cell and a second cell is described. The network node is configured to determine, using one or more artificial intelligence (Al) models, whether a forth and back handover (FBHO) event associated with the WD can occur at a location. The FBHO event includes at least a first handover (HO) of the WD from the first cell to the second cell and a second HO of the WD from the second cell to the first cell. The network node is further configured to avoid triggering at least one HO based on the determination of whether to avoid at least one HO of the WD.

[0042] In some embodiments, the network node is configured to store location information associated with the location of the WD at least once the WD experiences at a first time (tO) the FBHO event within a first predetermined period of time (T).

[0043] In some other embodiments, the network node is configured to obtain radio frequency (RF) metrics samples from the plurality of WD and train at least one Al model of the one or more Al models using the RF metrics samples to predict whether an HO can be associated with the FBHO.

[0044] In some embodiments, the network node is configured to receive, via the first cell, at second time (tl) a measurement report including a radio measurement event towards the second cell and avoid the at least one HO by postponing an HO triggering for a second predetermined period of time (Tl).

[0045] In some other embodiments, the measurement report is a radio resource control measurement report.

[0046] In some embodiments, the network node is configured to, at the expiry of Tl, transmit an HO command to the WD requesting the WD to communicate using the second cell or avoid transmission of the HO command to the WD if the WD stops reporting additional measurements reports to the network node.

[0047] In some other embodiments, the network node is configured to trigger the WD to ignore contents of the HO command at a third time equal to the sum of tl and Tl when HO conditions are not fulfilled and receive an indication indicating that the HO command was ignored by the WD.

[0048] In some embodiments, the indication includes an FBHO occurrence value.

[0049] In some other embodiments, the network node is configured to trigger the WD to perform an action based on the contents of the HO command at the third time when the HO conditions are fulfilled.

[0050] In some embodiments, the action corresponds to the triggering of the at least one HO and includes causing the WD to communicate using the second cell.

[0051] In some other embodiments, the network node is configured to trigger the at least one HO based on the determination that the FBHO event will not occur. According to one aspect, a method in a wireless device (WD) configured to communicate with the network node is described. The method includes determining, using one or more artificial intelligence (Al) models, whether a forth and back handover (FBHO) event associated with the WD can occur at a location. The FBHO event includes at least a first handover (HO) of the WD from the first cell to the second cell and a second HO of the WD from the second cell to the first cell. The method further includes avoiding triggering at least one HO based on the determination that the FBHO event can occur.

[0052] In some embodiments, the method further includes storing location information associated with the location of the WD at least once the WD experiences, at a first time (tO), the FBHO event within a first predetermined period of time (T).

[0053] In some other embodiments, the method further includes obtaining radio frequency (RF) metrics samples from the first cell and the second cell and training at least one Al model of the one or more Al models using the RF metrics samples to predict whether an HO can be associated with the FBHO event.

[0054] In some embodiments, the method further includes as long as the radio conditions are good at first cell, avoiding the at least one HO by not sending a measurement report including a radio measurement event towards the second cell and waiting for the WD to return to a location where the first cell becomes the best cell, or postponing an HO triggering for a second predetermined period of time (T) or when the RSRP margin between the first cell and the second cell exceeds a predefined threshold Y.

[0055] In some other embodiments, the method further includes sending to the first cell an indication indicating that the HO command was ignored by the WD and where the indication includes an FBHO occurrence value.

[0056] In some embodiments, the method further includes triggering the at least one HO based on the determination that the FBHO event will not occur.

[0057] According to another aspect, a wireless device (WD) configured to communicate with the network node is described. The WD is configured to determine, using one or more artificial intelligence (Al) models, whether a forth and back handover (FBHO) event associated with the WD can occur at a location. The FBHO event includes at least a first handover (HO) of the WD from the first cell to the second cell and a second HO of the WD from the second cell to the first cell. The WD is further configured to avoid triggering at least one HO based on the determination that the FBHO event can occur.

[0058] In some embodiments, the WD is further configured to store location information associated with the location of the WD at least once the WD experiences, at a first time (tO), the FBHO event within a first predetermined period of time (T).

[0059] In some other embodiments, the WD is further configured to obtain radio frequency (RF) metrics samples from the first cell and the second cell and train at least one Al model of the one or more Al models using the RF metrics samples to predict whether an HO can be associated with the FBHO event.

[0060] In some embodiments, the WD is further configured to as long as the radio conditions are good at first cell, avoid the at least one HO by not sending a measurement report including a radio measurement event towards the second cell and wait for the WD to return to a location where the first cell becomes the best cell, or postpone an HO triggering for a second predetermined period of time (T) or when the RSRP margin between the first cell and the second cell exceeds a predefined threshold Y.

[0061] In some other embodiments, the WD is further configured to send to the first cell an indication indicating that the HO command was ignored by the WD and where the indication includes an FBHO occurrence value.

[0062] In some embodiments, the WD is further configured to trigger the at least one HO based on the determination that the FBHO event will not occur.

[0063] BRIEF DESCRIPTION OF THE DRAWINGS

[0064] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0065] FIG. 1 shows an example oscillation feature;

[0066] FIG. 2 is a schematic diagram of an exemplary network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

[0067] FIG. 3 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure; FIG. 4 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure;

[0068] FIG. 5 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

[0069] FIG. 6 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

[0070] FIG. 7 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;

[0071] FIG. 8 is a flowchart of an exemplary process in a network node according to some embodiments of the present disclosure;

[0072] FIG. 9 is a flowchart of an exemplary process in a network node according to some embodiments of the present disclosure;

[0073] FIG. 10 is a flowchart of an example method according to some embodiments of the present disclosure;

[0074] FIG. 11 is a flowchart of an example method according to some embodiments of the present disclosure; and

[0075] FIG. 12 is a flowchart of an example method according to some embodiments of the present disclosure.

[0076] DETAILED DESCRIPTION

[0077] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to avoiding handover oscillations at location associated with a wireless device, a network node, and / or one or more cells. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0078] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0079] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0080] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0081] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi -standard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rdparty node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

[0082] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and / or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

[0083] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi -cell / multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0084] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0085] In some embodiments, the term a “forth and back handover” (FBHO) (or FBHO event) is used and may refer to a first handover of the WD from a first cell to a second cell and a second handover of the WD from the second cell to the first cell. In some embodiments, an FBHO or FBHO event may include multiple occurrences of one or both of the first handover and the second handover. Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0086] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0087] Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 2 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that may support standards such as LTE and / or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Any network node 16 such as network node 16c may be configured to communicate with a wireless device 22 via one or more cells such as cells 19a, 19b (collectively referred to as cells 19). Although cells 19 are shown within coverage area 18c for ease of understanding, cells 19 are not limited as such and may be within or outside any coverage area 18 and be usable by any network node 16 to communicate with any WD 22. In some embodiments, a coverage area 18 may have one or more cells 19. A cell 19 may cover at least a portion of at least one coverage area 18. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.

[0088] Also, it is contemplated that a WD 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0089] The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more subnetworks (not shown).

[0090] The communication system of FIG. 2 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and / or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24. A network node 16 is configured to include a NN management unit 32 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., NN functions. A wireless device 22 is configured to include a WD management unit 34 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., WD functions.

[0091] Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 3. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and / or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and / or read from) memory 46, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0092] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 48 and / or the host application 50 may include instructions that, when executed by the processor 44 and / or processing circuitry 42, causes the processor 44 and / or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24. The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and / or receive from the network node 16 and or the wireless device 22. The processing circuitry 42 of the host computer 24 may include a host management unit 54 configured to enable the service provider to observe / monitor / control / transmit to / receive from the network node 16 and or the wireless device 22.

[0093] The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and / or through one or more intermediate networks 30 outside the communication system 10.

[0094] In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read- Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read- Only Memory).

[0095] Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or processing circuitry 68, causes the processor 70 and / or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include NN management unit 32 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., NN functions.

[0096] The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0097] The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) memory 88, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0098] Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

[0099] The processing circuitry 84 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or processing circuitry 84, causes the processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the wireless device 22 may include WD management unit 34 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., WD functions.

[0100] In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 3 and independently, the surrounding network topology may be that of FIG. 2. In FIG. 3, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[0101] The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

[0102] In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.

[0103] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and / or the network node’s 16 processing circuitry 68 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the WD 22, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the WD 22.

[0104] In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and / or comprises a radio interface 82 and / or processing circuitry 84 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the network node 16, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the network node 16.

[0105] Although FIGS. 2 and 3 show various “units” such as NN management unit 32, and WD management unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0106] FIG. 4 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS. 2 and 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 3. In a first step of the method, the host computer 24 provides user data (Block SI 00). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).

[0107] FIG. 5 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14).

[0108] FIG. 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block SI 16). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

[0109] FIG. 7 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).

[0110] FIG. 8 is a flowchart of an exemplary process (i.e., method) in a network node 16. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including NN management unit 32), processor 70, radio interface 62 and / or communication interface 60. Network node 16 such as via processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60 is configured to determine (Block SI 34), using one or more artificial intelligence (Al) models, whether a forth and back handover (FBHO) event associated with the WD 22 can occur at a location. The FBHO event includes at least a first handover (HO) of the WD 22 from the first cell 19 to the second cell 19 and a second HO of the WD 22 from the second cell 19 to the first cell 19. The network node 16 is further configured to avoid (Block S136) triggering at least one HO based on the determination of whether to avoid at least one HO of the WD 22.

[0111] In some embodiments, the method further includes storing location information associated with the location of the WD 22 at least once the WD 22 experiences, at a first time, tO, the FBHO event within a first predetermined period of time (T).

[0112] In some other embodiments, the method further includes obtaining radio frequency (RF) metrics samples from the plurality of WDs 22 and training at least one Al model of the one or more Al models using the RF metrics samples to predict whether an HO can be associated with the FBHO event.

[0113] In some embodiments, the method further includes receiving, via the first cell 19, at second time (tl) a measurement report including a radio measurement event towards the second cell 19 and avoiding the at least one HO by postponing an HO triggering for a second predetermined period of time (Tl).

[0114] In some other embodiments, the measurement report is a radio resource control measurement report.

[0115] In some embodiments, the method further includes, at the expiry of Tl, transmitting an HO command to the WD 22 requesting the WD 22 to communicate using the second cell 19 or avoiding transmission of the HO command to the WD 22 if the WD 22 stops reporting additional measurements reports to the network node.

[0116] In some other embodiments, the method further includes triggering the WD 22 to ignore contents of the HO command at a third time equal to the sum of tl and Tl when HO conditions are not fulfilled and receiving an indication indicating that the HO command was ignored by the WD 22.

[0117] In some embodiments, the indication includes an FBHO occurrence value (e.g., value of forth&back HO occur ence) .

[0118] In some other embodiments, the method further includes triggering the WD 22 to perform an action based on the contents of the HO command at the third time when the HO conditions are fulfilled.

[0119] In some embodiments, the action corresponds to the triggering of the at least one HO and includes causing the WD 22 to communicate using the second cell 19.

[0120] In some other embodiments, the method further includes triggering the at least one HO based on the determination that the FBHO event will not occur.

[0121] FIG. 9 is a flowchart of an exemplary process (i.e., method) in a WD 22. One or more blocks described herein may be performed by one or more elements of WD 22 such as by one or more of processing circuitry 84 (including WD management unit 34), processor 86, radio interface 82. WD 22 such as via processing circuitry 84 and / or processor 86 and / or radio interface 82 is configured to determine (Block S138), using one or more artificial intelligence (Al) models, whether a forth and back handover (FBHO) event associated with the WD 22 can occur at a location. The FBHO event includes at least a first handover (HO) of the WD 22 from the first cell 19 to the second cell 19 and a second HO of the WD 22 from the second cell 19 to the first cell 19. The WD 22 is further configured to avoid (Block S140) triggering at least one HO based on the determination that the FBHO event can occur.

[0122] In some embodiments, the method further includes storing location information associated with the location of the WD 22 at least once the WD 22 experiences, at a first time (tO), the FBHO event within a first predetermined period of time (T).

[0123] In some other embodiments, the method further includes obtaining radio frequency (RF) metrics samples from the first cell 19 and the second cell 19 and training at least one Al model of the one or more Al models using the RF metrics samples to predict whether an HO can be associated with the FBHO event.

[0124] In some embodiments, the method further includes as long as the radio conditions are good at first cell 19, avoiding the at least one HO by not sending a measurement report including a radio measurement event towards the second cell 19 and waiting for the WD 22 to return to a location where the first cell 19 becomes the best cell 19, or postponing an HO triggering for a second predetermined period of time (T) or when the RSRP margin between the first cell 19 and the second cell 19 exceeds a predefined threshold Y.

[0125] In some other embodiments, the method further includes sending to the first cell 19 an indication indicating that the HO command was ignored by the WD 22 and where the indication includes an FBHO occurrence value.

[0126] In some embodiments, the method further includes triggering the at least one HO based on the determination that the FBHO event will not occur.

[0127] In some other embodiments, the determination that the FBHO event will not occur may refer to the determination that the FBHO event has a probability to occur (e.g., within a predetermined period of time) that is lower than a predetermined probability. In some embodiments, the determination that the FBHO event will not occur refers to the determination that the FBHO event cannot occur (e.g., such as within a predetermined period of time) at the location.

[0128] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for avoiding handover oscillations at location associated with a WD 22, a network node 16, and / or one or more cells 19.

[0129] In some embodiments, the term “UE drth&back HO detection entity" (or UE Jo' rth&back HO detection entity functions) is used and may refer to any steps and / or tasks and / or processes and / or functions and / or features performed by any of the components of system 10 such as network node 16 (and / or any of its components such as NN management unit 32), WD 22 (and / or any of its components such as WD management unit 34), and / or host computer 24 (and / or any of its components such as host management unit 54). In some other embodiments,

[0130] UE brth&back HO detection entity refers to a unit such as NN management unit 32, WD management unit 34, host management unit 54, etc.

[0131] In conventional systems, neither the WD location nor the radio conditions of the serving cell are taken into consideration. Knowing the location where such oscillations are occurring may be beneficial for troubleshooting of the oscillations. In one example, by using the location, the operator or any network automation tool may adjust the antennas tilt and / or transmission power of neighboring cells in order to avoid such oscillations.

[0132] In some embodiments, a first method is implemented at a WD 22 and may include detecting of a forth and back handover and / or determining whether to avoid the handover. An Artificial Intelligence (Al) and / or Machine Learning (ML) entity is implemented at the WD 22. The Al and / or ML entity may refer to one or more functions performed as part of the method. The one or more functions may include predicting, by the WD 22, the occurrence of a forth and back handover. In case the Al and ML entity detects one potential forth and back handover, rather than the WD 22 sending to the first cell an RRC MeasurementReport that includes a radio measurement event, e.g. event A3, in order for the first cell 19 to trigger a handover procedure towards the second cell 19, the WD 22 avoids sending the RRC MeasurementReport and behaves according to one of the following two features:

[0133] • First feature (Feature 1): Even though a radio measurement event, e.g. A3, has occurred, as long as the WD 22 has good radio conditions from the first cell 19, WD 22 does not send the RRC MeasurementReport and waits for the WD 22 to return to a location where the first cell 19 becomes best cell 19.

[0134] • Second feature (Feature 2): When a radio measurement event, e.g. A3, has occurred, even though the WD 22 has still good radio conditions from the first cell, WD 22 triggers a handover procedure if one of the below two conditions is met: o First condition (Condition 1): A new timer (T) has expired. o Second condition (condition 2): A Reference Signal Received Power (RSRP) margin (Y) between the first cell 19 and the second cell 19 is met).

[0135] Some other embodiments provide a Feature 3 associated with a second method that includes the detection of a forth and back handover event at the WD 22. The decision to avoid the event is made at the network node 16. The Al and ML entity implemented at the WD 22 may perform the detection of a forth and back handover at the WD. However, the avoidance of triggering a handover procedure is performed by the network node. A parameter, Q. . forth&back HO occur ence. coded into 1 bit, may be added to an RRC MeasurementReport message as follows:

[0136] • If the WD 22 detects a forth and back handover then the WD 22 sends an RRC MeasurementReport that includes forth&back HO occurence = 1.

[0137] • Otherwise, when the WD 22 sends a RRC MeasurementReport, WD 22 sets forth&back HO occurence = 0.

[0138] • When the first cell 19 (serving cell) receives the RRC MeasurementReport from the WD 22, it may perform the following: o If forth&back HO occurence = 0, a handover towards the second cell 19. o If forth&back HO occurence = 1, the handover towards the second cell 19 is not triggered by the first cell 19, which may be done in order to avoid the forth and back handover.

[0139] In one or more embodiments, HO occurence may a value indicative of the number of FBHO occurrences and referred to as an FBHO occurrence value. In some embodiments provide a Feature 4 associated with a second method that includes the detection of a forth and back handover event as well the decision to avoid the event, both performed at the network node. The Al and / or ML entity may be used by the network node to detect a forth and back handover and / or perform any other actions.

[0140] In some other embodiments, when the first cell receives at time, e.g. tl, an RRC MeasurementReport with a radio measurement event towards the second cell and if a forth and back handover is detected by the Al and / or ML entity, the first cell executes the following two actions: • Rather than immediately triggering a handover procedure, the first cell may postpone the handover triggering for a period of time, e.g., Tl.

[0141] • At the expiry of Tl, the first cell may send a handover command to the WD 22 in order to move to the second cell, if the conditions of the handover are still met because more RRC MeasurementReports have been received in that period of time Tl.

[0142] One or more embodiments provide reduction of unnecessary handover oscillations while avoiding a degradation in the radio conditions of the WD 22 and reduce processing at the radio nodes as multiple subscribers may be experiencing such types of handover oscillations. Such reductions may also reduce the energy consumption of in the network.

[0143] Some embodiments provide a first method (i.e., method 1) implemented by WD 22 such as to avoid sending a measurement report (e.g., a radio MeasurementReporf) during an expected handover event such as a forth and back handover. More specifically, a procedure implemented at the WD side may be performed such as to avoid a repetitive forth and back handover at a predetermined location (e.g., location X). FIG. 10 shows an example first method according to the principles of some embodiments.

[0144] Step S200: An Al (and / or ML) entity that detects the occurrence & location of forth & back handover is implemented at the WD 22

[0145] An Al entity may be implemented at the WD 22 such as implemented by WD management unit 34. The Al entity and / or functions associated with the Al entity may be referred to as UE drth&back HO detection entity . One or more functions of UE Jo' rth&back HO detection entity may be triggered at time tO. In some embodiments, each time a WD 22, e.g., a first WD 22, being served by a first cell 19 experiences the occurrence of a forth and back handover between the first cell 19 and a second cell 19, the first WD 22 may tag location X and the date at which that event has occurred. The occurrence of a forth and back handover between the first cell 19 and a second cell 19 may be when the first WD 22 has experienced a handover procedure from the first cell 19 to the second cell 19, and then another handover procedure from the second cell 19 to the first cell 19 within period T.

[0146] In some embodiments, location X may refer to an area (e.g., a circle that has a center location X and a radius of few meters). In some embodiments, a first procedure may be performed. The first procedure may include WD 22 detecting a forth and back handover. If the tagging occurs multiple time at location X, then location X may be considered as a location where repetitive forth and back handover may occur. The following actions may be performed (e.g., if the tagging occurs multiple times).

[0147] The first WD 22 may store, such as in a dataset, the following information:

[0148] 1. The geographical location X, e.g., Global Positioning System (GPS) coordinates, of WD 22 at time of the occurrence of the forth and back handover.

[0149] 2. Other information such as: a. Reference Signal Received Power (RSRP) of the serving cell 19; b. Reference Signal Received Quality (RSRQ) of the serving cell 19; c. Number of detected neighbor cells 19; d. N strongest neighbors (e.g., neighbor cells 19) sorted by the level of RSRP from 1 to N, and the following information for each one: i. Physical Cell Identity (PCI) Neighbor 1; ii. RSRP Neighbor 1; iii. RSRQ Neighbor 1; iv. RSRP of any Neighbor between 2-(N-l); v. RSRQ of any Neighbor between 2-(N-l); vi. PCI Neighbor N; vii. RSRP Neighbor N; and viii. RSRQ Neighbor N.

[0150] 3. Date or date information such as time, e.g. T, and day of the week.

[0151] WD 22 may also increase by 1 the number of occurrences of forth and back handovers. The total number may be collected based on a predefined period of time, e.g. every week. Other information may also be stored.

[0152] In some embodiments, the prediction of UE drth&back HO detection entity may be based on the WD location which is determined based on GPS information and reference signal information such as by determining “inaccurate GPS” + RSRP&RSRQ fingerprint. The following are nonlimiting examples.

[0153] Example 1 : The first WD 22 is in a first location XI, served by the first cell 19, the strongest neighbor PCI1, where forth and back handover have been detected. The first WD 22 may determine based on this information that a forth and back handover may be triggered or that there is likelihood (e.g., a probability) that the forth and back handover will be triggered.

[0154] Example 2: The first WD 22 is in a first location XI, served by the first cell 19, the strongest neighbor PCI where a forth and back handover has not been detected / caused in the past. The first WD 22 may determine based on this information that a forth and back handover may not be triggered or that is not likely (e.g., a probability lower than a threshold) that the forth and back handover will be triggered.

[0155] Example 3: The first WD 22 is in a first location X, served by the first cell 19, the strongest neighbor PCI, where a forth and back handover has not been detected / caused in the past. The first WD 22 may determine based on this information that a forth and back handover may not be triggered or that is not likely (e.g., a probability lower than a threshold) that the forth and back handover will be triggered.

[0156] In some embodiments, a second procedure may be performed. The second procedure may include WD 22 detecting a forth and back handover such as using the stored dataset (including all the RF metrics) for all the handovers and information indicating whether the handover was unnecessary. WD 22 may train a simple Al classification model to predict if a handover is going to be likely a forth and back handover or not.

[0157] Step S202: Procedures for determining when to launch the entity. In some embodiment, performing the functions of the

[0158] UE Jorth&back HO detection entity (e.g., WD management unit 34 functions) may demand at least a predetermined processing capacity. One or more steps may be performed based on processing capacity and / or battery charge (the battery of WD 22 is low). UE Jorth&back HO detection entity functions may be performed only when necessary, e.g., on demand, based on time and date of previous occurrences of forth and back handover, etc. In some embodiments, steps may be performed to achieve an efficient use of UE Jorth&back HO detection entity functions, such as when performed based on the location of WD 22 as shown in the examples above and not on the time and the date when forth and back handovers occur.

[0159] In some embodiments, the time and the day of the week are stored by UE Jorth&back HO detection entity . In some other embodiments, UE Jorth&back HO detection entity functions may be launched, or triggered, when necessary (or on demand) or all the time. In a first example, a first WD 22 experiences forth and back handover only between 06:00 pm and 07:00 am, which is when the first WD 22 is located at a home location for 7 days. The first WD 22 may trigger

[0160] UE Jorth&back HO detection entity functions only between 06:00 pm and 07:00 am. In a second example, a second WD 22 experiences forth and back handover between 09:00 am and 05:00 pm during the weekdays when the second WD is at an office location. In such scenario, the first WD 22 might trigger

[0161] UE Jorth&back HO detection entity only between 09:00 am and 05:00 pm. In a third example a third WD 22 rarely experiences forth and back handover, which may occur at an office or at home, where the radio coverage of the third WD 22 is covered by one specific cell 19. In such scenario, the third WD 22 may not trigger UE Jo' rth&back HO detection entity functions.

[0162] Step S204: Avoiding transmission o asurementReport.

[0163] Transmitting a radio MeasurementReport may be avoided when predetermined conditions are met and there is a probability greater than a threshold that a handover forth and back procedure is to be triggered. Depending on which of the above two procedures of step S200 for detecting a forth and back handover is used, one or more of the following may be performed.

[0164] In case the first procedure is performed, the next time the WD 22 moves to location X, WD 22 is aware that a forth and back handover may be triggered. At location X, when the WD 22 being served by the first cell 19 validates a handover event, e.g., event A3 is triggered, with a neighboring cell 19 such as the second cell 19, a first action is executed. In case the second procedure is performed, if it is determined that a handover is likely (e.g., a probability greater than a threshold) going to be a forth and back handover then the first action is executed.

[0165] First action: The WD 22 avoids transmitting the RRC MeasurementReport and performs one or more actions according to one of the following two features:

[0166] • Feature 1 : As long as the WD 22 has radio conditions associated with the first cell 19 (e.g., serving cell) that meet or exceed a threshold, then, even though a radio measurement event such as A3 has occurred, the WD 22 does not send the RRC MeasurementReport and waits for the WD 22 to return to a location where the first cell 19 becomes the best cell 19.

[0167] • Feature 2: When the WD 22 has radio conditions associated with the first cell 19 that meet or exceed a threshold, the WD 22 sends an RRC MeasurementReport to the first cell 19 in order to trigger handover procedure towards the second cell 19 if one of below conditions is validated (e.g., met): o First condition (Condition 1) - A timer has expired: A timer, e.g. denoted T, is used. At a known location X where a forth and back handover is expected, when the WD 22, being served by the first cell 19, fulfills a handover condition, T is started. Fulling the handover condition may include a radio measurement event that is validated at the WD side. If the handover fulfillment is ceased before T expiry, then no further action is performed. However, if the handover condition remains after T expiry, a handover procedure is triggered. o Second condition (Condition 2) - A RSRP margin is met: At a known location X where a forth and back handover is expected, when the WD 22 served by the first cell 19 fulfills a handover condition, one of the following two actions may be performed:

[0168] ■ While the handover fulfillment is still active and before T expiry, if the difference between RSRP of first cell 19 (serving cell) and RSRP of the second cell 19 (neighbor cell) is lower than parameter Y, then no further action is performed.

[0169] ■ Otherwise, a handover procedure is triggered.

[0170] Step S206: Informing the network about avoided as well as of failed forth and back handovers.

[0171] When “Feature 1” or “Feature 2” is applied, then one of the following two scenarios may occur. In a first scenario (Scenario 1), a handover procedure is avoided by WD 22. As a result, the WD 22 does not send a RRC MeasurementReport to the first cell 19 (serving cell). However, the network node 16 (e.g., network) is not aware that a forth and back handover procedure was experienced by the WD 22 at location X. In some cases, it may be beneficial for the network and / or operator to be aware of the occurrences of such events. Step S206 may provide one or more procedures to inform the network and / or operator about such events.

[0172] • First procedure (Procedure 1): A parameter, e.g., forthd hack handover avoided. which may be coded into 1 bit is added to the existing RRC MeasurementReport. The parameter may be used as follows: o Each time a forth and back handover is avoided, either via Feature 1 or Feature 2, a RRC MeasurementReport including forth&back handover avoided = 1 is sent by the WD 22 to the first cell 19 (serving cell 19), e.g. at the end of the avoided forth and back handover procedure. In case Feature 2 is applied forth&back andover avoided = 1 is sent before T expiry in case the radio conditions, e.g., radio measurement event, between the first cell 19 and the second cell 19 have ceased . o forth&back andover avoided = 1 may be communicated to the network node 16 at other times or based on a schedule. In one example, an RRC MeasurementReport containing forth&back andover avoided = 1 may be sent every predefined period of time, e.g. a quantity of days have elapsed.

[0173] • Second procedure (Procedure 2): The WD 22 includes a mobile application (i.e., a function of WD management unit 34) which may be provided or configured by the operator. Each time the WD 22 avoids a forth and back handover, the WD 22 sends to the network node 16 and via the new mobile application, a notification about such event together with the location X of the event.

[0174] In a second scenario (Scenario 2), when applying Feature 1 or Feature 2 and while avoiding the forth and back handover, a call may be released or terminated. In some embodiments, network node 16 is not aware of the reason for such release, which is the consequence of applying feature 1 or feature 2. A parameter denoted forth&back Jandover Jailed may be used which may be coded into 1 bit. Steps associated with the parameter may be as follows.

[0175] • Each time Feature 1 or Feature 2 fails, the WD 22 may send to the cell 19 the parameter forth&back handover Jailed = 1 in a dedicated RRC message together with the location of the WD 22. The parameter may be sent, together with the WD location, in the next RRC MeasurementReport transmitted by the WD 22 or it may be added to existing rlf-report which is included in RRC message UEInformationResponse and that is sent when the WD experiences a call release.

[0176] • Otherwise, the value of forth&back Jandover Jailed = 0. Using the parameter forth&back handover Jailed is beneficial at least for the network automation tools and / or operators such as for troubleshooting the handover failures in the network and / or adjusting in real time the value of T and Y.

[0177] Step S208: Adjusting the value of parameters T and Y

[0178] As the WD behavior changes depending on subscriber behavior and WD location, adjusting the values of T and Y for the WDs 22 may be beneficial.

[0179] How to communicate the values of T and Y

[0180] The values of T and Y may be communicated to the WD 22 at least in one of the following two options:

[0181] • (Option 1): The values of T and Y may be hardcoded at the WD 22, e.g. the WD 22 vendor may have hardcoded one value for T and another one for Y.

[0182] • (Option 2): Based on the number of occurrences of second new parameter forth&back -handover Jailed. The values of T and Y may be set by the operator at the network side and then communicated to the WD 22 via one dedicated signaling message, e.g. RRCReconfiguration message, or via one of the cell broadcasted System Information.

[0183] The values of T and Y may be static or dynamic .

[0184] In some embodiments, the values of T and Y are static. A static value may refer to a single value used for all WDs 22 of the same WD vendor (in case of WD hardcoded procedure) or it could be a unique value to be used by all WDs 22 in the cell 19. For example, T may be equal to 20 seconds and Y may equal 3 dB for all WDs 22. In some embodiments, the values of T and Y are dynamic. A dynamic value may refer to each WD 22 (depending on its circumstances, when experiencing forth and back handover procedure) using a different value for T and / or Y. For example, T and Y may be defined as less than a predefined value, e.g. T < 1 minute and Y < 4 dB. One or more embodiments may provide avoiding as many as possible forth and back handovers and / or allowing the WD 22 to move the quickest possible to the best cell 19, e.g., the second cell 19 in the examples above.

[0185] One of the advantages of the dynamic value over the static value is illustrated with the following example. If a static value of 30 seconds is used, and if a forth and back handover is occurring for a particular subscriber after 30 seconds with the dynamic value, e.g. < 1 minute or < 40 seconds, the forth and back handover may be avoided. In some embodiments, the limit of a dynamic value, e.g. T < 1 minute may be communicated to the WD 22 either via signaling from the network using System Information Block (SIB) or RRCReconfiguration message. In some other embodiments, the limit is hardcoded in the WD 22.

[0186] In some embodiments, after the values of T and Y are communicated to the WD 22, the values may be adjusted by the network node 16, for example:

[0187] • Option 1 (via existing counters): At time tO, counters related to the handover procedure are monitored on every cell 19. For example, counters that show the number of successes and failures of handovers, counters that show a number of dropped calls, etc. In some embodiments, counters are related to the parameter forth&back handover Jailed. At time tl, at least one value of T and Y is communicated to the WD 22. The counters that were monitored at time tO may be monitored again. Then, if for example, some radio counters are changed, e.g. number of failures of handovers has increased then the value of T and Y may be adjusted as they would have been considered as the main cause of the increase of the number of failures of handovers.

[0188] • Option 2 (based on the value of the parameter forth&back -handover Jailed)'. Each time the cell receives forth&back -handover Jailed =1, then an action to adjust the value of T and Y is performed as described below.

[0189] In some embodiments, options 1 and 2 may be used simultaneously. Based on the results of option 1 and option 2 the values of T and / or Y may be adjusted as follows:

[0190] • In case radio degradation reflected by the analysis of the radio counters was encountered in one cell 19, the values of T and / or Y may be reduced.

[0191] • Otherwise, if no degradation was experienced, the values T and / or Y may be increased as this may increase the number of avoided forth and back handovers while not degrading the network.

[0192] In some embodiments, the same values of T and Y may be sent for WDs 22 in the cell 19 and / or the network. In some other embodiments, different values of T and Y are sent for each WD 22 depending on experience with the forth and back handover. Any of the steps and / or functions and / or features and / or tasks described above (e.g., with respect to method 1) as performed by WD 22 may be performed by other components of system 10 (e.g., network node 16, host computer 24, etc.)

[0193] Some embodiments provide a second method (i.e., method 2) including at least some steps implemented a network node 16. The second method may include one or more of the following.

[0194] • Feature 3 : The detection of a forth and back handover is performed at the WD 22 whereas decision to avoid the forth and back handover is performed by the network node 16.

[0195] • Feature 4: The detection of a forth and back handover as well as the decision to avoid the forth and back handover are both performed by the network node 16.

[0196] FIG. 11 shows another example method (e.g., second method) according to some embodiments of the present disclosure, associated with a feature (Feature 3), and may include one or more of steps S300-S306.

[0197] Step S300: An Al (and / or ML) entity is implemented at the WD side.

[0198] The Al and / or ML entity, i.e., UE drth&back HO detection entity is implemented at the WD side, and it is used to perform one part of feature 3 of the second method. The entity may be similar to the entity described above in Step S200 of the first method. The method may include one or both of the following two procedures:

[0199] • In a first procedure, if the WD 22 experiences, at location X, multiple occurrences of forth and back handover, the WD 22 may consider location X as a location where forth and back handover is likely to happen.

[0200] • In a second procedure, by using the WD stored dataset (including the RF metrics) for the handovers (e.g., already labelled if they finally were unnecessary or not), the UE Jo' rth&back HO detection entity may predict whether a handover is likely going to be a forth and back handover.

[0201] Step S302: A parameter is introduced.

[0202] A parameter, e.g., denoted forth&back HO occurence which may be coded into 1 bit may be included in an RRC MeasurementReport message. For example, if the WD 22 detects a forth and back handover at location X, WD 22 sends an RRC MeasurementReport that includes parameter forth&back HO occurence = 1. Otherwise, in other situations when the WD 22 sends a RRC MeasurementReport, parameter forth&back HO occurence = 0.

[0203] Step 304: The first cell 19 receives n RRC MeasurementReport from the WD 22

[0204] When the first cell 19 (e.g., serving cell 19) receives an RRC MeasurementReport from the WD 22, one or both of the following may be performed.

[0205] • If forth&back HO occurence = 0, the actual standard procedures is followed which consists of triggering a handover procedure from first cell 19 towards second cell 19.

[0206] ■ If forth&back HO occurence = 1, either Feature 1 or Feature 2 of step S202 may be performed at the first cell 19. That is, the first cell 19 may avoid the forth and back handover. In some embodiments, with Feature 1, the forth and back handover may be avoided as long as radio conditions of the first cell 19 are good at the WD 22. In some other embodiments, with Feature 2, the forth and back handover may be avoided for a period T as long as radio conditions of the first cell 19 are good at the WD 22. When Feature 2 is applied, the values of T and Y may be available at cell side.

[0207] Monitorins the radio conditions of a cell 19 (serving cell) at the WD 22

[0208] In some embodiments, the WD 22 passes by a stored location X at time tl and a forth and back handover is detected. WD 22 sends an RRC MeasurementReport that includes a handover event, e.g. A3, and the radio conditions at the first and second cells 19 at time tl. The network node 16, in particular the first cell 19, may be aware of the radio conditions of the first cell 19 and the second cell 19, which were available at the WD 22 at time tl. In some other embodiments, the network may not have any visibility on the radio conditions, at the WD 22, of the first cell 19 and neighboring cells 19 (Cell 2), unless another RRC MeasurementReport is sent by that WD 22 at any time later such as t2. In other words, the network node may determine the radio condition only at time of reception of each RRC MeasurementReport. The network node 16 may determine the radio conditions of the WD 22 at time tl and at time t2 but has no visibility on what happened with the radio conditions at any time between tl and t2. For example, when A3 conditions are fulfilled, not only one MeasurementReport is sent. As long as the A3 conditions are still occurring, more A3 MeasurementReports may be sent, according to the configuration (reportinterval and report Amount). However, sending multiple A3 RRC MeasurementReports does not cover each scenario. In one example, between tl (reception by the cell 19 of the first A3 RRC MeasurementReporf) and t2 (reception by the cell 19 of the second A3 RRC MeasurementReport). a sudden degradation of the RF conditions may be experienced by the WD 22 and which might cause the communication to be released. In such a scenario, the repetitive transmission by the WD 22 of A3 RRC MeasurementReport is not helpful. .

[0209] Step S306: Transmitting an including forth&back HO occurence = 0

[0210] After detecting a potential forth and back handover, an RRC MeasurementReport including forth&back HO occurence = 0 is sent from the WD 22 to the network node 16. However, in order to avoid a situation where a sudden degradation of the RF conditions is experienced, another step may be added to Feature 3. The other step includes any of the following actions.

[0211] • First action: As long as the radio conditions of the WD 22 at the first cell 19 are good (e.g., a measure indicative of strength or quality of a radio signal from a base station received by the WD is greater than a predefined threshold), Feature 1 or Feature 2 may be used in order to avoid the forth and back handover procedure. The measure indicative of strength may be RSRP and for quality it may be RSRQ.

[0212] • Second: At any time after tl in case of Feature 1 is used or at any time between tl and T in case Feature 2 is used, if the radio conditions of the first cell 19 are degraded at the WD 22, the WD 22 may transmit another RRC MeasurementReport including forth&back HO occurence = 0. Once it is received by the network node 16, in particular by the cell 19, the previous status of forth&back HO occurence = 1 may be overwritten by forth&back HO occurence = 0. An immediate handover may be triggered from the first cell 19 to the second cell 19 as radio conditions on the first cell 19 have deteriorated.

[0213] Feature 4: The detection of a forth and back handover and the decision to avoid being executed by the network node 16, FIG. 12 shows an example method implemented at least by network node 16. The method may include one or both of steps S400 and S402 associated with a feature (Feature 4).

[0214] Step S400: Detecting a potential occurrence of a forth and back handover.

[0215] An Al software entity, i.e., Cell jorth&back HO detection entity, is implemented at the network node 16. This Al and ML entity may have similar objectives as UE jorth&back HO detection entity that was implemented at the WD 22 in the first method of the present disclosure, i.e., predict when a forth and back handover is likely to happen. Further, the entity may be implemented based on one or on both of the following two procedures, third and fourth procedures to be applied at the cell side.

[0216] • Third procedure (for a cell 19 to detect a forth and back handover): Each time a WD 22 experiences, at time tO, a forth and back handover (a first handover from the first cell 19 to the second cell 19, then a second handover from the second cell 19 to the first cell 19 within a predefined period of time T), Cell brth&back HO detection entity (e.g., NN management unit 32 or any of its functions) may store the location X of that WD 22. In some embodiments, based on the standards and for security reasons, the WD identity may not communicated over the air interface and as a consequence the WD identity is not known at the network node 16. In some other embodiments, location X may be considered as the Timing Advance (TA) of that WD 22 during that event. In some other embodiments, rather than using TA for location X, location X is calculated via any other positioning procedures, e.g. Time-of-Arrival (TOA) technology, Angle of Arrival (AO A), etc. and may be combined with other info, for example: o The timestamp and the day of the occurrence of the forth and back handover; and / or o The radio condition of the serving cell 19, i.e., the first cell 19, and neighbor cell 19, i.e., the second cell 19, received in RRC MeasurementReport which is sent at time tO to trigger a handover from the first cell 19 towards the second.

[0217] Such above information when combined with the location X of the WD could make the identification of that UE more accurate. In some embodiments, if the WD 22 experiences, at the same location X, a forth and back handover multiple times, network node 16 and / or NN management unit 32 (i.e., Cell Jo' rth&back HO detection entity) may tag in a list the location X and the period of the day as a potential location where a forth and back handover is likely to happen. In a first example, multiple times could be estimated as exceeding an absolute threshold e.g. more than a predefined times during a predefined period such as a day or a week. In a second example, multiple times could be estimated as a probability, e.g. the number of forth and back handovers divided by the total number of handovers exceeding a predefined threshold.

[0218] • A fourth procedure (for a cell 19 to detect a forth and back handover): The network node 16 collects the RF metrics samples coming from all the WDs 22, e.g. collecting radio measurements received via RRC MeasurementReport, trains an Al model to predict whether a handover is likely going to be a forth and back handover.

[0219] Step S402: Avoid the handover execution when a potential forth and back handover is detected.

[0220] The handover execution may be avoided when a potential forth and back handover is detected where such detection is performed either via the third or the fourth procedure. When the first cell 19 receives at time, e.g. tl, an RRC MeasurementReport with a radio measurement event towards the second cell 19 and if the third procedure or fourth procedure is validated, rather than immediately triggering a handover procedure, the network node, in particular the first cell 19 may postpone the handover triggering for a duration, e.g. Tl.

[0221] • At the expiry of Tl, the network node 16 (e.g., the first cell 19) may send a handover command to the WD 22 in order to move to the second cell 19. For example: o First scenario (Scenario 1): At time tl + Tl, the handover conditions are not fulfilled at the WD 22 side, the WD 22 ignores the contents of the handover command. In such a scenario, the WD 22 notifies the network node 16 that a handover execution was avoided. Such notification may be provided using a parameter or by sending in an RRC MeasurementReport including the parameter (i.e., forth&back HO occur ence). which may be set to equal to 1. o Second scenario (Scenario 2): At time tl + Tl, the handover conditions at time tl + Tl are still fulfilled at the WD 22 side, the WD 22 may execute the contents of the handover command and hence it moves to the second cell 19.

[0222] In some embodiments, the first scenario may require a change in communication standards. For example, that a new parameter such as forth&back HO occurence may be added to the communication standards. In some other embodiments, standard modification is not made. For example, if the values of reportinterval and reportAmount are selected at the expiration of Tl, the cell 19 can receive A3 events. Then, the handover command may be sent, and the WD 22 may execute the handover. If the cell 19 stops receiving A3 events, the handover conditions may not be fulfilled anymore at the WD 22 side and then after Tl expires, the network node 16 may determine that sending the handover command is not needed.

[0223] In some other embodiments, more than one RRC MeasurementReport including an A3 event is sent by the WD 22 to the first cell 19 (serving cell 19) as long as the conditions for the A3 event are still fulfilled at the WD 22 side. In some embodiments, depending on the selected value of Tl, the operator and / or an automation tool (e.g., at network node 16) may set the periodicity and a maximum number of events by changing the configuration of the parameters reportinterval and reportAmount, respectively. In some other embodiments, the value of Tl may be a value not related to the values set for reportinterval and reportAmount.

[0224] A nonlimitins comparison between Feature 3 and Feature 4

[0225] • One of the benefits of Feature 3 over Feature 4 is: o Trying different values of the configuration parameters reportinterval and reportAmount when configuring the event A3 may help extend the Tl value in Feature 4. However, with Feature 3 as the WD 22 may be aware, such as at all the times, about the radio conditions of the first cell 19 and the second cell 19, then given a sudden RF degradation, Feature 3 may be used by immediately sending a RRC MeasurementReport with forth&back HO occurence = 0, which in some cases may make Feature 3 react faster than Feature 4 and execute a handover in time.

[0226] • On of the benefits of Feature 4 over Feature 3 may be that the data set, which is used by the AI / ML entity to determine back and forth handovers, may be built using the samples of all the WDs 22 and not only one WD 22. In some cases, the prediction accuracy of Feature 4 may be higher than the prediction accuracy of Feature 3.

[0227] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD- ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0228] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0229] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0230] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0231] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0232] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the “C” programming language. The program code may execute entirely on the user’s computer, partly on the user’s computer, as a stand-alone software package, partly on the user’ s computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user’s computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0233] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0234] Abbreviations that may be used in the preceding description include:

[0235] AO A Angle of Arrival

[0236] DU Digital Unit GPS Global Positioning System

[0237] HO Handover

[0238] ML Machine Learning

[0239] PCI Physical Cell Identity

[0240] RAT Radio Access Technology

[0241] RRC Radio Resource Control

[0242] RSRP Reference Signal Received Power

[0243] RSRQ Reference Signal Received Quality

[0244] RU Radio Unit

[0245] SIB System Information Block

[0246] TA Timing Advance

[0247] To A Time-of- Arrival

[0248] UE User Equipment

[0249] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

Claims:

1. A method in a network node (16) configured to communicate at least with a wireless device, WD (22), of a plurality of WDs (22) using at least one of a first cell (19) and a second cell (19), the method comprising: determining (SI 34), using one or more artificial intelligence, Al, models, whether a forth and back handover, FBHO, event associated with the WD (22) can occur at a location, the FBHO event including at least a first handover, HO, of the WD (22) from the first cell (19) to the second cell (19) and a second HO of the WD (22) from the second cell (19) to the first cell (19); and avoiding (SI 36) triggering at least one HO based on the determination that the FBHO event can occur.

2. The method of Claim 1, wherein the method further includes: storing location information associated with the location of the WD (22) at least once the WD (22) experiences, at a first time, tO, the FBHO event within a first predetermined period of time, T.

3. The method of any one of Claims 1 and 2, wherein the method further includes: obtaining radio frequency, RF, metrics samples from the plurality of WDs (22); and training at least one Al model of the one or more Al models using the RF metrics samples to predict whether an HO can be associated with the FBHO event .

4. The method of any one of Claims 2 and 3, wherein the method further includes: receiving, via the first cell (19), at second time, tl, a measurement report including a radio measurement event towards the second cell (19); and avoiding the at least one HO by postponing an HO triggering for a second predetermined period of time, Tl.

5. The method of Claim 4, wherein the measurement report is a radio resource control measurement report.

6. The method of any one of Claims 4 and 5, wherein the method further includes: at the expiry of T1 : transmitting an HO command to the WD (22) requesting the WD (22) to communicate using the second cell (19); or avoiding transmission of the HO command to the WD (22) if the WD (22) stops reporting additional measurements reports to the network node (16).

7. The method of Claim 6, wherein the method further includes: triggering the WD (22) to ignore contents of the HO command at a third time equal to the sum of tl and T1 when HO conditions are not fulfilled; and receiving an indication indicating that the HO command was ignored by the WD (22).

8. The method of Claim 7, wherein the indication includes an FBHO occurrence value.

9. The method of any one of Claims 7 and 8, wherein the method further includes: triggering the WD (22) to perform an action based on the contents of the HO command at the third time when the HO conditions are fulfilled.

10. The method of Claim 9, wherein the action corresponds to the triggering of the at least one HO and includes causing the WD (22) to communicate using the second cell (19).

11. The method of any one of Claims 1-10, wherein the method further includes: triggering the at least one HO based on the determination that the FBHO event will not occur.

12. A network node (16) configured to communicate at least with a wireless device, WD (22), of a plurality of WDs (22) using at least one of a first cell (19) and a second cell (19), the network node (16) being configured to: determine, using one or more artificial intelligence, Al, models, whether a forth and back handover, FBHO, event associated with the WD (22) can occur at a location, the FBHO event including at least a first handover, HO, of the WD (22) from the first cell (19) to the second cell (19) and a second HO of the WD (22) from the second cell (19) to the first cell (19); and avoid triggering at least one HO based on the determination of whether to avoid at least one HO of the WD (22).

13. The network node (16) of Claim 12, wherein the network node (16) is configured to: store location information associated with the location of the WD (22) at least once the WD (22) experiences, at a first time, tO, the FBHO event within a first predetermined period of time, T.

14. The network node (16) of any one of Claims 12 and 13, wherein the network node (16) is configured to: obtain radio frequency, RF, metrics samples from the plurality of WDs (22); and train at least one Al model of the one or more Al models using the RF metrics samples to predict whether an HO can be associated with the FBHO.

15. The network node (16) of any one of Claims 13 and 14, wherein the network node (16) is configured to: receive, via the first cell (19), at second time, tl, a measurement report including a radio measurement event towards the second cell (19); and avoid the at least one HO by postponing an HO triggering for a second predetermined period of time, Tl.

16. The network node (16) of Claim 15, wherein the measurement report is a radio resource control measurement report.

17. The network node (16) of any one of Claims 15 and 16, wherein the network node (16) is configured to: at the expiry of Tl : transmit an HO command to the WD (22) requesting the WD (22) to communicate using the second cell (19); or avoid transmission of the HO command to the WD (22) if the WD (22) stops reporting additional measurements reports to the network node (16).

18. The network node (16) of Claim 17, wherein the network node (16) is configured to: trigger the WD (22) to ignore contents of the HO command at a third time equal to the sum of tl and Tl when HO conditions are not fulfilled; and receive an indication indicating that the HO command was ignored by the WD (22).

19. The network node (16) of Claim 18, wherein the indication includes an FBHO occurrence value.

20. The network node (16) of any one of Claims 18 and 19, wherein the network node (16) is configured to: trigger the WD (22) to perform an action based on the contents of the HO command at the third time when the HO conditions are fulfilled.

21. The network node (16) of Claim 20, wherein the action corresponds to the triggering of the at least one HO and includes causing the WD (22) to communicate using the second cell (19).

22. The network node (16) of any one of Claims 12-21, wherein the network node (16) is configured to: trigger the at least one HO based on the determination that the FBHO event will not occur.

23. A method in a wireless device, WD (22), configured to communicate with the network node (16), the method comprising: determining (SI 38), using one or more artificial intelligence, Al, models, whether a forth and back handover, FBHO, event associated with the WD (22) can occur at a location, the FBHO event including at least a first handover, HO, of the WD (22) from the first cell (19) to the second cell (19) and a second HO of the WD (22) from the second cell (19) to the first cell (19); and avoiding (S140) triggering at least one HO based on the determination that the FBHO event can occur.

24. The method of Claim 23, wherein the method further includes: storing location information associated with the location of the WD (22) at least once the WD (22) experiences, at a first time, tO, the FBHO event within a first predetermined period of time, T.

25. The method of any one of Claims 23 and 24, wherein the method further includes:Obtaining radio frequency, RF, metrics samples from the first cell (19) and the second cell (19); and training at least one Al model of the one or more Al models using the RF metrics samples to predict whether an HO can be associated with the FBHO event.

26. The method of any one of Claims 24 and 25, wherein the method further includes one of: as long as the radio conditions are good at first cell (19), avoiding the at least one HO by not sending a measurement report including a radio measurement event towards the second cell (19) and waiting for the WD (22) to return to a location where the first cell (19) becomes the best cell (19); and postponing an HO triggering for a second predetermined period of time, T, or when the RSRP margin between the first cell (19) and the second cell (19) exceeds a predefined threshold Y.

27. The method of claim 26, wherein the method further includes:sending to the first cell (19) an indication indicating that the HO command was ignored by the WD (22) and where the indication includes an FBHO occurrence value.

28. The method of any one of Claims 23-27, wherein the method further includes: triggering the at least one HO based on the determination that the FBHO event will not occur.

29. A wireless device, WD (22), configured to communicate with the network node (16), the WD (22) being configured to: determine, using one or more artificial intelligence, Al, models, whether a forth and back handover, FBHO, event associated with the WD (22) can occur at a location, the FBHO event including at least a first handover, HO, of the WD (22) from the first cell (19) to the second cell (19) and a second HO of the WD (22) from the second cell (19) to the first cell (19); and avoid triggering at least one HO based on the determination that the FBHO event can occur.

30. The WD (22) of Claim 29, wherein the WD (22) is further configured to: store location information associated with the location of the WD (22) at least once the WD (22) experiences, at a first time, tO, the FBHO event within a first predetermined period of time, T.

31. The WD (22) of any one of Claims 29 and 30, wherein the WD (22) is further configured to: obtain radio frequency, RF, metrics samples from the first cell (19) and the second cell (19); and train at least one Al model of the one or more Al models using the RF metrics samples to predict whether an HO can be associated with the FBHO event.

32. The WD (22) of any one of Claims 30 and 31, wherein the WD (22) is further configured to one of:as long as the radio conditions are good at first cell (19), avoid the at least one HO by not sending a measurement report including a radio measurement event towards the second cell (19) and wait for the WD (22) to return to a location where the first cell (19) becomes the best cell (19); and postpone an HO triggering for a second predetermined period of time, T, or when the RSRP margin between the first cell (19) and the second cell (19) exceeds a predefined threshold Y.

33. The WD (22) of claim 32, wherein the WD (22) is further configured to: send to the first cell (19) an indication indicating that the HO command was ignored by the WD (22) and where the indication includes an FBHO occurrence value.

34. The WD (22) of any one of Claims 29-33, wherein the WD (22) is further configured to: trigger the at least one HO based on the determination that the FBHO event will not occur.

Images