CN117155894A - Timing reminding method, device, server and medium - Google Patents

Abstract

The application discloses a timing reminding method, a timing reminding device, a server and a medium, which can be applied to the field of mobile interconnection or the field of finance. After the service flow is transferred to the target node, if the current time reaches the initial reminding time, generating notification content; determining notification times and notification time by aiming at the initial reminding time, the interval reminding time and the termination reminding time of a user processing the task; the notification content is copied to obtain notification content of a number of notification times. The notification time is used as the message number of the notification content to obtain a plurality of notification messages, and the plurality of notification messages are sequentially stored into a message queue from the late to the early according to the notification time; and in the subsequent process of sending the notification message, the notification message is taken out from the message queue. The user can receive the notification message, so that the user can not forget that the target node has own tasks to process, and the purpose of timing reminding is achieved.

Description

Timing reminding method, device, server and medium

Technical Field

The application relates to the field of mobile interconnection, in particular to a timing reminding method, a timing reminding device, a timing reminding server and a timing reminding medium.

Background

Enterprises in the financial field, such as banks, have many processes. Each flow is made up of a plurality of nodes. Some nodes require human participation. Tasks such as nodes require processing by the user. There are situations where the user may not know what time to process the task.

Based on this, a timed alert mechanism is needed to alert the user to transact tasks.

Disclosure of Invention

In view of the above, the application provides a timing reminding method, a timing reminding device, a timing reminding server and a timing reminding medium.

In order to achieve the above purpose, the present application provides the following technical solutions:

according to a first aspect of the embodiments of the present disclosure, a timing reminding method is provided, and the timing reminding method is applied to a process composed of a plurality of nodes, wherein a target node in the plurality of nodes is a node that needs to participate by people, the target node corresponds to timing information and service task information, the timing information includes a start reminding time, an interval reminding time and a termination reminding time of the target node, and the service task information includes description information of a task to be processed corresponding to the target node, and communication information of a user that processes the task to be processed; the timing reminding method comprises the following steps:

if the service flow is transferred to the target node and the current time reaches the initial reminding time, generating notification content containing the description information;

determining notification times and notification time according to the initial reminding time, the interval reminding time and the termination reminding time;

copying the notification content to obtain a plurality of notification content of the notification times;

determining the message number of the notification content as the notification time for each notification content, wherein the message numbers of different notification contents are different;

storing notification messages to a message queue sequentially from late to early according to the notification time, wherein the notification messages comprise the notification content and the notification time corresponding to the notification content;

reading a target notification time in a target notification message located in the message queue head;

if the current time reaches the target notification time, the target notification message positioned at the head of the message queue is taken out from the message queue;

sending the target notification message to terminal equipment corresponding to the communication information;

and if the message queue comprises the notification message, returning to the step of reading the target notification time in the target notification message positioned at the head of the message queue.

According to a second aspect of the embodiments of the present disclosure, a timing reminding device is provided, and the timing reminding device is applied to a flow composed of a plurality of nodes, wherein a target node in the plurality of nodes is a node needing to participate by people, the target node corresponds to timing information and service task information, the timing information comprises a start reminding time, an interval reminding time and a termination reminding time of the target node, and the service task information comprises description information of a task to be processed corresponding to the target node, and communication information of a user processing the task to be processed; the timing reminding device comprises:

the generating module is used for generating notification content containing the description information if the service flow is transferred to the target node and the current time reaches the initial reminding time;

the first determining module is used for determining notification times and notification time according to the initial reminding time, the interval reminding time and the termination reminding time;

the first acquisition module is used for copying the notification content to obtain a plurality of notification content of the notification times;

a second determining module, configured to determine, for each notification content, that a message number of the notification content is the notification time, where the message numbers of different notification contents are different;

the storage module is used for sequentially storing notification messages to a message queue from the late to the early according to the notification time, wherein the notification messages comprise the notification content and the notification time corresponding to the notification content;

a reading module, configured to read a target notification time in a target notification message located in the message queue header;

the extraction module is used for extracting the target notification message positioned at the message queue head from the message queue if the current time reaches the target notification time;

the first sending module is used for sending the target notification message to the terminal equipment corresponding to the communication information;

and the first triggering module is used for triggering the reading module if the message queue comprises the notification message.

According to a third aspect of embodiments of the present disclosure, there is provided a server comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the timed reminder method as described in the first aspect.

According to a fourth aspect of embodiments of the present disclosure, there is provided a computer readable storage medium, which when executed by a processor of a server, causes the server to perform the timed alert method according to the first aspect.

As can be seen from the above technical solution, the present application provides a timing reminding method, and after a service flows to a target node, if the current time reaches an initial reminding time, a notification content containing description information of a task for the target node is generated; determining notification times and notification time by aiming at the initial reminding time, the interval reminding time and the termination reminding time of a user processing the task; the notification content is copied to obtain notification content of a number of notification times. In the embodiment of the application, the notification time is used as the message number of the notification content to obtain a plurality of notification messages, and the plurality of notification messages are sequentially stored into a message queue from the late to the early according to the notification time; in the subsequent process of sending the notification message, the notification message is taken out from the message queue, and the notification message is not required to be regenerated every time the notification message is sent, so that the notification message can be quickly sent to the terminal equipment of the reminded user. The user can receive the notification message, so that the user can not forget that the target node has own tasks to process, and the purpose of timing reminding is achieved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic diagram of a hardware architecture according to an embodiment of the present application;

FIG. 2 is a flowchart illustrating a method of timing reminders, according to an exemplary embodiment;

FIG. 3 is a schematic diagram of task flows among a plurality of nodes included in a flow provided in an embodiment of the present application;

FIG. 4 is a schematic diagram of a message queue storing notification messages according to an embodiment of the present application;

FIG. 5 is a block diagram of a timed reminder according to one exemplary embodiment;

fig. 6 is a block diagram illustrating an apparatus for a server according to an exemplary embodiment.

Detailed Description

The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards of the related country and region.

The embodiment of the application provides a timing reminding method, a timing reminding device, a server and a medium. Before introducing the technical scheme provided by the embodiment of the application, the hardware architecture related to the application is described.

As shown in fig. 1, a schematic diagram of a hardware architecture according to an embodiment of the present application includes: server 11 and terminal device 12.

The server 11 may be a server, a server cluster formed by a plurality of servers, or a cloud computing service center.

It is understood that the server 11 is a device that runs the entire flow. Illustratively, when the flow runs to a certain node (hereinafter referred to as a target node), the server 11 transmits the relevant information to the electronic device corresponding to the target node.

Illustratively, a user handling a task of the target node may log onto the electronic device in order to handle the task.

The electronic device may be, for example, a terminal device 12. The above-described electronic devices may be different from the terminal device 12, for example.

By way of example, the terminal device 12 may be any electronic product that can interact with a user by one or more of a keyboard, touchpad, touch screen, remote control, voice interaction, or handwriting device, such as a mobile phone, tablet, palm top, wearable device, etc.

The terminal device 12 may be, for example, a device that is carried with a user.

The server 12 may send a notification message to the terminal device 12, where the notification message prompts the user to process the task of the target node, and since the terminal device 12 is a device carried by the user, the user may receive the notification message sent by the server at any time, so that the user may not forget to process the task.

Those skilled in the art will appreciate that the above servers and terminal devices are only examples, and that other servers and terminal devices now known or hereafter may be present as applicable to the present disclosure, are also included within the scope of the present disclosure and are incorporated herein by reference.

The following describes a timing reminding method provided by the embodiment of the application with reference to the above hardware architecture.

Fig. 2 is a flowchart illustrating a method of timing reminding according to an exemplary embodiment, and as shown in fig. 2, the method of timing reminding is used in a server, and includes the following steps S21 to S29.

Step S21: and if the service flow is transferred to the target node and the current time reaches the initial reminding time, generating notification content containing descriptive information.

The timing reminding method provided by the embodiment of the application is applied to a flow, and the flow consists of a plurality of nodes. Each node corresponds to a corresponding task, and the tasks of some of the plurality of nodes are programmed without human intervention, such as by RPA (Robotic process automation, robot flow automation) to perform the tasks corresponding to the node; illustratively, the tasks of certain nodes of the plurality of nodes are human participation. In the embodiment of the application, the node needing human participation is called as the target node.

Illustratively, the number of target nodes may be one or more.

Because the target node needs to participate manually, the target node corresponds to timing information and service task information; the timing information comprises an initial reminding time, an interval reminding time and an ending reminding time of the target node, and the service task information comprises description information of a task to be processed corresponding to the target node.

For example, the descriptive information may include a general description of the task and a latest processing deadline for the task.

For example, the timing information corresponding to different target nodes may be different and may be the same. The different target nodes may or may not be adjacent nodes.

Adjacent nodes and non-adjacent nodes are described below.

Fig. 3 is a schematic diagram of task flows among a plurality of nodes included in a flow provided in an embodiment of the present application.

The flow shown in fig. 3 includes 8 nodes, node 11, node 12, node 13, node 14, node 15, node 16, node 17, and node 18, respectively. Arrows connecting between nodes indicate directions of task flow.

Assume that node 12, node 13, node 14, node 16, node 17, and node 18 of the 8 nodes are target nodes requiring human participation. The task flow process between 8 nodes is shown in fig. 3.

Of the 6 target nodes shown in fig. 3, the node 12 and the node 14 are adjacent nodes, the node 16, the node 17 and the node 18 are adjacent nodes, and the node 12, the node 13 and the node 16 are non-adjacent nodes; node 12 and node 17 are non-adjacent nodes, and node 12 and node 18 are non-adjacent nodes; node 13 and node 17 are non-adjacent nodes and node 13 and node 18 are non-adjacent nodes.

Illustratively, the plurality of nodes includes a plurality of target nodes, and the plurality of target nodes are related in two ways.

In the first relation, tasks corresponding to two or more target nodes in the plurality of target nodes are sequentially executed.

Still taking fig. 3 as an example, the tasks corresponding to the node 16, the node 17 and the node 18 respectively have a sequential execution sequence, the task of the node 17 can be executed after the task of the node 16 is executed, and the task of the node 18 can be executed after the task of the node 17 is executed.

Still taking fig. 3 as an example, tasks corresponding to the node 12 and the node 16 respectively have a sequential execution sequence, and after the task of the node 12 is executed, the task of the node 16 can be executed.

For example, if the relationship of two or more target nodes is the first relationship, the start reminding time and the end reminding time in the timing information of the two or more target nodes are different.

If the task processing time of the node 12 is earlier than the task processing time of the node 16, the start reminding time of the timing information corresponding to the node 12 is earlier than the start reminding time of the timing information corresponding to the node 16.

If the task processing of the node 12 is completed, the task of the node 16 may start to be processed, so that the termination reminding time of the timing information of the node 12 is earlier than the termination reminding time of the timing information of the node 16.

In the second relation, tasks corresponding to two or more target nodes in the plurality of target nodes are not sequentially executed.

Still taking fig. 3 as an example, tasks corresponding to the nodes 12 and 13 are not sequentially executed. That is, the task corresponding to the node 12 and the task corresponding to the node 13 may be executed simultaneously or sequentially.

For example, if the relationship between two or more target nodes is the second relationship, the start reminding time and the end reminding time in the timing information of the two or more target nodes may be the same or different.

For example, the task processing time of the node 12 and the task processing time of the node 13 may be the same, so the start reminding time of the timing information corresponding to the node 12 may be equal to the start reminding time of the timing information corresponding to the node 16.

It can be understood that there are various ways to calculate the initial reminding time in the timing information of the target node, and the embodiments of the present application provide, but are not limited to, the following three ways.

The first method for calculating the initial reminding time of the timing information of the target node includes the following steps a11 to a12.

Step A11: and in the task processing process of the previous node of the target node, predicting the task processing completion time of the previous node.

The following describes the previous node.

Still taking fig. 3 as an example, the previous node to node 12 is node 11. The previous node to node 14 is node 12.

For example, the task processing completion time may be estimated based on the time at which the previous node processed the historical task.

Step A12: and determining the task processing completion time of the previous node as the initial reminding time.

The second method for calculating the initial reminding time of the timing information of the target node includes the following steps a21 to a22.

Step A21: and under the condition that the task of the previous node is processed, determining the estimated time length of the task corresponding to the target node to be processed in the future based on the processing time length of the historical task corresponding to the target node.

The embodiment of the application calls the task corresponding to the processed target node as the history task.

Illustratively, estimated duration = average of processing durations of historical tasks.

For example, the estimated duration of the task to be processed corresponding to the target node=the average value of the processing durations of the historical tasks of the same task type as the task to be processed.

Step A22: and determining the difference value between the latest task completion time corresponding to the target node and the estimated duration as the initial reminding time.

The initial alert times of the timing information of the first and second target nodes are dynamically changed as the processing completion time of the previous node is changed.

The third method for calculating the initial reminding time of the timing information of the target node includes the following step a31.

Step A31: presetting an initial reminding time of a target node.

The starting reminding time of the timing information of the third target node is fixed and is preset manually.

It can be understood that there are various ways to calculate the termination reminding time in the timing information of the target node, and the embodiments of the present application provide, but are not limited to, the following two ways.

The first calculation method of the termination reminding time in the timing information of the target node includes the following steps B11 to B12.

Step B11: and under the condition that the task of the previous node is processed, determining the estimated time length of the task corresponding to the target node to be processed in the future based on the processing time length of the historical task corresponding to the target node.

The description of the estimated time period may be referred to the description of the estimated time period of step a21, and will not be repeated here.

Step B12: and determining the sum of the task processing completion time, the estimated time length and the remaining time length of the previous node as the termination reminding time.

The second calculation method of the termination reminding time in the timing information of the target node includes the following steps B21 to B22.

Step B21: the processing time of the task of the target node is determined based on the work schedule of the user for processing the task of the target node.

For example, the work schedule may include a priority level and a processing duration corresponding to each of the plurality of tasks. Sequencing the tasks based on the priority level, so that the processing order of the tasks corresponding to the target node can be determined; based on the processing time periods respectively corresponding to the tasks, the processing time of the task corresponding to the target node can be determined.

Step B22: and determining the processing time as the termination reminding time.

For example, the interval reminding time in the timing information may be based on actual situations, and the comparison of the embodiment of the application is not limited.

Step S22: and determining the notification times and the notification time according to the initial reminding time, the interval reminding time and the termination reminding time.

Illustratively, the number of notifications = (ending alert time-starting alert time)/interval alert time +1.

If (end alert time-start alert time)/interval alert time is a fraction, then the number of notifications = round up { (end alert time-start alert time)/interval alert time is a fraction } +1; or, the number of notifications = round down { (end alert time-start alert time)/interval alert time is a fraction } +1.

The following describes a determination process of the notification time and the notification number by way of example.

Assume that the initial alert time is 13:00, the termination reminding time is 14:00, the interval reminding time is 30 minutes, and the notification times are= (14:00-13:00)/0.5+1=3; the 3 times of notification time are as follows: 13:00, 13:30, 14:00.

step S23: copying the notification content to obtain a plurality of notification contents of the notification times.

To avoid repeatedly executing step S22 a plurality of times, the notification content generated in step S22 may be copied to obtain a plurality of notification contents of the number of times of notification.

Step S24: and determining the message number of the notification content as the notification time for each notification content, wherein the message numbers of different notification contents are different.

Still with the initial alert time 13:00, the termination reminding time is 14:00, taking 30 minutes as an example of interval reminding time, if the notification times are 3, copying to obtain 3 notification contents; the message numbers corresponding to the 3 notification contents are as follows: 13:00, 13:30, 14:00.

step S25: and storing notification messages to a message queue sequentially from late to early according to the notification time, wherein the notification messages comprise the notification content and the notification time corresponding to the notification content.

Still for the above purpose, 3 notification messages are obtained, and the 3 notification messages are {13:00, notification content }, {13:30, notification content }, {14:00, notification content }.

The specific implementation of step S25 is illustrated below.

Fig. 4 is a schematic diagram of a message queue storing notification messages according to an embodiment of the present application.

Storing notification messages to a message queue sequentially from late to early according to the notification time, and then storing 3 notification messages {13:00, notification content }, {13:30, notification content }, {14:00, notification content } is stored in the order of the message queues from late to early according to time: {14:00, notification content }, {13:30, notification content }, {13:00, notification content }. So {14:00, notification content } at the end of the queue, {13:00, notification content } is located at the head of the team.

Step S26: and reading the target notification time in the target notification message of the message queue head.

In the embodiment of the application, the notification message positioned at the opposite head of the message queue is called as a target notification message. The notification time in the target notification message is referred to as the target notification time.

Step S27: and if the current time reaches the target notification time, the target notification message positioned at the head of the message queue is taken out from the message queue.

Assume that the current time reaches or approaches 13:00, then fetch {13:00, notification content }, and after retrieving the notification message, notification message {13:30, notification content } is located at the head of the message queue.

Step S28: and sending the target notification message to the terminal equipment corresponding to the communication information.

The target notification message received by the terminal device has notification time in addition to the notification content.

Step S29: if the message queue includes the notification message, returning to step S26.

If the message queue further includes a notification message, the instruction is that the user should be notified again, so that the process returns to step S26. If the notification message is not included in the message queue, it indicates that the user has been notified, so that it is not necessary to return to step S26.

The embodiment of the application provides a timing reminding method, which comprises the steps of generating notification content containing description information of a task aiming at a target node if the current time reaches the initial reminding time after traffic flows are transferred to the target node; determining notification times and notification time by aiming at the initial reminding time, the interval reminding time and the termination reminding time of a user processing the task; the notification content is copied to obtain notification content of a number of notification times. In the embodiment of the application, the notification time is used as the message number of the notification content to obtain a plurality of notification messages, and the plurality of notification messages are sequentially stored into a message queue from the late to the early according to the notification time; in the subsequent process of sending the notification message, the notification message is taken out from the message queue, and the notification message is not required to be regenerated every time the notification message is sent, so that the notification message can be quickly sent to the terminal equipment of the reminded user. The user can receive the notification message, so that the user can not forget that the target node has own tasks to process, and the purpose of timing reminding is achieved.

It will be appreciated that in the process of the server sending the notification message to the terminal device, there may be a case where the notification message is failed to be sent. If the notification message is sent failure, the terminal device does not receive the notification message, and therefore the purpose of reminding the user cannot be achieved.

Step C1: and if the indication of successful receipt of the target notification message fed back by the terminal equipment is received within the preset time, setting the state of the target notification message as successful sending.

For example, the preset time may be based on actual conditions, and is not limited herein.

Step C2: if the indication of successfully receiving the target notification message fed back by the terminal equipment is not received within the preset time, setting the state of the target notification message as a sending failure.

Step C3: and C1, if the state of the target notification message is that the transmission fails, and the number of times of transmitting the target notification message is smaller than or equal to a preset threshold value, transmitting the target notification message again, and returning to the step C1.

The execution time of step C3 is not limited, for example.

Illustratively, the execution time of step C3 needs to be before the notification time of the next head of the message queue, as exemplified below.

Still taking fig. 4 as an example, assume that the notification message currently fetched from the message queue is {13:00, notify content }, then the next head of the message queue is {13:30, notification content }. At 13:30, if the notification message {13:00, notify content } not sent successfully, can repeat the sending multiple times, at 13: after 30, even if the notification message {13:00, notification content } is not sent successfully, nor is it necessary to send again, because the notification message {13:30, notification content }.

It can be understood that, if the user logs in the electronic device to process the task of the target node after receiving the notification message, in this case, the notification message does not need to be sent to the terminal device of the user again, so the embodiment of the present application further provides the following method: and if the task to be processed is detected to be in a processing state, the message queue is emptied.

For example, if the user logs in to the electronic device to process the task of the target node after receiving the notification message, in this case, the notification message may also be sent again to the terminal device of the user.

The method is described in detail in the embodiments disclosed in the present application, and the method can be implemented by using various types of devices, so that the present application also discloses a device, and specific embodiments are given below for details.

FIG. 5 is a block diagram illustrating a timed reminder according to one example embodiment. The timing reminding device is applied to a flow consisting of a plurality of nodes, wherein a target node in the plurality of nodes is a node needing to participate manually, the target node corresponds to timing information and service task information, the timing information comprises starting reminding time, interval reminding time and ending reminding time of the target node, and the service task information comprises description information of a task to be processed corresponding to the target node and communication information of a user processing the task to be processed. Referring to fig. 5, the apparatus includes: the generating module 51, the first determining module 52, the first obtaining module 53, the second determining module 54, the storing module 55, the reading module 56, the retrieving module 57, the first sending module 58 and the first triggering module 59, wherein:

the generating module 51 is configured to generate notification content including the description information if the service flow is transferred to the target node and the current time reaches the initial reminding time;

a first determining module 52, configured to determine the notification times and notification times according to the initial alert time, the interval alert time, and the termination alert time;

a first obtaining module 53, configured to copy the notification content to obtain the notification content of the notification times;

a second determining module 54, configured to determine, for each of the notification contents, that a message number of the notification content is the notification time, and that message numbers of different notification contents are different;

a storage module 55, configured to store, in sequence from late to early, a notification message to a message queue according to the notification time, where the notification message includes the notification content and the notification time corresponding to the notification content;

a reading module 56, configured to read a target notification time in a target notification message located in the message queue header;

a retrieving module 57, configured to retrieve the target notification message located at the head of the message queue from the message queue if the current time reaches the target notification time;

a first sending module 58, configured to send the target notification message to a terminal device corresponding to the communication information;

and a first triggering module 59, configured to trigger the reading module if the message queue includes the notification message.

In an alternative implementation, the method further includes:

the first setting module is used for setting the state of the target notification message as successful sending if the indication of successful receiving of the target notification message fed back by the terminal equipment is received within the preset time;

and the second setting module is used for setting the state of the target notification message as transmission failure if the indication of successfully receiving the target notification message fed back by the terminal equipment is not received within the preset time.

In an alternative implementation, the method further includes:

the second sending module is used for sending the target notification message if the state of the target notification message is failed to send, and the number of times of sending the target notification message is smaller than or equal to a preset threshold value, and sending the target notification message again;

the first triggering module is used for triggering the first setting module.

In an alternative implementation, the method further includes:

and the control module is used for emptying the message queue if the task to be processed is detected to be in a processing state.

The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.

Fig. 6 is a block diagram illustrating an apparatus for a server according to an exemplary embodiment.

Servers include, but are not limited to: processor 61, memory 62, network interface 63, I/O controller 64, and communication bus 65.

It should be noted that the structure of the server shown in fig. 6 is not limited to the server, and the server may include more or less components than those shown in fig. 6, or may combine some components, or may be arranged with different components, as will be understood by those skilled in the art.

The following describes the respective constituent elements of the server in detail with reference to fig. 6:

the processor 61 is a control center of the server, connects respective parts of the entire server using various interfaces and lines, and performs various functions of the server and processes data by running or executing software programs and/or modules stored in the memory 62 and calling data stored in the memory 62, thereby performing overall monitoring of the server. Processor 61 may include one or more processing units; by way of example, the processor 61 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 61.

Processor 61 may be a central processing unit (Central Processing Unit, CPU), or a specific integrated circuit ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement embodiments of the present application, etc.;

the Memory 62 may include a Memory such as a Random-Access Memory (RAM) 621 and a Read-Only Memory (ROM) 622, and may further include a mass storage device 623 such as at least 1 disk Memory and the like. Of course, the server may also include hardware required for other services.

The memory 62 is used for storing executable instructions of the processor 61. The processor 61 has a function of executing the timed reminder method.

A wired or wireless network interface 63 is configured to connect the server to a network.

The processor 61, memory 62, network interface 63, and I/O controller 64 may be interconnected by a communication bus 65, which may be an ISA (Industry Standard Architecture ) bus, PCI (Peripheral Component Interconnect, peripheral component interconnect standard) bus, or EISA (Extended Industry Standard Architecture ) bus, among others. The buses may be classified as address buses, data buses, control buses, etc.

In an exemplary embodiment, the server may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the above-described timed alert method.

In an exemplary embodiment, the disclosed embodiments provide a storage medium including instructions, such as a memory 62 including instructions, executable by a processor 61 of a server to perform the above-described method. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

In an exemplary embodiment, a computer readable storage medium is also provided, which can be directly loaded into an internal memory of a computer, such as the memory 62 described above, and contains software code, and the computer program can implement the timing reminding method described above after being loaded and executed by the computer.

In an exemplary embodiment, a computer program product is also provided, which can be directly loaded into an internal memory of a computer, for example, a memory contained in the server, and contains software codes, and the computer program can implement the above-mentioned timing reminding method after being loaded and executed by the computer.

It should be noted that the timing reminding method, the timing reminding device, the server and the medium provided by the application can be used in the field of mobile interconnection or the field of finance. The foregoing is merely an example, and the application fields of the timing reminding method, the apparatus, the server and the medium provided by the application are not limited.

The features described in the respective embodiments in the present specification may be replaced with each other or combined with each other. For device or system class embodiments, the description is relatively simple as it is substantially similar to method embodiments, with reference to the description of method embodiments in part.

It is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software modules may be disposed in Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. The timing reminding method is characterized by being applied to a flow consisting of a plurality of nodes, wherein a target node in the plurality of nodes is a node needing to participate manually, the target node corresponds to timing information and service task information, the timing information comprises starting reminding time, interval reminding time and ending reminding time of the target node, and the service task information comprises description information of a task to be processed corresponding to the target node and communication information of a user processing the task to be processed; the timing reminding method comprises the following steps:

if the service flow is transferred to the target node and the current time reaches the initial reminding time, generating notification content containing the description information;

determining notification times and notification time according to the initial reminding time, the interval reminding time and the termination reminding time;

copying the notification content to obtain a plurality of notification content of the notification times;

determining the message number of the notification content as the notification time for each notification content, wherein the message numbers of different notification contents are different;

storing notification messages to a message queue sequentially from late to early according to the notification time, wherein the notification messages comprise the notification content and the notification time corresponding to the notification content;

reading a target notification time in a target notification message located in the message queue head;

if the current time reaches the target notification time, the target notification message positioned at the head of the message queue is taken out from the message queue;

sending the target notification message to terminal equipment corresponding to the communication information;

and if the message queue comprises the notification message, returning to the step of reading the target notification time in the target notification message positioned at the head of the message queue.

2. The timed reminder method according to claim 1, further comprising:

if the indication of successful receipt of the target notification message fed back by the terminal equipment is received within the preset time, setting the state of the target notification message as successful sending;

if the indication of successfully receiving the target notification message fed back by the terminal equipment is not received within the preset time, setting the state of the target notification message as a sending failure.

3. The timed reminder method according to claim 2, further comprising:

if the state of the target notification message is failed in transmission, and the number of times of transmitting the target notification message is smaller than or equal to a preset threshold value, transmitting the target notification message again;

and returning to the step of setting the state of the target notification message as successful sending if the indication of successful receiving the target notification message fed back by the terminal equipment is received within the preset time.

4. A method of timed reminding according to any one of claims 1-3, characterized in that it further comprises:

and if the task to be processed is detected to be in a processing state, the message queue is emptied.

5. The timing reminding device is characterized by being applied to a flow consisting of a plurality of nodes, wherein a target node in the plurality of nodes is a node needing to participate manually, the target node corresponds to timing information and service task information, the timing information comprises starting reminding time, interval reminding time and ending reminding time of the target node, and the service task information comprises description information of a task to be processed corresponding to the target node and communication information of a user processing the task to be processed; the timing reminding device comprises:

the generating module is used for generating notification content containing the description information if the service flow is transferred to the target node and the current time reaches the initial reminding time;

the first determining module is used for determining notification times and notification time according to the initial reminding time, the interval reminding time and the termination reminding time;

the first acquisition module is used for copying the notification content to obtain a plurality of notification content of the notification times;

a second determining module, configured to determine, for each notification content, that a message number of the notification content is the notification time, where the message numbers of different notification contents are different;

the storage module is used for sequentially storing notification messages to a message queue from the late to the early according to the notification time, wherein the notification messages comprise the notification content and the notification time corresponding to the notification content;

a reading module, configured to read a target notification time in a target notification message located in the message queue header;

the extraction module is used for extracting the target notification message positioned at the message queue head from the message queue if the current time reaches the target notification time;

the first sending module is used for sending the target notification message to the terminal equipment corresponding to the communication information;

and the first triggering module is used for triggering the reading module if the message queue comprises the notification message.

6. The timed reminder according to claim 5, further comprising:

the first setting module is used for setting the state of the target notification message as successful sending if the indication of successful receiving of the target notification message fed back by the terminal equipment is received within the preset time;

and the second setting module is used for setting the state of the target notification message as transmission failure if the indication of successfully receiving the target notification message fed back by the terminal equipment is not received within the preset time.

7. The timed reminder according to claim 6, further comprising:

the second sending module is used for sending the target notification message if the state of the target notification message is failed to send, and the number of times of sending the target notification message is smaller than or equal to a preset threshold value, and sending the target notification message again;

the first triggering module is used for triggering the first setting module.

8. The timed reminder according to any one of claims 5 to 7, further comprising:

and the control module is used for emptying the message queue if the task to be processed is detected to be in a processing state.

9. A server, comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the timed reminder method of any one of claims 1 to 4.

10. A computer readable storage medium, which when executed by a processor of a server, causes the server to perform the timed alert method according to any one of claims 1 to 4.