communication systems

Abstract

To provide a method for reinforcing handover procedure, a user device and a network node, for reducing further signaling and interruption.SOLUTION: In a communication system, a user device includes: means for receiving a radio resource control (RRC) message containing at least either information indicating physical cell identifier (PCI) regarding handover from a first cell to a second cell or information of a synchronization signal / physical broadcasting channel block (SSB) from a network node; means for keeping RRC configuration received by the first cell, while releasing the connection at the first cell; means for executing cell handover without RRC reconfiguration for connection and selecting the second cell; and means for re-establishing connection using the RRC configuration without RRC reconfiguration for the connection by the second cell, the handover to the second cell is conducted according to trigger by media access control (MAC) control element (CE).SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to wireless communication systems and apparatus therefor that operate in accordance with 3rd Generation Partnership Project (3GPP) standards or equivalents or derivatives thereof. The present disclosure is particularly, but not exclusively, related to improvements relating to handovers in so-called "5G" (or "Next Generation") systems that employ Non-Terrestrial Networks (NTNs). [Background technology]

[0002] Under 3GPP standards, a NodeB (or "eNB" in LTE and "gNB" in 5G) is a base station through which a communication device (user equipment or "UE") connects to the core network and communicates with other communication devices or remote servers. A communication device may be, for example, a mobile communication device such as a mobile phone, smartphone, smart watch, personal digital assistant, laptop / tablet computer, web browser, e-book reader, etc. Such mobile devices (or generally fixed devices) are typically operated by a user (and therefore are often collectively referred to as user equipment, "UE"), although IoT devices and similar MTC devices can also be connected to the network. For simplicity, this application will use the term base station to refer to such a base station and the term mobile device or UE to refer to such communication device.

[0003] The latest development in 3GPP standards is the so-called "5G" or "New Radio (NR)" standard, which refers to an evolving communications technology expected to support a variety of applications and services, such as machine type communications (MTC), Internet of Things (IoT) / Industrial Internet of Things (IIoT) communications, vehicular communications and autonomous vehicles, high-definition video streaming, and / or smart city services. 3GPP intends to support 5G through the so-called 3GPP Next Generation (NextGen) radio access network (RAN) and 3GPP NextGen core (NGC) network. Various details of 5G networks are described, for example, in the "NGMN 5G White Paper" V1.0 by the Next Generation Mobile Networks (NGMN) Alliance, available at https: / / www.ngmn.org / 5g-white-paper.html.

[0004] End-user communication devices are commonly referred to as User Equipment (UE) and may be operated by humans or may include automated (MTC / IoT) devices. Base stations in 5G / NR communication systems are commonly referred to as NR base stations (NR-BS) or "gNBs," although it will be understood that they may also be referred to using the term "eNB" (or 5G / NR eNB), which is more typically associated with Long Term Evolution (LTE) base stations (also commonly referred to as "4G" base stations). 3GPP Technical Specification (TS) 38.300 V16.4.0 and TS 37.340 V16.4.0 define, among other things, the following nodes: gNB: A node that provides termination of NR user plane and control plane protocols towards the UE and is connected to the 5G core network (5GC) via the NG interface. ng-eNB: A node that provides termination of E-UTRA (Evolved Universal Terrestrial Radio Access) user plane and control plane protocols for UEs and is connected to 5GC via the NG interface. En-gNB: A node that provides termination of NR user plane and control plane protocols towards the UE and acts as a secondary node in E-UTRA-NR Dual Connectivity (EN-DC). NG-RAN node: Either a gNB or a ng-eNB.

[0005] 3GPP is also working on specifying integrated satellite and terrestrial network infrastructure in the context of 5G. The term non-terrestrial networks (NTN) refers to a network or a segment of a network that uses airborne or spaceborne vehicles for transmission. A satellite refers to a spacecraft in geostationary Earth orbit (GEO) or in a non-geostationary Earth orbit (NGEO), such as low Earth orbits (LEO), medium Earth orbits (MEO), and highly elliptical orbits (HEO). Aircraft refers to High Altitude Platforms (HAPs), which encompass Unmanned Aircraft Systems (UAS), including tethered UAS, Lighter than Air UAS, and Heavier than Air UAS, all of which typically operate quasi-steady at altitudes between 8 and 50 km.

[0006] 3GPP Technical Report (TR) 38.811 V15.4.0 is a study on New Radio to support such non-terrestrial networks. This study includes, among other things, a description of NTN deployment scenarios and related system parameters (architecture, altitude, orbit, etc.), and the adaptation of 3GPP channel models to non-terrestrial networks (propagation conditions, mobility, etc.). 3GPP TR 38.821 V16.0.0 provides further details on NTN. Non-terrestrial networks are expected to: - Help accelerate the rollout of 5G services in unserved or underserved areas and upgrade the performance of terrestrial networks. - Enhance service reliability by providing service continuity to user equipment or to mobile platforms (e.g., passenger aircraft, ships, high-speed trains, buses). - Increase service availability everywhere, especially for critical communications and future rail / maritime / aviation communications. - Enabling 5G network scalability through the provision of efficient multicast / broadcast resources for data delivery towards the network edge or directly to user equipment. NTN Access is typically characterized by (among other things) the following elements: - NTN terminal, which may refer to a 3GPP UE, or to a UE specific to the satellite system if the satellite does not directly serve 3GPP UE. - Service link, which refers to the radio link between the user equipment and the space / air platform (which may be in addition to the radio link with the ground-based RAN). - Space or air platforms. - Gateways connecting satellite or aeronautical access networks to the core network ("NTN Gateways"). It will be understood that the majority of gateways will be co-located with base stations. - Feeder link refers to the radio link between the gateway and the space platform / air platform.

[0007] A satellite or aircraft may generate several beams over a given area to provide each NTN cell, with the beams typically having an elliptical footprint on the Earth's surface.

[0008] 3GPP intends to support three types of NTN beams or cells: - Earth-fixed cells characterized by beams that always cover the same geographic area (e.g. GEO satellites and HAPS). - A quasi-earth fixed cell characterized by a beam (e.g., an NGEO satellite generating a steerable beam) that covers one geographic area during one finite period and a different geographic area during another period. - Earth moving cells characterized by beams that cover one geographic area at one moment and a different geographic area at another moment (e.g., NGEO satellites that generate fixed or non-steerable beams).

[0009] For satellites or aircraft that maintain a fixed position in elevation / azimuth relative to a given Earth point, such as GEO, UAS, etc., the beam footprint is fixed to the Earth.

[0010] For satellites orbiting the Earth (e.g., LEO) or in elliptical orbits around the Earth (e.g., HEO), the beam footprint may move over the Earth as the satellite or aircraft moves in its orbit. Alternatively, the beam footprint may be temporarily Earth-fixed (or quasi-Earth-fixed), in which case an appropriate beam-pointing mechanism (mechanical or electronic steering) may be used to compensate for satellite or aircraft movement.

[0011] LEO satellites may have steerable beams, in which the beams are temporarily directed to a substantially fixed footprint on Earth. In other words, the beam footprint (representing a NTN cell) remains stationary on the Earth for a period of time before the focus area changes to another NTN cell (as the satellite moves in its orbit). From a cell coverage / UE perspective, this results in cell changes occurring periodically at discrete intervals. This is because, even if these beams serve the same terrestrial area (have the same footprint), different physical cell identities (PCIs) and / or synchronization signal / physical broadcast channel (PBCH) blocks (SSBs) must be assigned after each service link change. LEO satellites without steerable beams constantly sweep their moving beams (cells) across the Earth as the satellite moves along its orbit, and as with steerable beams, service link changes and resulting cell changes occur periodically at discrete intervals.

[0012] Similar to service link changes, feeder link changes also occur at regular intervals as the satellite moves in orbit. Both service link changes and feeder link changes may occur between different base stations / gateways (sometimes referred to as "inter-gNB radio link switching") or within the same base station / gateway ("intra-gNB radio link switching").

[0013] In both scenarios, it has been agreed that the system information can include information about the departure of a particular cell and the arrival of a new one, as an enhancement to the cell reselection procedure as the satellite system moves. The handover baseline is expected to use legacy (conditional) handover, i.e., conditional reconfiguration with synchronization procedures in the new cell.

[0014] In the case of an inter-gNB radio link switch, Layer 3 (L3) handover (i.e., Radio Resource Control (RRC) reconfiguration) is required because the two base stations have independent radio resource management. In the case of an intra-gNB radio link switch, the same base station serves the same area before and after the feeder / service link switch. However, because the "bending pipe" communication links between the base station and the UE (i.e., the gNB-satellite feeder link and the satellite-UE service link) change, the UE may be able to maintain its RRC configuration from before the switch, but it still needs to synchronize with the new beam.

[0015] The inventors have identified many problems with the change of service / feeder link. For example, the change of feeder / service link requires a large number of UEs (i.e., all connected UEs within the cell coverage) to perform handover simultaneously. Therefore, the legacy handover procedure needs to be enhanced to reduce further signaling and interruptions. Summary of the Invention [Problem to be solved by the invention]

[0016] SUMMARY OF THE INVENTION Accordingly, the present invention seeks to provide a method, and associated apparatus, that addresses or at least alleviates (at least some) of the above problems. [Means for solving the problem]

[0017] For the sake of efficient understanding by those skilled in the art, the present invention will be described in detail in the context of 3GPP systems (5G networks including NTN), but the principles of the present invention can be applied to other systems as well.

[0018] In one aspect, the present invention provides a method performed by a user equipment (UE) configured to communicate via a Non-Terrestrial Network (NTN) including a plurality of cells, the method comprising: receiving, from a network node, information regarding switching of a communication connection from a first cell to a second cell of the NTN; based on the received information, suspending the communication connection in the first cell and maintaining a Radio Resource Control (RRC) configuration associated with the first cell; performing a cell switch based on the received information to select the second cell; receiving a trigger to perform a random access procedure via the second cell; and after successful completion of the random access procedure, resuming the communication connection in the second cell using the RRC configuration associated with the first cell.

[0019] In one aspect, the present invention provides a method performed by a user equipment (UE) configured to communicate via a Non-Terrestrial Network (NTN) including a plurality of cells, the method comprising: receiving from a network node a Radio Resource Control (RRC) reconfiguration message including information regarding switching of a communication connection from the first cell to a second cell of the NTN and information regarding an RRC configuration to be applied to the second cell; performing a cell switch based on the received information to select the second cell; receiving a trigger to perform a random access procedure via the second cell; and resuming the communication connection in the second cell using the RRC configuration after successful completion of the random access procedure.

[0020] In one aspect, the present invention provides a method performed by a network node configured to communicate with user equipment (UE) via a Non-Terrestrial Network (NTN) comprising a plurality of cells, the method comprising: transmitting, to the at least one UE, information regarding switching of a communication connection from a first cell to a second cell of the NTN, the information being used by the at least one UE in performing a cell switch to select a second cell; maintaining a Radio Resource Control (RRC) configuration associated with the first cell when the UE discontinues the communication connection in the first cell; transmitting a trigger for the at least one UE to initiate a random access procedure via the second cell; and resuming, in the second cell, a communication connection using the RRC configuration associated with the first cell after successful completion of the random access procedure.

[0021] In one aspect, the present invention provides a method performed by a network node configured to communicate with user equipment (UE) via a Non-Terrestrial Network (NTN) comprising a plurality of cells, the method comprising: sending, to at least one UE, a Radio Resource Control (RRC) reconfiguration message including information regarding switching of a communication connection from a first cell to a second cell of the NTN and information regarding an RRC configuration to be applied to the second cell; sending a trigger for the at least one UE to initiate a random access procedure via the second cell; and resuming the communication connection in the second cell using the RRC configuration after successful completion of the random access procedure.

[0022] In one aspect, the present invention provides a user equipment (UE) configured to communicate over a non-terrestrial network (NTN) including a plurality of cells, the UE comprising a controller and a transceiver, the controller receiving from a network node information relating to switching of a communication connection from a first cell to a second cell of the NTN, suspending the communication connection in the first cell based on the received information and maintaining a Radio Resource Control (RRC) configuration associated with the first cell, performing a cell switch based on the received information to select the second cell, receiving a trigger to perform a random access procedure via the second cell, and resuming the communication connection in the second cell using the RRC configuration associated with the first cell after the random access procedure has been successfully completed.

[0023] In one aspect, the present invention provides a user equipment (UE) configured to communicate over a non-terrestrial network (NTN) including a plurality of cells, the UE comprising a controller and a transceiver, the controller receiving from a network node a Radio Resource Control (RRC) reconfiguration message including information regarding switching of a communication connection from a first cell to a second cell of the NTN and information regarding an RRC configuration to be applied to the second cell, performing a cell switch based on the received information to select the second cell, receiving a trigger to perform a random access procedure via the second cell, and resuming the communication connection in the second cell using the RRC configuration after successful completion of the random access procedure.

[0024] In one aspect, the present invention provides a network node configured to communicate with user equipment (UE) via a Non-Terrestrial Network (NTN) comprising a plurality of cells, the network node comprising a controller and a transceiver, the controller transmitting to the at least one UE information relating to switching of a communication connection from a first cell to a second cell of the NTN, the information being used by the at least one UE in performing a cell switch to select a second cell, maintaining a Radio Resource Control (RRC) configuration associated with the first cell when the UE discontinues the communication connection in the first cell, transmitting a trigger for the at least one UE to initiate a random access procedure via the second cell, and resuming, in the second cell, the communication connection using the RRC configuration associated with the first cell after the random access procedure has been successfully completed.

[0025] In one aspect, the present invention provides a network node configured to communicate with user equipment (UE) via a Non-Terrestrial Network (NTN) comprising a plurality of cells, the network node comprising a controller and a transceiver, the controller sending to the at least one UE a Radio Resource Control (RRC) reconfiguration message including information regarding switching of a communication connection from a first cell to a second cell of the NTN and information regarding an RRC configuration to be applied to the second cell, sending a trigger for the at least one UE to initiate a random access procedure via the second cell, and resuming the communication connection in the second cell using the RRC configuration after successful completion of the random access procedure.

[0026] In one aspect, the present invention provides a user equipment (UE) configured to communicate via a Non-Terrestrial Network (NTN) including a plurality of cells, the UE comprising: means for receiving, from a network node, information regarding switching of a communication connection from a first cell to a second cell of the NTN; means for suspending the communication connection in the first cell and maintaining a Radio Resource Control (RRC) configuration associated with the first cell based on the received information; means for performing a cell switch based on the received information to select the second cell; means for receiving a trigger to perform a random access procedure via the second cell; and means for resuming the communication connection in the second cell using the RRC configuration associated with the first cell after the random access procedure has been successfully completed.

[0027] In one aspect, the present invention provides a user equipment (UE) configured to communicate via a Non-Terrestrial Network (NTN) comprising a plurality of cells, the UE comprising: means for receiving from a network node a Radio Resource Control (RRC) reconfiguration message including information regarding switching of a communication connection from a first cell to a second cell of the NTN and information regarding an RRC configuration to be applied to the second cell; means for performing a cell switch based on the received information to select the second cell; means for receiving a trigger to perform a random access procedure via the second cell; and means for resuming the communication connection in the second cell using the RRC configuration after successful completion of the random access procedure.

[0028] In one aspect, the present invention provides a network node configured to communicate with user equipment (UE) via a Non-Terrestrial Network (NTN) comprising a plurality of cells, the network node comprising: means for transmitting, to the at least one UE, information relating to switching of a communication connection from a first cell to a second cell of the NTN, the information being used by the at least one UE when performing a cell switch to select a second cell; means for maintaining a Radio Resource Control (RRC) configuration associated with the first cell when the UE interrupts the communication connection in the first cell; means for transmitting a trigger for the at least one UE to initiate a random access procedure via the second cell; and means for resuming, in the second cell, the communication connection using the RRC configuration associated with the first cell after successful completion of the random access procedure.

[0029] In one aspect, the present invention provides a network node configured to communicate with user equipment (UE) via a Non-Terrestrial Network (NTN) comprising a plurality of cells, the network node comprising: means for transmitting to the at least one UE a Radio Resource Control (RRC) reconfiguration message including information regarding switching of a communication connection from a first cell to a second cell of the NTN and information regarding an RRC configuration to be applied to the second cell; means for transmitting a trigger for the at least one UE to initiate a random access procedure via the second cell; and means for resuming the communication connection in the second cell using the RRC configuration after successful completion of the random access procedure.

[0030] Exemplary aspects of the invention extend to corresponding systems, apparatus, and computer program products, such as computer-readable storage media having stored thereon instructions operable, for example, to program a programmable processor to perform the methods in the exemplary aspects and implementations described above or recited in the claims, and / or operable to program a suitably configured computer to provide an apparatus recited in any of the claims.

[0031] Each feature disclosed in this specification (which term includes claims) and / or shown in the drawings may be incorporated into the invention separately (or in any combination) of the features disclosed and / or shown. In particular, but without limitation, elements of any claim dependent on a particular independent claim may be introduced into that independent claim in any combination or individually. Exemplary embodiments of the present invention will now be described, by way of example only, with reference to the accompanying drawings in which: [Brief explanation of the drawings]

[0032] [Figure 1] FIG. 1 illustrates schematically a mobile (cellular or wireless) communication system in which exemplary embodiments of the present invention may be applied. [Figure 2] FIG. 2 illustrates an exemplary feeder link switching scenario. [Figure 3] FIG. 3 illustrates an exemplary feeder link switching scenario. [Figure 4] FIG. 4 illustrates an exemplary feeder link switching scenario. [Figure 5] FIG. 5 is a schematic block diagram of a mobile device forming part of the system shown in FIG. [Figure 6] FIG. 6 is a schematic block diagram of an NTN node (e.g., a satellite / UAS platform) forming part of the system shown in FIG. [Figure 7] FIG. 7 is a schematic block diagram of an access network node (eg a base station) forming part of the system shown in FIG. [Figure 8] FIG. 8 is a signaling (timing) diagram illustrating an exemplary manner in which a handover may be performed in accordance with an exemplary embodiment of the present invention. [Figure 9] FIG. 9 is a signaling (timing) diagram illustrating an exemplary manner in which a handover may be performed in accordance with an exemplary embodiment of the present invention. [Figure 10] FIG. 10 is a signaling (timing) diagram illustrating an exemplary manner in which a handover may be performed in accordance with an exemplary embodiment of the present invention. [Figure 11] FIG. 11 is a signaling (timing) diagram illustrating an exemplary manner in which a handover may be performed in accordance with an exemplary embodiment of the present invention. [Figure 12] FIG. 12 is a signaling (timing) diagram illustrating an exemplary manner in which a handover may be performed in accordance with an exemplary embodiment of the present invention. [Figure 13] FIG. 13 is a signaling (timing) diagram illustrating an exemplary manner in which a handover may be performed in accordance with an exemplary embodiment of the present invention. [Figure 14] FIG. 14 illustrates schematically some exemplary architectural options for providing NTN functionality in the system shown in FIG. DETAILED DESCRIPTION OF THE INVENTION

[0033] overview FIG. 1 illustrates schematically a mobile (cellular or wireless) communication system 1 in which exemplary embodiments of the present invention may be applied.

[0034] In this system 1, users of mobile devices 3 (UE) can communicate with each other and other users via access network nodes of respective satellites 5 and / or base stations 6 and data network 7 using an appropriate 3GPP radio access technology (RAT), such as E-UTRA and / or 5G RAT. As those skilled in the art will appreciate, while three mobile devices 3, one satellite 5, and one base station 6 are shown in FIG. 1 for illustrative purposes, the system, when implemented, will typically include other satellite / UAS platforms, base stations / RAN nodes, and mobile devices (UE).

[0035] It will be appreciated that a number of base stations 6 form a (Radio) Access Network or (R)AN, and a number of Non-Terrestrial Networks (NTN) nodes 5 (satellite and / or UAS platforms) form the NTN. Each NTN node 5 is connected to an appropriate gateway (in this case co-located with the base station 6) using a so-called feeder link, and is connected to a respective UE 3 via a corresponding service link. Thus, when served by an NTN node 5, a mobile device 3 communicates data to and from a base station 6 via the NTN node 5 using the appropriate service link (between the mobile device 3 and the NTN node 5) and feeder link (between the NTN node 5 and the gateway / base station 6). In other words, the NTN forms part of the (R)AN, although it may also provide satellite communication services separate from E-UTRA and / or 5G communication services.

[0036] Although not shown in Figure 1, adjacent base stations 6 are connected to each other via appropriate base station-base station interfaces (such as so-called "X2" and / or "Xn" interfaces), and the base stations 6 are also connected to data network nodes via appropriate interfaces (such as so-called "S1", "NG-C" and / or "NG-U" interfaces).

[0037] The data (or core) network 7 (e.g., EPC in the case of LTE, or NGC in the case of NR / 5G) typically includes logical nodes (or “functions”) for supporting communications in the communication system 1 and for subscriber management, mobility management, charging, security, and call / session management (among other things). For example, the data network 7 in a “Next Generation” / 5G system will include user plane and control plane entities, such as one or more control plane functions (CPF) and one or more user plane functions (UPF). The data network 7 may also be coupled to other data networks, such as the Internet or similar Internet Protocol (IP)-based networks (not shown in FIG. 1 ).

[0038] Each NTN node 5 may control several directional beams and serve associated NTN cells via these beams. Specifically, each beam has an associated radio footprint on the Earth's surface that corresponds to the NTN cell. Each NTN cell (beam) has an associated Physical Cell Identity (PCI) and / or beam identifier. The beam footprint may move as the NTN node 5 moves along its orbit. Alternatively, the beam footprint may be fixed to the Earth, in which case a suitable beam pointing mechanism (mechanical or electronic steering) may be used to compensate for the movement of the NTN node 5.

[0039] From the perspective of a mobile device, cell changes occur periodically at discrete intervals due to service / feeder link switching necessitated by the movement of NTN nodes 5 along their orbits. Similarly, from the perspective of a gateway, feeder link changes occur at regular intervals due to the movement of satellites along their orbits. Both service link changes and feeder link changes may occur between different base stations / gateways (referred to herein as "inter-gNB radio link switching") or within the same base station / gateway ("intra-gNB radio link switching").

[0040] Figure 2 shows a schematic diagram of an exemplary inter-gNB feeder link switch scenario (feeder / service link switch with gNB / gateway change), while Figures 3 and 4 show two possible intra-gNB feeder link switch scenarios (feeder / service link switch without gNB change). In Figure 3, the base station 6 switches from a first (old) satellite 5A to a second (new) satellite 5B, and in Figure 4, the base station 6 switches from a first gateway to a second gateway for the same satellite 5 (the two gateways are provided via respective distributed units of the base station device 6).

[0041] To facilitate handover of mobile devices 3 served via NTN nodes 5, the system information transmitted by base stations 6 (via NTN nodes 5) includes information (e.g., appropriate system information blocks / information elements) indicating that a particular cell is leaving and a new cell is approaching. Thus, handover of multiple mobile devices 3 can be performed efficiently when a feeder / service link switch occurs.

[0042] In the case of an intra-gNB radio link switch, the mobile device 3 does not need to perform a Layer 3 handover (as in a normal handover between neighboring cells). Instead, the base station 6 / NTN node 5 serving the mobile device 3 instructs the mobile device 3 to synchronize with the new cell and resume its RRC connection in the new cell using the same Layer 2 protocol state and RRC configuration as that of the previous NTN cell. More specifically, upon leaving the previous NTN cell, the mobile device 3 suspends uplink data transmission and reselects to a suitable new cell. The mobile device 3 synchronizes with the new cell via a Random Access Channel (RACH) procedure and can then resume transmission in the new cell.

[0043] In the case of an inter-gNB radio link switch, the source and target base stations 6 (i.e., the source and target gateways of the NTN node 5) are configured to maintain the same UE context for the mobile device 3 being handed over before and after the link change, eliminating the need for the mobile device 3 to perform Layer 3 handover signaling. If multiple mobile devices 3 are being handed over, the source base station 6 can transfer all associated UE contexts to the target base station 6 at once. The remaining handover procedure (synchronization and communication resumption) is the same as for an intra-gNB radio link switch.

[0044] Advantageously, the nodes of the system are configured to distribute the signaling load resulting from handover of multiple mobile devices 3 upon change of feeder / service link. This may be achieved, for example, using one or more of the following options: 1) Using PDCCH orders: The source base station 6 may send legacy Physical Downlink Control Channel (PDCCH) orders to all connected UEs 3 in a distributed manner (sent to different UEs 3 at different times) for load balancing purposes. In this case, the legacy PDCCH orders may be used to trigger the RACH procedure and synchronization with the new cell. 2) Using a group / common PDCCH order: A common / group PDCCH order may be sent to all UEs 3 or a group of UEs 3 (identified by an associated common / group RNTI value). 3) Using MAC CE: Information related to random access (synchronization) may be carried within an appropriate Medium Access Control (MAC) Control Element (CE). 4) Using RRC signaling: The source base station 6 may send information related to the cell switch using an appropriate conditional RRC reconfiguration information element (via an RRC reconfiguration message) or using an appropriate group handover command message (via broadcasting).

[0045] User Equipment (UE) FIG. 5 is a block diagram illustrating the main components of the mobile device (UE) 3 shown in FIG. 1. As shown, the UE 3 includes transceiver circuitry 31 operable to transmit signals to and receive signals from at least one connected node via one or more antennas 33. While not necessarily shown in FIG. 5, the UE 3 will, of course, have all of the usual functionality of a conventional mobile device (such as a user interface 35), which may be provided by any one or any combination of hardware, software, and firmware, as appropriate. A controller 37 controls the operation of the UE 3, for example, according to software stored in memory 39. The software may be pre-installed in memory 39 and / or downloaded via the telecommunications network 1 or from a removable data storage device (RMD). The software includes, among other things, an operating system 41 and a communications control module 43.

[0046] The communication control module 43 is responsible for processing (generating / sending / receiving) signaling messages and uplink / downlink data packets between the UE 3 and other nodes, including NTN nodes 5, (R)AN nodes 6 and core network nodes. The signaling may include control signaling for handover and associated procedures (e.g. random access) due to changes in feeder / service links.

[0047] NTN Node (Satellite / UAS Platform) FIG. 6 is a block diagram illustrating the major components of the NTN node 5 (satellite or UAS platform) shown in FIG. 1. As shown, the NTN node 5 includes transceiver circuitry 51 operable to transmit signals to and receive signals from at least one connected UE 3 via one or more antennas 53, and to transmit signals to and receive signals from other network nodes, such as gateways and base stations (directly or indirectly). A controller 57 controls the operation of the NTN node 5 in accordance with software stored in memory 59. The software may be pre-installed in memory 59 and / or downloaded via the telecommunications network 1 or, for example, from a removable data storage device (RMD). The software includes, among other things, an operating system 61 and a communications control module 63.

[0048] The communication control module 63 is responsible for handling (generating / sending / receiving) signaling between the NTN node 5 (via the base station / gateway) and other nodes such as the UE 3, base station 6, gateways, and core network nodes. The signaling may include control signaling for handover and related procedures (e.g. random access) due to changes in feeder / service links.

[0049] Base station / gateway (access network node) FIG. 7 is a block diagram illustrating the main components of the gateway 6 (base station (gNB) or similar access network node) shown in FIG. 1 . As shown, the gateway 6 / gNB 6 includes transceiver circuitry 71 operable to transmit signals to and receive signals from at least one connected UE 3 via one or more antennas 73, and to transmit signals to and receive signals from other network nodes (directly or indirectly) via a network interface 75. The signals are transmitted to and received from the at least one UE 3 directly and / or via an NTN node 5, as appropriate. The network interface 75 typically includes an appropriate base station, e.g., a base station interface (e.g., X2 / Xn), and an appropriate base station, e.g., a core network interface (e.g., S1 / NG-C / NG-U). A controller 77 controls the operation of the base station 6 in accordance with software stored in memory 79. The software may be pre-installed in memory 79 and / or downloaded via the telecommunications network 1 or, for example, from a removable data storage device (RMD). The software includes, among other things, an operating system 81 and a communications control module 83 .

[0050] The communication control module 83 is responsible for handling (generating / sending / receiving) signaling between the base station 6 and other nodes such as the UE 3, NTN nodes 5, and core network nodes. The signaling may include control signaling for handovers and related procedures (e.g. random access) due to changes in feeder / service links.

[0051] Detailed Description As shown in Figures 2 to 4, the following feeder / service link change scenarios are possible: Scenario 1: Inter-gNB radio link switching (feeder link switching to a different gNB) In this case, the satellite 5 first connects to a first (source) base station / gateway 6A and then to a second (destination) base station / gateway 6B serving the same area. Scenario 2: Intra-gNB radio link switching (service link switching or feeder link switching without changing the gNB)

[0052] For all scenarios, the system information may include information that a particular cell is leaving and a new cell is approaching. The handover baseline is expected to use legacy (conditional) handover, i.e., conditional reconfiguration with synchronization procedures in the new cell.

[0053] In the case of an intra-gNB radio link switch (scenario 2 above), the base station 6 / NTN node 5 serving the mobile device 3 instructs the mobile device 3 to synchronize with the new cell and resume its RRC connection in the new cell using the same Layer 2 protocol state and RRC configuration as that of the previous NTN cell. The mobile device 3 can suspend transmission in the NTN cell it is leaving, reselect the new NTN cell (i.e., a different beam), synchronize with the new cell by performing the appropriate RACH procedures, and then resume transmission in the new cell using the same Layer 2 protocol state and RRC configuration as the previous cell.

[0054] Advantageously, this approach does not require a layer 3 handover procedure and avoids the associated signaling. Below, several exemplary methods (methods 1 to 5) by which the above procedure can be implemented in the system shown in FIG. 1 are described.

[0055] Method 1 - PDCCH Order Based FIG. 8 is a signaling (timing) diagram illustrating an example procedure for performing handover without RRC reconfiguration (in the case of intra-gNB radio link switching). This procedure is based on a PDCCH order and includes the following steps: S1. The base station 6 (gNB) transmits information to the mobile devices 3 related to the cell switch. The information may include (implicitly or explicitly) information about leaving the current NTN cell and approaching a new NTN cell, and / or an indication that an intra-gNB cell switch should be performed without RRC reconfiguration. The information may be transmitted via broadcast or by transmitting an appropriate dedicated RRC message (or a combination of the two). The information may be transmitted to all mobile devices 3 (at least UEs in connected mode) that need to handover to the new NTN cell. In this example, the base station 6 transmits to the mobile device 3 information about: Timing of cell switching (handover), and · New cell PCI / SSB pattern (SSB raster). S2. At the indicated or calculated cell switch time, the mobile device 3 maintains its current RRC configuration and protocol state. The mobile device 3 also performs the following in preparation for the handover: At the MAC layer, the mobile device 3 may experience an expiration of a time alignment timer (TAT) associated with the current cell, which causes uplink transmission to be interrupted. Perform cell selection (switching) to the indicated new NTN cell, and Continue to monitor the PDCCH covered by the previous cell-specific Cell Radio Network Temporary Identifier (C-RNTI). Advantageously, step S2 may be performed by all connected mode UEs that need to handover to the new NTN cell (at the time indicated in step S1, e.g., either substantially simultaneously or at specific times indicated for each UE). S3. After the feeder / service link change is complete, the base station 6 (gNB) sends legacy PDCCH orders to all connected mode UEs 3. The PDCCH orders may be sent in a distributed manner (sent to different UEs at different times) for load balancing purposes. The legacy PDCCH order is used to trigger the UEs to perform the RACH procedure. A dedicated preamble can be indicated via the PDCCH order (unless ra-PreambleIndex is set to 0b000000, in which case a contention-based RACH procedure may be used). The following two approaches describe possible improvements to allow triggering a group of UEs to initiate a random access procedure at once: S4. Based on (i.e., upon receipt of) a PDCCH order targeted to mobile device 3 (by its C-RNTI), mobile device 3 performs the appropriate RACH procedure to resynchronize with the new NTN cell. S5. After the random access procedure is successfully completed, the mobile device 3 resumes uplink transmissions using the same configuration and the same protocol state. Therefore, the mobile device 3 does not need to change its security parameters and does not need to perform procedures for Radio Link Control (RLC) and Packet Data Convergence Protocol (PDCP) layer connection establishment.

[0056] Method 2 - Group / Common PDCCH Ordering This method is effectively the same as Method 1, with the following modifications: - A new RNTI value (common to all UEs or common to a group of UEs) is defined / configured in step S1. - The UE 3 monitors the configured or defined RNTI (instead of the C-RNTI) in step S2. - A common / group PDCCH order is sent to all UEs or a group of UEs in step S3. The common PDCCH order contains information indicating which UEs should use which RA resources when subsequently initiating the corresponding random access procedure (to synchronize with the new NTN cell) in step S4. For example, the information contained in the common / group PDCCH order may be in the form of a list such as: List of {UE identity#1 e.g. C-RNTI, preamble index, PRACH Mask Index(optional)} Step S4 is performed based on (when received) a group PDCCH order intended for all mobile devices 3 or a group of mobile devices 3 (by RNTI). Step S5 is the same as in Method 1.

[0057] Method 3 - MAC CE RA Order 9 is a signaling (timing) diagram illustrating another exemplary procedure for performing handover without RRC reconfiguration (in case of intra-gNB radio link switching). This procedure is similar to Approach 2, but the information related to random access is carried in an appropriate Medium Access Control (MAC) Control Element (CE) instead of a PDCCH order (to avoid potential limitations on the size of the PDCCH payload).

[0058] In this example, the information transmitted in step S1 includes the new RNTI value (common to all UEs or common to a group of UEs). UE3 (connected UE) monitors the configured / defined RNTI in step S2. In step S3, the common PDCCH schedules a PDSCH transmission carrying the appropriate MAC CE indicating which UEs need to use which random access resources when initiating a random access procedure to synchronize to the new NTN cell. In this example, the MAC CE includes the following random access related information: List of {UE identity#1 e.g. C-RNTI, preamble index, PRACH Mask Index(optional)} Step S4 is performed based on the information contained in the MAC CE (ie, upon reception of the MAC CE). Step S5 is the same as in Method 1.

[0059] Method 4 - RRC signaling based 10 is a signaling (timing) diagram illustrating yet another exemplary procedure for performing handover without RRC reconfiguration (in the case of intra-gNB radio link switching). The procedure uses RRC signaling and includes the following steps: S1. The base station 6 (gNB) transmits information to the mobile devices 3 related to the cell switch. The information may be transmitted using an appropriate RRC message (which may be transmitted via broadcasting) or using a group handover command / cell switch message. The information may be transmitted to all mobile devices 3 (at least UEs in connected mode) that need to hand over to the new NTN cell. In this example, the base station 6 transmits to the mobile device 3 information about: - Timing of cell switching (handover), PCI / SSB pattern of new cells (SSB raster), An indication (implicit or explicit) that an intra-gNB handover is to be performed at lower layers only (i.e. without further Layer 3 signaling), and Information identifying the appropriate RACH resource to be used (possibly including back-off values ​​for load control). S2. At the indicated or calculated cell switch time, the mobile device 3 maintains its current RRC configuration and protocol state. The mobile device 3 also performs the following in preparation for the handover: At the MAC layer, the mobile device 3 may experience an expiration of a time alignment timer (TAT) associated with the current cell, causing uplink transmission to be interrupted. -Perform cell selection (switching) for the specified new NTN cell. It will be appreciated that step S2 may be performed by all connected mode UEs that need to handover to a new NTN cell at the time indicated in step S1 (which may or may not be simultaneous). In this example, the base station 6 (gNB) does not need to send any additional signaling (e.g., legacy PDCCH order / MAC CE) to trigger synchronization with the new NTN cell, and therefore step S3 may be omitted. S4. The mobile device 3 performs the appropriate RACH procedures to resynchronize with the new NTN cell using the RACH resources configured via RRC signaling in step S1. S5. After successful completion of the random access procedure, the mobile device 3 resumes uplink transmissions using the same configuration and the same protocol state that was applicable to the previous NTN cell.

[0060] Method 5 - Hybrid (RRC+Group / Common PDCCH / MAC CE Order) 11 is a signaling (timing) diagram illustrating another exemplary procedure that is a combination of Method 4 and either Method 2 or 3. The procedure includes the following steps: S1. Step S1 is effectively the same as in technique 4 above, except that in this case the information sent using the RRC message or group handover command / cell switch message also includes information identifying the appropriate group C-RNTI for the group of UEs (or a C-RNTI common to all UEs). S2. This step is effectively the same as step S2 in Method 2. UE3 monitors the group / common C-RNTI. S3. The base station 6 sends a common / group PDCCH order (as in method 2) or a MAC CE RA order (as in method 3) targeted by the configured common / group C-RNTI, although it will be appreciated that this PDCCH order / MAC CE RA order may be simpler than the orders in methods 1 to 3, since the appropriate RACH resources have been pre-configured in step S1. Steps S4 and S5 are the same as above.

[0061] Method 6 - UE Context Transfer FIG. 12 is a signaling (timing) diagram illustrating an example procedure for performing a handover without RRC reconfiguration (in the case of an inter-gNB radio link switch).

[0062] In this case, the source and destination base stations 6 (i.e., the source and destination gateways of the NTN node 5) are configured to maintain an associated UE context for each mobile device 3 being handed over, eliminating the need for the mobile device 3 to perform Layer 3 handover signaling. In other words, the UE context may be the same before and after the handover.

[0063] Advantageously, the source base station 6A may be configured to transfer the UE context associated with the mobile device 3 (as generally shown in step S0 of Figure 12). If multiple mobile devices 3 need to be handed over, the source base station 6 may be configured to transfer all associated UE contexts simultaneously to the target base station 6 (e.g., using a single UE context transfer message or a series of UE context transfer messages).

[0064] The remainder of the procedure (synchronization and resumption of communication) may be implemented in a similar manner as described above for the intra-gNB radio link switching case.

[0065] Advantageously, this approach does not require a layer 3 handover procedure and also makes it possible to avoid or minimize the associated signaling.

[0066] Method 7 - Hybrid (RRC+Group / Common PDCCH / MAC CE RA Order) 13 is a signaling (timing) diagram illustrating an example procedure for performing handover using RRC reconfiguration. This procedure may be applied to both intra-gNB and inter-gNB radio link switching.

[0067] In effect, this procedure reuses the existing Layer 3 handover procedure, namely RRC reconfiguration with synchronization, with the following differences: In this case, the UE 3 monitors PDCCH / MAC CE RA orders to trigger the random access procedure instead of immediately initiating random access upon cell reselection (as in legacy Layer 3 handover). Thus, the base station 6 can control the timing of handover per UE or per UE group using appropriately formatted PDCCH or MAC CE RA orders.

[0068] In more detail, the procedure includes the following steps: S1. The base station 6 (gNB) sends information to the mobile devices 3 related to the cell switch, either via an RRC reconfiguration message using an appropriate conditional RRC reconfiguration information element, or via a group handover command message (which may be sent via broadcasting). The information may be sent to all (or a group of) mobile devices 3 that need to handover to the new NTN cell. In this example, the base station 6 transmits to the mobile device 3 information about: - Timing of cell switching (handover), PCI / SSB pattern of new cells (SSB raster), RRC reconfiguration (conditional or normal handover), and Information identifying the appropriate RACH resource to be used and / or load control back-off values, and Group / common C-RNTI (as in Method 2). It will be appreciated that the information identifying the RACH resource is optional: if this information is not provided, the mobile device 3 will perform a contention-based random access procedure via the new cell. S2. At the indicated or calculated cell switch time, the mobile device 3 applies the received RRC configuration and performs the following to prepare for handover: Perform cell selection (switching) to the indicated new NTN cell, and ·Start monitoring the PDCCH address for the configured common / group C-RNTI. S3. The base station 6 sends a common / group PDCCH order (as in method 2) or a MAC CE RA order (as in method 3) targeted by the common / group C-RNTI. Advantageously, this PDCCH order / MAC CE RA order can be simpler than the orders in methods 1-3, since the appropriate RACH resources are pre-configured in step S1. S4. After receiving the corresponding PDCCH order / MAC CE RA order, the mobile device 3 performs the appropriate RACH procedure to resynchronize with the new NTN cell. S5. After successful completion of the random access procedure, the mobile device 3 resumes uplink transmissions via the new NTN cell using the applicable new RRC configuration.

[0069] Variations and Substitutions Detailed exemplary embodiments have been described above. As those skilled in the art will appreciate, numerous modifications and alternatives can be made to the above exemplary embodiments and still obtain the benefits of the invention embodied therein. For purposes of illustration, only a few of these alternatives and modifications are described herein.

[0070] It will be understood that the above exemplary embodiments may be applied to both 5G New Radio and LTE systems (E-UTRAN). A base station (gateway) supporting E-UTRA / 4G protocols may be referred to as an "eNB," and a base station supporting Next Generation / 5G protocols may be referred to as a "gNB." It will be understood that some base stations may be configured to support both 4G and 5G protocols, and / or other 3GPP or non-3GPP communication protocols.

[0071] In the above description, when referring to a UE selecting a new cell, the terms "cell selection" or "cell switch" are used. This term is intended to encompass legacy cell selection methods (e.g., idle mode cell selection as defined in 3GPP TS in V16.3.0 of 38.304) and other similar mechanisms by which a UE leaves one cell and camps on another cell in preparation for reconnection via that cell.

[0072] It will be understood that cell selection may be the same or similar to a legacy or existing cell selection process in 5G NR, LTE, or 3G, or other radio access technologies. However, cell selection may be achieved by cell switching or by synchronizing to the downlink of a target cell. Cell switching may be performed, for example, by a UE switching its serving or camping cell from one cell to another in accordance with an RRC configuration received from a network node / base station device. Synchronization may be performed, for example, by a UE synchronizing to the downlink of a target cell and receiving necessary system information via that cell. However, if the UE already has the necessary timing information or if timing information is not required for random access, the UE may omit reading the Master Information Block (MIB). It will be understood that there are various architecture options for implementing NTN in a 5G system, some of which are schematically shown in FIG. 14. The first option shown is an NTN featuring an access network serving UEs, which is based on satellite / air with a bent-pipe payload and a terrestrial gNB (satellite hub or gateway level). The second option is an NTN featuring an access network serving UEs, which is based on satellite / air with a gNB. The third option is an NTN featuring an access network serving relay nodes, which is based on satellite / air with a bent-pipe payload. The fourth option is an NTN featuring an access network serving relay nodes, which is based on gNBs and satellite / air. It will be understood that other architecture options may also be used, for example, a combination of two or more of the above options. Alternatively, the relay node may include a satellite / UAS.

[0073] [Table 1]

[0074] In the above description, the UE, NTN node (satellite / UAS platform), and access network node (base station) are described for ease of understanding as having several separate modules (such as a communications control module). While these modules may be provided in this manner for a specific application, such as when an existing system is modified to implement the present invention, or for other applications, such as in a system designed from the beginning with the features of the present invention in mind, these modules may also be incorporated into an overall operating system or code, and thus may not be identifiable as separate entities. These modules may be implemented in software, hardware, firmware, or a combination thereof.

[0075] Each controller may comprise any suitable type of processing circuitry, including, but not limited to, one or more hardware-implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuitry, internal memory / cache (program and / or data), processing registers, communication buses (e.g., control, data, and / or address buses), direct memory access (DMA) facilities, hardware or software-implemented counters, pointers, and / or timers, etc.

[0076] In the above exemplary embodiment, several software modules have been described. As will be understood by those skilled in the art, the software modules may be provided in compiled or uncompiled form and may be supplied to the UE, NTN node, and access network node (base station) as a signal over a computer network or on a recording medium. Furthermore, the functions performed by some or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred because it facilitates updating the functionality of the UE, NTN node, and access network node (base station).

[0077] The above exemplary embodiments are also applicable to "non-mobile" or generally fixed user equipment, such as mobile devices, which may include MTC / IoT devices and the like.

[0078] The method may include receiving information regarding switching a communication connection from a first cell to a second cell of the NTN in at least one of an RRC message, a group handover command message, a cell switch message, and system information / broadcast signaling, where the information may be included in a conditional RRC reconfiguration information element.

[0079] The trigger may include at least one of a Physical Downlink Control Channel (PDCCH) order and a Medium Access Control (MAC) Control Element (CE). The trigger may include information identifying random access preambles for the UE (e.g., a list of UE identifiers and information identifying their respective random access preambles), and the method may include performing a random access procedure using the random access preambles so identified.

[0080] The information relating to the switch from the first cell to the second cell of the NTN may include information identifying the timing of the switch, a Physical Cell Identity (PCI) associated with the second cell, and / or a Synchronization Signal / Physical Broadcast Channel block (SSB) pattern associated with the second cell.

[0081] The information relating to the switch from the first cell to the second cell of the NTN may include information identifying resources that the UE will use for a random access procedure via the new cell, and the method may include performing the random access procedure using the resources so identified.

[0082] The information regarding the switch from the first cell to the second cell of the NTN may include identifiers of multiple UEs including the UE (e.g., group / common cell specific radio network temporary identifier, C-RNTI), and the trigger may be targeted to the identifiers.

[0083] The information regarding the switch from the first cell to the second cell of the NTN may include an indication that intra-gNB cell switch is performed without RRC reconfiguration.

[0084] The network node may include a gateway or a base station (eg, a target base station).

[0085] The method may further include transferring a UE context associated with the UE from another network node that controls the first cell before resuming the communication connection in the second cell.

[0086] Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0087] All or part of the embodiments disclosed above may be described as, but not limited to, the following supplementary notes.

[0088] [Appendix 1] 1. A method performed by user equipment (UE) configured to communicate over a non-terrestrial network (NTN) including a plurality of cells, the method comprising: receiving, from a network node, information regarding a switch of a communication connection from a first cell to a second cell of said NTN; suspending a communication connection in the first cell based on the received information and maintaining a Radio Resource Control (RRC) configuration associated with the first cell; performing a cell switch based on the received information to select the second cell; receiving a trigger to perform a random access procedure over the second cell; and and resuming, in the second cell, a communication connection using the RRC configuration associated with the first cell after the random access procedure has been successfully completed.

[0089] [Appendix 2] 2. The method of claim 1, comprising receiving the information regarding switching of a communication connection from a first cell to a second cell of the NTN in at least one of an RRC message, a group handover command message, a cell switch message, and system information / broadcast signaling.

[0090] [Appendix 3] 3. The method of claim 1, wherein the information is included in a conditional RRC reconfiguration information element.

[0091] [Appendix 4] 4. The method of any one of Supplementary Notes 1 to 3, wherein the trigger includes at least one of a Physical Downlink Control Channel (PDCCH) order and a Medium Access Control (MAC) Control Element (CE).

[0092] [Appendix 5] The trigger includes information identifying random access preambles for the UE (e.g., a list of UE identifiers and information identifying their respective random access preambles); the method comprising performing the random access procedure using the random access preamble so identified. 5. The method of any one of appendices 1 to 4.

[0093] [Appendix 6] 6. The method of any one of claims 1 to 5, wherein the information regarding the switch from the first cell to the second cell of the NTN includes information identifying a timing regarding the switch, a Physical Cell Identity (PCI) associated with the second cell, and / or a Synchronization Signal / Physical Broadcast Channel block (SSB) pattern associated with the second cell.

[0094] [Appendix 7] The information regarding the switch from the first cell to the second cell of the NTN includes information identifying resources used by the UE for a random access procedure via the new cell; the method comprising performing the random access procedure using the resources so identified. 7. The method of any one of appendices 1 to 6.

[0095] [Appendix 8] 8. The method of any one of Supplementary Notes 1 to 7, wherein the information regarding switching from the first cell to the second cell of the NTN includes identifiers (e.g., group / common cell specific radio network temporary identifiers, C-RNTIs) of multiple UEs including the UE, and the trigger is addressed to the identifiers.

[0096] [Appendix 9] The method of any one of Supplementary Notes 1 to 8, wherein the information regarding the switch from the first cell to the second cell of the NTN includes an indication that an intra-gNB cell switch is performed without RRC reconfiguration.

[0097] [Appendix 10] 10. The method of any one of Supplementary Notes 1 to 9, wherein the network node comprises a gateway or a base station.

[0098] [Appendix 11] 1. A method performed by user equipment (UE) configured to communicate over a non-terrestrial network (NTN) including a plurality of cells, the method comprising: receiving, from a network node, a Radio Resource Control (RRC) reconfiguration message including information regarding a switch of a communication connection from a first cell to a second cell of the NTN and information regarding an RRC configuration to be applied to the second cell; performing a cell switch based on the received information to select the second cell; and receiving a trigger to perform a random access procedure over the second cell; and and resuming the communication connection in the second cell using the RRC configuration after successful completion of the random access procedure.

[0099] [Appendix 12] The method of claim 11, wherein the information regarding switching of the communication connection from the first cell to the second cell of the NTN includes identifiers (e.g., group / common cell specific radio network temporary identifiers, C-RNTIs) of multiple UEs including the UE, and the trigger is addressed to the identifiers.

[0100] [Appendix 13] 13. The method of claim 11 or 12, wherein the trigger comprises at least one of a Physical Downlink Control Channel (PDCCH) order and a Medium Access Control (MAC) Control Element (CE).

[0101] [Appendix 14] 1. A method performed by a network node configured to communicate with each user equipment (UE) over a non-terrestrial network (NTN) comprising a plurality of cells, the method comprising: transmitting to the at least one UE information related to switching of a communication connection from the first cell to the second cell of the NTN, the information being used by the at least one UE in performing a cell switch to select a second cell; maintaining a Radio Resource Control (RRC) configuration associated with the first cell when the UE discontinues the communication connection in the first cell; sending a trigger for the at least one UE to initiate a random access procedure via the second cell; and and resuming, in the second cell, a communication connection using the RRC configuration associated with the first cell after the random access procedure has been successfully completed.

[0102] [Appendix 15] 1. A method performed by a network node configured to communicate with each user equipment (UE) over a non-terrestrial network (NTN) comprising a plurality of cells, the method comprising: transmitting, to at least one UE, a Radio Resource Control (RRC) reconfiguration message including information regarding a switch of a communication connection from the first cell to the second cell of the NTN and information regarding an RRC configuration to be applied to the second cell; sending a trigger for the at least one UE to initiate a random access procedure via the second cell; and and resuming the communication connection in the second cell using the RRC configuration after the random access procedure has been successfully completed.

[0103] [Appendix 16] the network node controls the second cell; 16. The method of claim 14 or 15, further comprising transferring a UE context associated with the UE from another network node that controls the first cell before resuming the communication connection in the second cell.

[0104] [Appendix 17] 1. A user equipment (UE) configured to communicate over a non-terrestrial network (NTN) including a plurality of cells, comprising: means for receiving, from a network node, information regarding a switch of a communication connection from the first cell to the second cell of the NTN; means for suspending a communication connection in the first cell based on the received information and maintaining a Radio Resource Control (RRC) configuration associated with the first cell; means for performing cell switching based on the received information to select the second cell; means for receiving a trigger to perform a random access procedure over the second cell; and means for resuming a communication connection in the second cell using the RRC configuration associated with the first cell after the random access procedure has been successfully completed.

[0105] [Appendix 18] 1. A user equipment (UE) configured to communicate over a non-terrestrial network (NTN) including a plurality of cells, comprising: means for receiving, from a network node, a Radio Resource Control (RRC) reconfiguration message comprising information regarding a switch of a communication connection from a first cell to a second cell of the NTN and information regarding an RRC configuration to be applied to the second cell; means for performing a cell switch based on the received information to select the second cell; means for receiving a trigger to perform a random access procedure over the second cell; and means for resuming the communication connection in the second cell using the RRC configuration after successful completion of the random access procedure.

[0106] [Appendix 19] 1. A network node configured to communicate with each user equipment (UE) via a non-terrestrial network (NTN) comprising a plurality of cells, the network node comprising: means for transmitting to the at least one UE information relating to switching of a communication connection from a first cell to the second cell of the NTN, the information being used by the at least one UE when performing a cell switch to select a second cell; means for maintaining a Radio Resource Control (RRC) configuration associated with the first cell when the UE discontinues the communication connection in the first cell; means for transmitting a trigger for the at least one UE to initiate a random access procedure via the second cell; and means for resuming, in the second cell, a communication connection using the RRC configuration associated with the first cell after the random access procedure has been successfully completed.

[0107] [Appendix 20] 1. A network node configured to communicate with each user equipment (UE) via a non-terrestrial network (NTN) comprising a plurality of cells, the network node comprising: means for transmitting to the at least one UE a Radio Resource Control (RRC) reconfiguration message, the RRC reconfiguration message including information regarding a switch of a communication connection from a first cell to a second cell of the NTN and information regarding an RRC configuration applied to the second cell; means for transmitting a trigger for the at least one UE to initiate a random access procedure via the second cell; means for resuming the communication connection in the second cell using the RRC configuration after the random access procedure has been successfully completed.

[0108] This application is a continuation of UK patent application no. 2100483.3 filed on 14 January 2021. No. 60 / 699,999, filed on Oct. 1, 2003, the disclosure of which is incorporated herein in its entirety.

Claims

1. means for receiving, from a network node, a Radio Resource Control (RRC) message including at least one of information indicating a Physical Cell Identity (PCI) and Synchronization Signal / Physical Broadcast Channel block (SSB) information regarding a switchover of a connection from a first cell to a second cell; means for releasing the connection in the first cell while maintaining a received RRC configuration in the first cell; means for performing a cell switch without RRC reconfiguration of the connection and selecting the second cell; means for re-establishing the connection using the RRC configuration in the second cell without RRC reconfiguration of the connection; Equipped with The switching to the second cell is triggered by a Medium Access Control (MAC) Control Element (CE), user equipment (UE).

2. The UE of claim 1 , wherein the RRC message includes information indicating resources to be used by the UE for a random access procedure via the second cell.

3. The UE according to claim 1 or 2, wherein the RRC message includes identifiers of a plurality of UEs including the UE.

4. The UE of claim 1 , wherein the RRC message includes an indicator indicating that an intra-base station cell switch should be performed without RRC reconfiguration.

5. means for transmitting, to a user equipment (UE), a Radio Resource Control (RRC) message including at least one of information indicating a Physical Cell Identity (PCI) and Synchronization Signal / Physical Broadcast Channel block (SSB) information regarding a connection switch from a first cell to a second cell; means for maintaining a Radio Resource Control (RRC) configuration received in the first cell when the UE releases the connection in the first cell and performs a cell switch to select the second cell without RRC reconfiguration of the connection; means for re-establishing the connection using the RRC configuration in the second cell without RRC reconfiguration of the connection; Equipped with The network node, wherein the switching to the second cell is triggered by a Medium Access Control (MAC) Control Element (CE).

6. means for controlling the second cell; means for receiving a UE context for the UE from another network node that controls the first cell before re-establishing the connection in the second cell; The network node of claim 5, comprising:

7. 7. A network node according to claim 5 or 6, comprising a gateway or a base station.

8. receiving, from a network node, a Radio Resource Control (RRC) message including at least one of information indicating a Physical Cell Identity (PCI) and Synchronization Signal / Physical Broadcast Channel block (SSB) information regarding a switchover of a connection from a first cell to a second cell; Releasing the connection in the first cell while maintaining a Radio Resource Control (RRC) configuration received in the first cell; performing a cell switch without RRC reconfiguration of the connection and selecting the second cell; re-establishing the connection using the RRC configuration without RRC reconfiguration of the connection in the second cell; Including, A method in a user equipment (UE), wherein the switching to the second cell is triggered by a Medium Access Control (MAC) Control Element (CE).

9. transmitting, to a user equipment (UE), a Radio Resource Control (RRC) message including at least one of information indicating a Physical Cell Identity (PCI) and Synchronization Signal / Physical Broadcast Channel block (SSB) information regarding a switchover of a connection from a first cell to a second cell; maintaining a Radio Resource Control (RRC) configuration received in the first cell when the UE releases the connection in the first cell and performs a cell switch to select the second cell without RRC reconfiguration of the connection; and re-establishing the connection using the RRC configuration without RRC reconfiguration of the connection in the second cell; Including, A method in a network node, wherein the switching to the second cell is triggered by a Medium Access Control (MAC) Control Element (CE).

Images