Method and system for managing a user equipment context in a network
The introduction of S1AP procedures for suspending and resuming UE contexts addresses LTE inefficiencies in non-terrestrial networks, enhancing IoT reliability and reducing disruptions by maintaining session continuity and minimizing signaling.
Patent Information
- Application Number
- PCT/IN2026/050790
- 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
Existing LTE systems face inefficiencies and disruptions due to frequent connectivity losses in non-terrestrial networks, particularly satellite-based IoT environments, leading to excessive signaling, power consumption, and service disruptions from full reattachment cycles.
Introduce SI Application Protocol (S1AP) procedures for suspending and resuming UE contexts at the eNodeB and MME level, allowing the eNodeB to buffer data and the MME to maintain a suspended session state, ensuring seamless continuity during intermittent connectivity.
Minimizes signaling overhead, reduces power consumption, and maintains session reliability by avoiding full reattachments, optimizing satellite-based LTE systems for IoT applications.
Smart Images

Figure IN2026050790_12112026_PF_FP_ABST
Abstract
Description
METHOD AND SYSTEM FOR MANAGING A USER EQUIPMENT CONTEXT IN A NETWORKRESERVATION 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. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD
[0002] The present disclosure relates generally to the field of communication systems. More particularly, the present disclosure relates to a system and method for managing a user equipment (UE) context between an evolved Node B (eNodeB) and a Mobility Management Entity (MME) in a network.DEFINITION
[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 to indicate otherwise.
[0004] The term “User Equipment (UE)”, as used herein, refers to a device utilized by an end user to communicate within a communication network. The UE may include, but is not limited to, a smartphone, tablet, modem, Internet of Things (loT) device, or any wireless communication device capable of performing channel measurements and reporting channel state information.
[0005] The term ‘MME’ may refer to a Mobility Management Entity, which is a key control node in Long Term Evolution (LTE) networks responsible for handling signaling related to mobility and session management for User Equipments (UEs)
[0006] The term ‘eNodeB’ (Evolved Node B) refers to a base station in the LTE networks that connects directly with the user devices and handles radio communication, including scheduling and resource allocation.
[0007] The term ‘S1AP (SI Application Protocol)’ message may refer to protocol messages exchanged between the eNodeB and the MME over the SI interface, used for signaling (e.g., UE attach, handover, context release).
[0008] The term ‘Serving gateway (S-GW)’ refers to a unit or a device configured to route and / or forward user data packets within the LTE network. The S-GW acts as a local mobility anchor during handovers between eNodeBs.
[0009] The term ‘Non-Terrestrial Network Gateway (NTN-Gateway)’ refers to a gateway that connects terrestrial core networks to non-terrestrial access networks like satellites or high-altitude platforms.
[0010] The term ‘Stream Control Transmission Protocol (SCTP)’ refers to a transport-layer protocol used for message-oriented communication between eNodeB and MME, offering reliable, ordered delivery of signaling messages.
[0011] The term ‘bearers’ refers to logical channels that carry user data with specific QoS (Quality of Service) characteristics through the LTE network.
[0012] The term ‘Non-Access Stratum (NAS)’ refers to a protocol layer used between the UE and the MME for signaling related to mobility management, session management, and authentication.
[0013] The ‘UE context’ refers to a data structure maintained by the MME (and eNodeB) that stores all relevant information about a connected user device, such as IMSI, IP address, bearer info, and security parameters.
[0014] The ‘MME-UE-S1AP-ID’ refers to a unique identifier assigned by the MME to a UE context, which is used to uniquely identify and track the UE within the core network during SI AP signalling procedures.
[0015] The ‘eNB-UE-SlAP-ID’ refers to a local identifier assigned by the eNodeB to a UE context, which is used to uniquely identify the UE within the eNodeB during S1AP signalling and to correlate messages with the corresponding UE context.
[0016] The ‘UEContextSuspendRequest’ refers to an S1AP signalling message initiated by the eNodeB and sent to the MME to request suspension of a UE context, including associated signalling connections and bearer resources, typically in scenarios of expected temporary connectivity interruption.
[0017] The ‘UEContextResumeRequest’ refers to an S1AP signalling message initiated by the eNodeB and sent to the MME to request restoration of a previously suspended UE context, enabling re-establishment of signalling and user-plane resources for the UE.BACKGROUND
[0018] 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 may 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.
[0019] With the evolution of cellular networks such as Long Term Evolution (LTE) and its continued relevance in conjunction with emerging fifth generation (5G) and non-terrestrial network (NTN) infrastructures, maintaining efficient and reliable connectivity between a user equipment (UE) and a core network has become increasingly challenging, particularly in environments with intermittent or non-continuous base station availability. In LTE systems, the Evolved Packet System (EPS) architecture includes a centralized control-plane interface, the SI interface, that connects a base station (eNodeB) to a Mobility Management Entity (MME) in the core network. This interface is designed under the presumption of persistent connectivity, where the base station remains continuously reachable by the MME, except in rare failure scenarios.
[0020] However, when the S 1 interface / link goes down or the eNodeB is unreachable, the MME releases the UE’s SI context, forcing the UE to do a full reconnection / reattachment the next time the network becomes available. This is tolerable for terrestrial networks where the eNB outages are minimal. However, in Non- Terrestrial Network (NTN) scenarios, particularly with satellites that have intermittent connectivity to ground stations, losing the link is not an anomaly but a regular occurrence (e.g., due to satellite orbit, coverage geometry, or feeder link switching).
[0021] The conventional techniques of handling connectivity interruptions introduce multiple inefficiencies, especially in satellite-based Internet of Things (loT) environments. loT devices often have limited battery life and transmit only small amounts of data. If every temporary loss of connectivity forces these devices to fully reattach, the resulting overhead (authentication, bearer setup, internet protocol (IP) allocation) is large. This also leads to significant delays each time the satellite returns or the link is restored, as well as unnecessary signaling that may drain device power. In a store-and-forward (S&F) satellite operation, the satellite eNB can collect uplinkdata from UEs even if it temporarily lacks ground connectivity. Without a new method, the core network (MME and S-GW) incorrectly assumes the UE has detached whenever the satellite eNB is unreachable, discarding any downlink data and forcing a new attach cycle on reconnection.
[0022] The existing techniques for maintaining the loss of connectivity are inefficient, as by default, an unreachable eNB triggers UE context Release. That means the MME tears down the session, removing NAS context and bearers. Although certain NAS-level or RRC-level optimizations exist (e.g., RRC Inactive, NB-IoT’s context retention), they do not properly integrate with the SI interface. The result is that, from the core network perspective, the UE is effectively gone, leading to a full attach next time.
[0023] Further, in satellite systems, once connectivity reappears, all UEs connected to that satellite eNB may attempt reattachment almost simultaneously, causing a signaling storm in the core network. This not only wastes bandwidth but can also overload the MME and lead to longer re-establishment times. The user plane reestablishment for each UE requiring PDN connectivity, authentication, and new IP addresses may lead to significant service disruption or data loss for time-critical loT applications.
[0024] Hence, the key problem is that LTE’s standard approach of context release and forced reattach is fundamentally inefficient and disruptive for environments with frequent or predictable SI link outages, such as LEO / GEO satellites performing store-and-forward for loT devices.
[0025] There is, therefore, a need in the art to provide a method and a system that can mitigate the disadvantages of the prior art.SUMMARY OF THE DISCLOSURE
[0026] In an exemplary embodiment, a method for managing a user equipment (UE) context between an evolved Node B (eNodeB) and a Mobility Management Entity (MME) in a network is disclosed. The method includes steps of detecting, by the eNodeB, a loss of signalling connectivity between the eNodeB and the MME over a SI interface, sending, by the eNodeB, a suspend request message requesting suspension of a UE context associated with the UE to the MME, in response to receipt of the suspend request message, identifying, by the MME, the UE context as suspended and storing one or more elements of UE context information associated with the UE context, identifying, by the eNodeB, a re-establishment of the signalling connectivity between the eNodeB and the MME, upon identification of the re-establishment of the signalling connectivity between the eNodeB and the MME, sending, by the eNodeB, a resume request message to the MME to resume the suspended UE context, and in response to receipt of the resume request message, performing, by the MME, a resume procedure for the suspended UE context.
[0027] The method further includes a step of sending, by the MME, a resume response message to the eNodeB after performing the resume procedure.
[0028] In some embodiments, when the MME determines that at least one of the UE context identified in the suspend request message is unavailable or suspension of the UE context is unsupported, the MME sends a failure response message to the eNodeB indicating failure of the suspension of the UE context.
[0029] In some embodiments, upon successful suspension of the UE context, the MME sends a success response message to the eNodeB indicating success of the suspension of the UE context.
[0030] In some embodiments, upon successful suspension of the UE context, the MME transmits a signalling message via an Sil interface to the S-GW to perform at least one of holding, buffering, delay forwarding or dropping General Packet RadioService (GPRS) Tunnelling Protocol User plane (GTP U) packets for the suspended UE context.
[0031] In some embodiments, the resume procedure performed by the MME includes steps of reactivating, by the MME, the suspended UE context and transmitting, by the MME to the S-GW, a request to re-establish a GTP U tunnel toward the eNodeB.
[0032] In some embodiments, the one or more elements of the UE context information include at least one of a Non-Access Stratum (NAS) security context, an Evolved Packet System (EPS) bearer state, or subscription data associated with the UE.
[0033] In some embodiments, the suspend request message includes at least one of an MME UE SI Application Protocol (AP) Identifier (ID), an eNodeB UE SI AP ID, an information element indicating a duration of the suspension and an information element indicating a cause of the suspension.
[0034] In some embodiments, when the information element indicating the duration of the suspension is available in the suspend request message, the MME determines an indicated suspend interval from the suspend request message and maintains the suspended UE context for at least the indicated suspend interval, and when no resume request message is received before expiry of the determined suspend interval, the MME releases the suspended UE context.
[0035] In some embodiments, the MME includes an identifier in the suspend response message where the identifier is a token allocated by the MME to identify the suspended UE context, and the eNodeB stores the identifier in the resume request message to resume the suspended UE context.
[0036] In some embodiments, the eNodeB buffers uplink user data during a period in which the UE context is suspended, and after re-establishment of the signallingconnectivity over the SI interface and receipt of the resume response message, the eNodeB sends at least a portion of the buffered uplink user data towards the network.
[0037] In some embodiments, in response to being unable to perform at least one of locating the suspended UE context, the method includes steps of restoring the suspended UE context and resuming one or more suspended E-UTRAN Radio Access Bearers (E-RABs), the MME transmits a resume failure message to the eNodeB.
[0038] In some embodiments, upon receipt of the resume failure message, the eNodeB performs at least one of releasing a Radio Resource Control (RRC) connection for the UE, releasing signalling and user-plane transport resources for the UE and initiating a fallback procedure for the UE.
[0039] In another exemplary embodiment, a system for managing a user equipment (UE) context between an evolved Node B (eNodeB) and a Mobility Management Entity (MME) in a network is disclosed. The system (108) includes a processing engine at the eNodeB and the MME where the processing engine is configured to detect a loss of signalling connectivity between the eNodeB and the MME over an SI interface, send a suspend request message requesting suspension of a UE context associated with the UE to the MME, identify the UE context as suspended and store one or more elements of UE context information associated with the UE context, in response to receipt of the suspend request message, identify a re-establishment of the signalling connectivity between the eNodeB and the MME, send a resume request message to the MME to resume the suspended UE context upon identification of the re-establishment of the signalling connectivity between the eNodeB and the MME and perform a resume procedure for the suspended UE context, in response to receipt of the resume request message.
[0040] In yet another exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The mediumincludes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for managing a user equipment (UE) context between an evolved Node B (eNodeB) and a Mobility Management Entity (MME) in a network is disclosed. The method includes steps of detecting, by the eNodeB, a loss of signalling connectivity between the eNodeB and the MME over a SI interface, sending, by the eNodeB, a suspend request message requesting suspension of a UE context associated with the UE to the MME, in response to receipt of the suspend request message, identifying, by the MME, the UE context as suspended and storing one or more elements of UE context information associated with the UE context, identifying, by the eNodeB, a re-establishment of the signalling connectivity between the eNodeB and the MME, upon identification of the re-establishment of the signalling connectivity between the eNodeB and the MME, sending, by the eNodeB, a resume request message to the MME to resume the suspended UE context, and in response to receipt of the resume request message, performing, by the MME, a resume procedure for the suspended UE context.
[0041] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.OBJECTIVES OF THE PRESENT DISCLOSURE
[0042] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:
[0043] An objective of the present disclosure is to introduce a standardized method for pausing and resuming a User Equipment (UE) context at a SI interface level, enabling a non-terrestrial network (NTN) Evolved Node B (eNodeB) to signal its temporary unavailability without triggering a full session release by a Mobility Management Entity (MME).
[0044] Another objective of the present disclosure is to define a new set of SI Application Protocol (S1AP) procedures, namely, a UE Context Suspend Request (UEContextSuspendRequest) and a UE Context Resume Request (UEContextResumeRequest), allowing the NTN eNodeB to explicitly request context preservation and reactivation from the MME.
[0045] Another objective of the present disclosure is to bridge core network context management with store-and-forward operation in NTNs, allowing the eNodeB to buffer uplink data while the MME maintains a suspended session state for the UE.
[0046] Another objective of the present disclosure is to replace simplistic timeout extensions with a coordinated, protocol-level suspend and resume mechanism, ensuring both the NTN eNodeB and the MME maintain synchronized awareness of a temporarily dormant session state.
[0047] Another objective of the present disclosure is to minimize disruption in satellite-based Long Term Evolution (LTE) systems by preserving Non-Access Stratum (NAS) security context, Evolved Packet System (EPS) bearer configurations, and subscription data across temporary SI link outages.
[0048] Another objective of the present disclosure is to ensure backward compatibility with existing UE implementations by limiting procedural changes to network-side components, specifically the eNodeB and the MME, while allowing standard UE behavior in Radio Resource Control (RRC) Idle and Resume states.
[0049] Another objective of the present disclosure is to enhance support for Internet of Things (loT) applications in NTN environments by reducing the signaling burden and power consumption associated with full attach / detach cycles following brief connectivity interruptions.
[0050] Another objective of the present disclosure is to provide a lightweight and efficient solution for session continuity in scenarios with predictable or intermittent backhaul unavailability, such as those caused by satellite feeder link switching or orbital movement.
[0051] Yet another objective of the present disclosure is to improve session reliability and reduce signaling storms in the core network by avoiding mass UE reattachments after link restoration, thus optimizing scalability for dense loT deployments in satellite communication systems.
[0052] 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
[0053] 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 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.
[0054] FIG. 1 illustrates an exemplary network architecture implementing a system for managing a user equipment (UE) context between an evolved Node B (eNodeB (eNB)) and a Mobility Management Entity (MME) in a network, in accordance with an embodiment of the present disclosure.
[0055] FIG. 2A illustrates an exemplary process flow of a successful operation of a UE context suspend procedure, in accordance with an embodiment of the present disclosure.
[0056] FIG. 2B illustrates an exemplary flow of a successful operation of a UE context resume procedure, in accordance with an embodiment of the present disclosure.
[0057] FIG. 2C illustrates an exemplary flow of an unsuccessful operation of the UE context resume procedure, in accordance with an embodiment of the present disclosure.
[0058] FIG. 2D illustrates an exemplary block diagram of the system for managing the UE context between the eNodeB and the MME in the network, in accordance with an embodiment of the present disclosure.
[0059] FIG. 3 illustrates an exemplary sequence diagram for managing the UE context between the eNodeB and the MME in the network, in accordance with an embodiment of the present disclosure.
[0060] FIG. 4 illustrates another exemplary sequence diagram for managing the UE context between the eNodeB and the MME in the network, in accordance with an embodiment of the present disclosure.
[0061] FIG. 5 illustrates an exemplary flowchart of a method implemented by the system for managing the UE context between the eNodeB and the MME in the network, in accordance with an embodiment of the present disclosure.
[0062] FIG. 6 illustrates an exemplary block diagram of a computer system in which or with which embodiments of the present disclosure may be implemented.
[0063] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS 100 - Network architecture102 -User(s)104 -User Equipments (UEs)106 -Network108 - System200A - Suspend flow200B - Resume flow200C - Resume failure flow202- eNodeB (eNB)204- Mobility management entity (MME) 200D - Block diagram218 - Processor(s)220 - Memory222 - Interface(s)224 - Processing Engine226 - Database300, 400 -Exemplary sequence diagram302 - Serving gateway (S-GW)402 - Non-Terrestrial Network Gateway (NTN-Gateway)500 - Method Flowchart600 - Computer System610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port670 - ProcessorDETAILED DESCRIPTION
[0064] 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, asillustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
[0065] 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 may 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.
[0066] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill 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.
[0067] 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.
[0068] 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.
[0069] 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.
[0070] 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 may be noted that theterms “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 may be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.
[0071] 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 other changes 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.
[0072] In long-term evolution (LTE), whenever an eNodeB (eNB)-mobility management entity (MME) link is lost (especially common in satellite “store-and-forward” modes), standard behavior is to drop a UE’s context. This causes repeated full-attach cycles, excessive signaling overhead, and service disruptions for loT devices.
[0073] To overcome this challenge, the present disclosure introduces two new SI Application Protocol (S1AP) procedures: Context Suspend and Context Resume that effectively pause the UE’s context at the MME rather than dropping it, and quickly unpause it when the link returns. This ensures smooth session continuity, minimal signaling, and efficient use of resources in non-terrestrial environments or any network with intermittent backhaul. By providing these dedicated suspend / resume messages atthe SI layer, the present disclosure resolves the lack of an official mechanism in prior LTE standards to handle planned or predictable outages gracefully, thus solving the major inefficiency problem and enabling a robust store-and-forward operation in NTN or other intermittently connected LTE systems.
[0074] The present disclosure introduces a dedicated, standardized way to “pause” and then “resume” an long term evolution (LTE) user’s connection at the SI interface level (between the eNB and the MME), rather than relying on a full detach or forced reconnection after every link loss. The present disclosure uniquely addresses NonTerrestrial Network (NTN) store-and-forward needs by linking the eNB’s ability to buffer data with the MME’s ability to pause the UE session. It’s not just a radio-level feature; it’s a core-network protocol extension ensuring that the UE’s NAS security and bearer state remain valid throughout the satellite outage.
[0075] Merely increasing idle or detach timers is a simplistic workaround. By contrast, the present disclosure offers a purposeful “suspend” handshake, ensuring both sides know that the UE’s session is in a special dormant state, avoiding confusion or inadvertent release. This fine-grained approach is non-obvious compared to standard “just wait longer” solutions. While the present disclosure significantly changes SI AP (network-to-network signaling), it doesn’t impose big changes on UE behavior. The eNB and MME synergy is new and inventive, allowing this solution to fit seamlessly even if UE only supports standard RRC idle / resume.
[0076] The present disclosure solves high signaling and attach delays. Instead of defaulting to context release, the SI -level Suspend maintains the UE’s session. Therefore, loT devices do not need a full attach each time the satellite link returns, drastically reducing network overhead and reconnection delays.
[0077] The present disclosure prevents unnecessary detach / reattach cycles. By introducing explicit messages to “pause” an SI connection, the MME refrains fromdetaching the UE or removing its PDP context, ensuring continuity of IP address assignments and security credentials.
[0078] The present disclosure enhances non-terrestrial loT feasibility. Intermittent feeder link coverage is inherent to satellite or remote loT deployments. The present disclosure addresses it at the core-protocol level (S1AP), enabling store-and-forward operation without losing the user’s session. This is vital for reliability and energy efficiency in satellite-based loT. The present disclosure maintains service continuity with minimal UE changes, because the solution primarily modifies the eNB-MME interface (S1AP), UEs do not need to implement a brand-new protocol. A standard RRC idle / resume approach is enough, while the network orchestrates the core context suspension / resumption. This lowers adoption barriers and leverages existing device capabilities.
[0079] The present disclosure contemplates multiple cycles of suspension / resumption if the satellite or eNB frequently enters coverage / no-coverage states. The MME can handle indefinite cycles of context freezing and thawing as long as a timer or policy doesn’t expire. This is critical for LEO satellites with short contact times to each gateway.
[0080] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
[0081] FIG. 1 illustrates an exemplary network architecture (100) implementing a system (108) managing a user equipment (UE) context between an evolved Node B (eNodeB) and a Mobility Management Entity (MME) in a network (106), in accordance with an embodiment of the present disclosure.
[0082] 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 theart will understand that one or more users (102-1, 102-2, ... 102-N) may be individually referred to as the user (102) and 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 individually referred to as the UE (104) and collectively referred to as the UEs (104). Although three UEs (104) are depicted in FIG. 1, however, any number of the user equipments (104) may be included without departing from the scope of the ongoing description. In an embodiment, each UE (104) may have a unique identifier attribute associated therewith. In an embodiment, the unique identifier attribute may be indicative of at least one of a Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, an International Mobile Subscriber Identity (IMSI), a Subscriber Permanent Identifier (SUPI), and the like.
[0083] In an embodiment, the UE (104) may include smart devices operating in a smart environment, such as 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, a smart security system, a 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 is not limited to, intelligent, multi-sensing, network- connected devices that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.
[0084] In an embodiment, the UE (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted 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 a wireless communication capabilities, and the like. In an embodiment, the UE (104) may include, but is not limited to, any electrical, electronic, electro-mechanical, or an equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. In addition, 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 an entity such as touch pad, a touch enabled screen, an 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.
[0085] In FIG. 1, the UE (104) may communicate with the system (108) via a network (106) to send data to the system (108). 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 UEs (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. 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.
[0086] In an embodiment, the UE (104) may be communicatively coupled with the network (106). The system (108) may receive a connection request from the UE (104). The system (108) 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. Once the connection is established, the system (108) may be configured to manage the UE context between the eNodeB and the MME in the network (106). A process for managing the UE context is explained in greater detail in conjunction with FIGS. 2-6.
[0087] 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).
[0088] FIG. 2A illustrates an exemplary process flow (200A) of a successful operation of a UE context suspend procedure, in accordance with an embodiment of the present disclosure.
[0089] As illustrated, the process flow (200A) depicts the eNodeB (202) (interchangeably referred to as the eNB (202)) and the MME (204).
[0090] In an embodiment, the purpose of the UE context suspend procedure is to suspend the UE context, the UE-associated logical S 1 -connection and the related bearer contexts in an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) and an Evolved Packet Core (EPC). The UE context suspend procedure is particularlyapplicable when the connectivity of the eNB (202) to the core network is temporarily unavailable (e.g., during an NTN feeder link outage), enabling a controlled suspension of the UE’s context for a defined duration while preserving bearers.
[0091] In an embodiment, at step (206), the eNB (202) transmits a UE CONTEXT SUSPEND REQUEST message to the MME (204). The UE CONTEXT SUSPEND REQUEST message may include a set of information elements (IES) associated with the UE (104). In an embodiment, the eNB (202) may include a User Location Information IE indicating the location of the UE (104). Further, the User Location Information IE may include a Primary Secondary Cell (PSCell) IE, indicating that the UE (104) is configured with E-UTRA-NR Dual Connectivity (EN-DC) radio resources at the eNB (202).
[0092] In an embodiment, the eNB (202) may include a Time Since Secondary Node Release IE, representing a duration elapsed since EN-DC operation was stopped for the UE (104). Additionally, the UE CONTEXT SUSPEND REQUEST message may include a Suspend Duration IE indicating a time interval for which the UE context is to be maintained, and a Suspend Cause IE specifying a reason for suspension, including but not limited to network backhaul loss or UE power saving.
[0093] Further, the eNB (202) may include information on Recommended Cells and eNBs for Paging IE, a Cell Identifier and Coverage Enhancement Level IE, and a Secondary RAT Usage Report List IE, enabling the MME (204) to store and utilize such information for subsequent paging, optimization, or reporting procedures.
[0094] In an embodiment, at step (208), upon receipt of the UE CONTEXT SUSPEND REQUEST message, the MME (204) processes the received information and responds with a UE CONTEXT SUSPEND RESPONSE message to the eNB (202). The MME (204) may store the UE context in a suspended state for at least theduration indicated in the Suspend Duration IE and may treat the UE (104) as temporarily unreachable based on the Suspend Cause IE.
[0095] In an embodiment, the UE CONTEXT SUSPEND RESPONSE message may include a Resume Identity IE, which uniquely identifies the suspended UE context and is used for a subsequent resume procedure. Additionally, the UE CONTEXT SUSPEND RESPONSE message may include a Security Context IE, which, upon receipt, is stored by the eNB (202) in the UE context, replacing any previously unused stored security parameters.
[0096] In an embodiment, upon receipt of the UE CONTEXT SUSPEND RESPONSE message, the eNB (202) suspends the UE context, releases or deactivates UE-associated logical SI connections and related bearer contexts, and transitions the UE (104) to an RRC IDLE state. The eNB (202) may further store the Resume Identity IE for use in a subsequent resume procedure and update the UE context with any received Security Context IE.
[0097] In an embodiment, the MME (204) maintains the suspended UE context until the expiry of the suspend duration, occurrence of a resume procedure, or execution of a network-triggered release. If the suspend duration expires without a resume, the MME (204) may release the UE context according to a normal SI release procedure.
[0098] FIG. 2B illustrates an exemplary flow (200B) of a successful operation of a UE context resume procedure, in accordance with an embodiment of the present disclosure.
[0099] In an embodiment, the purpose of the UE context resume procedure is to indicate to the MME (204) that the UE (104) has resumed the suspended RRC connection or accesses for early data transmission and to request the MME (204) to resume the UE context, UE-associated logical SI -connection and the related bearer contexts in the EPC.
[0100] In an embodiment, at step (210), the eNB (202) initiates the UE context resume procedure by sending a UE CONTEXT RESUME REQUEST message to the MME (204). If the eNB (202) is not able to admit all suspended E-RABs, the eNB (202) may indicate this in the E-RABs Failed to Resume List IE.
[0101] In an embodiment, upon receipt of the UE CONTEXT RESUME REQUEST message, the MME (204) acts as defined in the existing standards and responds with the UE CONTEXT RESUME RESPONSE at step (212). If the MME (204) is not able to admit all suspended E-RABs, the MME (204) indicates this in the E-RABs Failed to Resume List IE.
[0102] FIG. 2C illustrates an exemplary flow (200C) of an unsuccessful operation of the UE context resume procedure, in accordance with an embodiment of the present disclosure.
[0103] In an embodiment, at step (214), the eNB (202) initiates the UE CONTEXT RESUME REQUEST message to the MME (204).
[0104] In an embodiment, upon receipt of the UE CONTEXT RESUME REQUEST message, the MME (204) attempts to restore the UE context and associated bearer resources. However, if the MME (204) determines that the UE context cannot be successfully resumed, including scenarios where one or more E-RABs cannot be reestablished, the MME (204) initiates a failure handling procedure.
[0105] In an embodiment, at step (216), the MME (204) generates and transmits a UE CONTEXT RESUME FAILURE message to the eNB (202), thereby releasing a UE-associated logical SI connection. The UE CONTEXT RESUME FAILURE message may include a Cause IE indicating a reason for failure, including but not limited to “context not found” (e.g., due to expiry of a suspend duration) or “network congestion” (e.g., due to insufficient resources).
[0106] In an embodiment, upon receipt of the UE CONTEXT RESUME FAILURE message, the eNB (202) releases an RRC connection associated with the UE (104) based on predefined procedures and releases all related signaling and user-plane transport resources. The eNB (202) may further log a received failure cause and treat the failure condition equivalently to a UE context release procedure.
[0107] FIG. 2D illustrates an exemplary block diagram of the system (108) configured for managing the UE context between the eNodeB (202) and the MME (204) in the network (106), in accordance with an embodiment of the present disclosure.
[0108] With reference to FIG. 1, FIG. 2A, 2B, and 2C, FIG. 2D illustrates the system (108) that may include one or more processors (218). The one or more processor(s) (218) 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) (218) may be configured to fetch and execute computer-readable instructions stored in a memory (220) of the system (108). The memory (220) may be configured to store the 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 (220) 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.
[0109] In an embodiment, the system (108) may include an interface(s) (222). The interface(s) (222) may include a variety of interfaces, for example, interfaces for data input and output devices (I / O), storage devices, and the like. The interface(s) (222) may facilitate communication through the system (108). The interface(s) (222) may also provide a communication pathway for one or more components of the system (108).1Examples of such components include, but are not limited to, a processing engine (224) and a database (226).
[0110] In an embodiment, the processing engine (224) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine (224). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine (224) may be processor-executable instructions stored on a non-transitory machine-readable storage medium, and the hardware for the processing engine (224) may include a processing resource (for example, one or more processors (218), 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 (224). 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 (224) may be implemented by electronic circuitry.
[0111] In an embodiment, the database (226) may store data that may be generated as a result of functionalities implemented by any of the components of the processor (202) or the processing engine (224). In an embodiment, the database (226) may be indicative of including, but not limited to, a relational database, a distributed database, a cloud-based database, or the like. In an embodiment, the database (226) may be configured to store quality of service (QoS) contexts, UE bearers and the like to support management of UE context between the eNodeB (202) and the MME (204).
[0112] In an exemplary embodiment, the processing engine (224) may include one or more units having functions that may include, but are not limited to, testing, storage,and peripheral functions, such as a wireless communication unit for remote operation and the like.
[0113] In an embodiment, the processing engine (224) may be configured to manage the UE context between the eNodeB (202) and the MME (204). The term “UE context,” as used herein, refers to a collection of control-plane and user-plane-related information maintained by the eNodeB (202) and the MME (204) for a specific UE, such as the UE (104). The UE context may comprise a plurality of identifiers (e.g., MME-UE-S1AP-ID and eNB-UE-SlAP-ID), security parameters, bearer configuration details, Quality of Service (QoS) profiles, mobility state information, and session management data required to support ongoing communication. The UE context enables the eNodeB (202) to track, manage, and control the UE’s connectivity.
[0114] In an embodiment, the processing engine (224) may be implemented as a functional module within the eNodeB (202). In another embodiment, the processing engine (224) may be implemented as a functional module within the MME (204). In yet another aspect, the processing engine (208) may be distributed and implemented across both the eNodeB (202) and the MME, such that one or more functionalities are shared or coordinated between the eNodeB (202) and the MME (204).
[0115] In order to manage the UE context, the eNodeB (202) is configured to detect a loss of signaling connectivity between the eNodeB (202) and the MME (204) over an SI interface. The SI interface is a standardized component of Long Term Evolution (LTE) networks that facilitates communication between the eNodeB (202) and the MME (204) for control-plane signaling and bearer management. The detection process may involve a variety of mechanisms, such as a predicted link loss, where the eNodeB (202) may utilize one or more machine learning (ML) models to anticipate the loss of connectivity with the MME (204). Alternatively, the detection process may be triggered by an operator-commanded suspension, in which a network operator or an Operations and Management (O&M) system explicitly informs the eNodeB (202)about the loss of connection to the MME (204). For example, the eNodeB (202) may identify scenarios indicating that it is unable to maintain SI connectivity. Such scenarios may be the eNodeB (202) moving out of a gateway’s coverage beam, scheduled maintenance, known feeder link interruption, or implementation-specific triggers.
[0116] In such scenarios, the eNodeB (202) is configured to send a suspend request message requesting suspension of the UE context associated with the UE (104) to the MME (202). The suspend request message is an SI Application Protocol (S1AP) message that explicitly instructs the MME (204) to preserve the UE context, including Non-Access Stratum (NAS) security parameters, EPS bearer information, and subscription data. The eNodeB (202) notifies the MME (204) that it intends to temporarily go offline (or become unreachable) and asks the MME (204) to preserve the UE context rather than release it by sending the context-suspend request. The MME (204) marks the UE context “suspended” instead of deleting it. The suspend request message prevents premature context release and enables seamless reactivation upon reconnection. This approach explicitly adds a “pause” functionality to SI AP.
[0117] In an embodiment, the eNodeB (202) constructs a UEContextSuspendRequest that may include one or more IES, including but not limited to message type IE, MME UE S1AP ID IE, eNB UE S1AP ID IE, information on recommended cells and eNBs for paging IE, cell identifier and coverage enhancement level IE, secondary RAT usage report list IE, user location information IE, time since secondary node release IE, E-RABs to be released list IE, suspend cause IE, suspend duration IE, security context IE and UE paging identity IE.
[0118] The Message Type IE identifies the S1AP message as a UEContextSuspendRequest and enables correct decoding and processing of the message at the MME (204).
[0119] The MME UE SI AP ID IE is a unique identifier assigned by the MME (204) to the UE context, allowing the MME (204) to locate the corresponding context. The eNB UE S1AP ID IE is a local identifier assigned by the eNodeB (202) for the UE context, enabling correlation at the eNB (202) side.
[0120] The information on recommended cells and eNBs for paging IE provides a list of cells and / or eNBs that are preferable for paging the UE (104) optimizing paging efficiency. The cell identifier and coverage enhancement level IE indicate the last serving cell and associated coverage level of the UE (104), which may assist in subsequent paging or reachability procedures.
[0121] The secondary RAT usage report list IE conveys usage information related to secondary radio access technologies (e.g., NR in EN-DC), which may be used by the core network for analytics or optimization.
[0122] The user location information IE provides the geographical or cell-level location of the UE (104) and may include additional details such as PSCell information in dual connectivity scenarios.
[0123] The time since secondary node release IE indicates a duration elapsed since a secondary node (e.g., NR node in EN-DC) was released for the UE (104), which may be useful for mobility or resource management decisions.
[0124] The E-RABs to be released list IE identifies one or more E-RABs that are to be released as part of the suspend procedure, ensuring proper cleanup of user-plane resources.
[0125] The suspend cause IE is an optional IE that indicates a reason for suspension, including but not limited to SI suspension, feeder link outage, or network-triggered conditions.
[0126] The suspend duration IE is an optional IE that specifies a duration, typically as an integer value in seconds, for which the eNodeB (202) expects the UE context to remain suspended.
[0127] The security context IE contains security-related parameters associated with the UE context, including but not limited to cryptographic keys, key identifiers, and security algorithm information required for integrity protection and ciphering. The security context IE enables the MME (204) to maintain or update the security configuration of the UE (104) during suspend and resume procedures.
[0128] The UE paging identity IE provides an identity used for paging the UE (104) during the suspended state, enabling the core network to address paging messages appropriately when required.
[0129] In an aspect, the eNodeB (202) may send the UEContextSuspendRequest message over an established SI -MME SCTP (Stream Control Transmission Protocol) association link to the MME (204). In an alternative aspect, if the SI -MME SCTP association link is about to break, the eNodeB (202) ensures the UEContextSuspendRequest message is transmitted in time. If the SI -MME SCTP association link breaks unexpectedly, the eNodeB (202) might not be able to suspend in an orderly manner. In such a case, a normal release occurs. Herein, the normal release refers to the standard, steady-state functioning of the eNodeB (202) when signaling and user-plane connectivity are intact and no exceptional procedures (such as suspend or failure handling) are triggered. For instance, when the SI -MME link breaks unexpectedly, and no suspend procedure is completed, the normal release refers to the standard UE context release procedure defined in existing specifications, where the UE context and associated bearer resources are fully released instead of being preserved in a suspended state.
[0130] In an embodiment, in response to receipt of the suspend request message (UEContextSuspendRequest), the MME (204) is configured to identify the UE context as suspended and store one or more elements of UE context information associated with the UE context in the database (226). In an aspect, the one or more elements of the UE context information may include, but are not limited to, a NAS security context, an EPS bearer state, or subscription data associated with the UE (104).
[0131] In an example, the MME (204) receives the UEContextSuspendRequest, and locates the corresponding UE context using the IES received in the UEContextSuspendRequest. Further, the MME (204) flags the UE context as “Suspended”. This means the MME (204) restricts normal release procedures if it later loses contact with the eNodeB (202).
[0132] Additionally, when the IE indicating the duration of the suspension is available in the suspend request message, the MME (204) determines an indicated suspend interval from the suspend request message and maintains the suspended UE context for at least the indicated suspend interval, and when no resume request message is received before expiry of the determined suspend interval, the MME (204) releases the suspended UE context. For example, the MME (204) may set the indicated suspend interval (T) to 180 seconds, so that the MME (204) retains the UE context in a suspended state for up to 180 seconds from the time of suspension. If the UE CONTEXT RESUME REQUEST message is received within this interval, the MME (204) proceeds with resumption of the UE context, whereas if no such request is received within the 180-second interval, the MME (204) triggers a release of the UE context and associated bearer resources according to the normal SI release procedure.
[0133] In an aspect, upon successful suspension of the UE context, the MME (204) transmits a signalling message via an SI 1 interface to the S-GW to perform at least one of holding, buffering, delay forwarding or dropping General Packet Radio Service (GPRS) Tunnelling Protocol User plane (GTP U) packets for the suspended UEcontext. In an example, the MME (204) may determine whether the S-GW is carrying active data tunnels for the UE (104). Upon determining that the S-GW is carrying active data tunnels for the UE 104, the MME (204) instructs the S-GW via the SI 1 interface (modify bearer) to release or pause those data tunnels. The S-GW is informed to drop or hold the user-plane tunnels for that UE ( 104), but the core does not delete the session.
[0134] In an aspect, the MME (204) creates a suspend response (UEContextSuspendResponse) message. The UEContextSuspendResponse message indicates the success or failure of the suspend procedure and serves as an acknowledgment to the eNodeB (202), confirming whether the requested UE context preservation was executed as intended. For example, upon successful suspension of the UE context, the MME (204) sends a success response message (UEContextSuspendSucess) to the eNodeB (202) indicating that the UE context was successfully suspended. Conversely, when the MME (204) determines that the UE context identified in the suspend request message is unavailable or suspension of the UE context is unsupported, the MME (204) sends a failure response message (UEContextSuspendFailure) to the eNodeB (202) indicating failure of the suspension of the UE context.
[0135] In an embodiment, the MME (204) includes an identifier in the suspend response message. The identifier is a token allocated by the MME (204) to identify the suspended UE context.
[0136] In an embodiment, the eNodeB (202) is configured to identify a reestablishment of the signalling connectivity between the eNodeB (202) and the MME (204). In an example, after a time period (e.g., when the eNodeB (202) re-enters a gateway coverage beam), the eNodeB (202) re-establishes the SI -MME transport. This typically involves re-establishing an SCTP association with the MME (204), including performing SCTP procedures, followed by transmission of an SI SETUP REQUEST message from the eNodeB (202) to the MME (204). Upon successful processing, theMME (204) responds with an SI SETUP RESPONSE message, thereby restoring signalling connectivity.
[0137] In an embodiment, upon identification of the re-establishment of the signalling connectivity between the eNodeB (202) and the MME (204), the eNodeB (202) sends a resume request message to the MME (204) to resume the suspended UE context. In response to the receipt of the resume request message, the MME (204) is configured to perform a resume procedure for the suspended UE context. In an example, the eNodeB (202) may create a UEContextResumeRequest S1AP message for the UE (104), referencing the stored context. In an aspect, the eNodeB (202) may include the stored identifier in the resume request message to resume the suspended UE context. In an example, upon receiving the UEContextResumeRequest, the MME (204) immediately reactivates the suspended UE context and transmits a request to the S-GW to reestablish a GTP U tunnel toward the eNodeB (202), skipping a full re-attach procedure.
[0138] In an aspect, the eNodeB (202) sends the UEContextResumeRequest to the MME (204) over SI -MME. Further, the eNodeB (202) also ensures the radio connection is in a partial resume state. In some cases, the UE 104 may sent an RRCConnectionResume request. The eNodeB (202) lines up with the UEContextResumeRequest, so the MME (204) is ready for user-plane traffic.
[0139] In an embodiment, upon receiving the UEContextResumeRequest, the MME (204) identifies the UE context that is marked as “Suspended”. If the MME (204) finds a matching record and the suspend interval has not expired, the MME (204) proceeds to resume the suspended UE context.
[0140] In an aspect, the MME (204) keeps the same EPS bearer ID(s) and QoS contexts during the resuming process. The difference is that the S-GW was previously in a suspended or deactivated state for these bearers, now it becomes active again. TheMME (204) also ensures any pending NAS messages for the UE (104) (like a queued downlink NAS) can be delivered once the eNodeB (202) fully resumes.
[0141] In an aspect, the MME (204) creates a UEContextResumeResponse S1AP message. In an example, the MME (204) successfully updates the S-GW and reactivates the UE context by preparing the UEContextResumeResponse. The UEContextResumeResponse includes the mandatory MME-UE-SIAP-ID and eNB-UE-S1AP-ID to confirm the resumption or failure of resumption of the UE context. In an aspect, the MME (204) may optionally embed a list of E-RABs reactivated, each with new TEIDs if needed.
[0142] In an aspect, the MME (204) sends the UEContextResumeResponse to the eNodeB (202). If successful, the UEContextResumeResponse indicates the user-plane path is re-established. The eNodeB (202) also finalizes the RRC resume at the radio side. Further, the eNodeB (202) signals to the UE that it may proceed with normal data transmission. Because the NAS context was preserved, the UE (104) retains the same IP address, security keys, etc., and no new attach or PDN connectivity procedure is needed. Additionally, if any downlink data remains in the S-GW buffer, then it is forwarded to the eNodeB (202), and the UE (104) receives it as soon as the radio link is ready.
[0143] Conversely, if the MME is unable to perform at least one of locating the suspended UE context, restoring the suspended UE context, or resuming one or more suspended E-RABs, the MME (204) transmits a resume failure message to the eNodeB (202). In an aspect, upon receipt of the resume failure message, the eNodeB (202) is configured to release the RRC connection for the UE (104). Additionally, the eNodeB (202) is configured to release signaling and user plane transport resources for the UE (104) and initiate a fallback procedure for the UE (104).
[0144] In an exemplary embodiment, the tables below summarize the new or extended Abstract Syntax Notation One structures that enable the steps performed by the system (108):
[0145] In an exemplary embodiment, the procedure codes as shown in Table 1 uniquely identify specific S1AP procedures. For example, id-UEContextSuspend (55) indicates a UE context suspend procedure, and id-UEContextResume (56) indicates a UE context resume procedure. These codes enable the eNodeB (202) or MME (204), to correctly interpret, route, and process signalling messages, as well as correlate corresponding requests and responses within the same procedure.Procedure Codesid-UEContextSuspend ProcedureCode ::= 55 — exampleid-UEContextResume ProcedureCode ::= 56 — exampleTable 1
[0146] In an exemplary embodiment, the elementary procedures as shown in Table 2 define the complete signaling transactions for specific operations between the eNodeB (202) and the MME (204). Each elementary procedure specifies the initiating message, corresponding successful outcome, and, where applicable, an unsuccessful outcome, along with a unique procedure code and criticality handling. These elementary procedures are standardize the end-to-end message flow for operations such as UE context suspend and resume. For example, the UEContextSuspend procedure ensures a controlled suspension using request and response messages, while the UEContextResume procedure additionally defines failure handling through an unsuccessful outcome.Elementary ProceduresUEContextSuspend S1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE UEContextSuspendRequest, SUCCESSFUL OUTCOME UEContextSuspendResponse, PROCEDURE CODE id-UEContextSuspend,CRITICALITY rejectUEContextResume SI AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE UEContextResumeRequest, SUCCESSFUL OUTCOME UEContextResumeResponse, UNSUCCESSFUL OUTCOME UEContextResumeFailure, PROCEDURE CODE id-UEContextResume,CRITICALITY rejectTable 2
[0147] Although FIG. 2D shows exemplary components of the system (200D), in other embodiments, the system (200D) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 2. Additionally, or alternatively, one or more components of the system (200D) may perform functions described as being performed by one or more other components of the system (200D).
[0148] FIG. 3 illustrates an exemplary sequence diagram (300) for managing the UE context between the eNodeB (202) and the MME (204) in the network (106), in accordance with an embodiment of the present disclosure.
[0149] With reference to FIG. 1, FIG. 2A, 2B, 2C, and 2D, FIG.3, illustrate the context resume / resume procedure.
[0150] In an embodiment, the unique suspend / resume procedures primarily reside in and are executed by the network side of an LTE system, specifically in:
[0151] The eNodeB (eNB) (202) (also referred as satellite eNB (302)), where a new logic is implemented for deciding when to trigger the suspend request (e.g., before a satellite feeder link outage), and how to subsequently initiate the resume request when connectivity is restored, storage of suspended UE contexts (or their essential identifiers) so that, upon regaining SI connectivity the eNB (302) can properly reference the suspended session.
[0152] The MME (core network node) (204), where the MME (204) maintains and labels UE contexts as “suspended,” rather than releasing them, when the context suspend request is received. The MME (core) (204) coordinates with the (S-GW) to temporarily pause user-plane bearers. The MME (204) handles the resume procedure by immediately restoring the suspended context once the eNB (202) sends the resume request. The MME (204) implements timers and policies to decide how long a context should remain suspended if no resume occurs.
[0153] The S-GW (302): The S-GW (302) is informed by the MME (204) to release or hold GTP-U bearer resources during suspension. When resuming, the MME (204) instructs the S-GW (302) to re-establish or modify the tunnels with the eNB (202).
[0154] At step (304), normal data (Uplink / Downlink) is performed by the UE (104) and the eNB (202). The UE 104 engages in regular data communication with the core network. Uplink data is transmitted from the UE 104 to the satellite eNB 202, then forwarded to the MME 204, and ultimately routed through the S-GW 302 to the destination. Downlink data follows the reverse path. In this step reflects the eNB 202and MME 204 maintain an active SI link, and the S-GW 302 provides the necessary data tunneling for the ongoing communication.
[0155] At step (306), the satellite eNB (202) predicts or detects an outage or potential interruption in the feeder link connecting it to the terrestrial gateway. This prediction may result from satellite trajectory, link quality degradation, or anticipated maintenance. The prediction enables the satellite eNB 202 to safeguard session continuity in advance. The eNB (202) sees upcoming coverage loss with the MME (204).
[0156] At step (308), the satellite eNB (202) initiates the context suspension by transmitting a UE CONTEXT SUSPEND REQUEST to the MME (204) using SI AP. The suspend request includes the eNB UE SI AP ID, the MME UE SI AP ID, and the cause set to “feederLinkOutage”. The suspend request serves to inform the MME (204) of the unreachability while requesting the preservation of the UE context for seamless reactivation.
[0157] At step (310), the MME (204) responds by triggering a modify bearer request towards the S-GW (302). The modify bearer request enables the S-GW (302) to release the Sl-U user plane tunnel associated with the UE session. As a result, user-plane data transmission between the satellite eNB (202) and the S-GW (302) is temporarily halted, conserving network resources.
[0158] At step (312), the MME (204) acknowledges the suspend request by sending a “UE CONTEXT SUSPEND RESPONSE” to the satellite eNB (202). The MME (204) marks the associated UE context as “suspended,” retaining session information such as IP address, bearer configuration, and QoS profiles. Further, the MME (204) avoids the need for a complete session re-establishment later.
[0159] At step (314), the satellite eNB (202) signals the UE (104) that is suspend capable to release the RRC connection. The RRCConnectionRelease message informsthe UE (104) that the connection is temporarily suspended and can be resumed later. The UE (104) enters an idle state while retaining context information required for future resume operations.
[0160] In an embodiment, the feeder link outage occurs, and the satellite eNB (202) loses connectivity with the MME (204). Although the SI interface is down, the satellite eNB (202) may continue to maintain radio connectivity with the UE (104) and can buffer uplink data packets in store-and-forward mode.
[0161] At step (316), when the feeder link is restored, and the satellite eNB (202) reestablishes the SI signalling interface with the MME (204) through an SI Setup procedure.
[0162] At step (318), the satellite eNB (202) transmits a “UE CONTEXT RESUME REQUEST” to the MME (204). The “UE CONTEXT RESUME REQUEST” includes the current eNB UE S1AP ID and the previously used MME UE S1AP ID to reference the suspended UE context. The UE CONTEXT RESUME REQUEST” message reactivates the session.
[0163] At step (320), the MME (204) processes the resume request and identifies the suspended context. The MME (204) initiates a modify bearer request to the S-GW (302) to recreate the Sl-U tunnel. This re-establishes the user-plane path between the satellite eNB (202) and the S-GW (302).
[0164] At step (322), the MME (204) completes the reactivation by sending a “UE CONTEXT RESUME RESPONSE” to the satellite eNB (202). The suspended UE context is now marked as active. User-plane bearers are restored, and session attributes are synchronized, enabling seamless re-entry of the UE (104) into active data service.
[0165] In step (324), the user plane bearers are restored, and the UE's context is active in the core network. The satellite eNB (202) signals the UE (104) with an“RRCConnectionResume” message. This enables the UE (104) to resume data transmission without undergoing the entire LTE attach sequence.
[0166] At step (326), as a result of the RRCConnectionResume, the session state, bearer configuration, and IP address of the UE (104) are retained. Normal data flow or transmission resumes successfully between the UE (104) and the core network through the satellite eNB (202), MME (204), and S-GW (302), minimizing overhead and ensuring a smooth transition back to active communication.
[0167] FIG. 4 illustrates an exemplary sequence diagram (400) for managing the UE context between the eNodeB (202) and the MME (204) in the network (106), in accordance with an embodiment of the present disclosure. FIG. 4 is explained in conjunction with FIGS. 1, 2, and 3.
[0168] The steps below describe the normal operation.
[0169] At step (404), the normal LTE data (such as uplink / downlink) is performed between the UE (104) and the satellite eNB (202).
[0170] At step (406), the satellite eNB (202) engages with the NTN gateway (ground station) (402), and determines the status of the satellite feeder link as active.
[0171] At step (408), the NTN gateway (402) engages with the MME (204) and determines the SI -MME connection as active.
[0172] At step (410), the NTN gateway (402), the MME (204), and the S-GW (user plane gateway) (302) communicates with each other, and it is determined that the Sl-U GTP-U tunnel is active.
[0173] In an aspect, when the satellite eNB (202) detects imminent loss of feeder link connectivity with the MME (204), it may proceed with the UE context suspend procedure.
[0174] The steps below describe the context suspend procedure.
[0175] At step (412), the satellite eNB (202) creates the UE context suspend request. The UE context suspend request may include the IES such as the MME UE SI AP ID, eNB UE S1AP ID, Cause = SI, and the Suspend duration.
[0176] The eNB (202) sends the UE context suspend request to the MME (204). Upon receiving, the MME (204) retains UE NAS context, security keys, and the bearers.
[0177] Table 3, shown here, describes the ASN.1 excerpt for creating the UE context suspend request.UEContextSuspendRequest ::= SEQUENCE {protocolIEs ProtocolIE-Container {{ UEContextSuspendRequestlEs }},UEContextSuspendRequestlEs S1AP-PROTOCOL-IES ::= {{ ID id-MME-UE-S 1 AP-ID CRITICALITY rej ect TYPE MME-UE-S 1 AP- ID PRESENCE mandatory} |{ ID id-eNB-UE-Sl AP-ID CRITICALITY reject TYPE ENB-UE-S1 AP-ID PRESENCE mandatory} |{ ID id-Cause CRITICALITY ignore TYPE CausePRESENCE optional} |{ ID id-SuspensionDuration CRITICALITY ignore TYPE INTEGER (0..4095) PRESENCE optional},Table 3
[0178] At step (414), the MME (204) modifies bearer request by suspending Sl-U tunnels at the S-GW (302). Further, the S-GW (302) re-establishes the GTP-U tunnels.
[0179] At step (416), the S-GW (302) sends the modify bearer response the MME (202) indicating successful re-establishment of the GTP-U tunnels.
[0180] At step (418), the MME (204) sends the UE context suspend response to the satellite eNB (202). The table 4 shown below describes the ASN.1 excerpt for creating the UE context suspend response.UEContextSuspendResponse ::= SEQUENCE {protocolIEs ProtocolIE- Container {{ UEContextSuspendResponselEs }},UEContextSuspendResponselEs S1AP-PROTOCOL-IES ::= {{ ID id-MME-UE-S 1 AP-ID CRITICALITY ignore TYPE MME-UE-S 1 AP- ID PRESENCE mandatory} |{ ID id-eNB-UE-Sl AP-ID CRITICALITY ignore TYPE ENB-UE-S1 AP-ID PRESENCE mandatory} |{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional} — used only if failTable 4
[0181] At step (420), the satellite eNB (202) performs RRC connection release with the UE (104), indicating the MME (204) is capable of the resume process. After the RRC connection is released, the UE (104) stays in the suspended idle state.
[0182] At step (422), the satellite eNB (202) moves out of the coverage of the NTN gateway (402).
[0183] In an aspect, the satellite eNB (202) regains the NTN gateway (402) connectivity, and at step 424, the satellite eNB (202) re-establishes the feeder link.
[0184] At step (426), the SI setup request is sent ny the satellite eNB (202) to the MME (204).
[0185] At step (428), the MME (204) sent the SI setup response to the satellite eNB (202).
[0186] At step (430), the satellite eNB (202) creates and sends the UE context resume request to the MME (204). The UE context resume request includes the MME UE S1AP ID, and the resume identity.
[0187] Table 5, shown below, describes the ASN.l excerpt for creating the UE context resume request.UEContextResumeRequest ::= SEQUENCE {protocolIEs ProtocolIE-Container {{ UEContextResumeRequestlEs }},UEContextResumeRequestlEs S1AP-PROTOCOL-IES ::= {{ ID id-MME-UE-Sl AP-ID CRITICALITY reject TYPE MME-UE-S1 AP-ID PRESENCE optional },{ ID id-eNB-UE-Sl AP-ID CRITICALITY reject TYPE ENB-UE-S1 AP-ID PRESENCE mandatory },{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional },Table 5
[0188] Upon receiving, the MME (204) retrieves preserved context and reactivates bearers.
[0189] At step (432), the MME (204) sends the modify bearer request to the S-GW (302) for resuming Sl-U tunnels. The S-GW (302) re-establishes GTP-U tunnels.
[0190] At step (434), the S-GW (302) sends the modify bearer response to the MME (204) indicating successful re-establishment of the GTP-U tunnels.
[0191] At step (436), the MME (204) creates and sends the UE context resume response, including the bearer context information and GTP-U endpoints, to the satellite eNB (202).
[0192] Table 6, shown below, describes the ASN.l excerpt for creating the UE context resume response.UEContextResumeResponse ::= SEQUENCE {protocolIEs ProtocolIE-Container {{ UEContextResumeResponselEs }},UEContextResumeResponselEs S1AP-PROTOCOL-IES ::= {{ ID id-MME-UE-Sl AP-ID CRITICALITY ignore TYPE MME-UE-S1AP- ID PRESENCE mandatory} |{ ID id-eNB-UE-Sl AP-ID CRITICALITY ignore TYPE ENB-UE-S1 AP-ID PRESENCE mandatory} |{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional},Table 6
[0193] At step (438), the satellite eNB (202), send the RRC connection resume message to the UE (104). Upon receiving, the UE (104) returns to active LTE state without NAS reattach. This benefits a fast resume process.
[0194] At step (440), the normal LTE data is resumed between the UE (104) and the satellite eNB (202).
[0195] FIG. 5 illustrates an exemplary flowchart of a method (500) implemented by the system (102) for managing the UE context between the eNodeB (202) and the MME (204) in the network (106), in accordance with an embodiment of the present disclosure.
[0196] At step (502), the method (500) includes a step of detecting, by the eNodeB (202), the loss of signalling connectivity between the eNodeB (202) and the MME (204) over the SI interface.
[0197] At step (504), the method (500) includes a step of sending, by the eNodeB (202), a suspend request message to the MME (204) requesting suspension of the UE context associated with the UE (104). In an aspect, the suspend request message includes, but is not limited to, the MME UE SI AP ID, the eNodeB UE SI AP ID, the information element indicating the duration of the suspension, and the information element indicating the cause of the suspension. In an aspect, when the information element indicating the duration of the suspension is available in the suspend request message, the MME (204) determines an indicated suspend interval from the suspend request message and maintains the suspended UE context for at least the indicated suspend interval, and when no resume request message is received before expiry of the determined suspend interval, the MME (204) releases the suspended UE context
[0198] At step (506), the method (500) includes a step of identifying, by the MME (204), the UE context as suspended and storing the one or more elements of UE context information associated with the UE context, in response to receipt of the suspend request message. In an aspect, one or more elements of the UE context information include but are not limited to the NAS security context, the EPS bearer state, or subscription data associated with the UE (104).
[0199] In an aspect, upon successful suspension of the UE context, the MME (204) transmits a signalling message via an Sil interface to the S-GW (302) to perform at least one of holding, buffering, delay forwarding or dropping GPRS, GTP U packets for the suspended UE context.
[0200] In an aspect, upon successful suspension of the UE context, the MME (204) sends a success response message to the eNodeB (202) indicating success of the suspension of the UE context.
[0201] In an aspect, when the MME (204) determines that at least one of the UE context identified in the suspend request message is unavailable or suspension of theUE context is unsupported, the MME (204) sends the failure response message to the eNodeB (202) indicating failure of the suspension of the UE context.
[0202] At step (508), the method (500) includes a step of identifying, by the eNodeB (202), a re-establishment of the signalling connectivity between the eNodeB (202) and the MME (204). in an aspect, the eNodeB (202) buffers uplink user data during a period in which the UE context is suspended, and after re-establishment of the signalling connectivity over the SI interface and receipt of the resume response message, the eNodeB (202) sends at least a portion of the buffered uplink user data towards the network.
[0203] At step (510), the method (500) includes a step of sending, by the eNodeB (202), the resume request message to the MME (204) to resume the suspended UE context, upon identification of the re-establishment of the signalling connectivity between the eNodeB (202) and the MME (204).
[0204] At step (512), the method (500) includes a step of performing, by the MME (204), the resume procedure for the suspended UE context, in response to receipt of the resume request message. In an aspect, the resume procedure performed by the MME (204) includes steps of reactivating, by the MME (204), the suspended UE context and transmitting, by the MME (204) to the S-GW (302), a request to re-establish the GTP U tunnel toward the eNodeB (202).
[0205] In an aspect, the method (500) includes sending, by the MME (204), the resume response message to the eNodeB (202) after performing the resume procedure. In an aspect, the MME (204) includes the identifier in the suspend response message; where the identifier is the token allocated by the MME (204) to identify the suspended UE context and the eNodeB (202) stores the identifier in the resume request message to resume the suspended UE context.
[0206] In an aspect, in response to being unable to perform at least one of locating the suspended UE context, the method (500) includes steps of restoring the suspended UE context and resuming one or more suspended E-RABs. The MME (204) then transmits the resume failure message to the eNodeB (202).
[0207] In an aspect, upon receipt of the resume failure message, the eNodeB (202) performs at least one of releasing the RRC connection for the UE (104), releasing signalling and user plane transport resources for the UE (104) and initiating a fallback procedure for the UE (104).
[0208] In an exemplary embodiment, the system (108) configured to manage the UE context between the eNodeB (202) and the MME (204) is described. The system (108) includes the processing engine (224) at the eNodeB (202) and the MME (204). The processing engine (224) at the eNodeB (202) is configured to detect the loss of signalling connectivity between the eNodeB (202) and the MME (204) over the SI interface, send the suspend request message requesting suspension of the UE context associated with the UE (104) to the MME (204). In response to receipt of the suspend request message, the processing engine (224) at the MME (204) is configured to identify the UE context as suspended and store the one or more elements of UE context information associated with the UE context. Further, the processing engine (224) at the eNodeB (202) is configured to identify the re-establishment of the signalling connectivity between the eNodeB (202) and the MME (204) and send the resume request message to the MME (204) to resume the suspended UE context, upon identification of the re-establishment of the signalling connectivity between the eNodeB (202) and the MME (204). In response to receipt of the resume request message, the processing engine (224) at the MME (204) is configured to perform the resume procedure for the suspended UE context.
[0209] FIG. 6 illustrates an exemplary computer system (600) in which or with which embodiments of the present disclosure may be implemented.
[0210] 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.
[0211] 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 Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.
[0212] 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).
[0213] 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.
[0214] The bus (620) communicatively couples the processor (670) with the other memory, storage, and communication blocks. The bus (620) may be, e.g., a PeripheralComponent Interconnect (PCI) / PCI Extended (PCI-X) 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.
[0215] 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 to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.
[0216] In an exemplary embodiment, the processor (670) is configured to execute the method (500) for managing the UE context between the eNodeB (202) and the MME (204). The method includes steps of detecting (502), by the eNodeB (202), the loss of signalling connectivity between the eNodeB (202) and the MME (204) over the SI interface, sending, by the eNodeB (202), the suspend request message requesting suspension of the UE context associated with the UE (104) to the MME (204), in response to receipt of the suspend request message, identifying, by the MME (204), the UE context as suspended and storing the one or more elements of UE context information associated with the UE context, identifying, by the eNodeB (202), the reestablishment of the signalling connectivity between the eNodeB (202) and the MME (204), upon identification of the re-establishment of the signalling connectivity between the eNodeB (202) and the MME (204), sending, by the eNodeB (202), the resume request message to the MME (204) to resume the suspended UE context, and in response to receipt of the resume request message, performing, by the MME (204), the resume procedure for the suspended UE context.
[0217] In an embodiment, the present disclosure provides technical advancements over the conventional techniques. The conventional techniques fail to define a formal S1AP procedure named UE Context Suspend / UE Context Resume with request and response message structures. However, in an embodiment, the present disclosure introduces new Procedure Codes and full ASN.1 definitions (SuspendRequest / Response, ResumeRequest / Response / Failure), complete with Cause IES and optional SuspendDuration / Resumeldentity IES.
[0218] The conventional techniques discuss conceptual S&F but do not teach holding the SI context in MME via a suspend handshake. The conventional techniques discuss NGAP suspend / resume for 5G AMF / gNB, not LTE SI AP eNB / MME. However, in an embodiment, the present disclosure discloses that MME does not simply cache data, however it is instructed to “pause” UE context via the S1AP message and then to “thaw” it, coordinating with the S-GW to tear down or re-create GTP-U tunnels only on suspend / resume.
[0219] The conventional techniques address only the resume side and does not teach the suspend side (and is not NTN-specific). The conventional techniques fail to teach the minimal two-message exchange that preserves NAS security, EPS bearers, IP addresses, etc. However, in an embodiment, the present disclosure teaches that only UEContextSuspendRequest / Response and UEContextResumeRequest / Response are needed thus avoiding full Attach / Detach and bearer re-setup.
[0220] The conventional techniques mention store and forward at a high level by showing a UE-centric “coverage restoring information,” but not an eNB to MME SI AP suspend / resume with explicit messages. However, in an embodiment, the present disclosure tailors the procedure to NTN eNB (satellite) behavior, including prediction of feeder link loss, optional suspend timers, and integration with ground-MME vs. satellite-MME (MME-T vs. MME-NT).
[0221] The conventional techniques lacks any description of a ResumeFailure message or fallback flow to a full re-attach. However, in an embodiment, the present disclosure defines UEContextResumeFailure with explicit Cause IES so that the eNB can deterministically fall back if the suspend timer has expired or context is lost.
[0222] The conventional techniques fail to explain how legacy nodes gracefully ignore these messages. However, in an embodiment, the present disclosure specifies that these are optional S1AP extensions (criticality = reject), ensuring non-disruptive incremental deployment.
[0223] 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.
[0224] 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.ADVANTAGES OF THE PRESENT DISCLOSURE
[0225] The present disclosure reduces signaling overhead between a non-terrestrial network (NTN) evolved Node B (eNodeB) and the core network by introducing minimal context management procedures. Specifically, the two-message exchange comprising the User Equipment Context Suspend Request (UEContextSuspendRequest) and User Equipment Context Resume Request (UEContextResumeRequest) replaces the need for a full detach and reattach cycle. This significantly reduces signaling load over the SI interface and Non-Access Stratum (NAS), optimizing network efficiency in environments with intermittent backhaul connectivity.
[0226] The present disclosure enables faster session recovery for the UEs following a temporary outage of the SI link. By maintaining the security context and bearer state during the suspended phase, the present disclosure allows immediate resumption of data exchange without the latency of reauthentication, bearer re-establishment, or IP address reassignment, thereby ensuring low-latency reconnection and minimal service disruption.
[0227] The present disclosure ensures continuity of IP address allocation and bearer configuration across connectivity interruptions. During the suspend phase, the core network retains the complete EPS (Evolved Packet System) session context, eliminating the need for IP reallocation or PDN reconnection. This preservation of context enhances session integrity and supports seamless user experience upon resumption.
[0228] The present disclosure improves the operational efficiency of the UEs such as the Internet-of-Things (loT) devices, particularly those characterized by infrequent uplink transmissions and constrained battery resources. By avoiding repeated authentication and session setup, the proposed method reduces both powerconsumption and signaling overhead, which are critical considerations for low-power, wide-area loT deployments.
[0229] The present disclosure facilitates efficient store-and-forward operation in satellite-based LTE-NTN systems by enabling the evolved Node B (eNodeB) to buffer uplink data while preserving its session linkage with the core network. Upon restoration of the backhaul link, the buffered data can be forwarded without requiring session renegotiation or context re-creation, thereby supporting delay-tolerant applications and ensuring data reliability in intermittent connectivity scenarios.
Claims
We Claim:
1. A method (500) for managing a user equipment (UE) context between an evolved Node B (eNodeB) (202) and a Mobility Management Entity (MME) (204) in a network (106), the method (500) comprising:detecting (502), by the eNodeB (202), a loss of signalling connectivity between the eNodeB (202) and the MME (204) over an SI interface;sending (504), by the eNodeB (202), a suspend request message requesting suspension of a UE context associated with the UE (104) to the MME (204);in response to receipt of the suspend request message, identifying (506), by the MME (204), the UE (104) context as suspended and storing one or more elements of UE context information associated with the UE context;identifying (508), by the eNodeB (202), a re-establishment of the signalling connectivity between the eNodeB (202)and the MME (204);upon identification of the re-establishment of the signalling connectivity between the eNodeB (202) and the MME (204), sending (510), by the eNodeB (202), a resume request message to the MME (204) to resume the suspended UE context; and in response to receipt of the resume request message, performing (512), by the MME (204), a resume procedure for the suspended UE context.
2. The method (500) as claimed in claim 1, comprising:sending, by the MME (204), a resume response message to the eNodeB (202) after performing the resume procedure.
3. The method (500) as claimed in claim 1, wherein, when the MME (204) determines that at least one of: the UE context identified in the suspend request message is unavailable or suspension of the UE context is unsupported, the MME (204) sends afailure response message to the eNodeB (202) indicating failure of the suspension of the UE context.
4. The method (500) as claimed in claim 1, wherein, upon successful suspension of the UE context, the MME (204) sends a success response message to the eNodeB (202) indicating success of the suspension of the UE context.
5. The method (500) as claimed in claim 4, wherein upon successful suspension of the UE context, the MME (204) transmits a signalling message via an SI 1 interface to an S-GW to perform at least one of holding, buffering, delay forwarding or dropping General Packet Radio Service (GPRS) Tunnelling Protocol User plane (GTP U) packets for the suspended UE context.
6. The method (500) as claimed in claim 1, wherein, the resume procedure performed by the MME (204) comprising:reactivating, by the MME (204), the suspended UE context; and transmitting, by the MME (204) to the S-GW, a request to re-establish a GTP U tunnel toward the eNodeB (202).
7. The method (500) as claimed in claim 1, wherein the one or more elements of the UE context information comprises at least one of a Non-Access Stratum (NAS) security context, an Evolved Packet System (108)(EPS) bearer state, or subscription data associated with the UE (104).
8. The method (500) as claimed in claim 1, wherein the suspend request message comprises at least one of an MME UE SI Application Protocol (AP) Identifier (ID), an eNodeB UE S1AP ID, an information element indicating a duration of the suspension and an information element indicating a cause of the suspension.
9. The method (500) as claimed in claim 8, wherein, when the information element indicating the duration of the suspension is available in the suspend request message,the MME (204) determines an indicated suspend interval from the suspend request message and maintains the suspended UE context for at least the indicated suspend interval, and wherein, when no resume request message is received before expiry of the determined suspend interval, the MME (204) releases the suspended UE context.
10. The method (500) as claimed in claim 1, wherein the MME (204) includes an identifier in the suspend response message; wherein the identifier is a token allocated by the MME (204) to identify the suspended UE context; and wherein the eNodeB (202) stores the identifier in the resume request message to resume the suspended UE context.
11. The method (500) as claimed in claim 1, wherein the eNodeB (202) buffers uplink user data during a period in which the UE context is suspended, and wherein after reestablishment of the signalling connectivity over the SI interface and receipt of the resume response message, the eNodeB (202) sends at least a portion of the buffered uplink user data towards the network (106).
12. The method (500) as claimed in claim 1, wherein, in response to being unable to perform at least one of locating the suspended UE context, restoring the suspended UE context, and resuming one or more suspended E-UTRAN Radio Access Bearers (E-RABs), the MME (204) transmits a resume failure message to the eNodeB (202).
13. The method (500) as claimed in claim 12, wherein upon receipt of the resume failure message, the eNodeB (202) performs at least one of:releasing a Radio Resource Control (RRC) connection for the UE (104); releasing signalling and user-plane transport resources for the UE (104); and initiating a fallback procedure for the UE (104).
14. A system (108) for managing a user equipment (UE) context between an evolved Node B (eNodeB) (202) and a Mobility Management Entity (MME) (204) in a network (106), the system (108) comprising:a processing engine (224) at the eNodeB (202) and the MME (204), wherein the processing engine (224) is configured to:detect a loss of signalling connectivity between the eNodeB (202) and the MME (204) over an SI interface;send a suspend request message requesting suspension of a UE context associated with the UE (104) to the MME (204);identify the UE context as suspended and store one or more elements of UE context information associated with the UE context, in response to receipt of the suspend request message;identify a re-establishment of the signalling connectivity between the eNodeB (202) and the MME (204);send a resume request message to the MME (204) to resume the suspended UE context upon identification of the re-establishment of the signalling connectivity between the eNodeB (202) and the MME (204); andperform a resume procedure for the suspended UE context, in response to receipt of the resume request message.
15. The system (108) as claimed in claim 14, wherein the processing engine (224) is further configured to send a resume response message to the eNodeB (202) after performing the resume procedure.
16. The system (108)as claimed in claim 14, wherein, when the MME (204) determines that at least one of: the UE context identified in the suspend request message is unavailable or suspension of the UE context is unsupported, the MME (204) sends afailure response message to the eNodeB (202) indicating failure of the suspension of the UE context.
17. The system (108) as claimed in claim 14, wherein, upon successful suspension of the UE context, the MME (204) sends a success response message to the eNodeB (202) indicating success of the suspension of the UE context.
18. The system (108) as claimed in claim 17, wherein upon successful suspension of the UE context, the MME (204) transmits a signalling message via an SI 1 interface to an S-GW to perform at least one of holding, buffering, delay forwarding or dropping General Packet Radio Service (GPRS) Tunnelling Protocol User plane (GTP U) packets for the suspended UE context.
19. The system (108) as claimed in claim 14, wherein, the resume procedure performed by the MME (204), wherein the processing engine (224) at the MME (204) is configured to:reactivate the suspended UE context; andtransmit to the S-GW a request to re-establish a GTP-U tunnel toward the eNodeB (202).
20. The system (108) as claimed in claim 14, wherein the one or more elements of the UE context information comprises at least one of a Non-Access Stratum (NAS) security context, an Evolved Packet System (EPS) bearer state, or subscription data associated with the UE (104).
21. The system (108) as claimed in claim 14, wherein the suspend request message comprises at least one of an MME UE SI Application Protocol (AP) Identifier (ID), an eNodeB UE S1AP ID, an information element indicating a duration of the suspension and an information element indicating a cause of the suspension.
22. The system (108) as claimed in claim 21, wherein, when the information element indicating the duration of the suspension is available in the suspend request message, the MME (204) determines an indicated suspend interval from the suspend request message and maintains the suspended UE context for at least the indicated suspend interval, and wherein, when no resume request message is received before expiry of the determined suspend interval, the MME (204) releases the suspended UE context.
23. The system (108) as claimed in claim 14, wherein the MME (204) includes an identifier in the suspend response message; wherein the identifier is a token allocated by the MME (204) to identify the suspended UE context; and wherein the eNodeB (202) stores the identifier in the resume request message to resume the suspended UE context.
24. The system (108) as claimed in claim 14, wherein the eNodeB (202) buffers uplink user data during a period in which the UE context is suspended, and wherein after reestablishment of the signalling connectivity over the SI interface and receipt of the resume response message, the eNodeB (202) sends at least a portion of the buffered uplink user data towards the network (106).
25. The system (108) as claimed in claim 14, wherein, in response to being unable to perform at least one of locating the suspended UE context, restoring the suspended UE context, and resuming one or more suspended E-UTRAN Radio Access Bearers (E-RABs), the MME (204) transmits a resume failure message to the eNodeB (202).
26. The system (108) as claimed in claim 25, wherein upon receipt of the resume failure message, the eNodeB (202) performs at least one of:releasing a Radio Resource Control (RRC) connection for the UE (104);releasing signalling and user-plane transport resources for the UE (104); andinitiating a fallback procedure for the UE (104).
27. 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 perform a method (500)for managing a user equipment (UE) context between an evolved Node B (eNodeB) (202) and a Mobility Management Entity (MME) (204) in a network (106), the method (500) comprising:detecting (502), by the eNodeB (202), a loss of signalling connectivity between the eNodeB (202) and the MME (204) over an SI interface;sending (504), by the eNodeB (202), a suspend request message requesting suspension of a UE context associated with the UE (104) to the MME (204);in response to receipt of the suspend request message, identifying (506), by the MME (204), the UE (104) context as suspended and storing one or more elements of UE context information associated with the UE context;identifying (508), by the eNodeB (202), a re-establishment of the signalling connectivity between the eNodeB (202)and the MME (204);upon identification of the re-establishment of the signalling connectivity between the eNodeB (202) and the MME (204), sending (510), by the eNodeB (202), a resume request message to the MME (204) to resume the suspended UE context; andin response to receipt of the resume request message, performing (512), by the MME (204), a resume procedure for the suspended UE context.
