DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
SYSTEM AND METHOD FOR HIGH AVAILABILITY MANAGEMENT OF NETWORK FUNCTIONS (NFS) IN A NETWORK
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

FIELD OF THE INVENTION
[0001] The present invention generally relates to wireless networks, and more particularly relates to a system for High Availability (HA) management of Network Functions (NFs) in the networks.
BACKGROUND OF THE INVENTION
[0002] High Availability (HA) management is an important requirement in software deployment. HA management ensures a system, application, or service remains accessible and operational without interruption or downtime. HA management involves proper switchover time, integration effort, environment, auto-recovery, split-brain scenarios, controlled switchover, multiple instance management, and geo-redundancy. The switchover time indicates the duration the system takes to transition from one component or resource to another in the event of a failure or maintenance. An auto-recovery indicates the automatic process of recovering from a failure or service interruption without requiring a manual intervention. The split-brain scenario indicates a failure or communication that causes a partitioning of the system into multiple subgroups for processing the application.
[0003] Conventional HA management techniques are not well suited to resource handling and are not capable of ensuring the system operates without interruption or downtime.
[0004] Therefore, there is a need in an art to provide a system and a method for high availability management and anomaly detection.
SUMMARY OF THE INVENTION
[0005] One or more embodiments of the present disclosure provide a method for High Availability (HA) management of Network Functions (NFs) in a network.
[0006] In one aspect of the present invention a system for HA management of NFs in a network is disclosed. The system includes a registration module configured to register a plurality of NFs hosted in the network. Each of the plurality of NFs includes active NFs, standby NFs and geo-redundant NFs. The system further includes a NF checking module. The NF checking module configured to check in real time, if each of the active NFs meets a pre-defined criteria. In an embodiment, upon detecting if at least one of each of the active NFs does not meet the pre-defined criteria, a NF detection module is configured to check, availability of at least one of the standby NF and the geo-redundant NF. The system further includes a switching module. The switching module configured to switch to at least one of the standby NFs and the geo-redundant NFs based on the availability.
[0007] In another aspect of the present invention, a method for HA management of NFs in a network is disclosed. The method includes the steps of registering a plurality of NFs hosted in the network, wherein the plurality of NFs includes active NFs, standby NFs and georedundant NFs. The method includes the steps of checking in real time, if each of the active NFs meets the pre-defined criteria. The method includes the steps of upon detecting if at least one of each of the active NFs does not meet the pre-defined criteria, checking the availability of at least one of the standby NFs and the geo-redundant NFs. The method includes the steps of switching to at least one of the standby NFs and the geo-redundant NFs based on the availability.
[0008] In one embodiment, registering the plurality of NFs in the network by assigning a Virtual Internet Protocol (VIP) to each of the plurality of NFs. In one embodiment, the plurality of NFs are registered based on one of, configuring details in a configuration file of each NF and following a registration process. In one embodiment, the registration process includes receiving registration details of each NF and subsequently authenticating the respective NF.
[0009] In one embodiment, the pre-defined criteria are not met by the active NF when at least one of, traffic created due to multiple conditions at the active NF, a data replication failure at the active NF, active task being down, stack port being down, interface being down, the assigned VIP being removed from the active NF.
[00010] In another embodiment, the step of switching, to at least one of the standby NF and the geo-redundant NF based on the availability, includes, routing, one or more pre-defined tasks of the active NF to the at least one of the standby NF and the geo-redundant NF based on availability. In one embodiment, the step of switching to the at least one available geo-redundant NF from the active NF when none of the standby NFs are available. In one embodiment, the step of switching to at least one of the standby NF and the geo-redundant NF based on the availability is based on at least one switching technique.
[00011] In one embodiment, routing one or more predefined tasks from the active NF to one of the standby NF and geo redundant NF, by raising a Virtual Internet Protocol (VIP) request to one of the standby NF and the geo-redundant NF based on availability.
[00012] In one embodiment, the one or more processors is configured to receive instructions from a user through a User Equipment (UE) to switch from the at least one active NF to one of the standby NF and the geo-redundant NF. In one embodiment, receive instructions from the user via a Command Line Interface (CLI) to switch from the active NF to one of the standby NF and the geo-redundant NF. In one embodiment, one or more processors monitors each NF via the CLI.
[00013] In another embodiment, subsequent to registration of the plurality of NFs in the network, creating a cluster including the active NFs, standby NFs and the geo-redundant NFs, wherein the cluster enabling communication between each of the active NF, standby NF and the georedundant NF.
[00014] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
[00015] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[00016] FIG. 1 is an exemplary block diagram of an environment for High Availability (HA) management of Network Functions (NFs) in a network, according to various embodiments of the present invention.
[00017] FIG. 2 is an exemplary block diagram of a system for HA management of NFs in a network, according to various embodiments of the present invention.
[00018] FIG. 3a is an exemplary block diagram of a HA management of NFs in a network in a first scenario, according to various embodiments of the present system.
[00019] FIG. 3b is an exemplary block diagram of a HA management of NFs in a network in a second scenario, according to various embodiments of the present system.
[00020] FIG. 3c is an exemplary block diagram of a HA management of NFs in a network in a third scenario, according to various embodiments of the present system.
[00021] FIG. 4 shows a flow diagram of a method for HA management of NFs in a network, according to various embodiments of the present system.
[00022] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[00023] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[00024] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[00025] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[00026] As per various embodiments depicted, the invention is directed towards a system and method for High Availability (HA) management of Network Functions (NFs) in a network is disclosed. The invention disclosed enables controlled switchover, split-brain scenario handling without duplicate address detection for Internet Protocol version 6 (IPv6), multiple virtual IP management, application process, port monitoring, monitoring of multiple virtual local area network (VLAN).
[00027] Referring to FIG. 1, FIG. 1 illustrates an exemplary block diagram of an environment 100 for High Availability (HA) management of Network Functions (NFs) in a network 106, according to various embodiments of the present invention. The environment 100 includes one or more user devices 104-1, 104-2,…,104-n. At least one user device 104-1 from the one or more user devices 104-1, 104-2,…104-n is communicatively connected to a system 102 via a network 106. The one or more user devices 104-1, 104-2,…,104-n will henceforth collectively and individually be referred to as “the user device 104”. In one embodiment, the user device 104 may include, but are not limited to, a user equipment (UE), a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and/or any other type of computer device with wireless communication or VoIP capabilities.
[00028] In one embodiment, the user device 104 may comprise one or more processors coupled with a memory storing instructions, which are executed by the one or more processors. The user device 104 may comprise memory, such as a volatile memory (e.g., RAM), a non-volatile memory (e.g., disk memory, FLASH memory, EPROMs, etc.), an unalterable memory, and/or other types of memory. In one implementation, the memory might be configured or designed to store a data. The data may pertain to attributes and access rights specifically defined for at least one user device 104.
[00029] In one embodiment, the network 106, may include, by way of example but not limitation, one or more wireless interfaces/protocols such as, for example, 802.11 (Wi-Fi), 802.15 (including Bluetooth™), 802.16 (Wi-Max), 802.22, Cellular standards such as CDMA, CDMA2000, WCDMA, 5G, Radio Frequency (e.g., RFID), Infrared, laser, Near Field Magnetics, etc. The network 106 may also include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fibre optic network, a VOIP or some combination thereof.
[00030] The environment 100 further includes a remote server 108 communicably coupled to the user device 104 via the network 106. The remote server 108 may include by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise, a defence facility, or any other facility that provides content.
[00031] The environment 100 further includes the system 102 communicably coupled to the remote server 108 and the user device 104 via the network 106. The system 102 is configured to manage HA of NFs in the network 106. Further, in alternate embodiments, the system 102 is adapted to be embedded within the remote server 108 or is embedded as an individual entity, without deviating from the scope of the present disclosure.
[00032] Operational and construction features of the system 102 will be explained in detail with respect to the following figures.
[00033] Referring to FIG. 2, FIG. 2, is an exemplary block diagram of the system 102 for the HA management of the NFs in the network 106 (as shown in FIG. 1), according to various embodiments of the present invention. As per the illustrated embodiment, the system 102 includes one or more processors 202, a memory 204, an input/output interface unit 206 and a display 208. The one or more processors 202, hereinafter referred to as the processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. The processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204 of the system 102.
[00034] The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over the network 106. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as Random-Access Memory (RAM), or non-volatile memory such as Electrically Erasable Programmable Read-only Memory (EPROM), flash memory, and the like. In an embodiment, the input/output (I/O) interface unit 206 includes a variety of interfaces, for example, interfaces for data input and output devices, referred to as input/output (I/O) interface unit 206, storage devices, and the like. The input/output (I/O) interface unit 206 may facilitates communication for the system 102. In one embodiment, the input/output (I/O) interface unit 206 may also provide a communication pathway for one or more components of the system 102.
[00035] Further, the processor 202, in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 202. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 202 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for processor 202 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 204 may store instructions that, when executed by the processing resource, implement the processor 202. In such examples, the system 102 may comprise the memory 204 storing the instructions and the processing resource to execute the instructions, or the memory 204 may be separate but accessible to the system 102 and the processing resource. In other examples, the processor 202 may be implemented by electronic circuitry.
[00036] In order for the system 102 to operate as HA management of NFs in the network 106, the processor 202 of the system 102 includes a registration module 220, a NF checking module 225, a NF detection module 230 and a switching module 235 communicably coupled to each other.
[00037] The registration module 220 of the processor 202 is communicably connected to the user device 104 and the remote server 108 via the network 106. Accordingly, the registration module 220 is configured to register, a plurality of NFs hosted in the network 106, the plurality of NFs includes active NFs, standby NFs and georedundant NFs. In one embodiment, the registration of the plurality of NFs in the network 106 is done by assigning a Virtual Internet Protocol (VIP) address to each of the plurality of NFs on the remote server 108. In one embodiment, each of the VIP address aid in situations where multiple remote servers 108 are operating for the same service, for example, accessing a website, and for that, to ensure that if one server fails, the other servers can take over and maintain the availability of the service.
[00038] As per the embodiment, the plurality of NFs is registered based on configuring details available in a configuration file of each NFs. In one embodiment, the configuration file of each NFs stores the configuring details for NF applications that enable users to interact with NF applications in a specific way. For example, if the user is trying to configure a Structured Query Language (SQL), the user can use the configuration file to determine which IP addresses can access a database 245. The configuration file act as a bridge between the user, a program, or an aspect of an operating system. The configuring details includes, but not limited to, NF type, NF name, network addresses, service details, supported interfaces, security credentials, capacity and performance metrics, operational policies, discovery and registration information.
[00039] In one embodiment, the registration process includes receiving registration details of each NFs and subsequently authenticating the respective NF. In one embodiment, subsequent to registration of the plurality of NFs in the network 106. A cluster is created when the plurality of NFs is registered in the network 106. In an embodiment, creating the cluster includes the steps, but not limited to, defining the cluster configuration, initialization and registration of NFs, and cluster management of the NFs. The step defining of cluster configuration refers that each NF has the configuration file including details about its role in the cluster (active, standby, geo-redundant), as well as information about other NFs in the cluster. The step initialization and registration of NFs refers that each NF reads its configuration file upon initialization and registers with the Network Repository Function (NRF). The step cluster management refers that cluster management logic is implemented to handle communication, synchronization, load balancing, and failover processes.
[00040] In one embodiment, the cluster include, but not limited to, the active NFs, the standby NFs and the geo-redundant NFs. The cluster enables communication between each of the active NF, the standby NF and the georedundant NF. In one embodiment, the processors 202 of the system 102 monitors each cluster of the NFs via a Command Line Interface (CLI).
[00041] Further, the NF checking module 225 of the processor 202 is communicably connected to the registration module 220. The NF checking module 220 collects the registration details of the cluster of NFs in the network 106. The NF checking module 225 is configured to check the status of at least one active NF from the cluster of NFs in the real time, upon collection of the registration details of the active NFs, the standby NFs and the geo-redundant NFs. By doing so, the NF checking module 225 of the system 102 is communicated with the remote server 108 for satisfying the one or more pre-defined criteria.
[00042] The NF checking module 225 is configured to check if the status of each active NF from the cluster of NFs meets the one or more pre-defined criteria. In one embodiment, the one or more pre-defined criteria includes one of, but not limited to, a traffic created due to multiple conditions at the active NF, a data replication failure at the active NF, active task being down, stack port being down, interface being down, and the assigned VIP being removed from the active NF. In one embodiment, the one or more pre-defined criteria is stored in the remote server 108.
[00043] In one embodiment, the NF checking module 225 checks the status of at least one of the standby NF and the geo-redundant NF. The NF checking module 225 is configured to check if each of the active NF from the cluster of NFs meet the pre-defined criteria. In one embodiment, if at least one of the active NF does not meets the predefined criteria, the one or more predefined criteria is routed by transmitting the VIP request to one of the standby NF and the geo-redundant NF. Further, the NF detection module 230 checks availability and status of at least one of the standby NF and the geo redundant NF based on the one or more pre-defined criteria. In one embodiment, the availability and the status of the at least one standby NF and the geo-redundant NF meets the one or more pre-defined criteria.
[00044] The switching module 235 of the processor 202 is communicably connected to the NF detection module 230. The switching module 235 is configured to switch to at least one of the standby NF and the geo-redundant NF based on the availability by using plurality of switching techniques.
[00045] In one embodiment, the plurality of switching techniques include, but not limited to, controlled switchover, split-brain scenario handling without duplicate address detection for Internet Protocol version 6 (IPv6), multiple VIP management, NF process, port monitoring, and monitoring of multiple Virtual Local Area Networks (LANs). In one embodiment, the switching module 235 is configured to switch to the at least one available geo-redundant NF from the active NF when at least one of the standby NFs are not available. In one embodiment, the processors 202 of the system 102 is further configured to receive instructions from the user device 104 via the CLI to switch from the at least one active NF, to one of the standby NF and the geo-redundant NF.
[00046] Referring to FIG. 3a, FIG. 3a is an exemplary block diagram of the HA management of the NFs in a network 106 (as shown in FIG. 1) with the first scenario, according to various embodiments of the present system. In one embodiment, the blades 1 and 2 includes a High Availability State Manager-A(HSM-A) 304 and a High Availability State Manager-B (HSM-B) 310. In one embodiment, blade 1 is an active block 308 which includes the first active NF 302 (also referred to NF-active 302) from the cluster of the NFs and the HSM-A 304. In one embodiment, the HSM is a high availability managing the applications in the network 106. In one embodiment, the first NF-active 302 includes an active application. In one embodiment, the HSM-A 304 is an integral part of the first NF-Active 302. In one embodiment, blade 2 is a standby block, standby block includes the standby NF (also referred to NF-standby 312) from the cluster of the NFs and the HSM-B 310. In one embodiment, the HSM-B 310 is an integral part of the NF-standby 312.
[00047] The user device 104 sends an instruction to initiates a failover command. More specifically, the user device 104 sends the instruction to initiates the failover command via a CLI 306 to the HSM-A 304 for high availability managing of the active NF applications. Further, the HSM-A 304 is configured to changing a state of the NF-Active 302 based on the instruction received via the CLI 306. In one embodiment, the HSM-A 304 sends a heartbeat and data replication message to the HSM-B 310. In one embodiment, the heartbeat and data replication message are used to monitor health of the nodes in the networks 106, network interfaces, and also prevent cluster partitioning.
[00048] Further, the HSM-A 304 calls the HSM-B 310 to shift the VIP address. The HSM-B 310 checks the status and the availability of the NF-standby 312 based on the one or more pre-defined criteria (as explained above in FIG. 2). Furthermore, the HSM-B 310 determine the NF-standby 312 is available to switch from the NF-active 302 to the NF-standby 312. Further, the HSM-B 310 sends a “Remove VIP” message to the blade 1. Thereafter, the HSM-B 310 assigns the VIP to the NF-standby 312 and informs the NF-standby 312 about the current state.
[00049] Further, the HSM-B 310 sends a “VIP operation status” message to the HSM-A 304. The HSM-A 304 checks the VIP operation status of the NF-standby 312 and uses one of the switching operation techniques to switch from the NF-active 302 to the NF-standby 312. Thereafter, the HSM-A 304 sends “VIP operation status” message to the CLI 306. In one embodiment, the CLI 306 selects the switchover command, to shift the NF-active 302 to the standby-NF 312. Subsequently, the traffic moves from the NF-active 302 to NF-standby 312.
[00050] Referring to FIG. 3b, FIG. 3b is an exemplary block diagram illustrating a second scenario of the HA management of the NFs in the network 106 (as shown in FIG. 1), according to various embodiments of the present system. The user device 104 is configured to send an instruction to the HSM-A 304 via the CLI 306. In an embodiment, the instruction includes “initiated GR to the spare instance” to check the availability of the NF-Spare 318. Further, the HSM-A 304 prepares a change of the status of the NF-Active 302. The HSM-A 304 sends a heartbeat and data replication message to the High Availability State Manager-C (HSM-C) 316.
[00051] Further, the HSM-A 304 calls the HSM-C 316 to shift the VIP address. The HSM-C 316 checks the status and the availability of the NF-Spare 318 based on the one or more pre-defined criteria (as explained above in FIG. 2). Furthermore, the HSM-C 316 determines the NF-Spare 318 is available to switch from the NF-active 302 to the NF-Spare 318.
[00052] As per above embodiment, the HSM-C 316 sends a “VIP operation status” to the HSM-A 304. The HSM-A 304 checks the VIP operation status of the NF-active 302 and uses one of the switching operation techniques to switch from the NF-Spare 318 to the NF-active 302. Thereafter, the HSM-A 304 send the “VIP operation status” message to the CLI 306. In one embodiment, the CLI 306 selects the switchover command, to shift the NF-active 302 to the NF- Spare 318. Subsequently, the traffic moves from the NF-active 302 to the NF-Spare 318.
[00053] Referring to FIG. 3c. FIG. 3c is an exemplary block diagram of a HA management of NFs in a network 106 (as shown in FIG. 1) with third scenario, according to various embodiments of the present system. The auto switchover process is performed when any issue occurs in the NF-active 302. The HSM-A 304 detects the issue and performs switchover from the NF-active 302 to the NF-standby 312. Further, the HSM-A 304 calls the HSM-B 310 to shift the VIP. Further, the HSM-B 310 checks the status and availability of the NF-standby 312 based on the one or more predefined criteria (as explained above in FIG. 2). In one embodiment, the HSM-B 310 detects the issue and performs switchover from the NF-standby 312 to the NF-spare 318. Further, the HSM-A 304, the HSM-B 310, and the HSM-C 316 perform auto switching process when the NF-active 302 goes down, the NF-active 302 stack port goes down, the NF-active 302 server goes down, the NF-active 302 server interface goes down, the NF-active 302 container goes down, the NF-active 302 is not reachable, VIP is removed from active NF, active server network restarts and active NF is not reachable.
[00054] Referring to FIG. 4, FIG. 4 shows a flow chart of a method for HA management of NFs in the network 106 (as shown in FIG. 1), according to various embodiments of the present system. For the purpose of description, the method 400 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[00055] At step 401, the method 400 includes registering a plurality of NFs hosted in the network 106, wherein the plurality of NFs includes active NFs, standby NFs and georedundant NFs and the VIP is assigned to each of the plurality of NFs. In one embodiment, the plurality of NFs is registered based on one of the configuring details available in a configuration file of each NFs.
[00056] At step 402, method 400 includes creating a cluster. In one embodiment, cluster is created when the plurality of NFs is registered in the network 106. A cluster enables the communication between each of the active NFs, standby NFs and the georedundant NFs.
[00057] At step 403, the method 400 includes checking the status of at least one active NF from the cluster of NFs in the real time, upon collection of the registration details of the active NFs, the standby NFs and the geo-redundant NFs. In one embodiment, the status defines if at least one active NFs meets the pre-defined criteria. In one embodiment, the pre-defined criteria includes traffic created due to multiple conditions, a data replication failure, active task being down, stack port being down, interface being down, the assigned VIP being removed from the active NF.
[00058] At step 404, the method 400 includes detecting the availability of at least one of the standby NF and the georedundant NF, by checking if at least one active NF does not meet the pre-defined criteria. In one embodiment, if at least one of the active NF does not meets the predefined criteria, the one or more predefined criteria is routed by transmitting the VIP request to one of the standby NF and the geo-redundant NF. In one embodiment, the availability and the status of the at least one standby NF and the geo-redundant NF meets the one or more pre-defined criteria.
[00059] At step 404, the method 400 includes the step of switching from each of the active NF to at least one of the standby NF and the geo-redundant NF based on the availability. In one embodiment, the switching process is done by the user device 104 (as shown in FIG. 1) via the CLI 306 to switch from at least one active NF to one of the standby NF and the geo-redundant NF.
[00060] The presently disclosed system can be easily integrated in the existing and wide variety of applications. Further, the system supports multiple platforms such as physical server, virtual machines (VMs), container, cloud platforms, etc., controlled switchover, auto switchback, split-brain scenario handling without duplicate address detection for IPv6, multiple virtual IP management, local and spare HA support, monitoring of application process ID, application stack/server port monitoring, monitoring of server interface status, monitoring of multiple VLANs, server reachability checks, notification on anomaly with environment and one instance of HSM can handle HA of many applications.
[00061] The present invention further discloses a non-transitory computer-readable medium, according to some embodiments of the present disclosure. In some embodiments, the non-transitory computer-readable medium may include register and a plurality of NFs hosted in the network 106 (as shown in FIG. 1). Stored thereon computer-readable instructions that, when executed by one or more processors 202, causes the processor to the plurality of NFs may include active NFs, standby NFs, and georedundant NFs. Check in real time, if each active NF meets a pre-defined criteria. Upon detecting if at least one active NF may do not meet the pre-defined criteria, check, availability of at least one of the standby NF and the geo redundant NF. Switch, to at least one of the standby NF and the geo-redundant NF based on the availability.
[00062] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-4) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[00063] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.

REFERENCE NUMERALS
[00064] System-102
[00065] User devices -104
[00066] Network – 106
[00067] Remote server-108
[00068] Processor-202
[00069] Memory -204
[00070] Input/output (I/O) interface unit 206
[00071] Display-208
[00072] Registration module-220
[00073] NF checking module-225
[00074] NF Detection Module- 230
[00075] Switching module-235
[00076] Database- 245
[00077] NF-Active-302
[00078] High Availability State Manager-A (HSM-A) -304
[00079] CLI – 306
[00080] Active Block-308
[00081] High Availability State Manager-B (HSM-B) -310
[00082] NF-Standby -312
[00083] Standby Block – 311
[00084] Spare Block- 314
[00085] High Availability State Manager-C (HSM-C) – 316
[00086] NF-Spare – 318

,CLAIMS:CLAIMS:
We Claim:
1. A method (400) for High Availability (HA) management of Network Functions (NFs) in a network (106), the method (400) comprises the steps of:
registering (220), by the one or more processors (202), a plurality of NFs hosted in the network (106), wherein the plurality of NFs includes active NFs, standby NFs and georedundant NFs;
checking (225) in real time, by the one or more processors (202), if each active NF meets a pre-defined criteria;
upon detecting (230) if at least one active NF does not meet the pre-defined criteria, checking, by the one or more processors (202), availability of at least one of the standby NF and the geo redundant NF; and
switching (235), by the one or more processors (202), to at least one of the standby NF and the geo-redundant NF based on the availability.

2. The method (400) as claimed in claim 1, wherein the one or more processors (202), registers plurality of NFs in the network by assigning a Virtual IP (VIP) to each of the plurality of NFs.

3. The method (400) as claimed in claim 1, wherein the pre-defined criteria is not met by the active NF when at least one of, traffic created due to multiple conditions at the active NF, a data replication failure at the active NF, active task being down, stack port being down, interface being down, the assigned VIP being removed from the active NF.

4. The method (400) as claimed in claim 1, wherein the step of switching, to at least one of the standby NF and the geo-redundant NF based on the availability, includes:
routing, by the one or more processors (202), one or more pre-defined tasks of the active NF to the at least one of the standby NF and the geo-redundant NF based on availability.

5. The method (400) as claimed in claim 1, wherein the one or more processors (202) is configured to switch to the at least one available geo-redundant NF from the active NF when none of the standby NFs are available.

6. The method (400) as claimed in claim 4, wherein the one or more processors (202) are configured to route one or more predefined tasks from the active NF to one of the standby NF and geo redundant NF, by raising a Virtual Internet Protocol (VIP) request to one of the standby NF and the geo-redundant NF based on availability.

7. The method (400) as claimed in claim 1, wherein the step of switching, by the one or more processors (202), to at least one of the standby NF and the geo-redundant NF based on the availability is based on at least one switching technique.

8. The method (400) as claimed in claim 1, wherein the plurality of NFs are registered based on one of, configuring details in a configuration file of each NF and following a registration process.

9. The method (400) as claimed in claim 8, wherein the registration process includes receiving registration details of each NF and subsequently authenticating the respective NF.

10. The method (400) as claimed in claim 1, wherein the one or more processors (202) is further configured to receive instructions from a user through a User Equipment (UE) (104) to switch from the at least one active NF to one of the standby NF and the geo-redundant NF.

11. The method (400) as claimed in claim 10, wherein the one or more processors (202) receives instructions from the user via a Command Line Interface (CLI) to switch from the active NF to one of the standby NF and the geo-redundant NF.

12. The method (400) as claimed in claim 10, wherein the one or more processors (202) monitors each NF via the CLI (306).

13. The method (400) as claimed in claim 1, wherein subsequent to registration of the plurality of NFs in the network, the one or more processors (202) is configured to:
create a cluster including the active NFs, standby NFs and the georedundant NFs, wherein the cluster enabling communication between each of the active NF, standby NF and the georedundant NF.

14. A system (102) for High Availability (HA) management of Network Functions (NFs) in a network (106), the system (102) comprising:
a registration module (220) configured to, register, a plurality of NFs hosted in the network, wherein the plurality of NFs includes active NFs, standby NFs and georedundant NFs;
a Network Function (NF) checking module (225) configured to, check in real time, if each active NF meets a pre-defined criteria;
upon detecting if at least one active NF does not meet the pre-defined criteria, a NF detection module (230) configured to, check, availability of at least one of the standby NF and the geo redundant NF; and
a switching module (235) configured to, switch, to at least one of the standby NF and the geo-redundant NF based on the availability.

15. The system (102) as claimed in claim 14, wherein the one or more processors (202), registers plurality of NFs in the network by assigning a Virtual IP (VIP) to each of the plurality of NFs.

16. The system (102) as claimed in claim 14, wherein the pre-defined criteria is not met by the active NF when at least one of, traffic created due to multiple conditions at the active NF, a data replication failure at the active NF, active task being down, stack port being down, interface being down, the assigned VIP being removed from the active NF.

17. The system (102) as claimed in claim 14, wherein the step of switching, to at least one of the standby NF and the geo-redundant NF based on the availability, includes:
routing, by the one or more processors (202), one or more pre-defined tasks of the active NF to the at least one of the standby NF and the geo-redundant NF based on availability.

18. The system (102) as claimed in claim 14, wherein the one or more processors (202) is configured to switch to the at least one available geo-redundant NF from the active NF when none of the standby NFs are available.

19. The system (102) as claimed in claim 17, wherein the one or more processors (202) are configured to route one or more predefined tasks from the active NF to one of the standby NF and geo redundant NF, by raising a Virtual Internet Protocol (VIP) request to one of the standby NF and the geo-redundant NF based on availability.

20. The system (102) as claimed in claim 14, wherein the step of switching, by the one or more processors (202), to at least one of the standby NF and the geo-redundant NF based on the availability is based on at least one switching technique.

21. The system (102) as claimed in claim 14, wherein the plurality of NFs are registered based on one of, configuring details in a configuration file of each NF and following a registration process.

22. The system (102) as claimed in claim 21, wherein the registration process includes receiving registration details of each NF and subsequently authenticating the respective NF.

23. The system (102) as claimed in claim 14, wherein the one or more processors (202) is further configured to receive instructions from a user through a User Equipment (UE) (104) to switch from the at least one active NF to one of the standby NF and the geo-redundant NF.

24. The system (102) as claimed in claim 23, wherein the one or more processors (202) receives instructions from the user via a Command Line Interface (CLI) to switch from the active NF to one of the standby NF and the geo-redundant NF.

25. The system (102) as claimed in claim 23, wherein the one or more processors (202) monitors each NF via the CLI (306).

26. The system (102) as claimed in claim 14, wherein subsequent to registration of the plurality of NFs in the network, the one or more processors (202) is configured to:
create a cluster including the active NFs, standby NFs and the georedundant NFs, wherein the cluster enabling communication between each of the active NF, standby NF and the georedundant NF.