Method for obtaining an indication of a mobility procedure and performing an action related to the mobility procedure taking the indication into account

Abstract

Embodiments herein provide, for example, a method performed by a first radio network node (12) for handling communication of UEs in a communication network (1). The first radio network node (12) transmits an indication to a second radio network node (13), wherein the indication indicates one or more of the following: a probability of a mobility procedure for a UE (10) being carried out; a type of resource allocation required at the second radio network node (13) for the UE (10); a preemption vulnerability or capability; a retention priority; that the mobility procedure is a delayed mobility procedure; a reason of the mobility procedure; and / or a priority of the mobility procedure for the UE (10).

Description

[0001] METHOD FOR OBTAINING AN INDICATION OF A MOBILITY PROCEDURE AND PERFORMING AN ACTION RELATED TO THE MOBILITY PROCEDURE TAKING THE INDICATION INTO ACCOUNT

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a first radio network node, a second radio network node, and methods performed therein regarding wireless communication. Furthermore, a computer program product and a computer readable storage medium are also provided herein. In particular, embodiments herein relate to handling communication of user equipments (UE) in a communication network.

[0004] BACKGROUND

[0005] In a typical communication network, UEs, also known as wireless communication devices, mobile stations, stations (STA) and / or wireless devices, communicate via a Radio Access Network (RAN) with one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cells, with each service area or cell being served by a radio network node such as an access node e.g. a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, a gNodeB, or an eNodeB. The service area or cell is a geographical area where radio coverage is provided by the radio network node. The radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the radio network node. The radio network node communicates over a downlink (DL) to the UE and the UE communicates over an uplink (UL) to the radio network node.

[0006] A Universal Mobile Telecommunications System (UMTS) is a third generation (3G) telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and / or High-Speed Packet Access (HSPA) for communication with user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for present and future generation networks and investigate e.g. enhanced data rate and radio capacity. In some RANs, e.g. as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto. The RNCs are typically connected to one or more core networks.

[0007] Specifications for the Evolved Packet System (EPS) have been completed within the 3GPP and coming 3GPP releases, such as New Radio (NR), are worked on. The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN / LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network. As such, the Radio Access Network (RAN) of an EPS has an architecture comprising radio network nodes connected directly to one or more core networks.

[0008] With the emerging 5G technologies such as NR, the use of very many transmit- and receive-antenna elements may be of great interest as it makes it possible to utilize beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions. NR is connected to the 5G Core Network (5GC) which comprises a number of Network Functions (NF) such as Session Management Function (SMF), Access and Mobility Management Function (AMF), Authentication Service Function (ALISF), Policy Control Function (PCF), Unified Data Manager (UDM), Network Repository Function (NRF), Network Exposure Function (NEF), just to mention some. In the 5GC, NFs can discover other NFs by using a discovery service provided by the NRF.

[0009] A current 5G RAN architecture, such as a Next Generation Radio Access Network (NG- RAN) architecture, is depicted and described in TS 38.401 v18.0.0 and is shown in Fig. 1.

[0010] The NG-RAN consists of a set of gNBs connected to the 5GC through the NG interface.

[0011] As specified in TS 38.300 v.18.1.0, the NG-RAN could also consist of a set of ng-eNBs, an ng-eNB may consist of an ng-eNB-central unit (CU) and one or more ng-eNB-distributed units (DU). An ng-eNB-CU and an ng-eNB-DU are connected via W1 interface. The general principle described here also applies to ng-eNB and W1 interface, if not explicitly specified otherwise.

[0012] 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.

[0013] A gNB may consist of a gNB-CU and one or more gNB-DUs. A gNB-CU and a gNB-DU are connected via an F1 interface.

[0014] One gNB-DU is connected to only one gNB-CU.

[0015] NG, Xn, and F1 are logical interfaces.

[0016] For NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. For E-UTRAN NR-Dual connectivity (EN-DC), the S1-U and X2-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB.

[0017] The overall architecture for separation of gNB-CU-control plane (CP) and gNB-CU-user plane (UP) is depicted in Fig. 2. A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs and multiple gNB-DUs. The gNB-CU-CP is connected to the gNB-Dll through the F1-C interface. The gNB-CU-UP is connected to the gNB-Dll through the F1-LI interface. The gNB-CU-UP is connected to the gNB-CU-CP through the E1 interface. One gNB-DU is connected to only one gNB-CU-CP. One gNB-CU-UP is connected to only one gNB-CU-CP.

[0018] The architecture shown in Fig. 2 is what 3GPP has defined for 5G. Other standardization groups, such as the Open-RAN (O-RAN) Alliance, have further extended the architecture above and have for example split the gNB-DU into two further nodes connected by a fronthaul interface. The lower node of the split gNB-DU would contain the physical (PHY) protocol and the radio frequency (RF) parts while the upper node of the split gNB-DU would host the radio link control (RLC) and medium access control (MAC). In O-RAN the upper node is called open distributed unit (O-DU), while the lower node is called open radio unit (O-RU).

[0019] As detailed in RP-234054, agreed at RAN Plenary meeting #102, it has been agreed that new artificial intelligence (Al) and / or machine learning (ML)-based use-cases will be studied as part of a release (Rel)-19 Study Item (SI). The same SI will also include possible solutions for previously studied AI / ML-based use cases which were not finalized. Among the objectives of the SI, the study will focus on AI / ML-based Network Slicing and AI / ML-based Network Energy Saving (NES), as reported below:

[0020] The aim of this study item is to further investigate new AI / ML based use cases and identify enhancements to support AI / ML functionality, and further discussions on the Rel-18 leftovers.

[0021] The detailed objectives of the SI are listed as follows:

[0022] Study two new AI / ML based use cases, i.e., Network Slicing and coverage and capacity optimization (CCO), with existing NG-RAN interfaces and architecture (including non-split architecture and split architecture).

[0023] Rel-18 leftovers as candidates for normative work, based on the Rel-18 principles, as follows:

[0024] - Mobility optimization for NR-dual connectivity (DC)

[0025] - Split architecture support for Rel-18 use cases based on the conclusions from Rel-18 Work Item

[0026] - Energy Saving enhancements, e.g., Energy Cost Prediction

[0027] - Continuous minimization drive test (MDT) collection targeting the same UE across radio resource control (RRC) states

[0028] - Multi-hop UE trajectory across gNBs

[0029] Note: RAN 3 should take the Rel-18 discussions into account.

[0030] One open point from the Rel-18 discussion is the energy cost prediction, which is related to a prediction of the energy consumption at a NG-RAN node. This prediction may be related to a potential load being offloaded at the NG-RAN node, e.g., by handing over multiple UEs. However, there is no agreement on how a source NG-RAN node signals the “potential load” to the target NG- RAN node in order to obtain the predicted energy cost.

[0031] SUMMARY

[0032] As part of developing embodiments herein one or more issues have been identified. Prior art enables the reuse of signaling steps and / or messages of UE mobility procedures such as the Handover Preparation procedure over the Xn interface for describing the so-called “Additional Load” to the target NG-RAN node of a potential offloading action, which is a description of the UEs to be offloaded to the target NG-RAN node, and is an open issue for which no consensus or agreement was reached in Rel-18 due to the inadequacy and / or complexity of the solutions proposed at the time.

[0033] The Handover Preparation procedure may be enhanced with a specific indication, such as a cause value, that allows a second radio network node, i.e. , the target radio network node of the UE mobility action, to understand that, e.g., predicted Energy Cost (EC) derived after such Handover Preparation procedure should take into account the load generated by the prepared UE mobility action, as if such handover was successfully executed.

[0034] One realization of the above method was outlined in R3-242073, submitted to RAN3#123- bis.

[0035] The existing technology for coordinated offloading of UEs describes solutions at a high level. However, the details of the necessary signaling steps and / or messages over Xn interface are still unclear, and thus to be defined. There are problems with the existing technology, where signaling steps and / or messages of UE mobility procedures are reused to trigger derivation and exchange of predictions and / or measurements, e.g., predicted EC.

[0036] In the existing technology, a source radio network node is able to add an indication, e.g., a cause value, in a message related to a UE mobility procedure, e.g., a handover, towards the target radio network node to state whether said procedure is carried out for the purpose of enabling the target radio network node to derive predictions and / or measurements that take into account the load derived from the execution of the prepared UE mobility procedure. However, current technology does not reveal how the target radio network node should understand the priority and the importance of prompt and successful execution of the prepared handover.

[0037] As previously described, the source radio network node may decide to cancel one or more UE mobility procedures that were used to obtain predictions and / or measurements after realizing that these procedures are not beneficial. In that case, the target radio network node may have allocated resources and done preparations to receive and serve these UEs, which could have limited the resources available to receive other UEs. If the other UEs were losing cell coverage and needed to perform a handover, the limited resources at the target radio network node caused by allocating resources to previous handover preparations, that might eventually be cancelled, may imply handover preparation failures and, as a consequence, results in a poor network performance.

[0038] An object of embodiments herein is to handle communication of UEs in a communication network with an improved performance.

[0039] According to an aspect the object is achieved, according to some embodiments herein, by providing a method performed by a first radio network node, such as a gNB, for handling communication of UEs in a communication network. The first radio network node transmits an indication to a second radio network node. The indication indicates one or more of the following: a probability of a mobility procedure for a UE being carried out; a type of resource allocation required at the second radio network node for the UE; a preemption vulnerability or capability; a retention priority; that the mobility procedure is a delayed mobility procedure; a reason of the mobility procedure; and / or a priority of the mobility procedure for the UE.

[0040] According to another aspect the object is achieved, according to some embodiments herein, by providing a method performed by a second radio network node for handling communication of UEs in a communication network. The second radio network node receives an indication from a first radio network node. The indication indicates one or more of the following: a probability of a mobility procedure for a UE being carried out; a type of resource allocation required at the second radio network node for the UE; a preemption vulnerability or capability; a retention priority; that the mobility procedure is a delayed mobility procedure; a reason of the mobility procedure; and / or a priority of the mobility procedure for the UE. The second radio network node performs an action related to the mobility procedure of the UE taking the indication into account, such as handles the mobility procedure of one or more UEs taking the indication into account.

[0041] It is furthermore provided herein a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the first radio network node and the second radio network node, respectively. It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to the methods herein, as performed by the first radio network node and the second radio network node, respectively.

[0042] Furthermore, according to another aspect the object is achieved, according to some embodiments herein, by providing a first radio network node and a second radio network node configured to perform the methods herein, respectively.

[0043] Thus, according to an aspect the object is achieved, according to some embodiments herein, by providing a first radio network node for handling communication of UEs in a communication network. The first radio network node is configured to transmit an indication to a second radio network node. The indication indicates one or more of the following: a probability of a mobility procedure for a UE being carried out; a type of resource allocation required at the second radio network node for the UE; a preemption vulnerability or capability; a retention priority; that the mobility procedure is a delayed mobility procedure; a reason of the mobility procedure; and / or a priority of the mobility procedure for the UE.

[0044] According to another aspect the object is achieved, according to some embodiments herein, by providing a second radio network node for handling communication of UEs in a communication network. The second radio network node is configured to receive an indication from a first radio network node. The indication indicates one or more of the following: a probability of a mobility procedure for a UE being carried out; a type of resource allocation required at the second radio network node for the UE; a preemption vulnerability or capability; a retention priority; that the mobility procedure is a delayed mobility procedure; a reason of the mobility procedure; and / or a priority of the mobility procedure for the UE. The second radio network node is configured to perform an action related to the mobility procedure of the UE taking the indication into account, such as configured to handle the mobility procedure of one or more UEs taking the indication into account.

[0045] According to embodiments herein, it is herein provided a method for the first radio network node, e.g., a RAN node, to provide an indication to the second radio network node in relation to a UE mobility procedure, e.g., between the first and second radio network nodes, about, for example, the nature, the importance, and / or the priority of said UE mobility procedure.

[0046] The first radio network node, e.g., a source RAN node, may trigger procedures towards the second radio network node, e.g., a target RAN node, to prepare a UE mobility action, e.g., a Handover Preparation procedure. The first radio network node may indicate to the second radio network node, for example, the probability of a mobility procedure for the UE being carried out, the reason, and / or the priority of the UE mobility action, so that the second radio network node is able to efficiently compare this handover preparation with other incoming handover preparations and may deduce how to prioritize one procedure over others or to derive how to manage and reserve resources for various handover preparations triggered for different probabilities, reasons, and / or priorities.

[0047] As an example, the first radio network node, e.g., a target gNB-CU, may trigger procedures towards the second radio network node, e.g., a target gNB-DU, to prepare a UE mobility action, e.g., a UE Context Setup procedure. The first radio network node may indicate to the second radio network node the reason and / or the priority of the UE mobility action.

[0048] An advantage of the methods provided herein is that a target radio network node, being an example of the second radio network node, in a UE mobility procedure may understand the importance of successful and timely execution of each prepared UE mobility procedure based on the indication provided by a source radio network node, which is an example of the first radio network node.

[0049] With this, the second radio network node may handle in an optimized way the resources to be reserved for each prepared UE mobility procedure and may ensure that resources are available in time for those procedures with, for example, a higher priority. For procedures with lower priority, a less stringent commitment to resource allocation may be needed and, e.g., resources may be allocated with delays or only be allocated on-demand after a mobility procedure is executed.

[0050] This is particularly helpful to avoid that the second radio network node reserves resources, and therefore does not make these resources available to other, higher prioritized, UE mobility procedures. For example, avoid reserving resources for UE mobility procedures that may never materialize, such as those handover preparations described in the existing technology that will be cancelled because, e.g., a predicted EC derived by the second radio network node may reveal that executing the UE mobility procedure is not beneficial for the communication network.

[0051] This will thus result in an improved performance of communication of UEs in the communication network.

[0052] BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Embodiments will now be described in more detail in relation to the enclosed drawings, in which:

[0054] Fig. 1 is a schematic overview depicting architecture according to prior art;

[0055] Fig. 2 is a schematic overview depicting architecture according to prior art;

[0056] Fig. 3 shows an overview depicting a communication network according to embodiments herein;

[0057] Fig. 4 is a combined flowchart and signaling scheme according to embodiments herein;

[0058] Fig. 5 shows a flowchart illustrating a method performed by a first radio network node according to embodiments herein;

[0059] Fig. 6 shows a flowchart illustrating a method performed by a second radio network node according to embodiments herein;

[0060] Fig. 7 shows a block diagram depicting embodiments of a first radio network node according to embodiments herein;

[0061] Fig. 8 shows a block diagram depicting embodiments of a second radio network node according to embodiments herein;

[0062] Fig. 9 schematically illustrates embodiments of a communication system,

[0063] Fig. 10 is a generalized block diagram of embodiments of a UE,

[0064] Fig. 11 is a generalized block diagram of embodiments of a network node, and

[0065] Fig. 12 is a generalized block diagram of embodiments of a virtualization environment. DETAILED DESCRIPTION

[0066] Embodiments herein relate to communication networks in general. Fig. 3 is a schematic overview depicting a communication network 1 . The communication network 1 comprises one or more RANs and one or more CNs. The communication network 1 may use one or a number of different technologies. Embodiments herein relate to recent technology trends that are of particular interest in a New Radio (NR) context, however, embodiments are also applicable in further development of existing wireless communications systems such as, e.g., LTE or Wideband Code Division Multiple Access (WCDMA), or upcoming technologies such as 6G.

[0067] In the communication network 1 , one or more UEs such as a user equipment (UE) 10 exemplified herein as a wireless device such as a mobile station, a non-access point (non-AP) station (STA), a STA and / or a wireless terminal, are comprised communicating via, e.g., one or more Access Networks (AN), e.g., radio access network (RAN), to one or more core networks (CN). It should be understood by the skilled in the art that “UE” is a non-limiting term which means any terminal, wireless communications terminal, user equipment, narrowband internet of things (NB-loT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node, e.g., smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node within an area served by the radio network node.

[0068] The communication network 1 comprises a first radio network node 12 or just radio network node, providing radio coverage over a geographical area, a first service area 11 or first cell, of a first radio access technology (RAT), such as NR, LTE, or similar. The radio network node 12 may be a transmission and reception point such as an access node, an O-RAN node, an access controller, a base station, e.g., a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNodeB), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a UE within the area served by the first radio network node depending, e.g., on the first radio access technology and terminology used. The first radio network node may be referred to as a source or serving radio network node wherein the service area may be referred to as a serving cell, and the serving network node communicates with the wireless device in form of DL transmissions to the wireless device and UL transmissions from the wireless device. The first radio network node may be a gNB- CU, a source gNB-CU, a source radio network node or similar. It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage.

[0069] The communication network 1 comprises a second radio network node 13 or just radio network node, providing radio coverage over a geographical area, a second service area 14 or second cell, of a second RAT, such as NR, LTE, or similar. The second radio network node 13 may be a transmission and reception point such as an access node, an O-RAN node, an access controller, a base station, e.g., a radio base station such as a gNB, an eNB or eNodeB, a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a WLAN access point or an AP STA, a transmission arrangement of a radio base station, a standalone access point or any other network unit or node capable of communicating with a wireless device within the area served by the second radio network node depending, e.g., on the second radio access technology and terminology used. The second radio network node may be referred to as a visiting radio network node or target radio network node, wherein the service area may be referred to as a visiting cell or target cell, and the second radio network node communicates with the UE in form of DL transmissions to the UE and UL transmissions from the UE. The second radio network node may be a gNB-Dll, a target gNB-Cll, a target radio network node or similar. It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage.

[0070] The first RAT may be the same RAT as the second RAT or the first RAT may be a different RAT than the second RAT.

[0071] The communication network 1 may further comprise a number of network nodes providing, e.g., in NR, applications, such as an application server (AS), or network functions (NF) or actually instantiations of NFs also referred to as NF instances, such as a first network node 15 , also referred to as network node 15, providing, for example, an XR application, an instantiation of an AMF, or any other NF instances in the communication network 1. The different NF instances may have different tasks. Other functions may be for LTE such as Mobility Management Entity (MME) or similar.

[0072] The respective node may be a standalone server, a cloud-implemented server, a distributed server or processing resources in a server farm or same node. Embodiments herein may be implemented as physical bare metal, virtual or cloud native such as Kubernetes environment in, e.g., hyper-cloud networks.

[0073] According to embodiments herein, the first radio network node 12 transmits an indication to the second radio network node 13. The indication indicates one or more of the following: a probability of a mobility procedure for the UE 10 being carried out; a type of resource allocation required at the second radio network node 13 for the UE 10; a preemption vulnerability or capability; a retention priority; that the mobility procedure is a delayed mobility procedure; a reason of the mobility procedure; and / or a priority of the mobility procedure for the UE 10. The second radio network node 13 performs an action related to the mobility procedure of the UE 10 taking the indication into account. Thus, the second radio network node 13 may handle a mobility procedure of one or more UEs 10 taking the indication into account.

[0074] Embodiments herein provide a signaling of the indication between the first radio network node 12 and the second radio network node 13 about, for example, the nature, importance, and / or priority of a UE mobility procedure. When used in conjunction with the existing technology, it allows the UE mobility procedure to be efficiently used to trigger the derivation and exchange of predictions and / or measurements between radio network nodes without incurring resource saturation due to indiscriminate resource allocation towards all received handover preparation procedures. Namely, the second radio network node 13, such as a target radio network node of the UE mobility procedure, may allocate resources for the prepared handovers more efficiently and ensure that high priority handovers are served with higher probability.

[0075] Fig. 4 is a combined flow chart and signaling scheme according to some embodiments.

[0076] Action 401. The first radio network node 12 provides the indication to the second radio network node 13. The indication indicates one or more of the following: the probability of the mobility procedure for the UE 10 being carried out; the type of resource allocation required at the second radio network node 13 for the UE 10; the preemption vulnerability or capability; the retention priority; that the mobility procedure is a delayed mobility procedure; the reason of the mobility procedure; and / or the priority of the mobility procedure for the UE 10.

[0077] Action 402. The second radio network node 13 performs the action related to the mobility procedure of the UE 10 taking the indication into account. The second radio network node 13 may perform a mobility procedure taking the indication into account. For example, the second radio network node 13 may allocate resources for a mobility procedure by comparing priorities of different mobility procedures.

[0078] The method actions performed by the first radio network node 12 for handling communication of UEs in the communication network 1, for example, handling handover of the UE 10, according to embodiments herein will now be described with reference to a flowchart depicted in Fig. 5. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.

[0079] Action 501. The first radio network node 12 may determine the indication of the mobility procedure. The first radio network node 12 may determine the probability of a mobility procedure for the UE 10 being carried out; a type of resource allocation required at the second radio network node 13 for the UE 10; a preemption vulnerability or capability; a retention priority; that the mobility procedure is a delayed mobility procedure; a reason of the mobility procedure; and / or a priority of the mobility procedure for the UE 10. The second radio network node 13 performs an action related to the mobility procedure of the UE 10 taking the indication into account.

[0080] Action 502. The first radio network node 12 transmits the indication to the second radio network node 13. The indication indicates one or more of the following: the probability of the mobility procedure for the UE 10 being carried out; the type of resource allocation required at the second radio network node 13 for the UE 10; the preemption vulnerability or capability; the retention priority; that the mobility procedure is the delayed mobility procedure; the reason of the mobility procedure; and / or the priority of the mobility procedure for the UE 10. The indication may further indicate that a previously received UE mobility procedure needs to be updated, and / or that no actual mobility event is being attempted for the UE 10, but rather measurements and / or predictions are being requested. The indication may indicate an energy consumption for handling the UE to be derived at the second radio network node 13, and / or may comprise a numerical value. The indication may comprise an information element which indicates the reason and / or the priority. The reason may be one out of:

[0081] - a radio coverage reason,

[0082] - an energy saving reason,

[0083] - a service level agreement (SLA) fulfillment reason,

[0084] - a radio coverage reason and an energy saving reason, and / or

[0085] - a radio coverage reason and an SLA fulfillment reason The priority may be one out of:

[0086] - a numerical index, or

[0087] - an enumerated type, with one or more values indicating, for example, low, medium or high priority.

[0088] Thus, it is herein described a method for the first radio network node 12, e.g., a RAN node, to provide the indication to the second radio network node 13 in relation to a UE mobility procedure, e.g., transfer of the UE 10 or transfer of serving the UE 10, between the first and second radio network nodes. The indication may be about the nature, importance, and / or priority of said UE mobility procedure.

[0089] The first radio network node 12 may be a source gNB, or, a source gNB-CU, the second radio network node 13 may be a target gNB, or, target gNB-CU, and the UE mobility procedure may be a Handover Preparation procedure over the Xn interface, and / or the UE mobility procedure may be a Handover Preparation or a Handover Resource Allocation procedure over the NG interface.

[0090] The first radio network node 12 may be a target gNB-CU, or, target gNB-CU-CP, the second radio network node 13 may be a target gNB-DU, and the UE mobility procedure may be realized by means of a UE Context Setup procedure over the F1 interface.

[0091] The first radio network node 12 may be a target gNB-CU-CP, the second radio network node may be a target gNB-CU-UP, and the UE mobility procedure may be realized by means of a Bearer Context Setup procedure over the E1 interface.

[0092] The first radio network node 12 may include, in the signaling related to the UE mobility procedure, e.g., in an Xn application protocol (AP) HANDOVER REQUEST message for a Handover Preparation procedure, information describing the reason and the priority level of the UE mobility procedure. The indication may comprise one or more of the following, or alternatively, the characteristics below may be represented by a single piece of information with multiple code points:

[0093] - An information element (IE) indicating the reason for the UE mobility procedure, e.g., a handover, for example, whether the handover is triggered for:

[0094] (radio) coverage reasons, i.e., not executing the handover would imply that the UE 10 goes out of coverage; energy saving reasons, namely if the handover is executed, the communication network enters a better energy consumption state, but if the handover is not executed, the UE 10 does not move out of coverage, while the energy consumption of the communication network does not improve;

[0095] SLA fulfillment reasons, e.g., where the SLA fulfillment targets are for one or more network slices. Namely if the handover is executed, the communication network improves an SLA fulfillment status, but if the handover is not executed, the UE 10 does not move out of coverage, while the levels of SLA fulfillment, e.g., for one or more network slices, do not improve;

[0096] (radio) coverage and energy saving reasons, namely if the handover is executed, the communication network enters a better energy consumption state and if the handover is not executed the UE 10 moves out of coverage; and / or

[0097] (radio) coverage and SLA fulfillment reasons, namely if the handover is executed, the communication network improves an SLA fulfillment status and if the handover is not executed the UE 10 moves out of coverage.

[0098] - An IE indicating the priority of the UE mobility procedure, e.g., a handover. This might be encoded as a numerical index, where higher values would imply higher priority, or vice versa, or as an enumerated type, with values, e.g., “High Priority”, Medium Priority”, “Low Priority”. This parameter informs the second radio network node 13 about the importance of successful preparation and execution of the UE mobility procedure. In one embodiment, this parameter is used to inform the second radio network node 13 about how resource allocation for this procedure should be handled and whether the allocation should be “hard” or “guaranteed”, i.e., resources should be pre-allocated and readily available, or “soft” or “best effort”, i.e., resources do not need to be reserved and may be allocated once the UE 10 executes the handover, or resources for bearers not subject to guaranteed performance - like non-guaranteed bit rate (GBR) bearers - may be allocated only if available at the time of execution, or any other resource management policy in between.

[0099] - An IE indicating the probability of the UE mobility procedure being carried out. This parameter may be encoded as a numerical value, e.g., between 0 and 100, where the highest value, e.g., 100, corresponds to an absolute certainty that the UE mobility procedure will be executed and the lowest value, e.g., 0, corresponds to an absolute certainty that the UE mobility procedure will not be executed. For example, a probability of 0 would indicate that this UE mobility procedure will not be carried out, and it is merely signaled as a trigger to derive and report measurements and / or predictions, e.g., for assessing the benefits / gain expected to result from the UE mobility procedure for network and / or UE operation or to gather data that may be used at the source radio network node as training data or as rewards to fine tune an Al algorithm and / or an ML algorithm.

[0100] - An IE indicating the type of resource allocation required at the second radio network node 13 for the UE 10. In one option, the default value of the IE, or a value implicitly assumed if the IE is absent, indicates to the second radio network node 13 to reserve resources for the UE 10. In one variation, the type of resource allocation can be: “hard”, or “guaranteed”, or “soft”, or “best effort”, wherein “hard” indicates that resources are allocated to and ready to be used by the UE 10, and “soft” indicates that resources for the UE 10 can be reallocated to another UE if needed.

[0101] - An IE indicating a preemption vulnerability, for the Handover, or for the UE 10, or for the resources allocated to the UE 10, indicating to the second radio network node 13 to which degree the UE 10 associated to the Handover, or the resources allocated to the UE 10, can be preempted. For example, resources for a Handover at high preemption vulnerability can be released to make room for a handover at lower preemption vulnerability. In another example, a preemption vulnerability may be a flag indicating whether resources allocated to the UE 10 can be preempted or not.

[0102] - An IE indicating a preemption capability, for the Handover, or for the UE 10, or for the resources allocated to the UE 10, indicating to the second radio network node 13 to which degree the resources allocated to the UE 10 for this handover, can preempt resources allocated for another UE. For example, resources for a Handover at high value of preemption capability can preempt resources allocated for a UE who was prepared for handover or handed over before and for which the preemption capability has a lower value. In another example, a preemption capability is a flag indicating whether the handover for which the preemption capability flag is set can preempt resources allocated for a UE associated to a handover whose preemption vulnerability flag is set.

[0103] - An IE indicating a retention priority, for the Handover, or for the UE 10, or for the resources allocated to the UE 10, indicating to the second radio network node 13 to which degree the UE 10 associated to the Handover, or the resources allocated to the UE 10, can be retained. For example, resources for a Handover at low retention priority can be released to make room for a handover at higher retention priority.

[0104] - An IE indicating the value of one or more metrics relating to serving the UE 10, or a group of UEs comprising the UE 10, which allows the second radio network node 13 to understand the likelihood of the Handover, or a group of Handovers, to be executed. For example, if the second radio network node 13 predicts that it can serve the UE 10, or group of UEs comprising the UE 10, with an energy consumption or an EC lower than a certain value, it should assume that the first radio network node 12 will execute the Handover, or group of Handovers, and it is beneficial to allocate the needed resources. The further away the predicted energy consumption or EC is from the signaled value, the more certain the Handover, or group of Handovers, will be executed, if beneficial, or will not be executed, if not beneficial.

[0105] - An IE indicating that the UE 10 in subject for the Handover has a very high EC associated with it on the first radio network node 12, or an indication that offloading this particular UE 10 would enable significant energy savings at the first radio network node 12, i.e. , it may be blocking certain energy saving (ES) states and therefore it is preferable and highly likely that the handover procedure will be executed.

[0106] - An IE indicating a request for a delayed UE mobility procedure, e.g., a delayed Handover Preparation procedure. A corresponding wait time and / or delay to be adopted by the second radio network node 13 may be indicated as well, where the wait time and / or delay refers to how long the second radio network node 13 can wait before allocating resources.

[0107] - An IE indicating that the current UE mobility procedure, e.g., a Handover Preparation procedure, is for a delayed UE mobility procedure, e.g., a delayed Handover, i.e., a handover for which the second radio network node 13 is not requested to allocate resources immediately for the UE 10. Alternatively, the indication may be that the delayed UE mobility procedure at the second radio network node 13 is requested or allowed. A corresponding suggested, allowed, and / or maximum wait time and / or delay that the second radio network node 13 can use to determine when resources for the UE 10 need to be allocated may be indicated as well.

[0108] The method actions performed by the second radio network node 13 for handling communication of UEs in the communication network 1, for example, handling handover of the UE 10, according to embodiments herein will now be described with reference to a flowchart depicted in Fig. 6. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.

[0109] Action 601. The second radio network node 13 receives the indication from the first radio network node 12. The indication indicates one or more of the following: the probability of the mobility procedure for the UE 10 being carried out; the type of resource allocation required at the second radio network node 13 for the UE 10; the preemption vulnerability or capability; the retention priority; that the mobility procedure is a delayed mobility procedure; the reason of the mobility procedure; and / or the priority of the mobility procedure for the UE 10. Action 602. The second radio network node 13 performs an action related to a mobility procedure of the UE 10 taking the indication into account. The second radio network node 13 may derive or determine, from the indication, the probability of the mobility procedure for the UE 10 being carried out; the type of resource allocation required at the second radio network node 13 for the UE 10; the preemption vulnerability or capability; the retention priority; that the mobility procedure is a delayed mobility procedure; the reason of the mobility procedure; and / or the priority of the mobility procedure for the UE. The action may comprise admitting or not admitting the mobility procedure of the UE 10 based on the indication.

[0110] The action may comprise comparing the mobility procedure of the UE 10 with one or more other incoming mobility procedures and deducing how to prioritize the mobility procedures over one another.

[0111] The action may comprise allocating resources based on the indication.

[0112] The indication may be comprised in a HANDOVER REQUEST message indicating that the mobility procedure is a delayed mobility procedure and the action may comprise sending a HANDOVER REQUEST ACKNOWLEDGE message indicating that the HANDOVER REQUEST message is accepted and / or an amount of wait time for the delayed mobility procedure.

[0113] The action may comprise deriving, based on the indication, an energy consumption at the second radio network node 13. The second radio network node 13 may derive and / or predict that the second radio network node 13 can serve the UE 10 with an (additional) energy consumption or an EC lower than a certain value. And then the second radio network node 13 may assume that the first radio network node 12 will execute the Handover and it is beneficial to allocate the needed resources. Thus, the second radio network node 13 may derive the probability of the mobility procedure by comparing a received EC value with a local, predicted EC value.

[0114] In one embodiment, the first radio network node 12 includes in the HANDOVER REQUEST message the indication, e.g., a flag, indicating that no actual mobility event is being attempted for the UE 10, but rather measurements and / or predictions are being requested, and should be provided to the first radio network node 12, for a potential offloading action as if the UE 10 would be moved to the second radio network node 13. In this case, at reception of the indication, the second radio network node 13, such as a target radio network node, would take the information in the Handover Preparation signaling into account to, e.g., infer predictions concerning energy consumption levels or EC, but it would not allocate any resource for the UE 10 associated to the Handover Preparation.

[0115] In another embodiment, the HANDOVER REQUEST message comprises time related information concerning resource allocation at the second radio network node 13, e.g., when in the future the offloading action is planned to occur for the UE 10. In addition to the time of the planned action, the indication may indicate a delta time after the planned action until which any allocated resources that are blocked may be released even without an explicit indication that the handover is cancelled.

[0116] In one embodiment, the second radio network node 13, such as a gNB-CU-CP of a second RAN node, based on information provided in the HANDOVER REQUEST message concerning the reason for preparing the handover and / or the priority of the handover procedure, may refrain from setting up a UE Context for the UE 10, i.e., the gNB-CU-CP does not initiate an UE Context Setup procedure towards the gNB-DU for the UE 10. In one variation, the refraining from setting up a UE Context for the UE 10 occurs when the second radio network node 13, such as the gNB-CU-CP of the second RAN node, receives an indication which implicitly indicates to the second radio network node 13 not to setup a UE context. In a dependent embodiment, the second radio network node 13, such as the gNB-CU-CP of the second RAN node, based on information provided in the HANDOVER REQUEST message concerning the reason for preparing the handover and / or the priority of the handover procedure, may trigger an F1: UE Context Setup procedure. This procedure may include information concerning the reason for triggering the UE Context Setup procedure. Based on that the gNB-DU receiving the UE Context Setup Request message may decide to use the information in the message purely to, e.g., compute a prediction of the energy consumption levels or EC, but it will not store information into a UE context nor change its configuration in function of it.

[0117] In a related embodiment, when one of the attributes mentioned in the previous embodiments is included in the HANDOVER REQUEST message, e.g., a priority level, a type of resource allocation, a preemption vulnerability, or a retention priority, etc., the first radio network node 12 may not monitor the time for the Handover Preparation procedure, e.g., the source NG- RAN node does not start a timer TXnRELOCprep.

[0118] In one embodiment, the second radio network node 13, such as gNB-CU-CP of the second RAN node, based on information provided in the HANDOVER REQUEST message concerning the reason for preparing the handover and / or the priority of the handover procedure, indicates to a gNB-DU to initiate the setup of a UE Context for the UE 10. The UE Context, or any / all radio resources associated with the UE 10 may be characterized by one of the attributes comprised in the HANDOVER REQUEST message, or a translation thereof, for example a priority level, a type of resource allocation, a preemption vulnerability, and / or a retention priority.

[0119] The gNB-CU-CP of the second RAN node, based on information provided in a HANDOVER REQUEST message for a second UE, wherein none of the attributes indicated in the embodiments above, such as a priority level, a type of resource allocation, a preemption vulnerability, a retention priority, etc., is present, indicates to the gNB-DU to release a UE Context for a first UE, wherein the UE Context, or any / all radio resources associated with the first UE is characterized by at least one of the attributes indicated in the embodiments above, for example, a priority level, a type of resource allocation, a preemption vulnerability, a retention priority, etc.. In a related embodiment, the second radio network node 13, such as the gNB-CU-CP of the second RAN node, based on information provided in the HANDOVER REQUEST message concerning the reason for preparing the handover and / or the priority of the handover procedure, refrains from initiating the establishment of a bearer context in the gNB-CU-UP for the UE 10, i.e., the gNB-CU-CP does not initiate a Bearer Context Setup procedure towards the gNB-CU-UP for the UE 10.

[0120] In one embodiment, the second radio network node 13 such as the gNB-CU-CP of the second RAN node, based on information provided in the HANDOVER REQUEST message concerning the reason for preparing the handover and / or the priority of the handover procedure, indicates to the gNB-CU-UP to initiate the setup of a Bearer Context for the UE 10. The Bearer Context, or any part of it, associated with the UE 10 is characterized by one of the attributes comprised in the HANDOVER REQUEST message, or a translation thereof, for example a priority level, a type of resource allocation, a preemption vulnerability, and / or a retention priority.

[0121] In one embodiment, the second radio network node 13 such as the gNB-CU-CP of the second RAN node, based on information provided in a HANDOVER REQUEST message for a second UE, wherein none of the attributes indicated in the embodiments above, such as a priority level, a type of resource allocation, a preemption vulnerability, a retention priority, etc., is present, indicates to the gNB-CU-UP to release a Bearer Context for a first UE, wherein the Bearer Context, or any part of it, associated with the first UE is characterized by at least one of the attributes indicated in the embodiments above, such as a priority level, a type of resource allocation, a preemption vulnerability, a retention priority, etc..

[0122] In one embodiment, the second radio network node 13 such as the gNB-CU-CP of the second RAN node, based on the indication in the HANDOVER REQUEST message to wait before setting up resources for the UE 10, refrains from setting up a UE Context, or parts thereof, for the UE 10. That is, the gNB-CU-CP does not initiate a UE Context Setup procedure, or parts thereof, towards the gNB-DU.

[0123] In one embodiment, the second radio network node 13 such as the gNB-CU-CP of the second RAN node, based on the indication in the HANDOVER REQUEST message to wait before setting up resources for the UE 10, refrains from setting up a Bearer Context, or parts thereof, for the UE 10. That is, the gNB-CU-CP does not initiate a Bearer Context Setup procedure towards the gNB-CU-UP.

[0124] In one embodiment, the second radio network node 13 such as the gNB-CU-CP of the second RAN node, based on the indication in the HANDOVER REQUEST message to wait before setting up resources for the UE 10, sends a HANDOVER REQUEST ACKNOWLEDGE message indicating that the request is accepted and optionally an amount of wait time and / or delay.

[0125] In one embodiment, the second radio network node 13 such as the gNB-CU-CP of the second RAN node, based on the presence in the HANDOVER REQUEST message of a wait time and / or delay parameter, refrains from setting up a UE Context for the UE 10 until the time indicated by the wait time and / or delay parameter has passed, or a corresponding timer has expired. That is, the gNB-CU-CP does not initiate a UE Context Setup procedure towards the gNB-DU for the UE 10 during the established time.

[0126] In one embodiment, the second radio network node 13 such as the gNB-CU-CP of the second RAN node, based on the presence in the HANDOVER REQUEST message of a wait time and / or delay parameter, refrains from setting up a UE Context for the UE 10 for at least a time interval as long as the value of the wait time and / or delay parameter, or a function thereof, i.e., the gNB-CU-CP waits before initiating a UE Context Setup procedure towards the gNB-DU for the UE 10. If the wait time and / or delay parameter is set to a value indicating to wait indefinitely, then the UE Context Setup procedure towards the gNB-DU for the UE 10 is not initiated at all.

[0127] In a related embodiment, the wait time and / or delay parameter is transferred from the gNB- CU-CP to the gNB-DU. The gNB-DU, when a time interval whose duration is at least equal to the wait time and / or delay parameter has passed, sends a message to the gNB-CU-CP indicating that the setup of a UE Context Setup, or parts thereof, is required for the UE 10. If the answer is positive, the UE context can be set up for the UE 10 using legacy methods.

[0128] In one embodiment, the second radio network node 13 such as the gNB-CU-CP of the second RAN node, based on the presence in the HANDOVER REQUEST message of a wait time and / or delay parameter, refrains from initiating the establishment of a bearer context in the gNB- CU-UP for the UE 10 until the time indicated by the wait time and / or delay parameter has passed, or a corresponding timer has expired. That is, the gNB-CU-CP does not initiate a Bearer Context Setup procedure towards the gNB-CU-UP for the UE 10 during the established time.

[0129] In one embodiment, the second radio network node 13 such as the gNB-CU-CP of the second RAN node, based on the presence in the HANDOVER REQUEST message of a wait time and / or delay parameter, refrains from initiating the establishment of a bearer context in the gNB- CU-UP for the UE 10 for at least a time interval as long as the value of the wait time and / or delay parameter, or a function thereof, i.e., the gNB-CU-CP waits before initiating a Bearer Context Setup procedure towards the gNB-CU-UP. If the wait time / delay parameter is set to a value indicating to wait indefinitely, then the Bearer Context Setup procedure is not initiated at all.

[0130] In a related embodiment, the wait time and / or delay parameter is transferred from gNB-CU- CP to gNB-CU-UP. The gNB-CU-UP, when a time interval whose duration is at least equal to the wait time and / or delay parameter has passed, sends a message to the gNB-CU-CP indicating that the setup of a Bearer Context Setup, or parts thereof, is required for the UE 10. If the answer is positive, the Bearer context can be set up for the UE 10 using legacy methods.

[0131] In one embodiment, the first radio network node 12 signals to the second radio network node 13 that the previously received UE mobility procedure, e.g., a Handover Preparation procedure, needs to be updated, for e.g. one or more of the following reasons: - A new protocol data unit (PDU) Session or data radio bearer (DRB) needs to be established and handed over.

[0132] - A PDU Session or DRB needs to be removed.

[0133] The probability of arrival has drastically evolved.

[0134] The UE 10 needs to be handed over immediately for a radio condition reason.

[0135] The type of resource allocation, or the preemption parameters, or the retention priority, or any of the previously described parameters, or a combination of any of these parameters has changed.

[0136] In one embodiment, the update of the Handover Procedure is performed by sending a subsequent HANDOVER REQUEST message, including the same UE AP identities (ID) used in the previous procedure, and including an IE indicating that this new procedure should replace the previously received Handover Procedure.

[0137] A UE mobility procedure, e.g., Handover Preparation procedure, may be failed and / or rejected depending on the priority level, the type of resource allocation, the preemption vulnerability, the retention priority, and / or any of the previously described parameters / attributes, given that one or more of these parameters and / or attributes is comprised in an initiating message of the procedure.

[0138] In one embodiment, when one of these attributes in the HANDOVER REQUEST message, the second radio network node 13 may consider this information along with the resource capacity, utilization / allocation and / or availability, and / or the (number of) ongoing / pending procedures at the second radio network node 13 to determine whether to admit the UE 10, i.e. , admit all requested PDU session resources, or not admit the UE 10, or not admit at least one requested PDU session resource, depending on priority level, type of resource allocation, preemption vulnerability, retention priority, etc.

[0139] In a related embodiment, if the second radio network node 13 does not admit the UE 10, i.e., does not admit at least one requested PDU session resource due to one or more of: the priority level, the type of resource allocation, the preemption vulnerability, the retention priority, etc., the second radio network node 13 may indicate, e.g., in the HANDOVER PREPARATION FAILURE message, the reason for not admitting the UE 10 or at least one requested PDU session resource, e.g., too low priority level, too low priority level for hard resource allocation, or similar.

[0140] An initially acknowledged and / or accepted and pending UE mobility procedure, e.g., Handover Preparation procedure, may later be canceled depending on the priority level, the type of resource allocation, the preemption vulnerability, the retention priority, etc., given that one or more of these attributes is comprised in the initiating message of the procedure, e.g., due to a resource shortage.

[0141] In one embodiment, when one of these attributes in the HANDOVER REQUEST message, the second radio network node 13 may consider this information while continuously monitoring the resource capacity, utilization / allocation and / or availability at the second radio network node 13 as long as at least one handover is prepared but pending, i.e., not executed. If the second radio network node 13 experiences a shortage of resources during that time, the second radio network node 13 may decide to cancel one or more of the prepared but pending handovers depending on their priority level, their type of resource allocation, their preemption vulnerability, their retention priority, etc.

[0142] In a related embodiment, if the second radio network node 13 cancels such a handover due to one or more of: the priority level, the type of resource allocation, the preemption vulnerability, the retention priority, etc., the second radio network node 13 may indicate, e.g., in a handover cancel message, the reason for canceling the handover, e.g., too low priority level, too low priority level for hard resource allocation, or similar.

[0143] Other extensions and variations:

[0144] The HANDOVER REQUEST message mentioned in the embodiments above may be provided as an example carrying the indication, assuming Xn mobility as a common scenario where the embodiments may be applied. The methods of the solution may also apply to other procedures and / or scenarios, such as an NG handover, in a mobility procedure to add or change a Secondary Node, in a procedure to conditionally add or change a Secondary Node, in a procedure for L1 / L2-Triggered Mobility (LTM) mobility.

[0145] Examples of the indication as an extension of the HANDOVER REQUEST Xn message, are given below:

[0146] 9.1.1.1 HANDOVER REQUEST

[0147] This message is sent by the source NG-RAN node to the target NG-RAN node to request the preparation of resources for a handover. Added lEs are underlined, bold and italic and one or more of the added lEs may be used as the indication to the second radio network node 13.

[0148] Direction: source NG-RAN node target NG-RAN node.

[0149] Fig. 7 is a block diagram depicting the first radio network node 12 for handling communication of the UEs in the communication network 1 according to embodiments herein.

[0150] The first radio network node 12 may comprise processing circuitry 901 , e.g. one or more processors, configured to perform the methods herein.

[0151] The first radio network node 12 and / or the processing circuitry 901 is configured to transmit the indication to the second radio network node 13. The indication indicates the one or more of the following: the probability of the mobility procedure for the UE 10 being carried out; the type of resource allocation required at the second radio network node 13 for the UE 10; the preemption vulnerability or capability; the retention priority; that the mobility procedure is a delayed mobility procedure; the reason of the mobility procedure; and / or the priority of the mobility procedure for the UE 10. The indication may further indicate that a previously received UE mobility procedure needs to be updated, and / or that no actual mobility event is being attempted for the UE 10, but rather measurements and / or predictions are being requested. The indication may indicate the energy consumption to be derived at the second radio network node 13, and / or comprise the numerical value. The indication may comprise the IE which indicates the reason and / or the priority. The reason may be one out of:

[0152] - a radio coverage reason,

[0153] - an energy saving reason,

[0154] - a SLA fulfillment reason,

[0155] - a radio coverage reason and an energy saving reason, and / or

[0156] - a radio coverage reason and an SLA fulfillment reason.

[0157] The priority may be one out of:

[0158] - a numerical index, or

[0159] - an enumerated type, with one or more values.

[0160] The first radio network node 12 and / or the processing circuitry 901 may be configured to determine the indication of the mobility procedure.

[0161] The first radio network node 12 may comprise a memory 905. The memory 905 comprises one or more units to be used to store data on, such as data packets, indications, messages, UE context, messages, information, events and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the first radio network node 12 may comprise a communication interface 906 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.

[0162] The methods according to the embodiments described herein for the first radio network node 12 are respectively implemented by means of e.g. a computer program product 907 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the first radio network node 12. The computer program product 907 may be stored on a computer-readable storage medium 908, e g., a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 908, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the first radio network node 12. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose the first radio network node 12 for handling communication of UEs in a communication network, wherein the first radio network node 12 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said first radio network node 12 is operative to perform any of the methods herein.

[0163] Fig. 8 is a block diagram depicting the second radio network node 13 for handling communication of the UEs in the communication network 1 according to embodiments herein. The second radio network node 13 may comprise processing circuitry 1001 , e.g., one or more processors, configured to perform the methods herein.

[0164] The second radio network node 13 and / or the processing circuitry 1001 is configured to receive the indication from the first radio network node 12. The indication indicates one or more of the following: the probability of the mobility procedure for the UE 10 being carried out; the type of resource allocation required at the second radio network node 13 for the UE 10; the preemption vulnerability or capability; the retention priority; that the mobility procedure is a delayed mobility procedure; the reason of the mobility procedure; and / or the priority of the mobility procedure for the UE 10. The indication may comprise a numerical value.

[0165] The second radio network node 13 and / or the processing circuitry 1001 is configured to perform the action related to the mobility procedure of the UE 10 taking the indication into account, such as perform a mobility procedure taking the indication into account. The action may comprise admitting or not admitting the mobility procedure of the UE 10 based on the indication. The indication may be comprised in the HANDOVER REQUEST message indicating that the mobility procedure is a delayed mobility procedure and the action may comprise sending the HANDOVER REQUEST ACKNOWLEDGE message indicating that the HANDOVER REQUEST message is accepted and / or the amount of wait time for the delayed mobility procedure. The action may comprise comparing the mobility procedure of the UE 10 with one or more other incoming mobility procedures and deducing how to prioritize the mobility procedures over one another. The action may comprise allocating resources based on the indication, and / or the action may comprise deriving, based on the indication, the energy consumption at the second radio network node 13.

[0166] The second radio network node 13 may comprise a memory 1005. The memory 1005 comprises one or more units to be used to store data on, such as data packets, indications, messages, UE context, messages, information, events and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the second radio network node 13 may comprise a communication interface 1006 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.

[0167] The methods according to the embodiments described herein for the second radio network node 13 are respectively implemented by means of e.g. a computer program product 1007 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the second radio network node 13. The computer program product 1007 may be stored on a computer-readable storage medium 1008, e.g., a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 1008, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the second radio network node 13. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose the second radio network node 13 for handling communication of UEs in a communication network, wherein the second radio network node 13 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said second radio network node 13 is operative to perform any of the methods herein.

[0168] In some embodiments a more general term “network node” or “radio network node” is used and it can correspond to any type of radio-network node or any network node, which communicates with a UE and / or with another network node.

[0169] In some embodiments the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating with a network node and / or with another wireless device in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, proximity capable UE (aka ProSe UE), loT capable device, machine type UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.

[0170] Embodiments are applicable to any RAT or multi-RAT systems, where the wireless device receives and / or transmit signals (e.g. data) e.g. NR, Wi-Fi, LTE, LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

[0171] As will be readily understood by those familiar with communications design, that functions means or circuits may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example.

[0172] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware and / or program or application data. Other hardware, conventional and / or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0173] 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.

[0174] Fig. 9 shows an example of a communication system 15100 in accordance with some embodiments.

[0175] In the example, the communication system 15100 includes a telecommunication network 15102 that includes an access network 15104, such as a radio access network (RAN), and a core network 15106, which includes one or more core network nodes 15108. The access network 15104 includes one or more access network nodes, such as network nodes 15110a and 15110b (one or more of which may be generally referred to as network nodes 15110), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 15102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 15102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 15102, including one or more network nodes 15110 and / or core network nodes 15108.

[0176] Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (0-Dll), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1, E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 15110, such as the first radio network node 12 or the second radio network node 13, facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 15112a, 15112b, 15112c, and 15112d (one or more of which may be generally referred to as UEs 15112 or UE 10) to the core network 15106 over one or more wireless connections.

[0177] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 15100 may include any number of wired or wireless networks, network nodes, UEs, 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. The communication system 15100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0178] The UEs 15112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 15110 and other communication devices. Similarly, the network nodes 15110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 15112 and / or with other network nodes or equipment in the telecommunication network 15102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 15102.

[0179] In the depicted example, the core network 15106 connects the network nodes 15110 to one or more host computing systems, such as host 15116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 15106 includes one more core network nodes (e.g., core network node 15108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 15108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De- concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0180] The host 15116 may be under the ownership or control of a service provider other than an operator or provider of the access network 15104 and / or the telecommunication network 15102. The host 15116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0181] As a whole, the communication system 15100 of Figure 9 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0182] In some examples, the telecommunication network 15102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 15102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 15102. For example, the telecommunications network 15102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0183] In some examples, the UEs 15112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 15104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 15104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC). In the example, the hub 15114 communicates with the access network 15104 to facilitate indirect communication between one or more UEs (e.g., UE 15112c and / or 15112d) and network nodes (e.g., network node 15110b). In some examples, the hub 15114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 15114 may be a broadband router enabling access to the core network 15106 for the UEs. As another example, the hub 15114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 15110, or by executable code, script, process, or other instructions in the hub 15114. As another example, the hub 15114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 15114 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 15114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 15114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 15114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0184] The hub 15114 may have a constant / persistent or intermittent connection to the network node 15110b. The hub 15114 may also allow for a different communication scheme and / or schedule between the hub 15114 and UEs (e.g., UE 15112c and / or 15112d), and between the hub 15114 and the core network 15106. In other examples, the hub 15114 is connected to the core network 15106 and / or one or more UEs via a wired connection. Moreover, the hub 15114 may be configured to connect to an M2M service provider over the access network 15104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 15110 while still connected via the hub 15114 via a wired or wireless connection. In some embodiments, the hub 15114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 15110b. In other embodiments, the hub 15114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 15110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0185] Fig. 10 shows a UE 15300 in accordance with some embodiments. The UE 15300 presents additional details of some embodiments of the UE 15112 of Figure 9. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0186] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a 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).

[0187] The UE 15300 includes processing circuitry 15302 that is operatively coupled via a bus 15304 to an input / output interface 15306, a power source 15308, a memory 15310, a communication interface 15312, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Fig. 10. 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.

[0188] The processing circuitry 15302 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 15310. The processing circuitry 15302 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, 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 15302 may include multiple central processing units (CPUs).

[0189] In the example, the input / output interface 15306 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include 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. An input device may allow a user to capture information into the UE 15300. Examples of an input device 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, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0190] In some embodiments, the power source 15308 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 15308 may further include power circuitry for delivering power from the power source 15308 itself, and / or an external power source, to the various parts of the UE 15300 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 15308. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 15308 to make the power suitable for the respective components of the UE 15300 to which power is supplied.

[0191] The memory 15310 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 15310 includes one or more application programs 15314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 15316. The memory 15310 may store, for use by the UE 15300, any of a variety of various operating systems or combinations of operating systems.

[0192] The memory 15310 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), 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 micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 15310 may allow the UE 15300 to access instructions, application programs and 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 as or in the memory 15310, which may be or comprise a device-readable storage medium.

[0193] The processing circuitry 15302 may be configured to communicate with an access network or other network using the communication interface 15312. The communication interface 15312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 15322. The communication interface 15312 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 15318 and / or a receiver 15320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 15318 and receiver 15320 may be coupled to one or more antennas (e.g., antenna 15322) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0194] In the illustrated embodiment, communication functions of the communication interface 15312 may include cellular communication, Wi-Fi communication, LPWAN communication, 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. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0195] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 15312, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0196] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input. A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 15300 shown in Fig. 10.

[0197] As yet another specific example, in an loT scenario, a UE 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 UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0198] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0199] Fig. 11 shows a network node 15400 in accordance with some embodiments, such as the first radio network node 12 or the second radio network node 13. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication 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)), O-RAN nodes or components of an O-RAN node (e.g., 0-Rll, O- DU, O-CU).

[0200] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may 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, distributed units (e.g., in an O-RAN access node) 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).

[0201] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, 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), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, SelfOrganizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0202] The network node 15400 includes a processing circuitry 15402, a memory 15404, a communication interface 15406, and a power source 15408. The network node 15400 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 the network node 15400 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 NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 15400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 15404 for different RATs) and some components may be reused (e.g., a same antenna 15410 may be shared by different RATs). The network node 15400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 15400, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) 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 15400. The processing circuitry 15402 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 15400 components, such as the memory 15404, to provide network node 15400 functionality.

[0203] In some embodiments, the processing circuitry 15402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 15402 includes one or more of radio frequency (RF) transceiver circuitry 15412 and baseband processing circuitry 15414. In some embodiments, the radio frequency (RF) transceiver circuitry 15412 and the baseband processing circuitry 15414 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 15412 and baseband processing circuitry 15414 may be on the same chip or set of chips, boards, or units.

[0204] The memory 15404 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 nonvolatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 15402. The memory 15404 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 15402 and utilized by the network node 15400. The memory 15404 may be used to store any calculations made by the processing circuitry 15402 and / or any data received via the communication interface 15406. In some embodiments, the processing circuitry 15402 and memory 15404 is integrated.

[0205] The communication interface 15406 is used in wired or wireless communication of signalling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 15406 comprises port(s) / terminal(s) 15416 to send and receive data, for example to and from a network over a wired connection. The communication interface 15406 also includes radio front-end circuitry 15418 that may be coupled to, or in certain embodiments a part of, the antenna 15410. Radio front-end circuitry 15418 comprises filters 15420 and amplifiers 15422. The radio front-end circuitry 15418 may be connected to an antenna 15410 and processing circuitry 15402. The radio front-end circuitry may be configured to condition signals communicated between antenna 15410 and processing circuitry 15402. The radio front-end circuitry 15418 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 15418 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 15420 and / or amplifiers 15422. The radio signal may then be transmitted via the antenna 15410. Similarly, when receiving data, the antenna 15410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 15418. The digital data may be passed to the processing circuitry 15402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0206] In certain alternative embodiments, the network node 15400 does not include separate radio front-end circuitry 15418, instead, the processing circuitry 15402 includes radio front-end circuitry and is connected to the antenna 15410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 15412 is part of the communication interface 15406. In still other embodiments, the communication interface 15406 includes one or more ports or terminals 15416, the radio front-end circuitry 15418, and the RF transceiver circuitry 15412, as part of a radio unit (not shown), and the communication interface 15406 communicates with the baseband processing circuitry 15414, which is part of a digital unit (not shown).

[0207] The antenna 15410 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 15410 may be coupled to the radio front-end circuitry 15418 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 15410 is separate from the network node 15400 and connectable to the network node 15400 through an interface or port.

[0208] The antenna 15410, communication interface 15406, and / or the processing circuitry 15402 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 15410, the communication interface 15406, and / or the processing circuitry 15402 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0209] The power source 15408 provides power to the various components of network node 15400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 15408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 15400 with power for performing the functionality described herein. For example, the network node 15400 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 15408. As a further example, the power source 15408 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0210] Embodiments of the network node 15400 may include additional components beyond those shown in Fig. 11 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, the network node 15400 may include user interface equipment to allow input of information into the network node 15400 and to allow output of information from the network node 15400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 15400. In some embodiments providing a core network node, such as core network node 15108 of Fig. 9, some components, such as the radio front-end circuitry 15418 and the RF transceiver circuitry 15412 may be omitted.

[0211] Fig. 12 is a block diagram illustrating a virtualization environment 15500 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 any device described herein, 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. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 15500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 15500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

[0212] Applications 15502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q500 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0213] Hardware 15504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 15506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 15508a and 15508b (one or more of which may be generally referred to as VMs 15508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 15506 may present a virtual operating platform that appears like networking hardware to the VMs 15508.

[0214] The VMs 15508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 15506. Different embodiments of the instance of a virtual appliance 15502 may be implemented on one or more of VMs 15508, and the implementations may be made in different ways. 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.

[0215] In the context of NFV, a VM 15508 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 the VMs 15508, and that part of hardware 15504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 15508 on top of the hardware 15504 and corresponds to the application 15502.

[0216] Hardware 15504 may be implemented in a standalone network node with generic or specific components. Hardware 15504 may implement some functions via virtualization. Alternatively, hardware 15504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 15510, which, among others, oversees lifecycle management of applications 15502. In some embodiments, hardware 15504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes 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. In some embodiments, some signalling can be provided with the use of a control system 15512 which may alternatively be used for communication between hardware nodes and radio units.

[0217] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information 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. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0218] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 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 non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0219] It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.

Claims

CLAIMS1. A method performed by a first radio network node (12) for handling communication of user equipments, UE (10), in a communication network (1), the method comprising transmitting (502) an indication to a second radio network node (13), wherein the indication indicates one or more of the following: a probability of a mobility procedure for a UE (10) being carried out; a type of resource allocation required at the second radio network node (13) for the UE (10); a preemption vulnerability or capability; a retention priority; that the mobility procedure is a delayed mobility procedure; a reason of the mobility procedure; and / or a priority of the mobility procedure for the UE (10).

2. The method according to claim 1, wherein the indication further indicates that a previously received UE mobility procedure needs to be updated, and / or that no actual mobility event is being attempted for the UE (10), but rather measurements and / or predictions are being requested.

3. The method according to any of the claims 1-2, wherein the indication comprises a numerical value and / or indicates an energy consumption to be derived at the second radio network node.

4. The method according to any of the claims 1-3, wherein the indication comprises an information element which indicates the reason and / or the priority, wherein the reason is one out of:- a radio coverage reason,- an energy saving reason,- a service level agreement, SLA, fulfillment reason,- a radio coverage reason and an energy saving reason, and / or- a radio coverage reason and an SLA fulfillment reason, and wherein the priority is one out of:- a numerical index, or- an enumerated type, with one or more values.

5. A method performed by a second radio network node (13) for handling communication of user equipments, UE, (10) in a communication network (1), the method comprising receiving (601) an indication from a first radio network node (12), wherein the indication indicates one or more of the following: a probability of a mobility procedure for a UE (10) being carried out; a type of resource allocation required at the second radio network node (13) for the UE (10); a preemption vulnerability or capability; a retentionpriority; that the mobility procedure is a delayed mobility procedure; a reason of the mobility procedure; and / or a priority of the mobility procedure for the UE (10); and- performing (602) an action related to the mobility procedure of the UE (10) taking the indication into account.

6. The method according to claim 5, wherein the action comprises admitting or not admitting the mobility procedure of the UE (10) based on the indication.

7. The method according to any of the claims 5-6, wherein the action comprises comparing the mobility procedure of the UE (10) with one or more other incoming mobility procedures and deducing how to prioritize the mobility procedures over one another.

8. The method according to any of the claims 5-7, wherein the action comprises allocating resources based on the indication.

9. The method according to any of the claims 5-8, wherein the indication is comprised in a HANDOVER REQUEST message indicating that the mobility procedure is a delayed mobility procedure, and the action comprises sending a HANDOVER REQUEST ACKNOWLEDGE message indicating that the HANDOVER REQUEST message is accepted and / or an amount of wait time for the delayed mobility procedure.

10. The method according to any of the claims 5-9, wherein the action comprises deriving, based on the indication, an energy consumption at the second radio network node (13).

11. A first radio network node (12) for handling communication of user equipments, UE, in a communication network (1), wherein the first radio network node (12) is configured to: transmit an indication to a second radio network node (13), wherein the indication indicates one or more of the following: a probability of a mobility procedure for a UE (10) being carried out; a type of resource allocation required at the second radio network node (13) for the UE (10); a preemption vulnerability or capability; a retention priority; that the mobility procedure is a delayed mobility procedure; a reason of the mobility procedure; and / or a priority of the mobility procedure for the UE (10).

12. The first radio network node (12) according to claim 11, wherein the indication further indicates that a previously received UE mobility procedure needs to be updated, and / or that no actual mobility event is being attempted for the UE (10), but rather measurements and / or predictions are being requested.

13. The first radio network node (12) according to any of the claims 11-12, wherein the indication indicates an energy consumption to be derived at the second radio network node (13), and / or comprises a numerical value.

14. The first radio network node (12) according to any of the claims 11-13, wherein the indication comprises an information element which indicates the reason and / or the priority, wherein the reason is one out of:- a radio coverage reason,- an energy saving reason,- a service level agreement, SLA, fulfillment reason,- a radio coverage reason and an energy saving reason, and / or- a radio coverage reason and an SLA fulfillment reason, and wherein the priority is one out of:- a numerical index, or- an enumerated type, with one or more values.

15. A second radio network node (13) for handling communication of user equipments, UE, (10) in a communication network (1), wherein the second radio network node (13) is configured to: receive an indication from a first radio network node (12), wherein the indication indicates one or more of the following: a probability of a mobility procedure for a UE (10) being carried out; a type of resource allocation required at the second radio network node (13) for the UE (10); a preemption vulnerability or capability; a retention priority; that the mobility procedure is a delayed mobility procedure; a reason of the mobility procedure; and / or a priority of the mobility procedure for the UE (10); and perform an action related to the mobility procedure of the UE (10) taking the indication into account.

16. The second radio network node (13) according to claim 15, wherein the action comprises admitting or not admitting the mobility procedure of the UE (10) based on the indication.

17. The second radio network node (13) according to any of the claims 15-16, wherein the action comprises comparing the mobility procedure of the UE (10) with one or more other incoming mobility procedures and deducing how to prioritize the mobility procedures over one another.

18. The second radio network node (13) according to any of the claims 15-17, wherein the action comprises allocating resources based on the indication.

19. The second radio network node (13) according to any of the claims 15-18, wherein the indication is comprised in a HANDOVER REQUEST message indicating that the mobility procedure is a delayed mobility procedure, and the action comprises sending a HANDOVER REQUEST ACKNOWLEDGE message indicating that the HANDOVER REQUEST message is accepted and / or an amount of wait time for the delayed mobility procedure.

20. The second radio network node (13) according to any of the claims 15-19, wherein the action comprises deriving, based on the indication, an energy consumption at the second radio network node (13).

21. A computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-10, as performed by the first radio network node (12) and the second radio network node (13), respectively.

22. A computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-10, as performed by the first radio network node (12) and the second radio network node (13), respectively.

Images