Task calendar construction method and device, electronic equipment and storage medium

Abstract

The invention provides a task calendar construction method and device, electronic equipment and a storage medium. The task calendar construction method comprises the steps of obtaining a task set and at least one execution object chain; splitting the task set to generate at least one task vector, and generating a chain vector based on the execution object chain; for any task vector, determining a target execution object chain processed by the task vector based on the chain vector and the task vector; sequentially matching the task vector with the execution objects on the target execution object chain until a matching value is smaller than a matching threshold value; and generating a task calendar based on the task vector and the execution object matched with the target execution object chain. Through an automatic task distribution and scheduling mechanism, the demand of manual intervention is reduced, the working efficiency is improved, the problems of task omission or repetition and the like caused by human factors are avoided, the probability of error occurrence is reduced, meanwhile, the generated task calendar is clear, and a manager can conveniently master the task processing progress and the labor division condition of personnel at any time.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a task calendar construction method, device, electronic device and storage medium. Background Art

[0002] Every year, regulatory agencies will adjust the list of regulatory reporting tasks, or adjust the reporting frequency and reporting deadlines of existing reporting tasks. In addition to integrating the data they have, the regulatory reporting management department of the bank's head office also relies on the reporting data of other business departments, first-tier banks, and subsidiaries. First-tier banks may rely on the data of their own business departments and second-tier banks. There are many related parties and work nodes involved, which makes management difficult. Summary of the invention

[0003] The present disclosure aims to solve one of the technical problems in the related art at least to some extent.

[0004] To this end, an object of the present disclosure is to propose a task calendar construction method.

[0005] The second objective of the present disclosure is to provide a task calendar construction device.

[0006] A third objective of the present disclosure is to provide an electronic device.

[0007] A fourth object of the present disclosure is to provide a non-transitory computer-readable storage medium.

[0008] A fifth object of the present disclosure is to provide a computer program product.

[0009] To achieve the above-mentioned purpose, the first aspect of the present disclosure proposes a task calendar construction method, including: obtaining a task set and at least one execution object chain, the execution object chain including at least one execution object, and the execution objects are arranged on the execution object chain in descending order of execution level; disassembling the task set to generate at least one task vector, and generating a chain vector based on the execution object chain; for any task vector, determining the target execution object chain processed by the task vector based on the chain vector and the task vector; matching the task vector and the execution objects on the target execution object chain in sequence to generate a matching value, until the matching value appears to be less than a matching threshold, and then stopping matching; generating a task calendar based on the execution objects that have been matched between the task vector and the target execution object chain.

[0010] According to one embodiment of the present disclosure, the task calendar is generated based on the task vector and the execution object that has been matched with the target execution object chain, including: obtaining the task execution time of the target execution object whose matching value is less than a matching threshold, generating a reminder timestamp for the target execution object based on the task execution time, and generating a supervision timestamp for other execution objects with an execution level greater than the target execution object based on the task execution time; and generating the task calendar based on the task vector, the reminder timestamp and the supervision timestamp.

[0011] According to one embodiment of the present disclosure, generating the task calendar based on the task vector, the reminder timestamp and the supervision timestamp includes: setting a first reminder level for the reminder timestamp, and setting a second reminder level for the supervision timestamp, wherein the first reminder level is adapted to all execution objects, and the second reminder level is adapted to execution objects other than the target execution object; generating the task calendar based on the task vector, the first reminder level, the second reminder level, the reminder timestamp and the supervision timestamp.

[0012] According to one embodiment of the present disclosure, generating the task calendar based on the task vector, the first reminder level, the second reminder level, the reminder timestamp and the supervision timestamp includes: establishing a first reminder event based on the task vector at the reminder timestamp in the candidate reminder calendar; and establishing a second reminder event based on the task vector at the supervision timestamp in the candidate reminder calendar.

[0013] According to one embodiment of the present disclosure, the task calendar is generated based on the execution object that has been matched with the task vector and the target execution object chain, including: when the first reminder event and / or the second reminder event is triggered, a feedback task is generated and sent to the execution object corresponding to the first reminder event and / or the second reminder event; and task processing progress information sent by the execution object based on the feedback task is received.

[0014] According to one embodiment of the present disclosure, the method also includes: in response to not receiving the task processing progress information sent by the execution object based on the feedback task, establishing multiple reminder timestamps in the task calendar according to a preset reminder cycle; and reminding the execution object at the reminder timestamp.

[0015] According to an embodiment of the present disclosure, the decomposing the task set to generate at least one task vector includes: dividing the task set into at least one subtask data according to a responsible person; and generating the task vector based on the subtask data.

[0016] According to one embodiment of the present disclosure, generating the task vector based on the subtask data includes: performing semantic decomposition on the subtask data to obtain multiple atomic features; determining responsible person information, responsible agency information and reporting object information from the atomic features; and establishing the task vector in a three-dimensional coordinate system based on the responsible person information, the responsible agency information and the reporting object information, wherein the three dimensions of the three-dimensional coordinate system are personnel, responsible agency and reporting object, respectively.

[0017] According to one embodiment of the present disclosure, determining the target execution object chain processed by the task vector based on the chain vector and the task vector includes: calculating the Euclidean distance between all chain vectors and the task vector; and taking the execution object chain corresponding to the chain vector with the smallest Euclidean distance as the target execution object chain of the target task vector.

[0018] To achieve the above-mentioned purpose, the second aspect embodiment of the present disclosure proposes a task calendar construction device, including: an acquisition module, used to acquire a task set and at least one execution object chain, the execution object chain including at least one execution object, and the execution objects are arranged on the execution object chain in order from large to small execution levels; a disassembly module, used to disassemble the task set to generate at least one task vector, and generate a chain vector based on the execution object chain; a determination module, used to determine, for any task vector, a target execution object chain processed by the task vector based on the chain vector and the task vector; a matching module, used to match the task vector and the execution objects on the target execution object chain in sequence to generate a matching value, until the matching value appears to be less than a matching threshold, and the matching is stopped; a generation module, used to generate a task calendar based on the task vector and the execution objects that have been matched by the target execution object chain.

[0019] To achieve the above-mentioned purpose, the third aspect embodiment of the present disclosure proposes an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to implement the task calendar construction method as described in the first aspect embodiment of the present disclosure.

[0020] To achieve the above-mentioned purpose, the fourth aspect of the present disclosure proposes a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to implement the task calendar construction method as described in the first aspect of the present disclosure.

[0021] To achieve the above-mentioned purpose, a fifth aspect of the present disclosure proposes a computer program product, including a computer program, which, when executed by a processor, is used to implement the task calendar construction method as described in the first aspect of the present disclosure.

[0022] By generating an execution object chain and generating a task vector based on a task set, the execution objects involved in executing the task vector and supervising the execution can be accurately determined, thereby generating a task calendar. This reduces the need for manual intervention through an automated task allocation and scheduling mechanism, improves work efficiency, avoids problems such as task omissions or duplications caused by human factors, and reduces the probability of errors. At the same time, the generated task calendar is clear and concise, making it easy for managers to keep track of task processing progress and personnel division of labor at any time. Best practice recommendations based on historical data and current situation analysis help leaders make more informed strategic decisions. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 is a schematic diagram of a task calendar construction method according to an embodiment of the present disclosure;

[0024] Figure 2 is a schematic diagram of another task calendar construction method according to an embodiment of the present disclosure;

[0025] Figure 3 is a schematic diagram of another task calendar construction method according to an embodiment of the present disclosure;

[0026] Figure 4 is a schematic diagram of another task calendar construction method according to an embodiment of the present disclosure;

[0027] Figure 5 is a schematic diagram of a task calendar construction device according to one embodiment of the present disclosure;

[0028] Figure 6 is a schematic diagram of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0029] Embodiments of the present disclosure are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, and should not be construed as limiting the present disclosure.

[0030] The information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in this disclosure are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data comply with the relevant provisions of relevant laws and regulations.

[0031] It should be noted that in the embodiments of the present disclosure, certain software, components, models and other existing solutions in the industry may be mentioned, which should be regarded as exemplary. Their purpose is only to illustrate the feasibility of the technical solution embodiments of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0032] Figure 1 is a schematic diagram of a task calendar construction method according to an embodiment of the present disclosure. Figure 1 As shown, the task calendar construction method includes the following steps:

[0033] S101, obtaining a task set and at least one execution object chain, wherein the execution object chain includes at least one execution object, and the execution objects are arranged on the execution object chain in descending order of execution level.

[0034] The task calendar construction method of the embodiment of the present application can be applied to the scenario where banking tasks are assigned step by step. The executor of the task calendar construction of the embodiment of the present application can be the task calendar construction device of the embodiment of the present application, and the task calendar construction device can be set on an electronic device.

[0035] It should be noted that the execution object chain refers to various processing objects on the same system. For example, the execution object chain may be the head office and branches in region A.

[0036] In another possible implementation, the execution object chain may also be a plurality of execution objects that cooperate to complete a certain process, for example, the purchaser, the supervisor, and the supplier of a certain procurement process.

[0037] The execution level refers to the level of the execution object in the execution object chain. In the execution object chain, the execution object with a higher execution level has the right to supervise the execution object with a lower execution level.

[0038] It should be noted that the execution level is designed in advance and can be changed according to actual design needs. No limitation is made here.

[0039] S102: Decompose the task set to generate at least one task vector, and generate a chain vector based on the execution object chain.

[0040] It should be noted that a task vector is an independent task, and the task vector may include a variety of information, which is not limited here. For example, the task vector may include the execution time, task identifier, and execution object of the task.

[0041] In the disclosed embodiment, there are many methods for disassembling the task set, which are not limited here. For example, the configuration information table can be disassembled by a disassembly model to generate a task vector. The disassembly model is trained in advance and stored in the storage space of the electronic device to facilitate retrieval and use when needed.

[0042] In another possible implementation, the task set may be calculated by a natural language algorithm to generate at least one task vector. The natural language algorithm may be designed in advance and may be changed according to actual design requirements, which is not limited here.

[0043] S103, for any task vector, determining a target execution object chain to be processed by the task vector based on the chain vector and the task vector.

[0044] In the embodiment of the present disclosure, after the chain vector and the task vector are obtained, the chain vector and the task vector may be calculated, and the target execution object chain may be determined according to the calculation result.

[0045] It should be noted that the calculation method may be various and is not limited here. For example, the similarity and distance between the chain vector and the task vector may be calculated.

[0046] S104: Match the task vector and the execution objects on the target execution object chain in sequence to generate a matching value.

[0047] In the embodiment of the present disclosure, the matching value is a judgment value for determining whether the execution object is an executor of the task vector. The larger the matching value, the more likely the execution object is the executor of the task vector.

[0048] S105, until the matching value is less than the matching threshold, the matching is stopped, and a task calendar is generated based on the task vector and the execution objects that have been matched in the target execution object chain.

[0049] In the embodiment of the present disclosure, the matching threshold is a critical value for determining whether the execution object is a task vector executor.

[0050] In actual operation, the task vector may not be executed by one execution object, but requires multiple execution objects to cooperate or operate simultaneously. At the same time, in normal operation, the execution object with the lowest level is generally the first executor of the task vector. Objects with lower execution levels than the first executor can be considered not to participate in the processing of the task vector. At the same time, objects with higher levels generally have the right to supervise the execution of objects with lower levels. Therefore, when the matching value is less than the matching threshold, the matching is stopped, and the execution objects that have been matched are used as executors or supervisors of the task vector.

[0051] In the disclosed embodiment, firstly, a task set and at least one execution object chain are obtained, the execution object chain includes at least one execution object, and the execution objects are arranged on the execution object chain in descending order of execution level, then the task set is disassembled to generate at least one task vector, and then for any task vector, the target execution object chain processed by the task vector is determined, and then the task vector and the execution objects on the target execution object chain are matched in sequence to generate a matching value, and finally until the matching value is less than the matching threshold, the matching is stopped, and a task calendar is generated based on the task vector and the execution objects that have been matched by the target execution object chain. Thus, by generating an execution object chain and generating a task vector according to the task set, the execution objects that participate in the execution of the task vector and supervise the execution can be accurately determined, so as to generate a task calendar, so as to reduce the need for manual intervention, improve work efficiency, avoid problems such as task omission or duplication caused by human factors, and reduce the probability of errors through an automated task allocation and scheduling mechanism, and at the same time, the generated task calendar is clear and concise, which is convenient for managers to grasp the progress of task processing and the division of labor of personnel at any time, and the best practice recommendations based on historical data and current situation analysis help leaders make more wise strategic decisions.

[0052] In the above embodiment, the task calendar is generated based on the task vector and the execution object that has been matched with the target execution object chain, and the task calendar can also be generated by Figure 2 Explaining further, the method includes:

[0053] S201, obtaining the task execution time of the target execution object whose matching value is less than the matching threshold, generating a reminder timestamp for the target execution object based on the task execution time, and generating a supervision timestamp for other execution objects with an execution level greater than the target execution object based on the task execution time.

[0054] The task execution time is the execution time configured in the task collection.

[0055] It should be noted that there may be multiple reminder timestamps and supervision timestamps, which are used to remind the target execution object and other execution objects to pay attention to the execution progress of the task vector multiple times.

[0056] In the embodiments of the present disclosure, there may be multiple methods for generating reminder timestamps and supervision timestamps, which are not limited here.

[0057] In one possible implementation, the task execution time can be processed according to preset generation rules. For example, a time value for an advance reminder can be set, and a reminder timestamp and a supervision timestamp can be determined based on the time value and the task execution time. The time value can be multiple, so multiple reminder timestamps and supervision timestamps can be established.

[0058] In another possible implementation, the task execution time can also be input into a timestamp determination model to generate a reminder timestamp and a supervision timestamp. The timestamp determination model is trained in advance and can be stored in a storage space of an electronic device for easy retrieval when needed.

[0059] S202, generating a task calendar based on the task vector, the reminder timestamp and the supervision timestamp.

[0060] In an embodiment of the present disclosure, a first reminder level can be set for the reminder timestamp, and a second reminder level can be set for the supervision timestamp, wherein the first reminder level is adapted to all execution objects, and the second reminder level is adapted to execution objects other than the target execution object, and then a task calendar is generated based on the task vector, the first reminder level, the second reminder level, the reminder timestamp and the supervision timestamp.

[0061] It should be noted that the first reminder level is only used to remind all execution objects, and the second reminder level is used to remind execution objects other than the target execution object. Therefore, by setting different reminder levels, each execution object can know what they should pay attention to without spending too much time and energy to find relevant information. It can also help the execution object better remember important dates and events and reduce the possibility of forgetting.

[0062] In the disclosed embodiment, a task calendar is generated based on the task vector, the first reminder level, the second reminder level, the reminder timestamp, and the supervision timestamp. A first reminder event can be established based on the task vector at the reminder timestamp in the candidate reminder calendar, and a second reminder event can be established based on the task vector at the supervision timestamp in the candidate reminder calendar. Thus, by setting up reminder levels, the executors and supervisors in the execution object chain can be distinguished, and different types of reminders can be set for different roles.

[0063] In the disclosed embodiment, the task execution time of the target execution object whose matching value is less than the matching threshold is first obtained, a reminder timestamp is generated for the target execution object based on the task execution time, and a supervision timestamp is generated for other execution objects whose execution level is greater than the target execution object based on the task execution time, and then a task calendar is generated based on the task vector, the reminder timestamp and the supervision timestamp. Thus, in this way, the overall efficiency of the execution object chain in completing the task vector can be improved, and delays and errors caused by poor communication can be reduced. This method also helps to promote the development of personal responsibility, so that everyone is clear about their responsibilities and knows when to take action.

[0064] In the above embodiment, the task calendar is generated based on the task vector and the execution object that has been matched with the target execution object chain, and the task calendar can also be generated by Figure 3 Explaining further, the method includes:

[0065] S301, when a first reminder event and / or a second reminder event is triggered, a feedback task is generated and sent to an execution object corresponding to the first reminder event and / or the second reminder event.

[0066] S302, receiving task processing progress information sent by the execution object based on the feedback task.

[0067] In actual operation, when the first reminder event and / or the second reminder event is triggered, the corresponding execution object may not receive the first reminder event and / or the second reminder event or may not have the conditions to receive the first reminder event and / or the second reminder event, which will affect the timely execution of the task vector.

[0068] In order to prevent this situation from happening, the present disclosure proposes to generate a feedback task to realize a secondary reminder to the corresponding execution object, and at the same time, the task processing progress information of the execution object can be collected.

[0069] It should be noted that the feedback task can be sent to the execution object corresponding to the first reminder event and / or the second reminder event in various forms, which are not limited here. For example, it can be sent in the form of text message, phone call, email, etc.

[0070] In the embodiment of the present disclosure, when the first reminder event and / or the second reminder event are triggered, a feedback task is generated and sent to the execution object corresponding to the first reminder event and / or the second reminder event, and then the task processing progress information sent by the execution object based on the feedback task is received. Thus, by generating a feedback task and sending it to the execution object, it is possible to avoid the situation where the execution object does not receive the first reminder event and / or the second reminder event or does not have the conditions to receive the first reminder event and / or the second reminder event, and at the same time, the progress of the current task execution can be timely controlled, thereby improving the practicality of the present disclosure solution.

[0071] In another possible implementation, in response to not receiving the task processing progress information sent by the execution object based on the feedback task, multiple reminder timestamps are established in the task calendar according to the preset reminder cycle. In response to not receiving the task processing progress information sent by the execution object based on the feedback task, multiple reminder timestamps are established in the task calendar according to the preset reminder cycle. In this way, it can be prevented that the execution object cannot be notified through the feedback task, and the execution object can be further reminded through multiple reminder timestamps, which can further improve the timeliness of task completion.

[0072] In the above embodiment, the task set is decomposed to generate at least one task vector, and the task vector can also be generated by Figure 4 Explaining further, the method includes:

[0073] S401: Divide a task set into at least one subtask data according to the responsible person.

[0074] In the embodiment of the present disclosure, there may be multiple task sets, which are not limited here. For example, the task set may be displayed in the form of a report, for example, as shown in the following table:

[0075]

[0076]

[0077] Each row in the report can be regarded as a subtask data.

[0078] S402: Generate a task vector based on the subtask data.

[0079] In the disclosed embodiment, the subtask data may first be semantically decomposed to obtain multiple atomic features, and then the responsible person information, responsible agency information and reporting object information may be determined from the atomic features. Finally, a task vector may be established in a three-dimensional coordinate system based on the responsible person information, responsible agency information and reporting object information, wherein the three dimensions of the three-dimensional coordinate system are personnel, responsible agency and reporting object, respectively.

[0080] In the embodiments of the present disclosure, it should be noted that the atomic feature refers to the smallest, indivisible basic feature or attribute.

[0081] Atomic features may include lexical features, lexical tags, word stems, etc.

[0082] In the embodiments of the present disclosure, there may be many methods for decomposing historical event data to obtain multiple atomic features, and no limitation is made here.

[0083] In a possible implementation, the historical event data may be decomposed by a decomposition model to obtain multiple atomic features. The decomposition model is trained in advance and may be stored in a storage space of an electronic device.

[0084] In another possible implementation, the historical event data can be calculated through a decomposition algorithm to obtain multiple atomic features. The decomposition algorithm can be changed according to actual design needs. Thus, by converting text information into vectors, complex tasks can be decomposed into several relatively independent small tasks, which is conducive to clarifying the responsible persons and responsible units of each part and improving the efficiency of task processing.

[0085] In an embodiment of the present disclosure, the target execution object chain for task vector processing is determined based on the chain vector and the task vector. The Euclidean distances of all chain vectors and task vectors may be calculated first, and then the execution object chain corresponding to the chain vector with the smallest Euclidean distance may be used as the target execution object chain for the target task vector.

[0086] It should be noted that the smaller the Euclidean distance between the chain vector and the task vector, the greater the possibility that the execution object chain corresponding to the chain vector is the target execution object chain of the task vector. By calculating the Euclidean distance to determine the target execution object chain, the optimal option can be quickly screened out from many alternatives, saving time and energy. At the same time, since the Euclidean distance is a mathematical measurement method, this method is not only applicable to simple linear relationships, but also can handle more complex situations, such as those involving multiple variables.

[0087] Corresponding to the task calendar construction method provided in the above-mentioned embodiments, an embodiment of the present disclosure also provides a task calendar construction device. Since the task calendar construction device provided in the embodiment of the present disclosure corresponds to the task calendar construction method provided in the above-mentioned embodiments, the implementation method of the above-mentioned task calendar construction method is also applicable to the task calendar construction device provided in the embodiment of the present disclosure, and will not be described in detail in the following embodiments.

[0088] Figure 5 is a schematic diagram of a task calendar construction device according to an embodiment of the present disclosure. Figure 5 As shown, the task calendar construction device 500 includes: an acquisition module 510, a disassembly module 520, a determination module 530, a matching module 540 and a generation module 550.

[0089] The acquisition module 510 is used to acquire a task set and at least one execution object chain, where the execution object chain includes at least one execution object, and the execution objects are arranged on the execution object chain in descending order of execution level.

[0090] The disassembly module 520 is used to disassemble the task set to generate at least one task vector, and generate a chain vector based on the execution object chain.

[0091] The determination module 530 is used to determine, for any task vector, a target execution object chain to be processed by the task vector based on the chain vector and the task vector.

[0092] A matching module 540 is used to sequentially match the task vector with the execution objects on the target execution object chain to generate a matching value, and stop matching until the matching value is less than a matching threshold.

[0093] The generating module 550 is used to generate a task calendar based on the task vector and the execution object that has been matched with the target execution object chain.

[0094] In the embodiment of the present disclosure, the generation module 550 is also used to: obtain the task execution time of the target execution object whose matching value is less than the matching threshold, generate a reminder timestamp for the target execution object based on the task execution time, and generate a supervision timestamp for other execution objects with an execution level greater than the target execution object based on the task execution time; generate a task calendar based on the task vector, the reminder timestamp and the supervision timestamp.

[0095] In the embodiment of the present disclosure, the generation module 550 is also used to: set a first reminder level for the reminder timestamp, and set a second reminder level for the supervision timestamp, wherein the first reminder level is adapted to all execution objects, and the second reminder level is adapted to execution objects other than the target execution object; generate a task calendar based on the task vector, the first reminder level, the second reminder level, the reminder timestamp and the supervision timestamp.

[0096] In the disclosed embodiment, the generating module 550 is further used to: establish a first reminder event based on the task vector at the reminder timestamp in the candidate reminder calendar; and establish a second reminder event based on the task vector at the supervision timestamp in the candidate reminder calendar.

[0097] In the embodiment of the present disclosure, the generation module 550 is also used to: when the first reminder event and / or the second reminder event is triggered, generate a feedback task and send it to the execution object corresponding to the first reminder event and / or the second reminder event; receive task processing progress information sent by the execution object based on the feedback task.

[0098] In an embodiment of the present disclosure, the device is also used to: in response to not receiving task processing progress information sent by the execution object based on the feedback task, establish multiple reminder timestamps in the task calendar according to a preset reminder cycle; and remind the execution object at the reminder timestamp.

[0099] In the embodiment of the present disclosure, the disassembly module 520 is further used to: divide the task set into at least one subtask data according to the responsible person; and generate a task vector based on the subtask data.

[0100] In the disclosed embodiment, the disassembly module 520 is also used to: perform semantic decomposition on subtask data to obtain multiple atomic features; determine the responsible person information, responsible agency information and reporting object information from the atomic features; establish a task vector in a three-dimensional coordinate system based on the responsible person information, responsible agency information and reporting object information, wherein the three dimensions of the three-dimensional coordinate system are personnel, responsible agency and reporting object, respectively.

[0101] In the disclosed embodiment, the determination module 530 is further used to: calculate the Euclidean distances between all chain vectors and task vectors; and use the execution object chain corresponding to the chain vector with the smallest Euclidean distance as the target execution object chain of the target task vector.

[0102] By generating an execution object chain and generating a task vector based on a task set, the execution objects involved in executing the task vector and supervising the execution can be accurately determined, thereby generating a task calendar. This reduces the need for manual intervention through an automated task allocation and scheduling mechanism, improves work efficiency, avoids problems such as task omissions or duplications caused by human factors, and reduces the probability of errors. At the same time, the generated task calendar is clear and concise, making it easy for managers to keep track of task processing progress and personnel division of labor at any time. Best practice recommendations based on historical data and current situation analysis help leaders make more informed strategic decisions.

[0103] In order to implement the above embodiment, the present disclosure further provides an electronic device 600, Figure 6 is a schematic diagram of an electronic device according to an embodiment of the present disclosure, such as Figure 6 As shown, the electronic device 600 includes: a processor 601 and a memory 602 that is communicatively connected to the processor, the memory 602 stores instructions that can be executed by at least one processor, and the instructions are executed by at least one processor 601 to implement the present disclosure. Figure 1-Figure 4 A task calendar construction method of an embodiment.

[0104] In order to implement the above embodiments, the present disclosure also provides a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable the computer to implement the above embodiments. Figure 1-Figure 4 A task calendar construction method of an embodiment.

[0105] In order to implement the above embodiments, the present disclosure also provides a computer program product, including a computer program. When the computer program is executed by a processor, the computer program implements the above embodiments. Figure 1-Figure 4 A task calendar construction method of an embodiment.

[0106] It should be noted that personal information from users should be collected for legitimate and reasonable purposes and should not be shared or sold outside of these legitimate uses. In addition, such collection / sharing should be carried out after receiving the user's informed consent, including but not limited to notifying the user to read the user agreement / user notice and sign the agreement / authorization including authorization of relevant user information before the user uses the function. In addition, any necessary steps should be taken to protect and safeguard access to such personal information data and ensure that others who have access to personal information data comply with its privacy policy and procedures.

[0107] The present application is expected to provide an implementation scheme for users to selectively block the use or access of personal information data. That is, the present disclosure is expected to provide hardware and / or software to prevent or block access to such personal information data. Once the personal information data is no longer needed, the risk can be minimized by limiting data collection and deleting the data. In addition, when applicable, such personal information is de-identified to protect the privacy of the user.

[0108] In the description of the aforementioned embodiments, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0109] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0110] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.

[0111] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purpose of this specification, "computer-readable medium" can be any device that contains, stores, communicates, propagates or transmits a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples (non-exhaustive list) of computer-readable media include the following: an electrical connection with one or more wires (electronic device), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing in other suitable ways if necessary, and then stored in a computer memory.

[0112] It should be understood that the various parts of the present application can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0113] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

[0114] In addition, each functional unit in each embodiment of the present application may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0115] The storage medium mentioned above may be a read-only memory, a magnetic disk or an optical disk, etc. Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limiting the present application. A person of ordinary skill in the art may change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A task calendar construction method, characterized in that: include: Acquire a task set and at least one execution object chain, wherein the execution object chain includes at least one execution object, and the execution objects are arranged on the execution object chain in descending order of execution level; Decomposing the task set to generate at least one task vector, and generating a chain vector based on the execution object chain; For any task vector, determining a target execution object chain processed by the task vector based on the chain vector and the task vector; Matching the task vector and the execution objects on the target execution object chain in sequence to generate a matching value, and stopping the matching when the matching value is less than a matching threshold; A task calendar is generated based on the task vector and the execution object that has been matched with the target execution object chain.

2. The method according to claim 1, characterized in that The generating a task calendar based on the task vector and the execution object that has been matched with the target execution object chain includes: Obtaining the task execution time of the target execution object whose matching value is less than the matching threshold, generating a reminder timestamp for the target execution object based on the task execution time, and generating a supervision timestamp for other execution objects whose execution levels are greater than the target execution object based on the task execution time; The task calendar is generated based on the task vector, the reminder timestamp and the supervision timestamp.

3. The method according to claim 2, characterized in that The generating the task calendar based on the task vector, the reminder timestamp and the supervision timestamp comprises: Setting a first reminder level for the reminder timestamp, and setting a second reminder level for the supervision timestamp, wherein the first reminder level is adapted to all execution objects, and the second reminder level is adapted to execution objects other than the target execution object; The task calendar is generated based on the task vector, the first reminder level, the second reminder level, the reminder timestamp, and the supervision timestamp.

4. The method according to claim 3, characterized in that The generating the task calendar based on the task vector, the first reminder level, the second reminder level, the reminder timestamp and the supervision timestamp comprises: At the reminder timestamp in the candidate reminder calendar, establishing a first reminder event based on the task vector; and, A second reminder event is established based on the task vector at the supervision timestamp in the candidate reminder calendar.

5. The method according to claim 4, characterized in that The generating a task calendar based on the task vector and the execution object that has been matched with the target execution object chain includes: When the first reminder event and / or the second reminder event is triggered, a feedback task is generated and sent to an execution object corresponding to the first reminder event and / or the second reminder event; Receive task processing progress information sent by the execution object based on the feedback task.

6. The method according to claim 5, characterized in that The method further comprises: In response to not receiving the task processing progress information sent by the execution object based on the feedback task, establishing a plurality of reminder timestamps in the task calendar according to a preset reminder cycle; The execution object is reminded at the reminder timestamp.

7. The method according to claim 1, characterized in that The step of decomposing the task set to generate at least one task vector includes: Dividing the task set into at least one subtask data according to the responsible person; The task vector is generated based on the subtask data.

8. The method according to claim 7, characterized in that The generating the task vector based on the subtask data comprises: Performing semantic decomposition on the subtask data to obtain multiple atomic features; Determine the responsible person information, responsible agency information and reporting object information from the atomic features; The task vector is established in a three-dimensional coordinate system based on the responsible person information, the responsible organization information and the reporting object information, wherein the three dimensions of the three-dimensional coordinate system are personnel, responsible organization and reporting object respectively.

9. The method according to claim 1, characterized in that The step of determining the target execution object chain processed by the task vector based on the chain vector and the task vector includes: Calculating the Euclidean distances between all chain vectors and the task vector; The execution object chain corresponding to the chain vector with the smallest Euclidean distance is used as the target execution object chain of the target task vector.

10. A task calendar construction device, characterized in that: include: An acquisition module, used to acquire a task set and at least one execution object chain, wherein the execution object chain includes at least one execution object, and the execution objects are arranged on the execution object chain in descending order of execution level; A disassembly module, configured to disassemble the task set to generate at least one task vector, and generate a chain vector based on the execution object chain; a determination module, configured to determine, for any task vector, a target execution object chain processed by the task vector based on the chain vector and the task vector; A matching module, used for sequentially matching the task vector with the execution objects on the target execution object chain to generate a matching value, and stopping the matching until the matching value is less than a matching threshold; A generation module is used to generate a task calendar based on the task vector and the execution object that has been matched with the target execution object chain.

11. The device according to claim 10, characterized in that The generating module is further used for: Obtaining the task execution time of the target execution object whose matching value is less than the matching threshold, generating a reminder timestamp for the target execution object based on the task execution time, and generating a supervision timestamp for other execution objects whose execution levels are greater than the target execution object based on the task execution time; The task calendar is generated based on the task vector, the reminder timestamp and the supervision timestamp.

12. The device according to claim 11, characterized in that The generating module is further used for: Setting a first reminder level for the reminder timestamp, and setting a second reminder level for the supervision timestamp, wherein the first reminder level is adapted to all execution objects, and the second reminder level is adapted to execution objects other than the target execution object; The task calendar is generated based on the task vector, the first reminder level, the second reminder level, the reminder timestamp, and the supervision timestamp.

13. The device according to claim 12, characterized in that The generating module is further used for: At the reminder timestamp in the candidate reminder calendar, establishing a first reminder event based on the task vector; as well as, A second reminder event is established based on the task vector at the supervision timestamp in the candidate reminder calendar.

14. The device according to claim 13, characterized in that The generating module is further used for: When the first reminder event and / or the second reminder event is triggered, a feedback task is generated and sent to an execution object corresponding to the first reminder event and / or the second reminder event; Receive task processing progress information sent by the execution object based on the feedback task.

15. The device according to claim 14, characterized in that The device is also used for: In response to not receiving the task processing progress information sent by the execution object based on the feedback task, establishing a plurality of reminder timestamps in the task calendar according to a preset reminder cycle; The execution object is reminded at the reminder timestamp.

16. The device according to claim 1, characterized in that The disassembly module is also used for: Dividing the task set into at least one subtask data according to the responsible person; The task vector is generated based on the subtask data.

17. The device according to claim 16, characterized in that The disassembly module is also used for: Performing semantic decomposition on the subtask data to obtain multiple atomic features; Determine the responsible person information, responsible agency information and reporting object information from the atomic features; The task vector is established in a three-dimensional coordinate system based on the responsible person information, the responsible organization information and the reporting object information, wherein the three dimensions of the three-dimensional coordinate system are personnel, responsible organization and reporting object respectively.

18. The device according to claim 17, characterized in that The determining module is further used for: Calculating the Euclidean distances between all chain vectors and the task vector; The execution object chain corresponding to the chain vector with the smallest Euclidean distance is used as the target execution object chain of the target task vector.

19. An electronic device, characterized in that: Including memory and processor; The processor runs a program corresponding to the executable program code by reading the executable program code stored in the memory, so as to implement the method according to any one of claims 1 to 9.

20. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 9 when executed by a processor.

21. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images