RPA Scheduling Method, Device, Equipment and Storage Medium for Tax Filing System

Abstract

The present application relates to the field of data processing, and discloses an RPA scheduling method, device, equipment and storage medium for a tax declaration system. The tax declaration system includes a middle platform subsystem, a glue layer and an RPA capability layer, and the method includes: the middle platform subsystem creates a taxpayer queue corresponding to the taxpayer one by one; and after a preset time interval, the to-do tasks with the same tax number in each taxpayer queue are extracted respectively to obtain batch tasks corresponding to the taxpayer one by one, and the batch tasks are sent to the glue layer; the glue layer creates a task package corresponding to the taxpayer one by one based on the preset parallel configuration table for the batch tasks; wherein each task package includes one or more parallel to-do tasks or one non-parallel to-do task; 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; the glue layer receives the execution result returned by the RPA capability layer, and returns the execution result to the middle platform subsystem. The present invention can prevent taxpayers with different tax numbers from logging in at the same time and squeezing each other out, and all parallel tasks are executed in parallel to improve processing efficiency.

Description

Technical Field

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

[0002] The tax filing system can perform automated tax filing through RPA (Robotic Process Automation). Combining with cloud function technology, RPA has been serverless and interfaced according to tax types and tax filing task types. However, there is a limitation that different tax numbers of the same taxpayer cannot be logged in simultaneously in the tax bureau, and some of the different task types can be executed in parallel while some cannot. The existing tax filing system has not been optimized for the above limitations 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 this 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 filing system. The tax filing system includes a middle platform subsystem, a glue layer, and an RPA capability layer. The method includes:

[0005] The middle platform subsystem creates a taxpayer queue corresponding to each taxpayer; and after a preset time interval, it extracts the to-do tasks with the same tax number in each taxpayer queue respectively to obtain batch tasks corresponding to each taxpayer, and sends the batch tasks to the glue layer;

[0006] The glue layer creates a task package corresponding to each taxpayer based on a preset parallel configuration table; wherein, each task package includes one or more to-do tasks that can be executed in parallel or one to-do task that cannot be executed in parallel;

[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 result returned by the RPA capability layer and returns the execution result to the middle platform subsystem.

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

[0010] Then, the glue layer sending the task package to the RPA capability layer includes:

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

[0012] The to-do tasks in each task package call the RPA capability layer by carrying the login Cookie.

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

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

[0015] Extracting the to-do tasks with the same tax number and not exceeding the preset scheduling number in each tax filer queue.

[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 finishes executing all the to-do tasks included in the task package and returns the execution result; or

[0018] Within the preset execution time, the RPA capability layer does not finish executing all the to-do tasks included in the task package and returns the execution result.

[0019] According to the first aspect, in a possible implementation manner, the to-do tasks are declaration tasks, collection tasks, receipt tasks, deduction tasks, or declaration data download tasks.

[0020] According to the first aspect, in a possible implementation manner, 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 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;

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

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

[0023] A tax filer queue unit, configured to instruct the middle platform subsystem to create tax filer queues corresponding to tax filers one by one; and after a preset time interval, extract the to-do tasks with the same tax number in each tax filer queue respectively, obtain batch tasks corresponding to tax filers one by one, and send the batch tasks to the glue layer;

[0024] A task package unit, which is used to instruct the glue layer to create task packages corresponding to each tax filer one by one based on a preset parallel configuration table; each task package includes one or more parallel to-do tasks or one non-parallel to-do task.

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

[0026] An execution result return unit, which 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 filing system further includes a login service layer.

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

[0029] Instructing the glue layer to call the login service layer to obtain the login Cookie for each task package.

[0030] Instructing the to-do tasks in each task package to carry the login Cookie and 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, and the parallel configuration table maintenance module is used for: receiving a maintenance instruction for maintaining the parallel configuration table and maintaining the task types and tax types of the tax filing tasks in the parallel configuration table based on the maintenance instruction.

[0032] According to the second aspect, in a possible implementation, the tax filer queue unit includes an extraction module, and the extraction module is used for extracting no more than a preset scheduling number of to-do tasks with the same tax number in each tax filer queue.

[0033] According to the second aspect, in a possible implementation, the execution result return unit is specifically used for:

[0034] Within a preset execution time, the RPA capability layer finishes executing all the to-do tasks included in the task package and returns the execution result; or

[0035] Within a preset execution time, the RPA capability layer does not finish executing all the to-do tasks included in the task package and returns the execution result.

[0036] According to the second aspect, in a possible implementation, the to-do tasks are declaration tasks, collection tasks, receipt tasks, deduction tasks, or declaration data download tasks.

[0037] According to a 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] The asynchronous calls are made both between the middle platform subsystem and the glue layer and between the glue layer and the RPA capability layer.

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

[0040] In a fourth aspect, this specification provides a computer-readable storage medium storing 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 as follows:

[0042] Different from the prior art, the RPA scheduling method for a tax filing system provided by the present invention creates a tax filer queue corresponding to each tax filer through the middle platform subsystem; and after a preset time interval, it respectively extracts the to-do tasks with the same tax number in each tax filer queue to obtain batch tasks corresponding to each tax filer, and sends the batch tasks to the glue layer; the glue layer creates task packages corresponding to each tax filer based on a preset parallel configuration table; among them, each task package includes one or more parallel to-do tasks or one non-parallel to-do task; the glue layer sends the task packages to the RPA capability layer, so that the to-do tasks in each task package call the RPA capability layer; the glue layer receives the execution results returned by the RPA capability layer and returns the execution results to the middle platform subsystem. By adopting this means, the to-do tasks with the same tax number of tax filers are extracted in the same batch, avoiding the situation that different tax numbers of tax filers log in at the same time and squeeze each other out, and the parallel tasks are placed in a task package for parallel execution, thereby improving the processing efficiency. Description of the Drawings

[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only the embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained according to the provided drawings without creative efforts.

[0044] Figure 1Schematic flowchart of an RPA scheduling method for a tax filing system provided by an embodiment of the present application;

[0045] Figure 2 Schematic diagram of a task package carrying a login Cookie calling the RPA capability layer provided by an embodiment of the present application;

[0046] Figure 3 Schematic diagram of batch task creation in the case of exceeding the preset scheduling number provided by an embodiment of the present application;

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

[0048] Figure 5 Schematic diagram of RPA scheduling for an example tax filing system provided by an embodiment of the present application;

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

[0050] Figure 7 Schematic diagram of the structure of an RPA scheduling device for a tax filing system provided by an embodiment of the present application. Detailed implementation manners

[0051] Unless otherwise defined, the technical terms or scientific terms used in the embodiments of this specification should have the ordinary meanings understood by those of ordinary skill in the art to which this specification belongs. The "first", "second", and similar terms used in the embodiments of this specification do not indicate any order, quantity, or importance, but are only used to avoid confusion of components.

[0052] Unless otherwise required by the context, throughout this specification, "a plurality of" means "at least two", and "including" is interpreted as an open and 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", etc., are intended to indicate that specific features, structures, materials, or characteristics related to the embodiment or example are included in at least one embodiment or example of this specification. The schematic representations of the above terms do not necessarily refer to the same embodiment or example.

[0053] Next, the technical solutions in the embodiments of this specification will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of this specification. Obviously, the described embodiments are only a part of the embodiments of this specification, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in this specification without creative efforts shall fall within the scope of protection of this specification.

[0054] As shown Figure 1 in the figure, it is a schematic flowchart of an RPA scheduling method for a tax filing system provided by an embodiment of the present invention. The tax filing 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 tax filer queue corresponding to each tax filer one by one; and after a preset time interval, it respectively extracts the to-do tasks with the same tax number in each tax filer queue to obtain batch tasks corresponding to each tax filer one by one, and sends the batch tasks to the glue layer;

[0056] S120: The glue layer creates a task package corresponding to each tax filer based on a preset parallel configuration table; wherein, each task package includes one or more to-do tasks that can be executed in parallel or one to-do task that cannot be executed in parallel;

[0057] S130: 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;

[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 tax filer is an account logged in to the tax bureau, which is a natural person and can be one or more. Each tax filer queue contains to-do tasks (i.e., specific tasks) with one or more tax numbers of the corresponding tax filer. The types of tax filer queues created can include ordinary queues, circular queues, linked queues, priority queues, concurrent queues, and task queues, which can be selected according to needs. The preset time interval can be set according to the number of tax filers and / or the number of to-do tasks (for example, 1 minute). The glue layer is a logical layer that plays a role in gluing the middle platform subsystem and the RPA capability layer, responsible for task orchestration and scheduling, and includes cloud functions, middleware, databases, etc. A cloud function is a serverless computing service that allows developers to write and run code on the 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 lies in its elastic scaling ability, which can automatically adjust resources according to actual usage, thereby optimizing costs and performance. The parallel configuration table is pre-configured and stored in the glue layer, and is used to divide the types of to-do tasks (i.e., tasks that can be executed in parallel and tasks that cannot be executed in parallel). A task package is an abstract concept. A task package can contain one or more to-do tasks that can be executed in parallel. The tasks in a task package containing multiple to-do tasks that can be executed in parallel can be executed in parallel; task packages are executed serially. The RPA capability layer contains a series of RPA interfaces, which are used to receive specific tax filing tasks and perform execution and result return.

[0060] In this embodiment, the to-do tasks with the same taxpayer ID number are extracted in the same batch, which avoids the situation where different taxpayer ID numbers of taxpayers log in simultaneously and squeeze each other out. The parallel tasks are placed in a task package and executed in parallel, thereby improving the processing efficiency. In addition, the concept of task package is proposed, making the whole 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 further include a login service layer. The specific design of the glue layer sending the task package to the RPA capability layer is as follows: the glue layer calls the login service layer to obtain the login Cookie for each task package; the to-do tasks in each task package carry the login Cookie and call the RPA capability layer.

[0062] The glue layer calls the unified login service interface according to the login information of the to-do tasks in the task package to obtain the login Cookie, and injects the Cookie into the browser tax bureau page to log in to the e-tax bureau. The login service layer is specifically used to call the service interface, input relevant information such as account, password, and taxpayer ID number, and the interface will return the login Cookie. As Figure 2 shown, it is a schematic diagram of the task package carrying the login Cookie calling the RPA capability layer provided by the embodiment of the present invention.

[0063] This embodiment uses the Cookie to log in to the e-tax bureau, shortening the login time and reducing the consumption of text messages.

[0064] In at least one embodiment of the present application, the method further includes: the glue layer receives a maintenance instruction for maintaining the parallel configuration table, and maintains the task types and tax types of the tax filing tasks in the parallel configuration table based on the maintenance instruction. The tax filing tasks will change over time, such as name, quantity, etc. Whether the tax filing tasks 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 filing tasks. The maintenance instruction can be automatically triggered by the system, and the parallel configuration table is maintained according to the preset rules, or when maintenance is required, the maintenance instruction gives a reminder and relevant maintenance personnel perform the maintenance. The maintenance of the parallel configuration table helps to adapt to various tax filing tasks and changes in tax filing tasks, thereby enhancing the system availability.

[0065] In at least one embodiment of the present application, in order to reduce the waiting time, the design of extracting the to-do tasks with the same taxpayer ID number in each taxpayer queue is: extracting the to-do tasks with the same taxpayer ID number and not exceeding the preset scheduling number in each taxpayer queue.

[0066] The preset scheduling number can be set according to specific situations (such as the tax filer, the number of tax filing tasks, etc.). For example, if the tax filer 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 more tax filers and / or pending tasks, a certain percentage (such as 90%, 85%, 80%, etc.) of the preset scheduling number of pending tasks can be extracted each time, and when there are fewer tax filers and / or pending tasks, the preset scheduling number of pending tasks can be extracted each time. By setting the preset scheduling number in this embodiment, long waiting times are avoided and the processing efficiency is improved. As Figure 3 shown, it is a schematic diagram of batch task creation in the case of exceeding the preset scheduling number provided by the 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 situations (such as the tax filer, the number of tax filing tasks, etc.), for example, 40 seconds. If the RPA capability layer does not execute all the pending tasks included in the task package within the preset execution time and returns the execution result, the uncompleted pending tasks can be left in the task package and continue to be executed when the same tax number tasks of the same tax filer are extracted next time, or the execution status of the tax filing tasks of the tax filer corresponding to the uncompleted pending tasks in the middle-level subsystem can be set to uncompleted and wait to be extracted next time. Due to unreasonable task execution settings (such as the preset scheduling number) or unexpected situations (such as unstable network, congestion, etc.), long waiting times may occur. This embodiment can avoid long waiting times, thus bringing a better user experience.

[0069] In at least one embodiment of the present application, the pending tasks are declaration tasks, collection tasks, receipt tasks, deduction tasks or declaration data download tasks. Declaration tasks, collection tasks, receipt tasks, deduction tasks and declaration data download tasks are task types divided in the tax filing system according to the business. The collection tasks can be further divided into historical data collection, pre-filled data collection, taxpayer basic information collection and identification information collection. The receipt tasks can be divided into declaration receipts and deduction receipts. The declaration data download tasks can be divided into tax return downloads and tax payment certificate downloads. The task types of the pending tasks can be maintained automatically or manually according to needs.

[0070] In at least one embodiment of the present application, in order to shorten the processing time and improve the processing efficiency, settings can be made for the glue layer, as well as the scheduling between the glue layer and the middle platform subsystem, and between the glue layer and the RPA capability layer: 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; asynchronous calls are set between the middle platform subsystem and the glue layer, and between the glue layer and the RPA capability layer.

[0071] As Figure 4 shown, it is a schematic diagram of the logical structure of the glue layer, the middle platform subsystem, and the RPA capability layer provided by an embodiment of the present invention. The glue layer can be implemented using two Tencent Cloud functions. One task_create cloud function is triggered using an http interface to receive batch tasks sent by the middle platform and distribute 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.

[0072] Asynchronous calls are made between the middle platform 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 individual tasks.

[0073] An individual task is sent from the middle platform to the task_create cloud function of the glue layer. The tasks_create cloud function arranges the tasks into the form of task packages and distributes them to a certain cloud function of the RPA capability layer. After the cloud function finishes executing the tasks, it delivers the execution results to Ckafka. The tasks_callback cloud function of the glue layer, as a consumer of Ckafka, pushes the task execution results to the middle platform.

[0074] This embodiment realizes the glue layer through cloud functions and conducts scheduling design between the glue layer and the middle platform subsystem, and between the glue layer and the RPA capability layer, achieving a reduction in processing time and an improvement in processing efficiency.

[0075] Next, the RPA scheduling method of the above tax filing system will be explained by way of example. As Figure 5 shown, it is a schematic diagram of RPA scheduling of the example tax filing system provided by an embodiment of the present invention.

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

[0077] There are currently 5 tax number A tasks in the middle platform subsystem (including 4 parallel pending tasks), 4 tax number B tasks (including 2 parallel pending tasks), and 3 tax number C tasks (including 2 parallel pending tasks). The 5 tax number A tasks and 4 tax number B tasks are in the queue of taxpayer Zhang San, with the 5 tax number A tasks in the front of the queue and the 4 tax number B tasks in the back of the queue. The 3 tax number C tasks are in the queue of taxpayer Li Si. The middle platform subsystem simultaneously forms batch 1 with 5 tax number A tasks and batch 2 with 3 tax number C tasks and sends them to the glue layer.

[0078] For the tasks in batch 1, the glue layer arranges the pending tasks in them into a multi-task task package carrying 2 parallel pending tasks and a single-task task package carrying 1 non-parallel pending task, and carries the cookie to call the RPA capability layer. The number of tasks in the multi-task task package is settable, and this example only takes carrying two tasks as an example for illustration.

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

[0080] The execution result of each pending task in the RPA capability layer will be returned to the middle platform subsystem through the glue layer respectively.

[0081] This application also provides an RPA scheduling device for a tax filing system corresponding to the above RPA scheduling method.

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

[0083] A taxpayer queue unit 610, configured to instruct the middle platform subsystem to create taxpayer queues corresponding to taxpayers one by one; and after a preset time interval, respectively extract the pending tasks with the same tax number in each taxpayer queue to obtain batch tasks corresponding to taxpayers one by one, and send the batch tasks to the glue layer;

[0084] A task package unit 620, configured to instruct the glue layer to create task packages corresponding to taxpayers one by one based on a preset parallel configuration table; wherein each task package includes one or more parallel pending tasks or one non-parallel pending task;

[0085] A task execution unit 630, configured to instruct the glue layer to send the task packages to the RPA capability layer, so that the pending tasks in each task package call the RPA capability layer;

[0086] The execution result return unit 640 is used to indicate that the glue layer receives the execution result returned by the RPA capability layer and returns the execution result to the middle platform subsystem.

[0087] The tax filer is the account for logging in to the tax bureau, which is a natural person and can be one or more. Each tax filer queue contains one or more to-do tasks corresponding to the tax numbers of the corresponding tax filer. The types of tax filer queues created can include ordinary queues, circular queues, linked queues, priority queues, concurrent queues, and task queues, which can be selected according to needs. The preset time interval can be set according to the number of tax filers and / or the number of to-do tasks (for example, 1 minute). The glue layer is a logical layer that plays the role of gluing the middle platform subsystem and the RPA capability layer, responsible for task orchestration and scheduling, and includes cloud functions, middleware, databases, etc. A cloud function is a serverless computing service that allows developers to write and run code on the cloud platform without managing the server or runtime environment. 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 lies in its elastic scaling ability, which can automatically adjust resources according to the actual usage situation, thereby optimizing costs and performance. The parallel configuration table is pre-configured and stored in the glue layer and is used to divide the task types of to-do tasks (i.e., tasks that can be executed in parallel and tasks that cannot be executed in parallel). A task package is an abstract concept. A task package can contain one or more to-do tasks that can be executed in parallel. The tasks in a task package containing multiple to-do tasks that can be executed in parallel can be executed in parallel; task packages are executed serially. The RPA capability layer contains a series of RPA interfaces for receiving specific tax filing tasks and performing execution and result return.

[0088] In the above device, the tax filer queue unit 610 extracts to-do tasks with the same tax number of the tax filer in the same batch, avoiding different tax numbers of the tax filer from logging in simultaneously and squeezing each other out. The task package unit 620 places parallel tasks in a task package for parallel execution, thereby improving the processing efficiency. In addition, the concept of task packages is proposed, making 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 filing system is designed to further include a login service layer. The task execution unit 630 is specifically used for: instructing the glue layer to call the login service layer to obtain the login Cookie for each task package; instructing the to-do tasks in each task package to carry the login Cookie and call the RPA capability layer.

[0090] The glue layer calls the unified login service interface according to the login information of the to-do tasks in the task package to obtain the login cookie, and injects the cookie into the browser tax bureau page to log in to the e-tax bureau. The login service layer is specifically used to call the service interface, pass in relevant information such as account, password, and tax number, and the interface will return the login cookie.

[0091] This embodiment uses cookies to log in to the e-tax bureau, shortening the login time and reducing the consumption of text messages.

[0092] In at least one embodiment of the present application, the glue layer further includes a parallel configuration table maintenance module, which is used to: receive a maintenance instruction for maintaining the parallel configuration table, and maintain the task types and tax types of the tax filing tasks in the parallel configuration table based on the maintenance instruction. The tax filing tasks change over time, such as name, quantity, etc., and whether the tax filing tasks 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 filing tasks. The maintenance instruction can be automatically triggered by the system and the parallel configuration table is maintained according to preset rules, or when maintenance is required, a reminder is sent by the maintenance instruction and the relevant maintenance personnel perform the maintenance. The maintenance of the parallel configuration table helps to adapt to various tax filing tasks and changes in tax filing tasks, thereby enhancing system availability.

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

[0094] The preset scheduling number can be set according to specific situations (such as taxpayers, the number of tax filing tasks, etc.). For example, the taxpayer is Zhang San, and there are 120 to-do tasks under his tax number 001. When the preset scheduling number is 100, no more than 100 to-do tasks are extracted each time; for example, when there are more taxpayers and / or to-do tasks, a certain percentage (such as 90%, 85%, 80%, etc.) of the preset scheduling number of to-do tasks can be extracted each time, and when there are fewer taxpayers and / or to-do tasks, the preset scheduling number of to-do tasks can be extracted each time. This embodiment avoids long waiting times 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 return unit 640 can be designed to specifically be used for: within the preset execution time, the RPA capability layer finishes executing all the to-do tasks included in the task package and returns the execution result; or within the preset execution time, the RPA capability layer does not finish executing all the to-do 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 tax filer, the number of tax filing tasks, etc.), for example, 40 seconds. If the RPA capability layer fails to execute all the to-do tasks included in the task package within the preset execution time, after returning the execution result, the uncompleted to-do tasks can be left in the task package to continue execution when the same tax number task of the same tax filer is extracted next time, or the execution status of the tax filing tasks of the tax filer corresponding to the uncompleted to-do tasks in the middle platform subsystem can be set to uncompleted and wait to be extracted next time. Due to unreasonable task execution settings (such as the preset scheduling number) or unexpected situations (such as unstable network, congestion, etc.), it may lead to a long waiting time. This embodiment can avoid a long waiting time, thus bringing a better user experience.

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

[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, and 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 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 set between the middle platform subsystem and the glue layer, and between the glue layer and the RPA capability layer.

[0099] The glue layer can be implemented using two Tencent Cloud functions. A task_create cloud function is triggered using an 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 result 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 a server, and only need to write function code and deploy it to the cloud to be called on the applet side.

[0100] Asynchronous calls are made between the middle platform 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 individual tasks.

[0101] A single task is sent by the middleware to the task_create cloud function in the glue layer. The tasks_create cloud function arranges the task into the form of a task package and sends it to a certain cloud function in the RPA capability layer. After the cloud function finishes executing the task, it delivers the execution result to Ckafka. The tasks_callback cloud function in the glue layer, as the consumer of Ckafka, pushes the task execution result to the middleware. The message queue CKafka (Cloud Kafka) is based on the open-source Apache Kafka message queue engine and provides a message queue service with high throughput performance and high scalability.

[0102] This embodiment realizes the glue layer through cloud functions and conducts scheduling design between the glue layer and the middleware subsystem, as well as between the glue layer and the RPA capability layer, achieving a reduction in processing time and an improvement in processing efficiency.

[0103] As Figure 7 shown, a schematic structural diagram of the RPA scheduling device of the tax filing system provided by the 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 can be a central processing unit (CPU) or other forms of processing units with data processing capabilities and / or instruction execution capabilities, and can control other components in the RPA scheduling device 70 of the tax filing system to perform desired functions.

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

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

[0107] Of course, for simplicity, Figure 7Only some of the components related to this application in the RPA scheduling device 70 of the tax filing system are shown, and components such as buses, input / output interfaces, etc. are omitted. In addition, according to specific application scenarios, the RPA scheduling device 70 of the tax filing system may further include any other appropriate components.

[0108] Based on the embodiments of this application, this application also provides a computer-readable storage medium, wherein the computer instructions are used to cause a computer to execute the steps in the RPA scheduling method of the foregoing technical solution.

[0109] Based on the embodiments of this application, this application also provides a processor, and the foregoing processor is used to run a program, wherein when the program runs, it executes the steps in the RPA scheduling method of the foregoing technical solution.

[0110] Any process or method description shown in the flowchart or described in other ways herein can be understood to represent a module, segment, or portion of code including one or more executable instructions for implementing a customized logic function or process, and the scope of the preferred embodiments of the present invention includes additional implementations, where the functions may be executed in a substantially simultaneous manner or in a reverse order according to the functions involved, rather than in the order shown or discussed, which should be understood by those skilled in the art to which the embodiments of the present invention belong.

[0111] The logic and / or steps represented in the flowchart or described in other ways herein, for example, can be considered as an ordered list of executable instructions for implementing a logical function, and can be specifically implemented in any computer-readable medium for use by an instruction execution system, apparatus, or device (such as a computer-based system, a system including a processor, or other systems that can fetch and execute instructions from the instruction execution system, apparatus, or device), or in combination with these instruction execution systems, apparatus, or devices. For the purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. More specific examples (non-exhaustive list) of the computer-readable medium include the following: an electrical connection portion having one or more wirings (electronic device), a portable computer diskette (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). In addition, the computer-readable medium can even be paper or other suitable media on which the program can be printed, because the program can be obtained electronically, for example, by optically scanning the paper or other media, followed by editing, interpretation, or other appropriate processing as 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 embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system.

[0113] Regarding the above description of the disclosed embodiments, the features described in each embodiment of this specification can be replaced or combined with each other, enabling those skilled in the art to implement or use this application. The above is only a preferred embodiment of the present invention and does not impose any formal limitation on the present invention. Although the present invention has been disclosed above with preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art can make many possible changes and modifications to the technical solution of the present invention, or modify it into an equivalent embodiment with equivalent changes, without departing from the scope of the technical solution of the present invention. Therefore, any simple modification, equivalent change, and modification made to the above embodiments based on the technical essence of the present invention without departing from the content of the technical solution of the present invention still fall 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; The tax declaration system further 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; 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; 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.

2. According to the RPA scheduling method described in claim 1, it is 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.

3. The RPA scheduling method according to claim 2, 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 the pending tasks contained 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 contained in the task package and returns the execution result.

4. 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.

5. 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, 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; The tax declaration system further 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; 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; 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.

6. 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 4.

7. 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 4.

Images