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 FAULT MANAGEMENT IN A NETWORK”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.
2
METHOD AND SYSTEM FOR FAULT MANAGEMENT IN A NETWORK
FIELD OF THE DISCLOSURE
[0001]
Embodiments of the present disclosure generally relate to network 5 management systems. More particularly, embodiments of the present disclosure relate to methods and systems for fault management in a network.
BACKGROUND
10
[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, 15 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 20 based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized 25 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
3
technology has become more advanced, sophisticated, and capable of delivering
more services to its users.
[0004]
Traditional Network Management Systems (NMS) often struggle to handle the vast amount of fault management data generated by 5G Core Network 5 Functions (NFs). This can result in delays or inaccuracies in real-time monitoring. Older systems may not be designed to scale horizontally to meet the growing demands of modern 5G networks, limiting their effectiveness as the network expands. Prior art might lack a fault-tolerant design, meaning that a failure in one node can lead to significant network downtimes or data loss. Managing the variety 10 of FCAPS (Fault, Configuration, Accounting, Performance, and Security) data often requires separate tools or manual coordination, leading to complexity and possible human errors. Traditional systems might be more reactive than proactive, primarily responding to issues as they arise rather than pre-emptively managing potential problems. Older systems might not easily integrate with new 5G network 15 architectures, requiring extensive customization or even redevelopment. Prior solutions may be monolithic in nature, making it difficult to add new features or make updates without disrupting the entire system. Further, existing systems may not adequately address all the components of FCAPS, missing out on comprehensive network management. 20
[0005]
Thus, there exists an imperative need in the art for a system and method for optimized FCAPS management in 5G Networks, that aims to streamline and secure 5G network data management through a fault-resilient microservice called FCAPS Manager. 25
SUMMARY
[0006]
This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed 30
4
description. This summary is not intended to identify the key features or the scope
of the claimed subject matter.
[0007]
An aspect of the present disclosure relates to a method for fault management in a network. The method comprises receiving, by a transceiver unit 5 at a fault, configuration, alarm, performance, and security (FCAPS) manager service (FMS), an operation request from a Network Management System (NMS). The method further comprises transmitting, by the transceiver unit at the FMS, the operation request to one or more Network Functions (NFs). The method further comprises receiving, by the transceiver unit at the FMS, a connection establishment 10 request from the one or more NFs. The method further comprises storing, by a processing unit at the FMS, the information associated with the one or more NFs, based on the connection establishment request from the one or more NFs. The method further comprises receiving, by the transceiver unit at the FMS, data from the connected one or more NFs. The method further comprises transmitting, by the 15 transceiver unit at the FMS, the data to the NMS.
[0008]
In an exemplary aspect of the present disclosure, the information associated with each of the connected one or more NFs comprises at least an NF information, a cluster name and a number of active instances of the corresponding 20 NF.
[0009]
In an exemplary aspect of the present disclosure, the operation request is at least one of a get request, a put request and a delete request, and wherein the data is Fault, Configuration, Accounting, Performance, and Security (FCAPS) data 25 comprising at least one of counters, alarms and configurations for the connected one or more NFs.
[0010]
In an exemplary aspect of the present disclosure, the operation request is received as one of a periodic and on-demand. 30
5
[0011]
In an exemplary aspect of the present disclosure, the FMS comprises one or more active nodes and one or more spare nodes.
[0012]
In an exemplary aspect of the present disclosure, the method further 5 comprises assigning, by the processing unit, a spare node from the one or more spare nodes as an assigned active node in an event of a failure of a corresponding active node from the one or more active nodes.
[0013]
In an exemplary aspect of the present disclosure, the method further 10 comprises reverting, by the processing unit, the assigned active node to the spare node in an event of a recovery of the corresponding active node.
[0014]
In an exemplary aspect of the present disclosure, the method further comprises transmitting by the transceiver unit at the FMS, an update for each of the 15 one or more NFs to the NMS post receiving the information associated with the one or more NFs.
[0015]
In an exemplary aspect of the present disclosure, the update for each of the one or more NFs comprises at least a high availability information of the cluster, 20 a virtual local area network (VLAN) detail, a service group ID, and a status of the one or more NFs.
[0016]
Another aspect of the present disclosure may relate to a system for fault management in a network. The system comprises a transceiver unit at a fault, 25 configuration, alarm, performance, and security (FCAPS) manager service, the transceiver unit configured to: receive a request from a Network Management System (NMS); transmit, the request to a cluster of one or more Network Functions (NFs); and receive, a connection establishment request from the one or more NFs in the cluster; and a processing unit at the FMS, the processing unit configured to: 30
6
store, an information associated with the connected one or more NFs based on the
connection establishment request from the one or more NFs, wherein the transceiver unit is further configured to: receive, a data from the connected one or more NFs; and transmit, the data to the NMS.
5
[0017]
Yet another aspect of the present disclosure relates to a non-transitory computer readable storage medium storing one or more instructions for fault management in a network, the one or more instructions including executable code which, when executed by one or more units of a system, causes: the transceiver unit to: receive, at the fault, configuration, alarm, performance, and security (FCAPS) 10 manager service (FMS), the request from the network management system (NMS); transmit, at the FMS, the request to the cluster of one or more network functions (NFs); and receive, at the FMS, the connection establishment request from the one or more NFs in the cluster; and the processing unit to store, at the FMS, the information associated with the connected one or more NFs based on the connection 15 establishment request from the one or more NFs; and the transceiver unit to further: receive, at the FMS, data from the connected one or more NFs; and transmit, at the FMS, the data to the NMS.
OBJECTS OF THE DISCLOSURE 20
[0018]
Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0019]
It is an object of the present disclosure to provide a system and a method 25 for fault management in a network.
[0020]
It is another object of the present disclosure to provide a system and method for handling data from one or more network functions and to collate and aggregate the data before transmitting it to a management microservice. 30
7
[0021]
It is another object of the present disclosure to provide a system and method for fault management that can operate without interruption even in the event of failure of a node of operation.
BRIEF DESCRIPTION OF THE DRAWINGS 5
[0022]
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 10 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 15 disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0023]
FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture. 20
[0024]
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 implementations of the present disclosure.
25
[0025]
FIG. 3 illustrates an exemplary block diagram of a system for fault management in a network, in accordance with exemplary implementations of the present disclosure.
8
[0026]
FIG. 4 illustrates an exemplary flow diagram of a method for fault management in a network, in accordance with exemplary implementations of the present disclosure.
[0027]
FIG. 5 illustrates an exemplary process diagram for a process for fault 5 management in a network, in accordance with exemplary implementations of the present disclosure.
[0028]
The foregoing shall be more apparent from the following more detailed description of the disclosure. 10
DETAILED DESCRIPTION
[0029]
In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of 15 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 20 problems discussed above.
[0030]
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 25 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.
30
9
[0031]
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 5 embodiments in unnecessary detail.
[0032]
It should be noted that the terms "first", "second", "primary", "secondary", "target" and the like, herein do not denote any order, ranking, quantity, or importance, but rather are used to distinguish one element from another. 10
[0033]
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 15 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.
[0034]
The word “exemplary” and/or “demonstrative” is used herein to mean 20 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 25 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. 30
10
[0035]
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 5 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 10 functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
[0036]
As used herein, “a user equipment”, “a user device”, “a smart-user-15 device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart 20 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 unit(s) which are required to implement the features of the present disclosure. 25
[0037]
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”), 30
11
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.
5
[0038]
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 refer 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 10 called.
[0039]
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 15 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.
20
[0040]
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.
25
[0041]
As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a method and a system of fault management in a network.
30
12
[0042]
FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in the FIG. 1, the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session 5 Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], 10 a Unified Data Management (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data network (DN) [130], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
15
[0043]
Radio Access Network (RAN) [104] is the part of a mobile telecommunications system that connects user equipment (UE) [102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication. 20
[0044]
Access and Mobility Management Function (AMF) [106] is a 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging. 25
[0045]
Session Management Function (SMF) [108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement. 30
13
[0046]
Service Communication Proxy (SCP) [110] is a network function in the 5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces. 5
[0047]
Authentication Server Function (AUSF) [112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
10
[0048]
Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.
15
[0049]
Network Slice Selection Function (NSSF) [116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
[0050]
Network Exposure Function (NEF) [118] is a network function that 20 exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
[0051]
Network Repository Function (NRF) [120] is a network function that acts as a central repository for information about available network functions and 25 services. It facilitates the discovery and dynamic registration of network functions.
[0052]
Policy Control Function (PCF) [122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies. 30
14
[0053]
Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
5
[0054]
Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.
[0055]
User Plane Function (UPF) [128] is a network function responsible for 10 handling user data traffic, including packet routing, forwarding, and QoS enforcement.
[0056]
Data Network (DN) [130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may 15 include but are not limited to Internet services, private data network related services.
[0057]
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 20 implementation, the computing device [200] may also implement a method for fault management in a network utilising the system [300]. In another implementation, the computing device [200] itself implements the method for fault management in the network using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as 25 disclosed in the present disclosure.
[0058]
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 30
15
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, 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 5 intermediate information during execution of the instructions to be executed by the processor [204]. Such instructions, when stored in non-transitory storage media accessible to the processor [204], render the computing device [200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory 10 (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204].
[0059]
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 15 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) 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 20 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 direction information and command selections to the processor [204], and for controlling cursor movement on the display [212]. The input device typically has two degrees 25 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.
[0060]
The computing device [200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware 30 and/or program logic which in combination with the computing device [200] causes
16
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 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, 5 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 implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions. 10
[0061]
The computing device [200] also may include a communication interface [218] 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 15 [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, 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 20 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.
[0062]
The computing device [200] can send messages and receive data, 25 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], a host [224] and the communication interface [218]. The received code may be executed by the processor [204] as it is received, 30
17
and/or stored in the storage device [
210], or other non-volatile storage for later execution.
[0063]
The present disclosure is implemented by a system [300] (as shown in FIG. 3). In an implementation, the system [300] may include the computing device 5 [200] (as shown in FIG. 2). It is further noted that the computing device [200] is able to perform the steps of a method [400] (as shown in FIG. 4).
[0064]
FIG. 3 illustrates an exemplary block diagram of the system [300] for fault management in a network, in accordance with the exemplary implementations 10 of the present disclosure. The system [300] comprises at least one transceiver unit [302], and at least one processing unit [304] connected at least to the one transceiver unit [302]. Also, all of the components / units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in FIG. 3, all units shown within the system [300] should also be assumed to be connected to 15 each other. Also, in FIG. 3 only a few units are shown; however, the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. In another implementation, the system [300] may reside in a server or a network entity. In yet another implementation, the system [300] may reside partly 20 in the server/ network entity and partly in the user device.
[0065]
The system [300] is configured for fault management in the network, with the help of the interconnection between the components/units of the system [300]. 25
[0066]
The system [300] is further communicably coupled to one or more network functions (NFs) [310], and to a network management system (NMS) [312]. In an implementation, the one or more NFs [310] may include, without limitations, PCF [122], SMF [108], NRF [120] (shown in FIG. 1) etc. The NMS [312] may be 30
18
configured to manage faults in the network by accumulating the faults from the
different NFs [310] in the network. The system [300] may be further communicably coupled with a database [316]. The database [316] may be further communicably coupled with the NFs [310], and the NMS [312].
5
[0067]
The NMS [312] is a platform that enables the monitoring and management of a network. The NMS [312] is configured to identify, configure, monitor, update and troubleshoot network components (e.g., NFs [310]) in the network. The NMS [312] is further configured to indicate, to a user of the network, through a dashboard, the performance data collected from each network 10 component, allowing the user to make changes as required.
[0068]
The system [300] comprises a fault, configuration, alarm, performance, and security (FCAPS) manager service (FMS) [314]. In an embodiment, the FMS [314] is a microservice that is positioned between the NFs [310] and the NMS [312]. 15 In an embodiment, the system [300] is implemented in the FMS [314]. In an embodiment, the FMS [314] is co-located with a single NF [310], and is configured to receive data from the single NF [310]. In an embodiment, the FMS [314] is configured for a cluster of NFs [310]. The FMS [314] is configured to handle data from the NFs [310] before they are received at the NMS [312]. The FMS [314] is 20 further configured to perform requisite analysis, and synthesis of data from the NFs [310] to facilitate management of different aspects of the data. The different aspects of the data includes faults, configuration, accounting, performance, and security (FCAPS) data.
25
[0069]
The transceiver unit [302] is configured to receive, at the FMS [314], a request from the NMS [312]. In an embodiment, the request relates to fetching data from the NFs [310]. Specifically, the request related to fetching data from one or more connected NFs [310]. Connected NFs [310] may refer to currently functioning, or operable NFs [310] that are communicably coupled with the NMS 30
19
[312] via the FMS [314]. Further, the
data may comprise FCAPS data. In an embodiment, the data comprises counters, alarms, and configurations of the NFs [310]. In an embodiment, the alarms may be one of a raise alarm, and a clear alarm. The raise alarm may be indicative of a fault with one or more NFs, and a need to communicate the fault status with the NMS [312]. The clear alarm may be 5 indicative of a clearance of an existing fault with the one or more NFs.
[0070]
In an embodiment, the request from the NMS [312] is received by the FMS [314] as one of a periodic request, or an on-demand request. In an embodiment, the periodic request may be configured such that, at a predefined 10 instance of time or at a predefined frequency, the FMS [314] is configured to fetch the data from the NFs [310]. The periodic request may relate to general maintenance and monitoring of the NFs [310]. In another embodiment, the on-demand request may be configured such that, at the instant of receipt of the request, the FMS [314] is configured to fetch the data from the NFs [310]. The on-demand request may be 15 in response to a network event, such as a fault in one or more of the NFs [310].
[0071]
The transceiver unit [302] is further configured to transmit, at the FMS [314], the request to the NFs [310].
20
[0072]
The transceiver unit [302] is further configured to receive, at the FMS [314], a connection establishment request from the NFs [310]. The connection establishment request refers to a request for initialising a communication pathway between the one or more NFs [310] and the FMS [314] for transmission of the data from the NFs [310] to the FMS [314]. The connection establishment request may 25 further comprise information associated with the NFs [310]. The information may be used to establish the communication pathway. The information may relate to a location or address or identity of the one or more NFs [310] that would facilitate establishment of the communication pathway between the NFs [310] and the FMS
20
[314]. The information may comprise, without limitations,
identities of the NFs, cluster names of the NFs, and active instances of the NFs.
[0073]
In an embodiment, post receiving the information associated with the NFs [310], the transceiver unit [302] is further configured to transmit an update to 5 the NMS [312] relating to each of the one or more NFs [310]. In an embodiment, the update comprises one or more of high availability information of the NFs, operational status of the NFs, the latest FCAPS data relating to the NFs, identification of the NFs, etc. In an embodiment, the identification of the NFs may be through information such as, without limitation, a virtual local area network 10 detail of the NFs, a service group ID of the NFs, etc.
[0074]
The processing unit [304] is configured to store, at the FMS [314] the information associated with the one or more NFs [310]. In an embodiment, the processing unit [304] is configured to store the information associated with the NFs 15 [310] at the database [316]. In an embodiment, the processing unit [304] is further configured to generate a map of the communication pathways associated with the NFs [310] and the associated information received from the NFs [310]. In an embodiment, the processing unit [304] stores the generated map in the database [316]. The map allows future communication between the FMS [314] and the NFs 20 [310] to occur without requiring the NFs to generate a connection establishment request, as the map stored by the processing unit [304] already comprises all the information required. The FMS [314] may thus be able to operate faster by directly fetching the required data from the NFs [310].
25
[0075]
The transceiver unit [302] is further configured to receive, at the FMS [314], the data from the NFs [310] in response to the request transmitted thereon.
[0076]
Further, the transceiver unit [302] is configured to transmit, at the FMS [314] the received data to the NMS [312]. In an embodiment, the FMS [314] is 30
21
configured to further process the received
data from the NFs [310]. The processing of the data may include aggregation of the received data. The aggregation may include categorizing or classifying the received data based on a type of data (such as counter, alarm, or configuration), and the NF from which the data is received. The transceiver unit [302] is further configured to transmit the processed data to the 5 NMS [312].
[0077]
In an embodiment, the FMS [314] comprises at least one active FMS node [314-1], and one or more spare FMS nodes [314-2]. The active FMS node [314-1] is designated as a primary node, and the one or more spare FMS nodes 10 [314-2] are designated as secondary nodes. The primary node is a currently operating node, and the secondary nodes are stand-by nodes. In an event when the active FMS node [314-1] is at fault, or has failed, at least one spare FMS node [314-2] is redesignated as a primary node, and takes up operation of the FMS [314]. Once the faulty FMS node is back up, it is designated as a spare FMS node. Thus, the 15 FMS [314] is enabled to provide uninterrupted operation in the event of failure of its primary node.
[0078]
In an exemplary implementation, the NMS [312] is connected to a plurality of NFs [310] through the FMS [314]. One of the NFs [310] transmits a 20 ping to the FMS [314]. The ping may be indicative of an established connection between the NF [310] and the FMS [314]. The FMS [314] is initialized in response to the received ping, and, in turn, transmits a signal to the NMS [312]. The NMS [312] generates and transmits a request to the FMS [314] relating to fetching of the data from the connected NFs. The FMS [314], in response to the received request, 25 fetches the data from the connected NFs [310] based on an established connection between the NFs [310] and the FMS [314]. The FMS [314] further stores the information relating to the connection established between the FMS [314] and the NFs [310] as a map. The FMS [314] further processes the received data by aggregating them, and transmits the data and the processed data to the NMS [312]. 30 In a further instance of receiving, at the FMS [314] a request from the NMS [312]
22
for fetching
the data from the NFs [310], the FMS [312] uses the map stored therein, and directly fetches the data from the NFs [310] without there being a need to establish new communication pathways for the same. As a result, the process of fetching and processing data is made faster.
5
[0079]
FIG. 4 illustrates an exemplary flow diagram of a method [400] for fault management in the network, in accordance with exemplary implementations of the present disclosure. In an implementation the method [400] is performed by the system [300] (shown in FIG. 3). Further, in an implementation, the system [300] may be present in a server device to implement the features of the present 10 disclosure. Also, as shown in FIG. 4, the method [400] starts at step [402].
[0080]
At step [404], the method [400] comprises receiving, by the transceiver unit [302], at the FMS [314], the request from the NMS [312].
15
[0081]
At step [406], the method [400] comprises transmitting, by the transceiver unit [302], at the FMS [314], the request to the one or more from NFs [310].
[0082]
At step [408], the method [400] comprises receiving, by the transceiver 20 unit [302], at the FMS [314], the connection establishment request from the NFs [310].
[0083]
At step [410], the method [400] comprises storing, by the processing unit [304], at the FMS [314], the information associated with the connected one or 25 more NFs [310] based on the connection establishment request from the one or more NFs [310].
[0084]
At step [412], the method [400] comprises receiving, by the transceiver unit [302], at the FMS [314], data from the NFs [310]. 30
23
[0085]
At step [414], the method [400] comprises transmitting, by the transceiver unit [302], at the FMS [314], the data to the NMS [312].
[0086]
Thereafter, at step [416], the method [400] is terminated. 5
[0087]
FIG. 5 illustrates an exemplary process flow diagram for a process [500] of fault management in the network, in accordance with exemplary implementations of the present disclosure.
10
[0088]
The process [500] comprises receiving from one or more network functions (NFs) [502], at a fault, configuration, alarm, performance, and security (FCAPS) manager service (FMS) [504], a ping request. The ping request may be indicative of connectivity of the NFs [502] with the FMS [504]. The connectivity may include a high availability (HA) status of the NFs [502] with the FMS [504]. 15
[0089]
The process [500] further comprises, in response to receipt of the ping request, transmitting, by the FMS [504], a ping request to a network management system (NMS) [506]. The transmitted ping request may further contain information pertaining to selection of a port in at least one of the FMS [504] and the NMS [506] 20 for the NF [502] to establish a communication pathway.
[0090]
The process [500] further comprises, in response to receipt of the ping request by the NMS [506], receiving, by the FMS [504], from the NMS [506] a Get Request command related to fetching the data from the NFs [502]. The Get Request 25 command pertains to instructions that cause the FMS [504] to operate to receive or retrieve data from the NFs. The data may include FCAPS data. In another embodiment, the request commands can be a put request or a delete request. Further, the Get Request command may be accompanied by a mapping of the port on at least
24
one of the FMS [
504] and the NMS [506] for establishing the communication pathway between the NFs [502] and the NMS [506] through the FMS [504].
[0091]
The process [500] further comprises, requesting by the FMS [504] to the NFs [502], the data. In an embodiment, the Get Request command is broadcast 5 by the FMS [504] to all the connected NFs [502].
[0092]
The process [500] further comprises receiving, by the FMS [504], the data from the NFs [502]. The data includes FCAPS data associated with the NFs [502]. 10
[0093]
The process [500] further comprises processing the data at the FMS [504], and transmitting the data to the NMS [506].
[0094]
In an embodiment, the FMS [504] comprises at least one active FMS 15 node [504-1], and one or more spare FMS nodes [504-2]. The active FMS node [504-1] is designated as a primary node, and the one or more spare FMS nodes [504-2] are designated as secondary nodes. The primary node is a currently operating node, and the secondary nodes are stand-by nodes. In an event when the active FMS node [504-1] is at fault, or has failed, at least one spare FMS node [504-20 2] is redesignated as a primary node, and takes up operation of the FMS [504]. Once the faulty FMS node is back up, it is designated as a spare FMS node. Thus, the FMS [504] is enabled to provide uninterrupted operation in the event of failure of its primary node.
25
[0095]
As is evident from the above, the present disclosure provides a technically advanced solution for fault management in the network. The present solution ensures that synthesized and validated operational data is securely and effectively transmitted to the NMS. This enables both real-time monitoring and
25
deeper, long
-term analyses that are fundamental for robust, optimized, and adaptive management of 5G Core Networks.
[0096]
The invention of the FCAPS Manager service brings forth several distinct advantages in the realm of FCAPS (Fault, Configuration, Accounting, 5 Performance, and Security) data management and oversight within the intricate landscape of the 5G Core Network.
[0097]
Microservice Architecture: By embodying a microservice architecture, the FCAPS Manager operates as a lightweight and modular entity. This 10 architecture enhances scalability and flexibility, allowing the system to adapt to evolving network demands and efficiently accommodate additional functionalities or features.
[0098]
Comprehensive FCAPS Administration: The FCAPS Manager is 15 designed with the purpose of meticulously administering and supervising an extensive spectrum of FCAPS data, encompassing Fault, Configuration, Accounting, Performance, and Security. This comprehensive coverage ensures that no crucial operational aspects goes unnoticed or unaddressed.
20
[0099]
Fault Resilience and Continuity: The FCAPS Manager Cluster's primary-secondary arrangement, coupled with its seamless transition mechanism between Active and Spare nodes, guarantees continuous monitoring and management of FCAPS data. This fault resilience ensures that even in the event of a node failure, the nework's operational continuity remains intact, minimizing 25 disruptions.
[0100]
Simplified Troubleshooting: With effective fault management and performance monitoring, troubleshooting becomes more streamlined. We can quickly identify the source of issues and apply targeted fixes. 30
26
[0101]
The present disclosure further discloses a non-transitory computer readable storage medium storing one or more instructions for fault management in the network, the one or more instructions include executable code which, when executed by one or more units of a system [300], causes: the transceiver unit [304] 5 to: receive, at the fault, configuration, alarm, performance, and security (FCAPS) manager service (FMS) [314], the request from the network management system (NMS) [312]; transmit, at the FMS [314], the request to the cluster of one or more network functions (NFs) [310]; and receive, at the FMS [314], the connection establishment request from the one or more NFs [310] in the cluster; and the 10 processing unit [304] to store, at the FMS [314], the information associated with the connected one or more NFs [310] based on the connection establishment request from the one or more NFs [310]; and the transceiver unit [302] to further: receive, at the FMS [314], data from the connected one or more NFs [310]; and transmit, at the FMS [314], the data to the NMS [312]. 15
[0102]
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 20 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.
[0103]
Further, in accordance with the present disclosure, it is to be 25 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 30
27
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 [400] for fault management in a network, the method [400] comprising:
-
receiving, by a transceiver unit [302] at a fault, configuration, alarm, performance, and security (FCAPS) manager service (FMS) [314], an operation request from a Network Management System (NMS) [312];
-
transmitting, by the transceiver unit [302] at the FMS [314], the operation request to one or more Network Functions (NFs) [310];
-
receiving, by the transceiver unit [302] at the FMS [314], a connection establishment request from the one or more NFs [310];
-
storing, by a processing unit [304] at the FMS [314], the information associated with the one or more NFs [310], based on the connection establishment request from the one or more NFs [310];
-
receiving, by the transceiver unit [302] at the FMS [314], data from
the connected one or more NFs [302]; and
-
transmitting, by the transceiver unit [302] at the FMS [314], the data to the NMS [312].

2.The method [400] as claimed in claim 1, wherein the information associated 20 with each of the connected one or more NFs [310] comprises at least an NF information, a cluster name and a number of active instances of the corresponding NF.

3.The method [400] as claimed in claim 1, wherein the operation request is at 25 least one of a get request, a put request and a delete request, and wherein the data is Fault, Configuration, Accounting, Performance, and Security (FCAPS) data comprising at least one of counters, alarms and configurations for the connected one or more NFs [310].

4.The method [400] as claimed in claim 3, wherein the operation request is received as one of a periodic and on-demand.

5.The method [400] as claimed in claim 1, wherein the FMS [314] comprises one or more active nodes [314-1] and one or more spare nodes [314-2]. 5

6.The method [400] as claimed in claim 5, wherein the method [400] further comprises:
-
assigning, by the processing unit [304], a spare node [314-2] from the one or more spare nodes [314-2] as an assigned active node [314-1] in 10 an event of a failure of a corresponding active node [314-1] from the one or more active nodes [314-1].

7.The method [400] as claimed in claim 6, wherein the method [400] further comprises: 15
-
reverting, by the processing unit [304], the assigned active node to the spare node in an event of a recovery of the corresponding active node.

8.The method [400] as claimed in claim 1, wherein the method [400] further comprises: 20
-
transmitting by the transceiver unit [302] at the FMS [314], an update for each of the one or more NFs [310] to the NMS [312], post receiving the information associated with the one or more NFs [310].

9.The method [400] as claimed in claim 8, wherein the update for each of the 25 one or more NFs [310] comprises at least a high availability information of the cluster, a virtual local area network (VLAN) detail, a service group ID, and a status of the one or more NFs.

10.A system [300] for fault management in a network, the system [300] comprising:
-
a transceiver unit [302] at a fault, configuration, alarm, performance, and security (FCAPS) manager service (FMS) [314], the transceiver unit [302] configured to: 5
o
receive a request from a Network Management System (NMS) [312];
o
transmit, the request to a cluster of one or more Network Functions (NFs) [310]; and
o
receive, a connection establishment request from the one or more 10 NFs [310] in the cluster;
-
a processing unit [304] at the FMS [314] connected at least to the transceiver unit [302], the processing unit [304] configured to:
o
store, an information associated with the connected one or more NFs [310] based on the connection establishment request from 15 the one or more NFs [310]; and
-
the transceiver unit [302] is further configured to:
o
receive, a data from the connected one or more NFs [310]; and
o
transmit, the data to the NMS [312].

11.The system [300] as claimed in claim 10, wherein the information associated with each of the connected one or more NFs [310] comprises at least an NF information, a cluster name and a number of active instances of the corresponding NF.

12.The system [300] as claimed in claim 10, wherein the operation request is at least one of a get request, a put request and a delete request, and wherein the data is Fault, Configuration, Accounting, Performance, and Security (FCAPS) data comprising at least one of counters, alarms and configurations for the connected one or more NFs [310]. 30

13.The system [300] as claimed in claim 12, wherein the operation request from the NMS [312] is received by the FMS [314] as one of periodic and on-demand.

14.The system [300] as claimed in claim 10, wherein the FMS [314] comprises 5 one or more active nodes [314-1] and one or more spare nodes [314-2].

15.The system [300] as claimed in claim 14, wherein the processing unit [304] is configured to assign a spare node [314-2] from the one or more spare nodes [314-2] as an assigned active node [314-1] in an event of a failure of 10 a corresponding active node [314-1] from the one or more active nodes [314-1].

16.The system [300] as claimed in claim 15, wherein the processing unit [304] is configured to revert the assigned active node to the spare node in an event 15 of a recovery of the corresponding active node.

17. The system [300] as claimed in claim 10, wherein, post receiving the information associated with the connected one or more NFs [310], the transceiver unit [302] is configured to transmit, at the FMS [314], an update 20 for each of the connected one or more NFs [310] to the NMS [312].

18.The system [300] as claimed in claim 17, wherein the update for each of the connected one or more NFs [310] comprises at least high availability information of the cluster, virtual local area network (VLAN) details, 25 service group ID, status of the connected one or more NFs.

Dated this the 5th Day of September, 2023