Method, apparatus, device and computer readable medium for business processing

Abstract

The application discloses a service 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: dividing a payment service into multiple subtasks according to a service execution sequence and a service identifier in a service execution message, and determining a sub-service period based on a priority of the subtasks and a service period of the payment service; identifying the subtasks and the sub-service period of the subtasks in a batch processing framework, monitoring the service processing subtasks by using an interface, determining whether the service processing subtasks meet execution conditions of the subtasks in service tag information returned by the interface, triggering execution of the subtasks, and recording logs of the subtasks by the batch processing framework; identifying a processing state based on the logs, and determining a next subtask according to the processing state and a processing condition corresponding to the processing state, so as to execute the next subtask. The embodiment can respond to processing of service data in time and shorten a waiting time.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of big data, and in particular to a business processing method, device and equipment and a computer readable medium. BACKGROUND

[0002] With the rapid development of the Internet, the number of network users is growing explosively, and the data volume of each application system is increasing dramatically. Massive data puts higher requirements on the efficiency of processing programs, and the processing mode based on single-instance database single-node application deployment cannot meet the needs.

[0003] In the process of implementing the present application, the inventors have found that at least the following problems exist in the prior art: Due to the huge amount of data to be processed, the processing of business data cannot be responded to in time, and a long waiting time is required. SUMMARY

[0004] Therefore, the embodiments of the present application provide a business processing method, device, equipment and computer readable medium, which can respond to the processing of business data in time and shorten the waiting time.

[0005] To achieve the above object, according to one aspect of the embodiments of the present application, a business processing method is provided, comprising:

[0006] dividing a payment business into multiple sub-tasks according to a business execution sequence and a business identifier in a business execution message, and determining a sub-business cycle of the sub-tasks based on a priority of the sub-tasks and a business cycle of the payment business;

[0007] identifying the sub-tasks and the sub-business cycle of the sub-tasks in a batch processing framework, monitoring business processing sub-tasks of multiple users in the sub-tasks by an interface, determining that the business processing sub-tasks of the multiple users in the sub-tasks in the interface return business tag information satisfy an execution condition of the sub-tasks, triggering execution of the sub-tasks in the sub-business cycle of the sub-tasks, and recording logs of the sub-tasks by the batch processing framework;

[0008] after the sub-business cycle ends, identifying a processing state of the sub-tasks based on the logs of the batch processing framework, and determining a next sub-task of the business processing sub-tasks of the multiple users in the sub-tasks according to the processing state of the sub-tasks and a processing condition corresponding to the processing state, to execute the next sub-task of the business processing sub-tasks of the multiple users.

[0009] the step of dividing the payment business into multiple sub-tasks according to the business execution sequence and the business identifier in the business execution message, and determining the sub-business cycle of the sub-tasks based on the priority of the sub-tasks and the business cycle of the payment business, comprises:

[0010] The payment service is divided into multiple sub-tasks according to the service execution sequence and the service identification in the service execution message, the sub-tasks including a deduction sub-task, a customer identification sub-task, a preferential deduction sub-task, a settlement file obtaining sub-task, a settlement file sending sub-task, and a receiving file sub-task;

[0011] The sub-service period of the sub-task is determined based on the priority of the sub-task, the interactive party of the sub-task, and the service period of the payment service.

[0012] The sub-task and the sub-service period of the sub-task are identified in the batch processing framework, the interface is used to monitor the service processing sub-tasks of multiple users in the sub-task, and the service processing sub-tasks of multiple users in the sub-task in the interface return tag information are determined to meet the execution condition of the sub-task, so as to trigger the execution of the sub-task in the sub-service period of the sub-task and the batch processing framework records the log of the sub-task, including:

[0013] The interface in the batch processing framework is added with a service tag to identify the sub-task and the sub-service period of the sub-task, and the interface is used to monitor the service processing sub-tasks of multiple users in the sub-task;

[0014] The execution parameters of the service processing sub-tasks of multiple users in the sub-task are received, the service processing sub-tasks of multiple users in the sub-task in the interface return tag information are determined to meet the execution condition of the sub-task, so as to trigger the execution of the sub-task in the sub-service period of the sub-task and the batch processing framework records the log of the sub-task.

[0015] The processing state of the sub-task is identified based on the log of the batch processing framework, and the next sub-task of the service processing sub-tasks of multiple users in the sub-task is determined according to the processing state of the sub-task and the processing condition corresponding to the processing state, so as to execute the next sub-task of the service processing sub-tasks of multiple users, including:

[0016] The processing state of the sub-task is identified based on the log of the batch processing framework, and the processing condition corresponding to the processing state includes a skip threshold;

[0017] If the processing state of the sub-task includes skipping, and the number of skips of the sub-task is less than or equal to the skip threshold, the next sub-task of the service processing sub-tasks of multiple users in the sub-task is identified as the next sub-task of the current sub-task in the service execution sequence, so as to execute the next sub-task of the current sub-task;

[0018] If the processing state of the subtask includes skipping, the number of skips of the subtask is greater than a skip threshold, and the subtask job duration is greater than a subbusiness cycle of the subtask, it is identified that a next subtask of the business processing subtask of the plurality of users in the subtask is a current subtask in a business execution sequence, to execute the current subtask.

[0019] The log based on the batch processing framework identifies the processing state of the subtask, and determines a next subtask of the business processing subtask of the plurality of users according to the processing state of the subtask and a processing condition corresponding to the processing state, to execute the next subtask of the business processing subtask of the plurality of users, including:

[0020] The log based on the batch processing framework identifies the processing state of the subtask, and determines a next subtask of the business processing subtask of the plurality of users according to the processing state of the subtask and a processing condition corresponding to the processing state, to execute the next subtask of the business processing subtask of the plurality of users, including:

[0021] If the processing state of the subtask includes retry, the number of retries of the subtask is greater than a retry threshold, and the subtask job duration is greater than a subbusiness cycle of the subtask, it is identified that a next subtask of the business processing subtask of the plurality of users in the subtask is a previous subtask of a current subtask in a business execution sequence, to execute the previous subtask of the current subtask.

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

[0023] The log based on the batch processing framework identifies the processing state of the subtask, and determines a next subtask of the business processing subtask of the plurality of users according to the processing state of the subtask and a processing condition corresponding to the processing state, to execute the next subtask of the business processing subtask of the plurality of users, including:

[0024] The log based on the batch processing framework identifies the processing state of the subtask, and determines a next subtask of the business processing subtask of the plurality of users according to the processing state of the subtask and a processing condition corresponding to the processing state, to execute the next subtask of the business processing subtask of the plurality of users, including:

[0025] If the processing state of the subtask includes restart, the number of restarts of the subtask is greater than a restart threshold, and the subtask job duration is greater than a subbusiness cycle of the subtask, it is identified that a next subtask of the business processing subtask of the plurality of users in the subtask is a previous subtask of a current subtask in a business execution sequence, to execute the previous subtask of the current subtask.

[0026] When the processing state of the subtask includes restart, the number of restarts of the subtask is less than or equal to a retry threshold, and the next subtask of the plurality of user business processing subtasks in the subtask is identified as the current subtask, the current subtask is executed.

[0027] The current subtask is the last subtask in a business execution sequence of the payment business,

[0028] The next subtask of the plurality of user business processing subtasks includes:

[0029] The payment business of the current subtask is identified as completed deduction, and the first subtask in a business execution sequence of the next payment business is taken as the next subtask of the plurality of user business processing subtasks, so as to execute the next subtask of the plurality of user business processing subtasks.

[0030] According to a second aspect of the embodiment of the present application, a device for business processing is provided, including:

[0031] The task module is configured to divide the payment business into a plurality of subtasks according to a business execution sequence and a business identifier in a business execution message, and determine a sub-business period of the subtask based on a priority of the subtask and a business period of the payment business.

[0032] The execution module is configured to identify the subtask and the sub-business period of the subtask in a batch processing framework, monitor a plurality of user business processing subtasks in the subtask by using an interface, determine that the plurality of user business processing subtasks in the subtask meet an execution condition of the subtask in returned business tag information of the interface, and trigger execution of the subtask in the sub-business period of the subtask and record a log of the subtask by the batch processing framework.

[0033] The state module is configured to identify a processing state of the subtask based on the log of the batch processing framework after the sub-business period ends, and determine a next subtask of the plurality of user business processing subtasks in the subtask according to the processing state of the subtask and a processing condition corresponding to the processing state, so as to execute the next subtask of the plurality of user business processing subtasks.

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

[0035] One or more processors;

[0036] A storage device configured to store 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 method described above.

[0038] According to a fourth aspect of the embodiments of the present application, a computer readable medium is provided, having stored thereon a computer program which, when executed by a processor, implements the method as described above.

[0039] According to a fifth aspect of the embodiments of the present application, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the method as described above according to the embodiments of the present application.

[0040] The embodiment of the above-mentioned application has the following advantages or beneficial effects: according to the business execution sequence and the business identification in the business execution message, the payment business is divided into multiple sub-tasks, and based on the priority of the sub-tasks and the business period of the payment business, the sub-business period of the sub-tasks is determined; in the batch processing framework, the sub-tasks and the sub-business period of the sub-tasks are identified, the interface is used to monitor the business processing sub-tasks of multiple users in the sub-tasks, and when the business processing sub-tasks of multiple users in the sub-tasks in the interface return business tag information meet the execution conditions of the sub-tasks, the execution of the sub-tasks in the sub-business period of the sub-tasks is triggered, and the batch processing framework records the log of the sub-tasks; after the sub-business period ends, the processing state of the sub-tasks is identified based on the log of the batch processing framework, and the next sub-task of the business processing sub-tasks of multiple users in the sub-tasks is determined according to the processing state of the sub-tasks and the processing conditions corresponding to the processing state, so as to execute the next sub-task of the business processing sub-tasks of multiple users. Using the batch processing framework can process multiple sub-tasks in parallel, thereby being able to respond to the processing of business data in time and shorten the waiting time.

[0041] The further effects of the above-mentioned non-conventional optional mode will be described in the following combined with the specific embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0042] The accompanying drawings are used to better understand the present application, and do not constitute an improper limitation on the present application. Among them:

[0043] Figure 1 is the main flow diagram of the method of business processing according to the embodiments of the present application;

[0044] Figure 2 is the flow diagram of determining the sub-business period of the sub-tasks based on the priority of the sub-tasks and the business period of the payment business according to the embodiments of the present application;

[0045] Figure 3 is the flow diagram of monitoring the business processing sub-tasks of multiple users in the sub-tasks by using the interface according to the embodiments of the present application;

[0046] Figure 4is a flowchart of determining the next subtask according to the processing state of skip of an embodiment of the present application;

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

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

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

[0050] Figure 8 is an exemplary system architecture diagram to which an embodiment of the present application can be applied;

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

[0052] Exemplary embodiments of the present application are described below with reference to the accompanying drawings, which include various details of the embodiments of the present application to assist in understanding, and should be considered as merely exemplary. Thus, those skilled in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, for the sake of brevity and clarity, descriptions of well-known functions and constructions are omitted herein. In the technical solutions of the present application, the acquisition, storage, use, processing, etc. of data comply with relevant provisions of national laws and regulations.

[0053] It should be noted that in the embodiments of the present application, some industry existing solutions, components, models, etc. may be mentioned, which should be considered as exemplary, and the purpose is only to illustrate the feasibility of the technical solutions of the present application, but it does not mean that the applicant has or will necessarily use the solutions.

[0054] In order to solve the problem that the processing of business data cannot be responded in time and a long time is needed to wait, the following technical solutions in the embodiments of the present application can be used.

[0055] Referring to Figure 1 , Figure 1 is a main flowchart of a method for processing data according to an embodiment of the present application, which parallelly processes a plurality of subtasks of a payment service on the basis of a batch processing framework. As shown in Figure 1 , specifically comprising the following steps:

[0056] S101, divide the payment service into multiple sub-tasks according to the service execution sequence and the service identifier in the service execution message, and determine the sub-service period of the sub-tasks based on the priority of the sub-tasks and the service period of the payment service.

[0057] In the embodiment of the application, the payment service needs to implement the payment of service charges for each user in the process of the payment service. As an example, the payment service includes communication charges with a service period of a month. As another example, the payment service includes power charges with a service period of a month.

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

[0059] Referring to Figure 2 That is, 200, Figure 2 is a flowchart of determining the sub-service period of the sub-tasks based on the priority of the sub-tasks and the service period of the payment service according to the embodiment of the application. Specifically, it includes the following steps:

[0060] S201, divide the payment service into multiple sub-tasks according to the service execution sequence and the service identifier in the service execution message, and the sub-tasks include a charge deduction sub-task, a customer identification task, a preferential charge deduction task, a settlement file acquisition task, a settlement file sending task, and a received disk file receiving task.

[0061] In the embodiment of the application, the payment service can be divided into multiple sub-tasks according to the service execution sequence and the service identifier in the service execution message. The service execution sequence is the execution sequence of the payment service. The service execution message is a message involved in the interaction in the process of executing the service. The service identifier is extracted in the service execution message. As an example, the service identifier includes a charge deduction service identifier, a customer identification task identifier, a preferential charge deduction service identifier, a settlement file acquisition task identifier, a settlement file sending task identifier, and a received disk file receiving task identifier.

[0062] The sub-tasks include a charge deduction sub-task, a customer identification task, a preferential charge deduction task, a settlement file acquisition task, a settlement file sending task, and a received disk file receiving task.

[0063] The charge deduction sub-task: count customer information to generate unrecorded customer data. Store the customer data into a total customer charge information table and identify the next charge deduction date.

[0064] The customer identification task: count the list of customers who need to be charged. The list of customers includes the list of customers who need to be charged for the first time and the list of customers who need to be charged again.

[0065] The preferential deduction task is to calculate the deduction amount of a customer after a discount. As an example, a customer who can enjoy a discount is screened through a whitelist.

[0066] The settlement file acquisition task is to acquire a settlement file based on the deduction amount of a customer to establish a settlement file task.

[0067] The settlement file sending task is to send a settlement file to implement a settlement file sending task. As an example, the settlement file is sent by ntfy. Ntfy supports running on multiple operating systems, including Linux, macOS and other operating systems, providing cross-platform compatibility.

[0068] The feedback file receiving task is to receive a feedback file after processing the deduction amount. Based on the feedback file, it is determined whether the deduction of the customer is successful, and if so, the next deduction date of the customer is updated to the next period. If the deduction of the customer fails, the customer will be deducted again after a preset number of days.

[0069] S202, based on the priority of the subtask, the interaction party of the subtask and the business period of the payment business, respectively determine the sub-business period of the subtask.

[0070] In an embodiment of the present application, the payment business has a corresponding business period. The sub-business period of the subtask can be determined based on the priority of the subtask, the interaction party of the subtask and the business period of the payment business.

[0071] As an example, the higher the priority of the subtask, the longer the sub-business period of the subtask. The more the number of interaction parties of the subtask, the longer the sub-business period of the subtask. The sum of the sub-business periods of the subtasks under the payment business is equal to the business period of the payment business.

[0072] In an embodiment of the present application, the payment business is divided into multiple subtasks, each subtask has a corresponding sub-business period, and the subtasks can be processed in parallel. Figure 2

[0073] S102, identify the subtask and the sub-business period of the subtask in the batch processing framework, monitor the business processing subtask of the multiple users in the subtask through an interface, determine that the business processing subtask of the multiple users in the subtask in the interface returned business tag information satisfies the execution condition of the subtask, and then trigger the execution of the subtask in the sub-business period of the subtask and the batch processing framework records the log of the subtask.

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

[0075] ​Specifically, the subtask and the sub-business period of the subtask are identified in the batch processing framework. Then, the business processing subtasks of the plurality of users in the subtask are monitored by using the interface, and it is determined that the business processing subtasks of the plurality of users in the subtask in the business tag information returned by the interface satisfy the execution condition of the subtask, so as to trigger the execution of the subtask in the sub-business period of the subtask and the batch processing framework records the log of the subtask.

[0076] Referring to Figure 3 That is 300, Figure 3 is a flowchart of monitoring the business processing subtasks of the plurality of users in the subtask by using the interface according to an embodiment of the present application. Specifically, the following steps are included:

[0077] S301, adding a business label at an interface in a batch processing framework to identify a subtask and a sub-business period of the subtask, and monitoring business processing subtasks of a plurality of users in the subtask by using the interface.

[0078] In an embodiment of the present application, a business label is added at an interface in a batch processing framework to identify a subtask and a sub-business period of the subtask. As an example, the interface includes an interface BizSubTask. The business label is added for each subtask through the interface BizSubTask. The interface BizSubTask contains a labelMap method. The labelMap method is used to return business tag information. As an example, the labelMap method is used to return a Map containing business tag information. In this way, each subtask can have its own business label, which is convenient for monitoring and querying. Thus, the business processing subtasks of the plurality of users in the subtask are monitored by using the interface.

[0079] S302, receiving execution parameters of the business processing subtasks of the plurality of users in the subtask, and determining that the business processing subtasks of the plurality of users in the subtask in the business tag information returned by the interface satisfy the execution condition of the subtask, so as to trigger the execution of the subtask in the sub-business period of the subtask and the batch processing framework records the log of the subtask.

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

[0081] After the execution of the execution parameters of the business processing subtask, the business tag information returned by the interface can be used as a judgment whether the execution condition of the subtask is satisfied. That is, the business tag information represents the execution result of the execution parameters of the business processing subtask.

[0082] If the business processing subtasks for multiple users in the business tag information returned by the interface meet the execution conditions of the subtasks, then the execution of the subtasks will be triggered within the sub-business cycle of the subtasks, and the batch processing framework will record the logs of the subtasks. That is, while triggering the execution of the subtasks, the batch processing framework records the logs of the subtasks to monitor the subtasks.

[0083] As an example, the business tag information includes the deduction amount after calculating the customer's discount. The execution condition for the subtask is that all user business processing subtasks within the subtask have completed calculating the deduction amount after the customer's 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 any subtasks are ready to be executed and uses TaskScheduler to schedule the subtasks. The executeTask method is responsible for executing the specific business logic and handling any exceptions that may occur.

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

[0086] S103. After the sub-business cycle ends, the processing status of the subtask is identified by 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 conditions corresponding to the processing status, so as to execute the next subtask of the business processing subtask of multiple users.

[0087] In an embodiment of the present invention, the processing status of a subtask can be determined after the sub-business cycle ends, so as to ensure the stability and accuracy of the processing status of the subtask.

[0088] Each subtask has a corresponding processing status, which is stored in the batch processing framework's log. Based on the processing status of a subtask, the next subtask for multiple users' business processing subtasks can be determined, and the next subtask for multiple users' business processing subtasks can be executed.

[0089] See Figure 4 That is, 400. Figure 4 This is a flowchart illustrating the process of skipping the determination of the next subtask according to an embodiment of the present invention. Specifically, it includes the following steps:

[0090] S401, the processing state of the log identification subtask based on the batch processing framework, the processing state including skipping, the processing condition corresponding to the processing state including a skip threshold.

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

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

[0093] S402, if the processing state of the subtask includes skipping, and the number of skips of the subtask is less than or equal to the skip threshold, the next subtask of the business processing subtask of the plurality of users in the subtask is identified as the next subtask of the current subtask in the business execution sequence, to execute the next subtask of the current subtask.

[0094] In an embodiment of the application, the next subtask of the current subtask can be determined based on the number of skips of the subtask.

[0095] If the number of skips of the subtask is less than or equal to the skip threshold, it means that the subtask meets the task processing requirements, and the next subtask of the business processing subtask of the plurality of users in the subtask is identified as the next subtask of the current subtask in the business execution sequence, to execute the next subtask of the current subtask.

[0096] S403, if the processing state of the subtask includes skipping, and the number of skips of the subtask is greater than the skip threshold and the subtask job duration is greater than the sub-business period of the subtask, the next subtask of the business processing subtask of the plurality of users in the subtask is identified as the current subtask in the business execution sequence, to execute the current subtask.

[0097] If the number of skips of the subtask is greater than the skip threshold and the subtask job duration is greater than the sub-business period of the subtask, it means that the subtask does not meet the task processing requirements, and the execution of the current subtask fails, and the current subtask needs to be re-executed.

[0098] The next subtask of the business processing subtask of the plurality of users in the subtask is identified as the current subtask in the business execution sequence, to execute the current subtask.

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

[0100] Referring to Figure 5 That is, 500, Figure 5 is a flowchart for determining the next subtask when the processing state of the subtask is retry according to the embodiment of the application. Specifically, the method comprises the following steps:

[0101] S501, identifying the processing state of the subtask based on the log of the batch processing framework, the processing state comprising retry, and the processing condition corresponding to the processing state comprising a retry threshold.

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

[0103] S502, when the processing state of the subtask comprises retry, the retry number of the subtask is greater than the retry threshold, and the subtask job duration is greater than the sub-business period of the subtask, identifying that the next subtask of the business processing subtask of the plurality of users in the subtask is the previous subtask of the current subtask in the business execution sequence, to execute the previous subtask of the current subtask.

[0104] When the processing state of the subtask comprises retry, the retry number of the subtask is greater than the retry threshold, and the subtask job duration is greater than the sub-business period of the subtask, it indicates that the subtask does not meet the task processing requirement, and the previous subtask of the current subtask needs to be executed again.

[0105] The next subtask of the business processing subtask of the plurality of users in the subtask is identified as the previous subtask of the current subtask in the business execution sequence, to execute the previous subtask of the current subtask.

[0106] S503, when the processing state of the subtask comprises retry, the retry number of the subtask is less than or equal to the retry threshold, identifying that the next subtask of the business processing subtask of the plurality of users in the subtask is the current subtask, to execute the current subtask.

[0107] When the processing state of the subtask comprises retry, the retry number of the subtask is less than or equal to the retry threshold, it indicates that the subtask does not meet the task processing requirement, and the current subtask needs to be executed again.

[0108] The next subtask of the business processing subtask of the plurality of users in the subtask is identified as a previous subtask of the current subtask in the business execution sequence, so as to execute the previous subtask of the current subtask.

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

[0110] Referring to Figure 6 That is, 600, Figure 6 is a flowchart for determining the next subtask according to the processing state of the embodiment of the application. Specifically, the following steps are included:

[0111] S601, the processing state of the subtask is identified based on the log of the batch processing framework, the processing state includes restart, and the processing condition corresponding to the processing state includes a restart threshold.

[0112] In the embodiment of the application, the processing state and the key steps of the subtask are recorded by using the log of the batch processing framework in the processing logic of the subtask. The processing state includes restart, and the processing condition corresponding to the processing state includes a restart threshold. The number of restarts, i.e., the restart threshold, can be limited by setting startLimit.

[0113] S602, if the processing state of the 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 sub-business period of the subtask, the next subtask of the business processing subtask of the plurality of users in the subtask is identified as a previous subtask of the current subtask in the business execution sequence, so as to execute the previous subtask of the current subtask.

[0114] If the processing state of the 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 sub-business period of the subtask, it indicates that the subtask does not meet the task processing requirements, and the previous subtask of the current subtask needs to be executed again.

[0115] The next subtask of the business processing subtask of the plurality of users in the subtask is identified as a 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 state of the subtask includes restart, and the number of restarts of the subtask is less than or equal to the retry threshold, the next subtask of the business processing subtask of the plurality of users in the subtask is identified as the current subtask, so as to execute the current subtask.

[0117] If the processing state of the subtask includes restart, and the number of restarts of the subtask is less than or equal to the retry threshold, it indicates that the subtask does not meet the task processing requirements, and the current subtask needs to be executed again.

[0118] The next subtask of the plurality of user's business processing subtasks is the current subtask, to execute the current subtask.

[0119] In Figure 6 In an embodiment of the application, the processing state comprises a restart case, and the next processing subtask is determined based on the number of restarts and a restart threshold.

[0120] In the above embodiment, the reliable execution of the subtasks is achieved by the processing state. It is ensured that when facing errors and exceptions, the batch processing can be retried, skipped or restarted, thereby improving the reliability of business processing.

[0121] In an embodiment of the application, the current subtask is the last subtask in the business execution order of the payment business, and the next payment business can be executed.

[0122] Specifically, the payment business of the current subtask is identified as a completed charge, and the first subtask in the business execution order of the next payment business is taken as the next subtask of the plurality of user's business processing subtasks, to execute the next subtask of the plurality of user's business processing subtasks.

[0123] In the above embodiment of the application, the payment business is divided into a plurality of subtasks according to the business execution order and the business identifier in the business execution message, and the sub-business period of the subtask is determined based on the priority of the subtask and the business period of the payment business; the subtask and the sub-business period of the subtask are identified in the batch processing framework, the plurality of user's business processing subtasks in the subtask are monitored by an interface, and it is determined that the plurality of user's business processing subtasks in the subtask meet the execution conditions of the subtask in the business tag information returned by the interface, then the execution of the subtask in the sub-business period of the subtask is triggered, and the log of the subtask is recorded by the batch processing framework; after the end of the sub-business period, the processing state of the subtask is identified based on the log of the batch processing framework, and the next subtask of the plurality of user's business processing subtasks is determined according to the processing state of the subtask and the processing conditions corresponding to the processing state, to execute the next subtask of the plurality of user's business processing subtasks. Using the batch processing framework, a plurality of subtasks can be processed in parallel, and the processing of business data can be responded in time, thereby shortening the waiting time.

[0124] Referring to Figure 7 , Figure 7 is the main structure diagram of the business processing device according to the embodiment of the application, and the business processing device can implement the business processing method, such as Figure 7 As shown in 700, the business processing device specifically comprises:

[0125] The task module 701 is configured to divide the payment service into multiple sub-tasks according to the service execution sequence and the service identifier in the service execution message, and determine a sub-service period of the sub-tasks based on the priority of the sub-tasks and the service period of the payment service.

[0126] The execution module 702 is configured to identify the sub-tasks and the sub-service period of the sub-tasks in a batch processing framework, monitor the service processing sub-tasks of multiple users in the sub-tasks by using an interface, determine that the service processing sub-tasks of the multiple users in the sub-tasks satisfy the execution condition of the sub-tasks in the returned service tag information of the interface, and then trigger execution of the sub-tasks in the sub-service period of the sub-tasks and record logs of the sub-tasks in the batch processing framework.

[0127] The state module 703 is configured to identify the processing state of the sub-tasks based on the logs of the batch processing framework after the sub-service period ends, and determine the next sub-task of the service processing sub-tasks of the multiple users in the sub-tasks according to the processing state of the sub-tasks and the processing condition corresponding to the processing state, so as to execute the next sub-task of the service processing sub-tasks of the multiple users.

[0128] In an embodiment of the present application, the task module 701 is specifically configured to divide the payment service into multiple sub-tasks according to the service execution sequence and the service identifier in the service execution message, and the sub-tasks include a fee deduction sub-task, a client identification sub-task, a preferential fee deduction sub-task, a settlement file acquisition sub-task, a settlement file sending sub-task, and a received disk file receiving sub-task.

[0129] The sub-service period of the sub-tasks is determined based on the priority of the sub-tasks, the interaction party of the sub-tasks, and the service period of the payment service, respectively.

[0130] In an embodiment of the present application, the execution module 702 is specifically configured to add a service tag at an interface in a batch processing framework to identify the sub-tasks and the sub-service period of the sub-tasks, and monitor the service processing sub-tasks of multiple users in the sub-tasks by using the interface.

[0131] The execution module 702 is configured to identify the sub-tasks and the sub-service period of the sub-tasks in a batch processing framework, monitor the service processing sub-tasks of multiple users in the sub-tasks by using an interface, determine that the service processing sub-tasks of the multiple users in the sub-tasks satisfy the execution condition of the sub-tasks in the returned service tag information of the interface, and then trigger execution of the sub-tasks in the sub-service period of the sub-tasks and record logs of the sub-tasks in the batch processing framework.

[0132] In an embodiment of the present application, the state module 703 is specifically configured to identify the processing state of the sub-tasks based on the logs of the batch processing framework, and the processing state includes skipping, and the processing condition corresponding to the processing state includes a skipping threshold.

[0133] the processing state of the subtask comprises skipping, the skipping number of the subtask is less than or equal to a skipping threshold, and the next subtask of the plurality of user business processing subtasks in the subtask is identified as a next subtask of the current subtask in the business execution sequence, to execute the next subtask of the current subtask;

[0134] the processing state of the subtask comprises skipping, the skipping number of the subtask is greater than the skipping threshold, and the subtask job duration is greater than a sub-business cycle of the subtask, the next subtask of the plurality of user business processing subtasks in the subtask is identified as the current subtask in the business execution sequence, to execute the current subtask.

[0135] In an embodiment of the present application, the state module 703 is specifically configured to identify the processing state of the subtask based on a log of the batch processing framework, the processing state comprises retry, and the processing condition corresponding to the processing state comprises a retry threshold;

[0136] the processing state of the subtask comprises retry, the retry number of the subtask is greater than the retry threshold, and the subtask job duration is greater than a sub-business cycle of the subtask, the next subtask of the plurality of user business processing subtasks in the subtask is identified as a previous subtask of the current subtask in the business execution sequence, to execute the previous subtask of the current subtask;

[0137] the processing state of the subtask comprises retry, the retry number of the subtask is less than or equal to the retry threshold, and the next subtask of the plurality of user business processing subtasks in the subtask is identified as the current subtask, to execute the current subtask.

[0138] In an embodiment of the present application, the state module 703 is specifically configured to identify the processing state of the subtask based on a log of the batch processing framework, the processing state comprises restart, and the processing condition corresponding to the processing state comprises a restart threshold;

[0139] the processing state of the subtask comprises restart, the restart number of the subtask is greater than the restart threshold, and the subtask job duration is greater than a sub-business cycle of the subtask, the next subtask of the plurality of user business processing subtasks in the subtask is identified as a previous subtask of the current subtask in the business execution sequence, to execute the previous subtask of the current subtask;

[0140] the processing state of the subtask comprises restart, the restart number of the subtask is less than or equal to the retry threshold, and the next subtask of the plurality of user business processing subtasks in the subtask is identified as the current subtask, to execute the current subtask.

[0141] In an embodiment of the present application, the state module 703 is specifically configured to identify that the current subtask is the last subtask in the service execution sequence of the payment service, identify that the payment service of the current subtask is a completed charge deduction, and set the first subtask in the service execution sequence of the next payment service as the next subtask of the service processing subtasks of the plurality of users, so as to execute the next subtask of the service processing subtasks of the plurality of users.

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

[0143] As shown in Figure 8 , the system architecture 800 can include terminal devices 801, 802, 803, a network 804 and a server 805. The network 804 is a medium for providing a communication link between the terminal devices 801, 802, 803 and the server 805. The network 804 can include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

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

[0145] The terminal devices 801, 802, 803 can be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers and desktop computers, etc.

[0146] The server 805 can be a server providing various services, such as a background management server supporting a shopping website browsed by a user using a terminal device 801, 802, 803 (only as an example). The background management server can analyze and process received product information query requests and other data, and feed back the processing results (such as target push information, product information - only as examples) to the terminal device.

[0147] It should be noted that the method for service processing provided by the embodiments of the present application is generally executed by the server 805, and correspondingly, the apparatus for service processing is generally arranged in the server 805.

[0148] It should be understood that Figure 8 the number of terminal devices, networks and servers in the above description is only illustrative. Any number of terminal devices, networks and servers can be provided according to the needs of implementation.

[0149] A computer program product of an embodiment of the present application includes a computer program which, when executed by a processor, implements the method for service processing provided by the embodiment of the present application.

[0150] Reference will now be made to the following description Figure 9 which shows a structural diagram of a computer system 900 suitable for use in implementing the terminal device of an embodiment of the present application. Figure 9 The terminal device shown is merely an example and should not impose any limitation on the functions and scope of use of the embodiment of the present application.

[0151] As shown in Figure 9 , the computer system 900 includes a central processing unit (CPU) 901 which can perform various appropriate actions and processes in accordance with a program stored in a read only memory (ROM) 902 or a program loaded from a storage section 908 into a random access memory (RAM) 903. Various programs and data required for the operation of the system 900 are also stored in the RAM 903. 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 display such as 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 necessary. A removable media 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is attached to the drive 910 as necessary, so that a computer program read therefrom is installed into the storage section 908 as necessary.

[0153] In particular, the processes described above with reference to the flowcharts can be implemented as a computer software program in accordance with the embodiments disclosed herein. For example, the embodiments disclosed herein include a computer program product comprising a computer program carried on a computer readable medium, the computer program comprising program code for performing the methods illustrated by the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via the communication section 909 and / or installed from the removable media 911. When the computer program is executed by the central processing unit (CPU) 901, the above-described functions defined in the system of the present application are performed.

[0154] It should be noted that the computer-readable medium shown in the present application can 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, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, 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 application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device or component. In the present application, the computer-readable signal medium can include a data signal carried in a baseband or as a part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take various forms, including but not limited to an electromagnetic signal, an optical signal or any suitable combination of the above. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, which can send, propagate or transmit a program for use by or in conjunction with an instruction execution system, device or component. The program code contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0155] The flowcharts and block diagrams in the drawings illustrate the possible implementation architectures, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowcharts or block diagrams can represent a module, a program segment or a part of code containing one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur in different order than that shown in the drawings. For example, two blocks that are shown in succession can actually be executed substantially in parallel, and sometimes in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams or flowcharts, and the combination of blocks in the block diagrams or flowcharts, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0156] The modules described in the embodiments of the present application can be implemented in software or hardware. The modules described can be arranged in a processor, for example, a processor can include a task module, an execution module and a state module. In some cases, the names of the modules do not limit the modules themselves, for example, the task module can also be described as "a module for dividing a payment service into multiple sub-tasks according to a service execution sequence and a service identifier in a service execution message, and determining a sub-service period of the sub-tasks based on a priority of the sub-tasks and a service period of the payment service".

[0157] As another aspect, the present application also provides a computer readable medium, which can be included in the device described in the above embodiments, or can exist independently without being assembled into the device. The computer readable medium carries one or more programs, which, when executed by the device, cause the device to include:

[0158] dividing a payment service into multiple sub-tasks according to a service execution sequence and a service identifier in a service execution message, and determining a sub-service period of the sub-tasks based on a priority of the sub-tasks and a service period of the payment service;

[0159] identifying the sub-tasks and the sub-service periods of the sub-tasks in a batch processing framework, monitoring service processing sub-tasks of multiple users in the sub-tasks by an interface, determining that the service processing sub-tasks of the multiple users in the sub-tasks satisfy an execution condition of the sub-tasks in the returned service tag information of the interface, triggering execution of the sub-tasks in the sub-service periods of the sub-tasks, and recording logs of the sub-tasks by the batch processing framework;

[0160] after the sub-service periods end, identifying processing states of the sub-tasks based on the logs of the batch processing framework, and determining a next sub-task of the service processing sub-tasks of the multiple users in the sub-tasks according to the processing states of the sub-tasks and processing conditions corresponding to the processing states, to execute the next sub-task of the service processing sub-tasks of the multiple users.

[0161] According to the technical scheme of the embodiment of the present application, the payment service is divided into multiple sub-tasks according to the service execution sequence and the service identifier in the service execution message, and the sub-service period of the sub-task is determined based on the priority of the sub-task and the service period of the payment service; the sub-task and the sub-service period of the sub-task are identified in the batch processing framework, the interface is used to monitor the service processing sub-task of multiple users in the sub-task, and when it is determined that the service processing sub-task of multiple users in the sub-task in the return service tag information of the interface meets the execution condition of the sub-task, the execution of the sub-task in the sub-service period of the sub-task is triggered, and the log of the sub-task is recorded by the batch processing framework; after the sub-service period ends, the processing state of the sub-task is identified based on the log of the batch processing framework, and the next sub-task of the service processing sub-task of multiple users is determined according to the processing state of the sub-task and the processing condition corresponding to the processing state, so as to execute the next sub-task of the service processing sub-task of multiple users. The batch processing framework can be used to process multiple sub-tasks in parallel, so as to respond to the processing of service data in time and shorten the waiting time.

[0162] The above detailed description does not constitute a limitation on the protection scope of the present application. Those skilled in the art should understand that various modifications, combinations, sub-combinations and substitutions can occur depending on design requirements and other factors. Any modification, equivalent replacement and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.

[0163] It should be noted that in the technical scheme of the present application, the collection, analysis, use, transmission and storage of user personal information are in line with relevant laws and regulations and are used for legal and reasonable purposes, and are not shared, disclosed or sold outside these legal uses, and are subject to supervision and management by regulatory authorities. Necessary measures should be taken to prevent illegal access to such personal information data and to ensure that personnel with access to personal information data comply with relevant laws and regulations and ensure the security of user personal information. Once these user personal information data are no longer needed, the risk should be minimized by limiting or even prohibiting data collection and / or deleting data.

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

Claims

1. A method for business processing, characterized in that, include: The payment business is divided into multiple sub-tasks based on the business execution order and the business identifier in the business execution message, and the sub-business cycle of the sub-task is determined based on the priority of the sub-task and the business cycle of the payment business. In the batch processing framework, the subtask and the sub-business cycle of the subtask are identified. The interface monitors the business processing subtasks of multiple users in the subtask. If the business tag information returned by the interface shows that the business processing subtasks of multiple users in the subtask meet the execution conditions of the subtask, then the execution of the subtask in the sub-business cycle of the subtask is triggered and the batch processing framework records 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 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 business processing subtask of multiple users. The step of dividing payment transactions into multiple sub-tasks based on the order of business execution and the business identifier in the business execution message, and determining the sub-business cycle of each sub-task based on its priority and the business cycle of the payment transaction, includes: The payment process is divided into multiple sub-tasks based on the order of execution and the business identifier in the execution message. The sub-business cycle of the sub-task is determined based on the priority of the sub-task, the interacting party of the sub-task, and the business cycle of the payment service. The batch processing framework uses logs to identify the processing status of the subtasks, including skipping, and the processing conditions corresponding to the processing status include a skip threshold. The logs based on the batch processing framework identify the processing status of the subtask, the processing status includes retry, and the processing conditions corresponding to the processing status include a retry threshold. The processing status of the subtask is identified by the log of the batch processing framework. The processing status includes restart, and the processing conditions corresponding to the processing status include a restart threshold.

2. The business processing method according to claim 1, characterized in that, The subtasks include the deduction subtask, the customer identification subtask, the discount deduction subtask, the settlement document acquisition subtask, the settlement document sending subtask, and the return file receiving subtask.

3. The business processing method according to claim 1, characterized in that, The process involves identifying the subtask and its sub-business cycle within the batch processing framework, monitoring the business processing subtasks of multiple users within the subtask via an interface, and determining if the business processing subtasks of multiple users within the subtask meet the execution conditions of the subtask based on the business tag information returned by the interface. In this case, the execution of the subtask within its sub-business cycle is triggered, and the batch processing framework records the logs of the subtask. This includes: Add business tags to 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; If the execution parameters of the business processing subtasks of multiple users in the subtask are received, 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, then the execution of the subtask in the sub-business cycle of the subtask is triggered, and the batch processing framework records the log of the subtask.

4. The business processing method according to claim 1, characterized in that, The process involves using logs based on the batch processing framework to identify the processing status of the subtasks, and determining the next subtask for the business processing subtasks of multiple users within the subtasks according to the processing status and the corresponding processing conditions, in order to execute the next subtask for the business processing subtasks of multiple users. This includes: If the processing status of the subtask includes skipping, and the number of skips of the subtask is less than or equal to the skipping threshold, then 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 order, so as to execute the next subtask of the current subtask. If the processing status of the subtask includes skipping, and the number of skips of the subtask is greater than the skipping threshold and the subtask job duration is greater than the sub-business cycle of the subtask, then the next subtask of the business processing subtasks of multiple users in the subtask is 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 process involves using logs based on the batch processing framework to identify the processing status of the subtasks, and determining the next subtask for the business processing subtasks of multiple users within the subtasks according to the processing status and the corresponding processing conditions, in order to execute the next subtask for the business processing subtasks of multiple users. This includes: If the processing status of the subtask includes retry, and the number of retries of the subtask is greater than the retry 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 the previous subtask of the current subtask in the business execution order, 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 the retry threshold, then the next subtask of the business processing subtasks of multiple users in the subtask is the current subtask, and the current subtask is executed.

6. The business processing method according to claim 1, characterized in that, The process involves using logs based on the batch processing framework to identify the processing status of the subtasks, and determining the next subtask for the business processing subtasks of multiple users within the subtasks according to the processing status and the corresponding processing conditions, in order to execute the next subtask for the business processing subtasks of multiple users. This includes: If the processing status of the subtask includes restart, and the number of restarts of the subtask is greater than the restart 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 the previous subtask of the current subtask in the business execution order, so as to execute the previous subtask of the current subtask. 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, then the next subtask of the business processing subtasks of multiple users in the subtask is the current subtask, and the current subtask is executed.

7. The method for processing business 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 in the process of executing business processing subtasks for multiple users includes: The payment transaction of the current subtask is marked as completed, and the subtask with the first execution order of the next payment transaction is designated as the next subtask of the business processing subtasks of the multiple users, so as to execute the next subtask of the business processing subtasks of the multiple users.

8. A business processing apparatus, characterized in that, include: The task module is used to divide the payment business into multiple sub-tasks according to the business execution order and the business identifier in the business execution message, and to determine the sub-business cycle of the sub-tasks based on the priority of the sub-tasks and the business cycle of the payment business. Furthermore, the payment business is divided into multiple sub-tasks according to the business execution order and the business identifier in the business execution message, and the sub-business cycle of the sub-task is determined based on the priority of the sub-task, the interaction party of the sub-task, and the business cycle of the payment business. The execution module is used to identify the subtask and the sub-business cycle of the subtask in the batch processing framework, monitor the business processing subtasks of multiple users in the subtask through the interface, and determine that the business processing subtasks of multiple users in the subtask in the subtask meet the execution conditions of the subtask in the business tag information returned by the interface. Then, the execution of the subtask in the sub-business cycle of the subtask is triggered and the batch processing framework records the 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 to 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. The batch processing framework uses logs to identify the processing status of the subtasks, including skipping, and the processing conditions corresponding to the processing status include a skip threshold. The logs based on the batch processing framework identify the processing status of the subtask, the processing status includes retry, and the processing conditions corresponding to the processing status include a retry threshold. The processing status of the subtask is identified by the log of the batch processing framework. The processing status includes restart, and the processing conditions corresponding to the processing status include a restart threshold.

9. An electronic device for business processing, characterized in that, include: One or more processors; 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 as described in any one of claims 1-7.

10. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-7.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-7.

Images