CN109286672B - User request processing method and device and server - Google Patents
User request processing method and device and server Download PDFInfo
- Publication number
- CN109286672B CN109286672B CN201811158059.8A CN201811158059A CN109286672B CN 109286672 B CN109286672 B CN 109286672B CN 201811158059 A CN201811158059 A CN 201811158059A CN 109286672 B CN109286672 B CN 109286672B
- Authority
- CN
- China
- Prior art keywords
- user request
- uncompleted
- information
- stage
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/62—Establishing a time schedule for servicing the requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Telephonic Communication Services (AREA)
Abstract
The embodiment of the invention provides a method, a device and a server for processing a user request, wherein the method is applied to a server and comprises the following steps: after the service is restarted, inquiring a pre-recorded user request information table to obtain outlet identification information of a user request, wherein the outlet identification information corresponding to the user request is recorded in the user request information table and is used for indicating the completion state of the user request; determining whether the user request is completed or not according to the exit identification information; when it is determined that the user request is not completed, the uncompleted user request is executed. Therefore, after the service is restarted, the existing uncompleted user request can be detected and determined, the completion state of the uncompleted user request is further determined, the uncompleted user request is further executed, the service required by the user is provided, and the user experience is greatly improved.
Description
Technical Field
The present invention relates to the field of network technologies, and in particular, to a method, an apparatus, and a server for processing a user request.
Background
In order to ensure the normal operation of the application program and enable the user to use the local function provided by the application program normally, the client (also called user side) needs to cooperate with the corresponding server in the network, i.e. the server and the service program, and the corresponding server in the network provides the corresponding service.
The client obtains the service provided by the server by sending a user request to the server, that is, the client accesses the server, which is often realized by sending a user request to the server, where the user request is a request for requesting the service from the server, and for example, the user request may include various requests such as a login request and a video request. After receiving the user request, the server responds to the user request to provide the service requested by the client.
In order to provide better service or repair problems, the service provided by the server needs to be restarted, for example, the server needs to perform operations such as updating or maintenance regularly or irregularly, and generally needs to be restarted after the updating or maintenance is performed, or the server is restarted after a fault occurs, and the server is restarted so that the service program running on the server is also restarted, or the service program is restarted after a fault occurs. At present, for user requests which are not completed when a service provided at a server is restarted, the service does not process the user requests after the service is restarted, so that the user requests cannot be processed correspondingly, the user cannot obtain the required service, and the user experience is very poor.
Disclosure of Invention
The embodiment of the invention aims to provide a method, a device and a server for processing a user request, so as to continue to finish the uncompleted user request after the service is restarted and improve the user experience. The specific technical scheme is as follows:
in a first aspect, an embodiment of the present invention provides a method for processing a user request, where the method is applied to a server, and the method includes:
after the service is restarted, inquiring a pre-recorded user request information table to obtain outlet identification information of the user request, wherein the outlet identification information corresponding to the user request is recorded in the user request information table and is used for indicating the completion state of the user request;
determining whether the user request is completed or not according to the exit identification information;
when it is determined that the user request is not complete, the incomplete user request is executed.
Optionally, the determining whether the user request is completed according to the exit identification information includes:
and when the exit identification information is null or a preset value, determining that the user request is not completed.
Optionally, when it is determined that the user request is not completed, executing the uncompleted user request includes:
inquiring the pre-recorded user request information table to obtain the execution state information of the uncompleted user request, wherein the execution state information of the user request is recorded in the user request information table and is used for indicating the execution state of the user request;
and executing the uncompleted user request according to the execution state information.
Optionally, the execution state of the uncompleted user request includes a first-stage completion state or a first-stage ongoing state;
the executing the uncompleted user request according to the execution state information includes:
if the execution state of the uncompleted user request is a first-stage ongoing state, executing the uncompleted user request from the beginning of re-executing the first stage;
and if the execution state of the uncompleted user request is a first-stage completion state, continuing to execute the uncompleted user request from the next execution stage of the first stage.
Optionally, the method further includes:
and according to preset cleaning time, cleaning the pre-recorded user request information table, and deleting information corresponding to the finished user request indicated by the outlet identification information in the user request information table.
Optionally, the method further includes:
after receiving at least one user request sent by at least one application terminal, recording information corresponding to the at least one user request in the user request information table based on an execution process of the at least one user request, wherein the information corresponding to the at least one user request at least comprises an exit identifier corresponding to the user request.
In a second aspect, an embodiment of the present invention provides an apparatus for processing a user request, which is applied to a server, and the apparatus includes:
the information table searching module is used for detecting and inquiring a pre-recorded user request information table after the service is restarted, and acquiring the exit identification information of the user request, wherein the exit identification information corresponding to the user request is recorded in the user request information table, and the exit identification information is used for indicating the completion state of the user request;
a state determining module, configured to determine whether the user request is completed according to the exit identification information;
a request processing module, configured to execute the uncompleted user request when it is determined that the user request is uncompleted.
Optionally, the state determining module includes:
and the state determining submodule is used for determining that the user request is not finished when the exit identification information is null or a preset value.
Optionally, the request processing module includes:
the query submodule is used for querying the pre-recorded user request information table to acquire the execution state information of the uncompleted user request, the execution state information of the user request is recorded in the user request information table, and the execution state information is used for indicating the execution state of the user request;
and the processing submodule is used for executing the uncompleted user request according to the execution state information.
Optionally, the execution state of the uncompleted user request includes a first-stage completion state or a first-stage ongoing state;
the processing submodule comprises:
a first processing unit, configured to execute the incomplete user request from re-executing the first stage if an execution state of the incomplete user request is a first-stage in-progress state;
a second processing unit, configured to, if the execution state of the uncompleted user request is a first-stage completion state, continue to execute the uncompleted user request from a next execution stage of the first stage.
Optionally, the apparatus further comprises:
and the clearing module is used for clearing the prerecorded user request information table according to preset clearing time and deleting information corresponding to the finished user request indicated by the outlet identification information in the user request information table.
Optionally, the apparatus further comprises:
the information table recording module is configured to record, in the user request information table, information corresponding to at least one user request based on an execution process of the at least one user request after receiving the at least one user request sent by at least one application terminal, where the information corresponding to the at least one user request at least includes an exit identifier corresponding to the user request.
In a third aspect, an embodiment of the present invention further provides a server, which is characterized by including a processor, a memory, and a communication bus, where the processor and the memory complete communication with each other through the communication bus;
a memory for storing a computer program;
and the processor is used for realizing the steps of the processing method of any user request when executing the program stored in the memory.
In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when executed by a processor, the computer program implements any of the above-mentioned steps of the method for processing a user request.
In the scheme provided by the embodiment of the invention, after the service is restarted, a pre-recorded user request information table is inquired, and the export identification information of the user request is obtained, wherein the export identification information corresponding to the user request is recorded in the user request information table and is used for indicating the completion state of the user request; determining whether the user request is completed or not according to the exit identification information; when it is determined that the user request is not completed, the uncompleted user request is executed. Therefore, after the service is restarted, the user request which is not completed due to restarting can be continuously completed, and the user experience is greatly improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a flowchart of a method for processing a user request according to an embodiment of the present invention;
FIG. 2 is a detailed flowchart of step S103 in the embodiment shown in FIG. 1;
FIG. 3 is a flowchart of one manner of determining whether a processing result is accurate according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a device for processing a user request according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a server according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In order to continue to complete an incomplete user request after a service is restarted and improve user experience, embodiments of the present invention provide a method and an apparatus for processing a user request, a server, and a computer-readable storage medium.
First, a method for processing a user request according to an embodiment of the present invention is described below.
The method for processing the user request provided by the embodiment of the invention can be applied to any server side which needs to process the user request, and particularly can be a server.
As shown in fig. 1, a method for processing a user request is applied to a server, and the method includes:
s101, after the service is restarted, inquiring a pre-recorded user request information table to obtain outlet identification information of the user request;
the exit identification information corresponding to the user request is recorded in the user request information table, and the exit identification information is used for indicating the completion state of the user request.
S102, determining whether the user request is finished or not according to the exit identification information, and executing the step S103 when the user request is determined to be unfinished;
s103, executing the uncompleted user request.
It can be seen that, in the solution provided in the embodiment of the present invention, after the service is restarted, the pre-recorded user request information table is queried to obtain the exit identification information of the user request, where the exit identification information corresponding to the user request is recorded in the user request information table, and the exit identification information is used to indicate the completion status of the user request; determining whether the user request is completed or not according to the exit identification information; when it is determined that the user request is not completed, the uncompleted user request is executed. Therefore, the user request which is not completed due to restarting can be continuously completed after the service is restarted, and the user experience is greatly improved.
It should be noted that, in the embodiment of the present invention, the "service" may specifically refer to a service program provided on a server and providing a service for a client.
The service needs to be restarted for several reasons. For example, the server performs operations such as updating or maintenance regularly or irregularly, and generally needs to be restarted after the server performs the updating or maintenance, or the server goes down due to a failure and needs to be restarted, and the server is restarted so that a service program set on the server needs to be restarted, or the service program itself may also be restarted due to a failure. At the time of service restart, it is likely that some user requests are in progress, i.e., the restart occurs during the processing of the user requests, and therefore, these user requests have not yet been completed. In the embodiment of the present invention, after the service is restarted, in order to ensure the user experience, and in order to continue to process these incomplete user requests, a user request information table is set, where the table is used to record information related to the user request, for example, whether the execution is completed, to which stage the execution is performed, and information such as context, environment, parameters, and the like required by each stage of executing the user request, and specifically record which information is not limited, and those skilled in the art can set it as needed.
In the embodiment of the present invention, the exit identification information corresponding to the user request is recorded in the user request information table, and the exit identification information may be used to indicate the completion status of the user request, that is, whether the request has been processed. After the server is restarted, the server can query a pre-recorded user request information table to obtain the outlet identification information of the user request.
In an embodiment, the server records the corresponding egress identification information when the user request is completed, and if the egress identification information requested by a certain user is not recorded in the user request information table, that is, the egress identification information is empty, it indicates that the user request is not completed. Then after the service is restarted, the user request information table may be traversed to find whether the user request information table records corresponding exit identification information. Thereby determining whether the user request has been completed.
The exit identification information may be recorded in any form, as long as it can identify that the user request has been processed, and may be exit identification information formed by letters, numbers, a combination of the two, and the like, which is not specifically limited and described herein. For example, it may be c1, G, ywc #, 5#, etc. In addition, it is reasonable that the corresponding exit identification information of each user request may be the same or different.
If there is an incomplete user request, the server may execute step S103, that is, execute the determined incomplete user request, thereby completing the user request, providing a corresponding service for the user, and improving user experience. For clarity and layout, the specific manner in which the server performs the determined incomplete user request will be described as an example.
As an implementation manner, the user request information table recorded by the server may be as follows:
| user request | Exit identification information |
| User request 1 | a |
| User request 2 | |
| User request 3 | a |
Then, according to the table, the service end can determine that the user request 2 is an incomplete user request, and the user requests 1 and 3 are completed user requests.
As an implementation manner of the embodiment of the present invention, as shown in fig. 2, the step of determining whether the user request is completed according to the exit identification information may include:
and when the exit identification information is null or a preset value, determining that the user request is not completed.
In an embodiment, the server records the egress identification information corresponding to the user request only when the user request is processed, and then indicates that the user request is not processed when the egress identification information corresponding to the user request is empty.
That is, when the server queries the user request information table, if there is a user request without the egress identification information, the server may determine that there is an incomplete user request, and if there is no user request without the egress identification information, it indicates that there is no incomplete user request, and the server may not perform the operation.
In another embodiment, when the user request is processed, the server records that the exit identification information corresponding to the user request is a predetermined value, and when the exit identification information corresponding to a certain user request is the predetermined value, it indicates that the user request is not processed. The specific value of the predetermined value is not specifically limited in the embodiments of the present invention, and may be, for example, 0, 25, WWC, and the like.
If the predetermined value is 25, when the server queries the user request information table, if there is a user request with egress identification information of 25, the server may determine that there is an incomplete user request, and if there is no user request with egress identification information of 25, it indicates that there is no incomplete user request, and the server may not perform any operation.
Therefore, in this embodiment, the server may determine that the user request is not completed when the egress identification information is empty or the predetermined value, and may quickly and accurately determine whether there is an incomplete user request by this way, thereby improving the processing speed and accuracy of the user request.
As an implementation manner of the embodiment of the present invention, as shown in fig. 2, the step of executing the incomplete user request when it is determined that the user request is incomplete may include:
s201, inquiring the pre-recorded user request information table to acquire the execution state information of the uncompleted user request;
in order to better complete the incomplete user request, the server may determine execution status information of the incomplete user request, and when the server processes the user request, the server may record the execution status information of the user request in the user request information table, where the execution status information is used to indicate an execution status of the user request, that is, to indicate which stage the user request is executed.
Specifically, the user request information table may record, in addition to the exit identifier, various execution state information in the user request processing process, for example, various information carried in the user request, a network environment, a processing state, and the like. The processing state may include a processing progress identifier, a suspension identifier, and the like, and when the processing requested by the user is suspended, the server may record the suspension identifier corresponding to the user request.
Therefore, after the service is restarted, the user request information table recorded in advance can be inquired to obtain the recorded execution state information.
Of course, the server may also determine the execution state information of the incomplete user request in any other manner capable of determining the execution state information of the user request, which is not limited herein. For example, by monitoring the processing progress of the user request, if the processing progress is not changed within a preset time period, the user request is likely to be in a suspended state, and the server may determine that the execution state information is in the suspended state.
S202, according to the execution state information, the uncompleted user request is executed.
After obtaining the execution state information corresponding to the uncompleted user request, the server can execute the uncompleted user request according to the execution state information. If the execution state information of the uncompleted user request indicates that the uncompleted user request is still in progress, the uncompleted user request can be continuously executed; processing of an outstanding user request may be resumed if its execution state information characterizes it as a suspended state.
Therefore, in this embodiment, the server may query the pre-recorded user request information table to obtain the execution state information of the uncompleted user request, and then execute the uncompleted user request according to the execution state information, so as to ensure that the service required by the user is provided and improve the user experience.
As an implementation manner of the embodiment of the present invention, the execution state of the incomplete user request may include a first-stage completion state or a first-stage in-progress state.
Since the processing procedure for the user request may generally include multiple processing stages, the server may record the execution state information corresponding to each user request according to the multiple processing stages when recording the user request information table.
For example, the server receives a user request to create a virtual machine request, and in the process of processing the user request, the server generally has two execution stages, the first stage is a scheduling stage, and performs resource scheduling to determine the created virtual machine resources; the second stage is a virtual machine creating stage, and based on the determined resources, the virtual machine is created, configured and on-line. Then the server may record the execution status information in the user request information table: when the execution is in the scheduling stage, the execution state information may be recorded as indicating that the scheduling is in progress, the scheduling stage is completed, and the execution state information may be recorded as indicating that the scheduling is completed. Then, based on the recorded execution state information, the execution phase of the create virtual machine request may be known.
Assuming that the scheduling stage is the first stage, the virtual machine creation stage is the next stage of the first stage, the scheduling in progress represents the first stage proceeding state, and the scheduling completion represents the first stage completion state.
For this case, the executing the uncompleted user request according to the execution status information includes:
if the execution state of the uncompleted user request is a first-stage ongoing state, executing the uncompleted user request from the beginning of re-executing the first stage; and if the execution state of the uncompleted user request is a first-stage completion state, continuing to execute the uncompleted user request from the next execution stage of the first stage.
If the server determines that the uncompleted user request is in the first-stage ongoing state according to the inquired execution state information of the uncompleted user request, it indicates that the execution state of the uncompleted user request at the time of service restart is still in the first-stage processing process, and in order to ensure that the uncompleted user request can be completed, the server may execute the uncompleted user request from the first stage of re-executing the uncompleted user request processing process.
If the server determines that the uncompleted user request is in the first-stage completed state according to the queried execution state information of the uncompleted user request, it indicates that the execution state of the uncompleted user request when the service is restarted is that the first-stage processing is completed, and in order to ensure that the uncompleted user request can be completed and avoid the waste of computing resources due to repeated processing, the server may continue to execute the uncompleted user request from the next execution stage of the first stage.
Still taking the user request as an example of creating a virtual machine request, if the execution state information of the uncompleted user request queried by the server is scheduling completion, it indicates that the execution state of the uncompleted user request when the service is restarted is that the processing of the first phase is completed, and the server can execute the second phase, i.e. the virtual machine creation phase; if the execution state information of the uncompleted user request inquired by the server is in scheduling, it indicates that the execution state of the uncompleted user request when the service is restarted is a first-stage in-progress state, and the server can perform re-execution of the first stage, i.e., re-scheduling processing.
As can be seen, in this embodiment, when the execution state of the uncompleted user request is the first-stage ongoing state, the server executes the uncompleted user request from the beginning of re-executing the first stage; when the execution state of the uncompleted user request is the first-stage completion state, the uncompleted user request is continuously executed from the next execution stage of the first stage, so that the uncompleted user request can be processed in a targeted manner according to various different execution states of the uncompleted user request, and the uncompleted user request is accurately completed, and meanwhile, the waste of resources is avoided.
Since the information related to 1 or more user requests processed by the server may include the export identifier information, the execution state information, and information related to context, environment, parameters, callback method, and the like at each stage of the user request, which may all be recorded in the user request information table, each user request may be correspondingly recorded with a huge data structure, and thus, in order to ensure the performance of the server and improve the resource utilization rate, as an implementation manner of the embodiment of the present invention, the method may further include:
and according to preset cleaning time, cleaning the pre-recorded user request information table, and deleting information corresponding to the finished user request indicated by the outlet identification information in the user request information table.
The preset cleaning time may be set according to factors such as the number of user requests processed by the actual server, for example, every 24 hours, every 20 hours, every 3 days, and the like, and is not limited specifically herein.
In order to not influence the continuous execution of the uncompleted user request, when the server performs a cleaning operation on the pre-recorded user request information table according to the preset cleaning time, the information corresponding to the user request which is indicated by the export identification information and is completed is deleted, and the information corresponding to the uncompleted user request needs to be reserved.
For example, assuming that the preset cleaning time is every 24 hours, when the preset cleaning time is reached, the server performs the cleaning operation of the user request information table. At this time, the user request information table is shown as follows:
| user request | Portal identification information | Exit identification information | Context(s) | Callback method |
| User request Q1 | Entrance mark Ra | Exit mark Ca | Context 1 | Callback method 1 |
| User request Q2 | Entrance identification Rb | Context 2 | Callback method 1 | |
| User request Q3 | Entry identification Rc | Context 3 | Callback method 2 | |
| User request Q4 | Entry identifier Rd | Outlet sign Cc | Context 4 | Callback method 3 |
| … | … | … | … | … |
| User request Qn | Entry identity Rn | Exit identifier Cn | Context n | Callback method n |
The entry identification information may be used to instruct the server to start processing the corresponding user request, that is, the entry identification information of the user request may be recorded when the server starts processing the user request after receiving a user request. The execution state information of the user request may include entry identification information, exit identification information, and the like, where the entry identification information indicates that the user request starts execution, the exit identification information indicates that the user request completes execution, and the entry identification information may be regarded as two pieces of special execution state information indicating a processing state of the user request.
Since the user request Q2 and the user request Q3 do not have the exit identification information, which indicates that the user request Q2 and the user request Q3 are incomplete user requests, the related information of the user request Q2 and the user request Q3 may not be deleted during the cleaning operation of the user request information table.
As can be seen, in this embodiment, the server may perform a cleaning operation on the pre-recorded user request information table according to the preset cleaning time, and delete information corresponding to the executed user request in the user request information table. Therefore, on the premise of ensuring that the uncompleted user request can be successfully completed, resources such as storage space of the user request information table and time occupied by table lookup can be saved, the performance of the server side is ensured, and the resource utilization rate is improved.
As an implementation manner of the embodiment of the present invention, a user request information table may be preset, and after at least one user request sent by at least one application terminal is received, based on an execution process of the at least one user request, information corresponding to the at least one user request is recorded in the user request information table, where the information corresponding to the at least one user request at least includes an exit identifier corresponding to the user request.
In order to accurately record the user request information table corresponding to the user request to ensure that the uncompleted user request can be accurately processed in time, when the server side processes at least one user request sent by at least one received application side, the information corresponding to at least one user request can be recorded in the user request information table based on the execution process of the processed user request.
The recorded information corresponding to the processed user request may include any information about the user request, such as exit identification information, entry identification information, context, callback method, and the like corresponding to the user request, which is not specifically limited herein.
The user request information table may be configured in advance, or may be generated in real time when the user request is received for the first time, and may record at least one piece of information related to the user request.
As can be seen, in this embodiment, after receiving at least one user request sent by at least one application terminal, the server may record information corresponding to the at least one user request in the user request information table based on an execution process of the at least one user request, so as to ensure that, after subsequent restart, an incomplete user request can be accurately executed by using the recorded information.
In the case where the user request information table has recorded therein processing method information of a user request, the step of executing the uncompleted user request may include:
and processing the uncompleted user request by adopting a processing mode corresponding to the processing mode information of the user request.
When executing an incomplete user request, the server may determine the processing mode information of the user request recorded in the user request information table, and further execute the incomplete user request by using a processing mode corresponding to the determined processing mode information.
In an embodiment, the processing mode information requested by the user may be a network interface;
then, when executing the incomplete user request, the server may call the network interface recorded in the user request information table to execute the incomplete user request.
The network interface is an interface called by the server side when responding to the user request. Since the server already starts processing the incomplete user request before restarting, that is, calls the network interface to respond to the incomplete user request, the server can record the network interface as the processing mode information of the network interface.
Thus, after the service is restarted, the user request is determined to be an incomplete user request, and then in order to ensure that the incomplete user request is correctly responded, the service end can call the network interface to execute the incomplete user request.
Therefore, in the embodiment, when the server processes the user request, the processing mode information of each user request can be recorded, and the processing mode information of the user request can be a network interface, so that after the service is restarted, the recorded network interface can execute the uncompleted user request, the uncompleted user request is guaranteed to be correctly responded, a correct response result is obtained, and the user experience is further improved.
In order to determine whether to correctly respond to the incomplete user request, the method may further include:
judging whether the processing result is accurate or not when the uncompleted user request is reprocessed; if not, the outstanding user requests are reprocessed again.
When the server executes the uncompleted user request, whether the processing result is accurate can be judged, and then when the processing is inaccurate, the uncompleted user request is reprocessed again, so that correct service is provided for the user, and user experience is guaranteed. If the processing result is accurate, the server side does not operate.
Therefore, in this embodiment, in order to further improve the user experience, the server may determine whether the processing result is accurate when the server completes the incomplete user request, and when the processing is not accurate, the server re-processes the incomplete user request again to ensure that a correct service is provided for the user.
As an implementation manner of the embodiment of the present invention, as shown in fig. 3, the step of determining whether the processing result is accurate may include:
s301, determining a target service type corresponding to the uncompleted user request according to the recorded corresponding relation between the user request and the service type;
in order to determine whether the processing result of the server for the incomplete user request is accurate, when the server processes each user request, the server may record a service type corresponding to each user request, for example, a video service, a login service, an exit service, and the like.
Therefore, when the server re-processes the uncompleted user request to obtain a processing result, the server can determine the target service type corresponding to the uncompleted user request according to the corresponding relationship between the recorded user request and the service type.
For example, the corresponding relationship between the user request and the service type recorded by the server is as follows: the user request 1 corresponds to the service type f1, the user request 2 corresponds to the service type f2, the user request 3 corresponds to the service type f3, and the user request 4 corresponds to the service type f 2. Then, if it is determined that the user request 3 is an incomplete user request after the service is restarted, the server may determine, according to the correspondence, that the target server type corresponding to the incomplete user request 3 is f 2.
S302, judging whether the processing result accords with the target service type, and if so, executing the step S303; if not, executing step S304;
after determining the target service type corresponding to the uncompleted user request, the server may determine whether a processing result obtained by executing the uncompleted user request matches the target service type, if yes, perform step S303, and if not, perform step S304.
Still taking the example in the step S301 as an example, if the processing result obtained by the server executing the uncompleted user request 3 belongs to the service type f2, the processing result conforms to the target service type; if the processing result obtained by the server re-processing the incomplete user request 3 belongs to the service type f1, f3 or other service types, it is obvious that the processing result does not conform to the target service type.
S303, determining that the processing result is accurate;
s304, determining that the processing result is inaccurate.
If the processing result obtained by the server executing the uncompleted user request accords with the target service type, the processing result is indicated to belong to the target service type, and then the processing result can be determined to be accurate. On the contrary, if the server determines that the processing result obtained by executing the uncompleted user request does not conform to the target service type, the processing result is not the target service type, and it can be determined that the processing result is inaccurate.
It can be seen that, in this embodiment, when the server processes each user request, the server may record the service type requested by the server, so that, after the service is restarted, when an incomplete user request is executed to obtain a processing result, it may be determined whether the processing result matches a target service type corresponding to the incomplete user request, and further, whether the processing result obtained by executing the incomplete user request is accurate may be quickly determined, so that when the processing result is inaccurate, the server may reprocess the incomplete user request again, ensure that the incomplete user request is correctly processed, and further improve user experience.
In order to facilitate the server to process the incomplete user request, for various information of the user request recorded by the server, such as entry identification information, exit identification information, service type, network interface, suspension identification, etc., the server may record these information in a table, i.e., the user request information table, so as to perform a query when needed. For example, it can be shown in the following table:
| user request | Portal identification information | Exit identification information | Pause identification | Type of service | Network interface |
| User request Q1 | Entrance mark Ra | Exit mark Ca | Service type 1 | Network interface J1 | |
| User request Q2 | Entrance identification Rb | Service type 1 | Network interface J2 | ||
| User request Q3 | Entry identification Rc | Pause identifier Z3 | Service type 2 | Network interface J1 | |
| User request Q4 | Entry identifier Rd | Outlet sign Cc | Service type 3 | Network interface J3 | |
| … | … | … | … | … | |
| User request Qn | Entry identity Rn | Exit identifier Cn | Service type n | Network interface Jn |
It can be seen that, in the table, since the user request Q2 and the user request Q3 do not have the exit identification information, after the server is restarted, it may determine that the user request Q2 and the user request Q3 do not have the exit identification information by traversing the table, and further determine that the user request Q2 and the user request Q3 are incomplete user requests. Further, the server may also determine that the user request Q3 has the pause flag Z3 by querying the pause flag in the table, and further determine that the execution state of the user request Q3 is the pause state, so that the server may process the user request Q3 accordingly.
In one implementation, the server may determine that the web interface invoked before the restart for responding to the user request Q3 is the web interface J1 by querying the table, and then, when executing the user request Q3, the server may invoke the web interface J1 for responding to the user request Q3 to obtain a processing result.
Next, in order to determine whether to correctly process the user request Q3 when executing the response user request Q3, the server may further determine, according to the lookup table, that the service type corresponding to the user request Q3 is service type 2, and then the server may determine whether a processing result obtained by reprocessing the user request Q3 matches the service type 2, and if so, it indicates that the execution of the user request Q3 by the server is correct, and may provide an accurate service for the user.
If the processing result obtained by executing the user request Q3 does not conform to the service type 2, which indicates that the execution of the user request Q3 by the server is wrong, the server may re-execute the user request Q3 again, so as to ensure that the user request Q3 is correctly responded, provide the required service to the user, and improve the user experience.
Corresponding to the processing method of the user request, the embodiment of the invention also provides a processing device of the user request.
The following describes a processing apparatus for a user request according to an embodiment of the present invention.
The processing device for the user request provided by the embodiment of the invention can be applied to any server side which needs to process the user request.
As shown in fig. 4, an apparatus for processing a user request is applied to a server, and the apparatus includes:
the information table lookup module 410, after the service is restarted, detects and queries a pre-recorded user request information table to obtain the exit identification information of the user request, where the exit identification information corresponding to the user request is recorded in the user request information table, and the exit identification information is used to indicate the completion state of the user request;
a status determining module 420, configured to determine whether the user request is completed according to the exit identifier information;
a request processing module 430, configured to execute the incomplete user request when it is determined that the user request is incomplete.
It can be seen that, in the solution provided in the embodiment of the present invention, after the service is restarted, the pre-recorded user request information table is queried to obtain the exit identification information of the user request, where the exit identification information corresponding to the user request is recorded in the user request information table, and the exit identification information is used to indicate the completion status of the user request; determining whether the user request is completed or not according to the exit identification information; when it is determined that the user request is not completed, the uncompleted user request is executed. Therefore, the user request which is not completed due to restarting can be continuously completed after the service is restarted, and the user experience is greatly improved.
As an implementation manner of the embodiment of the present invention, the state determining module 420 may include:
a status determination sub-module (not shown in fig. 4) configured to determine that the user request is not completed when the egress identification information is empty or a predetermined value.
As an implementation manner of the embodiment of the present invention, the request processing module 430 may include:
a query submodule (not shown in fig. 4) configured to query the pre-recorded user request information table, and acquire execution state information of the uncompleted user request, where the execution state information of the user request is recorded in the user request information table, and the execution state information is used to indicate an execution state of the user request; (ii) a
A processing submodule (not shown in fig. 4) configured to execute the incomplete user request according to the execution status information.
As an implementation manner of the embodiment of the present invention, the execution state of the uncompleted user request may include a first-stage completion state or a first-stage ongoing state;
the processing submodule may include:
a first processing unit (not shown in fig. 4) configured to execute the incomplete user request from re-executing the first stage if an execution state of the incomplete user request is a first-stage in-progress state;
a second processing unit (not shown in fig. 4) configured to, if the execution status of the uncompleted user request is a first-stage completion status, continue executing the uncompleted user request from a next execution stage of the first stage.
As an implementation manner of the embodiment of the present invention, the apparatus may further include:
a cleaning module (not shown in fig. 4) configured to perform a cleaning operation on the pre-recorded user request information table according to a preset cleaning time, and delete information corresponding to a completed user request indicated by the exit identifier information in the user request information table.
As an implementation manner of the embodiment of the present invention, the apparatus may further include:
an information table recording module (not shown in fig. 4) configured to record, after receiving at least one user request sent by at least one application, information corresponding to the at least one user request in the user request information table based on an execution process of the at least one user request, where the information corresponding to the at least one user request at least includes an exit identifier corresponding to the user request.
Corresponding to the processing method of the user request, an embodiment of the present invention further provides a server, as shown in fig. 5, including a processor 501, a communication interface 502, a memory 503 and a communication bus 504, where the processor 501, the communication interface 502 and the memory 503 complete mutual communication through the communication bus 504,
a memory 503 for storing a computer program;
the processor 501, when executing the program stored in the memory 503, implements the following steps:
after the service is restarted, inquiring a pre-recorded user request information table to obtain outlet identification information of the user request, wherein the outlet identification information corresponding to the user request is recorded in the user request information table and is used for indicating the completion state of the user request;
determining whether the user request is completed or not according to the exit identification information;
when it is determined that the user request is not complete, the incomplete user request is executed.
It can be seen that, in the solution provided in the embodiment of the present invention, after the service is restarted, the pre-recorded user request information table is queried to obtain the exit identification information of the user request, where the exit identification information corresponding to the user request is recorded in the user request information table, and the exit identification information is used to indicate the completion status of the user request; determining whether the user request is completed or not according to the exit identification information; when it is determined that the user request is not completed, the uncompleted user request is executed. Therefore, the user request which is not completed due to restarting can be continuously completed after the service is restarted, and the user experience is greatly improved.
The communication bus mentioned in the above server may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface is used for communication between the server and other devices.
The Memory may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.
As an implementation manner of the embodiment of the present invention, the determining whether the user request is completed according to the exit identification information may include:
and when the exit identification information is null or a preset value, determining that the user request is not completed.
As an implementation manner of the embodiment of the present invention, when it is determined that the user request is not completed, executing the uncompleted user request may include:
inquiring the pre-recorded user request information table to obtain the execution state information of the uncompleted user request, wherein the execution state information of the user request is recorded in the user request information table and is used for indicating the execution state of the user request;
and executing the uncompleted user request according to the execution state information.
As an implementation manner of the embodiment of the present invention, the execution state of the uncompleted user request may include a first-stage completion state or a first-stage ongoing state;
the executing the uncompleted user request according to the execution state information may include:
if the execution state of the uncompleted user request is a first-stage ongoing state, executing the uncompleted user request from the beginning of re-executing the first stage;
and if the execution state of the uncompleted user request is a first-stage completion state, continuing to execute the uncompleted user request from the next execution stage of the first stage.
As an implementation manner of the embodiment of the present invention, the method may further include:
and according to preset cleaning time, cleaning the pre-recorded user request information table, and deleting information corresponding to the finished user request indicated by the outlet identification information in the user request information table.
As an implementation manner of the embodiment of the present invention, a recording manner of the user request information table may include:
after receiving at least one user request sent by at least one application terminal, recording information corresponding to the at least one user request in the user request information table based on an execution process of the at least one user request, wherein the information corresponding to the at least one user request at least comprises an exit identifier corresponding to the user request.
An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored, and when executed by a processor, the computer program implements the following steps:
after the service is restarted, inquiring a pre-recorded user request information table to obtain outlet identification information of the user request, wherein the outlet identification information corresponding to the user request is recorded in the user request information table and is used for indicating the completion state of the user request;
determining whether the user request is completed or not according to the exit identification information;
when it is determined that the user request is not completed, executing the completed user request
It can be seen that, in the solution provided in the embodiment of the present invention, when the computer program is executed by the processor, after the service is restarted, the pre-recorded user request information table is queried to obtain the exit identification information of the user request, where the exit identification information corresponding to the user request is recorded in the user request information table, and the exit identification information is used to indicate the completion state of the user request; determining whether the user request is completed or not according to the exit identification information; when it is determined that the user request is not completed, the uncompleted user request is executed. Therefore, the user request which is not completed due to restarting can be continuously completed after the service is restarted, and the user experience is greatly improved.
As an implementation manner of the embodiment of the present invention, the determining whether the user request is completed according to the exit identification information may include:
and when the exit identification information is null or a preset value, determining that the user request is not completed.
As an implementation manner of the embodiment of the present invention, when it is determined that the user request is not completed, executing the uncompleted user request may include:
inquiring the pre-recorded user request information table to obtain the execution state information of the uncompleted user request, wherein the execution state information of the user request is recorded in the user request information table and is used for indicating the execution state of the user request;
and executing the uncompleted user request according to the execution state information.
As an implementation manner of the embodiment of the present invention, the execution state of the uncompleted user request may include a first-stage completion state or a first-stage ongoing state;
the executing the uncompleted user request according to the execution state information may include:
if the execution state of the uncompleted user request is a first-stage ongoing state, executing the uncompleted user request from the beginning of re-executing the first stage;
and if the execution state of the uncompleted user request is a first-stage completion state, continuing to execute the uncompleted user request from the next execution stage of the first stage.
As an implementation manner of the embodiment of the present invention, the method may further include:
and according to preset cleaning time, cleaning the pre-recorded user request information table, and deleting information corresponding to the finished user request indicated by the outlet identification information in the user request information table.
As an implementation manner of the embodiment of the present invention, a recording manner of the user request information table may include:
after receiving at least one user request sent by at least one application terminal, recording information corresponding to the at least one user request in the user request information table based on an execution process of the at least one user request, wherein the information corresponding to the at least one user request at least comprises an exit identifier corresponding to the user request.
It should be noted that, for the above-mentioned embodiments of the apparatus, the server and the computer-readable storage medium, since they are basically similar to the method embodiments, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiments.
It is further noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (12)
1. A processing method for a user request is applied to a server side, and the method comprises the following steps:
after the service is restarted, inquiring a pre-recorded user request information table to obtain outlet identification information of the user request, wherein the outlet identification information corresponding to the user request is recorded in the user request information table and is used for indicating the completion state of the user request;
when the exit identification information is null or a preset value, determining that the user request is not completed;
when it is determined that the user request is not complete, the incomplete user request is executed.
2. The method of claim 1, wherein the performing the incomplete user request when it is determined that the user request is incomplete comprises:
inquiring the pre-recorded user request information table to obtain the execution state information of the uncompleted user request, wherein the execution state information of the user request is recorded in the user request information table and is used for indicating the execution state of the user request;
and executing the uncompleted user request according to the execution state information.
3. The method of claim 2,
the execution state of the uncompleted user request comprises a first-stage completion state or a first-stage in-progress state;
the executing the uncompleted user request according to the execution state information includes:
if the execution state of the uncompleted user request is a first-stage ongoing state, executing the uncompleted user request from the beginning of re-executing the first stage;
and if the execution state of the uncompleted user request is a first-stage completion state, continuing to execute the uncompleted user request from the next execution stage of the first stage.
4. The method of claim 1, wherein the method further comprises:
and according to preset cleaning time, cleaning the pre-recorded user request information table, and deleting information corresponding to the finished user request indicated by the outlet identification information in the user request information table.
5. The method of claim 1, wherein the method further comprises:
after receiving at least one user request sent by at least one application terminal, recording information corresponding to the at least one user request in the user request information table based on an execution process of the at least one user request, wherein the information corresponding to the at least one user request at least comprises an exit identifier corresponding to the user request.
6. An apparatus for processing a user request, applied to a server, the apparatus comprising:
the information table searching module is used for detecting and inquiring a pre-recorded user request information table after the service is restarted, and acquiring the exit identification information of the user request, wherein the exit identification information corresponding to the user request is recorded in the user request information table, and the exit identification information is used for indicating the completion state of the user request;
a status determining module, configured to determine that the user request is not completed when the exit identification information is null or a predetermined value;
a request processing module, configured to execute the uncompleted user request when it is determined that the user request is uncompleted.
7. The apparatus of claim 6, wherein the request processing module comprises:
the query submodule is used for querying the pre-recorded user request information table to acquire the execution state information of the uncompleted user request, the execution state information of the user request is recorded in the user request information table, and the execution state information is used for indicating the execution state of the user request;
and the processing submodule is used for executing the uncompleted user request according to the execution state information.
8. The apparatus of claim 7,
the execution state of the uncompleted user request comprises a first-stage completion state or a first-stage in-progress state;
the processing submodule comprises:
a first processing unit, configured to execute the incomplete user request from re-executing the first stage if an execution state of the incomplete user request is a first-stage in-progress state;
a second processing unit, configured to, if the execution state of the uncompleted user request is a first-stage completion state, continue to execute the uncompleted user request from a next execution stage of the first stage.
9. The apparatus of claim 6, wherein the apparatus further comprises:
and the clearing module is used for clearing the prerecorded user request information table according to preset clearing time and deleting information corresponding to the finished user request indicated by the outlet identification information in the user request information table.
10. The apparatus of claim 6, wherein the apparatus further comprises:
the information table recording module is configured to record, in the user request information table, information corresponding to at least one user request based on an execution process of the at least one user request after receiving the at least one user request sent by at least one application terminal, where the information corresponding to the at least one user request at least includes an exit identifier corresponding to the user request.
11. A server is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing the communication between the processor and the memory through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of any one of claims 1 to 5 when executing a program stored in the memory.
12. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method steps of any one of the claims 1-5.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811158059.8A CN109286672B (en) | 2018-09-30 | 2018-09-30 | User request processing method and device and server |
| PCT/CN2019/108212 WO2020063769A1 (en) | 2018-09-30 | 2019-09-26 | User request processing method and apparatus and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811158059.8A CN109286672B (en) | 2018-09-30 | 2018-09-30 | User request processing method and device and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109286672A CN109286672A (en) | 2019-01-29 |
| CN109286672B true CN109286672B (en) | 2020-11-27 |
Family
ID=65182600
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811158059.8A Active CN109286672B (en) | 2018-09-30 | 2018-09-30 | User request processing method and device and server |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN109286672B (en) |
| WO (1) | WO2020063769A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109286672B (en) * | 2018-09-30 | 2020-11-27 | 北京金山云网络技术有限公司 | User request processing method and device and server |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0741359A1 (en) * | 1994-11-14 | 1996-11-06 | Daikin Industries, Limited | Method and device for supporting production of moving-picture cd-rom software |
| CN1815466A (en) * | 2005-01-31 | 2006-08-09 | 兄弟工业株式会社 | System, server, and device for providing contents |
| CN101567805A (en) * | 2009-05-22 | 2009-10-28 | 清华大学 | Method for recovering failed parallel file system |
| CN107092598A (en) * | 2016-02-17 | 2017-08-25 | 阿里巴巴集团控股有限公司 | The management method and device of data storage location information |
| CN108076134A (en) * | 2017-10-31 | 2018-05-25 | 努比亚技术有限公司 | Record information acquisition method, terminal, server and computer readable storage medium |
| CN108459842A (en) * | 2018-01-29 | 2018-08-28 | 北京奇艺世纪科技有限公司 | A kind of model configuration method, device and electronic equipment |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP3704022B2 (en) * | 2000-04-25 | 2005-10-05 | 株式会社東芝 | Radio communication system, radio control station, and radio communication method |
| US7996837B2 (en) * | 2006-05-03 | 2011-08-09 | Oracle International Corporation | Recovery mechanism for transactions |
| GB2495079A (en) * | 2011-09-23 | 2013-04-03 | Hybrid Logic Ltd | Live migration of applications and file systems in a distributed system |
| CN104618471B (en) * | 2015-01-23 | 2018-04-06 | 天津大学 | Towards the Application Status transfer method of different terminals |
| CN109286672B (en) * | 2018-09-30 | 2020-11-27 | 北京金山云网络技术有限公司 | User request processing method and device and server |
-
2018
- 2018-09-30 CN CN201811158059.8A patent/CN109286672B/en active Active
-
2019
- 2019-09-26 WO PCT/CN2019/108212 patent/WO2020063769A1/en active Application Filing
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0741359A1 (en) * | 1994-11-14 | 1996-11-06 | Daikin Industries, Limited | Method and device for supporting production of moving-picture cd-rom software |
| CN1815466A (en) * | 2005-01-31 | 2006-08-09 | 兄弟工业株式会社 | System, server, and device for providing contents |
| CN101567805A (en) * | 2009-05-22 | 2009-10-28 | 清华大学 | Method for recovering failed parallel file system |
| CN107092598A (en) * | 2016-02-17 | 2017-08-25 | 阿里巴巴集团控股有限公司 | The management method and device of data storage location information |
| CN108076134A (en) * | 2017-10-31 | 2018-05-25 | 努比亚技术有限公司 | Record information acquisition method, terminal, server and computer readable storage medium |
| CN108459842A (en) * | 2018-01-29 | 2018-08-28 | 北京奇艺世纪科技有限公司 | A kind of model configuration method, device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109286672A (en) | 2019-01-29 |
| WO2020063769A1 (en) | 2020-04-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108255620B (en) | Service logic processing method, device, service server and system | |
| CN107589951B (en) | Cluster upgrading method and device | |
| WO2019237710A1 (en) | Method, device and equipment for recognizing video cards of gpu servers, and medium | |
| CN112581018A (en) | Process task management method, system, device and storage medium | |
| CN109286672B (en) | User request processing method and device and server | |
| CN115495142A (en) | Cloud resource arranging method and device, computer equipment and storage medium | |
| CN104750536A (en) | Virtual machine introspection (VMI) implementation method and device | |
| CN108650123B (en) | Fault information recording method, device, equipment and storage medium | |
| CN111125240A (en) | Distributed transaction implementation method and device, electronic equipment and storage medium | |
| CN110647463B (en) | Method and device for restoring test breakpoint and electronic equipment | |
| US20220327242A1 (en) | Data management method and apparatus | |
| CN115914387A (en) | Resource sharing and data query method, device and server | |
| CN115167896A (en) | Method and device for updating software version, storage medium and electronic equipment | |
| CN114942838A (en) | Data access method, device, equipment and storage medium | |
| CN107967181B (en) | Method and device for controlling critical section | |
| CN114416442A (en) | Hardware change detection method and device, electronic equipment and readable storage medium | |
| CN110113187B (en) | Configuration updating method and device, configuration server and configuration system | |
| CN109995855B (en) | Data acquisition method, device and terminal | |
| CN106776119A (en) | The method for restarting of Service Instance, device and server | |
| CN106557356B (en) | Task processing method and device | |
| CN110740062A (en) | Breakpoint resume method and device | |
| CN112765188A (en) | Configuration information processing method, configuration management system, electronic device, and storage medium | |
| CN109299117B (en) | Data request processing method and device, storage medium and processor | |
| CN112905602B (en) | Data comparison method, computing device and computer storage medium | |
| CN113849133B (en) | Processing method and device of privacy data, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |