Method for optimizing nas registration procedure with store-and-forward operation in non-terrestrial networks

Abstract

According to example embodiments of the present application, there are at least a method and apparatus to perform: transmitting, from a user equipment to a network node of a non-terrestrial network, first information comprising a radio resource control setup request, wherein based on the transmitting, at least one timer is started based on the radio resource control setup request, at least one of a response of the non-terrestrial network to the first information or a creation of a radio resource control connection, and wherein the at least one timer is dynamically updated based on at least one of an identity of the user equipment or a satellite of the non-terrestrial network to which the user equipment is attached; based on the at least one timer expiring due to a feeder link being unavailable, transmitting an indication of a first radio resource control reject message between the network node and the user equipment; and based on the first radio resource control reject message, transmitting another radio resource control setup request to another network node of the non-terrestrial network.

Description

Technical Field

[0001] The teachings of the exemplary embodiments of the present invention generally relate to a first NAS registration request message sent by a UE and received by a satellite gNB using at least one timer, and more specifically to a first NAS registration request message sent by a UE and received by a satellite gNB using at least one timer, wherein if the timer expires, a corresponding response can be calculated and sent back to the UE for NAS registration. Background Technology

[0002] This section is intended to provide background or context for the invention as set forth in the claims. The description herein may include concepts that may be explored, but are not necessarily concepts that have been previously conceived or explored. Therefore, unless otherwise indicated herein, what is described in this section is not prior art to the specification and claims of this application, and is not acknowledged as prior art by virtue of its inclusion in this section.

[0003] The following are definitions of some abbreviations that may appear in the instruction manual and / or drawings: 3GPP: Third Generation Partnership Project AI / ML: Artificial Intelligence and Machine Learning AMF: Access and Mobility Management Functions AUSF: Authentication Server Function NAS: Non-Access Layer NTN: Non-terrestrial network RAN: Radio Access Network RAT: Radio Access Technology RRC: Radio Resource Control S&F: Store and Forward SAT: Satellite UE: User Equipment

[0004] For 5GS mobility management via satellite NG-RAN cells, the UE shall apply the applicable NAS timer values ​​indicated in the table of Clause 10.2.1 of TS 24.501 for access via satellite NG-RAN cells.

[0005] In these operations, NAS timer values ​​are applied based on the current satellite NG-RAN access RAT type determined from information from lower layers.

[0006] The exemplary embodiments of the present invention propose at least improved mobility optimizations for NTN. Summary of the Invention

[0007] This section includes examples of possible implementations and does not imply any limitations.

[0008] In another example aspect of the invention, there is an apparatus, such as a network-side apparatus, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: transmit from a user equipment to a network node of a non-terrestrial network a first message including a radio resource control (RFC) establishment request, wherein based on the transmission, at least one timer is started based on the RFC establishment request, at least one of a response to the first message from the non-terrestrial network, or the creation of a RFC connection, and wherein the at least one timer is dynamically updated based on at least one of: the identifier of the user equipment or a satellite of the non-terrestrial network to which the user equipment is attached; an indication to transmit a first RFC rejection message between the network node and the user equipment based on the at least one timer expiring due to feeder link unavailability; and based on the first RFC rejection message, transmit another RFC establishment request to another network node of the non-terrestrial network.

[0009] In another example aspect of the invention, there is a method comprising: transmitting from a user equipment to a network node of a non-terrestrial network first information including a radio resource control establishment request, wherein based on the transmission, at least one timer is started based on the radio resource control establishment request, at least one of a response to the first information of the non-terrestrial network or the creation of a radio resource control connection, and wherein the at least one timer is dynamically updated based on at least one of: an identifier of the user equipment or a satellite of the non-terrestrial network to which the user equipment is attached; an indication that a first radio resource control rejection message is transmitted between the network node and the user equipment based on the at least one timer expiring due to a feeder link being unavailable; and transmitting another radio resource control establishment request to another network node of the non-terrestrial network based on the first radio resource control rejection message.

[0010] Another example embodiment is an apparatus and a method comprising the apparatus and method described in the foregoing paragraphs, wherein information including a radio resource control (RFC) establishment request is transmitted, wherein an initial random access channel procedure is transmitted with a network node in a non-terrestrial network; and based on the initial random access channel procedure, a RFC establishment request and store-and-forward availability are transmitted with the network node, wherein a first RFC rejection message includes redirected carrier information; and wherein based on the redirected carrier information, another RFC establishment request is transmitted with another network node in the non-terrestrial network, wherein the redirected carrier information includes an indication of a waiting time, for which a feeder link can be used to communicate with the other network node, wherein based on the redirected carrier information... The information includes at least one timer updated in the non-terrestrial network, wherein at least one timer is dynamically updated for each user equipment (UE) in the UE, wherein at least one timer uses the total time spent in network-attached storage and an offset of five times the total time, wherein the total time uses the time spent in network-attached storage registration requests from the network node to the non-terrestrial network, wherein the total time considers four message exchanges between core network functions and one message exchange between the random access network and the core network function, and wherein it is assumed that each message exchange will take the same amount of time, wherein the timer is one of a network-attached storage wait type timer or a store-and-forward type timer, wherein the network-attached storage wait type timer allows for updates between the UE and the network-attached storage. The time for network attachment storage registration requests between network nodes, wherein the store-and-forward type timer allows sufficient time for the network attachment storage registration process to be completed during intermittent gaps in the feeder link connection, wherein the network attachment storage wait type timer uses store-and-forward values ​​to obtain a statistical approximation of the expected network attachment storage timer for store-and-forward functionality, wherein additional offsets or buffers are added to the previous network attachment storage wait type timer for store-and-forward values ​​to create or update a new network attachment storage wait type timer, wherein the previous network attachment storage wait type timer for store-and-forward values ​​is used to obtain statistics of the expected network attachment storage timer for store-and-forward functionality. Approximate or calculated value estimates are used to create or update new network attached storage wait type timers, wherein statistical approximations or calculated value estimates are used depending on which has the larger value, wherein new network attached storage wait type timers are added to statistics to continuously improve the estimates, including information from radio resource control establishment requests using network attached storage store and forwarding flags, wherein user equipment supports store and forwarding functionality based on the use of network attached storage store and forwarding flags, wherein network attached storage store and forwarding flags are not used based on information including radio resource control establishment requests, and network attached storage registration rejection messages for radio resource control establishment requests are transmitted between user equipment and network nodes;And based on a network attached storage registration rejection message, a new store-and-forward type timer is created or updated in a non-terrestrial network, wherein based on the network attached storage registration rejection message, another network attached storage registration process is retried between the user equipment and the network node using another radio resource control establishment request, wherein regardless of whether the other radio resource control establishment request includes a network attached storage store-and-forward flag, at least one new timer value for store-and-forward is used between the user equipment and the network node for the other network attached storage registration process, wherein the new at least one timer value is configured to: allow sufficient time for the network attached storage registration process to be completed to account for intermittent gaps in the feeder link connection, wherein a new inter-satellite link is created for sharing the updated and latest data between satellites in the non-terrestrial network, and / or wherein the calculated time value of the new at least one timer is transmitted between the user equipment and the network node.

[0011] A non-transitory computer-readable medium storing program code that is executed by at least one processor to perform at least the methods described in the preceding paragraphs.

[0012] In another example aspect of the invention, there is an apparatus comprising: means for transmitting first information including a radio resource control establishment request from a user equipment to a network node of a non-terrestrial network, wherein based on the transmission, at least one timer is started based on at least one of the radio resource control establishment request, a response to the first information of the non-terrestrial network, or the creation of a radio resource control connection, and wherein the at least one timer is dynamically updated based on at least one of: the identifier of the user equipment or a satellite of the non-terrestrial network to which the user equipment is attached; means for transmitting an indication of a first radio resource control rejection message between the network node and the user equipment based on the expiration of at least one timer due to feeder link unavailability; and means for transmitting another radio resource control establishment request to another network node of the non-terrestrial network based on the first radio resource control rejection message.

[0013] A communication system includes a network-side device and a user equipment-side device for performing the above operations. Attached Figure Description

[0014] The above and other aspects, features, and benefits of various embodiments of the present disclosure will become more fully apparent from the following detailed description with reference to the accompanying drawings, in which the same reference numerals are used to designate the same or equivalent elements. The drawings are shown to facilitate a better understanding of the embodiments of the present disclosure and are not necessarily drawn to scale.

[0015] Figure 1 This illustrates a store-and-forward (S&F) scenario for non-terrestrial networks (NTNs).

[0016] Figure 2 A flowchart illustrating operation according to an exemplary embodiment of the present invention is shown;

[0017] Figure 3 A high-level block diagram of various devices for carrying out various aspects of the present invention is shown; and

[0018] Figure 4 A method that can be performed by an apparatus according to an example embodiment of the present invention is shown. Detailed Implementation

[0019] In an exemplary embodiment of the present invention, at least one method and apparatus are provided for a first NAS registration request message sent by a UE and received by a satellite gNB using at least one timer, wherein if the timer expires, a corresponding response can be calculated and sent back to the UE for NAS registration.

[0020] 5GS Mobility Management via Satellite NG-RAN Cells

[0021] For 5GS mobility management via satellite NG-RAN cells, the UE shall apply the applicable NAS timer values ​​indicated in the table of Clause 10.2.1 of TS 24.501 for access via satellite NG-RAN cells.

[0022] Note that the applied NAS timer value is based on the current satellite NG-RAN access RAT type, which is determined according to information from lower layers.

[0023] The acquired NAS timer values ​​shall be used as described in the appropriate procedure subclause of this specification. The NAS timer values ​​shall be calculated at the start of the NAS procedure and shall not be recalculated until the NAS procedure is completed, restarted, or aborted.

[0024] Access via a satellite NG-RAN cell by the UE is indicated to the AMF by a lower layer and should be stored by the AMF. When an AMF that supports access via a satellite NG-RAN cell performs NAS signaling with the UE via a satellite NG-RAN cell, the AMF should calculate the value of the applicable NAS timer indicated in the table of Clause 10.2.2 of TS 24.501 for access via a satellite NG-RAN cell.

[0025] Note that the applied NAS timer value is based on the current satellite NG-RAN access RAT type, which is determined according to information from lower layers.

[0026] The acquired NAS timer values ​​shall be used as described in the appropriate procedure subclause of this specification. The NAS timer values ​​shall be calculated at the start of the NAS procedure and shall not be recalculated until the NAS procedure is completed, restarted, or aborted.

[0027] 5GS Session Management via Satellite NG-RAN Cell

[0028] For 5GS session management via satellite NG-RAN cells, the UE shall apply the applicable NAS timer values ​​indicated in the table of Clause 10.2.1 of TS 24.501 for access via satellite NG-RAN cells.

[0029] Note that the applied NAS timer value is based on the current satellite NG-RAN access RAT type, which is determined according to information from lower layers.

[0030] The acquired NAS timer values ​​shall be used as described in the appropriate procedure subclause of this specification. The NAS timer values ​​shall be calculated at the start of the NAS procedure and shall not be recalculated until the NAS procedure is completed, restarted, or aborted.

[0031] If the AMF instructs the use of an extended NAS timer for access via satellite NG-RAN cells (see 3GPP TS 23.501 and 3GPP TS 23.502), the SMF shall calculate the value of the applicable NAS timer indicated in the table of Clause 10.3.2 of TS 24.501 for access via satellite NG-RAN cells.

[0032] The acquired NAS timer values ​​shall be used as described in the appropriate procedure subclause of this specification. The NAS timer values ​​shall be calculated at the start of the NAS procedure and shall not be recalculated until the NAS procedure is completed, restarted, or aborted.

[0033] In NTN store-and-forward (S&F) scenarios, the end-to-end connection from the UE to the terrestrial network is unavailable. Feeder link connections may be intermittently lost. Therefore, when the UE sends a NAS registration request to establish a secure NAS connection, the registration request may not be responded to to the UE in a timely manner. Furthermore, due to the intermittent unavailability of the feeder link connection, subsequent packets sent by the UE may also be delayed. This necessitates S&F feature capabilities at both the UE and the satellite access network. This S&F feature was introduced in 3GPP Rel-19.

[0034] Some of the technical issues to be addressed are based on satellite connectivity supported by the UE since version 17 / 18. However, version 19 will support satellite + gNB S&F functionality. New UEs supporting version 19 will support the new features of version 19.

[0035] However, it should be noted that: • Storage and forwarding operations introduce more latency during NAS registration. This leads to multiple failed NAS registration requests from the UE, and consequently, higher power consumption in the UE; • For IoT devices, high power consumption can be detrimental and should be addressed through optimization methods for NAS registration processes with S&F operations. Ensuring longer battery life is crucial for IoT devices. Furthermore, starting with 6G, power consumption optimization is a critical feature, and failures should only result in wasted energy, even if it's used by the network. This invention focuses on providing an optimized method by updating timers in the UE.

[0036] Example: The UE sends a message and waits for a response from the gNB for several seconds. Since it is a store-and-forward satellite / gNB, the gNB may not respond for an extended period due to feeder link unavailability. Therefore, the UE connection will fail.

[0037] To date, this problem has not been resolved in the standard.

[0038] The exemplary embodiments of the present invention focus on solutions with minimal UE impact to support S&F characteristics to ensure optimized energy / battery usage.

[0039] Some key concepts to be addressed according to exemplary embodiments of the present invention include: • Older UE versions do not support S&F: Older UE versions are identified by S&T satellite (without an indicator flag), and then S&F uses an appropriate rejection timer to reject the request; • Version 19 UEs do not support store and forward: Because S&F is an optional feature, not all UEs will support S&F. In this case, the S&F satellite identifies those UEs by having a flag, then rejects the request and requires the UE to connect to another satellite that does not have S&F. • Version 19 UE supports store and forward: In this case, the S&F satellite identifies the UE by having a flag in the RRC message and then provides S&F functionality.

[0040] Before describing the exemplary embodiments disclosed herein in detail, refer to Figure 3 , Figure 3 Simplified block diagrams are shown of various electronic devices suitable for use in exemplary embodiments of the practice of the present invention.

[0041] Figure 3 A block diagram of one possible, non-limiting, exemplary system in which example embodiments can be practiced is shown. Figure 3 In the middle, User Equipment (UE) 10 and such Figure 3 Wireless communication is conducted via wireless network 1 or network 1. For example... Figure 3 The wireless network 1 or network 1 in the document may include a communication network, such as a mobile network, for example, mobile network 1 or a first mobile network as disclosed herein. In this document, as... Figure 3 Any reference to wireless network 1 in this document may be regarded as a reference to any wireless network disclosed herein. Furthermore, as... Figure 3 The wireless network 1 in the RAN may also include hard-wired features that the communication network may require. The UE is a wireless device that can access the wireless network, typically a mobile device. For example, the UE may be a mobile phone (or "cellular") and / or a computer with mobile terminal capabilities. For example, the UE or mobile terminal may also be a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device that performs voice signaling and / or data exchange with the RAN.

[0042] UE 10 includes one or more processors DP 10A, one or more memories MEM 10B, and one or more transceivers TRANS 10D interconnected via one or more buses. Each of the one or more transceivers TRANS 10D includes a receiver and a transmitter. The one or more buses may be address buses, data buses, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optic cables, or other optical communication devices. The one or more transceivers TRANS 10D may optionally be connected to one or more antennas for communicating with NN 12 and NN 13 accordingly. The one or more memories MEM 10B include computer program code PROG 10C. UE 10 communicates with NN12 and / or NN 13 via wireless links 11 or 16.

[0043] NN 12 (NR / 5G / 6G node B, evolved NB or LTE equipment) is related to, for example Figure 3The NN 12 is a network node that communicates with devices such as NN 13 and UE 10, such as a primary node base station or a secondary node base station (e.g., for NR or LTE Long Term Evolution). NN 12 provides access to the wireless network 1 to wireless devices such as UE 10. NN 12 includes one or more processors DP 12A, one or more memories MEM 12B, and one or more transceivers TRANS 12D interconnected via one or more buses. According to an example embodiment, these TRANS 12Ds may include X2 and / or Xn interfaces for performing the example embodiment. Each of the one or more transceivers TRANS 12D includes a receiver and a transmitter. The one or more transceivers TRANS 12D may optionally be connected to one or more antennas for communicating with UE 10 via at least link 11. One or more memories MEM 12B and computer program code PROG 12C are configured, together with one or more processors DP 12A, to cause NN 12 to perform one or more of the operations described herein. NN 12 can communicate with another gNB or eNB, or devices such as NN 13, for example, via link 16 or link 18. Furthermore, link 11, link 16, and / or any other link can be wired, wireless, or both, and can implement, for example, an X2 or Xn interface. Additionally, link 11 and / or link 16 and / or link 18 can communicate via other network devices, such as, but not limited to, Figure 3 The NN 12 is an NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 device. It can perform the functions of MME (Mobility Management Entity) or SGW (Serving Gateway), such as user plane functions and / or access management functions for LTE and similar functions for 5G or 6G.

[0044] NN 13 can be used for WiFi or Bluetooth or other wireless devices associated with mobility function devices such as AMF or SMF. Furthermore, NN 13 may include NR / 5G / 6G Node B or possible evolved NB base stations, such as primary or secondary node base stations (e.g., for NR or LTE LTE) communicating with devices such as NN12 and / or UE 10 and / or Wireless Network 1. NN 13 includes one or more processors DP 13A, one or more memories MEM 13B, one or more network interfaces, and one or more transceivers TRANS 13D interconnected via one or more buses. According to an example embodiment, these network interfaces of NN 13 may include X2 and / or Xn interfaces for performing the example embodiment. Each of the one or more transceivers TRANS 13D includes a receiver and a transmitter that can be optionally connected to one or more antennas. The one or more memories MEM 13B include computer program code PROG 13C. For example, one or more memory MEM 13B and computer program code PROG 13C are configured, together with one or more processors DP 13A, to cause NN 13 to perform one or more of the operations described herein. NN 13 can communicate with another mobility function device and / or eNB (such as NN 12 and UE 10) or any other device using, for example, link 11, link 16, link 18, or another link. Figure 3 Link 16 or link 18 shown can be used for communication with NN 12. These links can be wired, wireless, or both, and can implement, for example, an X2 or Xn interface. Furthermore, as mentioned above, links 11 and / or 16 and / or 18 can be connected via other network devices, such as, but not limited to, NCE / MME / SGW devices, such as... Figure 3 NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14.

[0045] Figure 3 One or more buses of the device can be address buses, data buses, or control buses, and can include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fiber or other optical communication devices, wireless channels, etc. For example, one or more transceivers TRANS 12D, TRANS 13D, and / or TRANS 10D can be implemented as remote radio head ends (RRHs), where other components of NN 12 are physically located at a different location from the RRH, and these devices can include one or more buses, which can be partially implemented as fiber optic cables to connect other components of NN 12 to the RRH.

[0046] It should be noted that, although Figure 3Network nodes such as NN 12 and NN 13 are shown, but any of these nodes can be incorporated into or be incorporated into eNodeBs, eNBs, or gNBs for LTE and NR, and can still be configured to perform the example embodiments.

[0047] It should also be noted that the description in this document indicates that a "cell" performs the function; however, it should be clear that it is the gNB and / or user equipment and / or mobility management function equipment that forms the cell that will perform the function. Furthermore, a cell constitutes part of a gNB, and each gNB may have multiple cells.

[0048] Wireless Network 1 or any network that it may represent may include or may not include NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14, which may include (NCE) network control element functions, MME (Mobility Management Entity) / SGW (Serving Gateway) functions and / or Serving Gateway (SGW) and / or MME (Mobility Management Entity) and / or SGW (Serving Gateway) functions and / or User Data Management (UDM) functions and / or PCF (Policy Control) functions and / or Access and Mobility Management (AMF) functions and / or Session Management (SMF) functions and / or Location Management (LMF) functions and / or Authentication Server (AUSF) functions, and provide connectivity to other networks, such as telephone networks and / or data communication networks (e.g., the Internet), and is configured to perform any 5G, 6G and / or NR operations in addition to or in lieu of other standard operations at the time of this application. NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 can be configured to perform operations according to example embodiments of LTE, NR, 5G, 6G and / or any standard-based communication technology being implemented or discussed at the time of this application. Additionally, it should be noted that operations performed by NN 12 and / or NN 13 according to example embodiments can also be performed at NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14.

[0049] NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 includes one or more processors DP 14A, one or more memories MEM 14B, and one or more network interfaces ((multiple) N / WI / F) interconnected via one or more buses coupled to link 13 and / or link 16 and / or link 18. According to an example embodiment, these network interfaces may include X2 and / or Xn interfaces for performing the example embodiment. One or more memories MEM 14B include computer program code PROG 14C. The one or more memories MEM 14B and computer program code PROG 14C are configured, together with the one or more processors DP 14A, to cause NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 to perform one or more operations that may be required to support the operation according to the example embodiment.

[0050] It should be noted that NN 12 and / or NN 13 and / or UE 10 can be configured (e.g., based on standard implementations, etc.) to perform Location Management Function (LMF) functionality. LMF functionality can be embodied in any of these network devices or other devices associated with them. Additionally, at least as described below, LMF (such as...) Figure 3 The MME / SGW / UDM / PCF / AMF / SMF / LMF14 (LMF) can co-address with UE 10, such as with Figure 3 The NN 12 and / or NN 13 are separated for use in performing operations according to the example embodiments disclosed herein.

[0051] Wireless Network 1 can implement network virtualization, which is the process of combining hardware and software network resources and network functions into a single software-based management entity (virtual network). Network virtualization involves platform virtualization, which is often combined with resource virtualization. Network virtualization can be external (combining many networks or parts of networks into virtual units) or internal (providing network-like functionality to a software container on a single system). It should be noted that the virtualized entities created by network virtualization are still implemented to some extent using hardware such as processors DP 10, DP 12A, DP 13A and / or DP 14A and memory MEM 10B, MEM 12B, MEM 13B and / or MEM 14B, and such virtualized entities also create technical effects.

[0052] Computer-readable storage devices MEM 12B, MEM 13B, and MEM 14B can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic storage devices and systems, optical storage devices and systems, fixed memory, and removable memory. Computer-readable storage devices MEM 12B, MEM 13B, and MEM 14B can be components for performing storage functions. Processors DP 10, DP12A, DP 13A, and DP 14A can be of any type suitable for the local technical environment and, as a non-limiting example, can include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Processors DP 10, DP 12A, DP 13A, and DP 14A can be means for performing functions, such as controlling UE 10, NN 12, NN 13, and other functions as described herein.

[0053] Typically, various embodiments of any of these devices may include, but are not limited to, cellular phones (such as smartphones), tablet computers, personal digital assistants (PDAs) with wireless communication capabilities, portable computers with wireless communication capabilities, image capture devices (such as digital cameras with wireless communication capabilities), gaming devices with wireless communication capabilities, music storage and playback devices with wireless communication capabilities, internet devices that allow wireless internet access and browsing, tablet computers with wireless communication capabilities, and portable units or terminals that combine these functions.

[0054] Furthermore, various embodiments of any of these devices can be used with UE vehicles, high-altitude platform stations, or any other such type of node associated with a terrestrial network, or with any type of drone radio or radio in an aircraft or other airborne vehicle or vessel traveling on water (such as a ship).

[0055] As described above, some key concepts according to exemplary embodiments of the present invention include: • Older UE versions do not support S&F: Older UE versions are identified by S&T satellite (without indicator flags), and then S&F rejects the request with an appropriate rejection timer; • Version 19 UEs do not support store and forward: Because S&F is an optional feature, not all UEs will support S&F. In this case, the S&F satellite identifies those UEs by having a flag, then rejects the request and requires the UE to connect to another satellite that does not have S&F. • Version 19 UE supports store and forward: In this case, the S&F satellite identifies the UE by having a flag in the RRC message and then provides S&F functionality.

[0056] An example embodiment of the present invention relates to an NTN (non-terrestrial network) with a satellite access point, where "store and forward" (S&F) capabilities are supported. When S&F is deployed, entities can store data and forward the stored data only when the link becomes available later. In an NTN, the links (feeder links) between the UE and the satellite, and between the satellite and the ground station, may only be available at certain times. For user data, especially data related to IoT devices that, for example, only send some data from time to time and do not require real-time processing, the fact that the data will only be delivered later is not a problem, but this can be a problem for signaling (e.g., UE registration requests). When a UE sends a registration request, the UE also starts a timer to see if the required response is received. If no response is received and the timer times out, the process is aborted. (And a new registration request can be sent after a waiting period). Obviously, for both NTN and S&F, the required response can only be received later, so the corresponding timer needs to be adjusted. Although this requirement is generally known, the example embodiments of the present invention describe how (even for each UE) the process of dynamically adapting the timer.

[0057] Example embodiments of the present invention provide at least the following: The new indicator field in the RRC SETUP REQUEST message can be used by the satellite + gNB to check whether the UE supports store-and-forward functionality. ○ The missing indication message for this field is received from a UE that does not support the Rel-19 S&F feature; • Calculate NAS timers T3510 and T3517 for the S&F scenario, and update these timers in the AMF and UE using the first NAS registration rejection message. ○ When the UE first connects to the satellite gNB and the new field is not presented in the RRC SETUP REQUEST, and if the feeder link is unavailable, the satellite gNB begins calculating NAS timer T3510 for the S&F scenario. This invention proposes a new NAS timer T3510 for calculating S&F scenarios. This can be considered as the total time spent receiving the first response to the NAS registration request from the core network, plus a 5-fold offset of that time: NAS timer for S&F = 5 (The time spent between the NAS registration request sent from the satellite gNB to the core network and the authentication request received from the core network). This calculation considers four message exchanges between core network functions and one message exchange between the RAN and the core network function, and assumes that each message exchange will take the same amount of time. ○ In some embodiments, additional offsets or buffers may be added to the NAS timer calculated in the above steps; In some other embodiments, the previous "N" NAS timers used for the S&F value can be maintained to obtain a statistical approximation of the expected NAS timers for the S&F function: This statistical estimate or calculated value can be used depending on which value has the larger value. Furthermore, each new NAS timer used for S&F can be added to the statistics to continuously improve the estimation. Any estimation technique should remove outliers before deriving an approximation; ○ After calculating this new T3510 for the S&F scenario, the NAS registration request was rejected by the network with a new reason value: Reason #XX - The S&F timer was updated in the satellite network; After receiving a NAS registration rejection message from the network, the UE retryes the NAS registration process with the network: For any subsequent attempts at NAS registration from any UE, including or excluding the S&F indicator, the satellite gNB can use the new T3510 timer for S&F. This new timer allows sufficient time for the NAS registration process to be completed, even in the case of intermittent gaps in the feeder link connection. Inter-satellite links can be used to share updated and up-to-date T3510 data between satellites. This can be helpful in scenarios where satellite changes occur between a first NAS registration request message and a second NAS registration request message. ○ Using the new T3510 timer, even if the feeder link becomes available at a later time, the satellite gNB can send a NAS registration request to the core network when the core network is available. ○ If a good estimation technique is used to determine the T3510 timer, and more data is used for this purpose, the time required to acquire the feeder link connection can be taken into account, and seamless registration can be provided to all UEs; Similarly, this invention also proposes the calculation of T3517 and other related timers to ensure the completion of the registration and NAS security context establishment process for optimizing the solution; • The calculated timer value can be sent to the UE along with a first rejection message for the associated protocol; • In some embodiments, indicators supported by S&F features may be included in an RRC connection establishment completion message, which includes a NAS registration request message sent from the UE.

[0058] Typically, after a first registration request message is sent by the UE and received by the satellite gNB, the time elapsed until a corresponding response can be sent back to the UE is calculated. The adapted timer value can then be forwarded to the UE. ○ Describes several methods for transmitting new timer values ​​to the UE. In addition, corresponding new "rejection reasons" will be introduced; ○ The timer can be calculated based on the elapsed time between the UE sending a request message and the UE receiving a response message. For example, the timer can be set to x this time. In addition, additional fixed offsets can be added.

[0059] A UE declaration can be added, which shows that the UE will send a registration request message, at some point it will receive a registration rejection response, and (in the rejection message or via another means) can receive a new value for a timer, and then the UE adapts its timer accordingly and uses the adapted timer for any additional registration attempts.

[0060] Some technical details of the exemplary embodiments of the present invention include:

[0061] UE versions 7.1 17 / 18 do not support S&F functionality: When the UE sends an RRC establishment request to the SAT gNB, the SAT gNB checks whether there are any new fields in the message. S&F_ ind The absence of this field indicates that the request originates from an older version of the UE and that the S&F function is not applicable. If the SAT gNB does not have a feeder link connection, the SAT gNB will send an RRC rejection message (if present) with a rejection wait timer set. Therefore, the UE can either wait until this timeout and send an RRC connection establishment message to the same SAT, or it can attempt to contact another satellite. When the UE attempts to contact the same satellite and if the feeder link is unavailable, the same steps will be repeated until an end-to-end connection is available. • Note: If possible, RejectwaitTime can match the time when the feeder link is available, unless it is set to the maximum value.

[0062] Version 7.2.19 of the UE does not support S&F functionality:

[0063] Variant A:

[0064] When the UE sends an RRC establishment request to the SAT gNB, the UE includes a new field in the RRC establishment request message. S& F_ind The indicator is set to 0 or a constant value. Upon receiving this message, if the feeder link is unavailable, the SAT gNB sends an RRC rejection message with redirectedCarrierInfo. Using redirection, the UE can attempt an end-to-end connection to another available, working satellite. The RRC rejection message also includes a wait time set to the expected feeder link availability time. If no other satellite is available, the UE can attempt to connect to the same satellite after this timer expires.

[0065] Variant B:

[0066] The UE and satellite gNB execute the RACH procedure in regeneration mode, and MIB and SIB reception are completed. After the initial RACH procedure, the UE sends an RRC connection establishment request to the satellite gNB. The satellite gNB responds using the RRC connection establishment response. The UE then starts a fixed timer T3510 and sends a NAS registration request in the RRC connection establishment completion message.

[0067] Because the feeder link is unavailable, the SAT gNB will start timer Tx and store the NAS message. When the feeder link becomes available, the SAT gNB will forward the NAS registration request to the AMF. The AMF will start timer T3510 and forward the authentication request to the AUSF in parallel, and receive a response from the AUSF. The feeder link between the SAAT gNB and the terrestrial network is lost.

[0068] AMF will store HXRES And forward the authentication request to the NTN gateway.

[0069] [NTN Gateway Cannot Store Authentication Requests] If the feeder link is available, but authentication requests cannot be stored in the NTN gateway, authentication requests from the network are lost, and timer T3510 expires.

[0070] [NTN Gateway Can Store Authentication Requests] The NTN gateway stores the authentication request content and messages received from the AUSF. After the feeder link becomes available, the authentication request is sent to the SAT gNB. Timer Tx is now stopped. The SAT gNB reports the timer Tx value to the serving AMF and sends it to the AUSF. The AUSF then calculates a new timer value for T3510 for the Store & Forward NTN use case. This timer value is dynamically calculated for the mobile devices in the area. The timer expires before the authentication request arrives due to the latency inherent in the Store & Forward function.

[0071] After the authentication request is received, the NAS module will stop timer T3510. Timer T3510 will be started on the second attempt to request NAS registration (attempt 2). If timer Tx does not stop prematurely due to the loss of the authentication request at the NTN gateway, then the previously started timer Tx will be stopped.

[0072] The SAT gNB will report the timer value to the Serving AMF, and the timer value will be transmitted to the AUSF for use in calculating the T3510 for NTN satellite storage and forwarding.

[0073] The feeder link is unavailable, and the SAT gNB starts timer Tx. After the feeder link becomes available, a NAS registration request (attempt 2) is sent to the AUSF. The NAS registration request is rejected by the NTN with a new reason value S&F, and calculated T3510 and T3511 are sent to the UE via the SAT gNB.

[0074] In the future, the satellite will have known the discontinuous timer values ​​serving the UE. Therefore, the AMF will use these values ​​to configure each UE, and this feedback mechanism helps the network configure all UEs with the correct timer values. Thus, there will be no static T3510 and T3511 timers; instead, they will be dynamically updated by the network from time to time based on the satellite on which the UE resides.

[0075] Figure 2 A flowchart illustrating the operation according to an example embodiment of the present invention is shown.

[0076] Figure 2 This illustrates the communication between the UE, satellite gNB (regenerative mode), NTN gateway, AMF (serving network), and core network (home network). These devices can communicate with... Figure 3 The devices shown are associated with this.

[0077] like Figure 2 As shown in step 201, the RACH transmission process, BCH, and MIB+SIB reception between the UE and the satellite gNB are completed. Figure 2 As shown in step 202, an RRC connection establishment request is transmitted between the UE and the satellite gNB. Figure 2 As shown in step 203, an RRC connection establishment response is transmitted between the UE and the satellite gNB. For example... Figure 2 As shown in step 204, the RRC establishment completion and NAS registration request are transmitted between the UE and the satellite gNB. Then, as... Figure 2 As shown in step 205, timer T3510 is started at the UE. Figure 2As shown in step 206, an indication that the feeder link is unavailable is transmitted between the satellite gNB and the NTN gateway. Figure 2 As shown in step 207, timer Tx is started at the satellite gNB and NAS RR is stored. Figure 2 As shown in step 208, an indication that the feeder link is unavailable is transmitted between the satellite gNB and the NTN gateway. Figure 2 As shown in step 209, a NAS registration request is transmitted between the satellite gNB and the NTN gateway. Figure 2 As shown in step 210, a NAS registration request is transmitted between the NTN gateway and the AMF. Figure 2 As shown in step 211, timer T3510 is started at AMF. Figure 2 As shown in step 212, an authentication request is transmitted between the AMF and the core network. Figure 2 As shown in step 213, an authentication response is transmitted between the core network and the AMF. Figure 2 As shown in step 214, HXRES is stored at AMF. .like Figure 2 As shown in step 215, an indication that the feeder link is unavailable is transmitted between the satellite gNB and the NTN gateway. Figure 2 As shown in step 216, the authentication request is transmitted between the AMF and the NTN gateway. As shown in step 217, the NTN gateway is able to store the authentication request. Figure 2 As shown in step 218, the authentication request is stored at the NTN gateway. Figure 2 As shown in step 219, an indication of feeder link availability is transmitted between the satellite gNB and the NTN gateway. Figure 2 As shown in step 220, an authentication request is transmitted between the NTN gateway and the satellite gNB. Figure 2 As shown in step 221, timer Tx is stopped at satellite gNB. Figure 2 As shown in step 222, timer T3510 at the UE expires. Figure 2 As shown in steps 223 and 225, a report of the timer Tx value is transmitted between the satellite gNB and the NTN gateway to the serving AMF. Figure 2 As shown in step 226, the T3510 timer for the S&F NTN is calculated at the AMF. Figure 2 As shown in step 224, an authentication request is transmitted between the satellite gNB and the UE. Figure 2 As shown in step 227, the T3510 timer at the UE expires. Figure 2 As shown in step 228, the feeder link between the satellite gNB and the NTN gateway is available and the authentication request is lost. Figure 2As shown in step 229, the NAS registration process is aborted at the UE and timer T3511 is started. Figure 2 As shown in step 230, timer T3511 expires. Figure 2 As shown in step 231, the RRC connection establishment completion is transmitted between the UE and the satellite gNB. NAS registration request (attempt 2). For example... Figure 2 As shown in step 232, timer T350 is started at the UE. Figure 2 As shown in step 233, based on the fact that the timer did not stop prematurely due to the loss of the authentication request at the NTN gateway, communication is established between the satellite gNB, the NTN gateway, and the AMF to stop the previously started timer Tx at the satellite gNB, report the timer Tx value used to serve the AMF between the satellite gNB, the NTN gateway, and the AMF, and calculate the T3510 timer at the AMF for the S&F NTN. Figure 2 As shown in step 234, the feeder link between the satellite gNB and the NTN gateway is unavailable. Figure 2 As shown in step 235, timer Tx is started at the satellite gNB and NAS RR is stored. Figure 2 As shown in step 236, the feeder link between the satellite gNB and the NTN gateway is available. Figure 2 As shown in steps 237 and 238, a NAS registration request is transmitted between the satellite gNB, the NTN gateway, and the AMF (attempt 2). Then, as... Figure 2 As shown in steps 239, 240 and 241, registration rejection, reason #XX S&F NTN, and the calculated T3510 and T3511 values ​​are transmitted between the AMF, NTN gateway and satellite gNB NAS.

[0078] Enhancements according to exemplary embodiments of the present invention may include: a. Transmit a new rejection reason for satellite access (S&F) scenarios. Include this clause number in the following statement: "If the UE receives a REGISTRATION REJECT or SERVICE REJECT message with 5GMM reason values ​​#3, #6, #7, #12, #13, #15, #27, #72, #74, or #75 without integrity protection before the network has established a secure exchange of NAS messages for an N1 NAS signaling connection, the UE shall stop timer T3510 or T3517 (if it is running)." b. Transmit new steps for calculating NAS timers T3510 and T3517. RRCReject ::= SEQUENCE { criticalExtensions CHOICE { rrcReject RRCReject-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCReject-IEs ::= SEQUENCE { waitTime RejectWaitTime OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL, redirectedCarrierInfo RedirectedCarrierInfoOPTIONAL } RedirectedCarrierInfo ::= CHOICE { nr CarrierInfoNR, eutra RedirectedCarrierInfo-EUTRA, sat RedirectedCarrierInfo-SAT ... } RedirectedCarrierInfo-EUTRA ::= SEQUENCE { eutraFrequency ARFCN-ValueEUTRA, cnType ENUMERATED {epc,fiveGC} OPTIONAL -- Need N } RedirectedCarrierInfo-SAT ::= SEQUENCE { ntn-Config NTN-Config,OPTIONAL SatCarrierFrequency ARFCN-ValueSAT,OPTIONAL physcellId PhysCellIdOPTIONAL}

[0079] 7.3 For version 19, UEs that support S&F functionality: When the UE sends an RRC establishment request to the SAT gNB, the UE includes a new field in the RRC establishment request message. S&F_ind The indicator is set to 1 or some other constant value. The SAT gNB sends an RRC establishment message with the expected feeder link availability time. Therefore, the UE will not send the NAS payload during RRC establishment completion. After the feeder link becomes available (UE timer times out), the NAS payload is sent to the same SAT gNB.

[0080] Alternatively, the establishment terms in the RRC establishment request message may include store-and-forward data as one of the reasons for establishment. Changes in TS 38.331: RRCSetupRequest ::= SEQUENCE { rrcSetupRequest RRCSetupRequest-IEs } RRCSetupRequest-IEs ::= SEQUENCE { ue-Identity InitialUE-Identity, establishmentCause EstablishmentCause, spare bit string (size (1)) } InitialUE-Identity ::= CHOICE { ng-5G-S-TMSI-Part1 BIT STRING (SIZE (39)), randomValue BIT STRING (SIZE (39)) } EstablishmentCause ::= ENUMERATED { emergency, highPriorityAccess, mt-Access, mo-Signalling,mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess,Store-And-Forward-Data, spare5, spare4, spare3, spare2, spare1}.

[0081] Figure 4 A method that can be performed by an apparatus according to an example embodiment of the present invention is shown.

[0082] Figure 4 The diagram illustrates operations that can be performed by a device, such as, but not limited to, a network node (e.g., ...). Figure 3 UE 10, NN 12 and / or NN 13 in the example. Figure 4 As shown in box 405, first information, including a radio resource control establishment request, is transmitted from the user equipment to a network node in the non-terrestrial network. Figure 4 As shown in box 410, based on this transmission, at least one timer is initiated based on at least one of the following: a radio resource control establishment request, a response to a first message from a non-terrestrial network, or the creation of a radio resource control connection. Figure 4 As shown in box 415, an indication of transmitting a first radio resource control rejection message between the network node and the user equipment is based on at least one timer expiring due to feeder link unavailability. Then, as... Figure 4 As shown in box 420, based on the first radio resource control rejection message, another radio resource control establishment request is transmitted to another network node in the non-terrestrial network.

[0083] According to the example embodiments described in the preceding paragraphs, the transmission of information including a radio resource control establishment request is based on the transmission of an initial random access channel procedure with network nodes of a non-terrestrial network; and based on the initial random access channel procedure, the transmission of a radio resource control establishment request and store-and-forward availability with network nodes is also based on the transmission of a radio resource control establishment request and store-and-forward availability.

[0084] According to the example embodiment described in the preceding paragraphs, the first radio resource control rejection message includes redirected carrier information; and based on the redirected carrier information, another radio resource control establishment request is transmitted to another network node of the non-terrestrial network.

[0085] According to the example embodiment described in the preceding paragraphs, the redirected carrier information includes an indication of a waiting time, for which the feeder link can be used to communicate with another network node.

[0086] According to the example embodiments described in the above paragraphs, at least one timer is updated in a non-terrestrial network based on redirected carrier information.

[0087] According to the example embodiments described in the above paragraphs, at least one timer is dynamically updated for each user equipment in the user equipment.

[0088] According to the example embodiment described in the above paragraphs, at least one timer uses network attachment to store the total time spent and an offset of five times the total time.

[0089] According to the example embodiment described in the above paragraphs, the total time uses the time spent by the network attached storage registration request from the network node to the non-terrestrial network, wherein the total time takes into account four message exchanges between core network functions and one message exchange between the random access network and the core network function, and wherein it is assumed that each message exchange will take the same amount of time.

[0090] According to the example embodiments described in the above paragraphs, the timer is one of a network-attached store-and-wait type timer or a store-and-forward type timer.

[0091] According to the example embodiments described in the preceding paragraphs, the network attached storage wait-type timer allows for the time during which a network attached storage registration request is made between the user equipment and the network node.

[0092] According to the example embodiments described in the above paragraphs, the store-and-forward type timer allows sufficient time for the network attachment store registration process to be completed during intermittent gaps in the feeder link connection.

[0093] According to the example embodiments described in the above paragraphs, the network attached store wait type timer uses store and forward values ​​to obtain a statistical approximation of the expected network attached store timer for store and forward functions.

[0094] According to the example embodiments described in the preceding paragraphs, additional offsets or buffers are added to a previous network-attached store-wait type timer used for storing and forwarding values ​​to create or update a new network-attached store-wait type timer.

[0095] According to the example embodiments described in the preceding paragraphs, a previous network-attached storage wait-type timer for storing and forwarding values ​​is used to obtain a statistical approximation or calculated estimate of the expected network-attached storage timer for the storage and forwarding function, in order to create or update a new network-attached storage wait-type timer.

[0096] According to the example embodiments described in the above paragraphs, the statistical approximation or calculated value estimate is used depending on which has the larger value.

[0097] According to the example embodiment described in the above paragraphs, a new network-attached storage wait type timer is added to the statistics to continuously improve the estimation.

[0098] According to the example embodiments described in the preceding paragraphs, the information included in the Radio Resource Control Establishment Request is one of the use or non-use of the Network Attached Storage Store and Forward Flags.

[0099] According to the example embodiments described in the above paragraphs, where a network-attached storage storage and forwarding flag is used, the user equipment supports storage and forwarding functions.

[0100] According to the example embodiments described in the preceding paragraphs, a network attached storage registration rejection message for a radio resource control establishment request is transmitted between a user equipment and a network node without using a network attached storage storage and forwarding flag, based on information including a radio resource control establishment request; and a new storage and forwarding type timer is created or updated in a non-terrestrial network based on the network attached storage registration rejection message.

[0101] According to the example embodiments described in the preceding paragraphs, another radio resource control establishment request is used between the user equipment and the network node to retry another network attached storage registration process based on a network attached storage registration rejection message.

[0102] According to the example embodiments described in the preceding paragraphs, regardless of whether another radio resource control establishment request includes a network attached storage store and forwarding flag, at least one new timer value for store and forwarding is used between the user equipment and the network node for another network attached storage registration process.

[0103] According to the example embodiment described in the above paragraphs, at least one new timer value is configured to allow sufficient time for the network attachment storage registration process to be completed, taking into account intermittent gaps in the feeder link connection.

[0104] According to the example embodiments described in the above paragraphs, new inter-satellite links are created for sharing updated and up-to-date information between satellites in a non-terrestrial network.

[0105] According to the example embodiments described in the preceding paragraphs, the calculated time value of at least one new timer is transmitted between the user equipment and the network node.

[0106] A stored procedure code (such as) Figure 3Non-transitory computer-readable media (such as PROG 10C and / or PROG 12C and / or PROG 13C) Figure 3 In MEM 10B and / or MEM 12B and / or MEM 13B, the program code is handled by at least one processor (such as...). Figure 3 The DP 10A and / or DP 12A and / or DP 13A in the above section are executed to perform at least the operations described in the paragraphs above.

[0107] According to the exemplary embodiments of the present invention described above, there exists an apparatus comprising: for receiving data from a user equipment (such as...) Figure 3 UE 10 in the middle) to non-terrestrial networks (such as Figure 3 Network nodes in network 1) (such as Figure 3 NN 12 and / or NN 13 in the transmission (e.g. Figure 3 The DP 10A and / or DP 12A and / or DP 13A, PROG 10C and / or PROG 12C and / or PROG 13C, and MEM 10B and / or MEM 12B and / or MEM 13B) include a component containing the first information of a radio resource control establishment request, wherein, based on this transmission, at least one timer is activated based on the radio resource control establishment request, at least one of the following: a response to the first information of a non-terrestrial network or the creation of a radio resource control connection (e.g., Figure 3 Among them, DP10A and / or DP 12A and / or DP 13A, PROG 10C and / or PROG 12C and / or PROG 13C, and MEM 10B and / or MEM 12B and / or MEM 13B), and at least one of the timers is dynamically updated based on at least one of the following: the identifier of the user equipment or the satellite of the non-terrestrial network to which the user equipment is attached (e.g., Figure 3 DP 10A and / or DP12A and / or DP 13A, PROG 10C and / or PROG 12C and / or PROG 13C, and MEM 10B and / or MEM 12B and / or MEM 13B; used for transmitting (e.g., based on at least one timer expiring due to feeder link unavailability) between network nodes and user equipment. Figure 3 The components include: an indication of a first radio resource control rejection message for DP 10A and / or DP 12A and / or DP 13A, PROG 10C and / or PROG 12C and / or PROG 13C, and MEM 10B and / or MEM 12B and / or MEM 13B; and a component for transmitting (e.g.,...) a first radio resource control rejection message to another network node in a non-terrestrial network based on the first radio resource control rejection message. Figure 3The components of DP 10A and / or DP 12A and / or DP 13A, PROG 10C and / or PROG 12C and / or PROG 13C, and MEM10B and / or MEM 12B and / or MEM 13B) are another radio resource control establishment request components.

[0108] According to the example embodiments described in the preceding paragraphs, at least the components used for transmission, initiation, and updating include those encoded with computer programs [such as...]. Figure 3 Non-transitory computer-readable media [such as PROG 10C and / or PROG 12C and / or PROG 13C] Figure 3 [MEM 10B and / or MEM 12B and / or MEM 13B in the above], the computer program is powered by at least one processor [such as MEM 10B and / or MEM 12B and / or MEM 13B in the above], Figure 3 DP 10A and / or DP 12A and / or DP 13A in [the following] are executable.

[0109] The advantages of the exemplary embodiments of the present invention include at least the following: UE power savings and / or UL energy efficiency enhancements, while considering system-level aspects (e.g., interference management); and Potential Tput enhancement and / or latency reduction; Avoid unnecessary optimization work performed by gNBs covering a given geographic area, which has already been done by other gNBs covering the same area in the past; In detail, based on deterministic knowledge of LEO satellite movement, each gNB (first gNB) that makes changes to the location-based HO configuration compared to the previous or default configuration can share those changes with other gNBs (second gNBs), which can later cover the same area compared to the first gNB. The second gNBs will not need to repeat the optimization work performed by the first gNB. The other gNBs (second gNBs) can then continue optimizing the location-based CHO, and if another change to the location-based CHO configuration is discovered, the entire change is shared with another gNB (third gNB), which can later handle the same geographic area compared to the second gNB. The third gNB can avoid the optimization work performed by the first and second gNBs. Finally, the Nth gNB that receives the configuration change from the (N-1)th gNB will not have to repeat the optimization work performed by the previous N-1 gNBs that processed the same area in the past.

[0110] Note that computer-implemented inventions (CIIs) can be claimed as device claims, method claims, and software claims. In some jurisdictions, such as Europe, signal claims may also be filed. In the United States, software claims must be claimed as non-transitory computer program products or non-transitory computer-readable media.

[0111] As used herein, the term “non-transient” refers to the limitations of the medium itself (i.e., tangible, not signaling), rather than the limitations of data storage persistence (e.g., RAM vs. ROM).

[0112] In other jurisdictions, software claims may be claimed as computer programs, data structures, and / or computer-readable media.

[0113] Furthermore, according to exemplary embodiments of the present invention, there exists a circuit system for performing operations according to exemplary embodiments of the invention disclosed herein. This circuit system may include any type of circuit system, including content encoding circuit systems, content decoding circuit systems, processing circuit systems, image generation circuit systems, data analysis circuit systems, etc. Furthermore, this circuit system may include discrete circuit systems, application-specific integrated circuits (ASICs) and / or field-programmable gate arrays (FPGAs), etc., as well as processors specifically configured by software to perform corresponding functions, or dual-core processors having software and corresponding digital signal processors, etc. Additionally, necessary inputs to and outputs from the circuit system, functions performed by the circuit system, and interconnections between the circuit system and other components that may include other circuit systems (which may be via inputs and outputs) are provided to perform exemplary embodiments of the invention as described herein.

[0114] According to the exemplary embodiments of the present invention disclosed in this application, the provided "circuit system" may include at least one or more or all of the following: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuit systems only); (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits with software / firmware; and (ii) Any portion of a hardware processor(s) having software (including (a plurality of) digital signal processors), software, and (a plurality of) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions, such as the functions or operations of exemplary embodiments of the invention disclosed herein; and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or parts thereof, which require software (e.g., firmware) for operation, but may be absent when software is not required for operation.

[0115] According to exemplary embodiments of the present invention, there exists a suitable circuit system for at least performing novel operations. According to exemplary embodiments of the invention disclosed in this application, the "circuit system" as used herein refers to at least the following: (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuit systems); and (b) A combination of circuitry and software (and / or firmware), such as (where applicable): (i) a combination of (multiple) processors or (ii) portions of (multiple) processors / software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions; and (c) Circuits that require software or firmware to operate (even if the software or firmware does not actually exist), such as (multiple) microprocessors or a portion thereof.

[0116] This definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term "circuit system" will also cover only the implementation of a processor (or processors) or a portion of a processor and its accompanying software and / or firmware. For example, and if applicable to a particular claim element, the term "circuit system" will also cover baseband integrated circuits or application processor integrated circuits for mobile phones, or similar integrated circuits in servers, cellular network devices, or other network devices.

[0117] Generally, various embodiments can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while others may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although the invention is not limited thereto. While various aspects of the invention may be shown and described as block diagrams, flowcharts, or using some other graphical representation, it is well understood that, by way of non-limiting example, these blocks, apparatuses, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0118] Embodiments of the present invention can be practiced in various components such as integrated circuit modules. The design of integrated circuits is largely a highly automated process. Complex and powerful software tools can be used to transform logic-level designs into semiconductor circuit designs ready for etching and formation on semiconductor substrates.

[0119] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. All embodiments described in this detailed description are exemplary embodiments, provided to enable those skilled in the art to make or use the invention, and not to limit the scope of the invention as defined by the claims.

[0120] The foregoing description has provided a complete and informative description of the best methods and apparatus currently contemplated by the inventors for carrying out the invention, by way of exemplary and non-limiting examples. However, various modifications and adaptations will be apparent to those skilled in the art when read in conjunction with the accompanying drawings and appended claims, given the foregoing description. Nevertheless, all such and similar modifications to the teachings of exemplary embodiments of the invention will still fall within the scope of the invention.

[0121] It should be noted that the terms “connection,” “coupling,” or any variation thereof mean any direct or indirect connection or coupling between two or more elements, and may encompass the presence of one or more intermediate elements between two elements that are “connected” or “coupled” together. The coupling or connection between elements can be physical, logical, or a combination thereof. As adopted herein, two elements may be considered to be “connected” or “coupled” together by means of one or more wires, cables, and / or printed electrical connections, and by means of electromagnetic energy, such as electromagnetic energy having wavelengths in the radio frequency region, microwave region, and optical (visible and invisible) region, as several non-limiting and non-exhaustive examples.

[0122] Furthermore, some features of the preferred embodiments of the invention can be used advantageously without the need for corresponding use of other features. Therefore, the foregoing description should be considered merely as an illustration of the principles of the invention, and not as a limitation thereof.

Claims

1. An apparatus comprising: At least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the means to at least: The first message, including a radio resource control establishment request, is transmitted from the user equipment to the network node of the non-terrestrial network. Based on the transmission, at least one timer is started based on the radio resource control establishment request, at least one of the following: a response to the first information of the non-terrestrial network, or the creation of a radio resource control connection. The at least one timer is dynamically updated based on at least one of the following: the identifier of the user equipment or a satellite of the non-terrestrial network to which the user equipment is attached; Indication for transmitting a first radio resource control rejection message between the network node and the user equipment based on the expiration of the at least one timer due to the unavailability of the feeder link; as well as Based on the first radio resource control rejection message, another radio resource control establishment request is transmitted with another network node of the non-terrestrial network.

2. The apparatus of claim 1, wherein the transmission of the information including the radio resource control establishment request is based on: The at least one memory stores instructions, which, when executed by the at least one processor, cause the device to at least: The network nodes of the non-terrestrial network transmit the initial random access channel procedure; and Based on the initial random access channel procedure, the radio resource control establishment request and store-and-forward availability are transmitted to the network node.

3. The apparatus of claim 1, wherein the first radio resource control rejection message includes redirection carrier information; and wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the apparatus to at least: Based on the redirected carrier information, another radio resource control establishment request is transmitted to another network node of the non-terrestrial network.

4. The apparatus of claim 3, wherein the redirected carrier information includes an indication of a waiting time, for which the feeder link can be used to communicate with the other network node.

5. The apparatus of claim 4, wherein the at least one timer is updated in the non-terrestrial network based on the redirected carrier information.

6. The apparatus of claim 5, wherein the at least one timer is dynamically updated for each of the user equipments.

7. The apparatus of claim 1, wherein the at least one timer uses a network attachment to store the total time spent and an offset of five times the total time.

8. The apparatus of claim 7, wherein the total time uses the time spent by the network attachment storage registration request from the network node to the non-terrestrial network, wherein the total time takes into account four message exchanges between core network functions and one message exchange between the random access network and the core network function, and wherein it is assumed that each message exchange will take the same amount of time.

9. The apparatus of claim 1, wherein the timer is one of a network-attached store-and-wait type timer or a store-and-forward type timer.

10. The apparatus of claim 9, wherein the network attached storage wait-type timer allows for the time during which the network attached storage registration request is made between the user equipment and the network node.

11. The apparatus of claim 9, wherein the store-and-forward type timer allows sufficient time for the network attachment store registration process to be completed during intermittent gaps in the feeder link connection.

12. The apparatus of claim 9, wherein the network attached store wait type timer uses store and forward values ​​to obtain a statistical approximation of the expected network attached store timer for store and forward function.

13. The apparatus of claim 9, wherein the at least one memory stores instructions, which, when executed by the at least one processor, cause the apparatus to at least: Add additional offsets or buffers to the previous network-attached store-wait type timer used for storing and forwarding values ​​to create or update a new network-attached store-wait type timer.

14. The apparatus of claim 13, wherein the previous network-attached store-wait type timer for storing and forwarding values ​​is used to obtain a statistical approximation or calculated estimate of the expected network-attached store timer for store-and-forward functionality, for creating or updating the new network-attached store-wait type timer.

15. The apparatus of claim 14, wherein the statistical approximation or the calculated value estimate is used depending on which has the larger value.

16. The apparatus of claim 14, wherein the new network-attached storage wait type timer is added to the statistics to continuously improve the estimation.

17. The apparatus of claim 1, wherein the information of the radio resource control establishment request is using a network attachment store-and-forward flag, and wherein the user equipment supports store-and-forward functionality based on the use of the network attachment store-and-forward flag.

18. The apparatus of claim 17, wherein the at least one memory stores instructions, which, when executed by the at least one processor, cause the apparatus to at least: Based on the information including the Radio Resource Control Establishment Request, the network attachment storage registration rejection message for the Radio Resource Control Establishment Request is transmitted between the user equipment and the network node without using the network attachment storage storage and forwarding flag; and Based on the network attached storage registration rejection message, a new store and forwarding type timer is created or updated in the non-terrestrial network.

19. The apparatus of claim 18, wherein the at least one memory stores instructions, which, when executed by the at least one processor, cause the apparatus to at least: Based on the network attached storage registration rejection message, another network attached storage registration process is retried between the user equipment and the network node using another radio resource control establishment request.

20. The apparatus of claim 19, wherein, regardless of whether the other radio resource control establishment request includes a network attached storage store and forwarding flag, at least one new timer value for store and forward is used between the user equipment and the network node for the other network attached storage registration process.

21. The apparatus of claim 20, wherein the new at least one timer value is configured to allow sufficient time for the network attachment storage registration process to be completed, taking into account intermittent gaps in the feeder link connection.

22. The apparatus of claim 20, wherein the at least one memory stores instructions, which, when executed by the at least one processor, cause the apparatus to at least: Create new inter-satellite links to share updated and up-to-date information among satellites in the non-terrestrial network.

23. The apparatus of claim 1, wherein the at least one memory stores instructions, which, when executed by the at least one processor, cause the apparatus to at least: The calculated time value of the new at least one timer is transmitted between the user equipment and the network node.

24. A method comprising: The first message, including a radio resource control establishment request, is transmitted from the user equipment to the network node of the non-terrestrial network. Based on the transmission, at least one timer is started based on the radio resource control establishment request, at least one of the following: a response to the first information of the non-terrestrial network, or the creation of a radio resource control connection. The at least one timer is dynamically updated based on at least one of the following: the identifier of the user equipment or a satellite of the non-terrestrial network to which the user equipment is attached; Indication for transmitting a first radio resource control rejection message between the network node and the user equipment based on the expiration of the at least one timer due to the unavailability of the feeder link; as well as Based on the first radio resource control rejection message, another radio resource control establishment request is transmitted with another network node of the non-terrestrial network.

Images