CN111385335B - Data request processing method, device, equipment and storage medium - Google Patents

Abstract

The invention discloses a method, a device, equipment and a storage medium for processing a data request, wherein the method comprises the following steps: acquiring a data original request, wherein the data original request comprises a service identifier, a data identifier set and a data domain identifier set; if the service identifier is a non-specific service identifier, the data identifier set is covered by the data identifier set of the sent network request, and the data domain identifier set corresponding to the covered data identifier is covered by the data domain identifier set corresponding to the covered data identifier in the sent network request, waiting for request response data of the sent network request; otherwise, generating a network request according to the data identifier set and the data domain identifier set of the original data request, and sending the network request. By using the method, the effective combination of different data original requests in the request terminal can be realized, thereby effectively reducing the request quantity of the network requests really sent to the response terminal, and further saving the network resources, the data flow and the calculation resources of the request terminal.

Description

Data request processing method, device, equipment and storage medium

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for processing a data request.

Background

At present, when a request terminal sends a network request to a response terminal, the response terminal feeds back a corresponding request response for each network request in principle, that is, a service layer of the request terminal provides request content according to requirements, the request content is sent to the response terminal by the network layer, and the response terminal feeds back the response content to the service layer of the request terminal.

However, when the network resources, data traffic and computing power of the requesting terminal are limited, it is not favorable for normal transmission of the network request to the responding terminal and normal reception of the relevant reply content. In order to solve the above problems, the conventional method is to perform some cache merging processing on the network request before sending the network request, but this processing method can only implement merging processing on network requests with completely the same content and format, and cannot implement effective merging of different network requests in the requesting terminal.

Disclosure of Invention

In view of this, embodiments of the present invention provide a method, an apparatus, a device, and a storage medium for processing a data request, so as to reduce the actual number of network requests sent from a requesting terminal to a responding terminal.

In a first aspect, an embodiment of the present invention provides a method for processing a data request, including:

acquiring a data original request, wherein the data original request comprises a service identifier, a data identifier set and a data domain identifier set;

if the service identifier is a non-special service identifier, the data identifier set is covered by the data identifier set of the sent network request, and the data domain identifier set corresponding to the covered data identifier is covered by the data domain identifier set corresponding to the covered data identifier in the sent network request, waiting for request response data of the sent network request;

otherwise, generating a network request according to the data identifier set and the data domain identifier set of the original data request, and sending the network request, wherein the network request comprises an associated identifier for identifying the original data request.

Further, generating a network request according to the data identifier set and the data domain identifier set of the original data request, and sending an execution condition of the network request includes: the service identifier is a special service identifier; or, the service identifier is a non-specific service identifier, and the data identifier set is not covered by the data identifier set requested by the sent network; or, the service identifier is a non-special service identifier, the data identifier set is covered by the data identifier set of the sent network request, and the data domain identifier set is not covered by the data domain identifier set corresponding to the data identifier in the sent network request.

Further, the sent network request is stored in a sent network request cache table.

Further, after sending the network request, the method further includes: and adding the network request into a sent network request cache table.

Further, the method further comprises: and after receiving the request response data, deleting the sent network request corresponding to the request response data from the sent network request cache table.

Further, the method also includes: upon receiving the request response data, based on at least one of the following parameters: the method comprises the steps of requesting a network request corresponding to response data, an original data request, a sent network request cache table and the waiting time of the original data request, and determining target response data corresponding to the original data request.

Further, based on at least one of the following parameters: the method comprises the following steps of requesting a network request corresponding to response data, an original data request, a sent network request cache table and the waiting duration of the original data request, and determining target response data corresponding to the original data request, wherein the target response data comprises the following steps:

and if the service identifier of the original data request is a special service identifier and the identifier object of the associated identifier contained in the target network request is the original data request, using the request response data as the target response data of the original data request, and otherwise, keeping the original data request in a request response data waiting state.

Further, the method comprises the following steps of: the method comprises the following steps of requesting a network request corresponding to response data, an original data request, a sent network request cache table and the waiting duration of the original data request, and determining target response data corresponding to the original data request, wherein the target response data comprises the following steps:

if the service identifier of the original data request is a non-special service identifier and the data domain identifier set of the network request corresponding to the request response data completely covers the data domain identifier set of the original data request, extracting associated response data corresponding to the target data identifier from the request response data and correspondingly adding the target data identifier and the associated response data to a set data mapping table when the target data identifier contained in the data domain identifier set of the network request corresponding to the request response data exists in the data identifier set of the original data request;

if the data mapping table contains all data identifications of the data identification set in the data original request, using associated response data corresponding to each target data identification in the data mapping table as target response data of the data original request; otherwise, the original data request is kept in a request response data waiting state.

Further, based on at least one of the following parameters: the method for determining the target response data corresponding to the original data request comprises the following steps of requesting a network request corresponding to the response data, an original data request, a sent network request cache table and the waiting time of the original data request, wherein the target response data corresponding to the original data request comprises the following steps:

and if the sent network request cache table is empty and the original data request is still in a state of waiting for request response data, determining that target response data corresponding to the original data request is a request response failure.

Further, based on at least one of the following parameters: the method comprises the following steps of requesting a network request corresponding to response data, an original data request, a sent network request cache table and the waiting duration of the original data request, and determining target response data corresponding to the original data request, wherein the target response data comprises the following steps:

and if the original data request is still in a state of waiting for request response data and the waiting time of the original data request exceeds a set time, determining that the target response data corresponding to the original data request is request response overtime.

In a second aspect, an embodiment of the present invention provides a device for processing a data request, including:

the system comprises an original request acquisition module, a data domain identification acquisition module and a data domain identification acquisition module, wherein the original request acquisition module is used for acquiring an original data request which comprises a service identification, a data identification set and a data domain identification set;

a processing execution module, configured to wait for request response data of the sent network request when the service identifier is a non-special service identifier, the data identifier set is covered by the data identifier set of the sent network request, and the data domain identifier set corresponding to the covered data identifier is covered by the data domain identifier set corresponding to the covered data identifier in the sent network request; otherwise, generating a network request according to the data identifier set and the data domain identifier set of the original data request, and sending the network request, wherein the network request comprises an associated identifier for identifying the original data request.

In a third aspect, an embodiment of the present invention provides a computer device, including:

one or more processors;

storage means for storing one or more programs;

the one or more programs are executed by the one or more processors, so that the one or more processors implement the method for processing the data request provided by the embodiment of the first aspect of the present invention.

In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method for processing a data request provided in the embodiment of the first aspect of the present invention.

After the data original request is obtained, if the service identifier of the data original request is a non-specific service identifier, the data identifier set is covered by the data identifier set of the sent network request, and the data domain identifier set corresponding to the covered data identifier is covered by the data domain identifier set corresponding to the covered data identifier in the sent network request, waiting for the request response data of the sent network request; otherwise, generating a network request according to the data identifier set and the data domain identifier set of the original data request, and sending the network request, wherein the network request comprises the associated identifier for identifying the original data request. By using the method, the data information contained in the original data request and the data information contained in the sent network request can be compared and analyzed before the network request which can be sent is generated, and the new network request which corresponds to the original data request and can be sent can be determined according to the analysis result, or the request response data of the sent network request can be directly waited, thereby realizing the effective combination of different original data requests in the request terminal, effectively reducing the request quantity of the network request which is really sent to the response terminal, and further saving the network resources, the data flow and the calculation resources of the request terminal.

Drawings

Fig. 1 is a schematic flowchart illustrating a method for processing a data request according to an embodiment of the present invention;

fig. 2a is a schematic flowchart illustrating a processing method of a data request according to a second embodiment of the present invention;

fig. 2b is a flowchart illustrating an implementation of determining target response data of an original request of data in a data request processing method according to a second embodiment of the present invention;

fig. 3a is a schematic block diagram illustrating a structure of a data request processing apparatus according to a third embodiment of the present invention;

fig. 3b is an interaction diagram illustrating a request terminal and a response terminal configured with a processing device according to a third embodiment of the present invention to implement request interaction;

FIG. 3c provides a connection diagram of the cell structure of the process execution module and the response data determination module;

fig. 4 shows a schematic hardware structure diagram of a computer device according to a fourth embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not to be construed as limiting the invention. It should be further noted that, for convenience of description, only a part, not all of the structure or composition related to the present invention is shown in the drawings.

Example one

Fig. 1 is a flowchart illustrating a method for processing a data request according to an embodiment of the present invention, where the method is applicable to processing request sending and response receiving of an original data request, and the method can be executed by a data request processing apparatus, where the apparatus can be implemented by software and/or hardware and is generally integrated on a computer device.

It should be noted that an execution main body of the processing method for a data request provided in this embodiment may be a computer device serving as a request terminal in data information interaction, where the computer device may include: mobile terminals, tablet computers, desktop computers, and the like.

As shown in fig. 1, a method for processing a data request according to an embodiment of the present invention specifically includes the following operations:

s101, acquiring an original data request.

In this embodiment, the original data request may be specifically understood as a data request initially generated when a service module performs data interaction, and the service module may specifically refer to a functional application module installed on a request terminal as an execution subject. The step can obtain the original data request generated by each service module.

In this embodiment, the data information included in the data original request specifically includes a service identifier, a data identifier set, and a data domain identifier set. Specifically, the service identifier is used to identify whether the original data request generated by the service module is a special service, the data identifier set specifically includes data identifiers required by the service module for data interaction, and each data identifier in the data identifier set corresponds to a data domain identifier set, where the data domain identifier set specifically includes data domain identifiers of data information required by the corresponding data identifier.

Exemplarily, table 1 shows main data content of data information included in the original data request, and as shown in table 1, the original data request specifically includes a data identifier set, a data domain identifier set, request generation time, a service identifier, and a sub data table for storing response data corresponding to the original data request.

Table 1:

specifically, as can be seen from table 1, each data identifier in the data identifier set of the data original request is represented in a key form, and the data type of the data identifier in the data original request exists in a { key } form; each data identifier has a corresponding data domain identifier set, and the data type of each data domain identifier set exists in a { filtered } form; the request generation time may be specifically represented by a system time type, and the timeout judgment for subsequent request waiting may specifically be represented by a boolean type; the sub data table may be specifically represented in a form of a mapping table, and may be considered to include a part of data identifiers or all data identifiers determined from request response data returned by the server and response data corresponding to the data identifiers.

After acquiring the original data request, the present embodiment may compare and analyze data information (a service identifier, a data identifier set, and a data domain identifier set) included in the original data request through the following steps, thereby determining whether to generate a new transmittable network request for the original data request, or to directly wait for request response data fed back by the transmitted network request.

S102, judging whether the service identification of the original data request is a non-special service identification, if so, executing S103; if not, go to step S106.

Specifically, in this step, the service identifier of the original data request may be determined first to determine whether the service identifier is a non-special service identifier, and if so, it may be considered that the original data request does not need to generate an independent network request that can be sent, and S103 may be executed subsequently; if not, the service corresponding to the original request of the data is considered as a special service, a new transmittable network request needs to be generated, and then S106 is executed.

S103, judging whether the data identifier set of the original data request is covered by the data identifier set of the sent network request, if so, executing S104; if not, go to step S106.

In this embodiment, the sent network request may specifically refer to a network request that can be sent, which is sent to the responding terminal and generated based on a previous data original request. Further, the sent network request may be stored in a sent network request cache table in advance.

Specifically, when the determination at S102 is yes, it may be further determined based on this step whether the data identifier set of the data original request is covered by the data identifier set of the sent network request, if so, S104 may be continuously performed, otherwise, it may be considered that S106 needs to be performed to generate a new transmittable network request for the data original request. It should be noted that, the data identifier set of the data original request is covered by the data identifier set of the sent network request, which is understood that each data identifier in the data identifier set of the data original request is included in the data identifier set of the sent network request.

S104, judging whether a data domain identifier set corresponding to the covered data identifier in the original data request is covered by a data domain identifier set corresponding to the covered data identifier in the sent network request or not, if so, executing S105; if not, go to step S106.

Specifically, when each data identifier in the data identifier set of the original data request is covered by the sent network request, it may be determined which data identifier set of the sent network request covers each data identifier, or it may also be determined which data identifier set of the covered data identifier corresponds to the sent network request, so that this step may determine whether the data domain identifier set corresponding to the covered data identifier in the original data request is covered by the data domain identifier set corresponding to the covered data identifier set in the sent network request, if so, it is considered that the response data information required by the original data request may be obtained from the response data of the sent network request, and thus S105 may be performed, if not, it is considered that a transmittable network request needs to be newly generated for the original data request, so that the response data information required by the original data request is obtained from the sent network request.

S105, waiting for the request response data of the sent network request.

When the data information of the original request of data satisfies the above-mentioned determinations of S102 to S104, the request response data of the sent network request may be waited based on this step.

S106, generating a network request according to the data identification set and the data domain identification set of the data original request, and sending the network request.

When the data information of the original data request does not satisfy the determination in S102 to S104, a new network request that can be sent may be generated for the original data request based on this step, specifically, the network request specifically carries a data identifier set included in the original data request and a data domain identifier set corresponding to each data identifier in the data identifier set, and in addition, the network request further includes an association identifier that identifies the original data request.

Illustratively, table 2 shows the main data content of the data information included in the transmittable network request, as shown in table 2, the transmittable network request specifically includes a data identifier set, a data domain identifier set, and an association identifier of the original request of the associated data.

Table 2:

specifically, as can be seen from table 2, the transmittable network request specifically includes the data identifier set, the data domain identifier set, and the associated identifier of the associated data original request, and it is also known that, in the network request, the data type of the data identifier set exists in a { key } form, and each data identifier has a corresponding data domain identifier set, and the data type of each data domain identifier set also exists in a { filled } form; the association identifier is used for identifying a data original request associated with the network request, and may specifically be represented by an ID number of the data original request.

The data identifier set and the data domain identifier set contained in the original data request and the data identifier set and the data domain identifier set contained in the sent network request can be compared and analyzed before the network request which can be sent is generated, a new network request which corresponds to the original data request and can be sent can be determined according to the analysis result, or request response data of the sent network request can be directly waited, therefore, effective combination of different original data requests in a request terminal can be realized, the request quantity of the network requests which are really sent to a response terminal is effectively reduced, and network resources, data flow and calculation resources of the request terminal are further saved.

In an optional embodiment of the first embodiment, for the method for processing a data request provided in this embodiment, after sending the network request, the method further includes: and adding the network request into a sent network request cache table.

It can be understood that, after the network request of the data original request is generated and sent to the response terminal in this embodiment, the network request may be considered to be a sent network request, and therefore, the network request may be added to the sent network request cache table as a new sent network request, so as to be a comparison object for subsequently obtaining the data original request.

In addition, it should be noted that the method for processing a data request provided in this embodiment is applicable to all original data requests, and therefore, there may be a case where an original request for currently obtained data does not wait for required response data, and then a new original data request that needs to be processed is obtained, so that this embodiment considers setting an original request cache table for the original data request that does not obtain required response data in the cache processing, and also stores a request generation time of each original data request in the original request cache table for determining a waiting time for the corresponding original data request to wait for response data.

Example two

Fig. 2a is a schematic flow chart illustrating a data request processing method according to a second embodiment of the present invention, where the second embodiment of the present invention is optimized based on the above-mentioned embodiments, and in this embodiment, further optimization is added by: upon receiving the request response data, based on at least one of the following parameters: the method comprises the steps of requesting a network request corresponding to response data, a data original request, a sent network request cache table and the waiting duration of the data original request, and determining target response data corresponding to the data original request.

Further, in this embodiment, the method further includes: and after receiving the request response data, deleting the sent network request corresponding to the request response data from the sent network request cache table.

As shown in fig. 2a, a method for processing a data request according to a second embodiment of the present invention specifically includes the following operations:

s201, acquiring and storing the original data request.

Illustratively, the data original request generated by the service module may be obtained, and the obtained data original request includes a service identifier, a data identifier set, and a data domain identifier set corresponding to data identifiers in the data identifier set. Meanwhile, the embodiment can cache the acquired data original request into a preset original request cache table.

S202, judging whether the service identifier of the original request of the data is a non-special service identifier, if so, executing S203; if not, go to S206.

S203, judging whether the data identification set of the original data request is covered by the data identification set of the sent network request, if so, executing S204; if not, go to S206.

S204, judging whether a data domain identifier set corresponding to the covered data identifier in the original data request is covered by a data domain identifier set corresponding to the covered data identifier in the sent network request, if so, executing S205; if not, go to S206.

For example, by comparing and analyzing the data information included in the data original request and the data information included in the sent network request in S202 to S204, it can be determined whether S205 needs to be executed to wait for the request response data of the sent network request to obtain the response data of the data original request, or S206 is executed to generate a new transmittable network request for the data original request to obtain the required request response data.

S205, waiting for the request response data of the sent network request.

S206, generating a network request according to the data identifier set and the data domain identifier set of the original data request, sending the network request, and adding the network request into a sent network request cache table.

It can be understood that, in the present embodiment, the generation of the new network request for the data original request includes the association identifier identifying the data original request, and after the network request is sent to the response terminal, the network request may be added to the sent network request cache list as a new sent network request.

And S207, after receiving the request response data, deleting the sent network request corresponding to the request response data from the sent network request cache table.

In this embodiment, the request terminal as the execution subject may also continuously receive the request response data sent by the response terminal, and it can be known that, according to the received request response data, which sent network request the request response data specifically corresponds to may be determined, and after receiving the request response data of a certain sent network request, it may be considered that the request response data of the sent network request is no longer used as a reference target of a subsequent original request for newly obtaining data, so that the sent network request may be deleted from the sent network request cache table.

S208, according to at least one of the following parameters: the method comprises the steps of requesting a network request corresponding to response data, a data original request, a sent network request cache table and the waiting duration of the data original request, and determining target response data corresponding to the data original request.

In this embodiment, after receiving the request response data, it is necessary to analyze which data original requests can refer to the request response data to determine the response data required by the data original requests themselves. In this step, after the request response data is received, the target response data of the original data request may be determined according to the network request, the original data request, the sent network request cache table corresponding to the request response data, and the waiting duration of the original data request.

It should be noted that, in this embodiment, the determination operation of the target response data may be performed on each data original request in the original request cache table based on this step, and therefore, the data original request in this step may specifically be any data original request existing in the original request cache table.

Specifically, in the step of determining the target response data corresponding to the original data request, the data information of the original data request and the data information of the network request corresponding to the request response data may be compared and analyzed, so that the target response data corresponding to the original data request under different conditions may be determined according to different comparison and analysis results. For example, the service identifier of the data original request may be a special service identifier, in which case, the target response data should be the request response data that carries the association identifier and is exactly the request response data corresponding to the network request identifying the data original request; for another example, when the service identifier of the original data request is a non-specific service identifier, and both the data identifier set of the original data request and the data domain identifier set corresponding to each data identifier request the network request coverage of the response data, the target response data thereof may be extracted from the request response data of the covered network request; for another example, the network request requesting response data currently received does not satisfy the above condition of the original request of data, and when the cache table of the sent network request is empty again, it may be considered that the acquisition of response data of the original request of data fails, or when the waiting time of the original request of data exceeds the set time threshold, it may be considered that the acquisition of response data of the original request of data is overtime, where the acquisition of response data fails or the acquisition of response data is overtime may also be used as the target response data of the original request of data.

Further, fig. 2b shows a flowchart of an implementation of determining target response data of an original request of data in the data request processing method according to the second embodiment of the present invention. In this embodiment, through the implementation flowchart shown in fig. 2b, the process of determining the target response data may be better described, and specifically, the implementation process of the original request for the target response data shown in fig. 2b specifically includes the following operations:

s281, determining the target network request corresponding to the received request response data.

The step specifically determines a target network request corresponding to the received request response data, and may determine which sent network request the request response data specifically corresponds to through a request identifier included in the received request response data, and may mark the corresponding sent network request as the target network request.

In this embodiment, the target network request corresponding to the request response data is determined based on this step, and the target response data of the original request of the data may be further determined based on the following determination operations.

S282, judging whether the service identification of the data original request is a special service identification, if so, executing S283; if not, go to S285.

Specifically, in this step, it may be determined whether the service identifier of the data original request is a special service identifier, and if the service identifier is the special service identifier, the service corresponding to the data original request may be considered as a special service, and there is an independent sent network request that is generated specifically. In this step, S283 may be executed if it is determined as the special service identifier, and S285 may be executed if it is determined as the non-special service identifier.

S283, determining whether the identification object of the association identifier included in the target network request is the data original request, if yes, executing S284; if not, then S2810 is executed.

Specifically, after determining that the original data request is the special service identifier as described above in S282, an identifier object of the association identifier included in the target network request may be further determined based on this step, so as to determine whether the identifier object is the original data request. It can be known that the network request sent to the response terminal has the associated identifier for identifying the associated data original object, and if it is determined that the identifier object of the associated identifier included in the target network request is the data original request, S284 may be executed; otherwise, S2810 may be performed.

And S284, taking the request response data as target response data of the original data request.

Specifically, when the above-described determinations of S282 and S283 are satisfied, the operation of this step may be performed, and the target response data of the original request for data is determined to be the received request response data.

S285, judging whether the data domain identifier set requested by the target network completely covers the data domain identifier set requested by the original data, if so, executing S286; if not, then S2810 is executed.

Specifically, when the service identifier of the original request of data is determined as the non-special service identifier in S282, it may be further determined whether the set of data domain identifiers requested by the target network completely covers the set of data domain identifiers requested by the original request of data based on this step, and when the set of data domain identifiers completely covers, S286 is executed, otherwise, S2810 is executed.

It can be known that the target network request includes at least one data field identifier set, and each data field identifier set corresponds to a data identifier in the data identifier set included in the target network request. Therefore, the step can traverse each data domain identification set in the target network request to determine whether all data domain identification sets in the original data request can be completely covered.

S286, determining whether a target data identifier included in the data identifier set requested by the target network exists in the data identifier set requested by the data source, if yes, executing S287; if not, then S2810 is executed.

Specifically, after the above S283 determines that the data field identifier set of the original data request is completely covered, it may be determined which data field identifier set of the original data request is covered by which data field identifier in the target network request, and then it may be determined which target data field identifier set of the target network request covers the data field identifier set of the original data request, and it may determine corresponding standard data identifiers of the target data field identifier set in the data identifier set of the target network request.

And S287, extracting associated response data corresponding to the target data identifier from the request response data, and correspondingly adding the target data identifier and the associated response data into a set data mapping table.

Specifically, in this step, if it is determined in S286, the relevant response data corresponding to the target data identifier may be extracted from the request response data requested by the target network, and the target data identifier and the relevant response data may be added to a set data mapping table, where the data mapping table corresponds to a mapping table set for the original request of the data and includes data information of the relevant response data associated with the target data identifier.

S288, determining whether the data mapping table includes all the data identifiers of the data identifier set in the data original request, if yes, executing S289; if not, execute S2810.

Specifically, after the target data id and the association response data are added to the set data mapping table based on S287, the determination in this step may be performed, and if the determination is true, S289 is performed, or if the determination is false, S2810 is performed.

S289, using the associated response data corresponding to each target data identification in the data mapping table as the target response data of the data original request.

Specifically, the data mapping table includes all data identifiers of the data identifier set in the data original request, and it can be considered that all data information required by the data original request has been obtained based on each request response data received in the past, so that the associated response data corresponding to each target data identifier in the data mapping table can be used as the target response data of the data original request.

S2810, keeping the original data request in a request response data waiting state, and executing S2811 or S2813.

Specifically, when the determination in S283 to S288 is no, the operation of the step may be performed, that is, when it is determined based on the determination that the target response data of the original request of the data cannot be determined based on the currently received request response data, the operation of the step may be performed, and the original request of the data is still maintained in the request response data waiting state.

S2811, judging whether a sent network request cache table is empty, if so, executing S2812; if not, the process returns to the step S281.

Specifically, after it is determined that the original request of the data is still in the request response data waiting state, it may be further determined whether the current sent network request cache table is empty based on this step, and if the current sent network request cache table is empty, it may be considered that there is no receivable request response data in the subsequent process, and then S2812 may be executed; if not, it may be considered that there is receivable request response data subsequently, and then it may return to S281, and after receiving new request response data, start a new round of determination operation for target response data.

S2812, determining that the target response data corresponding to the original data request is a request response failure.

Specifically, when there is no receivable request response data subsequently, it may be considered that the target response data corresponding to the original request of the data is a request response failure. It will be appreciated that this situation is generally caused by the fact that there is a referenceable sent network request for the original request of data, but the request response data of the referenceable sent network request cannot be normally received (fails to be received) for some reasons (such as network bandwidth congestion or excessive resource occupation).

S2813, judging whether the waiting time of the original data request exceeds a set time, if so, executing S2814; if not, the process returns to step S282.

Specifically, after it is determined that the data original request is still in the request response data waiting state, it may be further determined whether the waiting time of the data original request exceeds the set time based on this step, where the waiting time may be specifically determined by a length value from the acquisition time of the data original request to the current time. If the set time length is exceeded, it is considered that there is no need to continue waiting, and S2814 may be executed; if the set time length is exceeded, the process may return to S281, and after receiving new request response data, a new round of determination operation of the target response data is started.

S2814, determining that the target response data corresponding to the original data request is a request response timeout.

Specifically, when it is determined that the waiting duration exceeds the set duration, the target response data corresponding to the original data request may be considered as a request response timeout, and it can be understood that this situation is also caused by that the original data request has a referenceable sent network request, but the request response data of the referenceable sent network request cannot be normally received (i.e., fails to be received) for some reasons (e.g., network bandwidth congestion or excessive resource occupancy).

The data request processing method provided by the second embodiment of the present invention can compare and analyze the data identifier set and the data domain identifier set included in the data original request with the data identifier set and the data domain identifier set included in the sent network request before generating the network request that can be sent, and can determine to generate a new network request that corresponds to the data original request according to the analysis result, or directly wait for the request response data of the sent network request, and specifically provide an implementation process that can be used as the data original request target response data according to the received request response data. Therefore, the effective combination of different data original requests in the request terminal can be realized, the request quantity of the network requests really sent to the response terminal is effectively reduced, and meanwhile, the response data required by the data original requests are accurately obtained, so that the network resources, the data flow and the computing resources of the request terminal and the response terminal are effectively saved.

EXAMPLE III

Fig. 3a is a schematic block diagram illustrating a structure of a data request processing apparatus according to a third embodiment of the present invention, which is suitable for processing request sending and receiving of an original data request, and which can be implemented by software and/or hardware and is generally integrated on a computer device. As shown in fig. 3a, the apparatus comprises: an original request acquisition module 31 and a process execution module 32.

The original request acquiring module 31 is configured to acquire an original data request, where the original data request includes a service identifier, a set of data identifiers, and a set of data domain identifiers;

a processing execution module 32, configured to wait for request response data of the sent network request when the service identifier is a non-specific service identifier, the data identifier set is covered by the data identifier set of the sent network request, and the data domain identifier set corresponding to the covered data identifier is covered by the data domain identifier set corresponding to the covered data identifier in the sent network request; otherwise, generating a network request according to the data identifier set and the data domain identifier set of the original data request, and sending the network request, wherein the network request comprises an associated identifier for identifying the original data request.

The data request processing device provided by the third embodiment of the present invention can compare and analyze the data identifier set and the data domain identifier set included in the original data request with the data identifier set and the data domain identifier set included in the sent network request before generating the network request that can be sent, and can determine to generate a new network request that corresponds to the original data request that can be sent according to the analysis result, or directly wait for the request response data of the sent network request, thereby being capable of implementing effective merging of different original data requests in the request terminal, effectively reducing the number of requests of network requests that are really sent to the response terminal, and further saving network resources, data traffic and computational resources of the request terminal.

Further, the generating a network request according to the data identifier set and the data domain identifier set of the original data request, and sending an execution condition of the network request includes: the service identifier is a special service identifier; or, the service identifier is a non-specific service identifier, and the data identifier set is not covered by the data identifier set requested by the sent network; or, the service identifier is a non-specific service identifier, the data identifier set is covered by the data identifier set of the sent network request, and the data domain identifier set is not covered by the data domain identifier set corresponding to the data identifier in the sent network request.

Further, the sent network request is stored in a sent network request cache table.

Further, the processing execution module 32 is further configured to:

and after the network request is sent, adding the network request into a sent network request cache table.

Further, the apparatus further comprises: the deletion executing module 33 is configured to, after receiving the request response data, delete the sent network request corresponding to the request response data from the sent network request cache table.

Further, the apparatus further comprises: a response data determining module 34, configured to, after receiving the request response data, determine the response data according to at least one of the following parameters: the method comprises the steps of requesting a network request corresponding to response data, an original data request, a sent network request cache table and the waiting time of the original data request, and determining target response data corresponding to the original data request.

Further, the response data determining module 34 may be specifically configured to:

determining a target network request corresponding to the received request response data;

and if the service identifier of the original data request is a special service identifier and the identifier object of the associated identifier contained in the target network request is the original data request, using the request response data as the target response data of the original data request, and otherwise, keeping the original data request in a request response data waiting state.

Further, the response data determining module 34 may be specifically configured to:

determining a target network request corresponding to the received request response data;

if the service identifier of the original data request is a non-specific service identifier and the data domain identifier set of the target network request completely covers the data domain identifier set of the original data request, extracting associated response data corresponding to the target data identifier from the request response data and correspondingly adding the target data identifier and the associated response data to a set data mapping table when the target data identifier contained in the data identifier set of the target network request exists in the data identifier set of the original data request;

if the data mapping table contains all data identifications of the data identification set in the data original request, using associated response data corresponding to each target data identification in the data mapping table as target response data of the data original request; otherwise, keeping the original data request in a request response data waiting state.

Further, the response data determining module 34 may be specifically configured to:

and if the sent network request cache table is empty and the original data request still keeps a request response data waiting state, determining that the target response data corresponding to the original data request is a request response failure.

Further, the response data determining module 34 is specifically configured to:

and if the original data request still keeps a request response data waiting state and the waiting time of the original data request exceeds a set time, determining that the target response data corresponding to the original data request is a request response overtime.

For example, it may be considered that the processing device for data request provided by the third embodiment of the present invention is specifically configured in the request terminal, and fig. 3b shows an interaction schematic diagram of the request terminal configured with the processing device provided by the third embodiment of the present invention and the response terminal for implementing request interaction, so as to better understand data interaction with the response terminal when there is an original request for data generated in the request terminal. As shown in fig. 3b, the request terminal includes an original request obtaining module 310, a processing executing module 320, and a response data determining module 330.

The requesting terminal 300 may first obtain an original request for data generated by a service application through the original request obtaining module 310, and then may perform a determination process on the obtained original request for data through the process executing module 320, so as to determine whether the original request for data waits for request response data of a network request that has been sent, or generates a new network request, and sends the network request to the responding terminal 340 when the new network request is generated.

It should be noted that the processing executing module 320 may specifically implement the determination processing on the original request of the data by executing S102 to S106 shown in fig. 1 in the first embodiment. Meanwhile, the original request cache table containing the original request of data and the sent network request cache table containing the sent network request can be updated by executing S206 shown in fig. 2a in the second embodiment.

Thereafter, the processing execution module 320 may pass the updated original request cache table and the sent network request cache table in the processing process to the response data determination module 330 as known information. For the response data determining module 330, it may receive the request response data sent by the response terminal 340, determine the target response data of the original request of the data according to the received request response data, the data information of the original request of the data included in the original request cache list, and the data information of the network request sent in the network request cache list, and feed back the determined target response data to the service application.

It should be noted that the response data determining module 330 may specifically implement the determination of the target response data of the original request of the data by executing S207 and S208 in the flowchart shown in fig. 2a in the second embodiment, and may specifically implement the determination of the target response data of the original request of the data by executing S281 to S2814 in the flowchart shown in fig. 2 b.

On the basis of the above example, fig. 3c provides a connection diagram of unit structures of the processing execution module and the response data determination module, and as shown in fig. 3c, the processing execution module may specifically include: an original request holding unit 3201, an original request determination unit 3202, a network request execution unit 3203, and a network request holding unit 3204,. Specifically, in conjunction with the second embodiment, it can be considered that the original request saving unit 3201 specifically executes S201 in fig. 2 a; the original request determining unit 3202 specifically executes S202 to S205 in fig. 2 a; the network request executing unit 3203 specifically performs the generating and sending operations of S206 in fig. 2a, and the network request holding unit 3204 specifically performs the request caching operation of S206 in fig. 2a and may perform the request deleting operation of S207.

As shown in fig. 3c, the response data determining module may specifically include: a response data receiving unit 3301, a response data analyzing unit 3302, and a response data feedback unit 3303. Specifically, in combination with the second embodiment, it can be considered that the response data receiving unit 3301 specifically performs the request response data receiving operation of S207 in fig. 2a, the response data analyzing unit 3302 is configured to perform the analysis and determination operation of the target response data of S208 in fig. 2a, and specifically performs the flow of steps in fig. 2b, and the response data feedback unit 3303 specifically may feed back the determined target response data corresponding to the original request of the data to the service application.

Example four

Fig. 4 is a hardware structure diagram of a computer device according to a fourth embodiment of the present invention, specifically, the computer device includes: a processor and a storage device. At least one instruction is stored in the storage device, and the instruction is executed by the processor, so that the computer device executes the processing method of the data request according to the method embodiment.

Referring to fig. 4, the computer device may specifically include: a processor 40, a storage device 41, a display 42, an input device 43, an output device 44, and a communication device 45. The number of processors 40 in the computer device may be one or more, and one processor 40 is taken as an example in fig. 4. The number of the storage devices 41 in the computer apparatus may be one or more, and one storage device 41 is taken as an example in fig. 4. The processor 40, the storage means 41, the display 42, the input means 43, the output means 44 and the communication means 45 of the computer device may be connected by a bus or in another way, as exemplified by the bus connection in fig. 4.

The storage device 41 is a computer-readable storage medium, and can be used to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the embodiments of the present invention (for example, the original request acquisition module 31 and the processing execution module 32, and the deletion execution module 33 and the response data determination module 34, etc. in the processing device for providing data requests according to the above-mentioned embodiments). The storage device 41 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating device, an application program required for at least one function; the storage data area may store data created according to use of the computer device, and the like. Further, the storage device 41 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, storage 41 may further include memory located remotely from processor 40, which may be connected to a computer device over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

Generally speaking, the display screen 42 is used for displaying data according to instructions of the processor 40, and is also used for receiving touch operations applied to the display screen 42 and sending corresponding signals to the processor 40 or other devices. Optionally, when the display screen 42 is an infrared screen, the display screen further includes an infrared touch frame, and the infrared touch frame is disposed around the display screen 42, and may also be configured to receive an infrared signal and send the infrared signal to the processor 40 or other computer devices.

Communication means 45 for establishing a communication connection with other computer devices, which may be wired communication means and/or wireless communication means.

The input means 43 may be used for receiving input numeric or character information and generating key signal inputs related to user settings and function control of the computer apparatus, and may also be a camera for acquiring images and a sound pickup computer apparatus for acquiring audio in video data. The output device 44 may include a video computer device such as a display screen and an audio computer device such as a speaker. It should be noted that the specific composition of the input device 43 and the output device 44 can be set according to actual conditions.

The processor 40 executes various functional applications of the computer device and data processing, i.e., implements the above-described processing method of the data request, by executing the software programs, instructions, and modules stored in the storage device 41.

Specifically, in the embodiment, when the processor 40 executes one or more programs stored in the storage device 41, the following operations are specifically implemented: acquiring a data original request, wherein the data original request comprises a service identifier, a data identifier set and a data domain identifier set; if the service identifier is a non-special service identifier, the data identifier set is covered by the data identifier set of the sent network request, and the data domain identifier set corresponding to the covered data identifier is covered by the data domain identifier set corresponding to the covered data identifier in the sent network request, waiting for request response data of the sent network request; otherwise, generating a network request according to the data identifier set and the data domain identifier set of the original data request, and sending the network request, wherein the network request comprises an associated identifier for identifying the original data request.

An embodiment of the present invention further provides a computer-readable storage medium, where when a program in the storage medium is executed by a processor of a computer device, the computer device is enabled to execute the method for processing a data request according to the foregoing embodiment. Illustratively, the method for processing a data request according to the foregoing embodiment includes: acquiring a data original request, wherein the data original request comprises a service identifier, a data identifier set and a data domain identifier set; if the service identifier is a non-specific service identifier, the data identifier set is covered by the data identifier set of the sent network request, and the data domain identifier set corresponding to the covered data identifier is covered by the data domain identifier set corresponding to the covered data identifier in the sent network request, waiting for request response data of the sent network request; otherwise, generating a network request according to the data identifier set and the data domain identifier set of the original data request, and sending the network request, wherein the network request comprises an associated identifier for identifying the original data request.

It should be noted that, as for the embodiments of the apparatus, the computer device, and the storage medium, since they are basically similar to the embodiments of the method, the description is relatively simple, and in the relevant places, reference may be made to the partial description of the embodiments of the method.

From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a robot, a personal computer, a server, or a network device) to execute the method for processing a data request according to any embodiment of the present invention.

It should be noted that, in the processing apparatus for data request, the units and modules included in the processing apparatus are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.

It should be understood that portions of the present invention 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 a memory and executed by a suitable instruction execution device. 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.

In the description of the specification, reference to the description of "one embodiment," "some embodiments," "an example," "a specific example," or "some examples" or the like 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 invention. 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.

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (13)

1. A method for processing a data request, comprising:

acquiring a data original request, wherein the data original request comprises a service identifier, a data identifier set and a data domain identifier set;

if the service identifier is a non-specific service identifier, the data identifier set is covered by the data identifier set of the sent network request, and the data domain identifier set corresponding to the covered data identifier is covered by the data domain identifier set corresponding to the covered data identifier in the sent network request, waiting for request response data of the sent network request;

otherwise, generating a network request according to the data identifier set and the data domain identifier set of the original data request, and sending the network request, wherein the network request comprises an associated identifier for identifying the original data request;

the data identification set comprises data identifications required by a service module for data interaction, and each data identification in the data identification set correspondingly has a data domain identification set;

the data field identification set comprises data field identifications of data information required by the corresponding data identifications.

2. The method according to claim 1, wherein the generating a network request according to the data identifier set and the data domain identifier set of the original request for data, and sending the network request is performed under conditions that include:

the service identifier is a special service identifier; or,

the service identification is a non-special service identification, and the data identification set is not covered by the data identification set of the sent network request; or,

the service identification is a non-special service identification, the data identification set is covered by the data identification set of the sent network request, and the data domain identification set is not covered by the data domain identification set corresponding to the data identification in the sent network request.

3. The method of claim 1, wherein the sent network request is stored in a sent network request cache table.

4. The method of claim 3, further comprising, after sending the network request:

and adding the network request into a sent network request cache table.

5. The method of claim 3, further comprising:

and after receiving the request response data, deleting the sent network request corresponding to the request response data from the sent network request cache table.

6. The method of claim 3, further comprising:

upon receiving the request response data, based on at least one of the following parameters: the method comprises the steps of requesting a network request corresponding to response data, an original data request, a sent network request cache table and the waiting time of the original data request, and determining target response data corresponding to the original data request.

7. The method of claim 6, wherein the method is based on at least one of the following parameters: the method comprises the following steps of requesting a network request corresponding to response data, an original data request, a sent network request cache table and the waiting duration of the original data request, and determining target response data corresponding to the original data request, wherein the target response data comprises the following steps:

determining a target network request corresponding to the received request response data;

and if the service identifier of the original data request is a special service identifier and the identifier object of the associated identifier contained in the target network request is the original data request, using the request response data as the target response data of the original data request, and otherwise, keeping the original data request in a request response data waiting state.

8. The method of claim 6, wherein the method is based on at least one of the following parameters: the method for determining the target response data corresponding to the original data request comprises the following steps of requesting a network request corresponding to the response data, an original data request, a sent network request cache table and the waiting time of the original data request, wherein the target response data corresponding to the original data request comprises the following steps:

determining a target network request corresponding to the received request response data;

if the service identifier of the original data request is a non-specific service identifier and the data domain identifier set of the target network request completely covers the data domain identifier set of the original data request, extracting associated response data corresponding to the target data identifier from the request response data and correspondingly adding the target data identifier and the associated response data to a set data mapping table when the target data identifier contained in the data identifier set of the target network request exists in the data identifier set of the original data request;

if the data mapping table contains all data identifications of the data identification set in the data original request, using associated response data corresponding to each target data identification in the data mapping table as target response data of the data original request; otherwise, keeping the original data request in a request response data waiting state.

9. The method of claim 6, wherein the method is based on at least one of the following parameters: the method comprises the following steps of requesting a network request corresponding to response data, an original data request, a sent network request cache table and the waiting duration of the original data request, and determining target response data corresponding to the original data request, wherein the target response data comprises the following steps:

and if the sent network request cache table is empty and the original data request still keeps a request response data waiting state, determining that the target response data corresponding to the original data request is a request response failure.

10. The method of claim 6, wherein the method is based on at least one of the following parameters: the method for determining the target response data corresponding to the original data request comprises the following steps of requesting a network request corresponding to the response data, an original data request, a sent network request cache table and the waiting time of the original data request, wherein the target response data corresponding to the original data request comprises the following steps:

and if the original data request still keeps a request response data waiting state and the waiting time of the original data request exceeds a set time, determining that the target response data corresponding to the original data request is request response overtime.

11. An apparatus for processing a data request, comprising:

the system comprises an original request acquisition module, a data domain identification acquisition module and a data domain identification acquisition module, wherein the original request acquisition module is used for acquiring an original data request which comprises a service identification, a data identification set and a data domain identification set;

a processing execution module, configured to wait for request response data of the sent network request when the service identifier is a non-specific service identifier, the data identifier set is covered by the data identifier set of the sent network request, and the data domain identifier set corresponding to the covered data identifier is covered by the data domain identifier set corresponding to the covered data identifier in the sent network request; otherwise, generating a network request according to the data identifier set and the data domain identifier set of the original data request, and sending the network request, wherein the network request comprises an associated identifier for identifying the original data request;

the data identification set comprises data identifications required by a service module during data interaction, and each data identification in the data identification set correspondingly has a data domain identification set;

the data field identification set comprises data field identifications of data information required by the corresponding data identifications.

12. A computer device, comprising:

one or more processors;

storage means for storing one or more programs;

the one or more programs being executable by the one or more processors to cause the one or more processors to implement a method of processing a data request as claimed in any one of claims 1-10.

13. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out a method for processing a data request according to any one of claims 1 to 10.

Images