System and method for managing mobility of a user equipment (UE) in a network
The UE-based predictive RNA update mechanism in NTNs uses satellite ephemeris and velocity data to optimize RNA updates, reducing inefficiencies and conserving battery life while maintaining network efficiency.
Patent Information
- Application Number
- PCT/IN2026/050789
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-08
- Filing Date
- 2026-05-07
- Publication Date
- 2026-11-12
AI Technical Summary
Conventional mobility management techniques in Non-Terrestrial Networks (NTNs) lead to frequent and unnecessary RNA updates due to the dynamic nature of satellite movements, causing inefficiencies in signaling, power consumption, and resource utilization.
A UE-based predictive RNA update mechanism that utilizes satellite ephemeris data and UE velocity measurements to estimate RNA boundary crossings, initiating updates only when necessary, with a dynamically adjustable hysteresis threshold to minimize redundant signaling and optimize power consumption.
Reduces unnecessary RNA updates, conserves UE battery life, minimizes network signaling overhead, and enhances mobility robustness by proactively managing RNA updates, thus improving network efficiency and resource utilization.
Smart Images

Figure IN2026050789_12112026_PF_FP_ABST
Abstract
Description
SYSTEM AND METHOD FOR MANAGING MOBILITY OF A USER EQUIPMENT (UE) IN A NETWORK RESERVATION OF RIGHTS
[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD
[0002] The present disclosure relates generally to the field of telecommunications. In particular, the present disclosure relates to a system and a method for managing mobility of a User Equipment (UE) operating in a network.DEFINITIONS
[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used indicates otherwise.
[0004] The term “5G New Radio (NR)” used hereinafter in the specification refers to a next-generation mobile communication radio access technology that supports high data rates, low latency, and flexible deployment scenarios. 5G NR builds upon earlier cellular technologies, including Long-Term Evolution (LIE), and enables enhanced mobile broadband, ultra-reliable low-latency communications, and massive connectivity.
[0005] The term “Non- Terrestrial Network (NTN)” used hereinafter in the specification refers to communication networks that utilize non-ground-based infrastructure to provide connectivity, including but not limited to satellites and high-altitude platforms. NTN deployments enable extended coverage and connectivity in environments where terrestrial infrastructure is limited or unavailable.
[0006] The term “Radio Resource Control (RRC)” used hereinafter in the specification refers to a control-plane signaling protocol used to establish, configure, maintain, and release radio connections between a User Equipment (UE) and a radio access network, and to manage mobility-related procedures.
[0007] The term “RRC INACTIVE state” used hereinafter in the specification refers to a reduced-signaling and power-saving state of a UE in which an active radio connection with the network is released while UE context information is retained by the network to enable faster resumption of communication.
[0008] The term “Radio Access Network (RAN) Notification Area (RNA)” used hereinafter in the specification refers to a logical or geographical area, or a defined set of cells, within which a UE is permitted to move without initiating a full location update procedure while operating in an inactive or idle-type state.
[0009] The term “RNA update” used hereinafter in the specification refers to a signaling procedure initiated by a UE to notify the network when the UE transitions out of a currently associated RNA, enabling the network to update mobility-related configuration information.
[0010] The term “Global Navigation Satellite System (GNSS)” used hereinafter in the specification refers to a satellite-based positioning system that provides geolocationand timing information to a GNSS-enabled receiver, and is capable of supporting positioning and velocity estimation of a UE.
[0011] The term “inertial sensors” used hereinafter in the specification refers to motion-sensing components integrated within a UE, including accelerometers and gyroscopes, that detect changes in velocity, acceleration, or orientation and may be used to estimate UE movement when GNSS measurements are unavailable or degraded.
[0012] The term “satellite ephemeris data”, as used herein, refers to satellite trajectory and timing information transmitted to a User Equipment (UE), indicating a predicted position of a satellite over time. In particular, satellite ephemeris data refers to configuration information received by the UE during an initialization phase, where the UE receives a Radio Access Network (RAN) Notification Area (RNA) definition, such as a cell list or a Tracking Area Code (TAC), together with satellite ephemeris data as part of a Non-Terrestrial Network (NTN) configuration (NTN-Config) from a gNodeB. The satellite ephemeris data includes, for example, orbital path and timing information of a satellite, such as satellite position, satellite velocity, orbital trajectory parameters, and clock correction information valid for a defined period, and is used by the UE to predict future satellite movement and corresponding RNA boundary dynamics.
[0013] The term “hysteresis threshold” used hereinafter in the specification refers to a configurable time-based threshold that defines a minimum remaining time duration for initiating an RNA update procedure and that delays triggering of RNA updates in order to avoid unnecessary signalling caused by minor, transient, or short-term location changes of the UE.
[0014] The term “fallback procedure” used hereinafter in the specification refers to a default RNA update mechanism executed by the UE when prediction-based RNA update mechanisms become unavailable, unreliable, or fail to complete successfully, and includes reverting to conventional RNA update triggers to maintain reachability.
[0015] The term “velocity vector” used hereinafter in the specification refers to a quantity that represents both a magnitude (speed) and a direction of movement of the UE with respect to the Earth’s surface.
[0016] The term “RNA boundary” used hereinafter in the specification refers to a geographical, logical, or cell-based border that defines the limits of a Radio Access Network Notification Area (RNA). The RNA boundary represents a point at which a UE moving out of a currently registered RNA typically performs an RNA update to inform the network of its new location. In satellite-assisted networks, the RNA boundary may be dynamically influenced by movement of satellite coverage footprints.
[0017] The term “proactively triggering” used hereinafter in the specification refers to initiation of an action by the UE, including an RNA update procedure, in anticipation of a future event such as an expected RNA boundary crossing rather than in response to an already occurred boundary crossing.
[0018] The term “dynamically adjusted” used hereinafter in the specification refers to the ability of a parameter, including a hysteresis threshold, to change or adapt in response to current operating conditions such as satellite movement speed, RNA geographic dimensions, or UE mobility behavior.
[0019] The term “RRCResumeRequesf ’ used hereinafter in the specification refers to a Radio Resource Control (RRC) signalling message transmitted by a UserEquipment (UE) to a network entity, such as a gNodeB, to request resumption of a previously suspended or released RRC connection. The RRCResumeRequest message enables fast reactivation of radio resources and is used in connection with mobility management procedures, including RNA update procedures. The RNA update procedures, also referred to as RAN-based Notification Area Updates (RNAU), are mobility management procedures performed by a User Equipment (UE) operating in the RRC IN ACTIVE state to inform the Radio Access Network (RAN) when the UE moves outside a currently assigned RAN Notification Area (RNA) or when a periodic RNA update condition is met. The RNA update procedure enables the RAN to update the UE’s RNA assignment and maintain accurate paging and reachability information without performing a full core-network registration update. The RNA update procedure is typically initiated by the UE transitioning from the RRC INACTIVE state to an active signaling state using an RRCResumeRequest message, after which the network may provide updated RNA configuration information and return the UE to the RRC IN ACTIVE state. For example, when a UE in the RRC IN ACTIVE state performs cell reselection to a cell that does not belong to its configured RNA, the UE initiates an RNA update procedure by transmitting an RRCResumeRequest to a gNodeB. The gNodeB retrieves the UE context, updates the RNA assignment by providing updated RAN-NotificationArealnfo and related configuration parameters, and configures the UE with the updated RNA definition, thereby enabling efficient mobility handling and reduced signaling overhead compared to full registration procedures.
[0020] The term “RNA definition” used hereinafter in the specification refers to configuration information that specifies the scope and composition of a Radio Access Network (RAN) Notification Area assigned to a User Equipment. The RNA definition may be provided to the UE through RAN-NotificationArealnfo and may identify a set of cells, tracking area codes, or other geographic or logical identifiers that togetherdefine the RNA within which the UE is permitted to move without initiating an RNA update procedure. For example, the RNA definition may include a cell list conveyed via RAN-NotificationArealnfo, suspended-state configuration information that controls UE behavior while operating in an inactive state, and UE-specific RNA policies that specify mobility handling rules, validity conditions, or triggering behavior applicable to the UE.
[0021] The term “RAN-NotificationArealnfo” used hereinafter in the specification refers to configuration information provided by the Radio Access Network (RAN) to a User Equipment (UE) that defines a RAN Notification Area (RNA) associated with the UE. The RAN-NotificationArealnfo includes parameters identifying one or more cells, tracking area codes, or other geographic or logical identifiers that together specify the RNA within which the UE is permitted to move while operating in an inactive or suspended connection state without initiating an RNA update procedure. The RAN-NotificationArealnfo further enables the UE to determine whether it remains within a currently assigned RNA and to identify an RNA boundary for mobility management decisions. The RAN-NotificationArealnfo may be updated and transmitted to the UE by the network during an RNA update procedure or other configuration update procedures.
[0022] The term “NTN-Config” used hereinafter in the specification refers to information elements broadcast by a Non-Terrestrial Network to a User Equipment (UE) and containing configuration parameters relevant to Non-Terrestrial Network operation. Such configuration parameters include, for example and without limitation, satellite ephemeris data, satellite identification information, satellite orbital characteristics, timing parameters, frequency and bandwidth configuration, cell or beam configuration information, RNA-related information, mobility assistanceparameters, and validity or update timing information associated with satellite coverage.
[0023] The term “satellite ground track speed” used hereinafter in the specification refers to a ground-referenced speed that represents the rate at which a point directly beneath a satellite moves across the Earth’s surface as the satellite travels along its orbital path and corresponds to a ground-relative component of the satellite’s orbital motion.
[0024] The term “gNodeB (gNB)” used hereinafter in the specification refers to a base station of a 5G New Radio (NR) network that provides radio access functionality, broadcasts configuration and ephemeris information to UEs, and processes mobility-related signalling including RNA update procedures.
[0025] The term “suspend configuration (suspendConfig)” used hereinafter in the specification refers to configuration information provided by the network to a User Equipment (UE) when transitioning the UE from an active Radio Resource Control (RRC) state to the RRC INACTIVE state. The suspend configuration includes parameters required to enable efficient resumption of the RRC connection, paging operation, and mobility management while the UE operates in the RRC INACTIVE state. The suspendConfig may include information such as an RRC resume identifier, security context parameters, paging-related configuration, RNA-related parameters, validity timers, and conditions governing RNA update procedures. The suspend configuration allows the UE to maintain reachability and perform RNA updates without establishing a full RRC connection.
[0026] The term “Fallback Procedure” used hereinafter in the specification refers to a behavior of a User Equipment (UE) in which prediction-based Radio Access Network(RAN) Notification Area (RNA) update mechanisms are disabled and conventional RNA update triggering mechanisms are applied. The fallback procedure is invoked when one or more inputs required for prediction-based operation, such as Global Navigation Satellite System (GNSS) measurements or satellite ephemeris data, are unavailable, unreliable, or fail to meet configured reliability criteria. During fallback operation, the UE initiates RNA update procedures using standard triggers, including detection of cell reselection events or expiration of a periodic RNA update timer, to maintain reachability and continuity of mobility management.
[0027] The term “geodesic distance” used hereinafter in the specification refers to a shortest distance measured along a surface of the Earth between two geographic points defined by latitude and longitude coordinates. The geodesic distance accounts for curvature of the Earth and represents a surface-based separation between a current UE position and an RNA boundary, rather than a straight-line distance through the Earth. In the present disclosure, the geodesic distance is used to accurately compute a remaining distance between the UE and the RNA boundary for estimating a time duration before an RNA boundary crossing.
[0028] These definitions are in addition to those expressed in the art.BACKGROUND
[0029] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0030] With the emergence of Non-Terrestrial Networks (NTNs), including satellite-based access networks, the 5G system architecture has evolved to accommodate coverage in remote and underserved regions. The NTNs, leveraging satellites and high-altitude platforms, offer the potential for universal connectivity, especially in remote areas. The integration of the NTNs into existing and future mobile communication systems, such as 5G New Radio (NR), presents unique challenges in managing the mobility and registration of User Equipments (UEs). Further, the NTNs offer wide-area connectivity using low Earth orbit (LEO), medium Earth orbit (MEO), and geostationary orbit (GEO) satellites. However, the inherent dynamics of satellite motion, including their orbital speeds and varying coverage footprints, introduce new challenges to traditional terrestrial mobility and registration management protocols.
[0031] Within cellular networks, mobility management procedures are crucial for maintaining seamless connectivity as the UEs move across different coverage areas. In cellular systems, particularly when the UE is in a RRC INACTIVE state, mobility is managed using Radio Access Network (RAN) Notification Areas (RNAs). The RNA defines a geographical region or a set of cells within which the UE can move without triggering a full registration with the core network. When the UE moves out of its current RNA while in RRC_INACTIVE state, it triggers an RNA update procedure to notify the network of its new location, ensuring continued reachability for incoming services. The RRC INACTIVE state refers to an operational state of the UE in which an active radio connection with the network is released in order to reduce signaling overhead and power consumption, while UE context information is retained at the network side. In the RRC INACTIVE state, the UE remains reachable for paging and mobility management through the configured RNAs without maintaining continuous radio resources. The RNA update procedure enables the network to update mobility-related context information associated with the UE and ensures continued reachability for incoming services while maintaining reduced signaling and power consumption compared to full connection re-establishment procedures.
[0032] However, applying conventional terrestrial mobility management techniques directly to NTNs introduces several complexities. One significant challenge arises from the inherent mobility of the network infrastructure itself, particularly in the case of the low Earth orbit (LEO) satellites. The rapid movement of the LEO satellites results in constantly changing coverage areas and cell boundaries. Consequently, the UE that is geographically stationary or moving slowly relative to the surface of the earth may experience frequent changes in the serving cell and potentially cross RNA boundaries more often than in a static terrestrial network.
[0033] The conventional approaches to RNA updates in cellular networks often rely on triggers such as cell reselection events or periodic timers. While these mechanisms are effective in terrestrial deployments, they can lead to inefficiencies in the NTNs. For instance, the UE served by a fast- moving satellite might trigger numerous RNA updates based on cell reselection as the satellite moves across the ground, even if the actual location of the UE has not significantly changed. Similarly, periodic timers might force updates even when the UE remains within the same RNA served by a moving satellite for extended periods.
[0034] Frequent and unnecessary RNA updates consume valuable radio resources, increase signaling overhead, and contribute to higher power consumption at the UE. In NTNs, where bandwidth can be a premium and propagation delays are often greater than in terrestrial networks, these inefficiencies become particularly pronounced.
[0035] Therefore, there exists a need for solutions that can minimize redundant signalling and optimize UE power consumption while maintaining accurate UE reachability.
[0036] Hence, a method and system that can address the shortcomings of existing solutions are needed.SUMMARY OF THE DISCLOSURE
[0037] In an exemplary embodiment, a method managing mobility of a User Equipment (UE) in a network is disclosed. The method includes receiving, by a receiving unit of the UE, satellite ephemeris data from a gNodeB. The method includes obtaining, by a velocity and position module of the UE, a UE velocity vector based on Global Navigation Satellite System (GNSS) measurements associated with the UE obtained from a GNSS module of the UE. The method includes estimating, by a Radio Access Network (RAN) Notification Area (RNA) prediction module of the UE, a time duration at which the UE is expected to cross a boundary of a RNA based on the received satellite ephemeris data and the obtained UE velocity vector. The method includes causing, by a triggering module of the UE, initiation of an RNA update procedure when the estimated time duration is below a threshold.
[0038] In some embodiments, the method further includes deriving, by the RNA prediction module, a satellite ground-relative speed from the received satellite ephemeris data. In some embodiments, the method further includes computing, by the RNA prediction module, a relative velocity between the satellite ground-relative speed and the UE velocity vector toward the RNA boundary. In some embodiments, the method further includes computing, by the RNA prediction module, a distance from the UE to the RNA boundary.
[0039] In some embodiments, the time duration is estimated based on the computed relative velocity and the distance from the UE to the RNA boundary.
[0040] In some embodiments, the distance from the UE to the RNA boundary is a geodesic distance computed by a haversine formula.
[0041] In some embodiments, the threshold is a hysteresis threshold, and the hysteresis threshold defines a minimum remaining time duration for initiating the RNA update procedure.
[0042] In some embodiments, a hysteresis module of the UE adjusts the threshold based on one or more of a satellite orbital speed and geographic dimensions of the RNA. The satellite orbital speed and the geographic dimensions of the RNA are derived from the satellite ephemeris data.
[0043] In some embodiments, the triggering module transmits a resume request message indicating the initiation of the RNA update procedure to the gNodeB when the estimated time duration is below the threshold.
[0044] In some embodiments, in response to reception of the resume request message, the gNodeB transmits updated RNA configuration parameters to the UE.
[0045] In an exemplary embodiment, a system for managing mobility of a User Equipment (UE) in a network is disclosed. The system includes a receiving unit of the UE configured to receive satellite ephemeris data from a gNodeB. The system includes a velocity and position module of the UE configured to obtain a UE velocity vector based on Global Navigation Satellite System (GNSS) measurements associated with the UE obtained from a GNSS module of the UE. The system includes a Radio Access Network (RAN) Notification Area (RNA) prediction module of the UE configured to estimate a time duration at which the UE is expected to cross a boundary of a RNA based on the received satellite ephemeris data and the obtained UE velocity vector. The system includes a triggering module of the UE configured to cause initiation of an RNA update procedure when the estimated time duration is below a threshold.
[0046] In yet another embodiment, a computer program product including a non-transitory computer-readable medium including instructions that, when executed by one or more processors, cause the one or more processors to execute a method for managing mobility of a User Equipment (UE) in a network. The method includes receiving, by a receiving unit of the UE, satellite ephemeris data from a gNodeB. The method includes obtaining, by a velocity and position module of the UE, a UE velocityvector based on Global Navigation Satellite System (GNSS) measurements associated with the UE obtained from a GNSS module of the UE. The method includes estimating, by a Radio Access Network (RAN) Notification Area (RNA) prediction module of the UE, a time duration at which the UE is expected to cross a boundary of a RNA based on the received satellite ephemeris data and the obtained UE velocity vector. The method includes causing, by a triggering module of the UE, initiation of an RNA update procedure when the estimated time duration is below a threshold.OBJECTIVES OF THE DISCLOSURE
[0047] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:
[0048] An objective of the present disclosure is to provide a method and a system for enabling predictive and adaptive management of Radio Access Network (RAN) Notification Area (RNA) updates in satellite-assisted network environments.
[0049] An objective of the present disclosure is to provide a method and a system for managing RNA updates in a Non-Terrestrial Network (NTN) using satellite location data and User Equipment (UE) mobility data, by enabling the UE to receive satellite ephemeris data from the network and to obtain UE motion information using positioning measurements, and by estimating a remaining time duration before the UE is expected to cross an RNA boundary to support autonomous RNA update decisions.
[0050] An objective of the present disclosure is to provide a method and a system for reducing redundant RNA update signalling caused by frequent and unnecessary update triggers when the UE operates in an inactive or reduced-signalling state, by initiating RNA update procedures only when an estimated RNA boundary crossing time satisfies one or more triggering criteria based on an adaptive threshold.
[0051] An objective of the present disclosure is to provide a method and a system for enhancing battery efficiency of a UE by minimizing needless RNA update procedures and reducing repeated wake-ups from low-power states through prediction-based triggering that initiates RNA updates only when a boundary crossing is imminent.
[0052] An objective of the present disclosure is to provide a method and a system for applying an adaptive hysteresis mechanism for RNA update decisions, by dynamically adjusting a hysteresis threshold based on satellite movement characteristics, geographic dimensions of an RNA, and mobility status of the UE, thereby preventing oscillatory or transient triggering.
[0053] An objective of the present disclosure is to provide a method and a system for improving mobility robustness and reachability, by estimating RNA boundary crossings in advance and proactively initiating RNA update procedures prior to the UE exiting a currently registered RNA, thereby reducing missed paging events and improving service continuity.
[0054] An objective of the present disclosure is to provide a method and a system for ensuring reliable RNA update operation through a fallback mechanism, in which the UE reverts to conventional RNA update triggers, including cell reselection events or periodic timer-based updates, when prediction-based mechanisms are unavailable or fail.
[0055] An objective of the present disclosure is to provide a method and a system for improving overall network efficiency and scalability, by enabling autonomous RNA boundary prediction and triggering at the UE and reducing dependence on continuous network-side control, thereby lowering processing and signalling load at network entities.
[0056] Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING
[0057] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals, refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale; emphasis is instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components, or circuitry commonly used to implement such components.
[0058] FIG. 1 illustrates an exemplary network architecture comprising a system for managing mobility of a User Equipment (UE) in a network, in accordance with an embodiment of the present disclosure.
[0059] FIG. 2 illustrates an exemplary block diagram of the system for managing the mobility of the UE in the network, in accordance with an embodiment of the present disclosure.
[0060] FIG. 3 illustrates an exemplary system architecture of the system for managing the mobility of the UE in the network, in accordance with an embodiment of the present disclosure
[0061] FIG. 4 illustrates an exemplary flow diagram of a method for managing the mobility of the UE in the network, in accordance with an embodiment of the present disclosure.
[0062] FIG. 5 illustrates another exemplary flow diagram of the method for managing the mobility of the UE in the network, in accordance with an embodiment of the present disclosure.
[0063] FIG. 6 illustrates an example computer system in which or with which the embodiments of the present disclosure may be implemented.
[0064] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102- 1 , 102-2... 102-N - User(s)104-1, 104-2... 104-N - User equipment(s)106 - Network108 - System200 - Block diagram202 - Processor(s)204 - Memory206 - Interface(s)208 - Processing engine210 - Global Navigation Satellite System (GNSS) module212 - Velocity and position module214 - Radio Access Network (RAN) Notification Area (RNA) prediction module 216 - Dynamic hysteresis module218 - Triggering module220 - Fallback procedure module222 - Database224 - Receiving unit300 - System Architecture302 - gNodeB (gNB)304 - Satellite ephemeris broadcast module306 - RNA configuration management module400, 500 - Flow diagram600 - Computer System610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port(s)670 - ProcessorDETAILED DESCRIPTION
[0065] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
[0066] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0067] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinaryskill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[0068] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
[0069] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive like the term “comprising” as an open transition word without precluding any additional or other elements.
[0070] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature,structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0071] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.
[0072] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and otherchanges in the preferred embodiment, as well as other embodiments of the disclosure, will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.
[0073] In current Non- Terrestrial Network (NTN) deployments, User Equipments (UEs) operating in a Radio Resource Control (RRC)_IN ACTIVE state are generally expected to perform Radio Access Network (RAN) Notification Area (RNA) updates based on conventional triggers, such as periodic timers and / or cell reselection procedures. However, in practical satellite-based scenarios, especially in deployments using Low Earth Orbit (LEO) satellite constellations, the satellite coverage footprint may shift rapidly over the Earth’s surface due to satellite movement. As a result, even when a UE is stationary or exhibits low mobility, the UE may experience frequent changes in serving coverage and corresponding RNA boundaries caused by footprint drift rather than by meaningful UE movement. This dynamic environment can lead to frequent, and often unnecessary, RNA update procedures triggered by minor positional variations and / or satellite-induced coverage changes. Such repeated RNA updates increase control-plane signalling overhead between the UE and the network, reduce UE battery life due to repeated wake-ups and signaling exchanges, and inefficiently consume network resources, particularly in satellite environments where radio resources and link budgets are constrained and signaling exchanges can be costly.
[0074] In an aspect, the present disclosure provides a system and a method for managing mobility of the UE in a network by enabling a UE-based predictive RNA update mechanism. In an embodiment, the UE receives satellite ephemeris data from a network entity, for example as part of an NTN configuration. The satellite ephemeris data includes, for example and without limitation, orbital path and timing information such as satellite position coordinates, satellite velocity information, timestamped state vectors, orbital trajectory parameters, validity period information, and clock correction1information. In an embodiment, the network entity includes, for example, a base station, a radio access node, or another network controller configured to broadcast or provide the NTN configuration. In an embodiment, the UE determines a current UE velocity vector based on measurements from one or more positioning sensors, such as a Global Navigation Satellite System (GNSS) module, an inertial measurement unit (IMU), an accelerometer, a gyroscope, a magnetometer, or a combination thereof, using successive position fixes and sensor fusion to obtain both a magnitude and a direction of UE motion.
[0075] Based on the satellite ephemeris data and the UE velocity vector, an RNA prediction module of the UE autonomously calculates a future RNA boundary crossing, for example by estimating a remaining time duration before the UE is expected to cross an RNA boundary influenced by a moving satellite footprint. The UE proactively initiates an RNA update when necessary, such as when the remaining time duration falls below a configured threshold, thereby reducing redundant signaling as compared to timer-based or reselection-based triggering. In an embodiment, the threshold is implemented as a hysteresis threshold, and a dynamic hysteresis adjustment mechanism adapts the hysteresis threshold based on one or more parameters derived from the satellite ephemeris data, such as satellite movement speed and geographic dimensions of the RNA, to reduce oscillatory or repeated triggers in highly dynamic conditions. In an embodiment, the dynamic hysteresis adjustment mechanism increases the hysteresis threshold when satellite movement speed increases or when the RNA has smaller geographic dimensions, and decreases the hysteresis threshold when satellite movement speed decreases or when the RNA has larger geographic dimensions. Non-limiting examples of the hysteresis threshold include about 5 seconds, 10 seconds, 15 seconds, 30 seconds, 60 seconds, or 120 seconds.
[0076] In the context of the present disclosure, hysteresis is employed as a decision-stabilization mechanism for controlling initiation of Radio Access Network (RAN) Notification Area (RNA) update procedures under dynamically changing coverage conditions. The term hysteresis threshold refers to a configurable time-based threshold that defines a minimum remaining time duration before an RNA update procedure is initiated. The hysteresis threshold is applied to prevent repeated or unnecessary RNA updates that may otherwise be triggered due to transient variations in satellite movement, UE motion, or short-term fluctuations in boundary estimation.
[0077] In an embodiment, a hysteresis margin represents a tolerance range applied around the hysteresis threshold and defines conditions under which RNA update triggering is temporarily suppressed even when minor changes are observed in the estimated remaining time duration. The hysteresis margin ensures that RNA update initiation is based on sustained and meaningful proximity to an RNA boundary rather than instantaneous or noisy measurements.
[0078] In an embodiment, a dynamic hysteresis adjustment mechanism refers to logic implemented at the UE that adapts the hysteresis threshold and / or hysteresis margin based on current operating conditions. Examples of operating conditions include satellite ground-relative movement speed, satellite orbital characteristics, geographic dimensions of the RNA, and UE mobility behavior. For instance, when satellite movement speed is high or when the RNA has smaller geographic dimensions, the dynamic hysteresis adjustment mechanism increases the hysteresis threshold to enable earlier RNA update initiation. Conversely, when satellite movement speed is lower or when the RNA has larger geographic dimensions, the hysteresis threshold is decreased to delay RNA update initiation and reduce unnecessary signalling.
[0079] In an embodiment, the RNA update is initiated by the UE transmitting a resume request message when the predicted boundary crossing time satisfies one or more triggering criteria. The resume request message indicates initiation of an RNA update procedure and enables a network entity to provide updated RNA configuration information to the UE. Further, to maintain robustness, the UE applies a fallback RNA update procedure when satellite ephemeris data and / or UE motion measurements become unavailable or unreliable. Examples of unavailability or unreliability include loss or degradation of positioning sensor measurements, insufficient positioning fix quality, intermittent or stale ephemeris information, missing ephemeris updates, inconsistent sensor readings, or a confidence level that falls below a configured reliability threshold. During the fallback RNA update procedure, the UE performs RNA updates based on triggers, including periodic update timing and coverage change events, and continues monitoring until reliable inputs become available again.
[0080] Accordingly, the disclosed approach reduces signalling overhead by avoiding frequent RNA update exchanges that would otherwise be triggered by moving satellite footprints, and instead initiating an RNA update only when a predicted boundary crossing satisfies one or more triggering criteria. The disclosed approach improves UE battery efficiency by reducing repeated wake-ups, repeated control messaging, and repeated processing associated with unnecessary RNA update procedures, enabling the UE to remain in power-saving operation for longer durations. The disclosed approach enhances mobility robustness and reachability in dynamic satellite environments by increasing the likelihood that RNA configuration remains current when a boundary crossing is imminent, thereby reducing missed paging opportunities and improving responsiveness for downlink reachability. The disclosed approach improves overall network resource utilization by lowering control-plane load, reducing contention for limited radio resources, and decreasing processing overhead at network entities that handle RNA update signaling and configuration updates. The disclosed approach further improves stability by applying a dynamically adjustedhysteresis threshold that reduces oscillatory triggers caused by minor variations in measurements or transient coverage changes, while a fallback RNA update procedure maintains service continuity when satellite ephemeris data or UE motion measurements become unavailable or unreliable. Collectively, these features support scalable mobility handling for a plurality of UEs operating under rapidly changing satellite coverage conditions, while maintaining reliable reachability and efficient utilization of network resources.
[0081] The various embodiments throughout the disclosure will be explained in more detail with reference to FIGS. 1- 6.
[0082] FIG. 1 illustrates an exemplary network architecture (100) comprising a system (108) for managing mobility of a User Equipment (UE) (104) in a network (106), in accordance with an embodiment of the present disclosure.
[0083] As illustrated in FIG. 1, the network architecture (100) may include one or more user equipments (UEs) (104-1, 104-2... 104-N) associated with one or more users (102-1, 102-2... 102-N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2... 102-N) may collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more UEs (104-1, 104-2... 104-N) may be collectively referred to as the UE (104). Although only three UEs (104) are depicted in FIG. 1, however, any number of the UE (104) may be included without departing from the scope of the ongoing description. In an example, the UE (104) may be an Internet of Things (loT) device.
[0084] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the UE (104) may include, but is not limited to, smartphones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system,communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the users (102) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE (104) may include, but not limited to, intelligent, multisensing, network- connected devices, which may integrate seamlessly with each other and / or with a central server or a cloud- computing system or any other device that is network-connected.
[0085] Additionally, in some embodiments, the UE (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a tablet device, and so on), a wearable computer device (e.g., a headmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE (104) may include, but is not limited to, any electrical, electronic, electromechanical, or equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein the UE (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or the entity such as touchpad, touch-enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.
[0086] Referring to FIG. 1, the UE (104) may communicate with the system (108) through the network (wireless communication network) (106) for sending or receiving various types of data. In an embodiment, the network (106) may include at least one of a fifth-generation (5G) network, a sixth-generation (6G) network, or the like. The network (106) may enable the UE (104) to communicate with other devices in the network architecture (100) and / or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.
[0087] The network (106) facilitates mobility management by enabling the UE (104) to exchange mobility-related signaling, such as Radio Access Network (RAN) Notification Area (RNA) updates, with the system (108). Through this communication, the UE (104) can leverage prediction-based or fallback mechanisms to maintain seamless connectivity during movement across different coverage areas in the network architecture (100).
[0088] In an embodiment, the network (106) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network (106) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructurenetwork, a Public Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.
[0089] In an embodiment, the UE (104) is communicatively coupled with the network (106). The network (106) may receive a connection request from the UE (104). The network (106) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request. The plurality of signals may include, for example and without limitation, one or more control messages associated with mobility management, an RNA update related message, capability information, measurement information, and status information associated with the UE (104). In an embodiment, the plurality of signals includes a resume request message transmitted by the UE (104) to initiate an RNA update procedure based on a predicted RNA boundary crossing. In response to reception of the plurality of signals, the network (106) may transmit configuration information to the UE (104), including an RNA definition and updated RNA configuration parameters, and may further transmit satellite ephemeris data and dynamic prediction configuration information for enabling predictive RNA update operation at the UE (104). The UE (104) may store the received configuration information and continue monitoring mobility conditions to determine whether to initiate subsequent RNA update procedures.
[0090] Although FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture (100).
[0091] In an embodiment, FIG. 2 illustrates an exemplary block diagram (200) of a system (108) for managing the mobility of the UE (104) in the network (106) inaccordance with an embodiment of the present disclosure. FIG. 2 is explained in conjunction with FIG. 1.
[0092] In an embodiment, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may include any non-transitory storage device including, for example, volatile memory such as a Random-Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, and the like.
[0093] Referring to FIG. 2, the system (108) may include an interface(s) (206) that may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as VO devices, storage devices, and the like. The interface(s) (206) may facilitate communication to / from the system (108). The interface(s) (206) may also provide a communication pathway for one or more components of the system (108). Examples of such components include but are not limited to, a processing engine (208) and a database (222).
[0094] In an embodiment, the processing engine (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine (208). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for theprocessing engine (208) may be processor-executable instructions stored on a non-transitory machine-readable storage medium, and the hardware for the processing engine (208) may include a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine (208). In such examples, the system (108) may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (108) and the processing resource. In other examples, the processing engine (208) may be implemented by electronic circuitry.
[0095] Among other capabilities, the processing engine (208) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may include any non-transitory storage device including, for example, volatile memory such as Random Access Memory (RAM), or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), flash memory, and the like.
[0096] In an embodiment, the database (222) may include data that may be either stored or generated as a result of functionalities implemented by the processing engine (208). In an embodiment, the database (222) may be separate from the system (108). In an embodiment, the database (222) may be indicative of including, but not limited to, a relational database, a distributed database, a cloud-based database, or the like
[0097] In an embodiment, the system (108) includes a User Equipment (UE) (104) that implements mobility-management functionality through the processing engine(208). In an embodiment, the processing engine (208) comprises of a Global Navigation Satellite System (GNSS) module (210) / inertial sensors, a velocity and position module (212), a Radio Access Network (RAN) Notification Area (RNA) prediction module (214), a dynamic hysteresis module (216), a triggering module (218), and a fallback procedure module (220).
[0098] In an embodiment, the UE (104) comprises a receiving unit (224) configured to receive satellite ephemeris data from a network entity. In an embodiment, the network entity includes a base station, a radio access node, or another access-side controller, and the term gNodeB (gNB) used hereinafter refers to such a base station of the network (106). The satellite ephemeris data forms part of initial configuration data delivered to the UE (104) during an initialization phase, connection setup phase, connection resumption phase, or a mobility configuration update phase. The initial configuration data also includes RAN-NotificationArealnfo and dynamic RNA prediction configuration data received from the network entity. In an embodiment, RAN-NotificationArealnfo provides RNA definition information used by the UE (104) to identify an RNA and determine an RNA boundary for RNA update decisions. Examples of RNA definition information include an RNA identifier, an RNA definition comprising a cell list and / or a tracking area code (TAC), a list of coverage identifiers associated with the RNA, a list of cell identifiers grouped into the RNA, one or more area codes associated with the RNA, or a mapping that associates coverage regions with RNA membership. In an embodiment, the dynamic RNA prediction configuration data includes one or more triggering criteria, a time-based threshold for initiating an RNA update, hysteresis settings, sensor reliability settings, validity timers for configuration elements, and fallback enablement settings. In an embodiment, the initial configuration data is stored in the database (222), and one or more modules of the UE (104) access the stored configuration data to perform prediction, threshold adjustment, and triggering operations.
[0099] In an embodiment, the satellite ephemeris data includes orbital path information and timing information that enables prediction of satellite movement over time. The satellite ephemeris data may be derived from ephemeris parameters broadcast by a satellite, provided by an associated ground-based control segment, or generated by a network-side controller using satellite orbit determination information. The satellite ephemeris data supports determination of a future trajectory of the satellite and corresponding movement of a satellite coverage footprint relative to the Earth’s surface, and the footprint movement influences RNA boundary dynamics experienced by the UE (104). Examples of satellite ephemeris data include satellite position information associated with a reference time, satellite velocity information, timestamped position and velocity vectors, orbital trajectory parameters, timing correction information, and clock correction information associated with a defined validity period. In an embodiment, the ephemeris data is refreshed periodically, for example every 2 minutes, 5 minutes, 10 minutes, 15 minutes, or 30 minutes, and each update includes a validity interval indicating a duration for which the ephemeris data remains applicable. In an embodiment, the receiving unit (224) is implemented as a software-based radio protocol layer module embedded within the UE (104), and the receiving unit (224) parses the received ephemeris data, validates using the validity interval, and stores ephemeris parameters in the database (222) for use by an RNA prediction module in estimating future RNA boundary crossings.
[0100] In an embodiment, a velocity and position module (212) of the UE (104) is configured to obtain a UE velocity vector based on Global Navigation Satellite System (GNSS) measurements associated with the UE (104) obtained from a GNSS module (210) of the UE (104). The UE velocity vector represents a magnitude and a direction of motion of the UE (104) and is generated for use in mobility prediction operations, including prediction of a future RNA boundary crossing. In an embodiment, the velocity and position module (212) obtains the UE velocity vector repeatedly over time to support continuous or periodic RNA prediction.
[0101] In an embodiment, the UE velocity vector represents a motion descriptor derived from positioning measurements and defines both a magnitude and a direction of movement of the UE relative to the Earth’s surface. The magnitude of the UE velocity vector corresponds to a speed at which the UE is moving, while the direction corresponds to a heading or trajectory of the UE along one or more geographic axes. The UE velocity vector may be expressed as a two-dimensional vector over a horizontal plane or as a three-dimensional vector that additionally includes vertical movement components.
[0102] In an embodiment, the UE velocity vector is computed by the velocity and position module using successive Global Navigation Satellite System (GNSS) position fixes obtained over time, and optionally refined using inertial sensor measurements. The UE velocity vector provides a continuous or periodically updated representation of UE motion and enables determination of how the UE is moving with respect to an RNA boundary. Accordingly, the UE velocity vector serves as a key input to the RNA prediction module for estimating relative movement between the UE and the RNA boundary and for predicting a remaining time duration before the UE is expected to cross the RNA boundary.
[0103] In an embodiment, the Global Navigation Satellite System (GNSS) module (210) is configured to determine GNSS data of the UE (104) using satellite-based positioning signals. The GNSS data includes at least a latitude and a longitude of a current position of the UE (104), and may further include altitude, a timestamp associated with the current position, and one or more measurement quality indicators. Examples of measurement quality indicators include an estimated position accuracy value, a confidence value, an uncertainty radius, a dilution-of-precision metric, a number of satellites contributing to a fix, or a fix type indicator. In an embodiment, inertial sensors of the UE (104), including accelerometers and gyroscopes, provide motion information indicative of changes in velocity, acceleration, or orientation of theUE (104). For example, accelerometer measurements enable detection of linear movement or acceleration, while gyroscope measurements enable detection of rotational motion or heading changes, and the inertial sensor outputs may be used to estimate or refine UE velocity during short-term GNSS signal degradation or unavailability. In an embodiment, the GNSS module (210) provides successive GNSS position fixes at predefined intervals, for example about every 500 ms or about every 1 second, to support tracking of UE movement for accurate RNA prediction, and the inertial sensor data complements the GNSS data to improve continuity and reliability of velocity estimation. In an embodiment, the GNSS module (210) and the inertial sensors are integrated with hardware of the UE (104), and in another embodiment, the GNSS module (210) and the inertial sensors operate through a software interface that exposes positioning and motion data to one or more modules of the UE (104).
[0104] In an embodiment, the velocity and position module (212) is coupled to the GNSS module (210) and is configured to determine velocity information and position information of the UE (104) based on the GNSS data obtained from the GNSS module (210). The velocity and position module (212) determines a current UE position from a most recent GNSS position fix and derives the UE velocity vector using successive GNSS position fixes associated with different timestamps. For example, the velocity and position module (212) computes a displacement between a first GNSS position fix and a second GNSS position fix and computes the UE velocity vector using the displacement and a time difference between the corresponding timestamps, and the UE velocity vector includes a speed component and a direction component. In an embodiment, the velocity information includes ground speed and heading, and the velocity and position module (212) outputs the UE velocity vector (V ue) for projecting a future movement path of the UE (104). In an embodiment, the velocity and position module (212) applies smoothing or filtering to reduce noise in successive velocity estimates, including a moving average filter, an exponentially weighted filter, or a state-estimation based filter. In an embodiment, the velocity and position module(212) combines GNSS data with motion sensor data available at the UE (104) to improve stability of the UE velocity vector, including accelerometer data and gyroscope data. The current position determined by the velocity and position module (212) serves as a starting point for prediction, and the UE velocity vector (V_ue) serves as an input used by an RNA prediction module to estimate a future RNA boundary crossing and a remaining time duration before the UE (104) is expected to cross an RNA boundary influenced by a moving satellite footprint.
[0105] In an embodiment, a Radio Access Network (RAN) Notification Area (RNA) prediction module (214) of the UE (104) estimates a time duration at which the UE (104) is expected to cross a boundary of a RNA based on the received satellite ephemeris data and the obtained UE velocity vector. In an embodiment, the RNA prediction module (214) calculates an estimated RNA boundary crossing time based on velocity data of the UE (104) and an expected movement of an RNA boundary derived from satellite movement information obtained using satellite ephemeris data received by the receiving unit (224). In an embodiment, the RNA prediction module (214) obtains a current UE position and the UE velocity vector (V ue) from the velocity and position module (212) and obtains an RNA definition from stored configuration information that identifies a boundary representation of a currently registered RNA.
[0106] In an embodiment, the RNA prediction module (214) derives satellite movement information from the satellite ephemeris data, including satellite position values at multiple time instants, satellite velocity values, and timing information associated with a validity interval, and the RNA prediction module (214) uses the satellite movement information to determine an expected shift of satellite coverage relative to the Earth’s surface that influences movement of the RNA boundary. In an embodiment, the RNA prediction module (214) derives a satellite ground- relative speed from the satellite ephemeris data as a ground-referenced speed having amagnitude and a direction associated with movement of a satellite footprint on the Earth’s surface. In an embodiment, the satellite ground-relative speed includes a satellite ground track speed denoted as V sat.
[0107] In an embodiment, the RNA prediction module (214) determines a direction associated with movement toward the RNA boundary using the RNA definition stored at the UE (104) and the current UE position and computes a relative movement between the UE (104) and the RNA boundary by combining the UE velocity vector (V_ue) with satellite-derived ground motion associated with V sat. In an embodiment, the relative velocity (V rel) is calculated as the difference between the projected ground track speed (V_sat) of the satellite and the velocity vector (V_ue) of the UE (104) toward the RNA boundary. In an embodiment, V sat represents a satellite ground-relative speed component derived from the satellite ephemeris data and corresponds to an apparent movement of a satellite coverage footprint across the Earth’s surface. The satellite ground track speed V sat reflects a rate and direction at which an RNA boundary shifts due to satellite motion and captures the effect of satellite orbital dynamics on RNA boundary location over time. By expressing satellite motion as a ground-relative speed, the RNA prediction module accounts for dynamic movement of coverage regions even when the UE is stationary or moving slowly.
[0108] In an embodiment, V ue represents the UE velocity vector derived from Global Navigation Satellite System (GNSS) measurements and corresponds to a magnitude and direction of movement of the UE relative to the Earth’s surface. The UE velocity vector V_ue indicates how the UE is moving with respect to a currently registered RNA and reflects user mobility characteristics such as pedestrian movement, vehicular movement, or stationary behavior. In an embodiment, the RNA prediction module (214) computes a relative velocity (V_rel) as an effective closing speed toward the RNA boundary using vector components directed toward the RNA boundary, as shown in Equation (1):V_rel = V_sat - V_ue (vector components directed toward the RNA boundary) . (1)
[0109] In an embodiment, the V rel computed using V sat and V ue represents an effective closing speed between the UE and an RNA boundary under satellite-influenced coverage movement. When V rel has a larger magnitude, the UE is expected to reach or cross the RNA boundary more rapidly, and when V rel has a smaller magnitude, RNA boundary crossing is expected to occur later or not at all. Accordingly, V_sat captures movement of the RNA boundary caused by satellite motion, V ue captures movement of the UE itself, and the combination of V sat and V ue enables accurate prediction of RNA boundary crossings in satellite-assisted network environments.
[0110] In an embodiment, the RNA prediction module (214) computes a remaining distance from the current UE position to the RNA boundary using a geodesic distance computation and denotes the remaining distance as d(t) at time instant t. In an embodiment, the geodesic distance refers to a shortest distance measured along a surface of the Earth between two geographic points, rather than a straight-line distance through the Earth. The geodesic distance accounts for the curvature of the Earth and provides an accurate representation of separation between a current UE position and an RNA boundary when both are expressed using geographic coordinates such as latitude and longitude.
[0111] In an embodiment, the geodesic distance computation uses a Haversinebased calculation when the RNA boundary is represented by geographic coordinates. The remaining distance is represented as shown in Equation (2):d(t) = Distance To Boundary . (2)
[0112] In an embodiment, the d(t) can be computed using the Haversine formula as in Equation (3):d(t) = 2R • arcsin ^jsin2(^~^) +cos(0i)cos(02)sin 2. (3)where: < >i, i: UE latitude and longitude (radians)< >2, A2: RNA boundary point coordinates (radians); andR Earth radius (6371 km)
[0113] In an embodiment, a Haversine-based computation is used to calculate the geodesic distance between two geographic points specified by latitude and longitude coordinates. The Haversine computation determines a shortest distance measured along the surface of the Earth by accounting for the curvature of the Earth, rather than approximating the distance using a planar or straight-line model. This approach enables accurate determination of a remaining distance between a current UE position and an RNA boundary when the positions are defined using geographic coordinates. In the present disclosure, the distance (Distance To Boundary) calculated using the Haversine-based computation is denoted as d(t) and is used as an input for estimating a remaining time duration before an RNA boundary crossing. The use of a Haversine-based distance calculation supports reliable and consistent RNA boundary prediction under satellite-influenced coverage movement.
[0114] In an embodiment, the RNA prediction module (214) estimates a remaining time duration before the UE (104) reaches or crosses the RNA boundary using the remaining distance and a magnitude of V rel. In an embodiment, the time duration is represented as an estimated time to RNA boundary crossing denoted as T exit, and T exit represents a remaining time duration before the UE (104) is expected to exit a current RNA. The RNA prediction module (214) computes T exit as shown in Equation (4):„ Distance to Boundary „= — iTs; — . <4»
[0115] In an embodiment, the RNA prediction module (214) updates V rel, d(t), and T exit as new positioning measurements and satellite ephemeris updates become available. In an embodiment, the RNA prediction module (214) generates a time window for the estimated boundary crossing time to account for measurement uncertainty, boundary movement variability, and update periodicity, and the time window includes an earliest expected crossing time computed using a higher relative speed and a shorter plausible distance and a latest expected crossing time computed using a lower relative speed and a longer plausible distance. In an embodiment, the RNA prediction module (214) associates a confidence measure with the estimated time window based on GNSS measurement quality indicators, freshness of ephemeris data relative to a validity interval, consistency of successive velocity estimates, and stability of boundary movement estimates across consecutive evaluation cycles. By analyzing the relative movement, the RNA prediction module (214) anticipates when the UE (104) is likely to move out of the currently registered RNA and outputs T exit or the time window for use by the triggering module (218) in determining whether initiation of an RNA update procedure satisfies one or more triggering criteria.
[0116] In an embodiment, a triggering module (218) of the UE (104) configured to cause initiation of an RNA update procedure when the estimated time duration (T exit) is below a threshold. In an embodiment, the RNA prediction module (214) computes T exit based on a computed distance d(t) from the UE (104) to the RNA boundary and a relative velocity toward the RNA boundary, such that a decrease in the distance d(t) results in a corresponding decrease in T exit. The triggering module (218) obtains T exit from the RNA prediction module (214) and compares T exit, which reflects proximity of the UE (104) to the RNA boundary, with the threshold based on one or more triggering criteria to determine whether to initiate the RNA update procedure.
[0117] In an embodiment, the RNA prediction module (214) evaluates whether an estimated RNA boundary crossing time satisfies the threshold and cooperates withother modules, including the dynamic hysteresis module (216), to support RNA reconfiguration prior to an expected boundary crossing. This coordination reduces paging-related overhead by maintaining reachability with fewer unnecessary RNA updates and supports session continuity by increasing the likelihood that RNA configuration remains current when a boundary crossing is imminent under moving satellite coverage conditions.
[0118] In an embodiment, the evaluation performed by the RNA prediction module (214) is based on a computed remaining time duration to the RNA boundary derived from a remaining distance between the UE and the RNA boundary and a relative velocity representing combined UE movement and satellite ground-relative movement. The RNA prediction module (214) compares the estimated remaining time duration with a hysteresis threshold provided or adjusted by the dynamic hysteresis module (216). The evaluation further considers consistency of successive boundary crossing estimates across multiple evaluation intervals to avoid triggering RNA updates based on transient fluctuations in UE position, velocity, or satellite movement. In an embodiment, when the estimated remaining time duration remains below the hysteresis threshold for a defined evaluation cycle, the RNA prediction module (214) determines that RNA reconfiguration is required and signals the triggering module to initiate an RNA update procedure. Conversely, when the estimated time duration varies within a hysteresis margin or remains above the hysteresis threshold, RNA update initiation is suppressed and monitoring continues. This cooperative logic between the RNA prediction module (214) and the dynamic hysteresis module (216) enables stable, timely, and controlled RNA update initiation under dynamically changing satellite coverage conditions.
[0119] In an embodiment, the dynamic hysteresis module (216) is configured to adjust the threshold used for triggering RNA updates. In an embodiment, the threshold is a hysteresis threshold. The dynamic hysteresis module (216) adjusts the thresholdbased on one or more parameters that include a satellite orbital speed and geographic dimensions of RNA regions, and the satellite orbital speed and the geographic dimensions are derived using satellite ephemeris data and stored RNA definition information. For example, when the satellite orbital speed indicates rapid movement of satellite coverage across the surface of the Earth and RNA boundaries change quickly, the dynamic hysteresis module (216) increases the threshold to support earlier triggering and timely RNA update initiation before the UE (104) reaches or crosses an RNA boundary influenced by footprint movement. Conversely, when satellite movement is slower or when an RNA region has geographic dimensions that accommodate extended movement of the UE (104) within the RNA, the dynamic hysteresis module (216) decreases the threshold to delay triggering. This reduces unnecessary RNA update signaling and conserves UE battery life and network resources.
[0120] In an embodiment, the dynamic hysteresis module (216) applies dynamic hysteresis criteria during adjustment of the threshold. The dynamic hysteresis criteria include dynamically adjusting a hysteresis margin associated with the threshold based on satellite orbital speed and RNA geographic dimensions derived using satellite ephemeris data. When satellite orbital speed is high and an RNA boundary shifts rapidly, the dynamic hysteresis module (216) increases the hysteresis margin to account for rapidly shifting coverage boundaries and reduce late initiation of RNA updates. When satellite orbital speed is low or an RNA region is large, the dynamic hysteresis module (216) decreases the hysteresis margin to allow greater tolerance and delay RNA updates to avoid unnecessary signalling. In an embodiment, the dynamic hysteresis module (216) factors in mobility status of the UE (104) during adjustment of the threshold and the hysteresis margin. For example, a stationary UE (104) uses a higher tolerance setting to prevent unnecessary RNA updates due to transient measurement fluctuations or temporary boundary movement. A highly mobile UE(104) uses a more responsive setting to maintain continuous RNA alignment during movement across multiple coverage regions.
[0121] In a non-limiting example, the hysteresis threshold is configured as 2.5 seconds, and since T_exit - 1.87 seconds is below 2.5 seconds, the triggering module initiates the RNA update procedure by transmitting a resume request message. In another non-limiting example, the hysteresis threshold is configured as 1.0 second, and since T exit - 1.87 seconds is not below 1.0 second, the triggering module defers initiation of the RNA update procedure until a later evaluation cycle.
[0122] In an embodiment, the triggering module (218) is configured to trigger the RNA update procedure for the UE (104) when the T exit falls below the threshold used for managing mobility of the UE (104) in the network (106). The triggering occurs in response to the estimated RNA boundary crossing determined by the RNA prediction module (214) and the adjusted threshold and hysteresis settings provided by the dynamic hysteresis module (216). In an embodiment, the triggering module (218) transmits a resume request message indicating initiation of the RNA update procedure to a gNodeB when T exit is below the threshold and the dynamic hysteresis criteria are satisfied. In an embodiment, the triggering module (218) transmits an RRCResumeRequest when the dynamic hysteresis criteria are met.
[0123] In an embodiment, in response to reception of the resume request message, the gNodeB transmits updated RNA configuration parameters to the UE (104). The updated RNA configuration parameters may include updated RNA definition information. For example, the updated RNA definition information may comprise an updated cell list and / or an updated tracking area code (TAC). The updated RNA configuration parameters may further include updated RAN-NotificationArealnfo that defines new or modified RNA boundaries. In an embodiment, the updated RNA configuration parameters include updated dynamic RNA prediction configuration data, such as prediction enablement flags, monitoring intervals, or reliability criteria. Theupdated RNA configuration parameters may also include an updated threshold value for triggering RNA updates and updated hysteresis settings, including hysteresis margins or adaptation parameters. In an embodiment, the updated RNA configuration parameters further include updated validity information indicating a duration for which the configuration parameters remain applicable. In some embodiments, the updated RNA configuration parameters include updated suspend-state configuration information, paging-related parameters, or mobility assistance information. The UE (104) stores at least a portion of the updated RNA configuration parameters in a local memory or database. The UE (104) subsequently uses the stored parameters for RNA boundary prediction, hysteresis evaluation, and RNA update triggering operations.
[0124] In an embodiment, a fallback procedure module (220) is configured to initiate one or more predefined fallback procedures when triggering conditions based on RNA boundary prediction and dynamic hysteresis evaluation do not result in a successful RNA update, or when signal availability or required inputs for prediction become compromised. The fallback procedure module (220) operates in coordination with the triggering module (218) to monitor a post-trigger status of the UE (104) after a resume request message is transmitted and to determine whether the RNA update procedure has completed successfully. In an embodiment, the fallback procedure module (220) starts a monitoring timer after transmission of an RRCResumeRequest and expects a confirmation or an update response from a network entity within a predefined time window. Examples of conditions that cause entry into fallback include failure to receive a response within the predefined time window, repeated transmission failures of the resume request message, detection of degraded positioning inputs over a prolonged period, loss of satellite ephemeris data updates beyond a validity interval, or suspension of predictive operations due to low confidence in motion measurements. In an embodiment, the fallback procedure module (220) also enters fallback when satellite ephemeris data and / or GNSS-based motion measurements are unavailable, unreliable, or stale beyond a validity interval, and the UE (104) disables prediction-based triggering until reliable inputs become available again. When a fallback condition is detected, the fallback procedure module (220) initiates a fallback RNA update mechanism to maintain reachability and service continuity.
[0125] In an embodiment, the fallback RNA update mechanism includes reverting to conventional RNA update procedures that do not rely on prediction inputs. In one example, the fallback procedure module (220) initiates an RNA update using a conventional network-controlled signaling exchange performed over control-plane messaging, and the UE (104) performs the RNA update using the same resume request message flow used for mobility management. In another example, the fallback procedure module (220) temporarily disables the prediction-based RNA update mechanism and relies on conventional coverage change events detected by the UE (104), including cell reselection events based on radio measurements, to decide whether an RNA update is needed. In another example, the fallback procedure module (220) initiates a periodic RNA update procedure based on expiry of a timer so that the UE (104) performs necessary updates at predetermined intervals during periods when prediction inputs remain unavailable or unreliable. In an embodiment, the UE (104) continues applying the fallback triggers until valid ephemeris data and reliable motion measurements become available again, after which the UE (104) resumes predictionbased RNA boundary crossing estimation and threshold-based triggering. In an embodiment, the fallback procedure module (220) also initiates recovery actions to restore prediction capability, including reinitializing the GNSS module (210), requesting refreshed ephemeris information, clearing stale prediction state, and rerunning input reliability checks before re-enabling prediction-based RNA updates. In an embodiment, the fallback procedure module (220) causes the UE (104) to report current location or measurement status information to a network entity to support updating RNA configuration and to support recovery of prediction-based operation. These fallback actions maintain service continuity during non-optimal conditions,including GNSS signal loss, missing ephemeris updates, rapidly changing satellite coverage, or temporary unavailability of network-side responses.
[0126] In an exemplary embodiment, the present disclosure operates by enabling a User Equipment (UE) to autonomously predict an RNA boundary crossing and initiate an RNA update procedure in advance of the crossing. For example, the UE determines its geographic position using positioning measurements and is located at a latitude of 28.6139° and a longitude of 77.2090°. The UE obtains an RNA boundary definition from configuration information and identifies a nearest RNA boundary point located at a latitude of 28.7041° and a longitude of 77.1025°. Using these coordinates, an RNA prediction module of the UE computes a geodesic distance between the UE and the RNA boundary using a Haversine-based distance computation, resulting in an estimated distance of approximately 14 kilometers (14,000 meters). The UE further receives satellite ephemeris data and determines satellite ground-relative movement influencing the RNA boundary. Based on the ephemeris data, a satellite velocity component directed toward the RNA boundary is determined to be approximately 7500 m / s, and based on positioning measurements, a UE velocity component is determined to be approximately 20 m / s. The RNA prediction module computes a relative velocity of approximately 7480 m / s between the satellite ground-relative movement and UE motion toward the RNA boundary. Using the computed distance and relative velocity, the RNA prediction module estimates a remaining time duration to RNA boundary crossing as T_exit, for example T_exit ~ 14,000 / 7,480 - 1.87 seconds. In accordance with the present disclosure, the UE compares the estimated T exit with a hysteresis threshold configured at the UE, and when T exit falls below the hysteresis threshold, the UE proactively triggers an RNA update procedure by transmitting a resume request message prior to the UE reaching the RNA boundary. For instance, when the hysteresis threshold is configured to about 5 seconds, the UE determines that T exit (~ 1.87 seconds) is below the hysteresis threshold and initiates the RNA update procedure. In another illustrative example, when the hysteresis threshold is configured to about 1second, the UE determines that T exit exceeds the hysteresis threshold and defers initiation of the RNA update procedure until a subsequent evaluation cycle. The hysteresis threshold may be dynamically adjusted based on satellite movement speed or RNA geographic dimensions. The numerical values described herein are exemplary and do not limit the scope of the present disclosure.
[0127] In an embodiment, one or more of the receiving unit (224), the GNSS module (210), the velocity and position module (212), the RNA prediction module (214), the dynamic hysteresis module (216), the triggering module (218), and the fallback procedure module (220) are implemented in software and integrated into the UE (104). In an embodiment, the modules are implemented as program instructions stored in a memory of the UE (104) and executed by one or more processors of the UE (104), and the modules exchange data using internal interfaces of the UE (104). In an embodiment, the software-based implementation supports updates to prediction parameters, threshold settings, and fallback behavior without requiring hardware modification, and supports adaptation to different satellite configurations, different RNA planning strategies, and different ephemeris update periodicities. In an embodiment, at least a portion of configuration information, prediction state, reliability indicators, and thresholds is stored in a database (222) accessible by the modules for performing prediction, triggering, and fallback operations.
[0128] FIG. 3 illustrates an exemplary system architecture (300) of the system (108) for managing the mobility of the UE (104) in the network (106), in accordance with an embodiment of the present disclosure. FIG. 3 is explained in conjunction with FIG. 1 and FIG. 2.
[0129] The system architecture (300) includes the UE (104) and the network (106), which may comprise a 5G network operating in satellite-based deployments. The UE (104) and the network (106) interact to manage Radio Access Network (RAN) Notification Area (RNA) update procedures by enabling autonomous, prediction-basedmobility handling at the UE (104), thereby reducing reliance on reactive network-triggered updates.
[0130] As illustrated in FIG. 3, the UE (104) comprises multiple functional modules that cooperate to estimate RNA boundary crossings and initiate RNA update procedures. The modules include a Global Navigation Satellite System (GNSS) module (210), a velocity and position module (212), a Radio Access Network (RAN) Notification Area (RNA) prediction module (214), a dynamic hysteresis module (216), a triggering module (218), and a fallback procedure module (220). The internal arrows within the UE (104) depict data flow between these modules, enabling coordinated mobility prediction and decision-making.
[0131] In an embodiment, the GNSS module (210) is configured to receive and decode satellite-based positioning signals to determine positioning measurements associated with the UE (104), including latitude and longitude, and optionally altitude and timestamp information. The GNSS module (210) periodically refreshes the positioning measurements and provides the positioning data to the velocity and position module (212) and other modules within the UE (104) to support continuous or periodic mobility prediction. In an embodiment, the velocity and position module (212) processes the positioning measurements obtained from the GNSS module (210) and computes a current UE position and a UE velocity vector. The UE velocity vector represents both magnitude and direction of UE movement across the Earth’s surface. The computed position and velocity information is forwarded to the RNA prediction module (214).
[0132] In an embodiment, the RNA prediction module (214) receives satellite ephemeris data broadcast by the gNodeB (gNB) (302) of the network (106). In an embodiment, the network (106) includes a satellite ephemeris broadcast module (304) that delivers satellite ephemeris data to the UE (104). The satellite ephemeris data provides satellite state information used to determine satellite footprint movementrelative to the Earth’s surface. In an embodiment, the RNA prediction module (214) combines the satellite ephemeris data with the current UE position and the UE velocity vector obtained from the velocity and position module (212) to estimate an RNA boundary crossing time duration (T exit). The RNA prediction module (214) determines a remaining distance to the RNA boundary, computes a relative velocity between satellite ground-relative movement and UE movement toward the RNA boundary, and estimates T exit using these values. The RNA prediction module (214) updates the estimated boundary crossing time as new GNSS measurements and ephemeris updates become available and outputs RNA boundary predictions to the dynamic hysteresis module (216).
[0133] In an embodiment, the dynamic hysteresis module (216) receives the estimated RNA boundary crossing time and related prediction information from the RNA prediction module (214) and determines a hysteresis threshold for RNA update triggering. The dynamic hysteresis module (216) adapts the hysteresis threshold based on factors including satellite movement speed derived from ephemeris data and geographic dimensions of the RNA, thereby suppressing unnecessary RNA update initiation caused by transient fluctuations or short-term boundary shifts.
[0134] In an embodiment, the triggering module (218) evaluates the estimated RNA boundary crossing time duration (T exit) against the hysteresis threshold based on one or more triggering criteria. When T exit indicates an imminent boundary crossing and satisfies the criteria, the triggering module (218) initiates an RNA update procedure by transmitting a resume request message toward the gNB (302). This interaction enables proactive RNA update initiation and reduced signalling overhead.
[0135] In an embodiment, the fallback procedure module (220) operates in coordination with the triggering module (218) to monitor the status of the RNA update procedure following transmission of the resume request message. The fallback procedure module (220) initiates fallback actions when prediction-based triggeringdoes not result in a successful RNA update or when prediction inputs become unavailable or unreliable. Examples include failure to receive a network response within a predefined time window, degraded GNSS measurements, loss of ephemeris updates, or low confidence in motion estimates.
[0136] In an embodiment, the fallback procedure module (220) initiates conventional RNA update procedures that do not rely on prediction inputs. The UE (104) may revert to RNA updates triggered by cell reselection events detected through radio measurements or by expiry of a periodic timer. The fallback procedure module (220) may also initiate recovery actions, including reinitialization of the GNSS module (210), requesting refreshed ephemeris data, and re-evaluation of input reliability, before re-enabling prediction-based triggering.
[0137] In an embodiment, the network (106) includes the gNB (302), which receives RNA update signalling from the UE (104) and provides configuration information in response. The gNB (302) is configured to deliver updated RNA configuration parameters to the UE (104). In an embodiment, the network (106) further includes an RNA configuration management module (306) that maintains and updates RNA-related configuration data. The RNA configuration management module (306) manages RNA definitions, including RAN-NotificationArealnfo, suspended-state configuration information, and UE-specific RNA policies, and operates in coordination with the gNB (302) to generate and provide updated RNA configuration parameters to the UE (104) following an RNA update procedure.
[0138] In an embodiment, the RNA configuration management module (306) is responsible for managing and maintaining RNA related configuration information applicable to the UE. The RNA definitions managed by the RNA configuration management module (306) include the RAN-NotificationArealnfo, which specifies the RNA structure and boundaries using information such as a cell list, tracking area code, or geographic attributes used by the UE to determine RNA membership. The RNAconfiguration management module (306) further manages the suspended-state configuration information that defines how the UE operates while in a suspended or inactive connection state, including parameters related to paging, resume behavior, and mobility handling during the suspended period.
[0139] In an embodiment, the RNA configuration management module (306) manages UE-specificRNA policies, which define policy rules or constraints applicable to individual UEs or classes of UEs. Examples of UE-specific RNA policies include priority handling rules, mobility assistance parameters, hysteresis configuration preferences, validity intervals for RNA definitions, and conditions under which RNA update procedures may be triggered or deferred.
[0140] The RNA configuration management module (306) operates in coordination with the gNB (302) to generate updated RNA configuration parameters when an RNA update procedure is performed. In response to an RNA update request from the UE, the RNA configuration management module (306) determines an appropriate RNA configuration based on current network conditions, satellite coverage characteristics, and UE mobility information, and provides the updated RNA configuration parameters to the UE via signaling through the gNB (302). The updated RNA configuration parameters enable the UE to maintain accurate RNA association, continue prediction-based RNA boundary monitoring, and perform subsequent RNA update decisions in accordance with the updated network configuration.
[0141] In an embodiment, the system architecture (300) illustrated in FIG. 3 enables a coordinated mobility management framework in which the UE autonomously predicts RNA boundary crossings based on satellite ephemeris data and UE mobility information, while the network dynamically responds with updated RNA configuration parameters. The interaction between the UE-side prediction, hysteresis, triggering, and fallback modules and the network-side gNodeB and RNA configuration management module allows RNA updates to be performed proactively when necessary andconservatively when conditions are stable. This architecture reduces redundant signalling, improves power efficiency at the UE, and ensures continuity of mobility management under dynamically changing satellite coverage conditions, while maintaining compatibility with conventional RNA update procedures when prediction inputs become unavailable.
[0142] FIG. 4 illustrates an exemplary flow diagram of a method (400) for managing mobility of the User Equipment (UE) (104) in the network (106) in accordance with an embodiment of the present disclosure. FIG. 4 is explained in conjunction with FIG. 1, FIG. 2, and FIG. 3.
[0143] In the flow diagram of FIG. 4, branch links labeled A, B, and C represent control-flow transitions that connect different stages of the method (400) and enable continuous, conditional execution of mobility management operations.
[0144] At step 402, the method (400) includes the UE (104) receiving initial configuration parameters from the network (106). The initial configuration parameters include Radio Access Network (RAN) Notification Area definition information provided through RAN-NotificationArealnfo. The RNA definition specifies a currently registered RNA for the UE (104) and may comprise a cell list and / or a Tracking Area Code (TAC) that identifies a group of coverage regions associated with the RNA. The initial configuration parameters further include satellite ephemeris data received as part of NTN-Config information elements broadcast by a base station and dynamic RNA prediction configuration parameters, including threshold settings, hysteresis control parameters, monitoring intervals, and validity timers. In an embodiment, the RNA prediction configuration parameters define operational settings used by the UE to control prediction-based RNA update behavior. The RNA prediction configuration parameters include one or more threshold settings that specify conditions under which an RNA update procedure is initiated based on an estimated remaining time duration before an RNA boundary crossing. The RNA prediction configuration parametersfurther include hysteresis control parameters that define hysteresis thresholds and, where applicable, hysteresis margins used to suppress oscillatory or repeated RNA update triggering caused by transient variations in estimated boundary crossing conditions. In an embodiment, the RNA prediction configuration parameters also include monitoring intervals that specify a periodic time duration at which the UE re-evaluates positioning data, satellite movement, and RNA boundary prediction, thereby establishing a continuous monitoring loop. The RNA prediction configuration parameters further include validity timers that define a duration for which the configuration data, satellite ephemeris data, or derived prediction inputs are considered valid, after which the UE performs re-evaluation, refresh, or fallback operations. Collectively, the RNA prediction configuration parameters enable adaptive, controlled, and reliable RNA boundary prediction and update decision-making under dynamic satellite coverage conditions.
[0145] At step 404, the UE (104) stores the received initial configuration parameters in the database (222). The stored parameters provide persistent access to RNA definitions, satellite ephemeris data, and prediction configuration values and are used by subsequent UE-side modules for boundary prediction, hysteresis adjustment, and triggering decisions without requiring repeated network interaction.
[0146] At step 406, the method (400) includes the UE (104) obtaining Global Navigation Satellite System (GNSS) data using an embedded GNSS module (210). The GNSS data includes a current geographic position of the UE (104), represented by latitude and longitude (P_ue), and a real-time UE velocity vector (V ue) that describes magnitude and direction of UE movement across the Earth’s surface. The GNSS module (210) may periodically refresh the position and velocity measurements to support continuous or periodic evaluation of UE mobility.
[0147] At step 408, the UE (104) evaluates reliability of the obtained GNSS data. The reliability check may be based on one or more quality indicators including positioning confidence, signal availability, consistency of successive measurements, or freshness relative to a validity interval. This step ensures that RNA boundary prediction is performed only when reliable motion and position inputs are available.
[0148] At step 410, if the GNSS data is determined to be unreliable (“No”), the method (400) branches to step 426 to initiate fallback operation. If the GNSS data is determined to be reliable (“Yes”), the method (400) proceeds to step 412 to perform satellite-assisted prediction-based processing. In an embodiment, the branching at step 410 determines whether the UE proceeds with prediction-based mobility management or transitions to fallback operation. When the GNSS data is determined to be unreliable (“No”), branch B directs the execution flow to step 426, indicating that prediction-based RNA boundary estimation cannot be reliably performed using the available positioning inputs. This condition may arise, for example, when GNSS measurements are unavailable, degraded beyond a configured reliability threshold, inconsistent across successive measurement intervals, or stale relative to a validity interval. By following branch B, the UE avoids relying on inaccurate prediction inputs and initiates fallback handling using conventional RNA update mechanisms to preserve reachability and network awareness. Conversely, when the GNSS data is determined to be reliable (“Yes”), the execution flow proceeds to step 412 to enable satellite-assisted prediction-based processing using refreshed positioning and ephemeris information.
[0149] At step 412, the UE (104) computes satellite position information from the received satellite ephemeris data. This computation includes determining current and future satellite positions, a satellite velocity vector (V sat), and an associated satellite beam coverage area or footprint. The computed satellite motion information representsground-relative movement of the satellite coverage region that influences RNA boundary dynamics.
[0150] At step 414, the UE (104) predicts an RNA boundary crossing event. This step includes determining a relative movement between the UE (104) and the RNA boundary by combining UE motion information and satellite ground-relative motion. The UE (104) computes a relative velocity (V rel) using vector components of the satellite ground-relative speed (V_sat) and the UE velocity vector (V_ue) directed toward the RNA boundary, for example V_rel = V_sat - V_ue. The UE (104) further computes a remaining distance to the RNA boundary, denoted as d(t), using a geodesic distance computation such as a Haversine-based formula applied to UE position coordinates and RNA boundary coordinates. Based on d(t) and |V_rel|, the UE (104) computes a remaining time duration to RNA boundary crossing denoted as T exit, for example T_exit = d(t) / |V_rel|.
[0151] At step 416, the method (400) includes applying dynamic hysteresis criteria to the predicted RNA boundary crossing time duration (T exit). The UE (104) adjusts a hysteresis threshold based on parameters such as satellite movement speed, geographic dimensions of the RNA, and mobility characteristics of the UE. For instance, when satellite movement speed is high or the RNA has small geographic dimensions, the hysteresis threshold may be increased to initiate RNA updates earlier, while under stable conditions or larger RNA regions the hysteresis threshold may be reduced to suppress premature or unnecessary triggers.
[0152] At step 418, a decision is made based on a comparison between the predicted time duration T exit and the hysteresis threshold. If the comparison indicates that T exit falls below the hysteresis threshold (“Yes”), the method (400) proceeds to step 420 to initiate an RNA update. If the comparison indicates that the threshold is not satisfied (“No”), the method (400) proceeds to step 424, and the UE (104) continues monitoring without initiating immediate action.
[0153] At step 420, the UE (104) triggers an RNA update procedure by transmitting a resume request message, such as an RRCResumeRequest, to the network (106). The resume request message indicates that an RNA update is required in anticipation of an imminent boundary crossing and allows the network (106) to prepare updated RNA configuration information in advance of the actual crossing event.
[0154] At step 422, upon receiving the resume request message, the network (106), including a base station, updates RNA configuration parameters associated with the UE (104). The network responds by transmitting updated suspended-state configuration information and updated RAN-NotificationArealnfo to the UE (104). The updated RNA configuration aligns the UE (104) with a new or modified RNA definition, thereby completing the proactive RNA update procedure.
[0155] At step 424, following RNA configuration update or when the hysteresis threshold is not met, the UE (104) continues monitoring its position and velocity relative to RNA boundaries. No immediate RNA update action is taken, and the UE (104) prepares for subsequent evaluation cycles.
[0156] At step 426, when reached due to unreliable GNSS data or unavailable prediction inputs, the method (400) initiates a fallback procedure. In fallback operation, the UE (104) disables prediction-based triggering and reverts to conventional RNA update mechanisms to maintain reachability and network awareness of UE location.
[0157] At step 428, the UE (104) determines whether a fallback trigger condition has been met. A fallback trigger condition corresponds to a condition in which prediction-based RNA update cannot be reliably performed or has failed to complete successfully. Examples of fallback trigger conditions include a coverage change event such as cell reselection detected by radio measurements, expiration of a periodic RNA update timer, failure to receive a response from the network within a predefined time window after transmission of a resume request message, loss or degradation of GNSSmeasurements beyond a reliability threshold, unavailability or staleness of satellite ephemeris data beyond a validity interval, or repeated inability to compute a reliable RNA boundary crossing time. In an embodiment, detection of any of the fallback trigger conditions causes the UE (104) to enter fallback operation.
[0158] At step 430, when a fallback trigger condition is met (“Yes”), the UE (104) initiates a standard RNA update procedure by transmitting an RRCResumeRequest to the network (106), independently of prediction-based RNA boundary estimation. For example, when the UE (104) detects that Global Navigation Satellite System (GNSS) positioning measurements are unavailable or unreliable for a predetermined duration, or when satellite ephemeris data is no longer valid due to expiration of a validity interval, the UE (104) determines that predictive RNA boundary estimation cannot be reliably performed. In such a scenario, the UE (104) initiates the standard RNA update procedure upon detection of a fallback trigger, such as expiration of a periodic RNA update timer or a cell reselection event detected by radio measurements. The standard RNA update procedure enables the UE (104) to update its RNA registration using conventional triggering mechanisms, thereby ensuring continuity of mobility management and maintaining network awareness of the UE location when prediction-based operation is unavailable or unreliable.
[0159] At step 432, upon receiving the standard RNA update request, the network (106) updates the RNA configuration for the UE (104) and transmits a standard RNA update response. The UE (104) stores the updated RNA configuration parameters for continued operation.
[0160] At step 434, when no fallback trigger condition is met (“No”), the UE (104) continues monitoring satellite movement and UE positioning information without initiating an RNA update. For example, when Global Navigation Satellite System (GNSS) measurements remain available and reliable, satellite ephemeris data is valid within a defined validity interval, no periodic RNA update timer has expired, and nocell reselection event is detected, the UE (104) determines that fallback operation is not required. In such a scenario, the UE (104) maintains prediction-based RNA boundary monitoring and periodically re-evaluates relative movement and estimated boundary crossing time without transmitting an RNA update request.
[0161] At step 436, the method (400) periodically repeats the monitoring and evaluation steps at a configured interval, for example every 10 seconds, thereby forming a continuous feedback loop for RNA update management. The loop supports ongoing prediction-based operation when inputs are reliable and seamless transition to fallback operation when required. In an embodiment, branch C represents a convergence and loop-back transition that returns execution to the periodic monitoring stage after completion of different mobility management outcomes. Branch C connects multiple exit points of the method (400), including completion of the proactive RNA update procedure at step 422, continuation without immediate action at step 424, completion of fallback- based RNA update handling at step 432, and continued monitoring during fallback operation at step 434. Through branch C, the execution flow is directed to step 436, which defines a periodic check interval. After completion of the periodic check interval at step 436, the execution flow follows branch A and returns to step 406, where the UE again obtains updated GNSS position and velocity information. Using the configuration parameters previously stored at step 404, the UE resumes prediction-based mobility monitoring and evaluation for subsequent RNA boundary crossing decisions. In an embodiment, the periodic check interval at step 436 is configured as a predefined time duration after which the UE resumes mobility evaluation through branch A. For example, the periodic check interval may be configured as about 10 seconds, such that the UE waits for approximately 10 seconds after reaching the convergence point represented by branch C before re-entering the mobility monitoring flow at step 406. During this interval, the UE does not initiate RNA update signalling unless a fallback trigger condition occurs. After expiration of the 10-second interval, the UE obtains updated GNSS position and velocityinformation and repeats RNA boundary prediction and hysteresis evaluation using the stored configuration parameters. Non-limiting examples of the periodic check interval include about 5 seconds, 10 seconds, 20 seconds, or 30 seconds.
[0162] Accordingly, FIG. 4 illustrates a closed-loop mobility management method that combines satellite-assisted prediction, adaptive hysteresis-controlled triggering, proactive RNA updates, and robust fallback mechanisms to efficiently manage RNA updates for a UE in satellite-assisted network environments.
[0163] FIG. 5 illustrates an exemplary flow diagram of a method (500) for managing mobility of a User Equipment (UE) (104) in a network (106). FIG. 5 is explained in conjunction with the FIGs. 1, 2, 3 and 4.
[0164] At step (502), the method includes receiving, by a receiving unit of the UE, satellite ephemeris data from a gNodeB of the network. The satellite ephemeris data is received as part of configuration signalling and includes parameters defining orbital characteristics and motion of a serving satellite, such as satellite position information, satellite velocity information, orbital trajectory parameters, timestamped position and velocity vectors, orbital altitude, inclination, and ground-track related parameters associated with movement of a satellite coverage footprint across the Earth’s surface.
[0165] At step (504), the method includes obtaining, by a velocity and position module of the UE, a UE velocity vector based on Global Navigation Satellite System (GNSS) measurements obtained from a GNSS module of the UE. The GNSS measurements include a current UE position represented by latitude and longitude and successive positioning samples used to derive a UE velocity vector indicating magnitude and direction of UE motion.
[0166] At step (506), the method includes estimating, by a Radio Access Network (RAN) Notification Area (RNA) prediction module of the UE, a time duration at whichthe UE is expected to cross a boundary of a currently registered RNA based on the satellite ephemeris data and the UE velocity vector. In an embodiment, the RNA prediction module derives a satellite ground-relative speed from the satellite ephemeris data and computes a relative velocity between the satellite ground-relative movement and the UE velocity vector directed toward the RNA boundary. The relative velocity represents an effective closing speed and may be expressed as V_rel = V_sat - V_ue, where V_sat represents satellite ground-relative speed toward the RNA boundary and V_ue represents UE movement toward the RNA boundary.
[0167] In an embodiment, the RNA prediction module further computes a distance from the UE to the RNA boundary, denoted as d(t). The distance d(t) is computed as a geodesic distance between the current UE position and RNA boundary coordinates obtained from RNA definition information. In an embodiment, the geodesic distance is computed using a Haversine-based formula applied to latitude and longitude coordinates.
[0168] Based on the computed distance and the relative velocity, the RNA prediction module estimates a remaining time duration to RNA boundary crossing, expressed as: T_exit = d(t) / |V_rel|, where T_exit represents a remaining time before the UE is expected to exit the currently registered RNA.
[0169] At step (508), the method includes causing, by a triggering module of the UE, initiation of an RNA update procedure when the estimated time duration T exit falls below a threshold. In an embodiment, the threshold is implemented as a hysteresis threshold that defines a minimum remaining time duration for initiating the RNA update procedure and suppresses unnecessary or premature RNA update triggering.
[0170] In an embodiment, a dynamic hysteresis module of the UE adjusts the hysteresis threshold based on parameters that include satellite orbital speed and geographic dimensions of the RNA, both derived from satellite ephemeris data andstored RNA definition information. The hysteresis threshold may be increased under rapidly changing satellite coverage conditions to initiate RNA updates earlier and decreased under stable conditions to reduce unnecessary signalling.
[0171] When the estimated time duration T exit falls below the hysteresis threshold, the triggering module transmits a resume request message, such as an RRCResumeRequest, to the gNodeB prior to the UE crossing the RNA boundary. In response, the gNodeB transmits updated RNA configuration parameters to the UE, including updated suspended-state configuration information and updated RAN-NotificationArealnfo defining a new or modified RNA assignment.
[0172] Accordingly, FIG. 5 illustrates a mobility management method in which the UE receives satellite ephemeris data and GNSS -based mobility information, computes relative velocity, distance, and estimated RNA boundary crossing time using defined mathematical relationships, applies adaptive hysteresis-controlled triggering, and proactively initiates RNA update procedures, thereby enabling efficient and robust RNA update handling in satellite-assisted network environments.
[0173] In an embodiment, a system (108) for managing mobility of a User Equipment (UE) (104) in a network (106) is disclosed. The system (108) comprises a receiving unit (224) of the UE (104) configured to receive satellite ephemeris data from a gNodeB. The system (108) comprises a velocity and position module (212) of the UE (104) configured to obtain a UE velocity vector based on Global Navigation Satellite System (GNSS) measurements obtained from a GNSS module (210) of the UE (104). The system (108) comprises a Radio Access Network (RAN) Notification Area (RNA) prediction module (214) of the UE (104) configured to estimate a time duration until the UE (104) is expected to cross a boundary of an RNA based on the received satellite ephemeris data and the obtained UE velocity vector. The system (108) comprises a triggering module (218) of the UE (104) configured to initiate an RNA update procedure when the estimated time duration is below a threshold.
[0174] In yet another embodiment, a computer program product including a non-transitory computer-readable medium is disclosed. The computer-readable medium includes instructions that, when executed by one or more processors, cause the one or more processors of a User Equipment (UE) (104) to execute a method for managing mobility of the UE (104) in a network (106). The method includes receiving, by a receiving unit (224) of the UE (104), satellite ephemeris data from a gNodeB. The method further includes obtaining, by a velocity and position module (212) of the UE (104), a UE velocity vector based on Global Navigation Satellite System (GNSS) measurements associated with the UE (104) and obtained from a GNSS module (210) of the UE (104). The method further includes estimating, by a Radio Access Network (RAN) Notification Area (RNA) prediction module (214) of the UE (104), a time duration at which the UE (104) is expected to cross a boundary of an RNA based on the received satellite ephemeris data and the obtained UE velocity vector. The method further includes causing, by a triggering module (218) of the UE (104), initiation of an RNA update procedure when the estimated time duration falls below a threshold.
[0175] FIG. 6 illustrates an exemplary computer system (600) in which or with which embodiments of the present disclosure may be implemented.
[0176] As shown in FIG. 6, the computer system (600) may include an external storage device (610), a bus (620), a main memory (630), a read-only memory (640), a mass storage device (650), communication port(s) (660), and a processor (670). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (670) may include various modules associated with embodiments of the present disclosure.
[0177] The communication port(s) (660) may be any of an RS-232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) (660) may be chosen depending on a network, such a LocalArea Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.
[0178] The main memory (630) may be random access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (640) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (670).
[0179] The mass storage device (650) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage device (650) includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.
[0180] The bus (620) communicatively couples the processor (670) with the other memory, storage, and communication blocks. The bus (620) may be, e.g., a Peripheral Component Interconnect (PCI) / PCI Extended (PCLX) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (670) to the computer system.
[0181] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (620) to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (660). Components described above are meant only toexemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.
[0182] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.
[0183] The present disclosure provides a technical advancement by addressing limitations of conventional RNA update mechanisms in satellite-based network deployments in which a UE in an inactive state relies primarily on cell reselection events or periodic timers for RNA updates. Such conventional approaches may lead to frequent and unnecessary RNA updates for stationary or low-mobility UEs due to rapid satellite movement, resulting in excessive signalling overhead, increased UE battery consumption, and inefficient use of network resources. The present disclosure overcomes these issues by enabling the UE to autonomously estimate future RNA boundary crossings using a combination of UE velocity information and satellite ephemeris data and to initiate RNA update procedures proactively based on an estimated remaining time duration before boundary crossing. By triggering RNA updates only when the estimated boundary crossing time satisfies adaptive hysteresis criteria, the disclosed approach significantly reduces redundant signalling, improves UE battery efficiency by minimizing wake-ups from low-power states, enhances mobility robustness and reachability in dynamic satellite coverage environments, and lowers overall network processing load, thereby providing a scalable and efficient solution for RNA management in satellite-assisted networks.
[0184] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.
[0185] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.TECHNICAL ADVANTAGES
[0186] The present disclosure, as described above, offers several significant technical advantages that enhance the functionality and efficiency of the network, including, but not limited to:
[0187] In an embodiment, the present disclosure reduces signalling overhead by enabling the User Equipment (UE) to proactively manage Radio Access Network (RAN) Notification Area (RNA) update procedures based on predicted RNA boundary crossings, thereby minimizing unnecessary signalling exchanges that would otherwisebe triggered by periodic timers or coverage change events in high-latency Non- Terrestrial Network (NTN) environments.
[0188] In an embodiment, the present disclosure improves power efficiency of the UE by reducing the frequency of wake-ups from low-power or inactive states for RNA update procedures. By initiating RNA updates only when a predicted boundary crossing satisfies adaptive hysteresis criteria, the UE conserves battery power while maintaining required reachability and mobility tracking.
[0189] In an embodiment, the present disclosure enhances mobility robustness by accurately estimating RNA boundary crossing events using satellite ephemeris data and UE motion information, and by initiating RNA updates in advance of actual boundary crossings. This predictive approach reduces missed paging events, improves continuity of ongoing services, and enhances responsiveness of the UE in rapidly changing satellite coverage environments.
[0190] In an embodiment, the present disclosure improves overall network efficiency by avoiding redundant RNA update procedures and reducing control-plane signalling load at network nodes. This reduction in unnecessary signalling lowers processing overhead and improves utilization of limited radio and backhaul resources, which is particularly beneficial in bandwidth- constrained satellite-based networks.
[0191] In an embodiment, the present disclosure improves stability of mobility management by applying adaptive hysteresis thresholds that account for satellite movement speed, RNA geographic dimensions, and UE mobility status. This adaptive hysteresis mechanism suppresses oscillatory triggering caused by transient boundary movement or short-term measurement fluctuations, resulting in fewer spurious RNA updates.
[0192] In an embodiment, the present disclosure increases scalability by enabling each UE to autonomously perform RNA boundary prediction and triggering decisionswithout continuous network intervention. This distributed processing model reduces centralized computation burden and enables the network to support a large number of UEs under rapidly changing satellite coverage conditions.
[0193] In an embodiment, the present disclosure improves reliability through a coordinated fallback mechanism that ensures continued RNA update operation when prediction inputs such as Global Navigation Satellite System (GNSS) measurements or satellite ephemeris data become unavailable or unreliable. By reverting to conventional RNA update triggers only when necessary, the system maintains service continuity without sacrificing the benefits of prediction-based operation.
[0194] In an embodiment, the present disclosure provides backward-compatible operation by integrating predictive RNA updates with existing RNA update signaling flows, thereby enabling gradual deployment without requiring fundamental changes to network infrastructure or UE radio procedures.
Claims
CLAIMS1. A method (500) for managing mobility of a User Equipment (UE) (104) in a network (106), the method (500) comprising:receiving (502), by a receiving unit (224) of the UE (104), satellite ephemeris data from a gNodeB;obtaining (504), by a velocity and position module (212) of the UE (104), a UE velocity vector based on Global Navigation Satellite System (GNSS) measurements associated with the UE (104) obtained from a GNSS module (210) of the UE (104);estimating (506), by a Radio Access Network (RAN) Notification Area (RNA) prediction module (214) oftheUE (104), a time duration at which the UE (104) is expected to cross a boundary of a RNA based on the received satellite ephemeris data and the obtained UE velocity vector; andcausing (508), by a triggering module (218) of the UE (104), initiation of an RNA update procedure when the estimated time duration is below a threshold.
2. The method (500) as claimed in claim 1, further comprising:deriving, by the RNA prediction module (214), a satellite ground-relative speed from the received satellite ephemeris data;computing, by the RNA prediction module (214), a relative velocity between the satellite ground-relative speed and the UE velocity vector toward the RNA boundary; andcomputing, by the RNA prediction module (214), a distance from the UE (104) to the RNA boundary.
3. The method (500) as claimed in claim 2, wherein the time duration is estimated based on the computed relative velocity and the distance from the UE (104) to the RNA boundary.
4. The method (500) as claimed in claim 2, wherein the distance from the UE (104) to the RNA boundary is a geodesic distance computed by a haversine formula.
5. The method (500) as claimed in claim 1, wherein the threshold is a hysteresis threshold; and wherein the hysteresis threshold defines a minimum remaining time duration for initiating the RNA update procedure.
6. The method (500) as claimed in claim 5, wherein a dynamic hysteresis module (216) of the UE (104) adjusts the threshold based on one or more of a satellite orbital speed and geographic dimensions of the RNA, wherein the satellite orbital speed and the geographic dimensions of the RNA are derived from the satellite ephemeris data.
7. The method (500) as claimed in claim 1, wherein the triggering module (218) transmits a resume request message indicating the initiation of the RNA update procedure to the gNodeB when the estimated time duration is below the threshold.
8. The method (500) as claimed in claim 7, wherein, in response to reception of the resume request message, the gNodeB transmits updated RNA configuration parameters to the UE (104).
9. A system (108) for managing mobility of a User Equipment (UE) (104) in a network (106), the system (108) comprising:a receiving unit (224) of the UE (104) configured to receive satellite ephemeris data from a gNodeB;a velocity and position module (212) of the UE (104) configured to obtain a UE velocity vector based on Global Navigation Satellite System (GNSS)measurements associated with the UE (104) obtained from a GNSS module (210) of the UE (104);a Radio Access Network (RAN) Notification Area (RNA) prediction module (214) of the UE (104) configured to estimate a time duration at which the UE (104) is expected to cross a boundary of a RNA based on the received satellite ephemeris data and the obtained UE velocity vector; anda triggering module (218) of the UE (104) configured to cause initiation of an RNA update procedure when the estimated time duration is below a threshold.
10. The system (108) as claimed in claim 9, wherein the RNA prediction module (214) is configured to:derive a satellite ground-relative speed from the received satellite ephemeris data;compute a relative velocity between the satellite ground-relative speed and the UE velocity vector toward the RNA boundary; andcompute a distance from the UE (104) to the RNA boundary.
11. The system (108) as claimed in claim 10, wherein the time duration is estimated based on the computed relative velocity and the distance from the UE (104) to the RNA boundary.
12. The system (108) as claimed in claim 10, wherein the distance from the UE (104) to the RNA boundary is a geodesic distance computed by a haversine formula.
13. The system (108) as claimed in claim 9, wherein the threshold is a hysteresis threshold; and wherein the hysteresis threshold defines a minimum remaining time duration for initiating the RNA update procedure.
14. The system (108) as claimed in claim 13, wherein a dynamic hysteresis module (216) of the UE (104) adjusts the threshold based on one or more of a satellite orbital speed and geographic dimensions of the RNA, wherein the satellite orbital speed and the geographic dimensions of the RNA are derived from the satellite ephemeris data.
15. The system (108) as claimed in claim 9, wherein the triggering module (218) transmits a resume request message indicating the initiation of the RNA update procedure to the gNodeB when the estimated time duration is below the threshold.
16. The system (108) as claimed in claim 15, wherein, in response to reception of the resume request message, the gNodeB transmits updated RNA configuration parameters to the UE (104).
17. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (500) for managing mobility of a User Equipment (UE) (104) in a network (106), the method (500) comprising:receiving (502), by a receiving unit (224) of the UE (104), satellite ephemeris data from a gNodeB;obtaining (504), by a velocity and position module (212) of the UE (104), a UE velocity vector based on Global Navigation Satellite System (GNSS) measurements associated with the UE (104) obtained from a GNSS module (210) of the UE (104);estimating (506), by a Radio Access Network (RAN) Notification Area (RNA) prediction module (214) oftheUE (104), a time duration at which the UE (104) is expected to cross a boundary of a RNA based on the received satellite ephemeris data and the obtained UE velocity vector; andcausing (508), by a triggering module (218) of the UE (104), initiation of an RNA update procedure when the estimated time duration is below a threshold.
