First user equipment, first source network node, network node and methods in a wireless communucation network

Abstract

A method performed by a first source network node for handling handover for a first User Equipment, UE, in a wireless communication network is provided. The first source network node determines (602) a handover timing condition for the first UE. The first UE is comprised in a wireless device further comprising a second UE. The handover timing condition enables handovers with disjoint handover interruption times for the first UE and the second UE. The first source network node sends (603) the handover timing condition to the first UE.

Description

[0001] FIRST USER EQUIPMENT, FIRST SOURCE NETWORK NODE, NETWORK

[0002] NODE AND METHODS IN A WIRELESS COMMUNUCATION NETWORK

[0003] TECHNICAL FIELD

[0004] Embodiments herein relate to a first source network node, a first user equipment, a network node and methods therein. In some aspects, they relate to handling handover in a wireless communication network.

[0005] BACKGROUND

[0006] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point, a Base Station (BS) or a radio base station (RBS), which in some networks may also be denoted, for example, a Base Station (BS), a NodeB, eNodeB (eNB), or gNodeB (gNB) as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on a radio frequency with the wireless devices within the range of the radio network node.

[0007] 3rd Generation Partnership Project (3GPP) is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E- UTRA) and Evolved Packet System (EPS) have been completed within the 3GPP. In 4G also called a Fourth Generation (4G) network, EPS is core network and E-UTRA is radio access network. In 5G, 5GC is core network, NR is radio access network. As a continued network evolution, the new release of 3GPP specifies a 5G network also referred to as 5G New Radio (NR) and 5G Core (5GC).

[0008] Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

[0009] Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a base station (BS), the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. The cell capacity can be increased linearly with respect to the number of antennas at the BS side. Due to that, more and more antennas are employed in BS. Such systems and / or related techniques are commonly referred to as massive MIMO.

[0010] The next generation networks, or 5G, architecture is defined by 3GPP. Figure 1 depicts a 5G reference architecture as described in 3GPP TS 23.501 v18.5.0, some of which are described below.

[0011] UE: The mobile terminal receiving network services.

[0012] RAN: Part of the network that connects to the UE via a certain radio technology and interconnects it to the ON.

[0013] Access and Mobility Management Function (AMF): The AMF manages the registration, connection and mobility management between the network and UE. It also mediates communication between the UE and SMF.

[0014] Session Management Function (SMF): The SMF is responsible for session establishment, modification and release, including selection and control of the User Plane Function (UPF) entities, maintaining the topology of the involved Packet Data Unit (PDU) Session Achor (PSA) UPFs, establishing and releasing the tunnel between Application Networks (AN) and UPF and between UPFs. It also configures traffic forwarding at UPF. SMF interacts with the UPF over N4 Reference point using Packet Forwarding Function Protocol (PFCP) procedures.

[0015] User Plane Function (UPF): the UPF handles the user data traffic. Among other, it provides the external Packet Data Units (PDU) Session point of interconnect to Data Network, such as PSA, and performs packet routing and forwarding, e.g., support of Uplink classifier (UL CL) to route traffic flows to an instance of a data network, support of Branching point to support multi-homed PDU Session.

[0016] Handover

[0017] Mobility in connected mode - which is used when a mobile terminal, such as UE, is active - is controlled by the network, assisted by the mobile terminal. The handover decision is made based on the measurements by the mobile terminal if the cellular link to the serving cell is getting degraded and / or another neighboring cell in the same frequency is getting better than the serving cell.

[0018] Based on these measurement reports provided by the mobile terminal to the RAN node, the network may possibly move, i.e. , hand over, the mobile terminal connection from the serving cell to that neighbor cell, so the mobile terminal will get better radio conditions and consequently a better user experience.

[0019] The handover preparation and execution phases in RAN are performed as specified in 3GPP TS 38.300 v18.5.0 clause 9.2.3, while the connected mode handover procedures are described in TS 23.502, clause 4.9. Herewith we give a brief description of the concept, illustrated in Figure 2; for the detailed description please refer to the above references:

[0020] 1. Handover from Source RAN to Target RAN. As part of the handover procedure, the Source RAN is configured to forward all downlink (DL) data received for the given UE PDU session(s) towards the Target RAN. The UL data is sent from the UE directly to the Target RAN, which sends it to the UPF using the UL tunnel identifier received from the Source RAN.

[0021] 2. The Target RAN issues a Path Switch Request to the AMF, targeting the SMF (in more generic terms, the control plane), with the aim to inform the AMF that the UE has moved to the Target RAN and so the PDU session(s) UP (i.e., the N3 tunnels to / from UPF) is to be switched. The request includes the AN tunnel info (i.e., tunnel identifiers for the DL traffic) for the PDU session to be switched.

[0022] 3. The request is forwarded by the AMF to the serving SMF. The SMF determines whether the existing UPF can continue to serve the UE. If the existing UPF(s) cannot continue to serve the UE, then intermediate UPF(s) (e.g., UPFs acting as UL CLs and local PSAs) may need to be selected and inserted via an N4 Session Establishment Request message; if yes, then the SMF sends an N4 Session Modification Request message to the UPF including the AN tunnel info.

[0023] 4. The UPF(s) returns an N4 Session Establishment / Modification Response message to the SMF after requested PDU Sessions are switched. Tunnel identifiers are provided for those PDU sessions that could be switched.

[0024] 5. In order to assist the reordering function in the Target RAN, the UPF sends one or more "end marker" packets for each N3 tunnel on the old path immediately after switching the path. The UPF starts sending downlink packets to the Target RAN

[0025] 6. SMF triggers (through the AMF) a Path Switch Request Ack message to Target RAN, including the list of PDU sessions that failed to be switched as well as the CN tunnel identifiers for the switched PDU sessions. Based on this, the Target RAN may switch the UL tunnel.

[0026] 7. By sending a Release Resources message to the Source RAN, the Target RAN confirms success of the handover. It then triggers the release of resources with the Source RAN.

[0027] Conditional handover

[0028] As part of 3GPP’s Release 16, ‘Conditional Handover’ is a new solution that aims to improve the mobility robustness of a mobile terminal. The main concept is depicted in Figure 3.

[0029] The conditional handover feature works as follows. The mobile terminal receives a handover command and stores it, e.g., an RRCReconfiguration message prepared by a target candidate as shown in Steps 2 and 3, without applying it as it would have done in legacy handover. Together with the command, the mobile terminal also receives in Step 3 an associated condition to be monitored. When the condition is fulfilled, the mobile terminal applies the previously stored handover command, as shown in Steps 5 and 6, as if the network would have just sent it, instead of first sending a measurement report, that could fail to be transmitted, and then waiting to receive the command, which may fail to be received.

[0030] Sending the handover command when the radio conditions are still favorable reduces the risk of failing the transmission of the measurement report and / or the reception of the handover command, thus it reduces the amount of mobility-related failures.

[0031] It is also possible in case of non-terrestrial networks (NTN) to specify a location or time-based trigger condition to execute the CHO, see e.g., 3GPP TS 38.300 v18.5.0 Section 16.14.3.2.2: “NTN supports the following additional trigger conditions upon which UE may execute CHO to a candidate cell, as defined in TS 38.331

[0012] :

[0032] The RRM measurement-based event A4;

[0033] A time-based trigger condition;

[0034] A location-based trigger condition.”

[0035] The main reason for this additional condition is to ensure minimal disruption when HO to a satellite RAN node.

[0036] Support for reliable communication with redundant user plane paths on multiple UEs per device

[0037] Figure 4 shows a reliability group-based redundancy concept in RAN. To support use cases that require high reliability, such as Time-Sensitive Network (TSN), Deterministic Network (DetNet), Ultra Relaible Low Latency Communication (URLLC), the mobile network could deploy redundant coverage with multiple gNBs and the end device could include two UEs. In this way it becomes possible to realize two disjoint user plane paths, using the reliability group concept as shown in Figure 3. More details can be found in 3GPP TS 23.501 v18.5.0, Annex F. Example of such terminal device is an industrial moving robotic device, which does not require high volume of data to be transmitted, on the other hand it is crucial for the device to always receive timely information, thus it is worth the additional UE and data transmission to send data to the robot over redundant paths.

[0038] SUMMARY

[0039] As a part of developing embodiments herein a problem was identified by the inventors and will first be discussed.

[0040] The current conditions to be fulfilled for HO command initiation by a UE towards the target RAN do in general not include any timing control, i.e., information on when the HO may be initiated, which would be beneficial in certain conditions. One such scenario is when the terminal device has multiple UEs to improve the reliability of the communication. Since the HO execution results in a short break of connectivity, also referred to as HO interruption time, it would be advantageous if only one of the UEs was executing the HO at a given time, while the other one is still operating without interruption, thus avoiding simultaneous interruption for both UEs. In a specific scenario, timing condition for conditional HO is specified for handovers to satellite-based RAN nodes, however, the current mechanism relies only on the information related to the timing conditions of the given satellite based RAN node and hence it cannot handle scenarios when the timing limitation is due to other reasons like a handover execution on a parallel, redundant path.

[0041] An object of embodiments herein is to improve the performance in a wireless communication network.

[0042] According to an aspect of embodiments herein, the object is achieved by a method performed by a first source network node for handling handover for a first User Equipment, UE, in a wireless communication network.

[0043] The first source network node determines a handover timing condition for the first UE. The first UE is comprised in a wireless device further comprising a second UE. The handover timing condition enables handovers with disjoint handover interruption times for the first UE and the second UE.

[0044] The first source network node sends the handover timing condition to the first UE.

[0045] According to an aspect of embodiments herein, the object is achieved by a method performed by a first User Equipment, UE, for handling handover in a wireless communication network. The first UE is comprised in a wireless device further comprising at least one second UE.

[0046] The first UE receives a handover timing condition from a first source network node. The handover timing condition configures to first UE to perform a handover with disjoint handover interruption time for the first UE and the at least one second UE comprised in the wireless device.

[0047] The first UE executes a handover based on the handover timing condition.

[0048] According to an aspect of embodiments herein, the object is achieved by a method performed by a network node for handling handover in a wireless communication network.

[0049] The network node determines a handover timing condition data for at two or more User Equipments, UE. The two or more UEs is comprised in a wireless device. The handover timing condition enables handovers with disjoint handover interruption times for the two or more UEs.

[0050] The network node sends, to two or more source network nodes, handover timing condition data related to the two or more UEs. According to an aspect of embodiments herein, the object is achieved by a first source network node configured to handle handover for a first User Equipment, UE, in a wireless communication network.

[0051] The first source network node is configured to determine a handover timing condition for the first UE. The first UE is configured to be comprised in a wireless device further being configured to be comprised a second UE. The handover timing condition is adapted to enable handovers with disjoint handover interruption times for the first UE and the second UE.

[0052] The first source network node is configured to send the handover timing condition to the first UE.

[0053] According to an aspect of embodiments herein, the object is achieved by a first User Equipment, UE, is configured to handle handover in a wireless communication network . The first UE is configured to be comprised in a wireless device further being configured to comprise at least one second UE.

[0054] The first UE is configured to receive a handover timing condition from a first source network node. The handover timing condition is adapted to configure to first UE to perform a handover with disjoint handover interruption time for the first UE and the at least one second UE comprised in the wireless device.

[0055] The first UE is configured to execute a handover based on the handover timing condition.

[0056] According to an aspect of embodiments herein, the object is achieved by a network node configured to handle handover in a wireless communication network.

[0057] The network node is configured to determine handover timing condition data related to two or more User Equipments, UE. The two or more UEs being comprised in a wireless device. The handover timing condition is adapted to enable handovers with disjoint handover interruption times for the two or more UEs.

[0058] The network node is configured to send, to two or more source network nodes, the handover timing condition data.

[0059] BRIEF DESCRIPTION OF THE DRAWINGS

[0060] Examples of embodiments herein are described in more detail with reference to attached drawings in which:

[0061] Figure 1 illustrates an example according to prior art. Figure 2 illustrates an example according to prior art.

[0062] Figure 3 illustrates an example according to prior art.

[0063] Figure 4 illustrates an example according to prior art.

[0064] Figure 5 is a schematic block diagram illustrating embodiments of a wireless communication network.

[0065] Figure 6 is a flowchart depicting embodiments of a method in a first source network node.

[0066] Figure 7 is a flowchart depicting embodiments of a method in a first UE.

[0067] Figure 8 is a flowchart depicting embodiments of a method in a network node.

[0068] Figure 9 illustrates an example according to embodiments herein.

[0069] Figure 10 illustrates an example according to embodiments herein.

[0070] Figure 11 illustrates an example according to embodiments herein.

[0071] Figure 12 illustrates an example according to embodiments herein.

[0072] Figure 13 illustrates an example according to embodiments herein.

[0073] Figure 14 illustrates an example according to embodiments herein.

[0074] Figure 15 illustrates an example according to embodiments herein.

[0075] Figure 16 is a schematic block diagram illustrating embodiments of a first source network node.

[0076] Figure 17 is a schematic block diagram illustrating embodiments of a first UE.

[0077] Figure 18 is a schematic block diagram illustrating embodiments of a network node.

[0078] Figure 19 shows an example of a communication system QQ100 in accordance with some embodiments.

[0079] Figure 20 shows a UE QQ200 in accordance with some embodiments.

[0080] Figure 21 shows a network node QQ300 in accordance with some embodiments.

[0081] Figure 22 is a block diagram illustrating a virtualization environment QQ400 in which functions implemented by some embodiments may be virtualized.

[0082] DETAILED DESCRIPTION

[0083] Embodiments herein relate to communication in wireless communication network.

[0084] Examples of embodiments herein, provide methods in a wireless communication network related to the Conditional Handover (CHO) Procedure for a terminal device equipped with multiple UEs. As part of the CHO execution, a source RAN node, such as a first network node, may determine a timing condition for CHO for at least one of the UEs of the terminal device based on information concerning the possible HO of the other UEs in the same device in order to avoid that the UE HO interruption time overlaps with that of the other UEs of the terminal device.

[0085] Further, the source RAN node may send to the UE, and optionally to a target RAN node, such as a target network node, the CHO timing condition in addition to the other conditions that may exist.

[0086] The UE may initiate the HO to the target RAN node such that the timing condition, besides other possible conditions, are met.

[0087] In some examples, the CHO timing condition may be determined in the source RAN node based on information from the target RAN node or from the CN, such as an AMF.

[0088] In some examples, the CHO timing condition may be based on pre-configuration in source RAN node.

[0089] In some examples, the CHO timing condition may also be configured in the network, e.g., in an UDM.

[0090] In some examples, the CHO timing condition may be of the form of a periodically repeated time interval.

[0091] In some examples, the UEs may provide an indication about the handover execution time and the time interval for the CHO timing condition is calculated based on this information.

[0092] In some examples, the CHO timing condition may be based on an indicator that is internal to the terminal device, e.g., a “Device HO lock”-indicator. The capability for such device internal indicator may be sent from the UEs to the RAN and / or CN.

[0093] In some examples, in case the CHO timing condition is sent from the source RAN node to the target RAN node, the target RAN node can verify if the condition was observed.

[0094] Examples of embodiments herein enables an improved performance in the wireless communication network e.g., by avoiding simultaneous handovers with overlapping service interruption times for devices equipped with multiple UEs, by which the reliability of the device communication may be increased.

[0095] Embodiments herein relate to wireless communication networks in general. Figure 5 is a schematic overview depicting a wireless communication network 100. The wireless communication network 100 comprises one or more RANs and one or more CNs. The wireless communication network 100 may use a number of different technologies, such as Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, 5G, New Radio (NR), 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. Embodiments herein relate to recent technology trends that are of particular interest in a 5G context, however, embodiments are also applicable in further development of the existing wireless communication systems such as e.g. WCDMA and LTE, or to future technologies such as 6G.

[0096] A number of network nodes operate in the wireless communication network 100 such as e g. a first source network node 111 and a second source network node 112. These nodes provide radio coverage in a number of cells which may also be referred to as a beam or a beam group of beams.

[0097] The first source network node 111 and second source network node 112 may be any of a NG-RAN node, a transmission and reception point e.g. a base station, a radio access network node such as a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), a gNB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a network controlled repeater or any other network unit capable of communicating with a wireless device within the service area served by the first source network node 111 and / or the second source network node 112 depending e.g. on the first radio access technology and terminology used. The first source network node 111 and / or the second source network node 112 may be referred to as a serving radio network node and communicates with a UE 121 and / or a UE 122 with Downlink (DL) transmissions to the UE 121 and / or UE 122 and Uplink (UL) transmissions from the UE 121 and / or UE 122.

[0098] In the wireless communication network 100, one or more wireless devices operate, such as e.g. a wireless device 120. The wireless device 120 may also be referred to as a, a device, an loT device, a mobile station, a non-access point (non-AP) STA, a STA, a user equipment and / or a wireless terminals, communicate via one or more Access Networks (AN), e.g. RAN, to one or more core networks (CN). It should be understood by the skilled in the art that “wireless device” is a non-limiting term which means any terminal, wireless communication terminal, user equipment, 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 communicating within a cell. The wireless device 120 may comprise a number of UEs, such as a first UE 121 and second UE 122. Thus, the wireless device 120 may comprise two UEs that may connect to the same or different source network nodes, such as any of the first source network node 111 and / or the second source network node 112.

[0099] The wireless communication network 100 further comprises network node 115. The network node 115 may e.g., comprise a User Data Repository (UDR) / User Data Management (UDM). The network node 115 may store and handle handover timing condition data related to the first UE 121 and / or the second UE 122.

[0100] The wireless communication network may further comprises a network node 116. The network node 116 may e.g., comprise a RAN server. The network node 116 may store and handle handover timing condition data related to the first UE 121 and / or the second UE 122.

[0101] Methods herein may be performed by the first source network node 1111 , the first UE 121 and the network node 115, 116. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in the cloud 190 as shown in Figure 5, may be used for performing or partly performing the methods herein.

[0102] The above-described problem is addressed in a number of embodiments, some of which may be seen as alternatives, while some may be used in combination.

[0103] Embodiments herein provide methods handling HO in the wireless communication network 100. A HO timing condition is determined. The HO timing condition is sent to the first UE 121 comprised in the wireless device 120. The wireless device 120 comprises the first UE 121 and the second UE 122. The first UE 121 executes a handover based on the HO timing condition. The HO timing condition provides non-overlapping HO interruption times of the first UE 121 and second UE 122 comprised in the wireless device 120.

[0104] A method according to embodiments will now be described from the view of the first source network node 111 together with Figure 6. Figure 6 shows example embodiments of a method performed by the first source network node 111 for handling handover for the first UE 121 in the wireless communication network 100. The below method may also be performed by the second source network node 112 for handling handover for the second UE 122 in the wireless communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 6.

[0105] Action 601

[0106] In some embodiments, the first source node 111 obtains handover timing condition data related to the first UE 121 and / or the second UE 122. The handover timing condition data may e.g., be received from the network node 115, 116, the second source network node 112, and / or the first UE 121. The handover timing condition data may e.g., comprise allowed handover times, a handover lock capability for the first UE 121, and / or handover execution time, such as maximum handover execution times, for the first UE 121 and / or the second UE 122. The allowed handover times may e.g., comprise a periodicity and allowed times, e.g., a time interval within a period, for the conditional handover.

[0107] Action 602

[0108] The first source network node 111 determines a handover timing condition for the first UE 121. The first UE 121 is comprised in the wireless device 120. The wireless device 120 further comprising the second UE 122. The handover timing condition enables handovers with disjoint handover interruption times for the first UE 121 and the second UE 122.

[0109] In some embodiments, the handover timing condition is determined based on the handover timing data. E.g., the first source network node 111 may determine that the handover timing condition comprises the allowed handover times comprised in the handover timing condition data. Alternatively, the first source network node 111 may determine that the handover timing condition comprises handover lock indication. Alternatively, the first source network node 111 may determine the handover timing condition by calculating the allowed handover times, such as a handover time interval, based on the maximum handover execution time. As mentioned above, in some embodiments, the handover timing condition comprises any one out of a handover time interval, or handover lock indication.

[0110] In some embodiments, the handover lock indication configures the first UE 121 to request a handover lock from the wireless device 120, such as e.g., a device layer in the wireless device 120, prior to initiating a handover. In other words, the handover lock indication may configure the first UE 121 to request a handover lock to be activated prior to executing a handover. This will prevent the second UE 122 to execute a handover while the handover lock is active, thus avoiding any service interruption time during the handover. In some embodiments, the handover time interval comprises a time interval the first UE 121 is allowed to initiate a handover. In other words, the first UE 121 will only be allowed to execute the handover during the indicated time interval. The second UE 122, which is configured with a different time interval, disjoint from the time interval associated with the first UE 121 , will not be allowed to execute a handover during the time interval associated with the first UE 121 , thus avoiding any service interruption time during the handover.

[0111] Action 603

[0112] The first source network node 111 sends the handover timing condition to the first UE 121. The handover timing condition may e.g., be sent in a conditional handover message.

[0113] A method according to embodiments will now be described from the view of the first UE 121 together with Figure 7. Figure 7 shows example embodiments of a method performed by the first UE 121 for handling handover for the first UE 121 in the wireless communication network 100. The below method may also be performed by the second source UE 122 for handling handover for the second UE 122 in the wireless communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 7.

[0114] Action 701

[0115] In some embodiments, the first UE 121 sends, to any one out of the network node 115 or the first source network node 111 , a handover execution time, such as maximum handover execution time, for the first UE 121. When the handover execution time is sent to the network node 115, the UE 121 may send the handover execution time via the first source network node 111.

[0116] Action 702

[0117] The first UE 121 receives a handover timing condition from the first source network node 111. Handover timing condition configures to first UE 121 to perform a handover with disjoint handover interruption time for the first UE 121 and the at least one second UE 122 comprised in the wireless device 120. in some embodiments, the handover timing condition comprises any one out of a handover time interval, or handover lock indication.

[0118] In some embodiments, the handover lock indication configures the first UE 121 to request a handover lock from the wireless device 120, such as e.g., a device layer in the wireless device 120, prior to initiating a handover. In other words, the handover lock indication may configure the first UE 121 to request a handover lock to be activated prior to executing a handover. This will prevent the second UE 122 to execute a handover while the handover lock is active, thus avoiding any service interruption time during the handover.

[0119] In some embodiments, the handover time interval comprises a time interval the first UE 121 is allowed to initiate a handover. In other words, the first UE 121 will only be allowed to execute the handover during the indicated time interval. The second UE 122, which is configured with a different time interval, disjoint from the time interval associated with the first UE 121 , will not be allowed to execute a handover during the time interval associated with the first UE 121 , thus avoiding any service interruption time during the handover.

[0120] Action 703

[0121] The first UE 121 executes a handover based on the handover timing condition.

[0122] In some embodiments, executing the handover comprises executing the handover within the handover time interval. Thus, unless the within the time interval, the first UE 121 is prevented from executing the handover. In other words, upon deciding to execute the handover, the first UE 121 determines whether handover timing condition is fulfilled, i.e. , it is within the time interval, before executing the handover.

[0123] In some embodiments, executing the handover comprises sending, to the wireless device 120, such as a device layer in the wireless device, a handover lock request. The handover lock request requests the wireless device 120 to lock handover for any other UEs in the wireless device 120, in order for the first UE 121 to execute the handover without any service interruption.

[0124] In some embodiments, executing the handover further comprises receiving a positive handover lock acknowledgement from the wireless device 120, initiating the handover execution, and sending, to the device layer in the wireless device 120, a handover lock release message upon completion of the handover. This may e.g., mean that the first UE 121 initiates the handover execution, such as starting the handover process, responsive to the receiving the positive handover lock acknowledgement. When the first UE 121 has been handed over, such as when connection between the first UE 121 and the first source network node 111 is released, the first UE 121 sends the handover lock release message to the wireless device 120. This allows the wireless device 120 to allow the second UE 122 to perform a handover process. In some embodiments, executing the handover further comprises receiving a negative handover lock acknowledgement from the wireless device 120, and refraining from initiating the handover execution until a positive acknowledgment is received.

[0125] This may e.g., mean that the first UE 121 refrains from initiating the handover execution, such as starting the handover process, responsive to the receiving the negative handover lock acknowledgement. The first UE 121 may monitor for a positive handover lock acknowledgement. When the first UE 121 receives a positive handover lock acknowledgement, the first UE 121 initiates the handover execution, such as starting the handover process. When the first UE 121 has been handed over, such as when connection between the first UE 121 and the first source network node 111 is released, the first UE 121 sends the handover lock release message to the wireless device 120.

[0126] A method according to embodiments will now be described from the view of the network node 115 together with Figure 8. Figure 8 shows example embodiments of a method performed by the network node 115 for handling handover in the wireless communication network 100. The network node 115, 116 may e.g., comprise any one out of the user data management node 115 or the RAN server 116. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 8.

[0127] Action 801

[0128] In some embodiments, the network node 115 obtains any one out or more out of handover execution times related to the two or more UEs 121 , 122, and handover lock capabilities related to the two or more UEs 121, 122.

[0129] Action 802

[0130] In some embodiments, the network node 115 determines the handover timing condition data based on any one out of handover execution times related to the two or more UEs 121, 122, or handover lock capabilities related to the two or more UEs 121, 122.

[0131] In some embodiments, the handover timing condition data comprises any one out of handover execution times, a handover time interval, or handover lock capability.

[0132] In other words, determining the handover timing condition data may e.g., comprise determining the handover execution times, the handover time interval, or the handover lock capability for the two or more UEs 121 , 122. The handover execution time may e.g., be determined based on the obtained handover execution times for the two or more UEs 121, 122, i.e. , the handover execution time comprised in the handover timing condition data comprises the obtained handover execution times for the two or more UEs 121, 122.

[0133] The handover time interval may e.g., be determined based on the obtained handover execution times for the two or more UEs 121 , 122. This may e.g., comprise calculating allowed handover times, such as the handover time interval, based on the handover execution time, such as a maximum handover execution time.

[0134] The handover lock capability may e.g., be determined based on the obtained handover lock capabilities for the two or more UEs 121 , 122, i.e., the handover lock capabilities comprised in the handover condition timing data comprises the obtained handover lock capabilities for the two or more UEs 121 , 122. The handover lock capability may e.g., indicate that the two or more UEs 121 , 122 supports the handover lock capability.

[0135] In some embodiments, the handover lock capability indicates that the two or more UEs (121, 122) supports being configured to request a handover lock from the wireless device (120) prior to initiating a handover.

[0136] In some embodiments, the handover time interval comprises a respective time interval the two or more UEs 121 , 122 are allowed to initiate a handover.

[0137] In some embodiments, the handover execution time indicates a respective maximum handover execution times for the two or more UEs 121 , 122.

[0138] Action 803

[0139] The network node 115 sends, to the two or more source network nodes 111 , 112, handover timing condition data related to the two or more UEs 121 , 122. The two or more UEs 121 , 122 is comprised in the wireless device 120. The handover timing enables handovers with disjoint handover interruption times for the two or more UEs 121 , 122. The two or more UEs 121, 122 may e.g., comprises the first UE 121 and the second UE 122.

[0140] Embodiments herein such as the embodiments mentioned above will now be further described and exemplified. The text below is applicable to embodiments herein and may be combined with any suitable embodiment described above.

[0141] Figure 9 shows a combined signaling diagram and flowchart according to embodiments herein. Examples of embodiments impacts S93-S95 in Figure 9. S93: The CHO timing condition is sent by the source network node 111 to the first UE 121. The CHO timing condition may e.g., be pre-configured or received from the network node 115. If the CHO timing condition is received by the source network node 110 from the network node 115, 116, it may also include an indication, such as a flag, related to the capability of the first UE 121 to support the CHO with timing condition.

[0142] The CHO timing condition may e.g., comprise the any one or more out the following attributes:

[0143] - T1 : The start time when the UE may perform the HO.

[0144] - T2: The end time until the UE may perform the HO. That is, that HO may be performed in the time interval T2-T1.

[0145] - AT: The time interval until the next start time, e.g., as explained further in relation to Figure 10, for the first UE 121 to perform the HO, i.e., the period time.

[0146] - N: the number of repetitions of the period until the current condition is valid.

[0147] S94: The first UE 121 may monitor the CHO timing condition, in addition to other potential HO conditions.

[0148] S95: The first UE 121 executes the HO when the CHO timing condition, in addition to any further HO conditions, is met.

[0149] The CHO timing conditions may, for example, be pre-defined parts of a certain time interval. For example, it may be defined from the Nth to the Mth millisecond of every 1 second interval.

[0150] In the case of multiple UEs per device, for every UE the time allowed for HO execution may be defined as disjoint time periods of a certain time interval. An example for two UEs per device is shown in Figure 10. Here, each UE, such as the first UE 121 and the second UE 122, has a HO execution time within each time interval AT which is disjoint from that of the other, and also takes into account the maximum execution time, such as the maximum HO interruption time, for each of the UEs. This may be known by the network if the UEs signal specific value e.g., at registration. Another alternative would be that the network uses a pre-configured value for the maximum HO interruption time. Yet another alternative is that the network continuously measures the UE HO interruption times and set the allowed HO times accordingly.

[0151] Figure 11 shows an exemplary realization of the 3GPP architecture according to examples of embodiments herein. In this example, the first UE 121 and the second UE 122 provide information about the handover execution times, as well as the capability for conditional handover with allowed handover time indication to the network node 115. This set of information is forwarded via RAN nodes, such as the source first network node 111 and the second source network node 112, to respective AMFs, such as the mobility functions 131, 132, and stored in a User Data Repository (UDR), such as the network node 115. Alternatively, it may be possible to use a different network function for such coordination, as a common SMF or common AMF or common PCF or common TSCTSF or any other common node. Once the network node 115 has collected the information, based on operator configuration, the network node 115, or another network function, may determine the periodicity and the allowed handover times for first UE 121 and the second UE 122 within the period. Subject to operator policies, which may be realized in the network node 115 or AMF 131 , 132, or in other network functions, the network node 115 provides the information via the AMF 131, 132 to the respective source network nodes 111 ,112. When triggering the conditional handover, the source nodes 111,112 provides the allowed handover times, such as the HO timing condition, which may comprise periodicity as well as allowed times within the period, to the first UE 121 and the second UE 122. In that way, even if the handover signaling takes place at the same, or at least almost the same, time for the first UE 121 and the second UE 122, the handovers will not be simultaneous because the allowed handover times are disjoint, and there is sufficient guard time between the disjoint allowed times to take care of the handover execution.

[0152] In case the UEs do not provide an indication about the handover execution time, such information may also be configured in the network, e.g., in the network node 115. Or alternatively it is possible that the allowed handover times are pre-configured in the network in the AMF 131 , 132 or in the source nodes 111 , 112. Then there is no need for the network node 115 to coordinate them. UEs in different reliability groups may have different, disjoint allowed handover times, using pre-configured periods and allowed times within the period.

[0153] Figure 12 shows an example of embodiments herein. In this example the network node 116 may be referred to as a central RAN configuration server 116, or just a RAN server 116. The network node 116 may be deployed for other purposes as well. The network node 116 obtains information about the UE capabilities, and the, optionally, the maximum handover execution times for the first UE 121 and the second UE 122. Based on the obtained information, the network node 116 may provide the allowed handover times to the respective RAN nodes, such as the first source network node 111 and the second source network node 112. Based on this, the source network nodes 111 , 112 send the respective conditional handover message to the UEs. In this example, the signaling between the respective UEs 121 , 122 and source network nodes 111, 112 may carry the respective identifiers which identify the UE as well as the device in which the UE is situated. The identifiers are provided to the RAN server 115. Additionally, and optionally, indications about the UE capabilities for the CHO and max handover execution time may also be provided, or alternatively configured into the source network nodes 111, 112 or in the network node 116.

[0154] Figure 13 shows an example of embodiments herein. In this example, the RAN nodes 1111, 112, such as the first source network node 111 and the second source network node 112, obtains the information about the UE capabilities and, optionally, handover execution time and the corresponding identities, and forward the information received from the UEs, such as the first UE 121 and the second UE 122, to all other neighboring RAN nodes that may serve a UE that is in the same device, i.e. , under the same coverage area. It may be configured within the source network nodes 111 , 112 which other RAN nodes to inform. In this way, all RAN nodes can collect the information about the UEs in the same device, and perform the same calculation to determine the allowed handover times. In this case, all RAN nodes have to perform the same calculation based on the same input except that the RAN nodes may be in different reliability groups and hence can differentiate the first and second UE and provide the appropriate allowed HO start times.

[0155] Figure 14 shows an example of embodiments herein. In this example, there is an Application Programming Interface (API) between the UEs, such as the first UE 121 and the second UE 122, and a device layer, in the wireless device 120, to request a HO lock for the other UEs of the same device when a given UE, such as the first UE 121 , executes a HO. In this case, a HO coordination avoiding simultaneous HO is possible within the device, and thus the timing condition set by the network may comprise a “Device handover lock” indication towards the UEs 121, 122, along with any other conditions for CHO, for the UEs where this coordination is required. The network node 115 may indicate to the source network nodes 111 , 112 the support for the handover lock capability of the UEs 121 , 122. Note that in this option, if the AMF 131 , 132 sends the CHO timing information to the RAN nodes, such as the source network nodes 111 , 112, then this information will also comprise the same “Device handover lock” indication and / or flag. This option also lends itself well to a RAN-only realization option which does not impact the core network. In this case, an indication about the terminal support for the feature can be provided over RAN signaling to the source network nodes 111, 112, e.g., by the network node 116, without impacting the core network. Figure 15 shows an example according to examples of embodiments herein. The UEs 121, 122, such as the first UE 121 and the second UE 122, indicate their capability for device HO lock mechanism to the network; this may be stored e.g., in the UDM, such as the network node 115. If the UEs 121, 122 indicate the capability for “Device HO lock” in a device, such as the wireless device 120, that is equipped with multiple UEs, and operator policies allow the function to be used in the given network, e.g., configured in the UDM or in the AMF or other network functions. The core network, e.g., via the AMF 131, 132, indicates to the RAN nodes, such as the source network nodes 111 , 112, that the conditional handover is to be used in combination with the device HO lock. This gives an indication to the UEs 121, 122 that the handover cannot be started while another UE in the same device is executing a handover. To realize this, a logical device layer in the wireless device 120 realizes a locking mechanism, which locks the device for additional handovers when one handover is in progress.

[0156] When a UE, such as the first UE 121, gets a conditional handover message, such as an RRC message, from a RAN node, such as the first source network node 111 , with the device handover lock condition, the first UE 121 asks for a device handover lock from the device layer in the wireless device 120. If there is no other handover in progress, the lock is granted and the handover may proceed provided all other conditions are met. If another handover is already in progress, the lock is not granted, and the UE will be notified when the other handover has finished, so that the handover can take place. The lock is released once the handover is completed.

[0157] S151 : The first UE 121 indicate its capability for device HO lock, which is stored in the network node 115.

[0158] S152: The second UE 122 indicate its capability for device HO lock, which is stored in the network node 115.

[0159] S153: Based on the indications, it is determined that the device HO lock capability is available. Subject to operator policies that may be set in the UDM or in the AMF or in other network functions, such as the network node 115, it is signaled to the first source network node 111 , that the device HO lock mechanism can be used.

[0160] S154: Based on the indications, it is determined that the device HO lock capability is available. Subject to operator policies that may be set in the UDM or in the AMF or in other network functions, such as the network node 115, it is signaled to the second source network node 112, that the device HO lock mechanism can be used. S155: A conditional handover is triggered for first UE 121. The CHO is sent to the first UE 121 form the first source network node 111. The CHO comprises an indication to use the device HO lock function.

[0161] S156: The first UE 121 requests for a HO lock from the Device Layer in the wireless device 120.

[0162] S157: The device layer in the wireless device 120 grants the request since no other handover is currently ongoing.

[0163] S158: A conditional handover is triggered for second UE 122. The CHO is sent to the second UE 122 form the second source node 111. The CHO comprises an indication to use the device HO lock function.

[0164] S159: The second UE 122 requests for a HO lock from the Device Layer in the wireless device 120.

[0165] S1510: The device layer in the wireless device 120 is not granted since a handover is in progress.

[0166] S1511: The first UE 121 executes the HO.

[0167] S1512: The first UE 121 releases the HO lock once it the HO complete by sending a release HO lock message to the device layer in the wireless device 120.

[0168] S1513: The device layer grants the handover lock for the second UE 122.

[0169] S1514: The second UE 122 executes the HO. which can then execute the handover, and then release the lock.

[0170] S1515: The second UE 122 releases the HO lock once it the HO complete by sending a release HO lock message to the device layer in the wireless device 120.

[0171] Based on the device HO lock, simultaneous handover for the first UE 121 and the second UE 122 can be avoided. Note that the signaling is exemplary and other entities in the network may be used to perform similar functions. The device HO lock may also be performed independently of CHO. The signaling presented here need not be separate, new standalone messages, but can be realized using new parameter setting on existing signaling messages, e.g., as part of the registration or PDU Session establishment procedures, and as part of the handover. The messages between the UEs and the device layer are also exemplary and can be realized e.g., by a device internal API.

[0172] To perform the method actions above, the first source network node 111 is configured to handle handover in the wireless communication network 100. The first source network node 111 may comprise an arrangement depicted in Figure 16. The first source network node 111 may comprise an input and output interface 10 configured to communicate with each other. The input and output interface 10 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0173] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 11 of a processing circuitry in the first source network node 111 depicted in Figure 16, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the first source network node 111. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the first source network node 111.

[0174] The first source network node 111 and / or processor 11 is configured to handle handover for the first UE 121 in the wireless communication network 100.

[0175] The first source network node 111 and / or processor 11 is configured to determine a handover timing condition for the first UE 121. the first UE 121 is configured to be comprised in a wireless device 120 further being configured to be comprised a second UE 122. The handover timing condition is adapted to enable handovers with disjoint handover interruption times for the first UE 121 and the second UE 122.

[0176] The first source network node 111 and / or processor 11 is configured to send the handover timing condition to the first UE 121.

[0177] In some embodiments, the handover timing condition is adapted to comprise any one out of a handover time interval, or a handover lock indication.

[0178] In some embodiments, the handover lock indication is adapted to configure the first UE 121 to request a handover lock from the wireless device 120 prior to initiating a handover.

[0179] In some embodiments, the handover time interval is adapted to comprise a time interval the first UE 121 is allowed to initiate a handover.

[0180] In some embodiments, the first source network node 111 and / or processor 11 is further configured to obtain handover timing condition data related to the first UE 121 and the second UE 122. In some embodiments, the handover timing condition is adapted to be determined based on the handover timing condition data.

[0181] In some embodiments, the handover timing condition is determined based on the handover timing data related to the first UE 121 and the second UE 122. The handover timing data may comprise any one out of handover execution times, a handover time interval, or handover lock capability.

[0182] The first source network node 111 may further comprise respective a memory 12 comprising one or more memory units. The memory 12 comprises instructions executable by the processor 11 in the first source network node 111.

[0183] The memory 12 is arranged to be used to store instructions, data, configurations, handover timing conditions, handover timing condition data, requests, responses, messages, identifiers, indications, parameters, applications to perform the methods herein when being executed in the first source network node 111.

[0184] In some embodiments, a computer program 13 comprises instructions, which when executed by the at least one processor 11 , cause the at least one processor 11 of the first source network node 111 to perform the actions above.

[0185] In some embodiments, a respective carrier 14 comprises the respective computer program 13, wherein the carrier 14 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0186] Thus, embodiments herein may disclose the first source network node 111 e.g., configured to handle handover in the wireless communication network 100. The first source network node 111 comprises the processor 11 and the memory 12, said memory 12 comprising instructions executable by said processor 11 whereby said first source network node 111 is operative to perform any of the methods herein.

[0187] As will be readily understood by those familiar with communications design, that functions means or modules 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 base station, for example.

[0188] 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, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and nonvolatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

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

[0190] To perform the method actions above, the first UE 121 is configured to handle handover in the wireless communication network 100. The first UE 121 may comprise an arrangement depicted in Figure 17.

[0191] The first UE 121 may comprise an input and output interface 20 configured to communicate with each other. The input and output interface 20 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0192] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 21 of a processing circuitry in the first UE 121 depicted in Figure 17, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the first UE 121. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the first UE 121.

[0193] The first UE 121 and / or processor 21 is configured to handle handover in the wireless communication network 100. The first UE 121 is configured to be comprised in the wireless device 120 further being configured to comprise at least one second UE 122.

[0194] The first UE 121 and / or processor 21 is configured to receive a handover timing condition from a first source network node 111. The handover timing condition is adapted to configure to first UE 121 to perform a handover with disjoint handover interruption time for the first UE 121 and the at least one second UE 122 comprised in the wireless device 120

[0195] The first UE 121 and / or processor 21 is configured to execute a handover based on the handover timing condition.

[0196] In some embodiments, the handover timing condition is adapted to comprise any one out of a handover time interval, or handover lock indication.

[0197] In some embodiments, the first UE 121 and or processor 21 is configured to execute the handover by further being configured to execute the handover within the handover time interval.

[0198] In some embodiments, the first UE 121 and or processor 21 is configured to execute the handover by further being configured to send, to the wireless device 120, a handover lock request.

[0199] In some embodiments, the first UE 121 and or processor 21 is configured to execute the handover by further being configured to receive a positive handover lock acknowledgement from the wireless device 120, initiate the handover execution, and send, to a device layer in the wireless device 120, a handover lock release message upon completion of the handover.

[0200] In some embodiments, the first UE 121 and or processor 21 is configured to execute the handover by further being configured to receive a negative handover lock acknowledgement from the wireless device 120, and refrain from initiating the handover execution until a positive acknowledgment is received. In some embodiments, the first UE 121 and or processor 21 is further configured to send, to a network node 111 , 115, 116, a handover execution time for the first UE 121.

[0201] The first UE 121 may further comprise respective a memory 22 comprising one or more memory units. The memory 22 comprises instructions executable by the processor 21 in the first UE 121.

[0202] The memory 22 is arranged to be used to store instructions, data, configurations, handover timing conditions, handover timing condition data, requests, responses, messages, identifiers, indications, parameters, applications to perform the methods herein when being executed in the first UE 121.

[0203] In some embodiments, a computer program 23 comprises instructions, which when executed by the at least one processor 21, cause the at least one processor 21 of the first UE 121 to perform the actions above.

[0204] In some embodiments, a respective carrier 24 comprises the respective computer program 23, wherein the carrier 24 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0205] Thus, embodiments herein may disclose the first UE 121 e.g., configured to handle handover in the wireless communication network 100. The first UE 121 comprises the processor 21 and the memory 22, said memory 22 comprising instructions executable by said processor 21 whereby said first UE 121 is operative to perform any of the methods herein.

[0206] As will be readily understood by those familiar with communications design, that functions means or modules 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 base station, for example.

[0207] 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, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and nonvolatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

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

[0209] To perform the method actions above, the first UE 121 is configured to handle handover in the wireless communication network 100. The first UE 121 may comprise an arrangement depicted in Figure 18.

[0210] The first UE 121 may comprise an input and output interface 30 configured to communicate with each other. The input and output interface 30 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0211] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 31 of a processing circuitry in the first UE 121 depicted in Figure 18, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the first UE 121. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the first UE 121.

[0212] The network node 115, 116 and / or processor 31 is configured to handle handover in the wireless communication network 100.

[0213] The network node 115, 116 and / or processor 31 is configured to send, to two or more source network nodes 111, 112, handover timing condition data related to two or more UEs 121 , 122. The two or more UEs 121, 122 being comprised in the wireless device 120. The handover timing condition is adapted to enable handovers with disjoint handover interruption times for the two or more UEs 121 , 122.

[0214] In some embodiments, the two or more UEs 121, 122 comprises a first UE 121 and a second UE 122.

[0215] In some embodiments, the handover timing condition data is adapted to comprise any one out of: handover execution times, a handover time interval, or handover lock capability.

[0216] In some embodiments, the handover lock capability is adapted to indicate that the two or more UEs 121 , 122 supports being configured to request a handover lock from the wireless device 120 prior to initiating a handover.

[0217] In some embodiments, the handover time interval is adapted to comprise a respective time interval the two or more UEs 121 , 122 are allowed to initiate a handover.

[0218] In some embodiments, the handover execution time is adapted to indicate respective maximum handover execution times for the two or more UEs 121 , 122.

[0219] In some embodiments, the network node 115, 116 and / or processor 31 may further be configured to determine the handover timing condition data based on any one out of handover execution times related to the two or more UEs 121 , 122, or handover lock capabilities related to the two or more UEs 121, 122.

[0220] In some embodiments, the network node 115, 116 and / or processor 31 may further be configured to obtain any one out of handover execution times related to the two or more UEs 121, 122, or handover lock capabilities related to the two or more UEs 121, 122.

[0221] In some embodiments, the network node 115, 116 and / or processor 31 may be adapted to comprise any one out of a user data management node 115, or a RAN server 116.

[0222] The first UE 121 may further comprise respective a memory 32 comprising one or more memory units. The memory 32 comprises instructions executable by the processor 31 in the first UE 121. The memory 32 is arranged to be used to store instructions, data, configurations, handover timing conditions, handover timing condition data, requests, responses, messages, identifiers, indications, parameters, applications to perform the methods herein when being executed in the first UE 121.

[0223] In some embodiments, a computer program 33 comprises instructions, which when executed by the at least one processor 31, cause the at least one processor 31 of the first UE 121 to perform the actions above.

[0224] In some embodiments, a respective carrier 34 comprises the respective computer program 33, wherein the carrier 34 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0225] Thus, embodiments herein may disclose the first UE 121 e.g., configured to handle handover in the wireless communication network 100. The first UE 121 comprises the processor 31 and the memory 32, said memory 32 comprising instructions executable by said processor 31 whereby said first UE 121 is operative to perform any of the methods herein.

[0226] As will be readily understood by those familiar with communications design, that functions means or modules 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 base station, for example.

[0227] 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, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and nonvolatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices. 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.

[0228] ADDITIONAL EXPLANATION

[0229] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0230] Figure 19 shows an example of a communication system QQ100 in accordance with some embodiments.

[0231] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3rdGeneration 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 QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 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 QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

[0232] 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- CLI-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 QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

[0233] 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 QQ100 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 QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0234] The UEs QQ112 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 QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 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 QQ102.

[0235] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more host computing systems, such as host QQ116. 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 QQ106 includes one more core network nodes (e.g., core network node QQ108) 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 QQ108. 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).

[0236] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102. The host QQ116 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.

[0237] As a whole, the communication system QQ100 of Figure 19 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.

[0238] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 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.

[0239] In some examples, the UEs QQ112 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 QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. 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).

[0240] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 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 QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 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 QQ114 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0241] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 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 QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0242] Figure 20 shows a UE QQ200 in accordance with some embodiments. The UE QQ200 presents additional details of some embodiments of the UE QQ112 of Figure 1. 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, vehiclemounted 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. 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).

[0243] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 20. 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.

[0244] The processing circuitry QQ202 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 QQ210. The processing circuitry QQ202 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 QQ202 may include multiple central processing units (CPUs).

[0245] In the example, the input / output interface QQ206 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 QQ200. 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.

[0246] In some embodiments, the power source QQ208 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 QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

[0247] The memory QQ210 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 QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0248] The memory QQ210 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 IIICC may for example be an embedded IIICC (elllCC), integrated IIICC (illlCC) or a removable IIICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 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 QQ210, which may be or comprise a device-readable storage medium.

[0249] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 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 QQ218 and / or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0250] In the illustrated embodiment, communication functions of the communication interface QQ212 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.

[0251] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, 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).

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

[0253] 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 smartwatch, 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 QQ200 shown in Figure 20.

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

[0255] Figure 21 shows a network node QQ300 in accordance with some embodiments. 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., O-RU, O-DU, O-CU).

[0256] 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).

[0257] 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- cel l / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs). The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 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 QQ300 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 QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, 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 QQ300.

[0258] The processing circuitry QQ302 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 QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.

[0259] In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 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 QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units. The memory QQ304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device- readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ302. The memory QQ304 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 QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0260] The communication interface QQ306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 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 QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components. In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

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

[0262] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 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 QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 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.

[0263] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 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 QQ308. As a further example, the power source QQ308 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.

[0264] Embodiments of the network node QQ300 may include additional components beyond those shown in 15 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 QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300. In some embodiments providing a core network node, such as core network node 108 of FIG. QQ1, some components, such as the radio front-end circuitry QQ318 and the RF transceiver circuitry QQ312 may be omitted.

[0265] Figure 22 is a block diagram illustrating a virtualization environment QQ400 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 QQ400 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 QQ400 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

[0266] Applications QQ402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. Hardware QQ404 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 QQ406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ408a and QQ408b (one or more of which may be generally referred to as VMs QQ408), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ406 may present a virtual operating platform that appears like networking hardware to the VMs QQ408.

[0267] The VMs QQ408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ406. Different embodiments of the instance of a virtual appliance QQ402 may be implemented on one or more of VMs QQ408, 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.

[0268] In the context of NFV, a VM QQ408 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 QQ408, and that part of hardware QQ404 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 QQ408 on top of the hardware QQ404 and corresponds to the application QQ402.

[0269] Hardware QQ404 may be implemented in a standalone network node with generic or specific components. Hardware QQ404 may implement some functions via virtualization. Alternatively, hardware QQ404 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 QQ410, which, among others, oversees lifecycle management of applications QQ402. In some embodiments, hardware QQ404 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 signaling can be provided with the use of a control system QQ412 which may alternatively be used for communication between hardware nodes and radio units.

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

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

[0272] When using the word "comprise" or “comprising” it shall be interpreted as nonlimiting, i.e. meaning "consist at least of".

[0273] The embodiments herein are not limited to the preferred embodiments described above. Various alternatives, modifications and equivalents may be used.

Claims

CLAIMS1. A method performed by a first source network node (111) for handling handover for a first User Equipment, UE, (121) in a wireless communication network (100), the method comprising: determining (602) a handover timing condition for the first UE (121), the first UE (121) being comprised in a wireless device (120) further comprising a second UE (122), wherein the handover timing condition enables handovers with disjoint handover interruption times for the first UE (121) and the second UE (122), and sending (603) the handover timing condition to the first UE (121).

2. The method according to claim 1, wherein the handover timing condition comprises any one out of:- a handover time interval, or- handover lock indication.

3. The method according to claim 2, wherein the handover lock indication configures the first UE (121), to request a handover lock from the wireless device (120) prior to initiating a handover.

4. The method according to claim 2, wherein the handover time interval comprises a time interval the first UE (121) is allowed to initiate a handover.

5. The method according to any of claims 1-4, wherein the method further comprises: obtaining (601) handover timing condition data related to the first UE (121) and the second UE (122), and wherein the handover timing condition is determined based on the handover timing data.

6. The method according to any of claims 1-5, wherein the handover timing condition is determined based on the handover timing data related to the first UE (121) and the second UE (122), the handover timing data comprising any one out of:- handover execution times,- a handover time interval, or- handover lock capability.

7. A computer program (13) comprising instructions, which when executed by a processor (11), causes the processor (11) to perform actions according to any of the claims 1-6.

8. A carrier (14) comprising the computer program (13) of claim 7, wherein the carrier (14) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer- readable storage medium.

9. A method performed by a first User Equipment, UE, (121) for handling handover in a wireless communication network (100), the first UE (121) being comprised in a wireless device (120) further comprising at least one second UE (122), the method comprising: receiving (702) a handover timing condition from a first source network node (111), wherein the handover timing condition configures to first UE (121) to perform a handover with disjoint handover interruption time for the first UE (121) and the at least one second UE (122) comprised in the wireless device (120), and executing (703) a handover based on the handover timing condition.

10. The method according to claim 9, wherein the handover timing condition comprises any one out of:- a handover time interval, or- handover lock indication.

11. The method according to claim 10, wherein executing (703) the handover comprises executing the handover within the handover time interval.

12. The method according to claim 10, wherein executing (703) the handover comprises sending, to the wireless device (120), a handover lock request.

13. The method according to claim 12, wherein executing (703) the handover further comprises receiving a positive handover lock acknowledgement from the wirelessdevice (120), initiating the handover execution, and sending, to the device layer in the wireless device (120), a handover lock release message upon completion of the handover.

14. The method according to claim any of claims 12-13, wherein executing (703) the handover further comprises receiving a negative handover lock acknowledgement from the wireless device (120), and refraining from initiating the handover execution until a positive acknowledgment is received.

15. The method according to any of claims 9-14, wherein the method further comprises: sending (701), to a network node (111, 115, 116), a handover execution time for the first UE (121).

16. A computer program (23) comprising instructions, which when executed by a processor (21), causes the processor (21) to perform actions according to any of the claims 9-15.

17. A carrier (24) comprising the computer program (23) of claim 16, wherein the carrier (24) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer- readable storage medium.

18. A method performed by a network node (115, 116) for handling handover in a wireless communication network (100), the method comprising: sending (803), to two or more source network nodes (111 , 112), handover timing condition data related to at two or more User Equipments, UE, (121 , 122), the two or more UEs (121, 122) being comprised in a wireless device (120), wherein the handover timing condition enables handovers with disjoint handover interruption times for the two or more UEs (121 , 122).

19. The method according to claim 18, wherein the two or more UEs (121 , 122) comprises a first UE (121) and a second UE (122).

20. The method according to any of claims 18-19, wherein the handover timing condition data comprises comprising any one out of:- handover execution times,- a handover time interval, or- handover lock capability.

21. The method according to claim 20, wherein any one or more out of:- the handover lock capability indicate that the two or more UEs (121 , 122) supports being configured to request a handover lock from the wireless device (120) prior to initiating a handover,- the handover time interval comprises a respective time interval the two or more UEs (121, 122) are allowed to initiate a handover, and- the handover execution time indicates respective maximum handover execution times for the two or more UEs (121, 122)22. The method according to any of claims 18-21 , wherein the method further comprises: determining (802) the handover timing condition data based on any one out of:- handover execution times related to the two or more UEs (121, 122), or- handover lock capabilities related to the two or more UEs (121 , 122).

23. The method according to any of claims 18-22, wherein the method further comprises: obtaining (801) any one out of:- handover execution times related to the two or more UEs (121, 122), or- handover lock capabilities related to the two or more UEs (121 , 122).

24. The method according to any of claims 18-23, wherein the network node (115, 116) comprises any one out of:- a user data management node (115), or- a Radio Access Network, RAN, server (116).

25. A computer program (33) comprising instructions, which when executed by a processor (31), causes the processor (31) to perform actions according to any of the claims 18-24.

26. A carrier (34) comprising the computer program (33) of claim 25, wherein the carrier (34) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer- readable storage medium.

27. A first source network node (111) configured to handle handover for a first User Equipment, UE, (121) in a wireless communication network (100), the first source network node (111) further being configured to: determine a handover timing condition for the first UE (121), the first UE (121) is configured to be comprised in a wireless device (120) further being configured to be comprised a second UE (122), wherein the handover timing condition is adapted to enable handovers with disjoint handover interruption times for the first UE (121) and the second UE (122), and send the handover timing condition to the first UE (121).

28. The first source network node (111) according to claim 27, wherein the handover timing condition is adapted to comprise any one out of:- a handover time interval, or- handover lock indication.

29. The first source network node (111) according to claim 28, wherein the handover lock indication is adapted to configure the first UE (121), to request a handover lock from the wireless device (120) prior to initiating a handover.

30. The first source network node (111) according to claim 28, wherein the handover time interval is adapted to comprise a time interval the first UE (121) is allowed to initiate a handover.

31. The first source network node (111) according to any of claims 27-30, wherein the first source network node (111) is further configured to: obtain handover timing condition data related to the first UE (121) and the second UE (122), and wherein the handover timing condition is adapted to be determined based on the handover timing condition data.

32. The first source network node (111) according to any of claims 27-31, wherein the handover timing condition is determined based on the handover timing data related to the first UE (121) and the second UE (122), the handover timing data comprising any one out of:- handover execution times,- a handover time interval, or- handover lock capability.

33. A first User Equipment, UE, (121) configured to handle handover in a wireless communication network (100), the first UE (121) is configured to be comprised in a wireless device (120) further being configured to comprise at least one second UE (122), the first UE (121) further being configured to: receive a handover timing condition from a first source network node (111), wherein the handover timing condition is adapted to configure to first UE (121) to perform a handover with disjoint handover interruption time for the first UE (121) and the at least one second UE (122) comprised in the wireless device (120), and execute a handover based on the handover timing condition.

34. The first UE (121) according to claim 33, wherein the handover timing condition is adapted to comprise any one out of:- a handover time interval, or- handover lock indication.

35. The first UE (121) according to claim 34, wherein the first UE (121) is configured to execute the handover by further being configured to execute the handover within the handover time interval.

36. The first UE (121) according to claim 34, wherein the first UE (121) is configured to execute the handover by further being configured to send, to the wireless device (120), a handover lock request.

37. The first UE (121) according to claim 36, wherein the first UE (121) is configured to execute the handover by further being configured to receive a positive handover lock acknowledgement from the wireless device (120), initiate the handoverexecution, and send, to a device layer in the wireless device (120), a handover lock release message upon completion of the handover.

38. The first UE (121) according to claim any of claims 36-37, wherein the first UE (121) is configured to execute the handover by further being configured to receive a negative handover lock acknowledgement from the wireless device (120), and refrain from initiating the handover execution until a positive acknowledgment is received.

39. The first UE (121) according to any of claims 33-38, wherein the first UE (121) is further configured to: send, to a network node (111 , 115, 116), a handover execution time for the first UE (121).

40. A network node (115, 116) configured to handle handover in a wireless communication network (100), the network node (115, 116) further being configured to: send, to two or more source network nodes (111 , 112), handover timing condition data related to at two or more User Equipments, UE, (121, 122), the two or more UEs (121 , 122) being comprised in a wireless device (120), wherein the handover timing condition is adapted to enable handovers with disjoint handover interruption times for the two or more UEs (121 , 122).

41. The network node (115, 116) according to claim 40, wherein the two or more UEs (121, 122) comprises a first UE (121) and a second UE (122).

42. The network node (115, 116) according to any of claims 40-41, wherein the handover timing condition data is adapted to comprise any one out of:- handover execution times,- a handover time interval, or- handover lock capability.

43. The network node (115, 116) according to claim 42, wherein any one or more out of:- the handover lock capability is adapted to indicate that the two or more UEs (121 , 122) supports being configured to request a handover lock from the wireless device (120) prior to initiating a handover,- the handover time interval is adapted to comprise a respective time interval the two or more UEs (121, 122) are allowed to initiate a handover, and- the handover execution time is adapted to indicate respective maximum handover execution times for the two or more UEs (121 , 122)44. The network node (115, 116) according to any of claims 40-43, wherein the network node (115, 116) is further configured to: determine the handover timing condition data based on any one out of:- handover execution times related to the two or more UEs (121, 122), or- handover lock capabilities related to the two or more UEs (121 , 122).

45. The network node (115, 116) according to any of claims 40-44 wherein the network node (115, 116) is further configured to: obtain any one out of:- handover execution times related to the two or more UEs (121, 122), or- handover lock capabilities related to the two or more UEs (121 , 122).

46. The network node (115, 116) according to any of claims 40-45, wherein the network node (115, 116) is adapted to comprise any one out of:- a user data management node (115), or- a Radio Access Network, RAN, server (116).

Images