WO2024051555A1 - Data query method, electronic device, and system - Google Patents

Abstract

The present application provides a data query method, an electronic device, and a system. The method comprises that: a user equipment sends a query request to a server; the server sends first return data and first information to the user equipment according to the query request, wherein the first return data is a subset of query results, the query results comprise a plurality of pieces of query result data, and the first information is used for identifying part or all of the plurality of pieces of query result data; the user equipment sends a loading request to the server, wherein the loading request carries second information; and according to the loading request, the server sends the query result data identified by the second information to the user equipment. In this way, the server sends, to the user equipment, part of the query result data and the first information used for identifying part or all of the query result data, so that the server does not need to cache the query result data, the cache pressure and cost of the server are reduced, and the user equipment can obtain all of the query result data by means of the server.

Description

A data query method, electronic device and system

This application claims priority for a Chinese patent application submitted to the State Intellectual Property Office on September 9, 2022, with application number 202211104733.0 and application title "A data query method, electronic device and system", the entire content of which is incorporated by reference. in this application.

Technical field

The present application relates to the field of terminal technology, and in particular to a data query method, electronic equipment and system.

Background technique

With the rapid development of Internet technology and the widespread use of user equipment, people have gradually entered the era of electronic reading. People are increasingly using user equipment to obtain various information content from major application (application, APP) servers through the Internet. For example, the user can use the user device to obtain information about nearby restaurants, cinemas, hotels, etc. through the consumer APP server. The user can also use the user device to browse and obtain news, literary works and other information through the information aggregation APP server.

Take the user using the user device to obtain nearby restaurant information through the consumer APP server as an example. The APP server receives a query request for nearby restaurant information sent by the user through the user device, and the APP server obtains query result data including nearby restaurant information based on the query request. Set, and cache the query result data set so that the user device can obtain the query result data from the APP server.

However, if the query result data set has a large amount of data, the APP server cannot cache the query result data set or the cost of caching is too high, which affects the user device's ability to obtain the query result data from the APP server.

Contents of the invention

Embodiments of the present application provide a data query method, electronic device and system. The method includes the server sending a part of the data and the unique identifier corresponding to the remaining (or remaining) data from all the data queried by the user to the user device. After the user device receives a part of the data, it can send the unique identifier corresponding to the remaining (or remaining) data to the server in response to the user's further loading operation, so that the APP server can obtain the remaining (or remaining) data based on the identifier corresponding to the remaining (or remaining) data. ) data and sent to the user device. In this way, the server does not need to cache data, which reduces the caching pressure and cost of the server, and does not affect the user device's ability to obtain all queried data through the server.

In order to achieve the above objectives, the embodiments of the present application adopt the following technical solutions:

In the first aspect, a data query method is provided, which is applied to user equipment. The method includes: the user equipment sends a query request to a server. The query request includes the user's query information, and the query request is used to obtain query results corresponding to the query information. The user equipment receives the first return data and the first information sent by the server. The first return data is a subset of the query results. The query results include multiple pieces of query result data. The first information is used to identify a part or part of the multiple pieces of query result data. All query result data. The user equipment sends a loading request to the server, where the loading request carries second information, and the second information is a subset of the first information; the user equipment receives query result data identified by the second information sent by the server.

In an implementation manner of the first aspect, the first information includes a set of identifiers, and the set of identifiers includes unique identifiers corresponding to some or all of the plurality of query result data; or the first information includes a session There is a mapping relationship between identifiers, session identifiers and identifier sets; the identifier set includes unique identifiers corresponding to part or all of the query result data in multiple query result data.

In this method, after the user equipment sends a query request to the server, it receives the first return data sent by the server, that is, a part of the query result data, and the first information used to identify part or all of the query result data in the plurality of query result data. The user equipment can determine the second information based on the first information, and obtain the query result data identified by the second information by sending a load request carrying the second information to the server, that is, obtain more query result data. In this way, the server jointly sends part of the query result data and the first information used to identify part or all of the query result data to the user device. The server does not need to cache the query result data, which reduces the server's caching pressure and cost, and the user device can also pass The server obtains all query result data.

In an implementation manner of the first aspect, the query request further includes at least one of the following information: location information of the user equipment, device attributes of the user equipment, and user attributes. In this implementation, the server determines the location of the user device in the query request. The configuration information, device attributes of the user device, and user attributes can generate the user's personalized query result data to improve the user experience.

In the second aspect, a data query method is provided, applied to a server. The method includes: the server receives a query request sent by a user device, the query request includes the user's query information, and the query request is used to obtain query results corresponding to the query information. The server determines the first returned data and the first information according to the query request. The first returned data is a subset of the query results, and the query results include multiple query result data; the first information is used to identify part or All query result data. The server sends first return data and first information to the user equipment. The server receives a loading request sent by the user device, where the loading request carries second information, and the second information is a subset of the first information. The server determines the query result data of the second information identifier according to the loading request. The server sends the query result data of the second information identifier to the user equipment.

In an implementation manner of the second aspect, the first information includes a set of identifiers, and the set of identifiers includes unique identifiers corresponding to some or all of the plurality of query result data; or, the first information includes a session There is a mapping relationship between identifiers, session identifiers and identifier sets; the identifier set includes unique identifiers corresponding to part or all of the query result data in multiple query result data.

In this method, the server sends part of the query result data and the first information used to identify part or all of the query result data to the user device. The server does not need to cache the query result data, which reduces the cache pressure and cost of the server, and the user device also All query result data can be obtained through the server.

In an implementation manner of the second aspect, the query request also includes: location information of the user equipment, device attributes of the user equipment, and user attributes. The server determines the first return data and the first information according to the query request, including: the server determines user portrait data based on device attributes and/or user attributes, and the user portrait data is used to characterize the user's query characteristics. The server determines the query result identifier set based on the user portrait data, location information, and device attributes. The query result identifier set includes the unique identifier corresponding to each query result data. The server determines the first return data and the first information based on the query result identifier set. In this implementation, the server can generate the user's personalized query result data based on the location information of the user device, device attributes of the user device, and user attributes in the query request, so as to improve the user experience.

In an implementation manner of the second aspect, the device attributes include a user device identifier, and the user attributes include a user identifier; determining the user portrait data according to the device attributes and/or user attributes includes: the server determines the user portrait data according to the user device identifier and/or Or user identifier, obtain user portrait data through the user portrait database. Wherein, the user portrait database includes user portrait data that has a mapping relationship with the user device identifier and/or the user identifier. In this implementation, the server can obtain user portrait data based on the user portrait database to characterize the user's query characteristics. And further generate the user's personalized query result data based on the portrait data to improve the user experience.

In an implementable manner of the second aspect, determining the set of query result identifiers based on the user portrait data, location information, and device attributes includes: retrieving the query based on the user portrait data, location information, and device attributes in a database. A collection of result identifiers; the retrieval database includes unique identifiers corresponding to each query result data.

In a third aspect, an electronic device is provided, including: a memory, one or more processors; the memory is coupled to the processor; wherein, computer program code is stored in the memory, and the computer program code includes computer instructions. When the computer instructions are processed When the processor is executed, the electronic device is caused to perform the method described in any one of the first aspects, or the electronic device is caused to perform the method described in any one of the second aspects.

In a fourth aspect, a computer-readable storage medium is provided, including computer instructions. When the computer instructions are run on an electronic device, the electronic device causes the electronic device to execute any of the methods described in the first aspect, or causes the electronic device to execute the method. The method according to any one of the above second aspects.

In a fifth aspect, a computer program product is provided. When the computer program product is run on a computer, it causes the computer to perform any of the methods described in the first aspect, or causes the computer to perform any of the methods described in the second aspect. method described.

It can be understood that the beneficial effects that can be achieved by the above-mentioned electronic device of the third aspect, the computer-readable storage medium of the fourth aspect, and the computer program product of the fifth aspect can be referred to the first aspect and any possible design method thereof. The beneficial effects will not be repeated here.

Description of the drawings

Figure 1 is a schematic diagram of a query data application scenario illustrated in an embodiment of the present application;

Figure 2 is a schematic flow chart of a data query method according to an embodiment of the present application;

Figure 3 is a schematic diagram of a user equipment sending a query request according to an embodiment of the present application;

Figure 4 is a schematic diagram 1 of the APP server sending query result data according to the embodiment of the present application;

Figure 5 is a schematic diagram of a user equipment sending a next page data request according to an embodiment of the present application;

Figure 6 is a schematic diagram 2 of the APP server sending query result data according to the embodiment of the present application;

Figure 7 is a schematic diagram showing query result data according to an embodiment of the present application;

Figure 8 is a schematic diagram of the architecture of a data query system according to an embodiment of the present application;

Figure 9 is a schematic diagram of the hardware structure of an electronic device according to an embodiment of the present application;

Figure 10 is a software structure block diagram of an electronic device according to an embodiment of the present application;

Figure 11 is a schematic flow chart of a data query method according to an embodiment of the present application;

Figure 12 is a schematic diagram of a user equipment sending a first query request according to an embodiment of the present application;

Figure 13 is a schematic diagram of a recommendation interface according to an embodiment of the present application;

Figure 14 is a schematic diagram of the APP server sending the first return data set and the first information according to the embodiment of the present application;

Figure 15 is a schematic diagram of a user equipment sending a second query request according to an embodiment of the present application;

Figure 16 is a schematic diagram of the APP server sending the second return data set according to the embodiment of the present application;

Figure 17 is a schematic flow chart of another data query method according to an embodiment of the present application;

FIG. 18 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Among them, in the description of this application, unless otherwise stated, "/" means that the related objects are an "or" relationship. For example, A/B can mean A or B; "and/or" in this application "It is just an association relationship that describes related objects. It means that there can be three relationships. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. Among them, A , B can be singular or plural. Furthermore, in the description of this application, unless otherwise specified, "plurality" means two or more than two. "At least one of the following" or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items). For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c can be single or multiple.

In addition, in order to facilitate a clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as “first” and “second” are used to distinguish identical or similar items with basically the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the number and execution order, and words such as "first" and "second" do not limit the number and execution order. At the same time, in the embodiments of this application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "such as" in the embodiments of the present application is not to be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete manner that is easier to understand.

With the rapid development of Internet technology and the widespread use of user equipment, people have gradually entered the era of electronic reading. People are increasingly using user equipment to obtain various information content from major APPs through the Internet. For example, users browse information through information aggregation APPs, such as various news, literary works and other information. Users can also browse business information through consumer apps, such as obtaining information about nearby restaurants, movie theaters, hotels, etc.

When the user browses the information content displayed by the APP, because the APP displays a lot of information content and the size of the display interface of the user device is limited, the information content displayed to the user through the display interface is limited, and the APP's information content cannot be displayed in one display. All information content is displayed to the user. At this time, in order to improve the user experience and enable the user to browse more information content, the terminal device can respond to the user's browsing operation of the information content on an APP and display the information content to the user in the form of an information flow. Information flow can refer to a collection of information content arranged according to certain rules (for example, arranged from near to far, arranged from near to far by release time, etc.). Displaying information content to users in the form of information flow can refer to responding to users. The browsing operation displays the information content to the user in sequence according to the arrangement rules of the information content. For example: when the user browses the information content displayed by the APP, the user device can display the information content sequentially in response to the user's sliding operation (such as sliding the display interface of the user device upward). At this time, the information content of the APP follows the user's sliding operation. The operation is displayed in a flowing manner.

For example, when the collection of information content includes multiple pages of information content, the user device can display the information content of each page in page order in response to the user's sliding operation. Among them, the information content of each page can be displayed by the display interface of the user device. Maximum information content. For example, if the maximum information content that can be displayed on the display interface of the user device is 10 pieces of data information, then the information content of each page includes 10 pieces of data information. When the user finishes browsing the page of information displayed on the user device (10 pieces of data), the user device can be triggered to display the next page of information (10 pieces of data after the 10 pieces of data on the previous page) through a sliding operation. .

Figure 1 is a schematic diagram of a data query application scenario illustrated in an embodiment of the present application, in a scenario where a user uses a consumer APP to query food information near the user. As shown in Figure 1, the information of the query result data (food) is displayed through the user device, where the query result data can be sorted in order of distance from the user device from closest to farthest.

Specifically, the user device responds to the user's inquiry operation of nearby restaurants on the consumer APP and sends a query request to the APP server. The APP server generates a query result data set based on the query request and saves the query result data set to the APP server. In cache. Generally, the APP server can perform data query based on the location of the user device (taking longitude and latitude information as an example) according to the query request sent by the user device. Specifically, the APP server can use the longitude and latitude of the user device as the origin, continue to expand to the surrounding area, sort the distance to the origin from near to far, and filter out the query result data set that meets the user's query request. The APP server can cache the query result data set with longitude and latitude as the primary key, and support the user device to obtain the query result data.

Among them, the query result data set can be displayed to the user through the user device in the form of information flow. When the user's sliding operation on the user device triggers the user device to display the query result data of the next page, the user device can carry the number of pages that have been displayed. (such as page 3) obtains the query result data of the next page from the APP server. In this way, the coherence and logic of user browsing query result data can be ensured.

Specifically, FIG. 2 is a schematic flowchart of a data query method according to an embodiment of the present application. As shown in Figure 2, taking the user using a consumer APP to query nearby restaurants, and the user device displaying the query result data in pages, as an example, the data query method is implemented in the user device, and the method can be implemented through the following steps S101-S110 accomplish:

S101. The user device responds to the user's query operation and obtains identification information.

Illustratively, Figure 3 is a schematic diagram of a user device sending a query request according to an embodiment of the present application. As shown in Figure 3, the user enters "query nearby restaurants" in the search box of the APP. The user equipment responds to the query operation to obtain the identification information of the user equipment. The identification information can be used to identify the user device, and the APP server can cache data corresponding to the user device based on the identification information. Specifically, the identification information of the user equipment includes but is not limited to: the location information (latitude and longitude) of the user equipment, the unique identifier of the user equipment, or the APP user account.

S102. The user device sends a query request to the APP server.

In response to the query operation, the user device sends a query request to the APP server after obtaining the identification information. The query request includes: location information of the user equipment, identification information of the user equipment, and query conditions. The query conditions may be, for example: querying nearby restaurants, querying nearby cinemas, or querying nearby hotels.

S103. The APP server receives the query request, generates a query result data set according to the query request, and saves the query result data set in the cache. Specifically, the APP server generates a query result data set according to the query request, and saves it in the cache of the APP server with the identification information of the user device as the primary key.

S104. The APP server sends the query result data of the first page to the user device.

Figure 4 is a schematic diagram 1 of an APP server sending query result data according to an embodiment of the present application. As shown in Figure 4, the APP server sends the query result data of the first page to the user device, where the query result data of the first page The quantity is the maximum amount of data that can be displayed on one page of the display interface of the user device. When the APP server receives a request sent by the user device to obtain the query result data of other pages, it then sends the query result data of the corresponding page number to the user device. In this way, the user device can display the query result data in the form of information flow.

S105. The user device receives the query result data of the first page, and displays the query result data of the first page on the user device.

Specifically, as shown in Figure 4, the user device can display the received query result data on the first page through the display interface, which specifically includes: the information of each restaurant arranged in ascending order of distance from the user device, so that the user can intuitively Browse information about nearby restaurants.

S106. The user device receives the user's data request instruction, and the request instruction is used by the device-side APP to obtain the query result data of the next page.

Specifically, when the user finishes browsing the query result data on the first page (the query result data currently displayed on the user device), it is necessary to When continuing to browse the query result data on the next page. As shown in Figure 5, the user can issue a data request instruction on the user device by sliding down to display the interface. The user device responds to the data request instruction and obtains the query result data of the next page from the APP server.

S107. The user device responds to the data request instruction and sends a next page data request to the APP server. The next page data request includes the identification information of the user device and the page number.

Specifically, the next page data request is used by the user equipment to obtain the query result data of the next page relative to the page number obtained in step S105. Among them, the identification information and page number of the user device can be used to accurately find the query result data corresponding to the page number of the user device in the cache of the APP server.

S108. The APP server receives the next page data request and searches for the query result data of the next page from the cache according to the next page data request.

Specifically, the APP server searches the cache for the query result data set of the user device based on the identification information of the user device. Then, search the query result data corresponding to the page number from the query result data set of the user device according to the page number, that is, the query result data of the next page.

S109. The APP server sends the query result data of the next page to the user device.

S110. The user device receives the query result data of the next page. As shown in Figure 6, the user device displays the query result data of the next page through the display interface. In this way, through the above steps S101-S110, the location information query result data based on the user equipment can be displayed in the user equipment in an information flow manner (paging manner).

However, in the above step S103, the APP server generates query result data based on the location information of the user device as the query condition. In this way, complex personalized query scenarios cannot be satisfied, that is, it cannot combine the user's needs and other characteristics to generate the user's personalized query results and obtain the query result data that the user expects to see.

For example, in some practical application scenarios, in order to improve the user experience, the APP server can combine user needs (or user preferences) and other characteristics to generate query result data for the user. In this case, the query result data is specific to the user. Depending on the specific needs of an individual, it can be called personalized query result data for that user. For example, the APP server can generate personalized query result data for the user based on the location information of the user's device and the user's profile (such as user gender, age, preferences, query time, query scenario, etc.). Since the user portraits of different users are different, the query result data sets of each user at the same time and in the same location may be different. Take the user using a consumer APP to query nearby coupons as an example. The APP server combines user portraits (user preferences) at the same time and place to push nearby coffee coupon query result data to some users (users who like to drink coffee). , push the query result data of nearby fast food coupons to some users (users who like to eat fast food). In this way, the user's personalized query result data can be generated according to the needs of different users to improve the user experience.

It can be understood that the personalized query result data is an exemplary naming and does not limit the solutions shown in the embodiments of this application. In the solutions described in the embodiments of the present application below, the query result data is the user's personalized query result data as an example for description. This is explained in a unified manner and will not be described in detail later.

However, in order to generate the user's personalized query result data, the query conditions used by the APP server include not only the location information of the user device, but also the user portrait information. In this way, due to too many query conditions, the amount of personalized query result data obtained is large. Moreover, the personalized query result data generated by the APP server cannot be cached using a valid primary key. If the distributed caching method is adopted, the cost of caching on the APP server will be increased.

Moreover, even if the APP server caches the user's personalized query result data, after the user's query conditions change, for example, the time, scene, etc. in the user portrait information change, such as the user returns home from work, the APP server New personalized query result data will be generated. Therefore, the original personalized query result data cached by the APP server will have no use value and cannot be reused by other users. The original personalized query result data will occupy a large amount of storage resources of the APP server, causing a waste of storage resources of the APP server.

Therefore, in some application scenarios, such as generating personalized query result data, the amount of personalized query result data is large, and the APP server cannot implement data caching or the cost of implementing data caching is too high, thus affecting user equipment. Obtain query result data from the APP server. For example, after the APP server sends a part (the first page) of personalized query result data to the user device for the first time, because the APP server cannot cache the personalized query result data, the user device cannot obtain other parts of the personalized query result data. Figure 7 is a schematic diagram showing query result data according to an embodiment of the present application. As shown in Figure 7, since the APP server does not cache the personalized query result data, the user device can only display the 15 personalized query result data received for the first time, and the user device cannot obtain other parts of the personalized query result data.

In order to solve the problem that when the data set has a large amount of data, the server cannot implement data caching for the data set or the cost of implementing data caching is too high, thus affecting the user device to obtain the query result data from the server.

Embodiments of the present application provide a data query method: the user equipment sends a query request to the server. The query request includes the user's query information, and the query request can be used to obtain query results corresponding to the query information. The server determines the first returned data and the first information according to the query request. The first returned data is a subset of query results, and the query results include multiple query result data; the first information is used to identify part or all of the multiple query result data. The user equipment receives the first return data and the first information sent by the server. Further, in response to the user's further loading operation, the user equipment may send a loading request to the server, where the loading request carries the second information. Wherein, the second information is a subset of the first information. The server determines the query result data of the second information identifier according to the loading request; the server sends the query result data of the second information identifier to the user device. In this way, the server jointly sends part of the query result data and the first information used to identify part or all of the query result data to the user device. The server does not need to cache the query result data, which reduces the cache pressure and cost of the server, and the user device can use the first information to identify the query result data. One message obtains all query result data through the server.

It can be understood that this application does not limit the naming of the first return data, server, etc. For example, the first return data can also be described as the first return data set and other names, and the server can also be described as the APP server and other names. The method described in this application is described below as an example of the first returned data set and APP server. The data query solution provided by the embodiment of the present application will be described below with reference to the accompanying drawings of the description.

Referring to Figure 8, a schematic diagram of the architecture of a data query system provided by an embodiment of the present application is shown. As shown in Figure 8, the system includes: a user device and an APP server. A communication connection can be established between the user device and the APP server.

Among them, the user device is installed with at least one APP client (or APP for short) that can provide specified functions, or the user device can be installed/deployed with an entrance to the APP that accesses the specified functions (such as an entrance card, etc.). Optionally, the APP can be a consumer APP or other types of APP with data query function. The APP server corresponds to the APP in the user device. The APP server can refer to the server that provides services for the APP in the user device. It can provide the entrance service of cloud-side services for the APP in the user device. The entrance service includes but is not limited to access to the APP. Perform authentication, authentication, preprocessing, routing and orchestration services.

Optionally, as shown in Figure 8, in this embodiment of the present application, a user portrait service instance, a retrieval service instance and a metadata query service instance are also deployed in the data query system. User portrait service instances, retrieval service instances and metadata query service instances are programmatic services that provide certain specified functions. Optionally, user portrait service instances, retrieval service instances and metadata query service instances can be deployed in cloud virtual machines. User portrait service instances, retrieval service instances and metadata query service instances can also be deployed in physical servers or containers. Optionally, user portrait service instances, retrieval service instances and metadata query service instances can be deployed together with the APP server, together with other servers, or independently.

The embodiments of this application do not limit the names of user portrait service instances, retrieval service instances and metadata query service instances. For example, they can be replaced with names that have the same or similar functions. In the following, the user profiling service instance, retrieval service instance and metadata query service instance are referred to as user profiling service, retrieval service and metadata query service respectively.

Among them, the user portrait service can provide services for querying user portrait (user characteristics, preferences, etc.) data, for example, obtaining user portrait data through user device identifiers or user accounts. The retrieval service can search based on query conditions such as user portraits and location information, and obtain unique identifiers corresponding to result data that meet the query conditions. The metadata query service can query based on the unique identifier provided by the retrieval service to obtain the result data corresponding to the unique identifier.

Taking the system framework shown in Figure 8 as an example, the principle of the data query method provided by the embodiment of this application is: the user device sends a query request to the APP server, and the query request includes location information, device attributes and user attributes. The APP server receives the query request and queries the user portrait data through the user portrait service according to the query request (for example, at least one of device attributes and user attributes). The APP server obtains a query result set through the retrieval service based on the user portrait data and query request (such as location information and device attributes). The query result set includes a unique identifier corresponding to each query result data. The APP server obtains the corresponding query result data through the metadata query service based on a part of the unique identifier in the query result set. The APP server combines the complete data of the above part of the query result data and the remaining unique identifiers in the query result set to form a returned result set. The APP server sends the returned result set to the user device. If the user device wants to obtain the complete remaining query result data Data, a unique identifier can be sent to the APP server. The APP server obtains the corresponding query result data through the metadata query service based on the unique identifier, and sends it to the user device. In this way, the APP server sends the unique identifier of part of the query result data and the remaining query result data to the user device. The APP server does not need to cache the query result data, which reduces the caching pressure and cost of the APP server, and the user device can obtain it through the APP server. All query result data.

Among them, user devices with APP installed can include but are not limited to smartphones, netbooks, tablets, smart watches, smart bracelets, phone watches, smart cameras, handheld computers, personal computers (PC), personal digital assistants ( personal digital assistant (PDA), portable multimedia player (PMP), augmented reality (AR)/virtual reality (VR) equipment, television, projection equipment or human-computer interaction scenarios Somatosensory game consoles, etc. Alternatively, the user equipment may also be electronic equipment of other types or structures, which is not limited by this application.

FIG. 9 shows a schematic diagram of the hardware structure of the electronic device 100. For example, the electronic device 100 shown in FIG. 9 may be a user device or an APP server in the embodiment of the present application.

As shown in Figure 9, the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, and a battery 142 , Antenna 1, Antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone interface 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193 , display screen 194, and subscriber identification module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, and ambient light. Sensor 180L, bone conduction sensor 180M, etc.

It can be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the electronic device 100 . In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figures, or some components may be combined, some components may be separated, or some components may be arranged differently. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (GPU), and an image signal processor. (image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (NPU) wait. Among them, different processing units can be independent devices or integrated in one or more processors.

The controller may be the nerve center and command center of the electronic device 100 . The controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110 . If the processor 110 needs to use the instructions or data again, it can be called directly from the memory. Repeated access is avoided and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. Interfaces may include integrated circuit (inter-integrated circuit, I2C) interface, integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, pulse code modulation (pulse code modulation, PCM) interface, universal asynchronous receiver and transmitter (universal asynchronous receiver/transmitter (UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (SIM) interface, and /or universal serial bus (USB) interface, etc.

The USB interface 130 is an interface that complies with the USB standard specification, and may be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transmit data between the electronic device 100 and peripheral devices. It can also be used to connect headphones to play audio through them. This interface can also be used to connect other electronic devices, such as AR devices, etc.

It can be understood that the interface connection relationships between the modules illustrated in the embodiment of the present invention are only schematic illustrations and do not constitute a structural limitation of the electronic device 100 . In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 may be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example: Antenna 1 can be reused as a diversity antenna for a wireless LAN. In other embodiments, antennas may be used in conjunction with tuning switches.

The mobile communication module 150 can provide solutions for wireless communication including 2G/3G/4G/5G applied on the electronic device 100 . The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves through the antenna 1, perform filtering, amplification and other processing on the received electromagnetic waves, and transmit them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves through the antenna 1 for radiation. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be disposed in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be provided in the same device.

A modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor.

The wireless communication module 160 can provide applications on the electronic device 100 including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), Bluetooth (bluetooth, BT), and global navigation satellites. System (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

In the embodiment of this application, when the electronic device 100 is the user equipment in the previous embodiment, the user equipment can send a query request to the APP server through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, etc. The user equipment can also receive the query result data sent by the APP server through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, etc.

In the embodiment of the present application, when the electronic device 100 is the APP server in the previous embodiment, the APP server can receive the query request sent by the user equipment through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, etc. The APP server can also send query result data to the user equipment through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, etc.

In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), broadband Code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC , FM, and/or IR technology, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (quasi) -zenith satellite system (QZSS) and/or satellite based augmentation systems (SBAS).

In the embodiment of the present application, when the electronic device 100 is the user equipment in the previous embodiment, the user equipment can perform positioning through GPS, GLONASS, BDS, QZSS, SBAS, etc., and obtain the location information of the user equipment.

The electronic device 100 implements display functions through a GPU, a display screen 194, an application processor, and the like. The GPU is an image processing microprocessor and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, videos, etc. Display 194 includes a display panel. The display panel can use a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active matrix organic light emitting diode or an active matrix organic light emitting diode (active-matrix organic light emitting diode). emitting diode (AMOLED), flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, quantum dot light emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

In this embodiment of the present application, when the electronic device 100 is the user equipment in the previous embodiment, the display screen 194 of the user equipment can display the query result data sent by the APP server to facilitate the user to browse the query result data.

The electronic device 100 can implement the shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.

The ISP is used to process the data fed back by the camera 193. For example, when taking a photo, the shutter is opened, the light is transmitted to the camera sensor through the lens, the optical signal is converted into an electrical signal, and the camera sensor passes the electrical signal to the ISP for processing, and converts it into an image visible to the naked eye.

Camera 193 is used to capture still images or video. The object passes through the lens to produce an optical image that is projected onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to convert it into a digital image signal. ISP outputs digital image signals to DSP for processing. DSP converts digital image signals into standard RGB, YUV and other format image signals. In some embodiments, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. Such as saving music, videos, etc. files in external memory card.

Internal memory 121 may be used to store computer executable program code, which includes instructions. The processor 110 executes instructions stored in the internal memory 121 to execute various functional applications and data processing of the electronic device 100 . The internal memory 121 may include a program storage area and a data storage area. Among them, the stored program area can store an operating system, at least one application program required for a function (such as a sound playback function, an image playback function, etc.). The storage data area may store data created during use of the electronic device 100 (such as audio data, phone book, etc.). In addition, the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

In the embodiment of the present application, when the electronic device 100 is the user device in the previous embodiment, the query result data sent by the APP server can be saved in the internal memory 121 . Alternatively, saved in an external memory card linked through the external memory interface 120 .

The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. This embodiment of the present invention takes the Android system with a layered architecture as an example to illustrate the software structure of the electronic device 100 .

Figure 10 is a software structure block diagram of an electronic device according to an embodiment of the present application;

The layered architecture divides the software into several layers, and each layer has clear roles and division of labor. The layers communicate through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: application layer, application framework layer, Android runtime and system libraries, and kernel layer.

The application layer can include a series of application packages.

As shown in Figure 10, the application package may include consumption recommendation applications, life applications, shopping applications or functional applications, etc. Specifically, for example, camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message and other applications.

The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 10, the application framework layer can include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

A window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, and lock screen, take screenshots, etc.

Content providers are used to store and retrieve data and make this data accessible to applications. Said data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls, such as controls that display text, controls that display pictures, etc. A view system can be used to build applications. The display interface can be composed of one or more views. For example, a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions of the electronic device 100 . For example, call status management (including connected, hung up, etc.).

The resource manager provides various resources to applications, such as localized strings, icons, pictures, layout files, video files, etc.

The notification manager allows applications to display notification information in the status bar, which can be used to convey notification-type messages and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be notifications that appear in the status bar at the top of the system in the form of charts or scroll bar text, such as notifications for applications running in the background, or notifications that appear on the screen in the form of conversation windows. For example, text information is prompted in the status bar, a beep sounds, the electronic device vibrates, the indicator light flashes, etc.

Android Runtime includes core libraries and virtual machines. Android Runtime is responsible for the scheduling and management of the Android system.

The core library contains two parts: one is the functional functions that need to be called by the Java language, and the other is the core library of Android.

The application layer and application framework layer run in virtual machines. The virtual machine executes the java files of the application layer and application framework layer into binary files. The virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection and other functions.

System libraries can include multiple functional modules. For example: surface manager (surface manager), media libraries (Media Libraries), 3D graphics processing library (for example: OpenGL ES), 2D graphics engine (for example: SGL), query module, etc.

The surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, composition, and layer processing.

2D Graphics Engine is a drawing engine for 2D drawing.

The query module allows users to send query requests to the server and receive query result data sent by the server.

The kernel layer is the layer between hardware and software. The kernel layer at least includes a display driver, a camera driver, an audio driver, a sensor driver, etc. This embodiment of the present application does not impose any restrictions on this.

The data query method provided by the embodiment of the present application will be described below in conjunction with the data query system architecture shown in Figure 8 above. The following user equipment and APP server may specifically refer to the components shown in Figure 9 and the application framework layer shown in Figure 10. Figure 11 is a schematic flowchart of a data query method according to an embodiment of the present application. As shown in Figure 11, the method may include the following steps S201-S212.

S201. The user initiates a query operation to the user device.

In this embodiment of the present application, the user equipment can initiate a query operation to the user equipment through the APP. In one example, the APP can be installed on the user's device and displayed to the user in the form of an APP icon. Users can open the APP by clicking on the APP icon, and can initiate query operations through the APP.

For example, as shown in Figure 12, the user can click the APP icon on the user device to open the APP. The user successfully logs in to the APP by entering the username (or user ID of the APP) and password. Users enter query information through the query box of the APP, for example, to query nearby restaurants. Then click the query button to initiate the query operation.

In another example, the APP can be a service-oriented program, and the service-oriented program is, for example, an atomized service. It is understandable that the atomized service can be used without explicit installation and can be used after being installed by the system program framework in the background. The service may be, for example, a feature ability (FA). It should be understood that the atomization service can be composed of one or more deployment packages (harmonyos ability package, HAP) of Harmony capabilities, and one HAP corresponds to one entry capability (mainAbility). Ability is an abstraction of the capabilities an application has. Each ability can run independently and complete a specific function. One or more functions can complete a specific convenience service.

For example, as shown in Figure 13, an APP entrance card is provided, through which the corresponding APP can be accessed (the APP can be an ordinary APP or a service). The entrance card can automatically initiate a query operation for nearby food through a scheduled task, or the user can click the entrance card to initiate a query operation for nearby food, enter the query result display interface, and browse the query results, that is, nearby food information.

Optionally, the query operation may also include manually inputting query information, such as inputting to query nearby restaurants, movie theaters, or hotels. For example, the user can click on the input box of the entrance card on the user device, manually enter "query nearby food", and click Query to initiate a query operation for nearby food.

S202. In response to the query operation initiated by the user, the user device sends a first query request to the APP server.

In this embodiment of the present application, the first query request can be used to request the APP server to perform data query to obtain query result data that satisfies the first query request. For example, in some application scenarios, the first query request is used to request the APP server to query restaurants, hotels, attractions, movie theaters, or product discount information near the user.

In one example, the first query request may include the user's identification information (for example, the user ID of the APP), and the query information (or the query keyword in the query information). For example, the query information is the queried restaurant (or query keyword: restaurant).

In yet another example, the first query request may not only include query information or query keywords, but may also include multiple query conditions. For example, the first query request may also include one or more query conditions such as location information of the user equipment, device attributes of the user equipment, and user attributes. In this way, the APP server can obtain the user's personalized query result data based on the query conditions based on the location information of the user device, so that the query result data is closer to the user's desired query result, thereby improving the user's experience.

As an example, the first query request includes location information of the user equipment, device attributes of the user equipment, and user attributes. Among them, the location information of the user equipment can be used to indicate the current location of the user equipment. The location information of the user equipment can include at least one of the following information: longitude and latitude information, street information, geographical area information (such as XX City, XX District). ), the business district information to which it belongs, etc. The location information of the user device can be used by the APP server to obtain the query result data in order from near to far using the location information as the origin.

For example, the user equipment can be the electronic equipment in Figure 9. The user equipment can implement global navigation satellite technology through antenna 1 or antenna 2 and the wireless communication module 160. The user equipment can be positioned through the global navigation satellite technology to obtain the user equipment. location information. For example, the user equipment can locate the user equipment through GPS, GLONASS, BDS, QZSS, SBAS, etc., and obtain the location information of the user equipment (such as latitude and longitude information, etc.).

The device attributes of the user equipment can be used to characterize the attribute information of the user equipment. The device attributes include at least one of the following information: user equipment identifier, system version number, APP client version number, user equipment model, and user equipment type. , user equipment configuration information and user equipment screen information, etc. The user equipment identifier can be used to identify the user equipment, such as International Mobile Equipment Identity (IMEI), International Mobile Subscriber Identity (IMSI), etc. The system version number is the version number of the user's device operating system, such as Harmony OS 2.0, Harmony OS 3.0, etc. The APP client version number is the version number of the APP in the user device. The model of the user device, such as Huawei P50Pro, Huawei Mate 40Pro, Huawei P40Pro+, etc. The type of user device, such as smartphone, tablet, smart watch, smart bracelet, etc. The user device configuration information includes the configuration parameters of the user device, for example, the amount of data that can be displayed on the home page of the user device, and the amount of data that the APP server needs to return for the first time for display, etc. The user equipment screen information indicates whether the user equipment has a display interface.

User attributes are used to characterize the user's identity information. User attributes include: user identification number (identity document, ID) of the user device, user ID of the APP, etc. The user ID of the APP may be, for example, the user login name of the APP, the user's mobile phone number, etc.

S203. The APP server obtains the user portrait data of the user according to the first query request.

Optionally, the user's user profile data can be used to represent the characteristics of the user and usage scenarios. For example, the user's user profile data includes at least one of the following information: the user's gender, the user's age, the user's preferences, the user's region, the query time, and the query scenario. Among them, the user's preferences include, for example: liking fast food, liking Chinese food, etc. User regions include: Northeastern region, Sichuan and Chongqing regions, Guangdong, Hong Kong and Macao regions, etc. Query times include, for example: morning, noon, and evening. Query scenarios include, for example: querying coupons, querying restaurant dishes, etc.

In some embodiments, a user profile service is deployed in the data query system, and the user profile data of the user can be obtained through the user profile service. Regarding the user profiling service, please refer to the description of the data query system above and will not go into details here.

The APP server can obtain the user's user portrait data through the user portrait service. For example, the first query request includes device attributes and user attributes, the device attributes include the user device identifier, and the user attributes include the user ID of the APP. The APP server can obtain the user's user portrait data in the user portrait database through the user portrait service based on the user's device identifier and/or the APP's user ID.

Optionally, the user portrait database may include user equipment identifiers and user portrait data corresponding to the user equipment identifiers. The APP server sends the user device identifier to the user portrait service, and the user portrait service receives the user device identifier. The user portrait service can query the user profile database for user portrait data corresponding to the user device identifier based on the user device identifier.

Optionally, the user portrait database may include the user ID of the APP and user portrait data corresponding to the user ID of the APP. The APP server sends the user ID of the APP to the user portrait service. The user portrait service receives the user ID of the APP. The user portrait service can query the user portrait data corresponding to the user ID of the APP in the user portrait database based on the user ID of the APP.

Optionally, the user portrait database may include the user device identifier and the user ID of the APP, as well as user portrait data corresponding to the user device identifier and the user ID of the APP. The APP server sends the user device identifier and/or the user ID of the APP to the user portrait service. The user portrait service receives the user device identifier and/or the user ID of the APP. The user portrait service uses the user device identifier and/or the user ID of the APP. The ID can query the user portrait database for user portrait data corresponding to the user's device identifier and/or the user ID of the APP.

In some embodiments, the user portrait database can be constructed and generated based on device attributes, user attributes, and the user's historical usage records. For example, a 20-year-old male user often uses his user ID to log in to a consumer recommendation APP with version number 5.0. The APP is installed on a smartphone running Harmony OS 3.0. The user often searches for Yuhuatai District, Nanjing City at 12 noon. Coupon information for fast food restaurants. In the user portrait database, the user portrait data corresponding to the user's user ID includes: {user's gender: male, user's age: young people (18-24 years old) 20 years old, user's region: Yuhuatai District, Nanjing City, Query time: noon (11:00-13:00), query scenario: fast food restaurant coupons, user device type: smartphone, user device system version: Harmony OS 3.0, APP client version: 5.0}.

In some embodiments, before executing S203, the APP server may also perform authentication, authentication, preprocessing, routing, and orchestration on the first query request. For example, if the user does not enter a user name (or user ID of the APP) and password to log in to the APP when initiating a query operation to the APP on the user device, the APP server can query the user ID of the APP in the first query request. Perform authentication and authentication to confirm the user's identity and whether the user has the authority to access the APP server. The APP server can also preprocess the first query request and parse it to obtain the information contained in the first query request. For example, it can be parsed to obtain: query information, location information of the user device, device attributes and user attributes of the user device, etc. The APP server routes the query processing process to the server deployed by the designated service (such as user portrait service, retrieval service, metadata query service) according to the specific request content. The APP server can also arrange the sequence of the entire query processing process according to the query. In this way, the APP server can query according to the query processing flow according to the first query request to prevent errors in the query processing flow.

S204. The APP server obtains a query result identifier set according to the user's user portrait data and the first query request.

In this embodiment of the present application, the APP server can obtain a set of query result identifiers based on the user portrait data obtained in S203, combined with the device attributes and location information in the first query request. The query result identifier set includes a unique identifier corresponding to each query result data. The unique identifier has a one-to-one mapping relationship with the query result data. A unique query result data can be determined based on a unique identifier. The unique identifier may be the unique ID of the query result data, or the attribute information associated with the query result data, etc.

Among them, the unique identifiers in the query result identifier set can be sorted according to the preset sorting rules. For example, the preset sorting rule may be to sort the location information from near to far. Specifically, for example, each query result data includes location information. Based on the location information in each query result data, the distance from the user's location is calculated. In order from nearest to far, each query structure data is Sort by corresponding unique identifier.

In some embodiments, a retrieval service is deployed in the data query system, through which the query result identifier can be obtained symbol collection. Regarding the retrieval service, please refer to the above description of the data query system, and will not be described in detail here.

As shown in Figure 11, the APP server can obtain the query result identifier set through the retrieval service based on user portrait data, device attributes and location information. Specifically, the APP server sends the user portrait data, device attributes and location information to the retrieval service. The retrieval service retrieves the result identifier set in the retrieval database based on the user portrait data, device attributes and location information, and collects the result identifier set. Return to the APP server.

Among them, the retrieval database includes information related to all display resources (business information) on the display interface corresponding to the APP. Businesses include, for example: restaurants, hotels, movie theaters, etc. Business information includes but is not limited to: the unique identifier of the business, and the business information. labels etc. The merchant's label refers to a summary description of the merchant's information, for example, a label for the merchant's type: fast food restaurant, a label for whether the merchant has coupon activities: yes, etc. The retrieval service can filter the merchant's information in the retrieval database based on the merchant's tag to obtain the merchant's information that satisfies the user's portrait data and the first query request. The merchant's tag can be added by the user based on the merchant's information when building the retrieval database. The merchant's tag can also be updated or added by the user during the use of the retrieval database.

Optionally, the merchant's information also includes the merchant's location information. The merchant's location information can be used to rank the unique identifiers in the set of query result identifiers according to their distance from the user's device.

Below, the first query request is: restaurant information near the user, and the user portrait data is: {user's gender: male, query time: noon, query scenario: restaurant coupons, age: young people, food preference: spicy hot pot} , the device properties are:

{User device type: smartphone}, the location information is: 45° north latitude, 123° east longitude, and the sorting rule is from nearest to far from the user device. Take this example to illustrate that the retrieval service retrieves the result identifier set in the retrieval database. the process of.

First, the retrieval service arranges all businesses in order from nearest to farthest from 45° north latitude and 123° east longitude based on the user's location information: 45° north latitude, 123° east longitude and the location information of the merchants. Then, the retrieval service filters merchants based on the above user portrait data, device attributes and merchant information (such as merchant tags). For example, if the label of the merchant type is: spicy hot pot, the merchant's information will be retained; otherwise, the merchant's information will be removed. For another example, if the merchant has a label for coupon activities: Yes, the merchant's priority will be increased based on the user portrait data, that is, if the merchant is close to the user's location (for example, the distance is less than 100m) and the location is the same, the merchant's ranking will be Higher than merchants without coupon activities to give priority to display the merchant's information. Finally, the retrieval service obtains merchant information that satisfies query conditions such as user portrait data, device attributes, and location information, and is sorted from nearest to far from the user device, extracts the unique identifier of each merchant in the merchant information, and combines all unique The identifiers form an identifier set, that is, the query result identifier set is obtained.

S205. The APP server obtains the first returned data and the first information according to the query result identifier set.

In this embodiment of the present application, the APP server obtains the first return data and the first information according to the query result identifier set, which may include: the APP server determines the query result data obtained from the query according to the query result identifier set, and according to the preset return method /Display mode (for example: paging mode) determines the batch return mode to return query result data to the user device. Based on the batch return method, the APP server obtains a part of the batch of query result data to be returned to the user device, and the first information used to indicate the unique identifier of the remaining batch of query result data. So that the user device responds to the user's further loading operation and obtains the remaining batches of query result data from the APP server according to the first information.

In this embodiment of the present application, the query result data returned in batches may include: query result data returned for the first time (first time) and query result data returned for a non-first time, such as query result data returned for the first time (first time). Can be called the first returned data set. The first returned data set includes query result data returned by the APP server to the user device for the first time. Optionally, the APP server may determine a first identifier set based on the query result identifier set, where the first identifier set includes: a unique identifier corresponding to the query result data returned for the first time. The first identifier set can be used to obtain query result data corresponding to the unique identifier, and return it to the user device for direct display. The first information may be used to indicate the second returned data set, that is, the query result data that is not returned for the first time. For example, the first information may include unique identifiers of all query result data returned other than for the first time.

In some embodiments, the APP server may determine the first set of identifiers based on device attributes. Specifically, taking the user device to display query result data in the form of paged display as an example, the APP server can determine the first identifier based on the amount of data (such as the number of data items) that can be displayed on the display interface of the user device at one time (one page or home page) gather. The first set of identifiers may include the amount of data on the homepage of the user device or the amount of data on previous pages to increase the amount of data that the user can browse. For example, the homepage of the user device can display 10 pieces of data, and the first identifier set can include the first 10 unique identifiers in the query result identifier set, or the unique identifiers of the first 10 integer multiples.

Optionally, in some embodiments, when the user device sends the first query request to the APP server, the device attributes include user device configuration information. The user device configuration information includes, for example: the amount of data that can be displayed on the homepage of the user device. , or the amount of data that the APP server needs to return for the first time for display. Of course, it can also include both the amount of data that can be displayed on the homepage of the user's device, and the amount of data that the APP server needs to return for the first time for display. The APP server may determine the number of unique identifiers returned for the first time based on the user device configuration information in the device properties, and form a first set of identifiers.

Optionally, in some embodiments, when the user device sends the first query request to the APP server, the device attributes may include attribute information such as the type of user device and the version number of the APP client. The APP server may determine the amount of data that can be displayed on the home page of the user device based on the type of the user device and the version number of the APP client, and then determine the first set of identifiers based on the amount of data that can be displayed on the home page of the user device. For example, if the device type is a smartphone and the APP client version number is version 2.0, and the APP version 2.0 can display 5 pieces of data on the homepage of the smartphone, the APP server determines that the first set of identifiers can include the query result identifier. The first 5 unique identifiers in the collection, or the unique identifiers of the first 5 integer multiples. For another example, if the device type is: tablet computer, the APP client version number is: version 2.0, and the homepage of version 2.0 APP can display 20 pieces of data on the tablet computer, then the APP server determines that the first identifier set can include the query result identifier The first 20 unique identifiers in the symbol set, or the number of unique identifiers that are an integer multiple of the first 20.

Optionally, in some embodiments, when the user device sends the first query request to the APP server, the device attributes carried therein may include caching capability information of the user device, and the APP server may obtain the network connection between it and the user device. state. The APP server determines the number of unique identifiers included in the first identifier set based on the caching capability information of the user device, the data volume of the query result data, the network status, and other conditions. Exemplarily, the number of unique identifiers included in the first set of identifiers is positively correlated with the cache capability of the user equipment and the quality of the network status. The higher the cache capacity of the user equipment, the better the network status. The number of unique identifiers included in an identifier set can be larger. The number of unique identifiers included in the first identifier set is negatively correlated with the data volume of the query result data. The larger the data volume of the query result data, the greater the number of unique identifiers included in the first identifier set. few. It is understandable that the APP server may determine the number of unique identifiers included in the first identifier set based on one or more of the caching capability information of the user device, the size of the query result data, and the network status. This application does not specifically limit the number of unique identifiers included in the first identifier set.

In some embodiments, a metadata query service is deployed in the data query system, and the corresponding query result data can be determined according to the unique identifier in the metadata query service. Regarding the metadata query service, please refer to the description of the data query system above, and will not be described in detail here.

As shown in Figure 11, the APP server can obtain the first return data set through the metadata query service according to the first identifier set. Specifically, the APP server sends the first set of identifiers to the metadata query service, and the metadata query service retrieves the query corresponding to each unique identifier in the metadata database based on each unique identifier in the first set of identifiers. The result data forms the first return data set and is sent to the APP server.

Among them, the metadata database includes the unique identifier of the query result data and the corresponding query result data. The unique query result data can be determined based on the unique identifier of the query result data. Taking the query result data as restaurant information as an example, the unique identifier can be the restaurant number. The restaurant information can be determined based on the restaurant number. For example, it can include: restaurant location, per capita consumption, business hours, contact number, dishes, reviews, and Discount information, etc.

Optionally, in some embodiments, the retrieval database used by the above retrieval service can be a metadata database with tags, that is, the retrieval database can be obtained by adding tags to the data in the metadata database.

In some embodiments, the first information may be used to indicate a second set of returned data. For example, the first information may include a second set of identifiers, and the second set of identifiers is determined based on a set of query result identifiers. For example, the second set of identifiers may include: the remainder of the set of query result identifiers after excluding the first set of identifiers. All unique identifiers, or the second set of identifiers is the same as the set of query result identifiers, or the unique identifiers included in the second set of identifiers are a subset of the unique identifiers included in the set of query result identifiers. The second identifier set can be used by the APP server to directly return to the user device, so that the user device can subsequently obtain other query result data based on the second identifier set.

In some embodiments, the first information may include a session identifier, and there is a mapping relationship between the session identifier and the second set of identifiers. When the amount of data in the second set of identifiers is large, the APP server may create a session identifier to identify the second set of identifiers. Specifically, the session identifier has a mapping relationship with the second set of identifiers. According to a session The identifier may uniquely identify a second set of identifiers. The APP server may cache the session identifier and the second identifier set having a mapping relationship with the session identifier, for example, in a retrieval service. The APP server sends the session identifier to the user device, and the user device can request query result data from the APP server based on the session identifier. In this way, the amount of data sent by the APP server to the user device can be reduced, thereby reducing the transmission pressure on the APP server.

S206. The APP server sends the first return data set and the first information to the user device.

In this embodiment of the present application, as shown in Figure 14, after performing data query according to the first query request sent by the user device, the APP server returns the first return data set and the first information to the user device for the first time. Taking the user device displaying query result data in the form of paged display as an example, the first returned data set includes a part (home page or previous pages) of query result data for display by the user device directly through the display interface of the user device. The first information is used to indicate the unique identifier of the remaining part of the query result data. For example, the first information includes a second set of identifiers, or includes a session identifier that has a mapping relationship with the second set of identifiers. The user equipment can query the APP server for remaining query result data based on the first information. In this way, the APP server does not need to cache the first returned data set and the first information, and the user device can also obtain all query result data through the APP server.

S207. The user equipment receives the first return data set and the first information, displays the first return data set, and saves the first information.

In this embodiment of the present application, as shown in Figure 14, after the user equipment receives the first returned data set and the first information, the user equipment can display the query result data in the first returned data set through the display interface. If the first returned data set includes multi-page query result data, the user can also slide down the display interface of the user device, that is, as the user drags and drops the display interface, the display interface scrolls from bottom to top, causing the user device to load Display query result data for the next page. At the same time, the memory of the user equipment saves the received first information for querying the APP server for remaining query result data based on the first information.

S208. The user initiates a loading operation to the APP on the user device.

In this embodiment of the present application, when the user has browsed all the query result data in the first returned data set and needs to browse other query result data, the user can initiate a loading operation to the APP on the user device. For example, taking the user equipment as a smartphone as an example, Figure 15 is a schematic diagram of the user equipment sending a second query request according to an embodiment of the present application. As shown in Figure 15, the user can browse the first returned data by sliding the display screen of the smartphone. Query result data in the set, after the last result data in the first returned data set is displayed, if the user wants to browse more query result data, he can slide down the display interface of the user device, that is, as the user navigates the display interface The drag operation causes the display interface to scroll from bottom to top. For example, as shown in Figure 15, the prompt "Load more..." can be displayed on the display interface of the electronic device, that is, the loading operation is initiated in the APP.

S209. In response to the loading operation initiated by the user, the user equipment sends a second query request to the APP server.

In this embodiment of the present application, the second query request may include second information.

In one example, the second information is used to represent a third return data set, and the third data set is part or all of the second return data set. For example, the second information may include a third set of identifiers. Wherein, the third set of identifiers is a subset of the second set of identifiers.

For example, it is assumed that the first information includes the second set of identifiers, and the second information includes the third set of identifiers. The third set of identifiers includes unique identifiers corresponding to the query result data to be obtained, which are part of the unique identifiers in the second set of identifiers. The APP server can obtain the corresponding query result data according to the unique identifier in the third identifier set, and return it to the user device.

Taking the user device displaying the query result data in a paged display as an example, the third set of identifiers may include unique identifiers corresponding to the query result data of the next page or several pages. The number of unique identifiers included in the third identifier set may refer to the method for determining the number of unique identifiers in the first identifier set in S205 above, which will not be described again here. The third identifier set may also include all unique identifiers in the second identifier set, which is not limited in this embodiment of the application.

In yet another example, the second information may include a session identifier. The APP server can determine the corresponding second identifier set according to the session identifier, to further obtain the corresponding query result data according to the second identifier set, and return it to the user device.

S210. The APP server obtains the third returned data set according to the second query request.

In this embodiment of the present application, the third returned data set includes query result data corresponding to the second information. Take, for example, that the second information includes the third set of identifiers. The APP server obtains each unique identifier in the third identifier set based on the received third identifier set. The query result data corresponding to an identifier constitutes the third returned data set.

In some embodiments, as shown in Figure 11, the APP server can obtain the third returned data set through the metadata query service. Specifically, the APP server sends the third set of identifiers to the metadata query service. The metadata query service retrieves the query corresponding to each unique identifier in the metadata database based on each unique identifier in the third set of identifiers. The result data forms a third return data set and is sent to the APP server.

S211. The APP server sends the third return data set to the user device.

In the embodiment of the present application, Figure 16 is a schematic diagram of the APP server sending the third return data set according to the embodiment of the present application. As shown in Figure 16, the APP server sends the third return data set obtained in S210 to the user device to Query result data corresponding to each unique identifier in the third identifier set is fed back to the user equipment, so that the user equipment obtains other query result data (ie, the third returned data set).

S212. The user equipment receives and displays the third returned data set.

In this embodiment of the present application, as shown in Figure 16, the user equipment can display the query result data in the third returned data set through the display interface to facilitate user browsing.

In some embodiments, the above-mentioned S208 and subsequent steps are optional steps. If the user device no longer needs to obtain other query result data (for example, the user has made a selection based on the displayed query result data, there is no need to browse other query result data. ), or all query result data has been obtained, S208 and subsequent steps will not be executed. If the user device needs to obtain other query result data, S208 and subsequent steps are performed.

In some embodiments, in order to improve the user's fluency in browsing query result data. In S208, before the user initiates a loading operation to the APP on the user device and obtains the query result data to be loaded (such as the query result data of the next page or the next few pages). The user device can obtain the query result data to be loaded (such as the query result data of the next page or the next few pages) in advance, and store the obtained query result data in the local (memory) of the user device. Subsequently, in response to the user's loading operation, the query result data to be loaded is obtained locally and displayed to the user.

For example, the user device can use an asynchronous thread to obtain the query result data to be loaded in advance. For example, two threads (or work processes) can be set up in the user device. One thread is used to perform the following loading process: respond to the user's loading operation, obtain and display the query result data, and this thread can be called the main thread. Another thread is used to perform the process of obtaining query result data during the above loading process. This thread can be called an auxiliary thread or a child thread. These two threads work independently (or work asynchronously). Before the main thread obtains the query result data to be loaded, the user device can start the auxiliary thread to obtain the query result data to be loaded from the APP server in advance.

For example, if the display interface of the user device can display 30 pieces of query result data on one page, the first returned data set includes 90 pieces of query result data. Then when the user browses to the 61st query result data, that is, when he browses to the 3rd page, the user device can start the above-mentioned asynchronous thread method to send a second query request to the APP server to obtain the 4th or more pages of queries. The resulting data is saved locally on the user's device. When the user needs to browse the query result data on page 4, the user device can locally obtain and directly display the query result data on page 4. In this way, the user's fluency in browsing query result data can be improved and the user's experience can be improved.

It should be noted that the time when the user device starts the asynchronous thread and the amount of query result data obtained through the asynchronous thread can be determined based on the user's browsing speed, the size of the query result data, and the number of query result data included in the first returned data set. The quantity, caching and other performance of the user equipment, and the status of the communication network between the user equipment and the APP server are comprehensively determined, and this application does not limit this.

In some embodiments, in order to reduce the caching pressure on the APP server and user equipment. Embodiments of the present application also provide a data query method that neither caches the query result data on the APP server nor caches the query result data on the user device. Each time the user device sends a query request, the APP server re-queries according to the query request and returns the latest query result data that satisfies the query request. The latest query result data includes the query result data of the home page or previous pages. Figure 17 is a schematic flow chart of another data query method according to an embodiment of the present application. As shown in Figure 17, taking data query based on location information as an example, the method includes the following steps S301-S314:

S301. The user initiates a query operation on the user device.

S302. In response to the query operation initiated by the user, the user device sends a first query request to the APP server.

S303. The APP server obtains the first user portrait data of the user according to the first query request.

S304. The APP server obtains the first query result identifier set according to the first user portrait data and the first query request.

In this embodiment of the present application, the specific implementation of S301-S304 may refer to the implementation of S201-S204 described above, and will not be described again here.

S305. The APP server obtains the first returned data set according to the first query result identifier set.

In some embodiments, the APP server may determine the first set of identifiers from the first set of query result identifiers, where the first set of identifiers includes the unique identifier of the query result data for which the APP server returns complete information to the user device for the first time. The APP server can obtain corresponding query result data according to the first identifier set to form a first returned data set.

In some embodiments, the APP server may obtain the first returned data set through the metadata query service according to the first query result identifier set. Wherein, the APP server determines the first set of identifiers and obtains the first set of returned data based on the first set of identifiers. The implementation method may refer to the method in S205, which will not be described again here.

S306. The APP server sends the first return data set to the user device.

In this embodiment of the present application, after performing data query according to the first query request sent by the user device, the APP server returns the first return data set to the user device for the first time. Taking the user device displaying the query result data in the form of paged display as an example, that is, a part of the query result data (the home page or the first few pages) is returned for the first time for display by the user device directly through the display interface of the user device. In this way, neither the APP server nor the user device needs to cache the query result data, and the transmission pressure of the APP server returning query data to the user device can be reduced.

S307. The user equipment receives the first return data set and displays the first return data set.

In this embodiment of the present application, the user equipment can display the query result data in the first returned data set through the display interface of the user equipment. If the first returned data set includes multi-page query result data, the user can also slide down the display interface of the user device, that is, as the user drags and drops the display interface, the display interface scrolls from bottom to top, causing the user device to load Display query result data for the next page. In this way, the user device does not need to cache other data, which reduces the cache pressure on the user device.

S308. The user initiates a loading operation to the APP on the user device.

In this embodiment of the present application, when the user has browsed all the query result data in the first returned data set and needs to browse other query result data, the user can initiate a loading operation to the APP on the user device. The specific implementation method for the user to initiate a loading operation to the APP on the user device may refer to the method in S208, which will not be described in detail here.

S309. In response to the loading operation initiated by the user, the user equipment sends a second query request to the APP server, and the second query request includes the query result data offset.

In this embodiment of the present application, in response to the loading operation initiated by the user, the user device can send a second query request to the APP server. The second query request is used to instruct the APP server to re-perform data query to obtain query results that satisfy the second query request. data.

The query result data offset is used to characterize the data characteristics of the query result data that the user has browsed, where the query result data that the user has browsed is the query result data in the first returned data set. The data feature is the offset of the same parameter in the query result data. For example, the offset of the position in the query result data.

In some embodiments, in the application scenario of performing data query based on the location information of the user equipment, the first query request includes the location information of the user equipment, the device attributes of the user equipment, and the user attributes as an example. Then the second query request includes the second location information of the user equipment, the device attributes of the user equipment, the user attributes, and the query result data offset. The query result data offset is the distance between the position of the query result data that the user has browsed relative to the first position of the user device. For example, if the location of the user's last browsed query result data is 3 kilometers (kilometer, Km) relative to the first location of the user device, the offset of the query result data is 3Km.

In some embodiments, the second location information may be the same as the first location information, or may be different. For example, in some application scenarios, if the location of the user device does not change while the user is browsing the query result data, the second location information is the same as the first location information. If the location of the user device changes while the user is browsing the query result data, for example, the user is holding the user device and viewing the query result data while walking. In this case, the second location information is different from the first location information, and the second location information should be the latest location information of the user. Therefore, in S309, before the user equipment sends the second query request to the APP server, it also includes obtaining the user's second location information. In this way, in the application scenario of data query based on the location information of the user device, the accuracy of the data query results can be improved.

For example, the user sends the first query request at location A and obtains the first returned data set. The user browses while walking. Browse the query result data in the first returned data collection. When the user reaches position B, he has browsed all the query result data in the first returned data set. Among them, the location displayed in the last query result data is 2Km away from the user. At this time, if the user needs to obtain the remaining query result data, the second query request is sent through the user device. The second query request includes at least: B location information, and the query result data offset is: 2Km. According to the second query request, the APP server can query and obtain query result data whose location is more than 2Km away from the user's latest location (location B). In this way, it can not only improve the accuracy of the data query results, but also ensure that the query result data browsed by the user maintains consistency in location information, thereby improving the user experience.

Optionally, in the application scenario of data query based on the sales volume of the query object (merchant), the query result data offset is the sales volume of the query result data that the user has browsed. In the application scenario of data query based on the rating of the query object (merchant), the query result data offset is the rating of the query result data that the user has browsed.

In some embodiments, in order to improve the user's fluency in browsing query result data, in S308, before the user initiates a loading operation to the APP on the user device, the user device can obtain the query result data to be loaded (the next page or the next few pages) in advance. Page query result data), for example, the user device can start an asynchronous thread in the background to send a second query request to the APP server in advance to obtain the query result data to be loaded. In this way, the user's fluency in browsing query result data can be improved and the user's experience can be improved.

It should be noted that the time when the user device starts the asynchronous thread and the amount of query result data obtained through the asynchronous thread can be determined based on the user's browsing speed, the size of the query result data, and the number of query result data included in the first returned data set. The quantity, caching and other performance of the user equipment, and the status of the communication network between the user equipment and the APP server are comprehensively determined, and this application does not limit this.

S310. The APP server obtains the second user portrait data of the user according to the second query request.

S311. The APP server obtains the second query result identifier set according to the second user portrait data and the second query request.

In this embodiment of the present application, the APP server re-queries according to the second query request and obtains the second query result identifier set.

In some embodiments, the APP server may obtain the user's second user profile data through the user profile service according to the second query request.

In some embodiments, the APP server may obtain the second query result identifier set through the retrieval service according to the second user portrait data and the second query request.

Specifically, take the second query request including the second location information of the user equipment, the device attributes of the user equipment, the user attributes, and the query result data offset as an example. The APP server can send the location information of the user device, device attributes of the user device, user attributes and query result data offset to the retrieval service. The retrieval service retrieves the second result identifier set in the retrieval database according to the above query conditions, and returns the second result identifier set to the APP server.

Specifically, reference may be made to S203-S204 for the specific implementation of the above S310-S311, which will not be described in detail here.

S312. The APP server obtains the second returned data set according to the second query result identifier set.

In some embodiments, the APP server can determine the second set of identifiers from the second set of query result identifiers. The second set of identifiers includes the unique identifier of the query result data for which the APP server returns complete information to the user device this time. . The APP server can obtain corresponding query result data according to the second identifier set to form a second return data set.

In some embodiments, the specific method for the APP server to determine the second identifier set may refer to the method for determining the first identifier set in S205, which will not be described again.

In some embodiments, the APP server can obtain the second return data set through the metadata query service according to the second query result identifier set. The implementation method of the APP server obtaining the second return data set according to the second identifier set can refer to S205. The method will not be described in detail here.

S313. The APP server sends the second return data set to the user device.

S314. The user equipment receives the second return data set and displays the second return data set.

In this embodiment of the present application, the specific implementation of S313-S314 may refer to the implementation of S306-S307 described above, and will not be described again here.

In some embodiments, the above-mentioned S308 and subsequent steps are optional steps. If the user device no longer needs to obtain other query result data, or all query result data has been obtained, S308 and subsequent steps will not be performed. If the user device needs to obtain other query result data, S308 and subsequent steps are performed.

The above mainly introduces the solution provided by the embodiment of the present application from the perspective of interaction between various nodes. It can be understood that in order to implement the above functions, each node, such as user equipment, APP server, etc., includes hardware structures and/or software modules corresponding to each function. Those skilled in the art should readily appreciate that the algorithm steps of each example described in conjunction with the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

Embodiments of the present application can group functional modules of user equipment, APP servers, etc. according to the above method examples. For example, each functional module can be grouped corresponding to each function, or two or more functions can be integrated into one processing module. . The above integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the grouping of modules in the embodiment of the present application is schematic and is only a logical function grouping. In actual implementation, there may be other grouping methods.

Figure 18 shows a schematic structural diagram of an electronic device 300. The electronic device 300 may be an APP server, a chip in the APP server, or a system on a chip. The electronic device 300 may be used to perform the first step involved in the above embodiment. Device functionality.

As an implementation manner, the electronic device 300 shown in FIG. 18 includes: a receiving module 310, a processing module 320, and a sending module 330. Among them, the receiving module 310 is used to receive the query request sent by the user equipment, the processing module 320 is used to obtain the query result data according to the query request, and the sending module 330 is used to send the query result data to the receiving user device.

It can be understood that the above-mentioned electronic device 300 may also include components as shown in Figure 9. At this time, the transceiver action in the above-mentioned electronic device 300 may be performed by antenna 1, antenna 2, mobile communication module 150, and wireless communication module 160 in Figure 9 and other components are executed, and specific processing actions may be executed by the processor 110 in FIG. 9 .

An embodiment of the present application also provides an electronic device, which may include one or more processors, memories, and communication interfaces. Among them, the memory, communication interface and processor are coupled. For example, memory, communication interfaces, and processors may be coupled together via a bus.

Among them, the communication interface is used for data transmission with other devices. Computer program code is stored in the memory. The computer program code includes computer instructions. When the computer instructions are executed by the processor, the electronic device causes the electronic device to execute the data query method in the embodiment of the present application.

It can be understood that the above-mentioned electronic device may also include components as shown in FIG. 9 . For example, the processor may be the processor 110 in FIG. 9 , the memory may be the internal memory 121 in FIG. 9 or an external memory connected through the external memory interface 120 , and the communication interface may be the USB interface in FIG. 9 .

Embodiments of the present application also provide a data query system, which includes a user device, an APP server, a user portrait service, a retrieval service and a metadata query service; wherein the user device is used to send a query request to the APP server, and the APP server is used to Obtain query result data according to the query request, and send the query result data to the receiving user device.

In some embodiments, the query request includes location information, device attributes and user attributes, then the above-mentioned data loading system may also include: user profiling service, retrieval service and metadata query service, wherein the user profiling service is used to determine the location information according to the device attributes. and/or user attributes determine the user portrait data. The retrieval service user retrieves the unique identifier set corresponding to the query result data based on the user portrait data, location information and device attributes. The metadata query service term determines the corresponding query result based on the unique identifier set. data.

Embodiments of the present application also provide a computer-readable storage medium. Computer program code is stored in the computer storage medium. When the above-mentioned processor executes the computer program code, the electronic device executes the relevant steps of the data query method in the above-mentioned method embodiment. .

Embodiments of the present application also provide a computer program product. When the computer program product is run on a computer, it causes the computer to execute the relevant steps of the data query method in the above method embodiment.

Among them, the electronic devices, data loading systems, computer storage media or computer program products provided by this application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the corresponding methods provided above. The beneficial effects of this method will not be repeated here.

Through the description of the above embodiments, those skilled in the art can clearly understand that for convenience and simplicity of description, Only the division of the above functional modules is used as an example. In practical applications, the above function allocation can be completed by different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all of the above descriptions or Some functions.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be The combination can either be integrated into another device, or some features can be omitted, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated. The components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place, or they may be distributed to multiple different places. . Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a readable storage medium. Based on this understanding, the essence of the technical solutions of the embodiments of the present application or the part that contributes or all or part of the technical solutions can be embodied in the form of a software product. The software product is stored in a storage medium and includes several Instructions are used to cause a device (which may be a microcontroller, a chip, etc.) or a processor to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code.

The above contents are only specific implementation modes of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be covered by the protection scope of the present application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims (11)

1. A data query method, characterized in that it is applied to user equipment, and the method includes:

   Send a query request to the server, where the query request includes the user's query information, and the query request is used to obtain the query results corresponding to the query information;

   Receive first return data and first information sent by the server, where the first return data is a subset of the query results, and the query results include multiple pieces of query result data; the first information is used to identify all Part or all of the query result data among the multiple query result data;

   Send a loading request to the server, where the loading request carries second information, where the second information is a subset of the first information;

   Receive query result data of the second information identifier sent by the server.
2. The method according to claim 1, characterized in that:

   The first information includes a set of identifiers, and the set of identifiers includes unique identifiers corresponding to some or all of the plurality of query result data;

   Alternatively, the first information includes a session identifier, and there is a mapping relationship between the session identifier and a set of identifiers; the set of identifiers includes a session identifier corresponding to some or all of the plurality of query result data. Unique identifier.
3. The method according to claim 1 or 2, characterized in that the query request further includes at least one of the following information: location information of the user equipment, device attributes of the user equipment, and user attributes.
4. A data query method, characterized in that it is applied to a server, and the method includes:

   Receive a query request sent by the user equipment, where the query request includes the user's query information, and the query request is used to obtain query results corresponding to the query information;

   According to the query request, first returned data and first information are determined. The first returned data is a subset of the query results, and the query results include multiple query result data; the first information is used to identify Some or all of the plurality of query result data;

   Send the first return data and the first information to the user equipment;

   Receive a loading request sent by the user equipment, where the loading request carries second information, and the second information is a subset of the first information;

   According to the loading request, determine the query result data of the second information identifier;

   Send the query result data of the second information identifier to the user equipment.
5. The method according to claim 4, characterized in that:

   The first information includes a set of identifiers, and the set of identifiers includes unique identifiers corresponding to some or all of the plurality of query result data;

   Alternatively, the first information includes a session identifier, and there is a mapping relationship between the session identifier and a set of identifiers; the set of identifiers includes a session identifier corresponding to some or all of the plurality of query result data. Unique identifier.
6. The method according to claim 4 or 5, characterized in that the query request further includes: location information of the user equipment, device attributes of the user equipment, and user attributes;

   Determining the first returned data and the first information according to the query request includes:

   Determine user portrait data according to the device attributes and/or the user attributes, and the user portrait data is used to characterize the query characteristics of the user;

   Determine a query result identifier set according to the user portrait data, the location information and the device attributes, where the query result identifier set includes a unique identifier corresponding to each query result data;

   The first returned data and the first information are determined based on the set of query result identifiers.
7. The method according to claim 6, wherein the device attributes include a user equipment identifier, and the user attributes include a user identifier; and determining the user portrait according to the device attributes and/or the user attributes. Data includes:

   According to the user equipment identifier and/or the user identifier, the user portrait data is obtained through a user portrait database; the user portrait database includes information that is related to the user equipment identifier and/or the user identifier. User portrait data of mapping relationship.
8. The method according to claim 6 or 7, characterized in that: based on the user portrait data, the location information information and the device attributes to determine the query result identifier set, including:

   According to the user portrait data, the location information and the device attributes, the query result identifier set is retrieved through a search database; the search database includes a unique identifier corresponding to each query result data.
9. An electronic device, characterized by comprising: a memory and one or more processors; the memory is coupled to the processor; wherein computer program code is stored in the memory, and the computer program code includes computer instructions , when the computer instructions are executed by the processor, the electronic device is caused to perform the method according to any one of claims 1-3, or the electronic device is caused to perform the method according to any one of claims 4-8. method described in the item.
10. A computer-readable storage medium, characterized by comprising computer instructions that, when the computer instructions are run on an electronic device, cause the electronic device to perform the method according to any one of claims 1-3, or, The electronic device is caused to perform the method according to any one of claims 4-8.
11. A computer program product, characterized in that, when the computer program product is run on a computer, it causes the computer to execute the method as claimed in any one of claims 1 to 3, or causes the computer to execute the method as claimed in claim 1. The method described in any one of claims 4-8.