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

METHOD AND SYSTEM FOR MANAGING A NODE
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to network performance
management systems. More particularly, embodiments of the present disclosure relate to managing a node.
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. The third-generation (3G) technology marked the introduction of high¬speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized 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. 5G network management faces a host of new challenges beyond 3G and 4G. There has been a change in the methodology for efficient network management with each generation.

[0004] Network management is a collection of applications, tools and processes used
to provision, operate, maintain, administer and secure network infrastructure. One of the primary goals of network management is to keep network services reliable. This involves proactive monitoring to identify and address issues before they cause disruptions, minimize downtime, and maximize network uptime. According to the International Organization for Standardization (ISO) network management model, there are five main functional areas of network management. These areas are defined as Fault Management, Configuration Management, Accounting Management, Performance Management and Security Management. These are also known as FCAPS data.
[0005] A Network Management System (NMS) is a critical piece in the overall
telecommunications-management solution. It is the sole mediator to monitor and manage the FCAPS data of network elements. The technical challenge in collecting and analyzing the network parameters involving the FCAPS data is involvement of multiple systems which monitor each parameter to check the health of the network. Specifically, the reliance on multiple systems to gather FCAPS data for Radio Access Network (RAN) nodes poses a significant challenge. The RAN nodes provide a communication link between the network and a User Equipment (UE). The large number of RAN nodes in a network creates an overhead on processing requirements, as each node needs to independently collect and process the data. Consequently, the network management system managing these RAN nodes faces increased computational demands, potentially leading to slower response times and decreased overall efficiency.
[0006] Further, over the period of time various solutions have been developed to
improve the performance of communication devices and to manage FCAPS of RAN nodes. However, there are certain challenges with existing solutions. Firstly, the reliance on multiple systems to determine FCAPS data for RAN nodes creates complexity and inefficiency. These systems often operate in isolation, leading to siloed data and disjointed processes. As a result, obtaining a holistic view of network performance and security becomes challenging. Secondly, the existing solutions may lack scalability and adaptability. As networks grow in size and complexity, the ability to handle increasing data volumes and accommodate new technologies becomes crucial. Additionally, the compatibility of existing solutions with different network architectures and vendors can be a limitation, as interoperability issues can arise. Moreover, the existing solutions may
3

not effectively address real-time monitoring and analysis requirements, leading to delays in identifying and resolving network faults or security threats. Finally, the lack of standardized approaches and protocols for FCAPS implementation can result in inconsistent practices and hinder interoperability.
[0007] Further, in the existing solutions, different applications are used by NMS, for
getting FCAPS data. Additionally, there is no mechanism to check down nodes or inactive nodes and so the requests for fetching the FCAPS data is sent to all nodes, irrespective of node status. This results in large number of requests being sent even to down nodes which are not in a state to respond with FCAPS data. As a result, there is a need to reduce the number of hits for requesting the FCAPS data from RAN nodes.
[0008] Thus, there exists an imperative need in the art to manage data related to Fault,
Configuration, Accounting, Performance and Security (FCAPS) of a node in a network, which the present disclosure aims to address.
SUMMARY
[0009] 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.
[0010] An aspect of the present disclosure may relate to a method for managing a node.
The method includes transmitting, by a transceiver unit, from a Network Management System (NMS), one or more health status check requests to one or more instances of a node, wherein each health status check request from the one or more health status check requests is for at least one instance from the one or more instances of the node. The method further includes receiving, by the transceiver unit, at the NMS, a health status response from each of the one or more instances of the node based on the one or more health status check requests. Furthermore, the method includes determining, by a processing unit, at the NMS, one of a node instance up status and a node instance down status for each of the one or more instances of the node based on the received health status response from each of the one or more instances of the node. The method further includes requesting, by the processing unit, at the NMS, one or more attributes associated with the node, in an event
4

of determining the node instance up status for the one or more instances of the node. The up status of the node instance refers to a scenario where the node is active or in operation. The down status of the node instance refers to the scenario where the node is not active or is not in operation.
[0011] In an exemplary aspect of the present disclosure, the one or more health status
check requests is transmitted by the transceiver unit from the NMS at a pre-configured time interval.
[0012] In an exemplary aspect of the present disclosure, the health status response from
each of the one or more instances of the node, comprises one or more parameters.
[0013] In an exemplary aspect of the present disclosure, the one or more parameters
comprise at least a computing resource information, a network information and a storage information.
[0014] In an exemplary aspect of the present disclosure, the one or more attributes
requested from the node, in an event of determining the node instance up status for all the node instances from the one or more node instances, are FCAPS (fault, configuration, accounting, performance, security) attributes.
[0015] In an exemplary aspect of the present disclosure, the method further includes
storing the received health status response from each of the one or more instances of the node in a predetermined database.
[0016] In an exemplary aspect of the present disclosure, the method further comprises,
triggering, by the processing unit, an alarm in an event of determining the node instance down status for at least one instance from the one or more instances of the node, based on the one or more parameters received in the health status response.
[0017] In an exemplary aspect of the present disclosure, the method further comprises,
detecting one or more issues with the at least one instance from the one or more instances of the node based on the alarm, and performing a remedial action for the detected one or more issues.

[0018] In an exemplary aspect of the present disclosure, the method further comprises,
managing the node by the processing unit, at the NMS, based on the FCAPS attributes received from the node.
[0019] In an exemplary aspect of the present disclosure, the managing of the node
based on the FCAPS attributes, comprises, identifying, at least, a fault, a configuration change, a network usage, network performance and security threats.
[0020] Another aspect of the present disclosure may relate to a network management
system for managing a node. The network management system includes a transceiver unit. The transceiver unit is configured to transmit one or more health status check requests to one or more instances of a node, wherein each health status check request from the one or more health status check requests is for at least one instance from the one or more instances of the node. The transceiver unit is further configured to receive, a health status response from each of the one or more instances of the node based on the one or more health status check requests. The network management system further includes a processing unit, connected to at least the transceiver unit. The processing unit is configured to determine, one of a node instance up status and a node instance down status for each of the one or more instances of the node based on the received health status response from each of the one or more instances of the node. The up status of the node instance refers to a scenario where the node is active or in operation. The down status of the node instance refers to the scenario where the node is not active or is not in operation.
[0021] The processing unit is further configured to request, one or more attributes
associated with the node, in an event of determining the node instance up status for the one or more instances of the node.
[0022] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing instructions for managing a node, the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit of the system to: transmit one or more health status check requests to one or more instances of a node, wherein each health status check request from the one or more health status check requests is for at least one instance from the one or

more instances of the node; and to receive, a health status response from each of the one or more instances of the node based on the one or more health status check requests. Further, instructions include executable code which, when executed causes a processing unit of the system to determine, one of a node instance up status and a node instance down status for each of the one or more instances of the node based on the received health status response from each of the one or more instances of the node. Further, instructions include executable code which, when executed causes the processing unit of the system to request, one or more attributes associated with the node, in an event of determining the node instance up status for the one or more instances of the node.
OBJECTS OF THE INVENTION
[0023] Some of the objects of the present disclosure, which at least one embodiment
disclosed herein satisfies are listed herein below.
[0024] It is an object of the present disclosure to provide a system and a method for
FCAPS management of RAN nodes.
[0025] It is another object of the present disclosure to provide a solution that marks a
node instance as up or down accordingly in a persistent storage based on response received for the health check requests.
[0026] It is yet another object of the present disclosure to provide a solution to check
up instance entries from the node instances in the persistent storage and request the FCAPS data from the node.
[0027] It is yet another object of the invention to provide enhancement of the existing
FCAPS request. Earlier, for getting FCAPS data, different applications were required to support it, also there was no mechanism to check down nodes and data was requested from all nodes irrespective of node status
[0028] It is yet another object of the invention to provide solution for at least the
following:
• Optimized hits for FCAPS data

• Support for different network domains from a single UI
• Option for generating FCAPS reports for users
• Integration of NMS with different North Bound Interfaces (NBI)
• Displaying Pan India node instances at a single place.
DESCRIPTION OF THE DRAWINGS
[0029] 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.
[0030] FIG. 1 illustrates an exemplary network architecture diagram depicting
communication between Network Management System (NMS) and nodes of a network, in accordance with the exemplary implementations of the present disclosure.
[0031] 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.
[0032] FIG. 3 illustrates an exemplary block diagram of a system for managing a node,
in accordance with exemplary implementations of the present disclosure.
[0033] FIG. 4 illustrates a method flow diagram for managing a node in accordance
with exemplary implementations of the present disclosure.

[0034] FIG. 5 illustrates an exemplary method flow of a Network Management System
(NMS), for managing a Fault, Configuration, Accounting, Performance and Security (FCAPS) of a Node in a network.
[0035] FIG. 6 illustrates an exemplary system architecture, for managing a Fault,
Configuration, Accounting, Performance and Security (FCAPS) of a node in a network.
[0036] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
[0037] In the following description, for the purposes of explanation, various specific
details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific 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.
[0038] 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.
[0039] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0040] Also, it is noted that individual embodiments may be described as a process
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.
[0041] The word “exemplary” and/or “demonstrative” is used herein to mean serving
as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any 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.
[0042] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for 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.
[0043] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a
smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of
10

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.
[0044] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable 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.
[0045] As used herein “interface” or “user interface” refers to a shared boundary across
which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
[0046] All modules, units, components used herein, unless explicitly excluded herein,
may be software modules or hardware processors, the processors being a 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.
[0047] As used herein the transceiver unit includes 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.

[0048] As used herein, a Radio Access Network (RAN) node is part of a mobile
telecommunications system that connects user equipment (UE) to the core network (CN)
and provides access to different types of networks (e.g., 5G network). It consists of radio
5 base stations and the radio access technologies that enable wireless communication.
[0049] As discussed in the background section, the current known solutions have
several shortcomings. There is lack of standardized approaches and protocols for FCAPS implementation, which results in inconsistent practices and hinders interoperability.
10 Further, in the existing solutions, different applications are used by NMS, for getting
FCAPS data. Additionally, there is no mechanism to check down nodes or inactive nodes and so the requests for fetching the FCAPS data is sent to all nodes, irrespective of node status. This results in large number of requests being sent even to down nodes which are not in a state to respond with FCAPS data. The present disclosure aims to overcome the
15 above-mentioned and other existing problems in this field of technology by providing
method and system of managing a node.
[0050] FIG. 1 illustrates an exemplary network architecture diagram showing
communication between a Network Management System [504] and a node [506], in
20 accordance with exemplary implementation of the present disclosure. The NMS [504]
includes at least one transceiver unit [302] and at least one processing unit [304].
[0051] Further, the network architecture as shown in FIG.1 is intended to be read in
conjunction with block diagram of a system [300] as shown in FIG.3, exemplary method
25 flow of a Network Management System (NMS) [504] as shown in FIG. 5 and exemplary
system architecture for managing FCAPS of a node in a network as shown in FIG. 6. The systems in FIG. 1, FIG. 3, FIG. 5 and FIG. 6 complement each other.
[0052] In an exemplary aspect of the present disclosure, the NMS [504] may support
30 managing of network node through a single User Interface (UI) [602].
[0053] In an exemplary aspect of the present disclosure, the NMS [504] may transfer
one or more health status check requests to one or more instances of the node [506]. Each health status check request from the one or more health status check requests is for at least
12

one instance from the one or more instances of the node [506]. The one or more health
status check requests are transmitted by the transceiver unit [302] of the NMS [504] at a
pre-configured time interval. The pre-configured time interval may be defined by a user.
In an exemplary aspect of the present disclosure, the NMS [504] may check the health
5 status of the node instances after every minute.
[0054] In an exemplary aspect of the present disclosure, the one or more instances of
the node [506] may further send a health status response based on the one or more health
status check requests to the NMS [504].
10
[0055] In an exemplary aspect of the present disclosure, the NMS [504] may further
determine, one of a node instance up status and a node instance down status for each of
the one or more instances of the node [506] based on the received health status response
from each of the one or more instances of the node [506]. The up status of the node instance
15 refers to a scenario where the node is active or in operation. The down status of the node
instance refers to the scenario where the node is not active or is not in operation.
[0056] In an exemplary aspect of the present disclosure, the NMS [504] may further
request one or more attributes associated with the node [506], in an event of determining
20 the node instance up status for the one or more instances of the node [506]. The one or
more attributes requested from the node [506], in an event of determining the node instance up status for the one or more instances of the node [506], are FCAPS (fault, configuration, accounting, performance, security) attributes. The fault attribute refers to recognizing and correcting of operational faults which may occur within the
25 communication network. The fault attribute may discover the occurrence of the faults and
may fix the fault.
[0057] In an exemplary aspect of the present disclosure, the NMS [504] may further
trigger, an alarm in an event of determining the node instance down status for at least one
30 instance from the one or more instances of the node [506], based on the one or more
parameters received in the health status response. The event of determining the up status and the down status of the node instance may involve the NMS [504] performing a monitoring of the one or more instances of the node [506]. While performing the monitoring of the one or more instances of the node [506], the NMS [504] may monitor
35 all the resources which include but may not be limited to CPU, RAM, network
13

connectivity, network bandwidth for the computing resource information, the network
information and the storage information. If the health check request fails because the one
or more nodes [506] are not responding, then the one or more parameters in the health
status response received at the NMS [504] will indicate a down status for the one or more
5 nodes.
[0058] In an exemplary aspect of the present disclosure, the NMS [504] may further
detect one or more issues with the at least one instance from the one or more instances of the node [506] based on the alarm and perform a remedial action for the identified one or
10 more issues. The identified one or more issues include but may not be limited to a database
error, a communication error, a processing error, a Quality-of-Service error, a User Equipment error, an environmental error, and the like. The NMS [504] may have the remedial action for each of the identified one or more issues. For instance, if resource utilization is high for an application, then auto scale out of the application is the remedial
15 action to serve more traffic. The remedial action may be pre-defined at the NMS [504] or
may be defined by the user. The NMS [504] may further manage the node [506] based on the FCAPS attributes associated with the node. The managing of the node based on the FCAPS attributes comprises, identifying, at least, a fault, a configuration change, a network usage, one or more network performance and security threats.
20
[0059] FIG. 2 illustrates an exemplary block diagram of a computing device [200]
upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [200] may also implement a method for managing a node. In another
25 implementation, the computing device [200] itself implements the method for managing
a node using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
30 [0060] The computing device [200] may include a bus [202] or other communication
mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device,
14

coupled to the bus [202] for storing information and instructions to be executed by the
processor [204]. The main memory [206] also may be used for storing temporary variables
or other intermediate information during execution of the instructions to be executed by
the processor [204]. Such instructions, when stored in non-transitory storage media
5 accessible to the processor [204], render the computing device [200] into a special-purpose
machine that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204].
10
[0061] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive
is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED)
15 display, Organic LED (OLED) display, etc. for displaying information to a computer user.
An input device [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command selections to the processor [204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating
20 direction information and command selections to the processor [204], and for controlling
cursor movement on the display [212]. 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.
25 [0062] The computing device [200] may implement the techniques described herein
using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [200] causes or programs the computing device [200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [200] in
30 response to the processor [204] executing one or more sequences of one or more
instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium, such as the storage device [210]. Execution of the sequences of instructions contained in the main memory [206] causes the processor [204] to perform the process steps described herein. In alternative
15

implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
[0063] The computing device [200] also may include a communication interface [218]
5 coupled to the bus [202]. The communication interface [218] provides a two-way data
communication coupling to a network link [220] that is connected to a local network [222].
For example, the communication interface [218] may be an integrated services digital
network (ISDN) card, cable modem, satellite modem, or a modem to provide a data
communication connection to a corresponding type of telephone line. As another example,
10 the communication interface [218] may be a local area network (LAN) card to provide a
data communication connection to a compatible LAN. Wireless links may also be
implemented. In any such implementation, the communication interface [218] sends and
receives electrical, electromagnetic or optical signals that carry digital data streams
representing various types of information.
15
[0064] The computing device [200] can send messages and receive data, including
program code, through the network(s), the network link [220] and the communication
interface [218]. In the Internet example, a server [230] might transmit a requested code for
an application program through the Internet [228], the ISP [226], the local network [222],
20 the host [224] and the communication interface [218]. The received code may be executed
by the processor [204] as it is received, and/or stored in the storage device [210], or other
non-volatile storage for later execution.
[0065] The present disclosure is implemented by a system [300] as shown in FIG. 3. In
25 an implementation, the system [300] may be implemented on the computing device [200]
as shown in FIG. 2.
[0066] Referring to FIG. 3, an exemplary block diagram of a system [300] for
managing a node, in accordance with the exemplary implementations of the present
30 disclosure. The system [300] comprises a Network Management System (NMS) [504]. In
an implementation of the present disclosure, the NMS [504] may support managing of network node through a single User Interface (UI) [602].
[0067] In an exemplary aspect of the present disclosure, the NMS [504] further
35 comprises at least one transceiver unit [302] and at least one processing unit [304]. Also,
16

in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple
such units or the system [300] may comprise any such numbers of said units, as required
to implement the features of the present disclosure. In an implementation, the system [300]
may reside in a server or a network entity.
5
[0068] Further, block diagram of the system [300] as shown in FIG. 3 is intended to be
read in conjunction with the network architecture [100] as shown in FIG.1, exemplary
method flow of a Network Management System (NMS) [504] as shown in FIG. 5 and
exemplary system architecture for managing FCAPS of a node in a network as shown in
10 FIG. 6. The systems in FIG. 1, FIG. 3, FIG. 5 and FIG. 6 complement each other.
[0069] The system [300] is configured for managing a node, with the help of the
interconnection between the components/units of the system [300].
15 [0070] In an exemplary aspect of the present disclosure, the system [300] shows the
NMS [504] which includes a transceiver unit [302]. The transceiver unit [302] is configured to transmit one or more health status check requests to one or more instances of a node [506]. Each health status check request from the one or more health status check requests is for at least one instance from the one or more instances of the node [506]. In
20 an implementation of the present disclosure, in the 5th generation core network, the one or
more instances of the node [506] refers to installing multiple instances of a network node to increase the network availability and provide multiple paths on network to manage traffic.
25 [0071] In an exemplary aspect of the present disclosure, the one or more health status
check requests are transmitted by the transceiver unit [302] at a pre-configured time interval. In an implementation of the present disclosure, a user may define the pre-configured time interval. In an implementation of the present disclosure, the pre-configured time interval may change for each of the one or more health status check
30 requests. For example, in an exemplary aspect, the NMS [504] checks the health of the
node instances after every minute to check if the node instance is up or not.
[0072] In an exemplary aspect of the present disclosure, the transceiver unit [302] is
further configured to receive, a health status response from each of the one or more
35 instances of the node [506] based on the one or more health status check requests. The
17

health status response from each of the one or more instances of the node [506] comprises one or more parameters. The one or more parameters comprise at least computing resource information, a network information and a storage information.
5 [0073] In an exemplary aspect of the present disclosure, the computing resource
information refers to information of the resources available for processing, storage, and
networking. The computing resource information may help to manage and optimize the
performance of a telecommunications network. The network information may include
information on availability or unavailability of network, rate of failure of requests in a
10 network, latency rate, packet loss, and the like. The storage information may include
information of availability of network attached storage (NAS), availability of storage, performance of storage, utilization of storage and the like.
[0074] In an exemplary aspect of the present disclosure, the NMS [504] of the system
15 [300] further includes a processing unit [304]. The processing unit [304] is connected to
at least the transceiver unit [302]. The processing unit [304] is configured to determine,
one of a node instance up status and a node instance down status for each of the one or
more instances of the node [506] based on the received health status response from each
of the one or more instances of the node [506]. The up status of the node instance refers
20 to a scenario where the node is active or in operation. The down status of the node instance
refers to the scenario where the node is not active or is not in operation.
[0075] Furthermore, the processing unit [304] is configured to request, one or more
attributes associated with the node [506], in an event of determining the node instance up
25 status for the one or more instances of the node [506]. The one or more attributes requested
from the node [506], in an event of determining the node instance up status for the one or more instances of the node [506], are FCAPS (fault, configuration, accounting, performance, security) attributes. The event of determining the up status and the down status of the node instance may involve the NMS [504] performing a monitoring of the
30 one or more instances of the node [506]. While performing the monitoring of the one or
more instances of the node [506], the NMS [504] may monitor all the resources which include but may not be limited to CPU, RAM, network connectivity, network bandwidth for the computing resource information, the network information and the storage information. If the health check request fails because the one or more nodes [506] are not
18

responding, then the one or more parameters in the health status response received at the NMS [504] will indicate a down status for the one or more nodes.
[0076] In an exemplary aspect of the present disclosure, the event of determining the
5 status of the one or more instances of the node [506] may include integrating the one or
more of the faults, the configuration, the accounting, the performance, and the security attributes. The fault attribute refers to operational faults which may occur within the communication network. The fault attribute may help discover the occurrence of the fault and fix the fault. The configuration attribute refers to the information regarding the
10 placement of network components. The asset attribute refers to the financial attributes of
the components configured in the network. The asset attribute includes but may not be limited to costs associated with the depreciation and maintenance of a component of a network, and accounting and charging for the contribution of a component of the network. The performance attribute refers to performance of the network against the as
15 expected, and in accordance with the service level agreements and other internal and
external metrics. The security attribute refers to any kind of threat or malicious interventions and helps to ensure that unauthorized individuals cannot access the network. In an implementation of the present disclosure, the processing unit [304] is further configured to store in a predetermined database [606], the health status response received
20 from each of the one or more instances of the node [506].
[0077] In an exemplary aspect of the present disclosure, the processing unit [304] is
further configured to trigger, an alarm in an event of determining the node instance down
status for at least one instance from the one or more instances of the node [506], based on
25 the one or more parameters received in the health status response.
[0078] In an exemplary aspect of the present disclosure, the processing unit [304]
further comprises, detecting one or more issues with the at least one instance from the one
or more instances of the node [506] based on the alarm, and performing a remedial action
30 for the identified one or more issues. The identified one or more issues include but may
not be limited to a database error, a communication error, a processing error, a Quality-of-Service error, a User Equipment error, an environmental error, and the like. The NMS [504] may have the remedial action for each of the identified one or more issues. For instance, if resource utilization is high for an application, then auto scale out of the
19

application is the remedial action to serve more traffic. The remedial action may be pre¬
defined at the NMS [504] or may be defined by the user. The processing unit [304] is
further configured to manage the node [506] based on the FCAPS attributes associated
with the node. The managing of the node by the processing unit [304], based on the FCAPS
5 attributes comprises, identifying, at least, a fault, a configuration change, a network usage,
one or more network performance and security threats.
[0079] In an exemplary aspect of the present disclosure, the FCAPS data associated
with the node instance is requested by the processing unit [304] based on the health status
10 response associated with said node instance stored in the predetermined database [606].
[0080] Referring to FIG. 4, an exemplary method flow diagram [400] for managing a
node, in accordance with exemplary implementations of the present disclosure is shown.
In an implementation, the method [400] is performed by the system [300]. Further, in an
15 implementation, the system [300] may be present in a server device to implement the
features of the present disclosure. In an implementation of the present disclosure, the NMS [504] may support managing of network node through a single User Interface (UI) [602].
[0081] Also, as shown in FIG. 4, the method [400] starts at step [402].
20
[0082] At step [404], the method comprises transmitting, by a transceiver unit [302],
from a Network Management System (NMS) [504], one or more health status check
requests to one or more instances of the node [506], wherein each health status check
request from the one or more health status check requests is for at least one instance from
25 the one or more instances of the node [506]. The one or more health status check requests
is transmitted by the transceiver unit [302] from the NMS [504] at a pre-configured time interval. In an implementation of the present disclosure, in the 5th generation core network, the one or more instances of the node [506] refers to installing multiple instances of a network node in a network to increase the network availability and provide multiple paths
30 on network to manage traffic. In an implementation of the present disclosure, the pre-
configured time interval may be defined by a user. In an embodiment, the pre-configured time interval may change for each of the one or more health status check requests. In an exemplary aspect of the present disclosure, the NMS [504] may check the health status of the node instances after every minute.
35
20

[0083] Next, at step [406], the method includes receiving, by the transceiver unit [302],
at the NMS [504], a health status response from each of the one or more instances of the node [506] based on the one or more health status check requests. The health status response from each of the one or more instances of the node [506], comprises one or more parameters. The one or more parameters comprise at least a computing resource information, a network information and a storage information.
[0084] In an exemplary aspect of the present disclosure, the computing resource
information refers to information of the resources available for processing, storage, and networking. The computing resource information may help to manage and optimize the performance of a telecommunications network. The network information may include information on availability or unavailability of network, rate of failure of requests in a network, latency rate, packet loss, and the like. The storage information may include information of availability of network attached storage (NAS), availability of storage, performance of storage, utilization of storage and the like.
[0085] In an exemplary aspect of the present disclosure, the method further comprises,
storing the received health status response from each of the one or more instances of the node [506] in a predetermined database [606].
[0086] Next, at step [408], the method includes determining, by a processing unit [304],
at the NMS [504], one of a node instance up status and a node instance down status for each of the one or more instances of the node [506] based on the received health status response from each of the one or more instances of the node [506]. The up status of the node instance refers to a scenario where the node is active or in operation. The down status of the node instance refers to the scenario where the node is not active or is not in operation.
[0087] In an exemplary aspect of the present disclosure, the method further comprises,
triggering, by the processing unit [304], an alarm in an event of determining the node instance down status for at least one instance from the one or more instances of the node [506], based on the one or more parameters received in the health status response. The method further comprises, detecting one or more issues with the at least one instance from the one or more instances of the node [506] based on the alarm, and performing a remedial action for the detected one or more issues. The identified one or more issues include but

may not be limited to a database error, a communication error, a processing error, a Quality-of-Service error, a User Equipment error, an environmental error, and the like. The NMS [504] may have the remedial action for each of the identified one or more issues. For instance, if resource utilization is high for an application, then auto scale out of the application is the remedial action to serve more traffic. The remedial action may be pre¬defined at the NMS [504] or may be defined by the user.
[0088] Next, at step [410], the method includes requesting, by the processing unit
[304], at the NMS [504], one or more attributes associated with the node [506], in an event of determining the node instance up status for the one or more instances of the node [506]. The one or more attributes requested from the node [506], in an event of determining the node instance up status for all the instances from the one or more instances of the node [506], are FCAPS (fault, configuration, accounting, performance, security) attributes. In an implementation of the present disclosure, checking the health status of the one or more instances of the node [506] prior to fetching the FCAPS attribute saves a lot of API hits. The API hits refer to a single request made to an API endpoint. The request may be made by a web application, mobile app, and the like. The event of determining the up status and the down status of the node instance may involve the NMS [504] performing a monitoring of the one or more instances of the node [506]. While performing the monitoring of the one or more instances of the node [506], the NMS [504] may monitor all the resources which include but may not be limited to CPU, RAM, network connectivity, network bandwidth for the computing resource information, the network information and the storage information. If the health check request fails because the one or more nodes [506] are not responding, then the one or more parameters in the health status response received at the NMS [504] will indicate a down status for the one or more nodes.
[0089] In an exemplary aspect of the present disclosure, the method further comprises,
managing the node [506] by the processing unit [304], at the NMS [504], based on the FCAPS attributes received from the node [506]. The managing of the node based on the FCAPS attributes, comprises, identifying, at least, a fault, a configuration change, a network usage, and one or more network performance and security threats.
[0090] In an exemplary aspect of the present disclosure, the event of determining the
status of the one or more instances of the node [506] may include integrating the one or

more of the faults, the configuration, the accounting, the performance, and the security attributes. The fault attribute refers to operational faults which may occur within the communication network. The fault attribute may help discover the occurrence of the fault and fix the fault. The configuration attribute refers to the information regarding the placement of network components. The asset attribute refers to the financial attributes of the components configured in the network. The asset attribute includes but may not be limited to costs associated with the depreciation and maintenance of a component of a network, and accounting and charging for the contribution of a component of the network. The performance attribute refers to performance of the network against the as expected, and in accordance with the service level agreements and other internal and external metrics. The security attribute refers to any kind of threat or malicious interventions and helps to ensure that unauthorized individuals cannot access the network.
[0091] Thereafter, the method terminates at step [412].
[0092] The method [400], as shown in FIG. 4 will be explained in detail by an
exemplary method flow of a Network Management System (NMS) [504] for managing nodes in a network as shown in FIG. 5.
[0093] Further, the method flow of a Network Management System (NMS) [504] as
shown in FIG. 5 is intended to be read in conjunction with the network architecture [100] as shown in FIG.1, block diagram of the system [300] as shown in FIG.3 and exemplary system architecture for managing FCAPS of a node in a network as shown in FIG. 6. The systems in FIG. 1, FIG. 3, FIG. 5 and FIG. 6 complement each other.
[0094] In an exemplary aspect of the present disclosure, in order to manage the
instances of RAN nodes, the transceiver unit [302] and the processing unit [304] of the system [300] as shown in FIG. 3 are configured to perform the steps in conjunction with method flow [500] as shown in FIG. 5. In an implementation of the present disclosure, the NMS [504] may support managing of network node through a single User Interface (UI) [602].
[0095] At step 1, the transceiver unit [302] is configured to send, from the Network
Management System (NMS) [504] to the node [506] in the network, one or more health status check requests for all the instances of the node [506], at a pre-configured time

interval. In an implementation of the present solution, the pre-configured time interval associated with the health status check requests may be a user defined interval. In an exemplary aspect of the present disclosure, the NMS [504] may check the health status of the one or more instances of the node [506] after every minute. In an implementation of the present disclosure, the pre-configured time interval may change for each of the one or more health status check requests.
[0096] Further, at step 2, the transceiver unit [302] of the system [300] in conjunction
with method flow [500] is configured to receive, at the NMS [504], the health status response based on each health check request from the health status check requests. In an implementation of the present disclosure, once the health status response is received, the NMS [504] will mark a node instance as up status or down status accordingly. Further, the NMS [504] may request one or more attributes associated with the node [506] in an event of determining the node instance up status of the one or more instances of the node [506]. The up status of the node instance refers to a scenario where the node is active or in operation. The down status of the node instance refers to the scenario where the node is not active or is not in operation. The event of determining the up status and the down status of the node instance may involve the NMS [504] performing a monitoring of the one or more instances of the node [506]. While performing the monitoring of the one or more instances of the node [506], the NMS [504] may monitor all the resources which include but may not be limited to CPU, RAM, network connectivity, network bandwidth for the computing resource information, the network information and the storage information. If the health check request fails because the one or more nodes [506] are not responding, then the one or more parameters in the health status response received at the NMS [504] will indicate a down status for the one or more nodes.
[0097] In an exemplary aspect of the present disclosure, the one or more attributes
requested from the node [506], in an event of determining the node instance up status for all the instances from the one or more instances of the node [506], are FCAPS (fault, configuration, accounting, performance, security) attributes. The event of determining the status of the one or more instances of the node [506] may include integrating the one or more of the faults, the configuration, the accounting, the performance, and the security attributes. The fault attribute refers to operational faults which may occur within the communication network. The fault attribute may help discover the occurrence of the fault

and fix the fault. The configuration attribute refers to the information regarding the placement of network components. The asset attribute refers to the financial attributes of the components configured in the network. The asset attribute includes but may not be limited to costs associated with the depreciation and maintenance of a component of a network, and accounting and charging for the contribution of a component of the network. The performance attribute refers to performance of the network against the as expected, and in accordance with the service level agreements and other internal and external metrics. The security attribute refers to any kind of threat or malicious interventions and helps to ensure that unauthorized individuals cannot access the network. The NMS [504] manages the node based on the FCAPS attributes received from the node.
[0098] Further, at step 3, the NMS [504] in the method flow [500] is configured to push
the FCAPS response to a Northbound Interface (NBI) [502]. The NBI [502] is an output-based interface to receive outputs. In an exemplary implementation, the Northbound Interface (NBI) [502] refers to an interface which is output oriented. The NBI [502] makes the FCAPS response available to the user.
[0099] The exemplary method flow for managing the node instances, as shown in FIG.
5 will be explained in a detailed method flow implementation as shown in FIG. 6. FIG. 6 provides an exemplary system architecture for managing FCAPS of a node in a network.
[0100] Further, the exemplary system architecture for managing FCAPS of a node in a
network as shown in FIG. 6 is intended to be read in conjunction with the network architecture [100] as shown in FIG.1, block diagram of the system [300] as shown in FIG.3, and the method flow of a Network Management System (NMS) [504] as shown in FIG. 5. The systems in FIG. 1, FIG. 3, FIG. 5 and FIG. 6 complement each other.
[0101] The exemplary method flow [500] may be implemented on the exemplary
system architecture as shown in FIG. 6.
[0102] A User Interface (UI) [602] of the NMS [504], may send one or more health
status check requests to a Configuration Management (CM) [604].
[0103] Thereafter the method flow is executed as follows:

[0104] Step 1: The CM [604] may transmit the one or more health status check requests
to the node [506] of the network for all its instances at a pre-configured time interval. The pre-configured time interval may be defined by the user. In an exemplary aspect of the present disclosure, the NMS [504] may check the health status of the one or more instances of the node [506] after every minute.
[0105] Step 2: Once, the NMS [504] receives the health check response from the node
[506], the NMS [504] may mark the one or more instances of the node [506] with an up status or a down status and accordingly may store the health check responses in a predetermined database [606]. The health status response from each of the one or more instances of the node [506] comprises one or more parameters. In an exemplary implementation of the present disclosure, the one or more parameters comprise at least a computing resource information, a network information and a storage information. If the NMS [504] does not receive the health check response from the node [506] in first attempt, the NMS [504] may re-send the health status check request multiple times, till the health status check response is received.
[0106] Step 3: The NMS [504] may determine the up status of the one or more instances
of the node [506]. Further, the NMS [504] requests one or more attributes from the node [506] in an event of determining the node instance up status for the instances of the node [506]. In an exemplary implementation of the present disclosure, the one or more attributes requested from the node [506], in an event of determining the node instance up status for all the instances of the node [506] from the one or more instances of the node [506], are FCAPS (fault, configuration, accounting, performance, security) attributes.
[0107] The event of determining the status of the one or more instances of the node
[506] may include integrating the one or more of the faults, the configuration, the accounting, the performance, and the security attributes. The fault attribute refers to operational faults which may occur within the communication network. The fault attribute may help discover the occurrence of the fault and fix the fault. The configuration attribute refers to the information regarding the placement of network components. The asset attribute refers to the financial attributes of the components configured in the network. The asset attribute includes but may not be limited to costs associated with the depreciation and maintenance of a component of a network, and accounting and charging for the contribution of a component of the network. The performance attribute refers to

performance of the network against the as expected, and in accordance with the service level agreements and other internal and external metrics. The security attribute refers to any kind of threat or malicious interventions and helps to ensure that unauthorized individuals cannot access the network.
[0108] The NMS [504] may further manage the node based on the FCAPS response
received from the node [506].
[0109] In an implementation of the present disclosure, the NMS [504] may send the
FCAPS data for the node [506] to a streaming module [608].
[0110] The streaming module [608] comprising the FCAPS response is forwarded to
the NBI [502]. The NBI [502] is an output-based interface to receive outputs. In an exemplary implementation, the Northbound Interface (NBI) [502] refers to an interface which is output oriented. The NBI [502] makes the FCAPS response available to the user.
[0111] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for managing a node, the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit [302] of the system to: transmit one or more health status check requests to one or more instances of a node [506], wherein each health status check request from the one or more health status check requests is for at least one instance from the one or more instances of the node [506]; and to receive, a health status response from each of the one or more instances of the node [506] based on the one or more health status check requests. Further, instructions include executable code which, when executed causes a processing unit [304] of the system to determine, one of a node instance up status and a node instance down status for each of the one or more instances of the node [506] based on the received health status response from each of the one or more instances of the node [506]. Further, instructions include executable code which, when executed causes the processing unit [304] of the system to request, one or more attributes associated with the node, in an event of determining the node instance up status for the one or more instances of the node [506].

[0112] As is evident from the above, the present disclosure provides a technically
advanced solution for FCAPS management of RAN Nodes by implementing a health check system for node instances prior to making FCAPS requests. This solution offers several technical advantages. Firstly, it optimizes the efficiency of API hits by reducing unnecessary requests. By periodically conducting health check requests and marking node instances as either "up" or "down," the solution ensures that only functional instances receive FCAPS requests. This eliminates wasted API hits on non-responsive or faulty nodes, saving valuable resources and reducing network congestion. Secondly, the persistent storage that maintains the status of node instances allows for streamlined decision-making and improved system performance. The Network Management System (NMS) can quickly identify and focus solely on the "up" instances when requesting FCAPS data, enhancing the overall efficiency of data retrieval. Moreover, this solution provides a proactive approach to system monitoring and maintenance by regularly assessing the health of node instances, enabling prompt detection of issues and facilitating timely remedial actions. By optimizing resource utilization and improving system performance, these technical advantages enhance the effectiveness and reliability of FCAPS data retrieval.
[0113] 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.
[0114] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various 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.

We Claim:
1. A method for managing a node, the method comprising:
- transmitting, by a transceiver unit [302], from a Network Management System (NMS) [504], one or more health status check requests to one or more instances of the node [506], wherein each health status check request from the one or more health status check requests is for at least one instance from the one or more instances of the node [506];
- receiving, by the transceiver unit [302], at the NMS [504], a health status response from each of the one or more instances of the node [506] based on the one or more health status check requests;
- determining, by a processing unit [304], at the NMS [504], one of a node instance up status and a node instance down status for each of the one or more instances of the node [506] based on the received health status response from each of the one or more instances of the node [506]; and
- requesting, by the processing unit [304], at the NMS [504], one or more attributes associated with the node [506], in an event of determining the node instance up status for the one or more instances of the node [506].

2. The method as claimed in claim 1, wherein the one or more health status check requests are transmitted by the transceiver unit [302] from the NMS [504] at a pre-configured time interval.
3. The method as claimed in claim 1, wherein the health status response from each of the one or more instances of the node [506], comprises one or more parameters.
4. The method as claimed in claim 3, wherein the one or more parameters comprise at least a computing resource information, a network information and a storage information.
5. The method as claimed in claim 1, wherein the one or more attributes requested from the node [506], in an event of determining the node instance up status for all the node instances from the one or more instances of the node [506], are FCAPS (fault, configuration, accounting, performance, security) attributes.

6. The method as claimed in claim 1, the method, further comprises, storing the received health status response from each of the one or more instances of the node [506] in a predetermined database [606].
7. The method as claimed in claim 3, the method further comprises, triggering, by the processing unit [304], an alarm in an event of determining the node instance down status for at least one instance from the one or more instances of the node [506], based on the one or more parameters received in the health status response.
8. The method as claimed in claim 7, wherein the method further comprises: detecting one or more issues with the at least one instance from the one or more instances of the node [506] based on the alarm, and performing a remedial action for the detected one or more issues.
9. The method as claimed in claim 5, further comprises, managing the node [506] by the processing unit [304], at the NMS [504], based on the FCAPS attributes received from the node [506].
10. The method as claimed in claim 9, wherein the managing of the node [506] based on the FCAPS attributes, comprises, identifying, at least, a fault, a configuration change, a network usage, network performance and security threats.
11. A network management system [504] for managing a node, the network management system [504] comprising:
- a transceiver unit [302], wherein the transceiver unit [302] is configured to:
• transmit, one or more health status check requests to one or more instances of a node [506], wherein each health status check request from the one or more health status check requests is for at least one instance from the one or more instances of the node [506],
• receive, a health status response from each of the one or more instances of the node [506] based on the one or more health status check requests; and
- a processing unit [304], connected to at least the transceiver unit [302], wherein the
processing unit [304] is configured to

• determine, one of a node instance up status and a node instance down status for each of the one or more instances of the node [506] based on the received health status response from each of the one or more instances of the node [506], and
• request, one or more attributes associated with the node [506], in an event of determining the node instance up status for the one or more instances of the node [506].

12. The network management system [504] as claimed in claim 11, wherein the one or more health status check requests are transmitted by the transceiver unit [302] at a pre-configured time interval.
13. The network management system [504] as claimed in claim 11, wherein the health status response from each of the one or more instances of the node [506] comprises one or more parameters.
14. The network management system [504] as claimed in claim 13, wherein the one or more parameters comprise at least a computing resource information, a network information and a storage information.
15. The network management system [504] as claimed in claim 11, wherein the one or more attributes requested from the node [506], in an event of determining the node instance up status for the one or more instances of the node [506], are FCAPS (fault, configuration, accounting, performance, security) attributes.
16. The network management system [504] as claimed in claim 11, wherein the processing unit [304] is further configured to store in a predetermined database [606], the health status response received from each of the one or more instances of the node [506].
17. The network management system [504] as claimed in claim 13, wherein the processing unit [304] is further configured to trigger, an alarm in an event of determining the node instance down status for at least one instance from the one or more instances of the node [506], based on the one or more parameters received in the health status response.
18. The network management system [504] as claimed in claim 17, wherein the processing unit [304] is further configured to detect one or more issues with the at least one instance

from the one or more instances of the node [506] based on the alarm and performing a remedial action for the detected one or more issues.
19. The network management system [504] as claimed in claim 15, wherein the processing unit [304] is further configured to manage the node [506] based on the FCAPS attributes associated with the node.
20. The network management system [504] as claimed in claim 19, wherein the managing of the node [506] by the processing unit [304], based on the FCAPS attributes comprises, identifying, at least, a fault, a configuration change, a network usage, network performance and security threats.