System and method for visualizing the performance of a network

Abstract

The present disclosure provides a method (1200) for visualizing the performance of a network (106) An input request is transmitted to a server (406) by an application on a user device (UE) (104). One or more parameters associated with the input request are extracted by the server (406). A data associated with the input request is fetched from the database (210) based on one or more extracted parameters by the server (406). The fetched data is further transmitted to the UE (104). A plurality of actions are performed by the user (102) related to the UE (104) at a geographical location based on the fetched data. The performance of the network (106) is dynamically visualized on the UE (104).

Description

SYSTEM AND METHOD FOR VISUALIZING THE PERFORMANCE OF A NETWORKRESERVATION OF RIGHTS

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

[0002] The present disclosure relates generally to the field of wireless communication networks. More particularly, the present disclosure relates to a system and method for visualizing the performance of a network. The present disclosure relates to a system and a method to determine underperforming cells in the network.DEFINITION

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

[0004] “Dashboard” refers to a mobile-friendly interface designed to display, track, and optimize underperforming cells in a network. The dashboard provides realtime data on site-specific performance metrics, user activities, and corrective actions taken by field engineers.

[0005] “Key Performance Indicator (KPI)” refers to a measurable value that indicates the performance of a network cell or site. Common KPIs include datathroughput, call drop rate, and session quality, which are used to evaluate network health and performance.

[0006] “Underperforming Cell” refers to a network cell that fails to meet predefined KPIs, such as data throughput, call quality, or traffic handling, leading to degraded user experience and requiring corrective actions.

[0007] “Mean Time to Repair (MTTR)” refers to the average time taken to identify and resolve an issue affecting a network cell. MTTR is a key metric in evaluating the efficiency of corrective actions taken by engineers.

[0008] “Action Owner” refers to an individual or team responsible for taking corrective actions on an underperforming cell. The actions are logged and tracked on a dashboard to ensure accountability and timely resolution.

[0009] “Health of Cell” refers to a measure of the operational status and performance efficiency of network cells, determined by KPIs and other performance metrics. A healthy cell meets all KPIs, while underperforming cells exhibit deteriorating performance.

[0010] “Field Engineer” refers to a network technician responsible for on-site troubleshooting and resolution of network performance issues. The field engineer uses the dashboard to log actions and provide evidence of corrective measures taken on underperforming cells.

[0011] “Ingestion of data” refers to a process by which raw network performance data from various cells is collected daily from the Network Performance Optimization (NPO) Server and transferred to the server for processing and visualization on the Dashboard.BACKGROUND

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

[0013] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog technology that offered only voice services. Further, when the second-generation (2G) technology was introduced, text messaging and data services became possible. The 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, improved network coverage, and security. Currently, the fifth generation (5G) technology is being deployed, with even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. While the 5G technology is still being rolled out globally, research and development into the Sixth Generation (6G) are rapidly progressing, with the aim of revolutionizing the way people connect and interact with the technology.

[0014] As wireless technologies are advancing, there is a need to maintain optimal performance across various network elements, ensuring high-quality service. Cellular network operators face challenges in monitoring the health of individual cells, particularly identifying underperforming cells and taking corrective action in real-time. Conventionally, tracking the health of these cells and monitoring user activity, action taken on sites, and site-specific details, such as area-wise performance, was limited. The conventional techniques often required manual tracking via desktop-based applications or emails, which provided delayed insights and lacked the capability to dynamically display health metrics for each area and track actions at the field level. The conventional systems for monitoring the performance of a network are generallyset up on trial and error, ignoring the fact that networks are dynamic and can constantly vary in speed, data traffic volume, signal strength, and so on. The conventional systems fail to provide an apparent / proactive solution to monitor or address the varying network performance. The conventional systems fail to provide a real-time dashboard solution that provides visualization of the tracking activity of the users (e.g., field engineers), actions taken by them on sites, and their details.

[0015] The lack of real-time data accessibility and the inability to track sitespecific details on mobile devices resulted in inefficiencies, delayed actions, and prolonged periods of cell underperformance, which directly impacted overall network performance. Further, conventional techniques fail to provide a comprehensive way to monitor the activity of field engineers and ensure that corrective measures are being effectively implemented on-site.

[0016] Thus, there is a need for a real-time solution to display, track, and optimize underperforming cells in the network that can be accessed by the user (field engineer) at anytime and anywhere.SUMMARY OF THE DISCLOSURE

[0017] In an exemplary embodiment, a method for visualizing a performance of a network is described. The method includes transmitting an input request to a server. The method further extracting one or more parameters associated with the input request. The method further includes fetching data associated with the input request from a database based on one or more extracted parameters. The method includes transmitting the fetched data to the UE. Further, the method includes performing a plurality of actions at a geographical location based on the fetched data. The method further includes dynamically visualizing the performance of the network on the UE.

[0018] In an embodiment, the method further comprising updating the database in a real-time based on the plurality of actions performed by the user.

[0019] In another embodiment, the one or more extracted parameters are associated with a user profile related to the user.

[0020] In another embodiment, the method further comprising deriving one or more key performance indicators (KPIs) associated with the performance of the network based on the plurality of actions performed by the user.

[0021] In another embodiment, the method further comprising visualizing a status of the plurality of actions performed by the user on the UE (104).

[0022] In another exemplary embodiment, a system for visualizing performance of a network is described. The system includes a memory, and one or more processors coupled to the memory and configured to execute a set of instructions stored therein to transmit an input request to a server. The processor execute a set of instructions stored therein to extract one or more parameters associated with the input request. Further, the processor execute a set of instructions stored therein to fetch data associated with the input request from a database based on one or more extracted parameters. The processor execute a set of instructions stored therein to transmit the fetched data to the UE. Further, the processor execute a set of instructions stored therein to perform a plurality of actions at a geographical location based on the fetched data. The processor execute a set of instructions stored therein to dynamically visualize the performance of the network on the UE.

[0023] In an exemplary embodiment, the present disclosure relates to a user equipment (UE) communicatively coupled with a network. The coupling includes steps of receiving, by the network, a connection request from the UE, sending, by the network, an acknowledgment of the connection request to the UE and transmitting a plurality of signals in response to the connection request. The performance of the network is visualized by a method that includes transmitting an input request to a server. The method further includes extracting one or more parameters associated with the input request. The method further includes fetching data associated with the inputrequest from a database based on one or more extracted parameters. The method further includes transmitting the fetched data to the UE. Further, the method further includes performing a plurality of actions at a geographical location based on the fetched data. The method further includes dynamically visualizing the performance of the network on the UE.

[0024] In yet another exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for visualizing the performance of the network. The method includes transmitting an input request to a server. The method further includes extracting one or more parameters associated with the input request. The method further includes fetching data associated with the input request from a database based on one or more extracted parameters. The method further includes transmitting the fetched data to the UE. Further, the method further includes performing a plurality of actions at a geographical location based on the fetched data. The method further includes dynamically visualizing the performance of the network on the UE.OBJECTIVES OF THE PRESENT DISCLOSURE

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

[0026] An objective of the present disclosure is to provide a system and a method for visualizing the performance of a network.

[0027] Another objective of the present disclosure is to provide a system and a method to determine underperforming cells in the network.

[0028] Another objective of the present disclosure is to provide an interactive user interface (UI) (e.g., a dashboard) for visualizing the performance of a network in realtime.

[0029] Other objectives and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

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

[0031] FIG. 1 illustrates an exemplary network architecture for visualizing the performance of a network, in accordance with embodiments of the present disclosure.

[0032] FIG. 2 illustrates an exemplary system architecture for visualizing the performance of the network, in accordance with embodiments of the present disclosure.

[0033] FIG. 3 illustrates an exemplary block diagram of the system for visualizing the performance of the network, in accordance with an embodiment of the present disclosure.

[0034] FIG. 4 illustrates another exemplary system architecture for visualizing the performance of the network, in accordance with an embodiment of the present disclosure.

[0035] FIG. 5 illustrates an exemplary user interface (UI) view of a dashboard, in accordance with an embodiment of the present disclosure.

[0036] FIG. 6 illustrates another exemplary UI view of the dashboard in accordance with an embodiment of the present disclosure.

[0037] FIG. 7 illustrates another exemplary UI view of the dashboard in accordance with an embodiment of the present disclosure.

[0038] FIG. 8 illustrates another exemplary UI view of the dashboard, in accordance with an embodiment of the present disclosure.

[0039] FIG. 9 illustrates another exemplary UI view of the dashboard, in accordance with an embodiment of the present disclosure.

[0040] FIG. 10 illustrates another exemplary UI view of the dashboard, in accordance with an embodiment of the present disclosure.

[0041] FIG. 11 illustrates another exemplary UI view of the dashboard, in accordance with an embodiment of the present disclosure.

[0042] FIG. 12 illustrates an exemplary flow diagram of a method for visualizing the performance of the network, in accordance with an embodiment of the present disclosure.

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

[0044] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102 - User(s)104 -User Equipments (UEs)106 - Network108 - System200 - Block diagram202 - Processor(s) 204 - Memory206 -Interface(s)208 - Processing engine210 - Database300 - System Architecture 302 - Source Node304 - Destination Node306 - Edge Node308 - Server310 - Database Table 400 - System Architecture402 - A plurality of user equipments404 - Load Balancer406 - A plurality of servers408 - Database500 - User Interface600 - User Interface700 - User Interface800 - User Interface900 - User Interface1000 - User Interface1100 - User Interface1200 - Flow diagram1300 - A computer system1310 - External storage device1320 - Bus1330 - Main memory1340 - Read only memory1350 - Mass storage device1360 - Communication port(s)1370 - ProcessorDETAILED DESCRIPTION

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

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

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

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

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

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

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

[0052] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical, and computing device. The user device is capable of receiving and / or transmitting one or parameters, performing function / s, communicating with other user devices, and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery, and an input-means such as a hard keypad and / or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.

[0053] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.

[0054] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data transfer are also expected to evolve and replace the older generations of technologies. In the field of wireless data communications, the dynamic advancement of various generations of cellular technology are also seen. The development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), and now fifth generation (5G), and more such generations such as Sixth Generation (6G) are expected to continue in the forthcoming time.

[0055] Radio Access Technology (RAT) refers to the technology used by mobile devices / User Equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with base stations, which are responsible for providing the wireless connection. Further, each RAT has its own set of protocols and standards for communication, which define the frequency bands, modulation techniques, and other parameters used for transmitting and receiving data. Examples of RATs include GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System), LTE (Long-Term Evolution), and 5G. The choice of RAT depends on a variety of factors, including the network infrastructure, the availablespectrum, and the mobile device's / device's capabilities. Mobile devices often support multiple RATs, allowing them to connect to different types of networks and provide optimal performance based on the available network resources.

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

[0057] The current systems fail to provide an apparent / proactive solution designed to monitor or address the varying network performance. The current systems fail to provide a real-time dashboard solution that provides visualization of the tracking activity of the users (e.g., field engineers), actions taken by them on sites, and their details. Furthermore, the current systems fail to provide location-wise cell details in the network such as key performance indicator (KPIs) of the site location and the KPIs health on the user’s terminal.

[0058] Thus, there is a need for a real-time dashboard solution to efficiently display, track, and optimize underperforming cells in the network that can be accessed by the user at any time anywhere. The real-time dashboard allows the user to visualize the performance of the network as soon as the data is added, removed, or modified. In simple words, any change in network is visualized in the dashboard instantly.

[0059] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing an improved system and a method for visualizing the performance of the network.

[0060] The present disclosure aims to overcome the challenges of the prior arts by providing a system and a method for determining underperforming cells in the network.

[0061] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0062] FIG. 1 illustrates an exemplary network architecture (100) for visualizing the performance of a network (106), in accordance with embodiments of the present disclosure.

[0063] As illustrated in FIG. 1, the network architecture (100) may include one or more User Equipments (UEs) (104-1, 104-2...104-N) associated with one or more users (102-1, 102-2... 102-N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2...102-N) may be collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more UEs (104-1, 104-2... 104-N) may be collectively referred to as the UE (104) or the UEs (104). Although only three UE (104) are depicted in FIG. 1, however, any number of the UE (104) may be included without departing from the scope of the ongoing description.

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

[0065] Additionally, in some embodiments, the UE (104) may include, but not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), a wearable computer device (e.g., a headmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE 104 may include, but are not limited to, any electrical, electronic, electromechanical, or equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. Further, the UE (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or an entity such as a touchpad, a touch-enabled screen, an electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.

[0066] In FIG. 1, the UE (104) may communicate with the system (108) through the network (106) for sending or receiving various types of data. In an embodiment, the network (106) may include at least one of a 5th Generation (5G) network, a 6th Generation (6G) network, or the like. The network (106) may enable the UE (104) to communicate with other devices in the network architecture (100) and / or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network 106may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

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

[0068] In an embodiment, the UE (104) is communicatively coupled with the network (106). The network (106) may receive a connection request from the UE (104). The network (106) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request.

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

[0070] FIG. 2 illustrates an exemplary system architecture (200) for visualizing the performance of the network (106), in accordance with an embodiment of the disclosure.

[0071] In an embodiment, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may include any non-transitory storage device including, for example, volatile memory such as a Random-Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, and the like.

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

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

[0074] In an embodiment, the processing engine (208) is configured for visualizing the performance of the network (106). There may be a plurality of parameters for visualizing the performance of the network (106). The plurality of parameters may include, but not limited to, a cell speed, a data transfer speed, stability of connection with the UE (104), a coverage area, orientation of cell towers, etc. The processing engine (208) is configured for transmitting an input request to a server by an application on the UE (104). The input request may request the assigned tasks associated with the user (102) from the server. The input request may correspond to a POST request to connect to a server. The POST request may be a Hyper Text Transfer Protocol (HTTP) request configured to transmit data to the server. The input request is transmitted by the UE (104) via the user (field engineer) (102). In an exemplary embodiment, a field engineer prompts an input request to get the assigned task corresponding to an anomaly in the network. The input request may be transmitted automatically to the server, upon logging into an application installed on the UE (104).

[0075] Further, the processing engine (208) is configured for extracting one or more parameters associated with the input request. The one or more extractedparameters are associated with a user profile related to the user (102). In an embodiment, the user (102) may refer to the field engineer. The user profile may be a collection of data that represents a user’ s identity and preferences. The user profile may include personal information such as username, email, profile picture, and other attributes like settings, preferences, and activity history. Further, the user profile helps personalize the user experience, storing relevant details like saved items, app configurations, and interaction data, enabling the app to tailor content and services based on individual user behavior and needs. The one or more parameters may include, but are not limited to, name of the user, location of the user, designation of the user, cell number, area code, authority of the user, previous performance of the user, status of other assigned tasks, feedback, etc. Further, the server may extract the one or more parameters upon receiving the POST request from the UE. The server may then parse the application, and the one or more parameters is extracted in a format such as, JavaScript Object Notation (JSON), Extensible Markup Language (XML), etc. In an exemplary embodiment, the one or more parameters are stored in the application installed on the UE (field engineer’s device).

[0076] The processing engine (208) is further configured for fetching data associated with the input request from the database (210) based on one or more extracted parameters. The data associated with the input request may include, but not limited to, network health, network connectivity, network coverage, recommendations, suggestions, action status, cell tower wrong tilt, cell tower’s incorrect height, any obstruction in network, etc. in any given cell or based on authority of the user (102). Each user (102) may be assigned an authority corresponding to their designation. The authority may define permission a user has to access, modify, remove, or add to the existing network (106). Typically, higher designated users have more authority than their lower counterparts. When a server fetches data from the database based on one or more parameters, the server uses the one or more parameters to construct an SQL query for relational databases and a semantic query in NoSQL databases. The query is thenexecuted against the database, retrieving matching records. The server then processes the result and returns the data in a structured format, like JSON or XML. In an embodiment, the database is updated on a daily basis. In an exemplary embodiment, the database stores the data associated with the input request of the field engineer and other users. Upon receiving the input request from the field engineer, the server may access the database and extract the parameters corresponding to the user (field engineer).

[0077] Further, the processing engine (208) is configured for transmitting the fetched data to the UE (104). In some embodiments, the fetched data may include a plurality of actions to solve any anomaly in the network (106). The plurality of actions are suggestions or recommendations provided to the user (102) to maintain the performance of the network (106). The plurality of action may include, but not limited to, moving to the cell tower’s location, changing the tilt of a dish of the cell tower, adjusting height of the cell tower, etc. to ensure the network performance is optimal. The processing engine is further configured for performing the plurality of actions at a geographical location based on the fetched data by the user related to the UE. In an exemplary embodiment, the plurality of actions may differ on task basis. For example, when an issue is detected such as, if the height of a cell tower is creating an anomaly in the performance of the network. The plurality of actions may instruct the field engineer to move to the location of the cell tower, identify the correct height of the cell tower, change the height of the cell tower for optimal performance of the network, and update the status of the task assigned in the application on the UE.

[0078] Further, the processing engine (208) is configured for dynamically visualizing the performance of the network (106) on the UE (104). The processing engine (208) is equipped to provide real-time visualization of the network’s performance (106) on the (UE) (104), enabling users to monitor and interact with network data seamlessly. The dynamic visualization means that as the user (field engineer) executes various tasks such as adjusting network parameters or updatingconfigurations, the system immediately reflects these changes in the application interface. For example, if the user modifies the status of a network component or addresses an issue, the visualization updates instantly, allowing for a clear and current representation of the network’s operational state. This immediacy not only enhances situational awareness for the user but also facilitates quicker decision-making and response times, ultimately contributing to more efficient network management and troubleshooting processes. In an embodiment, the processing engine (208) visualizes a status of the plurality of actions performed by the user on the UE (104). The status of the plurality of actions may include, but not limited to, a summary of the completed action, timestamp of the action performed by the user, total assigned tasks, recent tasks, etc. In an exemplary embodiment, the processing engine (208) may visualize the status of the plurality of actions in two tabs, such as my task summary tab associated with the actions performed and tasks assigned to the individual user, and a team task summary tab associated with the action performed and task assigned to the team of the user. The ‘my task summary tab’ may include completed tasks, total assigned tasks, recent tasks, acknowledged or unacknowledged tasks for the individual user. Further, the team task summary tab may include task summary for the team of the user, combined actions performed by the team of the user, etc.

[0079] The processing engine (208) renders the performance of the network (106) via the UI. The performance of the network (106) may be visualized by a chart, graph, map, bar graph, line chart, table, list, etc. The processing engine (208) may render the performance of the network (106) on a UE (104), so that the user (102) may track the network (106) in real-time, and in case of anomaly in the network (106), instant corrective measures are taken. The processing engine (208) may render the performance of the network in pre-defined templates based on the user preferences. The pre-defined templates and user preferences may include, but not limited to, a color combination, font size, font color, headings, title, etc. The predefined templates and user preferences may be stored in the database. In an exemplary embodiment, the UImay render the changes and the associated impact on the network on the UE, due to the plurality of actions performed by the field engineer. The user may further crosscheck and verify the network performance instantly based on the visualization rendered by the UI. In an embodiment, the processing engine (208) may render a landing page to the user depending on the user’s role in the network (106), and geographical location of the user. The landing page may include information associated with the user and the assigned tasks. Further, the user’s role in the network (106) may depend on the hierarchy of the user in the network (106). In an exemplary embodiment, If the user is a field engineer, then the landing page may only include the information relevant to the particular area or location assigned to the field engineer. However, for a senior hierarchy level user such as the manager of the field engineer, the landing page may include the information relevant to each of the field engineer and all the location assigned to every field engineer under the manager.

[0080] In an embodiment, one or more KPIs associated with the performance of the network (106) are derived based on the plurality of actions performed by the user (102). Deriving the KPIs associated with the performance of the network (106) based on the actions performed by the user (102) involves a process that begins with data collection. First, the system logs the specific actions taken by the user, such as configuration adjustments or troubleshooting steps, that measure latency, throughput, and error rates. Once this data is collected, relevant KPIs that reflect the impact of user actions on network performance are identified. For instance, if a user modifies network settings to enhance bandwidth, KPIs such as average latency, throughput, and user satisfaction scores can be calculated / derived to assess the effectiveness of those adjustments. The analysis phase includes examining correlations between the user’s actions and the performance metrics, identifying trends that emerge before and after the actions taken. Finally, the derived KPIs are presented on the dashboard in a user- friendly manner, allowing stakeholders to visualize the performance impacts related to their actions. Alerts may also be configured to notify users if any KPIs drop belowacceptable thresholds, along with recommendations for remediation, thereby creating a feedback loop that enables continuous improvement in network management.

[0081] In an embodiment, the database (210) includes data (e.g., date of the closed tasks, date of the assigned tasks, eNodeB identifier (ID), geographical location, last action, agent name, cell identifier (ID), network data, session data, predefined templates, user preferences, and the like) that may be either stored or generated as a result of functionalities implemented by any of the components of the processor (202) or the processing engine (208).

[0082] FIG. 3 illustrates an exemplary block diagram (300) of the system (108) for visualizing the performance of the network (106), in accordance with an embodiment of the present disclosure.

[0083] In an aspect, the present disclosure may allow a destination node (304) to communicate with a source node (302). The destination node (304) may include an edge node (306), a server (308), and a database table (310). In an aspect the source node (302) and the edge node (306) may have an Internet Protocol (IP) address as ‘10.X.X.X’.

[0084] In an aspect, an application or a tool running on the edge node (306) may pull the data from the source node (302). In an aspect, data may be ingested from the source node (302) to the destination node (304) on a daily basis. In an aspect, the edge node (306) may pull ‘n’ MB / day data from the source node (302). In an aspect, the edge node (306) may pull up to 200 MB / day of data from the source node (302). In an aspect, for example, the maximum average size for a circle may be around 4 MB and 28 files may be generated every day. In an aspect, the total data to be moved daily may be around 200 MB.

[0085] In an aspect, the data may be pulled via using a secure network protocol. In an aspect, the secure network protocol may be a Secure File Transfer Protocol(SFTP). The SFTP is a secure file transfer protocol that uses secure shell encryption to provide a high level of security for sending and receiving file transfers.

[0086] In an aspect, the edge node (306) may be enabled with a high availability (HA) system by including a plurality of servers in such a way that if one of the plurality of servers fails, another server may pull the data from the source node (302). The HA system in the edge node (306) may operate at a high level, continuously, without intervention, for a given time period.

[0087] In an aspect, the edge node (306) may further store the pulled data in a raw file format on a distributed file server (308). In an aspect, the distributed file server (308) may be a Distributed File System .

[0088] In an aspect, the edge node (306) may further store the pulled data in the form of a formatted file in the database (310). In an aspect, the file format may be a parsing comma-separated values (CSV) file in JAVA. The CSV file is a text file format that uses commas to separate values, and newlines to separate records.

[0089] For example, the raw files may be retained for approximately 365 days in the distributed file server (308), and the processed data (formatted file) may be retained for approximately 100 days in the database (310).

[0090] In an aspect, the number of rows in the file may change as and when a new site is made live in the Element Management System (EMS). The EMS manages specific types of one or more network elements within a communication network. In an aspect, raw files for each circle may be ingested into the distributed file server (308). In an aspect, the raw file may be available as a zip file.

[0091] In an aspect, from the daily raw files of each circle, a plurality of columns may be available as a table that may be read by and written into by the mobile application. In an embodiment, the plurality of columns may correspond to the data associated with the input request. The plurality of column may include, but not limitedto, Date, area, circle name, circle (ID), site friendly name, number of times appearance, action current state, Key Performance Indicator (KPI) impacted, average Mean Time To Repair (MTTR), average ageing, last open date, first open date, last action, maximum action, action owner, eNodeB ID, circle etc. The KPI’s of the network may measure the network’s efficiency, reliability, and user experience. Further, the KPI may include, but not limited to, latency, throughput, coverage, user experience data rate, mobility, energy efficiency, connection density, etc. In an exemplary embodiment, the date refers to a date of the generation of raw file, the area refers to the geographical location of the circle, the center name refer to a name of the center responsible for managing the corresponding area, the center ID refers to a unique code associated with the center, the KPI impacted refers to the KPI’s that are impacted due to various factors, the average MTTR refers to average time taken to identify and resolve an issue affecting a network (106).

[0092] In an aspect, Network Performance Optimization (NPO) and management team runs an analytics process to determine underperforming cells, identify the Root Cause Analysis (RCA), and suggest actions to mitigate the issues found. In an aspect, the data may be ingested in destination node (304) and published to field users through the mobile application.

[0093] FIG. 4 illustrates another exemplary system architecture (400) for visualizing the performance of the network (106), in accordance with an embodiment of the present disclosure.

[0094] The system architecture (400) may include a plurality of UEs analogous to the UE (104) of the system (108), a load balancer (404), a plurality of servers (406), and a database (408).

[0095] In an aspect, a UE (104) may be mobile phone of the field engineer connected to an internet. The load balancer (LB) (404) may receive an incoming request (e.g., POST request) from the UE (104) and forwards the request to a pluralityof servers (406). In an embodiment, the POST request is a specific type of data transfer method used in a Hypertext Transfer Protocol (HTTP) communication for sending data from the UE (104) to the server (406). The POST request may carry information such as registration data or updates about the UEs, facilitating the admission and management of the UEs. In an aspect, LB (404) may be a dedicated load balancer. The POST request is supported by the HTTP used by the World Wide Web. The POST request method requests that a web server accept the data enclosed in the body of the request message, most likely for storing it. The POST request method is often used when uploading a file or when submitting a completed web form.

[0096] In another aspect, when a specific server of the plurality of servers (406) gets heavily loaded, the LB (404) may direct the incoming request to other servers (406). In another aspect, the plurality of servers (406) may be configured in such a way that when a specific server fails, the other servers may take over to enable high availability (HA). In another aspect, the request from the plurality of servers (406) may be further transmitted to a database (408). The plurality Servers (406) have Representational State Transfer Application Programming Interfaces (REST APIs) to read data from the database (408). REST APIs provide simple, uniform interfaces because they can be used to make data / resources available through web Uniform Resource Locators (URLs). In an aspect, the database may include a Table name. In another aspect, the database may transmit the received data back to the plurality of the UEs (104) through / via the plurality of servers (406) and the LB (404).

[0097] In an aspect, ingestion of data may occur once daily, such that the dashboard is updated with a proactive database (DB) file that may be generated on the previous day. For example, the proactive database (DB) file may be generated at 10 p.m.

[0098] In an aspect, the plurality of UEs (104) may fetch the data from the database (408) via the LB (404) and through a GET request. The GET request is a requestmethod supported by the HTTP protocol used by the World Wide Web. The GET request is used to retrieve data from a specified resource. The GET request is constructed using the RESTful Application Program Interface (API) framework. The GET request returns data in formats like JSON or XML, ensuring secure and efficient communication within the 5G core network. In an aspect, the GET request may fetch required data from the database (408) via the dedicated LB (404). In an aspect, the system (108) may be configured by using Firewall 1 and Firewall 2.

[0099] In an aspect, the present disclosure enables the UE to keep downloaded data (dashboard data / site data) in the local database / memory to avoid multiple requests to a database for already fetched details.

[0100] FIG. 5 illustrates an exemplary user interface (UI) (500) view of a dashboard, in accordance with an embodiment of the present disclosure.

[0101] In an aspect, the UI (500) may display a number of metrics associated with the network.

[0102] In an aspect, the UI (500) may display a dashboard to track and optimize underperforming cells in the network. The dashboard displays a landing page available to the user that may depend on the role of the user. Each user belongs to a certain geography level (geography center / circle / national headquarter (NHQ)).

[0103] In an aspect, the geography may be determined by the level (geographywise) of the user. The user’s role, his name, and assigned geography center / circle / NHQ may be displayed on the UI (500).

[0104] In an aspect, the dashboard may be available as a container application for downloading and once the user has downloaded the container application, he / she does not need to download it again. In an aspect, data may be updated in the container application every day (e.g., at 8 A.M).

[0105] In an aspect, the dashboard is displayed on the UE with all the necessary details. For example, in an aspect, depending on the geography, the user may be shown the rank for the geography, the number of cells / eNodeBs in the geography, and the number of under observation cells and closed cells in that geography. Rank may be calculated from an available ranking sheet. For a given geographical circle, the rank to be displayed is the rank shown in the latest week (e.g., if current week is 2, then data under week 2 for a given geographical circle will be the rank of that geographical circle).

[0106] In an aspect, dashboard may display the two tabs “My Task Summary” and “Team Task Summary”. The “My Task Summary” and “Team Task Summary” may contain summarized metrics of the tasks.

[0107] In an aspect, dashboard may display geography center level user. In an aspect, geography center level users may be shown their rank relative to all geography center level users belonging to that geography center. A geography center level user may only be allowed to view the dashboard for his / her own geography center. In an aspect, for example, the “My Task Summary” metrics may show the values for the user, while the “Team Task Summary” may show the values for all geography center level users belonging to that geography center, excluding the tasks assigned to that particular user.

[0108] In an aspect, dashboard may display circle level user. In an aspect, circle level user may not be shown any rank. A circle level user may be shown statistics for his / her own circle by default. On clicking on the dropdown, the user may also be able to toggle between the other geography of his / her circle. Users may not be able to view data for other circles.

[0109] In an aspect, the “My Task Summary” may enable the user to view tasks assigned directly to the user, based on the geography the user has selected.

[0110] In an aspect, the “Team Task Summary” may display a circle level user the tasks assigned to all geography circle level users belonging to the same circle as the user.

[0111] In an aspect, dashboard may display national headquarter (NHQ) user. In an aspect, the user may be shown metrics related to NHQ by default. The user may have the option to select the circles. In an aspect, NHQ geography may have no rank.

[0112] In an aspect, all the metrics may be aggregated on different geographical circle levels. In an aspect, the data may also be specific to a given user. Either these metric counts may be maintained for each user separately or may be aggregated for each user dynamically.

[0113] FIG. 6 illustrates another exemplary UI (600) view of the dashboard, in accordance with an embodiment of the present disclosure.

[0114] In an aspect, the UI (600) may display the two tabs “My Task Summary” to the user. The UI (600) may allow the user to access a plurality of options such as “Open”, “Closed” and the “Under Observation (OB)”.

[0115] In an aspect, dashboard may display the count of completed tasks / total tasks labeled as “Tasks”. The completed tasks represent the tasks assigned to a user which have been completed by him / her and total tasks represent the total tasks assigned to the user.

[0116] In an aspect, dashboard may display tasks assigned today labeled as “Today”. In an aspect, for example, “Today” may represent a number of tasks with status “Open_Recent” or “Open_Recursive” and Ageing = 1.

[0117] In an aspect, dashboard may display recent tasks labeled as “Recent”. In an aspect, for example, “Recent” may represent a count of tasks with status “Open- Recent”.

[0118] In an aspect, dashboard may display perennial tasks labeled as “Perennial”. In an aspect, for example, “Perennial” may represent a count of tasks with status “Open_Recursive’ ’ .

[0119] In an aspect, dashboard may display tasks with ageing more than 7 labeled as “Critical”. In an aspect, for example, “Critical” may represent count of tasks with ageing more than 7.

[0120] In an aspect, dashboard may display unacknowledged tasks labeled as “!” icon. In an aspect, for example, “!” icon may represent count of tasks which have not been acknowledged by a user.

[0121] In an aspect, on clicking on the “My Task Summary” Tab, the user may be shown summary views for lower levels of geography. The hierarchy of geographies may be as follows: NHQ -> circle (State) -> geography center -> geography point.

[0122] In an aspect, all metric counts may be aggregated on geography point, geography center, and NHQ levels for each user.

[0123] In an aspect, a user may have different counts in different geography centers. For example, a Chief Technology Officer (CTO) level user may have tasks belonging to multiple geography centers. When the user views the task summary for his / her circle, the counts may be displayed for his / her circle. When the user views the task summary for a given geography center which lies within his / her circle, the counts may be displayed for him / her, for that particular geography center. Each area may be represented as a separate card, with the name of the area (circle, geography center, geography point) indicated in the header.

[0124] In an aspect, following metrics may be displayed on each card for that area. In an aspect, for example, “New Tasks” displays the tasks created on that day (Ageing =1 and Status = “Open_Recenf ’ or “Open_Recursive”). In another aspect, for example, “My Tasks” displays the tasks assigned to that user (same logic as of “My TaskSummary”). In another aspect, for example, “Team’s Tasks” displays same logic as landing page team tasks (same logic as “My Task summary” depending on what level the user is (circle / geography center / NHQ).

[0125] In an aspect, the bar at the top of the dashboard may display the metrics for the previous geography, from which the user has arrived as similar to “My Task Summary”. In an aspect, for example, if the user is viewing the “My Task Summary”, the metrics displayed above will be for that user, for that given geography center.

[0126] In an aspect, the user may also be able to toggle between views for open, closed and monitoring cells. In an aspect, the counts may be shown along with the headers. In an aspect, areas may be sorted by the number of New TasksIf status = “Open_Recent” - Action == Last ActionIf status = “Open_Recursive” - Action == Max Action

[0127] For example, if the Proactive database (DB) sheet contains “Traffic reduction in Gamma Sector” as the action assigned, the final action shown on the UI should be “Traffic Reduced (Gamma)”.

[0128] In an aspect, once the user clicks on a point view, his / her summary view may be changed, with the user now being shown the summary of actions to be performed in an area. The user may be able to toggle between different types of tasks in that geography point - “New Tasks”, “My Tasks”, “Team Tasks”.

[0129] In an aspect, the top bar may change to indicate the counts of KPIs affected by the actions to be performed. In an aspect, the top four KPIs by count may be shown by default, in descending order of count. The user can then click on more to see the entire count, as well as the full forms of the KPIs.

[0130] In an aspect, counts may be obtained by adding the count of cells with statuses as per the tab selected for that geography point. For “New Tasks”, it will becount of “yes” of the individual KPIs of all cells with status “Open_Recent” or “Open_Recursive” and Ageing = 1.

[0131] In an aspect, the user may also be able to access a map view of the given geography point.

[0132] In an aspect, each card may contain the action title in the card header. The count of unacknowledged tasks of that action belonging to that geography point may be highlighted here.

[0133] In an aspect, the card may contain icons indicating the KPIs that are being impacted and counts of recent and chronic tasks (cells with statuses “Open Recent” and “Open Recursive” belonging to that action category in that geography point).

[0134] In an aspect, cards may be sorted by the number of total recent + chronic tasks for a given action in that area.

[0135] In an aspect, there are various KPIs that are monitored to create the proactive network optimization sheet. In an aspect, for example, the five KPIs include “Low internet protocol (IP) Throughput”, “Voice over Long-Term Evolution (VoLTE) Drop High”, “Channel Quality Indicator (CQI) Degraded”, “Zero Traffic”, and “Call Degraded”. With each issue, the KPIs impacted are identified (e.g., impacted KPIs are the KPIs specified in the KPI-Impacted column). In an aspect, icons for the corresponding issue may be displayed in the cards for each issue. The low IP throughput refers to a situation where the amount of data successfully transmitted over the IP network is significantly lower than expected or required. Voice over Long-Term Evolution Drop) refers to the unexpected termination of voice calls made over an LTE network before the user intentionally ends the call. The high rates of VoLTE drops can indicate network issues such as congestion, poor signal quality, or handover problems, negatively impacting user experience. Reducing VoLTE drops is essential for ensuring reliable voice communication and maintaining customer satisfaction. The CQIdegraded refers to a situation where the Channel Quality Indicator, which measures the quality of the communication channel in mobile networks, indicates a decline in signal quality. This degradation can lead to poorer data rates, reduced connection stability, and increased call drop rates in LTE and other cellular networks. The zero traffic refers to a situation in a network where there is no data transmission or activity occurring over a given period. The call degraded refers to a situation in telecommunications where the quality of a voice call is significantly reduced compared to normal standards. This degradation can manifest as poor audio clarity, dropped calls, increased latency, or interruptions during the conversation.

[0136] FIG. 7 illustrates another exemplary UI (700) view of the dashboard, in accordance with an embodiment of the present disclosure.

[0137] In an aspect, the UI (700) may display options “New Tasks”, “My Tasks” under the “Open Tasks” option.

[0138] In an aspect, the UI (700) may display “Traffic Reduction”, “UL SINR Issue Found”, “Neighbour” etc. under the “New Tasks” option.

[0139] In an aspect, the top bar shows the top four KPIs by count of cells against which this KPI has been identified as degrading. In an aspect, on clicking on “see more”, the abbreviations and full names of the KPIs are shown, along with the counts of cells for which that KPI has been identified as degrading. In an aspect, the user can click on “see less” to return the top bar to its original form.

[0140] FIG. 8 illustrates another exemplary UI (800) view of the dashboard, in accordance with an embodiment of the present disclosure.

[0141] In an aspect, the UI (800) may display a map with open tasks associated with a particular geographical circle.

[0142] In an aspect, on the geography point level view, the user may have the option to view a map of the geography point. In an aspect, the user may be shown the map for the area, with the geography point boundary highlighted. In an aspect, cites in the geography point may be visible with the IDs of the sites being displayed. The numbers within the pin may indicate the number of tasks open on that site, based on a filter selected. In an aspect, the filter may include following items “New Tasks”, “My Tasks” and “Team Tasks”.

[0143] In an aspect, by clicking on the Options icon on the top right, the user may have access to a filter, from which the user can filter between the number of new tasks, all the user’s tasks, and their team’s tasks.

[0144] FIG. 9 illustrates another exemplary UI (900) view of the dashboard, in accordance with an embodiment of the present disclosure.

[0145] In an aspect, the UI (900) may display the details of the task associated with a particular eNodeB.

[0146] In an aspect, the UI (900) may display the KPI impacted, and cell summary details. In an aspect, the KPI impacted may be obtained from an action mapper table. The action mapper table may specify the KPIs that need to be analysed to arrive at a particular action.

[0147] In an aspect, the UI (900) may display “Traffic Reduction”, “UL SINR Issue Found”, “Neighbour” etc., associated with the particular eNodeB.

[0148] In an aspect, on clicking on a site, the user may be able to see a summary of the actions, status, KPIs and users assigned to a site. In an aspect, these metrics may be maintained cell-wise.

[0149] In an aspect, on clicking on an action, the user may be provided a list of all cells in that geography point for which that action has to be performed.

[0150] In an aspect, a bar on left can be either in red, blue, or green color. For example, red signifies cells for which the user has not opened the sub-action window even once, blue signifies cells for which the sub-action window has been opened once, and green signifies cells for which a sub-action has been specified by the user.

[0151] In an aspect, a user acknowledges a task, when the user clicks on a cell in the view and goes to the multiple-choice list of sub-actions. In an aspect, a count of acknowledged and unacknowledged tasks for each user may be maintained. In another aspect, the count may be updated in real-time. In an aspect, when a user acknowledges a task, the same may be communicated back to the server.

[0152] In an aspect, along with the cell name, the status of that cell may also be specified (e.g., status for that cell, which is obtained from the Proactive DB sheet). In an aspect, the user can see the history of the site. In another aspect, the ageing of each cell may also be displayed.

[0153] In an aspect, the bar on the left signifies whether the task has been acknowledged or not. In an aspect, the user can “Acknowledge” a task by clicking on the task. In another aspect, the user need not specify a sub-action.

[0154] In an aspect, the red, orange, and green color codes may be used to signify tasks. For example, “Unacknowledged” tasks are represented by red color, “Acknowledged” tasks are represented by orange color, and “Completed” tasks are represented by green color.

[0155] In an aspect, a task is completed once a user specifies a sub-action. In another aspect, if the tasks require a field visit, they may be completed once the user collects evidence.

[0156] FIG. 10 illustrates another exemplary UI (1000) view of the dashboard, in accordance with an embodiment of the present disclosure.

[0157] In an aspect, the UI (1000) may display a plurality of actions e.g., “Mechanical Tilt adjusted”, “Azimuth Adjusted”, “Pole Mount Changed”, “Antenna Replaced”, “Jumper replaced” and “Other” options to the user.

[0158] In an aspect, the user may select at least one of the actions performed on the eNodeB and may specify a sub action (e.g., “Antenna Height Change”) in the UI (1000).

[0159] In an aspect, once the user clicks on a cell, the sub-action list may be opened for that site. For example, the actions for which a site visit is required may need the user to be within 100 meters of the site to which the cell belongs, while clicking this. In another aspect, if the user is not within 100 meters, the user may be displayed an error message as per the mockups. In an aspect, 100 meters limit may be checked by accessing the user device location via the location API and calculating the distance between the user and the coordinates of the site that may be taken from a Master DB.

[0160] In an aspect, if the geo-fencing criteria is met, or the task does not need the user to be physically near the site, the sub-action list for that action may be shown to the user. In an aspect, the user may select one of more sub-actions for that action. If the user selects other, once the user clicks on submit, text box may pop out asking the user to specify which sub-action was performed in other. In an aspect, the user may specify sub-action as alphanumeric characters up to 50.

[0161] In an aspect, unless the user visits the site to perform the action, on clicking on submit, the user may be displayed a toast message “Successfully submitted”.

[0162] In an aspect, the user may revisit a completed task. In an aspect, for example, they may be shown the input provided and can make changes to the input. In another aspect, the submit button may be disabled until the user makes a change.

[0163] FIG. 11 illustrates another exemplary UI (1100) view of the dashboard, in accordance with an embodiment of the present disclosure.

[0164] In an aspect, for tasks which require a site visit, once the user clicks on submit after selecting the sub-actions, the user may have the option to submit evidence and comments.

[0165] In an aspect, the UI (1100) may allow the user to upload multiple images by clicking on the ‘+’ icon. Once the user clicks on ‘+’, a prompt may open for the user to select the labels for the image. The labels populated may be multi-selected and may be as per the sub-actions selected on the previous screen.

[0166] In an aspect, the UI (1100) may allow the user to enter comments. In an aspect, for example, the comments may be in alphanumeric and up to 500 characters. Once the user clicks on submit, the user may be displayed a successfully submitted toast message. In an aspect, the user may view a selected image by clicking on the image and delete an image by clicking on the delete icon at the bottom corner of the image.

[0167] In an aspect, when the user visits a sub-action page for an action that requires a field visit, he / she can change the sub-actions selected. If the user changes the sub-actions and clicks on submit, the user may be shown the previous evidence submitted. In an aspect, the user may delete images and change comments.

[0168] In an aspect, on the task view, the user may see the history of changes in status, assignee and actions performed on the cell by clicking on the history button. In an aspect, items may be arranged in the order of the time of their occurrence.

[0169] In another aspect, the changes may be captured as items of history on a site.

[0170] In an aspect, the changes may represent the change of status which may occur when a task has become chronic from recent, an issue has stopped occurring, and thus moves to “under observation”. The change of status may occur when a cell moves from under observation to closed as well, which may also be recorded as a ‘closed’event. In an aspect, for example, details like Action, Date, Old Status, New Status, Assignee, Sub- Actions may be displayed in a 4x2 matrix.

[0171] In another aspect, the changes may represent the change of assignee which may occur when the proactive action sheet assigns an action to another user. In an aspect, change of assignee may also occur when the status of an action changes from open to any other status. For example, in this case, the change of assignee may be treated as a change of status. In an aspect, for example, details like Action, Date, assigned to “Old assignee role” and name, assigned to “New assignee role” and name, Status, Sub- Actions may be displayed in a 4x2 matrix.

[0172] In another aspect, the changes may represent the change of action which may occur when the action for a given cell change, without the old action being closed. In an aspect, for example, details like Status, Date, Old Action, New Action, Assignee, Sub-Actions may be displayed in a 4x2 matrix.

[0173] FIG. 12 illustrates an exemplary flow diagram (1200) of a method for visualizing the performance of the network (106), in accordance with an embodiment of the present disclosure.

[0174] At step 1202, an input request is transmitted to a server. The input request is transmitted by an application installed on the UE via the user. The user may be one of network authorized person, network provider company employee, third-party service worker, etc. The user device may be a company issued device, or any other authorized device such as, a phone, a tablet, a PC, a laptop, a smartphone, etc.

[0175] At step 1204, one or more parameters associated with the input request are extracted. The one or more extracted parameters are associated with a user profile related to the user. The one or more parameters may include, but are not limited to, name of the user, location, designation, cell number, area code, authority of the user, previous performance of the user, status of other assigned tasks, feedback, etc.

[0176] At step 1206, a data associated with the input request from a database is fetched based on one or more extracted parameters. The data associated with the input request may include, but not limited to, network health, network connectivity, network coverage, recommendations, suggestions, action status, cell tower wrong tilt, cell tower’s incorrect height, any obstruction in network, etc. in any given cell or based on the authority of user.

[0177] At step 1208, the fetched data is transmitted to the UE. The UE may display the fetched data in a predefined format and layout via the UI. The UE may provide recommendations to solve any anomaly that occurs in the network. For example, the data may be organized in a table format, showcasing performance metrics like latency and bandwidth usage across different network segments. Alternatively, the UE utilizes graphical dashboards, featuring line graphs to illustrate network traffic trends or pie charts to represent error distributions. Additionally, alerts and notifications could pop up to highlight any anomalies, providing immediate recommendations for remediation. Other layouts might include summary dashboards for quick overviews, detailed views for in-depth analysis, and interactive maps that visually represent network components and their performance in real time.

[0178] At step 1210, a plurality of actions at a geographical location based on the fetched data are performed. The plurality of actions are generated based on the fetched data. The plurality of actions include a process to solve the anomaly in the network. The plurality of action may include moving to a tower location, changing the tilt of a dish, adjusting height of the cell tower, etc.

[0179] At step 1212, the performance of the network on the UE is dynamically visualized. The performance of the network is rendered via the UI. The performance of the network may be visualized in any one or a combination of bar graph, chart, animations, line chart, heatmap, graph, table, list etc.

[0180] In an embodiment, a status of the plurality of actions performed by the user is visualized on the UE. The status of the plurality of actions performed may include, but not limited to, a summary of the completed action, timestamp of the action performed by the user, total assigned tasks, recent tasks, etc. Further, the status of the plurality of actions is visualized in two tabs, such as my task summary tab associated with the actions performed and tasks assigned to the individual user, and a team task summary tab associated with the action performed and task assigned to the team of the user.

[0181] In an embodiment, one or more KPIs associated with the performance of the network (106) are derived based on the plurality of actions performed by the user (102). Deriving the KPIs associated with the performance of the network (106) based on the actions performed by the user (102) involves a process that begins with data collection. First, the system logs the specific actions taken by the user, such as configuration adjustments or troubleshooting steps, that measure latency, throughput, and error rates. Once this data is collected, relevant KPIs that reflect the impact of user actions on network performance are identified. For instance, if a user modifies network settings to enhance bandwidth, KPIs such as average latency, throughput, and user satisfaction scores can be calculated / derived to assess the effectiveness of those adjustments. The analysis phase includes examining correlations between the user’s actions and the performance metrics, identifying trends that emerge before and after the actions taken. Finally, the derived KPIs are presented on the dashboard in a user- friendly manner, allowing stakeholders to visualize the performance impacts related to their actions. Alerts may also be configured to notify users if any KPIs drop below acceptable thresholds, along with recommendations for remediation, thereby creating a feedback loop that enables continuous improvement in network management.

[0182] In an embodiment, a landing page is rendered to the user depending on the user’s role in the network, and geographical location of the user. The landing page may include information associated with the user and the assigned tasks. The landing pagemay act as a home page to access the assigned tasks and status of the actions performed by the user. Further, the landing page is uniquely curated for each individual user depending on the hierarchy of the user in the network and the geographical location of the user. In some embodiments, the user with higher hierarchy may be able to view the assigned tasks and status of the actions performed by the lower hierarchy users. For example, a manager of a team may be able to view the assigned tasks and status of the actions performed by the team members of the team.

[0183] In an exemplary embodiment, the present disclosure relates to a user equipment (UE) communicatively coupled with a network. The coupling includes steps of receiving, by the network, a connection request from the UE, sending, by the network, an acknowledgment of the connection request to the UE and transmitting a plurality of signals in response to the connection request. The performance of the network is visualized by a method that includes transmitting an input request to a server. The method further includes extracting one or more parameters associated with the input request. The method further includes fetching data associated with the input request from a database based on one or more extracted parameters. The method further includes transmitting the fetched data to the UE. Further, the method further includes performing a plurality of actions at a geographical location based on the fetched data. The method further includes dynamically visualizing the performance of the network on the UE.

[0184] In yet another exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for visualizing the performance of the network. The method includes transmitting an input request to a server. The method further includes extracting one or more parameters associated with the input request. The method further includes fetching data associated with the input request from a database based on one or more extracted parameters. The method further includes transmittingthe fetched data to the UE. Further, the method further includes performing a plurality of actions at a geographical location based on the fetched data. The method further includes dynamically visualizing the performance of the network on the UE.

[0185] FIG. 13 illustrates an exemplary computer system ( 1300) in which or with which embodiments of the present disclosure may be implemented.

[0186] The computer system (1300) may include an external storage device (1310), a bus (1320), a main memory (1330), a read-only memory (1340), a mass storage device (1350), a communication port(s) (1360), and a processor (1370). A person skilled in the art will appreciate that the computer system (1300) may include more than one processor and communication ports. The processor (1370) may include various modules associated with embodiments of the present disclosure. The communication port(s) (1360) may be any of an RS-232 port for use with a modembased dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fibre, a serial port, a parallel port, or other existing or future ports. The communication ports(s) (1360) may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (1300) connects.

[0187] In some embodiments, the main memory (1330) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (1340) 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 (1370). The mass storage device (1350) 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).

[0188] In some embodiments, the bus (1320) may communicatively couple the processor(s) (1370) with the other memory, storage, and communication blocks. The bus (1320) may be, e.g., a Peripheral Component Interconnect PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), 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 (1370) to the computer system (1300).

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

[0190] Thus, the present disclosure provides display of the data on the dashboard enables the users (e.g., field engineers) to specify which actions are taken on the site and collect evidence. In an aspect, the dashboard displays the graphs and charts. In an aspect, the dashboard allows logging user inputs (e.g., sub-actions) and appending the existing proactive file. In an aspect, the dashboard allows sending the notifications to the user. In an aspect, the dashboard allows displaying geography center ranking, cell, and site counts, along with average ageing and mean turnaround time. In an aspect, the dashboard allows displaying geography center and area wise aggregated statistics to ascertain the health of that area. In an aspect, the dashboard allows identifying specific actions to be taken on underperforming cells. In an aspect, the dashboard allows tracking user activity on the mobile application. In an aspect, the dashboard allows theusers to specify which actions are taken on the site and collect evidence. In an aspect, the dashboard allows generating a proactive action sheet by a Network Performance Optimization (NPO) Server from which the mobile application obtains the values shown on the dashboard.

[0191] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

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

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

[0194] The present disclosure provides a technical advancement related to monitoring and visualizing the underperforming cells of a network. This advancement addresses the challenges in real-time monitoring of the network by ingesting proactive data and presenting it in a dashboard format. The disclosure allows users to track cell health, user actions, and network KPIs via the real-time dashboard. Further, the present disclosure provide a plurality of actions to field engineer for interventions and collecting evidence, thus streamlining the troubleshooting process and enabling realtime, data-driven actions to resolve issues.TECHNICAL ADVANTAGES

[0195] As is evident from the above, the present disclosure provides a technically advanced solution by providing an improved system and method for visualizing the performance of a network.

[0196] The present disclosure provides a real-time dashboard solution to display, track, and optimize underperforming cells in the network that can be accessed by the user at any time at anywhere.

[0197] The present disclosure enables the proactive mitigation of issues in the communication network by identifying trends in the key performance indicators (KPIs) and identifying the root cause of the deteriorating KPI. Thus, increasing the overall system speed and making the system faster.

[0198] The present disclosure provides an interactive user interface (UI) for visualizing the performance of a network in real-time.

[0199] The present disclosure tracks user activity on the application, including actions taken on cell sites. To ensure accountability and allows field engineers to log actions and submit evidence of completed tasks, improving task management.

[0200] The present disclosure provides features, such as tracking of aging tasks, Mean Turnaround Time (MTTR), and area-based performance statistics, contributing to better allocation of resources and quicker response times to network issues.

Claims

We claim:

1. A method (1200) for visualizing performance of a network (106), the method (1200) comprising: transmitting (1202), by an application on a user device (UE) (104), an input request to a server (406); extracting (1204), by the server (406), one or more parameters associated with the input request; fetching (1206), by the server (406), data associated with the input request from a database (210) based on one or more extracted parameters; transmitting (1208), by the server (406), the fetched data to the UE (104); performing (1210), by a user related to the UE (104), a plurality of actions at a geographical location based on the fetched data; and dynamically visualizing (1212) the performance of the network (106) on the UE (104).

2. The method (1200) as claimed in claim 1, further comprising updating the database (210) in a real-time based on the plurality of actions performed by the user (102).

3. The method (1200) as claimed in claim 1, wherein the one or more extracted parameters are associated with a user profile related to the user (102).

4. The method (1200) as claimed in claim 1, further comprising deriving one or more key performance indicators (KPIs) associated with the performance of the network (106) based on the plurality of actions performed by the user (102).

5. The method (1200) as claimed in claim 1, further comprising visualizing a status of the plurality of actions performed by the user on the UE (104).

6. A system (108) for visualizing performance of a network (106), the system (108) comprising: a memory (204); one or more processors (202) coupled to the memory (204) and configured to execute a set of instructions stored therein to: transmit, by an application on a user device (UE) (104), an input request to a server (406); extract, by the server (406), one or more parameters associated with the input request; fetch, by the server (406), data associated with the input request from a database (210) based on one or more extracted parameters; transmit, by the server (406), the fetched data to the UE (104); perform, by a user related to the UE (104), a plurality of actions at a geographical location based on the fetched data; and dynamically visualize the performance of the network on the UE (104).

7. The system (108) as claimed in claim 6, further configured to update the database (210) in a real-time based on the plurality of actions performed by the user (102).

8. The system (108) as claimed in claim 6, wherein the one or more extracted parameters are associated with a user profile related to the user (102).

9. The system (108) as claimed in claim 6, further configured to derive one or more key performance indicators (KPIs) associated with the performance of the network (106) based on the plurality of actions performed by the user (102).

10. The system (108) as claimed in claim 6, further configured to visualize a status of the plurality of actions performed by the user on the UE (104).

11. A user equipment (UE) (104) communicatively coupled to a network (106), the coupling comprises steps of: receiving, by the network (106), a connection request from the UE (104); sending, by the network (106), an acknowledgment of the connection request to the UE (104); and transmitting a plurality of signals in response to the connection request, wherein performance of the network is visualized by a method as claimed in claim 1.

12. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors (202), cause the one or more processors (202) to perform a method (1200) for visualizing performance of a network (106), the method (1200) comprising: transmitting (1202), by an application on a user device (UE) (104), an input request to a server (406); extracting (1204), by the server (406), one or more parameters associated with the input request; fetching (1206), by the server (406), data associated with the input request from a database (210) based on one or more extracted parameters; transmitting (1208), by the server (406), the fetched data to the UE (104); performing (1210), by a user related to the UE (104), a plurality of actions at a geographical location based on the fetched data; and dynamically visualizing (1212) the performance of the network (106) on the UE (104).

Images