System and method for service restoration via user equipment fallback in multi-generation wireless networks

Abstract

The present disclosure relates to a system (102) and a method (400) for managing a fallback of a user equipment (UE) (104) in a network (108). The method (400) includes monitoring, by a fallback decision unit (310), one or more data flow parameters indicative of service unavailability over a first radio access node (202) operating within a first network (108A). The method (400) further includes detecting, by a disruption detection unit (312), at least one service disruption condition associated with the first radio access node (202) based on the one or more monitored data flow parameters. The method (400) further includes initiating, by a transition control unit (314), in response to the at least one detected service disruption condition, the fallback of at least one UE (104) from the first radio access node (202) to a second radio access node (203) operating within a second network (108B).

Description

SYSTEM AND METHOD FOR SERVICE RESTORATION VIA USER EQUIPMENT FALLBACK IN MULTI-GENERATION WIRELESS NETWORKSRESERVATION 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 or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.FIELD OF DISCLOSURE

[0002] The present disclosure generally relates to the field of wireless communication systems. More particularly, the present disclosure relates to a system and a method for automatic service restoration in user equipment (UE) through fallback to a lower generation radio access technology (RAT) in case of undetected service disruption in higher generation networks, such as fifth generation (5G) networks.DEFINITIONS

[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.

[0004] The expression ‘Core Network’ used hereinafter in the specification refers to the central part of a telecommunications network that provides various control-plane and user-plane functions including authentication, mobility management, session management, policy enforcement, data forwarding, and interconnection with external networks. In 5G, the core network is typically referred to as the 5G Core (5GC).

[0005] The expression ‘Control Plane’ used hereinafter in the specification refers to the logical network layer responsible for signaling, configuration, and management operations necessary to establish and maintain network services. The control plane includes signaling messages exchanged between network functions and the user equipment (UE) to handle mobility, authentication, session management, and policy control.

[0006] The expression ‘Data Plane’ used hereinafter in the specification refers to the logical network layer responsible for actual user data transfer between the user equipment (UE) and data networks (e.g., internet, enterprise network). It includes data forwarding, packet routing, quality of service (QoS) enforcement, and traffic shaping, typically handled by user-plane functions such as the user plane function (UPF) in 5G networks.

[0007] The expression ‘Fallback’ used hereinafter in the specification refers to a procedure where a user equipment (UE) transitions from a higher-generation network (e.g., 5G) to a lower-generation network (e.g., 4G LTE) when service degradation or disruption is detected in the current network, to maintain continuity of service such as voice or data sessions.

[0008] The expression ‘Network Function (NF)’ used hereinafter in the specification refers to a logical entity within a telecommunications core network, such as a fifth generation (5G) core network, that provides a specific service or performs a designated control or user-plane task. The NF is implemented as a software running on one or more physical or virtualized network nodes and is configured to interact with other NFs through service-based interfaces.

[0009] The expression ‘Access and Mobility Management Function (AMF)’ used hereinafter in the specification refers to a control-plane function in the 5G core network responsible for registration, connection management, reachability, mobility handling, and access authentication of the UE.

[0010] The expression ‘Session Management Function (SMF)’ used hereinafter in the specification refers to a control-plane function in the 5G core network that is responsible for session establishment, modification, and release, as well as allocation of internet protocol (IP) addresses and enforcement of QoS and charging rules.

[0011] The expression ‘Policy Control Function (PCF)’ used hereinafter in the specification refers to a control-plane function in the 5G core network that provides policy rules to control-plane functions such as AMF and SMF based on subscription information, network conditions, or application needs.

[0012] The expression ‘User Plane Function (UPF)’ used hereinafter in the specification refers to a user-plane function in the 5G core network that is responsible for packet routing and forwarding, quality of service (QoS) handling, traffic usage reporting, and interconnection with the data network (DN).

[0013] The expression ‘Network Data Analytics Function (NWDAF)’ used hereinafter in the specification refers to a network function in the 5G core network that collects and analyzes data from various network functions and provides insights or predictions (e.g., mobility patterns, load estimation) to improve network performance or decision-making.

[0014] The expression ‘Unified Data Management (UDM)’ used hereinafter in the specification refers to a network function in the 5G core responsible for subscriber data management, user identity handling, access authorization, and policy provisioning.

[0015] The expression ‘Network Repository Function (NRF)’ used hereinafter in the specification refers to a network function in the 5G core that maintains aregistry of available network functions and their capabilities, and supports service discovery and registration for other network functions.

[0016] The expression ‘gNodeB (gNB)’ used hereinafter in the specification refers to a radio access node in a 5G network that provides wireless connectivity between the UE and the 5G core network. The gNB handles both control-plane and user-plane communication over the air interface and interfaces with the core network via next generation (NG) interfaces.

[0017] The expression ‘eNodeB (eNB)’ used hereinafter in the specification refers to a radio access node in a 4G LTE network that connects UEs to the evolved packet core (EPC). It is responsible for radio resource management, scheduling, mobility support, and relaying control and user data to / from the core network.

[0018] The expression ‘Evolved Packet Core (EPC)’ used hereinafter in the specification refers to all-IP core network that supports packet-switched services, enabling high-speed data, voice over internet protocol (VoIP), and seamless mobility. EPC manages the control and user plane separation, user authentication, session management, mobility, policy enforcement, and interworking with other networks (e.g., 2G / 3G or wireless fidelity (Wi-Fi)).

[0019] The expression ‘Network Element (NE)’ used hereinafter in the specification refers to any identifiable component or logical function within the telecommunications infrastructure, including but not limited to radio access nodes, routers, core network functions, and management systems that participate in delivering communication services.

[0020] The expression ‘Downlink Data’ used hereinafter in the specification refers to data that is transmitted from the network (e.g., gNB or core network) to the user equipment (UE), such as incoming voice packets, video streams, or notifications.

[0021] The expression ‘Uplink Data’ used hereinafter in the specification refers to data that is transmitted from the user equipment (UE) to the network, such as voice commands, user inputs, sensor readings, or outbound requests.

[0022] The expression ‘Inhibited Mode’ used hereinafter in the specification refers to a system state or operational mode in which specific network actions, procedures, or transitions are temporarily disabled or restricted. This mode may be triggered due to network policy, failure detection, or ongoing recovery procedures to prevent unintended behavior.

[0023] The expression ‘System Information Blocks (SIBs)’ used hereinafter in the specification refers to structured information elements broadcast by a radio access node (e.g., eNB or gNB) to all user equipment (UE) in a cell. SIBs provide essential configuration and operational parameters required for the UE to access and operate within the network.

[0024] The expression ‘Network Exposure Function (NEF)’ used hereinafter in the specification refers to a service enabler within the 5G core network that provides secure and controlled exposure of network capabilities and events to external applications or third-party services.

[0025] The expression ‘Radio Access Node’ used hereinafter in the specification refers to a network element that provides wireless communication between user equipment (UE) and a core network. The radio access node (e.g., a next-generation Node B (gNodeB) in 5G or an evolved Node B (eNodeB) in LTE) manages radio resources, performs scheduling, handles mobility functions, and ensures the transmission and reception of user-plane and control-plane signals.

[0026] The expression ‘First Network’ used hereinafter in the specification refers to a higher-generation mobile communication network that provides advanced features such as higher data throughput, lower latency, and enhanced connectivity. For example, the first network may be a fifth generation (5G) or sixth generation (6G) network that is the default or preferred network for the UE under normal operating condition.

[0027] The expression ‘Second Network’ used hereinafter in the specification refers to a lower-generation mobile communication network that serves as a fallback network when the first network is unable to provide satisfactory service quality. For example, the second network may be a fourth generation (4G) LTE network or any earlier-generation network providing voice and data services.

[0028] The expression ‘First Radio Access Node’ used hereinafter in the specification refers to a radio access node (e.g., a 5G gNodeB) associated with the first network that establishes and maintains wireless communication with the UE under normal conditions.

[0029] The expression ‘Second Radio Access Node’ used hereinafter in the specification refers to a radio access node (e.g., a 4G eNodeB) associated with the second network that provides fallback connectivity for the UE when the first radio access node or the first network experiences service disruption or degraded performance.

[0030] The expression ‘Core Network Function’ used hereinafter in the specification refers to a logical function within the core network that performs control-plane or user-plane operations, including but not limited to session management, mobility management, data forwarding, policy control, or analytics.

[0031] The expression ‘Service Disruption Condition’ used hereinafter in the specification refers to a state or event where connectivity or service quality is degraded, interrupted, or unavailable. Such conditions may arise due to packet loss, throughput reduction, signaling failures, radio link failures, excessive latency, or user-plane impairments that affect essential services like voice calls, emergency communications, or data sessions.

[0032] The expression ‘Configurable Duration of Time’ used hereinafter in the specification refers to a pre-defined or dynamically adjustable time interval set by the system or operator. This interval defines how long a service degradation, outage, or unavailability must persist before triggering actions such as fallback, reselection, or recovery procedures.

[0033] The expression ‘Element Management System (EMS)’ used hereinafter in the specification refers to a centralized management system responsible for supervising, configuring, and monitoring network elements (NEs) such as radio access nodes or core network functions. The EMS performs tasks such as fault management, performance tracking, software updates, parameter adjustments, and can trigger fallback or recovery mechanisms when service disruptions are detected.

[0034] These definitions are in addition to those expressed in the art.BACKGROUND OF DISCLOSURE

[0035] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0036] Modem wireless communication networks, such as fifth generation (5G) networks, are designed to offer significantly enhanced data rates, ultra-low latency, and higher network capacity compared to legacy generations like fourth generation (4G) long-term evolution (LTE) networks. To leverage these capabilities, mobile devices are generally configured in a “5G preferred” mode by default. This configuration prioritizes connection to the 5G networks whenever available, while falling back to 4G or lower generation radio access technologies (RATs) only in scenarios where 5G coverage is not detected or 5G is unable to support specific services like voice calls through a voice over new radio (VoNR).

[0037] However, real-world deployments have revealed certain operational limitations in a 5G radio layer, particularly in rare but impactful cases where a control plane remains intact, but a user plane (data path) experiences disruptions due to internal issues at a 5G radio network (gNB). In such situations, user equipment (UE) continues to show 5G coverage and remains registered with a 5G core network, but user-level services such as voice and data become non-functional.

[0038] Conventional fallback mechanisms, such as evolved packet system (EPS) fallback, are generally limited to specific scenarios, for example, a voice service handover from the 5G network to the 4G network when the VoNR is unavailable. However, these mechanisms are not designed to address broader service disruptions that may originate from radio-side anomalies, where a userplane data flow is impaired even though control-plane signaling remains operational.

[0039] Users experiencing this condition often resort to manual intervention, such as toggling airplane mode, restarting a device, or manually switching their network preference to LTE / 4G to restore the services. However, such approaches are inconvenient, non-intuitive, and lack automation, leading to poor user experience and extended service downtime.

[0040] Thus, there is a need for a network-assisted or device-based intelligent fallback mechanism that can automatically detect service unavailability in a higher- generation RAT and initiate a controlled fallback to a lower-generation RAT (e.g., 4G or 3G) without requiring a user action.OBJECTIVES OF THE PRESENT DISCLOSURE

[0041] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as listed below.

[0042] An objective of the present disclosure is to provide a system and method for enabling intelligent fallback of a user equipment (UE) from a higher-generation radio access technology (RAT), such as 5G network, to a lower-generation RAT (e.g., 4G LTE) in response to service disruption conditions.

[0043] Another objective of the present disclosure is to provide a system and method for detecting partial or complete service unavailability in higher-generation radio cells by monitoring data flow parameters at UE, a radio access network (RAN), or a core network, and initiating fallback based on configurable thresholds and durations.

[0044] Yet another objective of the present disclosure is to provide a seamless and automatic restoration mechanism that allows UE to reconnect to a higher- generation RAT once service conditions are reestablished, without requiring manual intervention or persistent configuration changes.

[0045] Still another objective of the present disclosure is to minimize user service disruptions and improve the quality of experience (QoE) by enabling timely transitions between RATs based on real-time service availability and performance conditions, rather than static signal strength-based criteria.

[0046] Another objective of the present disclosure is to provide a UE-centric fallback and recovery mechanism that temporarily overrides higher-generation RAT preference settings, enabling the UE to maintain continuous connectivity and service availability even during higher-generation network issues.

[0047] Another objective of the present disclosure is to provide a system and method that enables service restoration of UE connections by transitioning the UE from a higher-generation network to a lower-generation network upon detecting a disruption, ensuring continuity of voice, data, and application-layer services.

[0048] Another objective of the present disclosure is to enable a system to identify service impact conditions and autonomously trigger fallback without requiring user input or external commands, thereby achieving automatic and intelligent network transitions.

[0049] Still another objective of the present disclosure is to provide a method that supports real-time monitoring of network conditions, such as throughput, latency, packet loss, and radio frequency (RF) metrics, to proactively detect service degradation before it significantly affects user experience.

[0050] Still another objective of the present disclosure is to provide a mechanism that factors in user preferences and historical behavior to optimize network reselection and fallback decisions, aligning with user expectations and prior usage patterns.

[0051] Another objective of the present disclosure is to enable a system to communicate transition status to users through notifications or status indicators, thereby improving transparency and user awareness during fallback and recovery operations.

[0052] Other objectives 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.SUMMARY

[0053] In an exemplary embodiment, the present invention discloses a method for managing a fallback of a user equipment (UE) in a network. The method includes monitoring, by a fallback decision unit, one or more data flow parameters indicative of service unavailability over a first radio access node operating within a first network. The method further includes detecting, by a disruption detection unit, at least one service disruption condition associated with the first radio access node based on the one or more monitored data flow parameters. The method further includes initiating, by a transition control unit, in response to the at least one detected service disruption condition, the fallback of at least one UE from the first radio access node to a second radio access node operating within a second network.

[0054] In some embodiments, each of the fallback decision unit, the disruption detection unit, and the transition control unit is implemented at one of the UE, a radio access node, or a core network function.

[0055] In some embodiments, the service disruption condition associated with the first radio access node is detected at the UE when the one or more monitored data flow parameters deviate from a predefined threshold for a configurable duration of time.

[0056] In some embodiments, the service disruption condition associated with the first radio access node is detected at the core network function by analyzing historical data patterns associated with the first radio access node.

[0057] In some embodiments, the method further includes transmitting, by the core network function, an indication of the service disruption condition to an element management system (EMS) when a deviation is identified between the historical data patterns and the one or more monitored data flow parameters.

[0058] In some embodiments, the service disruption condition is detected at the radio access node by identifying one or more anomalies at the radio access node. The one or more anomalies include at least one of internal software malfunctions, scheduling failures, and abnormal behavior at one or more radio protocol layers.

[0059] In some embodiments, the fallback of the at least one UE from the first radio access node to the second radio access node is triggered at the core network function by changing, through the EMS, an operational status of the first radio access node that causes the at least one UE to reselect to the second radio access node.

[0060] In some embodiments, the fallback of the at least one UE from the first radio access node to the second radio access node is triggered at the radio access node by ceasing a broadcast of one or more system information blocks (SIBs) from the first radio access node.

[0061] In some embodiments, the fallback of the at least one UE from the first radio access node to the second radio access node is triggered at the UE by initiating a reselection procedure even when the UE is configured with a preference for the first network.

[0062] In some embodiments, the first network is a fifth generation (5G) network and the second network is a fourth generation (4G) network.

[0063] In some embodiments, the fallback of the at least one UE from the first radio access node to the second radio access node is initiated despite an availability of the first network at the UE.

[0064] In an exemplary embodiment, a system for managing a fallback of a user equipment (UE) in a network is disclosed. The system includes a fallbackdecision unit configured to monitor one or more data flow parameters indicative of service unavailability over a first radio access node operating within a first network. The system further includes a disruption detection unit configured to detect at least one service disruption condition associated with the first radio access node based on the one or more monitored data flow parameters. The system further includes a transition control unit configured to initiate, in response to the at least one detected service disruption condition, the fallback of at least one UE from the first radio access node to a second radio access node operating within a second network.

[0065] In some embodiments, each of the fallback decision unit, the disruption detection unit, and the transition control unit is implemented at one of the UE, a radio access node, or a core network function.

[0066] In some embodiments, the service disruption condition associated with the first radio access node is detected at the UE when the one or more monitored data flow parameters deviate from a predefined threshold for a configurable duration of time.

[0067] In some embodiments, the service disruption condition associated with the first radio access node is detected at the core network function by analyzing historical data patterns associated with the first radio access node.

[0068] In some embodiments, the disruption detection unit is further configured to transmit, by the core network function, an indication of the service disruption condition to an element management system (EMS) when a deviation is identified between the historical data patterns and the one or more monitored data flow parameters.

[0069] In some embodiments, the service disruption condition is detected at the radio access node by identifying one or more anomalies at the radio access node. The one or more anomalies include at least one of internal software malfunctions, scheduling failures, and abnormal behavior at one or more radio protocol layers.

[0070] In some embodiments, the fallback of the at least one UE from the first radio access node to the second radio access node is triggered at the core network function by changing, through the EMS, an operational status of the first radio access node that causes the at least one UE to reselect to the second radio access node.

[0071] In some embodiments, the fallback of the at least one UE from the first radio access node to the second radio access node is triggered at the radio access node by ceasing a broadcast of one or more system information blocks (SIBs) from the first radio access node.

[0072] In some embodiments, the fallback of the at least one UE from the first radio access node to the second radio access node is triggered at the UE by initiating a reselection procedure even when the UE is configured with a preference for the first network.

[0073] In some embodiments, the first network is a fifth generation (5G) network and the second network is a fourth generation (4G) network.

[0074] In some embodiments, the fallback of the at least one UE from the first radio access node to the second radio access node is initiated despite an availability of the first network at the UE.

[0075] In an exemplary embodiment, a user equipment (UE) for managing a fallback in a network is disclosed. The UE is configured to monitor one or more data flow parameters indicative of service unavailability over the first radio access node operating within a first network. The UE is further configured to detect at least one service disruption condition associated with the first radio access node based on the one or more monitored data flow parameters. The UE is further configured to initiate, in response to the at least one detected service disruption condition, the fallback of at least one UE from the first radio access node to a second radio access node operating within a second network.

[0076] In some embodiments, the service disruption condition associated with the first radio access node is detected at the UE when the one or more monitored data flow parameters deviate from a predefined threshold for a configurable duration of time.

[0077] In some embodiments, the fallback of the at least one UE from the first radio access node to the second radio access node is triggered at the UE by changing, through the EMS, an operational status of the first radio access node that causes the at least one UE to reselect to the second radio access node.

[0078] In some embodiments, the first network is a fifth generation (5G) network and the second network is a fourth generation (4G) network.

[0079] In an exemplary embodiment, a computer program product including a non-transitory computer-readable medium including instructions that, when executed by one or more processors, cause the one or more processors to execute a method for managing a fallback of a user equipment (UE) in a network. The method includes monitoring, by a fallback decision unit, one or more data flow parameters indicative of service unavailability over a first radio access node operating within a first network. The method further includes detecting, by a disruption detection unit, at least one service disruption condition associated with the first radio access node based on the one or more monitored data flow parameters. The method further includes initiating, by a transition control unit, in response to the at least one detected service disruption condition, the fallback of at least one UE from the first radio access node to a second radio access node operating within a second network.

[0080] 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.BRIEF DESCRIPTION OF DRAWINGS

[0081] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of thedisclosed 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 the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0082] FIG. 1 illustrates an exemplary network architecture for implementing a system to manage a fallback of a user equipment (UE) in a network, in accordance with embodiments of the present disclosure.

[0083] FIG. 2 illustrates another exemplary network architecture of the system for service restoration of the UE connected with a first network, in accordance with embodiments of the present disclosure.

[0084] FIG. 3 illustrates an exemplary block diagram of the system, in accordance with embodiments of the present disclosure.

[0085] FIG. 4 illustrates an exemplary flowchart of a method for managing the fallback of the UE in the network, in accordance with embodiments of the present disclosure.

[0086] FIG. 5 illustrates an exemplary computer system in which or with which the system and method may be implemented, in accordance with embodiments of the present disclosure.

[0087] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102 - System104-1, 104-2. . . 104-N - Plurality of User Equipment (UE)106-1, 106-2. . . 106-N - Plurality of Users108 - Network108 A - First Network108B - Second Network200 - Network Architecture202 - First Radio Access Node203 - Second Radio Access Node204 - Core Network206 - Control Plane208 - Data Plane210 - Element Management System (EMS)212 - Database300 - Block Diagram302 - Processor(s)304 - Memory306 - Interface(s)308 - Processing Engine310 - Fallback Decision Unit312 - Disruption Detection Unit314 - Transition Control Unit400 - Method Flowchart500 - Computer System510 - External Storage Device520 - Bus530 - Main Memory540 - Read-Only Memory550 - Mass Storage Device560 - Communication Ports570 - ProcessorDETAILED DESCRIPTION OF DISCLOSURE

[0088] In the following description, for the purposes of explanation, various specific details are set forth to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

[0089] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in thefunction and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0090] 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 to avoid obscuring the embodiments.

[0091] 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.

[0092] 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.

[0093] 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 features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0094] The terminology used herein is to describe embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a” “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

[0095] As used herein, an “electronic device” or “portable electronic device” or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical, and computing device. The user device can receive and / or transmitting one or parameters, performing function / s, communicating with other user devices, and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery, and an input-means such as a hard keypad and / or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.

[0096] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general -purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.

[0097] Aspects of this disclosure are directed to a system and method for managing radio access and mobility of user equipment (UE) in a 5G communication network, in scenarios where the UE is registered with or latched onto a partially available or degraded 5G cell. In conventional deployments, UEs may remain connected to 5G cells that have limited or non-functional user plane services,leading to prolonged service outages, failed data sessions, or application-level timeouts, while the UE continues to report good radio conditions. This results in a degraded user experience, inefficient radio resource utilization, and delayed recovery from coverage gaps.

[0098] The present disclosure introduces a fallback mechanism that enables the UE, or a network, to detect prolonged data inactivity or service disruptions while connected to the 5G cell and to trigger an intelligent fallback to a lower generation RAT (e.g., 4G LTE) for service continuity. The fallback trigger is based on configurable thresholds such as inactivity timers, application-specific metrics, or network-side indications of degraded service availability. Once fallback conditions are met, the system initiates inter-radio access technology (RAT) reselection or redirection procedures to connect the UE to a more stable RAT, while continuously monitoring for restoration of 5G service. Upon re-establishment of satisfactory 5G service conditions, the system automatically re-attempts registration or handover back to 5G without user intervention. This inventive approach provides an end-to- end fallback and recovery framework that operates across UE, RAN, and core network layers to ensure consistent service availability, improve user experience, and optimize access network behavior under partially degraded 5G coverage scenarios.

[0099] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1- FIG. 5.

[0100] FIG. 1 illustrates an exemplary network architecture (100) for implementing a system (102) to manage a fallback of a user equipment (UE) (104) in a network (108), in accordance with embodiments of the present disclosure.

[0101] Referring to FIG. 1, the network architecture (100) may include one or more user equipment (UEs) (104-1, 104-2. .. 104-N) that may be associated with one or more users (106-1, 106-2. . . 106-N) and the system (102) in an environment. In an embodiment, the one or more UEs (104-1, 104-2. .. 104-N) may be communicated to the system (102) through the network (108). A person of ordinaryskill in the art will understand that the 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). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “UE” may be used interchangeably throughout the disclosure. Although three UEs (104) are depicted in the FIG. 1, however any number of the UE (104) may be included without departing from the scope of the ongoing description. Similarly, a person of ordinary skill in the art will understand that the one or more users (106-1, 106-2. . . 106-N) may be individually referred to as the user (106) and collectively referred to as the users (106).

[0102] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such 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 systems, 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 (106) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE (104) may include, but not be 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.

[0103] In an embodiment, the UE (104) may include but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, 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, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like.

[0104] In an embodiment, the UE (104) may include, but is not limited to, any electrical, electronic, electro-mechanical, or equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, a general -purpose computer, a desktop, a personal digital assistant, a mainframe computer, or any other computing device. In another embodiment, 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 (106) or the entity such as a touchpad, 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.

[0105] Referring to FIG. 1, the UE (104) may operate based on a set of executable instructions residing within its operating system. The executable instructions are configured to continuously evaluate the service availability and capabilities of the currently connected 5G cell. Upon detecting that the 5G cell is partially available or degraded, for example, lacking support for essential services such as internet protocol (IP) multimedia subsystem (IMS) voice, emergency calls, or lacking full mobility support. The executable instructions initiate a fallback procedure to an evolved packet system (EPS) network. The fallback procedure ensures that the UE (104) transitions to a legacy LTE cell that may reliably support the required services.

[0106] In an embodiment, the UE (104) may communicate with the system (102) through the network (108) for sending or receiving various types of data. In an embodiment, the network (108) may include at least one of a 5G network, a 6G network, or the like. The network (108) may enable the UE (104) to communicate with other devices in the network architecture (100) and / or with the system (102). The network (108) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (108) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local areanetwork (LAN), a wireless network, a mobile network, a virtual private network (VPN), the Internet or the like.

[0107] In an embodiment, the network (108) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network (108) may also include, by way of example but not limitation, one or more of a radio access network (RAN), a wireless network, a wired network, the internet, the intranet, a public network, a private network, a packet-switched network, a circuit- switched network, an ad hoc network, an infrastructure network, a public-switched telephone network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. In an embodiment, the system (102) may be connected to backend servers (not shown).

[0108] Although the 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).

[0109] FIG. 2 illustrates another exemplary network architecture (200) of the system (102) for service restoration of the UE (104) connected with a first network (108A), in accordance with embodiments of the present disclosure. In an embodiment, the network (108), as illustrated in FIG. 1, includes a heterogeneous architecture including multiple network types. In an embodiment, a network configuration facilitates improved connectivity and enhanced service resilience for the UE (104) operating within the system (102). In one embodiment, the network (108) may include the first network (108A) and a second network (108B), eachserving distinct roles in the overall communication framework. In an embodiment, the first network (108 A) represents a higher generation mobile communication network characterized by advanced technological capabilities and superior performance metrics. In this embodiment, the first network (108A) may be a fifthgeneration (5G) network or a sixth-generation (6G) network. The first network (108A) offers enhanced data throughput, reduced latency, and increased connection density compared to its predecessors. The first network (108A) is engineered to support a wide array of applications, including but not limited to, Internet of Things (loT) deployments, augmented reality (AR), and critical communications. In an embodiment, the network architecture (200) may leverage advanced technologies such as massive multiple-input multiple-output (MIMO), beamforming, and network slicing to optimize resource allocation and service delivery.

[0110] In an embodiment, the second network (108B) operates as a lower- generation mobile communication network, providing a fallback option for the UE (104) when the first network (108A) is unable to maintain a satisfactory level of service. In this embodiment, the second network (108B) may be identified as a fourth generation (4G) network. The 4G network, while offering lower data rates and higher latency compared to the 5G network, remains a viable alternative for supporting essential mobile communication services. The second network (108B) provides reliable voice and data services, ensuring continued connectivity for the UE (104) in scenarios where the first network (108A) experiences disruptions or degraded performance. By integrating the first network (108 A) and the second network (108B) within the network (108), the system (102) enables dynamic service restoration capabilities for the UE (104). This is beneficial in maintaining user experience during instances of service degradation in the higher-generation mobile communication network. The network architecture (200) supports automatic transitioning of the UE (104) from the first network (108A) to the second network (108B) based on real-time performance metrics, thereby ensuring uninterrupted access to communication services.

[0111] In an operative aspect, the UE (104) is operably connected to the first network (108 A) through a first radio access node (202), such as a next-generation Node B (gNodeB). The UE (104) refers to any device utilized by an end user to access network services, which may include, but is not limited to, smartphones, tablets, laptops, loT devices, and other mobile communication devices. The UE (104) serves as an interface for the users (106) to engage with capabilities of the first network (108 A), enabling functionalities such as voice communication, data transmission, and access to various applications. The first radio access node (202) represents the next-generation base station within the first network (108 A) architecture that facilitates wireless communication between the UE (104) and a core network (204). The first radio access node (202) manages radio resources, processes user data, and ensures seamless connectivity. The first radio access node (202) supports various radio access technologies and protocols that enable the transmission of data packets and voice calls to and from the UE (104). Furthermore, the first radio access node (202) is responsible for managing handover procedures, ensuring that the UE (104) maintains a continuous connection while moving between coverage areas or transitioning to different network conditions. In scenarios where the UE (104) detects service degradation within the first network (108 A) due to reduced radio coverage, the first radio access node (202) may facilitate the transition of the UE (104) to an alternative network, such as the second network (108B), thereby ensuring uninterrupted service availability.

[0112] Further, the first radio access node (202) and the second radio access node (203) may be connected to the core network (204). The core network (204) is a pivotal component that enables high-speed connectivity, low latency, and support for a vast number of devices. The core network (204) serves as a backbone of the network architecture (200), facilitating various functionalities such as data routing, service management, and user authentication. The network architecture (200) may be a 5G core network architecture that is designed to be flexible, scalable, and service-oriented. The core network (204) employs a service-based architecture(SBA), which allows different network functions to communicate with each other through standard application programming interfaces (APIs).

[0113] In an aspect, the core network (204) includes a control plane (206) and a data plane (208). The control plane (206) is responsible for signaling and managing connections and sessions between the UE (104) and the network (108), encompassing key functions such as session management (establishing, modifying, and releasing sessions), mobility management (tracking and managing user movement between different network cells), authentication and security (ensuring user authentication and data security), and policy and charging control (managing network policies and charging rules). The control plane (206) is handled primarily by the network functions such as an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), a unified data management (UDM), a network slice selection function (NSSF), and so forth. The control plane (206) is responsible for signaling and control functions that facilitate the management of network resources, user sessions, and mobility. The control plane (206) does not handle user data but manages the signaling messages necessary to establish and maintain connections. In an example, the control plane (206) may include:• a user plane function (UPF): Although the UPF is primarily associated with the data plane (208), the UPF interacts with the control plane (206) for the session management. The UPF may include dedicated hardware such as servers configured to handle session establishment requests and mobility management tasks. The UPF combines user traffic transport functions previously performed in 4G by a serving gateway (S-GW) and a packet data network gateway (P-GW) in a 4G evolved packet core (EPC);• the access and mobility management function (AMF): The AMF manages the registration, connection, and mobility of the UE (104). The AMF communicates with the first radio access node (202) to coordinate user sessions and track user location;• the session management function (SMF): The SMF is responsible for creating, modifying, and deleting sessions for the UE (104). The SMF interacts with the UPF and the AMF to establish necessary data paths and manage network resources effectively. The SMF brings the control plane (206) functionality of a serving gateway control plane (SGW-C) and a packet gateway control plane (PGW-C) in addition to providing the session management functionality of the 4G mobility management entity (MME); and• a network repository function (NRF): NRF maintains a database (212) of network functions and enables discovery and registration of various network components within the control plane (206).

[0114] The data plane (208) is responsible for an actual transmission of the user data in coordination with the radio network. The data plane (208) handles routing and forwarding of data packets between the UE (104) and the internet. The data plane (208) is configured for data forwarding (transmits data packets between the UE (104) and the external networks), traffic management (manages the flow of data to ensure that it meets the required performance criteria, such as latency and throughput), and maintaining quality of service (QoS) (ensures that the data flow meets the specified performance requirements, such as bandwidth, delay, and jitter, as defined by the control plane (206)). In the first network (108 A), the data plane (208) functions are managed by elements such as the UPF, which handles the actual user data forwarding and processing. The UPF plays a dual role, serving both the control plane (206) and the data plane (208). In the data plane (208), the UPF routes user data packets to their respective destinations, such as the Internet or other service providers. The UPF hardware includes high-throughput routers and switches optimized for low latency and high data rates. In an example, the control plane (206) further includes: a data network (DN) that refers to external networks that the 5G network connects to, such as the Internet or private enterprise networks. The DN may include routers, firewalls, and other network components that ensure secure and efficient data transmission; and edge computing nodes that aredistributed computing resources positioned at the edge of the network (108), allowing for localized data processing and storage. This helps in reducing the latency by processing data closer to the user and can be part of the data plane (208) for applications requiring real-time processing.

[0115] The network architecture (200) includes an element management system (EMS) (210), which includes various systems and applications for managing various network elements (NEs) on a network element-management layer (NEL). The EMS (210) is configured to manage one or more of a specific type of telecommunications network element. The EMS (210) manages the functions and capabilities within each NE but does not manage the traffic between different NEs in the network (108). The EMS (210) is responsible for the management and monitoring of the NEs. The EMS (210) is designed to manage individual NEs, such as routers, switches, base stations, and other equipment within the network (108). The EMS (210) ensures that these NEs are properly configured, operational, and maintained. The EMS (210) provides real-time monitoring of the NEs, tracking their performance and health. The EMS (210) detects faults or issues within these elements and triggers alerts or corrective actions to resolve problems. The EMS (210) allows for the configuration and reconfiguration of the NEs which includes setting parameters, updating software, and applying patches to ensure optimal performance. The EMS (210) collects and analyzes performance data from the NEs, providing insights into the overall network performance. The insights help in identifying bottlenecks, optimizing resources, and planning capacity. The EMS (210) manages a software lifecycle of the NEs, including software updates, patches, and version control. The EMS (210) ensures a security of the NEs by managing access controls, monitoring security events, and applying security policies. The EMS (210) facilitates centralized control and visibility over the network infrastructure, allowing network operators to efficiently manage resources and optimize performance. The EMS (210) provides an interface for configuring network settings, monitoring system health, and performing diagnostic tasks.

[0116] In an operative aspect, the EMS (210) is coupled with the first radio access node (202), and the core network (204). In an embodiment, a coupling of the EMS (210) with the first radio access node (202) allows management of radio resources, configuration of transmission parameters, and monitoring of radio performance. This coupling ensures an optimal operation of the radio access network and enables timely adjustments to enhance the user experience. The EMS (210) may remotely configure the settings of the first radio access node (202) based on real-time performance data, such as, but not limited to, adjusting power levels or modifying frequency allocations to mitigate interference and improve signal quality.

[0117] Further, in an embodiment, a coupling of the EMS (210) with the core network (204) enables a comprehensive management of network services and resources. This coupling facilitates the monitoring of data flows, session establishments, and overall network health, ensuring that user sessions are efficiently handled, and resources are optimally utilized. If the EMS (210) detects anomalies in data traffic patterns within the core network (204), the EMS (210) may initiate corrective actions, such as reallocating resources or notifying operators for further investigation.

[0118] In an operative aspect, the detection of service impact and the triggering of fallback within the system (102) may be performed at multiple levels, including the UE (104), the radio access node, and a core network function, as described below:

[0119] At the UE level, the detection of service impact involves monitoring radio frequency (RF) attributes received from the first network (108A). In an embodiment, RF signal strength is a critical metric indicating the quality of the link between the UE (104) and the first radio access node (202). Each UE (104) is configured with a predefined RF threshold necessary for reliable communication. When the RF signal remains above the predefined RF threshold, yet the UE (104) is unable to access services (e.g., no data flow or call connectivity), this indicates aservice-impacting condition that is not due to coverage issues but due to networkside degradation.

[0120] The UE (104) monitors both uplink and downlink signaling levels to assess connectivity. For instance, if the uplink signaling (e.g., transmission of requests or acknowledgments) is successful but no corresponding downlink data is received, the UE (104) interprets this as a potential unidirectional communication failure or partial data plane disruption. For example, the user attempting to stream video may observe that an application fails to load despite a strong RF signal. While the UE’s uplink requests (e.g., video stream initiation) are transmitted, no downlink packets are returned, indicating a service outage on a downlink path. Such scenarios trigger UE’s internal quality evaluation algorithms. In scenarios where the service remains unavailable for a configurable duration (e.g., 10 seconds), the UE (104) autonomously overrides its preferred network settings (e.g., “5G preferred”) and falls back to the second network (108B) (e.g., 4G LTE). This ensures uninterrupted access to the services without requiring manual intervention. For example, during a persistent service outage, the UE (104) automatically transitions to the 4G network to restore internet connectivity, even if the 5G network remains nominally available.

[0121] At the radio access node level, the service impact detection involves monitoring key performance indicators (KPIs) such as reference signal received power (RSRP), reference signal received quality (RSRQ), and signal -to-noise ratio (SNR). A degradation of these metrics below configured thresholds may indicate radio interference, hardware malfunction, or scheduling issues within the first radio access node (202).

[0122] The radio access node also monitors data flow metrics such as, but not limited to, throughput, latency, packet loss, and so forth. For example, persistently low throughput despite acceptable RF conditions indicates network congestion or internal protocol layer issues. Such conditions trigger the radio access node to initiate fallback actions.

[0123] In critical scenarios where the radio access node detects a non- recoverable failure affecting all the connected UEs (104), the radio access node may autonomously initiate the fallback by ceasing a broadcast of essential system information blocks (SIBs), such as SIB1 or SIB2. This action forces all the UEs (104) to reselect an alternative cell, such as a 4G LTE node (second network 108B). For example, if the gNodeB experiences a critical software fault resulting in a data plane failure, the broadcast halt ensures that the UEs (104) immediately transition to the 4G network without service interruption.

[0124] At the core network level, the service impact detection is performed by the core network function or the EMS (210) through real-time monitoring of data traffic KPIs such as, but not limited to, latency, throughput, packet loss, and session continuity. In an embodiment, high latency, sudden packet flow cessation, or repeated session setup failures indicate potential service disruptions. In an embodiment, the EMS (210) tracks the session management data, such as session establishment and modification statistics. Frequent session failures or abrupt session terminations may signal underlying service issues. Upon detecting that all the UEs (104) associated with the first radio access node (202) have lost data flow, the EMS (210) instructs the first radio access node (202) to enter an “inhibited mode,” forcing all the UEs (104) to reconnect to the second network (e.g., 4G LTE) (108B).

[0125] In an embodiment, the EMS (210) utilizes historical data patterns, stored in the database (212), to validate and optimize fallback decisions. For instance, if no packet flows are observed for all the connected UEs over the first radio access node (202) for a predefined interval (e.g., one minute), and the historical data patterns indicates recurring failures at that first radio access node (202), the EMS (210) switches the first radio access node (202) to an inhibited state. This triggers automatic fallback of the UEs (104) to neighboring LTE cells.

[0126] FIG. 3 illustrates an exemplary block diagram (300) of the system (102), in accordance with embodiments of the present disclosure. FIG. 3 is explained in conjunction with FIG. 1 and FIG. 2.

[0127] Referring to FIG. 3, in an embodiment, the system (102) may include one or more processor(s) (302). The one or more processor(s) (302) 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) (302) may be configured to fetch and execute computer-readable instructions stored in a memory (304) of the system (102). The memory (304) may be configured to store one or more computer- readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (304) 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.

[0128] In an embodiment, the system (102) may include an interface(s) (306). The interface(s) (306) may comprise a variety of interfaces, for example, interfaces for data input and output devices (VO), storage devices, and the like. The interface(s) (306) may facilitate communication through the system (102). The interface(s) (306) may also provide a communication pathway for one or more components of the system (102). Examples of such components include, but are not limited to, a processing engine(s) (308) and the database (212).

[0129] In an embodiment, the processing engine(s) (308) may be implemented as a combination of hardware and programming, for example, programmable instructions, to implement one or more functionalities of the processing engine(s) (308). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, theprogramming for the processing engine(s) (308) may be processor-executable instructions stored on a non-transitory machine-readable storage medium, and the hardware for the processing engine(s) (308) may comprise a processing resource, for example, one or more processors, to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) (308). In such examples, the system (102) may comprise 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 (102) and the processing resource. In other examples, the processing engine(s) (308) may be implemented by electronic circuitry.

[0130] In an embodiment, database (212) may include data that may be either stored or generated as a result of functionalities implemented by any of the components of the processor (302) or the processing engine (308). In an embodiment, the database (212) may be separate from the system (102). In an embodiment, the database (212) may store data that may be generated as a result of functionalities implemented by any of the components of the processor (302) or the processing engine (308). In an embodiment, the database (212) may be indicative of including, but not limited to, a relational database, a distributed database, a cloudbased database, or the like. In an exemplary embodiment, the processing engine (308) 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.

[0131] In an embodiment, the processing engine (308) may be implemented at the UE (104). The UE (104) is configured to independently monitor service availability and autonomously trigger the fallback of the UE (104) from the first radio access node (202) operating within the first network (108 A) to the second radio access node (203) operating within the second network (108B), upon detection of the service disruption. In another embodiment, the processing engine (308) may be implemented at the radio access node (e.g., gNB), where the radioaccess node detects network-wide malfunctions and ceases broadcasting system information to compel the UEs (104) to fallback from the first radio access node (202) to the second radio access node (203). In yet another embodiment, the processing engine (308) may be implemented at the core network function, where the core network function detects abnormal data flow patterns or service outages and instructs the EMS (210) to change the operational status of an affected radio node, thereby causing the connected UEs (104) to fallback from the first radio access node (202) to the second radio access node (203). In an embodiment, the processing engine (308) may be distributed across the UE (104), the radio access node and the core network function in a cooperative manner.

[0132] In an embodiment, the processing engine (308) may include a plurality of functional units that enable one of the UE (104), the radio access node, or the core network function to perform one or more operations for managing the fallback of the UE (104). The functional units may include, but are not limited to, a fallback decision unit (310), a disruption detection unit (312) and a transition control unit (314). Each of the fallback decision unit (310), the disruption detection unit (312) and the transition control unit (314) is implemented at one of the UE (104), the radio access node, or the core network function.

[0133] The fallback decision unit (310) is configured to monitor one or more data flow parameters indicative of the service unavailability over the first radio access node (202). As used herein, the term “service unavailability” refers to a condition where one or more essential services expected by the UE (104), such as IP multimedia subsystem (IMS) voice, emergency call support, or general packet- switched IP connectivity, are partially or entirely inaccessible or degraded beyond acceptable thresholds. The service unavailability may result from impairments in either or both of the data plane (208) and the control plane (206).

[0134] In an embodiment, the data flow parameters may be used to assess whether the essential services are operational over the first radio access node (202). In the case of data plane impairment, the fallback decision unit (310) may beconfigured to monitor the data flow parameters such as, but not limited to, a packet loss rate, a downlink or uplink throughput, a latency or round-trip time (RTT), a packet discard count, a quality of service (QoS) flow status (e.g., inactive or failed QoS flow identifier (QFI) mappings), a session continuity failure (e.g., interruption of an active packet data unit (PDU) session), a packet delay variation (jitter), and so forth. These data flow parameters, either individually or in combination, may indicate that the user plane data path is degraded or non-functional, even if the control plane (206) remains available. For example, persistent high latency or packet loss may indicate application layer services (e.g., video streaming, voice- over-IP) are unusable.

[0135] In another embodiment, the service unavailability may also result from control plane impairments. In such embodiment, the fallback decision unit (310) may monitor control-plane specific data flow parameters such as, but not limited to, inability of the UE (104) to register with the IMS, failure to establish or maintain signaling connections, unavailability of signaling bearers, rejection messages from core network functions during session or service setup, failures in executing or completing non-access stratum (NAS) procedures, and so forth. These data flow parameters indicate that the UE (104) is unable to establish or maintain necessary signaling exchanges, thereby preventing the service access.

[0136] In one embodiment, the fallback decision unit (310) is configured to periodically or continuously monitor the data flow parameters indicative of the service unavailability over the first radio access node (202). The periodic monitoring may be based on a predefined timer interval (e.g., every few seconds or minutes), a threshold-based trigger (e.g., sudden drop in throughput or increase in packet loss), or dynamically adjusted based on current traffic conditions or historical trends. The fallback decision unit (310) is configured to transmit the one or more monitored data flow parameters to the disruption decision unit (312).

[0137] The disruption decision unit (312) is communicatively coupled to the fallback decision unit (310), and configured to receive the one or more monitoreddata flow parameters. The disruption decision unit (312) is configured to detect at least one service disruption condition associated with the first radio access node (202) based on the monitored data flow parameters. In an exemplary embodiment, the service disruption condition may be defined as any persistent or significant degradation, interruption, or failure in service delivery that adversely impacts the user experience or compromises the reliability of ongoing or critical services (e.g., IMS voice or emergency calls). The disruption decision unit (312) may be configured to identify the service disruption conditions by analyzing the monitored data flow parameters against preconfigured thresholds, patterns, or learned behavior models. In an exemplary embodiment, the disruption decision unit (312) may be configured to compare real-time values of the data flow parameters (such as packet loss rate, RTT, throughput, jitter, etc.) against preconfigured threshold values that are specific to service types (e.g., voice, video). For instance, if the packet loss rate exceeds 2% for a VoIP service over a sustained time window, it may be flagged as the service disruption condition. In another exemplary embodiment, the disruption detection unit (312) may track historical trends of the data flow parameters over sliding time windows to detect abnormal increases or fluctuations. For example, a gradual but persistent rise in the RTT over 5 seconds may indicate early signs of congestion or link degradation. In yet another exemplary embodiment, the disruption detection unit (312) may correlate multiple data flow parameters to detect compound issues. For instance, a combination of increased jitter, reduced throughput, and QoS flow inactivity may collectively indicate a deeper transport layer or radio issue affecting user-plane quality.

[0138] In an embodiment, the service disruption conditions may be categorized into data plane-related and control plane-related issues. The user-plane disruption conditions may include, but are not limited to, an elevated packet loss rate exceeding a predefined threshold over a time window; a persistent increase in the RTT beyond acceptable latency limits for latency-sensitive services (e.g., IMS voice or emergency calls); a significant drop in the uplink or downlink throughput below a minimum service-level requirement; an inactive or failed QoS flow statusdue to missing or invalid QFI mappings; a disruption in session continuity, such as an unexpected interruption or termination of the active protocol data unit (PDU) session or failure to resume a suspended session; an excessive packet delay variation (jitter) that may degrade the quality of real-time communication; or multiple occurrences of packet discard events.

[0139] In an embodiment, the control-plane disruption conditions may be inferred from the inability to establish or maintain signaling bearers, repeated failures or rejections during non-access stratum (NAS) procedures such as unsuccessful IMS registration, unsuccessful PDU session establishment / modification, or repeated authentication failures.

[0140] The disruption detection unit (312) is configured to detect the disruption condition associated with the first radio access node (202) at the UE (104) when the monitored data flow parameters deviate from a predefined threshold for a configurable duration of time. In certain embodiments, a threshold-based deviation may include a variety of comparison schemes to accurately capture transient as well as persistent degradations in a service performance. In one embodiment, the deviation includes a value of the corresponding monitored data flow parameters exceeding a predefined upper threshold value. For example, the packet loss rate exceeding an upper threshold value of 5% over a defined observation period may be indicative of data plane degradation. In another embodiment, the deviation includes the value of the monitored data flow parameters falling below a predefined lower threshold value. For instance, an uplink throughput value dropping below the lower threshold value of 100 kbps for a minimum duration may be considered a disruption trigger for latency-sensitive services such as the IMS voice.

[0141] In yet another embodiment, the deviation is based on the value of the monitored data flow parameters falling outside a predefined acceptable threshold range. For example, if the packet delay variation (jitter) falls outside the acceptable threshold range, such as between 5 milliseconds (ms) and 30 ms, the service disruption may be inferred. In another embodiment, the deviation may include arelative deviation from a predefined nominal or baseline threshold value. For example, the RTT increasing by more than 50% compared to a historical average or baseline threshold may be used to detect service degradation.

[0142] In some embodiments, the predefined thresholds may be statically configured by the network (108) or dynamically adjusted based on real-time network conditions, UE-specific context, service type, or associated QoS profiles. The configurable duration of time refers to a minimum observation window or time period over which the deviation must persist in order to be classified as a valid service disruption condition, thereby reducing false positives caused by transient fluctuations. For example, if the packet discard count crosses a defined limit within a continuous 3 -second interval, it may indicate a transient congestion event; however, if the condition persists beyond a defined 5-second threshold, a fallback decision may be triggered.

[0143] Further, the disruption detection unit (312) is configured to detect the service disruption condition associated with the first radio access node (202) at the core network function by analyzing historical data patterns associated with the first radio access node (202). The core network function may include, for example, a network analytics function (NAF), an operations support system (OSS), a network data analytics function (NWDAF), a user plane function (UPF), and so forth.

[0144] In an embodiment, the historical data patterns may be obtained from a network data repository (e.g., NWDAF storage or OSS logs) or generated dynamically through continuous logging, aggregation and averaging of the monitored data flow parameters over configurable time intervals (e.g., 5-minute, hourly, or daily snapshots). The disruption detection unit (312) may be configured to compare the real-time values of the data flow parameters with the historical data patterns for identifying abnormal deviations, trends, or anomalies that are indicative of potential service disruption conditions. This comparison may include evaluating whether the values of the data flow parameters (e.g., downlink throughput, latency, jitter, or packet loss) deviate from long-term averages, expected value ranges, orbaseline behavioral models of the first radio access node (202). In one embodiment, this comparison includes detecting sudden spikes (e.g., packet loss rate exceeding 5%), prolonged drops (e.g., sustained 40% reduction in throughput), or irregular fluctuations in metrics (e.g., excessive variation in jitter) that diverge from a historical stability profile. In another embodiment, the disruption detection unit (312) applies statistical measures, such as moving averages, variance calculations, or confidence intervals, to identify whether real-time measurements of the data flow parameters exceed predetermined confidence bounds derived from the historical data patterns. In yet another embodiment, machine learning-based anomaly detection models may be employed to predict an expected behavior of the data flow parameters, and any deviation from these predictions is flagged as a potential service disruption.

[0145] Upon detecting the service disruption condition, the core network function generates an indication of the service disruption condition. The indication may include information about the type of deviation, affected data flow parameters, time of detection, identity of an impacted radio access node, and so forth. The core network function transmits the indication of the service disruption condition to the EMS (210) using a standardized northbound interface, such as, but not limited to, a network configuration protocol (NETCONF), a Representational State Transfer (RESTful) network configuration protocol (RESTCONF), a simple network management protocol (SNMP), a vendor-specific application programming interface (API), and so forth.

[0146] The disruption detection unit (312) is configured to detect the service disruption condition at the radio access node by identifying one or more anomalies at the radio access node in the monitored data flow parameters. These anomalies may represent a localized issue at the radio access node, which may arise due to multiple root causes, such as, but not limited to, internal software malfunctions, scheduling failures, abnormal behavior at one or more radio protocol layers, and so forth.

[0147] In one embodiment, the service disruption condition is detected when the radio access node encounters the internal software malfunction that disrupts the handling of user-plane data. The internal software malfunction manifests as abnormal variations in the monitored data flow parameters, such as a noticeable rise in the packet drop rate, persistently low uplink or downlink throughput during active sessions, or repeated failures in establishing or maintaining data bearers.

[0148] In another embodiment, the service disruption condition is detected when the radio access node fails to schedule radio resources effectively for the attached UEs (104). Such failures may result from a malfunctioning scheduler module or imbalances in time-frequency resource allocation. In this case, the monitored parameters, such as scheduling delays, transmission gap durations, and UE grant request denial ratios, deviate significantly from expected baselines. These deviations result in degraded throughput and increased latency, which the disruption detection unit (312) interprets as indicators of the service disruption condition.

[0149] In yet another embodiment, the service disruption condition may arise from the anomalies at specific radio protocol layers (e.g., a packet data convergence protocol (PDCP), a radio link control (RLC), a medium access control (MAC)) or due to misconfigured radio parameters (e.g., modulation and coding scheme (MCS), block error rate (BLER), or allocated maximum bit rate (AMBR)). For example, a PDCP buffer overflow or reordering delay may result in increased jitter and packet delay variation; a high RLC retransmission rate or segmentation failure may cause reduced effective throughput; an elevated BLER due to aggressive MCS selection may result in excessive retransmissions, leading to high latency and packet loss; or incorrect AMBR settings may artificially throttle data rates, keeping throughput below expected thresholds. Each of these conditions, when detected through the monitored data flow parameters, is treated as the service disruption condition.

[0150] The transition control unit (314) is configured to initiate, in response to the at least one detected service disruption condition, the fallback of the UE (104) from the first radio access node (202) to the second radio access node (203). For example, in a 5G network, the UE (104) may remain attached to a first radio access node (202) that continues to broadcast coverage even though its user-plane path has failed, preventing data sessions from being established. Upon detecting this service disruption condition, the transition control unit (314) triggers the fallback by instructing the UE (104) to reselect to a second radio access node (203), such as a 4G eNodeB, where normal data services are available. As a result, the user’s service is restored automatically without requiring any manual intervention, such as toggling airplane mode or changing network preferences.

[0151] In an embodiment, the fallback of the UE (104) from the first radio access node (202) to the second radio access node (203) is triggered at the core network function by instructing the EMS (210) to change an operational status of the first radio access node (202) to an inhibited mode, which alters the behavior of the first radio access node (202) and compels the UE (104) to fallback. The inhibited mode refers to a system state or operational mode in which specific network actions, procedures, or transitions are temporarily disabled or restricted. This mode may be triggered due to network policy, failure detection, or ongoing recovery procedures to prevent unintended behavior.

[0152] In an embodiment, the core network function autonomously initiates a fallback process upon detecting the service disruption condition, without requiring manual operator intervention. The core network function communicates with the EMS (210) to issue an inhibition command, which changes the operational status of the first radio access node (202). For example, the EMS (210) may modify an operational state parameter from “in-service” to “out-of-service” or “restricted,” resulting in the first radio access node (202) ceasing to accept new UE attachments or actively releasing connected UEs (104). This state change compels the UEs (104) to perform cell reselection or handover to the second radio access node (203), thereby restoring service continuity.

[0153] In some embodiments, the EMS (210) may execute the operational status change using network management protocols, such as, but not limited to, the NETCONF, RESTCONF, or SNMP, or through vendor-specific APIs. In an embodiment, the process may also involve coordination with the NAF or the NWDAF to confirm that the observed disruption condition persists before executing the fallback. This automated, closed-loop mechanism ensures rapid service recovery and minimizes a mean time to recovery (MTTR) for impacted UEs.

[0154] The fallback of the UE (104) from the first radio access node (202) to the second radio access node (203) is triggered at the radio access node by ceasing the broadcast of the SIBs from the first radio access node (202). In an embodiment, the SIBs are periodically transmitted by the radio access node to provide essential configuration parameters and access-related information required by the UE (104) to initiate or maintain a radio connection. By ceasing the broadcast of the SIBs, such as SIB1 (which carries cell access parameters) or SIB2 (which provides radio resource configuration), the first radio access node (202) becomes inaccessible to the UEs (104) attempting to establish or sustain a connection.

[0155] This targeted suppression of SIB transmission causes the UE (104) to interpret the first radio access node (202) as unavailable or barred, thereby prompting the UE (104) to initiate a cell reselection or establish a radio resource control (RRC) connection with the second radio access node (203). In some embodiments, the cessation of the SIBs transmission may be implemented dynamically by altering a transmission schedule of the SIBs, muting their associated physical channels (e.g., a physical broadcast channel (PBCH), a physical downlink shared channel (PDSCH)), or reconfiguring broadcast parameters through a control plane software of the radio access node. This approach enables a controlled fallback mechanism in response to localized service degradation events while avoiding the need to completely shut down the first radio access node (202), thereby allowing unaffected UEs or other services to continue functioning normally.

[0156] The fallback of the at least one UE (104) from the first radio access node (202) to the second radio access node (203) is triggered at the UE (104) by initiating a reselection procedure even when the UE (104) is configured with a preference for the first network (108A). In an embodiment, the UEs (104) are configured with a set of mobility preferences, such as absolute priority lists, reselection thresholds, and hysteresis values that guide their decision to remain connected to a preferred serving cell or technology for as long as service quality remains acceptable.

[0157] In an embodiment, when the UE (104) detects a significant degradation in the service quality associated with the first radio access node (202), based on the monitored parameters such as the packet loss, throughput reduction, deterioration of RSRP / RSRQ, or increased delay variation, the UE (104) is configured to autonomously override a preconfigured network selection preferences for the higher-generation network. Instead, it initiates a fallback reselection process targeting the lower-generation network, even if the higher-generation network remains nominally available. The fallback reselection process is governed by measurement reports and internal quality evaluation algorithms implemented within the UE’s mobility management logic.

[0158] For instance, the UE (104) may initiate the reselection based on one or more service unavailability triggers, including but not limited to persistent radio link failures; repeated connection setup failures; unavailability of critical system information; detection of Layer 3 signaling failures; quality-of-service (QoS) unfulfillment, and so forth. In some embodiments, the UE (104) may employ timerbased logic, whereby a fallback decision is triggered if the identified degradation persists beyond a predefined threshold duration.

[0159] In such scenarios, even when the first radio access node (202) remains nominally preferred (e.g., a higher-generation network such as 5G), the UE (104) determines that service continuity or quality of experience is better achievable through the second radio access node (203), corresponding to a lower-generationnetwork (e.g., 4G), and executes the reselection procedure accordingly. The UE (104) effectively overrides the “higher generation network preferred” configuration to ensure uninterrupted connectivity and service availability. This autonomous fallback mechanism ensures that the user experience is preserved even in the presence of localized node-level issues or silent degradations, by handing over the UE (104) to the second network (108B) despite the availability of the first network (108A).

[0160] FIG. 4 illustrates an exemplary flowchart of a method (400) for managing the fallback of the UE (104) in the network (108), in accordance with embodiments of the present disclosure. FIG. 4, with reference to FIG. 1, FIG. 2 and FIG. 3, illustrates the method (400) for managing the fallback of the UE (104) by using the processing engine (308) of the system (102).

[0161] At step (402), the method (400) includes monitoring, by the fallback decision unit (310), the data flow parameters indicative of service unavailability over the first radio access node (202) operating within the first network (108 A). The first network (108A) is the fifth generation (5G) network. The service unavailability may result from impairments in either or both of the data plane (208) and the control plane (206). In the case of data plane impairment, the data flow parameters may be, but not limited to, the packet loss rate, the downlink or uplink throughput, the latency or round-trip time (RTT), the packet discard count, the quality of service (QoS) flow status (e.g., inactive or failed QoS flow identifier (QFI) mappings), the session continuity failure (e.g., interruption of an active packet data unit (PDU) session), the packet delay variation (jitter), and so forth. In an embodiment, in the case of control plane impairments, the control-plane specific data flow parameters may be, but not limited to, inability of the UE (104) to register with the IMS, failure to establish or maintain signaling connections, unavailability of signaling bearers, rejection messages from core network functions during session or service setup, failures in executing or completing non-access stratum (NAS) procedures, and so forth.

[0162] At step (404), the method (400) includes detecting, by the disruption detection unit (312), at least one service disruption condition associated with the first radio access node (202) based on the monitored data flow parameters. In an embodiment, the service disruption condition associated with the first radio access node (202) is detected at the UE (104) when the monitored data flow parameters deviate from the predefined threshold for the configurable duration of time. In another embodiment, the service disruption condition associated with the first radio access node (202) is detected at the core network function by analyzing the historical data patterns associated with the first radio access node (202). In such embodiment, the core network function transmits an indication of the service disruption condition to the EMS (210) when the deviation is identified between the historical data patterns and the monitored data flow parameters. In yet another embodiment, the service disruption condition is detected at the radio access node by identifying the anomalies at the radio access node. The anomalies include at least one of internal software malfunctions, scheduling failures, and abnormal behavior at one or more radio protocol layers.

[0163] At step (406), the method (400) includes initiating, by the transition control unit (314), in response to the at least one detected service disruption condition, the fallback of at least one UE (104) from the first radio access node (202) to the second radio access node (203) operating within the second network (108B). The second network (108B) is a fourth generation (4G) network. In an embodiment, the fallback of the at least one UE (104) from the first radio access node (202) to the second radio access node (203) is triggered at the core network function by changing, through the EMS (210), an operational status of the first radio access node (202) that causes the at least one UE (104) to reselect to the second radio access node (203). In another embodiment, the fallback of the at least one UE (104) from the first radio access node (202) to the second radio access node (203) is triggered at the radio access node by ceasing the broadcast of the SIBs from the first radio access node (202).

[0164] In yet another embodiment, the fallback of the at least one UE (104) from the first radio access node (202) to the second radio access node (203) is triggered at the UE (104) by initiating the reselection procedure even when the UE (104) is configured with the preference for the first network (108A). The fallback of the at least one UE (104) from the first radio access node (202) to the second radio access node (203) is initiated despite an availability of the first network (108A) at the UE (104).

[0165] FIG. 5 illustrates an exemplary computer system (500) in which, or with which, the system (102) and the method (400) of the present disclosure may be implemented. As shown in FIG. 5, the computer system (500) may include an external storage device (510), a bus (520), a main memory (530), a read-only memory (540), a mass storage device (550), a communication port (560), and a processor (570). A person skilled in the art will appreciate that the computer system (500) may include more than one processor (570) and the communication ports (560). The processor (570) may include various modules associated with embodiments of the present disclosure.

[0166] In an embodiment, the external storage device (510) may be any device that is commonly known in the art, such as, but not limited to, a memory card, a memory stick, a solid-state drive, a hard disk drive (HDD), and so forth.

[0167] In an embodiment, the bus (520) may be communicatively coupled with the processor(s) (570) with the other memory, storage, and communication blocks. The bus (520) may be, e.g., a peripheral component interconnect (PCI) / PCI Extended (PCI-X) bus, a small computer system interface (SCSI), a 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 (570) to the computer system (500).

[0168] In an embodiment, the main memory (530) may be a random-access memory (RAM), or any other dynamic storage device commonly known in the art. The Read-only memory (540) may be any static storage device(s) e.g., but notlimited 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 (570).

[0169] In an embodiment, the mass storage device (550) may be any current or future mass storage solution, which may be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, a parallel advanced technology attachment (PATA) or a 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 (e.g., SATA arrays).

[0170] Further, the communication port (560) 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 (560) may be chosen depending on the network (108), such a local area network (LAN), wide area network (WAN), or any network to which the computer system (500) connects.

[0171] Optionally, operator and administrative interfaces, e.g., a display, a keyboard, a joystick, and a cursor control device, may also be coupled to the bus (520) to support a direct operator interaction with the computer system (500). Other operator and administrative interfaces may be provided through network connections connected through the communication port (560). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (500) limit the scope of the present disclosure.

[0172] In an exemplary embodiment, a user equipment (UE) (104) for managing a fallback in a network is disclosed. The UE (104) is configured to monitor one or more data flow parameters indicative of service unavailability over the first radio access node (202) operating within a first network (108A). The UE(104) is further configured to detect at least one service disruption condition associated with the first radio access node (202) based on the one or more monitored data flow parameters. The UE (104) is further configured to initiate, in response to the at least one detected service disruption condition, the fallback of at least one UE (104) from the first radio access node (202) to a second radio access node (203) operating within a second network (108B).

[0173] In an exemplary embodiment, a computer program product including a non-transitory computer-readable medium including instructions that, when executed by one or more processors, cause the one or more processors to execute a method for managing a fallback of a user equipment (UE) in a network. The method includes monitoring, by a fallback decision unit, one or more data flow parameters indicative of service unavailability over a first radio access node operating within a first network. The method further includes detecting, by a disruption detection unit, at least one service disruption condition associated with the first radio access node based on the one or more monitored data flow parameters. The method further includes initiating, by a transition control unit, in response to the at least one detected service disruption condition, the fallback of at least one UE from the first radio access node to a second radio access node operating within a second network.

[0174] The present disclosure provides a technical advancement in the field of 5G radio access and mobility management by addressing limitations of existing solutions related to prolonged service outages experienced by user equipment (UE) when connected to or associated with partially available or degraded 5G cells. This advancement is achieved through a UE- or network-initiated fallback mechanism that monitors data flow parameters and detects service disruption conditions based on configurable thresholds and timers. The inventive aspects include intelligent decision logic implemented across UE, RAN, or core entities, enabling temporary override of UE radio access technology (RAT) preferences to trigger fallback to a lower generation RAT (e.g., from 5G to 4G) while ensuring automatic reselection back to the preferred RAT upon service restoration. By incorporating dynamic monitoring, disruption detection, and controlled fallback initiation, the disclosedsolution improves service continuity, minimizes end-user impact during outages, and enhances the overall resilience and responsiveness of a mobile communication system.

[0175] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.TECHNICAL ADVANTAGES OF THE PRESENT DISCLOSURE

[0176] As is evident from above, the present disclosure described herein above has several technical advantages including:• enhancing user experience by enabling automatic fallback from a higher generation radio network (e.g., 5G) to a lower generation radio network (e.g., 4G), thereby restoring services without requiring manual user intervention.• improving service continuity during partial radio network failures where a control plane remains available but a data plane is impaired, by initiating fallback procedures at a device, network, or core level.• reducing mean time to recovery (MTTR) in scenarios where a user device remains connected on a non -functional 5G cell with persistent service outages, through autonomous decision-making based on configurable service unavailability timers.• enhancing network resilience by utilizing core network intelligence (e.g., gateway detection of abnormal traffic patterns) to proactively trigger fallback via EMS coordination with an impacted radio node.minimizing large-scale user impact through broadcast inhibition strategies initiated by a network in case of catastrophic or unrecoverable radio node failures, enabling mass fallback to functioning lower RATs.• preserving device configuration preferences (e.g., “5G preferred”) while allowing temporary override only under abnormal service-impacting conditions, ensuring the device returns to preferred settings once service is restored.

Claims

1. CLAIMS1. A method (400) for managing a fallback of a user equipment (UE) (104) in a network, the method (400) comprising: monitoring, by a fallback decision unit (310), one or more data flow parameters indicative of service unavailability over a first radio access node(202) operating within a first network (108 A); detecting, by a disruption detection unit (312), at least one service disruption condition associated with the first radio access node (202) based on the one or more monitored data flow parameters; and initiating, by a transition control unit (314), in response to the at least one detected service disruption condition, the fallback of at least one UE (104) from the first radio access node (202) to a second radio access node(203) operating within a second network (108B).

2. The method (400) as claimed in claim 1, wherein each of the fallback decision unit (310), the disruption detection unit (312), and the transition control unit (314) is implemented at one of the UE (104), a radio access node, or a core network function.

3. The method (400) as claimed in claim 2, wherein the service disruption condition associated with the first radio access node (202) is detected at the UE (104) when the one or more monitored data flow parameters deviate from a predefined threshold for a configurable duration of time.

4. The method (400) as claimed in claim 2, wherein the service disruption condition associated with the first radio access node (202) is detected at the core network function by analyzing historical data patterns associated with the first radio access node (202).

5. The method (400) as claimed in claim 4, comprising transmitting, by the core network function, an indication of the service disruption condition to an element management system (EMS) (210) when a deviation is identified between the historical data patterns and the one or more monitored data flow parameters.

6. The method (400) as claimed in claim 2, wherein the service disruption condition is detected at the radio access node by identifying one or more anomalies at the radio access node, wherein the one or more anomalies comprise at least one of internal software malfunctions, scheduling failures, and abnormal behavior at one or more radio protocol layers.

7. The method (400) as claimed in claim 2, wherein the fallback of the at least one UE (104) from the first radio access node (202) to the second radio access node (203) is triggered at the core network function by changing, through the EMS (210), an operational status of the first radio access node (202) that causes the at least one UE (104) to reselect to the second radio access node (203).

8. The method (400) as claimed in claim 2, wherein the fallback of the at least one UE (104) from the first radio access node (202) to the second radio access node (203) is triggered at the radio access node by ceasing a broadcast of one or more system information blocks (SIBs) from the first radio access node (202).

9. The method (400) as claimed in claim 2, wherein the fallback of the at least one UE (104) from the first radio access node (202) to the second radio access node (203) is triggered at the UE (104) by initiating a reselection procedure even when the UE (104) is configured with a preference for the first network (108A).

10. The method (400) as claimed in claim 1, wherein the first network (108 A) is a fifth generation (5G) network and the second network (108B) is a fourth generation (4G) network.

11. The method (400) as claimed in claim 1, wherein the fallback of the at least one UE (104) from the first radio access node (202) to the second radio access node (203) is initiated despite an availability of the first network ( 108 A) at the UE (104).

12. A system (102) for managing a fallback of a user equipment (UE) (104) in a network (108), the system (102) comprising: a fallback decision unit (310) configured to monitor one or more data flow parameters indicative of service unavailability over a first radio access node (202) operating within a first network (108 A); a disruption detection unit (312) configured to detect at least one service disruption condition associated with the first radio access node (202) based on the one or more monitored data flow parameters; and a transition control unit (314) configured to initiate, in response to the at least one detected service disruption condition, the fallback of at least one UE (104) from the first radio access node (202) to a second radio access node (203) operating within a second network (108B).

13. The system (102) as claimed in claim 12, wherein each of the fallback decision unit (310), the disruption detection unit (312), and the transition control unit (314) is implemented at one of the UE (104), a radio access node, or a core network function.

14. The system (102) as claimed in claim 13, wherein the service disruption condition associated with the first radio access node (202) is detected at the UE (104) when the one or more monitored data flow parameters deviate from a predefined threshold for a configurable duration of time.

15. The system (102) as claimed in claim 13, wherein the service disruption condition associated with the first radio access node (202) is detected at the core network function by analyzing historical data patterns associated with the first radio access node (202).

16. The system (102) as claimed in claim 15, wherein the disruption detection unit (312) is further configured to transmit, by the core network function, an indication of the service disruption condition to an element management system (EMS) (210) when a deviation is identified between the historical data patterns and the one or more monitored data flow parameters.

17. The system (102) as claimed in claim 13, wherein the service disruption condition is detected at the radio access node by identifying one or more anomalies at the radio access node, wherein the one or more anomalies comprise at least one of internal software malfunctions, scheduling failures, and abnormal behavior at one or more radio protocol layers.

18. The system (102) as claimed in claim 13, wherein the fallback of the at least one UE (104) from the first radio access node (202) to the second radio access node (203) is triggered at the core network function by changing, through the EMS (210), an operational status of the first radio access node (202) that causes the at least one UE (104) to reselect to the second radio access node (203).

19. The system (102) as claimed in claim 13, wherein the fallback of the at least one UE (104) from the first radio access node (202) to the second radio access node (203) is triggered at the radio access node by ceasing a broadcast of one or more system information blocks (SIBs) from the first radio access node (202).

20. The system (102) as claimed in claim 13, wherein the fallback of the at least one UE (104) from the first radio access node (202) to the second radio access node (203) is triggered at the UE (104) by initiating a reselection procedure even when the UE (104) is configured with a preference for the first network (108A).

21. The system (102) as claimed in claim 12, wherein the first network (108A) is a fifth generation (5G) network and the second network (108B) is a fourth generation (4G) network.

22. The system (102) as claimed in claim 12, wherein the fallback of the at least one UE (104) from the first radio access node (202) to the second radio access node (203) is initiated despite an availability of the first network ( 108 A) at the UE (104).

23. A user equipment (UE) (104) for managing a fallback in a network (108), wherein the UE (104) is configured to: monitor one or more data flow parameters indicative of service unavailability over the first radio access node (202) operating within a first network (108 A); detect at least one service disruption condition associated with the first radio access node (202) based on the one or more monitored data flow parameters; and initiate, in response to the at least one detected service disruption condition, the fallback of at least one UE (104) from the first radio access node (202) to a second radio access node (203) operating within a second network (108B).

24. The UE (104) as claimed in claim 23, wherein the service disruption condition associated with the first radio access node (202) is detected at theUE (104) when the one or more monitored data flow parameters deviate from a predefined threshold for a configurable duration of time.

25. The UE (104) as claimed in claim 23, wherein the fallback of the at least one UE (104) from the first radio access node (202) to the second radio access node (203) is triggered at the UE (104) by initiating a reselection procedure even when the UE (104) is configured with a preference for the first network (108A).

26. The UE (104) as claimed in claim 23, wherein the first network (108A) is a fifth generation (5G) network and the second network (108B) is a fourth generation (4G) network.

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 execute a method (400) for managing a fallback of a user equipment (UE) (104) in a network (108), the method (400) comprising steps of: monitoring, by a fallback decision unit (310), one or more data flow parameters indicative of service unavailability over a first radio access node(202) operating within a first network (108 A); detecting, by a disruption detection unit (312), at least one service disruption condition associated with the first radio access node (202) based on the one or more monitored data flow parameters; and initiating, by a transition control unit (314), in response to the at least one detected service disruption condition, the fallback of at least one UE (104) from the first radio access node (202) to a second radio access node(203) operating within a second network (108B).

Images