EP-4740399-A1 - METHOD AND SYSTEM FOR MONITORING IN REAL TIME NETWORK FUNCTION(S) STATUS

EP4740399A1EP 4740399 A1EP4740399 A1EP 4740399A1EP-4740399-A1

Abstract

The present disclosure relates to a method and a system for monitoring in real time one or more network functions status The disclosure encompasses: at a Network Repository Function (NRF) [302], determining a heartbeat message receipt status; detecting the unsuccessful heartbeat message receipt status associated with a target NF; generating automatically an alarm associated with the target NF; detecting automatically a registration success status of the target NF; and monitoring in real time the one or more NF status based on the heartbeat message receipt status and the alarm.

Inventors

Shetty, Mukta
BHATNAGAR, AAYUSH
Kalavadiya, Milankumar
Joshi, Yugandhara
GUPTA, ADITYA
Banka, Venkatakrishna
SINHA, ANURAG

Assignees

Jio Platforms Limited

Dates

Publication Date: 20260513
Application Date: 20240613

Claims (15)

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.
15. A non-transitory computer readable storage medium for monitoring in real time one or more Network Functions (NF) status, the storage medium comprising executable code which, when executed by one or more units of a system [300], causes: ^ a determination unit [301] 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], 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], 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] 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], 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.

Description

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 heartb