Task processing method and device and electronic equipment

Abstract

The invention provides a task processing method and device and electronic equipment, and the method comprises the steps: splitting an original outsourcing timed task, and obtaining a plurality of subtasks; screening a target sub-task in the plurality of sub-tasks, and packaging to obtain a target timed task; the target sub-task comprises the asset net value, the outsourcing scale, the outsourcing cost, the outsourcing rate, the life cycle and the solidified data of the outsourcing scale, and the service outsourcing system synchronizes to the asset service management system; in response to a received task processing instruction, executing a target sub-task in the target timed task based on a target execution strategy corresponding to the execution parameter; the task processing instruction is sent by the distributed task scheduling platform. According to the method, the subtasks in the original outsourcing timed task are recombined, the task granularity is refined, and the coupling between the tasks is reduced. According to the method, by reducing the coupling between the tasks, task management is facilitated, and the data security risk of batch tasks is reduced.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a task processing method, device and electronic device. Background Art

[0002] In the era of big data, all industries face enormous demands for data processing. To alleviate this pressure, these industries are turning to data outsourcing, essentially transferring tasks to other companies. After the outsourced tasks are completed, data migration is required to synchronize the outsourced data from the outsourced system with the company's own asset management system.

[0003] In related technologies, outsourced data is synchronized by reading outsourced data stored in the outsourcing system's database through an outsourced scheduled task and then storing the outsourced data in the company's asset business management system. However, because outsourced scheduled tasks include multiple tasks, each of which includes corresponding subtasks, the subtasks are highly coupled. Consequently, if an exception occurs in one subtask during data synchronization, it will cause anomalies in the data of multiple subtasks, leading to anomalies in the data of all modules in the asset business management system. Summary of the Invention

[0004] The present application provides a task processing method, device and electronic device to at least solve the above technical problems existing in the prior art.

[0005] In a first aspect of the present application, a task processing method is provided, comprising: Split the original outsourced scheduled task into multiple subtasks; Filtering target subtasks from the plurality of subtasks and encapsulating them to obtain target scheduled tasks; the target scheduled tasks are used to synchronize outsourced data from the business outsourcing system to the asset business management system, and the target subtasks include net asset value synchronization tasks, outsourcing scale synchronization tasks, outsourcing expense synchronization tasks, outsourcing rate synchronization tasks, lifecycle synchronization tasks, and outsourcing scale solidification; In response to receiving a task processing instruction, a target subtask in the target scheduled task is executed based on a target execution strategy corresponding to the execution parameters; the task processing instruction is sent by a distributed task scheduling platform.

[0006] In one embodiment, after receiving the task processing instruction, the method further includes: setting execution parameters, wherein the execution parameters include execution mode type, task type, product number and data date; wherein, The execution mode types include serial mode and parallel mode; The task types include net asset value synchronization, outsourcing scale synchronization, outsourcing cost synchronization, outsourcing rate synchronization, lifecycle synchronization, outsourcing scale solidification processing, forced re-run, execution of all subtasks, and no processing; The product number is the number of the product corresponding to the target scheduled task; The data date is the date corresponding to the data processed by the corresponding task.

[0007] In one possible implementation, executing a target subtask in the target scheduled task based on a target execution strategy corresponding to the execution parameter includes: Based on task processing instructions, obtain product account information in the business outsourcing system; Based on the product account information, a query interface is called to obtain corresponding outsourcing data; the query interface encapsulates a query command, and the query command is used to obtain the outsourcing data including: net asset value, outsourcing scale, outsourcing fee, outsourcing rate, life cycle and outsourcing scale solidification data; The target subtask in the target scheduled task is executed based on the target execution strategy corresponding to the execution parameter, so as to synchronize the outsourcing data corresponding to the target subtask from the business outsourcing system to the asset business management system.

[0008] In one possible implementation, executing the target subtask in the target scheduled task based on the target execution strategy corresponding to the execution parameter includes: Determine whether the task type is lifecycle synchronization; In response to the task type being lifecycle synchronization, performing lifecycle synchronization; Determine whether there are records of synchronization failures in the net asset value, outsourcing scale, and life cycle data, and whether any of them have data changes. If not, solidify the outsourcing scale.

[0009] In one possible implementation, executing the target subtask in the target scheduled task based on the target execution strategy corresponding to the execution parameter further includes: In response to the task type not being lifecycle synchronization, determining whether the execution mode type is a parallel mode; In response to the execution mode type being the parallel mode, simultaneously executing the data synchronization of the net asset value, the outsourcing scale, the outsourcing expense, and the outsourcing rate in a multi-threaded manner; In response to the execution mode type being the serial mode, determining whether the task type is any one of net asset value synchronization, forced rerun, or no processing; If the task type is any one of NAV synchronization, forced rerun, or not processing, then determine whether the task type is not processing and the execution parameter is set with a product account, and if the task type is not processing and the execution parameter is set with a product account, set the target subtask corresponding to the product account to not processing; After the task type is not "not processed" and the execution parameter is set to a product account or the target subtask corresponding to the product account is set to "not processed", determining whether the task type is net asset value synchronization; In response to the task type being net asset value synchronization, setting the net asset value synchronization record status to unprocessed, and if the execution parameter sets a product account, setting the record of the product account to unprocessed; In response to the task type not being a net asset value synchronization or setting the net asset value synchronization record status to unprocessed, and if the product account does not exist, setting the record of the product account to unprocessed, synchronizing the net asset value; After the NAV is synchronized, determine whether there are any projects that have not been synchronized with the outsourcing rate; In response to the existence of a project for which outsourcing rate synchronization has not been performed, performing outsourcing rate synchronization on the project for which outsourcing rate synchronization has not been performed; Perform lifecycle synchronization; Determine whether there are records of synchronization failures in the net asset value, outsourcing scale, and life cycle data, and whether any of them have data changes. If not, solidify the outsourcing scale.

[0010] In one embodiment, in response to the task type not being any one of net asset value synchronization, forced rerun, or no processing, determining whether the task type is outsourced scale synchronization; In response to the task type being outsourced scale synchronization, setting the outsourced scale synchronization record to unprocessed and the corresponding product number to unprocessed, and performing outsourced scale synchronization; In response to the task type not being outsourcing scale synchronization, determining whether the task type is outsourcing cost synchronization; In response to the task type being outsourcing expense synchronization, setting the outsourcing expense synchronization record to unprocessed and the corresponding product number to unprocessed, and performing outsourcing expense synchronization; In response to the task type not being outsourced expense synchronization, determining whether the task type is outsourced rate synchronization; In response to the task type being outsourcing rate synchronization, setting the outsourcing rate synchronization record to unprocessed and the corresponding product number to unprocessed, and performing outsourcing rate synchronization; In response to the task type not being outsourcing rate synchronization, determining whether the task type is outsourcing scale solidification processing; In response to the task type being outsourcing scale solidification processing, outsourcing scale solidification is performed.

[0011] In one embodiment, in response to the task type not being lifecycle synchronization, the method further includes: Determine whether the product account information for the day is synchronized successfully; In response to the successful synchronization of the product account information for the day, determining whether the task type is a forced rerun; In response to the failure to synchronize the product account information on that day or the task type being forced re-run, the synchronized product account information is deleted, the product account information is obtained from the business outsourcing system, and the outsourcing data corresponding to the product account information is obtained.

[0012] In one possible implementation, if there is data anomaly during the execution of a target subtask, an alarm is issued; the target subtask is any one of all target subtasks.

[0013] A second aspect of the present application provides a task processing device, comprising: Splitting module, used to split the original outsourced scheduled task into multiple subtasks; An encapsulation module is used to filter target subtasks from the plurality of subtasks and encapsulate them to obtain target scheduled tasks; the target scheduled tasks are used to synchronize outsourced data from the business outsourcing system to the asset business management system, and the target subtasks include net asset value synchronization tasks, outsourcing scale synchronization tasks, outsourcing expense synchronization tasks, outsourcing rate synchronization tasks, lifecycle synchronization tasks, and outsourcing scale solidification tasks; The execution module is used to execute the target subtask in the target scheduled task based on the target execution strategy corresponding to the execution parameters in response to receiving the task processing instruction; the task processing instruction is sent by the distributed task scheduling platform.

[0014] According to a third aspect of the present application, an electronic device is provided, including: At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method described in the present application.

[0015] The task processing method, device, and electronic device of this application reorganize the subtasks in the original outsourced scheduled task, refine the task granularity, and reduce the coupling between tasks. By reducing the coupling between tasks, this application facilitates task management and reduces the data security risks of running batch tasks.

[0016] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The above and other objects, features and advantages of the exemplary embodiments of the present application will become readily understood by reading the detailed description below with reference to the accompanying drawings. In the accompanying drawings, several embodiments of the present application are shown in an illustrative and non-limiting manner, in which: In the drawings, the same or corresponding reference numerals denote the same or corresponding parts.

[0018] Figure 1 The process diagram of the task processing method of the embodiment of the present application is shown Figure 1 ; Figure 2 The process diagram of the task processing method of the embodiment of the present application is shown Figure 2 ; Figure 3 The process diagram of the task processing method of the embodiment of the present application is shown Figure 3 ; Figure 4 The process diagram of the task processing method of the embodiment of the present application is shown Figure 4 ; Figure 5 The process diagram of the task processing method of the embodiment of the present application is shown Figure 5 ; Figure 6 A schematic diagram of the structure of a task processing device according to an embodiment of the present application is shown; Figure 7 A schematic diagram of the structure of an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0019] In order to make the purpose, features, and advantages of this application more obvious and easy to understand, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without making creative efforts shall fall within the scope of protection of this application.

[0020] The following describes a task processing method, device, and electronic device provided by the present application in conjunction with the accompanying drawings.

[0021] like Figure 1 As shown, the present application provides a task processing method, including: S101: Split the original outsourced scheduled task into multiple subtasks.

[0022] The task processing method provided in the present application can be implemented through electronic devices. The electronic device can be a smart terminal or a server; wherein, the smart terminal can be a mobile phone, a personal digital assistant (PAD), a tablet computer, a laptop computer, a desktop computer and other devices. The server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN) services, as well as basic cloud computing services such as big data and artificial intelligence platforms. The electronic device is equipped with the asset business management system of the enterprise. The task processing method provided in the present application can realize the synchronization of outsourced data from the business outsourcing system to the asset business management system.

[0023] This application identifies the outsourced projects within each product project and the original scheduled tasks for the outsourced projects. The original scheduled outsourced tasks are broken down into scheduled outsourced expense tasks, scheduled outsourced scale synchronization tasks, lifecycle tasks, and outsourced scale solidification tasks. The outsourced expense tasks are further divided into tasks for synchronizing outsourced expense receivables and net asset value. The outsourced scale tasks are further divided into tasks for synchronizing outsourced scale and outsourced rate. The lifecycle tasks are further divided into tasks for independent oversight projects and the outsourced project lifecycle.

[0024] In this application, outsourcing expense timing tasks, outsourcing scale synchronization timing tasks, life cycle tasks, outsourcing scale solidification tasks, outsourcing expense receivable synchronization tasks, net asset value synchronization tasks, outsourcing scale synchronization tasks, outsourcing rate synchronization tasks, independent supervision projects and outsourcing project life cycle are all regarded as subtasks.

[0025] S102, filter the target subtasks from the multiple subtasks and encapsulate them to obtain target scheduled tasks; the target scheduled tasks are used to synchronize the outsourced data from the business outsourcing system to the asset business management system, and the target subtasks include net asset value synchronization tasks, outsourcing scale synchronization tasks, outsourcing cost synchronization tasks, outsourcing rate synchronization tasks, life cycle synchronization tasks and outsourcing scale solidification.

[0026] To reduce the coupling between subtasks, this application selects six subtasks from multiple subtasks: net asset value synchronization task, outsourcing scale synchronization task, outsourcing expense synchronization task, outsourcing rate synchronization task, lifecycle synchronization task, and outsourcing scale solidification synchronization task as target subtasks. These six target subtasks are reorganized and encapsulated into a target scheduled task.

[0027] It should be noted that executing the target subtasks can synchronize data on net asset value, outsourcing scale, outsourcing fees, outsourcing rates, lifecycle, and outsourcing scale. This means synchronizing outsourcing data from the business outsourcing system to the asset business management system.

[0028] S103 , in response to receiving a task processing instruction, executing a target subtask in the target scheduled task based on a target execution strategy corresponding to the execution parameters; the task processing instruction is sent by a distributed task scheduling platform.

[0029] In this application, a distributed task scheduling platform issues task processing instructions to the asset business management system. The asset business management system executes the target subtasks within the target scheduled task based on the target execution policy corresponding to the execution parameters, achieving synchronization of outsourced data. Users can configure task monitoring instructions based on their needs. For example, a scheduled data synchronization can be set on the distributed task scheduling platform. When the scheduled time is reached, the distributed task scheduling platform sends the task processing instructions to the asset business management system.

[0030] Execution parameters can be parameters set by the user in advance. For example, the execution parameters can select the target subtask that needs to be executed at the moment, and choose whether to execute the target subtask in serial or parallel. This application sets a target execution strategy based on the execution parameters, and the target execution strategy executes the target subtask in the target scheduled task.

[0031] The task processing method provided by this application refines the task granularity and reduces the coupling between subtasks by splitting and reorganizing the original outsourced scheduled tasks. At the same time, this application executes the target subtasks according to the target execution strategy by setting execution parameters, thereby synchronizing outsourced data from the business outsourcing system to the asset business management system. By reducing the coupling between tasks and using execution parameters to execute tasks, this application can facilitate task management and reduce the data security risks of batch tasks.

[0032] In some embodiments, after receiving the task processing instruction, the method further includes: setting execution parameters, wherein the execution parameters include execution mode type, task type, product number, and data date; wherein, The execution mode types include serial mode and parallel mode; The task types include net asset value synchronization, outsourcing scale synchronization, outsourcing cost synchronization, outsourcing rate synchronization, lifecycle synchronization, outsourcing scale solidification processing, forced re-run, execution of all subtasks, and no processing; The product number is the number of the product corresponding to the target scheduled task; The data date is the date corresponding to the data processed by the corresponding task.

[0033] In this application, the execution parameters include the execution mode type, task type, product number, and data date. The execution parameter format is: whether concurrent & task type & product number & data date.

[0034] Execution modes include serial and parallel. If the execution mode is serial, the execution order is sequential: net asset value synchronization, outsourced scale synchronization, outsourced expense synchronization, outsourced rate synchronization, lifecycle synchronization, and outsourced scale fixation synchronization. The low coupling between the target subtasks prevents them from interfering with each other. Even if an exception occurs during the execution of a target subtask, it will not affect other target subtasks. If an exception occurs in any target subtask, it can be rerun to resolve the exception. If the execution mode is parallel, multiple threads can be launched simultaneously to execute the target subtasks. For example, four threads can be launched simultaneously to execute the net asset value synchronization task, outsourced scale synchronization task, outsourced expense synchronization task, and outsourced rate synchronization task. After the net asset value synchronization task, outsourced scale synchronization task, and lifecycle synchronization task have all successfully executed, the outsourced scale fixation task will be executed. The outsourced scale fixation task thread will wait until the net asset value synchronization task, outsourced scale synchronization task, and lifecycle synchronization task have successfully executed.

[0035] The task type refers to the target subtask that needs to be processed currently. It can be net asset value synchronization, outsourcing scale synchronization, outsourcing cost synchronization, outsourcing rate synchronization, lifecycle synchronization, outsourcing scale solidification processing, forced rerun, execution of all subtasks, or no processing. Among them, forced rerun is a key function for executing target subtasks for data repair and consistency assurance. By forcing a rerun, the cache, historical result verification and other mechanisms can be bypassed, so that all tasks can be fully re-executed. Among them, no processing means not executing any target subtask, and no processing means empty. Executing all subtasks means executing all target subtasks.

[0036] You can enter multiple product numbers in the execution parameters. If the product number in the execution parameters is not empty, only the project corresponding to the product number will be executed, and tasks for other products will be ignored.

[0037] The data date in the execution parameter corresponds to the date of the target scheduled task batch data.

[0038] For example, when the execution parameters are not set, the default execution parameters are 0&empty&empty&empty. At this time, the default serial mode is used to execute the target scheduled tasks, and the net asset value synchronization task, outsourcing scale synchronization task, outsourcing expense synchronization task, outsourcing rate synchronization task, life cycle synchronization task and outsourcing scale solidification synchronization task are executed in sequence.

[0039] In some embodiments, executing a target subtask in the target scheduled task based on a target execution strategy corresponding to the execution parameter includes: Based on task processing instructions, obtain product account information in the business outsourcing system; Based on the product account information, a query interface is called to obtain corresponding outsourcing data; the query interface encapsulates a query command, and the query command is used to obtain the outsourcing data including: net asset value, outsourcing scale, outsourcing fee, outsourcing rate, life cycle and outsourcing scale solidification data; The target subtask in the target scheduled task is executed based on the target execution strategy corresponding to the execution parameter, so as to synchronize the outsourcing data corresponding to the target subtask from the business outsourcing system to the asset business management system.

[0040] In this application, after receiving a task processing instruction from the distributed task scheduling platform, the asset business management system first determines the product account information in the business outsourcing system and stores it in the asset business management system database for use when executing subsequent target subtasks. It then synchronizes the outsourced data based on the existing product account information.

[0041] It should be noted that each target subtask in this application has a corresponding query interface, which encapsulates query commands for obtaining the outsourcing data, including: net asset value, outsourcing scale, outsourcing expenses, outsourcing rates, life cycle, and solidified outsourcing scale data. Therefore, through the corresponding query interface, it is possible to directly obtain the outsourcing data of the corresponding target subtask in the business outsourcing system without having to obtain the outsourcing data from the business outsourcing system's database. This achieves data isolation of the outsourcing data corresponding to each target subtask, reducing data security risks.

[0042] For example, after receiving a task processing instruction, the business outsourcing system is queried for existing product account information according to the task processing instruction. This information can be retrieved by querying the corresponding records based on the product account information, or by calling an internal service interface provided by the business outsourcing system. After obtaining the product account information, it can be passed as a parameter to a query interface. The query interface can be a Representational State Transfer (RESTful) interface, which may send the product account information to a specified Uniform Resource Locator (URL) address via the Hypertext Transfer Protocol (HTTP). The interface constructs a query command based on the passed parameters, such as a Structured Query Language (SQL) query statement, to retrieve and return relevant outsourcing data, such as net asset value and outsourcing scale, from the database. The target subtask within the target scheduled task is executed using the set execution parameters and the target execution strategy, thereby synchronizing the relevant outsourcing data in the business outsourcing system with the asset business management system.

[0043] In some embodiments, executing the target subtask in the target scheduled task based on the target execution strategy corresponding to the execution parameter includes: Determine whether the task type is lifecycle synchronization; In response to the task type being lifecycle synchronization, acquiring lifecycle data; Determine whether there are records of synchronization failures in the net asset value, outsourcing scale, and life cycle data, and whether any of them have data changes. If not, solidify the outsourcing scale.

[0044] Specifically, when executing the target subtask in the target scheduled task based on the target execution strategy corresponding to the execution parameter, such as Figure 2 As shown, first determine whether the target subtask to be executed is of the lifecycle synchronization type. The specific judgment method can be determined by reading the identification field of the task type, which is not limited in this application. It should be noted that if the current task type is already lifecycle synchronization, it means that other target subtasks have been synchronized and completed. At this time, only lifecycle synchronization and outsourcing scale solidification are required. Therefore, if the task type is lifecycle synchronization, the lifecycle data is obtained from the business outsourcing system. Then determine whether there are records of synchronization failures in the net asset value, outsourcing scale and lifecycle data and whether there are data changes in any of them. If not, it means that the outsourcing data synchronization of the above-mentioned target subtasks is successful. The next step is to perform outsourcing scale solidification. After the outsourcing scale solidification process, the outsourcing data synchronization process ends.

[0045] In some embodiments, executing the target subtask in the target scheduled task based on the target execution strategy corresponding to the execution parameter further includes: In response to the task type not being lifecycle synchronization, determining whether the execution mode type is a parallel mode; In response to the execution mode type being the parallel mode, simultaneously executing the net asset value synchronization, the outsourcing scale synchronization, the outsourcing expense synchronization, and the outsourcing rate synchronization in a multi-threaded manner; In response to the execution mode type being the serial mode, determining whether the task type is any one of net asset value synchronization, forced rerun, or no processing; If the task type is any one of NAV synchronization, forced rerun, or not processing, then determine whether the task type is not processing and the execution parameter is set with a product account, and if the task type is not processing and the execution parameter is set with a product account, set the target subtask corresponding to the product account to not processing; After the task type is not "not processed" and the "not executed" parameter is set to a product account or the target subtask corresponding to the product account is set to "not processed", determining whether the task type is net asset value synchronization; In response to the task type being net asset value synchronization, setting the net asset value synchronization record status to unprocessed, and if the product account does not exist, setting the record of the product account to unprocessed; In response to the task type not being a net asset value synchronization or setting the net asset value synchronization record status to unprocessed, and if the product account does not exist, setting the record of the product account to unprocessed, synchronizing the net asset value; After the NAV is synchronized, determine whether there are any projects that have not been synchronized with the outsourcing rate; In response to the existence of a project for which outsourcing rate synchronization has not been performed, performing outsourcing rate synchronization on the project for which outsourcing rate synchronization has not been performed; Perform lifecycle synchronization; Determine whether there are records of synchronization failures in the net asset value, outsourcing scale, and life cycle data, and whether any of them have data changes. If not, solidify the outsourcing scale.

[0046] As an embodiment, if the task type is not lifecycle synchronization, it is determined whether the execution mode type of the execution parameter is parallel mode. Figure 3As shown, if it is a parallel mode, the net asset value synchronization, outsourcing scale synchronization, outsourcing cost synchronization and outsourcing rate synchronization are executed simultaneously in a multi-threaded manner. Specifically, the first thread can synchronize the net asset value for products that have not been synchronized with the net asset value, and record the success of the net asset value synchronization. It is judged whether the outsourcing scale synchronization is successful. If successful, the life cycle is synchronized, and then the outsourcing scale is solidified. The second thread can synchronize the outsourcing scale for products that have not been synchronized with the outsourcing scale, record the success of the outsourcing scale synchronization, and synchronize the life cycle after determining that the outsourcing scale synchronization is successful, and then solidify the outsourcing scale. The third thread can synchronize the outsourcing costs for products that have not been synchronized with the outsourcing costs. The fourth thread is to synchronize the outsourcing rates for products that have not been synchronized with the outsourcing rates.

[0047] If the execution mode type is serial mode, determine whether the task type is any of the following: NAV synchronization, forced rerun, or no processing. Figure 4 If so, the task type is determined to be "Not Processed" and the execution parameter contains a product account. If so, the target subtask corresponding to the product account is set to "Not Processed." If the task type is not "Not Processed" and a product account is present, or if the target subtask corresponding to the product account is set to "Not Processed," the task type is determined to be "Net Asset Value Synchronization." If the task type is "Net Asset Value Synchronization," the Net Asset Value synchronization record status is set to "Not Processed," and if there is no product account, the product account record is set to "Not Processed." If the task type is not "Net Asset Value Synchronization," or if the Net Asset Value synchronization record status is set to "Not Processed," and if the product account does not exist, the product account record is set to "Not Processed," and then the Net Asset Value is synchronized. After the Net Asset Value synchronization, it is determined whether there are any projects for which outsourcing rates have not been synchronized. If there are projects that have not undergone outsourcing rate synchronization, then outsourcing rate synchronization will be performed on the projects that have not undergone outsourcing rate synchronization, and then lifecycle synchronization will be performed; finally, determine whether there are records of synchronization failures in the net asset value, outsourcing scale and lifecycle data and whether any of them have data changes. If not, and any target sub-project has data changes, then the outsourcing scale will be solidified.

[0048] In some embodiments, in response to the task type not being any one of net asset value synchronization, forced rerun, or no processing, determining whether the task type is outsourced scale synchronization; In response to the task type not being any one of net asset value synchronization, forced rerun, or no processing, determining whether the task type is outsourced scale synchronization; In response to the task type being outsourced scale synchronization, setting the outsourced scale synchronization record to unprocessed and the corresponding product number to unprocessed, and performing outsourced scale synchronization; In response to the task type not being outsourcing scale synchronization, determining whether the task type is outsourcing cost synchronization; In response to the task type being outsourcing expense synchronization, setting the outsourcing expense synchronization record to unprocessed and the corresponding product number to unprocessed, and performing outsourcing expense synchronization; In response to the task type not being outsourced expense synchronization, determining whether the task type is outsourced rate synchronization; In response to the task type being outsourcing rate synchronization, setting the outsourcing rate synchronization record to unprocessed and the corresponding product number to unprocessed, and executing the outsourcing rate synchronization; In response to the task type not being outsourcing rate synchronization, determining whether the task type is outsourcing scale solidification processing; In response to the task type being outsourcing scale solidification processing, outsourcing scale solidification is performed.

[0049] In one embodiment, if Figure 5 As shown, if the task type is not Net Asset Value Synchronization, Forced Rerun, or No Processing, determine whether the task type is Outsourced Scale Synchronization. If so, set the Outsourced Scale Synchronization Record to Unprocessed and the corresponding Product Number to Unprocessed, and then perform Outsourced Scale Synchronization. If the task type is not Outsourced Scale Synchronization, determine whether the task type is Outsourced Expense Synchronization. If the task type is Outsourced Expense Synchronization, set the Outsourced Expense Synchronization Record to Unprocessed and the corresponding Product Number to Unprocessed, and then perform Outsourced Expense Synchronization. If the task type is not Outsourced Expense Synchronization, determine whether the task type is Outsourced Rate Synchronization. If the task type is Outsourced Rate Synchronization, set the Outsourced Rate Synchronization Record to Unprocessed and the corresponding Product Number to Unprocessed, and then perform Outsourced Rate Synchronization. If the task type is not Outsourced Rate Synchronization, determine whether the task type is Outsourced Scale Solidification. If the task type is Outsourced Scale Solidification, perform Outsourced Scale Solidification.

[0050] In some embodiments, in response to the task type not being lifecycle synchronization, the method further includes: Determine whether the product account information for the day is synchronized successfully; In response to the successful synchronization of the product account information for the day, determining whether the task type is a forced rerun; In response to the failure to synchronize the product account information on that day or the task type being forced re-run, the synchronized product account information is deleted, the product account information is obtained from the business outsourcing system, and the outsourcing data corresponding to the product account information is obtained.

[0051] This application determines that the task type is not life cycle protection, such as Figure 2As shown, first determine whether the product account information for the day has been successfully synchronized. If so, determine whether the task type is a forced rerun. If the task type is a forced rerun, or if the product account information for the day has not been successfully synchronized, obtain the product account information from the business outsourcing system, as well as the corresponding outsourced data for the product account information.

[0052] In some embodiments, if there is a data anomaly during the execution of a target subtask, an alarm is issued; the target subtask is any one of all target subtasks.

[0053] For example, product account information is obtained from the business outsourcing system and stored in the database of the asset business management system. If any anomalies are detected in the product account information, an alarm is issued. This alarm may be displayed on the electronic device's display interface, stating "Synchronized product account information data is abnormal. Please address it promptly." Alternatively, after the net asset value is synchronized, if the net asset value data is abnormal, an alarm may be issued. This alarm may be displayed on the electronic device's display interface, stating "Synchronized net asset value data is abnormal. Please address it promptly." Alternatively, after the outsourcing scale is synchronized, if the outsourcing scale data is abnormal, an alarm may be issued. This alarm may be displayed on the electronic device's display interface, stating "Synchronized outsourcing scale data is abnormal. Please address it promptly." Alternatively, after the outsourcing cost is synchronized, if the outsourcing cost data is abnormal, an alarm may be issued. This alarm may be displayed on the electronic device's display interface, stating "Synchronized outsourcing cost data is abnormal. Please address it promptly." Alternatively, after the outsourcing rate is synchronized, if the outsourcing rate data is abnormal, an alarm may be issued. This alarm may be displayed on the electronic device's display interface, stating "Synchronized outsourcing rate data is abnormal. Please address it promptly." Alternatively, after the lifecycle is synchronized, if the lifecycle data is abnormal, an alarm is issued. The alarm may be displayed on the display interface of the electronic device, indicating that "the synchronized lifecycle data is abnormal, please handle it in time."

[0054] like Figure 6 As shown, the present application provides a task processing device, comprising: Splitting module 601, used to split the original outsourced scheduled task into multiple subtasks; The encapsulation module 602 is used to filter target subtasks from the plurality of subtasks and encapsulate them to obtain target scheduled tasks; the target scheduled tasks are used to synchronize outsourced data from the business outsourcing system to the asset business management system. The target subtasks include a net asset value synchronization task, an outsourcing scale synchronization task, an outsourcing expense synchronization task, an outsourcing rate synchronization task, a lifecycle synchronization task, and an outsourcing scale solidification task. The execution module 603 is configured to execute the target subtask in the target scheduled task based on the target execution strategy corresponding to the execution parameters in response to receiving the task processing instruction; the task processing instruction is sent by the distributed task scheduling platform.

[0055] The present application provides a task processing device, in which a splitting module 601 splits an original outsourced scheduled task to obtain multiple subtasks; an encapsulation module 602 screens target subtasks from the multiple subtasks and encapsulates them to obtain a target scheduled task; the target scheduled task is used to synchronize outsourced data from a business outsourcing system to an asset business management system, and the target subtasks include a net asset value synchronization task, an outsourced scale synchronization task, an outsourced expense synchronization task, an outsourced rate synchronization task, a life cycle synchronization task and an outsourced scale solidification; the execution module 603 executes the target subtask in the target scheduled task based on the target execution strategy corresponding to the execution parameter in response to receiving a task processing instruction; the task processing instruction is sent by a distributed task scheduling platform.

[0056] It should be noted that the task processing device of the embodiment of the present application solves the problem in a similar principle to the aforementioned task processing method. Therefore, the implementation process, implementation principle, and beneficial effects of the task processing device can all be referred to the description of the implementation process, implementation principle, and beneficial effects of the aforementioned method, and the repetitive parts will not be repeated.

[0057] An embodiment of the present application provides an electronic device, including: 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 enable the at least one processor to execute the method described in any of the above embodiments.

[0058] An embodiment of the present application provides a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable a computer to execute the method described in any of the above embodiments.

[0059] According to an embodiment of the present application, the present application also provides an electronic device and a readable storage medium.

[0060] Figure 7 A schematic block diagram of an example electronic device 800 that can be used to implement an embodiment of the present application is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or claimed herein.

[0061] like Figure 7 As shown, device 800 includes a computing unit 801, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 802 or a computer program loaded from a storage unit 808 into a random access memory (RAM) 803. RAM 803 may also store various programs and data required for the operation of device 800. Computing unit 801, ROM 802, and RAM 803 are interconnected via a bus 804. An input / output (I / O) interface 805 is also connected to bus 804.

[0062] Various components in device 800 are connected to I / O interface 805, including an input unit 806, such as a keyboard, mouse, etc.; an output unit 807, such as various types of displays, speakers, etc.; a storage unit 808, such as a magnetic disk, optical disk, etc.; and a communication unit 809, such as a network card, modem, wireless communication transceiver, etc. The communication unit 809 allows device 800 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0063] The computing unit 801 can be any general-purpose and / or specialized processing component with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various specialized artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 801 performs the various methods and processes described above, such as the task processing method. For example, in some embodiments, the task processing method may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as the storage unit 808. In some embodiments, part or all of the computer program may be loaded and / or installed onto the device 800 via the ROM 802 and / or the communication unit 809. When the computer program is loaded into the RAM 803 and executed by the computing unit 801, one or more steps of the task processing method described above may be performed. Alternatively, in other embodiments, the computing unit 801 may be configured to perform the task processing method via any other suitable means (e.g., via firmware).

[0064] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on a chip (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0065] The program code for implementing the methods of the present application can be written in any combination of one or more programming languages. Such program code can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the program code is executed by the processor or controller, the functions / operations specified in the flow charts and / or block diagrams are implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0066] In the context of this application, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or apparatus. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of machine-readable storage media may include an electrical connection based on one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fibers, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0067] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0068] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), and the Internet.

[0069] A computer system may include a client and a server. The client and server are generally remote from each other and typically interact through a communication network. The client-server relationship arises through computer programs running on the respective computers and having a client-server relationship with each other. The server may be a cloud server, a server in a distributed system, or a server integrated with a blockchain.

[0070] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this disclosure can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of this application can be achieved. This is not limited herein.

[0071] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features being referred to. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. Throughout the description of this application, "plurality" means two or more, unless otherwise specifically defined.

[0072] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A task processing method, characterized in that: include: Split the original outsourced scheduled task into multiple subtasks; Filtering target subtasks from the plurality of subtasks and encapsulating them to obtain a target scheduled task; The target scheduled task is used to synchronize outsourcing data from the business outsourcing system to the asset business management system. The target subtasks include net asset value synchronization task, outsourcing scale synchronization task, outsourcing cost synchronization task, outsourcing rate synchronization task, life cycle synchronization task and outsourcing scale solidification; In response to receiving a task processing instruction, a target subtask in the target scheduled task is executed based on a target execution strategy corresponding to the execution parameters; the task processing instruction is sent by a distributed task scheduling platform.

2. The method according to claim 1, characterized in that After receiving the task processing instruction, the method further includes: setting execution parameters, wherein the execution parameters include execution mode type, task type, product number and data date; wherein, The execution mode types include serial mode and parallel mode; The task types include net asset value synchronization, outsourcing scale synchronization, outsourcing cost synchronization, outsourcing rate synchronization, lifecycle synchronization, outsourcing scale solidification processing, forced re-run, execution of all subtasks, and no processing; The product number is the number of the product corresponding to the target scheduled task; The data date is the date corresponding to the data processed by the corresponding task.

3. The method according to claim 2, characterized in that Executing a target subtask in the target scheduled task based on a target execution strategy corresponding to the execution parameter includes: Based on task processing instructions, obtain product account information in the business outsourcing system; Based on the product account information, a query interface is called to obtain corresponding outsourcing data; the query interface encapsulates a query command, and the query command is used to obtain the outsourcing data including: net asset value, outsourcing scale, outsourcing fee, outsourcing rate, life cycle and outsourcing scale solidification data; The target subtask in the target scheduled task is executed based on the target execution strategy corresponding to the execution parameter, so as to synchronize the outsourcing data corresponding to the target subtask from the business outsourcing system to the asset business management system.

4. The method according to claim 3, characterized in that The executing of the target subtask in the target scheduled task based on the target execution strategy corresponding to the execution parameter includes: Determine whether the task type is lifecycle synchronization; In response to the task type being lifecycle synchronization, performing lifecycle synchronization; Determine whether there are records of synchronization failures in the net asset value, outsourcing scale, and life cycle data, and whether any of them have data changes. If not, solidify the outsourcing scale.

5. The method according to claim 4, characterized in that The target execution strategy corresponding to the execution parameter is used to execute the target subtask in the target scheduled task, further comprising: In response to the task type not being lifecycle synchronization, determining whether the execution mode type is a parallel mode; In response to the execution mode type being the parallel mode, simultaneously executing the data synchronization of the net asset value, the outsourcing scale, the outsourcing expense, and the outsourcing rate in a multi-threaded manner; In response to the execution mode type being the serial mode, determining whether the task type is any one of net asset value synchronization, forced rerun, or no processing; If the task type is any one of NAV synchronization, forced rerun, or not processing, then determine whether the task type is not processing and the execution parameter is set with a product account, and if the task type is not processing and the execution parameter is set with a product account, set the target subtask corresponding to the product account to not processing; After the task type is not "not processed" and the execution parameter is set to a product account or the target subtask corresponding to the product account is set to "not processed", determining whether the task type is net asset value synchronization; In response to the task type being net asset value synchronization, setting the net asset value synchronization record status to unprocessed, and if the execution parameter sets a product account, setting the record of the product account to unprocessed; In response to the task type not being a net asset value synchronization or setting the net asset value synchronization record status to unprocessed, and if the product account does not exist, setting the record of the product account to unprocessed, synchronizing the net asset value; After the NAV is synchronized, determine whether there are any projects that have not been synchronized with the outsourcing rate; In response to the existence of a project for which outsourcing rate synchronization has not been performed, performing outsourcing rate synchronization on the project for which outsourcing rate synchronization has not been performed; Perform lifecycle synchronization; Determine whether there are records of synchronization failures in the net asset value, outsourcing scale, and life cycle data, and whether any of them have data changes. If not, solidify the outsourcing scale.

6. The method according to claim 5, characterized in that In response to the task type not being any one of net asset value synchronization, forced rerun, or no processing, determining whether the task type is outsourced scale synchronization; In response to the task type being outsourced scale synchronization, setting the outsourced scale synchronization record to unprocessed and the corresponding product number to unprocessed, and performing outsourced scale synchronization; In response to the task type not being outsourcing scale synchronization, determining whether the task type is outsourcing cost synchronization; In response to the task type being outsourcing expense synchronization, setting the outsourcing expense synchronization record to unprocessed and the corresponding product number to unprocessed, and performing outsourcing expense synchronization; In response to the task type not being outsourced expense synchronization, determining whether the task type is outsourced rate synchronization; In response to the task type being outsourcing rate synchronization, setting the outsourcing rate synchronization record to unprocessed and the corresponding product number to unprocessed, and performing outsourcing rate synchronization; In response to the task type not being outsourcing rate synchronization, determining whether the task type is outsourcing scale solidification processing; In response to the task type being outsourcing scale solidification processing, outsourcing scale solidification is performed.

7. The method according to claim 5, characterized in that In response to the task type not being lifecycle synchronization, the method further includes: Determine whether the product account information for the day is synchronized successfully; In response to the successful synchronization of the product account information for the day, determining whether the task type is a forced rerun; In response to the failure to synchronize the product account information on that day or the task type being forced re-run, the synchronized product account information is deleted, the product account information is obtained from the business outsourcing system, and the outsourcing data corresponding to the product account information is obtained.

8. The method according to claim 1, characterized in that If there is a data anomaly during the execution of the target subtask, an alarm is issued; the target subtask is any one of all the target subtasks.

9. A task processing device, characterized in that: include: Splitting module, used to split the original outsourced scheduled task into multiple subtasks; An encapsulation module, configured to filter target subtasks from the plurality of subtasks and encapsulate them to obtain a target scheduled task; The target scheduled task is used to synchronize outsourcing data from the business outsourcing system to the asset business management system. The target subtasks include net asset value synchronization task, outsourcing scale synchronization task, outsourcing cost synchronization task, outsourcing rate synchronization task, life cycle synchronization task and outsourcing scale solidification; The execution module is used to execute the target subtask in the target scheduled task based on the target execution strategy corresponding to the execution parameters in response to receiving the task processing instruction; the task processing instruction is sent by the distributed task scheduling platform.

10. An electronic device, characterized in that: include: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 8.

Images