Method and apparatus for handling NTN storage and forwarding configuration in wireless communication system

Abstract

A method and user equipment for handling a non-terrestrial network storage and forwarding configuration in a wireless communication system are provided, in which the method includes providing an indication or configuration from a network regarding a traffic type for a storage and forwarding operation, and determining whether to use the storage and forwarding operation based on the indication or configuration.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 529,270 filed on July 27, 2023 and U.S. Provisional Patent Application No. 63 / 534,740 filed on August 25, 2023; each of the applications and publications referenced therein are incorporated herein by reference in their entirety. Technical Field

[0003] The present disclosure relates generally to wireless communication networks, and more particularly, to methods and apparatus for handling Non-Terrestrial Network (NTN) store and forward (S&F) configuration in a wireless communication system. Background Art

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

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

[0006] A method, system, and device for handling non-terrestrial network (NTN) store and forward (S&F) configuration in a wireless communication system are provided. In various embodiments, a user equipment (UE) can effectively transmit data based on S&F operations. A satellite network (NW) can obtain the required S&F related configuration from a terrestrial NW and can appropriately use the S&F operation.

[0007] In various embodiments, the method of the UE includes providing an indication or configuration regarding a traffic type for S&F operation from a network, and determining whether to use the S&F operation based on the indication or configuration. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1A diagram 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 According to an embodiment of the present invention Figure 3 Functional block diagram of the program code;

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

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

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

[0015] Figure 8 It is in 3GPP TR 38.821V16.0.0 Figure 5 .2.1-2: Reproduction of regenerated satellite with payload for ISL, gNB processing;

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

[0017] Fig.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;

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

[0019] Fig.12 is a reproduction of the diagram of possible call flows for intermittent feeder links in 3GPP RWS-230178;

[0020] Fig.13 It is in 3GPP TS23.501V18.1.0 Figure 4 .2.3-1: Re-emergence of non-roaming 5G system architecture;

[0021] Fig.14 is an example diagram showing an NTN network according to an embodiment of the present invention;

[0022] Fig.15 is an exemplary diagram according to an embodiment of the present invention, showing that after receiving a configuration for S&F operation, a satellite NW may start S&F operation (and / or provide S&F service to a UE) when there is no feeder link with a terrestrial NW;

[0023] Fig.16 is an example diagram according to an embodiment of the present invention, showing that a satellite NW may initiate a procedure, and then after the procedure is (successfully) completed, the satellite NW may begin S&F operations;

[0024] Fig.17 is an example diagram according to an embodiment of the present invention, showing that a ground NW may initiate a procedure, and then after the procedure is (successfully) completed, the ground NW may transmit data / signaling / messages to a satellite NW;

[0025] Fig.18 is a flow chart of a method of a UE according to an embodiment of the present invention, comprising receiving a configuration or indication related to an S&F operation, and determining whether to use the S&F operation based on the configuration or indication;

[0026] Fig.19 is a flow chart of a method of a first network node according to an embodiment of the present invention, comprising transmitting a first signaling to a second network node, and receiving a second signaling from the second network node;

[0027] Fig. 20 is a flow chart of a method of a second network node according to an embodiment of the present invention, comprising: receiving a first signaling from a first network node, wherein the first signaling is used to indicate or request an S&F operation; and transmitting a second signaling to the first network node;

[0028] Fig.21 is a flowchart of a method of a UE according to an embodiment of the present invention, comprising: providing an indication or configuration about a service type for S&F operation from a network, and determining whether to use S&F operation based on the indication or configuration. DETAILED DESCRIPTION

[0029] The present invention described herein may be applied to or implemented in the exemplary wireless communication systems and devices described below. In addition, the present invention is primarily described in the context of the 3GPP architecture reference model. However, it should be understood that with the disclosed information, those skilled in the art can easily make adjustments to use and implement aspects of the present invention in the 3GPP2 network architecture as well as other network architectures.

[0030] The exemplary wireless communication systems and devices described below employ wireless communication systems that support broadcast services. Wireless communication systems are 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) wireless access, 3GPP Long Term Evolution Advanced (LTE-A) wireless access, 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR), or some other modulation technology.

[0031] Specifically, the exemplary wireless communication system device described below can be designed to support one or more standards, such as standards provided by an association named "3rd Generation Partnership Project" (referred to herein as 3GPP), including: [1] 3GPP TR 38.821 V16.0.0, "Solution for NR Support of 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 System (5GS)"; and [4] 3GPP RWS-230178, "NR and IoT NTN". The standards and documents listed above are expressly and completely incorporated herein by reference in their entirety.

[0032] Figure 1 A multiple access wireless communication system according to an embodiment of the present invention is shown. An access network 100 (AN) includes multiple antenna groups, one antenna group includes 104 and 106, another antenna group includes 108 and 110, and another antenna group includes 112 and 114. Figure 1, only two antennas are shown for each antenna group, but each antenna group may utilize more or fewer antennas. Access terminal (AT) 116 communicates with antennas 112 and 114, 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 may use different frequencies for communication. For example, forward link 120 may use a different frequency than the frequency used by reverse link 118.

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

[0034] In communicating via forward links 120 and 126, the transmit antennas of access network 100 may utilize beamforming in order to improve the signal-to-noise ratio of the forward links for the different access terminals 116 and 122. Also, an access network that uses beamforming to transmit to access terminals that are randomly dispersed throughout the coverage area of ​​the access network will generally cause less interference to access terminals in neighboring cells than an access network that transmits to all of its access terminals via a single antenna.

[0035] AN can be a fixed station or 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. AT can also be referred to as user equipment (UE), a wireless communication device, a terminal, an access terminal, or some other term.

[0036] Figure 2 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 the transmitter system 210, traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.

[0037] In one embodiment, each data stream is transmitted via a respective transmit antenna.TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

[0038] The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream are then modulated (e.g., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for that data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions executed by the processor 230. The memory 232 is coupled to the processor 230.

[0039] The modulation symbols for all data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then converts the N T The modulation symbol stream is provided to N T Transmitters (TMTR) 222a through 222t. In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antennas from which the symbols are transmitted. Each transmitter 222 receives and processes a respective 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. T The antennas 224a to 224t transmit N signals from transmitters 222a to 222t. T a modulated signal.

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

[0041] RX data processor 260 then extracts the N R The receiver 254 receives and processes N R receive symbol streams to provide N TThe RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by the RX processor 260 is complementary to that performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[0042] Processor 270 periodically determines which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

[0043] The reverse link message may include various types of information related to the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238 (which also receives traffic data for a number of 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. The processor 230 then determines which precoding matrix to use to determine the beamforming weights and then processes the extracted message.

[0045] The memory 232 may be used to temporarily store some buffer / calculated data from 240 or 242 through the processor 230, store some buffer data from 212, or store some specific program codes. Also, the memory 272 may be used to temporarily store some buffer / calculated data from 260 through the processor 270, store some buffer data from 236, or store some specific program codes.

[0046] Steering Figure 3 , this figure shows an alternative simplified functional block diagram of a communication device according to one embodiment of the present invention. Figure 3 As shown in FIG. , the communication device 300 in the wireless communication system can be used to implement Figure 1UE (or AT) 116 and 122 in, 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, a 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 can receive a signal input by a user through the input device 302 (for example, a keyboard or a keypad), and can output images and sounds through the output device 304 (for example, a display or a speaker). The transceiver 314 is used to receive and transmit wireless signals to pass the received signal to the control circuit 306 and wirelessly output the signal generated by the control circuit 306.

[0047] Figure 4 According to one embodiment of the present invention, Figure 3 4. In this embodiment, program code 312 includes application layer 400, layer 3 portion 402, and layer 2 portion 404, and is coupled to layer 1 portion 406. Layer 3 portion 402 generally performs radio resource control. Layer 2 portion 404 generally performs link control. Layer 1 portion 406 generally performs physical connectivity.

[0048] For LTE, LTE-A or NR systems, the layer 2 portion 404 may include a radio link control (RLC) layer and a medium access control (MAC) layer. The layer 3 portion 402 may include a radio resource control (RRC) layer.

[0049] Any two or more of the following paragraphs, (sub) bullet points, points, actions or claims described in each invention 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 invention paragraph or section below can be implemented independently and individually to form a specific method or device. The dependency in the following invention disclosure (e.g., "based on", "more specifically", "example", etc.) is only a 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 transmission equipment relay nodes or base stations. [1] Further descriptions are also specified in 3GPP TR 38.821 V16.0.0.

[0052] *************************** Quote starts **********************************

[0053] 4.1 Overview of Non-terrestrial Networks

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

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

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

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

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

[0059] - One or more satellite gateways to connect non-terrestrial networks to the public data network

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

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

[0062] - Feeder link or radio link between satellite gateway and 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), which can implement transparent or regenerative (with onboard processing) payloads. Satellites (or UAS platforms) generate beams, typically multiple beams over a given service area bounded by their field of view. The footprint of the beams is typically elliptical. The field of view of a satellite (or UAS platform) depends on the onboard antenna pattern and the minimum elevation angle.

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

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

[0067] -Optionally, in case of satellite constellations, Inter-Satellite Links (ISL). This will require a regenerative payload on the satellites. ISLs can operate in RF frequencies or in the optical bands.

[0068] - The user equipment is served by a satellite (or UAS platform) within the target service area.

[0069] The following are some of the possible different types of satellites (or UAS platforms):

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

[0071]

[0072] generally

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

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

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

[0076] ****************************Next quote*******************************

[0077] 5.2 Regenerative Satellite Based on NG-RAN Architecture

[0078] 5.2.1 Payload processing 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 performs the regeneration of the signal received from the Earth.

[0082] NR-Uu radio interface over the service link between the UE and the satellite

[0083] • Satellite Radio Interface (SRI) on the feeder link between the NTN gateway and the satellite.

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

[0085] Figure 7 It is in 3GPP TR 38.821V16.0.0 Figure 5 .2.1-1: Reproduction of regenerated satellite without ISL, gNB processed payload.

[0086] Note: Satellites can enable additional traffic routing capabilities beyond the RAN range.

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

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

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

[0090] Figure 8 It is in 3GPP TR 38.821V16.0.0 Figure 5 .2.1-2: Reproduction of regenerated satellite with ISL, gNB processed payload.

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

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

[0093] If the satellite carries more than one gNB, the same SRI shall be transmitted for all corresponding NG interface instances.

[0094] ******************************Next quote*******************************

[0095] 5.2.2 Payload processed by gNB-DU

[0096] 5.2.2.1 Overview

[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 performs the regeneration of the signal received from the Earth.

[0099] ●NR-Uu radio interface over the service link between satellite and UE

[0100] ● Satellite Radio Interface (SRI) on the feeder link between the NTN gateway and the satellite. SRI transports the F1 protocol.

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

[0102] SRI (Satellite Radio Interface) is the transmission link; the logical interface F1 they transmit 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 connect to the same CU on the ground.

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

[0106] Fig. 9 It is in 3GPP TR 38.821V16.0.0 Figure 5 .2.2-1: Re-emergence of NG-RAN with satellite-based regeneration based on gNB-DU.

[0107] *****************************End of Quote**********************************

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

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

[0110] **************************** Quote starts *********************************

[0111] Annex A (Informative):

[0112] Store and forward satellite operations

[0113] Store and forward satellite operations in 5G systems 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 Operation” is shown in Figure A-1, in contrast to what may currently be considered the “Normal / Default Satellite Operation” assumption for a 5G system with satellite access.

[0115] As shown in Figure A-1:

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

[0117] - In contrast, in the "S&F satellite operation" 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, signaling / data is exchanged between the UE and the satellite without the satellite being simultaneously connected to the terrestrial network (i.e., the satellite is able to operate a service link without an active feeder link connection). In step B, a connection is established between the satellite and the terrestrial network, allowing communication 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] Fig.10 It 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 "S&F" services is widely used in the field of delay tolerant networks and outage tolerant networks. In the 3GPP context, a service that can be assimilated to an 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 an application server), but only between the endpoints and the SMSC acting as an intermediate node responsible for storage and dependency.

[0120] Support of S&F satellite operations is particularly applicable to NGSO satellites delivering delay tolerant / non-real-time IoT satellite services.

[0121] *****************************Next quote*******************************

[0122] 5.4 Use Cases for Store and Forward Data Delivery of IoT Devices in Remote Areas

[0123] 5.4.1 Description

[0124] Data transfer between remote sites is a very common requirement. Research institutions can obtain data from remote sites for scientific research, such as animal tracking [5]. Government agencies can obtain data from remote sites for disaster mitigation and avoidance, such as via remote sensing [6]. Commercial companies can obtain data from remote sites to make appropriate resource allocations. Data transfer to many remote sites is not sensitive to latency, and satellite coverage does not always ensure that the satellite is connected to both the service link and the feeder link. Over the past 30 years, many researchers have devoted their efforts to studying the problem of data transfer between remote sites and have developed store and forward mechanisms to solve this problem [7][8][9].

[0125] In remote areas, there are no terrestrial networks for various reasons, such as the difficulty in building and maintaining communication towers. Therefore, this makes it challenging to collect information for environmental protection purposes in these areas. For example, sensors mounted on animals need to be monitored regularly. In this case, the sensors mounted on animals send status information such as the animal's movement, physiology, and surrounding environment to the satellite; the satellite stores the received animal status information and forwards the information to the science center when a feeder link is available.

[0126] 5.4.2 Prerequisites

[0127] The EA Science Center has installed sensors (IoT devices) on the animals to collect information for environmental protection purposes in these remote areas. Satellite communications operator Satelles has launched store and forward satellite operations to support data delivery in remote areas. The EA Science Center has signed a contract with Satelles to allow sensors installed on animals to send status information (such as animal movement, physiology and surrounding environment) to the Science Center via satellite.

[0128] The satellite and IoT device are properly configured with sufficient information, such as credentials / certificates, required for the device to verify the satellite’s authenticity.

[0129] 5.4.3 Service Flow

[0130] Fig.11 It is in 3GPP TR 22.865V2.0.0 Figure 5 .4.3-1: Re-emergence of animal tracking in remote areas.

[0131] 1. IoT devices are mounted on animals and powered, and they are registered in the 5G network for store-and-forward satellite operations. Satellites with store-and-forward capabilities enable IoT devices to deliver data to the network even when the feed link to the ground is unavailable. A secure connection is established between the IoT device and the satellite to protect data security and privacy.

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

[0133] 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 allowed, the ground core network forwards the sensor status information to its destination data network.

[0134] 4. The ground core network sends the operation results to the satellite (either through the same satellite or different satellites in remote areas).

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

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

[0137] 5.4.4 Postconditions

[0138] After receiving the sensor status information at the science center, scientists can analyze the sensor status information and track the animal status.

[0139] ****************************End of Quote********************************

[0140] In [4] 3GPP RWS-230178, it is specified that on the basis of discontinuous coverage, in areas where the deployment of ground stations is not feasible or cost-effective, there may also be an intermittent feeder link (FL) connection to a ground station (GS). The possible invocation flow of the intermittent feeder link is specified:

[0141] **************************** Quote starts *********************************

[0142] Fig.12 is a reproduction of the diagram of a possible call flow for an intermittent feeder link in 3GPP RWS-230178.

[0143] *****************************End of Quote***********************************

[0144] In 3GPP TS23.501 ([3] 3GPP TS23.501 V18.1.0), the 5G system architecture is shown:

[0145] ***************************** Quote starts*******************************

[0146] 4.2.3 Non-roaming reference architecture

[0147] Figure 4 .2.3-1 describes the non-roaming reference architecture. Uses service-based interfaces within the control plane.

[0148] Fig.13 It is in 3GPP TS23.501V18.1.0 Figure 4 .2.3-1: Re-enactment of the non-roaming 5G system architecture.

[0149] *****************************End of Quote***********************************

[0150] A non-terrestrial network (NTN) is a network, such as a Next Generation (NG)-Radio Access Network (RAN) consisting of gNBs, which provides non-terrestrial access to user equipment (UE) through NTN payloads and NTN gateways on airborne or satellite-based NTN tools. UEs can be linked to, reside on, and / or connected to NTN networks involving airborne / satellite transmissions. NTNs may include various platforms, including low earth orbit (LEO) satellites, medium earth orbit (MEO) satellites, high elliptical orbit (HEO) satellites, geostationary orbit (GEO) satellites, geosynchronous orbit (GSO) satellites, non-geosynchronous orbit (NGSO) satellites, and / or high altitude communication platforms (HAPS). LEO satellites may have geo-fixed beams (e.g., beams temporarily fixed in one position for a period of time) or geo-mobile beams (e.g., beams continuously moving with the satellite). LEO satellites may serve / provide geo-mobile cells (e.g., having geo-fixed beams) and / or (quasi) geo-fixed cells (e.g., having geo-mobile beams). NTNs can provide wide area coverage and NW access where terrestrial networks (TNs) are not feasible (e.g., deserts, polar regions, and / or on airplanes). More details on different NTN platforms can be found in TR 38.821 ([1] 3GPP TR 38.821 V16.0.0).

[0151] Store and forward (S&F) operation is an operation mode of satellite access that provides a certain level of service (store and forward data) when the satellite connection is intermittent / temporarily unavailable, such as providing communication services to UEs under satellite coverage without the feeder link connection to the ground segment being active at the same time. A network supporting S&F operation can be based on an architecture with regenerative payload. At least some network nodes (or network segments) are located in the satellite. The network nodes (or network segments) on the satellite can be (or include) NG-RAN, evolved Node B (eNB), gNB, gNB distributed unit (DU), core network (CN) node, user plane function (UPF), part of UPF, access and mobility management function (AMF), part of AMF, session management function (SMF), part of SMF, mobility management entity (MME), part of MME, serving gateway (SGW), part of SGW, packet data network (PDN) gateway (PGW), part of PGW, home subscriber server (HSS), part of HSS, and / or a combination of the above. The remaining network nodes (or network segments) in the system (e.g., 5G system) may be located on the ground. The network nodes (or network segments) on the ground may be NG-RAN, eNB, gNB, gNB-DU, CN nodes, UPF, part of UPF, AMF, part of AMF, SMF, part of SMF, MME, part of MME, SGW, part of SGW, PGW, part of PGW, HSS, part of HSS, the remaining CN nodes not located on the satellite, and / or combinations thereof. For illustration, the network node (or network segment) located in the satellite may be represented as an NW on the satellite (or satellite NW). For illustration, the network node (or network segment) located on the ground may be represented as an NW on the ground (or ground NW). For example, the satellite NW may include an NG-RAN, and the ground NW may include a 5GC. For example, the satellite NW may include an eNB and an MME (or part of an MME), and the ground NW may include other parts of the MME. For example, a satellite NW may include a gNB and a UPF (or part of a UPF), and a terrestrial NW may include a 5G CN (excluding the UPF part located in the satellite). 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. Fig.14 Shown in.

[0152] In [4] RWS-230178, a possible call flow of S&F is shown. Based on the call flow, the UE performs communication with the NW normally (e.g., transmitting non-access stratum (NAS) protocol data units (PDUs), such as CP data) (e.g., similar to a conventional NTN, as if S&F operation is not used), and if the NW detects that there is no gateway link, it stores the NAS PDU and transmits "no feeder link indication" + "next scheduled time" in a release message (as in step 3 of the flow). After receiving the indication, the UE enters IDLE mode and indicates an acknowledgment (ACK) delay to the NAS. Based on the call flow, the UE cannot know that the NW is using S&F operation until it receives the indication in the release message. However, there may be several disadvantages of S&F operation based on the call flow. First, not every type of service (e.g., user plane (UP) data, control plane (CP) data, CP signaling, short message service (SMS)) may be suitable for S&F operation. For example, delay-sensitive data may not tolerate the delay of S&F operation. In this case, the data transmitted to the NW may be discarded in the satellite. Transmitting data and / or signaling to the satellite NW without a feeder link is a waste of radio resources.

[0153] Secondly, the UE is not aware that the NW is using S&F operation, e.g., when transmitting data and / or signaling to the NW, the data and / or signaling transmitted to the satellite NW will be stored until a feeder link is available later. Whether the NW is in S&F mode may affect the UE, e.g., in how the UE transmits data and / or signaling.

[0154] To address this issue, the NW (e.g., satellite NW) may provide / provision / configure / update (at least) S&F-related indications and / or configurations / parameters (e.g., before the UE transmits data to the NW), which may be included in the signaling. The UE may determine (at least) based on the indications and / or configurations / parameters whether and / or how to transmit data and / or signaling (e.g., using S&F operation). For example, if the UE detects that the NW is using S&F operation (e.g., the feeder link is currently unavailable), the UE may use S&F operation, and / or not generate (or transmit) data (or signaling) to the NW that is not suitable for S&F operation (e.g., cannot meet QoS requirements, such as delay requirements).

[0155] If the UE receives an indication and / or configuration / parameter related to S&F (signaling with the indication and / or configuration / parameter) (e.g., the indication and / or configuration / parameter is present and / or enabled), then the UE may consider that the NW (e.g., satellite NW) is using S&F operation, is in S&F mode, the feeder link of the NW is not available, and / or the NW is unable to forward data / signaling to the terrestrial NW. The UE may use (or enable) S&F operation (as a response). If the UE does not receive signaling, does not receive an indication and / or configuration / parameter related to S&F, and / or the indication and / or configuration is not present and / or disabled, then the UE may consider that the NW (e.g., satellite NW) is not using S&F operation, is not in S&F mode, the feeder link of the NW is available, and / or the NW is able to forward data / signaling to the terrestrial NW. The UE may not use (or disable) S&F operation (as a response).

[0156] Indications and / or configurations / parameters related to S&F may be provided in broadcast signaling (provided by NW, such as provided by satellite NW) (to UE), such as system information, paging. The UE may obtain the broadcast signaling when (or in response to) camping / selecting / reselecting a cell, switching (to the cell), changing the serving cell (to the cell) and / or being notified by the NW (e.g., notification of a system information change).

[0157] Indications and / or configurations / parameters related to S&F may be provided in dedicated signaling (provided by the NW, e.g., provided by a satellite NW) (to the UE). The dedicated signaling may be a NAS message or a radio resource control (RRC) message. The dedicated signaling may be a reconfiguration message (e.g., an RRC reconfiguration message). The dedicated signaling may be a NAS notification message. The dedicated signaling may be a paging message.

[0158] The dedicated signaling may be a response message to the UE request. The dedicated signaling may be a NAS message or an RRC message. The UE request may be a request message to establish an RRC connection, a NAS connection and / or a PDU session. The UE request may be a service request.

[0159] Indications and / or configurations / parameters related to S&F may (or may not) be provided during a procedure (e.g., between a UE and a NW). The procedure may be initiated by the UE. The procedure may be initiated by the NW. The procedure may (or may not) be a registration procedure. The registration procedure may (or may not) be used for initial registration. The registration procedure may (or may not) be used for mobility registration updates. The registration procedure may (or may not) be used for periodic registration updates. The procedure may (or may not) be a service request procedure. The procedure may (or may not) be a notification procedure. The procedure may (or may not) be a PDU session establishment procedure. The procedure may (or may not) be a PDU session modification procedure. The procedure may be an (initial) attachment procedure.

[0160] Indications and / or configurations / parameters related to S&F may be provided (to the UE) by pre-configuration or provisioning in the UE (provided by the NW, eg provided by a satellite NW).

[0161] The NW may determine whether to provide S&F-related indications and / or configurations / parameters based (at least) on whether the NW's feeder link is available. For example, if the NW receives a UE request from the UE (e.g., to establish / modify an RRC connection, a NAS connection, and / or a PDU session), the NW may determine (at least) whether the NW's feeder link is available and / or whether the UE request (e.g., the corresponding connection, PDU session, and / or quality of service (QoS) flow) can be operated in an S&F operation (e.g., whether the corresponding QoS requirements can be met) and accept (or reject) the UE request. If yes, the NW may accept the UE request. The NW may provide S&F-related indications and / or configurations in the acceptance message. If not, the NW may reject the UE request. The NW may provide the rejection reason to the UE in the rejection message. The rejection reason may be related to the S&F operation, such as the unavailability of the feeder link.

[0162] Configurations (and / or indications / parameters) related to S&F may be associated with (or specific to) an object. An object may be (or include) a UE, a cell, a connection (e.g., an RRC connection, a NAS connection), a service (type), a PDU session, and / or a QoS flow. The NW may indicate (or configure) an object associated with a configuration (and / or indication / parameter). The NW may provide (at least) one configuration (and / or indication / parameter) to (at least) one object.

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

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

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

[0166] UE Type

[0167] The configuration may (at least) indicate what (types of) UEs are allowed to use S&F operations. The configuration may (at least) indicate what (types of) UEs are allowed to perform transmission and / or reception to the NW (e.g., using S&F operations). The transmission and / or reception may be (UP) data and / or (CP) signaling.

[0168] The UE type (e.g., the first type) may be based on UE capabilities, UE mobility, QoS characteristics of the UE, UE status (or identified by / represented by / specific to the various items). The UE type may be (or include) (at least) a machine type communication (MTC) UE, a narrowband Internet of Things (NB-IoT) UE, a RedCap (reduced capability) UE, a NR-supported UE, a 5GC-supported UE, a NTN-supported UE, a UE supporting regenerative payload, a UE with a global navigation satellite system (GNSS), and / or a UE supporting S&F operations. The UE type may be (or include) (at least) a stationary UE, a low mobility UE, and / or a UE in a restricted area. The UE type may be (or include) (at least) a UE with low QoS requirements, and / or a UE without ultra-reliable low latency communication (URLLC).

[0169] The configuration may (also) be pre-configured. For example, if a UE of a first type receives an S&F mode indication, the UE is allowed to use S&F operation. For example, a UE of a first type is (always) allowed to use S&F operation. The UE may determine (at least) based on the configuration (whether) to use S&F operation. For example, if the UE receives a configuration and / or the UE belongs to a UE type in the configuration (or pre-configuration), the UE may consider that S&F operation is enabled (and / or activated, and / or allowed). If the UE receives a configuration and / or the UE does not belong to a UE type in the configuration (or pre-configuration), the UE may consider that S&F operation is not enabled (and / or activated, and / or allowed). If the UE does not receive a configuration, the UE may consider that S&F operation is not enabled (and / or activated, and / or allowed).

[0170] Business Type

[0171] The configuration may (at least) indicate what (types of) traffic or services are allowed to use S&F operation. The configuration may (at least) indicate what (types of) traffic or services are allowed to be transmitted to the NW (e.g., using S&F operation). Traffic (types of) may include (UP) data and / or (CP) signaling. Traffic (types of) may include SMS (Short Message Service). Traffic may be at access stratum (AS) level and / or NAS level. The configuration may (also) be pre-configured. The configuration may be based on QoS requirements of the traffic (or traffic type).

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

[0173] Explicit configuration may be used for a certain service (or service type), and implicit configuration (or pre-configuration) may be used for a certain (other) service (or service type). For example, whether a first service (or service type) is allowed to use S&F operation may be based on configuration. Whether a second service (or service type) is allowed to use S&F operation may be based on pre-configuration (e.g., allowed, not allowed, no configuration).

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

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

[0176] QoS parameters

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

[0178] The parameter may be (at least) based on (or identified by / represented by / specific to) a 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 (or identified by / represented by / specific to) a radio bearer (SRB and / or DRB), an RLC bearer and / or a logical channel. The configuration may (at least) indicate what type of radio bearer, RLC bearer and / or logical channel is associated with the parameter.

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

[0180] The parameters may (at least) indicate the QoS (related) levels / requirements / characteristics that are allowed to use S&F operations. The parameters may (at least) indicate the maximum QoS level (e.g., latency) that the NW can meet. The parameters may (at least) indicate the length of time (e.g., delay, latency) that data (or signaling) received from the UE is expected to be stored by the NW before delivery. The parameters may (at least) indicate the length of time (e.g., delay, latency) that a response to a UE request is (expected) to be transmitted (or received). The parameters may (at least) indicate the length of time (e.g., delay, latency) that a service will be delayed by S&F operations.

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

[0182] If the UE considers that S&F operation is allowed / enabled / activated for an object (or service, or PDU session), then the UE may perform transmission (and / or reception) of the object (or service, or PDU session) (e.g., using S&F operation), initiate a procedure to (or for) perform transmission (and / or reception) of the object (or service, or PDU session) (e.g., using S&F operation), and / or request permission / establishment / resources for the object (or service, or PDU session) (e.g., the S&F operation). If the UE considers that the S&F operation is not allowed / enabled / activated for the object (or service, or PDU session), the UE may not perform transmission (and / or reception) of the object (or service, or PDU session) (e.g., using the S&F operation), not initiate a procedure to (or for) perform transmission (and / or reception) of the object (or service, or PDU session) (e.g., using the S&F operation), and / or not 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), an attachment, a service request procedure, a PDU session establishment (or modification) procedure.

[0183] In order to determine whether a service (or PDU session, or UE) is allowed to use S&F operation, at least the objects of the service (or PDU session, or UE) need to meet the configured QoS. For example, if none of the objects of the service (or PDU session, or UE) meet the configured QoS, the UE may not be allowed to use S&F operation 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 operation for the service (or PDU session, or UE). If some objects (e.g., a first object) of the service (or PDU session, or UE) meet the configured QoS, and some other objects (e.g., a second object) of the service (or PDU session, or UE) do not meet the configured QoS, the UE may be allowed to use S&F operation for the first object, and not be allowed to use S&F operation for the second object. If some objects (e.g., the first object) of a service (or PDU session, or UE) satisfy the configured QoS, and some other objects (e.g., the second object) of the service (or PDU session, or UE) do not satisfy the configured QoS, then the UE may not be allowed to use S&F operations for the service (or PDU session, or UE) (e.g., including the first object and the second object). If some objects (e.g., the first object) of a service (or PDU session, or UE) satisfy the configured QoS, and some other objects (e.g., the second object) of the service (or PDU session, or UE) do not satisfy the configured QoS, then the UE may be allowed to use S&F operations for the service (or PDU session, or UE) (e.g., including the first object and the second object).

[0184] An object may be (or include) (at least) a connection, a service, a PDU session and / or a QoS flow. An object may be (or include) (at least) a radio bearer, an RLC bearer and / or a logical channel.

[0185] Data volume

[0186] The configuration may (at least) indicate a limit on the amount of data that is allowed to be operated using S&F. The configuration may (at least) indicate the amount of data that may be transmitted to the NW (e.g., using S&F operation). The data may be (or include) UP data and / or CP signaling. The data may be AS level and / or NAS level.

[0187] The configuration may be (at least) based on (or identified by / represented by / specific to) UE, connection, service, PDU session and / or QoS flow. The configuration may (at least) indicate what (or which) UE, connection, service, PDU session and / or QoS flow is associated with the configuration. The configuration may be (at least) based on (or identified by / represented by / specific to) radio bearers (SRBs and / or DRBs), RLC bearers and / or logical channels. The configuration may (at least) indicate what (or which) radio bearers, RLC bearers and / or logical channels are associated with the parameters.

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

[0189] An object may be (or include) (at least) a UE, a connection, a service, a PDU session and / or a QoS flow. An object may be (or include) (at least) a radio bearer, an RLC bearer and / or a logical channel.

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

[0191] If the UE considers that the S&F operation is allowed (e.g., for the service), the UE may perform (or continue) transmission (and / or reception) of the service (e.g., using the S&F operation), initiate (or continue) a procedure for (or for) performing transmission (and / or reception) of the service (e.g., using the S&F operation), and / or request authority / 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 update), a service request procedure, a PDU session establishment (or modification) procedure.

[0192] 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 a (RRC and / or NAS) connection release (request) procedure, initiate a deregistration procedure, and / or initiate a PDU session release (or modification) procedure (e.g., to release the PDU session). If the UE has transmitted data exceeding the data volume, the UE may release the (RRC and / or NAS) connection, and / or go to an (RRC and / or NAS) idle mode (e.g., RRC_IDLE, connection management (CM)_IDLE).

[0193] S&F operations may be (or include) (at least) one or more of the following:

[0194] - The UE may know (or be informed by the NW) that the NW is (or starts) using S&F to handle data (and / or signaling);

[0195] - The UE may initiate a procedure to request (or instruct) the (satellite) NW to handle data (and / or signaling) using S&F;

[0196] - the UE may perform data (and / or signalling) transfer to be handled by the S&F in the (satellite) NW; and / or

[0197] - The UE may (be ready to) perform reception of data (and / or signalling) stored in the (satellite) NW.

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

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

[0200] - an indication that S&F mode (and / or S&F mode is enabled) is received (or transmitted);

[0201] - received (or transmitted) a configuration related to S&F mode (and / or S&F mode enabled); and / or

[0202] - Enabling and / or activating the S&F mode (of the UE and / or the network node).

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

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

[0205] - an indication that the S&F mode was not received (or not transmitted);

[0206] - an indication to deactivate (or deactivate) the S&F mode is received (or transmitted);

[0207] - received (or transmitted) a configuration related to S&F mode (and / or S&F mode enabled);

[0208] - received (or transmitted) a configuration to deactivate (or deactivate) S&F mode; and / or

[0209] - S&F mode deactivation and / or deactivation (of the UE and / or network node).

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

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

[0212] - The UE may know (or be informed by the NW) that the NW is (or starts) using S&F to handle data (and / or signaling);

[0213] - The UE may initiate a procedure to request (or instruct) the (satellite) NW to handle data (and / or signaling) using S&F;

[0214] - the UE may perform data (and / or signalling) transfer to be handled by the S&F in the (satellite) NW; and / or

[0215] - The UE may (be ready to) perform reception of data (and / or signalling) stored in the (satellite) NW.

[0216] To support S&F operations, the satellite NW (e.g., NG-RAN or secondary eNB (SeNB) in [4] RWS-230178) needs to provide at least a certain level of service (and / or network access) to one or more UEs without a feeder link (connected to a terrestrial NW, such as a CN or gateway in [4] RWS-230178). To this end, the satellite NW and the terrestrial NW may need to have some negotiation in advance (e.g., when the feeder link of the satellite NW is available) on how to provide the service (and / or network access).

[0217] To address this issue, the satellite NW may be provided with (at least) some configuration related to the S&F operation by the terrestrial NW. The satellite NW may transmit a request (or indication) for S&F operation to the terrestrial NW (e.g., in advance). The terrestrial NW may accept (or reject) the request for S&F, and / or provide the satellite NW with the configuration for S&F operation (e.g., in response to the request or indication). After receiving the configuration for S&F operation, the satellite NW may start S&F operation (and / or provide S&F services to the UE) when there is no feeder link with the terrestrial NW. Example in Fig.15 Shown in.

[0218] In one or more examples, the satellite NW may be connected to the ground NW via a feeder link. The satellite NW may want to communicate / negotiate / handshake with the ground NW regarding S&F operations, such as whether to start S&F operations, whether S&F operations can be used, and whether S&F operations can be supported. The satellite NW may not have been able to use (or start) S&F operations before. The satellite NW may want to use (or start) S&F operations. The satellite NW may want to prepare for S&F operations. The satellite NW may want to obtain one or more configurations related to S&F, such as for future use. The satellite NW may initiate a procedure for this purpose. After the procedure is (successfully) completed, the satellite NW may start S&F operations. Examples of procedures are shown in FIG. Fig.16 Shown in.

[0219] In one or more examples, the satellite NW may be connected to the terrestrial NW via a feeder link. The satellite NW may reacquire (or recover) the feeder link with the terrestrial NW. The terrestrial NW may or may not be the same terrestrial NW as the last connected terrestrial NW. The satellite NW may want to transmit (or forward) some (temporarily stored) data / signaling / message to the terrestrial NW. When the feeder link is not available, the data / signaling / message may have been received by one or more UEs before, for example in S&F operation. The satellite NW may initiate a procedure for this purpose. After the procedure is (successfully) completed, the satellite NW may transmit the data / signaling / message to the terrestrial NW. An example of a procedure is shown in FIG. Fig.16 Shown in.

[0220] In one or more examples, the satellite NW may be connected to the terrestrial NW via a feeder link. The satellite NW may reacquire (or recover) the feeder link with the terrestrial NW. The terrestrial NW may or may not be the same terrestrial NW as the last connected terrestrial NW. The terrestrial NW may want to transmit (or forward) some data / signaling / message to the satellite NW. The data / signaling / message may be for one or more UEs. The data / signaling / message may be (temporarily) stored by the satellite NW. The data / signaling / message may be forwarded to one or more UEs via the satellite NW. The terrestrial NW may initiate a procedure for this purpose. After the procedure is (successfully) completed, the terrestrial NW may transmit the data / signaling / message to the satellite NW. An example of a procedure is shown in FIG. Fig.17 Shown in.

[0221] The satellite NW may transmit a first signaling to the ground NW, such as the one mentioned above or Fig.16 or Fig.17 During the procedure shown in . The first signaling may be transmitted via a feeder link. The first signaling may be (or include) an indication of an S&F operation. The first signaling may be (or include) a request to use an S&F operation. The first signaling may be initiated by the satellite NW, for example, in the absence of signaling received from the ground NW. The first signaling may be a response to signaling (e.g., the second signaling) from the ground NW.

[0222] The satellite NW may transmit a third signaling to the ground NW, such as the one mentioned above or Fig.16 or Fig.17 During the procedure shown in . The third signaling can be transmitted via the feeder link. The third signaling can be a response to the signaling (eg, the second signaling) from the ground NW.

[0223] The feeder link may be (or correspond to) an NG interface (e.g., NG-user plane interface (U), NG-core (C), NG-application protocol (AP)), an F1 interface (e.g., F1-U, F1-C), an N2 reference point and / or an N3 reference point.

[0224] The first signaling and / or the third signaling may include (or use) (at least) one or more of the following information. The one or more of the following information may be mandatory or optional in the first signaling (and / or the third signaling). The one or more of the following information may not exist (or be not included) in the first signaling (and / or the third signaling). The one or more of the following information may be provided to the UE (e.g., as a configuration of the S&F).

[0225] Instructions for S&F Operation

[0226] The first signaling (or indication) may indicate that the satellite NW is (will be) using S&F operation. The first signaling (or indication) may indicate that the satellite NW is ready to use S&F operation. The first signaling (or indication) may indicate that the satellite NW has used S&F operation. The first signaling (or indication) may indicate that the satellite NW is returning from S&F operation (to normal operation). Normal operation may be (or be similar to) normal / default satellite operation specified in TR 22.865 ([2] 3GPP TR 22.865 V2.0.0).

[0227] The first signaling (or indication) may indicate that the satellite NW has stored data / signaling / messages to be forwarded to the terrestrial NW. The stored data / signaling / messages may be received by one or more UEs, for example, when the feeder link of the satellite NW is unavailable.

[0228] The first signaling (or indication) may indicate that the satellite NW is ready to receive data / signaling / messages to be forwarded to the UE.

[0229] Request for S&F Operation

[0230] The first signaling (or request) may be used to request (the right to use) the S&F operation. The first signaling (or request) may be used to request the S&F configuration, for example, to initiate the S&F operation, to update the S&F configuration. The S&F configuration may be (or include) one or more configurations related to S&F mentioned in the present disclosure. The first signaling (or request) may be used to request to return from the S&F operation (to the normal operation). The normal operation may be (or be similar to) the normal / default satellite operation specified in TR 22.865 ([2] 3GPP TR 22.865 V2.0.0).

[0231] The first signaling (or request) may be used to request (authority to) forward data / signaling / messages stored in the satellite NW to the ground NW.

[0232] The first signaling (or request) may be used to request (the right to) receive data / signaling / messages stored in the terrestrial NW to be forwarded to the UE.

[0233] The first signaling (or request) may be used to request one or more of the information mentioned below (e.g., time information, neighboring satellite or satellite NW information, S&F configuration, UE information, service information, QoS information, data / signaling / message for forwarding).

[0234] Response of S&F Operations

[0235] The first signaling (or response) may be a response to the second signaling (e.g., as mentioned below). The first signaling (or response) may be a response to a request in the second signaling (e.g., as mentioned below). The first signaling (or response) may be used to confirm, accept, or reject the request (for S&F operation) from the ground NW.

[0236] The first signaling (or response) may be used to respond to a query from the terrestrial NW as to whether the satellite NW can forward data / signaling / message to the UE.

[0237] Time Information

[0238] The first signaling (or time information) may indicate the time (and / or duration) when the feeder link (of the satellite NW) is unavailable (or will become unavailable). The first signaling (or time information) may indicate the time (and / or duration) when the S&F operation is used (or will be used). The time information may be an estimate of the satellite NW. The time information may be (or include) a start time, an end time, and / or a duration. The time information may be derived (or calculated or estimated) based on satellite information (e.g., ephemeris) of the satellite where the satellite NW is located. The time information may be optional in the first signaling.

[0239] Neighboring satellite (or satellite NW) information

[0240] The first signaling (or information) may be (or include) information related to an adjacent satellite (or satellite NW). The adjacent satellite (or satellite NW) may have an inter-satellite link (ISL) with the satellite NW. The satellite NW can communicate (or connect) with the adjacent satellite (or satellite NW) via one or more ISLs.

[0241] The information may be (or include) ephemeris information of a neighboring satellite. The information may be (or include) an ephemeris information list of a neighboring satellite list. One ephemeris information in the list may correspond to one neighboring satellite.

[0242] The information may be (or include) a network identity of a neighboring satellite NW. The information may be (or include) a network identity list of a neighboring satellite NW (node). One network identity in the list may correspond to one neighboring satellite NW (node).

[0243] S&F Configuration

[0244] The first signaling (or information) may be (or include) an S&F configuration of the satellite NW. The S&F configuration may be used by the satellite NW, such as currently used in S&F operation, previously used in previous S&F operation. The configuration may be one or more of the S&F configurations mentioned in the present disclosure.

[0245] UE Information

[0246] The first signaling (or information) may be (or include) information related to one or more UEs. The UE may be served by the satellite NW, such as currently being served in an S&F operation, previously being served in a previous S&F operation. The UE may have data / signaling / messages stored in the satellite NW. The UE may (or may) be served by the satellite NW, such as being served in a next S&F operation in the future.

[0247] The information may be (or include) a UE identifier (or UE identity) of the UE. The information may be (or include) a UE identifier list of a UE list. One UE identifier (or UE identity) in the list may correspond to one UE.

[0248] The UE identifier (or UE identity) may be (or include) (at least) a subscription permanent identifier (SUPI), an international mobile subscriber identity (IMSI), a globally unique temporary identifier (GUTI), a 5G globally unique temporary identifier (5G-GUTI), a subscription hidden identifier (SUCI), a permanent equipment identifier (PEI), a radio network temporary identifier (RNTI), a cell radio network temporary identifier (C-RNTI), an inactive radio network temporary identifier (I-RNTI) and / or part of the above.

[0249] The information may be (or include) a UE context of a UE. The information may be (or include) a UE context list of a UE list. One UE context in the list may correspond to one UE.

[0250] The UE context may be (or include) (at least) AS configuration, RRC configuration, AS context, UE capability, Radio Resource Management (RRM) configuration and / or part of the above.

[0251] The information may be (or include) a configuration of the UE. The information may be (or include) a configuration list of the UE list. One configuration in the list may correspond to one UE. The configuration may be related to S&F. The configuration may be (or include) (at least) one or more of the S&F configurations mentioned in the present disclosure.

[0252] Service and / or QoS related information

[0253] The first signaling (or information) may be (or include) information related to one or more services and / or QoS. The services and / or QoS may be services and / or QoS that the satellite NW may support in S&F operations. The services may be (or include) delay tolerance. The services may be (or include) non-real-time.

[0254] The information may be (or include) (at least) one or more QoS parameters mentioned in the present disclosure.

[0255] Stored data / signaling / messages

[0256] The first signaling may include (one or more) data / signaling / messages stored in the satellite NW. The data / signaling / message is to be forwarded to the ground NW. When the satellite NW does not have a feeder link, the data / signaling / message may be received from one or more UEs, such as in S&F operation. The data / signaling / message may be associated with one or more UEs.

[0257] The data / signaling / message may be (user plane) data, control signaling, upper layer signaling, NAS message, RRC message, NAS PDU, NAS Service Data Unit (SDU), Internet Protocol (IP) packet, Packet Data Convergence Protocol (PDCP) SDU and / or PDCP PDU.

[0258] In one or more examples, the satellite NW may transmit a request to transmit the stored data / signaling / message to the ground NW (e.g., via a first signaling). The ground NW may transmit a response to the satellite NW indicating that the request is accepted (or rejected) and / or some related configuration (e.g., forwarding priority) (e.g., via a second signaling). When responding / if responding / in response to the response, the satellite NW may transmit the stored data / signaling / message to the ground NW, for example, based on the related configuration provided by the ground NW (e.g., via a third signaling).

[0259] The first signaling (and / or the third signaling) may be initiated (or triggered) by (at least) one or more of the following conditions:

[0260] -Feeder link of satellite NW is available;

[0261] The condition may be when the feeder link is available (or becomes available) / if the feeder link is available (or becomes available) / when the feeder link is available (or becomes available) / in response to the feeder link being available (or becoming available). The satellite NW may return from unavailable to available. When the feeder link is unavailable, the satellite NW may be in S&F operation. When the feeder link is unavailable, the satellite NW may not be in S&F operation.

[0262] - Satellite NW is about to lose its feeder link;

[0263] - Satellite NW wants to use (or start) S&F operations;

[0264] - Satellite NW wants to modify the (current) S&F operations;

[0265] - Satellite NW has stored data / signaling / messages;

[0266] - the satellite NW is (or has been) notified by the terrestrial NW; and / or

[0267] - when the second signaling (or request) / if the second signaling (or request) / at the time of the second signaling (or request) / in response to the second signaling (or request).

[0268] The first signaling (and / or the third signaling) may be (or include) (at least) AMF configuration update, RAN configuration update, initial context establishment request / response, NG reset, NG establishment request / response, PDU session resource establishment / modification request / response, UE context modification / suspend / resume request / response, downlink / uplink RAN ​​configuration transfer, UE information transfer, etc.

[0269] The procedure may be (or include) (at least) AMF configuration update, RAN configuration update, initial context establishment, NG reset, NG establishment, PDU session resource establishment / modification, UE context modification / suspend / resume, downlink / uplink RAN ​​configuration transfer, UE information transfer, etc.

[0270] The ground NW may transmit a second signaling to the satellite NW, such as the one mentioned above or Fig.16 or Fig.17 The second signaling may be transmitted via a feeder link. The second signaling may be a response to the first signaling. The ground NW may transmit the second signaling in response to receiving the first signaling (e.g., from the satellite NW). The second signaling may be initiated by the ground NW, for example, in the absence of signaling received from the satellite NW.

[0271] The ground NW may transmit a fourth signaling to the satellite NW, such as the one mentioned above or Fig.16 or Fig.17 During the procedure shown in . The fourth signaling may be transmitted via the feeder link. The fourth signaling may be a response to the signaling from the satellite NW (eg, the first signaling or the third signaling).

[0272] The feeder link may be (or correspond to) an NG interface (e.g., NG-U, NG-C, NG-AP), an F1 interface (e.g., F1-U, F1-C), an N2 reference point, and / or an N3 reference point.

[0273] The second signaling and / or the fourth signaling may include (at least) one or more of the following information. The one or more of the following information may be mandatory or optional in the second signaling (and / or the fourth signaling). The one or more of the following information may not exist (or be not included) in the second signaling (and / or the fourth signaling). The one or more of the following information may be provided to the UE (for example, as a configuration of S&F).

[0274] Instructions for S&F Operation

[0275] The second signaling (or indication) may indicate that the terrestrial NW confirms that the satellite NW is (will be) using S&F operation. The second signaling (or indication) may indicate that the terrestrial NW can support the satellite NW using S&F operation. The second signaling (or indication) may indicate that the terrestrial NW already supports the satellite NW using S&F operation. The second signaling (or indication) may indicate that the terrestrial NW cannot support the satellite NW using S&F operation.

[0276] The second signaling (or indication) may indicate that the terrestrial NW has data / signaling / messages for one or more UEs, and / or that the data / signaling / messages will be forwarded (to one or more UEs) via the satellite NW. The one or more UEs may not currently be served by the satellite NW. The one or more UEs may be served by the satellite NW in the future, for example, at a later time. When the one or more UEs are served by the satellite NW, the data / signaling / messages may be forwarded to the one or more UEs in the future, for example, at a later time.

[0277] The second signaling (or indication) may indicate that the ground NW is ready to receive data / signaling / messages (from one or more UEs) stored (temporarily) in the satellite NW. The satellite NW may forward the data / signaling / messages (from one or more UEs) to the ground NW, for example, after receiving the second signaling (or indication).

[0278] Response of S&F Operations

[0279] The second signaling (or response) may be used to confirm, accept or reject the request for S&F operation from the satellite NW. If the terrestrial NW accepts the request, the satellite NW may use S&F operation, for example, when the feeder link of the satellite NW is unavailable. If the terrestrial NW rejects the request, the satellite NW may not use S&F operation, for example, until S&F operation is accepted.

[0280] The second signaling (or response) may be used to confirm, accept or reject the request to forward the data / signaling / message stored in the satellite NW to the ground NW.

[0281] The second signaling (or response) may be used to confirm, accept or reject the request to transfer the data / signaling / message stored in the terrestrial NW to be forwarded to the UE.

[0282] Request for S&F Operation

[0283] The second signaling (or request) may be used to request (authority to) transmit data / signaling / messages (for one or more UEs) to be forwarded via the satellite NW. The one or more UEs may not currently be served by the satellite NW. The one or more UEs may be served by the satellite NW in the future, e.g., at a later time. When the one or more UEs are served by the satellite NW, the data / signaling / messages may be forwarded to the one or more UEs in the future, e.g., at a later time.

[0284] The second signaling (or request) may be used to query the satellite NW whether the data / signaling / message can be forwarded to the UE. The terrestrial NW may have data / signaling / message to be sent to the UE. The terrestrial NW may transmit the data / signaling / message to the satellite NW, for example after / if / in response to the satellite NW accepting the query (or request) the query (or request).

[0285] The second signaling (or request) may be used to request one or more of the information mentioned below (e.g., time information, neighboring satellite or satellite NW information, S&F configuration, UE information, service information, QoS information, data / signaling / message for forwarding).

[0286] S&F Configuration

[0287] The second signaling (or information) may be (or include) one or more configurations related to S&F. The one or more configurations may be used by the satellite NW.

[0288] The satellite NW may store one or more configurations, for example, when / when / after / in response to receiving the second signaling (or configuration) when the second signaling (or configuration) is received. The satellite NW may apply one or more configurations, for example, when the feeder link of the satellite NW is unavailable / when the feeder link of the satellite NW is unavailable / if the feeder link of the satellite NW is unavailable / in response to the feeder link of the satellite NW being unavailable, when the satellite NW starts to use S&F operation / when the satellite NW starts to use S&F operation / if the satellite NW starts to use S&F operation / in response to the satellite NW starting to use S&F operation. The satellite NW may update its current configuration by one or more configurations received in the second signaling, for example, if the satellite NW has already been configured with some S&F configurations.

[0289] The ground NW may provide one or more configurations related to S&F to the satellite NW, for example, when the ground NW accepts a request for S&F operation / if the ground NW accepts a request for S&F operation / when the ground NW accepts a request for S&F operation / in response to the ground NW accepting a request for S&F operation.

[0290] The configuration may be one or more of the S&F configurations mentioned in this disclosure.

[0291] UE Information

[0292] The second signaling (or information) may be (or include) (at least) information related to one or more UEs. The terrestrial NW may have data / signaling / messages to be sent to the UE. The data / signaling / messages may be forwarded to the UE via the satellite NW. The UE may (or may) be served by the satellite NW, for example, in the next S&F operation in the future. The UE may be served by the satellite NW, for example, currently in S&F operation, previously in a previous S&F operation.

[0293] The information may be (or include) (at least) a UE identifier (or UE identity) of the UE. The information may be (or include) a UE identifier list of a UE list. One UE identifier (or UE identity) in the list may correspond to one UE.

[0294] The UE identifier (or UE identity) may be (or include) (at least) SUPI, IMSI, GUTI, 5G-GUTI, SUCI, PEI, RNTI, C-RNTI, I-RNTI and / or part of the above.

[0295] The information may be (or include) (at least) a UE context of a UE. The information may be (or include) a UE context list of a UE list. One UE context in the list may correspond to one UE.

[0296] The UE context may be (or include) (at least) AS configuration, RRC configuration, AS context, UE capability, RRM configuration and / or part of the above.

[0297] The information may be (or include) (at least) a configuration of the UE. The information may be (or include) a configuration list of a UE list. One configuration in the list may correspond to one UE. The configuration may be related to S&F. The configuration may be one or more of the S&F configurations mentioned in the present disclosure.

[0298] Service and / or QoS related information

[0299] The second signaling (or information) may be (or include) information related to one or more services and / or QoS. The services and / or QoS may be services and / or QoS that the satellite NW will support in S&F operations. The services may be (or include) delay tolerance. The services may be (or include) non-real time.

[0300] The information may be (or include) (at least) one or more QoS parameters mentioned in the present disclosure.

[0301] Data / signaling / message (to be forwarded or stored)

[0302] The second signaling may include (one or more) data / signaling / messages (to be stored in the satellite NW). The data / signaling / message is to be forwarded to one or more UEs. When the satellite NW does not have a feeder link, the data / signaling / message may be transmitted to one or more UEs, such as in S&F operation. The data / signaling / message may be associated with one or more UEs.

[0303] The data / signaling / message may be (user plane) data, control signaling, upper layer signaling, NAS message, RRC message, NAS PDU, NAS SDU, IP packet, PDCP SDU and / or PDCP PDU.

[0304] Time Information

[0305] The second signaling (or time information) may indicate the time (and / or duration) when the feeder link (of the satellite NW) is unavailable (or will be unavailable). The first signaling (or time information) may indicate the time (and / or duration) when the S&F operation is used (or will be used). The time information may be an estimate of the satellite NW. The time information may be (or include) a start time, an end time, and / or a duration. The time information may be derived (or calculated, or estimated) based on satellite information (e.g., ephemeris) of the satellite where the satellite NW is located.

[0306] The time information may be optional in the first signaling.

[0307] Neighboring satellite (or satellite NW) information

[0308] The second signaling (or information) may be (or include) information related to a neighboring satellite (or satellite NW). The neighboring satellite (or satellite NW) may have an ISL with the satellite NW. The satellite NW can communicate (or connect) with the neighboring satellite (or satellite NW) via one or more ISLs.

[0309] The information may be (or include) ephemeris information of a neighboring satellite. The information may be (or include) an ephemeris information list of a neighboring satellite list. One ephemeris information in the list may correspond to one neighboring satellite.

[0310] The information may be (or include) a network identity of a neighboring satellite NW. The information may be (or include) a network identity list of a neighboring satellite NW (node). One network identity in the list may correspond to one neighboring satellite NW (node).

[0311] In one or more examples, the ground NW may transmit a request to transmit data / signaling / message to the satellite NW (e.g., via a second signaling, for forwarding to one or more UEs). The satellite NW may transmit a response (e.g., via a first signaling, via a third signaling) indicating that the request is accepted (or rejected) and / or some related configurations (e.g., forwarding priority, data retention period, data storage quota) to the ground NW. When responding / if responding / in response to the response, the ground NW may transmit the stored data / signaling / message to the satellite NW, for example, based on the related configuration provided by the satellite NW (e.g., via a fourth signaling).

[0312] The second signaling (and / or the third signaling) may be initiated (or triggered) by (at least) one or more of the following conditions:

[0313] -Feeder link of satellite NW is available;

[0314] The condition may be when the feeder link is available (or becomes available) / if the feeder link is available (or becomes available) / when the feeder link is available (or becomes available) / in response to the feeder link being available (or becoming available). The satellite NW may return from unavailable to available. When the feeder link is unavailable, the satellite NW may be in S&F operation. When the feeder link is unavailable, the satellite NW may not be in S&F operation.

[0315] - Ground NW wants to use (or start) S&F operations;

[0316] - Ground NW wants to modify the (current) S&F operations;

[0317] - The terrestrial NW has data / signaling / messages to be forwarded or stored;

[0318] - The ground NW is (or has been) notified by the satellite NW; and / or

[0319] -When the first signaling or the third signaling (or request) / If the first signaling or the third signaling (or request) / At the time of the first signaling or the third signaling (or request) / In response to the first signaling or the third signaling (or request).

[0320] The second signaling (and / or the fourth signaling) may be (or include) (at least) AMF configuration update, RAN configuration update, initial context establishment request / response, NG reset, NG establishment request / response, PDU session resource establishment / modification request / response, UE context modification / suspend / resume request / response, downlink / uplink RAN ​​configuration transfer, UE information transfer, etc.

[0321] The procedure may be (or include) (at least) AMF configuration update, RAN configuration update, initial context establishment, NG reset, NG establishment, PDU session resource establishment / modification, UE context modification / suspend / resume, downlink / uplink RAN ​​configuration transfer, UE information transfer, etc.

[0322] The S&F configuration may be (or include) one or more of the following information: The S&F configuration may be specific to a satellite or a satellite NW. The S&F configuration may be specific to a satellite or a UE.

[0323] -Data retention period;

[0324] The information may be (or indicate) the time length for which data / signaling / messages may be stored (in total or for UE) in the satellite (or satellite NW). If the data / signaling / message is stored for too long (e.g., exceeds the data retention period), the data / signaling / message may be discarded (by the satellite NW).

[0325] -Data storage quota;

[0326] The information may be (or indicate) the amount of data / signaling / messages (in total or for UE) that can be stored in the satellite (or satellite NW). If the data / signaling / messages stored in the satellite NW are too much (e.g., exceeding the data storage limit), some data / signaling / messages may be discarded (by the satellite NW).

[0327] - forwarding priority; and / or

[0328] The information may be (or indicate) what type of data / signaling / message (total or for a UE) should be forwarded first. Data / signaling / message with a higher priority is forwarded first (eg, over data / signaling / message with a lower priority).

[0329] -Confirm the strategy.

[0330] The information may be (or indicate) whether the data / signaling / message requires confirmation.

[0331] After receiving the S&F configuration from the terrestrial NW (or in response to receiving the S&F configuration from the terrestrial NW), the satellite NW may provide (or broadcast) S&F-related indications and / or configurations in signaling (e.g., before the UE transmits data to the NW). The signaling is transmitted via the service link. The UE may determine (at least) based on the indications and / or configurations whether and / or how to transmit data and / or signaling (e.g., using S&F operation). For example, if the UE detects that the NW is using S&F operation (e.g., the feeder link is currently unavailable), the UE may use S&F operation and / or not generate (or transmit) data (or signaling) to the NW that is not suitable for S&F operation (e.g., cannot meet QoS requirements, such as delay requirements).

[0332] If the UE receives an indication and / or configuration related to S&F (signaling with the indication and / or configuration) (e.g., the indication and / or configuration is present and / or enabled), the UE may consider that the NW (e.g., satellite NW) is using S&F operation, is in S&F mode, the feeder link of the NW is unavailable, and / or the NW cannot forward data / signaling to the terrestrial NW. The UE may use (or enable) S&F operation (in response).

[0333] If the UE does not receive signaling, does not receive an indication and / or configuration related to S&F, and / or the indication and / or configuration does not exist and / or is deactivated, then the UE may assume that the NW (e.g., satellite NW) is not using S&F operation, is not in S&F mode, the NW's feeder link is available, and / or the NW is able to forward data / signaling to the terrestrial NW. The UE may not use (or deactivate) S&F operation (in response).

[0334] Indications and / or configurations related to S&F may be provided in broadcast signaling (provided by NW, such as provided by satellite NW) (to UE), such as system information, paging. The UE may obtain the broadcast signaling when (or in response to) camping / selecting / reselecting a cell, switching (to the cell), changing the serving cell (to the cell) and / or being notified by the NW (e.g., notification of a system information change).

[0335] Indications and / or configurations related to S&F may be provided in dedicated signaling (provided by the NW, e.g., provided by a satellite NW) (to the UE). The dedicated signaling may be a NAS message or an RRC message. The dedicated signaling may be a reconfiguration message (e.g., an RRC reconfiguration message). The dedicated signaling may be a NAS notification message. The dedicated signaling may be a paging message.

[0336] The dedicated signaling may be a response message to the UE request. The dedicated signaling may be a NAS message or an RRC message. The UE request may be a request message to establish an RRC connection, a NAS connection and / or a PDU session. The UE request may be a service request.

[0337] Indications and / or configurations related to S&F may (or may not) be provided during a procedure (e.g., between a UE and a NW). The procedure may be initiated by the UE. The procedure may be initiated by the NW. The procedure may (or may not) be a registration procedure. The registration procedure may (or may not) be used for initial registration. The registration procedure may (or may not) be used for mobility registration updates. The registration procedure may (or may not) be used for periodic registration updates. The procedure may (or may not) be a service request procedure. The procedure may (or may not) be a notification procedure. The procedure may (or may not) be a PDU session establishment procedure. The procedure may (or may not) be a PDU session modification procedure.

[0338] The NW may determine whether to provide S&F-related indications and / or configurations (at least) based on whether the NW's feeder link is available. For example, if the NW receives a UE request from the UE (e.g., to establish / modify an RRC connection, a NAS connection, and / or a PDU session), the NW may determine (at least) whether the NW's feeder link is available and / or whether the UE request (e.g., the corresponding connection, PDU session, and / or QoS flow) can be operated in the S&F operation (e.g., whether the corresponding QoS requirements can be met) and accept (or reject) the UE request. If yes, the NW may accept the UE request. The NW may provide S&F-related indications and / or configurations in the acceptance message. If not, the NW may reject the UE request. The NW may provide the rejection reason to the UE in the rejection message. The rejection reason may be related to the S&F operation, such as the unavailability of the feeder link.

[0339] The NW 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, a NG-RAN, an eNB, a gNB, a part of the above, and / or a combination of the above.

[0340] The NW 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, a NG-RAN, an eNB, a gNB, a part of the above, and / or a combination of the above.

[0341] Satellite NW and terrestrial NW may be mutually exclusive.

[0342] NW may be a cell. NW may be a serving cell. NW may be a neighboring cell. NW may be a source cell. NW may be a target cell.

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

[0344] The UE may be in CM Idle state. The UE may be in CM Connected state.

[0345] The UE may be in RM deregistered state. The UE may be in RM registered state.

[0346] 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 LEO, GEO, MEO, HEO and / or HAPS.

[0347] UE may be referred to as UE, an RRC entity of UE, or a MAC entity of UE.

[0348] The UE may be a NR device. The UE may be a NR light device. The UE may be a reduced capability device. The UE may be a mobile phone. The UE may be a wearable device. The UE may be a sensor. The UE may be a fixed device.

[0349] The network (NW) may be a network node. The network (NW) may be a base station. The network (NW) may be an access point. The network (NW) may be an eNB. The network (NW) may be a gNB. The network (NW) may be a gateway. The network (NW) may be an MME. The network (NW) may be an SGW. The network (NW) may be a PGW. The network (NW) may be an AMF. The network (NW) may be a UPF. The network (NW) may be an HSS.

[0350] The program may be (or include) a NAS program.

[0351] The program (eg, NAS program) may be (or include) a registration program. The program (eg, NAS program) may be (or include) a deregistration program.

[0352] The registration procedure may be used for initial registration. The UE may be in RM-DEREGISTERED state.

[0353] The registration procedure can be used for mobility registration. The registration procedure can be used for periodic registration.

[0354] The registration procedure can be used for emergency registration. The registration procedure can be used for disaster roaming registration.

[0355] A program (eg, a NAS program) may be (or include) a service request program.

[0356] The procedure (e.g., NAS procedure) may be (or include) a PDU session establishment procedure (requested by the UE). The procedure (e.g., NAS procedure) may be (or include) a PDU session modification procedure (requested by the UE). The procedure (e.g., NAS procedure) may be (or include) a PDU session release procedure (requested by the UE).

[0357] The program (eg, NAS program) may be (or include) a NAS transport program.

[0358] A program (eg, a NAS program) may be (or include) an attach program. A program (eg, a NAS program) may be (or include) a detach program.

[0359] The procedure (eg, NAS procedure) may be (or include) a tracking area update procedure.

[0360] The procedure (eg, NAS procedure) may be (or include) a PDN connection procedure. The procedure (eg, NAS procedure) may be (or include) a PDN disconnection procedure.

[0361] The procedure (eg, NAS procedure) may be (or include) a bearer resource allocation procedure. The procedure (eg, NAS procedure) may be (or include) a bearer resource modification procedure.

[0362] The program (eg, the first program, the second program, the third program) may be (or include) an RRC program.

[0363] The procedure (eg, RRC procedure) may be (or include) an RRC connection establishment procedure.

[0364] The procedure (eg, RRC procedure) may be (or include) an RRC connection re-establishment procedure.

[0365] The procedure (eg, RRC procedure) may be (or include) an RRC connection recovery procedure.

[0366] The procedure (eg, RRC procedure) may be (or include) a UL information transfer procedure.

[0367] The procedure (eg, RRC procedure) may be (or include) a UE assistance information procedure.

[0368] The procedure (eg, RRC procedure) may be (or include) a UL message segment delivery procedure.

[0369] Exemplary embodiments of the present invention are described below.

[0370] refer to Fig.18Through this and other concepts, systems and methods of the present invention, the method 1000 of the UE includes: receiving a configuration or indication related to S&F operation (step 1002), and determining whether to use S&F operation based on the configuration or indication (step 1004).

[0371] In various embodiments, the indication is an S&F mode indication.

[0372] In various embodiments, the configuration is a UE type configuration.

[0373] In various embodiments, the configuration is a business type configuration.

[0374] In various embodiments, the configuration is a QoS parameter.

[0375] In various embodiments, if the UE determines to use the S&F operation, the UE performs a procedure or transmission based on the S&F operation.

[0376] In various embodiments, if the UE determines not to use S&F operation, then the UE does not perform a procedure or transmission based on the S&F operation.

[0377] Return to reference Figure 3 and Figure 4 In one or more embodiments from the perspective of the UE, the apparatus 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 a configuration or indication related to S&F operation; and (ii) determine whether to use S&F operation based on the configuration or indication. In addition, the CPU 308 can execute the program code 312 to perform all of the actions, steps, and methods described above, below, or otherwise herein.

[0378] refer to Fig.19 , through this and other concepts, systems and methods of the present invention, the method 1010 of the first network node includes transmitting first signaling to the second network node, wherein the first signaling is used to indicate or request an S&F operation (step 1012); and receiving second signaling from the second network node, wherein the second signaling at least includes one or more configurations related to the S&F operation (step 1014).

[0379] In various embodiments, the first network node is located in a satellite.

[0380] In various embodiments, the first network node is a NG-RAN node.

[0381] In various embodiments, the second network node is located on the ground.

[0382] In various embodiments, the second network node is a 5G CN node.

[0383] In various embodiments, the second signaling is a response to the first signaling.

[0384] In various embodiments, the method further includes transmitting third signaling to the second network node, wherein the third signaling is transmitted in response to receiving the second signaling.

[0385] Return to reference Figure 3 and Figure 4 In one or more embodiments from the perspective of the first network node, the apparatus 300 includes a program code 312 stored in a memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) transmit a first signaling to the second network node, wherein the first signaling is used to indicate or request an S&F operation; and (ii) receive a second signaling from the second network node, wherein the second signaling at least includes one or more configurations related to the S&F operation. In addition, the CPU 308 may execute the program code 312 to perform all of the actions, steps, and methods described above, below, or otherwise herein.

[0386] refer to Fig. 20 , through this and other concepts, systems and methods of the present invention, the method 1020 of the second network node includes: receiving first signaling from the first network node, wherein the first signaling is used to indicate or request an S&F operation (step 1022); and transmitting second signaling to the first network node, wherein the second signaling at least includes one or more configurations related to the S&F operation (step 1024).

[0387] In various embodiments, the first network node is located in a satellite.

[0388] In various embodiments, the first network node is a NG-RAN node.

[0389] In various embodiments, the second network node is located on the ground.

[0390] In various embodiments, the second network node is a 5G CN node.

[0391] In various embodiments, the second signaling is a response to the first signaling.

[0392] In various embodiments, the method further includes transmitting third signaling to the second network node, wherein the third signaling is transmitted in response to receiving the second signaling.

[0393] Return to reference Figure 3 and Figure 4In one or more embodiments from the perspective of the second network node, the apparatus 300 includes a program code 312 stored in a memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) receive a first signaling from the first network node, wherein the first signaling is used to indicate or request an S&F operation; and (ii) transmit a second signaling to the first network node, wherein the second signaling at least includes one or more configurations related to the S&F operation. In addition, the CPU 308 may execute the program code 312 to perform all of the actions, steps, and methods described above, below, or otherwise herein.

[0394] refer to Fig.21 , through this and other concepts, systems and methods of the present invention, the method 1030 of the UE includes: providing an indication or configuration about the service type for S&F operation from the network (step 1032); and determining whether to use S&F operation based on the indication or configuration (step 1034).

[0395] In various embodiments, S&F operations provide communication services when a feeder link of the network is unavailable.

[0396] In various embodiments, the feeder link is a connection between the satellite network and the terrestrial network.

[0397] In various embodiments, if the first service satisfies the indicated or configured conditions, the UE considers that the S&F operation is allowed for the first service.

[0398] In various embodiments, if the UE considers that the S&F operation is allowed for the first service, the UE determines to perform a transfer or initiation procedure using the S&F operation for the first service.

[0399] In various embodiments, if the second service does not satisfy the indicated or configured conditions, the UE considers that the S&F operation is not allowed for the second service.

[0400] In various embodiments, if the UE considers that the S&F operation is not allowed for the second service, the UE determines to perform transmission without using the S&F operation or to initiate a procedure without using the S&F operation for the second service.

[0401] In various embodiments, the configuration is pre-configured.

[0402] In various embodiments, the indication or configuration is included in a system information or NAS message.

[0403] In various embodiments, the indication or configuration is included in a response message to the UE request or is included during a registration procedure.

[0404] Return to reference Figure 3 and Figure 4 In one or more embodiments from the perspective of the UE, the apparatus 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) provide an indication or configuration from the network regarding the type of service to be used for S&F operation; and (ii) determine whether to use S&F operation based on the indication or configuration. In addition, the CPU 308 may execute the program code 312 to perform all of the actions, steps, and methods described above, below, or otherwise herein.

[0405] Any combination of the concepts or teachings above or here can be combined or formed into new embodiments in whole or in part. The disclosed details and embodiments can be used to solve at least (but not limited to) the problems mentioned above and here.

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

[0407] 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 only representative. Based on the teachings herein, it should be understood by those skilled in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, by using other structures, functionality, or structures and functionality other than one or more aspects of the aspects set forth herein or different from one or more aspects of the aspects set forth herein, this device can be implemented or this method can be practiced. As an example of some of the above concepts, in some aspects, parallel channels can be established based on pulse repetition frequency. In some aspects, parallel channels can be established based on pulse position or offset. In some aspects, parallel channels can be established based on time hopping sequences. In some aspects, parallel channels can be established based on pulse repetition frequency, pulse position or offset, and time hopping sequences.

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

[0409] 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 conjunction with the various aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two, which may be designed using source decoding or some other technique), and various forms of programs or design code with instructions (which may be referred to herein as "software" or "software modules" for convenience), or a combination of the two. To clearly illustrate this interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those of ordinary skill in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0410] In addition, the various illustrative logical blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented within or performed by an integrated circuit ("IC"), an access terminal, or an access point. An IC may include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, outside the IC, or both. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration.

[0411] It should be understood that any specific order or hierarchy of steps in any disclosed process is an example of an exemplary 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 elements of the various steps in an exemplary order, but are not meant to be limited to the specific order or hierarchy presented.

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

[0413] Although the present invention has been described in conjunction with various aspects and examples, it will be appreciated that the present invention is capable of further modifications. This application is intended to cover any changes, uses or adaptations of the present invention, which generally follow the principles of the present invention and include such deviations from the present disclosure, which are within the scope of known and customary practice in the technical field to which the present invention belongs.

Claims

1. A method for handling user equipment configured for non-terrestrial network storage and forwarding, characterized in that include: providing an indication or configuration from the network regarding the type of traffic to be used for store and forward operations; as well as Based on the indication or the configuration, it is determined whether to use the store and forward operation.

2. The method according to claim 1, characterized in that The store and forward operation provides communication services when a feeder link of the network is unavailable.

3. The method according to claim 2, characterized in that The feeder link is the connection between the satellite network and the terrestrial network.

4. The method according to claim 1, characterized in that: If the first service meets the indicated or configured condition, the user equipment considers that the store and forward operation is allowed for the first service.

5. The method according to claim 4, characterized in that If the user equipment considers that the store and forward operation is allowed for the first service, the user equipment determines to perform a transfer or initiation procedure using the store and forward operation for the first service.

6. The method according to claim 1, characterized in that If the second service does not meet the indicated or configured condition, the user equipment considers that the store and forward operation is not allowed for the second service.

7. The method according to claim 6, characterized in that If the user equipment considers that the store and forward operation is not allowed for the second service, the user equipment determines to perform transmission without using the store and forward operation or to initiate a procedure without using the store and forward operation for the second service.

8. The method according to claim 1, characterized in that The configuration is pre-configured.

9. The method according to claim 1, characterized in that: The indication or the configuration is included in system information or non-access stratum message.

10. The method according to claim 1, characterized in that The indication or the configuration is included in a response message to a user equipment request or is included during a registration procedure.

11. A user equipment for handling non-terrestrial network storage and forwarding configuration, characterized in that include: Memory; as well as a processor operatively coupled to the memory, wherein the processor is configured to execute program code to: providing an indication or configuration from the network as to the type of traffic to be used for store and forward operations; and Based on the indication or the configuration, it is determined whether to use the store and forward operation.

12. The user equipment according to claim 11, characterized in that The store and forward operation provides communication services when a feeder link of the network is unavailable.

13. The user equipment according to claim 12, characterized in that: The feeder link is the connection between the satellite network and the terrestrial network.

14. The user equipment according to claim 11, characterized in that If the first service meets the indicated or configured condition, the user equipment considers that the store and forward operation is allowed for the first service.

15. The user equipment according to claim 14, characterized in that: If the user equipment considers that the store and forward operation is allowed for the first service, the user equipment determines to perform a transfer or initiation procedure using the store and forward operation for the first service.

16. The user equipment according to claim 11, characterized in that If the second service does not meet the indicated or configured condition, the user equipment considers that the store and forward operation is not allowed for the second service.

17. The user equipment according to claim 16, characterized in that If the user equipment considers that the store and forward operation is not allowed for the second service, the user equipment determines to perform transmission without using the store and forward operation or to initiate a procedure without using the store and forward operation for the second service.

18. The user equipment according to claim 11, characterized in that The configuration is pre-configured.

19. The user equipment according to claim 11, characterized in that The indication or the configuration is included in system information or non-access stratum message.

20. The user equipment according to claim 11, characterized in that The indication or the configuration is included in a response message to a user equipment request or is included during a registration procedure.

Images