CN106933850B - Network data query method, device and system - Google Patents
Network data query method, device and system Download PDFInfo
- Publication number
- CN106933850B CN106933850B CN201511020946.5A CN201511020946A CN106933850B CN 106933850 B CN106933850 B CN 106933850B CN 201511020946 A CN201511020946 A CN 201511020946A CN 106933850 B CN106933850 B CN 106933850B
- Authority
- CN
- China
- Prior art keywords
- query
- data
- characteristic value
- server
- query request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/951—Indexing; Web crawling techniques
Abstract
The application provides a network data query method and a device, wherein the network data query method comprises the following steps: receiving a query request sent by a client, and acquiring query data corresponding to the query request; calculating characteristic values of a fixed data set in the query data, wherein the fixed data set is a set formed by pre-selected data fields; and if the query request contains a characteristic value, and the calculated characteristic value is the same as the characteristic value contained in the query request, deleting the fixed data set from the query data, and sending the query data with the fixed data set deleted and the calculated characteristic value as a query result to the client. The method can reduce unnecessary transmission of repeated data, thereby reducing unnecessary network flow overhead and user waiting time.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a method, an apparatus, and a system for querying network data.
Background
When a user uses a mobile application, the user may encounter a situation that data needs to be queried for a server. For example, a user queries the server for store detail data through a client of a mobile application. Currently, when data query is performed each time, basically consistent complete data is returned. However, partial data of the complete data remains unchanged for a long time, such as addresses, telephones, etc. If these substantially constant data are returned for each query, unnecessary traffic overhead is increased and user latency may be increased.
Disclosure of Invention
The present application is directed to solving, at least to some extent, one of the technical problems in the related art.
Therefore, an object of the present application is to provide a network data query method, which can reduce unnecessary transmission of repeated data, thereby reducing unnecessary network traffic overhead and user waiting time.
Another object of the present application is to provide a network data query device.
Another object of the present application is to provide a network data query system.
In order to achieve the above object, an embodiment of the present application provides a network data query method, including: receiving a query request sent by a client, and acquiring query data corresponding to the query request; calculating characteristic values of a fixed data set in the query data, wherein the fixed data set is a set formed by pre-selected data fields; and if the query request contains a characteristic value, and the calculated characteristic value is the same as the characteristic value contained in the query request, deleting the fixed data set from the query data, and sending the query data with the fixed data set deleted and the calculated characteristic value as a query result to the client.
In the network data query method provided in the embodiment of the first aspect of the present application, by calculating the feature values of the fixed data set and not sending the fixed data set when the query request includes the same feature value, transmission of unnecessary repeated data can be reduced, thereby reducing unnecessary network traffic overhead and user waiting time.
In order to achieve the above object, an embodiment of a second aspect of the present application provides a network data query method, including: sending a query request to a server so that the server acquires query data corresponding to the query request; receiving a query result sent by the server, wherein when the query request contains a characteristic value and is the same as the characteristic value of a fixed data set in the query data calculated by the server, the query result comprises: deleting the data of the fixed data set and the characteristic value obtained by the server side in the query data; and caching the query result.
In the network data query method provided in the embodiment of the second aspect of the present application, when the eigenvalue calculated by the server is the same as the eigenvalue included in the query request, the received query result sent by the server does not include a fixed data set, so that transmission of unnecessary repeated data can be reduced, and unnecessary network traffic overhead and user waiting time can be reduced.
In order to achieve the above object, an embodiment of a third aspect of the present application provides a network data query apparatus, including: the receiving module is used for receiving a query request sent by a client and acquiring query data corresponding to the query request; the computing module is used for computing the characteristic value of a fixed data set in the query data, wherein the fixed data set is a set formed by pre-selected data fields; and the first sending module is used for deleting the fixed data set from the query data and sending the query data with the deleted fixed data set and the calculated characteristic value as query results to the client if the query request contains the characteristic value and the calculated characteristic value is the same as the characteristic value contained in the query request.
In the network data query device provided in the third aspect of the present application, by calculating the feature value of the fixed data set and not sending the fixed data set when the query request includes the same feature value, transmission of unnecessary repeated data can be reduced, thereby reducing unnecessary network traffic overhead and user waiting time.
In order to achieve the above object, a network data query device according to a fourth aspect of the present application includes: the sending module is used for sending a query request to a server so that the server can obtain query data corresponding to the query request; a receiving module, configured to receive a query result sent by the server, where, when the query request includes a feature value and is the same as a feature value of a fixed data set in the query data calculated by the server, the query result includes: deleting the data of the fixed data set and the characteristic value obtained by the server side in the query data; and the cache module is used for caching the query result.
According to the network data query device provided by the embodiment of the fourth aspect of the present application, when the eigenvalue calculated by the server is the same as the eigenvalue included in the query request, the received query result sent by the server does not include a fixed data set, so that transmission of unnecessary repeated data can be reduced, and unnecessary network traffic overhead and user waiting time can be reduced.
In order to achieve the above object, an embodiment of a fifth aspect of the present application provides a network data query system, including: the network data query device provided in the third aspect of the present application and the network data query device provided in the fourth aspect of the present application are provided.
In the network data query system provided in the embodiment of the fifth aspect of the present application, by calculating the feature values of the fixed data set and not sending the fixed data set when the query request includes the same feature value, transmission of unnecessary repeated data can be reduced, so as to reduce unnecessary network traffic overhead and user waiting time.
Additional aspects and advantages of the present application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the present application.
Drawings
The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
fig. 1 is a schematic flowchart of a network data query method according to an embodiment of the present application;
fig. 2 is a schematic flow chart of a network data query method according to another embodiment of the present application;
fig. 3 is a schematic flowchart of a network data query method according to another embodiment of the present application;
fig. 4 is a schematic flowchart of a network data query method according to another embodiment of the present application;
fig. 5 is a schematic structural diagram of a network data query device according to another embodiment of the present application;
fig. 6 is a schematic structural diagram of a network data query device according to another embodiment of the present application;
fig. 7 is a schematic structural diagram of a network data query device according to another embodiment of the present application;
fig. 8 is a schematic structural diagram of a network data query device according to another embodiment of the present application;
fig. 9 is a schematic structural diagram of a network data query device according to another embodiment of the present application.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar modules or modules having the same or similar functionality throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present application. On the contrary, the embodiments of the application include all changes, modifications and equivalents coming within the spirit and terms of the claims appended hereto.
Fig. 1 is a schematic flowchart of a network data query method according to an embodiment of the present application, where the method includes:
s11: receiving a query request sent by a client, and acquiring query data corresponding to the query request.
When a user needs to acquire data, for example, needs to check store detail data, a query request can be sent to the server through the client to acquire corresponding query data.
After receiving the query request sent by the client, the server can obtain the corresponding query data according to the information contained in the query request. For example, the query request includes indication information of store detail data to be queried and specific store identification information, the server can determine the store detail data to be queried according to the indication information, and query the store detail data corresponding to the store identification information from a database storing the store detail data, so as to obtain query data corresponding to the query request.
S12: and calculating characteristic values of a fixed data set in the query data, wherein the fixed data set is a set formed by pre-selected data fields.
The fixed data set of preselected data fields is, for example, an empirically derived set of data fields that are not subject to change with relevance. For example, the basic information of a business can be a fixed data set, including business name, address, and phone number.
The characteristic value is, for example, a hash (hash) value. The hash algorithm maps a binary value of arbitrary length to a smaller binary value of fixed length, referred to as a hash value. Hash values are a unique and extremely compact representation of a piece of data as a value. Alternatively, the first and second electrodes may be,
the characteristic value is, for example, the last modified time of the data. In the embodiment of the present application, the characteristic value is a hash value as an example.
S13: and if the query request contains a characteristic value, and the calculated characteristic value is the same as the characteristic value contained in the query request, deleting the fixed data set from the query data, and sending the query data with the fixed data set deleted and the calculated characteristic value as a query result to the client.
For example, the corresponding query data obtained from the query request is as follows:
assume that the fixed data set includes:
“image”:”http://xxxxxxx.jpg”,
"name": grandma house ",
"Address" is the number 1 of Wantang Lu,
“tel”:”0571-888888”,
“longitude”:”120.2”,
“latitude”:”30.3”,
support [ "WIFI", "parking space", "credit card payment ],
and the hash value calculated according to the fixed data set is: "hash 1": aa21ebb1f3k ".
When the query request includes the above "hash 1": aa21ebb1f3k ", the query result returned to the client will not include the above fixed data set, and specifically, the query result includes:
in some embodiments, referring to fig. 2, the method may further comprise:
s14: and if the query request does not contain the characteristic value, or the calculated characteristic value is different from the contained characteristic value, sending the query data and the calculated characteristic value to a client as a query result.
For example, if the query request does not contain the above-mentioned "hash 1": aa21ebb1f3k ", the returned query result is:
in this embodiment, by calculating the feature value of the fixed data set and not sending the fixed data set when the query request includes the same feature value, unnecessary transmission of repeated data can be reduced, thereby reducing unnecessary network traffic overhead and user waiting time.
Fig. 3 is a schematic flowchart of a network data query method according to another embodiment of the present application, where the method includes:
s31: and sending a query request to a server so that the server acquires query data corresponding to the query request.
When the client needs to obtain data from the server, a query request can be sent to the server to obtain corresponding query data.
S32: receiving a query result sent by the server, wherein when the query request contains a characteristic value and is the same as the characteristic value of a fixed data set in the query data calculated by the server, the query result comprises: and deleting the data after the fixed data set is deleted from the query data and the characteristic value calculated by the server.
For example, as shown in the foregoing embodiment, when the eigenvalue calculated by the server is the same as the eigenvalue included in the query request, the server no longer sends a fixed data set to the client, so as to reduce duplicate data transmission.
The fixed data set has a set of data fields which are not easy to change and have relevance, such as basic business information.
The characteristic value is, for example, a hash value or a last modified time of the data.
On the other hand, when the query request includes a feature value, or the feature value included in the query request is different from the feature value calculated by the server, the query result includes: and the query data and the characteristic value obtained by the server side through calculation.
For example, when the feature value calculated by the server is different from the feature value in the query request, or the query request does not include the feature value, the query result sent by the server to the client includes the fixed data set, the corresponding feature value, and other query data.
S33: and caching the query result.
After receiving the query result sent by the server, the client can cache the query result. So that cached query results can be cached as a local history for subsequent processes.
In some embodiments, referring to fig. 4, the method comprises:
s41: and inquiring whether the characteristic value exists in the local history cache.
For example, the client queries a local history cache to determine if characteristic values exist.
Correspondingly, the sending of the query request to the server includes:
s42: and if so, the existing characteristic value is contained in the query request and is sent to the server.
For example, when one or more feature values exist in the local history cache, the client includes all the feature values existing in the local history cache in the query request and sends the query request to the server.
S43: and if not, directly sending the query request without the characteristic value to the server.
For example, when the feature value does not exist in the local history cache, the client directly sends a normal query request to the server.
The processing flow after the server receives the query request may refer to the above embodiment, and is not described herein again.
After the query and the processing of the server, the server can return a query result to the client.
In some embodiments, referring to fig. 4, after the client receives and caches the query result sent by the server (S44), the method may further include:
s45: and judging whether the characteristic value exists in the local history cache, if so, executing S46, and otherwise, executing S48.
For example, it may be determined whether a feature value exists by looking at a local history cache.
S46: and judging whether the characteristic value identical to the received characteristic value exists in the local history cache, if so, executing S47, otherwise, executing S48.
The determination may be made by comparing the eigenvalues in the local history cache with the received eigenvalues.
S47: and acquiring fixed set data corresponding to the received characteristic values from the local history cache, and taking the fixed set data and the received query data as service processing data for subsequent service processing.
The characteristic value and the data set can be correspondingly stored in the local history cache, so that the fixed set data corresponding to the received characteristic value can be acquired according to the corresponding relation.
After the fixed set data can be correspondingly stored in the local history cache, the fixed set data and the received query data can form service processing data, and then subsequent service processing can be performed according to the service processing data.
For example, both the local history cache and the received query results include: "hash 1": aa21ebb1f3k ", then the fixed data set corresponding to the hash1 can be obtained from the local history cache, for example:
in addition, the query data in the received query results are:
then, by combining the fixed set data obtained from the local history cache with the received query data, the service processing data is obtained:
s48: and using the received query data as service processing data for subsequent service processing.
For example, the query data received is:
the query data is used as service processing data for subsequent service processing.
In this embodiment, when the eigenvalue calculated by the server is the same as the eigenvalue included in the query request, the received query result sent by the server does not include a fixed data set, which can reduce unnecessary transmission of repeated data, thereby reducing unnecessary network traffic overhead and user waiting time.
Fig. 5 is a schematic structural diagram of a network data query device according to another embodiment of the present application, where the device 50 includes: a receiving module 51, a calculating module 52 and a first transmitting module 53.
The receiving module 51 is configured to receive a query request sent by a client, and obtain query data corresponding to the query request.
When a user needs to acquire data, for example, needs to check store detail data, a query request can be sent to the server through the client to acquire corresponding query data.
After receiving the query request sent by the client, the server can obtain the corresponding query data according to the information contained in the query request. For example, the query request includes indication information of store detail data to be queried and specific store identification information, the server can determine the store detail data to be queried according to the indication information, and query the store detail data corresponding to the store identification information from a database storing the store detail data, so as to obtain query data corresponding to the query request.
A calculating module 52, configured to calculate a feature value of a fixed data set in the query data, where the fixed data set is a set formed by pre-selected data fields.
The fixed data set of preselected data fields is, for example, an empirically derived set of data fields that are not subject to change with relevance. For example, the basic information of a business can be a fixed data set, including business name, address, and phone number.
The characteristic value is, for example, a hash (hash) value. The hash algorithm maps a binary value of arbitrary length to a smaller binary value of fixed length, referred to as a hash value. Hash values are a unique and extremely compact representation of a piece of data as a value. Alternatively, the characteristic value is, for example, the last modified time of the data.
A first sending module 53, configured to delete the fixed data set from the query data if the query request includes a feature value and the calculated feature value is the same as the feature value included in the query request, and send the query data from which the fixed data set is deleted and the calculated feature value to the client as a query result.
In some embodiments, referring to fig. 6, the apparatus further comprises:
a second sending module 54, configured to send the query data and the calculated feature value to the client as a query result if the query request does not include the feature value, or the calculated feature value is different from the included feature value.
For the content of the specific query result, reference may be made to the relevant description in the above method embodiment, and details are not described herein again.
In this embodiment, by calculating the feature value of the fixed data set and not sending the fixed data set when the query request includes the same feature value, unnecessary transmission of repeated data can be reduced, thereby reducing unnecessary network traffic overhead and user waiting time.
Fig. 7 is a schematic structural diagram of a network data query device according to another embodiment of the present application, where the device 70 includes: a sending module 71, a receiving module 72 and a caching module 73.
The sending module 71 is configured to send a query request to a server, so that the server obtains query data corresponding to the query request.
When the client needs to obtain data from the server, a query request can be sent to the server to obtain corresponding query data.
A receiving module 72, configured to receive a query result sent by the server, where, when the query request includes a feature value and is the same as a feature value of a fixed data set in the query data calculated by the server, the query result includes: and deleting the data after the fixed data set is deleted from the query data and the characteristic value calculated by the server.
In some embodiments, when the query request includes a feature value, or the feature value included in the query request is different from the feature value calculated by the server, the query result includes: and the query data and the characteristic value obtained by the server side through calculation.
For example, when the eigenvalue calculated by the server is the same as the eigenvalue included in the query request, the server no longer sends a fixed data set to the client, so as to reduce duplicate data transmission.
The fixed data set has a set of data fields which are not easy to change and have relevance, such as basic business information.
The characteristic value is, for example, a hash value or a last modified time of the data.
On the other hand, when the query request includes a feature value, or the feature value included in the query request is different from the feature value calculated by the server, the query result includes: and the query data and the characteristic value obtained by the server side through calculation.
For example, when the feature value calculated by the server is different from the feature value in the query request, or the query request does not include the feature value, the query result sent by the server to the client includes the fixed data set, the corresponding feature value, and other query data.
And the caching module 73 is used for caching the query result.
After receiving the query result sent by the server, the client can cache the query result. So that cached query results can be cached as a local history for subsequent processes.
In some embodiments, referring to fig. 8, the apparatus 70 further comprises:
a query module 74, configured to query whether a feature value exists in the local history cache;
for example, the client queries a local history cache to determine if characteristic values exist.
Correspondingly, the sending module 71 is specifically configured to:
if the judgment result of the query module is that the characteristic value exists, the existing characteristic value is contained in the query request and is sent to the server;
and if the judgment result of the query module does not exist, directly sending a query request without the characteristic value to the server.
For example, when one or more feature values exist in the local history cache, the client includes all the feature values existing in the local history cache in the query request and sends the query request to the server.
For example, when the feature value does not exist in the local history cache, the client directly sends a normal query request to the server.
In some embodiments, referring to fig. 8, the apparatus 70 further comprises:
the first determining module 75 is configured to determine whether a characteristic value exists in the local history cache.
For example, it may be determined whether a feature value exists by looking at a local history cache.
And a second judging module 76, configured to judge whether a feature value identical to the received feature value exists in the local history cache if the judgment result of the first judging module is yes.
The determination may be made by comparing the eigenvalues in the local history cache with the received eigenvalues.
A first processing module 77, configured to, if the determination result of the second determining module is that the same feature value exists, obtain fixed set data corresponding to the same feature value from the local history cache, and use the fixed set data and the received query data as service processing data for subsequent service processing.
The characteristic value and the data set can be correspondingly stored in the local history cache, so that the fixed set data corresponding to the received characteristic value can be acquired according to the corresponding relation.
After the fixed set data can be correspondingly stored in the local history cache, the fixed set data and the received query data can form service processing data, and then subsequent service processing can be performed according to the service processing data.
A second processing module 78, configured to, if the determination result of the first determining module is that no feature value exists in the local history cache or the determination result of the second determining module is that no feature value identical to the received feature value exists, use the received query data as service processing data for subsequent service processing.
For specific contents of the service processing data, reference may be made to the related description in the foregoing method embodiment, and details are not described herein again.
In this embodiment, when the eigenvalue calculated by the server is the same as the eigenvalue included in the query request, the received query result sent by the server does not include a fixed data set, which can reduce unnecessary transmission of repeated data, thereby reducing unnecessary network traffic overhead and user waiting time.
Fig. 9 is a schematic structural diagram of a network data query device according to another embodiment of the present application, where the device 90 includes: a client device 91 and a server device 92.
The client device 91 may be as shown in fig. 7 or fig. 8, and the server device 92 may be as shown in fig. 5 or fig. 6.
In this embodiment, by calculating the feature value of the fixed data set and not sending the fixed data set when the query request includes the same feature value, unnecessary transmission of repeated data can be reduced, thereby reducing unnecessary network traffic overhead and user waiting time.
It should be noted that, in the description of the present application, the terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Further, in the description of the present application, the meaning of "a plurality" means at least two unless otherwise specified.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.
Claims (9)
1. A network data query method is characterized by comprising the following steps:
receiving a query request sent by a client, and acquiring query data corresponding to the query request;
calculating characteristic values of a fixed data set in the query data, wherein the fixed data set is a set formed by pre-selected data fields;
if the query request contains a characteristic value, and the calculated characteristic value is the same as the characteristic value contained in the query request, deleting the fixed data set from the query data, and sending the query data with the fixed data set deleted and the calculated characteristic value to a client as a query result;
and if the query request does not contain the characteristic value, or the calculated characteristic value is different from the contained characteristic value, sending the query data and the calculated characteristic value to a client as a query result.
2. The method of claim 1, wherein the fixed data set is a set of non-variable data fields with associations.
3. The method of claim 1, wherein the feature values comprise: the hash value, or, the last modified time of the data.
4. A network data query method is characterized by comprising the following steps:
sending a query request to a server so that the server acquires query data corresponding to the query request;
receiving a query result sent by the server, wherein when the query request contains a characteristic value and is the same as the characteristic value of a fixed data set in the query data calculated by the server, the query result comprises: the data after deleting the fixed data set in the query data and the feature value calculated by the server side, when the query request does not include the feature value, or the feature value included in the query request is different from the feature value calculated by the server side, the query result includes: the query data and the characteristic value calculated by the server side;
and caching the query result.
5. The method of claim 4, further comprising:
inquiring whether a characteristic value exists in a local history cache or not;
the sending of the query request to the server includes:
if the characteristic value exists, the existing characteristic value is contained in the query request and is sent to the server;
and if not, directly sending the query request without the characteristic value to the server.
6. The method according to claim 4, wherein after receiving the query result sent by the server, the method further comprises:
judging whether a characteristic value exists in a local history cache or not;
if yes, judging whether a characteristic value identical to the received characteristic value exists in the local history cache or not;
if the same characteristic value exists, acquiring fixed set data corresponding to the same characteristic value from a local history cache, and taking the fixed set data and the received query data as service processing data for subsequent service processing;
and if the characteristic value does not exist in the local history cache or the characteristic value identical to the received characteristic value does not exist, the received query data is used as service processing data for subsequent service processing.
7. A network data query device, comprising:
the receiving module is used for receiving a query request sent by a client and acquiring query data corresponding to the query request;
the computing module is used for computing the characteristic value of a fixed data set in the query data, wherein the fixed data set is a set formed by pre-selected data fields;
the first sending module is used for deleting the fixed data set from the query data and sending the query data with the deleted fixed data set and the calculated characteristic value as query results to the client if the query request contains the characteristic value and the calculated characteristic value is the same as the characteristic value contained in the query request;
and the second sending module is used for sending the query data and the calculated characteristic value to the client as a query result if the query request does not contain the characteristic value or the calculated characteristic value is different from the contained characteristic value.
8. A network data query device, comprising:
the sending module is used for sending a query request to a server so that the server can obtain query data corresponding to the query request;
a receiving module, configured to receive a query result sent by the server, where, when the query request includes a feature value and is the same as a feature value of a fixed data set in the query data calculated by the server, the query result includes: the data after deleting the fixed data set in the query data and the feature value calculated by the server side, when the query request does not include the feature value, or the feature value included in the query request is different from the feature value calculated by the server side, the query result includes: the query data and the characteristic value calculated by the server side;
and the cache module is used for caching the query result.
9. A network data query system, comprising:
the apparatus of claim 7; and the number of the first and second groups,
the apparatus of claim 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201511020946.5A CN106933850B (en) | 2015-12-29 | 2015-12-29 | Network data query method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201511020946.5A CN106933850B (en) | 2015-12-29 | 2015-12-29 | Network data query method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106933850A CN106933850A (en) | 2017-07-07 |
| CN106933850B true CN106933850B (en) | 2020-08-07 |
Family
ID=59441919
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201511020946.5A Active CN106933850B (en) | 2015-12-29 | 2015-12-29 | Network data query method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106933850B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107451204B (en) * | 2017-07-10 | 2021-01-05 | 创新先进技术有限公司 | Data query method, device and equipment |
| CN110084060B (en) * | 2019-03-26 | 2021-05-04 | 银江股份有限公司 | Complex information system collaborative data extraction method |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102456059A (en) * | 2010-10-21 | 2012-05-16 | 英业达股份有限公司 | Data deduplication processing system |
| CN102624605A (en) * | 2011-04-01 | 2012-08-01 | 北京小米科技有限责任公司 | Data transmission method |
| CN102880686A (en) * | 2012-09-17 | 2013-01-16 | 曹欢欢 | Method and device for searching interest point |
| CN104050284A (en) * | 2014-06-27 | 2014-09-17 | 北京思特奇信息技术股份有限公司 | Asynchronous data query method and system based on single process |
| CN104462095A (en) * | 2013-09-13 | 2015-03-25 | 阿里巴巴集团控股有限公司 | Extraction method and device of common pars of query statements |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090094224A1 (en) * | 2007-10-05 | 2009-04-09 | Google Inc. | Collaborative search results |
| US9626361B2 (en) * | 2014-05-09 | 2017-04-18 | Webusal Llc | User-trained searching application system and method |
-
2015
- 2015-12-29 CN CN201511020946.5A patent/CN106933850B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102456059A (en) * | 2010-10-21 | 2012-05-16 | 英业达股份有限公司 | Data deduplication processing system |
| CN102624605A (en) * | 2011-04-01 | 2012-08-01 | 北京小米科技有限责任公司 | Data transmission method |
| CN102880686A (en) * | 2012-09-17 | 2013-01-16 | 曹欢欢 | Method and device for searching interest point |
| CN104462095A (en) * | 2013-09-13 | 2015-03-25 | 阿里巴巴集团控股有限公司 | Extraction method and device of common pars of query statements |
| CN104050284A (en) * | 2014-06-27 | 2014-09-17 | 北京思特奇信息技术股份有限公司 | Asynchronous data query method and system based on single process |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106933850A (en) | 2017-07-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106911780B (en) | Service ID generation method, device and system | |
| US8549105B1 (en) | Map tile data pre-fetching based on user activity analysis | |
| US8812031B2 (en) | Map tile data pre-fetching based on mobile device generated event analysis | |
| US8972529B1 (en) | Management of pre-fetched mapping data incorporating user-specified locations | |
| US20130282854A1 (en) | Node and method for generating shortened name robust against change in hierarchical name in content-centric network (ccn) | |
| US20160335243A1 (en) | Webpage template generating method and server | |
| CN107291874B (en) | Map point location aggregation method and device | |
| CN109167840B (en) | Task pushing method, node autonomous server and edge cache server | |
| US20140067994A1 (en) | Reducing costs related to use of networks based on pricing heterogeneity | |
| CN108021333B (en) | System, device and method for randomly reading and writing data | |
| CN112527843B (en) | Data query method, device, terminal equipment and storage medium | |
| CN105005567B (en) | Interest point query method and system | |
| CN104426838A (en) | Internet cache scheduling method and system | |
| CN109936639A (en) | A kind of service calling method and server | |
| CN110764688B (en) | Method and device for processing data | |
| CN106933850B (en) | Network data query method, device and system | |
| CN107665235B (en) | Cache processing method and device, computer equipment and storage medium | |
| CN109656592B (en) | Card management method, device, terminal and computer readable storage medium | |
| CN113779091A (en) | Information query method and device, electronic equipment and readable storage medium | |
| CN110990714B (en) | User behavior intention prediction method and device | |
| CN109815351B (en) | Information query method and related product | |
| CN111783005A (en) | Method, apparatus and system for displaying web page, computer system and medium | |
| US20190238603A1 (en) | Response caching | |
| CN113849125B (en) | CDN server disk reading method, device and system | |
| CN112003885B (en) | Content transmission apparatus and content transmission method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |