Communication system

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 operating 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 employing Non-Terrestrial Networks (NTN). [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 fixed devices in general) are typically operated by a user (and thus they are often collectively referred to as user equipment, "UE"), although it is also possible to connect IoT devices and similar MTC devices to the network. For simplicity, this application uses the term base station to refer to such base stations and the term mobile device or UE to refer to such communication devices.

[0003] The latest development in 3GPP standards is the so-called "5G" or "New Radio (NR)" standards, which refer to evolving communications technologies that are expected to support a variety of applications and services, such as, for example, 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) networks. Various details of 5G networks are described, for example, in the "NGMN 5G White Paper" V1.0 by the NGMN (Next Generation Mobile Networks) Alliance, which is 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 New Radio 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 (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 operates 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 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 based 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 based 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 and underserved areas and upgrade the performance of terrestrial networks. - Enhancing service reliability by providing service continuity to user equipment or to moving platforms (e.g. passenger aircraft, ships, high-speed trains, buses). - Increase service availability everywhere, especially for critical communications, future rail / maritime / aviation communications. - Enabling 5G network scalability through the provision of efficient multicast / broadcast resources for delivering data 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 a satellite system if the satellite does not provide direct service to 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 that connect satellite or aeronautical access networks to the core network ("NTN Gateways"). It will be appreciated 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 / air platform.

[0007] A satellite or aircraft may generate several beams over a given area to provide each NTN cell, 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). - Quasi-Earth fixed cells characterized by beams that cover one geographic area during one finite period and a different geographic area during another period (e.g. NGEO satellites generating steerable beams). - 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, e.g., 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 around 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 a suitable 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 case the beams are temporarily directed to a substantially fixed footprint on the Earth. In other words, the beam footprint (representing the NTN cell) remains stationary on the ground for a certain time before the focus area changes to another NTN cell (due to the satellite moving in its orbit). From a cell coverage / UE perspective, this results in cell changes occurring periodically at discrete intervals, 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 have a constant sweeping motion of the beams (cells) moving over the Earth as the satellite moves along its orbit, and as in the case of steerable beams, service link changes and therefore cell changes occur periodically at discrete intervals.

[0012] Similar to the service link change, the feeder link change also occurs at regular intervals as the satellite moves in orbit. Both the service link change and the feeder link change may be performed between different base stations / gateways (sometimes called "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 that a particular cell is leaving and a new cell is coming in 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 inter-gNB radio link switchover, Layer 3 (L3) handover (i.e., Radio Resource Control (RRC) reconfiguration) is required since the two base stations have independent radio resource management. In the case of intra-gNB radio link switchover, the same base station serves the same area before and after the feeder / service link switchover. However, since 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 the RRC configuration from before the switchover, but 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 in a 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] 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 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 information from a network node regarding a switch 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 resuming a communication connection in the second cell using the RRC configuration associated with the first cell after successful completion of the random access procedure.

[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, comprising: receiving from a network node a Radio Resource Control (RRC) reconfiguration message including information regarding a switch 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 each 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 relating to switching of a communication connection from a first cell to the second cell of the NTN, for use 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 interrupts 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 the random access procedure has been successfully completed.

[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: transmitting to at least one UE 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; transmitting 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 via a Non-Terrestrial Network (NTN) including a plurality of cells, the UE comprising a controller and a transceiver, the controller receiving information from a network node regarding switching of a communication connection from a first cell to a second cell of the NTN, interrupting 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 a communication connection in the second cell using the RRC configuration associated with the first cell after the random access procedure is successfully completed.

[0023] 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 a controller and a transceiver, the controller 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, 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 each 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 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 interrupts 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 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.

[0025] In one aspect, the present invention provides 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 a controller and a transceiver, the controller transmitting to the at least one UE 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, transmitting 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 information from a network node 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 a communication connection in the second cell using the RRC configuration associated with the first cell after the random access procedure is successfully completed.

[0027] 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 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; 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 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, for use by the at least one UE in 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, a communication connection using the RRC configuration associated with the first cell after the random access procedure has been successfully completed.

[0029] In one aspect, the present invention provides 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 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; 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 instructions stored thereon operable, for example, to program a programmable processor to perform the methods in the exemplary aspects and implementations recited above or in the claims, and / or 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 in the present invention separately (or in any combination) of the features disclosed and / or shown, and in particular, without limitation, any claim element dependent on a particular independent claim may be introduced in that independent claim in any combination or separately. Exemplary embodiments of the present invention will now be described, by way of example only, with reference to the accompanying drawings in which: [Brief description of the drawings]

[0032] [Figure 1] FIG. 1 illustrates generally a mobile (cellular or wireless) communication system in which exemplary embodiments of the invention may be applied. [Diagram 2] FIG. 2 illustrates an exemplary feeder link switching scenario. [Diagram 3] FIG. 3 illustrates generally an exemplary feeder link switching scenario. [Figure 4] FIG. 4 illustrates generally an exemplary feeder link switching scenario. [Diagram 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 example manner in which a handover may be performed in accordance with an example embodiment of the present invention. [Figure 9] FIG. 9 is a signaling (timing) diagram illustrating an example manner in which a handover may be performed in accordance with an example 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 generally some exemplary architectural options for the provision of NTN functionality in the system illustrated in FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0033] overview FIG. 1 illustrates diagrammatically a mobile (cellular or wireless) communication system 1 in which exemplary embodiments of the 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 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 one skilled in the art will appreciate, although three mobile devices 3, one satellite 5, and one base station 6 are shown in Figure 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 understood 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 connected to a respective UE 3 via a corresponding service link. Thus, when served by the NTN node 5, the mobile device 3 communicates data to and from the 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 separately from E-UTRA and / or 5G communication services.

[0036] Although not shown in Figure 1, neighbouring base stations 6 are connected to each other via suitable base station-base station interfaces (such as the so-called "X2" and / or "Xn" interfaces), and the base stations 6 are also connected to data network nodes via suitable interfaces (such as the 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 (among other things) subscriber management, mobility management, charging, security, and call / session management. For example, the data network 7 in a "Next Generation" / 5G system will include user plane entities 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 a similar Internet Protocol (IP)-based network (not shown in FIG. 1).

[0038] Each NTN node 5 may control several directional beams through which it serves its associated NTN cell. Specifically, each beam has an associated radio footprint on the surface of the Earth 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 mobile device's perspective, service / feeder link switching necessitated by the NTN nodes 5 moving along their orbits results in cell changes periodically at discrete intervals. Similarly, from the gateway's perspective, satellite movement along its orbit results in feeder link changes at regular intervals. 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 switching scenario (feeder / service link switching with gNB / gateway change), while Figures 3 and 4 show two possible intra-gNB feeder link switching scenarios (feeder / service link switching 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 being 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 efficiently performed when a feeder / service link switch occurs.

[0042] In case of intra-gNB radio link switching, the mobile device 3 does not need to perform a layer 3 handover (as in case of 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 transmission of uplink data and reselects to a suitable new cell. The mobile device 3 can synchronize with the new cell via a Random Access Channel (RACH) procedure and then resume transmission in the new cell.

[0043] In case of inter-gNB radio link switching, 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, so that the mobile device 3 does not need to perform layer 3 handover signaling. If multiple mobile devices 3 are handed over, the source base station 6 can transfer all related UE contexts to the target base station 6 at once. The remaining handover procedure (synchronization and communication resumption) is the same as in the case of intra-gNB radio link switching.

[0044] Advantageously, the nodes of the system are configured to distribute the signaling load due to handover of multiple mobile devices 3 upon change of feeder / service links. 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 a transceiver circuit 31 operable to transmit signals to and receive signals from at least one connected node via one or more antennas 33. Although 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 according to software stored, for example, in a memory 39. The software may be pre-installed in the 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 communication 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) Figure 6 is a block diagram illustrating the main components of the NTN node 5 (satellite or UAS platform) shown in Figure 1. As shown, the NTN node 5 includes a transceiver circuit 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 according to software stored in memory 59. The software may be pre-installed in memory 59 and / or downloaded via the telecommunications network 1 or from, for example, a removable data storage device (RMD). The software includes, among other things, an operating system 61 and a communication control module 63.

[0048] The communication control module 63 is responsible for handling (generating / sending / receiving) signaling between the NTN node 5 (through the base stations / gateways) and other nodes such as UEs 3, base stations 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 a transceiver circuit 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 and receive signals to and from other network nodes (directly or indirectly) via a network interface 75. The signals are transmitted to and received from at least one UE 3 directly and / or via an NTN node 5 as required. The network interface 75 typically includes a suitable base station, e.g., a base station interface (such as X2 / Xn), and a suitable base station, e.g., a core network interface (such as S1 / NG-C / NG-U). The controller 77 controls the operation of the base station 6 in accordance with software stored in a memory 79. The software may be pre-installed in the memory 79 and / or may be downloaded via the telecommunications network 1 or from, for example, 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, the NTN node 5, and the 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.

[0051] Detailed Description As shown in Figures 2 to 4, the following feeder / service link modification 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 gNB change)

[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 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 leaving NTN cell, reselect the new NTN cell (i.e., a different beam), synchronize with the new cell by performing an appropriate RACH procedure, 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 layer 3 handover procedures and avoids the associated signalling. Below, several exemplary methods (methods 1 to 5) are described in which the above procedure can be implemented in the system shown in FIG.

[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 the PDCCH order and includes the following steps: S1. The base station 6 (gNB) transmits information to the mobile devices 3 related to cell switching. The information may include (implicitly or explicitly) information about leaving a current NTN cell and approaching a new NTN cell, and / or an indication to perform intra-gNB cell switching 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 regarding: Timing of cell switching (handover), and · PCI / SSB pattern for new cells (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 detect that a time alignment timer (TAT) associated with the current cell expires, causing uplink transmission to be interrupted; Perform cell selection (switchover) 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 a specific time indicated for each UE). S3. After the feeder / service link change is completed, 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 refinements to be able to trigger 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 the mobile device 3 (by its C-RNTI), the mobile device 3 performs an 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, so 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 Order 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 eg C-RNTI, preambleindex, PRACH Mask Index(optional)} - Step S4 is performed based on (when received) a group PDCCH order which is 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 example procedure for performing handover without RRC reconfiguration (in case of intra-gNB radio link switching). The procedure is similar to Approach 2, but the random access related information is carried in a suitable 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 eg C-RNTI, preambleindex, 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 handover to the new NTN cell. In this example, the base station 6 transmits to the mobile device 3 information regarding: - 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 signalling); and · Information identifying the appropriate RACH resource to be used (possibly including a back-off value 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. Therefore, step S3 may be omitted. S4. The mobile device 3 performs the appropriate RACH procedure 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 showing another exemplary procedure, which 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 Method 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. UE 3 monitors the group / common C-RNTI. S3. The base station 6 sends a common / group PDCCH order (as in scheme 2) or a MAC CE RA order (as in scheme 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 schemes 1-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 handover without RRC reconfiguration (in the case of inter-gNB radio link switching).

[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, so that the mobile device 3 does not need 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 FIG. 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 layer 3 handover procedures and also makes it possible to avoid or minimize associated signalling.

[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 with RRC reconfiguration. This procedure may be applied to both intra-gNB radio link switching 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 for triggering 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 handover timing 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) transmits 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 transmitted via broadcasting). The information may be transmitted to all mobile devices 3 (or a group thereof) that need to handover to the new NTN cell. In this example, the base station 6 transmits to the mobile device 3 information regarding: - 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 A 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 over 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 (switchover) 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 an 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 may be made to the exemplary embodiments described above 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 is 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 NextGeneration / 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 term "cell selection" or "cell switching" is used. This term is intended to cover 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 where a UE leaves one cell and camps on another cell in preparation for reconnection via that cell.

[0072] It will be understood that the cell selection may be the same or similar process as the selection process of a legacy or existing cell in 5G NR, LTE, or 3G, or other radio access technology. However, the cell selection may be realized by cell switching or synchronizing to the downlink of the target cell. The cell switching may be performed, for example, in a manner in which the UE switches its serving cell or camping cell from one cell to another cell according to the RRC configuration received from the network node / base station device. The synchronization may be performed, for example, in a manner in which the UE can achieve synchronization to the downlink of the target cell and receive the necessary system information via that cell. However, if the UE already has the necessary timing information or if the 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 the 5G system, some of which are shown in FIG. 14 as a schematic diagram. The first option shown is an NTN featuring an access network serving UEs, based on satellite / aerial with bent-pipe payload and terrestrial gNB (satellite hub or gateway level). The second option is an NTN featuring an access network serving UEs, based on satellite / aerial with gNB. The third option is an NTN featuring an access network serving relay nodes, based on satellite / aerial with bent-pipe payload. The fourth option is an NTN featuring an access network serving relay nodes, based on gNB and satellite / aerial. 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 as having several separate modules (such as a communication control module) for ease of understanding. While these modules may be provided in this way for a specific application, for example where an existing system has been modified to implement the present invention, or for other applications, for example in a system designed from the beginning with the features of the present invention in mind, these modules may also be incorporated into the overall operating system or code, and therefore may not be identifiable as separate entities. These modules may be implemented in software, hardware, firmware, or a combination of these.

[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 those skilled in the art will appreciate, the software modules may be provided in compiled or uncompiled form and may be provided to the UE, NTN node, and access network node (base station) as a signal on a computer network or on a recording medium. Furthermore, the functions performed by part or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred as it facilitates updating the functions of the UE, NTN node, and access network node (base station) to update them.

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

[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, the information being 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 a random access preamble for the UE (e.g., a list of UE identifiers and information identifying the 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 a switch from the first cell to the second cell of the NTN may include information identifying a timing for 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 switching from the first cell to the second cell of the NTN may include information identifying resources for the UE to 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 identifier.

[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 destination 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 a part of the embodiments disclosed above may be described as, but is not limited to, the following supplementary notes.

[0088] [Appendix 1] 1. A method performed by a user equipment (UE) configured to communicate over a non-terrestrial network (NTN) including a plurality of cells, the method comprising: receiving information from a network node regarding a switch of a communication connection from a first cell to a second cell of the 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; and receiving a trigger to perform a random access procedure over the second cell; and and after the random access procedure is successfully completed, resuming a communication connection in the second cell using the RRC configuration associated with the first cell.

[0089] [Appendix 2] The method of claim 1, comprising receiving the information regarding a switch 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 or 2, wherein the information is included in a conditional RRC reconfiguration information element.

[0091] [Appendix 4] 4. The method of claim 1, 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 a random access preamble for the UE (e.g., a list of UE identifiers and information identifying their respective random access preambles); performing the random access procedure using the random access preamble so identified. 5. The method according to any one of claims 1 to 4.

[0093] [Appendix 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; performing the random access procedure using the resources so identified. 7. The method according to any one of claims 1 to 6.

[0095] [Appendix 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 an identifier (e.g., a group / common cell specific radio network temporary identifier, C-RNTI) of a plurality of UEs including the UE, and the trigger is addressed to the identifier.

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

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

[0098] [Appendix 11] 1. A method performed by a user equipment (UE) configured to communicate over a non-terrestrial network (NTN) including a plurality of cells, the method comprising: receiving a Radio Resource Control (RRC) reconfiguration message from a network node, 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 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 a communication connection from the first cell to the second cell of the NTN includes an identifier (e.g., a group / common cell specific radio network temporary identifier, C-RNTI) of a plurality of UEs including the UE, and the trigger is addressed to the identifier.

[0100] [Appendix 13] 13. The method of claim 11 or 12, wherein the trigger includes 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) via 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 after the random access procedure is successfully completed, resuming a communication connection in the second cell using the RRC configuration associated with the first cell.

[0102] [Appendix 15] 1. A method performed by a network node configured to communicate with each user equipment (UE) via 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 is 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] A user equipment (UE) configured to communicate over a non-terrestrial network (NTN) including a plurality of cells, means for receiving information from a network node 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 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 a communication connection in the second cell using the RRC configuration associated with the first cell after the random access procedure is successfully completed.

[0105] [Appendix 18] A user equipment (UE) configured to communicate over a non-terrestrial network (NTN) including a plurality of cells, 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] 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 a switch 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 in 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] 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 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 the random access procedure has been successfully completed.

[0108] This application is a subsidiary of UK patent application no. 2100483.3 filed on 14 January 2021. No. 6,313,939, the disclosure of which is incorporated herein in its entirety.

Claims

1. A means for receiving a Radio Resource Control (RRC) message from a network node, the 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 a resource that the UE should use 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. A 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 switching of a connection 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 without RRC reconfiguration of the connection to select 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 network node, wherein 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 according to claim 5 , comprising:

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

8. receiving a Radio Resource Control (RRC) message from a network node, the 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 in the second cell without RRC reconfiguration of the connection; 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 a Radio Resource Control (RRC) message to a user equipment (UE), the RRC message including at least one of information indicating a Physical Cell Identity (PCI) and Synchronization Signal / Physical Broadcast Channel block (SSB) information regarding switching 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 without RRC reconfiguration of the connection to select the second cell; re-establishing the connection using the RRC configuration in the second cell without RRC reconfiguration of the connection; Including, A method in a network node, wherein switching to the second cell is triggered by a Medium Access Control (MAC) Control Element (CE).

Images