System and method for monitoring data transmission in a network

Abstract

The present disclosure provides a system (108) and a method (400) for monitoring data transmission between a network function (NF) and a network management system (NMS) (114). The system (108) ensures reliable counter file transmission by establishing communication between the NF and the NMS (114). The counter file includes performance metrics that are generated at predefined intervals and stored with associated timestamps in a database (218). In the event of connectivity disruptions, the NF autonomously store the generated counter file locally. Upon restoration of the connection, the NMS (114) initiates an audit request to retrieve the missing counter file for specific time intervals. A scheduling unit (216) monitors the database (218) to identify the missing counter file and restores it from local server. The recovered counter file is then transmitted to the NMS (114), ensuring data completeness, minimizing data loss, and improving network reliability during network fluctuations or outages.

Description

SYSTEM AND METHOD FOR MONITORING DATA TRANSMISSION IN A NETWORKRESERVATION OF RIGHTS

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

[0002] The present disclosure relates generally to the field of telecommunications. In particular, the present disclosure relates to a system and a method for monitoring data transmission between one or more Network Functions (NFs) and a Network Management System (NMS) in a network.DEFINITION

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

[0004] The expression “network function (NF)” used hereinafter in the specification refers to a functional entity that performs a specific task or set of tasks to support the operation of a telecommunication network. Each NF provides a specific service or set of services and interacts with other NFs through standardized interfaces, typically using a service-based approach in a Fifth Generation (5G) network or a reference point-based approach in earlier generations (e.g., Fourth Generation (4G)).

[0005] The expression “FCAPS” as used hereinafter in the specification refers to a fault, configuration, accounting, performance, and security management. The FCAPS is a microservice used in network management that provides a comprehensive approach for managing and monitoring health, configuration, usage, performance, and security of various network resources.

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

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

[0008] The expression “network management system (NMS)” as used hereinafter in the specification refers to a software platform or a set of tools used for managing, monitoring, and controlling network resources within the telecommunication network. The NMS provides functionalities such as FCAPS, helping network administrators to maintain the health and efficiency of the network.

[0009] The expression “network function (NF) cluster” as used hereinafter in the specification refers to a group of NFs deployed together and managed as a collective unit within the network. These NFs work collaboratively to provide specific network services or capabilities.

[0010] The expression “counter file” used hereinafter in the specification refers to a set of numerical values or performance statistics collected and maintained by the NFs (e.g., NF clusters) in a database to reflect operational state and activity levels ofthe network. Counter files may include metrics such as traffic volume, session counts, error rates, latency, packet loss, bandwidth usage, and resource utilization. The counter file is incremented or updated during normal operation and periodically transmitted to the NMS for monitoring, analysis, and optimization of network performance.

[0011] The expression “reset request” used hereinafter in the specification refers to a periodic and routine request initiated by the NMS. The reset request is triggered at predefined intervals based on a system schedule or configuration and is part of a regular counter lifecycle in normal operating conditions. The reset request ensures that the subsequent set of counters reported by the NF reflects fresh operational data from the next reporting cycle.

[0012] The expression “audit request” used hereinafter in the specification refers to a non-routine request initiated by the NMS to retrieve or verify the counter file from the one or more NFs in response to detected anomalies, such as connectivity failures, transmission interruptions, or missing counter records. The audit request is triggered when the NMS is unable to confirm receipt of the expected counter file, for example, due to a failed or delayed transmission. The purpose of the audit request is to recover or reconcile the counter values that were not successfully received during the regular reporting cycle.

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

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

[0015] In telecommunication, a network function (NF) is an integral part of the network architecture that supports essential operations such as the network performance, security, reliability and scalability. The NFs provide various operations and services, such as monitoring network metrics and maintaining network connectivity to manage and support seamless communication. The various NFs, such as a policy control function (PCF), a session management function (SMF), and a Binding support function (BSF), are deployed in the network architecture to ensure reliable communication. The NFs facilitate the data transmission and reception among the users in the network. The NFs continuously monitor various network parameters to detect potential network performance and stability issues. Among the most critical types of monitored data are performance counters (counter file), which track key indicators such as traffic volume, session counts, packet loss, and error rates.

[0016] Further, a network management system (NMS) is a crucial component that helps to maintain the health, performance, and security of the modern telecommunication network. The NMS continuously observes network performance and health indicators, including traffic flow, bandwidth usage, and device status. The NMS receives monitoring data (e.g., counter file) from the NFs and analyses the network performance based on performance metrics such as latency, throughput, and packet loss to optimize network efficiency and user experience. The NMS handles various user accounts, permissions and authentication to ensure that the network resources are used securely. The NMS is also responsible for generating alarms, reporting anomalies, and initiating corrective actions in case of faults or failures. A key input for all these activities is an accurate and timely counter file sent from NFs to the NMS.

[0017] In addition, the NFs and the NMS are closely connected with each other to monitor, oversee, and optimize the various network operations. The network operations include network monitoring, network configuration management,troubleshooting and support, and performance optimization. During the network operations, the continuity and reliability of data transmission (counter file transmission) from the NFs to the NMS are crucial for monitoring and analysis. However, there is a significant risk of counter file transmission interruptions when network fluctuations, link instability, or temporary connectivity issues occur between the NFs and the NMS. These interruptions may result in gaps in the counter file records, which are essential for tracking metrics such as traffic volume, error rates, and resource utilization.

[0018] At times, loss of the counter file may lead to misinformed decisionmaking in the network management process. For instance, without a continuous and reliable stream of counter files, the NMS may lack real-time visibility into current network conditions, making it difficult to detect or respond to potential issues or anomalies. Moreover, gaps in the counter file may compromise the reliability of historical trend analysis, preventing operators from identifying performance degradation over time or recognizing patterns that may indicate future faults.

[0019] Hence, there is a need to provide a method and a system that can address the shortcomings of existing solutions.OBJECTIVES OF THE DISCLOSURE

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

[0021] An objective of the present disclosure is to provide a system and a method for maintaining continuous data transmission (e.g., counter file) between one or more network functions (NFs) and a Network Management System (NMS) during network fluctuation.

[0022] Another objective of the present disclosure is to provide a system and a method that enables accurate and complete monitoring of network operations.

[0023] Another objective of the present disclosure is to provide a system and a method that implements mechanisms that effectively handle link fluctuations, including periodic storage of counters and retransmission strategies, thereby minimizing data loss or interruptions.

[0024] Another objective of the present disclosure is to provide a system and a method that maintains uninterrupted data transmission between the NFs and the NMS despite link fluctuations or connectivity issues.

[0025] Another objective of the present disclosure is to provide a system and a method that addresses intermittent connectivity issues without compromising data integrity, thus providing continuous visibility into network performance metrics.

[0026] Another objective of the present disclosure is to provide a system and a method that facilitates continuous visibility of network performance metrics.

[0027] Yet another objective of the present disclosure is to provide a system and a method for efficient data storage and retrieval mechanisms within the NFs.

[0028] 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

[0029] In an exemplary embodiment, a method for monitoring data transmission in a network is described. The method includes establishing, by a communication unit, a connection between at least one network function and a network management system (NMS). In response to establishing the connection, the methodfurther includes receiving, by a receiving unit, a reset request from the NMS. The method includes generating, by a generating unit, at least one counter file of a predefined time interval upon receiving the reset request from the NMS. The method further includes monitoring, by a scheduling unit, a database at a predefined time to detect if at least one counter file generated by the generating unit within the predefined time interval is missing from the database, wherein each counter file of the at least one counter file is stored in the database with an associated timestamp. Upon monitoring, the method further includes restoring, by the scheduling unit, the at least one missing counter file in the database. The at least one missing counter file is restored using a local server associated with the at least one network function. The local server stores one or more counter files that are generated within the predefined time interval to enable access to one or more other network functions. The method further includes receiving, by the receiving unit, an audit request from the NMS to provide the at least one counter file missing from the one or more counter files generated in the predefined time interval, the NMS sends the audit request to the at least one network function upon resumption of a stable connection after detecting disruption in connectivity with the at least one network function. The method further includes obtaining, by the scheduling unit, the at least one missing counter file restored in the database in response to the received audit request. The method further includes transmitting, by the communication unit, the at least one missing counter file obtained from the database to the NMS.

[0030] In an embodiment, the one or more counter files stored in the local server and the database comprise a record of one or more network activities, and performance metrics associated with the at least one network function, and wherein the NMS retrieves the one or more counter files to monitor and analyze performance of the at least one network function.

[0031] In an embodiment, the at least one counter file is missing from the database when the connection between the NMS and the at least one network function is not successfully established due to an unstable connection in the network.

[0032] In an embodiment, the audit request comprises time period detail specifying a missing time period during which the at least one counter file is missing.

[0033] In an embodiment, to obtain the at least one missing counter file restored in the database, the method includes extracting, by the scheduling unit, the missing time period associated with the at least one counter file from the audit request. The method further includes querying, by the scheduling unit, the database using the missing time period to locate the at least one missing counter file. The at least one missing counter file is located among a plurality of counter files that are stored in the database based on the timestamp of each of the plurality of counter files. The method further includes extracting, by the scheduling unit, the at least one missing counter file from the database.

[0034] In an embodiment, the method further includes displaying, by the NMS, the one or more counter files on a user interface (UI) to present one or more performance metrics of the at least one network function for monitoring and analysis.

[0035] In another exemplary embodiment, a system for monitoring data transmission in a network is disclosed. The system includes a communication unit configured to establish a connection between at least one network function and a network management system (NMS). In response to establishing the connection, the system further includes a receiving unit configured to receive a reset request from the NMS. The system further includes a generating unit configured to generate at least one counter file of a predefined time interval upon receiving the reset request from the NMS. The system further includes a scheduling unit configured to monitor a database at a predefined time to detect if at least one counter file generated by the generatingunit within the predefined time interval is missing from the database, each counter file of the at least one counter file is stored in the database with an associated timestamp. Upon monitoring, the scheduling unit is configured to restore the at least one missing counter file in the database. The at least one missing counter file is restored using a local server associated with the at least one network function. The local server stores one or more counter files that are generated within the predefined time interval to enable access to one or more other network functions. The receiving unit further receives an audit request from the NMS to provide the at least one counter file missing from the one or more counter files generated in the predefined time interval. The NMS sends the audit request to the at least one network function upon resumption of a stable connection after detecting disruption in connectivity with the at least one network function. The scheduling unit is further configured to obtain the at least one missing counter file restored in the database in response to the received audit request. The communication unit is further configured to transmit the at least one missing counter file obtained from the database to the NMS.

[0036] In yet another exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for monitoring data transmission in a network. The method includes establishing, by a communication unit, a connection between at least one network function and a network management system (NMS). In response to establishing the connection, the method further includes receiving, by a receiving unit, a reset request from the NMS. The method includes generating, by a generating unit, at least one counter file of a predefined time interval upon receiving the reset request from the NMS. The method further includes monitoring, by a scheduling unit, a database at a predefined time to detect if at least one counter file generated by the generating unit within the predefined time interval is missing from the database, wherein each counter file of the at least one counter file is stored in the database withan associated timestamp. Upon monitoring, the method further includes restoring, by the scheduling unit, the at least one missing counter file in the database. The at least one missing counter file is restored using a local server associated with the at least one network function. The local server stores one or more counter files that are generated within the predefined time interval to enable access to one or more other network functions. The method further includes receiving, by the receiving unit, an audit request from the NMS to provide the at least one counter file missing from the one or more counter files generated in the predefined time interval, the NMS sends the audit request to the at least one network function upon resumption of a stable connection after detecting disruption in connectivity with the at least one network function. The method further includes obtaining, by the scheduling unit, the at least one missing counter file restored in the database in response to the received audit request. The method further includes transmitting, by the communication unit, the at least one missing counter file obtained from the database to the NMS.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

[0037] 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 is 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.

[0038] FIG. 1A illustrates an exemplary network architecture of a system for monitoring data transmission in a network, in accordance with an embodiment of the present disclosure.

[0039] FIG. IB illustrates an exemplary system architecture, in accordance with an embodiment of the present disclosure.

[0040] FIG. 2 illustrates an exemplary block diagram of the system, in accordance with an embodiment of the present disclosure.

[0041] FIG. 3 illustrates an exemplary flow diagram of a method for monitoring the data transmission in the network, in accordance with an embodiment of the present disclosure.

[0042] FIG. 4 illustrates another exemplary flow diagram of a method for monitoring the data transmission in the network, in accordance with an embodiment of the present disclosure

[0043] FIG. 5 illustrates an example computer system in which or with which the embodiments of the present disclosure may be implemented.

[0044] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 A - Network Architecture102 - Users104 - User Equipment (UE)106 - Network108 - System110 - Network function (NF) Clusters112 - Base Stations114 - Network management system (NMS) 116 - Fault, configuration, accounting, performance, and security management(FCAPS) Manager116-1 - FCAPS active116-2 - FCAPS spare100B - System Architecture 200 - Block Diagram202 - Processor(s)204 - Memory206 - Interface(s)208 - Processing Engine 210 - Communication Unit212 - Receiving Unit214 - Generating Unit216 - Scheduling Unit218 - Database300, 400 - Method Steps500 - Computer system510 - External Storage Device520 - Bus530 - Main Memory540 - Read Only Memory550 - Mass Storage Device560 - Communication Port570 - ProcessorDETAILED DESCRIPTION

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

[0046] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather,the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

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

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

[0049] 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 ordinaryskill 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.

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

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

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

[0053] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog, offering only voice services. Further, text messaging and data services became possible when the second-generation (2G) technology was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Currently, fifth generation (5G) technology is being deployed, offering significantly faster data speeds, lower latency, and the ability to connect many devices simultaneously. Further, sixth generation (6G) successor to 5G is expected to provide significantly high data speed with reduced latency, which may offer improved connectivity for a vast number of devices concurrently. The capabilities of 6G enable new types of applications and services, such as advanced augmented reality (AR) and virtual reality (VR), holographic communications, and more immersive digital experiences. These advancements represent a significant leap forward from previous generations, enabling enhanced mobile broadband, improved Internet of Things (loT) connectivity, and more efficient use of network resources. The 6G technology promisesto build upon these advancements, pushing the boundaries of wireless communication even further. While the 5G technology is still being rolled out globally, research and development into the 6G are rapidly progressing, with the aim of revolutionizing the way we connect and interact with technology.

[0054] In a network architecture, monitoring data transmission (e.g., counter file) between at least one network function (hereafter referred to as NF) and a Network management system (NMS) is tedious and cumbersome, as the network has a wide range of NFs. In a conventional technique, the data transmission between the NFs and the NMS is monitored and managed through manual intervention, such as a network administrator keeping track of various network metrics. The network metrics include throughput, uptime / downtime rate, error rates, and response times to user requests. The network administrator may have to record the various network metrics to ensure the smooth functioning of the network. The network metrics are gathered from the NFs and analyzed by the NMS. At times, the network may face fluctuations and loss of connectivity that impede the network monitoring and management process by the network administrator. The network administrator manually recovers the network from fluctuations and records the issues. The loss of connectivity or network fluctuation may interrupt the data transmission between the network components, such as the NFs and NMS. The impact of such interruptions can be extreme, as inaccurate or incomplete data leads to misinformed decision-making during network management tasks.

[0055] To have a real-time view of network conditions, a continuous flow of accurate data is essential. Without this, it is challenging to promptly identify and address potential issues or anomalies. Additionally, gaps in data transmission make it difficult to assess long-term network performance or detect patterns that could indicate upcoming problems.

[0056] The present disclosure addresses the challenge of maintaining uninterrupted data transmission (counter file) between the NFs and the NMS duringperiods of network instability. Specifically, when connectivity between the NMS and the NFs is temporarily disrupted, resulting in the loss of the counter file, the present disclosure enables the NFs to store the counter file in a local database. Upon the restoration of connectivity, the NMS is enabled to initiate an audit request for the counter file corresponding to the periods of disruption. The counter file refers to the quantitative measurements or records of network activities or performance metrics that the NFs collect and maintain. During periods of instability or connectivity disruptions, the NFs autonomously store the counter file in the local database (e.g., local server) to ensure that no information is lost despite the communication breakdown with the NMS. This stored data includes metrics such as traffic volumes, error rates, and other performance indicators that are essential for accurate network monitoring and management. Once connectivity is restored, the NMS can request this stored counter file to ensure a complete and accurate view of network performance during the disruption period.

[0057] In response to the audit request, the NFs access the locally stored database to retrieve and compile the counter file for the affected time intervals. The retrieved data is then transmitted to the NMS. This mechanism ensures that the NMS obtains a comprehensive and accurate set of counter files, notwithstanding any connectivity interruptions, by utilizing robust data storage and retrieval capabilities within the NFs. Consequently, this approach enhances the reliability and accuracy of network monitoring and management functions, effectively mitigating the impact of connectivity issues on data continuity and integrity.

[0058] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1 A - FIG. 5.

[0059] FIG. 1A illustrates an exemplary network architecture (100 A) of a system (108) for monitoring the data transmission in a network (106), in accordance with an embodiment of the present disclosure.

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

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

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

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

[0064] The system (108) may include a fault, configuration, accounting, performance, and security management (FCAPS) manager (116), a network management system (NMS) (114), and a plurality of network function (NF) clusters (NF cluster-1 110-1, NF cluster-2 110-2.... NF cluster-N 110-N) collectively referred to as the NF clusters (110).

[0065] In an aspect, the plurality of base stations (112) interacts with the NF clusters (110) to manage user access, enforce policies, establish and manage data sessions, and handle data traffic. The FCAPS manager (116) is a microservice used in network management that performs tasks such as monitoring, configuring, accounting for, optimizing, and securing the network (106), ensuring that interactions between the plurality of base stations (112) and the NF clusters (110) are properly managed.

[0066] In an aspect, the FCAPS manager (116) may implement at least one FCAPS microservice to manage and monitor network infrastructure effectively. The FCAPS manager (116) manages the functional areas of fault, configuration, accounting, performance, and security in the network (106), ensuring that the network (106) operates smoothly, securely, and efficiently. In an aspect, the fault managementis to detect, diagnose, and resolve network faults or issues. The fault management involves real-time monitoring of network devices and services, generation of alerts for detected issues, and tools for troubleshooting and resolving faults. In an aspect, the configuration management is performed to manage and control the configuration of network devices and services. The configuration management includes deploying, modifying, and managing configurations across network devices, tracking configuration changes, backing up configurations, and ensuring consistency. In an aspect, the accounting management tracks and reports on network resource usage and activities. The accounting management includes collecting and analyzing data on network usage, generating reports for billing or auditing, and managing usage statistics. In an aspect, the performance management is to monitor and optimize the performance of the network (106). The performance management is used for measuring and analyzing network performance metrics such as bandwidth, latency, and throughput. The performance management includes performance dashboards, alerting for performance degradation, and capacity planning. In an aspect, the security management is performed to protect the network (106) from security threats and manage security policies. Security management is used to implement security measures, monitor for security breaches, and manage access controls. The security management further includes intrusion detection systems, firewall management, and security policy enforcement.

[0067] In an aspect, the NMS (114) is configured to monitor, manage, and maintain the infrastructure of the network (106). The NMS (114) provides centralized control over the network devices, such as routers, switches, servers, and other network components, ensuring the network operates efficiently, securely, and reliably.

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

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

[0070] In an embodiment, the UE (104) is communicatively coupled with the system (108). The system (108) may receive a connection request from the UE (104). The system (108) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request. The system (108) is configured for monitoring continuous data transmission between the NF clusters (110) and the NMS (114) in the network (106).

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

[0072] FIG. IB illustrates an exemplary system architecture (100B) for monitoring the data transmission in the network (106), in accordance with an embodiment of the present disclosure.

[0073] In an embodiment, the system architecture (100B) may include the NF clusters (110), the FCAPS manager (116) and the NMS (114). In an aspect, the FC APS manager (116) may include an FCAPS active (116-1) and an FCAPS spare (116-2). In an aspect, the FCAPS spare (116-2) is on standby and ready to take on the responsibilities of the FCAPS active (116-1) if the FCAPS active (116-1) fails or becomes unresponsive. In response to the failure detection of the FCAPS active (116- 1) due to network issues, the FCAPS spare (116-2) may take over to perform the tasks. This helps maintain continuous service and minimizes disruptions (i.e., high availability and reliability). In an aspect, the FCAPS active (116-1) may assign a plurality of microservices (e.g., active microservices and spare microservices) formanaging data of the NF clusters (110). The FCAPS active (116-1) may activate the spare microservice if the active microservice fails or becomes unresponsive.

[0074] In an embodiment, each NF in the NF clusters (110) may be configured to generate data (counter file) based on various operational parameters associated with the network (106). The generated data may include performance metrics, usage statistics, and other relevant information that may be used for monitoring, optimization, and decision-making processes within the network (106). In an aspect, the data may be session data, policy data, authentication data, access data, and network performance data. For example, the network function may be the SMF. The SMF may be responsible for handling session-related tasks. These tasks may include the establishment, modification, and release of sessions between the UE (104) and the network (106). The data may be session establishment data, session modification data, session termination data, network statistics, or performance data. The data may be stored in the memory or the database (210).

[0075] In an embodiment, the FCAPS manager (116) may initiate one or more requests to retrieve the data (counter file) from the NF clusters (110). In an exemplary aspect, the one or more requests may be a proxy request. The proxy request may be initiated on behalf of the NMS (114). The proxy request may include a forward request, a reverse proxy, a transparent proxy, and a caching proxy. The requests may be processed by the NF clusters (110).

[0076] In an embodiment, when the network connection is stable, the NMS (114) may be configured to send a request (normal request / reset request) to the NF clusters (110) for receiving data from the NF clusters (110). The request may include a Hypertext Transfer Protocol (HTTP) request, a Domain Name System (DNS) request, a network service request, a network management request and an Application Programming Interface (API) request. In an aspect, the NMS (114) is configured to send the normal request if a network connection between the NF cluster and the NMSis a stable connection (no network fluctuations). The stable connection may be a consistent and reliable network connectivity. In an aspect, each NF is configured to generate the data, even if the connection between the NF and NMS is disturbed (unstable). The generated data is referred to as the counter file. In an aspect, the counter file may include a network counter, an error counter, a latency and response time counter, a connection counter, and a protocol counter. The NF clusters (110) may store the data on the local server. The FCAPS manager (116) may be configured to broadcast the request to the plurality of NF clusters (110). The NF clusters (110) may send the data to the FCAPS manager (116) by retrieving the data from the local database or the server. In an aspect, the FCAPS manager (116) may be configured to handle faults, manage configurations, track usage, and optimize performance. For example, the data sent by the NF cluster (110) may be used by the FCAPS manager (116) to continuously track performance metrics such as bandwidth, latency, and packet loss. The FCAPS manager (116) gathers the data and applies new configurations or updates to the network resources.

[0077] The FCAPS manager (116) may establish a connection with each of the plurality of NF clusters (110) to be monitored. The FCAPS manager (116) enables network management using the NMS (e.g., NMS (114)) for the plurality of NF clusters (110) within the network (106). The FCAPS-NMS architecture or platform is used to monitor and manage the health, configuration, performance, and security aspects of all NF clusters (110) from a single interface. The FCAPS manager (116) may collect the data from the plurality of NF clusters (110) based on the request initiated by the NMS (114). The FCAPS manager (116) may provide the retrieved data to the NMS (114).

[0078] In an aspect, the NMS (114) may stop sending any request to the NF cluster (110) if there are fluctuations in the network (106) and the connection between the NF cluster (110) and the NMS (114) is an unstable connection. Once the network connection is stable again, the NMS (114) may be configured to generate an audit1 request. In another embodiment, the NMS (114) may be configured to send the audit request to the NF clusters (110) via the FCAPS manager (116). The unstable connection may indicate a condition of loss of network connectivity or fluctuation in network connectivity. The one or audit requests may include a performance audit request, a network audit request, a compliance audit request, and a security audit request. The NMS (114) may be configured to initiate the audit request to retrieve one or more counter files that are missed during the unstable connection of the network (106).

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

[0080] FIG. 2 illustrates an exemplary block diagram (200) of the system (108) for monitoring data transmission (e.g., counter file) in the network (106), in accordance with an embodiment of the present disclosure. FIG. 2 is explained in conjunction with FIGS. lA and IB.

[0081] In an embodiment, the monitoring of the data transmission may refer to ensuring a reliable delivery of counter data (e.g., counter files) from at least one NF of the NF clusters (110) to the NMS (114) over the network (106). This includes tracking whether the counter file is transmitted to the NMS (114) without interruption, detecting transmission failures or delays, and initiating corrective actions such as triggering the audit request to recover the counter file that is missed during transmission failure. The counter file may refer to a set of numerical values or performance statistics collected and maintained by the NFs (e.g., NF clusters 110) in a database, such as a database 218to reflect operational state and activity levels of the network (106). The counter file may include metrics such as traffic volume, session counts, error rates, latency, packet loss, bandwidth usage, and resource utilization. The counter file is incremented or updated during normal operation and periodically transmitted to the NMS (114) for monitoring, analysis, and optimization of network performance.

[0082] 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). 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 include 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.

[0083] In an embodiment, the system (108) may include an interface(s) (206). The interface(s) (206) may include a variety of interfaces, for example, interfaces for data input and output devices (VO), storage devices, and the like. The interface(s) (206) may facilitate communication through the system (108). The interface(s) (206) may also provide a communication pathway for one or more components of the system (108). Examples of such components include, but are not limited to, a processing engine (208) and a database (218).

[0084] In an embodiment, the processing engine (208) may be implemented as a combination of hardware and programming (for example, programmableinstructions) to implement one or more functionalities of the processing engine (208). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine (208) may be processor-executable instructions stored on a non- transitory machine-readable storage medium. The hardware for the processing engine (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine (208). In such examples, the system (108) may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system and the processing resource. In other examples, the processing engine (208) may be implemented by electronic circuitry.

[0085] The processing engine (208) may include various modules, such as a communication unit (210), the receiving unit (212), the generating unit (214), and the scheduling unit (216). In an embodiment, the processing engine (208) may be configured to monitor the data transmission in the network (106).

[0086] The communication unit (210) is configured to establish a connection between at least one NF of the NF clusters (110) andtheNMS (114). In an embodiment, the communication unit (214) may initialize a defined interface (e.g., HTTP interface) to set up a connection to each of the plurality of NF clusters (110) to be monitored. In an aspect, the HTTP interface may establish a connection between the FCAPS manager (116) and each of the plurality of NF clusters (110) to facilitate communication with the plurality of NF clusters (110).

[0087] Upon establishing the connection, the receiving unit (212) is configured to receive a reset request (normal request) from the NMS (114). In an embodiment, thereceiving unit (212) may receive the reset request from the NMS (114). In an embodiment, the reset request is a periodic and routine request initiated by the NMS (114). The reset request is triggered at predefined intervals (e.g., after every 15 minutes) based on a system schedule or configuration and is part of a regular counter lifecycle in normal operating conditions (e.g., stable connection conditions).

[0088] Upon receiving the reset request from the NMS (114), the generating unit (214) is configured to generate at least one counter file of a predefined time interval (e.g., the last 15 minutes). The counter file contains a record of one or more network activities (e.g., session establishment, handovers, bearer modifications, user plane activity) and performance metrics (e.g., resource utilization, memory consumption, traffic volume, error rates, and latency) associated with at least one NF, and it is produced on a regular schedule set by the respective at least one NF. The interval at which these counter files are created is predetermined based on operational requirements or performance monitoring needs. This ensures that the NMS (114) receives up-to-date information about the NF’s status and activities.

[0089] In an embodiment, after generating the at least one counter file, the NF stores the at least one counter file in a local storage (e.g., a local server, a cache memory, a random access memory (RAM), etc.) and the database (218). The at least one counter file may be stored in a form, for example, an Excel file, a text file, a comma-separated file (CSV), etc. In an embodiment, the local server stores one or more counter files that are generated within the predefined time interval to enable access to one or more other NFs of the NF clusters (110). Additionally, the database (218) stores the one or more counter files that are generated within the predefined time interval to enable access to the NMS (114). In an embodiment, each counter file of the at least one counter file is stored in the database (218) with an associated timestamp. The timestamp records the exact date and time when the counter file was created. This storage mechanism ensures that each counter file is preserved with its associated timeinformation, allowing for precise tracking and retrieval of historical data. The inclusion of the timestamp is crucial for accurate data management and analysis, as it provides context for when the data was collected.

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

[0091] The scheduling unit (216) is configured to monitor the database (218) at a predefined time to detect if at least one counter file generated by the generating unit (214) within the predefined time interval is missing from the database (218). In an embodiment, the scheduling unit (216) may detect that the at least one counter file is missing from the database (218) when the connection between the NMS (114) and the at least one NF is interrupted due to an unstable connection in the network (106).

[0092] In an aspect, the scheduling unit (216) may periodically check for the counter file in the database (218) or the local server. The periodic check may be performed at a predefined time. The predefined time may include a minute, an hour, a day, etc. In an embodiment, the scheduling unit (216) may be configured to managethe order and timing of data transmission and processing to ensure efficient network operation and performance. For example, the scheduling unit (216) may perform a periodical check after every 2 minutes of generating the counter file to determine whether the counter file is successfully stored in the local server as well as the database (210). By doing so, the NF ensures regular and reliable checks for the counter file, which may be crucial for tracking and managing data or system performance.

[0093] Upon detecting that the at least one counter file is missing, the scheduling unit (216) is configured to restore the at least one missing counter file in the database (218). In an embodiment, the at least one missing counter file may be restored using the local server associated with the at least one NF. The restoring involves accessing the local server, which temporarily stores the counter file generated during the relevant time intervals. These locally stored files are preserved to ensure redundancy and accessibility by other NFs within the NF clusters (110). The restored counter file contains the same network activity logs and performance metrics as originally intended.

[0094] Upon resumption of a stable connection after detecting disruption in connectivity with the at least one NF, the receiving unit (212) further receives an audit request from the NMS (114) to provide the at least one counter file missing from the one or more counter files generated in the predefined time interval. In an embodiment, the audit request includes a time period detail specifying a missing time period during which the at least one counter file is missing.

[0095] The scheduling unit (216) is further configured to obtain the restored counter file (e.g., the at least one missing counter file that is restored in the database (218)) in response to the received audit request. In an embodiment, to obtain the at least one missing counter file restored in the database (218), the scheduling unit (216) extracts the missing time period (i.e., the duration during which one or more counterfiles were not received by the NMS (114) due to the network disruption) associated with the at least one counter file from the audit request.

[0096] Once the missing time period is determined, the scheduling unit (216) perform a query operation on the database (218) using the missing time period to locate the at least one missing counter file. The at least one missing counter file is located among a plurality of counter files that are stored in the database (218) based on the timestamp of each of the plurality of counter files. The database (218) maintains a collection of counter files, each tagged with a unique timestamp indicating when the file was generated. The scheduling unit (216) searches through these timestamps to accurately locate the counter files that fall within the identified missing time window.

[0097] Upon successful identification, the scheduling unit (216) extracts (or retrieves) the at least one missing counter file from the database (218). These retrieved counter files represent the counter data that was originally generated by the NF during the connection outage but was not delivered to the NMS (114) at that time. By executing this retrieval process, the scheduling unit (216) ensures that any gaps in performance data caused by intermittent connectivity are efficiently closed, thereby enabling the NMS (114) to maintain a complete and consistent monitoring record.

[0098] The communication unit (210) is configured to transmit the at least one missing counter file obtained from the database (210) to the NMS (114). In an embodiment, the NMS (114) retrieves the at least counter file to monitor and analyze the performance of at least one NF. This includes examining various performance indicators such as session activity, error rates, resource usage, traffic volume, and latency metrics that were recorded by the at least one NF during the missing time window.

[0099] In an embodiment, the NMS (114) may display the one or more counter files on a user interface (UI) to present one or more performance metrics of the at leastone network function for monitoring and analysis, enabling network operators and administrators to quickly assess operational status, detect anomalies, and make informed decisions. By ensuring that even the previously missed counter data is made available to the NMS (114), the system (108) helps to maintain the continuity, accuracy, and completeness of network performance monitoring and analysis operations.

[0100] FIG. 3 illustrates an exemplary flow diagram of a method (300) for monitoring the data transmission in the network (106), in accordance with an embodiment of the present disclosure. FIG. 3 is explained in conjunction with FIGS. 1A, IB, and 2. Each step of the method (300) may be performed by various modules (e.g., the communication unit (210), the receiving unit (212), the generating unit (214), and the scheduling unit (216)) of the processing engine (208).

[0101] At step 302, an application associated with the FCAPS manager (116) is configured (started) for monitoring the data transmission between the plurality of NF clusters (110) and the NMS (114) in the network (106). In an embodiment, the application associated with the FCAPS manager (116) may be, for example, a microservice responsible for monitoring data transmission (counter file) between the plurality of NF clusters (110) and the NMS (114).

[0102] At step 304, a connection is established between the application and the NMS (114). In particular, the NMS (114) may establish the connection with the FCAPS manager (116) and the plurality of NF clusters (110). The plurality of NF clusters (110) may establish the connection to receive one or more requests from the NMS (114). For example, one or more requests may be a Hypertext Transfer Protocol (HTTP) connection request, a Domain Name System (DNS) request, a Dynamic Host Configuration Protocol (DHCP) request, and an Internet Control Message Protocol (ICMP) request.

[0103] At steps 306 and 310, the processing engine (208) may determine whether the network (106) is stable (no fluctuation) or unstable (fluctuation). This determination may be conducted by determining no interruption in the network (106) upon the successful establishment of the connection with the NF clusters (110). The NMS (114) establishes the connection with the plurality of NF clusters (110) via the FCAPS manager (116).

[0104] Upon determining that the network (106) is stable (no fluctuation), at step 308, the NMS (114) may send a reset request (i.e., the normal request) to the NF clusters (110). The reset request may be used for requesting data (counter file) from the NF clusters (110) via the FCAPS manager (116) at a regular time interval (say, after every 15 minutes). In an aspect, each NF cluster (110) may generate the counter file (such as session data, policy data, authentication data, access data, performance data, etc.) and store it in both the local storage and the database (218). The local storage may be a local server, a cache memory, a Random Access Memory (RAM), or a secondary storage. The database (218) may be used for long-term storage and recovery purposes. On receiving the audit request, the NF clusters (110) may retrieve the counter file from the local storage. The retrieved counter file may be sent to the NMS (114) as a response via the FCAPS manager (116). For example, a response may be an HTTP response. The HTTP response may include a status code, a header, and a body. For example, the response may be a result sent by the NF clusters (110) after processing the normal request. The response may include a snapshot of the data stored in the local storage. The snapshot may include the counter file or data related to a particular time. The data may include network metrics, performance metrics, and usage metrics. The particular time may be a minute, an hour, a day, a week, etc.

[0105] Upon determining that the network (106) is unstable (having network fluctuation) and is unable to establish the connection with the NF clusters (110), at step 312, an audit request is initiated by the NMS (114) when the counter data does notreach the NF clusters (110) due to network fluctuation or loss of network connection. In an embodiment, the NMS (114) may trigger the audit request to the NF clusters (110) via the FCAPS manager (116). The audit request may be sent to the NF clusters (110) after the resumption of the network connectivity. The audit request may be initiated to retrieve one or more missing counter files that may have been missed during a certain time period of the unstable connection. The missing counter file may be the data that is missed for a particular time period due to network fluctuation or a loss of network connection. For example, the particular time period may be represented as 11.15 AM to 11.23 AM. The audit request may be sent with a timestamp for the one or more missed counter files. The timestamp may include a time and date. For example, the timestamp may represent date (e.g., 02 / 08 / 2025) and time (e.g., 12:15 AM). In response to the audit request, the NF clusters (110) may retrieve the missed counter files from the database (218) and send the missed counter files to the NMS (114). The NMS (114) may receive a response to the audit request. The response may include an acknowledgement for the missing counter file retrieved from the database (218) via the FCAPS manager (116).

[0106] In an aspect, the NF cluster (110) may trigger the scheduling unit (216) whenever a request is received from the NMS (114). The request may be an audit request or a normal request. In an aspect, the scheduling unit (216) performs a periodic check for the counter file stored in the database (218) and the local server. If any data is missing in the database (218) or local memory, the scheduling unit (216) may capture a data snapshot from the NF cluster (110) and store it in the local server and the database (218).

[0107] At step 314, the NMS (114) may collect the counter file and send it to an application counter. The NF maintains the application counter that tracks ongoing activities and performance metrics. The counter file can be visualized through a dashboard, which provides a graphical representation of various performanceindicators and ongoing activities. After retrieving the counter file from the database (218), the NF transmits the counter file to the NMS (114). The data provided may include various metrics related to at least one NF’s performance, usage statistics, and other relevant information.

[0108] At step 316, upon receiving the counter file, the NMS (114) may update an associated dashboard to reflect the received counter file. The NMS dashboard may provide real-time or historical views of the at least one NF’s performance and help in monitoring and analysis.

[0109] FIG. 4 illustrates another exemplary flow diagram of a method (400) for monitoring the data transmission in the network (106), in accordance with an embodiment of the present disclosure. FIG. 4 is explained in conjunction with FIGS. 1 A, IB, 2, and 3. In an embodiment, each step of the method (400) may be performed by various modules (e.g., the communication unit (210), the receiving unit (212), the generating unit (214), and the scheduling unit (216)) of the processing engine (208).

[0110] At step 402, a communication unit (210) is configured to establish a connection between at least one NF and the NMS (114). In response to establishing the connection, at step 404, the receiving unit (212) is configured to receive a reset request from the NMS (114).

[0111] At step 406, the generating unit (214) is configured to generate at least one counter file of a predefined time interval upon receiving the reset request from the NMS (114).

[0112] At step 408, the scheduling unit (216) is configured to monitor a database (218) at a predefined time to detect if at least one counter file generated by the generating unit (214) within the predefined time interval is missing from the database (218). In an embodiment, each counter file of the at least one counter file is stored in the database (218) with an associated timestamp. In an embodiment, the atleast one counter file is missing from the database (218) when the connection between the NMS (114) and the at least one NF is not successfully established due to an unstable connection in the network (106).

[0113] Upon monitoring, at step 410, the scheduling unit (216) is configured to restore the at least one missing counter file in the database (218). The at least one missing counter file is restored using a local server associated with the at least one NF. In an embodiment, the local server stores one or more counter files that are generated within the predefined time interval to enable access to one or more other NFs of the NF clusters (110). In an embodiment, the one or more counter files stored in the local server and the database (218) include a record of one or more network activities, and performance metrics associated with the at least NF.

[0114] At step 412, the receiving unit (212) further receives an audit request from the NMS (114) to provide the at least one counter file missing from the one or more counter files generated in the predefined time interval. The NMS (114) sends the audit request to the at least one NF upon resumption of a stable connection after detecting disruption in connectivity with the at least one NF. In an embodiment, the audit request comprises time period detail specifying a missing time period during which the at least one counter file is missing.

[0115] At step 414, the scheduling unit (216) is further configured to obtain the at least one missing counter file restored in the database (218) in response to the received audit request. In an embodiment, to obtain the at least one missing counter file restored in the database (218), the scheduling unit (216) extracts the missing time period associated with the at least one counter file from the audit request. Further, the scheduling unit (216) queries the database (218) using the missing time period to locate the at least one missing counter file. The at least one missing counter file is located among a plurality of counter files that are stored in the database (218) based on thetimestamp of each of the plurality of counter files. Further, the scheduling unit (216) extracts the at least one missing counter file from the database (218).

[0116] At step 416, the communication unit (210) is further configured to transmit the at least one missing counter file obtained from the database (210) to the NMS (114). In an embodiment, the NMS (114) retrieves the one or more counter files to monitor and analyze the performance of at least one NF. In an embodiment, the NMS (114) may display the one or more counter files on a user interface (UI) to present one or more performance metrics of the at least one network function for monitoring and analysis.

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

[0118] 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 (560), and a processor (570). A person skilled in the art will appreciate that the computer system (500) may include more than one processor (570) and communication ports (560). The processor (570) may include various modules associated with embodiments of the present disclosure.

[0119] In an embodiment, the communication port (560) may be any of an RS- 232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fibre, a serial port, a parallel port, or other existing or future ports. The communication port (560) may be chosen depending on the network (106), such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (500) connects.

[0120] In an embodiment, the memory (530) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory (540) may be any static storage device(s) e.g., but not limited to, aProgrammable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (570).

[0121] In an embodiment, the mass storage (550) may be any current or future mass storage solution, which may be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks (e.g., SATA arrays).

[0122] In an embodiment, the bus (520) communicatively couples the processor(s) (570) with the other memory, storage, and communication blocks. The bus (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).

[0123] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, 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 may be provided through network connections connected through the communication port (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.

[0124] In an exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the oneor more processors to perform a method for monitoring data transmission in a network. The method includes establishing, by a communication unit, a connection between at least one network function and a network management system (NMS). In response to establishing the connection, the method further includes receiving, by a receiving unit, a reset request from the NMS. The method includes generating, by a generating unit, at least one counter file of a predefined time interval upon receiving the reset request from the NMS. The method further includes monitoring, by a scheduling unit, a database at a predefined time to detect if at least one counter file generated by the generating unit within the predefined time interval is missing from the database, wherein each counter file of the at least one counter file is stored in the database with an associated timestamp. Upon monitoring, the method further includes restoring, by the scheduling unit, the at least one missing counter file in the database. The at least one missing counter file is restored using a local server associated with the at least one network function. The local server stores one or more counter files that are generated within the predefined time interval to enable access to one or more other network functions. The method further includes receiving, by the receiving unit, an audit request from the NMS to provide the at least one counter file missing from the one or more counter files generated in the predefined time interval, the NMS sends the audit request to the at least one network function upon resumption of a stable connection after detecting disruption in connectivity with the at least one network function. The method further includes obtaining, by the scheduling unit, the at least one missing counter file restored in the database in response to the received audit request. The method further includes transmitting, by the communication unit, the at least one missing counter file obtained from the database to the NMS.

[0125] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is forillustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0126] 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 is to be implemented merely as illustrative of the disclosure and not as a limitation.

[0127] The present disclosure offers significant technical advancements in monitoring the data transmission in the network. These advancements overcome the limitations of existing solutions by enabling autonomous detection, storage, and retrieval of missing performance counter data during periods of network instability or disconnection. The disclosure involves a scheduler-based mechanism for monitoring counter file availability, timestamped data storage in local servers, and an audit requestresponse process between the NFs and the NMS, which offer significant improvements in data integrity, system reliability, and post-failure recovery efficiency. By implementing a timestamp-based audit mechanism and local data caching within NFs, the disclosure enhances network monitoring and diagnostics, resulting in continuous visibility into NF performance, reduced data loss during outages, and improved decision-making for network operators.ADVANTAGES OF THE PRESENT DISCLOSURE

[0128] The present disclosure provides a method and a system for monitoring data transmission in a network.

[0129] The present disclosure maintains continuous counter file transmission between at least one network function (NF) and a network management system (NMS) during network fluctuations or intermittent connectivity.

[0130] The present disclosure ensures the completeness and accuracy of counter files used for network performance monitoring and analysis, even in the event of interruptions or unstable connections.

[0131] The present disclosure enhances the reliability, efficiency, and effectiveness of network monitoring and management operations by implementing robust mechanisms for autonomous counter storage, timestamping, and retransmissions.

[0132] The present disclosure handles connectivity fluctuations by periodically storing counter files locally and using retransmission strategies to restore any missing data upon resumption of connectivity.

[0133] The present disclosure minimizes the risk of counter data loss and ensures data integrity, thereby enabling continuous visibility of network performance metrics for network administrators.

[0134] The present disclosure ensures robust and resilient data transmission mechanisms between the NFs and the NMS to maintain the integrity and effectiveness of network monitoring and management operations,

Claims

We Claim:

1. A method (400) for monitoring data transmission in a network (106), the method (400) comprising: establishing (402), by a communication unit (210), a connection between at least one network function and a network management system (NMS) (114); in response to establishing the connection, receiving (404), by a receiving unit (212), a reset request from the NMS (114); generating (406), by a generating unit (214), at least one counter file of a predefined time interval upon receiving the reset request from the NMS (114); monitoring (408), by a scheduling unit (216), a database (218) at a predefined time to detect if at least one counter file generated by the generating unit (214) within the predefined time interval is missing from the database (218), wherein each counter file of the at least one counter file is stored in the database (218) with an associated timestamp; upon monitoring, restoring (410), by the scheduling unit (216), the at least one missing counter file in the database (218), wherein the at least one missing counter file is restored using a local server associated with the at least one network function, and wherein the local server stores one or more counter files that are generated within the predefined time interval to enable access to one or more other network functions; receiving (412), by the receiving unit (212), an audit request from the NMS (114) to provide the at least one counter file missing from the one or more counter files generated in the predefined time interval, wherein the NMS (114) sends the audit request to the at least one network function upon resumption of a stable connection after detecting disruption in connectivity with the at least one network function; obtaining (414), by the scheduling unit (216), the at least one missing counter file restored in the database (218) in response to the received audit request; andtransmitting (416), by the communication unit (210), the at least one missing counter file obtained from the database (218) to the NMS (114).

2. The method (400) as claimed in claim 1 , wherein the one or more counter files stored in the local server and the database (218) comprise a record of one or more network activities, and performance metrics associated with the at least one network function, and wherein the NMS (114) retrieves the one or more counter files to monitor and analyze performance of the at least one network function.

3. The method (400) as claimed in claim 1, wherein the at least one counter file is missing from the database (218) when the connection between the NMS (114) and the at least one network function is not successfully established due to an unstable connection in the network (106).

4. The method (400) as claimed in claim 1, wherein the audit request comprises time period detail specifying a missing time period during which the at least one counter file is missing.

5. The method (400) as claimed in claim 4, wherein obtaining the at least one missing counter file restored in the database (218) comprises: extracting, by the scheduling unit (216), the missing time period associated with the at least one counter file from the audit request; querying, by the scheduling unit (216), the database (218) using the missing time period to locate the at least one missing counter file, wherein the at least one missing counter file is located among a plurality of counter files that are stored in the database (218) based on the timestamp of each of the plurality of counter files; and extracting, by the scheduling unit (216), the at least one missing counter file from the database (218).

6. The method (400) as claimed in claim 1, comprising: displaying, by the NMS (114), the one or more counter files on a user interface (UI) to present one or more performance metrics of the at least one network function for monitoring and analysis.

7. A system (108) for monitoring data transmission in a network (106), the system (108) comprising: a communication unit (210) configured to establish a connection between at least one network function and a network management system (NMS) (114); a receiving unit (212) configured to receive a reset request from the NMS (114) in response to establishing the connection; a generating unit (214) configured to generate at least one counter file of a predefined time interval upon receiving the reset request from the NMS (114); a scheduling unit (216) configured to monitor a database (218) at a predefined time to detect if at least one counter file generated the generating unit (214) within the predefined time interval is missing from the database (218), wherein each counter file of the at least one counter file is stored in the database (218) with an associated timestamp; upon monitoring, the scheduling unit (216) configured to restore the at least one missing counter file in the database (218), wherein the at least one missing counter file is restored using a local server associated with the at least one network function, and wherein the local server stores one or more counter files that are generated within the predefined time interval to enable access to one or more other network functions; the receiving unit (212) configured to receive an audit request from the NMS (114) to provide the at least one counter file missing from the one or morecounter files generated in the predefined time interval, wherein the NMS (114) sends the audit request to the at least one network function upon resumption of a stable connection after detecting disruption in connectivity with the at least one network function; the scheduling unit (216) configured to obtain by the at least one network function, the at least one missing counter file restored in the database (218) in response to the received audit request; and the communication unit (210) to transmit the at least one missing counter file obtained from the database (218) to the NMS (114).

8. The system (108) as claimed in claim 7, wherein the one or more counter files stored in the local server and the database (218) comprise a record of one or more network activities, and performance metrics associated with the at least one network function, and wherein the NMS (114) retrieves the one or more counter files to monitor and analyze performance of the at least one network function.

9. The system (108) as claimed in claim 7, wherein the at least one counter file is missing from the database (218) when the connection between the NMS (114) and the at least one network function is not successfully established due to an unstable connection in the network.

10. The system (108) as claimed in claim 7, wherein the audit request comprises time period detail specifying a missing time period during which the at least one counter file is missing.

11. The system (108) as claimed in claim 10, to obtain the at least one missing counter file restored in the database (218), the scheduling unit (216) is configured to:extract the missing time period associated with the at least one counter file from the audit request; query the database (218) using the missing time period to locate the at least one missing counter file, wherein the at least one missing counter file is located among a plurality of counter files that are stored in the database (218) based on the timestamp of each of the plurality of counter files; and extract the at least one missing counter file from the database (218).

12. The system (108) as claimed in claim 7, wherein the NMS (114) is configured to: display the one or more counter files on a user interface (UI) to present one or more performance metrics of the at least one network function for monitoring and analysis.

13. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method (400) for monitoring data transmission in a network, the method (400) comprising: establishing (402), by a communication unit (210), a connection between at least one network function and a network management system NMS (114); in response to establishing the connection, receiving (404), by a receiving unit (212), a reset request from the NMS (114); generating (406), by a generating unit (214), at least one counter file of a predefined time interval upon receiving the reset request from the NMS (114); monitoring (408), by a scheduling unit (216), a database (218) at a predefined time to detect if at least one counter file generated by the generating unit (214) within the predefined time interval is missing from the database (218), wherein each counter file of the at least one counter file is stored in the database (218) with an associated timestamp;upon monitoring, restoring (410), by the scheduling unit (216), the at least one missing counter file in the database (218), wherein the at least one missing counter file is restored using a local server associated with the at least one network function, and wherein the local server stores one or more counter files that are generated within the predefined time interval to enable access to one or more other network functions; receiving (412), by the receiving unit (212), an audit request from the NMS (114) to provide the at least one counter file missing from the one or more counter files generated in the predefined time interval, wherein the NMS (114) sends the audit request to the at least one network function upon resumption of a stable connection after detecting disruption in connectivity with the at least one network function; obtaining (414), by the scheduling unit (216), the at least one missing counter file restored in the database (218) in response to the received audit request; and transmitting (416), by the communication unit (210), the at least one missing counter file obtained from the database (218) to the NMS (114).

Images