CN107798135B

CN107798135B - Paging query method and device and electronic equipment

Info

Publication number: CN107798135B
Application number: CN201711172207.7A
Authority: CN
Inventors: 刘晨曦
Original assignee: Alibaba Group Holding Ltd
Current assignee: Advanced New Technologies Co Ltd; Advantageous New Technologies Co Ltd
Priority date: 2017-11-22
Filing date: 2017-11-22
Publication date: 2020-06-16
Anticipated expiration: 2037-11-22
Also published as: CN107798135A; TWI686705B; WO2019100853A1; TW201926085A

Abstract

The embodiment of the specification provides a paging query method, a paging query device and electronic equipment, wherein a first request of paging data query initiated by a client is received; initiating a second request for a data query to each data source involved in the paged data query; merging the data returned by each data source, and sequencing the merged data according to the creation time of each data; intercepting the data of the number of the queries before, and recording a second creation time in the intercepted data; and returning the intercepted data of the query number and the recorded second creation time of each data source to the client.

Description

Paging query method and device and electronic equipment

Technical Field

The embodiment of the specification relates to the technical field of internet, in particular to a paging query method and device and electronic equipment.

Background

With the increasing of internet services, the services related to the platform are increased correspondingly. Since the service data generated by different services are different, the databases and the database types to be stored are also different. There are currently some needs for the simultaneous paging display of different service data. For these query requests, data is often queried from different data sources, and then these different service data are converted into the same type of temporary data, which can be provided to the requester after paging.

It is desirable to provide a more efficient paging query scheme.

Disclosure of Invention

The paging query method, apparatus and electronic device provided in the embodiments of this specification are used to provide a more efficient scheme for finding a service user using a discarded field.

According to an embodiment of the present specification, a paging query method is provided, and the method includes:

a client initiates a first request of paging data query to a server; the paging data query relates to at least two data sources, the first request carries a user identifier, a query number and a first creation time of each data source, and the first creation time is the creation time when the client queries the data source last time and returns the last data;

the server side initiates a second request of data query to each data source after receiving the first request initiated by the client side; the second request carries the user identification, the query number and the first creation time corresponding to the data source;

after receiving a second request initiated by the server, the data source queries data which belong to the user identification and conform to the first creation time;

the data source sorts the inquired data according to the creation time of each data and returns the data of the number inquired to the server;

the server side merges the data returned by each data source, and sorts the merged data according to the creation time of each data;

the server intercepts the data of the number of the queries before and records a second creation time in the intercepted data; the second creation moment is the creation moment when the last data is returned from the data source after the query;

the server side returns the intercepted data with the number of the inquires and the recorded second creating time of each data source to the client side;

the client receives the data returned by the server and the second creation time of each data source;

and the client updates the first creation time of each data source according to the second creation time of each data source.

initiating a first request of paging data inquiry to a server; the paging data query relates to at least two data sources, the first request carries a user identifier, a query number and a first creation time of each data source, and the first creation time is the creation time of returning the last data from the last query to the data source;

receiving data returned by the server and a second creation time of each data source;

and updating the first creation time of each data source according to the second creation time of each data source.

receiving a first request of paging data inquiry initiated by a client; the paging data query relates to at least two data sources, the first request carries a user identifier, a query number and a first creation time of each data source, and the first creation time is the creation time when the client queries the data source last time and returns the last data;

initiating a second request for a data query to each data source involved in the paged data query; the second request carries the user identification, the query number and the first creation time corresponding to the data source;

merging the data returned by each data source, and sequencing the merged data according to the creation time of each data;

intercepting the data of the number of the queries before, and recording a second creation time in the intercepted data; the second creation moment is the creation moment when the last data is returned from the data source after the query;

and returning the intercepted data of the query number and the recorded second creation time of each data source to the client.

receiving a second request of data query initiated by a server; the second request carries a user identifier, a query number and a first creation time corresponding to the data source, wherein the first creation time is the creation time when the client queries the data source last time and returns the last data;

querying data belonging to the user identification and conforming to the first creation time;

and sequencing the inquired data according to the creation time of each data, and returning the data of the inquired number to the server.

According to an embodiment of the present specification, there is provided a paging inquiry apparatus, including:

the request unit is used for initiating a first request of paging data query to the server; the paging data query relates to at least two data sources, the first request carries a user identifier, a query number and a first creation time of each data source, and the first creation time is the creation time of returning the last data from the last query to the data source;

the receiving unit is used for receiving the data returned by the server and the second creation time of each data source;

and the updating unit updates the first creation time of each data source according to the second creation time of each data source.

the receiving unit is used for receiving a first request of paging data inquiry initiated by a client; the paging data query relates to at least two data sources, the first request carries a user identifier, a query number and a first creation time of each data source, and the first creation time is the creation time when the client queries the data source last time and returns the last data;

a request unit, which initiates a second request of data query to each data source related to the paging data query; the second request carries the user identification, the query number and the first creation time corresponding to the data source;

the sorting unit is used for merging the data returned by each data source and sorting the merged data according to the creation time of each data;

the processing unit intercepts the data of the number of the queries before and records a second creation time in the intercepted data; the second creation moment is the creation moment when the last data is returned from the data source after the query;

and the return unit is used for returning the intercepted data of the query number and the recorded second creation time of each data source to the client.

the receiving unit is used for receiving a second request of data query initiated by the server; the second request carries a user identifier, a query number and a first creation time corresponding to the data source, wherein the first creation time is the creation time when the client queries the data source last time and returns the last data;

the query unit is used for querying data which belongs to the user identification and accords with the first creation time;

and the return unit is used for sequencing the inquired data according to the creation time of each data and returning the data with the number of the inquired data to the server.

According to this specification embodiment, provide an electronic equipment, include:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

In the embodiment of the present specification, by transmitting the parameter of the creation time, paging data query across multiple data sources can be implemented; and a new data table is not needed, and paging data query delay is not caused.

Drawings

FIG. 1 is a diagram of a system architecture for implementing paging queries according to an embodiment of the present disclosure;

FIG. 2 is a flowchart of a paging query method according to an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of a first request and a second request provided by an embodiment of the present disclosure;

FIG. 4 is a schematic diagram of returning queries to data as provided by an embodiment of the present description;

FIG. 5 is a flowchart of a paging query method according to an embodiment of the present disclosure;

fig. 6 is a flowchart of a method for targeting a client according to an embodiment of the present disclosure;

fig. 7 is a flowchart of a method for a server as a main body according to an embodiment of the present disclosure;

FIG. 8 is a flowchart of a method for targeting data sources according to an embodiment of the present disclosure;

FIG. 9 is a block diagram of a paging query device according to an embodiment of the present disclosure;

FIG. 10 is a block diagram of a paging query device according to an embodiment of the present disclosure;

fig. 11 is a block diagram of a paging query device according to an embodiment of the present disclosure.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.

The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present specification. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

As mentioned above, with the increase of internet services, the services involved in the platform are also increased. Since the service data generated by different services are different, the databases and the database types to be stored are also different. There are currently some needs for the simultaneous paging display of different service data. For these query requests, data is often required to be queried from different data sources, and the data in different data sources cannot coordinate to complete paging display. Therefore, in the prior art, a new data table is required, data queried in different data sources are temporarily and uniformly stored in the new data table, then operations such as sorting and screening are performed on the data in the new data table, and finally the required data is returned to the requesting party. Therefore, the paging data query is delayed due to the operations of creating a data table, storing data into the data table, and the data table during the query process.

Fig. 1 is a system architecture diagram for implementing paging query provided in the embodiment of the present application. In this embodiment, the system may include a client 11, a server 12, and a plurality of data sources 13.

The client 11 may be a terminal installed with an application, such as a mobile application (App) installed in the IOS system of apple, an application installed in the Android system of Google, or an application installed in the Windows/Windows phone system of microsoft. In conjunction with the installed application, the client 11 may communicate with the server 12, and in this embodiment, the client 11 may initiate a request for paging query to the server 12.

The server 12 may be an application server for data query, a server cluster, or a service platform constructed based on the server cluster, which is corresponding to the application in the client 11. The server 12 may query the data source 13 for data based on the request sent by the client 11, and return the queried data to the client 11.

The data source 13 may refer to a database or a database server used by a database application. The data source 13 may generally have associated data stored therein. The plurality of data sources 13 may refer to at least 2 data sources. As mentioned above, different data sources may store different data, for example, different services may correspond to different data sources, and the service data generated by each service needs to be stored in the corresponding data source.

The user inquires data in pages through the client 11, the server 12 inquires data from a corresponding data source based on a request initiated by the client 11, processes the inquired data, returns the processed data to the client 11, and the client 11 displays the data returned by the server 12.

An embodiment of a paging query method of the present disclosure is described below with reference to an example shown in fig. 2, and the method may include the following steps:

step 210: the client side sends a first request of paging data inquiry to the server side.

In this embodiment, the paged data query relates to at least two data sources, the first request carries a user identifier, a query number, and a first creation time of each data source, where the first creation time is a creation time when the client queries the data source last time and returns the last data.

The user identifier may refer to a unique identifier of a user or an account, and may include, for example, a user ID, a user account name, a mobile phone number, and the like.

The query number may include the maximum number of data pieces that can be simultaneously displayed on the client screen, or may include the number of data pieces that is set by the user.

For ease of reading and understanding, the number of queries is defined below as N; the first creation time is T; the first creation time of the different data sources may be, for example, T1, T2 … ….

It needs to be noted that, when the client initiates a first request for paging data query to the server for the first time, the first creation time of each data source carried in the first request is null.

Step 220: and the server side initiates a second request of data query to each data source after receiving the first request initiated by the client side.

After receiving the first request initiated by the client, the server may initiate second requests for data queries to the data sources according to the multiple data sources involved in the first request.

The second request carries the user identifier, the query number and the first creation time corresponding to the data source. That is to say, the server may transmit the user identifier, the number of queries, and the first creation time transmitted by the client to the corresponding data source.

In one example, as shown in FIG. 3, a client initiates a first request for a paged data query, the paged data query involving an A data source and a B data source; the first request carries a user identifier user, a query number N, a first creation time T1 of a data source A and a first creation time T2 of a data source B;

then, after receiving the first request, the server may respectively initiate a second request of data query to the a data source and the B data source:

the second request initiated to the data source A carries the user identifier user, the query number N, and the first creation time T1 of the data source A;

the second request initiated to the B data source carries the user identifier user, the query number N, and the first creation time T2 of the B data source.

Step 230: and after receiving a second request initiated by the server, the data source queries data which belong to the user identification and conform to the first creation time.

It should be noted that the data stored in the data source generally has a creation time, which is generally the time when the data is written into the data source, or the time or time stamp when the data is generated in the data source.

In this embodiment, the data meeting the first creation time specifically needs to be sorted according to paging data query. Generally, the sorting mode may include a positive order and a negative order;

1: if the order is positive, the data corresponding to the first creation time may specifically include:

data having a creation time greater than the first creation time.

The method adopts a positive sequence, the data displayed in the client is sequenced according to the sequence of the creation time, and the later data at the creation time is ranked earlier and the earlier data at the creation time is ranked later.

In the application process:

after receiving the second request initiated by the server, the data source may query data according to the parameters carried in the second request, specifically:

firstly, inquiring all data input by a user identifier according to the user identifier;

then, screening out data with the creation time larger than the first creation time from the data of the user identifier according to the first creation time; the data screened out in this way is the data required by the query.

For example, the data of a certain user identifier is as follows:

data 1, create time 2017, 10 months and 1 day (for convenience of presentation, this example is accurate only to days, and may actually be accurate to seconds, milliseconds, even microseconds, etc.);

data 2, creation time 2017, 8 month and 1 day;

data 3, creation time 2016, 10 months, 1 day;

data 4, creating time 2017, 11 month and 1 day;

data 5, creation time 2017, 5 month, 1 day;

assume that the first creation time is 2017, 9, 1;

then, the data corresponding to the first creation time should be data whose creation time is greater than 2017, 9, month, 1, i.e., data 1 and data 4.

2: if the order is the reverse order, the data conforming to the first creation time may specifically include:

data having a creation time less than or equal to the first creation time.

The method adopts a reverse order, the data displayed in the client is sorted according to the sequence of the creation time, and the earlier the data at the creation time is, the later the data at the creation time is.

In the application process:

then, screening out data with the creation time less than or equal to the first creation time from the data of the user identifier according to the first creation time; the data screened out in this way is the data required by the query.

Following the above example, the data that conforms to the first creation time should be data whose creation time is less than or equal to 2017, 9, month, 1, data 2, data 3, and data 5.

Step 240: and the data source sorts the inquired data according to the creation time of each data and returns the data of the inquired number before and after sorting to the server.

The data queried in the previous step is generally unordered, so this step needs to sort it.

As mentioned above, the sorting may specifically be according to a sorting manner of the paged data query, and if the paged data query specifies a positive order, the sorting is also the positive order; if the paged data query specifies reverse order, then the ordering here is also reverse order.

1: if the sequence is positive;

the server can arrange the inquired data in the order from late to early according to the creation time.

Taking the example in the previous step, the queried data is:

data 1, creation time 2017, 10 month and 1 day;

data 4, creating time 2017, 11 month and 1 day;

the server side sorts according to the creation time of the data 1 and the data 4, and the creation time of the data 4 is later than that of the data 1; the order after sorting is therefore: data 4 precedes and data 1 succeeds.

2: in the case of the reverse order,

the server can arrange the inquired data in the order from early to late according to the creation time.

Taking the example in the previous step, the queried data is:

data 2, creation time 2017, 8 month and 1 day;

data 3, creation time 2016, 10 months, 1 day;

data 5, creation time 2017, 5 month, 1 day;

the server side sorts according to the creation time of the data 2, the data 3 and the data 5, and the creation time of the data 3 is earliest, the creation time of the data 2 is latest, and the creation time of the data 5 is located in the middle; the order after sorting is therefore: data 3 is before, data 5 is in the middle, and data 2 is after.

After the data is sorted, the front N sorted data can be returned to the server according to the number N of queries carried in the second request. Of course, if the number of the sorted data is less than N, all the sorted data are directly returned, that is, how much data is returned when how much data is queried.

Step 250: and the server side merges the data returned by each data source and sorts the merged data according to the creation time of each data.

Since each data source may return N data, the server may receive X × N data by initiating X second requests. Similarly, although the data returned by a single data source can be considered as sorted, the data returned by a plurality of data sources is merged and becomes unordered, and therefore the server needs to sort the data.

The server side is sequenced with the data source in the same way, and if the data source is in a positive sequence, the server side is also in the positive sequence; if the data source is in the reverse order, the server is also in the reverse order, and the specific sorting process is not described herein again.

For example, the following steps are carried out:

as shown in fig. 4, both the a data source and the B data source return N data to the server; after the server merges the 2N data, it needs to sort the data.

Assuming that N is 3, the sorting mode is reverse order, and the a data source returns 3 data:

data 1, creation time 2016, 5 months, 1 day;

data 2, creation time 2016, 10 months, 1 day;

data 3, time of creation 2017, 5 month and 1 day;

b3 data returned by data source:

data 4, creation time 2016, 8, month, 1;

data 5, creation time 2017, 3, month 1;

data 6, creating time 2017, 10 month and 1 day;

the sequence after the server side is sequenced is as follows: data 1, data 4, data 2, data 5, data 3, data 6.

Step 260: and intercepting the data of the query number before the sequencing by the server side, and recording a second creation time in the intercepted data.

And the second creation time is the creation time when the last data is returned from the data source after the query.

Step 270: and the server returns the intercepted data of the query number and the recorded second creation time of each data source to the client.

After the merged data are sequenced at the server, the first N data may be intercepted, and the second creation time of the first N data may be recorded.

With continued reference to fig. 4, the number of data returned by the server to the client is N, and the number of data also carries the second creation time of each data source.

Continuing with the example in the previous step, the server side sequentially orders as follows: data 1, data 4, data 2, data 5, data 3, data 6;

since N is 3, the first 3 data are intercepted as follows: data 1, data 4, data 2;

further, since the data 2 is the last data returned by the data source a in the intercepted data, the second creation time of the data source a is the creation time T1' of the data 2, that is, 2016, 10, 1;

since the data 4 is the last data returned by the data source B in the intercepted data, the second creation time of the data source B is the creation time T2' of the data 4, that is, 2016, 8, 1;

finally, the server returns to the client including data 1, data 4, data 2, and T1 'and T2'.

It is worth mentioning that the server receives X × N data, but only intercepts the first N data and returns them to the client; while the remaining (X-1) × N data are not returned to the client. Since the remaining data is garbage data, after step 270, the method may further comprise:

and the server side empties the data left after interception.

Therefore, the utilization rate of the storage space of the server side, particularly the utilization rate of the memory space, can be improved.

Step 280: and the client receives the data returned by the server and the second creation time of each data source.

Step 290: and the client updates the first creation time of each data source according to the second creation time of each data source.

After receiving the data returned by the server and the second creation time of each data source, the client may display the data, and update the first creation time of each data source according to the second creation time of each data source, that is, assign the second creation time of each data source to the first creation time of each data source.

For example, the first creation time of the data source A is 2017, 5, month and 1; the second creation time of the received data source A is 2017, 6 and 1; then the client may update the first creation time of the a data source from 2017, month 5, day 1 to 2017, month 6, day 1.

When the user turns the page and queries the next page of data, the client may repeatedly execute the above step 210 and 290. Since the client has updated the first creation time locally, the data of the next query is the data after the data of the current query.

In this embodiment, by transferring the parameter of the creation time, paging data query across multiple data sources can be implemented; and a new data table is not needed, and paging data query delay is not caused.

On the basis of the embodiment shown in fig. 2, as shown in fig. 5, the first request further carries a first identification number of each data source; the first identification number is the identification number of the last data returned by the last time the client inquires the data source;

correspondingly, the second request also carries a first identification number corresponding to the data source;

the step 240 may specifically include:

step 241: the data source sorts the inquired data according to the creation time of each data;

step 242: under the condition that the data at the same creation time exist, the data source sorts the data at the same creation time according to the identification number of the data;

step 243: and the data source returns the data of the query number before the sequencing to the server.

After the step 250, the method may further include:

the step 251: and under the condition that the data at the same creation time exist, the server sorts the data at the same creation time according to the identification number of the data.

The step 260 may specifically include:

the server intercepts the data of the number of the queries before, and records a second creation time and a second identification number in the intercepted data; and the second identification number is the identification number of the last data returned by the data source inquired this time.

The step 270 may specifically include:

and the server returns the intercepted data of the query number and the recorded second creation time and identification number of each data source to the client.

The step 280 may specifically include:

and the client receives the data returned by the server, the second creation time and the second identification number of each data source.

The step 290 may specifically include:

step 291: the client updates the first creation time of each data source according to the second creation time of each data source;

step 292: and the client updates the first identification number of each data source according to the second identification number of each data source.

Through the embodiment, the data at the same creation time can be further sorted according to the identification number during sorting.

An embodiment of the method mainly based on the client side is described below with reference to fig. 6, and this embodiment may correspond to fig. 2:

step 310: initiating a first request of paging data inquiry to a server; the paging data query relates to at least two data sources, the first request carries a user identifier, a query number and a first creation time of each data source, and the first creation time is the creation time of returning the last data from the last query to the data source.

It is worth mentioning that when a first request of paging data query is initiated to a server for the first time, the first creation time of each data source carried in the first request is null.

Step 320: and receiving the data returned by the server and the second creation time of each data source.

Step 330: and updating the first creation time of each data source according to the second creation time of each data source.

On the basis of the embodiment shown in fig. 6, another specific embodiment may correspond to fig. 5:

the first request also carries a first identification number of each data source; the first identification number is the identification number of the last data returned by the last time the client inquires the data source;

the step 320 specifically includes:

receiving data returned by the server, a second creation time and a second identification number of each data source;

the step 330 specifically includes:

updating the first creation time of each data source according to the second creation time of each data source;

and updating the first identification number of each data source according to the second identification number of each data source.

An embodiment of a method for the present application with a server as a main component is described below with reference to fig. 7, where the embodiment may correspond to fig. 2:

step 410: receiving a first request of paging data inquiry initiated by a client; the paging data query relates to at least two data sources, the first request carries a user identifier, a query number and a first creation time of each data source, and the first creation time is the creation time when the client queries the data source last time and returns the last data.

It is worth mentioning that when the client initiates the first request of paging data query for the first time, the first creation time of each data source carried in the first request is null.

Step 420: initiating a second request for a data query to each data source involved in the paged data query; the second request carries the user identification, the query number and the first creation time corresponding to the data source;

step 430: merging the data returned by each data source, and sequencing the merged data according to the creation time of each data;

step 440: intercepting the data of the number of the queries before, and recording a second creation time in the intercepted data; and the second creation time is the creation time when the last data is returned from the data source in the query.

It is worth mentioning that after the step 440, the method may further include:

and the server side empties the data left after interception.

Step 450: and returning the intercepted data of the query number and the recorded second creation time of each data source to the client.

On the basis of the embodiment shown in fig. 7, another specific embodiment may correspond to fig. 5:

the first request also carries a first identification number of each data source, wherein the first identification number is an identification number of the last data returned by the last data source inquired by the client;

the second request also carries a first identification number corresponding to the data source;

after the step 430, the method may further include:

under the condition that the data at the same creation time exist, sorting the data at the same creation time according to the identification number of the data;

the step 440 may specifically include:

intercepting the data of the number of the queries before, and recording a second creation time and a second identification number in the intercepted data; the second identification number is the identification number of the last data returned by the data source after the data source is inquired at this time;

the step 450 may specifically include:

and returning the intercepted data of the query number, the recorded second creating time of each data source and the second identification number to the client.

An embodiment of the method for data source targeting according to the present application is described below with reference to fig. 8, and this embodiment may correspond to fig. 2:

step 510: receiving a second request of data query initiated by a server; the second request carries a user identifier, a query number and a first creation time corresponding to the data source, wherein the first creation time is the creation time when the client queries the data source last time and returns the last data;

step 520: querying data belonging to the user identification and conforming to the first creation time;

step 530: and sequencing the inquired data according to the creation time of each data, and returning the data of the inquired number to the server.

On the basis of the embodiment shown in fig. 8, another specific embodiment may correspond to fig. 5:

the step 530 specifically includes:

sequencing the inquired data according to the creation time of each data;

and returning the data of the query number after the sorting to the server.

Corresponding to the foregoing embodiment of the paging query method shown in fig. 6, the present specification further provides an embodiment of a paging query apparatus. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor of the device where the software implementation is located as a logical means. In terms of hardware, a hardware structure of the device in which the paging query apparatus of this specification is located may include a processor, a network interface, a memory, and a nonvolatile memory, and the device in which the apparatus is located in the embodiment may also include other hardware according to the actual function of the paging query, which is not described in detail herein.

Referring to fig. 9, a block diagram of a paging query apparatus according to an embodiment of the present disclosure is provided, where the apparatus includes:

a request unit 610, configured to initiate a first request for paging data query to a server; the paging data query relates to at least two data sources, the first request carries a user identifier, a query number and a first creation time of each data source, and the first creation time is the creation time of returning the last data from the last query to the data source;

a receiving unit 620, configured to receive the data returned by the server and the second creation time of each data source;

the updating unit 630 updates the first creation time of each data source according to the second creation time of each data source.

In an alternative embodiment:

when a first request of paging data inquiry is initiated to a server for the first time, the first creation time of each data source carried in the first request is null.

In an alternative embodiment:

the receiving unit 620 specifically includes:

the updating unit 630 specifically includes:

Corresponding to the foregoing embodiment of the paging query method in fig. 7, the present specification further provides an embodiment of a paging query apparatus. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor of the device where the software implementation is located as a logical means. In terms of hardware, a hardware structure of the device in which the paging query apparatus of this specification is located may include a processor, a network interface, a memory, and a nonvolatile memory, and the device in which the apparatus is located in the embodiment may also include other hardware according to the actual function of the paging query, which is not described in detail herein.

Referring to fig. 10, a block diagram of a paging query apparatus according to an embodiment of the present disclosure is provided, where the apparatus includes:

a receiving unit 710, configured to receive a first request for paging data query initiated by a client; the paging data query relates to at least two data sources, the first request carries a user identifier, a query number and a first creation time of each data source, and the first creation time is the creation time when the client queries the data source last time and returns the last data;

a request unit 720, which initiates a second request of data query to each data source involved in the paged data query; the second request carries the user identification, the query number and the first creation time corresponding to the data source;

the sorting unit 730, which merges the data returned by each data source, and sorts the merged data according to the creation time of each data;

the processing unit 740 is configured to intercept the data of the number of queries before, and record a second creation time in the intercepted data; the second creation moment is the creation moment when the last data is returned from the data source after the query;

and a returning unit 750, which returns the intercepted data of the number of queries and the recorded second creation time of each data source to the client.

In an alternative embodiment:

when the client side initiates a first request of paging data inquiry for the first time, the first creation time of each data source carried in the first request is null.

In an alternative embodiment:

after the sorting unit 730, the apparatus further includes:

the processing unit 740 specifically includes:

the return unit 750 specifically includes:

Corresponding to the foregoing embodiment of the paging query method in fig. 8, the present specification further provides an embodiment of a paging query apparatus. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor of the device where the software implementation is located as a logical means. In terms of hardware, a hardware structure of the device in which the paging query apparatus of this specification is located may include a processor, a network interface, a memory, and a nonvolatile memory, and the device in which the apparatus is located in the embodiment may also include other hardware according to the actual function of the paging query, which is not described in detail herein.

Referring to fig. 11, a block diagram of a paging query apparatus according to an embodiment of the present disclosure is provided, where the apparatus includes:

a receiving unit 810, which receives a second request of data query initiated by the server; the second request carries a user identifier, a query number and a first creation time corresponding to the data source, wherein the first creation time is the creation time when the client queries the data source last time and returns the last data;

a query unit 820 configured to query data belonging to the user identifier and corresponding to the first creation time;

a returning unit 830, which sorts the queried data according to the creation time of each data, and returns the queried data to the server

In an alternative embodiment:

the returning unit 830 specifically includes:

sequencing the inquired data according to the creation time of each data;

and returning the data of the query number after the sorting to the server.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.

Fig. 9 above describes the internal functional modules and the structural schematic of the paging inquiry apparatus, and the substantial execution subject may be an electronic device, including:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

Optionally, when a first request for paging data query is initiated to the server for the first time, the first creation time of each data source carried in the first request is null.

Optionally, the first request further carries a first identification number of each data source, where the first identification number is an identification number of the last data returned by the last data source queried by the client;

the receiving the data returned by the server and the second creation time of each data source specifically includes:

the updating the first creation time of each data source according to the second creation time of each data source specifically includes:

Fig. 10 above describes the internal functional modules and the structural schematic of the paging inquiry apparatus, and the substantial execution subject may be an electronic device, including:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

Optionally, when the client initiates a first request for paging data query for the first time, the first creation time of each data source carried in the first request is null.

after the merging the data returned by each data source and sorting the merged data according to the creation time of each data, the method further includes:

the querying the number of data before the intercepting and recording a second creation time in the intercepted data specifically include:

the returning the intercepted data of the number of queries and the recorded second creation time of each data source to the client specifically includes:

Fig. 11 above describes the internal functional modules and the structural schematic of the paging inquiry apparatus, and the substantial execution subject may be an electronic device, including:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

Optionally, the second request further carries a first identification number corresponding to the data source;

the sorting the queried data according to the creation time of each data and returning the data of the number queried to the server specifically includes:

sequencing the inquired data according to the creation time of each data;

and returning the data of the query number after the sorting to the server.

In the above embodiments of the electronic device, it should be understood that the Processor may be a Central Processing Unit (CPU), other general-purpose processors, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), etc. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, and the aforementioned memory may be a read-only memory (ROM), a Random Access Memory (RAM), a flash memory, a hard disk, or a solid state disk. The steps of a method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the embodiment of the electronic device, since it is substantially similar to the embodiment of the method, the description is simple, and for the relevant points, reference may be made to part of the description of the embodiment of the method.

Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This specification is intended to cover any variations, uses, or adaptations of the specification following, in general, the principles of the specification and including such departures from the present disclosure as come within known or customary practice within the art to which the specification pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the specification being indicated by the following claims.

It will be understood that the present description is not limited to the precise arrangements described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.

Claims

1. A method of paging queries, the method comprising:

a client initiates a first request of paging data query to a server; the paging data query relates to at least two data sources with different service data, the first request carries a user identifier, a query number and a first creation time of each data source, and the first creation time is the creation time when the client queries the data source last time and returns the last data;

2. The method according to claim 1, wherein when the client initiates a first request for paging data query to the server for the first time, a first creation time of each data source carried in the first request is null.

3. The method of claim 1, after the server returns the intercepted number of data of the queries and the recorded second creation time of each data source to the client, the method further comprising:

and the server side empties the data left after interception.

4. The method according to claim 2, wherein the first request further carries a first identification number of each data source, and the first identification number is an identification number of the last data returned by the last query of the client to the data source;

the data source sorts the queried data according to the creation time of each data, and returns the data of the number queried to the server, and the method specifically includes:

the data source sorts the inquired data according to the creation time of each data;

under the condition that the data at the same creation time exist, the data source sorts the data at the same creation time according to the identification number of the data;

the data source returns the data of the query number before the sorting to the server;

after the server merges the data returned by each data source and sorts the merged data according to the creation time of each data, the method further includes:

under the condition that the data at the same creation time exist, the server sorts the data at the same creation time according to the identification number of the data;

the server intercepts the data of the number of queries before and records a second creation time in the intercepted data, and specifically includes:

the server intercepts the data of the number of the queries before, and records a second creation time and a second identification number in the intercepted data; the second identification number is the identification number of the last data returned by the data source after the data source is inquired at this time;

the step of returning, by the server, the intercepted data of the query number and the recorded second creation time of each data source to the client, specifically includes:

the server side returns the intercepted data of the query number, the recorded second creating time of each data source and the second identification number to the client side;

the receiving, by the client, the data returned by the server and the second creation time of each data source specifically includes:

the client receives the data returned by the server, the second creation time and the second identification number of each data source;

the updating, by the client, the first creation time of each data source according to the second creation time of each data source specifically includes:

the client updates the first creation time of each data source according to the second creation time of each data source;

and the client updates the first identification number of each data source according to the second identification number of each data source.

5. A method of paging queries, the method comprising:

initiating a first request of paging data inquiry to a server; the paging data query relates to at least two data sources with different service data, the first request carries a user identifier, a query number and a first creation time of each data source, and the first creation time is the creation time from the last query to the last data return of the data source;

6. The method according to claim 5, wherein when a first request for paging data query is initiated to a server for the first time, the first creation time of each data source carried in the first request is null.

7. The method according to claim 5, wherein the first request further carries a first identification number of each data source, and the first identification number is an identification number of the last data returned by the last query of the client to the data source;

8. A method of paging queries, the method comprising:

receiving a first request of paging data inquiry initiated by a client; the paging data query relates to at least two data sources with different service data, the first request carries a user identifier, a query number and a first creation time of each data source, and the first creation time is the creation time when the client queries the data source last time and returns the last data;

9. The method of claim 8, wherein when the client first initiates a first request for paging data query, a first creation time of each data source carried in the first request is null.

10. The method according to claim 8, wherein the first request further carries a first identification number of each data source, and the first identification number is an identification number of the last data returned by the last query of the client to the data source;

11. A method of paging queries, the method comprising:

receiving a second request which is initiated by the server and is used for carrying out data query on at least two data sources with different service data; the second request carries a user identifier, a query number and a first creation time corresponding to the data source, wherein the first creation time is the creation time when the client queries the data source last time and returns the last data;

12. The method according to claim 11, wherein the second request further carries a first identification number corresponding to the data source;

sequencing the inquired data according to the creation time of each data;

and returning the data of the query number after the sorting to the server.

13. A paging inquiry apparatus, the apparatus comprising:

the request unit is used for initiating a first request of paging data query to the server; the paging data query relates to at least two data sources with different service data, the first request carries a user identifier, a query number and a first creation time of each data source, and the first creation time is the creation time from the last query to the last data return of the data source;

14. A paging inquiry apparatus, the apparatus comprising:

the receiving unit is used for receiving a first request of paging data inquiry initiated by a client; the paging data query relates to at least two data sources with different service data, the first request carries a user identifier, a query number and a first creation time of each data source, and the first creation time is the creation time when the client queries the data source last time and returns the last data;

15. A paging inquiry apparatus, the apparatus comprising:

the receiving unit is used for receiving a second request which is initiated by the server and used for carrying out data query on at least two data sources with different service data; the second request carries a user identifier, a query number and a first creation time corresponding to the data source, wherein the first creation time is the creation time when the client queries the data source last time and returns the last data;

16. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

17. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

18. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to: