Method for satellite to enhance non-access stratum process in sf mode of operation and apparatus therefor

Abstract

A satellite is described in Samp; various solutions for enhanced NAS processes in F mode of operation. An apparatus may send a request message to a network node of a wireless network to initiate a NAS process. The network node includes a first satellite. The apparatus may then receive, from the network node, a response message corresponding to the non-access stratum process. The response message comprises at least one of the following: a first indication that the non-access stratum process is not completed; and a second indication to assist the apparatus in subsequent retry or resume of the non-access stratum process.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure is part of a non-provisional application claiming priority to U.S. Patent Application No. 63 / 497,765, filed on April 24, 2023, the contents of which are incorporated herein by reference in their entirety. TECHNICAL FIELD

[0003] The present disclosure relates generally to mobile communications, and more specifically to enhancing non-access stratum (NAS) procedures for satellites in store-and-forward (S&F) mode of operation. BACKGROUND

[0004] Unless otherwise indicated herein, methodologies described in this section are not prior art to the claims listed below, nor are they admitted to be prior art by inclusion in this section.

[0005] In 3rd Generation Partnership Project (3GPP) Release 17, non-terrestrial networks (NTNs) are introduced as a terminal-satellite direct communication technology based on Long-Term Evolution (LTE) or New Radio (NR) interfaces. Through the integration of satellite networks with terrestrial cellular networks (e.g., 4th / 5th Generation (4G / 5G) networks), NTNs can provide ubiquitous coverage that is not limited by terrain and topography. Based on the altitude above the Earth’s surface, satellites can be categorized into geostationary orbit (GEO) satellites, medium earth orbit (MEO) satellites, and low earth orbit (LEO) satellites. FIG. 1 Different satellite orbits in satellite communications are shown. GEO satellites are typically located about 35,786 kilometers (km) above the Earth’s surface. LEO satellites typically operate in orbits that are about 2,000 km above the Earth’s surface or below. MEO satellites typically operate at altitudes that are higher than LEO but lower than GEO, ranging from about 2,000 km above the Earth’s surface to 35,786 km.

[0006] Constellation generally refers to a set of satellites operating at a certain altitude. For example, a sparse LEO constellation can include tens of satellites to provide a certain level of satellite coverage in a way that continuous connectivity to ground stations (GSs) via these satellites is not possible. To address the issue of lack of continuous connectivity, a solution is discussed in 3GPP, i.e., satellites of a sparse LEO constellation can be equipped with base station (BS) and core network (CN) elements, i.e.,. This allows the satellites to provide partial CN services as well as uplink (UL) and downlink (DL) data services for user equipment (UEs), e.g., by implementing a store-and-forward (S&F) type of functionality in the satellites. However, a challenge for S&F operation is that, due to security and / or capacity reasons, the satellites cannot host all network functions, e.g., home subscriber server (HSS) functions for managing subscriber information, and / or security functions for establishing non-access stratum (NAS) / access stratum (AS) security between UEs and the network. Therefore, due to incomplete network functions in the satellites, the S&F solution will impact existing NAS procedures, e.g., initial registration procedure in 5G and attach procedure in 4G. Thus, how to enhance NAS procedures in the satellites in S&F operation mode has become an important issue in newly developed wireless communication systems.

[0007] Therefore, there is a need to provide appropriate solutions and designs to solve this problem. SUMMARY

[0008] The following summary is provided merely for purposes of summarizing the novel and non-obvious concepts, highlights, and advantages of the technology described herein. The following summary is not intended to identify key features of the claimed subject matter, nor is it intended to be used to determine the scope of the claimed subject matter.

[0009] An object of the present disclosure is to propose a solution to solve the aforementioned problem of enhancing NAS procedures in the satellites in S&F operation mode.

[0010] In an aspect, a method can involve a device sending, to a network node of a wireless network, a request message for initiating a NAS procedure, where the network node comprises a first satellite. The method can further involve the device receiving, from the network node, a response message corresponding to the non-access stratum procedure, where the response message comprises at least one of: a first indication that the non-access stratum procedure is not completed; and a second indication to assist the device in a subsequent retry or resumption of the non-access stratum procedure.

[0011] In an aspect, an apparatus can include a transceiver that, during operation, wirelessly communicates with a network node of a wireless network. The apparatus can further include a processor communicatively coupled to the transceiver. During operation, the processor can perform operations including sending, via the transceiver, to the network node, a request message for initiating a NAS procedure, where the network node comprises a first satellite; and receiving, via the transceiver, from the network node, a response message corresponding to the non-access stratum procedure, where the response message comprises at least one of: a first indication that the non-access stratum procedure is not completed; and a second indication to assist the device in a subsequent retry or resumption of the non-access stratum procedure.

[0012] In an aspect, a method can involve receiving, by a network node from a device, a request message for initiating a NAS procedure, where the network node comprises a first satellite. The method can further involve sending, by the network node to the device, a response message corresponding to the non-access stratum procedure, where the response message comprises at least one of: a first indication that the non-access stratum procedure is not completed; and a second indication to assist the device in a subsequent retry or resumption of the non-access stratum procedure.

[0013] Notably, while the description provided herein can be in the context of certain radio access technologies, networks, and network topologies, such as Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, 5G, New Radio (NR), Internet-of-Things (IoT) and Narrow Band Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), Beyond 5G (B5G), and 6G, the proposed concepts, schemes, and any variants / derivatives thereof can be implemented in other types of radio access technologies, networks, and network topologies. Thus, the scope of the disclosure is not limited to the examples described herein. BRIEF DESCRIPTION OF DRAWINGS

[0014] The accompanying drawings are included to provide a further understanding of the application, and are incorporated in and constitute a part of this application. The drawings illustrate embodiments of the application and, together with the description, serve to explain the principles of the application. It is understood that the drawings are not necessarily to scale, as some components can be exaggerated for clarity of illustration.

[0015] FIG. 1 Different satellite orbits in satellite communications are shown.

[0016] FIG. 2 Example scenarios of a communication environment in which various proposed methods and schemes according to embodiments of the present disclosure can be implemented are shown.

[0017] FIG. 3A and 3B show example scenarios of enhanced NAS procedures for satellites in S&F mode of operation according to embodiments of the present disclosure.

[0018] FIG. 4 Example scenarios of evolved packet system (EPS) mobility management (EMM) or 5G mobility management (5GMM) information elements (IEs) for carrying retry assistance information according to embodiments of the present disclosure are shown.

[0019] FIG. 5 is a block diagram of an example communication system according to embodiments of the present disclosure.

[0020] FIG. 6 is a flowchart of an example procedure according to embodiments of the present disclosure.

[0021] FIG. 7 is a flowchart of another example procedure according to embodiments of the present disclosure. DETAILED DESCRIPTION

[0022] Detailed embodiments and implementations of the claimed subject matter are disclosed herein. It is understood, however, that the disclosed embodiments and implementations are merely examples of the claimed subject matter and can be embodied in various forms. The application can be implemented in numerous ways, including but not limited to the exemplary embodiments and implementations described herein. Rather, these exemplary embodiments and implementations are provided so that this disclosure will be thorough and complete and will fully convey the scope of the application to those skilled in the art. In the following description, details of well-known features and techniques can be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0023] SUMMARY

[0024] Embodiments according to the present disclosure relate to various techniques, methods, schemes, and / or solutions related to enhancements of NAS procedures with satellites in S&F mode of operation. According to the present disclosure, multiple possible solutions can be implemented individually or jointly. That is, although these possible solutions can be described separately below, two or more of these possible solutions can be implemented in one or another combination.

[0025] FIG. 2An example scenario 200 of a communication environment in which various proposed methods and schemes according to embodiments of the disclosure can be implemented is shown. The scenario 200 involves a UE 210 wirelessly communicating with a network 220 (e.g., a wireless network including an NTN and a terrestrial network (TN)) via a terrestrial network node 222 (e.g., an evolved Node-B (eNB), a Next Generation Node-B (gNB), or a transmission / reception point (TRP)) and / or a non-terrestrial network node 224 (e.g., a satellite). The UE 210 can be an IoT device, such as an NB-IoT UE or an enhanced Machine Type Communication (eMTC) UE (e.g., a bandwidth reduced low complexity (BL) UE or a coverage enhancement (CE) UE). The non-terrestrial network node 224 can operate in an S&F mode of operation to form a satellite cell for wireless communication with the UE 210 over a feeder link to a GS (e.g., the terrestrial network node 222). In some embodiments, the non-terrestrial network node 224 can include one or more constellations of satellites (sparse LEO), and each satellite can be equipped with some eNB / gNB and CN functionalities / elements (e.g., without HSS functionality for managing user information and / or security functionality for establishing NAS / AS security between the UE 210 and the network 220), providing partial CN services and UL and DL data services for the UE 210 by implementing S&F type functionalities in the satellite. In such a communication environment, the UE 210, the network 220, the terrestrial network node 222, and the non-terrestrial network node 224 can implement various schemes related to NAS procedure enhancements for satellites in an S&F mode of operation as described below. Notably, while various proposed schemes can be described separately or individually below, in actual embodiments, some or all of the proposed schemes can be used or implemented jointly. Of course, each proposed scheme can be used or implemented separately or individually.

[0026] In this disclosure, NTN refers to a network that provides communication services for UEs using radio frequency (RF) and information processing resources carried on high, medium, or low orbit satellites or other high-altitude communication platforms. According to the load capacity on the satellite, there are two typical scenarios, i.e., transparent payload and regenerative payload. In the transparent payload mode, the satellite does not process signals and waveforms in the communication service, but only forwards data as an RF amplifier. In the regenerative payload mode, the satellite has processing capabilities such as modulation / demodulation, encoding / decoding, switching, routing, etc. in addition to RF amplification.

[0027] Since the satellite can not carry all network functions, there can be some impacts on existing NAS procedures. For example, if a new subscriber (e.g., a UE) is performing an initial registration / attach procedure with a satellite that currently lacks access to a GS, the initial registration / attach procedure needs to be split into two or more stages. In the first stage (e.g., the first flyover), the UE is allowed to start the initial registration / attach procedure with a satellite that identifies the UE. In the second stage (e.g., the second flyover after the UE information is uploaded to the satellite), the UE is allowed to start the initial registration / attach procedure again to complete the procedure. However, in 3GPP, the details of the NAS procedure for the satellite in the S&F operation mode have not been fully discussed.

[0028] In view of the above, this disclosure proposes several solutions related to NAS procedure enhancements for the satellite in the S&F operation mode. According to the solutions of this disclosure, a UE can send a request message (e.g., an attach request message or a registration request message) to a network node of a wireless network for initiating a NAS procedure, where the network node includes a satellite operating in the S&F operation mode. Then, the UE can receive a response message corresponding to the NAS procedure from the network node, where the response message includes at least one of: a first indication that the NAS procedure is not completed (e.g., a reject cause); and a second indication for assisting the UE to retry or resume the NAS procedure in a subsequent attempt. Thereafter, the UE can suspend / terminate the NAS procedure based on the first indication, and retry / resume the NAS procedure based on the second indication. On the other hand, for a network node including a satellite operating in the S&F operation mode, it can receive a request message for initiating a NAS procedure from a UE. Then, the network node can send a response message corresponding to the NAS procedure to the UE, where the response message includes at least one of: a first indication that the NAS procedure is not completed; and a second indication for assisting the UE to retry or resume the NAS procedure in a subsequent attempt. Therefore, by applying the solutions of this disclosure, the NAS procedure for the satellite in the S&F operation mode can be enhanced to allow the NAS procedure to be properly processed and successfully completed.

[0029] FIG. 3Aand 3B show an example scenario 300 of enhanced NAS procedure for a satellite in S&F operation mode according to an embodiment of the disclosure. The scenario 300 involves a UE wirelessly communicating with a multi-satellite (IoT) NTN. It is assumed that initially the UE is turned on and needs to be registered in the network, but the UE's (terrestrial) home public land mobile network (PLMN) is not found, the UE starts searching for a satellite cell. In step 301, a first satellite (denoted as SAT#i) enters the communication range of the UE, i.e., the UE detects the cell of SAT#i. The UE can acquire the PLMN and the two-line element set (TLE) of multiple satellites in the constellation (e.g., from system information block type 32 (SIB32)). The UE can also learn from system information block type 31 (SIB31) or SIB32 that the satellite cell is operating in S&F operation mode. In step 302, the UE initiates an initial registration / attach procedure by sending a registration / attach request message. In one example, in the registration / attach request message, the UE can include its capability information indicating the UE's capability of handling S&F operation (e.g., through a "S&F function supported" flag).

[0030] In step 303, the first satellite rejects the initial registration / attach procedure due to the lack of currently active feeder link to retrieve the subscription data from the GS during the satellite pass, as the UE's subscription data, e.g., E-UTRAN authentication vector (AV), is missing on the satellite. Specifically, the first satellite rejects the initial registration / attach procedure by sending a registration / attach reject message to the UE, the registration / attach reject message including at least a new rejection cause (e.g., indicating that the S&F operation NAS procedure is not completed) and retry assistance information (i.e., an indication to assist the UE in a subsequent retry or resume NAS procedure). In this scenario, the retry assistance information includes a value of a timer to indicate when the UE is allowed to retry or resume the NAS procedure.

[0031] In step 304, the UE suspends / terminates the initial registration / attach procedure, and starts a timer with the value, and the UE is not allowed to retry or resume the NAS procedure until the timer expires. Next, in step 305, a second satellite (denoted as SAT#j) enters the communication range of the UE. Similar to the first satellite described in step 303, assume that the second satellite also operates in the S&F mode, and there is no subscription information (e.g. E-UTRAN AV) on the satellite to resume / complete the attach registration with the UE. When detecting the cell of the second satellite, the UE can identify that the satellite cell belongs to the same PLMN as the cell it previously tried the initial registration / attach procedure, and learn from the broadcast system information that the second satellite operates in the S&F mode. In this scenario, the UE does not trigger the retry or resume of the initial registration / attach procedure since the second satellite operates in the S&F mode and the timer has not expired yet.

[0032] In step 306, the timer on the UE expires. From this point, the UE knows that it can retry or resume the initial registration / attach procedure in any upcoming satellite cell of the PLMN. Subsequently, in step S307, a third satellite (denoted as SAT#k) enters the communication range of the UE. In step 308, in response to detecting the cell of the third satellite after the timer expires, the UE retries or resumes the initial registration / attach procedure in the third satellite since the timer has expired. Specifically, the UE retries or resumes the initial registration / attach procedure by sending a registration / attach request message. Assume that at some point in time prior to step 308, the first satellite is connected to the GS via the feeder link, so that the first satellite can exchange information with the ground network to obtain the subscription information (e.g. E-UTRAN AV) of the UE. Further, assume that at some point in time prior to step 308, the third satellite is also connected to the GS via the feeder link, and the E-UTRAN AV of the subscriber / UE is uploaded to the third satellite, in view of the expectation that the third satellite will fly over the area where the UE can retry / resume the initial registration / attach procedure after the timer expires.

[0033] In step 309, the authentication and security setup procedure is successfully completed in view of the fact that the third satellite already has the subscription information of the UE. In step 310, the third satellite accepts the initial registration / attach procedure by sending a registration / attach accept message to the UE. In step 311, the UE replies to the third satellite with a registration / attach complete message, and the initial registration / accept procedure is successfully completed. After that, the UE is able to obtain UL / D data service from the multi-satellite (IoT) NTN.

[0034] In some embodiments, the retry assistance information can include / indicate at least one of: (i) a value of a timer for indicating when the UE is allowed to retry or resume the NAS procedure; (ii) a number of satellites that the UE needs to wait before retrying or resuming the NAS procedure; and (iii) a satellite identifier (ID) for indicating on which satellite the UE is allowed to retry or resume the NAS procedure. In one example, if the retry assistance information indicates the number of satellites that the UE needs to wait before retrying or resuming the NAS procedure, the UE can only retry or resume the NAS procedure in the number of satellites adjacent to the satellite that rejected the NAS procedure. For example, if the EMM / 5GMM IE indicates a value of 1, it means that the next satellite can serve the UE to complete the NAS procedure; if the EMM / 5GMM IE indicates a value of 3, it means that the third satellite after the current satellite can serve the UE to complete the NAS procedure; or if the EMM / 5GMM IE indicates a value of 4, it means that the UE should retry or resume the NAS procedure when the fourth satellite after the current satellite becomes available. In another example, if the retry assistance information includes a satellite ID for indicating the satellite that can serve the UE to complete the NAS procedure, the UE can determine the satellite ID of the detected / available satellite based on the satellite assistance information (e.g., ephemeris data or in-coverage or out-of-coverage information) in the broadcast system information of the detected / available satellite, and only retry or resume the NAS procedure when the satellite ID in the satellite assistance information matches the satellite ID in the retry assistance information. The broadcast system information can include at least one of SIB31, SIB31-NB, SIB32, and SIB32-NB.

[0035] FIG. 4 An example scenario 400 for the EMM / 5GMM IE carrying retry assistance information according to embodiments of the present disclosure is shown. The scenario 400 involves a general packet radio service (GPRS) timer IE for carrying retry assistance information. FIG. 4 Part (A) of FIG. 4A depicts the format of the GPRS timer IE, which includes 2 octets in total. FIG. 4 Part (B) of FIG. 4A depicts a representation of the encoded values of the bits in the second octet of the GPRS timer IE. As shown, the second octet of the GPRS timer IE includes 8 bits, each of which can be set to 0 or 1. FIG. 4As shown in part (B), in case the retry assistance information contains a timer value, bits 6 to 8 in the second octet of the GPRS timer IE define the unit of the timer value of the GPRS timer, while bits 5 to 1 in the second octet of the GPRS timer IE can be encoded to provide the retry assistance information. Alternatively, in case the retry assistance information indicates the number of satellites or contains a satellite ID, the entire second octet of the GPRS timer IE can be encoded to provide the retry assistance information. In one example, if octet 2 of the GPRS timer IE (or another corresponding timer IE) is set to ‘0000 0111’ (i.e., equal to decimal value 7), the UE can retry / resume the NAS procedure in case the UE location becomes available with the seventh satellite (in order). In another example in which the retry assistance information contains a satellite ID, if octet 2 of the GPRS timer IE (or another corresponding timer IE) is set to ‘0111 0101’ (i.e., equal to decimal value 117), the UE can retry / resume the NAS procedure when in coverage of satellite #117.

[0036] It is noted that although in FIG. 4 the GPRS timer IE is used as an example EMM / 5GMM IE to carry the retry assistance information, other EMM / 5GMM IEs, e.g., a new IE or another existing IE, can also be used to carry the retry assistance information, and the present disclosure is not limited thereto.

[0037] Example Implementation

[0038] FIG. 5 An example communication system 500 with an example communication device 510 and an example network device 520 according to an implementation of the present disclosure is shown. Each of the communication device 510 and the network device 520 can perform various functions to implement the schemes, techniques, procedures, and methods described herein with respect to the NAS procedure enhancement for satellites in S&F mode of operation, including the scenarios / schemes described above and the procedures 600 and 700 described below.

[0039] The communication device 510 may be part of an electronic device, which may be a UE, such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, the communication device 510 may be implemented in a smartphone, smartwatch, personal digital assistant, electronic control unit (ECU) in a vehicle, digital camera, or computing device such as a tablet, laptop, or notebook computer. The communication device 510 may also be part of a machine-type device, which may be an IoT, NB-IoT, IIoT, BL, or CE UE, such as a fixed or static device, home device, roadside unit (RSU), wired communication device, or computing device. For example, the communication device 510 may be implemented in a smart thermostat, smart refrigerator, smart door lock, wireless speaker, or home control center. Alternatively, the communication device 510 may be in the form of one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more Reduced Instruction Set Computing (RISC) processors, or one or more Complex Instruction Set Computing (CISC) processors. The communication device 510 may include... FIG. 5 At least some of the components shown are included, for example, the processor 512. The communication device 510 may also include one or more other components unrelated to the proposed solutions of this disclosure (e.g., internal power supply, display device, and / or user interface device). Therefore, for the sake of brevity and simplicity, these components of the communication device 510 are not listed in the [disclosure details]. FIG. 5 It is shown in the text but not described below.

[0040] Network device 520 may be part of an electronic device, which may be a network node, such as a satellite, base station (BS), small cell, router, or gateway of an (IoT) NTN. For example, network device 520 may be implemented in a satellite operating in S&F mode. Alternatively, network device 520 may be implemented as one or more IC chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. Network device 520 may include FIG. 5 At least some of the components shown are included, for example, processor 522. Network device 520 may also include one or more other components unrelated to the proposed solutions of this disclosure (e.g., internal power supply, display device, and / or user interface device); therefore, for the sake of brevity and simplicity, these components of communication device 510 are not included. FIG. 6 It is shown in the text but not described below.

[0041] In an aspect, each of the processor 512 and the processor 522 can be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, although the singular term “processor” is used herein to refer to the processor 512 and the processor 522, each of the processor 512 and the processor 522 can include multiple processors in certain implementations of the present disclosure, while in other implementations can be a single processor. In another aspect, each of the processor 512 and the processor 522 can be implemented in the form of hardware (and optionally firmware) having electronic components, including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more varactors, configured and arranged to achieve certain purposes in accordance with the present disclosure. In other words, each of the processor 512 and the processor 522 is, in at least some implementations, a special purpose machine specially designed, arranged, and configured to perform certain tasks, including the NAS procedure enhancements for satellites in S&F operating mode in UEs (e.g., represented by the communication apparatus 510) and network nodes (e.g., represented by the network apparatus 520) in accordance with various implementations of the present disclosure.

[0042] In some implementations, the communication apparatus 510 can further include a transceiver 516 coupled to the processor 512 and capable of wirelessly transmitting and receiving data. In some implementations, the transceiver 516 can be capable of wirelessly communicating with different types of user equipment (UEs) and / or wireless networks of different radio access technologies (RATs). In some implementations, the transceiver 516 can be equipped with multiple antenna ports (not shown), such as four antenna ports. That is, the transceiver 516 can be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communications. In some implementations, the network apparatus 520 can further include a transceiver 526 coupled to the processor 522. The transceiver 526 can include a transceiver capable of wirelessly transmitting and receiving data. In some implementations, the transceiver 526 can be capable of wirelessly communicating with different types of UEs of different RATs. In some implementations, the transceiver 526 can be equipped with multiple antenna ports (not shown), such as four antenna ports. That is, the transceiver 526 can be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communications.

[0043] In some implementations, the communication device 510 can also include a memory 514 coupled to the processor 512 and accessible to the processor 512 for storing data and instructions. In some implementations, the network device 520 can also include a memory 524 coupled to the processor 522 and accessible to the processor 522 for storing data and instructions. Each of the memory 514 and the memory 524 can include a random access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero capacitor RAM (Z-RAM). Alternatively or additionally, each of the memory 514 and the memory 524 can include a read-only memory (ROM), such as a mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively or additionally, each of the memory 514 and the memory 524 can include a non-volatile random access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase change memory.

[0044] Each of the communication device 510 and the network device 520 can be a communication entity capable of communicating using various schemes presented in the disclosure. For illustrative purposes and without limitation, capability descriptions of the communication device 510 as a UE (e.g., an IoT UE such as a NB-IoT UE or a BL / CE UE) and the network device 520 as a network node (e.g., a satellite) are provided below.

[0045] Under certain schemes presented in the disclosure regarding enhanced NAS procedures for satellites in S&F operation mode, the processor 512 of the communication device 510 can transmit, via the transceiver 516, a request message for initiating a NAS procedure to the network device 520, where the network device 520 comprises a first satellite. Then, the processor 512 can receive, via the transceiver 516, a response message corresponding to the NAS procedure from the network device 520, where the response message comprises at least one of: a first indication that the NAS procedure is not completed; and a second indication for assisting the communication device 510 in a subsequent retry or resume of the NAS procedure.

[0046] In some implementations, the processor 512 can further suspend or terminate the NAS procedure based on the first indication, and retry or resume the NAS procedure based on the second indication.

[0047] In some implementations, the first indication can be a reject cause.

[0048] In some implementations, the first satellite can operate in the S&F operation mode.

[0049] In some embodiments, the second indication can comprise a value of a timer for indicating when the communication apparatus 510 is allowed to retry or resume the NAS procedure. Further, the processor 512 can also start the timer with the value in response to receiving the response message, wherein the retry or resume of the NAS procedure is performed after the timer expires.

[0050] In some embodiments, the second indication can indicate a number of satellites that the communication apparatus 510 needs to wait for before retrying or resuming the NAS procedure. Further, the processor 512 can also determine a second satellite of the number of satellites that is adjacent to the first satellite, wherein the retry or resume of the NAS procedure is performed if the second satellite is available at the location of the communication apparatus 510.

[0051] In some embodiments, the processor 512 can also receive broadcast system information from the network apparatus 520, wherein the broadcast system information comprises satellite assistance information, and the second satellite is determined based on the satellite assistance information.

[0052] In some embodiments, the broadcast system information can comprise SIB31, SIB31-NB, SIB32, or SIB32-NB.

[0053] In some embodiments, the satellite assistance information can comprise ephemeris data or in-orbit or out-of-coverage information.

[0054] In some embodiments, the second indication can comprise a satellite identifier (ID) for indicating on which satellite the communication apparatus 510 is allowed to retry or resume the NAS procedure, and the retry or resume of the NAS procedure is performed if a second satellite associated with the satellite ID is available at the location of the communication apparatus 510.

[0055] In some embodiments, the processor 522 of the network apparatus 520 can receive, via the transceiver 526, a request message for initiating a NAS procedure from a communication apparatus 510, wherein the network apparatus 520 comprises a first satellite. Then, the processor 522 can send, via the transceiver 526, a response message corresponding to the NAS procedure to the communication apparatus 510, wherein the response message comprises at least one of: a first indication that the NAS procedure is not completed; and a second indication for assisting the communication apparatus 510 in a subsequent retry or resume of the NAS procedure.

[0056] In some embodiments, the first satellite can operate in a S&F operation mode.

[0057] In some embodiments, the first indication can be a reject cause, and the second indication can include at least one of: (i) a value of a timer for indicating when the communication apparatus 510 is allowed to retry or resume the NAS procedure; (ii) a number of satellites that the communication apparatus 510 needs to wait for before retrying or resuming the NAS procedure; and (iii) a satellite identifier (ID) for indicating on which satellite the communication apparatus 510 is allowed to retry or resume the NAS procedure.

[0058] In some embodiments, the processor 522 can further transmit, via the transceiver 526, broadcast system information to the communication apparatus 510, where the broadcast system information includes the satellite assistance information.

[0059] In some embodiments, the broadcast system information can include SIB31, SIB31-NB, SIB32, or SIB32-NB, and / or the satellite assistance information can include ephemeris data or in-coverage or out-of-coverage information.

[0060] Exemplary flow

[0061] FIG. 6 An example flow 600 according to embodiments of the present disclosure is shown. The flow 600 can be an example implementation, whether partial or complete, of the above-described scenarios / scenarios involving enhanced NAS procedures for satellites in S&F mode of operation. The flow 600 can represent one aspect of an implementation of features of the communication apparatus 510. The flow 600 can include one or more operations, actions, or functions illustrated by one or more of blocks 610 and 620. Although illustrated as discrete blocks, various blocks of the flow 600 can be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Further, the blocks of the flow 600 can be performed in the order shown in FIG. 6, or in a different order. FIG. 7 The flow 600 can be implemented by the communication apparatus 510 or any suitable UE or machine-type device. For illustrative purposes only and without limitation, the flow 600 is described below in the context of the communication apparatus 510 as a UE and the network apparatus 520 as a network node. The flow 600 can begin at block 610.

[0062] At 610, the flow 600 can involve the processor 512 of the communication apparatus 510 transmitting, via the transceiver 516, a request message to the network apparatus 520 for initiating a NAS procedure, where the network apparatus 520 includes a first satellite. The flow 600 can proceed from 610 to 620.

[0063] At 620, the process 600 can involve the processor 512 receiving, via the transceiver 516 from the network device 520, a response message corresponding to the NAS procedure, wherein the response message comprises at least one of: a first indication that the NAS procedure is not completed; and a second indication for assisting the communication device 510 to retry or resume the NAS procedure.

[0064] In some embodiments, the process 600 can further involve the processor 512 suspending or terminating the NAS procedure based on the first indication, and retrying or resuming the NAS procedure based on the second indication.

[0065] In some embodiments, the first indication can be a reject cause.

[0066] In some embodiments, the first satellite can operate in an S&F mode of operation.

[0067] In some embodiments, the second indication can comprise a value of a timer for indicating when the communication device 510 is allowed to retry or resume the NAS procedure. Further, the process 600 can further involve the processor 512 starting the timer with the value in response to receiving the response message, wherein the retry or resume of the NAS procedure is performed after the timer expires.

[0068] In some embodiments, the second indication can indicate a number of satellites that the communication device 510 needs to wait for before retrying or resuming the NAS procedure. Further, the process 600 can further involve the processor 512 determining a second satellite of the number of satellites that is adjacent to the first satellite, wherein the retry or resume of the NAS procedure is performed if the second satellite is available at the location of the communication device 510.

[0069] In some embodiments, the process 600 can further involve the processor 512 receiving, via the transceiver 516 from the network device 520, broadcast system information, wherein the broadcast system information comprises satellite assistance information, and the second satellite is determined based on the satellite assistance information.

[0070] In some embodiments, the broadcast system information can comprise SIB31, SIB31-NB, SIB32, or SIB32-NB.

[0071] In some embodiments, the satellite assistance information can comprise ephemeris data or in-coverage or out-of-coverage information.

[0072] In some embodiments, the second indication can comprise a satellite identifier (ID) for indicating on which satellite the communication device 510 is allowed to retry or resume the NAS procedure, and the retry or resume of the NAS procedure is performed if a second satellite associated with the satellite ID is available at the location of the communication device 510.

[0073] FIG. 7 An example flow 700 is shown in accordance with embodiments of the present disclosure. The flow 700 can be an example implementation, whether partial or complete, of the above-described scenarios / scenarios involving enhanced NAS procedures for satellites in S&F operating mode. The flow 700 can represent one aspect of a feature implementation of the network device 520. The flow 700 can include one or more operations, actions, or functions shown by one or more of blocks 710 and 720. Although shown as discrete blocks, each block of the flow 700 can be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Also, the blocks of the flow 700 can be performed in an order different from that shown, as indicated by the various arrows in the figure. The flow 700 can be implemented by the network device 520 and any variants thereof. For illustrative purposes only and not by way of limitation, the flow 700 is described below in the context of the communication device 510 as a UE and the network device 520 as a network node. The flow 700 can begin at block 710. ​

[0074] At 710, the flow 700 can involve the processor 522 of the network device 520 receiving, via the transceiver 526, a request message from the communication device 510 for initiating a NAS procedure, where the network device 520 comprises a first satellite. The flow 700 can proceed from 710 to 720.

[0075] At 720, the flow 700 can involve the processor 522 transmitting, via the transceiver 526, a response message corresponding to the NAS procedure to the communication device 510, where the response message comprises at least one of: a first indication that the NAS procedure is not completed; and a second indication for assisting the communication device 510 in a subsequent retry or resuming the NAS procedure.

[0076] In some embodiments, the first satellite can operate in the S&F operating mode.

[0077] In some embodiments, the first indication can be a reject cause.

[0078] In some embodiments, the second indication can comprise a value of a timer for indicating when the communication device 510 is allowed to retry or resume the NAS procedure.

[0079] In some embodiments, the second indication can indicate a number of satellites that the communication device 510 needs to wait for before retrying or resuming the NAS procedure.

[0080] In some embodiments, the flow 700 can further involve the processor 522 transmitting, via the transceiver 526, broadcast system information to the communication device 510, where the broadcast system information comprises satellite assistance information.

[0081] ​In some embodiments, the broadcast system information can comprise SIB31, SIB31-NB, SIB32, or SIB32-NB, and / or the satellite assistance information can comprise ephemeris data or in-coverage or out-of-coverage information.

[0082] In some embodiments, the second indication can comprise a satellite identifier (ID) for indicating on which satellite the communication apparatus 510 is allowed to retry or resume the NAS procedure.

[0083] Additional Description

[0084] The subject matter described herein is sometimes illustrated using different components contained within, or connected with, different other components. It is to be understood that the described architectures are merely examples, and that in fact many other architectures can implement the same functions in differing configurations. In the conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermediate components. Likewise, any two components so associated can also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being "operably couplable", to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and / or physically interacting components and / or wirelessly interactable and / or wirelessly interacting components and / or logically interacting and / or logically interactable components.

[0085] Further, with respect to the use of substantially any plural and / or singular term herein, those having skill in the art can translate the plural and / or singular term to a singular and / or plural term, respectively, as is appropriate in the context of a particular situation, now known or later developed. Specifically, where any singular term is used herein to connote "one", it will be understood by those skilled in the art to include, within its meaning, the plural term "multiple", as well or in other contexts.

[0086] Further, those skilled in the art will appreciate that, in general, the terms used herein, particularly in the appended claims, such as the terms in the body of the appended claims, are intended to be interpreted as "open" terms, e.g., the terms "comprising", "including," "carrying" should be construed as "including but not limited to", the term "having" should be construed as "having at least", the term "including" should be construed as "including, but not limited to". Those skilled in the art will further appreciate that, if a specific number of an introduced claim recitation is intended, such intent will be recited explicitly in the claim, and in the absence of such recitation, no such intent is present. For example, to help understand, the following appended claims can contain the use of introductory phrases such as "at least one" and "one or more" to introduce a claim recitation. However, the use of such phrases is not to be construed to imply that the exclusive

[0087] In light of the above, it will be appreciated that the various embodiments of the application have been described herein for purposes of illustration, and that various modifications can be made without departing from the scope and spirit of the application. Accordingly, the various embodiments disclosed herein are not intended to be limiting, the true scope and spirit of the application being indicated by the following claims.

Claims

1. A method comprising: The device's processor sends a request message to a network node in a wireless network, including a first satellite, to initiate a non-access stratum process; and The processor receives a response message from the network node corresponding to the non-access stratum process, wherein the response message includes at least one of the following indications: a first indication that the non-access stratum process has not been completed; and a second indication to assist the device in subsequently retrying or resuming the non-access stratum process.

2. The method as described in claim 1, wherein, Further includes: The processor suspends or terminates the non-access layer process based on the first instruction; and The processor may retry or resume the non-access layer process based on the second instruction.

3. The method as described in claim 1, wherein, The first instruction is the reason for refusal.

4. The method of claim 1, wherein, The first satellite is operating in store-and-forward mode.

5. The method of claim 1, wherein, The second indication includes a timer value for indicating when the device is allowed to retry or resume the non-access stratum process, and the method further includes: The processor starts the timer with this value in response to the received response message. The process will either retry or resume the non-access layer process after the timer expires.

6. The method of claim 1, wherein, The second indication specifies the number of satellites the device needs to wait before retrying or resuming the non-access stratum process, and the method further includes: The processor determines the number of second satellites adjacent to the first satellite. If the location of the second satellite at the device is available, the non-access layer process will be retried or resumed.

7. The method of claim 6, wherein, Further includes: The processor receives broadcast system information from the network node, wherein the broadcast system information includes satellite-aided information, which includes ephemeris data or information within or outside the satellite coverage area, and The second satellite was identified based on the satellite's auxiliary information.

8. The method of claim 1, wherein, The second indication includes a satellite identifier that indicates on which satellite the device is permitted to retry or resume the non-access stratum process, and that the retry or resumption of the non-access stratum process is performed if a second satellite associated with the satellite identifier is available at the device's location.

9. An apparatus comprising: A transceiver that communicates wirelessly with network nodes in a wireless network during operation; as well as A processor, communicatively coupled to the transceiver, enables the processor to perform the following operations during operation: The transceiver sends a request message to the network node for initiating a non-access stratum process, wherein the network node includes a first satellite; and The transceiver receives a response message corresponding to the non-access stratum process from the network node, wherein the response message includes at least one of the following: a first indication that the non-access stratum process has not been completed; and a second indication to assist the device in retrying or resuming the non-access stratum process in the future.

10. The apparatus of claim 9, wherein, During operation, the processor further performs the following operations: Based on the first instruction, the non-access layer process may be suspended or terminated; and Based on this second indication, the non-access stratum process can be retried or resumed.

11. The apparatus of claim 9, wherein, The first instruction is the reason for refusal.

12. The apparatus of claim 9, wherein, The first satellite is operating in store-and-forward mode.

13. The apparatus of claim 9, wherein, The second indication includes a timer value for indicating when the device is allowed to retry or resume the non-access stratum process, and during operation, the processor further performs the following operations: Start the timer with this value in response to the received response message. The process will either retry or resume the non-access layer process after the timer expires.

14. The apparatus of claim 9, wherein, The second instruction indicates the number of satellites the device needs to wait before retrying or resuming the non-access stratum process, and that during operation, the processor further performs the following operations: Determine the number of second satellites adjacent to the first satellite. If the location of the second satellite at the device is available, the non-access layer process will be retried or resumed.

15. The apparatus of claim 14, wherein, During operation, and during operation, the processor further performs the following operations: Broadcast system information is received from the network node via a transceiver. This broadcast system information includes satellite-aided information, which includes ephemeris data or information within or outside the satellite's coverage area. The second satellite was identified based on the satellite's auxiliary information.

16. The apparatus of claim 9, wherein, The second indication includes a satellite identifier that indicates on which satellite the device is permitted to retry or resume the non-access stratum process, and that the retry or resumption of the non-access stratum process is performed if a second satellite associated with the satellite identifier is available at the device's location.

17. A method comprising: The processor of the network node receives a request message from the device for initiating a non-access stratum process, wherein the network node includes a first satellite; and The processor sends a response message to the device corresponding to the non-access stratum process, wherein the response message includes at least one of the following: a first indication that the non-access stratum process has not been completed; and a second indication to assist the device in retrying or resuming the non-access stratum process in the future.

18. The method of claim 17, wherein, The first satellite is operating in store-and-forward mode.

19. The method of claim 17, wherein, The first instruction is the reason for refusal, and the second instruction includes at least one of the following: When is the timer value for which the device is allowed to retry or resume the non-access stratum process? The number of satellites the device needs to wait before retrying or resuming the non-access stratum process; as well as A satellite identifier used to indicate on which satellite the device can retry or resume the non-access stratum process.

20. The method of claim 17, wherein, Further includes: The processor sends broadcast system information to the device, wherein the broadcast system information includes satellite auxiliary information, which includes ephemeris data or information within or outside the satellite coverage area.

Images