Outbound call task compensation method, device, equipment and storage medium
By monitoring outbound call tasks in real time and restarting abnormal tasks, the problem of inconsistent task status in outbound call systems is solved, the success rate and result accuracy of outbound call tasks are improved, and it is suitable for large-scale outbound call scenarios.
Patent Information
- Application Number
- CN202210547175.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-05-19
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2042-05-19
AI Technical Summary
In the outgoing call system, the status and execution of the outgoing call task are inconsistent, resulting in a decrease in the success rate of scheduling execution. Especially in the large-scale outgoing call scenario, abnormal tasks cannot be handled in time, affecting the continuity of the task and the accuracy of the result.
By monitoring the ongoing outbound call tasks in real time, compare the interval between the current time and the cache time and the outbound call progress and the cache progress. If the set time exceeds the set time and the progress does not change, update the cache time and restart the task to ensure the continuity of the task and consistency.
It improves the success rate of outbound call task scheduling, ensures the consistency of task status and the accuracy of results, reduces the dependence of human monitoring, and is suitable for large-scale outbound call scenarios.
Smart Images

Figure CN114938413B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to an outbound call task compensation method, device, equipment and storage medium. Background Art
[0002] With the rapid development of communication technology, outbound call systems are increasingly widely used. For example, in the financial industry, financial institutions can use outbound call systems to remind users to repay on time, promote related services, and make return visits to users for related services. Compared with traditional manual calls, outbound call systems have obvious advantages, such as high work efficiency and low operating costs.
[0003] At present, in the outbound call system, an outbound call task usually contains multiple outbound call lists. The outbound call lists are time-sensitive, and the expected execution time of the outbound call task is uncertain. In actual applications, there may be inconsistencies between the outbound call task status and the outbound call execution status, which in turn affects the success rate of outbound call task scheduling and execution. Summary of the invention
[0004] The present application provides an outbound call task compensation method, device, equipment and storage medium to improve the success rate of outbound call task scheduling execution.
[0005] In a first aspect, the present application provides an outbound call task compensation method, comprising:
[0006] Get the ongoing outbound calling tasks;
[0007] Determine the waiting time corresponding to the outbound call task according to whether re-call is configured for the outbound call task. The waiting time is used to represent the duration during which the outbound call progress of the outbound call task does not change.
[0008] Determine the current outbound call progress of the outbound call task;
[0009] Get the cache time and cache progress corresponding to the outbound call task. The cache progress is the outbound call progress of the most recently cached outbound call task, and the cache time is the time for caching the cache progress.
[0010] If the time interval between the current time and the cache time is greater than the waiting time, and the current outbound call progress is the same as the cache progress, the cache time is updated to the current time and the outbound call task is restarted.
[0011] In a second aspect, the present application provides an outbound call task compensation device, comprising:
[0012] The first acquisition module is used to acquire the ongoing outbound call task;
[0013] The first determination module is used to determine the waiting time corresponding to the outbound call task according to whether the recall is configured for the outbound call task, and the waiting time is used to represent the continuous time during which the outbound call progress of the outbound call task does not change;
[0014] The second determination module is used to determine the current outbound call progress of the outbound call task;
[0015] The second acquisition module is used to obtain the cache time and cache progress corresponding to the outbound call task, the cache progress is the outbound call progress of the outbound call task cached most recently, and the cache time is the time for caching the cache progress;
[0016] The first processing module is used to update the cache time to the current time and restart the outbound call task if the time interval between the current time and the cache time is greater than the waiting time and the current outbound call progress is the same as the cache progress.
[0017] In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;
[0018] Memory stores computer-executable instructions;
[0019] The processor executes the computer-executable instructions stored in the memory to implement the outbound call task compensation method as described in the first aspect of the present application.
[0020] In a fourth aspect, the present application provides a computer-readable storage medium, in which computer program instructions are stored. When the computer program instructions are executed by a processor, the outbound call task compensation method as described in the first aspect of the present application is implemented.
[0021] In a fifth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the outbound call task compensation method as described in the first aspect of the present application.
[0022] It can be seen that in the embodiment of the present application, due to the real-time monitoring of the ongoing outbound call tasks, the time interval between the current time and the cache time corresponding to the outbound call task is compared with the waiting time corresponding to the outbound call task, and the current outbound call progress of the outbound call task is compared with the cache progress corresponding to the outbound call task to determine whether the outbound call task is abnormal; when the outbound call task is abnormal, the outbound call task is restarted to reschedule the outbound call task, thereby improving the success rate of the outbound call task scheduling execution, ensuring the continuity of the outbound call task scheduling execution, the consistency of the outbound call task status and the accuracy of the outbound call task results. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0024] Figure 1 A schematic diagram of an application scenario provided for an embodiment of the present application;
[0025] Figure 2 A flowchart of an outbound call task compensation method provided in an embodiment of the present application;
[0026] Figure 3 A flowchart of an outbound call task compensation method provided by another embodiment of the present application;
[0027] Figure 4 A flowchart of an outbound call task compensation method provided by another embodiment of the present application;
[0028] Figure 5 A schematic diagram of the structure of an outbound call task compensation device provided in one embodiment of the present application;
[0029] Figure 6 A schematic diagram of the structure of an electronic device provided in one embodiment of the present application. DETAILED DESCRIPTION
[0030] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0031] In the technical solution of this application, the collection, storage, use, processing, transmission, provision and disclosure of information such as financial data or user data involved shall comply with the provisions of relevant laws and regulations and shall not violate public order and good morals.
[0032] First, some technical terms involved in this application are explained:
[0033] Remote Dictionary Server (Redis) is a key-value storage system used to cache data and has high efficiency in reading and writing data.
[0034] Recall, that is, in an outbound call task, when the first round of calls is not connected, the second round, third round, and other preset rounds of calls are made;
[0035] The recall interval refers to the interval between making a second outbound call when the first call is not connected.
[0036] At present, in the actual application of the outbound call system, there may be a situation where the status of the outbound call task is in progress but the outbound call has not actually started due to some reasons or errors in the outbound call system, or the status of the outbound call list of the outbound call task is that the outbound call has been completed but the status of the outbound call task is still in progress. For the above situation, the outbound call task will not automatically change to abnormal, and the outbound call list in the outbound call task is time-sensitive. It cannot wait until the outbound call task is completed or the execution time is observed to be too long to handle the abnormal outbound call task. At the same time, because there are a large number of outbound call lists corresponding to each outbound call task, the changes in the outbound call progress of the outbound call task cannot be observed by manual observation. Especially in the scenario of large-scale outbound calls, when there is no obvious abnormality in the execution process of the outbound call task, but the outbound call task is not closed normally within the effective time, it will cause the outbound call task to be unable to return the task conclusion normally.
[0037] Based on the above problems, the present application provides an outbound call task compensation method, device, equipment and storage medium. By real-time monitoring of the outbound call progress of the ongoing outbound call task, when the outbound call task has no progress within the set time period, the abnormal outbound call task is compensated, which can improve the success rate of the outbound call task scheduling execution, ensure the continuity of the outbound call task scheduling execution, the consistency of the outbound call task status and the accuracy of the outbound call task results.
[0038] In the following, the application scenarios of the solutions provided in this application are first illustrated.
[0039] Figure 1 This is a schematic diagram of an application scenario provided by an embodiment of the present application. Figure 1 As shown, in this application scenario, the server 101 where the outbound call system is located obtains the outbound call task. The outbound call task can be created by the business party through the client and then sent to the server 101, or it can be sent to the server 101 by other devices. The outbound call task contains multiple outbound call lists, that is, user mobile phone numbers. Server 101 passes the user mobile phone number in the outbound call task to the server 102 where the dialing system is located, and server 102 dials the user's mobile phone number. After the user answers the call, server 101 passes the content to be broadcast to server 102, and server 102 broadcasts the content to the user until the user hangs up the phone, completing the outbound call task. Among them, server 101 monitors the ongoing outbound call tasks in real time, and when it is found that the outbound call progress of the outbound call task is abnormal, it performs compensation processing on the outbound call task.
[0040] It should be noted that Figure 1 This is only a schematic diagram of an application scenario provided by the embodiment of the present application. Figure 1 does not limit the equipment included in Figure 1 The positional relationship between the devices in the Figure 1 In the application scenario shown, a data storage device may also be included. The data storage device may be an external memory relative to the server 101 or the server 102 , or an internal memory integrated in the server 101 or the server 102 .
[0041] Next, the outbound call task compensation method is introduced through a specific embodiment.
[0042] Figure 2 The flowchart of the outbound call task compensation method provided by an embodiment of the present application. The method of the embodiment of the present application can be applied to an electronic device, which can be a server or a server cluster. Figure 2 As shown, the method of the embodiment of the present application includes:
[0043] S201. Obtain an ongoing outbound call task.
[0044] In the embodiment of the present application, the status of the outbound call task may include, for example, not started, in progress, completed, terminated, manually suspended, or queued. Therefore, an outbound call task with an in-progress status may be obtained. Exemplarily, all in-progress outbound call tasks may be obtained, and the outbound call task compensation method provided in the embodiment of the present application may be performed on each in-progress outbound call task by traversing.
[0045] S202: Determine the waiting time corresponding to the outbound call task according to whether a re-call is configured for the outbound call task.
[0046] The waiting time is used to represent the duration during which the outbound call progress of the outbound call task does not change.
[0047] In this step, it is possible to pre-configure whether the outbound call task supports recall, and then determine the waiting time corresponding to the outbound call task according to whether recall is configured for the outbound call task. The waiting time corresponding to the outbound call task is used to determine that the outbound call task is abnormal after waiting for a long time without progress. Exemplarily, the waiting time corresponding to the outbound call task is, for example, 5 minutes. For how to determine the waiting time corresponding to the outbound call task according to whether recall is configured for the outbound call task, please refer to the subsequent embodiments, which will not be repeated here.
[0048] S203: Determine the current outbound call progress of the outbound call task.
[0049] In this step, the present application does not specifically limit the method for determining the current outbound call progress of the outbound call task. For example, the current outbound call progress of the outbound call task can be determined based on the total number of outbound calls included in the outbound call task and the number of completed outbound calls. For specific methods for determining the current outbound call progress of the outbound call task, please refer to the subsequent embodiments, which will not be described in detail here.
[0050] S204, obtaining the cache time and cache progress corresponding to the outbound call task, the cache progress is the outbound call progress of the outbound call task cached most recently, and the cache time is the time for caching the cache progress.
[0051] It is understandable that the outbound call task has been stored in the cache. This application does not specifically limit the specific cache tool. Exemplarily, the cache tool is Redis, and the most recent outbound call progress of the outbound call task, that is, the cache progress, is cached in Redis, and the time for caching the cache progress is cached in Redis. Therefore, the cache time and cache progress corresponding to the outbound call task can be obtained from Redis.
[0052] S205: If the time interval between the current time and the cache time is greater than the waiting time, and the current outbound call progress is the same as the cache progress, the cache time is updated to the current time, and the outbound call task is restarted.
[0053] In this step, after obtaining the cache time and cache progress corresponding to the outbound call task, the time interval between the current time and the cache time corresponding to the outbound call task can be compared with the waiting time, and the current outbound call progress of the outbound call task can be compared with the cache progress corresponding to the outbound call task to determine whether the outbound call task is abnormal. Specifically, if the time interval between the current time and the cache time corresponding to the outbound call task is greater than the waiting time, and the current outbound call progress of the outbound call task is the same as the cache progress corresponding to the outbound call task, it can be determined that the outbound call task is abnormal, and therefore, the outbound call task is compensated, that is, the cache time corresponding to the outbound call task is updated to the current time, and the cache progress corresponding to the outbound call task in the cache does not need to be updated, and the outbound call task is restarted to reschedule the outbound call task.
[0054] After executing step S205, execute step S201 to continue processing the next ongoing outbound call task until all ongoing outbound call tasks are processed, that is, the outbound call task compensation method provided in the embodiment of the present application is executed on each ongoing outbound call task in a traversal manner.
[0055] Optionally, the outbound call task compensation method may further include: periodically executing steps S201 to S205.
[0056] For example, a scan is performed every 3 minutes, and a round of processing of all ongoing outbound call tasks is completed by executing steps S201 to S205. By periodically executing steps S201 to S205, the ongoing outbound call tasks can be monitored in real time, and when the outbound call progress of the outbound call task is found to be abnormal, the outbound call task can be compensated in time.
[0057] The outbound call task compensation method provided in the embodiment of the present application obtains the outbound call task in progress, determines the waiting time corresponding to the outbound call task according to whether the outbound call task is configured for recall; determines the current outbound call progress of the outbound call task; obtains the cache time and cache progress corresponding to the outbound call task, the cache progress is the outbound call progress of the outbound call task cached most recently, and the cache time is the time for caching the cache progress; if the time interval between the current time and the cache time is greater than the waiting time, and the current outbound call progress is the same as the cache progress, then the cache time is updated to the current time, and the outbound call task is restarted. Since the embodiment of the present application monitors the outbound call task in progress in real time, the time interval between the current time and the cache time corresponding to the outbound call task is compared with the waiting time corresponding to the outbound call task, and the current outbound call progress of the outbound call task is compared with the cache progress corresponding to the outbound call task to determine whether the outbound call task is abnormal. When the outbound call task is abnormal, the outbound call task is restarted to reschedule the outbound call task. Therefore, the success rate of outbound call task scheduling execution can be improved, and the continuity of outbound call task scheduling execution, the consistency of outbound call task status, and the accuracy of outbound call task results can be ensured.
[0058] Figure 3 This is a flow chart of an outbound call task compensation method provided by another embodiment of the present application. Based on the above embodiment, the embodiment of the present application further describes the outbound call task compensation method. Figure 3 As shown, the method of the embodiment of the present application may include:
[0059] S301: Obtain the ongoing outbound call task.
[0060] The detailed description of this step can be found in Figure 2 The relevant description of S201 in the illustrated embodiment will not be repeated here.
[0061] S302: Lock the outbound call task.
[0062] For example, acquiring an Rdis lock to lock an outbound call task can prevent data confusion and duplicate writing.
[0063] In the embodiment of the present application, Figure 2 The step S202 may further include the following three steps S303 to S305:
[0064] S303: If re-call is not configured for the outbound call task, determine that the waiting time corresponding to the outbound call task is the first time.
[0065] Exemplarily, the first duration is, for example, 5 minutes, and the first duration can be understood as a default duration, which can be set as needed. In this step, if recall is not configured for the outbound call task, that is, the multiple outbound call lists included in the outbound call task do not support recall, then it can be determined that the waiting time corresponding to the outbound call task is 5 minutes.
[0066] S304: If re-calling is configured for the outbound call task and the first round of outbound calls is not completed, determine that the waiting time corresponding to the outbound call task is a second time.
[0067] The second duration is less than or equal to the first duration.
[0068] For example, if one of the multiple outbound call lists included in the outbound call task has a status of not completing the first outbound call, it can be determined that the first round of outbound calls of the outbound call task is not completed. In this step, if recall is configured for the outbound call task, that is, the multiple outbound call lists included in the outbound call task all support recall, and the first round of outbound calls is not completed, it can be determined that the waiting time corresponding to the outbound call task is the second time. The second time is, for example, 5 minutes, and the second time can be understood as the default setting time.
[0069] S305: If recall is configured for the outbound call task and the first round of outbound calls has been completed, determine the waiting time corresponding to the outbound call task as the recall time interval.
[0070] The recall time interval is greater than or equal to the first duration.
[0071] Exemplarily, the recall time interval is, for example, 10 minutes. If recall is configured for an outbound call task and the first round of outbound calls has been completed, it can be determined that the waiting time corresponding to the outbound call task is 10 minutes.
[0072] In the embodiment of the present application, Figure 2 The step S203 may further include the following step S306:
[0073] S306: Determine the current outbound call progress of the outbound call task as the number of outbound calls completed in the outbound call task.
[0074] For example, assuming that the outbound call task contains 5 outbound call lists, 3 of which are in the status of completed outbound calls, it can be determined that the number of completed outbound calls in the outbound call task is 3, and thus the current outbound call progress of the outbound call task can be determined to be 3.
[0075] In the embodiment of the present application, Figure 2 The step S204 may further include the following step S307:
[0076] S307: When it is determined that the outbound call task is stored in the cache, the cache time and cache progress corresponding to the outbound call task are obtained.
[0077] The cache progress is the outbound call progress of the outbound call task cached most recently, and the cache time is the time for caching the cache progress.
[0078] For example, the outbound call task has been cached in Redis, and the cache time and cache progress corresponding to the outbound call task can be queried from Redis.
[0079] S308: If it is determined that the outbound call task is not stored in the cache, the current time and the current outbound call progress are stored in the cache.
[0080] It is understandable that when the outbound call task in progress is obtained for the first time, the outbound call task does not exist in the cache. Therefore, if it is determined that the outbound call task is not stored in the cache, the current time and the current outbound call progress of the outbound call task can be stored in the cache, and then step S312 is executed. Exemplarily, if it is determined that the outbound call task is not stored in Redis, the current time and the current outbound call progress of the outbound call task are stored in Redis.
[0081] Optionally, the expiration time of the outbound call task in the cache can be set to the sum of the waiting time corresponding to the outbound call task and the preset time, so as to automatically clean up the outbound call tasks in the cache. Exemplarily, the preset time is, for example, 5 minutes. By setting the expiration time of the outbound call task in the cache (such as Redis), the outbound call tasks in the cache can be automatically deleted according to the expiration time to prevent excessive data in the cache and make rational use of cache resources. The expiration time is set based on the waiting time, which can avoid the data in the cache from being cleaned up in advance, and also prevent the data in the cache from being not cleaned up for a long time.
[0082] S309: If the time interval between the current time and the cache time is greater than the waiting time, and the current outbound call progress is the same as the cache progress, the cache time is updated to the current time, and the outbound call task is restarted.
[0083] The detailed description of this step can be found in Figure 2 The relevant description of S205 in the illustrated embodiment will not be repeated here.
[0084] Optionally, after restarting the outbound call task, the outbound call task compensation method may further include: sending a notification message of the outbound call task compensation process according to a preset notification method, wherein the preset notification method at least includes an email notification method, a text message notification method or a notification method of a third-party notification function.
[0085] While performing compensation processing on the abnormal outbound call tasks, by sending a notification message of the outbound call task compensation processing, the business personnel can timely understand the compensation status of the outbound call tasks.
[0086] Optionally, restarting the outbound call task may be restarting the outbound call task immediately or not.
[0087] Alternatively, before restarting the outbound call task, the outbound call task compensation method includes:
[0088] If the number of outbound call tasks currently in progress is less than the first threshold, restart the outbound call task immediately;
[0089] If the number of outbound call tasks currently in progress is greater than or equal to the first threshold, determining the importance of the outbound call tasks;
[0090] If the importance of the outbound call task is greater than or equal to the preset importance, restart the outbound call task immediately;
[0091] If the importance of the outbound call task is less than the preset level, and the current outbound call progress of the outbound call task is greater than or equal to the second threshold, restart the outbound call task immediately;
[0092] If the importance of the outbound call task is less than the preset level, and the current outbound call progress of the outbound call task is less than the second threshold, the outbound call task is added to the restart queue to wait for restart in the order of joining the queue.
[0093] The first threshold value may be, for example, 100 or other values, and the second threshold value may be, for example, 80% or other values.
[0094] It can be seen that when the number of outbound call tasks currently in progress is small, the outbound call task is immediately restarted and the outbound call task is rescheduled in time, so that the outbound call task is processed in time; when the number of outbound call tasks currently in progress is large, it is determined whether the outbound call task needs to be restarted immediately according to the importance of the outbound call task, so that the outbound call task with high importance is rescheduled in time, and then the outbound call task with high importance is processed in time; when the importance of the outbound call task is not so important, it is determined whether the outbound call task needs to be restarted immediately according to the current outbound call progress of the outbound call task, so that the outbound call task that is close to completion is rescheduled in time, and then the outbound call task that is close to completion is processed in time, so that the outbound call task is completed as soon as possible; when the current outbound call progress of the outbound call task is still some distance away from completion, in order to avoid the situation where there are too many outbound call tasks in progress and the device is overloaded with processing tasks, the outbound call task is first put into the restart queue to wait for restarting.
[0095] The specific implementation method of determining the importance of the outbound call task includes: determining the importance of the outbound call task according to at least one of the type of the outbound call task and the current outbound call progress of the outbound call task.
[0096] Further, determining the importance of the outbound call task according to at least one of the type of the outbound call task and the current outbound call progress of the outbound call task includes:
[0097] If the type of the outbound call task is a specified type, determining the importance of the outbound call task to be a first level, the first level being greater than or equal to the preset level;
[0098] If the type of the outbound call task is not the specified type, the importance of the outbound call task is determined according to the current outbound call progress of the outbound call task and a mapping relationship, where the mapping relationship is a mapping relationship between the outbound call progress of the outbound call task and the importance of the outbound call task.
[0099] The mapping relationship between the outbound call progress of the outbound call task and the importance of the outbound call task is shown in Table 1. The second degree is greater than or equal to the preset degree, and the third degree is less than the preset degree.
[0100] Table 1
[0101] Outbound call progress of outbound call tasks Importance of outbound call tasks 80%~100% Second degree 0%~80% Third degree
[0102] The designated type may be, for example, a service type for reminding users to repay on time, a service type for user return visit, and the like.
[0103] It can be seen that since the type of the outbound call task can evaluate whether the outbound call task is important, and the outbound call progress of the outbound call task can evaluate the progress of the outbound call task, using at least one of the two to evaluate the importance of the outbound call task can make the determined importance more reasonable.
[0104] S310: If the current outbound call progress is different from the cached progress, the cached time is updated to the current time, and the cached progress is updated to the current outbound call progress.
[0105] In this step, after obtaining the cache progress corresponding to the outbound call task, the current outbound call progress of the outbound call task can be compared with the cache progress corresponding to the outbound call task to determine whether the outbound call task is abnormal. Specifically, if the current outbound call progress is different from the cache progress, it can be determined that the outbound call task is normal. Therefore, there is no need to compensate for the outbound call task. It is only necessary to update the cache time corresponding to the outbound call task to the current time and update the cache progress corresponding to the outbound call task to the current outbound call progress.
[0106] S311. If the time interval between the current time and the cache time is less than or equal to the waiting time, and the current outbound call progress is the same as the cache progress, the cache time and cache progress are maintained.
[0107] In this step, after obtaining the cache time and cache progress corresponding to the outbound call task, the time interval between the current time and the cache time corresponding to the outbound call task can be compared with the waiting time, and the current outbound call progress of the outbound call task can be compared with the cache progress corresponding to the outbound call task to determine whether the outbound call task is abnormal. Specifically, if the time interval between the current time and the cache time is less than or equal to the waiting time, and the current outbound call progress is the same as the cache progress, it can be determined that the outbound call task is normal, and there is no need to update the cache time and cache progress corresponding to the outbound call task, that is, the cache time and cache progress are maintained.
[0108] Optionally, the progress growth rate corresponding to the current outbound call progress is determined based on the current outbound call progress and the cache progress; when the progress growth rate is less than the growth rate threshold, the outbound call task is not restarted, and a notification message of abnormal progress of the outbound call task is sent through the above-mentioned preset notification method.
[0109] Exemplarily, the percentage corresponding to the ratio of the difference between the current outbound call progress and the cached progress to the cached progress is used as the progress growth rate corresponding to the current outbound call progress. When the progress growth rate is less than the growth rate threshold, a notification message of abnormal progress of the outbound call task is sent, which can promptly notify the business personnel of the abnormal progress of the outbound call task. The business personnel can determine whether to manually restart the outbound call task based on the priority of the outbound call task. For example, for a high-priority outbound call task, the outbound call task can be manually restarted. The business personnel can also adjust the priority of the outbound call task to ensure that the high-priority outbound call task is rescheduled in time.
[0110] S312: Release the lock of the outbound call task.
[0111] It can be understood that after executing any step S308 or S309 to S311, the outbound call task can be released from the lock, which means that the outbound call task has been processed and the next outbound call task in progress can be processed.
[0112] The outbound call task compensation method provided in the embodiment of the present application obtains the ongoing outbound call task and locks the outbound call task; if the outbound call task is not configured with a re-call, the waiting time corresponding to the outbound call task is determined to be the first time; if the outbound call task is configured with a re-call and the first round of outbound calls is not completed, the waiting time corresponding to the outbound call task is determined to be the second time; if the outbound call task is configured with a re-call and the first round of outbound calls is completed, the waiting time corresponding to the outbound call task is determined to be the re-call time interval; the current outbound call progress of the outbound call task is determined to be the number of outbound calls completed in the outbound call task; when it is determined that the outbound call task is stored in the cache, the cache corresponding to the outbound call task is obtained. Store the time and cache progress; if it is determined that the outbound call task is not stored in the cache, store the current time and the current outbound call progress in the cache; if the time interval between the current time and the cache time is greater than the waiting time, and the current outbound call progress is the same as the cache progress, update the cache time to the current time, and restart the outbound call task; if the current outbound call progress is different from the cache progress, update the cache time to the current time, and update the cache progress to the current outbound call progress; if the time interval between the current time and the cache time is less than or equal to the waiting time, and the current outbound call progress is the same as the cache progress, maintain the cache time and cache progress; and release the lock on the outbound call task. Since the embodiment of the present application monitors the ongoing outbound call tasks in real time, each ongoing outbound call task is locked and released to prevent data confusion and repeated writing; by comparing the time interval between the current time and the cache time corresponding to the outbound call task with the waiting time corresponding to the outbound call task, and comparing the current outbound call progress of the outbound call task with the cache progress corresponding to the outbound call task, it is determined whether the outbound call task is abnormal. When the outbound call task is abnormal, the outbound call task is restarted to reschedule the outbound call task. Therefore, the success rate of the outbound call task scheduling execution can be improved, and the continuity of the outbound call task scheduling execution, the consistency of the outbound call task status and the accuracy of the outbound call task results can be ensured.
[0113] Based on the above embodiments, Figure 4 A flowchart of an outbound call task compensation method provided by another embodiment of the present application. Based on the above embodiment, the present application embodiment takes the example of performing a scan once every 3 minutes and scanning three times to further illustrate the outbound call task compensation method. Figure 4 As shown, the method of the embodiment of the present application may include:
[0114] S401. Assume that the first scan is performed at 09:00 in the morning and an ongoing outbound call task A is scanned.
[0115] S402. Assuming that the outbound call task A does not exist in the Redis cache, determine the current outbound call progress a1 of the outbound call task A, use the current outbound call progress a1 of the outbound call task A as the cache progress corresponding to the outbound call task A, and use the current time t1 as the cache time corresponding to the outbound call task A; write the cache progress and cache time corresponding to the outbound call task A into the cache.
[0116] S403, performing the scan for the second time at 09:03, and once again scanning the ongoing outbound call task A, determining the waiting time D corresponding to the outbound call task A, assuming that there is no repeated call for the outbound call task A, the waiting time is, for example, 5 minutes.
[0117] S404. Determine the time interval between the current time t2 and the cache time t1 of the outbound call task A, which is 3 minutes, which is less than 5 minutes; and determine whether the outbound call progress of the outbound call task A has changed based on the current outbound call progress of the outbound call task A and the cache progress a1 corresponding to the outbound call task A; if the outbound call progress of the outbound call task A has not changed, execute step S405; if the outbound call progress of the outbound call task A has changed, execute step S406.
[0118] S405: Redis is not updated, the cache progress corresponding to the outbound call task A in Redis is still a1, and the cache time corresponding to the outbound call task A in Redis is still t1.
[0119] S406. Update the outbound call progress of outbound call task A in Redis to a2, and the cache time corresponding to outbound call task A to t2.
[0120] S407, the scan is performed for the third time at 09:06, and the outbound call task A in progress is scanned again.
[0121] S408. Based on steps S405 and S407, determine the time interval between the current time t3 and the cache time t1 corresponding to the outbound call task A. The time interval is 6 minutes, which is greater than 5 minutes. And based on the current outbound call progress of the outbound call task A and the cache progress corresponding to the outbound call task A, determine whether the outbound call progress of the outbound call task A has changed. If the outbound call progress of the outbound call task A has not changed, execute step S409; if the outbound call progress of the outbound call task A has changed, execute step S410.
[0122] S409, reschedule the outbound call task A, and update the cache time corresponding to the outbound call task A in Redis to t3, and the cache progress corresponding to the outbound call task A in the cache is still a1.
[0123] S410, updating the outbound call progress of outbound call task A in Redis to a3, and the cache time corresponding to outbound call task A to t3.
[0124] S411. Based on steps S406 and S407, determine the time interval between the current time t3 and the cache time t2 corresponding to the outbound call task A, which is 3 minutes, less than 5 minutes; and based on the current outbound call progress a3 of the outbound call task A and the cache progress a2 corresponding to the outbound call task A, determine whether the outbound call progress of the outbound call task A has changed; if the outbound call progress of the outbound call task A has not changed, execute step S412; if the outbound call progress of the outbound call task A has changed, execute step S413.
[0125] S412: Do not update Redis.
[0126] S413, updating the current outbound call progress a3 of the outbound call task A in Redis, and the cache time corresponding to the outbound call task A is t3.
[0127] In summary, the technical solution provided by the present application has at least the following advantages: the progress of each outbound call task can be monitored in real time; when the outbound call task has no progress within the set time, the abnormal outbound call task can be compensated in time, without the need for real-time human monitoring, and can be completely independent of personnel dependence; and the technical solution provided by the present application will not affect business continuity, and is unaware of upstream and downstream dependencies; at the same time, in the technical solution provided by the present application, the judgment and filtering of abnormal outbound call tasks is completely determined by the configuration of the outbound call task itself, and is also related to the task type (i.e. whether recall is configured), with high adaptability, which can avoid all outbound call tasks from using a unified waiting time, and prevent excessive scheduling of outbound call tasks or failure to detect abnormalities for a long time.
[0128] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.
[0129] Figure 5 A schematic diagram of the structure of an outbound call task compensation device provided in an embodiment of the present application is shown in FIG. Figure 5 As shown, the outbound call task compensation device 500 of the embodiment of the present application includes: a first acquisition module 501, a first determination module 502, a second determination module 503, a second acquisition module 504 and a first processing module 505.
[0130] in:
[0131] The first acquisition module 501 is used to acquire the ongoing outbound call task.
[0132] The first determining module 502 is used to determine the waiting time corresponding to the outbound call task according to whether a recall is configured for the outbound call task, where the waiting time is used to represent the duration during which the outbound call progress of the outbound call task does not change.
[0133] The second determining module 503 is used to determine the current outbound call progress of the outbound call task.
[0134] The second acquisition module 504 is used to acquire the cache time and cache progress corresponding to the outbound call task, the cache progress is the outbound call progress of the outbound call task cached most recently, and the cache time is the time for caching the cache progress.
[0135] The first processing module 505 is used to update the cache time to the current time and restart the outbound call task if the time interval between the current time and the cache time is greater than the waiting time and the current outbound call progress is the same as the cache progress.
[0136] In some embodiments, the first determination module 502 can be specifically used for at least one of the following: if recall is not configured for the outbound call task, the waiting time is determined to be a first time period; if recall is configured for the outbound call task and the first round of outbound calls is not completed, the waiting time is determined to be a second time period, and the second time period is less than or equal to the first time period; if recall is configured for the outbound call task and the first round of outbound calls is completed, the waiting time is determined to be the recall time interval, and the recall time interval is greater than or equal to the first time period.
[0137] In some embodiments, the second determining module 503 may be specifically configured to: determine the current outbound call progress of the outbound call task as the number of outbound calls completed in the outbound call task.
[0138] In some embodiments, the second acquisition module 504 may be specifically configured to: when it is determined that the outbound call task is stored in the cache, acquire the cache time and cache progress corresponding to the outbound call task.
[0139] Optionally, the second acquisition module 504 may also be used to: if it is determined that the outbound call task is not stored in the cache, store the current time and the current outbound call progress in the cache.
[0140] Optionally, the first processing module 505 can also be used for: if the current outbound call progress is different from the cached progress, then updating the cached time to the current time, and updating the cached progress to the current outbound call progress; and / or, if the time interval between the current time and the cached time is less than or equal to the waiting time, and the current outbound call progress is the same as the cached progress, then maintaining the cached time and cached progress.
[0141] In some embodiments, the first acquisition module 501 can also be used to: lock the outbound call task after acquiring the ongoing outbound call task; the first processing module 505 can also be used to: release the lock of the outbound call task after updating the cache time to the current time and restarting the outbound call task.
[0142] The device of this embodiment can be used to execute the technical solution of any of the above-mentioned method embodiments. Its implementation principle and technical effects are similar and will not be repeated here.
[0143] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. For example, the electronic device can be provided as a server or a computer. Figure 6 , the electronic device 600 includes a processing component 601, which further includes one or more processors, and a memory resource represented by a memory 602, for storing instructions that can be executed by the processing component 601, such as an application. The application stored in the memory 602 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 601 is configured to execute instructions to perform any of the above method embodiments.
[0144] The electronic device 600 may further include a power supply component 603 configured to perform power management of the electronic device 600, a wired or wireless network interface 604 configured to connect the electronic device 600 to a network, and an input / output (I / O) interface 605. The electronic device 600 may operate based on an operating system stored in the memory 602, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™ or the like.
[0145] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above-mentioned outbound call task compensation method is implemented.
[0146] The present application also provides a computer program product, including a computer program, which implements the above-mentioned outbound call task compensation method when executed by a processor.
[0147] The computer-readable storage medium mentioned above can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.
[0148] An exemplary readable storage medium is coupled to the processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the readable storage medium can also exist in the outbound call task compensation device as discrete components.
[0149] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.
[0150] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.
Claims
1. A method for compensating an outbound call task, characterized in that: include: Get the ongoing outbound calling tasks; Determine the waiting time corresponding to the outbound call task according to whether a recall is configured for the outbound call task, wherein the waiting time is used to represent the duration during which the outbound call progress of the outbound call task does not change; Determine the current outbound call progress of the outbound call task; Obtain the cache time and cache progress corresponding to the outbound call task, the cache progress is the outbound call progress of the outbound call task cached most recently, and the cache time is the time for caching the cache progress; If the time interval between the current time and the cache time is greater than the waiting time, and the current outbound call progress is the same as the cache progress, the outbound call task is determined to be abnormal, the cache time is updated to the current time, and the outbound call task is restarted.
2. The outbound call task compensation method according to claim 1, characterized in that: The determining the waiting time corresponding to the outbound call task according to whether a recall is configured for the outbound call task includes: If a re-call is not configured for the outbound call task, determining the waiting time to be the first time; If a re-call is configured for the outbound call task and the first round of outbound calls is not completed, determining the waiting time to be a second time, and the second time is less than or equal to the first time; If recall is configured for the outbound call task and the first round of outbound calls has been completed, the waiting time is determined to be the recall time interval, and the recall time interval is greater than or equal to the first time interval.
3. The outbound call task compensation method according to claim 1, characterized in that: The determining the current outbound call progress of the outbound call task includes: The current outbound call progress of the outbound call task is determined as the number of outbound calls completed in the outbound call task.
4. The outbound call task compensation method according to claim 1, characterized in that: The obtaining of the cache time and cache progress corresponding to the outbound call task includes: When it is determined that the outbound call task is stored in the cache, the cache time and cache progress corresponding to the outbound call task are obtained.
5. The outbound call task compensation method according to claim 4, characterized in that: Also includes: If it is determined that the outbound call task is not stored in the cache, the current time and the current outbound call progress are stored in the cache.
6. The outbound call task compensation method according to any one of claims 1 to 5, characterized in that: Also includes: If the current outbound call progress is different from the cached progress, updating the cached time to the current time, and updating the cached progress to the current outbound call progress; If the time interval between the current time and the cache time is less than or equal to the waiting time, and the current outbound call progress is the same as the cache progress, the cache time and the cache progress are maintained.
7. The outbound call task compensation method according to any one of claims 1 to 5, characterized in that: After obtaining the ongoing outbound call task, the method further includes: Locking the outbound call task; After updating the cache time to the current time and restarting the outbound call task, a lock release process is performed on the outbound call task.
8. An outbound call task compensation device, characterized in that: include: The first acquisition module is used to acquire the ongoing outbound call task; A first determination module is used to determine the waiting time corresponding to the outbound call task according to whether a recall is configured for the outbound call task, and the waiting time is used to represent the continuous time during which the outbound call progress of the outbound call task does not change; A second determination module is used to determine the current outbound call progress of the outbound call task; A second acquisition module is used to acquire the cache time and cache progress corresponding to the outbound call task, wherein the cache progress is the outbound call progress of the outbound call task cached most recently, and the cache time is the time for caching the cache progress; A processing module is used to determine that the outbound call task is abnormal, update the cache time to the current time, and restart the outbound call task if the time interval between the current time and the cache time is greater than the waiting time, and the current outbound call progress is the same as the cache progress.
9. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the outbound call task compensation method according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by the processor, the outbound call task compensation method according to any one of claims 1 to 7 is implemented.
