Data layer service availability

US9600508B1 · US · B1

Patent metadata
FieldValue
Publication numberUS-9600508-B1
Application numberUS-201514814824-A
CountryUS
Kind codeB1
Filing dateJul 31, 2015
Priority dateMay 30, 2013
Publication dateMar 21, 2017
Grant dateMar 21, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Disclosed are various embodiments for a token management application. A data block tokenization call to a data layer service fails when a data store is unavailable. The token management application issues a temporary data token to the service calling the data layer service. The token management application completes the data block tokenization call on behalf of the service to obtain a valid data token. The valid data token is then communicated to services having the temporary data token.

First claim

Opening claim text (preview).

Therefore, the following is claimed: 1. A non-transitory computer-readable medium embodying a program executable in at least one computing device, the program, when executed, causing the at least one computing device to at least: generate a temporary token responsive to at least one data store being unavailable to complete a data block tokenization call from one of a plurality of services to a data layer service facilitating access to the at least one data store; and communicate the temporary token to the one of the plurality of services, wherein the temporary token is capable of being passed to other ones of the plurality of services. 2. The non-transitory computer-readable medium of claim 1 , wherein the program further causes the at least one computing device to at least: communicate a valid token to a respective one of the plurality of services having the temporary token after the at least one data store becomes available; and wherein the valid token facilitates access to a data block corresponding to the valid token stored in the at least one data store. 3. The non-transitory computer-readable medium of claim 2 , wherein the program further causes the at least one computing device to at least repeatedly query the data layer service with the data block tokenization call until obtaining the valid token from the data layer service in response to the data block tokenization call. 4. A system, comprising: at least one data store; at least one computing device comprising at least one processor and memory storing instructions that, when executed by the at least one processor, cause the at least one computing device to at least: generate a temporary token responsive to the at least one data store being unavailable to complete a data block tokenization call from one of a plurality of services to a data layer service facilitating access to the at least one data store; and communicate the temporary token to the one of the plurality of services, wherein the temporary token is capable of being passed to other ones of the plurality of services. 5. The system of claim 4 , wherein the instructions further cause the at least one computing device to at least: communicate a valid token to a respective one of the plurality of services having the temporary token after the at least one data store becomes available; and wherein the valid token facilitates access to a data block corresponding to the valid token stored in the at least one data store. 6. The system of claim 5 , wherein the instructions further cause the at least one computing device to at least: receive a request comprising the temporary token from the respective one of the plurality of services having the temporary token; and wherein communicating the valid token to the respective one of the plurality of services is performed in response to the request. 7. The system of claim 6 , wherein the request comprises an application program interface call from the respective one of the plurality of services having the temporary token. 8. The system of claim 5 , wherein the instructions further cause the at least one computing device to at least repeatedly query the data layer service with the data block tokenization call until obtaining the valid token from the data layer service in response to the data block tokenization call. 9. The system of claim 8 , wherein the data layer service is repeatedly queried at an interval of an increasing duration. 10. The system of claim 4 , wherein the temporary token comprises an identifier prohibiting access to a data block corresponding to the data block tokenization call. 11. The system of claim 4 , wherein the instructions further cause the at least one computing device to at least: communicate to at least a subset of the plurality of services a notification that a valid token is available; and wherein the valid token facilitates access to a data block corresponding to the valid token stored in the at least one data store. 12. The system of claim 11 , wherein the instructions further cause the at least one computing device to at least communicate the notification by publishing the notification to a subscription notification service to which the at least a subset of the plurality of services is subscribed. 13. The system of claim 12 , wherein the notification comprises the valid token. 14. A method, comprising: generate, by at least one computing device, a temporary token responsive to at least one data store being unavailable to complete a data block tokenization call from one of a plurality of services to a data layer service facilitating access to the at least one data store; and communicate, by the at least one computing device, the temporary token to the one of the plurality of services, wherein the temporary token is capable of being passed to other ones of the plurality of services. 15. The method of claim 14 , further comprising: communicating, by the at least one computing device, a valid token to a respective one of the plurality of services having the temporary token after the at least one data store becomes available; and wherein the valid token facilitates access to a data block corresponding to the valid token stored in the at least one data store. 16. The method of claim 15 , further comprising: receive an application program interface call from the respective one of the plurality of services having the temporary token; and wherein communicating the valid token to the respective one of the plurality of services is performed in response to the application program interface call. 17. The method of claim 16 , wherein the application program interface call comprises the temporary token. 18. The method of claim 16 , wherein the application program interface call comprises a callback application program interface call. 19. The method of claim 14 , wherein the temporary token comprises an identifier prohibiting access to a data block corresponding to the data block tokenization call. 20. The method of claim 15 , further comprising repeatedly querying, by the at least one computing device, the data layer service with the data block tokenization call until obtaining the valid token from the data layer service in response to the data block tokenization call.

Assignees

Inventors

Classifications

  • Indexing structures · CPC title

  • Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units (interface circuits for specific input/output devices G06F3/00 {; multiprogram control therefor  G06F9/46}; multiprocessor systems  G06F15/16 ) · CPC title

  • Synchronisation and timing concerns (synchronisation on a memory bus G06F13/4234) · CPC title

  • using a common memory, e.g. mailbox · CPC title

  • Bus transfer protocol, e.g. handshake; Synchronisation · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9600508B1 cover?
Disclosed are various embodiments for a token management application. A data block tokenization call to a data layer service fails when a data store is unavailable. The token management application issues a temporary data token to the service calling the data layer service. The token management application completes the data block tokenization call on behalf of the service to obtain a valid dat…
Who is the assignee on this patent?
Amazon Tech Inc
What technology area does this patent fall under?
Primary CPC classification G06F16/2228. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Mar 21 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).