System and method for managing requests in a network

Abstract

The present disclosure introduces a technique to manage requests within a network. A request is initiated at a predetermined time setting and sent to a designated server. Further, the relevant parameters are extracted from the request. The parameters are associated with a user profile of the user. Further, the information associated with the parameters is retrieved from a database. The information may include tasks assigned for the user related 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. The retrieved information is then transmitted to a user device, which processes the information to perform specific operations, enhancing efficiency by automating request handling, data retrieval, and processing based on predefined time settings. The specific operation may include storing the retrieved information in a storage of the user device.

Description

SYSTEM AND METHOD FOR MANAGING REQUESTS IN A NETWORKRESERVATION OF RIGHTS

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

[0002] The present disclosure relates generally to the field of wireless communication network. More particularly, the present disclosure relates to a system and a method for managing one or more requests in a network. The present disclosure relates to a system and method for an application programming interface (API) developed to avoid multiple requests being transmitted to a database for retrieving information related to 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] “Database” refers to a structured collection of data that is stored electronically in a computer system. Databases can store information such as key Performance Indicator (KPIs) related to the network.

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

[0007] “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.

[0008] “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.

[0009] “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.

[0010] “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.

[0011] “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.

[0012] “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

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

[0014] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog, offering only voice services. Further, text messaging and data services became possible when the second-generation (2G) technology was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Currently, fifth generation (5G) technology is being deployed, offering significantly faster data speeds, lower latency, and the ability to connect many devices simultaneously. These advancements represent a significant leap forward from previous generations, enabling enhanced mobile broadband, improved Internet of Things (loT) connectivity, and more efficient use of network resources. The sixth generation (6G) technology promises to build upon these advancements, pushing the boundaries of wireless communication even further. While the 5G technology is still being rolled out globally, research and development into the 6G are rapidlyprogressing, with the aim of revolutionizing the way we connect and interact with technology.

[0015] As the wireless technologies are advancing, there is a need to cope up with the network requirements and delivering a high level of service to the customers. The conventional systems for monitoring the performance of a network are generally set up on trial and error, ignoring the fact that networks are dynamic and can be constantly varying in speed, data traffic volume, signal strength, and so on. The conventional systems fail to provide an apparent / proactive solution designed to monitor or address the varying network performance variables. The conventional systems fail to provide a real-time dashboard solution that visualizes tracking activity of the user’s (e.g., field engineers), actions taken by them on sites and their details. Further, the conventional systems for monitoring the network performance are generally slow and suffer from overloading conditions due to large incoming requests for retrieving information related to the network at their server / database. Moreover, for real-time dashboard solution, multiple requests needs to be transmitted towards the server / database connected to the dashboard for retrieving the information related to the network. However, multiple requests may overload the server / database making database slow and inefficient.

[0016] Therefore, there is a need for an improved technique that can overcome the deficiencies of the conventional systems.SUMMARY OF THE DISCLOSURE

[0017] In an exemplary embodiment, a method for managing one or more requests in a network is described. The method includes triggering a first request based on a predefined setting time towards at least one server. Further, the method includes extracting one or more parameters associated with the triggered first request. The method further includes querying a database to retrieve information associated with the one or more extracted parameters. Further, the method includes transmitting theretrieved information to the UE. The method further includes performing one or more operations associated with the retrieved information.

[0018] In an embodiment, the one or more parameters are associated with a user profile related to a user associated with the UE.

[0019] In another embodiment, the one or more operations performed by the UE comprising at least one of processing the retrieved information or storing the retrieved information at the UE.

[0020] In another embodiment, the method further includes triggering a second request associated with the processed retrieved information based on the predefined setting time towards the at least one server. Further, the method includes validating the triggered second request to authenticate the processed retrieved information. The method may further includes storing the processed retrieved information. Further, the method includes transmitting a response message comprising either a success message or a failure message towards the UE.

[0021] In another embodiment, the method further includes authenticating the processed retrieved information via token validation. Based on authentication, the method further includes parsing the processed retrieved information to a predefined format.

[0022] In another exemplary embodiment, a system for managing one or more requests in a network is described. The system includes a memory, and a processing engine coupled to the memory to execute a set of instructions stored in the memory. The processing engine is configured to trigger a first request based on a predefined setting time towards at least one server. Further, the processing engine is configured to extract one or more parameters associated with the triggered first request. The processing engine is configured to query a database to retrieve information associated with the one or more extracted parameters. Further, the processing engine is configuredto transmit the retrieved information to the UE. The processing engine is configured to perform one or more operations associated with the retrieved information.

[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 one or more requests are managed by a method that includes triggering a first request based on a predefined setting time towards at least one server. Further, the method includes extracting one or more parameters associated with the triggered first request. The method further includes querying a database to retrieve information associated with the one or more extracted parameters. Further, the method includes transmitting the retrieved information to the UE. The method further includes performing one or more operations associated with the retrieved information.

[0024] In another exemplary embodiment, a computer program product including a non-transitory computer-readable medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for managing one or more requests in a network. The method includes triggering a first request based on a predefined setting time towards at least one server. Further, the method includes extracting one or more parameters associated with the triggered first request. The method further includes querying a database to retrieve information associated with the one or more extracted parameters. Further, the method includes transmitting the retrieved information to the UE. The method further includes performing one or more operations associated with the retrieved information.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 managing one or more requests in a network.

[0027] Another objective of the present disclosure is to provide a system and a method for enabling a user device (mobile device) to keep downloaded data (dashboard data / cell site data) in its local database / memory to avoid multiple requests hitting a database / server of the dashboard for fetching information related to the network.

[0028] Another objective of the present disclosure is to provide a system and a method for developing an application programming interface (API) to avoid multiple requests hitting to the database / server for monitoring the varying network performance.

[0029] Another objective of the present disclosure is to provide a system and a method that prevents repeated database hits after multiple user inputs or sub-actions. This ensures that once the data is retrieved, it remains unchanged and consistent, allowing a dashboard in a user device to display accurate and up-to-date information without unnecessary database interactions.

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

[0031] 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 electricalcomponents, electronic components or circuitry commonly used to implement such components.

[0032] FIG. 1 illustrates an exemplary network architecture for managing one or more requests in a network, in accordance with embodiments of the present disclosure.

[0033] FIG. 2 illustrates an exemplary system architecture for managing the one or more requests in the network, in accordance with embodiments of the present disclosure.

[0034] FIG. 3A illustrates an exemplary user interfaces (UI) view of a dashboard, in accordance with an embodiment of the present disclosure.

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

[0036] FIG. 4 illustrates an exemplary block diagram of a system for managing the one or more requests in the network, in accordance with an embodiment of the present disclosure.

[0037] FIG. 5 illustrates another exemplary system architecture for managing the one or more requests in the network, in accordance with an embodiment of the present disclosure.

[0038] FIG. 6 illustrates an exemplary flow diagram of a method for managing the one or more requests in the network, in accordance with an embodiment of the present disclosure.

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

[0040] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102 - User104 - User Equipment (UE) 106 - Network108 - System200 - System Architecture202 - Processor(s)204 - Memory 206 - Interface(s)208 - Processing Engine210 - Database300A / 300B - User Interface (UI) of dashboard400 - Block Diagram 402 - Source Node404 - Destination node406 - Edge node408 - Server410 - Database table500 - System Architecture502 - A plurality of internet users504 - Load balancer506 - A plurality of servers508 - Database600 - Flow Diagram700 - A computer system710 - External storage device720 - Bus730 - Main memory740 - Read only memory750 - Mass storage device760 - Communication port(s)770 - ProcessorDETAILED DESCRIPTION

[0041] 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 present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussedabove 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.

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

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

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

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

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

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

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

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

[0050] 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 is also seen. The development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G), and now Sixth Generation (6G), and more such generations are expected to continue in the forthcoming time.

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

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

[0053] As the wireless technologies are advancing, a real time dashboard monitoring the performance of the network is essential to keep the network architecture efficient. The current real-time dashboard fetch network related information from a server / database based on the requests from a user equipment (UE) of a user (field engineer). The UE may transmit multiple requests to fetch network related information from the server / database, for example every time the user (field engineer) login into the dashboard, the dashboard fetch information from the server / database. The multiple requests may cause the server / dashboard to become overloaded and the efficiency of the dashboard may drop significantly.

[0054] The current systems fail to provide an apparent / proactive solution designed to manage the multiple requests hitting the server / database of the dashboard for retrieving information related to the network. The current systems send a request to dashboard to fetch the information related to the network every time the user login to the dashboard which utilizes extra resources of the network. Further, the multiple requests hitting the dashboard makes the current system generally slow and suffer from overloading conditions due to large incoming requests at the server / database of the dashboard.

[0055] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a system and a method for managing the multiple requests in the network.

[0056] The present disclosure aims to overcome challenges of the prior arts by providing a system and a method for developing an application programming interface (API) to avoid multiple requests hitting a database of a dashboard for fetching network related information. The API may include a GET request for fetching the network related information from the server / database. Further, the API may include a POST request for downloading the network related information from the database, replacing the multiple requests that are hitting the database of the dashboard.

[0057] The present disclosure aims to overcome challenges of the prior arts by providing a system and a method for enabling a user device (mobile device) to keep downloaded data (dashboard data / site data) in its local database / memory to avoid multiple requests hitting a database for fetching network related information.

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

[0059] FIG. 1 illustrates an exemplary network architecture (100) for managing one or more requests in a network (106), in accordance with embodiments of the present disclosure.

[0060] 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.Y11, however, any number of the UE (104) may be included without departing from the scope of the ongoing description.

[0061] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, 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-connected devices, 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.

[0062] 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 asa 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.

[0063] 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 106 may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

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

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

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

[0067] FIG. 2 illustrates an exemplary system architecture (200) for managing the one or more requests in the network (106), in accordance with an embodiment of the disclosure.

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

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

[0070] 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 hardware and programming may be implemented in several different ways. For example, the programming for the processing engine (208) may be processor-executable instructions stored on a non-transitory machine -readable storage medium 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.

[0071] In an embodiment, a real time dashboard monitoring the performance of the network (106) is essential to keep the network architecture (100) efficient. The current real-time dashboard fetch network related information from a server / database connected to the dashboard based on the requests from the UE (104) of the user (102). The UE (104) may transmit one or more requests to fetch network related informationfrom the server / database, for example every time the user (field engineer) login into the dashboard, the dashboard fetch information from the server / database. The multiple requests may cause the server / dashboard to become overloaded and the efficiency of the dashboard may drop significantly. The current implementation of the dashboard suffers from inefficiencies in handling user requests, particularly in scenarios involving multiple requests from user equipment UE (104).

[0072] In some embodiments, each time a user (102) logs into the dashboard, the UE (104) sends multiple requests to the database / server to fetch the required network performance data. This process may occur irrespective of whether the same network related information was recently fetched or if the network related information remains unchanged, evidently overloading the database and making the whole system slow.

[0073] The present disclosure provides a system and a method for enabling a user device (mobile device) to keep downloaded data (dashboard data / cell site data) in its local database / memory to avoid multiple requests hitting a database / server of the dashboard for fetching information related to the network.

[0074] In an embodiment, the processing engine (208) is configured for triggering a first request based on a predefined setting time towards at least one server. In an embodiment, the first request may be initiated once the user (102) login to the dashboard. In an embodiment, the first request may request the assigned tasks associated with the user (102) from the server. In an embodiment, the first request may correspond to a GET request to connect to a server. The GET request may be a Hyper Text Transfer Protocol (HTTP) request configured to initiate data transfer from the server to the UE (104). Further, the first request is triggered based on the predefined setting time that is configurable by a network operator. The predefined setting time may correspond to a time period after which the first request is triggered automatically, such as every 4 hours, every 24 hours, or any time period as such. In an embodiment, the processing engine monitors the clock and triggers the request automatically whenthe specified time or interval is reached. Once the condition is met, the processing engine sends a GET request to the server to retrieve the necessary data, ensuring that the system responds with accurate and up-to-date information. In simpler words, the processing engine (208) monitors the predefined setting time within the network (106). In an embodiment, once the predefined setting time is triggered, the processing engine (208) formulates the first request to be sent to the server. The first request is then transmitted to the server via a secure and efficient protocol, such as RESTful Application Programming Interface (APIs) or Session Initiation Protocol (SIP).

[0075] Further, the processing engine (208) is configured for extracting one or more parameters associated with the triggered first request. The one or more extracted parameters 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. Further, the one or more parameters associated with the user profile may include, but are not limited to, name of the user, authentication token, location of the user, designation of the user, user identifier (ID), cell number, area code, authority of the user, previous performance of the user, status of other assigned tasks, feedback, designation of the user, etc., ensuring that the data retrieved or action initiated by the system is relevant and specific to the user. The extraction process involves capturing specific parameters from the triggered first request, such as user ID, authentication token, or other relevant data tied to the user profile. These parameters can be retrieved from various parts of the request, such as query parameters, headers, or session data. Once identified, the processing engine extracts these parameters and uses them to customize the request, ensuring that the appropriate user-specific data is fetched and processed. This allows the system to tailor its response according to the user's profile, ensuring accuracy and personalization in the data retrieval process. Further, the processing engine (208) may query a user profile database containing detailed information about the user profile.

[0076] The processing engine (208) is further configured for querying a database (210) to retrieve information associated with the one or more extracted parameters. The processing engine (208) queries the database based on the one or more parameters related to the user (102) and the predefined setting time. The information associated with the one or more extracted parameters may include, but not limited to, tasks assigned for the user related 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). In an embodiment, the processing engine (208) translates the extracted parameters into a structured query, optimized for the database schema. Further, the processing engine (208) sends the query to the database via a secure connection using APIs or query interfaces. The authority may define permission user has to access, modify, remove, or add elements 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 the one or more parameters, the server uses the one or more parameters to construct a Structured Query Language (SQL) query for relational databases and a semantic query in not only SQL (NoSQL) databases. The query is then executed against the database, retrieving matching records. The server then processes the result and returns the data in a structured format, like JavaScript Object Notation (JSON) or Extensible Markup Language (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 first request from the dashboard, the processing engine (208) may access the database and extract the information related to the network corresponding to the user (field engineer). 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 exemplaryembodiment, the one or more parameters are stored in the application installed on the UE (field engineer’s device) (104).

[0077] Further, the processing engine (208) is configured for transmitting the retrieved information to the UE (104). In some embodiments, the retrieved information may include a plurality of actions to be performed by user (102) 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 actions may include, but not limited to, moving to the cell tower’s location, changing the tilt of a dish of the cell tower corresponding to cell tower wrong tilt, adjusting height of the cell tower corresponding to cell tower’s incorrect height, etc. to ensure the network performance is optimal.

[0078] The processing engine (208) is further configured for performing one or more operations associated with the retrieved information. The one or more operations may include at least one of processing the retrieved information or storing the retrieved information at the UE (104). Further, the processing of retrieved information may include visualizing the performance of the network (106) on the dashboard. The processing engine (208) is equipped to provide real-time visualization of the network’s performance on the dashboard, 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 updating configurations, 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 ofthe 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. 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.

[0079] In an exemplary embodiment, the processing engine (208) may visualize the status of the plurality of actions performed by the user such as actions performed by the individual user, action performed by the team of the user (102) on the dashboard.

[0080] The processing engine (208) may trigger a second request associated with the processed retrieved information based on the predefined setting time towards the at least one server. The second request may be a POST request associated to retrieve data from the server. The server accepts input data (in JSON format) and processes it, often saving it to a database (210). Further, the processing engine (208) may validate the triggered second request to authenticate the processed retrieved information. To validate the triggered second request, the processing engine (208) may authenticate the processed retrieved information via token validation. Based on the authentication, the processing engine (208) may parse the processed retrieved information to a predefined format. The token validation ensures secure communication between the UE (104) and server. The token (such as JSON Web Token (JWT), Open Authorization (OAuth)) is issued to the UE (104). Further, the server verifies the token before processing any sensitive operations. If the token is valid, the processing engine (208) proceeds to parse the information. In an embodiment, the parsing means converting data into a specific format expected by downstream systems or APIs for compatibility.

[0081] Upon validating, the processing engine (208) stores the processed retrieved information in a storage of the UE (104) so that the UE (104) does not send requests todatabase (210) or the server repeatedly to retrieve the relevant information, ensuring minimum load on the database (210). Further, the processing engine (208) may transmit a response message comprising either a success message or a failure message towards the UE (104). The response message may include a status along with the reason of failure. In an embodiment, if the retrieved information is stored successfully in the storage of the UE (104). The processing engine (208) may transmit a success message. Further, if the retrieved information is not stored successfully in the storage of the UE (104). The processing engine (208) may transmit a failure message.

[0082] In some embodiments, the processing engine (208) renders the performance of the network (106) via the user interface (UI) of the dashboard. 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 the 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 UI may 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 cross-check and verify the network performance instantly based on the visualization rendered by the UI.

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

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

[0085] In an embodiment, the dashboard (300A) renders the performance of the network (106) for the user (field engineer) (102). The dashboard fetches network related information from a server / database based on the requests from the UE (104) of the user (102). The UE (104) may transmit request to fetch network related information from the server / database according to a predefined setting time, for example every 4 hours, every 24 hours or the like.

[0086] In an aspect, the dashboard (300 A) may display, and underperforming cells in the network. In an aspect, the present disclosure allows to hit the database only once in a day for fetching all the details for a geographical circle in the mobile dashboard. Thus, the load on the database due to multiple incoming requests may be reduced, and the system may become faster.

[0087] In an embodiment, an average size of each file generated for a circle is approximately 4MB, with a total of 28 files produced daily. As a result, the total volume of data transferred on a daily basis is around 200MB. This substantial amount of data requires efficient handling and optimized data transfer mechanisms to ensure the system operates smoothly, without overwhelming the network or storage capacity. To optimize performance and reduce the load on the database, the system has been designed to make at least a single database request per day to fetch all the necessary details for a circle on the mobile dashboard. Previously, multiple requests would be made throughout the day, leading to increased database load and slower performance. By consolidating these requests into one daily fetch, the system reduces unnecessary database interactions, improves efficiency, and ensures faster data retrieval, providing users with a more responsive and streamlined experience.

[0088] In an aspect, the dashboard (300A) may allow a network performance optimization & management (NPO) system to run an analytics process to determineunderperforming cells data, identify the root cause analysis (RCA), and may suggest actions to mitigate the issues found. In an aspect, the collected data may be ingested in the dashboard and may be published to the users (field engineers) through a mobile application. In an aspect, the dashboard may enable 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. In an aspect, the dashboard may allow the display of the data and may enable the user (field engineers) to specify which actions may be taken on the geographical circle (site). Further, in an aspect, the dashboard may allow to collect evidence become faster and the data and the sites count detail may be accurate. In an aspect, the dashboard may allow a proper display of graphs and charts.

[0089] In an aspect, dashboard (300A) 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. In an aspect, dashboard may display average Mean Time To Repair (MTTR) and average ageing etc. In an aspect, the dashboard (300A) may be displayed on the UE of the user (field engineer) with all the necessary details. For example, in an aspect, depending on the geography, the user may view a rank for the geography, the number of cells / eNodeBs in the geography, and the number of under observation cells and closed cells etc. in that geography. In an aspect, the rank may be calculated from a ranking sheet. For a given geographical circle, the rank to be displayed may be the rank shown in the latest week (e.g., if the current week is 2, then data under week 2 for a given geographical circle will be the rank of that geographical circle). In an embodiment, 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.

[0090] FIG. 3B illustrates another exemplary UI view of the dashboard (300B), in accordance with an embodiment of the present disclosure.

[0091] In an embodiment, the user (102) may request the server / database of the dashboard (300B) to retrieve the information related to the network (106). The user (102) may initiate a GET request to query the server / database of the dashboard. Further, the server / database may return the network related information to the dashboard (300B) as explained in detail in below paragraphs. Further, the user (102) may initiate a POST request to store the retrieved network related information in the storage of the UE (104) so that the number of requests hitting the database decrease significantly, making the dashboard faster.

[0092] In an aspect, the UI may display the two tabs “My Task Summary” to the user. The UI (300B) may allow the user to access a plurality of options such as “Open”, “Closed” and the “Under Observation (OB)”. In an aspect, the dashboard (300B) 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. 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_Recenf ’ or “Open_Recursive” and Ageing = 1. 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”.

[0093] In an aspect, dashboard (300B) may display tasks as “Critical” or “Chronic”. 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 forhis / 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.

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

[0095] FIG. 4 illustrates an exemplary block diagram of a system (400) for managing the one or more requests in the network (106), in accordance with an embodiment of the present disclosure.

[0096] In an aspect, the present disclosure may allow a destination node (404) to communicate with a source node (402). The destination node (404) may include an edge node (406), a server (408) and a database table (410). In an aspect the source node (402) and the edge node (406) may have an IP address as ‘10.X.X.X’.

[0097] In an aspect, an application or a tool running on the edge node (406) may pull the data from the source node (402). In an aspect, the edge node (406) may pull ‘n’ MB / day data from the source node (402). In an aspect, the edge node (406) may pull 200 MB / day of data from the source node (402).

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

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

[0100] In an aspect, the edge node (406) may further store the pulled data in a raw file format on a distributed file server (408). In an aspect, a distributed file server (408) may be a Hadoop Distributed File System (HDFS). The HDFS operates as a distributed file system designed to run on commodity hardware. The HDFS is fault-tolerant and designed to be deployed on low-cost, commodity hardware.

[0101] In an aspect, the edge node (406) may further store the pulled data in the form of a formatted file in the database table (410). In an aspect, the database table (410) may be an Oracle table. 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.

[0102] FIG. 5 illustrates an exemplary system architecture (500) for managing the one or more requests in the network 106, in accordance with an embodiment of the present disclosure.

[0103] In an aspect, FIG. 5 illustrates a system architecture (500) for managing the one or more requests in the network (106), in accordance with an embodiment of the present disclosure. The system architecture (500) may include a plurality of internet users (502), a load balancer (504), a plurality of servers (506), and a database (508).

[0104] In an aspect, a UE (502) may be mobile phone of the field engineer connected to an internet. The load balancer (LB) (504) may receive an incoming request (e.g., POST request) from the internet user (502) and forward the request to a plurality of servers (506). In an aspect, LB (504) may be a dedicated load balancer, the A POST request is a request method supported by a Hypertext Transfer Protocol (HTTP) used by the World Wide Web. The POST request method requests that a webserver 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. In an aspect, the plurality of servers (506) may include a plurality of Drop wizard servers.

[0105] In another aspect, when a specific server of the plurality of servers (506) gets heavily loaded, the LB (504) may direct the incoming request to other servers (506). In another aspect, the plurality of servers (506) may be configured in such a way that when a specific server fails, the other servers (506) may take over to enable high availability (HA). In another aspect, the request from the plurality of servers (506) may be further transmitted to the database (508). In an aspect, the database (508) may be an Oracle database. In an aspect, the Oracle database may include a Table name. In another aspect, the database (508) may transmit the received data back to the plurality of the internet users (502) through / via the plurality of servers (506) and the LB (504).

[0106] In an aspect, the plurality of internet users (502) may fetch the data from the database (508) via the LB (504) and through a GET request. The GET request is a request method supported by the HTTP protocol used by the World Wide Web. The GET request is used to retrieve data from a specified resource. In an aspect, the GET request may fetch the required data from the database (508) (oracle table) via the dedicated LB (504). In an aspect, the system may be monitored using Firewall 1 and Firewall 2.

[0107] In an aspect, the application programming interface (API) is developed to avoid multiple hits on the database such as the GET request and the POST request.

[0108] In an aspect, the GET application programming interface (API) request may fetch required data from the database (508) (oracle table) via the dedicated LB (504).

[0109] In an aspect, the GET API request is only going to request data from the database (508), once a day only.

[0110] In an aspect, the Post API request may post the data (e.g., the captured images and corresponding comments associated with the geographical circle) to the database (508) via the LB (504) (dedicated LB) through the plurality of servers (506).

[0111] In an aspect, the present invention may allow the internet user (502) to keep / store the downloaded data into its local database / memory to avoid multiple requests to get transmitted to a database for already fetched details. In an aspect, after multiple or repeated logging user inputs (sub-actions) the hit may not go to the database again. Thus, the data may not be changed and shown accurate & properly.

[0112] EIG. 6 illustrates an exemplary flow diagram of a method (600) for managing one or more requests in a network (106), in accordance with an embodiment of the present disclosure.

[0113] At step 602, a first request is triggered based on a predefined setting time towards at least one server. The first request may correspond to a GET request to connect to a server. The GET request may be a Hyper Text Transfer Protocol (HTTP) request configured to initiate data transfer from the server to the UE (104). The predefined setting time may be configurable and may correspond to a time period after which the first request is triggered automatically, such as every 4 hours, every 24 hours, or any time period as such.

[0114] At step 604, one or more parameters associated with the triggered first request are extracted. The one or more extracted parameters are associated with a user profile related to the user. The user profile may be a collection of data that represents a user’s identity and preferences. 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.

[0115] At step 606, a database is queried to retrieve information associated with the one or more extracted parameters. The information associated with the one or more extracted parameters 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.

[0116] At step 608, the retrieved information is transmitted to the UE. In an embodiment, the retrieved information may include a plurality of actions to solve any anomaly in the network. The plurality of actions are suggestions or recommendations provided to the user to maintain the performance of the network. 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.

[0117] At step 610, one or more operations associated with the retrieved information are performed. The one or more operations performed by the UE (104) include at least one of processing the retrieved information or storing the retrieved information at the UE (104). In an embodiment, processing the retrieved information includes visualizing the performance of the network (106) on the UE (104). In another embodiment, the method further includes triggering a second request associated with the processed retrieved information based on the predefined setting time towards the at least one server. Further, the method includes validating the triggered second request to authenticate the processed retrieved information. The method may further includes storing the processed retrieved information. Further, the method includes transmitting a response message comprising either a success message or a failure message towards the UE. Further, the second request associated with the processed retrieved informationbased on the predefined setting time is transmitted towards the at least one server. The second request may include a POST request associated to retrieve data from the server. The retrieved data is then stored in the storage of the UE. In another embodiment, the method further includes authenticating the processed retrieved information via token validation. Based on authentication, the method further includes parsing the processed retrieved information to a predefined format.

[0118] In another exemplary embodiment, a system for managing one or more requests in a network is described. The system includes a memory, and a processing engine coupled to the memory to execute a set of instructions stored in the memory. The processing engine is configured to trigger a first request based on a predefined setting time towards at least one server. Further, the processing engine is configured to extract one or more parameters associated with the triggered first request. The processing engine is configured to query a database to retrieve information associated with the one or more extracted parameters. Further, the processing engine is configured to transmit the retrieved information to the UE. The processing engine is configured to perform one or more operations associated with the retrieved information.

[0119] 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 one or more requests are managed by a method that includes triggering a first request based on a predefined setting time towards at least one server. Further, the method includes extracting one or more parameters associated with the triggered first request. The method further includes querying a database to retrieve information associated with the one or more extracted parameters. Further, the method includes transmitting the retrieved information to the UE. The method further includes performing one or more operations associated with the retrieved information.

[0120] In another exemplary embodiment, a computer program product including a non-transitory computer-readable medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for managing one or more requests in a network. The method includes triggering a first request based on a predefined setting time towards at least one server. Further, the method includes extracting one or more parameters associated with the triggered first request. The method further includes querying a database to retrieve information associated with the one or more extracted parameters. Further, the method includes transmitting the retrieved information to the UE. The method further includes performing one or more operations associated with the retrieved information.

[0121] FIG. 7 illustrates an exemplary computer system (700) in which or with which embodiments of the present disclosure may be implemented. The computer system (700) may include an external storage device (710), a bus (720), a main memory (730), a read-only memory (740), a mass storage device (750), a communication port(s) (760), and a processor (770). A person skilled in the art will appreciate that the computer system (700) may include more than one processor and communication ports. The processor (770) may include various modules associated with embodiments of the present disclosure. The communication port(s) (760) may be any of an RS-232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) (760) 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 (700) connects.

[0122] In some embodiments, the main memory (730) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (740) 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 (770). Themass storage device (750) 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).

[0123] In some embodiments, the bus (720) may communicatively couple the processor(s) (770) with the other memory, storage, and communication blocks. The bus (720) 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 (770) to the computer system (700).

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

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

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

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

[0128] The present disclosure provides a technical advancement related to optimizing the process of fetching and downloading data for mobile dashboards. Previously, multiple Application Programming Interface (API) requests were made to the database, resulting in a significant load on the system as it retrieved individual data sets for the mobile application. This approach led to increased network traffic and database strain due to frequent and redundant database queries. The technical advancement consolidates these multiple API requests based on a predefined setting time, enabling the system to fetch all necessary data in one operation. By reducing the number of database hits and minimizing network overhead, the present disclosure allows the system to operate more efficiently, with faster data retrieval and reducedload on the database. This improvement enhances the overall performance, ensuring a smoother and more responsive user experience.TECHNICAL ADVANCEMENTS

[0129] As is evident from the above, the present disclosure provides a technically advanced solution by providing an improved system and for overload reduction in a database.

[0130] The present disclosure relates to a system and method for developing an application programming interface (API) to avoid multiple requests to a database for a dashboard.

[0131] The present disclosure provides a system and method for enabling a user device (mobile device) to keep downloaded data (dashboard data / cell site data) into its local database / memory to avoid multiple requests hitting a database / server of the dashboard / site for fetching information related to the network.

[0132] The present disclosure provides a system and method that that prevents repeated database hits after multiple user inputs or sub-actions. This ensures that once the data is retrieved, it remains unchanged and consistent, allowing a dashboard in a user device to display accurate and up-to-date information without unnecessary database interactions.

Claims

CLAIMS1. A method (600) for managing one or more requests in a network (106), the method (600) comprising: triggering (602), by a user equipment (UE) (104), a first request based on a predefined setting time towards at least one server; extracting (604), by the at least one server (408), one or more parameters associated with the triggered first request; querying (606), by the at least one server (408), a database (210) to retrieve information associated with the one or more extracted parameters; transmitting (608), by the at least one server (408), the retrieved information to the UE (104); and performing (610), by the UE (104), one or more operations associated with the retrieved information.

2. The method (600) as claimed in claim 1 , wherein the one or more parameters are associated with a user profile related to a user associated with the UE (104).

3. The method (600) as claimed in claim 1, wherein the one or more operations performed by the UE (104) comprising at least one of processing the retrieved information or storing the retrieved information at the UE (104).

4. The method (600) as claimed in claim 3, further comprising: triggering, by the UE (104), a second request associated with the processed retrieved information based on the predefined setting time towards the at least one server (408);validating, by the at least one server (408), the triggered second request to authenticate the processed retrieved information; storing, by the at least one server (408), the processed retrieved information; and transmitting, by the at least one server (408), a response message comprising either a success message or a failure message towards the UE (104).

5. The method (600) as claimed in claim 4, further comprising: authenticating, by the at least one server (408), the processed retrieved information via token validation; and based on the authentication, parsing, by the at least one server (408), the processed retrieved information to a predefined format.

6. A system (108) for managing one or more requests in a network (106), the system (108) comprising: a memory (204); and a processing engine (208) coupled to the memory (204) to execute a set of instructions stored in the memory (204), the processing engine (208) is configured to: trigger, by a user equipment (UE) (104), a first request based on a predefined setting time towards at least one server (408); extract, by the at least one server (408), one or more parameters associated with the triggered first request; query, by the at least one server (408), a database (210) to retrieve information associated with the one or more extracted parameters;transmit, by the at least one server (408), the retrieved information to the UE (104); and perform, by the UE (104), one or more operations associated with the retrieved information.

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

8. The system (108) as claimed in claim 6, wherein the one or more operations performed by the UE (104) comprising at least one of processing the retrieved information or storing the retrieved information at the UE (104).

9. The system (108) as claimed in claim 8, wherein the processing engine (208) is further configured to: trigger, by the UE (104), a second request associated with the processed retrieved information based on the predefined setting time towards the at least one server (408); validate, by the at least one server (408), the triggered second request to authenticate the processed retrieved information; store, by the at least one server (408), the processed retrieved information; and transmit, by the at least one server (408), a response message comprising either a success message or a failure message towards the UE (104).

10. The system (108) as claimed in claim 9, wherein the processing engine (208) is further configured to: authenticate, by the at least one server (408), the processed retrieved information via token validation; andbased on the authentication, parse, by the at least one server (408), the processed retrieved information to a predefined format.

11. A user equipment (UE) (104) communicatively coupled with 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 one or more requests are managed in the network (106) by a method (600) 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 execute a method (600) for managing one or more requests in a network (106), the method (600) comprising: triggering (602), by a user equipment (UE) (104), a first request based on a predefined setting time towards at least one server; extracting (604), by the at least one server (408), one or more parameters associated with the triggered first request; querying (606), by the at least one server (408), a database (210) to retrieve information associated with the one or more extracted parameters; transmitting (608), by the at least one server (408), the retrieved information to the UE (104); and performing (610), by the UE (104), one or more operations associated with the retrieved information.

Images