Method, device and equipment for displaying repayment operation progress, medium and program product

Abstract

The invention provides an account supplementing operation progress display method and device, equipment, a medium and a program product, and can be applied to the field of information technology or financial science and technology. The method comprises the steps that task level information of multiple account supplementing jobs is acquired, the task level information comprises n levels divided by the multiple account supplementing jobs and m account supplementing tasks included in each level, and n and m are positive integers larger than or equal to 0; historical data and account supplementing operation data of the account supplementing operation are obtained, the historical data comprise historical completion durations corresponding to the n hierarchies, the account supplementing operation data comprise the execution state of the account supplementing task, and the execution state represents whether the account supplementing task is executed or not; determining a hierarchy weight of the hierarchy based on the historical completion duration; determining the repayment job progress based on the hierarchical weight and the repayment job data; and sending the repayment operation progress to a terminal display device, so that the terminal display device displays the repayment operation progress.

Description

Technical Field

[0001] The present disclosure relates to the field of information technology or financial technology, and more specifically to a method, device, equipment, medium and program product for displaying the progress of an account replenishment operation. Background Art

[0002] The existing method for displaying the progress of account replenishment operations requires manual review of the account replenishment operations and the positioning of the account replenishment progress by comparing the account replenishment process diagram. The automated method for displaying the progress of account replenishment operations only roughly estimates the progress based on the linear ordering relationship of the operations in the process, and does not take into account the problem of inconsistent completion time of the sub-operations in each account replenishment operation, resulting in low accuracy of the progress estimate display. Summary of the invention

[0003] In view of the above problems, the present disclosure provides a method, device, equipment, medium and program product for displaying the progress of an account replenishment operation.

[0004] According to a first aspect of the present disclosure, a method for displaying progress of a payment replenishment operation is provided, comprising: obtaining task level information of multiple payment replenishment operations, wherein the task level information comprises: n levels into which the multiple payment replenishment operations are divided, and m payment replenishment tasks included in each level, where n and m are both positive integers greater than or equal to 0; obtaining historical data and payment replenishment operation data of the payment replenishment operations, wherein the historical data comprises historical completion times corresponding to the n levels, and the payment replenishment operation data comprises execution status of the payment replenishment tasks, wherein the execution status represents whether the payment replenishment tasks are completed; determining level weights of the levels based on the historical completion times; determining payment replenishment operation progress based on the level weights and the payment replenishment operation data; and sending the payment replenishment operation progress to a terminal display device, so that the payment replenishment operation progress is displayed through the terminal display device.

[0005] According to an embodiment of the present disclosure, the above-mentioned determination of the progress of the account replenishment operation based on the above-mentioned level weight and the above-mentioned account replenishment operation data includes: determining the execution level and the execution progress of the above-mentioned execution level based on the above-mentioned account replenishment operation data; determining the progress of the account replenishment operation based on the above-mentioned execution progress and the level weight corresponding to the above-mentioned execution level.

[0006] According to an embodiment of the present disclosure, the n levels and the m account replenishment tasks are stored in order, and the determination of the execution level and the execution progress of the execution level based on the account replenishment operation data includes: searching for the execution account replenishment task from the account replenishment operation data, the execution account replenishment task being the first account replenishment task in the account replenishment operation whose execution status is incomplete; and determining the execution level and the execution progress corresponding to the execution task based on the task level information of the execution task.

[0007] According to an embodiment of the present disclosure, the above-mentioned determination of the level weights of the above-mentioned levels based on the above-mentioned historical completion times includes performing the following operations for any i-th level: determining the total historical completion times corresponding to all n levels; when the i-th level is a non-concurrent level, determining the first historical completion time corresponding to the first i levels; and calculating the level weights of the above-mentioned first i levels based on the above-mentioned first historical completion time and the above-mentioned total historical completion time.

[0008] According to an embodiment of the present disclosure, the above-mentioned task level information also includes the correspondence between the account replenishment task and the level identifier; the above-mentioned task level information based on the above-mentioned execution task determines the execution level corresponding to the above-mentioned execution task and the above-mentioned execution progress, including: determining the execution level identifier based on the above-mentioned correspondence and the above-mentioned execution task; based on the above-mentioned execution level identifier, searching from the above-mentioned task level information to obtain the number of completed tasks and the number of uncompleted tasks corresponding to the above-mentioned execution level; determining the execution progress of the above-mentioned level based on the number of completed tasks and the number of uncompleted tasks.

[0009] According to an embodiment of the present disclosure, the above method also includes: when the above i-th level is a concurrent level, determining the second historical completion time corresponding to the first i-1 levels; and calculating the level weights of the above first i-1 levels based on the above second historical completion time and the above total historical completion time.

[0010] According to an embodiment of the present disclosure, determining the progress of the account replenishment operation based on the level weights and the account replenishment operation data includes: when the i-th level is a non-concurrent level, using the weights of the first i levels as the progress of the account replenishment operation.

[0011] A second aspect of the present disclosure provides a progress display device for a replenishment operation, comprising: a task level acquisition module, used to acquire task level information of multiple replenishment operations, wherein the task level information includes: n levels into which the multiple replenishment operations are divided, and m replenishment tasks included in each of the levels, where n and m are both positive integers greater than or equal to 0; a historical data acquisition module, used to acquire historical data of the replenishment operations and replenishment operation data, wherein the historical data includes historical completion times corresponding to the n levels, and the replenishment operation data includes execution status of the replenishment tasks, wherein the execution status indicates whether the replenishment tasks have been completed; a level weight determination module, used to determine the level weight of the level based on the historical completion time; a replenishment operation progress determination module, used to determine the replenishment operation progress based on the level weight and the replenishment operation data; and a sending module, used to send the replenishment operation progress to a terminal display device, so that the replenishment operation progress is displayed through the terminal display device.

[0012] According to an embodiment of the present disclosure, the above-mentioned account replenishment operation progress determination module includes: an execution level determination submodule, which is used to determine the execution level and the execution progress of the above-mentioned execution level based on the above-mentioned account replenishment operation data; and a job progress determination submodule, which is used to determine the account replenishment operation progress based on the above-mentioned execution progress and the level weight corresponding to the above-mentioned execution level.

[0013] According to an embodiment of the present disclosure, the above-mentioned n levels and the above-mentioned m account replenishment tasks are stored in order, and the above-mentioned execution level determination submodule includes: an execution account replenishment task determination unit, which is used to search and obtain the execution account replenishment task from the above-mentioned account replenishment job data, and the above-mentioned execution account replenishment task is the first account replenishment task in the above-mentioned account replenishment job whose execution status is incomplete; an execution progress determination unit, which is used to determine the execution level and the above-mentioned execution progress corresponding to the above-mentioned execution task based on the task level information of the above-mentioned execution task.

[0014] According to an embodiment of the present disclosure, the above-mentioned level weight determination module includes: a total historical completion time determination submodule, which is used to determine the total historical completion time corresponding to all n levels; a first historical completion time determination submodule, which is used to determine the first historical completion time corresponding to the first i levels when the above-mentioned i-th level is a non-concurrent level; a level weight determination submodule, which is used to calculate the level weights of the above-mentioned first i levels based on the above-mentioned first historical completion time and the above-mentioned total historical completion time.

[0015] According to an embodiment of the present disclosure, the above-mentioned task level information also includes the correspondence between the account-making tasks and the level identifier, and the above-mentioned execution progress determination unit includes: a level identifier determination subunit, which is used to determine the execution level identifier based on the above-mentioned correspondence and the above-mentioned execution tasks; a completed task quantity determination subunit, which is used to find out the number of completed tasks and the number of uncompleted tasks corresponding to the above-mentioned execution level from the above-mentioned task level information based on the above-mentioned execution level identifier; a level execution progress determination subunit, which is used to determine the execution progress of the above-mentioned level based on the above-mentioned number of completed tasks and the above-mentioned number of uncompleted tasks.

[0016] According to an embodiment of the present disclosure, the above-mentioned hierarchical weight determination module also includes: a second historical completion time determination sub-module, which is used to determine the second historical completion time corresponding to the first i-1 levels when the above-mentioned i-th level is a concurrent level; a second hierarchical weight determination sub-module, which is used to calculate the hierarchical weights of the above-mentioned first i-1 levels based on the above-mentioned second historical completion time and the above-mentioned total historical completion time.

[0017] According to an embodiment of the present disclosure, the above-mentioned account replenishment operation progress determination module includes: a determination submodule, which is used to use the weights of the first i levels as the account replenishment operation progress when the above-mentioned i-th level is a non-concurrent level.

[0018] A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the above method.

[0019] The fourth aspect of the present disclosure further provides a computer-readable storage medium having a computer program or instructions stored thereon, which implements the steps of the above method when the above computer program or instructions are executed by a processor.

[0020] The fifth aspect of the present disclosure further provides a computer program product, including a computer program or instructions, which implement the steps of the above method when the above computer program or instructions are executed by a processor.

[0021] According to the embodiments of the present disclosure, the account replenishment operation is divided into vertical levels, and each level is divided into multiple tasks horizontally, the task progress of the account replenishment operation in the horizontal and vertical depth is fully considered, and the level weights of each vertical level are determined by the historical completion time of the account replenishment operation. The progress of the account replenishment operation is further determined by the level weights and the account replenishment operation data, and sent to the terminal display device to ensure that the progress of the account replenishment operation is accurately displayed. At the same time, when the progress stagnates, the abnormal points of the account replenishment operation can be quickly located. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The above contents and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0023] Figure 1 A diagram schematically shows an application scenario of a method and device for displaying progress of an account replenishment operation according to an embodiment of the present disclosure;

[0024] Figure 2 A flowchart of a method for displaying progress of an account replenishment operation according to an embodiment of the present disclosure is schematically shown;

[0025] Figure 3 The following schematically shows a task level division diagram according to an embodiment of the present disclosure;

[0026] Figure 4 A schematic diagram of a general account replenishment progress total device according to an embodiment of the present disclosure is schematically shown;

[0027] Figure 5 A schematic diagram of a structural block diagram of a device for displaying progress of a replenishment operation according to an embodiment of the present disclosure is shown;

[0028] Figure 6 A block diagram of an electronic device suitable for implementing a method for displaying progress of an account replenishment operation according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0029] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0030] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0031] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0032] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0033] It should be noted that the method, device, equipment, medium and program product for displaying the progress of account replenishment operations disclosed in the present invention can be used in the field of financial technology, and can also be used in any field other than the field of financial technology. The present invention does not limit the application field of the method, device, equipment, medium and program product for displaying the progress of account replenishment operations.

[0034] In the technical solution of the present disclosure, the user information (including but not limited to user personal information, user image information, user device information, such as location information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0035] In the scenario of using personal information for automated decision-making, the methods, devices, and systems provided by the embodiments of the present disclosure provide users with corresponding operation portals for users to choose to agree or reject the automated decision-making results; if the user chooses to reject, the expert decision-making process will be entered. The expression "automated decision-making" here refers to the activity of automatically analyzing and evaluating a person's behavioral habits, interests and hobbies, or economic, health, credit status, etc. through computer programs, and making decisions. The expression "expert decision-making" here refers to the activity of making decisions by people who specialize in a certain field, have specialized experience, knowledge and skills, and have reached a certain level of professionalism.

[0036] The existing method for displaying the progress of account replenishment operations requires manual review of the account replenishment operations and the positioning of the account replenishment progress by comparing the account replenishment process diagram. In the automated account replenishment operation progress display method, there are different types of recovery sub-operations with large differences in their running time. The overall process progress cannot be accurately estimated only by the linear sorting relationship of the operations in the process. In addition, only the start and end operations are often captured as the key elements of the progress display. In the case of high host concurrency, the progress of the account replenishment operation cannot be accurately predicted.

[0037] In view of this, an embodiment of the present disclosure provides a method for displaying the progress of a payment replenishment operation, which obtains task level information of multiple payment replenishment operations, wherein the task level information includes: n levels into which the multiple payment replenishment operations are divided, and m payment replenishment tasks included in each level, where n and m are both positive integers greater than or equal to 0; historical data and payment replenishment operation data of the payment replenishment operation are obtained, the historical data includes historical completion times corresponding to the n levels, and the payment replenishment operation data includes execution status of the payment replenishment task, and the execution status represents whether the payment replenishment task has been completed; the level weight of the level is determined based on the historical completion time; the progress of the payment replenishment operation is determined based on the level weight and the payment replenishment operation data; and the progress of the payment replenishment operation is sent to a terminal display device so that the progress of the payment replenishment operation is displayed through the terminal display device.

[0038] Figure 1 The application scenario diagram of the method and device for displaying the progress of account replenishment operations according to an embodiment of the present disclosure is schematically shown.

[0039] like Figure 1 As shown, the application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, a first server 105, and a second server 106. The network 104 is used to provide a medium for a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, the first server 105, and the second server 106. The network 104 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0040] The user may use the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the first server 105 through the network 104 to receive or send messages, etc. Various communication client applications may be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only for example).

[0041] The first terminal device 101, the second terminal device 102, and the third terminal device 103 may be various electronic devices having display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0042] The first server 105 and the second server 106 may be servers that provide various services, such as a background management server (only as an example) that provides support for websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0043] According to an embodiment of the present disclosure, the second server 106 may be a server that provides services for the reconciliation module, the account replenishment module, and the reporting module. The second server 106 forwards the task execution progress in the reconciliation module, the account replenishment module, and the reporting module to the first server 105 through the network 104, and the first server 105 stores the task execution progress in the database.

[0044] It should be noted that the method for displaying the progress of the account replenishment operation provided in the embodiment of the present disclosure can generally be executed by the first server 105. Accordingly, the device for displaying the progress of the account replenishment operation provided in the embodiment of the present disclosure can generally be set in the first server 105. The method for displaying the progress of the account replenishment operation provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the first server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and / or the first server 105. Accordingly, the device for displaying the progress of the account replenishment operation provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the first server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and / or the first server 105.

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

[0046] The following will be based on Figure 1 The scene described by Figure 2~Figure 4 The method for displaying the progress of an account replenishment operation in a disclosed embodiment is described in detail.

[0047] Figure 2 The flowchart of the method for displaying the progress of an account replenishment operation according to an embodiment of the present disclosure is schematically shown.

[0048] like Figure 2 As shown, the method for displaying the progress of the account replenishment operation in this embodiment includes operations S210 to S250.

[0049] In operation S210 , task level information of a plurality of account replenishment operations is obtained.

[0050] The task level information includes: n levels into which the multiple account replenishment operations are divided, and m account replenishment tasks included in each level, where n and m are both positive integers greater than or equal to 0.

[0051] Figure 3 The diagram schematically shows a task hierarchy division diagram according to an embodiment of the present disclosure.

[0052] like Figure 3 As shown, the account replenishment operation can be composed of a reconciliation module, an account replenishment module, and a reporting module, wherein the reconciliation module can perform reconciliation operations on levels B, C, and D, the account replenishment module can perform account replenishment operations on level F, and the reporting module can generate reports for level H. The overall account replenishment operation is divided into 10 levels [A, B, C, D, E, F, G, H, I, J], wherein levels B, C, D, F, and H can all be divided into multiple account replenishment tasks. For example, level B can include tasks B0, B1, B2, and other tasks.

[0053] According to the embodiment of the present disclosure, a job execution status sending submodule may be embedded in each module in the account replenishment job, so that the job execution status is sent to the server database for storage.

[0054] In operation S220, historical data of the account replenishment operation and account replenishment operation data are acquired.

[0055] The historical data includes the historical completion time corresponding to n levels, and the account replenishment operation data includes the execution status of the account replenishment task, and the execution status indicates whether the account replenishment task has been completed.

[0056] The following Table 1 schematically shows a progress table of an account replenishment operation according to an embodiment of the present disclosure.

[0057] Table 1

[0058]

[0059] As shown in Table 1, for concurrent tasks, the longest estimated execution time corresponding to the tasks in the level can be used as the historical completion time of the level. For example, the tasks JOB-B0 and JOB-B1 corresponding to level B are concurrent tasks, and the estimated execution time t B0 and t B1 The duration of t B0 In the case of a longer duration, t B0 As the historical completion time of level B. For non-concurrent tasks, the historical completion time of the level can be determined based on the estimated execution time of all tasks in the level.

[0060] According to an embodiment of the present disclosure, the execution status in the above Table 1 includes three values ​​of "0", "1" and "2", where "0" indicates that the account replenishment task is to be executed, "1" indicates that the account replenishment task is executed successfully, and "2" indicates that the account replenishment task is abnormally interrupted.

[0061] According to an embodiment of the present disclosure, when there are concurrent tasks, the subsequent task can only be executed after all concurrent tasks are completed. For example, for JOB-B0 and JOB-B1 in Table 1 above, the subsequent task JOB-C1 can only be started after both tasks are completed.

[0062] In operation S230 , the level weight of the level is determined based on the historical completion duration.

[0063] According to the embodiments of the present disclosure, the historical weight of each level can be obtained by calculating the historical completion time and the total historical completion time of each level, or the weighted average of multiple historical completion times can be taken, and then the level weight of the level can be determined based on the averaged data. The present disclosure does not impose any restrictions on this.

[0064] In operation S240 , the progress of the account replenishment operation is determined based on the level weight and the account replenishment operation data.

[0065] In operation S250, the progress of the account replenishment operation is sent to the terminal display device, so that the progress of the account replenishment operation is displayed through the terminal display device.

[0066] According to an embodiment of the present disclosure, after determining the progress of the account replenishment operation, the progress of the account replenishment operation and the corresponding file sequence (for example, a data table) can be loaded as a host sequence file, the progress of the account replenishment operation is written into the sequence storage file in real time, and the aforementioned host sequence file is pushed to a terminal display device via FTP (File Transfer Protocol). The file display device can be, for example, a display data screen. The terminal display device parses the sequence storage file according to a preset file structure and displays it on the terminal display device.

[0067] According to the embodiments of the present disclosure, the account replenishment operation is divided into vertical levels, and each level is divided into multiple tasks horizontally, the task progress of the account replenishment operation in the horizontal and vertical depth is fully considered, and the level weights of each vertical level are determined by the historical completion time of the account replenishment operation. The progress of the account replenishment operation is further determined by the level weights and the account replenishment operation data, and sent to the terminal display device to ensure that the progress of the account replenishment operation is accurately displayed. At the same time, when the progress stagnates, the abnormal points of the account replenishment operation can be quickly located.

[0068] According to an embodiment of the present disclosure, the above-mentioned determination of the progress of the account replenishment operation based on the level weight and the account replenishment operation data includes: determining the execution level and the execution progress of the execution level based on the account replenishment operation data; determining the progress of the account replenishment operation based on the execution progress and the level weight corresponding to the execution level.

[0069] According to an embodiment of the present disclosure, n levels and m account replenishment tasks are stored in order, and the execution level and the execution progress of the execution level are determined based on the account replenishment job data, including: searching and obtaining the execution account replenishment task from the account replenishment job data, the execution account replenishment task being the first account replenishment task in the account replenishment job whose execution status is incomplete; and determining the execution level and execution progress corresponding to the execution task based on the task level information of the execution task.

[0070] For example, as shown in Table 1 above, the first task with an unfinished execution status can be found in the table as "JOB-D1", and the execution account replenishment task can be determined to be "JOB-D1". Further, the execution level can be determined to be "D" through a database query statement.

[0071] According to the embodiment of the present disclosure, the task identifier of the account replenishment task corresponding to the current level can be searched in the database, and the execution progress can be determined according to the label in the task identifier.

[0072] For example, for level D, the database stores account replenishment tasks identified as "JOB-D1", "JOB-D2", "JOB-D3" and "JOB-D4". At this time, the account replenishment task to be executed is "JOB-D1". Since the account replenishment tasks are stored in order, it can be determined that the execution progress is 25%.

[0073] According to the embodiments of the present disclosure, by orderly storing levels and account replenishment tasks, the execution of account replenishment tasks, execution levels and execution progress of execution levels can be determined more quickly, reducing the data table query time and improving the efficiency of determining the progress of account replenishment operations. On the other hand, by determining the progress of account replenishment operations through execution progress and level weights, the actual progress of account replenishment operations can be accurately determined at a smaller granularity.

[0074] According to an embodiment of the present disclosure, the above-mentioned task level information also includes the correspondence between the account replenishment task and the level identifier. Based on the task level information of the execution task, the execution level and execution progress corresponding to the execution task are determined, including: determining the execution level identifier based on the correspondence and the execution task; based on the execution level identifier, searching from the task level information to obtain the number of completed tasks and the number of uncompleted tasks corresponding to the execution level; and determining the execution progress of the level based on the number of completed tasks and the number of uncompleted tasks.

[0075] According to an embodiment of the present disclosure, after determining the execution level, the number of completed tasks and the number of uncompleted tasks corresponding to the execution level can be obtained through a database query statement, and the execution progress of the level can be calculated.

[0076] For example, when it is determined that the execution level is "D", the number of unfinished tasks corresponding to the execution level D can be queried through the database query statement "SELECT COUNT (STATUS = '0') FROM JOB_STATUS_TAB WHERE MODULE = "D"", where 'STATUS' represents the execution status of the account replenishment task, 'JOB_STATUS_TAB' is the name of the account replenishment job data storage table, and 'MODULE' is the level.

[0077] Table 2 schematically shows a progress chart of the account replenishment operation according to an embodiment of the present disclosure.

[0078] Table 2

[0079]

[0080] As shown in Table 2, the progress percentage is the execution progress corresponding to the execution level.

[0081] According to an embodiment of the present disclosure, the above-mentioned determination of the level weight of the level based on the historical completion time includes performing the following operations for any i-th level: determining the total historical completion time corresponding to all n levels; when the i-th level is a non-concurrent level, determining the first historical completion time corresponding to the first i levels; and calculating the level weights of the first i levels based on the first historical completion time and the total historical completion time.

[0082] According to an embodiment of the present disclosure, the above method also includes: when the i-th level is a concurrent level, determining the second historical completion time corresponding to the first i-1 levels; and calculating the level weights of the first i-1 levels based on the second historical completion time and the total historical completion time.

[0083] According to the embodiment of the present disclosure, the total historical completion time corresponding to all n levels can be determined by the following formula (1).

[0084] (1)

[0085] Among them, T represents the total historical completion time, ti represents the historical completion time corresponding to the i-th level, and n represents the number of levels.

[0086] When the level is a non-concurrent level, the first historical completion time corresponding to the first i levels can be calculated using the following formula (2).

[0087] (2)

[0088] Among them, T 0 It represents the first historical completion time corresponding to the first i levels, and ti represents the historical completion time corresponding to the i-th level.

[0089] When the level is a concurrent level, the second historical completion time corresponding to the first i-1 levels can be calculated using the following formula (3).

[0090] (3)

[0091] Among them, T ’ It represents the second historical completion time corresponding to the first i-1 levels, and ti represents the historical completion time corresponding to the i-th level.

[0092] The level weights of the first i levels can be calculated using the following formula (4).

[0093] (4)

[0094] Among them, T 0 represents the first historical completion time corresponding to the first i levels, T represents the total historical completion time, K 0 Represents the level weight of the first i levels.

[0095] The level weights of the first i-1 levels can be calculated using the following formula (5).

[0096] (5)

[0097] Among them, T ’represents the second historical completion time corresponding to the first i-1 levels, T represents the total historical completion time, K ’ Represents the level weights of the first i-1 levels.

[0098] For example, when the first historical completion time corresponding to the first two levels is 10s, the second historical completion time corresponding to the first level is 5s, and the total historical completion time is 100s, the level weights of the first two levels are 0.1, and the level weight corresponding to the first level is 0.05.

[0099] According to an embodiment of the present disclosure, when the current level i is a non-concurrent level, the level weights of the previous i levels may be used as the progress of the account replenishment operation.

[0100] For example, for the second level of the non-concurrent level, the level weight corresponding to the first two levels is calculated to be 0.1, and 0.1 can be used as the progress of the account replenishment operation.

[0101] According to the embodiment of the present disclosure, when the level is a concurrent level, the progress of the account replenishment operation can be calculated by the following formula (6).

[0102] (6)

[0103] Among them, P represents the progress of the account replenishment operation, K' represents the level weight of the first i-1 levels, and C 0 It indicates the execution progress of the execution level, ti indicates the historical completion time corresponding to the ith level, and T indicates the total historical completion time.

[0104] For example, for the first i-1 levels, the level weight K' is 0.1, and the execution progress C 0 The data is 0.5, ti is 10s, T is 100s, and the progress of the account replenishment operation is 0.15.

[0105] According to the embodiments of the present disclosure, the weight is specifically determined by determining whether the execution levels are concurrent. In a non-concurrent state, the level weights of the first i levels are directly used as the progress of the account replenishment operation. In a concurrent state, the progress of the account replenishment operation is determined based on the level weights of the first i-1 levels, the level weights of the i-th level, and the execution progress of the i-th level. This takes into account the concurrency in the account replenishment operation and can accurately calculate the progress of the account replenishment operation.

[0106] Figure 4 The schematic diagram of the general account replenishment progress device according to an embodiment of the present disclosure is schematically shown.

[0107] like Figure 4As shown, operations S210~S220 can be executed by a job execution status sending device and a job execution status persistence device. The job execution status sending device is embedded in the tail of the key job of the account replenishment process, and the execution status is written into the job execution persistence device. The above operations S230~S240 can be executed by a process progress calculation and statistics device, and the above operation S250 can be executed by a progress result loading device and displayed through a progress result push and display device.

[0108] Based on the above-mentioned method for displaying the progress of a replenishment operation, the present disclosure also provides a device for displaying the progress of a replenishment operation. Figure 5 The device is described in detail.

[0109] Figure 5 The structural block diagram of the account replenishment operation progress display device according to an embodiment of the present disclosure is schematically shown.

[0110] like Figure 5 As shown, the account replenishment operation progress display device 500 of this embodiment includes a task level acquisition module 510, a historical data acquisition module 520, a level weight determination module 530, an account replenishment operation progress determination module 540 and a sending module 550.

[0111] The task level acquisition module 510 is used to acquire task level information of multiple account replenishment operations, wherein the task level information includes: n levels into which the multiple account replenishment operations are divided, and m account replenishment tasks included in each level, where n and m are both positive integers greater than or equal to 0. In one embodiment, the task level acquisition module 510 can be used to perform the operation S210 described above, which will not be described in detail herein.

[0112] The historical data acquisition module 520 is used to acquire historical data and account replenishment operation data of the account replenishment operation, the historical data includes the historical completion time corresponding to the n levels, and the account replenishment operation data includes the execution status of the account replenishment task, and the execution status represents whether the account replenishment task is completed. In one embodiment, the historical data acquisition module 520 can be used to perform the operation S220 described above, which will not be repeated here.

[0113] The level weight determination module 530 is used to determine the level weight of the level based on the historical completion time. In one embodiment, the level weight determination module 530 can be used to perform the operation S230 described above, which will not be repeated here.

[0114] The account replenishment operation progress determination module 540 is used to determine the account replenishment operation progress based on the level weight and the account replenishment operation data. In one embodiment, the account replenishment operation progress determination module 540 can be used to perform the operation S240 described above, which will not be repeated here.

[0115] The sending module 550 is used to send the progress of the account replenishment operation to the terminal display device, so that the progress of the account replenishment operation is displayed through the terminal display device. In one embodiment, the sending module 550 can be used to perform the operation S250 described above, which will not be repeated here.

[0116] According to an embodiment of the present disclosure, the above-mentioned account replenishment operation progress determination module includes: an execution level determination submodule, which is used to determine the execution level and the execution progress of the above-mentioned execution level based on the above-mentioned account replenishment operation data; and a job progress determination submodule, which is used to determine the account replenishment operation progress based on the above-mentioned execution progress and the level weight corresponding to the above-mentioned execution level.

[0117] According to an embodiment of the present disclosure, the above-mentioned n levels and the above-mentioned m account replenishment tasks are stored in order, and the above-mentioned execution level determination submodule includes: an execution account replenishment task determination unit, which is used to search and obtain the execution account replenishment task from the above-mentioned account replenishment job data, and the above-mentioned execution account replenishment task is the first account replenishment task in the above-mentioned account replenishment job whose execution status is incomplete; an execution progress determination unit, which is used to determine the execution level and the above-mentioned execution progress corresponding to the above-mentioned execution task based on the task level information of the above-mentioned execution task.

[0118] According to an embodiment of the present disclosure, the above-mentioned level weight determination module includes: a total historical completion time determination submodule, which is used to determine the total historical completion time corresponding to all n levels; a first historical completion time determination submodule, which is used to determine the first historical completion time corresponding to the first i levels when the above-mentioned i-th level is a non-concurrent level; a level weight determination submodule, which is used to calculate the level weights of the above-mentioned first i levels based on the above-mentioned first historical completion time and the above-mentioned total historical completion time.

[0119] According to an embodiment of the present disclosure, the above-mentioned task level information also includes the correspondence between the account replenishment task and the level identifier, and the above-mentioned execution progress determination unit includes: a level identifier determination subunit, used to determine the execution level identifier based on the above-mentioned correspondence and the above-mentioned execution task; a completed task quantity determination subunit, used to search from the above-mentioned task level information based on the above-mentioned execution level identifier to obtain the number of completed tasks and the number of uncompleted tasks corresponding to the above-mentioned execution level; a level execution progress determination subunit, used to determine the execution progress of the above-mentioned level based on the above-mentioned number of completed tasks and the above-mentioned number of uncompleted tasks.

[0120] According to an embodiment of the present disclosure, the above-mentioned hierarchical weight determination module also includes: a second historical completion time determination sub-module, which is used to determine the second historical completion time corresponding to the first i-1 levels when the above-mentioned i-th level is a concurrent level; a second hierarchical weight determination sub-module, which is used to calculate the hierarchical weights of the above-mentioned first i-1 levels based on the above-mentioned second historical completion time and the above-mentioned total historical completion time.

[0121] According to an embodiment of the present disclosure, the above-mentioned account replenishment operation progress determination module includes: a determination submodule, which is used to use the weights of the first i levels as the account replenishment operation progress when the above-mentioned i-th level is a non-concurrent level.

[0122] According to an embodiment of the present disclosure, any multiple modules among the task level acquisition module 510, the historical data acquisition module 520, the level weight determination module 530, the account replenishment operation progress determination module 540 and the sending module 550 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the task level acquisition module 510, the historical data acquisition module 520, the level weight determination module 530, the account replenishment operation progress determination module 540 and the sending module 550 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in an appropriate combination of any of them. Alternatively, at least one of the task level acquisition module 510, the historical data acquisition module 520, the level weight determination module 530, the account replenishment operation progress determination module 540 and the sending module 550 can be at least partially implemented as a computer program module, and when the computer program module is executed, the corresponding function can be executed.

[0123] Figure 6 A block diagram of an electronic device suitable for implementing a method for displaying progress of an account replenishment operation according to an embodiment of the present disclosure is schematically shown.

[0124] like Figure 6 As shown, the electronic device 600 according to an embodiment of the present disclosure includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage part 608 to a random access memory (RAM) 603. The processor 601 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a dedicated microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 601 may also include an onboard memory for caching purposes. The processor 601 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0125] In RAM 603, various programs and data required for the operation of electronic device 600 are stored. Processor 601, ROM 602 and RAM 603 are connected to each other via bus 604. Processor 601 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 602 and / or RAM 603. It should be noted that the program can also be stored in one or more memories other than ROM 602 and RAM 603. Processor 601 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0126] According to an embodiment of the present disclosure, the electronic device 600 may further include an input / output (I / O) interface 605, which is also connected to the bus 604. The electronic device 600 may further include one or more of the following components connected to the input / output (I / O) interface 605: an input portion 606 including a keyboard, a mouse, etc.; an output portion 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 608 including a hard disk, etc.; and a communication portion 609 including a network interface card such as a LAN card, a modem, etc. The communication portion 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the input / output (I / O) interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed, so that a computer program read therefrom is installed into the storage portion 608 as needed.

[0127] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0128] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, it may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the ROM 602 and / or RAM 603 described above and / or one or more memories other than ROM 602 and RAM 603.

[0129] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program includes a program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the method for displaying the progress of the account replenishment operation provided in the embodiment of the present disclosure.

[0130] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 601. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0131] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 609, and / or installed from a removable medium 611. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0132] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 609, and / or installed from the removable medium 611. When the computer program is executed by the processor 601, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, apparatus, module, unit, etc. described above can be implemented by a computer program module.

[0133] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

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

[0135] It will be appreciated by those skilled in the art that the features described in the various embodiments of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations or combinations are not explicitly described in the present disclosure. In particular, without departing from the spirit and teachings of the present disclosure, the features described in the various embodiments of the present disclosure may be combined and / or combined in a variety of ways. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0136] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A method for displaying the progress of an account replenishment operation, characterized in that: The method comprises: Acquire task level information of multiple account replenishment operations, wherein the task level information includes: n levels into which the multiple account replenishment operations are divided, and m account replenishment tasks included in each level, where n and m are both positive integers greater than or equal to 0; Acquire historical data and account-replenishment operation data of the account-replenishment operation, wherein the historical data includes historical completion durations corresponding to n levels, and the account-replenishment operation data includes an execution status of the account-replenishment task, wherein the execution status indicates whether the account-replenishment task has been completed; Determining a level weight of the level based on the historical completion time; Determining the progress of the account replenishment operation based on the level weight and the account replenishment operation data; The progress of the account replenishment operation is sent to a terminal display device so that the progress of the account replenishment operation is displayed through the terminal display device.

2. The method according to claim 1, characterized in that The determining the progress of the account replenishment operation based on the level weight and the account replenishment operation data includes: Determining an execution level and an execution progress of the execution level based on the account replenishment operation data; The progress of the account replenishment operation is determined based on the execution progress and the level weight corresponding to the execution level.

3. The method according to claim 2, characterized in that The n levels and the m account replenishment tasks are stored in order, and the determining of the execution level and the execution progress of the execution level based on the account replenishment operation data includes: Searching and obtaining an execution account replenishment task from the account replenishment operation data, wherein the execution account replenishment task is the first account replenishment task in the account replenishment operation whose execution status is unfinished; Based on the task level information of the execution task, the execution level and the execution progress corresponding to the execution task are determined.

4. The method according to claim 3, characterized in that Determining the level weight of the level based on the historical completion time includes performing the following operations for any i-th level: Determine the total historical completion time corresponding to all n levels; When the i-th level is a non-concurrent level, determining the first historical completion duration corresponding to the first i levels; The level weights of the first i levels are calculated based on the first historical completion time and the total historical completion time.

5. The method according to claim 3, characterized in that: The task level information also includes a correspondence between the account replenishment task and the level identifier. The determining the execution level and the execution progress corresponding to the execution task based on the task level information of the execution task includes: Determine an execution level identifier based on the corresponding relationship and the execution task; Based on the execution level identifier, searching from the task level information to obtain the number of completed tasks and the number of uncompleted tasks corresponding to the execution level; An execution progress of the level is determined based on the number of completed tasks and the number of uncompleted tasks.

6. The method according to claim 4, characterized in that The method further comprises: When the i-th level is a concurrent level, determining the second historical completion duration corresponding to the first i-1 levels; The level weights of the first i-1 levels are calculated based on the second historical completion time and the total historical completion time.

7. The method according to claim 4, characterized in that The determining the progress of the account replenishment operation based on the level weight and the account replenishment operation data includes: When the i-th level is a non-concurrent level, the weights of the first i levels are used as the progress of the account replenishment operation.

8. A progress display device for replenishment operation, characterized in that: The device comprises: A task level acquisition module, used to acquire task level information of multiple account replenishment operations, wherein the task level information includes: n levels into which the multiple account replenishment operations are divided, and m account replenishment tasks included in each level, where n and m are both positive integers greater than or equal to 0; A historical data acquisition module, used to acquire historical data and account replenishment operation data of the account replenishment operation, wherein the historical data includes historical completion time corresponding to n levels, and the account replenishment operation data includes the execution status of the account replenishment task, and the execution status indicates whether the account replenishment task has been completed; A level weight determination module, used to determine the level weight of the level based on the historical completion time; A module for determining the progress of an account replenishment operation, configured to determine the progress of an account replenishment operation based on the level weight and the account replenishment operation data; The sending module is used to send the progress of the account replenishment operation to the terminal display device, so that the progress of the account replenishment operation is displayed through the terminal display device.

9. An electronic device, comprising: one or more processors; a memory for storing one or more computer programs, It is characterized in that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 7.

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

Images