System and method for preventing false suspension notifications of network functions

Abstract

The disclosure relates to a method (400) and system (108) for preventing false suspension of a plurality of network functions (NFs) (110) in a network (106). The system (108) includes one or more network repository functions (NRFs) (112), each configured to receive operational status data from at least one NF (110) via a heartbeat request. Upon detecting cessation of the heartbeat request, each NRF (112) determines whether all mirrored NRFs (112) are interconnected. If any disconnection is identified, each NRF (112) stores the operational status data in a corresponding local database (232). Upon restoration of connectivity, each NRF (112) initiates synchronization of the operational status data with peer NRFs (112). The system (108) further compares the locally stored data and determines a current operational state of the NF (110) based on the comparison, thereby enabling accurate identification of suspended NFs and avoiding premature suspension notifications.

Description

SYSTEM AND METHOD FOR PREVENTING FALSE SUSPENSION NOTIFICATIONS OF NETWORK FUNCTIONSRESERVATION OF RIGHTS

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

[0002] The present disclosure relates generally to the field of communication systems. More particularly, the present disclosure relates to systems and methods for preventing false suspension notifications of a plurality of network functions (NFs) in a network.DEFINITIONS

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

[0004] The term ‘Network Repository Function (NRF)’ used hereinafter in the specification refers to a centralized repository, that maintains comprehensive records about various available network functions (NFs), including their capabilities, configurations, and status.

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

[0006] The term ‘Local Database’ used hereinafter in the specification refers to a high-availability storage module integrated within each NRF, configured to store the most recent operational status data of associated NFs during temporary disconnection from one or more mirrored NRFs. The local database ensures retention of NF state information in isolation scenarios and enables post-reconnection verification and synchronization.

[0007] The term ‘Main Database’ used hereinafter in the specification refers to a persistent and shared data repository operably accessible by a plurality of mirrored NRFs, configured to store synchronized NF status records, heartbeat logs, and peer notification information. The main database supports distributed consistency and enables authoritative determination of NF operational states across the NRF cluster.

[0008] The term ‘Suspended Notification’ used hereinafter in the specification refers to a formal message generated by an NRF, indicating that a given NF has entered a suspended or unresponsive state. The suspended notification is configured to include information such as the NF instance identifier, time of last known activity, cause of suspension, and may be transmitted to one or more consumer NFs or monitoring systems using standardized service-based interfaces

[0009] The term “Predefined time interval” refers to a fixed and predetermined time period that is established in advance and used consistently for a specific purpose.

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

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

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

[0013] Modern fifth-generation (5G) telecommunication networks rely on a service-based architecture wherein Network Functions (NFs) are virtualized and dynamically orchestrated across the network core. The Network Repository Function (NRF) is an architectural component that maintains a repository of NF profiles and enables NF discovery and registration. In deployments involving multiple NRF instances organized within a logical NFSet, it is expected that all NRFs maintain synchronized views of NF registration and status data through inter-NRF communication protocols. This synchronization is maintained to achieve consistent service discovery and status tracking throughout the network.

[0014] NFs regularly exchange heartbeat signals with NRFs to indicate their operational status. Typically, once an NF registers with an NRF, its profile and status are synchronized across other NRFs in the NFSet to ensure consistency. However, in real- world deployments, temporary disconnection between NRFs due to networkfaults, link degradation, or service updates may interrupt this synchronization process. If one NRF becomes isolated and fails to receive heartbeat or update signals that are otherwise correctly exchanged between the NF and other connected NRFs, it may falsely conclude that the NF is non-operational.

[0015] In such cases, the disconnected NRF may unilaterally mark the NF as suspended and trigger suspension notifications to subscribed consumer NFs or orchestrators, even though the NF remains active and functional within the broader network. This premature action, based solely on incomplete local information, can introduce considerable instability. Unwarranted suspension notifications may result in unnecessary rerouting, failover initiation, or service degradation, and can significantly undermine trust in network state accuracy.

[0016] Certain existing solutions attempt to address aspects of inter -NRF synchronization by introducing mechanisms for profile version auditing, NF list queries, and subscription-based update dissemination. These approaches are typically geared towards maintaining consistency in NF records across NRF clusters or providing responsive updates upon registration or deregistration events. However, such techniques generally assume continuous inter-NRF connectivity and do not provide a robust fallback mechanism to handle temporary disconnections. In the absence of such a mechanism, even short-lived disruptions in synchronization may lead to misinterpretation of NF status and the issuance of erroneous notifications.

[0017] A few known implementations attempt to refine the response to missing heartbeat signals by altering the way NRFs handle resource discovery or registration during partial connectivity. Nonetheless, these approaches often continue to rely on immediate local status evaluation, lacking a deferred or confirmatory strategy to validate the suspension condition through inter-NRF comparison once connectivity is restored. As a result, false suspension states may still be propagated based on transient communication failures rather than actual NF inactivity.

[0018] Therefore, there exists a need for an improved method and system that enables NRFs to mitigate the risk of false NF suspension during periods of connectivity loss.OBJECTIVES OF THE DISCLOSURE

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

[0020] An objective of the present disclosure is to provide a system and a method for preventing false suspension notifications of a plurality of network functions (NFs) in a network.

[0021] Another objective of the present disclosure is to reduce the risk of false notifications due to communication failures between a plurality of network repository functions (NRFs).

[0022] Yet another objective of the present disclosure is to temporarily store data in the local database by a disconnected NRF during connection loss.

[0023] Yet another objective of the present disclosure is to enable an NRF (i.e., disconnected NRF) to accurately assess the status of registered NFs upon regaining connectivity and synchronize data, accordingly, maintaining data integrity across the network.

[0024] Yet another objective of the present disclosure is to send a suspended notification to the NFs only when the NF is found to be suspended.

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

[0026] In an exemplary embodiment, a method for preventing false suspension of a plurality of network functions (NFs) in a network is described. The method comprising receiving, by each network repository function (NRF) of one or more mirrored NRFs, operational status data from at least one NF associated with a corresponding NRF, via a heartbeat request. The method comprising, upon detecting that the heartbeat request has stopped, determining, by each NRF, whether all of the one or more mirrored NRFs are connected together. The method comprising storing, by each NRF, the operational status data in a local database of the corresponding NRF, upon determination that one or more mirrored NRFs are not connected together. The method further comprising initiating, by each NRF, synchronization of the operational status data between all of the one or more mirrored NRFs, upon detecting reestablishment of a connection between all of the one or more mirrored NRFs.

[0027] In an embodiment, the method further comprises detecting, by each NRF, whether reception of the heartbeat request has stopped for a duration exceeding a predefined threshold time.

[0028] In an embodiment, the method further comprises, upon determination that all of the one or more mirrored NRFs are connected, detecting, by each NRF, one NRF that was last communicated with the at least one NF.

[0029] In an embodiment, the method further comprises, upon synchronization of the operational status data, initiating, by each NRF, a verification process to compare the locally stored operational status data with the data stored in the one or more mirrored NRFs; determining, by each NRF, a current operational state of the at least one NF as one of an operational state and a suspended state based on the comparison; and upon determination that the at least one NF is in the suspended state, detecting, by each NRF, the one NRF that was last communicated with the at least one NF.

[0030] In an embodiment, the method further comprises sending, by the detected NRF, a suspended notification to other plurality of NFs.

[0031] In an embodiment, the method further comprises receiving, by each NRF, the operational status data of the at least one NF at a predefined time interval.

[0032] In an embodiment, the method further comprises, upon determining that the at least one NF is in the operational state, performing, by each NRF, no action.

[0033] In an exemplary embodiment, a system for preventing false suspension of a plurality of NFs in a network is disclosed. The system comprises one or more mirrored NRFs, each NRF comprising a receiving unit configured to receive operational status data from at least one NF associated with a corresponding NRF, via a heartbeat request. Upon detecting that the heartbeat request has stopped, a detection unit is configured to determine whether all of the one or more mirrored NRFs are connected together. A processing unit is configured to store the operational status data in a local database of the corresponding NRF, upon determination that one or more mirrored NRFs are not connected together, and to initiate synchronization of the operational status data between all of the one or more mirrored NRFs, upon detecting re-establishment of a connection between all of the one or more mirrored NRFs.

[0034] In an exemplary embodiment, a computer program product is described. The computer program product comprises a non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to execute a method for preventing false suspension of a plurality of network functions in a network. The method comprises receiving, by each network repository function of one or more mirrored network repository functions, operational status data from at least one network function associated with a corresponding network repository function, via a heartbeat request. The method further comprises, upon detecting that the heartbeat request has stopped, determining, by each networkrepository function, whether all of the one or more mirrored network repository functions are connected together. The method further comprises storing, by each network repository function, the operational status data in a local database of the corresponding network repository function, upon determination that one or more mirrored network repository functions are not connected together. The method further comprises initiating, by each network repository function, synchronization of the operational status data between all of the one or more mirrored network repository functions, upon detecting re-establishment of a connection between all of the one or more mirrored network repository functions.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

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

[0036] FIG. 1 illustrates an exemplary network architecture for implementing a system for preventing false suspension notifications of a plurality of network functions (NFs), in accordance with an embodiment of the present disclosure.

[0037] FIG. 2A illustrates an exemplary system architecture of the system for preventing false suspension notifications of the plurality of NFs, in accordance with an embodiment of the present disclosure.

[0038] FIG. 2B illustrates an exemplary block diagram of the system for preventing false suspension notifications of the plurality of NFs, in accordance with an embodiment of the present disclosure.

[0039] FIG. 3 illustrates an exemplary flow diagram for preventing false suspension notifications of the plurality of NFs, in accordance with an embodiment of the present disclosure.

[0040] FIG. 4 illustrates a flow chart of a method for preventing false suspension notifications of the plurality of NFs, in accordance with an embodiment of the present disclosure.

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

[0042] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 Network Architecture102 User104 User Equipment106 Network108 System110 Network Function (NF)112 Network Repository Function (NRF)200A System Architecture200B Block Diagram202 Processor204 Memory 206 Interface(s)208 Synchronizing Unit210 Transmitting Unit212 Registration Unit216 Database 222 Receiving Unit224 Sending Unit226 Processing Unit228 Detection Unit230 Main Database 232 Local database300 Flow Diagram400 Flow chart500 Computer system510 External storage device520 Bus530 Main memory540 Read only memory550 Mass storage device560 Communication port(s)570 ProcessorDETAILED DESCRIPTION

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

[0044] 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 theart 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.

[0045] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

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

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

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

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

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

[0051] In a network environment, multiple Network Repository Functions (NRFs) are organized within a set of Network Functions (NFs). The NRFs communicate and synchronize data among themselves to ensure consistency. When an NF registers with one of the NRFs, the data is synchronized across all NRFs in the set. The NF establishes a connection with one of the NRFs via connection signals (e.g., heartbeats) to report its status. The NRFs coordinate and update each other with this information. However, if one of the NRFs loses connectivity and fails to receive data from the other NRFs due to a connection issue, it may not be informed about the communication status of the registered NF. As a result, the disconnected NRF might incorrectly consider the registered NF as suspended, despite it being operational. This can lead to the erroneous suspension of the NF and the dispatch of incorrect suspension notifications. To address this issue, it is crucial to implement robust communication protocols to minimize the potential for misinterpretation due to communication failures.

[0052] Therefore, there is a need for systems and methods to prevent false suspension notifications of a plurality of network functions (NFs).

[0053] Specifically, there is a requirement for an NRF to store relevant NF status data locally when disconnected and to refrain from marking NFs as suspended until a reconnection allows for verification against synchronized data from peer NRFs. Such an approach ensures that suspension decisions are based on validated and complete information, thereby enhancing the accuracy and resilience of NF status management. The present disclosure addresses this technical problem by enabling intelligent deferral of suspension actions and context-aware evaluation of NF operational state, thus improving the overall robustness of multi-NRF deployments within a 5G network environment.

[0054] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a system and a method for mitigating the risk of false notifications due to communication failures in a network of NRFs. A disconnected NRF temporarily stores data locally during a connection loss, the system ensures that no information is mistakenly classified as suspended prematurely. Upon re-establishment of the connection, the NRF checks the stored data against the status of the network function (NF). If the NF is found to be suspended (i.e., the NRF is not receiving data from the NF), only then is a suspended notification dispatched. This reduces the occurrence of erroneous suspension notifications. The NRF may autonomously verify the status of registered NFs upon regaining connectivity, thus enhancing the accuracy and reliability of the system.

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

[0056] FIG. 1 illustrates an exemplary network architecture for implementing a system for preventing false suspension notifications of a plurality of network functions (NFs), in accordance with an embodiment of the present disclosure.

[0057] As illustrated in FIG. 1, one or more user equipments (UEs) (104-1, 104-2... 104-N) may be connected to the network (106). A person of ordinary skill in the art will understand that the one or more UEs (104-1, 104-2... 104-N) may be collectively referred to as UEs (104) and individually referred to as a UE (104). One or more users (102-1, 102-2... 102-N) may provide one or more requests to the end server through the network (106). A person of ordinary skill in the art will understand that the one or more users (102-1, 102-2... 102-N) may be collectively referred to as users (102) and individually referred to as a user (102).

[0058] In an embodiment, the UE (104) may include, but not be limited to, a mobile, a laptop, etc. Further, the UE (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, audio aid, microphone, or keyboard. Furthermore, the UE (104) may include a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, and a mainframe computer. Additionally, input devices for receiving input from the user (102) such as a touchpad, touch-enabled screen, electronic pen, and the like may be used. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.

[0059] Referring to FIG. 1, the UE (104) is configured to communicate with the network (106). In an embodiment, the network (106) may include at least one of a Third Generation (3G) Network, Fourth Generation (4G) network, Fifth Generation (5G) network, 6G network, WiFi Network, Fiber to the Home (FTTx) network, or the like which provides internet service to individual or to the subscriber home. The network (106) may enable the UE (104) to communicate with other devices in the network architecture (100). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment,the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

[0060] In an embodiment, the network (106) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network (106) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet- switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0061] In an embodiment, the network architecture (100) further includes a system (108). The system (108) comprises a plurality of network functions (NFs) (110- 1, 110-2... .110-N) and a plurality of network repository functions (NRFs) (112-1, 112- 2....112-N). A person of ordinary skill in the art will understand that the plurality of NFs (110-1, 110-2....110-N) may be collectively referred to as the plurality of NFs (110) and individually referred to as NF (110). A person of ordinary skill in the art will understand that the plurality of NRFs (112-1, 112-2... ,112-N) may be collectively referred to as the plurality of NRFs (112) and individually referred to as NRF (112). The system (108) is configured to mitigate the risk of false notifications due to communication failures (or connection loss) between the plurality of NRFs (112) and the plurality of NFs (110). In an aspect, a NF (110) may register data to one of the NRFs (112) within the network (106) and initiate a synchronization process. The received data is synchronized across the plurality of NRFs (112) within the network(106) to ensure consistency and uniformity of information. The NF (110) commences communication with the plurality of NRFs via a plurality of connection signals (e.g., heartbeat signals) to notify them of its operational status. This helps facilitate ongoing monitoring of connections and disconnections in the network (106). If one of the NRFs (112) is disconnected due to connection loss, the disconnected NRF (112) temporarily stores data locally during the connection loss. In this way, the system (108) ensures that no information is prematurely considered suspended. Upon reestablishment of the connection, the NRF (112) may check the stored data against the status of the NF (110). The status of the NF is operational or suspended. If the NF is found to be suspended (i.e., on detecting that the data is not received from the NF (110)), only then does the NRF (112) send a suspended notification. This effectively addresses the challenge of erroneous suspension notifications by enabling the NRF (112) to autonomously verify the status of registered NFs (110) upon regaining connectivity, thus enhancing the accuracy and reliability of the system (108).

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

[0063] FIG. 2A illustrates an exemplary system architecture (200A) of the system (108) for preventing false suspension notifications of the plurality of NFs (110), in accordance with an embodiment of the present disclosure.

[0064] The system architecture (200A) includes the plurality of NFs (110-1, 110-2... 110-N) and the plurality of NRF (112-1, 112-2....112-N).

[0065] In an aspect, the network repository function (NRF) is a network function used in 5G and network function virtualization (NFV) environments. The NRF is used in managing and coordinating network functions by providing mechanisms for service discovery, registration, configuration management, and communication.

[0066] In an aspect, the NFs are used to handle specific tasks within the network (106). The plurality of NFs (110) includes, but is not limited to, an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a network slice selection function (NSSF), a policy control function (PCF), an application function (AF) and a network exposure function (NEF).

[0067] The AMF manages user registration, mobility, and connection setup in the network. The SMF handles the establishment, modification, and release of user sessions and manages session-related data. The UPF manages user plane data traffic, including routing and forwarding data packets. The PCF defines, distributes, and enforces policies related to network behavior and service management. This includes policies for Quality of Service (QoS), traffic management, and access control. The AF manages application-level services and interacts with other network functions. The AF provides specific application services, such as content delivery or application analytics. The NEF exposes network capabilities and services to external applications and third- party services.

[0068] In an aspect, an NF (110) may register data to one of the NRFs (112) within the network (106). The NF (110) may initiate a synchronization process to synchronize the received data with the plurality of NRFs (112) within the network (106). The received data is data corresponding to the NF (110). In an aspect, the data corresponding to the NF (110) includes, but is not limited to, NF registration information, NF service availability, NF capability information, configuration data, fault and status information, performance metrics, etc.

[0069] The NF (110) commences communication with the NRFs (112) via connection signals (e.g., heartbeat signals) to notify its operational status. If a connection break occurs in one of the plurality of NRFs (112) within the network (106), the affected NRF (112) stores the received data internally to prevent data loss during the disconnection period. In an example, the NRF-1 (112-1) loses connection with the NF (110). Further, upon re-establishing the connection, the NRF-1 (112-1) verifies the status of the stored data. The NRF-1 (112-1) checks whether the status of the NF (110) is suspended or operational. The NRF-1 (112-1) checks the status of the NF (110) by comparing the stored data with data of other NRFs (e.g., NRF-2 (112-2) - NRF-N (112- N)). If the NF (110) is found to be suspended (i.e., indicating the data is not received by the NRF-2 (112-2) from the NF (110) due to a potential issue), the NRF-1 (112-1) sends a suspended notification to other NFs (110). Further, the suspended notification may also be sent to users (e.g., relevant stakeholders, network operators, service providers, etc.). The suspended notification is sent to inform the user about the potential issue and prompt appropriate action. The appropriate action may include, but is not limited to, modification to network settings, increasing bandwidth, or optimizing routing to improve overall connection reliability.

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

[0071] In yet another embodiment, the computer program product may comprise a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors (202), cause the one or more processors(202) to execute a method (400) for preventing false suspension of a plurality of network functions (NFs) (110) in a network (106). The non-transitory computer- readable medium may be implemented as a persistent storage device such as a solid- state drive, magnetic hard disk, optical medium, flash memory, or any other nonvolatile storage medium capable of storing executable program code and operational data without power loss. The one or more processors (202) may be implemented as microprocessors, microcontrollers, digital signal processors, central processing units, logic circuitry, or any combination thereof, configured to execute the machine-readable instructions. The instructions, when executed by the one or more processors (202), cause each network repository function (NRF) (112) of one or more mirrored NRFs (112) to receive (402) operational status data from at least one NF (110) associated with a corresponding NRF (112), via a heartbeat request. The operational status data may include identifiers of the NF (110), service availability status, health check metrics, and timestamps of received heartbeat signals. The heartbeat request may be transmitted at a predefined time interval and may be implemented over standardized service-based interfaces to ensure compatibility between NRFs (112) and NFs (110).

[0072] In an embodiment, the instructions further cause each NRF (112), upon detecting that the heartbeat request has stopped, to determine whether all of the one or more mirrored NRFs (112) are connected together. This determination may be performed by exchanging connectivity status messages among the mirrored NRFs (112) and validating peer links to confirm inter-NRF communication availability. The instructions further cause each NRF (112) to store (406) the operational status data in a local database (232) of the corresponding NRF (112), upon determination that one or more mirrored NRFs (112) are not connected together. The local database (232) may be implemented as a high-performance data store, such as an embedded key-value database or relational storage engine, optimized for quick write operations and retrieval during disconnection periods, ensuring the last known operational state of the NF (110) is preserved.

[0073] In an embodiment, the instructions further cause each NRF (112) to initiate (408) synchronization of the operational status data between all of the one or more mirrored NRFs (112), upon detecting re-establishment of a connection between all of the one or more mirrored NRFs (112). The synchronization process may include exchanging operational status records, comparing timestamped updates, resolving data conflicts, and ensuring that all mirrored NRFs (112) store an identical and up-to-date representation of the NF (110) status.

[0074] FIG. 2B illustrates an exemplary block diagram of the system (108) for preventing false suspension notifications of the plurality of network functions (NFs) (110), in accordance with an embodiment of the present disclosure.

[0075] Referring to FIG. 2B, in an embodiment, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). In operation, the processor(s) (202) coordinate and control the functional execution of various components of the system (108), including managing data flow between the NFs (110) and the NRFs (112), invoking detection and processing logic, and controlling communication routines.

[0076] The memory (204) may be configured to store one or more computer- readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may comprise any non-transitory storage device including, for example, volatile memory such as random-access memory (RAM), or non-volatile memory such as erasable programmable read only memory (EPROM),flash memory, and the like. The memory (204) may further include dedicated partitions for buffering real-time status data, maintaining NF-initiated transactions, and caching recent synchronization events.

[0077] In an embodiment, the system (108) may include an interface(s) (206). The interface(s) (206) may comprise a variety of interfaces, for example, interfaces for data input and output devices (I / O), storage devices, and the like. The interface(s) (206) may facilitate communication through the system (108), and serve as the link for intercomponent signaling and data exchange. The interface(s) (206) may also provide a communication pathway between internal components such as processor(s) (202), memory (204), and external endpoints such as NT's (110), NRFs (112), and consumer network entities via standardized protocols.

[0078] The system (108) comprises the plurality of NT's (110) and the plurality of NRFs (112), functionally and logically integrated to maintain operational continuity of the network (106). The collaborative interplay between the NFs (110) and NRFs (112) is designed to ensure fault-tolerant behavior, particularly under conditions of connectivity loss or inconsistency in heartbeat signals.

[0079] Each NF (110) comprises a registration unit (212), a synchronizing unit (208), and a transmitting unit (210). These components work together to facilitate the proactive advertisement of NF operational data, ensure its consistent replication, and maintain regular status reporting.

[0080] In particular, the registration unit (212) is configured to provide registration of data to at least one NRF (112) within the network (106), thereby initiating a synchronization process. This registration triggers the synchronizing unit (208) to replicate the registered data across a plurality of mirrored NRFs (112). This operation ensures uniform availability of the NF profile and its associated service endpoints across all designated NRFs.

[0081] Subsequently, the transmitting unit (210) is configured to send the operational status of the NF (110) to the mirrored NRFs (112) via a plurality of connection signals at a predefined time interval. These signals, typically heartbeat messages, form the continuous health-check mechanism between the NF (110) and its associated NRFs (112). The integration of the registration unit (212), synchronizing unit (208), and transmitting unit (210) ensures seamless registration, consistent replication, and uninterrupted communication of the NF’s availability and health status. In one embodiment, the mirrored NRF is a configuration wherein two or more instances of the NRF are deployed in a coordinated, redundant, and synchronized manner within a telecommunications network, such that each instance maintains a consistent and realtime replica of registration, discovery, and operational status data of all registered NFs. These instances are operatively interconnected and designed to collectively ensure continuity, availability, and fault-tolerance in NF state monitoring and lifecycle management operations.

[0082] On the receiving end, each NRF (112) includes a receiving unit (222), a sending unit (224), a detection unit (228), a processing unit (226), a main database (230), and a local database (232). These components operate in a coordinated sequence to receive NF status, detect anomalies, verify peer consistency, make decisions on suspensions, and distribute suspension notifications only when legitimately warranted.

[0083] The receiving unit (222) is configured to receive the operational status of the NFs (110) via the connection signals dispatched by the transmitting unit (210). The reception of timely and consistent heartbeats is critical for the detection unit (228), which continually monitors whether the reception of such signals has ceased. If the reception is stopped, and more importantly, if one or more NRFs are found to be disconnected from the group, the detection unit (228) flags a partial disconnection scenario.

[0084] Upon determining such a disconnection, the processing unit (226) of the affected NRF (e.g., NRF-2 (112-2)) is configured to store the operational status in the local database (232). The local database (232) serves as a temporary, high-availability, NRF-specific storage entity designed to retain last known NF data during connection interruptions. The configuration of the local database (232) may include embedded key -value data engines, with journaling support to preserve time-sensitive operational state in a compact and retrievable format. This preserves state integrity during isolation and enables deferred evaluation of suspension events.

[0085] The main database (230), in contrast, acts as the shared persistent repository among the mirrored NRFs. It is configured to store all synchronized NF data received from the receiving unit (222), the sending unit (224), the processing unit (226), and the detection unit (228). Configured using distributed data platforms such as Apache Cassandra or MongoDB, the main database (230) ensures horizontally scalable, fault-tolerant storage of NF identifiers, status values, historical heartbeats, and peer event logs. The tight integration between the local database (232) and main database (230) allows the system to maintain both temporary and authoritative records, improving resilience and ensuring traceability.

[0086] Once the detection unit (228) determines that the disconnection has been resolved, the processing unit (226) triggers the synchronization operation, during which all NRFs (112) reconcile their locally stored NF data. This reconciliation process involves cross-verifying the operational status of each NF (110) based on the data previously stored in the local database (232) and the data available in the main database (230) or reported by peer NRFs.

[0087] In an embodiment, upon successful synchronization of the operational status data following reconnection of the plurality of NRFs (112), the processing unit (226) of each participating NRF is configured to initiate a verification process. This process involves a structured comparison between the locally stored operational statusdata, persisted during the disconnection event within the local database (232), and the status data retrieved from one or more of the mirrored NRFs (112), including data records stored in their respective main databases (230). This verification process is executed to determine the reliability and completeness of the operational status previously stored during the isolation period. The comparison operation is carried out using timestamp-matching algorithms and NF-specific status fields such as last heartbeat time, suspension flag, and activity sequence number. This enables the processing unit (226) to establish whether the NF (110) maintained continuity across the mirrored NRFs during the temporary disconnection.

[0088] Concurrently, the detection unit (228) is configured to analyze the output of the comparison process to determine a current operational state of the at least one NF (110). The state is classified into one of two possible outcomes: an operational state or a suspended state. The detection unit (228) concludes that the NF (110) is operational if at least one of the mirrored NRFs reports consistent and timely heartbeat receptions, and the state is corroborated by the mirrored data. Conversely, if all mirrored NRFs report an absence of heartbeat data beyond a preconfigured suspension threshold duration, the detection unit (228) concludes that the NF (110) is in a suspended state.

[0089] In an embodiment, the detection unit (228) is further configured to perform an advanced verification process upon determining that all of the one or more mirrored NRFs (112) are reconnected and available for communication within the network (106). In particular, the detection unit (228), in conjunction with the processing unit (226), is configured to detect and identify one NRF (112) among the plurality of mirrored NRFs that was last in communication with the at least one NF (110) during the disconnection event. This enables accurate inference of the NF’s operational status by deferring to the most recently informed peer. In operation, each NRF (112) maintains a timestamped log of received heartbeat messages from everyregistered NF (110). These logs are recorded either in the main database (230) or cached within the local database (232), and comprise data fields such as the NF instance ID, the time of last received heartbeat, the source NRF ID, and any anomalies observed. When a temporary disconnection is resolved and full inter-NRF communication is restored, the detection unit (228) exchanges these logs with peer NRFs to create a synchronized view of the most recent interactions with the NF (110).

[0090] Based on this comparative analysis, the detection unit (228) identifies the NRF instance with the most recent successful heartbeat timestamp for the corresponding NF (110). That NRF is then designated as the last-communicated NRF. The processing unit (226) retrieves the NF’s status from the last-communicated NRF’s log and uses this status as the definitive operational condition of the NF during the disconnection period.

[0091] By implementing this logic, the system (108) ensures that suspension decisions are not made prematurely or based on partial views. This hierarchical deferral model allows NRFs that were disconnected to trust the timeline of the most recently connected NRF, thereby improving accuracy and avoiding false positive suspensions.

[0092] Upon determination that the NF (110) is in the suspended state, the sending unit (224) of the corresponding NRF (112), such as NRF-2 (112-2), is configured to provide a suspended notification. The suspended notification refers to a formal communication sent by the NRF to inform other NFs or consumer functions about the unavailability or inactivity of the registered NF. The notification includes details such as NF instance ID, suspension cause (e.g., heartbeat loss), time of last contact, and any associated policy actions. It may be sent via service-based interfaces using JSON-based REST APIs, allowing interoperability and programmatic handling by other network functions.

[0093] In an embodiment, upon determining that the at least one NF (110) is in the operational state, the processing unit (226) is configured to perform no action.

[0094] The database (216) is configured to store program instructions that control the behavior of the system (108), including the logical operations executed by the processor(s) (202), the timing policies for heartbeats, the data handling logic in the processing unit (226), and the criteria for triggering suspended notifications. Additionally, the database (216) stores operational data received from the NF (110) and the NRF (112). The configuration of the database (216) may include non-volatile storage media such as flash drives or persistent volumes on network-attached storage (NAS), structured to allow fast lookup of heartbeat logs, notification trails, and audit records.

[0095] In an embodiment, the user equipment (UE) (104) may be communicatively coupled with a system (108) operating within a network (106). The coupling may include a sequence of communication steps enabling the UE (104) to initiate and establish interaction with the system (108) while ensuring that the system (108) performs its configured function of preventing false suspension of a plurality of network functions (NFs) (110) in the network (106). In an embodiment, the coupling process comprises receiving, by the system (108), a connection request from the UE (104). The connection request may be generated by the UE (104) when initiating a service session, registering with the network (106), or requesting access to one or more NFs (110). The connection request may contain identification parameters, authentication tokens, session setup information, and other control signalling necessary for initiating communication. In an embodiment, the coupling process further comprises sending, by the system (108), an acknowledgment of the connection request to the UE (104). The acknowledgment may serve as a confirmation that the system (108) has successfully received and processed the connection request, and may include connection acceptance indicators, assigned session parameters, and readiness notifications for further data exchange. In an embodiment, the coupling process furthercomprises transmitting, by the system (108), a plurality of signals in response to the connection request. These signals may include control messages, configuration parameters, service availability indications, and heartbeat signals, depending on the operational requirements of the session. The transmission may occur over secure and standardized communication protocols to ensure reliability and interoperability within the network (106). In an embodiment, the system (108) is configured to prevent false suspension of a plurality of NT's (110) in the network (106).

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

[0097] In one example, consider a deployment in a 5G core where an AMF (Access and Mobility Management Function), acting as NF (110), is registered with three mirrored NRFs (112-1, 112-2, and 112-3). Heartbeats are transmitted every five seconds via the transmitting unit (210) to all three NRFs. A network fault causes NRF- 2 (112-2) to become disconnected from NRF-1 and NRF-3. While heartbeats are still received by NRF-1 and NRF-3, NRF-2 detects missing signals but also detects that it is partitioned from the group. The processing unit (226) of NRF-2 then stores the last received operational state in the local database (232) instead of sending a suspended notification. Upon reconnection, the detection unit (228) of NRF-2 triggers synchronization. The processing unit (226) compares its local records with those of the main database (230) and peer NRFs. Upon confirming that heartbeats were continuously received by NRF-1 and NRF-3, the detection unit (228) determines that the AMF was operational. No suspension notification is issued.

[0098] In another example, consider a scenario where a Network Function (NF), such as a Network Slice Selection Function (NSSF), is registered with three mirrored NRFs: NRF-X (112-1), NRF-Y (112-2), and NRF-Z (112-3). Due to a partial outage, NRF-Y becomes disconnected from NRF-X and NRF-Z for a period of 45 seconds. During this time, NSSF continues to transmit heartbeats only to NRF-X and NRF-Z. NRF-Y, upon reconnection, initiates synchronization of NF status using its local database (232) and shared synchronization logs exchanged with NRF-X and NRF-Z. The processing unit (226) of NRF-Y begins the verification process by comparing its locally cached heartbeat logs with the main database (230) records from NRF-X and NRF-Z. The detection unit (228) observes that neither NRF-X nor NRF-Z received heartbeats from NSSF for the last 35 seconds, which exceeds the suspension timeout of 30 seconds. Hence, NSSF is classified into a suspended state. To confirm the status and assist in downstream decisions, the detection unit (228) identifies that NRF-Z had received a heartbeat from NSSF more recently (timestamp T3) compared to NRF-X (timestamp Tl). Accordingly, NRF-Z is marked as the last-communicated NRF. NRF-Y then retrieves the most recent operational data for NSSF from NRF-Z to finalize its status report and to conditionally trigger a suspended notification only if no more recent activity is detected.

[0099] FIG. 3 illustrates an exemplary flow diagram (300) for preventing false suspension notifications of the plurality of NFs (110), in accordance with an embodiment of the present disclosure.

[0100] In an aspect, the NF (110) may register data to one NRF of the plurality of NRFs (112). The NF (110) may initiate synchronization. The registered data is synchronized across the plurality of NRFs (112) within the network (106). In an aspect, the NF (110) registers data with the NRF (112) to provide information about itself and its capabilities to the NRF (112). This registration process allows the NRF (112) to keep an up-to-date record of available network functions and their capabilities,enabling other network functions to discover and utilize them as needed. In an example, the NF (110) (e.g., AMF) sends a registration request, including data such as its identifier, function type, capabilities, service type, and any supported interfaces to the NRF (112). The NRF (112) receives the registration request from the AMF and updates its repository with the AMF's details. In this way, the NRF records data corresponding to AMF's existence and its capabilities.

[0101] At step 302, the NF (110) may send connection signals (e.g., heartbeat signals) at a predefined interval to the NRFs (112). The NF (110) may send the connection signals at the predefined time interval to notify its operational status. This ensures ongoing monitoring of the NFs (110) and NRFs (112). In an aspect, the NF (110) may need to maintain communication with the NRF (112) to ensure proper operation and coordination. The NF (110) can achieve this by sending a heartbeat signal to the NRF (112) at a predefined time interval. The NF (110) uses the heartbeat signals to notify the NRF (112) that it is still active and functioning properly. The heartbeat signal provides regular updates about the NF's status and operational state. In an example, the NF (110) (e.g., AMF) communicates with the NRF (112). The AMF sends a heartbeat signal to the NRF (112) at predefined time interval (e.g., 30 seconds). After every 30 seconds, the AMF sends the heartbeat message to the NRF (112). The heartbeat message includes information like the AMF's ID, status, and timestamp. The NRF (112) receives the heartbeat signal and updates its records to confirm that the AMF is active and operational.

[0102] At step 304, the NRF (112) may check whether the connection signal from the NF (110) is stopped. The NRF (112) may monitor stopping of the connection signal to determine if there is any connection break (or connection loss or disconnection) between the NF (110) and the NRFs (112).

[0103] At step 306, upon detecting that there is no stoppage of the connection signal, the NRF (112) may not take any action. The NF (110) may continuously send the connection signal to the NRF (112).

[0104] At step 308, upon detecting that there is a stoppage of the connection signal, the NRF (112) may check whether all synced (or mirrored) NRFs (112) are connected.

[0105] At step 310, upon detecting that all synced NRFs (112) are not connected, affected NRF (112) may locally store the data and wait until the connection is re-established. The affected NRF (112) may store the received data internally to prevent data loss during the disconnection period. Furthermore, the NRF (112) stores the data locally and reconcile it upon reconnection. This enhances the network's resilience to connectivity issues.

[0106] At step 312, upon detecting the connection is re-established, the NRF (112) may sync the stored data. The NRF (112) may verify the status of the stored data. The NRF (112) may verify the status of the stored data by synchronizing its stored data with the data of the other NRFs (112). Further, the NRF (112) may check the stored data against the current NF status.

[0107] At step 314, the NRF (112) may check status of the NF (110). In an aspect, the NRF (112) may check whether the status of the NF (110) is suspended or operational by comparing the stored data with other NRFs data. The NRF (112) can accurately assess the status of the NFs (110) and synchronize data accordingly. In this way, the NRF (112) maintains data integrity across the network.

[0108] Upon detecting that the NF (110) is not suspended, the NRF (112) may proceed to the step 306 (i.e., not take any action). Upon detecting that the NF (110) is suspended, the NRF (112) may proceed to step 316.

[0109] At step 316, upon detecting that all synced NRFs (112) are connected, the NF (110) may check the last communicated NRF (112). The last communicated NRF (112) may be the NRF (112) with which the NF (110) last interacted or exchanged information.

[0110] At step 318, the NF (110) may find the last communicated NRF (112). In an aspect, the NF (110) may find the last communicated NRF (112) using an identifier associated with the NRF (112).

[0111] At step 320, the NRF (112) may send suspended notification to other NFs (110). In an aspect, if the NF (110) is found to be suspended (i.e., the data is not received by the NRF (112) from the NF (110) due to a potential issue), the NRF (112) may send a suspended notification to relevant users (e.g., stakeholders, network operators, service providers, end users, etc.). The suspended notification is sent to inform the users about the potential issue and prompt appropriate action. Further, the NRF (112) may re-evaluate the status of NFs (110) upon reconnection and issue suspended notifications only when necessary. This improves resource utilization, minimizes unnecessary alerts, and streamlines overall notification management.

[0112] In an aspect, the NRF (112) may autonomously verify the status of registered NFs (110) upon regaining connectivity, thus enhancing the accuracy and reliability of the overall system. Further, the NRF (112) avoids prematurely suspending NFs due to communication failures. This helps to prevent the issuance of false suspended notifications, thereby improving system accuracy.

[0113] FIG. 4 illustrates a method (400) for preventing false suspension of a plurality of network functions (NFs) in a network (106), in accordance with one embodiment of the present disclosure.

[0114] In one embodiment, the method (400) comprises receiving, by each network repository function (NRF) of one or more mirrored NRFs, operational statusdata from at least one NF associated with a corresponding NRF, via a heartbeat request, as shown in step (402). The operational status data may include indicators of service availability, connectivity health, and activity metrics, transmitted at a predefined time interval to ensure periodic monitoring of the NF's operability. In accordance with one embodiment, the operational status data may be received at each NRF at a fixed periodicity, such as every five seconds, thereby enabling continuous state awareness and timely detection of connectivity anomalies.

[0115] In one embodiment, upon detecting that the heartbeat request has stopped, the method (400) includes determining, by each NRF, whether all of the one or more mirrored NRFs are connected together, as shown in step (406). The detection may be based on the absence of heartbeat signals for a duration exceeding a predefined threshold time, such as thirty seconds. This threshold-based analysis helps each NRF to discriminate between temporary network latencies and critical connectivity failures, thereby improving detection accuracy.

[0116] In one embodiment, the method (400) further includes storing, by each NRF, the operational status data in a local database of the corresponding NRF, upon determination that one or more mirrored NRFs are not connected together, as shown in step (408). The local database at each NRF is configured as a high-availability storage buffer to retain the most recently received NF operational status during temporary disconnections from peer NRFs. This ensures that each NRF maintains a last-known- good-state snapshot of associated NFs in the event of isolation, without prematurely flagging the NF as suspended.

[0117] In one embodiment, the method (400) proceeds with initiating, by each NRF, synchronization of the operational status data between all of the one or more mirrored NRFs, upon detecting re-establishment of a connection between all of the one or more mirrored NRFs, as shown in step (410). The synchronization process ensures that status records accumulated locally during disconnection are reconciled across themirrored NRF group to restore a unified, authoritative view of the NF's operational state.

[0118] In another embodiment, upon determination that all of the one or more mirrored NRFs are connected, each NRF is configured to detect one NRF that was last communicated with the at least one NF. The detection may be based on timestamp comparison of heartbeat logs retained during the disconnection period. This logic is designed to prioritize the most recently informed NRF as the authoritative source of NF status.

[0119] In another embodiment, upon synchronization of the operational status data, the method (400) further comprises initiating, by each NRF, a verification process to compare the locally stored operational status data with the data stored in the one or more mirrored NRFs. Each NRF determines a current operational state of the at least one NF as one of an operational state and a suspended state based on the comparison. Upon determination that the at least one NF is in the suspended state, each NRF is further configured to detect the one NRF that was last communicated with the at least one NF.

[0120] In another embodiment, the detected NRF sends a suspended notification to other plurality of NFs. The suspended notification comprises a structured message including NF identifier, suspension cause, and timestamp, enabling downstream functions to take appropriate remedial action.

[0121] In another embodiment, upon determining that the at least one NF is in the operational state, each NRF performs no action and maintains the status as operational, thereby avoiding any false suspension alerts.

[0122] FIG. 5 illustrates an example computer system (500) for managing User Equipment (UE) (104) policy control signaling in a network, in accordance with theembodiments of the present disclosure. FIG. 5 is explained in conjunction with FIGs 1, 2, 3 and 4.

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

[0124] In an embodiment, the main memory (530) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (540) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basic input / output system (BIOS) instructions for the processor (570). The mass storage device (550) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PAT A) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces).

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

[0126] The present disclosure provides a technical advancement in the field of service-based 5G core network management by enabling a Network Repository Function (NRF) to locally store network function (NF) status data during periods of connection loss, thereby preventing the issuance of false suspended notifications due to transient communication failures. By preserving NF status information locally, the disclosed system enhances data integrity, ensuring that no information is lost during disconnection and allowing accurate synchronization once connectivity is restored. This approach improves network resilience by enabling smooth recovery from disruptions without compromising data consistency. Furthermore, by re-evaluating NF status upon reconnection and issuing notifications only when necessary, the system optimizes resource utilization, reduces unnecessary signaling, and streamlines notification management. The resulting reduction in false notifications enhances the accuracy and reliability of system status updates, thereby fostering trust in network operations and improving the overall user experience.

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

[0128] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter to be implemented merely as illustrative of the disclosure and not as limitation.ADVANTAGES OF THE PRESENT DISCLOSURE

[0129] The present disclosure described herein above has several technical advantages including,

[0130] Reducing the risk of false notifications by storing data locally during connection loss. The NRF avoids prematurely suspending NFs due to communication failures. This helps to prevent the issuance of false suspended notifications, thereby improving system accuracy.

[0131] Enhancing data integrity by storing data locally and ensuring that no information is lost during periods of disconnection. Once the connection is restored, the NRF can accurately assess the status of the NFs and synchronize the data, accordingly, maintaining data integrity across the network.

[0132] Improving resilience by storing data locally and reconciling it upon reconnection enhances the network's ability to handle connectivity issues. This approach allows the system to recover smoothly from disruptions and resume normal operations without compromising data consistency.

[0133] Efficiently managing notifications by re-evaluating the status of NFs upon reconnection and issuing alerts only, when necessary. This improves resourceutilization, minimizes unnecessary notifications, and streamlines overall notification management.

[0134] Enhancing user experience by reducing instances of false notifications. This improvement leads to greater reliability and accuracy in system status updates, fostering trust in the system and enhancing the overall user experience.

Claims

CLAIMS1. A system (108) for preventing false suspension of a plurality of network functions (NFs) (110) in a network (106), the system (108) comprising one or more mirrored network repository functions (NRFs) (112), each NRF (112) of the one or more mirrored NRFs comprising: a receiving unit (222) configured to: receive operational status data from at least one NF (110) associated with a corresponding NRF (112), via a heartbeat request; upon detecting that the heartbeat request has stopped, a detection unit (228) is configured to: determine whether all of the one or more mirrored NRFs (112) are connected together; and a processing unit (226) configured to: store the operational status data in a local database (232) of the corresponding NRF (112), upon determination that one or more mirrored NRFs (112) are not connected together; and initiate synchronization of the operational status data between all of the one or more mirrored NRFs (112), upon detecting reestablishment of a connection between all of the one or more mirrored NRFs (112).

2. The system (108) as claimed in claim 1, wherein the detection unit (228) is configured to detect whether reception of the heartbeat request has stopped for a duration exceeding a predefined threshold time.

3. The system (108) as claimed in claim 1, whereinupon determination that all of the one or more mirrored NRFs (112) are connected, the detection unit (228) is configured to detect one NRF (112) that was last communicated with the at least one NF (110).

4. The system (108) as claimed in claim 1, wherein upon synchronization of the operational status data, the processing unit (226) is configured to initiate a verification process to compare the locally stored operational status data with the data stored in the one or more mirrored NRFs (112); the detection unit (228) is configured to determine a current operational state of the at least one NF (110) as one of an operational state and a suspended state based on the comparison; and upon determination that the at least one NF (110) is in the suspended state, the detection unit (228) is configured to detect the one NRF (112) that was last communicated with the at least one NF (110).

5. The system (108) as claimed in claim 4, wherein the detected NRF (112) is configured to send a suspended notification to other plurality of NFs (110) via the sending unit (224).

6. The system (108) as claimed in claim 1, wherein the receiving unit (222) is configured to receive the operational status data of the at least one NF (110) at a predefined time interval.

7. The system (108) as claimed in claim 4, wherein upon determining that the at least one NF (110) is in the operational state, the processing unit (226) is configured to perform no action.

8. A method (400) for preventing false suspension of a plurality of network functions (NFs) (110) in a network (106), the method (400) comprising: receiving (402), by each network repository function (NRF) (112) of one or more mirrored NRFs (112), operational status data from at least one NF (110) associated with a corresponding NRF (112), via a heartbeat request; upon detecting that the heartbeat request has stopped, determining (404), by each NRF (112), whether all of the one or more mirrored NRFs (112) are connected together; storing (406), by each NRF (112), the operational status data in a local database (232) of the corresponding NRF (112), upon determination that one or more mirrored NRFs (112) are not connected together; and initiating (408), by each NRF (112), synchronization of the operational status data between all of the one or more mirrored NRFs (112), upon detecting re-establishment of a connection between all of the one or more mirrored NRFs (H2).

9. The method (400) as claimed in claim 8, comprising: detecting, by each NRF (112), whether reception of the heartbeat request has stopped for a duration exceeding a predefined threshold time.

10. The method (400) as claimed in claim 8, comprising: upon determination that all of the one or more mirrored NRFs (112) are connected, detecting, by each NRF (112), one NRF (112) that was last communicated with the at least one NF (110).

11. The method (400) as claimed in claim 8, comprising:upon synchronization of the operational status data, initiating, by each NRF (112), a verification process to compare the locally stored operational status data with the data stored in the one or more mirrored NRFs (112); determining, by each NRF (112), a current operational state of the at least one NF (110) as one of an operational state and a suspended state based on the comparison; and upon determination that the at least one NF (110) is in the suspended state, detecting, by each NRF (112), the one NRF (112) that was last communicated with the at least one NF (110).

12. The method (400) as claimed in claim 11, comprising: sending, by the detected NRF (112), a suspended notification to other plurality of NFs (110).

13. The method (400) as claimed in claim 8, comprising: receiving, by each NRF (112), the operational status data of the at least one NF (110) at a predefined time interval.

14. The method (400) as claimed in claim 11, comprising: upon determining that the at least one NF (110) is in the operational state, performing, by each NRF (112), no action.

15. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors (202), cause the one or more processors to execute a method (400) for preventing false suspension of a plurality of network functions (NFs) (110) in a network (106), the method (400) comprising: receiving (402), by each network repository function (NRF) (112) of one or more mirrored NRFs (112), operational status data from at least one NF (110) associated with a corresponding NRF (112), via a heartbeat request;upon detecting that the heartbeat request has stopped, determining (404), by each NRF (112), whether all of the one or more mirrored NRFs (112) are connected together; storing (406), by each NRF (112), the operational status data in a local database (232) of the corresponding NRF (112), upon determination that one or more mirrored NRFs (112) are not connected together; and initiating (408), by each NRF (112), synchronization of the operational status data between all of the one or more mirrored NRFs (112), upon detecting re-establishment of a connection between all of the one or more mirrored NRFs (112).

Images