Precomputing processes associated with requests

• US 9,240,023 B1
• Filed: 01/30/2013
• Issued: 01/19/2016
• Est. Priority Date: 01/30/2013
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Varangaonkar, Ajit Ashok
• Primary Examiner(s): Rosen, Nicholas D
• Application Number:
  US13/754,785
• Time in Patent Office: 1,084 Days
• Field of Search: 705/26.1, 705/26.8, 705/26.81, 705/26.82, 705/27.1, 715/205
• US Class Current: 1/1
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 9/4881 Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06F 9/543 User-generated data transfer, e.g. clipboards, dynamic data exchange [DDE], object linking and embedding [OLE]
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 30/0633 Lists, e.g. purchase orders, compilation or processing
• CPC Class Codes: G06Q 30/0635 Processing of requisition or of purchase orders
• CPC Class Codes: G06Q 30/0637 Approvals

Abstract

Processes from a set of processes for use at a second triggering event may be processed by performing a subset of the set of processes in response to a first triggering event to obtain a first result. A remainder of the set of processes may be processed in response to the second triggering event occurring after the first triggering event, and using the first result, to obtain a second result.

Claims

1. A method for completing a purchase using a set of processes, comprising:

receiving a request for a network page including an item for purchase from a client device;

sending the network page to the client device;

performing a subset of the set of processes in response to the request for the network page using a processor, where remainder processes outside of the subset are unperformed;

saving a state of the subset of the set of processes; and

performing the remainder processes using the processor, based on the state of the subset of the set of processes, when a purchase page is requested for the item.

2. The method of claim 1, wherein saving a state of the subset of the set of processes further comprises saving a state multiple times while performing the subset of the set of processes, the method further saving a state while performing the remainder processes.

3. The method of claim 1, further comprising tracking user interaction with the network page and initiating performance of the remainder processes when the user interaction indicates a likelihood that the purchase page will be requested.

4. The method of claim 1, wherein the set of processes includes a loading data process, a setting data process, an deriving data process, a validating data process and a finalizing data process.

5. The method of claim 4, wherein the subset of the set of processes includes the loading data process and the setting data process.

6. The method of claim 1, further comprising:

prefetching some of the remainder processes when tracked user interaction indicates a likelihood that the purchase page will be requested; and

finishing performing the remainder processes after the purchase page has been requested.

7. A system for precomputing processes associated with requests, comprising:

a processor to process a subset of purchase processes in response to a page request;

a state module to store a state of the subset of processes when the subset of processes have been processed by the processor; and

a remainder module to perform a remainder of purchase processes, based on the state of the subset of purchase processes, when a purchase page is requested for an item for purchase.

8. The system of claim 7, further comprising a prefetch module configured to perform intermediary purchase processes in response to a likelihood greater than a predetermined threshold, based on user interaction with the page, that the purchase request will be received.

9. The system of claim 7, further comprising a history module for accessing a history of the subset of purchase processes as a basis for performing a current instance of the subset of purchase processes.

10. The system of claim 7, further comprising a shipping module to identify a shipping history of a user, the subset of purchase processes including processes for:

identifying a shipping address;

selecting a shipping method; and

calculating a shipping cost.

11. The system of claim 7, further comprising a user data module to identify user data including a purchase payment method, the subset of purchase processes including processes for calculating a purchase sub-total, calculating a purchase tax, calculating a purchase total based on the sub-total and tax, and populating the purchase payment method based on the user data.

12. The system of claim 7, further comprising an expiration module to expire the state after a predetermined period of time.

13. The system of claim 12, further comprising a recalculation module to recalculate the state after the state has been expired.

14. The system of claim 7, further comprising a tracking module to track user interaction with the page.

15. The system of claim 14, further comprising an inventory management module to identify available inventory and reserve inventory for the purchase request in advance of the purchase request when the user interaction with the page indicates a likelihood greater than a predetermined threshold that the purchase request will be received.

16. A non-transitory computer readable medium having instructions embodied thereon, which, when executed by a processor, are operable to:

load user data in response to a first request from a client device;

set order data for purchase of an item based on the user data in response to the first request;

derive item data to determine availability of the item for purchase in response to an indication that a second request will be received;

validate the order data, including the item data, in response to the indication that the second request will be received; and

finalize the order data to complete the purchase of the item in response to the second request.