User equipment, network-entity, and method for adjusting timers while switching between terrestrial-network and non-terrestrial-network
Adaptive timer management systems address the mismatch in propagation delays between TN and NTN by dynamically adjusting timer values, enhancing signaling robustness and reducing latency in multi-RAT scenarios.
Patent Information
- Application Number
- PCT/KR2026/096710
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-07
- Publication Date
- 2026-11-12
AI Technical Summary
Existing timer management systems in wireless communication networks fail to adapt to the varying and longer propagation delays of non-terrestrial networks (NTN), leading to premature timer expiry, false failures, unnecessary retransmissions, and mobility stalls when switching between terrestrial-networks (TN) and NTN, especially in multi-RAT scenarios.
Adaptive timer adjustment mechanisms that account for different round-trip time characteristics of TN and NTN by dynamically adjusting timer values during mobility events, using configurable or network-configured offsets to ensure timely and efficient communication.
Enhances signaling robustness and reduces latency by aligning timer operations with propagation delays, preventing premature expiry and resource wastage, thus improving mobility performance across TN and NTN links.
Smart Images

Figure KR2026096710_12112026_PF_FP_ABST
Abstract
Description
USER EQUIPMENT, NETWORK-ENTITY, AND METHOD FOR ADJUSTING TIMERS WHILE SWITCHING BETWEEN TERRESTRIAL-NETWORK AND NON-TERRESTRIAL-NETWORK
[0001] The present application relates to the field of timer management in wireless communication systems, and more particularly relates to a user equipment (UE), a network-entity, and a method for adjusting timers while switching between terrestrial-network (TN) and non-terrestrial-network (NTN) during mobility.
[0002] Timer handling in wireless networks includes the initiation, monitoring, and expiry of timers that govern protocol behaviour, state transitions, retransmission control, and resource management. In conventional terrestrial deployments, such timers are typically configured with fixed values aligned with relatively short and predictable round-trip times (RTTs) of ground-based radio links. These timers span multiple protocol layers, including, but is not limited to, the non-access stratum (NAS) and Layer 2 (L2) sub-layers such as medium access control (MAC), radio link control (RLC), and packet data convergence protocol (PDCP), and are used for functions such as registration, session continuity, handovers, and resource releases.
[0003] Figure 1a illustrates a high-level multi-radio access technology (RAT) architecture for a user equipment (UE) connected with two parallel network generations, according to the prior art. As referred to in Figure 1, in the high-level multi-RAT architecture, the modern UEs are designed to operate across multiple RATs, such as a 5th generation (5G) core / RAN and a 6th generation (6G) core / radio access network (RAN), either simultaneously or alternately.
[0004] The introduction of non-terrestrial-networks (NTN) in the 3rd Generation Partnership Project (3GPP) ecosystem alters this delay profile. NTN links, including satellite-based communications via low earth orbit (LEO), medium earth orbit (MEO), and geostationary earth orbit (GEO) constellations, can exhibit end-to-end propagation delays ranging from a few milliseconds (e.g., LEO) to several hundred milliseconds (e.g., GEO). Such delays are substantially larger than terrestrial delays and can vary with orbital altitude, satellite position, and link geometry.
[0005] Figure 1b illustrates a conventional 3GPP-based NTN system architecture, according to the prior art.
[0006] As referred to in Figure 1b, the NTN network, involving the LEO, MEO, or GEO satellites and UAV-mounted gNodeBs, introduces significantly higher and variable propagation delays compared to the TN. When a multi-RAT UE transitions between the NTN network and the TN network during handover or dual connectivity, the existing fixed 3GPP timer values, originally dimensioned for terrestrial RTTs, become inadequate. The mismatch leads to premature timer expiry, false radio link failures, unnecessary retransmissions, handover stalls, and degraded mobility performance across NAS, RRC, L2, and IMS signalling layers.
[0007] A mismatch between fixed terrestrial timer values and the longer and more variable NTN propagation delays can degrade signalling and data reliability. For example, timers configured based on terrestrial RTT assumptions may expire before a valid response traverses the NTN path, causing false failure detection and unnecessary retransmissions. Conversely, configuring timers conservatively to accommodate worst-case NTN delays can increase latency, extend active-state durations, and increase UE power consumption. Timer misalignment may also stall mobility procedures, including handovers between cells and between terrestrial and non-terrestrial access points, due to signalling timeouts occurring during critical steps.
[0008] In addition, user equipment (UE) and network architectures increasingly support multi-radio access technology (multi-RAT) operation and multi-connectivity, in which a UE can access multiple radio access technologies (RATs) (e.g., long-term evolution (LTE), 5G new radio (NR), and wireless local area network (WLAN)) simultaneously or sequentially. In such multi-RAT scenarios, timer management becomes more complex because each RAT (and corresponding protocol stack) may experience different RTT and reliability characteristics. When a UE maintains concurrent connectivity to a terrestrial-network (TN) and the NTN, e.g., dual connectivity and dual active protocol stack (DAPS) operation, a timer value suitable for one access leg may be unsuitable for the other, if configured timer not take the different path delays into account which existing fixed-timer frameworks are not designed to accommodate.
[0009] Furthermore, mobility procedures such as L1 / L2 triggered mobility (LTM) and radio resource control (RRC)-based handover may not always provide proactive reconfiguration of timer values for the target cell or target RAT. In such cases, the UE may continue operating with timer settings selected for the source link, which can be misaligned with the delay characteristics of the new access. The lack of timely timer adaptation during mobility events can reduce signalling robustness in hybrid TN / NTN and multi-RAT deployments.
[0010] Accordingly, there is a need for techniques that adjust timer behaviour when a UE switches between, or concurrently operates over, TN and NTN access so that timer operation remains aligned with the applicable RTT and propagation-delay conditions, including during mobility.
[0011] Therefore, it is desirable to provide enhanced timer-adjustment techniques that mitigate premature expiry, avoid unnecessary retransmissions, and improve signalling robustness when operating across TN and NTN links, particularly in multi-RAT mobility scenarios.
[0012] This summary is provided to introduce a selection of features, in a simplified format, that are further described in the detailed description of the disclosure. This summary is neither intended to identify key or essential inventive concepts of the disclosure nor is it intended for determining the scope of the disclosure.
[0013] This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the disclosure. This summary is neither intended to identify key nor essential inventive concepts of the disclosure, nor is it intended to determine the scope of the disclosure.
[0014] According to an embodiment, a method by a user equipment (UE) for adjusting timers while switching between Terrestrial-network (TN) and Non-terrestrial-network (NTN) during mobility is provided. The method includes transmitting a signalling message to a network via a first radio access technology (RAT). The first RAT is one of the TN and the NTN. Further, the method includes initiating a first timer with the transmission of the signalling message, wherein the first timer has a first timer value specified for accessing the first RAT. Furthermore, the method includes detecting, during the transmission of the signalling message, a mobility event from the first RAT to a second RAT having a second timer value specified for accessing the second RAT. The second RAT is the other of the TN and the NTN. The first RAT and the second RAT have different round-trip time characteristics. Additionally, the method includes adjusting the first timer while switching between the TN and the NTN in response to the detected mobility event of the UE.
[0015] According to an embodiment, the first RAT and the second RAT includes any access technology and not limited to TN and NTN.
[0016] According to an embodiment, a user equipment (UE) for adjusting timers while switching between Terrestrial-network (TN) and Non-terrestrial-network (NTN) during mobility is provided. The UE includes a transceiver, a memory and a processor. The transceiver is configured to communicate with the TN and the NTN. The processor is coupled to the transceiver and the memory. The processor is configured to transmit a signalling message to a network via a first radio access technology (RAT). The first RAT is one of the TN and the NTN. Further, the processor is configured to initiate a first timer with the transmission of the signalling message. The first timer has a first timer value specified for accessing the first RAT. Furthermore, the processor is configured to detect, during the transmission of the signalling message, a mobility event from the first RAT to a second RAT having a second timer value specified for accessing the second RAT. The second RAT is the other of the TN and the NTN. The first RAT and the second RAT have different round-trip time characteristics. Still further, the processor is configured to adjust the timer while switching between the TN and the NTN in response to the detected mobility event of the UE.
[0017] According to an embodiment, a network-entity for adjusting timers while switching between Terrestrial-network (TN) and Non-terrestrial-network (NTN) during mobility. The network-entity includes a communication interface, a processor and a memory. The communication interface is configured to communicate with a user equipment (UE) via the TN and the NTN. The processor is coupled to the communication interface and the memory. The processor is configured to receive a signalling message to the UE via a first radio access technology (RAT). The processor is configured to initiate a first timer upon the reception of the signalling message. The first timer has a first timer value specified for accessing the first RAT. Further, the processor is configured to detect, during the reception of the signalling message, that the UE has performed a mobility event from the first RAT to a second RAT. Additionally, the processor is configured to adjust the timer in response to the mobility event by performing at least one of restarting the first timer with a second timer value specified for accessing the second RAT, adjusting the first timer to a configurable timer value, and stopping the first timer and thereby waiting for a new signalling message from the UE.
[0018] To further clarify the advantages and features of the present disclosure, a more particular description of the disclosure will be rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the disclosure and are therefore not to be considered limiting of its scope. The disclosure will be described and explained with additional specificity and detail in the accompanying drawings.
[0019] Features, aspects, and advantages of embodiments of the disclosure will be described below with reference to the accompanying drawings, in which reference numerals denote like elements, and wherein:
[0020] Figure 1aillustrates a high-level multi-radio access technology (RAT) architecture for a user equipment (UE) connected with two parallel network generations, according to the prior art;
[0021] Figure 1b illustrates a conventional 3rd Generation Partnership Project (3GPP)-based Non-terrestrial-network (NTN) system architecture, according to the prior art;
[0022] Figure 2aillustrates a sequence of operations depicting a method in which a timer mismatch occurs during NTN -to- Terrestrial-network (TN) mobility of the UE for emergency registration, according to the related art;
[0023] Figure 2b illustrates a sequence of operations depicting a method for adjusting timers while the UE switches between the NTN and the TN, according to implementations of the present disclosure;
[0024] Figure 3a illustrates a TN timing diagram for the baseline uplink scheduling flow with zero timing advance (TA) in the TN, according to the related art;
[0025] Figure 3b illustrates a TN timing diagram for the baseline uplink scheduling flow with a non-zero TA in the TN, according to the related art;
[0026] Figure 3c illustrates an NTN timing diagram for the uplink scheduling flow, according to the related art;
[0027] Figure 3d illustrates a critical failure scenario in the NTN, according to the related art;
[0028] Figure 3e illustrates a premature timer expiry scenario in the NTN, according to the related art;
[0029] Figure 3f illustrates a timing diagram for timer adjustment while the UE switches between the TN and the NTN, according to implementations of the present disclosure;
[0030] Figure 4a illustrates a signalling flow diagram depicting a problematic scenario in which the UE transitions between the NTN and the TN while a service request procedure is ongoing, according to the related art;
[0031] Figure 4b illustrates a sequence of operations depicting a method for adjusting timers while the UE switches between the NTN and the TN, according to implementations of the present disclosure;
[0032] Figure 5a illustrates a sequence of operations depicting a method in which the timer mismatch occurs during the NTN-to-TN mobility of the UE, according to the related art;
[0033] Figure 5b illustrates a sequence of operations depicting a method for adjusting timers while the UE switches between the NTN and the TN, according to implementations of the present disclosure;
[0034] Figure 5c illustrates a sequence of operations depicting a method for triggering Mobility registration while the UE switches between the NTN and the TN, according to implementations of the present disclosure;
[0035] Figure 6a illustrates a sequence of operations depicting a method in which the PDU session establishment timer mismatch occurs during the NTN-to-TN handover, according to the related art;
[0036] Figure 6b illustrates a sequence of operations depicting a method to overcome the PDU session establishment timer mismatch occurring during the NTN-to-TN handover, according to implementations of the present disclosure;
[0037] Figure 7a illustrates a sequence of operations depicting a method in which the registration accept timer is not adjusted at AMF during the TN-to-NTN handover, according to the related art;
[0038] Figure 7b illustrates a sequence of operations depicting a method for adjusting the registration accept timer at AMF during the TN-to-NTN handover to overcome the registration accept timer mismatch occurring during the NTN-to-TN handover, according to implementations of the present disclosure;
[0039] Figure 8illustrates a process flow of a method performed by the UE for adjusting timers while switching between the TN and the NTN during mobility, in accordance with one or more embodiments of the disclosure;
[0040] Figure 9illustrates the UE for adjusting timers while switching between the TN and the NTN during mobility the TN and the NTN during mobility, in accordance with one or more embodiments of the disclosure; and
[0041] Figure 10 illustrates a network-entity for adjusting timers while switching between the TN and the NTN during mobility, in accordance with one or more embodiments of the disclosure.
[0042] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
[0043] For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the various embodiments, and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the invention as illustrated therein, being contemplated as would normally occur to one skilled in the art to which the invention relates.
[0044] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are explanatory of the invention and are not intended to be restrictive thereof.
[0045] Reference throughout this specification to "an aspect," "another aspect," or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrase "in an embodiment", "in another embodiment", and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.
[0046] The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or sub-systems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices or other sub-systems or other elements or other structures or other components or additional devices or additional sub-systems or additional elements or additional structures or additional components.
[0047] The present disclosure relates to techniques for adaptive timer management for multi-radio access technology (RAT) 5th generation (5G) network / 6th generation (6G) network with terrestrial-networks (TNs) and non-terrestrial-networks (NTNs).
[0048] Figure 2a illustrates a sequence of operations depicting a method 200a in which a timer mismatch occurs during NTN-to-TN mobility of a user equipment (UE) 201 for emergency registration, according to the related art.
[0049] As illustrated in Figure 2a, a wireless communication system may include the UE 201 and a network-entity 209. The network-entity 209 may include a terrestrial 5G New radio access network node (NG-RAN-TN) 203, a non-terrestrial 5G New RAN node operating via a geostationary satellite (NG-RAN-satellite-NTN, GEO) 205, and a 5th generation (5G) network access and mobility management function (AMF) 207. The sequence of operation may correspond to a communication between the UE 201 and the network-entity 209 (e.g., the NG-RAN-TN 203, the NG-RAN-satellite-NTN, GEO 205, and the AMF 207). In an implementation, the NG-RAN-TN) 203, the NG-RAN-satellite-NTN (GEO) 205, and the AMF 207. UE 201 may initially be registered for emergency service with limited service in the NTN 205, and maintain a registered tracking area identity (TAI) list. The TAI may include TAI-1 associated with the NG-RAN-TN 203 and TAI-2 associated with the NG-RAN-satellite-NTN, GEO 205. The NG-RAN-TN 203 may be interchangeably referred to herein and after as the "TN 203", and NG-RAN-satellite-NTN, GEO 205 may be interchangeably referred to herein and after as the "NTN 205". At operation 202, the UE 201 may initially be camped on the NTN 205 in a 5GMM-IDLE state. Further, at operation 204, the UE 201 may transition to a 5GMM-registered limited service state. Further, at operation 206, the UE 201 may initiate an emergency registration request by transmitting an RRCConnectionSetupComplete (REGISTRATION REQUEST) to the NTN 205. At operation 208, the transmission may cause the UE 201 to enter a 5GMM-registered-initiated state. At operation 210, upon initiating the registration, the UE 201 may start a non-access stratum (NAS) timer T3510 with a duration of 27 seconds. A timer value may be configured for the NTN access type to account for the higher propagation delay of the GEO satellite link via node 205. Further, at operation 212, the NTN 205 may forward the emergency registration request by transmitting the RRCConnectionSetupComplete (REGISTRATION REQUEST) to the AMF 207. Further, at operation 214, the timer T3510 may be initiated by the UE 201. Subsequently, at operation 216, the UE 201 may perform a handover and move from the NTN 205 to the TN 203. However, at operation 218, the UE 201 may not adjust the running T3510 timer to the shorter 15-second duration appropriate for the TN 203. Instead, the UE 201 may continue to wait the full 27 seconds for a registration acceptance from the AMF 207 218. As a result, at operation 220, when no response is received within the duration of the timer T3510. At operation 122, the timer T3510 may expire after 27-x seconds where x is duration spent on the NTN 205. At operation 224, the UE 201 may be forced to re-attempt the emergency registration, thereby experiencing an unnecessary delay. In an implementation, the unnecessary delay of 12 seconds beyond the terrestrial access via the TN 203 may have been required, which may be particularly detrimental in emergency service scenarios where rapid network access is critical. Thus, a critical timing inefficiency may occur when the UE 201 transitions between the TN 203 and the NTN 205 RANs during an emergency registration procedure.
[0050] Further to overcome the above problem, as depicted in Figure 2a, the solution is provided in the forthcoming paragraph while explaining Figure 2b.
[0051] Figure 2b illustrates a sequence of operations depicting a method 200b for adjusting timers while the UE 201 switches between the TN 203 and the NTN 205, according to implementations of the present disclosure.
[0052] In one embodiment, as illustrated in Figure 2b, operations 232-246 relate to the movement of the UE 201 from the NTN node 205 to the TN 203 to perform the handover and, as explained in reference to operations 202-216 (shown in Fig. 2a), respectively. Accordingly, a detailed description of the operations 232-246 has been omitted for the sake of brevity. In an implementation, upon performing the handover from the NTN 205 to the TN 203, the UE 201 may set the timer value to the new RAT type (TN) and may further apply one of the different solution alternatives to address the timer mismatch.
[0053] In an embodiment, at operation 248, the UE 201 may adopt the timer value appropriate for the new RAT type by changing the expiry value of T3510 from 27 seconds to 15 seconds. At operation 250, the T3510 may exhibit the standard NAS timer duration for the TN 203. Further, at operation 252, the UE 201 may receive the registration accept message from the AMF 207 within the correct terrestrial timeframe without unnecessary delay.
[0054] In another embodiment, at operation 254, the UE 201 may adjust the running timer T3510 to a configurable X value. At operation 256, the difference between the NTN and TN timer durations may be reconciled by applying a network-configurable or pre-configured offset value X. In a non-limiting example, the T3510 may allow the flexible timer adaptation that may account for varying deployment scenarios. At operation 258, after the completion of T3510, the UE 201 may receive the registration accept message from the AMF 207 within the adjusted X-second window.
[0055] In another embodiment, the UE 201 may abort the ongoing registration procedure entirely upon moving to the TN 203. At operation 260, the UE 201 may re-initiate a fresh registration by transmitting a new registration request for the emergency service to the TN 203. At operation 262, the TN 203 may forward the new registration request for the emergency service to the AMF 207. At operation 264, the UE 201 may enter the 5GMM-registered-initiated state. At operation 266, the timer T3510 may now be initiated. At operation 268, the timer T3510 may expire after 15 seconds, which may be the value native to the TN access type. At operation 270, the UE 201 may receive the registration accept message from the AMF 207, thereby ensuring that the emergency registration is handled entirely within the terrestrial domain with the appropriate timer configuration.
[0056] In another embodiment, a reverse scenario, where the UE 201 may move from the terrestrial node 203 to the NTN 205 during an ongoing registration procedure, is also applicable. In the reverse scenario, the timer T3510 may be adjusted upward from 15 seconds to 27 seconds or to a configurable value (X) to account for the higher satellite propagation delay. In an advantageous aspect, the method 200b may ensure consistent and appropriate timer behaviour regardless of the direction of the inter-RAT mobility.
[0057] In another embodiment, when the UE 201 may be attached to the NTN 205, configured Layer-2 timer values, which govern packet transmission and acknowledgement cycles, may be typically set to the TN 203 defaults. Further, the UE 201 may not account for the significantly longer round-trip times (RTT) inherent to satellite links. Because the timers expire before the NTN propagation delay is fully traversed, the UE 201 may misinterpret normal in-flight transmissions as failures, resulting in erroneous packet retransmissions and unnecessary consumption of radio resources. In essence, the mismatch between TN-calibrated timers and actual NTN timing conditions may introduce both signalling inefficiency and resource waste at the L2 layer.
[0058] Further, TN timing diagrams associated with the NTN 205 and the TN 203 are provided in the forthcoming paragraph.
[0059] Figure 3a illustrates a TN timing diagram for the baseline uplink scheduling flow with zero timing advance (TA) in the TN 203, according to the related art.
[0060] The TN timing diagram may correspond to a baseline uplink scheduling cycle in the TN 203 when the TA is zero. As referred to in Figure 3a, two slot timelines corresponding to a gnb_DL / UE (downlink) and a gnb_UL / UE (uplink) are indexed by a system frame number and slot number (Sfn: Slot). In an implementation, the gNodeB may transmit an uplink downlink control information (UL DCI) scheduling grant at slot 10, instructing the UE 201 when and where to send the uplink data. After a fixed scheduling offset of K2 = 4 slots, the UE 201 may transmit on the physical uplink shared channel (PUSCH) at slot 14, computed as DCI slot (10) + K2 (4). The TA being zero may represent a negligible propagation delay in the TN 203. Thus, when the TA is zero, an uplink frame associated with the UE 201 may align perfectly with a reception frame of the gNodeB. Further, the entire DCI-to-PUSCH cycle may be completed within just 4 slots with no round-trip compensation required. The perfect alignment may establish an ideal terrestrial baseline against which the NTN scenario (TA 햕s contrasted. NTN 205, the same scheduling cycle may be accounted for substantially longer propagation delays, causing existing fixed timers to expire prematurely and directly motivating the need for the proposed adaptive timer management mechanism.
[0061] Figure 3b illustrates a TN timing diagram for the baseline uplink scheduling flow with a non-zero TA in the TN 203, according to the related art.
[0062] The TN timing diagram may correspond to the baseline uplink scheduling cycle in the TN 203 when the TA is not equal to zero. As referred to in Figure 3b, the TN uplink scheduling timing diagram under a non-zero TA (TA 0) condition, showing four distinct timelines, including gnb_DL (gNodeB downlink), gnb_UL (gNodeB uplink), Ue_DL (UE downlink), and Ue_UL (UE uplink), each indexed by System Frame Number and Slot (Sfn: Slot). Unlike the ideal TA = 0 case, where gNodeB and timelines of the UE 201 may be perfectly aligned, the non-zero TA of 100 μs (split as 50 μs in each direction) may introduce a slight offset between the network and device perspectives. The delay may necessitate four separate timelines. The gNodeB may initiate the process by transmitting an uplink downlink control information (UL DCI) scheduling grant at slot 10 on the gNB_DL timeline. The grant may propagate to the UE 201 with a one-way downlink delay of approximately TA / 2 (~50 μs), shown by the DL Sync arrow between gnb_DL and Ue_DL. Upon receiving the grant, the UE 201 may apply the K2 with a 4-slot scheduling offset to determine the PUSCH transmission opportunity at slot 14. To ensure that the uplink transmission arrived at the gNodeB correctly aligned with the expected slot boundary, the UE 201 may apply the TA compensation. The TA compensation may include transmitting slightly earlier on a local Ue_UL timeline so that after the ~50 μs uplink propagation, the PUSCH may land precisely at slot 14 on the gnb_UL timeline. Thus, even with the non-zero TA, the propagation delay may remain negligibly small (sub-slot). Therefore, existing fixed timer values and scheduling offsets may function correctly without any adaptation in NTN scenarios where satellite-induced delays may span multiple slots.
[0063] Figure 3c illustrates an NTN timing diagram for the uplink scheduling flow, according to the related art.
[0064] The NTN timing diagram illustrates the uplink scheduling flow when the UE 201 may operate through the NTN 205, where the propagation may be orders of magnitude larger than in the TN 203. Figure 3c presents four timelines, including the gnb_DL, the gnb_UL, the Ue_DL, and the Ue_UL, each indexed by Sfn: Slot, with significant misalignment between the gNodeB and perspectives of the UE 201 due to the large round-trip delay. The scheduling parameters may include the UL DCI sent from the network at slot 10, K2 = 4, TA = 20 slots (considering 10 slots in each direction for UL and DL), K_Offset = 190, and PUSCH = 204 (computed as K_Offset + K2 + 10 (current slot in this example) = 190 + 4 + 10 = 204). The flow may begin when the gNodeB transmit the UL DCI scheduling grant at slot 10 on the gNB_DL timeline. In an implementation, unlike the TN 203case, the grant may not reach the UE 201 until slot 20 on the UE_DL timeline,i.e.,a 10-slot one-way downlink propagation delay through the satellite link. Upon receiving the DCI at slot 20, the UE 201 may subsequently begin data packet preparation and start a poll timer. The poll timer may be a configurable retransmission timer (t-PollRetransmit in 3GPP protocols) used to ensure reliability by triggering retransmissions when a sender, such as the UE 201, fails to receive an acknowledgement (ACK / NACK) from a receiver, such as network-entity 209, within a specified duration. However, the UE 201 may not simply transmit K2 = 4 slots later. Rather, the UE 201 may have to account for the massive K_Offset = 190 slots, which may compensate for the satellite link delay so that the PUSCH may arrive at the gNodeB at the correct slot. The combined scheduling offset may become K2 + K_Offset (= 194 slots) from the perspective of the UE 201, placing the actual PUSCH transmission at slot 194 on the UE_UL timeline. After the 10-slot uplink propagation delay, the PUSCH may arrive at the gNB_UL timeline of the gNodeB at slot 204. The critical observation may include a gap between when the UE 201 starts the poll timer (slot 20) and when the actual physical transmission occurs (slot 194). Therefore, a span of 174 slots during which any terrestrial-calibrated L2 timer, such as the default 45 ms poll timer (case where NW not configured the timer), may expire well before the data even reaches the physical layer i.e. premature expiry lead to retransmission of packet and resource wastage.. Hence, the present scenario may precisely indicate the timer mismatch problem associated with the NTN timings.
[0065] Figure 3d illustrates a critical failure scenario in the NTN 205, according to the related art.
[0066] A default configuration of 45ms demonstrating the critical failure scenario in the NTN 205 is referred to in Figure 3d, when a L2 poll timer may retain the TN default value of 45 ms without any NTN-specific adaptation. Figure 3d represents the four timelines, including the gnb_DL, the gnb_UL, the Ue_DL, and the Ue_UL, indexed by Sfn: Slot, with the same NTN scheduling parameters as the preceding Figure 3c. The UL DCI may be sent from the network at slot 10, as K2 = 4, TA = 20 slots (10 each direction), K_Offset = 190, and PUSCH = 204. The flow may begin at slot 20 on the Ue_DL timeline, where the UE 201 may receive the scheduling grant after the 10-slot downlink satellite propagation delay. The UE 201 may start data packet preparation and simultaneously start the poll timer with a default TN-configured value of 45 ms upon receipt of the scheduling grant. A poll timer duration may span from slot 20 to approximately slot 65 on the Ue_UL timeline, representing the 45 ms window during which the UE 201 may expect an acknowledgement or response. However, the actual physical data transmission from the PHY layer, accounting for the K_Offset and TA compensation, may not occur until slot 194 on the Ue_UL timeline. The PUSCH may finally arrive at the gNodeB at slot 204 on the gNB_UL timeline. A burst symbol at slot 65 may indicate that the poll timer expires at slot 65, which may be 129 slots before; the data may even reach the physical layer at slot 194 and far earlier than any acknowledgement may return from the network. Thus, a premature expiry may cause the UE 201 to falsely conclude that the transmission has failed. Further, the premature expiry may trigger unnecessary retransmissions, wasting radio resources, and potentially cascading into higher-layer signalling failures. Thus, the terrestrial-calibrated timer values may be fundamentally incompatible with NTN propagation characteristics.
[0067] Figure 3e illustrates a premature timer expiry scenario in the NTN 205, according to the related art.
[0068] As referred to in Figure 3e, the network may have configured a larger L2 poll timer value of 150 ms (significantly higher than the 45 ms default in Figure 3d). Still, the timer value may be less than the K_Offset of 190 slots, resulting in the premature timer expiry problem. Figure 3e presents four timelines, including the gnb_DL, the gnb_UL, the Ue_DL, and the Ue_UL, with identical scheduling parameters. The UL DCI may be sent from the network at slot 10, K2 = 4, TA = 20 slots (10 in each direction), K_Offset = 190, and PUSCH = 204 (190 + 4 + 10). The UE 201 may receive the DCI at slot 20 on the Ue_DL timeline after the 10-slot downlink propagation delay, and immediately begin data packet preparation and start the poll timer. The poll timer duration of 150 ms is shown in Figure 3e as a bar spanning from slot 20 to approximately slot 170 on the Ue_UL timeline, where the timer expiry is marked by a starburst. However, the actual data transmission from the physical (PHY) layer with TA consideration may not occur until slot 194, with the PUSCH finally arriving at the gNB_UL at slot 204. In an implementation, the poll timer may expire at slot 170, a full 24 slots before the UE 201 may even physically transmit the data at slot 194 and far before any acknowledgement may return from the network. Thus, even when the network actively configures the timer value larger than the default, if that value remains smaller than the K_Offset (150 ms < 190 slots), the timer may still expire before the data reaches the air interface. As a result, erroneous retransmissions, wasted radio resources, and potential signalling failures may occur, reinforcing the need for a timer adaptation mechanism that accounts for the full NTN scheduling offset.
[0069] Further, the solutions to overcome the limitations as discussed in Figures 3a to 3e are provided in the forthcoming paragraphs.
[0070] In an embodiment, the UE 201 may replace the configured timer value with a new configurable value "X" that may be sufficiently large to cover the full NTN scheduling and propagation cycle. Rather than relying on the network-configured 150 ms, the UE 201 may substitute a value that may account for the satellite link characteristics, ensuring the timer may not expire before the transmission and acknowledgement cycle completes.
[0071] In an embodiment, the UE 201 may perform timer validity detection. During the timer validity detection, the network-configured timer values may be analysed to determine whether the timer values are adequate for the current NTN conditions. The timer validity detection may be triggered under one or more of the conditions. A first condition may be related to a scenario when the timer value is less than the Kcell_Offset, which may correspond to a limitation described in Figure 3e, where 150 ms < 190 slots. A second condition may be related to a scenario when the timer value is less than the TA. A third condition may be related to a scenario when the timer value is less than Kcell_Offset + RTT (i.e.,TA + processing time at receiver, K2). These conditions may be applied standalone or in combination, acting as a safeguard that may automatically detect an inadequate timer configuration before causing a failure.
[0072] Figure 3f illustrates a timing diagram for timer adjustment while the UE 201 switches between the TN 203 and the NTN 205, according to implementations of the present disclosure.
[0073] In an embodiment, a new timer value may be determined in line with NTN considerations, scaling from the LEO to the GEO orbit scenarios. The determination of the new timer value may ensure the peer entity has sufficient time to process and act before the timer expires. Three alternatives for the determination of the new timer value as given in expressions (1), (2), and (3) below:
[0074] New_timer Configured_timer() + Kcell_Offset + RTT (1)
[0075] which may add the full round-trip and offset on top of the configured timer.
[0076] New_timer Configured_timer() + Kcell_Offset + RTT / 2 (2)
[0077] which may use only the one-way propagation.
[0078] New_timer Kcell_Offset + RTT / 2, (3)
[0079] which may discard the configured timer entirely and determine the new timer purely from the NTN parameters.
[0080] In an implementation, the new_timer may be determined using equation (4) as given below:
[0081] New_timer = (K_Offset + K2 - TA / 2 + T_Poll(i.e. configured timer value))) = (190+ - 10 + 150) = 334 ms.(4)
[0082] In a non-limiting example, as shown in Figure 3f, the poll timer duration may be extended to 334 ms. The Ue_UL timeline may now reflect the poll timer duration spanning from slot 20 all the way past the actual data transmission point at slot 194, ensuring the timer remains active throughout the full scheduling cycle. The PUSCH may arrive at the gNB_UL at slot 204 well within the timer window, eliminating the premature expiry problem.
[0083] In an embodiment, the timer value can be further extended to accommodate for max RLC retransmission (configured by NW). The max value for the New timer value derived as given in eqution (5):
[0084] New_Timer (max) = New_Timer * Max_Retx_Count (5)
[0085] Therefore, it is to be understood that the New_Timer value can be a value in between New_Timer to New_Timer (max).
[0086] Figure 4a illustrates a signalling flow diagram 400a depicting a problematic scenario in which the UE 201 transitions between the NTN and the TN while a service request procedure is ongoing, according to the related art.
[0087] As referred to in Figure 4a, the UE 201 may communicate with the network-entity 209, including the AMF 207, via the NTN 205 and the TN 203.
[0088] At operation 402, the UE 201 may be registered for normal service in the NTN 205 (LEO / GEO) with a registered TAI list containing TAI-1 mapped to the TN 203 and TAI-2 mapped to the NTN 205. Further, the UE 201 may have an active PDU session (PDU1) for emergency service. At operation 404, the UE 201 may be in 5GMM-IDLE mode. Further, at operation 406, the UE 201 may be in 5GMM-registered limited service state. At operation 408, uplink data may become pending for the PDU1 emergency service. To transmit the data, at operation 410, the UE 201 may initiate a service request procedure by sending an RRCConnectionSetupComplete message containing a service request for emergency service, along with a corresponding registration request at operation 412 for emergency. At operation 414, the UE 201 may transition into the 5GMM-service request initiated state. Further, at operation 416, upon triggering the service request, a timer T3517 may be initiated with a value of 27 seconds. At operation 418, the timer T3517 may have a duration of 27 seconds, which may correspond to the timer configuration associated with the NTN 205. The timer T3517 may account for the longer round-trip delays inherent in satellite communication. At operation 420, while the timer is still running, the UE 201 may move from the NTN 205 to the TN 203 via handover. However, at operation 422, after the inter-RAT mobility event, the UE 201 may continue to wait up to full 27 seconds for a service accept response from the network, even though the UE 201 may now be operating on the TN 203, where the appropriate timer value would be significantly shorter. Further, at operation 424, since no response may be received from the network before the timer T3517expires. At operation 426, the time corresponding to the timer T3517 may expire. As a consequence, at operation 428, the UE 201 may indicate an emergency call (EMC) failure to the upper layers, resulting in a service disruption despite the UE 201 being connected to the TN 203. In an implementation, the same scenario may be possible in the vice versa case, where the UE 201 may move from the TN 203 to the NTN 205. In that situation, the UE201 may wait only 15 seconds (i.e.,the TN-configured T3517 value) for a service accept after moving to the NTN 205 RAT, instead of the 27 seconds required for NTN satellite communication. The insufficient wait time may similarly lead to premature timer expiry and service failure, as the network may need the longer NTN-appropriate duration to respond.
[0089] Further to overcome the above problem, as depicted in Figure 4a, the solution is provided in the forthcoming paragraph while explaining Figure 4b.
[0090] Figure 4b illustrates a sequence of operations depicting a method 400b for adjusting timers while the UE 201 switches between the TN 203 and the NTN 205, according to implementations of the present disclosure.
[0091] In one embodiment, as illustrated in Figure 4b, operations 432-450 relate to the movement of the UE 201 from the NTN node 205 to the TN 203 to perform the handover and, as explained in reference to operations 402-420 (shown in Fig. 4a), respectively. Accordingly, a detailed description of the operations 432-450 has been omitted for the sake of brevity. In an implementation, upon performing the handover from the NTN 205 to the TN 203, the UE 201 may set the timer value to the new RAT type (TN) and may further apply one of the different solution alternatives to address the timer mismatch.
[0092] In an embodiment, at operation 452, the UE 201 may wait for 15 seconds by changing the timer expiry value of the T3517. At operation 454, the timer T3517 may expire after 15 seconds. At 456, the AMF 207 may transmit the service accept message to the UE 201. Accordingly, the difference in timer value between the RAT to the configurable value may be adjusted.
[0093] In an embodiment, at operation 458, the UE 201 may wait for X seconds by changing the timer expiry value of timer T2517 to the configurable timer value. In an implementation, the UE 201 may adjust the timer T3517 to the configurable value X seconds instead of the fixed 15 seconds, allowing more flexibility. At operation 460, the UE may set the timer T3517 to 27 seconds (or X seconds, depending on the configuration). At operation 462, service accept message may arrive from the AMF 207 which may indicate a successful outcome under the configurable timer approach.
[0094] In an embodiment, If neither timer adjustment as explained in operations 452-456 and operations 458-462 yields a response in time, the UE 201 may abort and retry the entire procedure in the TN 203. At operation 464, the UE 201 may send a new service request message (RRCConnectionSetupComplete with emergency indication) directly through the TN 203.
[0095] At operation 466, the TN 203 may forward the service request message to the AMF 207. At operation 468 the UE 201 may enter the 5GMM-service request-initiated state again, now fully in the TN 203 context. At operation 470 the timer T3517 may be restarted at 27 seconds for the fresh attempt in the TN 203. At operation 472, the timer T3517 = 27 seconds may now be counting down for the new procedure. At operation 474, if the timer T3517 expires again without a response, the UE 201 may indicate the EMC failure to the upper layer, signaling that the emergency service request has failed. At operation 476, the service request message may represent the scenario where the network may not respond in time during the retry, successfully completing the emergency service request in the TN 203.
[0096] Figure 5a illustrates a sequence of operations depicting a method 500a in which the timer mismatch occurs during the NTN-to-TN mobility of the UE 201, according to the related art.
[0097] At operation 502, the UE 201 may initially be in the 5G MM-IDLE state in the NTN 205 coverage area, specifically under the TAI-2, which may be mapped to the NTN 205 (GEO or LEO). In the idle state, the UE 201 may not be actively connected to the network but may be registered and paged. The UE 201 may have a registered TAI list that may include the TAI-1 mapped to the TN 203 and TAI-2 mapped to the NTN 205. The UE 201 may intend to perform a registration procedure for normal service and wishes to request the eDRX parameters to optimise its power consumption during idle mode in the NTN environment.
[0098] At operation 504, the UE 201 may initiate the initial registration procedure by sending the Registration Request message to the network through the NTN 205. The Registration Request message may be carried within the RRCConnectionSetupComplete message. As part of the registration request, the UE 201 may include the requested eDRX cycle length value (denoted as X) and the paging time window (PTW) value (denoted as Y). The requested values may represent the preferred eDRX configuration of the UE 201 for optimising battery life while maintaining reachability in the NTN 205. The eDRX and PTW values may be specifically requested for normal service operation in the NTN.
[0099] At operation 506, the NTN 205 may forward the registration request message from the UE 201 to the AMF 207, via the NG interface. The forwarding may include the requested eDRX value (X) and PTW value (Y) of the UE 201 as originally included in the registration request message. The AMF 207 may receive the complete registration request and begin processing the UE 201 registration, including evaluating the eDRX and PTW parameters requested by the UE 201 for accessing the NTN 205.
[0100] At operation 506, upon receiving the registration request message, the AMF 207 may evaluate the requested eDRX parameters in the context of the NTN 205. The AMF 207 may take into account the unavailability period that may be inherent to NTN operations. The NTN operations may include the periods when the satellite may not be visible or accessible to the UE 201. The AMF 207 may adjust the eDRX cycle value to accommodate these unavailability periods, potentially modifying the requested values to ensure that the eDRX cycle aligns with visibility windows of the satellite and the paging capabilities of the network in the NTN 205. The AMF 207 may compute new eDRX values that may specifically be tailored for the NTN access type. One or more factors, such as satellite orbital period, coverage gaps, and paging coordination requirements, may be considered for computing the new eDRX values.
[0101] At operation 510, the AMF 207 may complete the registration procedure by sending a registration accept message back to the UE 201 through the NTN access. The registration accept message may include the network-provided eDRX value (X) and PTW value (Y), which may be determined by the AMF 207 after considering the NTN unavailability periods as described in operation 508. The network-provided values may differ from the originally requested values of the UE 201, as the AMF 207 may have factored in the NTN-specific characteristics such as satellite pass durations, inter-satellite handover gaps, and coverage discontinuities. The UE 201 may be expected to use the network-provided eDRX and PTW values for idle mode DRX operations. The network-provided eDRX and PTW values may be calculated and optimised for the NTN access type.
[0102] At operation 512, after the registration procedure is successfully completed, the network may send the RRC release message to the UE 201. The RRC release message may instruct the UE 201 to release the RRC connection and transition from the RRC Connected state back to the RRC Idle state. At this point, the UE 201 may have completed the registration with the NTN 205 and may have received the network-provided eDRX and PTW values. The RRC release message may effectively move the UE 201 into idle mode, where the UE 201 may begin applying the eDRX cycle and paging time window for monitoring paging occasions.
[0103] At operation 514, following the RRC release message, the UE 201 may enter the idle mode and may further begin applying the eDRX cycle length and PTW values that were provided by the AMF 207 in the registration accept message. While the UE 201 remains in the NTN coverage area under TAI-2, the eDRX configuration may be appropriate because the eDRX cycle length and PTW values were specifically computed by the AMF 207, considering the NTN satellite unavailability periods. The UE 201 may use the eDRX cycle length and PTW values to determine when to wake up and monitor paging channels, thereby conserving battery power during the extended sleep periods between paging occasions in the NTN.
[0104] At operation 516, the UE 201 may physically move from the NTN coverage area (TAI-2, served by the satellite) to the TN coverage area (TAI-1, served by NG-RAN-TN). The mobility event may represent a transition between two fundamentally different access types - from satellite-based NTN access to ground-based terrestrial access. The TAI may change from TAI-2 (NTN) to TAI-1 (TN). The transition may be considered as a critical point because the radio environment, propagation characteristics, coverage continuity, and network timing characteristics may be significantly different between the NTN 205 and the TN 203. The eDRX and PTW values that were optimised for the NTN 205 (considering satellite unavailability periods) may not be suitable for the TN 203, where the unavailability periods may not exist.
[0105] At operation 518, after moving to the TN, the UE 201 may enter idle mode and may further continue to apply the same eDRX cycle length and the same PTW values that were provided by the network for the NTN access. Since the eDRX values were specifically calculated by the AMF 207, considering the NTN satellite unavailability periods. The eDRX values calculated by the AMF 207 may include longer sleep cycles to account for satellite orbit gaps. Thus, the existing eDRX values may be inappropriate for the TN 203, where such unavailability periods may not exist. The TN 203 may have continuous coverage, but the TN 203 may not have the same timing constraints as satellite-based NTN 205. As a result, the UE 201 may use an excessively long eDRX cycle in the TN 203. Using long eDRX means that the UE 201 may wake up less frequently to check for paging, that leading to increased latency in receiving pages, potential missed paging occasions, and degraded service responsiveness. Thus, the mismatch between the eDRX parameters optimised for the NTN 205 and the actual TN 203 may represent a significant problem. The same scenario may also be possible in the reverse direction when UE 201 moves from the TN 203 to the NTN 205. The UE 201 may wrongly apply TN-optimised eDRX values in the NTN environment, potentially causing the UE 201 to wake up too frequently (wasting battery) or misalign with the satellite paging schedule.
[0106] Further to overcome the above problem, as depicted in Figure 5a, the solution is provided in the forthcoming paragraph while explaining Figure 5b.
[0107] Figure 5b illustrates a sequence of operations depicting a method 500b for adjusting timers while the UE 201 switches between the TN 203 and the NTN 205, according to implementations of the present disclosure.
[0108] In one embodiment, as illustrated in Figure 5b, operations 522-526 relate to the transmission of the registration request message from the UE 201 to the AMF 207, as explained in reference to operations 502-506 (shown in Fig. 5a), respectively. Accordingly, a detailed description of the operations 522-526 has been omitted for the sake of brevity.
[0109] At operation 528, the AMF 207 may provide eDRX values separately for the TN 203 and the NTN 205. Upon receiving the registration request, the AMF 207 may determine the eDRX parameters not as a single set of values, but separately for each access type, that is the TN 203 and the NTN 205. The AMF 207 may recognize that the registered TAI list of the UE 201 may include both the TN 203 and the NTN 205 tracking areas. Therefore, the UE 201 may operate in either network type during idle mode. By computing and providing distinct eDRX values for each RAT type, the AMF 207 may ensure that the UE 201 may have appropriate eDRX configurations regardless of which network the UE 201 is currently camped on. The per-access-type or per-RAT mapping approach may be implemented where the single eDRX value may be provided without distinguishing between the TN 203 and the NTN 205 characteristics.
[0110] At operation 530, the AMF 207 may consider unavailability period for the NTN 205. While computing the separate eDRX values, the AMF207 may specifically consider the unavailability period that may be inherent to the operations associated with the NTN 205 when determining the NTN-specific eDRX configuration. The unavailability period may refer to the time intervals when the satellite may not be visible or accessible to the UE 201, particularly in the LEO satellite scenarios where satellites may orbit the Earth and may have intermittent coverage windows. For the NTN eDRX value, the AMF 207 may factor in the satellite orbital period, coverage gaps, inter-satellite handover durations, and paging coordination requirements. Further, the AMF 207 may compute an eDRX cycle (Z value) and PTW (W value) that may align with the visibility windows of the satellite. For the TN eDRX value, no such unavailability period consideration may be needed. The TN 203 may provide continuous coverage, so the AMF 207 may provide eDRX values (X value for eDRX and Y value for PTW) that may be optimized for the TN 203 without the overhead of accounting for satellite unavailability.
[0111] At operation 532, the registration accept message with Dual eDRX and PTW Values (TN and NTN) may be received by the UE 201 from the AMF 207. The AMF 207 may complete the registration procedure by sending the registration accept message back to the UE 201 through the NTN access. The registration accept message may include two separate sets of the eDRX and the PTW values, each indicated by corresponding access type or RAT mapping, The one of the two separate sets may include the eDRX value (X) and the PTW value (Y) mapped to TN / NG-RAN RAT, The eDRX value (X) and the PTW value (Y) may be optimized for the TN 203 operation without satellite unavailability considerations. The other of the two separate sets may include the eDRX value (Z) and the PTW value (W) mapped to NTN / NG-RAN satellite RAT. The eDRX value (Z) and the PTW value (W) may be computed considering the NTN-specific unavailability periods and satellite coverage characteristics. By providing values corresponding to both the sets with clear access type or RAT mapping, the network may enable the UE 201 to apply the correct eDRX configuration based on which network type the UE 201 may be currently operating in.
[0112] At operation 534, after the registration procedure is successfully completed, the NTN 205 may send the RRC release message to the UE 201. The RRC release message may instruct the UE 201 to release the RRC connection and transition from the RRC connected state back to the RRC Idle state. During, transition, the UE 201 may receive and store both sets of the eDRX and the PTW values, one for the TN 203 and one for the NTN 205 along with respective access type or RAT mappings. The UE 201 may now be equipped to apply the appropriate eDRX configuration based on the current serving network type.
[0113] At operation 536, following the RRC release, the UE 201 may enter the idle mode while still being camped in the NTN coverage area under TAI-2. The UE 201 may identify being currently operating on the NTN / NG-RAN satellite RAT. Therefore, the UE 201 may apply the eDRX value (Z) and PTW value (W) that were specifically provided for the NTN / NG-RAN satellite RAT in the registration accept message. The eDRX and PTW values may be optimized by the AMF 207 considering the satellite unavailability periods. In an advantageous aspect, the paging monitoring schedule of the UE 201 may align with the coverage windows of the satellite. The UE 201 may use the NTN-specific values to determine when to wake up and monitor paging channels. In an advantageous aspect, the battery power may be efficiently conserved while remaining reachable through the satellite access.
[0114] At operation 538, the UE 201 may move from the NTN 205 to the TN 203. The UE 201 may physically move from the NTN coverage area (TAI-2, served by the satellite) to the TN coverage area (TAI-1, served by NG-RAN-TN). The mobility event may represent the transition between two the TN 203 and the NTN 205. The UE 201 may be already equipped with the separate eDRX values for both network types during the registration procedure. The UE 201 may detect the change in the RAT type from the NTN / NG-RAN satellite to TN / NG-RAN and may prepare to switch to the corresponding eDRX configuration.
[0115] At operation 540, upon moving to the TN 203, the UE 201 may correctly apply the eDRX value (X) and PTW value (Y) that may be specifically provided for the TN / NG-RAN RAT in the registration accept message (operation 532). Since the TN-specific eDRX values were computed by the AMF 207 without the overhead of satellite unavailability period considerations, the TN-specific eDRX values may be appropriately optimized for the TN 203 environment where continuous coverage is available. In an advantageous aspect, the UE 201 may monitor paging channels at the correct frequency for the TN 203, avoiding the long NTN-optimized eDRX cycles in the TN 203 that may cause increased paging latency and degraded service responsiveness. The UE 201 may seamlessly transition the eDRX behavior based on the RAT mapping, delivering optimal power savings and reachability in both network types without requiring a new registration procedure. In an implementation, the same approach may work in the reverse direction as well. If the UE 201 moves from the TN 203 to the NTN 205, the TN 203 eDRX values (X, Y) may be applied to the NTN 205 eDRX values (Z, W) while switching. In an advantageous aspect, the correct eDRX behavior may be implemented regardless of the direction of mobility between the TN 203 and the NTN 205.
[0116] Figure 5c illustrates a sequence of operations depicting a method 500c for adjusting timers while the UE 201 switches between the TN 203 and the NTN 205, according to implementations of the present disclosure.
[0117] In one embodiment, as illustrated in Figure 5b, operations 542-546 relate to the transmission of the registration request message from the UE 201 to the AMF 207, as explained in reference to operations 502-506 (shown in Fig. 5a), respectively. Accordingly, a detailed description of the operations 542-546 has been omitted for the sake of brevity.
[0118] At operation 548, the AMF 207 may consider the NTN unavailability Period. The AMF 207 may evaluate the requested eDRX parameters in the context of the NTN-specific characteristics. The NTN-specific characteristics may include the satellite orbital periods, the coverage gaps, and the intermittent visibility windows. The AMF 207 may adjust the eDRX value to account for the unavailability periods, computing values suitable for the satellite environment.
[0119] At operation 550, the registration acceptance may be transmitted from the AMF 207 to the UE 201 with the network-provided eDRX (X) and PTW (Y) values. Unlike Figure 5b, where the dual values (i.e.,the TN and the NTN) are provided in a single accept, in method 500c, only a single set of the NTN-optimised values may be provided.
[0120] At operation 552, the NTN 205 may transmit the RRC Release to the UE 201. In a non-limiting example, the network may release the RRC connection, transitioning the UE 201 back to the RRC Idle state. The UE 201 may have now completed the NTN registration with the NTN-specific eDRX parameters stored.
[0121] At operation 554, the UE 201 may apply the NTN eDRX. The UE 201 may enter the idle mode in the NTN 205 and correctly apply the network-provided eDRX values optimized for satellite operation, aligning the paging monitoring schedule with the satellite coverage windows.
[0122] At operation 556, the UE 201 may move from the NTN 205 to the TN 203. In a non-limiting example, the UE 201 may physically move from the satellite coverage area (TAI-2) into the TN coverage (TAI-1). The transition from the TAI-2 to the TAI-1 may be critical being fundamentally different access types with very different timing and coverage characteristics.
[0123] At operation 558, the UE 201 may trigger a mobility registration for the TN eDRX. Instead of relying on the pre-provided values (as discussed in Figure 5b), the UE 201 may proactively initiate a new mobility registration request specifically to obtain eDRX parameters appropriate for the TN 203. The UE 201 may recognise that the current NTN-optimised eDRX values may be unsuitable for the TN 203 and autonomously trigger a fresh registration to resolve the issue associated with the pre-provided dual values.
[0124] At operation 560, the new registration request may be transmitted from the UE 201 to the TN 203. The UE 201 may send a new registration request through the terrestrial access (NG-RAN-TN, TAI-1), again requesting eDRX value (X) and the PTW value (Y). The request may arrive through the TN infrastructure, signalling to the AMF 207 that the TN-appropriate parameters are needed.
[0125] At operation 562, the TN 203 may forward the new registration request to the AMF 207. In a non-limiting example, the terrestrial RAN may forward the registration request to the AMF 207 with the requested eDRX (X) and the PTW (Y) values of the UE 201. The AMF 207 may now process the requested eDRX (X) and the PTW (Y) values as the mobility registration from the UE 201 that may have moved from the NTN 205 to the TN 203.
[0126] At operation 564, the registration accept message with the TN-Appropriate eDRX may be forwarded from the AMF 207 to the UE 201. In a non-limiting example, the AMF 207 may send the registration accept message with the network-provided eDRX (X) and the PTW (Y) values that may now be computed for the TN 203 environment. The registration accept message may be sent without the overhead of satellite unavailability period adjustments. The eDRX (X) and the PTW (Y) values may be optimised for continuous ground-based coverage.
[0127] At operation 566, the UE 201 may apply the TN-Specific eDRX. In a non-limiting example, the UE 201 may apply the newly received eDRX (X) and PTW (Y) values mapped to the TN / NG-RAN RAT. The UE 201 may now monitor the paging channels at the correct, TN-appropriate frequency, avoiding the problem of using excessively long NTN-optimised eDRX cycles in the terrestrial-network as discussed in Figure 5a.
[0128] Figure 6a illustrates a sequence of operations depicting a method 600a in which the PDU session establishment timer mismatch occurs during the NTN-to-TN handover, according to the related art.
[0129] In an embodiment, the UE 201 may be registered with a public land mobile network (PLMN) A via the NTN 205. The NTN 205 may provide the registered TAI list containing both NG-RAN satellite and NG-RAN terrestrial RAT entries, TAI-1 *and TAI-2 →? NTN. The UE 201 may need to establish an emergency PDU session while camped on the NTN 205, and mid-procedure UE 201 may hand over to the TN 203, exposing a timer mismatch problem.
[0130] At operations 602, the UE 201 may be in the 5GMM-registered limited service state while camped on the NTN satellite cell under TAI-2. The TAI-2 state may indicate the UE 201 has completed registration but is only authorised for limited / emergency services. The UE 201 may not have full normal service access. The UE 201 may be configured to maintain a registered TAI list containing both TAI-1 (TN) and TAI-2 (NTN 205).
[0131] At operation 604, the UE 201 may be registered for emergency services. In an implementation, the UE 201 may have successfully registered with the AMF 207 for emergency access through the NTN 205, such that the UE 201 may initiate emergency-related NAS procedures, including the emergency PDU session establishment.
[0132] At operation 606, an upper-layer application or internal logic of the UE 201 may trigger the need for the emergency PDU session. For example, an emergency call or emergency data service may initiate the PDU session establishment procedure at the NAS layer.
[0133] At operation 608, the UE 201 may send the PDU session establishment request message marked as emergency to the NTN 205 via the RRC connection. The PDU session establishment request message may request the NTN 205 to establish the emergency PDU session for the UE 201.
[0134] At operation 610, upon transmitting the PDU session establishment request message, the UE 201 may start timer T3580 with a value of 21 seconds. The timer value may be set according to the NTN 205 environment. The timer T3580 may require longer timer durations to account for the significantly higher round-trip propagation delay inherent in satellite communication (especially GEO satellites) and potential satellite unavailability periods. The standard TN value for T3580 may be 16 seconds, but the NTN 205 may add an extra 5 seconds to accommodate satellite link delays.
[0135] At operation 612, the satellite access node of the NTN 205 may forward the PDU session establishment request message received from the UE 201 to the AMF 207 in the 5G core network via the NG interface. The AMF 207 may begin processing the emergency PDU session establishment request message.
[0136] At operation 614, the timer value of 21 seconds may confirm the running state of timer T3580 at 21 seconds, reflecting the NTN-specific timer configuration. The UE 201 may now be waiting for a response from the NTN 205 within the 21-second window.
[0137] At operation 616, the UE 201 may perform the handover from the NTN 205 (TAI-2) to the TN 203 (TAI-1). Since TAI-1 is already in the registered TAI list of the UE 201, no new registration may be required. The UE 201 may simply transition to the terrestrial NG-RAN cell of the TN 203. The UE 201 may have moved to a fundamentally different radio environment where propagation delays may be orders of magnitude smaller, but the T3580 timer may still be running with the NTN-configured value of 21 seconds.
[0138] At operation 618, after arriving in the TN 203, the UE 201 may continue to wait using the original T3580 value of upto 21 seconds that was configured for the NTN 205. The UE 201 may not adjust or re-evaluate the timer upon changing the RAT type. In the TN 203 environment, the appropriate T3580 value may be only 16 seconds. Thus, the UE 201 may be waiting for an unnecessary extra 5 seconds beyond the requirement of the TN 203.
[0139] At operation 620, the TN 203 may not respond within the T3580 window, for example, due to the handover disrupting the ongoing procedure. Hence, a message loss during the transition may occur, or the AMF 207 may not be able to complete the procedure in time. Further, the timer may expire after the full 21 seconds,i.e.,5 seconds later than the timer would have in the TN 203 scenario.
[0140] At operation 622, the expiration of timer T3580 may occur, where the UE 201 may take recovery action per the NAS specification for T3580 expiry.
[0141] At operation 624, upon T3580 expiry, the UE 201 may either report the EMC failure to the upper layers or retry the emergency PDU session establishment. The retry may happen after 21 seconds instead of the appropriate 16 seconds for the TN 203 environment. Thus, the 5-second delay in the emergency service recovery may be significant. For instance, in life-threatening emergency scenarios, every second counts, and the UE 201 may be unnecessarily delayed because of the carryover of the NTN timer value into the TN 203.
[0142] Hence, the UE 201 may not adapt the NAS timer T3580 when transitioning between the NTN 205 and TN RAT types mid-procedure. The UE 201 may blindly continue with the NTN-configured value. Further, the extra 5 seconds of delay before the emergency PDU session recovery in the TN 203 may directly affect the emergency service availability.
[0143] Further to overcome the above problem, as depicted in Figure 6a, the solution is provided in the forthcoming paragraph while explaining Figure 6b.
[0144] Figure 6b illustrates a sequence of operations depicting a method 600b to overcome the PDU session establishment timer mismatch occurring during the NTN-to-TN handover, according to implementations of the present disclosure.
[0145] In one embodiment, as illustrated in Figure 6b, operations 632-638 relate to the transmission of the PDU session establishment request message from the UE 201 to the NTN 205, as explained in reference to operations 602-608 (shown in Fig. 6a), respectively. Accordingly, a detailed description of the operations 632-638 has been omitted for the sake of brevity.
[0146] At operation 640, the PDU session establishment request message may be forwarded from the NTN 205 to the AMF 207.
[0147] At operation 642, the timer T3580 may be initiated for 21 seconds. The timer T3580 may correspond to the NTN timer value, longer than the TN value (i.e.,16 seconds) to account for satellite propagation delays.
[0148] At operation 644, the timer T3580 for 21 seconds may be running at the UE 201.
[0149] At operation 646, the UE 201 may transit from the NTN 205 (TAI-1) to the TN 203 (TAI-2) and perform the handover. Since the TAI-2 may be in the current registered TAI list, no new registration may be required. The UE 201 may now be on the NG-RAN terrestrial cell of the TN 203. However, the PDU establishment procedure may still be ongoing with the old NTN timer value. The UE 201 may set the timer value to the new RAT (TN 203).
[0150] At operation 648, the UE 201 may detect being now on the TN 203 and adjust T3580 from 21s down to the standard timer value of 16 seconds corresponding to the NT 203.
[0151] At operation 650, the timer value corresponding to the T3580 may be 16 seconds, which may be the remaining wait governed by the TN timer.
[0152] At operation 652, the PDU establishment accept (Emergency) message may be received from the network. In an implementation, the UE 201 may get the emergency service ~5 seconds earlier than if the UE 201 kept waiting with the 21-second NTN timer.
[0153] At operation 654, instead of the fixed 16 seconds, the UE 201 may adjust the timer T3580 to a configurable X seconds. The timer adjustment may allow operators to fine-tune the difference between RAT timer values.
[0154] At operation 656, the UE 201 may wait until the timer T3580 with the configurable value X expires.
[0155] At operation 658, the PDU establishment accept (Emergency) message may be received by the UE 201. In an advantageous aspect, the flexibility to balance between waiting too long and timing may be eliminated prematurely.
[0156] At operation 660, the UE 201 may abort the ongoing PDU procedure entirely and initiate a new PDU establishment request (Emergency) message on the TN cell.
[0157] At operation 662, the new PDU establishment request (Emergency) message may be forwarded to the AMF 207 via the TN 203.
[0158] At operation 664, the timer T3580 may be initiated fresh with the correct TN timer value.
[0159] At operation 666, the PDU establishment accept (Emergency) message may be received by the UE 201.
[0160] At operation 668, the UE 201 may get the emergency service in ~6 seconds earlier than the emergency service availed through the method 600a as referred to in Figure 6a, where the UE 201 may have waited the full 21 seconds and potentially timed out. In an advantageous aspect, the UE 201 may recognise the RAT change after handover and adapt accordingly, ensuring faster emergency service delivery in the TN 203.
[0161] Figure 7a illustrates a sequence of operations depicting a method 700a in which the registration accept timer is not adjusted during the TN-to-NTN handover, according to the related art.
[0162] At operation 702, the UE 201 may begin in the 5GMM-IDLE state.
[0163] At operation 704, the UE 201 may transition to the 5GMM-registered normal service.
[0164] At operation 706, the UE 201 may already be registered with the PLMN A and hold the registered TAI list containing both TAI-1 (mapped to the TN 203) and TAI-2 (mapped to the NTN 205).
[0165] At operation 708, the periodic registration timer T3512 may be running, which may eventually trigger the UE 201 to perform a periodic registration update.
[0166] At operation 710, when the timer T3512 expires, the UE 201 may initiate the periodic registration request message. The UE 201 may transmit the periodic registration request message via RRCConnectionSetupComplete to the TN 203.
[0167] At operation 712, the TN 203 may forward the periodic registration request message to the AMF 207.
[0168] At operation 714, upon transmitting the periodic registration request message, the UE 201 may enter the 5GMM-registered initiated substate.
[0169] At operation 716, the UE-side timer T3510 may begin guarding the registration procedure from the perspective of the UE 201.
[0170] At operation 716, the AMF 207 may process the periodic registration request message.
[0171] At operation 718, the AMF 207 may transmit the registration accept message back toward the UE 201 via the TN 203.
[0172] At operation 720, the AMF 207 may initiate a timer T3550 (a registration accept timer) with a value of 6 seconds (720) simultaneously with the transmission of the registration accept. The timer T3550 may be the network-side timer that guards the registration procedure. The AMF 207 may expect to receive the registration complete message from the UE 201 before the timer T3550 expires.
[0173] At operation 722, before the registration accept message reaches the UE 201, the UE 201 may be handed over from the TN cell (TAI-1) to the NTN satellite cell (TAI-2) via handover. Since TAI-2 may be within the current registered TAI list of the UE 201, no new registration may be triggered. Thus, the UE 201 may simply continue waiting for the registration accept message on the new NTN link.
[0174] At operation 724, the registration accept message may be delivered to the UE 201 through the NTN 205, which may introduce significantly higher propagation delay compared to TN 203.
[0175] At operation 726, the AMF 207 may still run the timer of 6 seconds instead of 11 seconds.
[0176] At operation 728, the UE 201 may successfully receive the registration accept message and transmit a registration complete message back to the NTN 205, but the response must now travel the longer NTN satellite path back to the NTN 205.
[0177] At operation 730, the timer T3550 may expires prematurely, while the AMF 207 may be still running the T3550 at the original 6-second value, which was appropriate for the low-latency TN path. However, the round trip may now involve the high-latency NTN satellite link. The AMF 207 may not have adjusted the timer T3550 to a longer value (e.g., 11 seconds) to accommodate the satellite propagation delay. As a result, the timer T3550 expires before the registration complete message from the UE201 can reach the AMF 207.
[0178] At operation 730, the AMF 207 may interpret the expiry as a failure and abnormally retransmit the registration accept message even though the UE 201 may have already successfully processed and sent the registration complete message.
[0179] Hence, unnecessary retransmission may waste the network resources, causing redundant signalling over the satellite link, and may lead to a confusion state between the UE 201 and the AMF 207. The same problem may occur in the reverse direction when the UE 201 moves from the NTN 205 to the TN 203. Thus, the timer mismatch may happen whenever the RAT type changes mid-procedure, and the network may not adapt the timer accordingly. The same scenario may be applied broadly to a PDU modification procedure and a PDU release procedure that may use similar network-side guard timers.
[0180] Further to overcome the above problem, as depicted in Figure 7a, the solution is provided in the forthcoming paragraph while explaining Figure 7b.
[0181] Figure 7b illustrates a sequence of operations depicting a method 700b for adjusting the timer to overcome the registration accept timer mismatch occurring during the TN-to-NTN handover, according to implementations of the present disclosure.
[0182] In one embodiment, as illustrated in Figure 7b, operations 742-746 relate to the UE 201 registration, as explained in reference to operations 602-606 (shown in Fig. 7a), respectively. Accordingly, a detailed description of the operations 742-746 has been omitted for the sake of brevity.
[0183] At operation 748, the UE 201 may initiate the periodic registration procedure by sending the registration request via RRCConnectionSetupComplete to the TN 203.
[0184] At operation 750, the TN 203 may forward the registration request via RRCConnectionSetupComplete to the AMF 207.
[0185] At operation 752, the UE 201 may enter the 5GMM-registered initiated substate.
[0186] At operation 754, the UE-side guard timer T3510 may be initiated.
[0187] At operation 756, the AMF 207 may process the periodic registration and send the registration accept message to the UE 201 via the TN 203.
[0188] At operation 758, the AMF 207 may initiate the timer T3550 with an initial value of 6 seconds, which may be appropriate for the low-latency terrestrial path.
[0189] At operation 760, the handover from the TN 203 to the NTN 205 may take place. The AMF 207 may adjust the timer to the current RAT type.
[0190] In an embodiment, at operation 762, the AMF may adjust the timer T3550 from 6 seconds to 11 seconds, accounting for the additional propagation delay introduced by the GEO satellite link.
[0191] At operation 764, the adjusted timer value T3550 = 11 seconds may now provide a sufficient time for the round trip over the satellite path.
[0192] At operation 766, the registration accept message may be delivered to the UE 201 via the NTN 205. The UE 201 may successfully process the registration accept message.
[0193] At operation 768, the UE 201 may send the registration complete message back through the NTN 205.
[0194] At operation 768, because the timer T3550 may have extended to 11 seconds, the AMF 207 may receive the registration complete message well within the timer window, eliminating the premature expiry and the abnormal retransmission.
[0195] In another embodiment, at operation 772, the AMF may adjust the timer T3550 to the configurable value of X seconds instead of using a fixed adjustment. The configurable value may be a network-operator-defined parameter that may be tuned based on the specific satellite constellation characteristics (e.g., GEO vs. LEO vs. MEO orbit altitude and corresponding delay). The adjusted timer T3550 = X seconds may provide flexibility for different deployment scenarios.
[0196] At operation 774, the NTN 205 may forward the registration accept message to the UE 201.
[0197] At operation 776, the UE 201 may respond with the registration complete message to the NTN 205.
[0198] At operation 778, the AMF 207 may receive the registration complete message from the NTN 205 within the configurable timer window. In an advantageous aspect, the present approach may give the operators a provision to optimise the timer value based on their specific NTN deployment parameters.
[0199] Thus, the AMF guard timer may accommodate the higher latency of the satellite link, preventing the premature T3550 expiry and unnecessary retransmission as discussed in Figure 7a. The fixed adjustment (operations 762-770) may be simpler to implement, while the configurable adjustment (operations 772-778) may offer greater flexibility across the diverse NTN 205 deployments. In an implementation, the same solution may be applicable in the reverse direction when the UE 201 moves from the NTN 205 to the TN 203. In the reverse direction, the AMF 207 may similarly need to adjust T3550 to match the new (shorter) propagation characteristics of the terrestrial link. The method 700b may also be extended to other NAS procedures that may rely on network-side guard timers, including the PDU session modification and the PDU session release.
[0200] In an implementation, the timer T3525 may not be adjusted after the NTN-to-TN handover during a service request retry. In an implementation, the timer inefficiency may occur when the UE 201 transitions from the NTN 205 to the TN 203 while the service request retry timer T3525 is actively running. The UE 201 may be registered for the normal service in the NTN cell (LEO or GEO satellite) under the PLMN A. The network may have provided the UE 201 with the registered TAI list that may include both TAI-1 (mapped to TN, the terrestrial NG-RAN cell) and TAI-2 (mapped to NTN, the satellite NG-RAN cell). The UE 201 may currently be camped on the NTN cell in 5GMM-IDLE mode. While in idle mode, uplink data may become pending at the UE 201, triggering the need for a service request procedure to re-establish the signalling connection. The UE 201 may attempt the service request procedure, but UE 201 may fail repeatedly. In an implementation, the UE 201 may try 5 times without success. After exhausting these attempts, the UE 201 may start the timer T3525 with a value of 72 seconds. The timer T3525 may be a back-off timer that may be governed when the UE 201 is allowed to retry the service request procedure. As a result, the UE 201 may have to wait for T3525 to expire before initiating another service request attempt. The 72-second value may be configured for the NTN 205 environment, reflecting the higher latency and longer round-trip times inherent in satellite communication links. While the timer T3525 is still running, the UE 201 may move from the NTN cell (TAI-2) to the TN cell (TAI-1). Since TAI-1 is within the current Registered TAI list of the UE 201, no new registration may be triggered. The UE 201 may simply continue operating on the TN cell. However, critically, the UE 201 may not adjust the running T3525 timer to reflect the new RAT type.
[0201] The unnecessary waiting time may prevail. The TN cell may operate with significantly lower propagation delay compared to the NTN satellite link. In the TN 203 environment, the appropriate T3525 value may be around 60 seconds (or even shorter), not the 72 seconds configured for NTN. Because the UE 201 may not adjust T3525 after the handover, and continue counting down from the original 72-second NTN value. Thus, even though the UE 201 may have already been waiting and may reasonably take T3525 expiry actions at the 60th second (the TN-appropriate duration). The UE 201 may instead wait for an additional 12 seconds unnecessarily before the timer expires and retry the service request. Thus, the extra 12 seconds of idle waiting may be translated directly into delayed uplink data delivery for the operator or a user.
[0202] In an embodiment, as a solution to the problem described above, the UE 201 may be registered for the normal service in NTN (LEO / GEO) under the PLMN A, with the registered TAI list covering both TAI-1 (TN) and TAI-2 (NTN). The UE 201 may be camped on the TAI-2 in 5GMM-IDLE mode. When uplink data arrives, the UE 201 may attempt the service request procedure, which may fail after 5 retries. The UE 201 may start backoff timer T3525 at 72 seconds (the NTN-appropriate value), barring further SR attempts until expiry. While T3525 is still running, the UE 201 may handover from the NTN cell (TAI-2) to the TN cell (TAI-1). Since TAI-1 is in the registered TAI list, no re-registration may be required. Upon detecting the RAT change to the TN, the UE 201 may adjust T3525 from 72 seconds down to the value suited to terrestrial latency, for example, 60 seconds. When the adjusted timer expires, the UE 201 may immediately retrigger the service request over the TN, recovering the uplink data path up to 12 seconds earlier than the unadjusted NTN timer would have allowed. In an implementation, the same solution apply symmetrically when the UE 201 moves from the TN 203 to the NTN 205. Accordingly, the timer T3525 may be adjusted upward (e.g., 60 to 72 seconds) to prevent premature retries over the higher-latency satellite link. The same adaptive principle may be extended to a RAT-dependent NAS backoff or guard timer running during the inter-RAT handover.
[0203] Figure 8illustrates a process flow of a method 800 performed by the UE 201 for adjusting timers while switching between the TN and the NTN during mobility, in accordance with one or more embodiments of the disclosure.
[0204] In an embodiment, at step 802, the method 800 may include transmitting the signalling message to the network via the first RAT. The first RAT may be, but not limited to, one of the TN 203 and the NTN 205.
[0205] At step 804, the method 800 may include initiating the first timer with the transmission of the signalling message. The first timer may have a first timer value specified for accessing the first RAT.
[0206] At step 806, the method 800 may include detecting, during the transmission of the signalling message, the mobility event from the first RAT to a second RAT having a second timer value specified for accessing the second RAT. The second RAT may be the other of the TN and the NTN. Further, the first RAT and the second RAT may have different round-trip time characteristics.
[0207] At step 808, the method 800 may include adjusting the first timer while switching between the TN 203 and the NTN 205 in response to the detected mobility event of the UE 201. In an implementation, the timer may be adjusted by restarting the first timer with the second timer value corresponding to the second RAT. The second timer value may be a predefined timer value for the second RAT. In another implementation, the timer may be adjusted by adjusting the first timer to the configurable timer value (X) based on the switching between the TN 203 and the NTN 205. In another implementation, the timer may be adjusted by aborting the transmission of the signalling message, thereby initiating a new signalling message on the second RAT with the second timer value corresponding to the second RAT.
[0208] In an embodiment, the configurable timer value (X) may be determined using a statistical method using past timer iterations performed by the UE. In another implementation, an artificial intelligence model is trained based on one or more features. The one or more features may include signal conditions for predicting delay, retransmissions, and signalling success probability associated with the signalling message, the current RAT type, a targeted RAT type, the RTT, and one or more cell offset parameters. The RTT may indicate a signalling exchange for avoiding premature expiry. The one or more cell offset parameters may correspond to biasing and stabilising decisions associated with the mobility.
[0209] In an embodiment, the configurable timer value (X) may be determined using received configuration information for adjusting the first timer. The determination may be based on the first timer value being less than a cell offset value (Kcell_Offset). In another implementation, the determination may be based on the Kcell_Offset indicating the adjustment to one of the timing and measurement associated with the signalling message. In another implementation, the determination may be based on the first timer value being less than the TA value. In another implementation, the determining may be based on the first timer value being less than a sum of the cell offset value and a round-trip time, wherein the round-trip time could be estimated as twice the TA.
[0210] In an embodiment, the first timer may be adjusted to the configured timer value (X) that may be greater than or equal to the first timer value, being one of greater than or equal to the Kcell_offset. In another implementation, the first timer may be adjusted to the first timer value being either greater than or equal to the Kcell_offset minus KUE_offset. In a non-limiting example, the KUE_offset may be a network configurable parameter with a non-zero value. In another implementation, the first timer may be adjusted to the first timer value combined with a cell offset value (Kcell_Offset) and a weighted round-trip time. The weight may include either an integer value or a decimal value.
[0211] In an embodiment, the first timer value may be greater than the second timer value when the first RAT is associated with the NTN 205 and the second RAT is associated with the TN 203.
[0212] In another embodiment, the first timer value may be less than the second timer value when the first RAT is associated with the TN 203 and the second RAT is associated with the NTN 205.
[0213] In an embodiment, the method 800 may include receiving the paging message in the TA corresponding to one of the TN 203 and the NTN 205 in response to the transmitted signalling message. The paging message may be received in accordance with the PTV selected based on the RAT type of the TA.
[0214] In an embodiment, the method 800 may include transmitting the signalling message corresponding to the registration request message to the network (i.e.,TN 203, or the NTN 205). The registration request message may include the requested eDRX value. Further, the method 800 may include receiving the registration accept message from the network in response to the transmitted registration request message to the network. The registration accept message may include the first eDRX value corresponding to the TN 203 and the second eDRX value corresponding to the NTN 205. In an implementation, the registration accept message may further include a first PTW value for the TN 203 and a second PTW value for the NTN 205. The first PTW value may be applied in response to the mobility event of the UE 201 from the NTN 205 to the TN 203. Furthermore, the method 800 may include applying the second eDRX value while the UE 201 may be connected to the NTN 205. Additionally, the method 800 may include detecting the mobility event of the UE 201 from the NTN 205 to the TN 203. Accordingly, the first timer may be adjusted by applying the first eDRX value in response to the detected mobility event of the UE 201 from the NTN 205 to the TN 203.
[0215] In an embodiment, the method 800 may include initiating a mobility registration request message to the network upon a change in the RAT from the TN 203 to the NTN 205, and the UE 201 may be configured with the eDRX value associated with the TN 203. The registration request message may include the requested eDRX value for the NTN 205. Further, the registration accept message from the network may be received in response to the transmitted registration request message to the network. The registration accept message may include the eDRX value corresponding to the NTN 205.
[0216] In an embodiment, the method 800 may include initiating the mobility registration request message to the network upon a change in the RAT from the NTN 205 to the TN 203, and the UE 201 may be configured with the eDRX value associated with the NTN 205. The registration request message may include the requested eDRX value for the TN 203.
[0217] In an embodiment, the method 800 may include receiving the registration accept message from the network in response to the transmitted registration request message to the network. The registration accept message may include the eDRX value corresponding to the TN 203. In an implementation, the signalling message may include the NAS signalling message. The first timer may include at least one of a registration request timer (T3510), a mobility management timer (T3517), a timer associated with a UE 201 subscription (T3525), the PDU session establishment request timer (T3580), a PDU session modification timer (T3581), a PDU session release timer (T3582), and an authentication response timer (T3520). In another implementation, the signalling message may include the RRC signalling message. The first timer may include at least one of a connection setup timer (T300), a RRC connection re-establishment request timer (T301), a critical RRC supervisory timer (T304), a critical RRC timer (T310), a RRC connection re-establishment timer after a radio link failure (RLF) (T311), and a connection resume timer (T319). In another implementation, the signalling message may include an IMS signalling message. The first timer may include at least one of a session initiation protocol (SIP) (SIP T1 and SIP T2), a registration timer, a transaction timeout timer for non-INVITE requests (Timer F), a session timer, a signalling compression timer, and an emergency registration timer. In another implementation, the signalling message may include other timers corresponding to the signalling messages and IP messages corresponding to Layer 2 and Layer 1 of the 3GPP access and non-3GPP access.
[0218] Figure 9 illustrates the UE 201 for adjusting timers while switching between the TN 203 and the NTN 205 during mobility, in accordance with one or more embodiments of the disclosure.
[0219] In an embodiment, the UE 201 may include a processor 902, a memory 904, and a transceiver 906. By way of example, the UE 201 may be a cellular phone or other device that communicates over a plurality of cellular networks (such as a 3G, 4G, 5G or pre-5G, 6G network or any future wireless communication network). The transceiver 906 may perform functions for transmitting and receiving signals via a wireless channel. The transceiver 906 may be configured to communicate with the TN 203 and the NTN 205. The processor 902 may be in communication with the transceiver 906 and the memory 904.
[0220] As an example, the processor 902 may be a single processing unit or several units, all of which could include multiple computing units. The processor 902 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and / or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor 902 is configured to fetch and execute computer-readable instructions and data stored in the memory. The processor 902 may include one or a plurality of processors. At this time, one or a plurality of processors 902 may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an AI-dedicated processor such as a neural processing unit (NPU). The one or a plurality of processors 902 may control the processing of the input data in accordance with a predefined (or alternatively, given) operating rule or artificial intelligence (AI) model stored in the non-volatile memory and the volatile memory, e.g., memory 904. The predefined (or alternatively, given) operating rule or artificial intelligence model is provided through training or learning.
[0221] The memory 904 may include any non-transitory computer-readable medium known in the art, including, for example, volatile memory, such as Static Random Access Memory (SRAM) and Dynamic Random Access Memory (DRAM), and / or non-volatile memory, such as Read-Only Memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.
[0222] In an embodiment, the processor 902 may control the processing of the timer adjustment in accordance with a predefined operating rule or an AI model (not shown in Figure) stored in the non-volatile memory and the volatile memory. The predefined operating rule or AI model may be provided through training or learning. Here, being provided through learning means that, by applying learning techniques to learning data, a predefined operating rule or AI model of the desired characteristic may be prepared. The learning may be performed in the UE 201 itself, in which AI may be performed, and / or may be implemented through a separate server / system. The learning technique is a method for training a predetermined target device using a plurality of learning data to cause, allow, or control the target device to decide or predict. Examples of learning techniques include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning. The AI model may consist of a plurality of neural network layers. Each layer has a plurality of weight values and performs a layer operation through a calculation of a previous layer and an operation of a plurality of weights. Examples of neural networks include, but are not limited to, convolutional neural networks (CNNs), deep neural networks (DNNs), recurrent neural networks (RNNs), restricted boltzmann machine (RBMs), deep belief networks (DBNs), bidirectional recurrent deep neural networks (BRDNNs), generative adversarial networks (GANs), and deep Q-networks.
[0223] In an embodiment, the processor 902 may be configured to transmit the signalling message to the network via the RAT. The first RAT may be, but not limited to, one of the TN 203 and the NTN 205. Further, the processor 902 may be configured to initiate the first timer with the transmission of the signalling message. The first timer may have the first timer value specified for accessing the first RAT. Additionally, the processor 902 may be configured to detect, during the transmission of the signalling message, the mobility event from the first RAT to the second RAT having the second timer value specified for accessing the second RAT. The second RAT may be the other of the TN 203 and the NTN 205. The first RAT and the second RAT may have different RTT characteristics. Furthermore, the processor 902 may be configured to adjust the timer while switching between the TN 203 and the NTN 205 in response to the detected mobility event of the UE 201. The processor 902 may be configured to adjust the timer by restarting the first timer with the second timer value specified for accessing the second RAT. In another implementation, the processor 902 may be configured to adjust the timer by adjusting the first timer to a configurable timer value. In another implementation, the processor 902 may be configured to adjust the timer by aborting the transmission of the signalling message, thereby initiating the new signalling message on the second RAT.
[0224] Figure 10 illustrates a network-entity 209 for adjusting timers while switching between the TN 203 and the NTN 205 during mobility, in accordance with one or more embodiments of the disclosure.
[0225] In an embodiment, the network-entity 209 may include a processor 1002, a memory 1004 and a communication interface 1006 (e.g., communicator or communication interface). The communication interface 1006 may be configured to communicate with the UE 201 via the TN 203 and the NTN 205. The processor 1002 may be coupled to the communication interface 1006 and the memory 1004. The UE 201 may be implemented in the network-entity 209 (e.g., the network). The communication unit 1006 may perform one or more functions for transmitting and receiving signals via a wireless channel.
[0226] As an example, the processor 1002 may be a single processing unit or a number of units, all of which could include multiple computing units. The processor 1002 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and / or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor 1002 is configured to fetch and execute computer-readable instructions and data stored in the memory. The processor 1002 may include one or a plurality of processors. The processor 1002 may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an AI-dedicated processor such as a neural processing unit (NPU). The processor 1002 may control the processing of the input data in accordance with a predefined (or alternatively, given) operating rule or artificial intelligence (AI) model stored in the non-volatile memory and the volatile memory, e.g., the memory 1004. The predefined (or alternatively, given) operating rule or artificial intelligence model is provided through training or learning.
[0227] The memory 1004 may include any non-transitory computer-readable medium known in the art, including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and / or non-volatile memory, such as read-only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and / or magnetic tapes.
[0228] In an embodiment, the processor 1002 may be configured to receive the signalling message to the UE 201 via the first RAT. Further, the processor 1002 may be configured to initiate the first timer upon the reception of the signalling message. The first timer may have the first timer value specified for accessing the first RAT.
[0229] In an embodiment, the network-entity 209 may include the AMF, and wherein the first timer may include at least one of the registration accept timer (T3550), an authentication request timer (T3560), a deregistration request timer (T3522), a back-off timer (T3565 and T3575), a registration reject timer (T3570), a paging timer (T3513), a configuration update timer (T3555), a NAS signalling connection release timer (T3591), and the like.
[0230] Furthermore, the processor 1002 may be configured to detect, during the reception of the signalling message, that the UE 201 may have performed the mobility event from the first RAT to the second RAT. Additionally, the processor 1002 may be configured to adjust the timer in response to the mobility event by restarting the first timer with a second timer value specified for accessing the second RAT. In another implementation, the processor 1002 may be configured to adjust the timer in response to the mobility event by adjusting the first timer to the configurable timer value (X). In another implementation, the processor 1002 may be configured to adjust the timer in response to the mobility event by stopping the first timer and thereby waiting for the new signalling message from the UE 201.
[0231] In an embodiment, the processor 1002 may be configured to determine that the registration area associated with the UE 201 includes the first tracking area corresponding to the TN 203 and the second tracking area corresponding to the NTN 205. Further, the processor 1002 may be configured to initiate the paging procedure for the UE 201 corresponding to the received signalling message. Furthermore, the processor 1002 may be configured to select the paging timer indicating the PTV based on the RAT type of the tracking area in which the paging is transmitted. Additionally, the processor 1002 may be configured to adjust the timer based on one of retransmitting the paging, and determining that the UE 201 is not reachable upon expiry of the first timer without receiving a paging response from the UE.
[0232] In another advantageous aspect, the present disclosure provides RTT-aware timer adaptation that ensures reliable mobility across both radio-access and core-network signalling layers in the TN 203 and the NTN 205. Such timer adaptation avoids NAS procedure failures during transitions between the TN 203 and the NTN 205 that may otherwise arise due to RAT-specific timer dependencies. Further, the present disclosure reduces the likelihood of paging misses in eDRX / DRX operation, particularly in the NTN 205. Further, by aligning timer values with the applicable propagation delay and the RTT characteristics, the present disclosure reduces signalling overhead and unwanted retransmissions, thereby maintaining service quality while preventing resource waste. In addition, the present disclosure enables faster establishment of emergency services by avoiding unnecessary waiting times caused by misaligned timers, and it optimizes UE power consumption by applying appropriate timer values for the serving RAT.
[0233] While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person in the art, various working modifications may be made to the method to implement the inventive concept as taught herein. The drawings and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein.
Claims
1.A method (800) performed by a user equipment (UE) for adjusting timers while switching between Terrestrial-network (TN) and Non-terrestrial-network (NTN) during mobility, the method (800) comprising:transmitting (802) a signalling message to a network via a first radio access technology (RAT), wherein the first RAT is one of the TN and the NTN;initiating (804) a first timer with the transmission of the signalling message, wherein the first timer has a first timer value specified for accessing the first RAT;detecting (806), during the transmission of the signalling message, a mobility event from the first RAT to a second RAT having a second timer value specified for accessing the second RAT, wherein the second RAT is the other of the TN and the NTN, and wherein the first RAT and the second RAT have different round-trip time characteristics; andadjusting (808) the first timer while switching between the TN and the NTN in response to the detected mobility event of the UE.2.The method (800) as claimed in claim 1, wherein adjusting (808) the timer comprises one of:restarting the first timer with the second timer value corresponding to the second RAT, wherein the second timer value is a predefined timer value for the second RAT.adjusting the first timer to a configurable timer value based on the switching between the TN and the NTN; andaborting the transmission of the signalling message, thereby initiating a new signalling message on the second RAT with the second timer value corresponding to the second RAT.3.The method (800) as claimed in claim 2, wherein adjusting (808) the timer comprises adjusting the first timer to the configurable timer value based on the switching between the TN and the NTN, and wherein the configurable timer value is determined using at least one of:a statistical method using past timer iterations performed by the UE; andan artificial intelligence model trained based on one or more features comprising:signal conditions for predicting delay, retransmissions, and signalling success probability associated with the signalling message,a current RAT type,a targeted RAT type,a round-trip time indicating a signalling exchange for avoiding premature expiry, andone or more cell offset parameters corresponding to biasing and stabilising decisions associated with the mobility.4.The method (800) as claimed in claim 1, further comprising:determining a configurable timer value using a received configuration information for adjusting the first timer, wherein the determining is based on at least one of:the first timer value being less than a cell offset value (Kcell_Offset), wherein the Kcell_Offset indicates an adjustment to one of timing and measurement associated with the signalling message;the first timer value being less than the TA value, andthe first timer value being less than a sum of the cell offset value and a round-trip time, wherein the round-trip time could be estimated as twice TA.5.The method (800) as claimed in claim 1, wherein the adjusting (808) comprises adjusting the first timer to a configured timer value that is one of greater than or equal to at least one of:the first timer value being one of greater than or equal to Kcell_offset;the first timer value being one of greater than or equal to Kcell_offset minus KUE_offset, where KUE_offset is a network configurable parameter with a non-zero value; andthe first timer value is combined with a cell offset value (Kcell_Offset), and a weighted round-trip time, where weight comprises at least one of an integer value and a decimal value.6.The method (800) as claimed in claim 1, wherein the first timer value is greater than the second timer value when the first RAT is associated with the NTN and the second RAT is associated with the TN.7.The method (800) as claimed in claim 1, wherein the first timer value is less than the second timer value when the first RAT is associated with the TN and the second RAT is associated with the NTN.8.The method (800) as claimed in claim 1, further comprising receiving a paging message in a tracking area corresponding to one of the TN and the NTN in response to the transmitted signalling message, wherein the paging message is received in accordance with a paging timer value selected based on a RAT type of the tracking area.9.The method (800) as claimed in claim 1, further comprising:transmitting the signalling message corresponding to a registration request message to the network, wherein the registration request message includes a requested extended discontinuous reception (eDRX) value;receiving a registration accept message from the network in response to the transmitted registration request message to the network, wherein the registration accept message includes a first eDRX value corresponding to the TN and a second eDRX value corresponding to the NTN;applying the second eDRX value while the UE is connected to the NTN;detecting the mobility event of the UE from the NTN to the TN; andadjusting the first timer by applying the first eDRX value in response to the detected mobility event of the UE from the NTN to the TN.10.The method (800) as claimed in claim 9, wherein the registration accept message further comprises a first paging time window (PTW) value for the TN and a second PTW value for the NTN, wherein the first PTW value is applied in response to the mobility event of the UE from the NTN to the TN.11.The method (800) as claimed in claim 1, further comprising:initiating a mobility registration request message to the network upon a change in the RAT from the TN to the NTN, and the UE is configured with an extended discontinuous reception (eDRX) value associated with the TN, wherein the registration request message comprises a requested eDRX value for the NTN;receiving a registration accept message from the network in response to the transmitted registration request message to the network, wherein the registration accept message comprises the eDRX value corresponding to the NTN.12.The method (800) as claimed in claim 1, further comprising:initiating a mobility registration request message to the network upon a change in the RAT from the NTN to the TN, and the UE is configured with an extended discontinuous reception (eDRX) value associated with the NTN, wherein the registration request message comprises a requested eDRX value for the TN;receiving a registration accept message from the network in response to the transmitted registration request message to the network, wherein the registration accept message comprises the eDRX value corresponding to the TN.13.The method (800) as claimed in claim 1, wherein the signalling message comprises one of:a non-access stratum (NAS) signalling message, and wherein the first timer comprises at least one of a registration request timer (T3510), a mobility management timer (T3517), a timer associated with a UE subscription (T3525), a packet data unit (PDU) session establishment request timer (T3580), a PDU session modification timer (T3581), a PDU session release timer (T3582), and an authentication response timer (T3520);a radio resource control (RRC) signalling message, and wherein the first timer comprises at least one of a connection setup timer (T300), a RRC connection re-establishment request timer (T301), a critical RRC supervisory timer (T304), a critical RRC timer (T310), a RRC connection re-establishment timer after a radio link failure (RLF) (T311), and a connection resume timer (T319) ;an IP multimedia subsystem (IMS) signalling message, and wherein the first timer comprises at least one of a session initiation protocol (SIP) (SIP T1 and SIP T2), a registration timer, transaction timeout timer for non-INVITE requests (Timer F), session timer, signalling compression timer, and emergency registration timer; andother timers corresponding to the signalling messages and internet protocol (IP) message corresponding to Layer 2 and Layer 1 of a 3rd Generation Partnership Project (3GPP) access and non-3GPP access.14.A user equipment (UE) (900) for adjusting timers while switching between Terrestrial-network (TN) and Non-terrestrial-network (NTN) during mobility, the UE (900) comprising:a transceiver (906) configured to communicate with the TN and the NTN; anda processor (902) coupled to the transceiver (906) and a memory (904), the processor (902) configured to:transmit a signalling message to a network via a first radio access technology (RAT), wherein the first RAT is one of the TN and the NTN;initiate a first timer with the transmission of the signalling message, wherein the first timer has a first timer value specified for accessing the first RAT,detect, during the transmission of the signalling message, a mobility event from the first RAT to a second RAT having a second timer value specified for accessing the second RAT, wherein the second RAT is the other of the TN and the NTN, and wherein the first RAT and the second RAT have different round-trip time characteristics, andadjust the timer while switching between the TN and the NTN in response to the detected mobility event of the UE.15.The UE (201) as claimed in claim 14, wherein to adjust the timer, the processor (902) is configured to one of:restart the first timer with the second timer value specified for accessing the second RAT,adjust the first timer to a configurable timer value, andabort the transmission of the signalling message, thereby initiating a new signalling message on the second RAT.16.A network-entity (209) for adjusting timers while switching between Terrestrial-network (TN) and Non-terrestrial-network (NTN) during mobility, the network-entity (209) comprising:a communication interface (1006) configured to communicate with a user equipment (UE) (201) via the TN and the NTN; anda processor (10020 coupled to the communication interface (1006) and a memory (1004), the processor (1002) configured to:receive a signalling message to the UE via a first radio access technology (RAT);initiate a first timer with the reception of the signalling message, wherein the first timer has a first timer value specified for accessing the first RAT;detect, during the reception of the signalling message, that the UE has performed a mobility event from the first RAT to a second RAT; andadjust the timer in response to the mobility event by performing at least one of:restarting the first timer with a second timer value specified for accessing the second RAT,adjusting the first timer to a configurable timer value, andstopping the first timer and thereby waiting for a new signalling message from the UE.17.The network-entity (209) as claimed in claim 16, wherein the processor (1002) is configured to:determine that a registration area associated with the UE includes a first tracking area corresponding to the TN and a second tracking area corresponding to the NTN;initiate a paging procedure for the UE corresponding to the received signalling message;select a paging timer indicating a paging timer value based on a RAT type of a tracking area in which the paging is transmitted; andadjust the timer based on one of:retransmitting the paging, anddetermining that the UE is not reachable upon expiry of the first timer without receiving a paging response from the UE.18.The network-entity (209) as claimed in claim 16, wherein the network-entity (209) comprises an access and mobility management function (AMF), and wherein the first timer comprises at least one of a registration accept timer (T3550), an authentication request timer (T3560), a deregistration request timer (T3522), a back-off timer (T3565 and T3575), a registration reject timer (T3570), a paging timer (T3513), a configuration update timer (T3555), and a non-access stratum (NAS) signalling connection release timer (T3591).
