Methods to optimize NAS registration procedure with store and forward operations in non-terrestrial networks

Abstract

In accordance with example embodiments of the invention there is at least a method an apparatus to perform communicating from user equipment to a network node of a non- terrestrial network first information comprising a radio resource control setup request, wherein based on the communicating, at least one timer is started based on the radio resource control setup request for at least one of a response to the non-terrestrial network first information or creation of a radio resource control connection, and wherein the at least one timer is dynamically updated at least based on at least one of an identity of the user equipment or on a satellite of the non-terrestrial network that the user equipment is attached; based on expiration of the at least one timer for a feeder link not being available, communicating between the network node and the user equipment an indication of a first radio resource control reject message; and based on the first radio resource control reject message, communicating another radio resource control setup request with another network node of the non-terrestrial network.

Description

METHODS TO OPTIMIZE NAS REGISTRATION PROCEDURE WITH STORE AND FORWARD OPERATIONS IN NON-TERRESTRIAL NETWORKSTECHNICAL FIELD

[0001] The teachings in accordance with the exemplary embodiments of this invention relate generally to a first NAS registration request message sent by a UE and received by the satellite gNB using at least one timer, and more specifically relates to a first NAS registration request message sent by a UE and received by the satellite gNB using at least one timer where if the timer elapses a respective response can be calculated and transmitted back to the UE for NAS registration.BACKGROUND:

[0002] This section is intended to provide a background or context to the invention that is recited in the claims. The description herein may include concepts that could be pursued, but are not necessarily ones that have been previously conceived or pursued. Therefore, unless otherwise indicated herein, what is described in this section is not prior art to the description and claims in this application and is not admitted to be prior art by inclusion in this section.

[0003] Certain abbreviations that may be found in the description and / or in the Figures are herewith defined as follows:3 GPP 3rdgeneration partnership programAI / ML artificial intelligence machine learning AMF access and mobility management functionAUSF authentication server functionNAS non-access stratumNTN non-terrestrial networkRAN radio access networkRAT radio Access technologyRRC radio resource controlS&F store and forwardSAT satelliteUE user equipment

[0004] For 5GS mobility management via a satellite NG-RAN cell the UE shall apply the value of the applicable NAS timer indicated in table from TS 24.501 clause 10.2.1 for access via a satellite NG-RAN cell.

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

[0006] Example embodiments of this invention proposes improved at least mobility optimizations for NTN.SUMMARY:

[0007] This section contains examples of possible implementations and is not meant to be limiting.

[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 at least to: communicate from user equipment to a network node of a non-terrestrial network first information comprising a radio resource control setup request, wherein based on the communicating, at least one timer is started based on the radio resource control setup request for at least one of a response to the non-terrestrial network first information or creation of a radio resource control connection, and wherein the at least one timer is dynamically updated at least based on at least one of an identity of the user equipment or on a satellite of the nonterrestrial network that the user equipment is attached; based on expiration of the at least one timer for a feeder link not being available, communicate between the network node and the user equipment an indication of a first radio resource control reject message; and based on the first radio resource control reject message, communicate another radio resource control setup request with another network node of the non-terrestrial network.

[0009] In still another example aspect of the invention, there is a method, comprising: communicating from user equipment to a network node of a non-terrestrial network first information comprising a radio resource control setup request, wherein based on the communicating, at least one timer is started based on the radio resource control setup request for at least one of a response to the non-terrestrial network first information or creation of a radio resource control connection, and wherein the at least one timer is dynamically updated at least based on at least one of an identity of the user equipment or on a satellite of the non-terrestrial network that the user equipment is attached; based on expiration of the at least one timer for a feeder link not being available, communicating between the network node and the user equipment an indication of a first radio resource control reject message; and based on the first radio resource control reject message, communicating another radio resource control setup request with another network node of the non-terrestrial network.

[0010] A further example embodiment is an apparatus and a method comprising the apparatus and the method of the previous paragraphs, wherein communicating the information comprising a radio resource control setup request, wherein there is communicating with the network node of the non-terrestrial network an initial random access channel procedure; and based on the initial random access channel procedure, communicating with the network node the radio resource control setup request and a store and forward availability, wherein the first radio resource control reject message comprises redirect carrier information; and wherein there is, based on the redirect carrier information, communicating another radio resource control setup request with another network node of the non-terrestrial network, wherein the redirect carrier information comprises an indication of a wait time for which a feeder link is available for communicating with the another network node, wherein based on the redirect carrier information the at least one timer is updated in the non-terrestrial network, wherein the at least one timer is dynamically updated for each of the user equipment, wherein the at least one timer is using a total time taken from network attached storage and an offset of five times the total time, wherein the total time is using a time taken between network attached storage registration request from the network node to the non-terrestrial network, wherein the total time considers four message exchanges between core network functions and one message between a random access network and acore network function, and wherein it is assumed that each message exchange would take a same 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 time between the user equipment and the network node of the network attached storage registration request, wherein the store and forward type timer allows enough time for network attached storage registration procedure to be completed with intermittent gaps in feeder link connections, wherein the network attached storage wait type timer uses store and forward values to obtain a statistical approximation of expected network attached storage timer for store and forward functionality, wherein there is adding a further offset or buffer to a prior network attached storage wait type timer for store and forward values to create or update a new network attached storage wait type timer, wherein the prior network attached storage wait type timer for store and forward values is used to obtain a statistical approximation or computed value estimates of an expected network attached storage timer for store and forward functionality for use to create or update the new network attached storage wait type timer, wherein the statistical approximation or the computed value estimates are used depending on whichever is having a greater value, wherein the new network attached storage wait type timer is added to statistical data for continuously improving estimates, wherein the information comprising a radio resource control setup request is using a network attached storage store and forward flag, wherein based on the network attached storage store and forward flag being used the user equipment supports store and forward functionality, wherein there is, based on the information comprising the radio resource control setup request not using a network attached storage store and forward flag, communicating a network attached storage registration rejection message for the radio resource control setup request between the user equipment and the network node; and based on the network attached storage registration rejection message creating or updating a new store and forward type timer in the non-terrestrial network, wherein there is, based on the network attached storage registration rejection message, another network attached storage registration procedure is re-attempted using another radio resource control setup request between the user equipment and the network node, wherein whether or not the another radio resource control setup request comprises a network attached storage store and forward flag a new at least one timer value for store and forward is used between the user equipment and the network node for the another network attached storage registration procedure, wherein the new at least one timer value is configured to allow enough time for a network attachedstorage registration procedure to be completed considering intermittent gaps in feeder link connections, wherein there is creating new inter-satellite links for use to share updated and latest between satellites of the non-terrestrial network, and / or wherein there is communicating between the user equipment and the network node computed time values of the new at least one timer.

[0011] A non-transitory computer-readable medium storing program code, the program code executed by at least one processor to perform at least the method as described in the paragraphs above.

[0012] In yet another example aspect of the invention, there is an apparatus comprising: means for communicating from user equipment to a network node of a nonterrestrial network first information comprising a radio resource control setup request, wherein based on the communicating, at least one timer is started based on the radio resource control setup request for at least one of a response to the non-terrestrial network first information or creation of a radio resource control connection, and wherein the at least one timer is dynamically updated at least based on at least one of an identity of the user equipment or on a satellite of the non-terrestrial network that the user equipment is attached; means based on expiration of the at least one timer for a feeder link not being available, for communicating between the network node and the user equipment an indication of a first radio resource control reject message; and means, based on the first radio resource control reject message, for communicating another radio resource control setup request with another network node of the non-terrestrial network.

[0013] A communication system comprising a network side apparatus and a user equipment side apparatus performing operations as described above.BRIEF DESCRIPTION OF THE DRAWINGS:

[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 like reference signs are used to designate like or equivalent elements. The drawings are illustrated for facilitatingbetter understanding of the embodiments of the disclosure and are not necessarily drawn to scale, in which:

[0015] FIG. 1 shows a non-terrestrial network (NTN) Store & Forward (S&F) scenario;

[0016] FIG. 2 shows a flow chart of operations in accordance with example embodiments of the invention;

[0017] FIG. 3 shows a high level block diagram of various devices used in carrying out various aspects of the invention; and

[0018] FIG. 4 shows a method in accordance with example embodiments of the invention which may be performed by an apparatus.DETAILED DESCRIPTION:

[0019] In example embodiments of this invention there is proposed at least a method and apparatus for a first NAS registration request message sent by a UE and received by the satellite gNB using at least one timer where if the timer elapses a respective response can be calculated and transmitted back to the UE for NAS registration.

[0020] 5GS mobility management via a satellite NG-RAN cell

[0021] For 5GS mobility management via a satellite NG-RAN cell the UE shall apply the value of the applicable NAS timer indicated in table from TS 24.501 clause 10.2.1 for access via a satellite NG-RAN cell.

[0022] It is noted that the applied NAS timer values are based on the current satellite NG-RAN access RAT type determined based on information from lower layers.

[0023] The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at startof a NAS procedure, and shall not be re-calculated until the NAS procedure is completed, restarted or aborted.

[0024] The access via a satellite NG-RAN cell by a UE is indicated to the AMF by lower layers and shall be stored by the AMF. When an AMF that supports access via satellite NG-RAN cells performs NAS signalling with a UE via satellite NG-RAN cells, the AMF shall calculate the value of the applicable NAS timer indicated in table from TS 24.501 clause 10.2.2 for access via a satellite NG-RAN cell.

[0025] It is noted that the applied NAS timer values are based on the current satellite NG-RAN access RAT type determined based on information from lower layers.

[0026] The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not be re-calculated until the NAS procedure is completed, restarted or aborted.

[0027] 5GS session management via a satellite NG-RAN cell

[0028] For 5GS session management via a satellite NG-RAN cell the UE shall apply the value of the applicable NAS timer indicated in table from TS 24.501 clause 10.2.1 for access via a satellite NG-RAN cell.

[0029] It is noted that that the applied NAS timer values are based on the current satellite NG-RAN access RAT type determined based on information from lower layers.

[0030] The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure, and shall not be re-calculated until the NAS procedure is completed, restarted or aborted.

[0031] If the use of extended NAS timer for access via a satellite NG-RAN cell is indicated by the AMF (see 3GPP TS 23.501 and 3GPP TS 23.502), the SMF shall calculatethe value of the applicable NAS timer indicated in table from TS 24.501 clause 10.3.2 for access via a satellite NG-RAN cell.

[0032] The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not be re-calculated until the NAS procedure is completed, restarted or aborted.

[0033] In NTN Store & Forward (S&F) scenario, the end-to-end connection from UE to ground network is not available. The feeder link connection may be missing intermittently. Hence, when UE sends NAS registration request to establish secure NAS connection, the registration request may not be responded to the UEs in timely manner. Moreover, it is likely that subsequent packets sent by the UEs are also delayed because of intermittent unavailability of feeder link connection. This would require S&F feature capability at the UEs as well as in the satellite-access network. This S&F feature is introduced in 3GPP Rel-19.

[0034] Some technical problems to solve are based on a satellite connection supported by UE since release 17 / 18. However, S&F functionality of Satellite+gNB will be supported in Rell9. New functionality of Rell9 will be supported by new UEs supporting Rell9.

[0035] However it is noted that:• Store-and-forward operations introduce more latency in the NAS registration procedure. This leads to multiple rounds of failures of NAS registration requests from UEs, and hence, higher energy consumption in UEs;• For loT devices, higher energy consumption can be detrimental and should be addressed by an optimized method for NAS registration procedure with S&F operations. For loT devices, it is very important to ensure longer battery lives. Also, 6G onwards, optimization of energy consumption is one of the very important features, and failures result in only waste of energy used even by the network;This invention focusses on providing optimized methods by updating timers in UEs.

[0036] Example: UE sends a message and waiting for a response within few seconds from gNB. As it is a Store and forwards Sat / gNB, then gNB may not respond within the time duration due to feeder link unavailability. So, UE connection will fail.

[0037] As of now this issue is not addressed in the standards.

[0038] Example embodiments of this invention focus on a solution which has minimal UE impacts to support the S&F feature ensuring optimized energy / battery usage.

[0039] Some main ideas in accordance with example embodiments of the invention to handle include:• Old release UE not supporting S&F : Old release UE are identified by S&T satellite (not having an indicator flag) then S&F rejects the request with appropriate reject timer;• Rell9 UE not supporting Store and forward: Because S&F is an optional functionality, not all UEs will support S&F. In this case S&F Satellite identified those UE by having a flag and then reject the request and ask UE to connect to the other Satellite not having S&F;• Rell9 UE supporting Store and forward: In this case S&F Satellite identifies the UE by having a flag in RRC message and then provide S&F functionality.

[0040] Before describing the example embodiments as disclosed herein in detail, reference is made to FIG. 3 for illustrating a simplified block diagram of various electronic devices that are suitable for use in practicing the example embodiments of the example embodiments of the invention.

[0041] FIG. 3 shows a block diagram of one possible and non-limiting exemplary system in which the example embodiments may be practiced. In FIG. 3, a user equipment (UE) 10 is in wireless communication with a wireless network 1 or network, 1 as in FIG. 3. The wireless network 1 or network 1 as in FIG. 3 can comprise a communication network such as a mobile network e.g., the mobile network 1 or first mobile network as disclosed herein. Any reference herein to a wireless network 1 as in FIG. 3 can be seen as a reference to any wireless network as disclosed herein. Further, the wireless network 1 as in FIG. 3 can also comprises hardwired features as may be required by a communication network. A UE is a wireless, typically mobile device that can access a wireless network. The UE, for example, may be a mobile phone (or called a "cellular" phone) and / or a computer with a mobile terminal function. For example, the UE or mobile terminal may also be a portable, pocket, handheld, computer-embedded or vehicle-mounted mobile device and performs a language signaling and / or data exchange with the RAN.

[0042] The UE 10 includes one or more processors DP 10 A, one or more memories MEM 10B, and one or more transceivers TRANS 10D interconnected through 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, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, and the like. The one or more transceivers TRANS 10D which can be optionally connected to one or more antennas for communication to NN 12 and NN 13, respectively. The one or more memories MEM 10B include computer program code PROG 10C. The UE 10 communicates with NN 12 and / or NN 13 via a wireless link 11 or 16.

[0043] The NN 12 (NR / 5G / 6G Node B, an evolved NB, or LTE device) is a network node such as a master or secondary node base station (e.g., for NR or LTE long term evolution) that communicates with devices such as NN 13 and UE 10 of FIG. 3. The NN 12 provides access to wireless devices such as the UE 10 to the wireless network 1. The NN 12 includes one or more processors DP 12A, one or more memories MEM 12B, and one or more transceivers TRANS 12D interconnected through one or more buses. In accordance with the example embodiments these TRANS 12D can include X2 and / or Xn interfaces for use to perform the example embodiments. Each of the one or more transceivers TRANS 12Dincludes a receiver and a transmitter. The one or more transceivers TRANS 12D can be optionally connected to one or more antennas for communication over at least link 11 with the UE 10. The one or more memories MEM 12B and the computer program code PROG 12C are configured to cause, with the one or more processors DP 12 A, the NN 12 to perform one or more of the operations as described herein. The NN 12 may communicate with another gNB or eNB, or a device such as the NN 13 such as via link 16 or link 18. Further, the link 11, link 16 and / or any other link may be wired or wireless or both and may implement, e.g., an X2 or Xn interface. Further the link 11 and / or link 16 and / or link 18 may be through other network devices such as, but not limited to an NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 device as in FIG. 3. The NN 12 may perform functionalities of an MME (Mobility Management Entity) or SGW (Serving Gateway), such as a User Plane Functionality, and / or an Access Management functionality for LTE and similar functionality for 5G or 6G.

[0044] The NN 13 can be for WiFi or Bluetooth or other wireless device associated with a mobility function device such as an AMF or SMF, further the NN 13 may comprise a NR / 5G / 6G Node B or possibly an evolved NB a base station such as a master or secondary node base station (e.g., for NR or LTE long term evolution) that communicates with devices such as the NN 12 and / or UE 10 and / or the wireless network 1. The NN 13 includes one or more processors DP 13 A, one or more memories MEM 13B, one or more network interfaces, and one or more transceivers TRANS 13D interconnected through one or more buses. In accordance with the example embodiments these network interfaces of NN 13 can include X2 and / or Xn interfaces for use to perform the example embodiments. Each of the one or more transceivers TRANS 13D includes a receiver and a transmitter that can optionally be connected to one or more antennas. The one or more memories MEM 13B include computer program code PROG 13C. For instance, the one or more memories MEM 13B and the computer program code PROG 13C are configured to cause, with the one or more processors DP 13 A, the NN 13 to perform one or more of the operations as described herein. The NN 13 may communicate with another mobility function device and / or eNB such as the NN 12 and the UE 10 or any other device using, e.g., link 11 or link 16 or link 18 or another link. The link 16 or link 18 as shown in FIG. 3 can be used for communication with the NN12. These links maybe wired or wireless or both and may implement, e.g., an X2 or Xn interface. Further, as stated above the link 11 and / or link 16 and / or link 18 may be through othernetwork devices such as, but not limited to an NCE / MME / SGW device such as the NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 of FIG. 3.

[0045] The one or more buses of the device of FIG. 3 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, wireless channels, and the like. For example, the one or more transceivers TRANS 12D, TRANS 13D and / or TRANS 10D may be implemented as a remote radio head (RRH), with the other elements of the NN 12 being physically in a different location from the RRH, and these devices can include one or more buses that could be implemented in part as fiber optic cable to connect the other elements of the NN 12 to a RRH.

[0046] It is noted that although FIG. 3 shows a network nodes such as NN 12 and NN 13, any of these nodes may can incorporate or be incorporated into an eNodeB or eNB or gNB such as for LTE and NR, and would still be configurable to perform example embodiments.

[0047] Also it is noted that description herein indicates that “cells” perform functions, but it should be clear that the gNB that forms the cell and / or a user equipment and / or mobility management function device that will perform the functions. In addition, the cell makes up part of a gNB, and there can be multiple cells per gNB.

[0048] The wireless network 1 or any network it can represent may or may not include a NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 that may include (NCE) network control element functionality, MME (Mobility Management Entity ) / SGW (Serving Gateway) functionality, and / or serving gateway (SGW), and / or MME (Mobility Management Entity) and / or SGW (Serving Gateway) functionality, and / or user data management functionality (UDM), and / or PCF (Policy Control) functionality, and / or Access and Mobility Management Function (AMF) functionality, and / or Session Management (SMF) functionality, and / or Location Management Function (LMF), and / or Authentication Server (AUSF) functionality and which provides connectivity with a further network, such as a telephone network and / or a data communications network (e.g., the Internet), and which is configured to perform any 5G, 6G, and / or NR operations in addition to or instead of otherstandard operations at the time of this application. The NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 is configurable to perform operations in accordance with example embodiments in any of an LTE, NR, 5G, 6G, and / or any standards based communication technologies being performed or discussed at the time of this application. In addition, it is noted that the operations in accordance with example embodiments, as performed by the NN 12 and / or NN 13, may also be performed at the NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14.

[0049] The 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 (N / W I / F(s)), interconnected through one or more buses coupled with the link 13 and / or link 16 and / or link 18. In accordance with the example embodiments these network interfaces can include X2 and / or Xn interfaces for use to perform the example embodiments. The one or more memories MEM 14B include computer program code PROG 14C. The one or more memories MEM14B and the computer program code PROG 14C are configured to, with the one or more processors DP 14A, cause the NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 to perform one or more operations which may be needed to support the operations in accordance with the example embodiments.

[0050] It is noted that that the NN 12 and / or NN 13 and / or UE 10 can be configured (e.g. based on standards implementations etc.) to perform functionality of a Location Management Function (LMF). The LMF functionality may be embodied in any of these network devices or other devices associated with these devices. In addition, an LMF such as the LMF of the MME / SGW / UDM / PCF / AMF / SMF / LMF 14 of FIG. 3, as at least described below, can be co-located with UE 10 such as to be separate from the NN 12 and / or NN 13 of FIG. 3 for performing operations in accordance with example embodiments as disclosed herein.

[0051] The wireless Network 1 may implement network virtualization, which is the process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network. Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is categorized as either external, combining many networks, or parts ofnetworks, into a virtual unit, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities that result from the network virtualization are still implemented, at some level, using hardware such as processors DP 10, DP12A, DP13A, and / or DP14A and memories MEM 10B, MEM 12B, MEM 13B, and / or MEM 14B, and also such virtualized entities create technical effects.

[0052] The computer readable memories MEM 12B, MEM 13B, and MEM 14B may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The computer readable memories MEM 12B, MEM 13B, and MEM 14B may be means for performing storage functions. The processors DP10, DP12A, DP13A, and DP14A may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi-core processor architecture, as non-limiting examples. The processors DP10, DP12A, DP13A, and DP14A may be means for performing functions, such as controlling the UE 10, NN 12, NN 13, and other functions as described herein.

[0053] In general, various embodiments of any of these devices can include, but are not limited to, cellular telephones such as smart phones, tablets, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, image capture devices such as digital cameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback appliances having wireless communication capabilities, Internet appliances permitting wireless Internet access and browsing, tablets with wireless communication capabilities, as well as portable units or terminals that incorporate combinations of such functions.

[0054] Further, the various embodiments of any of these devices can be used with a UE vehicle, a High Altitude Platform Station, or any other such type node associated with a terrestrial network or any drone type radio or a radio in aircraft or other airborne vehicle or a vessel that travels on water such as a boat.

[0055] As similarly stated above, some main ideas in accordance with example embodiments of the invention to handle include:• Old release UE not supporting S&F : Old release UE are identified by S&T satellite (not having an indicator flag) then S&F rejects the request with appropriate reject timer;• Rell9 UE not supporting Store and forward: Because S&F is an optional functionality, not all UEs will support S&F. In this case S&F Satellite identified those UE by having a flag and then reject the request and ask UE to connect to the other Satellite not having S&F;• Rell9 UE supporting Store and forward: In this case S&F Satellite identifies the UE by having a flag in RRC message and then provide S&F functionality.

[0056] Example embodiments of the invention relate to NTN (non-terrestrial networks) with satellite access point, where the “store & forward” (S&F) capability is supported. When S&F is deployed entities may store data and forward the stored data only later on when a link is available. In NTN, the link between UE and satellite, but also between satellite and ground station (feeder link) may only be available at some times. Where for user data, particularly for data relating to e.g. loT devices that only send from time to time some data which is also not requiring real time handling, it is not an issue that data will only be delivered later, this might be an issue for signaling, like e.g. the registration request of a UE. When the UE sends a registration request, the UE will also start a timer to see if the needed responses are received. If no response is received and the timer expires, the procedure is aborted. (And a new registration request may be sent, potentially after some wait time). Obviously, with NTN and S&F the needed response might only be received later - therefore the respective timers needs to be adapted. Whereas this requirement is generally known, example embodiments of the present invention describes a procedure how the timer can, even per UE, be dynamically adapted

[0057] Example embodiments of this invention propose at least the following:• a new indicator field in the RRC SETUP REQUEST message which can be used by the satellite + gNB to check if the UE is supporting Store&Forward functionality, o Absence of this field indicates the message is received from UE which does not support Rel-19 S&F feature;• Computing NAS timers T3510 and T3517 for S&F scenario and updating these in the AMF as well as UE with the first NAS Registration Reject message, o When UE connects with the satellite gNB for the first time, and does not present this new field in RRC SETUP REQUEST, and if the feeder link is not available, the satellite gNB starts computing the NAS timer T3510 for S&F scenario, o This invention proposes that a new NAS timer T3510 is computed for S&F scenario. This can be considered as the total time taken for receiving the first response for NAS registration request from the core network, plus an offset of 5 times this time:■ NAS Timer for S&F = 5 * (Time taken between NAS Registration Request sent from satellite gNB to the core network and the Authentication Request received from the core network),■ This computation considers 4 message exchanges between core network functions and one message between RAN and core network function, and assumes that each message exchange would take the same time; o In some embodiments, a further offset or buffer may be added to the NAS timer computed in above step;o In some other embodiments, the previous “N” NAS timer for S&F values may be maintained to obtain a statistical approximation of expected NAS timer for S&F functionality:■ This statistical estimate OR the computed value may be used depending on whichever is having a greater value,■ Also, every new NAS timer used for S&F can be added to the statistical data for continuously improving estimate,■ Any estimation technique should remove outliers before arriving at an approximate value; o After computing this new T3510 for S&F scenario, the NAS Registration Request is rejected by the network with a new cause value : Cause #XX - S&F timers updated in satellite network;• After receiving the NAS Registration Reject message from the network, the UE reattempts NAS registration procedure with the network: o For any subsequent attempt of NAS registration from any UE which does OR does not include S&F indicator, the new T3510 timer for S&F can be used by the Satellite gNB. This new timer can allow enough time for NAS registration procedure to be completed even with intermittent gaps in feeder link connections, o Inter-Satellite-Links can be used to share the updated and latest T3510 between satellites. This can help in scenarios when between the first and second NAS registration request messages, the serving satellite changes, o Using the new T3510 timer, even if the feeder link is available at a later point in time, the satellite gNB can send the NAS registration request to the core network whenever it is available,o If good estimation techniques are used to determine a T3510 timer, and with more amount of data used for the same, the time required for obtaining feeder link connections can be factored and a seamless registration can be provided to all UEs;• Similarly, this invention also proposes computation of T3517 and other relevant timers to ensure completion of registration and NAS security context establishment procedures for optimized solution;• The computed timer values can be sent to the UE along with the first reject message for the associated protocol;• In some embodiments, the indicator of S&F feature support may be included in RRC Connection Setup Complete message which includes NAS registration request message sent from the UE.

[0058] Generally, after one first registration request message sent by a UE and received by the satellite gNB, the time that elapses until the respective response that can or could really be transmitted back to the UE will be calculated. An adapted timer value may then be forwarded to the UE: o Multiple ways how the new timer value can be transported to the UE are described. Also, a respective new “reject cause” will be introduced; o The timer may be calculated based on the time that will elapse between sending by the UE the request message, and receiving by the UE the response message. For example, the timer may be set as x * this time. Also, an additional fixed offset can be added.

[0059] A UE claims could be added showing that the UE will send the registration request message, that at some point it will receive a registration reject response, and that (in the reject message or via another way) a new value for the timer may be received, and thatsubsequently, the UE adapts its timer accordingly and uses the adapted timer for any further registration attempt.

[0060] Certain technical details in accordance with example embodiments of the invention include:

[0061] 7.1 Rell7 / 18 UEs which are not supporting the S&F functionality:• when UE sends the RRC setup request to SAT gNB, SAT gNB checks if the new field S&F ind is present in the message. The absence of this field indicates the request came from an old release UE and S&F functionality is not applicable. If SAT gNB does not have feeder link connection, the SAT gNB will send RRC reject message with Reject wait timer set (as existing). So UE can either wait till this timeout and send the RRC connection establishment to same SAT or can try to reach out to other Satellites. When UE is trying to reach out same satellite and if the feeder link is not available, same steps will repeat until an end to end connection is available;• Note: The RejectwaitTime could match the time of Feeder link available time if possible other it set to the max value.

[0062] 7.2 Rell9 UEs not supporting S&F functionality:

[0063] Variant A:

[0064] When UE sends the RRC setup request to SAT gNB, the UE includes an indication in RRC setup request message with the new field S&F ind setting as 0 or some constant value. On receiving this, if feeder link is not available, the SAT gNB sends an RRC reject message with redirectedCarrierlnfo. With the redirection, UE can try other normal satellites where end to end connection is available. RRC reject message also includes the wait time which is set to expected feeder link available time. If no other satellites are available, UE can try connecting to the same satellite after this timer expiry.

[0065] Variant B:

[0066] UE and the regenerative mode of the satellite gNB performs the RACH procedure and MIB, SIB reception is complete. After the initial RACH procedure, RRC connection setup request is sent form UE to Satellite gNB. Sat gNB responds with RRC connection setup response. And the UE will start the fixed timer T3510 and sends the NAS registration request in the RRC connection setup complete message.

[0067] As the Feeder link is not available, the SAT gNB will start the timer Tx and stores the NAS message. When the Feeder link is available, the SAT gNB will forward the NAS registration request to the AMF. The AMF will start the timer T3510 and in parallel forward the Authentication request to AUSF and receives the response from AUSF. Feeder link between SAAT gNB and Ground network is lost.

[0068] AMF will store the HXRES* and forwards the authentication request to NTN gateway.

[0069] [NTN Gateway not capable of storing the Authentication Request] If the Feeder link is available but if the authentication request can’t be stored in the NTN gateway then the authentication request from network is lost and timer T3510 expires.

[0070] [NTN Gateway capable of storing the Authentication Request] The NTN gateway will store the authentication request content and message received form the AUSF. Once the Feeder link is available, the authentication request is sent to SAT gNB. Now the timer Tx is stopped. The SAT gNB will report the timer Tx value to serving AMF and the same is sent to AUSF. With this AUSF will compute the new timer value for T3510 for Store and forward NTN use case. This timer value is calculated dynamically for this region of mobiles. Still timer has expired before the Authentication request is reached, because there was a delay in the store and forward functionality.

[0071] Once the Authentication request is received NAS module will stop the timer T3510. Start the timer T3510 with second attempt of NAS registration request (attempt 2).If the timer Tx did not stop earlier because of the reason that Authentication request is lost at NTN gateway. So stop the previously started timer Tx.

[0072] SAT gNB will report the timer value to serving AMF and the same is communicated to the AUSF for the computation of T3510 of Store and forward of NTN satellite.

[0073] Feeder link is not available and SAT gNB will start the timer Tx. Once Feeder link is available, the NAS registration request(attempt 2) is sent to AUSF. NAS registration request is rejected with new cause value of S&F NTN and computed T3510 and T3511 is sent to UE via SAT gNB.

[0074] In future, this Satellite is known for the discontinuity timer value to serve the UEs. So, the AMF will configure each UEs with this value and so such a feedback mechanism of calculation helps the network to configure all UEs with right value of timer values. So will not have static T3510 and T3511 timers instead it is dynamically updated form time to time by network depending upon the satellites the UE camps on.

[0075] FIG. 2 shows a flow chart of operations in accordance with example embodiments of the invention.

[0076] FIG. 2 shows communications between a UE, a satellite gNB (regenerative mode), an NTN gateway, an AMF (serving network), and a core network (home network). These devices can be related to devices as shown in FIG. 3.

[0077] As shown in step 201 of FIG. 2 there is communicated between the UE and the satellite gNB a RACH procedure, BCH, MIB + SIB reception complete. As shown in step 202 of FIG. 2 there is communicated between the UE and the satellite gNB an RRC connection setup request. As shown in step 203 of FIG. 2 there is communicated between the UE and the satellite gNB an RRC connection setup response. As shown in step 204 of FIG. 2 there is communicated between the UE and the satellite gNB an RRC setup complete and a NAS registration request. Then as shown in step 205 of FIG. 2 there is starting a timer T3510 at the UE. As shown in step 206 of FIG. 2 there is communicated between the satellite gNB and the NTN gateway an indication that a feeder link is not available. As shown in step207 of FIG. 2 there is starting a timer Tx and storing NAS RR at the satellite gNB. As shown in step 208 of FIG. 2 there is communicated between the satellite gNB and the NTN gateway an indication that a feeder link is not available. As shown in step 209 of FIG. 2 there is communicated between the satellite gNB and the NTN gateway an NAS registration request. As shown in step 210 of FIG. 2 there is communicated between the NTN gateway and the AMF an NAS registration request. As shown in step 211 of FIG. 2 there is starting a timer T3510 at the AMF. As shown in step 212 of FIG. 2 there is communicated between the AMF and the Core network an authentication request. As shown in step 213 of FIG. 2 there is communicated between the Core network and the AMF an authentication response. As shown in step 214 of FIG. 2 there is storing HXRES* at the AMF. As shown in step 215 of FIG. 2 there is communicated between the satellite gNB and the NTN gateway an indication that a feeder link is not available. As shown in step 216 of FIG. 2 there is communicated between the AMF and the NTN gateway an authentication request. As shown in step 217 is an NTN gateway capable of storing an authentication request. As shown in step 218 of FIG. 2 there is storing an authentication request at the NTN gateway. As shown in step 219 of FIG. 2 there is communicating between the satellite gNB and the NTN gateway an indication that a feeder link is available. As shown in step 220 of FIG. 2 there is communicating between the NTN gateway and the satellite gNB an authentication request. As shown in step 221 of FIG. 2 there is stopping a timer Tx at the satellite gNB. As shown in step 222 of FIG. 2 there is expiration of the timer T3510 at the UE. As shown in steps 223 and 225 of FIG. 2 there is communicating between the satellite gNB and the NTN gateway a report of a timer Tx value to serving AMF. As shown in step 226 of FIG. 2 there is computing at the AMF the T3510 timer for S&F NTN. As shown in step 224 of FIG. 2 there is communicating between the satellite gNB and the UE an authentication request. As shown in step 227 of FIG. 2 there is expiration of T3510 Timer at the UE. As shown in step 228 of FIG. 2 there is communicating between the satellite gNB and the NTN gateway that feeder link is available and authentication request lost. As shown in step 229 of FIG. 2 there is aborting NAS registration procedure and starting Timer T3511 at the UE. As shown in step 230 of FIG. 2 there is expiration of Timer T3511. As shown in step 231 of FIG. 2 there is communicating between the UE and the satellite gNB an RRC connection setup complete and * NAS registration request (attempt 2). As shown in step 232 of FIG. 2 there is starting Timer T350 at the UE. As shown in step 233 of FIG. 2 there is communicating between the satellite gNB, the NTN gateway and the AMF, based on timer does not stopping earlierbecause of authentication request that was lost at NTN gateway, to stop a previously started Timer Tx at the satellite gNB, report between the satellite gNB, the NTN gateway, and the AMF a Timer Tx value for serving AMF, and computing T3510 Timer for S&F NTN at the AMF. As shown in step 234 of FIG. 2 there is communicating between the satellite gNB and the NTN gateway that feeder link is not available. As shown in step 235 of FIG. 2 there is starting Timer Tx and storing NAS RR at the satellite gNB. As shown in step 236 of FIG. 2 there is communicating between the satellite gNB and the NTN gateway that a feeder link is available. As shown in step 237 and step 238 of FIG. 2 there is communicating between the satellite gNB and the NTN gateway and the AMF a NAS registration request (attempt 2). Then as shown in step 239, step 240, and step 241 of FIG. 2 there is communicating between the AMF, the NTN gateway, and the satellite gNB NAS registration reject, cause #XX S&F NTN, computed T3510 and T3511 values.

[0078] Enhancements in accordance with example embodiments of the invention may include: a. Communicating new Reject Cause for Satellite access S&F scenario. And include this clause number in statements like: “If the UE receives a REGISTRATION REJECT or SERVICE REJECT message without integrity protection with 5GMM cause value #3, #6, #7, #12, #13, #15, #27, #72, #74, or #75 before the network has established secure exchange of NAS messages for the N1 NAS signalling connection, the UE shall stop timer T3510 or T3517, if running”; b. Communicating new steps to compute NAS timers T3510 and T3517.RRCReject ::= SEQUENCE { criticalExtensions CHOICE { rrcReject RRCReject-IEs, criticalExtensionsFuture SEQUENCE {} }}RRCReject-IEs ::= SEQUENCE { waitTime Rej ectWai tTime OPTIONAL, - NeedN lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{ } OPTIONAL, redirectedCarrierlnfo RedirectedCarrierlnfo OPTIONAL}RedirectedCarrierlnfo : := CHOICE { nr CarrierlnfoNR, eutra RedirectedCarrierlnfo-EUTRA, sat RedirectedCarrierlnfo-SAT}RedirectedCarrierlnfo-EUTRA ::= SEQUENCE { eutraFrequency ARFCN-ValueEUTRA, cnType ENUMERATED {epc,fiveGC} OPTIONAL -Need N }RedirectedCarrierlnfo-SAT ::= SEQUENCE { ntn-Config NTN-Config, OPTIONALS atCarrierF requency ARF CN -V alue S AT, OPTIONAL physcellld PhysCellld OPTIONAL}

[0079] 7.3 For Rel. 19 UEs supporting S&F functionality:• When UE sends the RRC setup request to SAT gNB, the UE includes an indication in RRC setup request message with the new field S&F ind set as 1 or some different constant value. SAT gNB sends the RRC setup message with expected Feeder link available time. So UE will not send the NAS payload in the RRC setup complete.After the Feeder link is available (UE timer times out), the NAS payload is sent to same SAT gNB.

[0080] Alternatively, Establishment clause in RRC Setup Request message can contain Store and forward Data as one of the establishment cause.TS 38.331 changes: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-Partl BIT STRING (SIZE (39)), random Value BIT STRING (SIZE (39))}Establishmentcause ::= ENUMERATED { emergency, highPriority Access, mt-Access, mo-Signalling,mo-Data, mo-VoiceCall, mo- VideoCall, mo-SMS, mps-Priority Access, mcs-Priority Access, Store- And-Forward-Data, spare5, spared, spare3, spare2, sparel }.

[0081] FIG. 4 shows a method in accordance with example embodiments of the invention which may be performed by an apparatus.

[0082] FIG. 4 illustrates operations which may be performed by a device such as, but not limited to, a device such as a network node (e.g., the UE 10, the NN12 and / or NN13 as in FIG. 3). As shown in block 405 of FIG. 4 there is communicating from user equipment to a network node of a non-terrestrial network first information comprising a radio resourcecontrol setup request. As shown in block 410 of FIG. 4, wherein based on the communicating, at least one timer is started based on the radio resource control setup request for at least one of a response to the non-terrestrial network first information or creation of a radio resource control connection. As shown in block 415 of FIG. 4 there is, based on expiration of the at least one timer for a feeder link not being available, communicating between the network node and the user equipment an indication of a first radio resource control reject message. Then as shown in block 420 of FIG. 4 there is, based on the first radio resource control reject message, communicating another radio resource control setup request with another network node of the non-terrestrial network.

[0083] In accordance with the example embodiments as described in the paragraph above, wherein communicating the information comprising a radio resource control setup request is based on communicating with the network node of the non-terrestrial network an initial random access channel procedure; and based on the initial random access channel procedure, communicating with the network node the radio resource control setup request and a store and forward availability.

[0084] In accordance with the example embodiments as described in the paragraphs above wherein the first radio resource control reject message comprises redirect carrier information; and wherein there is, based on the redirect carrier information, communicate another radio resource control setup request with another network node of the non-terrestrial network.

[0085] In accordance with the example embodiments as described in the paragraphs above, wherein the redirect carrier information comprises an indication of a wait time for which a feeder link is available for communicating with the another network node.

[0086] In accordance with the example embodiments as described in the paragraphs above, wherein based on the redirect carrier information the at least one timer is updated in the non-terrestrial network.

[0087] In accordance with the example embodiments as described in the paragraphs above, wherein the at least one timer is dynamically updated for each of the user equipment.

[0088] In accordance with the example embodiments as described in the paragraphs above, wherein the at least one timer is using a total time taken from network attached storage and an offset of five times the total time.

[0089] In accordance with the example embodiments as described in the paragraphs above, wherein the total time is using a time taken between network attached storage registration request from the network node to the non-terrestrial network, wherein the total time considers four message exchanges between core network functions and one message between a random access network and a core network function, and wherein it is assumed that each message exchange would take a same time.

[0090] In accordance with the example embodiments as described in the paragraphs above, wherein the timer is one of a network attached storage wait type timer or a store and forward type timer.

[0091] In accordance with the example embodiments as described in the paragraphs above, wherein the network attached storage wait type timer allows for time between the user equipment and the network node of the network attached storage registration request.

[0092] In accordance with the example embodiments as described in the paragraphs above, wherein the store and forward type timer allows enough time for network attached storage registration procedure to be completed with intermittent gaps in feeder link connections.

[0093] In accordance with the example embodiments as described in the paragraphs above, wherein the network attached storage wait type timer uses store and forward values to obtain a statistical approximation of expected network attached storage timer for store and forward functionality.

[0094] In accordance with the example embodiments as described in the paragraphs above, wherein there is adding a further offset or buffer to a prior network attached storage wait type timer for store and forward values to create or update a new network attached storage wait type timer.

[0095] In accordance with the example embodiments as described in the paragraphs above, wherein the prior network attached storage wait type timer for store and forwardvalues is used to obtain a statistical approximation or computed value estimates of an expected network attached storage timer for store and forward functionality for use to create or update the new network attached storage wait type timer.

[0096] In accordance with the example embodiments as described in the paragraphs above, wherein the statistical approximation or the computed value estimates are used depending on whichever is having a greater value.

[0097] In accordance with the example embodiments as described in the paragraphs above, wherein the new network attached storage wait type timer is added to statistical data for continuously improving estimates.

[0098] In accordance with the example embodiments as described in the paragraphs above, wherein the information comprising a radio resource control setup request is one of using or not using a network attached storage store and forward flag,

[0099] In accordance with the example embodiments as described in the paragraphs above, wherein based on the network attached storage store and forward flag being used the user equipment supports store and forward functionality.

[0100] In accordance with the example embodiments as described in the paragraphs above, wherein there is, based on the information comprising the radio resource control setup request not using a network attached storage store and forward flag, communicating a network attached storage registration rejection message for the radio resource control setup request between the user equipment and the network node; and based on the network attached storage registration rejection message creating or updating a new store and forward type timer in the non-terrestrial network.

[0101] In accordance with the example embodiments as described in the paragraphs above, wherein there is, based on the network attached storage registration rejection message, another network attached storage registration procedure is re-attempted using another radio resource control setup request between the user equipment and the network node.

[0102] In accordance with the example embodiments as described in the paragraphs above, wherein whether or not the another radio resource control setup request comprises anetwork attached storage store and forward flag a new at least one timer value for store and forward is used between the user equipment and the network node for the another network attached storage registration procedure.

[0103] In accordance with the example embodiments as described in the paragraphs above, wherein the new at least one timer value is configured to allow enough time for a network attached storage registration procedure to be completed considering intermittent gaps in feeder link connections.

[0104] In accordance with the example embodiments as described in the paragraphs above, wherein there is creating new inter-satellite links for use to share updated and latest between satellites of the non-terrestrial network.

[0105] In accordance with the example embodiments as described in the paragraphs above, wherein there is communicating between the user equipment and the network node computed time values of the new at least one timer.

[0106] A non-transitory computer-readable medium (MEM 10B and / or MEM 12B / and / or MEM 13B as in FIG. 3) storing program code (PROG 10C and / or PROG 12C and / or PROG 13C as in FIG. 3), the program code executed by at least one processor (DP 10A and / or DP 12A and / or DP 13 A as in FIG. 3) to perform the operations as at least described in the paragraphs above.

[0107] In accordance with an example embodiment of the invention as described above there is an apparatus comprising: means for communicating (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 as in FIG. 3) from user equipment (UE 10 as in FIG. 3) to a network node (NN 12 and / or NN 13 as in FIG. 3) of a non-terrestrial network (Network 1 as in FIG. 3) first information comprising a radio resource control setup request, wherein based on the communicating, at least one timer is started (DP 10A and / or DP 12A and / or DP 13 A, PROG 10C and / or PROG 12C and / or PROG 13C, and MEM 10B and / or MEM 12B / and / or MEM 13B as in FIG. 3) based on the radio resource control setup request for at least one of a response to the non-terrestrial network first information or creation of a radio resource control connection, and wherein the at least one timer is dynamically updated (DP 10A and / or DP 12A and / or DP 13 A, PROG 10C and / or PROG 12C and / or PROG 13C, and MEM10B and / or MEM 12B / and / or MEM 13B as in FIG. 3) at least based on at least one of an identity of the user equipment or on a satellite of the non-terrestrial network that the user equipment is attached; means, based on expiration of the at least one timer for a feeder link not being available, for communicating (DP 10A and / or DP 12A and / or DP 13 A, PROG IOC and / or PROG 12C and / or PROG 13C, and MEM 10B and / or MEM 12B / and / or MEM 13B as in FIG. 3) between the network node and the user equipment an indication of a first radio resource control reject message; and means, based on the first radio resource control reject message, for communicating (DP 10A and / or DP 12A and / or DP 13 A, PROG IOC and / or PROG 12C and / or PROG 13C, and MEM 10B and / or MEM 12B / and / or MEM 13B as in FIG. 3) another radio resource control setup request with another network node of the nonterrestrial network.

[0108] In accordance with the example embodiments as described in the paragraph above, at least the means for communicating, starting and updating comprises a non- transitory computer readable medium [MEM 10B and / or MEM 12B and / or MEM 13B as in FIG. 3] encoded with a computer program [PROG 10C and / or PROG 12C and / or PROG 13C as in FIG. 3] executable by at least one processor [DP 10A and / or DP 12A and / or DP 13A as in FIG. 3],

[0109] Advantages of example embodiments of the invention at least include:■ UE power saving and / or UL energy efficiency enhancement while considering system level aspects (e.g., interference management); and■ Potential Tput enhancements and / or latency reduction;■ Avoiding unnecessary optimization work to be done by the gNB covering the given geographical area which was already made by other gNBs that covered the same area in the past;■ In details, each gNB (first gNB) which made a change in the configuration of the location based HO compared to previous configuration or default configuration based on deterministic knowledge of movement of the LEO satellite may share thischange to other gNB (2nd gNB) satellites which may cover the same area later compared to first gNB . the 2nd gNB will not have to repeat the optimization work done by 1st gNB. The other gNB (2nd gNB) then may continue in the optimization of the location-based CHO on the top of that and if finds another change in the configuration of location-based CHO share the whole change into another gNB (3rd gNB) which may handle the same geographical area in some later time compared to 2nd gNB. The 3rd gNB may avoid the optimization work done by 1st and 2nd gNB;■ Finally, it may be obtained that N-th gNB which received configuration changes form (N-l) th gNB will not have to repeat the optimization work done by previous N-l gNBs that handled the same area in the past.

[0110] It is noted that computer-implemented inventions (CII) may be claimed as apparatus claims, method claims, and software claims. In some jurisdictions, such as in Europe, signal claims can also be made. In the U.S., a software claim must be claimed as a non-transitory computer program product or a non-transitory computer readable medium.

[0111] The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal ) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0112] In other jurisdictions, a software claim can be claimed as a computer program, a data structure, and / or a computer readable medium.

[0113] Further, in accordance with example embodiments of the invention there is circuitry for performing operations in accordance with example embodiments of the invention as disclosed herein. This circuitry can include any type of circuitry including content coding circuitry, content decoding circuitry, processing circuitry, image generation circuitry, data analysis circuitry, etc.). Further, this circuitry can include discrete circuitry, application-specific integrated circuitry (ASIC), and / or field-programmable gate array circuitry (FPGA), etc. as well as a processor specifically configured by software to perform the respective function, or dual-core processors with software and corresponding digital signal processors, etc.). Additionally, there are provided necessary inputs to andoutputs from the circuitry, the function performed by the circuitry and the interconnection (perhaps via the inputs and outputs) of the circuitry with other components that may include other circuitry in order to perform example embodiments of the invention as described herein.

[0114] In accordance with example embodiments of the invention as disclosed in this application this application, the “circuitry” provided can include at least one or more or all of the following:(a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry);(b) combinations of hardware circuits and software, such as (as applicable):(i) a combination of analog and / or digital hardware circuit(s) with software / firmware; and(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions, such as functions or operations in accordance with example embodiments of the invention as disclosed herein); and(c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.”

[0115] In accordance with example embodiments of the invention, there is adequate circuitry for performing at least novel operations in accordance with example embodiments of the invention as disclosed in this application, this 'circuitry' as may be used herein refers to at least the following:(a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry); and(b) to combinations of circuits and software (and / or firmware), such as (as applicable): (i) to a combination of processor(s) or (ii) to portions of processor(s) / software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions); and(c) to circuits, such as a microprocessor(s) or a portion of a microprocessor s), that require software or firmware for operation, even if the software or firmware is not physically present.

[0116] This definition of ' circuitry' applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term "circuitry" would also cover an implementation of merely a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and / or firmware. The term "circuitry" would also cover, for example and if applicable to the particular claim element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or other network device.

[0117] In general, the various embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may 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 illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0118] Embodiments of the inventions may be practiced in various components such as integrated circuit modules. The design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logiclevel design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

[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 of the embodiments described in this Detailed Description are exemplary embodiments provided to enable persons skilled in the art to make or use the invention and not to limit the scope of the invention which is defined by the claims.

[0120] The foregoing description has provided by way of exemplary and nonlimiting examples a full and informative description of the best method and apparatus presently contemplated by the inventors for carrying out the invention. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of example embodiments of this invention will still fall within the scope of this invention.

[0121] It should be noted that the terms "connected," "coupled," or any variant thereof, mean any connection or coupling, either direct or indirect, 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 the elements can be physical, logical, or a combination thereof. As employed herein two elements may be considered to be "connected" or "coupled" together by the use of one or more wires, cables and / or printed electrical connections, as well as by the use of electromagnetic energy, such as electromagnetic energy having wavelengths in the radio frequency region, the microwave region and the optical (both visible and invisible) region, as several non-limiting and non-exhaustive examples.

[0122] Furthermore, some of the features of the preferred embodiments of this invention could be used to advantage without the corresponding use of other features. As such, the foregoing description should be considered as merely illustrative of the principles of the invention, and not in limitation thereof.

Claims

CLAIMSWhat is claimed is:

1. An 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 at least to: communicate from user equipment to a network node of a non-terrestrial network first information comprising a radio resource control setup request, wherein based on the communicating, at least one timer is started based on the radio resource control setup request for at least one of a response to the non-terrestrial network first information or creation of a radio resource control connection, and wherein the at least one timer is dynamically updated at least based on at least one of an identity of the user equipment or on a satellite of the non-terrestrial network that the user equipment is attached; based on expiration of the at least one timer for a feeder link not being available, communicate between the network node and the user equipment an indication of a first radio resource control reject message; and based on the first radio resource control reject message, communicate another radio resource control setup request with another network node of the non-terrestrial network.

2. The apparatus of claim 1, wherein communicating the information comprising a radio resource control setup request is based on: the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: communicate with the network node of the non-terrestrial network an initial random access channel procedure; and based on the initial random access channel procedure, communicate with the network node the radio resource control setup request and a store and forward availability.

3. The apparatus of claim 1, wherein the first radio resource control rejectmessage comprises redirect carrier information; and wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the apparatus at least to: based on the redirect carrier information, communicate another radio resource control setup request with another network node of the non-terrestrial network.

4. The apparatus of claim 3, wherein the redirect carrier information comprises an indication of a wait time for which a feeder link is available for communicating with the another network node.

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

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

7. The apparatus of claim 1, wherein the at least one timer is using a total time taken from network attached storage and an offset of five times the total time.

8. The apparatus of claim 7, wherein the total time is using a time taken between network attached storage registration request from the network node to the non-terrestrial network, wherein the total time considers four message exchanges between core network functions and one message between a random access network and a core network function, and wherein it is assumed that each message exchange would take a same time.

9. The apparatus of claim 1, wherein the timer is one of a network attached storage 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 time between the user equipment and the network node of the network attached storage registration request.

11. The apparatus of claim 9, wherein the store and forward type timer allows enough time for network attached storage registration procedure to be completed with intermittent gaps in feeder link connections.

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

13. The apparatus of claim 9, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the apparatus at least to: add a further offset or buffer to a prior network attached storage wait type timer for store and forward values to create or update a new network attached storage wait type timer.

14. The apparatus of claim 13, wherein the prior network attached storage wait type timer for store and forward values is used to obtain a statistical approximation or computed value estimates of an expected network attached storage timer for store and forward functionality for use to create or update the new network attached storage wait type timer.

15. The apparatus of claim 14, wherein the statistical approximation or the computed value estimates are used depending on whichever is having a greater value.

16. The apparatus of claim 14, wherein the new network attached storage wait type timer is added to statistical data for continuously improving estimates.

17. The apparatus of claim 1, wherein the information comprising a radio resource control setup request is using a network attached storage store and forward flag, and wherein based on the network attached storage store and forward flag being used the user equipment supports store and forward functionality.

18. The apparatus of claim 17, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the apparatus at least to: based on the information comprising the radio resource control setup request not using a network attached storage store and forward flag, communicate a network attached storage registration rejection message for the radio resource control setup request between the user equipment and the network node; and based on the network attached storage registration rejection message create or update a new store and forward type timer in the non-terrestrial network.

19. The apparatus of claim 18, wherein the at least one memory stores instructions, that when executed by the at least one processor, cause the apparatus at least to: based on the network attached storage registration rejection message, another network attached storage registration procedure is re-attempted using another radio resource control setup request between the user equipment and the network node.

20. The apparatus of claim 19, wherein whether or not the another radio resource control setup request comprises a network attached storage store and forward flag a new at least one timer value for store and forward is used between the user equipment and the network node for the another network attached storage registration procedure.

21. The apparatus of claim 20, wherein the new at least one timer value is configured to allow enough time for a network attached storage registration procedure to be completed considering intermittent gaps in feeder link connections.

22. The apparatus of claim 20, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the apparatus at least to: create new inter-satellite links for use to share updated and latest between satellites of the non-terrestrial network.

23. The apparatus of claim 1, wherein the at least one memory stores instructions, that when executed by the at least one processor, cause the apparatus at least to: communicate between the user equipment and the network node computed time values of the new at least one timer.

24. A method, comprising: communicating from user equipment to a network node of a non-terrestrial network first information comprising a radio resource control setup request, wherein based on the communicating, at least one timer is started based on the radio resource control setup request for at least one of a response to the non-terrestrial network first information or creation of a radio resource control connection, and wherein the at least one timer is dynamically updated at least based on at least one of an identity of the user equipment or on a satellite of the non-terrestrial network that the user equipment is attached; based on expiration of the at least one timer for a feeder link not being available, communicating between the network node and the user equipment an indication of a first radio resource control reject message; and based on the first radio resource control reject message, communicating another radio resource control setup request with another network node of the non-terrestrial network.

Images