FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR IMPLEMENTING A SHUTDOWN PROCESS OF A NODE IN A NETWORK”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR IMPLEMENTING A SHUTDOWN PROCESS OF A NODE IN A NETWORK
TECHNICAL FIELD
[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to implementing a shutdown process of a node in a network.
BACKGROUND
[0002] The following description of the 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 is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication

technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] Moreover, the 5G core networks are based on service-based architecture (SBA) that is centered around network function (NF) services. Each NF can register itself and its supported services to a Network Repository Function (NRF), which is used by other NFs for the discovery of NF instances and their services. The NRF refers to a central repository in the 5th generation network that may provide a unified view of the network resources that may provide ease of communication and coordination between the network elements. The NRF therefore supports functions related to 1) maintaining the profiles of the available network function (NF) instances and their supported services in the 5G core network, 2) allowing NF instances to discover other NF instances in the 5G core network, and 3) allowing the NF instances to track the status of other NF instances. Also, certain NF related details are captured at the NRF whenever an NF comes up with a planned event or first-time commissioning.
[0005] Therefore, there are multiple nodes working or providing their functionality services in 5G/4G network. However, due to many reasons like functionality release upgrade, maintenance purposes, troubleshooting etc., the node server needs to be put down from its services for a particular interval of time. For example- due to some maintenance activity it may be required to remove one AMF’s network node from network, this requires shutdown of this AMF node in a holistic manner.
[0006] As this node was live before, a certain number of consumers/UEs must be served by this node and sudden shutdown of node may put the consumers/UEs in bad state or chances are there that the consumers/UEs may get stuck in network as this node is providing services to millions of users. Taking an example of AMF node, suppose, N2 Handover procedure, as per 3GPP standard (TS 23.502) is in progress. The N2 handover procedure refers to transfer of an active session from one gNodeB to another gNodeB. When Handover Required message is received at

AMF, AMF sends Updatesmcontext Request towards SMF and after getting Updatesmcontext Response, the AMF sends Handover Request towards T-NGRAN. The Updatesmcontext request is sent during the N2 handover to update a mobility management context of a UE. The T-NGRAN refers to a Radio Access network that may support 5th Generation new radio. At this very point, resources for handover are allocated at above mentioned nodes and if now forceful shutdown of AMF has occurred, this will lead to uncertainty of states of UE in network nodes like UE, RAN, SMF and UPF.
[0007] To solve such problems, there is a requirement of an improved Shutdown Framework in the network nodes. Currently known solutions failed to provide such a Shutdown Framework and therefore there is a requirement in the art to overcome the limitations of the existing solutions, which the present disclosure aims to address.
SUMMARY
[0008] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0009] An aspect of the present disclosure may relate to a method for implementing a shutdown process of a node in a network. The system includes receiving, by a processing unit, a request for execution of the shutdown process for the node in the network, from a user interface (UI) of the node, wherein the shutdown process comprises one or more phases. Furthermore, the method includes transmitting, by the processing unit, a data collection request to a shutdown module at the node. The method further encompasses receiving, by the processing unit, in response to the data collection request, an estimated time of completion for each phase of the one or more phases of the shutdown process, from the shutdown module. Furthermore,

the method includes computing, by the processing unit, an estimated time of completion for the shutdown process based at least on the estimated time for each phase of the one or more phases. Further, the method encompasses implementing, by the processing unit, the one or more phases of the shutdown process, based on a sequence associated with each phase of the one or more phases.
[0010] In an exemplary aspect of the present disclosure, the method further comprises initiating, by the processing unit, via the shutdown module, an expiry timer before each phase of the one or more phases is implemented. The method further includes implementing, by the processing unit, one or more operations associated with each phase of the one or more phases. Furthermore, the method includes receiving, by the processing unit, a frame response from the node, depicting status of each phase of the one or more phases. The method further includes updating, by the processing unit, the estimated time of completion for each phase of the one or more phases based at least on the frame response.
[0011] In an exemplary aspect of the present disclosure, the method further comprises receiving, by the processing unit, via the shutdown module, a status update request. Furthermore, the method includes, upon receiving the status update request, displaying, by the processing unit, at least one of the estimated time of completion of each phase of the one or more phases or the estimated time of completion for execution of the shutdown process, on a display unit.
[0012] In an exemplary aspect of the present disclosure, the frame response comprises at least one of an initial frame status and an end frame status.
[0013] In an exemplary aspect of the present disclosure, the one or more phases comprises a first phase, wherein, the first phase terminates registration of new user equipment (UE) with the node.

[0014] In an exemplary aspect of the present disclosure, the one or more phases comprises a second phase, wherein, the second phase enables de-registration of already connected UE from the node.
[0015] In an exemplary aspect of the present disclosure, the one or more phases comprises a third phase, wherein, the third phase enables de-registration of the node from the network.
[0016] In an exemplary aspect of the present disclosure, the one or more phases comprises a fourth phase, wherein, the fourth phase facilitates cleanup of a set of data associated with UE earlier connected with the node, wherein the set of data is stored in a database.
[0017] In an exemplary aspect of the present disclosure, the method further comprises initiating, by the processing unit, from the shutdown module, a periodic trigger to the node. The method further encompasses checking, by the processing unit, via the shutdown module, after time-out of the periodic trigger, a state associated with the node, wherein the state denotes one of a presence or an absence of a progress of at least one phase from the one or more phases of the shutdown process. Furthermore, the method encompasses transmitting, by the processing unit, via the shutdown module, a message about the shutdown process to a standby process at the node, in an event of the absence of the progress of at least one phase from the one or more phases of the shutdown process. The method further includes activating, by the processing unit, the standby process at the node, based on the transmitted message.
[0018] In an exemplary aspect of the present disclosure, the periodic trigger is triggered to the node until, the one or more phases of the shutdown process are implemented.

[0019] Another aspect of the present disclosure may relate to a system for implementing a shutdown process of a node in a network. The system includes a processing unit. The processing unit is configured to receive a request for execution of the shutdown process for the node in the network, from a user interface (UI) of the node. The shutdown process comprises one or more phases. The processing unit is further configured to transmit a data collection request to a shutdown module at the node. Furthermore, the processing unit is configured to receive, an estimated time of completion for each phase of the one or more phases of the shutdown process, from the shutdown module. The processing unit is further configured to compute, an estimated time of completion for the shutdown process based at least on the estimated time of completion for each phase of the one or more phases. Furthermore, the processing unit is configured to implement the one or more phases of the shutdown process, based on a sequence associated with each phase of the one or more phases.
[0020] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for implementing a shutdown process of a node in a network, the instructions include executable code which, when executed by a one or more units of a system, causes: a processing unit of the system to receive a request for execution of the shutdown process for the node in the network, from a user interface (UI) of the node, wherein the shutdown process comprises one or more phases. Further, the instructions include executable code which, when executed causes the processing unit of the system to further transmit a data collection request to a shutdown module at the node. Further, the instructions include executable code which, when executed causes the processing unit of the system to receive, an estimated time of completion for each phase of the one or more phases of the shutdown process, from the shutdown module. Further, the instructions include executable code which, when executed causes the processing unit of the system to further compute, an estimated time of completion for the shutdown process based at least on the estimated time of completion for each phase of the one or more phases; and to further implement the one or more phases

of the shutdown process, based on a sequence associated with each phase of the one or more phases.
OBJECTS OF THE INVENTION
[0021] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0022] It is an object of the present disclosure to provide a system and a method for providing a streamlined shutdown framework that can be used for all NFs of a network.
[0023] It is another object of the present disclosure to provide a solution that reduces the chances of UEs getting stuck in different network nodes via forcefully removing the current Users/UEs from that particular network node by initiating a procedure for each Users/UEs which will detach Users/UEs from that node administratively e.g. In AMF, AMF will initiate Admin Deregistration procedure, so that all Users/UEs get removed from current AMF node and can get freshly registered with other suitable selected AMF node.
[0024] It is also an object of the present disclosure to provide a solution that diminishes the race conditions that could have occurred on other Network function nodes while shutting down a network node.
[0025] It is another object of the present disclosure to provide a solution that in addition to the shutdown process, can provide multiple interim status check functionality through which the node operator can check below things:
• shutdown process is ongoing or not.
• If the shutdown process is in progress, then how much time is left for its completion.
• In which phase the process is currently in.

[0026] It is another object of the present disclosure to provide shutdown framework
that also includes Periodic Triggering functionality to support HA framework of the
node i.e., due to any reasons when node’s active process goes down, its standby
5 process must take control of its services.
[0027] It is yet another object of the present disclosure to provide shutdown
framework that is designed to cope up with many human errors like if multiple
people initiate shutdown at same time or one shutdown is in progress, and someone
10 tries to initiate another.
DESCRIPTION OF THE DRAWINGS
[0028] The accompanying drawings, which are incorporated herein, and constitute
15 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. Also, the embodiments shown in the figures are not to be construed as
20 limiting the disclosure, but the possible variants of the method and system
according to the disclosure are illustrated herein to highlight the advantages of the
disclosure. It will be appreciated by those skilled in the art that disclosure of such
drawings includes disclosure of electrical components or circuitry commonly used
to implement such components.
25
[0029] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.
[0030] FIG. 2 illustrates an exemplary block diagram of a computing device upon
30 which the features of the present disclosure may be implemented in accordance with
exemplary implementation of the present disclosure.
9

[0031] Fig. 3 illustrates an exemplary block diagram of a system for implementing a shutdown process of a node in a network, in accordance with exemplary implementations of the present disclosure. 5
[0032] Fig. 4 illustrates a method flow diagram for implementing a shutdown process of a node in a network in accordance with exemplary implementations of the present disclosure.
10 [0033] FIG. 5 illustrates an illustrates an exemplary system shutdown orchestration
framework for providing streamlined shutdown framework, in accordance with exemplary embodiments of the present disclosure.
[0034] FIG.6 illustrates an exemplary process for streamlined shutdown
15 framework, in accordance with exemplary embodiments of the present disclosure.
[0035] FIG.7 illustrates an exemplary method flow diagram indicating the process for estimating time of completion of the shutdown, in accordance with exemplary embodiments of the present disclosure. 20
[0036] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
25
[0037] 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
30 details. Several features described hereafter may each be used independently of one
another or with any combination of other features. An individual feature may not
10

address any of the problems discussed above or might address only some of the problems discussed above.
[0038] The ensuing description provides exemplary embodiments only, and is not
5 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
10 disclosure as set forth.
[0039] 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
15 specific details. For example, circuits, systems, processes, and other components
may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0040] Also, it is noted that individual embodiments may be described as a process
20 which 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 may 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
25 included in a figure.
[0041] 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
30 aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or
11

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—in a manner
5 similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0042] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for
10 processing instructions. A 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 (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of
15 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 or processing unit is a hardware processor.
20 [0043] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
“a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The
25 user equipment/device may include, but is not limited to, a mobile phone, smart
phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of
30 a transceiver unit, a processing unit, a storage unit, a detection unit and any other
such unit(s) which are required to implement the features of the present disclosure.
12

[0044] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a
form readable by a computer or similar machine. For example, a computer-readable
5 medium includes read-only memory (“ROM”), random access memory (“RAM”),
magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
10
[0045] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with
15 each other, which also includes the methods, functions, or procedures that may be
called.
[0046] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a
20 general-purpose processor, a special purpose processor, a conventional processor,
a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
25
[0047] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
30
13

[0048] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the above-
mentioned and other existing problems in this field of technology by providing a
method and a system for providing streamlined shutdown framework that can be
5 used for all NFs of a network. This streamlined shutdown framework provides the
hooks to the different components of a network node. Through these hooks these components can register themselves for different phases of shutdown. So, this framework starts through CLI (command line interface) and starts its phases in sequential manner, whenever any new phase starts then this framework informs all
10 the components about starting of this phase, so that components who were
interested to do some handling in that phase can start their activity. After finishing their activity for that particular phase, these components can send a completion message towards the framework. In this way, all the configured number of phases will be executed by this framework and all the activities at all the components
15 required for shutdown of that particular node will be completed in given sequence.
In this way that network node will be smoothly shutdown. Here the number of phases is configurable depending upon the requirement of node.
[0049] FIG. 1 illustrates an exemplary block diagram representation of 5th
20 generation core (5GC) network architecture, in accordance with exemplary
implementation of the present disclosure. As shown in FIG. 1, the 5GC network
architecture [100] includes a user equipment (UE) [102], a radio access network
(RAN) [104], an access and mobility management function (AMF) [108], a Session
Management Function (SMF) [106], a Service Communication Proxy (SCP) [110],
25 an Authentication Server Function (AUSF) [112], a Network Slice Specific
Authentication and Authorization Function (NSSAAF) [114], a Network Slice
Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a
Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122],
a Unified Data Management (UDM) [124], an application function (AF) [126], a
30 User Plane Function (UPF) [128], a data network (DN) [130], wherein all the
14

components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
[0050] Radio Access Network (RAN) [104] is the part of a mobile
5 telecommunications system that connects user equipment (UE) [102] to the core
network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
10 [0051] Session Management Function (SMF) [106] is a 5G core network function
responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
15 [0052] Access and Mobility Management Function (AMF) [108] is a 5G core
network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.
20 [0053] Service Communication Proxy (SCP) [110] is a network function in the 5G
core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.
25 [0054] Authentication Server Function (AUSF) [112] is a network function in the
5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
[0055] Network Slice Specific Authentication and Authorization Function
30 (NSSAAF) [114] is a network function that provides authentication and
15

authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.
[0056] Network Slice Selection Function (NSSF) [116] is a network function
5 responsible for selecting the appropriate network slice for a UE based on factors
such as subscription, requested services, and network policies.
[0057] Network Exposure Function (NEF) [118] is a network function that exposes
capabilities and services of the 5G network to external applications, enabling
10 integration with third-party services and applications.
[0058] Network Repository Function (NRF) [120] is a network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions. 15
[0059] Policy Control Function (PCF) [122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.
20 [0060] Unified Data Management (UDM) [124] is a network function that
centralizes the management of subscriber data, including authentication, authorization, and subscription information.
[0061] Application Function (AF) [126] is a network function that represents
25 external applications interfacing with the 5G core network to access network
capabilities and services.
[0062] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS
30 enforcement.
16

[0063] Data Network (DN) [130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.
5 [0064] FIG. 2 illustrates an exemplary block diagram of a computing device [200]
upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [200] may also implement a method for establishing packet data unit (PDU) session with user plane function (UPF) utilising
10 the system. In another implementation, the computing device [200] itself
implements the method for establishing packet data unit (PDU) session with user plane function (UPF) using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
15
[0065] The computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The
20 computing device [200] may also include a main memory [206], such as a random-
access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the
25 processor [204]. Such instructions, when stored in non-transitory storage media
accessible to the processor [204], render the computing device [200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static
30 information and instructions for the processor [204].
17

[0066] A storage device [210], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [202] for storing information and
instructions. The computing device [200] may be coupled via the bus [202] to a
display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
5 Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
displaying information to a computer user. An input device [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command selections to the processor [204]. Another type of user input device may be a cursor controller [216], such as
10 a mouse, a trackball, or cursor direction keys, for communicating direction
information and command selections to the processor [204], and for controlling cursor movement on the display [212]. The input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
15
[0067] The computing device [200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [200] causes or programs the computing device [200] to be a special-purpose machine.
20 According to one implementation, the techniques herein are performed by the
computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium, such as the storage device [210]. Execution of the sequences of instructions
25 contained in the main memory [206] causes the processor [204] to perform the
process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
30 [0068] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a two-
18

way data communication coupling to a network link [220] that is connected to a
local network [222]. For example, the communication interface [218] may be an
integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of
5 telephone line. As another example, the communication interface [218] may be a
local area network (LAN) card to provide a data communication connection to a
compatible LAN. Wireless links may also be implemented. In any such
implementation, the communication interface [218] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing
10 various types of information.
[0069] The computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the communication interface [218]. In the Internet example, a server [230] might
15 transmit a requested code for an application program through the Internet [228], the
ISP [226], the host [224], the local network [222] and the communication interface [218]. The received code may be executed by the processor [204] as it is received, and/or stored in the storage device [210], or other non-volatile storage for later execution.
20
[0070] The present disclosure is implemented by a system [300] as shown in FIG. 3. In an implementation, the system [300] may include the computing device [200] (as shown in FIG. 2). It is further noted that the computing device [200] is able to perform the steps of a method [400] (as shown in FIG. 4).
25
[0071] Referring to FIG. 3, an exemplary block diagram of a system [300] for implementing a shutdown process of a node in a network, is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one processing unit [302], a display unit [306], and a database
30 [308] in a shutdown module [304]. The database [308] may act a storage unit. Also,
all of the components/ units of the system [300] are assumed to be connected to
19

each other unless otherwise indicated below. As shown in the figures all units
shown within the system should also be assumed to be connected to each other.
Further, the system [300] is intended to be read in conjunction with an exemplary
implementation system [500] as shown in FIG. 5. The systems in FIG. 3 and FIG.
5 5 complement each other or are different embodiments of the system of the present
solution. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [300] may be present in a user
10 device to implement the features of the present disclosure. The system [300] may
be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as a UE). In another implementation, the system [300] may reside in a server or a network entity. In yet another implementation, the system [300] may reside partly in the server/ network entity
15 and partly in the user device.
[0072] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components/units can be implemented interchangeably. While specific embodiments may disclose a
20 particular functionality of these units for clarity, it is recognized that various
configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended
25 functionality described herein, are considered to be encompassed within the scope
of the present disclosure.
[0073] The system [300] is configured for implementing a shutdown process of a
node in a network, with the help of the interconnection between the
30 components/units of the system [300]. In an implementation of the present
disclosure, the system [300] is shown to perform the steps in a 5th Generation core
20

network. However, it is to be noted that the system [300] may be implemented across any network which includes but may not be limited to 4th generation, 3rd generation, 6th generation, and any future generations of the network.
5 [0074] The system [300] includes a processing unit [302]. The processing unit
[302] is configured to receive a request for execution of the shutdown process for the node in the network, from a user interface (UI) of the node. The processing unit [302] is further configured to initiate, an expiry timer, via a shutdown module [304], before each phase of the one or more phases is implemented.
10
[0075] The network node refers to a device/ server that may be able to send, receive information in the 5th generation network. The network node may include, but is not limited to, the UE [102], the RAN [104], the AMF [108], the SMF [106], the SCP [110], the AUSF [112], the NSSAAF [114], the NSSF [116], the NEF [118],
15 the NRF [120], the PCF [122], the UDM [124], the AF [126] and the UPF [128].
[0076] In an implementation of the present disclosure, a network node of the AMF
[108] is to be removed from the 5th generation core network. The AMF [108] is
removed due to at least: maintenance of the AMF [108], troubleshooting, an
20 upgrade, a change in infrastructure, and the like. Multiple User Equipment (UE)
may be dependent on the AMF node [108], and a sudden shutdown of the AMF node [108] may affect the user experience. To solve this problem, there is a requirement of a smooth shutdown.
25 [0077] The process of the smooth shutdown involves the processing unit [302] to
receive the request to execute the shutdown process for the node in the 5th generation core network from a network node operator. The request may be sent through any interface of the network node. The interface may be a Graphical User Interface (GUI) or a Command Line Interface (CLI) of that node. The shutdown
30 process includes the one or more phases. The processing unit [302] of the shutdown
module [304] initiates expiry timer for each of the one or more phases. For instance,
21

if the shutdown process is through the CLI, then the CLI command “rt5gamf-admin-initiate-graceful-shutdown” may be used.
[0078] The processing unit [302] is further configured to transmit a data collection
5 request to a shutdown module [304] at the node. In an implementation of the present
disclosure, the shutdown module [304] sends a data collection request through the
processing unit [302] for collecting data from the network node before the
shutdown. A timer may be started for the data collection and the shutdown module
[304] may collect the data. The data includes, but may not be limited to, a current
10 session information, a user activity, and a network performance.
[0079] The processing unit [302] is further configured to receive, an estimated time
of completion for each phase of the one or more phases of the shutdown process,
from the shutdown module [304]. Furthermore, the processing unit [302] is
15 configured to compute, an estimated time of completion for the shutdown process
based at least on the estimated time of completion for each phase of the one or more phases.
[0080] In an implementation of the present disclosure, when the each of the one or
20 more phases start, for instance- start of the Phase 1, the system [300] may notify all
the network nodes who may be involved in the Phase 1 shutdown process. The
network node/s involved in the Phase 1 shutdown process may send the estimated
time for completion of the phase 1 shutdown process at their end. The estimated
time may comprise a minimum and a maximum time of completion. For instance-
25 the estimated time for completion of the phase 1 shutdown process sent by the AMF
[108] is- 20 minutes to 30 minutes. The system [300] may choose the maximum
time of completion, i.e., 30 minutes. Further, the system [300] may have a threshold
limit of the maximum time of completion upper limit, defined by the user/
administrator. For instance, the system’s [300] threshold is 25 minutes, then the
22

system [300] may consider the maximum time of completion of the phase 1 shutdown process as 25 minutes.
[0081] The processing unit [302] may query the shutdown module [304] to receive
5 the estimated time of completion for the each of the one or more phases. For
instance, the shutdown module [304] sends the estimated time of completion for the each of the one or more phases to the processing unit [302] as follows-Estimated time of completion for Phase 1 - 5 minutes,
Estimated time of completion for Phase 2 - 15 minutes, and
10 Estimated time of completion for Phase 3 - 2 minutes.
Estimated time of completion for the shutdown process will thus be 22 minutes.
[0082] In an implementation of the present disclosure, the processing unit [302] may receive a data on estimated time for completion of each of the one or more
15 phases. For instance– the AMF [108] server is active, and the graceful shutdown
may be started by the user at 02:30 AM and request landed on an active system manager [502]. The processing unit [302] may compute the estimated time of completion for the shutdown process, based on the estimated completion of each phase of the one or more phases. The processing unit [302] may compute all the
20 estimated time of the one or more phases and computes the estimated shutdown
time as, say, 22 minutes.
[0083] The processing unit [302] is configured to implement, one or more
operations associated with each phase of the one or more phases. The one or more
25 phases comprises a first phase. The first phase terminates registration of new user
equipment (UE) with the node. The one or more phases comprises a second phase. The second phase enables de-registration of already connected UE from the node. The one or more phases comprises a third phase. The third phase enables de-registration of the node from the network. The one or more phases comprises a
23

fourth phase, wherein, the fourth phase facilitates cleanup of a set of data associated
with UE earlier connected with the node. The set of data is stored in a database
[308]. In an implementation of the present disclosure, on completion of the fourth
phase of the one or more phases, once cleanup of the set of data is performed, the
5 set of data may be stored in the database [308] of the shutdown module [304].
[0084] In an implementation of the present disclosure, after the data collection timeout takes place at the shutdown module [304], the one or more operations of each of the one or more phases are implemented. A first phase expiry timer is
10 implemented by the processing unit [302] of the shutdown module [304]. The first
phase expiry timer refers to the data received for the estimated time for completion of each of the one or more phases. In the first phase, the AMF [108] may terminate registration of a new User Equipment (UE) with the network node of the AMF [108], so that no new UE may register to the AMF [108]. The AMF [108] may only
15 process the procedures for already registered UEs to the AMF [108]. Once a timeout
for the first phase expiry or the end frame response of completion of the first phase is received by the processing unit [302] of the shutdown module [304], the shutdown module [304] may start the expiry timer for a second phase and publishes the second phase trigger. In second phase, the AMF [108] may start removing all
20 the UEs registered to the AMF [108]. If a UE is not idle, it refers to that a process
may be ongoing in the UE. The process may include an ongoing voice call, a call setup, a call ending, and the like. After completion of the process, the AMF [108] may initiate “Network initiated Deregistration procedure with re-registration required” for the UEs registered or connected to the AMF [108]. Consequently, the
25 AMF [108] may restrict the UEs from connecting to the process, the process may
be initiated in the UE by other nodes in the network. Once the second phase timeout or the end frame is received, the shutdown module [304] starts the third phase expiry timer. In the third phase, the AMF [108] may deregister or disconnect from the 5th generation core network on its own. The AMF [108] may deregister all the
30 interfaces from the 5th generation core network. The deregistration includes but may
not be limited to N1 interface, N2 interface, HTTP/2 interface (with 5G core
24

Network Functions like SMF, NRF, and the like) and N26 interface (with MME) to
avoid unnecessary messages or to make sure that no new user may attach to it. The
N1 interface refers to an interface for communication between the UE and the AMF
[108]. The N2 interface refers to an interface for communication between the AMF
5 [108] and the base station. The base station in the 5th generation core network may
be the gNodeB. The HTTP/2 interface may be used by service-based interfaces for communication between the Network Function Services. The N26 interface may refer to an inter network interface for communication between the AMF [108] and a Mobile Management Entity (MME). The AMF [108] may deregister from
10 Network Repository Function (NRF), Service Control Point (SCP), and the like.
Once the third phase timeout or the end frame is received, the shutdown module [304] starts the Fourth phase expiry timer. In the fourth phase, cleanup or removal of the data present in a database [308] of the AMF [108] related to the UE, which are not registered or connected to the AMF [108]. The data from the database [308]
15 of the AMF [108] may be cleared like shared memory data and Database's data. The
AMF [108] may raise alarms, that may be raised in the third phase, in case of any errors detected by the AMF [108].
[0085] Based on the data received, the processing unit [302] may compute and
20 calculate the total estimated time for completion of the shutdown process.
[0086] The processing unit [302] is further configured to receive a frame response
from the node depicting status of each phase of the one or more phases. The frame
response comprises at least one of an initial frame status and an end frame status.
25 The initial frame status refers to the initial status of each of the one or more phases
and the end frame status refers to the final status of each of the one or more phases. The frame response may be sent by the processing unit [302] based on the data collection, the detailed phase wise estimated time, to the User's interface.
30 [0087] In an implementation of the present disclosure, after the data collection
timeout takes place at the shutdown module [304], the processing unit implements
25

a first phase expiry timer of the shutdown module [304]. The first phase expiry
timer refers to the data received for the estimated time for completion of each of the
one or more phases. Once the timer starts, the processing unit [302] of the shutdown
module [304] may receive the frame response from the node. The frame response
5 refers to the status of each of the one or more phases of the shutdown process.
[0088] The processing unit [302] is further configured to receive, a status update
request, via the shutdown module [304]. Furthermore, the processing unit [302] is
configured to upon receipt of the status update request, display at least one of the
10 estimated time of completion of each phase of the one or more phases or the
estimated time of completion for execution of the shutdown process, on a display unit [306].
[0089] In an implementation of the present disclosure, when the node operator
15 sends a request to the shutdown module [304] to obtain status of the shutdown
process, the processing unit [302] may update the shutdown process in the shutdown module [304] and display the update on the estimated time of completion of each of the one or more phases on the display unit [306].
20 [0090] The processing unit [302] is further configured to initiate, from the
shutdown module [304], a periodic trigger to the node. Further, the processing unit [302] is configured to check, via the shutdown module [304], after time-out of the periodic trigger, a state associated with the node, wherein the state denotes one of a presence or an absence of a progress of at least one phase from the one or more
25 phases of the shutdown process. The processing unit [302] is further configured to
transmit, via the shutdown module [304], a message about the shutdown process to a standby process at the node, in an event of the absence of the progress of at least one phase from the one or more phases of the shutdown process. The processing unit [302] is further configured to activate, the standby process at the node, based
30 on the transmitted message. The periodic trigger is triggered to the node, until the
one or more phases of the shutdown process are implemented.
26

[0091] In an implementation of the present disclosure, the processing unit [302] of
the shutdown module [304] may send the periodic trigger to the AMF’s [108]
network nodes consequently with the shutdown process in progress. The periodic
5 trigger may support high availability of the AMF [108]. The periodic trigger may
be performed by the processing unit [302] to check the active status of the AMF [108]. The periodic trigger is initiated to get an update on the estimated time of completion of the each phase of the one or more phases. The periodic trigger may include details of the ongoing phase shutdown process. A response to the periodic
10 trigger may help in determining whether the AMF [108] is in active mode or
inactive. When the shutdown process is initiated at the shutdown module [304], the shutdown module [304] starts the expiry timer and on receiving the timeout, it may check the end status of the AMF [108]. If any of the one or more phases is in progress, the processing unit [302] of the shutdown module [304] may not perform
15 the periodic trigger. If any of the one or more phases is in progress, the processing
unit [302] of the shutdown module [304] may perform the periodic trigger. The periodic trigger may help in performing the shutdown process smoothly at the AMF [108] even if one of the one or more phases is ongoing.
20 [0092] For instance – Let us say the AMF [108] server is up with AMF01 process
as active and AMF11 process as standby. The node operator started the shutdown process at 02:30 AM and request landed on AMF01. The estimated time for whole process was received as 40 minutes, but at 02:45AM AMF01 goes down due to any error. The error may be arithmetic error, unavailability of required memory, and the
25 like. The standby process AMF11 may turn active and start providing services. But
since the AMF11 does not know about the ongoing shutdown process, the periodic trigger which may take place at predefined time intervals, may inform the AMF11 about the ongoing shutdown process. The AMF11 may continue the process. The predefined time interval may be defined by a user, a network node operator, the
30 system [300], or the like.
27

[0093] These acts will not cause any failure in the framework state machine
functioning, in addition to that it will respond to all in between triggers with an ‘in
progress’ message. For example – If Person 1 initiated the shutdown of a node
(AMF) [108] at time 06:30 AM using command-line interface command and in
5 response to the command “Est Time It'll Take – 30min” displays. At 06:40AM
Person 2 also initiated the shutdown of same node (AMF) [108], then “TRANSACTION STATUS: FAILURE: The Shutdown is already in progress.” command response will come on its screen and this new request will not affect the ongoing shutdown process started by Person 1. 10
[0094] The processing unit [302] is further configured to update the estimated time of completion for each phase of the one or more phases based at least on the frame response.
15 [0095] In an implementation of the present disclosure, in between the starting of
the first phase and completion of the fourth phase, the processing unit [302] may revise the total estimated time for completion of the shutdown process in the shutdown module [304]. The revision of the total estimated time for completion of the shutdown process may done based on the frame response of each of the one or
20 more phases. The network node operator can check the revised estimated time left
for completion of the shutdown process via the CLI or the GUI command for interim status.
[0096] Referring to FIG. 4, an exemplary method flow diagram [400] for
25 implementing the shutdown process of a node in a network, in accordance with
exemplary implementations of the present disclosure is shown. In an
implementation the method [400] is performed by the system [300]. Further, in an
implementation, the system [300] may be present in a server device to implement
the features of the present disclosure. Also, as shown in FIG. 4, the method [400]
30 starts at step [402].
28

[0097] At step [404], the method comprises receiving, by a processing unit [302], a request for execution of the shutdown process for the node in the network, from a user interface (UI) of the node, wherein the shutdown process comprises one or more phases. 5
[0098] In an implementation of the present disclosure, a network node of an AMF
[108] is to be removed from the 5th generation core network. The reason for removal
includes but may not be limited to maintenance of the AMF [108], troubleshooting,
an upgrade, a change in infrastructure, and the like. Multiple User Equipment (UE)
10 may be dependent on the AMF node [108], and a sudden shutdown of the AMF
node [108] may affect the user experience. To solve this problem, there is a requirement of a smooth shutdown.
[0099] The process of the smooth shutdown involves the processing unit [302] to
15 receive the request to execute the shutdown process for the node in the 5th
generation core network from a network node operator. The request may be sent
through any interface of the network node. It may be a Graphical User Interface
(GUI) or a Command Line Interface (CLI) of that node The processing unit [302]
of the shutdown module [304] initiates expiry timer for each of the one or more
20 phases. For instance, if the shutdown process is through the CLI, then the CLI
command “rt5gamf-admin-initiate-graceful-shutdown” may be used.
[0100] At step [406], the method comprises transmitting, by the processing unit [302], a data collection request to a shutdown module at the node. In an
25 implementation of the present disclosure, the shutdown module [304] sends a data
collection request through the processing unit [302] for collecting data from the network node before the shutdown. A timer may be started for the data collection and the shutdown module [304] may collect the data. The data includes but may not be limited to a current session information, a user activity, and a network
30 performance.
29

[0101] Next at step [408], the method comprises receiving, by the processing unit [302], in response to the data collection request, an estimated time of completion for each phase of the one or more phases of the shutdown process, from the shutdown module [304]. 5
[0102] In an implementation of the present disclosure, the processing unit [302] may receive a data on estimated time for completion of each of the one or more phases.
10 [0103] Next, at step [410], the method comprises computing, by the processing unit
[302], an estimated time of completion for the shutdown process based at least on the estimated time for each phase of the one or more phases.
[0104] In an implementation of the present disclosure, based on the data received
15 of the estimated time for completion for each of the one or more phases, the
processing unit [302] may compute and calculate the total estimated time for completion of the shutdown process.
[0105] The method further includes initiating, by the processing unit [302], via the
20 shutdown module [304], an expiry timer before each phase of the one or more
phases is implemented. Further, the method includes implementing, by the
processing unit [302], one or more operations associated with each phase of the one
or more phases. In an implementation of the present disclosure, Furthermore, the
method includes receiving, by the processing unit [302], a frame response from the
25 node depicting status of each phase of the one or more phases. The method further
includes updating, by the processing unit [302], the estimated time of completion for each phase of the one or more phases based at least on the frame response.
[0106] In an implementation of the present disclosure, after the data collection
30 timeout takes place at the shutdown module [304], a first phase expiry timer is
implemented by the processing unit [302] of the shutdown module [304]. The first
30

phase expiry timer refers to the data received for the estimated time for completion
of each of the one or more phases. Once the timer starts, the processing unit [302]
of the shutdown module [304] may receive the frame response from the node. The
frame response refers to the status of each of the one or more phases of the shutdown
5 process. The frame response includes an initial frame status and an end frame status.
The initial frame status refers to the initial status of each of the one or more phases
and the end frame status refers to the final status of each of the one or more phases.
The frame response may be sent by the processing unit [302] based on the data
collection, the detailed phase wise estimated time may be returned to the User's
10 interface.
[0107] Next, at step [412], the method comprises implementing, by the processing unit [302], the one or more phases of the shutdown process, based on a sequence associated with each phase of the one or more phases.
15
[0108] In an implementation of the present disclosure, the sequence associated with each phase of the one or more phases may be decided by the network node, i.e., the AMF [108] in this instance. The AMF [108] may allocate numbers to the one or more phases to determine the order of the shutdown process. After the data
20 collection timeout takes place at the shutdown module [304], the one or more
operations of each of the one or more phases are implemented. A first phase expiry timer is implemented by the processing unit [302] of the shutdown module [304]. The first phase expiry timer refers to the data received for the estimated time for completion of each of the one or more phases. In the first phase, the AMF [108]
25 may terminate registration of a new User Equipment (UE) with the network node
of the AMF [108], so that no new UE may register to the AMF [108]. The AMF [108] may only process the procedures for already registered UEs to the AMF [108]. Once a timeout for the first phase expiry or the end frame response of completion of the first phase is received by the processing unit [302] of the shutdown module
30 [304], the shutdown module [304] may start the expiry timer for a second phase and
publishes the second phase trigger. In second phase, the AMF [108] may start
31

removing all the UEs registered to the AMF [108]. If a UE is not idle, it refers to
that a process may be ongoing in the UE. The process may include an ongoing voice
call, a call setup, a call ending, and the like. After completion of the process, the
AMF [108] may initiate “Network initiated Deregistration procedure with re-
5 registration required” for the UEs registered or connected to the AMF [108].
Consequently, the AMF [108] may restrict the UEs from connecting to the process, the process may be initiated in the UE by other nodes in the network. Once the second phase timeout or the end frame is received, the shutdown module [304] starts the third phase expiry timer. In third phase, the AMF [108] may deregister or
10 disconnect from the 5th generation core network on its own. The AMF [108] may
deregister all the interfaces from the 5th generation core network. The deregistration includes but may not be limited to N1 interface, N2 interface, HTTP/2 interface (with 5G core Network Functions like SMF, NRF etc.) and GTP N26 interface (with MME) to avoid unnecessary messages or to make sure that no new user will get
15 attach to it. The AMF [108] may deregister from Network Repository Function
(NRF), and the like. The NRF refers to a central repository in the 5th generation network that may provide a unified view of the network resources. The NRF may provide ease of communication and coordination between the network elements. Once the third phase timeout or the end frame is received, the shutdown module
20 [304] starts the fourth phase expiry timer. In fourth phase, cleanup or removal of
the data present in a database of the AMF [108] related to the UE, which are not registered or connected to the AMF [108]. The data from the database of the AMF [108] may be cleared like shared memory data and Database's data. The AMF [108] may raise alarms, that may be raised in this phase, in case of any errors detected by
25 the AMF [108].
[0109] The method further includes receiving, by the processing unit [302], via the
shutdown module [304], a status update request. The method further includes upon
receiving the status update request, displaying, by the processing unit [302], at least
30 one of the estimated time of completion of each phase of the one or more phases or
32

the estimated time of completion for execution of the shutdown process, on a display unit [306].
[0110] In an implementation of the present disclosure, when the node operator
5 sends a request to the shutdown module [304] to obtain status of the shutdown
process, the processing unit [302] may update the shutdown process in the shutdown module [304] and display the update on the estimated time of completion of each of the one or more phases on the display unit [306].
10 [0111] The method further includes initiating, by the processing unit [302], from
the shutdown module [304], a periodic trigger to the node. The method further includes checking, by the processing unit, via the shutdown module [304], after time-out of the periodic trigger, a state associated with the node, wherein the state denotes one of a presence or an absence of a progress of at least one phase from the
15 one or more phases of the shutdown process. Furthermore, the method encompasses
transmitting, by the processing unit, via the shutdown module [304], a message about the shutdown process to a standby process at the node, in an event of the absence of the progress of at least one phase from the one or more phases of the shutdown process. The method further includes activating, by the processing unit
20 [302], the standby process at the node, based on the transmitted message. In an
implementation of the present disclosure, the message may be sent to the standby system manager [504] based on the update received from the active system manager [502] of an inactive status of the active system manager [502]. The message may include information of no progress of the shutdown process after a predetermined
25 number of periodic triggers, where the predetermined number of periodic triggers
may be defined by the user. For example-[0112] At periodic trigger 1, the estimated time of completion of the shutdown process is- 27 minutes.
30
33

[0113] At periodic trigger 2, the estimated time of completion of the shutdown process is- 25 minutes.
[0114] Further at periodic trigger 3, the estimated time of completion of the
5 shutdown process remains at 25 minutes.
[0115] The estimated time of completion of the shutdown process remains at 25
minutes for 2 more periodic triggers, and the predetermined number of periodic
triggers having same amount of the estimated time of completion of the shutdown
10 process is determined by the user to be 4. After which the processing unit [302]
may send the message ‘AMF inactive’ to the standby system manager [504].
[0116] In an implementation of the present disclosure, the processing unit [302] of the shutdown module [304] may send the periodic trigger to the AMF’s [108]
15 network nodes consequently with the shutdown process in progress. The periodic
trigger may support high availability of the AMF [108]. When the shutdown process is initiated at the shutdown module [304], the shutdown module [304] starts the expiry timer and on receiving the timeout, it may check the end status of the AMF [108]. If any of the one or more phases is in progress, the processing unit [302] of
20 the shutdown module [304] may not perform the periodic trigger. If any of the one
or more phases is in progress, the processing unit [302] of the shutdown module [304] may perform the periodic trigger. The periodic trigger may include details of the ongoing phase shutdown process. The periodic trigger may help in performing the shutdown process smoothly at the AMF [108] even if one of the one or more
25 phases is ongoing. For instance – Let us say the AMF [108] server is up with
AMF01 process as active and AMF11 process as standby. The node operator started the shutdown process at 02:30 AM and request landed on AMF01. The estimated time for whole process was received as 40 minutes, but at 02:45AM AMF01 goes down due to any error. The error may be arithmetic error, unavailability of required
30 memory, and the like. The standby process AMF11 will turn active and start
providing services. But since the AMF11 does not know about the ongoing
34

shutdown process, the periodic trigger which may take place at predefined time
intervals, may inform the AMF11 about the ongoing shutdown process. The
AMF11 will be able to continue the process. The predefined time interval may be
defined by a user, a network node operator, the system [300], or the like. 5
[0117] These acts will not cause any failure in the framework state machine functioning, in addition to that it will respond to all in between triggers with an ‘in progress’ information message. For example – If Person 1 initiated the shutdown of a node (AMF) [108] at time 06:30 AM using command-line interface command
10 and in response to the command “Est Time It'll Take – 30min” displays. At
06:40AM Person 2 also initiated the shutdown of same node (AMF) [108], then “TRANSACTION STATUS: FAILURE: The Shutdown is already in progress.” command response will come on its screen and this new request will not affect the ongoing shutdown process started by Person 1.
15
[0118] The method terminates at [414].
[0119] It is pertinent to note that the functionalities as disclosed in the present
disclosure are exemplary and not limited to AMF. The scope of the present
20 disclosure may extend to the solution for the other network nodes as well in light
of the exemplary implementations as provided in the present disclosure.
[0120] The system [300] and method [400] will be explained in detail in the
exemplary illustration as shown in FIG. 5. Referring to FIG. 5, it illustrates an
25 exemplary implementation of shutdown orchestration framework for providing
streamlined shutdown framework, in accordance with exemplary embodiments of the present disclosure.
[0121] As shown in FIG. 5, in the system [500], the shutdown process is initiated
30 either manually by the network node operator or automatically by an event trigger
scheduled in the system [500].
35

[0122] An active system manager [502] may perform the shutdown process. If the
active system manager [502] is inactive due to any reason, the shutdown process
may be continued by a standby system manager [504]. The active system manager
5 [502] may be directly connected to the Phase 1 [506], Phase 2 [508], Phase 3 [510],
Phase 4 [512], …...Phase n. The standby system manager [504] may not be directly connected to the Phase1 [506], Phase 2 [508], Phase 3 [510], Phase 4 [512], …...Phase n. The standby system manager [504] may be connected with the active system manager [502]. The standby system manager [504] may check-point the
10 active system manager [502] to ensure continuation of graceful shutdown process
at the AMF [108]. For instance– The AMF [108] server is active as AMF01 process. The AMF11 process is at standby. The graceful shutdown may be started by the user at 02:30 AM and this request lands on the active system manager [502], AMF01 in this instance. The estimated time for the completion of the graceful
15 shutdown process is 40min. At 02:45AM, the active system manager [502], in this
example the AMF01 goes down due to an arithmetic error or unavailability of required memory. The standby system manager [504] may then turn active, in this example the AMF11, and continue the graceful shutdown process.
20 [0123] The request may be sent through any interface of the network node. It may
be a Graphical User Interface (GUI) or a Command Line Interface (CLI) [516] or an application programming Interface [518] of that node.
[0124] The processes [506], [508], [510], and [512] depicts the first phase, the
25 second phase, the third phase, and the fourth phase of the shutdown process,
respectively. The first phase, the second phase, the third phase,….Phase ‘n’ may be implemented by a Network Management System (NMS) ping module [522]. The NMS ping module [522] helps in monitoring the availability and working of the UEs within the 5th generation core network. 30
36

[0125] At [506], the first phase trigger is implemented by the shutdown module
[304]. The periodic trigger may include details of the ongoing phase shutdown
process. The periodic trigger may help in performing the shutdown process
smoothly at the AMF [108] even if one of the one or more phases is ongoing. If the
5 first phase is in progress, the shutdown module [304] may not perform anything in
the periodic trigger. If the first phase is in progress, the shutdown module [304]
may publish the periodic trigger. In the first phase, the AMF [108] may terminate
registration of a new User Equipment (UE) with the network node of the AMF
[108], so that no new UE may register to the AMF [108]. The AMF [108] may only
10 process the procedures for already registered UEs to the AMF [108]. The timeout
for the first phase expiry or the end frame response of completion of the first phase.
[0126] At [508], the second phase begins when the timeout for the first phase expiry or the end frame response of completion of the first phase is received by the
15 shutdown module [304]. The shutdown module [304] may start the expiry timer for
a second phase and publishes the second phase trigger. In the second phase, the AMF [108] may start removing all the UEs registered to the AMF [108]. If a UE is not idle, it refers to that a process may be ongoing in the UE. The process may include an ongoing voice call, a call setup, a call ending, and the like. After
20 completion of the process, the AMF [108] may initiate “Network initiated
Deregistration procedure with re-registration required” for the UEs registered or connected to the AMF [108]. Consequently, the AMF [108] may restrict the UEs from connecting to the process, the process may be initiated in the UE by other nodes in the network. The second phase timeout or the end frame is received, the
25 shutdown module [304].
[0127] At [510], once the second phase timeout or the end frame is received, the
shutdown module [304] starts the Third phase expiry trigger. In third phase, the
AMF [108] may deregister or disconnect from the 5th generation core network on
30 its own. The AMF [108] may deregister all the interfaces from the 5th generation
core network. The deregistration includes but may not be limited to N1 interface,
37

N2 interface, HTTP/2 interface (with 5G core Network Functions like SMF, NRF
etc.) and GTP N26 interface (with MME) to avoid unnecessary messages or to make
sure that no new user will get attach to it. The AMF [108] may deregister from
Network Repository Function (NRF), Service Control Point (SCP), and the like.
5 The third phase timeout or the end frame is received.
[0128] At [512], once the third phase timeout or the end frame is received, the
shutdown module [304] starts the fourth phase expiry timer. In fourth phase,
cleanup or removal occurs of the data present in a database of the AMF [108] related
10 to the UE, which are not registered or connected to the AMF [108]. The data from
the database of the AMF [108] may be cleared like shared memory data and Database's data. The AMF [108] may raise alarms, that may be raised in this phase, in case of any errors detected by the AMF [108].
15 [0129] At [514], in between the starting of the first phase [506] and completion of
the fourth phase [512], the network node operator can check the revised estimated time left for completion of the shutdown process via using provided command-line interface [516] commands or GUI commands or Application programming Interface [518], for Interim status.
20
[0130] An alarm module [520] may raise alarms, that may be raised in this phase, in case of any errors detect by the system [502].
[0131] The implementation system as shown in FIG. 5 will be clearer by an
25 exemplary process as shown in FIG. 5. Referring to FIG.6, it illustrates an
exemplary process for streamlined shutdown framework, in accordance with exemplary embodiments of the present disclosure.
[0132] At step 1, the shutdown module [304] receives the request to execute the
30 shutdown process for the node in the 5th generation core network from a node 1
User Interface [602].
38

[0133] At step 2, the shutdown module [304] sends the data collection request to a
NODE 1 [604] for collecting data from the network node before the shutdown. The
timer may be started for the data collection and the shutdown module [304] may
collect the data. The data includes but may not be limited to a current session
5 information, a user activity, and a network performance.
[0134] At step 3, after the data collection timeout takes place at the shutdown module [304], the first phase expiry timer is implemented by the shutdown module [304]. The first phase expiry timer refers to the data received for the estimated time
10 for completion of each of the one or more phases. Once the timer starts, the
shutdown module [304] may receive the frame response from the node. The frame response refers to the status of each of the one or more phases of the shutdown process. The frame response includes an initial frame status and an end frame status. The initial frame status refers to the initial status of each of the one or more phases
15 and the end frame status refers to the final status of each of the one or more phases.
[0135] At step 4, the shutdown module [304] sends the estimated time for
completion of each of the one or more phases to the Node 1 UI [602]. The shutdown
module [304] may also compute and calculate the total estimated time for
20 completion of the shutdown process.
[0136] At step 5, after the data collection timeout takes place at the shutdown
module [304], the one or more operations of each of the one or more phases are
implemented. 25
[0137] At step 6, the first phase trigger is implemented by the shutdown module
[304] to the NODE 1 [604]. The NODE 1 may be the AMF [108], in the
implementation. The NODE 2 may be the SMF [106] or the UDM [124]. The
periodic trigger may include details of the ongoing phase shutdown process. The
30 periodic trigger may help in performing the shutdown process smoothly at the AMF
[108] even if one of the one or more phases is ongoing. If the first phase is in
39

progress, the shutdown module [304] may not perform anything in the periodic trigger. If the first phase is in progress, the shutdown module [304] may publish the periodic trigger.
5 [0138] At step 7, 8 and 9, the first phase expiry timer refers to the data received for
the estimated time for completion of each of the first phases. In the first phase, the
AMF [108] may terminate registration of a new User Equipment (UE) with the
network node of the AMF [108], so that no new UE may register to the AMF [108].
The AMF [108] may only process the procedures for already registered UEs to the
10 AMF [108]. The timeout for the first phase expiry or the end frame response of
completion of the first phase.
[0139] At step 10, the second phase begins when the timeout for the first phase
expiry or the end frame response of completion of the first phase is received by the
15 shutdown module [304], the shutdown module [304] may start the expiry timer for
a second phase and publishes the second phase trigger at step 11.
[0140] At steps 12, 13, and 14, in second phase, the AMF [108] may start removing all the UEs registered to the AMF [108]. If a UE is not idle, it refers to that a process
20 may be ongoing in the UE. The process may include an ongoing voice call, a call
setup, a call ending, and the like. After completion of the process, the AMF [108] may initiate “Network initiated Deregistration procedure with re-registration required” for the UEs registered or connected to the AMF [108]. Consequently, the AMF [108] may restrict the UEs from connecting to the process, the process may
25 be initiated in the UE by other nodes in the network. The second phase timeout or
the end frame is received, the shutdown module [304].
[0141] At step 15, once the second phase timeout or the end frame is received, the
shutdown module [304] starts the third phase expiry trigger at step 16. 30
40

[0142] At steps 17, 18, and 19, in third phase, the AMF [108] may deregister or
disconnect from the 5th generation core network on its own. The AMF [108] may
deregister all the interfaces from the 5th generation core network. The deregistration
includes but may not be limited to N1 interface, N2 interface, HTTP/2 interface
5 (with 5G core Network Functions like SMF, NRF etc.) and GTP N26 interface (with
MME) to avoid unnecessary messages or to make sure that no new user will get
attach to it. The AMF [108] may deregister from Network Repository Function
(NRF), Service Control Point (SCP), and the like. The third phase timeout or the
end frame is received. 10
[0143] At step 20, the shutdown module [304] may perform the further steps for
any other phase ‘n’. for instance, once the third phase timeout or the end frame is
received, the shutdown module [304] starts the fourth phase expiry timer. In fourth
phase, cleanup or removal of the data present in a database of the AMF [108] related
15 to the UE, which are not registered or connected to the AMF [108]. The data from
the database of the AMF [108] may be cleared like shared memory data and Database's data. The AMF [108] may raise alarms, that may be raised in this phase, in case of any errors detected by the AMF [108].
20 [0144] At step 21, once all the phases and frames are complete, the shutdown
process comes to an end.
[0145] FIG. 7 illustrates an exemplary method flow diagram indicating the process for estimating time of completion of the shutdown. 25
[0146] At step 1, the request to execute the shutdown process for the node in the 5th generation core network from a node 1 User Interface [602] is received by the shutdown module [304].
30 [0147] At step 2, the shutdown module [304] sends the data collection request to a
NODE 1 [604] for collecting data from the network node before the shutdown. The
41

timer may be started for the data collection and the shutdown module [304] may collect the data. The data includes but may not be limited to a current session information, a user activity, and a network performance.
5 [0148] At step 3, based on the data collected and received by the shutdown module
[304], the NODE 1 [604] sends an estimate of time for each of the one or more phases.
[0149] At step 4, on the basis of the phase wise estimated time received by the
10 shutdown module [304] for completion of the shutdown process, the shutdown
module [304] may compute the total estimated time for completion of the shutdown process.
[0150] At step 5, when the node operator sends the request to the shutdown module
15 [304] to obtain status of the shutdown process, the shutdown module [304] forwards
the request to the NODE 1 [604] to obtain a current status on the data collection.
[0151] At step 6, the shutdown module [304] received the current status of the data collection. 20
[0152] At step 7, based on the received current status, the shutdown module [304] may update the shutdown process and send a revised estimated time for completion to the NODE1 UI [602].
25 [0153] At step 8, the shutdown process comes to an end.
[0154] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for implementing a shutdown process of a node
in a network, the instructions include executable code which, when executed by a
30 one or more units of a system, causes: a processing unit [302] of the system to
receive a request for execution of the shutdown process for the node in the network,
42

from a user interface (UI) of the node, wherein the shutdown process comprises one or more phases. Further, the instructions include executable code which, when executed causes the processing unit [302] of the system to further transmit a data collection request to a shutdown module at the node; and receive, an estimated time of completion for each phase of the one or more phases of the shutdown process, from the shutdown module [304]. Further, the instructions include executable code which, when executed causes the processing unit [302] of the system to further compute, an estimated time of completion for the shutdown process based at least on the estimated time of completion for each phase of the one or more phases. Further, the instructions include executable code which, when executed causes the processing unit [302] of the system to further implement the one or more phases of the shutdown process, based on a sequence associated with each phase of the one or more phases.
[0155] As is evident from the above, the present disclosure provides a technically advanced solution for implementing a shutdown process of a node in a network. The present solution provides a system and method for providing streamlined shutdown framework that can be used for all NFs of a network. The present solution further provides a solution that reduces the chances of UEs, getting stuck in different network nodes via forcefully removing the current Users/UEs from that particular network node by initiating a procedure for each Users/UEs which will detach Users/UEs from that node administratively e.g. In the AMF, the AMF will initiate Admin Deregistration procedure, so that all Users/UEs get removed from current AMF node and can get freshly registered with other suitable selected AMF node. The present disclosure provides a solution that diminishes the race conditions that could have occurred on other Network function nodes while shutting down a network node. The present solution provides a solution that in addition to the shutdown process, can provide multiple interim status check functionality through which the node operator can check whether the shutdown process is ongoing or not, if shutdown process is in progress, then how much time is left for its completion, and in which phase the process is currently in.

[0156] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

We Claim:
1. A method for implementing a shutdown process of a node in a network,
comprising:
- receiving, by a processing unit [302], a request for execution of the shutdown process for the node in the network, from a user interface (UI) [602] of the node, wherein the shutdown process comprises one or more phases;
- transmitting, by the processing unit [302], a data collection request to a shutdown module [304] at the node;
- receiving, by the processing unit [302], in response to the data collection request, an estimated time of completion for each phase of the one or more phases of the shutdown process, from the shutdown module [304];
- computing, by the processing unit [302], an estimated time of completion for the shutdown process based at least on the estimated time for each phase of the one or more phases; and
- implementing, by the processing unit [302], the one or more phases of the shutdown process, based on a sequence associated with each phase of the one or more phases.
2. The method as claimed in claim 1, further comprising:
- initiating, by the processing unit [302], via the shutdown module [304], an expiry timer before each phase of the one or more phases is implemented;
- implementing, by the processing unit [302], one or more operations associated with each phase of the one or more phases;
- receiving, by the processing unit [302], a frame response from the node depicting status of each phase of the one or more phases; and
- updating, by the processing unit [302], the estimated time of completion for each phase of the one or more phases based at least on the frame response.

3. The method as claimed in claim 2, further comprising:
- receiving, by the processing unit [302], via the shutdown module [304], a status update request; and
- upon receiving the status update request, displaying, by the processing unit [302], at least one of the estimated time of completion of each phase of the one or more phases or the estimated time of completion for execution of the shutdown process, on a display unit [306].

4. The method as claimed in claim 2, wherein the frame response comprises at least one of an initial frame status and an end frame status.
5. The method as claimed in claim 1, wherein the one or more phases comprises a first phase, wherein, the first phase terminates registration of new user equipment (UE) with the node.
6. The method as claimed in claim 1, wherein, the one or more phases comprises a second phase, wherein, the second phase enables de-registration of already connected UE from the node.
7. The method as claimed in claim 1, wherein, the one or more phases comprises a third phase, wherein, the third phase enables de-registration of the node from the network.
8. The method as claimed in claim 1, wherein, the one or more phases comprises a fourth phase, wherein, the fourth phase facilitates cleanup of a set of data associated with UE earlier connected with the node, wherein the set of data is stored in a database [308].
9. The method as claimed in claim 1, further comprising:
- initiating, by the processing unit [302], from the shutdown module
[304], a periodic trigger to the node;

- checking, by the processing unit [302], via the shutdown module [304], after time-out of the periodic trigger, a state associated with the node, wherein the state denotes one of a presence or an absence of a progress of at least one phase from the one or more phases of the shutdown process;
- transmitting, by the processing unit [302], via the shutdown module [304], a message about the shutdown process to a standby process at the node, in an event of the absence of the progress of at least one phase from the one or more phases of the shutdown process; and
- activating, by the processing unit [302], the standby process at the node, based on the transmitted message.

10. The method as claimed in claim 9, wherein the periodic trigger is triggered to the node until the one or more phases of the shutdown process are implemented.
11. A system for implementing a shutdown process of a node in a network, comprising:
- a processing unit [302], configured to:
receive a request for execution of the shutdown process for the
node in the network, from a user interface (UI) [602] of the node,
wherein the shutdown process comprises one or more phases;
transmit a data collection request to a shutdown module [304] at
the node;
receive, an estimated time of completion for each phase of the
one or more phases of the shutdown process, from the shutdown
module [304];
compute, an estimated time of completion for the shutdown
process based at least on the estimated time of completion for
each phase of the one or more phases; and

implement the one or more phases of the shutdown process, based on a sequence associated with each phase of the one or more phases.
12. The system as claimed in claim 11, wherein the processing unit [302] is
further configured to:
- Initiate an expiry timer via the shutdown module [304], before each phase of the one or more phases is implemented;
- Implement one or more operations associated with each phase of the one or more phases;
- receive a frame response, from the node, depicting status of each phase of the one or more phases; and
- update the estimated time of completion for each phase of the one or more phases based at least on the frame response.
13. The system as claimed in claim 12, wherein the processing unit [302] is
further configured to:
- receive a status update request via the shutdown module [304]; and
- upon receipt of the status update request, display at least one of the estimated time of completion of each phase of the one or more phases or the estimated time of completion for execution of the shutdown process, on a display unit [306].

14. The system as claimed in claim 12, wherein the frame response comprises at least one of an initial frame status and an end frame status.
15. The system as claimed in claim 11, wherein the one or more phases comprises a first phase, wherein, the first phase terminates registration of new user equipment (UE) with the node.

16. The system as claimed in claim 11, wherein, the one or more phases comprises a second phase, wherein, the second phase enables de-registration of already connected UE from the node.
17. The system as claimed in claim 11, wherein, the one or more phases comprises a third phase, wherein, the third phase enables de-registration of the node from the network.
18. The system as claimed in claim 11, wherein, the one or more phases comprises a fourth phase, wherein, the fourth phase facilitates cleanup of a set of data associated with UE earlier connected with the node, wherein the set of data is stored in a database [308].
19. The system as claimed in claim 11, wherein the processing unit [302] is further configured to:

- initiate, from the shutdown module [304], a periodic trigger to the node;
- checking, via the shutdown module [304], after time-out of the periodic trigger, a state associated with the node, wherein the state denotes one of a presence or an absence of a progress of at least one phase from the one or more phases of the shutdown process;
- transmit, via the shutdown module [304], a message about the shutdown process to a standby process at the node, in an event of the absence of the progress of at least one phase from the one or more phases of the shutdown process; and
- activate, the standby process at the node, based on the transmitted message.
20. The system as claimed in claim 19, wherein, the periodic trigger is triggered
to the node until the one or more phases of the shutdown process are
implemented.