Non access stratum (NAS) and satellite store-and-forward operation

By coordinating NAS procedures with satellite operating mode and transition times, the UE efficiently manages NAS operations in non-terrestrial networks, conserving resources and ensuring successful connectivity.

WO2026236120A1PCT designated stage Publication Date: 2026-11-12GOOGLE LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/US2026/026540
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-04
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in managing Non-Access Stratum (NAS) procedures when satellites in non-terrestrial networks (NTNs) transition between store-and-forward (S&F) mode and normal mode, leading to inefficient use of power and radio resources due to unpredictable feeder link availability.

Method used

User Equipment (UE) manages NAS procedures based on satellite operating mode and transition times by refraining from performing NAS procedures during S&F mode and postponing them until the satellite transitions to normal mode, using system information to coordinate timing.

Benefits of technology

This approach conserves power and radio resources by preventing failed NAS procedures, improves connectivity, and ensures successful completion of NAS procedures when the satellite is in normal mode.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2026026540_12112026_PF_FP_ABST
    Figure US2026026540_12112026_PF_FP_ABST
Patent Text Reader

Abstract

This disclosure provides systems, methods and apparatuses for managing a non-access stratum (NAS) procedure via a non-terrestrial network (NTN) node (e.g., a satellite 112) that supports a store-and-forward (S&F) capability. A user equipment (UE) (102) receives system information (105) indicating a transition time when the satellite will transition from an S&F mode to a normal mode, or from the normal mode to the S&F mode. In some aspects, the UE refrains (107) from performing a NAS procedure when the UE is camping on a cell of a satellite that is operating in the S&F mode. The UE performs (109) the NAS procedure when (or after) the satellite transitions to the normal mode. The UE can manage when to perform (or refrain from performing) the NAS procedure based on the operating mode of the satellite and transition time.
Need to check novelty before this filing date? Find Prior Art

Description

Docket No. 14730932100PCTNON ACCESS STRATUM (NAS) AND SATELLITE STORE-AND-FORWARD OPERATIONRELATED APPLICATION

[0001] This application claims the priority benefit of U.S. Provisional Patent Application Serial No. 63 / 802,225, filed May 8, 2025, entitled “NON ACCESS STRATUM (NAS) AND SATELLITE STORE-AND-FORWARD OPERATION,” the entire contents of which are hereby incorporated by reference herein.TECHNICAL FIELD

[0002] This disclosure relates generally to wireless communication, and some aspects relate to a store and forward capability of a non-terrestrial network (NTN) to support user equipment (UE) non-access stratum (NAS) connectivity.BACKGROUND

[0003] This background description is provided for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

[0004] A wireless communication system includes one or more network entities (such as base stations) enabling communication for a mobile communication device (referred to as a user equipment (UE)). Each base station operates one or more cells to provide coverage for the UE. Existing wireless communication systems and network selection techniques are based primarily on legacy terrestrial networks (TNs). The 3rdGeneration Partnership Project (3 GPP) organization has proposed to extend 5thGeneration (5G) communications to non-terrestrial networks (NTNs) with 5G new radio (NR) technologies, or with the Long-Term-Evolution (LTE) technologies tailored for the Narrowband Internet-of-Things (NB-IoT) or the enhanced Machine Type Communication (eMTC) technologies. A non-terrestrial network (NTN) refers to a network, or segment of a network, using radio frequency (RF) resources on board an NTN node. An NTN can also include inter-satellite links (ISLs) when multiple NTN nodes form constellations. Example NTN nodes include spaceborne vehicles and airborne vehicles, such asDocket No. 14730932100PCTa satellite, airplane, balloon, or uncrewed aerial vehicle (UAV or drone). For simplicity, the discussion below refers to all such apparatuses as satellites or NTN nodes.

[0005] In addition to NTN nodes, an NTN can include one or more gateways (sometimes referred to as NTN gateways or sat-gateways). NTN gateways connect satellites to a core network. A feeder link refers to a communication link between a sat-gateway and a satellite. A service link refers to a communication link between a satellite and a UE. The UE and the NTN node can implement a radio resource control (RRC) protocol to manage aspects of the service link (sometimes referred to as an Access Stratum (AS)), such as radio resources, connectivity state, etc. A Non-Access Stratum (NAS) procedure refers to a protocol between the UE and a component of the core network. During normal operation (sometimes referred to as “normal mode”), NAS messages are communicated via a combination of the service link and the feeder link when the satellite connects to one or more serving NTN gateways with sufficient time duration to proceed with mobility anchoring and hand-over.

[0006] Some NTN deployments provide coverage for UEs in remote regions. In some instances, even if a UE is under the coverage of a satellite (such as a non-geostationary (NGSO) satellite), that satellite might not have a feeder link to an NTN gateway. Thus, the satellite cannot directly connect the UE to services of the core network when the service link and feeder link are not concurrently available. Depending on the location of the satellite in relation to an NTN gateway, there might be instances where the feeder link can become temporarily unavailable. The 3 GPP has proposed a store-and-forward (S&F) operation to enable partial connectivity when the service link and the feeder link are not concurrently available. In S&F operation (sometimes referred to as “S&F mode”), a satellite can process part of a NAS procedure using a NAS component onboard the satellite. Alternatively, the satellite can buffer (i.e., temporarily store and then later forward) NAS messages until the relevant feeder link or service link becomes available. When a satellite operating in S&F mode cannot perform a NAS procedure, the satellite will reject the NAS procedure.BRIEF SUMMARY

[0007] The systems, methods, and apparatuses of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0008] One innovative aspect of the subject matter described in this disclosure can be implemented as a method of a user equipment (UE) for wireless communication via a non-Docket No. 14730932100PCTterrestrial network (NTN). The method includes the UE receiving system information indicating a transition time when a first cell of a first satellite will transition from a store-and-forward (S&F) mode to a normal mode. The S&F mode is associated with the first satellite not operating a feeder link to a core network, and the normal mode is associated with the first satellite operating the feeder link to the core network. The method includes the UE refraining from performing a non-access stratum (NAS) procedure via the first cell when the first cell is operating in the S&F mode.

[0009] Another innovative aspect of the subject matter described in this disclosure can be implemented as a method of UE for wireless communication via an NTN. The method includes the UE camping on a cell of a satellite. The method includes the UE receiving system information indicating whether the cell is presently operating in an S&F mode or a normal mode. The system information includes timing information indicating when the cell will transition from the S&F mode to the normal mode, or vice versa. The method includes the UE initiating a NAS procedure. The method includes the UE postponing the NAS procedure until after the satellite transitions to the normal mode based on the timing information.

[0010] Another innovative aspect of the subject matter described in this disclosure can be implemented as a method of UE for wireless communication via an NTN. The method includes the UE camping on a cell of a satellite when the cell is operating in a normal mode, the normal mode associated with the cell operating a feeder link to a core network. The method includes the UE receiving system information indicating that the cell is presently operating in the normal mode and indicating a transition time when the cell will transition from the normal mode to an S&F mode. The S&F mode is associated with the cell not operating the feeder link to the core network. The method includes the UE calculating a remaining time period (77) between a current time ( / ) and the transition time. The method includes the UE refraining from performing a NAS procedure via the cell when the remaining time period (77) is less than a threshold time period ( thresh) ■

[0011] Another innovative aspect of the subject matter described in this disclosure can be implemented as an apparatus that includes a communication unit and a processing system configured to control the communication unit to implement any one of the above-referenced methods.

[0012] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims.Docket No. 14730932100PCTBRIEF DESCRIPTION OF THE DRAWINGS

[0013] Like reference numbers and designations in the various drawings indicate like elements. Note that the relative dimensions of the figures may not be drawn to scale. To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

[0014] FIG. 1 shows an example wireless communication system in which a user equipment (UE) communicates via a non-terrestrial network (NTN) having one or more satellites.

[0015] FIG.2A illustrates an example of store-and-forward (S&F) mode in contrast to a normal mode.

[0016] FIG. 2B shows an example wireless communication system in which a satellite includes onboard non-access stratum (NAS) features.

[0017] FIG. 3 shows an example split mobility management entity (MME) deployment.

[0018] FIG. 4 shows a message diagram in which a NAS procedure is rejected with a S&F wait time duration.

[0019] FIG. 5A shows a system diagram in which a satellite indicates a transition time from S&F mode to normal mode.

[0020] FIG. 5B shows a system diagram in which a satellite indicates a transition time from normal mode to S&F mode.

[0021] FIG. 6 shows a message diagram in which a LIE manages a NAS procedure based on the satellite indicating a transition time from S&F mode to normal mode.

[0022] FIG. 7A shows a message diagram of an example scenario in which a UE determines whether and how to pause a NAS Attach procedure based on the system information indicating a transition time from the S&F mode to the normal mode.

[0023] FIG. 7B shows a message diagram of an example scenario in which a UE determines whether to cancel a NAS Attach procedure based on the system information indicating a transition time from the S&F mode to the normal mode.

[0024] FIG. 7C shows a message diagram of an example scenario in which a UE manages a NAS timer based on the system information indicating a transition time from the S&F mode to the normal mode.

[0025] FIG. 8 shows a message diagram of an example scenario in which a UE manages a NAS procedure based on an operating mode and transition time for a new cell after cell reselection.Docket No. 14730932100PCT

[0026] FIG. 9 shows a message diagram of an example scenario in which a UE controls a NAS timer based on operating mode and transition time for a new cell after cell reselection.

[0027] FIG. 10 shows a message diagram of an example scenario in which a UE manages a NAS procedure based on available time to complete the NAS procedure before the satellite transitions to an S&F mode.

[0028] FIG. 11 shows a flow diagram of example operations of a UE managing a NAS procedure based on a transition time when a cell of a satellite will transition from an S&F mode to a normal mode.

[0029] FIG. 12A shows a flow diagram of example operations of a UE in which the UE determines whether to pause a NAS procedure based on satellite operating mode and transition time.

[0030] FIG. 12B shows a flow diagram of example operations of a UE in which the UE determines whether to cancel a NAS procedure based on satellite operating mode and transition time.

[0031] FIG. 12C shows a flow diagram of example operations of a UE in which the UE manages a NAS timer based on system information indicating a transition time from the S&F mode to the normal mode.

[0032] FIG. 13 shows a flow diagram of example operations of a UE in which the UE manages a NAS procedure based on an operating mode and transition time for a new cell after cell reselection.

[0033] FIG. 14 shows a flow diagram of example operations of a UE in which the UE controls a NAS timer based on operating mode and transition time for a new cell after cell reselection.

[0034] FIG. 15 shows a flow diagram of example operations of a UE in which the UE manages a NAS procedure based on available time to complete the NAS procedure before the satellite transitions to an S&F mode.

[0035] FIG. 16 shows a flow diagram of example operations of a UE.

[0036] FIG. 17 shows another flow diagram of example operations of a UE.

[0037] FIG. 18 shows a flow diagram of example operations of a UE in which the UE managed a NAS procedure based on a remaining time period (71) for a cell of a satellite to operate in the normal mode.

[0038] FIG. 19 shows a flow diagram of example operations of a satellite.Docket No. 14730932100PCT

[0039] FIG. 20 is a block diagram illustrating an example user equipment.

[0040] FIG. 21A shows an example control plane protocol stack in accordance with aspects of this disclosure.

[0041] FIG. 21B shows an example user plane protocol stack in accordance with aspects of this disclosure.

[0042] FIG. 22 shows a block diagram of an example wireless communication system showing hardware features and communication interfaces.DETAILED DESCRIPTION

[0043] The following description is directed to certain implementations for the purpose of describing innovative aspects of this disclosure. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. Some of the examples in this disclosure are based on wireless communication according to the 3rdGeneration Partnership Project (3 GPP) wireless standards, such as the 4th generation (4G) Long Term Evolution (LTE) and 5thgeneration (5G) New Radio (NR) standards. However, the described implementations can be implemented in any device, system, or network that is capable of transmitting and receiving radio frequency signals according to any of the wireless communication standards, including any of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 or 802.16 wireless standards, or other known signals that are used to communicate within a wireless, cellular, or internet of things (loT) network, such as a system utilizing 4G, 5G, sixth generation (6G), Wi-Fi, or future radio technology.

[0044] A non-terrestrial network (NTN) node (e.g., a satellite) can include components for an access stratum (AS) and a non-access stratum (NAS). For example, an NTN node can include functionality associated with a base station (BS) of a radio access network (RAN). In some implementations, an NTN node also includes an on-board mobility management entity (MME) to process NAS messages. In this disclosure, the term “satellite” can refer to any type of NTN node. As described above, a satellite can implement a store-and-forward (S&F) feature when a feeder link between the satellite and a ground node (e.g., an NTN gateway) is unavailable. For clarity, this disclosure refers to a satellite operating in either a S&F mode or normal mode. The S&F mode (sometimes referred to as S&F operation or S&F operating mode) is when the satellite does not have access to the core network but can perform some limited NAS operations (such as buffering NAS messages or processing NAS requests using an on-board MME). The normalDocket No. 14730932100PCTmode (sometimes referred to as normal operation, normal operating mode, or non-S&F mode) is when the satellite has access to the core network via a feeder link.

[0045] A user equipment (UE) can initiate a NAS procedure with an MME onboard a satellite. If the satellite is operating in the S&F mode, the MME might reject the NAS procedure if the MME does not have UE security context or if the MME needs to retrieve UE-specific authentication vectors or subscription information from the core network. Repeating unsuccessful NAS procedure attempts or repeatedly checking the satellite S&F status might consume significant power from the UE. It is desirable for the UE to manage timing for a NAS procedure based on when the satellite is operating in normal mode and refrain from performing a NAS procedure when the satellite is operating in S&F mode.

[0046] This disclosure provides systems, methods, and apparatuses for performing a NAS procedure based on satellite operating mode. In some aspects, a UE refrains from performing a NAS procedure when the UE is camping on a cell of a satellite that is operating in the S&F mode. Examples of “refraining” from performing the NAS procedure can include pausing, suspending, canceling, withdrawing, or otherwise preventing the NAS procedure from proceeding. The UE can perform the NAS procedure after the satellite transitions to the normal mode. Examples of “performing” the NAS procedure includes resuming a paused / suspended NAS procedure, restarting a NAS procedure, or initiating a new instance of the NAS procedure. “Initiating” a NAS procedure can also be referred to as triggering a NAS operation of a NAS layer of the UE. For example, a UE can initiate a NAS Attach procedure as part of a UE booting / startup procedure, triggered by a NAS operation, or triggered by an upper layer of the UE. The phrase “initiating a NAS procedure” refers to a determination to begin the NAS procedure before actually transmitting a NAS message for the NAS procedure, and the phrase “performing the NAS procedure” refers to communication of NAS message(s) for the NAS procedure.

[0047] In accordance with aspects of this disclosure, the satellite can transmit system information that indicates the present operating mode of the satellite and timing information to indicate when the satellite will transition from the S&F mode to the normal mode and / or from the normal mode to the S&F mode. For example, the satellite can transmit a system information block (SIB) type 31 (SIB31) that includes at least one transition time parameter to inform the UE when the satellite will transition from one operating mode to the other operating mode. The UE can manage when to perform (or refrain from performing) the NAS procedure based on the operating mode of the satellite and transition time.Docket No. 14730932100PCT

[0048] The S&F mode may be useful for some NAS messages, such as user plane packet data. However, some types of NAS procedures might require the satellite to communicate with the core network. Examples of such NAS procedures include a NAS attach procedure, a service request procedure, a tracking area update (TAU) procedure, or a detach procedure, among other examples. When the satellite is operating in the S&F mode, the NAS procedures may fail because the satellite cannot presently communicate with the core network. In some implementations, the satellite can communicate an S&F wait duration when rejecting the NAS procedure. However, the transmission of further NAS messages after a failed NAS procedure can consume power and radio resources that could be preserved using the techniques of this disclosure.

[0049] A satellite that implements S&F operation can transmit system information to indicate whether the satellite is operating in S&F mode or normal mode. In a traditional implementation, the system information is used by a radio resource control (RRC) layer of a UE to control access stratum (AS) communication with the satellite. In some implementations, the system information can include at least one transition time indicating when the satellite will transition between modes. For example, the transition time may be a coordinated universal time (UTC) value based on ephemeris information of the satellite in relation to an NTN gateway. Recently, the 3GPP has suggested that a satellite can implement some NAS capability, such as using an on-board MME. Absent the techniques of this disclosure, the UE might repeatedly attempt a NAS procedure when the system information indicates the satellite is operating in the S&F mode. There is ambiguity whether (or when) the UE should reinitiate a NAS procedure based on the satellite's S&F operation.

[0050] In some aspects, a UE can determine an earliest timing for performing a NAS procedure based on when the satellite will transition from the S&F mode to the normal mode. The UE can refrain from attempting to perform the NAS procedure during a time period when the satellite is operating in the S&F mode since the NAS procedure is expected to fail when the satellite does not have a feeder link to the core network. The UE can postpone the NAS procedure until the transition time when the satellite transitions from the S&F mode to the normal mode.

[0051] In some aspects, a UE can determine a remaining time for the satellite to operate in the normal mode before the satellite will transition to the S&F mode based on the timing information obtained from the system information. The UE can postpone the NAS procedure if the remaining time (7i) is less than a threshold amount of time (Tthresh). For example, a NAS attach procedure may be associated with a predefined or configurable threshold amount of time (Tthresh = TATTACH).Docket No. 14730932100PCTIn some implementations, the threshold amount of time is the amount of time expected to complete the NAS procedure. In some implementations, the threshold amount of time is the amount of time required for an uplink NAS message to arrive at the core network. In some implementations, the threshold amount of time is configured by an MME via a dedicated NAS message. In some implementations, when the UE is camped on a cell of a satellite that will transition to the S&F mode before the T ATTACH, the UE postpones the NAS attach procedure until the next opportunity for the satellite (or another satellite) to operate in the normal mode.

[0052] This disclosure includes several example scenarios for the UE to coordinate timing of a NAS procedure based on the satellite operating mode and transition time. Some examples include a NAS timer that the UE can use to refrain from performing the NAS procedure. In some implementations, the NAS timer is a new timer for the techniques of this disclosure. Alternatively, or additionally, the UE can repurpose an existing NAS timer (e.g., the timer T3451). For example, the UE can set, expire, or restart the timer T3451 to a duration that is based on the difference between a current time and a transition time from S&F mode to normal mode.

[0053] When a UE performs a cell reselection to a new satellite, the new satellite might have an available feeder link or a different transition time between the S&F mode and the normal mode. In some implementations, the UE can adjust timing of the NAS procedure (e.g., earlier or later) based on the current operating mode of the new satellite and / or the transition timing information of the new satellite. For example, if the UE has a running timer T3451 based on a failed NAS procedure attempted with a first satellite, the UE can expire or cancel the timer T3451 when the UE camps on a second cell (e.g., of a second satellite) that is operating in the normal mode. Alternatively, when the UE camps on a second cell (e.g., of a second satellite) operating in the S&F mode, the UE can adjust or extend the timer T3451 duration based on the transition time when the second satellite will transition to the normal mode.

[0054] Particular implementations of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. A UE can save power and radio resources by preventing communication of NAS messages for a NAS procedure that will predictably fail due to the satellite operating in S&F mode. A UE can also save power by postponing a NAS procedure until the satellite transitions to the normal mode. By performing the NAS procedure when the satellite is in the normal mode, and refraining from performing the NAS procedure when the satellite is in the S&F mode, the UE can improve chances ofDocket No. 14730932100PCTsuccessfully completing the NAS procedure, resulting in more efficient use of RAN resources. The techniques of this disclosure may remove ambiguity regarding how the UE should implement a satellite transition time (for various operating modes) at the NAS layer of the UE. When the NAS layer of the UE receives a command from an upper layer of the UE to initiate a NAS procedure, the NAS layer of the UE can refrain from or postpone the NAS procedure until the UE is camping on a cell of a satellite operating in normal mode, thereby improving user experience and connectivity.

[0055] Several examples of this disclosure refer to a NAS attach procedure as an example NAS procedure. However, the disclosed techniques can be applied to other NAS procedures. In some implementations, the UE uses the features of this disclosure when the NAS procedure is one of a first type of NAS procedures that require access to the core network, such as a NAS Attach procedure, a tracking area update (TAU) procedure, a service request procedure, or a detach procedure. The examples of this disclosure refer to a satellite operating in the S&F mode or the normal mode. This disclosure is applicable to other types of NTN nodes and the term “satellite” is used for brevity. Similarly, while some examples refer to a satellite operating in S&F mode, it should be apparent that the satellite might operate multiple cells.

[0056] In the examples of this disclosure, a time period that uses upper case “7” refers to an amount of time, such as a time span, duration, remaining time, time threshold period / value, interval, timer value, etc. Time instances referred to by lower case “7” can refer to an absolute time (e.g., UTC time, or a System Frame Number (SFN) plus a sub-frame index). For example, the current time (e.g., t) and a transition time (e.g., ti) can refer to a UTC time. Although the various examples throughout this disclosure refer to system information including a transition time (e.g., / ?, / ?, etc.) in absolute time, it should be understood that transition time can alternatively be indicated by relative time. For example, a transition time can refer to a time duration (in the units of system frames, subframes, slots, milliseconds, seconds, minutes, or hours) instead of an absolute time instance. The UE can calculate the absolute transition time using the current time ( / ) and the time duration for a relative time.

[0057] FIG. 1 shows an example wireless communication system 100 in which a UE 102 communicates via an NTN having one or more satellites. An NTN extends or augments the service capability of a wireless communication system. An NTN refers to a network, or segment of a network, using RF resources on board an NTN node (such as a spaceborne vehicle or an airborne vehicle). Airborne vehicles can include unmanned aircraft systems (UAS), High-Docket No. 14730932100PCTAltitude Platform Systems (HAPS), balloons, dirigibles, winged vehicles such as airplane or drones, among other examples. Spaceborne vehicles can include a Geostationary Earth Orbit (GEO) satellite (sometimes also referred to as a geosynchronous orbit (GSO) satellite), a Low Earth Orbit (LEO) satellite, a Medium Earth Orbit (MEO) satellite, or a Highly Elliptical Orbit (HEO) satellite, among other examples. An NTN node can belong to one of several types based on altitude, orbit, and beam footprint size. An NTN can also include inter-satellite links (ISLs), such as when multiple NTN nodes form constellations and communicate directly between the NTN nodes.

[0058] FIG. 1 shows an NTN node 111 as a first satellite 112. The NTN node 111 also includes at least part of a first BS 114 and a first MME-onboard 118 that are carried in the first satellite 112. For brevity, references to the NTN node 111 or the first satellite 112 can interchangeably refer to the satellite itself as well as all onboard features of the first satellite 112. A first satellite 112 can support a transparent or a regenerative (with on board processing for an integrated or distributed base station) payload, and typically generates several beams for a given service area bounded by the satellite’s field of view. For a transparent payload implementation, a first satellite 112 can apply RF filtering and frequency conversion and amplification, and not change the waveform signal provided by a ground BS 134 (sometimes also referred to as an NTN BS). For a regenerative payload implementation (such as shown in FIG. 1), a first satellite 112 can apply RF filtering, frequency conversion and amplification, demodulation and decoding, routing, and coding / modulation. In FIG. 1, the NTN node 111 (e.g., first satellite 112) can perform some or all functions of a base station (shown as first BS 114) such as managing an RRC protocol as well as some or all features of an MME (shown as first MME-onboard 118).

[0059] An NTN gateway 132 (sometimes also referred to as a “sat-gateway” or “GW”) communicatively couples the first satellite 112 to ground components of the example wireless communication system 100 (such as ground BS 134 (when present), a core network (CN) 131, or other data network resources). In this disclosure, the term first BS 114 can refer to either or both of the ground BS 134 on the ground (when present), a portion of a distributed BS (e.g., a Central Unit or a Distributed Unit), or the first BS 114 (when onboard the first satellite 112). In the example of FIG. 1, the first satellite 112, the NTN gateway 132, and the first BS 114 form part of a RAN (sometimes referred to as an NTN RAN). In some implementations, the radio access technology for the NTN RAN is based on 5G NR. Alternatively, the radio access technology for the NTN RAN can use an Evolved Universal Terrestrial Radio Access (E-UTRA) air interfaceDocket No. 14730932100PCTfor 4G LTE, or another radio access technology such as Narrowband Internet-of-Things (NB-loT), among other examples. Any number of RANs can be communicatively coupled to the CN 131 . The CN 131 can be implemented as an evolved packet core (EPC), a 5G core (5GC), or a 6G core.

[0060] When the UE 102 is in-coverage (e.g., within a coverage area) of the first satellite 112, the UE 102 can establish a radio connection to the first satellite 112 via an NTN cell 117. The NTN cell 117 refers to a coverage area in which the first satellite 112 operates as part of a radio network. The radio network can be associated with a footprint on the surface of the Earth or could be deployed in air, space, a spaceship, or other planetary objects. The radio connection between the UE 102 and the first satellite 112 is referred to as a service link. When the UE 102 and the first BS 114 have established the service link 113A, the UE 102 is said to be in an RRC connected (RRC CONNECTED) state. After the UE 102 is in the RRC CONNECTED state, the UE 102 might send a network registration request or other uplink NAS messages to the CN 131 (or the first MME-onboard 118) via the NTN node 111. When the feeder link 115A that communicatively couples the first satellite 112 to the NTN gateway 132 is available, the first satellite 112 communicates the network registration request or other NAS messages to the CN 131 via the feeder link 115A. The CN 131 determines whether to accept or reject the network registration based on user subscription information. Depending on where the UE 102 is located or what RAN is being accessed, the CN 131 might accept or reject the network registration request. After registering with the CN 131, the UE 102 can release or suspend the radio connection (e.g., service link 113 A). An RRC idle (RRC IDLE) state refers to a state where the radio connection is released. An RRC inactive (RRC INACTIVE) state refers to a state where the radio connection remains configured but is suspended.

[0061] During normal operation (sometimes referred to as a default mode), the first satellite 112 is concurrently connected to the UE 102 (via a service link) and to the CN 131 (via a feeder link and the NTN gateway 132). In the normal operation, the signaling and data exchange between a UE 102 with satellite access and the CN 131 includes both the service link and the feeder link both being available such that the UE 102 has an end-to-end path to the CN 131. However, there may be some times when one of the links becomes unavailable. For example, when the first satellite 112 is in a first position 119A, the first satellite 112 might have a service link 113A to the UE 102 but no feeder link 115A to the NTN gateway 132. As an example, the first position 119A might be over a remote area, such as the middle of an ocean, a sparselyDocket No. 14730932100PCTpopulated area, or any location in which the first satellite 112 cannot directly communicate with the NTN gateway 132. In another position (referred to as a second position 119B), the first satellite 112 might have a feeder link 115B to the NTN gateway 132 but no service link 113B to the UE 102. For example, the UE 102 might remain located at a remote area while the first satellite 112 has moved to the second position 119B where the first satellite 112 can establish the feeder link 115B to the NTN gateway 132.

[0062] In some instances, even if a UE is in the coverage area of a satellite (such as a non-geostationary (NGSO) satellite), the satellite may be unable to directly connect the UE to services of the core network due to an unavailable feeder link. RRC and NAS procedures have traditionally been designed for terrestrial network (TN) connectivity where presence of AS and NAS connection options might be consistent. The UE and the satellite would unnecessarily consume radio resources and power if they restart RRC and NAS procedures each time service and feeder link continuity is restored. To enable intermittent feeder / service link connectivity, the 3 GPP has introduced a store and forward (S&F) mode. The S&F mode can provide some level of service (in storing and forwarding the data) when end-to-end connectivity is intermittently / temporarily unavailable. The S&F mode is particularly suitable for delay-tolerant loT services via an NGSO space segment. For example, a service provider offers a service of remote monitoring of fields by deploying and tracking many battery-powered loT type UEs across the globe. The loT remote monitoring UEs can include a modem that is able to access the satellite network. In some implementations, the S&F operation enables delay-tolerant, non-real-time NTN services to be offered in areas visited by a satellite having intermittent access to an NTN gateway infrastructure. The S&F mode can support discontinuous coverage, cost-effective deployment of loT NTN services and rapid deployment options. In some implementations, the S&F operation enables a service provider to deploy wireless coverage using sparse LEO constellations and reduced ground segment infrastructure. It is expected that the S&F operation can support NTN solutions on par with other non-3GPP solutions intended for massive satellite loT.

[0063] During S&F mode, end-to-end exchange of signaling / data (such as NAS message) is not achieved by concurrently available service link and feeder link. Rather, the exchange of signaling / data is achieved in multiple steps, such as a first step at the first position 119A and a second step at the second position 119B. In some deployments, the CN 131 can provide downlink signal / data to another satellite (such as the second satellite 122 shown in FIG. 1) instead of (orDocket No. 14730932100PCTin addition to) the first satellite 112. The second satellite 122 might move to a position that will provide a service link 123 to the UE 102 earlier than the first satellite 112 moving back to the first position 119A. The second satellite 122 can also include onboard components, such as a second BS 124 and a second MME-onboard 128, collectively referred to as the second satellite 122 or a second NTN node 121. The CN 131 can provide downlink (DL) NAS messages to the second satellite 122 via a feeder link 125 from the NTN gateway 132 (or another NTN gateway, not shown) to the second satellite 122. Alternatively, or additionally, the second satellite 122 and the first satellite 112 can coordinate S&F operation (such as UE context, NAS messaging, MME-onboard data) via an inter-satellite link (shown as ISL 129). The first MME-onboard 118, the second MME-onboard 128, and the MME-ground 138 can collectively form an MME-group. In some implementations, the MME-ground and several satellites with MME-onboard features can be grouped together to offer a complete MME functionality that is able to share and manage the UE context. From the perspective of the NAS layer in the UE 102, the MME-group may appear to behave as a single MME performing all the functions of an MME that would normally be present only in the CN 131.

[0064] In accordance with aspects of this disclosure, the UE 102 can receive system information (e.g., a SIB31) indicating the transition time (e.g., / ;) for an NTN node to transition from S&F mode to normal mode, or transition from the normal mode to the S&F mode. For example, the UE 102 can receive system information 105 from the first satellite 112 (at the first position 119A) indicating that the NTN cell 117 is operating in the S&F mode and indicating a transition time ti (e.g., a UTC time value) when the NTN cell 117 will transition to the normal mode. Shown at block 107, the UE 102 can refrain from performing a NAS procedure when the NTN cell 117 is operating in the S&F mode. As the first satellite 112 moves from the first position 119A towards the second position 119B there is a position 126 where the satellite can operate in the normal mode because the feeder link 115B becomes available at time ti. The transition time ti is predictable based on ephemeris data of the satellite, location of the NTN gateway 132, movement directi on / speed of the satellite, and / or other factors. When the satellite is at the position 126, the UE 102 might still have a service link 113A with the satellite. The UE 102 performs the NAS procedure (shown at block 109) when the satellite is in normal mode. Using the techniques of this disclosure, the UE 102 can coordinate when to perform the NAS procedure based on the transition time ti that the UE 102 receives ( 105) in system information. In some implementations, the UE 102 receives the system information for the first satellite 112 via the NTN cell 117.Docket No. 14730932100PCTAlternatively, or additionally, the UE 102 might receive system information for the first satellite 112 via another NTN cell or another satellite.

[0065] FIG. 2A illustrates an example of an S&F mode in contrast to a normal mode. In the examples shown in FIG. 2A, an example wireless communication system operates in a normal mode 200 A of signaling and data exchange between a UE 102 with satellite access and the remote data network. In the normal / default mode shown in FIG. 2A, signaling and data exchange between a UE 102 with satellite access and the remote data network (via CN 131) uses both the service and feeder links, perhaps simultaneously. When both the service link and feeder link are available, the UE 102 interacts over the service link with the first satellite 112 and there is a continuous end-to-end connectivity path between the UE 102 and the CN 131 via the service link and the feeder link.

[0066] In the example shown in FIG. 2A, example wireless communication system operates in an S&F mode 200B. In the S&F mode, the end-to-end exchange of signaling / data between a UE 102 with satellite access and the remote data network is not achieved as a single atomic communication, but is instead achieved in a two-step procedure, referred to as “step A” and “step B.” In step A, the UE 102 and the satellite 112 exchange control signaling and / or data, where the satellite 112 does not have a feeder link to the NTN gateway 132. For example, in step A, the satellite 112 can operate the service link with the UE 102 and does not have an active feeder link connection with the NTN gateway 132. In step B, when the satellite 112 is closer to the NTN gateway 132 (and is further away from UE 102), the connection between the satellite 112 and the feeder link between NTN gateway 132 can be established. In step B, the uplink data / signal stored on the satellite 112 (from step A) can now be forwarded to the CN 131 via the NTN gateway 132. In step B, the satellite 112 can store downlink control signaling and / or data for the UE 102. In this situation, the stored downlink data / signal can be forwarded to the UE 102 later when the satellite 112 is once again able to communicate with the UE 102 (e.g., the satellite 112 travels a complete orbit around the Earth and is back to the same position again as in step A).

[0067] The S&F mode is useful for buffing user data. However, some NAS procedures might fail when the UE transmits NAS messages to a satellite operating in the S&F mode. The techniques of this disclosure provide a potential technical advantage of coordinating NAS procedures based on the operating mode and transition time(s) as the satellite transitions between the normal mode and the S&F mode.Docket No. 14730932100PCT

[0068] FIG. 2B shows an example wireless communication system 201 in which a satellite includes onboard NAS features. In the example of FIG. 2B, first satellite 112 includes an NTN BS (shown as first BS 114) implementing a regenerative payload. A satellite implementing with an NTN BS implementing a regenerative payload is sometimes referred to as a “regenerative satellite.” The first BS 114 can perform some or all of the functions of a base station, including those described with reference to first BS 114 or ground BS 134 in this disclosure. The service link enables a Uu interface between the UE 102 and the first BS 114. In the example of FIG. 2B, the feeder link from the first BS 114 to the NTN gateway 132 can be referred to as the satellite radio interface (SRI). In this example, the SRI is a transport link between the NTN gateway 132 and the first satellite 112 that carries traffic for the Ng interface (or SI interface, when part of the first BS 114 is implemented in a ground unit) interface. The NTN gateway 132 at one end of the SRI serves as an intermediate node forwarding the Sl / Ng traffic to and from the data network 230 via CN 131. The Ng interface from the first BS 114 includes a portion over the SRI (referred to as “Ng over SRI”) and a portion on the ground. The first MME-onboard 118 can implement at least part of a NAS protocol for mobility, user subscription and / or access to the data network 230, in coordination with an MME-ground (not shown).

[0069] In some implementations, a first portion of the base station functionality (shown as first BS 114) can be implemented on the first satellite 112 while a second portion of the base station functionality can be implemented at a ground entity (e.g., FIG. 1, ground BS 134). For example, in a disaggregated network, first BS 114 can be divided into two components: the Distributed Unit (DU) and Centralized Unit (CU). In an example, the first BS 114 can operate as a DU that handles baseband processing, including RF signal processing and modulation / demodulation. The ground BS 134 can be an example CU that manages higher-layer tasks such as resource management, scheduling, and network optimization.

[0070] In some examples of the regenerative satellite payload architecture shown in FIG. 2B, part of the MME (e.g., MME-onboard 118) in a split-MME architecture or the entire MME is installed on the “regenerative” satellite (e.g., satellite 112). In such examples, the feeder link does not carry either the SI interface or the NG interface. Instead, the feeder link carries the internal interface within a core network node (e.g., CN 131). Different regenerative satellites can connect to the same CN 131 on the ground, via the same NTN gateway (e.g., NTN gateway 132), or via different NTN gateways.Docket No. 14730932100PCT

[0071] In some aspects, the UE 102 compensates for time and frequency drift while transmitting control signals and / or data to a moving satellite using its global navigations satellite system (GNSS) position. The UE 102 may obtain its GNSS position via a signal obtained or measured from at least one GNSS satellite 212.

[0072] Although examples of this disclosure are based on the regenerative payload architecture illustrated in FIG. 2B, the techniques of this disclosure can apply to a transparent payload architecture as well, particularly where the transparent first satellite 112 includes some subset or limited features for S&F operation (such as a capability to maintain coordinated states of RRC and NAS protocols).

[0073] The NTN can support different types of service links, depending on the satellite moving pattern. In some examples, there are three types of service links that are supported in an NTN:• Earth-fixed: provisioned by beam(s) continuously covering the same geographical areas all the time (e.g., the case of Geostationary Earth Orbit or Geosynchronous Orbit (GEO / GSO) satellites)• Quasi-Earth-fixed: provisioned by beam(s) covering one geographic area for a limited period and a different geographic area during another period (e.g., the case of Low Earth Orbit or Medium Earth Orbit (LEO / MEO) satellites capable of using steerable beams), or • Earth-moving: provisioned by beam(s) whose coverage area slides over the Earth surface (e.g., the case of LEO / MEO satellites using fixed or non-steerable beams).

[0074] With respect to LEO / MEO satellites, the first BS 114 can provide either quasi-Earth-fixed cell coverage or Earth-moving cell coverage. With respect to GEO satellites, the first BS 114 can provide Earth fixed cell coverage.

[0075] FIG. 3 shows an example split MME deployment 300. The example shown in FIG. 3 includes the UE 102, two NTN nodes 111 and 121, and the CN 131. NTN node 111, NTN node 121, and an CN 131. In the example shown in FIG. 3, the UE 102 communicates with a first satellite (e.g., first satellite 112) that is moving away from the UE 102, and a second satellite (e.g., second satellite 122) that is moving toward the UE 102. The first satellite 112 implements the first BS 114 and the first MME-onboard 118. The second satellite 122 implements the second BS 124 and the second MME-onboard 128. The CN 131 implements MME-ground 138. Collectively, the first MME-onboard 118, the second MME-onboard 128, and the MME-ground 138 can be referred to as an MME 338. The UE 102 can communicate with the MME 338 (i.e., any of the first MME-onboard 118, the second MME-onboard 128, or the MME-ground 138)Docket No. 14730932100PCTusing NAS messages that would traditionally be communicated between the UE 102 and MME of a core network.

[0076] The UE 102 includes a physical (PHY) layer 302, an RRC layer 304, and a NAS layer 309. The NAS layer 309 coordinates NAS protocol messaging with the MME 338 via an N1 interface. The Uu interface refers to the RRC layer protocol between the RRC layer 304 of the UE and a BS (such as the first BS 114 or the second BS 124). The N1 interface and the Uu interface are illustrated as separate connections for reference. However, the N1 interface typically is carried by the Uu interface, which in turn is carried over a PHY layer connection between the UE 102 and the first satellite 112 (or the second satellite 122).

[0077] The MME 338 is split into two functions, MME-onboard and MME-ground. MME-onboard includes the MME portions that are onboard the first satellite 112 and the second satellite 122 (e.g., the first MME-onboard 118 and the second MME-onboard 128, respectively). In some examples, an MME-onboard communicates with its respective BS via and SI -MME interface.

[0078] MME-ground is part of the MME 338 that is implemented on the ground network (e.g., MME-ground 138). MME-ground handles interfaces towards various CN functions. Examples of such interfaces and CN functions include the S6a interface towards the home subscriber system (HSS), SGd interface towards short message service-gateway mobile switching center (SMS-GMSC), interworking mobile switching center (IWMSC), and / or SMS Router, T6a interface towards service capability exposure function (SCEF), T6ai interface towards interworking function-SCEF (IWF-SCEF), and / or Sil interface towards servicing gateway (SGW) among others. In some implementations, one MME-ground 138 instance can be associated with one or multiple MME-onboard instances. In some implementations, an MME group includes at least one MME-onboard that is in charge of handling the SI interface with the onboard enhanced or next generation NodeB base station (eNB or gNB) and at least one MME-ground that is in charge of handling the rest of interfaces towards other CN functions.

[0079] The MME-ground (e.g., MME-ground 138) together with the set of MME-onboard instances (e.g., first MME-onboard 118 and second MME-onboard 128) deployed in the set of satellites can behave jointly as a single MME entity (e.g., MME 338). The UE context is synchronized between MME-ground and MME-onboard.

[0080] When the UE 102 communicates an uplink (UL) NAS message that needs an interaction with a core network node on the ground, the MME-onboard (e.g., the first MME-onboard 118 and / or the second MME-onboard 128) can store the UL NAS message if the feeder link is notDocket No. 14730932100PCTavailable and later synchronizes with the MME-ground (e.g., MME-ground 138) when the feeder link becomes available. The MME-ground executes the procedure with the ground network nodes and synchronizes the UE context with the MME-onboard when the feeder link becomes available. A DL NAS message can be stored in the MME-ground when the feeder link is unavailable and transferred to the MME-onboard (e.g., first MME-onboard 118 and / or second MME-onboard 128) when the feeder link for either satellite becomes available. The MME-ground can determine the satellite that will serve the UE 102 next and send the DL NAS message to the corresponding MME-onboard. As noted above, in the example of FIG. 3 the first satellite 112 is moving away from the UE 102 and the second satellite 122 is moving towards the UE 102. The MME-ground 138 can determine that the second satellite 122 will serve the UE 102 next. The MME-ground 138 can send the DL NAS message to the second MME-onboard 128 when the feeder link to the second satellite 122 is available. If the service link to the UE 102 is unavailable, the second MME-onboard 128 can store the DL NAS message for transfer to the UE 102 when the service link becomes available.

[0081] The techniques of this disclosure may be applicable to both the “Split-MME” and “Full-MME” architectures. In the “Split-MME” architecture (such as shown in FIG. 3), the MME-onboard coordinates with an MME-ground. In the “Full-MME” architecture, the MME-onboard coordinates with other core network components (such as an HSS, SGW, etc.) for subscription information, security context, etc.

[0082] Although this disclosure refers to “MME,” the descriptions of MME can also refer to an Access and Mobility Management Function (AMF) or future network entities that perform some NAS functionality. For example, “MME” can be replaced by AMF or evolved AMF or 6G AMF. The MME or AMF onboard a satellite might communicate with ground network components, such as the HSS, SGW, Authentication Server Function (AUSF), Policy Control Function (PCF), Unified Data Management (UDM), or Session Management Function (SMF).

[0083] In some situations, an MME on a satellite cannot store UL NAS message for a NAS procedure (such as the NAS Attach procedure, a service request, or a TAU procedure) or the MME may require access to a core network function. In such cases, the MME may reject the NAS procedure. For example, the MME on a satellite can reject the NAS procedure if the MME does not have a security context, authentication data, subscription information, or other parameters for the UE 102.Docket No. 14730932100PCT

[0084] FIG. 4 shows a message diagram 400 in which a NAS procedure is rejected with a S&F wait time duration (Ti). When a UE 102 initiates an NAS procedure with an MME onboard the satellite that has no feeder link (i.e., operating in the S&F mode), the MME can reject the NAS procedure, such as when the MME does not have UE security context or when the MME needs to retrieve UE-specific authentication vectors or subscription information from the ground network. The 3 GPP has introduced an S&F wait time duration based on an access control mechanism to prevent the UE 102 from reattempting the same NAS procedure or attempting other NAS procedures that are likely to be rejected. The satellite 112 can include an S&F wait time duration (e.g., Ti) in aDLNAS message to reject NAS procedure. FIG. 4 shows an example scenario using the S&F wait time duration.

[0085] In the example message diagram 400, a UE 102 is operating in the RRC_IDLE state 402 and camping on a cell provided by an NTN node 111 (e.g., satellite 112). The satellite 112 includes a BS 114 and MME-onboard 118. As a part of the UE booting procedure or triggered by upper layers of the UE 102, the UE 102 initiates 406 a NAS Attach procedure. In the example of FIG. 4, the UE 102 attempts to perform the NAS attach procedure while the UE is not aware the satellite 112 is operating in the S&F mode 404. The UE 102 triggers the UE RRC to perform an RRC connection establishment procedure (shown as block 410) with the BS 114 onboard the satellite 112. In the S&F mode 404, the satellite 112 does not have a feeder link available when the UE 102 attempts to perform the NAS Attach procedure. After the UE RRC enters a connected state 412 following the RRC connection establishment procedure, the UE 102 transmits a NAS Attach Request message 414 to the MME 118 onboard the satellite 112.

[0086] The MME 118 is unable to accept the NAS Attach Request message 414 because the satellite 112 is operating in the S&F mode 404 and the MME 118 cannot reach the ground network. The MME 118 responds with a NAS Attach Reject message 416 that includes a S&F wait time duration (e.g., Ti) parameter. For example, the S&F wait time duration indicates an amount of time that the UE 102 needs to wait before the feeder link becomes available. The UE 102 starts 420 a timer T3451 with a duration set to the S&F wait time duration (e.g., Ti). In some implementations, the timer T3451 is a countdown timer with a timer value based on the S&F wait time duration. While the timer T3451 is running, the UE 102 refrains from transmitting NAS messages. In some implementations, the UE 102 enters the RRC_IDLE state 422, such as when the UE 102 receives an RRC Connection Release message (not shown) from the BS 114 or when a data inactivity timer of the UE 102 expires.Docket No. 14730932100PCT

[0087] In FIG. 4, after expiration 424 of the timer T3451, the UE 102 initiates another NAS attach procedure 428. For example, the UE 102 might reattempt the same NAS attach procedure that was previously rejected due to the unavailability of the feeder link at the satellite 112. The UE 102 sends a NAS Attach Request message 434 to the MME 118. This time the satellite 112 is operating in the normal mode 426 because the satellite 112 has a feeder link to the ground network (not shown). The MME 118 onboard the satellite 112 responds with a NAS Attach Accept message 436 to successfully accept the NAS Attach procedure. Note that prior to transmitting the NAS Attach Request message 436, if the UE 102 is in the RRC IDLE state, the UE 102 may first need to perform an RRC connection establishment procedure 430 with the BS 114 to enter the RRC CONNECTED state 432.

[0088] The example technique illustrated in FIG. 4 shows the UE 102 performing the NAS procedure at least once to enable the UE 102 to obtain the S&F wait time duration Ti. Absent the techniques of this disclosure, the UE 102 and the satellite 112 expend power / radio resources for communication of the NAS messages 414, 416 of a NAS procedure that fails due to the satellite 112 operating in the S&F mode 404. The techniques of this disclosure enable the UE 102 to obtain the S&F transition time of a serving satellite based on system information. A potential technical advantage of the disclosed technique is that the UE 102 can prevent the transmission of NAS messages for a NAS procedure that will likely fail when the serving satellite is operating in the S&F mode.

[0089] FIG. 5A shows a system diagram 500A in which a satellite 112 indicates a transition time from S&F mode to normal mode. The satellite 112 can indicate the transition time (U) at which the satellite 112 will transition from the S&F mode to the normal mode in the system information (e.g., SIB31). The UE 102 receiving the system information including the transition time (ti) can refrain from performing the NAS procedure until the normal mode (e.g., at transition time ( / ;)). Compared to FIG. 4, the UE 102 in FIG. 5 A does not need to transmit the first NAS request message and hence is more power-efficient.

[0090] FIG. 5B shows a system diagram 500B in which system information (e.g., SIB31) indicates a transition time from normal mode to S&F mode. In the example of FIG. 5B, a satellite 112 is moving away from an NTN gateway 132 and will lose the feeder link 515B at some time (e.g., U) in the future. The satellite 112 can indicate the time (e.g., I2) at which the satellite 112 will transition from the normal mode to the S&F mode in the system information (e.g., SIB31). The UE 102 receiving the system information can decide not to initiate a NAS procedure if theDocket No. 14730932100PCTremaining time period (Tr) of feeder link continuity is insufficient to complete the NAS procedure. For example, the remaining time period (Tr) may be the difference between the current time ( / ) and the transition time ( / ?). The UE 102 can compare the 7 to a threshold time period (Thresh). In some implementations, the UE 102 AS layer might reselect to another cell (of the satellite 112 or another satellite, not shown) having a longer remaining time period for feeder link continuity (e.g., a later transition time / ?). This disclosure describes the handling in the UE NAS layer upon receiving the S&F mode transition time from the RRC layer, and also the UE handling at the situation when both the S&F wait time (obtained from the dedicated NAS response message) and the S&F mode transition time (obtained from the system information) are both available at the UE NAS layer.

[0091] Next, several example scenarios are discussed with reference to FIG. 6 through FIG. 10 in which a UE and / or a network node perform the techniques of this disclosure for controlling the performance (or refraining from performance) of a NAS procedure. Generally speaking, similar events in the drawings are labeled with reference numbers that have the same lower-order digits. For example, event 605 is similar to events 105, 705, 805-1, 805-2, etc. Event 607 is similar to events 107, 707A, 707B, 707C, 807-1, 807-2, etc. For brevity, similar events are not discussed in detail in each instance, but the discussion of a certain event with reference to one of the figures also applies to similar events in other figures.

[0092] FIG. 6 shows a message diagram 600 in which a UE 102 manages a NAS procedure based on the satellite 112 indicating a transition time (O) from S&F mode 404 to a normal mode 426. The satellite 112 transmits, and the UE 102 receives, system information 605 (e.g., SIB31) that indicates the transition time ( / ;) of a future time when the satellite 112 will transition from S&F mode 404 to a normal mode 426. For example, the transition time (O) can be a future time in UTC time format. In some implementations, the satellite 112 calculates the transition time (Z7) based on satellite ephemeris data, location of the NTN gateway, feeder link signal quality, or other parameters.

[0093] The UE 102 initiates 606 a NAS procedure. For example, an upper layer of the UE 102 can communicate a command to the NAS layer of the UE 102. Alternatively, the NAS layer of the UE 102 might initiate the NAS procedure based on a UE bootup sequence or other triggering event for NAS control signaling. Rather than transmit a NAS message for the NAS procedure, shown at block 414 in FIG. 4, the UE 102 refrains 607 from performing the NAS procedure while the satellite 112 is operating in the S&F mode. At the transition time (Z7), the satellite 112Docket No. 14730932100PCTtransitions to the normal mode 426 after establishing the feeder link to the NTN gateway (not shown). The UE 102 performs 609 the NAS procedure at (or after) the transition time ( / ;). For example, the UE 102 performs the NAS procedure by establishing an RRC connection (if needed) and transmitting a NAS message to the MME 118. See FIG. 4 elements 430, 432, 434, 436.

[0094] FIG. 7A shows a message diagram 700A of an example scenario in which a UE determines whether and how to pause a NAS Attach procedure based on the system information indicating a transition time from the S&F mode to the normal mode. In this example scenario, the UE 102 is operating in the RRC IDLE state 402 and camping on a cell provided by a satellite 112, where a BS 114 and an MME 118 are onboard the satellite 112. Initially, the satellite 112 is operating in the S&F mode 404 (i.e., the satellite 112 does not have a feeder link available). The UE 102 receives system information 705 indicating the transition time (L) when the satellite 112 will transition from the S&F mode to the normal mode 426.

[0095] In the example scenario of FIG. 7A, as a part of the UE booting procedure or upon being triggered by upper layers, the UE 102 initiates 406 a NAS Attach procedure. Before proceeding with the NAS attach procedure, the UE 102 refrains (shown at bracket 607) from performing the NAS attach procedure. In the example scenario of FIG. 7A, refraining 607 from performing the NAS attach procedure includes the UE 102 pausing or suspending 707A the NAS Attach procedure before the UE 102 transmits a NAS attach request message to the MME 118. In some implementations, the UE 102 determines to pause or suspend the NAS Attach procedure because the UE 102 has been informed (by the system information 705) that the satellite 112 is operating in the S&F mode 404 and will transition to the normal mode 426 at the future transition time (L).

[0096] Later, at the transition time (L), the UE 102 performs the NAS attach procedure (shown at bracket 609). In the example scenario of FIG. 7A, performing the NAS attach procedure (bracket 609) includes the UE 102 resuming 708 the paused / suspended NAS Attach procedure. For example, the UE 102 can perform an RRC connection establishment procedure 430 with the BS 114 onboard the satellite 112. At the end of the RRC connection establishment procedure, the UE 102 enters the RRC_CONNECTED state 432, and transmits a NAS attach request message 434 to the MME 118. In response to the NAS attach request message 434, the MME 118 transmits a NAS attach accept message 436 to the UE 102, assuming the MME 118 is able to accept the NAS attach request based on UE-specific information that the MME 118 obtains from the ground network (e.g., the UE’s security context, the UE’s authentication, and / or the UE subscription information).Docket No. 14730932100PCT

[0097] Although in the example message diagram 700A, a NAS Attach procedure is used to demonstrate the UE operations after receiving the transition time ti indicator from the network, other UE-initiated NAS procedures such as the TAU procedure, the service request procedure, and the detach procedure, can be used to replace the NAS Attach procedure and the UE operations are the same. If the NAS Attach procedure in 700A is replaced by a TAU procedure, the NAS attach request message 434 is replaced by a TAU request message, and the NAS attach accept message 436 is replaced by a TAU accept message. If the NAS Attach procedure in 700A is replaced by a detach procedure, the NAS attach request message 434 is replaced by a detach request message, and the NAS attach accept message 436 is replaced by a detach accept message. If the NAS Attach procedure in 700A is replaced by a service request procedure, the NAS attach request message 434 is replaced by a service request message, and the NAS Attach accept message 436 is replaced by a service accept message.

[0098] FIG. 7B shows a message diagram 700B of an example scenario in which a UE 102 determines whether to cancel a NAS Attach procedure based on the system information indicating a transition time from the S&F mode to the normal mode. The message diagram in FIG. 7B is similar to FIG. 7A, with the differences discussed below. Rather than pausing / resuming (e.g., blocks 707A and 708) the NAS procedure as described in FIG. 7A, FIG.7B shows the UE 102 cancels or withdraws 707B the NAS Attach procedure. In the example scenario of FIG. 7A, refraining 607 from performing the NAS attach procedure includes the UE 102 canceling or withdrawing the NAS attach procedure. In the example scenario of FIG. 7B, performing 609 the NAS attach procedure includes the UE 102 reinitiating the NAS attach procedure or initiating a new instance of the NAS attach procedure 428. In some implementations, the NAS Attach procedure 428 is triggered by upper layers in the event 609 as a result of the previously triggered NAS Attach procedure 406 being unresolved.

[0099] Although not illustrated in FIG. 7B, it is possible that the UE 102 NAS layer cancels multiple instances of the NAS attach procedure during bracket 607, such as when the UE 102 upper layer(s) serially triggers the multiple instances of the NAS procedure. In some implementations, the upper layer may repeatedly trigger the NAS attach procedure until an instance (such as block 428) occurs at or after the transition time ( / ;).

[0100] FIG. 7C shows a message diagram 700C of an example scenario in which a UE 102 manages a NAS timer (e.g., timer T3451 or a newly-defined timer) based on the system information 705 indicating a transition time (ti) when the satellite 112 will transition from theDocket No. 14730932100PCTS&F mode to the normal mode. The message diagram in FIG. 7C is similar to FIG. 7A, with the differences discussed below. FIG. 7C shows an example scenario where the UE 102 can use a NAS timer to control how long the UE 102 refrains 607 from performing the NAS procedure. In some implementations, the NAS timer is an existing timer (e.g., the timer T3451) as described with reference to FIG. 4 that is repurposed to implement the features of this disclosure.

[0101] After the UE 102 receives system information 705 indicating the transition time ti, the UE 102 can set the NAS timer (e.g., timer T3451) to a duration 77 based on the amount of time from the current time (7) until the transition time ( / ;). The UE 102 starts 707C the NAS timer with the duration Ti. While the NAS timer is running, the UE 102 refrains from performing any NAS procedure. In this example scenario, because the NAS timer is started after receiving the system information, the UE 102 does not perform the NAS Attach procedure 609 until after the expiration of the NAS timer. Although not shown in FIG. 7C, the upper layer of the UE 102 may initiate a NAS procedure while the NAS timer is running, but the NAS layer of the UE 102 may disregard or cancel the NAS procedure while the NAS timer is running. Later, after the expiration 424 of the NAS timer (e.g., T3451), the UE 102 initiates a NAS attach procedure 428 and performs the NAS procedure 609.

[0102] Next, several example scenarios described with reference to FIG. 8 and FIG. 9 deal with how a UE manages performance of a NAS procedure after a cell reselection. Each cell (or each satellite) might have a different timing for transitions from S&F mode to normal mode. Furthermore, the UE may reselect a new cell operating in the normal mode after previously camping on a cell operating in the S&F mode. The example scenarios describe how the UE can update the refraining 607 (such as pausing a NAS procedure or updating a NAS timer) after a cell reselection.

[0103] FIG. 8 shows a message diagram 800 of an example scenario in which a UE 102 manages a NAS procedure based on an operating mode and transition time for a new cell after cell reselection. The example scenario illustrates the UE 102 determining how to pause a NAS Attach procedure after switching to a new cell, based on the system information indicating when the new cell will transition from the S&F mode to the normal mode. Initially, a UE 102 is operating in the RRC IDLE state 402 and camping on a cell provided by a first satellite 112, where a BS 114 and an MME 118 are onboard the satellite 112. In this example scenario, the UE 102 is in a coverage area of a neighbor cell(s) provided by another second satellite 122, on which another BS 124 and MME 128 are on board. Although FIG. 8 shows the second cell beingDocket No. 14730932100PCTprovided by the second satellite 122, in some implementations, the second cell can be another cell / beam of the first satellite 112.

[0104] In the example scenario of FIG. 8, the first satellite 112 is initially operating in the S&F mode 404 (i.e., the satellite 112 does not have a feeder link available) at the time when the UE 102 is initially camping on the cell provided by the first satellite 112. The UE 102 receives system information 805-1 indicating the transition time (i.e., ti) when the first satellite 112 will transition from the S&F mode to the normal mode 426 (i.e., the mode where the satellite 112 has an operational feeder link). The UE 102 initiates 406 a NAS attach procedure, such as a part of the device booting procedure or upon being triggered by upper layers. As described with reference to FIG. 6 and FIG. 7A, the UE 102 refrains 607 from performing the NAS attach procedure by pausing or suspending the NAS attach procedure (shown as block 807-1).

[0105] While the NAS attach procedure is still paused, the UE 102 might perform an intrafrequency or inter-frequency measurement and decide to reselect to a second cell based on the measurement results and cell reselection criteria (e.g., as specified in 3 GPP technical specification (TS) 36.304). Block 840 shows the UE 102 performing the cell reselection. In this scenario, the cell reselection results in selection of a second cell provided by the second satellite 122. After downlink-synchronizing with the target cell of the second satellite 122, the UE 102 receives system information 805-2. The system information 805-2 indicates that the second satellite 122 is also operating in the S&F mode 404 and indicates a transition time (i.e., ) when the second satellite 122 will transition from the S&F mode to the normal mode 826-2 (i.e., when the second satellite 122 will have an available feeder link).

[0106] Based on receiving the second transition time t2, the UE 102 determines to continue pausing / suspending the NAS Attach procedure until the second transition time t2 of the second satellite 122) instead of the first transition time h (of the first satellite 112). Although FIG. 8 shows the second transition time t2 occurs before the first transition time ti, in some implementations, the second transition time t2 is later and the UE 102 extends the timer period for refraining 607 until the second transition time t2. Alternatively, the UE 102 can disregard the first transition time ti since the UE 102 is no longer camping on the first cell of the first satellite 112 and instead the UE 102 can reset the refraining period for bracket 607 based on the second transition time t2. Later, at the second transition time L, the second satellite 122 operates in the normal mode 826-2 and the UE 102 performs the NAS attach procedure 609. For example, the UE 102 can resume 808 the paused / suspended NAS Attach procedure and perform theDocket No. 14730932100PCTprocedures / messages at events 430, 432, 434, and 436 as described with reference to FIG. 4 and FIG. 7A.

[0107] Although FIG. 8 shows the second satellite 122 initially operating in the S&F mode 404 when the UE 102 reselects to the second cell of the second satellite 122, it is also possible that the second satellite 122 is already operating in the normal mode 826-2. The UE 102 might immediately perform the NAS attach procedure after performing the cell reselection if the second satellite 122 is already in the normal mode 826-2. Alternatively, the UE 102 may determine whether to resume the NAS attach procedure based on a remaining time period (7 ) of the normal mode, as further described with reference to FIG. 10.

[0108] In some implementations, a cell reselection procedure 840 can take into account the current operating mode and / or transition time of candidate neighbor cells. For example, the UE 102 can use a cell reselection criterion that prioritizes cell (re)selection to a candidate cell from a satellite operating in the normal mode, having a longer remaining time in the normal mode, or having an earlier time to transition to the normal mode.

[0109] FIG. 9 shows a message diagram 900 of an example scenario in which a UE controls a NAS timer (e.g., timer T3451) based on operating mode and transition time for a new cell after cell reselection. The message diagram in FIG. 9 is similar to that in FIG. 8, with the differences discussed below. In this example scenario, the BS 114 onboard the satellite 112 did not indicate the transition time (L) from the S&F mode 404 to the normal mode in the system information (not shown). Thus, FIG. 9 begins similar to the scenario in FIG. 4 where the UE 102 transmits a NAS attach request message 414 to the MME 118 onboard the satellite 112 and receives a NAS attach reject message 416 indicating an S&F wait time duration. The UE 102 starts 420 the timer T3451 with a duration equal to the S&F wait time duration. The UE 102 refrains from performing any NAS procedure while the timer T3451 is running.

[0110] Later, before the timer T3451 expires, the UE 102 performs a cell reselection 840 to a second cell as a result of intra-frequency or inter-frequency neighbor cell measurements. After downlink-synchronizing with the second cell of the second satellite 122, the UE 102 receives system information 705 indicating the transition time (i.e., ti) from the S&F mode 404 to the normal mode 426. Based on the UE 102 receiving the transition time ti, the UE 102 restarts 921 the timer T3451 with an updated duration Ti that will keep the timer T3451 running until the transition time ti. The updated duration of the timer T3451 causes the UE 102 to refrain from performing any NAS procedure until ti. Later, at the transition time (i.e., L), the timer T3451Docket No. 14730932100PCTexpires 424 and the UE 102 removes the restriction from performing any NAS procedure. The UE 102 then performs a NAS Attach procedure 909 while the second satellite 122 is operating in the normal mode 426 as previously described with reference to FIG. 4 and FIG. 7A elements 430, 432, 434, and 436. In some implementations, the UE 102 resumes or reattempts the NAS procedure begun with the previous NAS attach request message 414. Alternatively, the UE 102 initiates a new instance of the NAS attach procedure.

[0111] FIG. 10 shows a message diagram 1000 of an example scenario in which a UE 102 manages a NAS procedure based on available time to complete the NAS procedure before the satellite transitions to an S&F mode. In some implementations, the UE 102 determines whether to perform a NAS Attach procedure based on the system information indicating when a serving satellite will transition from a normal mode 1003 to an S&F mode 404.

[0112] Initially, a UE 102 is operating in the RRC IDLE state 402 and camping on a cell provided by a satellite 112, where a BS 114 and an MME 118 are onboard the satellite 112. The satellite 112 is operating in the normal mode 1003 (i.e., the satellite 112 has an available feeder link). The UE 102 receives system information 1038 indicating the transition time (i.e., ti) from the normal mode 1003 to the S&F mode 404 (i.e., the mode where the satellite 112 does not have a feeder link). The UE 102 initiates 406 a NAS Attach procedure. Before proceeding with the NAS attach procedure, the UE 102 can determine the remaining time period (71) (e.g., the amount of time from the current time ( / ) to the transition time ( / / )) before the satellite 112 transitions to the S&F mode 404. In the example scenario of FIG. 10, the UE 102 pauses or suspends 1042 the NAS Attach procedure before the UE 102 transmits a NAS attach request message to the MME 118. In some implementations, the UE 102 determines to pause or suspend the NAS Attach procedure when the remaining time period (T) is less than a threshold time period Tthresh, where the value of Tthresh can be a fixed value specified in the 3GPP specifications and pre-coded in the UE, or a configurable value provided by the network via a dedicated message (e.g., RRC or NAS message) or via the system information. In some implementations, the value of Tthresh is the amount of time required for an uplink message to arrive at the core network via the satellite 112. In some implementations, the threshold time period is based on the type of NAS procedure. For example, the threshold time period (Tthresh) can be referred to as a threshold time period TATTACII having a first value for a NAS attach procedure, a threshold time period TTAU having a second value for a TAU procedure, and so on. In some implementations, the value of Tthresh can depend on a radio access technology of the NTN, network congestion, or other considerations.Docket No. 14730932100PCT

[0113] Later, at the first transition time ti, the satellite 112 transitions to the S&F mode 404 (i.e., loses the feeder link) and hence the UE 102 receives another system information 1005 including a value indicating a next transition time (e g., L) when the satellite 112 will transition from the S&F mode 404 to the normal mode 426. Based on the satellite 112 operating in the S&F mode 404, the UE 102 continues pausing / suspending 1007 the NAS Attach procedure until the second transition time t2. Later, at the second transition time L, the satellite 112 transitions again from the S&F mode 404 to the normal mode 426. Meanwhile, also at transition time L, the UE 102 resumes 708 the paused / suspended NAS Attach procedure and performs the procedures / messages at events 430, 432, 434, and 436 as described with reference to FIG. 4 and FIG. 7A.

[0114] In some implementations, instead of pausing or suspending the NAS Attach procedure in the block 1042, the UE 102 cancels or withdraws the NAS Attach procedure. Furthermore, the concepts described with reference to any of FIG. 6 through FIG. 9 can be adapted to the scenario in FIG. 10.

[0115] Next, several example operations are discussed with reference to flow diagrams of FIG.11 through FIG. 19. As with FIG. 6 through FIG. 10, similar events in the drawings are labeled with reference numbers that have the same lower-order digits. For example, block 1105 is similar to events 105, 705, 805-1, 805-2, etc. For brevity, similar events are not discussed in detail in each instance, but the discussion of a certain event with reference to one of the figures also applies to similar events in other figures. Although the flow diagrams depict a particular sequence of operations, the sequence may be altered without departing from the scope of the present disclosure. For example, some of the operations depicted may be performed in parallel or in a different sequence that does not materially affect the function of the routine. In other examples, different components of an example device or system that implements the routine may perform functions at substantially the same time or in a specific sequence.

[0116] FIG. 11 shows a flow diagram 1100 of example operations of a UE managing a NAS procedure based on an indicated time when a cell of a satellite will transition from an S&F mode to a normal mode. FIG. 11 includes operations similar to those described with reference to FIG.6. The UE receives 1105 system information (e g., SIB31) indicating the transition time (e.g., / / ) from the S&F mode to the normal mode. Then, the UE initiates a NAS procedure 1106. When the satellite is operating in S&F mode, the UE refrains 1107 from performing the NASDocket No. 14730932100PCTprocedure. Instead, the UE performs 1109 the NAS procedure at or after the satellite transitions to the normal mode as indicated by the transition time.

[0117] FIG. 12A shows a flow diagram 1200A of example operations of a UE in which the UE determines whether to pause a NAS procedure based on satellite operating mode and transition time. FIG. 12A includes operations similar to those described with reference to FIG. 7A. Initially, the UE operates 1202 in the RRC idle state and camps on a satellite having a BS node (e.g., eNB or gNB) and a full / partial network node (e.g., a full or partial MME) installed on it. As a part of the device booting procedure or upon being triggered by upper layers, the UE initiates 1206 a NAS procedure. The UE determines 1205 whether the UE has received system information indicating the serving cell or satellite is currently operating in the S&F mode and including a transition time ti indicating when the satellite will transition from the S&F mode to the normal mode.

[0118] If the determination 1205 is negative (“NO” branch), the UE performs 1209 the NAS procedure by transmitting the corresponding NAS message to the network. Otherwise, if the determination 1205 is positive (“YES” branch), the flow proceeds to block 1220.

[0119] The UE checks 1220 if the current time ( / ) is less than the indicated transition time ti. If the determination 1220 is positive (“YES” branch), the UE pauses or suspends 1207AtheNAS procedure (before transmitting a corresponding NAS message to the network). In some implementations, the UE determines to pause or suspend the NAS Attach procedure because the UE knows that the satellite is currently operating in the S&F mode and will transition to the normal mode in the near future. After block 1207A, the flow returns to an earlier block (e.g., block 1220). If the determination 1220 is negative (“NO” branch), meaning the current time is later than transition time ti and the transition time ti has already occurred, the UE resumes 1208 the paused / suspended NAS procedure and transmits the corresponding NAS message to the network.

[0120] FIG. 12B shows a flow diagram 1200B of example operations of a UE in which the UE determines whether to cancel a NAS procedure based on the satellite operating mode and transition time. FIG. 12B includes operations similar to those described with reference to FIG.7B. The flow diagram in FIG. 12B is similar to FIG. 12A, with the differences discussed below. If the determination 1220 is positive (“YES” branch), meaning the transition time ti has not yet occurred, the UE cancels or withdraws 1207B the NAS procedure (before transmitting a corresponding NAS message to the network). If the determination 1220 is negative (“NO”Docket No. 14730932100PCTbranch) and the UE has a pending NAS procedure, the UE performs 1209 the NAS procedure by transmitting the corresponding NAS message to the network. FIG. 12B shows that the UE can initiate 1206 another NAS procedure or new instance of the original NAS procedure after canceling the previous NAS procedure 1207B. In the event that a new instance of the NAS procedure is not initiated after block 1207B.

[0121] FIG. 12C shows a flow diagram 1200C of example operations of a UE in which the UE manages a NAS timer based on system information indicating a transition time from the S&F mode to the normal mode. FIG. 12C includes operations similar to those described with reference to FIG. 7C. Initially, the UE might operate 1202 in the RRC idle state and camps on a satellite having a BS node (e.g., eNB or gNB) and a full / partial network node (e.g., a full or partial MME) installed on it. While camping on the satellite, the UE receives 1205C system information indicating the serving cell or satellite is currently operating in the S&F mode and also indicating a transition time ti when the satellite will transition from the S&F mode to the normal mode.

[0122] The UE starts 1207C a NAS timer (e.g., the timer T3451 or a newly defined timer) with a duration Ti based on when the satellite will transition to the normal mode. For example, the duration Ti may be the time difference between the current time ( / ) and the transition time ti. Then the UE checks 1250 whether the NAS timer is still running. If the NAS timer is still running (i.e., “YES” branch of check 1250), the UE refrains 1207D from attempting or reattempting any NAS procedure. The UE continues refraining from performing NAS procedures until the result of check 1250 is negative (“NO” branch), meaning the NAS timer has expired. If the NAS timer has expired (i.e., “NO” branch of check 1250), the UE might perform 1230 an RRC connection establishment procedure. The UE transmits 1234 a NAS message for the NAS procedure. A potential technical advantage of repurposing the timer T3451 for a duration Ti based on transition time (tv) (1207C) is that after the UE sets the new duration Ti of the timer T3451, the UE can follow existing UE behavior for the timer T3451 specified in 3GPP TS 24.301.

[0123] FIG. 13 shows a flow diagram 1300 of example operations of a UE in which the UE manages a NAS procedure based on an operating mode and transition time for a new cell after cell reselection. FIG. 13 includes operations similar to those described with reference to FIG. 8. Initially, the UE operates 1302 in the RRC idle state and camps on a first cell provided by a satellite having a BS node (e.g., eNB or gNB) and a full / partial network node (e.g., a full or partial MME) installed on it. The UE receives 1305-1 system information indicating the first cell or satellite is operating in the S&F mode and including a first time information (e.g., firstDocket No. 14730932100PCTtransition time ti) indicating when the first cell will transition from the S&F mode to the normal mode. As a part of the device booting procedure or upon being triggered by upper layers, the UE initiates 1206 a NAS procedure.

[0124] The UE determines 1320 whether the current time ( / ) is less than ti. If the current time is past ti (i.e., the “NO” branch of determination 1320), the UE performs 1309 the NAS procedure via the first cell. Otherwise, if the current time is less than ti (i.e., the “YES” branch of determination 1320), the UE pauses or suspends 1307-1 the NAS procedure before transmitting a corresponding NAS message to the network. In some implementations, the flow returns from block 1307-1 to block 1320 to again check whether the current time ( / ) is less than ti. Alternatively, the flow may proceed from block 1307-1 to block 1340 if the UE performs a cell reselection.

[0125] Continuing the example of FIG. 13, the UE performs 1340 a cell reselection to a second cell (e.g., due to idle mode mobility). For example, the UE might select the second cell as a result of intra-frequency or inter-frequency measurements and one or more cell reselection criterion. The UE receives 1305-2 system information indicating the second cell or satellite is operating in the S&F mode and including a second time information (e.g., second transition time / ) indicating when the second cell will transition from the S&F mode to the normal mode.

[0126] The UE determines 1325 whether the current time ( / ) is less than t2. If the current time is past (i.e., the “NO” branch of determination 1325), the UE performs 1309 the NAS procedure via the second cell. Otherwise, if the current time is less than t2 (i.e., the “YES” branch of determination 1325), the UE continues to pause or suspend 1307-2 the NAS procedure (before transmitting a corresponding NAS message to the network). Similar to block 1307-1, after pausing / suspending the NAS operation in block 1307-2, the UE may return to block 1325 to repeatedly check whether the current time is greater than U. Alternatively, the UE may select a new target cell (e.g., via cell reselection in block 1340).

[0127] FIG. 14 shows a flow diagram 1400 of example operations of a UE in which the UE controls a NAS timer based on operating mode and transition time for a new cell after cell reselection. FIG. 14 includes operations similar to those described with reference to FIG. 9. The example operations enable the UE to determine how to handle a NAS timer (e.g., timer T3451) after switching to a new cell based on the system information indicating when the new cell will transition from the S&F mode to the normal mode. The operations in blocks 1302 and 1206 have been previously described. In this scenario, after initiating 1206 the NAS procedure, the UEDocket No. 14730932100PCTattempts to perform a first instance of a NAS procedure (e.g., a NAS Attach procedure) by transmitting a NAS message (e.g., a NAS attach request message) to the network. The UE receives 1416 a NAS response message (e.g., a NAS attach reject message) including an S&F wait time duration Ti as part of the NAS procedure. The UE starts 1420 a NAS timer (e.g., T3451) with the duration set to the S&F wait time duration Ti. While the NAS timer is running, the UE refrains from attempting or reattempting any NAS procedure. This follows the existing UE behavior specified in 3GPP TS 24.301.

[0128] While the NAS timer is running, the UE performs 1340 a cell reselection and selects a second cell (e.g., due to the idle mode mobility). After downlink-synchronizing with the second cell, the UE receives 1405 system information indicating whether the second cell is operating in the S&F mode. The UE checks 1450 whether the second cell is operating in the S&F mode. If the second cell is operating in the normal mode (i.e., the “NO” branch of check 1450), the UE stops 1452 the NAS timer (e.g., T3451). This means the UE does not postpone communicating a NAS message if the UE initiates a NAS procedure. On the other hand, if the second cell is operating in the S&F mode (i.e., the “YES” branch of check 1450), the flow proceeds to block 1455.

[0129] The UE determines 1455 whether the system information acquired from the second cell indicates (e.g., transition time (t;)) when the second cell will transition to the normal mode. If the determination at the block 1455 is negative (“NO” branch of check 1455), the UE continues running 1456 the NAS timer (e.g., T3451) with the remaining duration of Ti previously configured in block 1420. On the other hand, if the determination 1455 is positive (“YES” branch of check 1455), the UE restarts 1421 the NAS timer (e.g., T3451) with a new duration T2 set to expire at (or after) the transition time ti when the second cell will transition to the normal mode.

[0130] In some implementations, instead of restarting 1421 the NAS timer (e.g., T3451) with a new duration, the UE may continue running the NAS timer with the remaining duration when the remaining duration will cause the NAS timer to expire later than the transition time ti. Alternatively, instead of restarting 1421 the NAS timer (e.g., T3451) with a new duration, the UE may continue running the NAS timer (e.g., T3451) with the remaining duration when the remaining duration will cause the NAS timer to expire earlier than the transition time ti. In other words, some implementations may adopt either the earliest or the latest option from among the remaining duration of Ti and a new duration that would expire at ti.Docket No. 14730932100PCT

[0131] FIG. 15 shows a flow diagram 1500 of example operations of a UE in which the UE manages a NAS procedure based on available time to complete the NAS procedure before the satellite transitions to an S&F mode. FIG. 15 includes operations similar to those described with reference to FIG. 10. Initially, the UE might operate 1202 in the RRC idle state and camps on a satellite having a BS node (e.g., eNB or gNB) and a full / partial network node (e.g., a full or partial MME) installed on it. In this example, the UE receives 1501 system information indicating the satellite is currently operating in the normal mode (i.e., having a feeder link available). In other words, the system information does not indicate that the satellite is operating in the S&F mode. The UE then initiates 1206 a NAS procedure (e.g., a NAS Attach procedure).

[0132] The UE determines 1538 whether the system information indicates when the satellite will transition to the S&F mode. If the determination 1538 is negative (“NO” branch), the UE performs 1209 the NAS procedure. Otherwise, if the determination 1538 is positive (“YES” branch), meaning the system information indicates a transition time ti indicating when the satellite will transition to the S&F mode, then the flow proceeds to block 1541.

[0133] The UE then determines 1541 whether the remaining time period (77) of the normal mode is less than a threshold value Tthresh. The threshold value Tthresh can be a fixed value specified in the 3 GPP specifications and pre-coded in the UE, or a configurable value provided by the network via a dedicated message (e.g., RRC or NAS message) or via system information. If the determination 1541 is negative (“NO” branch), the flow proceeds to block 1209. Otherwise, if the determination 1541 is positive (“YES” branch), the UE pauses or suspends 1542 the NAS procedure. From block 1542, the flow returns to block 1501 where the UE can receive updated system information indicating the next time when the serving satellite is operating in the normal mode.

[0134] FIG. 16 shows a flow diagram 1600 of example operations of a UE. The UE receives 1605 system information indicating a transition time (fi) when a first cell of a first satellite will switch from an S&F mode to a normal mode. The S&F mode is associated with the first satellite not operating a feeder link to a core network, while the normal mode is associated with the first satellite operating the feeder link to the core network. The UE refrains 1607 from performing a NAS procedure via the first cell when it operates in the S&F mode.

[0135] In some implementations, the UE performs the NAS procedure after the transition time ( / / ) and while the first cell is operating in the normal mode.Docket No. 14730932100PCT

[0136] FIG. 17 shows another flow diagram 1700 of example operations of a UE. The UE camps 1702 on a cell of a satellite. The UE receives 1705 system information indicating whether the cell operates in an S&F mode or a normal mode. The system information indicates timing information (7z) when the cell will transition between the S&F mode and the normal mode. The UE then initiates 1706 a NAS procedure. Based on the timing information, the UE postpones 1707 transmission of a wireless communication message of the NAS procedure until after the satellite transitions to the normal mode.

[0137] In some implementations, postponing the NAS procedure includes refraining from performing the NAS procedure while the first cell is operating in the S&F mode and performing the NAS procedure after the cell transitions to the normal mode at ti.

[0138] FIG. 18 shows a flow diagram of example operations of a UE in which the UE manages a NAS procedure based on a remaining time period (A) for a cell of a satellite to operate in the normal mode. The UE camps 1802 on a cell of a satellite when the cell operates in normal mode. In the normal mode, the cell operates a feeder link to a core network. The UE receives 1805 system information indicating a transition time (fi) when the cell will transition from the normal mode to an S&F mode. The UE calculates 1841 a remaining time period (Tr) between the current time ( / ) and the transition time (A). When the remaining time period (Tr) is less than a threshold time period (Tthresh), the UE refrains 1807 from performing a NAS procedure via the cell.

[0139] FIG. 19 shows a flow diagram 1900 of example operations of a satellite. The satellite operates 1904 a cell of an NTN node in an S&F mode. The satellite communicates 1905 system information including a transition time ti indicating when the satellite will transition from the S&F mode to the normal mode. The satellite operates 1926 the cell in the normal mode beginning at (or after) the transition time. The satellite receives 1934 a NAS message from a UE at (or after) ti while the cell is in the normal mode. In some implementations, the satellite does not receive (and / or does not expect to receive) a NAS message for a UE-initiated NAS procedure while the satellite is in the S&F mode.

[0140] FIG. 20 is a block diagram 2000 illustrating an example user equipment. Note that the depicted hardware configurations represent the processing components and communication components of a UE 2001 (such as the UE 102 described herein). The depicted hardware configurations may omit certain components well-understood to be frequently implemented in such electronic devices, such as displays, peripherals, power supplies, and the like.Docket No. 14730932100PCT

[0141] The UE 2001 includes antennas 2011 A, a radio frequency front end (RF front end) 201 IB, and radio-frequency transceivers (e.g., an LTE transceiver 2003A and a 5G NR transceiver 2003B) for communicating with a network entity (such as an NTN node). The RF front end 201 IB includes one or more modems configured for the corresponding RAT(s) employed (for example, 5G NR, one or more analog-to-digital converters (ADCs), one or more digital-to-analog converters (DACs), signal processors, and the like. In the example illustrated in FIG. 20, the RF front end 201 IB of the UE 2001 may couple or connect the LTE transceiver 2003 A, and the 5G NR transceiver 2003B to the antennas 2011 A to facilitate various types of wireless communication. The RF front end 201 IB operates, in effect, as a physical (PHY) transceiver interface to conduct and process signaling between the one or more processor(s) 2003C and antennas 2011A so as to facilitate various types of wireless communication.

[0142] The antennas 2011A of the UE 2001 may include an array of multiple antennas that may be tuned to one or more frequency bands associated with a corresponding RAT. The antennas 2011 A and the RF front end 201 IB may be tuned to, and / or be tunable to, one or more frequency bands defined by the 3 GPP LTE and 5G NR communication standards and implemented by the LTE transceiver 2003 A, and / or the 5GNR transceiver 2003B. Additionally, the antennas 2011A, the RF front end 201 IB, the LTE transceiver 2003A, and / or the 5G NR transceiver 2003B may be configured to support beamforming for the transmission and reception of communications with an NTN node (e.g., the first BS 114 and first satellite 112). By way of example and not limitation, the antennas 2011A and the RF front end 201 IB may be implemented for operation in sub-gigahertz bands, sub-6 GHz bands, and / or above 6 GHz bands that are defined by the 3GPP LTE and 5G NR communication standards.

[0143] The UE 2001 also includes processor(s) 2003C and computer- readable storage media (CRM) 2003D. The processor(s) 2003C may include, for example, one or more central processing units, graphics processing units (GPUs), or other application-specific integrated circuits (ASIC), and the like. To illustrate, the processor(s) 2003 C may include an application processor (AP) utilized by the UE 2001 to execute an operating system and various user-level software applications, as well as one or more processors utilized by modems or a baseband processor of the RF front end 201 IB.

[0144] CRM 2003D may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), Flash memory, solid-state drive (SSD) or other mass-storage devices,Docket No. 14730932100PCTand the like useable to store one or more sets of executable software instructions and associated data that manipulate the one or more processor(s) 2003 C and other components of the UE 2001 to perform the various functions described herein and attributed to the UE 2001. The sets of executable software instructions include, for example, an operating system (OS) and various drivers (not shown), and various software applications (not shown), which are executable by processor(s) 2003C to enable user-plane communication, control-plane signaling, and user interaction with the UE 2001.

[0145] In accordance with aspects of this disclosure, the UE 2001 implements a NAS layer 2008 (similar to NAS layer 309) and an RRC layer 2004 (similar to RRC layer 304). The UE 2001 can implement the NAS layer 2008 and the RRC layer 2004 using hardware and / or software -such as using a special-purpose processor or by a combination of a processor with computer readable instructions. The RRC layer 2004 can process communications from a lower layer (such as the physical and media access control layers (shown as PHY / MAC 2002)) and the NAS layer 2008. In some implementations, the UE 2001 maintains a NAS procedure module 2050 that implements features of this disclosure, such as any of the operations / capabilities described with reference to FIG. 6 through FIG. 18. In some aspects, the UE 2001 may maintain the NAS procedure module 2050 in computer readable media / memory 2003D. In accordance with aspects of this disclosure, the UE 2001 implements an S&F operation module 2009. The S&F operation module 2009 may implement one or more of the techniques of the disclosure. For example, the S&F operation module 2009 can process and store information about the operating mode (e.g., S&F mode or normal mode) of a satellite. In some aspects, the S&F operation module 2009 may reside in computer readable media / memory 2003D.

[0146] FIG. 21A shows an example control plane protocol stack 2100 A in accordance with aspects of this disclosure. The diagram of the NTN control plane protocol stack 2100A shows the NR-Uu interface (e.g., via a service link) between the first satellite 112 (e.g., the first BS 114) and the UE 102. The NR-Uu includes a radio resource control (RRC) protocol in addition to the PDCP, RLC, MAC, and PHY layers. The UE 102 and the first BS 114 serve as endpoints of the RRC layer 304 and the RRC 2114, respectively. The RRC protocol can have one of a plurality of different states associated with the RRC connection. For example, the RRC connection can have an RRC state 2104 of RRC IDLE, RRC CONNECTED, or RRC INACTIVE as described with reference to FIG. 1.Docket No. 14730932100PCT

[0147] The Ng-C interface is between the first BS 114 and the CN 131. The example CN 131 in FIG. 21A can illustrate the operation of an AMF of the 5GC. The diagram of the NTN control plane protocol stack 2100A shows an N1 interface between the NAS layer 309 of the UE 102 and the NAS layer 2138 of the CN 131. The N1 interface links the UE 102 and the AMF of the CN 131 via an access network. In FIG. 21 A, the access network includes the NTN (such as the first satellite 112, first BS 114) coupled by the NTN gateway 132. In normal operation, and in traditional implementations of regenerative satellite access, the first satellite 112 does not participate in the N1 interface other than to relay communications through the lower layers of the protocol stacks of the NR-Uu and Ng-C interfaces. In some implementations, the first satellite 112 can perform an S&F operation 2109. In accordance with aspects of this disclosure, the NAS layer 309 can refrain from performing a NAS procedure (e.g., triggered by a command from upper layers 301) depending on the operating mode of the first satellite 112. For example, the NAS layer 309 can suspend, pause, cancel, withdraw, or otherwise prevent the NAS operation from continuing when the first satellite 112 is operating in the S&F mode. In some implementations, the RRC layer 304 may implement aspects of this disclosure. For example, the RRC layer 304 might implement techniques to prevent performance of a NAS procedure when the first satellite 112 is operating in the S&F mode.

[0148] The example illustrated in FIG. 21A shows the first BS 114 as a gNB. However, FIG.21A could be modified to describe a scenario in which the first BS 114 is an eNB or gNB. The CN 131 can illustrate the operation of a mobility management entity (MME) of an EPC. For example, if the radio access technology for the NTN RAN is E-UTRA or NB-IoT, the Ng-C interface can be referred to as an SI -MME interface. The Nr-Uu can be referred to as an LTE-Uu interface.

[0149] FIG. 21A shows the S&F operation 2109 as part of the first satellite 112. However, alternatively, or additionally, the first BS 114 (or even the NTN gateway 132) can perform some or all of the S&F operation 2109. For example, the NTN gateway 132 can include a combination of nodes or functions, some of which are implemented in proximity to the first satellite 112 and some of which are implemented in proximity to the CN 131. The S&F operation 2109 (implemented by whichever NTN node or nodes) can maintain a status of the RRC state 2104 and the NAS mode 2108 in association with a particular UE (such as the UE 102). The first satellite 112 can maintain the status by any combination of local memory, messaging, or other protocols (not shown).Docket No. 14730932100PCT

[0150] In accordance with aspects of this disclosure, an MME-onboard can implement all or part of the S&F operation 2109. The MME-onboard can coordinate with an MME-ground to collectively implement the features of the NAS entity 2138.

[0151] FIG.21B shows an example user plane protocol stack 2100B in accordance with aspects of this disclosure. FIG. 21B includes a visual representation of the NTN portion of user plane protocol stack 2100B involving the UE 102, the first satellite 112, the NTN gateway 132, and a CN 131. The example CN 131 in FIG. 2 IB can illustrate a user plane function (UPF) of the 5GC. If the CN 131 is an EPC, the features of CN 131 can be performed by a serving gateway (SGW) function. In FIG. 21B, the NTN first BS 114 is onboard the first satellite 112. In the illustrated example in FIG. 21B, the first BS 114 is a 5G NR base station, referred to as a gNB. In an alternative implementation, the first BS 114 can use E-UTRA or NB-IoT and can be referred to as an eNB.

[0152] The diagram of the NTN user plane protocol stack 2100B shows the NR-Uu interface (e.g., via a service link) between the first satellite 112 (e.g., the first BS 114) and the UE 102. When the first BS 114 is an eNB, the user interface is referred to as LTE-Uu instead of NR-Uu. The diagram of the NTN user plane protocol stack 2100B shows the Ng-U interface (e.g., via a feeder link) between the first satellite 112 (e.g., first BS 114) and the CN 131 via the NTN gateway 132. When the first BS 114 is an eNB, the user interface is referred to as Sl-U instead of Ng-U.

[0153] On the UE 102, the user plane protocol stack 2100B includes protocol layers for the user-plane Protocol Data Unit (PDU), the Service Data Adaptation Protocol (SDAP), the Packet Data Convergence Protocol (PDCP), the Radio Link Control (RLC) protocol, the Medium Access Control (MAC), and Physical Layer (PHY). The first satellite 112 also implements the SDAP, PDCP, RLC, MAC, and PHY layers. However, user data (e.g., PDU messages) are passed through the first satellite 112 (via the lower layer protocols) to the PDU on the CN 131. If the radio access technology for the NTN RAN is E-UTRA or NB-IoT, the SDAP layer may not exist. In some alternative implementations, user plane PDUs may be exchanged between the UE 102 and the CN 131 via the N1 interface or the control plane protocol stack 2100A. In such cases, the user plane protocol state may not exist.

[0154] FIG. 22 shows a block diagram of an example wireless communication system 2200 showing hardware features and communication interfaces. The depicted hardware configurations may omit certain components well-understood to be frequently implemented in such electronicDocket No. 14730932100PCTdevices, such as displays, peripherals, power supplies, and the like. The wireless communication system 2200 includes the same elements as described with reference to FIG. 1, including the UE 102, the first BS 114, the first satellite 112, and the CN 131. In some implementations, the UE 102 can support at least a 5G NR (or simply, “NR”) or E-UTRA air interface to communicate with the first BS 114. The first BS 114 connects to the CN 131 via an interface (e.g., SI or NG interface). The first BS 114 can connect to other base stations (including the ground BS 134 or the BS 2214 operating a TN cell 2217) via an interface (e.g., X2 or Xn interface) for interconnecting NG RAN nodes.

[0155] The first BS 114 is equipped with processing hardware 2204 that can include a receiver 2205B configured to receive data in the uplink direction. The processing hardware 2204 can also include a transmitter 2205A configured to transmit data in the downlink direction. The processing hardware further can one or more general-purpose processor(s) 2205C (e.g., CPUs) and a non-transitory computer-readable memory (CRM) 2205D storing instructions that the one or more general-purpose processors execute. Additionally, or alternatively, the processing hardware 2204 can include special-purpose processing units. The processor 2205C may include, for example, one or more central processing units, graphics processing units (GPUs), or other application-specific integrated circuits (ASICs), and the like. CRM 2205D may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory usable to store device data of the first BS 114. The first satellite 112 can include processing hardware 2212, such as a transmitter 2212 A, a receiver 2212B, a processor 2212C, and CRM 2212D (similar to components 2204, 2205A, 2205B, 2205C and 2205D of the first BS 114). In some implementations, the components 2212A, 2212B, 2212C and 2212D are shared or commonly implemented with the components 2205 A, 2205B, 2205C and 2205D. The BS 2214 can include similar components (not shown) as the processing hardware 2204.

[0156] The CN 131 can be an Evolved Packet Core (EPC) and / or a 5G core (5GC). Among other components, the EPC can include a Serving Gateway (SGW), a Mobility Management Entity (MME), a Home Subscriber Server (HSS), and a Packet Data Network Gateway (PGW). The SGW in general is configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., and the MME is configured to manage authentication, registration, paging, and other related functions. The PGW provides connectivity from the UE to one or more external packet data networks, e.g., an Internet network and / or an Internet Protocol (IP)Docket No. 14730932100PCTMultimedia Subsystem (IMS) network. The 5GC includes a UPF, a UDM, an AMF, and / or an SMF. Generally speaking, the UPF is configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., the AMF is configured to manage authentication, registration, paging, and other related functions, and the SMF is configured to manage PDU sessions. The HSS and the UDM store and maintain subscription information regarding the UE 102. The CN 131 can be implemented by one or more processing elements (shown as processing hardware 2231). The processing hardware 2231 can include a transmitter 2232A, a receiver 2232B, a processor 2232C, and a CRM 2232D, similarly, to corresponding components described with reference to processing hardware 2212 and 2204.

[0157] The transmitters 2202A, 2212A, 2205 A, and 2232A and receivers 2202B, 2212B, 2205B, and 2232B are examples of a communication unit. The processors 2202C, 2212C, 2205C, and 2232C can also be referred to as a processing system. Other examples of a communication unit and a processing system are possible, including some examples that are commonly used in a wireless communication system. The first BS 114, UE 102, first satellite 112, and CN 131 can include other components not illustrated in FIG. 22.

[0158] This disclosure includes examples for managing S&F transition time. Some aspects relate to handling S&F transition time information from lower layers. A RAN node broadcasts time information for a transition from a current S&F operation mode to normal mode (and vice versa) as part of system information. The transition time is also provided to a NAS layer. In some implementations, the information from the lower layer can be utilized for the NAS layer, e.g., as a value for NAS timer T3451. When a NAS layer receives a “S&F transition time” value from lower layers, the NAS layer initiates timer T3451 with the values.

[0159] In some implementations, when (a) the UE indicates support for S&F satellite operation in an ATTACH REQUEST message, (b) the UE is not a UE configured to use AC11 - 15 in a selected PLMN, (c) the UE receives and stores estimated uplink delivery time duration included in the S&F satellite operation parameters IE, and (d) lower layers provide “S&F transition time from non-S&F mode to S&F mode” or provides "S&F transition time" and "current operation mode" is non-S&F mode, the UE calculates the S&F remaining time duration. The UE calculates S&F remaining time duration as follows: let tl be the transition time offset value provided by lower layers, and let t be the current time offset to the beginning of week (Monday 00:00:00 UTC) in seconds. If tl is greater than or equal to t, then the time shall be the value tl - t. If tl is less than / , the time shall be the value tl + 604800 - 1. If the S&F remaining time duration is lessDocket No. 14730932100PCTthan the estimated uplink delivery time duration, the UE does not request the lower layer to establish a RRC connection.

[0160] In some implementations, a NAS layer receives a "S&F transition time" from the lower layers. If lower layers provides "S&F transition time from S&F mode to non-S&F mode" or provides "S&F transition time" and "current operation mode" is S&F mode, the UE proceeds as described below. If the UE indicates support for S&F satellite operation in the ATTACH REQUEST message and the UE is not a UE configured to use AC11 - 15 in selected PLMN, then the UE may start timer T3451 with the following value and reset the attach attempt counter, let tl be the transition time offset value provided by lower layers, and let t be the current time offset to the beginning of week (Monday 00:00:00 UTC) in seconds. If tl is greater than or equal to t, then the time shall be the value tl - t. If tl is less than / . the time shall be the value tl + 604800 - t. If the above conditions do not apply, the UE ignores the “S&F transition time.” The UE aborts the attach procedure, stay in the current serving cell, change the state to EMM-DEREGISTERED. ATTEMPTING-TO-ATTACH and apply the normal cell reselection process.

[0161] FIG. 1 through FIG. 22 and the operations described herein are examples meant to aid in understanding example implementations and should not be used to limit the potential implementations or limit the scope of the claims, some implementations may perform additional operations, fewer operations, operations in parallel or in a different order, and some operations differently. Alternatively, or in addition to the other examples described herein, examples include any combination of the following enumerated example implementation options (referred to as clauses for clarity).

[0162] Clause 1 : A method of a user equipment (UE) (102) for wireless communication via a non-terrestrial network (NTN), the method comprising: receiving system information (105, 605, 705, 805-1, 805-2, 1005) indicating a transition time (ti) when a first cell of a first satellite (112) will transition from a store-and-forward (S&F) mode to a normal mode, the S&F mode associated with the first satellite not operating a feeder link to a core network and the normal mode associated with the first satellite operating the feeder link to the core network; refraining (107, 607, 707A, 707B, 707C, 807-1, 807-2, 1007) from performing a non-access stratum (NAS) procedure via the first cell when the first cell is operating in the S&F mode.

[0163] Clause 2: The method of clause 1, wherein the refraining from performing the NAS procedure is based on a determination that the NAS procedure is one of a first type of NAS procedures that require access to the core network, the first type of NAS procedures including atDocket No. 14730932100PCTleast one of the following: a NAS Attach procedure, a tracking area update (TAU) procedure, a service request procedure, or a detach procedure.

[0164] Clause 3 : The method of clause 1 or 2, wherein the refraining from performing the NAS procedure includes at least one of: pausing (707A) or suspending the NAS procedure until the transition time, canceling (707B) or withdrawing the NAS procedure, or starting (707C) a NAS timer with a duration set to expire at, or after, the transition time.

[0165] Clause 4: The method of clause 3, wherein the NAS timer is a timer T3451, and wherein starting the NAS timer includes setting the duration (77) of the timer T3451 based on a difference between a current time ( / ) and the transition time ( / ;).

[0166] Clause 5: The method of any one of clauses 1 to 4, further comprising: performing (109, 609, 909, 708) the NAS procedure when the first cell is operating in the normal mode at, or after, the transition time.

[0167] Clause 6: The method of clause 5, wherein the performing the NAS procedure includes at least one of: resuming the NAS procedure after pausing or suspending the NAS procedure, reinitiating the NAS procedure after canceling or withdrawing the NAS procedure, or initiating a new instance of the NAS procedure.

[0168] Clause 7: The method of any one of clauses 1 to 6, further comprising: camping on the first cell of the first satellite when the first cell is operating in the normal mode; receiving system information (1038) indicating an S&F transition time I2) when the first cell will transition from the normal mode to the S&F mode; refraining from performing the NAS procedure via the first cell when a remaining time period (77) until the S&F transition time is less than a threshold time period (Tthresh).

[0169] Clause 8: The method of clause 7, where the threshold time period (Tthresh) is associated with one of: an amount of time for completion of the NAS procedure; an amount of time for transmission of an uplink (UL) NAS message of the NAS procedure from the UE via the satellite to a network entity of the core network; an amount of time for the satellite to receive a response from the network entity after the transmission of the UL NAS message; or an amount of time configured by a mobility management entity (MME) of the satellite.

[0170] Clause 9: The method of any one of clauses 1 to 4, further comprising: reselecting and camping on a second cell; receiving, from the second cell, second system information indicating whether the second cell is operating in the S&F mode or the normal mode, the second system information further indicating a second transition time when the second cell will transition fromDocket No. 14730932100PCTthe S&F mode to the normal mode, or vice versa; refraining from performing the NAS procedure via the second cell when the second cell is operating in the S&F mode; and performing the NAS procedure via the second cell when the second cell is operating in the normal mode.

[0171] Clause 10: The method of clause 9, further comprising: resetting (921) a running NAS timer (T3451) to a new duration after the receiving the second system information when the second system information indicates the second cell is operating in the S&F mode, the new duration based on a difference between a current time and the second transition time from the S&F mode to the normal mode.

[0172] Clause 11: The method of clause 9, further comprising: expiring (424) a running NAS timer (T3451) after the receiving the second system information when the second system information indicates the second cell is operating in the normal mode or when the second cell transitions to the normal mode.

[0173] Clause 12: A method of a user equipment (UE) (102) for wireless communication via a non -terrestrial network (NTN), the method comprising: camping on a cell of a satellite; receiving system information indicating whether the cell is presently operating in a store-and-forward (S&F) mode or a normal mode, the S&F mode associated with the cell not operating a feeder link to a core network and the normal mode associated with the cell operating the feeder link to the core network, wherein the system information includes timing information (C) indicating when the cell will transition from the S&F mode to the normal mode, or vice versa; initiating a non-access stratum (NAS) procedure; and postponing the NAS procedure until after the satellite transitions to the normal mode based on the timing information.

[0174] Clause 13: The method of clause 12, wherein the postponing the NAS procedure includes at least one of: refraining from performing the NAS procedure when the cell is operating in the S&F mode; or performing the NAS procedure when the cell is operating in the normal mode.

[0175] Clause 14: The method of clause 12, further comprising: determining a remaining time (Tr) for the cell to operate in the normal mode before the cell will transition to the S&F mode based on the timing information ( / ;); and refraining from performing the NAS procedure if the remaining time is less than a threshold amount of time (Tthresh) for the NAS procedure.

[0176] Clause 15: A method of a user equipment (UE) (102) for wireless communication via a non -terrestrial network (NTN), the method comprising: camping on a cell of a satellite (122) when the cell is operating in a normal mode, the normal mode associated with the cell operating a feeder link to a core network; receiving system information indicating that the cell is presentlyDocket No. 14730932100PCToperating in the normal mode and indicating a transition time (L) when the cell will transition from the normal mode to a store-and-forward (S&F) mode, the S&F mode associated with the cell not operating the feeder link to the core network; calculating a remaining time period (77) between a current time ( / ) and the transition time (tv); and refraining (1042) from performing a NAS procedure via the cell when the remaining time period (77) is less than a threshold time period (Thresh associated with the NAS procedure.

[0177] Clause 16: The method of clause 15, where the threshold time period Tthresh) is associated with one of: an amount of time for completion of the NAS procedure; an amount of time for transmission of an uplink (UL) NAS message of the NAS procedure from the UE via the satellite to a network entity of the core network; an amount of time for the satellite to receive a response from the network entity after the transmission of the UL NAS message; or an amount of time configured by a mobility management entity (MME) of the satellite.

[0178] Clause 17: The method of clause 15 or 16, further comprising, after the cell transitions to the S&F mode: receiving system information indicating a transition time (C) when the cell will transition from the S&F mode to the normal mode; and performing the NAS procedure at, or after the transition time (tT) while the cell is operating in the normal mode.

[0179] Clause 18: An apparatus, comprising: a communication unit; and a processing system configured to control the communication unit to implement any one of the methods of any one of clauses 1 to 14.

[0180] Aspects of the subject matter described in this disclosure can be implemented as a computer-readable medium having stored therein instructions which, when executed by a processor, causes the processor to perform any one of the above-mentioned functionalities. Aspects of the subject matter described in this disclosure can be implemented as a system having means for implementing any one of the above-mentioned functionalities. Aspects of the subject matter described in this disclosure can be implemented as an apparatus having one or more processors configured to perform one or more operations from any one of the above-mentioned functionalities.

[0181] The following additional considerations may apply to the foregoing and the following discussions. Generally speaking, description for one of the above figures can apply to another of the above figures. Any event or block described above can be optional. For example, an event orblock with dashed lines can be optional. In some implementations, “message” is used and can be replaced by “information element (IE),” and vice versa. In some implementations, “IE” isDocket No. 14730932100PCTused and can be replaced by “field,” and vice versa. In some implementations, “configuration” can be replaced by “configurations” or “configuration parameters,” and vice versa. In some implementations, “some” means “one or more.” In some implementations, “at least one” means “one or more.” The “eNB” can be replaced by “base station,” “gNB,” “6G base station,” “evolved gNB,” or 6G gNB. “Core network (CN)” can be replaced by EPC, 5GC or 6GC.

[0182] Unless defined otherwise, technical and scientific terms used herein have the same meaning as is commonly understood by one of ordinary skill in the art to which this specification belongs. The terms “first,” “second,” and the like, as used herein do not denote any order, quantity, or importance, but rather are used to distinguish one element from another. The use of terms “including,” “comprising” or “having” and variations thereof herein are meant to encompass the items listed thereafter and equivalents thereof as well as additional items. The terms “connected” and “coupled” are not restricted to physical or mechanical connections or couplings and can include electrical connections or couplings, whether direct or indirect. Furthermore, terms “circuit” and “circuitry” and “control unit” may include either a single component or a plurality of components, which are either active and / or passive and are connected or otherwise coupled together to provide the described function. In addition, the term operationally coupled as used herein includes wired coupling, wireless coupling, electrical coupling, magnetic coupling, radio communication, software based communication, or combinations thereof.

[0183] Some or all of the foregoing or the following implementations can be jointly combined or formed to be a new or another one implementation. The foregoing or the following techniques can be used to solve at least (but not limited to) the issue(s) or scenario(s) mentioned in this disclosure. Any two or more than two of the foregoing or the following paragraphs, (sub)-bullets, points, actions, or claims described in each method / technique / implementation may be combined logically, reasonably, and properly to form a specific method. Any sentence, paragraph, (sub)-bullet, point, action, or claim described in each of the foregoing or the following technique(s) / implementation(s) / concept(s) may be implemented independently and separately to form a specific method. Dependency, such as “based on,” “more specifically,” “where” or etc., in technique(s) / implementation(s) / concept(s) mentioned in this disclosure is just one possible implementation which would not restrict the specific method.

[0184] As used herein, the terms “user device”, “user equipment” (for example, UE 102), “wireless communication device”, “mobile communication device”, “communication device”, orDocket No. 14730932100PCT“mobile device” refer to any one or all of cellular telephones, smartphones, portable computing devices, personal or mobile multi-media players, laptop computers, tablet computers, smartbooks, Internet-of-Things (loT) devices, palm-top computers, wireless electronic mail receivers, multimedia Internet enabled cellular telephones, wireless gaming controllers, display sub-systems, driver assistance systems, vehicle controllers, vehicle system controllers, vehicle communication system, infotainment systems, vehicle telematics systems or subsystems, vehicle display systems or subsystems, vehicle data controllers, point-of-sale (POS) terminals, health monitoring devices, drones, cameras, media-streaming dongles or another personal media devices, wearable devices such as smartwatches, wireless hotspots, femtocells, broadband routers or other types of routers, and similar electronic devices which include a programmable processor and memory and circuitry configured to perform operations as described herein. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Still further, the user device can operate as an internet-of-things (loT) device or a mobile-internet device (MID). Depending on the type, the user device can include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0185] Certain techniques are described in this disclosure as including logic or a number of components or modules. Modules can be software modules (e.g., code, or machine-readable instructions stored on non-transitory machine-readable medium) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module can comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), a digital signal processor (DSP), etc.) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

[0186] When implemented in software, the techniques can be provided as part of the operating system, a library used by multiple applications, a particular software application, etc. TheDocket No. 14730932100PCTsoftware can be executed by one or more general-purpose processors or one or more specialpurpose processors.

[0187] As used herein, the terms “component” and “module” are intended to be broadly construed as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, or a combination of hardware and software. As used herein, the phrase “based on” is intended to be broadly construed to mean “based at least in part on.”

[0188] As used herein, a phrase referring to a list of items separated by “or” refers to any combination of those items, including single members. For example, “a, b, or c” is intended to cover the possibilities of: a only, b only, c only, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a and b and c.

[0189] In this disclosure, an expression of “X / Y” may include meaning of any of the following: “X or Y” or “X and Y” or “X and / or Y." An expression of “(A) B” or “B (A)” may include concept of “only B.” An expression of “(A) B” or “B (A)” may include the concept of “A+B” or “B+A.”

[0190] In this disclosure, the term "can" indicates a capability, or alternatively indicates a possible implementation option. The term "may" indicates a permission or a possible implementation option.

[0191] Some aspects are described herein in connection with thresholds. As used herein, satisfying a threshold may refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.

[0192] The various illustrative components, logic, logical blocks, modules, circuits, operations and algorithm processes described in connection with the implementations disclosed herein may be implemented as electronic hardware, firmware, software, or combinations of hardware, firmware or software, including the structures disclosed in this specification and the structural equivalents thereof. The interchangeability of hardware, firmware and software has been described generally, in terms of functionality, and illustrated in the various illustrative components, blocks, modules, circuits and processes described above. Whether such functionality is implemented in hardware, firmware or software depends upon the particular application and design constraints imposed on the overall system.Docket No. 14730932100PCT

[0193] As described above, some aspects of the subject matter described in this specification can be implemented as software. For example, various functions of components disclosed herein, or various blocks or steps of a method, operation, process or algorithm disclosed herein can be implemented as one or more modules of one or more computer programs. Such computer programs can include non-transitory processor-executable or computer-executable instructions encoded on one or more tangible processor-readable or computer-readable storage media for execution by, or to control the operation of, a data processing apparatus including the components of the devices described herein. By way of example, and not limitation, such storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store program code in the form of instructions or data structures. Combinations of the above should also be included within the scope of storage media.

[0194] Various modifications to the implementations described in this disclosure may be readily apparent to persons having ordinary skill in the art, and the generic principles defined herein may be applied to other implementations without departing from the scope of this disclosure. Thus, the claims are not intended to be limited to the implementations shown herein but are to be accorded the widest scope consistent with this disclosure, the principles and the novel features disclosed herein.

[0195] Additionally, various features that are described in this specification in the context of separate implementations also can be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation also can be implemented in multiple implementations separately or in any suitable subcombination. As such, although features may be described above as acting in particular combinations, and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

[0196] The drawings may schematically depict one or more example processes in the form of a flowchart or flow diagram. However, other operations that are not depicted can be incorporated in the example processes that are schematically illustrated. For example, one or more additional operations can be performed before, after, simultaneously, or between any of the illustrated operations. In some circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the implementations described aboveDocket No. 14730932100PCTshould not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other implementations are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results.

[0197] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects. While the aspects of the disclosure have been described in terms of various examples, any combination of aspects from any of the examples is also within the scope of the disclosure. The examples in this disclosure are provided for pedagogical purposes.

Claims

Docket No. 14730932100PCTCLAIMSWhat is claimed is:

1. A method of a user equipment (UE) (102) for wireless communication via a non-terrestrial network (NTN), the method comprising:receiving system information (105, 605, 705, 805-1, 805-2, 1005) indicating a first cell of a first satellite (112) is operating in a store-and-forward (S&F) mode and including a transition time (ti) when the first cell will transition from the S&F mode to a normal mode, the S&F mode associated with the first satellite not operating a feeder link to a core network and the normal mode associated with the first satellite operating the feeder link to the core network;starting (707C, 1207C) a non-access stratum (NAS) timer with a duration set to expire at, or after, the transition time; andrefraining (107, 607, 807-1, 807-2, 1007, 1107, 1207D) from performing a NAS procedure via the first cell while the NAS timer is running.

2. The method of claim 1, wherein the refraining from performing the NAS procedure is based on a determination that the NAS procedure is one of a first type of NAS procedures that require access to the core network, the first type of NAS procedures including at least one of the following:a NAS Attach procedure,a tracking area update (TAU) procedure,a service request procedure, ora detach procedure.

3. The method of claim 1 or 2, wherein the NAS timer is a timer T3451, and wherein starting the NAS timer includes setting the duration (77) of the timer T3451 based on a difference between a current time ( / ) and the transition time ( / ;).

4. The method of any one of claims 1 to 3, further comprising:performing (109, 609, 909, 708) the NAS procedure when the first cell is operating in the normal mode at, or after, the transition time.

5. The method of claim 4, whereinthe refraining from performing the NAS procedure includes at least one of:Docket No. 14730932100PCTpausing (707A) or suspending the NAS procedure until the transition time, canceling (707B) or withdrawing the NAS procedure; andwherein the performing the NAS procedure includes at least one of:resuming the NAS procedure after pausing or suspending the NAS procedure, reinitiating the NAS procedure after canceling or withdrawing the NAS procedure, orinitiating a new instance of the NAS procedure.

6. The method of any one of claims 1 to 5, further comprising:camping on the first cell of the first satellite when the first cell is operating in the normal mode;receiving system information (1038) indicating an S&F transition time (t2) when the first cell will transition from the normal mode to the S&F mode; andrefraining (1042) from performing the NAS procedure via the first cell when a remaining time period (71) until the S&F transition time is less than a threshold time period (Tthresh).

7. The method of claim 6, wherein the threshold time period (Tthresh) is associated with one of:an amount of time for completion of the NAS procedure;an amount of time for transmission of an uplink (UL) NAS message of the NAS procedure from the UE via the satellite to a network entity of the core network;an amount of time for the satellite to receive a response from the network entity after the transmission of the UL NAS message; oran amount of time configured by a mobility management entity (MME) of the satellite.

8. The method of any one of claims 1 to 3, further comprising:reselecting and camping on a second cell;receiving, from the second cell, second system information indicating the second cell is operating in the S&F mode or the normal mode, the second system information including a second transition time when the second cell will transition from the S&F mode to the normal mode, or vice versa;resetting (921) the NAS timer to a new duration after the receiving the second system information, the new duration based on a difference between a current time and the second transition time; andDocket No. 14730932100PCTrefraining from performing the NAS procedure via the second cell while the NAS timer is running.

9. The method of any one of claims 1 to 8, further comprising:expiring (424) the NAS timer after the receiving subsequent system information indicating the first cell is operating in the normal mode.

10. A method of a user equipment (UE) (102) for wireless communication via a non-terrestrial network (NTN), the method comprising:camping on a cell of a satellite (122) when the cell is operating in a normal mode, the normal mode associated with the cell operating a feeder link to a core network;receiving system information indicating a first transition time (ti) when the cell will transition from the normal mode to a store-and-forward (S&F) mode, the S&F mode associated with the cell not operating the feeder link to the core network;calculating a remaining time period (Ti) between a current time ( / ) and the first transition time (Z7); andrefraining (1042) from performing a NAS procedure via the cell when the remaining time period (71) is less than a threshold time period (Tthresh) associated with the NAS procedure.

11. The method of claim 10, wherein the threshold time period (Tthresh) is associated with one of:an amount of time for completion of the NAS procedure;an amount of time for transmission of an uplink (UL) NAS message of the NAS procedure from the UE via the satellite to a network entity of the core network;an amount of time for the satellite to receive a response from the network entity after the transmission of the UL NAS message; oran amount of time configured by a mobility management entity (MME) of the satellite.

12. The method of claim 10 or 11, further comprising, after the cell transitions to the S&F mode:receiving system information indicating the cell is operating in the S&F mode and including a second transition time ( / ?) when the cell will transition from the S&F mode to the normal mode; andrefraining from performing the NAS procedure via the cell when the cell is operating in the S&F mode.

13. The method of claim 12, further comprising:Docket No. 14730932100PCTstarting a NAS timer with a duration set to expire at, or after, the second transition time ( / ?); andrefraining from performing the NAS procedure via the cell while the NAS timer is running.

14. The method of claim 12 or 13, comprising:performing the NAS procedure at, or after the transition time (7 ) while the cell is operating in the normal mode.

15. An apparatus, comprising:a communication unit; anda processing system configured to control the communication unit to implement any one of the methods of any one of claims 1 to 14.