Subscription management service

• US 10,074,115 B1
• Filed: 08/14/2013
• Issued: 09/11/2018
• Est. Priority Date: 08/14/2013
• Status: Expired due to Fees

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Hynoski, Jeremy Stephen, Chang, Eugene, Halim, Andygibb, Cura, Hector
• Primary Examiner(s): Danneman, Paul
• Application Number:
  US13/966,550
• Time in Patent Office: 1,854 Days
• Field of Search: None
• CPC Class Codes: G06Q 30/04 Billing or invoicing

Abstract

A subscription management service utilizes a timer service to maintain timers corresponding to subscription events. The subscription management service exposes an interface through which clients can define new subscriptions that are then created and managed by the subscription management service. The subscription management service can charge subscribers on an appropriate billing period, and cancel or automatically renew subscriptions at the end of a contract period. The subscription management service can also provide notifications to clients, to subscribers, and/or to other components. The subscription management service might also perform other types of actions with regard to the subscriptions on behalf of the clients. The timer service receives payloads from clients, such as the subscription management service, and provides the payloads back to the clients at a specified time. The timer service might also utilize a jitter threshold to compute the time at which payloads should be provided to clients.

Claims

1. A computer-implemented method for successively firing timers for clients of a timer service, the computer-implemented method comprising executing instructions in a computer system to perform the operations of:

exposing a Web services application programming interface (API) to the clients of the timer service, wherein the API exposes functionality for creating a timer for individual clients and the timer service is associated with a subscription service;

storing client configuration records for the clients, individual client configuration records specifying a payload destination and a jitter threshold for a respective client;

receiving, via one or more computers of the subscription service, a request from individual clients to create a timer via the Web services API, the request comprising a payload and specifying a time at which the payload is to be provided to the payload destination, the jitter threshold specifying a maximum amount of time after the time specified in the request that the payload can be provided to the payload destination;

modifying, via one or more computers of the timer service, the time specified in individual timer creation requests by selecting a random amount of time less than the jitter threshold and by adding the random amount of time to the time specified in the timer creation request for the respective client;

creating, via the one or more computers of the timer service, the timer for individual clients using the respective modified time and the payload; and

providing, via the one or more computers of the timer service, individual payloads to the payload destination at approximately the respective modified time.

2. The computer-implemented method of claim 1, wherein creating the timer using the modified time and the payload comprises storing a timer record comprising the modified time and the payload in at least two nodes of a database cluster associated with the timer service.

3. The computer-implemented method of claim 2, wherein the payload destination comprises a distributed queue.

4. The computer-implemented method of claim 3, wherein the client configuration record and the timer record further comprise a client identifier that uniquely identifies the client.

5. The computer-implemented method of claim 2, wherein providing each payload to the payload destination comprises sweeping timer data stores within the at least two nodes of the database cluster to identify timer records about to expire.

6. A computer-readable storage medium having computer-executable instructions stored thereupon which, when executed by the computer, cause the computer to:

expose an interface for receiving requests to create new timers, wherein the interface is an application programming interface (API) that exposes functionality for creating the new timers and wherein the interface is utilized by subscription service clients to communicate with a subscription service that is associated with a timer service;

receive, by way of the interface, requests from clients to create new timers, individual requests comprising a payload and data identifying a time at which the payload is to be delivered to a destination;

modify, by one or more computers of the timer service, the time for the individual requests using a jitter threshold associated with the client, the jitter threshold specifying a maximum amount of time after the time that the payload can be provided to the destination, comprising;

select a random amount of time less than the jitter threshold; and

add the random amount of time to the time at which the payload is to be delivered to the destination;

cause, by the one or more computers of the timer service, a new timer to be created by the timer service at the modified time for the individual clients; and

deliver, by the one or more computers of the timer service, the payload for the individual clients to the destination at approximately the modified time.

7. The computer-readable storage medium of claim 6, wherein the API comprises a Web services application programming interface.

8. The computer-readable storage medium of claim 6, having further computer-executable instructions stored thereupon which, when executed by the computer, cause the computer to store a client configuration record for the client, the client configuration record comprising data identifying the destination and the jitter threshold.

9. The computer-readable storage medium of claim 8, wherein the client configuration record further specifies a type for the payload destination.

10. The computer-readable storage medium of claim 8, wherein the client configuration record further specifies a maximum period of time in the future that a timer can be created for the client.

11. The computer-readable storage medium of claim 8, wherein the client configuration record further specifies a unique client identifier for the client.

12. The computer-readable storage medium of claim 6, having further computer-executable instructions stored thereupon which, when executed by the computer, cause the apparatus to create a timer record on at least two nodes of a database cluster, the timer record comprising the modified time and the payload.

13. An apparatus configured to successively fire timers for clients of a timer service, the apparatus comprising:

at least one processor; and

a computer-readable storage medium having computer-executable instructions stored thereon which, when executed on the at least one processor, cause the apparatus to

receive requests, via an interface exposed by the timer service, to create timers, individual requests identifying a payload and a time at which the payload is to be delivered to a destination, wherein the interface is an application programming interface (API) that exposes functionality for creating the timers and wherein the interface is utilized by subscription service clients to communicate with a subscription service associated with the timer service;

in response to receiving the individual requests, modify, by one or more computers of the timer service, the time using a jitter threshold, the jitter threshold specifying a maximum period after the time that the payload can be provided to the destination, wherein the modification comprises;

select a random amount of time less than the jitter threshold, and

add the random amount of time to the time at which the payload is to be delivered to the destination,

cause, by the one or more computers of the timer service, a timer that expires at the modified time to be created by the timer service for the individual requests, and

deliver, by the one or more computers of the timer service, the payload for the individual requests to the destination at approximately the respective modified time.

14. The apparatus of claim 13, wherein the computer-readable storage medium has further computer-executable instructions stored thereon which, when executed on the at least one processor, cause the apparatus to create a timer record on at least two nodes of a database cluster, the timer record comprising the modified time and the payload.

15. The computer-implemented method of claim 14, wherein deliver the payload for each request to the destination comprises sweeping timer data stores within the at least two nodes of the database cluster to identify timer records about to expire.

16. The apparatus of claim 13, wherein the destination comprises a queue.

17. The apparatus of claim 13, wherein the payload comprises data relating to a subscription event.

18. The apparatus of claim 13, wherein the apparatus is further configured to maintain a client configuration record for a client submitting the request, the client configuration record comprising data identifying the destination and the jitter threshold.

19. The apparatus of claim 18, wherein the client configuration record further specifies a destination type for the destination.

20. The apparatus of claim 19, wherein the client configuration record further specifies a maximum period of time in the future that a timer can be created for the client.