User information management system, user information management method and storage medium

Abstract

The embodiment of the present invention discloses a user information management system, a user information management method and a storage medium. When the supply end allocates a call task to the call end, the supply end does not interact with the server, and thus does not involve the acquisition of user information, which effectively avoids the leakage of user information by the supply end, thereby improving the security of user information. The embodiment of the present invention includes: a demand end, a supply end, a call end and a server; the demand end is used to send a task list to the call end through the supply end, and the task list includes a task identity ID corresponding to the call task; send user information and a task ID corresponding to the user information to the server, and the user information includes a user name and contact information; the server is used to receive the user information sent by the demand end and the task ID corresponding to the user information; the call end is used to receive the task list sent by the demand end; according to the task list, obtain the user information corresponding to the task ID from the server.

Description

Technical Field

[0001] The present invention relates to the technical field of user information management, and in particular to a user information management system, a user information management method and a storage medium. Background Art

[0002] In marketing activities, if the demand side wants to sell products to potential customers, they often reach potential users by purchasing suppliers through telephone sales.

[0003] However, even though the country's control over personal information is becoming increasingly strict, there will still be bad suppliers who maliciously obtain user information, resulting in a higher risk of user information leakage. Summary of the invention

[0004] The embodiments of the present invention provide a user information management system, a user information management method and a storage medium. Since the task list only includes the task ID corresponding to the call task and does not involve the user information corresponding to the task ID, and the user information corresponding to the task ID is stored in the server, the supply side does not interact with the server during the process of allocating call tasks to the call side, and thus does not involve the acquisition of user information, which effectively avoids the leakage of user information by the supply side, thereby improving the security of user information.

[0005] A first aspect of an embodiment of the present invention provides a user information management system, which may include: a demand side, a supply side, a call side and a server;

[0006] The demand side is used to send a task list to the call side through the supply side, the task list includes a task identity ID corresponding to the call task; send user information and the task ID corresponding to the user information to the server, the user information includes the user name and contact information;

[0007] The server is used to receive the user information sent by the demand end and the task ID corresponding to the user information;

[0008] The calling end is used to receive the task list sent by the demanding end; and obtain the user information corresponding to the task ID from the server according to the task list.

[0009] Optionally, the server is also used to record interaction information with the calling end; and determine whether the call task performed by the calling end is normal based on the interaction information; wherein the interaction information includes first relevant information corresponding to when the calling end obtains user information from the server, and / or second relevant information corresponding to when the calling end sends feedback information to the server.

[0010] Optionally, the server is specifically used to obtain characteristic data of the calling end based on the interactive information; input the characteristic data into a preset detection model and output a floating-point value; and determine whether the call task performed by the calling end is normal based on the floating-point value.

[0011] Optionally, the server is specifically used to determine that the call task executed by the calling end is normal if the floating point value is greater than a first preset threshold and less than or equal to a second preset threshold; if the floating point value is greater than the second preset threshold and less than or equal to a third preset threshold, determine that the call task executed by the calling end is abnormal.

[0012] Optionally, the server is also used to send a first prompt message to the management terminal if the floating point value is greater than the second preset threshold and less than or equal to a fourth preset threshold, and the first prompt message is used to prompt that the call task executed by the calling end is abnormal; if the floating point value is greater than the fourth preset threshold and less than or equal to the third preset threshold, the first prompt message is sent to the management terminal and the user access rights of the calling end to the server are disconnected.

[0013] Optionally, the server is also used to obtain the number of target call ends within a preset time period, and the target call end is the call end corresponding to the call task being executed abnormally; when the number is greater than a preset number threshold, the second prompt message is sent to the management terminal, and the user access rights of the target call end to the server are disconnected, and the second prompt message is used to prompt the target call end that the call task being executed is abnormal.

[0014] Optionally, the first relevant information includes at least one of the task ID, time, account, Internet Protocol IP address, browser type and session ID corresponding to when the calling end obtains user information from the server; the second relevant information includes at least one of the task ID, time, account, IP address, browser type and session ID corresponding to when the calling end sends feedback information to the server.

[0015] Optionally, the preset detection model includes one of a gradient descent decision tree GBDT, a random forest algorithm, a gradient boosting decision tree model XGBoosT, a light gradient enhancement machine LightGBM, a support vector machine, a logistic regression, and a neural network model.

[0016] Optionally, the demand end is specifically used to send the task list to the call end through the supply end in a first manner; and send the user information and the task ID corresponding to the user information to the server in a second manner;

[0017] The calling end is specifically used to obtain user information corresponding to the task ID from the server by using a third method according to the task list;

[0018] The first method, the second method and the third method include: a global wide area network WEB page method or a QR code method.

[0019] A second aspect of an embodiment of the present invention provides a user information management method, which is applied to a user information management system, the user information management system includes a server, a demand end and a call end, and the method may include:

[0020] The server receives the user information sent by the demand end and the task identity ID corresponding to the user information. The task ID is used by the call end to obtain the user information corresponding to the task ID from the server. The user information includes the user name and contact information.

[0021] Optionally, the method also includes: recording, by the server, interaction information between the calling end and the calling end; determining, by the server, whether the call task performed by the calling end is normal based on the interaction information; wherein the interaction information includes first relevant information corresponding to when the calling end obtains user information from the server, and / or second relevant information corresponding to when the calling end sends feedback information to the server.

[0022] Optionally, the server determines whether the call task performed by the call end is normal based on the interaction information, including: obtaining feature data of the call end through the server based on the interaction information; inputting the feature data into a preset detection model through the server and outputting a floating-point value; and determining whether the call task performed by the call end is normal based on the floating-point value through the server.

[0023] Optionally, the server determines whether the call task executed by the calling end is normal based on the floating-point value, including: if the floating-point value is greater than a first preset threshold and less than or equal to a second preset threshold, the server determines that the call task executed by the calling end is normal; if the floating-point value is greater than the second preset threshold and less than or equal to a third preset threshold, the server determines that the call task executed by the calling end is abnormal.

[0024] Optionally, after determining that the call task executed by the calling end is abnormal if the floating-point value is greater than the second preset threshold and less than or equal to the third preset threshold, the method further includes: sending a first prompt message to the management terminal through the server if the floating-point value is greater than the second preset threshold and less than or equal to the fourth preset threshold, and the first prompt message is used to prompt that the call task executed by the calling end is abnormal; if the floating-point value is greater than the fourth preset threshold and less than or equal to the third preset threshold, sending the first prompt message to the management terminal and disconnecting the user access right of the calling end to the server.

[0025] Optionally, the method also includes: obtaining, through the server, the number of target call ends within a preset time period, the target call end being the call end corresponding to the call task being executed abnormally; and sending, through the server, the second prompt message to the management terminal when the number is greater than a preset number threshold, and disconnecting the user access rights of the target call end to the server, the second prompt message being used to prompt the target call end that the call task being executed is abnormal.

[0026] A third aspect of an embodiment of the present invention provides a server, which may include:

[0027] The transceiver module is used to receive the user information sent by the demand end and the task identity ID corresponding to the user information. The task ID is used by the calling end to obtain the user information corresponding to the task ID from the server. The user information includes the user name and contact information.

[0028] A fourth aspect of an embodiment of the present invention provides a server, which may include:

[0029] A memory storing executable program code;

[0030] and a processor and a transceiver coupled to the memory;

[0031] The processor calls the executable program code stored in the memory, and when the executable program code is executed by the processor, the processor and the transceiver implement the method described in the second aspect of the embodiment of the present invention.

[0032] Another aspect of an embodiment of the present invention provides a computer-readable storage medium having executable program code stored thereon. When the executable program code is executed by a processor, the method described in the second aspect of the embodiment of the present invention is implemented.

[0033] Yet another aspect of an embodiment of the present invention discloses a computer program product. When the computer program product runs on a computer, the computer is enabled to execute any one of the methods disclosed in the second aspect of the embodiment of the present invention.

[0034] Another aspect of an embodiment of the present invention discloses an application publishing platform, which is used to publish a computer program product. When the computer program product runs on a computer, the computer executes any one of the methods disclosed in the second aspect of the embodiment of the present invention.

[0035] It can be seen from the above technical solutions that the embodiments of the present invention have the following advantages:

[0036] In an embodiment of the present invention, a user information management system includes: a demand side, a supply side, a call side and a server; the demand side is used to send a task list to the call side through the supply side, the task list includes a task identity ID corresponding to the call task; send user information and the task ID corresponding to the user information to the server, the user information includes a user name and contact information; the server is used to receive the user information sent by the demand side and the task ID corresponding to the user information; the call side is used to receive the task list sent by the demand side; according to the task list, obtain the user information corresponding to the task ID from the server. Since the task list only includes the task ID corresponding to the call task, and does not involve the user information corresponding to the task ID, the user information corresponding to the task ID is stored in the server, so the supply side does not interact with the server in the process of allocating call tasks to the call side, and thus does not involve the acquisition of user information, which effectively avoids the leakage of user information by the supply side, thereby improving the security of user information. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments and the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention, and other drawings can be obtained based on these drawings.

[0038] Figure 1 A schematic diagram of an embodiment of a user information management system in an embodiment of the present invention;

[0039] Figure 2 A schematic diagram of an embodiment of a user information management method in an embodiment of the present invention;

[0040] Figure 3 A schematic diagram of another embodiment of the user information management method in an embodiment of the present invention;

[0041] Figure 4 A schematic diagram of another embodiment of the user information management method in an embodiment of the present invention;

[0042] Figure 5 A schematic diagram of another embodiment of the user information management method in an embodiment of the present invention;

[0043] Figure 6 A schematic diagram of an embodiment of a server in an embodiment of the present invention;

[0044] Figure 7 FIG. 2 is a schematic diagram of another embodiment of a server in an embodiment of the present invention. DETAILED DESCRIPTION

[0045] The embodiments of the present invention provide a user information management system, a user information management method and a storage medium. Since the task list only includes the task ID corresponding to the call task and does not involve the user information corresponding to the task ID, and the user information corresponding to the task ID is stored in the server, the supply side does not interact with the server during the process of allocating call tasks to the call side, and thus does not involve the acquisition of user information, which effectively avoids the leakage of user information by the supply side, thereby improving the security of user information.

[0046] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiment of the present invention will be described below in conjunction with the drawings in the embodiment of the present invention. Obviously, the described embodiment is only a part of the embodiment of the present invention, not all of the embodiments. Based on the embodiments in the present invention, they should all fall within the scope of protection of the present invention.

[0047] In the prior art, common solutions to prevent user information leakage are as follows: Solution 1: Use contract terms to constrain suppliers; Solution 2: The demander provides a telephone call center to provide suppliers with desensitized user information. The telephone number is replaced with a telephone link that only the demander can interpret. The supplier uses the telephone link to reach the user through the telephone call center.

[0048] However, in Plan 1, if the supplier fails to fulfill the terms of the contract, user information may be leaked; in Plan 2, although the demander uses a call center, it still needs to provide customer information to the supplier to facilitate the execution of the call task, which may also lead to user information leakage.

[0049] It should be noted that the demand side, supply side and call side involved in the embodiments of the present invention are all electronic devices, which can be mobile terminal devices or wearable devices.

[0050] The technical solution of the present invention is further described below by way of embodiments. Figure 1 As shown, it is a schematic diagram of an embodiment of a user information management system in an embodiment of the present invention, which may include: a demand end 101, a supply end 102, a call end 103 and a server 104;

[0051] The demand side 101 is used to send a task list to the call side 103 through the supply side 102, and the task list may include a task identity ID corresponding to the call task; send user information and the task ID corresponding to the user information to the server 104, and the user information may include the user name and contact information;

[0052] The server 104 is used to receive the user information and the task ID corresponding to the user information sent by the demand end 101;

[0053] The calling end 103 is used to receive the task list sent by the demanding end 101 ; and obtain the user information corresponding to the task ID from the server 104 according to the task list.

[0054] It should be noted that the user using the demand side 101 can be called the demander; the user using the supply side 102 can be called the supplier; and the user using the call side 103 can be called the call specialist.

[0055] Optionally, the contact information may include but is not limited to mobile phone number, WeChat or QQ.

[0056] It should be noted that the task ID corresponding to the call task is unique, and the number of task IDs is unlimited; the number of user information is unlimited. For example, the task list may include 10 task IDs corresponding to the call task; the user information may include 10 user names and the contact information of the 10 users, wherein each user information corresponds to a task ID.

[0057] It is understandable that one supply end 102 can correspond to at least one call end 103, that is, one supply end 102 can assign a call task to at least one call end 103, and the number of call ends 103 is unlimited. Specifically, the supply end 102 can send a task list to one call end 103, that is, this call end 103 can receive all task IDs corresponding to the call tasks in the task list; the supply end 102 can also send the first number of task IDs in the task list to the first call end, so that the first call end can obtain the user information corresponding to the first number of task IDs, and send the second number of task IDs to the second call end, so that the second call end can obtain the user information corresponding to the second number of task IDs. The first number and the second number can be the same or different.

[0058] For example, it is assumed that the task list includes 10 task IDs corresponding to the call tasks, the first number is 4, and the second number is 6. The supply end 102 may send the 4 task IDs corresponding to the call tasks in the task list to the first call end, so that the first call end can obtain the user information corresponding to the 4 task IDs; and send the remaining 6 task IDs corresponding to the call tasks in the task list to the second call end, so that the second call end can obtain the user information corresponding to the 6 task IDs.

[0059] It should be noted that the demand side 101 can first send a task list to the call side 103 through the supply side 102, and then send the user information and the task ID corresponding to the user information to the server 104; it can first send the user information and the task ID corresponding to the user information to the server 104, and then send the task list to the call side 103 through the supply side 102; it can also send the user information and the task ID corresponding to the user information to the server 104 at the same time as sending the task list to the call side 103 through the supply side 102, and the timing is not specifically limited.

[0060] Optionally, the user information may also include, but is not limited to, at least one of the following: user gender, location of the user's mobile phone number, user ID number, and user address.

[0061] In the embodiment of the present invention, the role of the supply end 102 is to send and receive the task list. Specifically, the supply end 102 can receive the task list sent by the demand end 101, and send the task list to the call end 103. Since the task list only includes the task ID corresponding to the call task, and does not involve the user information corresponding to the task ID, the user information corresponding to the task ID is stored in the server 104. Therefore, in the process of allocating the call task to the call end 103, the supply end 102 does not interact with the server 104, and thus does not involve the acquisition of user information, which effectively avoids the leakage of user information by the supply end 102, thereby improving the security of user information.

[0062] Optionally, the demand side 101 is specifically configured to send the task list to the call side 103 through the supply side 102 in a first manner; and send the user information and the task ID corresponding to the user information to the server 104 in a second manner;

[0063] The calling end 103 is specifically used to obtain the user information corresponding to the task ID from the server 104 using the third method according to the task list;

[0064] The first method, the second method and the third method may include but are not limited to: a global wide area network WEB page method or a QR code method.

[0065] It should be noted that the global wide area network WEB page, also known as the World Wide Web, can provide a graphical, easy-to-access, intuitive interface for users to find and browse specific information (e.g., a task list). The WEB page can use a uniform resource locator (URL) link, which is a method for specifying location information. For example, the supply end 102 uses a URL link to send a task list to the call end 103.

[0066] A two-dimensional code, also known as a two-dimensional barcode, is a black and white graphic that records data symbol information and is distributed in a plane (two-dimensional direction) according to a certain geometric pattern. For example, the calling terminal 103 obtains the user information corresponding to the task ID from the server 104 using a two-dimensional code.

[0067] Optionally, the first method, the second method and the third method may also include, but are not limited to: a barcode method, a three-dimensional code method, or other custom code methods.

[0068] In the embodiment of the present invention, whether it is a WEB page method or a QR code method, it is a carrier for transmitting data (for example, task list, user information), so that the data has high directionality and security during the transmission process, and effectively avoids data leakage.

[0069] Optionally, the server 104 is also used to record the interaction information between the server 104 and the calling end 103; based on the interaction information, determine whether the call task performed by the calling end 103 is normal; wherein the interaction information may include the first relevant information corresponding to when the calling end 103 obtains user information from the server 104, and / or the second relevant information corresponding to when the calling end 103 sends feedback information to the server 104.

[0070] Optionally, the first relevant information may include but is not limited to at least one of the task ID, time, account, Internet Protocol (IP) address, browser type and session ID corresponding to when the calling end 103 obtains user information from the server 104; the second relevant information may include but is not limited to at least one of the task ID, time, account, IP address, browser type and session ID corresponding to when the calling end 103 sends feedback information to the server 104.

[0071] It should be noted that the unit of time can be one of day, hour (h), minute (min) and second (s), and is not specifically limited here.

[0072] The account may be a user name corresponding to the user using the calling terminal 103 .

[0073] Exemplarily, the browser type may include, but is not limited to, one of 360 Safe Browser, Firefox, and Google Chrome, and is not specifically limited here.

[0074] It is understandable that the interaction information may be stored in the server 104 in the form of a table. For example, as shown in Table 1, it is a table of interaction information in an embodiment of the present invention.

[0075]

[0076] Table 1

[0077] Optionally, the interaction information may further include third related information corresponding to when the calling end 103 logs into the server 104 , and / or fourth related information corresponding to when the calling end 103 logs out of the server 104 .

[0078] Optionally, the third relevant information may include but is not limited to at least one of the corresponding time, account, IP address, browser type and session ID when the calling end 103 logs into the server 104; the fourth relevant information may include but is not limited to at least one of the corresponding time, account, IP address, browser type and session ID when the calling end 103 logs out of the server 104.

[0079] The calling end 103 logging out of the server 104 refers to the calling end 103 exiting the server 104 .

[0080] Optionally, the server 104 is specifically configured to periodically record interaction information with the calling end 103 .

[0081] It should be noted that the recording period of the server 104 for the interaction information may be set before the server leaves the factory, or may be set by the user, which is not specifically limited here.

[0082] Exemplarily, the server 104 records the interaction information between the active call terminals 103 in the server 104 every 5 minutes.

[0083] In an embodiment of the present invention, the server 104 can determine in real time whether the call task executed by the call end 103 is normal based on the recorded interaction information between the server 104 and the call end 103, effectively improving the timeliness of the server 104's analysis and judgment on whether the call task executed by the call end 103 is normal.

[0084] Optionally, the server 104 is specifically used to obtain feature data of the calling end 103 based on the interaction information; input the feature data into a preset detection model and output a floating-point value; and determine whether the call task performed by the calling end 103 is normal based on the floating-point value.

[0085] It is understandable that the floating point value may represent the probability that the server 104 detects that the calling end 103 maliciously obtains user information from the server 104 .

[0086] Optionally, the floating point value generally ranges from (0, 1).

[0087] It should be noted that if the interactive information only includes the third relevant information and / or the fourth relevant information, but does not include the first relevant information and / or the second relevant information, then the interactive information cannot be used as input data for the preset detection model. At this time, the server 104 cannot analyze and determine whether the call task executed by the calling terminal 103 is normal.

[0088] If the interaction information only includes the first relevant information and / or the second relevant information, the server 104 will use the first relevant information of the first record as the third relevant information, and assume that the maximum session duration of the calling end 103 is the first preset duration (e.g., 8 hours). At this time, the server 104 can analyze and determine whether the call task executed by the calling end 103 is normal based on the interaction information.

[0089] In summary, the interaction data must include the first relevant information and / or the second relevant information, and may but need not include the third relevant information and / or the fourth relevant information. That is, the presence or absence of the third relevant information and / or the fourth relevant information does not affect the subsequent analysis and judgment by the server 104 on whether the call task executed by the calling end 103 is normal.

[0090] It is understandable that the characteristic data may be stored in the server 104 in the form of a table. For example, as shown in Table 2, it is a table of characteristic data in an embodiment of the present invention.

[0091]

[0092]

[0093] Table 2

[0094] It should be noted that the users in Table 2 refer to users who are actively using the calling terminal 103 in the server 104 , and the users may be called calling specialists.

[0095] uid refers to the ID set for user information by the application software (Application, APP) in the demand side 101; vin refers to the identifier set on the vehicle by the demand side 101, which is unique.

[0096] In an embodiment of the present invention, the server 104 obtains characteristic data of the calling end 103 based on the recorded interaction information with the calling end 103; then, based on the characteristic data and the preset detection model, it can determine in real time whether the call task executed by the calling end 103 is normal, thereby effectively improving the timeliness of the server 104's analysis and judgment on whether the call task executed by the calling end 103 is normal.

[0097] Optionally, the preset detection model includes one of a gradient descent decision tree GBDT, a random forest algorithm, a gradient boosting decision tree model XGBoosT, a light gradient enhancement machine LightGBM, a support vector machine, a logistic regression, and a neural network model.

[0098] It should be noted that the preset detection model can construct a binary classifier to determine a floating-point value with higher accuracy.

[0099] Exemplarily, as shown in Table 3, it is a table of model parameters of the gradient descent decision tree GBDT in an embodiment of the present invention.

[0100] parameter Value illustrate max_depth 6 Maximum depth of the tree eta 0.1 Learning Rate objective binary:logistic Loss Function

[0101] Table 3

[0102] In an embodiment of the present invention, feature data as input data of GBDT is diverse. When determining feature data, server 104 plans according to three feature domains: user attributes, task attributes, and interaction between users and tasks. Among them, some feature data, such as "the number of task IDs viewed by users in the past 5 minutes", are obtained by server 104 after trying different time windows (1m, 10m, 30m), and filtering out empirical parameters that can make the preset detection model predict with higher accuracy, so that server 104 can more accurately determine whether the call task executed by the call end 103 is normal according to the preset detection model.

[0103] Optionally, the server 104 is specifically used to determine that the call task executed by the call end 103 is normal if the floating point value is greater than a first preset threshold and less than or equal to a second preset threshold; if the floating point value is greater than the second preset threshold and less than or equal to a third preset threshold, determine that the call task executed by the call end 103 is abnormal.

[0104] It should be noted that, since the selection of the preset threshold is related to the model parameters and feature data of the preset detection model, the preset threshold can be selected by the server 104 according to actual conditions.

[0105] It is understandable that if the server 104 selects a third preset threshold that is too large, the call end 103 may be missed, and it is impossible to determine whether the call task executed by the missed call end 103 is normal; if the server 104 selects a first preset threshold that is too small, the call end 103 corresponding to the call task executed normally will be determined as an abnormal call task executed by the call end 103, which will cause the server 104 to have a deviation in the result of judging the call end 103.

[0106] Exemplarily, assuming that the value of the first preset threshold is 0, the value of the second preset threshold is 0.9, and the value of the third preset threshold is 1.0. When the server 104 obtains a floating point value of 0.36 through the preset detection model, the 0.36 is within (0, 0.9). At this time, the server 104 determines that the call task performed by the call end 103 is normal; when the server 104 obtains a floating point value of 0.92 through the preset detection model, the 0.92 is within (0.9, 1.0). At this time, the server 104 determines that the call task performed by the call end 103 is abnormal.

[0107] Optionally, the server 104 is also used to send a first prompt message to the management terminal if the floating point value is greater than the second preset threshold and less than or equal to the fourth preset threshold, and the first prompt message is used to prompt that the call task executed by the calling end 103 is abnormal; if the floating point value is greater than the fourth preset threshold and less than or equal to the third preset threshold, the first prompt message is sent to the management terminal and the user access rights of the calling end 103 to the server 104 are disconnected.

[0108] Exemplarily, assuming that the value of the fourth preset threshold is 0.97, when the server 104 obtains a floating point value of 0.94 through the preset detection model, the 0.94 is within (0.9, 0.97), and at this time, the server 104 sends a first prompt message to the management terminal.

[0109] Optionally, the server 104 is specifically configured to send the first prompt information to the management terminal in a fourth manner. The fourth manner may include but is not limited to one of the following: email, text message, and APP message push.

[0110] It should be noted that when the floating point value is greater than the second preset threshold and less than or equal to the fourth preset threshold, it indicates that the degree of abnormality of the call task executed by the call end 103 is moderate. At this time, the server 104 only needs to send a first prompt message to the management terminal associated with the server 104.

[0111] When the floating point value is greater than the fourth preset threshold and less than or equal to the third preset threshold, it indicates that the abnormality of the call task executed by the calling end 103 is severe. In this case, the server 104 not only needs to send a first prompt message to the management terminal associated with the server 104, but also needs to directly prevent the calling end 103 from obtaining new user information from the server 104, so as to timely prevent the calling end 103 from maliciously obtaining user information, thereby achieving the purpose of reducing the probability of user information leakage.

[0112] Optionally, server 104 is also used to obtain the number of target call ends within a preset time period, and the target call end is the call end corresponding to the call task being executed abnormally; when the number is greater than a preset number threshold, the second prompt message is sent to the management terminal, and the user access rights of the target call end to the server 104 are disconnected, and the second prompt message is used to prompt that the call task being executed by the target call end is abnormal.

[0113] Optionally, the server 104 is further configured to send the second prompt information to the management terminal when the number is equal to the preset number threshold.

[0114] It should be noted that the preset quantity threshold may be set by the server 104 before leaving the factory, or may be user-defined, and is not specifically limited here.

[0115] If the preset number threshold is the number of all calling terminals 103 corresponding to the supply terminal 102 , the server 104 may disconnect the user access right of the supply terminal 102 to the server 104 .

[0116] Optionally, the server 104 is specifically configured to send the second prompt information to the management terminal in a fifth manner. The fifth manner may include but is not limited to one of the following: email, text message, and APP message push.

[0117] In the embodiment of the present invention, the server 104 can timely prevent the calling end 103 from maliciously obtaining user information, thereby achieving the purpose of reducing the probability of user information leakage.

[0118] Optionally, the calling end 103 is further used to execute a calling task according to the user information, obtain feedback information corresponding to the user information, and send the feedback information to the server 104 .

[0119] Exemplarily, the calling end 103 obtains user information corresponding to five task IDs from the server 104 , executes the calling task according to the user information corresponding to the five task IDs, obtains feedback information corresponding to the five user information respectively, and sends the five feedback information to the server 104 .

[0120] In the embodiment of the present invention, since the demand side 101 obtains the feedback information directly from the server 104 instead of through the supply side 102, during the transmission of the feedback information, there will be no leakage of the user information and the feedback information corresponding to the user information, thereby ensuring the security of the transmission of the user information and the feedback information corresponding to the user information.

[0121] Optionally, the demand side 101 is further used to obtain target feedback information from the server 104, and the feedback information includes the target feedback information.

[0122] In an embodiment of the present invention, the demand side 101 obtains feedback information from the server 104. It can obtain all the feedback information in the server 104, or it can obtain part of the feedback information (i.e., target feedback information) in the server 104, which reflects the flexibility of the demand side 101 in obtaining feedback information.

[0123] like Figure 2 FIG. 1 is a schematic diagram of an embodiment of a user information management method in an embodiment of the present invention, which is applied to a user information management system. The user information management system includes a server, a demand end, and a call end. The method may include:

[0124] 201. Receive, through the server, user information sent by the demand side and a task identity ID corresponding to the user information.

[0125] The task ID is used by the calling end to obtain user information corresponding to the task ID from the server, and the user information includes the user name and contact information.

[0126] For example, Figure 3 FIG. 1 is a schematic diagram of another embodiment of the user information management method in an embodiment of the present invention. Figure 3 In the process, the demand side 101 sends a task list to the supply side 102, and the task list includes a task identity ID corresponding to the call task; the demand side 101 sends user information and the task ID corresponding to the user information to the server 104; the supply side 102 receives the task list sent by the demand side 11, and sends the task list to the call side 103; the server 104 receives the user information sent by the demand side 101 and the task ID corresponding to the user information; the call side 103 receives the task list sent by the supply side 102, and obtains the user information corresponding to the task ID from the server 104 according to the task list, and then obtains the feedback information corresponding to the user information according to the user information corresponding to the task ID, and sends the feedback information to the server 104; the server 104 receives the feedback information sent by the call side 103; the demand side 101 obtains the feedback information from the server 104.

[0127] 202. Record, by the server, interaction information with the calling end.

[0128] The interaction information may include first related information corresponding to when the calling end obtains user information from the server, and / or second related information corresponding to when the calling end sends feedback information to the server.

[0129] Optionally, the first relevant information may include but is not limited to at least one of the task ID, time, account, Internet Protocol IP address, browser type and session ID corresponding to when the calling end 103 obtains user information from the server; the second relevant information may include but is not limited to at least one of the task ID, time, account, IP address, browser type and session ID corresponding to when the calling end 103 sends feedback information to the server 104.

[0130] Optionally, the interaction information may further include third related information corresponding to when the calling end 103 logs into the server 104 , and / or fourth related information corresponding to when the calling end 103 logs out of the server 104 .

[0131] Optionally, the third relevant information may include but is not limited to at least one of the corresponding time, account, IP address, browser type and session ID when the calling end 103 logs into the server 104; the fourth relevant information may include but is not limited to at least one of the corresponding time, account, IP address, browser type and session ID when the calling end 103 logs out of the server 104.

[0132] For example, Figure 4 FIG. 1 is a schematic diagram of another embodiment of the user information management method in an embodiment of the present invention. Figure 4 When the server 104 detects that the calling end 103 logs into the server 104, the server 104 records the third relevant information; when the server 104 detects that the calling end 103 obtains the user information from the server 104, the server 104 records the first relevant information; when the server 104 receives the feedback information corresponding to the user information sent by the calling end 103 to the server 104, the server 104 records the second relevant information; when the server 104 detects that the calling end 103 logs out of the server 104, the server 104 records the fourth relevant information.

[0133] Optionally, recording the interaction information between the calling end and the calling end through the server 104 may include: periodically recording the interaction information between the calling end and the calling end 103 through the server 104 .

[0134] 203. Determine whether the call task executed by the calling end is normal according to the interaction information.

[0135] Optionally, determining whether the call task performed by the calling end is normal based on the interaction information may include: obtaining characteristic data of the calling end through the server based on the interaction information; inputting the characteristic data into a preset detection model through the server and outputting a floating-point value; and determining whether the call task performed by the calling end is normal based on the floating-point value through the server.

[0136] Optionally, the preset detection model includes one of a gradient descent decision tree GBDT, a random forest algorithm, a gradient boosting decision tree model XGBoosT, a light gradient enhancement machine LightGBM, a support vector machine, a logistic regression, and a neural network model.

[0137] Optionally, the server determines whether the call task executed by the calling end is normal based on the floating-point value, including: if the floating-point value is greater than a first preset threshold and less than or equal to a second preset threshold, the server determines that the call task executed by the calling end is normal; if the floating-point value is greater than the second preset threshold and less than or equal to a third preset threshold, the server determines that the call task executed by the calling end is abnormal.

[0138] Optionally, after determining that the call task executed by the calling end is abnormal if the floating-point value is greater than the second preset threshold and less than or equal to the third preset threshold, the method further includes: sending a first prompt message to the management terminal through the server if the floating-point value is greater than the second preset threshold and less than or equal to the fourth preset threshold, and the first prompt message is used to prompt that the call task executed by the calling end is abnormal; if the floating-point value is greater than the fourth preset threshold and less than or equal to the third preset threshold, sending the first prompt message to the management terminal and disconnecting the user access right of the calling end to the server.

[0139] Optionally, sending the first prompt information to the management terminal may include: sending the first prompt information to the management terminal in a fourth manner. The fourth manner may include but is not limited to one of the following: email, text message, and APP message push.

[0140] In the embodiment of the present invention, since the task list only includes the task ID corresponding to the call task and does not involve the user information corresponding to the task ID, when the supply end 102 assigns a call task to the call end 103, it does not interact with the server 104, and thus does not involve the acquisition of user information, effectively avoiding the leakage of user information by the supply end 102, thereby improving the security of user information.

[0141] like Figure 5 FIG. 1 is a schematic diagram of another embodiment of a user information management method in an embodiment of the present invention, which is applied to a user information management system. The user information management system includes a server, a demand end, and a call end. The method may include:

[0142] 501. Receive, through the server, user information sent by the demand side and a task identity ID corresponding to the user information.

[0143] The task ID is used by the calling end to obtain user information corresponding to the task ID from the server, and the user information includes the user name and contact information.

[0144] 502. Record, by the server, interaction information between the server and the calling end.

[0145] The interaction information includes first related information corresponding to when the calling end obtains user information from the server, and / or second related information corresponding to when the calling end sends feedback information to the server.

[0146] 503. Determine whether the call task executed by the calling end is normal according to the interaction information.

[0147] It should be noted that steps 501-503 are similar to those in this embodiment. Figure 2 The steps 201-203 shown are similar and will not be repeated here.

[0148] 504. Obtain the number of target calling terminals within a preset time period through the server.

[0149] The target calling end is the calling end corresponding to the abnormal call task being executed.

[0150] 505. When the number is greater than a preset number threshold, the server sends the second prompt information to the management terminal and disconnects the user access right of the target calling end to the server.

[0151] The second prompt information is used to prompt that the call task executed by the target calling end is abnormal.

[0152] Optionally, sending the second prompt information to the management terminal may include: sending the second prompt information to the management terminal in a fifth manner. The fifth manner may include but is not limited to one of the following: email, text message, and APP message push.

[0153] Optionally, the method may further include: sending the second prompt information to the management terminal by the server when the number is equal to the preset number threshold.

[0154] In an embodiment of the present invention, the server 104 can determine in real time whether the call task executed by the call end 103 is normal based on the recorded interaction information between the server 104 and the call end 103, effectively improving the timeliness of the server 104's analysis and judgment on whether the call task executed by the call end 103 is normal.

[0155] like Figure 6As shown, it is a schematic diagram of an embodiment of a server in an embodiment of the present invention, which may include: a transceiver module 601, a processing module 602 and an acquisition module 603;

[0156] The transceiver module 601 is used to receive the user information sent by the demand end and the task identity ID corresponding to the user information. The task ID is used by the calling end to obtain the user information corresponding to the task ID from the server. The user information includes the user name and contact information.

[0157] Optionally, in some embodiments of the present invention,

[0158] Processing module 602 is used to record the interaction information between the calling end and the calling end; based on the interaction information, determine whether the call task performed by the calling end is normal; wherein the interaction information includes the first relevant information corresponding to when the calling end obtains user information from the server, and / or the second relevant information corresponding to when the calling end sends feedback information to the server.

[0159] Optionally, in some embodiments of the present invention,

[0160] The processing module 602 is specifically used to obtain the characteristic data of the calling end according to the interactive information; input the characteristic data into a preset detection model and output a floating point value; and determine whether the call task executed by the calling end is normal according to the floating point value.

[0161] Optionally, in some embodiments of the present invention,

[0162] Processing module 602 is specifically used to determine through the server that the call task executed by the calling end is normal if the floating point value is greater than the first preset threshold and less than or equal to the second preset threshold; if the floating point value is greater than the second preset threshold and less than or equal to the third preset threshold, determine that the call task executed by the calling end is abnormal.

[0163] Optionally, in some embodiments of the present invention,

[0164] Processing module 602 is also used to send a first prompt message to the management terminal through the server if the floating point value is greater than the second preset threshold and less than or equal to the fourth preset threshold, and the first prompt message is used to prompt that the call task executed by the calling end is abnormal; if the floating point value is greater than the fourth preset threshold and less than or equal to the third preset threshold, the first prompt message is sent to the management terminal and the user access right of the calling end to the server is disconnected.

[0165] Optionally, in some embodiments of the present invention,

[0166] The acquisition module 603 is used to acquire the number of target call ends within a preset time period, where the target call ends are the call ends corresponding to the abnormal call tasks being executed;

[0167] The transceiver module 601 is also used to send the second prompt information to the management terminal and disconnect the user access right of the target calling end to the server when the number is greater than a preset number threshold. The second prompt information is used to prompt the target calling end that the call task executed is abnormal.

[0168] like Figure 7 As shown, it is a schematic diagram of an embodiment of a server in an embodiment of the present invention, which may include: a memory 701, a processor 702 and a transceiver 703; the memory 701 is coupled to the processor 702, and the processor 70 can call the executable program code stored in the memory 701; the memory 701 is coupled to the transceiver 703;

[0169] In an embodiment of the present invention, the transceiver 703 is used to receive the user information sent by the demand end and the task identity ID corresponding to the user information. The task ID is used by the calling end to obtain the user information corresponding to the task ID from the server. The user information includes the user name and contact information.

[0170] Optionally, processor 702 is used to record interaction information with the calling end; and determine whether the call task performed by the calling end is normal based on the interaction information; wherein the interaction information includes first relevant information corresponding to when the calling end obtains user information from the server, and / or second relevant information corresponding to when the calling end sends feedback information to the server.

[0171] Optionally, the processor 702 is specifically used to obtain characteristic data of the calling end according to the interactive information; input the characteristic data into a preset detection model and output a floating-point value; and determine whether the call task performed by the calling end is normal according to the floating-point value.

[0172] Optionally, the processor 702 is specifically used to determine through the server that the call task executed by the calling end is normal if the floating point value is greater than a first preset threshold and less than or equal to a second preset threshold; if the floating point value is greater than the second preset threshold and less than or equal to a third preset threshold, determine that the call task executed by the calling end is abnormal.

[0173] Optionally, processor 702 is also used to send a first prompt message to the management terminal through the server if the floating point value is greater than the second preset threshold and less than or equal to the fourth preset threshold, and the first prompt message is used to prompt that the call task executed by the calling end is abnormal; if the floating point value is greater than the fourth preset threshold and less than or equal to the third preset threshold, the first prompt message is sent to the management terminal and the user access right of the calling end to the server is disconnected.

[0174] Optionally, the processor 702 is further configured to obtain the number of target call terminals within a preset time period, where the target call terminals are corresponding to the call terminals when the executed call task is abnormal;

[0175] The transceiver 703 is also used to send the second prompt information to the management terminal and disconnect the user access right of the target calling end to the server when the number is greater than a preset number threshold. The second prompt information is used to prompt the target calling end that the call task executed is abnormal.

[0176] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0177] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present invention is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, a computer, a server, or a data center to another website site, a computer, a server, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or a data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive Solid State Disk (SSD)), etc.

[0178] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0179] In the several embodiments provided by the present invention, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0180] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0181] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0182] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for 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 method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc., various media that can store program codes.

[0183] As described above, the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features thereof may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A user information management system, characterized in that: include: Demand side, supply side, call side and server; The demand side is used to send a task list to the call side through the supply side, wherein the task list only includes the task identity ID corresponding to the call task; send user information and the task identity ID corresponding to the user information to the server, wherein the user information includes the user name and contact information, and the demand side sends the task list to the call side through the supply side, including: the supply side receives the task list sent by the demand side, and sends the task list to the call side; The server is used to receive the user information sent by the demand side and the task identity ID corresponding to the user information; the user information corresponding to the task identity ID is stored in the server; the supply side does not exchange information with the server during the process of allocating the call task to the call side; The calling end is used to receive the task list sent by the demand end; and obtain the user information corresponding to the task identity ID from the server according to the task list.

2. The user information management system according to claim 1, characterized in that: The server is further configured to record interaction information with the calling end; and determine whether the calling task performed by the calling end is normal according to the interaction information; The interaction information includes first related information corresponding to when the calling end obtains user information from the server, and / or second related information corresponding to when the calling end sends feedback information to the server.

3. The user information management system according to claim 2, characterized in that: The server is specifically used to obtain feature data of the calling end according to the interaction information; input the feature data into a preset detection model and output a floating point value; and determine whether the call task performed by the calling end is normal according to the floating point value.

4. The user information management system according to claim 3, characterized in that: The server is specifically configured to determine that the call task executed by the calling end is normal if the floating point value is greater than a first preset threshold and less than or equal to a second preset threshold; If the floating point value is greater than the second preset threshold and less than or equal to the third preset threshold, it is determined that the call task executed by the calling end is abnormal.

5. The user information management system according to claim 4, characterized in that: The server is further configured to send a first prompt message to the management terminal if the floating point value is greater than the second preset threshold and less than or equal to a fourth preset threshold, wherein the first prompt message is used to prompt that the call task executed by the calling end is abnormal; If the floating point value is greater than the fourth preset threshold and less than or equal to the third preset threshold, the first prompt information is sent to the management terminal, and the user access right of the calling end to the server is disconnected.

6. The user information management system according to claim 4 or 5, characterized in that: The server is also used to obtain the number of target call ends within a preset time period, and the target call end is the call end corresponding to the call task executed abnormally; when the number is greater than a preset number threshold, a second prompt message is sent to the management terminal, and the user access right of the target call end to the server is disconnected, and the second prompt message is used to prompt that the call task executed by the target call end is abnormal.

7. The user information management system according to any one of claims 2 to 5, characterized in that: The first relevant information includes at least one of a task identity ID, time, account, Internet Protocol IP address, browser type, and session ID corresponding to when the calling end obtains user information from the server; The second related information includes at least one of a task identity ID, time, account, IP address, browser type, and session ID corresponding to when the calling end sends feedback information to the server.

8. The user information management system according to any one of claims 3 to 5, characterized in that: The preset detection model includes one of the gradient descent decision tree GBDT, random forest algorithm, gradient boosting decision tree model XGBoosT, light gradient enhancement machine LightGBM, support vector machine, logistic regression and neural network model.

9. The user information management system according to claim 1, characterized in that: The demand side is specifically used to send a task list to the call side through the supply side in a first manner; and send user information and a task identity ID corresponding to the user information to the server in a second manner; The calling end is specifically used to obtain the user information corresponding to the task identity ID from the server by using a third method according to the task list; The first method, the second method and the third method include: a global wide area network WEB page method or a QR code method.

10. A user information management method, characterized in that: Applied to a user information management system, the user information management system includes a server, a demand side, a supply side and a call side, the method includes: The server receives user information sent by the demand side and a task identity ID corresponding to the user information. The task identity ID is used by the call side to obtain the user information corresponding to the task identity ID from the server. The user information includes the user name and contact information. The task identity ID is determined by the call side according to a task list sent by the demand side to the call side through the supply side. The task list only includes the task identity ID corresponding to the call task. The user information corresponding to the task identity ID is stored in the server. The supply side does not exchange information with the server during the process of allocating call tasks to the call side.

11. The method according to claim 10, characterized in that The method further comprises: Recording the interaction information between the server and the calling end; Determining, by the server according to the interaction information, whether the call task performed by the calling end is normal; The interaction information includes first related information corresponding to when the calling end obtains user information from the server, and / or second related information corresponding to when the calling end sends feedback information to the server.

12. The method according to claim 11, characterized in that The determining, by the server according to the interaction information, whether the call task performed by the calling end is normal includes: obtaining, by the server according to the interaction information, characteristic data of the calling end; Inputting the feature data into a preset detection model through the server and outputting a floating point value; The server determines whether the call task performed by the calling end is normal according to the floating point value.

13. The method according to claim 12, characterized in that The determining, by the server according to the floating point value, whether the call task executed by the calling end is normal includes: If the floating point value is greater than the first preset threshold and less than or equal to the second preset threshold, it is determined that the call task executed by the calling end is normal; if the floating point value is greater than the second preset threshold and less than or equal to the third preset threshold, it is determined that the call task executed by the calling end is abnormal.

14. The method according to claim 13, characterized in that After determining that the call task executed by the calling end is abnormal if the floating point value is greater than the second preset threshold and less than or equal to the third preset threshold, the method further includes: If the floating point value is greater than the second preset threshold and less than or equal to the fourth preset threshold, a first prompt message is sent to the management terminal, where the first prompt message is used to prompt that the call task executed by the calling end is abnormal; If the floating point value is greater than the fourth preset threshold and less than or equal to the third preset threshold, the first prompt information is sent to the management terminal, and the user access right of the calling end to the server is disconnected.

15. The method according to claim 13 or 14, characterized in that The method further comprises: Acquiring the number of target call terminals within a preset time period through the server, wherein the target call terminals are corresponding call terminals when the executed call task is abnormal; When the number is greater than a preset number threshold, the server sends a second prompt message to the management terminal and disconnects the user access right of the target call end to the server. The second prompt message is used to prompt that the call task executed by the target call end is abnormal.

16. A server, characterized in that: Applied to a user information management system, the user information management system further includes a demand side, a supply side and a call side, and the server includes: A transceiver module is used to receive the user information sent by the demand side and the task identity ID corresponding to the user information, wherein the task identity ID is used by the call side to obtain the user information corresponding to the task identity ID from the server, and the user information includes the user name and contact information; the task identity ID is determined by the call side according to the task list sent by the demand side to the call side through the supply side; the task list only includes the task identity ID corresponding to the call task; the user information corresponding to the task identity ID is stored in the server; the supply side does not exchange information with the server during the process of allocating call tasks to the call side.

17. A server, characterized in that: include: A memory storing executable program code; and a processor and a transceiver coupled to the memory; The processor calls the executable program code stored in the memory, and when the executable program code is executed by the processor, the processor and the transceiver implement the method according to any one of claims 10 to 15.

18. A computer-readable storage medium having executable program code stored thereon, characterized in that: When the executable program code is executed by a processor, the method according to any one of claims 10 to 15 is implemented.

Images