Handover in multiple orbit non-terrestrial networks
The transitional handover method in multiple orbit NTN systems addresses service continuity issues by allowing data transmissions during a transition period with a higher orbit cell, ensuring minimal interruption and maintaining quality of service for high-speed users.
Patent Information
- Application Number
- PCT/CN2025/094501
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-13
- Publication Date
- 2026-11-19
AI Technical Summary
Existing handover mechanisms in multiple orbit non-terrestrial networks (NTN) fail to provide seamless service continuity with minimal interruption, particularly for high-speed mobile broadband users like ships and aircraft, due to significant differences in link budgets and coverage gaps between low-earth orbit (LEO) and higher orbits like medium-earth orbit (MEO) or geosynchronous earth orbit (GEO).
A transitional handover approach is implemented, where a terminal device receives configurations for handovers to both a first and second target cells, performing data transmissions during a transition period with a higher orbit cell to maintain service continuity for delay-sensitive traffic, and subsequently switching to a lower orbit cell, thereby minimizing additional handovers and protocol overhead.
This approach ensures minimal service interruption and maintains quality of service for high-speed mobile broadband users by optimizing handovers between different satellite orbits, reducing the need for additional handovers and associated delays.
Smart Images

Figure CN2025094501_19112026_PF_FP_ABST
Abstract
Description
HANDOVER IN MULTIPLE ORBIT NON-TERRESTRIAL NETWORKSFIELD
[0001] Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices, apparatuses and computer readable storage medium for handover (HO) in multiple orbit non-terrestrial networks (NTN) .BACKGROUND
[0002] Currently, NTN networks comprised of multiple satellites operating on different earth orbits are widely used. Each satellite may cover certain areas to provide network services for the user.SUMMARY
[0003] In a first aspect of the present disclosure, there is provided an apparatus. The apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from a first network device managing a source cell of the apparatus, a first handover configuration for a first handover procedure of the apparatus to a first target cell managed by a second network device and a second handover configuration for a second handover procedure of the apparatus to a second target cell managed by a third network device, wherein the second handover configuration indicates a transition period within which the apparatus is to be served by the second target cell; perform, after a completion of the second handover procedure to the second target cell and based on the second handover configuration, data transmissions of a set of quality of service (QoS) flows or data radio bearers (DRBs) with the third network device during the transition period; in accordance with a determination that at least one condition for the first handover procedure is met during the transition period, perform the first handover procedure to the first target cell; and perform, after a completion of the first handover procedure to the first target cell and based on the first handover configuration, data transmissions of a further set of QoS flows or DRBs with the second network device, wherein the set of QoS flows or DRBs are comprised in the further set of QoS flows or DRBs.
[0004] In a second aspect of the present disclosure, there is provided an apparatus. The apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: determine a first handover procedure of a terminal device to a first target cell managed by a second network device and a second handover procedure of the terminal device to a second target cell managed by a third network device are to be performed, wherein the second handover procedure is for a transition period within which the terminal device is to be served by the second target cell; perform, based on the determination, handover preparation with the second network device and the third network device to obtain a first handover configuration for the first handover procedure and a second handover configuration for the second handover procedure; and transmit the first and the second handover configurations to the terminal device.
[0005] In a third aspect of the present disclosure, there is provided an apparatus. The apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from a first network device, a HO request for a second handover procedure of a terminal device to a second target cell managed by the apparatus, wherein the HO request indicates that the second handover procedure is for a transition period within which the terminal device is to be served by the second target cell; and transmit, to the first network device, a HO acknowledgement in response to the HO request, at least indicating the transition period granted for the terminal device, wherein the terminal device is allowed to be served by the second target cell within the transition period.
[0006] In a fourth aspect of the present disclosure, there is provided a method. The method comprises: receiving, by a terminal device from a first network device managing a source cell of the terminal device, a first handover configuration for a first handover procedure of the terminal device to a first target cell managed by a second network device and a second handover configuration for a second handover procedure of the terminal device to a second target cell managed by a third network device, wherein the second handover configuration indicates a transition period within which the terminal device is to be served by the second target cell; performing, after a completion of the second handover procedure to the second target cell and based on the second handover configuration, data transmissions of a set of QoS flows or DRBs with the third network device during the transition period; in accordance with a determination that at least one condition for the first handover procedure is met during the transition period, performing the first handover procedure to the first target cell; and performing, after a completion of the first handover procedure to the first target cell and based on the first handover configuration, data transmissions of a further set of QoS flows or DRBs with the second network device, wherein the set of QoS flows or DRBs are comprised in the further set of QoS flows or DRBs.
[0007] In a fifth aspect of the present disclosure, there is provided a method. The method comprises: determining, by a first network device, a first handover procedure of a terminal device to a first target cell managed by a second network device and a second handover procedure of the terminal device to a second target cell managed by a third network device are to be performed, wherein the second handover procedure is for a transition period within which the terminal device is to be served by the second target cell; performing, based on the determination, handover preparation with the second network device and the third network device to obtain a first handover configuration for the first handover procedure and a second handover configuration for the second handover procedure; and transmitting the first and the second handover configurations to the terminal device.
[0008] In a sixth aspect of the present disclosure, there is provided a method. The method comprises: receiving, by a third network device from a first network device, a HO request for a second handover procedure of a terminal device to a second target cell managed by the third network device, wherein the HO request indicates that the second handover procedure is for a transition period within which the terminal device is to be served by the second target cell; and transmitting, to the first network device, a HO acknowledgement in response to the HO request, at least indicating the transition period granted for the terminal device, wherein the terminal device is allowed to be served by the second target cell within the transition period.
[0009] In a seventh aspect of the present disclosure, there is provided an apparatus. The apparatus comprises means for receiving, from a first network device managing a source cell of the apparatus, a first handover configuration for a first handover procedure of the apparatus to a first target cell managed by a second network device and a second handover configuration for a second handover procedure of the apparatus to a second target cell managed by a third network device, wherein the second handover configuration indicates a transition period within which the apparatus is to be served by the second target cell; means for performing, after a completion of the second handover procedure to the second target cell and based on the second handover configuration, data transmissions of a set of QoS flows or DRBs with the third network device during the transition period; means for in accordance with a determination that at least one condition for the first handover procedure is met during the transition period, performing the first handover procedure to the first target cell; and means for performing, after a completion of the first handover procedure to the first target cell and based on the first handover configuration, data transmissions of a further set of QoS flows or DRBs with the second network device, wherein the set of QoS flows or DRBs are comprised in the further set of QoS flows or DRBs.
[0010] In an eighth aspect of the present disclosure, there is provided an apparatus. The apparatus comprises means for determining a first handover procedure of a terminal device to a first target cell managed by a second network device and a second handover procedure of the terminal device to a second target cell managed by a third network device are to be performed, wherein the second handover procedure is for a transition period within which the terminal device is to be served by the second target cell; means for performing, based on the determination, handover preparation with the second network device and the third network device to obtain a first handover configuration for the first handover procedure and a second handover configuration for the second handover procedure; and means for transmitting the first and the second handover configurations to the terminal device.
[0011] In a ninth aspect of the present disclosure, there is provided an apparatus. The apparatus comprises means for receiving, from a first network device, a HO request for a second handover procedure of a terminal device to a second target cell managed by the apparatus, wherein the HO request indicates that the second handover procedure is for a transition period within which the terminal device is to be served by the second target cell; and means for transmitting, to the first network device, a HO acknowledgement in response to the HO request, at least indicating the transition period granted for the terminal device, wherein the terminal device is allowed to be served by the second target cell within the transition period.
[0012] In a tenth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fourth aspect.
[0013] In an eleventh aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fifth aspect.
[0014] In a twelfth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the sixth aspect.
[0015] It is to be understood that the Summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS
[0016] Some example embodiments will now be described with reference to the accompanying drawings, where:
[0017] FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;
[0018] FIG. 2 illustrates examples of service continuity through multi-orbit satellite access;
[0019] FIG. 3 illustrates an example of a transitional handover in accordance with some example embodiments of the present disclosure;
[0020] FIG. 4 illustrates a signaling chart according to some example embodiments of the present disclosure;
[0021] FIG. 5 illustrates a signaling chart according to some example embodiments of the present disclosure;
[0022] FIG. 6 illustrates a flowchart of a method implemented at an apparatus in accordance with some example embodiments of the present disclosure;
[0023] FIG. 7 illustrates a flowchart of a method implemented at an apparatus in accordance with some example embodiments of the present disclosure;
[0024] FIG. 8 illustrates a flowchart of a method implemented at an apparatus in accordance with some example embodiments of the present disclosure;
[0025] FIG. 9 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and
[0026] FIG. 10 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.
[0027] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION
[0028] Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.
[0029] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0030] References in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
[0031] It shall be understood that although the terms “first, ” “second, ” …, etc. in front of noun (s) and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another and they do not limit the order of the noun (s) . For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.
[0032] As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or” , mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0033] As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included.
[0034] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and / or “including” , when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.
[0035] As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable) : (i) a combination of analog and / or digital hardware circuit (s) with software / firmware and (ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[0036] As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in analog, digital and / or quantum circuitry) and (b) combinations of hardware circuit (s) and software, such as (as applicable) : (i) a combination of analog, digital and / or quantum hardware circuit (s) with software / firmware and (ii) any or all portions of hardware processor (s) (including digital and / or quantum signal processor (s) ) with software, and memory (ies) that work together to cause an apparatus, such as a mobile device, computing device, or server, to perform various functions) and (c) any or all portions of hardware circuit (s) , such as a microprocessor (s) , processor (s) , and / or quantum processor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[0037] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR) , Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , 5.5G, the sixth generation (6G) communication protocols, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.
[0038] As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , an NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node. An IAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.
[0039] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) . The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. The terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node) . In the following description, the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.
[0040] As used herein, the term “resource, ” “transmission resource, ” “resource block, ” “physical resource block” (PRB) , “uplink resource, ” or “downlink resource” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other combination of the time, frequency, space and / or code domain resource enabling a communication, and the like. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
[0041] FIG. 1 illustrates an example communication network 100 in which example embodiments of the present disclosure can be implemented. As shown in FIG. 1, the communication network 100 may comprise a terminal device 110 which may also be, for example, a UE.
[0042] The communication network 100 may further comprise a first network device 120, a second network device 130 and a third network device 140, which may be, for example, considered as being included in some device operating in the network. In some example embodiments, these devices may be discussed as a BS, a gNB, or an eNB.
[0043] A serving area provided by the first network device 120 is called a cell. The first network device 120 may provide one or more cells serving the terminal device 110. For example, the terminal device 110 may communicate with the first network device 120 within the cell 102. In some scenarios, the cell 102 may be considered as a cell that is serving the terminal device 110.
[0044] In the following, for the purpose of illustration, in some example embodiments, operations described in connection with a terminal device may be implemented at a network device or other device, and operations described in connection with a network device may be implemented at a terminal device or other device.
[0045] In some example embodiments, if the terminal device 110 is a terminal device and the first network device 120 or a second network device 130 or a third network device 140 is a network device, a link from the first network device 120 or a second network device 130 or a third network device 140 to terminal device 110 is referred to as a downlink (DL) , while a link from the terminal device 110 to the first network device 120 or a second network device 130 or a third network device 140 is referred to as an UL. In DL, the first network device 120 or a second network device 130 or a third network device 140 is a transmitting (TX) apparatus (or a transmitter) and the terminal device 110 is a receiving (RX) apparatus (or a receiver) . In UL, the terminal device 110 is a TX apparatus (or a transmitter) and the first network device 120 or a second network device 130 or a third network device 140 is an RX apparatus (or a receiver) .
[0046] It is to be understood that the number of devices and their connections shown in FIG. 1 are only for the purpose of illustration without suggesting any limitation. The communication environment 100 may include any suitable number of devices configured to implementing example embodiments of the present disclosure. Although not shown, it would be appreciated that one or more additional devices may be located in the cell 102, and one or more additional cells may be deployed in the communication environment 100. It is noted that although illustrated as a network device, the first network device 120 or a second network device 130 or a third network device 140 may be another device than a network device. Although illustrated as a terminal device, the terminal device 110 may be another device than a terminal device.
[0047] Communications in the communication environment 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA) , Frequency Division Multiple Access (FDMA) , Time Division Multiple Access (TDMA) , Frequency Division Duplex (FDD) , Time Division Duplex (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiple (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.
[0048] In some discussed schemes, support of service continuity with minimized service interruption in multi-orbit non terrestrial network (NTN) has been discussed, where the scheme describes a number of potential use cases and related service requirements for NTN.
[0049] In some other discussed schemes, support for service continuity with minimized service interruption for on-the-ground mobile broadband (MBB) user such as UE on a ship and on-the-air MBB user such as UE on an aircraft has been discussed, the users in those cases may access the NTN through a multi-orbit satellite access.
[0050] Reference is now made to FIG. 2, which shows examples of service continuity through multi-orbit satellite access.
[0051] As shown in block 250 in FIG. 2, at T1, a device A 205 is in the coverage area of both the (low-earth orbit satellite) LEO Sat-A 210 and the (medium-earth orbit / geosynchronous orbit satellite) MEO / GEO Sat-B 215 at T1. In this situation, the device A 205 may choose to establish a link to the LEO Sat-A 210 since LEO access is preferred for providing MBB services due to significantly better link budget, compared to MEO or GEO orbit.
[0052] However, the UE in LEO orbit may suffer from discontinuities or gaps in coverage and thus there may be a need to hand the UE over to higher-orbit SAT and then back to LEO from time to time to overcome the coverage gap issue of LEO while using LEO as much as possible for MBB services.
[0053] As shown in block 260 in FIG. 2, the device A 205 moves to a new location at T2, at this location, the device A 205 is no longer in the coverage area of the LEO Sat-A 210. Therefore, the device A 205 may establish a connection with the MEO / GEO Sat-B 215.
[0054] At T3, which is shown at block 270 in FIG. 2, the device A 205 moves to the coverage area of the LEO Sat-C 220, then a handover process is performed, the device A 205 establishes a connection with the LEO Sat-C 220.
[0055] Depending on deployment of LEO and mobility of the UE, there are cases where coverage gap of LEO may be considerably large, i.e., lasting for considerable time in the order of minutes, as seen from UE perspective. This may be applied for the examples shown in FIG. 2 for certain use cases considering limited number of SATs deployed for LEO orbit and maritime UE such as ship, referred to as low-altitude UE. Then there are cases where the coverage gap of LEO may be rather short, in the order of seconds. This may also be applied for some other use cases considering aircraft UE, which may be referred to as high-altitude UE.
[0056] HO mechanisms specified in some discussed schemes for NTN may be applied in general for handing over the UE from a cell in LEO orbit, shortly LEO, to a cell in higher-orbit, shortly higher-orbit, and then back to LEO to overcome the coverage gap issue of LEO. This may be sufficient in case the coverage gap of LEO is lasting for considerable time, as in examples with low-altitude UE mentioned above.
[0057] Some discussed schemes considered the concept of using a preconfigured chain of conditional handovers (CHOs) for UE with predictable mobility in NTN. This concept neither considered the coverage gap issue of LEO nor inter-orbit handover (HO) . That is, the chain of CHOs is effective in case data traffic of the UE remains the same and all the target cells or target satellites (SATs) are able to handle the data traffic of the UE and provide and maintain configuration and resource allocation for the UE throughout the chain of CHOs. This may not be the case with MBB and inter-orbit HO in general, as MBB may be rather dynamic and there may be significant imbalance or difference between link budgets, capabilities or capacities of LEO and higher orbit.
[0058] Based on the above discussion, there are several issues related to the HO and coverage problem. The inter-orbit HO between LEO and higher-orbit is needed for providing service continuity with minimum service interruption for the UE due to the coverage-gap issue of LEO.
[0059] There is a significant difference between link budgets of LEO and higher orbit. Thus, HO of the UE with high-speed MBB connection, such as UE providing backhaul internet connection for ship or aircraft in some use cases as discussed above, from LEO to higher orbit may result in service degradation or interruption affecting passengers’ UEs on board of ship or aircraft. That is, as link budget of the higher-orbit may be rather limited, the target cell on the higher-orbit may not be able to accommodate all ongoing traffic of the UE and / or maintaining Quality of Service (QoS) that is currently provided by the source cell in the LEO orbit for at least a subset of QoS flows or data radio bearer (DRBs) of the UE.
[0060] The target cell therefore may not admit a subset of QoS flows or DRBs causing the UE to drop those QoS flows or DRBs, or reconfigure a subset of QoS flows or DRBs with degraded QoS causing QoS degradation.
[0061] There are cases where the coverage gap of LEO is rather short that may be tolerable for at least a subset of QoS flows or DRBs of the UE which carry, e.g., delay-tolerable non-real-time data traffic. However, the coverage gap may still cause service interruption for another subset of QoS flows or DRBs of the UE which carry, e.g., delay-sensitive real-time data traffic.
[0062] Thus, the problem is how to address the issues identified in the above observations for the UE to which a high-speed MBB connection needs to be provided and maintained. Then, optimizing protocol overhead for handling frequent back-and-forth HOs between LEO and higher orbit is also beneficial.
[0063] In accordance with some example embodiments of the present disclosure, there is provided a solution for transitional handover in multiple orbit NTN. In this solution, the terminal device 110 receives, from a first network device 120 managing a source cell of the apparatus (i.e., the terminal device 110) , a first handover configuration for a first handover procedure of the apparatus to a first target cell managed by a second network device 130 and a second handover configuration for a second handover procedure of the terminal device 110 to a second target cell managed by a third network device 140. The terminal device 110 performs, after a completion of the second handover procedure to the second target cell and based on the second handover configuration, data transmissions of a set of quality of service (QoS) flows or data radio bearers (DRBs) with the third network device 140 during a transition period within which the terminal device 110 is served by the second target cell. If the terminal device 110 determines that at least one condition for the first handover procedure is met, the terminal device 110 notifies, to the third network device 140, the first handover procedure is to be performed. The terminal device 110 performs, after a completion of the first handover procedure to the first target cell and based on the first handover configuration, data transmissions of a further set of QoS flows or DRBs with the second network device 130. The set of QoS flows or DRBs are comprised in the further set of QoS flows or DRBs.
[0064] In this way, the service continuity with minimized service interruption can be provided and maintained for the terminal device 110 with the assistance of the transitional handover (HO) to the second target cell in higher orbit for the set of QoS flows or DRBs carrying more delay sensitive traffic.
[0065] The embodiments of the present disclosure can also avoid another inter-orbit HO control / mobility management procedure back to LEO from the second target cell in higher orbit, which helps reducing overhead as well as delay that may have been caused by using a second inter-orbit HO from higher orbit back to LEO.
[0066] Example embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.
[0067] Reference is now made to FIG. 3, which shows an example of a transitional handover (THO) in accordance with some example embodiments of the present disclosure. The scenario shown in FIG. 3 shows the general concept of the proposed solutions.
[0068] As shown in FIG. 3, a HO scheme is illustrated. The handover may be initiated by a source cell 350 (provided by satellite 320) for a terminal device 110 comprising a first conditional handover (CHO) for a first set of QoS flows or DRBs of the terminal device 110 to a first target cell 370 (provided by the satellite 340) in the same orbit and a second CHO for a second set of QoS flows or DRBs of the terminal device 110 to a second target cell 360 (provided by the satellite 330) in higher orbit. The orbit herein may comprise a LEO for lower orbit, a MEO / GEO for higher orbit, and the apparatus providing the cell may be deployed in a high-altitude platform system (HAPS) .
[0069] In this situation, the second set of QoS flows or DRBs may be a subset of the first set of QoS flows or DRBs. The second set of QoS flows or DRBs is corresponding to the set of QoS flows or DRBs and the first set of QoS flows or DRBs is corresponding to the further set of QoS flows or DRBs. The second set of QoS flows or DRBs has stringent service continuity requirements. The second target cell 360 may provide a reduced set of functions or services to the terminal device 110 during a transition period 380, excluding at least functions and services related to mobility management for the terminal device 110.
[0070] In some embodiments, the second CHO may be associated with the transition period 380 of time, which may also be referred to as transition time.
[0071] The transition period 380 may be utilized to fill the coverage gap between the source cell 350 and the first target cell 370 in LEO orbit in order to meet QoS requirements and therefore maintain service continuity for the second set of QoS flows or DRBs. The second CHO may be executed before the first CHO and also referred to as a transitional HO. The transition period may start upon the terminal device 110 completing the execution of the second CHO with the second target cell 360.
[0072] In some scenarios, the first CHO may be executed during the transition period 380 while the terminal device 110 is being served by the second target cell 360.
[0073] Reference is now made to FIG. 4, which shows a signaling chart 400 for communication according to some example embodiments of the present disclosure. As shown in FIG. 4, the signaling chart 400 involves a terminal device 110, a first network device 120, a second network device 130 and a third network device 140. For the purpose of discussion, reference is made to FIG. 1 to describe the signaling chart 400.
[0074] FIG. 4 shows a general process of the first handover procedure and the second handover procedure according to some embodiments of the present disclosure.
[0075] As shown in FIG. 4, the first network device 120 may determine (405) a first handover procedure of a terminal device 110 (for example, from a source cell managed by the first network device 120) to a first target cell managed by a second network device 130 and a second handover procedure of the terminal device 110 to a second target cell managed by a third network device 140 are to be performed for maintaining service continuity or minimizing service interruption for the terminal device.
[0076] In some embodiments, the determination may be based on information obtained by the first network device 120. For example, the first network device 120 may determine the first handover procedure and the second handover procedure are to be performed based on cell coverage related information.
[0077] In some embodiments, the cell coverage related information may comprise mobility and location information associated with the terminal device 110 based on the measurement information, or coverage and neighboring cell information associated with the second network device 130 and the third network device 140 based on operation, administration, and maintenance (OAM) information.
[0078] In some examples, the cell coverage related information may comprise measurement information associated with the terminal device 110. In some other examples, the cell coverage related information may comprise OAM information.
[0079] Based on the above-mentioned information, the first network device 120 determines whether the first handover procedure and the second handover procedure may be performed. The two handovers mentioned herein may comprise different procedures involving different network devices.
[0080] For example, the first handover procedure may comprise a switch of the serving cell for the first apparatus 110. In the first handover procedure, the serving cell of the first apparatus 110 may be switched from the source cell provided by the first network device 120 to a first target cell. Similarly, the second handover procedure may comprise switching the serving cell of the first apparatus 110 from the source cell to a second target cell.
[0081] In some embodiments, the first handover procedure may be a conditional handover procedure. For example, the conditional handover procedure may comprise a handover procedure that is triggered based on a condition configured for the terminal device 110. If the configured condition is satisfied, the handover may be performed.
[0082] In some embodiments, the second handover procedure may be transitional handover procedure. For example, in some scenarios, when the terminal device 110 is attempting to switch its serving cell from the source cell to the first target cell, the handover may not happen directly, since there may be a gap between the coverage areas of the source cell and the first target cell.
[0083] In this case, a second target cell may be involved in the handover procedure, and the serving cell of the terminal device 110 may be switched from the source cell to the second target cell for a transition period for a second set of QoS flows or DBR services which have stringent service continuity requirements, then the serving cell of the terminal device 110 may be switched from the source cell to the first target cell for a first set of QoS flows or DRB services comprising the second set of QoS flows or DRB services. The handover procedure between the source cell and the second target cell may be referred to as the transitional handover procedure.
[0084] In some embodiments, the source cell and the first target cell are in a first earth orbit, and the second target cell is in a second earth orbit, and the second earth orbit is higher than the first earth orbit.
[0085] For example, the first earth orbit may comprise a LEO and the second earth orbit may comprise a MEO / GEO. Moreover, the first network device 120 and the second network device 130 may comprise devices operating in a LEO satellite, and the third network device 140 may comprise devices operating in a MEO / GEO satellite.
[0086] Based on the determination, the first network device 120 may perform, based on the determination, handover preparation with the second network device 130 and the third network device 140 to obtain a first handover configuration for the first handover procedure and a second handover configuration for the second handover procedure. During the HO preparation, the first handover configuration and the second handover configuration may be obtained from the second network device 130 and the third network device 140.
[0087] In some embodiments, the first handover configuration or the second handover configuration may indicate an association between the first handover procedure and the second handover procedure. For example, the conditional handover configuration may indicate the relationship between the conditional handover procedure and the transitional handover procedure.
[0088] In some further embodiments, the first handover configuration or the second handover configuration may indicate information related to the QoS flow or DRBs. For example, the conditional handover configuration may indicate a reduced set of at least one signaling radio bearer (SRB) associated with the second target cell and at least one QoS flow or DRB associated with the set of QoS flows or DRBs, at least one service type associated with the set of QoS flows or DRBs and a mapping between the set of QoS flows and corresponding DRBs. In some examples, the second handover configuration may comprise a reduced set of at least one function or service associated with the second target cell.
[0089] In some other embodiments, the first handover configuration or the second handover configuration may indicate information related to the transition period. For example, the conditional handover configuration may indicate a configuration of a transition period and grants for the data transmission with the third network device during the transition period.
[0090] As shown in FIG. 4, as a part of the HO preparation, the first network device 120 may transmit (415) , to the third network device 140, a handover (HO) request at least indicating that the second handover procedure is to be performed by the terminal device 110. In some embodiments, the HO preparation process may be initiated by the first network device 120.
[0091] In some embodiments, the HO request may further indicate a cause for the second handover. For example, the cause may indicate that this handover is a transitional handover.
[0092] In some embodiments, the HO request may indicate information related to the handover and the transition period, which may comprise an expected transition period during which the terminal device 110 is expected to be served by the second target cell and an identity of the first target cell.
[0093] Moreover, the HO request may also indicate context information for a set of QoS flows or DRBs associated with the second handover and at least one of a trigger or a constraint for the first handover procedure.
[0094] Based on the HO request, the third network device 140 may transmit (420) , to the first network device 120, a HO acknowledgement at least indicating a transition period granted for the terminal device 110, and terminal device 110 is allowed to be served by the second target cell within the transition period.
[0095] Similarly, a HO preparation procedure may also be performed between the first network device 120 and the second network device 130. For example, the first network device 120 may transmit (422) the HO request to the second network device 130. Based on the HO request, the second network device 130 may transmit (424) a HO acknowledgement to the first network device 120. It is noted that step 422 and step 424 are not shown in FIG. 4, as the first HO procedure may be based on or considered as legacy HO procedure.
[0096] In the HO preparation process, the second network device 130 and the third network device 140 may generate or provide the first and the second handover configuration.
[0097] As shown in FIG. 4, the first network device 120 may transmit (425) and / or (427) , to the terminal device 110, the first handover configuration and / or the second handover configuration via at least one radio resource control (RRC) reconfiguration message. The first handover configuration and the second handover configuration may be transmitted to the terminal device 110 via separate RRC messages (425 and 427) or the first handover configuration and the second handover configuration may also be transmitted to the terminal device 110 in a single RRC message (427) .
[0098] As shown in FIG. 4, the first network device 120 may transmit (425) the first handover configuration via an RRC reconfiguration message, which may be optional here, since the first handover configuration and the second handover configuration may only require one RRC message for the transmission. Based on the obtained the first handover configuration or the second handover configuration, the terminal device 110 may perform the second handover procedure and switch its serving cell to the third network device 140.
[0099] If the terminal device 110 performs the second handover procedure to the second target cell, the terminal device 110 may transmit (430) , to the third network device 140, an RRC reconfiguration complete message indicating the second handover procedure is completed. Upon completion of the second handover procedure, the terminal device 110 may start the transition period.
[0100] In some embodiments, the third network device 140 may determine a second handover configuration indicating a second handover procedure of the terminal device 110 to a second target cell managed by the third network device 140. The second handover procedure herein may be associated with a first handover procedure of the terminal device 110 to a first target cell managed by a further apparatus (for example, the second network device 130) .
[0101] Based on the configuration, the third network device 140 may perform data transmission on a set of QoS flows or DRBs after a completion of the second handover procedure to the second target cell.
[0102] After a completion of the second handover procedure to the second target cell and based on the first handover configuration or the second handover configuration, the terminal device 110 may perform (435) data transmissions of a set of QoS flows or DRBs with the third network device 140 during a transition period within which the terminal device 110 is served by the second target cell.
[0103] As shown in FIG. 4, the terminal device 110 may maintain (440) , based on the second conditional handover configuration, context information associated with the set of QoS flows or DRBs.
[0104] As an option, upon completing the second handover procedure, the terminal device 110 may initiate the first handover procedure when the transition period ends as configured.
[0105] In some embodiments, if the terminal device 110 determines that at least one condition for the first handover procedure is met, the terminal device 110 may notify (442) , to the third network device 140, the first handover procedure is to be performed and perform the first handover procedure to the first target cell.
[0106] For example, the third network device 140 may receive a notification from the terminal device 110 indicating that the first handover procedure to the first target cell is to be performed by the terminal device 110.
[0107] As shown in FIG. 4, the terminal device 110 may perform, after a completion of the first handover procedure to the first target cell and based on the first handover configuration or the second handover configuration, data transmissions of a further set of QoS flows or DRBs with the second network device 130.
[0108] In some embodiments, the set of QoS flows or DRBs may be comprised in the further set of QoS flows or DRBs. For example, the set of QoS flows or DRBs may be a subset of the further set of QoS flows or DRBs.
[0109] Based on the first handover configuration or the second handover configuration, the terminal device 110 may store (450) the context information associated with the further set of QoS flows or DRBs.
[0110] Through the above process, the scenario where both the second handover procedure and the first handover procedure are successful is introduced. However, the first handover procedure may not be always successful. In this case, if the terminal device 110 determines that the terminal device 110 fails to perform the first handover procedure, the terminal device 110 may transmit (455) , to the third network device 140, an indication of a failure of the first handover procedure.
[0111] In some embodiments, if the third network device 140 determines, based on location and mobility information of the terminal device 110 and the second network device 130, that the first handover procedure is not applicable, the third network device 140 may configure the terminal device 110 to stay with the second target cell.
[0112] As another option, for example, the terminal device may also maintain the connection with the third network device 140. In this case, if the terminal device 110 determines that the terminal device 110 is reconfigured to stay with the third network device 140 and be served by the second target cell, the terminal device 110 may release context information associated with the further set of QoS flows or DRBs. Or the terminal device 110 may stop the transition period.
[0113] In some other embodiments, if the third network device 140 determines that an indication of a failure of the first handover procedure is received from the terminal device 110, the third network device 140 may determine that terminal device 110 stays with the second target cell.
[0114] Reference is now made to FIG. 5, which shows a signaling chart 500 for communication according to some example embodiments of the present disclosure. As shown in FIG. 5, the signaling chart 500 involves a terminal device 110, a first network device 120, a second network device 130 and a third network device 140. For the purpose of discussion, reference is made to FIG. 1 to describe the signaling chart 500.
[0115] FIG. 5 shows a more detailed process of the first handover procedure and the second handover procedure according to some embodiments of the present disclosure. In the situation shown in FIG. 5, the first network device 120 may be referred to as base station 1 (BS1) , the second network device 130 may be referred to as base station 2 (BS2) and the third network device 140 may be referred to as base station 3 (BS3) .
[0116] Furthermore, some aspects of the present disclosure related to core network (CN) may also be introduced in connection with FIG. 5.
[0117] In some embodiments, the first network device 120, the third network device 140 and the terminal device 110 may need to be authorized to perform THO by the CN in advance based on capability and service level agreement of the terminal device 110.
[0118] As shown in FIG. 5, after obtaining the authorization, the first network device 120 of the source serving cell in LEO may determine (505) a CHO for the terminal device 110 to the second network device 130 of a first target cell in the same orbit of LEO. Due to an expected coverage gap between the source cell and the first target cell in LEO, a THO to a third network device 140 of a second target cell in higher orbit may be needed for maintaining service continuity for a subset of QoS flows or DRBs of the terminal device 110 that have stringent service continuity requirements (such as for delay-sensitive real-time services) .
[0119] The determination of the need for the THO may be based on awareness of location, mobility, coverage or neighbor-cell information of the terminal device 110, the second network device 130 and the third network device 140, which is either from measurement reports from the terminal device 110 or from operation, administration, and maintenance (OAM) information update from the network.
[0120] The above-mentioned CHO to the first target cell may be associated with all current QoS flows or DRBs of the terminal device 110, which may be referred to as the full set, first set or further set of QoS flows or DRBs, including the subset of QoS flows or DRBs under the THO, which may be referred to as the set or second set of QoS flows or DRBs.
[0121] In some embodiments, the THO may be applied for a predefined subset of SRBs and / or selected subset of DRBs or QoS flows (i.e., the second set) to reduce burden to the third network device 140, which may be reflected in the HO request and HO acknowledgement described below for HO preparation.
[0122] This step for the determination of the CHO may be performed based on awareness of QoS requirements of current QoS flows, configurations of DRBs, link budget imbalance between the source cell in LEO and the second target cell in higher orbit, location and mobility information of the terminal device 110 and the first target cell in LEO.
[0123] As shown in FIG. 5, the first network device 120 may prepare (510) a CHO for the terminal device 110 and perform HO request procedure with the second network device 130 using existing HO mechanism.
[0124] For example, in this step of preparation, the first network device 120 may transmit a HO request to the second network device 130 to request for the CHO. Based on the request, the second network device 130 may transmit a HO acknowledgement to the first network device 120 as a response. The HO acknowledgement comprises configurations for the terminal device 110.
[0125] As shown at block 512 in FIG. 5, the first network device 120 may prepare the THO for the terminal device 110 with the third network device 140. For example, the first network device 120 may send (515) a HO request to the third network device 140, indicating that the HO request is for THO explicitly via setting a specific value for a ‘cause’ information element (IE) or implicitly via other indication or IE included in the HO request.
[0126] In some embodiments, the other indication or IE as mentioned above may include an expected or minimum transition time or identity of the first target cell. The HO request may further include context information of the second set of QoS flows or DRBs, which is determined by the source cell provided by the first network device 120 based on the coverage gap between the source cell and the first target cell (provided by the second network device 130) in LEO and configurations or characteristics of QoS flows or DRBs.
[0127] In some embodiments, the HO request for THO may also include configuration for CHO to the second network device 130 such as triggers or constraints configured for CHO to the second network device 130 (time window configured for CHO for example) . This configuration may be used by the third network device 140 to determine optimal THO configurations for the terminal device 110.
[0128] Based on the preparation for the requested THO, the third network device 140 may send (520) a HO acknowledgement to the first network device 120 in response to the HO request. The HO acknowledgement may include a granted or maximum transition time for the terminal device 110 to be served by third network device 140 and configurations for the terminal device 110 for the transition period to be served by third network device 140.
[0129] In some embodiments, if the granted or maximum transition time is not shorter than the expected or minimum transition time of the terminal device 110, the THO preparation may be determined to be successful.
[0130] In some embodiments, the configurations comprised in the HO acknowledgement may include (re) configurations of the predefined subset or reduced set of SRBs (e.g., no more than signal resource bearer (SRB) 1 and SRB2) , functions and services (e.g., no configurations for layer 3 (L3) measurement and reporting) to be provided during the transition period.
[0131] In some embodiments, the configurations for the terminal device 110 may include (re) configuration of DRBs and rules for mapping QoS flows to DRBs for serving the second set of QoS flows or DRBs in the second target cell of the third network device 140.
[0132] In some embodiments, the configurations for the terminal device 110 may also include time gaps during the transition period for the terminal device 110 to detect and perform CHO to the second network device 130.
[0133] In some embodiment, if the third network device 140 rejects the HO request from the first network device 120 for THO of the terminal device 110 in step 520, the first network device 120 may proactively reconfigure the terminal device 110 to terminate or release the second set of QoS flows or DRBs. The first network device 120 may also notify CN about the termination of QoS flows in the second set.
[0134] Similar to the above process, the first network device 120 may transmit (522) the HO request to the second network device 130. Based on the received HO request, the second network device 130 may transmit (524) the corresponding HO acknowledgement to the first network device 120.
[0135] Based on the result of the preparation, the first network device 120 may send (525) an RRC reconfiguration message to the terminal device 110, providing the terminal device 110 with the configurations for CHO to the second network device 130, also referred to as the first HO configuration.
[0136] In some embodiment, at this step, the first network device may indicate to the terminal device 110 that the CHO to the second network device 130 may be associated with THO to the third network device 140 for the second set of QoS flows or DRBs.
[0137] As shown in FIG. 5, the first network device 120 may send (530) an RRC reconfiguration message to the terminal device 110, providing the terminal device 110 with the configurations for THO to the third network device 140 as described above, also referred to as the second HO configuration.
[0138] In some embodiments, the RRC message sent in this step may be combined with the RRC message in step 525. In this case, the terminal device 110 needs to send a single RRC reconfiguration complete 535 to the first network device 120. In case step 525 and step 530 are sent in separate RRC reconfiguration messages, the terminal device 110 needs to send separate RRC reconfiguration complete messages to the first network device 120 for each of the RRC reconfiguration messages sent in step 525 and step 530.
[0139] In some embodiment, the terminal device 110, based on the received configurations in step 525 and step 530, may keep double context information associated with the second set of QoS flows or DRBs provided by the second network device 130 and the third network device 140. The terminal device 110 may also store data of QoS flows that are configured for CHO to the second network device 130 though the QoS flows are not in the second set to be handed over to the third network device 140 using THO and served by the third network device 140 during the transition period.
[0140] In some embodiments, the first network device 120 may indicate to the terminal device 110 in step 530 that the THO to the third network device 140 is associated with the CHO to the second network device 130.
[0141] Regarding the process for the preparation of the handover, in some embodiments, procedures for preparation and configuration of THO to the third network device 140 in steps 515-520 may be performed before or in parallel with procedures of CHO to the second network device 130 in steps 522-524. With some embodiment, step 525 and step 530 may be combined so that the terminal device 110 gets the configuration for CHO to the second network device 130 and THO to the third network device 140 in one RRC Reconfiguration message.
[0142] As shown in FIG. 5, the terminal device110 may send (535) an RRC reconfiguration complete message to the first network device 120 in response to the RRC reconfiguration message in step 530.
[0143] In some embodiments, based on positive outcomes of the HO preparation for CHO and associated THO comprising the first and second HO configurations, the first network device 120 may also indicate to CN about CHO and associated THO configured for the terminal device 110 including QoS flows in the second set so that CN is able to determine to continue routing data traffic of the QoS flows in the second set to the third network device 140 or BS3 and store the rest until CHO of the terminal device 110 to second network device 130 is completed.
[0144] In some embodiments, the terminal device 110 may perform THO to the third network device 140 and send (540) an RRC reconfiguration complete message to the third network device 140, starting the transition period in the second target cell.
[0145] Upon finishing the reconfiguration, the terminal device 110 may be served by the third network device 140 for data transmissions for the second set of QoS flows or DRBs for the transition period. For example, the terminal device 110 may perform (545) the data transmission during the transition time.
[0146] In some embodiments, the third network device 140 may determine and reconfigure the terminal device 110 to stay with the third network device 140 in regular serving mode which means that the transition period may be stopped and the terminal device 110 may be served by third network device 140 in regular serving mode. The terminal device 110 therefore may release data and context information associated with CHO to the second network device 130. This may be applied in case the third network device 140, based on latest location and mobility information of the terminal device 110 and the LEO satellite of the second network device 130, determines that CHO to the second network device 130 is no longer applicable to the terminal device 110.
[0147] Alternatively or in addition, the second network device 130 or the third network device 140 may indicate to the CN about THO of the terminal device 110 including QoS flows in the second set so that the CN is able to determine to continue routing data traffic of the QoS flows in the second set to the third network device 140 and store the rest until CHO of the terminal device 110 to the second network device 130 is completed.
[0148] Upon detecting that a condition for CHO to the second network device 130 has been met during the transition period, the terminal device 110 may notify (550) the third network device 140 that the terminal device 110 may perform the CHO to the second network device 130.
[0149] In some embodiments, the terminal device 110 may perform CHO to the second network device 130 during the transition period and send (555) the RRC reconfiguration complete to the second network device 130.
[0150] In some embodiments, the terminal device 110 may be configured to notify the third network device 140 in case the terminal device 110 fails to perform CHO to the second network device 130. Then, it is up to the third network device 140 whether to reconfigure the terminal device 110 to stay with the third network device 140 in regular serving mode, as described above, or release the terminal device 110.
[0151] Upon finishing the reconfiguration, the terminal device 110 may be served by the second network device 130 for data transmissions for the first set of QoS flows or DRBs including the second set of QoS flows or DRBs. For example, the terminal device 110 may perform (560) data transmission via the second network device 130. The terminal device 110 may release context information associated with the third network device 140.
[0152] In some embodiments, once the terminal device 110 is connected to the second network device 130, the CN may release context information of the terminal device 110 associated with the third network device 140.
[0153] Alternatively or in addition, in some embodiments, direct Xn connections via inter-satellite link (ISL) may be available between the first network device 120, the second network device 130, and the third network device 140. In this case, embodiments of the present disclosure may be implemented without involving the CN. In this situation, the first network device 120 may need to act as an anchor for data traffic of the terminal device 110 during the transition period.
[0154] Alternatively or in addition, the data traffic of QoS flows in the second set may be routed via the first network device 120 to / from the third network device 140 while data traffic of other QoS flows may be stored at the first network device 120 and forwarded to the second network device 130 later on or forwarded to the second network device 130 to be stored at the second network device 130 in advance. However, such solution may not be preferable in NTN environment, as ISL may not be available, or storage capacity of satellites is limited in general.
[0155] In this way, the embodiments of the present disclosure can provide a handover process without any discontinuation of data transmission. By preparing and transmitting the handover configuration in the above-described manner, an efficient handover configuration process can be achieved and the user experience can be improved.
[0156] FIG. 6 shows a flowchart of an example method 600 implemented at an apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 600 will be described from the perspective of the terminal device 110 in FIG. 1.
[0157] At block 610, the terminal device 110 receives, from a first network device managing a source cell of the terminal device, a first handover configuration for a first handover procedure of the terminal device to a first target cell managed by a second network device and a second handover configuration for a second handover procedure of the terminal device to a second target cell managed by a third network device, wherein the second handover configuration indicates a transition period within which the terminal device is to be served by the second target cell.
[0158] At block 620, the terminal device 110 performs, after a completion of the second handover procedure to the second target cell and based on the second handover configuration, data transmissions of a set of QoS flows or DRBs with the third network device during the transition period.
[0159] At block 630, in accordance with a determination that at least one condition for the first handover procedure is met during the transition period, at block 640, the terminal device 110 performs the first handover procedure to the first target cell.
[0160] At block 650, the terminal device 110 performs, after a completion of the first handover procedure to the first target cell and based on the first handover configuration, data transmissions of a further set of QoS flows or DRBs with the second network device, wherein the set of QoS flows or DRBs are comprised in the further set of QoS flows or DRBs.
[0161] In some example embodiments, the source cell and the first target cell are in a first earth orbit, and the second target cell is in a second earth orbit, and wherein the second earth orbit is higher than the first earth orbit.
[0162] In some example embodiments, the first and the second handover configurations are received via separate RRC reconfiguration messages.
[0163] In some example embodiments, the first and the second handover configurations are received via a same RRC reconfiguration message.
[0164] In some example embodiments, the second handover configuration indicates at least one of the following: an association between the first handover procedure and the second handover procedure; a reduced set of at least one SRB associated with the second target cell, a reduced set of at least one function or service associated with the second target cell, at least one QoS flow or DRB associated with the set of QoS flows or DRBs, at least one service type associated with the set of QoS flows or DRBs, a mapping between the set of QoS flows and corresponding DRBs, a configuration of the transition period, or grants for the data transmission with the third network device during the transition period.
[0165] In some example embodiments, the method 600 further comprises: maintaining, based on the second handover configuration, context information associated with the set of QoS flows or DRBs.
[0166] In some example embodiments, the method 600 further comprises: storing, based on the first handover configuration, context information associated with the further set of QoS flows or DRBs.
[0167] In some example embodiments, the method 600 further comprises: in accordance with performing the second handover procedure to the second target cell, transmitting to the third network device, an RRC reconfiguration complete message indicating the second handover procedure is completed; and starting the transition period.
[0168] In some example embodiments, the method 600 further comprises: in accordance with a determination that the terminal device is reconfigured to stay with the third network device and be served by the second target cell, performing at least one of: stopping the transition period; or releasing context information associated with the further set of QoS flows or DRBs.
[0169] In some example embodiments, the method 600 further comprises: in accordance with a determination that the at least one condition for the first handover procedure is met, notifying to the third network device, the first handover procedure is to be performed.
[0170] In some example embodiments, the method 600 further comprises: in accordance with a determination that the terminal device fails to perform the first handover procedure, transmitting to the third network device, an indication of a failure of the first handover procedure.
[0171] FIG. 7 shows a flowchart of an example method 700 implemented at an apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 700 will be described from the perspective of the first network device 120 in FIG. 1.
[0172] At block 710, the first network device 120 determines a first handover procedure of a terminal device to a first target cell managed by a second network device and a second handover procedure of the terminal device to a second target cell managed by a third network device are to be performed, wherein the second handover procedure is for a transition period within which the terminal device is to be served by the second target cell.
[0173] At block 720, the first network device 120 performs, based on the determination, handover preparation with the second network device and the third network device to obtain a first handover configuration for the first handover procedure and a second handover configuration for the second handover procedure.
[0174] At block 730, the first network device 120 transmits the first and the second handover configurations to the terminal device.
[0175] In some example embodiments, a source cell managed by the apparatus and the first target cell are in a first earth orbit, and the second target cell is in a second earth orbit, and wherein the second earth orbit is higher than the first earth orbit.
[0176] In some example embodiments, the first and second handover configuration are transmitted via separate RRC reconfiguration messages.
[0177] In some example embodiments, the first handover configuration and the second handover configuration are transmitted via a same RRC reconfiguration message.
[0178] In some example embodiments, the second handover configuration indicates at least one of the following: an association between the first handover procedure and the second handover procedure; a reduced set of at least one SRB associated with the second target cell, a reduced set of at least one function or service associated with the second target cell, at least one QoS flow or DRB associated with the set of QoS flows or DRBs, at least one service type associated with the set of QoS flows or DRBs, a mapping between the set of QoS flows and corresponding DRBs, a configuration of the transition period, or grants for the data transmission with the third network device during the transition period.
[0179] In some example embodiments, the method 700 further comprises: determining the first handover procedure and the second handover procedure are to be performed based on cell coverage related information comprising at least one of the following: mobility and location information associated with the apparatus based on the measurement information, or coverage and neighboring cell information associated with the second network device and the third network device based on OAM information.
[0180] In some example embodiments, the handover preparation with the third network device comprises: transmitting, to the third network device, a HO request at least indicating that the second handover procedure is to be performed for the terminal device for the transition period within which the terminal device is to be served by the second target cell; and receiving, from the third network device, a HO acknowledgement at least indicating the transition period granted for the terminal device, wherein the terminal device is allowed to be served by the second target cell within the transition period.
[0181] In some example embodiments, the HO request further indicates at least one of the following: a cause for the second handover, an expected transition period during which the terminal device is expected to be served by the second target cell, an identity of the first target cell, context information for a set of QoS flows or DRBs associated with the second handover, or at least one of a trigger or a constraint for the first handover procedure.
[0182] FIG. 8 shows a flowchart of an example method 800 implemented at an apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 800 will be described from the perspective of the third network device 140 in FIG. 1.
[0183] At block 810, third network device 140 receives, from a first network device, a HO request for a second handover procedure of a terminal device to a second target cell managed by the third network device, wherein the HO request indicates that the second handover procedure is for a transition period within which the terminal device is to be served by the second target cell.
[0184] At block 820, third network device 140 transmits, to the first network device, a HO acknowledgement in response to the HO request, at least indicating the transition period granted for the terminal device, wherein the terminal device is allowed to be served by the second target cell within the transition period.
[0185] In some example embodiments, the method 800 further comprises: determining, based on the HO request, a second handover configuration for the second handover procedure of the terminal device, at least indicating the transition period granted for the terminal device, wherein the terminal device is allowed to be served by the second target cell within the transition period; and performing data transmission on a set of QoS flows or DRBs after a completion of the second handover procedure to the second target cell.
[0186] In some example embodiments, the method 800 further comprises: in accordance with a determination, configuring on location and mobility information of the terminal device and the second network device, that the first handover procedure is not applicable, configure the terminal device to stay with the second target cell.
[0187] In some example embodiments, the method 800 further comprises: in accordance with a determination that an indication of a failure of the first handover procedure is received from the terminal device, configuring the terminal device to stay with the second target cell.
[0188] In some example embodiments, the method 800 further comprises: receiving a notification from the terminal device indicating that the first handover procedure to the first target cell is to be performed by the terminal device.
[0189] In some example embodiments, the first handover procedure is a conditional handover procedure, and the second handover procedure is a transitional handover procedure.
[0190] In some example embodiments, the third network device comprises a third network device.
[0191] In some example embodiments, an apparatus capable of performing any of the method 600 (for example, the terminal device 110 in FIG. 1) may comprise means for performing the respective operations of the method 600. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The apparatus may be implemented as or included in the terminal device 110 in FIG. 1.
[0192] In some example embodiments, the apparatus comprises means for receiving, from a first network device managing a source cell of the apparatus, a first handover configuration for a first handover procedure of the apparatus to a first target cell managed by a second network device and a second handover configuration for a second handover procedure of the apparatus to a second target cell managed by a third network device, wherein the second handover configuration indicates a transition period within which the apparatus is to be served by the second target cell; means for performing, after a completion of the second handover procedure to the second target cell and based on the second handover configuration, data transmissions of a set of QoS flows or DRBs with the third network device during the transition period; means for in accordance with a determination that at least one condition for the first handover procedure is met during the transition period, performing the first handover procedure to the first target cell; and means for performing, after a completion of the first handover procedure to the first target cell and based on the first handover configuration, data transmissions of a further set of QoS flows or DRBs with the second network device, wherein the set of QoS flows or DRBs are comprised in the further set of QoS flows or DRBs.
[0193] In some example embodiments, the source cell and the first target cell are in a first earth orbit, and the second target cell is in a second earth orbit, and wherein the second earth orbit is higher than the first earth orbit.
[0194] In some example embodiments, the first and the second handover configurations are received via separate RRC reconfiguration messages.
[0195] In some example embodiments, the first and the second handover configurations are received via a same RRC reconfiguration message.
[0196] In some example embodiments, the second handover configuration indicates at least one of the following: an association between the first handover procedure and the second handover procedure; a reduced set of at least one SRB associated with the second target cell, a reduced set of at least one function or service associated with the second target cell, at least one QoS flow or DRB associated with the set of QoS flows or DRBs, at least one service type associated with the set of QoS flows or DRBs, a mapping between the set of QoS flows and corresponding DRBs, a configuration of the transition period, or grants for the data transmission with the third network device during the transition period.
[0197] In some example embodiments, the apparatus further comprises: means for maintaining, based on the second handover configuration, context information associated with the set of QoS flows or DRBs.
[0198] In some example embodiments, the apparatus further comprises: means for storing, based on the first handover configuration, context information associated with the further set of QoS flows or DRBs.
[0199] In some example embodiments, the apparatus further comprises: means for in accordance with performing the second handover procedure to the second target cell, transmitting to the third network device, an RRC reconfiguration complete message indicating the second handover procedure is completed; and means for starting the transition period.
[0200] In some example embodiments, the apparatus further comprises: means for in accordance with a determination that the apparatus is reconfigured to stay with the third network device and be served by the second target cell, performing at least one of: means for stopping the transition period; or means for releasing context information associated with the further set of QoS flows or DRBs.
[0201] In some example embodiments, the apparatus further comprises: means for in accordance with a determination that the at least one condition for the first handover procedure is met, notifying to the third network device, the first handover procedure is to be performed.
[0202] In some example embodiments, the apparatus further comprises: means for in accordance with a determination that the apparatus fails to perform the first handover procedure, transmitting to the third network device, an indication of a failure of the first handover procedure.
[0203] In some example embodiments, the apparatus comprises a terminal device.
[0204] In some example embodiments, an apparatus capable of performing any of the method 700 (for example, the first network device 120 in FIG. 1) may comprise means for performing the respective operations of the method 700. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The apparatus may be implemented as or included in the first network device 120 in FIG. 1.
[0205] In some example embodiments, the apparatus comprises means for determining a first handover procedure of a terminal device to a first target cell managed by a second network device and a second handover procedure of the terminal device to a second target cell managed by a third network device are to be performed, wherein the second handover procedure is for a transition period within which the terminal device is to be served by the second target cell; means for performing, based on the determination, handover preparation with the second network device and the third network device to obtain a first handover configuration for the first handover procedure and a second handover configuration for the second handover procedure; and means for transmitting the first and the second handover configurations to the terminal device.
[0206] In some example embodiments, a source cell managed by the apparatus and the first target cell are in a first earth orbit, and the second target cell is in a second earth orbit, and wherein the second earth orbit is higher than the first earth orbit.
[0207] In some example embodiments, the first and second handover configuration are transmitted via separate RRC reconfiguration messages.
[0208] In some example embodiments, the first handover configuration and the second handover configuration are transmitted via a same RRC reconfiguration message.
[0209] In some example embodiments, the second handover configuration indicates at least one of the following: an association between the first handover procedure and the second handover procedure; a reduced set of at least one SRB associated with the second target cell, a reduced set of at least one function or service associated with the second target cell, at least one QoS flow or DRB associated with the set of QoS flows or DRBs, at least one service type associated with the set of QoS flows or DRBs, a mapping between the set of QoS flows and corresponding DRBs, a configuration of the transition period, or grants for the data transmission with the third network device during the transition period.
[0210] In some example embodiments, the apparatus further comprises: means for determining the first handover procedure and the second handover procedure are to be performed based on cell coverage related information comprising at least one of the following: means for mobility and location information associated with the apparatus based on the measurement information, or means for coverage and neighboring cell information associated with the second network device and the third network device based on OAM information.
[0211] In some example embodiments, the handover preparation with the third network device comprises: transmitting, to the third network device, a HO request at least indicating that the second handover procedure is to be performed for the terminal device for the transition period within which the terminal device is to be served by the second target cell; and receiving, from the third network device, a HO acknowledgement at least indicating the transition period granted for the terminal device, wherein the terminal device is allowed to be served by the second target cell within the transition period.
[0212] In some example embodiments, the HO request further indicates at least one of the following: a cause for the second handover, an expected transition period during which the terminal device is expected to be served by the second target cell, an identity of the first target cell, context information for a set of QoS flows or DRBs associated with the second handover, or at least one of a trigger or a constraint for the first handover procedure.
[0213] In some example embodiments, the apparatus comprises a first network device.
[0214] In some example embodiments, an apparatus capable of performing any of the method 800 (for example, the third network device 140 in FIG. 1) may comprise means for performing the respective operations of the method 800. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The apparatus may be implemented as or included in the third network device 140 in FIG. 1.
[0215] In some example embodiments, the apparatus comprises means for receiving, from a first network device, a HO request for a second handover procedure of a terminal device to a second target cell managed by the apparatus, wherein the HO request indicates that the second handover procedure is for a transition period within which the terminal device is to be served by the second target cell; and means for transmitting, to the first network device, a HO acknowledgement in response to the HO request, at least indicating the transition period granted for the terminal device, wherein the terminal device is allowed to be served by the second target cell within the transition period.
[0216] In some example embodiments, the apparatus further comprises: means for determining, based on the HO request, a second handover configuration for the second handover procedure of the terminal device, at least indicating the transition period granted for the terminal device, wherein the terminal device is allowed to be served by the second target cell within the transition period; and means for performing data transmission on a set of QoS flows or DRBs after a completion of the second handover procedure to the second target cell.
[0217] In some example embodiments, the apparatus further comprises: means for in accordance with a determination, configuring on location and mobility information of the terminal device and the second network device, that the first handover procedure is not applicable, configure the terminal device to stay with the second target cell.
[0218] In some example embodiments, the apparatus further comprises: means for in accordance with a determination that an indication of a failure of the first handover procedure is received from the terminal device, configuring the terminal device to stay with the second target cell.
[0219] In some example embodiments, the apparatus further comprises: means for receiving a notification from the terminal device indicating that the first handover procedure to the first target cell is to be performed by the terminal device.
[0220] In some example embodiments, the first handover procedure is a conditional handover procedure, and the second handover procedure is a transitional handover procedure.
[0221] In some example embodiments, the apparatus comprises a third network device.
[0222] FIG. 9 is a simplified block diagram of a device 900 that is suitable for implementing example embodiments of the present disclosure. The device 900 may be provided to implement a communication device, for example, the terminal device 110 or the first network device 120 or the second network device 130 or the third network device 140 as shown in FIG. 1. As shown, the device 900 includes one or more processors 910, one or more memories 920 coupled to the processor 910, and one or more communication modules 940 coupled to the processor 910.
[0223] The communication module 940 is for bidirectional communications. The communication module 940 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interface that is necessary for communication with other network elements. In some example embodiments, the communication module 940 may include at least one antenna.
[0224] The processor 910 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 900 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
[0225] The memory 920 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 924, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , an optical disk, a laser disk, and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random-access memory (RAM) 922 and other volatile memories that will not last in the power-down duration.
[0226] A computer program 930 includes computer executable instructions that are executed by the associated processor 910. The instructions of the program 930 may include instructions for performing operations / acts of some example embodiments of the present disclosure. The program 930 may be stored in the memory, e.g., the ROM 924. The processor 910 may perform any suitable actions and processing by loading the program 930 into the RAM 922.
[0227] The example embodiments of the present disclosure may be implemented by means of the program 930 so that the device 900 may perform any process of the disclosure as discussed with reference to FIG. 2 to FIG. 8. The example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
[0228] In some example embodiments, the program 930 may be tangibly contained in a computer readable medium which may be included in the device 900 (such as in the memory 920) or other storage devices that are accessible by the device 900. The device 900 may load the program 930 from the computer readable medium to the RAM 922 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .
[0229] FIG. 10 shows an example of the computer readable medium 1000 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 1000 has the program 930 stored thereon.
[0230] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Although various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method 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.
[0231] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
[0232] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
[0233] In the context of the present disclosure, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.
[0234] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0235] Further, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated, certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single embodiment may also be implemented in a plurality of embodiments separately or in any suitable sub-combination.
[0236] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
1.An apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:receive, from a first network device managing a source cell of the apparatus, a first handover configuration for a first handover procedure of the apparatus to a first target cell managed by a second network device and a second handover configuration for a second handover procedure of the apparatus to a second target cell managed by a third network device, wherein the second handover configuration indicates a transition period within which the apparatus is to be served by the second target cell;perform, after a completion of the second handover procedure to the second target cell and based on the second handover configuration, data transmissions of a set of quality of service, QoS, flows or data radio bearers, DRBs, with the third network device during the transition period;in accordance with a determination that at least one condition for the first handover procedure is met during the transition period, perform the first handover procedure to the first target cell; andperform, after a completion of the first handover procedure to the first target cell and based on the first handover configuration, data transmissions of a further set of QoS flows or DRBs with the second network device, wherein the set of QoS flows or DRBs are comprised in the further set of QoS flows or DRBs.2.The apparatus of claim 1, wherein the source cell and the first target cell are in a first earth orbit, and the second target cell is in a second earth orbit, and wherein the second earth orbit is higher than the first earth orbit.3.The apparatus of claim 1 or 2, wherein the first and the second handover configurations are received via separate radio resource control, RRC, reconfiguration messages.4.The apparatus of any of claims 1-3, wherein the first and the second handover configurations are received via a same RRC reconfiguration message.5.The apparatus of any of claims 1-4, wherein the second handover configuration indicates at least one of the following:an association between the first handover procedure and the second handover procedure;a reduced set of at least one signaling radio bearer, SRB, associated with the second target cell,a reduced set of at least one function or service associated with the second target cell,at least one QoS flow or DRB associated with the set of QoS flows or DRBs,at least one service type associated with the set of QoS flows or DRBs,a mapping between the set of QoS flows and corresponding DRBs,a configuration of the transition period, orgrants for the data transmission with the third network device during the transition period.6.The apparatus of any of claims 1-5, wherein the apparatus is caused to:maintain, based on the second handover configuration, context information associated with the set of QoS flows or DRBs.7.The apparatus of any of claims 1-6, wherein the apparatus is caused to:store, based on the first handover configuration, context information associated with the further set of QoS flows or DRBs.8.The apparatus of any of claims 1-7, wherein the apparatus is caused to:in accordance with performing the second handover procedure to the second target cell, transmit, to the third network device, an RRC reconfiguration complete message indicating the second handover procedure is completed; andstart the transition period.9.The apparatus of any of claims 1-8, wherein the apparatus is caused to:in accordance with a determination that the apparatus is reconfigured to stay with the third network device and be served by the second target cell, perform at least one of:stop the transition period; orrelease context information associated with the further set of QoS flows or DRBs.10.The apparatus of any of claims 1-9, wherein the apparatus is caused to:in accordance with a determination that the at least one condition for the first handover procedure is met, notify, to the third network device, the first handover procedure is to be performed.11.The apparatus of any of claims 1-10, wherein the apparatus is caused to:in accordance with a determination that the apparatus fails to perform the first handover procedure, transmit, to the third network device, an indication of a failure of the first handover procedure.12.The apparatus of any of claims 1-11, wherein the apparatus comprises a terminal device.13.An apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:determine a first handover procedure of a terminal device to a first target cell managed by a second network device and a second handover procedure of the terminal device to a second target cell managed by a third network device are to be performed, wherein the second handover procedure is for a transition period within which the terminal device is to be served by the second target cell;perform, based on the determination, handover preparation with the second network device and the third network device to obtain a first handover configuration for the first handover procedure and a second handover configuration for the second handover procedure; andtransmit the first and the second handover configurations to the terminal device.14.The apparatus of claim 13, wherein a source cell managed by the apparatus and the first target cell are in a first earth orbit, and the second target cell is in a second earth orbit, and wherein the second earth orbit is higher than the first earth orbit.15.The apparatus of claim 13 or 14, wherein the first and second handover configuration are transmitted via separate radio resource control, RRC, reconfiguration messages.16.The apparatus of any of claims 13-15, wherein the first handover configuration and the second handover configuration are transmitted via a same RRC reconfiguration message.17.The apparatus of any of claims 13-16, wherein the second handover configuration indicates at least one of the following:an association between the first handover procedure and the second handover procedure;a reduced set of at least one signaling radio bearer, SRB, associated with the second target cell,a reduced set of at least one function or service associated with the second target cell,at least one QoS flow or DRB associated with the set of QoS flows or DRBs,at least one service type associated with the set of QoS flows or DRBs,a mapping between the set of QoS flows and corresponding DRBs,a configuration of the transition period, orgrants for the data transmission with the third network device during the transition period.18.The apparatus of claim 13, wherein the apparatus is caused to:determine the first handover procedure and the second handover procedure are to be performed based on cell coverage related information comprising at least one of the following:mobility and location information associated with the apparatus based on the measurement information, orcoverage and neighboring cell information associated with the second network device and the third network device based on operation, administration, and maintenance, OAM, information.19.The apparatus of claim 13, wherein the handover preparation with the third network device comprises:transmitting, to the third network device, a handover, HO, request at least indicating that the second handover procedure is to be performed for the terminal device for the transition period within which the terminal device is to be served by the second target cell; andreceiving, from the third network device, a HO acknowledgement at least indicating the transition period granted for the terminal device, wherein the terminal device is allowed to be served by the second target cell within the transition period.20.The apparatus of claim 19, wherein the HO request further indicates at least one of the following:a cause for the second handover,an expected transition period during which the terminal device is expected to be served by the second target cell,an identity of the first target cell,context information for a set of QoS flows or DRBs associated with the second handover, orat least one of a trigger or a constraint for the first handover procedure.21.The apparatus of any of claim 13-20, wherein the apparatus comprises a first network device.22.An apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:receive, from a first network device, a handover, HO, request for a second handover procedure of a terminal device to a second target cell managed by the apparatus, wherein the HO request indicates that the second handover procedure is for a transition period within which the terminal device is to be served by the second target cell; andtransmit, to the first network device, a HO acknowledgement in response to the HO request, at least indicating the transition period granted for the terminal device, wherein the terminal device is allowed to be served by the second target cell within the transition period.23.The apparatus of claim 22, wherein the apparatus is caused to:determine, based on the HO request, a second handover configuration for the second handover procedure of the terminal device, at least indicating the transition period granted for the terminal device, wherein the terminal device is allowed to be served by the second target cell within the transition period; andperform data transmission on a set of quality of service, QoS, flows or data radio bearers, DRBs, after a completion of the second handover procedure to the second target cell.24.The apparatus of claim 22, wherein the apparatus is caused to:in accordance with a determination, based on location and mobility information of the terminal device and the second network device, that the first handover procedure is not applicable, configure the terminal device to stay with the second target cell.25.The apparatus of claim 24, wherein the apparatus is caused to:in accordance with a determination that an indication of a failure of the first handover procedure is received from the terminal device, configure the terminal device to stay with the second target cell.26.The apparatus of claim 22, wherein the apparatus is caused to:receive a notification from the terminal device indicating that the first handover procedure to the first target cell is to be performed by the terminal device.27.The apparatus of any of claims 22-26 wherein the first handover procedure is a conditional handover procedure, and the second handover procedure is a transitional handover procedure.28.The apparatus of any of claims 22-27, wherein the apparatus comprises a third network device.29.A method comprising:receiving, by a terminal device from a first network device managing a source cell of the terminal device, a first handover configuration for a first handover procedure of the terminal device to a first target cell managed by a second network device and a second handover configuration for a second handover procedure of the terminal device to a second target cell managed by a third network device, wherein the second handover configuration indicates a transition period within which the terminal device is to be served by the second target cell;performing, after a completion of the second handover procedure to the second target cell and based on the second handover configuration, data transmissions of a set of quality of service, QoS, flows or data radio bearers, DRBs, with the third network device during the transition period;in accordance with a determination that at least one condition for the first handover procedure is met during the transition period, performing the first handover procedure to the first target cell; andperforming, after a completion of the first handover procedure to the first target cell and based on the first handover configuration, data transmissions of a further set of QoS flows or DRBs with the second network device, wherein the set of QoS flows or DRBs are comprised in the further set of QoS flows or DRBs.30.A method comprising:determining, by a first network device, a first handover procedure of a terminal device to a first target cell managed by a second network device and a second handover procedure of the terminal device to a second target cell managed by a third network device are to be performed, wherein the second handover procedure is for a transition period within which the terminal device is to be served by the second target cell;performing, based on the determination, handover preparation with the second network device and the third network device to obtain a first handover configuration for the first handover procedure and a second handover configuration for the second handover procedure; andtransmitting the first and the second handover configurations to the terminal device.31.A method comprising:receiving, by a third network device from a first network device, a handover, HO, request for a second handover procedure of a terminal device to a second target cell managed by the third network device, wherein the HO request indicates that the second handover procedure is for a transition period within which the terminal device is to be served by the second target cell; andtransmitting, to the first network device, a HO acknowledgement in response to the HO request, at least indicating a transition period granted for the terminal device, wherein the terminal device is allowed to be served by the second target cell within the transition period.32.A apparatus comprising:means for receiving, from a first network device managing a source cell of the apparatus, a first handover configuration for a first handover procedure of the apparatus to a first target cell managed by a second network device and a second handover configuration for a second handover procedure of the apparatus to a second target cell managed by a third network device, wherein the second handover configuration indicates a transition period within which the apparatus is to be served by the second target cell;means for performing, after a completion of the second handover procedure to the second target cell and based on the second handover configuration, data transmissions of a set of quality of service, QoS, flows or data radio bearers, DRBs, with the third network device during the transition period;means for, in accordance with a determination that at least one condition for the first handover procedure is met during the transition period, performing the first handover procedure to the first target cell; andmeans for performing, after a completion of the first handover procedure to the first target cell and based on the first handover configuration, data transmissions of a further set of QoS flows or DRBs with the second network device, wherein the set of QoS flows or DRBs are comprised in the further set of QoS flows or DRBs.33.An apparatus comprising:means for determining a first handover procedure of a terminal device to a first target cell managed by a second network device and a second handover procedure of the terminal device to a second target cell managed by a third network device are to be performed, wherein the second handover procedure is for a transition period within which the terminal device is to be served by the second target cell;means for performing, based on the determination, handover preparation with the second network device and the third network device to obtain a first handover configuration for the first handover procedure and a second handover configuration for the second handover procedure; andmeans for transmitting the first and the second handover configurations to the terminal device.34.An apparatus comprising:means for receiving, by a third network device from a first network device, a handover, HO, request for a second handover procedure of a terminal device to a second target cell managed by the apparatus, wherein the HO request indicates that the second handover procedure is for a transition period within which the terminal device is to be served by the second target cell; andmeans for transmitting, to the first network device, a HO acknowledgement in response to the HO request, at least indicating a transition period granted for the terminal device, wherein the terminal device is allowed to be served by the second target cell within the transition period.35.A computer readable medium comprising instructions stored thereon for causing an apparatus at least to perform the method of claim 29 or the method of claim 30 or the method of claim 31.
