Business processing method, device and equipment and computer readable medium

Abstract

The invention discloses a business processing method, device and equipment and a computer readable medium, and relates to the technical field of big data. A specific embodiment of the method comprises the following steps: dividing a payment service into multiple types of sub-tasks according to a service execution sequence and a service identifier in a service execution message, and determining a sub-service period based on priorities of the sub-tasks and a service period of the payment service; identifying the sub-task and the sub-service period of the sub-task in a batch processing framework, monitoring the service processing sub-task by adopting an interface, and determining that the service processing sub-task in the service label information returned by the interface meets the execution condition of the sub-task, if yes, triggering to execute the sub-task and the batch processing framework to record a log of the sub-task; and identifying the processing state based on the log, and determining the next sub-task according to the processing state and the processing condition corresponding to the processing state so as to execute the next sub-task. According to the embodiment, processing of the service data can be responded in time, and the waiting time is shortened.

Description

Technical Field

[0001] The present invention relates to the field of big data technology, and in particular to a business processing method, device, equipment and computer-readable medium. Background Art

[0002] With the rapid development of the Internet, the number of network users has exploded, and the amount of data in various application systems has increased dramatically. Massive data places higher demands on the efficiency of processing programs, and the processing method based on single-instance database and single-node application deployment can no longer meet the needs.

[0003] In the process of implementing the present invention, the inventors found that there are at least the following problems in the prior art: due to the huge amount of data to be processed, it is impossible to respond to the processing of business data in a timely manner, and a long waiting time is required. Summary of the invention

[0004] In view of this, the embodiments of the present invention provide a method, apparatus, device and computer-readable medium for business processing, which can respond to the processing of business data in a timely manner and shorten the waiting time.

[0005] To achieve the above object, according to one aspect of an embodiment of the present invention, a service processing method is provided, including:

[0006] Divide the payment service into multiple subtasks according to the service execution sequence and the service identifier in the service execution message, and determine the sub-service cycle of the subtask based on the priority of the subtask and the service cycle of the payment service;

[0007] Identify the subtask and the sub-business cycle of the subtask in a batch processing framework, use an interface to monitor the business processing subtasks of multiple users in the subtask, determine that the business processing subtasks of multiple users in the subtask in the business tag information returned by the interface meet the execution condition of the subtask, then trigger the execution of the subtask in the sub-business cycle of the subtask and the batch processing framework to record the log of the subtask;

[0008] After the sub-business cycle ends, the processing status of the subtask is identified based on the log of the batch processing framework, and the next subtask of the business processing subtask for multiple users in the subtask is determined according to the processing status of the subtask and the processing conditions corresponding to the processing status, so as to execute the next subtask of the business processing subtask for multiple users.

[0009] The method of dividing the payment service into multiple subtasks according to the service execution sequence and the service identifier in the service execution message, and determining the sub-service cycle of the subtask based on the priority of the subtask and the service cycle of the payment service includes:

[0010] The payment service is divided into multiple subtasks according to the service execution sequence and the service identifier in the service execution message, and the subtasks include a deduction subtask, a customer identification task, a preferential deduction task, a settlement file acquisition task, a settlement file sending task and a return file receiving task;

[0011] The sub-service cycles of the sub-tasks are determined based on the priorities of the sub-tasks, the interacting parties of the sub-tasks, and the service cycles of the payment services.

[0012] The step of identifying the subtask and the sub-business cycle of the subtask in the batch processing framework, using an interface to monitor the business processing subtasks of multiple users in the subtask, and determining that the business processing subtasks of multiple users in the subtask in the business tag information returned by the interface meet the execution condition of the subtask, triggering the execution of the subtask in the sub-business cycle of the subtask and the batch processing framework recording a log of the subtask, includes:

[0013] Adding a business tag at the interface in the batch processing framework to identify the subtask and the sub-business cycle of the subtask, and using the interface to monitor the business processing subtasks of multiple users in the subtask;

[0014] Receive the business processing subtask execution parameters of multiple users in the subtask, determine that the business processing subtasks of multiple users in the subtask in the business tag information returned by the interface meet the execution conditions of the subtask, then trigger the execution of the subtask in the sub-business cycle of the subtask and the batch processing framework to record the log of the subtask.

[0015] The processing status of the subtask is identified based on the log of the batch processing framework, and the next subtask of the business processing subtask of multiple users in the subtask is determined according to the processing status of the subtask and the processing condition corresponding to the processing status, so as to execute the next subtask of the business processing subtask of multiple users, including:

[0016] Identifying a processing status of the subtask based on a log of the batch processing framework, the processing status including skipping, and a processing condition corresponding to the processing status including a skipping threshold;

[0017] If the processing status of the subtask includes skipping, and the number of skipping times of the subtask is less than or equal to the skipping threshold, it is identified that the next subtask of the business processing subtask of multiple users in the subtask is the next subtask of the current subtask in the business execution sequence, so as to execute the next subtask of the current subtask;

[0018] If the processing status of the subtask includes skipping, the number of skipping times of the subtask is greater than the skipping threshold and the job duration of the subtask is greater than the sub-business cycle of the subtask, then the next subtask of the business processing subtask of multiple users in the subtask is identified as the current subtask in the business execution order, so as to execute the current subtask.

[0019] The processing status of the subtask is identified based on the log of the batch processing framework, and the next subtask of the business processing subtask of multiple users in the subtask is determined according to the processing status of the subtask and the processing condition corresponding to the processing status, so as to execute the next subtask of the business processing subtask of multiple users, including:

[0020] Identifying a processing status of the subtask based on a log of the batch processing framework, wherein the processing status includes a retry, and a processing condition corresponding to the processing status includes a retry threshold;

[0021] If the processing status of the subtask includes retry, the number of retries of the subtask is greater than the retry threshold and the duration of the subtask operation is greater than the sub-business cycle of the subtask, it is identified that the next subtask of the business processing subtask of multiple users in the subtask is the previous subtask of the current subtask in the business execution sequence, so as to execute the previous subtask of the current subtask;

[0022] If the processing status of the subtask includes retry, and the number of retries of the subtask is less than or equal to a retry threshold, it is identified that the next subtask of the business processing subtask of multiple users in the subtask is the current subtask, so as to execute the current subtask.

[0023] The processing status of the subtask is identified based on the log of the batch processing framework, and the next subtask of the business processing subtask of multiple users in the subtask is determined according to the processing status of the subtask and the processing condition corresponding to the processing status, so as to execute the next subtask of the business processing subtask of multiple users, including:

[0024] Identifying a processing status of the subtask based on a log of the batch processing framework, the processing status including restarting, and the processing condition corresponding to the processing status including a restart threshold;

[0025] If the processing status of the subtask includes restarting, the number of restarts of the subtask is greater than the restart threshold and the subtask operation duration is greater than the sub-business cycle of the subtask, it is identified that the next subtask of the business processing subtask of multiple users in the subtask is the previous subtask of the current subtask in the business execution sequence, so as to execute the previous subtask of the current subtask;

[0026] If the processing status of the subtask includes restarting, and the number of restarts of the subtask is less than or equal to a retry threshold, it is identified that the next subtask of the business processing subtasks of multiple users in the subtask is the current subtask, so as to execute the current subtask.

[0027] The current subtask is the last subtask in the execution order of the payment service.

[0028] The next subtask of executing the business processing subtask of multiple users includes:

[0029] The payment service of the current subtask is marked as having completed deduction, and the subtask with the first service execution order of the next payment service is used as the next subtask of the service processing subtasks of the multiple users, so as to execute the next subtask of the service processing subtasks of the multiple users.

[0030] According to a second aspect of an embodiment of the present invention, a service processing device is provided, including:

[0031] A task module, used to divide the payment service into multiple subtasks according to the service execution sequence and the service identifier in the service execution message, and determine the sub-service cycle of the subtask based on the priority of the subtask and the service cycle of the payment service;

[0032] An execution module is used to identify the subtask and the sub-business cycle of the subtask in a batch processing framework, monitor the business processing subtasks of multiple users in the subtask using an interface, and determine that the business processing subtasks of multiple users in the subtask in the business tag information returned by the interface meet the execution condition of the subtask, then trigger the execution of the subtask in the sub-business cycle of the subtask and the batch processing framework to record a log of the subtask;

[0033] The status module is used to identify the processing status of the subtask based on the log of the batch processing framework after the sub-business cycle ends, and determine the next subtask of the business processing subtask of multiple users in the subtask according to the processing status of the subtask and the processing conditions corresponding to the processing status, so as to execute the next subtask of the business processing subtask of multiple users.

[0034] According to a third aspect of an embodiment of the present invention, there is provided an electronic device for service processing, including:

[0035] one or more processors;

[0036] a storage device for storing one or more programs,

[0037] When the one or more programs are executed by the one or more processors, the one or more processors implement the above method.

[0038] According to a fourth aspect of an embodiment of the present invention, there is provided a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the method as described above is implemented.

[0039] According to a fifth aspect of an embodiment of the present invention, a computer program product is provided, including a computer program, and when the program is executed by a processor, the method as described above provided by an embodiment of the present invention is implemented.

[0040] An embodiment of the above invention has the following advantages or beneficial effects: the payment service is divided into multiple subtasks according to the service execution order and the service identifier in the service execution message, and the sub-service cycle of the subtask is determined based on the priority of the subtask and the service cycle of the payment service; the subtask and the sub-service cycle of the subtask are identified in the batch processing framework, and the service processing subtasks of multiple users in the subtask are monitored by an interface, and it is determined that the service processing subtasks of multiple users in the subtask in the service tag information returned by the interface meet the execution conditions of the subtask, then the execution of the subtask in the sub-service cycle of the subtask and the batch processing framework recording of the subtask log are triggered; after the sub-service cycle ends, the processing status of the subtask is identified based on the log of the batch processing framework, and the next subtask of the service processing subtask of multiple users in the subtask is determined according to the processing status of the subtask and the processing conditions corresponding to the processing status, so as to execute the next subtask of the service processing subtask of multiple users. The batch processing framework can process multiple subtasks in parallel, so as to respond to the processing of service data in a timely manner and shorten the waiting time.

[0041] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention.

[0043] Figure 1 is a schematic diagram of the main flow of a method for business processing according to an embodiment of the present invention;

[0044] Figure 2 is a schematic diagram of a process of determining a sub-service cycle of a sub-task based on the priority of the sub-task and the service cycle of the payment service according to an embodiment of the present invention;

[0045] Figure 3 is a schematic flow chart of a service processing subtask for multiple users in an interface monitoring subtask according to an embodiment of the present invention;

[0046] Figure 4is a flowchart of a process in which a processing state is skipping and determining a next subtask according to an embodiment of the present invention;

[0047] Figure 5 is a flowchart of determining the next subtask in a retry state according to an embodiment of the present invention;

[0048] Figure 6 is a flowchart of determining the next subtask for a restart processing state according to an embodiment of the present invention;

[0049] Figure 7 is a schematic diagram of the main structure of a device for service processing according to an embodiment of the present invention;

[0050] Figure 8 is an exemplary system architecture diagram to which embodiments of the present invention may be applied;

[0051] Fig. 9 It is a schematic diagram of the structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present invention. DETAILED DESCRIPTION

[0052] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description. The acquisition, storage, use, and processing of data in the technical solution of this application comply with the relevant provisions of national laws and regulations.

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

[0054] In order to solve the problem of being unable to respond to business data processing in a timely manner and having to wait for a long time, the following technical solution in the embodiment of the present invention can be adopted.

[0055] See also Figure 1 , Figure 1 1 is a schematic diagram of the main flow of a method for processing data according to an embodiment of the present invention, which processes multiple subtasks of a payment service in parallel based on a batch processing framework. Figure 1 As shown in 100, the following steps are specifically included:

[0056] S101. Divide the payment service into multiple subtasks according to the service execution sequence and the service identifier in the service execution message, and determine the sub-service cycle of the subtask based on the priority of the subtask and the service cycle of the payment service.

[0057] In an embodiment of the present invention, the payment of service fees needs to be realized for each user during the payment service process. As an example, the payment service includes communication fees with a service cycle of one month. As another example, the payment service includes electricity fees with a service cycle of one month.

[0058] The payment service can be divided into multiple subtasks according to the service execution sequence and the service identifier in the service execution message, and the sub-service cycle of the subtask is determined based on the priority of the subtask and the service cycle of the payment service. The sum of the sub-service cycles of the subtasks under the payment service is equal to the service cycle of the payment service.

[0059] See also Figure 2 That is 200, Figure 2 The flowchart of determining the sub-service cycle of a sub-task based on the priority of the sub-task and the service cycle of the payment service according to an embodiment of the present invention includes the following steps:

[0060] S201. Divide the payment service into multiple subtasks according to the service execution sequence and the service identifier in the service execution message. The subtasks include a deduction subtask, a customer identification task, a preferential deduction task, a settlement file acquisition task, a settlement file sending task, and a return file receiving task.

[0061] In an embodiment of the present invention, the payment service can be divided into multiple subtasks according to the service execution order and the service identifier in the service execution message. The service execution order is the execution order of the payment service. The service execution message is a message involved in the interaction during the service execution process. The service identifier is extracted from the service execution message. As an example, the service identifier includes a deduction service identifier, a customer marking task identifier, a preferential deduction service identifier, a settlement file acquisition task identifier, a settlement file sending task identifier, and a return file receiving task identifier.

[0062] Among them, the subtasks include deduction subtask, customer identification task, preferential deduction task, settlement file acquisition task, settlement file sending task and return file receiving task.

[0063] Deduction subtask: Count customer information to generate unrecorded customer data. Store customer data in the total customer deduction information table and mark the next deduction date.

[0064] Identify customer tasks: compile a list of customers who need to be deducted. The customer list includes the first-time deduction customer list and the second-time deduction customer list.

[0065] Discount deduction task: Calculate the deduction amount after the customer discount. As an example, select customers who can enjoy the discount through the whitelist.

[0066] Get settlement file task: Get settlement files based on the customer's deduction amount to create a settlement file task.

[0067] Send settlement file task: Send settlement files to implement the Send settlement file task. As an example, use ntfy to send settlement files. ntfy supports running on multiple operating systems, including Linux, macOS, and other operating systems, providing cross-platform compatibility.

[0068] Receive feedback file task: After processing the deduction amount, receive the feedback feedback file. If the customer deduction is successful based on the feedback file, update the customer's next deduction date to the next cycle. If the customer deduction fails, it will be deducted again after the preset days.

[0069] S202: Determine the sub-service cycles of the sub-tasks based on the priorities of the sub-tasks, the interacting parties of the sub-tasks, and the service cycles of the payment services.

[0070] In the embodiment of the present invention, the payment service has a corresponding service cycle, and the sub-service cycles of the sub-tasks can be determined based on the priority of the sub-tasks, the interacting parties of the sub-tasks, and the service cycle of the payment service.

[0071] As an example, the higher the priority of a subtask, the longer the sub-service cycle of the subtask. The more interacting parties a subtask has, the longer the sub-service cycle of the subtask. The sum of the sub-service cycles of the subtasks under the payment service is equal to the service cycle of the payment service.

[0072] exist Figure 2 In the embodiment of the present invention, the payment service is divided into multiple subtasks, each subtask has a corresponding sub-service cycle, and the subtasks can be processed in parallel.

[0073] S102. Identify the subtask and the sub-business cycle of the subtask in the batch processing framework, use the interface to monitor the business processing subtasks of multiple users in the subtask, and determine that the business processing subtasks of multiple users in the subtask in the business tag information returned by the interface meet the execution conditions of the subtask, then trigger the execution of the subtask in the sub-business cycle of the subtask and the batch processing framework to record the log of the subtask.

[0074] In an embodiment of the present invention, batch processing of subtasks is implemented in a batch processing framework. As an example, the batch processing framework includes Spring Batch. The execution status, progress and performance indicators of the subtasks can be monitored through the interface of Spring Batch.

[0075] Specifically, the subtask and the sub-business cycle of the subtask are identified in the batch processing framework. Then, the business processing subtasks of multiple users in the subtask are monitored using an interface, and it is determined that the business processing subtasks of multiple users in the subtask in the business tag information returned by the interface meet the execution conditions of the subtask, which triggers the execution of the subtask in the sub-business cycle of the subtask and the batch processing framework records the log of the subtask.

[0076] See also Figure 3 That is 300, Figure 3 This is a flow chart of a service processing subtask for multiple users in an interface monitoring subtask according to an embodiment of the present invention. Specifically, it includes the following steps:

[0077] S301. Add a business tag at the interface in the batch processing framework to identify the subtask and the sub-business cycle of the subtask, and use the interface to monitor the business processing subtasks of multiple users in the subtask.

[0078] In an embodiment of the present invention, a business label is added at the interface in the batch processing framework to identify the subtask and the sub-business cycle of the subtask. As an example, the interface includes the interface BizSubTask. The business label is added to each subtask through the interface BizSubTask. The interface BizSubTask includes a labelMap method. The labelMap method is used to return business label information. As an example, the labelMap method is used to return a Map containing business label information. In this way, each subtask can have its own business label, which is convenient for monitoring and querying. This is to achieve the use of an interface to monitor the business processing subtasks of multiple users in a subtask.

[0079] S302, receiving business processing subtask execution parameters for multiple users in the subtask, determining that the business processing subtasks for multiple users in the subtask in the business tag information returned by the interface meet the execution conditions of the subtask, then triggering the execution of the subtask in the sub-business cycle of the subtask and the batch processing framework recording the log of the subtask.

[0080] In an embodiment of the present invention, business processing subtask execution parameters of multiple users in a subtask are received. As an example, in Spring Batch, business processing subtask execution parameters of multiple users in a subtask can be received by configuring ChunkProcessorChunkHandler. The distributed subtask (Chunk) can be received through the message channel of Spring Integration, and then business logic processing can be performed.

[0081] After the execution of the business processing subtask execution parameters, the interface returns the business tag information which can be used to determine whether the execution condition of the subtask is met. That is, the business tag information represents the execution result of the business processing subtask execution parameters.

[0082] If the business processing subtasks of multiple users in the subtasks in the business tag information returned by the interface meet the execution conditions of the subtasks, the subtasks are executed in the sub-business cycle of the subtasks and the batch processing framework records the logs of the subtasks. That is, while the execution of the subtasks is triggered, the batch processing framework records the logs of the subtasks to realize the monitoring of the subtasks.

[0083] As an example, the business tag information includes the deduction amount after calculating the customer discount. The execution condition of the subtask includes that the business processing subtasks of all users in the subtask have completed the deduction amount after calculating the customer discount.

[0084] In one embodiment of the present invention, the SubTaskExecutor component is responsible for checking and executing business processing subtasks that meet the execution conditions. The executeSubTasks method periodically checks whether there are subtasks ready to execute and uses TaskScheduler to schedule the subtasks. The executeTask method is responsible for executing specific business logic and handling possible exceptions.

[0085] exist Figure 3 In an embodiment, the business processing subtasks of multiple users in the subtask are monitored through an interface to trigger the execution of the subtask in the sub-business cycle of the subtask and the batch processing framework to record the log of the subtask.

[0086] S103. After the sub-business cycle ends, the processing status of the subtask is identified based on the log of the batch processing framework, and the next subtask of the business processing subtask for multiple users in the subtask is determined according to the processing status of the subtask and the processing conditions corresponding to the processing status, so as to execute the next subtask of the business processing subtask for multiple users.

[0087] In the embodiment of the present invention, after the sub-service cycle ends, the processing status of the sub-task can be determined to ensure the stability and accuracy of the processing status of the sub-task.

[0088] Each subtask has a corresponding processing status, and the processing status of the subtask is stored in the log of the batch processing framework. The next subtask of the business processing subtask of multiple users in the subtask can be determined based on the processing status of the subtask to execute the next subtask of the business processing subtask of multiple users.

[0089] See also Figure 4 That is 400, Figure 4 This is a flowchart of a process in which the processing state is skipping and determining the next subtask according to an embodiment of the present invention. Specifically, the following steps are included:

[0090] S401 , identifying a processing status of a subtask based on a log of a batch processing framework, where the processing status includes skipping, and a processing condition corresponding to the processing status includes a skipping threshold.

[0091] In the embodiment of the present invention, in the processing logic of the subtask, the log of the batch processing framework is used to record the processing status and key steps of the subtask. For example, logs are recorded when the subtask starts processing, when the subtask is processing, and when the subtask ends processing. In this way, the execution status of the subtask can be tracked by viewing the logs. As an example, in AccountTransferProcessor, logger.info is used to record the start, processing, and end status of the subtask.

[0092] In subtask processing, the processing status is identified by capturing and recording exceptions. As an example, the processing status includes skipping, and the processing condition corresponding to the processing status includes a skip threshold. As an example, SkipPolicy is used to skip certain exceptions. You can specify to skip certain exceptions and set the maximum number of skips, i.e., the skip threshold.

[0093] S402, if the processing status of the subtask includes skipping, and the number of skipping times of the subtask is less than or equal to the skipping threshold, then the next subtask of the business processing subtask for multiple users in the identification subtask is the next subtask of the current subtask in the business execution order, so as to execute the next subtask of the current subtask.

[0094] In an embodiment of the present invention, the next subtask of the current subtask may be determined based on the number of times the subtask is skipped.

[0095] If the number of times the subtask is skipped is less than or equal to the skip threshold, it means that the subtask meets the task processing requirements. Then, the next subtask of the business processing subtask for multiple users in the subtask is identified as the next subtask of the current subtask in the business execution order, so that the next subtask of the current subtask is executed.

[0096] S403, if the processing status of the subtask includes skipping, and the number of skipping times of the subtask is greater than the skipping threshold and the subtask job duration is greater than the subtask's sub-business cycle, then the next subtask of the business processing subtask for multiple users in the subtask is identified as the current subtask in the business execution order, so as to execute the current subtask.

[0097] If the number of times a subtask is skipped is greater than the skip threshold and the duration of the subtask operation is greater than the sub-business cycle of the subtask, it means that the subtask does not meet the task processing requirements, the execution of the current subtask fails, and the current subtask needs to be executed again.

[0098] The next subtask of the business processing subtask for multiple users in the identification subtask is the current subtask in the business execution sequence, so as to execute the current subtask.

[0099] exist Figure 4 In the embodiment, when the processing state is skip, the next subtask to be executed can be determined based on the skip threshold and the sub-business cycle of the subtask.

[0100] See also Figure 5 That is 500, Figure 5 The flowchart of the process of determining the next subtask in the retry state according to an embodiment of the present invention is shown in FIG. The process of determining the next subtask in the retry state according to an embodiment of the present invention includes the following steps:

[0101] S501 . The processing status of the log identification subtask based on the batch processing framework, the processing status includes retry, and the processing condition corresponding to the processing status includes a retry threshold.

[0102] In an embodiment of the present invention, in the processing logic of a subtask, the log of a batch processing framework is used to record the processing status and key steps of the subtask. The processing status includes a retry, and the processing condition corresponding to the processing status includes a retry threshold. The retry is used to ensure the stability and reliability of the subtask job. As an example, a retry is performed using RetryPolicy. The retry threshold, retry interval, and error handling strategy can be set.

[0103] S502, if the processing status of the subtask includes retry, the number of retries of the subtask is greater than the retry threshold and the subtask job duration is greater than the subtask's sub-business cycle, then the next subtask of the business processing subtask for multiple users in the subtask is identified as the previous subtask of the current subtask in the business execution order, so as to execute the previous subtask of the current subtask.

[0104] The processing status of a subtask includes retries. If the number of retries of a subtask is greater than the retry threshold and the subtask job duration is greater than the subtask's subbusiness cycle, it means that the subtask does not meet the task processing requirements, the execution of the current subtask fails, and the previous subtask of the current subtask needs to be re-executed.

[0105] The next subtask of the business processing subtask for multiple users in the identification subtask is the previous subtask of the current subtask in the business execution sequence, so as to execute the previous subtask of the current subtask.

[0106] S503: If the processing status of the subtask includes retry, and the number of retries of the subtask is less than or equal to the retry threshold, it is identified that the next subtask of the business processing subtask for multiple users in the subtask is the current subtask, so as to execute the current subtask.

[0107] The processing status of a subtask includes retries. If the number of retries of a subtask is less than or equal to the retry threshold, it means that the subtask does not meet the task processing requirements, the execution of the current subtask fails, and the current subtask needs to be re-executed.

[0108] The next subtask of the business processing subtask of multiple users in the identification subtask is the current subtask, so as to execute the current subtask.

[0109] exist Figure 5 In the embodiment, the processing state includes a retry situation, and the next subtask to be processed is determined based on the number of retries and the retry threshold.

[0110] See also Figure 6 That is 600, Figure 6 This is a flow chart of determining the next subtask for a processing state of restart according to an embodiment of the present invention. Specifically, the following steps are included:

[0111] S601 . The processing status of the log identification subtask based on the batch processing framework, the processing status includes restarting, and the processing condition corresponding to the processing status includes a restart threshold.

[0112] In an embodiment of the present invention, in the processing logic of the subtask, the log of the batch processing framework is used to record the processing status and key steps of the subtask. The processing status includes restarting, and the processing condition corresponding to the processing status includes a restart threshold. The restart number, i.e., the restart threshold, can be limited by setting startLimit.

[0113] S602, if the processing status of the subtask includes restart, the number of restarts of the subtask is greater than the restart threshold and the subtask job duration is greater than the subtask's sub-business cycle, then the next subtask of the business processing subtask for multiple users in the subtask is identified as the previous subtask of the current subtask in the business execution order, so as to execute the previous subtask of the current subtask.

[0114] If the processing status of a subtask includes restart, and the number of restarts of the subtask is greater than the restart threshold and the subtask job duration is greater than the subtask's subbusiness cycle, it means that the subtask does not meet the task processing requirements, and the execution of the current subtask fails. The previous subtask of the current subtask needs to be re-executed.

[0115] The next subtask of the business processing subtask for multiple users in the identification subtask is the previous subtask of the current subtask in the business execution sequence, so as to execute the previous subtask of the current subtask.

[0116] S603: If the processing status of the subtask includes restarting, and the number of restarts of the subtask is less than or equal to the retry threshold, it is identified that the next subtask of the business processing subtask of multiple users in the subtask is the current subtask, so as to execute the current subtask.

[0117] If the processing status of the subtask includes restart, and the number of restarts of the subtask is less than or equal to the retry threshold, it means that the subtask does not meet the task processing requirements, the execution of the current subtask fails, and the current subtask needs to be re-executed.

[0118] The next subtask of the business processing subtask of multiple users in the identification subtask is the current subtask, so as to execute the current subtask.

[0119] exist Figure 6 In the embodiment, the processing status includes a restart situation, and the next processing subtask is determined based on the restart number and the restart threshold.

[0120] In the above embodiment, reliable execution of subtasks is achieved through processing status, ensuring that batch processing can be retried, skipped or restarted when faced with errors and exceptions, thereby improving the reliability of business processing.

[0121] In one embodiment of the present invention, if the current subtask is the last subtask in the service execution sequence of the payment service, then the next payment service may be executed.

[0122] Specifically, the payment service of the current subtask is marked as having completed deduction, and the subtask with the first service execution order of the next payment service is used as the next subtask of the service processing subtasks for multiple users, so as to execute the next subtask of the service processing subtasks for multiple users.

[0123] In the above-mentioned embodiment of the present invention, the payment service is divided into multiple subtasks according to the service execution order and the service identifier in the service execution message, and the sub-service cycle of the subtask is determined based on the priority of the subtask and the service cycle of the payment service; the subtask and the sub-service cycle of the subtask are identified in the batch processing framework, and the service processing subtasks of multiple users in the subtask are monitored by an interface, and it is determined that the service processing subtasks of multiple users in the subtask in the service tag information returned by the interface meet the execution conditions of the subtask, then the execution of the subtask in the sub-service cycle of the subtask and the log of the subtask recorded by the batch processing framework are triggered; after the sub-service cycle ends, the processing status of the subtask is identified based on the log of the batch processing framework, and the next subtask of the service processing subtask of multiple users in the subtask is determined according to the processing status of the subtask and the processing conditions corresponding to the processing status, so as to execute the next subtask of the service processing subtask of multiple users. The batch processing framework can process multiple subtasks in parallel, so as to respond to the processing of service data in a timely manner and shorten the waiting time.

[0124] See also Figure 7 , Figure 7 is a schematic diagram of the main structure of a service processing device according to an embodiment of the present invention. The service processing device can implement a service processing method, such as Figure 7 As shown in 700, the service processing device specifically includes:

[0125] Task module 701, used to divide the payment service into multiple subtasks according to the service execution order and the service identifier in the service execution message, and determine the sub-service cycle of the subtask based on the priority of the subtask and the service cycle of the payment service;

[0126] An execution module 702 is used to identify the subtask and the sub-business cycle of the subtask in the batch processing framework, use an interface to monitor the business processing subtasks of multiple users in the subtask, and determine that the business processing subtasks of multiple users in the subtask in the business tag information returned by the interface meet the execution condition of the subtask, then trigger the execution of the subtask in the sub-business cycle of the subtask and the batch processing framework to record the log of the subtask;

[0127] The status module 703 is used to identify the processing status of the subtask based on the log of the batch processing framework after the sub-business cycle ends, and determine the next subtask of the business processing subtask of multiple users in the subtask according to the processing status of the subtask and the processing conditions corresponding to the processing status, so as to execute the next subtask of the business processing subtask of multiple users.

[0128] In one embodiment of the present invention, the task module 701 is specifically used to divide the payment service into multiple subtasks according to the service execution order and the service identifier in the service execution message, wherein the subtasks include a deduction subtask, a customer identification task, a preferential deduction task, a settlement file acquisition task, a settlement file sending task and a return file receiving task;

[0129] The sub-service cycles of the sub-tasks are determined based on the priorities of the sub-tasks, the interacting parties of the sub-tasks, and the service cycles of the payment services.

[0130] In one embodiment of the present invention, the execution module 702 is specifically used to add a business tag at the interface in the batch processing framework to identify the subtask and the sub-business cycle of the subtask, and use the interface to monitor the business processing subtasks of multiple users in the subtask;

[0131] Receive the business processing subtask execution parameters of multiple users in the subtask, determine that the business processing subtasks of multiple users in the subtask in the business tag information returned by the interface meet the execution conditions of the subtask, then trigger the execution of the subtask in the sub-business cycle of the subtask and the batch processing framework to record the log of the subtask.

[0132] In one embodiment of the present invention, the state module 703 is specifically used to identify the processing state of the subtask based on the log of the batch processing framework, the processing state includes skipping, and the processing condition corresponding to the processing state includes a skipping threshold;

[0133] If the processing status of the subtask includes skipping, and the number of skipping times of the subtask is less than or equal to the skipping threshold, it is identified that the next subtask of the business processing subtask of multiple users in the subtask is the next subtask of the current subtask in the business execution sequence, so as to execute the next subtask of the current subtask;

[0134] If the processing status of the subtask includes skipping, the number of skipping times of the subtask is greater than the skipping threshold and the job duration of the subtask is greater than the sub-business cycle of the subtask, then the next subtask of the business processing subtask of multiple users in the subtask is identified as the current subtask in the business execution order, so as to execute the current subtask.

[0135] In one embodiment of the present invention, the state module 703 is specifically used to identify the processing state of the subtask based on the log of the batch processing framework, the processing state includes retry, and the processing condition corresponding to the processing state includes a retry threshold;

[0136] If the processing status of the subtask includes retry, the number of retries of the subtask is greater than the retry threshold and the duration of the subtask operation is greater than the sub-business cycle of the subtask, it is identified that the next subtask of the business processing subtask of multiple users in the subtask is the previous subtask of the current subtask in the business execution sequence, so as to execute the previous subtask of the current subtask;

[0137] If the processing status of the subtask includes retry, and the number of retries of the subtask is less than or equal to a retry threshold, it is identified that the next subtask of the business processing subtask of multiple users in the subtask is the current subtask, so as to execute the current subtask.

[0138] In one embodiment of the present invention, the state module 703 is specifically used to identify the processing state of the subtask based on the log of the batch processing framework, the processing state includes restarting, and the processing condition corresponding to the processing state includes a restart threshold;

[0139] If the processing status of the subtask includes restarting, the number of restarts of the subtask is greater than the restart threshold and the subtask operation duration is greater than the sub-business cycle of the subtask, it is identified that the next subtask of the business processing subtask of multiple users in the subtask is the previous subtask of the current subtask in the business execution sequence, so as to execute the previous subtask of the current subtask;

[0140] If the processing status of the subtask includes restarting, and the number of restarts of the subtask is less than or equal to a retry threshold, it is identified that the next subtask of the business processing subtasks of multiple users in the subtask is the current subtask, so as to execute the current subtask.

[0141] In one embodiment of the present invention, the status module 703 is specifically used to mark the payment business of the current subtask as having completed deduction when the current subtask is the last subtask in the business execution order of the payment business, and to use the subtask that is first in the business execution order of the next payment business as the next subtask of the business processing subtask of the multiple users, so as to execute the next subtask of the business processing subtask of the multiple users.

[0142] Figure 8 An exemplary system architecture 800 is shown to which the service processing method or service processing apparatus according to the embodiments of the present invention may be applied.

[0143] like Figure 8 As shown, system architecture 800 may include terminal devices 801, 802, 803, a network 804, and a server 805. Network 804 is used to provide a medium for communication links between terminal devices 801, 802, 803 and server 805. Network 804 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0144] Users can use terminal devices 801, 802, and 803 to interact with server 805 through network 804 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 801, 802, and 803, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).

[0145] The terminal devices 801 , 802 , and 803 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0146] The server 805 may be a server that provides various services, such as a backend management server (only an example) that provides support for shopping websites browsed by users using the terminal devices 801, 802, and 803. The backend management server may analyze and process the received data such as product information query requests, and feed back the processing results (such as target push information, product information - only an example) to the terminal device.

[0147] It should be noted that the service processing method provided in the embodiment of the present invention is generally executed by the server 805 , and accordingly, the service processing device is generally set in the server 805 .

[0148] It should be understood that Figure 8 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0149] A computer program product according to an embodiment of the present invention includes a computer program, and when the program is executed by a processor, the business processing method provided by the embodiment of the present invention is implemented.

[0150] Reference below Fig. 9 , which shows a schematic diagram of the structure of a computer system 900 of a terminal device suitable for implementing an embodiment of the present invention. Fig. 9 The terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0151] like Fig. 9 As shown, the computer system 900 includes a central processing unit (CPU) 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage part 908 into a random access memory (RAM) 903. In the RAM 903, various programs and data required for the operation of the system 900 are also stored. The CPU 901, the ROM 902, and the RAM 903 are connected to each other through a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0152] The following components are connected to the I / O interface 905: an input section 906 including a keyboard, a mouse, etc.; an output section 907 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, a modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I / O interface 905 as needed. A removable medium 911, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 910 as needed, so that a computer program read therefrom is installed into the storage section 908 as needed.

[0153] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 909, and / or installed from the removable medium 911. When the computer program is executed by the central processing unit (CPU) 901, the above-mentioned functions defined in the system of the present invention are executed.

[0154] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with 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), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0155] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0156] The modules involved in the embodiments of the present invention may be implemented in software or hardware. The modules described may also be set in a processor. For example, they may be described as: a processor includes a task module, an execution module, and a status module. The names of these modules do not constitute a limitation on the module itself in some cases. For example, the task module may also be described as "used to divide the payment service into multiple categories of subtasks according to the service execution order and the service identifier in the service execution message, and determine the sub-service cycle of the subtask based on the priority of the subtask and the service cycle of the payment service."

[0157] As another aspect, the present invention further provides a computer-readable medium, which may be included in the device described in the above embodiment; or may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device includes:

[0158] Divide the payment service into multiple subtasks according to the service execution sequence and the service identifier in the service execution message, and determine the sub-service cycle of the subtask based on the priority of the subtask and the service cycle of the payment service;

[0159] Identify the subtask and the sub-business cycle of the subtask in a batch processing framework, use an interface to monitor the business processing subtasks of multiple users in the subtask, determine that the business processing subtasks of multiple users in the subtask in the business tag information returned by the interface meet the execution condition of the subtask, then trigger the execution of the subtask in the sub-business cycle of the subtask and the batch processing framework to record the log of the subtask;

[0160] After the sub-business cycle ends, the processing status of the subtask is identified based on the log of the batch processing framework, and the next subtask of the business processing subtask for multiple users in the subtask is determined according to the processing status of the subtask and the processing conditions corresponding to the processing status, so as to execute the next subtask of the business processing subtask for multiple users.

[0161] According to the technical solution of the embodiment of the present invention, the payment service is divided into multiple subtasks according to the service execution order and the service identifier in the service execution message, and the sub-service cycle of the subtask is determined based on the priority of the subtask and the service cycle of the payment service; the subtask and the sub-service cycle of the subtask are identified in the batch processing framework, and the service processing subtasks of multiple users in the subtask are monitored by an interface, and it is determined that the service processing subtasks of multiple users in the subtask in the service tag information returned by the interface meet the execution conditions of the subtask, then the execution of the subtask in the sub-service cycle of the subtask and the log of the subtask recorded by the batch processing framework are triggered; after the sub-service cycle ends, the processing status of the subtask is identified based on the log of the batch processing framework, and the next subtask of the service processing subtask of multiple users in the subtask is determined according to the processing status of the subtask and the processing conditions corresponding to the processing status, so as to execute the next subtask of the service processing subtask of multiple users. The batch processing framework can process multiple subtasks in parallel, so as to respond to the processing of service data in a timely manner and shorten the waiting time.

[0162] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

[0163] It should be noted that in the technical solution of the present invention, the collection, analysis, use, transmission, storage and other aspects of user personal information involved are in compliance with the provisions of relevant laws and regulations, are used for legal and reasonable purposes, are not shared, leaked or sold outside of these legal uses, and are subject to supervision and management by regulatory authorities. Necessary measures should be taken for user personal information to prevent illegal access to such personal information data, ensure that persons who have access to personal information data comply with the provisions of relevant laws and regulations, and ensure the security of user personal information. Once these user personal information data are no longer needed, the risks should be minimized by limiting or even prohibiting data collection and / or deleting data.

[0164] When applicable, including in certain relevant applications, protect user privacy by de-identifying data, such as by removing specific identifiers (e.g., date of birth, etc.) when applicable, controlling the amount or specificity of data stored (e.g., collecting location data at a city level rather than at a specific address level), controlling how data is stored, and / or other de-identification methods.

Claims

1. A business processing method, characterized in that: include: Divide the payment service into multiple subtasks according to the service execution sequence and the service identifier in the service execution message, and determine the sub-service cycle of the subtask based on the priority of the subtask and the service cycle of the payment service; Identify the subtask and the sub-business cycle of the subtask in a batch processing framework, use an interface to monitor the business processing subtasks of multiple users in the subtask, determine that the business processing subtasks of multiple users in the subtask in the business tag information returned by the interface meet the execution condition of the subtask, then trigger the execution of the subtask in the sub-business cycle of the subtask and the batch processing framework to record the log of the subtask; After the sub-business cycle ends, the processing status of the subtask is identified based on the log of the batch processing framework, and the next subtask of the business processing subtask for multiple users in the subtask is determined according to the processing status of the subtask and the processing conditions corresponding to the processing status, so as to execute the next subtask of the business processing subtask for multiple users.

2. The method for business processing according to claim 1, characterized in that: The method of dividing the payment service into multiple subtasks according to the service execution sequence and the service identifier in the service execution message, and determining the sub-service cycle of the subtask based on the priority of the subtask and the service cycle of the payment service includes: The payment service is divided into multiple subtasks according to the service execution sequence and the service identifier in the service execution message, and the subtasks include a deduction subtask, a customer identification task, a preferential deduction task, a settlement file acquisition task, a settlement file sending task and a return file receiving task; The sub-service cycles of the sub-tasks are determined based on the priorities of the sub-tasks, the interacting parties of the sub-tasks, and the service cycles of the payment services.

3. The business processing method according to claim 1, characterized in that: The step of identifying the subtask and the sub-business cycle of the subtask in the batch processing framework, using an interface to monitor the business processing subtasks of multiple users in the subtask, and determining that the business processing subtasks of multiple users in the subtask in the business tag information returned by the interface meet the execution condition of the subtask, triggering the execution of the subtask in the sub-business cycle of the subtask and the batch processing framework recording a log of the subtask, includes: Adding a business tag at the interface in the batch processing framework to identify the subtask and the sub-business cycle of the subtask, and using the interface to monitor the business processing subtasks of multiple users in the subtask; Receive the business processing subtask execution parameters of multiple users in the subtask, determine that the business processing subtasks of multiple users in the subtask in the business tag information returned by the interface meet the execution conditions of the subtask, then trigger the execution of the subtask in the sub-business cycle of the subtask and the batch processing framework to record the log of the subtask.

4. The method for business processing according to claim 1, characterized in that: The processing status of the subtask is identified based on the log of the batch processing framework, and the next subtask of the business processing subtask of multiple users in the subtask is determined according to the processing status of the subtask and the processing condition corresponding to the processing status, so as to execute the next subtask of the business processing subtask of multiple users, including: Identifying a processing status of the subtask based on a log of the batch processing framework, the processing status including skipping, and a processing condition corresponding to the processing status including a skipping threshold; If the processing status of the subtask includes skipping, and the number of skipping times of the subtask is less than or equal to the skipping threshold, it is identified that the next subtask of the business processing subtask of multiple users in the subtask is the next subtask of the current subtask in the business execution sequence, so as to execute the next subtask of the current subtask; If the processing status of the subtask includes skipping, the number of skipping times of the subtask is greater than the skipping threshold and the job duration of the subtask is greater than the sub-business cycle of the subtask, then the next subtask of the business processing subtask of multiple users in the subtask is identified as the current subtask in the business execution order, so as to execute the current subtask.

5. The business processing method according to claim 1, characterized in that: The processing status of the subtask is identified based on the log of the batch processing framework, and the next subtask of the business processing subtask of multiple users in the subtask is determined according to the processing status of the subtask and the processing condition corresponding to the processing status, so as to execute the next subtask of the business processing subtask of multiple users, including: Identifying a processing status of the subtask based on a log of the batch processing framework, wherein the processing status includes a retry, and a processing condition corresponding to the processing status includes a retry threshold; If the processing status of the subtask includes retry, the number of retries of the subtask is greater than the retry threshold and the duration of the subtask operation is greater than the sub-business cycle of the subtask, it is identified that the next subtask of the business processing subtask of multiple users in the subtask is the previous subtask of the current subtask in the business execution sequence, so as to execute the previous subtask of the current subtask; If the processing status of the subtask includes retry, and the number of retries of the subtask is less than or equal to a retry threshold, it is identified that the next subtask of the business processing subtask of multiple users in the subtask is the current subtask, so as to execute the current subtask.

6. The method for business processing according to claim 1, characterized in that: The processing status of the subtask is identified based on the log of the batch processing framework, and the next subtask of the business processing subtask of multiple users in the subtask is determined according to the processing status of the subtask and the processing condition corresponding to the processing status, so as to execute the next subtask of the business processing subtask of multiple users, including: Identifying a processing status of the subtask based on a log of the batch processing framework, the processing status including restarting, and the processing condition corresponding to the processing status including a restart threshold; If the processing status of the subtask includes restarting, the number of restarts of the subtask is greater than the restart threshold and the subtask operation duration is greater than the sub-business cycle of the subtask, it is identified that the next subtask of the business processing subtask of multiple users in the subtask is the previous subtask of the current subtask in the business execution sequence, so as to execute the previous subtask of the current subtask; If the processing status of the subtask includes restarting, and the number of restarts of the subtask is less than or equal to a retry threshold, it is identified that the next subtask of the business processing subtasks of multiple users in the subtask is the current subtask, so as to execute the current subtask.

7. The method for business processing according to any one of claims 1 to 6, characterized in that: The current subtask is the last subtask in the execution order of the payment service. The next subtask of executing the business processing subtask of multiple users includes: The payment service of the current subtask is marked as having completed deduction, and the subtask with the first service execution order of the next payment service is used as the next subtask of the service processing subtasks of the multiple users, so as to execute the next subtask of the service processing subtasks of the multiple users.

8. A device for business processing, characterized in that: include: A task module, used to divide the payment service into multiple subtasks according to the service execution sequence and the service identifier in the service execution message, and determine the sub-service cycle of the subtask based on the priority of the subtask and the service cycle of the payment service; An execution module is used to identify the subtask and the sub-business cycle of the subtask in a batch processing framework, monitor the business processing subtasks of multiple users in the subtask using an interface, and determine that the business processing subtasks of multiple users in the subtask in the business tag information returned by the interface meet the execution condition of the subtask, then trigger the execution of the subtask in the sub-business cycle of the subtask and the batch processing framework to record a log of the subtask; The status module is used to identify the processing status of the subtask based on the log of the batch processing framework after the sub-business cycle ends, and determine the next subtask of the business processing subtask of multiple users in the subtask according to the processing status of the subtask and the processing conditions corresponding to the processing status, so as to execute the next subtask of the business processing subtask of multiple users.

9. An electronic device for business processing, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 7.

10. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

11. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images