Work order processing reminding method and device and electronic equipment

Abstract

The embodiment of the invention provides a work order processing reminding method and device and electronic equipment. The method comprises the following steps: firstly, responding to a query request, acquiring an unprocessed work order from a plurality of business processing work orders, then analyzing the unprocessed work order, and determining at least one target reminded object and target work order reminding information of the unprocessed work order, finally, according to a preset pushing strategy, the target work order reminding information is pushed to at least one target reminded object, and the pushing strategy is jointly determined based on the first priority sequence of the work order reminding information received by the level of the at least one reminded object and the second priority sequence of the at least one reminding mode. According to the method provided by the invention, the work order reminding information is pushed to the target reminded object, and the work order processing efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus and electronic device for reminding users of work order processing. Background Technology

[0002] As cybersecurity becomes increasingly severe, the pressure on enterprise service personnel for emergency repairs, monitoring, and surveillance is intensifying. When enterprises initiate "network protection operations," they will be unable to use external network applications or devices, severely impacting normal business operations. Customer requests requiring immediate response often experience delays, leading to problems such as untimely processing, delayed responses, and low service efficiency. Therefore, it is necessary to remind enterprise service personnel to handle customer requests promptly upon receiving their work orders.

[0003] Currently, reminders for work order processing typically require access to external databases, voice libraries, physical telephones, dialing devices, etc., and reminders are sent to enterprise service personnel through login applications and voice dialing tools to ensure timely work order processing.

[0004] However, existing work order reminder methods are limited, experiencing issues such as dial-up congestion and reminder delays. Furthermore, these methods lack operational flexibility for emergency repair personnel, leading to low work order processing efficiency. Therefore, developing a safer, more efficient, and more widely applicable work order reminder method is an urgent problem to be solved. Summary of the Invention

[0005] This application provides a method, apparatus, and electronic device for reminding users of work orders, in order to improve the efficiency of work order processing.

[0006] In a first aspect, embodiments of this application provide a method for reminding users of work order processing, including:

[0007] In response to the query request, unprocessed work orders are retrieved from multiple business processing work orders;

[0008] The unprocessed work orders are parsed to determine at least one target notification object and target work order notification information for the unprocessed work orders, wherein the at least one target notification object has a different level;

[0009] According to a preset push strategy, the target work order reminder information is pushed to the at least one target reminder object. The push strategy is determined by the first priority order of receiving work order reminder information corresponding to the level of the at least one reminder object and the second priority order of at least one reminder method.

[0010] In one or more embodiments, the first priority order includes at least one from high to low: direct object level, first object level, and second object level; the second priority order includes at least one from high to low: SMS, telephone, and voice.

[0011] Accordingly, the step of pushing the target work order reminder information to the at least one target reminder recipient according to a preset push strategy includes:

[0012] The target work order reminder information is pushed to the target reminder object corresponding to the target direct object level in the second priority order according to the reminder method, until any reminder method is successfully pushed;

[0013] If the push to the target reminder objects corresponding to the target direct object level fails, the target work order reminder information will be pushed to the target reminder objects corresponding to the target first object level in the second priority order according to the reminder method in the second priority order, until any reminder method is successfully pushed.

[0014] If the notification to the target objects corresponding to the first target object level fails to be pushed, the target work order notification information will be pushed to the target objects corresponding to the second target object level in sequence according to the notification method in the second priority order, until any one of the notification methods is successfully pushed.

[0015] In one or more embodiments, the at least one notification method includes: SMS, telephone, and voice;

[0016] Accordingly, the target work order reminder information is pushed sequentially according to the reminder methods in the second priority order until any reminder method is successfully pushed, including:

[0017] The target work order reminder information is pushed as an SMS reminder. If feedback is received within a first preset time period, it is determined that the SMS reminder was successfully pushed.

[0018] If the feedback notification is not received within the first preset time period, it is determined that the SMS reminder method has failed to be pushed, and the target work order reminder information is pushed by telephone. If the telephone is hung up within the second preset time period, it is determined that the telephone reminder method has been successfully pushed.

[0019] If the call is answered within the second preset time period, the target work order reminder information will be pushed out as a voice reminder, then the call reminder will be considered successfully pushed out.

[0020] In one or more embodiments, the method further includes:

[0021] If the call is not connected within the second preset time period, continue dialing the preset number of times until the call is connected or hung up.

[0022] If the dialing continues for the preset number of times without being connected, the push notification is considered to have failed.

[0023] In one or more embodiments, the step of parsing the unprocessed work order to determine at least one target notification object and target work order notification information for the unprocessed work order includes:

[0024] The unprocessed work orders are parsed to obtain their basic information.

[0025] For each reminder method, the basic information is generated and processed according to the reminder method to obtain the target work order reminder information corresponding to the reminder method;

[0026] The at least one target to be reminded and the level of the at least one target to be reminded are identified in the contact field of the basic information.

[0027] In one or more embodiments, the step of retrieving unprocessed work orders from multiple business processing work orders in response to a query request includes:

[0028] In response to the query request, at least one query item in the query request is retrieved;

[0029] Obtain the target business processing work order that contains at least one query item from the plurality of business processing work orders;

[0030] The target business processing work order is identified as the unprocessed work order.

[0031] In one or more embodiments, the step of retrieving unprocessed work orders from multiple business processing work orders in response to a query request includes:

[0032] In response to a user's login request, the system retrieves the login credentials corresponding to the user's level from the intranet server. These login credentials are used to indicate that the user's authentication has been successful.

[0033] In response to the query request, the unprocessed work order is retrieved from multiple business processing work orders in the intranet server;

[0034] A firewall is installed between the communication link between the intranet server and the extranet device.

[0035] In one or more embodiments, before retrieving unprocessed work orders from multiple business processing work orders in response to a query request, the method further includes:

[0036] In response to a work order return operation from another device, the returned work order corresponding to the work order return operation is obtained, and the returned work order carries a record identifier of the returned work order;

[0037] Add the returned work order to the multiple business processing work orders.

[0038] Secondly, embodiments of this application provide a work order processing reminder device, comprising:

[0039] The retrieval module is used to respond to query requests and retrieve unprocessed work orders from multiple business processing work orders;

[0040] The processing module is used to parse and process the unprocessed work orders, determine at least one target reminder object and target work order reminder information of the unprocessed work orders, wherein the at least one target reminder object has a different level;

[0041] The push module is used to push the target work order reminder information to the at least one target reminder object according to a preset push strategy. The push strategy is determined by the first priority order of receiving work order reminder information corresponding to the level of the at least one reminder object and the second priority order of at least one reminder method.

[0042] In one or more embodiments, the first priority order includes at least one from high to low: direct object level, first object level, and second object level; the second priority order includes at least one from high to low: SMS, telephone, and voice.

[0043] Accordingly, according to a preset push strategy, the target work order reminder information is pushed to at least one target reminder recipient. Specifically, the push module is used for:

[0044] The target work order reminder information is pushed to the target reminder object corresponding to the target direct object level in the second priority order according to the reminder method, until any reminder method is successfully pushed;

[0045] If the push to the target reminder objects corresponding to the target direct object level fails, the target work order reminder information will be pushed to the target reminder objects corresponding to the target first object level in the second priority order according to the reminder method in the second priority order, until any reminder method is successfully pushed.

[0046] If the notification to the target objects corresponding to the first target object level fails to be pushed, the target work order notification information will be pushed to the target objects corresponding to the second target object level in sequence according to the notification method in the second priority order, until any one of the notification methods is successfully pushed.

[0047] In one or more embodiments, the at least one notification method includes: SMS, telephone, and voice;

[0048] Accordingly, the target work order reminder information is pushed sequentially according to the reminder methods in the second priority order until any reminder method is successfully pushed. The push module is specifically used for:

[0049] The target work order reminder information is pushed as an SMS reminder. If feedback is received within a first preset time period, it is determined that the SMS reminder was successfully pushed.

[0050] If the feedback notification is not received within the first preset time period, it is determined that the SMS reminder method has failed to be pushed, and the target work order reminder information is pushed by telephone. If the telephone is hung up within the second preset time period, it is determined that the telephone reminder method has been successfully pushed.

[0051] If the call is answered within the second preset time period, the target work order reminder information will be pushed out as a voice reminder, then the call reminder will be considered successfully pushed out.

[0052] In one or more embodiments, the push module is further configured to:

[0053] If the call is not connected within the second preset time period, continue dialing the preset number of times until the call is connected or hung up.

[0054] If the dialing continues for the preset number of times without being connected, the push notification is considered to have failed.

[0055] In one or more embodiments, the step of parsing the unprocessed work order to determine at least one target notification object and target work order notification information for the unprocessed work order, the processing module is specifically used for:

[0056] The unprocessed work orders are parsed to obtain their basic information.

[0057] For each reminder method, the basic information is generated and processed according to the reminder method to obtain the target work order reminder information corresponding to the reminder method;

[0058] The at least one target to be reminded and the level of the at least one target to be reminded are identified in the contact field of the basic information.

[0059] In one or more embodiments, the acquisition module is specifically used for:

[0060] In response to the query request, at least one query item in the query request is retrieved;

[0061] Obtain the target business processing work order that contains at least one query item from the plurality of business processing work orders;

[0062] The target business processing work order is identified as the unprocessed work order.

[0063] In one or more embodiments, the step of retrieving unprocessed work orders from multiple business processing work orders in response to a query request, wherein the retrieval module is specifically used for:

[0064] In response to a user's login request, the system retrieves the login credentials corresponding to the user's level from the intranet server. These login credentials are used to indicate that the user's authentication has been successful.

[0065] In response to the query request, the unprocessed work order is retrieved from multiple business processing work orders in the intranet server;

[0066] A firewall is installed between the communication link between the intranet server and the extranet device.

[0067] In one or more embodiments, before retrieving unprocessed work orders from multiple business processing work orders in response to a query request, the retrieval module is further configured to:

[0068] In response to a work order return operation from another device, the returned work order corresponding to the work order return operation is obtained, and the returned work order carries a record identifier of the returned work order;

[0069] Add the returned work order to the multiple business processing work orders.

[0070] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0071] The memory stores computer-executed instructions;

[0072] The processor executes computer execution instructions stored in the memory, such that the processor, when executed, is used to implement the method described in the first aspect and any of the embodiments above.

[0073] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the methods described in the first aspect and any of the embodiments above.

[0074] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, is used to implement a work order processing reminder method as described in the first aspect and various possible implementations of the first aspect.

[0075] This application provides a method, apparatus, and electronic device for reminding users of work order processing. The method first responds to a query request by retrieving unprocessed work orders from multiple business processing work orders. Then, it parses and processes these unprocessed work orders to determine at least one target recipient and target work order reminder information. The at least one target recipient has a different level. Finally, according to a preset push strategy, the target work order reminder information is pushed to the at least one target recipient. The push strategy is determined based on a first priority order for receiving work order reminder information corresponding to the level of the at least one recipient, and a second priority order for at least one reminder method. In the above method, unprocessed work orders are automatically queried through query requests and parsed, which can efficiently filter out work orders that need to be processed from a large number of work orders. Based on the level of at least one target notification object of the unprocessed work order and the first priority order of receiving work order notification information according to the level of at least one notification object, work order notification information can be pushed according to the first priority order, ensuring that work order notification information is pushed in order of priority and guaranteeing the timeliness of work order notification. Different notification methods have different priorities, and notifications can be pushed according to the priority order of the notification methods to avoid the problem of delayed processing due to the failure to push the target work order notification information in a timely manner. Attached Figure Description

[0076] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0077] Figure 1 A flowchart illustrating the work order processing reminder method provided in this application embodiment. Figure 1 ;

[0078] Figure 2 A flowchart illustrating the work order processing reminder method provided in this application embodiment. Figure 2 ;

[0079] Figure 3 A flowchart illustrating the work order processing reminder method provided in this application embodiment. Figure 3 ;

[0080] Figure 4 A flowchart illustrating the work order processing reminder method provided in this application embodiment. Figure 4 ;

[0081] Figure 5 A flowchart illustrating the work order processing reminder method provided in this application embodiment. Figure 5 ;

[0082] Figure 6A flowchart illustrating the work order processing reminder method provided in this application embodiment. Figure 6 ;

[0083] Figure 7 A flowchart illustrating the work order processing reminder method provided in this application embodiment. Figure 7 ;

[0084] Figure 8 A schematic diagram of the structure of the work order processing reminder device provided in the embodiments of this application;

[0085] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0086] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0087] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0088] Before introducing the embodiments of this application, the application background of the embodiments of this application will be explained first:

[0089] As cybersecurity becomes increasingly severe, the pressure on enterprise service personnel for emergency repairs, monitoring, and surveillance is intensifying. When enterprises initiate "network protection operations," they are unable to use external network applications or devices, severely impacting normal business operations. To ensure that enterprises can respond to unexpected customer needs in a timely manner and improve customer satisfaction and service quality, service personnel need to respond quickly upon receiving customer requests. However, due to the ever-increasing workload of work order processing, the pressure on enterprise service personnel has significantly increased, often leading to delays in response and processing, resulting in a series of problems such as untimely processing, response delays, and low service efficiency. Therefore, it is necessary to remind enterprise service personnel to handle customer requests promptly upon receipt of work orders.

[0090] Currently, reminders for work order processing typically require access to external databases, voice libraries, physical telephones, dialing devices, etc., and reminders are sent to enterprise service personnel through login applications and voice dialing tools so that attacks can be dealt with in a timely manner.

[0091] However, existing work order reminder methods are limited, experiencing issues such as dial-up congestion and reminder delays. Furthermore, these methods lack operational flexibility for emergency repair personnel, leading to low work order processing efficiency. Therefore, developing a safer, more efficient, and more widely applicable work order reminder method is an urgent problem to be solved.

[0092] The work order processing reminder method provided in this application aims to solve the above-mentioned technical problems of the prior art. The inventive concept of this application is as follows: Addressing the limitations of existing work order reminder methods, this application pushes target work order reminder information to the target recipient through at least one reminder method, enabling a combination of multiple reminder methods for work order processing reminders. Through a preset push strategy, based on a first priority order for receiving work order reminder information according to the level of at least one recipient and a second priority order of at least one reminder method, the method accurately provides escalation reminders for work order processing to recipients at different levels, thereby enabling timely processing of work orders.

[0093] The execution subject of this application embodiment is an electronic device, which can be a terminal device, such as a laptop, desktop computer, or tablet computer, or a server. In practical applications, whether the electronic device is a terminal device or a server can be determined according to the actual situation, and no specific limitation is imposed on it.

[0094] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0095] Figure 1 A flowchart illustrating the work order processing reminder method provided in this application embodiment. Figure 1 .like Figure 1 As shown, the reminder method for processing this work order includes the following steps:

[0096] S110. In response to the query request, retrieve the unprocessed work orders from multiple business processing work orders.

[0097] In this step, a response is made to the query request, the query information contained in the query request is analyzed, and the query is performed in multiple business processing work orders according to the query information contained in the query request to obtain the unprocessed work orders.

[0098] For example, a query request is used to instruct the filtering of multiple business processing work orders to obtain unprocessed work orders.

[0099] For example, a query request may contain at least one query item, such as the time the work order was generated, the region to which the work order belongs, and the type of work order.

[0100] In one possible implementation, step S110 may further include the following steps:

[0101] Step 1: In response to the user's login request, obtain the login credentials corresponding to the user's level from the intranet server;

[0102] The login credentials are used to indicate whether the user has been authenticated.

[0103] In one possible implementation, in response to a user's login request, a request for web page login from the Python request library is sent to the internal network server to automatically request access to the internal network login page provided by the server. Simultaneously, the Selenium automated testing tool is used to simulate a user logging into the internal network login page provided by the server.

[0104] For example, an intranet server contains work order information that can be accessed by different user levels. This means setting access permissions so that specific content in the work order information can only be accessed and processed by authorized personnel.

[0105] Correspondingly, the login credentials returned by the intranet server vary depending on the user's level of login request; that is, the returned login credentials correspond to the user's level when logging into the intranet server.

[0106] In one possible implementation, the intranet server also stores information on users allowed to log in. When an automatic request is made to access the intranet login page provided by the intranet server, the intranet server matches the user who sent the login request against the stored information on users allowed to log in.

[0107] If the match fails, it means that the user does not have permission to log in to the intranet server and cannot simulate logging in to the intranet server.

[0108] If the match is successful, it means that the user has permission to log in to the intranet server. The login credentials corresponding to the user's level can be obtained from the intranet server. Based on the login credentials, the user can be instructed to pass authentication, thereby realizing automatic login to the intranet server and simulating the user sending query requests based on the intranet server.

[0109] Step 2: In response to the query request, retrieve the unprocessed work orders from multiple business processing work orders in the intranet server.

[0110] A firewall is installed between the internal network server and the external network device communication link.

[0111] In one possible implementation, after the user is authenticated and successfully simulates logging into the intranet server, they can simulate performing operations such as clicking on the visual operation components on the intranet operation page provided by the intranet server, scrolling the intranet operation page window, etc., to access the intranet server. By clicking on the visual operation components on the intranet operation page, they can access the intranet server and obtain multiple business processing work orders stored in the intranet server.

[0112] For example, a firewall is set up between the communication link between the intranet server and the external network device. When the intranet server actively transmits information to the external network device, and / or the external network device requests information transmission from the intranet server, the firewall set up between the intranet server and the external network device will intercept the information transmission, verify the information transmission permission, and prevent the external network device from accessing the information abnormally.

[0113] In one possible implementation, a firewall is also provided between the communication link between the intranet server and the electronic device corresponding to the execution subject of this application embodiment, in order to verify the information transmission permission and ensure the security of information transmission when information is transmitted between the intranet server and the electronic device corresponding to the execution subject of this application embodiment.

[0114] Furthermore, intranet servers and electronic devices have different hardware configurations. Depending on the different functional implementations and task requirements, the hardware configuration requirements for intranet servers and electronic devices vary. The work order processing reminder method provided in this embodiment can be executed normally based on intranet servers and electronic devices with lower hardware configurations. For example, the lower hardware configuration of intranet servers and electronic devices can meet the needs of users to simulate logging into the intranet server and performing operations on the intranet operation page provided by the intranet server, and information can be transmitted between the intranet server and the electronic device.

[0115] In one possible implementation, Figure 2 A flowchart illustrating the work order processing reminder method provided in this application embodiment. Figure 2 .like Figure 2 As shown, prior to step S110 above, the reminder method for processing this work order also includes:

[0116] S1. In response to work order return operations from other devices, obtain the return work order corresponding to the work order return operation;

[0117] The returned work order contains a record indicating that it has been returned.

[0118] For example, other devices can perform work order return operations, and in response to the work order return operation of other devices, a return work order carrying a record identifier of the returned work order can be obtained.

[0119] The returned record identifier can identify returned work orders among multiple business processing work orders, distinguishing between unprocessed work orders and returned work orders among multiple business processing work orders.

[0120] In one possible implementation, the work order information includes the identifier of the target push device, which is used to indicate that the work order should be pushed to the target push device.

[0121] When a work order is pushed to other devices, those devices verify the work order, determine the target pushing device based on the work order information, and then perform a work order return operation.

[0122] For example, when work order T1 is pushed to another device A, the other device A verifies work order T1, determines the target pushing device B of work order T based on the construction site information, adds a return record identifier to work order T1, and performs a construction site return operation to obtain a returned work order T2.

[0123] S2. Add the returned work order to multiple business processing work orders.

[0124] In one possible implementation, if a returned work order requires another push notification, the returned work order can be added to multiple business processing work orders for further processing.

[0125] In one possible implementation, when a return work order carrying the identifier of the returned record is added to multiple business processing work orders and a push notification is sent again, and subsequently successfully pushed to the target push device, a notification that the return work order has been successfully pushed can be sent to other devices corresponding to the work order return operation that executed the return work order.

[0126] For example, based on the above example, the returned work order T2 can be added to multiple business processing work orders for further processing. When the returned work order T2 is successfully pushed to the target push device B, an SMS reminder can be sent to other devices A that "Work order T1 has been successfully reassigned and processed".

[0127] S120. Parse and process the unprocessed work orders to determine at least one target notification object and target work order notification information for the unprocessed work orders;

[0128] In this case, at least one of the targets is alerted at a different level.

[0129] In this step, the unprocessed work order carries the identifier of at least one target object to be reminded, the level of at least one target object to be reminded, and the target work order reminder information. The unprocessed work order is parsed and processed. Based on the identifier of at least one target object to be reminded, the at least one target object to be reminded in the unprocessed work order is determined, as well as the level of at least one target object to be reminded and the target work order reminder information.

[0130] For example, the target work order reminder information includes text reminders, ringing reminders, and voice reminders.

[0131] In one possible implementation, an unprocessed work order includes at least one target reminder object and at least one level of the target reminder object. The unprocessed work order can be directly parsed to determine this level. To determine the target work order reminder information for an unprocessed work order, it is necessary to parse the unprocessed work order to obtain its basic information and generate the target reminder information for the unprocessed work order based on this basic information.

[0132] S130. According to the preset push strategy, push the target work order reminder information to at least one target reminder recipient;

[0133] The push strategy is determined by the first priority order of receiving work order reminder information corresponding to the level of at least one reminded object, and the second priority order of at least one reminder method.

[0134] In this step, the priority order for receiving work order reminder information differs depending on the level of the reminded object, and the priority order also differs depending on the reminder method. The push strategy can be jointly determined based on the first priority order for receiving work order reminder information at least one level of the reminded object and the second priority order of at least one reminder method. According to the preset push strategy, the target work order reminder information corresponding to at least one reminder method can be pushed to at least one target reminded object according to the first priority order for receiving work order reminder information at least one level of the reminded object and the second priority order of at least one reminder method.

[0135] In one possible implementation, the target work order reminder information may differ depending on the reminder method. If the reminder method is SMS, the corresponding target work order reminder information will be in text format. If the reminder method is telephone, the corresponding target work order reminder information will be in ringtone format. If the reminder method is voice reminder, the corresponding target work order reminder information will be in voice format.

[0136] For example, the target work order reminder information corresponding to the SMS reminder can be generated based on a preset text-based reminder information template.

[0137] For example, a text-based reminder message template could be: "(Target recipient), Hello! You have a work order pending processing. The user reported an issue of type (work order type) in (work order region). (Work order processing details), please coordinate and handle it promptly."

[0138] The basic information of an unprocessed work order may include a tag indicating its urgency level. If a pending work order contains a tag indicating high urgency, the corresponding text-based reminder message template could be: "(Target Reminder), Hello! You have a pending work order. The user requests urgent processing, involving a (work order type) issue. The user reports that (work order processing content) occurred in (work order region). Please coordinate and process it promptly."

[0139] For example, if a high-urgency issue such as an emergency power outage or elevator entrapment occurs in area Q, the corresponding pending work order with a "high urgency" tag will generate a text-based reminder message: "Hello, repair technician! You have a pending work order. The user requests urgent handling of an emergency repair issue. The user reports that an elevator is entrapped in area Q. Please coordinate and handle this promptly."

[0140] A ringing notification can be used to send a ringing reminder.

[0141] Voice notifications can be text-based notifications generated from the target work order notification information corresponding to the SMS notification and converted into voice notifications.

[0142] In one possible implementation, the push results of pushing target work order reminder information to at least one target reminded object can be recorded and stored in an Excel file. The recorded Excel file is then archived and saved in an offline storage space. The recorded Excel file can be accessed at any time without a network connection for subsequent parsing and analysis. At the same time, saving the recorded Excel file in an offline storage space can effectively prevent abnormal access from external networks and ensure the security of file data.

[0143] For example, the push result may include whether the target work order reminder information was successfully pushed to at least one target reminded object. If the push was successful, the push result may also include the push duration of the target work order reminder information being pushed to at least one target reminded object.

[0144] The work order processing reminder method provided in this application first responds to a query request by obtaining unprocessed work orders from multiple business processing work orders. Then, it parses and processes the unprocessed work orders to determine at least one target reminder object and target work order reminder information for the unprocessed work orders. The at least one target reminder object has a different level. Finally, according to a preset push strategy, the target work order reminder information is pushed to the at least one target reminder object. The push strategy is jointly determined based on the first priority order of receiving work order reminder information corresponding to the level of the at least one reminder object and the second priority order of at least one reminder method. In this embodiment, unprocessed work orders are automatically queried through query requests, and these unprocessed work orders are parsed to efficiently filter out the work orders that need to be processed from a large number of work orders. Based on the first priority order of receiving work order reminder information according to the level of at least one target reminder object of the unprocessed work order, work order reminder information can be pushed according to the first priority order, ensuring that work order reminder information is pushed in order of priority and guaranteeing the timeliness of work order reminders. Different reminder methods have different priorities, and reminders can be sent according to the priority order of the reminder methods to avoid delays in processing due to the untimely delivery of target work order reminder information.

[0145] Based on the above embodiments, Figure 3 A flowchart illustrating the work order processing reminder method provided in this application embodiment. Figure 3 .like Figure 3 As shown, the first priority order includes at least one from high to low: direct object level, first object level, and second object level; the second priority order includes at least one from high to low: SMS, telephone, and voice; correspondingly, a possible implementation of the above step S130 also includes the following steps:

[0146] S310. Push the target work order reminder information to the target reminder objects corresponding to the target direct object level in the second priority order according to the reminder method, until any reminder method is successfully pushed.

[0147] In this step, the reminder methods in the second priority order include at least one from high to low: SMS, telephone, and voice. The target work order reminder information is then pushed to the target reminder object corresponding to the target direct object level in the order of SMS, telephone, and voice.

[0148] For example, the direct object level could be the direct contact person who processes the target work order based on the target reminder information, such as a repair technician.

[0149] In one possible implementation, the target work order reminder information is pushed to the target reminder object corresponding to the target direct object level via SMS. If the push is successful, the next step is executed; if unsuccessful, it is pushed to the target reminder object corresponding to the target direct object level via telephone. If the push is successful, the next step is executed; if unsuccessful, it is pushed to the target reminder object corresponding to the target direct object level via voice.

[0150] S320. If the push to the target reminder objects corresponding to the direct object level of the target fails, the target work order reminder information will be pushed to the target reminder objects corresponding to the first object level of the target in the second priority order according to the reminder method, until any reminder method is successfully pushed.

[0151] In this step, if it is unsuccessful to push the notification to the target recipients at the direct object level, the target work order notification information will be pushed to the target recipients at the first object level in the order of SMS, telephone, and voice.

[0152] For example, the first object level can be the contact person above the direct object level contact person who processes the target work order based on the target reminder information, such as the station manager of the emergency repair team.

[0153] For example, if the target work order reminder information is not successfully sent to the emergency repair technician in the order of SMS, telephone, and voice, the target work order reminder information should be sent to the station manager of the emergency repair team in the same order.

[0154] S330. If the push to the target reminder objects corresponding to the first target object level fails, the target work order reminder information is pushed to the target reminder objects corresponding to the second target object level in the order of the second priority according to the reminder method, until any reminder method is successfully pushed.

[0155] For example, the second object level can be the contact person above the first object level who processes the target work order based on the target reminder information, such as the director of the emergency repair station.

[0156] In one possible implementation, reminders are pushed sequentially according to the second priority order, i.e., reminders are sent in the order of SMS, telephone, and voice, which is the default reminder setting. The reminder methods can also be customized according to different object levels. For example, if the reminder method is set to SMS and telephone for the direct object level, the target work order reminder information will be pushed to the target reminded object corresponding to the direct object level according to the SMS and telephone reminder methods. If the reminder method is set to SMS for the first object level, the target work order reminder information will only be pushed to the target reminded object corresponding to the first object level according to the SMS reminder method.

[0157] In one possible implementation, at least one notification method includes: SMS, telephone, and voice; correspondingly, the target work order notification information is pushed sequentially according to the notification methods in the second priority order until any notification method is successfully pushed, including:

[0158] Step 1: Send the target work order reminder information via SMS. If feedback is received within the first preset time period, the SMS reminder has been successfully sent.

[0159] For example, the first preset duration is used to indicate the maximum waiting time for determining that the SMS reminder has been successfully sent after the target work order reminder information has been sent via SMS.

[0160] The feedback message is used to indicate that the SMS notification was successfully sent. When the SMS is read within the first preset time period, a feedback message will be sent, such as "SMS has been read".

[0161] In one possible implementation, when reading SMS messages within a first preset time period, the text-based reminder information corresponding to the SMS reminder method can be simultaneously converted into a voice-based reminder information and pushed out as a voice reminder.

[0162] Step 2: If no feedback is received within the first preset time period, the SMS reminder method is deemed to have failed. The target work order reminder will then be sent via telephone. If the call is disconnected within the second preset time period, the telephone reminder method is deemed to have succeeded.

[0163] For example, the terminal corresponding to the target being reminded can be a mobile phone terminal with call function, and the second preset duration is used to indicate the maximum waiting time for confirming the successful push of the call reminder after the target work order reminder information is pushed by telephone.

[0164] In one possible implementation, pushing the target work order reminder information as a telephone reminder can be done by dialing the terminal corresponding to the target reminder object. The terminal corresponding to the target reminder object will ring and display "XX Bureau Emergency Repair Reminder Assistant" on the terminal's display page.

[0165] If the call is disconnected within the second preset time period, i.e. the call is rejected, it can mean that the target work order reminder information has been pushed to the recipient via SMS, or that the target recipient has received the target work order reminder information, confirming that the call reminder method was successfully pushed.

[0166] Step 3: If the call is answered within the second preset time period, the target work order reminder information will be pushed out as a voice reminder, thus confirming that the call reminder was successfully pushed out.

[0167] In one possible implementation, the call is connected within a second preset time period, and the target work order reminder information is pushed out in the form of a voice reminder, that is, the reminder information is played in the form of a voice message.

[0168] The Pygame game development library in Python can be used to play voice-based reminders. A Virtual Audio Cable (VAC) tool can be used to transmit the voice-based reminders to a virtual audio device, preventing transmission to external devices or networks and thus preventing information leakage. The virtual audio device converts the voice-based reminders into stereo reverberant voice messages, allowing for offline playback without a network connection. The stereo reverberant voice messages are then directly output to a virtual microphone, effectively avoiding the use of physical speakers and preventing environmental noise interference.

[0169] In one possible implementation, the work order processing notification method further includes:

[0170] Step 1: If the call is not connected within the second preset time period, continue dialing the preset number of times until the call is connected or hung up.

[0171] For example, the preset number of dials indicates the maximum number of times a call can be made to the target recipient.

[0172] In one possible implementation, if the call is not connected within a second preset time period, the correctness of the dialed number is determined based on the number information of the target being reminded.

[0173] If the dialed number is correct but the call is not connected, it indicates that the dialing wait timeout has occurred. At this point, click the visual button to hang up the call on the operation page of the simulated intranet system, and simultaneously stop the output of voice reminder messages.

[0174] For example, a second preset duration can be set to 50 seconds. If the call is not connected within 50 seconds after dialing, it is determined that the dialing wait timeout has occurred.

[0175] For example, if the call is not connected, the system continues to dial the target recipient within a preset number of times until the call is connected or disconnected within the preset number of dials.

[0176] For example, you can set the preset number of attempts to 2. If the first call fails, the system will make a second call to the target recipient. If the call is answered or disconnected, the push notification is considered successful. If the call fails, proceed to the next step.

[0177] Step 2: If the call is not connected after dialing the preset number of times, the push notification has failed.

[0178] For example, if the call is not connected after a preset number of attempts, it indicates that the target work order reminder information has not been pushed to the target recipient, confirming the push failure and indicating a fault in the processing of the unprocessed work order.

[0179] In one possible implementation, if the number of dialing attempts fails to connect after a preset number of attempts, a reminder message is sent to the notification device in the production command center. The notification device displays a text message indicating that there is a processing failure for the unprocessed work order on its display page, and plays a music reminder on the audio playback tool in the notification device.

[0180] The work order processing reminder method provided in this application embodiment includes at least one priority order from high to low: direct object level, first object level, and second object level; and at least one priority order from high to low: SMS, telephone, and voice. Accordingly, the target work order reminder information is first pushed sequentially to the target reminded object corresponding to the target direct object level according to the reminder methods in the second priority order, until any one reminder method is successfully pushed. If pushing to the target reminded object corresponding to the target direct object level fails, the target work order reminder information is pushed sequentially to the target reminded object corresponding to the target first object level according to the reminder methods in the second priority order, until any one reminder method is successfully pushed. If pushing to the target reminded object corresponding to the target first object level fails, the target work order reminder information is pushed sequentially to the target reminded object corresponding to the target second object level according to the reminder methods in the second priority order, until any one reminder method is successfully pushed. In this embodiment, by setting different levels of alert recipients and sequentially pushing target work order reminder information according to the reminder methods in the second priority order, the accuracy and priority of work order reminders can be ensured. Furthermore, the escalation of reminders effectively reduces delayed reminders, ensuring that target work orders can be processed in a timely manner. By combining SMS, telephone, and voice reminder methods, the limitations of a single reminder method are overcome. Moreover, by setting a second priority order for reminder methods, the target recipients can be reminded based on different levels of urgency, ensuring that the target work order reminder information is ultimately successfully pushed to the target recipients.

[0181] Based on the above embodiments, Figure 4 A flowchart illustrating the work order processing reminder method provided in this application embodiment. Figure 4 .like Figure 4 As shown, a possible implementation of step S120 above also includes the following steps:

[0182] S410. Parse and process the unprocessed work orders to obtain their basic information.

[0183] In this step, the unprocessed work order carries detailed work order content. The unprocessed work order is parsed to obtain the detailed work order content. The work order identification content and key work order content in the detailed work order content are extracted to obtain the basic information of the unprocessed work order, which is used to identify and process the unprocessed work order.

[0184] For example, the basic information of an unprocessed work order includes: work order number, work order region, work order type, work order processing content, work order processing address, and contact person field, etc.

[0185] In one possible implementation, the work order number and the region to which the work order belongs can be used to uniquely identify the unprocessed work order, the work order type and the content of work order processing are used to indicate the actual work order processing operation, the work order processing address is used to indicate the actual geographical location of the work order processing, and the contact person field is used to indicate the recipient of the push notification for the work order.

[0186] S420. For each type of reminder, the basic information is generated and processed according to the reminder method to obtain the target work order reminder information corresponding to the reminder method.

[0187] In this step, there are multiple reminder methods, and the target work order reminder information is different for different reminder methods. For each reminder method, the target work order reminder information corresponding to the reminder method is generated based on the basic information of the unprocessed work order.

[0188] In one possible implementation, the notification message in the form of a ringing bell could be a notification to ring the bell.

[0189] The target work order reminder information corresponding to the SMS reminder can be generated based on a preset text-based reminder information template;

[0190] For example, a text-based reminder message template could be: "(Target recipient), Hello! You have a work order pending processing. The user reported an issue of type (work order type) in (work order region). (Work order processing details), please coordinate and handle it promptly."

[0191] The basic information of an unprocessed work order may include a tag indicating its urgency level. If a pending work order contains a tag indicating high urgency, the corresponding text-based reminder message template could be: "(Target Reminder), Hello! You have a pending work order. The user requests urgent processing, involving a (work order type) issue. The user reports that (work order processing content) occurred in (work order region). Please coordinate and process it promptly."

[0192] The voice reminder can be a text-based reminder generated from the target work order reminder information corresponding to the SMS reminder and converted into a voice reminder, or it can be generated from a preset voice reminder template.

[0193] For example, if the basic information includes the area to which the work order belongs (Area B) and the type of work order (line fault), the preset template for the voice reminder message could be "(Area to which the work order belongs) has an issue of type (work order type), please coordinate and handle it in a timely manner." Then, if the content of the basic information is entered into this preset template, the text content corresponding to the generated voice reminder message will be "A line fault has occurred in Area B, please coordinate and handle it in a timely manner."

[0194] In one possible implementation, in an offline environment, the pyttsx3 text-to-speech engine tool from the Python library can be used. The text content corresponding to the generated speech-formatted reminder message can be used as the conversion object of the pyttsx3 text-to-speech engine tool. Based on the text content corresponding to the generated speech-formatted reminder message, speech synthesis can be performed to obtain the speech-formatted reminder message.

[0195] For example, during the process of synthesizing the text content corresponding to the generated voice prompts, the voice settings tool supported by the pyttsx3 text-to-speech engine can be used to set the speech rate, volume, and timbre of the generated voice prompts.

[0196] In addition, the generated voice reminders have incompleteness issues. The voice reminders can be verified by converting them into text reminders and comparing them with the corresponding text content of the generated reminders. If the comparison results are consistent, the voice reminders pass the verification; otherwise, the voice reminders are incomplete and fail the verification.

[0197] S430. Identify at least one target to be reminded and at least one level of the target to be reminded in the contact field of the basic information.

[0198] In this step, the basic information includes a contact field. Based on the contact field, the level of the contact field can be obtained. Then, at least one target to be reminded and at least one level of the target to be reminded can be determined from the contact field of the basic information.

[0199] In one possible implementation, the execution order of step S430 and step S420 above can be replaced. That is, at least one target to be reminded and at least one level of the target to be reminded can be determined first in the contact field of the basic information. Then, for each reminder method, the basic information is generated according to the reminder method to obtain the target work order reminder information corresponding to the reminder method.

[0200] The work order processing reminder method provided in this application first parses unprocessed work orders to obtain their basic information. Then, for each reminder method, the basic information is processed to generate the corresponding target work order reminder information. Finally, at least one target recipient and its level are determined from the contact field of the basic information. In this embodiment, by parsing unprocessed work orders and obtaining their basic information, target work order reminder information for different reminder methods can be generated based on the basic information of the unprocessed work orders. This ensures that each unprocessed work order can be pushed to at least one corresponding target recipient according to its basic information. Through the contact field of the basic information, at least one target recipient and its level can be determined for the unprocessed work order. The order in which different levels receive the target work order reminder information is determined according to the level of the at least one target recipient, which improves the accuracy of work order processing reminders.

[0201] Based on the above embodiments, Figure 5 A flowchart illustrating the work order processing reminder method provided in this application embodiment. Figure 5 .like Figure 5 As shown, a possible implementation of step S110 above also includes the following steps:

[0202] S510. In response to the query request, retrieve at least one query item from the query request.

[0203] In this step, the query request contains at least one query item, and in response to the query request, at least one query item in the query request is retrieved.

[0204] In one possible implementation, at least one query item may include at least one attribute of the business processing work order and the content of at least one attribute of the information to be queried.

[0205] For example, if a business processing work order includes basic information such as work order type, work order generation time, and work order region, then at least one query item in the query request may include at least one of the basic information such as work order type, work order generation time, and work order region.

[0206] For example, a query request could be for work orders of the fault reporting type in region D with a time range of 00:00 to 06:00. In this case, at least one query item in the query request would be: work order generation time, work order region, and work order type.

[0207] S520. Obtain the target business processing work order that has at least one query item from multiple business processing work orders.

[0208] In this step, multiple business processing work orders are matched according to at least one query item to obtain the business processing work orders that have at least one query item among the multiple business processing work orders, and these are identified as the target business processing work orders.

[0209] In one possible implementation, multiple business processing work orders can be matched and filtered according to at least one query item, filtering out business processing work orders that do not have a query item.

[0210] In addition, the uniqueness of a business processing work order can be determined based on the work order number and the region to which the work order belongs. The work orders can then be filtered a second time to delete duplicate work orders that have at least one query item, leaving only one work order.

[0211] After filtering out non-existent query items and duplicate business processing work orders, the target business processing work order with at least one query item is obtained from multiple business processing work orders.

[0212] S530. Determine the target business processing work order as an unprocessed work order.

[0213] In one possible implementation, after determining that the target business processing work order with at least one query item is an unprocessed work order, the work order reminder records included in the business processing work order can be used to help determine whether there is already a push record of work order reminder information for the target business processing work order.

[0214] If there is no record of push notification for the target business processing work order, it means that the target business processing work order needs to be reminded for work order processing, and the target business processing work order is identified as an unprocessed work order.

[0215] The work order processing reminder method provided in this application first responds to a query request by obtaining at least one query item from the query request. Then, it identifies a target business processing work order containing at least one query item from multiple business processing work orders. Finally, it determines the target business processing work order as an unprocessed work order. In this embodiment, by responding to a query request and filtering multiple business processing work orders based on at least one query item in the query request, the efficiency of processing business processing work orders can be improved. By flexibly setting at least one query item in the query request, target business processing work orders that need to be processed can be obtained according to actual business needs and identified as unprocessed work orders, thereby improving overall work efficiency.

[0216] Based on the above embodiments, Figure 6 A flowchart illustrating the work order processing reminder method provided in this application embodiment. Figure 6 .like Figure 6As shown, one possible implementation of the work order processing reminder method includes the following steps:

[0217] S610, simulate login to the intranet server;

[0218] For example, a request from the Python request library is sent to the internal network server to automatically request access to the internal network login page provided by the server. After receiving the login credential cookie returned by the internal network server, automatic login to the internal network server and simulation of a user sending a query request based on the internal network server can be achieved. Simultaneously, the Selenium automated testing tool is used to simulate a user logging into the internal network login page provided by the internal network server.

[0219] In one possible implementation, a preset detection interval can be used to detect the login status of simulated logins to the intranet server.

[0220] For example, you can set a time interval of 1 second to check the login status of the simulated intranet system. When the login status of the simulated intranet system is detected to be offline, the login status will be automatically restored.

[0221] S620: In response to the query request, query and retrieve the unprocessed work order from the intranet server.

[0222] For example, after successfully simulating login to the intranet server, you can click on the visual acquisition operation component on the intranet operation page provided by the intranet server to access the intranet server and obtain multiple business processing work orders stored in the intranet server.

[0223] Based on at least one query item contained in the query request, filter among the multiple business processing work orders obtained to obtain the unprocessed work orders.

[0224] For example, the query items in the query request can be set to include "power supply unit", "fault repair", "non-direct handling", and "work orders that require local business processing from 18:00 yesterday to the present".

[0225] In one possible implementation, clicking the visual loading operation component on the intranet operation page loads the notification records of multiple business processing work orders stored in the intranet server. Business processing work orders with empty notification records are matched as unprocessed work orders, and the attribute information of unprocessed work orders is extracted.

[0226] S630. Parse and process the unprocessed work orders to obtain their basic information.

[0227] For example, the basic information of an unprocessed work order includes: work order number, work order region, work order type, work order processing content, work order processing address, work order notification record, and contact person field, etc.

[0228] In one possible implementation, the work order number and the region to which the work order belongs can be used to uniquely identify the unprocessed work order, and the work order notification record can be used to assist in identifying the unprocessed work order.

[0229] The lxml parsing tool in the Python library can be used to parse each unprocessed work order individually.

[0230] S640. According to the preset push strategy, push the target work order reminder information to at least one target reminder recipient.

[0231] In one possible implementation, the pyautogui tool from the Python library, which automates graphical user interfaces, can be used to simulate mouse and keyboard operations, identify and click on the visual SMS sending component on the intranet operation page provided by the simulated intranet server, and push the target work order reminder information corresponding to the SMS reminder method to at least one target reminder object.

[0232] In one possible implementation, the pyautogui tool from the Python library, which automates the graphical user interface, can be used to identify and click on the visual telephone dialing component on the intranet operation page provided by the simulated intranet server, and push the target work order reminder information corresponding to the telephone reminder method to at least one target reminder object.

[0233] In one possible implementation, the voice playback tool in the Pygame game development library of Python can be used to play the voice-based reminder information. A Virtual Audio Cable (VAC) tool is then used to transmit the voice-based reminder information to a virtual audio device, preventing transmission to external devices or networks and thus preventing leakage. The virtual audio device converts the played voice-based reminder information into a stereo reverb-based message, which can be played offline without relying on a network connection. The stereo reverb-based reminder information is then directly output to a virtual microphone hardware, effectively avoiding playback of the voice-based reminder information through physical speakers and preventing environmental noise interference.

[0234] S650: Based on the push results of the target work order reminder information, determine the work order notification push record and store it in the offline storage space.

[0235] For example, the push results include push success / failure, push duration, and the target notification recipient. The work order notification push records can be read from the logs in the offline storage space.

[0236] In one possible implementation, Figure 7 A flowchart illustrating the work order processing reminder method provided in this application embodiment. Figure 7 .like Figure 7 As shown, the reminder method for processing this work order also includes the following steps:

[0237] S710 monitors multiple business processing work orders stored in the simulated intranet server;

[0238] For example, on the intranet operation page provided by the intranet server, you can click on the visualization to access the query item "fault reporting" for unprocessed work orders.

[0239] S720. Determine whether the processing stage of the unprocessed work order is the "City-level Business Processing" stage; if yes, execute S730; if no, execute S750.

[0240] S730. Match the unprocessed work order number with the notification record to determine whether the unprocessed work order is a new work order; if yes, proceed to S740; if no, proceed to S710.

[0241] S740. Confirm the target recipient of the reminder, i.e. the power supply station that needs to be notified, and push the target work order reminder information according to the preset push strategy. The preset push strategy includes: pushing the target work order reminder information to the target recipient via SMS, and / or pushing the target work order reminder information to the target recipient via telephone.

[0242] S750. Determine the processing stage of the unprocessed work order as the "City-level Request Review" processing stage;

[0243] S760. Match the unprocessed work order number with the notification record to determine whether the unprocessed work order is a new work order; if yes, proceed to S740; if no, proceed to S780.

[0244] S770. Confirm the target recipient of the reminder, i.e. the power supply station that needs to be notified, and push the target work order reminder information according to the preset push strategy. The preset push strategy includes: pushing the target work order reminder information to the target recipient via SMS, and / or pushing the target work order reminder information to the target recipient via telephone.

[0245] S780. If the unprocessed work order is determined to be a reassignment work order, the unprocessed work order shall be returned to the "City-level Request Review" processing stage and retransmitted to the correct target reminder object. The unprocessed work order shall be verified and the target reminder object shall be confirmed. The target reminder object includes the first target reminder object before the reassignment and the second target reminder object after the reassignment carried in the reassignment work order.

[0246] According to the preset push strategy, the target work order reminder information is pushed to the second target reminder object after reassignment. The preset push strategy includes: pushing the target work order reminder information to the target reminder object via SMS, and / or pushing the target work order reminder information to the target reminder object via telephone call.

[0247] The target work order reminder message is pushed to the first target recipient via SMS to indicate that the unprocessed "fault repair" work order has been successfully reassigned by the first target recipient to the second target recipient for follow-up.

[0248] as well as:

[0249] Following S740 and S780, the following is also executed:

[0250] S790: Record the push process of unprocessed work orders and generate notification records.

[0251] For example, the push results of pushing target work order reminder information to at least one target reminded object can be recorded. The push results can be recorded in an Excel file and stored in offline storage space, which can effectively prevent abnormal access from external networks and ensure the security of file data.

[0252] The work order processing reminder method provided in this application automatically queries unprocessed work orders through query requests and parses them to efficiently filter out work orders that need to be processed. After parsing and processing the unprocessed work orders, the target reminder type and target reminder object are clearly defined, which can ensure that the target work order reminder information is targeted and accurate and can effectively avoid irrelevant reminder information. Through a preset push strategy, different target work order reminder information can be pushed to the target reminder object according to different target reminder types, ensuring the timely delivery of target work order reminder information.

[0253] Based on the above embodiments, the following is a work order processing reminder device provided in this embodiment, which can execute the method provided in the above method embodiments.

[0254] Figure 8 This is a schematic diagram of the work order processing reminder device provided in an embodiment of this application. Figure 8 As shown, the work order processing reminder device 800 includes:

[0255] The acquisition module 810 is used to retrieve unprocessed work orders from multiple business processing work orders in response to query requests;

[0256] The processing module 820 is used to parse and process unprocessed work orders, determine at least one target reminder object and target work order reminder information of the unprocessed work order, wherein at least one target reminder object has a different level;

[0257] The push module 830 is used to push target work order reminder information to at least one target reminder object according to a preset push strategy. The push strategy is determined by the first priority order of receiving work order reminder information based on the level of at least one reminder object and the second priority order of at least one reminder method.

[0258] In one or more embodiments, the first priority order includes at least one from high to low: direct object level, first object level, and second object level; the second priority order includes at least one from high to low: SMS, telephone, and voice.

[0259] Accordingly, based on the preset push strategy, the target work order reminder information is pushed to at least one target recipient. The push module 830 is specifically used for:

[0260] The target work order reminder information is pushed to the target reminder objects at the target direct object level in the second priority order according to the reminder method, until any reminder method is successfully pushed;

[0261] If the push to the target reminder objects corresponding to the direct object level of the target fails, the target work order reminder information will be pushed to the target reminder objects corresponding to the first object level of the target in the second priority order according to the reminder method, until any reminder method is successfully pushed.

[0262] If the notification fails to be pushed to the target objects corresponding to the first object level, the target work order notification information will be pushed to the target objects corresponding to the second object level in the order of the second priority, until any one of the notification methods is successfully pushed.

[0263] In one or more embodiments, at least one notification method includes: SMS, telephone, and voice;

[0264] Accordingly, the target work order reminder information is pushed sequentially according to the reminder methods in the second priority order until any reminder method is successfully pushed. The push module 830 is specifically used for:

[0265] The target work order reminder information is pushed via SMS. If feedback is received within the first preset time period, the SMS reminder is considered to have been successfully pushed.

[0266] If no feedback is received within the first preset time period, the SMS reminder method is deemed to have failed, and the target work order reminder information will be sent via telephone. If the telephone call is disconnected within the second preset time period, the telephone reminder method is deemed to have succeeded.

[0267] If the call is answered within the second preset time period, the target work order reminder information will be pushed out via voice reminder, thus confirming that the call reminder was successfully pushed out.

[0268] In one or more embodiments, the push module 830 is further configured to:

[0269] If the call is not connected within the second preset time period, continue dialing the preset number of times until the call is connected or hung up.

[0270] If the dialing continues for the preset number of times without being connected, the push notification is considered to have failed.

[0271] In one or more embodiments, unprocessed work orders are parsed to determine at least one target notification object and target work order notification information for the unprocessed work orders. The processing module 820 is specifically used for:

[0272] The unprocessed work orders are parsed and processed to obtain their basic information.

[0273] For each type of reminder, the basic information is generated and processed according to the reminder method to obtain the target work order reminder information corresponding to the reminder method;

[0274] Identify at least one target to be reminded and the level of at least one target to be reminded in the contact field of the basic information.

[0275] In one or more embodiments, the acquisition module 810 is specifically used for:

[0276] In response to a query request, retrieve at least one query item from the query request;

[0277] Retrieve the target business processing work order that contains at least one query item from multiple business processing work orders;

[0278] The target business processing work order is identified as an unprocessed work order.

[0279] In one or more embodiments, in response to a query request, unprocessed work orders are obtained from multiple business processing work orders. The obtaining module 810 is specifically used for:

[0280] In response to a user's login request, the system retrieves the login credentials corresponding to the user's level from the internal network server. These credentials are used to indicate that the user's authentication has been successful.

[0281] In response to a query request, retrieve unprocessed work orders from multiple business processing work orders on the intranet server;

[0282] A firewall is installed between the internal network server and external network devices (excluding electronic devices) for communication.

[0283] In one or more embodiments, before retrieving unprocessed work orders from multiple business processing work orders in response to a query request, the acquisition module 810 is further configured to:

[0284] In response to work order return operations from other devices, retrieve the return work order corresponding to the work order return operation. The return work order carries a record identifier indicating that the work order was returned.

[0285] Add the returned work order to multiple business processing work orders.

[0286] Based on the above embodiments, Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 9 As shown, the electronic device 900 includes: a processor 910, a memory 920, and a bus 930;

[0287] The memory 920 is used to store the computer-executed instructions of the processor 910;

[0288] The processor 910 is configured to execute the technical solutions of any of the foregoing method embodiments by executing computer execution instructions.

[0289] Optionally, the memory 920 can be either standalone or integrated with the processor 910.

[0290] Optionally, the memory 920 may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0291] Bus 930 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, only one thick line is used to represent a bus in the accompanying drawings of this application, but this does not imply that there is only one bus or one type of bus.

[0292] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0293] The electronic device is used to execute the technical solution of any of the foregoing method embodiments. Its implementation principle and technical effect are similar, and will not be repeated here.

[0294] This application also provides a computer-readable storage medium storing computer-executable instructions thereon, which, when executed by a processor, are used to implement the technical solutions provided in any of the above method embodiments.

[0295] This application also provides a computer program product, including a computer program, which includes computer instructions stored in a computer-readable storage medium. When the computer program is executed by a processor, it is used to implement the technical solutions provided in any of the above method embodiments.

[0296] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0297] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0298] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0299] Furthermore, unless otherwise specified, the functional units / modules in the various embodiments of this application can be integrated into one unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated together. The integrated units / modules described above can be implemented in hardware or as software program modules.

[0300] When integrated units / modules are implemented in hardware, the hardware can be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic or magneto-optical storage medium, such as Resistive Random Access Memory (RRAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Enhanced Dynamic Random Access Memory (EDRAM), High-Bandwidth Memory (HBM), Hybrid Memory Cube (HMC), etc.

[0301] If the integrated unit / module is implemented as a software program module and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0302] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0303] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

Claims

1. A method for reminding users of work order processing, characterized in that, include: In response to the query request, unprocessed work orders are retrieved from multiple business processing work orders; The unprocessed work orders are parsed to determine at least one target notification object and target work order notification information for the unprocessed work orders, wherein the at least one target notification object has a different level; According to a preset push strategy, the target work order reminder information is pushed to the at least one target reminder object. The push strategy is determined by the first priority order of receiving work order reminder information corresponding to the level of the at least one reminder object and the second priority order of at least one reminder method.

2. The method according to claim 1, characterized in that, The first priority order includes at least one from high to low: direct object level, first object level, and second object level; the second priority order includes at least one from high to low: SMS, telephone, and voice. Accordingly, the step of pushing the target work order reminder information to the at least one target reminder recipient according to a preset push strategy includes: The target work order reminder information is pushed to the target reminder object corresponding to the target direct object level in the second priority order according to the reminder method, until any reminder method is successfully pushed; If the push to the target reminder objects corresponding to the target direct object level fails, the target work order reminder information will be pushed to the target reminder objects corresponding to the target first object level in the second priority order according to the reminder method in the second priority order, until any reminder method is successfully pushed. If the notification to the target objects corresponding to the first target object level fails to be pushed, the target work order notification information will be pushed to the target objects corresponding to the second target object level in sequence according to the notification method in the second priority order, until any one of the notification methods is successfully pushed.

3. The method according to claim 2, characterized in that, The at least one notification method includes: SMS, telephone, and voice; Accordingly, the target work order reminder information is pushed sequentially according to the reminder methods in the second priority order until any reminder method is successfully pushed, including: The target work order reminder information is pushed as an SMS reminder. If feedback is received within a first preset time period, it is determined that the SMS reminder was successfully pushed. If the feedback notification is not received within the first preset time period, it is determined that the SMS reminder method has failed to be pushed, and the target work order reminder information is pushed by telephone. If the telephone is hung up within the second preset time period, it is determined that the telephone reminder method has been successfully pushed. If the call is answered within the second preset time period, the target work order reminder information will be pushed out as a voice reminder, then the call reminder will be considered successfully pushed out.

4. The method according to claim 3, characterized in that, The method further includes: If the call is not connected within the second preset time period, continue dialing the preset number of times until the call is connected or hung up. If the dialing continues for the preset number of times without being connected, the push notification is considered to have failed.

5. The method according to claim 2 or 4, characterized in that, The step of parsing the unprocessed work orders to determine at least one target notification object and target work order notification information includes: The unprocessed work orders are parsed to obtain their basic information. For each reminder method, the basic information is generated and processed according to the reminder method to obtain the target work order reminder information corresponding to the reminder method; The at least one target to be reminded and the level of the at least one target to be reminded are identified in the contact field of the basic information.

6. The method according to any one of claims 1-4, characterized in that, The response to the query request, retrieving unprocessed work orders from multiple business processing work orders, includes: In response to the query request, at least one query item in the query request is retrieved; Obtain the target business processing work order that contains at least one query item from the plurality of business processing work orders; The target business processing work order is identified as the unprocessed work order.

7. The method according to any one of claims 1-4, characterized in that, The response to the query request, retrieving unprocessed work orders from multiple business processing work orders, includes: In response to a user's login request, the system retrieves the login credentials corresponding to the user's level from the intranet server. These login credentials are used to indicate that the user's authentication has been successful. In response to the query request, the unprocessed work order is retrieved from multiple business processing work orders in the intranet server; A firewall is installed between the communication link between the intranet server and the extranet device.

8. The method according to any one of claims 1-4, characterized in that, Before retrieving unprocessed work orders from multiple business processing work orders in response to a query request, the method further includes: In response to a work order return operation from another device, the returned work order corresponding to the work order return operation is obtained, and the returned work order carries a record identifier of the returned work order; Add the returned work order to the multiple business processing work orders.

9. A work order processing reminder device, characterized in that, include: The retrieval module is used to respond to query requests and retrieve unprocessed work orders from multiple business processing work orders; The processing module is used to parse and process the unprocessed work orders, determine at least one target reminder object and target work order reminder information of the unprocessed work orders, wherein the at least one target reminder object has a different level; The push module is used to push the target work order reminder information to the at least one target reminder object according to a preset push strategy. The push strategy is determined by the first priority order of receiving work order reminder information corresponding to the level of the at least one reminder object and the second priority order of at least one reminder method.

10. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-8.

Images