Method and user equipment for waiting timer for NTN storage and forwarding

Abstract

A method and user equipment for providing a wait timer for non-terrestrial network storage and forwarding in a wireless communication system, where the method for the user equipment comprises: initiating a first program to a first network, where the first program is an attach, tracking area update program or a service request program; receiving a configuration of latency for storage and forwarding operations; starting a first timer based on the latency, where when the first timer is running, the user equipment is prohibited from initiating a first program to the first network for storage and forwarding operations; and stopping the first timer if the user equipment initiates or successfully completes a second procedure in a cell of a second network, where the second procedure is an attach, tracking area update procedure or a service request procedure.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority and benefit to U.S. Provisional Patent Application Serial No. 63 / 666,041, filed June 28, 2024, which is hereby incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure generally relates to wireless communication networks, and more specifically, to methods and apparatus for using wait timers for store-and-forward (S&F) in non-terrestrial networks (NTNs) within wireless communication systems. Background Technology

[0004] With the rapid growth in demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that communicate with Internet Protocol (IP) packets. This type of IP packet communication can provide users of mobile communication devices with IP-bearing voice, multimedia, multicast, and video-on-demand communication services.

[0005] An exemplary network architecture is the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). E-UTRAN systems can provide high data throughput to enable the aforementioned IP-based voice and multimedia services. Currently, the 3GPP standards organization is discussing next-generation (e.g., 5G) radio technologies. Therefore, changes to the current body of the 3GPP standards are currently being submitted and considered to facilitate the evolution and completion of the 3GPP standards. Summary of the Invention

[0006] Methods, systems, and apparatus are provided for a wait timer for store-and-forward (S&F) in a non-terrestrial network (NTN) wireless communication system, enabling user equipment (UE) to properly handle the wait timer.

[0007] In various embodiments, a method for a UE in a wireless communication system includes: initiating a first procedure to a first network, wherein the first procedure is an attach, tracking area update (TAU) procedure, or service request procedure; receiving a configuration of a waiting time for S&F operations; starting a first timer based on the waiting time, wherein while the first timer is running, the UE is prohibited from initiating the first procedure to the first network for the S&F operations; and stopping the first timer when the UE initiates a second procedure in a cell of a second network, wherein the second procedure is an attach, TAU procedure, or service request procedure. Attached Figure Description

[0008] Figure 1 A diagram showing a wireless communication system according to an embodiment of the present invention;

[0009] Figure 2 This is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an embodiment of the present invention;

[0010] Figure 3 This is a functional block diagram of a communication system according to an embodiment of the present invention;

[0011] Figure 4 This is according to an embodiment of the present invention. Figure 3 Functional block diagram of the program code;

[0012] Figure 5 It is in 3GPP TR 38.821V16.0.0 Figure 4 .1-1: Reproduction of a typical case of non-terrestrial networks based on transparent payloads;

[0013] Figure 6 It is in 3GPP TR 38.821V16.0.0 Figure 4 .1-2: Reproduction of typical non-terrestrial network scenarios based on regenerative payloads;

[0014] Figure 7 It is in 3GPP TR 38.821V16.0.0 Figure 5 2.1-1: Reproduction of regenerated satellites without ISL or gNB processing payloads;

[0015] Figure 8 It is in 3GPP TR 38.821V16.0.0 Figure 5 2.1-2: Reproduction of regenerated satellites with payloads that have ISL and gNB processing;

[0016] Figure 9 It is in 3GPP TR 38.821V16.0.0 Figure 5 2.2-1: Reproduction of NG-RAN with gNB-DU-based regenerative satellites;

[0017] Figure 10 This is a reproduction of Figure A-1 in 3GPP TR 22.865V2.0.0: a diagram illustrating the “Normal / Default Operation” and “S&F Operation” modes in a 5G system with satellite access;

[0018] Figure 11 It is in 3GPP TR 23.700-29V1.0.0 Figure 6.12.2-1: Reproduction of attachments without PDN connectivity;

[0019] Figure 12 This is an example diagram illustrating an NTN network according to an embodiment of the present invention;

[0020] Figure 13 This is an example diagram illustrating a first procedure according to an embodiment of the present invention, wherein a UE can initiate a first procedure (e.g., to a first network);

[0021] Figure 14 The following is an example diagram illustrating the problem according to an embodiment of the present invention: retrying to attach to the original network or a TAU procedure (e.g., for S&F) is not the best option because the UE may lose the opportunity to obtain normal service;

[0022] Figure 15 This is an illustration of an embodiment of the present invention. Figure 14 Example diagrams illustrating solutions to the problems presented in the document;

[0023] Figure 16 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention, including receiving a configuration of a first timer from a first network, starting the first timer based on the configuration, and stopping the first timer in response to initiating a second procedure or determining to reselect to a second network;

[0024] Figure 17 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention, comprising: initiating a first procedure to a first network, wherein the first procedure is an attach procedure, a TAU procedure, or a service request procedure; receiving a configuration of a waiting time for S&F operations; starting a first timer based on the waiting time, wherein while the first timer is running, the UE is prohibited from initiating the first procedure to the first network for S&F operations; and stopping the first timer when the UE initiates a second procedure in a cell of a second network, wherein the second procedure is an attach procedure, a TAU procedure, or a service request procedure. Detailed Implementation

[0025] The invention described herein can be applied to or implemented in the exemplary wireless communication systems and apparatus described below. Furthermore, the invention is primarily described in the context of the 3GPP architecture reference model. However, it should be understood that, based on the disclosed information, those skilled in the art can readily make adaptations to use and implement aspects of the invention in 3GPP2 network architectures and other network architectures.

[0026] The exemplary wireless communication systems and apparatus described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communication, such as voice, data, etc. These systems may be based on Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), 3GPP Long Term Evolution (LTE) Radio Access, 3GPP Long Term Evolution Advanced (LTE-A) Radio Access, 3GPP2 Ultra Mobile Broadband (UMB), WiMAX, etc. 3GPP New Radio (NR) or some other modulation techniques.

[0027] Specifically, the exemplary wireless communication system apparatus described below may be designed to support one or more standards, such as those provided by an association called the "Third Generation Partnership Project" (referred to herein as 3GPP), including: [1] 3GPP TR 38.821 V16.0.0, "Solutions for NR to support non-terrestrial networks (NTN)"; [2] 3GPP TR22.865 V2.0.0, "Study on satellite access phase 3 (version 19)"; [3] 3GPP TR 23.700-29 V1.0.0, "Study on the integration of satellite components in 5G architecture; phase 3 (version 19)"; [4] 3GPP S2-2407191, "KI#2: Conclusion"; [5] 3GPP TS 23.501 V18.1.0, "System architecture for 5G systems (5GS)"; and [6] 3GPP RWS-230178, "NR and IoT NTN". The standards and documents listed above are hereby explicitly and completely incorporated in full.

[0028] Figure 1 A multiple access wireless communication system according to an embodiment of the present invention is illustrated. Access network 100 (AN) includes multiple antenna groups, one antenna group comprising 104 and 106, another antenna group comprising 108 and 110, and yet another antenna group comprising 112 and 114. Figure 1In this diagram, only two antennas are shown for each antenna group, but each antenna group may utilize more or fewer antennas. Access Terminal (AT) 116 communicates with antennas 112 and 114, which transmit information to AT 116 via forward link 120 and receive information from AT 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, which transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In an FDD system, communication links 118, 120, 124, and 126 may use different frequencies for communication. For example, forward link 120 may use a different frequency than the reverse link 118.

[0029] Each antenna group and / or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, each antenna group is designed to communicate with an access terminal in a sector of the area covered by access network 100.

[0030] In communications via forward links 120 and 126, the transmit antennas of access network 100 can utilize beamforming to improve the signal-to-noise ratio of the forward links for different access terminals 116 and 122. Furthermore, compared to an access network that transmits to all its access terminals via a single antenna, an access network using beamforming to transmit to access terminals randomly distributed throughout its coverage area typically causes less interference to access terminals in neighboring cells.

[0031] An AN can be a fixed station or base station used for communication with a terminal, and may also be referred to as an access point, Node B, base station, enhanced base station, eNodeB, or some other term. An AT can also be referred to as User Equipment (UE), wireless communication device, terminal, access terminal, or some other term.

[0032] Figure 2 This is a simplified block diagram of an embodiment of the transmitter system 210 (also referred to as the access network) and receiver system 250 (also referred to as the access terminal (AT) or user equipment (UE)) in the MIMO system 200. At the transmitter system 210, service data for several data streams is provided from the data source 212 to the transport (TX) data processor 214.

[0033] In one embodiment, each data stream is transmitted via a corresponding transmit antenna. The TX data processor 214 formats, decodes, and interleaves the service data of the data stream based on a specific decoding scheme selected for each data stream to provide decoded data.

[0034] OFDM technology can be used to multiplex the decoded data and pilot data for each data stream. The pilot data is typically a known data pattern processed in a known manner and can be used at the receiver system to estimate the channel response. The multiplexed pilot and decoded data for said data stream are then modulated (e.g., symbol mapping) based on a specific modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for each data stream to provide modulated symbols. The data rate, decoding, and modulation for each data stream can be determined by instructions executed by processor 230. Memory 232 is coupled to processor 230.

[0035] The modulation symbols of all data streams are then provided to the TX MIMO processor 220, which can further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then... T A modulation symbol stream is provided to N T Transmitters (TMTRs) 222a to 222t. In some embodiments, the TX MIMO processor 220 applies beamforming weights to symbols of the data stream and the antennas transmitting said symbols therefrom.

[0036] Each transmitter 222 receives and processes a corresponding symbol stream to provide one or more analog signals, and further modulates (e.g., amplifies, filters, and up-converts) the analog signals to provide a modulated signal suitable for transmission via a MIMO channel. Then, from N... T Antennas 224a to 224t transmit N from transmitters 222a to 222t. T A modulated signal.

[0037] At receiver system 250, by N R Each antenna 252a to 252r receives the transmitted modulated signal and provides the signal received from each antenna 252 to a corresponding receiver (RCVR) 254a to 254r. Each receiver 254 modulates (e.g., filters, amplifies, and down-converts) the corresponding received signal, digitizes the modulated signal to provide a sample, and further processes the sample to provide a corresponding "received" symbol stream.

[0038] The RX data processor 260 then uses specific receiver processing technology from N R Each receiver receives and processes N data. R A received symbol stream to provide N TEach detected symbol stream is then demodulated, deinterleaved, and decoded by the RX data processor 260 to recover the service data of the data stream. The processing performed by the RX processor 260 is complementary to the processing performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[0039] Processor 270 periodically determines which pre-decoded matrix to use (discussed below). Processor 270 formulates a reverse link message including the matrix index portion and the rank portion.

[0040] The reverse link message may include various types of information related to the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238 (which also receives service data from several data streams from the data source 236), modulated by the modulator 280, regulated by the transmitters 254a to 254r, and transmitted back to the transmitter system 210.

[0041] At transmitter system 210, the modulated signal from receiver system 250 is received via antenna 224, conditioned by receiver 222, demodulated by demodulator 240, and processed by RX data processor 242 to extract the reverse link message transmitted through receiver system 250. Next, processor 230 determines which pre-decoding matrix to use to determine beamforming weights and then processes the extracted message.

[0042] Memory 232 can be used to temporarily store some buffered / calculated data from processor 240 or 242 via processor 230, some buffered data from 212, or some specific program code. Furthermore, memory 272 can be used to temporarily store some buffered / calculated data from processor 260 via processor 270, some buffered data from 236, or some specific program code.

[0043] Turning Figure 3 This figure illustrates an alternative simplified functional block diagram of a communication device according to an embodiment of the present invention. Figure 3 As shown, this can be achieved using the communication device 300 in a wireless communication system. Figure 1The UE (or AT) 116 and 122 are used, and the wireless communication system is preferably an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 via the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by a user via the input device 302 (e.g., a keyboard or keypad) and can output images and sounds via the output device 304 (e.g., a display or speaker). The transceiver 314 is used to receive and transmit wireless signals to pass the received signals to the control circuit 306 and wirelessly output signals generated by the control circuit 306.

[0044] Figure 4 According to an embodiment of the present invention Figure 3 The diagram shows a simplified block diagram of program code 312. In this embodiment, program code 312 includes an application layer 400, a layer 3 portion 402, and a layer 2 portion 404, and is coupled to a layer 1 portion 406. Layer 3 portion 402 generally performs radio resource control. Layer 2 portion 404 generally performs link control. Layer 1 portion 406 generally performs physical connections.

[0045] For LTE, LTE-A, or NR systems, Layer 2, Part 404 may include the Radio Link Control (RLC) layer and the Media Access Control (MAC) layer. Layer 3, Part 402 may include the Radio Resource Control (RRC) layer.

[0046] Any two or more of the following paragraphs, (sub)bullets, points, actions or claims described in each paragraph or section of the invention may be logically, reasonably and appropriately combined to form a particular method.

[0047] Any sentence, paragraph, (sub)bullet, point, action, or claim described in each of the following invention paragraphs or sections can be implemented independently and separately to form a particular method or apparatus. The dependencies in the following invention disclosures (e.g., "based on," "more specifically," "example," etc.) are merely possible embodiments that do not limit the specific method or apparatus.

[0048] ***********************************************************

[0049] In 3GPP TR 38.821 ([1] 3GPP TR 38.821 V16.0.0), the study of NR NTN (non-terrestrial network) is introduced. NTN is defined as a network or network segment that uses airborne or spaceborne tools to access the relay nodes or base stations of the transmission equipment. [1] 3GPP TR 38.821 V16.0.0 also specifies further descriptions.

[0050] 4.1 Overview of Non-Terrestrial Networks

[0051] Non-terrestrial networks refer to networks or network segments that use RF resources on satellites (or UAS platforms).

[0052] The following depicts a typical scenario where a non-terrestrial network provides access to user equipment:

[0053] Figure 5 It is in 3GPP TR 38.821 V16.0.0 Figure 4 .1-1: Reproduction of a typical case of non-terrestrial networks based on transparent payloads.

[0054] Figure 6 It is in 3GPP TR 38.821 V16.0.0 Figure 4 .1-2: Reproduction of typical non-terrestrial network scenarios based on regenerative payloads.

[0055] Non-terrestrial networks typically have the following components:

[0056] - Connecting non-terrestrial networks to one or more satellite gateways in the public data network

[0057] - GEO satellites are fed by one or more satellite gateways deployed within the satellite's target coverage area (e.g., regional or even continental coverage). We assume that a UE in a cell is served by only one satellite gateway.

[0058] - For non-GEO satellites, service is provided sequentially by one or more satellite gateways. The system ensures continuity of service and feed links between continuously serving satellite gateways, and provides sufficient duration for mobility anchoring and handover.

[0059] - Feed link or radio link between the satellite gateway and the satellite (or UAS platform)

[0060] - A service link or radio link between user equipment and a satellite (or UAS platform).

[0061] - Satellites (or UAS platforms) can implement transparent or regenerative (with onboard processing) payloads. Satellite (or UAS platform) beam generation typically generates multiple beams over a given service area bounded by its field of view. The coverage area of ​​the beams is typically elliptical. The field of view of a satellite (or UAS platform) depends on the onboard antenna pattern and minimum elevation angle.

[0062] - Transparent payload: RF filtering, frequency conversion, and amplification. Therefore, the waveform signal repeated by the payload remains unchanged;

[0063] - Regenerated payload: RF filtering, frequency conversion and amplification, as well as demodulation / decoding, switching and / or routing, encoding / modulation. This is essentially equivalent to having all or part of the base station functionality on a satellite (or UAS platform) (e.g., gNB).

[0064] - Optionally, in the case of a satellite constellation, inter-satellite links (ISL). This will require a regenerable payload on the satellite. ISLs can operate in RF frequencies or optical bands.

[0065] - User equipment is served by satellites (or UAS platforms) within the target service area.

[0066] The following may list different types of satellites (or UAS platforms):

[0067] Table 4.1-1: Types of NTN Platforms

[0068]

[0069] generally

[0070] ●GEO satellites and UAS are used to provide services to the mainland, regions, or local areas.

[0071] ● LEO and MEO constellations are used to provide service in the Northern and Southern Hemispheres. In some cases, constellations can even provide global coverage, including the polar regions. For the latter, this requires a proper orbital inclination, sufficient beam generation, and inter-satellite links.

[0072] The HEO satellite system is not considered in this article.

[0073] [...]

[0074] 5.2 Regenerative Satellites Based on NG-RAN Architecture

[0075] 5.2.1 Effective load processed by gNB

[0076] 5.2.1.1 Overview

[0077] The NG-RAN logical architecture described in TS 38.401 serves as the baseline for the NTN scenario.

[0078] The satellite payload regenerates signals received from Earth.

[0079] ● NR-Uu radio interface on the service link between the UE and the satellite

[0080] ● Satellite Radio Interface (SRI) on the feed link between the NTN gateway and the satellite.

[0081] SRI (Satellite Radio Interface) is the transmission link between the NTN GW and the satellite.

[0082] Figure 7 It is in 3GPP TR 38.821V16.0.0 Figure 5 2.1-1: Reproduction of regenerated satellites without ISL or gNB processing payloads.

[0083] Note: Satellites can initiate additional service routing functions beyond the RAN range.

[0084] The satellite payload also provides inter-satellite links (ISL) between satellites.

[0085] Inter-Satellite Link (ISL) is a transmission link between satellites. An ISL can be a radio interface or an optical interface, and it can be defined by 3GPP or non-3GPP standards, but this is outside the scope of this research project.

[0086] The NTN GW is a transport network layer node and supports all required transport protocols.

[0087] Figure 8 It is in 3GPP TR 38.821V16.0.0 Figure 5 2.1-2: Reproduction of regenerated satellites with payloads that have ISL and gNB processing.

[0088] The diagram above shows how a UE served by a gNB on a satellite can access a 5GCN via ISL.

[0089] gNBs on different satellites can connect to the same 5GCN on the ground.

[0090] If a satellite carries more than one gNB, then the same SRI will transmit all corresponding NG interface instances.

[0091] [...]

[0092] 5.2.2 Payload processed by gNB-DU

[0093] 5.2.2.1 Overview

[0094] The NG-RAN logical architecture with CU / DU partitioning described in TS 38.401 serves as the baseline for the NTN scenario.

[0095] The satellite payload regenerates signals received from Earth.

[0096] ● NR-Uu radio interface on the service link between the satellite and the UE

[0097] ● Satellite Radio Interface (SRI) on the feed link between the NTN gateway and the satellite. SRI transmits the F1 protocol.

[0098] Satellite payloads can provide inter-satellite links between satellites.

[0099] SRI (Satellite Radio Interface) are transmission links; their logical interface F1 is specified by 3GPP.

[0100] The NTN GW is a transport network layer node and supports all required transport protocols.

[0101] DUs on different satellites can connect to the same CU on the ground.

[0102] If a satellite carries more than one DU, then the same SRI will transmit all corresponding F1 interface instances.

[0103] Figure 9 It is in 3GPP TR 38.821 V16.0.0 Figure 5 2.2-1: Reproduction of NG-RAN with gNB-DU-based regenerable satellites.

[0104] ***********************************************************

[0105] Store and forward (S&F) operation is described in 3GPP TR 22.865 ([2] 3GPP TR 22.865 V2.0.0). S&F is an operating mode for 5G systems with satellite access, in which the 5G system can provide a certain level of service (store and forward data) when the satellite connection is intermittent / temporarily unavailable, such as providing communication services to UEs under satellite coverage without the feed link connection to the ground segment being active at the same time.

[0106] [2] 3GPP TR 22.865V2.0.0 also specifies more details, including use cases and potential requirements for S&F operations:

[0107] Appendix A (Informative):

[0108] Store and forward satellite operations

[0109] Store-and-forward satellite operations in 5G systems with satellite access are designed to provide a level of communication service for UEs under satellite coverage with intermittent / temporary satellite connections (e.g., when the satellite is not connected to the terrestrial network via a feed link or ISL) to provide latency-tolerant communication services.

[0110] An example of “S&F satellite operation” is shown in Figure A-1, in contrast to the “normal / default satellite operation” assumption that can currently be considered as a 5G system with satellite access.

[0111] As shown in Figure A-1:

[0112] - In the "Normal / Default Satellite Operation" mode, the signaling and data service exchange between the UE with satellite access and the remote terrestrial network requires both the service link and the feed link to be active simultaneously, so that when the UE interacts with the satellite through the service link, there is a continuous end-to-end connection path between the UE, the satellite and the terrestrial network.

[0113] In contrast, in "S&F Satellite Operation" mode, the end-to-end exchange of signaling / data services is now handled as a combination of two steps that are not simultaneous (steps A and B in Figure A-1). In step A, signaling / data exchange occurs between the UE and the satellite without the satellite simultaneously being connected to the terrestrial network (i.e., the satellite can operate the service link without an active feed link connection). In step B, a connection is established between the satellite and the terrestrial network, enabling communication between them. Therefore, the satellite moves from connecting to the UE in step A to connecting to the terrestrial network in step B.

[0114] Figure 10 This is a reproduction of Figure A-1 in 3GPP TR 22.865V2.0.0: a diagram illustrating the “Normal / Default Operation” and “S&F Operation” modes in a 5G system with satellite access.

[0115] The concept of “S&F” services is widely used in the fields of delay-tolerant and interruption-tolerant networks. In the 3GPP context, the service that can be assimilated as an S&F service is SMS. For SMS, there is no need for an end-to-end connection between endpoints (e.g., one endpoint can be a UE and the other endpoint can be an application server), but only an end-to-end connection between the endpoint and the SMSC, which acts as an intermediate node responsible for storage and dependencies.

[0116] S&F satellite operations support is particularly suitable for NGSO satellite delivery delay-tolerant / non-real-time IoT satellite services.

[0117] ***********************************************************

[0118] In 3GPP TR 23.700-29 ([3] 3GPP TR 23.700 to 29 V1.0.0), the key issues, candidate solutions and conclusions of S&F are specified:

[0119] 5.2 Key Issue #2: Support for Store-and-Forward Satellite Operations

[0120] 5.2.1 Description

[0121] S&F satellite operations are particularly well-suited for delivery delay-tolerant / non-real-time satellite services (i.e., CIoT / MTC, SMS). To support S&F satellite operations for such services, the following research is proposed:

[0122] -If applicable, what minimum set of essential core network components / network functions should be placed on the satellite to provide the intended services;

[0123] - Whether and how to trigger S&F satellite operations, and how to perform S&F satellite operations;

[0124] - What enhancements are needed to the relevant UE and network procedures to support S&F satellite operation, including:

[0125] - Whether to notify the UE when applying S&F satellite operations.

[0126] Note 1: S&F for IoT NTN will be studied first, and NR NTN can be studied if there is still time remaining.

[0127] Note 2: Coordination with SA3-LI is required regarding LI.

[0128] Note 3: Candidate solutions need to indicate which services they are addressing (CIoT CP optimization, CIoT UP optimization, SMS).

[0129] [...]

[0130] Solution 6.12 #12: S&F for Multi-Satellite Deployment via Anchored Ground MME

[0131] 6.12.1 Description

[0132] For control plane management of registration and connection management procedures, we recommend installing an eNB and MME on the satellite.

[0133] The principle behind the solution is as follows:

[0134] 1. The terrestrial MME is an anchor node located in the terrestrial network and possesses the UE context. The terrestrial MME synchronizes the UE context with all airborne MMEs.

[0135] 2. The eNB and airborne MME are located on the satellite, thus providing basic connectivity management procedures. The airborne MME and UE perform all procedures, without needing to interact with other core network nodes on the ground when the service link is available.

[0136] 3. Whenever a program needs to interact with a ground core network node, the airborne MME stores it when the feed link is unavailable and forwards the corresponding message to the ground MME when the feed link is available. The ground MME and the ground network node execute the program and synchronize the UE context with the airborne MME or send the response message back to the airborne MME.

[0137] 4. The ground MME first receives any downlink signaling messages and forwards them to the airborne MME (when the feed link is available). The airborne MME can then page the UE (when the serving link is available) and deliver the corresponding message / execute procedures with the UE.

[0138] 5. To reduce the number of iterations, if the terrestrial MME is trustworthy, authentication information and subscription data acquisition (i.e., updating location and ack) will be performed together before authenticating the UE. Whether such a procedure is allowed is determined by the HSS. If the HSS does not allow this combined procedure to complete the attach procedure, then at least two interactions with the terrestrial network are required: a) to obtain the authentication vector; b) to obtain the subscription data after performing the authentication procedure in the first iteration.

[0139] 6. GUTI management, periodic registration management, and how the UE identifies whether it is allowed to register S&F are described in the program section.

[0140] 7. The process is illustrated using satellite 1 and satellite 2 as examples. However, the system can deploy "n" satellites in the same process (or program).

[0141] 6.12.2 Procedure

[0142] Figure 11 It is in 3GPP TR 23.700-29V1.0.0 Figure 6 .12.2-1: Reproduction of attachments without PDN connectivity.

[0143] The eNB and airborne MME are assumed to be located on the satellite, with a ground MME that acts as the anchor point for the satellite MME.

[0144] Perform the attachment procedure described in Section 5.3.2.1 of TS23.401[5] and make the following modifications.

[0145] At time T0 (i.e., when the service link is available but the feed link connectivity is unavailable).

[0146] 1) In step 1, if the UE recognizes that the current serving cell supports S&F mode and the UE is allowed to use S&F (see section 6.12.3.1.2), then the UE sends an attach request message to the network.

[0147] 2) Perform the steps in section 5.3.2.1 of TS23.401[5] between the user and the UE until step 4.

[0148] 3) The onboard MME sends a NAS message (partial attach accept, which may be unprotected) to the UE, instructing the UE that the attached request message sent is stored by the onboard MME, and the network will reach the UE after the onboard MME obtains the UE's authentication and subscription details from the terrestrial network. The partial attach accept includes a temporary GUTI (even though the UE is not registered with the network) and a wait timer for the UE to wait for the network to send a paging message. Before the wait timer runs, the UE will not select any other network to provide store-and-forward services. While the wait timer is running, the UE can select another network that can provide normal service (if available). The MME stores the UE's service area.

[0149] 4) The UE receives the attach accept message. The UE will not trigger the attach request again until it receives a paging message or the waiting timer expires.

[0150] Editor's Note: Security issues related to authentication failures in steps 1-4 need to be addressed (e.g., denial-of-service attacks, fake BS attacks).

[0151] At time T1 (i.e., when the service link is unavailable and the feed link connectivity is available).

[0152] 5) The airborne MME selects the ground MME (see section 6.12.3.1.3). The airborne MME forwards the stored attach request message and UE service area to the ground MME.

[0153] 6) Step 5 is performed between the ground MME and the HSS, that is, the ground MME obtains the authentication vector and other details from the HSS.

[0154] 7) Perform steps 8 & 11. That is, update the location using the HSS, and the updated location ACK is received by the ground MME. That is, all subscription details are retrieved by the ground MME. The MME instructs the S&F to the HSS to retrieve S&F-specific subscription details (if they exist), and indicates that it is pre-fetching subscription data without authenticating the UE.

[0155] 8) The ground MME synchronizes the UE information it retrieves with the airborne MME. For optimization purposes, the airborne MME can be any airborne MME that will serve the UE next.

[0156] At time T2 (i.e., when the service link is available but the feed link connectivity is unavailable).

[0157] 9) When entering the UE service area, the onboard MME will use the assigned GUTI in the partial attach receive message to page the UE.

[0158] 10) Upon receiving a paging message, the UE retransmits the attach request message.

[0159] Editor's Note: Further research is needed on recovery from paging UE failures.

[0160] 11) The onboard MME performs step 5 of the authentication and security procedures with the UE. Once the authentication procedure is successful, the system will perform the remaining steps to complete the attachment procedure with the UE. The onboard MME also provides the UE with an S&F policy, which includes a UE context activation timer. The UE starts the UE context activation timer after receiving the NAS message, and the UE should consider itself to have registered with the network when this timer expires. Based on available subscription data, the MME can send a rejection message to the UE before or after performing the authentication / security procedures.

[0161] At time T3 (i.e., when the service link is unavailable and the feed link connectivity is available).

[0162] 12) The airborne MME indicates to the ground MME whether the UE has successfully registered or whether the registration procedure has been successful. If the registration procedure is successful, the airborne MME will synchronize the UE context with the ground MME.

[0163] 13) The ground MME sends an updated location to the HSS, indicating whether the UE has been successfully authenticated or not. This means that the HSS does not need to subscribe to data in response.

[0164] 14) If a UE context is created or modified in any airborne MME, it will be synchronized with all airborne MMEs when they connect to the terrestrial network. The deployment should handle the synchronization of UE contexts with all satellites, and this process should not exceed the UE context activation timer.

[0165] Editor's Note: After the UE context is changed in the onboard MME, the UE must wait for the new UE context to be transferred to other satellites before it can reconnect to the satellite. How to manage this requires further research.

[0166] 15) After the UE context activation timer expires, the UE enters the EMM-REGISTERED state.

[0167] 6.12.2.1.1 Periodic Timers and Mobile Reachability Timers

[0168] The Mobile Reachability Timer (MRT) operates only at the ground MME. Each time the UE enters connection mode with any airborne MME, the airborne MME notifies the ground MME, and then the ground MME restarts the MRT timer.

[0169] A mobile reachability timer value must be added to the network to account for the delay in receiving information from the onboard MME after the UE enters connected mode (in the case of PTAU procedures).

[0170] For example, the mobile reachability timer = the PTAU timer for the UE + the maximum potential delay in the connection between the airborne MME and the ground MME after the UE enters connected mode (including the PTAU procedure).

[0171] Each airborne MME runs an MME-UE-context airborne timer. When the timer expires, the airborne MME synchronizes the UE context with the ground MME.

[0172] 6.12.2.1.2 How does the UE identify whether it is allowed to attach to the network for S / F?

[0173] If the UE determines that there are no other networks that can provide normal service, then the UE can choose to attach in store-and-forward mode. Similar to the CAG mechanism available in 5GS, we recommend that the UE be configured to use S&F information. If the configured S&F ID is broadcast along with an indication that S / F mode is supported (i.e., the feed link is unavailable), then the UE will attach to the network in S&F mode. If the UE is not configured to use an S&F ID, and the serving network broadcasts S&F support (i.e., the feed link is unavailable), then the UE can attempt to attach to register and receive an allowed S&F ID from the network.

[0174] 6.12.2.1.3 GUTI Management and MME Selection

[0175] The GUTI is assigned to the UE only by the ground MME, and this ground MME is stored together with all onboard MMEs in the UE context. The onboard eNB selects the onboard MME:

[0176] a) Based on the ability to maintain a common MME group ID across all airborne MMEs, these airborne MMEs can provide services to the UE based on the UE's service area and ground-based MMEs; or

[0177] b) The following range of MME IDs are expected to be identical in selection. That is, if the eNB receives an MME-ID (during RRC connection establishment), it can select any MME for its connection from the MME ID range;

[0178] c) The eNB will follow the current mechanism to select the airborne MME, and it may consider the S&F indication in the RRC signaling procedure.

[0179] 6.12.2.1.4 Ground MME Selection Performed by Airborne MME

[0180] When the UE first attaches to the network, the airborne MME selects the ground MME.

[0181] Airborne MMEs should follow the same selection mechanism as eNBs in version 18 for selecting ground MMEs.

[0182] Assume that the airborne MME supports all the features supported by the ground-based MME.

[0183] Once a GUTI is assigned to the ground MME, the airborne MME can uniquely identify it. The airborne MME is configured to connect to all ground station IDs that can reach the ground MME. During the UE attachment procedure, this information is provided to all airborne MMEs, and the successful UE context is synchronized.

[0184] The terrestrial MME is configured to use potential airborne MMEs that can provide services to the UE based on the UE's service area. The terrestrial MME is configured locally to use this information, or it can be configured by the O&M or AF (via the SCEF path).

[0185] 6.12.2.1.5 Acquisition of authentication / subscription details during any other process

[0186] The above-mentioned concept of partial attachment acceptance applies if the network decides to perform the authentication procedure / retrieve subscription details at any time (e.g., during the execution of a service request procedure). That is, the NAS message indicates to the UE that the network has stored the uplink message, and the network will return it to the UE once the UE authentication / subscription details are obtained from the terrestrial network.

[0187] 6.12.2.1.6 Attachment of multiple satellites with PDN connectivity

[0188] Assume that gNB, MME, S-GW and P-GW are located on a satellite.

[0189] Assumption 1: If we assume that PCRF is not needed, since the PCC strategy may be configured in the P-GW airborne satellite, and the communication is for delay-tolerant devices, then specific or very minor strategies may not be required.

[0190] Assumption 2: In cases where dynamic PCC deployment is required, it is also assumed that the PCRF is located on a satellite.

[0191] Therefore, no changes are expected beyond the above process. This is because the P-GW / S-GW / PCRF can be used to interact with the MME on the satellite to establish a PDN connection.

[0192] Similar to the ground-based MME, there is P-GW-Ground, S-GW-Ground, and UE context synchronization.

[0193] Editor's Note: Any other enhancements required for handling data transmission or airborne core network entities require further investigation.

[0194] 6.12.3 Impact on services, entities, and interfaces

[0195] a) The terrestrial MME is an anchor node located in the terrestrial network and possesses the UE context. The terrestrial MME synchronizes the UE context with all airborne MMEs.

[0196] b) Both the eNB and the airborne MME are located on satellites. Therefore, they can provide basic connectivity management procedures with the UE. The airborne MME performs all procedures with the UE, which does not need to interact with other core network nodes on the ground when a service link is available.

[0197] c) Whenever a program needs to interact with a ground core network node, the airborne MME stores it when the feed link is unavailable and forwards the corresponding message to the ground MME when the feed link is available. The ground MME and the ground network node execute the program and synchronize the UE context with the airborne MME or send a response message back to the airborne MME.

[0198] d) GUTI management, periodic registration management, and how the UE identifies whether it is allowed to register S&F are described in the program section.

[0199] [...]

[0200] 8.2 KI#2 Conclusion: Support for Store-and-Forward Satellite Operations

[0201] Note 1: Whether a satellite has a full CN or segmented MME architecture depends on the operational deployment.

[0202] Note 2: Security issues (if any) of these conclusions fall within the scope of SA WG3.

[0203] Note 3: The LI problem (if it exists) of these conclusions is within the scope of SA WG3-LI.

[0204] Note 4: Deployment must comply with regulatory requirements.

[0205] Agree to the following options to support storage and forwarding operations in a segmented MME architecture, and adhere to the following (informative) principles:

[0206] 1) In a split MME architecture, the HSS is on the ground.

[0207] 2) The MME function is divided into two parts: airborne MME - the MME part located on the satellite, and terrestrial MME - the MME part located on the terrestrial network and whose interface is not within the scope of 3GPP.

[0208] 3) MO data is stored in the onboard MME when the serving link is available but the feed link is unavailable, and is transmitted to the ground when the feed link becomes available. MT data is stored in the ground MME or S-GW when the feed link is unavailable, and is transmitted to the onboard MME when the feed link becomes available. MT data is stored in the onboard MME when the feed link is available but the serving link is unavailable, and is transmitted to the UE when the serving link becomes available. All types of data services (e.g., IP, etc.) can be supported and transmitted using existing user plane and control plane procedures defined in the EPS.

[0209] 4) For MO SMS, after receiving MO SMS, the onboard MME stores MO-SMS and can then send a delivery report (i.e., RP-ACK) to the UE, as if the MO-SMS had been successfully delivered to the service center (SC).

[0210] It has the following normative effects:

[0211] 1) When the feed link is unavailable and the network supports S&F operation, the network will be able to notify the UE whether to apply S&F satellite operation (e.g., the eNB broadcasts support for S&F operation as part of the system information).

[0212] Note 1: The triggers for eNB broadcasting S&F operations are based on RAN WG decisions. From a system perspective, the expectation is that if the network does not support S&F operations and the feed link is unavailable, the eNB will shut down and not broadcast any signals.

[0213] 2) When a UE initiates an attach or TAU procedure, it will indicate to the MME, based on existing NAS capabilities, that it supports S&F mode. If these procedures cannot be completed due to S&F operation, the MME will send an attach or TAU rejection message to the UE. The attach or TAU rejection message includes:

[0214] a) Indicates that the UE is unable to complete the attach or TAU procedure due to S&F operation and that the UE can retry the attach or TAU with new information in this PLMN during the next satellite transfer. This indicates to the UE that the information contained in the attach or TAU request message is stored by the MME and will be available to the UE after interaction with the terrestrial network.

[0215] b) Waiting timer: Indicates to the UE the time to wait before retrying the attach / TAU procedure on another satellite in the current or same PLMN.

[0216] c) Optionally, after the wait timer expires, the UE can use the list of satellite IDs from which it retryes the attach / TAU procedure. The satellite IDs are based on SIB information broadcast by the eNB.

[0217] 3) How the UE processes this information depends on the UE implementation plan. During the waiting timer period, the UE can search for another ground or satellite PLMN to obtain normal service.

[0218] 4) The MME can indicate a "request time" to the HSS, allowing the HSS to check that no other (e.g., ground) MME has sent an update location request after the "request time," and to obtain the authentication vector and other details from the HSS according to the current authentication and security procedures. The MME can trigger an update location with the HSS, and the update location ACK is received by the MME; that is, all subscription details are retrieved by the ground MME. The update location request includes an indication that this location update is temporary; that is, the HSS must not consider the UE to be registered until it receives the final update location request.

[0219] 5) When the waiting timer given to the UE in step 2 expires, if the UE has not successfully attached to another PLMN and the UE finds that the cell with the broadcast satellite ID is valid, it can retry the attachment procedure. Then the UE will resend the attach or TAU request message.

[0220] 6) During the attachment or TAU procedure with the UE, the MME can also provide the UE with a list of satellite IDs through which the UE can exchange signaling and data, as well as a waiting timer that indicates to the UE how long it should wait before attempting to exchange signaling and data with these satellites.

[0221] 7) The MME can indicate the estimated delivery time to the UE in a NAS message (Attach Accept, TAU Accept, or Service Accept). How the UE uses this information depends on the UE implementation scheme.

[0222] Note 2: The estimated delivery time is the estimated time from the UE to send data to the gateway.

[0223] 8) The core network can indicate to the external SCS / AS whether the UE is registered in S&F mode and the estimated delivery time.

[0224] Note 3: Whether any existing monitoring events or procedures can be used or enhanced to achieve the above objectives will be determined during the specification phase.

[0225] Note 4: SA WG2 will be further modified according to the protocols in SA WG3, such as security procedures and attachment / TAU procedures.

[0226] The segmented MME architecture will be described in the informative appendix.

[0227] Agree to the following options to support CN-wide store-and-forward operations on satellites, and adhere to the following (informational) principles:

[0228] Each satellite has a complete CN including eNB, MME, SGW, PGW, HSS, E-SMLC, SMSC, etc. Agents are deployed on satellites and ground for application services, including support for MT services, MO services, SMS, etc.

[0229] - Implementations of proxies and the interfaces between them are not within the 3GPP scope.

[0230] -The UE attaches, transmits data (e.g., SMS, MO, and MT data) and detaches from each satellite as needed and as determined by the listening list.

[0231] Note 5: MT services are delivered to the UE after the UE performs attach.

[0232] Note 6: After moving from an S&F operation, MT services may get stuck in the ground agent and will only be retrieved when the UE returns to the S&F operation.

[0233] For MT services, the UE attaches to the satellite and allows MO services to be delivered from the user or an application on the UE. Depending on the implementation, the UE may first wait for instructions from the user or an application on the UE regarding pending MT services before performing the attach, or it may wait based on its knowledge of when the MT service will arrive.

[0234] - Depending on the deployment and implementation scheme (i.e., not within the 3GPP scope in this version), the HSS on the satellite can be populated with subscription data for UEs that can access the satellite only or for all UEs that can access the satellite.

[0235] - Depending on the deployment, the UE can have a USIM enhanced for IOPS or a USIM dedicated to satellite networks.

[0236] Note 7: The solution does not support the roaming architecture defined in TS23.501[2] or TS23.401[5].

[0237] It has the following normative effects:

[0238] - Storage and forwarding are only supported by EPS.

[0239] - Optionally, the MME provides the UE with a S&F listener list of satellite IDs during attach / TAU. The UE uses satellites in the S&F listener list to communicate with the CN for MO / MT data / signaling. The S&F listener list can be determined by the CN. How the network determines the S&F listener list is not within the scope of this version of the 3GPP specification.

[0240] Note 8: The S&F listening list can help the UE retrieve MT data.

[0241] - The UE needs to know that the satellite supports S&F mode.

[0242] Note 9: How the UE knows that the satellite supports S&F operating mode depends on the RAN.

[0243] - If the satellite is unable to support the UE at this time, the UE may be rejected. Attach rejection can provide a timer for how long the UE should wait before retrying, as well as a list of S&F listeners the UE can retry attaching to.

[0244] ***********************************************************

[0245] A non-terrestrial network (NTN) can be viewed as a network that provides non-terrestrial access to user equipment (UE), for example, through an NTN payload and NTN gateway mounted on an airborne or spaceborne NTN vehicle. An NTN may include one or more network nodes, such as a Next Generation Radio Access Network (NG-RAN) node or a Next Generation Node B (gNB). UEs may link to, reside in, and / or connect to an NTN network for transmitting and / or receiving.

[0246] NTN can include various platforms, including Low Earth Orbit (LEO) satellites, Medium Earth Orbit (MEO) satellites, Highly Elliptical Orbit (HEO) satellites, Geostationary Orbit (GEO) satellites, Geostationary Geosynchronous Orbit (GSO) satellites, Non-Geostationary Geosynchronous Orbit (NGSO) satellites, and / or High Altitude Communication Platforms (HAPS). LEO satellites can have a fixed Earth beam (e.g., a beam temporarily fixed at a location for a period of time) or a moving Earth beam (e.g., a beam that moves continuously with the satellite). LEO satellites can serve / provide services to moving Earth cells (e.g., with a fixed Earth beam) and / or (quasi) fixed Earth cells (e.g., with a moving Earth beam).

[0247] NTN can provide wide-area coverage and network (NW) access in situations where terrestrial networks (TN) are not feasible (e.g., in deserts, polar regions, and / or on aircraft). More details about the different NTN platforms can be found in [1] 3GPP TR38.821V16.0.0.

[0248] Store and forward (S&F) operation can be viewed as an operating mode of satellite access that provides a certain level of service (while storing and forwarding data) when satellite connectivity is intermittent / temporarily unavailable. For example, it can provide communication services to UEs within satellite coverage without simultaneously establishing an active feed link connection with the ground segment.

[0249] Networks supporting S&F operations may be based on a regenerated payload architecture (e.g., as specified in [1] 3GPP TR38.821 V16.0.0). The network may include a Radio Access Network (RAN) and / or a Core Network (CN). The RAN may include one or more RAN nodes. The CN may include one or more CN nodes. The RAN (or RAN nodes) may be (or include) NG-RAN nodes, gNBs, gNB Distributed Units (DUs), gNB Central Units (CUs), Evolved Universal Terrestrial Radio Access Network (E-UTRAN) nodes, Evolved Node Bs (eNBs), and / or base stations. A CN (or CN node) may be (or include) an evolved packet core (EPC), a mobility management entity (MME), a serving gateway (S-GW), a 5G core (5GC), a user plane function (UPF), an access and mobility management function (AMF), a session management function (SMF), a home subscriber server (HSS), and / or a network node specified in TS23.501 ([5] 3GPP TS23.501V18.1.0).

[0250] A network (e.g., a 5G system) can be divided into (at least) two parts. One part of the network includes one or more network nodes or network segments located on a satellite. The other part of the network includes one or more network nodes or network segments located on the ground, not on a satellite. Network nodes and / or network segments can be one or more network nodes (e.g., RAN nodes or CN nodes) and / or combinations of some and / or network nodes, whether mentioned above or not. For simplicity, a network, network node, and / or network segment located on a satellite (or the relevant network mentioned above) can be referred to as a satellite-based NW (or satellite NW). A network, network node, and / or network segment located on the ground (or the relevant network mentioned above) can be referred to as a terrestrial NW (or terrestrial NW).

[0251] For example, a satellite NW can be (or include) a RAN (e.g., NG-RAN, gNB, and / or eNB). A terrestrial NW can be (or include) a CN (e.g., EPC, 5GC, MME, S-GW, AMF, and / or UPF). For example, a satellite NW can be (or include) a gNB-DU. A terrestrial NW can be (or include) a gNB-CU and / or one or more CN nodes (e.g., AMF, UPF). For example, a satellite NW can be (or include) a RAN (e.g., NG-RAN, gNB, and / or eNB) and / or one or more CN nodes (or segments) (e.g., AMF, UPF, MME, S-GW). A terrestrial NW can be another / other one or more CN nodes (or segments) (e.g., portions not containing a satellite NW).

[0252] The link / connection / interface between a satellite NW and a terrestrial NW can be called a feed link. The link / connection / interface between a satellite NW and a UE can be called a service link. Examples are shown in... Figure 12 As shown in the image.

[0253] Based on the candidate solutions and / or conclusions of S&F specified in [3] 3GPP TR 23.700-29V1.0.0, when (or in response to) the UE initiating an attach or tracking area update (TAU) procedure (e.g., for S&F) and / or transmitting an attach request or TAU request, the UE may receive a response message containing a configuration of a waiting time (or a waiting timer). The UE may start a waiting timer based on the configuration. While the waiting timer is running, the UE should not attempt to access the (same) network (at least for S&F). While the waiting timer is running, the UE may search for another public land mobile network (PLMN) (e.g., to obtain normal service). When the waiting timer expires, if the UE has not successfully attached to another PLMN, then the UE should retry the attach or TAU procedure and / or (re)transmit the attach request or TAU request (e.g., for S&F).

[0254] However, if the UE determines whether it has successfully attached to another PLMN after the waiting timer expires, then the UE may have already found another PLMN and initiated an attach / TAU procedure (e.g., to obtain normal service) before the procedure has successfully completed by the timer expires. The procedure may be in progress while the waiting timer expires. In this case, it is not appropriate to immediately retry the attach or TAU procedure with the original network (e.g., for S&F). Retrying the attach or TAU procedure with the original network (e.g., for S&F) may not be the best option, as the UE may lose the opportunity to obtain normal service. An example of this problem is... Figure 14 As shown in the diagram. Furthermore, while the waiting timer is running, the UE may find a cell within the same PLMN that provides normal service, and if the found cell does provide normal service, retrying the original network (e.g., for S&F) is not the best option.

[0255] To at least resolve this problem, at least one or more of the methods, aspects, embodiments, and concepts described below may be considered.

[0256] The UE can initiate a first procedure (e.g., to a first network). The first procedure can be for S&F operations. The first procedure can be (or include) an attach procedure. The first procedure can be (or include) a Tracking Area Update (TAU) procedure. The first procedure can be (or include) a registration procedure. The first procedure can be (or include) a service request procedure. Examples of first procedures are in Figure 13 As shown in the image.

[0257] The UE may, for example, transmit a first message (e.g., a request message) to the network (e.g., a first network) during a first procedure. The first message may (at least) indicate that the UE supports S&F operation. The first message may (at least) indicate that the UE requests S&F operation. The first message may (at least) indicate a request within S&F operation. The first message may be (or include) a request message of the first procedure. The first message may be (or include) an attach request. The first message may be (or include) a TAU request. The first message may be (or include) a registration request. The first message may be (or include) a service request.

[0258] The UE may, for example, receive a second message (e.g., a response message) from a network (e.g., a first network) in response to transmitting a first message during a first procedure. The second message may (at least) indicate that the network supports S&F operation. The second message may (at least) indicate that the network enables (or activates / starts) S&F operation. The second message may (at least) indicate that the first message is stored at the (satellite) network, and / or that the first message will subsequently (e.g., when the feed link is available) be transmitted (or forwarded) to the terrestrial network. The second message may (at least) indicate that the network will subsequently (e.g., after the network receives a response from the terrestrial network) respond to the UE. The second message may be (or include) an accept message. The second message may be (or include) a reject message. The second message may be (or include) a partially accept message. The second message may be (or include) a partially reject message.

[0259] The waiting time (configuration) can be included in the second message. The waiting time can indicate the duration the UE should wait for a network response (e.g., a paging from the network). The waiting time can indicate the duration the UE is prohibited from triggering (or initiating) the first procedure (and / or transmitting the first message) to the network (e.g., the first network) (e.g., for S&F). The waiting time can be (or include) a duration (or period). The waiting time can be a time reference (or time point).

[0260] The UE may initiate a first timer (e.g., a wait timer) based on the aforementioned wait time. The first timer may be started by setting a value for the wait time. The first timer may be started in response to receiving the wait time (configuration) (and / or a second message). The first timer may be a wait timer. The first timer may be a Non-Access Stratum (NAS) timer. The first timer may be used for S&F operations. The first timer may be used to control when the UE should retry the first procedure. The first timer may be used to control the duration the UE should wait before retrying the first procedure.

[0261] While the first timer is running, the UE may be prohibited (or not allowed) from initiating (or triggering) the first procedure (and / or transmitting the first message) to the (same) network (e.g., for S&F). While the first timer is running, the UE may be prohibited (or not allowed) from selecting another network (e.g., a second network) for S&F operation. While the first timer is running, the UE may be allowed to select another network for normal service.

[0262] A list of satellite identifiers (IDs) may be included in the second message (e.g., along with the waiting time). The satellite ID list may indicate satellites for which the UE can retry the first procedure (and / or retransmit the first message) after the first timer expires (or after expiration / when expiration / if expiration / in response to expiration). The satellite ID list may also indicate satellites for which the UE cannot retry the first procedure (and / or retransmit the first message) while the first timer is running. Finally, the satellite ID list may indicate satellites for which the UE can exchange data or signaling restricted by the first timer.

[0263] When the first timer expires (or after it expires / if it expires / after it expires / in response to it), the UE may again initiate (or trigger) the first procedure (and / or transmit the first message) to the network (e.g., the first network), for example, for S&F operations. When the first timer expires (or after it expires / if it expires / after it expires / in response to it), the UE may be permitted to again initiate (or trigger) the first procedure (and / or transmit the first message) to the network (e.g., the first network), for example, for S&F operations.

[0264] The UE is capable of using S&F operations. The network is capable of providing S&F operations.

[0265] While the first timer is running, the UE can initiate a second procedure (e.g., to a second network). The UE can initiate a second procedure in response to the UE (determining) (re)selecting another network (e.g., a second network) (or connecting to / attaching to / registering with / subscribing to services on another network) (or when (determining) (re)selecting / after (determining) (re)selecting / if (determining) (re)selecting / due to (determining) (re)selecting), for example, for normal service.

[0266] The second procedure can be used for normal service. The second procedure can be the same as the first procedure. The second procedure can be different from the first procedure. The second procedure can be (or include) an attachment procedure. The second procedure can be (or include) a TAU procedure. The second procedure can be (or include) a registration procedure. The second procedure can be (or include) a service request procedure.

[0267] The UE may, for example, transmit a third message (e.g., a request message) to the network (e.g., a second network) during the second procedure. The third message may (at least) instruct the UE to request normal service (e.g., excluding S&F operations). The third message may (at least) instruct a request within normal service (e.g., excluding S&F operations). The third message may be (or include) a request message from the second procedure. The third message may be (or include) an attach request. The third message may be (or include) a TAU request. The third message may be (or include) a registration request. The third message may be (or include) a service request.

[0268] The UE may receive a fourth message (e.g., a response message) from the network (e.g., a second network) in response to the transmission of a third message, for example, during the second procedure. The fourth message may (at least) instruct the network to enable (or activate / start) normal service (e.g., in addition to S&F operation). The fourth message may be (or include) an accept message. The fourth message may be (or include) a reject message.

[0269] When the UE (determines) (re)selects another network (e.g., a second network) (or connects to another network / attaches to another network / registers with another network / subscribes to a service with another network) (or after (determines) (re)selects / if (determines) (re)selects / in response to (determines) (re)selects), for example, if the first timer is running, the UE can stop the first timer.

[0270] When the UE initiates a second procedure (or after initiation / if initiation / in response to initiation), for example, if (at least) the first timer is running, the UE can stop the first timer.

[0271] When the UE transmits a third message (or after transmission / if transmission / in response to transmission), for example, if (at least) the first timer is running, the UE can stop the first timer.

[0272] When the UE receives the fourth message (or after / if received / in response to receiving), for example, if the first timer is running (at least), the UE can stop the first timer.

[0273] When the UE completes (or terminates) the second procedure (or after completion (or termination) / if completion (or termination) / in response to completion (or termination)), for example, if (at least) the first timer is running, the UE can stop the first timer. The second procedure can complete (or terminate) successfully. The second procedure can fail to complete (or terminate).

[0274] When (or once / if / in response to) the UE successfully executes or completes the second procedure, the UE may stop the first timer if (at least) the first timer is running.

[0275] When the UE cancels (or aborts) the second procedure (or after cancellation (or aborts) / if cancellation (or aborts) / in response to cancellation (or aborts)), for example, if the first timer is running, the UE can stop the first timer.

[0276] Examples of solutions are in Figure 15 As shown in the image.

[0277] When the UE (determines) (re)selects another network (e.g., a second network) (or connects to another network / attaches to another network / registers with another network / subscribes to a service with another network) (or after (determines) (re)selects / if (determines) (re)selects / in response to (determines) (re)selects), for example, if the first timer is running, the UE can pause the first timer.

[0278] When the UE initiates a second procedure (or after initiation / if initiation / in response to initiation), for example, if (at least) the first timer is running, the UE can pause the first timer.

[0279] When the UE transmits a third message (or after transmission / if transmission / in response to transmission), for example, if (at least) the first timer is running, the UE can pause the first timer.

[0280] When the UE receives the fourth message (or after / if received / in response to the reception), for example, if (at least) the first timer is running, the UE can pause the first timer.

[0281] When the UE completes (or terminates) the second procedure (or after completion (or termination) / if completion (or termination) / in response to completion (or termination)), for example, if the first timer is running, the UE can pause the first timer. The second procedure can complete (or terminate) successfully. The second procedure can fail to complete (or terminate).

[0282] When the UE cancels (or aborts) the second procedure (or after cancellation (or aborts) / if cancellation (or aborts) / in response to cancellation (or aborts)), for example, if the first timer is running, the UE can pause the first timer.

[0283] Before the UE initiates a second procedure, for example, if the first timer is (at least) running, the UE can pause the first timer.

[0284] When the UE (determines) (re)selects another network (e.g., a second network) (or connects to another network / attaches to another network / registers with another network / subscribes to a service with another network) (or after (determines) (re)selects / if (determines) (re)selects / in response to (determines) (re)selects), for example, if (at least) the first timer is suspended, the UE can resume the first timer.

[0285] When the UE transmits a third message (or after transmission / if transmission / in response to transmission), for example, if (at least) the first timer is paused, the UE can resume the first timer.

[0286] When the UE receives the fourth message (or after / if received / in response to the reception), for example, if (at least) the first timer is paused, the UE can resume the first timer.

[0287] When the UE initiates a second procedure (or after initiation / if initiation / in response to initiation), for example, if (at least) the first timer is suspended, the UE can resume the first timer.

[0288] When the UE completes (or terminates) the second procedure (or after completion (or termination) / if completion (or termination) / in response to completion (or termination)), for example, if the first timer is paused (at least), the UE can resume the first timer. The second procedure can complete (or terminate) successfully. The second procedure can fail to complete (or terminate).

[0289] When the UE cancels (or aborts) the second procedure (or after cancellation (or aborts) / if cancellation (or aborts) / in response to cancellation (or aborts)), for example, if the first timer is (at least) suspended, the UE can resume the first timer.

[0290] When the UE (determines) (re)selects another network (e.g., a second network) (or connects to another network / attaches to another network / registers with another network / subscribes to a service with another network) (or after (determines) (re)selects / if (determines) (re)selects / in response to (determines) (re)selects), the UE may start (or restart) the first timer.

[0291] When the UE initiates the second procedure (or after initiation / if initiation / in response to initiation), the UE may start (or restart) the first timer.

[0292] When the UE transmits a third message (or after transmission / if transmission / in response to transmission), the UE may start (or restart) the first timer.

[0293] When the UE receives a fourth message (or after / if received / in response to receiving), for example, if the first timer stopped due to the second procedure, the UE can start (or restart) the first timer.

[0294] When the UE completes (or terminates) the second procedure (or after completion (or termination) / if completion (or termination) / in response to completion (or termination)), for example, if the first timer stopped due to the second procedure, the UE can start (or restart) the first timer. The second procedure may complete (or terminate) successfully. The second procedure may fail to complete (or terminate).

[0295] When the UE cancels (or aborts) the second procedure (or after cancellation (or aborts) / if cancellation (or aborts) / in response to cancellation (or aborts)), for example, if the first timer stops due to the second procedure, the UE can start (or restart) the first timer.

[0296] After the first timer expires (or when it expires / if it expires / in response to the expiration), the UE may perform at least the first action. If (at least) the second procedure is not in progress, then the UE may perform at least the first action.

[0297] During the second procedure, for example, after the first timer expires, if the first timer is not running, the UE may not perform at least the first action. If the first timer expires during the second procedure, for example, after the first timer expires, if the first timer is not running, the UE may not perform at least the first action.

[0298] The UE can (for example, after the first timer expires, or when the first timer is not running) determine whether to perform at least the first action based on whether at least the second procedure is in progress.

[0299] After the second procedure is completed (or terminated, or canceled) (or when completed (or terminated, or canceled) / if completed (or terminated, or canceled) / in response to completion (or termination, or cancellation)), for example, if the first timer expires during the second procedure, the UE may perform at least the first action. The second procedure may complete (or terminate) successfully. The second procedure may fail to complete (or terminate).

[0300] At the end of the second procedure, for example, if the first timer expires during the second procedure, the UE can consider the first timer to have expired.

[0301] After the second procedure is completed (or terminated, or canceled) (or when completed (or terminated, or canceled) / if completed (or terminated, or canceled) / in response to completion (or termination, or cancellation)), for example, if the first timer expires during the second procedure, the UE may consider the first timer to have expired. The second procedure may complete (or terminate) successfully. The second procedure may fail to complete (or terminate) successfully.

[0302] After the UE receives the fourth message (or when / if / in response to receiving), for example, if the first timer expires during the second procedure, the UE may perform at least the first action.

[0303] The first action can be (or includes) one or more of the following:

[0304] - Initiate (or re-initiate) the first procedure (e.g., for S&F operations, or via the first network),

[0305] - Transmit (or retransmit) the first message (e.g., for S&F operations, or via a first network),

[0306] - Allow (or enable) the UE to (re)select a network (e.g., a first network) (or connect to a network, attach to a network, register with a network, or subscribe to a service from a network), and / or

[0307] - Allow (or enable) the UE to continue (or resume) the first procedure (e.g., for S&F operation, or via the first network).

[0308] While the first timer is running, the UE can be prohibited (or not allowed) from initiating (or triggering) the first procedure (and / or transmitting the first message), such as to the first network, and / or for S&F operations. While the first timer is running, the UE can be prohibited (or not allowed) from (re)selecting a network (or connecting to a network, or attaching to a network, or registering with a network or subscribing to services with a network), such as a second network, and / or for S&F operations. Prohibition can be applied to networks indicated by the satellite ID list. Prohibition can not be applied to networks not indicated by the satellite ID list.

[0309] While the first timer is running, the UE may be permitted (or may not be prohibited) to initiate (or trigger) a second procedure (and / or transmit a third message), for example, to a second network, and / or for normal service (e.g., other than S&F operation). While the first timer is running, the UE may be permitted (or may not be prohibited) to (re)select a network (or connect to a network, or attach to a network, or register with a network or subscribe to services from a network), for example, a second network, and / or for normal service (e.g., other than S&F operation).

[0310] When the first timer is not running, the UE may be permitted to initiate (or trigger) the first procedure (and / or transmit the first message), for example, to the first network, and / or for S&F operations. When the first timer is not running, the UE may be permitted to (re)select a network (or connect to a network, or attach to a network, or register with a network or subscribe to services with a network), for example, a second network, and / or for S&F operations.

[0311] The network (e.g., the first network, the second network) can be (or include) a PLMN.

[0312] The network (e.g., the first network, the second network) may be (or include) satellite NW.

[0313] The network (e.g., the first network, the second network) can be (or include) an NTN.

[0314] The network (e.g., the first network, the second network) can be (or include) TN.

[0315] A network (e.g., a first network, a second network) can be (or include) a cell.

[0316] A network (e.g., a first network, a second network) can be (or include) a group of cells.

[0317] The first and second networks can have different network types (e.g., TN, NTN).

[0318] The first and second networks can have different PLMNs.

[0319] The first network can be a first PLMN and / or the second network can be a second PLMN.

[0320] The first network and the second network can have different cells.

[0321] The first and second networks can provide different types of services (e.g., S&F operations, normal services).

[0322] The first network and the second network can belong to the same PLMN.

[0323] The first network can be (or include) an S&F satellite network (e.g., E-UTRAN).

[0324] The second network can be (or include) other networks that are different from the first network.

[0325] The second network can be (or include) a non-S&F satellite network (e.g., E-UTRAN).

[0326] The second network can be (or include) a terrestrial network (e.g., E-UTRAN).

[0327] The first network can be (or include) a network (or network node) indicated by (or within) the satellite ID list.

[0328] The second network can be (or include) a network (or network node) that is not indicated in the satellite ID list (or is outside of it).

[0329] The first and / or second procedures may be (or include): a registration (or deregistration) procedure, an attachment procedure, a tracking area update procedure, a Protocol Data Unit (PDU) session establishment (or modification) procedure, a NAS transfer procedure, a Packet Data Network (PDN) connectivity procedure, and / or a service request procedure.

[0330] The first and / or second procedures may be (or include): Radio Resource Control (RRC) connection establishment procedure, RRC connection re-establishment procedure, and / or RRC connection recovery procedure.

[0331] The first procedure can be used for S&F operations, for non-S&F operations, or for normal service.

[0332] The second procedure can be used for S&F operations, for non-S&F operations, or for normal service.

[0333] The first network may initially operate in S&F mode and / or provide S&F services. The first network may provide (or broadcast) instructions for S&F operation, for example, in system information. These instructions may indicate that the first network is in S&F mode, using S&F operation, and / or providing S&F services. The UE may receive a configuration of a waiting time (or a first timer) from the first network, for example, in a second message, during the first procedure, and / or when the first network is operating in S&F mode.

[0334] In some cases, the first network may be able to change (or switch) its operating mode, for example, leave S&F mode, disable S&F operation, enable normal service, and / or enter the default mode (or normal mode). The change may be due to the first network's feed link becoming available. The first network may stop providing (or stop broadcasting) indications of S&F operation, for example, in system information. The first network may indicate that it is in the default mode, using normal operation, and / or providing normal service (e.g., by an indication that it is absent or disabled).

[0335] When the UE detects at least the first condition (or if detected / after detected / in response to detection), the UE may stop the first timer, for example, if (at least) the first timer is running.

[0336] The first condition can be (or include) one or more of the following:

[0337] - The first network changes (or switches) its operating mode (e.g., from S&F mode to default / normal mode).

[0338] - The first network disables S&F operations, stops providing S&F services, and / or exits S&F mode.

[0339] - The first network is enabled to operate normally, begin providing normal service, and / or enter default mode (or normal mode).

[0340] - The first network stops providing an indication of S&F mode (e.g., in system information), and / or

[0341] - The first network changes the value of the S&F mode indicator (e.g., from enabled to disabled).

[0342] Operating modes can include: S&F mode / operation / service, and normal (or default) mode / operation / service.

[0343] Throughout this disclosure, the following terms may be used interchangeably: S&F, S&F mode, S&F operation, S&F service.

[0344] Throughout this disclosure, the following terms may be used interchangeably: normal mode, default mode, normal service, normal operation.

[0345] The UE and / or network (e.g., network node) may be in S&F mode (or using S&F operation) if at least one or more of the following conditions are met:

[0346] - The feed link (to the UE and / or the network or network node) is unavailable.

[0347] - Receive (or transmit / provide / broadcast) instructions for S&F mode (and / or enable S&F mode),

[0348] - Receive (or transmit / provide / broadcast) configurations related to (and / or enable) S&F mode, and / or

[0349] - Enable and / or activate (UE and / or network or network node) S&F mode.

[0350] The UE and / or network or network node may be in normal mode (e.g., instead of S&F mode) if at least one or more of the following conditions are met:

[0351] - Feed links (for the UE and / or the network or network nodes) are available.

[0352] - No indication of S&F mode received (or transmitted / provided)

[0353] - Receive (or transmit / provide / broadcast) an instruction to deactivate (or deactivate) S&F mode.

[0354] - No configuration related to (and / or enabled) S&F mode was received (or transmitted / provided / broadcast).

[0355] - Receive (or transmit / provide / broadcast) the configuration to deactivate (or deactivate) S&F mode, and / or

[0356] - Disable and / or deactivate (UE and / or network or network node) S&F mode.

[0357] The UE and / or network or network node can enter S&F mode from normal mode, and / or leave S&F mode and enter normal mode.

[0358] When the UE and / or the network or network node are in S&F mode (or using S&F operation), at least one or more of the following can be performed:

[0359] - The UE is aware (or is notified by the NW) that the NW is (or has begun) using S&F to process data (and / or signaling).

[0360] - The UE may initiate a procedure to request (or instruct) the (satellite) NW to use the S&F to process data (and / or signaling).

[0361] - The UE can perform the transmission of data (and / or signaling) that will be processed by the S&F in the (satellite) NW, and / or

[0362] - The UE can (be ready) perform data (and / or signaling) reception stored in the (satellite) NW.

[0363] One or more configurations (indicators / parameters) associated with S&F can be provided to the UE (e.g., from the network or network nodes, for example, in addition to information). S&F-related configurations (and / or indications / parameters) (or S&F configurations) can be associated with (or specific to) an object. Objects can be (or include) UEs, cells, connections (e.g., RRC connections, NAS connections), PDU sessions, and / or Quality of Service (QoS) flows. The NW can indicate (or configure) the object associated with the configuration (and / or indication / parameter). The NW can provide (at least) one configuration (and / or indication / parameter) to (at least) one object.

[0364] S&F-related configurations (and / or indications / parameters) may be / include / used to / indicate one or more of the following (headings):

[0365] S&F mode indication

[0366] The indication can (at least) indicate whether S&F operation is enabled (e.g., in a cell, for a UE, for a NW). The indication can (at least) indicate whether the feed link of the NW is available. The indication can (at least) indicate whether the UE is allowed to use S&F operation (e.g., in a cell, for a NW).

[0367] The UE can (at least) determine whether to use S&F operation based on an indication. For example, if the UE receives an indication, then the UE can consider S&F operation enabled (and / or activated). If the UE does not receive an indication, then the UE can consider S&F operation disabled (and / or activated). If the UE receives an indication, then the UE can be allowed to use S&F operation. If the UE does not receive an indication, then the UE may not be allowed to use S&F operation. The UE can have a specific UE type. UE types are shown below.

[0368] UE type

[0369] The configuration can (at least) indicate what type of UE is permitted to use S&F operation. The configuration can (at least) indicate what type of UE is permitted to perform transmissions and / or receptions to the NW (e.g., using S&F operation). Transmissions and / or receptions can be (User Plane (UP)) data and / or (Control Plane (CP)) signaling.

[0370] UE type (e.g., first type) can be based on UE capabilities, UE mobility, UE QoS characteristics, UE state (or identified by / represented by / specific to said items). UE type can be (or includes) at least Enhanced Machine Type Communication ((e)MTC) UE, Narrowband Internet of Things (NB-IoT) UE, Reduced Capability (RedCap) UE, UE supporting New Radio (NR), UE supporting 5GC, UE supporting NTN, UE supporting regenerated payload, UE with Global Navigation Satellite System (GNSS), and / or UE supporting S&F operation. UE type can be (or includes) at least Stationary UE, Low Mobility UE, and / or UE in a restricted area. UE type can be (or includes) at least UE with low QoS requirements, and / or UE without Ultra Reliable Low Latency Communication (URLLC).

[0371] The configuration can also be pre-configured. For example, if a Type 1 UE receives an S&F mode indication, then the UE is allowed to use S&F operation. For example, a Type 1 UE is always allowed to use S&F operation.

[0372] The UE can (at least) determine whether to use S&F operations based on its configuration. For example, if the UE receives a configuration and / or the UE belongs to the UE type in the configuration (or pre-configuration), then the UE can consider S&F operations enabled (and / or activated, and / or allowed). If the UE receives a configuration and / or the UE does not belong to the UE type in the configuration (or pre-configuration), then the UE can consider S&F operations disabled (and / or activated, and / or allowed). If the UE does not receive a configuration, then the UE can consider S&F operations disabled (and / or activated, and / or allowed).

[0373] Business type

[0374] The configuration can (at least) indicate what (types) of service are allowed to use S&F operations. The configuration can (at least) indicate what (types) of service are allowed to be transmitted to the NW (e.g., using S&F operations). Service can be (UP) data and / or (CP) signaling. Service can be at the Access Layer (AS) level and / or NAS level. The configuration can (also) be pre-configured. The configuration can be based on the QoS requirements of the service (or service type).

[0375] Services (or service types) may be based on QoS flows, PDU sessions, radio bearers (signaling radio bearers (SRB) and / or data radio bearers (DRB)), radio link control (RLC) bearers, and / or logical channels (or identified by / represented by / specific to the aforementioned items).

[0376] Explicit configuration can be used for a specific service (or service type), while implicit configuration (or pre-configuration) can be used for a (other) service (or service type). For example, whether a first service (or service type) is allowed to use S&F operations can be based on configuration. Whether a second service (or service type) is allowed to use S&F operations can be based on pre-configuration (e.g., allowed, disallowed, not configured).

[0377] The UE can (at least) determine whether to use S&F operations based on configuration (e.g., for a specific service or service type). For example, if the UE receives a configuration and / or the UE's service is included in the configuration (or pre-configuration), then the UE can consider S&F operations enabled (or disabled) (and / or activated, and / or allowed), for example, for a service. If the UE receives a configuration and / or the UE's service is not included in the configuration (or pre-configuration), then the UE can consider S&F operations disabled (or enabled) (and / / or activated, and / or allowed), for example, for a service. If the UE receives a configuration and / or the UE's service meets the conditions / limitations / constraints / requirements of the configuration (or pre-configuration), then the UE can consider S&F operations enabled (and / / or activated, and / or allowed), for example, for a service. If the UE receives a configuration and / or the UE's service does not meet the conditions / limitations / constraints / requirements of the configuration (or pre-configuration), then the UE can consider S&F operations disabled (or enabled) (and / / or activated, and / or allowed), for example, for a service. If the UE does not receive the configuration, then the UE may assume that the S&F operation is enabled (or disabled) (and / or activated, and / or allowed), for example, for each (or all) service of the UE.

[0378] If the UE deems the S&F operation to be permitted / enabled / activated for the service, then the UE may perform the transmission (and / or reception) of the service (e.g., using the S&F operation), initiate procedures for (or used for) performing the transmission (and / or reception) of the service (e.g., using the S&F operation), and / or request permissions / establishment / resources for the service (e.g., using the S&F operation). These procedures may be registration procedures (e.g., for initial and / or mobility updates), service request procedures, or PDU session establishment (or modification) procedures.

[0379] QoS parameters

[0380] The parameters are available to the UE (e.g., at least based on the parameters) to (at least) determine whether the QoS requirements of a UE request (e.g., for a service, connection, PDU session, and / or QoS flow) can be met. The parameters are available to the UE (e.g., at least based on the parameters) to (at least) determine whether to initiate a UE request (e.g., for a service, connection, PDU session, and / or QoS flow).

[0381] Parameters may (at least) be based on UE, connection, service, PDU session, and / or QoS flow (or identified by / represented by / specific to said items). Configuration may (at least) indicate what types of UE, connection, service, PDU session, and / or QoS flow are associated with the parameters. Parameters may (at least) be based on radio bearers (SRB and / or DRB), RLC bearers, and / or logical channels (or identified by / represented by / specific to said items). Configuration may (at least) indicate what types of radio bearers, RLC bearers, and / or logical channels are associated with the parameters.

[0382] The parameters may be (or include) (at least) QoS Flow Identifier (QFI), 5G QoS Identifier (5QI), Allocation and Preservation Priority (ARP), Resource Type, Priority, Packet Error Rate, Average Window, Delay Budget (e.g., Packet Delay Budget), and / or Data Volume (Maximum Data Burst).

[0383] The parameters may (at least) indicate the QoS (related) tier / requirement / feature that allows S&F operation. The parameters may (at least) indicate the maximum QoS tier (e.g., latency) that the NW can satisfy. The parameters may (at least) indicate the duration for which the NW is expected to store data (or signaling) received from the UE before delivery. The parameters may (at least) indicate the duration for which a response to a UE request is expected to be transmitted (or received).

[0384] The UE can (at least) determine whether to use S&F operations based on configuration (e.g., for a specific object, for a service, for a PDU session). For example, if the UE receives a configuration and / or the UE's object (or service or PDU session) is included in the configuration (or pre-configuration), then the UE can consider S&F operations enabled (or disabled) (and / or activated, and / or allowed), for example, for an object, for a service, and / or for a PDU session. If the UE receives a configuration and / or the UE's object (or service, or PDU session) is not included in the configuration (or pre-configuration), then the UE can consider S&F operations disabled (or enabled) (and / / or activated, and / or allowed), for example, for an object, for a service, and / or for a PDU session. If the UE receives a configuration and / or the UE's object (or service, or PDU session) satisfies the conditions / limitations / constraints / requirements of the configuration (or pre-configuration), then the UE can consider S&F operations enabled (and / / or activated, and / or allowed), for example, for an object, for a service, and / or for a PDU session. If the UE receives a configuration and / or the UE's object (or service, or PDU session) does not meet the conditions / limitations / constraints / requirements of the configuration (or pre-configuration), then the UE may consider S&F operation not enabled (or enabled) (and / or activated, and / or allowed), for example, for objects, for services, and / or for PDU sessions. If the UE does not receive a configuration, then the UE may consider S&F operation enabled (or not enabled) (and / or activated, and / or allowed), for example, for each (or all) of the UE's objects (or services, or PDU sessions).

[0385] If the UE believes that the S&F operation is allowed / enabled / activated for the object (or service, or PDU session), then the UE can perform the transmission (and / or reception) of the object (or service, or PDU session) (e.g., using the S&F operation), initiate procedures for (or for) performing the transmission (and / or reception) of the object (or service, or PDU session) (e.g., using the S&F operation), and / or request permissions / establishment / resources for the object (or service, or PDU session) (e.g., using the S&F operation). The procedures can be registration procedures (e.g., for initial and / or mobility updates), service request procedures, or PDU session establishment (or modification) procedures.

[0386] To determine whether a service (or PDU session, or UE) is allowed to use S&F operations, at least the objects of the service (or PDU session, or UE) must meet the configured QoS. For example, if none of the objects of the service (or PDU session, or UE) meet the configured QoS, then the UE may not be allowed to use S&F operations for the service (or PDU session, or UE). If every object of the service (or PDU session, or UE) meets the configured QoS, then the UE may be allowed to use S&F operations for the service (or PDU session, or UE). If some objects of the service (or PDU session, or UE) (e.g., the first object) meet the configured QoS, and some other objects of the service (or PDU session, or UE) (e.g., the second object) do not meet the configured QoS, then the UE may be allowed to use S&F operations for the first object, but not for the second object. If some objects (e.g., the first object) of a service (or PDU session, or UE) meet the configured QoS, and some other objects (e.g., the second object) of the service (or PDU session, or UE) do not meet the configured QoS, then the UE may not be allowed to use S&F operations for the service (or PDU session, or UE) (e.g., including the first and second objects). Conversely, if some objects (e.g., the first object) of a service (or PDU session, or UE) meet the configured QoS, and some other objects (e.g., the second object) of the service (or PDU session, or UE) do not meet the configured QoS, then the UE may be allowed to use S&F operations for the service (or PDU session, or UE) (e.g., including the first and second objects).

[0387] The object can be (or includes) (at least) a connection, service, PDU session, and / or QoS flow. The object can be (or includes) (at least) a radio bearer, RLC bearer, and / or logical channel.

[0388] Data volume

[0389] The configuration may (at least) indicate the data volume limit allowed for S&F operations. The configuration may (at least) indicate the amount of data that can be transmitted to the NW (e.g., using S&F operations). The data may be (or include) UP data and / or CP signaling. The data may be AS-level and / or NAS-level.

[0390] The configuration may (at least) be based on UE, connection, service, PDU session, and / or QoS flow (or identified by / represented by / specific to said items). The configuration may (at least) indicate what (or which) UE, connection, service, PDU session, and / or QoS flow is associated with the configuration. The configuration may (at least) be based on radio bearers (SRB and / or DRB), RLC bearers, and / or logical channels (or identified by / represented by / specific to said items). The configuration may (at least) indicate what (or which) radio bearer, RLC bearer, and / or logical channel is associated with the parameters.

[0391] The UE can (at least) determine, based on its configuration, whether to use S&F operations (e.g., for a specific object). The UE can (at least) determine, based on its configuration, whether to stop S&F operations (e.g., for a specific object). The UE can (at least) determine, based on its configuration, whether S&F operations can continue (e.g., for a specific object).

[0392] The object may be (or includes) (at least) a UE, connection, service, PDU session, and / or QoS flow. The object may be (or includes) (at least) a radio bearer, RLC bearer, and / or logical channel.

[0393] For example, if the UE receives a configuration and / or the UE's service (e.g., for an object) has not exceeded the data limit, then the UE may (be allowed) use S&F operation, for example, for the service. If the UE receives a configuration and / or the UE's service (e.g., for an object) has exceeded the data limit, then the UE may not (be allowed) use S&F operation, for example, for the service. If the UE does not receive a configuration, then the UE may assume that there is no data limit for using S&F operation, for example, for the UE and for the object.

[0394] If the UE deems S&F operation permitted (e.g., for a service), then the UE may perform (or continue) the transmission (and / or reception) of the service (e.g., using S&F operation), initiate (or continue) procedures for performing the transmission (and / or reception) of the service (e.g., using S&F operation), and / or request permissions / establishment / resources for the service (e.g., using S&F operation). Procedures may include registration procedures (e.g., for initial and / or mobility updates), service request procedures, and PDU session establishment (or modification) procedures.

[0395] If the UE has transmitted more data than the data limit, the UE can stop S&F operations, stop transmitting data, and stop the (in-process) procedure. If the UE has transmitted more data than the data limit, the UE can send an indication to the NW (e.g., indicating that the data limit has been reached), initiate a (RRC and / or NAS) connection release (request) procedure, initiate a deregistration procedure, and / or initiate a PDU session release (or modification) procedure (e.g., to release the PDU session). If the UE has transmitted more data than the data limit, the UE can release the (RRC and / or NAS) connection and / or switch to (RRC and / or NAS) idle mode (e.g., RRC_IDLE, Connection Management (CM)_IDLE).

[0396] An NW (or network node) can be a satellite NW. A satellite NW can be a network node, a CN node, a RAN node, an AMF, an SMF, an MME, a RAN, an NG-RAN, an eNB, a gNB, a subset of the above, and / or a combination of the above.

[0397] NW (or network node) can be a terrestrial NW. A terrestrial NW can be a network node, CN node, RAN node, AMF, SMF, MME, RAN, NG-RAN, eNB, gNB, or a combination thereof.

[0398] Satellite NW and ground-based NW can be mutually exclusive.

[0399] An NW (or network node) can be a cell. An NW can be a serving cell. An NW can be a neighboring cell. An NW can be a source cell. An NW can be a target cell.

[0400] The UE can be in RRC connected mode. The UE can be in RRC idle mode. The UE can be in RRC inactive mode.

[0401] The UE can be in CM idle state. The UE can be in CM connected state.

[0402] The UE can be in a registration management (RM) deregistration state. The UE can be in an RM registration state.

[0403] The UE can be in an NTN cell. The UE can connect to an NTN cell. The UE can connect to LEO, GEO, MEO, HEO, and / or HAPS.

[0404] The UE can be referred to as the UE, the UE's RRC entity, or the UE's Media Access Control (MAC) entity.

[0405] The UE can be an NR device. The UE can be a lightweight NR device. The UE can be a degraded device. The UE can be a mobile phone. The UE can be a wearable device. The UE can be a sensor. The UE can be a fixed device.

[0406] NW can be a network node. NW can be a base station. NW can be an access point. NW can be an eNB. NW can be a gNB. NW can be a gateway. NW can be a PLMN.

[0407] Various examples and embodiments of the invention are described below. The following aspects and embodiments are possible in relation to the methods, alternatives, concepts, examples, and embodiments detailed above and herein.

[0408] refer to Figure 16 According to this and other concepts, systems and methods of the present invention, a method 1000 for a UE in a wireless communication system includes: receiving a configuration of a first timer from a first network (step 1002), starting the first timer based on the configuration (step 1004), and stopping the first timer in response to initiating a second procedure or determining to reselect a second network (step 1006).

[0409] In various embodiments, the first network is a first PLMN.

[0410] In various embodiments, the second network is a second PLMN.

[0411] In various embodiments, the first timer indicates the period during which the UE is prohibited from initiating the first procedure to the first network.

[0412] In various embodiments, the first timer and / or the first program are used for S&F operations.

[0413] In various embodiments, the second procedure is not used for S&F operations.

[0414] In various embodiments, the first or second program is an attachment program.

[0415] In various embodiments, the first or second program is the TAU program.

[0416] Return to reference Figure 3 and Figure 4In one or more embodiments viewed from the perspective of a UE in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) receive a configuration of a first timer from a first network; (ii) start the first timer based on the configuration; and (iii) stop the first timer in response to initiating or successfully completing a second procedure or determining to reselect a second network. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described herein above, below, or otherwise.

[0417] Return to reference Figure 3 and Figure 4 In one or more embodiments viewed from the perspective of a first NW in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) transmit a configuration of a first timer to the UE; (ii) at the UE, start the first timer based on the configuration; and (iii) at the UE, stop the first timer in response to initiating or successfully completing a second procedure or determining to reselect a second network. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described herein above, below, or otherwise.

[0418] refer to Figure 17 According to this and other concepts, systems and methods of the present invention, a method 1010 for a UE in a wireless communication system includes: initiating a first procedure to a first network, wherein the first procedure is an attach procedure, a TAU procedure or a service request procedure (step 1012); receiving a configuration of a waiting time for S&F operations (step 1014); starting a first timer based on the waiting time, wherein while the first timer is running, the UE is prohibited from initiating the first procedure to the first network for S&F operations (step 1016); and stopping the first timer if the UE initiates or successfully completes a second procedure in a cell of a second network, wherein the second procedure is an attach procedure, a TAU procedure or a service request procedure (step 1018).

[0419] In various embodiments, the configuration of the waiting time is included in the response message of the first program.

[0420] In various embodiments, the first procedure is for S&F operations.

[0421] In various embodiments, the second procedure is used for normal service or not for S&F operations.

[0422] In various embodiments, the first network is a satellite cell of a first PLMN that is in S&F operation.

[0423] In various embodiments, the second network is not a satellite cell of the first PLMN that is in S&F operation.

[0424] In various embodiments, the first network is indicated by a list of satellite IDs.

[0425] In various embodiments, the satellite ID list indicates one or more satellites for which the UE cannot retry the first procedure while the first timer is running.

[0426] In various embodiments, the second network is a satellite cell and / or TN that is in normal service.

[0427] In various embodiments, the second network is a second PLMN.

[0428] In various embodiments, after the first timer expires, the UE is allowed to initiate a first procedure to the first network.

[0429] Return to reference Figure 3 and Figure 4 In one or more embodiments viewed from the perspective of a UE in a wireless communication system, apparatus 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) initiate a first procedure to a first network, wherein the first procedure is an attach procedure, a TAU procedure, or a service request procedure; (ii) receive a configuration of a waiting time for S&F operations; (iii) start a first timer based on the waiting time, wherein while the first timer is running, the UE is prohibited from initiating the first procedure to the first network for S&F operations; and (iv) stop the first timer if the UE initiates or successfully completes a second procedure in a cell of a second network, wherein the second procedure is an attach procedure, a TAU procedure, or a service request procedure. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described herein above, below, or otherwise.

[0430] Return to reference Figure 3 and Figure 4In one or more embodiments viewed from the perspective of a first NW in a wireless communication system, apparatus 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) initiate a first procedure from the UE, wherein the first procedure is an attach procedure, a TAU procedure, or a service request procedure; (ii) transmit a configuration of a waiting time for S&F operation to the UE; (iii) at the first UE, based on the waiting time, start a first timer, wherein while the first timer is running, the UE is prohibited from initiating the first procedure to the first network for S&F operation; and (iv) at the UE, stop the first timer if the UE initiates or successfully completes a second procedure in a cell of the second network, wherein the second procedure is an attach procedure, a TAU procedure, or a service request procedure. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described herein above, below, or otherwise.

[0431] Any combination of the concepts or teachings described above or herein may be combined, in whole or in part, to form new embodiments. The disclosed details and embodiments may be used to solve at least (but not limited to) the problems mentioned above and herein.

[0432] It should be noted that any of the methods, alternatives, steps, examples, and embodiments presented herein may be used independently, alone, and / or in combination with multiple methods, alternatives, steps, examples, and embodiments.

[0433] Various aspects of this disclosure have been described above. It should be understood that the teachings herein can be implemented in a wide variety of forms, and any particular structure, function, or both disclosed herein are merely representative. Based on the teachings herein, those skilled in the art will understand that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement an apparatus or practice. Furthermore, this apparatus or practice can be implemented or practiced by using other structures, functions, or structures and functions other than or different from one or more aspects set forth herein. As examples of some of the foregoing concepts, in some aspects, a parallel channel can be established based on the pulse repetition frequency. In some aspects, a parallel channel can be established based on the pulse position or offset. In some aspects, a parallel channel can be established based on a time-hopping sequence. In some aspects, a parallel channel can be established based on the pulse repetition frequency, the pulse position or offset, and the time-hopping sequence.

[0434] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the foregoing description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0435] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of both, which may be designed using source decoding or some other technique) and various forms of program or design code (which, for convenience, may be referred to herein as "software" or "software module"), or a combination thereof, with instructions. To clearly illustrate this interchangeability between hardware and software, the functionality of the various illustrative components, blocks, modules, circuits, and steps has been described above in general terms. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as causing a deviation from the scope of this disclosure.

[0436] Furthermore, the various illustrative logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or executed by an integrated circuit (“IC”), access terminal, or access point. An IC may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein and capable of executing code or instructions residing within the IC, outside the IC, or both. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0437] It should be understood that any particular order or hierarchy of steps in any disclosed process is an example of an exemplary method. It should be understood that a particular order or hierarchy of steps in the process may be rearranged based on design preferences while remaining within the scope of this disclosure. The accompanying method claims present the elements of the various steps in an exemplary order, but are not intended to limit one to the specific order or hierarchy presented.

[0438] The steps of the methods or algorithms described in conjunction with the aspects disclosed herein can be implemented directly in hardware, with a software module executed by a processor, or a combination of both. The software module (e.g., containing executable instructions and associated data) and other data can reside in a data memory, such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of computer-readable storage media known in the art. Example storage media can be coupled to a machine such as a computer / processor (for convenience, the machine may be referred to herein as a "processor"), such that the processor can read information (e.g., code) from the storage media and write information to the storage media. Example storage media can be integrated with the processor. The processor and storage media can reside in an ASIC. The ASIC can reside in a user equipment. Alternatively, the processor and storage media can reside in a user equipment as discrete components. Additionally, in some aspects, any suitable computer program product may include a computer-readable medium comprising code associated with one or more aspects of this disclosure. In some aspects, the computer program product may include packaging material.

[0439] While the invention has been described in conjunction with various aspects and examples, it should be understood that further modifications are possible. This application is intended to cover any changes, uses, or adaptations to the invention that generally follow the principles of the invention and include such deviations from this disclosure that fall within the scope of known and customary practice in the art to which this invention pertains.

Claims

1. A method for non-terrestrial network store and forward of a wait timer for a user equipment, characterized in that, comprising: initiating a first procedure to a first network, wherein the first procedure is an attach, tracking area update procedure, or service request procedure; receiving a configuration of a wait time for store-and-forward operation; starting a first timer based on the wait time, wherein the user equipment is prohibited from initiating the first procedure to the first network for the store-and-forward operation when the first timer is running; and stopping the first timer if the user equipment initiates or successfully completes a second procedure in a cell of a second network, wherein the second procedure is an attach, tracking area update procedure, or service request procedure.

2. The method of claim 1, wherein, The configuration of the wait time is included in a response message of the first procedure.

3. The method of claim 1, wherein, The first procedure is for store-and-forward operation.

4. The method of claim 1, wherein, The second procedure is for normal service, or not for store-and-forward operation.

5. The method of claim 1, wherein, The first network is a satellite cell of a first public land mobile network in store-and-forward operation.

6. The method of claim 5, wherein, The second network is not a satellite cell of the first public land mobile network in store-and-forward operation.

7. The method of claim 1, wherein, The first network is indicated by a list of satellite identities, or the list of satellite identities indicates one or more satellites that the user equipment cannot re-attempt the first procedure when the first timer is running.

8. The method of claim 7, wherein, The second network is a second public land mobile network.

9. The method of claim 1, wherein, The second network is a satellite cell or a terrestrial network in normal service.

10. The method of claim 1, wherein, After the first timer expires, the user equipment is allowed to initiate the first procedure to the first network. 11.A user equipment, comprising: comprising: a memory; and a processor coupled in operation with the memory, wherein the processor is configured to execute program code to: initiate a first procedure to a first network, wherein the first procedure is an attach, tracking area update procedure, or service request procedure; receive a configuration of a wait time for store-and-forward operation; start a first timer based on the wait time, wherein the user equipment is prohibited from initiating the first procedure to the first network for the store-and-forward operation when the first timer is running; and stop the first timer if the user equipment initiates or successfully completes a second procedure in a cell of a second network, wherein the second procedure is an attach, tracking area update procedure, or service request procedure.

12. The user equipment of claim 11, wherein, The configuration of the wait time is included in a response message of the first procedure.

13. The user equipment of claim 11, wherein, The first procedure is for store-and-forward operation.

14. The user equipment of claim 11, wherein, The second procedure is for normal service, or not for store-and-forward operation.

15. The user equipment of claim 11, wherein, The first network is a satellite cell of a first public land mobile network in store-and-forward operation.

16. The user equipment of claim 15, wherein, The second network is not a satellite cell of the first public land mobile network in store-and-forward operation.

17. The user equipment of claim 11, wherein, The first network is indicated by a list of satellite identities, or the list of satellite identities indicates one or more satellites that the user equipment cannot re-attempt the first procedure when the first timer is running.

18. The user equipment of claim 17, wherein, The second network is a second public land mobile network.

19. The user equipment of claim 11, wherein, The second network is a satellite cell or a terrestrial network in normal service. After the first timer expires, the user equipment is allowed to initiate the first procedure to the first network.

20. The user equipment of claim 11, wherein, After expiry of the first timer, the user equipment is allowed to initiate the first procedure to the first network.

Images