Collection table notification task scheduling method, related device and medium

Abstract

The invention provides a collection table notification task scheduling method, a related device and a medium. The collection table notification task scheduling method comprises the steps that a plurality of collection table notification tasks are obtained, the collection table notification tasks are used for notifying opposite side nodes of events associated with editing of collection tables to the events, and the collection table notification tasks have priorities; recording the plurality of collection table notification tasks into a notification task pipeline table; determining a target notification task in a plurality of collection table notification tasks based on the priorities of the plurality of collection table notification tasks in the notification task pipeline table; and sending the target notification task to a notification center, and notifying an event in the target notification task to an opposite party node in the target notification task by the notification center. According to the embodiment of the invention, the timeliness of the important notification task is guaranteed. The embodiment of the invention can be applied to various fields of online document processing, Internet, data processing and the like.

Description

Technical Field

[0001] The present disclosure relates to the field of big data, and in particular to a collection table notification task scheduling method, related devices and media. Background Art

[0002] The collection form is a form consisting of one or more questions. It is usually created by the collector. The filler can fill in the form content according to the questions and submit it. The online form corresponds to the collection form. It summarizes the submission results of multiple fillers for the collection form in the form of a table. The collector can check the submission results of multiple fillers through the online form. In the process of transferring the data of the collection form to the online form for summary scheduling, the administrator of the online form side usually needs to urge the users who have not submitted the collection form to fill it out, or when the filler of the collection form submits or modifies the collection form, it is necessary to remind the administrator of the online form side. Therefore, a large number of collection form notification tasks are usually generated in a short period of time, and the speed of sending the collection form notification tasks to the collection form side or the online form side is relatively slow. The throughput difference between the generation and sending of the collection form notification tasks is large. When the generation speed of the collection form notification tasks is much faster than the sending speed, loss will occur.

[0003] At present, the collection table notification task scheduling method decouples the generation system and the issuance system of the collection table notification task through an asynchronous queue. Multiple queues are set between the collection table end or the online table end that generates the notification and the notification center. When the collection table notification task is generated, it is stored in the queue. When the notification center notifies, the collection table notification tasks are taken out one by one from the queue according to the first-in-first-out principle and the notification is made. Since the queue plays the role of storing the collection table notification tasks that have not been notified, when the generation speed of the collection table notification tasks is much faster than the issuance speed, they will not be lost because they are stored in the queue. The disadvantage of the prior art is that the notification tasks in the queue are in an equal position, and the consumers will take them out one by one and send them to the notification center. Some important notification tasks will be blocked by some less important notification tasks and will not be notified for a long time. In addition, some notification tasks have a strong timeliness, and it will be useless to notify them after a period of time. That is, the prior art cannot guarantee the immediacy and lack of timeliness of important notifications. Summary of the invention

[0004] The disclosed embodiment provides a collection table notification task scheduling method, related device and medium, which improves the notification immediacy and timeliness of the collection table notification task.

[0005] According to one aspect of the present disclosure, a collection table notification task scheduling method is provided, comprising:

[0006] Acquire a plurality of collection table notification tasks, wherein the collection table notification tasks are used to notify a counterparty node of an event associated with editing of the collection table, and the collection table notification tasks have a priority;

[0007] Recording a plurality of the collection table notification tasks into a notification task flow table;

[0008] Determine a target notification task from among the plurality of collection table notification tasks based on the priorities of the plurality of collection table notification tasks in the notification task flow table;

[0009] The target notification task is sent to a notification center, and the notification center notifies the counterparty node in the target notification task of the event in the target notification task.

[0010] According to one aspect of the present disclosure, a collection table notification task scheduling device is provided, comprising:

[0011] A task acquisition unit, used for acquiring a plurality of collection table notification tasks, wherein the collection table notification tasks are used for notifying a counterparty node of an event associated with editing of the collection table, and the collection table notification tasks have a priority;

[0012] A task recording unit, used for recording a plurality of the collection table notification tasks into a notification task flow table;

[0013] A target confirmation unit, configured to determine a target notification task from among the plurality of collection table notification tasks based on the priorities of the plurality of collection table notification tasks in the notification task flow table;

[0014] The notification sending unit is used to send the target notification task to a notification center, and the notification center notifies the counterpart node in the target notification task of the event in the target notification task.

[0015] Optionally, the collection table notification task further has an object identifier of an object that edits the collection table;

[0016] The target confirmation unit is specifically used for:

[0017] Based on the priorities of the plurality of collection table notification tasks corresponding to the same object identifier in the notification task flow table, a target notification task is determined from the plurality of collection table notification tasks corresponding to the object identifier.

[0018] Optionally, the target confirmation unit is specifically used to:

[0019] For each of the object identifiers, determining the number of notification tasks in the first collection table corresponding to the object identifier in the notification task flow table;

[0020] Determine a target object identifier based on the number of notification tasks in the first collection table corresponding to each of the object identifiers;

[0021] Based on the priorities of the plurality of collection table notification tasks corresponding to the target object identifier in the notification task flow table, a target notification task is determined from the plurality of collection table notification tasks corresponding to the target object identifier.

[0022] Optionally, the target object identifier is a plurality of target object identifiers; the notification center includes a plurality of processes corresponding to the plurality of target object identifiers;

[0023] The target confirmation unit is specifically used to: for each target object identifier, based on the priority of the multiple collection table notification tasks corresponding to the target object identifier in the notification task flow table, determine the target notification task corresponding to the target object identifier among the multiple collection table notification tasks corresponding to the target object identifier;

[0024] The notification sending unit is specifically used to send the target notification task corresponding to each target object identifier to the notification center, and the process corresponding to each target object identifier notifies the counterparty node in the target notification task of the event in the target notification task corresponding to the target object identifier.

[0025] Optionally, the target confirmation unit is specifically used to:

[0026] For the collection table notification task corresponding to the target object identifier and having the same priority level, obtaining the recording time of the collection table notification task being recorded in the notification task flow table;

[0027] Based on the priority and the recording time, a target notification task is determined from a plurality of collection table notification tasks corresponding to the target object identifier.

[0028] Optionally, the target confirmation unit is specifically used to:

[0029] Obtaining a batch maximum task quantity of each batch of the target notification tasks sent to the notification center;

[0030] Arrange the plurality of collection table notification tasks corresponding to the target object identifier in descending order of priority, and arrange the collection table notification tasks of the same priority in descending order of recording time, thereby forming a scheduling sequence;

[0031] The collection table notification tasks are sequentially taken out from the scheduling sequence according to the maximum task quantity of the batch as the target notification tasks of the batch.

[0032] Optionally, the target confirmation unit is specifically used to:

[0033] Determine a first score of each of the collection table notification tasks based on the priority of each of the collection table notification tasks corresponding to the target object identifier;

[0034] Determine a second score of each of the collection table notification tasks based on the recording time of each of the collection table notification tasks corresponding to the target object identifier;

[0035] Determining a total score of each of the collection form notification tasks based on the first score and the second score;

[0036] Based on the total score, the target notification task is determined from a plurality of notification tasks in the collection table corresponding to the target object identifier.

[0037] Optionally, the collection table notification task further has a task type, a collection table identifier, and an object identifier of an object that edits the collection table;

[0038] The collection table notification task scheduling device also includes:

[0039] The first determining unit is used to determine that there are multiple notification tasks to be deduplicated in the notification task flow table, the task type of which is a reminder type, the collection table identifier is the same, and the object identifier is the same;

[0040] The task deduplication unit is used to deduplicate the multiple notification tasks to be deduplicated so as to retain only one notification task to be deduplicated.

[0041] Optionally, the first determining unit is specifically configured to:

[0042] Filter out the collection table notification tasks whose task type is a reminder type from the notification task flow table;

[0043] Classifying the filtered collection table notification tasks according to the collection table identifiers to obtain multiple classes;

[0044] Classify the collection table notification tasks under each of the classes according to the object identifiers to obtain multiple subclasses;

[0045] If there are multiple collection table notification tasks under one subclass, the multiple collection table notification tasks under the subclass are determined as multiple notification tasks to be deduplicated.

[0046] Optionally, the collection table notification task further includes a task type, a collection table identifier, and task content;

[0047] The collection table notification task scheduling device also includes:

[0048] The second determining unit is used to determine that there are multiple notification tasks to be merged in the notification task flow table, the task type of which is the collection table edit notification type and the collection table identifier is the same;

[0049] A generating and merging unit is used to generate a merged notification task, wherein the task content of the merged notification task is the union of the task contents of the multiple notification tasks to be merged;

[0050] The task replacement unit is used to replace the plurality of notification tasks to be merged with the merged notification task in the notification task flow table.

[0051] Optionally, the collection table notification task also has a task status;

[0052] The collection table notification task scheduling device also includes:

[0053] a state setting unit, configured to set the task state of the target notification task in the notification task flow table to a first state if the notification is successful;

[0054] The target confirmation unit is specifically configured to determine the target notification task from among the plurality of collection table notification tasks based on the priorities of the plurality of collection table notification tasks whose task states are not the first state in the notification task flow table.

[0055] Optionally, the target confirmation unit is executed periodically, and the collection table notifies the task scheduling device further comprising:

[0056] An indicator acquisition unit, used to acquire expected timeliness indicators;

[0057] A number acquisition unit, used to acquire the average number of the collection table notification tasks generated per unit time;

[0058] A period determination unit is used to determine the period based on the expected timeliness indicator and the average number.

[0059] Optionally, the target confirmation unit is specifically used to:

[0060] Determine in real time the number of notification tasks in the second collection table whose task status is not the first status in the notification task flow table;

[0061] If the number of notification tasks in the second collection table is greater than a first threshold, the target notification task is determined from among the plurality of notification tasks in the collection table based on the priorities of the plurality of notification tasks in the notification task flow table whose task states are not the first state.

[0062] Optionally, the task recording unit is specifically used for:

[0063] storing a plurality of the collection table notification tasks in a queue;

[0064] The collection table notification task is taken out from the queue by using a queue consumer, and recorded in the notification task flow table.

[0065] Optionally, the queue is a plurality of queues, and the collection table notification task has a collection table identifier;

[0066] The task recording unit is specifically used for:

[0067] Determine a consistent hash value of the collection table identifier of the collection table notification task;

[0068] Based on the consistent hash value, determining an allocation queue among the plurality of queues;

[0069] The collection table notification task is stored in the allocation queue.

[0070] Optionally, the queue consumer is a plurality of queue consumers corresponding one-to-one to the plurality of queues;

[0071] The task recording unit is specifically used for:

[0072] By using the multiple queue consumers corresponding to the multiple queues, the collection table notification tasks are taken out from the queues at the same time, and recorded in the notification task flow table at the same time.

[0073] Optionally, the task acquisition unit is specifically used to: receive the collection table notification task of the collection table edit notification type from the object terminal, the collection table notification task of the collection table edit notification type is generated in response to the object editing the collection table, the event associated with the editing of the collection table is an edit event, and the counterpart node is an administrator terminal;

[0074] The notification sending unit is specifically used to: notify the administrator terminal of the editing event.

[0075] Optionally, the task acquisition unit is specifically used to: receive the collection form notification task of the urging filling type from an administrator terminal, the collection form notification task of the urging filling type is generated in response to the administrator issuing an urging filling instruction for the collection form to be urged to be filled, the event associated with the editing of the collection form is an urging filling event, and the counterparty node is the object terminal of the object to be urged to be filled;

[0076] The notification sending unit is specifically configured to notify the object terminal of the object to be urged to fill in the urging event.

[0077] Optionally, the task acquisition unit is specifically used to: receive the collection form notification task of a reminder type from an object terminal or an administrator terminal, the collection form notification task of the reminder type is generated in response to a filling reminder condition set by the object or the administrator for the collection form becoming satisfied, the event associated with the editing of the collection form is a reminder event, and the counterparty node is the object terminal or the administrator terminal that sets the filling reminder condition;

[0078] The notification sending unit is specifically used for notifying the reminder event to the target terminal or the administrator terminal that sets the filling reminder condition.

[0079] According to one aspect of the present disclosure, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the collection table notification task scheduling method as described above when executing the computer program.

[0080] According to one aspect of the present disclosure, a computer-readable storage medium is provided, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, the collection table notification task scheduling method as described above is implemented.

[0081] According to one aspect of the present disclosure, a computer program product is provided. The computer program product includes a computer program. The computer program is read and executed by a processor of a computer device, so that the computer device executes the collection table notification task scheduling method as described above.

[0082] The disclosed embodiment decouples the generation system and the issuance system of the collection table notification tasks not through a queue but through a task flow table. After obtaining the multiple generated collection table notification tasks, they are placed in the task flow table for storage. Then, the collection table notification tasks are taken out one by one from the task flow table to perform the tasks. In this way, even when the generation speed of the collection table notification tasks is much faster than the issuance speed, they will not be lost because they are stored in the task flow table. In the disclosed embodiment, the collection table notification tasks stored in the task flow table have priorities. In the task flow table, the target notification task can be determined from the multiple collection table notification tasks according to the priority of each task, and sent to the notification center for notification first, so as to ensure the immediacy of the notification of important notifications and improve the timeliness of the execution of the collection table notification tasks.

[0083] Other features and advantages of the present disclosure will be described in the following description, and partly become apparent from the description, or understood by practicing the present disclosure. The purpose and other advantages of the present disclosure can be realized and obtained by the structures particularly pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0084] The accompanying drawings are used to provide further understanding of the technical solution of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the technical solution of the present disclosure and do not constitute a limitation on the technical solution of the present disclosure.

[0085] Figure 1 It is a system architecture diagram of a system to which the collection table notification task scheduling method is applied according to an embodiment of the present disclosure;

[0086] FIG. 2A to FIG. 2C It is a schematic diagram of an interface in which the collection table notification task scheduling method according to an embodiment of the present disclosure is applied to a scenario of urging filling;

[0087] Figure 3 is an overall flow chart of a collection table notification task scheduling method according to an embodiment of the present disclosure;

[0088] Figure 4 It is a schematic diagram of the task priority queue;

[0089] Figure 5 is a schematic diagram of a collection table notification task scheduling method according to an embodiment of the present disclosure;

[0090] Figure 6 yes Figure 3 A specific flow chart of step 310 and step 340;

[0091] FIG. 7A to FIG. 7B It is a schematic diagram of an interface in which the collection table notification task scheduling method according to an embodiment of the present disclosure is applied to a collection table editing notification scenario;

[0092] Figure 8 yes Figure 3 Another specific flow chart of step 310 and step 340;

[0093] Fig. 9 yes Figure 3 Another specific flow chart of step 310 and step 340;

[0094] FIG. 10A to FIG. 10D It is a schematic diagram of an interface in which the collection table notification task scheduling method according to an embodiment of the present disclosure is applied to a reminder scenario;

[0095] Fig.11 yes Figure 3 A specific flow chart of step 320 in FIG.

[0096] Fig.12 yes Fig.11 A specific flow chart of step 1110 in FIG.

[0097] Fig.13It is a schematic diagram of collecting table notification task records to notification task flow table according to an embodiment of the present disclosure;

[0098] Fig.14 yes Fig.11 A specific flow chart of step 1120 in FIG.

[0099] Fig.15 yes Figure 3 A specific flow chart of step 330;

[0100] Fig.16 is a schematic diagram of a notification task flow table provided according to an embodiment of the present disclosure;

[0101] Fig.17 yes Fig.15 A specific flow chart of step 1510;

[0102] Fig.18 yes Fig.17 A specific flow chart of step 1730 in FIG.

[0103] Fig.19 yes Fig.17 Another specific flow chart of step 1720;

[0104] Fig. 20 yes Fig.19 A specific flow chart of step 1920 in FIG.

[0105] Fig.21 yes Fig.19 Another specific flow chart of step 1920;

[0106] Fig. 22 It is a flow chart of deduplication of a collection table notification task of a collection table notification task scheduling method according to an embodiment of the present disclosure;

[0107] Fig.23 yes Fig. 22 Another specific flow chart of step 2210;

[0108] Fig.24 It is a flow chart of the collection table notification task merging of the collection table notification task scheduling method according to an embodiment of the present disclosure;

[0109] Fig.25 It is a flow chart of setting the task state of a collection table notification task of a collection table notification task scheduling method according to an embodiment of the present disclosure;

[0110] Fig.26 It is a specific flow chart for cycle setting;

[0111] Fig. 27 yes Fig.25A specific flow chart of step 2520 in FIG.

[0112] Fig.28 is a block diagram of a collection table notification task scheduling device according to an embodiment of the present disclosure;

[0113] Fig.29 An embodiment according to the present disclosure is shown. Figure 3 The terminal structure diagram of the collection table notification task scheduling method shown;

[0114] Fig.30 An embodiment according to the present disclosure is shown. Figure 3 The server structure diagram of the collection table notification task scheduling method shown. DETAILED DESCRIPTION

[0115] In order to make the purpose, technical solution and advantages of the present disclosure more clear, the present disclosure is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present disclosure and are not used to limit the present disclosure.

[0116] Before further describing the embodiments of the present disclosure in detail, the nouns and terms involved in the embodiments of the present disclosure are described. The nouns and terms involved in the embodiments of the present disclosure are subject to the following interpretations:

[0117] Collection form: A form consisting of one or more questions. Collection forms are usually created by collectors. The filler can fill in the form content according to the questions and submit it. The collector can check the submission results of all fillers.

[0118] Online form: Corresponding to the collection form, one online form corresponds to multiple collection forms. The online form records the submission results of all fillers for the collection form. The collector can check the submission results of all fillers through the online form.

[0119] Administrator: A form administrator, also known as an online form administrator, is the owner or creator of a collection form. He or she can view the contents of the online form and manage the online form on the online form end.

[0120] Form filler: also known as collection form filler, is the person who fills in the collection form. He or she can fill in the collection form and submit, modify, delete, and perform other operations on the collection form.

[0121] Collection forms and online forms are two commonly used online documents on the Internet. In the collection form, the filler fills in the answer to the question. The online form summarizes the submission results of multiple fillers for the collection form in the form of a table, and the collector checks the submission results of multiple fillers through the online form. In the process of transferring the data of the collection form to the online form for summary scheduling, the administrator of the online form side usually needs to urge the user who has not submitted the collection form to fill it out, or when the filler of the collection form submits, modifies, etc. the collection form, it is necessary to remind the administrator of the online form side. Therefore, a large number of collection form notification tasks are usually generated in a short period of time, and the speed of sending the collection form notification tasks to the collection form side or the online form side is relatively slow. The throughput difference between the generation and sending of the collection form notification tasks is large. When the generation speed of the collection form notification tasks is much faster than the sending speed, loss will occur.

[0122] At present, the collection table notification task scheduling method decouples the generation system and the issuance system of the collection table notification task through an asynchronous queue. Multiple queues are set between the collection table end or the online table end that generates the notification and the notification center. When the collection table notification task is generated, it is stored in the queue. When the notification center notifies, the collection table notification tasks are taken out one by one from the queue according to the first-in-first-out principle and notified. Since the queue plays the role of storing the collection table notification tasks that have not been notified, when the generation speed of the collection table notification tasks is much faster than the issuance speed, they will not be lost because they are stored in the queue. The disadvantage of this solution is that the notification tasks in the queue are in an equal position, and the consumers will take them out one by one and send them to the notification center. Some important notification tasks will be blocked by some less important notification tasks and will not be notified for a long time. In addition, some notification tasks have a strong timeliness, and it is no longer effective to notify them after a period of time. That is, the immediacy and lack of timeliness of important notifications cannot be guaranteed.

[0123] In addition, in the related art, an online form may correspond to millions of collection forms. If the administrator clicks the one-click reminder function multiple times in a short period of time, that is, repeatedly urges the form fillers who have not filled in the form to fill in the collection form, then a large number of notification tasks will be generated in a short period of time, and the form fillers will be frequently disturbed by the same message.

[0124] Based on this, the embodiments of the present disclosure provide a collection table notification task scheduling method, related devices and media, which can ensure the immediacy and timeliness of important notification tasks.

[0125] System architecture and scenario description of the application of the embodiments of the present disclosure

[0126] Figure 1The system architecture diagram is applied to the collection table notification task scheduling method according to the embodiment of the present disclosure, and includes a collection table notification task scheduling server 110, the Internet 120, a terminal 130, and the like.

[0127] The collection table notification task scheduling server 110 includes an online table node, a collection table node and a notification center, wherein the online table node and the online table node can generate a collection table notification task according to the operation instruction of the event associated with the collection table editing at the corresponding terminal 130, the notification center is a device that sends the event in the notification task to the terminal 130, and the online table node, the collection table node and the notification center are connected in communication. Relative to the terminal 130, the collection table notification task scheduling server 110 has very high requirements in terms of stability, security, performance, etc. The server 110 can be a high-performance computer in a network platform, a cluster of multiple high-performance computers, a part of a high-performance computer (such as a virtual machine), a combination of parts of multiple high-performance computers (such as virtual machines), etc. The collection table notification task scheduling server 110 can also communicate with the Internet 120 in a wired or wireless manner to exchange data.

[0128] The terminal 130 is a device used to display the events corresponding to the target notification task. The terminal 130 can be divided into an online form terminal and a collection table terminal. It includes various forms such as touch screen terminals, desktop computers, laptops, PDAs (personal digital assistants), mobile phones, car terminals, home theater terminals, and dedicated terminals. In addition, it can be a single device or a collection of multiple devices. For example, multiple devices are connected through a local area network and share a display device to work together to form a terminal. The terminal 130 can also communicate with the Internet 120 in a wired or wireless manner to exchange data, wherein the online form terminal communicates with the online form node through the Internet 120, and the collection table terminal communicates with the collection table node through the Internet 120. In addition, the notification center communicates with the online form terminal and the collection table terminal through the Internet 120.

[0129] The embodiments of the present disclosure can be applied to any scenario using a notification task scheduling service, such as FIG. 2A to FIG. 2B The scene shown.

[0130] like Figure 2A As shown, Figure 2A It is the interface of the online form. This interface displays the online form. The online form shows the content of the collection form submitted by each user and the submission time. According to the online form, it can be known that user C, user E, etc. have not filled in the online form. At this time, the administrator can click the "One-click Reminder" button to remind users who have not filled in the collection form to fill in the collection form.

[0131] After the administrator clicks the "One-click Request" button, a collection form notification task is generated based on the request event. The request event is generated to urge users to fill in the collection form, and its corresponding collection form notification task has a higher priority. The related technology sets an asynchronous queue between the collection form end, the online form end and the notification center, and sends the collection form notification task to the notification center through the asynchronous queue. The queue follows the first-in-first-out principle, and the notification task with a higher priority may be blocked in the queue and cannot be taken out in time. The user may not receive the request event before the collection form filling deadline.

[0132] Figure 2B and Figure 2C These are two different notification modes for scheduling notification tasks according to the collection table notification task scheduling method provided in the embodiment of the present disclosure, but user C received the same notification as Figure 2A The online form has the same collection form ID, that is, the collection form due for completion notice with ID A.

[0133] The disclosed embodiment can preferentially send notification tasks with higher priorities to counterparty nodes, thereby ensuring the immediacy and timeliness of important notifications.

[0134] It should be understood that the above content only illustrates some application scenarios of the present disclosure, and the business scenarios to which the present disclosure can be applied may include, but are not limited to, the specific embodiments listed above.

[0135] General description of the disclosed embodiments

[0136] It should be emphasized that the embodiments of the present disclosure can be applied to a variety of application scenarios, such as reminders for filling out notifications, reminders of impending deadlines, and notifications for filling out collection forms. The collection form notification task scheduling method of the related art has the problem that the timeliness of important notification tasks cannot be guaranteed. According to some embodiments of the present disclosure, a collection form notification task scheduling service method, related devices and media are provided, which can send notification tasks with higher priority, that is, important notification tasks, to the counterparty node first, thereby ensuring the immediacy and timeliness of important notifications.

[0137] The collection table notification task scheduling service method is a method for processing the collection table notification task and sending it to the notification center to notify the corresponding event to the counterpart node. The collection table notification task scheduling method can send notification tasks with higher priority, that is, important notification tasks, to the counterpart node first, thereby ensuring the immediacy and timeliness of important notifications.

[0138] The collection table notification task scheduling method of the embodiment of the present disclosure obtains the collection table notification task from the terminal 130, processes the collection table notification task in the collection table notification task scheduling processor 110, and sends the collection table notification task to the notification center, and the notification center notifies the corresponding counterpart node, i.e., the terminal 130, of the time in the target notification task to realize the scheduling processing of the collection table notification task.

[0139] like Figure 3 As shown, according to an embodiment of the present disclosure, a collection table notification task scheduling method may include:

[0140] Step 310: Acquire multiple collection table notification tasks, where the collection table notification tasks are used to notify the counterparty node of the event associated with the editing of the collection table, and the collection table notification tasks have a priority;

[0141] Step 320, recording multiple collection table notification tasks into the notification task flow table;

[0142] Step 330: Determine a target notification task from among the multiple collection table notification tasks based on the priorities of the multiple collection table notification tasks in the notification task flow table;

[0143] Step 340: Send the target notification task to the notification center, and the notification center notifies the counterparty node in the target notification task of the event in the target notification task.

[0144] Steps 310 to 340 are briefly described below.

[0145] In step 310, multiple collection table notification tasks are obtained, and the collection table notification tasks are used to notify the event-related event associated with the collection table editing to the counterpart node of the event, and the collection table notification tasks have a priority. The object operates on the terminal, generates an event associated with the collection table editing, and then determines the collection table notification task.

[0146] There are various times associated with the editing of a collection form. Specifically, when an object performs editing operations such as deletion, submission, and modification on a collection form, a corresponding event may be generated. Alternatively, when an administrator prompts a user who has not filled out a collection form with one click on the online form side, a corresponding event may be generated.

[0147] The counterpart node can be one of the collection table end and the online table end, or can be the collection table end and the online table end. Different collection table notification tasks correspond to different counterpart nodes.

[0148] The collection table notification task has a priority, which represents the importance of the event in the collection table notification task. The priority of the collection table notification task is usually related to the task type and the collection table identifier. For the collection table notification tasks under the same collection table identifier, the priorities of the collection table notification tasks with different task types are different. For the collection table notification tasks under multiple collection table identifiers, the priorities corresponding to the collection table notification tasks with different collection table identifiers may also be different.

[0149] In step 320, multiple collection table notification tasks are recorded in a notification task flow table. The notification task flow table is used to record and store collection table notification tasks. Compared with a queue, the order of taking out collection table notification tasks in the notification task flow table is not restricted in any way.

[0150] The collection table notification tasks can be recorded in the notification task flow table based on different bases. For example, based on the generation time of the collection table notification tasks, multiple collection table notification tasks can be recorded in the notification task flow table so that the collection table notification tasks are arranged in the notification task flow table in the order of generation time. In addition, multiple collection table notification tasks can also be sorted according to the corresponding collection table identifier, task type or priority. Since the order of taking out the collection table notification tasks in the notification task flow table is not subject to any restrictions, the collection table notification tasks can be arranged in any order in the notification task flow table.

[0151] In step 330, based on the priorities of the multiple collection table notification tasks in the notification task flow table, a target notification task is determined from the multiple collection table notification tasks. The collection table notification task has a priority, and the more important the event in the collection table notification task, the higher its priority. Based on the priorities of the multiple collection table notification tasks in the notification task flow table, one or more collection table notification tasks with the highest priority are determined as target notification tasks.

[0152] In one embodiment, referring to Figure 4 , Figure 4 A method for determining the target notification task based on the task priority queue. Different collection table notification tasks have different priorities. The priorities of collection table notification tasks are stored in the task priority queue from low to high. Figure 4 In the task priority queue shown, Q0 corresponds to the lowest priority and Q2 corresponds to the highest priority. The task priority queue follows the first-in-last-out principle, that is, Q2 is the first priority to be taken out and Q0 is the last priority to be taken out. When the priority taken out from the task priority queue is Q2, the collection table notification task with priority Q2 in the notification task flow table is searched and the found collection table notification task is used as the target notification task.

[0153] in addition, Figure 4This is just an example of a task priority queue. The priority of the task notified by the collection table can also be stored in the task priority queue in descending order. Correspondingly, the task priority follows the first-in-first-out principle, that is, Q2 is the first priority stored in, and Q2 is also the first priority taken out.

[0154] The priority of the collection table notification task can also be stored in the priority flow table, so multiple priorities can be arranged arbitrarily in the priority flow table, and the collection table notification task can be arranged arbitrarily in the notification task flow table. Therefore, the embodiment of the present disclosure usually determines the priority of the retrieval according to the task priority queue or based on the priorities of multiple collection table notification tasks in the notification task flow table, directly determines the priority corresponding to the target notification task.

[0155] In step 340, the target notification task is sent to the notification center, and the notification center notifies the counterparty node in the target notification task of the events in the target notification task. After the target notification task is determined based on the priority of the collection table notification task, the target notification task is taken out from the notification task flow table and sent to the notification center. The notification center is a device that sends the received events in the target notification task to the counterparty node. If the target notification task is one or more collection table notification tasks with the highest priority in the notification task flow table, then the events that the counterparty node receives first are important notification events.

[0156] In one embodiment, referring to Figure 5 In the process of executing the collection table notification task scheduling method, the collection table notification task is first obtained, and the collection table notification task record is stored in the notification task flow table. Then, one or more collection table notification tasks with the highest priority in the notification task flow table are determined as target notification tasks, and the target notification tasks are sent to the notification center so that the notification center notifies the counterpart node of the events related to the collection table editing corresponding to the collection table notification tasks. The determination of the target notification tasks enables the collection table notification tasks with higher priorities to be sent to the notification center first, and the corresponding events to be sent to the counterpart node first, thereby ensuring the immediacy and timeliness of important notifications.

[0157] The above-mentioned embodiments of steps 310 to 340 obtain multiple collection table notification tasks, each of which has a corresponding priority. The collection table notification tasks are then recorded in the notification task flow table. According to the priorities of the multiple collection table notification tasks in the notification task flow table, a target notification task is determined among the multiple collection table notification tasks, and the priority of the target notification task is higher than that of other collection table notification tasks. The target notification task is sent to the task center, and the task center notifies the counterparty node in the target notification task of the event in the collection table notification task. Since different collection table notification tasks have different corresponding priorities, in the notification task flow table, some collection table notification tasks with higher priorities can be determined as target notification tasks according to the priorities of each collection table notification task, and sent to the notification center to give priority to notifying the corresponding counterparty nodes, so that notification tasks with higher priorities, that is, important notification tasks, can be sent to the counterparty nodes first, thereby ensuring the immediacy and timeliness of important notifications.

[0158] The above is a general description of step 310 to step 340. Step 310 to step 340 are described in detail below. Since step 310 and step 340 are closely related, they are described together. Step 320 and step 330 are described in detail separately.

[0159] Detailed description of step 310 and step 340

[0160] In step 310, a plurality of collection table notification tasks are obtained, where the collection table notification tasks are used to notify the counterparty node of the event associated with the editing of the collection table, and the collection table notification tasks have priorities.

[0161] In step 340, the target notification task is sent to the notification center, and the notification center notifies the counterparty node in the target notification task of the event in the target notification task.

[0162] Reference Figure 6 In one embodiment, step 310 includes:

[0163] Step 610: Receive a collection table notification task of a collection table edit notification type from the object terminal. The collection table edit notification type collection table notification task is generated in response to the object editing the collection table. The event associated with the collection table editing is an edit event, and the counterpart node is the administrator terminal.

[0164] Corresponding to step 610, step 340 includes:

[0165] Step 620: Notify the administrator terminal of the editing event.

[0166] Step 610 and step 620 are described in detail below.

[0167] In step 610, a collection table notification task of a collection table edit notification type is received from the object terminal. The collection table edit notification type collection table notification task is generated in response to the object editing the collection table. The event associated with the editing of the collection table is an edit event. The counterpart node is the administrator terminal. The object terminal is the collection table terminal, and the administrator terminal is the online form terminal. The object performs editing operations such as filling in, modifying, and deleting the collection table at the object terminal, and a collection table notification task of a collection table edit notification type is generated.

[0168] After the object edits the collection table at the object terminal, the administrator needs to be notified that the object has edited the collection table. Therefore, in response to the object editing the collection table, a collection table notification task of the collection table edit notification type is generated, the event under the collection table notification task is an edit event, and the counterpart node is the administrator terminal.

[0169] In step 620, the administrator terminal is notified of the edit event. After the collection table notification task of the collection table edit notification type is generated, the collection table notification task is processed based on steps 320 and 330 to determine the target notification task. When the target notification task is the collection table notification task of the collection table edit notification type, the administrator terminal is notified of the edit event in the collection table notification task to remind the object that the collection table has been edited.

[0170] In one embodiment, referring to Fig. 7A , user A modifies the filled collection form on the collection form end, i.e., the object terminal, and clicks the "Modify" button to synchronize the modified collection form content to the online form, and generates an edit event, thereby determining a collection form notification task of the collection form edit notification type. After processing the collection form notification task based on the collection form notification task scheduling method of the embodiment of the present disclosure, the administrator terminal is notified of the edit event. The interface of the administrator terminal is as shown in FIG. Figure 7B As shown, the interface is specifically the notification reminder interface of the software used by the online form, or the interface of the public account associated with the online form. The interface displays a collaborative editing notification, which displays the collaborative content, collaborators, and collaborative time. Among them, the collaborator is the object that edits the collection form, that is, user A, the collaborative content is the content edited by user A on the collection form, and the collaborative time is the time when user A edited the collection form. In addition, Fig. 7A The interface shown also includes the time of collaborative editing notification. The higher the priority of the collection table notification task, the closer the notification time is to the collaborative time.

[0171] In addition, when the administrator clicks the collaborative editing notification, the interface of the online form will appear. The online form is synchronized based on the collection form edited by user A.

[0172] The above-mentioned embodiments of step 610 and step 620 show a collection table notification task of the collection table edit notification type, which is generated based on the object's editing operation on the collection table, and the corresponding counterpart node is the administrator terminal. Corresponding to the collection table notification task of the collection table edit notification type, the editing event corresponding to the target notification task is sent to the administrator terminal. The disclosed embodiment is provided with a collection table notification task of the collection table edit notification type, which can notify the administrator terminal of the editing event generated based on the object's editing of the collection table.

[0173] Reference Figure 8 In one embodiment, step 310 includes:

[0174] Step 810: Receive a collection form notification task of the urging filling type from the administrator terminal. The collection form notification task of the urging filling type is generated in response to the urging filling instruction issued by the administrator to the object to be urged to fill in the collection form. The event associated with the editing of the collection form is the urging filling event, and the counterpart node is the object terminal of the object to be urged to fill in.

[0175] Corresponding to step 810, step 340 includes:

[0176] Step 820: Notify the object terminal of the object to be urged to fill in the form of the urging event.

[0177] Step 810 and step 820 are described in detail below.

[0178] In step 810, a collection form notification task of a urging filling type is received from the administrator terminal. The collection form notification task of a urging filling type is generated in response to an urging filling instruction issued by the administrator to the object to be urged to fill in the collection form. The event associated with the editing of the collection form is an urging filling event, and the counterparty node is the object terminal of the object to be urged to fill in. When the online form of the administrator terminal shows that there is a collection form notification task for an object not filled in, the administrator can issue a urging filling instruction to the object that has not filled in the collection form, that is, the object to be urged to fill in, and generate a collection form notification task of a urging filling type based on the urging filling instruction. The event in the collection form notification task is an urging filling event, and the counterparty node is the object terminal of the object that has not filled in the collection form.

[0179] In step 820, the object terminal of the object to be urged is notified of the urging event. After the collection form notification task of the urging type is generated, the collection form notification task is processed based on steps 320 and 330 to determine the target notification task. When the target notification task is a collection form notification task of the urging type, the object terminal of the object to be urged is notified of the urging event in the collection form notification task to remind the object to be urged to fill in the collection form.

[0180] In one embodiment, referring to Figure 2A, the online form on the administrator terminal displays the content of the collection form submitted by each user and the submission time, and displays that user C, user E, etc. have not yet filled in the online form. At this time, the administrator can click the "one-click urging filling" button to issue a urging filling instruction to the object to be urged to fill in the collection form, and generate a collection form notification task of the urging filling type based on the urging filling instruction. After the collection form notification task is processed by the collection form notification task scheduling method based on the embodiment of the present disclosure, the urging filling event is notified to the object terminal of the object to be urged to fill in, and the interface of the object terminal of the object to be urged to fill in is as shown in FIG. Figure 2B or Figure 2C shown.

[0181] Figure 2B The collection form interface of the object terminal of the object to be urged to fill in includes a collection form due filling notification, which corresponds to the online form and the collection form, and displays the collection form identifier corresponding to the collection form, that is, identifier A. The collection form due filling notification displays the filling deadline and reminds the object to be urged to fill in, such as user C, to fill in the collection form as soon as possible.

[0182] Figure 2C The interface shown is specifically a notification reminder interface of the software used by the online form, or an interface of a public account associated with the online form, which displays a due filling notification, which displays the notification object, the filling form and the deadline. Among them, the notification object is the object to be urged to fill in, the filling form is the collection form identifier of the collection form to be filled in, and the deadline is the submission deadline of the collection form to be filled in. Figure 2C The interface shown also includes the time for the due filling notification. The higher the priority of the collection form notification task, the closer the notification time is to the time when the reminder filling instruction is issued.

[0183] In addition, when the object to be filled in is clicked Figure 2C When the due filling notification is shown, a collection form interface is displayed, and the object to be reminded to fill in the collection form can complete the filling in of the collection form on this interface.

[0184] The above-mentioned embodiments of step 810 and step 820 show a collection form notification task of the urging filling type. The collection form notification task of the urging filling type is generated based on the urging filling instruction issued by the administrator to the object to be urged to fill in the collection form. The corresponding counterparty node is the object terminal of the object to be urged to fill in. Corresponding to the collection form notification task of the urging filling notification type, the urging filling event corresponding to the target notification task is sent to the object terminal of the object to be urged to fill in. The disclosed embodiment is provided with a collection form notification task of the urging filling type, which can timely remind the object who has not filled in the collection form to fill in the collection form in time.

[0185] Reference Fig. 9 In one embodiment, step 310 includes:

[0186] Step 910: Receive a reminder type collection form notification task from the object terminal or the administrator terminal. The reminder type collection form notification task is generated in response to the filling reminder condition set by the object or the administrator for the collection form being met. The event associated with the editing of the collection form is a reminder event, and the counterpart node is the object terminal or the administrator terminal that sets the filling reminder condition.

[0187] Corresponding to step 910, step 320 includes:

[0188] Step 920: Notify the reminder event to the target terminal or administrator terminal that has filled in the reminder condition.

[0189] Step 910 and step 920 are described in detail below.

[0190] In step 910, a collection table notification task of a reminder type is received from an object terminal or an administrator terminal. The collection table notification task of the reminder type is generated in response to the filling reminder condition set by the object or the administrator for the collection table becoming satisfied. The event associated with the editing of the collection table is a reminder event, and the counterparty node is the object terminal or the administrator terminal that sets the filling reminder condition. The object or the administrator can set the filling reminder condition for the collection table according to the needs. When the filling reminder condition is satisfied, a collection table notification task of the reminder type is generated. The event in the collection table notification task is the reminder time, and the counterparty node is the object terminal or the administrator terminal that sets the filling reminder condition.

[0191] The filling reminder condition is set by the object or administrator according to their own needs. Specifically, when the filling reminder condition is set for the object, the reminder event is mainly used to remind the object to fill in the collection form in time. When the filling reminder condition is set for the administrator, the reminder event is mainly used to remind the administrator to check the online form and urge the object who has not filled in the collection form to fill in.

[0192] In step 920, the reminder event notification setting fills in the object terminal or administrator terminal of the reminder condition. After the collection table notification task of the reminder type is generated, the collection table notification task is processed based on steps 320 and 330 to determine the target notification task. When the target notification task is a collection table notification task of the reminder type, the reminder event notification setting in the collection table notification task fills in the object terminal or administrator terminal of the reminder condition.

[0193] In one embodiment, referring to Fig. 10A , Fig. 10AThe desktop interface of the object terminal of user D includes a desktop reminder. When user D clicks the desktop reminder, a desktop reminder setting box is displayed. In the desktop reminder setting box, user D can set the filling reminder conditions. The filling reminder conditions include setting the time, that is, filling the reminder time. In addition, user D also needs to set the collection form identifier and the deadline of the collection form.

[0194] When the filling reminder time is met, that is, the current time is the filling reminder time, a collection table notification task of the reminder type is generated. After the collection table notification task of the reminder type is processed by the collection table notification task scheduling method based on the embodiment of the present disclosure, the reminder event is notified to the object terminal that sets the filling reminder condition. The interface of the object terminal that sets the filling reminder condition is as follows: Fig. 10B shown.

[0195] Fig. 10B The interface of the object terminal for setting filling reminder conditions includes a desktop reminder, which is used to remind user D to fill in the collection form marked A and display the deadline for filling in the collection form.

[0196] In another embodiment, referring to 10C, Fig. 10C The desktop interface of the administrator's terminal includes a desktop reminder. When the administrator clicks on the desktop reminder, the desktop reminder setting box is displayed. In the desktop reminder setting box, the administrator can set the reminder conditions. The reminder conditions include the setting time, i.e., the desktop reminder time. In addition, the administrator also needs to set the collection form ID corresponding to the online form of the desktop reminder and the collection form filling deadline.

[0197] When the set time is met, a collection table notification task of the reminder type is generated. After processing the collection table notification task of the reminder type based on the collection table notification task scheduling method of the embodiment of the present disclosure, the reminder event is notified to the administrator terminal that sets the reminder conditions. The interface of the administrator terminal that sets the reminder conditions is as follows: Fig. 10D shown.

[0198] Fig. 10D The interface shown includes a desktop reminder, which is used to remind the administrator to check whether the collection form corresponding to the online form has been filled out. If it has not been filled out, the administrator is reminded to urge the users who have not filled out the form to fill it out with one click.

[0199] The above-mentioned embodiments of step 910 and step 920 show a collection table notification task of a reminder type. The collection table notification task of a reminder type is generated based on the filling reminder condition set by the object or administrator for the collection table becoming satisfied. The corresponding counterparty node is the object terminal or administrator terminal that sets the filling reminder condition. Corresponding to the collection table notification task of the reminder notification type, the reminder event corresponding to the target notification task is sent to the object terminal or administrator terminal that sets the filling reminder condition. The disclosed embodiment is provided with a collection table notification task of a reminder type. The collection table notification task is set by the object or administrator according to their own needs, and can timely remind the object or administrator that sets the filling reminder condition to perform the operation.

[0200] In one embodiment, the task type of the collection form notification task is form capacity overlimit notification. When too many collection forms are submitted and the online form cannot be recorded, the administrator terminal is notified that the form capacity exceeds the limit, so that the administrator can end the filling of the collection form corresponding to the online form in advance.

[0201] Detailed description of step 320

[0202] In step 320, a plurality of the collection table notification tasks are recorded into a notification task flow table.

[0203] Reference Fig.11 In one embodiment, step 320 includes:

[0204] Step 1110, storing multiple collection table notification tasks in a queue;

[0205] Step 1120: Use the queue consumer to take out the collection table notification task from the queue and record it in the notification task flow table.

[0206] Step 1110 and step 1120 are described in detail below.

[0207] In step 1110, multiple collection table notification tasks are stored in a queue. The number of queues is not limited. In the embodiment of the present disclosure, the collection table notification tasks can be stored in one queue or in multiple queues. When multiple queues are set, the multiple queues are set in parallel, which is an asynchronous queue.

[0208] The queue is set between the collection table node, the online table node and the notification task flow table. The queue serves as a transit station for the collection table notification task records to the notification task flow table. It can buffer the collection table notification tasks and decouple the collection table notification task generation system with different throughputs and the collection table notification task system issued by the notification center.

[0209] In step 1120, the collection table notification task is taken out from the queue by the queue consumer and recorded in the notification task flow table. The queue consumer can take out the collection table notification task from the queue and record it in the notification task flow table.

[0210] The disclosed embodiment does not limit the number of queue consumers. The number of queue consumers can be the same as the number of queues, so that queue consumers correspond to queues one by one. The number of queue consumers can also be less than the number of queues, or even one, so that a single consumer corresponds to multiple queues.

[0211] In one embodiment, referring to Figure 5 The embodiment of the present disclosure is provided with a queue, and the queue is arranged adjacent to the notification task flow table. After obtaining the collection table notification task, the collection table notification task is stored in the queue, and the collection table notification task in the queue is recorded in the notification task flow table by using the consumer.

[0212] The embodiments of the above steps 1110 and 1220 are provided with a queue, and the multiple collection table notification tasks obtained are stored in the queue, and then the collection table notification tasks are taken out from the queue by the queue consumer and recorded in the notification task flow table. The embodiment of the present disclosure is provided with a queue, and the setting of the queue buffers the process of storing the collection table notification tasks in the notification task flow table, reduces the system crash caused by too much task data, realizes the decoupling of systems with different throughputs, and facilitates the processing of the collection table notification tasks.

[0213] The above is a general description of step 1110 and step 1120. The specific implementation process of step 1110 and step 1120 will be described in detail below.

[0214] In step 1110, a plurality of collection table notification tasks are stored in a queue.

[0215] Reference Fig.12 In one embodiment, the queue is a plurality of queues, the collection table notification task has a collection table identifier, and step 1110 includes:

[0216] Step 1210: determine the consistent hash value of the collection table identifier of the collection table notification task;

[0217] Step 1220: Determine an allocation queue from among multiple queues based on the consistent hash value;

[0218] Step 1230: Store the collection table notification task into the allocation queue.

[0219] Steps 1210 to 1230 are described in detail below.

[0220] In step 1210, the consistent hash value of the collection table identifier of the collection table notification task is determined. The collection table notification task has a collection table identifier, and the online table and the multiple collection tables corresponding to it have the same collection table identifier. According to the collection table identifier, the online table and the collection table corresponding to the collection table notification task can be determined. According to the collection table identifier in the collection table notification task, the consistent hash value is determined. The consistent hash values ​​of the collection table notification tasks under the same collection table identifier are also the same.

[0221] In step 1220, an allocation queue is determined among multiple queues based on the consistent hash value. According to the consistent hash value corresponding to the collection table notification task, an allocation queue is determined among multiple queues so that collection table notification tasks with the same collection table identifier are allocated to the same queue.

[0222] The hash ring corresponding to multiple parallel queues can be determined according to the value range of the hash function output value. After that, hash calculation is performed on multiple queues to determine the position of each queue on the hash ring, and hash calculation is performed on the consistent hash value of the collection table identifier to determine the position of each collection table identifier on the hash ring. Based on the position of the collection table identifier on the hash ring, the nearest queue is searched clockwise to determine the allocation queue corresponding to the collection table identifier.

[0223] In addition, the relationship between the consistent hash value and the allocation queue can be preset, whereby, based on the consistent hash value, the allocation queue corresponding to the collection table identifier can be directly determined from multiple queues.

[0224] In step 1230, the collection table notification task is stored in the allocation queue. After the allocation queue is determined, the collection table notification task is allocated to the allocation queue. The queue has a first-in-first-out principle, so multiple collection table notification tasks are arranged in the allocation queue in chronological order.

[0225] The embodiments of steps 1210 to 1230 above determine the consistent hash value of the collection table identifier in the collection table notification task, and then determine the allocation queue among multiple queues based on the consistent hash value to allocate the collection table notification task to the allocation queue. The disclosed embodiment is provided with a consistent hash value, so that the collection table identifier corresponds to the queue one by one, so that the collection table update result data corresponding to the same collection table identifier can be allocated to the same queue. In addition, the present application is provided with multiple queues, and the collection table notification task can be transferred through multiple queues to record the collection table notification task in the notification task flow table. The setting of multiple queues speeds up the transfer efficiency of the collection table notification task, and can further buffer the collection table notification task data, so as to facilitate the processing of the collection table notification task.

[0226] In another embodiment, the embodiment of the present disclosure is provided with multiple queues, and the order of the multiple queues is fixed, and the collection table notification tasks are stored in the multiple queues in a loop in chronological order. Specifically, the embodiment of the present disclosure obtains multiple collection table notification tasks A, B, and C arranged in chronological order, and is provided with queue 1 and queue 2. The collection table notification task A is stored in queue 1, and the collection table notification task B is stored in queue 2. After that, the collection table notification task C is stored in queue 1 in a loop storage manner.

[0227] In another embodiment, the embodiment of the present disclosure is provided with multiple queues, and multiple collection table notification tasks are randomly stored in the multiple queues. Afterwards, the collection table notification tasks are taken out from the queues by using the queue consumer and recorded in the notification task flow table.

[0228] Reference Fig.13 There are multiple queues set in parallel. After obtaining the collection table notification task, the multiple collection table notification tasks are placed in multiple queues through the above steps 1210 to 1230 or other methods, and the collection table notification tasks are taken out from the queue by the queue consumer and recorded in the notification task flow table.

[0229] In step 1120, the collection table notification task is taken out from the queue by using the queue consumer and recorded in the notification task flow table.

[0230] Reference Fig.14 In one embodiment, the queue consumer is a plurality of queue consumers corresponding one-to-one to the plurality of queues, and step 1120 includes:

[0231] Step 1410: Utilize multiple queue consumers corresponding to multiple queues to simultaneously retrieve collection table notification tasks from the queues and record them in the notification task flow table.

[0232] The embodiment of step 1410 above is provided with multiple queue consumers, referring to Fig.13 , the queue consumer is set in one-to-one correspondence with multiple queues in the asynchronous queue, and the collection table notification task is taken out from the corresponding queue by the queue consumer and recorded in the notification task flow table. The queue consumer is set in one-to-one correspondence with the queue, and the collection table notification tasks in multiple queues can be processed at the same time, which improves the processing efficiency of the collection table notification tasks, thereby shortening the time for scheduling the collection table notification tasks, and ensuring the immediacy and timeliness of the notification tasks.

[0233] Detailed description of step 330

[0234] In step 330, based on the priorities of the plurality of collection table notification tasks in the notification task flow table, a target notification task is determined from the plurality of collection table notification tasks.

[0235] Reference Fig.15 In one embodiment, the collection table notification task further has an object identifier of an object that edits the collection table, and step 330 includes:

[0236] Step 1510: Determine a target notification task from among the multiple collection table notification tasks corresponding to the same object identifier based on the priorities of the multiple collection table notification tasks corresponding to the same object identifier in the notification task flow table.

[0237] Reference Fig.16 , multiple collection table notification tasks are stored in the notification task flow table, each collection table notification task has an object identifier, which is the identifier of the object that edits the collection table, and one collection table notification task corresponds to one object identifier. When the collection table notification task is a collection table edit notification type, the object identifier is the identifier of the object that edits the collection table. When the collection table notification task is a reminder type, the object identifier is the object identifier of the object to be reminded. When the collection table notification task is a reminder type, the object identifier is the object identifier of the object or administrator who sets the reminder conditions.

[0238] In another embodiment, based on the priorities of multiple collection table notification tasks in the notification task flow table, one or more with the highest priority are determined as the target priority, and then, based on the object identifiers of the multiple collection table notification tasks corresponding to the target priority, the target notification task is determined among the multiple collection table notification tasks. Specifically, after determining the target priority, for each object identifier of the multiple collection table notification tasks under the target priority, the number of collection table notification tasks under each object identifier is determined, and based on the number of collection table notification tasks under each object identifier, the target notification task is determined.

[0239] The embodiment of step 1510 above determines the target notification task among the multiple collection table notification tasks corresponding to the same object identifier in the notification task flow table based on the priorities of the multiple collection table notification tasks corresponding to the object identifier, so as to send the target notification task to the notification center, and the notification center notifies the terminal where the object identifier is located of the time. The embodiment of the present disclosure first searches for the collection table notification task corresponding to each object, and then determines the priority of the collection table notification task sent to the object, thereby improving the scheduling efficiency of the collection table notification task.

[0240] The above is a brief description of step 1510. The specific implementation process of step 1510 is described in detail below.

[0241] In step 1510, based on the priorities of multiple collection table notification tasks corresponding to the same object identifier in the notification task flow table, a target notification task is determined from among the multiple collection table notification tasks corresponding to the object identifier.

[0242] Reference Fig.17 In one embodiment, step 1510 includes:

[0243] Step 1710: for each object identifier, determine the number of notification tasks in the first collection table corresponding to the object identifier in the notification task flow table;

[0244] Step 1720: determine the target object identifier based on the number of notification tasks in the first collection table corresponding to each object identifier;

[0245] Step 1730: Determine a target notification task from among the multiple collection table notification tasks corresponding to the target object identifier in the notification task flow table based on the priorities of the multiple collection table notification tasks corresponding to the target object identifier.

[0246] Steps 1710 to 1730 are described in detail below.

[0247] In step 1710, for each object identifier, the number of first collection table notification tasks corresponding to the object identifier in the notification task flow table is determined. There are also many object identifiers corresponding to multiple collection table notification tasks in the notification task flow table. In the notification task flow table, the number of first collection table notification tasks corresponding to each object identifier is determined, and there is at least one first collection table notification task number corresponding to the object identifier.

[0248] In step 1720, the target object identifier is determined based on the number of first collection table notification tasks corresponding to each object identifier. The number of first collection table notification tasks corresponding to each object identifier is different, and the object identifier with more first collection table notification tasks has more notification events that its corresponding object needs to receive. Therefore, the object identifier corresponding to the largest number of one or more first collection table notification tasks is used as the target object identifier, thereby reducing the occurrence of too many target notification tasks corresponding to the object identifier and ensuring the immediacy of the target notification task issuance.

[0249] In step 1730, based on the priorities of the multiple collection table notification tasks corresponding to the target object identifier in the notification task flow table, the target notification task is determined from the multiple collection table notification tasks corresponding to the target object identifier. For the target object identifier, the priorities of the multiple collection table notification tasks corresponding to it are determined, and the highest one or more priorities are used as the target priority, and the collection table notification task under the priority is determined as the target notification task.

[0250] The embodiment of the above steps 1710 to 1730 obtains the number of first collection table notification tasks corresponding to each object identifier in the notification task flow table, and uses the object identifier corresponding to the largest number of first collection table notification tasks as the target object identifier. Afterwards, based on the priority of multiple collection table notification tasks corresponding to the target object identifier in the notification task flow table, the target notification task is determined from the multiple collection table notification tasks corresponding to the target object identifier. The determination of the target object identifier in the disclosed embodiment can reduce the occurrence of too many target notification tasks corresponding to the object identifier, and ensure the immediacy of the target notification task issuance.

[0251] In another embodiment, based on the priorities of multiple collection table notification tasks corresponding to the same object identifier in the notification task flow table, one or more with the highest priority are determined as the target priority. Afterwards, for the object identifiers of multiple collection table notification tasks corresponding to the target priority, the number of collection table notification tasks corresponding to each identifier is determined, and the collection table notification tasks under the object identifier corresponding to the largest number of one or more collection table notification tasks are used as the target notification tasks, which can reduce the occurrence of the counterparty node that cannot be notified in time due to the high priority but too few collection table notification tasks under the corresponding object identifier, and further ensure the immediacy of important notifications.

[0252] The above is a brief description of step 1710 to step 1730. The specific implementation process of step 1730 is described in detail below.

[0253] In step 1730, based on the priorities of the multiple collection table notification tasks corresponding to the target object identifier in the notification task flow table, a target notification task is determined from the multiple collection table notification tasks corresponding to the target object identifier.

[0254] Reference Fig.18 In one embodiment, the target object identifier is a plurality of target object identifiers, the notification center includes a plurality of processes corresponding to the plurality of target object identifiers, and step 1730 includes:

[0255] Step 1810: For each target object identifier, based on the priorities of multiple collection table notification tasks corresponding to the target object identifier in the notification task flow table, determine the target notification task corresponding to the target object identifier among the multiple collection table notification tasks corresponding to the target object identifier.

[0256] Corresponding to step 1810, step 340 includes:

[0257] Step 1820: Send the target notification task corresponding to each target object identifier to the notification center, and the process corresponding to each target object identifier notifies the counterpart node in the target notification task of the event in the target notification task corresponding to the target object identifier.

[0258] Step 1810 and step 1820 are described in detail below.

[0259] In step 1810, for each target object identifier, based on the priorities of the multiple collection table notification tasks corresponding to the target object identifier in the notification task flow table, a target notification task corresponding to the target object identifier is determined among the multiple collection table notification tasks corresponding to the target object identifier. There are multiple target object identifiers, and for each target object identifier, based on the priorities of the multiple collection table notification tasks corresponding to the target object identifier in the notification task flow table, one or more highest priorities are determined as target priorities, and based on the target priorities, the target notification task is determined among the multiple collection table notification tasks corresponding to the target object identifier.

[0260] In step 1820, the target notification task corresponding to each target object identifier is sent to the notification center, and the process corresponding to each target object identifier notifies the counterparty node in the target notification task of the event in the target notification task corresponding to the target object identifier. The notification center is provided with a process, and the process is used to notify the counterparty node in the target notification task of the event in the target notification task. One process usually corresponds to one counterparty node, that is, one process corresponds to one target object identifier. After the target notification task is sent to the notification center, for each target object identifier, the corresponding process notifies the counterparty node in the target notification task of the event in the target notification task corresponding to the target object identifier.

[0261] The processes are set corresponding to the counterpart nodes, so when there are multiple target object identifiers, the notification center is set with the same number of processes as the target object identifiers.

[0262] The notification center in the embodiment of the above steps 1810 and 1820 includes multiple processes corresponding to the target object identifiers, and notifies the counterparty node in the target notification task of the events in the target notification task corresponding to the target object identifier through the processes. It can notify multiple counterparty nodes at the same time, thereby realizing parallel processing of the target notification tasks by the notification center, thereby improving the scheduling efficiency of the collection table notification tasks and improving the immediacy of event notifications.

[0263] Reference Fig.19 In another embodiment, step 1730 includes:

[0264] Step 1910: For the collection table notification task corresponding to the target object identifier and having the same priority, obtain the recording time of the collection table notification task recorded in the notification task flow table;

[0265] Step 1920: Based on the priority and the recording time, determine the target notification task from the multiple collection table notification tasks corresponding to the target object identifier.

[0266] Step 1910 and step 1920 are described in detail below.

[0267] In step 1910, for the collection table notification task corresponding to the target object identifier and the same priority, the recording time of the collection table notification task recorded in the notification task flow table is obtained. The recording time corresponds to the recording time of the collection table notification task recorded in the task flow table, and the recording time corresponds to the generation time of the collection table notification task.

[0268] In step 1920, based on the priority and the recording time, the target notification task is determined from the multiple collection table notification tasks corresponding to the target object identifier. According to the priority and the recording time of the collection table notification task, the collection table notification task with a higher priority and an earlier recording time is determined as the target notification task.

[0269] The target notification task is determined by priority and recording time. In the process of determining the target notification task, the priority and recording time have different weights. Different weights can be set for the priority and recording time as needed so that important tasks can be notified to the counterparty node in a timely manner. Specifically, when the recording times of multiple collection table notification tasks corresponding to the target object identifier are close to the current time or are the same, the target notification task is determined based on the priority among the multiple collection table notification tasks corresponding to the target object identifier. When the difference between the recording time of the collection table notification task and the current time is equal to the preset time threshold, even if the priority of the collection table notification task is lower, the collection table notification task is determined as the target notification task.

[0270] The priority is usually related to the task type and collection table identifier of the collection table notification task. For the same priority, the task type and collection table identifier of the collection table notification task are the same. Usually, one or more collection table notification tasks with the latest recording time are used as target notification tasks.

[0271] The above-mentioned embodiments of step 1910 and step 1920 determine the target notification task from the multiple collection table notification tasks corresponding to the target object identifier based on the priority and the recording time. The disclosed embodiment realizes the timeliness scheduling by setting the recording time, thereby ensuring the immediacy of the event notification.

[0272] The above is a general description of step 1910 and step 1920. The specific implementation process of step 1920 is described in detail below.

[0273] In step 1920, based on the priority and the recording time, a target notification task is determined from a plurality of collection table notification tasks corresponding to the target object identifier.

[0274] Reference Fig. 20In one embodiment, step 1920 includes:

[0275] Step 2010: Obtain the maximum task quantity of each batch of target notification tasks sent to the notification center;

[0276] Step 220: Arrange multiple collection table notification tasks corresponding to the target object identifier in order of priority from high to low, and arrange the collection table notification tasks of the same priority in order of recording time from late to early, so as to form a scheduling sequence;

[0277] Step 2030: Take out the collection table notification tasks from the scheduling sequence in sequence according to the maximum task quantity of the batch as the target notification tasks of the batch.

[0278] Steps 2010 to 2030 are described in detail below.

[0279] In step 2010, the maximum batch task quantity of each batch of target notification tasks sent to the notification center is obtained. The number of target notification tasks received by the notification center in each batch is usually the same, but when the number of collection table notification tasks obtained is small, the number of target notification tasks received by the notification center will also decrease. Therefore, it is necessary to obtain the maximum batch task quantity of each batch of target notification tasks sent to the notification center, that is, the maximum batch task quantity of each batch of target notification tasks received by the notification center.

[0280] In step 220, the plurality of collection table notification tasks corresponding to the target object identifiers are arranged in order of priority from high to low, and the collection table notification tasks of the same priority are arranged in order of recording time from late to early, thereby forming a scheduling sequence. First, the plurality of collection table notification tasks are arranged in order of priority from high to low, and the collection table notification tasks of the same priority are arranged in order of recording time from late to early, thereby forming a scheduling sequence.

[0281] In the scheduling sequence, multiple collection table notification tasks in each row have the same priority, and the row with higher priority is at the front. For multiple collection table notification tasks in the same row, the one with the latest recording time, that is, the latest collection table notification task, is at the front.

[0282] In step 2030, the collection table notification tasks are sequentially taken out from the scheduling sequence according to the maximum task quantity of the batch as the target notification tasks of the batch. The maximum task quantity of the batch is the maximum task quantity that the notification center can notify and process. The collection table notification tasks are sequentially taken out from the scheduling sequence in order as the target notification tasks of the current batch. Specifically, the collection table notification tasks with the highest priority are first taken out in the order from the last to the first time. When the number of the taken out collection table notification tasks is less than the maximum task quantity of the batch, the collection table notification tasks with the second highest priority are taken out in the order from the last to the first time.

[0283] The embodiments of the above steps 2010 to 2030 arrange the multiple collection table notification tasks corresponding to the target object identifiers in order of priority from high to low, and arrange the collection table notification tasks of the same priority in order of record time from late to early, thereby forming a scheduling sequence, and determining the target notification task based on the scheduling sequence. Therefore, the collection table task scheduling method provided in the embodiment of the present disclosure follows the principle of polling by priority and giving priority to the latest tasks of the same priority for event notification to multiple objects, and can give priority to notifying the counterpart node of events with higher priorities, thereby realizing priority and timeliness scheduling and ensuring the immediacy of event notification.

[0284] Reference Fig.21 In another embodiment, step 1920 includes:

[0285] Step 2110: Determine a first score of each collection table notification task based on the priority of each collection table notification task corresponding to the target object identifier;

[0286] Step 2120: Determine a second score for each collection table notification task based on the recording time of each collection table notification task corresponding to the target object identifier;

[0287] Step 2130: Determine the total score of each collection table notification task based on the first score and the second score;

[0288] Step 2140: Based on the total score, determine the target notification task from the multiple collection table notification tasks corresponding to the target object identifier.

[0289] Steps 2110 to 2140 are described in detail below.

[0290] In step 2110, a first score of each collection table notification task is determined based on the priority of each collection table notification task corresponding to the target object identifier. The first score is determined based on the priority of the collection table notification task, and the higher the priority, the higher the first score of the collection table notification task.

[0291] In step 2120, a second score of each collection table notification task is determined based on the recording time of each collection table notification task corresponding to the target object identifier. The second score is determined based on the recording time of the collection table notification task, and the later the recording time is, the higher the second score of the collection table notification task is.

[0292] In step 2130, the total score of each collection table notification task is determined based on the first score and the second score. The total score of the collection table notification task is determined based on the first score and the second score, for example, the total score of the collection table notification task = first score * priority weight + second score * time weight, wherein the priority weight is the weight of the priority, the time weight is the weight of the recording time, and the priority weight and the time weight are fixed values.

[0293] In step 2140, based on the total score, a target notification task is determined from among the multiple collection table notification tasks corresponding to the target object identifier. One or more collection table notification tasks with the total score are selected as the target notification task from among the multiple collection table notification tasks corresponding to the target object identifier.

[0294] The embodiments of steps 2110 to 2140 above determine the first score according to the priority of the collection table notification task, determine the second score according to the recording time of the collection table notification task, and determine the target notification task from the multiple collection table notification tasks corresponding to the target object identifier based on the first score and the second score. The disclosed embodiment identifies the importance of each collection table notification task through the first score, the second score and the total score, making the process of scheduling the target notification task more intuitive, and being able to give priority notification to the counterparty node for events with higher priority, thus realizing the scheduling of priority and timeliness, and ensuring the immediacy and timeliness of event notification.

[0295] Collection table notification task deduplication

[0296] Reference Fig. 22 In one embodiment, the collection table notification task further includes a task type, a collection table identifier, and an object identifier of an object that edits the collection table. Before step 330, the collection table notification task scheduling method further includes:

[0297] Step 2210: determine that there are multiple notification tasks to be deduplicated in the notification task flow table, with the task type being the reminder type, the same collection table identifier, and the same object identifier;

[0298] Step 2220: deduplicate multiple notification tasks to be deduplicated so as to retain only one notification task to be deduplicated.

[0299] Step 2210 and step 2220 are described in detail below.

[0300] In step 2210, it is determined that there are multiple notification tasks to be deduplicated in the notification task flow table, whose task types are the urging filling type, the same collection table identifier, and the same object identifier. When the task types of multiple collection table notification tasks are all the urging filling type, and the collection table identifier and the object identifier are the same, the multiple collection table notification tasks are the same tasks, and therefore, the multiple collection table notification tasks are determined as multiple notification tasks to be deduplicated.

[0301] Reference Fig.16 The collection table notification task in the notification task flow table also includes a task type, a collection table identifier and an object identifier, wherein the task type includes a collection table editing notification type, a reminder type and a reminder type, and the object identifier is the identifier of the object that edits the collection table.

[0302] In step 2220, multiple notification tasks to be deduplicated are deduplicated to retain only one notification task to be deduplicated. Multiple collection table notification tasks of the same reminder type with the same collection table ID and object ID are deduplicated to retain only the notification task to be deduplicated.

[0303] For deduplication of multiple to-be-deduplication notification tasks, any one of the to-be-deduplication notification tasks may be retained, or the to-be-deduplication notification task with the latest recording time may be retained.

[0304] The embodiments of step 2210 and step 2220 above deduplicate multiple tasks to be deduplicated that have the same reminder type, collection table identifier, and object identifier, and only retain one notification task to be deduplicated in the task flow table. The disclosed embodiment deduplicates the collection table notification tasks, deletes duplicate tasks, reduces data redundancy, improves the scheduling efficiency of the collection table notification tasks, and reduces the occurrence of users being frequently disturbed by the same notification messages.

[0305] The above is a general description of step 2210 and step 2220. The specific implementation process of step 2210 is described in detail below.

[0306] In step 2210, it is determined that there are multiple to-be-deduplicated notification tasks in the task flow table, whose task type is a reminder type, whose collection table identifier is the same, and whose object identifier is the same.

[0307] Reference Fig.23 In one embodiment, step 2210 includes:

[0308] Step 2310: Filter out the collection form notification tasks whose task type is the reminder type from the notification task flow table;

[0309] Step 2320, classify the filtered collection table notification tasks according to the collection table identifier to obtain multiple categories;

[0310] Step 2330, classify the collection table notification tasks under each class according to the object identifier to obtain multiple subclasses;

[0311] Step 2340: If there are multiple collection table notification tasks under a subclass, the multiple collection table notification tasks under the subclass are determined as multiple notification tasks to be deduplicated.

[0312] Steps 2310 to 2340 are described in detail below.

[0313] In step 2310, the collection table notification tasks with the task type of urging filling are filtered out from the notification task flow table. According to the task type of the collection table notification task, the collection table notification tasks with the task type of urging filling are determined from the task flow table.

[0314] In step 2320, the filtered collection table notification tasks are classified according to the collection table identifier to obtain multiple classes. The filtered collection table notification tasks of the reminder type are classified according to the collection table identifier to obtain multiple classes, each class corresponds to the collection table identifier, and each class includes multiple collection table notification tasks with the same collection table identifier.

[0315] In step 2330, the collection table notification tasks under each class are classified according to the object identifier to obtain multiple subclasses. For each class, the collection table notification tasks under the class are classified according to the object identifier to obtain multiple subclasses, each subclass corresponds to the object identifier, and the collection table identifier and object identifier of multiple collection table notification tasks in each subclass are the same.

[0316] In step 2340, if there are multiple collection table notification tasks under a subclass, the multiple collection table notification tasks under the subclass are determined as multiple notification tasks to be deduplicated. If there are multiple collection table notification tasks corresponding to a subclass, the multiple collection table notification tasks under the subclass are determined as multiple notification tasks to be deduplicated. Afterwards, the multiple notification tasks to be deduplicated are deduplicated to retain only one notification task to be deduplicated.

[0317] The embodiment of the above steps 2310 to 2340 classifies the collection table notification tasks according to the task type, collection table identifier, and object identifier in sequence, thereby determining multiple notification tasks to be deduplicated. The notification tasks to be deduplicated can determine duplicate tasks, thereby facilitating the deletion of duplicate tasks, reducing data redundancy, improving the scheduling efficiency of the collection table notification tasks, and reducing the occurrence of users being frequently disturbed by the same notification messages.

[0318] Collect table notification task merge

[0319] Reference Fig.24 In one embodiment, the collection table notification task further includes a task type, a collection table identifier, and a task content. Before step 330, the collection table notification task scheduling method further includes:

[0320] Step 2410: determine that there are multiple notification tasks to be merged in the notification task flow table whose task type is collection table edit notification type and whose collection table identifier is the same;

[0321] Step 2420: Generate a merged notification task, where the task content of the merged notification task is the union of the task contents of the multiple notification tasks to be merged;

[0322] Step 2430: In the notification task flow table, replace the multiple notification tasks to be merged with the merged notification task.

[0323] Steps 2410 to 2430 are described in detail below.

[0324] In step 2410, it is determined that there are multiple notification tasks to be merged in the notification task flow table, whose task types are the collection table edit notification type and whose collection table identifiers are the same. When the task types of the multiple collection table notification tasks are all the collection table edit notification type and the collection table identifiers are the same, the multiple collection table notification tasks are tasks for multiple objects to edit the collection table corresponding to the same online form, or the multiple collection table notification tasks are tasks for one object to edit the same online form multiple times within a period of time, and therefore, the multiple collection table notification tasks are determined as multiple notification tasks to be merged.

[0325] In step 2420, a merged notification task is generated, and the task content of the merged notification task is the union of the task contents of the multiple notification tasks to be merged. Multiple collection table notification tasks of the collection table edit notification type with the same collection table identifier are merged to obtain a merged notification task, and the task content of the merged notification task is the union of the task contents of the multiple notification tasks to be merged.

[0326] Reference Fig.16 The collection table notification task in the notification task flow table also includes task content. When the collection table notification task is a collection table edit notification type, the task content at least includes the specific operation type of the edit performed by the object, such as submit, delete, modify, etc. The task content may also include the specific content of the edit operation performed by the object, such as the content of the object's modification of the collection table, etc. Specifically, when user A modifies the answer to question A and user B deletes the answer to question B, the content of the merged notification task includes user A modifying question A and user B deleting question B.

[0327] In step 2430, in the notification task flow table, the multiple notification tasks to be merged are replaced with the merged notification task. After the merged notification task is determined, the multiple notification tasks to be merged are replaced with the merged notification task. The merged notification task and the notification task to be merged have the same collection table identifier, and the corresponding counterpart node is the administrator terminal corresponding to the collection table identifier.

[0328] The embodiment of the above steps 2410 to 2430 merges the task contents of multiple notification tasks to be merged that have the same collection table edit notification type and collection table identifier, generates a merged notification task, and the merged notification task replaces the multiple notification tasks to be merged. The disclosed embodiment performs deduplication and merging of collection table notification tasks, reduces the redundancy of notification tasks, shortens the processing time of collection table notification tasks, and improves the scheduling efficiency of collection table notification tasks.

[0329] In one embodiment, collection table notification tasks whose task type is the collection table editing notification type are filtered out from the notification task flow table, and then the collection table notification tasks at the filtered location are classified according to the collection table identifier to obtain multiple classes. If there are multiple collection table notification tasks for a class, the multiple collection table notification tasks under the class are determined as multiple notification tasks to be merged.

[0330] Task status settings for collection table notification tasks

[0331] Reference Fig.25 In one embodiment, the collection table notification task also has a task state. After step 340, the collection table notification task scheduling method further includes:

[0332] Step 2510: If the notification is successful, set the task state of the target notification task in the notification task flow table to the first state.

[0333] Corresponding to step 2510, step 330 includes:

[0334] Step 2520: Determine a target notification task from among the multiple collection table notification tasks based on the priorities of the multiple collection table notification tasks whose task status is not the first status in the notification task flow table.

[0335] Step 2510 and step 2520 are described in detail below.

[0336] In step 2510, if the notification is successful, the task state of the target notification task in the notification task flow table is set to the first state. Fig.16 The collection table notification task in the notification task flow table also includes a task status. When the task status is the first state, it means that the corresponding target notification task should be successfully notified to the counterpart node.

[0337] In step 2520, a target notification task is determined from among the multiple collection table notification tasks based on the priorities of the multiple collection table notification tasks whose task status is not the first status in the notification task flow table. The multiple collection table notification tasks whose task status is not the first status include collection table notification tasks that have not yet been notified and collection table notification tasks that have failed to notify. The target notification task is determined based on the priorities of the multiple collection table notification tasks whose task status is not the first status.

[0338] The implementation example of the above-mentioned steps 2510 and 2520 is provided with a task status, and the task status is set according to whether the notification of the collection table notification task is successful or not. The notification task that fails to notify can be rescheduled, thereby reducing the occurrence of task abandonment due to errors in the notification center and the counterparty node, improving the system disaster recovery, and thereby ensuring the data reliability of the collection table notification task.

[0339] The above is a general description of step 2510 and step 2520. The specific implementation process of step 2520 is described in detail below.

[0340] In step 2520, based on the priorities of the multiple collection table notification tasks whose task status is not the first status in the notification task flow table, a target notification task is determined from the multiple collection table notification tasks.

[0341] Reference Fig.26 In one embodiment, step 2520 is performed periodically, and the period is determined by:

[0342] Step 2610: Obtain expected timeliness index;

[0343] Step 2620, obtaining the average number of collection table notification tasks generated per unit time;

[0344] Step 2630: Determine the period based on the expected timeliness index and the average number.

[0345] Steps 2610 to 2630 are described in detail below.

[0346] In step 2610, an expected timeliness index is obtained. The expected timeliness index is a timeliness index of the collection table notification task in the scheduling process, which specifically represents the relationship between the generation time of the collection table notification task and the time when the event in the collection table notification task is notified to the counterparty node. The higher the expected timeliness index, the closer the event notification time is to the task generation time. Collection table notification tasks of different priorities have different corresponding expected timeliness indexes.

[0347] In step 2620, the average number of collection table notification tasks generated per unit time is obtained.

[0348] In step 2630, a period is determined based on the expected timeliness index and the average number. The period is determined based on the expected timeliness index and the average number. The higher the expected timeliness index and the larger the average number, the more frequently the target notification task should be determined, and the shorter the period.

[0349] Reference Figure 5The embodiment of the present disclosure is provided with a timer, a period is set by the timer, a target notification task is determined from a plurality of collection table notification tasks according to the period, and the target notification task is sent to the notification center.

[0350] The embodiments of steps 2610 to 2630 above determine the period of the target notification task based on the expected timeliness index and the average number, so that the period is adapted to the collection table notification task, reducing the problem of resource waste caused by a period that is too long or too short, thereby improving the scheduling efficiency of the collection table notification task.

[0351] Reference Fig. 27 In one embodiment, step 2520 includes:

[0352] Step 2710, determining in real time the number of notification tasks in the second collection table whose task status is not in the first status in the notification task flow table;

[0353] Step 2720: If the number of notification tasks in the second collection table is greater than the first threshold, determine the target notification task from the multiple collection table notification tasks based on the priorities of the multiple collection table notification tasks whose task status is not the first status in the notification task flow table.

[0354] Step 2710 and step 2720 are described in detail below.

[0355] In step 2710, the number of second collection table notification tasks whose task status is not the first status in the notification task flow table is determined in real time. The number of collection table notification tasks whose notification fails in the notification task flow table is determined in real time as the number of second collection table notification tasks.

[0356] In step 2720, if the number of notification tasks in the second collection table is greater than the first threshold, a target notification task is determined from among the multiple collection table notification tasks based on the priorities of the multiple collection table notification tasks whose task states are not in the first state in the notification task flow table. The first threshold can be set as needed, and when the number of notification tasks in the second collection table is greater than the first threshold, that is, the number of notification tasks in the collection table that failed to be notified is greater than the first threshold, a target notification task is determined from among the multiple collection table notification tasks to resend the task that failed to be notified.

[0357] The embodiments of the above-mentioned steps 2710 and 2720 are provided with a first threshold value, and the first threshold value is the condition for resending the collection table notification task that fails to be notified. When the number of the second collection table notification tasks is greater than the first threshold value, based on the priorities of the multiple collection table notification tasks whose task status is not the first status in the notification task flow table, the target notification task is determined among the multiple collection table notification tasks, and the notification task that fails to be notified is rescheduled, thereby reducing the occurrence of task abandonment caused by errors in the notification center and the counterparty node, improving the system disaster recovery, and thereby ensuring the data reliability of the collection table notification task.

[0358] In one embodiment, the embodiment of the present disclosure is provided with a retry cycle, and the collection table notification task that fails to notify is processed according to the retry cycle. Based on the priority of multiple collection table notification tasks that fail to notify in the notification task flow table, a target notification task is determined among multiple collection table notification tasks.

[0359] In one embodiment, a retry threshold is set in the embodiment of the present disclosure. When the number of times a collection table notification task retries notification is equal to the retry threshold, the collection table notification task is deleted. The retry threshold is set according to the performance of the notification center and the counterparty node to reduce the occupation of the notification task flow table space by failed data and improve the scheduling efficiency of the collection table notification task.

[0360] Description of the apparatus and device of the present disclosure

[0361] It is to be understood that, although the steps in the above-mentioned flowcharts are sequentially displayed according to the characterization of arrows, these steps are not necessarily executed in sequence according to the order of arrow characterization. Unless there is a clear description in the present embodiment, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the above-mentioned flowcharts can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the steps or stages in other steps.

[0362] It should be noted that in various specific implementations of the present disclosure, when it comes to the need to perform relevant processing based on data related to the characteristics of the target object such as the target object attribute information or attribute information set, the permission or consent of the target object will be obtained first, and the collection, use and processing of these data will comply with relevant laws, regulations and standards. In addition, when the embodiment of the present disclosure needs to obtain the attribute information of the target object, the separate permission or separate consent of the target object will be obtained through a pop-up window or jump to a confirmation page. After clearly obtaining the separate permission or separate consent of the target object, the necessary target object-related data for the normal operation of the embodiment of the present disclosure will be obtained.

[0363] Reference Fig.28 According to one aspect of the present disclosure, a collection table notification task scheduling device 2800 is provided, comprising:

[0364] The task acquisition unit 2810 is used to acquire a plurality of collection table notification tasks, where the collection table notification tasks are used to notify the event-related event-related editing to the counterparty node of the event, and the collection table notification tasks have a priority;

[0365] A task recording unit 2820, used to record multiple collection table notification tasks into a notification task flow table;

[0366] A target confirmation unit 2830, configured to determine a target notification task among the plurality of collection table notification tasks based on the priorities of the plurality of collection table notification tasks in the notification task flow table;

[0367] The notification sending unit 2840 is used to send the target notification task to the notification center, and the notification center notifies the counterpart node in the target notification task of the event in the target notification task.

[0368] Optionally, the collection table notification task also has an object identifier of an object that edits the collection table;

[0369] The target confirmation unit 2830 is specifically used for:

[0370] Based on the priorities of multiple collection table notification tasks corresponding to the same object identifier in the notification task flow table, a target notification task is determined among the multiple collection table notification tasks corresponding to the object identifier.

[0371] Optionally, the target confirmation unit 2830 is specifically configured to:

[0372] For each object identifier, determine the number of notification tasks in the first collection table corresponding to the object identifier in the notification task flow table;

[0373] Determine the target object identifier based on the number of notification tasks in the first collection table corresponding to each object identifier;

[0374] Based on the priorities of the multiple collection table notification tasks corresponding to the target object identifier in the notification task flow table, a target notification task is determined from the multiple collection table notification tasks corresponding to the target object identifier.

[0375] Optionally, the target object identifier is a plurality of target object identifiers; the notification center includes a plurality of processes corresponding to the plurality of target object identifiers;

[0376] The target confirmation unit 2830 is specifically used to: for each target object identifier, based on the priorities of multiple collection table notification tasks corresponding to the target object identifier in the notification task flow table, determine the target notification task corresponding to the target object identifier among the multiple collection table notification tasks corresponding to the target object identifier;

[0377] The sending notification unit 2840 is specifically used to: send the target notification task corresponding to each target object identifier to the notification center, and the process corresponding to each target object identifier notifies the counterpart node in the target notification task of the event in the target notification task corresponding to the target object identifier.

[0378] Optionally, the target confirmation unit 2830 is specifically configured to:

[0379] For the collection table notification task corresponding to the target object identifier and having the same priority, obtain the recording time of the collection table notification task recorded in the task flow table;

[0380] Based on the priority and the recording time, a target notification task is determined from a plurality of collection table notification tasks corresponding to the target object identifier.

[0381] Optionally, the target confirmation unit 2830 is specifically configured to:

[0382] Get the maximum batch size of each batch of target notification tasks sent to the notification center;

[0383] Arrange multiple collection table notification tasks corresponding to the target object identifier in order of priority from high to low, and arrange the collection table notification tasks of the same priority in order of recording time from late to early, so as to form a scheduling sequence;

[0384] According to the maximum task quantity of the batch, the collection table notification tasks are taken out from the scheduling sequence in sequence as the target notification tasks of the batch.

[0385] Optionally, the target confirmation unit 2830 is specifically configured to:

[0386] Determine a first score for each collection table notification task based on the priority of each collection table notification task corresponding to the target object identifier;

[0387] determining a second score for each collection table notification task based on a recording time of each collection table notification task corresponding to the target object identifier;

[0388] determining a total score for each collection form notification task based on the first score and the second score;

[0389] Based on the total score, a target notification task is determined from a plurality of collection table notification tasks corresponding to the target object identifier.

[0390] Optionally, the collection table notification task further has a task type, a collection table identifier, and an object identifier of an object that edits the collection table;

[0391] The collection table notification task scheduling device 2800 also includes:

[0392] The first determination unit is used to determine that there are multiple to-be-deduplicated notification tasks in the task flow table whose task type is a reminder filling type, whose collection table identifier is the same, and whose object identifier is the same;

[0393] The task deduplication unit is used to deduplicate multiple tasks to be notified of deduplication so as to retain only one task to be notified of deduplication.

[0394] Optionally, the first determining unit is specifically configured to:

[0395] Filter out the collection form notification tasks with the task type of reminder type from the task flow table;

[0396] The filtered collection table notification tasks are classified according to the collection table identifiers to obtain multiple classes;

[0397] Classify the collection table notification tasks under each class according to the object identifier to obtain multiple subclasses;

[0398] If there are multiple collection table notification tasks under one subclass, the multiple collection table notification tasks under the subclass are determined as multiple notification tasks to be deduplicated.

[0399] Optionally, the collection table notification task further has a task type, a collection table identifier, and task content;

[0400] The collection table notification task scheduling device 2800 also includes:

[0401] The second determining unit is used to determine that there are multiple notification tasks to be merged in the task flow table whose task type is the collection table edit notification type and whose collection table identifier is the same;

[0402] Generate a merging unit, which is used to generate a merged notification task, where the task content of the merged notification task is the union of the task contents of multiple notification tasks to be merged;

[0403] The task replacement unit is used to replace multiple notification tasks to be merged with the merged notification task in the task flow table.

[0404] Optionally, the collection table notification task also has a task status;

[0405] The collection table notification task scheduling device 2800 also includes:

[0406] A state setting unit, configured to set the task state of the target notification task in the task flow table to the first state if the notification is successful;

[0407] The target confirmation unit 2830 is specifically used to determine the target notification task from the multiple collection table notification tasks based on the priorities of the multiple collection table notification tasks whose task status is not the first status in the notification task flow table.

[0408] Optionally, the target confirmation unit 2830 is executed periodically, and the collection table notification task scheduling device 2800 further includes:

[0409] An indicator acquisition unit, used to acquire expected timeliness indicators;

[0410] A number acquisition unit, used to acquire the average number of collection table notification tasks generated per unit time;

[0411] The period determination unit is used to determine the period based on the expected timeliness index and the average number.

[0412] Optionally, the target confirmation unit 2830 is specifically configured to:

[0413] Real-time determination of the number of notification tasks in the second collection table whose task status is not in the first status in the notification task flow table;

[0414] If the number of notification tasks in the second collection table is greater than the first threshold, a target notification task is determined from among the plurality of notification tasks in the collection table based on the priorities of the plurality of notification tasks in the notification task flow table whose task states are not the first state.

[0415] Optionally, the task recording unit 2820 is specifically used for:

[0416] Store multiple collection table notification tasks into a queue;

[0417] Use the queue consumer to take out the collection table notification task from the queue and record it in the notification task flow table.

[0418] Optionally, the queue is a plurality of queues, and the collection table notification task has a collection table identifier;

[0419] The task recording unit 2820 is specifically used for:

[0420] Determine a consistent hash value of the collection table identifier of the collection table notification task;

[0421] Based on the consistent hash value, determine the allocation queue among multiple queues;

[0422] Store the collection table notification tasks into the allocation queue.

[0423] Optionally, the queue consumer is a plurality of queue consumers corresponding one-to-one to the plurality of queues;

[0424] The task recording unit 2820 is specifically used for:

[0425] Using multiple queue consumers corresponding to multiple queues, collection table notification tasks are taken out from the queues at the same time, and recorded in the notification task flow table at the same time.

[0426] Optionally, the task acquisition unit 2810 is specifically configured to: receive a collection table notification task of a collection table edit notification type from an object terminal, the collection table notification task of the collection table edit notification type being generated in response to the object editing the collection table, the event associated with the editing of the collection table being an edit event, and the counterpart node being an administrator terminal;

[0427] The notification sending unit 2840 is specifically used to notify the administrator terminal of the editing event.

[0428] Optionally, the task acquisition unit 2810 is specifically configured to: receive a collection form notification task of a reminder filling type from an administrator terminal, the collection form notification task of the reminder filling type being generated in response to a reminder filling instruction issued by the administrator for the collection form to be reminded filling object, the event associated with the editing of the collection form is a reminder filling event, and the counterparty node is the object terminal of the object to be reminded filling;

[0429] The notification sending unit 2840 is specifically used to notify the object terminal of the object to be reminded of the reminder event.

[0430] Optionally, the task acquisition unit 2810 is specifically configured to: receive a collection form notification task of a reminder type from an object terminal or an administrator terminal, the collection form notification task of the reminder type being generated in response to a filling reminder condition set by the object or the administrator for the collection form becoming satisfied, the event associated with the editing of the collection form is a reminder event, and the counterpart node is the object terminal or the administrator terminal that sets the filling reminder condition;

[0431] The notification sending unit 2840 is specifically used to notify the object terminal or the administrator terminal who has set and filled in the reminder condition of the reminder event.

[0432] Reference Fig.29 , Fig.29The structural block diagram of the terminal 140 for implementing the collection table notification task scheduling method of the embodiment of the present disclosure includes: a radio frequency (RF) circuit 2910, a memory 2915, an input unit 2930, a display unit 2940, a sensor 2950, ​​an audio circuit 2960, a wireless fidelity (WiFi) module 2970, a processor 2980, and a power supply 2990. Those skilled in the art can understand that Fig.29 The structure of the terminal 140 shown in the figure does not constitute a limitation on a mobile phone or a computer, and may include more or less components than those shown in the figure, or combine certain components, or arrange the components differently.

[0433] RF circuit 2910 can be used for receiving and sending signals during information transmission or calls. In particular, after receiving the downlink information from the base station, it is sent to processor 2980 for processing; in addition, the designed uplink data is sent to the base station.

[0434] The memory 2915 may be used to store software programs and modules. The processor 2980 executes various functional applications and data processing of the terminal by running the software programs and modules stored in the memory 2915 .

[0435] The input unit 2930 may be used to receive input digital or character information and generate key signal input related to the terminal's settings and function control. Specifically, the input unit 2930 may include a touch panel 2931 and other input devices 2932 .

[0436] The display unit 2940 may be used to display input information or provided information and various menus of the terminal. The display unit 2940 may include a display panel 2941.

[0437] The audio circuit 2960, the speaker 2961, and the microphone 2962 may provide an audio interface.

[0438] In this embodiment, the processor 2980 included in the terminal 140 can execute the collection table notification task scheduling method of the previous embodiment.

[0439] The terminals of the embodiments of the present disclosure include but are not limited to mobile phones, computers, intelligent voice interaction devices, smart home appliances, vehicle terminals, aircraft, etc. The embodiments of the present invention can be applied to various fields, including but not limited to online documents, data processing, the Internet, etc.

[0440] Fig.30A block diagram of the structure of a portion of a server for implementing the collection table notification task scheduling method of an embodiment of the present disclosure. The server may have relatively large differences due to different configurations or performances, and may include one or more central processing units (CPUs) 3302 (for example, one or more processors) and a memory 3032, and one or more storage media 3030 (for example, one or more mass storage devices) storing application programs 3042 or data 3044. Among them, the memory 3032 and the storage medium 3030 can be short-term storage or permanent storage. The program stored in the storage medium 3030 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the server 3000. Furthermore, the central processing unit 3022 can be configured to communicate with the storage medium 3030 to execute a series of instruction operations in the storage medium 3030 on the server.

[0441] The server may also include one or more power supplies 3026, one or more wired or wireless network interfaces 3050, one or more input and output interfaces 3058, and / or one or more operating systems 3041, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

[0442] The processor in the server can be used to execute the collection table notification task scheduling method of the embodiment of the present disclosure.

[0443] The embodiment of the present disclosure further provides a computer-readable storage medium, which is used to store program codes, and the program codes are used to execute the collection table notification task scheduling method of each of the aforementioned embodiments.

[0444] The embodiment of the present disclosure also provides a computer program product, which includes a computer program. A processor of a computer device reads and executes the computer program, so that the computer device executes and implements the above-mentioned collection table notification task scheduling method.

[0445] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present disclosure described herein can, for example, be implemented in an order other than those illustrated or described herein. In addition, the terms "comprises" and "comprising" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0446] It should be understood that in the present disclosure, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0447] It should be understood that in the description of the embodiments of the present disclosure, the meaning of multiple (or multiple items) is more than two, greater than, less than, exceed, etc. are understood to not include the number, and above, below, within, etc. are understood to include the number.

[0448] In the several embodiments provided in the present disclosure, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0449] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0450] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0451] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present disclosure is essentially 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, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store program codes.

[0452] It should also be understood that the various implementations provided in the embodiments of the present disclosure can be combined arbitrarily to achieve different technical effects.

[0453] The above is a specific description of the implementation methods of the present disclosure, but the present disclosure is not limited to the above implementation methods. Technical personnel familiar with the art can also make various equivalent modifications or substitutions without violating the spirit of the present disclosure. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present disclosure.

Claims

1. A collection table notification task scheduling method, characterized in that: include: Acquire a plurality of collection table notification tasks, wherein the collection table notification tasks are used to notify a counterparty node of an event associated with editing of the collection table, and the collection table notification tasks have a priority; Recording a plurality of the collection table notification tasks into a notification task flow table; Determine a target notification task from among the plurality of collection table notification tasks based on the priorities of the plurality of collection table notification tasks in the notification task flow table; The target notification task is sent to a notification center, and the notification center notifies the counterparty node in the target notification task of the event in the target notification task.

2. The collection table notification task scheduling method according to claim 1, characterized in that: The collection table notification task also has an object identifier of an object that edits the collection table; The determining of a target notification task from among the plurality of collection table notification tasks based on the priorities of the plurality of collection table notification tasks in the notification task flow table comprises: Based on the priorities of the plurality of collection table notification tasks corresponding to the same object identifier in the notification task flow table, a target notification task is determined from the plurality of collection table notification tasks corresponding to the object identifier.

3. The collection table notification task scheduling method according to claim 2, characterized in that: Determining a target notification task from among the plurality of collection table notification tasks corresponding to the object identifier based on the priorities of the plurality of collection table notification tasks corresponding to the same object identifier in the notification task flow table includes: For each of the object identifiers, determining the number of notification tasks in the first collection table corresponding to the object identifier in the notification task flow table; Determine a target object identifier based on the number of notification tasks in the first collection table corresponding to each of the object identifiers; Based on the priorities of the plurality of collection table notification tasks corresponding to the target object identifier in the notification task flow table, a target notification task is determined from the plurality of collection table notification tasks corresponding to the target object identifier.

4. The collection table notification task scheduling method according to claim 3, characterized in that: The target object identifier is a plurality of target object identifiers; the notification center includes a plurality of processes corresponding to the plurality of target object identifiers; The step of determining a target notification task from among the multiple collection table notification tasks corresponding to the target object identifier based on the priorities of the multiple collection table notification tasks corresponding to the target object identifier in the notification task flow table comprises: for each target object identifier, determining, from among the multiple collection table notification tasks corresponding to the target object identifier, a target notification task corresponding to the target object identifier based on the priorities of the multiple collection table notification tasks corresponding to the target object identifier in the notification task flow table; The sending of the target notification task to a notification center, and the notification center notifying the counterparty node in the target notification task of the event in the target notification task, includes: sending the target notification task corresponding to each target object identifier to a notification center, and the process corresponding to each target object identifier notifying the counterparty node in the target notification task of the event in the target notification task corresponding to the target object identifier.

5. The collection table notification task scheduling method according to claim 3, characterized in that: Determining a target notification task from among the plurality of collection table notification tasks corresponding to the target object identifier based on the priorities of the plurality of collection table notification tasks corresponding to the target object identifier in the notification task flow table includes: For the collection table notification task corresponding to the target object identifier and having the same priority level, obtaining the recording time of the collection table notification task being recorded in the notification task flow table; Based on the priority and the recording time, a target notification task is determined from a plurality of collection table notification tasks corresponding to the target object identifier.

6. The collection table notification task scheduling method according to claim 5, characterized in that: The determining, based on the priority and the recording time, a target notification task from a plurality of notification tasks in the collection table corresponding to the target object identifier comprises: Obtaining a batch maximum task quantity of each batch of the target notification tasks sent to the notification center; Arrange the plurality of collection table notification tasks corresponding to the target object identifier in descending order of priority, and arrange the collection table notification tasks of the same priority in descending order of recording time, thereby forming a scheduling sequence; The collection table notification tasks are sequentially taken out from the scheduling sequence according to the maximum task quantity of the batch as the target notification tasks of the batch.

7. The collection table notification task scheduling method according to claim 5, characterized in that: The determining, based on the priority and the recording time, a target notification task from a plurality of notification tasks in the collection table corresponding to the target object identifier comprises: Determine a first score of each of the collection table notification tasks based on the priority of each of the collection table notification tasks corresponding to the target object identifier; Determine a second score of each of the collection table notification tasks based on the recording time of each of the collection table notification tasks corresponding to the target object identifier; Determining a total score of each of the collection form notification tasks based on the first score and the second score; Based on the total score, the target notification task is determined from a plurality of notification tasks in the collection table corresponding to the target object identifier.

8. The collection table notification task scheduling method according to claim 1, characterized in that: The collection table notification task also has a task type, a collection table identifier, and an object identifier of an object that edits the collection table; Before determining a target notification task from among the plurality of collection table notification tasks based on the priorities of the plurality of collection table notification tasks in the notification task flow table, the collection table notification task scheduling method further includes: Determine in the notification task flow table that there are multiple notification tasks to be deduplicated whose task type is a reminder type, whose collection table identifier is the same, and whose object identifier is the same; Deduplication is performed on the plurality of notification tasks to be deduplicated, so as to retain only one notification task to be deduplicated.

9. The collection table notification task scheduling method according to claim 8, characterized in that: The determining that there are multiple notification tasks to be deduplicated in the notification task flow table, the task type of which is a reminder type, the collection table identifier is the same, and the object identifier is the same, includes: Filter out the collection table notification tasks whose task type is a reminder type from the notification task flow table; Classifying the filtered collection table notification tasks according to the collection table identifiers to obtain multiple classes; Classify the collection table notification tasks under each of the classes according to the object identifiers to obtain multiple subclasses; If there are multiple collection table notification tasks under one subclass, the multiple collection table notification tasks under the subclass are determined as multiple notification tasks to be deduplicated.

10. The collection table notification task scheduling method according to claim 1, characterized in that: The collection table notification task also has a task type, a collection table identifier, and task content; Before determining a target notification task from among the plurality of collection table notification tasks based on the priorities of the plurality of collection table notification tasks in the notification task flow table, the collection table notification task scheduling method further includes: Determine in the notification task flow table that there are multiple notification tasks to be merged whose task type is the collection table edit notification type and whose collection table identifier is the same; Generate a merged notification task, wherein the task content of the merged notification task is the union of the task contents of the multiple notification tasks to be merged; In the notification task flow table, the merged notification task replaces the plurality of notification tasks to be merged.

11. The collection table notification task scheduling method according to claim 1, characterized in that: The collection table notification task also has a task status; After the target notification task is sent to the notification center, and the notification center notifies the counterparty node in the target notification task of the event in the target notification task, the collection table notification task scheduling method further includes: if the notification is successful, setting the task state of the target notification task in the notification task flow table to the first state; The method of determining a target notification task from among the multiple collection table notification tasks based on the priorities of the multiple collection table notification tasks in the notification task flow table comprises: determining the target notification task from among the multiple collection table notification tasks based on the priorities of the multiple collection table notification tasks whose task status is not the first status in the notification task flow table.

12. The collection table notification task scheduling method according to claim 11, characterized in that: The determining of the target notification task from the plurality of notification tasks in the collection table based on the priorities of the plurality of notification tasks in the notification task flow table whose task status is not the first status is performed periodically; The period is determined by: Obtain expected timeliness indicators; Obtaining the average number of the collection table notification tasks generated per unit time; The period is determined based on the expected timeliness indicator and the average number.

13. The collection table notification task scheduling method according to claim 11, characterized in that: The determining the target notification task from the plurality of collection table notification tasks based on the priorities of the plurality of collection table notification tasks whose task status is not the first status in the notification task flow table comprises: Determine in real time the number of notification tasks in the second collection table whose task status is not the first status in the notification task flow table; If the number of notification tasks in the second collection table is greater than a first threshold, the target notification task is determined from among the plurality of notification tasks in the collection table based on the priorities of the plurality of notification tasks in the notification task flow table whose task states are not the first state.

14. The collection table notification task scheduling method according to claim 1, characterized in that: The step of recording the plurality of collection table notification tasks into the notification task flow table includes: storing a plurality of the collection table notification tasks in a queue; The collection table notification task is taken out from the queue by using a queue consumer, and recorded in the notification task flow table.

15. The collection table notification task scheduling method according to claim 14, characterized in that: The queue is a plurality of queues, and the collection table notification task has a collection table identifier; The storing of the plurality of collection table notification tasks into a queue comprises: Determine a consistent hash value of the collection table identifier of the collection table notification task; Based on the consistent hash value, determining an allocation queue among the plurality of queues; The collection table notification task is stored in the allocation queue.

16. The collection table notification task scheduling method according to claim 15, characterized in that: The queue consumer is a plurality of queue consumers corresponding one-to-one to the plurality of queues; The process of taking out the collection table notification task from the queue by using the queue consumer and recording it in the notification task flow table includes: By using the multiple queue consumers corresponding to the multiple queues, the collection table notification tasks are taken out from the queues at the same time, and recorded in the notification task flow table at the same time.

17. A collection table notification task scheduling device, characterized in that: include: A task acquisition unit, used for acquiring a plurality of collection table notification tasks, wherein the collection table notification tasks are used for notifying a counterparty node of an event associated with editing of the collection table, and the collection table notification tasks have a priority; A task recording unit, used for recording a plurality of the collection table notification tasks into a notification task flow table; A target confirmation unit, configured to determine a target notification task from among the plurality of collection table notification tasks based on the priorities of the plurality of collection table notification tasks in the notification task flow table; The notification sending unit is used to send the target notification task to a notification center, and the notification center notifies the counterpart node in the target notification task of the event in the target notification task.

18. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the collection table notification task scheduling method described in any one of claims 1 to 16 is implemented.

19. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the collection table notification task scheduling method described in any one of claims 1 to 16 is implemented.

20. A computer program product, comprising a computer program, wherein the computer program is read and executed by a processor of a computer device, so that the computer device executes the collection table notification task scheduling method according to any one of claims 1 to 16.

Images