WO2023213390A1

WO2023213390A1 - Method for handover

Info

Publication number: WO2023213390A1
Application number: PCT/EP2022/062024
Authority: WO
Inventors: Krzysztof Kordybach; Raghuram Reddy KRISHNAMURTHY; Ahmad AWADA; Srinivasan Selvaganapathy; Jedrzej STANCZAK
Original assignee: Nokia Solutions And Networks Oy
Priority date: 2022-05-04
Filing date: 2022-05-04
Publication date: 2023-11-09

Abstract

An apparatus comprising means for receiving an addition request from a target master node with indication that the request refers to a conditional handover, said request comprising an identifier of a user equipment and an identifier of a source master node; means for using the identifier of the user equipment and the identifier of the source master node to check, if the apparatus has a controlling target primary cell prepared for this user equipment; means for comparing an existing secondary group configuration with a secondary group configuration included in the request; means for verifying, based on the comparison, that a same data radio bearer can be allocated for the addition request; and means for responding to the request with an identifier of a tunnel endpoint for downlink data forwarding, which have already been allocated for a previous addition request.

Description

METHOD FOR HANDOVER

TECHNICAL FIELD

[0001] The present invention relates to handover methods.

BACKGROUND

[0002] A conditional handover (CHO) is a feature supported in LTE and in 5G NR. The CHO resembles in many aspects the previously known “ordinary” handover (HO), i.e. the legacy HO. As a main difference to the legacy HO, in the CHO the user equipment (UE) starts the preparations for handover to the target node only when an additional CHO execution condition is met. Another difference between the legacy HO and the CHO is the preparation of multiple target cells in the CHO. Thus, the CHO reserves more resources at target cells than a legacy HO while waiting for the execution.

[0003] In case of multiple preparations, each of the target Master Nodes (MNs) may prepare its own target Secondary Node (SN). Each target SN will therefore have to reserve the needed resources, too.

[0004] When a secondary cell group (SCG) bearer configuration contains SN- terminated bearers, the SN allocates the needed tunnel endpoints. Then, the information on the allocated Tunnel Endpoint Identities (TEIDs) is forwarded to the source node, which may start data forwarding. In case of CHO, it may be the early data forwarding, which is started yet before the UE selects the target node for handover execution. Therefore, the source sends data to all prepared target nodes (after the target nodes have been prepared and configured to the UE). From the target SN perspective, if there are SN-terminated bearers, it means possibly receiving the same data to all allocated TEIDs. This, in turn, requires allocating and managing separate downlink (DL) buffers for the same data. Effectively, this leads to severe resource over-allocation.

SUMMARY

[0005] Now, an improved method and technical equipment implementing the method has been invented, by which the above problems are alleviated. Various aspects include a method, an apparatus and a non-transitory computer readable medium comprising a computer program, or a signal stored therein, which are characterized by what is stated in the independent claims. Various details of the embodiments are disclosed in the dependent claims and in the corresponding images and description.

[0006] The scope of protection sought for various embodiments of the invention is set out by the independent claims. The embodiments and features, if any, described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embodiments of the invention.

[0007] According to a first aspect, there is provided an apparatus comprising means for receiving an addition request from a target master node with indication that the request refers to a conditional handover, said request comprising an identifier of a user equipment and an identifier of a source master node; means for using the identifier of the user equipment and the identifier of the source master node to check, if the apparatus has a controlling target primary cell prepared for this user equipment; means for comparing an existing secondary group configuration with a secondary group configuration included in the request; means for verifying, based on the comparison, that a same data radio bearer can be allocated for the addition request; and means for responding to the request with an identifier of a tunnel endpoint for downlink data forwarding, which have already been allocated for a previous addition request.

[0008] An apparatus according to a second aspect comprises at least one processor and at least one memory, said at least one memory stored with computer program code thereon, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: receive an addition request from a target master node with indication that the request refers to a conditional handover, said request comprising an identifier of a user equipment and an identifier of a source master node; use the identifier of the user equipment and the identifier of the source master node to check, if the apparatus has a controlling target primary cell prepared for this user equipment; compare an existing secondary group configuration with a secondary group configuration included in the request; verify, based on the comparison, that a same data radio bearer can be allocated for the addition request; and respond to the request with an identifier of a tunnel endpoint for downlink data forwarding, which have already been allocated for a previous addition request. [0009] According to an embodiment, the apparatus comprises computer program code configured to cause the apparatus to perform: identifying that the addition request is related to a preparation from another master node; and allocating the same identifier of a tunnel endpoint for the addition request.

[0010] According to an embodiment, the apparatus comprises computer program code configured to cause the apparatus to perform: responding to the addition request to the target master node by including an indication to an addition request acknowledgement message that the target secondary node is going to share the allocated identifiers of the tunnel endpoints for downlink data forwarding with any other target master node, if there is a matching addition request.

[0011] According to an embodiment, the apparatus comprises computer program code configured to cause the apparatus to perform: examining whether the addition requests comprise identification of the same user equipment and the same secondary cell group configuration.

[0012] According to an embodiment, the apparatus comprises computer program code configured to cause the apparatus to perform: allocating only a single buffer for downlink data; and associate the identifier of the tunnel endpoint with the single buffer.

[0013] A method according to a third aspect comprises receiving an addition request from a target master node with indication that the request refers to a conditional handover, said request comprising an identifier of a user equipment and an identifier of a source master node; using the identifier of the user equipment and the identifier of the source master node to check, if the apparatus has a controlling target primary cell prepared for this user equipment; comparing an existing secondary group configuration with a secondary group configuration included in the request; verifying, based on the comparison, that a same data radio bearer can be allocated for the addition request; and responding to the request with an identifier of a tunnel endpoint for downlink data forwarding, which have already been allocated for a previous addition request.

[0014] An apparatus according to a fourth aspect comprises means for receiving, by a source node, a tunnel endpoint identifier of a first target master node and a first target tunnel endpoint identifier from the first target master node; means for receiving, by the source node, a tunnel endpoint identifier of a second target master node and a second target tunnel endpoint identifier from the second target master node; means for determining, by the source node, that the first target tunnel endpoint identifier and the second target tunnel endpoint identifier correspond with each other; and means for deciding, by the source node, to send data addressed to a target secondary node via only one of the first target master node and the second target master node.

[0015] An apparatus according to a fifth aspect comprises at least one processor and at least one memory, said at least one memory stored with computer program code thereon, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: receive a tunnel endpoint identifier of a first target master node and a first target tunnel endpoint identifier from the first target master node; receive a tunnel endpoint identifier of a second target master node and a second target tunnel endpoint identifier from the second target master node; determine that the first target tunnel endpoint identifier and the second target tunnel endpoint identifier correspond with each other; and decide to send data addressed to a target secondary node via only one of the first target master node and the second target master node.

[0016] A method according to a sixth aspect comprises receiving, by a source node, a tunnel endpoint identifier of a first target master node and a first target tunnel endpoint identifier from the first target master node; receiving, by the source node, a tunnel endpoint identifier of a second target master node and a second target tunnel endpoint identifier from the second target master node; determining, by the source node, that the first target tunnel endpoint identifier and the second target tunnel endpoint identifier correspond with each other; and deciding, by the source node, to send data addressed to a target secondary node via only one of the first target master node and the second target master node.

[0017] An apparatus according to a seventh aspect comprises means for sending an addition request related to a conditional handover to a target secondary node, the addition request comprising information of requested secondary cell group bearer configuration and information of identity of a user equipment; means for receiving an addition request acknowledgement from the target secondary node, the addition request acknowledgement comprising a secondary cell group configuration and an indication that an identifier of a tunnel endpoint allocated by the target secondary node for downlink data is shared with another target master node; means for deciding to perform, based on the indication, one of the following: using indirect data forwarding and send an identifier of a tunnel endpoint of the apparatus and the shared identifier of the tunnel endpoint allocated by the target secondary node for downlink data to a source master node, or using direct data forwarding and send an identifier of the shared identifier of the tunnel endpoint allocated by the target secondary node for downlink data to a source master node.

[0018] An apparatus according to an eighth aspect comprises at least one processor and at least one memory, said at least one memory stored with computer program code thereon, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: send an addition request related to a conditional handover to a target secondary node, the addition request comprising information of requested secondary cell group bearer configuration and information of identity of a user equipment; receive an addition request acknowledgement from the target secondary node, the addition request acknowledgement comprising a secondary cell group configuration and an indication that an identifier of a tunnel endpoint allocated by the target secondary node for downlink data is shared with another target master node; based on the indication decide to perform one of the following: use indirect data forwarding and send an identifier of a tunnel endpoint of the apparatus and the shared identifier of the tunnel endpoint allocated by the target secondary node for downlink data to a source master node, or use direct data forwarding and send an identifier of the shared identifier of the tunnel endpoint allocated by the target secondary node for downlink data to a source master node.

[0019] A method according to a ninth aspect comprises sending an addition request related to a conditional handover to a target secondary node, the addition request comprising information of requested secondary cell group bearer configuration and information of identity of a user equipment; receiving an addition request acknowledgement from the target secondary node, the addition request acknowledgement comprising a secondary cell group configuration and an indication that an identifier of a tunnel endpoint allocated by the target secondary node for downlink data is shared with another target master node; based on the indication deciding to perform one of the following: using indirect data forwarding; and sending an identifier of a tunnel endpoint of the apparatus and the shared identifier of the tunnel endpoint allocated by the target secondary node for downlink data to a source master node, or using direct data forwarding and sending an identifier of the shared identifier of the tunnel endpoint allocated by the target secondary node for downlink data to a source master node.

[0020] An apparatus according to a tenth aspect comprises means for sending, by a target master node, an addition request related to a conditional handover to a target secondary node, the addition request comprising information of requested secondary cell group bearer configuration and information of identity of a user equipment; means for receiving an addition request acknowledgement from the target secondary node, the addition request acknowledgement comprising a secondary cell group configuration and an indication that an identifier of a tunnel endpoint allocated by the target secondary node for downlink data is shared with another target master node; means for performing, based on the indication, one of the following: deciding to use indirect data forwarding and sending an identifier of a tunnel endpoint of the apparatus and the shared identifier of the tunnel endpoint allocated by the target secondary node for downlink data to a source master node, or deciding to use direct data forwarding and sending an identifier of the shared identifier of the tunnel endpoint allocated by the target secondary node for downlink data to a source master node.

[0021] Computer readable storage media according to further aspects comprise code for use by an apparatus, which when executed by a processor, causes the apparatus to perform the above methods.

BRIEF DESCRIPTION OF THE DRAWINGS

[0022] For a more complete understanding of the example embodiments, reference is now made to the following descriptions taken in connection with the accompanying drawings in which:

[0023] Fig. 1 shows a schematic block diagram of a user equipment apparatus for incorporating functionalities for implementing various embodiments;

[0024] Fig. 2 shows schematically a layout of a user equipment apparatus according to an example embodiment;

[0025] Fig. 3 shows a part of an exemplifying radio access network;

[0026] Fig. 4 shows a signalling diagram for a conditional handover process; [0027] Fig. 5a illustrates a signalling diagram according to an example embodiment;

[0028] Fig. 5b illustrates a signalling diagram according to another example embodiment;

[0029] Fig. 5 c illustrates a signalling diagram according to yet another example embodiment;

[0030] Fig. 6a shows a flow chart for a method for signalling in conditional handover in view of a target SN according to an embodiment;

[0031] Fig. 6b shows a flow chart for a method for signalling in conditional handover in view of a target MN according to an embodiment;

[0032] Fig. 7 shows a schematic block diagram of a network node apparatus according to an embodiment;

[0033] Fig. 8a shows an exemplified signalling chart for obtaining the identification of the user equipment according to an approach;

[0034] Fig. 8b shows an exemplified signalling chart for obtaining the identification of the user equipment according to another approach.

DETAILED DESCRIPTON OF SOME EXAMPLE EMBODIMENTS

[0035] The following describes in further detail suitable apparatus and possible mechanisms carrying out the operations for a conditional handover. While the following focuses on 5G networks, the embodiments as described further below are by no means limited to be implemented in said networks only, but they are applicable in any network supporting conditional handover.

[0036] In this regard, reference is first made to Figures 1 and 2, where Figure 1 shows a schematic block diagram of an exemplary apparatus or electronic device 50, which may incorporate the arrangement according to the embodiments. Figure 2 shows a layout of an apparatus according to an example embodiment. The elements of Figs. 1 and 2 will be explained next.

[0037] The electronic device 50 may for example be a mobile terminal or user equipment of a wireless communication system. The apparatus 50 may comprise a housing 30 for incorporating and protecting the device. The apparatus 50 further may comprise a display 32 and a keypad 34. Instead of the keypad, the user interface may be implemented as a virtual keyboard or data entry system as part of a touch-sensitive display.

[0038] The apparatus may comprise a microphone 36 or any suitable audio input which may be a digital or analogue signal input. The apparatus 50 may further comprise an audio output device, such as anyone of: an earpiece 38, speaker, or an analogue audio or digital audio output connection. The apparatus 50 may also comprise a battery 40 (or the device may be powered by any suitable mobile energy device such as solar cell, fuel cell or clockwork generator). The apparatus may further comprise a camera 42 capable of recording or capturing images and/or video. The apparatus 50 may further comprise an infrared port 41 for short range line of sight communication to other devices. In other embodiments the apparatus 50 may further comprise any suitable short-range communication solution such as for example a Bluetooth wireless connection or a USB/firewire wired connection.

[0039] The apparatus 50 may comprise a controller 56 or processor for controlling the apparatus 50. The controller 56 may be connected to memory 58 which may store both user data and instructions for implementation on the controller 56. The memory may be random access memory (RAM) and/or read only memory (ROM). The memory may store computer-readable, computer-executable software including instructions that, when executed, cause the controller/processor to perform various functions described herein. In some cases, the software may not be directly executable by the processor but may cause a computer (e.g., when compiled and executed) to perform functions described herein. The controller 56 may further be connected to codec circuitry 54 suitable for carrying out coding and decoding of audio and/or video data or assisting in coding and decoding carried out by the controller.

[0040] The apparatus 50 may comprise radio interface circuitry 52 connected to the controller and suitable for generating wireless communication signals for example for communication with a cellular communications network, a wireless communications system or a wireless local area network. The apparatus 50 may further comprise an antenna 44 connected to the radio interface circuitry 52 for transmitting radio frequency signals generated at the radio interface circuitry 52 to other apparatus(es) and for receiving radio frequency signals from other apparatus(es). [0041] In the following, different exemplifying embodiments will be described using, as an example of an access architecture to which the embodiments may be applied, a radio access architecture based on Long Term Evolution Advanced (LTE Advanced, LTE-A) or new radio (NR, 5G), without restricting the embodiments to such an architecture, however. A person skilled in the art appreciates that the embodiments may also be applied to other kinds of communications networks having suitable means by adjusting parameters and procedures appropriately. Some examples of other options for suitable systems are the universal mobile telecommunications system (UMTS) radio access network (UTRAN or E-UTRAN), long term evolution (LTE, the same as E-UTRA), wireless local area network (WLAN or WiFi), worldwide interoperability for microwave access (WiMAX), Bluetooth®, personal communications services (PCS), ZigBee®, wideband code division multiple access (WCDMA), systems using ultra-wideband (UWB) technology, sensor networks, mobile ad-hoc networks (MANETs) and Internet protocol multimedia subsystems (IMS) or any combination thereof.

[0042] Figure 3 depicts examples of simplified system architectures only showing some elements and functional entities, all being logical units, whose implementation may differ from what is shown. The connections shown in Figure 3 are logical connections; the actual physical connections may be different. It is apparent to a person skilled in the art that the system typically comprises also other functions and structures than those shown in Figure 3. The embodiments are not, however, restricted to the system given as an example but a person skilled in the art may apply the solution to other communication systems provided with necessary properties.

[0043] The example of Figure 3 shows a part of an exemplifying radio access network. [0044] Figure 3 shows user devices 300 and 302 configured to be in a wireless connection on one or more communication channels in a cell with an access node (such as (e/g)NodeB) 304 providing the cell. The physical link from a user device to a (e/g)NodeB is called uplink or reverse link and the physical link from the (e/g)NodeB to the user device is called downlink or forward link. It should be appreciated that (e/g)NodeBs or their functionalities may be implemented by using any node (such as Integrated Access and Backhaul (IAB) node), host, server or access point etc. entity suitable for such a usage. [0045] A communication system typically comprises more than one (e/g)NodeB in which case the (e/g)NodeBs may also be configured to communicate with one another over links, wired or wireless, designed for the purpose. These links may be used for signaling purposes. The (e/g)NodeB is a computing device configured to control the radio resources of communication system it is coupled to. The NodeB may also be referred to as a base station, an access point or any other type of interfacing device including a relay station capable of operating in a wireless environment. The (e/g)NodeB includes or is coupled to transceivers. From the transceivers of the (e/g)NodeB, a connection is provided to an antenna unit that establishes bi-directional radio links to user devices. The antenna unit may comprise a plurality of antennas or antenna elements. The (e/g)NodeB is further connected to core network 310 (CN or next generation core NGC). Depending on the system, the counterpart on the CN side can be a serving gateway (S-GW, routing and forwarding user data packets), packet data network gateway (P-GW), for providing connectivity of user devices (UEs) to external packet data networks, or mobile management entity (MME), etc. The CN may comprise network entities or nodes that may be referred to management entities. Examples of the network entities comprise at least an Access and Mobility Management Function (AMF).

[0046] In 5G NR, the User Plane Function (UPF) may be used to separate the control plane and the user plane functions. Therein, the Packet Gateway (PGW) control and user plane functions may be decoupled, whereby the data forwarding component (PGW-U) may be decentralized, while the PGW-related signaling (PGW-C) remains in the core. This allows packet processing and traffic aggregation to be performed closer to the network edge, increasing bandwidth efficiencies while reducing network load.

[0047] The user device (also called a user equipment (UE), a user terminal, a terminal device, a wireless device, a mobile station (MS) etc.) illustrates one type of an apparatus to which resources on the air interface are allocated and assigned, and thus any feature described herein with a user device may be implemented with a corresponding network apparatus, such as a relay node, an eNB, and an gNB. An example of such a relay node is a layer 3 relay (self-backhauling relay) towards the base station.

[0048] The user device typically refers to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (mobile phone), smartphone, personal digital assistant (PDA), handset, device using a wireless modem (alarm or measurement device, etc.), laptop and/or touch screen computer, tablet, game console, notebook, and multimedia device. It should be appreciated that a user device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network. A user device may also be a device having capability to operate in Internet of Things (loT) network which is a scenario in which objects are provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction. Accordingly, the user device may be an loT-device. The user device may also utilize cloud. In some applications, a user device may comprise a small portable device with radio parts (such as a watch, earphones or eyeglasses) and the computation is carried out in the cloud. The user device (or in some embodiments a layer 3 relay node) is configured to perform one or more of user equipment functionalities. The user device may also be called a subscriber unit, mobile station, remote terminal, access terminal, user terminal or user equipment (UE) just to mention but a few names or apparatuses.

[0049] Various techniques described herein may also be applied to a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities). CPS may enable the implementation and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers, etc.) embedded in physical objects at different locations. Mobile cyber physical systems, in which the physical system in question has inherent mobility, are a subcategory of cyberphysical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals.

[0050] Additionally, although the apparatuses have been depicted as single entities, different units, processors and/or memory units (not all shown in Fig. 1) may be implemented.

[0051] 5G enables using multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and employing a variety of radio technologies depending on service needs, use cases and/or spectrum available. The access nodes of the radio network form transmission/reception (TX/Rx) points (TRPs), and the UEs are expected to access networks of at least partly overlapping multi-TRPs, such as macro-cells, small cells, pico-cells, femto-cells, remote radio heads, relay nodes, etc. The access nodes may be provided with Massive MIMO antennas, i.e. very large antenna array consisting of e.g. hundreds of antenna elements, implemented in a single antenna panel or in a plurality of antenna panels, capable of using a plurality of simultaneous radio beams for communication with the UE. The UEs may be provided with MIMO antennas having an antenna array consisting of e.g. dozens of antenna elements, implemented in a single antenna panel or in a plurality of antenna panels. Thus, the UE may access one TRP using one beam, one TRP using a plurality of beams, a plurality of TRPs using one (common) beam or a plurality of TRPs using a plurality of beams.

[0052] The 4G/LTE networks support some multi-TRP schemes, but in 5G NR the multi-TRP features are enhanced e.g. via transmission of multiple control signals via multi- TRPs, which enables to improve link diversity gain. Moreover, high carrier frequencies (e.g., mmWaves) together with the Massive MIMO antennas require new beam management procedures for multi-TRP technology.

[0053] 5G mobile communications supports a wide range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications (such as (massive) machine-type communications (mMTC), including vehicular safety, different sensors and real-time control. 5G is expected to have multiple radio interfaces, namely below 6GHz, cmWave and mmWave, and also capable of being integrated with existing legacy radio access technologies, such as the LTE. Integration with the LTE may be implemented, at least in the early phase, as a system, where macro coverage is provided by the LTE and 5G radio interface access comes from small cells by aggregation to the LTE. In other words, 5G is planned to support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6GHz - cmWave, below 6GHz - cmWave - mmWave). One of the concepts considered to be used in 5G networks is network slicing in which multiple independent and dedicated virtual sub-networks (network instances) may be created within the same infrastructure to run services that have different requirements on latency, reliability, throughput and mobility. [0054] Frequency bands for 5G NR are separated into two frequency ranges: Frequency

Range 1 (FR1) including sub-6 GHz frequency bands, i.e. bands traditionally used by previous standards, but also new bands extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz, and Frequency Range 2 (FR2) including frequency bands from 24.25 GHz to 52.6 GHz. Thus, FR2 includes the bands in the mmWave range, which due to their shorter range and higher available bandwidth require somewhat different approach in radio resource management compared to bands in the FR1.

[0055] The current architecture in LTE networks is fully distributed in the radio and fully centralized in the core network. The low latency applications and services in 5G require to bring the content close to the radio which leads to local break out and multiaccess edge computing (MEC). 5G enables analytics and knowledge generation to occur at the source of the data. This approach requires leveraging resources that may not be continuously connected to a network such as laptops, smartphones, tablets and sensors. MEC provides a distributed computing environment for application and service hosting. It also has the ability to store and process content in close proximity to cellular subscribers for faster response time. Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer-to-peer ad hoc networking and processing also classifiable as local cloud/fog computing and grid/mesh computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and/or latency critical), critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications).

[0056] The communication system is also able to communicate with other networks, such as a public switched telephone network or the Internet 312, or utilize services provided by them. The communication network may also be able to support the usage of cloud services, for example at least part of core network operations may be carried out as a cloud service (this is depicted in Fig. 3 by “cloud” 314). The communication system may also comprise a central control entity, or a like, providing facilities for networks of different operators to cooperate for example in spectrum sharing. [0057] Edge cloud may be brought into radio access network (RAN) by utilizing network function virtualization (NFV) and software defined networking (SDN). Using edge cloud may mean access node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or base station comprising radio parts. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. Application of cloudRAN architecture enables RAN real time functions being carried out at the RAN side (in a distributed unit, DU) and non-real time functions being carried out in a centralized manner (in a centralized unit, CU 308).

[0058] It should also be understood that the distribution of labor between core network operations and base station operations may differ from that of the LTE or even be nonexistent. Some other technology advancements probably to be used are Big Data and all-IP, which may change the way networks are being constructed and managed. 5G (or new radio, NR) networks are being designed to support multiple hierarchies, where MEC servers can be placed between the core and the base station or nodeB (gNB). It should be appreciated that MEC can be applied in 4G networks as well. The gNB is a next generation Node B (or, new Node B) supporting the 5G network (i.e., the NR).

[0059] 5G may also utilize non-terrestrial nodes 306, e.g. access nodes, to enhance or complement the coverage of 5G service, for example by providing backhauling, wireless access to wireless devices, service continuity for machine-to-machine (M2M) communication, service continuity for Internet of Things (loT) devices, service continuity for passengers on board of vehicles, ensuring service availability for critical communications and/or ensuring service availability for future railway/maritime/aeronautical communications. The non-terrestrial nodes may have fixed positions with respect to the Earth surface or the non-terrestrial nodes may be mobile nonterrestrial nodes that may move with respect to the Earth surface. The non-terrestrial nodes may comprise satellites and/or HAPSs. Satellite communication may utilize geostationary earth orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in particular mega-constellations (systems in which hundreds of (nano)satellites are deployed). Each satellite in the mega-constellation may cover several satellite-enabled network entities that create on-ground cells. The on-ground cells may be created through an on-ground relay node 304 or by a gNB located on-ground or in a satellite. [0060] A person skilled in the art appreciates that the depicted system is only an example of a part of a radio access system and in practice, the system may comprise a plurality of (e/g)NodeBs, the user device may have an access to a plurality of radio cells and the system may comprise also other apparatuses, such as physical layer relay nodes or other network elements, etc. At least one of the (e/g)NodeBs or may be a Home(e/g)nodeB. Additionally, in a geographical area of a radio communication system a plurality of different kinds of radio cells as well as a plurality of radio cells may be provided. Radio cells may be macro cells (or umbrella cells) which are large cells, usually having a diameter of up to tens of kilometers, or smaller cells such as micro-, femto- or picocells. The (e/g)NodeBs of Fig. 1 may provide any kind of these cells. A cellular radio system may be implemented as a multilayer network including several kinds of cells. Typically, in multilayer networks, one access node provides one kind of a cell or cells, and thus a plurality of (e/g)NodeBs are required to provide such a network structure.

[0061] For fulfilling the need for improving the deployment and performance of communication systems, the concept of “plug-and-play” (e/g)NodeBs has been introduced. Typically, a network which is able to use “plug-and-play” (e/g)Node Bs, includes, in addition to Home (e/g)NodeBs (H(e/g)nodeBs), a home node B gateway, or HNB-GW (not shown in Fig. 1). A HNB Gateway (HNB-GW), which is typically installed within an operator’s network may aggregate traffic from a large number of HNBs back to a core network.

[0062] The Radio Resource Control (RRC) protocol is used in various wireless communication systems for defining the air interface between the UE and a base station, such as eNB/gNB. This protocol is specified by 3GPP in in TS 36.331 for LTE and in TS 38.331 for 5G. In terms of the RRC, the UE may operate in LTE and in 5G in an idle mode or in a connected mode, wherein the radio resources available for the UE are dependent on the mode where the UE at present resides. In 5G, the UE may also operate in inactive mode. In the RRC idle mode, the UE has no connection for communication, but the UE is able to listen to page messages. In the RRC connected mode, the UE may operate in different states, such as CELL DCH (Dedicated Channel), CELL FACH (Forward Access Channel), CELL PCH (Cell Paging Channel) and URA PCH (URA Paging Channel). The UE may communicate with the eNB/gNB via various logical channels like Broadcast Control Channel (BCCH), Paging Control Channel (PCCH), Common Control Channel (CCCH), Dedicated Control Channel (DCCH), Dedicated Traffic Channel (DTCH). [0063] The transitions between the states is controlled by a state machine of the RRC. When the UE is powered up, it is in a disconnected mode/idle mode. The UE may transit to RRC connected mode with an initial attach or with a connection establishment. If there is no activity from the UE for a short time, eNB/gNB may suspend its session by moving to RRC Inactive and can resume its session by moving to RRC connected mode. The UE can move to the RRC idle mode from the RRC connected mode or from the RRC inactive mode.

[0064] The actual user and control data from network to the UEs is transmitted via downlink physical channels, which in 5G include Physical downlink control channel (PDCCH) which carries the necessary downlink control information (DCI), Physical Downlink Shared Channel (PDSCH), which carries the user data and system information for user, and Physical broadcast channel (PBCH), which carries the necessary system information to enable a UE to access the 5G network.

[0065] The user and control data from UE to the network is transmitted via uplink physical channels, which in 5G include Physical Uplink Control Channel (PUCCH), which is used for uplink control information including HARQ (Hybrid Automatic Repeat reQuest) feedback acknowledgments, scheduling request, and downlink channel-state information for link adaptation, Physical Uplink Shared Channel (PUSCH), which is used for uplink data transmission, and Physical Random Access Channel (PRACH), which is used by the UE to request connection setup referred to as random access.

[0066] A conditional handover (CHO) is a feature supported in LTE and in 5G NR. The CHO resembles in many aspects the previously known “ordinary” handover (HO), i.e. the legacy HO. An exemplary signalling diagram of CHO is shown in Fig. 4. A configured event triggers the UE to send a measurement report to its current serving node e/gNB. In terms of the HO process, the currently serving node may be referred to as a source node. Based on this report, the source node typically prepares one or more candidate target nodes for the handover. The preparation includes a Handover Request sent to each target node and a Handover Request Acknowledge received from each target node. The source node then sends a handover command (including the RRC Reconfiguration message) to the UE. For the legacy HO, the UE would immediately handover to the target node by reconfiguring it as its new serving e/gNB node to complete the handover.

[0067] Instead, for the CHO, the UE will only access the target node once an additional CHO execution condition is fulfilled. The condition is configured, e.g. by the source cell during HO Command. Thus, the UE monitors whether the CHO execution condition is fulfilled, and meanwhile the user data may be transmitted between the UE and the source node. Only when the CHO execution condition is fulfilled, the UE starts the preparations for handover to the target node.

[0068] Dual Connectivity (DC) is a feature supported in LTE and in 5G NR enabling aggregation of two radio links at the PDCP (Packet Data Convergence Protocol) layer level. For resource aggregation, a UE in RRC CONNECTED state is allocated two radio links from two different network nodes that may be connected via a non-ideal backhaul. The first node, Master Node (MN), serves as mobility and signaling anchor and the second node, Secondary Node (SN), provides additional local radio resources for UE. The two resource sets are called as Master Cell Group (MCG, associated with MN) and Secondary Cell Group (SCG, associated with SN). The MN can be either LTE eNB or NR gNB. The SN can be either LTE eNB or NR gNB. The MN and the SN can be the same node.

[0069] Dual Connectivity can improve user throughput and mobility robustness, since the users may be connected simultaneously to MCG and SCG, as well as improve load balancing between MCG and SCG resources.

[0070] The CHO has been specified for UEs configured with use of Dual Connectivity. Herein, the source MN node (controlling Primary Cell, PCell) sends a handover request to the target MN node (controlling target PCell) which in turn selects a secondary node (controlling target PSCell) and prepares it as part of the CHO preparation. When the CHO execution condition is met, the UE performs access to the target PCell and PSCell.

[0071] One of the main differences between the legacy HO and the CHO is the preparation of multiple target cells. In future, the CHO is expected to be used much more widely to make sure that the UE has a prepared target when the execution condition is met. This means that CHO reserves more resources at target cells than a legacy HO while waiting for the execution. 3 GPP has enabled mechanism to allow the target node to optimise the allocation, because it may be aware of each preparation that concerns the same UE.

[0072] In case of multiple preparations, each of the target Master Nodes (MNs) may prepare its own target Secondary Node (SN). Each target SN will therefore have to reserve the needed resources, too.

[0073] Since each of the target MNs receives the same measurements, it may well happen that they decide to prepare the same SN (especially if the cloud deployment makes the covered area of the SN wide). If this SN is the same as used in the source MN, the SN receives the UE ID allocated for the communication with the source MN and thus it may identify the preparations as related to the already known UE. Moreover, by comparing the SCG configurations, target SN is able to recognise that the target MNs has provided the same configuration for SN terminated bearers.

[0074] In the following, several embodiments will be described aiming to avoid forcing the SN to manage the same data coming via different paths.

[0075] Fig. 5a illustrates a signalling diagram according to an example embodiment. In this example there are two target MNs, namely Target MN 1 and Target MN 2, but in practical implementations the number of target MNs which may take part to the CHO, may be different from two, e.g. more than two. The UE detects a configured event, which triggers the UE to send a measurement report 501 to its current serving node e/gNB. In terms of the HO process, the currently serving node may be referred to as a source node. Based on this report, the source MN node prepares one or more candidate target nodes for the handover. The source MN node (controlling Primary Cell, PCell) sends a handover request 502 to one candidate target MN node (controlling target PCell) which in turn selects a target secondary node (controlling target PS Cell) and sends to it an Addition Request message 503. In this example the candidate target MN node is Target MN 1 at this stage but could also be the Target MN 2 or another target MN. The Addition Request message may comprise information of requested secondary cell group bearer configuration (SCG Config) including information of capabilities of the UE. The target SN examines the Addition Request message and decides 504 to prepare a PSCell 1 and provides a secondary cell group bearer configuration SCG Config 1. The target SN also provides 505 identification information of Tunnel Endpoints (TEIDs) for downlink data forwarding. The target SN then sends 506 an Addition Request Acknowledgement with SCG Config 1 to the target MN node.

[0076] The target MN 1 node generates 507 a first conditional hand over configuration (CHO 1 config) and includes the secondary cell group configuration 1 (SCG config 1) received from the target SN in the first conditional hand over configuration.

[0077] The target MN 1 node sends 508 a Handover Request Acknowledgement message to the source MN, which prepares and sends 509 an RRC Reconfiguration message to the UE. The RRC Reconfiguration message includes the first conditional hand over configuration.

[0078] A configured event may later trigger the UE to send 510 another measurement report to its current serving node e/gNB for possible handover. The current serving node then sends 511 a handover request to another target MN, such as the Target MN 2 of Fig. 5a. The target MN 2 node sends an Addition Request message 512 to the target SN. The Addition Request message may comprise information of requested secondary cell group bearer configuration and information of identity of the UE.

[0079] When the target SN has received the Addition Request message, the target SN examines from which target MN the message was received. Based on the examination, when the target SN detects that this Addition Request message 512 has been sent by a different target MN than the previous Addition Request message 503 (Target MN 2 in the example of Fig. 5a), the target SN may also compare a previous SCG configuration (e.g. SGC Config 1 prepared in step 504) with the SCG configuration of the Addition Request message 512. By comparing the SCG configurations, the target SN is able to recognise that the other target MN has provided the same configuration for SN terminated bearers but that it relates to the same UE and the same SCG bearer configuration for SN-terminated bearers. Therefore, the target SN decides 513 to prepare a PSCell 1 and provides the same secondary cell group bearer configuration SCG Config 1.

[0080] In other words, once the Addition Request message is received from the target MN 2 by the target SN with indication that the Addition Request message refers to a CHO, the target SN may use the included identifications of the UE (UE ID) and the source MN (MN ID) to check if the target SN has a PSCell prepared for this UE. If the target SN finds the PSCell prepared for this UE, the target SN may compare the existing SCG configuration with the SCG configuration associated with the request to verify 514 that the same data radio bearers (DRB) can be allocated in the new request. Once this is confirmed, the target SN may respond to the new Addition Request with TEIDs for DL data forwarding already allocated for the other request. The target SN then sends an Addition Request Acknowledgement 515 with SCG Config 1 to the target MN 2 node.

[0081] The target MN 2 node, from which the Addition Request message 512 was transmitted, generates 516 a second conditional hand over configuration (CHO config 2) and includes the secondary cell group configuration 1 (SCG config 1) received from the target SN in the first conditional hand over configuration.

[0082] The target MN 2 node sends 517 a Handover Request Acknowledgement message to the source MN, which prepares and sends 518 an RRC Reconfiguration message to the UE. The RRC Reconfiguration message includes the second conditional hand over configuration (CHO config 2).

[0083] According to an embodiment, the target SN, when it identifies that the Addition request is related to a preparation from another target MN, i.e. is related to the same UE and the same SCG config is provided for SN-terminated bearers, allocates the same TEIDs for this request.

[0084] According to an embodiment, when responding to the Addition Request to the target MN, the target SN may include an indication (e.g. a flag) to the Addition Request Acknowledgement message 515 that the target SN is going to share the allocated TEIDs for DL data forwarding with any other target MN, if there is a matching Addition Request. The matching Addition Request may be determined, for example, by examining whether it comprises inter alia identification of the same UE and the same SCG configuration than another Addition Request.

[0085] The target MN may then forward the TEIDs from the target SN to the source MN, either directly as the TEIDs for data forwarding (in case of direct data forwarding), or as additional information associated with the MN’s own TEIDs.

[0086] Fig. 5b illustrates a signalling diagram according to another example embodiment. Similar to the embodiment of Fig. 5a, the UE detects a configured event, which triggers the UE to send a measurement report 501 to its current serving node e/gNB. In terms of the HO process, the currently serving node may be referred to as a source node. Based on this report, the source MN node prepares one or more candidate target nodes for the handover. The source MN node (controlling Primary Cell, PCell) sends a handover request 502 to one candidate target MN node (controlling target PCell) which in turn selects a target secondary node (controlling target PS Cell) and sends to it an Addition Request message 503. The Addition Request message may comprise information of requested secondary cell group bearer configuration (SCG Config) including information of capabilities of the UE. The target SN examines the Addition Request message and decides 504 to prepare a PSCell 1 and provides a first secondary cell group bearer configuration SCG Config 1. The target SN also provides 505 identification information of Tunnel Endpoints (TEIDs) for downlink data forwarding. The target SN then sends 506 an Addition Request Acknowledgement with SCG Config 1 to the target MN node. [0087] The target MN node generates 507 a first conditional hand over configuration (CHO 1 config) and includes the first secondary cell group configuration 1 (SCG config 1) received from the target SN in the first conditional hand over configuration.

[0088] The target MN node sends 508 a Handover Request Acknowledgement message to the source MN, which prepares and sends 509 an RRC Reconfiguration message to the UE. The RRC Reconfiguration message includes the first conditional hand over configuration.

[0089] A configured event may later trigger the UE to send 510 another measurement report to its current serving node e/gNB for possible handover. The current serving node then sends 511 a handover request to another target MN, such as the Target MN 2 of Fig. 5b. The target MN node sends an Addition Request message 512 to the target SN. The Addition Request message may comprise information of requested secondary cell group bearer configuration and information of identity of the UE.

[0090] When the target SN has received the Addition Request message, the target SN examines from which target MN the message was received. Based on the examination, when the target SN detects that this Addition Request message 512 has been sent by a different target MN than the previous Addition Request message 503, the target SN may also compare a previous SCG configuration (e.g. SGC Config 1 prepared in step 504) with the SCG configuration of the Addition Request message 512. By comparing the SCG configurations, the target SN is able to recognise that the target MNs has provided the same configuration for SN terminated bearers but that it relates to the same UE and the same SCG bearer configuration for SN-terminated bearers. Therefore, the target SN decides 513 to prepare a PSCell 1 and provides the same secondary cell group bearer configuration SCG Config 1.

[0091] If the target SN finds the PSCell prepared for this UE and the existing SCG configuration corresponds with the SCG configuration associated with the request the target SN verifies 514 that the same data radio bearers (DRB) can be allocated in the new request. Once this is confirmed, the target SN may respond to the new Addition Request with TEIDs for DL data forwarding already allocated for the other request. The target SN then sends to the target MN node an Addition Request Acknowledgement 515 with SCG Config 1 and an indication that the TEIDs for DL data forwarding are shared with another target MN, or may be shared, if the indication is provided in advance. Shared data forwarding means that the target MNs forward the SN’s TEIDs to the source node, so that direct forwarding between the source node (source MN/or source SN) and target SN is enabled without having the packets to be intercepted by the target MN.

[0092] If the target MN node from which the Addition Request message 512 was transmitted, decides to enable direct data forwarding instead of indirect forwarding, the target MN node sends 519 the TEIDs of target SN to the source node, which may be the source MN or the source SN.

[0093] The target MN node also generates 520 a second conditional hand over configuration (CHO config 2) and includes the secondary cell group configuration 1 (SCG config 1) received from the target SN in the first conditional hand over configuration.

[0094] The target MN node sends 521 a Handover Request Acknowledgement message to the source MN included with the SCG config 1.

[0095] The source MN prepares and sends 522 an RRC Reconfiguration message to the UE. Also the RRC Reconfiguration message includes the second conditional hand over configuration (CHO config 2).

[0096] Fig. 5 c illustrates a signalling diagram according to yet another example embodiment. The procedures from 501 to 514 are similar to the embodiment of Fig. 5b. However, in this example embodiment of the disclosure, the target SN decides to share the allocated TEIDs for downlink data forwarding with any other target MN, if there is a matching Addition Request. Therefore, the target SN includes an indication such as a flag (e.g. 1 bit) to indicate the target MNs and the source SN about the shared allocated TEIDs. Hence, the target SN sends to the target MN node the Addition Request Acknowledgement 515 with SCG Config 1 and the indication that the TEIDs for DL data forwarding are shared with another target MN.

[0097] The target MN receives the Addition Request Acknowledgement with SCG Config 1 and the indication and based on the indication, in the process phase 519, the target MN decides to use indirect data forwarding instead of direct data forwarding. Hence, the target MN sends the TEIDs of the target MN to source node and includes also the TEIDs of the target SN.

[0098] The target MN node also generates 520 a second conditional hand over configuration (CHO config 2) and includes in the second conditional hand over configuration the first secondary cell group configuration 1 (SCG config 1) received from the target SN in the first conditional hand over configuration.

[0099] The target MN node sends 521 a Handover Request Acknowledgement message to the source MN included with the CHO config 2 and also the TEIDs of the target MN and the TEIDs of the target SN.

[0100] The source MN prepares and sends 522 an RRC Reconfiguration message to the UE. Also the RRC Reconfiguration message includes the second conditional hand over configuration (CHO config 2).

[0101] At step 523, Source MN is now able to start data forwarding towards target MN/SN, since data path is established between the source MN and the target MN/SN. If the source MN decides to start data forwarding after data path is established, it is called early data forwarding. Early data forwarding enables the network to reduce gap of user data transmission when UE actually changes into the cell of the target MN/SN since the user data is already available at the target MN/SN.

[0102] If the embodiment of Fig. 5a is used, and the target MNs use indirect forwarding, the source node (the source MN) is not aware that there is a single target SN behind the target MNs. The source node forwards then the same data to each target MN separately, and the target MNs forward it to the target SN. However, since the target SN uses the same target TEIDs, and since the forwarded data in case of intra-RAT HO is numbered, the target SN will be able to eliminate duplicated PDUs and keep a single DL buffer. However, once the source node is made aware that there is a single target SN behind different target MNs (either because the target MN apply direct forwarding or because allocated TEIDs are shared as explained above), it can forward the data once instead of copying it over multiple paths. In this case, even if the target MN over which data is forwarded is cancelled (CHO is cancelled there), the source node may switch to forwarding data over another target MN. Again, thanks to the PDU numbering and the single TEIDs at the target SN, the target SN will be able to assemble a single DL buffer. [0103] The source node, when receiving the same TEIDs from multiple target MNs will understand that there is a common destination for data forwarding and will forward the data only once. Finally, even if one or more of the target MNs prefers to use indirect forwarding, i.e. packets of target SN are sent first from the source node to the target MN which in turn forwards them to the target SN, the target MN may provide the target TEIDs from the target SN along with own TEIDs. When the source node receives two TEID from the target node, the source node may identify common destination for data forwarding by comparing the final TEIDs and thus the source node may forward the data only over one of the prepared target MNs.

[0104] In accordance with an embodiment, in order to avoid that the SN is forced to manage the same data coming via different paths, the target SN merges or fills or queues the received data into the same data buffer or path end. When the target SN identifies that the Addition request is related to a preparation from another target MN, i.e. is related to the same UE and the same SCG config is provided for SN-terminated bearers, the target SN allocates the same TEIDs for this Addition request.

[0105] When the target SN receives a data unit from any of the paths, such as from other gNB/MN/SN, the target SN examines a data buffer of the target SN to check whether that received data unit is already queued or otherwise available. If so, the target SN does not add this duplicated data unit into the data buffer or queue.

[0106] In accordance with an embodiment, the detection of duplicated data unit and possible deletion is executed in a network node before transmitting the data unit via air interface to the UE. [0107] In accordance with an embodiment, such a duplicate data unit may also be detected in the UE as well.

[0108] In the following, an enhanced method for conditional handover will be described in more detail, in accordance with various embodiments.

[0109] The method is disclosed in the flow chart of Fig. 6a as reflecting the operation of an access node, such as an e/gNB, wherein the method comprises receiving (600), by an access node, an addition request from a target master node with indication that the request refers to a conditional handover, said request comprising an identifier of a user equipment and an identifier of a source master node, using (602) the identifier of a user equipment and the identifier of a source master node to check if the access node has a controlling target primary cell prepared for this user equipment, comparing (604) an existing secondary group configuration with the secondary group configuration included in the request, verifying (606), based on the comparison, that a same data radio bearer can be allocated for the addition request, and responding (608) to the request with an identifier of a tunnel endpoint for downlink data forwarding already allocated for a previous addition request. [0110] Another method is disclosed in the flow chart of Fig. 6b as reflecting the operation of a source node, such as the source MN of Figs. 5a, 5b or 5c. The method comprises receiving (620), by the source node, a tunnel endpoint identifier of a first target MN and a first target tunnel endpoint identifier from the first target MN, receiving (622), by the source node, a tunnel endpoint identifier of a second target MN and a second target tunnel endpoint identifier from the second target MN, determining (624) that the first target tunnel endpoint identifier and the second target tunnel endpoint identifier correspond with each other, and deciding (626) to send data addressed to a target SN via only one of the first target MN and the second target MN.

[0111] Thus, in order to make the target SN aware that the preparation requests received from different MNs concern the same UE, the target SN shall be provided with an identification of the UE involved in the conditional handover process. The identification may be assigned e.g. by the source MN or the source SN, for example upon initiating the CHO process. The identification is shared with all potential target MNs, and therefore, upon receiving requests from a plurality of MNs to be included as a secondary node into a CHO process, the access node may immediately determine, based on the UE identifications included in the requests, if a plurality (i.e. two or more) of said requests concern the same UE. Accordingly, upon determining that multiple CHO preparation requests relate to the same UE, the access node may optimize its radio resource reservation when initiating its operation as a target SN.

[0112] According to an embodiment, the identification of the user equipment is unique among said master nodes.

[0113] Thus, when the source MN or the source SN assigns the identification to the UE, the identification will be shared with all potential target MNs. Therefore, all the target MN(s) shall be bound to use the same identification when dealing with any given target SN. In order to tell the difference of UEs associated with the requests coming from the MNs, as well as identify the requests relating to the same UE, the identification of the UE shall be unique among all target MNs involved in the CHO preparations.

[0114] According to an embodiment, the identification of the user equipment is temporary such that its validity is dependent on a preparation time for the conditional handover process.

[0115] Since the purpose of the identification of the UE is to facilitate the radio resource reservation process of an access node upon initiating its operation as a target SN in CHO process, only a temporary identification is needed for the UE. The validity time of the identification of the UE may be set e.g. as somewhat longer than the maximum CHO preparation time.

[0116] According to an embodiment, the identification of the user equipment is obtained from an Addition Request received from a master node. As a part of the Dual Connectivity handover process, the target MN sends an Addition Request to a potential target SN to notify it for the CHO preparations. Now the identification of the UE may be included in this existing request message sent from the target MN to the target SN.

[0117] According to an embodiment, the identification of the user equipment comprises an identification of a secondary node to a current serving node of the user equipment included in the Addition Request.

[0118] This embodiment is illustrated in the signalling diagram of Fig. 8a. It is noted that Fig. 8a shows only the initial stages of the CHO preparation signalling. Based e.g. on the measurement report from the UE, the source MN sends Conditional Handover Requests to two potential target MNs, Target MN1 and Target MN2. Both potential target MNs, Target MN1 and Target MN2, send an Addition Request to the access node, i.e. Target SN. The Addition Request includes a Xn UE AP ID, which uniquely identifies a logical connection associated to a UE over the Xn interface within an M-NG-RAN node (i.e. the source SN in this case) for dual connectivity, as defined in 3 GPP 38.401 Release- 16. [0119] Now the Xn UE AP ID in the Addition Request is provided with an identification of a secondary node to a current serving node of the user equipment, i.e. the identification of current Source SN of the UE (Source SN ID), which enables to the Target SN to identify, together with the Xn UE AP ID, the associated UE uniquely.

[0120] According to an embodiment, the identification of the user equipment further comprises an identification of the current serving node of the user equipment included in the Addition Request.

[0121] Thus, in addition to the identification of a secondary node to a current serving node of the user equipment, i.e. Source SN ID, the Addition Request is provided with the identification of the current serving node of the user equipment, the identification of current Source MN of the UE (Source MN ID). This is illustrated in the signalling diagram of Fig. 8b, which is otherwise similar to the signalling diagram of Fig. 8a, but the Addition Request further includes a Source MN ID.

[0122] According to an embodiment, the identification of the user equipment comprises an identification of the current serving node of the user equipment and the identification of the user equipment in the current serving node of the user equipment, both included in the Addition Request.

[0123] Thus, if the source MN uses the same Xn UE AP Id across all the interfaces, then the identification of the user equipment comprises the source MN ID and the Xn UE AP ID allocated in the source MN ID, both included in the Addition Request. In other words, the Addition Request is provided with the identification of the current serving node of the user equipment, i.e. the source MN ID, and the Xn UE AP ID allocated in the current serving node of the user equipment.

[0124] According to an embodiment, the identification of the user equipment comprises a random number, generated by the current serving node of the user equipment or the secondary node to a current serving node of the user equipment, included in the Addition Request.

[0125] Thus, instead of the Source SN ID, and possibly Source MN ID, a random number may be assigned to the UE at the source MN or source SN. The random number as the UE ID may be passed to all prepared target MNs which would then include it in the Addition Request towards a selected target SN. If the target SN receives the same number from different MNs, it may assume it concerns the same UE.

[0126] Both Conditional Handover Requests sent by the Source MN to the Target MNs and the Addition Requests sent by the Target MNs to the Target SN include an updated SCG configuration provided with the random number as the temporary UE ID.

[0127] It is noted that all the above solutions lead to the situation where the target SN is able to identify requests coming from different target MNs but concerning the same UE. [0128] The method and the embodiments related thereto may also be implemented in an apparatus implementing an access point or a base station of a radio access network, such as an eNB or a gNB. An apparatus, such as a gNB, according to an aspect comprises means for receiving requests from a plurality of master nodes to be included added as a secondary node into as part of a conditional handover process for a user equipment; means for obtaining, from each of said requests, an identification of the user equipment involved in the conditional handover process; and means for determining, based on said identifications of the user equipment, that a plurality of said requests concern the same user equipment.

[0129] According to an embodiment, the identification of the user equipment is unique among said master nodes.

[0130] According to an embodiment, the identification of the user equipment is temporary such that its validity is dependent on a preparation time for the conditional handover process.

[0131] According to an embodiment, the apparatus comprises means for obtaining the identification of the user equipment from an Addition Request received from a master node.

[0132] According to an embodiment, the identification of the user equipment comprises an identification of a secondary node to a current serving node of the user equipment included in the Addition Request. [0133] According to an embodiment, the identification of the user equipment further comprises an identification of the current serving node of the user equipment included in the Addition Request.

[0134] According to an embodiment, the identification of the user equipment comprises a random number, generated by the current serving node of the user equipment or the secondary node to a current serving node of the user equipment, included in the Addition Request.

[0135] According to an embodiment, the apparatus comprises means for generating a temporary identification for a Secondary Cell Group configuration; and means for including the temporary identification for the Secondary Cell Group configuration in acknowledgement messages to be sent to one or more of said plurality of master nodes. [0136] According to an embodiment, the apparatus comprises means for obtaining, from at least one of said master nodes, a request to release radio resources reserved for the user equipment by the apparatus in response to the master node receiving a conditional handover cancel request from the current serving node of the user equipment.

[0137] According to an embodiment, the conditional handover cancel request comprises the temporary identification for the Secondary Cell Group configuration.

[0138] An apparatus, such as an access point or a base station of a radio access network, e.g. an eNB or a gNB, according to a further aspect comprises at least one processor and at least one memory, said at least one memory stored with computer program code thereon, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: receive requests from a plurality of master nodes to be added as a secondary node as part of a conditional handover process for a user equipment; obtain, from each of said requests, an identification of the user equipment involved in the conditional handover process; and determine, based on said identifications of the user equipment, that a plurality of said requests concern the same user equipment.

[0139] Such apparatuses may comprise e.g. the functional units disclosed in Fig. 7 showing a simplified block diagram of a network node, i.e. the apparatus, according to the aspects and the related embodiments. It is noted that while the above embodiments are mainly disclosed in connection with a target Secondary Node (SN), the structure and functional units as disclosed in Fig. 7 are equally applicable in network node, such as in a source MN, a source SN and a target MN, as disclosed above.

[0140] The network node 1100 may be a base station, an access point, an access node, a gNB, a evolved NodeB (eNB), a server, a host, or any other network entity that may communicate with the UE.

[0141] The apparatus may include at least one processor or control unit or module 1102. At least one memory 1104 may be provided in the apparatus. The memory may include computer program instructions or computer code contained therein. One or more transceivers 1106 may be provided, and the apparatus may also include an antenna 1108, Although only one antenna each is shown, many antennas and multiple antenna elements may be provided to the apparatus. Other configurations of the apparatus, for example, may be provided. For example, in addition to wireless communication, the network node may be additionally configured for wired communication with the UE, and in such a case antenna 1108 may illustrate any form of communication hardware, without being limited to merely an antenna.

[0142] Transceiver 1106 may be a transmitter, a receiver, or both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception. The transmitter and/or receiver (as far as radio parts are concerned) may also be implemented as a remote radio head which is not located in the device itself, but in a mast, for example. The operations and functionalities may be performed in different entities, such as nodes, hosts or servers, in a flexible manner. In other words, division of labor may vary case by case. One possible use is to make a network node deliver local content. One or more functionalities may also be implemented as virtual application(s) in software that can run on a server.

[0143] In certain embodiments, the apparatus may comprise at least one processor and at least one memory including computer program code. The at least one memory including computer program code can be configured to, with the at least one processor, cause the apparatus at least to perform any of the processes described herein.

[0144] Processors 1102 may be embodied by any computational or data processing device, such as a central processing unit (CPU), digital signal processor (DSP), application specific integrated circuit (ASIC), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), digitally enhanced circuits, or comparable device or a combination thereof. The processors may be implemented as a single controller, or a plurality of controllers or processors.

[0145] For firmware or software, the implementation may include modules or unit of at least one chip set (for example, procedures, functions, and so on). The at least one memory 1104 may independently be any suitable storage device, such as a non-transitory computer- readable medium. A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memory may be combined on a single integrated circuit as the processor, or it may be separate therefrom. Furthermore, the computer program instructions may be stored in the memory and which may be processed by the processors can be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language. The memory or data storage entity is typically internal but may also be external or a combination thereof, such as in the case when additional memory capacity is obtained from a service provider. The memory may be fixed or removable.

[0146] The memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus such as network node 1100, to perform any of the processes described above. Therefore, in certain embodiments, a non-transitory computer-readable medium may be encoded with instructions or one or more computer program (such as added or updated software routine, applet or macro) that, when executed in hardware, may perform a process such as one of the processes described herein. In other embodiments, a computer program product may encode instructions for performing any of the processes described above, or a computer program product embodied in a non-transitory computer-readable medium and encoding instructions that, when executed in hardware, perform any of the processes describes above. Computer programs may be coded by a programming language, which may be a high-level programming language, such as objective-C, C, C++, C#, Java, etc., or a low-level programming language, such as a machine language, or assembler. Alternatively, certain embodiments may be performed entirely in hardware.

[0147] According to an embodiment, a computer program comprises instructions stored thereon for causing an apparatus to perform at least the following: receive an addition request from a target master node with an indication that the request refers to a conditional handover, said request comprising an identifier of a user equipment and an identifier of a source master node; use the identifier of the user equipment and the identifier of the source master node to check, if the apparatus has a controlling target primary cell prepared for this user equipment; compare an existing secondary group configuration with a secondary group configuration included in the request; verify, based on the comparison, that a same data radio bearer can be allocated for the addition request; and respond to the request with an identifier of a tunnel endpoint for downlink data forwarding, which have already been allocated for a previous addition request.

[0148] According to an embodiment, a computer program comprises instructions stored thereon for causing an apparatus to perform at least the following: receive a tunnel endpoint identifier of a first target master node and a first target tunnel endpoint identifier from the first target master node; receive a tunnel endpoint identifier of a second target master node and a second target tunnel endpoint identifier from the second target master node; determine that the first target tunnel endpoint identifier and the second target tunnel endpoint identifier correspond with each other; and decide to send data addressed to a target secondary node via only one of the first target master node and the second target master node.

[0149] According to an embodiment, a computer program comprises instructions stored thereon for causing an apparatus to perform at least the following: send an addition request related to a conditional handover to a target secondary node, the addition request comprising information of requested secondary cell group bearer configuration and information of identity of a user equipment; receive an addition request acknowledgement from the target secondary node, the addition request acknowledgement comprising a secondary cell group configuration and an indication that an identifier of a tunnel endpoint allocated by the target secondary node for downlink data is shared with another target master node; based on the indication decide to use indirect data forwarding; and send an identifier of a tunnel endpoint of the apparatus and the shared identifier of the tunnel endpoint allocated by the target secondary node for downlink data to a source master node. [0150] In certain embodiments, an apparatus may include circuitry configured to perform any of the processes or functions illustrated above. Circuitry, in one example, may be hardware-only circuit implementations, such as analog and/or digital circuitry.

Circuitry, in another example, may be a combination of hardware circuits and software, such as a combination of analog and/or digital hardware circuit(s) with software or firmware, and/or any portions of hardware processor(s) with software (including digital signal processor(s)), software, and at least one memory that work together to cause an apparatus to perform various processes or functions. In yet another example, circuitry may be hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that include software, such as firmware for operation. Software in circuitry may not be present when it is not needed for the operation of the hardware.

[0151] Specific examples of circuitry may be content coding circuitry, content decoding circuitry, processing circuitry, image generation circuitry, data analysis circuitry, or discrete circuitry. The term circuitry may also be, for example, a baseband integrated circuit or processor integrated circuit for a mobile device, a network entity, or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0152] A further aspect relates to a computer program product, stored on a non- transitory memory medium, comprising computer program code, which when executed by at least one processor, causes an apparatus at least to perform: receive requests from a plurality of master nodes to be added as a secondary node as part of a conditional handover process for a user equipment; obtain, from each of said requests, an identification of the user equipment involved in the conditional handover process; and determine, based on said identifications of the user equipment, that a plurality of said requests concern the same user equipment.

[0153] In general, the various embodiments of the invention may be implemented in hardware or special purpose circuits or any combination thereof. While various aspects of the invention may be illustrated and described as block diagrams or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof. [0154] Embodiments of the inventions may be practiced in various components such as integrated circuit modules. The design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

[0155] Programs, such as those provided by Synopsys, Inc. of Mountain View, California and Cadence Design, of San Jose, California automatically route conductors and locate components on a semiconductor chip using well established rules of design as well as libraries of pre stored design modules. Once the design for a semiconductor circuit has been completed, the resultant design, in a standardized electronic format (e.g., Opus, GDSII, or the like) may be transmitted to a semiconductor fabrication facility or "fab" for fabrication.

[0156] The foregoing description has provided by way of exemplary and non-limiting examples a full and informative description of the exemplary embodiment of this invention. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended examples. However, all such and similar modifications of the teachings of this invention will still fall within the scope of this invention.

Claims

1. An apparatus comprising at least one processor and at least one memory, said at least one memory stored with computer program code thereon, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: receive an addition request from a target master node with an indication that the request refers to a conditional handover, said request comprising an identifier of a user equipment and an identifier of a source master node; use the identifier of the user equipment and the identifier of the source master node to check, if the apparatus has a controlling target primary cell prepared for this user equipment; compare an existing secondary group configuration with a secondary group configuration included in the request; verify, based on the comparison, that a same data radio bearer can be allocated for the addition request; and respond to the request with an identifier of a tunnel endpoint for downlink data forwarding, which have already been allocated for a previous addition request.

2. The apparatus according to claim 1, comprising computer program code configured to cause the apparatus to perform: identifying that the addition request is related to a preparation from another master node; and allocating the same identifier of a tunnel endpoint for the addition request.

3. The apparatus according to claim 1 or 2, comprising computer program code configured to cause the apparatus to perform: responding to the addition request to the target master node by including an indication to an addition request acknowledgement message that the target secondary node is going to share the allocated identifiers of the tunnel endpoints for downlink data forwarding with any other target master node, if there is a matching addition request.

4. The apparatus according to claim 3, comprising computer program code configured to cause the apparatus to determine the matching addition request by: examining whether the addition requests comprise identification of the same user equipment and the same secondary cell group configuration.

5. The apparatus according to any of the claims 1 to 4, comprising computer program code configured to cause the apparatus to perform: allocating only a single buffer for downlink data; and associate the identifier of the tunnel endpoint with the single buffer.

6. A method comprising: receiving an addition request from a target master node with an indication that the request refers to a conditional handover, said request comprising an identifier of a user equipment and an identifier of a source master node; using the identifier of the user equipment and the identifier of the source master node to check, if the apparatus has a controlling target primary cell prepared for this user equipment; comparing an existing secondary group configuration with a secondary group configuration included in the request; verifying, based on the comparison, that a same data radio bearer can be allocated for the addition request; and responding to the request with an identifier of a tunnel endpoint for downlink data forwarding, which have already been allocated for a previous addition request.

7. An apparatus comprising at least one processor and at least one memory, said at least one memory stored with computer program code thereon, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: receive a tunnel endpoint identifier of a first target master node and a first target tunnel endpoint identifier from the first target master node; receive a tunnel endpoint identifier of a second target master node and a second target tunnel endpoint identifier from the second target master node; determine that the first target tunnel endpoint identifier and the second target tunnel endpoint identifier correspond with each other; and decide to send data addressed to a target secondary node via only one of the first target master node and the second target master node.

8. The apparatus according to claim 7, comprising computer program code configured to cause the apparatus to perform: receive two tunnel endpoint identifiers from one of the first target master node and the second target master node; compare the two tunnel endpoint identifiers; based on the comparison, identify common destination for data forwarding; and forward data targeted to the common destination only over one of the first target master node and the second target master node.

9. A method comprising: receiving, by a source node, a tunnel endpoint identifier of a first target master node and a first target tunnel endpoint identifier from the first target master node; receiving, by the source node, a tunnel endpoint identifier of a second target master node and a second target tunnel endpoint identifier from the second target master node; determining, by the source node, that the first target tunnel endpoint identifier and the second target tunnel endpoint identifier correspond with each other; and deciding, by the source node, to send data addressed to a target secondary node via only one of the first target master node and the second target master node.

10. An apparatus comprising at least one processor and at least one memory, said at least one memory stored with computer program code thereon, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: send an addition request related to a conditional handover to a target secondary node, the addition request comprising information of requested secondary cell group bearer configuration and information of identity of a user equipment; receive an addition request acknowledgement from the target secondary node, the addition request acknowledgement comprising a secondary cell group configuration and an indication that an identifier of a tunnel endpoint allocated by the target secondary node for downlink data is shared with another target master node; based on the indication decide to perform one of the following: use indirect data forwarding and send an identifier of a tunnel endpoint of the apparatus and the shared identifier of the tunnel endpoint allocated by the target secondary node for downlink data to a source master node, or use direct data forwarding and send an identifier of the shared identifier of the tunnel endpoint allocated by the target secondary node for downlink data to a source master node.

11. The apparatus according to claim 10, comprising computer program code configured to cause the apparatus to perform: generating a second conditional hand over configuration; and including in the second conditional hand over configuration the secondary cell group configuration.

12. The apparatus according to claim 11, comprising computer program code configured to cause the apparatus to perform: sending a handover request acknowledgement message to the source MN included with the second conditional hand over configuration and the identifier of the tunnel endpoint of the apparatus and the identifier of a tunnel endpoint of the target secondary node.

13. The apparatus according to any of the claims 10 to 12, comprising computer program code configured to cause the apparatus to perform: forwarding packets between the source master node and the target secondary node without intercepting the packets.

14. A method comprising: sending an addition request related to a conditional handover to a target secondary node, the addition request comprising information of requested secondary cell group bearer configuration and information of identity of a user equipment; receiving an addition request acknowledgement from the target secondary node, the addition request acknowledgement comprising a secondary cell group configuration and an indication that an identifier of a tunnel endpoint allocated by the target secondary node for downlink data is shared with another target master node; based on the indication deciding to use indirect data forwarding; sending an identifier of a tunnel endpoint of the apparatus and the shared identifier of the tunnel endpoint allocated by the target secondary node for downlink data to a source master node.

15. A computer program comprising instructions stored thereon for causing an apparatus to perform at least the following: receive an addition request from a target master node with an indication that the request refers to a conditional handover, said request comprising an identifier of a user equipment and an identifier of a source master node; use the identifier of the user equipment and the identifier of the source master node to check, if the apparatus has a controlling target primary cell prepared for this user equipment; compare an existing secondary group configuration with a secondary group configuration included in the request; verify, based on the comparison, that a same data radio bearer can be allocated for the addition request; and respond to the request with an identifier of a tunnel endpoint for downlink data forwarding, which have already been allocated for a previous addition request.

16. A computer program comprising instructions stored thereon for causing an apparatus to perform at least the following: receive a tunnel endpoint identifier of a first target master node and a first target tunnel endpoint identifier from the first target master node; receive a tunnel endpoint identifier of a second target master node and a second target tunnel endpoint identifier from the second target master node; determine that the first target tunnel endpoint identifier and the second target tunnel endpoint identifier correspond with each other; and decide to send data addressed to a target secondary node via only one of the first target master node and the second target master node.

17. A computer program comprising instructions stored thereon for performing at least the following: send an addition request related to a conditional handover to a target secondary node, the addition request comprising information of requested secondary cell group bearer configuration and information of identity of a user equipment; receive an addition request acknowledgement from the target secondary node, the addition request acknowledgement comprising a secondary cell group configuration and an indication that an identifier of a tunnel endpoint allocated by the target secondary node for downlink data is shared with another target master node; based on the indication decide to use indirect data forwarding; send an identifier of a tunnel endpoint of the apparatus and the shared identifier of the tunnel endpoint allocated by the target secondary node for downlink data to a source master node.