A user lead query method and related device

Abstract

An embodiment of the present application discloses a method for querying user leads. The method includes: obtaining a user lead query request including multiple filtering conditions; matching the user lead information set in the value field of the key-value pair data table according to the multiple filtering conditions, where the value field of the key-value pair entry is used to store the user lead information corresponding to the user identifier; screening out the target key-value pair entries corresponding to the multiple filtering conditions from the key-value pair entries included in the key-value pair data table through the matching result; and determining the query result corresponding to the user lead query request according to the target key-value pair entries. The processing device can centrally store the user lead information in a single key-value pair data table, so that when determining the users meeting the filtering conditions through the user lead information, only a single-table query needs to be performed in this data table, reducing the query difficulty; at the same time, by setting the user lead information in the value field with relatively low modification difficulty, it is convenient to update the user lead information.

Description

Technical Field

[0001] This application relates to the field of data processing, and in particular, to a method for querying user leads and related devices. Background Art

[0002] In addition to providing social services for ordinary users, social software can also provide social services for enterprise users. During the service provision process, user lead information is determined based on user behavior. The user status included in a user's user lead information can reflect what services this user can currently obtain.

[0003] However, since user lead information is generated based on user behavior in social software, the relevant data currently used to determine user lead information is scattered in data tables corresponding to each user behavior process.

[0004] In the related art, when it is necessary to query user lead information to determine what services to provide to a user that match the current user status, only a join query can be performed on multiple scattered data tables based on the query requirements. The logical complexity of the join query is relatively large, and it will also bring a large overhead to the system. Summary of the Invention

[0005] To solve the above technical problems, this application provides a method for querying user leads. The processing device can convert the relevant data in multiple data tables into the user lead information of a user, and set it corresponding to the user identifier of the user in a unified key-value pair data table. Thus, when determining a user that meets the screening conditions through the user lead information, only a single-table query needs to be performed in this key-value pair data table, reducing the query difficulty; at the same time, by setting the user lead information in a value field with a relatively low modification difficulty, it is convenient to update the user lead information, improving the convenience of the key-value pair data table.

[0006] Embodiments of this application disclose the following technical solutions:

[0007] In a first aspect, an embodiment of this application provides a method for querying user leads, and the method includes:

[0008] Obtain a user lead query request including multiple screening conditions;

[0009] Match the user lead information set in the value field of the key-value pair data table according to the multiple screening conditions. The key-value pair data table stores the user identifier through the key field of the key-value pair entry, and the value field of the key-value pair entry is used to store the user lead information corresponding to the user identifier;

[0010] From the key-value pair entries included in the key-value pair data table, filter out the target key-value pair entries corresponding to the multiple filtering conditions according to the matching result;

[0011] Determine the query result corresponding to the user lead query request according to the target key-value pair entries;

[0012] Among them, the key-value pair data table is updated in the following manner:

[0013] Obtain the lead data to be updated through a timing queue, where the lead data is used to determine the user lead information;

[0014] Determine the corresponding pending user status according to the lead data;

[0015] Determine whether to update the key-value pair data table according to the user identifier corresponding to the lead data and the pending user status.

[0016] In a second aspect, an embodiment of the present application provides a user lead query device, which includes a first acquisition unit, a matching unit, a filtering unit, a first determination unit, a fourth acquisition unit, a second determination unit, and a third determination unit:

[0017] The first acquisition unit is configured to acquire a user lead query request including multiple filtering conditions;

[0018] The matching unit is configured to match the user lead information set in the value field of the key-value pair data table according to the multiple filtering conditions. The key-value pair data table stores the user identifier through the key field of the key-value pair entry, and the value field of the key-value pair entry is used to store the user lead information corresponding to the user identifier;

[0019] The filtering unit is configured to, through the matching result, filter out the target key-value pair entries corresponding to the multiple filtering conditions from the key-value pair entries included in the key-value pair data table;

[0020] The first determination unit is configured to determine the query result corresponding to the user lead query request according to the target key-value pair entries;

[0021] The fourth acquisition unit acquires the lead data to be updated through a timing queue, and the lead data is used to determine the user lead information;

[0022] The second determination unit is configured to determine the corresponding pending user status according to the lead data;

[0023] The third determination unit is configured to determine whether to update the key-value pair data table according to the user identifier corresponding to the lead data and the pending user status.

[0024] In a third aspect, an embodiment of the present application provides a computer device, which includes a processor and a memory:

[0025] The memory is used to store program code and transmit the program code to the processor;

[0026] The processor is used to execute the user clue query method described in the first aspect according to the instructions in the program code.

[0027] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which is used to store a computer program, and the computer program is used to execute the user clue query method described in the first aspect.

[0028] It can be seen from the above technical solutions that the user clue information generated through different user behavior processes is uniformly stored in a key-value pair data table. The key field of the key-value pair entry in the key-value pair data table is set with a user identifier, and the value field is set with the user clue information corresponding to the user identifier. When it is necessary to query user clues through the user clue information, according to the user clue query request including multiple screening conditions, the screening conditions are matched through the user clue information set in the value field of the key-value pair data table, and the target key-value pair entries corresponding to the multiple screening conditions are screened out from the key-value pair entries included in the key-value pair data table. The query result corresponding to the user clue query request is determined according to the target key-value pair entry. Since the user clue information is uniformly set in a key-value pair data table, when matching the user clue information, there is no need to perform a join query with a high time complexity through multiple data tables as in the related art, which reduces the screening complexity and improves the screening efficiency. At the same time, since in the key-value pair data table, the editing difficulty of the value field is less than that of the key field, it is convenient to update the user clue information corresponding to each user identifier, thereby realizing a specific retrieval method of the key-value pair data table through the value field instead of the key field. On the premise of ensuring the retrieval efficiency, the update convenience of the key-value pair data table is improved, and the maintenance difficulty of the key-value pair data table is reduced. Description of the Drawings

[0029] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0030] Figure 1 It is a schematic diagram of a user clue query method in an actual application scenario provided by an embodiment of the present application;

[0031] Figure 2 Flow chart of a user lead query method provided by an embodiment of the present application;

[0032] Figure 3 Schematic diagram of a user lead query method provided by an embodiment of the present application;

[0033] Figure 4 Schematic diagram of a user lead query method provided by an embodiment of the present application;

[0034] Figure 5 Schematic diagram of a user lead query method provided by an embodiment of the present application;

[0035] Figure 6 Schematic diagram of a user lead query method provided by an embodiment of the present application;

[0036] Figure 7 Schematic diagram of a user lead query method provided by an embodiment of the present application;

[0037] Figure 8 Schematic diagram of a user lead query method provided by an embodiment of the present application;

[0038] Figure 9 Schematic diagram of a user lead query method in an actual application scenario provided by an embodiment of the present application;

[0039] Figure 10 Schematic diagram of a user lead query method in an actual application scenario provided by an embodiment of the present application;

[0040] Figure 11 Block diagram of the structure of a user lead query device provided by an embodiment of the present application;

[0041] Figure 12 Structure diagram of a computer device provided by an embodiment of the present application;

[0042] Figure 13 Structure diagram of a server provided by an embodiment of the present application. Detailed implementation manners

[0043] The embodiments of the present application will be described below with reference to the accompanying drawings.

[0044] Querying enterprise users that meet the requirements through user lead information is one of the common operations for ordinary users when using social software. Since the user lead information may include information on various user behaviors, in related technologies, data related to the user lead information is stored in multiple data tables corresponding to multiple user behaviors. When a user performs a filtering query through the user lead information, the processing device needs to first obtain the data related to the user lead information from multiple data tables, and then determine whether the user lead information corresponding to the user meets the filtering conditions for this screening based on this related data. This requires the processing device to perform a joined-table query in multiple data tables, resulting in a relatively high query difficulty and low efficiency.

[0045] To solve the above technical problems, this application provides a user lead query method. The processing device can convert the relevant data in multiple data tables into the user's user lead information and set it corresponding to the user identification in a unified key-value pair data table. Thus, when determining the users that meet the screening conditions through the user lead information, only a single-table query in this key-value pair data table needs to be performed, reducing the query difficulty. At the same time, by setting the user lead information in a value field with relatively low modification difficulty, it is convenient to update the user lead information, improving the convenience of the key-value pair data table.

[0046] It can be understood that this method can be applied to a processing device, which is a processing device with an information query function, such as a terminal device or a server with an information query function. This method can be independently executed by the terminal device or the server, or can also be applied to a network scenario where the terminal device and the server communicate, and runs through the cooperation of the terminal device and the server. Among them, the terminal device can be a mobile phone, a desktop computer, a personal digital assistant (Personal Digital Assistant, abbreviated as PDA), a tablet computer, and other devices. The server can be understood as an application server or a Web server. In actual deployment, the server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. The terminal and the server can be directly or indirectly connected through wired or wireless communication methods, and this application does not make any restrictions here.

[0047] To facilitate the understanding of the technical solution of this application, next, a user lead query method provided by an embodiment of this application will be introduced in combination with an actual application scenario.

[0048] See Figure 1 , Figure 1A schematic diagram of a user lead query method provided by an embodiment of this application. In this actual application scenario, the processing device is server 102, which can aggregate the user lead information generated by each user behavior process in a key-value data table. The key-value data table includes multiple key-value table entries. One key-value table entry is used to store the user identifier and user lead information of a user. The user identifier is set in the key field of the key-value table entry, and the user lead information is set in the value field of the key-value table entry. For example, the user identifier can be the enterprise identifier shown in the figure, and the user lead information can include information such as enterprise certification status, number of enterprise employees, and location of the enterprise.

[0049] User lead information refers to various information related to the user himself. Based on this user lead information, other users can query users who meet their own needs from multiple users. For example, as Figure 1 shown, when a user has a query requirement, multiple filtering conditions can be set through terminal device 101, such as setting an enterprise employee number range, enterprise location range, etc. Terminal device 101 can generate a user lead query request according to the multiple filtering conditions set by the user, and send the user lead query request to server 102. The user lead query request is used to query users that match the multiple filtering conditions.

[0050] After obtaining the user lead query request, server 102 can match the user lead information set in the value field of the key-value data table according to the multiple filtering conditions included therein. Through the matching result, target key-value table entries are filtered out from the key-value table entries included in the key-value data table. The target key-value table entry refers to the key-value table entry whose user lead information set in the value field meets the multiple filtering conditions, indicating that the user corresponding to the target key-value table entry meets the user needs of the user who initiated this query. For example, when a user wants to query an enterprise located in City A, with more than 100 employees and certified, the filtering conditions can be set as "located in City A", "enterprise employees more than 100", and "enterprise certified". Server 102 can match the filtering conditions with the value field in the key-value data table, and determine the key-value table entry with user lead information that meets the filtering conditions as the target key-value table entry. Subsequently, the server can determine the query result corresponding to the user lead query request according to the target key-value table entry and send it to terminal device 101 for the user to view.

[0051] Since the key-value pair data table is a unified data table with user identifiers of multiple users and corresponding user lead information, when the server 102 conducts lead queries, it only needs to query in this data table, without the need to perform a joined table query in multiple data tables, simplifying the query logic of the data table, reducing the difficulty of the query operation, thereby reducing the requirements for the query capabilities of the query device and enabling this user lead query method to be applied to more devices. In addition, since the user lead information is set in the value field of the key-value pair data table, compared with the key field, the information in the value field is easier to modify. Therefore, when the processing device needs to update the key-value pair data table, the update difficulty is lower, improving the convenience of the key-value pair data table.

[0052] Next, in combination with the accompanying drawings, a user lead query method provided by an embodiment of the present application will be introduced.

[0053] See Figure 2 , Figure 2 which is a flowchart of a user lead query method provided by an embodiment of the present application. The method includes:

[0054] S201: Obtain a user lead query request including multiple screening conditions.

[0055] During the process of using a social software, there may be a need to query certain specific users. For example, when a user wants to cooperate with some other users in this social software, they may perform a query operation to find users that meet their own needs; when a user wants to provide services for other users, they may need to perform a query operation to find users who need this service.

[0056] Among them, when querying users, in order to be able to find the required users, the processing device first needs to determine a query basis that can be used for accurate query. It can be understood that since the query operation is mainly executed based on the query intention of the query initiator, in the embodiments of the present application, the processing device can pre-provide the query initiator with the function of selecting screening conditions, which are used to screen the users recorded in the social software during the query process. The query initiator can use this function to select the conditions that the users they want to find should have.

[0057] For example, as Figure 3 shown, Figure 3Shows a schematic diagram of the interface of a social software with a filtering query function. In the scenario corresponding to this schematic diagram, the query initiator can be a service provider who wants to provide services to other users, and other users can be potential service customers who have registered on this social platform. As shown in the figure, the potential service customers can include project test customers, beverage stores, design companies, training schools, etc. The processing device can provide the service provider with multiple filtering conditions including service source, service status, service method, allocation time, enterprise certification status, etc., and the service provider can select any one or more of these filtering conditions for filtering. Among them, the service source refers to the source from which the service provider provides services, such as including promotion activities of attendance machines, direct promotion by high-quality enterprises, active appointment for on-site services, etc.; the service status refers to the status of the service corresponding to the customer currently, including not contacted, contacted, reserved, etc.; the service method refers to the way the customer needs to be served, which can include on-site service, remote service, etc.; the allocation time refers to the time when the service corresponding to the customer is allocated, which can include yesterday, the last 7 days, the last 30 days, etc.; the enterprise certification status refers to whether the enterprise corresponding to the customer has completed the entity certification, which can include completed and not completed, etc.

[0058] As shown in the following table, the following table shows multiple filtering conditions that can be used for user queries:

[0059]

[0060]

[0061] As Figure 3 shown, the service provider can set the filtering conditions as "direct promotion by high-quality enterprises", "not contacted", "remote service", and "the last 7 days", and then click the "OK" control in the lower right corner to query customers. After triggering the query, a user lead query request including multiple filtering conditions can be generated. This user lead query request is used to query the user lead information corresponding to each user through these filtering conditions. The user lead information refers to various information related to the user himself, such as the service status of the service corresponding to the user, the required service method, etc. The processing device can obtain this user lead query request and provide the query initiator with users that meet the filtering conditions.

[0062] S202: Match the user lead information set in the value field of the key-value pair data table according to multiple filtering conditions.

[0063] As described above, user lead information refers to various information related to the user himself / herself. Since user lead information is usually generated based on the user's behavior in this social software, and different user lead information may need to be obtained from different user behavior processes. Therefore, in the related art, when a processing device wants to screen and query users through multiple screening conditions, the user lead information corresponding to the multiple screening conditions may be stored in multiple different user behavior processes, for example, it may be stored in the data tables corresponding to multiple user behavior processes. The processing device needs to perform a join query in multiple data tables based on multiple screening conditions to determine the users who meet multiple screening conditions at the same time, which will bring a large amount of processing pressure to the processing device, consume a long time, and have a low query efficiency.

[0064] For example, in the related art, the enterprise authentication status of a user is stored in the data table corresponding to the enterprise entity authentication process, and the enterprise compliance status of the user is stored in the data table corresponding to the enterprise standard authentication process. If the screening conditions set by the query party are "the enterprise entity has been authenticated" and "the enterprise has met the standards", then it is necessary to first query the authenticated users from the data table corresponding to the enterprise entity authentication process, query the compliant users from the data table corresponding to the enterprise standard authentication process, and then take the users who are simultaneously in these two parts of users as the users corresponding to this query and feedback them to the query party, which requires multiple queries and processing.

[0065] In order to simplify the query logic and improve the query efficiency, in the embodiments of the present application, the processing device can first centralize the user lead information in the data tables corresponding to multiple user behavior processes in a key-value pair data table. The key-value pair data table stores the user identifier through the key field of the key-value pair entry. The value field of the key-value pair entry is used to store the user lead information corresponding to the user identifier. The user lead information includes the user lead information corresponding to the user with the user identifier in the data tables of multiple user behavior processes. The key-value pair entry is the unit entry of the key-value pair data table, and one key-value pair entry is used to store the user lead information of one user.

[0066] Since the key-value pair data table includes the user lead information corresponding to the user in multiple user behavior processes, when the processing device obtains a user lead query request, it does not need to perform a multi-table join query, but only needs to match the user lead information set in the value field of the key-value pair data table according to multiple screening conditions. As Figure 4 shown, Figure 4It shows a schematic diagram of a key-value pair data table in an embodiment of the present application. The user lead information of the user identifier A in the data tables of the service status recording process, service mode recording process, enterprise entity authentication process, and enterprise standard authentication process can be centrally stored in the key-value pair data table, forming a key-value pair data table with unified user lead information. The key field in the key-value pair entry corresponding to this user is used to store the user identifier A, and the value field in the key-value pair entry is used to store the user lead information corresponding to the user identifier A.

[0067] Since only one key-value pair data table needs to be queried and matched, and this key-value pair data table includes user lead information corresponding to multiple user behavior processes, the processing device only needs to perform one query in this key-value pair data table to determine the users that meet the screening conditions, without having to perform multiple queries in multiple data tables. In addition, it can be understood that in the key-value pair data table, the editing difficulty of the key field is much higher than that of the value field, and the user lead information is more likely to change as the user progresses in the user behavior process and needs to be modified and updated in real time. Therefore, in the embodiment of the present application, by storing the user lead information in the value field and matching the value field during query, it is convenient to update the user lead information, improving the convenience of the key-value pair data table.

[0068] S203: Through the matching result, screen out the target key-value pair entries corresponding to multiple screening conditions from the key-value pair entries included in the key-value pair data table.

[0069] After obtaining the user lead query request, the processing device can match the screening conditions included in the request with the user lead information stored in the value field of the key-value pair data table to obtain a matching result that meets the multiple screening conditions. The matching result can be a key-value pair entry with user lead information that meets the multiple screening conditions, that is, the user corresponding to this key-value pair entry is the user required by the querying party. For example, if the screening conditions included in the user lead query request are "authenticated", "qualified", and "door-to-door service", then Figure 4 the user lead information corresponding to the user identifier A shown meets the screening conditions, and this key-value pair entry can be used as the matching result of this match. The user corresponding to the user identifier A can be fed back to the querying party as the user required by the querying party. Therefore, through this matching result, the processing device can screen out the key-value pair entries that meet the screening conditions from the key-value pair data table, and then can determine the target key-value pair entries corresponding to multiple screening conditions from these key-value pair entries. The target key-value pair entries refer to any one or more key-value pair entries among the key-value pair entries that meet the screening conditions.

[0070] For example, when the processing device wants to provide as many query results as possible for the user, all key-value pair entries that meet the filtering conditions can be used as target key-value pair entries and fed back to the user through the matching result. In addition, for other purposes, the processing device can also determine some key-value pair entries that meet the filtering conditions as target key-value pair entries and feed them back to the user.

[0071] S204: Determine the query result corresponding to the user clue query request according to the target key-value pair entries.

[0072] The processing device can generate the query result corresponding to this user clue query request based on the determined target key-value pair entries. This query result is used to enable the querying party to know the users who meet the filtering conditions and the information related to these users. For example, the processing device can generate a profile interface corresponding to the user identifier according to the user identifier and user clue information in the target key-value pair entries, and feed this interface back to the user as the query result.

[0073] As Figure 5 shown, Figure 5 FIG. is a schematic diagram of the query result determined by the processing device. The filtering conditions set for this query can be that the server status is "not contacted", a custom time period from "2020 / 9 / 18 - 2020 / 9 / 21", etc. The processing device can generate profile interfaces of multiple users who meet this filtering condition based on the determined target key-value pair entries for the querying party to view and select.

[0074] As can be seen from the above technical solution, the user lead information generated through different user behavior processes is uniformly stored in a key-value pair data table. The user identifier is set through the key field of the key-value pair entry in the key-value pair data table, and the user lead information corresponding to the user identifier is set through the value field. When it is necessary to query user leads through the user lead information, according to the user lead query request including multiple filtering conditions, the user lead information set through the value field of the key-value pair data table is used to match the filtering conditions, and the target key-value pair entries corresponding to the multiple filtering conditions are filtered out from the key-value pair entries included in the key-value pair data table. The query result corresponding to the user lead query request is determined according to the target key-value pair entries. Since the user lead information is uniformly set in a key-value pair data table, when matching user lead information, there is no need to perform a join query with a high time complexity through multiple data tables as in the related art, which reduces the filtering complexity and improves the filtering efficiency. At the same time, since in the key-value pair data table, the editing difficulty of the value field is less than that of the key field, it is convenient to update the user lead information corresponding to each user identifier, thereby realizing a specific retrieval method for the key-value pair data table through the value field instead of the key field. On the premise of ensuring the retrieval efficiency, the update convenience of the key-value pair data table is improved, and the maintenance difficulty of the key-value pair data table is reduced.

[0075] As mentioned above, for other purposes, the processing device can determine some key-value pair entries in the key-value pair data table that meet the filtering conditions as the target key-value pair entries based on the matching result and feedback them to the querying party. For example, in a possible implementation, the number of query results that can be displayed at one time on the query result display page of a social software may be limited. For example, in Figure 5 the shown query result display page, only four users who meet the filtering conditions and their related information can be displayed at one time. Therefore, to further improve the query efficiency, the processing device can filter out a target number of target key-value pair entries from the key-value pair entries included in the key-value pair data table, and the target number is determined according to the display number of the query result display page.

[0076] For example, when matching user lead information set for value fields, the processing device can count the number of key-value pair entries in the obtained matching results. After this number reaches the target number, the processing device can stop the matching and use the key-value pair entries of this target number as the target key-value pair entries. Thus, the processing device does not need to match the value fields of all key-value pair entries in the key-value pair data table, and only needs to obtain the target key-value pair entries of the target number, saving query time and improving the speed at which the processing device feeds back the query results to the query initiator. In related technologies, when only the target number of user query results are needed, since users meeting each screening condition are first separately queried in multiple data tables and then the intersection users are taken as the query results from these users, the processing device cannot determine whether and when it has obtained the target number of users meeting the screening conditions before the full-scale query of each data table is completed. This will cause the processing device to waste a lot of time on user queries, which is not conducive to improving the query experience of the query initiator and results in low query efficiency.

[0077] Meanwhile, it can be understood that when the processing device displays the query results to the query initiator in the form of a query result display page, if the query initiator cannot find a satisfactory user on the current page, the query initiator may jump to the next query result display page through a paging operation to view more query results; if the query initiator finds a satisfactory user on the current page, it is very likely that the query initiator will not continue to view more query results but perform subsequent operations based on this user. Based on this, on the basis of saving query time and improving query efficiency, in order to provide the query initiator with query results that meet the requirements, the processing device can monitor the operations of the query initiator and judge whether the users displayed on the current page of the query result display page can meet the requirements of the query initiator through the operations of the query initiator.

[0078] In a possible implementation manner, if the processing device obtains a paging operation for this query result display page, it indicates that the users displayed on the current page cannot meet the requirements of the query initiator. At this time, in order to provide the query initiator with richer query results, the processing device can, according to this paging operation, re-execute the step of matching the user status set for the value fields in the key-value pair data table according to multiple screening conditions, so as to find more users meeting this screening condition. For example, a new batch of target key-value pair entries of the target number can be determined as the query results and fed back to the user.

[0079] It can be understood that, in order to avoid providing the query initiator with query results that have already been displayed, when the processing device matches the key-value pair data table, after determining the target number of target key-value pair entries, it can record the key-value pair entries that have not been matched by adding identifiers. When it is necessary to re-execute the step of matching the user status set in the value field of the key-value pair data table according to multiple filtering conditions, the matching can be performed from the unmatched key-value pair entries, thereby avoiding providing duplicate query results to the query initiator to a certain extent and improving the query experience of the query initiator.

[0080] It can be understood that the user lead information in the key-value pair data table is collected from the data tables corresponding to each user behavior process and other relevant data tables. In actual situations, the user's own information may change, and as the user operates in each user behavior process, the information of the user in the data tables corresponding to these user behavior processes may also change. For example, user lead information such as the enterprise authentication status, enterprise compliance status, and service status corresponding to the user may change as the user operates in each user behavior process in the social software, and the user's own information such as the geographical location and the number of employees hired may change as the user changes in actual situations. Therefore, in order to make the user lead information stored in the key-value pair data table more comprehensive and effective, during the query process through the key-value pair data table, the processing device can also write back the user lead information stored in the key-value pair data table in various ways, that is, improve and update the user lead information in the table.

[0081] As mentioned above, user lead information is various information related to the user himself. Among them, for different types of user lead information, the way the processing device writes back may also be different. The user lead information related to the user's status in each user behavior process can be called the user status. For example, the status of the user in the enterprise entity authentication process can include "completed entity authentication" status and "uncompleted entity authentication" status, etc., and in the enterprise standard authentication process, it can include "compliant" status and "non-compliant" status, etc. Since these user statuses are related to the process situation of the user in the user behavior process, the user status may often change during the operation of the user behavior process. Based on this, in order to make the user lead information in the key-value pair data table have a high degree of accuracy, the processing device can update the user lead information stored in the value field based on the change of the user's user status.

[0082] In a possible implementation, the user clue information includes the user status. When the user goes through various user behavior processes, if the user status of the user is successfully changed due to the user's behavior, a status update request for requesting to change the user status can be triggered. This status update request is used to instruct the processing device to change the corresponding user status in the key-value pair data table. It can be understood that the status update request is triggered based on the user status changed by the user in the user behavior process. Therefore, in order to enable the processing device to know the user whose status has changed and the specific change situation, the user identification of the user whose status has changed and the user status after the change of this user can be carried in this status update request.

[0083] The processing device can obtain the status update request for requesting to change the user status, and then update the key-value pair data table according to the user identification and the changed user status carried in this status update request. For example, the processing device can, according to this user identification, find out the key-value pair table entry corresponding to this user in the key-value pair data table, and then update the user status in the user clue information saved in the value field of this key-value pair table entry to the changed user status.

[0084] Among them, since there may be various user behavior processes in the social software, the user status included in the user clue information can also include a variety of statuses. For example, the user status in the enterprise standard detection process can include the compliance status of having met the standard and not having met the standard, and this compliance status is used to identify whether the enterprise standard detection corresponding to this user has passed; the user status in various authentication processes can include authentication statuses such as having been authenticated and not having been authenticated, and this authentication status is used to identify whether the user has passed the authentication.

[0085] In a possible implementation, when the user status is the authentication status of the user in the authentication process, when the user executes this authentication process, if an unauthenticated user successfully passes the authentication, or an authenticated user fails the authentication in a new round of user authentication process, a user authentication request can be initiated to the processing device. This user authentication request is used to request to change the authentication status of the user. The processing device can obtain the user authentication request received in the user authentication process and use this user authentication request as this status update request to update the user authentication status in the key-value pair data table.

[0086] For example, as Figure 6 shown, Figure 6A schematic diagram for updating a user status is shown, and the user status may be the enterprise entity authentication status corresponding to the user. The enterprise entity authentication background module is used to execute the enterprise entity authentication process. If a user who originally did not pass the enterprise entity authentication completes the enterprise entity authentication in the process, the enterprise entity authentication background module may initiate a user authentication request to the processing device. The user authentication request may carry the user ID of the user who has completed the enterprise entity authentication and the authentication status of the changed user, that is, the status of the completed enterprise entity authentication. The processing device may update the corresponding authentication status in the key-value pair data table according to the user authentication request.

[0087] As mentioned above, the user status is only part of the user clue information, and not all user statuses may be updated in real time through the user's behavior in various user behavior processes. Therefore, in order to maintain the validity of the information in the key-value pair data table as much as possible, in the embodiment of the present application, the processing device can also update the user clue information in the key-value pair data table in other ways.

[0088] It is understandable that some user clue information in the key-value pair data table can be determined by collecting data from other databases. For example, when the user clue information is information used to reflect whether the user meets the standards, the processing device may need to first obtain data related to the user standards when determining the user clue information, and judge whether the user meets the standards based on these data, so as to determine the user clue information. For this type of user clue information, when the processing device determines whether to update it, it first needs to obtain the clue data used to determine the user clue information. For example, when the user clue information is whether the number of employees employed by the user meets the standards, the clue data can be the number of employees employed by the user.

[0089] In a possible implementation, the key-value pair data table may be updated in the following manner:

[0090] The processing device can obtain the clue data to be updated through the timing queue, and the clue data is used to determine the user clue information. The clue data to be updated can be used to enable the processing device to update the key-value pair data table. It is understandable that because the clue data may have a certain stability over a period of time, and when the clue data changes, it may not affect the user clue information recorded in the key-value pair data table. For example, when the clue information is information used to determine whether a certain enterprise meets the standards, if the user clue information corresponding to the enterprise in the key-value pair data table has met the standards, and the clue information is still within the scope of the enterprise's standards after the change, then the user clue information does not actually need to be updated.

[0091] Based on this, the processing device can first determine the corresponding pending user status according to the clue data, and this pending user status is used to identify whether the user clue information corresponding to the clue data needs to be updated. The processing device can determine whether to update the key-value pair data table according to the user identifier corresponding to the clue data and the pending user status. Among them, the user identifier corresponding to the clue data is used to determine the user clue information corresponding to the clue data in the key-value pair data table.

[0092] Among them, when updating the user clue information based on the clue data, due to different focuses of the update, the specific update methods of the processing device may also be different. For example, in a possible implementation, since when some clue data is updated, the corresponding user clue information has a high probability of needing to be updated. In this case, in order to be able to update the user clue information as soon as possible when the clue data changes, so as to improve the effectiveness of the user clue information, the processing device can monitor the database responsible for storing the clue data. If the clue data is updated, the processing device can obtain the updated clue data, that is, the processing device can determine whether the corresponding pending user status is a status that needs to be updated or a status that does not need to be updated according to whether the clue data is the updated clue data. It can be understood that in the database responsible for storing the clue data, in order to prevent data chaos and accurately record the clue data corresponding to each user, the clue data is usually stored corresponding to the user identifier of the user in the database. Based on this, in order to enable the processing device to know the user corresponding to the updated clue data, the updated clue data obtained by the processing device can include the corresponding user identifier. The processing device can update the key-value pair data table according to the updated clue data and the corresponding user identifier.

[0093] It can be understood that when the clue data is updated, the updated clue data does not necessarily cause the corresponding user clue information to need to be updated. For example, when the clue data is clue data related to a certain user standard, a user who was originally unqualified may still not meet the requirements of the user standard after the update of the clue data this time. Therefore, in the user clue information corresponding to this user, this user is still in the unqualified state and there is no need to update the user clue information. Therefore, in order to further improve the accuracy of the update of the user clue information, after obtaining the updated clue data, the processing device can determine whether to update the user clue information corresponding to the user identifier according to the clue information and the corresponding user identifier, and then perform the operation of updating the key-value pair data table after determining that the update is required.

[0094] For example, when the lead data is the number of employees hired by a user, the user lead information can be whether the number of employees hired by the user reaches the required value. When the processing device monitors the database responsible for storing the number of employees hired by the user and finds that the number of employees hired by a certain user has been updated, it can obtain the updated number of employees hired and the user identifier of the user, and determine whether the number of employees hired by the user reaches the required value. Subsequently, the processing device can obtain, based on the user identifier, whether the current user lead information corresponding to the user identifier in the key-value pair data table is in the "has reached the required value" state or the "has not reached the required value" state. If the current state is the "has not reached the required value" state, and after this update of the lead data, the processing device determines that the number of employees hired by the user still has not reached the required value, then there is no need to update the user lead information; if it is determined that the number of employees hired by the user reaches the required value, then the user lead information can be updated.

[0095] Among them, in addition to monitoring the relevant database as described above and immediately obtaining the updated data when the lead data is updated, the ways for the processing device to obtain the updated lead data can also include various methods. For example, in one possible implementation, in order to be able to update the key-value pair data table at a reasonable update frequency, the processing device can set one or more timed queues, and the timed queue is used to obtain the updated lead data at regular intervals. The processing device can set the time node or time interval for obtaining the lead data for the timed queue, as well as the database from which it obtains the updated lead data. When the time interval has passed or the time node is reached, the processing device can obtain the updated lead data from the database through the timed queue.

[0096] As Figure 7 shown, Figure 7 FIG. shows a schematic diagram of updating the key-value pair data table through a timed queue. The timed queue can obtain the updated lead data from the background of the relevant database and return the updated lead data to the processing device. The processing device can update the user lead information in the key-value pair data table based on the updated lead data and the corresponding user identifier. Among them, the timed queue can be a queue set in the processing device. Here, in order to show the utilization relationship between the processing device and the timed queue, it is separately displayed. Figure 8 Similarly.

[0097] The above method can obtain the updated data in the first time when the lead data is updated and complete the update of the user lead information, which is beneficial to improving the effectiveness of the user lead information. In addition, in order to be able to update the user lead information as comprehensively as possible and avoid missing updates, in another possible implementation, the processing device can also update the key-value pair data table not based on the updated lead data, but based on the user lead information in the key-value pair data table.

[0098] It is understandable that user lead information may have a certain timeliness. After exceeding the time limit corresponding to this timeliness, the effectiveness of user lead information may decrease. For example, a certain qualification obtained by a user may only be valid for three months. After three months of passing the certification, this user qualification will become invalid. At this time, in order to ensure the accuracy of the user qualification recorded in the user lead information, the processing device can re-obtain the lead data related to the qualification verification and determine whether the user can still obtain this user qualification.

[0099] Based on this, in order to improve the accuracy of user lead information in the key-value pair data table, the processing device can first determine a preset time period. This preset time period is the time period during which the processing device needs to determine whether to update the user lead information when updating the user lead information. The processing device can determine this preset time period based on the timeliness of the user lead information. For example, when the timeliness of most user lead information in the key-value pair data table is 15 days, this preset time period can be 15 days, that is, the processing device can obtain the user lead information within 15 days for updating.

[0100] The processing device can obtain the target user lead information in the key-value pair data table within this preset time period. This target user lead information is the user lead information that needs to be determined whether to be updated this time. As mentioned above, this part of user lead information is determined through lead data. Therefore, in order to determine whether this target user lead information needs to be updated, the processing device can obtain the lead data corresponding to this target user lead information. This lead data is used to determine the user lead information. The processing device can determine the corresponding pending user lead information based on this lead data. This pending user lead information is the accurate user lead information currently corresponding to this lead data.

[0101] As mentioned above, in order to be able to effectively store the lead data and avoid data chaos and the situation where it is impossible to determine the user corresponding to the lead data, when the relevant database stores the lead data, it can store this lead data corresponding to the user identifier of the user. Therefore, when obtaining the lead data, the processing device can also obtain the user identifier corresponding to this lead data. In order to be able to accurately update the user lead information in the key-value pair data table, after the processing device determines the pending user lead information, when determining the pending user status corresponding to the lead information, it can determine whether the corresponding target user lead information matches this pending user lead information based on the user identifier corresponding to this lead data. If they match, it means that this target user lead information still does not need to be updated, that is, this pending user status is the status of not needing to be updated; if they do not match, it means that this target user lead information needs to be updated, that is, this pending user status is the status of needing to be updated.

[0102] For example, when the lead data is the number of employees hired by a user, the processing device can determine whether the current number of employees corresponding to the user reaches the quantity standard based on the lead data. Subsequently, the processing device can determine the compliance status of the number of employees corresponding to the user identifier in the target user lead information according to the user identifier of the user, and match it with the compliance status determined based on the lead data.

[0103] If they match, it indicates that the target user lead information still has a certain degree of accuracy and can be not updated; if they do not match, it indicates that the target user lead information has become invalid and does not conform to the current lead data. At this time, in order to improve the effectiveness of the key-value pair data table, the processing device can update the key-value pair data table according to the user identifier corresponding to the lead data and the pending user lead information. The processing device can determine the user lead information corresponding to the user identifier in the key-value pair data table through the user identifier, and update the part corresponding to the pending user lead information in the user lead information to the pending user lead information. For example, when the pending user lead information is "the number of employees hired reaches the requirement", and the corresponding target user lead information is "the number of employees hired does not reach the requirement", the processing device can determine the user lead information corresponding to the user identifier in the key-value pair data table according to the user identifier, and update "the number of employees hired does not reach the requirement" in the user lead information to "the number of employees hired reaches the requirement".

[0104] As Figure 8 shown, Figure 8 FIG. is a schematic diagram of updating based on a key-value pair data table provided by an embodiment of the present application. In this schematic diagram, the processing device can also obtain the target user lead information in the key-value pair data table during a preset period through a timing queue. The preset period can be three months. The processing device can obtain the target user lead information within three months through the timing queue and obtain the corresponding lead data from the relevant database background, and determine whether the pending user lead information determined based on the lead data matches the target user lead information. If they do not match, the user lead information in the key-value pair data table can be updated.

[0105] To introduce the technical solution of the present application more vividly, next, a user lead query method provided by an embodiment of the present application will be introduced in combination with an actual application scenario.

[0106] See Figure 9 , Figure 9 FIG. is a schematic diagram of a user lead query method in an actual application scenario provided by an embodiment of the present application. In this actual application scenario, the processing device can be a server including a key-value pair data table, and the query initiator can be a service provider that has provided services to some users. After providing services, the service provider can pass through Figure 9The interface shown queries for some specific users to apply for subsidy amounts for services.

[0107] As shown in the figure, the service provider can select filtering conditions such as the service status of the required users, the follow-up personnel, the enterprise certification status, customer compliance, and whether to apply for rewards in the filtering condition selection interface. The specific filtering conditions are shown in the following table:

[0108]

[0109] After determining the filtering conditions, the service provider can click the OK button in the lower right corner of the interface to initiate a user lead query request. The server obtains this user lead query request and then matches it in the key-value pair data table storing user lead information. As Figure 10 shown, since the query result display interface can display at most 4 query results at a time, therefore, according to the matching results, the server can first determine 4 target key-value pair options from the key-value pair data table, and generate query results based on the user identifiers and user lead information in these 4 target key-value pair options and display them to the service provider.

[0110] In this result display interface, the service provider can also click on each user label to view the specific information of the user. As Figure 10 shown, the service provider can click on the label of "G Education Institution" to view information such as the service allocation time, industry type, and location area of this user. Among them, when the service provider's permissions are different, the information that can be viewed may also be different. For example, when the service provider is a service manager, the completion status of the service follow-up personnel can be viewed in this interface; when the service provider is a service follow-up personnel, the user status, whether the user can apply for a reported subsidy, etc. can be known in this interface, and corresponding follow-up processing can be carried out according to different user statuses.

[0111] Based on the user lead query method provided in the above embodiment, the embodiment of the present application also provides a user lead query device. Refer to Figure 11 , Figure 11 which is a structural block diagram of a user lead query device 1100 provided by the embodiment of the present application. The device 1100 includes a first acquisition unit 1101, a matching unit 1102, a filtering unit 1103, a first determination unit 1104, a fourth acquisition unit 1105, a second determination unit 1106, and a third determination unit 1107:

[0112] The first acquisition unit 1101 is used to acquire a user lead query request including multiple filtering conditions;

[0113] A matching unit 1102, configured to match the user lead information set in the value field of the key-value pair data table according to the multiple screening conditions, where the key-value pair data table stores user identifiers through the key fields of the key-value pair entries, and the value field of the key-value pair entry is used to store the user lead information corresponding to the user identifier;

[0114] A screening unit 1103, configured to screen out target key-value pair entries corresponding to the multiple screening conditions from the key-value pair entries included in the key-value pair data table according to the matching result;

[0115] A first determination unit 1104, configured to determine a query result corresponding to the user lead query request according to the target key-value pair entry;

[0116] A fourth acquisition unit 1105, configured to acquire lead data to be updated through a timing queue, where the lead data is used to determine the user lead information;

[0117] A second determination unit 1106, configured to determine a corresponding pending user status according to the lead data;

[0118] A third determination unit 1107, configured to determine whether to update the key-value pair data table according to the user identifier corresponding to the lead data and the pending user status.

[0119] In a possible implementation manner, the screening unit 1103 is specifically configured to:

[0120] Screen out a target number of the target key-value pair entries from the key-value pair entries included in the key-value pair data table according to the matching result, where the target number is determined according to the display number of the query result display page.

[0121] In a possible implementation manner, the apparatus 1100 further includes a second acquisition unit and an execution unit:

[0122] The second acquisition unit is configured to acquire a paging operation for the query result display page;

[0123] The execution unit is configured to re-execute the step of matching the user status set in the value field of the key-value pair data table according to the multiple screening conditions according to the paging operation.

[0124] In a possible implementation manner, the user lead information includes a user status, and the apparatus 1100 further includes a third acquisition unit and an update unit:

[0125] The third acquisition unit is configured to acquire a status update request for requesting to change the user status;

[0126] An update unit, configured to update the key-value pair data table according to the user identifier and the changed user status carried in the status update request.

[0127] In a possible implementation, the third acquisition unit is specifically configured to:

[0128] Acquire a user authentication request received in the user authentication process, where the user authentication request is used to request a change in the user's authentication status;

[0129] Use the user authentication request as the status update request.

[0130] In a possible implementation, the apparatus 1100 further includes a fifth acquisition unit:

[0131] The fifth acquisition unit is configured to acquire target user lead information within a preset time period in the key-value pair data table;

[0132] The fourth acquisition unit 1105 is specifically configured to:

[0133] Acquire lead data corresponding to the target user lead information through a timing queue;

[0134] The third determination unit 1107 is specifically configured to determine whether the corresponding target user lead information and the pending user lead information match according to the user identifier corresponding to the lead data;

[0135] If they do not match, update the key-value pair data table according to the user identifier corresponding to the lead data and the pending user lead information.

[0136] The embodiments of the present application further provide a computer device, which will be introduced below with reference to the accompanying drawings. Please refer to Figure 12 As shown, the embodiments of the present application provide a device, and the device may also be a terminal device. The terminal device may be any intelligent terminal including a mobile phone, a tablet computer, a personal digital assistant (Personal Digital Assistant, abbreviated as PDA), a point of sales (Point of Sales, abbreviated as POS), an in-vehicle computer, etc. Taking the terminal device as a mobile phone as an example:

[0137] Figure 12 Shown is a block diagram of a part of the structure of a mobile phone related to the terminal device provided by the embodiments of the present application. Refer to Figure 12, the mobile phone includes components such as a Radio Frequency (RF) circuit 1210, a memory 1220, an input unit 1230, a display unit 1240, sensors 1250, an audio circuit 1260, a wireless fidelity (WiFi) module 1270, a processor 1280, and a power supply 1290. Those skilled in the art can understand that Figure 12 the mobile phone structure shown in

[0138] does not limit the mobile phone, and it may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements. Figure 12 The following specifically introduces each component of the mobile phone:

[0139] The RF circuit 1210 can be used for receiving and sending signals during information reception or a call. Specifically, after receiving the downlink information from the base station, it is given to the processor 1280 for processing; in addition, the designed uplink data is sent to the base station. Generally, the RF circuit 1210 includes but is not limited to antennas, at least one amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, etc. In addition, the RF circuit 1210 can also communicate with the network and other devices through wireless communication. The above wireless communication can use any communication standard or protocol, including but not limited to the Global System of Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Messaging Service (SMS), etc.

[0140] The memory 1220 can be used to store software programs and modules. The processor 1280 executes various functional applications and data processing of the mobile phone by running the software programs and modules stored in the memory 1220. The memory 1220 mainly includes a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for at least one function (such as a sound playback function, an image playback function, etc.); the data storage area can store data created according to the use of the mobile phone (such as audio data, phone book, etc.). In addition, the memory 1220 may include a high-speed random access memory and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0141] The input unit 1230 can be used to receive input digital or character information and generate key signal inputs related to the user settings and function controls of the mobile phone. Specifically, the input unit 1230 may include a touch panel 1231 and other input devices 1232. The touch panel 1231, also known as a touch screen, can collect touch operations of the user on or near it (such as operations of the user using a finger, a stylus, or any suitable object or accessory on or near the touch panel 1231), and drive corresponding connection devices according to a pre-set program. Optionally, the touch panel 1231 may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the touch orientation of the user, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it to the processor 1280, and can receive and execute commands sent by the processor 1280. In addition, various types such as resistive, capacitive, infrared, and surface acoustic wave can be used to implement the touch panel 1231. In addition to the touch panel 1231, the input unit 1230 may further include other input devices 1232. Specifically, the other input devices 1232 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, power on / off keys, etc.), a trackball, a mouse, a joystick, etc.

[0142] The display unit 1240 can be used to display information input by the user or information provided to the user, as well as various menus of the mobile phone. The display unit 1240 may include a display panel 1241. Optionally, the display panel 1241 can be configured in the form of, for example, a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc. Further, the touch panel 1231 can cover the display panel 1241. When the touch panel 1231 detects a touch operation on or near it, it is transmitted to the processor 1280 to determine the type of touch event. Subsequently, the processor 1280 provides a corresponding visual output on the display panel 1241 according to the type of touch event. Although in Figure 12 , the touch panel 1231 and the display panel 1241 are implemented as two independent components to realize the input and input functions of the mobile phone, but in some embodiments, the touch panel 1231 and the display panel 1241 can be integrated to realize the input and output functions of the mobile phone.

[0143] The mobile phone may further include at least one sensor 1250, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor. Among them, the ambient light sensor can adjust the brightness of the display panel 1241 according to the brightness of the ambient light, and the proximity sensor can turn off the display panel 1241 and / or the backlight when the mobile phone is moved to the ear. As a kind of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary, and can be used for applications that identify the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors that the mobile phone can also be configured with, such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be elaborated here.

[0144] The audio circuit 1260, the speaker 1261, and the microphone 1262 can provide an audio interface between the user and the mobile phone. The audio circuit 1260 can transmit the electrical signal converted from the received audio data to the speaker 1261, and the speaker 1261 converts it into a sound signal for output; on the other hand, the microphone 1262 converts the collected sound signal into an electrical signal, which is received by the audio circuit 1260 and then converted into audio data. After the audio data is output to the processor 1280 for processing, it is sent through the RF circuit 1210 to, for example, another mobile phone, or the audio data is output to the memory 1220 for further processing.

[0145] WiFi belongs to short - range wireless transmission technology. The mobile phone can help users send and receive emails, browse the web, and access streaming media through the WiFi module 1270. It provides users with wireless broadband Internet access. Although Figure 12 the WiFi module 1270 is shown, it can be understood that it does not belong to the essential components of the mobile phone and can be omitted entirely within the scope of not changing the essence of the invention as needed.

[0146] The processor 1280 is the control center of the mobile phone. It connects various parts of the entire mobile phone using various interfaces and circuits. By running or executing software programs and / or modules stored in the memory 1220, and by calling the data stored in the memory 1220, it performs various functions of the mobile phone and processes data, thereby monitoring the mobile phone as a whole. Optionally, the processor 1280 may include one or more processing units; preferably, the processor 1280 may integrate an application processor and a modem processor. Among them, the application processor mainly processes the operating system, user interface, and application programs, etc., and the modem processor mainly processes wireless communication. It can be understood that the above - mentioned modem processor may not be integrated into the processor 1280.

[0147] The mobile phone also includes a power source 1290 (such as a battery) that supplies power to each component. Preferably, the power source can be logically connected to the processor 1280 through a power management system, so as to realize functions such as management of charging, discharging, and power consumption management through the power management system.

[0148] Although not shown, the mobile phone may also include a camera, a Bluetooth module, etc., which will not be elaborated here.

[0149] In this embodiment, the processor 1280 included in the terminal device further has the following functions:

[0150] Obtain a user lead query request including multiple screening conditions;

[0151] Match the user lead information set in the value field of the key - value pair data table according to the multiple screening conditions. The key - value pair data table stores user identifiers through the key fields of the key - value pair entries, and the value fields of the key - value pair entries are used to store the user lead information corresponding to the user identifiers;

[0152] Through the matching result, screen out the target key - value pair entries corresponding to the multiple screening conditions from the key - value pair entries included in the key - value pair data table;

[0153] Determine the query result corresponding to the user lead query request according to the target key - value pair entries.

[0154] This application embodiment also provides a server. Please refer to Figure 13 as shown.Figure 13 This is the structural diagram of server 1300 provided by an embodiment of the present application. Server 1300 may vary significantly due to different configurations or performances, and may include one or more central processing units (CPUs) 1322 (for example, one or more processors) and a memory 1332, and one or more storage media 1330 (for example, one or more mass storage devices) for storing application programs 1342 or data 1344. Among them, the memory 1332 and the storage media 1330 may be transient storage or persistent storage. The programs stored in the storage media 1330 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the server. Further, the central processing unit 1322 may be configured to communicate with the storage media 1330 and execute a series of instruction operations in the storage media 1330 on the server 1300.

[0155] Server 1300 may further include one or more power supplies 1326, one or more wired or wireless network interfaces 1350, one or more input / output interfaces 1358, and / or one or more operating systems 1341, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, and so on.

[0156] In the above embodiments, the steps executed by the server may be based on Figure 13 the server structure shown.

[0157] An embodiment of the present application further provides a computer-readable storage medium for storing a computer program, and the computer program is used to execute any one of the user clue query methods described in the foregoing embodiments.

[0158] Those of ordinary skill in the art can understand that all or part of the steps to implement the above method embodiments can be completed by hardware related to program instructions. The foregoing program may be stored in a computer-readable storage medium, and when the program is executed, it executes the steps including the above method embodiments; and the foregoing storage medium may be at least one of the following media: read-only memory (abbreviation: ROM), RAM, magnetic disk, or optical disc, etc., which can store program codes.

[0159] It should be noted that the embodiments in this specification are all described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other, and the key point of each embodiment is to illustrate the differences from other embodiments. In particular, for the embodiments of the device and system, since they are basically similar to the method embodiments, the description is relatively simple, and reference can be made to the relevant parts of the method embodiments for the relevant content. The device and system embodiments described above are only illustrative. 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 to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement it without creative efforts.

[0160] As described above, this is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed by the present application should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A user lead query method, characterized in that, The method includes: Obtaining a user lead query request including multiple filtering conditions; Matching the user lead information set in the value field of the key-value pair data table according to the multiple filtering conditions, where the key-value pair data table stores user identifiers through the key fields of the key-value pair entries, and the value field of the key-value pair entry is used to store the user lead information corresponding to the user identifier; Filtering out target key-value pair entries corresponding to the multiple filtering conditions from the key-value pair entries included in the key-value pair data table through the matching result; Determining a query result corresponding to the user lead query request according to the target key-value pair entries; Among them, the key-value pair data table is updated in the following manner: Obtaining lead data to be updated through a timing queue, where the lead data is used to determine the user lead information; Determining a corresponding pending user status according to the lead data; Determining whether to update the key-value pair data table according to the user identifier corresponding to the lead data and the pending user status; The user lead information includes a user status, and the method further includes: Obtaining a user authentication request received in the user authentication process, where the user authentication request is used to request a change in the user's authentication status; Taking the user authentication request as the status update request; Updating the key-value pair data table according to the user identifier carried in the status update request and the changed user status.

2. The method according to claim 1, wherein The filtering out target key-value pair entries corresponding to the multiple filtering conditions from the key-value pair entries included in the key-value pair data table through the matching result includes: Filtering out a target number of the target key-value pair entries from the key-value pair entries included in the key-value pair data table through the matching result, where the target number is determined according to the display number of the query result display page.

3. The method according to claim 2, wherein The method further includes: Obtaining a paging operation for the query result display page; According to the paging operation, re-executing the step of matching the user status set in the value field of the key-value pair data table according to the multiple filtering conditions.

4. The method according to claim 1, wherein The method further includes: Obtaining target user lead information within a preset time period in the key-value pair data table; The obtaining lead data to be updated through a timing queue includes: Obtaining lead data corresponding to the target user lead information through a timing queue; The determining whether to update the key-value pair data table according to the user identifier corresponding to the lead data and the pending user status includes: Determining whether the corresponding target user lead information and the pending user lead information match according to the user identifier corresponding to the lead data; If they do not match, updating the key-value pair data table according to the user identifier corresponding to the lead data and the pending user lead information.

5. A user lead query device, characterized in that, The device includes a first obtaining unit, a matching unit, a filtering unit, a first determining unit, a third obtaining unit, a fourth obtaining unit, a second determining unit, a third determining unit, and an updating unit: The first obtaining unit is used to obtain a user lead query request including multiple filtering conditions; The matching unit is configured to match the user lead information set in the value field of the key-value pair data table according to the multiple screening conditions. The key-value pair data table stores user identifiers through the key fields of the key-value pair entries, and the value field of the key-value pair entry is used to store the user lead information corresponding to the user identifier; The screening unit is configured to screen out target key-value pair entries corresponding to the multiple screening conditions from the key-value pair entries included in the key-value pair data table based on the matching result; The first determination unit is configured to determine a query result corresponding to the user lead query request according to the target key-value pair entries; The fourth acquisition unit acquires lead data to be updated through a timing queue, and the lead data is used to determine the user lead information; The second determination unit is configured to determine a corresponding pending user status according to the lead data; The third determination unit is configured to determine whether to update the key-value pair data table according to the user identifier corresponding to the lead data and the pending user status; The user lead information includes a user status. The third acquisition unit is configured to acquire a user authentication request received in the user authentication process, and the user authentication request is used to request to change the authentication status of the user; Use the user authentication request as the status update request; The update unit is configured to update the key-value pair data table according to the user identifier carried in the status update request and the changed user status.

6. The device according to claim 5, wherein Specifically, the screening unit is configured to: Screen out a target number of the target key-value pair entries from the key-value pair entries included in the key-value pair data table through the matching result, and the target number is determined according to the display number of the query result display page.

7. The device according to claim 6, characterized in that, The device further includes a second acquisition unit and an execution unit: The second acquisition unit is configured to acquire a paging operation for the query result display page; The execution unit is configured to re-execute the step of matching the user status set in the value field of the key-value pair data table according to the multiple screening conditions according to the paging operation.

8. The device according to claim 5, characterized in that, The device further includes a fifth acquisition unit: The fifth acquisition unit is configured to acquire target user lead information within a preset time period in the key-value pair data table; Specifically, the fourth acquisition unit is configured to: Acquire lead data corresponding to the target user lead information through a timing queue; Specifically, the third determination unit is configured to: Determine whether the corresponding target user lead information and the pending user lead information match according to the user identifier corresponding to the lead data; If they do not match, update the key-value pair data table according to the user identifier corresponding to the lead data and the pending user lead information.

9. A computer device, characterized in that, The device includes a processor and a memory: The memory is used to store program code and transmit the program code to the processor; The processor is configured to execute the user lead query method according to any one of claims 1-4 according to the instructions in the program code.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program, and the computer program is used to execute the user clue query method according to any one of claims 1-4.

Images