Breakpoint task processing method and device, electronic equipment and medium

Abstract

The embodiment of the invention provides a breakpoint task processing method and device, electronic equipment and a medium, and relates to the technical field of the Internet, and the technical scheme comprises the steps that attribute information and source information of a breakpoint task are obtained, and the breakpoint task represents that in the online registration process, the source information of the breakpoint task is obtained; the task is generated after the staying duration of the user in at least one registration link exceeds the preset timeout duration. And then, according to the attribute information and the source information, determining a processor of the breakpoint task, and pushing the breakpoint task to user equipment associated with the processor, so that the processor provides online registration guidance for a user according to the breakpoint task. The online registration experience of the user is improved, and user loss is reduced.

Description

Technical Field

[0001] This application relates to the field of Internet technologies, and in particular, to a method, apparatus, electronic device, and medium for processing breakpoint tasks. Background Art

[0002] For a user to open an account and register with a business institution is the basis for carrying out various businesses. With the increasing maturity of Internet technologies and mobile applications, the process of user registration no longer requires the user to go to the physical office of the business institution, but can be operated online through mobile devices and other means. Different from the process of registering at a physical office, when registering online, the user does not have the professional guidance of a staff member. Therefore, for each additional registration step, the possibility of the user abandoning online registration increases. Especially in the financial field, due to the characteristics of strong compliance and strong supervision, there are many steps involved in user registration and the operation is cumbersome, resulting in a high possibility of users abandoning online registration.

[0003] When a user abandons the online registration process, it is called a breakpoint. After a breakpoint occurs, the user can only receive a text message or intelligent voice reminder, that is, reminding the user that the registration has failed, which does not provide any practical help for the user's registration. Therefore, it not only makes the user experience poor, but also increases the possibility of user churn, causing losses to the business institution. Summary of the Invention

[0004] The purpose of the embodiments of this application is to provide a method, apparatus, electronic device, and medium for processing breakpoint tasks, so as to improve the user's online registration experience and reduce user churn. The specific technical solutions are as follows:

[0005] In a first aspect, the embodiments of this application provide a method for processing breakpoint tasks, the method including:

[0006] Obtain the attribute information and source information of a breakpoint task, where the breakpoint task represents: a task generated after the residence time of a user in at least one registration step exceeds a preset timeout duration during the online registration process;

[0007] Determine the processor of the breakpoint task according to the attribute information and the source information;

[0008] Push the breakpoint task to the user device associated with the processor, so that the processor provides online registration guidance for the user according to the breakpoint task.

[0009] Optionally, before obtaining the attribute information and source information of the breakpoint task, it further includes:

[0010] Check whether the current date is within a preset whitelist;

[0011] If the current date is not within the preset whitelist, determine whether the current date meets the preset whitelist rules, is not within the preset blacklist, and does not meet the preset blacklist rules;

[0012] If the current date is within the preset whitelist or the judgment results are all yes, verify whether the current time belongs to the preset dispatch time period and whether the task dispatch status is the open status;

[0013] If the verification results are all yes, execute the step of obtaining the attribute information and source information of the breakpoint task;

[0014] If any judgment result is no or any verification result is no, after waiting for a preset duration, return to the step of checking whether the current date is within the preset whitelist.

[0015] Optionally, determining the handler of the breakpoint task based on the attribute information and the source information includes:

[0016] Determine the characteristic value corresponding to the attribute information and the characteristic value corresponding to the source information;

[0017] Determine the product of the characteristic value corresponding to the attribute information and the weight corresponding to the attribute information, and the product of the characteristic value corresponding to the source information and the weight corresponding to the source information;

[0018] Based on the preset mapping rule, determine the target task level mapped by each product from the preset task levels;

[0019] Select the handler of the breakpoint task from the executor whitelist corresponding to the target task level.

[0020] Optionally, the method further includes:

[0021] Receive configuration information, where the configuration information includes candidates configured by the initial configurator for a single task level;

[0022] Judge whether the candidate supports task execution;

[0023] If so, use the candidate as the executor of this task level and add it to the executor whitelist corresponding to this task level;

[0024] If not, obtain the candidates configured by the candidate for this task level and return to the step of judging whether the candidate supports task execution.

[0025] Optionally, the method further includes:

[0026] For the executor whitelist corresponding to each task level, obtain the statistical values of each task statistic item of each executor who has executed the breakpoint task in the executor whitelist;

[0027] For each executor, based on the statistical values of the executor, determine the processing score of the executor;

[0028] Screen out the executors to be eliminated whose processing scores are lower than the preset threshold corresponding to the task level;

[0029] Delete the executor to be eliminated from the white list of the executor.

[0030] Optionally, the determining the processing score of the executor based on the statistical values of the executor includes:

[0031] For the statistical value of each task statistical item, determine the product of the statistical value and the weight corresponding to the task statistical item;

[0032] Through a preset calculation method, calculate each product to obtain the processing score of the processor.

[0033] Optionally, after deleting the executor to be eliminated from the white list of the executor, it further includes:

[0034] Determine the target configurator who configures the executor to be eliminated for the task level;

[0035] Obtain the executors newly added by the target configurator for the task level and add them to the white list of executors corresponding to the task level.

[0036] In a second aspect, an embodiment of the present application provides a breakpoint task processing device, and the device includes:

[0037] An acquisition module, configured to acquire attribute information and source information of a breakpoint task, where the breakpoint task represents: a task generated after the residence time of a user in at least one registration link exceeds a preset timeout duration during an online registration process;

[0038] A determination module, configured to determine a processor of the breakpoint task according to the attribute information and the source information;

[0039] A push module, configured to push the breakpoint task to a user device associated with the processor, so that the processor provides online registration guidance for the user according to the breakpoint task.

[0040] Optionally, the device further includes a verification module, and the verification module is configured to:

[0041] Before acquiring the attribute information and source information of the breakpoint task, check whether the current date is in a preset white list;

[0042] If the current date is not within the preset whitelist, then determine whether the current date meets the preset whitelist rules, is not within the preset blacklist, and does not meet the preset blacklist rules;

[0043] If the current date is within the preset whitelist or the judgment results are all yes, then verify whether the current time belongs to the preset dispatch time period and whether the task dispatch status is the open status;

[0044] If the verification results are all yes, then call the acquisition module to execute the steps of acquiring the attribute information and source information of the breakpoint task;

[0045] If any judgment result is no or any verification result is no, then after waiting for a preset duration, return to the step of checking whether the current date is within the preset whitelist.

[0046] Optionally, the determination module is specifically configured to:

[0047] Determine the characteristic value corresponding to the attribute information and the characteristic value corresponding to the source information;

[0048] Determine the product of the characteristic value corresponding to the attribute information and the weight corresponding to the attribute information, and the product of the characteristic value corresponding to the source information and the weight corresponding to the source information;

[0049] Based on the preset mapping rules, determine the target task level mapped by each product from the preset task levels;

[0050] Select the handler of the breakpoint task from the executor whitelist corresponding to the target task level.

[0051] Optionally, the device further includes a configuration module, and the configuration module is used for:

[0052] Receive configuration information, where the configuration information includes candidates configured by the initial configurator for a single task level;

[0053] Judge whether the candidate supports task execution;

[0054] If so, use the candidate as the executor of this task level and add it to the executor whitelist corresponding to this task level;

[0055] If not, obtain the candidates configured by the candidate for this task level and return to the step of judging whether the candidate supports task execution.

[0056] Optionally, the device further includes an elimination module, and the elimination module is used for:

[0057] For the executor whitelist corresponding to each task level, obtain the statistical values of each task statistic item of the breakpoint tasks that have been executed by each executor in the executor whitelist;

[0058] For each executor, determine the processing score of the executor based on the statistical values of the executor;

[0059] Filter out the executors to be eliminated whose processing scores are lower than the preset threshold corresponding to this task level;

[0060] Delete the executor to be eliminated from the executor whitelist.

[0061] Optionally, the elimination module is specifically used for:

[0062] For the statistical value of each task statistic item, determine the product of the statistical value and the weight corresponding to the task statistic item;

[0063] Through a preset calculation method, calculate each product to obtain the processing score of this processor.

[0064] Optionally, the device further includes an addition module, and the addition module is used for:

[0065] After deleting the executor to be eliminated from the executor whitelist, determine the target configurator who configures the executor to be eliminated for this task level;

[0066] Obtain the executors newly added by the target configurator for this task level and add them to the executor whitelist corresponding to this task level.

[0067] In a third aspect, an embodiment of the present application provides an electronic device, including a processor, a communication interface, a memory, and a communication bus. Among them, the processor, the communication interface, and the memory complete mutual communication through the communication bus;

[0068] The memory is used to store a computer program;

[0069] When the processor is used to execute the program stored on the memory, it implements the method described in any item of the first aspect.

[0070] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, and a computer program is stored in the computer-readable storage medium. When the computer program is executed by a processor, it implements the method described in any item of the first aspect.

[0071] In a fifth aspect, an embodiment of the present application provides a computer program product containing instructions. When it runs on a computer, it causes the computer to execute the method described in any item of the first aspect above.

[0072] Beneficial effects of the embodiments of the present application:

[0073] The breakpoint task processing method, device, electronic device and medium provided by the embodiments of the present application can, after a breakpoint occurs, determine the processor of the breakpoint task according to the attribute information and source information of the breakpoint task, and send the breakpoint task to the processor, so that the processor can provide online registration guidance for the user according to the breakpoint task. That is, the user can obtain professional guidance from the staff without arriving at the physical office, which reduces the difficulty of online registration, improves the user's online registration experience, and reduces user churn.

[0074] Of course, when implementing any product or method of the present application, it is not necessarily required to achieve all the above-mentioned advantages at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0076] Figure 1 It is a flowchart of a breakpoint task processing method provided by the embodiments of the present application;

[0077] Figure 2 It is a flowchart of a method for determining whether task dispatching is supported provided by the embodiments of the present application;

[0078] Figure 3 It is a flowchart of a method for configuring an executor whitelist provided by the embodiments of the present application;

[0079] Figure 4 It is a flowchart of a method for eliminating some executors provided by the embodiments of the present application;

[0080] Figure 5 It is a flowchart of another method for eliminating some executors provided by the embodiments of the present application;

[0081] Figure 6 It is a flowchart of another breakpoint task processing method provided by the embodiments of the present application;

[0082] Figure 7 It is a schematic structural diagram of a breakpoint task processing device provided by the embodiments of the present application;

[0083] Figure 8 It is a schematic structural diagram of an electronic device provided by the embodiments of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0084] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art based on the present application belong to the scope of protection of the present application.

[0085] To improve the user's online registration experience and reduce user churn, the embodiments of the present application provide a breakpoint task processing method, which is applied to an electronic device. For example, the electronic device can be a desktop computer, a laptop computer, or a server, etc., which are devices with data processing capabilities. The breakpoint task processing method provided by the embodiments of the present application can be executed by a software module in the electronic device, and the software module can be a database, such as a relational database system (SQL-server).

[0086] As Figure 1 shown, the breakpoint task processing method provided by the embodiments of the present application includes the following steps:

[0087] S101. Obtain the attribute information and source information of the breakpoint task, where the breakpoint task refers to a task generated after the residence time of the user in at least one registration link exceeds the preset timeout duration during the online registration process.

[0088] The online registration process includes multiple registration links. Taking the online registration of a bank application (APP) as an example, the registration links include: setting a user name, setting a login password, filling in a registered mobile phone number, entering a bank card number, and identity verification, etc. Taking the online registration of a video APP as an example, the registration links include: setting a login password and filling in a registered mobile phone number, etc.

[0089] The preset timeout duration corresponding to each registration link can be the same or different. For example, the preset timeout duration can be set separately for different registration links according to the user operation difficulty and data transmission requirements of different registration links. Among them, when the business organization includes a multi-layer structure of headquarters and branches, the staff setting the preset timeout duration can be the headquarters staff; when the business organization is a single-layer structure, the staff setting the preset timeout duration can be the designated personnel of the business organization.

[0090] For example, the identity authentication process needs to verify whether the username of the bank card number entered by the user is the username set by the user, send a verification code to the registered mobile phone number filled in by the user and receive the verification code filled in by the user, and then verify whether the received verification code is the sent verification code, etc. Therefore, the data transmission requirements are high and the user operation is difficult, so a longer preset timeout period can be set, such as 10 minutes. The username setting process needs to receive a username entered by the user, so the data transmission requirements are low and the user operation is not difficult, so a shorter preset timeout period can be set, such as 5 minutes.

[0091] The electronic device can detect the start time of each registration link according to the user operation in the registration process. If a registration link has not been completed, and the duration from the start time of the registration link to the current time, that is, the dwell time, exceeds the preset timeout duration corresponding to the registration link, then a breakpoint task can be generated. On the contrary, if the dwell time of each registration link in the registration process does not exceed the preset timeout duration corresponding to the registration link, then no breakpoint task is generated for the registration process.

[0092] The attribute information of the breakpoint task includes: basic attributes and derived attributes. Among them, the basic attributes include: timestamp, registered mobile phone number and the registration link where the breakpoint occurs. For example, the timestamp can be the time when the breakpoint task is generated, the time when the user operation is last detected during the registration process, or other times during the registration process. Derived attributes include: the location information of the registered mobile phone number, the bank information of the bank card number, and the selected business department information.

[0093] The electronic device may pre-record various channel information corresponding to uniform resource locator (URL), which can be used to find the channel information corresponding to the URL used when entering the registration page during the registration process to which the breakpoint task belongs. The channel information indicates the channel for entering the online registration, for example, the channel information includes: live broadcast, offline advertising or text messages, etc.

[0094] S102: Determine a person who handles the breakpoint task based on the attribute information and the source information.

[0095] Among them, the attribute information can reflect the task type of the breakpoint task, and the source information can reflect the source of the online registration. In the embodiment of the present application, different handlers can be configured in advance for breakpoint tasks of different types and sources. Therefore, the handler of this breakpoint task can be determined based on the attribute information and source information. The specific method of determining the handler can be described below.

[0096] S103: Push the breakpoint task to the user device associated with the processor, so that the processor provides online registration guidance for the user according to the breakpoint task.

[0097] Among them, the electronic device can pre-record the device identifiers corresponding to each employee who supports processing breakpoint tasks. For example, it can record the Internet Protocol (IP) addresses of the work computers corresponding to each employee. When executing S103, the electronic device can push the breakpoint task to the user device to which the device identifier corresponding to the handler belongs, and the handler can view the breakpoint task through this user device.

[0098] Alternatively, the electronic device can pre-record the accounts corresponding to each employee who supports processing breakpoint tasks. For example, it can record the instant messaging accounts within the business organization corresponding to each employee. When executing S103, the electronic device can push the breakpoint task to the account corresponding to the handler, and the handler can view the breakpoint task through the user device that logs in to this account.

[0099] Among them, the pushed breakpoint task can include: task identifier, attribute information, source information, etc., so that the handler can contact the user based on the breakpoint task and provide professional online registration guidance for the user.

[0100] For example, the handler can call the registered mobile phone number of the breakpoint task and assist the user in online registration by phone. Another example is that the handler can add the instant messaging account of the user based on the registered mobile phone number, send the online registration tutorial to the user's instant messaging account, and assist the user in online registration through a voice call. Or, the handler can also provide online registration guidance for the user in other ways, and the embodiments of the present application do not make specific limitations on this.

[0101] The breakpoint task processing method provided by the embodiments of the present application can, after a breakpoint occurs, determine the handler of the breakpoint task according to the attribute information and source information of the breakpoint task, and send the breakpoint task to the handler, so that the handler can provide online registration guidance for the user based on the breakpoint task. That is, it enables the user to obtain professional guidance from the staff without reaching the physical office, reduces the difficulty of online registration, thus improving the user's online registration experience and reducing user churn.

[0102] The following details the breakpoint task processing method provided by the embodiments of the present application:

[0103] The embodiments of the present application support staff to set the dispatch date of breakpoint tasks. Among them, the electronic device can receive the dispatch date information input by the staff through its own external keyboard, mouse and other devices, or the electronic device can receive the dispatch date information sent by the staff through the client. When the business organization is a multi-layer structure including headquarters and branches, the staff who set the dispatch date information can be the headquarters staff; when the business organization is a single-layer structure, the staff who set the dispatch date information can be the designated personnel of the business organization. The dispatch date information includes: preset whitelist, preset whitelist rules, preset blacklist and preset blacklist rules.

[0104] Among them, the preset whitelist includes the specified dates allowed for task dispatch, and the preset blacklist includes the specified dates not allowed for task dispatch. For example, assume that the staff of the business organization have fixed working days on the 1st and 15th of each month, and fixed rest days on the 10th and 20th of each month. Then the preset whitelist includes the 1st and 15th of each month, and the preset blacklist includes the 10th and 20th of each month. Another example, assume that the business organization holds a large-scale event from June 1st to 5th. During this period, the staff of the business organization need to specifically serve this event. Therefore, the preset blacklist can be set to include June 1st to 5th.

[0105] Among them, the staff can select options such as working days, natural days, trading days, legal holidays, etc., and connect each option through predicate logics such as AND, OR, NOT, etc. to form preset whitelist rules or preset blacklist rules. The preset whitelist rules are the rules that the dates allowed for task dispatch need to meet, and the preset blacklist rules are the rules that the dates not allowed for task dispatch need to meet. For example, the preset whitelist rule is: working days AND trading days; the preset blacklist rule is: non-working days AND legal holidays.

[0106] The embodiments of the present application also support staff to set the dispatch time period of breakpoint tasks. Among them, the value range of the dispatch time period is from 0 to 24 hours. The electronic device can receive the start time and end time of the dispatch time period input by the staff through its own external keyboard, mouse and other devices, or the electronic device can receive the start time and end time of the dispatch time period sent by the staff through the client.

[0107] The embodiments of the present application also support staff to set the task dispatch status to the on state or the off state. Among them, the task dispatch status can also be called the total task dispatch switch. The on state indicates that breakpoint task dispatch is allowed, and the off state indicates that breakpoint task dispatch is not allowed. The electronic device can receive the task dispatch status selected by the staff through its own external keyboard, mouse and other devices, or the electronic device can receive the task dispatch status sent by the staff through the client.

[0108] Under normal circumstances, the task distribution status is defaulted to the open state. In case of special circumstances, the staff can set it to the closed state. For example, in the event of an emergency such as a natural disaster, the staff can send a message to the electronic device through the client that the task distribution status is in the closed state. At this time, the electronic device can update the task distribution status to the closed state in real time, so as to stop the task distribution in a timely manner.

[0109] Based on this, before the task distribution process shown in Figure 1 , the electronic device can first determine whether the current time supports task distribution. That is, as shown in Figure 2 , the electronic device can also perform the following steps:

[0110] Step 1: Check whether the current date is in the preset whitelist. If the current date is not in the preset whitelist, then execute Step 2. If the current date is in the preset whitelist, then execute Step 3.

[0111] Step 2: Determine whether the current date meets the preset whitelist rules, is not in the preset blacklist, and does not meet the preset blacklist rules.

[0112] If all the judgment results are yes, then execute Step 3.

[0113] If any of the judgment results is no, then execute Step 4.

[0114] That is, as shown in Figure 2 , the electronic device can determine whether the current date meets the preset whitelist rules. If not, then execute Step 4. If so, then determine whether the current date is not in the preset blacklist. If not, then execute Step 4. If so, then determine whether the current date does not meet the preset blacklist rules. If not, then execute Step 4. If so, then execute Step 3.

[0115] Step 3: Verify whether the current moment belongs to the preset distribution time period and whether the task distribution status is in the open state.

[0116] If any of the verification results is no, then execute Step 4.

[0117] If all the verification results in Step 3 are yes, then it is determined that the task can be distributed, and the subsequent task distribution process shown in Figure 1 can be executed.

[0118] That is, as shown in Figure 2 , the electronic device can verify whether the current moment is greater than or equal to the start moment of the preset distribution time period. If not, then execute Step 4. If so, then verify whether the current moment is less than or equal to the end moment of the preset distribution time period. If not, then execute Step 4. If so, then verify whether the task distribution status is in the open state. If not, then execute Step 4. If so, then it is determined that the task can be distributed.

[0119] Step 4: Determine that the task cannot be dispatched. After waiting for a preset duration, return to Step 1 to check whether the current date is within the preset whitelist.

[0120] Among them, the preset duration can be set according to the actual application scenario. For example, the preset duration is 1 minute.

[0121] It should be noted that in the embodiments of the present application, before dispatching each breakpoint task, it can be determined whether the breakpoint task can be dispatched in the manner shown by Figure 2 and when it can be dispatched, the breakpoint task is dispatched in the manner shown by Figure 1 . Alternatively, in the embodiments of the present application, every preset duration, it can be determined whether task dispatching is allowed at present in the manner shown by Figure 2 . If so, it is dispatched in the manner shown by Figure 1 .

[0122] The dispatchable time of the breakpoint task in the embodiments of the present application can be expressed as: F = F1 and F2 and F3 = F1 and (F21 or (F22 and not (F23 or F24))) and (F31 and F32). Among them, F is the dispatchable time, F1 indicates that the task dispatch status is in the enabled state, F2 = F21 or (F22 and not (F23 or F24)), F21 indicates that the current date is within the preset whitelist, F22 indicates that the current date meets the preset whitelist rules, F23 indicates that the current date meets the preset blacklist rules, F24 indicates that the current date is within the preset blacklist, F3 = F31 and F32, F31 indicates that the current moment is greater than or equal to the start moment of the preset dispatch time period, and F32 indicates that the current moment is less than or equal to the end moment of the preset dispatch time period.

[0123] Through the above method, the embodiments of the present application can sequentially judge according to the priority order of whether the current moment is within the preset whitelist, meets the preset whitelist rules, is within the preset blacklist, and meets the preset blacklist rules, so as to obtain whether task dispatching is allowed at present, improving the accuracy and efficiency of task dispatching.

[0124] Moreover, since the preset whitelist, preset whitelist rules, preset blacklist, and preset blacklist rules all support being updated at any time, that is, the time when task dispatching is allowed may change at any time. Therefore, the electronic device in the embodiments of the present application can periodically and continuously judge whether task dispatching can be performed at the current time, improving the accuracy and flexibility of the task dispatching time.

[0125] In some embodiments of the present application, the method for determining the processor of the breakpoint task according to the attribute information and source information in S102 includes the following steps:

[0126] Step 1: Determine the eigenvalue corresponding to the attribute information and the eigenvalue corresponding to the source information.

[0127] The electronic device can pre-record the correspondence between each type of attribute information and the eigenvalue, so as to determine the eigenvalue corresponding to the attribute information of the breakpoint task according to this correspondence. Moreover, the electronic device can pre-record the correspondence between each type of source information and the eigenvalue, so as to determine the eigenvalue corresponding to the source information of the breakpoint task according to this correspondence.

[0128] For example, the correspondence between each type of attribute information and the eigenvalue is shown in Table 1:

[0129] Table 1

[0130] Attribute information Characteristic value Registration process a 1 Registration process b 2 Registration process c 3 Region A 1 Region B 2 Region C 3

[0131] The correspondence between each type of source information and the eigenvalue is shown in Table 2:

[0132] Table 2

[0133] Source information Characteristic value Channel 1 1 Channel 2 2 Channel 3 3

[0134] Suppose that the registration link where the breakpoint occurs in a breakpoint task is registration link a, then the corresponding eigenvalue is 1; and the territorial information of the registered mobile phone number included in this breakpoint task is region B, then the corresponding eigenvalue is 2; and the channel information included in this breakpoint task is channel 3, then the corresponding eigenvalue is 3.

[0135] Step 2: Determine the product of the eigenvalue corresponding to the attribute information and the weight corresponding to the attribute information, and the product of the eigenvalue corresponding to the source information and the weight corresponding to the source information.

[0136] The electronic device can pre-record the correspondence between each type of attribute information and the weight, and the correspondence between each type of source information and the weight.

[0137] For example, suppose the eigenvalue corresponding to the registration link where the breakpoint occurs is 1 and the weight is 0.3, then the product is 1×0.3 = 0.3; and the eigenvalue corresponding to the territorial information of the registered mobile phone number is 2 and the weight is 0.2, the product is 2×0.2 = 0.4; and the eigenvalue corresponding to the channel information is 3 and the weight is 0.5, then the product is 3×0.5 = 1.5.

[0138] Step 3: Based on the preset mapping rule, determine the target task level mapped by each product from the preset task levels.

[0139] Among them, the preset mapping rule represents the rule for mapping each product to the task level. The task level can also be called the priority of the task.

[0140] For example, the preset mapping rule includes: each task level corresponds to a numerical range, the products are summed up, and the task level corresponding to the numerical range to which the sum value belongs is used as the target task level.

[0141] Another example is that the preset mapping rule includes: each task level corresponds to a numerical value, the products are concatenated, a hash operation is performed on the concatenated result, and the task level corresponding to the obtained hash value is used as the target task level.

[0142] Alternatively, the preset mapping rule can also be other rules, and specific limitations are not made in this embodiment of the present application.

[0143] In the embodiment of the present application, the target task level can be expressed as: p = P(f(S(C, W), R)). Where p represents the target task level, P represents the preset task level set, C represents the set of characteristic values of the breakpoint task, W represents the weight set, S represents the weighted characteristic value set, that is, the product set, R represents the preset mapping rule, and f represents the value obtained by mapping each product based on the mapping rule.

[0144] Step 4: Select the handler of the breakpoint task from the white list of handlers corresponding to the target task level.

[0145] Among them, the white list of handlers corresponding to each task level includes one or more handlers.

[0146] When the white list of handlers corresponding to the target task level includes multiple handlers, the electronic device can select the handler with the least amount of tasks dispatched during the current dispatch period from these multiple handlers as the handler of the breakpoint task. Among them, the dispatch period can be set according to actual needs. For example, each dispatch period is a natural day.

[0147] Alternatively, the electronic device can also select a handler from the white list of handlers corresponding to the target task level in other ways, and specific limitations are not made in this embodiment of the present application.

[0148] In the embodiment of the present application, the handler of the breakpoint task can not only provide online registration guidance for the user. After the user successfully completes online registration, there is still an association relationship between the handler and the user, that is, the handler can also provide other guidance such as transfer or transaction for the user.

[0149] Embodiments of the present application can preset multiple task levels and configure the executor corresponding to each task level, so that when the electronic device dispatches a task, it can determine the task level of the breakpoint task according to the attribute information and source information of the breakpoint task, and then dispatch the breakpoint task to the executor corresponding to the task level. This method realizes the division of task levels for breakpoint tasks, so that more suitable processors can be configured for different task levels respectively, thereby improving the efficiency and success rate of the processor in processing breakpoint tasks.

[0150] In some embodiments of the present application, the electronic device also supports configuring a corresponding processor for each task level.

[0151] That is, the electronic device can also receive configuration information, where the configuration information includes candidates configured by the initial configurator for a single task level, and determine whether the candidates support task execution.

[0152] If so, the candidate is used as the executor of the task level and added to the whitelist of executors corresponding to the task level.

[0153] If not, the candidates configured by the candidate for the task level are received, and the step of determining whether the candidates support task execution is returned.

[0154] In embodiments of the present application, the candidate can be a grass-roots employee who supports task execution, or a manager who does not support task execution. The electronic device can pre-record whether each employee belongs to a grass-roots employee or a manager.

[0155] When the candidate is a grass-roots employee, the electronic device can determine that the candidate supports task execution and use the candidate as the processor of the task level.

[0156] When the candidate is a manager, the electronic device can send a configuration request to the user device associated with the candidate, where the configuration request is used to request to configure candidates for the task level. After that, the user device can display a configuration interface, receive the candidates configured for the task level within the configuration interface, and send a configuration response to the electronic device. The configuration response includes the candidates of the task level received by the user device. After that, the electronic device can obtain the candidates of the task level from the configuration response and continue to determine whether the candidates support task execution based on the obtained candidates.

[0157] Taking the multi-layer structure of the business organization as the headquarters and branches as an example, the process of configuring the processors of each task level is as Figure 3 shown. See Figure 3, the headquarters staff can select a task level through the user device associated with themselves, configure the candidates corresponding to the task level, and then send the configuration information to the electronic device, where the configuration information includes the candidates corresponding to the task level. The electronic device determines whether the candidate is a grass-roots employee. If so, the candidate is used as the executor of the task level and added to the white list of executors corresponding to the task level.

[0158] If not, the electronic device can determine the candidate as the manager of the branch and add it to the white list of branch managers. Then, a configuration request is sent to the user device associated with the manager of the branch, so that the manager of the branch can configure the candidates for the task level through the user device. Then, the electronic device receives the configuration response sent by the user device, obtains the candidates for the task level from the configuration response, and returns to the step of determining whether the candidate is a grass-roots employee. If the judgment result is still no, the electronic device can determine the candidate as the subordinate manager of the branch manager and add it to the white list of branch managers. Then, a configuration request is sent to the user device associated with the subordinate manager, and the candidates for the task level are obtained from the received configuration response, and the step of determining whether the candidate is a grass-roots employee is returned, and so on.

[0159] Through the above method, the embodiments of the present application support configuring a white list of executors for each task level, and new executors can be added to the white list of executors. Compared with unified management of all executors, the embodiments of the present application can manage the executors of different task levels separately. Therefore, the management granularity is finer, and the executors of different task levels can be configured more flexibly.

[0160] Among them, the user devices associated with each person in the embodiments of the present application all have a display screen, so as to display the application program interface through the display screen and receive information such as candidates to be configured within the application program interface.

[0161] In some embodiments of the present application, the electronic device can also eliminate some executors based on the situation of each executor in each execution white list processing tasks. That is, see Figure 4 , the electronic device can also perform the following steps:

[0162] S401. For the white list of executors corresponding to each task level, obtain the statistical values of each task statistic item of each executor who has executed the breakpoint task in the white list of executors.

[0163] The electronic device can perform periodically Figure 4The elimination process shown is to perform an elimination process every other elimination cycle. Among them, the elimination cycle can be set according to actual needs. For example, the elimination cycle is 7 days. The electronic device can obtain, for each task level, the statistical values of each task statistical item of each executor in the executor white list corresponding to that task level in the previous elimination cycle.

[0164] Among them, the task processing statistical values include: observation time interval, task processing volume, task conversion rate, and task conversion amount, etc.

[0165] The observation time interval is the time interval to which the duration between the moment of viewing the breakpoint task and the moment of contacting the user belongs. For example, the electronic device pre - records multiple time intervals, such as [0,60), [60,120), and [120,∞], with the unit being seconds. Assuming that the duration between the executor viewing the breakpoint task and contacting the user is 60 seconds, then the observation time interval is [60,120). For example, the user device associated with the executor can use the moment of displaying the breakpoint task as the moment when the executor views the breakpoint task, and the moment when the executor clicks the call button as the moment when the executor contacts the user. When the task statistical item includes the observation time interval, a value can be taken from the observation time interval and multiplied by the weight corresponding to the observation time interval. For example, the minimum value of the observation time interval is taken.

[0166] The task processing volume is the number of executed breakpoint tasks.

[0167] The task conversion rate is: the probability that the user successfully completes online registration after the executor contacts the user. That is, the task conversion rate is: the proportion of the number of users who successfully complete online registration after the executor contacts the user in the previous elimination cycle in the task reception volume of the executor in the previous elimination cycle.

[0168] The task conversion amount is: the total transaction amount of the subject matter provided by the business institution by the user who successfully completes online registration after the executor contacts the user and within a certain duration after registration. Among them, the certain duration can be set according to actual needs. For example, it is 3 days. Taking the financial scenario as an example, the subject matter provided by the business institution can be: stocks, funds, or bonds, etc.

[0169] To reduce the influence of different dimensions of different statistical items on calculating the processing score, the electronic device can also normalize the statistical values of each task statistical item, and then calculate the product of the normalized statistical value and the weight.

[0170] S402. For each executor, determine the processing score of the executor based on the statistical values of the executor.

[0171] When determining the processing score of each executor, the electronic device can calculate the statistical value for each task statistic item, determine the product of the statistical value and the weight corresponding to the task statistic item, and then calculate the products through a preset calculation method to obtain the processing score of the executor. Among them, the preset calculation method can be summation, taking the average value, or taking the maximum value, etc.

[0172] For example, the corresponding relationship between each task statistic item and the weight is shown in Table 3.

[0173] Table 3

[0174] Task statistics item Weight Observation time interval 0.2 Task processing volume 0.2 Task conversion rate 0.3 Task conversion amount 0.3

[0175] Combined with Table 3, assuming that after normalization, the observation time interval of an executor is 0.5, the task processing volume is 0.6, the task conversion rate is 0.8, and the task conversion amount is 0.7, and assuming that the preset calculation method is summation, then the processing score of this executor is: 0.5×0.2 + 0.6×0.2 + 0.8×0.3 + 0.7×0.3 = 0.67.

[0176] S403. Screen out the executors to be eliminated whose processing scores are lower than the preset threshold corresponding to this task level, and delete the executors to be eliminated from the white list of this executor.

[0177] The embodiments of this application support the staff to set the preset threshold corresponding to each task level. When the business organization is a multi-layer structure including the headquarters and branches, the staff setting the preset threshold can be the headquarters staff; when the business organization is a single-layer structure, the staff setting the preset threshold can be the designated personnel of the business organization.

[0178] The executor to be eliminated can be expressed as: d = (f(S(C, W), R) < T). Where d represents the executor to be eliminated, C represents the set of statistical values of each task statistic item for which the executor has executed breakpoint tasks, W represents the set of weights corresponding to each task statistic item, S represents the set of products of statistical values and weights, R represents the preset calculation method, f represents the processing score of the executor, and T represents the set of preset thresholds corresponding to each task level.

[0179] Through the above method, the embodiments of this application can determine the processing score of the executor in combination with the situation of the executor executing breakpoint tasks, and delete the executor with a lower processing score, thereby improving the processing efficiency, conversion rate, and conversion amount of breakpoint tasks, and bringing higher benefits to the business organization.

[0180] After deleting the executor to be eliminated, the electronic device can also add an executor to the white list of the executor corresponding to this task level, including the following steps:

[0181] Step Ⅰ: Determine the target configurator for configuring the executors to be phased out for this task level.

[0182] Among them, in combination with the above process of configuring executors for the task level, the target configurator can be the initial configurator or the candidate.

[0183] Step Ⅱ: Obtain the new executors added by the target configurator for this task level and add them to the executor whitelist corresponding to this task level.

[0184] The electronic device can send a configuration request to the user device associated with the target configurator, then receive the configuration response sent by the user device associated with the target configurator, and obtain the new executors added by the target configurator for this task level from the configuration response.

[0185] Through the above method, the embodiments of the present application can timely supplement the executor whitelist after deleting the executors to be phased out, reducing the situation where the number of people included in the executor whitelist is too small, resulting in too many breakpoint tasks assigned to each executor, and improving the execution efficiency of breakpoint tasks.

[0186] As Figure 5 shown, the following takes an actual application scenario as an example to illustrate the overall process of the electronic device phasing out executors and adding new executors:

[0187] For the executor whitelist corresponding to each task level, obtain the statistical values of each task statistical item of each executor in the executor whitelist. Then, for each executor, determine the processing score of the executor based on the statistical values of the executor, and determine whether the processing score is lower than the preset threshold corresponding to this task level. If so, determine that the executor is an executor to be phased out, and delete the executor to be phased out from the executor whitelist, that is, phase out the executor; if not, retain the executor in the executor whitelist.

[0188] Determine the target configurator for configuring the executors to be phased out for this task level, send a configuration request to the user device associated with the target configurator, then receive the configuration response sent by the user device associated with the target configurator, and obtain the executors configured by the target configurator for this task level from the configuration response and add them to the executor whitelist corresponding to this task level.

[0189] See Figure 6 , the following takes an actual application scenario as an example to illustrate the overall process of task distribution involved in the embodiments of the present application:

[0190] S601: Real-time detect breakpoint events during the online registration process.

[0191] Among them, the electronic device can obtain the operation behavior data of the user during online registration in real time, so as to detect whether the residence time of the user in at least one registration link exceeds the preset timeout duration. If so, a breakpoint event is generated.

[0192] S602. Perform customer retention filtering on the detected breakpoint events.

[0193] The breakpoint event includes information such as the registration link where the residence time exceeds the preset timeout duration, the registered mobile phone number, and the user name. The electronic device can check whether the user name is the user name of an existing customer, or check whether the registered mobile phone number is the registered mobile phone number of an existing customer. If so, filter the breakpoint event; if not, retain the breakpoint event.

[0194] S603. Generate breakpoint tasks based on each retained breakpoint event after filtering.

[0195] S604. Dispatch the breakpoint tasks.

[0196] The process of task dispatching can refer to the relevant description above Figure 1 and will not be elaborated here.

[0197] S605. Perform message push based on the dispatched breakpoint tasks.

[0198] The electronic device can count the total number of dispatched breakpoint tasks in each time period, and at the end of each time period, send the total number of dispatched breakpoint tasks in this time period to the user device associated with the headquarters staff. Among them, the duration of each time period can be set according to the actual application scenario. For example, the duration of each time period is 1 hour. The headquarters staff can be the managers in the headquarters who configure the executors for the task level.

[0199] The electronic device can pre-record the branch to which each handler belongs. For each branch, count the number of breakpoint tasks dispatched to the handlers of this branch in each time period, and at the end of each time period, send the number of breakpoint tasks dispatched to the handlers of this branch in this time period to the user device associated with the staff of this branch. So that the branch staff can timely understand the overall task volume dispatched to this branch, and then supervise and assist each executor to complete the breakpoint tasks in a timely manner. Among them, the branch staff can be the managers in the branch who configure the executors for the task level.

[0200] After dispatching each breakpoint task, the electronic device can promptly push a reminder message to the user device associated with the person to whom the breakpoint task is dispatched. Moreover, for each breakpoint task, the electronic device can detect whether the waiting duration after dispatching the breakpoint task and before the person processes it exceeds the specified duration. If so, an instant messaging reminder message within the business organization is sent to the user device associated with the person, and / or a reminder message is sent to the user device associated with the person through an intelligent outbound call robot. The reminder message can include: breakpoint task identifier, breakpoint task dispatch time, waiting duration, etc. This realizes timely reminding the person to process the breakpoint task, thereby minimizing the loss of users who experience breakpoints during online registration to the greatest extent.

[0201] After dispatching each breakpoint task, the electronic device can send a notification message to the user device associated with the user targeted by the breakpoint task. For example, a notification message is sent to the registered mobile phone number included in the breakpoint task to prompt the user that a breakpoint has occurred during the online registration process and that a staff member will provide assistance later, enabling the user to be mentally prepared to receive the help in advance.

[0202] S606: Obtain the processing information generated by the person processing the breakpoint task.

[0203] In one implementation, the person can perform the breakpoint task online through the user device associated with themselves. For example, by using the network phone function configured on the user device to call the registered mobile phone number, thereby contacting the user through the network phone and providing online registration guidance. At this time, the user device associated with the person can record processing information such as the time interval during which the person observes the breakpoint task, the start time, end time, call duration, and call recording of the network phone, and send the processing information to the electronic device.

[0204] In the embodiments of this application, the registered mobile phone number included in the breakpoint task can be an encrypted version of the mobile phone number obtained by encrypting the mobile phone number filled in by the user, so that when the person views the breakpoint task, only the encrypted version of the mobile phone number can be obtained, thus avoiding the leakage of the user's privacy. When the person triggers a call to the registered mobile phone number on the user device associated with themselves, the electronic device can decrypt the encrypted version of the mobile phone number and call the decrypted registered mobile phone number.

[0205] In another implementation, the person can perform the breakpoint task through a device other than the user device already associated with them. For example, by using the landline or mobile phone of the person to call the registered mobile phone number, thereby contacting the user by phone and providing online registration guidance. At this time, the person can upload processing information such as the time interval during which the person observes the breakpoint task, the start time, end time, call duration, and call recording of the phone to the user device already associated with them, and then the user device sends the processing information to the electronic device.

[0206] S607. Determine the statistical values of each task statistic item of the processor based on the processing information of each processor.

[0207] For the method of determining the statistical values of each task statistic item, reference can be made to the above relevant description, which will not be elaborated here.

[0208] S608. Conduct summary analysis on each statistical value.

[0209] The electronic device can summarize based on each statistical value and generate a report, and send the report to the user devices associated with the headquarters staff and the staff of each branch respectively.

[0210] The electronic device can also track in real time the online registration result of the user targeted by the processed breakpoint task, such as the registration result is successful registration or failed registration, and send the registration result to the processor of the breakpoint task.

[0211] For business institutions, the embodiments of the present application support customized task distribution rules, including time configuration of distributable tasks, task level configuration, executor configuration corresponding to different task levels, preset threshold configuration for eliminating executors, and preset timeout duration configuration for checking breakpoints, etc., which improves the flexibility of task distribution. It can be continuously adjusted according to the changes in business and the execution situation of breakpoint tasks in the actual application scenario, ensuring that the distribution rules of breakpoint tasks can meet the requirements of various management granularities and various marketing and service scenarios. Moreover, the configured various rules can take effect in real time, reducing the delay in processing breakpoint tasks caused by rule adjustment and resulting in user loss. In addition, the embodiments of the present application can make full use of existing resources for task distribution, such as determining breakpoint users based on information such as registered mobile phone numbers and user names generated during the online registration process, realizing low-cost screening of unregistered users with the intention of registration.

[0212] At the same time, for the branches of business institutions, in the traditional scenario, before establishing a service relationship with a user whose online registration fails, the branch employees need to go through a cumbersome approval process and retrieve various relevant information of the user to get familiar with the user, resulting in heavy workload and low efficiency of the branch employees. In addition, there is also the problem of repeated harassment to users caused by different branch employees establishing service relationships with the same user. In the embodiments of the present application, the branch employees can be assigned breakpoint tasks, so there is no need to manually establish a service relationship with the user, eliminating the cumbersome approval process and information retrieval process; moreover, the breakpoint tasks are assigned to one employee, so the problem of repeated harassment caused by users is reduced.

[0213] In addition, for users, after a breakpoint occurs during online registration, they can obtain timely manual guidance and achieve the same experience as offline registration. Moreover, users do not need to fill in too much privacy information during online registration. By using the registered mobile phone number authorized by the user, the breakpoint task can be dispatched. The authorization information filled in by the user during online registration is only used within the business institution and is not publicly disclosed, ensuring the user's information security and avoiding privacy leakage.

[0214] Based on the same inventive concept, corresponding to the above method embodiments, the embodiments of the present application further provide a breakpoint task processing device, as Figure 7 shown. The device includes: an acquisition module 701, a determination module 702, and a push module 703;

[0215] The acquisition module 701 is configured to acquire the attribute information and source information of the breakpoint task. The breakpoint task represents a task generated after the residence time of the user in at least one registration link during the online registration process exceeds a preset timeout duration;

[0216] The determination module 702 is configured to determine the handler of the breakpoint task according to the attribute information and source information;

[0217] The push module 703 is configured to push the breakpoint task to the user device associated with the handler, so that the handler provides online registration guidance for the user according to the breakpoint task.

[0218] Optionally, the device further includes a verification module, and the verification module is configured to:

[0219] Before acquiring the attribute information and source information of the breakpoint task, check whether the current date is within a preset whitelist;

[0220] If the current date is not within the preset whitelist, then determine whether the current date meets the preset whitelist rules, is not within the preset blacklist, and does not meet the preset blacklist rules;

[0221] If the current date is within the preset whitelist or the judgment results are all yes, then verify whether the current moment belongs to the preset dispatch time period and whether the task dispatch status is the open state;

[0222] If the verification results are all yes, then call the acquisition module 701 to execute the step of acquiring the attribute information and source information of the breakpoint task;

[0223] If any judgment result is no or any verification result is no, then wait for a preset duration and return to the step of checking whether the current date is within the preset whitelist.

[0224] Optionally, the determination module 702 is specifically configured to:

[0225] Determine the eigenvalue corresponding to the attribute information and the eigenvalue corresponding to the source information;

[0226] Determine the product of the eigenvalue corresponding to the attribute information and the weight corresponding to the attribute information, and the product of the eigenvalue corresponding to the source information and the weight corresponding to the source information;

[0227] Based on the preset mapping rules, determine the target task level mapped by each product from the preset task levels;

[0228] Select the handler for the breakpoint task from the white list of task handlers corresponding to the target task level.

[0229] Optionally, the device further includes a configuration module, and the configuration module is used for:

[0230] Receive configuration information, where the configuration information includes candidates configured by the initial configurator for a single task level;

[0231] Determine whether the candidate supports task execution;

[0232] If so, use the candidate as the task handler for this task level and add the candidate to the white list of task handlers corresponding to this task level;

[0233] If not, obtain the candidates configured by the candidate for this task level, and return to the step of determining whether the candidate supports task execution.

[0234] Optionally, the device further includes an elimination module, and the elimination module is used for:

[0235] For the white list of task handlers corresponding to each task level, obtain the statistical values of each task statistic item for which each task handler in the white list of task handlers has executed the breakpoint task;

[0236] For each task handler, determine the processing score of the task handler based on the statistical values of the task handler;

[0237] Screen out the task handlers to be eliminated whose processing scores are lower than the preset threshold corresponding to this task level;

[0238] Delete the task handlers to be eliminated from the white list of task handlers.

[0239] Optionally, the elimination module is specifically used for:

[0240] For the statistical value of each task statistic item, determine the product of the statistical value and the weight corresponding to the task statistic item;

[0241] Calculate each product through a preset calculation method to obtain the processing score of the task handler.

[0242] Optionally, the device further includes an addition module, and the addition module is used for:

[0243] After deleting the executor to be phased out from the white list of the executor, determine the target configurator who configures the executor to be phased out for this task level;

[0244] Obtain the executors newly added by the target configurator for this task level, and add them to the white list of executors corresponding to this task level.

[0245] The embodiment of the present application also provides an electronic device, as Figure 8 shown, including a processor 801, a communication interface 802, a memory 803, and a communication bus 804. Among them, the processor 801, the communication interface 802, and the memory 803 complete mutual communication through the communication bus 804.

[0246] The memory 803 is used to store a computer program;

[0247] When the processor 801 is used to execute the program stored on the memory 803, it implements the method steps executed by the electronic device in the above method embodiment.

[0248] The communication bus mentioned in the above electronic device may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of simplicity, only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

[0249] The communication interface is used for communication between the above electronic device and other devices.

[0250] The memory may include a Random Access Memory (RAM), or may also include a Non-Volatile Memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located far from the aforementioned processor.

[0251] The above-mentioned processor can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0252] In another embodiment provided by the present application, a computer-readable storage medium is further provided. A computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the steps of any of the above breakpoint task processing methods are implemented.

[0253] In another embodiment provided by the present application, a computer program product containing instructions is further provided. When it runs on a computer, the computer is made to execute any of the breakpoint task processing methods in the above embodiments.

[0254] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer, or a data storage device such as a server or data center that includes one or more integrated available media. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a Solid State Disk (SSD)).

[0255] It should be noted that in this document, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprising", "including" or any other variant thereof are intended to cover non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or device comprising the said element.

[0256] Each embodiment in this specification is described in a related manner. For the same or similar parts among the embodiments, reference can be made to each other, and the differences between each embodiment and other embodiments are emphasized. In particular, for the device embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and reference can be made to the relevant parts of the method embodiments for the relevant content.

[0257] The above are only the preferred embodiments of the present application and are not used to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application are included within the protection scope of the present application.

Claims

1. A breakpoint task processing method, characterized in that, The method includes: Obtaining the attribute information and source information of a breakpoint task, where the breakpoint task represents a task generated after the residence time of a user in at least one registration link exceeds a preset timeout duration during the online registration process; Determining the handler of the breakpoint task based on the attribute information and the source information; Pushing the breakpoint task to the user device associated with the handler, so that the handler provides online registration guidance for the user based on the breakpoint task.

2. The method according to claim 1, characterized in that, Before obtaining the attribute information and source information of the breakpoint task, it further includes: Checking whether the current date is within a preset whitelist; If the current date is not within the preset whitelist, then determining whether the current date meets the preset whitelist rules, is not within the preset blacklist, and does not meet the preset blacklist rules; If the current date is within the preset whitelist or the judgment results are all yes, then verifying whether the current moment belongs to a preset dispatching time period and whether the task dispatching status is an open status; If the verification results are all yes, then execute the step of obtaining the attribute information and source information of the breakpoint task; If any judgment result is no or any verification result is no, then after waiting for a preset duration, return to the step of checking whether the current date is within the preset whitelist.

3. The method according to claim 1, wherein The determining the handler of the breakpoint task based on the attribute information and the source information includes: Determining the eigenvalue corresponding to the attribute information and the eigenvalue corresponding to the source information; Determining the product of the eigenvalue corresponding to the attribute information and the weight corresponding to the attribute information, and the product of the eigenvalue corresponding to the source information and the weight corresponding to the source information; Based on a preset mapping rule, determining the target task level mapped by each product from each preset task level; Selecting the handler of the breakpoint task from the executor whitelist corresponding to the target task level.

4. The method according to claim 3, characterized in that, The method further includes: Receiving configuration information, where the configuration information includes candidates configured for a single task level by an initial configurator; Judging whether the candidate supports task execution; If so, using the candidate as the executor of this task level and adding the candidate to the executor whitelist corresponding to this task level; If not, obtaining the candidates configured by the candidate for this task level and returning to the step of judging whether the candidate supports task execution.

5. The method according to claim 3 or 4, characterized in that, The method further includes: For each executor whitelist corresponding to a task level, obtaining the statistical values of each task statistic item of the breakpoint tasks already executed by each executor in the executor whitelist; For each executor, determining the processing score of the executor based on the statistical values of the executor; Screening out the executors to be eliminated whose processing scores are lower than the preset threshold corresponding to this task level; Deleting the executors to be eliminated from the executor whitelist.

6. The method according to claim 5, characterized in that, The determining the processing score of the executor based on the statistical values of the executor includes: For the statistical value of each task statistic item, determining the product of the statistical value and the weight corresponding to this task statistic item; Calculating each product through a preset calculation method to obtain the processing score of this handler.

7. The method according to claim 5, characterized in that After deleting the executors to be eliminated from the executor whitelist, it further includes: Determine the target configurator for the task level to configure the executor to be phased out; Obtain the executors newly added by the target configurator for this task level, and add them to the executor whitelist corresponding to this task level.

8. A breakpoint task processing device, characterized in that, The device includes: An obtaining module, configured to obtain the attribute information and source information of a breakpoint task, where the breakpoint task represents: a task generated after the residence time of a user in at least one registration link exceeds a preset timeout duration during the online registration process; A determining module, configured to determine the handler of the breakpoint task according to the attribute information and the source information; A pushing module, configured to push the breakpoint task to the user device associated with the handler, so that the handler provides online registration guidance for the user according to the breakpoint task.

9. An electronic device, characterized in that, It includes a processor, a communication interface, a memory, and a communication bus. Among them, the processor, the communication interface, and the memory complete mutual communication through the communication bus; The memory is used to store a computer program; The processor is configured to implement the method according to any one of claims 1-7 when executing the program stored on the memory.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, the method according to any one of claims 1-7 is implemented.

Images