Mechanism for supporting inactive UEs in NTN architecture

Abstract

Mechanisms for supporting inactive UEs in an NTN architecture. Example embodiments of the present disclosure relate to paging. In one embodiment, a method comprises receiving a message from a first network device, the message comprising at least Radio Access Network (RAN)-based Notification Area (RNA) information, the RNA information configured to a terminal device, the terminal device transitioning to or having transitioned to a Radio Resource Control (RRC) inactive state via the first network device; and determining, based on the message, a target paging procedure for the terminal device between an RNA-based paging procedure and another network-triggered paging procedure.

Description

TECHNICAL FIELD

[0001] Various example embodiments of the present disclosure generally relate to the field of telecommunications, and in particular, to methods, devices, apparatuses, and computer-readable storage media for supporting radio resource control (RRC) inactive user equipment (UE) in non-terrestrial network (NTN) architecture or non-NTN architecture. BACKGROUND

[0002] Non-terrestrial network (NTN) refers to a network that utilizes radio frequency (RF) resources on board or space-borne platforms such as unmanned aerial vehicles (UAVs), high-altitude platform stations (HAPS), or satellites to provide communication services. These platforms are equipped with transmission equipment relay nodes or base stations to facilitate communication with ground user equipment. NTN can be applied to various applications, including enhanced mobile broadband (eMBB) and massive machine type communications (mMTC). In addition, paging is proposed, which is generally used when a UE is not in an active state (i.e., the UE is not currently communicating with the network). When the network has data or signaling to be transmitted to a specific UE, the network will initiate a paging procedure by sending a paging message. Therefore, it is worth studying the paging procedure in the NTN scenario. SUMMARY

[0003] In a first aspect of the present disclosure, a core network device is provided. The core network device includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the core network device to: receive a message from a first network device, the message including at least radio access network (RAN)-based notification area (RNA) information configured to a terminal device that has transitioned to or is transitioning to a radio resource control (RRC) inactive state via the first network device; and determine a target paging procedure for the terminal device between a RNA-based paging procedure and another network triggered paging procedure based on the message.

[0004] In a second aspect of the present disclosure, a first network device is provided. The first network device includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the first network device to: transmit a message to a core network device, the message including at least radio access network (RAN)-based notification area (RNA) information configured to a terminal device that has transitioned to or is transitioning to a radio resource control (RRC) inactive state via the first network device.

[0005] In a third aspect of the disclosure, a second network device is provided. The second network device includes at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the second network device to: receive, from a core network device, a request, the request including at least information of a radio access network (RAN) notification area (RNA) configured to a terminal device; and determine at least one cell belonging to the RNA; and transmit, to the terminal device, a paging message through the at least one cell, wherein the terminal device is transferred to a radio resource control (RRC) inactive state via a first network device, and the first network device has no interface with the second network device.

[0006] In a fourth aspect of the disclosure, a method is provided. The method includes: receiving, at a core network device and from a first network device, a message, the message including at least information of a radio access network (RAN) notification area (RNA) configured to a terminal device, the terminal device being transferred to or having been transferred to a radio resource control (RRC) inactive state via the first network device; and determining, based on the message, a target paging procedure for the terminal device between a RNA-based paging procedure and another network triggered paging procedure.

[0007] In a fifth aspect of the disclosure, a method is provided. The method includes: transmitting, at a first network device and to a core network device, a message, the message including at least information of a radio access network (RAN) notification area (RNA) configured to a terminal device, the terminal device being transferred to or having been transferred to a radio resource control (RRC) inactive state via the first network device.

[0008] In a sixth aspect of the disclosure, a method is provided. The method includes: receiving, at a second network device and from a core network device, a request, the request including at least information of a radio access network (RAN) notification area (RNA) configured to a terminal device; and determining at least one cell belonging to the RNA; and transmitting, to the terminal device, a paging message through the at least one cell, wherein the terminal device is transferred to a radio resource control (RRC) inactive state via a first network device, and the first network device has no interface with the second network device.

[0009] In a seventh aspect of the disclosure, a core network device is provided. The core network device includes means for receiving, from a first network device, a message, the message including at least information of a radio access network (RAN) notification area (RNA) configured to a terminal device, the terminal device being transferred to or having been transferred to a radio resource control (RRC) inactive state via the first network device; and means for determining, based on the message, a target paging procedure for the terminal device between a RNA-based paging procedure and another network triggered paging procedure.

[0010] In an eighth aspect of the disclosure, a first network device is provided. The first network device comprises means for transmitting a message to a core network device, the message comprising at least radio access network, RAN, based notification area, RNA, information, the RNA information being configured to a terminal network, the terminal network being switched to or having been switched to a radio resource control, RRC, inactive state via the first network device.

[0011] In a ninth aspect of the disclosure, a second network device is provided. The second network device comprises means for receiving a request from a core network device, the request comprising at least radio access network, RAN, based notification area, RNA, information, the RNA information being configured to a terminal device; and means for determining at least one cell belonging to the RNA; and means for transmitting a paging message to the terminal device via the at least one cell, wherein the terminal device is switched to a radio resource control, RRC, inactive state via a first network device, the first network device not having an interface with the second network device.

[0012] In a tenth aspect of the disclosure, a computer readable medium is provided. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to one of the fourth, fifth or sixth aspects.

[0013] It should be understood that the summary is not intended to identify key or essential features of embodiments of the disclosure, nor is it intended to limit the scope of the disclosure. Other features of the disclosure will be readily apparent from the following description. BRIEF DESCRIPTION OF DRAWINGS

[0014] Some example embodiments will now be described with reference to the drawings, in which:

[0015] Figure 1 An example communication environment in which example embodiments of the disclosure can be implemented is shown;

[0016] Figure 2A And Figure 2B A schematic diagram of an NTN architecture with network equipment on an NTN device in which example embodiments of the disclosure can be implemented is shown;

[0017] Figure 3 A signaling flow of a network triggered paging procedure according to some example embodiments of the disclosure is shown;

[0018] Figure 4 A signaling flow of an RNA paging procedure according to some example embodiments of the disclosure is shown;

[0019] Figure 5A And Figure 5B Signaling flows of paging procedures according to some example embodiments of the disclosure are shown, respectively;

[0020] Figure 6 A flow diagram illustrating a method implemented at a core network device, in accordance with some example embodiments of the disclosure is shown;

[0021] Figure 7 A flow diagram illustrating a method implemented at a first network device, in accordance with some example embodiments of the disclosure is shown;

[0022] Figure 8 A flow diagram illustrating a method implemented at a second network device, in accordance with some example embodiments of the disclosure is shown;

[0023] Figure 9 A simplified block diagram of a device suitable for implementing example embodiments of the disclosure is shown; and

[0024] Figure 10 A block diagram of an example computer readable medium, in accordance with some example embodiments of the disclosure is shown.

[0025] In all of the drawings, like or similar reference numerals are used to refer to like or similar elements throughout different figures. DETAILED DESCRIPTION

[0026] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described for illustrative purposes only and help to understand and implement the present disclosure, without implying any limitation to the scope of the present disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0027] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0028] Reference within this disclosure to “one embodiment”, “an embodiment”, “example embodiments” or the like means that a particular feature, structure, or characteristic described is included in at least one embodiment, but not necessarily all embodiments, of what the described implementations can be. Furthermore, these phrases and words are not necessarily referring to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of those skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0029] It should be understood that although the terms "first," "second," etc., preceding the noun(s) herein may be used to describe various elements, these elements should not be limited to these terms. These terms are used only to distinguish one element from another, and they do not restrict the order of the noun(s). For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any or all combinations of one or more of the listed terms.

[0030] As used herein, “at least one of the following: ” and “at least one of ” and similar expressions, wherein the list of two or more elements is connected by “and” or “or”, means at least any one of these elements, or at least any two or more of these elements, or at least all of these elements.

[0031] As used herein, unless explicitly stated otherwise, the “response to A” execution step does not indicate that the step is executed immediately after “A” occurs, and may include one or more intermediate steps.

[0032] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the terms “comprising,” “including,” “having,” “possessing,” “containing,” and / or “covering,” as used herein, specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0033] As used in this application, the term "circuit" may refer to one or more or all of the following:

[0034] (a) Hardware circuit implementation only (e.g., implementation with only analog and / or digital circuits) and

[0035] (b) A combination of hardware circuitry and software, such as (if applicable):

[0036] (i) A combination of (multiple) analog hardware circuits and / or digital hardware circuits with software / firmware, and

[0037] (ii) Any part of a hardware processor having software (including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions) and

[0038] (c) The operation requires software (e.g., firmware) for the operation of (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or parts thereof, but the software may be absent when the operation does not require the software.

[0039] This definition of "circuit" applies to all uses of the term in this application, including in any claim. As a further example, as used in this application, the term "circuit" also covers only hardware circuitry or processors (or processors), or portions of hardware circuitry or processors and their accompanying software and / or firmware implementations. For example, if applicable to a particular claim element, the term "circuit" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0040] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), LTE (Long Term Evolution), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, sixth-generation (6G) communication protocols, and / or any other currently known or to be developed in the future. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will naturally be future types of communication technologies and systems that can implement this disclosure. The scope of this disclosure should not be considered limited to the systems described above.

[0041] As used herein, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives services. Depending on the terminology and technology applied, a network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Head (RH), a Remote Radio Head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low-power node (such as a femto or pico), a non-terrestrial network (NTN) or non-terrestrial network equipment (such as satellite network equipment, low Earth orbit (LEO) satellites, and geostationary Earth orbit (GEO) satellites), an aircraft network equipment, etc. In some example embodiments, the Radio Access Network (RAN) split architecture includes a central unit (CU) and a distributed unit (DU) at the IAB donor node. An IAB node includes a mobile terminal (IAB-MT) portion similar to the UE facing the parent node, and the DU portion of the IAB node is similar to the base station facing the next-hop IAB node.

[0042] The term "terminal device" refers to any end device with wireless communication capabilities. As an example and not a limitation, a terminal device can refer to communication equipment, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices can include, but are not limited to, mobile phones, cellular phones, smartphones, VoIP phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image acquisition terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, smart devices, wireless client devices (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile terminal MT portion of an IAB node (e.g., a relay node). In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0043] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication, such as communication between a terminal device and a network device, including resources in the time domain, frequency domain, spatial domain, code domain, or any other combination of time-domain, frequency-domain, spatial-domain, and / or code-domain resources that enable communication. In the following, unless explicitly stated otherwise, resources in the frequency and time domains will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. Note that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0044] In the context of NTN, the term "regenerative architecture" refers to a type of satellite payload that not only performs RF filtering, frequency conversion, and amplification but also possesses onboard processing capabilities such as demodulation / decoding, switching and / or routing, and encoding / modulation. This means that the satellite is not merely a simple signal transponder but a complex communication node with base station functions capable of digital signal processing. In a regenerative payload NTN architecture, the satellite can perform tasks typically performed by base stations in terrestrial networks, such as processing user data and implementing network protocols and algorithms.

[0045] The term "RRC Idle" / "RRC_IDLE" used in this document refers to a low-activity state designed to conserve battery life and manage UE mobility in the absence of active communication. In this state, the UE does not actively participate in data transmission but can still receive system information and paging messages. The term "RRC Connected" / "RRC_CONNECTED" used in this document refers to an active state in which the UE can communicate directly with the network for data transmission and signaling. This state supports application data exchange and network control tasks such as handover. The term "RRC Inactive" / "RRC_INACTIVE" used in this document refers to a state in which the UE / terminal device maintains Connection Management (CM) - CONNECTED and can move within an area (RNA) configured by the Next Generation NG Radio Access Network (NG-RAN) without notifying the NG-RAN. In RRC_INACTIVE, the node that last served the gNB / network device maintains the UE context and the NG associated with the UE, along with the Serving Access and Mobility Management Function (AMF) and User Plane Function (UPF). The “RNA-based paging process” used in this article can refer to the paging process of an RRC INACTIVE UE, in which the core network device, rather than the last-serving network device, sends a paging request to (multiple) network devices based on the RAN-based notification area (RNA) for paging terminal devices / UEs.

[0046] Figure 1An example communication environment 100 in which exemplary embodiments of the present disclosure may be implemented is illustrated. Communication environment 100 includes multiple communication devices, including one or more network devices (such as network device 120-1, network device 120-2, and network device 120-3) and terminal devices 130. Communication environment 100 may also include core network equipment 110, such as AMF. The service area of ​​network device 120-1 may be referred to as cell 101, and the service area of ​​network device 120-3 may be referred to as cell 102. Each network device may serve one or more cells. The coverage area of ​​a cell (e.g., cell 102) may cover one or more tracking areas.

[0047] like Figure 1 As shown, the network device is connected to the same CN (i.e., core network device 110). Terminal device 130 transitions to RRC INACTIVE via network device 120-1. The RNA configured for terminal device 130 includes a cell identifier (ID) or RNA region ID associated with network device 120-2. Subsequently, terminal device 130 moves from the coverage area of ​​network device 120-1 to the coverage area of ​​network device 120-2. Core network device 110 needs to deliver mobility termination data or signaling to terminal device 130, therefore a network-triggered transition from RRC INACTIVE to RRC CONNECTED is performed.

[0048] Currently, transitions from RRC INACTIVE to RRC CONNECTED (e.g., network-triggered transitions) require an Xn interface between the last serving gNB / network device and the currently serving gNB / network device. However, for various reasons, an Xn interface may not exist between the last serving gNB / network device and the currently serving gNB / network device; for example, the operator may not have configured an Xn interface, or the Xn interface may have been removed when the mobile gNB / relay was moved. In this case, a method is needed to support RRC INACTIVE, and more specifically, to support transitions from RRC INACTIVE to RRC CONNECTED without relying on the Xn interface.

[0049] It should be understood that Figure 1 The number of devices and their connections shown are for illustrative purposes only and do not imply any limitation. Communication environment 100 may include any suitable number of devices configured to implement the exemplary embodiments of this disclosure. Although not shown, it should be understood that one or more additional devices may be located in cells 101 and 102, and one or more additional cells may be deployed in communication environment 100. In some exemplary embodiments, operations described in connection with terminal devices may be implemented at network devices or other devices, and operations described in connection with network devices may be implemented at terminal devices or other devices.

[0050] In some example embodiments, the transmission direction from the network device to the terminal device 130 is referred to as the downlink (DL), while the transmission direction from the terminal device 130 to the network device is referred to as the uplink (UL). In the DL, network devices 120-1 / 120-2 are transmitting (TX) devices (or transmitters), and terminal device 130 is a receiving (RX) device (or receiver). In the UL, terminal device 130 is a TX device (or transmitter), and the network device is an RX device (or receiver).

[0051] Communication in communication environment 100 can be implemented according to any and more suitable communication protocols, including but not limited to cellular communication protocols, wireless local area network communication protocols (such as IEEE 802.11), and / or any other currently known or future-developed protocols. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Discrete Fourier Transform Spread Spectrum (DFT-s-OFDM), and / or any other currently known or future-developed technologies.

[0052] Figure 2A It shows Figure 1 An example of a communication environment 100 is shown. Figure 2A As shown, network devices 120-1, 120-2, and 120-3 can be NTN devices. The coverage area of ​​a cell (e.g., cell 102) can cover one or more tracking areas. Note that NTN devices are merely examples of network devices.

[0053] Figure 2B A schematic diagram of an NTN regeneration architecture 200 having network devices on an NTN carrier (e.g., a satellite) that can implement an example embodiment of the present disclosure is shown. Figure 2B As shown, the NTN regeneration architecture 200 may include core network equipment 210 (such as AMF or UPF). In some example embodiments, Figure 1 The core network device 110 can be implemented on the core network device 210. The NTN regeneration architecture 200 may also include one or more NTN gateways (GWs) (such as NTN GW 220-1 and 220-2). When a satellite / gNB (such as gNB 230-1 and gNB 230-2) connects to the NTN-GW, the gNB is assigned one or more Internet Protocol (IP) addresses anchored in the NTN-GW. In some example embodiments, gNB 230-1 may refer to network device 120-1, and gNB 230-2 may refer to... Figure 1Network device 120-2 in the network. This ensures that DL control plane / user plane (CP / UP) traffic with the destination IP address set to the gNB's IP address is routed to the NTN-GW on the right, and then further forwarded to the satellite / gNB. Separate IP addresses can be assigned to the gNB for the control plane and user plane.

[0054] In a non-geostationary orbit (NGSO) NTN system, a stationary UE (e.g., terminal device 130) is served by different satellites at different times, and each satellite may only serve the terminal device for a few minutes. For example: between T1 and T2, the geographic area of ​​terminal device 130 is served by network device 120-1; between T2 and T3, due to the removal of network device 120-1, the geographic area of ​​terminal device 130 is served by network device 120-2; between T3 and T4, due to the removal of network device 120-2, the geographic area of ​​terminal device 130 is served by network device 120-3, where T1, T2, T3, and T4 represent different time points.

[0055] In the example NR NTN architecture, the Xn interface between gNBs / satellites can use an inter-satellite link (ISL). In this case, Xn is only available between adjacent satellites (e.g., between network device 120-1 and network device 120-2, and between network device 120-2 and network device 120-3), but there is no ISL / Xn between network device 120-1 and network device 120-3. For example, Xn / ISL can exist between gNBs / satellites in the same orbital plane. In another example, Xn / ISL can exist between gNBs / satellites in different orbital planes.

[0056] Figure 3 The signaling flow of a network-triggered paging procedure according to some example embodiments of this disclosure is illustrated. For example, such as Figure 3As shown, after terminal device 130 is in the RRC_INACTIVE state, network device 120-1 (the last serving gNB) can trigger RAN paging. Network device 120-1 can transmit the RAN paging request to network device 120-2 (the current gNB). Network device 120-2 can page terminal device 130. Terminal device 130 can recover from RRC_INACTIVE. In this case, support for RRC_INACTIVE depends on the availability of Xn between the last serving gNB and the current gNB. When the last serving gNB allocates RNA to the terminal device, the last serving gNB needs to consider Xn availability, for example, only considering the Tracking Area Identifier (TAI) of the (multiple) gNBs connected by Xn. Mobility termination (MT) signaling / data (in the case of buffering in the RAN) or RAN paging requests (in the case of buffering in the core network CN) can be sent to the last serving gNB. Due to ISL limitations, ISL / Xn is only available between adjacent gNBs. In some cases, since there is no Xn between the last serving gNB and the current gNB, the last serving gNB cannot request the current gNB to page the terminal device.

[0057] According to some example embodiments of this disclosure, a paging solution is provided. Specifically, a novel paging component is proposed to support network-triggered transitions from RRC_INACTIVE to RRC_CONNECTED in NRNTN systems. In this way, terminal devices can be paged even if there is no connection between the last served network device and the current network device. Since NRN devices behave like gNBs, Figure 4 to Figure 5B The NTN device used in this example is a gNB.

[0058] Example embodiments of this disclosure will now be described in detail with reference to the accompanying drawings. Note that although embodiments of this disclosure have been described with reference to an NTN scenario, embodiments of this disclosure may also be applied to non-NTN scenarios.

[0059] Figure 4 A paging signaling flow 400 according to some example embodiments of the present disclosure is illustrated. For illustrative purposes, reference is made to... Figure 1 The signaling flow 400 is described using core network device 110, network device 120-1, and network device 120-2 shown in the diagram. Terminal device 130 is transitioned to or has transitioned to an RRC inactive state via network device 120-1. For example, terminal device 130 simultaneously transitions to an RRC inactive state while within the coverage area of ​​network device 120-1 (i.e., cell 101).

[0060] In some example embodiments, network device 120-1 may determine a time point (2005) after which an RNA-based paging process is applied. For example, network device 120-1 may determine this time point based on its own trajectory information and the trajectory information of other network devices. In some example embodiments, this time point may be determined based on information defining when terminal device 130 is under or within the coverage area of ​​another network device that does not interface with network device 120-1. The coverage area may be a tracking area, RAN area, or cell. Alternatively or additionally, this time point may be determined based on when another network device begins servicing terminal device 130 that does not interface with network device 120-1. For example, this time point may be based on when the UE is in the coverage area of ​​network device 120-3 that does not interface with network device 120-1.

[0061] Network device 120-1 transmits a (2010) message to core network device 110, which includes at least RNA information configured to terminal device 130. That is, core network device 110 receives the (2010) message from network device 120-1. In some example embodiments, the RNA information may include a list of cell identifiers belonging to the RNA. For example, an explicit list of cells constituting the RNA may be provided to terminal device 130. Alternatively or additionally, the RNA information may include a list of RAN region identifiers. A RAN region identifier (ID), including a Tracking Area Code (TAC) and an optional RAN region code, may identify a RAN region. A RAN region is a subset of or equal to a CN tracking region. The RNA information may include cell IDs or RAN region IDs of one or more gNBs(s). The RNA information may be configured to terminal device 130, for example, by broadcasting it in system information.

[0062] In some example embodiments, messages may be transmitted when terminal device 130 transitions to an RRC inactive state. For example, the message may be included in an RRC inactive transition report message. In some other example embodiments, messages may be transmitted after terminal device 130 has transitioned to an RRC inactive state. For example, after terminal device 130 has transitioned to an RRC inactive state, the message may be included in a Next Generation Application Protocol (NGAP) message.

[0063] Based on the received (2010) message, core network device 110 determines (2020) a paging procedure for terminal device 130 between an RNA-based paging procedure and a paging procedure triggered by another network. For example, signaling or data may need to be transmitted to terminal device 130, and if terminal device 130 is in an RRC inactive state, terminal device 130 needs to be paged first. In some example embodiments, core network device 110 decides whether to perform an RNA-based paging procedure. In this case, the message of step (2010) may also include one or more of the following: an indication or time point regarding the transition to an RRC inactive state after which the RNA-based paging procedure is applied. After receiving an indication of MT data for terminal device 130 from another core network device (such as a UPF), core network device 110 can determine (2020) the target paging procedure based on the time and time point of receipt of the indication of the mobile termination data. For example, if the reception time is earlier than that point in time, core network device 110 can determine (2020) another network-triggered paging procedure as the target paging procedure. In this case, core network device 110 can transmit a request for the network-triggered paging procedure to network device 120-1. This is because it can be assumed that terminal device 130 is still in the coverage area of ​​network device 120-1, or in the coverage area of ​​network device 120-2 connected to network device 120-1. Alternatively, if the reception time is not earlier than that point in time, core network device 110 can determine (2020) an RNA-based paging procedure as the target paging procedure. This is because it can be assumed that terminal device 130 is no longer in the coverage area of ​​network device 120-1, or in the coverage area of ​​network device 120-2 connected to network device 120-1. In other words, terminal device 130 is in the coverage area of ​​a network device (e.g., network device 120-3) that is not connected to network device 120-1. In another example embodiment, when there is signaling (e.g., a NAS message) to be transmitted to the RRC INACTIVE UE, core network device 110 can perform a determination (2020). This determination can be based on the time of reception of the NAS message at the transport layer, or when the NAS message should be sent. See later. Figure 5A A detailed example embodiment describes how the core network device 110 determines whether to execute an RNA-based paging process.

[0064] In some other example embodiments, network device 120-1 determines whether to execute an RNA-based paging procedure. In this case, the message may also include an instruction to execute an RNA-based paging procedure. For example, the message may include a request for an RNA-based paging procedure. In some example embodiments, after receiving MT data or signaling for terminal device 130 from another core network device, network device 120-1 may determine the target paging procedure based on the reception time and time point of the mobile termination data or signaling. For example, if the reception time is earlier than that time point, network device 120-1 may determine that a paging procedure triggered by another network is the target paging procedure. In this case, network device 120-1 may transmit a paging message for paging terminal device 130 to network device 120-2 or terminal device 130. Alternatively, if the reception time is not earlier than that time point, network device 120-1 may determine that an RNA-based paging procedure is the target paging procedure. See below. Figure 5B A detailed example embodiment describes how network device 120-1 determines whether to perform an RNA-based paging process.

[0065] In some example embodiments, based on RNA information configured to terminal device 130, core network device 110 may identify at least one network device (such as network device 120-3) and then transmit (2040) a request for an RNA-based paging procedure to network device 120-3. In some example embodiments, the request may include one or more of the following: an indication that terminal device 130 is in an RRC inactive state, an identifier of a first network device, or RNA information configured to terminal device 130.

[0066] After receiving the request (2040), network device 120-3 determines (2050) at least one cell belonging to RNA. For example, network device 120-3 may determine cell 102 belonging to RNA. Network device 120-3 transmits a paging message (2050) to terminal device 130 through cell 102. In this way, the terminal device can be paged.

[0067] According to the reference Figure 4 The described example embodiment presents an RNA-based paging process. In this way, NW-triggered transitions from RRC_INACTIVE to RRC_CONNECTED are supported in NR NTN systems with a regenerative architecture.

[0068] Figure 5A A paging signaling flow 500 according to some example embodiments of the present disclosure is illustrated. For illustrative purposes, reference is made to... Figure 1The signaling flow 500 is described by the core network device 110, network device 120-1, network device 120-2, network device 120-3, terminal device 130, and core network device 520 shown in the figure.

[0069] Terminal device 130 can transition to an RRC inactive state (5005) via network device 120-1. Network device 120-1 can transmit an RRC INACTIVE TRANSITION REPORT message (5010) to core network device 130, reporting the UE transition to RRC INACTIVE. This message may include a new Information Element (IE), including the RNA assigned to terminal device 130. That is, RNA information can be transmitted in a new IE within the RRC INACTIVE TRANSITION REPORT message. The RNA information may include a list of cell IDs or RAN area IDs that can be served by more than one gNB. Alternatively, the RNA information may be included in any NGAP message, such as an MT communication processing request message based on the enhanced core network (CN).

[0070] In some embodiments, the message transmitted to core network device 130 (5010) also includes a time point, for example, RNA-based paging may be used after T3. That is, the indication of this time point can inform core network device 110 when paging should be performed based on RNA. Network device 120-1 can determine this time point based on when the next network device (e.g., network device 120-3) that does not have Xn with network device 120-1 begins serving the geographic area of ​​terminal device 130.

[0071] Network device 120-1 can know when the next(s) satellite(s) will serve the geographic area of ​​terminal device 130 and whether it has an Xn / ISL with the next satellite. For example, RNA-based paging can be used from T3 (i.e., when network device 120-3, which does not have an Xn with network device 120-1, begins to serve the geographic area of ​​terminal device 130).

[0072] When core network device 520 needs to transmit data (e.g., mobility termination data) to network device 120-1, core network device 520 may transmit an indication of (5016) MT data to core network device 110.

[0073] Core network device 110 can decide (5020) whether to use an RNA-based paging process / mechanism. For example, core network device 110 can make a decision based on an indication of when to receive MT data in core network device 110 or when core network device 110 needs to send signaling to terminal device 130, receive (5010) RNA information from network device 120-1, and the time point (e.g., T3).

[0074] For example, if the indication of MT data is received before T3 and between T1 and T2, network device 110 still serves the geographic area of ​​terminal device 130. In this case, core network device 110 can determine that the NW-triggered procedure is a paging procedure for paging terminal device 130. Alternatively, if the indication of MT data is received before T3 and between T2 and T3, network device 120-2 can serve the geographic area of ​​terminal device 130. Since network device 120-1 has an Xn interface with network device 120-2, core network device 110 can determine that the NW-triggered procedure is a paging procedure for paging terminal device 130. For example, refer to Figure 3 The paging process described can be applied to paging terminal equipment 130.

[0075] Alternatively, if an indication of MT data is received after T3, network device 120-3 may serve the geographic area of ​​terminal device 130. Since network device 120-3 does not have an Xn interface with network device 120-1, core network device 110 may determine that RNA-based paging is a paging procedure for terminal device 130. For example, if an indication of MT is received after time point (i.e., T3), core network device 110 may decide to initiate an NGAP paging procedure based on the received (5010) RNA information. For example, core network device 110 may determine to initiate an NGAP paging procedure to a list of network devices for RNA, such as all network devices (i.e., gNBs) involved in the RNA at the time of this paging. In this example, core network device 110 may not send paging requests to network devices 120-1 and 120-2 because they do not serve the geographic area of ​​terminal device 130. Core network device 110 may only send (5025) paging requests to network device 120-3.

[0076] For network devices in the list other than the last-served network device, core network device 110 can use NGAP paging messages with RNA information and indications that terminal device 130 is in an RRC inactive state without context in that gNB. Core network device 110 can also indicate the identifier of network device 120-1 to network device 120-3, which is the last-served gNB.

[0077] Based on RNA information, core network device 110 can identify the target network device (i.e., network device 120-3) and initiate an NGAP request procedure (e.g., an NGAP paging procedure) with RNA information to network device 120-3. For example, core network device 110 can send (5025) a paging request to network device 120-3.

[0078] Upon receiving a request, network device 120-3 may behave as if it has received an XnAP RAN PAGING message. For example, network device 120-3 may use RNA information to identify (multiple) cells to page terminal device 130 via Uu. Terminal device 130 may initiate a recovery procedure (5030).

[0079] Since network device 120-3 understands that network device 120-1 does not have Xn, network device 120-3 can transmit (5035) NGAP RETRIEVE UE CONTEXT REQUEST message, which may include one or more of the following: target gNB ID, i.e., the gNB ID of the last served gNB (i.e., network device 120-1), which is extracted from the inactive radio network temporary identifier (I-RNTI) received from terminal device 130 or has been received (5025) from core network device 110; source gNB ID, i.e., the gNB ID of the currently served gNB (i.e., network device 120-3); and tunnel endpoint information in network device 120-3, which allows network device 120-1 to forward DL data to network device 120-3 via a tunnel.

[0080] Since both network devices are connected to the same core network device 110, it is sufficient to use the I-RNTI's gNB ID for routing to the last serving gNB (i.e., network device 120-1). Core network device 110 can check the target gNB ID and forward the NGAP RETRIEVE UE CONTEXT REQUEST message to the last serving gNB (i.e., network device 120-1).

[0081] Network device 120-1 can transmit a (5040) NGAP RETREVE UE CONTEXT RESPONSE message to core network device 110. Then, core network device 110 can forward the NGAP RETRIEVE UE CONTEXT RESPONSE message to network device 120-3.

[0082] Network device 120-1 can forward DL data (5045) to network device 120-3. Network device 120-3 can send DL data to terminal device 130.

[0083] Figure 5B A paging signaling flow 500' according to some example embodiments of this disclosure is illustrated. For illustrative purposes, reference is made to... Figure 1 The core network device 110, network device 120-1, network device 120-2, network device 120-3, terminal device 130, and core network device 520 shown are used to describe signaling flow 500'. In this example, it is assumed that MT signaling / data is buffered in the last-served gNB (i.e., network device 120-1).

[0084] Terminal device 130 can switch to (5105) RRC inactive state via network device 120-1. Network device 120-1 can transmit (5110) RRC INACTIVE TRANSITION REPORT message to core network device 130 to report that the UE has switched to RRC INACTIVE.

[0085] In some embodiments, network device 120-1 can determine a time point, for example, when RNA-based paging should be used after T3. That is, the indication of this time point can inform core network device 110 when RNA-based paging should be performed. Network device 120-1 can determine the time indication based on when the next network device (e.g., network device 120-3) that does not have Xn with network device 120-1 begins serving the geographic area of ​​terminal device 130.

[0086] Network device 120-1 can know when the next(s) satellite(s) will serve the geographic area of ​​terminal device 130 and whether it has an Xn / ISL with the next satellite. For example, RNA-based paging can be used from T3 (i.e., when network device 120-3 no longer has an Xn with network device 120-1 to start serving the geographic area of ​​terminal device 130).

[0087] Core network device 520 can transmit (5115) MT data or signaling to network device 120-1. Network device 120-1 can decide (5120) whether to use an RNA-based paging mechanism / procedure. For example, network device 120-1 can make a decision based on when it receives MT data or signaling in network device 120-1, as well as RNA information and a time point (e.g., T3).

[0088] For example, if MT data or signaling is received before T3 and between T1 and T2, network device 110 still serves the geographic area of ​​terminal device 130. In this case, network device 120-1 can determine that the NW-triggered procedure is a paging procedure for paging terminal device 130. Alternatively, if MT data is received before T3 and between T2 and T3, network device 120-2 can serve the geographic area of ​​terminal device 130. Since network device 120-1 has an Xn interface with network device 120-2, network device 120-1 can determine that the NW-triggered procedure is a paging procedure for paging terminal device 130. For example, refer to Figure 3 The described paging procedure can be applied to paging terminal device 130. Alternatively, if MT data or signaling is received after T3, network device 120-3 can serve the geographic area of ​​terminal device 130. Since network device 120-3 does not have an Xn interface with network device 120-1, network device 120-1 can determine that the RNA-based paging procedure is for paging terminal device 130. Network device 120-1 can transmit a request message (5125) to core network device 110 to paging terminal device 130. The request message can be an enhancement of the current NGAP message, such as an enhancement of the current NGAP RRCINACTIVE TRANSITION REPORT message or a new NGAP message.

[0089] Based on RNA information, core network device 110 can identify the target network device (i.e., network device 120-3) and initiate an NGAP request procedure (e.g., NGAP paging procedure) with RNA information to network device 120-3. For example, core network device 110 can send (5130) a paging request to network device 120-3.

[0090] Upon receiving a request (e.g., an NGAP PAGING message), network device 120-3 may behave as if it has received an XnAP RAN PAGING message. For example, network device 120-3 may use RNA information to identify (multiple) cells to page terminal device 130 via Uu. Terminal device 130 may initiate a recovery procedure (5135).

[0091] Since network device 120-3 understands that there is no Xn with network device 120-1, network device 120-3 can transmit (5140) NGAP RETRIEVE UE CONTEXT REQUEST message, which may include one or more of the following: target gNB ID, i.e., the gNB ID of the last serving gNB (i.e., network device 120-1), which is extracted from the inactive radio network temporary identifier (I-RNTI) received from terminal device 130 or has been received (5130) from core network device 110; source gNB ID, i.e., the gNB ID of the currently serving gNB (i.e., network device 120-3); and tunnel endpoint information in network device 120-3, which allows network device 120-1 to forward DL data to network device 120-3 via a tunnel.

[0092] Since both network devices are connected to the same core network device 110, it is sufficient to use the I-RNTI's gNB ID for routing to the last serving gNB (i.e., network device 120-1). Core network device 110 can check the target gNB ID and forward the NGAP RETRIEVE UE CONTEXT REQUEST message to the last serving gNB (i.e., network device 120-1).

[0093] Network device 120-1 can transmit the (5145) NGAP RETREVE UE CONTEXT RESPONSE message to core network device 110. Then, core network device 110 can forward the NGAP RETRIEVE UE CONTEXT RESPONSE message to network device 120-3.

[0094] Network device 120-1 can forward DL data (5150) to network device 120-3. Network device 120-3 can send DL data to terminal device 130.

[0095] Figure 6 A flowchart of an example method 600 implemented at a core network device according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 The angle description method of the core network device 110 in the 600.

[0096] At box 610, the core network device receives a message from the first network device. The message includes at least notification area RNA information based on the radio access network (RAN). The RNA information is configured to the terminal device, which is transitioned to or has been transitioned to the radio resource control (RRC) inactive state via the first network device.

[0097] At box 620, based on the message, the core network device determines the target paging procedure for the terminal device between an RNA-based paging procedure and a paging procedure triggered by another network.

[0098] In some example embodiments, the message may also include at least one of the following: an indication of transition to an RRC inactive state, or a time point after which an RNA-based paging process is applied.

[0099] In some example implementations, messages are transmitted when the terminal device transitions to an RRC inactive state, or after the terminal device has already transitioned to an RRC inactive state.

[0100] In some example embodiments, the time point is based on information defining when the terminal device is in the coverage area of ​​another network device, where the first network device and the other network device do not have an interface, or the time point is based on when the other network device starts serving the terminal device, where the other network device and the first network device do not have an interface.

[0101] In some example embodiments, method 600 further includes: receiving an indication of mobility termination data for a terminal device from another core network device; and determining a target paging process based on the time and time point of receiving the indication of mobility termination data.

[0102] In some example embodiments, method 600 further includes: in response to a reception time earlier than a time point, determining another network-triggered paging process as the target paging process; and transmitting a request to a first network device for the network-triggered paging process.

[0103] In some example embodiments, method 600 further includes: determining an RNA-based paging process as a target paging process in response to a reception time not earlier than a certain point in time; determining at least one second network device based on RNA information configured to a terminal device; and transmitting a request for the RNA-based paging process to the at least one second network device.

[0104] In some example embodiments, method 600 further includes: in response to a message further including an instruction to perform an RNA-based paging process, determining an RNA-based paging process as the target paging process; determining at least one second network device based on RNA information configured to the terminal device; and transmitting a request for the RNA-based paging process to the at least one second network device.

[0105] In some example embodiments, the request includes at least one of the following: an indication that the terminal device is in an RRC inactive state, an identifier of a first network device, or RNA information configured to the terminal device.

[0106] In some example embodiments, the RNA information includes at least one of the following: a list of cell identifiers or a list of RAN region identifiers.

[0107] Figure 7 A flowchart of an example method 700 implemented at a first network device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 The angular description method of network device 120-1 in 700.

[0108] At box 710, the first network device transmits a message to the core network device. The message includes at least notification area RNA information based on the radio access network (RAN). The RNA information is configured to the terminal device, which is switched to or has been switched to the radio resource control (RRC) inactive state via the first network device.

[0109] In some example embodiments, method 700 further includes transmitting a message to a core network device, the message including a time point indicating when an RNA-based paging process should be applied.

[0110] In some example embodiments, method 700 further includes receiving a request from a core network device for a network-triggered paging procedure.

[0111] In some example embodiments, method 700 further includes: receiving mobility termination data or signaling for a terminal device from another core network device; and determining a target paging procedure based on the time of receipt of the mobility termination data or signaling, the time indicating when an RNA-based paging procedure should be applied.

[0112] In some example embodiments, method 700 further includes: determining, in response to a reception time earlier than a specific time point, that the network-triggered paging process is the target paging process. In some example embodiments, at block 720, the first network device transmits a paging message for paging a terminal device to a second network device or a terminal device.

[0113] In some example embodiments, method 700 further includes: determining the RNA-based paging process as the target paging process in response to a reception time not earlier than a time point; and transmitting a message to the core network device after the determination of the RNA-based paging process, the message further including an instruction to perform the RNA-based paging process.

[0114] In some example embodiments, method 700 further includes determining a point in time based on one of the following: defining information about when the terminal device is in the coverage area of ​​another network device, when the first network device does not have an interface with the other network device, or when the other network device begins to serve the terminal device, when the other network device does not have an interface with the first network device.

[0115] In some example embodiments, the message also includes an indication of transition to an RRC inactive state.

[0116] Figure 8 A flowchart of an example method 800 implemented at a second network device according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 The angular description method of network device 120-2 in 800.

[0117] At box 810, the second network device receives a request from the core network device. The request includes at least information about the notification area RNA based on the radio access network RAN, and the RNA information is configured to the terminal device.

[0118] At box 820, the second network device identifies at least one cell belonging to RNA.

[0119] At box 830, the second network device transmits a paging message to the terminal device via at least one cell. The terminal device transitions to an inactive Radio Resource Control (RRC) state via the first network device, and the first and second network devices do not have an interface.

[0120] In some exemplary embodiments, the request includes at least one of the following: an indication that the terminal device is in an inactive state, an identifier of a first network device, or RNA information configured to the terminal device.

[0121] In some example embodiments, any one of method 600 can be performed (e.g., Figure 1 The first means of the core network device 110 may include components for performing corresponding operations of method 600 or any embodiment thereof. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The first means may be implemented as or included in... Figure 1 Among the core network devices in the 110.

[0122] In some example embodiments, a second means capable of performing any of method 700 (e.g., network device 120-1 in the figures) may include components for performing corresponding operations of method 700 or any embodiment thereof. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The second means may be implemented as or included in... Figure 1 Network device 120-1.

[0123] In some example embodiments, any one of method 800 can be performed (e.g., Figure 1The third means of the network device 120-3 may include components for performing corresponding operations of method 800 or any embodiment thereof. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The third means may be implemented as or included in... Figure 1 Network device 120-3.

[0124] Figure 9 This is a simplified block diagram of a device 900 suitable for implementing exemplary embodiments of the present disclosure. Device 900 can be provided to implement a communication device, for example, Figure 1 The terminal device 130, network device, or core network device 110 shown are illustrated. As shown, device 900 includes one or more processors 910, one or more memories 920 coupled to processor 910, and one or more communication modules 940 coupled to processor 910.

[0125] Communication module 940 is used for bidirectional communication. Communication module 940 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface necessary for communication with other network elements. In some example embodiments, communication module 940 may include at least one antenna.

[0126] Processor 910 can be any type suitable for a local technology network and may include one or more of the following as non-limiting examples: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 900 may have multiple processors, such as application integrated circuit chips, which are time-subordinate to a clock synchronized with the main processor.

[0127] Memory 920 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory ROM 924, electrically programmable read-only memory EPROM, flash memory, hard disk, optical disc CD, digital video disc DVD, optical disc, laser disc, and other magnetic and / or optical memories. Examples of volatile memories include, but are not limited to, random access memory RAM 922 and other volatile memories that will not be maintained during power outages.

[0128] Computer program 930 includes computer-executable instructions that are executed by an associated processor 910. The instructions of program 930 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 930 may be stored in memory, such as ROM 924. Processor 910 can perform any suitable actions and processes by loading program 930 into RAM 922.

[0129] Example embodiments of this disclosure can be implemented using the method of procedure 930, such that device 900 can perform as described in the reference. Figure 2A to Figure 8 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or a combination of software and hardware.

[0130] In some example embodiments, program 930 may be tangibly contained in a computer-readable medium, which may be included in device 900 (such as in memory 920) or other storage devices accessible by device 900. Device 900 may load program 930 from the computer-readable medium into RAM 922 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. As used herein, the term "non-transitory" is a limitation of the medium itself (i.e., tangible, not tactile), and not a limitation of data storage persistence (e.g., RAM vs. ROM).

[0131] Figure 10 An example of a computer-readable medium 1000 is shown, which may be in the form of a CD, DVD, or other optical storage disk. The computer-readable medium 1000 has a program 930 stored thereon.

[0132] In general, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof, as examples of non-limiting examples.

[0133] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored on a computer-readable medium (such as a non-transitory computer-readable medium). The computer program product includes computer-executable instructions, such as those included in a program module, which are executed in a device targeting a physical or virtual processor to implement any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. The functionality of the program module can be combined or split as needed among program modules in various embodiments. The machine-executable instructions for the program module can be executed within a local or distributed device. In a distributed device, the program module can reside on both local and remote storage media.

[0134] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code enables the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0135] In the context of this disclosure, computer program code or related data may be carried on any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0136] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0137] Furthermore, although operations are described in a specific order, this should not be construed as requiring such operations to be performed in the specific order shown or in sequential order, or to perform all shown operations to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the discussion above, these should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated otherwise, certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated otherwise, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0138] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.

[0139] Furthermore, the various implementations of this disclosure can be described with reference to the following terms, and their features can be combined in any reasonable manner.

[0140] Clause 1. A core network device, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the core network device to: receive a message from a first network device, the message including at least Radio Access Network (RAN) Notification Area (RNA) information configured to a terminal device via the first network device to or having been switched to a Radio Resource Control (RRC) inactive state; and, based on the message, determine a target paging process for the terminal device between an RNA-based paging process and a paging process triggered by another network.

[0141] Clause 2. The core network equipment as described in Clause 1, wherein the message further includes at least one of the following: an indication of the transition to the RRC inactive state, or a time point after which the RNA-based paging procedure is applied.

[0142] Clause 3. The core network equipment as described in Clause 2, wherein the message is transmitted when the terminal device transitions to the RRC inactive state, or after the terminal device has transitioned to the RRC inactive state.

[0143] Clause 4. The core network device as described in Clause 2, wherein the time point is based on information defining when the terminal device is in the coverage area of ​​another network device, the first network device and the other network device not having an interface, or wherein the time point is based on when the other network device begins to serve the terminal device, the other network device and the first network device not having an interface.

[0144] Clause 5. The core network equipment as described in Clause 2, wherein the core network equipment is configured to: receive an indication of mobile termination data for the terminal equipment from another core network equipment; and determine the target paging procedure based on the time of receipt of the indication of mobile termination data and the time point of receipt.

[0145] Clause 6. The core network device as described in Clause 5, wherein the core network device is configured to: determine the other network-triggered paging procedure as the target paging procedure in response to the reception time being earlier than the time point; and transmit a request for the network-triggered paging procedure to the first network device.

[0146] Clause 7. The core network device according to Clause 5, wherein the core network device is configured to: determine the RNA-based paging process as the target paging process in response to the reception time not being earlier than the time point; determine at least one second network device based on the RNA information configured to the terminal device; and transmit a request for the RNA-based paging process to the at least one second network device.

[0147] Clause 8. The core network device according to Clause 1, wherein the core network device is configured to: determine the RNA-based paging process as the target paging process in response to the message further including an instruction to perform the RNA-based paging process; determine at least one second network device based on the RNA information configured to the terminal device; and transmit a request for the RNA-based paging process to the at least one second network device.

[0148] Clause 9. The core network device as described in Clause 7 or 8, wherein the request includes at least one of the following: the terminal device is an indication of the RRC inactive state, the identifier of the first network device, or the RNA information configured to the terminal device.

[0149] Clause 10. The core network equipment according to any one of Clauses 1 to 9, wherein the RNA information includes at least one of the following: a list of cell identifiers or a list of RAN area identifiers.

[0150] Clause 11. The core network equipment according to any one of Clauses 1 to 10, wherein the first network equipment is a first non-terrestrial network equipment and the second network equipment is a second non-terrestrial network equipment.

[0151] Clause 12. A first network device, comprising: at least one processor; and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the first network device to: transmit a message to a core network device, the message including at least Radio Access Network (RAN) Notification Area (RNA) information configured to a terminal device via the first network device to or having been converted to a Radio Resource Control (RRC) inactive state.

[0152] Clause 13. The first network device according to Clause 12, wherein the first network device is configured to: transmit the message to the core network device, the message further comprising a time point after which the RNA-based paging process is applied.

[0153] Clause 14. The first network device as described in Clause 13, wherein the first network device is configured to: receive from the core network device a request for a network-triggered paging procedure.

[0154] Clause 15. The first network device according to Clause 12, wherein the first network device is configured to: receive mobility termination data or signaling for the terminal device from another core network device; and determine the target paging procedure based on the time of receipt of the mobility termination data or signaling and a time point after which the RNA-based paging procedure is applied.

[0155] Clause 16. The first network device according to Clause 15, wherein the first network device is configured to: determine, in response to the reception time being earlier than the time point, determine that the network-triggered paging process is the target paging process; and transmit a paging message for paging the terminal device to the second network device or the terminal device.

[0156] Clause 17. The first network device according to Clause 12, wherein the first network device is configured to: determine the RNA-based paging process as the target paging process in response to the reception time not being earlier than the time point; and after the determination of the RNA-based paging process, transmit the message to the core network device, the message further including an instruction to perform the RNA-based paging process.

[0157] Clause 18. A first network device according to any one of Clauses 13 to 17, wherein the first network device is configured to determine the point in time based on one of the following: defining information about when the terminal device is in the coverage area of ​​another network device, the first network device and the other network device not having an interface, or when the other network device begins to serve the terminal device, the other network device and the first network device not having an interface.

[0158] Clause 19. The first network device according to any one of Clauses 13 to 18, wherein the message further includes an indication of the transition to the RRC inactive state.

[0159] Clause 20. The first network device according to any one of Clauses 12 to 19, wherein the first network device is a first non-terrestrial network device and the second network device is a second non-terrestrial network device.

[0160] Clause 21. A second network device, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second network device to: receive a request from a core network device, the request including at least information based on a notification area (RNA) of a radio access network (RAN), the RNA information being configured to a terminal device; determine at least one cell belonging to the RNA; and transmit a paging message to the terminal device via the at least one cell, wherein the terminal device is switched to a radio resource control (RRC) inactive state via a first network device, the first network device and the second network device having no interface.

[0161] Clause 22. The second network device as described in Clause 21, wherein the request includes at least one of the following: the terminal device is an indication of the inactive state, the identifier of the first network device, or the RNA information configured to the terminal device.

[0162] Clause 23. The second network device pursuant to any one of Clauses 21 to 22, wherein the first network device is a first non-terrestrial network device and the second network device is a second non-terrestrial network device.

[0163] Clause 24. A method comprising: receiving, at a core network device and from a first network device, a message comprising at least radio access network (RAN) notification area (RNA) information configured to a terminal device, the terminal device being switched to or having been switched to a radio resource control (RRC) inactive state via the first network device; and, based on the message, determining a target paging procedure for the terminal device between an RNA-based paging procedure and a paging procedure triggered by another network.

[0164] Clause 25. A method comprising: transmitting a message at a first network device and to a core network device, the message including at least radio access network (RAN) notification area (RNA) information, the RNA information being configured to a terminal device, the terminal device being switched to or having been switched to a radio resource control (RRC) inactive state via the first network device.

[0165] Clause 26. A method comprising: receiving a request at a second network device and from a core network device, the request including at least information of a notification area RNA based on a radio access network (RAN), the information of the RNA being configured to a terminal device; determining at least one cell belonging to the RNA; and transmitting a paging message to the terminal device via the at least one cell, wherein the terminal device is switched to a radio resource control (RRC) inactive state via a first network device, the first network device and the second network device having no interface.

[0166] Clause 27. A first apparatus comprising: components for receiving a message from a first network device, the message including at least radio access network (RAN) notification area (RNA) information configured to a terminal device, the terminal device being switched to or having been switched to a radio resource control (RRC) inactive state via the first network device; and components for determining a target paging process for the terminal device based on the message between an RNA-based paging process and a paging process triggered by another network.

[0167] Clause 28. A second apparatus comprising: a component for transmitting a message to a core network device, the message including at least notification area RNA information based on a radio access network (RAN), the RNA information being configured to a terminal network, the terminal network being switched to or having been switched to a radio resource control (RRC) inactive state via the first network device.

[0168] Clause 29. A third apparatus comprising: components for receiving a request from a core network device, the request including at least information based on a notification area (RNA) of a radio access network (RAN), the information of the RNA being configured to a terminal device; components for determining at least one cell belonging to the RNA; and components for transmitting a paging message to the terminal device via the at least one cell, wherein the terminal device is switched to a radio resource control (RRC) inactive state via a first network device, the first network device having no interface with a second network device.

[0169] Clause 30. A computer-readable medium comprising instructions stored thereon for causing a device to perform at least the method described in accordance with Clause 24, 25, or 26.

Claims

1. A core network device for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the core network device to: A message is received from a first network device, the message including at least radio access network (RAN) notification area (RNA) information, the RNA information being configured to a terminal device, the terminal device being switched to or having been switched to a radio resource control (RRC) inactive state via the first network device; as well as Based on the message, a target paging process for the terminal device is determined between an RNA-based paging process and a paging process triggered by another network.

2. The core network device of claim 1, wherein the message further comprises at least one of the following: an indication of the transition to the RRC inactive state, or a time point after which the RNA-based paging process is applied.

3. The core network device according to claim 2, wherein the message is transmitted when the terminal device transitions to the RRC inactive state, or after the terminal device has transitioned to the RRC inactive state.

4. The core network device according to claim 2, wherein the time point is based on information defining when the terminal device is in the coverage area of ​​another network device, the first network device and the other network device do not have an interface, or The time point mentioned is based on when the other network device starts serving the terminal device, and the other network device does not have an interface with the first network device.

5. The core network device according to claim 2, wherein the core network device is configured to: Receive an instruction for the termination of mobility data for the terminal device from another core network device; and The target paging process is determined based on the receipt time and the time point of the indication of the mobile termination data.

6. The core network device according to claim 5, wherein the core network device is configured to: In response to the reception time being earlier than the specified time point, the paging process triggered by the other network is determined to be the target paging process; and A request for a network-triggered paging process is transmitted to the first network device.

7. The core network device according to claim 5, wherein the core network device is configured to: In response to the fact that the receiving time is not earlier than the time point, the RNA-based paging process is determined to be the target paging process; Based on the RNA information configured to the terminal device, at least one second network device is identified; and A request for the RNA-based paging process is transmitted to the at least one second network device.

8. The core network device according to claim 1, wherein the core network device is configured to: The message also includes an instruction to perform the RNA-based paging process, determining the RNA-based paging process as the target paging process; Based on the RNA information configured to the terminal device, at least one second network device is identified; and A request for the RNA-based paging process is transmitted to the at least one second network device.

9. The core network device according to claim 7 or 8, wherein the request includes at least one of the following: The terminal device is an indication of the RRC inactive state. The identifier of the first network device, or The RNA information configured into the terminal device.

10. The core network device according to any one of claims 1 to 8, wherein the RNA information includes at least one of the following: a list of cell identifiers or a list of RAN region identifiers.

Images