Systems, methods, and computer program products for service processing

• US 9,794,353 B2
• Filed: 12/15/2014
• Issued: 10/17/2017
• Est. Priority Date: 12/19/2013
• Status: Expired due to Fees

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: LaPlante, Lance C.
• Primary Examiner(s): Chacko, Joe
• Application Number:
  US14/570,371
• Publication Number:
  US 20150180702A1
• Time in Patent Office: 1,037 Days
• CPC Class Codes: H04L 41/5012 determining service availability, e.g. which services are available at a certain point in time
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 43/0805 by checking availability
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

A system for managing process requests includes at least one memory operable to store request and response queues and a processor coupled to the memory. A request to execute a process is received and stored in a request queue among a set of request queues, the request queue corresponding to the process. It is determined if one or more nodes on a network are available to perform the process. An expiration value for the request is set based on a type of the process. The request is dispatched to the one or more nodes on the network to perform the process at a predetermined timing. A response is received from the one or more nodes. The response is stored in a response queue among a set of response queues, the response queue corresponding to the process. The response is dispatched from the response queue.

Claims

1. A system to manage requests for network nodes that are not available to perform a type of process, comprising:

at least one memory operable to store request and response queues; and

a processor coupled to the memory, the processor being operable to;

receive a request to execute a process;

store the request in a request queue among a set of request queues, wherein the request queue corresponds to a type of process corresponding to the request;

determine that one or more nodes on a network are not available to perform the process;

set an expiration value for the request based on the type of the process in response to determining that the one or more nodes on the network are not available to perform the process, wherein the expiration value indicates how long requests of the type of the process are to be queued following the determination that the one or more nodes operable to perform the type of the process are not available;

dispatch the request from the request queue to the one or more nodes on the network to perform the process at a predetermined timing earlier than a time associated with the expiration value, if the one or more nodes on the network become available to perform the process before the time associated with the expiration value; and

dispatch the request from the request queue to a request expire queue if the one or more nodes on the network continue to remain not available to perform the process at or after the time associated with the expiration value.

2. The system according to claim 1, wherein the processor is operable to limit the number of requests dispatched from the request queue.

3. The system according to claim 2, wherein the number of requests dispatched from the request queue is limited in accordance with a number of previous requests dispatched from the request queue within a predetermined amount of time.

4. The system according to claim 1, further comprising an interface operable to receive the expiration value from a mobile device.

5. The system according to claim 1, wherein respective expiration values are associated with mobile devices.

6. The system according to claim 1, wherein the determination of whether one or more nodes on a network are available to perform the process is performed by communicating with a service availability service.

7. A method to manage process requests, comprising:

storing, by one or more computing devices, request and response queues;

receiving, by one or more computing devices, a request to execute a process;

storing, by one or more computing devices, the request in a request queue among a set of request queues, wherein the request queue corresponds to the process;

determining, by one or more computing devices, that one or more nodes on a network are not available to perform the process;

setting, by one or more computing devices, an expiration value for the request based on a type of the process in response to determining that the one or more nodes on the network are not available to perform the process, wherein the expiration value indicates how long requests of the type of the process are to be queued following the determination that the one or more nodes operable to perform the type of the process is not available;

dispatching, by one or more computing devices, the request from the request queue to the one or more nodes on the network to perform the process at a predetermined timing earlier than a time associated with the expiration value, if the one or more nodes on the network becomes available to perform the process before the time associated with the expiration value; and

dispatching, by one or more computing devices, the request queue to a request expire queue if the one or more nodes on the network continue to remain not available to perform the process at or after the time associated with the expiration value.

8. The method according to claim 7, further comprising limiting, by the one or more computing devices, the number of requests dispatched from the request queue.

9. The method according to claim 8, wherein the number of requests dispatched from the request queue is limited in accordance with a number of previous requests dispatched from the request queue within a predetermined amount of time.

10. The method according to claim 7, further comprising receiving, by the one or more computing devices, the expiration value from a mobile device.

11. The method according to claim 7, wherein respective expiration values are associated with mobile devices.

12. The method according to claim 7, wherein the determination of whether one or more nodes on a network are available to perform the process is performed by communicating with a service availability service.

13. A non-transitory computer readable storage medium having stored thereon instructions that, when executed by a system including at least one processor and at least one memory, cause the system to:

store request and response queues;

receive a request to execute a process;

store the request in a request queue among a set of request queues, wherein the request queue corresponds to the process;

determine that one or more nodes on a network are not available to perform the process;

set an expiration value for the request based on a type of the process in response to determining that the one or more nodes on the network are not available to perform the process, wherein the expiration value indicates how long requests of the type of the process are to be queued following the determination that the one or more nodes operable to perform the type of the process is not available;

dispatch the request from the request queue to the one or more nodes on the network to perform the process at a predetermined timing earlier than a time associated with the expiration value, in a case that the one or more nodes on the network become available to perform the process before the time associated with the expiration value; and

dispatch the response from the request queue to a request expire queue if the one or more nodes on the network continue to remain unavailable to perform the process at or after the time associated with the expiration value.

14. The storage medium according to claim 13, wherein the instructions further cause the system to limit the number of requests dispatched from the request queue.

15. The storage medium according to claim 14, wherein the number of requests dispatched from the request queue is limited in accordance with a number of previous requests dispatched from the request queue within a predetermined amount of time.

16. The storage medium according to claim 13, wherein the instructions further cause the system to receive the expiration value from a mobile device.

17. The storage medium according to claim 13, wherein respective expiration values are associated with mobile devices.