Method and system for managing a transition operation in a network

Abstract

The disclosure relates to a method (500) and system (108) for managing a transition operation in a network (106). The method (500) involves receiving (502), by a receiving unit (212), a request to initiate a transition operation, which includes either a shutdown operation or a switchover operation. Upon receiving the request, a list comprising a set of commands associated with the transition operation is transferred (504) to a processing engine (208). The processing engine (208) categorizes (506) the set of commands into a first set comprising one or more asynchronized commands and a second set comprising one or more synchronized commands, based on predefined criteria. The processing engine (208) then performs (508) a first set of operations to execute the first set of commands and a second set of operations to execute the second set of commands, thereby managing the transition operation in the network (106).

Description

METHOD AND SYSTEM FOR MANAGING A TRANSITION OPERATION IN A NETWORKRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD

[0002] The present disclosure relates to a telecommunications network. In particular, the present disclosure relates to a method and a system for managing a transition operation in a network.DEFINITIONS

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

[0004] The term ‘Network Function (NF)’ used hereinafter in the specification refers to a virtualized or physical entity that provides specific network services such as routing, firewalling, load balancing, or session management within a telecommunications system. An NF may be implemented in software or hardware and is a fundamental building block in modern network architectures, including cloudnative and virtualized environments.

[0005] The term ‘Cluster Mode’ used hereinafter in the specification refers to a deployment configuration of Network Functions (NFs) in which multiple instances are distributed across different nodes. This configuration includes one or more backup instances that can assume the workload of an active instance in the event of a failure, thereby enabling failover capabilities and high availability.

[0006] The term ‘Standalone Mode’ used hereinafter in the specification refers to a deployment configuration of a Network Function (NF) where a single instance operates independently without any associated backup or redundant nodes. In this mode, a failure in the NF typically results in a complete interruption of the network service provided by that instance.

[0007] The term ‘Shutdown’ used hereinafter in the specification refers to the process in which a Network Function (NF) or its host server is intentionally or unintentionally terminated. This may occur due to planned maintenance, system commands, failures, or crashes, and typically results in the cessation of all processes associated with the NF.

[0008] The term ‘Switchover’ used hereinafter in the specification refers to the transition of traffic or workload from an active Network Function (NF) instance to a backup or secondary instance. This process may be initiated manually by an operator or automatically by the system in response to faults, degradation, or shutdown events affecting the active instance.

[0009] The term ‘Failover’ used hereinafter in the specification refers to the process of switching from a failed or faulty active instance of a Network Function (NF) to a backup instance. Failover may be initiated manually by an operator or automatically by the system when a fault is detected.

[0010] The term ‘Automatic Switchover’ used hereinafter in the specification refers to a type of failover in which the transition from an active instance to a backupinstance of a Network Function (NF) occurs without human intervention, typically triggered by monitoring systems or predefined fault-detection logic.

[0011] The term ‘Abrupt Shutdown’ used hereinafter in the specification refers to an unplanned and immediate termination or failure of a Network Function (NF) instance, typically caused by hardware faults, software errors, or automatic switchover events that do not allow for graceful termination or state preservation.

[0012] The term ‘Backup Node’ used hereinafter in the specification refers to a secondary instance or environment configured to take over the responsibilities of an active Network Function (NF) instance in the event of a failure or switchover.

[0013] The term ‘Asynchronized Commands’ used hereinafter in the specification refers to the set of commands that are resource-intensive and take a relatively longer time to execute. These commands are not required to complete before proceeding with the transition operation and may continue execution in the background while other essential tasks are performed concurrently. Examples may include commands like jmap or jstack, which require substantial processing time and system resources.

[0014] The term ‘Synchronized Commands’ used hereinafter in the specification refers to the set of commands that are lightweight and execute quickly, consuming minimal system resources. These commands are executed and completed before the transition operation is carried out, ensuring essential data is captured without significant delay. Examples may include commands like netstat or free -g.

[0015] These definitions are in addition to those expressed in the art.BACKGROUND

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

[0017] Network Functions (NFs) are foundational components in modern telecommunications infrastructure, responsible for providing essential services such as routing, traffic management, and network security. Depending on the specific requirements of the network architecture, NFs can be deployed in either cluster mode or standalone mode.

[0018] In cluster mode, NFs operate across multiple nodes with the inclusion of backup nodes to support failure scenarios. When a fault occurs in an active application running on one of the nodes, traffic can be redirected to one of the available backup instances. This redirection may be triggered either manually, through operator intervention, or automatically, based on predefined system logic.

[0019] In standalone mode, an NF runs as a single, isolated instance without any redundancy. In this configuration, a failure in the NF typically results in a complete service outage, as there is no secondary instance to continue processing traffic or requests. While the standalone mode may be simpler in terms of deployment and resource requirements, it also introduces a higher degree of risk due to the absence of failover support.

[0020] A significant challenge arises during automatic and abrupt shutdowns or switchovers, particularly in cluster mode. When a failure in the active NF instance leads to an immediate transition to a backup node, critical runtime and diagnostic data from the original NF instance may be lost. The system often does not preserveoperational context such as active network connections, the ports to which the application was listening, thread states, memory usage statistics, system load, and the names or statuses of other processes running within the same environment. Additionally, internal metrics such as the sizes of request queues may also be lost. The absence of this data makes it difficult to perform effective debugging and root cause analysis.

[0021] This issue is not confined to cluster deployments. In standalone configurations, where no backup node is available to assume control, a failure results in both service interruption and a lack of operational visibility unless external logging or monitoring systems are employed. In either mode, the inability to retain or access runtime diagnostic information during failure events creates substantial challenges in analyzing faults and identifying their causes. The resulting delay in troubleshooting can increase system downtime and may allow recurring issues to persist undetected.

[0022] Therefore, there is a need for a system and a method that overcomes the limitations of the prior art.OBJECTIVES OF THE DISCLOSURE

[0023] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:

[0024] An objective of the present disclosure is to provide a method and a system for managing a shutdown operation or a switchover operation associated with a network function (NF) in a network.

[0025] An objective of the present disclosure is to provide a method and a system for capturing and storing critical setup information, including data related to the Network Function (NF) and its underlying server environment, at the time of shutdown or switchover.

[0026] Another objective of the present disclosure is to prevent or handle failure scenarios where operational or performance-related information becomes unavailable to the user at the time of shutdown or switchover of the NF.

[0027] Another objective of the present disclosure is to collect performance- related information of the NF during shutdown or switchover events. The performance- related information includes, but is not limited to, local data maps, request queue sizes, active network connections, number of maintained sessions, memory usage, thread states, system load, ports in use, and a list of peer applications to which the NF is connected.

[0028] Another objective of the present disclosure is to capture such performance-related information by executing one or more predefined system-level commands and storing the output of these commands in text-based or structured files according to the configured settings.

[0029] Another objective of the present disclosure is to enable the quick capture of command outputs and in-memory cached data immediately after shutdown or switchover, thus preserving runtime context necessary for troubleshooting.

[0030] Another objective of the present disclosure is to reduce the time and effort required for debugging by consolidating critical diagnostic and performance data in a single location, making it easily accessible for root cause analysis.

[0031] Another objective of the present disclosure is to provide the capability to execute and record multiple commands, allowing users to retrieve outputs from different system tools or application-level methods in one place.

[0032] Another objective of the present disclosure is to utilize the stored information and command outputs to analyze and determine the root cause of a failureor abnormal behavior in the NF, thereby aiding in post-failure investigation and system recovery.

[0033] 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

[0034] In an exemplary embodiment, a method for managing a transition operation in a network is described. The method comprising receiving, by a receiving unit, a request for initiating a transition operation associated with a network function (NF). The transition operation comprises either a shutdown operation or a switchover operation. The method comprising transferring, by the receiving unit, a list comprising a set of commands associated with the initiated transition operation towards a processing engine. The method comprising categorizing, by the processing engine, the set of commands as a first set of commands or as a second set of commands based on a predefined criteria. The first set of commands comprising one or more asynchronized commands and the second set of commands comprising one or more synchronized commands. The method comprising performing, by the processing engine, a first set of operations for executing the first set of commands and a second set of operations for executing the second set of commands to manage the transition operation in the network.

[0035] In an embodiment, the predefined criteria comprising comparing, by the processing engine, an execution time period of each command from the set of commands in the transferred list with a threshold time period associated with the transition operation.

[0036] In an embodiment, each command having the execution time period more than the threshold time period is categorized under the first set of commands andeach command having the execution time period less than the threshold time period is categorized under the second set of commands.

[0037] In an embodiment, the threshold time period is a user-defined timer value indicating a permissible duration for performing the transition operation associated with the NF.

[0038] In an embodiment, the first set of operations for executing the first set of commands comprising scheduling, by the processing engine, the execution of each command from the first set of commands. Storing, by the processing engine, generated output results in a database after completion of the execution.

[0039] In an embodiment, the second set of operations for executing the second set of commands comprising scheduling, by the processing engine, the execution of each command from the second set of commands in parallel with the execution of the first set of commands. Waiting, by the processing engine, completion of the execution of each command from the second set of commands. Storing, by the processing engine, generated output results in the database after completion of the execution. Performing the transition operation in the network after completion of the execution.

[0040] In an exemplary embodiment, a system for managing a transition operation in a network is disclosed. The system comprising a receiving unit configured to receive a request for initiating a transition operation associated with a network function (NF). The transition operation comprises either a shutdown operation or a switchover operation. The receiving unit configured to transfer a list comprising a set of commands associated with the initiated transition operation towards a processing engine. The processing engine is configured to categorize the set of commands as a first set of commands or as a second set of commands based on a predefined criteria. The first set of commands comprising one or more asynchronized commands and the second set of commands comprising one or more synchronized commands. Theprocessing engine is configured to perform a first set of operations for executing the first set of commands and a second set of operations for executing the second set of commands to manage the transition operation in the network.

[0041] In yet another exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for managing a transition operation in a network is described. The method comprising receiving, by a receiving unit, a request for initiating a transition operation associated with a network function (NF). The transition operation comprises either a shutdown operation or a switchover operation. The method comprising transferring, by the receiving unit, a list comprising a set of commands associated with the initiated transition operation towards a processing engine. The method comprising categorizing, by the processing engine, the set of commands as a first set of commands or as a second set of commands based on a predefined criteria. The first set of commands comprising one or more asynchronized commands and the second set of commands comprising one or more synchronized commands. The method comprising performing, by the processing engine, a first set of operations for executing the first set of commands and a second set of operations for executing the second set of commands to manage the transition operation in the network.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

[0042] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagramsand may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0043] FIG. 1 illustrates an exemplary network architecture including a system configured managing a transition operation in a network, in accordance with an embodiment of the present disclosure.

[0044] FIG. 2 illustrates an exemplary block diagram of the system configured for managing the transition operation in the network, in accordance with an embodiment of the disclosure.

[0045] FIG. 3 illustrates an exemplary flow chart of a method for managing the transition operation in the network, in accordance with an embodiment of the disclosure.

[0046] FIG. 4 illustrates an exemplary system architecture for managing the transition operation in the network, in accordance with an embodiment of the disclosure.

[0047] FIG. 5 another exemplary flow chart of the method for managing the transition operation in the network, in accordance with an embodiment of the disclosure.

[0048] FIG. 6 illustrates an exemplary computer system in which or with which the embodiments of the present disclosure may be implemented.

[0049] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102 - User(s)104 -User Equipments (UEs)106 - Network 108 - System200 - Block Diagram202 - Processor(s)204 - Memory206 -Interface(s) 208 - Processing Engine210 - Database212 - Receiving Unit300, 500 - Flow Diagram400 - System architecture 402 - Network Function404 - Transition Application600 - Computer System610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port670 - ProcessorDETAILED DESCRIPTION

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

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

[0052] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of the ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

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

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

[0055] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

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

[0057] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that manyembodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment, as well as other embodiments of the disclosure, will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.

[0058] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog, offering only voice services. Further, text messaging and data services became possible when the second-generation (2G) technology was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Currently, fifth generation (5G) technology is being deployed, offering significantly faster data speeds, lower latency, and the ability to connect many devices simultaneously. Further, sixth generation (6G) successor to 5G is expected to provide significantly high data speed with reduced latency, which may offer improved connectivity for a vast number of devices concurrently. The capabilities of 6G enable new types of applications and services, such as advanced augmented reality (AR) and virtual reality (VR), holographic communications, and more immersive digital experiences. These advancements represent a significant leap forward from previous generations, enabling enhanced mobile broadband, improved Internet of Things (loT) connectivity, and more efficient use of network resources. The 6G technology promises to build upon these advancements, pushing the boundaries of wireless communication even further. While the 5G technology is still being rolled out globally, research and development into the 6G are rapidly progressing, with the aim of revolutionizing the way we connect and interact with technology.

[0059] Abrupt automatic shutdown operations or switchover operations of a Network Function (NF), which may occur due to faults, failures, or maintenance activities, often result in the loss of critical information such as the NF’s active connections, application ports in use, thread states, memory consumption, system load, and the statuses of other processes running within the Network Function environment. Important performance metrics like request queue sizes and other data essential for understanding NF behavior may also be lost.

[0060] A shutdown operation refers to the process of terminating the functioning of a NF or its components. This process can be either planned, allowing orderly resource release, state preservation, and minimal service disruption, or unplanned, causing abrupt cessation of activities without saving state. The requirements for a shutdown operation include freeing system resources, preserving Network Function state where possible, notifying relevant systems or administrators, generating detailed logs, and minimizing impact on ongoing services. Proper management of shutdown operations prevents data loss, supports maintenance, maintains system stability, and enables smooth restarts by preserving critical system state.

[0061] A switchover operation involves transferring the active workload of the NF from a primary instance to a standby or backup instance either manually or automatically. This is typically triggered to maintain service continuity during failures or planned maintenance. Key requirements for switchover operations include seamless traffic redirection, synchronization of state information between instances, reliable fault detection, minimal latency in the switch, and comprehensive logging. The benefits of effective switchover operations include enhanced high availability, fault tolerance, improved load balancing, operational flexibility, and overall system reliability.

[0062] The absence of critical information during shutdown or switchover operations significantly complicates the debugging process and makes it challengingY1 to identify the root cause of failures. Therefore, effective logging and monitoring systems are crucial to capture such data in real time, ensuring that sufficient information is retained even during abrupt transitions. Robust logging not only aids in post-failure analysis but also enhances overall system stability and reliability.

[0063] To address these challenges, the present disclosure provides a method and system that enable the application to effectively manage shutdown and switchover operations of a NF, preserving critical diagnostic and performance data during these events.

[0064] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0065] FIG. 1 illustrates an exemplary network architecture (100) including a system (108) configured managing a transition operation in a network (106), in accordance with an embodiment of the present disclosure.

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

[0067] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the UE (104) may include, but is not limited to, smart phones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the users (102) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE (104) may include, but is not limited to, intelligent, multisensing, network- connected devices, which 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.

[0068] In an embodiment, the UE (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device(e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the user equipment (104) may include, but is not limited to, any electrical, electronic, electro-mechanical, or an equipment, or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein the UE (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user(102) or the entity such as touch pad, touch enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the

[0069] In an embodiment, the network (106) may include at least one of a Fourth Generation (4G) network, 5G network, 6G network, or the like. The network (106) may enable the UE (104) to communicate with other devices in the network architecture (100) and / or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), an internet, an 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 another embodiment, the network (106) includes, 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.

[0070] Although FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture (100).

[0071] FIG. 2 illustrates an exemplary block diagram (200) of the system (108) configured for managing the transition operation in the network (106), in accordance with an embodiment of the disclosure. FIG. 2 is explained in conjunction with FIG. 1.

[0072] In an embodiment, the system (108) may include one or more processor(s) 202. The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as a Random-Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, and the like.

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

[0074] In an embodiment, the system (108) may include a processing engine (208) that may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine (208). In examples described herein, such combinations of hardwareand programming may be implemented in several diverse ways. For example, the programming for the processing engine (208) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine (208) may 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 (208). In such examples, the system (108) 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 (108) and the processing resource. In other examples, the processing engine (208) may be implemented by electronic circuitry.

[0075] In an embodiment, the system (108) may include a database (210) that includes data that may be either stored or generated as a result of functionalities implemented by any of the components of the processor (202) or the processing engine (208).

[0076] In one embodiment, the system (108) may be implemented as a network function (NF) and may be interchangeably referred to as an NF throughout the present disclosure. The NF refers to a virtualized or physical component within a network infrastructure that is responsible for performing specific tasks necessary for the delivery and management of network services. Examples of suchNFs may include, but are not limited to, a session border controller (SBC), which manages signaling and media streams for real-time communication sessions; a load balancer, which distributes network traffic across multiple servers to optimize resource utilization; a network address translation (NAT) function, which enables multiple devices on a local network to access external networks using a single public IP address and a domain name system(DNS) function, which translates human- readable domain names into machine- readable IP addresses.

[0077] These network functions are configured to perform well-defined roles that are essential to the efficient operation and reliability of telecommunications and data networks. The specific functions carried out by these NFs may include, but are not limited to, packet routing, network switching, traffic filtering and firewalling, load distribution, traffic prioritization, session handling, and other traffic management operations. Such capabilities enable the network to maintain service continuity, improve responsiveness, manage congestion, and ensure secure and optimized data flow across interconnected systems and services.

[0078] In an embodiment, the system (108) may include a receiving unit (212) configured for receiving a request for initiating a transition operation associated with the network function (NF). In an embodiment, the transition operation comprising either a shutdown operation or a switchover operation. When a shutdown or switchover operation is initiated at the NF, the system (108) will first automatically capture and dump critical performance-related information. This includes data such as local maps, request queue sizes, active connections established by the application, the number of sessions currently maintained, memory usage, and a list of peer applications to which the NF is connected. A shutdown operation refers to the controlled deactivation of a network function (NF), typically initiated for planned maintenance, upgrades, reconfiguration, or scaling down. The primary requirement for a shutdown operation is that it must be graceful, allowing the NF to complete or offload ongoing tasks, release system resources properly, and preserve critical operational or diagnostic information before termination. This may involve notifying peer applications, draining active sessions, closing network connections, and saving relevant runtime data. On the other hand, a switchover operation involves redirecting the NF’s traffic or workload to a backup or standby instance, typically in response to failure events, health checkviolations, or performance degradation. Switchover operations require the availability of a pre- configured secondary instance, synchronization of session or state data, and minimal disruption to service continuity. Both operations are essential for maintaining system reliability, scalability, and availability. The benefits of properly managing shutdown and switchover operations include reduced downtime, simplified debugging, minimal data loss, and greater operational resilience. Additionally, when combined with automated systems to capture performance-related information during these transitions, these operations contribute to faster root cause analysis and improved overall network stability.

[0079] In an embodiment, the request received by the receiving unit (212) may originate from various sources and may be triggered in different ways. In some scenarios, the request may be initiated manually by a network administrator through a command-line interface, graphical user interface, or via orchestration tools such as a network management system or controller. For example, an operator may manually issue a shutdown command to decommission or restart the NF during planned maintenance. In other scenarios, the request may be generated automatically by a monitoring or orchestration system in response to predefined conditions or failure events. For instance, if the NF fails a health check or exhibits degraded performance, an automatic switchover request may be triggered to shift the workload to a standby instance. The request may also be scheduled in advance as part of routine updates or configuration cycles. The receiving unit (212) is capable of interfacing with external systems or internal services over various communication mechanisms, including RESTful APIs, messaging queues, internal service buses, or configuration triggers. External systems refer to components outside the NF environment, such as network management systems, service orchestrators, cloud controllers, or monitoring platforms that initiate requests based on administrative actions or predefined policies. Internal services, on the other hand, are modules operating within or alongside the NF itself, such as embedded health check mechanisms, automation scripts, local schedulers, orruntime agents, which autonomously detect events or thresholds that require a transition. Upon receiving the request, the receiving unit (212) parses and validates the input parameters, such as the NF identifier and the type of transition operation, and subsequently initiates further actions by passing this information to the processing engine (208) for execution.

[0080] In an embodiment, the receiving unit (212) is configured for transferring a list comprising a set of commands associated with the initiated transition operation towards a processing engine (208). In an embodiment, the receiving unit (212) obtains the list comprising a set of commands associated with the initiated transition operation from internal storage such as pre-configured repositories, configuration files, or a command management system that is maintained within the NF environment or its management framework. These sources are typically located in secure memory modules, local databases, or configuration management servers that store predefined scripts and commands relevant to various transition operations. Upon receiving the request to initiate the transition, the receiving unit (212) accesses these stored commands and transfers the list to the processing engine (208) using internal communication protocols or application programming interfaces (APIs), ensuring accurate and efficient delivery for execution during the transition process.

[0081] In an embodiment, the processing engine (208) is configured to categorize the set of commands as a first set of commands or as a second set of commands based on a predefined criteria. In an embodiment, the first set of commands comprising one or more asynchronized commands and the second set of commands comprising one or more synchronized commands. Synchronized and asynchronized commands serve different purposes in managing network function transitions, each with its own advantages and limitations. Synchronized commands run sequentially, where each command finishes before the next starts. This ensures orderly execution and straightforward handling of outputs, making it ideal for lightweight commands thatcomplete quickly, such as checking system memory or network connections. On the other hand, asynchronized commands run independently and can execute simultaneously, which is well-suited for heavyweight or time-intensive commands like thread dumps or memory maps. By using synchronized commands for fast, simple tasks and asynchronized commands for heavier operations, the system (108) achieves a balanced and efficient transition process that enhances both speed and reliability.

[0082] In an embodiment, the predefined criteria comprising comparing an execution time period of each command from the set of commands in the transferred list with a threshold time period associated with the transition operation. In an embodiment, each command having the execution time period more than the threshold time period is categorized under the first set of commands (asynchronized commands) and each command having the execution time period less than the threshold time period is categorized under the second set of commands (synchronized commands). For instance, if the threshold execution time is set to five seconds, commands that typically take longer than five seconds to execute are classified as asynchronized, while those expected to complete within five seconds are classified as synchronized. In an embodiment, the threshold time period is a user-defined timer value that indicates the permissible duration for performing the transition operation associated with the network function (NF). This value serves as a reference for categorizing commands based on how long they are expected to take. By defining this threshold, system administrators can control which commands should be treated as lightweight and executed immediately, and which should be handled separately due to their longer execution times. The threshold can be adjusted depending on the specific performance needs and operational constraints of the network environment. For example, commands such as ‘jmap’ and ‘jstack’, which usually require around eight to ten seconds to execute, would be categorized as asynchronized commands. On the other hand, commands like netstat and free-g, which typically complete in one to two seconds, would be considered synchronized commands. This division allows the system toefficiently handle lightweight commands promptly while managing heavier commands separately, thereby optimizing the transition operation without causing unnecessary delays.

[0083] In an embodiment, the processing engine (208) is configured to perform a first set of operations for executing the first set of commands and a second set of operations for executing the second set of commands to manage the transition operation in the network (106). In an embodiment, the first set of operations for executing the first set of commands comprising scheduling the execution of each command from the first set of commands and storing generated output results in the database (210) after completion of the execution. In an embodiment, the first set of operations relates to asynchronized commands, which typically take longer to execute. To manage this efficiently, a separate execution thread is created specifically for handling these heavyweight commands. This design ensures that the execution of time-consuming commands does not interfere with critical or time-sensitive tasks. Each asynchronized command is scheduled for execution on this separate thread in the background, and upon completion, the output of the command is stored in the database (210) for further analysis or historical tracking. First, asynchronized commands will be scheduled to execute, and NF will display their outputs whenever it finishes processing them. For example, if the command j stack is executed, the resulting thread dump showing the state of all running threads in the Java Virtual Machine (JVM) is stored. Similarly, for a jmap command, the heap memory structure or memory usage report is captured and saved. This output is critical for post-transition debugging or performance analysis, especially when diagnosing failures or unusual behavior in the network function. This approach allows the system to continue essential shutdown or switchover activities without being delayed by commands that require longer processing time.

[0084] In an embodiment, the second set of operations for executing the second set of commands (synchronized commands) comprising scheduling, by the processingengine (208), the execution of each command from the second set of commands in parallel with the execution of the first set of commands. In an embodiment, the processing engine (208) waits for the completion of the execution of each command from the synchronized commands. These commands are typically lightweight and are processed in a timely manner without significantly affecting the overall operation flow. In an embodiment, the command execution is handled in synchronized mode on a single thread. This setup ensures that while each lightweight command is being executed, it does not delay or block the execution of other critical operations.

[0085] In an embodiment, the processing engine (208) stores the generated output results in the database after completion of the execution of asynchronized commands and synchronized commands. For example, a synchronized command like netstat, which provides information about active network connections, is executed and its output such as a list of open ports and connection statuses is captured and saved. This stored information can later be used for diagnostics or performance analysis during the transition operation. In an embodiment, the processing engine (208) performs the transition operation in the network after completion of the execution of the synchronized commands.

[0086] In an embodiment, the captured outputs of various NF-r elated information and commands will be displayed and stored in text-based files such as log files (.log), plain text files (.txt), configuration dumps (.conf or .cfg), or system output files (.out or .csv) as per configuration for later debugging. Once all required synchronized commands are completed and their outputs successfully stored, and the application information dump and synchronized commands execution are processed, the processing engine (208) proceeds with executing the actual transition operation in the network. This may involve safely shutting down the NF or switching over to a standby instance, depending on the nature of the request that initiated the process.

[0087] Although FIG. 2 shows an exemplary block diagram (200) of the system (108), in other embodiments, the system (108) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 2. Additionally, or alternatively, one or more components of the system (108) may perform functions described as being performed by one or more other components of the system (108).

[0088] FIG. 3 illustrates an exemplary flow chart (300) of a method for managing the transition operation in the network, in accordance with an embodiment of the disclosure. FIG. 3 is explained in conjunction with FIGs 1 and 2.

[0089] In step 302, the processing engine (208) receives a request to initiate a shutdown or switchover operation related to a network function. This request may originate either manually triggered by an operator or administrator or automatically, as a response to predefined conditions such as failure detection, system health checks, or resource thresholds being crossed. In some cases, the operation may be abrupt, especially in failure scenarios where immediate action is required to maintain service continuity or protect system integrity. Upon receiving the request, the processing engine (208) is configured to collect and record relevant performance-related information before proceeding with the shutdown or switchover. This data capture is essential for diagnosing the system’s condition at the time of the transition. The captured information may include system-level and application-level details such as active connections, session counts, memory usage, and other critical runtime parameters. To extract this information, the processing engine (208) prepares and uses a predefined list of commands. These commands are categorized as either synchronized or asynchronized based on their execution time and nature. The processing engine (208) executes these commands accordingly and gathers their output. All collected information is then stored in a structured format in the database (210), allowing it to be retrieved and analyzed later for debugging, root cause analysis, or system auditpurposes. This process ensures that valuable diagnostic information is not lost during transition operations.

[0090] In step 304, the processing engine (208) schedules the execution of the asynchronized commands in the background. These commands are typically heavier and more time-consuming, such as generating thread dumps or memory maps. Unlike synchronized commands, asynchronized commands are not executed in a strict sequential order and do not block the execution of other operations. Instead, they are scheduled to run independently. Once each asynchronized command is completed, its output is displayed and recorded, ensuring that all relevant performance-related data is eventually collected without delaying the transition process.

[0091] In step 306, the processing engine (208) executes the synchronized commands from the prepared list in parallel to executing the asynchronized commands at the same time. These synchronized commands are typically lightweight and are run sequentially to ensure predictable and orderly execution. The processing engine (208) waits for each command to complete before proceeding to the next, ensuring that all necessary outputs are accurately captured. This helps maintain consistency and reliability, especially when gathering critical runtime information during the early stages of a shutdown or switchover operation. In an embodiment, the captured outputs of various NF related information and commands will be displayed and stored in textbased files as per configuration for later debugging.

[0092] In step 308, the application of the processing engine 208 may enable the NF to proceed to shutdown or switchover. This step is initiated after the necessary performance-related information has been collected and the synchronized commands have been scheduled or executed as required. By this point, the system ensures that critical diagnostic data is secured, minimizing the risk of losing valuable insights during the transition. Once this preparation is complete, the NF can safely and efficiently carry out the shutdown or switchover process.

[0093] In an embodiment, the output of the commands, the performance- related information and the logs are analyzed to determine the root cause of an unplanned switchover or shutdown. In examples, the unplanned switchovers or shutdowns occur due to unexpected events or failures of applications or the NF that disrupt the normal operation of overall system or one or more applications. These events may happen for a variety of reasons, each with their own potential impact on the system. Some reasons of unplanned switchovers or shutdowns include hardware failure, software crashes, power outages, network failures, security incidents, overloads, human errors, environmental factors, dependency failures, updates, and the like. The output of the commands, the performance-related information, and the logs, when analyzed, may provide insights into the reasons for the unplanned switchover or shutdown. These insights may be used for preventive maintenance or error rectifications.

[0094] FIG. 4 illustrates an exemplary system architecture (400) for managing the transition operation in the network (106), in accordance with an embodiment of the disclosure. FIG. 4 is explained in conjunction with FIGs 1, 2 and 3.

[0095] In an embodiment, the processing engine (208) may include a transition application (404) that is specifically designed to manage the shutdown or switchover transition of the NF (402). When a shutdown or switchover operation is triggered either manually or automatically, the processing engine (208) initiates the transition application (404) to begin handling the transition. Through this transition application (404) collects and dumps essential performance-related information about the NF (402). This performance-related information may include, but is not limited to, internal data structures such as local maps used by the NF, the current sizes of request queues, the number and details of active network connections, the number of active or ongoing sessions being maintained by the NF, the memory utilization at the time of transition, and a list of peer applications or services to which the NF is connected. Thisinformation provides valuable insight into the operational state of the NF and is critical for post-event analysis, diagnostics, and troubleshooting. Dumping some of the performance-related information ensures that some of the key operational details are captured for analysis, helping to preserve information that might otherwise be lost during the transition.

[0096] In exemplary implementations, the transition application (404) may prioritize asynchronized commands, scheduling them for execution. Asynchronized commands may execute independently, and their outputs are captured and displayed once processing is complete. In some examples, the transition application (404) is configured to execute synchronized commands in parallel with the asynchronized commands. In some examples, the synchronized commands are executed one at a time, ensuring that all commands are executed before the NF (402) proceeds with the shutdown or switchover transitions. For example, parallel execution allows for efficient handling of the execution of synchronized commands while ensuring that performance- related information is obtained before moving forward.

[0097] In aspects, the NF (402) may display both the NF related information and the executed commands information in, for example, real-time. In aspects, the processing engine 208 may store the NF-related information and the executed commands information in text-based files according to configured settings in the database (210). This database (210) may be used for debugging, allowing operators to review the captured data and analyze any issues that may have occurred during the transition.

[0098] The transition application (404) waits for the execution of the synchronized commands before moving to the transition of the NF (402). Once the transition application (404) has completed the information dump, and synchronized commands have been executed and the outputs are obtained, the NF (402) proceeds with the transition, whether it be the shutdown or the switchover to a different instance.By ensuring that performance-related information and command outputs are captured, the transition application (404) can minimize a risk of data loss and facilitate smoother troubleshooting if any issues arise post-transition.

[0099] FIG. 5 another exemplary flow chart of the method (500) for managing the transition operation in the network (106), in accordance with an embodiment of the disclosure. FIG. 5 is explained in conjunction with FIGs 1, 2, 3 and 4.

[0100] At step (502), the method (500) includes receiving (502) a request for initiating a transition operation associated with a network function (NF) by a receiving unit (212). The transition operation comprises either a shutdown operation or a switchover operation.

[0101] At step (504), the method (500) includes transferring (504) a list comprising a set of commands associated with the initiated transition operation by the receiving unit (212) towards a processing engine (208).

[0102] At step (506), the method (500) includes categorizing (506) the set of commands as a first set of commands or as a second set of commands by the processing engine (208) based on a predefined criteria. The first set of commands comprising one or more asynchronized commands and the second set of commands comprising one or more synchronized commands. The predefined criteria comprising comparing, by the processing engine (208), an execution time period of each command from the set of commands in the transferred list with a threshold time period associated with the transition operation. In an embodiment, each command having the execution time period more than the threshold time period is categorized under the first set of commands and each command having the execution time period less than the threshold time period is categorized under the second set of commands. In an embodiment, the threshold time period is a user-defined timer value indicating a permissible duration for performing the transition operation associated with the NF.

[0103] At step (508), the method (500) includes performing (508), by the processing engine (208), a first set of operations for executing the first set of commands and a second set of operations for executing the second set of commands to manage the transition operation in the network (106). In an embodiment, the first set of operations for executing the first set of commands comprising scheduling the execution of each command from the first set of commands and storing generated output results in a database after completion of the execution.

[0104] In an embodiment, the second set of operations for executing the second set of commands comprising scheduling the execution of each command from the second set of commands in parallel with the execution of the first set of commands. Waiting completion of the execution of each command from the second set of commands. Storing generated output results in the database after completion of the execution and performing the transition operation in the network after completion of the execution.

[0105] The present disclosure aims to prevent the failures that will occur in the scenario where important data becomes unavailable to the user of the NF at the time of its shutdown or switchover. When either of those scenarios occur, the system (108) will first run the asynchronized commands in the background and then run synchronized commands and wait for the completion. After successful execution of the configured commands, the NF proceeds with the shutdown or switchover operation. During this process, all relevant performance-related information and system data are stored in the logs for future reference. Additionally, if configured, the output of specific commands is saved in separate files, enabling easier access and organized analysis during posttransition debugging or performance evaluation. This structured approach ensures that critical information is preserved and accessible even after the NF has transitioned.

[0106] FIG. 6 illustrates an exemplary computer system (600) in which or with which embodiments of the present disclosure may be implemented.

[0107] As shown in FIG. 6, the computer system (600) may include an external storage device (610), a bus (620), a main memory (630), a read-only memory (640), a mass storage device (650), a communication port (660), and a processor (670). A person skilled in the art will appreciate that the computer system (600) may include more than one processor (670) and communication ports (660). The processor (670) may include various modules associated with embodiments of the present disclosure.

[0108] In an embodiment, the communication port (660) may be any of an RS- 232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fibre, a serial port, a parallel port, or other existing or future ports. The communication port (660) may be chosen depending on the network (106), such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (600) connects.

[0109] In an embodiment, the memory (630) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory (640) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (670).

[0110] In an embodiment, the mass storage (650) 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, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks (e.g., SATA arrays).

[0111] In an embodiment, the bus (620) communicatively couples the processor(s) (670) with the other memory, storage, and communication blocks. Thebus (620) may be, e.g., a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB) or the like, for connecting expansion cards, drives and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (670) to the computer system (600).

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

[0113] In yet another exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (500) for managing a transition operation in a network (106). The method (500) comprises receiving (502), by a receiving unit (212), a request for initiating a transition operation associated with a network function (NF). The transition operation comprises either a shutdown operation or a switchover operation. The method further includes transferring (504), by the receiving unit (212), a list comprising a set of commands associated with the initiated transition operation towards a processing engine (208). The processing engine (208) categorizes (506) the set of commands as a first set of commands or as a second set of commands based on a predefined criteria. The first set of commands comprises one or more asynchronized commands and the second set of commands comprises one or more synchronized commands. The processing engine (208) then performs (508) a first set of operationsfor executing the first set of commands and a second set of operations for executing the second set of commands to manage the transition operation in the network (106).

[0114] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0115] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.

[0116] The present disclosure provides a technical advancement in the field of network function management by introducing a method and system that enables efficient handling of shutdown and switchover operations through the structured execution of performance-related diagnostic commands. By categorizing the commands into synchronized and asynchronized sets based on predefined criteria such as execution time, the system ensures that critical data is captured without delaying essential transition processes. This approach allows resource-intensive commands torun concurrently with other operations, preserving important runtime information in logs and configured output files. As a result, the solution significantly improves the reliability, observability, and debuggability of network functions during transition events, helping network operators minimize downtime and troubleshoot issues more effectively. This ensures that essential information such as request queues, active connections, memory usage, thread states, and peer application mappings are retained for post-event analysis. By reducing dependency on manual intervention and minimizing data loss, the present disclosure enhances system observability, shortens debugging time, and improves fault resilience and service continuity in both standalone and clustered deployments of network functions.ADVANTAGES OF THE PRESENT DISCLOSURE

[0117] The present disclosure provides a method and a system for preventing or handling failure scenarios where critical operational or performance-related data becomes unavailable to a user of a Network Function (NF) at the time of shutdown or switchover.

[0118] The present disclosure provides a method and a system that enables the collection of performance-related information from the NF during a shutdown or switchover event. This information includes, but is not limited to, local data maps, request queue sizes, active connections, the number of sessions maintained, memory usage, thread states, system load, and the list of peer applications the NF was connected to.

[0119] The present disclosure provides a method and a system that captures this performance-related information by executing one or more predefined systemlevel or application-specific commands. The outputs of these commands are stored in text-based or structured files according to configured settings.

[0120] The present disclosure provides a method and a system that allows for the immediate and automatic execution of these commands and the saving of cached runtime data at the moment of shutdown or switchover, ensuring that valuable diagnostic information is retained even in the event of an abrupt termination.

[0121] The present disclosure provides a method and a system that reduces debugging time by consolidating all relevant operational data and command outputs into a single accessible location, thereby facilitating quicker root cause analysis.

[0122] The present disclosure provides a method and a system that supports the execution and tracking of multiple commands or diagnostic methods simultaneously, allowing operators or support systems to observe diverse aspects of the NF’s behavior without requiring separate manual efforts.

[0123] The present disclosure provides a method and a system that enables detailed post-event analysis using the captured data to determine the cause of a failure or unexpected behavior in the NF, contributing to faster resolution and improved system reliability.

[0124] The present disclosure provides a method and a system that enables real-time preservation of internal state and system behavior of NFs during transition events such as shutdowns or switchovers, ultimately supporting enhanced observability, fault management, and operational efficiency.

Claims

CLAIMS1. A method (500) for managing a transition operation in a network (106), the method (500) comprising: receiving (502), by a receiving unit (212), a request for initiating a transition operation associated with a network function (NF), wherein the transition operation comprising either a shutdown operation or a switchover operation; transferring (504), by the receiving unit (212), a list comprising a set of commands associated with the initiated transition operation towards a processing engine (208); categorizing (506), by the processing engine (208), the set of commands as a first set of commands or as a second set of commands based on a predefined criteria, wherein the first set of commands comprising one or more asynchronized commands and the second set of commands comprising one or more synchronized commands; and performing (508), by the processing engine (208), a first set of operations for executing the first set of commands and a second set of operations for executing the second set of commands to manage the transition operation in the network (106).

2. The method (500) as claimed in claim 1, wherein the predefined criteria comprising comparing, by the processing engine (208), an execution time period of each command from the set of commands in the transferred list with a threshold time period associated with the transition operation.

3. The method (500) as claimed in claim 2, wherein each command having the execution time period more than the threshold time period is categorized under the first set of commands and each command having the execution time period less than the threshold time period is categorized under the second set of commands.

4. The method (500) as claimed in claim 3, wherein the threshold time period is a user-defined timer value indicating a permissible duration for performing the transition operation associated with the NF.

5. The method (500) as claimed in claim 1, wherein the first set of operations for executing the first set of commands comprising: scheduling, by the processing engine (208), the execution of each command from the first set of commands; and storing, by the processing engine (208), generated output results in a database after completion of the execution.

6. The method (500) as claimed in claim 1, wherein the second set of operations for executing the second set of commands comprising: scheduling, by the processing engine (208), the execution of each command from the second set of commands in parallel with the execution of the first set of commands; waiting, by the processing engine (208), completion of the execution of each command from the second set of commands; storing, by the processing engine (208), generated output results in the database after completion of the execution; and performing the transition operation in the network after completion of the execution.

7. A system (108) for managing a transition operation in a network (106), the system (108) comprising: a receiving unit (212) configured to: receive a request for initiating a transition operation associated with a network function (NF), wherein the transition operation comprising either a shutdown operation or a switchover operation; transfer a list comprising a set of commands associated with the initiated transition operation towards a processing engine (208); wherein the processing engine (208) configured to: categorize the set of commands as a first set of commands or as a second set of commands based on a predefined criteria, wherein the first set of commands comprising one or more asynchronized commands and the second set of commands comprising one or more synchronized commands; and perform a first set of operations for executing the first set of commands and a second set of operations for executing the second set of commands to manage the transition operation in the network (106).

8. The system (108) as claimed in claim 7, wherein the predefined criteria comprising comparing, by the processing engine (208), an execution time period of each command from the set of commands in the transferred list with a threshold time period associated with the transition operation.

9. The system (108) as claimed in claim 8, wherein each command having the execution time period more than the threshold time period is categorized under the first set of commands and each command having the execution time period less than the threshold time period is categorized under the second set of commands.

10. The system (108) as claimed in claim 9, wherein the threshold time period is a user-defined timer value indicating a permissible duration for performing the transition operation associated with the NF.

11. The system (108) as claimed in claim 7, wherein for performing the first set of operations for executing the first set of commands, the processing engine (208) is configured to: schedule the execution of each command from the first set of commands; and store generated output results in a database after completion of the execution.

12. The system (108) as claimed in claim 7, wherein for performing the second set of operations for executing the second set of commands, the processing engine (208) is configured to: schedule the execution of each command from the second set of commands in parallel with the execution of the first set of commands; wait for completion of the execution of each command from the second set of commands; store generated output results in the database after completion of the execution; and perform the transition operation in the network after completion of the execution.

13. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or moreprocessors, cause the one or more processors to execute a method (500) for managing a transition operation in a network, the method (500) comprising: receiving (502), by a receiving unit (212), a request for initiating a transition operation associated with a network function (NF), wherein the transition operation comprising either a shutdown operation or a switchover operation; transferring (504), by the receiving unit (212), a list comprising a set of commands associated with the initiated transition operation towards a processing engine (208); categorizing (506), by the processing engine (208), the set of commands as a first set of commands or as a second set of commands based on a predefined criteria , wherein the first set of commands comprising one or more asynchronized commands and the second set of commands comprising one or more synchronized commands; and performing (508), by the processing engine (208), a first set of operations for executing the first set of commands and a second set of operations for executing the second set of commands to manage the transition operation in the network (106).

Images