RPA scheduling method and device of tax declaring system, equipment and storage medium

By designing RPA scheduling methods in the tax filing system and creating tax filing queues and task packages, the problem of inefficient parallel execution of different tax numbers and task types for the same tax filing is solved, and efficient RPA calls and task processing is achieved.

CN118917804AActive Publication Date: 2024-11-08BEIJING SHENZHOU YUNHE DATA TECH DEV CO LTD
View PDF 10 Cites 0 Cited by

Patent Information

Application Number
CN202411093323.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-09
Publication Date
2024-11-08
Estimated Expiration
2044-08-09

AI Technical Summary

Technical Problem

When the existing tax filing system handles different tax numbers and different task types of the same tax filing, there are problems of inefficiency and inconvenience in parallel execution, and fails to effectively optimize RPA calls.

Method used

A tax filing system RPA scheduling method is designed, a tax filing queue is created through the middle platform subsystem, a to-do tasks with the same tax number is drawn, a task package is formed, and a task package is sent to the RPA capability layer for parallel or strings based on the parallel configuration table. Line execution, using cloud functions to implement asynchronous calls to improve efficiency.

Benefits of technology

It effectively avoids the problem of squeezing out parallel tasks of different tax numbers, improves processing efficiency, simplifies the process, and optimizes processing time through asynchronous calls and cloud functions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118917804A_ABST
    Figure CN118917804A_ABST
Patent Text Reader

Abstract

The invention relates to the field of data processing, and discloses an RPA scheduling method and device of a tax declaring system, equipment and a storage medium. The tax declaration system comprises a middle platform subsystem, a glue layer and an RPA capability layer. The method comprises the following steps: the middle platform subsystem creates tax declarator queues in one-to-one correspondence with tax declarators; after a preset time interval, respectively extracting to-do tasks with the same tax number in each tax declarator queue to obtain batch tasks in one-to-one correspondence with the tax declarators, and issuing the batch tasks to a glue layer; the glue layer creates task packages in one-to-one correspondence with the tax declarators for the batch tasks based on a preset parallel configuration table; wherein each task package comprises one or more parallel to-be-handled tasks or one non-parallel to-be-handled task; the glue layer sends the task packets to an RPA capability layer, so that to-be-processed tasks in each task packet call the RPA capability layer; and the glue layer receives the execution result returned by the RPA capability layer and returns the execution result to the middle platform subsystem. According to the invention, mutual extrusion caused by simultaneous login of different tax numbers of tax declarators can be avoided, and parallel tasks are all executed in parallel, so that the processing efficiency is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of data processing, and more specifically, to an RPA scheduling method, apparatus, device and storage medium for a tax declaration system. Background Art

[0002] The tax filing system can automate tax filing through RPA (Robotic Process Automation). Combined with cloud function technology, RPA has completed serviceless and interface-based processing according to the tax type and tax filing task type. However, the tax bureau has restrictions that different tax numbers of the same taxpayer cannot log in at the same time, and some of the different task types can be executed in parallel while others cannot. The existing tax filing system has not been optimized for the above restrictions and situations. Therefore, how to efficiently call RPA for tax filing processing is an urgent problem to be solved. Summary of the invention

[0003] In view of this, the embodiments of the present application are committed to providing an RPA scheduling method, device, equipment and storage medium for a tax filing system to solve the problem of low efficiency in calling RPA for tax filing processing.

[0004] In a first aspect, this specification provides an RPA scheduling method for a tax declaration system, wherein the tax declaration system includes a middle platform subsystem, a glue layer, and an RPA capability layer. The method includes:

[0005] The middle-office subsystem creates a queue of taxpayers corresponding to the taxpayers one by one; and after a preset time interval, extracts the pending tasks with the same tax number in each taxpayer queue, obtains batch tasks corresponding to the taxpayers one by one, and sends the batch tasks to the glue layer;

[0006] The glue layer creates task packages corresponding to the tax filers based on the preset parallel configuration table for batch tasks; each task package includes one or more parallelizable tasks or one non-parallelizable task;

[0007] The glue layer sends the task package to the RPA capability layer, so that the to-do tasks in each task package call the RPA capability layer.

[0008] The glue layer receives the execution results returned by the RPA capability layer and returns the execution results to the middle platform subsystem.

[0009] According to the first aspect, in a possible implementation, the tax declaration system further includes a login service layer;

[0010] The glue layer sends the task package to the RPA capability layer, including:

[0011] The glue layer calls the login service layer to obtain the login cookie of each task package;

[0012] The to-do tasks in each task package carry the login cookie to call the RPA capability layer.

[0013] According to the first aspect, in a possible implementation, the method further includes: the glue layer receives a maintenance instruction for maintaining the parallel configuration table, and maintains the task type and tax type of the tax declaration task in the parallel configuration table based on the maintenance instruction.

[0014] According to the first aspect, in a possible implementation, extracting to-do tasks with the same tax number in each taxpayer queue includes:

[0015] Extract the pending tasks with the same tax number from each taxpayer's queue, which shall not exceed the preset number.

[0016] According to the first aspect, in a possible implementation manner, receiving the execution result returned by the RPA capability layer includes:

[0017] Within the preset execution time, the RPA capability layer completes all pending tasks contained in the task package and returns the execution results; or

[0018] Within the preset execution time, the RPA capability layer did not complete all the to-do tasks included in the task package and returned the execution result.

[0019] According to the first aspect, in a possible implementation manner, the to-do task is a declaration task, a collection task, a receipt task, a deduction task, or a declaration material download task.

[0020] According to the first aspect, in a possible implementation, the glue layer is implemented by a first cloud function and a second cloud function, the first cloud function is used to receive batch tasks and send task packages to the RPA capability layer, and the second cloud function is used to receive execution results and return the execution results to the middle platform subsystem;

[0021] Asynchronous calls are made between the middle platform subsystem and the glue layer, and between the glue layer and the RPA capability layer.

[0022] In the second aspect, this specification provides an RPA scheduling device for a tax declaration system. The tax declaration system includes a middle platform subsystem, a glue layer, and an RPA capability layer. The RPA scheduling device includes:

[0023] The taxpayer queue unit is used to instruct the middle office subsystem to create a taxpayer queue corresponding to each taxpayer; and after a preset time interval, the pending tasks with the same tax number in each taxpayer queue are extracted to obtain batch tasks corresponding to each taxpayer, and the batch tasks are sent to the glue layer;

[0024] The task package unit is used to instruct the glue layer to create task packages corresponding to the tax filers one by one based on the preset parallel configuration table for the batch tasks; wherein each task package includes one or more parallelizable to-do tasks or one non-parallelizable to-do task;

[0025] The task execution unit is used to instruct the glue layer to send the task package to the RPA capability layer, so that the to-do tasks in each task package call the RPA capability layer;

[0026] The execution result returning unit is used to instruct the glue layer to receive the execution result returned by the RPA capability layer and return the execution result to the middle platform subsystem.

[0027] According to the second aspect, in a possible implementation, the tax declaration system further includes a login service layer;

[0028] The task execution unit is specifically used for:

[0029] Instruct the glue layer to call the login service layer to obtain the login cookie of each task package;

[0030] Instructs the to-do tasks in each task package to carry the login cookie to call the RPA capability layer.

[0031] According to the second aspect, in a possible implementation, the glue layer further includes a parallel configuration table maintenance module, which is used to: receive maintenance instructions for maintaining the parallel configuration table, and maintain the task type and tax type of the tax declaration task in the parallel configuration table based on the maintenance instructions.

[0032] According to the second aspect, in a possible implementation, the taxpayer queue unit includes an extraction module, which is used to extract to-do tasks with the same tax number in each taxpayer queue that do not exceed a preset scheduling number.

[0033] According to the second aspect, in a possible implementation manner, the execution result returning unit is specifically configured to:

[0034] Within the preset execution time, the RPA capability layer completes all pending tasks contained in the task package and returns the execution results; or

[0035] Within the preset execution time, the RPA capability layer did not complete all the to-do tasks included in the task package and returned the execution result.

[0036] According to the second aspect, in a possible implementation, the to-do task is a declaration task, a collection task, a receipt task, a deduction task, or a declaration material download task.

[0037] According to the second aspect, in a possible implementation, the glue layer is implemented by a first cloud function and a second cloud function, the first cloud function is used to receive batch tasks and send task packages to the RPA capability layer, and the second cloud function is used to receive execution results and return the execution results to the middle platform subsystem;

[0038] Asynchronous calls are made between the middle platform subsystem and the glue layer, and between the glue layer and the RPA capability layer.

[0039] On the third aspect, this specification provides an RPA scheduling device for a tax reporting system, including a processor, an input device, an output device and a memory, wherein the processor, the input device, the output device and the memory are interconnected, wherein the memory is used to store a computer program, the computer program includes program instructions, and the processor is configured to call the program instructions to execute the described method.

[0040] In a fourth aspect, the present specification provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is executed to implement the described method.

[0041] Compared with the prior art, the beneficial effects of the present invention are:

[0042] Different from the prior art, the RPA scheduling method for the tax filing system provided by the present invention creates a taxpayer queue corresponding to the taxpayer one-to-one through the middle-office subsystem; and extracts the pending tasks with the same tax number in each taxpayer queue after a preset time interval, obtains batch tasks corresponding to the taxpayer one-to-one, and sends the batch tasks to the glue layer; the glue layer creates a task package corresponding to the taxpayer one-to-one based on the preset parallel configuration table for the batch tasks; wherein each task package includes one or more parallel pending tasks or one non-parallel pending task; the glue layer sends the task package to the RPA capability layer, so that the pending tasks in each task package call the RPA capability layer; the glue layer receives the execution result returned by the RPA capability layer, and returns the execution result to the middle-office subsystem. By adopting this method, pending tasks with the same tax number of taxpayers are extracted in the same batch, which avoids taxpayers with different tax numbers logging in at the same time and squeezing each other out, and parallel tasks are placed in one task package for parallel execution, thereby improving processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0044] Figure 1A flowchart of an RPA scheduling method for a tax declaration system provided in an embodiment of the present application;

[0045] Figure 2 A schematic diagram of a task package carrying a login cookie calling an RPA capability layer provided in an embodiment of the present application;

[0046] Figure 3 A schematic diagram of creating a batch task when the number of scheduled tasks exceeds a preset number provided in an embodiment of the present application;

[0047] Figure 4 A schematic diagram of the logical structure of the glue layer, the middle platform subsystem, and the RPA capability layer provided in the embodiment of the present application;

[0048] Figure 5 A schematic diagram of RPA scheduling for an example tax declaration system provided in an embodiment of the present application;

[0049] Figure 6 An RPA scheduling device for a tax declaration system provided in an embodiment of the present application;

[0050] Figure 7 A schematic diagram of the structure of the RPA scheduling device of the tax declaration system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0051] Unless otherwise defined, the technical terms or scientific terms used in the embodiments of this specification shall have the common meanings understood by persons with ordinary skills in the field to which this specification belongs. The words "first", "second" and similar words used in the embodiments of this specification do not indicate any order, quantity or importance, but are only used to avoid confusion of constituent elements.

[0052] Unless the context requires otherwise, throughout the specification, "plurality" means "at least two", and "including" is interpreted as an open, inclusive meaning, that is, "including, but not limited to". In the description of the specification, the terms "one embodiment", "some embodiments", "exemplary embodiments", "examples", "specific examples" or "some examples" are intended to indicate that a particular feature, structure, material or characteristic associated with the embodiment or example is included in at least one embodiment or example of the specification. The schematic representation of the above terms does not necessarily refer to the same embodiment or example.

[0053] The following will be combined with the drawings in the embodiments of this specification to clearly and completely describe the technical solutions in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0054] like Figure 1 As shown, it is a flow chart of an RPA scheduling method for a tax reporting system provided in an embodiment of the present invention. The tax reporting system includes a middle platform subsystem, a glue layer and an RPA capability layer. The method may specifically include the following steps.

[0055] S110: The middle platform subsystem creates a taxpayer queue corresponding to each taxpayer; and extracts pending tasks with the same tax number from each taxpayer queue after a preset time interval, obtains batch tasks corresponding to each taxpayer, and sends the batch tasks to the glue layer;

[0056] S120: The glue layer creates task packages corresponding to the tax filers based on the preset parallel configuration table for the batch tasks; wherein each task package includes one or more parallelizable to-do tasks or one non-parallelizable to-do task;

[0057] S130: The glue layer sends the task package to the RPA capability layer, so that the to-be-done tasks in each task package call the RPA capability layer;

[0058] S140: The glue layer receives the execution result returned by the RPA capability layer, and returns the execution result to the middle platform subsystem.

[0059] In the above method, the taxpayer is an account for logging into the tax bureau, which is a natural person, and can be one or more. Each taxpayer queue contains pending tasks (i.e., specific tasks) corresponding to one or more tax numbers of the taxpayer. The types of taxpayer queues created can include ordinary queues, circular queues, chain queues, priority queues, concurrent queues, and task queues, which can be selected as needed. The preset time interval can be set according to the number of taxpayers and / or the number of pending tasks (for example, 1 minute). The glue layer is a logical layer that plays the role of gluing the middle-end subsystem and the RPA capability layer, and is responsible for the orchestration and scheduling of tasks, including cloud functions, middleware, databases, etc. Cloud functions are a serverless computing service that allows developers to write and run code on a cloud platform without managing servers or runtime environments. Cloud functions are usually triggered by events and can respond to various types of requests, such as HTTP requests, database changes, file uploads, etc. The advantage of this service is its elastic scaling capability, which can automatically adjust resources according to actual usage to optimize costs and performance. The parallel configuration table is pre-configured and stored in the glue layer, which is used to divide the task types of pending tasks (i.e., parallel execution and non-parallel execution). A task package is an abstract concept. A task package can contain one or more parallel to-do tasks. Tasks in a task package containing multiple parallel to-do tasks can be executed in parallel; task packages are executed serially. The RPA capability layer contains a series of RPA interfaces for receiving specific tax declaration tasks, executing them, and returning results.

[0060] This embodiment extracts pending tasks with the same tax number of the taxpayer in the same batch, thereby avoiding the situation where taxpayers with different tax numbers log in at the same time and squeeze each other out. Parallel tasks are put into one task package and executed in parallel, thereby improving processing efficiency. In addition, the concept of task package is proposed, making the entire process clearer and simpler.

[0061] In at least one embodiment of the present application, in order to call the RPA capability layer, the tax filing system is designed to also include a login service layer, and the glue layer sends the task package to the RPA capability layer. The specific design is as follows: the glue layer calls the login service layer to obtain the login cookie of each task package; the to-do tasks in each task package carry the login cookie to call the RPA capability layer.

[0062] The glue layer calls the unified login service interface to obtain the login cookie based on the login information of the pending tasks in the task package. The cookie can be injected into the tax bureau page in the browser to log in to the electronic tax bureau. The login service layer is specifically used to call the service interface, pass in the account, password, tax number and other related information, and the interface will return the login cookie. Figure 2 As shown, it is a schematic diagram of the task package carrying the login cookie provided by an embodiment of the present invention calling the RPA capability layer.

[0063] This embodiment uses Cookie to log in to the electronic tax bureau, shortening the login time and reducing the consumption of SMS.

[0064] In at least one embodiment of the present application, the method further includes: the glue layer receives a maintenance instruction for maintaining a parallel configuration table, and maintains the task type and tax type of the tax reporting task in the parallel configuration table based on the maintenance instruction. Tax reporting tasks will change over time, such as name, quantity, etc., and whether the tax reporting task can be executed in parallel mainly depends on the task type and tax type, so the parallel configuration table can be maintained based on the task type and tax type of the tax reporting task. The maintenance instruction can be automatically triggered by the system, and the parallel configuration table can be maintained according to preset rules, or when maintenance is required, the maintenance instruction will remind the relevant maintenance personnel to perform maintenance. The maintenance of the parallel configuration table helps to adapt to a variety of tax reporting tasks and changes in tax reporting tasks, thereby enhancing system availability.

[0065] In at least one embodiment of the present application, in order to reduce waiting time, the to-do tasks with the same tax number in each taxpayer queue are extracted and designed as follows: to-do tasks with the same tax number in each taxpayer queue that do not exceed a preset scheduling number are extracted.

[0066] The preset scheduling number can be set according to specific circumstances (e.g., the taxpayer, the number of tax filing tasks, etc.). For example, the taxpayer is Zhang San, and there are 120 pending tasks under his tax number 001. When the preset scheduling number is 100, no more than 100 pending tasks will be drawn each time; for example, when there are many taxpayers and / or pending tasks, a certain proportion (e.g., 90%, 85%, 80%, etc.) of the preset scheduling number of pending tasks can be drawn each time; when there are few taxpayers and / or pending tasks, a preset scheduling number of pending tasks can be drawn each time. This embodiment avoids long waiting times and improves processing efficiency by setting a preset scheduling number. Figure 3 , which is a schematic diagram of creating batch tasks when the number of scheduled tasks exceeds a preset number provided by an embodiment of the present invention.

[0067] In at least one embodiment of the present application, in order to further reduce the waiting time, the execution result returned by the receiving RPA capability layer can be designed as follows: within the preset execution time, the RPA capability layer executes all the pending tasks included in the task package and returns the execution result; or within the preset execution time, the RPA capability layer does not execute all the pending tasks included in the task package and returns the execution result.

[0068] The preset execution time can be set according to specific circumstances (such as the taxpayer, the number of tax return tasks, etc.), for example, 40 seconds. If the RPA capability layer does not complete all pending tasks contained in the task package within the preset execution time, after returning the execution result, the unfinished pending tasks can be left in the task package, waiting for the next extraction of the same tax number task for the same taxpayer, or the execution status of the tax return task of the taxpayer corresponding to the unfinished pending task in the middle-office subsystem is set to unfinished, waiting for the next extraction. Due to unreasonable task execution settings (such as preset scheduling numbers) or unexpected situations (such as network instability, congestion, etc.), a long waiting time may be caused. This embodiment can avoid long waiting times, thereby bringing a better user experience.

[0069] In at least one embodiment of the present application, the to-do task is a declaration task, a collection task, a receipt task, a deduction task, or a declaration material download task. The declaration task, the collection task, the receipt task, the deduction task, and the declaration material download task are task types divided in the tax declaration system according to the business. The collection task can be further divided into historical data collection, pre-filled data collection, taxpayer basic information collection, and identification information collection. The receipt task can be divided into declaration receipt and deduction receipt. The declaration material download task can be divided into declaration form download and tax payment certificate download. The task type of the to-do task can be maintained automatically or manually as needed.

[0070] In at least one embodiment of the present application, in order to shorten the processing time and improve the processing efficiency, the glue layer, as well as the scheduling between the glue layer and the middle platform subsystem, and the glue layer and the RPA capability layer can be set: the glue layer is implemented by a first cloud function and a second cloud function, the first cloud function is used to receive batch tasks and send task packages to the RPA capability layer, and the second cloud function is used to receive execution results and return the execution results to the middle platform subsystem; the middle platform subsystem and the glue layer, and the glue layer and the RPA capability layer are all set as asynchronous calls.

[0071] like Figure 4 The figure shows the logical structure diagram of the glue layer, the middle platform subsystem, and the RPA capability layer provided in the embodiment of the present invention. The glue layer can be implemented using two Tencent cloud functions. A task_create cloud function is triggered using the http interface to receive batch tasks sent by the middle platform and send the batch tasks to the RPA capability layer. A task_callback cloud function is triggered using Ckafka to receive the execution results of the RPA capability layer. Both cloud functions support concurrent calls.

[0072] Asynchronous calls are used between the middleware subsystem and the glue layer, and between the glue layer and the RPA capability layer. The glue layer uses the Redis service to cache the execution status of a single task.

[0073] A single task is sent to the task_create cloud function of the glue layer through the middle platform. The tasks_create cloud function orchestrates the task into a task package and sends it to a cloud function in the RPA capability layer. After the task is executed, the cloud function delivers the execution result to Ckafka. The tasks_callback cloud function of the glue layer acts as a consumer of Ckafka and pushes the task execution result to the middle platform.

[0074] This embodiment implements the glue layer through cloud functions, and performs scheduling design between the glue layer and the middle platform subsystem, and between the glue layer and the RPA capability layer, thereby reducing processing time and improving processing efficiency.

[0075] The following is an example to illustrate the RPA scheduling method of the above tax declaration system. Figure 5 , which is a schematic diagram of RPA scheduling of an example tax declaration system provided in an embodiment of the present invention.

[0076] Tax number A and tax number B are the tax numbers of two subsidiaries under the same group, and they are both bound to the same taxpayer Zhang San. Tax number C is the tax number of a company under another group, and is bound to taxpayer Li Si.

[0077] Currently, there are 5 A tax number tasks (including 4 parallel pending tasks), 4 B tax number tasks (including 2 parallel pending tasks), and 3 C tax number tasks (including 2 parallel pending tasks) in the middle platform subsystem. The 5 A tax number tasks and 4 B tax number tasks are in the queue of taxpayer Zhang San, of which 5 A tax numbers are in the front of the queue, 4 B tax numbers are in the back of the queue, and 3 C tax number tasks are in the queue of taxpayer Li Si. The middle platform subsystem organizes the 5 A tax number tasks into batch 1 and the 3 C tax number tasks into batch 2 and sends them to the glue layer at the same time.

[0078] For tasks in batch 1, the glue layer arranges the to-do tasks into a multi-task task package that carries two parallel to-do tasks and a single-task task package that carries one non-parallel to-do task, and carries the cookie to call the RPA capability layer. The number of tasks in a multi-task task package can be set. This example only takes two tasks as an example.

[0079] At the same time, for the tasks in batch 2, the glue layer arranges the to-do tasks into a multi-task task package that carries two parallel to-do tasks and a single-task task package that carries one non-parallel to-do task, and carries the cookie to call the RPA capability layer.

[0080] The results of each to-do task executed at the RPA capability layer will be returned to the middle platform subsystem through the glue layer.

[0081] The present application also provides an RPA scheduling device for a tax reporting system corresponding to the above-mentioned RPA scheduling method.

[0082] like Figure 6 As shown, an RPA scheduling device 600 of a tax declaration system provided by an embodiment of the present invention, the tax declaration system includes a middle platform subsystem, a glue layer and an RPA capability layer, and the RPA scheduling device includes:

[0083] The taxpayer queue unit 610 is used to instruct the middle platform subsystem to create a taxpayer queue corresponding to each taxpayer; and after a preset time interval, the to-do tasks with the same tax number in each taxpayer queue are extracted to obtain batch tasks corresponding to each taxpayer, and the batch tasks are sent to the glue layer;

[0084] The task package unit 620 is used to instruct the glue layer to create task packages corresponding to the tax filers based on the preset parallel configuration table for the batch tasks; wherein each task package includes one or more parallelizable to-do tasks or one non-parallelizable to-do task;

[0085] The task execution unit 630 is used to instruct the glue layer to send the task package to the RPA capability layer, so that the to-be-done tasks in each task package call the RPA capability layer;

[0086] The execution result returning unit 640 is used to instruct the glue layer to receive the execution result returned by the RPA capability layer and return the execution result to the middle platform subsystem.

[0087] The taxpayer is an account for logging into the tax bureau. It is a natural person and can be one or more. Each taxpayer queue contains pending tasks corresponding to one or more tax numbers of the taxpayer. The types of taxpayer queues created can include ordinary queues, circular queues, chain queues, priority queues, concurrent queues, and task queues, which can be selected as needed. The preset time interval can be set according to the number of taxpayers and / or the number of pending tasks (for example, 1 minute). The glue layer is a logical layer that plays the role of gluing the middle-end subsystem and the RPA capability layer. It is responsible for the orchestration and scheduling of tasks, including cloud functions, middleware, databases, etc. Cloud functions are a serverless computing service that allows developers to write and run code on a cloud platform without managing servers or runtime environments. Cloud functions are usually triggered by events and can respond to various types of requests, such as HTTP requests, database changes, file uploads, etc. The advantage of this service is its elastic scaling capability, which can automatically adjust resources according to actual usage to optimize costs and performance. The parallel configuration table is pre-configured and stored in the glue layer, which is used to divide the task types of pending tasks (i.e., parallel execution and non-parallel execution). A task package is an abstract concept. A task package can contain one or more parallel to-do tasks. Tasks in a task package containing multiple parallel to-do tasks can be executed in parallel; task packages are executed serially. The RPA capability layer contains a series of RPA interfaces for receiving specific tax declaration tasks, executing them, and returning results.

[0088] In the above device, the taxpayer queue unit 610 extracts pending tasks with the same taxpayer ID in the same batch, thereby preventing taxpayers with different tax IDs from logging in at the same time and squeezing each other out. The task package unit 620 puts parallel tasks into a task package and executes them in parallel, thereby improving processing efficiency. In addition, the concept of task package makes the entire process clearer and simpler.

[0089] In at least one embodiment of the present application, in order to call the RPA capability layer, the tax reporting system is designed to also include a login service layer, and the task execution unit 630 is specifically used to: instruct the glue layer to call the login service layer to obtain the login cookie of each task package; instruct the to-do tasks in each task package to carry the login cookie to call the RPA capability layer.

[0090] The glue layer calls the unified login service interface to obtain the login cookie based on the login information of the pending tasks in the task package, and then injects the cookie into the tax bureau page in the browser to log in to the electronic tax bureau. The login service layer is specifically used to call the service interface, pass in the account, password, tax number and other related information, and the interface will return the login cookie.

[0091] This embodiment uses Cookie to log in to the electronic tax bureau, shortening the login time and reducing the consumption of SMS.

[0092] In at least one embodiment of the present application, the glue layer also includes a parallel configuration table maintenance module, which is used to: receive maintenance instructions for maintaining the parallel configuration table, and maintain the task type and tax type of the tax reporting task in the parallel configuration table based on the maintenance instructions. Tax reporting tasks will change over time, such as name, quantity, etc., and whether the tax reporting task can be executed in parallel mainly depends on the task type and tax type. Therefore, the parallel configuration table can be maintained based on the task type and tax type of the tax reporting task. The maintenance instruction can be automatically triggered by the system, and the parallel configuration table can be maintained according to preset rules, or when maintenance is required, the maintenance instruction will remind you and the relevant maintenance personnel will perform maintenance. The maintenance of the parallel configuration table helps to adapt to various tax reporting tasks and changes in tax reporting tasks, thereby enhancing system availability.

[0093] In at least one embodiment of the present application, in order to reduce waiting time, the taxpayer queue unit 610 can be designed to include an extraction module, which is used to extract to-do tasks with the same tax number in each taxpayer queue that do not exceed a preset scheduling number.

[0094] The preset scheduling number can be set according to specific circumstances (e.g., the number of taxpayers, the number of tax filing tasks, etc.). For example, the taxpayer is Zhang San, and there are 120 pending tasks under his tax number 001. When the preset scheduling number is 100, no more than 100 pending tasks are extracted each time; for example, when there are many taxpayers and / or pending tasks, a certain proportion (e.g., 90%, 85%, 80%, etc.) of the preset scheduling number of pending tasks can be extracted each time; when there are fewer taxpayers and / or pending tasks, the preset scheduling number of pending tasks can be extracted each time. This embodiment avoids long waiting time and improves processing efficiency by setting the preset scheduling number.

[0095] In at least one embodiment of the present application, in order to further reduce the waiting time, the execution result returning unit 640 can be designed to be specifically used for: within the preset execution time, the RPA capability layer completes the execution of all pending tasks included in the task package and returns the execution result; or within the preset execution time, the RPA capability layer fails to complete the execution of all pending tasks included in the task package and returns the execution result.

[0096] The preset execution time can be set according to specific circumstances (such as the taxpayer, the number of tax return tasks, etc.), for example, 40 seconds. If the RPA capability layer does not complete all pending tasks contained in the task package within the preset execution time, after returning the execution result, the unfinished pending tasks can be left in the task package, waiting for the next extraction of the same tax number task for the same taxpayer, or the execution status of the tax return task of the taxpayer corresponding to the unfinished pending task in the middle-office subsystem is set to unfinished, waiting for the next extraction. Due to unreasonable task execution settings (such as preset scheduling numbers) or unexpected situations (such as network instability, congestion, etc.), a long waiting time may be caused. This embodiment can avoid long waiting times, thereby bringing a better user experience.

[0097] In at least one embodiment of the present application, the to-do task is a declaration task, a collection task, a receipt task, a deduction task, or a declaration material download task. The declaration task, the collection task, the receipt task, the deduction task, and the declaration material download task are task types divided in the tax declaration system according to the business. The collection task can be further divided into historical data collection, pre-filled data collection, taxpayer basic information collection, and identification information collection. The receipt task can be divided into declaration receipt and deduction receipt. The declaration material download task can be divided into declaration form download and tax payment certificate download. The task type of the to-do task can be maintained automatically or manually as needed.

[0098] In at least one embodiment of the present application, in order to shorten the processing time and improve the processing efficiency, the glue layer, as well as the scheduling between the glue layer and the middle platform subsystem, and the glue layer and the RPA capability layer can be set: the glue layer is implemented by a first cloud function and a second cloud function, the first cloud function is used to receive batch tasks and send task packages to the RPA capability layer, and the second cloud function is used to receive execution results and return the execution results to the middle platform subsystem; the middle platform subsystem and the glue layer, and the glue layer and the RPA capability layer are all set as asynchronous calls.

[0099] The glue layer can be implemented using two Tencent Cloud functions. One task_create cloud function is triggered using the http interface to receive batch tasks sent by the middle office and send the batch tasks to the RPA capability layer. One task_callback cloud function is triggered using Ckafka to receive the execution results of the RPA capability layer. Both cloud functions support concurrent calls. A cloud function is a function that runs in the cloud. Developers do not need to purchase or build servers. They only need to write function code and deploy it to the cloud to call it on the mini program side.

[0100] Asynchronous calls are used between the middleware subsystem and the glue layer, and between the glue layer and the RPA capability layer. The glue layer uses the Redis service to cache the execution status of a single task.

[0101] A single task is sent to the task_create cloud function of the glue layer through the middle platform. The tasks_create cloud function arranges the task into a task package and sends it to a cloud function of the RPA capability layer. After the task is completed, the cloud function delivers the execution result to Ckafka. The tasks_callback cloud function of the glue layer, as a consumer of Ckafka, pushes the task execution result to the middle platform. The message queue CKafka (Cloud Kafka) is based on the open source Apache Kafka message queue engine, providing high throughput and high scalability message queue services.

[0102] This embodiment implements the glue layer through cloud functions, and performs scheduling design between the glue layer and the middle platform subsystem, and between the glue layer and the RPA capability layer, thereby reducing processing time and improving processing efficiency.

[0103] like Figure 7 As shown, a schematic diagram of the structure of the RPA scheduling device of the tax filing system provided in an embodiment of the present invention is shown. As shown in the figure, the RPA scheduling device 70 of the tax filing system includes one or more processors 71 and a memory 72.

[0104] The processor 71 may be a central processing unit (CPU) or other forms of processing units having data processing capabilities and / or instruction execution capabilities, and may control other components in the RPA scheduling device 70 of the tax filing system to perform desired functions.

[0105] The memory 72 may include one or more computer program products, and the memory may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory (cache), etc. The non-volatile memory may include, for example, a read-only memory (ROM), a hard disk, a flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 71 may run the program instructions to implement the RPA scheduling method of each embodiment of the present application described above and / or other desired functions. Various contents such as input signals, signal components, noise components, etc. may also be stored in the computer-readable storage medium.

[0106] In one example, the RPA scheduling device 70 of the tax declaration system may further include: an input device 73 and an output device 74, and these components are interconnected via a bus system and / or other forms of connection mechanisms (not shown).

[0107] Of course, to simplify, Figure 7Only some of the components related to the present application in the RPA scheduling device 70 of the tax filing system are shown, and components such as a bus, an input / output interface, etc. are omitted. In addition, according to the specific application situation, the RPA scheduling device 70 of the tax filing system may also include any other appropriate components.

[0108] Based on the embodiments of the present application, the present application also provides a computer-readable storage medium, wherein computer instructions are used to enable a computer to execute each step in the RPA scheduling method of the aforementioned technical solution.

[0109] Based on the embodiments of the present application, the present application also provides a processor, which is used to run a program, wherein the program executes each step in the RPA scheduling method of the aforementioned technical solution when it is running.

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

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

[0112] It should be understood that each part of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the described embodiment, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system.

[0113] For the above description of the disclosed embodiments, the features recorded in each embodiment in this specification can be replaced or combined with each other, so that professionals in the field can implement or use the present application. The above is only a preferred embodiment of the present invention, and does not limit the present invention in any form. Although the present invention has been disclosed as above with a preferred embodiment, it is not used to limit the present invention. Any technician familiar with the field can make many possible changes and modifications to the technical solution of the present invention using the methods and technical contents disclosed above without departing from the scope of the technical solution of the present invention, or modify it into an equivalent embodiment of equivalent changes. Therefore, any simple modification, equivalent change and modification made to the above embodiments according to the technical essence of the present invention without departing from the content of the technical solution of the present invention still falls within the scope of protection of the technical solution of the present invention.

Claims

1. An RPA scheduling method for a tax declaration system, characterized in that: The tax declaration system includes a middle platform subsystem, a glue layer and an RPA capability layer, and the RPA scheduling method includes: The middle platform subsystem creates a taxpayer queue corresponding to each taxpayer; and extracts pending tasks with the same tax number from each taxpayer queue after a preset time interval, obtains batch tasks corresponding to each taxpayer, and sends the batch tasks to the glue layer; The glue layer creates task packages corresponding to the tax filers one by one based on the preset parallel configuration table for the batch tasks; wherein each task package includes one or more parallelizable to-do tasks or one non-parallel to-do task; The glue layer sends the task package to the RPA capability layer, so that each to-be-done task in the task package calls the RPA capability layer; The glue layer receives the execution result returned by the RPA capability layer, and returns the execution result to the middle platform subsystem.

2. The RPA scheduling method according to claim 1, characterized in that: The tax declaration system also includes a login service layer; The glue layer sends the task package to the RPA capability layer, including: The glue layer calls the login service layer to obtain the login cookie of each task package; Each to-do task in the task package carries the login cookie to call the RPA capability layer.

3. The RPA scheduling method according to claim 2, characterized in that: Also includes: The glue layer receives a maintenance instruction for maintaining the parallel configuration table, and maintains the task type and tax type of the tax declaration task in the parallel configuration table based on the maintenance instruction.

4. The RPA scheduling method according to any one of claims 1 to 3, characterized in that: The extracting of pending tasks with the same tax number in each of the taxpayers' queues includes: The to-do tasks with the same tax number in each taxpayer queue, which do not exceed a preset number, are selected.

5. The RPA scheduling method according to claim 4, characterized in that: The receiving the execution result returned by the RPA capability layer includes: Within the preset execution time, the RPA capability layer executes all pending tasks contained in the task package and returns the execution result; or Within the preset execution time, the RPA capability layer does not complete the execution of all pending tasks included in the task package and returns the execution result.

6. The RPA scheduling method according to claim 1, characterized in that: The pending tasks are declaration tasks, collection tasks, receipt tasks, deduction tasks or declaration material download tasks.

7. The RPA scheduling method according to claim 4, characterized in that: The glue layer is implemented by a first cloud function and a second cloud function, wherein the first cloud function is used to receive the batch task and send the task package to the RPA capability layer, and the second cloud function is used to receive the execution result and return the execution result to the middle platform subsystem; Asynchronous calls are made between the middle platform subsystem and the glue layer, and between the glue layer and the RPA capability layer.

8. An RPA scheduling device for a tax declaration system, characterized in that: The tax declaration system includes a middle platform subsystem, a glue layer and an RPA capability layer, and the RPA scheduling device includes: The taxpayer queue unit is used to instruct the middle platform subsystem to create a taxpayer queue corresponding to each taxpayer; and after a preset time interval, the to-do tasks with the same tax number in each taxpayer queue are extracted to obtain batch tasks corresponding to each taxpayer, and the batch tasks are sent to the glue layer; A task package unit, used to instruct the glue layer to create a task package corresponding to each tax filer based on the batch task and a preset parallel configuration table; wherein each task package includes one or more parallelizable to-do tasks or one non-parallelizable to-do task; A task execution unit, configured to instruct the glue layer to send the task package to the RPA capability layer, so that each to-be-done task in the task package calls the RPA capability layer; An execution result returning unit is used to instruct the glue layer to receive the execution result returned by the RPA capability layer and return the execution result to the middle platform subsystem.

9. An RPA scheduling device for a tax declaration system, characterized in that: The invention comprises a processor, an input device, an output device and a memory, wherein the processor, the input device, the output device and the memory are interconnected, wherein the memory is used to store a computer program, the computer program comprises program instructions, and the processor is configured to call the program instructions to execute the RPA scheduling method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the computer program is executed to implement the RPA scheduling method according to any one of claims 1 to 7.

Citation Information

Patent Citations

  • Robot process automation task parallel processing method and device

    CN110648054A

  • Automatic tax declaring method and system based on cloud service architecture and related equipment

    CN110764872A

  • Tax terminal system log real-time analysis method, device, medium and system

    CN111209258A

  • Tax number switching method and system based on parallel operation of multiple golden tax devices

    CN112799727A

  • Multi-tax-control-device centralized shared invoicing data processing method

    CN114511363A