WO2022124972A1

WO2022124972A1 - Handling of mobility event feedback information

Info

Publication number: WO2022124972A1
Application number: PCT/SE2021/051224
Authority: WO
Inventors: Luca LUNARDI; Angelo Centonza; Pradeepa Ramachandra; Henrik RYDÉN; Pablo SOLDATI
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2020-12-11
Filing date: 2021-12-08
Publication date: 2022-06-16

Abstract

A first example of a method according to an embodiment of the invention comprises a method of operating a first radio access network, RAN, node of a radio communication network. The first RAN node transmits (1105) a request to a second RAN node, wherein the request includes an indication to provide mobility event feedback. The first RAN node receives (1115) a response from the second RAN node after transmitting the request, wherein the response includes mobility event feedback information relating to User Equipment, UE, mobility between at least one cell of the first RAN node and at least one cell of the second RAN node.

Description

HANDLING OF MOBILITY EVENT FEEDBACK INFORMATION

TECHNICAL FIELD

[0001] The present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting wireless communications.

BACKGROUND

[0002] The 5th generation (5G) radio access network (RAN) Architecture is discussed below.

[0003] The current 5G RAN (NG-RAN (Next Generation-RAN)) architecture is depicted and described in 3GPP TS 38.401 vl5.4.0 (http://www.3gpp.Org/ftp//Specs/archive/38_series/38.401/38401-f40.zip), also referred to as Reference [1] herein, as shown in Figure 1.

[0004] The NG architecture can be further described as follows. The NG-RAN includes a set of gNBs connected to the 5GC through the NG. An gNB can support frequency division duplex (FDD) mode, time division duplex (TDD) mode or dual mode operation. gNBs can be interconnected through the Xn interface. A gNB may include a gNB-CU and gNB-DUs. A gNB- CU and a gNB-DU are connected via an Fl logical interface. One gNB-DU is connected to only one gNB-CU. For resiliency, a gNB-DU may be connected to multiple gNB-CUs by appropriate implementation. NG, Xn and Fl are logical interfaces. The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, i.e., the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, Fl) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport and signaling transport.

[0005] A gNB may also be connected to an LTE eNB via the X2 interface. Another architectural option is that where an LTE eNB connected to the Evolved Packet Core network is connected over the X2 interface with a so called nr-gNB. The latter is a gNB not connected directly to a core network (CN) and connected via X2 to an eNB for the sole purpose of performing dual connectivity. [0006] The architecture in Figure 1 can be expanded by spitting the gNB-CU into two entities. One gNB-CU-UP, which serves the user plane and hosts the packet data convergence protocol (PDCP) protocol and one gNB-CU-CP, which serves the control plane and hosts the PDCP and radio resource control (RRC) protocols. For completeness it should be said that a gNB-DU hosts the RLC/MAC/PHY (radio link control/medium access control/physical) protocols.

[0007] Basics of Mobility Load Balancing (MLB) in LTE are discussed below.

[0008] In mobile networks, the load of a radio access node is constantly measured so that when it gets above a pre-configure threshold, procedures can be triggered so that part of this load is transferred to either a neighbor cell of the same radio access technology (RAT) or another RAT or frequency.

[0009] The set of procedures to support this transfer is called mobility load balancing (MLB). Currently, 3GPP specifies the following components for the MLB solution: Load reporting; Load balancing action based on handovers (HO)s; and Adapting HO/ cell reselection (CR) configuration so that the load remains balanced.

[0010] For LTE, the load reporting function is executed by exchanging cell specific load information between neighbor enhanced NodeBs (eNBs) over the X2 (intra-LTE scenario) or SI (inter-RAT scenario) interfaces. In the case of intra-LTE load balance, the source eNB may trigger a RESOURCE STATUS REQUEST message to potential target eNBs at any point in time, for example, when the load is above a pre-defined value (i.e., Lte load threshold) as shown in the graph of Figure 2, which illustrates an overloaded scenario triggering MLB procedures. Upon successful configuration of resource status reports from target to source, the target eNB can respond (periodically or not) with a RESOURCE STATUS UPDATE containing information about its load per cell. The message exchange is highlighted in the diagram of Figure 3, which illustrates X2 load exchange procedures for MLB.

[0011] A mobility load balancing algorithm running at a radio access node (for example, an eNB) has to decide which user equipments (UEs) will be handed over (a process called UE selection) and to which neighbor cells (a process called cell selection). These decisions are typically taken based mainly on the load reports and potentially available radio measurements of source cell and neighbor cells reported by the UE candidates. More details about UE/cell selection processes are given later. [0012] In other words, the UE may send measurement reports (RSRP, RSRQ, SINR, etc.) for a given neighbour cell (e.g., cell-2 in eNB-2) and, upon the reception of these and having load information of such neighbor cell the source may decide to handover the UE to the neighbor cell due to overload or not. In this case, an handover preparation is triggered towards a target node, e.g., eNB-2.

[0013] As part of Resource Status Reporting procedure, a first eNB sending load information to a second eNB can include an indication (such as Cell Reporting Indicator) to indicate to the second eNB node that the ongoing transfer of load information has to be stopped. This may be used, e.g., as an indication that the load in the first eNB has become excessive. [0014] Another procedure that may be executed is a Mobility Setting Change. The Mobility Setting Change procedure can be run before or after a MLB handover is performed. This procedure is aimed at negotiating between source cell and potential target cell a change on the *Handover Trigger event, which is used to trigger the mobility event from one cell to another. As an example, the case where the Mobility Setting Change is performed after the handover (HO) can be considered. Once the source eNB has selected the target eNB and which UE’s will be offloaded, it performs a Mobility Setting Change Procedure (also specified by 3GPP TS 36.423 VI 6.3.0, also referred to as Reference [2] herein). During this procedure, new mobility settings are negotiated between the source and target eNBs so that UEs handed over due to load balance will not be immediately handed over back. The procedure can either be followed or preceded by ordinary handovers, depending on the vendor implementation. A summary is shown in the message diagram of Figure 4, which illustrates MLB execution, including Mobility Parameter Change procedures.

[0015] Basics of Mobility Load Balancing (MLB) in NG RAN are discussed below.

[0016] MLB in NR follows signaling principles that are in line with LTE. Similar signaling mechanisms are used in NG-RAN with the difference that the MLB metrics are reported over the split RAN interfaces. To this end, signaling support for Resource Status Reporting has been introduced over Xn, Fl and El inter-node interfaces as well as enhanced over X2 for EN-DC scenarios. In addition, the NG-RAN MLB functionality has been enhanced with new types of load metrics and with finer load granularity compared to LTE (where load information is expressed on a per-cell basis only). In particular, it the NG-RAN MLB enhancements include:

Load information on a per SSB coverage area granularity, such as o Radio Resource Status reporting per SSB area o Composite Available Capacity reporting per SSB Area Load information on a per network slice granularity, such as o Slice Available Capacity reporting per slice Hardware load indicator over El TNL capacity indication Number of active UEs Number of RRC connections

[0017] As an example, one can consider the Xn interface specification in 3GPP TS 38.423 vl 6.2.0, also referred to as Reference [3] herein, where the Resource Status Reporting Indication procedure is specified in sections 8.4.10, 8.4.11 and 9.1.3.

[0018] Capacity cells are discussed below.

[0019] One way to improve the capacity of networks is to deploy capacity cells which are typically placed in areas with high mobile traffic. By activating the capacity cell during high traffic around the capacity cell coverage, the cell that provides basic coverage can be offloaded which ideally would lead to gains, in terms of capacity and power. Energy efficiency is an important aspect in radio networks, one method to provide energy saving is to put capacity cells into sleep mode. The activation of a capacity cell may be triggered by a RAN node serving a “coverage cell”, namely a cell deployed to provide the coverage layer for a given RAT. Deactivation of a capacity cell may be independently decided by the node serving the capacity cell. This process is typically a tradeoff between energy efficiency and capacity.

[0020] Existing UE Mobility History Information is discussed below.

[0021] In current specifications it is possible to signal at every UE handover a “mobility history information”. This information includes a list of up to 16 cells which the UE visited while in RRC CONNECTED mode. Namely, the list also represents the handovers the UE was subject to, together with the source and target cells of such handovers.

[0022] A description of this information as described in 3GPP TS 38.413 V16.3.0, also referred to as Reference [4] herein, is provided below.

[0023] Section 9.3.1.95 of Reference [4] discusses the UE History Information IE. This information element (IE) contains information about cells that a UE has been served by in active state prior to the target cell. Elements of this IE are illustrated in Table 1 below. Table 1

[0024] Section 9.3.1.96 of Reference [4] discusses the Last Visited Cell Information IE. This IE may contain cell specific information. Elements of this IE are illustrated in Table 2 below.

Table 2

[0025] Section 9.3.1.97 of Reference [4] discusses the Last Visited NG-RAN Cell Information IE. This IE contains information about a cell. In case of a NR cell, this IE contains information about a set of NR cells with the same NR ARFCN for reference point A, and the Global Cell ID IE identifies one of the NR cells in the set. The information is to be used for RRM purposes. Elements of this IE are illustrated in Table 3 below.

Table 3

[0026] As it can be seen from excerpt from Reference [4] discussed above, the UE History Information includes a list of up to 16 cells of various RAT type. For each cell change an HO cause is provided, as well as the time the UE stayed in the cell while in RRC CONNECTED. SUMMARY

[0027] According to some embodiments of inventive concepts, a method of operating a first radio access network (RAN) node of a radio communication network is provided. A request is transmitted to a second RAN node, wherein the request includes an indication to provide mobility event feedback. A response is received from the second RAN node after transmitting the request, wherein the response includes mobility event feedback information relating to User Equipment UE mobility between at least one cell of the first RAN node and at least one cell of the second RAN node.

[0028] First RAN nodes, computer program, and computer program products are also provided.

[0029] According to some embodiments of inventive concepts, a method of operating a second radio access network (RAN) node of a radio communication network is provided. A request is received from a first RAN node, wherein the request includes an indication to provide mobility event feedback. A response is transmitted to the first RAN node responsive to receiving the request, wherein the response includes mobility event feedback information relating to User Equipment, UE, mobility between at least one cell of the first RAN node and at least one cell of the second RAN node.

[0030] Second RAN nodes, computer programs, and computer program products are also provided.

[0031] Advantages that may be achieved using the various embodiments of inventive concepts include enabling more informed decisions to be taken by a RAN node for mobility load balancing actions which can translate into an improved user experience in the area of mobility and integrity. The feedbacks collected by a RAN node can be used to understand how much and how efficiently the neighbor relations are used under certain (known) load conditions. Consequent manual or automatic actions are possible to optimize the mobility performance indicators, the use of network resources and the end-user experience. Further, various embodiments of inventive concepts enable efficient estimation of future traffic in a RAN node. This allows the RAN node to perform preventive actions such as activating or deactivating energy saving features such as antenna sleep, leading to energy savings. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

[0033] Figure 1 is a block diagram illustrating a 5^th Generation Radio Access Network architecture;

[0034] Figure 2 is graph illustrating an overloaded scenario triggering Mobility Load Balancing MLB procedures;

[0035] Figure 3 is a diagram illustrating X2 interface load exchange procedures for MLB;

[0036] Figure 4 is a message diagram illustrating MLB execution including Mobility

Parameter Change procedures;

[0037] Figures 5A and 5B are a flow chart illustrating RAN node operations according to some embodiments of inventive concepts;

[0038] Figure 6 is a message diagram illustrating signaling between RAN nodes according to some embodiments of inventive concepts;

[0039] Figure 7 is a diagram illustrating MLB feedback based on handover ratios according to some embodiments of inventive concepts;

[0040] Figure 8 is a block diagram illustrating a wireless device UE according to some embodiments of inventive concepts;

[0041] Figure 9 is a block diagram illustrating a radio access network RAN node (e.g., a base station eNB/gNB) according to some embodiments of inventive concepts;

[0042] Figure 10 is a block diagram illustrating a core network CN node (e.g., an AMF node, an SMF node, etc.) according to some embodiments of inventive concepts;

[0043] Figures 11 and 12 are flow charts illustrating operations of RAN nodes according to some embodiments of inventive concepts;

[0044] Figure 13 is a block diagram of a wireless network in accordance with some embodiments;

[0045] Figure 14 is a block diagram of a user equipment in accordance with some embodiments

[0046] Figure 15 is a block diagram of a virtualization environment in accordance with some embodiments; [0047] Figure 16 is a block diagram of a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments;

[0048] Figure 17 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments;

[0049] Figure 18 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments;

[0050] Figure 19 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments;

[0051] Figure 20 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments; and

[0052] Figure 21 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

DETAILED DESCRIPTION

[0053] Inventive concepts will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.

[0054] The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded upon without departing from the scope of the described subject matter.

[0055] Figure 8 is a block diagram illustrating elements of a communication device UE 300 (also referred to as a mobile terminal, a mobile communication terminal, a wireless device, a wireless communication device, a wireless terminal, mobile device, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.) configured to provide wireless communication according to embodiments of inventive concepts. (Communication device 300 may be provided, for example, as discussed below with respect to wireless device 1310 of Figure 13, UE 1400of Figure 14, UEs 1691, 1692 of Figure 16, and/or UE 1730 of Figure 17.) As shown, communication device UE may include an antenna 307 (e.g., corresponding to antenna 1311 of Figure 13), and transceiver circuitry 301 (also referred to as a transceiver, e.g., corresponding to interface 1314 of Figure 13) including a transmitter and a receiver configured to provide uplink (UL) and downlink (DL) radio communications with a base station(s) (e.g., corresponding to network node 1360 of Figure 13, also referred to as a RAN node) of a radio access network. Communication device UE may also include processing circuitry 303 (also referred to as a processor, e.g., corresponding to processing circuitry 1320 of Figure 13) coupled to the transceiver circuitry, and memory circuitry 305 (also referred to as memory, e.g., corresponding to device readable medium 1330 of Figure 13) coupled to the processing circuitry. The memory circuitry 305 may include computer readable program code that when executed by the processing circuitry 303 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 303 may be defined to include memory so that separate memory circuitry is not required. Communication device UE may also include an interface (such as a user interface) coupled with processing circuitry 303, and/or communication device UE may be incorporated in a vehicle.

[0056] As discussed herein, operations of communication device UE may be performed by processing circuitry 303 and/or transceiver circuitry 301. For example, processing circuitry 303 may control transceiver circuitry 301 to transmit communications through transceiver circuitry 301 over a radio interface to a radio access network node (also referred to as a base station) and/or to receive communications through transceiver circuitry 301 from a RAN node over a radio interface. Moreover, modules may be stored in memory circuitry 305, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 303, processing circuitry 303 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to wireless communication devices). According to some embodiments, a communication device UE 300 and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/ machines .

[0057] Figure 9 is a block diagram illustrating elements of a radio access network RAN node 400 (also referred to as a network node, base station, eNodeB/eNB, gNodeB/gNB, etc.) of a Radio Access Network (RAN) configured to provide cellular communication according to embodiments of inventive concepts. (RAN node 400 may be provided, for example, as discussed below with respect to network node 1360 of Figure 13, base stations 1612A, 1612B, 1612C of Figure 16, and/or base station 1720 of Figure 17.) As shown, the RAN node may include transceiver circuitry 401 (also referred to as a transceiver, e.g., corresponding to portions of interface 1390 of Figure 13) including a transmitter and a receiver configured to provide uplink and downlink radio communications with mobile terminals. The RAN node may include network interface circuitry 407 (also referred to as a network interface, e.g., corresponding to portions of interface 1390 of Figure 13) configured to provide communications with other nodes (e.g., with other base stations) of the RAN and/or core network (CN). The network node may also include processing circuitry 403 (also referred to as a processor, e.g., corresponding to processing circuitry 1370) coupled to the transceiver circuitry, and memory circuitry 405 (also referred to as memory, e.g., corresponding to device readable medium 1380 of Figure 13) coupled to the processing circuitry. The memory circuitry 405 may include computer readable program code that when executed by the processing circuitry 403 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 403 may be defined to include memory so that a separate memory circuitry is not required.

[0058] As discussed herein, operations of the RAN node may be performed by processing circuitry 403, network interface 407, and/or transceiver 401. For example, processing circuitry 403 may control transceiver 401 to transmit downlink communications through transceiver 401 over a radio interface to one or more mobile terminals UEs and/or to receive uplink communications through transceiver 401 from one or more mobile terminals UEs over a radio interface. Similarly, processing circuitry 403 may control network interface 407 to transmit communications through network interface 407 to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes. Moreover, modules may be stored in memory 405, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 403, processing circuitry 403 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to RAN nodes). According to some embodiments, RAN node 400 and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/machines.

[0059] According to some other embodiments, a network node may be implemented as a core network (CN) node without a transceiver. In such embodiments, transmission to a wireless communication device UE may be initiated by the network node so that transmission to the wireless communication device UE is provided through a network node including a transceiver (e.g., through a base station or RAN node). According to embodiments where the network node is a RAN node including a transceiver, initiating transmission may include transmitting through the transceiver.

[0060] Figure 10 is a block diagram illustrating elements of a core network (CN) node (e.g., an SMF node, an AMF node, etc.) of a communication network configured to provide cellular communication according to embodiments of inventive concepts. As shown, the CN node may include network interface circuitry 507 (also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the radio access network RAN. The CN node may also include a processing circuitry 503 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 505 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 505 may include computer readable program code that when executed by the processing circuitry 503 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 503 may be defined to include memory so that a separate memory circuitry is not required.

[0061] As discussed herein, operations of the CN node may be performed by processing circuitry 503 and/or network interface circuitry 507. For example, processing circuitry 503 may control network interface circuitry 507 to transmit communications through network interface circuitry 507 to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 505, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 503, processing circuitry 503 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to core network nodes). According to some embodiments, CN node 500 and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/ machines .

[0062] The UE history information mentioned above may not allow the RAN to build statistics regarding mobility, which can be taken as reliable data for understanding the mobility trends and likelihood towards a given target cell. The reasons for this are that the UE history information may be limited to the last 16 cells the UE visited, it is a UE-associated information, i.e. only transferred when an HO occurs, and it is available while the UE context is present at the RAN.

[0063] Namely, it may not be possible to derive meaningful statistics from this information and it may not be possible to request from a neighbor RAN node periodic reporting of this statistic (given its availability subject to occurrence of a UE HO).

[0064] With this assessed, there may currently be no information exchanged between nodes that allow a RAN node to determine what is the likelihood of mobility towards a served cell to occur. Such likelihood, or prediction, can be built if enough historical data from past mobility events within a given time frame are available at the RAN node.

[0065] Without this information a RAN node may be less likely to optimally deduce, for example, when it is the best time trigger energy saving actions such as deactivation of a cell, or how to modify mobility settings to increase or decrease the frequency of handovers between certain cells.

[0066] According to some embodiments of inventive concepts, a first RAN node may be able to request a second RAN node (e.g., as part of Resource Status Request XnAP message) to provide the first RAN node with feedback concerning mobility events (e.g., as part of Resource Status Update XnAP message). The feedback received at the first RAN node can be used by the first RAN node to predict the characteristics and performances of future mobility events between the cells of the first RAN node and the cells of the second RAN node and adjust radio parameter settings accordingly.

[0067] The radio parameter settings can relate to: Mobility settings; and/or Energy saving settings, such as activating/deactivating capacity cells or activating/deactivating MIMO sleep (e.g., to turn off/on one or more antennas to save battery).

[0068] The feedback can relate to: mobility events occurring between one specific cell controlled by the first RAN node and one specific cell controlled by the second RAN node; mobility events between cell(s) controlled by the first RAN node and cell(s) controlled by the second RAN node where either the cell(s) controlled by the first RAN node or the cell(s) controlled by the second RAN node belong to a group of cells characterized by a specific deployment or a specific type(s) of support, such as: cells operating at a given carrier frequency (or frequencies), cells supporting given slice(s), standalone non-public network (SNPN) cells, public network integrated non-public network (PNI-NPN) cells, cells with integrated access and backhaul (I AB) -support, cells pertaining to a certain public land mobile network (PLMN) (or Equivalent PLMN), cells included in certain Tracking Area or Tracking Area List; and/or mobility events occurring between one specific cell controlled by the first RAN node towards each of the known neighbor cells of the first RAN node.

[0069] In general, two RAN nodes are neighbor RAN nodes if there is a signaling path (e.g., a signaling path over an XnAP interface, and X2AP interface, an NGAP interface, and/or an S1AP interface) between the two RAN nodes. Moreover, two neighbor RAN nodes may be part of a same radio communication network, or two neighbor RAN nodes may be part of different radio communication networks (e.g., one node may be part of a E-UTRAN communication network, and the other node may be part of an NG-RAN communication network). In addition, a neighbor relation may be defined as a relation between two cells that may be controlled by the same RAN node or that may be controlled by different RAN nodes.

[0070] The feedback may comprise additional indications indicating events occurring shortly after a mobility event, such as subsequent handovers attempted within a given time interval after handover completion, use performance after handover, an indication if an ongoing session is still ongoing after a certain time after handover, an indication of the quality of service (QoS) or the quality of experience (QoE) in the target cell.

[0071] The time period associated with the reported mobility performance can be fixed or configured (e.g., the time interval between consecutive resource updates or a multiple of such interval).

[0072] The mobility performance may comprise events that occurred in the past and/or events predicted in the future.

[0073] The mobility events that are exchanged could be further sub-categorized under mobility events associated with load a balancing purpose, mobility events associated with coverage, etc. For example, consider cell-A to have cell-B and Cell-C as its neighbor cells. Cell- A has 50 mobility events from cell-A towards cell-B and 30 mobility events from cell-A towards cell-C. Out of the 50 mobility events from cell-A to cell-B, 10 of them are for the coverage purpose and the remaining 40 are for load balancing purpose. Out of the 30 mobility events from cell-A to cell-C, 15 of them are for the coverage purpose and the remaining 15 are for load balancing purpose. In this example, cell-A would inform cell-B and cell-C and any other neighbor cell or the operations and management (0AM) that it has 50/(50+30) probability of overall mobility towards cell-B and 30/(50+30) probability of overall mobility towards cell-C. Further, cell-A would inform cell-B and cell-C and any other neighbor cell or the 0AM that it has 10/50 probability of coverage related mobility towards cell-B and 40/50 probability of load balancing mobility towards cell-B. Further, cell-A would inform cell-B and cell-C and any other neighbor cell or the 0AM that it has 15/30 probability of coverage related mobility towards cell- C and 15/30 probability of load balancing mobility towards cell-C.

[0074] In some other embodiments, the mobility events are categorized separately for PCell changes and PSCell changes.

[0075] According to some embodiments of inventive concepts, a RAN node may be able to make more informed decisions for mobility load balancing actions which can translate into an improved user experience in the area of mobility and integrity. The feedback collected by a RAN node can be used to understand how much and how efficiently the neighbor relations are used under certain (known) load conditions. Consequent manual or automatic actions may be possible to improve/optimize the mobility performance indicators, the use of network resources, and/or the end-user experience. [0076] According to some embodiments of inventive concepts, a signaling method may be provided to enable efficient estimation of future traffic in a RAN node. This may allow the node to perform preventive actions such as activating or deactivating energy saving features (such as antenna sleep), leading to energy savings.

[0077] According to some embodiments of inventive concepts, the following is considered: a RAN node, which can be any of a gNB, eNB, an en-gNB, an ng-eNB, a gNB-CU, a gNB-CU- CP, a eNB-CU, and/or an eNB-CU-CP.

[0078] Methods according to some embodiments of inventive concepts are illustrated in the flow chart of Figures 5 A and 5B. Figure 6 and Figure 7 respectively illustrate an example of signaling and an example scenario for the proposed solution.

[0079] Figure 7 illustrates an example of feedback for MLB based on Handover Ratio. In the example of Figure 7, the first RAN node provides Cell B, Cell C, and Cell D, and the second RAN node provides Cell A. As shown, handovers HOs may occur between Cells A and B, between Cells A and C, and between Cells A and D.

[0080] For a time period in the past, “H0_A_M= M1+M2+M3” handover attempts are measured between Cell A and Cell B (Ml), between Cell A and Cell C (M2), and between Cell A and Cell D (M3).

[0081] For a time period in the future, “HO_A_P = P1+P2+P3” handover attempts are predicted between Cell A and Cell B (Pl), between Cell A and Cell C (P2), and between Cell A and Cell D (P3).

[0082] For a Handover Ratio for handovers between Cells A and D the following calculations may be performed to determine Measured and Predicted Handover Ratios:

Measured Handover Ratio = 100*M3/(HO_A_M)

Predicted Handover Ratio = 100*P3/(HO_A_P)

[0083] For a Handover Ratio for handovers between Cells A and C the following calculations may be performed to determine Measured and Predicted Handover Ratios:

Measured Handover Ratio = 100*M2/(HO_A_M)

Predicted Handover Ratio = 100*P2/(HO_A_P)

[0084] For a Handover Ratio for handovers between Cells A and B the following calculations may be performed to determine Measured and Predicted Handover Ratios: Measured Handover Ratio = 100*M1/(HO_A_M)

Predicted Handover Ratio = 100*P1/(HO_A_P)

[0085] Embodiments at a first RAN node (e.g., the first RAN node of Figures 5A-5B, 6, and/or 7) are discussed below, where the first RAN node can:

• send to the second RAN node (e.g., the second RAN node of Figures 5A-5B, 6, and/or 7) a request to provide feedback to the first RAN node, the feedback being related to mobility between cells, wherein: o the request for feedback can relate to events that occurred in the past or prediction of future events/values o the time period to which the feedback refers to can be fixed or configured (e.g., a time interval between consecutive resource updates or a multiple of such interval), o the mobility may refer to one or more performance indicators. Non limiting examples are:

■ (Per Neighbor Relation Handover Ratio) a ratio indicating a handover preparation ratio per neighbor relation, namely per neighbor cell identifier (or indicating a handover execution ratio per neighbor relation), with:

• the numerator representing the attempted handover preparations (or the attempted handover executions) between one of the cells of the first RAN node and one of the cells of the second RAN node, occurred during the time period,

• the denominator representing the attempted handover preparations (or the attempted handover executions) between the same cell of the first RAN node as used at the numerator and any of the cells of the second RAN node occurred during the time period,

• in a variant, an increase or a decrease of a ratio indicating a handover preparation ratio per neighbor relation (or an increase or a decrease of a ratio expressing a handover success ratio per neighbor relation)

■ (Per Neighbor Relation Handover Success Rate) a ratio indicating a handover preparation success rate per neighbor relation, namely per neighbor cell identifier (or a handover execution success rate per neighbor relation), with:

• the numerator representing the successful handover preparations (or the successful handover executions), between one of the cells of the first RAN node and one of the cells of the second RAN node, occurred during the time period,

• the denominator representing the attempted handover preparations (or the attempted handover executions) between the same cell of the first RAN node and the same cell of the second RAN node as used at the numerator, during the time period

• in a variant, an increase or a decrease of a ratio indicating a handover preparation success rate per neighbor relation or a ratio indicating a handover execution success rate per neighbor relation

■ (Per Neighbor Relation Handover Attempts) a number of attempted handover preparations (or a number of attempted handover executions) between one of the cells of the first RAN node and one of the cells of the second RAN node, during the time period

• in a variant, an increase or a decrease in the number of attempted handover preparations (or in the number of attempted handover executions)

■ (Per Neighbor Relation Handover Success) a number of successful handover preparations (or a number of successful handover executions) between one of the cells of the first RAN node and one of the cells of the second RAN node, during the time period

• in a variant, an increase or decrease in the number of successful handover preparations (or in the number of successful handover executions)

■ the mobility can be related to different cause values, e.g.:

• handovers triggered due to a specific cause or a set of causes (e.g. handover triggered with cause “Reduce load in serving cell” or with cause “Resource optimization handover”) • handovers triggered irrespective of the cause

• An explicit indication of either the cause value per mobility event or of the nature of the mobility event trigger can be provided. The mobility event trigger could be classified, e.g., as “Handover for coverage reasons”, “Handover for capacity optimization”.

■ the mobility can be related to different deployment characteristics or different types of cell support. Non-limiting examples include:

• cells operating on a specific carrier frequency (or frequencies), SNPN cells, PNI-NPN cells, cells with lAB-support, cells pertaining to a certain PLMN (or Equivalent PLMN), cells included in a certain Tracking Area or Tracking Area List

■ complementary information may be added, such as:

• an indication of the SSB area involved in the mobility both for the source cell and the target cell

• an indication indicating the number of subsequent handovers attempted within a given time interval after handover completion

• an indication indicating the number of RLFs that occurred within a given time interval after handover completion

■ the mobility can be related to different type of traffic, such as:

• delay/latency tolerant traffic, that is, events associated with UEs with traffic that can tolerate large latency

• delay/latency intolerant traffic, that is, events associated with UEs with traffic that may have latency requirements

■ the mobility can be related to different network slices, that is mobility events associated with user devices belonging to one or more types of network slice(s). the performance indicators may be in relation to a certain UE category, for example one indicator corresponding to internet of things (loT) UEs, and another indicator related to ultra-reliable and low latency communications (URLLC) UEs. o the performance indicators can also be related to a certain traffic characteristic of the UE, for example, the ratio of heavy traffic UEs handed over. Where heavy traffic can be UEs with a data transfer higher than a threshold value.

• receive from the second RAN node an indication indicating that the request to provide periodic updates to the first RAN node on mobility related events and associated performance has been acknowledged, or o receive from the second RAN node an indication indicating that the request to provide periodic updates to the first RAN node on mobility related events and associated performance has been refused

• receive from the second RAN node periodic updates comprising feedback on mobility events and additional indications

• use the received periodic updates comprising feedback on mobility events and additional indications to predict the characteristics and/or performances of future mobility events between the cells of the first RAN node and the cells of the second RAN node

• send to the second RAN node proposals for adjusted mobility settings (e.g., using Mobility Setting Change procedure) which are deduced from the analysis of the information received from the second RAN node. For example, if the target of the first RAN node is to reduce the successful incoming HO rate towards a given cell, the mobility setting for that cell will be configured and signaled to the second RAN node in such way that HOs will be triggered less often.

• Take the decision of

1) deactivating certain cells as a consequence of deducing from the data received from the second RAN node that mobility towards the cell is low enough to make it acceptable for the cell to be deactivated

2) activating other cells as a consequence of deducing from the data received from the second RAN node that mobility towards served cells is high enough to make it acceptable for other neighbor cells to be activated and to provide load sharing support

3) Signalling to the Second RAN node a request to activate one or more cells to cope with an increased level of UE mobility and traffic demand, deduced by the information signaled by the second RAN node [0086] Embodiments at a second RAN node (e.g., the second RAN node of Figures 5A-5B, 6, and/or 7) are discussed below, where the second RAN node can:

• receive from the first RAN node a request to provide feedback to the first RAN node, the feedback being described in the embodiments related to the first RAN node

• send to the first RAN node an indication indicating that the request to provide periodic updates to the first RAN node on mobility related events and associated performance has been acknowledged, or o sending to the first RAN node an indication indicating that the request to provide periodic updates to the first RAN node on mobility related events and associated performance has been refused

• send to the first RAN node periodic updates comprising feedback on mobility events and additional indications. Such feedback may relate to past mobility events and/or future mobility events

• receive from the first RAN node proposals for adjusted mobility settings (e.g. using legacy Mobility Setting Change procedure) with characteristics described above

• Receive from the first RAN node indications of cell activation as described above

• (optional) predict characteristics and performances of future mobility between cells of the first RAN node and cells of the second RAN node.

[0087] An example of a possible implementation is discussed below according to some embodiments of inventive concepts.

[0088] According to some embodiments of inventive concepts, Section 9.1.3.18 of Reference [3] (“RESOURCE STATUS REQUEST”) may be modified as discussed below to include the IES “Mobility Event Information” and “Report Characteristics” and the condition “if Mobility Eventinformation.”

[0089] The RESOURCE STATUS REQUEST message is sent by NG-RAN nodei (e.g., the first RAN node of Figures 5A-5B, 6, and/or 7) to NG-RAN node2 (e.g., the second RAN node of Figures 5A-5B, 6, and/or 7) to initiate the requested measurement according to the parameters given in the message.

[0090] Direction: NG-RAN nodei

[0091] According to some embodiments of inventive concepts, Section 9.1.3.21 of Reference [3], (“RESOURCE STATUS UPDATE”) may be modified as discussed below to include the IES “Mobility Event Information List” and “Mobility Event Information Item,” and the Mobility Event Information Item may be further defined as discussed below with respect to a proposed new Section for Reference [3], shown as Section 9.2.2.x.

[0092] This message is sent by NG-RAN node2 (e.g., the second RAN node of Figures 5A- 5B, 6, and/or 7) to NG-RAN nodei (e.g., the first RAN node of Figures 5A-5B, 6, and/or 7) to report the results of the requested measurements.

[0093] Direction:

nodei.

[0094] The Mobility Event Information Item is further defined as discussed below with respect to a proposed new section for Reference [3] (e.g., Section 9.2.2.x of Reference [3]).

[0095] This IE contains feedback results for monitored mobility events.

[0096] Alternative Examples of implementation are discussed below according to some embodiments of inventive concepts.

[0097] In this example of an implementation, the existing UE History Information may be extended to a value of 64 to provide some of the information described in the methods above.

[0098] According to some embodiments of inventive concepts, Section 9.3.1.95 of Reference [4] (“UE History Information”) may be modified to provide a value of 64 for the maximum number of cells in the UE history information.

[0099] This IE contains information about cells that a UE has been served by in active state prior to the target cell.

[0100] In the above example the length of the UE History Information list has been extended so to provide more statistically valid information about past UE mobility. The length of the list has been set to the value “64”, but it could be set to any value providing statistical significance.

[0101] According to some embodiments of inventive concepts, Section 9.3.1.97 of Reference [4] (“Last Visited NG-RAN Cell Information”) may be modified to add a “HO Triggering Event” IE.

[0102] The Last Visited NG-RAN Cell Information IE contains information about a cell. In case of NR cell, this IE contains information about a set of NR cells with the same NR ARFCN for reference point A, and the Global Cell ID IE identifies one of the NR cells in the set. The information is to be used for RRM purposes.

[0103] Examples of radio parameter configurations given the mobility feedback are discussed below according to some embodiments of inventive concepts.

[0104] The first network RAN node can use the received feedback to configure its radio parameters. The first RAN node can combine information from the mobility feedback with information regarding the current load in the second RAN node to predict a future load value in the first RAN node. For example, in Figure 7, the first RAN node can estimate the number of future UEs by combining the current load value (current number of UEs) in the second RAN node with the handover ratio.

[0105] Radio parameter configurations (e.g., capacity cell activation and/or mobility settings) are discussed below according to some embodiments of inventive concepts. [0106] For Capacity cell activation, the network (e.g., the first RAN node) can, for example, activate one or more capacity cells based on the predicted arrival of traffic. The first RAN node can, for example, activate a capacity cell in case more than N UEs are expected to be served by the network node in next T seconds.

[0107] For Mobility settings, the first RAN node can perform inter-frequency handovers based on the predicted arrival of traffic in order to be able to support the expected arrival of UEs. [0108] In the above embodiments, the term handover is used. However, it should be noted that the methods mentioned above are also applicable for Secondary Node (SN) change related operations.

[0109] Operations of a first RAN node 400 (e.g., a first RAN node as discussed above with respect to Figures 5A-5B, 6, and/or 8, implemented using the structure of Figure 9) will now be discussed with reference to the flow chart of Figure 11 according to some embodiments of inventive concepts. For example, modules may be stored in memory 405 of Figure 9, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 403, processing circuitry 403 performs respective operations of the flow chart.

[0110] According to some embodiments at block 1105, processing circuitry 403 (of the first RAN node) transmits (through network interface 407) a request to a second RAN node, wherein the request includes an indication to provide mobility event feedback. For example, the request of block 1105 may be transmitted as discussed above with respect to the Resource Status Request of Figure 6.

[0111] According to some embodiments at block 1109, processing circuitry 403 (of the first RAN node) receives (through network interface 407) an acknowledgement of the request from the second RAN node. For example, the acknowledgement of block 1109 may be received as discussed above with respect to the Resource Status Response (acknowledge to send feedback) of Figure 6.

[0112] According to some embodiments at block 1115, processing circuitry 403 (of the first RAN node) receives (through network interface 407) a response from the second RAN node after transmitting the request and after receiving the acknowledgement. The response includes mobility event feedback information relating to User Equipment UE mobility between at least one cell of the first RAN node and at least one cell of the second RAN node. For example, the response of block 1115 may be received as discussed above with respect to the Resource Status Update (including feedbacks on performance for mobility related events per cell) of Figure 6. [0113] According to some embodiments at block 1119, processing circuitry 403 (of the first RAN node) adjusts a radio parameter setting based on the mobility event feedback information relating to UE mobility.

[0114] Various operations from the flow chart of Figure 11 may be optional with respect to some embodiments of RAN nodes and related methods. Regarding methods of example embodiment 1 (set forth below), for example, operations of blocks 1109 and/or 1119 of Figure 11 may be optional.

[0115] Operations of a second RAN node 400 (e.g., a second RAN node as discussed above with respect to Figures 5A-5B, 6, and/or 8, implemented using the structure of Figure 9) will now be discussed with reference to the flow chart of Figure 12 according to some embodiments of inventive concepts. For example, modules may be stored in memory 405 of Figure 9, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 403, processing circuitry 403 performs respective operations of the flow chart.

[0116] According to some embodiments at block 1205, processing circuitry 403 (of the second RAN node) receives (through network interface 407) a request from a first RAN node, wherein the request includes an indication to provide mobility event feedback. For example, the request of block 1205 may be received as discussed above with respect to the Resource Status Request of Figure 6.

[0117] According to some embodiments at block 1209, processing circuitry 403 (of the second RAN node) transmits (through network interface 407) an acknowledgement of the request to the first RAN node. For example, the acknowledgement of block 1209 may be transmitted as discussed above with respect to the Resource Status Response (acknowledge to send feedback) of Figure 6.

[0118] According to some embodiments at block 1215, processing circuitry 403 (of the second RAN node) transmits (through network interface 407) a response to the first RAN node responsive to receiving the request and after transmitting the acknowledgement. The response includes mobility event feedback information relating to User Equipment UE mobility between at least one cell of the first RAN node and at least one cell of the second RAN node. For example, the response of block 1215 may be transmitted as discussed above with respect to the Resource Status Update (including feedbacks on performance for mobility related events per cell) of Figure 6.

[0119] According to some embodiments at block 1219, processing circuitry 403 (of the second RAN node) receives (through network interface 407) a request to adjust a radio parameter setting from the first RAN node after transmitting the response.

[0120] According to some embodiments at block 1225, processing circuitry 403 (of the second RAN node) adjusts the radio parameter setting based on the request to adjust the radio parameter setting.

[0121] Various operations from the flow chart of Figure 12 may be optional with respect to some embodiments of RAN nodes and related methods. Regarding methods of example embodiment 44 (set forth below), for example, operations of blocks 1209, 1219, and/or 1225 of Figure 12 may be optional.

[0122] Example embodiments are discussed below.

1. A method of operating a first radio access network, RAN, node of a radio communication network, the method comprising: transmitting (1105) a request to a second RAN node, wherein the request includes an indication to provide mobility event feedback; and receiving (1115) a response from the second RAN node after transmitting the request, wherein the response includes mobility event feedback information relating to User Equipment, UE, mobility between at least one cell of the first RAN node and at least one cell of the second RAN node.

2. The method of Embodiment 1 further comprising: adjusting (1119) a radio parameter setting based on the mobility event feedback information relating to UE mobility.

3. The method of Embodiment 2, wherein adjusting the radio parameter setting comprises predicting characteristics/performances of future UE mobility events between the at least one cell of the first RAN node and at least one cell of the second RAN node based on the mobility event feedback information relating to UE mobility, and adjusting the radio parameter setting based on predicting the characteristics/performances of the future UE mobility events.

4. The method of Embodiment 2-3, wherein adjusting the radio parameter setting comprises at least one of activating/deactivating a cell of the first RAN node based on the mobility event feedback information, activating/deactivating a multiple input multiple output, MIMO, sleep mode of the first RAN node based on the mobility event feedback information, and/or turning on/off a MIMO antenna of the first RAN node based on the mobility event feedback information.

5. The method of any of Embodiments 2-4, wherein adjusting the radio parameter setting comprises transmitting a request to the second RAN node to activate/deactivate a cell of the second RAN node based on the mobility event feedback information, to activate/deactivate a multiple input multiple output, MIMO, sleep mode of the second RAN node based on the mobility feedback information, and/or to turn on/off a MIMO antenna of the second RAN node based on the mobility event feedback information.

6. The method of any of Embodiments 2-5, wherein adjusting the radio parameter setting comprises adjusting a mobility setting configuration relating to the at least one cell of the first RAN node based on the mobility event feedback information.

7. The method of Embodiment 6, wherein adjusting the radio parameter setting further comprises transmitting an indication of the mobility setting configuration to the second RAN node.

8. The method of any of Embodiments 1-6, wherein the mobility event feedback information includes information regarding UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node. 9. The method of Embodiment 8, wherein the mobility event feedback information further includes a number of subsequent UE handovers from the at least one cell of the second RAN node by UEs corresponding to the UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node.

10. The method of Embodiment 9, wherein the subsequent UE handovers are from the at least one cell of the second RAN Node to at least one cell of a third RAN node.

11. The method of Embodiment 8, wherein the mobility event feedback information further includes an indication of subsequent UE handovers between the at least one cell of the first RAN node and the at least one cell of the second RAN node.

12. The method of Embodiment 8, wherein the mobility event feedback information further includes an indication of subsequent UE handovers between the at least one cell of the first RAN node and the at least one cell of the second RAN node by UEs corresponding to the UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node.

13. The method of any of Embodiments 8-12, wherein the mobility event feedback information further includes respective user performances experienced by UEs corresponding to the UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node.

14. The method of Embodiment 13, wherein each of the user performances comprises at least one of a Quality of Service, QoS, and/or a Quality of Experience, QoE.

15. The method of any of Embodiments 8-14, wherein the mobility event feedback information further includes indications of durations of sessions with the at least one cell of the second RAN node by UEs corresponding to the UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node. 16. The method of any of Embodiments 8-15, wherein the mobility event feedback information includes a number of radio link failures, RLFs, corresponding to the UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node

17. The method of any of Embodiments 1 -6, wherein the mobility event feedback information includes information regarding UE handovers from the at least one cell of the second RAN node to the at least one cell of the first RAN node.

18. The method of any of Embodiments 1-17, wherein the mobility event feedback information relating to UE mobility between the at least one cell of the first RAN node and the at least one cell of the second RAN node comprises mobility event feedback information relating to UE mobility between one cell of the first RAN node and one cell of the second RAN node.

19. The method of any of Embodiments 1-17, wherein the mobility event feedback information relating to UE mobility between the at least one cell of the first RAN node and the at least one cell of the second RAN node comprises mobility event feedback information relating to UE mobility between one cell of the first RAN node and a plurality of cells of the second RAN node.

20. The method of any of Embodiments 1-17 and/or 19, wherein the at least one cell of the second RAN node comprises a plurality of cells of the second RAN node sharing a common characteristic, wherein the common characteristic comprises at least one of a carrier frequency, a network slice, a non-public network, NPN, cell type, an integrated access and backhaul, IAB, supported cell type, a public land mobile network, and/or a tracking area, and/or a tracking area list.

21. The method of any of Embodiments 1-17, wherein the mobility event feedback information relating to UE mobility between the at least one cell of the first RAN node and the at least one cell of the second RAN node comprises mobility event feedback information relating to UE mobility between a plurality of cells of the first RAN node and one cell of the second RAN node. 22. The method of any of Embodiments 1-17 and/or 21, wherein the at least one cell of the first RAN node comprises a plurality of cells of the first RAN node sharing a common characteristic, wherein the common characteristic comprises at least one of a carrier frequency, a network slice, a non-public network, NPN, cell type, an integrated access and backhaul, IAB, supported cell type, a public land mobile network, and/or a tracking area, and/or a tracking area list.

23. The method of any of Embodiments 1-22, wherein the mobility event feedback information relates to UE mobility events in the past.

24. The method of any of Embodiments 1 -22, wherein the mobility event feedback information relates to UE mobility events predicted in the future.

25. The method of any of Embodiments 1-24, wherein the mobility feedback information relates to UE mobility events associated with load balancing.

26. The method of any of Embodiments 1 -24, wherein the mobility feedback information relates to UE mobility events associated with coverage.

27. The method of any of Embodiments 1 -24, wherein the mobility feedback information relates to UE mobility events to reduce load in a serving cell.

28. The method of any of Embodiments 1-24, wherein the mobility feedback information relates to UE mobility events to provide resource optimization.

29. The method of any of Embodiments 1-28, wherein the mobility feedback information includes an indication of a cause of a mobility event between the at least one cell of the first RAN node and the at least one cell of the second RAN node, and/or wherein the mobility feedback information includes an indication of a nature of a mobility event between the at least one cell of the first RAN node and the at least one cell of the second RAN node. 30. The method of any of Embodiments 1-29 further comprising: receiving (1109) an acknowledgement of the request from the second RAN node; where the response from the second RAN node is received after receiving the acknowledgement.

31. The method of an of Embodiments 1-30, wherein the mobility event feedback information includes a performance indicator.

32. The method of Embodiment 31, wherein the performance indicator is provided with respect to UE mobility events for a category of UEs.

33. The method of Embodiment 32, wherein the category of UEs comprises at least one of Internet of Things, loT, UEs, and/or Ultra-Reliable and Low Latency Communication UEs.

34. The method of any of Embodiments 32-33, wherein the category of UEs comprises UEs having a data transfer rate greater than a threshold.

35. The method of any of Embodiments 31-34, wherein the at least one cell of the first RAN node comprises a cell of the first RAN node, wherein the at least one cell of the second RAN node comprises a plurality of cells of the second RAN node, and wherein the performance indicator includes a per neighbor relation handover ratio defined as a number of attempted handover preparations/executions between the cell of the first RAN node and one of the plurality of cells of the second RAN node divided by a number of attempted handover preparations/executions between the cell of the first RAN node and the plurality of cells of the second RAN node, and/or wherein the performance indicator includes an indication of an increase/decrease of a ratio indicating a handover preparation ratio per neighbor relation, and/or wherein the performance indicator includes an indication of an increase/decrease of a ratio expressing a handover success ratio per neighbor relation. 36. The method of any of Embodiments 31-34, wherein the at least one cell of the first RAN node comprises a plurality of cells of the first RAN node, wherein the at least one cell of the second RAN node comprises a cell of the second RAN node, and wherein the performance indicator includes a per neighbor relation handover ratio defined as a number of attempted handover preparations/executions between one of the plurality of cells of the first RAN node and the cell of the second RAN node divided by a number of attempted handover preparations/executions between the plurality of cells of the first RAN node and the cell of the second RAN node.

37. The method of any of Embodiments 31-34, wherein the at least one cell of the first RAN node comprises a cell of the first RAN node, wherein the at least one cell of the second RAN node comprises a plurality of cells of the second RAN node, and wherein the performance indicator includes a per neighbor relation handover success ratio defined as a number of successful handover preparations/executions between the cell of the first RAN node and one of the plurality of cells of the second RAN node divided by a number of attempted handover preparations/executions between the cell of the first RAN node and the one of the plurality of cells of the second RAN node, and/or wherein the performance indicator includes an indication of an increase/decrease of a ratio indicating a handover preparation success rate per neighbor relation, and/or wherein the performance indicator includes an indication of an increase/decrease of a handover execution success rate per neighbor relation.

38. The method of any of Embodiments 31-34, wherein the at least one cell of the first RAN node comprises a plurality of cells of the first RAN node, wherein the at least one cell of the second RAN node comprises a cell of the second RAN node, and wherein the performance indicator includes a per neighbor relation handover success ratio defined as a number of successful handover preparations/executions between one of the plurality of cells of the first RAN node and the cell of the second RAN node divided by a number of successful handover preparations/executions between the plurality of cells of the first RAN node and the cell of the second RAN node. 39. The method of E any of Embodiments 31-34, wherein the at least one cell of the first RAN node comprises a cell of the first RAN node, wherein the at least one cell of the second RAN node comprises a cell of the second RAN node, and wherein the performance indicator includes a per neighbor relation handover attempts defined as a number of attempted handover preparations/executions between the cell of the first RAN node and the cell of the second RAN node.

40. The method of any of Embodiments 31-34, wherein the at least one cell of the first RAN node comprises a cell of the first RAN node, wherein the at least one cell of the second RAN node comprises a cell of the second RAN node, and wherein the performance indicator includes a per neighbor relation successful handovers defined as a number of successful handover preparations/executions between the cell of the first RAN node and the cell of the second RAN node.

41. The method of any of Embodiments 1-40, wherein the mobility event information includes an indication of an area associated with the at least one cell of the first RAN node and/or the at least one cell of the second RAN node.

42. The method of Embodiment 41, wherein the area associated with the at least one cell of the first RAN node and/or the at least one cell of the second RAN node comprises at least one of a tracking area, and/or a tracking area list, and/or a Synchronization Signal and/or Physical Broadcast Channel, SSB, area.

43. The method of any of Embodiments 1-42, wherein the second RAN node is a neighbor of the first RAN node.

44. A method of operating a second radio access network, RAN, node of a radio communication network, the method comprising: receiving (1205) a request from a first RAN node, wherein the request includes an indication to provide mobility event feedback; and transmitting (1215) a response to the first RAN node responsive to receiving the request, wherein the response includes mobility event feedback information relating to User Equipment, UE, mobility between at least one cell of the first RAN node and at least one cell of the second RAN node.

45. The method of Embodiment 44 further comprising: receiving (1219) a request to adjust a radio parameter setting from the first RAN node after transmitting the response; and adjusting (1225) the radio parameter setting based on the request to adjust the radio parameter setting.

46. The method of Embodiment 45, wherein the request to adjust the radio parameter setting comprises a request to activate/deactivate a cell of the second RAN node based on the mobility event feedback information, and wherein adjusting the radio parameter setting comprises activating/deactivating the cell of the second RAN node responsive to the request to activate/deactivate the cell of the second RAN node.

47. The method of any of Embodiments 45-46, wherein the request to adjust the radio parameter setting comprises a request to activate/deactivate a multiple input multiple output, MIMO, sleep mode based on the mobility event feedback information, and wherein adjusting the radio parameter setting comprises activating/deactivating the MIMO sleep mode responsive to the request to activate/deactivate the MIMO sleep mode.

48. The method of any of Embodiments 45-47, wherein the request to adjust the radio parameter setting comprises a request to turn on/off a multiple input multiple output MIMO antenna based on the mobility feedback information, and wherein adjusting the radio parameter setting comprises turning on/off the MIMO antenna responsive to the request to turn on/off the MIMO antenna.

49. The method of any of Embodiments 45-48, wherein the request to adjust the radio parameter setting comprises an indication of a mobility setting configuration relating to the at least one cell of the first RAN node, and wherein adjusting the radio parameter setting comprises updating a handover threshold based on the indication of the mobility setting configuration.

50. The method of any of Embodiments 44-49, wherein the mobility event feedback information includes information regarding UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node.

51. The method of Embodiment 50, wherein the mobility event feedback information further includes a number of subsequent UE handovers from the at least one cell of the second RAN node by UEs corresponding to the UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node.

52. The method of Embodiment 51, wherein the subsequent UE handovers are from the at least one cell of the second RAN Node to at least one cell of a third RAN node.

53. The method of Embodiment 50, wherein the mobility event feedback information further includes an indication of subsequent UE handovers between the at least one cell of the first RAN node and the at least one cell of the second RAN node.

54. The method of Embodiment 50, wherein the mobility event feedback information further includes an indication of subsequent UE handovers between the at least one cell of the first RAN node and the at least one cell of the second RAN node by UEs corresponding to the UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node.

55. The method of any of Embodiments 50-54, wherein the mobility event feedback information further includes respective user performances experienced by UEs corresponding to the UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node. 56. The method of Embodiment 55, wherein each of the user performances comprises at least one of a Quality of Service, QoS, and/or a Quality of Experience, QoE.

57. The method of any of Embodiments 50-56, wherein the mobility event feedback information further includes indications of durations of sessions with the at least one cell of the second RAN node by UEs corresponding to the UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node.

58. The method of any of Embodiments 50-57, wherein the mobility event feedback information includes a number of radio link failures, RLFs, corresponding to the UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node

59. The method of any of Embodiments 44-49, wherein the mobility event feedback information includes information regarding UE handovers from the at least one cell of the second RAN node to the at least one cell of the first RAN node.

60. The method of any of Embodiments 44-59, wherein the mobility event feedback information relating to UE mobility between the at least one cell of the first RAN node and the at least one cell of the second RAN node comprises mobility event feedback information relating to UE mobility between one cell of the first RAN node and one cell of the second RAN node.

61. The method of any of Embodiments 44-59, wherein the mobility event feedback information relating to UE mobility between the at least one cell of the first RAN node and the at least one cell of the second RAN node comprises mobility event feedback information relating to UE mobility between one cell of the first RAN node and a plurality of cells of the second RAN node.

62. The method of any of Embodiments 44-59 and/or 61, wherein the at least one cell of the second RAN node comprises a plurality of cells of the second RAN node sharing a common characteristic, wherein the common characteristic comprises at least one of a carrier frequency, a network slice, a non-public network, NPN, cell type, an integrated access and backhaul, IAB, supported cell type, a public land mobile network, and/or a tracking area, and/or a tracking area list.

63. The method of any of Embodiments 44-59, wherein the mobility event feedback information relating to UE mobility between the at least one cell of the first RAN node and the at least one cell of the second RAN node comprises mobility event feedback information relating to UE mobility between a plurality of cells of the first RAN node and one cell of the second RAN node.

64. The method of any of Embodiments 44-59 and/or 63, wherein the at least one cell of the first RAN node comprises a plurality of cells of the first RAN node sharing a common characteristic, wherein the common characteristic comprises at least one of a carrier frequency, a network slice, a non-public network, NPN, cell type, an integrated access and backhaul, IAB, supported cell type, a public land mobile network, and/or a tracking area, and/or a tracking area list.

65. The method of any of Embodiments 44-64, wherein the mobility event feedback information relates to UE mobility events in the past.

66. The method of any of Embodiments 44-64, wherein the mobility event feedback information relates to UE mobility events predicted in the future.

67. The method of any of Embodiments 44-66, wherein the mobility feedback information relates to UE mobility events associated with load balancing.

68. The method of any of Embodiments 44-66, wherein the mobility feedback information relates to UE mobility events associated with coverage.

69. The method of any of Embodiments 44-66, wherein the mobility feedback information relates to UE mobility events to reduce load in a serving cell. 70. The method of any of Embodiments 44-66, wherein the mobility feedback information relates to UE mobility events to provide resource optimization.

71. The method of any of Embodiments 44-70, wherein the mobility feedback information includes an indication of a cause of a mobility event between the at least one cell of the first RAN node and the at least one cell of the second RAN node, and/or wherein the mobility feedback information includes an indication of a nature of a mobility event between the at least one cell of the first RAN node and the at least one cell of the second RAN node.

72. The method of any of Embodiments 44-71 further comprising: transmitting (1209) an acknowledgement of the request to the first RAN node; where the response is transmitted to the first RAN node after transmitting the acknowledgement.

73. The method of an of Embodiments 44-72, wherein the mobility event feedback information includes a performance indicator.

74. The method of Embodiment 73, wherein the performance indicator is provided with respect to UE mobility events for a category of UEs.

75. The method of Embodiment 74, wherein the category of UEs comprises at least one of Internet of Things, loT, UEs, and/or Ultra-Reliable and Low Latency Communication UEs.

76. The method of any of Embodiments 74-75, wherein the category of UEs comprises UEs having a data transfer rate greater than a threshold.

77. The method of any of Embodiments 73-76, wherein the at least one cell of the first RAN node comprises a cell of the first RAN node, wherein the at least one cell of the second RAN node comprises a plurality of cells of the second RAN node, and wherein the performance indicator includes a per neighbor relation handover ratio defined as a number of attempted handover preparations/executions between the cell of the first RAN node and one of the plurality of cells of the second RAN node divided by a number of attempted handover preparations/executions between the cell of the first RAN node and the plurality of cells of the second RAN node, and/or wherein the performance indicator includes an indication of an increase/decrease of a ratio indicating a handover preparation ratio per neighbor relation, and/or wherein the performance indicator includes an indication of an increase/decrease of a ratio expressing a handover success ratio per neighbor relation.

78. The method of any of Embodiments 73-77, wherein the at least one cell of the first RAN node comprises a plurality of cells of the first RAN node, wherein the at least one cell of the second RAN node comprises a cell of the second RAN node, and wherein the performance indicator includes a per neighbor relation handover ratio defined as a number of attempted handover preparations/executions between one of the plurality of cells of the first RAN node and the cell of the second RAN node divided by a number of attempted handover preparations/executions between the plurality of cells of the first RAN node and the cell of the second RAN node.

79. The method of any of Embodiments 73-77, wherein the at least one cell of the first RAN node comprises a cell of the first RAN node, wherein the at least one cell of the second RAN node comprises a plurality of cells of the second RAN node, and wherein the performance indicator includes a per neighbor relation handover success ratio defined as a number of successful handover preparations/executions between the cell of the first RAN node and one of the plurality of cells of the second RAN node divided by a number of attempted handover preparations/executions between the cell of the first RAN node and the one of the plurality of cells of the second RAN node, and/or wherein the performance indicator includes an indication of an increase/decrease of a ratio indicating a handover preparation success rate per neighbor relation, and/or wherein the performance indicator includes an indication of an increase/decrease of a handover execution success rate per neighbor relation.

80. The method of any of Embodiments 73-77, wherein the at least one cell of the first RAN node comprises a plurality of cells of the first RAN node, wherein the at least one cell of the second RAN node comprises a cell of the second RAN node, and wherein the performance indicator includes a per neighbor relation handover success ratio defined as a number of successful handover preparations/executions between one of the plurality of cells of the first RAN node and the cell of the second RAN node divided by a number of successful handover preparations/executions between the plurality of cells of the first RAN node and the cell of the second RAN node.

81. The method of E any of Embodiments 73-77, wherein the at least one cell of the first RAN node comprises a cell of the first RAN node, wherein the at least one cell of the second RAN node comprises a cell of the second RAN node, and wherein the performance indicator includes a per neighbor relation handover attempts defined as a number of attempted handover preparations/executions between the cell of the first RAN node and the cell of the second RAN node.

82. The method of any of Embodiments 73-77, wherein the at least one cell of the first RAN node comprises a cell of the first RAN node, wherein the at least one cell of the second RAN node comprises a cell of the second RAN node, and wherein the performance indicator includes a per neighbor relation successful handovers defined as a number of successful handover preparations/executions between the cell of the first RAN node and the cell of the second RAN node.

83. The method of any of Embodiments 44-82, wherein the mobility event information includes an indication of an area associated with the at least one cell of the first RAN node and/or the at least one cell of the second RAN node.

84. The method of Embodiment 83, wherein the area associated with the at least one cell of the first RAN node and/or the at least one cell of the second RAN node comprises at least one of a tracking area, and/or a tracking area list, and/or a Synchronization Signal and/or Physical Broadcast Channel, SSB, area.

85. The method of any of Embodiments 44-84, wherein the second RAN node is a neighbor of the first RAN node. 86. A first radio access network, RAN, node (400) comprising: processing circuitry (403); and memory (405) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the first RAN node to perform operations according to any of Embodiments 1-43.

87. A first radio access network, RAN, node (400) adapted to perform operations according to any of Embodiments 1-43.

88. A computer program comprising program code to be executed by processing circuitry (403) of a first radio access network, RAN, node (400), whereby execution of the program code causes the first RAN node (400) to perform operations according to any of embodiments 1-43.

89. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (403) of a first radio access network, RAN, node (400), whereby execution of the program code causes the first RAN node (400) to perform operations according to any of embodiments 1-43.

90. A second radio access network, RAN, node (400) comprising: processing circuitry (403); and memory (405) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the second RAN node to perform operations according to any of Embodiments 44-85.

91. A second radio access network, RAN, node (400) adapted to perform operations according to any of Embodiments 44-85.

92. A computer program comprising program code to be executed by processing circuitry (403) of a second radio access network, RAN, node (400), whereby execution of the program code causes the second RAN node (400) to perform operations according to any of embodiments 44-85.

93. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (403) of a second radio access network, RAN, node (400), whereby execution of the program code causes the second RAN node (400) to perform operations according to any of embodiments 44-85.

[0123] Explanations are provided below for various abbreviations/acronyms used in the present disclosure.

Abbreviation Explanation

3 GPP 3^rd Generation Partnership Project

5G 5^th Generation

5GC 5^th Generation Core Network

ARFCN Absolute Radio Frequency Channel Number

CN Core Network

CR Cell Reselection

CU Centralized unit

CU-CP Centralized unit - control plane

CU-UP Centralized unit - user plane

DL Downlink

DU Distributed unit

El Interface between gNB-CU-CP and gNB-CU-UP

EN-DC E-UTRA-NR Dual Connectivity

E-UTRA Evolved Universal Terrestrial Radio Access

E-UTRAN Evolved Universal Terrestrial Radio Access Network

Fl Interface between gNB-CU and gNB-DU

FDD Frequency Division Duplex gNB Node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC gNB-CU CU of a gNB gNB-CU-CP CU-CP of a gNB gNB-CU-UP CU-UP of a gNB gNB-DU DU of a gNB HO Handover IAB Integrated Access and Backhaul IE Information element loT Internet of Things LTE Long Term Evolution MAC Medium Access Control MIMO Multiple input multiple output MLB Mobility Load Balancing MN Master node ng-eNB Node providing E-UTRA user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC ng-eNB-CU CU of an ng-eNB ng-eNB-DU DU of an ng-eNB NG-C Control plane interface between NG-RAN and 5GC NG-U User plane interface between NG-RAN and 5GC NG Next Generation NPN Non-Public Network NR New Radio 0AM Operation and Maintenance PBCH Physical Broadcast Channel PCell Primary Cell PSCell Primary secondary cell (LTE) or Primary SCG cell (NR) PDCP Packet Data Convergence Protocol PHY Physical PLMN Public Land Mobile Network PNI-NPN Public Network Integrated Non-Public Network QoE Quality of Experience QoS Quality of Service

RAN Radio access network

RAT Radio Access Technology

RLC Radio Link Control

RLF Radio Link Failure

RNL Radio Network Layer

RRC Radio Resource Control

RRM Radio Resource Management

RSRP Reference Signal Received Power

RSRQ Reference Signal Received Quality

SINR Signal to Interference and Noise Ratio

SCG Secondary Cell Group

SN Secondary Node

SNPN Standalone Non-Public Network

SpCell Primary cell of a master or secondary cell group

SS Synchronization Signal

SSB SS/PBCH Block

TDD Time Division Duplex

TNL Transport Network Layer

UE User equipment

UL uplink

URLLC Ultra-Reliable and Low Latency Communications

X2-C X2-Control plane between two eNBs

X2-U X2-User Plane Between two eNBs or between two en-gNBs

X2 Network Interface Between E-UTRAN nodes

X2AP X2 Application Protocol

Xn Network Interface Between NG-RAN Nodes

Xn-C Xn-Control plane

Xn-U Xn-User plane

XnAP Xn Application Protocol [0124] Additional explanation is provided below.

[0125] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0126] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. [0127] Figure 13 illustrates a wireless network in accordance with some embodiments. [0128] Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure 13. For simplicity, the wireless network of Figure 13 only depicts network 1306, network nodes 1360 and 1360b, and WDs 1310, 1310b, and 1310c (also referred to as mobile terminals). In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 1360 and wireless device (WD) 1310 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network. [0129] The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

[0130] Network 1306 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0131] Network node 1360 and WD 1310 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

[0132] As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSRBSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

[0133] In Figure 13, network node 1360 includes processing circuitry 1370, device readable medium 1380, interface 1390, auxiliary equipment 1384, power source 1386, power circuitry 1387, and antenna 1362. Although network node 1360 illustrated in the example wireless network of Figure 13 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 1360 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 1380 may comprise multiple separate hard drives as well as multiple RAM modules).

[0134] Similarly, network node 1360 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 1360 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 1360 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 1380 for the different RATs) and some components may be reused (e.g., the same antenna 1362 may be shared by the RATs). Network node 1360 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1360, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1360.

[0135] Processing circuitry 1370 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 1370 may include processing information obtained by processing circuitry 1370 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

[0136] Processing circuitry 1370 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1360 components, such as device readable medium 1380, network node 1360 functionality. For example, processing circuitry 1370 may execute instructions stored in device readable medium 1380 or in memory within processing circuitry 1370. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 1370 may include a system on a chip (SOC).

[0137] In some embodiments, processing circuitry 1370 may include one or more of radio frequency (RF) transceiver circuitry 1372 and baseband processing circuitry 1374. In some embodiments, radio frequency (RF) transceiver circuitry 1372 and baseband processing circuitry 1374 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1372 and baseband processing circuitry 1374 may be on the same chip or set of chips, boards, or units [0138] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 1370 executing instructions stored on device readable medium 1380 or memory within processing circuitry 1370. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 1370 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 1370 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1370 alone or to other components of network node 1360, but are enjoyed by network node 1360 as a whole, and/or by end users and the wireless network generally.

[0139] Device readable medium 1380 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 1370. Device readable medium 1380 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1370 and, utilized by network node 1360. Device readable medium 1380 may be used to store any calculations made by processing circuitry 1370 and/or any data received via interface 1390. In some embodiments, processing circuitry 1370 and device readable medium 1380 may be considered to be integrated.

[0140] Interface 1390 is used in the wired or wireless communication of signalling and/or data between network node 1360, network 1306, and/or WDs 1310. As illustrated, interface 1390 comprises port(s)/terminal(s) 1394 to send and receive data, for example to and from network 1306 over a wired connection. Interface 1390 also includes radio front end circuitry 1392 that may be coupled to, or in certain embodiments a part of, antenna 1362. Radio front end circuitry 1392 comprises filters 1398 and amplifiers 1396. Radio front end circuitry 1392 may be connected to antenna 1362 and processing circuitry 1370. Radio front end circuitry may be configured to condition signals communicated between antenna 1362 and processing circuitry 1370. Radio front end circuitry 1392 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1392 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1398 and/or amplifiers 1396. The radio signal may then be transmitted via antenna 1362. Similarly, when receiving data, antenna 1362 may collect radio signals which are then converted into digital data by radio front end circuitry 1392. The digital data may be passed to processing circuitry 1370. In other embodiments, the interface may comprise different components and/or different combinations of components.

[0141] In certain alternative embodiments, network node 1360 may not include separate radio front end circuitry 1392, instead, processing circuitry 1370 may comprise radio front end circuitry and may be connected to antenna 1362 without separate radio front end circuitry 1392. Similarly, in some embodiments, all or some of RF transceiver circuitry 1372 may be considered a part of interface 1390. In still other embodiments, interface 1390 may include one or more ports or terminals 1394, radio front end circuitry 1392, and RF transceiver circuitry 1372, as part of a radio unit (not shown), and interface 1390 may communicate with baseband processing circuitry 1374, which is part of a digital unit (not shown).

[0142] Antenna 1362 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 1362 may be coupled to radio front end circuitry 1392 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 1362 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 1362 may be separate from network node 1360 and may be connectable to network node 1360 through an interface or port.

[0143] Antenna 1362, interface 1390, and/or processing circuitry 1370 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 1362, interface 1390, and/or processing circuitry 1370 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

[0144] Power circuitry 1387 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 1360 with power for performing the functionality described herein. Power circuitry 1387 may receive power from power source 1386. Power source 1386 and/or power circuitry 1387 may be configured to provide power to the various components of network node 1360 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1386 may either be included in, or external to, power circuitry 1387 and/or network node 1360. For example, network node 1360 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 1387. As a further example, power source 1386 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 1387. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used. [0145] Alternative embodiments of network node 1360 may include additional components beyond those shown in Figure 13 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 1360 may include user interface equipment to allow input of information into network node 1360 and to allow output of information from network node 1360. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1360. [0146] As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (loT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3 GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3 GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

[0147] As illustrated, wireless device 1310 includes antenna 1311, interface 1314, processing circuitry 1320, device readable medium 1330, user interface equipment 1332, auxiliary equipment 1334, power source 1336 and power circuitry 1337. WD 1310 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 1310, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 1310. [0148] Antenna 1311 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 1314. In certain alternative embodiments, antenna 1311 may be separate from WD 1310 and be connectable to WD 1310 through an interface or port. Antenna 1311, interface 1314, and/or processing circuitry 1320 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 1311 may be considered an interface.

[0149] As illustrated, interface 1314 comprises radio front end circuitry 1312 and antenna 1311. Radio front end circuitry 1312 comprise one or more filters 1318 and amplifiers 1316. Radio front end circuitry 1312 is connected to antenna 1311 and processing circuitry 1320, and is configured to condition signals communicated between antenna 1311 and processing circuitry 1320. Radio front end circuitry 1312 may be coupled to or a part of antenna 1311. In some embodiments, WD 1310 may not include separate radio front end circuitry 1312; rather, processing circuitry 1320 may comprise radio front end circuitry and may be connected to antenna 1311. Similarly, in some embodiments, some or all of RF transceiver circuitry 1322 may be considered a part of interface 1314. Radio front end circuitry 1312 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1312 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1318 and/or amplifiers 1316. The radio signal may then be transmitted via antenna 1311. Similarly, when receiving data, antenna 1311 may collect radio signals which are then converted into digital data by radio front end circuitry 1312. The digital data may be passed to processing circuitry 1320. In other embodiments, the interface may comprise different components and/or different combinations of components. [0150] Processing circuitry 1320 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 1310 components, such as device readable medium 1330, WD 1310 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 1320 may execute instructions stored in device readable medium 1330 or in memory within processing circuitry 1320 to provide the functionality disclosed herein.

[0151] As illustrated, processing circuitry 1320 includes one or more of RF transceiver circuitry 1322, baseband processing circuitry 1324, and application processing circuitry 1326. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 1320 of WD 1310 may comprise a SOC. In some embodiments, RF transceiver circuitry 1322, baseband processing circuitry 1324, and application processing circuitry 1326 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 1324 and application processing circuitry 1326 may be combined into one chip or set of chips, and RF transceiver circuitry 1322 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 1322 and baseband processing circuitry 1324 may be on the same chip or set of chips, and application processing circuitry 1326 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 1322, baseband processing circuitry 1324, and application processing circuitry 1326 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 1322 may be a part of interface 1314. RF transceiver circuitry 1322 may condition RF signals for processing circuitry 1320.

[0152] In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 1320 executing instructions stored on device readable medium 1330, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 1320 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 1320 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1320 alone or to other components of WD 1310, but are enjoyed by WD 1310 as a whole, and/or by end users and the wireless network generally.

[0153] Processing circuitry 1320 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 1320, may include processing information obtained by processing circuitry 1320 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 1310, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

[0154] Device readable medium 1330 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1320. Device readable medium 1330 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 1320. In some embodiments, processing circuitry 1320 and device readable medium 1330 may be considered to be integrated.

[0155] User interface equipment 1332 may provide components that allow for a human user to interact with WD 1310. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 1332 may be operable to produce output to the user and to allow the user to provide input to WD 1310. The type of interaction may vary depending on the type of user interface equipment 1332 installed in WD 1310. For example, if WD 1310 is a smart phone, the interaction may be via a touch screen; if WD 1310 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 1332 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 1332 is configured to allow input of information into WD 1310, and is connected to processing circuitry 1320 to allow processing circuitry 1320 to process the input information. User interface equipment 1332 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 1332 is also configured to allow output of information from WD 1310, and to allow processing circuitry 1320 to output information from WD 1310. User interface equipment 1332 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 1332, WD 1310 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

[0156] Auxiliary equipment 1334 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 1334 may vary depending on the embodiment and/or scenario.

[0157] Power source 1336 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 1310 may further comprise power circuitry 1337 for delivering power from power source 1336 to the various parts of WD 1310 which need power from power source 1336 to carry out any functionality described or indicated herein. Power circuitry 1337 may in certain embodiments comprise power management circuitry. Power circuitry 1337 may additionally or alternatively be operable to receive power from an external power source; in which case WD 1310 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 1337 may also in certain embodiments be operable to deliver power from an external power source to power source 1336. This may be, for example, for the charging of power source 1336. Power circuitry 1337 may perform any formatting, converting, or other modification to the power from power source 1336 to make the power suitable for the respective components of WD 1310 to which power is supplied.

[0158] Figure 14 illustrates a user Equipment in accordance with some embodiments.

[0159] Figure 14 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 1400 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 1400, as illustrated in Figure 14, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although Figure 14 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

[0160] In Figure 14, UE 1400 includes processing circuitry 1401 that is operatively coupled to input/output interface 1405, radio frequency (RF) interface 1409, network connection interface 1411, memory 1415 including random access memory (RAM) 1417, read-only memory (ROM) 1419, and storage medium 1421 or the like, communication subsystem 1431, power source 1413, and/or any other component, or any combination thereof. Storage medium 1421 includes operating system 1423, application program 1425, and data 1427. In other embodiments, storage medium 1421 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 14, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0161] In Figure 14, processing circuitry 1401 may be configured to process computer instructions and data. Processing circuitry 1401 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1401 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0162] In the depicted embodiment, input/output interface 1405 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 1400 may be configured to use an output device via input/output interface 1405. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 1400. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 1400 may be configured to use an input device via input/output interface 1405 to allow a user to capture information into UE 1400. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0163] In Figure 14, RF interface 1409 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 1411 may be configured to provide a communication interface to network 1443a. Network 1443a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 1443a may comprise a Wi-Fi network. Network connection interface 1411 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 1411 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately. [0164] RAM 1417 may be configured to interface via bus 1402 to processing circuitry 1401 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 1419 may be configured to provide computer instructions or data to processing circuitry 1401. For example, ROM 1419 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 1421 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 1421 may be configured to include operating system 1423, application program 1425 such as a web browser application, a widget or gadget engine or another application, and data file 1427. Storage medium 1421 may store, for use by UE 1400, any of a variety of various operating systems or combinations of operating systems.

[0165] Storage medium 1421 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external microDIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 1421 may allow UE 1400 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 1421, which may comprise a device readable medium.

[0166] In Figure 14, processing circuitry 1401 may be configured to communicate with network 1443b using communication subsystem 1431. Network 1443a and network 1443b may be the same network or networks or different network or networks. Communication subsystem 1431 may be configured to include one or more transceivers used to communicate with network 1443b. For example, communication subsystem 1431 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11, CDMA, WCDMA, GSM, LIE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 1433 and/or receiver 1435 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 1433 and receiver 1435 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

[0167] In the illustrated embodiment, the communication functions of communication subsystem 1431 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 1431 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 1443b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 1443b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 1413 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 1400.

[0168] The features, benefits and/or functions described herein may be implemented in one of the components of UE 1400 or partitioned across multiple components of UE 1400. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 1431 may be configured to include any of the components described herein. Further, processing circuitry 1401 may be configured to communicate with any of such components over bus 1402. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 1401 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 1401 and communication subsystem 1431. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

[0169] Figure 15 illustrates a virtualization environment in accordance with some embodiments.

[0170] Figure 15 is a schematic block diagram illustrating a virtualization environment 1500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

[0171] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1500 hosted by one or more of hardware nodes 1530. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

[0172] The functions may be implemented by one or more applications 1520 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 1520 are run in virtualization environment 1500 which provides hardware 1530 comprising processing circuitry 1560 and memory 1590. Memory 1590 contains instructions 1595 executable by processing circuitry 1560 whereby application 1520 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

[0173] Virtualization environment 1500, comprises general-purpose or special-purpose network hardware devices 1530 comprising a set of one or more processors or processing circuitry 1560, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 1590-1 which may be non-persistent memory for temporarily storing instructions 1595 or software executed by processing circuitry 1560. Each hardware device may comprise one or more network interface controllers (NICs) 1570, also known as network interface cards, which include physical network interface 1580. Each hardware device may also include non-transitory, persistent, machine-readable storage media 1590-2 having stored therein software 1595 and/or instructions executable by processing circuitry 1560.

Software 1595 may include any type of software including software for instantiating one or more virtualization layers 1550 (also referred to as hypervisors), software to execute virtual machines 1540 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

[0174] Virtual machines 1540 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1550 or hypervisor. Different embodiments of the instance of virtual appliance 1520 may be implemented on one or more of virtual machines 1540, and the implementations may be made in different ways.

[0175] During operation, processing circuitry 1560 executes software 1595 to instantiate the hypervisor or virtualization layer 1550, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 1550 may present a virtual operating platform that appears like networking hardware to virtual machine 1540.

[0176] As shown in Figure 15, hardware 1530 may be a standalone network node with generic or specific components. Hardware 1530 may comprise antenna 15225 and may implement some functions via virtualization. Alternatively, hardware 1530 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 15100, which, among others, oversees lifecycle management of applications 1520. [0177] Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0178] In the context of NFV, virtual machine 1540 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 1540, and that part of hardware 1530 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 1540, forms a separate virtual network elements (VNE).

[0179] Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 1540 on top of hardware networking infrastructure 1530 and corresponds to application 1520 in Figure 15. [0180] In some embodiments, one or more radio units 15200 that each include one or more transmitters 15220 and one or more receivers 15210 may be coupled to one or more antennas 15225. Radio units 15200 may communicate directly with hardware nodes 1530 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

[0181] In some embodiments, some signalling can be effected with the use of control system 15230 which may alternatively be used for communication between the hardware nodes 1530 and radio units 15200.

[0182] Figure 16 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.

[0183] With reference to Figure 16, in accordance with an embodiment, a communication system includes telecommunication network 1610, such as a 3 GPP-type cellular network, which comprises access network 1611, such as a radio access network, and core network 1614. Access network 1611 comprises a plurality of base stations 1612a, 1612b, 1612c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1613a, 1613b, 1613c. Each base station 1612a, 1612b, 1612c is connectable to core network 1614 over a wired or wireless connection 1615. A first UE 1691 located in coverage area 1613c is configured to wirelessly connect to, or be paged by, the corresponding base station 1612c. A second UE 1692 in coverage area 1613a is wirelessly connectable to the corresponding base station 1612a. While a plurality of UEs 1691, 1692 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 1612.

[0184] Telecommunication network 1610 is itself connected to host computer 1630, 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. Host computer 1630 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. Connections 1621 and 1622 between telecommunication network 1610 and host computer 1630 may extend directly from core network 1614 to host computer 1630 or may go via an optional intermediate network 1620. Intermediate network 1620 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1620, if any, may be a backbone network or the Internet; in particular, intermediate network 1620 may comprise two or more sub-networks (not shown).

[0185] The communication system of Figure 16 as a whole enables connectivity between the connected UEs 1691, 1692 and host computer 1630. The connectivity may be described as an over-the-top (OTT) connection 1650. Host computer 1630 and the connected UEs 1691, 1692 are configured to communicate data and/or signaling via OTT connection 1650, using access network 1611, core network 1614, any intermediate network 1620 and possible further infrastructure (not shown) as intermediaries. OTT connection 1650 may be transparent in the sense that the participating communication devices through which OTT connection 1650 passes are unaware of routing of uplink and downlink communications. For example, base station 1612 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 1630 to be forwarded (e.g., handed over) to a connected UE 1691. Similarly, base station 1612 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1691 towards the host computer 1630. [0186] Figure 17 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments. [0187] Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 17. In communication system 1700, host computer 1710 comprises hardware 1715 including communication interface 1716 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1700. Host computer 1710 further comprises processing circuitry 1718, which may have storage and/or processing capabilities. In particular, processing circuitry 1718 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 1710 further comprises software 1711, which is stored in or accessible by host computer 1710 and executable by processing circuitry 1718. Software 1711 includes host application 1712. Host application 1712 may be operable to provide a service to a remote user, such as UE 1730 connecting via OTT connection 1750 terminating at UE 1730 and host computer 1710. In providing the service to the remote user, host application 1712 may provide user data which is transmitted using OTT connection 1750.

[0188] Communication system 1700 further includes base station 1720 provided in a telecommunication system and comprising hardware 1725 enabling it to communicate with host computer 1710 and with UE 1730. Hardware 1725 may include communication interface 1726 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1700, as well as radio interface 1727 for setting up and maintaining at least wireless connection 1770 with UE 1730 located in a coverage area (not shown in Figure 17) served by base station 1720. Communication interface 1726 may be configured to facilitate connection 1760 to host computer 1710. Connection 1760 may be direct or it may pass through a core network (not shown in Figure 17) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 1725 of base station 1720 further includes processing circuitry 1728, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 1720 further has software 1721 stored internally or accessible via an external connection. [0189] Communication system 1700 further includes UE 1730 already referred to. Its hardware 1735 may include radio interface 1737 configured to set up and maintain wireless connection 1770 with a base station serving a coverage area in which UE 1730 is currently located. Hardware 1735 of UE 1730 further includes processing circuitry 1738, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 1730 further comprises software 1731, which is stored in or accessible by UE 1730 and executable by processing circuitry 1738. Software 1731 includes client application 1732. Client application 1732 may be operable to provide a service to a human or non-human user via UE 1730, with the support of host computer 1710. In host computer 1710, an executing host application 1712 may communicate with the executing client application 1732 via OTT connection 1750 terminating at UE 1730 and host computer 1710. In providing the service to the user, client application 1732 may receive request data from host application 1712 and provide user data in response to the request data. OTT connection 1750 may transfer both the request data and the user data. Client application 1732 may interact with the user to generate the user data that it provides.

[0190] It is noted that host computer 1710, base station 1720 and UE 1730 illustrated in Figure 17 may be similar or identical to host computer 1630, one of base stations 1612a, 1612b, 1612c and one of UEs 1691, 1692 of Figure 16, respectively. This is to say, the inner workings of these entities may be as shown in Figure 17 and independently, the surrounding network topology may be that of Figure 16.

[0191] In Figure 17, OTT connection 1750 has been drawn abstractly to illustrate the communication between host computer 1710 and UE 1730 via base station 1720, 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 UE 1730 or from the service provider operating host computer 1710, or both. While OTT connection 1750 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).

[0192] Wireless connection 1770 between UE 1730 and base station 1720 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments may improve the performance of OTT services provided to UE 1730 using OTT connection 1750, in which wireless connection 1770 forms the last segment. More precisely, the teachings of these embodiments may improve the random access speed and/or reduce random access failure rates and thereby provide benefits such as faster and/or more reliable random access.

[0193] 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 OTT connection 1750 between host computer 1710 and UE 1730, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 1750 may be implemented in software 1711 and hardware 1715 of host computer 1710 or in software 1731 and hardware 1735 of UE 1730, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 1750 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 1711, 1731 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 1750 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 1720, and it may be unknown or imperceptible to base station 1720. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 1710’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 1711 and 1731 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 1750 while it monitors propagation times, errors etc.

[0194] Figure 18 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments. [0195] Figure 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 16 and 17. For simplicity of the present disclosure, only drawing references to Figure 18 will be included in this section. In step 1810, the host computer provides user data. In substep 1811 (which may be optional) of step 1810, the host computer provides the user data by executing a host application. In step 1820, the host computer initiates a transmission carrying the user data to the UE. In step 1830 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1840 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0196] Figure 19 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments. [0197] Figure 19 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 16 and 17. For simplicity of the present disclosure, only drawing references to Figure 19 will be included in this section. In step 1910 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 1920, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1930 (which may be optional), the UE receives the user data carried in the transmission.

[0198] Figure 20 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments [0199] Figure 20 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 16 and 17. For simplicity of the present disclosure, only drawing references to Figure 20 will be included in this section. In step 2010 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2020, the UE provides user data. In substep 2021 (which may be optional) of step 2020, the UE provides the user data by executing a client application. In substep 2011 (which may be optional) of step 2010, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 2030 (which may be optional), transmission of the user data to the host computer. In step 2040 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0200] Figure 21 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments [0201] Figure 21 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 16 and 17. For simplicity of the present disclosure, only drawing references to Figure 21 will be included in this section. In step 2110 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 2120 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 2130 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0202] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure. [0203] The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

[0204] At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s). lx RTT CDMA2000 lx Radio Transmission Technology

ABS Almost Blank Subframe

ARQ Automatic Repeat Request

AWGN Additive White Gaussian Noise

BCCH Broadcast Control Channel

BCH Broadcast Channel

CA Carrier Aggregation

CC Carrier Component

CCCH SDU Common Control Channel SDU

CDMA Code Division Multiplexing Access

CGI Cell Global Identifier

CIR Channel Impulse Response

CP Cyclic Prefix

CPI CH Common Pilot Channel

CPI CH Ec/No CPI CH Received energy per chip divided by the power density in the band

CQI Channel Quality information

C-RNTI Cell RNTI

CSI Channel State Information

DCCH Dedicated Control Channel

DM Demodulation

DMRS Demodulation Reference Signal

DRX Discontinuous Reception DTX Discontinuous Transmission

DTCH Dedicated Traffic Channel

DUT Device Under Test

E-CID Enhanced Cell-ID (positioning method)

E-SMLC Evolved-Serving Mobile Location Centre

ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH enhanced Physical Downlink Control Channel

E-SMLC evolved Serving Mobile Location Center

E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN

FFS For Further Study

GERAN GSM EDGE Radio Access Network

GNSS Global Navigation Satellite System

GSM Global System for Mobile communication

HARQ Hybrid Automatic Repeat Request

HSPA High Speed Packet Access

HRPD High Rate Packet Data

LOS Line of Sight

LPP LTE Positioning Protocol

MBMS Multimedia Broadcast Multicast Services

MBSFN Multimedia Broadcast multicast service Single Frequency Network

MBSFN ABS MBSFN Almost Blank Subframe

MDT Minimization of Drive Tests

MIB Master Information Block

MME Mobility Management Entity

MSC Mobile Switching Center

NPDCCH Narrowband Physical Downlink Control Channel

OCNG OFDMA Channel Noise Generator

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access OSS Operations Support System

OTDOA Observed Time Difference of Arrival

O&M Operation and Maintenance

P-CCPCH Primary Common Control Physical Channel

PCFICH Physical Control Format Indicator Channel

PDCCH Physical Downlink Control Channel

PDP Profile Delay Profile

PDSCH Physical Downlink Shared Channel

PGW Packet Gateway

PHI CH Physical Hybrid- ARQ Indicator Channel

PMI Precoder Matrix Indicator

PRACH Physical Random Access Channel

PRS Positioning Reference Signal

PSS Primary Synchronization Signal

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QAM Quadrature Amplitude Modulation

RLM Radio Link Management

RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

RS Reference Signal

RSCP Received Signal Code Power

RS SI Received Signal Strength Indicator

RSTD Reference Signal Time Difference

SCH Synchronization Channel

SCell Secondary Cell

SDU Service Data Unit

SFN System Frame Number

SGW Serving Gateway

SI System Information SIB System Information Block

SNR Signal to Noise Ratio

SON Self Optimized Network

SSS Secondary Synchronization Signal

TDOA Time Difference of Arrival

TO A Time of Arrival

TSS Tertiary Synchronization Signal

TTI Transmission Time Interval

UMTS Universal Mobile Telecommunication System

USIM Universal Subscriber Identity Module

UTDOA Uplink Time Difference of Arrival

UTRA Universal Terrestrial Radio Access

UTRAN Universal Terrestrial Radio Access Network

WCDMA Wide CDMA

WUAN Wide Local Area Network

[0205] Further definitions and embodiments are discussed below.

[0206] In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. 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 present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, 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.

[0207] When an element is referred to as being "connected", "coupled", "responsive", or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly connected", "directly coupled", "directly responsive", or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, "coupled", "connected", "responsive", or variants thereof as used herein may include wirelessly coupled, connected, or responsive. 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. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term "and/or" (abbreviated “/”) includes any and all combinations of one or more of the associated listed items.

[0208] It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another element/operation. Thus a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.

[0209] As used herein, the terms "comprise", "comprising", "comprises", "include", "including", "includes", "have", "has", "having", or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation "e.g.", which derives from the Latin phrase "exempli gratia," may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation "i.e.", which derives from the Latin phrase "id est," may be used to specify a particular item from a more general recitation.

[0210] Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).

[0211] These computer program instructions may also be stored in a tangible computer- readable 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 medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as "circuitry," "a module" or variants thereof.

[0212] It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. 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. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, 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.

[0213] Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

Claims

83 CLAIMS

1. A method of operating a first radio access network, RAN, node (400) of a radio communication network, the method comprising: transmitting (1105) a request to a second RAN node, wherein the request includes an indication to provide mobility event feedback; and receiving (1115) a response from the second RAN node after transmitting the request, wherein the response includes mobility event feedback information relating to User Equipment, UE, mobility between at least one cell of the first RAN node and at least one cell of the second RAN node.

2. The method of Claim 1 further comprising: adjusting (1119) a radio parameter setting based on the mobility event feedback information relating to UE mobility.

3. The method of Claim 2, wherein adjusting the radio parameter setting comprises predicting characteristics/performances of future UE mobility events between the at least one cell of the first RAN node and at least one cell of the second RAN node based on the mobility event feedback information relating to UE mobility, and adjusting the radio parameter setting based on predicting the characteristics/performances of the future UE mobility events.

4. The method of any of Claims 2-3, wherein adjusting the radio parameter setting comprises at least one of activating/deactivating a cell of the first RAN node based on the mobility event feedback information, activating/deactivating a multiple input multiple output, MIMO, sleep mode of the first RAN node based on the mobility event feedback information, and/or turning on/off a MIMO antenna of the first RAN node based on the mobility event feedback information.

5. The method of any of Claims 2-4, wherein adjusting the radio parameter setting comprises transmitting a request to the second RAN node to activate/deactivate a cell of the second RAN node based on the mobility event feedback information, to activate/deactivate a multiple input multiple output, MIMO, sleep mode of the second RAN node based on the 84 mobility feedback information, and/or to turn on/off a MIMO antenna of the second RAN node based on the mobility event feedback information.

6. The method of any of Claims 2-5, wherein adjusting the radio parameter setting comprises adjusting a mobility setting configuration relating to the at least one cell of the first RAN node based on the mobility event feedback information.

7. The method of any of Claims 1 -6, wherein the mobility event feedback information includes information regarding UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node.

8. The method of Claim 7, wherein the mobility event feedback information further includes respective user performances experienced by UEs corresponding to the UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node.

9. The method of any of Claims 1-8, wherein the mobility feedback information includes an indication of a cause of a mobility event between the at least one cell of the first RAN node and the at least one cell of the second RAN node, and/or wherein the mobility feedback information includes an indication of a nature of a mobility event between the at least one cell of the first RAN node and the at least one cell of the second RAN node.

10. The method of any of Claims 1 -9, wherein the mobility event feedback information includes a performance indicator.

11. The method of Claim 10, wherein the at least one cell of the first RAN node comprises a cell of the first RAN node, wherein the at least one cell of the second RAN node comprises a plurality of cells of the second RAN node, and wherein the performance indicator includes a per neighbor relation handover success ratio defined as a number of successful handover preparations/executions between the cell of the first RAN node and one of the plurality of cells of the second RAN node divided by a number of attempted handover preparations/executions between the cell of the first RAN node and the one of the plurality of cells of the second RAN node, and/or wherein the performance indicator includes an indication of an increase/decrease of a ratio indicating a handover preparation success rate per neighbor relation, and/or wherein the 85 performance indicator includes an indication of an increase/decrease of a handover execution success rate per neighbor relation.

12. The method of Claim 10, wherein the at least one cell of the first RAN node comprises a cell of the first RAN node, wherein the at least one cell of the second RAN node comprises a cell of the second RAN node, and wherein the performance indicator includes a per neighbor relation successful handovers defined as a number of successful handover preparations/executions between the cell of the first RAN node and the cell of the second RAN node.

13. The method of any of Claims 1-12, wherein the mobility event information includes an indication of an area associated with the at least one cell of the first RAN node and/or the at least one cell of the second RAN node, wherein the area comprises at least one of a tracking area, and/or a tracking area list, and/or a Synchronization Signal and/or Physical Broadcast Channel, SSB, area.

14. A method of operating a second radio access network, RAN, node (400) of a radio communication network, the method comprising: receiving (1205) a request from a first RAN node, wherein the request includes an indication to provide mobility event feedback; and transmitting (1215) a response to the first RAN node responsive to receiving the request, wherein the response includes mobility event feedback information relating to User Equipment, UE, mobility between at least one cell of the first RAN node and at least one cell of the second RAN node.

15. The method of Claim 14, further comprising: receiving (1219) a request to adjust a radio parameter setting from the first RAN node after transmitting the response; and adjusting (1225) the radio parameter setting based on the request to adjust the radio parameter setting.

16. The method of Claim 15, wherein the request to adjust the radio parameter setting comprises a request to activate/deactivate a cell of the second RAN node based on the mobility event feedback information, and wherein adjusting the radio parameter setting comprises 86 activating/deactivating the cell of the second RAN node responsive to the request to activate/deactivate the cell of the second RAN node.

17. The method of any of Claims 15-16, wherein the request to adjust the radio parameter setting comprises a request to activate/deactivate a multiple input multiple output, MIMO, sleep mode based on the mobility event feedback information, and wherein adjusting the radio parameter setting comprises activating/deactivating the MIMO sleep mode responsive to the request to activate/deactivate the MIMO sleep mode.

18 The method of any of Claims 15-17, wherein the request to adjust the radio parameter setting comprises a request to turn on/off a multiple input multiple output MIMO antenna based on the mobility feedback information, and wherein adjusting the radio parameter setting comprises turning on/off the MIMO antenna responsive to the request to turn on/off the MIMO antenna.

19. The method of any of Claims 15-18, wherein the request to adjust the radio parameter setting comprises an indication of a mobility setting configuration relating to the at least one cell of the first RAN node, and wherein adjusting the radio parameter setting comprises updating a handover threshold based on the indication of the mobility setting configuration.

20. The method of any of Claims 14-19, wherein the mobility event feedback information includes information regarding UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node.

21. The method of Claim 20, wherein the mobility event feedback information further includes respective user performances experienced by UEs corresponding to the UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node.

22. The method of any of Claims 14-21, wherein the mobility feedback information includes an indication of a cause of a mobility event between the at least one cell of the first RAN node and the at least one cell of the second RAN node, and/or wherein the mobility feedback information includes an indication of a nature of a mobility event between the at least one cell of the first RAN node and the at least one cell of the second RAN node. 87

23. The method of any of Claims 14-22, wherein the mobility event feedback information includes a performance indicator.

24. The method of Claim 23, wherein the at least one cell of the first RAN node comprises a cell of the first RAN node, wherein the at least one cell of the second RAN node comprises a plurality of cells of the second RAN node, and wherein the performance indicator includes a per neighbor relation handover success ratio defined as a number of successful handover preparations/executions between the cell of the first RAN node and one of the plurality of cells of the second RAN node divided by a number of attempted handover preparations/executions between the cell of the first RAN node and the one of the plurality of cells of the second RAN node, and/or wherein the performance indicator includes an indication of an increase/decrease of a ratio indicating a handover preparation success rate per neighbor relation, and/or wherein the performance indicator includes an indication of an increase/decrease of a handover execution success rate per neighbor relation.

25. The method of any of Claims 14-24, wherein the mobility event information includes an indication of an area associated with the at least one cell of the first RAN node and/or the at least one cell of the second RAN node, wherein the area comprises at least one of a tracking area, and/or a tracking area list, and/or a Synchronization Signal and/or Physical Broadcast Channel, SSB, area.

26. A first radio access network, RAN, node (400) of a radio communication network and comprising: processing circuitry (403); and memory (405) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the first RAN node to: transmit (1105) a request to a second RAN node, wherein the request includes an indication to provide mobility event feedback; and receive (1115) a response from the second RAN node after transmitting the request, wherein the response includes mobility event feedback information relating to User Equipment, UE, mobility between at least one cell of the first RAN node and at least one cell of the second RAN node. 88

27. The first RAN node (400) of Claim 26, wherein the memory includes instructions that when executed by the processing circuitry causes the first RAN node to: adjust (1119) a radio parameter setting based on the mobility event feedback information relating to UE mobility.

28 The first RAN node (400) of Claim 27, wherein adjusting the radio parameter setting comprises predicting characteristics/performances of future UE mobility events between the at least one cell of the first RAN node and at least one cell of the second RAN node based on the mobility event feedback information relating to UE mobility, and adjusting the radio parameter setting based on predicting the characteristics/performances of the future UE mobility events.

29. The first RAN node (400) of any of Claims 27-28, wherein adjusting the radio parameter setting comprises at least one of activating/deactivating a cell of the first RAN node based on the mobility event feedback information, activating/deactivating a multiple input multiple output, MIMO, sleep mode of the first RAN node based on the mobility event feedback information, and/or turning on/off a MIMO antenna of the first RAN node based on the mobility event feedback information.

30. The first RAN node (400) of any of Claims 27-29, wherein adjusting the radio parameter setting comprises transmitting a request to the second RAN node to activate/deactivate a cell of the second RAN node based on the mobility event feedback information, to activate/deactivate a multiple input multiple output, MIMO, sleep mode of the second RAN node based on the mobility feedback information, and/or to turn on/off a MIMO antenna of the second RAN node based on the mobility event feedback information.

31. The first RAN node (400) of any of Claims 27-30, wherein adjusting the radio parameter setting comprises adjusting a mobility setting configuration relating to the at least one cell of the first RAN node based on the mobility event feedback information.

32. The first RAN node (400) of any of Claims 26-31, wherein the mobility event feedback information includes information regarding UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node. 89

33. The first RAN node (400) of Claim 32, wherein the mobility event feedback information further includes respective user performances experienced by UEs corresponding to the UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node.

34. The first RAN node (400) of any of Claims 26-33, wherein the mobility feedback information includes an indication of a cause of a mobility event between the at least one cell of the first RAN node and the at least one cell of the second RAN node, and/or wherein the mobility feedback information includes an indication of a nature of a mobility event between the at least one cell of the first RAN node and the at least one cell of the second RAN node.

35. The first RAN node (400) of any of Claims 26-34, wherein the mobility event feedback information includes a performance indicator.

36. The first RAN node (400) of Claim 35, wherein the at least one cell of the first RAN node comprises a cell of the first RAN node, wherein the at least one cell of the second RAN node comprises a plurality of cells of the second RAN node, and wherein the performance indicator includes a per neighbor relation handover success ratio defined as a number of successful handover preparations/executions between the cell of the first RAN node and one of the plurality of cells of the second RAN node divided by a number of attempted handover preparations/executions between the cell of the first RAN node and the one of the plurality of cells of the second RAN node, and/or wherein the performance indicator includes an indication of an increase/decrease of a ratio indicating a handover preparation success rate per neighbor relation, and/or wherein the performance indicator includes an indication of an increase/decrease of a handover execution success rate per neighbor relation.

37. The first RAN node (400) of Claim 35, wherein the at least one cell of the first RAN node comprises a cell of the first RAN node, wherein the at least one cell of the second RAN node comprises a cell of the second RAN node, and wherein the performance indicator includes a per neighbor relation successful handovers defined as a number of successful handover preparations/executions between the cell of the first RAN node and the cell of the second RAN node. 90

38. The first RAN node (400) of any of Claims 26-37, wherein the mobility event information includes an indication of an area associated with the at least one cell of the first RAN node and/or the at least one cell of the second RAN node, wherein the area comprises at least one of a tracking area, and/or a tracking area list, and/or a Synchronization Signal and/or Physical Broadcast Channel, SSB, area.

39. A second radio access network, RAN, node (400) of a radio communication network and comprising: processing circuitry (403); and memory (405) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the second RAN node to: receive (1205) a request from a first RAN node, wherein the request includes an indication to provide mobility event feedback; and transmit (1215) a response to the first RAN node responsive to receiving the request, wherein the response includes mobility event feedback information relating to User Equipment, UE, mobility between at least one cell of the first RAN node and at least one cell of the second RAN node.

40. The second RAN node (400) of Claim 39, wherein the memory includes further instructions that when executed by the processing circuitry causes the second RAN node to: receive (1219) a request to adjust a radio parameter setting from the first RAN node after transmitting the response; and adjust (1225) the radio parameter setting based on the request to adjust the radio parameter setting.

41. The second RAN node (400) of Claim 40, wherein the request to adjust the radio parameter setting comprises a request to activate/deactivate a cell of the second RAN node based on the mobility event feedback information, and wherein adjusting the radio parameter setting comprises activating/deactivating the cell of the second RAN node responsive to the request to activate/deactivate the cell of the second RAN node.

42. The second RAN node (400) of any of Claims 40-41, wherein the request to adjust the radio parameter setting comprises a request to activate/deactivate a multiple input multiple output, MIMO, sleep mode based on the mobility event feedback information, and wherein adjusting the radio parameter setting comprises activating/deactivating the MIMO sleep mode responsive to the request to activate/deactivate the MIMO sleep mode.

43. The second RAN node (400) of any of Claims 40-42, wherein the request to adjust the radio parameter setting comprises a request to turn on/off a multiple input multiple output MIMO antenna based on the mobility feedback information, and wherein adjusting the radio parameter setting comprises turning on/off the MIMO antenna responsive to the request to turn on/off the MIMO antenna.

44. The second RAN node (400) of any of Claims 40-43, wherein the request to adjust the radio parameter setting comprises an indication of a mobility setting configuration relating to the at least one cell of the first RAN node, and wherein adjusting the radio parameter setting comprises updating a handover threshold based on the indication of the mobility setting configuration.

45. The second RAN node (400) of any of Claims 39-44, wherein the mobility event feedback information includes information regarding UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node.

46. The second RAN node (400) of Claim 45, wherein the mobility event feedback information further includes respective user performances experienced by UEs corresponding to the UE handovers from the at least one cell of the first RAN node to the at least one cell of the second RAN node.

47. The second RAN node (400) of any of Claims 39-46, wherein the mobility feedback information includes an indication of a cause of a mobility event between the at least one cell of the first RAN node and the at least one cell of the second RAN node, and/or wherein the mobility feedback information includes an indication of a nature of a mobility event between the at least one cell of the first RAN node and the at least one cell of the second RAN node.

48. The second RAN node (400) of any of Claims 39-47, wherein the mobility event feedback information includes a performance indicator.

49. The second RAN node (400) of Claim 48, wherein the at least one cell of the first RAN node comprises a cell of the first RAN node, wherein the at least one cell of the second RAN node comprises a plurality of cells of the second RAN node, and wherein the performance indicator includes a per neighbor relation handover success ratio defined as a number of successful handover preparations/executions between the cell of the first RAN node and one of the plurality of cells of the second RAN node divided by a number of attempted handover preparations/executions between the cell of the first RAN node and the one of the plurality of cells of the second RAN node, and/or wherein the performance indicator includes an indication of an increase/decrease of a ratio indicating a handover preparation success rate per neighbor relation, and/or wherein the performance indicator includes an indication of an increase/decrease of a handover execution success rate per neighbor relation.

50. The second RAN node (400) of any of Claims 39-49, wherein the mobility event information includes an indication of an area associated with the at least one cell of the first RAN node and/or the at least one cell of the second RAN node, wherein the area comprises at least one of a tracking area, and/or a tracking area list, and/or a Synchronization Signal and/or Physical Broadcast Channel, SSB, area.

51. A first radio access network, RAN, node (400) adapted to perform according to any of Claims 1-13.

52. A second radio access network, RAN, node (400) adapted to perform according to any of Claims 14-25.

53. A computer program comprising program code to be executed by processing circuitry (403) of a first radio access network, RAN, node (400), whereby execution of the program code causes the first RAN node (400) to perform according to any of Claims 1-13.

54. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (403) of a first radio access network, RAN, node (400), whereby execution of the program code causes the first RAN node (400) to perform according to any of Claims 1-13. 93

55. A computer program comprising program code to be executed by processing circuitry (403) of a second radio access network, RAN, node (400), whereby execution of the program code causes the second RAN node (400) to perform according to any of Claims 14-25.

56. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (403) of a second radio access network, RAN, node (400), whereby execution of the program code causes the second RAN node (400) to perform according to any of Claims 14-25.