A system and method for monitoring connectivity between network node and network management devices

Abstract

The present disclosure may relate to a system (102) for managing connectivity between a network node and network management devices. The system may comprise a memory (204) and processors (202) configured to execute instructions to: fetch, by a data fetching module (212), details of network management devices from a database (210). The connectivity monitoring module (214) sends connectivity requests at predetermined intervals to the network management devices and determine a connectivity status for each network management device based on responses to the requests. A notification module (216) notifies an operational unit to check connectivity when a network management device is determined to be not connected. The system may provide efficient monitoring of connectivity between network nodes and management devices in radio access networks, enabling quick identification of failures and proactive maintenance of network performance.

Description

A SYSTEM AND METHOD FOR MONITORING CONNECTIVITY BETWEEN NETWORK NODE AND NETWORK MANAGEMENT DEVICESRESERVATION 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.FIELD OF THE DISCLOSURE

[0002] The embodiments of the present disclosure generally relate the field of wireless communication networks. In particular, the present disclosure relates to a system and method for managing connectivity between a network node and one or more network management devices.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 to indicate otherwise.

[0004] Radio Access Network (RAN) refers to the part of a mobile telecommunication system that implements radio access technology, connecting user equipment wirelessly to the core network. It typically consists of base stations and antennas covering specific geographical areas called cells. For example, in a 5G network deployment, the RAN would include gNodeB base stations distributed across a metropolitan area, each serving users within a radius of several hundred meters to a few kilometers.

[0005] Network node refers to any device or data point within a larger network infrastructure, typically within a RAN. This includes equipment such as base stations, routers, or switches that play a role in transmitting, receiving, or processing network data. For example, a single gNodeB base station installed on a rooftop that provides 5G coverage to a business would be considered a network node within the larger telecommunications network.

[0006] Network management device refers to specialized hardware and / or software systems used to monitor, configure, and maintain network nodes and overall network infrastructure. These devices provide functionalities such as performance monitoring, fault detection, and configuration management. For example, a server running network management software that monitors the performance of 200 base stations in a metropolitan area, collecting data on throughput, latency, and error rates, would be considered a network management device.

[0007] Element Management System (EMS) refers to a comprehensive package of software applications designed for network management. It provides a suite of end-user applications for monitoring, controlling, and managing network elements from one or multiple vendors. For example, an EMS might provide a graphical interface allowing network engineers to view the status of all network elements on a map, drill down into performance metrics, and apply batch configuration changes to groups of similar devices. It also provides functionalities such as configuration management of base stations, performance monitoring of radio links, fault management, and security administration.

[0008] Connectivity request refers to a message or signal sent to verify the accessibility and responsiveness of a network device. This could be a simple ping, a transmission control protocol (TCP) connection attempt, or a more complex application-level health check. For example, a connectivity monitoring systemmight send an echo request (ping) to a base station every five minutes to verify that the base station is operational and reachable on the network.

[0009] Connectivity status refers to the current state of connection between network elements, typically categorized as "connected," "disconnected," or sometimes intermediate states like "degraded" or "intermittent." For example, if a base station consistently responds to connectivity requests with normal response times, it would be classified as "connected"; if it responds with significantly higher than normal latency, it might be classified as "degraded"; and if it fails to respond altogether, it would be classified as "disconnected."

[0010] Operational unit refers to a team or department responsible for the day-to-day maintenance and operation of network infrastructure, often taking the form of a Network Operations Center (NOC). For example, a telecommunications company might have an operational unit consisting of network technicians working in shifts to provide 24 / 7 monitoring of network performance, with the authority to dispatch field technicians when physical intervention is required at a network site.

[0011] Network Operations Center (NOC) refers to a centralized location where multiple teams continuously monitor and manage the performance and health of a network, equipped with tools for visualizing network status and staffed by technicians who respond to network issues. For example, a telecommunications provider might maintain a NOC with multiple large display screens showing realtime network status maps, performance dashboards, and alert queues, staffed by technicians who work in shifts to provide continuous monitoring and rapid response to incidents.

[0012] Authentication check refers to the process of verifying the identity and access rights of a network device or user, typically involving the verification of credentials such as usernames and passwords or digital certificates. For example, when a network administrator attempts to log into a base station's managementinterface to change configuration settings, the system performs an authentication check by comparing the provided username and password against stored credentials before granting access.

[0013] Ping request refers to a specific type of network probe, formally known as an internet control message protocol (ICMP) Echo Request, used to test the reachability of a host on an Internet Protocol (IP) network. For example, a network monitoring system might send a ping request to a base station at IP address 192.168.1.100, expecting a response within 50 milliseconds; if no response is received, the system might flag the base station as potentially disconnected.

[0014] Source IP refers to the Internet Protocol address of the device sending a network request, typically the network platform or management system initiating connectivity checks or other network operations. For example, a network management server with IP address 10.0.0.5 might send periodic connectivity checks to multiple base stations; in this case, 10.0.0.5 would be the source IP address for these requests.

[0015] Destination IP refers to the Internet Protocol address of the device receiving a network request, typically a network management device or network node being monitored or managed. For example, a base station with IP address 192.168.1.100 that is receiving connectivity checks from a management server would be identified by this destination IP in network traffic analysis and logs.

[0016] Eogin request refers to an attempt to authenticate with a network management device or system by providing credentials, usually involving the submission of a username and password or other authentication data. For example, a monitoring system might automatically send a login request to a base station's management interface every 12 hours using administrative credentials to verify that the authentication system is functioning properly and that the credentials remain valid.

[0017] Predetermined intervals refer to set time periods between recurring actions in network monitoring and management, such as connectivity checks or login attempts, often configurable by network administrators to balance information timeliness with network load considerations. For example, critical core network devices might be configured for connectivity checks every 60 seconds, while less- critical edge devices might be checked every 5 minutes to reduce overall monitoring traffic on the network.BACKGROUND OF THE DISCLOSURE

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

[0019] The present disclosure relates to the field of wireless communication networks, particularly to systems and methods for managing and optimizing the performance of radio access networks (RANs) in advanced mobile communication technologies.

[0020] Wireless communication technology has undergone rapid evolution over the past few decades. From the first generation's analog voice services to the current fifth generation (5G) technology, each advancement has brought significant improvements in capabilities and user experience. The 5G technology, in particular, promises unprecedented data speeds, low latency, and the ability to connect multiple devices simultaneously, opening up new possibilities for various applications and services.

[0021] As wireless technologies advance, radio access networks (RANs) play a crucial role in connecting user equipment to core networks. RANs typically consist of radio base stations with large antennas that wirelessly connect user equipments to the broader network infrastructure. With the advent of 5G and the increasing demand for high-speed, reliable internet services, RANs are becoming increasingly complex. They now need to handle higher speeds, manage a larger number of interconnected units, and integrate various sub-networks into larger, more sophisticated systems.

[0022] The growing complexity of RANs presents significant challenges for network operators. Telecommunications nodes, such as RAN nodes, require frequent configuration changes to adapt to new services, update firmware, and optimize performance. These nodes can be configured in various ways to provide different levels of service to users, such as specific calling features or data service tiers. As new services are added and network demands evolve, the configuration of these nodes must be regularly updated.

[0023] In both new and conventional communication networks, a major challenge lies in effectively testing and troubleshooting to identify the causes of performance issues. Current techniques often struggle to accurately detect the root causes of RAN performance degradation. Moreover, monitoring telecommunications node connectivity for configuration changes and optimizing RAN performance typically requires substantial manual effort from telecom operators.

[0024] Conventional systems and methods face difficulty in efficiently managing the connectivity between network nodes and network management devices, leading to potential disruptions in service and suboptimal network performance. The manual nature of many existing monitoring and troubleshooting processes makes them time-consuming, error-prone, and inefficient. This is particularly problematic in the context of 5G networks, where rapid response toissues and continuous optimization are crucial for maintaining the promised high levels of service.

[0025] There is, therefore, a need in the art to provide a method and a system that can overcome the shortcomings of the existing prior arts. Specifically, there is a need for an automated, efficient system that can continuously monitor network node connectivity, quickly identify and address connectivity issues, and optimize the performance of radio access networks with minimal manual intervention.SUMMARY OF THE DISCLOSURE

[0026] In an exemplary embodiment, a system for monitoring connectivity between a network node and one or more network management devices is described. The system comprises a data fetching module configured to fetch details of one or more network management devices from a database, wherein said details comprise one or more of device identifiers, network addresses, authentication parameters, and operational status information. The system also includes connectivity monitoring module configured to send, at first predetermined intervals, a connectivity request to each of the network management devices based on the fetched details The connectivity monitoring module is further configured to determine a connectivity status for each of the network management devices based on responses to the connectivity requests. The system also includes a notification module configured to notify an operational unit to perform an action when at least one of the network management devices is determined to be not connected.

[0027] In some embodiments, the system further includes an authentication module configured to perform after the determination, at second predetermined intervals, authentication with the network management devices. The authentication module is configured to send an authentication request to each of the network management devices to perform the authentication. The notification module is further configured to notify an administrative authority to reset authentication credentials of the network management devices when authentication fails.

[0028] In some embodiments, the network node is a radio access network (RAN) node configured to wirelessly connect user equipment to a core network. The RAN node is capable of being configured through the network management devices, which comprise one or more Element Management Systems (EMS).

[0029] In some embodiments, the operational unit is a network operations center (NOC), and the administrative authority is responsible for the element management system (EMS) with access privileges for credential management.

[0030] In some embodiments, the notification module is configured to send one or more messages to notify the operational unit and the administrative authority.

[0031] In some embodiments, the system further includes a database configured to store the connectivity status of each of the network management devices. The connectivity status comprises "connection up" when connected and "connection down" when not connected.

[0032] In some embodiments, the connectivity monitoring module is configured to monitor, at configurable predetermined intervals or continuously, the connectivity between the network node and the network management devices to provide near real-time verification.

[0033] In some embodiments, the system is configured to enable a user to pre-plan for connectivity issues and authentication issues of the network management devices.

[0034] In another exemplary embodiment, a method for monitoring connectivity between a network node and one or more network management devices is described. The method comprises fetching, by a data fetching module,details of one or more network management devices from a database. The said details comprise one or more of device identifiers, network addresses, authentication parameters, and operational status information. The method also includes sending, by a connectivity monitoring module, at a first predetermined intervals, a connectivity request to each of the network management devices based on fetched details. The said connectivity request comprises a network probe configured to test responsiveness of the network management devices. The method further comprises determining, by the connectivity monitoring module, a connectivity status for each of the network management devices based on responses to the connectivity requests. Finally, the method includes notifying, by a notification module, to an operational unit to perform an action when at least one of the network management devices is determined to be not connected.

[0035] In some embodiments, the method further comprises performing, by an authentication module, at a second predetermined intervals, to an authentication with the network management devices. After the determination, the authentication module sends an authentication request to each of the network management devices to perform the authentication. The method also includes notifying, by the notification module, an administrative unit to reset authentication credentials of the network management devices when authentication fails.

[0036] In some embodiments, the network node is a radio access network (RAN) node configured to wirelessly connect user equipment to a core network. The RAN node is capable of being configured through the network management devices, which comprise one or more network element management systems (EMS).

[0037] In some embodiments, the operational unit is a network operations center (NOC), and the administrative unit is an element management system (EMS)with access privileges for credential management.

[0038] In some embodiments, the method further comprises sending, by the notification module, one or more messages to notify the operational unit and the administrative unit.

[0039] In some embodiments, the method further comprises storing the connectivity status of each of the network management devices in the database. The connectivity status comprises "connection up" when connected and "connection down" when not connected.

[0040] In some embodiments, the method further comprises monitoring, at configurable predetermined intervals or continuously, by the connectivity monitoring module , said connectivity between the network node and the one or more network management devices to provide near real-time verification.

[0041] In some embodiments, the method further comprises enabling a user to pre-plan for connectivity issues and authentication issues of the network management devices.

[0042] In yet another exemplary embodiment, a non-transitory computer- readable medium storing instructions for monitoring connectivity between a network node and one or more network management devices is described. When executed by one or more processors of a system, the instructions cause the processors to perform operations. These operations comprise fetching, by a data fetching module, details of one or more network management devices from a database. The details comprise one or more of device identifiers, network addresses, authentication parameters, and operational status information. The operations also include sending, by a connectivity monitoring module, at a first predetermined intervals, a connectivity request to each of the network management devices based on the fetched details. The connectivity request comprises a network probe configured to test responsiveness of the network management devices. The operations further comprise determining, by the connectivity monitoring module, aconnectivity status for each of the network management devices based on responses to the connectivity requests. Finally, the operations include notifying, by a notification module, an operational unit to perform an action when at least one of the network management devices is determined to be not connected.

[0043] In an additional exemplary embodiment, a user equipment communicatively coupled to a system for monitoring connectivity between a network node and one or more network management devices via a network is described. The system comprises a memory and one or more processors configured to execute a set of instructions stored in the memory. These instructions cause the processors to perform the method for managing connectivity as described in the method embodiment.

[0044] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.OBJECTS OF THE DISCLOSURE

[0045] Some of the objects of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.

[0046] An object of the present disclosure is to provide a system and a method for managing connectivity of a network node with a element management system (EMS) efficiently.

[0047] An object of the present disclosure is to provide a system and a method for rapidly identifying the important point of failure in the network and communicating an automatic alert to a concerned team.

[0048] An object of the present disclosure is to provide a system and a method that allows a user to pre-plan for any connectivity issue and authentication issue between the network node and the EMS.

[0049] An object of the present disclosure is to provide a system and a method for optimizing the performance of the Radio Access Network (RAN).

[0050] An object of the present disclosure is to provide a system and a method for continuously monitoring the connectivity between network nodes and network management devices.

[0051] An object of the present disclosure is to provide a system and a method for automatically determining the connectivity status of network management devices at predetermined intervals.

[0052] An object of the present disclosure is to provide a system and a method for notifying operational units promptly when connectivity issues are detected.

[0053] An object of the present disclosure is to provide a system and a method for automated authentication checks with network management devices.

[0054] An object of the present disclosure is to provide a system and a method for notifying administrative units when authentication failures occur, enabling quick resolution of credential issues.

[0055] An object of the present disclosure is to provide a system and a method for maintaining an up-to-date database of connectivity statuses for network management devices.

[0056] An object of the present disclosure is to provide a system and a method for real-time verification of network connectivity, enhancing overall network reliability.

[0057] An object of the present disclosure is to provide a user equipment capable of interfacing with a system for managing network connectivity, extending the reach and utility of the connectivity management system.BRIEF DESCRIPTION OF DRAWINGS

[0058] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the componentsusing 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 the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0059] FIG. 1 illustrates an exemplary network architecture of a system for managing connectivity between a network node and one or more network management devices, in accordance with embodiments of the present disclosure.

[0060] FIG. 2 illustrates an exemplary block diagram of a system, in accordance with embodiments of the present disclosure.

[0061] FIG. 3 illustrates an exemplary flow diagram of a method for managing connectivity between a network node and one or more network management devices, in accordance with embodiments of the present disclosure.

[0062] FIG. 4 illustrates an exemplary micro service-based architecture of a system, in accordance with embodiments of the present disclosure.

[0063] FIG. 5 illustrates an exemplary flowchart of a method, in accordance with embodiments of the present disclosure.

[0064] FIG. 6 illustrates an exemplary computer system in which or with which embodiments of the present disclosure may be implemented.

[0065] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102 - System104- Network106 - Centralized server108-1, 108-2... 108-N - User equipment(s)110-1, 110-2...110-N - Users202 - One or more processor(s)204- Memory206 - I / O interface(s)208 - Processing module(s)210, 410 - Database212- Data fetching module214- Connectivity monitoring module216- Notification module218- Authentication module220-Other module(s)300- Flow diagram400- Block diagram402 - Element Management System404 - A plurality of Services500-Flowchart610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port670- ProcessorDETAILED DESCRIPTION OF THE DISCLOSURE

[0066] 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 all 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.

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

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

[0069] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations 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.

[0070] 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, anyaspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.

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

[0072] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly 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 and all combinations of one or more of the associated listed items.

[0073] The aspects of the present disclosure are directed to a system and method for managing connectivity between network nodes and networkmanagement devices in a telecommunications network, particularly in radio access networks (RANs). The invention provides an automated solution for continuously monitoring connectivity, rapidly identifying points of failure, and promptly notifying appropriate operational units. The advantages of the current invention include real-time verification of network connectivity, automated authentication checks, and the ability to pre-plan for connectivity and authentication issues. The system aims to optimize RAN performance, reduce manual intervention, and enhance overall network reliability, thereby addressing the growing complexities in modern wireless communication networks, especially in the context of 5G technology deployment.

[0074] The various embodiments throughout the disclosure will be explained in more detail with reference to FIGS. 1-6.

[0075] As illustrated in FIG. 1, one or more user equipments (108-1, 108- 2...108-N) may be connected to a system (102) for managing connectivity between a network node and one or more network management devices through a network (104). A person of ordinary skill in the art will understand that the one or more user equipments (108-1, 108-2...108-N) may be collectively referred to as user equipments (108) and individually referred to as a user equipment (108).

[0076] In an embodiment, the user equipment (108) may include, but not be limited to, a mobile phone, a tablet, etc. Furthermore, the user equipment (108) may include a smartphone, virtual reality (VR) devices, augmented reality (AR) devices, a general-purpose computer, a desktop, a personal digital assistant, and a laptop computer.

[0077] In an embodiment, the network (104) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals,waves, voltage or current levels, some combination thereof, or so forth. The network (104) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a 2G network, a 3G network, a 4G network, a 5G network, a 6G network, or some combination thereof. The system (102) may be connected to backend servers such as centralized server (106).

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

[0079] FIG. 2 illustrates an exemplary micro service-based architecture of a proposed system (102) for managing connectivity between a network node and one or more network management devices, in accordance with an embodiment of the present disclosure.

[0080] Referring to FIG. 2, in an embodiment, the system (102) 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 (102). 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 manage connectivity and monitornetwork management devices. The memory (204) may comprise any non-transitory storage device including, for example, volatile memory such as random-access memory (RAM), or non-volatile memory such as erasable programmable read only memory (EPROM), flash memory, and the like.

[0081] In an embodiment, the system (102) may include an interface(s) (206). The interface(s) (206) may comprise a variety of interfaces, for example, interfaces for data input and output devices (I / O), storage devices, and the like. The interface(s) (206) may facilitate communication through the system (102). The interface(s) (206) may also provide a communication pathway for one or more components of the system (102). Examples of such components include, but are not limited to, processing module(s) (208), and a database (210) for storing connectivity status data. Further, the processing module(s) (208) may include a data fetching module (212), a connectivity monitoring module (214), a notification module (216), an authentication module (218), and other modules (220).

[0082] The other module(s) (220) may encompass various additional functionalities that support the overall operation of the system (102) for managing connectivity. These may include, but are not limited to, a security module for data encryption, a data compression module, a reporting module for generating performance reports, and a network analysis module. These modules work in concert with the primary modules to enhance the robustness, efficiency, and reliability of the connectivity management system.

[0083] The data fetching module (212) may fetch details of one or more network management devices from the database (210). The connectivity monitoring module (214) may send connectivity requests at predetermined intervals and determine the connectivity status. The notification module (216) may notify operational units when connectivity issues are detected. The authentication module (218) may attempt to authenticate with the network management devices and notify administrative units of authentication failures.

[0084] In an embodiment, the processing module(s) (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing module(s) (208). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing module(s) (208) may be processorexecutable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing module(s) (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 module(s) (208). In such examples, the system 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 module(s) (208) may be implemented by electronic circuitry.

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

[0086] The system (102) for managing connectivity between a network node and one or more network management devices may comprise a memory (204) and one or more processors (202) coupled to the memory (204). The processors (202) may be configured to execute a set of instructions stored in the memory (204) to perform various operations related to connectivity management.

[0087] In the context of this disclosure, a 'network management device' refers to any device or system used to monitor, configure, and maintain network nodes..

[0088] In some implementations, the system (102) may include a data fetching module (212) that may retrieve details of one or more network management devices from a database (210). These details may include information necessary for establishing and monitoring connections with the network management devices, such as IP / network addresses, port numbers, protocol specifications, device identifiers, authentication parameters, and operational status information.

[0089] The data fetching module (212) may employ various data retrieval techniques to obtain information about the network management devices from the database (210). The various data retrieval techniques may involve database queries for relational databases, API calls for web-based databases, or custom protocols for proprietary data storage systems. The data fetching module (212) may be configured to handle large volumes of data efficiently, possibly employing caching mechanisms to reduce database load and improve response times.

[0090] For example, the data fetching module (212) might retrieve information such as: a. Device identifiers (e.g., unique IDs, IP addresses) b. Device types (e.g., routers, switches, base stations) c. Geographical locations d. Software versions e. Last known status f. Historical performance metrics

[0091] The system (102) may also comprise a connectivity monitoring module (214) that may send connectivity requests to each of the network management devices at a first predetermined intervals. These intervals may be configurable and may be set based on network requirements and operational considerations. For example, the system may be configured to send connectivity requests every 5 minutes. The connectivity requests may serve as a means to verify the accessibility and responsiveness of the network management devices.

[0092] The connectivity monitoring module (214) may implement algorithms to determine the optimal intervals for sending connectivity requests. These algorithms might take into account factors such as network load, time of day, historical performance data, and criticality of the device. For instance, a critical core network component might be checked more frequently than a peripheral device. Examples of the algorithms may include:

[0093] Adaptive Sampling algorithm dynamically adjusts the sampling rate based on the device's recent performance. If a device has been stable for an extended period, the algorithm may reduce the frequency of checks. Conversely, if a device has shown recent instability, the check frequency may be increased. For example, a router that has been operating normally might be checked every 15 minutes, but if it starts showing intermittent connectivity issues, the checks might increase to every 5 minutes.

[0094] Time-of-Day Based algorithm varies the check frequency based on historical network usage patterns. During peak hours when network load is high, and any issues could have a more significant impact, checks might be more frequent. For instance, a corporate network might increase check frequencies to every 2 minutes during business hours (9 AM to 5 PM) but reduce them to every 10 minutes during off-hours.

[0095] Criticality-Weighted approach assigns a criticality score to each device and adjusts the check frequency accordingly. A core router might have a high criticality score of 9 out of 10 and be checked every minute, while an auxiliary switch with a criticality score of 3 might only be checked every 10 minutes.

[0096] Machine Learning-Based Prediction Algorithm uses historical data to predict when a device is most likely to experience issues and adjusts check frequencies accordingly. For example, if data shows that a particular server often experiences high load every Monday at 9 AM due to weekly batch processes, the algorithm might increase check frequency to every 30 seconds during this period.

[0097] These algorithms allow the connectivity monitoring module to optimize its operation, ensuring critical devices and potential problem areas are monitored more closely while minimizing unnecessary network overhead from excessive checking of stable, non-critical devices.

[0098] The connectivity monitoring module (214) employs a sophisticated process to determine the connectivity status of each network management device based on responses to said connectivity requests. The process may involve multiple steps and protocols to ensure accurate status determination. Initially, the module sends a series of Internet Control Message Protocol (ICMP) echo requests (pings) to the IP address of each network management device. These pings are configured with a timeout of 500 milliseconds to balance responsiveness with network latency considerations. The ICMP is a network layer protocol used by network devices to diagnose network communication issues. It is primarily used to determine whether a particular host is reachable across an Internet Protocol (IP) network and the time it takes for packets to travel to and from that host. In this context, ICMP echo requests serve as a fundamental tool for quickly assessing the basic connectivity of network management devices.

[0099] If no response is received from the ICMP echo requests, the module then attempts to establish a TCP connection to a predefined port on the device. This port is typically configured during the initial setup of the network management device and is stored in the database (210) along with device details. The TCP connection attempt provides an additional layer of verification, as some devices may have ICMP responses disabled for security reasons.

[0100] Should both the ICMP and TCP methods fail, the connectivity monitoring module (214) proceeds to send an application-specific health check request. This request is tailored to the particular type of network management device being monitored. For instance, for an EMS, this might involve a simple HTTP GET request to a known endpoint that returns the device's status.

[0101] A network management device is considered 'connected' if it responds successfully to any of these three types of requests within the specified timeframes. The module maintains a connection status log for each device, recording the type of successful connection (Internet Control Message Protocol (ICMP), Transmission Control Protocol (TCP), or application- specific) and the response time. The ICMP is used for diagnostic and control purposes in IP networks, while TCP is one of the main protocols in the Internet Protocol Suite, providing reliable, ordered, and error-checked delivery of data between applications running on hosts communicating over an IP network. The applicationspecific checks are tailored to the particular software or service running on the network management device. This comprehensive approach ensures that the connectivity status is determined using multiple protocols, increasing the accuracy of the assessment and providing a more complete picture of the device's accessibility and functionality within the network.

[0102] If all three methods fail in three consecutive attempts, with each attempt spaced 60 seconds apart to account for temporary network issues, the deviceis marked as 'not connected'. This multi-attempt approach helps differentiate between momentary network glitches and genuine connectivity problems.

[0103] The entire process is repeated at regular intervals for each network management device. The default interval is set to 5 minutes, striking a balance between timely status updates and network overhead. However, for critical infrastructure components, this frequency is increased to every 1 minute to ensure rapid detection of any connectivity issues.

[0104] The connectivity monitoring module (214) also implements an adaptive monitoring frequency algorithm. This algorithm adjusts the monitoring frequency based on factors such as the device's historical stability, its criticality to network operations, and current network conditions. For example, if a particular EMS has shown frequent connectivity fluctuations, the module may automatically increase the monitoring frequency for that device.

[0105] All connectivity status determinations, including successful connections and failures, are logged in the database (210) with timestamps. This historical data is valuable for trend analysis, allowing network administrators to identify patterns in connectivity issues and make informed decisions about network management and infrastructure improvements.

[0106] The connectivity requests sent by the module (214) could take various forms depending on the network protocols in use. This might include: a. ICMP echo requests (ping) b. TCP connection attempts c. Application-layer health checks (e.g., HTTP GET requests) d. Simple Network Management Protocol (SNMP) queries

[0107] Based on the responses received to these connectivity requests, the connectivity monitoring module (214) may determine a connectivity status for eachof the network management devices. This status information may be used for maintaining an up-to-date view of the network's health and functionality. The connectivity status may be categorized as "connection up" when a device is responsive and "connection down" when it fails to respond.

[0108] The connectivity monitoring module (214) sends connectivity requests at predetermined intervals to each of the network management devices. These intervals are configurable and can be adjusted based on the network's requirements and operational needs. The predetermined intervals typically range from as short as one minute for critical infrastructure components to as long as sixty minutes for less essential devices. For instance, a core network router might be checked every minute to ensure rapid detection of any issues, while a less critical edge device might be checked every fifteen minutes. The system allows network administrators to fine-tune these intervals based on the importance of each device and the overall network performance requirements.

[0109] The connectivity request sent by the module (214) includes several key parameters to ensure comprehensive monitoring. Each request contains the source IP address, which identifies the network node or platform initiating the check. It also includes the destination IP address of the specific network management device being monitored. The request type is another crucial parameter, which could be an ICMP echo request (commonly known as a ping), a TCP connection attempt, or an application-specific health check, depending on the nature of the device and the depth of monitoring required. To facilitate accurate tracking and analysis, each request is timestamped with the exact time it is sent and assigned a unique sequence number. This sequence number helps in detecting packet loss and maintaining the integrity of the monitoring process. Finally, the request includes a timeout value, typically set between 100 and 1000 milliseconds, which specifies the maximum time the system will wait for a response before considering the attempt failed. These parameters collectively enable the system toconduct thorough and efficient connectivity checks, providing a comprehensive view of the network's health and performance.

[0110] The system (102) may maintain a detailed log of all connectivity checks, including timestamps, response times, and any error messages received. This data may be valuable for network performance analysis and capacity planning.

[0111] In scenarios where the connectivity monitoring module (214) determines that at least one of the network management devices is not connected, the notification module (216) may alert an operational unit to investigate and address the connectivity issue. This proactive approach may help in minimizing network downtime and ensuring smooth operations. The operational unit may be a Network Operations Center (NOC), which is a centralized location where IT teams can continuously monitor the performance and health of a network.

[0112] The connectivity status can take several values, primarily categorized as "Connected," "Disconnected," or "Degraded." A status of "Connected" indicates that the device is fully accessible and responding within expected parameters. "Disconnected" signifies that the device is completely unreachable or not responding to any requests. The "Degraded" status represents a state where the device is partially responsive but experiencing issues, such as high latency or intermittent connectivity.

[0113] In cases where the initial request fails, the system may perform multiple retries before finalizing the connectivity status. The number of failed attempts, along with any partial responses or error codes received, are also considered part of the response data used to determine the final connectivity status.

[0114] The system employs two sets of predetermined intervals: one for connectivity checks and another for authentication attempts. The first set of predetermined intervals, used by the connectivity monitoring module (214), isprimarily focused on checking the network devices' reachability and basic functionality. The second set of predetermined intervals, utilized by the authentication and compliance module (218), is specifically for verifying the validity of authentication credentials, ensuring secure access to the network management devices, and confirming policy compliance status. These second predetermined intervals may be longer than the connectivity check intervals, as authentication and policy compliance checks are typically less frequent but more resource intensive. The policy compliance checks verify that network management devices adhere to established security protocols, configuration standards, and operational guidelines, enabling proactive identification of potential security vulnerabilities and compliance issues.

[0115] The system distinguishes between two types of notification recipients: the operational unit and the administrative unit. The operational unit, such as a Network Operations Center (NOC), is responsible for addressing day-to- day connectivity issues and ensuring the network's smooth operation. In contrast, the administrative unit, which might be an IT security team or a higher-level network management group, has more specialized responsibilities related to security and access control. This unit is notified specifically for authentication- related issues, such as failed login attempts or expired credentials. The administrative unit has higher-level access privileges that allow them to reset authentication credentials, modify security policies, and manage overall network access controls. This separation of duties ensures that security-related tasks are handled by personnel with the appropriate expertise and authorization levels, maintaining a strong security posture for the network infrastructure.

[0116] The system (102) may further include an authentication module (218) that may attempt to authenticate with the network management devices at a second predetermined intervals. This authentication process may involve sending login requests to each of the network management devices. Regular authentication attempts may help in identifying potential security issues or expired credentialsproactively. For instance, the system may attempt authentication every 5 minutes, similar to the connectivity checks.

[0117] In cases where authentication fails, the notification module (216) may alert an administrative unit to reset the authentication credentials of the affected network management devices. This prompt notification may enable quick resolution of authentication issues, thereby maintaining secure and uninterrupted access to the network management devices. The administrative unit may be an Element Management System (EMS) Network Operations Center (NOC) head, responsible for overseeing the management of network elements.

[0118] The system differentiates between two key units responsible for maintaining network health and security: the operational unit and the administrative unit. The operational unit, typically embodied as a Network Operations Center (NOC), serves as the frontline team for monitoring and managing the day-to-day functioning of the network infrastructure. This unit is staffed by network technicians and engineers who are responsible for tasks such as monitoring network performance, responding to alerts, troubleshooting connectivity issues, and coordinating with field teams for hardware-related problems. For instance, if a network management device becomes unresponsive, the NOC team would be the first to receive the alert and initiate the troubleshooting process. They might perform initial diagnostics, attempt remote restarts, or dispatch on-site technicians if necessary.

[0119] The administrative unit, on the other hand, is represented by higher- level management within the network operations structure, such as the Element Management System (EMS) Network Operations Center (NOC) head. This role encompasses broader responsibilities and higher-level access privileges. The EMS NOC head, for example, would be responsible for overseeing the entire network management system, making strategic decisions about network configurations, and managing security policies. In the context of authentication issues, the EMS NOChead might be called upon to reset high-level access credentials, approve changes to authentication protocols, or make decisions about upgrading security measures across the network. For instance, if multiple network devices experience simultaneous authentication failures, the EMS NOC head might be notified to investigate potential system-wide security breaches or to implement a network- wide password reset policy. This role might also be involved in capacity planning, approving major network changes, and liaising with vendor management for significant upgrades or troubleshooting of the element management system itself.

[0120] The notification module (216) may incorporate advanced filtering and prioritization mechanisms to ensure that alerts are actionable and relevant. For example, it might suppress notifications for transient issues that self-resolve quickly, or aggregate multiple related alerts into a single notification to prevent alert fatigue among operations staff.

[0121] The notification module (216) may support multiple notification channels beyond email, such as: a. SMS text messages b. Push notifications to mobile apps c. Integration with incident management platforms (e.g., PagerDuty, ServiceNow) d. Automated voice calls for critical issues

[0122] The network node in this system may be a radio access network (RAN) node that may be configured to wirelessly connect user equipment (108) to a core network. In this disclosure, the term 'network node' refers to any node in a telecommunications network. A 'RAN node' is a specific type of network node that is part of the Radio Access Network. In the context of this invention, the terms 'network node' and 'RAN node' may be used interchangeably, as the focus is on nodes within the Radio Access Network. The RAN, in the context of mobile telecommunications, is the part of a mobile telecommunication system thatimplements a radio access technology. It resides between user equipment, such as a mobile phone, a computer, or any remotely controlled machine, and provides the connection with its core network.

[0123] The notification module (216) may be configured to send automated emails to notify both the operational unit and the administrative unit about relevant issues. These emails may contain detailed information about the nature of the connectivity or authentication issue, the affected devices, and the time of occurrence. This automated communication may ensure timely dissemination of critical information to the appropriate personnel.

[0124] The system (102) may also be designed to store the connectivity status of each network management device in the database (210). This persistent storage of connectivity information may facilitate historical analysis and trend identification. For example, network administrators may use this data to identify patterns of connectivity issues, such as recurring problems at specific times or with particular devices.

[0125] To provide real-time verification of network health, the connectivity monitoring module (214) may continuously monitor the connectivity between the network node and the network management devices. This constant vigilance may allow for immediate detection and response to any connectivity issues that may arise, potentially reducing network downtime and improving overall service quality.

[0126] By maintaining a consistent and up-to-date view of the network's connectivity status, the system (102) may facilitate more efficient network management and troubleshooting. The real-time monitoring and automated notifications may reduce response times to connectivity issues, potentiallyminimizing network downtime and improving the overall user experience for those relying on the network.

[0127] The authentication mechanism implemented by the system (102) may enhance the security of the network by regularly verifying the credentials of the network management devices. This may help in preventing unauthorized access and may ensure that only authenticated devices can interact with the network node. In the context of 5G networks, where security is paramount due to the increased number of connected devices and the sensitivity of transmitted data, this feature becomes particularly crucial.

[0128] The authentication module (218) may support a variety of authentication protocols to accommodate different types of network management devices. The authentication protocols may include: a. Username / password authentication b. Certificate-based authentication c. Two-factor authentication d. OAuth for API access

[0129] The authentication module (218) may also implement advanced security features such as: a. Automatic lockout after multiple failed attempts b. Password complexity enforcement c. Regular password rotation d. Audit logging of all authentication attempts

[0130] The system's ability to store historical connectivity data may prove valuable for long-term network analysis and optimization. By analyzing patterns in connectivity status over time, network administrators may identify recurring issues or trends that require attention. This data-driven approach may lead to more informed decision-making in network management and infrastructure planning.

[0131] The automated email notifications sent by the system (102) may streamline communication between different units involved in network management. This may lead to improved coordination and faster resolution of both connectivity and authentication issues. In large-scale network operations, where multiple teams may be involved in maintaining different aspects of the network, this automated communication can significantly reduce response times and improve overall efficiency.

[0132] By enabling users to pre-plan for potential issues, the system (102) may foster a proactive approach to network management. This may result in more robust network configurations and better preparedness for handling unexpected connectivity or authentication problems. For example, network administrators might use this feature to schedule maintenance windows during periods of historically low network activity, minimizing potential disruptions.

[0133] In the context of 5G networks, which are characterized by high data rates, reduced latency, and massive network capacity, the importance of efficient connectivity management becomes even more pronounced. The system (102) may be particularly beneficial in managing the increased complexity of 5G network architectures, which often involve a larger number of small cells and network slicing.

[0134] The system (102) may also play a crucial role in ensuring the quality of service (QoS) in modern networks. By promptly identifying and addressing connectivity issues, it may help maintain the high standards of performance required for applications such as autonomous vehicles, remote surgery, or industrial loT, which rely on consistent and reliable network connections.

[0135] The system (102) may offer a comprehensive solution for managing connectivity between a network node and multiple network management devices.Through its various features including real-time monitoring, automated notifications, authentication checks, and data storage, the system may contribute to more efficient, secure, and reliable network operations, particularly in the context of advanced mobile networks like 5G.

[0136] In the context of a radio access network (RAN), the system (102) may play a crucial role in maintaining the performance and reliability of the wireless network. For instance, in a 5G network, the RAN consists of a complex array of macro cells, small cells, and distributed antenna systems. The system (102) may help manage the connectivity of these various elements, ensuring seamless handovers and optimal network performance. Specifically, the system (102) monitors and manages: a. The connectivity between RAN elements (such as macro cells and small cells) and the core network, ensuring that data can flow efficiently between the radio access and core parts of the network. b. The connectivity among different RAN elements, facilitating coordination for functions like coordinated multipoint transmission and reception (CoMP) in 5G networks. c. The connectivity between RAN elements and user equipment, helping to maintain stable connections as users move between different cells.

[0137] By managing these multiple layers of connectivity, the system (102) helps to ensure that the complex ecosystem of a modern RAN functions as a cohesive whole, providing users with a seamless and high-performance wireless experience.

[0138] The EMS may be responsible for tasks such as: a. Radio resource management b. Mobility management c. Quality of Service (QoS) managementd. Inter-cell interference coordination

[0139] The system (102) may interface with these EMS's to ensure they remain connected and functional, which is critical for maintaining the overall health of the network.

[0140] The database (210) used by the system may be designed to handle the specific requirements of network management data. This could involve timeseries data storage for performance metrics, which allows the system to track how network performance changes over time. For example, it might store data points for metrics like CPU utilization, memory usage, or network throughput at regular intervals, allowing for historical analysis and trend identification. The database might also employ graph structures to represent network topology, enabling efficient storage and querying of complex network relationships. For instance, it could model how different network devices are connected, making it easier to analyze the impact of a single device failure on the broader network. Additionally, the system might utilize distributed databases to ensure high availability and fault tolerance. This approach spreads data across multiple servers, ensuring that the system remains operational even if one server fails.

[0141] The system (102) may implement data retention policies to manage the growth of historical data while ensuring that sufficient information is available for long-term trend analysis. Data retention policies define how long different types of data are kept in the system before being archived or deleted. For example, high- resolution performance data (such as per-minute network utilization statistics) might be retained for 30 days, while daily summaries are kept for a year, and monthly aggregates are stored indefinitely. Historical data in this context refers to past records of network performance, configuration changes, and incident reports. This could include logs of past connectivity issues, records of network upgrades, or archives of performance metrics. By carefully managing this historical data, thesystem can provide valuable insights for capacity planning and long-term network optimization while controlling storage costs and system performance.

[0142] The continuous monitoring capability of the connectivity monitoring module (214) extends beyond simple connectivity checks to provide a comprehensive view of network health and performance. In addition to verifying basic reachability, the module tracks a range of performance metrics that offer deeper insights into network behavior. These include latency, which measures the time it takes for data to travel from source to destination, helping identify potential bottlenecks or routing issues. Packet loss is another crucial metric, indicating the percentage of data packets that fail to reach their destination, which can significantly impact application performance. The module also monitors throughput, measuring the actual amount of data successfully transferred over a given time period, which is essential for assessing whether the network is meeting bandwidth requirements. Additionally, it tracks error rates, such as CRC (Cyclic Redundancy Check) errors or frame errors, which can indicate physical layer issues or interference in wireless networks. By continuously monitoring these metrics, the module can detect subtle degradations in network performance before they escalate into full connectivity failures, enabling proactive network management and optimization.

[0143] The performance metrics may be analyzed in real-time to detect anomalies that could indicate impending failures or performance degradation.

[0144] The pre-planning functionality for connectivity and authentication issues may include features such as: a. Simulation tools to model the impact of device failures b. Automated failover testing c. Scheduled maintenance windows with automated device updates d. Capacity planning tools to predict future network requirements31

[0145] The system (102) may integrate with artificial intelligence and machine learning algorithms to enhance its capabilities. This could include: a. Predictive maintenance to anticipate device failures before they occur b. Automatic optimization of network parameters based on usage patterns c. Anomaly detection to identify security threats or unusual network behavior

[0146] The system (102) may also offer functionality to enable users to preplan for potential connectivity and authentication issues related to the network management devices. The pre-planning may allow network administrators to develop contingency plans and implement pre-emptive measures to minimize disruptions. For instance, they might set up backup communication channels or prepare automated scripts to handle common issues.

[0147] In an exemplary embodiment, a non-transitory computer-readable medium storing instructions for managing connectivity between a network node and network management devices via a network (104) is described. When executed by processors (202) of a system (102), the instructions perform several operations. First, a data fetching module (212) retrieves details of network management devices from a database (210). Next, a connectivity monitoring module (214) sends connectivity requests to each network management device at predetermined intervals based on the fetched details. The module (214) then determines the connectivity status of each device based on the responses received. If at least one of said one or more network management devices is found to be disconnected, a notification module (216) alerts an operational unit to investigate the connectivity issue. This claimed invention provides an automated, systematic approach to monitoring and managing network connectivity, enabling quick detection and response to potential network management device failures or connectivity problems.

[0148] FIG. 3 illustrates a flow diagram (300) of a method for monitoring the connectivity between Radio Access Network (RAN) nodes and network management devices, specifically Element Management Systems (EMS). A RAN node refers to a component of the wireless network infrastructure, such as a base station or small cell, that directly communicates with user devices. An EMS is a specialized network management device responsible for configuring, monitoring, and optimizing RAN nodes. This method is implemented by the system (102), which functions as a centralized connectivity monitoring platform, orchestrating the interactions between these network elements through its various modules including the data fetching module (212), connectivity monitoring module (214), and notification module (216).

[0149] At step 302, the system (102) fetches details of the EMS's available in the network. This step is executed by the data fetching module (212) of the system (102). The fetched details include, but are not limited to, the IP addresses of the EMS's (e.g., 192.168.1.100), their unique identifiers (e.g., EMS_001), current status (e.g., active, inactive, or maintenance mode), and relevant configuration parameters (e.g., software version, supported protocols). For example, a typical EMS entry might contain: {ID: EMS_001, IP: 192.168.1.100, Status: Active, Software_Version: 5.2.1 }. This information is retrieved from the database (210) and forms the basis for subsequent connectivity checks.

[0150] At step 304, the system (102) checks the connectivity between RAN nodes and EMS's. The connectivity monitoring module (214) performs this step by sending a ping request to each EMS. A ping request, or ICMP Echo Request, is a network utility that tests the reachability of a host on an IP network and measures the round-trip time for messages sent to the host. These ping requests serve as a simple yet effective means of verifying basic network connectivity. They help identify any EMS's that are unreachable due to network issues or device failures. For instance, if EMS_001 doesn't respond to a ping, it may indicate a networkoutage or device malfunction. The system (102) is configured to send these ping requests at regular intervals, typically every 5 minutes, to maintain an up-to-date view of the network's status.

[0151] In addition to the ping request, the connectivity monitoring module (214) sends a login request to each EMS to verify the authentication mechanisms. A login request involves attempting to establish a secure session with the EMS using predefined credentials. This step goes beyond basic network connectivity checks to identify issues related to expired credentials, misconfigured authentication services, or other access-related problems that might not be apparent from a simple ping test. For example, if the system can ping EMS_001 but fails to log in, it might indicate an authentication issue such as an expired password or a change in access policies.

[0152] At step 306, if the system (102) fails to receive a response from one or more EMS's, the notification module (216) sends an email to the Network Operations Center (NOC). The NOC is a centralized location where IT teams continuously monitor the performance and health of a network. This email updates the NOC about the connectivity status of the non-responsive EMS's. The notification includes detailed information such as the IP addresses of the unresponsive EMS's, the time of the last successful connection, and any error messages received. For instance, an alert might state: "EMS_001 (192.168.1.100) unresponsive since 2023-07-24 14:30:00 UTC. Last error message: Connection timed out. " This prompt notification enables the NOC team to quickly identify and address connectivity issues, minimizing potential disruptions to network operations.

[0153] At step 308, when the system (102) receives a response from an EMS, the connectivity monitoring module (214) updates the EMS's connectivity status in the database (210). The updated status includes information such as the time of the successful connection, the response time of the EMS, and any otherrelevant metrics gathered during the connectivity check. For example, a status update might include: {EMS_ID: EMS_001, Last_Connected: 2023-07-24 15:00:00 UTC, Response_Time: 50ms, Status: Connected}.

[0154] These steps collectively form a comprehensive method for monitoring and managing the connectivity between RAN nodes and EMS's. By regularly fetching EMS details, conducting both basic connectivity and authentication checks, promptly notifying relevant personnel of issues, and maintaining up-to-date status information, this method enables network operators to maintain high levels of network performance and quickly address any connectivity problems that may arise.

[0155] The system (102) executes this method at configurable predetermined intervals to ensure ongoing monitoring of the network's health, allowing network administrators to adjust the frequency of monitoring based on network requirements, criticality of devices, and available resources. This approach represents a proactive strategy for network management, allowing potential issues to be identified and addressed before they can significantly impact network performance or user experience. For instance, if the system detects that EMS_001 is consistently showing high response times during peak hours, network administrators can investigate and potentially upgrade the hardware or optimize the network configuration before users experience any service degradation.

[0156] [] FIG. 4 illustrates an exemplary block diagram (400) of a system(102) for monitoring the connectivity of a network node in accordance with an embodiment of the present disclosure. This block diagram (400) represents the system (102) that implements the method detailed in FIG. 3. The system architecture provides a comprehensive overview of the components involved in maintaining and monitoring network connectivity, including the functional modules that execute the various steps of the method such as fetching details,sending connectivity requests, determining connectivity status, and notifying operational units.

[0157] In an aspect, the block diagram (400) may include a plurality of Element Management systems (EMS) (402), such as EMS-1 (402-1), and EMS-2 (402-2). The EMS's (402) represent the network management devices for the operation and configuration of radio access network (RAN) nodes. Each EMSmay be responsible for managing a subset of the network's RAN nodes, handling tasks such as configuration management, performance monitoring, and fault management. The architecture also includes a plurality of services (404), such as service 1 (404-1), service 2 (404-2), and a database (210).

[0158] In an aspect, the plurality of services (404), such as service 1 (404- 1), service 2 (404-2), and the database (210) may collectively manage the EMS connectivity status. The collaborative approach ensures comprehensive monitoring and management of network connectivity. The database (210) may be implemented using various database management systems, such as relational databases, nonrelational databases, object-oriented databases, or any other suitable database system, depending on the specific requirements of the network environment. The selection of database type is based on factors such as data structure complexity, query patterns, scalability needs, and performance requirements for the particular network monitoring deployment.

[0159] In an aspect, the plurality of EMS (402) may be connected to the plurality of services (404), and the plurality of services (404) may be connected to the database (210). This interconnected structure allows for efficient data flow and real-time updates of connectivity status.

[0160] In the context of Figure 4, the system (102) is composed of multiple services (404) that work in concert to manage the connectivity between Radio Access Network (RAN) nodes and their corresponding EMS (402). While the RANnodes are not explicitly depicted in Figure 4, they are the network elements managed by the EMS's. The services (404) interact with both the EMS's (402) and the central database (210) to maintain an up-to-date view of the network's connectivity status.

[0161] One of the key components of this system is the connectivity monitoring service, which is responsible for conducting regular connectivity checks. This service operates on a predefined schedule, initiating connectivity requests at specified intervals. These intervals are configurable to suit the specific needs of the network, with a common setting being every five minutes. This frequency strikes a balance between timely detection of issues and minimizing network overhead.

[0162] The Connectivity Monitoring Service begins its process by querying the database (210) to retrieve a comprehensive list of all EMS's (402) present in the network. Armed with this information, the service then systematically sends a connectivity request to each EMS. These requests serve as probes to determine whether each EMS is accessible and functioning correctly.

[0163] Upon sending a request, the Connectivity Monitoring Service waits for a response from each EMS. The nature of this response, or the absence thereof, is used in determining a connection status. If an EMS responds within the expected timeframe, it is considered connected, and its status is logged as 'Connection up'. Conversely, if an EMS fails to respond or sends an error message, it is marked as 'Connection down'.

[0164] Following the completion of each round of checks, the Connectivity Monitoring Service updates the database (210) with the latest status information for each EMS. This update ensures that the database always contains the most current view of the network's connectivity state. The status information stored in the database serves as a valuable resource for other services within the system, as wellas for network administrators who need to monitor and manage the network's health.

[0165] By maintaining this systematic cycle of checking and updating at configurable predetermined intervals, the system enables swift detection of any connectivity issues between the RAN nodes and their managing Element Management Systems (EMS). The frequency of these intervals can be adjusted based on network criticality, with more frequent checks for mission-critical elements and less frequent checks for non-critical components, optimizing both detection speed and system resource utilization. This proactive approach allows network operators to identify and address potential problems before they escalate into more serious issues that could impact network performance or user experience. Moreover, the historical data accumulated in the database can be analyzed to identify patterns or recurring issues, facilitating long-term improvements in network reliability and performance.

[0166] When connectivity issues are detected by the Connectivity Monitoring Service, one of the services (404) within the system (102), it triggers the Notification Service. This Notification Service is responsible for transmitting an email to the operational unit, typically the Network Operations Center (NOC). The email contains detailed information about the connectivity problem, including the source IP of the system (102) itself and the destination IP of the affected EMS (402). This comprehensive notification allows the NOC team to swiftly identify and address the specific connectivity issue between the system and the EMS in question.

[0167] Following the connectivity check, an authentication service, another component within the services (404) of the system (102), performs an authentication check with each EMS (402). This process is similarto the connectivity check in its regularity but serves a different purpose. The authentication service sends login requests to each EMS (402) at predefined intervals, which can be configured separately from the connectivity check intervals.These login attempts verify that the system (102) can not only reach the EMS but also authenticate with it, ensuring full operational access.If the login is successful, the authentication service records this status in the database (210). However, if the login fails, the service marks it as a failed authentication attempt. In this case, the notification service is once again activated, this time to automatically send an email to the administrative authority responsible for the network element management system with access privileges for credential management. In an example, the email alerts the authentication management system to the authentication failure and triggers an automated credential resolution workflow. This workflow initiates necessary actions such as credential reset processes, security protocol verification, or escalation to appropriate authorization systems, depending on the configuration and severity of the authentication issue detected.

[0168] The comprehensive approach to connectivity and authentication management allows users to plan proactively for potential issues. By providing realtime status updates and automated notifications, the system enables network administrators to anticipate and address connectivity and authentication problems before they can significantly impact network performance.

[0169] The system (102) for managing connectivity between a network node and one or more network management devices may address challenges in high scale 4G and 5G radio access networks (RANs). These RANs typically include multiple telecommunications nodes, referred to as RAN nodes. To manage these nodes, the network may employ multiple element management systems (EMS).

[0170] A key challenge in RAN management is that the ability to read and change RAN node configurations depends on the connectivity between the network and the EMS. If this connectivity is lost, users may be unable to read or modify RAN node configurations. Additionally, issues such as expired EMS login credentials can prevent users from accessing the EMS (402).

[0171] To address these challenges, the system (102) may include a data fetching module (212) that retrieves details of the network management devices, such as EMS's (402), from a database (210). This information may be crucial for establishing and monitoring connections.

[0172] The system (102) may also comprise a connectivity monitoring module (214) that sends connectivity requests to each network management device at predetermined intervals. These intervals, which may be user-defined, could be set to every 'n' minute, with 5 minutes being a typical example. The connectivity request may take the form of a ping request or other suitable network probe.

[0173] Based on the responses to these requests, the connectivity monitoring module (214) may determine a connectivity status for each network management device. This status may be stored in the database (210), with "connection up" indicating an active connection and "connection down" signifying a lost or inactive connection.

[0174] When the connectivity monitoring module (214) detects that a network management device is not connected, a notification module (216) may alert an operational unit to investigate and address the issue. This operational unit may be a Network Operations Center (NOC), a centralized location for monitoring network health and performance.

[0175] The notification module (216) may send automated emails to the NOC, providing details such as the source IP of the network platform and the destination IP of the affected EMS (402). This allows for quick identification and resolution of connectivity issues.

[0176] In addition to connectivity checks, the system (102) may include an authentication module (218) that attempts to authenticate with the networkmanagement devices at regular intervals. This process may involve sending login requests to each EMS (402) every 'n' minutes, again with 5 minutes being a typical interval.

[0177] If authentication is successful, it may be logged as such. However, if authentication fails, the notification module (216) may alert an administrative unit, such as the EMSNOC head, to reset the authentication credentials. This proactive approach helps prevent prolonged access issues due to expired or invalid credentials.

[0178] The system (102) may allow users to pre-plan for potential connectivity and authentication issues. By providing a comprehensive view of network status and potential points of failure, network administrators can develop contingency plans and implement pre-emptive measures.

[0179] Through its continuous monitoring and automated notification features, the system (102) may provide a quick way to identify critical points of failure in the network. By promptly communicating automatic alerts to the relevant teams, the system helps maintain connectivity between the network node and the EMS (402), thereby optimizing overall network performance.

[0180] The network platform, which may be used for network planning and node configuration management, may leverage this system (102) to manage connectivity between network nodes and EMS's (402). It may perform the necessary steps to maintain and verify this connectivity in real-time.

[0181] By providing high reliability for network node configuration changes and read functionality, the system (102) addresses a critical need in modern telecommunications networks. It offers an efficient method for monitoring connectivity between network nodes and EMS's (402), thereby optimizing RAN performance.

[0182] The system (102) represents a comprehensive solution for managing connectivity in complex radio access networks. By automating connectivity checks, authentication attempts, and notifications, it enables network operators to maintain high levels of network performance and quickly address any issues that arise. This approach not only improves the reliability of network operations but also allows for more efficient use of network management resources.

[0183] The block diagram illustrated in FIG. 4 represents a robust and scalable solution for managing network connectivity. It provides a clear visualization of how different components interact to ensure continuous monitoring and management of EMSconnectivity, thereby contributing to the overall stability and performance of the radio access network.

[0184] FIG. 5 illustrates an exemplary flow diagram of a method (500) for monitoring connectivity between a network node and one or more network management devices, in accordance with embodiments of the present disclosure.

[0185] At step (502), the method (500) includes fetching, by a data fetching module (212), details of one or more network management devices from a database (210). The said details comprise device identifiers, network addresses, authentication parameters, and operational status information. Network management devices are specialized hardware or software systems used to monitor, configure, and maintain network infrastructure. This infrastructure includes a wide range of components such as routers, switches, firewalls, base stations, and data centers. For example, in a typical telecommunications network, the infrastructure might include: a. Core network routers that handle high-speed data transfer between different parts of the network b. Edge switches that connect end-user devices to the networkc. Cellular base stations that provide wireless connectivity to mobile devices d. Fiber optic transmission systems that form the backbone of the network e. Data centers that host critical network services and applications

[0186] To manage this complex infrastructure, various types of network management devices are employed. Examples include Element Management Systems (EMS), which provide a comprehensive suite of tools for managing network elements from multiple vendors. Other examples might include: a. Network Monitoring Systems (NMS) that provide real-time visibility into network performance b. Configuration Management Databases (CMDB) that maintain records of all network assets and their configurations c. Security Information and Event Management (SIEM) systems that monitor network security d. Software-Defined Networking (SDN) controllers that manage network flow control to improve network resource optimization

[0187] The database stores the details about these devices, such as their IP addresses, port numbers, authentication credentials, and device types. For instance, the database might contain entries like: "EMS-01, IP: 192.168.1.100, Port: 8080, Username: admin_EMS01, Type: Radio Network Manager" "EMS-Core-01, IP: 10.0.0.50, Port: 443, Username: ems_admin, Type: Core Network Manager" "NMS-01, IP: 172.16.0.25, Port: 161, Community String: public_ro, Type: Network Monitoring System".

[0188] At step (504), the method (500) includes sending, by a connectivity monitoring module (214), at a first predetermined intervals, a connectivity request to each of said one or more network management devices. A connectivity request is a network probe sent to verify if a device is reachable and is responsive on thenetwork. Common examples of the connectivity request include ICMP ping requests or TCP connection attempts. The first predetermined intervals could be configurable, such as every 5 minutes or every hour, depending on the network's requirements and resources. For example, the system might send a ping request to EMS-01 at 192.168.1.100 every 5 minutes. The said connectivity request comprises a network probe designed to test reachability and responsiveness of the network management devices.

[0189] At step (506), the method (500) includes determining, by said connectivity monitoring module (214), a connectivity status for each of said one or more network management devices based on responses to said connectivity requests. The connectivity status indicates whether the network management device is reachable and functioning normally on the network.

[0190] The concept of an "acceptable time frame" is crucial in this determination and is typically defined based on network characteristics and operational requirements. This time frame, often referred to as the Round-Trip Time (RTT) or latency, is the duration between sending a request and receiving a response. The acceptable RTT can vary depending on factors such as network topology, network technology, and device type and function. In a local area network, an RTT of less than 10ms might be expected, while for geographically distributed networks, an RTT of up to 100-200ms might be acceptable. Fiber optic networks generally have lower latencies compared to satellite networks, for example. Critical core network devices might have stricter RTT requirements compared to peripheral devices.

[0191] System administrators typically configure threshold to determine the connectivity based on network design and performance expectations. For example, the threshold might be set such that less than 50ms is considered excellent connectivity, 50ms to 100ms is good, 100ms to 200ms is fair, and over 200ms is poor.

[0192] Based on these criteria, the connectivity status could be categorized as "Connected," "Degraded," or "Disconnected." A "Connected" status is assigned if the device responds within the acceptable time frame. For instance, if EMS-01 responds to the ping within 100ms, its status would be set to "Connected." A "Degraded" status might be used if the device responds, but the response time is higher than ideal yet below the disconnection threshold. For example, if EMS-01 responds in 180ms, it might be marked as "Degraded." A "Disconnected" status is assigned if there's no response or if the response time exceeds the predefined threshold. For example, if EMS-01 doesn't respond within 500ms (assuming this is set as the disconnection threshold), its status would be set to "Disconnected."

[0193] The connectivity monitoring module might also consider factors such as packet loss or jitter in determining the overall connectivity status. For instance, if EMS-01 responds within 50ms but 20% of the packets are lost, it might still be categorized as "Degraded" despite the low latency. By employing these nuanced status categories and considering multiple factors, the connectivity monitoring module can provide a more accurate and useful representation of each network management device's connectivity state. This detailed information allows network operators to quickly identify and prioritize issues, ensuring optimal network performance.

[0194] At step (508), the method (500) includes notifying, by a notification module (216), to an operational unit to perform an action when at least one of said one or more network management devices is determined to be not connected. The operational unit refers to a team or department responsible for maintaining network operations, such as a Network Operations Center (NOC). The notification could be in the form of an automated email, SMS, or an alert in a network monitoring dashboard. For example, if EMS-01 fails to respond to three consecutive ping requests, an email might be sent to noc@company.com with the subject "Connectivity Alert: EMS-01 Unreachable".

[0195] The method (500) may include additional operations to enhance network management. An authentication module (218) attempts, at predetermined intervals, to authenticate with said one or more network management devices by sending a login request to each device. The authentication involves verifying the identity of the network node to ensure that it has the necessary permissions to access and manage the network management devices. This authentication process could involve sending encrypted credentials over secure protocols like Secure Shell (SSH) or Hypertext Transfer Protocol Secure (HTTPS). SSH is a cryptographic network protocol that provides a secure channel over an unsecured network, commonly used for remote command-line login and remote command execution. HTTPS, on the other hand, is an extension of the Hypertext Transfer Protocol (HTTP) used for secure communication over a computer network, widely used on the internet. Both protocols use encryption to protect the confidentiality and integrity of the data being transmitted.

[0196] For instance, every hour, the system might attempt to establish an SSH connection to EMS-01 using stored credentials. This regular authentication process ensures that the system maintains secure and authorized access to the network management devices. By using these secure protocols, the system protects sensitive information such as login credentials from potential interception or tampering during transmission across the network. This approach not only verifies the connectivity of the network management devices but also confirms that the proper security measures are in place and functioning correctly.

[0197] The notification module (216) also notifies an administrative unit to reset authentication credentials of said one or more network management devices when authentication fails. The administrative unit is typically a higher-level management team with the authority to modify critical system settings, such as an EMS Network Operations Center head. This notification ensures that potential security issues are addressed promptly. For example, if the SSH authentication toEMS-01 fails three times in a row, an urgent email might be sent to ems- admin@company.com requesting a credential reset.

[0198] The method (500) is particularly applicable to radio access network (RAN) nodes. A RAN node is a key component in wireless networks that connects user equipment (like smartphones) to the core network. Examples include base stations in cellular networks. These nodes often require frequent configuration updates and monitoring, which is facilitated by network management devices like EMSs.

[0199] To ensure efficient communication, the notification module (216) may leverage various channels for alerts. This could include integration with enterprise communication platforms (e.g., Slack, Microsoft Teams), ticketing systems (e.g., ServiceNow, Jira), or SMS gateways for urgent notifications.

[0200] The connectivity monitoring module (214) operates continuously, providing real-time verification of the network's state. This constant monitoring allows for immediate detection of issues, minimizing network downtime. For example, if EMS-01 becomes unreachable at 3:27 AM, the system would detect this within minutes, rather than waiting for the next scheduled check.

[0201] Furthermore, the method (500) enables proactive network management. By analyzing connectivity and authentication patterns over time, network administrators can identify recurring issues or potential vulnerabilities. For instance, if EMS-01 consistently becomes unreachable every day at 2:00 AM for 5 minutes, this might indicate a scheduled task causing temporary downtime, allowing administrators to adjust their maintenance windows accordingly.

[0202] In another exemplary embodiment, the user equipment (108) communicatively coupled to the system (102) is disclosed. The user equipment gains access to a more stable and reliable network environment. The system (102),comprising a memory (204) and one or more processors (202), executes a set of instructions that implement the connectivity management method (500).

[0203] The present disclosure provides technical advancement related to network management and monitoring. This advancement addresses the limitations of existing solutions by providing a comprehensive and automated method for managing connectivity between network nodes and their management devices. The disclosure involves continuous monitoring, authentication checks, and automated notifications, which offer significant improvements in network reliability and efficiency. By implementing real-time verification and proactive issue detection, the disclosed invention enhances network operations, resulting in reduced downtime and improved overall network performance. For example, in a large telecom network with hundreds of RAN nodes and dozens of EMSs, this system could reduce the average time to detect and respond to connectivity issues from hours to minutes, significantly improving network uptime and customer satisfaction.

[0204] FIG. 6 illustrates an exemplary computer system (600) in which or with which the embodiments of the present disclosure may be implemented.

[0205] As shown in FIG. 6, the computer system (600) may include an external storage device (610), a bus (620), a main memory (630), a read-only memory (640), a mass storage device (650), a communication port(s) (660), and a processor (670). A person skilled in the art will appreciate that the computer system (600) may include more than one processor and communication ports. The processor (670) may include various modules associated with embodiments of the present disclosure. The communication port(s) (660) 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 ports(s) (660) may be chosendepending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (600) connects.

[0206] In an embodiment, the main memory (630) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (640) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basic input / output system (BIOS) instructions for the processor (670). The mass storage device (650) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (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).

[0207] In an embodiment, the bus (620) may communicatively couple the processor(s) (670) with the other memory, storage, and communication blocks. The bus (620) may be, e.g. a Peripheral Component Interconnect PCI) / PCI Extended (PCLX) 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 (670) to the computer system (600).

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

[0209] 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 for illustration 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.

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

[0211] The present disclosure provides a system and method for managing connectivity of a network node with the EMS efficiently, thereby enhancing the overall stability and reliability of the network infrastructure. By implementing regular connectivity checks and automated notifications, the system ensures that any disruptions in connectivity are swiftly identified and addressed.

[0212] The present disclosure provides a quick way to identify the important point of failure in the network and communicate a respective automatic alert to a respective concerned team. This rapid identification and notification process significantly reduces the time required to diagnose and resolve network issues, minimizing downtime and improving overall network performance.

[0213] The present disclosure allows a user to pre-plan for any connectivity issue and authentication issue between the network node and the EMS. By providing comprehensive connectivity status information and historical data, the system enables network administrators to anticipate potential problems and develop proactive strategies to maintain network integrity.

[0214] The present disclosure optimizes the performance of the RAN by ensuring consistent connectivity between network nodes and management devices. This optimization leads to improved network efficiency, reduced latency, and enhanced quality of service for end-users.

[0215] The present disclosure introduces a modular and scalable architecture that can adapt to evolving network technologies and increasing complexity in telecommunications infrastructure. This flexibility ensures that the system remains effective and relevant as networks continue to grow and evolve.

[0216] The present disclosure implements an automated authentication check mechanism, which helps prevent unauthorized access to network resources and ensures that all connected devices are properly authenticated. This feature significantly enhances the security posture of the network.

[0217] The present disclosure facilitates improved coordination between different operational units involved in network management. By automatically routing notifications to the appropriate teams, the system ensures that issues are addressed by the most qualified personnel in a timely manner.

[0218] The present disclosure contributes to cost reduction in network management by automating many routine tasks and reducing the need for manual intervention. This automation allows network operators to manage larger and more complex networks with greater efficiency and fewer resources.

Claims

CLAIMS1. A system (102) for monitoring connectivity between a network node and one or more network management devices, said system (102) comprising: a data fetching module (212) configured to fetch details of one or more network management devices from a database (210); a connectivity monitoring module (214) configured to send, at first predetermined intervals, a connectivity request to each of said one or more network management devices based on the fetched details, and determine a connectivity status for each of said one or more network management devices based on responses to said connectivity requests; and a notification module (216) configured to notify an operational unit to perform an action when at least one of said one or more network management devices is determined to be not connected.

2. The system (102) as claimed in claim 1, wherein said details comprise one or more of device identifiers, network addresses, authentication parameters, and operational status information.

3. The system (102) as claimed in claim 1, wherein said connectivity request comprises a network probe configured to test responsiveness of the one or more network management devices.

4. The system (102) as claimed in claim 1 further comprises an authentication module (218), wherein the authentication module (218) configured to perform at a second predetermined intervals, after said determining, an authentication with said one or more network management devices, wherein said authentication module (218) is configured to send an authentication request to each of said one or more network management devices to perform the authentication; and said notification module (216) is configured to notify an administrative unit (220) to reset authentication credentials of said one or more network management devices when the authentication fails.

5. The system (102) as claimed in claim 1, wherein said network node is a radio access network (RAN) node configured to wirelessly connect user equipment to a core network, and wherein said RAN node is capable of being configured through said one or more network management devices, wherein said one or more network management devices comprise one or more element management systems (EMS).

6. The system (102) as claimed in claim 4, wherein said operational unit is a network operations center (NOC), and wherein said administrative unit is an element management system (EMS) with access privileges for credential management.

7. The system (102) as claimed in claim 4, wherein said notification module (216) is further configured to: send one or more messages to notify said operational unit and said administrative unit.

8. The system (102) as claimed in claim 1, wherein said database (210) is further configured to: store said connectivity status of each of said one or more network management devices, wherein said connectivity status comprises "connection up" when connected and "connection down" when not connected.

9. The system (102) as claimed in claim 1, wherein said connectivity monitoring module (214) is configured to monitor: continuously or at configurable predetermined intervals, said connectivity between the network node and the one or more network management devices to provide real-time verification.

10. A method (500) for monitoring connectivity between a network node and one or more network management devices, the method (500) comprising: fetching (502), by a data fetching module (212), details of one or more network management devices from a database (210); sending (504), by a connectivity monitoring module (214), at a first predetermined intervals, a connectivity request to each of said one or more network management devices based on the fetched details; determining (506), by said connectivity monitoring module (214), a connectivity status for each of said one or more network management devices based on responses to said connectivity requests; and notifying (508), by a notification module (216), to an operational unit to perform an action when at least one of said one or more network management devices is determined to be not connected.

11. The method (500) as claimed in claim 10, wherein said details comprise one or more of device identifiers, network addresses, authentication parameters, and operational status information.

12. The method (500) as claimed in claim 10, wherein said connectivity request comprises a network probe configured to test responsiveness of the one or more network management devices.

13. The method (500) as claimed in claim 10, further comprising: performing (510), by an authentication module (218), at a second predetermined intervals and after said determining, an authentication with said one or more network management devices, wherein said authentication module (218) sends an authentication request to each of said one or more network management devices to perform the authentication; andnotifying (512), by said notification module (216), an administrative unit (220) to reset authentication credentials of said one or more network management devices when authentication fails.

14. The method (500) as claimed in claim 10, wherein said network node is a radio access network (RAN) node configured to wirelessly connect user equipment to a core network, and wherein said RAN node is capable of being configured through said one or more network management devices, wherein said one or more network management devices comprise one or more element management systems (EMS).

15. The method (500) as claimed in claim 13, wherein said operational unit is a network operations center (NOC), and wherein said administrative unit (220) is an element management system (EMS) with access privileges for credential management.

16. The method (500) as claimed in claim 13, further comprising: sending, by said notification module (216), one or more messages to notify said operational unit and said administrative unit.

17. The method (500) as claimed in claim 10, further comprising: storing said connectivity status of each of said one or more network management devices in said database (210), wherein said connectivity status comprises "connection up" when connected and "connection down" when not connected.

18. The method (500) as claimed in claim 13, further comprising: monitoring, at configurable predetermined intervals or continuously, by said connectivity monitoring module (214), said connectivity between the network node and the one or more network management devices to provide near real-time verification.

19. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors (202) of a system (102) for monitoring connectivity between a network node and one or more network management devices via a network (104), cause the one or more processors (202) to perform operations comprising: fetching, by a data fetching module (212), details of one or more network management devices from a database (210); sending, by a connectivity monitoring module (214), at predetermined intervals, a connectivity request to each of said one or more network management devices based on the fetched details; determining, by said connectivity monitoring module (214), a connectivity status for each of said one or more network management devices based on responses to said connectivity requests; and notifying, by a notification module (216), to an operational unit to perform an action when at least one of said one or more network management devices is determined to be not connected.

Images