System and method for triggering real-time push notifications corresponding to work orders

Abstract

A system (102) and a method (500) for enabling real-time push notifications corresponding to at least one work order is described. A user equipment (108) receives a messaging key from a messaging module (112) upon first launch of an application and sends a device registration request to an application module (114). The application module (114) stores the messaging key in a device detail table (302) and, upon receiving the at least one work order creation request from a network management platform (402), creates at least one work order. A reporting module (106) reads the stored work order, retrieves the corresponding messaging key, and forwards it to the messaging module (112). The messaging module (112) then sends a push notification to the user equipment (108), indicating reception of the at least one work order. This system streamlines work order communication, enhancing operational efficiency and task management for field personnel.

Description

SYSTEM AND METHOD FOR TRIGGERING REAL-TIME PUSH NOTIFICATIONS CORRESPONDING TO WORK ORDERSRESERVATION OF RIGHTS

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

[0002] The embodiments of the present disclosure generally relate to work order management systems. In particular, the present disclosure relates to systems and methods for triggering real-time push notifications corresponding to work orders using a messaging module and application module infrastructure.DEFINITION

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

[0004] Messaging key refers to a unique identifier used for secure communication between the user equipment and the messaging module, particularly for sending and receiving push notifications.

[0005] Network management platform refers to a system or interface used for creating and managing work orders.

[0006] Device detail table refers to a database table that stores information about registered user equipment, including their associated messaging keys.

[0007] Work order table refers to a database table that stores information about created work orders, including their details and current status.

[0008] Reporting module refers to a software component that reads work orders from the work order table, retrieves associated messaging keys, and initiates the process of sending push notifications.

[0009] Push notification refers to a message sent from a module to a user equipment that appears even when the target application is not actively running, used in this context to inform users about new work orders.BACKGROUND OF THE DISCLOSURE

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

[0011] Work order management systems play a crucial role in various industries, facilitating the assignment and execution of tasks to a field personnel. These systems typically involve a central management platform, mobile applications for field workers, and communication infrastructure to relay information between the two. As businesses strive for increased efficiency and realtime responsiveness, the ability to quickly disseminate work orders and receive timely updates has become paramount.

[0012] Traditionally, work order management systems have relied on periodic synchronization between mobile devices and central modules. Field personnel would need to manually refresh their applications or wait for scheduled updates to receive new work orders. This approach, while functional, often led todelays in task assignment and execution, potentially impacting customer satisfaction and operational efficiency.

[0013] With the advent of push notification technology, there was an opportunity to enhance the real-time capabilities of these systems. Push notifications allow modules to send immediate alerts to mobile devices, even when the target application is not actively running. This technology promised to revolutionize how field personnel receive and respond to new work assignments.

[0014] However, the integration of push notifications into existing work order management systems has not been without challenges. Many systems struggle with reliable and timely delivery of notifications. Issues such as network connectivity, device registration, and module-side processing delays can all contribute to inconsistent notification delivery. This unreliability can lead to missed or delayed work orders, impacting the overall efficiency of field operations.

[0015] Furthermore, the process of device registration and key management for push notifications has often been a point of failure in many systems. When a mobile application is first launched, it typically registers with a messaging module to receive a unique key for future communications. However, maintaining the association between this key, the user's device, and the work order management system has proven challenging for many implementations.

[0016] Another significant issue in existing systems is the lack of real-time synchronization between work order creation and notification delivery. In many cases, there is a considerable lag between when a work order is created in the system and when the assigned field personnel receive the notification. This delay can lead to inefficiencies, missed deadlines, and poor resource allocation.

[0017] Conventional systems and methods face difficulty in providing reliable, real-time push notifications for work orders while maintaining proper device registration and key management. There is, therefore, a need in the art to provide a method and a system that can overcome the shortcomings of the existingprior arts, ensuring timely delivery of work order notifications and improving the overall efficiency of field operations.SUMMARY OF THE DISCLOSURE

[0018] In an exemplary embodiment, a method for triggering real-time push notifications corresponding to at least one work order is described. The method includes receiving, by an application module, at least one work order creation request from a network management platform based on one or more factors, creating, by the application module, at least one work order corresponding to the at least one work order request, storing, by the application module, the at least one created work order in a work order table, running, by a reporting module, a scheduler to periodically fetch the at least one work order from the work order table, analyzing, by the reporting module, the at least one fetched work order, retrieving, by the reporting module, the messaging key from a device detail table, forwarding, by the reporting module, the retrieved messaging key to the messaging module, and triggering, by the messaging module, a push notification to the user equipment corresponding to the retrieved messaging key, where the push notification indicates reception of the at least one work order.

[0019] In some embodiments, the method further comprises generating, by the messaging module, the messaging key upon launching of an application on the user equipment.

[0020] In some embodiments, the messaging key is a messaging service key. The messaging key is stored in the device detail table. The device detail table and the work order table are maintained at a database.

[0021] In some embodiments, the one or more factors include network performance data, customer requests, scheduled maintenance cycles, automated alerts, equipment lifecycle management, regulatory compliance, capacity planning, emergency responses, software updates, or quality of service improvements.

[0022] In some embodiments, the reporting module configured to perform the analysis of the at least one work order by identifying a device identifier (ID) associated with the at least one work order and retrieving the messaging key associated with the identified device ID from the device detail table.

[0023] In some embodiments, the push notification sent by the messaging module includes the work order details comprising at least one of a work order ID and a scheduled time for executing the at least one work order.

[0024] In some embodiments, the method further comprises receiving, by the application module, a device registration request from the user equipment and upon receiving, performing, by the application module, a registration of the user equipment. Upon performing registration of the user equipment, the application module is further configured to store device details comprising the device ID of the user equipment in the device detail table.

[0025] In another exemplary embodiment, a method for receiving real-time push notifications by a user equipment is described. The method includes receiving, by the user equipment, a messaging key from a messaging module, sending, by the user equipment, a device registration request to an application module, where upon detecting a schedule of a work order corresponding to the user equipment in a work order table, retrieving, by a reporting module, the messaging key from a device detail table, and forwarding, by the reporting module, the retrieved messaging key to the messaging module. The method also includes receiving, by the user equipment, a push notification from the messaging module, where the push notification indicates reception of the at least one work order.

[0026] In some embodiments, the method further comprises receiving, by the user equipment, the messaging key from the messaging module upon launching of an application on the user equipment.

[0027] In another exemplary embodiment, a system for triggering real-time push notifications corresponding to at least one work order is described. The systemincludes a messaging module, an application module, and a reporting module, the application module configured to: receive at least one work order request from a network management platform based on one or more factors, create at least one work order corresponding to the at least one work order request, and store the at least one created work order in a work order table, the reporting module configured to: run a scheduler to periodically fetch the at least one work order from the work order table, analyze the at least one fetched work order, based on the analysis, retrieve a messaging key from a device detail table, and forward the retrieved messaging key to the messaging module, and the messaging module configured to trigger a push notification to the user equipment corresponding to the messaging key, where the push notification indicates reception of the at least one work order.

[0028] In some embodiments, the messaging module is configured to generate the messaging key upon launching of an application on the user equipment.

[0029] In some embodiments, the messaging key is a messaging service key. The messaging key is stored in the device detail table. The device detail table and work order table are maintained at a database.

[0030] In some embodiments, the one or more factors include network performance data, customer requests, scheduled maintenance cycles, automated alerts, equipment lifecycle management, regulatory compliance, capacity planning, emergency responses, software updates, or quality of service improvements.

[0031] In some embodiments, the analysis of the at least one work order comprising the reporting module configured to identify a device identifier (ID) associated with the at least one work order and retrieve the messaging key associated with the identified device ID from the device detail table.

[0032] In some embodiments, the push notification sent by the messaging module includes the work order details comprising at least one of a work order ID and a scheduled time for executing the at least one work order.

[0033] In some embodiments, the application module is configured to receive a device registration request from the user equipment and perform a registration of the user equipment. Upon performing registration of the user equipment, the application module is further configured to store device details comprising the device ID of the user equipment in the device detail table.

[0034] In yet another exemplary embodiment, a user equipment for receiving real-time push notifications is described. The user equipment configured to receive a messaging key from a messaging module and send a device registration request to an application module. Upon detecting a schedule of a work order corresponding to the user equipment in a work order table, a reporting module configured to retrieve the messaging key from a device detail table and forward the retrieved messaging key to the messaging module. The messaging module configured to communicate a push notification to the user equipment corresponding to the retrieved messaging key. The user equipment receives the push notification from the messaging module. The push notification indicates reception of the at least one work order.

[0035] In some embodiments, the user equipment comprises step of receiving, by the user equipment, the messaging key from the messaging module upon launching of an application on the user equipment.

[0036] In yet another exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium having stored thereon computer-executable instructions that, when executed by a processor, cause the processor to perform a method for triggering real-time push notifications corresponding to at least one work order is described. The method includes receiving, by an application module, at least one work order creation request from a network management platform based on one or more factors, creating, by the application module, at least one work order corresponding to the at least one work order request, storing, by the application module, the at least one created work order in a work order table, running, by a reporting module, a scheduler to periodicallyfetch the at least one work order from the work order table, analyzing, by the reporting module, the at least one fetched work order, retrieving, by the reporting module, the messaging key from a device detail table, forwarding, by the reporting module, the retrieved messaging key to the messaging module, and triggering, by the messaging module, a push notification to the user equipment corresponding to the retrieved messaging key, where the push notification indicates reception of the at least one work order.

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

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

[0039] An object of the present disclosure is to provide a system and a method for triggering real-time push notifications via a messaging module, thereby improving the timeliness of work order delivery to field personnel.

[0040] Another object of the present disclosure is to fetch work order details in a user device via the messaging service notification, thereby providing immediate access to relevant information for field personnel.

[0041] Yet another object of the present disclosure is to execute the work orders at a scheduled time, thereby enhancing operational efficiency and timely task completion.

[0042] Another object of the present disclosure is to store data related to work order details and messaging service keys in a database, thereby ensuring data consistency and facilitating efficient retrieval of information.

[0043] An object of the present disclosure is to provide a system and a method that integrates device registration with work order management, thereby streamlining the process of assigning tasks to specific user devices.

[0044] An object of the present disclosure is to provide a system and a method that utilizes a reporting module to periodically read work orders, ensuring continuous monitoring and timely distribution of tasks.

[0045] An object of the present disclosure is to provide a system and a method that associates device IDs with messaging keys, thereby enhancing security and ensuring accurate delivery of push notifications.

[0046] An object of the present disclosure is to provide a system and a method that allows for monitoring and updating work order execution status, thereby improving visibility into field operations and task completion rates.

[0047] An object of the present disclosure is to provide a system and a method that generates reports based on the execution of multiple work orders, thereby facilitating performance analysis and operational insights.

[0048] An object of the present disclosure is to provide a system and a method that presents one or more user interface elements for initiating work order execution, thereby improving user experience and task management for field personnel.

[0049] Other objects 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 DRAWINGS

[0050] 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 sameparts 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 the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0051] FIG. 1 illustrates an exemplary network architecture for implementing a system for triggering real-time push notifications corresponding to at least one work order, in accordance with embodiments of the present disclosure.

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

[0053] FIG. 3 illustrates an exemplary flow diagram of a system architecture for registration of a user equipment, in accordance with embodiments of the present disclosure.

[0054] FIG. 4 illustrates an exemplary flow diagram of the system for enabling push notification via a messaging module, in accordance with embodiments of the present disclosure.

[0055] FIG. 5 illustrates an exemplary flow diagram of a method for triggering push notifications corresponding to at least one work order, in accordance with embodiments of the present disclosure.

[0056] FIG. 6 illustrates an exemplary flow diagram of a method for receiving real-time push notifications by the user equipment, in accordance with embodiments of the present disclosure.

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

[0058] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102 - System104 - Network106 - Reporting Module108, 108-1, 108-2. . . 108-N - Computing Device / User Equipment (UE)110, 110-1, 110-2...110-N - Users112 - Messaging Module114 - Application Module200 - Block Diagram of the System202 - Processor(S)204 - Memory206 - Interface(S)208 - Processing Engine210 - Database212 - Communication Module214 - Notification Management Module216 - Application Management Module218 - Messaging Management Module220 - Database Management Module222 - Reporting Management Module226 - Administrator Interface Module228 - Other Module(S)300 -Flow Diagram302 - Device Detail Table400 - Flow Diagram402 - Network Management Platform404 - Work Order Table500 - Method502, 504, 506, 508, 510, 512, 514, 516, 518 - Method Steps600 - Method602, 604, 606 - Method Steps700 - Computer System710 - External Storage Device720 - Bus730 - Main Memory740 - Read-Only Memory750 - Mass Storage Device760 - Communication Port(S)770 - ProcessorDETAILED DESCRIPTION OF THE DISCLOSURE

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

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

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

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

[0063] 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 in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.

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

[0065] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items.

[0066] The aspects of the present disclosure are directed to a system and method for triggering real-time push notifications corresponding to at least one work order. In modern work order management systems, efficient and timely communication of tasks to field personnel is crucial, yet increasingly challenging due to the growing number of work orders and the need for real-time updates. This challenge is particularly acute in industries relying heavily on mobile workforces and time-sensitive operations.

[0067] When an application is launched for the first time on a user equipment (UE), the device is registered with a messaging key received from a messaging module. A device registration request is sent to an application module, and the messaging key is stored in a device detail table. However, after performingthe device registration, users often face difficulties in receiving push notifications by respective registered devices after work order creation from a network management platform. This impacts the count of work orders, affects data integrity, and results in a drop in the number of work orders being processed efficiently.

[0068] To address these challenges, the present disclosure discloses an approach that employs a messaging module, along with an integrated system of application modules, reporting modules, and databases. This architecture is designed to efficiently handle the real-time communication demands of work order management systems, significantly reducing delays in task assignment while improving overall operational performance.

[0069] The disclosed system comprises several key components working in concert. A user equipment (UE) receives a messaging key from a messaging module upon first launch of an application. An application module handles device registration, stores messaging keys, and manages work order creation and storage. A reporting module reads / fetches stored work orders and retrieves corresponding messaging keys. The messaging module sends push notifications to the UE, indicating the reception of work orders.

[0070] The work order management process in this system follows a sophisticated workflow. When at least one work order is created on a network management platform, the application module receives the request and stores it in a work order table. A reporting module then reads the stored at least one work order, retrieves the corresponding messaging key and forwards it to the messaging module. The messaging module subsequently sends a push notification to the appropriate UE, ensuring the field personnel receive work order details in real-time.

[0071] The disclosed system supports of advanced features that enhance its efficiency and functionality. It implements both device detail and work order tables for efficient data management. The system also integrates device IDs with messaging keys, ensuring accurate push notification targeting. Moreover, itefficiently handles work order execution monitoring and status updates, providing a comprehensive view of field operations.

[0072] By addressing the challenges posed by delayed work order notifications and inefficient task assignments, this system provides a scalable and efficient solution for managing work orders in real time. It leverages messaging services and distributed database approaches to optimize work order management, enabling timely task execution and improved operational efficiency in various industries relying on mobile workforces.

[0073] As industries continue to evolve towards more dynamic and realtime operational models, the disclosed system is well-positioned to meet the evolving challenges and opportunities presented by work order management. With the anticipated growth in mobile workforces and the need for instant communication, this efficient, scalable, and real-time notification solution becomes increasingly vital. By catering to the unique requirements of modern work order management, including timely task assignment and execution monitoring, this system represents a significant advancement in field operation management architectures, potentially playing a pivotal role in shaping the future of mobile workforce management.

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

[0075] FIG. 1 illustrates an exemplary network architecture (100) for implementing a system (102) for triggering real-time push notifications corresponding to at least one work order, in accordance with embodiments of the present disclosure.

[0076] In an embodiment, the system (102) may be configured to implement an Operation Support Systems / Business Support Systems (OSS / BSS) service. The system (102) is connected to a network (104), which is further connected to at least one computing device 108-1, 108-2, ... 108-N (collectively referred to ascomputing device 108, herein) associated with one or more users 110-1, 110-2, . . . 110-N (collectively referred as user (110), herein). The computing device (108) may be personal computers, laptops, tablets, wristwatch, or any custom-built computing device integrated within a modern diagnostic machine that can connect to a network as an loT (Internet of Things) device. In an embodiment, the computing device (108) may also be referred to as user equipment (UE) or user device. Accordingly, the terms “computing device” and “user equipment” may be used interchangeably throughout the disclosure. In an aspect, the user (110) is a network operator or a field engineer.

[0077] In an embodiment, the system (102) may receive at least one input data from the user (110) via the at least one computing devices (108). In an aspect, the user (110) may be configured to initiate the process of authentication and authorization of subscribers at edge of the network (104), through an application interface of a mobile application installed in the computing devices (108). The mobile application may be configured to communicate with the network analysis module. In some examples, the mobile application may be a software or a mobile application from an application distribution platform. Examples of application distribution platforms include the App Store for iOS provided by Apple, Inc., Play Store for Android OS provided by Google Inc., and such application distribution platforms. In an embodiment, the computing device (108) may transmit the at least one captured data packet over a point-to-point or point-to-multipoint communication channel or network (104) to the system (102). In an embodiment, the computing device (108) may involve collection, analysis, and sharing of data received from the system (102) via the network (104).

[0078] In an exemplary embodiment, the network (104) may include, but not be limited to, 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. In an exemplary embodiment, the network 104 may include, but not be limited to, a wirelessnetwork, a wired network, an internet, an intranet, a public network, a private network, a packet- switched network, a circuit- switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0079] The user equipment (108) is communicatively coupled with the network (104). The coupling comprises steps of receiving, by the network (104), a connection request from the user equipment and sending, by the network (104), an acknowledgment of the connection request to the user equipment (108). Further, the coupling comprises steps of transmitting a plurality of signals in response to the connection request. Based on the connection request, real-time push notifications corresponding to at least one work order is triggered.

[0080] The system (102) further comprises a messaging module (112), an application module (114) and a reporting module (106). Further, the network (104) may enable the system (102) to communicate with the messaging module (112) and the application module (114). In an aspect, the messaging module (112) may also be referred to as a messaging server. In an aspect, the application module (114) may also be referred to as an application server. In an aspect, the reporting module (106) may also be referred to as a reporting server.

[0081] In one implementation, the system (102) may begin its workflow when the user equipment (108), which may be a mobile device used by field personnel, receives a messaging key from the messaging module (112). In an aspect, the messaging module is a software application or a dedicated module that facilitates the exchange of messages between different clients or devices. The messaging module plays a crucial role in ensuring secure and efficient communication between user equipment and other components of the system.

[0082] After receiving the messaging key, the user equipment (108) may send a device registration request to the application module (114). In an aspect, theapplication module is a software framework that provides the necessary services and infrastructure to run applications and manage their interactions with users and other systems. The application module handles device registration requests and manages the associated data. The application module processes the device registration requests from the user equipment (108). The application module interacts with a database management module to store and manage data related to the user equipments. When the registration request is received, the application module stores the messaging key and other relevant information in a device detail table, creating a link between the device and its messaging key.

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

[0084] FIG. 2 with reference to FIG. 1, illustrates an exemplary block diagram (200) of the system (102), in accordance with an embodiment of the present disclosure.

[0085] The system (102) includes one or more processor(s) (202), a memory (204), a processing engine (208), a database (210), and an interface(s) (206). In an exemplary embodiment, the processing engine (208) may include one or more modules / engines selected from any of a communication module (212), a notification management module (214), an application management module (216), a messaging management module (218), a database management module (220), a reporting management module (222), an administrator interface module (226) and other module(s) (228) having functions that may include but are not limited to receiving data, processing data, testing, storage, and peripheral functions, such as wireless communication unit for remote operation, audio unit for alerts and the like.

[0086] The one or more processor(s) (202) is configured to initiate the processor of authentication and authorization of subscribers at edge of a network through the application interface of the user equipment (UE) (108). In an embodiment, the application interface is configured to transmit one or more instructions to the one or more processor(s) (202).

[0087] In an embodiment, the one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog 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 the memory (204) of the system (102). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may comprise any non-transitory storage device including, for example, volatile memory such as Random Access Memory (RAM), or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), flash memory, and the like.

[0088] The interface(s) (206) is included within the system (102) to serve as a medium for data exchange, configured to facilitate user interaction with the mobile application. The interface(s) (206) may be composed of interfaces for data input and output devices, storage devices, and the like, providing a communication pathway for the various components of the system (102).

[0089] The interface(s) (206) may comprise a variety of interfaces, for example, interfaces for data input and output devices, referred to as RO devices, storage devices, and the like. The interface(s) (206) may facilitate communication to / from the system (102). The interface(s) (206) may also provide a communication pathway for one or more components of the system (102). Examples of suchcomponents include, but are not limited to, the processing unit / engine(s) (208) and the database (210).

[0090] In an embodiment, the processing unit / engine(s) (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (208). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) (208) may be processorexecutable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) (208). In such examples, the system (102) 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 (102) and the processing resource. In other examples, the processing engine(s) (208) may be implemented by electronic circuitry.

[0091] In an embodiment, the database (210) is configured for serving as a centralized repository for storing and retrieving various operational data. The database (210) is designed to interact seamlessly with other components of the system (102) to support the system's functionality effectively. The database (210) may store data that may be either stored or generated as a result of functionalities implemented by any of the components of the one or more processor(s) (202) or the processing engines (208). In an embodiment, the database (210) may be separate from the system (102).

[0092] As illustrated in Fig. 2, the memory (204) and the one or more processors (202) may be configured to execute a set of instructions stored in thememory (204). These instructions may orchestrate a series of operations involving various components to streamline the work order management process.

[0093] In one implementation, the system (102) may begin its workflow when the user equipment (108), which may be a mobile device (user equipment) used by a field personnel, receives the messaging key from the messaging module (112). The reception may occur upon the first launch of an application on the user equipment (108). The application may be a network monitoring mobile application. The messaging key may serve as a unique identifier, facilitating secure communication between the mobile device and the system throughout subsequent operations. It must be noted that the communication between the user equipment (108) and the system (102) is facilitated by the communication module (212).

[0094] Following the receipt of the messaging key, the user equipment (108) may send the device registration request to the application module (114) through the application management module (216). This step may establish the device's presence within the system (102), preparing it to receive at least one work order. Once the user equipment sends the device registration request, the application module recognizes the device, stores its unique messaging key, and sets up secure communication channels. This process enables the dynamic assignment of tasks based on real-time conditions, allowing field personnel to receive timely updates and instructions. Additionally, the registered device can interact with other system components and access necessary resources, creating an efficient feedback loop that enhances operational efficiency and responsiveness in managing work orders. Upon receiving the device registration request, the application module (114) may store the messaging key in the device detail table using the database management module (220). This action may create a record linking the specific device to its messaging key, enabling efficient communication in future interactions.

[0095] The work order creation process may be initiated when the application module (114) receives at least one work order creation request from a network management platform.

[0096] In an aspect, the network management platform may be an interface utilized by managers or automated systems to generate new tasks related to the network.

[0097] In response to this request, the application module (114) may create the at least one work order and store it in a work order table. This storage may ensure that all work order details are properly recorded and accessible for future reference. In an embodiment, the at least one work order may be created based on one or more factors and requirements within the network management platform. The one or more factors may include network equipment installation when new hardware needs to be installed at a specific location, routine maintenance, speed tests, scheduled checks, updates for existing network infrastructure, fault resolution when a network issue is detected and requires on-site intervention, software upgrades, and customer service requests such as setting up new connections or addressing service complaints. The at least one work order is typically created based on factors such as network performance data, customer requests, scheduled maintenance cycles, or automated alerts from network monitoring systems.

[0098] In an example, the at least one work order may be created is generated based on the specific roles assigned to the field personnel, ensuring that tasks align with their skills and responsibilities. Each of the field personnels is linked to a designated device, such as a mobile phone or tablet, configured to deliver relevant applications and access rights. When a task arises, the system creates work orders tailored to the personnel’s role — such as network technician or maintenance engineer — and sends these orders directly to their allocated device. This real-time communication allows for prompt action on tasks, presented in a user-friendly interface that includes clear instructions and necessary resources. Additionally, the system can adapt to changing conditions, updating work orders as needed, while also enabling personnel to provide feedback upon task completion, enhancing overall operational efficiency and responsiveness.

[0099] In one embodiment, a reporting module (106) (as shown in FIG. 1) may play a crucial role in the subsequent steps of the process. The reporting module may read the stored at least one work order from the work order table and then retrieve the corresponding messaging key from the device detail table with the help of the Reporting Management Module (222). This step may be essential for determining which user equipment (108) should receive the notification about the new work order, ensuring that tasks are assigned to the appropriate field personnel.

[0100] After retrieving the necessary information, the reporting module may forward the retrieved messaging key to the messaging module (112). Based on this information, the messaging module (112) may trigger a push notification to the correct user equipment (108) using the Notification Management Module (214), indicating the reception of a new work order. This real-time notification may allow field personnel to promptly respond to new assignments, potentially improving overall operational efficiency. The operations of the messaging module (112) may be handled by the Messaging Management Module (218). The triggering of push notifications is a critical process in the real-time work order management system. When a new work order is created and assigned, or when there's an update to an existing work order, the system (102) initiates the notification process. The reporting module identifies the relevant user equipment by matching the work order details with the device information stored in the device detail table. The reporting module then sends the messaging key associated with that device to the messaging module (112). The messaging module (112) uses this key to establish a secure connection with the specific user equipment (108) and pushes the notification. This triggered notification appears on the user equipment (108) regardless of whether the application is active, ensuring that field personnel are immediately aware of new or updated work orders. The messaging module (112) also employs intelligent triggers, such as location-based notifications or time-sensitive alerts, to ensure that push notifications are timely and contextually relevant to the field personnel's current situation. The system's approach to work order execution represents a significant advancement in efficiency and automation. When the push notificationis triggered and sent to the user equipment (108), it initiates a streamlined process that enhances the execution of at least one work order.

[0101] In one embodiment, the field engineer may receive instant intimation of new work order directly on their devices via messaging notifications. This realtime communication ensures that field personnel are promptly informed of new assignments, reducing delays in task initiation. The immediate nature of these notifications allows for quick response times and improved resource allocation. Upon receiving the push notification, the application on the user equipment (108) automatically fetches the complete work order details from the application module (114). This eliminates the need for manual synchronization or data retrieval, ensuring field personnel have immediate access to all necessary information. The automatic fetching process significantly reduces the time between work order creation and the field personnel's ability to start the task.

[0102] In one embodiment, the fetched work order details are stored locally on the user equipment (108). This local storage capability allows field personnel to access work order information even in areas with poor network connectivity, enhancing reliability and reducing potential delays. Field personnel can continue to work efficiently regardless of network conditions by having all necessary data available offline. Further, the application is configured to automatically initiate the execution of the at least one work order at the scheduled time. This automated scheduling reduces the risk of human error in timing and ensures that tasks are started promptly as planned. The system's ability to manage execution timing without manual intervention contributes to a more consistent and reliable work order process. By combining immediate notification, automatic data fetching, local storage, and scheduled execution, the system (102) significantly improves the work order execution rate. Field personnel can begin tasks more quickly and with all necessary information at hand, leading to faster completion times. This improved execution rate translates to increased productivity and better resource utilization across the organization. The automated process minimizes the risk of work order execution failures. By ensuring that all necessary information is available on thedevice and that execution is triggered at the appropriate time, the system reduces the likelihood of missed or improperly executed tasks. This reduction in failure rate leads to improved customer satisfaction and reduced need for rework or follow-up visits.

[0103] The overall automation of the work order execution process, from notification to scheduled start, streamlines operations and reduces manual intervention. This leads to improved operational efficiency, allowing field personnel to focus on task execution rather than administrative processes. By minimizing the administrative burden on field personnel, the system enables the field personnel to dedicate more time and effort to their core responsibilities. By leveraging messaging notifications and intelligent on-device processing, the system transforms the work order execution process into a more automated, efficient, and reliable operation. This approach not only accelerates task completion but also enhances the overall productivity of field operations, representing a significant advancement in work order management systems. The seamless integration of realtime communication, automated data management, and scheduled execution creates a robust framework for managing field operations with unprecedented efficiency and accuracy.

[0104] The system (102) may incorporate several additional features that enhance its functionality and adaptability to various work environments. For instance, the messaging key may be a messaging service key, with the messaging module (112) functioning as a cloud messaging module. The messaging module may be a cross-platform messaging solution that allows the system (102) to deliver messages reliably. The messaging module enables sending notification messages to drive user re-engagement and retention. The messaging module can send two types of messages, namely notification messages and data messages. The messaging module supports message targeting to single devices, groups of devices, or topics, and can be used with Android, iOS, and web applications. Both the device detail table and work order table may be maintained in a database (210), ensuring data consistency and facilitating easy access to information across the system (102).Integrating the messaging module with the database (210) allows for efficient, secure, and scalable real-time messaging, crucial for timely work order notifications to the field personnel.

[0105] The application on the user equipment (108) may be configured to fetch work order details from the application module (114) in response to receiving the push notification. This feature may provide the field personnel with immediate access to all relevant information about their assigned tasks. Furthermore, the application may be capable of executing the at least one work order at a scheduled time, allowing for efficient task management and timely completion of assignments.

[0106] To ensure that no tasks are overlooked, the reporting module may be configured to run a scheduler that periodically reads at least one work order from the work order table. This proactive approach may help maintain a steady flow of tasks to field personnel, potentially increasing productivity and reducing idle time.

[0107] The process of retrieving the messaging key may involve the reporting module identifying the device ID associated with the at least one work order and then retrieving the corresponding messaging key. This method may ensure that notifications are consistently sent to the correct device, reducing the risk of miscommunication or misdirected work orders.

[0108] The push notifications sent by the messaging module (112) may include specific work order details, such as the work order ID and scheduled execution time. This immediate provision of key information may allow field personnel to quickly assess the nature and urgency of the task, facilitating better time management and prioritization of work.

[0109] The application on the user equipment (108) may be further enhanced to display the fetched work order details and present one or more user interface elements for initiating task execution. This feature may provide a user-friendly interface for field personnel to interact with their assignments, potentially improving task comprehension and execution efficiency.

[0110] The application module (114) may be configured to monitor work order execution and update the work order table with the current status. This realtime tracking may provide managers and administrators with up-to-date information on task progress, allowing for better resource allocation and prompt addressing of any issues that may arise during execution. The execution of at least one work order may be monitored through a multi-step process. Initially, a field personnel use the application on their user equipment (108) to provide real-time status updates as they progress through the at least one work order. Further, the application module (114) may require confirmation at key stages of the at least one work order, such as arrival at the site, commencement of work, and completion of specific tasks. Further, the application module (114) may record the time taken for each stage of the work order execution. For certain tasks, the field personnel may be required to upload photos or documents as proof of work completed. The application module (114) may use the user equipment's GPS to verify the location of the field personnel during work order execution.

[0111] The system (102) may also allow for confirmation of work order execution from the user equipment (108). Upon receiving this confirmation, the application module (114) may update the work order table accordingly. This feature may provide a clear record of completed tasks, facilitating accurate reporting and performance evaluation. The work order execution status can be categorized into several types including pending, in progress, on hold, completed, and failed. In the event of a failed execution, an immediate notification may be sent to the supervisor or manager. Further, the field personnel may be prompted to provide a detailed reason for the failure and the at least one work order may be flagged for review and potential reassignment or rescheduling. Any partial progress made on the at least one work order may be saved to avoid duplication of efforts in future attempts.

[0112] To support data-driven decision making, the application may be capable of generating comprehensive reports based on the execution of multiple work orders. These reports may be transmitted, by the Administrator Interface Module (226), to administrators. The reports provide valuable insights corresponding to operational efficiency, resource utilization, and areas for potential improvement.

[0113] The application module (114) may integrate the device ID of the user equipment (108) with the messaging key in the device detail table. This integration may ensure a robust link between devices and their communication channels, enhancing the system's ability to target notifications and maintain secure connections with field devices accurately. The integration of the device ID with the messaging key in the device detail table serves several crucial objectives such as enhanced security by linking the unique device ID to the messaging key, the system ensures that push notifications are only sent to authenticated and authorized devices. Further the integration minimizes the risk of work orders being sent to incorrect devices, ensuring that each field personnel receives only their assigned tasks. The linked IDs allow for faster and more direct communication between the system and specific user equipment. This integration provides a clear record of which devices have been used for which work orders, aiding in accountability and troubleshooting. It allows the system to tailor notifications and work order details to the specific user and device, potentially improving user experience and efficiency.

[0114] By leveraging cloud-based messaging and distributed database approaches, this system (102) may optimize work order management, enabling timely task execution and improving operational efficiency. The real-time nature of the notifications and updates may allow for more responsive and agile field operations, potentially leading to enhanced customer satisfaction and resource utilization.

[0115] The modular design of the system (102) may allow for easy scalability and adaptability. As the volume of work orders increases or new types of work orders are introduced, the system (102) may be easily expanded or modified to handle new requirements. This flexibility may make the system (102) suitable for a wide range of industries and organizational sizes, from small local businesses to large multinational corporations.

[0116] The integration of the device IDs with the messaging keys in the device detail table may enhance the security and accuracy of the system. This integration may ensure that push notifications are sent to the correct devices, reducing the risk of assigning work orders to the wrong personnel. The system's ability to monitor work order execution and update statuses in real-time may provide valuable insights into operational efficiency and help identify areas for improvement.

[0117] In conclusion, the described system (102) may provide a comprehensive solution for real-time work order management and communication. By leveraging push notifications, centralized data management, and intelligent reporting, the system (102) may significantly enhance the efficiency and effectiveness of field operations. The real-time nature of the system (102) may allow for more responsive and agile field services, potentially leading to improved customer satisfaction and operational performance.

[0118] FIG. 3 illustrates an exemplary flow diagram (300) of a system architecture for the registration of the user equipment (108), in accordance with an embodiment of the present disclosure.

[0119] Referring to FIG. 3, the system architecture comprises the user equipment (108), the application module (114), the database (210) containing the device detail table (302), and the messaging module (112). The messaging module (112) may be a backend module, such as the cloud messaging module.

[0120] When an application is launched in the user equipment (108) for the first time, the application may receive a messaging key from the messaging module (112). The user equipment (108) may then send a device registration request to the application module (114). The application module (114) may store the messaging key in the device detail table (302) of the database (210).

[0121] In an aspect, if the at least one work order is created from a network management platform (402) or from any other source, the work order request may first go to the database (210) to find the particular device ID. The device ID may be integrated with the messaging key in the messaging module (112). Thus, there may be a unique messaging key that is integrated with that particular device ID.

[0122] After identifying the particular user equipment (108) by retrieving the device details from the device detail table (302), the system may provide the push notification containing the work order details and the work order ID. Upon receiving the push notification in the application on the user equipment (108), all the work order details and the actions to be taken may be automatically fetched from the application module (114) to the application on the user equipment (108).

[0123] FIG. 4 illustrates an example of a flow diagram (400) of the system architecture for enabling the push notification flow via the messaging module (112), in accordance with an embodiment of the present disclosure.

[0124] A network management platform (402) performs the creation of the at least one work order. The at least one created work order from the network management platform (402) is stored in a work order table (404) via the application module (114). The work order table acts as a single source of truth for all work orders, both active and completed. Each work order in the work order table is typically organized in a structured format, containing key details such as work order ID, assigned personnel, task description, status (active, in progress, completed), priority level, and timestamps for creation and completion. This structure facilitates easy data retrieval and analysis. The work order table provides real-time visibilityinto all active tasks across the organization. The work order table can be integrated with other systems, such as inventory management or customer relationship management (CRM) systems, enhancing its functionality.

[0125] The reporting module (106) runs a scheduler to read the at least one work order. The reporting module (106) retrieves the messaging key corresponding to the at least one work order from the device detail table (302).

[0126] The reporting module (106) forwards the messaging key to the messaging module (112). The messaging module (112) then sends a push notification to the respective user equipment (108). The push notification may include work order details such as the time and work order ID. Using the messaging key, the work order details are fetched to the user equipment (108). When the user receives the push notification details, execution of the at least one work order may be initiated.

[0127] As the users (e.g., field engineers) receive the at least one work order and details corresponding to their devices via the push notification, execution of work orders is improved and becomes faster and without failure. After receiving the push notification, the at least one work order is fetched in the user equipment (108) itself and can be executed at the scheduled time. Due to the push notification, the work order execution process may become more automated and efficient.

[0128] FIG. 5 illustrates an exemplary flow diagram of a method (500) for triggering the real-time push notifications corresponding to the at least one work order, in accordance with embodiments of the present disclosure.

[0129] At step (502), the method (500) may include receiving, by the application module (114), at least one work order creation request from the network management platform (402) based on one or more factors. The one or more factors may include network performance data, customer requests, scheduled maintenance cycles, automated alerts, equipment lifecycle management, regulatory compliance, capacity planning, emergency responses, software updates, or quality of serviceimprovements. This step may mark the beginning of a new work order's lifecycle within the system. The network management platform (402) may be an interface used by managers or automated systems to input new tasks or assignments. The at least one work order creation request may contain various details about the task, such as its nature, location, priority, and scheduled execution time.

[0130] At step (504), the method (500) includes creating, by the application module (114), at least one work order. In an aspect, the work order creation process may be initiated when the application module (114) receives at least one work order creation request from the network management platform. In response to this request, the application module (114) may create the at least one work order. The at least one work order may be created based on one or more factors and requirements within the network management platform. The one or more factors may include network equipment installation when new hardware needs to be installed at a specific location, routine maintenance, speed tests, scheduled checks, updates for existing network infrastructure, fault resolution when a network issue is detected and requires on-site intervention, software upgrades, and customer service requests such as setting up new connections or addressing service complaints. The at least one work order is typically created based on factors such as network performance data, customer requests, scheduled maintenance cycles, or automated alerts from network monitoring systems.

[0131] At step (506), the method (500) includes storing, by the application module (114), the at least one created work order in a work order table (404). This step may involve processing the information received in the at least one work order creation request and formatting it into a structured work order entry. The work order table (404) may serve as a centralized repository for all active and completed work orders, enabling efficient tracking and management of tasks across the organization. The application module (114) stores the created work order in the work order table (404).

[0132] At step (508), the method (500) includes running, by reporting module (106), a scheduler to periodically fetch the at least one work order from the work order table (404). In an aspect, the reporting module (106), fetches the stored at least one work order from the work order table (404). This step may initiate the process of assigning the at least one work order to an appropriate field personnel. The reporting module (106) may be configured to run the scheduler to periodically read work orders from the work order table (404), ensuring that new tasks are promptly processed and assigned. This proactive approach may help maintain a steady flow of work to field personnel, potentially reducing idle time and improving overall productivity.

[0133] Furthermore, at step (510), the method (500) may include analyzing, by the reporting module (106), the at least one fetched work order. This analyzing step may involve identifying the device ID associated with the at least one work order.

[0134] At step (512), the method (500) may include retrieving, by the reporting module (106), the messaging key corresponding to the at least one work order from the device detail table (302). The reporting module (106) retrieves the messaging key associated with that device ID. This process ensures that the work order notification is sent to the correct user equipment (108), reducing the risk of misassigned tasks or communication errors. In an aspect, the messaging key may be a messaging service key. The messaging service key may be a cloud messaging key, and the messaging module (112) may be a cloud messaging module. This implementation may leverage the robust infrastructure of cloud-based messaging services, potentially enhancing the reliability and scalability of the system.

[0135] The application module (114) may store the messaging key in a device detail table (302). This step may create a persistent record linking the user equipment (108) to its unique messaging key. The device detail table (302) may be maintained in the database (210), along with the work order table (404). Furthermore, upon receiving the messaging key from the messaging module (112)upon launch of the application, the user equipment (108) sends a device registration request to the application module (114). Upon receiving the device registration request from the user equipment (108), the application module (114) performs a registration of the user equipment (108). After performing registration of the user equipment (108), the application module (114) is further configured to store device details comprising the device ID of the user equipment (108) in the device detail table (302). The application module (114) integrates the device ID of the user equipment (108) with the messaging key in the device detail table (302). This centralized storage of device and work order information may facilitate efficient data retrieval and management, potentially reducing the risk of data inconsistencies or communication errors.

[0136] At step (514), the method (500) may include forwarding, by the reporting module (106), the retrieved messaging key to the messaging module (112). This step prepares the messaging module (112) to send a targeted notification to the appropriate user equipment (108). By providing the messaging module (112) with the correct messaging key, the system ensures that the push notification reaches the intended recipient promptly and securely.

[0137] At step (516), the method (500) may include triggering, by the messaging module (112), a push notification to the user equipment (108), wherein the push notification indicates reception of the at least one work order. This step delivers the work order information directly to the field personnel's device, enabling immediate awareness of new assignments. The push notification may include work order details such as the work order ID and the scheduled time for executing the at least one work order, allowing the recipient to quickly assess the nature and urgency of the task.

[0138] FIG. 6 illustrates an exemplary flow diagram of a method (600) for receiving real-time push notifications by the user equipment (108), in accordance with embodiments of the present disclosure.

[0139] At step (602), the method (600) may include receiving, by the user equipment (108), the messaging key from the messaging module (112). The messaging module (112) is configured to generate the messaging key upon launch of an application on the user equipment (108). In an aspect, the launch may be first launch of the application on the user equipment (108). This step may initiate the process of integrating the user equipment (108) into the work order management system. The messaging key may serve as a unique identifier for the user equipment (108), enabling secure and targeted communication throughout the work order process.

[0140] At step (604), the method (500) may include sending, by the user equipment (108), a device registration request to the application module (114). This step may establish the user equipment (108) as an active participant in the work order management system. The device registration request may contain information about the user equipment (108), such as its device ID, which may be used for future identification and communication. This registration process may enable the system to maintain an up-to-date roster of available field personnel and their associated devices, potentially improving task allocation efficiency.

[0141] In an aspect, upon detecting a schedule of a work order corresponding to the user equipment (108) in the work order table (404), the reporting module (106) retrieves the messaging key from the device detail table (302). The reporting module (106) forwards the retrieved messaging key to the messaging module (112). The messaging module (112) communicates a push notification to the user equipment (108) corresponding to the retrieved messaging key.

[0142] At step (606), the method (600) includes receiving, by the user equipment (108), the push notification from the messaging module (112). The push notification indicates reception of the at least one work order.

[0143] Following the reception of the push notification, the method (600) may further include additional steps to enhance the work order management process. The application on the user equipment (108) may fetch work order details from the application module (114) in response to receiving the push notification. This step provides the field personnel with comprehensive information about their assigned task, potentially improving their ability to prepare for and execute the work efficiently.

[0144] The application on the user equipment (108) may then display the fetched work order details and present one or more user interface elements for initiating execution of the at least one work order. This user-friendly interface may facilitate easy interaction with the at least one work order, potentially reducing confusion and improving task comprehension. The application may also be configured to execute the at least one work order at a scheduled time, ensuring that tasks are performed according to the planned timeline.

[0145] Throughout the work order execution process, the application module (114) may monitor the progress and update the work order table (404) with the current status of the work order execution. This real-time tracking may provide managers and administrators with up-to-date information on task progress, enabling better resource allocation and prompt addressing of any issues that may arise during execution.

[0146] Upon completion of the at least one work order, the user equipment (108) may send a confirmation of work order execution to the application module (114). The application module (114) may then update the work order table (404) based on this confirmation, maintaining an accurate record of completed tasks. This feature may facilitate precise reporting and performance evaluation, potentially improving overall operational efficiency.

[0147] In an aspect, the method (600) may also include generating, by the application module (114), a report based on the execution of multiple work orders.This comprehensive report may be transmitted to administrators, providing valuable insights into operational efficiency, resource utilization, and areas for potential improvement. These data-driven insights may guide strategic decisionmaking and continuous process optimization. To enhance the system's ability to accurately target notifications and maintain secure connections with field devices, the method (500) may include integrating, by the application module (114), the device ID of the user equipment (108) with the messaging key in the device detail table (302). This integration creates a robust link between devices and their communication channels, potentially improving the overall security and reliability of the work order management system.

[0148] The methods (500, 600) described above presents a comprehensive approach to real-time work order management, leveraging push notifications and centralized data management to streamline operations. By enabling prompt communication of work orders, facilitating easy access to task details, and providing real-time status updates, these methods (500, 600) may significantly enhance the efficiency and effectiveness of field operations. The integration of reporting and analysis tools further supports data-driven decision making, potentially leading to continuous improvement in operational processes. As organizations increasingly rely on mobile workforces and require agile response to changing task priorities, this method offers a robust solution to meet these evolving needs.

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

[0150] As shown in FIG. 7, 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), communication port(s) (760), and a processor (770). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (770) may include various modules associated with embodiments of the presentdisclosure. 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 port(s) (760) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.

[0151] 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) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (770). The mass 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 device (750) includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.

[0152] The bus (720) communicatively couples the processor (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), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (770) to the computer system.

[0153] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (720) to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through networkconnections 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 limit the scope of the present disclosure.

[0154] The exemplary computer system (700) is configured to execute 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 triggering real-time push notifications corresponding to at least one work order is described. The method includes receiving, by an application module, at least one work order creation request from a network management platform based on one or more factors, creating, by the application module, at least one work order corresponding to the at least one work order request, storing, by the application module, the at least one created work order in a work order table, running, by a reporting module, a scheduler to periodically fetch the at least one work order from the work order table, analyzing, by the reporting module, the at least one fetched work order, retrieving, by the reporting module, the messaging key from a device detail table, forwarding, by the reporting module, the retrieved messaging key to the messaging module, and triggering, by the messaging module, a push notification to the user equipment corresponding to the retrieved messaging key, where the push notification indicates reception of the at least one work order.

[0155] The present disclosure provides technical advancement related to real-time work order management systems. This advancement addresses the limitations of existing solutions by introducing a comprehensive, integrated approach to work order assignment and execution through push notifications. The disclosure involves a novel combination of device registration, real-time notification, and centralized data management, which significantly improves operational efficiency and task completion rates. By implementing a messaging key-based system integrated with device identification, the disclosed invention enhances the accuracy and security of work order assignments, resulting in reducedmiscommunication and improved resource utilization. The incorporation of a reporting module that periodically checks for new work orders ensures timely task distribution, while the real-time status updates facilitate better oversight and management of field operations. Furthermore, the system's ability to generate comprehensive reports based on multiple work order executions provides valuable insights for continuous process improvement. This integrated approach to work order management not only streamlines operations but also enhances the responsiveness of field personnel, potentially leading to improved customer satisfaction and operational cost-effectiveness.

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

[0157] The present disclosure provides a system and method for enabling real-time push notifications via a messaging module, which may be a cloud messaging module. This approach significantly enhances the efficiency of work order management by delivering timely notifications to field personnel.

[0158] The present disclosure improves the execution of work orders by providing users, such as field engineers, with immediate intimation of new tasks and corresponding details directly to their devices. This real-time communication reduces delays and minimizes the risk of missed assignments, potentially leading to faster and more reliable task completion.

[0159] The present disclosure enables automatic fetching of work order details on the user device upon receipt of a push notification. This feature ensures that field personnel have immediate access to all necessary information, potentially reducing preparation time and improving task comprehension.

[0160] The present disclosure facilitates the execution of work orders at scheduled times, as the system can include timing information in the push notifications. This capability may enhance overall operational efficiency by ensuring tasks are performed according to plan.

[0161] The present disclosure includes a reporting module that periodically reads work orders from a centralized table. This proactive approach helps maintain a steady flow of tasks to field personnel, potentially reducing idle time and improving overall productivity.

[0162] The present disclosure incorporates a mechanism for monitoring work order execution and updating statuses in real-time. This feature provides managers with up-to-date information on task progress, enabling better resource allocation and prompt addressing of any issues that may arise during execution.

[0163] The present disclosure allows for the generation of comprehensive reports based on the execution of multiple work orders. This capability supports data-driven decision making and may lead to continuous improvement in operational processes.

[0164] The present disclosure integrates device IDs with messaging keys in a centralized table, enhancing the security and accuracy of the notification system. This integration ensures that push notifications are sent to the correct devices, reducing the risk of work orders being assigned to the wrong personnel.

[0165] The present disclosure's modular design allows for easy scalability and adaptability. As the volume of work orders increases or new types of workorders are introduced, the system can be easily expanded or modified to handle new requirements.

[0166] The present disclosure's real-time nature allows for more responsive and agile field services, potentially leading to improved customer satisfaction and operational performance.

Claims

We claim:

1. A method (500) for triggering real-time push notifications corresponding to at least one work order, the method (500) comprising: receiving (502), by an application module (114), at least one work order creation request from a network management platform (402) based on one or more factors, creating (504), by the application module (114), at least one work order corresponding to the at least one work order request; storing (506), by the application module (114), the at least one created work order in a work order table (404); running (508), by a reporting module (106), a scheduler to periodically fetch the at least one work order from the work order table (404); analyzing (510), by the reporting module (106), the at least one fetched work order; based on analysis, retrieving (512), by the reporting module (106), a messaging key from a device detail table (302); forwarding (514), by the reporting module (106), the retrieved messaging key to the messaging module (112); and triggering (516), by the messaging module (112), a push notification to the user equipment (108) corresponding to the retrieved messaging key, wherein the push notification indicates reception of the at least one work order.

2. The method (500) of claim 1, further comprising: generating, by the messaging module (112), the messaging key upon launching of an application on the user equipment (108).

3. The method (500) of claim 1, wherein the messaging key is a messaging service key, and the messaging key is stored in the device detail table (302), wherein the device detail table (302) and the work order table (404) are maintained at a database (210).

4. The method (500) of claim 1, wherein the one or more factors include network performance data, customer requests, scheduled maintenance cycles, automated alerts, equipment lifecycle management, regulatory compliance, capacity planning, emergency responses, software updates, or quality of service improvements.

5. The method (500) of claim 1, wherein the reporting module (106) configured to perform the analysis of the at least one work order by: identifying a device identifier (ID) associated with the at least one work order; and retrieving the messaging key associated with the identified device ID from the device detail table (302).

6. The method (500) of claim 1, wherein the push notification sent by the messaging module (112) includes the work order details comprising at least one of a work order ID and a scheduled time for executing the at least one work order.

7. The method (500) of claim 5, further comprising: receiving, by the application module (114), a device registration request from the user equipment (108); and upon receiving, performing, by the application module (114), a registration of the user equipment (108), wherein upon performing registration of the user equipment (108), the application module (114) is further configured to store device details comprising the device ID of the user equipment (108) in the device detail table (302).

8. A method (600) for receiving real-time push notifications by a user equipment (108), the method (600) comprising: receiving (602), by the user equipment (108), a messaging key from a messaging module (112); sending (604), by the user equipment (108), a device registration request to an application module (114), wherein upon detecting a schedule of a work order corresponding to the user equipment (108) in a work order table (404), retrieving, by a reporting module (106), the messaging key from a device detail table (302); forwarding, by the reporting module (106), the retrieved messaging key to the messaging module (112); and communicating, by the messaging module (112), a push notification to the user equipment (108) corresponding to the retrieved messaging key; and receiving (606), by the user equipment (108), a push notification from the messaging module (112), wherein the push notification indicates reception of the at least one work order.

9. The method (600) of claim 8, further comprising: receiving, by the user equipment (108), the messaging key from the messaging module (112) upon launching of an application on the user equipment (108).

10. A system (102) for triggering real-time push notifications corresponding to at least one work order, the system (102) comprising a messaging module (112), an application module (114), and a reporting module (106), the application module (114) configured to:receive at least one work order request from a network management platform (402) based on one or more factors; create at least one work order corresponding to the at least one work order request; and store the at least one created work order in a work order table (404); a reporting module (106) configured to: run a scheduler to periodically fetch the at least one work order from the work order table (404); analyze the at least one fetched workorder; based on the analysis, retrieve a messaging key from a device detail table (302); and forward the retrieved messaging key to the messaging module (112); and the messaging module (112) configured to trigger a push notification to the user equipment (108) corresponding to the messaging key, wherein the push notification indicates reception of the at least one work order.

11. The system (102) of claim 10, wherein the messaging module (112) is configured to generate the messaging key upon launching of an application on the user equipment (108).

12. The system (102) of claim 10, wherein the messaging key is a messaging service key, and wherein the messaging key is stored in the device detail table (302), wherein the device detail table (302) and the work order table (404) are maintained at a database (210).

13. The system (102) of claim 10, wherein the one or more factors include network performance data, customer requests, scheduled maintenance cycles, automated alerts, equipment lifecycle management, regulatory compliance, capacity planning, emergency responses, software updates, or quality of service improvements.

14. The system (102) of claim 10, wherein the analysis of the at least one work order comprising: the reporting module (106) configured to: identify a device identifier (ID) associated with the at least one work order; and retrieve the messaging key associated with the identified device ID from the device detail table (302).

15. The system (102) of claim 10, wherein the push notification sent by the messaging module (112) includes the work order details comprising at least one of a work order ID and a scheduled time for executing the at least one work order.

16. The system (102) of claim 14, wherein the application module (114) is configured to: receive a device registration request from the user equipment (108); perform a registration of the user equipment (108), wherein upon performing registration of the user equipment, the application module (114) is further configured to store device details comprising the device ID of the user equipment (108) in the device detail table (302).

17. A user equipment (108) for receiving real-time push notifications, the user equipment (108) configured to: receive a messaging key from a messaging module (112);send a device registration request to an application module (114), wherein upon detecting a schedule of a work order corresponding to the user equipment (108) in a work order table (404), a reporting module (106) configured to: retrieve the messaging key from a device detail table (302); and forward the retrieved messaging key to the messaging module (112); and the messaging module (112) configured to communicate a push notification to the user equipment (108) corresponding to the retrieved messaging key; and receive the push notification from the messaging module (112), wherein the push notification indicates reception of the at least one work order.

18. The user equipment (108) of claim 17, wherein the user equipment (108) configured to receive the messaging key from the messaging module (112) upon launching of an application on the user equipment (108).

19. A computer program product comprising a non- transitory computer- readable medium having stored thereon computer-executable instructions that, when executed by a processor, cause the processor to perform method (500) for triggering real-time push notifications corresponding to at least one work order, the method (500) comprising: receiving (502), by an application module (114), at least one work order creation request from a network management platform (402) based on one or more factors,creating (504), by the application module (114), at least one work order corresponding to the at least one work order request; storing (506), by the application module (114), the at least one created work order in a work order table (404); running (508), by a reporting module (106), a scheduler to periodically fetch the at least one work order from the work order table (404); analyzing (510), by the reporting module (106), the at least one fetched work order; based on analysis, retrieving (512), by the reporting module (106), a messaging key from a device detail table (302); forwarding (514), by the reporting module (106), the retrieved messaging key to the messaging module (112); and triggering (516), by the messaging module (112), a push notification to the user equipment (108) corresponding to the retrieved messaging key, wherein the push notification indicates reception of the at least one work order.

Images