WO2017133531A1 - 异步服务处理方法及服务器 - Google Patents

异步服务处理方法及服务器 Download PDF

Info

Publication number
WO2017133531A1
WO2017133531A1 PCT/CN2017/072145 CN2017072145W WO2017133531A1 WO 2017133531 A1 WO2017133531 A1 WO 2017133531A1 CN 2017072145 W CN2017072145 W CN 2017072145W WO 2017133531 A1 WO2017133531 A1 WO 2017133531A1
Authority
WO
WIPO (PCT)
Prior art keywords
request
service
service request
polling
asynchronous
Prior art date
Application number
PCT/CN2017/072145
Other languages
English (en)
French (fr)
Inventor
黄梅龙
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2017133531A1 publication Critical patent/WO2017133531A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • 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/56—Provisioning of proxy services
    • H04L67/566—Grouping or aggregating service requests, e.g. for unified processing
    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • 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

Definitions

  • the present invention relates to the field of computer technologies, and in particular, to an asynchronous service processing method and a server.
  • FIG. 1 The main architecture is shown in Figure 1, including a forwarding server (to prevent single points of failure, usually There will be two or more active/standby forwarding servers. If the current primary forwarding server fails, it will automatically switch to the standby forwarding server, but usually only one forwarding server will be used at the same time. Multiple identical application servers (each application) The server provides exactly the same service and runs at the same time) and a database.
  • a forwarding server to prevent single points of failure, usually There will be two or more active/standby forwarding servers. If the current primary forwarding server fails, it will automatically switch to the standby forwarding server, but usually only one forwarding server will be used at the same time.
  • Multiple identical application servers (each application) The server provides exactly the same service and runs at the same time) and a database.
  • the working principle is as follows: the user sends a service request to the forwarding server, and the forwarding server randomly forwards the service request to any application server, and the application server reads and writes the database during the processing of the service request, and returns the result data after the processing is completed. To the user.
  • This multi-host service system can improve the stability of the system. Any failure of one server will not affect the normal service of the system, and can handle more user service requests at the same time.
  • the multi-host service system shown in FIG. 1 has an asynchronous request service for invoking a third-party server, its main architecture is as shown in FIG. 2, and a third-party server is added to the multi-host service system shown in FIG.
  • the working principle is as follows: 1. The user sends a service request to the forwarding server through the client; 2. The forwarding server randomly forwards the service request to any one of the application servers; 3 the application server will be asynchronous The service request is sent to the third-party server. 4. The application server receives a response of the asynchronous service request returned by the third-party server, and the response includes an identifier of the asynchronous service request. 5.
  • the application server returns the asynchronous service request according to the third-party server.
  • the identifier sends the polling request to the third-party server, where the polling request includes the identifier of the asynchronous service request; 6.
  • the application server receives the request result data corresponding to the identifier of the asynchronous service request returned by the third-party server; 7.
  • the application server is configured according to Obtaining the request result data update database; 8.
  • the forwarding server randomly forwards the query request to any one of the application servers; 10.
  • the application server is in the database. Query request knot Data, and returned to the user.
  • the application server polling the third-party server
  • the polling stops, the database is not updated, and the request in the third-party server is caused.
  • the result data is inconsistent with the data in the database, and the user cannot know the exact request result data.
  • the operation and maintenance personnel manually query whether the data in the database is consistent with the data in the third-party server.
  • the operation and maintenance personnel manually query whether the data in the database is consistent with the data in the third-party server.
  • the user cannot be sure to know the accurate request result data in time, and the labor cost is high, and the processing is Less efficient.
  • the invention provides an asynchronous service processing method and a server, which can automatically complete an uncompleted polling operation after a fault recovery without human intervention, and ensure that the request result data in the service provider is consistent with the data recorded by the service requester. Ensure that users are informed of accurate request result data in a timely manner, reducing labor costs and improving processing efficiency.
  • the present invention provides an asynchronous service processing method, including: obtaining, according to the recorded processing detail information of each service request, a service request that needs to re-request the result data to the service provider as a target service request; Resending a polling request to the service provider to request acquisition of result data of the target service request; receiving and recording result data of the target service request returned by the service provider.
  • the present invention provides an asynchronous service processing method, including: performing an asynchronous service processing flow for a service request; and recording processing detail information of the service request in a process of executing the asynchronous service processing flow.
  • the present invention provides a server, comprising: an obtaining module, configured to acquire, according to the recorded processing detailed information of each service request, a service request that needs to re-request the result data to the service provider as a target service request; the polling module And, for the target service request, resending a polling request to the service provider to request to obtain result data of the target service request; and a receiving module, configured to receive and record the returned by the service provider The result data of the target service request.
  • the present invention provides a server, including: an execution module, configured to execute an asynchronous service processing flow for a service request, and a second recording module, configured to execute the asynchronous service processing flow in the execution module And recording processing details of the service request.
  • the asynchronous service processing method and server acquires a service request that needs to re-request the result data to the service provider as a target service request according to the recorded processing detail information of each service request, and re-directs the target service request for the target service request.
  • the service provider sends a polling request to request the result data of the target service request, receives and records the result data of the target service request returned by the service provider, and ensures the request result data in the service provider. Consistent with the data recorded by the service requester, ensuring that the user knows the accurate request result data in time, because the human intervention is not required in the process, the labor cost is reduced, and the processing efficiency is improved.
  • FIG. 1 is a schematic structural diagram of an existing multi-host service system
  • FIG. 2 is a schematic diagram showing the architecture and working principle of an existing multi-host asynchronous service system
  • FIG. 3 is a schematic flowchart diagram of an embodiment of an asynchronous service processing method according to the present invention.
  • FIG. 4 is a schematic flowchart diagram of still another embodiment of an asynchronous service processing method according to the present invention.
  • FIG. 5 is a schematic flowchart of a possible implementation manner of the asynchronous service processing method in the embodiment shown in FIG. 4;
  • FIG. 6 is a schematic diagram of an architecture and interaction logic of the asynchronous service processing method shown in FIG. 5 applied to a multi-host asynchronous service system;
  • FIG. 7 is a schematic flowchart diagram of still another embodiment of an asynchronous service processing method according to the present invention.
  • FIG. 8 is a schematic flowchart diagram of still another embodiment of an asynchronous service processing method according to the present invention.
  • FIG. 9 is a schematic flowchart of a possible implementation manner of an asynchronous service processing method in the embodiment shown in FIG. 8;
  • FIG. 10 is a schematic diagram of an architecture and interaction logic of the asynchronous service processing method shown in FIG. 9 applied to a multi-host asynchronous service system;
  • FIG. 11 is a schematic structural diagram of an embodiment of a server provided by the present invention.
  • FIG. 12 is a schematic structural diagram of still another embodiment of a server provided by the present invention.
  • FIG. 3 is a schematic flowchart diagram of an embodiment of an asynchronous service processing method according to the present invention.
  • the asynchronous service processing method of the embodiment of the present invention can be applied to an asynchronous service requester, for example, an application server in the asynchronous service system shown in FIG. 2, which is a data recovery process of the asynchronous service system.
  • the asynchronous service processing method in the embodiment of the present invention may specifically include:
  • the embodiment of the present invention describes a data recovery process of asynchronous service request processing.
  • the asynchronous service requester obtains a service request that needs to re-request the result data to the service provider as the target service request according to the processed processing details of the service requests, that is, obtains the service request due to the failure to complete the polling operation as the target service request.
  • Re-performing the polling operation for the target service request that is, re-sending the polling request to the service provider to request the result data of the target service request, receiving and recording the result data of the target service request returned by the service provider to ensure the service
  • the provider's request result data is consistent with the result data recorded by the service requester.
  • the result data of the target service request returned by the service provider may be recorded in a local database, or may be recorded in other external storage media, such as a cloud disk, a mobile hard disk, or the like.
  • the asynchronous service processing method of the embodiment of the present invention acquires a service request that needs to re-request the result data to the service provider as a target service request according to the recorded processing detail information of each service request, and resends the service request to the service provider for the target service request. Polling the request to request the result data of the target service request, receiving and recording the result data of the target service request returned by the service provider, ensuring that the request result data in the service provider is consistent with the data recorded by the service requester, and ensuring the user Timely knowledge of accurate request result data, because no human intervention is required in the process, reducing labor costs and improving processing efficiency.
  • FIG. 4 is a schematic flowchart diagram of still another embodiment of an asynchronous service processing method according to the present invention.
  • the asynchronous service processing method of the embodiment of the present invention can be applied to an asynchronous service requester, for example, an application server in the asynchronous service system shown in FIG. 2, which is a data recovery process of the asynchronous service system.
  • the asynchronous service processing method in the embodiment of the present invention is a possible implementation manner of the asynchronous service processing method in the embodiment shown in FIG.
  • step S301 in the embodiment shown in FIG. 3 the processing detailed information of each service request may specifically include a receiving time and an execution status of each service request, and the execution status may specifically include a “send asynchronous request successful” status and “polishing result completion”. "status. Therefore, step S301 in the embodiment shown in FIG. 3 may specifically include the following steps S401-S402.
  • the service request that obtains the difference between the receiving time and the current time is greater than the specified time, and the execution state is the “send asynchronous request successful” state, to obtain the service request that is not completed due to the failure of the polling operation.
  • the specified time can be set according to requirements. Generally, a maximum polling duration is set, for example, 30 minutes. If the result has not been polled within 30 minutes, the asynchronous service processing is considered to be invalid, so the specified time can be set here.
  • the maximum polling duration is long, but it cannot be set too large to avoid excessive data recovery time, for example, set to 2 times the maximum polling duration.
  • step S404 is performed.
  • steps S403-S404 are the same as the steps S302-S303 in the embodiment shown in FIG. 3.
  • the steps S403-S404 are the same as the steps S302-S303 in the embodiment shown in FIG. 3.
  • the steps S403-S404 are the same as the steps S302-S303 in the embodiment shown in FIG. 3.
  • the steps S403-S404 are the same as the steps S302-S303 in the embodiment shown in FIG. 3.
  • the steps S403-S404 are the same as the steps S302-S303 in the embodiment shown in FIG. 3.
  • asynchronous service processing method of the embodiment of the present invention may further include:
  • step S405 when the polling operation is re-completed for the service request that has not completed the polling operation due to the fault, and the corresponding result data is obtained, the execution status of the service request is updated from the status of “sending asynchronous request success” to “ The polling result is completed, to prevent the service request from being acquired again as a service request for the incomplete polling operation, avoiding the pair The service requests to perform the polling operation again, causing waste of resources.
  • asynchronous service processing method of the embodiment of the present invention may further include:
  • step S403 if the polling request is not successfully transmitted, the following step S406 is performed.
  • step S406 After waiting for the set duration, returning to step S403 to resend the polling request to the service provider.
  • the polling operation for the service request can be quickly resumed if the fault time is short.
  • the setting duration can be set according to requirements. Generally, a maximum polling duration is set, for example, 30 minutes. If the result has not been polled within 30 minutes, the asynchronous service processing is considered to be unsuccessful, and it is unnecessary to poll continuously and waste. Resources, so here you can set the set duration to the maximum polling duration, for example 30 minutes.
  • step S406 may specifically include: if the polling request is not successfully sent, determine whether the set polling threshold is reached; if not, wait for the set duration and then return to step S403 to resend the polling request to the service provider.
  • the number of polling thresholds and the set duration can be set as needed.
  • the step S401 may specifically include: when the preset scan period arrives, acquiring, according to the processed processing detail information of each service request, a service request that needs to re-request the result data to the service provider as the target service request; or At the time of restart, a service request for requesting the result data of the service provider to be re-requested as the target service request is acquired according to the recorded processing details information of each service request.
  • the preset scan period can be set according to requirements. Generally, a maximum polling duration is set, for example, 30 minutes. If the result is not polled within 30 minutes, the asynchronous service processing is considered to be failed, so the pre-set can be set here. Set the scan period to be longer than the maximum polling duration. Try not to set too short, to avoid the asynchronous service processing has not been completed, and to obtain the service request that needs to re-request the result data to the service provider, for example, set to 10 times the maximum polling duration.
  • FIG. 5 is a schematic flowchart of a feasible implementation manner of the asynchronous service processing method in the embodiment shown in FIG.
  • the asynchronous service processing method of the embodiment shown in FIG. 4 is applied to the asynchronous service system shown in FIG. 2, where the application server serves as a service requester and the third-party server serves as a service provider, including:
  • the application server searches for a candidate record data in the database that is in the state of “sending the asynchronous service request success” and carries the identifier of the application server.
  • the candidate record data also carries the service request receiving time and the identifier of the asynchronous service request.
  • the application server calculates a difference between the receiving time of the service request and the current time in the candidate record data, and uses the candidate record data whose difference is greater than the specified time as the target record data.
  • the application server sends the polling request to the third-party server, where the polling request includes an identifier of the asynchronous service request carried in the target record data.
  • the application server determines whether a response to the successful polling request sent by the third-party server is received within the first set time. If no, step S505 is performed; if yes, step S507 is performed.
  • the first set time can be set as needed, and is generally set to 60 seconds or less, for example, 30 seconds.
  • the application server determines whether the polling threshold is reached. If yes, go back to step S501; if no, go to step S506.
  • the polling threshold can be set to 5 times.
  • the application server waits for the first set duration, and then returns to step S503.
  • the first set duration can be set to 6 minutes.
  • step S507. The application server determines whether the result of the successful polling request carries the result data. If no, step S508 is performed; if yes, step S509 is performed.
  • the application server waits for the second set duration, and then returns to step S503.
  • the second set duration can be set to 30 minutes.
  • the application server updates the corresponding target record data in the database according to the result data, and updates the status of the corresponding target record data to a “polling result completed” state.
  • the application server waits for the preset scan period to arrive and returns to step S501.
  • the preset scan period may be specifically.
  • FIG. 6 The architecture diagram of the multi-host asynchronous service system corresponding to the data recovery process of the asynchronous service processing method shown in FIG. 5 and the interaction logic of the data recovery process may be as shown in FIG. 6, including:
  • the multi-host asynchronous service system starts, and while executing the main process of the asynchronous service processing method, the data recovery process of the asynchronous service processing method is executed, and the application server starts timing.
  • the application server searches, in the database, the record data carrying the identifier of the application server, the status is “send asynchronous service request success”, and the difference between the receiving time of the service request and the current time is greater than the specified time as the target record data.
  • the application server sends the polling request to the third-party server, where the polling request includes an identifier of the asynchronous service request carried in the target record data.
  • the application server receives result data corresponding to the identifier of the asynchronous service request returned by the third-party server.
  • the application server updates the corresponding target record data in the database according to the obtained result data, and updates the status of the corresponding target record data to a “polling result completed” state.
  • the processing detailed information of each service request (including the receiving time and the execution state of each service request) describes the asynchronous service processing of the main process of the asynchronous service request processing in the following examples III and IV.
  • the method is recorded in the method, and the specific process will not be described here.
  • the asynchronous service processing method of the embodiment of the present invention acquires a service request that needs to re-request the result data to the service provider as a target service request according to the recorded processing detail information of each service request, and resends the service request to the service provider for the target service request. Polling the request to request the result data of the target service request, receiving and recording the result data of the target service request returned by the service provider, ensuring that the request result data in the service provider is consistent with the data recorded by the service requester, ensuring that the user is timely Obtain accurate request result data, because human intervention is not required in the process, which reduces labor costs and improves processing efficiency.
  • FIG. 7 is a schematic flowchart diagram of still another embodiment of an asynchronous service processing method according to the present invention.
  • the asynchronous service processing method of the embodiment of the present invention can be applied to an asynchronous service requesting party, for example, an application server in the asynchronous service system shown in FIG. 2, which is a main flow of the asynchronous service system, and can be combined with the following FIG.
  • the data recovery process of the asynchronous service processing method is implemented in combination or separately.
  • the asynchronous service processing method in the embodiment of the present invention may specifically include:
  • the processing detailed information of the service request in the process of executing the asynchronous service processing flow for the service request, it is convenient to record the services according to the data recovery process of the asynchronous service processing method shown in FIG. 3 to FIG. 5 above.
  • Request processing details information and obtain a service request that needs to re-request the result data to the service provider.
  • the result data of the target service request returned by the service provider may be recorded in a local database, or may be recorded in other external storage media, such as a cloud disk, a mobile hard disk, or the like.
  • the asynchronous service processing method of the embodiment of the present invention records the processing detailed information of the service request in the process of executing the asynchronous service processing flow for the service request, so that the processing detailed information of the service request corresponding to different stages in the processing process is different, and is convenient for
  • the service request for the unfinished polling operation is searched, and the polling operation is automatically completed, so that the request result data in the service provider is consistent with the data recorded by the service requester, and the user is sure to know the accurate request result data in time, because No human intervention is required in the process, which reduces labor costs and improves handling. effectiveness.
  • FIG. 8 is a schematic flowchart diagram of still another embodiment of an asynchronous service processing method according to the present invention.
  • the asynchronous service processing method of the embodiment of the present invention can be applied to an asynchronous service requesting party, for example, an application server in the asynchronous service system shown in FIG. 2, which is a main flow of the asynchronous service system, and can be combined with the following FIG.
  • the data recovery process of the asynchronous service processing method is implemented in combination or separately.
  • the asynchronous service processing method in the embodiment of the present invention is a possible implementation manner of the asynchronous service processing method in the embodiment shown in FIG.
  • Step S701 in the embodiment shown in FIG. 7 may specifically include the following steps S801-S805.
  • step S803 if the asynchronous request is successfully transmitted, the following step S805 is performed.
  • the asynchronous service requester receives the service request, and sends an asynchronous request to the service provider for the service request, and if the asynchronous request is successfully sent, sends a polling request to the service provider to request the result data of the service request.
  • step S702 in the embodiment shown in FIG. 7 may specifically include at least one of the following steps S802-S806:
  • step S802 After receiving the service request in step S801, the following step S802 is performed.
  • step S804 if the asynchronous request is successfully sent, the following step S804 is performed.
  • the execution status of the record service request is a status of “send asynchronous request success”.
  • step S806 if the polling request is successfully transmitted, the following step S806 is performed.
  • asynchronous service processing method of the embodiment of the present invention may further include:
  • step S805 if the polling request is not successfully transmitted, the following step S807 is performed.
  • step S807 after waiting for the set time, returning to step S805 to resend the polling request to the service provider.
  • this step can attempt to quickly resume the polling operation on the service request in the case that the fault time is short.
  • the setting duration refer to the related description in the foregoing embodiment shown in FIG. 4, and details are not described herein again.
  • step S807 may specifically include: if the polling request is not successfully sent, determining whether the set polling threshold is reached; if not, waiting for the set duration, then returning to step S805 to resend the polling request to the service provider.
  • the polling number threshold and the setting duration refer to the related description in the embodiment shown in FIG. 4 above, and details are not described herein again.
  • FIG. 9 is a schematic flowchart of a possible implementation manner of the asynchronous service processing method in the embodiment shown in FIG.
  • the asynchronous service processing method of the embodiment shown in FIG. 8 is applied to the asynchronous service system shown in FIG. 2, where the application server serves as a service requester and the third-party server serves as a service provider, including:
  • the application server receives a service request sent by the forwarding server.
  • the application server stores the record data corresponding to the service request in a database, where the record data includes a receiving time of the service request and an identifier of the application server.
  • the application server sends an asynchronous service request corresponding to the service request to the third-party server.
  • the application server determines whether a response to the asynchronous service request sent by the third-party server is successfully received within the second set time. If not, execute S905; if yes, execute S906.
  • the second set time can be set as needed, and is generally set to 60 seconds or less, for example, 30 seconds.
  • S905 The application server sends a notification message that the asynchronous service request fails to the forwarding server, and ends the process.
  • S906 The application server sets the status of the record data to a “send asynchronous service request success” state, and adds an identifier of the asynchronous service request carried in the response of the asynchronous service request success to the record data.
  • the application server sends the polling request to the third-party server, and the polling request includes an identifier of the asynchronous service request.
  • step S908 The application server determines whether a response to the successful polling request sent by the third-party server is received within the first set time. If no, step S909 is performed; if yes, step S911 is performed.
  • the first set time can be set as needed, and is generally set to 60 seconds or less, for example, 30 seconds.
  • step S909 The application server determines whether the polling threshold is reached. If yes, the process ends; if not, step S910 is performed.
  • the polling threshold can be set to 5 times.
  • the application server waits for the first set duration, and then returns to step S907.
  • the first set duration can be set to 6 minutes.
  • step S911 The application server determines whether the result of the successful polling request carries the result data. If no, step S912 is performed; if yes, step S913 is performed.
  • the application server waits for the second set duration, and then returns to step S907.
  • the second set duration can be set It is 30 minutes.
  • S913 The application server updates the corresponding record data in the database according to the result data, and updates the status of the corresponding record data to a “polishing result completion” state, and ends the process.
  • FIG. 10 The architecture diagram of the multi-host asynchronous service system corresponding to the main process of the asynchronous service processing method shown in FIG. 9 and the interaction logic of the main process may be as shown in FIG. 10, including:
  • the multi-host asynchronous service system starts and executes the main flow of the asynchronous service processing method.
  • S1001 The user sends a service request to the forwarding server through the client.
  • S1002 The forwarding server randomly forwards the service request to any one of the application servers.
  • the application server stores the receiving time of the service request and the identifier of the application server into corresponding record data in the database.
  • S1004 The application server sends an asynchronous service request to the third-party server.
  • the application server receives a response of the asynchronous service request returned by the third-party server, where the response includes an identifier of the asynchronous service request.
  • S1006 The application server sets the state of the corresponding record data in the database to the “send asynchronous service request success” state.
  • the application server sends the polling request to the third-party server according to the identifier of the asynchronous service request returned by the third-party server, where the polling request includes an identifier of the asynchronous service request.
  • the application server receives result data corresponding to the identifier of the asynchronous service request returned by the third-party server.
  • the application server updates the corresponding record data in the database according to the obtained request result data, and updates the status of the corresponding record data to a “polishing result completed” state.
  • S1011 The forwarding server randomly forwards the query request to any one of the application servers.
  • S1012 The application server queries the result data in the database and returns it to the user.
  • the asynchronous service processing method of the embodiment of the present invention acquires a service request that needs to re-request the result data to the service provider as a target service request according to the recorded processing detail information of each service request, and resends the service request to the service provider for the target service request. Polling the request to request the result data of the target service request, receiving and recording the result data of the target service request returned by the service provider, ensuring that the request result data in the service provider is consistent with the data recorded by the service requester, ensuring that the user is informed Accurate request result data, because no human intervention is required in the process, reducing labor costs and improving processing efficiency.
  • FIG. 11 is a schematic structural diagram of an embodiment of a server provided by the present invention.
  • the server of the embodiment of the present invention corresponds to the service requester in the embodiment shown in FIG. 3 to FIG. 5, and the asynchronous service processing method in any of the embodiments shown in FIG. 3 to FIG. 5 can be executed.
  • the server of the embodiment of the present invention may specifically include an obtaining module 111, a polling module 112, and a receiving module 113, where:
  • the obtaining module 111 is configured to obtain, according to the recorded processing detail information of each service request, a service request that needs to re-request the result data to the service provider as the target service request;
  • the polling module 112 is configured to resend a polling request to the service provider for the target service request to request to obtain the result data of the target service request;
  • the receiving module 113 is configured to receive and record result data of the target service request returned by the service provider.
  • the processing detailed information of each service request includes a receiving time and an execution status of each service request.
  • the obtaining module 111 is specifically configured to: obtain a service request in a success state of sending an asynchronous request as a candidate service request according to an execution state of each service request; calculate a difference between a receiving time of the candidate service request and a current time, and obtain a difference A service request that is greater than the specified time is requested as a target service.
  • the receiving module 113 is further configured to: when the service provider successfully returns the result data of the target service request, update the execution status of the target service request to a polling result completion status.
  • the polling module 112 is further configured to: if the polling request is not successfully sent, wait for the set duration and then resend the polling request to the service provider.
  • the polling module 112 is further configured to: determine whether the set polling threshold is reached before re-sending the polling request to the service provider after waiting for the set duration; if not, execute the waiting for the set duration and then restart The step of sending a polling request to the service provider.
  • the obtaining module 111 is specifically configured to: when the preset scan period arrives, obtain a service request that needs to re-request the result data to the service provider as the target service request according to the processed processing detail information of each service request; or At the time of the second restart, the service request that needs to re-request the result data to the service provider is acquired as the target service request according to the recorded processing details information of each service request.
  • the obtaining module 111 is further configured to: perform asynchronous service processing for each service request before acquiring a service request that needs to re-request the result data to the service provider as the target service request according to the processed detailed information of the service request of the record. In the process of the process, the processing details of each service request are recorded.
  • the obtaining module 111 is specifically configured to perform at least one of the following operations: when receiving each service request Recording the receiving time of each service request; when the asynchronous request is successfully sent to the service provider for each service request, the execution status of each service request is recorded as the asynchronous request success status; when the service provider successfully returns the result of each service request When the data is updated, the execution status of each service request is updated to the polling result completion status.
  • the server acquires a service request that needs to re-request the result data to the service provider as a target service request according to the recorded processing detail information of each service request, and resends the polling request to the service provider for the target service request.
  • receiving and recording the result data of the target service request returned by the service provider ensures that the request result data in the service provider is consistent with the data recorded by the service requester, ensuring that the user is accurately informed in time. Requesting result data, because no human intervention is required in the process, the labor cost is reduced, and the processing efficiency is improved.
  • FIG. 12 is a schematic structural diagram of an embodiment of a server provided by the present invention.
  • the server of the embodiment of the present invention corresponds to the service requester in the embodiment shown in FIG. 7 to FIG. 9, and the asynchronous service processing method in any of the embodiments shown in FIG. 7 to FIG. 9 can be executed.
  • the server of the embodiment of the present invention may specifically include an execution module 121 and a recording module 122, where:
  • the execution module 121 is configured to execute an asynchronous service processing flow for the service request.
  • the recording module 122 is configured to record processing details of the service request during the execution of the asynchronous service processing flow by the execution module.
  • the execution module 121 is specifically configured to: receive a service request; send an asynchronous request to the service provider for the service request; and send a polling request to the service provider to request the result data of the service request if the asynchronous request is successfully sent.
  • the recording module 122 is specifically configured to perform at least one operation of: recording a service request receiving time when receiving the service request; and recording an execution status of the service request when successfully sending the asynchronous request to the service provider for the service request To send an asynchronous request success status; when the service provider successfully returns the result data of each service request, the execution status of the update service request is the polling result completion status.
  • execution module 121 is further configured to: if the polling request is not successfully sent, wait for the set duration and then resend the polling request to the service provider.
  • the execution module 121 is further configured to: resend the polling to the service provider after waiting for the set duration Before the request, it is judged whether the set polling threshold is reached; if not, the step of resending the polling request to the service provider after waiting for the set duration is executed.
  • the server of the embodiment of the present invention records the processing detail information of the service request in the process of executing the asynchronous service processing procedure for the service request, so that the processing details of the service request corresponding to different stages in the processing process are different, which is convenient after the fault is recovered.
  • the aforementioned program can be stored in a computer readable storage medium.
  • the program when executed, performs the steps including the foregoing method embodiments; and the foregoing storage medium includes various media that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer And Data Communications (AREA)

Abstract

本发明提供了一种异步服务处理方法及服务器。该方法包括：根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求；针对所述目标服务请求，重新向所述服务提供方发送轮询请求，以请求获取所述目标服务请求的结果数据；接收并记录所述服务提供方返回的所述目标服务请求的结果数据。本发明提供的异步服务处理方法及服务器，保证了服务提供方中的请求结果数据与服务请求方记录的数据一致，确保用户及时获知准确的请求结果数据，由于过程中无需人力参与，降低了人力成本，提高了处理效率。

Description

异步服务处理方法及服务器
本申请要求2016年02月04日递交的申请号为201610080674.6、发明名称为“异步服务处理方法及服务器”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及计算机技术领域，尤其涉及一种异步服务处理方法及服务器。
背景技术
目前，有些网络(web)服务系统，为了保障高可靠性，经常会采用多主机冗余的系统提供服务，其主要架构如图1所示，包括一台转发服务器(为了防止单点故障，通常会有两台或者多台主备转发服务器，如果当前的主转发服务器故障则自动切换到备转发服务器，但通常同一时间只有一台转发服务器投入使用)、多台相同的应用服务器(每台应用服务器提供完全相同的服务并且同时运行)和一个数据库。其工作原理如下：用户向转发服务器发出服务请求，转发服务器将该服务请求随机转发到任意一台应用服务器，应用服务器处理该服务请求的过程中会读写数据库，处理完成后再将结果数据返回给用户。这种多主机服务系统可以提高系统的稳定性，任何一台服务器故障不会影响该系统正常提供服务，同时可以同时处理更多的用户服务请求。
如果图1所示的多主机服务系统中有调用第三方服务器的异步请求服务，则其主要架构如图2所示，在图1所示的多主机服务系统的基础上增加了第三方服务器。若异步请求结果采用轮询模式，则其工作原理如下：1、用户通过客户端向转发服务器发出服务请求；2、转发服务器将该服务请求随机转发到任意一台应用服务器；3应用服务器将异步服务请求发送至第三方服务器；4、应用服务器接收第三方服务器返回的异步服务请求成功的响应，该响应中包括异步服务请求的标识；5、应用服务器根据第三方服务器返回的该异步服务请求的标识将轮询请求发送至第三方服务器，该轮询请求中包括异步服务请求的标识；6、应用服务器接收第三方服务器返回的与异步服务请求的标识对应的请求结果数据；7、应用服务器根据获取到的请求结果数据更新数据库；8、用户想查询请求结果数据时，向转发服务器发出查询请求；9、转发服务器将该查询请求随机转发到任意一台应用服务器；10、应用服务器在数据库中查询请求结果数据，并返回给用户。
在应用服务器轮询第三方服务器的过程中，若应用服务器因故障或升级发布停机或网络异常导致应用服务器无法连接上第三方服务器，则轮询停止，数据库不更新，导致第三方服务器中的请求结果数据与数据库中的数据不一致，用户无法获知准确的请求结果数据。
为保证第三方服务器中的请求结果数据与数据库中的数据一致，确保用户获知准确的请求结果数据，现有技术中通过运维人员手动查询数据库中的数据与第三方服务器中的数据是否一致，来确定未完成轮询操作的数据，并手动订正数据库中未完成轮询操作的数据来恢复数据，但由于为事后处理，无法保证用户及时获知准确的请求结果数据，且人力成本较高，处理效率较低。
发明内容
本发明提供一种异步服务处理方法及服务器，无需人力参与，即可实现在故障恢复后自动完成未完成的轮询操作，保证服务提供方中的请求结果数据与服务请求方记录的数据一致，确保用户及时获知准确的请求结果数据，降低了人力成本，提高了处理效率。
为达到上述目的，本发明采用如下技术方案：
一方面，本发明提供一种异步服务处理方法，包括：根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求；针对所述目标服务请求，重新向所述服务提供方发送轮询请求，以请求获取所述目标服务请求的结果数据；接收并记录所述服务提供方返回的所述目标服务请求的结果数据。
另一方面，本发明提供一种异步服务处理方法，包括：针对服务请求，执行异步服务处理流程；在执行所述异步服务处理流程的过程中，记录所述服务请求的处理详情信息。
另一方面，本发明提供一种服务器，包括：获取模块，用于根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求；轮询模块，用于针对所述目标服务请求，重新向所述服务提供方发送轮询请求，以请求获取所述目标服务请求的结果数据；接收模块，用于接收并记录所述服务提供方返回的所述目标服务请求的结果数据。
另一方面，本发明提供一种服务器，包括：执行模块，用于针对服务请求，执行异步服务处理流程；第二记录模块，用于在所述执行模块执行所述异步服务处理流程的过程中，记录所述服务请求的处理详情信息。
本发明提供的异步服务处理方法及服务器，根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求，针对所述目标服务请求，重新向所述服务提供方发送轮询请求，以请求获取所述目标服务请求的结果数据，接收并记录所述服务提供方返回的所述目标服务请求的结果数据，保证了服务提供方中的请求结果数据与服务请求方记录的数据一致，确保用户及时获知准确的请求结果数据，由于过程中无需人力参与，降低了人力成本，提高了处理效率。
上述说明仅是本发明技术方案的概述，为了能够更清楚了解本发明的技术手段，而可依照说明书的内容予以实施，并且为了让本发明的上述和其它目的、特征和优点能够更明显易懂，以下特举本发明的具体实施方式。
附图说明
通过阅读下文优选实施方式的详细描述，各种其他的优点和益处对于本领域普通技术人员将变得清楚明了。附图仅用于示出优选实施方式的目的，而并不认为是对本发明的限制。而且在整个附图中，用相同的参考符号表示相同的部件。在附图中：
图1为现有的多主机服务系统的架构示意图；
图2为现有的多主机异步服务系统的架构及工作原理示意图；
图3为本发明提供的异步服务处理方法一个实施例的流程示意图；
图4为本发明提供的异步服务处理方法又一个实施例的流程示意图；
图5为图4所示实施例的异步服务处理方法一种可行实施方式的流程示意图；
图6为图5所示的异步服务处理方法应用于多主机异步服务系统的架构及交互逻辑示意图；
图7为本发明提供的异步服务处理方法又一个实施例的流程示意图；
图8为本发明提供的异步服务处理方法又一个实施例的流程示意图；
图9为图8所示实施例的异步服务处理方法一种可行实施方式的流程示意图；
图10为图9所示的异步服务处理方法应用于多主机异步服务系统的架构及交互逻辑示意图；
图11为本发明提供的服务器一个实施例的结构示意图；
图12为本发明提供的服务器又一个实施例的结构示意图。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
下面结合附图对本发明实施例的异步服务处理方法及服务器进行详细描述。
实施例一
图3为本发明提供的异步服务处理方法一个实施例的流程示意图。本发明实施例的异步服务处理方法可应用于异步服务请求方，例如图2所示的异步服务系统中的应用服务器中，为异步服务系统的数据恢复流程。如图3所示，本发明实施例的异步服务处理方法具体可包括：
S301，根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求。
S302，针对目标服务请求，重新向服务提供方发送轮询请求，以请求获取目标服务请求的结果数据。
S303，接收并记录服务提供方返回的目标服务请求的结果数据。
具体的，本发明实施例描述了异步服务请求处理的数据恢复流程。异步服务请求方根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求，即获取因故障未完成轮询操作的服务请求作为目标服务请求。针对目标服务请求，重新执行轮询操作，即重新向服务提供方发送轮询请求，以请求获取目标服务请求的结果数据，接收并记录服务提供方返回的目标服务请求的结果数据，以保证服务提供方的请求结果数据与服务请求方记录的结果数据一致。其中，可以将服务提供方返回的目标服务请求的结果数据记录在本地数据库中，也可以记录在外部的其他存储介质中，例如云盘、移动硬盘等中。
本发明实施例的异步服务处理方法，根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求，针对目标服务请求，重新向服务提供方发送轮询请求，以请求获取目标服务请求的结果数据，接收并记录服务提供方返回的目标服务请求的结果数据，保证了服务提供方中的请求结果数据与服务请求方记录的数据一致，确保用户及时获知准确的请求结果数据，由于过程中无需人力参与，降低了人力成本，提高了处理效率。
实施例二
图4为本发明提供的异步服务处理方法又一个实施例的流程示意图。本发明实施例的异步服务处理方法可应用于异步服务请求方，例如图2所示的异步服务系统中的应用服务器中，为异步服务系统的数据恢复流程。如图4所示，本发明实施例的异步服务处理方法为图3所示实施例的异步服务处理方法的一种可行实施方式，具体可包括：
图3所示实施例中的步骤S301中，各服务请求的处理详情信息具体可包括各服务请求的接收时间和执行状态，执行状态具体可包括“发送异步请求成功”状态和“轮询结果完成”状态。因此图3所示实施例中的步骤S301具体可包括如下步骤S401-S402。
S401，根据各服务请求的执行状态，获取处于“发送异步请求成功”状态的服务请求作为候选服务请求。
S402，计算候选服务请求的接收时间与当前时间的差值，获取差值大于指定时间的服务请求作为目标服务请求。
具体的，步骤S401-S402中，通过获取接收时间与当前时间的差值大于指定时间，且执行状态为“发送异步请求成功”状态的服务请求，以获取因故障未完成轮询操作的服务请求。其中，指定时间可以根据需要设定，一般会设置一个最大轮询时长，例如30分钟，30分钟内还未轮询到结果，则认为此次异步服务处理失败，因此此处可设置指定时间大于最大轮询时长，但也不能设置过大，避免数据恢复时间过长，例如设置为最大轮询时长的2倍。
S403，针对目标服务请求，重新向服务提供方发送轮询请求，以请求获取目标服务请求的结果数据。
若轮询请求发送成功，则执行以下步骤S404。
S404，接收并记录服务提供方返回的目标服务请求的结果数据。
具体的，步骤S403-S404与图3所示实施例中的步骤S302-S303相同，具体过程可参见图3所示实施例中的相关描述，此处不再赘述。
进一步的，本发明实施例的异步服务处理方法还可包括：
S405，当服务提供方成功返回目标服务请求的结果数据时，更新目标服务请求的执行状态为“轮询结果完成”状态。
具体的，本步骤S405当对因故障未完成轮询操作的服务请求重新完成轮询操作，获取到对应的结果数据后，将该服务请求的执行状态由“发送异步请求成功”状态更新为“轮询结果完成”，避免该服务请求再次被获取为未完成轮询操作的服务请求，避免对 该服务请求再次执行轮询操作，造成资源浪费。
进一步的，本发明实施例的异步服务处理方法还可包括：
在步骤S403之后，若未成功发送轮询请求，则执行以下步骤S406。
S406，等待设定时长后返回步骤S403重新向服务提供方发送轮询请求。
具体的，在发送轮询请求失败的情况下，通过本步骤S406可在故障时间较短的情况下，尝试快速恢复对服务请求的轮询操作。其中，设定时长可根据需要设定，一般会设置一个最大轮询时长，例如30分钟，30分钟内还未轮询到结果，则认为此次异步服务处理失败，没必要一直轮询，浪费资源，因此此处可设置设定时长为最大轮询时长，例如30分钟。
进一步的，步骤S406具体可包括：若未成功发送轮询请求，判断是否达到设定的轮询次数阈值；若否，则等待设定时长后返回步骤S403重新向服务提供方发送轮询请求。
具体的，轮询次数阈值和设定时长可根据需要设定，一般会设置一个最大轮询时长，例如30分钟，而最大轮询时长＝轮询次数*(轮询间隔+轮询操作需要的时间)，轮询操作需要的时间一般为毫秒级别可以忽略不计，因此可认为最大轮询时长＝轮询次数*轮询间隔，因此可设置轮询次数为5次，轮询间隔即设定时长为6分钟等组合方式。
进一步的，步骤S401具体可包括：当预设扫描周期到达时，根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求；或者在每次重新启动时，根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求。其中，预设扫描周期可以根据需要设定，一般会设置一个最大轮询时长，例如30分钟，30分钟内还未轮询到结果，则认为此次异步服务处理失败，因此此处可设置预设扫描周期大于最大轮询时长，尽量不要设置过短，避免异步服务处理还未完成，又去获取需要重新向服务提供方请求结果数据的服务请求，例如设置为最大轮询时长的10倍。
为更清楚的说明本发明实施例的异步服务处理方法的具体过程，图5给出了图4所示实施例的异步服务处理方法一种可行实施方式的流程示意图。如图5所示，图4所示实施例的异步服务处理方法应用于图2所示的异步服务系统中，应用服务器作为服务请求方，第三方服务器作为服务提供方，包括：
S501，应用服务器在数据库中查找状态为“发送异步服务请求成功”状态且携带有应用服务器的标识的候选记录数据，候选记录数据中还携带有服务请求的接收时间和异步服务请求的标识。
S502，应用服务器计算候选记录数据中服务请求的接收时间与当前时间的差值，将差值大于指定时间的候选记录数据作为目标记录数据。其中，指定时间可设置为30分钟*2＝60分钟。
S503，应用服务器将轮询请求发送至第三方服务器，轮询请求中包括目标记录数据中携带的异步服务请求的标识。
S504，应用服务器判断在第一设定时间内是否接收到第三方服务器发送的轮询请求成功的响应。若否，则执行步骤S505；若是，则执行步骤S507。其中，第一设定时间可以根据需要设定，一般设置为60秒以下，例如30秒。
S505，应用服务器判断是否达到轮询次数阈值。若是，则返回步骤S501；若否，则执行步骤S506。其中，轮询次数阈值可设置为5次。
S506，应用服务器等待第一设定时长后返回步骤S503。其中，第一设定时长可设置为6分钟。
S507，应用服务器判断轮询请求成功的响应中是否携带有结果数据。若否，则执行步骤S508；若是，则执行步骤S509。
S508，应用服务器等待第二设定时长后返回步骤S503。其中，第二设定时长可设置为30分钟。
S509，应用服务器根据结果数据更新数据库中对应的目标记录数据，并将对应的目标记录数据的状态更新为“轮询结果完成”状态。
S510，应用服务器等待预设扫描周期到达后返回步骤S501。其中，预设扫描周期具体可以为。其中，预设扫描周期可设置为30分钟*10＝300分钟。
上述图5所示的异步服务处理方法的数据恢复流程对应的多主机异步服务系统的架构图及数据恢复流程的交互逻辑可如图6所示，包括：
多主机异步服务系统启动，在执行异步服务处理方法的主流程的同时，执行异步服务处理方法的数据恢复流程，应用服务器开始计时。
S601，应用服务器在数据库中查找携带有应用服务器的标识、状态为“发送异步服务请求成功”且服务请求的接收时间与当前时间的差值大于指定时间的记录数据作为目标记录数据。
S602，应用服务器将轮询请求发送至第三方服务器，轮询请求中包括目标记录数据中携带的异步服务请求的标识。
S603，应用服务器接收第三方服务器返回的与异步服务请求的标识对应的结果数据。
S604，应用服务器根据获取到的结果数据更新数据库中对应的目标记录数据，并将对应的目标记录数据的状态更新为“轮询结果完成”状态。
此处需要说明的是，本发明实施例中各服务请求的处理详情信息(包括各服务请求的接收时间和执行状态)在下述实例三、四中描述异步服务请求处理的主流程的异步服务处理方法中进行记录，具体过程此处不再赘述。
本发明实施例的异步服务处理方法，根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求，针对目标服务请求，重新向服务提供方发送轮询请求，以请求获取目标服务请求的结果数据，接收并记录服务提供方返回的目标服务请求的结果数据保证了服务提供方中的请求结果数据与服务请求方记录的数据一致，确保用户及时获知准确的请求结果数据，由于过程中无需人力参与，降低了人力成本，提高了处理效率。
实施例三
图7为本发明提供的异步服务处理方法又一个实施例的流程示意图。本发明实施例的异步服务处理方法可应用于异步服务请求方，例如图2所示的异步服务系统中的应用服务器中，为异步服务系统的主流程，可与图3-图5所示的异步服务处理方法的数据恢复流程相结合实施，也可单独实施。如图7所示，本发明实施例的异步服务处理方法具体可包括：
S701，针对服务请求，执行异步服务处理流程。
S702，在执行异步服务处理流程的过程中，记录服务请求的处理详情信息。
具体的，通过在针对服务请求执行异步服务处理流程的过程中，记录服务请求的处理详情信息，方便在上述图3-图5所示的异步服务处理方法的数据恢复流程中根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求。其中，可以将服务提供方返回的目标服务请求的结果数据记录在本地数据库中，也可以记录在外部的其他存储介质中，例如云盘、移动硬盘等中。
本发明实施例的异步服务处理方法，通过在针对服务请求执行异步服务处理流程的过程中，记录服务请求的处理详情信息，使得处理过程中不同阶段对应的服务请求的处理详情信息不同，便于在故障恢复后查找未完成轮询操作的服务请求，并自动完成轮询操作，保证了服务提供方中的请求结果数据与服务请求方记录的数据一致，确保用户及时获知准确的请求结果数据，由于过程中无需人力参与，降低了人力成本，提高了处理 效率。
实施例四
图8为本发明提供的异步服务处理方法又一个实施例的流程示意图。本发明实施例的异步服务处理方法可应用于异步服务请求方，例如图2所示的异步服务系统中的应用服务器中，为异步服务系统的主流程，可与图3-图5所示的异步服务处理方法的数据恢复流程相结合实施，也可单独实施。如图8所示，本发明实施例的异步服务处理方法为图7所示实施例的异步服务处理方法的一种可行实施方式，具体可包括：
图7所示实施例中的步骤S701具体可包括如下步骤S801-S805。
S801，接收服务请求。
S803，针对服务请求，向服务提供方发送异步请求。
在步骤S803之后，若成功发送异步请求，则执行以下步骤S805。
S805，向服务提供方发送轮询请求，以请求服务请求的结果数据。
具体的，异步服务请求方接收服务请求，针对该服务请求，向服务提供方发送异步请求，若成功发送异步请求，向服务提供方发送轮询请求，以请求服务请求的结果数据。
进一步的，图7所示实施例中的步骤S702具体可包括以下步骤S802-S806中的至少一个步骤：
在步骤S801接收到服务请求之后，执行以下步骤S802。
S802，记录服务请求的接收时间。
在步骤S803之后，若发送异步请求成功，则执行以下步骤S804。
S804，记录服务请求的执行状态为“发送异步请求成功”状态。
在步骤S805之后，若成功发送轮询请求，则执行以下步骤S806。
S806，当服务提供方成功返回各服务请求的结果数据时，更新服务请求的执行状态为“轮询结果完成”状态。
进一步的，本发明实施例的异步服务处理方法还可包括：
在步骤S805之后，若未成功发送轮询请求，则执行以下步骤S807。
S807，等待设定时长后返回步骤S805重新向服务提供方发送轮询请求。
具体的，在发送轮询请求失败的情况下，通过本步骤可在故障时间较短的情况下，尝试快速恢复对服务请求的轮询操作。其中，设定时长的设置可参见上述图4所示实施例中的相关描述，此处不再赘述。
进一步的，步骤S807具体可包括：若未成功发送轮询请求，判断是否达到设定的轮询次数阈值；若否，则等待设定时长后返回步骤S805重新向服务提供方发送轮询请求。其中，轮询次数阈值和设定时长的设置可参见上述图4所示实施例中的相关描述，此处不再赘述。
为更清楚的说明本发明实施例的异步服务处理方法的具体过程，图9给出了图8所示实施例的异步服务处理方法一种可行实施方式的流程示意图。如图9所示，图8所示实施例的异步服务处理方法应用于图2所示的异步服务系统中，应用服务器作为服务请求方，第三方服务器作为服务提供方，包括：
S901，应用服务器接收转发服务器发送的服务请求。
S902，应用服务器将与服务请求对应的记录数据存储至数据库中，记录数据包括服务请求的接收时间和应用服务器的标识。
S903，应用服务器将与服务请求对应的异步服务请求发送至第三方服务器。
S904，应用服务器判断在第二设定时间内是否接收到第三方服务器发送的异步服务请求成功的响应。若否，则执行S905；若是，则执行S906。其中，第二设定时间可根据需要进行设置，一般设置为60秒以下，例如30秒。
S905，应用服务器将异步服务请求失败的通知消息发送至转发服务器，结束流程。
S906，应用服务器将记录数据的状态设置为“发送异步服务请求成功”状态，并将异步服务请求成功的响应中携带的异步服务请求的标识添加到记录数据中。
S907，应用服务器将轮询请求发送至第三方服务器，轮询请求中包括异步服务请求的标识。
S908，应用服务器判断第一设定时间内是否接收到第三方服务器发送的轮询请求成功的响应。若否，则执行步骤S909；若是，则执行步骤S911。其中，第一设定时间可以根据需要设定，一般设置为60秒以下，例如30秒。
S909，应用服务器判断是否达到轮询次数阈值。若是，则结束流程；若否，则执行步骤S910。其中，轮询次数阈值可设置为5次。
S910，应用服务器等待第一设定时长后返回步骤S907。其中，第一设定时长可设置为6分钟。
S911，应用服务器判断轮询请求成功的响应中是否携带有结果数据。若否，则执行步骤S912；若是，则执行步骤S913。
S912，应用服务器等待第二设定时长后返回步骤S907。其中，第二设定时长可设置 为30分钟。
S913，应用服务器根据结果数据更新数据库中对应的记录数据，并将对应的记录数据的状态更新为“轮询结果完成”状态，结束流程。
上述图9所示的异步服务处理方法的主流程对应的多主机异步服务系统的架构图及主流程的交互逻辑可如图10所示，包括：
多主机异步服务系统启动，执行异步服务处理方法的主流程。
S1001，用户通过客户端向转发服务器发出服务请求。
S1002，转发服务器将该服务请求随机转发到任意一台应用服务器。
S1003，应用服务器将服务请求的接收时间和应用服务器的标识存储至数据库中对应的记录数据中。
S1004，应用服务器将异步服务请求发送至第三方服务器。
S1005，应用服务器接收第三方服务器返回的异步服务请求成功的响应，该响应中包括异步服务请求的标识。
S1006，应用服务器将数据库中对应的记录数据的状态设置为“发送异步服务请求成功”状态。
S1007，应用服务器根据第三方服务器返回的该异步服务请求的标识将轮询请求发送至第三方服务器，该轮询请求中包括异步服务请求的标识。
S1008，应用服务器接收第三方服务器返回的与异步服务请求的标识对应的结果数据。
S1009，应用服务器根据获取到的请求结果数据更新数据库中对应的记录数据，并将对应的记录数据的状态更新为“轮询结果完成”状态。
S1010，用户想查询结果数据时，向转发服务器发出查询请求。
S1011，转发服务器将该查询请求随机转发到任意一台应用服务器。
S1012，应用服务器在数据库中查询结果数据，并返回给用户。
本发明实施例的异步服务处理方法，根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求，针对目标服务请求，重新向服务提供方发送轮询请求，以请求获取目标服务请求的结果数据，接收并记录服务提供方返回的目标服务请求的结果数据保证了服务提供方中的请求结果数据与服务请求方记录的数据一致，确保用户获知准确的请求结果数据，由于过程中无需人力参与，降低了人力成本，提高了处理效率。
实施例五
图11为本发明提供的服务器一个实施例的结构示意图。本发明实施例的服务器对应图3-图5所示实施例中的服务请求方，可执行图3-图5所示任一实施例中的异步服务处理方法。如图11所示，本发明实施例的服务器具体可包括获取模块111、轮询模块112和接收模块113，其中：
获取模块111，用于根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求；
轮询模块112，用于针对目标服务请求，重新向服务提供方发送轮询请求，以请求获取目标服务请求的结果数据；
接收模块113，用于接收并记录服务提供方返回的目标服务请求的结果数据。
其中，各服务请求的处理详情信息包括各服务请求的接收时间和执行状态。
进一步的，获取模块111具体可用于：根据各服务请求的执行状态，获取处于发送异步请求成功状态的服务请求作为候选服务请求；计算候选服务请求的接收时间与当前时间的差值，获取差值大于指定时间的服务请求作为目标服务请求。
进一步的，接收模块113还可用于：当服务提供方成功返回目标服务请求的结果数据时，更新目标服务请求的执行状态为轮询结果完成状态。
进一步的，轮询模块112还可用于：若未成功发送轮询请求，等待设定时长后重新向服务提供方发送轮询请求。
进一步的，轮询模块112还可用于：在等待设定时长后重新向服务提供方发送轮询请求之前，判断是否达到设定的轮询次数阈值；若否，则执行等待设定时长后重新向服务提供方发送轮询请求的步骤。
进一步的，获取模块111具体可用于：当预设扫描周期到达时，根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求；或者在每次重新启动时，根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求。
进一步的，获取模块111还可用于：在根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求之前，在针对各服务请求执行异步服务处理流程的过程中，记录各服务请求的处理详情信息。
进一步的，获取模块111具体可用于执行以下至少一种操作：当接收到各服务请求 时，记录各服务请求的接收时间；当针对各服务请求成功向服务提供方发送异步请求时，记录各服务请求的执行状态为发送异步请求成功状态；当服务提供方成功返回各服务请求的结果数据时，更新各服务请求的执行状态为轮询结果完成状态。
具体的，本发明实施例的服务器中各模块实现其功能的具体过程可参见上述图3-图9所示实施例中的相关描述，此处不再赘述。
本发明实施例的服务器，根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求，针对目标服务请求，重新向服务提供方发送轮询请求，以请求获取目标服务请求的结果数据，接收并记录服务提供方返回的目标服务请求的结果数据保证了服务提供方中的请求结果数据与服务请求方记录的数据一致，确保用户及时获知准确的请求结果数据，由于过程中无需人力参与，降低了人力成本，提高了处理效率。
实施例六
图12为本发明提供的服务器一个实施例的结构示意图。本发明实施例的服务器对应图7-图9所示实施例中的服务请求方，可执行图7-图9所示任一实施例中的异步服务处理方法。如图12所示，本发明实施例的服务器具体可包括执行模块121和记录模块122，其中：
执行模块121，用于针对服务请求，执行异步服务处理流程。
记录模块122，用于在执行模块执行异步服务处理流程的过程中，记录服务请求的处理详情信息。
进一步的，执行模块121具体可用于：接收服务请求；针对服务请求，向服务提供方发送异步请求；若成功发送异步请求，向服务提供方发送轮询请求，以请求服务请求的结果数据。
进一步的，记录模块122具体可用于执行以下至少一种操作：当接收到服务请求时，记录服务请求的接收时间；当针对服务请求成功向服务提供方发送异步请求时，记录服务请求的执行状态为发送异步请求成功状态；当服务提供方成功返回各服务请求的结果数据时，更新服务请求的执行状态为轮询结果完成状态。
进一步的，执行模块121还可用于：若未成功发送轮询请求，等待设定时长后重新向服务提供方发送轮询请求。
进一步的，执行模块121还可用于：在等待设定时长后重新向服务提供方发送轮询 请求之前，判断是否达到设定的轮询次数阈值；若否，则执行等待设定时长后重新向服务提供方发送轮询请求的步骤。
具体的，本发明实施例的服务器中各模块实现其功能的具体过程可参见上述图7-图9所示实施例中的相关描述，此处不再赘述。
本发明实施例的服务器，通过在针对服务请求执行异步服务处理流程的过程中，记录服务请求的处理详情信息，使得处理过程中不同阶段对应的服务请求的处理详情信息不同，便于在故障恢复后查找未完成轮询操作的服务请求，并自动完成轮询操作，保证了服务提供方中的请求结果数据与服务请求方记录的数据一致，确保用户及时获知准确的请求结果数据，由于过程中无需人力参与，降低了人力成本，提高了处理效率。
本领域普通技术人员可以理解：实现上述各方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成。前述的程序可以存储于一计算机可读取存储介质中。该程序在执行时，执行包括上述各方法实施例的步骤；而前述的存储介质包括：ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是：以上各实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述各实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (26)

  1. 一种异步服务处理方法，其特征在于，包括：
    根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求；
    针对所述目标服务请求，重新向所述服务提供方发送轮询请求，以请求获取所述目标服务请求的结果数据；
    接收并记录所述服务提供方返回的所述目标服务请求的结果数据。
  2. 根据权利要求1所述的方法，其特征在于，所述各服务请求的处理详情信息包括各服务请求的接收时间和执行状态；
    所述根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求，包括：
    根据所述各服务请求的执行状态，获取处于发送异步请求成功状态的服务请求作为候选服务请求；
    计算所述候选服务请求的接收时间与当前时间的差值，获取所述差值大于指定时间的服务请求作为所述目标服务请求。
  3. 根据权利要求2所述的方法，其特征在于，还包括：
    当所述服务提供方成功返回所述目标服务请求的结果数据时，更新所述目标服务请求的执行状态为轮询结果完成状态。
  4. 根据权利要求1所述的方法，其特征在于，还包括：
    若未成功发送所述轮询请求，等待设定时长后重新向所述服务提供方发送所述轮询请求。
  5. 根据权利要求4所述的方法，其特征在于，所述等待设定时长后重新向所述服务提供方发送所述轮询请求之前，还包括：
    判断是否达到设定的轮询次数阈值；
    若否，则执行所述等待所述设定时长后重新向所述服务提供方发送所述轮询请求的步骤。
  6. 根据权利要求1所述的方法，其特征在于，所述根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求，包括：
    当预设扫描周期到达时，根据记录的所述各服务请求的处理详情信息，获取需要重 新向所述服务提供方请求结果数据的服务请求作为所述目标服务请求；或者
    在每次重新启动时，根据记录的所述各服务请求的处理详情信息，获取需要重新向所述服务提供方请求结果数据的服务请求作为所述目标服务请求。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求之前，还包括：
    在针对所述各服务请求执行异步服务处理流程的过程中，记录所述各服务请求的处理详情信息。
  8. 根据权利要求7所述的方法，其特征在于，所述在针对所述各服务请求执行异步服务处理流程的过程中，记录所述各服务请求的处理详情信息，包括以下至少一种操作：
    当接收到所述各服务请求时，记录所述各服务请求的接收时间；
    当针对所述各服务请求成功向所述服务提供方发送所述异步请求时，记录所述各服务请求的执行状态为发送异步请求成功状态；
    当所述服务提供方成功返回所述各服务请求的结果数据时，更新所述各服务请求的执行状态为轮询结果完成状态。
  9. 一种异步服务处理方法，其特征在于，包括：
    针对服务请求，执行异步服务处理流程；
    在执行所述异步服务处理流程的过程中，记录所述服务请求的处理详情信息。
  10. 根据权利要求9所述的方法，其特征在于，所述针对服务请求，执行异步服务处理流程，包括：
    接收所述服务请求；
    针对所述服务请求，向服务提供方发送异步请求；
    若成功发送所述异步请求，向所述服务提供方发送轮询请求，以请求所述服务请求的结果数据。
  11. 根据权利要求10所述的方法，其特征在于，所述在执行所述异步服务处理流程的过程中，记录所述服务请求的处理详情信息，包括以下至少一种操作：
    当接收到所述服务请求时，记录所述服务请求的接收时间；
    当针对所述服务请求成功向所述服务提供方发送所述异步请求时，记录所述服务请求的执行状态为发送异步请求成功状态；
    当所述服务提供方成功返回所述各服务请求的结果数据时，更新所述服务请求的执行状态为轮询结果完成状态。
  12. 根据权利要求10所述的方法，其特征在于，所述针对服务请求，执行异步服务处理流程，还包括：
    若未成功发送所述轮询请求，等待设定时长后重新向所述服务提供方发送所述轮询请求。
  13. 根据权利要求12所述的方法，其特征在于，所述等待设定时长后重新向所述服务提供方发送所述轮询请求之前，还包括：
    判断是否达到设定的轮询次数阈值；
    若否，则执行所述等待设定时长后重新向所述服务提供方发送所述轮询请求的步骤。
  14. 一种服务器，其特征在于，包括：
    获取模块，用于根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求；
    轮询模块，用于针对所述目标服务请求，重新向所述服务提供方发送轮询请求，以请求获取所述目标服务请求的结果数据；
    接收模块，用于接收并记录所述服务提供方返回的所述目标服务请求的结果数据。
  15. 根据权利要求14所述的服务器，其特征在于，所述各服务请求的处理详情信息包括各服务请求的接收时间和执行状态；
    所述获取模块具体用于：
    根据所述各服务请求的执行状态，获取处于发送异步请求成功状态的服务请求作为候选服务请求；
    计算所述候选服务请求的接收时间与当前时间的差值，获取所述差值大于指定时间的服务请求作为所述目标服务请求。
  16. 根据权利要求15所述的服务器，其特征在于，所述接收模块还用于：
    当所述服务提供方成功返回所述目标服务请求的结果数据时，更新所述目标服务请求的执行状态为轮询结果完成状态。
  17. 根据权利要求14所述的服务器，其特征在于，所述轮询模块还用于：
    若未成功发送所述轮询请求，等待设定时长后重新向所述服务提供方发送所述轮询请求。
  18. 根据权利要求17所述的服务器，其特征在于，所述轮询模块还用于：
    在所述等待设定时长后重新向所述服务提供方发送所述轮询请求之前，判断是否达到设定的轮询次数阈值；
    若否，则执行所述等待所述设定时长后重新向所述服务提供方发送所述轮询请求的步骤。
  19. 根据权利要求14所述的服务器，其特征在于，所述获取模块具体用于：
    当预设扫描周期到达时，根据记录的所述各服务请求的处理详情信息，获取需要重新向所述服务提供方请求结果数据的服务请求作为所述目标服务请求；或者
    在每次重新启动时，根据记录的所述各服务请求的处理详情信息，获取需要重新向所述服务提供方请求结果数据的服务请求作为所述目标服务请求。
  20. 根据权利要求14-19任一项所述的服务器，其特征在于，所述获取模块还用于：
    在所述根据记录的各服务请求的处理详情信息，获取需要重新向服务提供方请求结果数据的服务请求作为目标服务请求之前，在针对所述各服务请求执行异步服务处理流程的过程中，记录所述各服务请求的处理详情信息。
  21. 根据权利要求20所述的服务器，其特征在于，所述获取模块具体用于执行以下至少一种操作：
    当接收到所述各服务请求时，记录所述各服务请求的接收时间；
    当针对所述各服务请求成功向所述服务提供方发送所述异步请求时，记录所述各服务请求的执行状态为发送异步请求成功状态；
    当所述服务提供方成功返回所述各服务请求的结果数据时，更新所述各服务请求的执行状态为轮询结果完成状态。
  22. 一种服务器，其特征在于，包括：
    执行模块，用于针对服务请求，执行异步服务处理流程；
    记录模块，用于在所述执行模块执行所述异步服务处理流程的过程中，记录所述服务请求的处理详情信息。
  23. 根据权利要求22所述的服务器，其特征在于，所述执行模块具体用于：
    接收所述服务请求；
    针对所述服务请求，向服务提供方发送异步请求；
    若成功发送所述异步请求，向所述服务提供方发送轮询请求，以请求所述服务请求的结果数据。
  24. 根据权利要求23所述的服务器，其特征在于，所述记录模块具体用于执行以下至少一种操作：
    当接收到所述服务请求时，记录所述服务请求的接收时间；
    当针对所述服务请求成功向所述服务提供方发送所述异步请求时，记录所述服务请求的执行状态为发送异步请求成功状态；
    当所述服务提供方成功返回所述各服务请求的结果数据时，更新所述服务请求的执行状态为轮询结果完成状态。
  25. 根据权利要求23所述的服务器，其特征在于，所述执行模块还用于：
    若未成功发送所述轮询请求，等待设定时长后重新向所述服务提供方发送所述轮询请求。
  26. 根据权利要求25所述的服务器，其特征在于，所述执行模块还用于：
    在所述等待设定时长后重新向所述服务提供方发送所述轮询请求之前，判断是否达到设定的轮询次数阈值；
    若否，则执行所述等待设定时长后重新向所述服务提供方发送所述轮询请求的步骤。
PCT/CN2017/072145 2016-02-04 2017-01-23 异步服务处理方法及服务器 WO2017133531A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610080674.6A CN107040563B (zh) 2016-02-04 2016-02-04 异步服务处理方法及服务器
CN201610080674.6 2016-02-04

Publications (1)

Publication Number Publication Date
WO2017133531A1 true WO2017133531A1 (zh) 2017-08-10

Family

ID=59500983

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/072145 WO2017133531A1 (zh) 2016-02-04 2017-01-23 异步服务处理方法及服务器

Country Status (3)

Country Link
CN (1) CN107040563B (zh)
TW (1) TWI753876B (zh)
WO (1) WO2017133531A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109711741A (zh) * 2018-12-29 2019-05-03 上海二三四五金融科技有限公司 一种获取设备风控数据的控制方法及控制装置

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107729165A (zh) * 2017-10-12 2018-02-23 郑州云海信息技术有限公司 一种信息获取方法、装置及系统
CN110827108B (zh) * 2018-08-13 2023-05-26 阿里巴巴集团控股有限公司 信息搜索方法、搜索请求控制方法及系统
CN109889593B (zh) * 2019-02-27 2021-11-12 中国人民解放军海军工程大学 一种移动机动保障方舱的分布式主从机通讯方法及装置
CN111711826B (zh) * 2019-03-18 2023-11-03 北京奇虎科技有限公司 视频直播服务系统及方法
CN112085490A (zh) * 2019-06-13 2020-12-15 百度在线网络技术（北京）有限公司 异步计费方法、装置、设备及计算机可读存储介质
CN110543381B (zh) * 2019-08-21 2022-02-22 语联网（武汉）信息技术有限公司 机器翻译引擎服务恢复方法及装置
CN113065054B (zh) * 2021-03-31 2024-03-01 北京达佳互联信息技术有限公司 请求处理方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100223620A1 (en) * 2009-02-27 2010-09-02 Yahoo! Inc. Smart recovery of asynchronous processing
CN102710665A (zh) * 2012-06-27 2012-10-03 深圳中兴网信科技有限公司 移动终端、服务器和移动终端的数据同步方法
CN103885988A (zh) * 2012-12-21 2014-06-25 中国移动通信集团公司 输出内容的方法及装置、内容输出系统
CN104753966A (zh) * 2013-12-25 2015-07-01 明博教育科技有限公司 一种基于服务器和客户端缓存的资源文件查询方法及系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1912885B (zh) * 1995-02-13 2010-12-22 英特特拉斯特技术公司 用于安全交易管理和电子权利保护的系统和方法
US7987491B2 (en) * 2002-05-10 2011-07-26 Richard Reisman Method and apparatus for browsing using alternative linkbases
CN103220206B (zh) * 2012-01-19 2017-04-19 阿里巴巴集团控股有限公司 一种消息发送方法、装置和一种消息接收方法、装置
CN104852991A (zh) * 2015-06-01 2015-08-19 上海雷腾软件股份有限公司 分布式推送服务器系统及应用该系统的数据推送方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100223620A1 (en) * 2009-02-27 2010-09-02 Yahoo! Inc. Smart recovery of asynchronous processing
CN102710665A (zh) * 2012-06-27 2012-10-03 深圳中兴网信科技有限公司 移动终端、服务器和移动终端的数据同步方法
CN103885988A (zh) * 2012-12-21 2014-06-25 中国移动通信集团公司 输出内容的方法及装置、内容输出系统
CN104753966A (zh) * 2013-12-25 2015-07-01 明博教育科技有限公司 一种基于服务器和客户端缓存的资源文件查询方法及系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109711741A (zh) * 2018-12-29 2019-05-03 上海二三四五金融科技有限公司 一种获取设备风控数据的控制方法及控制装置

Also Published As

Publication number Publication date
CN107040563B (zh) 2021-01-19
TW201732654A (zh) 2017-09-16
TWI753876B (zh) 2022-02-01
CN107040563A (zh) 2017-08-11

Similar Documents

Publication Publication Date Title
WO2017133531A1 (zh) 异步服务处理方法及服务器
US11277464B2 (en) Data restoration for datacenter failover
US20170302502A1 (en) Arbitration processing method after cluster brain split, quorum storage apparatus, and system
US9477738B2 (en) Initialization protocol for a peer-to-peer replication environment
US8379645B2 (en) Link data transmission method, node and system
US11741075B2 (en) Methods and system of tracking transactions for distributed ledger
US9722890B2 (en) Integrated incident management for hybrid landscapes
WO2013078689A1 (zh) 一种云消息服务中实现消息传递的方法和装置
US10187181B2 (en) Method and device for handling exception event in telecommunication cloud
WO2016127884A1 (zh) 消息推送方法及装置
US20220317897A1 (en) Performing various operations at the granularity of a consistency group within a cross-site storage solution
US11537314B1 (en) Resynchronization of individual volumes of a consistency group (CG) within a cross-site storage solution while maintaining synchronization of other volumes of the CG
JP6700308B2 (ja) データ・コピー方法及びデバイス
JP2019502186A (ja) グローバル情報を取得、処理および更新するためのシステムおよび方法
WO2017071384A1 (zh) 报文处理的方法及装置
US11070635B2 (en) Device management server and method
JP6434021B2 (ja) データフィードの管理
KR20170068533A (ko) 가상 카드 처리 방법 및 장치
CN109189854B (zh) 提供持续业务的方法及节点设备
CN106557522B (zh) 一种用于提供定时功能的方法与设备
WO2016095699A1 (zh) 一种标签交换路径状态的获取方法及装置
EP3602974A1 (en) Apparatus and method for maintaining message databases in eventual consistency distributed database systems
US20090106781A1 (en) Remote call handling methods and systems
CN114090342A (zh) 存储容灾的链路管理方法及消息执行节点、存储控制集群
JP4862346B2 (ja) ダウンロードシステム及びプログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17746851

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17746851

Country of ref document: EP

Kind code of ref document: A1