Method and system for maintaining application-level high availability (HA) in a network environment

Abstract

The present disclosure relates to a method and a system for maintaining application-level HA in a network environment. The method encompasses determining network functions (NFs) to be configured for HA; determining one or more interfaces of the one or more NFs that are serving data traffic; modifying kernel level parameters such that active Duplicate Address Detection DAD parameters for each of the one or more interfaces of the one or more NFs is disabled; generating for each of the one or more interfaces of the one or more NFs, a virtual IP (VIP) address; and confirming for the one or more interfaces of the one or more NFs, if the corresponding DAD parameter is disabled, based on an interaction of the corresponding VIP addresses with data traffic.

Description

METHOD AND SYSTEM FOR MAINTAINING APPLICATION-LEVEL HIGH AVAILABILITY (HA) IN A NETWORK ENVIRONMENT FIELD OF THE INVENTION

[0001] The present disclosure generally relates to wireless communication systems. More particularly, embodiments of the present disclosure relate to a method and system for maintaining application-level High Availability (HA) in a network environment. 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] In the current existing solutions, High Availability (HA) state manager (SM) maintains an application level High Availability using Virtual internet protocol (VIP) failure. Thereby, at a given time VIP may be present / configured on the Active application instance. Also, in the current existing solution, by default, duplicate address detection (DAD) is enabled at operating system (OS) kernel level. So, when this DAD is enabled, it is found that VIP failure usually takes more than 3 seconds to configure the VIP on the standby application instance. Hence, when active instance goes down, this leads to a packet drop i.e. a request outage for 3 seconds or more. Thismuch time is taken by the DAD module to check for any IP duplicity in network before configuring the VIP.

[0005] Thus, there exists an imperative need in the art to minimize the outage and reduce the VIP failover time. In the present disclosure, this can be addressed by disabling the DAD config change. SUMMARY

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

[0007] An aspect of the present disclosure may relate to a method for maintaining application- level High Availability (HA) in a network environment. The method includes determining, by a determining unit at a state manager (SM) module, one or more network functions (NFs) to be configured for HA. The method further includes determining, by the determining unit at the SM module, one or more interfaces of the one or more NFs that are serving data traffic. The method further includes modifying, by a modifying unit at the SM module, kernel level parameters, such that active Duplicate Address Detection DAD parameters for each of the one or more interfaces of the one or more NFs is disabled. The method further includes generating, by a generating unit at the SM module, for each of the one or more interfaces of the one or more NFs, a virtual IP (VIP) address. The method includes confirming, by a processing unit at the SM module, for the one or more interfaces of the one or more NFs, if the corresponding DAD parameter is disabled, based on an interaction of the corresponding VIP addresses with data traffic.

[0008] In an exemplary aspect of the present disclosure, the method further comprises uploading, by the processing unit at the SM module, the modified kernel level parameters to enable application of the disabled DAD parameters for each of the one or more interfaces of the one or more NFs.

[0009] In an exemplary aspect, the generated VIP address of each of the one or more interfaces of the one or more NFs is based on a corresponding data traffic at each of the one or more interfaces of the one or more NFs.

[0010] In an exemplary aspect, the one or more NFs are selected from a set of NFs in the network environment, and wherein the one or more NFs are selected based on being configured with an active DAD parameter.

[0011] In an exemplary aspect, each of the generated VIP address is adapted to serve data traffic.

[0012] Another aspect of the present disclosure may relate to a system for maintaining application- level High Availability (HA) in a network environment. The system comprises a determining unit configured to determine one or more network functions (NFs) to be configured for HA. The determining unit is further configured to determine one or more interfaces of the one or more NFs that are serving data traffic. The system further comprises a modifying unit configured to modify kernel level parameters, such that active Duplicate Address Detection (DAD) parameters for each of the one or more interfaces of the one or more NFs is disabled. The system further comprises a generating unit configured to generate for each of the one or more interfaces of the one or more NFs, a virtual IP (VIP) address. The system further comprises a processing unit configured to confirm for the one or more interfaces of the one or more NFs, if the corresponding DAD parameter is disabled, based on an interaction of the corresponding VIP addresses with data traffic.

[0013] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for maintaining application-level High Availability (HA) in a network environment, the instructions include executable code which, when executed by one or more units of a system, causes a determining unit to determine one or more network functions (NFs) to be configured for HA. The instructions when executed further causes the determining unit to determine one or more interfaces of the one or more NFs that are serving data traffic. The instructions when executed further causes a modifying unit to modify kernel level parameters, such that active Duplicate Address Detection (DAD) parameters for each of the one or more interfaces of the one or more NFs is disabled. The instructions when executed further causes a generating unit to generate for each of the one or more interfaces of the one or more NFs, a virtual IP (VIP) address. The instructions when executed further causes a processing unit to confirm for the one or more interfaces of the one or more NFs, if the corresponding DAD parameter is disabled, based on an interaction of the corresponding VIP addresses with data traffic. OBJECTS OF THE INVENTION

[0014] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0015] It is an object of the present disclosure to provide a system and a method for detecting duplicate address based on configuration change.

[0016] It is yet another object of the present disclosure to provide a solution to minimize the outage and reduce the VIP failover time.DESCRIPTION OF THE DRAWINGS

[0017] 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. Also, the embodiments shown in the figures are not to be construed as 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.

[0018] FIG.1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.

[0019] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.

[0020] FIG. 3 illustrates an exemplary block diagram of a system for maintaining application- level High Availability (HA) in a network environment, in accordance with exemplary implementations of the present disclosure.

[0021] FIG. 4 illustrates a method flow diagram for maintaining application-level High Availability (HA) in a network environment, in accordance with exemplary implementations of the present disclosure.

[0022] FIG. 5 illustrates a process diagram for maintaining application-level High Availability (HA) in a network environment, in accordance with exemplary implementations of the present disclosure.

[0023] FIG. 6 illustrates a process flow diagram for maintaining application-level High Availability (HA) in a network environment, in accordance with exemplary implementations of the present disclosure.

[0024] The foregoing shall be more apparent from the following more detailed description of the disclosure. DETAILED DESCRIPTION

[0025] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.

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

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

[0028] Also, it is noted that individual embodiments may be described as a process 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 included in a figure.

[0029] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.

[0030] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for 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 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.

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

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

[0033] 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 each other, which also includes the methods, functions, or procedures that may be called.

[0034] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a 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.

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

[0036] As used herein, Duplicate Address Detection DAD parameters are the parameters by which a node determines that an IPv6 address considered for use is not already in use by a neighbouring node (equivalent to the use of gratuitous ARP frames in IPv4). The DAD parameters consist of sending a neighbour discovery whenever the platform is assigned a new IP address, asking for a neighbour with the same address.

[0037] As used herein, virtual IP (VIP) is an IP address used to represent a service or application rather than a specific physical device, enabling flexible network management. VIPs facilitate load balancing by directing traffic to multiple servers, enhance scalability and flexibility in Network Function Virtualization (NFV) by allowing virtual functions to be dynamically assigned, and ensure high availability by enabling seamless failover to backup systems. This abstraction of IP addresses from physical hardware improves network efficiency, reliability, and adaptability.

[0038] 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 method and system for maintaining application- level High Availability (HA) in a network environment.

[0039] FIG.1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network architecture

[0100] includes a user equipment (UE)

[0102] , a radio access network (RAN)

[0104] , an access and mobility management function (AMF)

[0106] , a Session Management Function (SMF)

[0108] , a Service Communication Proxy (SCP)

[0110] , an Authentication Server Function (AUSF)

[0112] , a Network Slice Specific Authentication and Authorization Function (NSSAAF)

[0114] , a Network Slice Selection Function (NSSF)

[0116] , a Network Exposure Function (NEF)

[0118] , a Network Repository Function (NRF)

[0120] , a PolicyControl Function (PCF)

[0122] , a Unified Data Management (UDM)

[0124] , an application function (AF)

[0126] , a User Plane Function (UPF)

[0128] , a data network (DN)

[0130] , wherein all the 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.

[0040] Radio Access Network (RAN)

[0104] is the part of a mobile telecommunications system that connects user equipment (UE)

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

[0041] Access and Mobility Management Function (AMF)

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

[0042] Session Management Function (SMF)

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

[0043] Service Communication Proxy (SCP)

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

[0044] Authentication Server Function (AUSF)

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

[0045] Network Slice Specific Authentication and Authorization Function (NSSAAF)

[0114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.

[0046] Network Slice Selection Function (NSSF)

[0116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.

[0047] Network Exposure Function (NEF)

[0118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.

[0048] Network Repository Function (NRF)

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

[0049] Policy Control Function (PCF)

[0122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.

[0050] Unified Data Management (UDM)

[0124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.

[0051] Application Function (AF)

[0126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.

[0052] User Plane Function (UPF)

[0128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.

[0053] Data Network (DN)

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

[0054] FIG.2 illustrates an exemplary block diagram of a computing device

[0200] (also referred to herein as computer system

[0200] ) 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

[0200] may also implement a method for maintaining application-level High Availability (HA) in a network environment. utilising the system. In another implementation, the computing device

[0200] itself implements the method for maintaining application-level High Availability (HA) in a network environment using one or more units configured within the computing device

[0200] , wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.

[0055] The computing device

[0200] may include a bus

[0202] or other communication mechanism for communicating information, and a hardware processor

[0204] coupled with bus

[0202] for processing information. The hardware processor

[0204] may be, for example, a general-purpose microprocessor. The computing device

[0200] may also include a main memory

[0206] , such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus

[0202] for storing information and instructions to be executed by the processor

[0204] . The main memory

[0206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor

[0204] . Such instructions, when stored in non-transitory storage media accessible to the processor

[0204] , render the computing device

[0200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device

[0200] further includes a read only memory (ROM)

[0208] or other static storage device coupled to the bus

[0202] for storing static information and instructions for the processor

[0204] .

[0056] A storage device

[0210] , such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus

[0202] for storing information and instructions. The computing device

[0200] may be coupled via the bus

[0202] to a display

[0212] , such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device

[0214] , including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus

[0202] for communicating information and command selections to the processor

[0204] . Another type of user input device may be a cursor controller

[0216] , such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor

[0204] , and for controlling cursor movement on the display

[0212] . This 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.

[0057] The computing device

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

[0200] causes or programs the computing device

[0200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device

[0200] in response to the processor

[0204] executing one or more sequences of one or more instructions contained in the main memory

[0206] . Such instructions may be read into the main memory

[0206] from another storage medium, such as the storage device

[0210] . Execution of the sequences of instructions contained in the main memory

[0206] causes the processor

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

[0058] The computing device

[0200] also may include a communication interface

[0218] coupled to the bus

[0202] . The communication interface

[0218] provides a two-way data communication coupling to a network link

[0220] that is connected to a local network

[0222] . For example, thecommunication interface

[0218] 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 telephone line. As another example, the communication interface

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

[0218] sends and receives electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information.

[0059] The computing device

[0200] can send messages and receive data, including program code, through the network(s), the network link

[0220] and the communication interface

[0218] . In the Internet example, a server

[0230] might transmit a requested code for an application program through the Internet

[0228] , the ISP

[0226] , the local network

[0222] , host

[0224] and the communication interface

[0218] . The received code may be executed by the processor

[0204] as it is received, and / or stored in the storage device

[0210] , or other non-volatile storage for later execution.

[0060] The computing device

[0200] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of computing device

[0200] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems. The devices may operate independently or as part of a network and can perform a variety of tasks such as data storage, retrieval, and analysis. Additionally, computing device

[0200] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications.

[0061] Referring to FIG. 3, an exemplary block diagram of a system

[0300] for maintaining application-level High Availability (HA) in a network environment, is shown, in accordance with the exemplary implementations of the present disclosure. The system

[0300] comprises at least one determining unit

[0302] , at least one modifying unit

[0304] , at least one generating unit

[0306] , and at least one processing unit

[0308] . Also, all of the components / units of the system

[0300] are assumed to be connected to 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. Also, in FIG.3 only a few units are shown, however, the system

[0300] may comprise multiple such units or the system

[0300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system

[0300] may be present in a user device to implement the features of the present disclosure. The system

[0300] may be a part of the user device / or may be independent of but in communication with the user device (may alsoreferred herein as a UE). In another implementation, the system

[0300] may reside in a server or a network entity. In yet another implementation, the system

[0300] may reside partly in the server / network entity and partly in the user device.

[0062] The system

[0300] is configured for maintaining application-level High Availability (HA) in a network environment, with the help of the interconnection between the components / units of the system

[0300] .

[0063] The system

[0300] comprises a determining unit

[0302] configured to determine one or more network functions (NFs) to be configured for high availability (HA).

[0064] The determining unit

[0302] determines one or more network functions (NFs) that are to be configured for high availability (HA). In an exemplary aspect, the one or more NFs may include such as but not limited only to the access and mobility management function (AMF)

[0106] , the session management function (SMF)

[0108] , the network exposure function (NEF)

[0118] etc. For example, in a 5G core network, several NFs such as the AMF

[0106] or the SMF

[0108] are responsible for handling essential tasks like user authentication, mobility management, and session handling. The determining unit

[0302] evaluates the one or more NFs based on specific a set of criteria, such as their role in the network, the volume of traffic they handle, or their susceptibility to failures, and then decides which of these functions need to be configured for HA.

[0065] In an exemplary aspect, the one or more NFs are selected from a set of NFs in the network environment, and wherein the one or more NFs are selected based on being configured with an active DAD parameter.

[0066] In an exemplary aspect, the determining unit

[0302] selects one or more NFs from the set of NFs in a network environment. The set of NFs may include such as but not limited to the access and mobility management function (AMF)

[0106] , the session management function (SMF)

[0108] , the network exposure function (NEF)

[0118] , policy control function

[0122] etc.

[0067] In an exemplary aspect, the one or more NFs are selected based on Duplicate Address Detection (DAD) parameters. In an exemplary aspect, the DAD parameters refer to the settings and configurations within an operating system's network stack that control the process of verifying the uniqueness of an IP address before it is assigned to a network interface. DAD is a technique that facilitates in preventing IP address conflicts within a network, ensuring that no two devices are inadvertently assigned the same IP address, which could cause communication failures or data loss. When a new IP address is assigned, DAD parameters dictate how the system checks for the presence of that address on the network—typically by sending probe messages and waiting for aresponse to confirm that the address is not already in use. In cases where quick failover and high availability are essential, such as in telecommunications networks, DAD can introduce delays. Disabling or modifying DAD parameters can minimize the delays, allowing for faster IP address assignment and reduced service interruption during failover events.

[0068] The determining unit

[0302] is further configured to determine one or more interfaces of the one or more NFs that are serving data traffic.

[0069] The determining unit

[0302] determines the one or more interfaces associated with the one or more NFs that are actively handling / serving data traffic. This helps in configuring these interfaces properly for HA. In an exemplary aspect, the one or more interfaces may include such as but not limited only to N1 interface which is the interface between the UE

[0102] and the AMF

[0106] , N2 interface which is the interface between the RAN

[0104] and the AMF

[0106] , N3 interface which is the interface between the RAN

[0104] and the UPF

[0128] , N4 interface which is the interface between the SMF

[0108] and the UPF

[0128] etc. In a network environment, each Network Function (NF) may have one or more interfaces that handle various types of communication and data transmission. The one or more interfaces facilitates in managing the flow of data packets between different parts of the network and such that the services provided by the one or more NFs are available to users and other network elements. For example, in a 5G core network, an NF like the User Plane Function (UPF) might have several interfaces, each responsible for different tasks such as routing user data, managing QoS (Quality of Service), or connecting with external networks. The determining unit

[0302] determines which of these interfaces are actively involved in serving data traffic. The determination facilitates in performing tasks like configuring High Availability (HA) or modifying kernel-level settings, such as disabling Duplicate Address Detection (DAD). For example, if the determining unit

[0302] identifies that the NF interface handling user data traffic is critical, the system will prioritize configuring the NF interface for HA to minimize any potential data loss or service disruption during a failover event.

[0070] The system

[0300] further comprises a modifying unit

[0304] which is configured to modify kernel level parameters, such that active Duplicate Address Detection (DAD) parameters for each of the one or more interfaces of the one or more NFs is disabled. In an exemplary aspect, the modifying unit

[0304] is connected to the determining unit

[0302] .

[0071] The modifying unit

[0304] modifies the kernel level parameters, which are the parameters that enables modification at the highest level in an operating system (OS). The modified kernel parameters arbitrate access to protected hardware and controls how limited resources such as running time on the CPU and physical memory pages are used by processes on the system

[0300] .The modification, by the modifying unit

[0304] of the kernel level parameters occurs so that the active DAD parameters of the one or more is disabled. By disabling active DAD, the modifying unit

[0304] avoid conflicts when configuring HA solutions involving virtual IPs (VIPs). By disabling DAD, the system bypasses the time-consuming checks typically performed to detect duplicate IP addresses. The modification significantly reduces the time required to reassign a virtual IP address during failover, thus minimizing service disruption. For example, in a high- availability setup where the system needs to switch the virtual IP from an active to a standby instance of a Network Function (NF) like the Access and Mobility Management Function (AMF), the usual DAD process could delay this switchover by several seconds. During this period, the service might experience packet loss or temporary unavailability. The modifying unit

[0304] prevents this delay by disabling DAD on the relevant interfaces, ensuring that the VIP (Virtual IP) can be reassigned almost instantly, thus maintaining continuous service availability.

[0072] The system

[0300] further comprises a generating unit

[0306] which is configured to generate for each of the one or more interfaces of the one or more NFs, the virtual IP (VIP) address. In an exemplary aspect, the generating unit

[0306] is connected to the modifying unit

[0304] .

[0073] For each of the one or more interfaces of the one or more NFs identified, this generating unit

[0306] generates the virtual IP (VIP) address. In an exemplary aspect, the VIP is used in HA setups to allow multiple network functions to appear as a single entity, providing failover capabilities. If one network function fails, another can take overusing the same VIP.

[0074] In an exemplary aspect, the generated VIP address of each of the one or more interfaces of the one or more NFs is based on a corresponding data traffic at each of the one or more interfaces of the one or more NFs.

[0075] In an exemplary aspect, the generated Virtual IP (VIP) address for each one or more interfaces of one or more network functions (NFs) is determined based on the data traffic observed at the one or more interface. This means that the VIP address is not static but is instead assigned or adjusted according to the specific patterns and requirements of the traffic flowing through each interface. By aligning the VIP address with the data traffic, the system

[0300] ensures that the virtual IPs are configured to handle the traffic load and provide consistent access to the network functions, thereby enhancing the overall efficiency and reliability of the High Availability (HA) setup.

[0076] In an exemplary aspect, each of the generated VIP address is adapted to serve data traffic.

[0077] In an exemplary aspect, each generated Virtual IP (VIP) address is adapted to handle the specific data traffic needs of its corresponding network function interface. This adaptation ensuresthat the VIP address is configured to effectively manage and route incoming data traffic, aligning with the traffic patterns and load characteristics of the interface. By doing this, the VIP address supports seamless and efficient data handling, contributing to the overall stability and performance of the High Availability (HA) setup.

[0078] In an exemplary aspect, the VIP allows traffic to be dynamically rerouted to different physical servers or network functions (NFs) without requiring users or external systems to know the actual IP addresses of these components. For example, in a 5G network, an NF such as the User Plane Function (UPF) might have multiple interfaces managing different types of data traffic. The generating unit

[0306] assigns a VIP to each of these interfaces, enabling seamless failover and load balancing. For example, suppose a UPF is handling user data on one interface and signalling traffic on another. The generating unit

[0306] will generate separate VIPs for both interfaces. In the event of a failure in the active instance of the UPF, the VIPs can be quickly reassigned to a standby instance, ensuring that data continues to flow without interruption. The process thus facilitates in maintaining high availability and minimizing downtime, as the VIPs abstract the underlying network changes from the users and other network functions.

[0079] The system

[0300] further comprises a processing unit

[0308] which is configured to confirm for the one or more interfaces of the one or more NFs, if the corresponding DAD parameter is disabled, based on an interaction of the corresponding VIP addresses with data traffic. In an exemplary aspect, the processing unit

[0308] is connected to the generating unit

[0306] .

[0080] The processing unit

[0308] confirms whether the DAD parameter has been successfully disabled for the one or more interfaces of the one or more NFs and whether the VIP addresses are functioning as expected. It does this by monitoring how the Virtual IP (VIP) addresses assigned to these interfaces interact with the data traffic. The processing unit

[0308] checks if the VIP addresses are functioning correctly and not causing conflicts, which would indicate that the DAD parameters have been properly disabled. In an exemplary aspect, successful interaction of VIP addresses with data traffic confirms that the system's configuration is effective, and that the HA setup is operating as intended.

[0081] After the DAD parameters have been modified and disabled by the modifying unit

[0304] , the processing unit

[0308] conducts a verification process. The verification process includes monitoring the interaction of the VIP addresses with the ongoing data traffic. For example, when a VIP is assigned to an interface and begins routing traffic, the processing unit

[0308] checks to see if there are any signs of IP conflict or other issues that DAD would typically prevent. The absence of such issues indicates that the DAD parameter has been successfully disabled and that the systemis functioning correctly without unnecessary delays. For example, a Network Function (NF) such as the Session Management Function (SMF) has multiple interfaces serving different types of traffic. Each of these interfaces would have had its DAD parameters disabled to ensure rapid failover. The processing unit

[0308] would monitor these interfaces as they start handling data via their newly assigned VIPs. If the data traffic flows smoothly without any interruptions or conflicts, the processing unit confirms that the DAD parameters are indeed disabled and that the VIPs are functioning properly.

[0082] It would be appreciated by the person skilled in the art that the confirmation provides assurance that the intended optimizations (disabling DAD to expedite VIP assignment) have been correctly implemented. It also ensures that the network remains stable and reliable, even after such significant configuration changes. If the processing unit

[0308] detects any anomalies, it may trigger alerts or perform corrective actions to address potential issues before they impact service availability.

[0083] The processing unit

[0308] is further configured to upload the modified kernel level parameters to enable application of the disabled DAD parameters for each of the one or more interfaces of the one or more NFs.

[0084] The processing unit

[0308] uploads the modified kernel level parameters to manage the configuration of disable Duplicate Address Detection (DAD) parameters for each of the one or more interfaces of the one or more NFs. In an exemplary aspect, the modified kernel level parameters are uploaded such that changes may take place immediately to minimize the VIP failover time from for example, 3 sec to 1 sec. This stops excessive packet drops during heavy load specially in production servers. For example, if the DAD parameter were disabled on interfaces handling critical data traffic for a Network Function like the Access and Mobility Management Function (AMF), the processing unit

[0308] would upload these changes so that they are recognized and implemented by the system’s operating environment.

[0085] By uploading these modified parameters, the processing unit

[0308] ensures that the changes are persistent and that the network operates according to the newly configured settings. This step is essential to maintain consistency across the network and to ensure that all interfaces are aligned with the high-availability requirements. In a large-scale network, where numerous NFs and interfaces are involved, this automated uploading process helps streamline the deployment of configuration changes, reducing the likelihood of errors and ensuring that all components are properly synchronized.

[0086] For example, once the processing unit

[0308] uploads the modified parameters, any subsequent reboots or resets of the network devices will retain the configuration where DAD is disabled, allowing the system to consistently benefit from the faster VIP assignment and reduced failover times. This process is crucial for maintaining the network’s performance, particularly in high-availability environments where every second of downtime can lead to significant service disruption.

[0087] Referring to FIG.4, an exemplary method flow diagram

[0400] for maintaining application- level High Availability (HA) in a network environment in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method

[0400] is performed by the system

[0300] . Further, in an implementation, the system

[0300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG.4, the method

[0400] starts at step

[0402] .

[0088] At step 404, the method

[0400] comprises determining, by a determining unit

[0302] at a state manager (SM) module [300a], one or more network functions (NFs) to be configured for HA.

[0089] The determining unit

[0302] determines one or more network functions (NFs) that are to be configured for high availability (HA). In an exemplary aspect, the one or more NFs may include such as but not limited only to the access and mobility management function (AMF)

[0106] , the session management function (SMF)

[0108] , the network exposure function (NEF)

[0118] etc. For example, in a 5G core network, several NFs such as the AMF

[0106] or the SMF

[0108] are responsible for handling essential tasks like user authentication, mobility management, and session handling. The determining unit

[0302] evaluates the one or more NFs based on specific a set of criteria, such as their role in the network, the volume of traffic they handle, or their susceptibility to failures, and then decides which of these functions need to be configured for HA.

[0090] In an exemplary aspect, the one or more NFs are selected from a set of NFs in the network environment, and wherein the one or more NFs are selected based on being configured with an active DAD parameter.

[0091] In an exemplary aspect, the determining unit

[0302] selects one or more NFs from the set of NFs in a network environment. The set of NFs may include such as but not limited to the access and mobility management function (AMF)

[0106] , the session management function (SMF)

[0108] , the network exposure function (NEF)

[0118] , policy control function

[0122] etc.

[0092] In an exemplary aspect, the one or more NFs are selected based on Duplicate Address Detection (DAD) parameters. In an exemplary aspect, the DAD parameters refer to the settingsand configurations within an operating system's network stack that control the process of verifying the uniqueness of an IP address before it is assigned to a network interface. DAD is a technique that facilitates in preventing IP address conflicts within a network such that no two devices are inadvertently assigned the same IP address, which could cause communication failures or data loss. When a new IP address is assigned, DAD parameters dictate how the system checks for the presence of that address on the network—typically by sending probe messages and waiting for a response to confirm that the address is not already in use. In cases where quick failover and high availability are essential, such as in telecommunications networks, DAD can introduce delays. Disabling or modifying DAD parameters can minimize the delays, allowing for faster IP address assignment and reduced service interruption during failover events.

[0093] At step 406, the method

[0400] comprises determining, by the determining unit

[0302] at the SM module [300a], one or more interfaces of the one or more NFs that are serving data traffic.

[0094] The determining unit

[0302] determines the one or more interfaces associated with the one or more NFs that are actively handling / serving data traffic. This helps in configuring these interfaces properly for HA. In an exemplary aspect, the one or more interfaces may include such as but not limited only to N1 interface which is the interface between the UE

[0102] and the AMF

[0106] , N2 interface which is the interface between the RAN

[0104] and the AMF

[0106] , N3 interface which is the interface between the RAN

[0104] and the UPF

[0128] , N4 interface which is the interface between the SMF

[0108] and the UPF

[0128] etc. In a network environment, each Network Function (NF) may have one or more interfaces that handle various types of communication and data transmission. The one or more interfaces facilitates in managing the flow of data packets between different parts of the network and such that the services provided by the one or more NFs are available to users and other network elements. For example, in a 5G core network, an NF like the User Plane Function (UPF) might have several interfaces, each responsible for different tasks such as routing user data, managing QoS (Quality of Service), or connecting with external networks. The determining unit

[0302] determines which of these interfaces are actively involved in serving data traffic. The determination facilitates in performing tasks like configuring High Availability (HA) or modifying kernel-level settings, such as disabling Duplicate Address Detection (DAD). For example, if the determining unit

[0302] identifies that the NF interface handling user data traffic is critical, the system will prioritize configuring the NF interface for HA to minimize any potential data loss or service disruption during a failover event.

[0095] At step 408, the method

[0400] comprises modifying, by a modifying unit

[0304] at the SM module [300a], kernel level parameters, such that active Duplicate Address Detection DAD parameters for each of the one or more interfaces of the one or more NFs is disabled.

[0096] The modifying unit

[0304] modifies the kernel level parameters, which are the parameters that enables modification at the highest level in an operating system (OS). The modified kernel parameters arbitrate access to protected hardware and controls how limited resources such as running time on the CPU and physical memory pages are used by processes on the system

[0300] . The modification, by the modifying unit

[0304] of the kernel level parameters occurs so that the active DAD parameters of the one or more is disabled. By disabling active DAD, the modifying unit

[0304] avoid conflicts when configuring HA solutions involving virtual IPs (VIPs). By disabling DAD, the system bypasses the time-consuming checks typically performed to detect duplicate IP addresses. The modification significantly reduces the time required to reassign a virtual IP address during failover, thus minimizing service disruption. For example, in a high- availability setup where the system needs to switch the virtual IP from an active to a standby instance of a Network Function (NF) like the Access and Mobility Management Function (AMF), the usual DAD process could delay this switchover by several seconds. During this period, the service might experience packet loss or temporary unavailability. The modifying unit

[0304] prevents this delay by disabling DAD on the relevant interfaces such that the VIP (Virtual IP) can be reassigned almost instantly, thus maintaining continuous service availability.

[0097] At step 410, the method

[0400] comprises generating, by a generating unit

[0306] at the SM module [300a], for each of the one or more interfaces of the one or more NFs, a virtual IP (VIP) address.

[0098] For each of the one or more interfaces of the one or more NFs identified, this generating unit

[0306] generates the virtual IP (VIP) address. In an exemplary aspect, the VIP is used in HA setups to allow multiple network functions to appear as a single entity, providing failover capabilities. If one network function fails, another can take overusing the same VIP.

[0099] In an exemplary aspect, the generated VIP address of each of the one or more interfaces of the one or more NFs is based on a corresponding data traffic at each of the one or more interfaces of the one or more NFs.

[0100] In an exemplary aspect, the generated Virtual IP (VIP) address for each one or more interfaces of one or more network functions (NFs) is determined based on the data traffic observed at the one or more interface. This meansthat the VIP address is not static but is instead assigned or adjusted according to the specific patterns and requirements of the traffic flowing through each interface. By aligning the VIP address with the data traffic, the system

[0300] enables that the virtual IPs are configured to handle the traffic load and provide consistent access to the network functions, thereby enhancing the overall efficiency and reliability of the High Availability (HA) setup.

[0101] In an exemplary aspect, each of the generated VIP address is adapted to serve data traffic.

[0102] In an exemplary aspect, the VIP allows traffic to be dynamically rerouted to different physical servers or network functions (NFs) without requiring users or external systems to know the actual IP addresses of these components. For example, in a 5G network, an NF such as the User Plane Function (UPF) might have multiple interfaces managing different types of data traffic. The generating unit

[0306] assigns a VIP to each of these interfaces, enabling seamless failover and load balancing. For example, suppose a UPF is handling user data on one interface and signalling traffic on another. The generating unit

[0306] will generate separate VIPs for both interfaces. In the event of a failure in the active instance of the UPF, the VIPs can be quickly reassigned to a standby instance, such that data continues to flow without interruption. The process thus facilitates in maintaining high availability and minimizing downtime, as the VIPs abstract the underlying network changes from the users and other network functions.

[0103] At step 412, the method

[0400] comprises confirming, by a processing unit

[0308] at the SM module [300a], for the one or more interfaces of the one or more NFs, if the corresponding DAD parameter is disabled, based on an interaction of the corresponding VIP addresses with data traffic.

[0104] The processing unit

[0308] confirms whether the DAD parameter has been successfully disabled for the one or more interfaces of the one or more NFs and whether the VIP addresses are functioning as expected. The processing unit

[0308] monitors how the Virtual IP (VIP) addresses assigned to these interfaces interact with the data traffic. The processing unit

[0308] checks if the VIP addresses are functioning correctly and not causing conflicts, which would indicate that the DAD parameters have been properly disabled. In an exemplary aspect, successful interaction of VIP addresses with data traffic confirms that the system's configuration is effective, and that the HA setup is operating as intended.

[0105] The method

[0400] further comprises uploading, by the processing unit

[0308] at the SM module [300a], the modified kernel level parameters to enable application of the disabled DAD parameters for each of the one or more interfaces of the one or more NFs.

[0106] The processing unit

[0308] uploads, at the state manager (SM) module [300a], the modified kernel level parameters to manage the configuration of disable Duplicate Address Detection (DAD) parameters for each of the one or more interfaces of the one or more NFs. In an exemplary aspect, the modified kernel level parameters are uploaded such that changes may take place immediately to minimize the VIP failover time from for example, 3 sec to 1 sec. This stops excessive packet drops during heavy load specially in production servers.

[0107] At step 414, the method

[0400] terminates.

[0108] Referring to FIG.5, an exemplary process flow

[0500] diagram for maintaining application- level High Availability (HA) in a network environment, is shown, in accordance with the exemplary implementations of the present disclosure.

[0109] At step 502, the process includes the State Manager (SM) module [300a] actively monitoring the Virtual IP (VIP) associated with one or more network functions (NFs). This monitoring includes continuously overseeing the status and performance of the VIP to ensure it remains functional and available for routing traffic. The SM [300a] checks the availability of the VIP to confirm it is correctly assigned to the active instance of the NF and is accessible to other network elements. Additionally, the process may include assessing the VIP's performance to ensure it efficiently handles data traffic without delays or interruptions. The SM [300a] also verifies that the VIP is ready for failover, meaning it can be quickly and smoothly transferred to a standby instance of the NF if the active instance fails.

[0110] At step 504, the process includes implementing the Duplicate Address Detection (DAD) configuration change on the active application instance. The step includes disabling the DAD mechanism at the kernel level for the active network interfaces that are handling traffic. The purpose of this change is to eliminate the delay typically introduced by DAD when assigning a Virtual IP (VIP) to an interface. By disabling DAD, the active application instance can quickly assume the VIP without performing the usual checks for IP address duplication, thereby significantly reducing the failover time in the event of a system failure.

[0111] At step 506, the process includes configuring the standby application instance with the Duplicate Address Detection (DAD) setting disabled. By disabling DAD on the standby instance, the system avoids the time-consuming process of checking for duplicate IP addresses when the Virtual IP (VIP) is reassigned to the standby instance. The configuration change significantly reduces the failover time, enabling the standby instance to quickly assume the active role and continue handling data traffic with minimal disruption.

[0112] At step 508, the process includes the assignment or reassignment of the Virtual IP (VIP) to the appropriate network function (NF) instance, based on the current network state. The VIP serves as a stable endpoint for traffic, abstracting the underlying physical or virtual instances of the NF. When an active NF instance fails or is taken offline for maintenance, step 508 includes reassigning the VIP to a standby or backup instance. The process further includes confirming that the VIP is properly configured and operational on the new instance, allowing it to handle incoming and outgoing traffic effectively, thereby minimizing downtime and maintaining service reliability.

[0113] At step 510, the process includes handling requests from other nodes to the application endpoint. The step 510 further includes the application receiving and processing incoming data or service requests that are directed to it from various nodes within the network. These nodes could be other network functions, user devices, or external systems that rely on the application to perform specific tasks or provide certain services.

[0114] Referring to FIG.6, an exemplary process

[0600] diagram for maintaining application-level High Availability (HA) in a network environment in accordance with exemplary implementations of the present disclosure is shown.

[0115] At step 602, the process

[0600] includes selecting the 5G Network Function (NF) where the Duplicate Address Detection (DAD) configuration change is expected. The selection process includes determining which NF within the 5G network requires the DAD configuration change, often based on factors such as the NF's role in handling critical traffic, its current performance, or its need for faster failover capabilities. For example, an NF like the User Plane Function (UPF), which is responsible for managing user data traffic, might be selected because disabling DAD on its interfaces would reduce the time needed for VIP failover, thereby minimizing potential service disruptions.

[0116] At step 604, the process

[0600] includes listing down the traffic-serving interfaces of the selected 5G Network Function (NF). This includes identifying and cataloguing all the network interfaces on the NF that are actively handling data traffic. The interfaces facilitates in maintaining network operations, as they manage the flow of data between the NF and other network components. By listing these interfaces, the system ensures that any subsequent configuration changes, such as disabling Duplicate Address Detection (DAD), are applied specifically to the interfaces that are crucial for traffic handling, thereby optimizing the network's performance and reliability.

[0117] At step 606, the process

[0600] includes checking the existing Duplicate Address Detection (DAD) configuration settings in the kernel file, specifically within the `sysctl` configuration. The step includes accessing the system's kernel parameters to determine the current status of the DAD feature on the relevant network interfaces. By reviewing these settings, the process verifies whether DAD is currently enabled or disabled, providing the necessary information to proceed with any required adjustments.

[0118] At step 608, the process

[0600] includes making the Duplicate Address Detection (DAD) configuration changes for each individual interface of the selected Network Function (NF). The step includes modifying the kernel-level parameters to disable DAD on each interface that handles data traffic. By doing so, the system ensures that each interface can reassign a Virtual IP (VIP) more quickly during failover, reducing delays caused by the DAD process.

[0119] At step 610, the process

[0600] includes implementing the automation code for changing the Duplicate Address Detection (DAD) configuration. The step includes deploying a script or set of automated commands that modify the DAD settings on the selected 5G Network Function (NF). The automation code is designed to disable DAD on the relevant network interfaces, ensuring that the changes are applied consistently and efficiently across the network without requiring manual intervention. By automating this process, the system can quickly implement the configuration changes, reducing the potential for errors and ensuring that the network is optimized for faster failover and improved reliability.

[0120] At step 612, the process

[0600] includes conducting a sanity check for the Duplicate Address Detection (DAD) configuration change. The step includes verifying the correctness of the DAD parameter modifications across the relevant network interfaces, confirming that the intended changes have been applied without errors. The step

[0612] may further include checking the system's logs, monitoring the network's response to the configuration change, and running basic tests to confirm that all components are functioning as expected after the DAD change.

[0121] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for maintaining application-level High Availability (HA) in a network environment, the instructions include executable code which, when executed by one or more units of a system, causes a determining unit

[0302] to determine one or more network functions (NFs) to be configured for HA. The instruction when executed further causes the determining unit

[0302] to determine one or more interfaces of the one or more NFs that are serving data traffic. The instructions when executed further causes a modifying unit

[0304] to modify kernel level parameters, such that active Duplicate Address Detection (DAD) parameters for each of the oneor more interfaces of the one or more NFs is disabled. The instructions when executed further causes a generating unit

[0306] to generate for each of the one or more interfaces of the one or more NFs, a virtual IP (VIP) address. The instructions when executed further causes a processing unit

[0308] to confirm for the one or more interfaces of the one or more NFs, if the corresponding DAD parameter is disabled, based on an interaction of the corresponding VIP addresses with data traffic.

[0122] As is evident from the above, the present disclosure provides a technically advanced solution for maintaining application-level High Availability (HA) in a network environment. The present solution enables to minimize the Virtual IP address failover time from 3 sec to 1 sec. It would be appreciated by the person skilled in the art that the present disclosure reduces packet drops during heavy load specially, in production servers.

[0123] 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 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 functionality described herein, are considered to be encompassed within the scope of the present disclosure.

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

Claims

We Claim:

1. A method for maintaining application-level High Availability (HA) in a network environment, the method comprising: - determining, by a determining unit [302] at a state manager (SM) module [300a], one or more network functions (NFs) to be configured for HA; - determining, by the determining unit [302] at the SM module [300a], one or more interfaces of the one or more NFs that are serving data traffic; - modifying, by a modifying unit [304] at the SM module [300a], kernel level parameters, such that active Duplicate Address Detection DAD parameters for each of the one or more interfaces of the one or more NFs is disabled; - generating, by a generating unit [306] at the SM module [300a], for each of the one or more interfaces of the one or more NFs, a virtual IP (VIP) address; and - confirming, by a processing unit [308] at the SM module [300a], for the one or more interfaces of the one or more NFs, if the corresponding DAD parameter is disabled, based on an interaction of the corresponding VIP addresses with data traffic.

2. The method as claimed in claim 1, wherein the method comprises uploading, by the processing unit [308] at the SM module [300a], the modified kernel level parameters to enable application of the disabled DAD parameters for each of the one or more interfaces of the one or more NFs.

3. The method as claimed in claim 1, wherein the generated VIP address of each of the one or more interfaces of the one or more NFs is based on a corresponding data traffic at each of the one or more interfaces of the one or more NFs.

4. The method as claimed in claim 1, wherein the one or more NFs are selected from a set of NFs in the network environment, and wherein the one or more NFs are selected based on being configured with an active DAD parameter.

5. The method as claimed in claim 1, wherein each of the generated VIP address is adapted to serve data traffic.

6. A system for maintaining application-level High Availability (HA) in a network environment, the system comprising:- a determining unit [302] configured to: o determine one or more network functions (NFs) to be configured for HA; anddetermine one or more interfaces of the one or more NFs that are serving data traffic; - a modifying unit [304] configured to modify kernel level parameters, such that active Duplicate Address Detection (DAD) parameters for each of the one or more interfaces of the one or more NFs is disabled; - a generating unit [306] configured to generate for each of the one or more interfaces of the one or more NFs, a virtual IP (VIP) address; and - a processing unit [308] configured to confirm for the one or more interfaces of the one or more NFs, if the corresponding DAD parameter is disabled, based on an interaction of the corresponding VIP addresses with data traffic.

7. The system as claimed in claim 6, wherein the processing unit [308] is further configured to upload the modified kernel level parameters to enable application of the disabled DAD parameters for each of the one or more interfaces of the one or more NFs.

8. The system as claimed in claim 6, wherein the generated VIP address of each of the one or more interfaces of the one or more NFs is based on a corresponding data traffic at each of the one or more interfaces of the one or more NFs.

9. The system as claimed in claim 6, wherein the one or more NFs are selected from a set of NFs in the network environment, and wherein the one or more NFs are selected based on being configured with an active DAD parameter.

10. The system as claimed in claim 6, wherein each of the generated VIP address is adapted to serve data traffic.

11. A non-transitory computer-readable storage medium storing instructions for maintaining application-level High Availability (HA) in a network environment which, when executed by one or more units of a system, causes: - a determining unit [302] to: o determine one or more network functions (NFs) to be configured for HA; ando determine one or more interfaces of the one or more NFs that are serving data traffic; - a modifying unit [304] to modify kernel level parameters, such that active Duplicate Address Detection (DAD) parameters for each of the one or more interfaces of the one or more NFs is disabled; - a generating unit [306] to generate for each of the one or more interfaces of the one or more NFs, a virtual IP (VIP) address; and - a processing unit [308] to confirm for the one or more interfaces of the one or more NFs, if the corresponding DAD parameter is disabled, based on an interaction of the corresponding VIP addresses with data traffic.

Images