Method, apparatus and device for entity information query and storage medium

Abstract

This application discloses a method, apparatus, device, and storage medium for entity information querying, belonging to the field of information querying. The method includes: receiving a first query request for target parameters corresponding to a target entity sent by a first terminal; when it is determined that valid parameter information for the target entity's target parameters is not stored locally, obtaining the target entity's communication information; querying the parameter information of the target entity's target parameters based on the communication information; storing the parameter information of the target parameters; and feeding back the parameter information of the target parameters to the first terminal. Using this application, the problem of users being unable to obtain valid information when querying entity information that has not been entered or has not been updated in a timely manner can be solved.

Description

Technical Field

[0001] This application relates to the field of information retrieval, and in particular to a method, apparatus, device, and storage medium for retrieving entity information. Background Technology

[0002] Online service platforms offer users services such as merchant information lookup, order management, news recommendations, and online booking. Among these, merchant information lookup is one of the most frequently used services. Common merchant information includes the merchant's address, phone number, menu, and queue length, etc.

[0003] Currently, the merchant information provided by online service platforms is generally entered and updated by the merchants themselves on the platform.

[0004] However, some merchants may not have entered or updated their information in a timely manner, so users cannot obtain valid information when they search for this information. Summary of the Invention

[0005] This application provides a method, apparatus, device, and storage medium for querying entity information, which can solve the problem that users cannot obtain valid information when querying entity information that has not been entered or has not been updated in a timely manner.

[0006] Firstly, a method for querying entity information is provided, the method comprising: receiving a first query request for target parameters of a corresponding target entity sent by a first terminal; when it is determined that no valid parameter information of the target parameters of the target entity is stored locally, obtaining communication information of the target entity; querying the parameter information of the target parameters of the target entity based on the communication information; storing the parameter information of the target parameters, and feeding back the parameter information of the target parameters to the first terminal.

[0007] In one possible implementation, querying the parameter information of the target parameter of the target entity based on the communication information includes: sending a second query request corresponding to the target parameter of the target entity to a second terminal corresponding to the target entity based on the communication information; and receiving the parameter information of the target parameter of the target entity sent by the second terminal.

[0008] In one possible implementation, querying the parameter information of the target parameter of the target entity based on the communication information includes: initiating a voice call to the target entity based on the communication information to query the parameter information of the target parameter of the target entity; and determining the parameter information of the target parameter of the target entity based on the voice data received during the voice call.

[0009] In one possible implementation, after storing the parameter information of the target parameter, the method further includes: adding the parameter information of the target parameter to the entity display page of the target entity.

[0010] In one possible implementation, after storing the parameter information of the target parameter, the method further includes: adding the acquisition time point corresponding to the parameter information of the target parameter to the entity display page of the target entity.

[0011] In one possible implementation, determining that the target parameters of the target entity are not stored locally includes: determining that the target parameters of the target entity are not stored locally, or that the storage duration of the target parameters of the target entity stored locally is greater than a target duration threshold.

[0012] In one possible implementation, the method further includes: determining the target duration threshold corresponding to the target parameter based on the correspondence between the parameter and the duration threshold.

[0013] In one possible implementation, the method further includes: determining the number of query requests corresponding to each non-mandatory parameter of the target entity within a target historical time period, wherein the non-mandatory parameters of the target entity are parameters other than the preset mandatory parameters in the entity display page corresponding to the target entity; determining, among the various non-mandatory parameters of the target entity, the parameters whose corresponding query request counts satisfy preset conditions, and setting them as additional parameters of the entity display page corresponding to the target entity; and adding parameter information of the additional parameters of the target entity to the entity display page corresponding to the target entity.

[0014] Secondly, an entity information query apparatus is provided, the apparatus comprising: a receiving module, configured to receive a first query request for target parameters of a corresponding target entity sent by a first terminal; an acquiring module, configured to acquire communication information of the target entity when it is determined that no valid parameter information of the target parameter of the target entity is stored locally; a querying module, configured to query the parameter information of the target parameter of the target entity based on the communication information; and a storage module, configured to store the parameter information of the target parameter and feed back the parameter information of the target parameter to the first terminal.

[0015] In one possible implementation, the query module is configured to: send a second query request corresponding to the target parameter of the target entity to a second terminal corresponding to the target entity based on the communication information; and receive parameter information of the target parameter of the target entity sent by the second terminal.

[0016] In one possible implementation, the query module is configured to: initiate a voice call to the target entity based on the communication information to query parameter information of the target entity's target parameters; and determine the parameter information of the target entity's target parameters based on voice data received during the voice call.

[0017] In one possible implementation, the storage module is further configured to: add parameter information of the target parameter to the entity display page of the target entity.

[0018] In one possible implementation, the storage module is further configured to: add the acquisition time point corresponding to the parameter information of the target parameter to the entity display page of the target entity.

[0019] In one possible implementation, the acquisition module is configured to: determine that parameter information of the target parameter of the target entity is not stored locally, or that the storage duration of the parameter information of the target parameter of the target entity stored locally is greater than a target duration threshold.

[0020] In one possible implementation, the acquisition module is further configured to: determine the target duration threshold corresponding to the target parameter based on the correspondence between the parameter and the duration threshold.

[0021] In one possible implementation, the storage module is further configured to: determine the number of query requests corresponding to each non-mandatory parameter of the target entity within the target historical time period, wherein the non-mandatory parameters of the target entity are parameters other than the preset mandatory parameters in the entity display page corresponding to the target entity; among the various non-mandatory parameters of the target entity, determine the parameters whose corresponding query request counts satisfy preset conditions, and set them as additional parameters of the entity display page corresponding to the target entity; and add parameter information of the additional parameters of the target entity to the entity display page corresponding to the target entity.

[0022] Thirdly, a computer device is provided, the computer device including a processor and a memory, the memory for storing computer instructions, and the processor for executing the computer instructions stored in the memory to cause the computer device to perform the method of the first aspect and its possible implementations.

[0023] Fourthly, a computer-readable storage medium is provided, which stores computer program code, such that when the computer program code is executed by a computer device, the computer device performs the method of the first aspect and its possible implementations.

[0024] Fifthly, a computer program product is provided, comprising computer program code, wherein when the computer program code is executed by a computer device, the computer device executes the method of the first aspect and its possible implementations.

[0025] In this embodiment, after receiving a query request for target parameters of a target entity from a terminal (which may be a user's terminal), the server, upon determining that it does not have valid parameter information for the target entity stored locally, obtains the target entity's communication information. Based on this communication information, it then queries the target entity's target parameter information, stores the target parameter information, and sends the target parameter information back to the terminal. This allows the server to proactively query the target entity's target parameter information even when it does not have valid parameter information stored locally, and then send this information back to the terminal. Therefore, it solves the problem of users being unable to obtain valid information when querying entity information that has not been entered or has not been updated in a timely manner. Attached Figure Description

[0026] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0027] Figure 1 This is a schematic diagram of an online service platform interface provided in an embodiment of this application;

[0028] Figure 2 This is a schematic diagram of a query assistant page provided in an embodiment of this application;

[0029] Figure 3 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application;

[0030] Figure 4 This is a flowchart of a method for querying entity information provided in an embodiment of this application;

[0031] Figure 5 This is a schematic diagram illustrating a method for querying entity information provided in an embodiment of this application;

[0032] Figure 6 This is a schematic diagram of an entity display page provided in an embodiment of this application;

[0033] Figure 7 This is a schematic diagram of the structure of an entity information query device provided in an embodiment of this application;

[0034] Figure 8This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0035] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0036] When users want to search for information about a specific entity on an online service platform, there are several ways to do so. For example, they can enter the desired entity's information in the search bar, or use a search assistant. An entity can be one or more of a business, product, or service. Businesses can be located in various service sectors, such as catering, accommodation, transportation, and entertainment. The business information searched can include the business's opening hours, address, phone number, recommended items, menu, and set meals.

[0037] This application uses a user querying merchant information in the catering service sector as an example for illustration; other situations are similar and will not be described in detail here. Figure 1 As shown, users can click the query assistant control in the platform interface to enter the query assistant page, which can be viewed as follows: Figure 2 As shown. Users can input the merchant information they want to query via voice or text on the query assistant page. The query assistant can then provide the query results to the user through voice broadcast or text display.

[0038] Based on the above application scenarios, this application provides a method for querying entity information, which can be implemented by a computer device. The computer device can be a server. The server can be a single server or a server group consisting of multiple servers.

[0039] Figure 3 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. From the perspective of hardware composition, the structure of the computer device 30 can be as follows: Figure 3 As shown, it includes a processor 301, a memory 302, and a display unit 303.

[0040] The processor 301 can be a central processing unit (CPU) or a system on chip (SoC), etc. The processor 301 can be used to determine the valid parameter information of the target entity that is not stored locally, to obtain the communication information of the target entity, and to query the parameter information of the target entity's target parameters, etc.

[0041] The memory 302 may include various volatile or non-volatile memories, such as solid-state disks (SSDs) and dynamic random access memory (DRAM). The memory 302 can be used to store pre-stored data, intermediate data, and result data during the entity information query process, such as the target entity's target parameters, the target entity's communication information, and so on.

[0042] In addition to processor 301 and memory 302, computer device 30 may also include communication component 303.

[0043] The communication component 303 can be a wired network connector, a wireless fidelity (WiFi) module, a Bluetooth module, a cellular network communication module, etc. The communication component 303 can be used to transmit data with other devices, such as servers or terminals. For example, the computer device 30 can receive a first query request for target parameters corresponding to a target entity sent by the first terminal, and the computer device 30 can also send parameter information of the target parameters to the first terminal.

[0044] Figure 4 This is a flowchart of a method for querying entity information provided in an embodiment of this application. Figure 5 This is a diagram illustrating the method for querying entity information. See also... Figure 4 The method may include the following steps:

[0045] 401, Receive the first query request for the target parameters of the corresponding target entity sent by the first terminal.

[0046] The target entity can be a business, such as "XX Restaurant" or "XX Snack Shop". The target parameters can be various types of business information, such as address, phone number, number of people in line, and service fee.

[0047] Users can query business information in various ways, such as text queries and voice queries. For text queries, users can enter their query information in the question bar on the query assistant page, such as "Does XX restaurant charge a service fee?" The user terminal (in this scenario, the user terminal is the first terminal) can send a first query request to the server, which can include the text query information. For voice queries, users can speak their query information on the query assistant page, such as "How many people are in the queue at XX restaurant?" The user terminal can recognize the speech, obtain the corresponding text query information, and then send the first query request containing the text query information to the server. Optionally, the text result obtained from the speech recognition can be displayed on the user terminal's query assistant page to allow the user to judge whether the speech recognition result is correct.

[0048] Alternatively, users can query target entities that meet preset conditions, and then further query business information based on the query results. For example, a user might ask on the query assistant page, "Which hot pot restaurant is the closest to XX company?" The query assistant would then return "XX Hot Pot Restaurant." The user could then ask, "How many people are in line at this hot pot restaurant?" The user terminal can generate the query information "How many people are in line at XX Hot Pot Restaurant" based on the context of the user's query, i.e., the query result "XX Hot Pot Restaurant" above and the question "How many people are in line at this hot pot restaurant?" below, and then send a first query request carrying this query information to the server.

[0049] 402. When it is determined that there is no valid parameter information of the target entity's target parameters stored locally, the communication information of the target entity is obtained.

[0050] Among them, the valid parameter information is the parameter information that the storage duration of local storage is not greater than the target duration threshold.

[0051] In implementation, after receiving the first query request from the terminal, the server can obtain the text query information in the first query request, and then identify the target entity and target parameters contained in the text query information. For example, for the text query information "How many people are in the queue at XX restaurant?", the server can identify "XX restaurant" as the target entity and "number of people in the queue" as the target parameter. The identification of text query information can be performed using a machine learning model.

[0052] Then, the server can query the target entity's target parameter information stored locally. If the target entity is not found locally, a response message corresponding to the query result can be sent to the user terminal, such as "Sorry, this merchant does not exist." If the target entity is found locally, but the target parameter information is not stored, it can be determined that the target entity's target parameter information is not stored locally, and step 403 can be performed.

[0053] If the target entity is found in local storage, along with its target parameter information, the target duration threshold corresponding to the target parameter is determined based on the correspondence between the parameter and the duration threshold. A first correspondence table, as shown in Table 1, can be pre-defined and stored on the server. This table records the correspondence between parameters and duration thresholds. The server can then view this first correspondence table to determine the target duration threshold corresponding to the target parameter.

[0054] parameter Duration threshold Number of people in queue 30 minutes Business Hours 30 days address 30 days …… ……

[0055] Table 1

[0056] After determining the target duration threshold corresponding to the target parameter, the server can query the storage duration of the latest parameter information of the target entity's target parameters stored locally. When storing the parameter information of the target entity's target parameters, the server can also store the time point when the parameter information of the target parameter was obtained (referred to as the acquisition time point). The server can subtract the acquisition time point from the current time point to obtain the storage duration, which is the difference between the current time point and the acquisition time point when the parameter information of the target parameter was stored.

[0057] Subsequently, the server can compare the storage duration with the target duration threshold. If the storage duration of the target entity's target parameter information stored locally is greater than the target duration threshold, it can be determined that there is no valid target parameter information for the target entity stored locally, and step 403 can be performed. If the storage duration of the target entity's target parameter information stored locally is not greater than the target duration threshold, it can be determined that there is valid target parameter information for the target entity stored locally, and a response message corresponding to the target entity's target parameter can be generated and sent to the user terminal. For example, if the target entity is "XX Restaurant", the target parameter is "number of people in line", and the retrieved parameter information is "32 people", then the generated response message could be "XX Restaurant has 32 people in line waiting". Optionally, the generated response message can also include the time point when the parameter information was obtained, such as "XX Restaurant had 32 people in line waiting at 18:30".

[0058] If the server determines that it has the target entity stored locally, but does not have valid parameter information for the target entity's target parameters, it can retrieve the pre-stored communication information of the target entity. This communication information can be one or more of the target entity's IP address and telephone number.

[0059] 403, Based on communication information, query the parameter information of the target entity's target parameters.

[0060] In practice, after the server finds that the target entity is stored locally but the target parameters of the target entity are not stored, it can generate the query information corresponding to the target parameters of the target entity.

[0061] There are several ways to generate query information. For example, the text query information carried in the first query request can be used as the query information corresponding to the target parameter of the target entity. Alternatively, a second correspondence table stored locally can be queried to determine the query information corresponding to the target parameter, as shown in Table 2. The second correspondence table can record the correspondence between target parameters and query information. For example, if the target parameter is "number of people in the queue," the corresponding query information could be "How many people are in the queue at your shop?" Or, a third correspondence table stored locally can be queried to determine the preliminary query information corresponding to the target parameter, as shown in Table 3. The third correspondence table can record the correspondence between target parameters and preliminary query information. For example, if the target parameter is "address," the corresponding preliminary query information could be "Is your shop's address [ ]?" The server can query the latest parameter information of the target parameter and insert it into the "[ ]" in the preliminary query information to obtain the query information corresponding to the target parameter. In this way, after receiving the query information, the merchant's staff can give a positive or negative answer regarding the parameter information contained in the query information without needing to provide the specific parameter information, thereby reducing the merchant's workload and improving work efficiency.

[0062] parameter Query information Number of people in queue How many people are in line at your shop? Service fee Does your shop charge a service fee? …… ……

[0063] Table 2

[0064] parameter Preparing to query information address Is your shop's address [ ]? Business Hours Are your shop's opening hours [ ]? …… ……

[0065] Table 3

[0066] After determining the query information corresponding to the target parameters of the target entity, the server can perform a query based on the communication information. There are various ways to perform a query based on the communication information.

[0067] Method 1: Based on communication information, send a second query request corresponding to the target parameters of the target entity to the second terminal corresponding to the target entity, and receive the parameter information of the target parameters of the target entity sent by the second terminal.

[0068] When the communication information is the IP address of the target entity, the server can send a second query request to the second terminal (referred to as the merchant terminal) corresponding to the target entity. This second query request can carry query information corresponding to the target parameters of the target entity. The query information carried in the second query request can be text data or voice data, etc. For example, the second query request could carry the query information "How many people are in the queue at your store?" After receiving the second query request, the merchant's staff can click on the message bar corresponding to the second query request in the message list on the query assistant page to open a message pop-up window. The staff can then reply by entering text or voice in the message pop-up window.

[0069] Method 2: Based on communication information, initiate a voice call to the target entity to query the target entity's target parameters. Based on the voice data received during the voice call, determine the target entity's target parameters.

[0070] When the communication information is the target entity's IP address or phone number, the server can invoke an outbound call robot program to initiate a voice call to the target entity. After the voice call is connected, the outbound call robot can play a voice message inquiring about the target entity's information to the merchant's staff. For example, the outbound call robot can play a voice message asking, "Does your shop charge a service fee?" The merchant's staff can then respond to this message. Alternatively, to ensure that the merchant and the target entity in the voice call are consistent, the outbound call robot can first play the voice message corresponding to the target entity's query information, and then play the voice message corresponding to the target parameters of the target entity. For example, the outbound call robot can first play, "Are you the XX hot pot restaurant?", and after receiving an affirmative response, then play the voice message asking, "Does your shop charge a service fee?"

[0071] The server receives voice data from the merchant during a call and can determine the target entity's parameters based on this data. For example, if the outbound call robot plays the voice message "Does your store charge a service fee?" and the merchant replies with "Our store does not charge a service fee," the server can identify the merchant's "service fee" parameter as "none." Voice data recognition can be performed using machine learning models.

[0072] 404, store the target parameter information and feed it back to the user terminal.

[0073] In practice, there are several ways to provide feedback to the user terminal. For example, a reply message can be sent to the user terminal, which may carry parameter information of the target parameter; or, a voice call can be initiated to the user terminal to play voice containing parameter information of the target parameter, and so on.

[0074] Optionally, after storing the target parameter information, the target parameter information can also be added to the target entity's entity display page. For example... Figure 6 As shown, the entity display page of the target entity can display parameter information such as the target entity's address, phone number, and service plan. Optionally, while adding the parameter information of the target parameters to the entity display page, the corresponding acquisition time point of the target parameter information can also be added.

[0075] Based on this embodiment, the entity display page of the target entity can also be dynamically adjusted according to the merchant's reply message. For example, additional parameter information of the target entity can be added to the entity display page corresponding to the target entity.

[0076] The additional parameters are those parameters among the various optional parameters of the target entity whose corresponding query request count meets preset conditions. Optional parameters are those parameters other than the preset required parameters displayed on the entity's display page. Required parameters can be of various types, such as address and phone number. Optional parameters can also be of various types, such as recommended dishes and service fees. It should be noted that required and optional parameters are manually set and can be flexibly configured according to actual needs. For example, the number of people in the queue can be made a required parameter, etc.

[0077] In implementation, the entity display page corresponding to the target entity can display required parameters and optional parameters. Required parameters are those that will definitely be displayed on the entity display page, such as address and phone number; optional parameters are those that can be displayed on the entity display page other than the required parameters, such as recommended dishes and service fees.

[0078] Whenever the server receives a query request corresponding to a non-mandatory parameter, it can record the time point at which the query request was received. The server can query the number of time points at which query requests corresponding to non-mandatory parameters were received within a certain time period (i.e., the target historical time period), thereby determining the number of query requests corresponding to each non-mandatory parameter of the target entity within the target historical time period.

[0079] Then, the server can determine the parameters whose query request counts meet preset conditions from among the various optional parameters of the target entity, and set them as additional parameters on the entity display page corresponding to the target entity. The preset conditions can be varied; for example, it could be sorting the query request counts of the optional parameters from high to low and selecting parameters with query request counts reaching a preset ranking as additional parameters; or it could be selecting parameters with query request counts reaching a target threshold, and so on. Furthermore, the server can obtain the latest parameter information for the additional parameters and add it to the entity display page corresponding to the target entity.

[0080] Optionally, the query information corresponding to the additional parameters can be obtained and added together with the parameter information of the additional parameters to the entity display page corresponding to the target entity.

[0081] Optionally, the time point at which the parameter information of the additional parameters is received can be obtained and added together with the parameter information of the additional parameters to the entity display page corresponding to the target entity.

[0082] Optionally, additional query information and parameter information receiving time points can be added to the entity display page corresponding to the target entity.

[0083] Figure 7 This application provides an entity information query device, comprising: a receiving module 701 for receiving a first query request for target parameters of a corresponding target entity sent by a first terminal; an acquiring module 702 for acquiring communication information of the target entity when it is determined that no valid parameter information of the target parameter of the target entity is stored locally; a querying module 703 for querying the parameter information of the target entity's target parameter based on the communication information; and a storage module 704 for storing the parameter information of the target parameter and feeding back the parameter information of the target parameter to the first terminal.

[0084] In one possible implementation, the query module 703 is configured to: send a second query request corresponding to the target parameter of the target entity to a second terminal corresponding to the target entity based on the communication information; and receive parameter information of the target parameter of the target entity sent by the second terminal.

[0085] In one possible implementation, the query module 703 is configured to: initiate a voice call to the target entity based on the communication information to query parameter information of the target entity's target parameters; and determine the parameter information of the target entity's target parameters based on the voice data received during the voice call.

[0086] In one possible implementation, the storage module 704 is further configured to: add parameter information of the target parameter to the entity display page of the target entity.

[0087] In one possible implementation, the storage module 704 is further configured to: add the acquisition time point corresponding to the parameter information of the target parameter to the entity display page of the target entity.

[0088] In one possible implementation, the acquisition module 702 is used to: determine that the parameter information of the target parameter of the target entity is not stored locally, or that the storage duration of the parameter information of the target parameter of the target entity stored locally is greater than the target duration threshold.

[0089] In one possible implementation, the acquisition module 702 is further configured to: determine the target duration threshold corresponding to the target parameter based on the correspondence between the parameter and the duration threshold.

[0090] In one possible implementation, the storage module 704 is further configured to: determine the number of query requests corresponding to each non-mandatory parameter of the target entity within the target historical time period, wherein the non-mandatory parameters of the target entity are parameters other than the preset mandatory parameters in the entity display page corresponding to the target entity; among the various non-mandatory parameters of the target entity, determine the parameters whose corresponding query request counts satisfy preset conditions, and set them as additional parameters of the entity display page corresponding to the target entity; and add parameter information of the additional parameters of the target entity to the entity display page corresponding to the target entity.

[0091] Figure 8 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. The computer device 800 can vary significantly due to differences in configuration or performance. It may include one or more central processing units (CPUs) 801 and one or more memories 802. The memory 802 stores at least one instruction, which is loaded and executed by the processor 801 to implement the methods provided in the various method embodiments described above. Of course, the computer device may also have wired or wireless network interfaces, a keyboard, and input / output interfaces for input and output. The computer device may also include other components for implementing device functions, which will not be elaborated upon here.

[0092] In an exemplary embodiment, a computer-readable storage medium is also provided, such as a memory including instructions that can be executed by a processor in a terminal to complete the entity information query method described in the above embodiments. This computer-readable storage medium can be non-transitory. For example, the computer-readable storage medium can be ROM (read-only memory), RAM (random access memory), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0093] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0094] The above are merely optional embodiments of this application and are not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for querying entity information, characterized in that, The method includes: Receive the first query request for the target parameters of the corresponding target entity sent by the first terminal; When it is determined that there is no valid parameter information of the target entity's target parameters stored locally, the communication information of the target entity is obtained; Based on the communication information, query the parameter information of the target parameter of the target entity; The parameter information of the target parameter is stored, and the parameter information of the target parameter is fed back to the first terminal; the step of querying the parameter information of the target entity based on the communication information includes: Based on the communication information, a second query request corresponding to the target parameter of the target entity is sent to the second terminal corresponding to the target entity; Receiving parameter information of the target parameters of the target entity sent by the second terminal; the step of querying the parameter information of the target parameters of the target entity based on the communication information includes: Based on the communication information, a voice call is initiated to the target entity to query parameter information of the target entity's target parameters; Based on the voice data received during the voice call, the parameter information of the target parameter of the target entity is determined.

2. The method according to claim 1, characterized in that, After storing the parameter information of the target parameter, the method further includes: Add the parameter information of the target parameter to the entity display page of the target entity.

3. The method according to claim 2, characterized in that, After storing the parameter information of the target parameter, the method further includes: Add the acquisition time point corresponding to the parameter information of the target parameter to the entity display page of the target entity.

4. The method according to claim 1, characterized in that, The determination of valid parameter information for target parameters of the target entity that are not stored locally includes: It is determined that the parameter information of the target parameter of the target entity is not stored locally, or the storage duration of the parameter information of the target parameter of the target entity stored locally is greater than the target duration threshold.

5. The method according to claim 4, characterized in that, The method further includes: Based on the correspondence between parameters and duration thresholds, the target duration threshold corresponding to the target parameter is determined.

6. The method according to claim 1, characterized in that, The method further includes: Determine the number of query requests corresponding to each non-mandatory parameter of the target entity within the target historical time period, wherein the non-mandatory parameters of the target entity are parameters other than the preset mandatory parameters in the entity display page corresponding to the target entity; among the various non-mandatory parameters of the target entity, determine the parameters whose corresponding query request counts meet preset conditions, and set them as additional parameters of the entity display page corresponding to the target entity; Add parameter information of the additional parameters of the target entity to the entity display page corresponding to the target entity.

7. A device for querying entity information, characterized in that, The device includes: The receiving module is used to receive a first query request for the target parameters of the corresponding target entity sent by the first terminal; The acquisition module is used to acquire the communication information of the target entity when it is determined that there is no valid parameter information of the target entity's target parameters stored locally. A query module is used to query the parameter information of the target parameter of the target entity based on the communication information; a storage module is used to store the parameter information of the target parameter and feed back the parameter information of the target parameter to the first terminal. The step of querying the parameter information of the target entity's target parameters based on the communication information includes: Based on the communication information, a second query request corresponding to the target parameter of the target entity is sent to the second terminal corresponding to the target entity; Receiving parameter information of the target parameters of the target entity sent by the second terminal; the step of querying the parameter information of the target parameters of the target entity based on the communication information includes: Based on the communication information, a voice call is initiated to the target entity to query parameter information of the target entity's target parameters; Based on the voice data received during the voice call, the parameter information of the target parameter of the target entity is determined.

8. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing at least one instruction, which is loaded and executed by the processor to perform the operation of the entity information query method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The storage medium stores at least one instruction, which is loaded and executed by a processor to perform the operation of the entity information query method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, The computer program product includes at least one instruction, which is loaded and executed by a processor to perform the operation of the entity information query method as described in any one of claims 1 to 6.

Images