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 MONITORING IN REAL TIME NETWORK FUNCTION(s)
STATUS”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR MONITORING IN REAL TIME NETWORK FUNCTION(s)
STATUS
TECHNICAL FIELD OF THE DISCLOSURE
[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to monitoring in real time one or more network functions status.
BACKGROUND OF THE DISCLOSURE
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high¬speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] There is a compelling need for monitoring and managing the suspension of Network Function (NF) instances by a Network Resource Function (NRF) in order to ensure a smooth operation and optimal performance of network infrastructures. One or more suspensions may occur due to various reasons, such as failures or the discontinuation of subsequent Heartbeat requests. Without effective monitoring in place, it becomes challenging to promptly detect and respond to these suspensions, which may lead to potential service disruptions and inefficiencies in the network. By implementing a robust monitoring and management system, organizations can proactively identify suspension events, generate alarms, and facilitate timely actions to address the issues. This helps in minimizing downtime,

maximizing network availability, and ensuring an optimal user experience. The need for an innovative system and method to monitor in real time one or more Network Functions (NF) status is crucial for maintaining the stability, reliability, and efficiency of modern network infrastructures.
[0005] Further, over the period of time various solutions have been developed to improve the performance of communication devices and to monitor in real time suspended a Network Function (NF) instance by a Network Resource Function (NRF). However, there are certain challenges with existing solutions. One such major limitation is the lack of real-time monitoring capabilities. The existing solutions often rely on periodic or infrequent checks, which can result in delays in detecting suspensions and responding to them promptly. This limitation increases the risk of service disruptions and inefficiencies in the network. Additionally, the prior known solutions often lack an effective alarm system to immediately alert network administrators about suspension events. Without timely notifications, administrators may not be aware of suspensions until they have already caused disruptions, leading to extended downtime and reduced performance. Furthermore, the existing solutions fail to provide a comprehensive system and method for detecting suspensions, generating alarms, and facilitating timely management of NF instances.
[0006] Thus, there exists an imperative need in the art to address the above-mentioned problems, which the present disclosure aims to address.
SUMMARY OF THE DISCLOSURE
[0007] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0008] An aspect of the present disclosure may relate to a method for monitoring in real time one or more network functions status. The method comprises determining, by a determination unit at a Network Repository Function (NRF), a heartbeat message receipt status associated with each Network Function (NF) from the one or more Network Functions (NFs), wherein the heartbeat message receipt status is at least one of a successful heartbeat message receipt status and an unsuccessful heartbeat message receipt status; detecting, by an analysis unit, at the NRF, the unsuccessful heartbeat message receipt status associated with a target NF from the one or more NFs; generating automatically, by a generation unit, at the NRF, an alarm associated with the target NF, the alarm associated with at least a set of NFs information associated with the target NF and a unique NF instance ID associated with the target NF, wherein the alarm is generated based on the unsuccessful heartbeat message receipt status; detecting automatically, by the analysis unit, at the NRF, a registration success status of the target NF

based on the successful heartbeat message receipt status associated with the target NF; and monitoring in real time, by a monitoring unit, at the NRF, the one or more NF status based on at least the heartbeat message receipt status associated with each NF from the one or more NFs and the alarm associated with said each NF.
[0009] In an exemplary aspect of the present disclosure, the method further comprises that wherein the successful heartbeat message receipt status is determined at the NRF in an event the NRF detects a successful receipt of a heartbeat message at the NRF from the NF, and wherein the unsuccessful heartbeat message receipt status is determined at the NRF in an event the NRF detects an unsuccessful receipt of the heartbeat message at the NRF from the NF.
[0010] In an exemplary aspect of the present disclosure, the method further comprises that wherein the heartbeat message is received at the NRF from the NF at a predefined time interval.
[0011] In an exemplary aspect of the present disclosure, the method further comprises that wherein the unique NF instance ID is generated by a UUID (Universal Unique Identifier) generating unit in a predefined format.
[0012] In an exemplary aspect of the present disclosure, the method further comprises that wherein said unique NF instance ID is allocated to one NF instance from the one or more NF instances.
[0013] In an exemplary aspect of the present disclosure, the method further comprises transmitting by a transceiver unit to a centralized monitoring module, the generated alarm associated with the target NF.
[0014] In an exemplary aspect of the present disclosure, the method further comprises updating, by the analysis unit, the NF status of the target NF to a suspended status based on the detection of the unsuccessful heartbeat message receipt status and a predefined threshold value.
[0015] Another aspect of the present disclosure may relate to a system for monitoring in real time one or more Network Functions (NF) status. The system comprises a determination unit configured to determine, at a Network Repository Function (NRF), a heartbeat message receipt status associated with each Network Function (NF) from the one or more Network Functions (NFs), wherein the heartbeat message receipt status is at least one of a successful heartbeat message receipt status and an unsuccessful heartbeat message receipt status. The system further comprises an analysis unit connected to at least the determination unit, and the analysis unit is configured to detect, at the NRF, the unsuccessful heartbeat message receipt status associated with a target NF from the one or more NFs. The system further

comprises a generation unit connected to at least the analysis unit, and the generation unit is configured to generate automatically, at the NRF, an alarm associated with the target NF, the alarm associated with at least a set of NFs information associated with the target NF and a unique NF instance ID associated with the target NF, wherein the alarm is generated based on the unsuccessful heartbeat message receipt status. The system further comprises that the analysis unit is further configured to detect automatically, at the NRF, a registration success status of the target NF based on the successful heartbeat message receipt status associated with the target NRF. And finally, the system comprises a monitoring unit connected to at least the generation unit, and the monitoring unit is configured to monitor in real time, at the NRF, the one or more NF status based on at least the heartbeat message receipt status associated with each NF from the one or more NFs and the alarm associated with said each NF.
[0016] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for monitoring in real time one or more network functions status, the instructions include executable code which, when executed by a one or more units of a system, causes: a determination unit of the system to determine, at a Network Repository Function (NRF), a heartbeat message receipt status associated with each Network Function (NF) from the one or more Network Functions (NFs), wherein the heartbeat message receipt status is at least one of a successful heartbeat message receipt status and an unsuccessful heartbeat message receipt status; an analysis unit of the system to detect, at the NRF, the unsuccessful heartbeat message receipt status associated with a target NF from the one or more NFs; a generation unit of the system to generate automatically, at the NRF, an alarm associated with the target NF, the alarm associated with at least a set of NFs information associated with the target NF and a unique NF instance ID associated with the target NF, wherein the alarm is generated based on the unsuccessful heartbeat message receipt status; the analysis unit of the system to detect automatically, at the NRF, a registration success status of the target NF based on the successful heartbeat message receipt status associated with the target NRF; and a monitoring unit of the system to monitor in real time, at the NRF, the one or more NF status based on at least the heartbeat message receipt status associated with each NF from the one or more NFs and the alarm associated with said each NF.
OBJECTS OF THE DISCLOSURE
[0017] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0018] It is an object of the present disclosure to provide a system and a method for real time monitoring of suspended a Network Function (NF) instance by a Network Resource Function (NRF).

[0019] It is another object of the present disclosure to provide a solution that generates one or more NF instance ID associated with the at least one Network Function (NF) from the from one or more Network Functions (NFs).
[0020] It is yet another object of the present disclosure to provide a solution to detect a NF instance ID associated with the target NF from the from one or more Network Functions (NFs).
DESCRIPTION OF THE DRAWINGS
[0021] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0022] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.
[0023] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0024] Fig. 3 illustrates an exemplary block diagram of a system [300] for monitoring in real time one or more network functions status, in accordance with exemplary implementations of the present disclosure.
[0025] Fig. 4 illustrates a method flow diagram indicating the process [400] for monitoring in real time one or more network functions status in accordance with exemplary implementations of the present disclosure.
[0026] FIG.5 illustrates an exemplary architecture diagram of a system [500] for monitoring in real time one or more Network Functions (NF) status, in accordance with exemplary embodiments of the present disclosure.

[0027] FIG. 6 depicts an exemplary flow chart [700] for monitoring in real time one or more Network Functions (NF) status in other words, in accordance with exemplary embodiments of the present disclosure.
[0028] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION OF THE DISCLOSURE
[0029] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
[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 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.
[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 embodiments in unnecessary detail.
[0032] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
[0033] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited

by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0034] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
[0035] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
[0036] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.

[0037] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
[0038] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0039] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
[0040] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system of monitoring in real time one or more network functions status.
[0041] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session 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], 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.
[0042] 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.
[0043] 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.
[0044] 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.
[0045] 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.
[0046] 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.
[0047] 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.
[0048] 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.
[0049] Network Exposure Function (NEF) [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
[0050] Network Repository Function (NRF) [120] is a network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.

[0051] 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.
5 [0052] Unified Data Management (UDM) [124] is a network function that centralizes the management
of subscriber data, including authentication, authorization, and subscription information.
[0053] Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services. 10
[0054] User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
[0055] Data Network (DN) [130] refers to a network that provides data services to user equipment
15 (UE) in a telecommunications system. The data services may include but are not limited to Internet
services, private data network related services.
[0056] Fig. 2 illustrates an exemplary block diagram of a computing device [1000] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation
20 of the present disclosure. In an implementation, the computing device [1000] may also implement a
method for monitoring in real time one or more network functions status utilising the system. In another implementation, the computing device [1000] itself implements the method for monitoring in real time one or more network functions status using one or more units configured within the computing device [1000], wherein said one or more units are capable of implementing the features as disclosed in the
25 present disclosure.
[0057] The computing device [1000] may include a bus [1002] or other communication mechanism for communicating information, and a hardware processor [1004] coupled with bus [1002] for processing information. The hardware processor [1004] may be, for example, a general-purpose
30 microprocessor. The computing device [1000] may also include a main memory [1006], such as a
random-access memory (RAM), or other dynamic storage device, coupled to the bus [1002] for storing information and instructions to be executed by the processor [1004]. The main memory [1006] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [1004]. Such instructions, when stored in non-transitory
35 storage media accessible to the processor [1004], render the computing device [1000] into a special-
purpose machine that is customized to perform the operations specified in the instructions. The
11

computing device [1000] further includes a read only memory (ROM) [1008] or other static storage device coupled to the bus [1002] for storing static information and instructions for the processor [1004].
[0058] A storage device [1010], such as a magnetic disk, optical disk, or solid-state drive is provided
5 and coupled to the bus [1002] for storing information and instructions. The computing device [1000]
may be coupled via the bus [1002] to a display [1012], 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 [1014], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [1002] for communicating information and command
10 selections to the processor [1004]. Another type of user input device may be a cursor controller [1016],
such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [1004], and for controlling cursor movement on the display [1012]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
15
[0059] The computing device [1000] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [1000] causes or programs the computing device [1000] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the
20 computing device [1000] in response to the processor [1004] executing one or more sequences of one
or more instructions contained in the main memory [1006]. Such instructions may be read into the main memory [1006] from another storage medium, such as the storage device [1010]. Execution of the sequences of instructions contained in the main memory [1006] causes the processor [1004] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired
25 circuitry may be used in place of or in combination with software instructions.
[0060] The computing device [1000] also may include a communication interface [1018] coupled to the bus [1002]. The communication interface [1018] provides a two-way data communication coupling to a network link [1020] that is connected to a local network [1022]. For example, the communication
30 interface [1018] 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 [1018] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [1018] sends and receives
35 electrical, electromagnetic or optical signals that carry digital data streams representing various types
of information.
12

[0061] The computing device [1000] can send messages and receive data, including program code,
through the network(s), the network link [1020] and the communication interface [1018]. In the Internet
example, a server [1030] might transmit a requested code for an application program through the
Internet [1028], the ISP [1026], the host [1024], the local network [1022] and the communication
5 interface [1018]. The received code may be executed by the processor [1004] as it is received, and/or
stored in the storage device [1010], or other non-volatile storage for later execution.
[0062] Referring to Figure 3, an exemplary block diagram of a system [300] for monitoring in real time one or more network functions status, is shown, in accordance with the exemplary implementations
10 of the present disclosure. The system [300] comprises at least one determination unit [301], at least one
network repository function (NRF) [302], at least one analysis unit [303], at least one generation unit [304], at least one monitoring unit [305], at least one universal unique identifier generating unit [306], at least one transceiver unit [307] and at least one centralized monitoring module [308]. Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise
15 indicated below. As shown in the figures all units shown within the system should also be assumed to
be connected to each other. Also, in Fig. 1 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. Further, in an implementation, the system [300] may be present in a user device to implement the features of the present disclosure. In another
20 implementation, the system [300] may reside in a server or a network entity. In yet another
implementation, the system [300] may reside partly in the server/ network entity and partly in the user device.
[0063] Further, in accordance with the present disclosure, it is to be acknowledged that the
25 functionality described for the various the components/units can be implemented interchangeably.
While specific embodiments may disclose a particular functionality of these units for clarity, it is
recognized that various configurations and combinations thereof are within the scope of the disclosure.
The functionality of specific units as disclosed in the disclosure should not be construed as limiting the
scope of the present disclosure. Consequently, alternative arrangements and substitutions of units,
30 provided they achieve the intended functionality described herein, are considered to be encompassed
within the scope of the present disclosure.
[0064] The system [300] is configured for monitoring in real time one or more network functions status, with the help of the interconnection between the components/units of the system [300]. 35
[0065] The determination unit [301] configured to determine, at a Network Repository Function (NRF) [302], a heartbeat message receipt status associated with each Network Function (NF) from the one or
13

more Network Functions (NFs), wherein the heartbeat message receipt status is at least one of a
successful heartbeat message receipt status and an unsuccessful heartbeat message receipt status. It is
to be noted that the successful heartbeat message receipt status is determined at the NRF [302] in an
event the NRF [302] detects a successful receipt of a heartbeat message at the NRF [302] from the NF
5 while the unsuccessful heartbeat message receipt status is determined at the NRF [302] in an event the
NRF [302] detects an unsuccessful receipt of the heartbeat message at the NRF [302] from the NF. It is further noted that the heartbeat message is received at the NRF [302] from the NF at a predefined time interval. The analysis unit [303] of the system [300] is configured to detect, at the NRF [302], the unsuccessful heartbeat message receipt status associated with a target NF from the one or more NFs.
10 The generation unit [304] of the system [300] is configured to generate automatically, at the NRF [302],
an alarm associated with the target NF, the alarm associated with at least a set of NFs information associated with the target NF and a unique NF instance ID associated with the target NF, wherein the alarm is generated based on the unsuccessful heartbeat message receipt status. Thus, the alarm associated with the set of NFs information and the unique NF instance ID, serves to alert network
15 administrators of potential issues or abnormalities within the NFs. For e.g., upon detecting a suspended
instance from the set of NFs, the alarm gets promptly generated thereby giving quick real-time notification and intervention to address the said issue such as service disruptions, hardware failures, configuration errors, and performance degradation etc. Thus, the alarm ensures the reliability, availability, and performance of the communication network. In another implementation of the
20 disclosure, the alarm associated with the set of NFs information may be generated along with the set of
NFs information. It is important to note that a transceiver unit [307] of the system [300] is configured to transmit to a centralized monitoring module [308], the generated alarm associated with the target NF. It is to be noted that the unique NF instance ID is generated by the UUID (Universal Unique Identifier) generating unit [306] in a predefined format. It is further noted that unique NF instance ID is allocated
25 to one NF instance from one or more NF instances. The analysis unit [303] is further configured to
detect automatically, at the NRF [302], a registration success status of the target NF based on the successful heartbeat message receipt status associated with the target NRF. And finally, the monitoring unit [305] of the system [300] is configured to monitor in real time, at the NRF [302], the one or more NF status based on at least the heartbeat message receipt status associated with each NF from the one
30 or more NFs and the alarm associated with said each NF. It is to be noted that the analysis unit [303] is
further configured to update the NF status of the target NF to a suspended status based on the detection of the unsuccessful heartbeat message receipt status and a predefined threshold value. It is to be noted that the predefined threshold value may include but not limited to time-interval based threshold, threshold based on the frequency of missed event of the heartbeat message. For e.g., the time interval
35 based predefined threshold value may be a predetermined duration within which the heartbeat message
associated with the NF is expected to be received i.e., if the heartbeat message is not received within said time frame, the alarm gets generated, thereby indicating the unsuccessful heartbeat message receipt
14

status. Also, on the other hand, the predefined threshold value based on the number of times the
heartbeat message of the NF is missed may refer to a predefined set count of consecutive missed
heartbeat messages associated with the NF before the alarm is triggered and generated i.e., if the
predefined threshold value is set to the predefined set count of 3, it means that the alarm will be
5 generated after the heartbeat message associated with the NF is missed 3 times in a row, thereby
indicating the unsuccessful heartbeat message receipt status.
[0066] It is to be noted that one or more modules, units, components (including but not limited to the determination unit [301], the network repository function (NRF) [302], the analysis unit [303], the
10 generation unit [304], the monitoring unit [305], the universal unique identifier generating unit [306],
the transceiver unit [307] and the centralized monitoring module [308]) used herein may be software modules configured via hardware modules/processor, or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a DSP core,
15 a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate
Array circuits, any other type of integrated circuits, etc.
[0067] Referring to Figure 4, an exemplary method flow diagram [400] for monitoring in real time one
or more network functions status, in accordance with exemplary implementations of the present
20 disclosure is shown. In an implementation the method [400] is performed by the system [300]. Further,
in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in Figure 4, the method [400] starts at step [402].
[0068] At step [404], the method comprises determining, by a determination unit [301] at a Network
25 Repository Function (NRF) [302], a heartbeat message receipt status associated with each Network
Function (NF) from the one or more Network Functions (NFs), wherein the heartbeat message receipt status is at least one of a successful heartbeat message receipt status and an unsuccessful heartbeat message receipt status.
30 [0069] It is important to note that the successful heartbeat message receipt status is determined at the
NRF [302] in an event the NRF [302] detects a successful receipt of a heartbeat message at the NRF [302] from the NF, and wherein the unsuccessful heartbeat message receipt status is determined at the NRF [302] in an event the NRF [302] detects an unsuccessful receipt of the heartbeat message at the NRF [302] from the NF.
35
[0070] It is further important to note that the heartbeat message is received at the NRF [302] from the NF at a predefined time interval.
15

[0071] At step [406], the method comprises detecting, by an analysis unit [303], at the NRF [302], the unsuccessful heartbeat message receipt status associated with a target NF from the one or more NFs.
5 [0072] At step [408], the method comprises generating automatically, by a generation unit [304], at
the NRF [302], an alarm associated with the target NF, the alarm comprising at least a set of NFs information associated with the target NF and a unique NF instance ID associated with the target NF, wherein the alarm is generated based on the unsuccessful heartbeat message receipt status. Thus, the alarm associated with the set of NFs information and the unique NF instance ID, serves to alert network
10 administrators of potential issues or abnormalities within the NFs. For e.g., upon detecting a suspended
instance (pertaining to the unsuccessful heartbeat message receipt status) from the set of NFs, the alarm gets promptly generated thereby giving quick real-time notification and intervention to address the said issue such as service disruptions, hardware failures, configuration errors, and performance degradation etc. Thus, the alarm ensures the reliability, availability, and performance of the communication network.
15 In another implementation of the disclosure, the alarm associated with the set of NFs information may
be generated along with the set of NFs information.
[0073] It is important to note that the unique NF instance ID is generated by a UUID (Universal Unique Identifier) generating unit [306] in a predefined format. 20
[0074] It is also important to note that unique NF instance ID is allocated to one NF instance from one or more NF instances.
[0075] At step [410], the method comprises detecting automatically, by the analysis unit [303], at the
25 NRF [302], a registration success status of the target NF based on the successful heartbeat message
receipt status associated with the target NF.
[0076] At step [412], the method comprises monitoring in real time, by a monitoring unit [305], at the
NRF [302], the one or more NF status based on at least the heartbeat message receipt status associated
30 with each NF from the one or more NFs and the alarm associated with said each NF.
[0077] The method further comprises transmitting by a transceiver unit [307] to a centralized monitoring module [308], the generated alarm associated with the target NF.
35 [0078] The method also comprises updating, by the analysis unit [303], the NF status of the target NF
to a suspended status based on the detection of the unsuccessful heartbeat message receipt status and a predefined threshold value. It is to be noted that the predefined threshold value may include but not
16

limited to time-interval based threshold, threshold based on the frequency of missed event of the
heartbeat message. For e.g., the time interval based predefined threshold value may be a predetermined
duration within which the heartbeat message associated with the NF is expected to be received i.e., if
the heartbeat message is not received within said time frame, the alarm gets generated, thereby
5 indicating the unsuccessful heartbeat message receipt status. Also, on the other hand, the predefined
threshold value based on the number of times the heartbeat message of the NF is missed may refer to a
predefined set count of consecutive missed heartbeat messages associated with the NF before the alarm
is triggered and generated i.e., if the predefined threshold value is set to the predefined set count of 3,
it means that the alarm will be generated after the heartbeat message associated with the NF is missed
10 3 times in a row, thereby indicating the unsuccessful heartbeat message receipt status.
[0079] Thereafter, the method terminates at step [414].
[0080] The present disclosure further discloses a non-transitory computer readable storage medium
15 storing instructions for monitoring in real time one or more network functions status, the instructions
include executable code which, when executed by a one or more units of a system [300], causes: a determination unit [301] of the system [300] to determine, at a Network Repository Function (NRF) [302], a heartbeat message receipt status associated with each Network Function (NF) from the one or more Network Functions (NFs), wherein the heartbeat message receipt status is at least one of a
20 successful heartbeat message receipt status and an unsuccessful heartbeat message receipt status; an
analysis unit [303] of the system [300] to detect, at the NRF [302], the unsuccessful heartbeat message receipt status associated with a target NF from the one or more NFs; a generation unit [304] of the system [300] to generate automatically, at the NRF [302], an alarm associated with the target NF, the alarm associated with at least a set of NFs information associated with the target NF and a unique NF
25 instance ID associated with the target NF, wherein the alarm is generated based on the unsuccessful
heartbeat message receipt status; the analysis unit [303] of the system [300] to detect automatically, at the NRF [302], a registration success status of the target NF based on the successful heartbeat message receipt status associated with the target NRF; and a monitoring unit [305] of the system [300] to monitor in real time, at the NRF [302], the one or more NF status based on at least the heartbeat message receipt
30 status associated with each NF from the one or more NFs and the alarm associated with said each NF.
[0081] Referring to Figure 5, an exemplary architecture diagram of a system [500] for monitoring in
real time one or more Network Functions (NF) status, in accordance with exemplary embodiments of
the present disclosure. Further, the system [500] as shown in Figure 5 comprises various components
35 such as a Network Repository Function (NRF) unit, involved in implementation of the features of the
present disclosure. The system [500] comprises of at least one of Session Management Function (SMF), at least one of Access and Mobility Function (AMF), at least one of Charging Function (CHF), at least
17

one of Gateway Mobile Location Centre (GMLC), at least one of Policy Control Function (PCF) and at
least one of Location management function (LMF). The SMF is a 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
5 enforcement. The AMF 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. The CHF is a network function which supports both session-based charging and event-based charging scenarios, with or without unit reservation, including new 5G capabilities such as but not limited to network slicing. The GMLC is the network entity in the 5G Core
10 Network (5GC). Within the 5GC, the GMLC offers services to the AMF, GMLC and NEF via the ngmlc
service-based interface. The PCF is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies. The LMF is a network function in a 5G Core Network to provide positioning functionality by means to determine the geographic position of a mobile device based on downlink and uplink location measuring radio
15 signals. Also, all of the components/ units of the system [300] are assumed to be connected to each
other unless otherwise indicated below.
[0082] Also, in Fig. 5 only a few units are shown, however, the system [500] may comprise multiple such units or the system [500] may comprise any such numbers of said units, as required to implement
20 the features of the present disclosure. In another implementation, the system [500] may reside in a server
or a network entity. In yet another implementation, the system [500] may reside partly in the server/ network entity and partly in the user device. In an implementation of the present disclosure, the system [500] in conjunction with system [300] (shown in Figure 3) and method [400] (shown in Figure 4), is configured to perform monitoring in real time one or more Network Functions (NFs) (preferably having
25 a suspended NF instance) by a Network Resource Function (NRF). A Network Function Heartbeat
message (NFHM) is determined from the NRF, wherein the NFHM is at least one of a successful heartbeat receipt status and an unsuccessful heartbeat receipt status. In an implementation of the present solution, each NF from the one or more NFs sends the NFHM to the NRF periodically at a fixed time interval. In an implementation, of the present solution, each NF from the one or more NFs sends to the
30 NRF, the NFHM periodically at a pre-configured time interval. After that, the system [500] detects the
unsuccessful heartbeat receipt status. Further, in an implementation of the present solution the NRF monitors the NFHM and the unsuccessful NFHM is detected is an event, the system [500] fails to detect the NFHM from the NF for at least one of the fixed time intervals and the pre-configured time interval. Next, the system [500] in conjugation with system [300] is configured to change a status associated
35 with a target NF from the one or more NFs to suspended based on detecting the unsuccessful NFHM.
Next, the system [500] in conjugation with system [300] is configured to identify from the NRF, an alarm to ensure quick notification. Next, the system [500] in conjugation with system [300] is
18

configured to transmit the alarm to a Northbound Interface (NBI node). The NBI node here refers to a
boundary interface that connects higher-level network management systems or applications to the
network management layer for allowing the exchange of information. In an implementation of the
present solution, the alarm is generated with information of the NF instances associated with at least
5 one NF from the one or more NFs, and an NF instance ID associated with each NF from the one or
more NFs. Further, in another implementation of the present solution, the alarm transmitting, by the processing to a centralised monitoring unit for further processing. Next, the system [500] in conjugation with system [300] is configured to determine, one or more NF instance ID associated with the at least one NF from the one or more NFs. Next, the system [500] in conjugation with system [300] is
10 configured to detect, a NF instance ID associated with the target NF from the one or more NFs. In an
implementation of the present solution, determining by the system [500], the NF instance ID, comprises generating by the system [500] the NF instance ID, wherein the NF instance ID may be a unique NF instance ID associated with each NF from the one or more NFs. In another implementation of the present solution, the NF instance ID may be generated by the system [500] via a Universal Unique Identifier
15 (UUID) generator. Further, in an implementation of the present solution, the NF instance ID is generated
by the system [500] at least one of a fixed format and pre-defined format, wherein the pre-defined format is at least one of a system defined format or a user defined format. Next, the system [500] in conjugation with system [300] is configured to monitor in real time, the target NF from the one or more NFs based on the detecting by the system [500], the NF instance ID associated with the target NF from
20 the one or more NFs. In an implementation of the present solution, monitoring in real time, by the
system [500], the target NF from the one or more NFs may further comprise detecting by the NRF, an event when the suspended instance is re-registered at NRF, thus reducing need for manual intervention.
[0083] Referring to Figure 6, an exemplary flow chart [700] for monitoring in real time one or more
25 Network Functions (NF) status in other words, in accordance with exemplary embodiments of the
present disclosure. In an exemplary scenario of the present solution, the following step-by-step
procedure for initiating a load attribute scheduling from a network repository function (NRF) may be
followed:
Each NF sends NF Heartbeat message to NRF periodically at fixed time interval and NRF monitors this
30 heartbeat message and changes the status of NF to Suspended if it detects that NF has not send heartbeat
message for more than configured time.
Once NRF detects missed heartbeat, it generates alarm to ensure quick notification and forwards alarm
to NBI node for centralized monitoring.
Alarm is generated with information of NF instances and key parameter is NF instance ID, which is
35 generated by UUID generator. In our case, we are generating NF instance ID uniquely within network
by using fixed format.
19

By keeping NF instance ID fixed for NFs, NRF can detect when suspended instance is re-registered at NRF, reducing need for manual intervention.
[0084] As is evident from the above, the present disclosure provides a technically advanced solution
5 for monitoring in real time one or more network functions status. The present solution as disclosed
herein provides several technical effects. Firstly, it enables real-time monitoring of Network Function (NF) instances' suspension status by the Network Repository Function (NRF), ensuring immediate awareness of any state changes. This allows for proactive identification of issues and prompt intervention. Additionally, the solution facilitates the generation of alarms as soon as a suspended
10 instance is detected, ensuring quick notification and enabling timely troubleshooting. Furthermore, the
invention automates the clearance of alarms when a suspended instance re-registers at the NRF, reducing the need for manual intervention and streamlining operational processes. Lastly, the unique management of instance IDs for NF instances across the network ensures effective alarm clearance logic, even if an NF undergoes maintenance and comes back online. Further, the present novel solution
15 offers several technical advantages. Firstly, the real-time monitoring capability enhances network
performance by providing up-to-date information on the suspension status of NF instances. This allows for proactive troubleshooting and efficient resource allocation. The proactive alarm generation ensures that any issues with suspended instances are immediately brought to the attention of network administrators, enabling them to take prompt action. The automatic alarm clearance feature reduces
20 manual effort and enhances operational efficiency by clearing alarms when suspended instances are re-
registered. Finally, the unique instance ID management ensures consistent and reliable alarm clearance logic, even when NF instances go offline for maintenance and return to operation. This enhances the reliability and effectiveness of the monitoring system, minimizing disruptions and improving overall network performance.
25
[0085] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art,
30 whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative
and non-limiting.
35
20

We Claim:
1. A method [400] for monitoring in real time one or more Network Functions (NF) status, the
method [400] comprising:
- determining, by a determination unit [301] at a Network Repository Function (NRF) [302], a heartbeat message receipt status associated with each Network Function (NF) from one or more Network Functions (NFs), wherein the heartbeat message receipt status is at least one of a successful heartbeat message receipt status and an unsuccessful heartbeat message receipt status;
- detecting, by an analysis unit [303], at the NRF [302], the unsuccessful heartbeat message receipt status associated with a target NF from the one or more NFs;
- generating automatically, by a generation unit [304], at the NRF [302], an alarm associated with the target NF, the alarm associated with at least a set of NFs information associated with the target NF and a unique NF instance ID associated with the target NF, wherein the alarm is generated based on the unsuccessful heartbeat message receipt status;
- detecting automatically, by the analysis unit [303], at the NRF [302], a registration success status of the target NF based on the successful heartbeat message receipt status associated with the target NF; and
- monitoring in real time, by a monitoring unit [305], at the NRF [302], the one or more NF status based on at least the heartbeat message receipt status associated with each NF from the one or more NFs and the alarm associated with said each NF.

2. The method [400] as claimed in claim 1, wherein the successful heartbeat message receipt status is determined at the NRF [302] in an event the NRF [302] detects a successful receipt of a heartbeat message at the NRF [302] from the NF, and wherein the unsuccessful heartbeat message receipt status is determined at the NRF [302] in an event the NRF [302] detects an unsuccessful receipt of the heartbeat message at the NRF [302] from the NF.
3. The method [400] as claimed in claim 2, wherein the heartbeat message is received at the NRF [302] from the NF at a predefined time interval.
4. The method [400] as claimed in claim 1, wherein the unique NF instance ID is generated by a UUID (Universal Unique Identifier) generating unit [306] in a predefined format.
5. The method [400] as claimed in claim 4, wherein said unique NF instance ID is allocated to one NF instance from one or more NF instances.

6. The method [400] as claimed in claim 1 further comprising: transmitting by a transceiver unit [307] to a centralized monitoring module [308], the generated alarm associated with the target NF.
7. The method [400] as claimed in claim 1 further comprising: updating, by the analysis unit [303], the NF status of the target NF to a suspended status based on the detection of the unsuccessful heartbeat message receipt status and a predefined threshold value.
8. A system [300] for monitoring in real time one or more Network Functions (NF) status, the system [300] comprises:

• a determination unit [301] configured to determine, at a Network Repository Function (NRF) [302], a heartbeat message receipt status associated with each Network Function (NF) from one or more Network Functions (NFs), wherein the heartbeat message receipt status is at least one of a successful heartbeat message receipt status and an unsuccessful heartbeat message receipt status;
• an analysis unit [303] connected to at least the determination unit [301], the analysis unit [303] configured to detect, at the NRF [302], the unsuccessful heartbeat message receipt status associated with a target NF from the one or more NFs;
• a generation unit [304] connected to at least the analysis unit [303], the generation unit [304] configured to generate automatically, at the NRF [302], an alarm associated with the target NF, the alarm associated with at least a set of NFs information associated with the target NF and a unique NF instance ID associated with the target NF, wherein the alarm is generated based on the unsuccessful heartbeat message receipt status;
• the analysis unit [303] is further configured to detect automatically, at the NRF [302], a registration success status of the target NF based on the successful heartbeat message receipt status associated with the target NF; and
• a monitoring unit [305] connected to at least the generation unit [304], the monitoring unit [305] configured to monitor in real time, at the NRF [302], the one or more NF status based on at least the heartbeat message receipt status associated with each NF from the one or more NFs and the alarm associated with said each NF.
9. The system [300] as claimed in claim 8, wherein the successful heartbeat message receipt status
is determined at the NRF [302] in an event the NRF [302] detects a successful receipt of a
heartbeat message at the NRF [302] from the NF, and wherein the unsuccessful heartbeat message
receipt status is determined at the NRF [302] in an event the NRF [302] detects an unsuccessful
receipt of the heartbeat message at the NRF [302] from the NF.

10. The system [300] as claimed in claim 9, wherein the heartbeat message is received at the NRF [302] from the NF at a predefined time interval.
11. The system [300] as claimed in claim 8, wherein the unique NF instance ID is generated by a UUID (Universal Unique Identifier) generating unit [306] in a predefined format.
12. The system [300] as claimed in claim 11, wherein said unique NF instance ID is allocated to one NF instance from one or more NF instances.
13. The system [300] as claimed in claim 8 further comprising a transceiver unit [307] configured to transmit to a centralized monitoring module [308], the generated alarm associated with the target NF.
14. The system [300] as claimed in claim 8 wherein the analysis unit [303] is further configured to update the NF status of the target NF to a suspended status based on the detection of the unsuccessful heartbeat message receipt status and a predefined threshold value.