Completing a non-access-stratum procedure in store &forward architecture
Patent Information
- Application Number
- PCT/CN2023/092121
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-04
- Publication Date
- 2024-11-07
Smart Images

Figure CN2023092121_07112024_PF_FP_ABST
Abstract
Description
COMPLETING A NON-ACCESS-STRATUM PROCEDURE IN STORE &FORWARD ARCHITECTUREFIELD
[0001] Embodiments of the present disclosure generally relate to the field of telecommunication and in particular to devices, methods, apparatuses and computer readable storage media of completing a Non-Access Stratum (NAS) procedure in a Non-Terrestrial Networks (NTN) store &forward (S&F) architecture, especially by using more than one Radio Access Network (RAN) nodes.BACKGROUND
[0002] The Third Generation Partnership Project (3GPP) has initiated a discussion on NTN for New Radio (NR) and Narrow Band Internet of Things (NB-IoT) . During the discussion, the S&F operation has been proposed, which may allow a satellite to provide service to NTN terminal device (s) even in periods / areas when / where the satellite does not have simultaneous connection with a terminal device and with a core network (CN) device.
[0003] SUMMARY
[0004] In general, example embodiments of the present disclosure provide a solution of completing a NAS procedure in an NTN S&F architecture.
[0005] In a first aspect, there is provided an apparatus. The apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to obtain, from a first RAN device, an indication including an unique identifier, the unique identifier being assigned by the first RAN device, determine that a Radio Resource Control (RRC) procedure or a NAS procedure cannot be completed via the first RAN device; and in accordance with a determination that a paging message from a second RAN device indicating the apparatus to continue the uncompleted RRC procedure or the uncompleted NAS procedure is received, transmit, to the second RAN device, a request for a communication between the apparatus and the second RAN device, to continue the uncompleted RRC procedure or the uncompleted NAS procedure by using the stored context of the apparatus.
[0006] In a second aspect, there is provided an apparatus. The apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to obtain, from a CN device, a configuration of at least one unique identifier for at least one terminal device; assign, to a terminal device, an unique identifier of the terminal device from the at least one unique identifier, when the apparatus does not have simultaneous connection with the core network device; and transmit an indication including the unique identifier, to the terminal device to be stored as a context of terminal device.
[0007] In a third aspect, there is provided an apparatus. The apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to transmit, to a first RAN device, a configuration of at least one unique identifier for at least one terminal device, before the terminal device connect with the first RAN device.
[0008] In a fourth aspect, there is provided an apparatus. The apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to receive, from a core network device, a message including a context of a terminal device created by a first RAN device, for resuming the context of a terminal device at the apparatus, to continue an uncompleted RRC procedure or an uncompleted NAS procedure with the terminal device; transmit a paging message indicating the terminal device to continue the uncompleted RRC procedure or the uncompleted NAS procedure; and receive, from the terminal device, a request for a communication between the apparatus and the terminal device, to continue the uncompleted RRC procedure or the uncompleted NAS procedure by using the context received from core network device.
[0009] In a fifth aspect, there is provide a method. The method comprises obtaining, from a first RAN device, an indication including an unique identifier, the unique identifier being assigned by the first RAN device, determining that a RRC procedure or a NAS procedure cannot be completed via the first RAN device; and in accordance with a determination that a paging message from a second RAN device indicating the apparatus to continue the uncompleted RRC procedure or the uncompleted NAS procedure is received, transmitting, to the second RAN device, to continue the uncompleted RRC procedure or the uncompleted NAS procedure by using the stored context of the terminal device.
[0010] In a sixth aspect, there is provide a method. The method comprises obtaining, from a CN device, a configuration of at least one unique identifier for at least one terminal device; assigning, to a terminal device, an unique identifier of the terminal device from the at least one unique identifier, when the first RAN device does not have simultaneous connection with the core network device; and transmitting an indication including the unique identifier, to the terminal device to be stored as a context of terminal device.
[0011] In a seventh aspect, there is provide a method. The method comprises transmitting, to a first RAN device, a configuration of at least one unique identifier for at least one terminal device, before the terminal device connect with the first RAN device.
[0012] In an eighth aspect, there is provide a method. The method comprises receiving, from a core network device, a message including a context of a terminal device created by a first RAN device, for resuming the context of a terminal device at the second RAN device, to continue an uncompleted RRC procedure or an NAS procedure with the terminal device; transmitting a paging message indicating the terminal device to continue the uncompleted RRC procedure or the uncompleted NAS procedure; and receiving, from the terminal device, a request for a communication between a second RAN device and the terminal device, to continue the uncompleted RRC procedure or the uncompleted NAS procedure by using the context received from core network device.
[0013] In a ninth aspect, there is provided an apparatus comprising means for obtaining, from a first RAN device, an indication including an unique identifier, the unique identifier being assigned by the first RAN device, means for determining that a RRC procedure or a NAS procedure cannot be completed via the first RAN device; and means for in accordance with a determination that a paging message from a second RAN device indicating the apparatus to continue the uncompleted RRC procedure or the uncompleted NAS procedure is received, transmitting, to the second RAN device, to continue the uncompleted RRC procedure or the uncompleted NAS procedure by using the stored context of the apparatus.
[0014] In a tenth aspect, there is provided an apparatus comprising means for obtaining, from a CN device, a configuration of an unique identifier pool for at least one terminal device; means for assigning, to a terminal device, an unique identifier of the terminal device from the at least one unique identifier, when the apparatus does not have simultaneous connection with the core network device; and means for transmitting an indication including the unique identifier, to the terminal device to be stored as a context of terminal device.
[0015] In an eleventh aspect, there is provided an apparatus comprising means for transmitting, to a first RAN device, a configuration of at least one unique identifier for at least one terminal device, before the terminal device connect with the first RAN device.
[0016] In a twelfth aspect, there is provided an apparatus comprising means for receiving, from a core network device, a message including a context of a terminal device created by a first RAN device, for resuming the context of a terminal device at the apparatus, to continue an uncompleted RRC procedure or an uncompleted NAS procedure with the terminal device; means for transmitting a paging message indicating the terminal device to continue the uncompleted RRC procedure or the uncompleted NAS procedure; and means for receiving, from the terminal device, a request for a communication between the apparatus and the terminal device, to continue the uncompleted RRC procedure or the uncompleted NAS procedure by using the context received from core network device.
[0017] In a thirteenth aspect, there is provided a computer readable medium having a computer program stored thereon which, when executed by at least one processor of an apparatus, causes the apparatus to carry out the method according to the fifth aspect, the sixth aspect, the seventh aspect or the eighth aspect.
[0018] Other features and advantages of the embodiments of the present disclosure will also be apparent from the following description of specific embodiments when read in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of embodiments of the disclosure.BRIEF DESCRIPTION OF THE DRAWINGS
[0019] Embodiments of the disclosure are presented in the sense of examples and their advantages are explained in greater detail below, with reference to the accompanying drawings.
[0020] FIG. 1 illustrates an example environment in which example embodiments of the present disclosure may be implemented;
[0021] FIG. 2 shows a signaling chart illustrating an example of process according to some example embodiments of the present disclosure;
[0022] FIG. 3 shows a flowchart of an example method of completing a NAS procedure in an NTN S&F architecture according to some example embodiments of the present disclosure;
[0023] FIG. 4 shows a flowchart of an example method of completing a NAS procedure in an NTN S&F architecture according to some example embodiments of the present disclosure;
[0024] FIG. 5 shows a flowchart of an example method of completing a NAS procedure in an NTN S&F architecture according to some example embodiments of the present disclosure;
[0025] FIG. 6 shows a flowchart of an example method of completing a NAS procedure in an NTN S&F architecture according to some example embodiments of the present disclosure;
[0026] FIG. 7 shows a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and
[0027] FIG. 8 shows a block diagram of an example computer readable medium in accordance with some embodiments of the present disclosure.
[0028] Throughout the drawings, the same or similar reference numerals may represent the same or similar element.DETAILED DESCRIPTION
[0029] Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein may be implemented in various manners other than the ones described below.
[0030] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein may have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0031] References in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
[0032] It shall be understood that although the terms “first, ” “second” and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.
[0033] As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or” , mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0034] As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included.
[0035] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and / or “including” , when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.
[0036] As used in this application, the term “circuitry” may refer to one or more or all of the following:
[0037] (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and
[0038] (b) combinations of hardware circuits and software, such as (as applicable) :
[0039] (i) a combination of analog and / or digital hardware circuit (s) with software / firmware and
[0040] (ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and
[0041] (c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[0042] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0043] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR) , Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) , an Enhanced Machine type communication (eMTC) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , the sixth generation (6G) communication protocols, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.
[0044] As used herein, the terms “network device” , “radio network device” and / or “radio access network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , an NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a remote radio head (RRH) , a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a non-geosynchronous orbit (NGSO) satellite and a geosynchronous orbit (GSO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, a gNB includes a Central Unit (CU) and a Distributed Unit (DU) . In some other example embodiments, part of the radio access network device or full of the radio access network device may embarked on an airborne or space-borne NTN vehicle.
[0045] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) . The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. The terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node) . In the following description, the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.
[0046] As used herein, the term “resource, ” “transmission resource, ” “resource block, ” “physical resource block” (PRB) , “uplink resource, ” or “downlink resource” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
[0047] FIG. 1 shows an example communication network 100 in which embodiments of the present disclosure can be implemented. As shown in FIG. 1, the communication network 100 may comprise a terminal device 110. Hereinafter the terminal device 110 may also be referred to as a UE.
[0048] The communication network 100 may further comprise a first RAN device 120-1 and a second RAN device 120-2. Hereinafter the first RAN device 120-1 or the second RAN device 120-2 may also be referred to as a network device in the RAN, which may also be called as a BS, a gNB, or an eNB. In some scenario, the first RAN device 120-1 or the second RAN device 120-2 may be hosted in satellites. The terminal device 110 may communicate with the first RAN device 120-1 within a coverage of the first RAN device 120-1, for example, the geographical area of the terminal device 110 is served by a satellite beam or cell from the first RAN device 120-1. Later, at a different time, the terminal device 110 may communicate with the second RAN device 120-2 within coverage of the second RAN device 120-2, for example, the geographical area of the terminal device 110 is served by a satellite beam or cell from the second RAN device 120-2.
[0049] Furthermore, the communication network 100 may also comprise a Core Network (CN) device 130. Hereinafter the CN device 130 may also be referred to a network function in the CN, such as Access and Mobility Management Function (AMF) , or Mobility Management Entity (MME) , Home Subscriber Server (HSS) , etc. The terminal device 110 may communicate with the CN device 130, for example, for performing a NAS procedure between the terminal device 110 and the CN device 130 via the RAN devices 120-1 and / or 120-2. The NAS procedure may be a registration procedure in 5G system, or an attach procedure in LTE system, or a service request procedure, etc. The connection or communication between the RAN device 120-1 (or 120-2) and the CN device 130 may be based on S1 Application Protocol (S1AP) in LTE system, or Next Generation Application Protocol (NGAP) in 5G system, or any other application protocol.
[0050] In some scenarios, the communication network 100 may refer to an NTN network and the RAN devices 120-1 and 120-2 may be implemented in a satellite and moves along with the satellite. More specifically, the satellite is a NGSO satellite. In some other scenarios, the communication network 100 may also refer to any other suitable networks.
[0051] It is to be understood that the number of network devices and terminal devices shown in FIG. 1 is given for the purpose of illustration without suggesting any limitations. The communication network 100 may include any suitable number of network devices and terminal devices.
[0052] Communications in the communication environment 100 may be implemented according to any proper communication protocol (s) , includes, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) , the fifth generation (5G) , the sixth generation (6G) , and the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, includes but not limited to: Code Division Multiple Access (CDMA) , Frequency Division Multiple Access (FDMA) , Time Division Multiple Access (TDMA) , Frequency Division Duplex (FDD) , Time Division Duplex (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiple (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.
[0053] As described above, the S&F operation has been proposed, which may refer to a discontinuous coverage scenario, where the UE may only occasionally and temporarily have coverage from a satellite. It is also possible that the discontinuous coverage scenario may be expanded with defining that the satellite is not always connected with the CN device. Hereinafter the RAN device may be referred to as an eNB, a gNB or any other suitable RAN devices.
[0054] For example, in the example communication network 100 as shown in FIG. 1, the first RAN device 120-1 may not connect with terminal device 110 and CN device 130 all the time or at the same time. When the satellite moves to the geographical area of the terminal device 110, the first RAN device 120-1 may provide a cell coverage to cover the geographical area 102, the terminal device 110 may connect with the first RAN device 120-1. However, at the same time, the first RAN device 120-1 may not have the connection with the CN 130. At a different time later (or before) , the first RAN device 120-1 may connect to the CN 130, but the first RAN device 120-1 may move out of the geographical area of the terminal device 110 and may not be able to connect with the terminal device 110. That is, possibility of UE connectivity and CN connectivity may be at different time instances.
[0055] That is, in S&F mode, the RAN device / satellite may only have the connection with CN device for a period. Similarly, the RAN device / satellite have the connection with UE for a period. The RAN device / satellite may not simultaneously have both connections, i.e., with the UE, and with the CN device.
[0056] The S&F architecture enables a low-cost deployment consisting of just a few satellites and a few ground stations. This means the connectivity cost per device can be further reduced at the cost of only being able to support delay tolerant data.
[0057] Furthermore, the LTE NAS attach procedure (or the NR NAS registration procedure) may require multiple interactions between the terminal device and the RAN device (hosted in satellite) , and between the RAN device and CN device (e.g., a network node on the ground) . By assuming a RAN device to have simultaneous connection with the terminal device and the CN device, therefore a NAS procedure may be completed by using only one RAN device.
[0058] However, in the S&F scenario, a RAN device may only be able to connect with the terminal device or with the CN device for a period, but not have the simultaneous connection with both the terminal device and the CN device. This causes problem in the completion of a NAS procedure, because it is impossible to complete a NAS procedure by using only one RAN device.
[0059] For example, by using the example as shown in FIG. 1, first, the first RAN device 120-1 moves in geographical area of terminal device 110 and the terminal device 110 may initiate a RRC establishment procedure. Then the first RAN device 120-1 may move out of the geographical area of terminal device 110 and may connect with a CN device 130 (e.g., an AMF, or a MME) , and the first RAN device 120-1 may send the INITIAL UE MESSAGE to the CN device 130. The message may include a RAN UE NGAP ID (or AP ID in short) assigned by the first RAN device 120-1. Then the CN device 130 may determine, for example, the second RAN device 120-2 may serve the terminal device 110 and then send the DL NAS TRANSPORT to the second RAN device 120-2.
[0060] In this case, the second RAN device 120-2 may reject the DL NAS TRANSPORT message, since the message includes a mandatory RAN UE NGAP ID assigned by the first RAN device 120-1 that is unknown to the second RAN device 120-2.
[0061] Even if the second RAN device 120-2 does not reject the DL NAS TRANSPORT message and continue the following procedures, when the second RAN device 120-2 moves in the terminal device 110’s geographical area, the second RAN device 120-2 just cannot continue the RRC procedure, since the second RAN device 120-2 does not have any context for the terminal device, e.g. Timing Advance, current RRC state, the RRC message that have been exchanged between the terminal device 110 and the first RAN device 120-1, etc.
[0062] Therefore, the terminal device 110 can only re-start the RRC establishment procedure. The second RAN device 120-2 then sends the INITIAL UE MESSAGE to CN device 130, when the second RAN device 120-2 has a connection with CN device 130. However, the further procedures will fail again, e.g., the CN device 130 may send a DL NAS TRANSPORT to a new RAN device, and new RAN device may repeat the above procedure. As a result, the terminal device 110 cannot complete the NAS registration procedure. This issue also happens when the satellite hosts RAN device and some CN device, for example, MME or AMF, but other CN device, for example, a Home Subscriber Server (HSS) is on the ground.
[0063] In this situation, a mechanism to support the terminal device to complete a NAS procedure in the S&F scenario is expected. The present disclosure proposes a solution for completing a NAS procedure in the S&F by using more than one RAN devices.
[0064] In this solution, the CN device 130 may configure a pool of identifiers (or a list of identifiers) for terminal devices and transmit the configuration of the pool (or the list of the identifiers) to the RAN device. During a RRC procedure or a NAS procedure, the first RAN device may assign a unique identifier to the terminal device which is selected from the pool. The first RAN device may indicate the unique identifier to the CN device and the CN device may also indicate the unique identifier of the terminal device in a procedure for resuming the UE context at a second RAN device to be connected with the terminal device. If the terminal device receives a paging message from the second RAN device including the unique identifier, the terminal device 110 may continue or complete the RRC procedure or the NAS procedure with the second RAN device.
[0065] Example embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.
[0066] Reference is now made to FIG. 2, which shows a signaling chart 200 for communication according to some example embodiments of the present disclosure. As shown in FIG. 2, the signaling chart 200 involves the terminal device 110, the first RAN device 120-1, the second RAN device 120-2 and the CN device 130. For the purpose of discussion, reference is made to FIG. 1 to describe the signaling chart 200.
[0067] In some scenarios, the first RAN device 120-1 and RAN device 120-2 may be hosted in a satellite, respectively.
[0068] As shown in FIG. 2, the CN device 130 may configure an identifier (ID) pool or a list of identifiers. For example, the identifier pool may comprise a set of terminal device IDs. The CN device 130 may transmit (202) a configuration of ID pool to the first RAN device 120-1 when the first RAN device 120-1 has a connection with the CN device 130. The IDs may be used later when a terminal device connect with the first RAN device 120-1. This step may be performed before the terminal device connect with the first RAN device 120-1.
[0069] The ID as described above may be unique per CN device 130, for example, the ID is unique per Access and Mobility Management Function (AMF) in 5G system. For example, the ID may be a 5G-S-Temporary Mobile Subscriber Identity (5G S-TMSI) .
[0070] Then the first RAN device 120-1 may lose the connection with the CN device 130 and moves in a geographical area of the terminal device 110.
[0071] When the first RAN device 120-1 has a connection with the terminal device 110, the terminal device 110 may initiate a NAS registration procedure. For example, the terminal device 110 first send (204) a RRCSetupRequest to the first RAN device 120-1. The first RAN device 120-1 may assign, from the ID pool configured by the CN device 130, an unique identifier for the terminal device 110 and transmit (206) an indicating including the assigned unique identifier for the terminal device 110 to the terminal device 110 in a response to the RRC setup request.
[0072] It is to be understood that the RRCSetupRequest message received by the first RAN device 120-1 does not include a 5G-S-TMSI, the first RAN device 120-1 may know that, for example, this is the first power up of the terminal device 110, or the geographical area of the terminal device 110 is out of previous registration area. Then the first RAN device 120-1 may assign an unique identifier to the terminal device 110.
[0073] If the terminal device 110 determines that the response to the RRCSetupRequest including the assigned unique identifier for the terminal device 110, the terminal device 110 may know that the NAS procedure cannot be completed with the first RAN device 120-1 and the first RAN device 120-1 will not provide any NAS response, but instead may get it from a further RAN device.
[0074] After receiving the response to the RRC setup request from the first RAN device 120-1, the terminal device 110 may transmit (208) to the first RAN device 120-1, a NAS REGISTRATION REQUEST during the RRC connection setup. However, the first RAN device 120-1 then may moves out the geographical area of the terminal device 110 and stop serving the terminal device 110.
[0075] In some other example embodiment, the first RAN device 120-1 may transmit the unique identifier to the terminal device 110 in other RRC procedures, for example, during a RRC resume procedure, or a RRC reestablishment procedure, or a RRC release procedure.
[0076] Upon the reception of the unique identity, the terminal device 110 know the NAS procedure cannot be completed with the first RAN device 120-1. In other words, part of a NAS procedure is performed via the first RAN device 120-1 and the uncompleted part of the NAS procedure is to be performed via a further RAN device. In one example embodiment, the NAS procedure may be initiated by the terminal device 110, for example, the terminal device 110 transmit a NAS message to the CN device 130 via the first RAN device 120-1, but the terminal device 110 then receive the NAS response message from the CN device 130 via a further RAN device. In another example embodiment, the NAS procedure may be initiated by the CN device 130, for example, the terminal device 110 receive a NAS message from the CN device 130 via the first RAN device 120-1, but the terminal device 110 then transmit the NAS response message to the CN device 130 via a further RAN device.
[0077] In some example embodiment, it may be a RRC procedure performed via different RAN devices. In other words, part of a RRC procedure is performed via the first RAN device 120-1 and the uncompleted part of the RRC procedure is to be performed via a further RAN device. For example, the terminal device 110 transmit a RRC message to the first RAN device 120-1, but the terminal device 110 then receive the RRC response message from a further RAN device. In another example, the terminal device 110 receive a RRC message from the first RAN device 120-1, but the terminal device 110 then transmit the RRC response message to a further RAN device.
[0078] Before the first RAN device 120-1 moves out of the geographical area of the terminal device 110, the first RAN device 120-1 may initiate the RRC Release procedure to release the RRC connection between the terminal device 110 and the first RAN device 120-1. The RRC Release or other RRC procedure may include the information for the next RAN device to continue the NAS registration procedure. The RRC connection between the terminal device 110 and the first RAN device 120-1 may also be implicitly released because the terminal device 110 know the next step in the registration procedure requires feedback / information from the CN device, which the RAN device is not currently connected with. If the RRC connection between the terminal device 110 and the first RAN device 120-1 is released (for example, via the RRC release procedure) , or lost, the terminal device 110 store the context. The context may include at least one of the unique identity assigned to the terminal device 110 by the first RAN device 120-1, a RRC state, a last RRC message transmitted from the terminal device 110 to the first RAN device 120-1, a last RRC message received in terminal device 110 from the first RAN device 120-1, an indication for an uncompleted RRC procedure, a NAS state, a last NAS message transmitted from the terminal device 110 via the first RAN device 120-1, a last NAS message received in the terminal device 110 via the first RAN device 120-1, an indication for an uncompleted NAS procedure, etc.
[0079] In this case, the information for the next RAN device to continue the Registration procedure can be included in any DL RRC message (e.g., RRC Setup) . The RRC INACTIVE cannot be used due to the lack of Access Stratum (AS) security.
[0080] When the first RAN device 120-1 has a connection with the CN device 130, the first RAN device 120-1 may transmit (210) to the CN device 130, an INITIAL UE MESSAGE including the unique identifier assigned by the first RAN device 120-1 for the terminal device 110.
[0081] As another option, the unique identifier assigned by the first RAN device 120-1 for the terminal device 110 may also be transmit (212) , from the first RAN device 120-1 to the CN device 130, in a STORE UE CONTEXT message. In this message, the first RAN device 120-1 may send the context of the terminal device 110 to the CN device 130. The context of the terminal device 110 may include the unique identifier assigned by the first RAN device 120-1 for the terminal device 110, a RRC state, a last RRC message received from the terminal device 110, a last RRC message transmitted to the terminal device 110, an indication for an uncompleted RRC procedure, a RAN Application Protocol (AP) context including a RAN AP UE ID (for example, RAN UE NGAP ID in 5G system) ) created at the first RAN device 120-1; or a location of the terminal device 110 (e.g. the Mapped Cell ID, or the Tracking Area Code, an actual location of the terminal device, etc) , etc. Accordingly, the CN device 130 store the context received from the first RAN device 120-1. The CN device 130 may also determine that a NAS procedure with the terminal device 110 is uncompleted via the first RAN device 120-1, for example, the CN device may receive the NAS message from the terminal device 110 via the first RAN device 120-1, but the CN device cannot send the NAS response message to the terminal device 110 via the first RAN device 120-1 since the first RAN device 120-1 does not have a connection with the terminal device 110 when the first RAN device 120-1 has the connection with the CN device 130. The CN device 130 may store the NAS context for the terminal device 110. The NAS context includes a non-access-stratum, NAS, state; a last NAS message transmitted from CN device 130 to the terminal device 110 via first RAN device 120-1, a last NAS message received in the CN device 130 from the terminal device 110 via first RAN device 120-1; an indication for an uncompleted NAS procedure, etc.
[0082] When the second RAN device 120-2 has a connection with the CN device 130, the CN device 130 may, for example, determine that the second RAN device 120-2 will service the geographical area of the terminal device 110. The CN device 130 can select the second RAN device 120-2 to complete the uncompleted RRC procedure or the uncompleted NAS procedure for the terminal device 110. In this case, i.e., the second RAN device 120-2 will provide coverage to the terminal device 110 and the connection between the CN device 130 and the second RAN device 120-2 is available to transfer the information from the CN device 130 to the second RAN device 120-2, the CN device 130 may resume (214) , at the second RAN device 120-2 the context for the terminal device 110 received from the first RAN device 120-1. The CN device 130 may transmit (214) , to the second RAN device 120-2, a message (for example, RESUME UE CONTEXT message) for resuming the context of the terminal device at the second RAN device 120-2, in order to continue the uncompleted RRC procedure or the uncompleted NAS procedure with the terminal device 110.
[0083] In some example embodiments, the context may include the unique identifier assigned by the first RAN device 120-1 for the terminal device 110, RRC state, a last RRC message transmitted from the terminal device, a last RRC message received in the terminal device, an indication for an uncompleted RRC procedure, a RAN AP context including an AP ID created at the first RAN device, a location of the terminal device 110 (e.g. the Mapped Cell ID, or the Tracking Area Code, an actual location of the terminal device, etc) , etc.
[0084] It is to be understood that the CN device 130 may resume context for multiple terminal devices. That is, the RESUME UE CONTEXT message transmitted from the CN device 130 to the second RAN device 120-2 may include the context for more than one terminal devices. Thus, it can be a non-UE-associated procedure.
[0085] Then the second RAN device 120-2 may reply (216) with the RESUME UE CONTEXT ACKNOWLEDGE message to the CN device 130.
[0086] In some example embodiments, the message may include a mapping of the old RAN UE AP ID assigned by the first RAN device 120-1 and the new RAN UE AP ID (for example, RAN UE NGAP ID in 5G system) assigned by the second RAN device 120-2. This mapping is used when the RAN UE AP ID assigned by the first RAN device 120-1 is already assigned by the second RAN device 120-2 to a different UE, thus the second RAN device 120-2 assign a new RAN UE AP ID which will be used by the CN device 130 to send DL NAS TRANSPORT message.
[0087] By establishing the context of the terminal device 110 in the second RAN device 120-2, the further NGAP message (e.g., DL NAS TRANSPORT message sent) will not be rejected by the second RAN device 120-2. Then the CN device 130 may send the DL NAS TRANSPORT message to the second RAN device 120-2.
[0088] Then when the second RAN device 120-2 moves in the geographical area of the terminal device 110, the second RAN device 120-2 may initiate (218) a paging procedure for the terminal device 110. The paging message may include the unique identifier assigned by the first RAN device 120-1 for the terminal device 110 and / or a paging cause, indicating the terminal device 110 to continue the uncompleted RRC procedure or the uncompleted NAS procedure via a communication with the second RAN device 120-2, by using the stored context in the terminal device 110.
[0089] The terminal device 110 may monitor a paging channel for S&F paging using the unique identifier assigned for the terminal device 110. When the terminal device 110 receives a paging message from the second RAN device 120-2 including the unique identifier of the terminal device 110 and / or a new paging cause indicating the terminal device 110 to continue the uncompleted RRC procedure or the uncompleted NAS procedure, the terminal device 110 may send (220) to the second RAN device 120-2, a RRCContinueRequest message including the unique identifier of the terminal device 110 and / or a cause indicating the communication is requested to continue the uncompleted RRC procedure or the uncompleted NAS procedure via the second RAN device 120-2, by using the stored context..
[0090] The RRCContinueRequest message transmitted from the terminal device 110 to the second RAN device 120-2 may also be referred to as a new RRC message, because RRCContinueRequest message used in this solution is not based on the AS security context previously established between the terminal device 110 and the first RAN device 120-1 or the second RAN device 120-2. The AS security context has not established yet.
[0091] Based on the received unique identifier of the terminal device 110, the second RAN device 120-2 can identify the related UE context. The second RAN device 120-2 may continue the uncompleted NAS procedure by using the resumed UE context, for example, send the DLInformationTransport message to the terminal device 110. The terminal device 110 continue the uncompleted NAS procedure by using the stored context, for example, send the ULInformationTransport to the second RAN device 120-2.
[0092] When the second RAN device 120-2 has a connection with the CN device 130 again, the second RAN device 120-2 may send UL NAS TRANSPORT message to the CN device 130.
[0093] Similarly, the second RAN device 120-2 may send the context of the terminal device 110 to CN device 130. The context may include the Uu context, the unique identifier of the terminal device 110, the RRC context (e.g., the RRC state, the last sent / received RRC messages, indication of uncompleted RRC procedure, etc) , the NGAP context created at the second RAN device 120-2 (e.g., RAN UE NGAP ID assigned by the second RAN device 120-2) , etc. Accordingly, the CN device 130 may store the received context and NAS context for the terminal device 110 and continue the RRC procedure or NAS procedure with the terminal device 110 via a further RAN device.
[0094] The above-mentioned process may be repeated when a new RAN device arrives or leaves. By using the above procedures, the terminal device 110 may complete the NAS procedure (e.g., Attach / Registration procedure) by using multiple S&F RAN devices.
[0095] In subsequent communication phases (i.e., after the completion of the Attach procedure) , the terminal device and RAN device may utilize the RRC Inactive / suspend / resume procedure to quickly enable a connection setup.
[0096] The solution of the present disclosure enables the complete of a NAS procedure using multiple RAN devices, including multiple interactions between the UE and the RAN node, and between the RAN node and the CN node in the S&F system. Similarly, the solution of the present disclosure enables the complete of a RRC procedure using multiple RAN devices in the S&F system. The assignment of the unique UE ID enables multiple RAN nodes to handle the UE context and continue the divided NAS procedure. Furthermore, a transmission of the new RRC Connection Continue Request by the UE indicates to the RAN node to continue the ongoing NAS procedure.
[0097] FIG. 3 shows a flowchart of an example method 300 of completing a NAS procedure (or a RRC procedure) in an NTN S&F architecture according to some example embodiments of the present disclosure. The method 300 may be implemented at the terminal device 110 as shown in FIG. 1. For the purpose of discussion, the method 300 will be described with reference to FIG. 1.
[0098] At 310, the terminal device 110 obtains, from a first RAN device, an indication including a unique identifier. In one example, the indication indicates the terminal device 110 to store a context of the terminal device, including the unique identifier being assigned by the first RAN device. In another example, the indication indicates the terminal device 110 to first store the unique identifier as a context of the terminal device 110, and the other context of the terminal device 110 (e.g., RRC state, last transmitted RRC message, etc) is stored later, for example, when the RRC connection between the terminal device 110 and the first RAN device is released or lost.
[0099] At 320, the terminal device 110 determines a RRC procedure or a NAS procedure cannot be completed via the first RAN device, due to the RRC connection between the terminal device 110 and the first RAN device will be released or lost. The terminal device 110 store the context.
[0100] At 330, if the terminal device 110 determines that a paging message from a second RAN device indicating the apparatus to continue the uncompleted RRC procedure or the uncompleted NAS procedure is received, at 340, the terminal device 110 transmits, to the second RAN device, a request for a communication between the terminal device and the second RAN device, to continue the uncompleted RRC procedure or the uncompleted NAS procedure by using the stored context of the terminal device.
[0101] In some example embodiments, the terminal device may obtain, from the first RAN device, the indication including the unique identifier in a radio resource control RRC setup procedure, or a RRC resume procedure, or a RRC re-establishment procedure, or a RRC release procedure; and store the context of the terminal device if a RRC connection of the terminal device is released or lost.
[0102] In some example embodiments, the context of the terminal device comprises at least one of: the unique identifier assigned to the terminal device; or a RRC state; or a last RRC message transmitted from the terminal device; or a last RRC message received in the terminal device; or an indication for an uncompleted RRC procedure, or a NAS state; or a last NAS message transmitted from the terminal device; or a last NAS message received in the terminal device; or an indication for an uncompleted NAS procedure.
[0103] In some example embodiments, the request for the communication between the terminal device and the second RAN device is a RRC continue request message.
[0104] In some example embodiments, in accordance with a determination that the unique identifier is obtained, the terminal device may determine that the RRC procedure or the NAS procedure is to be continued with a further RAN device other than the first RAN device.
[0105] In some example embodiments, the indication further indicates that the communication is to be continued with the second RAN device.
[0106] In some example embodiments, the paging message received from the second RAN device includes the unique identifier of the apparatus and / or a paging cause, indicating the terminal device to continue the uncompleted RRC procedure or the uncompleted NAS procedure via a communication with the second RAN device, by using the stored context of the terminal device.
[0107] In some example embodiments, the terminal device may transmit, to the second RAN device, the unique identifier and / or a cause indicating the communication is requested to continue the uncompleted RRC procedure or the uncompleted NAS procedure via the second RAN device, by using the stored context.
[0108] In some example embodiments, the terminal device may transmit, a RRC message or a NAS message to the first RAN device and receive a RRC response message or a NAS response message from the second RAN device; or receive, a RRC message or a NAS message from the first RAN device and transmit a RRC response message or a NAS response message to the second RAN device.
[0109] FIG. 4 shows a flowchart of an example method 400 of completing a NAS procedure in an NTN S&F architecture according to some example embodiments of the present disclosure. The method 400 may be implemented at the first RAN device 120-1 as shown in FIG. 1. For the purpose of discussion, the method 400 will be described with reference to FIG. 1.
[0110] At 410, the first RAN device 120-1 obtains, from a CN device, a configuration of at least one unique identifier for at least one terminal device. This may be performed before the terminal device connect with the first RAN device 120-1.
[0111] At 420, the first RAN device 120-1 assigns, to a terminal device, a unique identifier of the terminal device from the at least one unique identifier, when the first RAN device 120-1 does not have simultaneous connection with the core network device.
[0112] At 430, the first RAN device 120-1 transmits an indication including the unique identifier, to the terminal device to be stored as a context of terminal device.
[0113] In some example embodiments, the first RAN device 120-1 may transmit, to the terminal device, the indication during a radio resource control RRC setup procedure, or a RRC resume procedure, or a RRC re-establishment procedure, or a RRC release procedure.
[0114] In some example embodiments, the first RAN device 120-1 may determine a RRC procedure or a NAS procedure with the terminal device cannot be completed, when the apparatus does not have simultaneous connection with the core network device.
[0115] In some example embodiments, the first RAN device 120-1 may transmit, to the terminal device, the indication during a radio resource control RRC setup procedure, or a RRC resume procedure, or a RRC re-establishment procedure, or a RRC release procedure.
[0116] In some example embodiments, the first RAN device 120-1 may transmit, to the core network device, the unique identifier assigned to the terminal device.
[0117] In some example embodiments, the unique identifier of the terminal device is transmitted to the core network device via at least one of: an initial UE message, or a UE context store message.
[0118] In some example embodiments, the initial UE message or UE context store message further comprises a context of the terminal device.
[0119] In some example embodiments, the context of the terminal device comprises at least one of: the unique identifier assigned by the apparatus; or a RRC state; or a last RRC message transmitted from the terminal device; or a last RRC message received in the terminal device; or an indication for an uncompleted RRC procedure, or a NAS state; or a last NAS message transmitted from the terminal device; or a last NAS message received in the terminal device; or an indication for an uncompleted NAS procedure; or a RAN AP context including an AP ID created at the apparatus; or a location of the terminal device.
[0120] FIG. 5 shows a flowchart of an example method 500 of completing a NAS procedure in an NTN S&F architecture according to some example embodiments of the present disclosure. The method 500 may be implemented at the CN device 130 as shown in FIG. 1. For the purpose of discussion, the method 500 will be described with reference to FIG. 1.
[0121] At 510, the CN device 130 transmits, to a first RAN device, a configuration of at least one unique identifier for at least one terminal device. This may be performed before the terminal device connect with the first RAN device.
[0122] In some example embodiments, the CN device 130 may receive, from the first RAN device, context of the terminal device created at the first RAN device; and store the context received from the first RAN device and a NAS context established with the terminal device via the first RAN device.
[0123] In some example embodiments, the context of the terminal device is transmitted to the core network device via at least one of: an initial UE message, or a UE context store message.
[0124] In some example embodiments, the context of the terminal device comprises at least one of: an unique identifier assigned by the first RAN device; or RRC state; or a last RRC message transmitted from the terminal device; a last received RRC message received in the terminal device; an indication for an uncompleted RRC procedure; a RAN AP context including an AP ID created at the first RAN device; or a location of the terminal device.
[0125] In some example embodiments, the NAS context comprises at least one of: a NAS state; or a NAS message transmitted from the terminal device; a last NAS message received in the terminal device; or an indication for an uncompleted NAS procedure.
[0126] In some example embodiments, the CN device 130 may determine a NAS procedure with the terminal device is uncompleted via the first RAN device.
[0127] In some example embodiments, in accordance with a determination that an uncompleted RRC procedure or the uncompleted NAS procedure with the terminal device is to be continued via a second RAN device, the CN device 130 may transmit, to the second RAN device, a message for resuming the context of the terminal device at the second RAN device, in order to continue the uncompleted RRC procedure or the uncompleted NAS procedure with the terminal device.
[0128] In some example embodiments, the CN device 130 may receive, from the second RAN device, an acknowledge for the message for resuming the context of the terminal device.
[0129] In some example embodiments, the context of the terminal device further includes RAN UE AP ID assigned by the first RAN device, and wherein the acknowledge includes a mapping of the RAN UE AP identifier assigned by the first RAN device and a further RAN UE AP identifier assigned by the second RAN device.
[0130] In some example embodiments, the CN device 130 may transmit, to the second RAN device, a message by using the further RAN UE AP ID assigned by the second RAN device.
[0131] In some example embodiments, the CN device 130 may transmit, a NAS message to the terminal device via the first RAN device and receive a NAS response message from the terminal device via the second RAN device; or receive, a NAS message from the terminal device via the first RAN device and transmit a NAS response message to the terminal device via the second RAN device.
[0132] FIG. 6 shows a flowchart of an example method 600 of completing a NAS procedure in an NTN S&F architecture according to some example embodiments of the present disclosure. The method 600 may be implemented at the second RAN device 120-2 as shown in FIG. 1. For the purpose of discussion, the method 600 will be described with reference to FIG. 1.
[0133] At 610, the second RAN device 120-2 receive, from a core network device, a message including a context of a terminal device created by a first RAN device, for resuming the context of a terminal device at the second RAN device, to continue an uncompleted RRC procedure or an uncompleted NAS procedure with the terminal device.
[0134] At 620, the second RAN device 120-2 transmits a paging message indicating the terminal device to continue the uncompleted RRC procedure or the uncompleted NAS procedure.
[0135] At 630, the second RAN device 120-2 receives, from the terminal device, a request for a communication between the second RAN device 120-2 and the terminal device to continue the uncompleted RRC procedure or the uncompleted NAS procedure by using the context received from core network device.
[0136] In some example embodiments, the context received from the core network device further includes at least one of: the unique identifier assigned to the terminal device; or RRC state; a last RRC message transmitted from the terminal device; a last received RRC message received in the terminal device; an indication for an uncompleted RRC procedure; a RAN AP context including a RAN UE AP ID created at the first RAN device; or a location of the terminal device.
[0137] In some example embodiments, the second RAN device 120-2 may transmit, to the core network device, an acknowledge for the message for resuming the context of the terminal device, including at least one of a further RAN UE AP identifier assigned by the apparatus, and a mapping of the RAN UE AP identifier assigned by the first RAN device and the further RAN UE AP identifier assigned by the second RAN device 120-2.
[0138] In some example embodiments, the second RAN device 120-2 may transmit, to the core network device, an acknowledge for the message for resuming the context of the terminal device, including at least one of a further RAN UE AP identifier assigned by the second RAN device, and a mapping of the RAN UE AP identifier assigned by the first RAN device and the further RAN UE AP identifier assigned by the second RAN device.
[0139] In some example embodiments, the second RAN device 120-2 may receive, from the core network device, a further message including the further RAN UE AP ID assigned by the second RAN device 120-2.
[0140] In some example embodiments, the request for the communication between the second RAN device 120-2 and the terminal device via a RRC continue request.
[0141] In some example embodiments, an apparatus capable of performing the method 300 (for example, implemented at the terminal device 110) may include means for performing the respective steps of the method 300. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0142] In some example embodiments, the apparatus comprises means for obtaining, from a first RAN device, an indication including an unique identifier, the unique identifier being assigned by the first RAN device, means for determining that a RRC procedure or a NAS procedure cannot be completed via the first RAN device; and means for in accordance with a determination that a paging message from a second RAN device indicating the apparatus to continue the uncompleted RRC procedure or the uncompleted NAS procedure is received, transmitting, to the second RAN device, a request for a communication between the apparatus and the second RAN device to continue the uncompleted RRC procedure or the uncompleted NAS procedure by using the stored context of the apparatus.
[0143] In some example embodiments, the apparatus may also comprise means for obtaining, from the first RAN device, the indication including the unique identifier in a radio resource control RRC setup procedure, or a RRC resume procedure, or a RRC re- establishment procedure, or a RRC release procedure; and means for storing the context of the apparatus if a RRC connection of the apparatus is released or lost.
[0144] In some example embodiments, the context of the apparatus comprises at least one of:the unique identifier assigned to the apparatus; or a RRC state; or a last RRC message transmitted from the apparatus; or a last RRC message received in the apparatus; an indication for an uncompleted RRC procedure, or a non-access-stratum, NAS, state; or a last NAS message transmitted from the apparatus; or a last NAS message received in the apparatus; or an indication for an uncompleted NAS procedure.
[0145] In some example embodiments, the request for the communication between the apparatus and the second RAN device is a RRC continue request message.
[0146] In some example embodiments, in accordance with a determination that the unique identifier is obtained, the apparatus may also comprise means for determining that the RRC procedure or the non-access-stratum, NAS, procedure is to be continued with a further RAN device other than the first RAN device.
[0147] In some example embodiments, the indication further indicates that the communication is to be continued with the second RAN device.
[0148] In some example embodiments, the paging message received from the second RAN device includes the unique identifier of the apparatus and / or a paging cause, indicating the apparatus to continue the uncompleted RRC procedure or the uncompleted NAS procedure via a communication with the second RAN device, by using the stored context of the apparatus.
[0149] In some example embodiments, the apparatus may also comprise means for transmitting, to the second RAN device, the unique identifier and / or a cause indicating the communication is requested to continue the uncompleted RRC procedure or the uncompleted NAS procedure via the second RAN device, by using the stored context.
[0150] In some example embodiments, the apparatus may also comprise transmitting, a RRC message or a NAS message to the first RAN device and receive a RRC response message or a NAS response message from the second RAN device; or receive, a RRC message or a NAS message from the first RAN device and transmit a RRC response message or a NAS response message to the second RAN device.
[0151] In some example embodiments, an apparatus capable of performing the method 400 (for example, implemented at the first RAN device 120-1) may include means for performing the respective steps of the method 400. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0152] In some example embodiments, the apparatus comprises means for obtaining, from a CN device, a configuration of at least one unique identifier for at least one terminal device; means for assigning, to a terminal device, an unique identifier of the terminal device from the at least one unique identifier, when the apparatus does not have simultaneous connection with the core network device; and means for transmitting an indication including the unique identifier, to the terminal device to be stored as a context of terminal device.
[0153] In some example embodiments, the apparatus comprises means for determining a RRC procedure or a NAS procedure with the terminal device cannot be completed, when the apparatus does not have simultaneous connection with the core network device.
[0154] In some example embodiments, the apparatus comprises means for transmitting, to the terminal device, the indication during a radio resource control RRC setup procedure, or a RRC resume procedure, or a RRC re-establishment procedure, or a RRC release procedure.
[0155] In some example embodiments, the apparatus comprises means for transmitting, to the CN device, the unique identifier assigned to the terminal device.
[0156] In some example embodiments, the unique identifier of the terminal device is transmitted to the core network device via at least one of: an initial UE message, or a UE context store message.
[0157] In some example embodiments, the initial UE message or UE context store message further comprises a context of the terminal device.
[0158] In some example embodiments, the context of the terminal device comprises at least one of: the unique identifier assigned by the apparatus; or a RRC state; or a last RRC message transmitted from the terminal device; or a last RRC message received in the terminal device; an indication for an uncompleted RRC procedure; or a non-access-stratum, NAS, state; or a NAS message transmitted from the terminal device; or a last NAS message received in the terminal device; or an indication for an uncompleted NAS procedure; or a RAN AP context including an AP ID created at the apparatus; or a location of the terminal device.
[0159] In some example embodiments, an apparatus capable of performing the method 500 (for example, implemented at the CN device 130) may include means for performing the respective steps of the method 500. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0160] In some example embodiments, the apparatus comprises means for transmitting, to a first RAN device, a configuration of at least one unique identifier for at least one terminal device, before the terminal device connect with the first RAN device.
[0161] In some example embodiments, the apparatus comprises means for receiving, from the first RAN device, a context of the terminal device created at the first RAN device; and store the context received from the first RAN device and a NAS context established with the terminal device via the first RAN device.
[0162] In some example embodiments, the context of the terminal device is transmitted to the core network device via at least one of: an initial UE message, or a UE context store message.
[0163] In some example embodiments, the context of the terminal device comprises an unique identifier assigned by the first RAN device; a RRC state; a last RRC message transmitted from the terminal device; a last received RRC message received in the terminal device; an indication for an uncompleted RRC procedure; a RAN AP context including an AP ID created at the first RAN device; or a location of the terminal device.
[0164] In some example embodiments, the NAS context comprises at least one of: a non-access-stratum, NAS, state; or a NAS message transmitted from the terminal device; a last NAS message received in the terminal device; or an indication for an uncompleted NAS procedure.
[0165] In some example embodiments, the apparatus comprises means for determining a NAS procedure with the terminal device is uncompleted via the first RAN device.
[0166] In some example embodiments, in accordance with a determination that an uncompleted RRC procedure or the uncompleted NAS procedure with the terminal device is to be continued via a second RAN device, the apparatus comprises means for transmitting, to the second RAN device, a message for resuming the context of the terminal device at the second RAN device, in order to continue the uncompleted RRC procedure or the uncompleted NAS procedure with the terminal device.
[0167] In some example embodiments, the apparatus comprises means for receiving, from the second RAN device, an acknowledge for the message for resuming the context of the terminal device.
[0168] In some example embodiments, the context of the terminal device further includes RAN UE AP ID assigned by the first RAN device, and wherein the acknowledge includes a mapping of the RAN UE AP identifier assigned by the first RAN device and a further RAN UE AP identifier assigned by the second RAN device.
[0169] In some example embodiments, the apparatus comprises means for transmitting, to the second RAN device, a message by using the further RAN UE AP ID assigned by the second RAN device.
[0170] In some example embodiments, the apparatus comprises means for transmitting, a NAS message to the terminal device via the first RAN device and receive a NAS response message from the terminal device via the second RAN device; or receive, a NAS message from the terminal device via the first RAN device, and transmit a NAS response message to the terminal device via the second RAN device.
[0171] In some example embodiments, an apparatus capable of performing the method 600 (for example, implemented at the second device 120-2) may include means for performing the respective steps of the method 600. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0172] In some example embodiments, the apparatus comprises means for receiving, from a core network device, a message including a context of a terminal device created by a first RAN device, for resuming the context of a terminal device at the apparatus, to continue an uncompleted RRC procedure or an uncompleted NAS procedure with the terminal device; means for transmitting a paging message indicating the terminal device to continue the uncompleted RRC procedure or the uncompleted NAS procedure; and means for receiving, from the terminal device, a request for a communication between the apparatus and the terminal device, to continue the uncompleted RRC procedure or the uncompleted NAS procedure by using the context received from core network device.
[0173] In some example embodiments, the context received from the core network device further includes at least one of : the unique identifier assigned to the terminal device; or RRC state; a last RRC message transmitted from the terminal device; a last received RRC message received in the terminal device; an indication for an uncompleted RRC procedure; a RAN AP context including a RAN UE AP ID created at the first RAN device; or a location of the terminal device..
[0174] In some example embodiments, the apparatus comprises means for transmitting, to the core network device, an acknowledge for the message for resuming the context of the terminal device, including at least one of a further RAN UE AP identifier assigned by the apparatus, and a mapping of the RAN UE AP identifier assigned by the first RAN device and the further RAN UE AP identifier assigned by the second RAN device.
[0175] In some example embodiments, the apparatus comprises means for receiving, from the core network device, a further message including the further RAN UE AP ID assigned by the apparatus.
[0176] In some example embodiments, the request for the communication between the apparatus and the terminal device via a RRC continue request.
[0177] FIG. 7 is a simplified block diagram of a device 700 that is suitable for implementing example embodiments of the present disclosure. The device 700 may be provided to implement a communication device, for example, the terminal device 110, the first RAN device 120-1, the CN device 130 and the second RAN device 120-2 as shown in FIG. 1. As shown, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processor 710, and one or more communication modules 740 coupled to the processor 710.
[0178] The communication module 740 is for bidirectional communications. The communication module 740 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interface that is necessary for communication with other network elements. In some example embodiments, the communication module 740 may include at least one antenna.
[0179] The processor 710 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 700 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
[0180] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 724, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , an optical disk, a laser disk, and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 722 and other volatile memories that will not last in the power-down duration.
[0181] A computer program 730 includes computer executable instructions that are executed by the associated processor 710. The instructions of the program 730 may include instructions for performing operations / acts of some example embodiments of the present disclosure. The program 730 may be stored in the memory, e.g., the ROM 724. The processor 710 may perform any suitable actions and processing by loading the program 730 into the RAM 722.
[0182] The example embodiments of the present disclosure may be implemented by means of the program 730 so that the device 700 may perform any process of the disclosure as discussed with reference to FIG. 2 to FIG. 6. The example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
[0183] In some example embodiments, the program 730 may be tangibly contained in a computer readable medium which may be included in the device 700 (such as in the memory 720) or other storage devices that are accessible by the device 700. The device 700 may load the program 730 from the computer readable medium to the RAM 722 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .
[0184] FIG. 8 shows an example of the computer readable medium 800 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 800 has the program 730 stored thereon.
[0185] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[0186] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
[0187] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
[0188] In the context of the present disclosure, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.
[0189] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0190] Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated, certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single embodiment may also be implemented in a plurality of embodiments separately or in any suitable sub-combination.
[0191] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
1.An apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:obtain, from a first radio access network, RAN, device, an indication including an unique identifier, the unique identifier being assigned by the first RAN device,determine that a radio resource control, RRC, procedure or a non-access-stratum, NAS, procedure cannot be completed via the first RAN device; andin accordance with a determination that a paging message from a second RAN device indicating the apparatus to continue the uncompleted RRC procedure or the uncompleted NAS procedure is received, transmit, to the second RAN device, a request for a communication between the apparatus and the second RAN device, to continue the uncompleted RRC procedure or the uncompleted NAS procedure by using the stored context of the apparatus.2.The apparatus of Claim 1, wherein the apparatus is further caused toobtain, from the first RAN device, the indication including the unique identifier in RRCsetup procedure, or a RRC resume procedure, or a RRC re-establishment procedure, or a RRC release procedure; andstore the context of the apparatus if a RRC connection of the apparatus is released or lost.3.The apparatus of Claim 1 or 2, wherein the context of the apparatus comprises at least one of:the unique identifier assigned to the apparatus; ora RRC state; ora last RRC message transmitted from the apparatus; ora last RRC message received in the apparatus; oran indication for an uncompleted RRC procedure, ora non-access-stratum, NAS, state; ora last NAS message transmitted from the apparatus; ora last NAS message received in the apparatus; oran indication for an uncompleted NAS procedure.4.The apparatus of Claim 1, wherein the apparatus is further caused to:in accordance with a determination that the unique identifier is obtained, determine that the RRC procedure or the non-access-stratum, NAS, procedure is to be continued with a further RAN device other than the first RAN device.5.The apparatus of Claim 1, wherein the paging message received from the second RAN device includes the unique identifier of the apparatus and / or a paging cause, indicating the apparatus to continue the uncompleted RRC procedure or the uncompleted NAS procedure via a communication with the second RAN device, by using the stored context of the apparatus.6.The apparatus of Claim 1, wherein the apparatus is further caused to:transmit, to the second RAN device, the unique identifier and / or a cause indicating the communication is requested to continue the uncompleted RRC procedure or the uncompleted NAS procedure via the second RAN device, by using the stored context.7.The apparatus of Claim 1, wherein the apparatus is further caused to:transmit, a RRC message or a NAS message to the first RAN device, and receive a RRC response message or a NAS response message from the second RAN device; orreceive, a RRC message or a NAS message from the first RAN device; andtransmit a RRC response message or a NAS response message to the second RAN device.8.An apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:obtain, from a core network device, a configuration of at least one unique identifier for at least one terminal device;assign, to a terminal device, an unique identifier of the terminal device from the at least one unique identifier, when the apparatus does not have simultaneous connection with the core network device; andtransmit an indication including the unique identifier, to the terminal device to be stored as a context of terminal device.9.The apparatus of Claim 8, wherein the apparatus is further caused to:determine a RRC procedure or a NAS procedure with the terminal device cannot be completed, when the apparatus does not have simultaneous connection with the core network device.10.The apparatus of Claim 8, wherein the apparatus is further caused to:transmit, to the terminal device, the indication during a radio resource control RRC setup procedure, or a RRC resume procedure, or a RRC re-establishment procedure, or a RRC release procedure.11.The apparatus of Claim 8, wherein the apparatus is further caused to:transmit, to the core network device, the unique identifier assigned to the terminal device.12.An apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:transmit, to a first radio access network, RAN, device, a configuration of at least one unique identifier for at least one terminal device, before the terminal device connect with the first RAN device.13.The apparatus of claim 12, wherein the apparatus is further caused to:receive, from the first RAN device, a context of the terminal device created at the first RAN device; andstore the context received from the first RAN device, and a NAS context established with the terminal device via the first RAN device.14.The apparatus of Claim 13, wherein the NAS context comprises at least one of:a non-access-stratum, NAS, state; ora NAS message transmitted from the terminal device;a last NAS message received in the terminal device; oran indication for an uncompleted NAS procedure.15.The apparatus of claim 12 to 14, wherein the apparatus is further caused to:in accordance with a determination that an uncompleted RRC procedure or the uncompleted NAS procedure with the terminal device is to be continued via a second RAN device, transmit, to the second RAN device, a message for resuming the context of the terminal device at the second RAN device, in order to continue the uncompleted RRC procedure or the uncompleted NAS procedure with the terminal device.16.The apparatus of claim 15, the apparatus is further caused to:receive, from the second RAN device, an acknowledge for the message for resuming the context of the terminal device, wherein the context of the terminal device further includes RAN UE AP ID assigned by the first RAN device, and wherein the acknowledge includes a mapping of the RAN UE AP identifier assigned by the first RAN device and a further RAN UE AP identifier assigned by the second RAN device.17.The apparatus of claim 15 or 16, the apparatus is further caused to:transmit, to the second RAN device, a message by using the further RAN UE AP ID assigned by the second RAN device.18.The apparatus of Claim 12 to 17, wherein the apparatus is further caused to:transmit, a NAS message to the terminal device via the first RAN device, and receive a NAS response message from the terminal device via the second RAN device; orreceive, a NAS message from the terminal device via the first RAN device; andtransmit a NAS response message to the terminal device via the second RAN device.19.An apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:receive, from a core network device, a message including a context of a terminal device created by a first RAN device, for resuming the context of a terminal device at the apparatus, to continue an uncompleted radio resource control, RRC, procedure or an uncompleted non-access-stratum, NAS, procedure with the terminal device;transmit a paging message indicating the terminal device to continue the uncompleted RRC procedure or the uncompleted NAS procedure; andreceive, from the terminal device, a request for a communication between the apparatus and the terminal device, to continue the uncompleted RRC procedure or the uncompleted NAS procedure by using the context received from core network device.20.The apparatus of claim 19, the apparatus is further caused to:transmit, to the core network device, an acknowledge for the message for resuming the context of the terminal device, including at least one of a further RAN UE AP identifier assigned by the apparatus, and a mapping of the RAN UE AP identifier assigned by the first RAN device and the further RAN UE AP identifier assigned by the apparatus.
Citation Information
Patent Citations
Handover-based connection resume technique
CN111316701A
Apparatuses to switch between LTE rat and NR rat during transition from inactive state to active state
US20190320483A1
Satellite access with non-continuous coverage
WO2022178457A1
Cited By
Methods and apparatus for NTN-UE detach for onboard satellite architecture in mobile communications
WO2026103594A1
