System and method for managing fcaps data

Abstract

A method (400) and a system (108) for managing fault, configuration, accounting, performance, security (FCAPS) data of one or more network function (NF) clusters (110) in a network (106) are described. A centralized data manager (116) is initialized with a defined configuration. The centralized data manager (116) establishes a connection with a network management system (NMS) (114) and initializes a defined interface to set up a connection with each of the one or more NF clusters (110) to be monitored. Upon initializing the defined interface, the centralized data manager (116) sets up a connection to each of the plurality NF clusters (110) and collects FCAPS data. The collected FCAPS data is then processed to generate a centralized FCAPS data. Finally, the centralized FCAPS data is presented on a user interface (UI) of the NMS (114).

Description

SYSTEM AND METHOD FOR MANAGING FCAPS DATARESERVATION OF RIGHTS

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

[0002] The present disclosure relates generally to the field of communication systems. More particularly, the present disclosure relates to systems and methods for managing Fault, Configuration, Accounting, Performance, and Security (FCAPS) data.DEFINITION

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

[0004] The term “Network Function (NF)” used hereinafter in the specification refers to a specific software or hardware component within a network and is designed to perform a particular function, such as routing, switching, firewalling, load balancing, traffic optimization, and the like, to enable network operations and enhance performance.

[0005] The term “Core network” used hereinafter in the specification refers to a central, high-capacity part of a network infrastructure that provides criticalconnectivity and routing functions. The core network is responsible for efficiently and reliably handling data traffic between various network segments or nodes.

[0006] The term “Network Management System (NMS)” used hereinafter in the specification refers to a system designed to manage, monitor, and control network resources and operations.

[0007] The term “Fault, Configuration, Accounting, Performance, and Security (FCAPS) manager” used hereinafter in the specification refers to a network service used in network management that provides a comprehensive approach for managing and monitoring health, configuration, usage, performance, and security of various network resources.

[0008] The term “Network services” used hereinafter in the specification refers to the architectural and deployment paradigm where applications are composed of small, independent services that are deployed and managed within the virtualized environment. Each network service is designed to perform a specific business function and communicates with other network services over well-defined application programming interfaces (APIs). The network service is also referred to as a microservice.

[0009] The term “Network entity” used hereinafter in the specification refers to any distinct component or element within a network that performs specific functions or roles.

[0010] The term “Network function cluster” used hereinafter in the specification refers to a group of network functions deployed together and managed as a collective unit within the network. These network functions work collaboratively to provide specific network services or capabilities.

[0011] The term “Predefined interface” used hereinafter in the specification refers to an interface established between the FCAPS manager and NF clusters to communicate or interact with each other.

[0012] The term “Hyper-text transfer protocol (HTTP) interface” used hereinafter in the specification refers to a set of protocols and methods used for communication over the Hyper-text Transfer Protocol (HTTP) between the network nodes / entities.

[0013] The term “Graphical User Interface (GUI)” used hereinafter in the specification refers to a user interface that allows users to interact with electronic devices using graphical elements such as windows, icons, buttons, and menus.

[0014] The term “Set-up connection” used hereinafter in the specification refers to a process of establishing a communication link between two or more networked devices or systems. This process involves configuring and initiating the necessary parameters and protocols to enable successful data exchange between the devices.

[0015] The term “Service endpoints” used hereafter in the specification refers to specific addresses or interfaces through which the services (e.g. network services) communicate with each other.

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

[0017] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0018] The 5G Core (5GC) network uses counters and alarms extensively for realtime fault management across various network functions (NFs). Each NF consists of multiple instances that provide fault management data, which is then sent to a network management system (NMS) dashboard for detailed monitoring.

[0019] A network-service called a FCAPS manager is used to effectively manage and oversee the extensive FCAPS (Fault, configuration, accounting, performance, and security) data. This network-service operates as a distinct network entity within the 5G Core Network. It is strategically positioned between various 5G network functions (a binding support function (BSF), a charging function (CHF), a network repository function (NRF), and a policy control function (PCF)) and the NMS that handles the complete FCAPS data. The FCAPS manager efficiently analyzes and synthesizes FCAPS data, facilitating the effective management of fault, configuration, accounting, and performance aspects within the 5G Core network.

[0020] Multiple NF clusters send large volumes of FCAPS data to the NMS, making management and monitoring laborious. Each NF cluster deployed in the network requires a dedicated FCAPS managing system to handle and process the information needed for monitoring the health and performance of each NF associated with the NF cluster. This approach is resource-intensive and necessitates the deployment of multiple FCAPS managing systems. Managing multiple FCAPS managing systems independently results in a fragmented view of network health and performance. Operating and maintaining separate FCAPS managing systems for each NF cluster consume substantial resources, including hardware, software licenses, and administrative effort. This approach raises operational costs and demands ongoing maintenance and updates for each system.

[0021] As the network expands or evolves with new NF clusters, deploying an additional FCAPS managing system for each new NF cluster becomes impractical and increases the management burden. Scaling up infrastructure in a decentralized mannercan lead to inefficiencies and inconsistent monitoring capabilities. The current setup involves redundant efforts in configuring, monitoring, and managing FC APS data across different NF clusters, complicating operational tasks and raising the risk of inconsistencies in monitoring practices and data reporting.

[0022] Hence, there is a need for a system and a method for managing FCAPS data of one or more NF clusters in the network.OBJECTIVES

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

[0024] An objective of the present disclosure is to provide a system and a method for managing fault, configuration, accounting, performance, and security (FCAPS) data of one or more network function (NF) clusters.

[0025] Another objective of the present disclosure is to manage FCAPS data for multiple network function (NF) clusters by a single network management system (NMS).

[0026] Yet another objective of the present disclosure is to connect all the NF clusters to a centralized FCAPS manager so that data can be centralized.

[0027] Yet another objective of the present disclosure is to monitor and manage health, configuration, performance, and security aspects of all NF clusters via the single interface of the NMS.

[0028] Yet another objective of the present disclosure is to add / remove the NFs to the centralized FCAPS manager during runtime based on requirement.

[0029] Other objectives and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.SUMMARY

[0030] In an exemplary embodiment, a method for managing operational data associated with one or more network function (NF) clusters is disclosed. The method comprises steps of initializing, by an initializing unit of a centralized data manager, a defined interface to communicate with each of the one or more NF clusters to be monitored. Upon initialization, monitoring, by an execution unit of the centralized data manager, the operational data associated with each of the one or more NF clusters, and communicating, by a communication unit of the centralized data manager, the monitored operational data to a network management system (NMS).

[0031] In some embodiments, the method comprises upon initializing the defined interface, establishing, by the execution unit, a connection with each of the one or more NF clusters.

[0032] In some embodiments, monitoring of the operational data comprises collecting, by a collection unit of the centralized data manager, the operational data from each of the one or more connected NF clusters via the established connection and processing, by the execution unit, the collected data to generate the monitored operational data.

[0033] In some embodiments, the method comprises establishing, by the execution unit, a connection with the NMS. The NMS is further configured to receive the monitored operational data communicated by the centralized data manager and display the monitored operational data on a user interface (UI).

[0034] In some embodiments, the method comprises storing, by the collection unit, the collected data in a database in a structured format.

[0035] In some embodiments, the operational data comprises fault, configuration, accounting, performance, and security (FCAPS) data.

[0036] In some embodiments, the method comprises performing, by the execution unit, an addition or a removal of a defined NF cluster based on real-time operational requirements.

[0037] In some embodiments, the defined interface is a hypertext transfer protocol (HTTP) interface.

[0038] In some embodiments, the method comprises initializing, by the initializing unit, the centralized data manager with a set of configurations defined by an operator.

[0039] In another exemplary embodiment, a system for managing operational data associated with one or more network function (NF) clusters is disclosed. The system comprises a centralized data manager. The centralized data manager comprises an initializing unit configured to initialize a defined interface to communicate with each of the one or more NF clusters to be monitored. Upon initializing, an execution unit is configured to monitor the operational data associated with each of the one or more NF clusters. A communication unit is configured to communicate the monitored operational data to a network management system (NMS).

[0040] In some embodiments, the execution unit is configured to establish a connection with each of the one or more NF clusters upon initializing the defined interface for each of the one or more NF clusters.

[0041] In some embodiments, to monitor the operational data, a collection unit configured to collect the operational data from each of the one or more connected NFclusters via the established connection and the execution unit configured to receive the collected data and is further configured to process the collected data to generate the monitored operational data.

[0042] In some embodiments, the execution unit is further configured to establish a connection with the NMS. The NMS is further configured to receive the monitored operational data communicated by the centralized data manager and display the monitored operational data on a user interface (UI).

[0043] In some embodiments, the collection unit is configured to store the collected data in a database in a structured format.

[0044] In some embodiments, the operational data comprises fault, configuration, accounting, performance, and security (FCAPS) data.

[0045] In some embodiments, the execution unit is configured to add or remove a defined NF cluster based on real-time operational requirements.

[0046] In some embodiments, the defined interface is a hypertext transfer protocol (HTTP) interface.

[0047] In some embodiments, the initializing unit is configured to initialize the centralized data manager with a set of configurations defined by an operator.

[0048] In yet another exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method for managing operational data associated with one or more network function (NF) clusters is disclosed. The method comprises steps of initializing, by an initializing unit of a centralized data manager, a defined interface to communicate with each of the one or more NF clusters to be monitored. Upon initialization, monitoring, by anexecution unit of the centralized data manager, the operational data associated with each of the one or more NF clusters, and communicating, by a communication unit of the centralized data manager, the monitored operational data to a network management system (NMS).BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

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

[0050] FIG. 1 illustrates an exemplary network architecture for implementing a system for managing fault, configuration, accounting, performance and security (FCAPS) data, in accordance with embodiments of the present disclosure.

[0051] FIG. 2A illustrates an exemplary system architecture for managing the FCAPS data in a network, in accordance with an embodiment of the present disclosure.

[0052] FIG. 2B illustrates an exemplary block diagram of the system for managing FCAPS data in the network, in accordance with an embodiment of the present disclosure.

[0053] FIG. 3 illustrates an exemplary flow diagram for managing the FCAPS data of network function (NF) clusters by a FCAPS manager in the network, in accordance with an embodiment of the present disclosure.

[0054] FIG. 4 illustrates an exemplary flow diagram of a method for managing operational data in the network, in accordance with an embodiment of the present disclosure.

[0055] FIG. 5 illustrates an exemplary block diagram of a computer system in which or with which embodiments of the present disclosure may be implemented.

[0056] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102-1, 102-2... 102-N - Plurality of Users104-1, 104-2... 104-N - Plurality of User Equipments106 - Network108 - System110-1, 110-2....110-N - NF Clusters112-1, 112-2... .112-N - Base Stations114 - Network Management System (NMS)116 - Centralized Data Manager / FCAPS Manager200A - System Architecture116-1 - FCAPS Active Manager / Primary FCAPS Manager116-2 - FCAPS Spare Manager / Secondary FCAPS Manager200B - Block Diagram of System201 - Processor(s) 203 - Memory205 - Plurality of Interfaces210 - Database212 - Initializing Unit214 - Communication Unit 216 - Execution Unit218 - Collection Unit300 - Flow Diagram400 - Method Flow Diagram500 - Computer system 510 - External Storage Device520 - Bus530 - Main Memory540 - Read Only Memory550 - Mass Storage Device560 - Communication Port570 - ProcessorDETAILED DESCRIPTION

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

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

[0059] 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, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms,structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0060] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

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

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

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

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

[0065] The 5G Core (5GC) network extensively uses counters and alarms for realtime fault management across various network functions (NFs). Each NF is made up of multiple instances that provide fault management data, which is then sent to a Network Management System (NMS) dashboard for detailed monitoring. A network service called a Fault, Configuration, Accounting, Performance, and Security (FCAPS) Manager is used to efficiently manage and oversee the extensive FCAPS data. This service functions as a distinct network entity within the 5GC Network, positioned strategically between various 5G network functions (such as the Binding Support Function (BSF), Charging Function (CHF), Network Repository Function (NRF), and Policy Control Function (PCF)) and the NMS, which handles the complete FCAPS data. The FCAPS Manager analyzes and synthesizes the data, facilitating the effective management of fault, configuration, accounting, and performance aspects within the 5GC network architecture.

[0066] Multiple NF clusters generate large volumes of FCAPS data, which is sent to the NMS, making monitoring and management labor-intensive. Each NF cluster deployed in the network requires a dedicated FCAPS management system to process the necessary information for monitoring the health and performance of each associated NF. This approach is resource-intensive and requires the deployment of multiple FCAPS management systems. Managing these systems independently results in a fragmented view of network health and performance.

[0067] Operating separate FCAPS management systems for each NF cluster consumes significant resources, including hardware, software licenses, and administrative effort. This setup increases operational costs and requires continuous maintenance and updates for each system. As the network expands or evolves with new NF clusters, deploying an additional FCAPS management system for each new cluster becomes impractical, adding to the management burden. Scaling infrastructure in a decentralized manner leads to inefficiencies and inconsistent monitoring capabilities.The current approach involves redundant efforts in configuring, monitoring, and managing FCAPS data across the NF clusters, complicating operations and raising the risk of inconsistencies in monitoring practices and data reporting.

[0068] Hence, there is a need for system and method for managing FCAPS data of the NF clusters in the network.

[0069] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a system and a method for managing fault, configuration, accounting, performance, security (FCAPS) data of one or more network function (NF) clusters in a network. The method comprises initializing a centralized FCAPS manager with a defined configuration. The centralized FCAPS manager establishes a connection with a network management system (NMS) and initializes an interface to set-up a connection to each of one or more NF clusters to be monitored. Upon initializing the defined interface, the centralized FCAPS manager sets up the connection to each of the plurality NF clusters to be monitored and collects the FCAPS data from each connected NF cluster. The collected FCAPS data is represented on a user interface (e.g., graphical user interface (GUI)) of the NMS. In this way, the centralized FCAPS manager provides FCAPS data to the NMS for monitoring network’s health and performance metrics. Comprehensive insights about the network's overall performance trends, potential issues, and historical data analysis help in making informed decisions for network optimization and future planning.

[0070] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings FIGS. 1-5.

[0071] FIG. 1 illustrates an exemplary network architecture (100) for implementing a system (108) for managing FCAPS data in a network (106), in accordance with embodiments of the present disclosure.Y1

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

[0073] In an embodiment, the user equipment (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the user equipment (104) may include, but is not limited to, smart phones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the users (102) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the user equipment (104) may include, but is not limited to, intelligent, multi-sensing, network-connected devices, that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

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

[0075] Referring to FIG. 1, the user equipment (104) may communicate with the system (108) via a network (106). In an embodiment, the network (106) may include at least one of a Fifth Generation (5G) network, 6G network, or the like. The network (106) may enable the user equipment (104) to communicate with other devices in the network architecture (100) and / or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network(PSTN), or the like. In an embodiment, the network (106) may include one or more base stations (112) for facilitating communication between the one or more UEs (104).

[0076] The network architecture (100) comprises a plurality of base stations (112- 1, 112-2... ,112-N). A person of ordinary skill in the art will understand that one or more base stations (112-1, 112-2... 112-N) may be individually referred to as the base station (112) and collectively referred to as the base station (112). The base station (112) may be a network infrastructure that provides wireless access to one or more terminals associated therewith. The base station may have coverage defined to be a predetermined geographic area based on the distance over which a signal may be transmitted. The base station (112) may be, but not be limited to, wireless access point, evolved NodeB (eNodeB), 5G node or next generation NodeB (gNB), wireless point, transmission / reception point (TRP), and the like. In an embodiment, the base station (112) may include one or more operational units that enable telecommunication between two or more UEs (104). In an embodiment, the one or more operational units may include, but not be limited to, transceivers, baseband unit (BBU), (remote radio unit - RRU), antennae, mobile switching centres, radio network control units, one or more processors associated thereto, and a plurality of network entities such as Access and Mobility Management Function (AMF), Session Management Function (SMF), Network Exposure Function (NEF), or any custom built functions executing one or more processor-executable instructions, but not limited thereto. Each base station (112) of the plurality of base stations (112) includes a load capacity value associated therewith, and the plurality of base stations (112) may be associated with a geographical area. In an embodiment, the geographical area may indicate the signal coverage of the set of base stations (112). The network (106) may be formed by the plurality of base stations (112-1, 112-2) communicatively coupled to enable telecommunication exchanges between the one or more UEs (104).

[0077] The network architecture (100) includes the system (108), a network management system (NMS) (114), and one or more network function (NF) clusters (110-1, 110-2....110-N). Further, the system (108) comprises a centralized data manager (116).

[0078] In an aspect, the centralized data manager (116) refers to an entity responsible for overseeing, controlling, and organizing data from various sources within the network (106) in a centralized manner. This centralization means that all data is collected, stored, and managed in one central system rather than being distributed across multiple locations or databases. The centralized data manager (116) is also referred to as a fault, configuration, accounting, performance, and security (FCAPS) manager. A person of ordinary skill in the art will appreciate that the terms “centralized data manager” and “FCAPS manager” may be used interchangeably throughout the disclosure.

[0079] In an aspect, the plurality of base stations (112) handles radio communication with the user equipments (104) and interacts with the one or more NF clusters (110) to manage user access, enforce policies, establish and manage data sessions, and handle data traffic. The centralized data manager (e.g., FCAPS manager) (116) may perform tasks such as monitoring, configuring, accounting for, optimizing, and securing the network (106), ensuring that interactions between the plurality of base stations (112) and the one or more NF clusters (110) are properly managed.

[0080] In an aspect, the centralized data manager (e.g., FCAPS manager) (116) may implement at least one FCAPS network service to manage and monitor network infrastructure effectively. In particular, the centralized data manager (116) manages the functional areas of fault, configuration, accounting, performance, and security in the network, ensuring that the network operates smoothly, securely, and efficiently.

[0081] In an aspect, the fault management is performed to detect, diagnose, and resolve network faults or issues. The fault management involves real-time monitoring of network devices and services, generation of alerts for detected issues, and tools for troubleshooting and resolving faults. In an aspect, the configuration management is performed to manage and control the configuration of network devices and services. The configuration management includes deploying, modifying, and managing configurations across network devices, tracking configuration changes, backing up configurations, and ensuring consistency. In an aspect, the accounting management is performed to track and report network resource usage and activities. The accounting management includes collecting and analyzing data on network usage, generating reports for billing or auditing, and managing usage statistics. In an aspect, the performance management is performed to monitor and optimize the performance of the network (106). The performance management is used for measuring and analyzing network performance metrics such as bandwidth, latency, and throughput. It includes performance dashboards, alerting for performance degradation, and capacity planning. In an aspect, the security management is performed to protect the network (106) from security threats and manage security policies. Security management is used to implement security measures, monitor security breaches, and manage access controls. The security management further includes intrusion detection systems, firewall management, and security policy enforcement.

[0082] In an aspect, the one or more NF clusters (110-1, 110-2....110-N) refer to a group of the network functions (NFs) that are logically or physically organized to work together within the network (106). In an aspect, the NFs are network components that perform critical roles in the operation, management, and optimization of the network (106). The NFs may include, but are not limited to, a user plane function (UPF), a session management function (SMF), an access mobility and management function (AMF), a network slice selection function (NSSF), a policy control function (PCF), etc. The UPF may handle user data traffic and perform packet routing,forwarding, and QoS (Quality of Service) enforcement. The SMF may manage session establishment, modification, and release for user connections. The SMF coordinates with the UPF to handle user data and enforce session policies. The AMF may manage the connection and mobility of user devices. The AMF handles registration, authentication, and mobility management. The NSSF may determine and allocate network slices based on user requirements and network policies. The PCF may manage and enforce policies related to QoS, access control, and network resource usage.

[0083] In an aspect, a person of ordinary skill in the art will understand that one or more NF clusters (110-1, 110-2... 110-N) may be individually referred to as the NF cluster (110) and collectively referred to as the NF clusters (110). In an aspect, the NF clusters (110) may organize network functions (e.g., user plane function (UPF), access mobility and management function (AMF), session management function (SMF), and a network slice management function (NSMF)) into logical or physical groupings to provide efficient, scalable, and reliable network services. By clustering the NF functions, the network (106) can handle large traffic volumes, manage user sessions, support network slicing, and ensure high availability and fault tolerance. For example, the UPF cluster handles user data traffic, including packet forwarding, packet inspection, and data session management. The AMF cluster manages the signaling and control plane functions related to user access and mobility. The SMF cluster manages session establishment, modification, and release. The NSMF cluster handles the creation, modification, and deletion of network slices, ensuring each slice operates according to its specific requirements. In an aspect, the network cluster may include different types of network functions.

[0084] In an embodiment, the FCAPS manager (116) may collect the FCAPS data from the one or more NF clusters (110) and generate centralized FCAPS data from the collected FCAPS data. The centralized FCAPS data is then sent to a single network management system (NMS) (e.g., NMS (114)) within the network (106). In an aspect,the network management system (NMS) is a system used to monitor, manage, and maintain a network's infrastructure. The NMS (114) provides centralized control over network devices, such as routers, switches, servers, and other network components, ensuring the network operates efficiently, securely, and reliably.

[0085] In an embodiment, the user equipment (UE) (104) is communicatively coupled with the system (108). The system (108) may receive a connection request from the UE (104). The system (108) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request. The system (108) is configured for managing fault, configuration, accounting, performance, and security (FCAPS) data of the one or more NF clusters in the network (106).

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

[0087] FIG. 2A illustrates an exemplary system architecture (200A) for managing the FCAPS data in the network (106), in accordance with an embodiment of the present disclosure.

[0088] The system architecture (200A) includes the one or more NF clusters (110), the FCAPS manager (116), and the NMS (114). The FCAPS manager (116) may be initialized with the required configuration. In an aspect, the FCAPS manager (116) may be configured with the required settings and parameters to define thresholds, configure alerts, and implement policies for monitoring and controlling network operations. In an example, threshold range may be set as CPU < 90%, memory usage as < 75%,security setting, etc. In an aspect, the FCAPS manager (116) may assign network services for managing the FCAPS data of the one or more NF clusters (110) in the network (106).

[0089] In an embodiment, the FCAPS manager (116) may establish a connection with the NMS (114). TheFCAPS manager (116) may initialize an interface (e.g., HTTP interface) to set up a connection with each of the one or more NF clusters (110) to be monitored. This approach centralizes the FCAPS (Fault, Configuration, Accounting, Performance, Security) management using the single NMS (e.g., NMS (114)) for the one or more NF clusters (110) within the network (106). This provides a centralized FCAPS-NMS architecture or platform to monitor and manage the health, configuration, performance, and security aspects of all the NF clusters (110) from the single interface.

[0090] Upon initializing the defined interface with the one or more NF clusters (110), the FCAPS manager (116) may set up the connection with each of one or more NF clusters (110) to be monitored. After the connection set-up, the FCAPS manager (116) may collect the FCAPS data from the one or more connected NF clusters (110). The FCAPS data from the one or more connected NF clusters (110) may be consolidated (i.e., collected and combined into centralized FCAPS data). The centralized FCAPS data may then be represented on the graphical user interface (GUI) of the NMS (114). So, by centralizing the FCAPS data into the NMS (114), the system (108) may provide a unified view of the entire network's health and performance metrics, thereby simplifying the troubleshooting and monitoring tasks significantly.

[0091] In one aspect, the FCAPS manager (116) may add / remove the interfaces of the NF clusters (110) at runtime if the addition / removal of the NF clusters is required. In this way, the centralization allows for easier scalability as the network (106) grows. Adding new NF clusters (110) doesn’t necessarily require deploying new FCAPS; instead, they can be integrated into the existing centralized FCAPS-NMS architecture.

[0092] In an aspect, the FCAPS manager (116) includes an FCAPS active manager (116-1) and an FCAPS spare manager (116-2). The FCAPS active manager (116-1) may be referred to as a primary FCAPS manager and the FCAPS spare manager (116- 2) may be referred to as a secondary FCAPS manager. In an aspect, the FCAPS spare manager (116-2) is on standby and ready to take the responsibilities of the FCAPS active manager (116-1) if the FCAPS active manager (116-1) fails or becomes unresponsive. In response to the detection failure of the FCAPS active manager (116- 1) due to network issues, the FCAPS spare manager (116-2) may take over to perform the tasks. This helps in maintaining continuous service and minimizes disruptions (i.e., high availability and reliability). In an aspect, the FCAPS active manager (116-1) may assign a plurality of network services (e.g., active network services and spare network services) for managing the FCAPS data of the one or more NF clusters (110). The FCAPS active manager (116-1) may activate the spare network service if the active network service fails or becomes unresponsive.

[0093] In an embodiment, the FCAPS manager (116) may comprise a plurality of FCAPS manager network services to manage functional areas (i.e., fault, configuration, accounting, performance, and security). The FCAPS manager (116) may initialize one of the plurality of FCAPS manager network services with a required configuration (e.g., setting up service endpoints, authentication, authorization, performance metrics, etc.). The FCAPS manager (116) may connect the initialized FCAPS network service to the NMS (114). The FCAPS manager (116) may initialize an interface (e.g., HTTP interface) for each of the NF clusters (110) to set up the connection for monitoring the FCAPS data. The FCAPS manager (116) may connect the FCAPS manager network service to all NF clusters (110) to be monitored. Once connected, the FCAPS manager network service may collect the data from all connected NF clusters (110). The collected data is then processed to generate the centralized data. The centralized data of each connected NF cluster is represented on a user interface (e.g., graphical user interface (GUI)) of the NMS (114). In this way, the FCAPS manager (116) maymonitor and manage the health, configuration, performance, and security aspects of all NF clusters (110). Further, information corresponding to the connected NF clusters (110) is maintained in a structured format in a database, such as a database (210).

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

[0095] FIG. 2B illustrates an exemplary block diagram (200B) of the system (108) for managing the FCAPS data in the network (106), in accordance with an embodiment of the present disclosure.

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

[0097] Referring to FIG. 2B, the system (108) may include an interface(s) (205). The interface(s) (205) may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as I / O devices, storage devices, and the like. The interface(s) (205) may facilitate communication to / from the system (108). The interface(s) (205) may also provide a communication pathway for one or more components of the system (108). Examples of such components include, but are not limited to, the FCAPS manager (116) and the database (210).

[0098] The system (108) may include the centralized data manager (i.e., the FCAPS manager) (116) and the database (210). The centralized data manager / FCAPS manager (116) may include an initializing unit (212), a communication unit (214), an execution unit (216), and a collection unit (218).

[0099] In an aspect, a person of ordinary skill in the art will understand that the FCAPS manager is also referred to as a centralized data manager and will appreciate that the terms “centralized data manager” and “FCAPS manager” may be used interchangeably throughout the disclosure.

[0100] The system (108) may manage operational data associated with one or more network function (NF) clusters (110). The operational data includes fault, configuration, accounting, performance, and security (FCAPS) data. In an aspect, the FCAPS data refers to data corresponding to fault, configuration, accounting, performance, and security of the network. The FCAPS data is used for managing and maintaining the health and efficiency of the network.

[0101] In an aspect, a person of ordinary skill in the art will understand that operational data is also referred to as the FCAPS data. A person of ordinary skill in the art will appreciate that the terms “operational data” and “FCAPS data” may be used interchangeably throughout the disclosure.

[0102] In an aspect, the fault data comprises data related to network failures, outages, or malfunctions. This data is used in fault management, which focuses on detecting, diagnosing, and resolving issues such as dropped calls, network outages, or service interruptions. It is crucial for maintaining network availability and reliability.

[0103] In an aspect, configuration data comprises data corresponding to configuration settings of network devices (e.g., routers, switches, and cell towers). The configuration data is used to configure the network’s hardware and software components, ensure proper setup of base stations, cell towers, and network elements, and maintain consistency across the network.

[0104] In an aspect, accounting data comprises data corresponding to usage data, including billing information, resource consumption data (e.g., voice minutes, and data usage), and subscriber details. This data helps to track and manage network resource usage, generate billing data, and control usage.

[0105] In one aspect, performance data comprises data corresponding to the network's operational performance, including latency, throughput, signal strength, error rates, and network traffic. This data is used to monitor the health and efficiency of the network by analyzing parameters (e.g., signal strength, call drop rates, data throughput) and overall user experience. It is essential for ensuring optimal network quality and avoiding congestion.

[0106] In an aspect, security data comprises data corresponding to the network's security status, including authentication logs, encryption details, intrusion detection, and vulnerability reports. The security data is used to protect the system / network against unauthorized access, fraud, and attacks. It involves managing encryption, authentication, and intrusion detection systems.

[0107] In an embodiment, the initializing unit (212) may perform initialization of the centralized data manager (e.g., the FCAPS manager) (116) with a definedconfiguration. The initializing unit (212) is configured to initialize the centralized data manager (116) with a set of configurations defined by an operator. The defined configuration of the FCAPS manager (116) may refer to the setup and parameters that are tailored to manage and provide effective monitoring, control, and reporting functions. The set of configurations comprises, but is not limited to, addressing and routing configuration, data traffic management configuration, security configuration, data collection configuration, data monitoring configuration, data storage configuration, service configuration, access control configuration, etc.

[0108] The communication unit (214) may establish a connection with the NMS (114). The communication unit (214) may send the FCAPS data to the NMS (114) over the established connection. In an aspect, the NMS (114) may use the FCAPS data to monitor, manage, and control the network’s operation and ensure its performance, reliability, and security.

[0109] The initializing unit (212) may initialize a defined interface to set up a connection to each of the one or more NF clusters (110) to be monitored. In an embodiment, the defined interface is a Hypertext Transfer Protocol (HTTP) interface. The HTTP interface refers to an interface used to interact with various network services, devices, and applications. It provides a convenient, often web-based way for network operators and users to manage configurations, monitor performance, and troubleshoot network issues. In an operative aspect, the HTTP interface may establish a connection between the FCAPS manager (116) and the one or more NF clusters (110) to facilitate communication with the one or more NF clusters (110).

[0110] Upon initializing the defined interface to each of the one or more NF clusters (110), the execution unit (216) may set up the connection with each of the one or more NF clusters (110) to be monitored. In an aspect, the execution unit (216) may add / remove the NF clusters (110) based on requirements. The execution unit (216) may add or remove NF clusters (110) to effectively manage the scaling of the NF clusters(110) to meet the changing requirements of the network (106). Upon detecting a sudden increase in traffic, if more load balancing functions are required to distribute traffic across the network (106), the execution unit (216) may assess the situation and determine that additional NF clusters (110) are needed, provisioning the required resources. The execution unit (216) may then add NF clusters (110) to manage the increased traffic. Furthermore, upon detecting a decrease in traffic, the operator may decide to reduce resources to save costs. In this case, underutilized NF clusters (110) are identified, and the unnecessary ones are removed or shut down.

[0111] Upon initializing the connection to each of the plurality of NF clusters (110) to be monitored, the execution unit (216) is configured to monitor the operational data associated with each of the one or more NF clusters (110). The operational data includes fault, configuration, accounting, performance, and security (FCAPS) data. To monitor the operational data, the collection unit (218) is configured to collect the operational data from each of the one or more connected NF clusters (110) via the established connection. The execution unit (216) is configured to receive the collected data from the collection unit (218). The execution unit (216) is further configured to process the collected data to generate the monitored operational data. The monitored operational data is centralized FCAPS data. The centralized FCAPS data refers to data corresponding to fault, configuration, accounting, performance, and security management that is stored and managed in a unified, centralized management platform (i.e., centralized data manager (or FCAPS manager) (116)). In an aspect, the processing of the collected data comprises, but is not limited to, filtering, cleaning, synchronization, data normalization, etc. In filtering, irrelevant or duplicate data is removed from the data. The data cleaning includes handling missing values, correcting errors, etc. The synchronization (e.g., timestamp synchronization) is performed across data sources. The data normalization includes organizing data based on relationships, standardizing units or data formats. Organizing data based on relationships includes creating relations (e.g., relational tables).

[0112] In an aspect, after setting up the connection, the execution unit (216) may receive the FCAPS data from the one or more NF clusters (110). The execution unit (216) may generate centralized FCAPS data (i.e., monitored operational data) of the collected FCAPS data from the one or more NF clusters (110).

[0113] In an embodiment, the database (210) includes data that may be either stored or generated as a result of functionalities implemented by any of the components of the processor (201) or the FCAPS manager (116). In an embodiment, the database (210) may be separate from the system (108). In an aspect, the database (210) may be part of the FCAPS manager (116). In an embodiment, the database (210) may be indicative of including, but not limited to, a relational database, a distributed database, a cloud-based database, or the like. In an aspect, data corresponding to the connected NF clusters (110) is maintained in the database (210). The data corresponding to the connected NF clusters (110) may include, but is not limited to, cluster ID, NF type, timestamp, status, fault management data (e.g., fault or issue data), configuration data (e.g., central processing unit (CPU) and memory resources allocation, storage capacity and type, IP Addressing, load balancing, security rules, threshold setting for the NF clusters), accounting data (e.g., bandwidth, CPU usage, memory usage, cost, etc.), performance data (e.g., throughput, latency, error rate, etc.), security management data (e.g., security policies and rules applied to NF clusters, security-related events and activities, etc.)

[0114] The collection unit (218) is configured to store the collected data in the database (210) in a structured format. In an example, the collected data is stored in a table format with defined relationships.

[0115] The fault data is stored in a fault table as shown in Table 1.Table 1

[0116] The configuration data is stored in the configuration table as shown in table 2:Table 2

[0117] The accounting data is stored in the accounting table as shown in table 3.Table 3

[0118] The performance data is stored in the performance table as shown in table 4:Table 4

[0119] The security data is stored in the security table as shown in table 5:Table 5

[0120] The database (210) may store the monitored operational data (i.e., centralized FCAPS data). In an aspect, centralized FCAPS data comprises all data from network devices, applications, and services related to the FCAPS. The centralized FCAPS data is stored in the database (210). This allows the network operators to havea single point of access for managing, analyzing, and reporting on network health, performance, and security.

[0121] The execution unit (216) is further configured to establish a connection with the NMS (114). The NMS (114) is configured to receive the monitored operational data communicated by the centralized data manager (116) and display the monitored operational data on the user interface (UI). In an aspect, the user interface (UI) may be a graphical user interface (GUI). The GUI is a visual interface that allows users to interact with devices through graphical icons, buttons, and menus. In an operative aspect, the GUI provides users (e.g., network operators) with quick and intuitive access to critical network data, helping them identify and resolve issues more efficiently.

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

[0123] FIG. 3 illustrates an exemplary flow diagram (300) for managing FCAPS data of the NF clusters (110) by the FCAPS manager (116) in the network (106), in accordance with an embodiment of the present disclosure.

[0124] The FCAPS manager (116) uses an application to manage the FCAPS data of the NF clusters (110). In an aspect, the application is a monitoring platform or tool used to collect network operational data and communicate the collected data to the NMS (114) to detect performance issues and provide analytics for network performance optimization.

[0125] At step (302), the flow diagram (300) includes configuring the application corresponding to the FCAPS manager (116) for managing the FC APS data of the one or more NF clusters (110) in the network (106).

[0126] At step (304), the flow diagram (300) includes performing booting up of the configured application. In an aspect, the boot up of an application refers to a process by which the application transitions from being inactive or not running to being fully operational and ready for interaction. In this way, the FCAPS manager (116) may initialize with the required configuration (e.g., setting up of threshold for CPU usage, memory usage, security settings, authentication, authorization, etc.). The FCAPS manager (116) may establish the connection with the NMS (114).

[0127] At step (306), the flow diagram (300) includes initializing, by the FCAPS manager (116), a defined interface (e.g., HTTP interface) to set up the connection with each of the one or more NF clusters (110) to be monitored.

[0128] At step (308), the flow diagram (300) includes checking, by the FCAPS manager (116), whether the initialization of the defined interface for each of the one or more NF clusters (110) to be monitored is successful or not.

[0129] At step (310), the flow diagram (300) includes, upon detecting that the initialization of the defined interface for each of the one or more NF clusters (110) to be monitored is successful, connecting, by the FCAPS manager (116), each of the one or more NF clusters (110) to be monitored via the defined interface. Upon detecting that the initialization of the defined interface for each of the one or more NF clusters (110) to be monitored is unsuccessful, the flow diagram (300) may again perform step (308), i.e., the FCAPS manager (116) may again check whether the initialization of the defined interface for each of the one or more NF clusters (110) to be monitored is successful or not.

[0130] At step (312), the flow diagram (300) includes, after connecting each of the one or more NF clusters (110) to be monitored via the defined interface, the FCAPS manager (116) may collect the centralized FCAPS data from the one or more connected NF clusters (110). The collected centralized FCAPS data is then sent to the NMS (114) to detect performance issues and provide analytics for network performance.

[0131] FIG. 4 illustrates an exemplary flow diagram of a method (400) for managing FCAPS data in the network (106), in accordance with an embodiment of the present disclosure.

[0132] At step (402), the method (400) includes initializing, by the initializing unit (212) of the centralized data manager (116), the defined interface to communicate with each of the one or more NF clusters (110) to be monitored. The centralized data manager (116) is an FCAPS manager.

[0133] In an aspect, the centralized data manager (116) may be initialized with a set of configurations defined by an operator / subject matter expert (SME) / administrator. The centralized data manager (116) may be configured with the required settings and parameters to define thresholds, configure alerts, and implement policies for monitoring and controlling network operations.

[0134] The centralized data manager (116) is initialized with the defined interface to communicate with each of the one or more NF clusters (110) to be monitored. The defined interface is a http interface. Upon initializing the defined interface, the execution unit (216) may establish a connection with each of the one or more NF clusters (110). The defined interface (e.g., HTTP interface) may establish a connection between the centralized data manager (e.g., FCAPS manager) (116) and the one or more NF clusters (110) to facilitate communication with the one or more NF clusters (110). Furthermore, the execution unit (216) of the centralized data manager (116) may perform the addition or removal of the defined NF cluster (110) based on real-timeoperational requirements. The defined NF cluster (110) is added / removed to effectively manage the scaling of the NF clusters (110) to meet the changing requirements of the network.

[0135] At step (404), the method (400) includes, upon initialization, monitoring, by the execution unit (216) of the centralized data manager (116), the operational data associated with each of the one or more NF clusters (110). The monitoring of the operational data comprises collecting, by the collection unit (218), the operational data from each of the one or more connected NF clusters (110) via the established connection and processing, by the execution unit (216), the collected data to generate the monitored operational data.

[0136] In an aspect, operational data (e.g., fault, configuration, accounting, performance, and security (FCAPS) data) is collected from each of the one or more connected NF clusters (110) via the established connection. The collection unit (218) of the centralized data manager (116) may store the collected data in the database (210) in a structured format (e.g., table format with defined relationships). The collected data is processed to generate monitored operational data (i.e., centralized FCAPS data). The database (210) may store the monitored operational data.

[0137] At step (406), the method (400) includes communicating, by the communication unit (214) of the centralized data manager (116), the monitored operational data to the network management system (NMS) (114). The centralized data manager (116) may establish a connection with the NMS (114). The NMS (114) is further configured to receive the monitored operational data communicated by the centralized data manager (116) and display the monitored operational data on a user interface (UI). The monitored operational data (i.e., centralized FCAPS data) helps the network operator manage, analyze, and report on network health, performance, and security through a single access point to the monitored operational data.

[0138] FIG. 5 illustrates an exemplary computer system (500) in which or with which embodiments of the present disclosure may be implemented.

[0139] As shown in FIG. 5, the computer system (500) may include an external storage device (510), a bus (520), a main memory (530), a read-only memory (540), a mass storage device (550), communication port(s) (560), and a processor (570). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (570) may include various modules associated with embodiments of the present disclosure. The communication port(s) (560) may be any of an RS-232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) (560) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.

[0140] The main memory (530) may be random access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (540) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (570). The mass storage device (550) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage device (550) includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.

[0141] The bus (520) communicatively couples the processor (570) with the other memory, storage, and communication blocks. The bus (520) may be, e.g., a PeripheralComponent Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (570) to the computer system.

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

[0143] The exemplary computer system (500) is configured to execute a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for managing operational data associated with one or more network function (NF) clusters. The method comprises steps of initializing, by a centralized data manager, a defined interface to communicate with each of the one or more NF clusters to be monitored, upon initializing, monitoring, by the centralized data manager, the operational data associated with each of the one or more NF clusters, and communicating, by the centralized data manager, the monitored operational data to a network management system (NMS).

[0144] The present disclosure provides technical advancements related to managing operational data (i.e., FCAPS data) associated with one or more network function (NF) clusters. The advancement addresses the limitations of existing solutions by providing a centralized data manager (e.g., FCAPS manager) to manage the FCAPS data. The centralized data manager establishes connections with each NF cluster to be monitored. After connection establishment, the centralized data manager collects thedata from each NF cluster. The collected data is then processed to generate centralized FCAPS data. Thereafter, the centralized FC APS data is provided to the NMS for monitoring the network's health and performance metrics. The NMS performs monitoring and management of the health, configuration, performance, and security aspects of all NF clusters from a single user interface (e.g., GUI) of the NMS. The centralized data manager easily adds / removes NF clusters and allows easier scalability as the network grows.

[0145] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.ADVANTEGES OF THE PRESENT DISCLOSURE

[0146] The present disclosure described herein above has several technical advantages including, but not limited to,• Providing centralized FCAPS data to the NMS for monitoring network's health and performance metrics.• Performing monitoring and management of the health, configuration, performance, and security aspects of all NF clusters from a single interface (e.g., GUI) of the NMS.• Easily adding / removing NF clusters and allowing for easier scalability as the network grows.Simplifying troubleshooting and monitoring tasks.• Efficiently handling the processing of FCAPS data.• Providing comprehensive insights into the network's overall performance trends, potential issues, and historical data analysis. This helps in making informed decisions for network optimization and future planning. • Streaming operational tasks (e.g., reporting, auditing, and compliance) through centralized FCAPS data.• Improving overall operational efficiency and reducing the complexity of managing disparate FCAPS.

Claims

CLAIMS1. A method (400) for managing operational data associated with one or more network function (NF) clusters, the method (400) comprising: initializing (402), by an initializing unit (212) of a centralized data manager ( 116), a defined interface to communicate with each of the one or more NF clusters (110) to be monitored; upon initialization, monitoring (404), by an execution unit (216) of the centralized data manager (116), the operational data associated with each of the one or more NF clusters (110); and communicating (406), by a communication unit (214) of the centralized data manager (116), the monitored operational data to a network management system (NMS) (114).

2. The method (400) as claimed in claim 1, comprising: upon initializing the defined interface, establishing, by the execution unit (216), a connection with each of the one or more NF clusters (110).

3. The method (400) as claimed in claim 2, wherein monitoring of the operational data comprises: collecting, by a collection unit (218) of the centralized data manager (116), the operational data from each of the one or more connected NF clusters (110) via the established connection; and processing, by the execution unit (216), the collected operational data to generate the monitored operational data.

4. The method (400) as claimed in claim 1, comprising: establishing, by the execution unit (216), a connection with the NMS (114), wherein the NMS (114) is configured to receive the monitoredoperational data communicated by a centralized data manager (116) and to display the monitored operational data on a user interface (UI).

5. The method (400) as claimed in claim 3, comprising: storing, by the collection unit (218), the collected data in a database in a structured format.

6. The method (400) as claimed in claim 1 , wherein the operational data comprises fault, configuration, accounting, performance, and security (FCAPS) data.

7. The method (400) as claimed in claim 1, comprising: performing, by the execution unit (216), addition or removal of a defined NF cluster (110) based on real-time operational requirements.

8. The method (400) as claimed in claim 1, wherein the defined interface is a hypertext transfer protocol (HTTP) interface.

9. The method (400) as claimed in claim 1, comprising: initializing, by the initializing unit (212), the centralized data manager (116) with a set of configurations defined by an operator.

10. A system (108) for managing operational data associated with one or more network function (NF) clusters, the system (108) comprising a centralized data manager (116), the centralized data manager (116) comprising: an initializing unit (212) configured to initialize a defined interface to communicate with each of the one or more NF clusters (110) to be monitored; upon initializing, an execution unit (216) configured to monitor the operational data associated with each of the one or more NF clusters (110); anda communication unit (214) configured to communicate the monitored operational data to a network management system (NMS) (114).

11. The system (108) as claimed in claim 10, wherein the execution unit (216) is configured to establish a connection with each of the one or more NF clusters (110) upon initializing the defined interface for each of the one or more NF clusters (110).

12. The system (108) as claimed in claim 11, wherein to monitor the operational data, a collection unit (218) configured to collect the operational data from each of the one or more connected NF clusters (110) via the established connection; and the execution unit (216) configured to receive the collected data and to process the collected data to generate the monitored operational data.

13. The system (108) as claimed in claim 10, wherein the execution unit (216) is configured to establish a connection with the NMS (114), wherein the NMS (114) is configured to receive the monitored operational data communicated by the centralized data manager (116) and to display the monitored operational data on a user interface (UI).

14. The system (108) as claimed in claim 12, wherein the collection unit (218) is configured to store the collected data in a database in a structured format.

15. The system (108) as claimed in claim 10, wherein the operational data comprises fault, configuration, accounting, performance, and security (FCAPS) data.

16. The system (108) as claimed in claim 10, wherein the execution unit (216) is configured to add or remove a defined NF cluster (110) based on real-time operational requirements.

17. The system (108) as claimed in claim 10, wherein the defined interface is a hypertext transfer protocol (HTTP) interface.

18. The system (108) as claimed in claim 10, wherein the initializing unit (212) is configured to initialize the centralized data manager (116) with a set of configurations defined by an operator.

19. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (400) for managing operational data associated with one or more network function (NF) clusters, the method (400) comprising: initializing (402), by an initializing unit (212) of a centralized data manager ( 116), a defined interface to communicate with each of the one or more NF clusters (110) to be monitored; upon initialization, monitoring (404), by an execution unit (216) of the centralized data manager (116), the operational data associated with each of the one or more NF clusters (110); andcommunicating (406), by a communication unit (214) of the centralized data manager (116), the monitored operational data to a network management system (NMS) (114).

Images