To-be-called user management method and device, equipment and medium

By filtering and managing invalid users and generating a valid user list for calls, the waste of resources caused by user status problems in the call service system is solved, and the call success rate and resource utilization efficiency are improved.

CN118900302APending Publication Date: 2024-11-05LINGXI TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411037708.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-31
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

In the fields of finance and insurance, call service systems often fail to call due to empty mobile phone numbers, shutdown, shutdown, etc., resulting in waste of system resources and call line resources.

Method used

By filtering invalid users based on the user's historical call data, putting them into the invalid user data pool, and generating a valid user list based on the valid user data pool to make calls, avoiding the system processing resources and call line resources. Specific measures include setting permanent invalid users and short-term invalid users screening rules, regularly updating user status, and timely releasing resources.

Benefits of technology

It effectively avoids the waste of system and call line resources, improves call success rate, optimizes resource utilization, and adapts to business needs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118900302A_ABST
    Figure CN118900302A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a to-be-called user management method and device, equipment and a medium, and relates to the technical field of data processing. The to-be-called user management method comprises the following steps: screening invalid users from all users according to historical call data of all users, and putting target call data of the invalid users into an invalid user data pool; and screening valid users from all the users according to the invalid user data pool, generating a valid user list, and calling according to the valid user list. According to the embodiment of the invention, the technical effects of calling effective users and avoiding occupying system processing resources and calling line resources can be realized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a method, device, equipment and medium for managing users on call. Background Art

[0002] At present, call service systems often make full calls based on a list of selected users. However, in actual scenarios, call operations in the fields of finance and insurance will almost always encounter situations where the user's mobile number is invalid, suspended, or turned off, and the user's call is transferred to voicemail, muted throughout, or immediately hung up. Calling these invalid users not only has no business value, but also occupies system processing resources and call line resources. Summary of the invention

[0003] The purpose of the embodiments of the present invention is to provide a method, device, equipment and medium for managing users waiting to be called, so as to achieve the technical effect of calling valid users and avoiding occupying system processing resources and call line resources.

[0004] In a first aspect, an embodiment of the present invention provides a method for managing a user waiting to be called, comprising:

[0005] According to the historical call data of all users, invalid users are screened from all the users, and the target call data of the invalid users are put into the invalid user data pool;

[0006] According to the invalid user data pool, valid users are screened from all the users to generate a valid user list, so as to make calls according to the valid user list.

[0007] In the above implementation process, invalid users are screened out from all users based on their historical call data, the target call data of invalid users are put into an invalid user data pool, valid users are reversely selected from all users based on the invalid user data pool, and a list of valid users is generated for calling. In this way, calls can be made to valid users to avoid occupying system processing resources and call line resources.

[0008] Furthermore, the method of screening invalid users from all the users according to the historical call data of all the users and placing the target call data of the invalid users into an invalid user data pool specifically includes:

[0009] Based on the preset permanently invalid user screening rules, permanently invalid users are screened from all the users according to the historical call data of all the users, and the target call data of the permanently invalid users are put into the permanently invalid user data pool;

[0010] Based on the preset short-term invalid user screening rules, short-term invalid users are screened from all the users according to the historical call data of all the users, and the target call data of the short-term invalid users are put into the short-term invalid user data pool.

[0011] In the above implementation process, by refining the setting of permanent invalid user screening rules and short-term invalid user screening rules, permanent invalid users are screened from all users, and the target call data of permanent invalid users are placed in the permanent invalid user data pool. In addition, short-term invalid users are screened from all users, and the target call data of short-term invalid users are placed in the short-term invalid user data pool. This enables fine-grained screening of invalid users and facilitates subsequent fine-grained management of the invalid user data pool.

[0012] Furthermore, the method for managing users waiting to be called further includes:

[0013] According to a first preset period, regularly checking whether the joining time of each short-term invalid user in the short-term invalid user data pool reaches the corresponding freezing time;

[0014] If the joining time of any of the short-term invalid users reaches the corresponding freezing time, the target call data of the short-term invalid user is moved out of the short-term invalid user data pool, so that the short-term invalid user becomes a valid user.

[0015] In the above implementation process, by regularly checking whether the joining time of each short-term invalid user in the short-term invalid user data pool has reached the corresponding freezing time, and when the joining time of any short-term invalid user has reached the corresponding freezing time, the target call data of the short-term invalid user is moved out of the short-term invalid user data pool, so that the short-term invalid user becomes a valid user, and the data in the short-term invalid user data pool can be regularly updated to ensure that all valid users are obtained in a timely and comprehensive manner in the subsequent period.

[0016] Furthermore, the method for managing users waiting to be called further includes:

[0017] According to a second preset period, regularly checking whether the historical call data of each valid user in the valid user list meets the permanent invalid user screening rule, and checking whether the historical call data of each valid user meets the short-term invalid user screening rule;

[0018] If the historical call data of any valid user meets the permanently invalid user screening rule, the target call data of the valid user is put into the permanently invalid user data pool, so that the valid user becomes a permanently invalid user;

[0019] If the historical call data of any valid user meets the short-term invalid user screening rule, the target call data of the valid user is put into the short-term invalid user data pool, so that the valid user becomes a short-term invalid user.

[0020] In the above implementation process, by regularly checking whether the historical call data of each valid user in the valid user list meets any of the permanent invalid user screening rules and the short-term invalid user screening rules, and when the historical call data of any valid user meets the permanent / short-term invalid user screening rules, the target call data of the valid user is put into the permanent / short-term invalid user data pool, so that the valid user becomes a permanent / short-term invalid user, and the data in the permanent invalid user data pool and the short-term invalid user data pool can be regularly updated to ensure that all valid users are obtained in a timely and accurate manner in the subsequent period.

[0021] Furthermore, the step of placing the target call data of the short-term invalid user into a short-term invalid user data pool specifically includes:

[0022] Counting the cumulative number of times the short-term invalid user joins the short-term invalid user data pool;

[0023] If the accumulated number of times does not reach the preset number threshold, the target call data of the short-term invalid user is put into the short-term invalid user data pool.

[0024] In the above implementation process, by placing the target call data of short-term invalid users into the short-term invalid user data pool only when the cumulative number of short-term invalid users joining the short-term invalid user data pool does not reach the preset threshold, the invalid user data pool can be managed in a fine-grained manner, further ensuring that calls are made to valid users and avoiding occupying system processing resources and call line resources.

[0025] Furthermore, the step of placing the target call data of the short-term invalid user into a short-term invalid user data pool specifically includes:

[0026] If the accumulated number reaches the preset number threshold, the target call data of the short-term invalid user is put into the permanent invalid user data pool, so that the short-term invalid user becomes a permanent invalid user.

[0027] In the above implementation process, when the cumulative number of short-term invalid users joining the short-term invalid user data pool reaches the preset threshold, the target call data of the short-term invalid users is directly placed into the permanent invalid user data pool, which enables fine-grained management of the invalid user data pool and further ensures that calls are made to valid users to avoid occupying system processing resources and call line resources.

[0028] Further, the calling according to the valid user list specifically includes:

[0029] Based on a predefined calling strategy, calls are made according to the valid user list.

[0030] In the above implementation process, by making calls based on a predefined calling strategy and a valid user list, it is possible to adapt to business needs and flexibly call valid users.

[0031] In a second aspect, an embodiment of the present invention provides a device for managing users waiting to be called, including:

[0032] An invalid user data pool management module, used to screen invalid users from all users according to historical call data of all users, and put target call data of the invalid users into an invalid user data pool;

[0033] The valid user list generation module is used to screen valid users from all the users according to the invalid user data pool, generate a valid user list, and make calls according to the valid user list.

[0034] In a third aspect, an embodiment of the present invention provides an electronic device, comprising a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor; the memory is coupled to the processor, and the processor implements the method for managing users on call as described above when executing the computer program.

[0035] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium includes a stored computer program; wherein, when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute the method for managing users on call as described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments of the present invention are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0037] Figure 1 A flowchart of a method for managing a user waiting to be called provided by the first embodiment of the present invention;

[0038] Figure 2 A schematic diagram of the structure of a waiting user management device provided by the second embodiment of the present invention;

[0039] Figure 3 A schematic structural diagram of an electronic device provided in the third embodiment of the present invention. DETAILED DESCRIPTION

[0040] The technical solutions in the embodiments of the present invention will be described below in conjunction with the accompanying drawings in the embodiments of the present invention.

[0041] It should be noted that in the description of the present invention, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance. At the same time, the step numbers in the text are only for the convenience of explaining the embodiments of the present invention and do not serve to limit the order of execution of the steps. The method provided in the embodiments of the present invention can be executed by relevant terminal devices, and the following description will be given by taking the call service terminal as the execution subject as an example. Among them, the call service terminal refers to a terminal device installed with a call service system.

[0042] Please see Figure 1 , Figure 1 The first embodiment of the present invention provides a method for managing a user on call, comprising steps S101 to S102:

[0043] S101, based on the historical call data of all users, screen invalid users from all users, and put the target call data of invalid users into an invalid user data pool;

[0044] S102: Screen valid users from all users according to the invalid user data pool, generate a valid user list, and make calls according to the valid user list.

[0045] As an example, before making a call operation, actual business needs may be considered, invalid users may be predefined, an invalid user data pool may be configured, and invalid user screening rules may be set. Invalid users are users that are prohibited from making calls.

[0046] Get the historical call data of all users, which includes multiple data items such as the user's identity, personal information (mobile phone number, age, gender, etc.), and call records. The call records are used to record the call results, call lines, and other information generated by each call to the user.

[0047] Based on the pre-set invalid user screening rules, invalid users are screened from all users according to the historical call data of all users, and the target call data of invalid users are placed in an invalid user data pool. Specifically, for each user, it is determined whether the historical call data of the user meets the invalid user screening rules. If the historical call data of the user meets the invalid user screening rules, the user is regarded as an invalid user, and the target call data of the invalid user, such as a mobile phone number, is obtained, and the target call data of the invalid user is placed in an invalid user data pool; if the historical call data of the user does not meet the invalid user screening rules, no processing is performed.

[0048] When performing a call operation, obtain the current invalid user data pool, which stores the target call data of all invalid users. According to the invalid user data pool, determine all invalid users, select valid users from all users, sort out all valid users, generate a valid user list, and call all valid users in the valid user list.

[0049] The embodiment of the present invention screens out invalid users from all users according to the historical call data of all users, puts the target call data of the invalid users into an invalid user data pool, reversely selects valid users from all users according to the invalid user data pool, generates a list of valid users for calling, and can call valid users to avoid occupying system processing resources and call line resources.

[0050] In an optional embodiment, the method of screening invalid users from all users according to the historical call data of all users, and placing the target call data of invalid users into an invalid user data pool specifically includes: based on a preset permanent invalid user screening rule, screening permanently invalid users from all users according to the historical call data of all users, and placing the target call data of permanently invalid users into a permanent invalid user data pool; based on a preset short-term invalid user screening rule, screening short-term invalid users from all users according to the historical call data of all users, and placing the target call data of short-term invalid users into a short-term invalid user data pool.

[0051] As an example, before making a call operation, the actual business needs can be considered, and invalid users can be subdivided into permanent invalid users and short-term invalid users in advance, and the invalid user data pool can be subdivided into permanent invalid user data pool and short-term invalid user data pool, and the permanent invalid user screening rules and short-term invalid user screening rules can be set with reference to the invalid user screening rules. Among them, permanent invalid users refer to users who are permanently prohibited from calling, and short-term invalid users refer to users who are short-term prohibited from calling.

[0052] In actual scenarios, for the user's call records, the call results generated by any historical call to the user may be that the user's mobile number is invalid, the user's mobile number is out of service, the user's mobile number is turned off, the user's mobile number is busy, the call line used is blocked or other disconnection results; the user may be transferred to the voicemail after the call is connected, the user may be silent throughout the call, the user may be hung up immediately after the call is connected or other connection failure results; it may also be the connection result of the user answering the call normally; any historical call to the user may use only one call line or more than two call lines.

[0053] In actual applications, the permanently invalid user screening rules can be pre-set, including: if the call results generated by the most recent a1 consecutive (a1 is a positive integer greater than or equal to 1, such as a1=4) calls to the user are all unconnected results because the user's mobile phone number is invalid, and the number of call lines used is greater than b1 (b1 is a positive integer greater than or equal to 2, such as b1=2), then the user is regarded as a permanently invalid user; if the call results generated by the most recent a2 consecutive (a2 is a positive integer greater than or equal to 1, such as a2=5) calls to the user are all failed connection results, and the number of call lines used is greater than b2 (b2 is a positive integer greater than or equal to 2, b2≥2), then the user is regarded as a permanently invalid user.

[0054] And the short-term invalid user screening rules can be pre-set, including: if the call results of the latest a3 consecutive (a3 is a positive integer greater than or equal to 1, such as a3 = 10) calls to the user are all any of the following unconnected results, such as the user's mobile phone number is empty, the user's mobile phone number is suspended, the user's mobile phone number is turned off, the user's mobile phone number is busy, the used call line is blocked, and the number of used call lines is greater than b3 (b3 is a positive integer greater than or equal to 2, such as b3 = 2), then the user is regarded as a short-term invalid user, and the freezing period of the user is set to c1 (c1>0, such as c1=60 days); if the latest a4 consecutive (a4 is a positive integer greater than or equal to 1 and less than a2, such as a4=2 ) times of calling the user result in all connection failures, and the number of call lines used is greater than b4 (b4 is a positive integer greater than or equal to 2, b4≥2), the user is regarded as a short-term invalid user, and the freezing period of the user is set to c2 (c2>0, for example, c2=60 days); if the most recent a5 (a5 is a positive integer greater than a4 and less than a2, for example, a5=3) consecutive calls to the user result in all connection failures, and the number of call lines used is greater than b5 (b5 is a positive integer greater than or equal to 2, b5≥2), the user is regarded as a short-term invalid user, and the freezing period of the user is set to c3 (c3>c2, for example, c3=120 days).

[0055] For each user, determine whether the user's historical call data meets the preset permanent invalid user screening rules, and determine whether the user's historical call data meets the preset short-term invalid user screening rules. If the user's historical call data meets the permanent invalid user screening rules, the user is treated as a permanently invalid user, and the target call data of the permanently invalid user is obtained, and the target call data of the permanently invalid user is placed in the permanent invalid user data pool; if the user's historical call data meets the short-term invalid user screening rules, the user is treated as a short-term invalid user, and the target call data of the short-term invalid user is obtained, and the target call data of the short-term invalid user is placed in the short-term invalid user data pool; if the user's historical call data neither meets the permanent invalid user screening rules nor meets the short-term invalid user screening rules, no processing is performed.

[0056] The embodiment of the present invention refines the permanently invalid user screening rules and the short-term invalid user screening rules, screens permanently invalid users from all users, and puts the target call data of permanently invalid users into a permanently invalid user data pool, and screens short-term invalid users from all users, and puts the target call data of short-term invalid users into a short-term invalid user data pool, thereby refining the screening of invalid users and facilitating subsequent fine-grained management of the invalid user data pool.

[0057] In an optional embodiment, the method for managing users waiting for calls further includes steps S103 to S104:

[0058] S103, according to the first preset period, regularly checking whether the joining time of each short-term invalid user in the short-term invalid user data pool reaches the corresponding freezing time;

[0059] S104. If the joining time of any short-term invalid user reaches the corresponding freezing time, the target call data of the short-term invalid user is removed from the short-term invalid user data pool, so that the short-term invalid user becomes a valid user.

[0060] As an example, considering the actual business needs, the first preset period is predetermined. According to the first preset period, the joining time of each short-term invalid user in the short-term invalid user data pool is regularly counted, and for each short-term invalid user, it is determined whether the joining time of the short-term invalid user reaches the freezing time corresponding to the short-term invalid user. If the joining time of the short-term invalid user reaches the freezing time corresponding to the short-term invalid user, the target call data of the short-term invalid user is removed from the short-term invalid user data pool, so that the short-term invalid user becomes a valid user; if the joining time of the short-term invalid user does not reach the freezing time corresponding to the short-term invalid user, no processing is performed.

[0061] In actual applications, an additional thawed user data pool may be configured. When the joining time of any short-term invalid user reaches the corresponding freezing time, the target call data of the short-term invalid user is moved out of the short-term invalid user data pool, making the short-term invalid user a valid user. At the same time, the target call data of the short-term invalid user is placed in the thawed user data pool, so that these previously frozen valid users can be directly obtained from the thawed user data pool later.

[0062] The embodiment of the present invention periodically checks whether the joining time of each short-term invalid user in the short-term invalid user data pool has reached the corresponding freezing time, and when the joining time of any short-term invalid user reaches the corresponding freezing time, the target call data of the short-term invalid user is moved out of the short-term invalid user data pool, so that the short-term invalid user becomes a valid user. The data in the short-term invalid user data pool can be regularly updated to ensure that all valid users are subsequently obtained in a timely and comprehensive manner.

[0063] In an optional embodiment, the method for managing users waiting for calls further includes steps S105 to S107:

[0064] S105, according to the second preset period, regularly checking whether the historical call data of each valid user in the valid user list meets the permanent invalid user screening rule, and checking whether the historical call data of each valid user meets the short-term invalid user screening rule;

[0065] S106, if the historical call data of any valid user meets the permanent invalid user screening rule, the target call data of the valid user is put into the permanent invalid user data pool, so that the valid user becomes a permanent invalid user;

[0066] S107. If the historical call data of any valid user meets the short-term invalid user screening rule, the target call data of the valid user is put into the short-term invalid user data pool, so that the valid user becomes a short-term invalid user.

[0067] As an example, the second preset period is determined according to actual business needs. According to the second preset period, the historical call data of each valid user in the valid user list is retrieved regularly. For each valid user, it is determined whether the historical call data of the valid user meets the permanent invalid user screening rule, and whether the historical call data of the valid user meets the short-term invalid user screening rule. If the historical call data of the valid user meets the permanent invalid user screening rule, the target call data of the valid user is placed in the permanent invalid user data pool, so that the valid user becomes a permanent invalid user; if the historical call data of the valid user meets the short-term invalid user screening rule, the target call data of the valid user is placed in the short-term invalid user data pool, so that the valid user becomes a short-term invalid user; if the historical call data of the valid user does not meet the permanent invalid user screening rule or the short-term invalid user screening rule, no processing is performed.

[0068] The embodiment of the present invention periodically checks whether the historical call data of each valid user in the valid user list meets any one of the permanent invalid user screening rules and the short-term invalid user screening rules, and when the historical call data of any valid user meets the permanent / short-term invalid user screening rule, the target call data of the valid user is placed in the permanent / short-term invalid user data pool, so that the valid user is changed into a permanent / short-term invalid user, and the data in the permanent invalid user data pool and the short-term invalid user data pool can be regularly updated to ensure that all valid users are subsequently obtained in a timely and accurate manner.

[0069] In an optional embodiment, the target call data of short-term invalid users is placed into a short-term invalid user data pool, specifically including: counting the cumulative number of times that short-term invalid users join the short-term invalid user data pool; if the cumulative number does not reach a preset number threshold, the target call data of the short-term invalid user is placed into the short-term invalid user data pool.

[0070] As an example, considering the actual business needs, the preset number threshold is determined in advance. When the historical call data of any user meets the short-term invalid user screening rules, the user is regarded as a short-term invalid user. At this time, the cumulative number of times the short-term invalid user joins the short-term invalid user data pool is first counted, and it is determined whether the cumulative number of times the short-term invalid user joins the short-term invalid user data pool reaches the preset number threshold. If the cumulative number of times the short-term invalid user joins the short-term invalid user data pool does not reach the preset number threshold, it is considered that the short-term invalid user can still be allowed to prohibit calls in the short term, and then the target call data of the short-term invalid user is obtained, and the target call data of the short-term invalid user is put into the short-term invalid user data pool.

[0071] The embodiment of the present invention can manage the invalid user data pool in a fine-grained manner by placing the target call data of a short-term invalid user into the short-term invalid user data pool only when the cumulative number of times the short-term invalid user joins the short-term invalid user data pool does not reach a preset number threshold, thereby further ensuring that calls are made to valid users and avoiding occupying system processing resources and call line resources.

[0072] In an optional embodiment, the target call data of short-term invalid users is placed into a short-term invalid user data pool, which specifically includes: if the cumulative number of times reaches a preset threshold, the target call data of the short-term invalid user is placed into a permanent invalid user data pool, so that the short-term invalid user becomes a permanent invalid user.

[0073] As an example, when the historical call data of any user meets the short-term invalid user screening rules, the user is treated as a short-term invalid user. At this time, the cumulative number of times the short-term invalid user joins the short-term invalid user data pool is counted, and it is determined whether the cumulative number of times the short-term invalid user joins the short-term invalid user data pool reaches the preset number threshold. If the cumulative number of times the short-term invalid user joins the short-term invalid user data pool reaches the preset number threshold, it is considered that the short-term invalid user is no longer allowed to ban calls in the short term, and then the target call data of the short-term invalid user is obtained, and the target call data of the short-term invalid user is directly put into the permanent invalid user data pool, so that the short-term invalid user becomes a permanent invalid user.

[0074] The embodiment of the present invention can manage the invalid user data pool in a fine-grained manner by directly placing the target call data of the short-term invalid user into the permanent invalid user data pool when the cumulative number of times the short-term invalid user joins the short-term invalid user data pool reaches a preset threshold number of times, thereby further ensuring that calls are made to valid users and avoiding occupying system processing resources and call line resources.

[0075] In an optional embodiment, making a call according to a valid user list specifically includes: making a call according to a valid user list based on a predefined calling strategy.

[0076] As an example, considering actual business needs, call strategies are predefined, such as scheduling 1 / 2 of the valid users to idle seats for calling, and scheduling 1 / 2 of the valid users to call robots for calling, etc. Based on the predefined call strategy, calls are made to valid users in the valid user list to complete the call job.

[0077] The embodiment of the present invention makes calls based on a predefined calling strategy and a valid user list, thereby being able to adapt to business requirements and flexibly make calls to valid users.

[0078] Please see Figure 2 , Figure 2A schematic diagram of the structure of a waiting-to-be-called user management device provided by the second embodiment of the present invention. The second embodiment of the present invention provides a waiting-to-be-called user management device, comprising: an invalid user data pool management module 201, used to screen invalid users from all users according to the historical call data of all users, and put the target call data of the invalid users into the invalid user data pool; a valid user list generation module 202, used to screen valid users from all users according to the invalid user data pool, and generate a valid user list, so as to make calls according to the valid user list.

[0079] In an optional embodiment, the method of screening invalid users from all users according to the historical call data of all users, and placing the target call data of invalid users into an invalid user data pool specifically includes: based on a preset permanent invalid user screening rule, screening permanently invalid users from all users according to the historical call data of all users, and placing the target call data of permanently invalid users into a permanent invalid user data pool; based on a preset short-term invalid user screening rule, screening short-term invalid users from all users according to the historical call data of all users, and placing the target call data of short-term invalid users into a short-term invalid user data pool.

[0080] In an optional embodiment, the invalid user data pool management module 201 is also used to: regularly check whether the joining time of each short-term invalid user in the short-term invalid user data pool has reached the corresponding freezing time according to the first preset period; if the joining time of any short-term invalid user has reached the corresponding freezing time, the target call data of the short-term invalid user will be moved out of the short-term invalid user data pool, so that the short-term invalid user becomes a valid user.

[0081] In an optional embodiment, the invalid user data pool management module 201 is also used to: regularly check whether the historical call data of each valid user in the valid user list meets the permanent invalid user screening rules according to the second preset period, and check whether the historical call data of each valid user meets the short-term invalid user screening rules; if the historical call data of any valid user meets the permanent invalid user screening rules, the target call data of the valid user is placed in the permanent invalid user data pool, so that the valid user becomes a permanent invalid user; if the historical call data of any valid user meets the short-term invalid user screening rules, the target call data of the valid user is placed in the short-term invalid user data pool, so that the valid user becomes a short-term invalid user.

[0082] In an optional embodiment, the target call data of short-term invalid users is placed into a short-term invalid user data pool, specifically including: counting the cumulative number of times that short-term invalid users join the short-term invalid user data pool; if the cumulative number does not reach a preset number threshold, the target call data of the short-term invalid user is placed into the short-term invalid user data pool.

[0083] In an optional embodiment, the target call data of short-term invalid users is placed into a short-term invalid user data pool, which specifically includes: if the cumulative number of times reaches a preset threshold, the target call data of the short-term invalid user is placed into a permanent invalid user data pool, so that the short-term invalid user becomes a permanent invalid user.

[0084] In an optional embodiment, making a call according to a valid user list specifically includes: making a call according to a valid user list based on a predefined calling strategy.

[0085] The implementation process of the functions and effects of each module in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, which will not be repeated here.

[0086] Please see Figure 3 , Figure 3 The third embodiment of the present invention provides an electronic device 30, comprising a processor 301, a memory 302, and a computer program stored in the memory 302 and configured to be executed by the processor 301; the memory 302 is coupled to the processor 301, and when the processor 301 executes the computer program, the method for managing users on call as described in the first embodiment of the present invention is implemented, and the same beneficial effects can be achieved.

[0087] The processor 301 reads the computer program from the memory 302 through the bus 303 and executes the computer program to implement any method of the method for managing users on call as described in the first embodiment of the present invention.

[0088] Processor 301 can process digital signals and can include various computing structures, such as complex instruction set computer structure, reduced instruction set computer structure, or a structure that implements a combination of multiple instruction sets. In some examples, processor 301 can be a microprocessor.

[0089] The memory 302 may be used to store instructions executed by the processor 301 or data related to the execution of instructions. These instructions and / or data may include codes for implementing some functions or all functions of one or more modules described in the embodiments of the present invention. The processor 301 of the embodiment of the present disclosure may be used to execute instructions in the memory 302 to implement the method for managing waiting users as described in the first embodiment of the present invention. The memory 302 includes a dynamic random access memory, a static random access memory, a flash memory, an optical memory, or other memory well known to those skilled in the art.

[0090] The fourth embodiment of the present invention provides a computer-readable storage medium, which includes a stored computer program; wherein, when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute the method for managing users on call as described in the first embodiment of the present invention, and can achieve the same beneficial effects.

[0091] In summary, the embodiments of the present invention provide a method, device, equipment and medium for managing users to be called, and the method for managing users to be called includes: filtering invalid users from all users according to the historical call data of all users, and putting the target call data of invalid users into an invalid user data pool; filtering valid users from all users according to the invalid user data pool, generating a valid user list, and making calls according to the valid user list. The embodiments of the present invention can make calls to valid users and avoid occupying system processing resources and call line resources by filtering invalid users from all users according to the historical call data of all users, putting the target call data of invalid users into an invalid user data pool, and deselecting valid users from all users according to the invalid user data pool to generate a valid user list for calling.

[0092] In several embodiments provided by the present invention, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present invention. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, program segment or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0093] In addition, the functional modules in the various embodiments of the present invention may be integrated together to form an independent part, or each module may exist independently, or two or more modules may be integrated to form an independent part.

[0094] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0095] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A method for managing users waiting to be called, characterized in that: include: According to the historical call data of all users, invalid users are screened from all the users, and the target call data of the invalid users are put into the invalid user data pool; According to the invalid user data pool, valid users are screened from all the users to generate a valid user list, so as to make calls according to the valid user list.

2. The method for managing users waiting to be called according to claim 1, characterized in that: The step of screening invalid users from all the users according to the historical call data of all the users and placing the target call data of the invalid users into an invalid user data pool specifically includes: Based on the preset permanently invalid user screening rules, permanently invalid users are screened from all the users according to the historical call data of all the users, and the target call data of the permanently invalid users are put into the permanently invalid user data pool; Based on the preset short-term invalid user screening rules, short-term invalid users are screened from all the users according to the historical call data of all the users, and the target call data of the short-term invalid users are put into the short-term invalid user data pool.

3. The method for managing users waiting to be called according to claim 2, characterized in that: Also includes: According to the first preset period, regularly checking whether the joining time of each short-term invalid user in the short-term invalid user data pool reaches the corresponding freezing time; If the joining time of any of the short-term invalid users reaches the corresponding freezing time, the target call data of the short-term invalid user is moved out of the short-term invalid user data pool, so that the short-term invalid user becomes a valid user.

4. The method for managing users waiting to be called according to claim 2, characterized in that: Also includes: According to a second preset period, regularly checking whether the historical call data of each valid user in the valid user list meets the permanent invalid user screening rule, and checking whether the historical call data of each valid user meets the short-term invalid user screening rule; If the historical call data of any valid user meets the permanently invalid user screening rule, the target call data of the valid user is put into the permanently invalid user data pool, so that the valid user becomes a permanently invalid user; If the historical call data of any valid user meets the short-term invalid user screening rule, the target call data of the valid user is put into the short-term invalid user data pool, so that the valid user becomes a short-term invalid user.

5. The method for managing users waiting to be called according to any one of claims 2 to 4, characterized in that: The step of placing the target call data of the short-term invalid user into a short-term invalid user data pool specifically includes: Counting the cumulative number of times the short-term invalid user joins the short-term invalid user data pool; If the accumulated number of times does not reach the preset number threshold, the target call data of the short-term invalid user is put into the short-term invalid user data pool.

6. The method for managing users waiting to be called according to claim 5, characterized in that: The step of placing the target call data of the short-term invalid user into a short-term invalid user data pool specifically includes: If the accumulated number reaches the preset number threshold, the target call data of the short-term invalid user is put into the permanent invalid user data pool, so that the short-term invalid user becomes a permanent invalid user.

7. The method for managing users waiting to be called according to claim 1, characterized in that: The calling according to the valid user list specifically includes: Based on a predefined calling strategy, calls are made according to the valid user list.

8. A device for managing users waiting to be called, characterized in that: include: An invalid user data pool management module, used to screen invalid users from all users according to historical call data of all users, and put target call data of the invalid users into an invalid user data pool; The valid user list generation module is used to screen valid users from all the users according to the invalid user data pool, generate a valid user list, and make calls according to the valid user list.

9. An electronic device, characterized in that: It comprises a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor; the memory is coupled to the processor, and when the processor executes the computer program, it implements the method for managing users on call according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored computer program; wherein, when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute the method for managing users on call according to any one of claims 1 to 7.