Method and apparatus for storing and forwarding time information for non-terrestrial network operations

Abstract

Methods, systems, and devices are provided for time information for non-terrestrial network storage and forwarding operations such that a user equipment can more efficiently apply storage and forwarding operations, where the method of the user equipment includes receiving time information for storage and forwarding operations in a non-terrestrial network cell, and determining when to enter or leave a storage and forwarding mode for the non-terrestrial network cell based on the time information.

Description

[0001] Cross - reference to related applications

[0002] This application claims the priority and benefit of U.S. Provisional Patent Application No. 63 / 604,605, filed on November 30, 2023, which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure generally relates to wireless communication networks, and more particularly, to methods and devices for time information for non - terrestrial network (NTN) store - and - forward operations in a wireless communication system. Background Art

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

[0005] An exemplary network structure is the Evolved Universal Terrestrial Radio Access Network (E - UTRAN). The E - UTRAN system can provide high data throughput to enable the above - mentioned IP - bearer voice and multimedia services. Currently, the 3GPP standards organization is discussing new radio technologies for the next generation (e.g., 5G). Thus, changes to the current body of the 3GPP standards are currently being submitted and considered to evolve and complete the 3GPP standards. Summary of the Invention

[0006] Methods, systems, and devices for time information for non - terrestrial network (NTN) store - and - forward operations in a wireless communication system are provided, enabling a user equipment (UE) to more efficiently apply store - and - forward (S&F) operations. In various embodiments, the method of the UE includes receiving time information for S&F operations in an NTN cell and determining when to enter or leave the S&F mode for the NTN cell based on the time information.

[0007] In various embodiments, the method for an NTN cell in a wireless communication system includes transmitting time information for S&F operations. Brief Description of the Drawings

[0008] Figure 1 Drawings showing a wireless communication system according to an embodiment of the present invention.

[0009] Figure 2 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 is a functional block diagram of a communication system according to an embodiment of the present invention.

[0011] Figure 4 is according to an embodiment of the present invention Figure 3 functional block diagram of the program code of

[0012] Figure 5 is in 3GPP TR 38.821 V16.0.0 Figure 4 .1-1: Reproduction of a typical scenario of a non-terrestrial network based on a transparent payload.

[0013] Figure 6 is in 3GPP TR 38.821 V16.0.0 Figure 4 .1-2: Reproduction of a typical scenario of a non-terrestrial network based on a regenerated payload.

[0014] Figure 7 is in 3GPP TR 38.821 V16.0.0 Figure 5 .2.1-1: Reproduction of a regenerative satellite without an ISL and with a payload processed by a gNB.

[0015] Figure 8 is in 3GPP TR 38.821 V16.0.0 Figure 5 .2.1-2: Reproduction of a regenerative satellite with an ISL and with a payload processed by a gNB.

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

[0017] Figure 10 is a reproduction of FIG. A-1 in 3GPP TR 22.865 V2.0.0: Illustration of "normal / default operation" and "S&F operation" modes in a 5G system with satellite access.

[0018] Figure 11 is in 3GPP TR 22.865 V2.0.0 Figure 5 .4.3-1: Reproduction of animal tracking in remote areas.

[0019] Figure 12It is a reproduction of the diagram of the possible call flow for the intermittent feeder link in 3GPP RWS-230178.

[0020] Figure 13 It is in 3GPP TS 23.501 V18.1.0 Figure 4 .2.3-1: Reproduction of the non-roaming 5G system architecture.

[0021] Figure 14 It is a diagram showing an example illustration of the NTN network according to an embodiment of the present invention.

[0022] Figure 15 It is a diagram showing an example of the S&F mode to the normal mode according to an embodiment of the present invention.

[0023] Figure 16 It is a diagram showing an example of the normal mode to the S&F mode according to an embodiment of the present invention.

[0024] Figure 17 It is a flowchart of a method of a UE in a wireless communication system according to an embodiment of the present invention, the method including receiving information for deriving the time of S&F operation, and determining whether to perform an action based on the information.

[0025] Figure 18 It is a flowchart of a method of a first network node in a wireless communication system according to an embodiment of the present invention, the method including transmitting information for deriving the time of S&F operation to the UE, and performing the S&F operation at the time indicated by the information.

[0026] Figure 19 It is a flowchart of a method of a UE in a wireless communication system according to an embodiment of the present invention, the method including receiving time information for S&F operation in an NTN cell, and determining when to enter or leave the S&F mode for the NTN cell based on the time information.

[0027] Figure 20 It is a flowchart of a method of an NTN cell in a wireless communication system according to an embodiment of the present invention, the method including transmitting time information for S&F operation. Detailed Description

[0028] The present invention described herein can be applied to or implemented in the exemplary wireless communication systems and apparatuses described below. Additionally, the present invention is mainly described in the context of the 3GPP architecture reference model. However, it should be understood that those skilled in the art can easily adapt and implement aspects of the present invention using and in 3GPP2 network architectures and other network architectures with the disclosed information.

[0029] The exemplary wireless communication systems and devices described below employ a wireless communication system that supports broadcast services. Wireless communication systems have been widely deployed to provide various types of communications, such as voice, data, etc. These systems can 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®, 3GPP New Radio (NR), or some other modulation techniques.

[0030] Specifically, the exemplary wireless communication systems and devices described below can be designed to support one or more standards, such as those provided by a consortium named "Third Generation Partnership Project" and 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 TR 22.865 V2.0.0, "Study on Satellite Access Phase 3 (Release 19)"; [3] 3GPP TS 23.501 V18.1.0, "System Architecture for 5G Systems (5GS)"; and [4] 3GPP RWS-230178, "NR and IoT NTN". The standards and documents listed above are hereby incorporated herein by reference in their entirety and completely.

[0031] Figure 1 A multi-access wireless communication system according to an embodiment of the present invention is shown. The access network 100 (access network, AN) includes multiple antenna groups, one including 104 and 106, another including 108 and 110, and still another including 112 and 114. In Figure 1In [the figure], only two antennas are shown for each antenna group. However, more or fewer antennas can be utilized for each antenna group. Access Terminal (AT) 116 communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 via forward link 120 and receive information from AT 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, where antennas 106 and 108 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 can use different frequencies for communication. For example, forward link 120 can use a frequency different from the frequency used by reverse link 118.

[0032] Each group of antennas 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 access terminals in a sector of the area covered by access network 100.

[0033] In communication via forward links 120 and 126, the transmitting 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. Also, compared to an access network that transmits to all of its access terminals via a single antenna, the access network using beamforming to transmit to access terminals randomly dispersed throughout the coverage area of the access network generally causes less interference to access terminals in adjacent cells.

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

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

[0036] In one embodiment, each data stream is transmitted via a corresponding transmitting antenna. TX data processor 214 formats, encodes, and interleaves the traffic data of the data streams based on a particular encoding scheme selected for each data stream to provide encoded data.

[0037] The OFDM technique can be used to multiplex the decoded data and pilot data of each data stream. 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. Subsequently, the multiplexed pilot and decoded data for the data stream are modulated (e.g., symbol mapped) based on a specific modulation scheme selected for each data stream (e.g., BPSK, QPSK, M-PSK, or M-QAM) to provide modulated symbols. The data rate, decoding, and modulation for each data stream can be determined by instructions executed by the processor 230. The memory 232 is coupled to the processor 230.

[0038] Next, the modulated symbols of all data streams are provided to the TX MIMO processor 220, which can further process the modulated symbols (e.g., for OFDM). The TX MIMO processor 220 then provides N T streams of modulated symbols to N T transmitters (TMTR) 222a through 222t. In some embodiments, the TX MIMO processor 220 applies beamforming weights to the symbols of the data stream and the antennas from which the symbols are transmitted.

[0039] Each transmitter 222 receives and processes the corresponding symbol stream to provide one or more analog signals and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission via the MIMO channel. Then, N T modulated signals from transmitters 222a through 222t are transmitted from N T antennas 224a through 224t, respectively.

[0040] At the receiver system 250, the transmitted modulated signals are received by N R antennas 252a through 252r, and the signals received from each antenna 252 are provided to the corresponding receivers (RCVR) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) the corresponding received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding "received" symbol stream.

[0041] The RX data processor 260 then receives and processes the N R received symbol streams from the N R receivers 254 based on specific receiver processing techniques to provide N Ta "detected" symbol stream. The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing performed by the RX data 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.

[0042] The processor 270 periodically determines which precoding matrix (discussed below) to use. The processor 270 formulates a reverse link message that includes a matrix index portion and a rank value portion.

[0043] The reverse link message can include various types of information about 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 the traffic data for several data streams from the data source 236), modulated by the modulator 280, conditioned by the transmitters 254a to 254r, and transmitted back to the transmitter system 210.

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

[0045] The memory 232 can be used to temporarily store some buffered / computed data from 240 or 242 via the processor 230, store some buffered data from 212, or store some specific program code. Also, the memory 272 can be used to temporarily store some buffered / computed data from 260 via the processor 270, store some buffered data from 236, or store some specific program code.

[0046] Turning to Figure 3 , this figure shows an alternative simplified functional block diagram of a communication device according to an embodiment of the present invention. As Figure 3 shown, the communication device 300 in a wireless communication system can be utilized to implement Figure 1UEs (or ATs) 116 and 122 therein, 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 through the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 may receive signals input by a user through the input device 302 (e.g., a keyboard or keypad), and may output images and sounds through the output device 304 (e.g., a monitor or speaker). The transceiver 314 is used to receive and transmit wireless signals, transfer the received signals to the control circuit 306, and wirelessly output the signals generated by the control circuit 306.

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

[0048] For LTE, LTE-A, or NR systems, the layer 2 part 404 may include a Radio Link Control (RLC) layer and a Medium Access Control (MAC) layer. The layer 3 part 402 may include a Radio Resource Control (RRC) layer.

[0049] Any two or more of the following paragraphs, (sub)bullet points, key points, actions, or claims described in each inventive paragraph or section may be logically, reasonably, and appropriately combined to form a specific method.

[0050] Any sentence, paragraph, (sub)bullet point, key point, action, or claim described in each of the following inventive paragraphs or sections may be implemented independently and separately to form a specific method or device. Dependencies such as "based on", "more specifically", "example", etc. in the following disclosure of the present invention are only one possible embodiment that does not limit a specific method or device.

[0051] 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 vehicles to carry transmission equipment relay nodes or base stations. More descriptions are also specified in [1] 3GPP TR 38.821 V16.0.0:

[0052] ********************** Citation begins ************************

[0053] 4.1 Overview of Non-Terrestrial Networks

[0054] A non-terrestrial network refers to a network or network segment that uses RF resources on satellites (or UAS platforms).

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

[0056] Figure 5 is from 3GPP TR 38.821 V16.0.0 Figure 4 .1-1: Reproduction of a typical scenario of a non-terrestrial network based on a transparent payload.

[0057] Figure 6 is from 3GPP TR 38.821 V16.0.0 Figure 4 .1-2: Reproduction of a typical scenario of a non-terrestrial network based on a regenerative payload.

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

[0059] - One or several satellite gateways that connect the non-terrestrial network to a public data network

[0060] - GEO satellites are fed by one or several satellite gateways deployed across the satellite target coverage area (e.g., regional or even continental coverage). We assume that UEs in a cell are served by only one satellite gateway

[0061] - Non-GEO satellites that are continuously served by one or several satellite gateways at a time. The system ensures service and feeder link continuity between continuously served satellite gateways with sufficient duration for mobility anchoring and handover

[0062] - A feeder link or radio link between the satellite gateway and the satellite (or UAS platform)

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

[0064] - Satellites (or UAS platforms) that can implement transparent or regenerative (with on-board processing) payloads. The satellites (or UAS platforms) generate beams, typically generating several beams over a given service area bounded by their field of view. The occupied area of the beam is typically an elliptical shape. The field of view of the satellites (or UAS platforms) depends on the on-board antenna pattern and the minimum elevation angle.

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

[0066] - Regenerative payload: RF filtering, frequency conversion, and amplification, as well as demodulation / decoding, switching, and / or routing, encoding / modulation. This effectively is equivalent to implementing all or part of the base station functions (e.g., gNB) on-board the satellite (or UAS platform).

[0067] - Inter-satellite links (ISL), optionally in the case of a satellite constellation. This would require regenerative payloads on-board the satellites. The ISL can operate in the RF frequency or optical band.

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

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

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

[0071]

[0072] Typically

[0073] ● GEO satellites and UAS are used to provide continental, regional, or local services.

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

[0075] HEO satellite systems are not considered in this article.

[0076] *********************** Next Citation *********************

[0077] 5.2 Regenerative Satellites Based on the NG-RAN Architecture

[0078] 5.2.1 Payload Processed by gNB

[0079] 5.2.1.1 Overview

[0080] The NG-RAN logical architecture described in TS 38.401 is used as a baseline for the NTN scenario.

[0081] The satellite payload implements the regeneration of signals received from the Earth.

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

[0083] ● The satellite radio interface (SRI) on the feeder link between the NTN gateway and the satellite.

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

[0085] Figure 7 is in 3GPP TR 38.821 V16.0.0 Figure 5 .2.1-1: Representation of a regenerative satellite without ISL, payload processed by gNB.

[0086] Note: The satellite may initiate additional service routing functions outside the RAN scope.

[0087] The satellite payload also provides an inter-satellite link (ISL) between satellites

[0088] The ISL (Inter-Satellite Link) is the transmission link between satellites. The ISL can be a radio interface or an optical interface, which can be defined by 3GPP or non-3GPP, but this is not within the scope of the research project.

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

[0090] Figure 8 is in 3GPP TR 38.821 V16.0.0 Figure 5 .2.1-2: Representation of a regenerative satellite with ISL, payload processed by gNB.

[0091] The figure above shows that a UE served by a gNB on a satellite can access the 5GCN via the ISL.

[0092] gNBs on different satellites can be connected to the same 5GCN on the ground.

[0093] If the satellite hosts more than one gNB, then the same SRI will transport all corresponding NG interface instances.

[0094] ********************** Next citation *********************

[0095] 5.2.2 Payload Processed by gNB-DU

[0096] 5.2.2.1 General Description

[0097] The NG-RAN logical architecture with CU / DU split described in TS 38.401 is used as the baseline for the NTN scenario.

[0098] The satellite payload implements the regeneration of signals received from the Earth.

[0099] ● The NR-Uu radio interface on the serving link between the satellite and the UE

[0100] ● The satellite radio interface (SRI) on the feeder link between the NTN gateway and the satellite. The SRI transports the F1 protocol.

[0101] The satellite payload can provide an inter-satellite link between satellites.

[0102] The SRIs (satellite radio interfaces) are transport links; the logical interface F1 they transport is specified by 3GPP.

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

[0104] DUs on different satellites can be connected to the same CU on the ground.

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

[0106] Figure 9 is from 3GPP TR 38.821 V16.0.0 Figure 5 .2.2-1: Reproduction of the NG-RAN with a regenerative satellite based on gNB-DU.

[0107] *********************** End of Quotation ***********************

[0108] In 3GPP TR 22.865 ([2] 3GPP TR 22.865 V2.0.0), the store-and-forward (S&F) operation is introduced. S&F is an operation mode of the 5G system with satellite access, where the 5G system can provide a certain level of service (in terms of storing and forwarding data) when satellite connectivity is intermittently / temporarily unavailable, e.g., providing communication services for UEs under satellite coverage without a simultaneous active feeder link connection to the ground segment.

[0109] [2] Further details are also specified in 3GPP TR 22.865 V2.0.0, including use cases and potential requirements for S&F operations:

[0110] ********************* Citation begins *********************

[0111] Annex A (Informative):

[0112] Store-and-Forward Satellite Operations

[0113] Store-and-Forward satellite operations in a 5G system with satellite access are intended to provide a certain level of communication service to UEs under satellite coverage with intermittent / temporary satellite connectivity (e.g., when the satellite is not connected to the terrestrial network via a feeder link or via an ISL), to provide delay-tolerant communication services.

[0114] An example of "S&F satellite operations" is shown in Figure A-1, in contrast to the "normal / default satellite operations" assumption of what can currently be considered a 5G system with satellite access.

[0115] As shown in Figure A-1:

[0116] - In the "normal / default satellite operations" mode, the exchange of signaling and data traffic between a UE with satellite access and a remote terrestrial network requires both the service link and the feeder link to be active simultaneously, so that when the UE interacts with the satellite via the service link, there is a continuous end-to-end connection path between the UE, the satellite, and the terrestrial network.

[0117] - In contrast, in the "S&F satellite operations" mode, the end-to-end exchange of signaling / data traffic is now handled as a combination of two steps that are not simultaneous in time (Steps A and B in Figure A-1). In Step A, the signaling / data exchange occurs between the UE and the satellite without the satellite being simultaneously connected to the terrestrial network (i.e., the satellite can operate the service link without an active feeder link connection). In Step B, a connection is established between the satellite and the terrestrial network so that communication can occur between the satellite and the terrestrial network. Thus, the satellite moves from being connected to the UE in Step A to being connected to the terrestrial network in Step B.

[0118] Figure 10 is a reproduction of Figure A-1 in 3GPP TR 22.865 V2.0.0: Illustration of "Normal / Default Operation" and "S&F Operation" Modes in a 5G System with Satellite Access.

[0119] The concept of "store and forward" (S&F) services is widely applied in the fields of delay-tolerant networks and disruption-tolerant networks. In the 3GPP context, the service that can be assimilated to the S&F service is SMS, for which there is no need to have 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 endpoints and the SMSC that acts as an intermediate node responsible for storage and relay.

[0120] The support for S&F satellite operations is particularly applicable to the delivery of delay-tolerant / non-real-time IoT satellite services by NGSO satellites.

[0121] ********************* Next citation *********************

[0122] 5.1 Use cases of store and forward - MO

[0123] 5.1.1 Description

[0124] This use case shows the implementation of the S&F service between a UE with satellite access and an application server for delay-tolerant / non-real-time IoT NTN services in the case of a mobile-originated message.

[0125] A description of the store and forward operation is provided in Appendix A.

[0126] TrackingInc provides remote monitoring services for sites and deploys and tracks many battery-powered IoT-type UEs globally. All IoT remote monitoring UEs deployed include 5G communication with satellite access. Some UEs are deployed in remote areas where there is no mobile coverage of MNOs and only satellites are possible.

[0127] For satellite access, TrackingInc uses the services of IoTSAT for 5G IoT connectivity via satellite, and IoTSAT uses a LEO constellation that supports the S&F operating mode.

[0128] All IoT remote monitoring UEs regularly send information related to the areas they monitor to TrackingInc's application server and sometimes receive new parameters from the application server. In most cases, the messages exchanged are delay-tolerant / non-real-time IoT.

[0129] 5.1.2 Preconditions

[0130] In this use case, the IoT remote monitoring UE is in a remote area where there is no ground station available for feeder link connectivity, and the IoT remote monitoring UE knows that the IoTSAT constellation operates in the S&F mode.

[0131] 5.1.3 Service Flow

[0132] The IoT remote monitoring UE needs to send messages to the TrackingInc application server. The UE waits for satellite network coverage and sends its messages when a satellite passes by.

[0133] The IoT remote monitoring UE and the satellite providing coverage interact via a service link, allowing the UE to transmit messages to the satellite, which does not have connectivity to the ground segment. And thus, the satellite must locally store the received messages.

[0134] At this time:

[0135] 1. A limit on the size / quantity of data that can be sent from the UE can be imposed.

[0136] 2. A forwarding priority for the stored data to the ground station and a data retention period for the exchanged data can be established.

[0137] 3. An acknowledgement for the data received by the satellite can be issued.

[0138] At a later time, the satellite with the stored messages establishes connectivity with the ground network via a feeder link and relays / forwards / downloads the messages to the ground network. Once the feeder link is available, all the accumulated and stored MO messages are delivered to the ground. Meanwhile, all the accumulated and stored relevant MT messages are also delivered to the satellite via the same feeder link, which will significantly affect the performance of the feeder link, 5GC, and the satellite. Therefore, relevant performance optimization methods will be considered.

[0139] Based on the established connectivity configuration and routing, the ground network delivers the messages to the TrackingInc application server.

[0140] 5.1.4 Post - condition

[0141] The messages generated by the IoT remote monitoring UE have been successfully delivered to the TrackingInc application server without relying on a continuous end - to - end network connectivity path in between, or in the case where the data retention period has been exceeded, the messages have been discarded.

[0142] ********************* Next Quote ***********************

[0143] 5.2 Store - and - Forward Use Case - MT

[0144] 5.2.1 Description

[0145] This use case illustrates the implementation of the S&F service between a UE with satellite access and an application server for delay-tolerant / non-real-time IoT NTN services in the case of a mobile-terminated message.

[0146] A description of the store-and-forward operation is provided in Appendix A.

[0147] TrackingInc provides remote monitoring services for sites and deploys and tracks many battery-powered IoT-type UEs globally. All IoT remote monitoring UEs deployed include 5G communication with satellite access. Some UEs are deployed in remote areas where there is no mobile coverage from an MNO and only satellite is possible.

[0148] For satellite access, TrackingInc uses the services of IoTSAT for 5G IoT connectivity via satellite, and IoTSAT uses a LEO constellation that supports the S&F operation mode.

[0149] All IoT remote monitoring UEs regularly send information related to the areas they monitor to TrackingInc's application server and sometimes receive new parameters from the application server. In most cases, the messages exchanged are delay-tolerant / non-real-time IoT.

[0150] 5.2.2 Preconditions

[0151] In this use case, the IoT remote monitoring UE is in a remote area where there is no ground station available for feeder link connectivity, and the IoT remote monitoring UE knows that the IoTSAT constellation is operating in the S&F mode.

[0152] 5.2.3 Service Flow

[0153] The TrackingInc application server needs to send new parameters to the IoT remote monitoring UE. Based on the information provided by the network, the application server knows that the communication with the UE is in the S&F mode.

[0154] The TrackingInc application server message will send the new parameters to the network entry point (e.g., SCEF, PDN-GW, SMSC) via a dedicated message in a conventional way (e.g., IP routing, tunneling), and additional information about delivery priority, confirmation, etc. can be provided to the network.

[0155] At this time:

[0156] 4. A limit can be imposed on the amount of data to be delivered to the IoT remote monitoring UE.

[0157] 5. A forwarding priority to the UE can be established.

[0158] 6. A confirmation of data received by the network can be sent to the application server, possibly with additional information about store-and-forward, e.g., the estimated time of delivery of the message.

[0159] 7. An end-to-end confirmation policy can be established.

[0160] The network stores the message until the message can be delivered / relayed to a satellite that is expected to fly over and provide coverage to the destination IoT remote monitoring UE.

[0161] When the satellite is connected to the terrestrial network via the feeder link, the message is uploaded to the satellite. All the accumulated and stored MT messages are uploaded to the satellite via the feeder link. At the same time, all the accumulated and stored MO messages are also delivered to the 5GC via the same feeder link, which will cause performance impacts on the feeder link, the satellite, and the 5GC. Performance optimization methods are needed here. When flying over the area where the IoT remote monitoring UE is located, the satellite with the stored message triggers paging on the service link for the UE to connect to the network. (How does the satellite know where to page the UE (e.g., it has to associate the stored data with the location of the UE and its UE identity)? And what happens if the UE moves?)

[0162] The stored message is delivered / downloaded from the satellite to the IoT remote monitoring UE. A confirmation can be requested / sent. A mechanism to ensure the integrity of the delivered information can be in place.

[0163] 5.2.4 Postconditions

[0164] The message generated by the TrackingInc application server has been successfully delivered to the IoT remote monitoring UE, independent of a continuous end-to-end network connectivity path in between.

[0165] ********************* Next Quote ***********************

[0166] 5.4 Use Case of Store-and-Forward - Data Delivery for IoT Devices in Remote Areas

[0167] 5.4.1 Description

[0168] Data transfer at remote sites is a very common requirement. Research institutions can obtain data from remote sites for scientific research, e.g., animal tracking [5]. Government agencies can obtain data from remote sites via remote sensing, e.g., for disaster mitigation and avoidance [6]. Commercial companies can obtain data from remote sites for proper resource allocation. Data transfer at many remote sites is delay-insensitive, and satellite coverage does not always ensure satellite connection to both service links and feeder links. In the past 30 years, many scholars have been dedicated to studying the data transfer problem at remote sites and developing store-and-forward mechanisms to solve the problem [7][8][9].

[0169] In remote areas, there is no terrestrial network for various reasons, e.g., it is difficult to build and maintain communication towers. This thus makes it challenging to collect information in these areas for environmental protection purposes. For example, sensors installed on animals need to be monitored regularly. In this scenario, the sensors installed on animals send status information such as the movement, physiological functions, and the state of the surrounding environment of the animal to the satellite; and the satellite stores the received status information of the animal and forwards the information to the science center when the feeder link becomes available.

[0170] 5.4.2 Prerequisites

[0171] EA Science Center has installed sensors (IoT devices) on animals to collect information in these remote areas for environmental protection purposes. Satelles, as a satellite communication operator, has initiated store-and-forward satellite operations to support data transfer in remote areas. EA Science Center has signed a contract with Satelles to allow the sensors installed on animals to send status information (e.g., the movement, physiological functions, and the surrounding environment of the animal) to the science center via the satellite.

[0172] The satellite and IoT devices are correctly configured with sufficient information, e.g., credentials / certificates required for the devices to verify the authenticity of the satellite.

[0173] 5.4.3 Service Flow

[0174] Figure 11 is in 3GPP TR 22.865 V2.0.0 Figure 5 .4.3-1: Reproduction of animal tracking in remote areas.

[0175] 1. IoT devices are installed on animals and powered on. They are registered in the 5G network for store-and-forward satellite operations. The satellite with store-and-forward capabilities enables IoT devices to transfer data to the network even when the feeder link to the ground is unavailable. A secure connection is established between the IoT devices and the satellite to protect data security and privacy.

[0176] 2. The IoT device sends sensor status information to the satellite, and the satellite stores the sensor status information received from the IoT device.

[0177] 3. When the satellite has a feeder link available for the ground segment, the satellite forwards the sensor status information and other necessary information to the ground core network. The ground core network verifies the IoT device based on the received information; if permitted, then the ground core network forwards the sensor status information to its destination data network.

[0178] 4. The ground core network sends the operation result to the satellite (either the same satellite or a different satellite passing through the remote area).

[0179] 5. When the satellite (or the next satellite) passes through the remote area, the satellite pages the UE, and based on the result received from the ground core network, the satellite sends the operation result to the IoT device.

[0180] 6. If the IoT device needs to update the sensor status information, it can send it to the satellite when connected to the satellite. The satellite stores it and forwards the sensor status information to the ground core network when the feeder link is available.

[0181] 5.4.4 Post - condition

[0182] After the scientific center receives the sensor status information, the scientist can analyze the sensor status information and track the animal status.

[0183] ********************* Next citation ***********************

[0184] 5.16 Store - and - Forward Use Case - Emergency Report

[0185] 5.16.1 Description

[0186] This use case illustrates the implementation of the S&F service between a UE with satellite access and an application server for an emergency reporting service.

[0187] A description of the store - and - forward operation is provided in Appendix A.

[0188] Bob is sailing on an intercontinental container ship that sinks for some external reason. Bob is now stranded on a remote island. Although he is not in immediate danger, he needs to be rescued within a few days as food and water are scarce.

[0189] Several items on the container ship were washed ashore with Bob. One of them is an IoT device from TrackingInc, which has a subscription to IoTSAT for 5G IoT connectivity via satellite, and IoTSAT uses a LEO constellation that supports the S&F operating mode.

[0190] The IoT device allows Bob to send an emergency report containing his location via the S&F network. The IoT device receives confirmation to "pass" the emergency report as soon as possible. When the indicator light of the emergency button on the IoT device starts to flash green, Bob knows it's only a matter of time before Alice comes to rescue him.

[0191] 5.16.2 Prerequisites

[0192] In this use case, the emergency reporting UE is in a remote area without a ground station available for feeder link connectivity, and the emergency reporting UE knows that the IoTSAT constellation is operating in the S&F mode.

[0193] 5.16.3 Service Flow

[0194] 1. Bob is sailing on an intercontinental container ship, and the ship sinks.

[0195] 2. Bob is on shore and finds an IoT device from TrackingInc, which has a subscription to IoTSAT for 5G IoT connectivity via satellite.

[0196] 3. Bob uses the IoT device from TrackingInc to send an emergency report containing his location via IoTSAT.

[0197] 4. Bob's emergency report is received by a passing satellite of the IoTSAT constellation and stored in the satellite waiting for delivery because there is no available feeder link in the area where Bob is on shore.

[0198] 5. The satellite of the IoTSAT constellation can deliver the "emergency report" from Bob within seconds once the first feeder link becomes available because it identifies the service as an emergency and there are no restrictions on using any feeder link and ground station for such services.

[0199] 6. Inform Bob during the next flyover of the satellite from the IoTSAT constellation that the emergency report has been delivered.

[0200] 5.16.4 Postconditions

[0201] The emergency report generated by the IoT UE has been successfully delivered to the TrackingInc application server and forwarded to the service capable of processing the report, and the response has been forwarded to the IoT UE without relying on the continuous end-to-end network connectivity path therebetween.

[0202] *********************** Next citation ***********************

[0203] 6.2 Store-and-Forward Satellite Operations

[0204] The potential requirements corresponding to the supported store-and-forward satellite information are listed in the following table.

[0205] Table 6.2-1 - Comprehensive Requirements for Store-and-Forward Satellite Operations

[0206]

[0207]

[0208]

[0209] ********************* Citation ends ***********************

[0210] In [4] 3GPP RWS-230178, it is specified that in areas with discontinuous coverage where it is not feasible or economical to deploy a ground station (GS), there can also be an intermittent feeder link (FL) connectivity to the ground station. The potential call flow specified for the intermittent feeder link:

[0211] *********************** Citation from ***********************

[0212] Figure 12 is a reproduction of the figure of the possible call flow for the intermittent feeder link in 3GPP RWS-230178.

[0213] *********************** Citation ends *********************

[0214] In 3GPP TS 23.501 ([3] 3GPP TS 23.501 V18.1.0), the 5G system architecture is shown:

[0215] *********************** Citation Start ***********************

[0216] 4.2.3 Non-roaming reference architecture

[0217] Figure 4 .2.3-1 depicts the non-roaming reference architecture. Service-based interfaces are used within the control plane.

[0218] Figure 13 from 3GPP TS 23.501 V18.1.0 Figure 4 .2.3-1: Reproduction of the non-roaming 5G system architecture.

[0219] ********************* Citation End *********************

[0220] A non-terrestrial network (NTN) is a network that provides non-terrestrial access to user equipment (UE), e.g., by means of an NTN payload and an NTN gateway mounted on an airborne or spaceborne NTN vehicle. The NTN may include one or more network nodes, such as next-generation radio access network (NG-RAN) nodes or next-generation Node B (gNB). The UE may link to, camp on, and / or connect to the NTN network for transmission and / or reception.

[0221] The NTN may include various platforms, including low Earth orbit (LEO) satellites, medium Earth orbit (MEO) satellites, highly elliptical orbit (HEO) satellites, geostationary Earth orbit (GEO) satellites, geostationary-synchronous orbit (GSO) satellites, non-geostationary-synchronous orbit (NGSO) satellites, and / or high-altitude platform stations (HAPS). LEO satellites may have Earth-fixed beams (e.g., the beam is temporarily fixed at a position during a time period) or Earth-moving beams (e.g., the beam moves continuously together with the satellite). LEO satellites may serve / provide Earth-moving cells (e.g., with Earth-fixed beams) and / or (quasi) Earth-fixed cells (e.g., with Earth-moving beams).

[0222] The NTN may provide wide-area coverage and provide network (NW) access in scenarios where a terrestrial network (TN) is not feasible (e.g., deserts, polar regions, and / or on an aircraft). More details on different NTN platforms can be found in TR38.821 ([1] 3GPP TR 38.821 V16.0.0).

[0223] Store-and-Forward (S&F) operations can be considered as an operating mode for satellite access, which provides a certain level of service (in terms of storing and forwarding data) when satellite connectivity is intermittently / temporarily unavailable. For example, it provides communication services for UEs under satellite coverage without the need for a simultaneous active feeder link connection to the ground segment.

[0224] A network supporting S&F operations can be based on a regenerative payload architecture (e.g., as specified in [1] 3GPP TR38.821 V16.0.0). The network can include a Radio Access Network (RAN) and / or a Core Network (CN). The RAN can include one or more RAN nodes. The CN can include one or more CN nodes. The RAN (or RAN node) can be (or include) an NG-RAN node, a gNB, a gNB Distributed Unit (DU), a gNB Central Unit (CU), an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) node, an Evolved Node B (eNB), and / or a base station. The CN (or CN node) can 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), and / or a network node specified in TS 23.501 ([3] 3GPP TS 23.501 V18.1.0).

[0225] A network (e.g., a 5G system) can be divided into two parts. One part of the network, which includes one or more network nodes or network segments, is located on the satellite. The other part of the network, which includes one or more network nodes or network segments and is not located on the satellite, is located on the ground. The network nodes and / or network segments can be one or more network nodes (e.g., RAN nodes or CN nodes) and / or a part and / or combination of the network nodes mentioned above or not mentioned above. For simplicity, the network, network nodes, and / or network segments located in the satellite (or the relevant network mentioned above, for example) can be referred to as the NW on the satellite (or satellite NW). The network, network nodes, and / or network segments located on the ground (or the relevant network mentioned above, for example) can be called the NW on the ground (or ground NW).

[0226] For example, the satellite NW may be (or include) a RAN (e.g., NG-RAN, gNB, and / or eNB). The terrestrial NW may be (or include) a CN (e.g., EPC, 5GC, MME, S-GW, AMF, and / or UPF). For example, the satellite NW may be (or include) a gNB-DU. The terrestrial NW may be (or include) a gNB-CU and / or one or more CN nodes (e.g., AMF, UPF). For example, the satellite NW may 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). The terrestrial NW may be the other one or more CN nodes (or segments) (e.g., the part excluding the satellite NW).

[0227] For example, the satellite NW may be (or include) a first part of the MME (e.g., on the satellite). The terrestrial NW may be (or include) a second part of the MME (e.g., on the ground). The first part of the MME and the second part of the MME may be different. The first part and the second part of the MME may be mutually exclusive.

[0228] The link / connection / interface between the satellite NW and the terrestrial NW may be referred to as a feeder link. The link / connection / interface between the satellite NW and the UE may be referred to as a service link. Figure 14 Examples are shown in.

[0229] Based on TR 22.865 ([2] 3GPP TR 22.865 V2.0.0), a 5G system with satellite access should be able to inform the UE of the requirement to apply the "store and forward" operation. And in [4] 3GPP RWS-230178, a feeder link absence indication may be included in the release message to the UE. To let the UE know whether the satellite network is operating in the "store and forward" (S&F) mode, the network may need to provide an indication of the purpose to the UE. When the UE does not receive this indication, the UE may consider that the satellite network is not operating in the S&F mode and / or is operating in the normal mode (or default mode).

[0230] However, the UE can only know immediately after receiving the indication that the satellite network is changing the operation mode (e.g., the S&F mode). The method of detecting the operation mode (e.g., the S&F mode) based only on the indication may have some disadvantages:

[0231] - For example, consider the case of an operation mode switch from the S&F mode to the normal mode, as Figure 15As shown, for a UE that does not support S&F operations, the UE may not be connected to the cell when the cell is operating in the S&F mode (e.g., consider the cell as prohibited). However, since the UE does not know when the cell will switch the operating mode to the normal mode, the UE cannot quickly connect to the cell after the cell switches to the normal mode.

[0232] - For example, consider the case of an operating mode switch from the normal mode to the S&F mode, as Figure 16 shown, since the UE does not know when the cell will switch to the S&F mode, the UE may initiate a scheduling request (SR) / buffer status report (BSR) at the end of the normal mode (e.g., after non-S&F data arrives), which may cause useless signaling overhead and power consumption.

[0233] - For example, if an indication is provided via system information, for a narrowband Internet of Things (NB-IoT) UE, the UE needs to move to the idle mode to re-acquire the system information, which also causes additional signaling overhead.

[0234] Since the operating mode of the satellite network can depend on whether the feeder link is available, the availability of the feeder link can be predictable (e.g., based on the movement of the satellite in its orbit). It can be beneficial for the UE to know in advance when the satellite network will operate in the S&F mode (or switch from the default / normal mode to the S&F mode). Information in addition to (or as a supplement to) the indication can be used for this purpose.

[0235] The following terms may be interchangeable: S&F (store and forward) mode, S&F (store and forward) operation, and / or non-real-time (RT) mode.

[0236] The following terms may be interchangeable: normal mode, normal operation, default mode, default operation, RT (real-time) mode, RT (real-time) operation, non-S&F mode, and / or non-S&F operation.

[0237] To solve the problem, (one or more) information indicating (or for deriving) the time for S&F operations (and / or the time related to the feeder link) can be provided to the UE. The time for S&F operations can be (or include) the time to start S&F operations, the time to end S&F operations, and / or the duration (or time period) of S&F operations. The time related to the feeder link can be (or include) the time when the feeder link becomes available, the time when the feeder link becomes unavailable, and / or the duration (or period) of the feeder link being unavailable. The information can be an estimated or expected value. The information can include one or more elements, such as a time element, a feature indication, and / or a boolean bit.

[0238] The information may be included in system information (e.g., System Information Block (SIB)). The information may be included in dedicated signaling (e.g., Radio Resource Control (RRC) message, RRC reconfiguration message). The information may not be an ephemeris (e.g., associated with a cell, associated with a network, associated with a satellite). The information may be provided in addition to an ephemeris (e.g., associated with a cell, associated with a network, associated with a satellite).

[0239] A network node may provide information when it is in the S&F mode. A network node may provide information when it is in the default mode (or normal mode). A network node may provide information before it operates in the S&F mode. A network node may provide information before it enters (or switches to, or enables, or activates) the S&F mode (from the normal / default mode). A network node may provide information when the feed link of the network node is unavailable. A network node may provide information when the feed link of the network node is available. A network node may provide information when the serving link of the network node is available. A network node may be (or include, or be replaced by) a network, a radio access network, a cell, an NTN cell, a base station, an eNB, a gNB, a satellite, and / or a satellite network.

[0240] The information may be used for (or associated with, or corresponding to) a network (e.g., a satellite network), a network node, a cell (e.g., an NTN cell). The cell may be the serving cell of the UE. The cell may be an adjacent cell of the UE.

[0241] A UE may receive information when it is in the S&F mode. A UE may receive information when it is not in the S&F mode. A UE may receive information when it is in the normal / default mode. A UE may receive information before it operates in the S&F mode. A UE may receive information before it enters (or switches to, or enables, or activates) the S&F mode (from the normal / default mode). A UE may receive information when the feed link of the UE is unavailable. A UE may receive information when the feed link of the UE is available. A UE may receive information when the serving link of the UE is available.

[0242] The said one or more information may indicate or may be used (by the UE) to derive at least one or more of the following:

[0243] - The time to start (or expected to start) S&F operation; and / or

[0244] - The time to end (or expected to end) S&F operation; and / or

[0245] - The (expected / estimated) duration (or time period) of the S&F operation; and / or

[0246] - The time to enter (or enable, or activate) the S&F mode (e.g., from the default / normal mode); and / or

[0247] - The time to leave (or deactivate, or deactivate) the S&F mode (e.g., to the default / normal mode); and / or

[0248] - The time to switch the operating mode (e.g., between the S&F mode and the default / normal mode); and / or

[0249] - The time when the feed link will be (or become) unavailable (or is expected to be unavailable); and / or

[0250] - The time when the feed link will (or become) available (or is expected to be available); and / or

[0251] - The (expected / estimated) duration (or time period) when the feed link is unavailable; and / or

[0252] - Whether the S&F operation is enabled (or not); and / or

[0253] - Whether S&F operation is allowed (or not); and / or

[0254] - Whether the S&F operation is supported (or not).

[0255] More than one piece of information can be provided to the UE. Different information can indicate different things. For example, the first piece of information can indicate the time related to the S&F operation. The second piece of information can indicate the time related to the status of the feed link. For example, the first piece of information can indicate the time to switch the operating mode. The second piece of information can indicate the duration of the operating mode.

[0256] The information can be (or include) absolute time, relative time, and / or time relative to a time reference. For example, the information can be (or include) the time after 00:00:00 on January 1, 1900 in the Gregorian calendar (midnight between Sunday, December 31, 1899 and Monday, January 1, 1900). The information can be indicated in multiples of 10 ms. For example, the information can be (or include) a frame number (e.g., a system frame number (SFN) and / or a subframe number).

[0257] Based on (at least) the (one or more) information, the UE can determine (whether / when) to apply (or use) the S&F operation. The UE can (determine) to apply the S&F operation, for example, during the period indicated (or derived) by the information. The UE can (determine) not to apply the S&F operation, for example, outside the period indicated (or derived) by the information (or at least for a period outside the said period).

[0258] Based on (at least) the said (one or more) information, the UE can determine (whether / when) to start S&F operations (or enter / enable / activate the S&F mode). The UE can (determine) to start (applying) S&F operations, for example, at the time indicated (or derived) by the said information. The UE can (determine) to enter / enable / activate the S&F mode, for example, at the time indicated (or derived) by the said information (e.g., from the default / normal mode).

[0259] Based on (at least) the said (one or more) information, the UE can determine (whether / when) to stop S&F operations (or leave / deactivate / de - activate the S&F mode). The UE can (determine) to stop (applying) S&F operations, for example, at the time indicated (or derived) by the said information. The UE can (determine) to leave / deactivate / de - activate the S&F mode, for example, at the time indicated (or derived) by the said information (e.g., to the default / normal mode).

[0260] Based on (at least) the said (one or more) information, the UE can determine (whether / when) to switch the operation mode. The operation mode can include the S&F mode, the default mode, and / or the normal mode. The UE can (determine) to switch to the S&F mode, for example, at the time indicated (or derived) by the said information (e.g., from the normal / default mode). The UE can, for example, switch to the normal / default mode at the time indicated (or derived) by the said information (e.g., from the S&F mode).

[0261] Based on (at least) the said (one or more) information, the UE can determine (whether / when) to apply (at least) the configuration related to S&F. The UE can (determine) to apply (at least) the configuration related to S&F, for example, at the time indicated (or derived) by the said information. The UE can (determine) to start applying (at least) the configuration related to S&F, for example, at the time indicated (or derived) by the said information. The UE can (determine) to release (at least) the configuration related to S&F, for example, at the time indicated (or derived) by the said information. The UE can (determine) to stop applying (at least) the configuration related to S&F, for example, at the time indicated (or derived) by the said information. The S&F configuration can be provided to the UE before the UE uses (or applies) S&F operations.

[0262] Based on (at least) the said (one or more) information, the UE can determine (whether) to transmit S&F data. The S&F data can be (or include) delay - tolerant data, small data, data that allows the use of S&F operations (or mode), and / or data that is configured to use S&F operations (or mode).

[0263] Based on the (at least) said (one or more) information, the UE can determine whether to allow (or prohibit) S&F data transmission. The UE can determine, for example, to allow (or prohibit) S&F data transmission at the time indicated (or derived) by the said information. The UE can determine, for example, to allow (or prohibit) S&F data transmission during the time period indicated (or derived) by the said information. The UE can determine, for example, to allow (or prohibit) S&F data transmission outside the time period indicated (or derived) by the said information (or at least for a period of time outside the said time period).

[0264] In one or more instances, if there is S&F data arrival at the UE (e.g., becomes available or waits for transmission), the UE can determine whether to use or request (uplink) resources for (uplink) data transmission (e.g., for S&F data). The request can be (or include): a scheduling request, a random access preamble, a connection request, a registration request, a service request, and / or a PDU session establishment request.

[0265] In one or more instances, if S&F data transmission is in progress, the UE can determine whether to continue (or cancel) the transmission based on the said information (or based on the S&F indication). If the UE is about to leave the S&F mode (e.g., the remaining time before leaving the S&F mode is approaching), the UE can determine to continue (or cancel) the transmission. The UE can, for example, continue (or cancel) the transmission at the time indicated (or derived) by the said information (e.g., when the UE leaves / deactivates / deractivates the S&F mode). The UE can continue (or cancel) the transmission when leaving the S&F mode (or in response to this, or after this).

[0266] In one or more instances, if a request is pending, the UE can determine whether to continue (or cancel) the request based on the said information (or based on the S&F indication). If the UE is about to leave / deactivate / deractivate the S&F mode (e.g., the remaining time before leaving the S&F mode is approaching), the UE can determine to continue (or cancel) the request. The UE can, for example, continue (or cancel) the request at the time indicated (or derived) by the said information (e.g., when the UE leaves / deactivates / deractivates the S&F mode). The UE can continue (or cancel) the request when leaving the S&F mode (or in response to this, or after this).

[0267] Based on the (at least) one or more pieces of information, the UE can determine whether to transmit non-S&F data. Based on the (at least) one or more pieces of information, the UE can determine whether to request (or use) uplink resources for the transmission of (e.g., non-S&F data). Non-S&F data can be (or include) data other than S&F data, non-tolerant-to-delay data, delay-sensitive data, data prohibited from using S&F operations (or modes), and / or data not configured to use S&F operations (or modes). The request can be (or include) an SR and / or a BSR.

[0268] Based on the (at least) one or more pieces of information, the UE can determine whether to allow (or prohibit) non-S&F data transmission. The UE can (determine) to allow (or prohibit) non-S&F data transmission, for example, at the time indicated (or derived) by the information. The UE can (determine) to allow (or prohibit) non-S&F data transmission, for example, during the period indicated (or derived) by the information. The UE can (determine) to allow (or prohibit) non-S&F data transmission, for example, outside the period indicated (or derived) by the information (or at least for a period of time outside the period).

[0269] In one or more instances, if non-S&F data arrives at the UE (e.g., becomes available), the UE can determine based on the information whether to use uplink resources for non-S&F data transmission. If the UE is about to enter / enable / activate the S&F mode (e.g., the remaining time before entering / enabling / activating the S&F mode is not sufficient), the UE can (determine) not to use uplink resources for non-S&F data transmission. The remaining time can be derived by (or based on) the (at least) one or more pieces of information.

[0270] In one or more instances, if non-S&F data arrives at the UE (e.g., becomes available), the UE can determine based on the information whether to request uplink resources for non-S&F data transmission. If the UE is about to enter / enable / activate the S&F mode (e.g., the remaining time before entering / enabling / activating the S&F mode is not sufficient), the UE can (determine) not to request uplink resources for non-S&F data transmission. The remaining time can be derived by (or based on) the (at least) one or more pieces of information. The request can be (or include): a scheduling request, a random access preamble, a connection request, a registration request, a service request, and / or a PDU session establishment request.

[0271] In one or more instances, if a request for non-S&F data (or triggered by it) has been triggered (or is pending), the UE may determine (whether to) cancel the request based on the information (or based on an S&F indication). If the UE is about to enter / enable / activate the S&F mode (e.g., there is not enough remaining time before entering / enabling / activating the S&F mode), the UE may (determine to) cancel the request. The UE may cancel the request, for example, at the time indicated (or derived) by the information (e.g., when the UE enters / enables / activates the S&F mode). The UE may cancel the request when entering / enabling / activating the S&F mode (or in response thereto).

[0272] In one or more instances, if non-S&F data transmission is in progress, the UE may determine (whether to) cancel the transmission based on the information (or based on an S&F indication). If the UE is about to enter / enable / activate the S&F mode (e.g., there is not enough remaining time before entering / enabling / activating the S&F mode), the UE may (determine to) cancel the transmission. The UE may cancel the transmission, for example, at the time indicated (or derived) by the information (e.g., when the UE enters / enables / activates the S&F mode). The UE may cancel the transmission when entering / enabling / activating the S&F mode (or in response thereto).

[0273] Based on (at least) the (one or more) information, the UE may determine (whether to) initiate (or suspend) a specific procedure (and / or function). The UE may (determine to) initiate (or suspend) the specific procedure (and / or function), for example, at the time indicated (or derived) by the information. The UE may (determine to) initiate (or suspend) the specific procedure (and / or function), for example, during the period indicated (or derived) by the information. The UE may (determine to) initiate (or suspend) the specific procedure (and / or function), for example, outside the period indicated (or derived) by the information (or at least for a period of time outside the said period).

[0274] In one or more instances, if a procedure cannot be initiated in the S&F mode (or using S&F operations) and the UE derives that the remaining time before entering / enabling / activating the S&F mode is not enough (e.g., not enough to complete the procedure), the UE may determine to suspend (or not initiate) the procedure. The remaining time may be derived by (or based on) (at least) the information.

[0275] Based on the (at least) said (one or more) information, the UE can determine whether to allow or prohibit a specific program. The UE can determine, for example, to allow or prohibit a specific program (and / or function) at the time indicated (or derived) by the information. The UE can determine, for example, to allow or prohibit a specific program (and / or function) during the time period indicated (or derived) by the information. The UE can determine, for example, to allow or prohibit a specific program (and / or function) outside the time period indicated (or derived) by the said information (or at least for a period of time outside the said time period).

[0276] In one or more instances, if a program is not allowed in the S&F mode (or using S&F operation), and the UE derives that the remaining time before entering / enabling / activating the S&F mode is not sufficient (e.g., not sufficient to complete the program), then the UE can determine to prohibit or not allow the program. The remaining time can be derived based on the said information.

[0277] In one or more instances, if a program (or function) triggered by non-S&F data (or due to the said data, or based on the said data) is pending (or in progress), then the UE can determine to cancel or continue the program (or function) based on the said information. If the UE is about to enter / enable / activate the S&F mode (e.g., the remaining time before entering / enabling / activating the S&F mode is not sufficient), then the UE can determine to cancel the program (or function). The UE can cancel the program (or function), for example, at the time indicated (or derived) by the information (e.g., when the UE enters / enables / activates the S&F mode). The UE can cancel the program (or function) when entering / enabling / activating the S&F mode (or in response thereto).

[0278] In one or more instances, the UE can determine whether to access (or connect to, or pre-empt, or prohibit) a cell (or network, or satellite) based on the (at least) said (one or more) information. The cell can be an adjacent cell, a candidate cell, and / or a serving cell. The UE can determine the current operation mode of the cell (or network, or satellite) based on the said information. The operation mode can be (or include) the S&F mode, the normal mode, and / or the default mode. If (at least) the UE determines that the current operation mode is the S&F mode, then the UE can not access (or connect to, or pre-empt) the cell (or network, or satellite). If (at least) the UE determines that the current operation mode is the S&F mode, then the UE can consider the cell (or network, or satellite) as prohibited. If (at least) the UE determines that the current operation mode is the normal mode, then the UE can be allowed to access (or connect to, or pre-empt) the cell (or network, or satellite). If (at least) the UE determines that the current operation mode is the normal mode, then the UE can not consider the cell (or network, or satellite) as prohibited. The UE can be a UE that does not support S&F operation.

[0279] A specific procedure (or function) may be (or include): early data transfer, small data transfer, random access procedure, scheduling request, and / or buffer status report.

[0280] A specific procedure (or function) may be (or include): registration (or deregistration) procedure, attachment procedure, tracking area update procedure, PDU session establishment (or modification) procedure, non-access stratum (NAS) transfer procedure, packet data network (PDN) connectivity procedure, and / or service request procedure.

[0281] A specific procedure (or function) may be (or include): RRC connection establishment procedure, RRC connection re-establishment procedure, and / or RRC connection resume procedure.

[0282] A specific procedure (or function) may be triggered by (or due to) non-S&F data, e.g., arrival of non-S&F data, non-S&F data becoming available for transmission.

[0283] If at least one or more of the following conditions are met, then the UE and / or network node may be in the S&F mode (or use S&F operation):

[0284] - The feeder link of (the UE and / or network node) is unavailable; and / or

[0285] - An indication of the S&F mode (and / or enabling the S&F mode) is received (or has been transmitted); and / or

[0286] - A configuration related to (and / or enabling) the S&F mode is received (or has been transmitted); and / or

[0287] - The S&F mode of (the UE and / or network node) is enabled and / or activated.

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

[0289] - The feeder link of (the UE and / or network node) is available; and / or

[0290] - An indication of the S&F mode is not received (or transmitted); and / or

[0291] - An indication to deactivate (or deactivate) the S&F mode is received (or has been transmitted); and / or

[0292] - A configuration related to (and / or enabling) the S&F mode is not received (or has been transmitted); and / or

[0293] - A configuration to deactivate (or deactivate) the S&F mode is received (or has been transmitted); and / or

[0294] - The S&F mode (of the UE and / or network node) is deactivated and / or released.

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

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

[0297] - The UE can be aware (or informed by the NW) that the NW is (or starts to) use S&F to process data (and / or signaling); and / or

[0298] - The UE can initiate a procedure to request (or indicate) that the (satellite) NW use S&F to process data (and / or signaling); and / or

[0299] - The UE can perform the transmission of data (and / or signaling) to be processed by S&F in the (satellite) NW; and / or

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

[0301] One or more configurations ( / indications / parameters) related to S&F can be provided to the UE (e.g., in addition to information, e.g., from a network node). The configuration (and / or indication / parameter) related to S&F (or S&F configuration) can be associated (or specific) to an object. The object can be (or include) the UE, cell, connection (e.g., RRC connection, NAS connection), PDU session, and / or Quality of Service (QoS) flow. The NW can indicate (or configure) to which object the configuration (and / or indication / parameter) is associated. The NW can provide (at least) one configuration (and / or indication / parameter) to (at least) one object.

[0302] The configuration (and / or indication / parameter) related to S&F can be / include / be used to / indicate one or more of the following:

[0303] S&F Mode Indication

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

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

[0306] UE Type

[0307] The configuration can (at least) indicate which (type of) UE is allowed to use the S&F operation. The configuration can (at least) indicate which (type of) UE is allowed to perform transmission and / or reception to the NW (e.g., using the S&F operation). The transmission and / or reception can be user plane (UP) data and / or control plane (CP) signaling.

[0308] The UE type (e.g., the first type) can be based on UE capabilities, UE mobility, QoS characteristics of the UE, UE status (or identified by / represented by / specific to it). The UE type can be (or include) (at least) enhanced machine type communication ((e)MTC) UE, NB-IoT UE, Reduced Capability (RedCap) UE, NR-supported UE, 5GC-supported UE, NTN-supported UE, regenerative payload-supported UE, UE with Global Navigation Satellite System (GNSS), and / or S&F operation-supported UE. The UE type can be (or include) (at least) stationary UE, low mobility UE, and / or UE within a restricted area. The UE type can be (or include) (at least) UE with low QoS requirements, and / or UE without ultra-reliable low latency communication (URLLC).

[0309] The configuration can also be pre-configured. For example, if the UE receives an S&F mode indication, the first type of UE is allowed to use the S&F operation. For example, the first type of UE is (always) allowed to use the S&F operation.

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

[0311] Service Type

[0312] The configuration can (at least) indicate which (type of) service is allowed to use the S&F operation. The configuration can (at least) indicate which (type of) service is to be sent to the NW (e.g., using the S&F operation). The service can be (UP) data and / or (CP) signaling. The service can be at the access stratum (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).

[0313] The service (or service type) can be based on QoS flow, PDU session, radio bearer (signaling radio bearer (SRB) and / or data radio bearer (DRB)), radio link control (RLC) bearer, and / or logical channel (or identified by / represented by / specific to the foregoing).

[0314] Explicit configuration can be used for some services (or service types), and implicit configuration (or pre-configuration) can be used for some (other) services (or service types). For example, whether the first service (or service type) is allowed to use the S&F operation can be based on the configuration. Whether the second service (or service type) is allowed to use the S&F operation can be based on pre-configuration (e.g., allowed, not allowed, no configuration).

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

[0316] If the UE determines that the S&F operation is allowed / enabled / activated for a service, the UE may perform the transmission (and / or reception) of the service (e.g., using the S&F operation), initiate a procedure for the transmission (and / or reception) of the service (e.g., using the S&F operation), and / or request permission / establishment / resources for the service (e.g., using the S&F operation). The procedure may be a registration procedure (e.g., for initial and / or mobility updates), a service request procedure, a PDU session establishment (or modification) procedure.

[0317] QoS Parameter

[0318] The parameter may be used by the UE (e.g., based on at least the parameter) to determine (at least) whether the QoS requirements of a UE request (e.g., for a service, connection, PDU session, and / or QoS flow) can be satisfied. The parameter may be used by the UE (e.g., based on at least the parameter) to determine (at least) whether to initiate a UE request (e.g., for a service, connection, PDU session, and / or QoS flow).

[0319] The parameter may be (at least) based on / identified by / represented by / specific to the UE, connection, service, PDU session, and / or QoS flow. The configuration may (at least) indicate what type of UE, connection, service, PDU session, and / or QoS flow is associated with the parameter. The parameter may be (at least) based on / identified by / represented by / specific to a radio bearer (SRB and / or DRB), RLC bearer, and / or logical channel. The configuration may (at least) indicate what type of radio bearer, RLC bearer, and / or logical channel is associated with the parameter.

[0320] The parameter may be (or include) (at least) a QoS flow identifier (QFI), 5G QoS identifier (5QI), allocation and retention priority (ARP), resource type, priority, packet error rate, average window, delay budget (e.g., packet delay budget), and / or data volume (maximum data burst volume).

[0321] The parameter may (at least) indicate the QoS (related) level / requirement / characteristic for which the S&F operation is allowed. The parameter may (at least) indicate the maximum QoS level (e.g., latency) that the NW can satisfy. The parameter may (at least) indicate how long data (or signaling) received from the UE is expected to be stored by the NW before delivery. The parameter may (at least) indicate how long a response to a UE request is expected to be transmitted (or received).

[0322] The UE may determine (whether) to use the S&F operation (e.g., for a specific object, for a service, for a PDU session) based on (at least) the said configuration. For example, if the UE receives the configuration and / or the object (or service, or PDU session) of the UE is included in the configuration (or pre-configuration), the UE may consider that the S&F operation is (or is not) enabled (and / or activated, and / or permitted), e.g., for the object, for the service, and / or for the PDU session. If the UE receives the configuration and / or the object (or service, or PDU session) of the UE is not included in the configuration (or pre-configuration), the UE may consider that the S&F operation is not (or is) enabled (and / or activated, and / or permitted), e.g., for the object, for the service, and / or for the PDU session. If the UE receives the configuration and / or the object (or service, or PDU session) of the UE can meet the conditions / limitations / restrictions / requirements of the configuration (or pre-configuration), the UE may consider that the S&F operation is enabled (and / or activated, and / or permitted), e.g., for the object, for the service, and / or for the PDU session. If the UE receives the configuration and / or the object (or service, or PDU session) of the UE cannot meet the conditions / limitations / restrictions / requirements of the configuration (or pre-configuration), the UE may consider that the S&F operation is not (or is) enabled (and / or activated, and / or permitted), e.g., for the object, for the service, and / or for the PDU session. If the UE does not receive the configuration, the UE may consider that the S&F operation is (or is not) enabled (and / or activated, and / or permitted), e.g., for each (or all) object (or service, or PDU session) of the UE.

[0323] If the UE considers that the S&F operation is permitted / enabled / activated for an object (or service, or PDU session), the UE may perform the transmission (and / or reception) of the object (or service, or PDU session) (e.g., using the S&F operation), initiate a procedure 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 permission / establishment / resources for the object (or service, or PDU session) (e.g., using the S&F operation). The procedure may be a registration procedure (e.g., for initial and / or mobility update), a service request procedure, a PDU session establishment (or modification) procedure.

[0324] To determine whether to allow a service (or PDU session, or UE) to use S&F operations, at least the objects of the service (or PDU session, or UE) need to meet the configured QoS. For example, if no objects of the service (or PDU session, or UE) meet the configured QoS, the UE may not be allowed to use S&F operations for the service (or PDU session, or UE). If each object of the service (or PDU session, or UE) meets the configured QoS, the UE may be allowed to use S&F operations for the service (or PDU session, or UE). If some (certain) objects of the service (or PDU session, or UE) (e.g., the first object) meet the configured QoS and some (certain) other objects of the service (or PDU session, or UE) (e.g., the second object) do not meet the configured QoS, the UE may be allowed to use S&F operations for the first object and not allowed to use S&F operations for the second object. If some (certain) objects of the service (or PDU session, or UE) (e.g., the first object) meet the configured QoS and some (certain) other objects of the service (or PDU session, or UE) (e.g., the second object) do not meet the configured QoS, the UE may not be allowed to use S&F operations for the service (or PDU session, or UE) (e.g., including the first object and the second object). If some (certain) objects of the service (or PDU session, or UE) (e.g., the first object) meet the configured QoS and some (certain) other objects of the service (or PDU session, or UE) (e.g., the second object) do not meet the configured QoS, the UE may be allowed to use S&F operations for the service (or PDU session, or UE) (e.g., including the first object and the second object).

[0325] The objects can be (or include) (at least) a connection, a service, a PDU session, and / or a QoS flow. The objects can be (or include) (at least) a radio bearer, an RLC bearer, and / or a logical channel.

[0326] Data Volume

[0327] The configuration can (at least) indicate the data volume limit for allowing the use of S&F operations. The configuration can (at least) indicate how much data can be transmitted to the NW (e.g., using S&F operations). The data can be (or include) UP data and / or CP signaling. The data can be at the AS level and / or at the NAS level.

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

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

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

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

[0332] If the UE considers that the S&F operation is allowed (e.g., for the traffic), the UE may perform (or continue) the transmission (and / or reception) of the traffic (e.g., using the S&F operation), initiate a procedure for (or for) performing the transmission (and / or reception) of the traffic (e.g., using the S&F operation), and / or request permission / establishment / resources for the traffic (e.g., using the S&F operation). The procedure may be a registration procedure (e.g., for initial and / or mobility updates), a service request procedure, a PDU session establishment (or modification) procedure.

[0333] If the UE has transmitted data exceeding the data volume, the UE may stop the S&F operation, stop transmitting data, and stop the (ongoing) procedure. If the UE has transmitted data exceeding the data volume, the UE may transmit an indication to the NW (e.g., indicating that the data volume limit has been reached), initiate an (RRC and / or NAS) connection release (request) procedure, initiate a deregistration procedure, and / or initiate a PDU session release (or modification) procedure (e.g., release the PDU session). If the UE has transmitted data exceeding the data volume, the UE may release the (RRC and / or NAS) connection and / or enter the (RRC and / or NAS) idle mode (e.g., RRC_IDLE, Connection Management (CM)_IDLE).

[0334] The NW (or network node) may be a satellite NW. The satellite NW may 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 base station, a part of the above, and / or a combination of the above.

[0335] The NW (or network node) may be a terrestrial NW. The terrestrial NW may 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 base station, a part of the above, and / or a combination of the above.

[0336] The satellite NW and the terrestrial NW may be mutually exclusive.

[0337] The NW (or network node) may be a cell. The NW may be a serving cell. The NW may be an adjacent cell. The NW may be a source cell. The NW may be a target cell.

[0338] The UE may support the S&F operation. The UE may not support the S&F operation.

[0339] The UE may be in the RRC connected mode. The UE may be in the RRC idle mode. The UE may be in the RRC inactive mode.

[0340] The UE may be in the CM idle state. The UE may be in the CM connected state.

[0341] The UE may be in the Registration Management (RM) deregistered state. The UE may be in the RM registered state.

[0342] The UE may be in a cell of the NTN. The UE may be connected to a cell of the NTN. The UE may be connected to a LEO, GEO, MEO, HEO, and / or HAPS.

[0343] The UE may be referred to as the UE, the RRC entity of the UE, or the Media Access Control (MAC) entity of the UE.

[0344] The UE can be an NR device. The UE can be an NR light device. The UE can be a device with insufficient capabilities. 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.

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

[0346] Various examples and embodiments of the present invention are described below. For the methods, alternatives, concepts, examples, and embodiments detailed above and herein, the following aspects and embodiments are possible.

[0347] See Figure 17 , for such and other concepts, systems, and methods of the present invention, method 1000 for a UE in a wireless communication system includes receiving information for deriving the time of S&F operation (step 1002), and determining whether to perform an action based on the information (step 1004).

[0348] Now refer to Figure 3 and 4 , in one or more embodiments from the perspective of a UE in a wireless communication system, device 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) receive information for deriving the time of S&F operation; and (ii) determine whether to perform an action based on the information. In addition, the CPU 308 can execute the program code 312 to perform all the described actions, steps, and methods described above, below, or herein.

[0349] See Figure 18 , for such and other concepts, systems, and methods of the present invention, method 1010 for a first network node in a wireless communication system includes transmitting information for deriving the time of S&F operation to the UE (step 1012) and performing the S&F operation at the time indicated by the information (step 1014).

[0350] Now refer to Figure 3 and 4 , in one or more embodiments from the perspective of a first network node in a wireless communication system, device 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) transmit information for deriving the time of S&F operation to the UE; and (ii) perform the S&F operation at the time indicated by the information. In addition, the CPU 308 can execute the program code 312 to perform all the described actions, steps, and methods described above, below, or herein.

[0351] In various embodiments, the information includes the (expected) time to start the S&F operation.

[0352] In various embodiments, the information includes the (expected) time to end the S&F operation.

[0353] In various embodiments, the information includes the (expected) duration of the S&F operation.

[0354] In various embodiments, the action includes starting (or stopping) the application of the S&F operation.

[0355] In various embodiments, the action includes applying (or releasing) the S&F configuration.

[0356] In various embodiments, the action includes allowing (or prohibiting) non-S&F data transfer.

[0357] In various embodiments, the action includes allowing (or prohibiting) a specific program.

[0358] In various embodiments, the specific program includes a registration program.

[0359] See Figure 19 , for such and other concepts, systems, and methods of the present invention, method 1020 for a UE in a wireless communication system includes receiving time information for an S&F operation in an NTN cell (step 1022), and determining when to enter or leave the S&F mode for the NTN cell based on the time information (step 1024).

[0360] In various embodiments, the time information is provided in system information.

[0361] In various embodiments, the time information includes the time to enter the S&F mode, the time to leave the S&F mode, and / or the duration of the S&F mode.

[0362] In various embodiments, the value of the time information is an absolute time or relative to a time reference.

[0363] In various embodiments, the method further includes deriving the remaining time of the S&F operation based on the time information.

[0364] In various embodiments, the method further includes determining when to enter or leave the S&F mode based on the time information.

[0365] In various embodiments, the method further includes determining whether to allow connection establishment to the NTN cell based on the time information.

[0366] In various embodiments, the method further includes determining whether to request one or more uplink resources (e.g., for non-S&F data) based on time information.

[0367] In various embodiments, the time information is received from a network node.

[0368] Now referring Figure 3 and 4 and, in one or more embodiments from the perspective of a UE in a wireless communication system, apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. A CPU 308 may execute the program code 312 to: (i) receive time information for S&F operations in an NTN cell; and (ii) determine when to enter or leave the S&F mode for the NTN cell based on the time information. Additionally, the CPU 308 may execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or elsewhere herein.

[0369] Referring Figure 20 and, with respect to such and other concepts, systems, and methods of the present invention, a method 1030 for an NTN cell in a wireless communication system includes transmitting time information for S&F operations (step 1032).

[0370] In various embodiments, the NTN cell provides S&F operations at a time indicated or derived by the time information.

[0371] In various embodiments, the time information is transmitted to a user equipment (UE).

[0372] Now referring Figure 3 and 4 and, in one or more embodiments from the perspective of an NTN cell in a wireless communication system, apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. A CPU 308 may execute the program code 312 to: (i) transmit time information for S&F operations. Additionally, the CPU 308 may execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or elsewhere herein.

[0373] Any combination of the concepts or teachings above or herein may be fully or partially combined together or formed into a new embodiment. The disclosed details and embodiments can be used to at least (but not limited to) solve the problems mentioned above and herein.

[0374] It should be noted that any one of the methods, alternatives, steps, examples, and embodiments presented herein may be applied independently, separately, and / or together with multiple methods, alternatives, steps, examples, and embodiments combined together.

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

[0376] Those skilled in the art will appreciate that any of a variety of different technologies and techniques can be used to represent information and signals. By way of example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0377] Those of ordinary skill in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware (e.g., digital implementations, analog implementations, or combinations thereof, which can be designed using source coding or some other technique), various forms of program or design code with instructions (for convenience, which may be referred to herein as "software" or "software modules"), or a combination of both. To clearly illustrate the interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been generally described above in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the particular 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 particular application, but such implementation decisions should not be construed as causing a departure from the scope of the present disclosure.

[0378] Additionally, various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein can be implemented within or performed by an integrated circuit ("IC"), an access terminal, or an access point. The IC can 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 can execute code or instructions residing within the IC, outside the IC, or in both cases. The general-purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0379] It should be understood that any specific order or hierarchy of steps in any disclosed process is an example of an instance of a method. It should be understood that, based on design preferences, the specific order or hierarchy of steps in a process can be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present the elements of the various steps in a sample order and are not intended to be limited to the specific order or hierarchy presented.

[0380] The steps of a method or algorithm described in connection with the aspects disclosed herein can be implemented directly in hardware, in a software module executed by a processor, or in a combination of the two. Software modules (e.g., including executable instructions and related data) and other data can reside in a data memory, such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. The exemplary storage medium can be coupled to a machine such as a computer / processor (for convenience, the machine can be referred to herein as "processor") such that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. The exemplary storage medium can be integral with the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user equipment. In the alternative, the processor and the storage medium can reside as discrete components in the user equipment. Additionally, in some aspects, any suitable computer program product can include a computer-readable medium including code associated with one or more of the aspects of the present disclosure. In some aspects, the computer program product can include packaging material.

[0381] Although the invention has been described in connection with various aspects and examples, it is to be understood that the invention is capable of further modification. This application is intended to cover any variations, uses, or adaptations of the invention, which generally follow the principles of the invention and include such departures from the present disclosure as come within the known and customary practice within the art to which the invention pertains.

Claims

1. A method for a user device, characterized in that: The method comprises: receiving time information for store and forward operations in a non-terrestrial network cell; and A determination is made based on the time information as to when to enter or leave a store and forward mode for the non-terrestrial network cell.

2. The method according to claim 1, characterized in that The time information is provided in the system information.

3. The method according to claim 1, characterized in that The time information includes a time of entering the store and forward mode, a time of leaving the store and forward mode and / or a duration of the store and forward mode.

4. The method according to claim 1, characterized in that: The value of the time information is an absolute time or relative to a time reference.

5. The method according to claim 1, characterized in that The method further includes deriving a remaining time for the store and forward operation based on the time information.

6. The method according to claim 1, characterized in that The method further includes determining when to enter or leave the store and forward mode based on the time information.

7. The method according to claim 1, characterized in that The method further includes determining whether to allow connection establishment to the non-terrestrial network cell based on the time information.

8. The method according to claim 1, characterized in that The method further includes determining whether to request one or more uplink resources based on the time information.

9. The method according to claim 1, characterized in that: The time information is received from a network node.

10. A method for a non-terrestrial network cell, characterized in that: The method comprises: Carries time information for store and forward operations.

11. The method according to claim 10, characterized in that The non-terrestrial network cell provides the store and forward operation at a time indicated or derived from the time information.

12. The method according to claim 10, characterized in that The time information is transmitted to the user equipment.

13. A user equipment, characterized in that: The user equipment comprises: Memory; and a processor operatively coupled to the memory, wherein the processor is configured to execute program code to: receiving time information for store and forward operations in a non-terrestrial network cell; and A determination is made based on the time information as to when to enter or leave a store and forward mode for the non-terrestrial network cell.

14. The user equipment according to claim 13, characterized in that The time information is provided in the system information.

15. The user equipment according to claim 13, characterized in that The time information includes a time of entering the store and forward mode, a time of leaving the store and forward mode and / or a duration of the store and forward mode.

16. The user equipment according to claim 13, characterized in that The value of the time information is an absolute time or relative to a time reference.

17. The user equipment according to claim 13, characterized in that The processor is further configured to execute the program code to derive a remaining time for the store and forward operation based on the time information.

18. The user equipment according to claim 13, characterized in that The processor is further configured to execute the program code to determine when to enter or leave the store and forward mode based on the time information.

19. The user equipment according to claim 13, characterized in that The processor is further configured to execute the program code to determine whether to allow connection establishment to the non-terrestrial network cell based on the time information.

20. The user equipment according to claim 13, characterized in that The processor is further configured to execute the program code to determine whether to request one or more uplink resources based on the time information.

Images