Service associated with persistent storage

• US 9,898,401 B2
• Filed: 06/05/2017
• Issued: 02/20/2018
• Est. Priority Date: 04/12/2011
• Status: Expired due to Fees

• Current Assignee: Empire Technology Development LLC (Allied Inventors Management, LLC)
• Original Assignee: Empire Technology Development LLC (Allied Inventors Management, LLC)
• Inventors: Cilibrasi, Rudi
• Primary Examiner(s): PEUGH, BRIAN R
• Application Number:
  US15/613,349
• Publication Number:
  US 20170270039A1
• Time in Patent Office: 260 Days
• Field of Search: None
• CPC Class Codes: G06F 12/023 Free address space management
• CPC Class Codes: G06F 12/0292 using tables or multilevel address translation means G06F12/023 takes precedence; address translation in virtual memory systems G06F12/10
• CPC Class Codes: G06F 3/0614 Improving the reliability of storage systems
• CPC Class Codes: G06F 3/064 Management of blocks
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 3/0679 Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]

Abstract

Examples are disclosed for allocating a block of persistent storage or accessing a block of persistent storage based on a storage service string that includes a universally unique identifier and associated metadata.

Claims

1. A method to allocate a block of persistent storage, the method comprising:

forming a storage service string associated with the block of persistent storage; and

creating an entry in a sparse non-deterministic block index to store information associated with the storage service string, wherein the information includes a universally unique identifier and metadata that indicates one or more characteristics for a storage service associated with the block of persistent storage.

2. The method according to claim 1, wherein the forming the storage service string comprises encoding the universally unique identifier and the metadata to form a uniform resource identifier (URI).

3. The method according to claim 1, wherein the sparse non-deterministic block index is available to one or more applications and/or file systems interconnected via one or more network communication links.

4. The method according to claim 1, wherein the universally unique identifier comprises a 32-byte number that was randomly generated by a file system or an application that forwarded the storage service string.

5. The method according to claim 1, further comprising:

generating the universally unique identifier for the block of persistent storage; and

forwarding the storage service string to a storage device driver.

6. The method according to claim 5, wherein the storage service string is used to allocate the block of persistent storage from persistent storage that is accessible to the storage device driver.

7. The method according to claim 1, further comprising:

forwarding the storage service string to a storage device driver to submit an allocation request for the block of persistent storage.

8. The method according to claim 1, wherein the one or more characteristics for the storage service comprises one or more of:

a size for the block of persistent storage,

an expiration time period for the block of persistent storage,

a number of allowed reads per given time period for the block of persistent storage, or

a number of allowed writes per given time period for the block of persistent storage.

9. The method according to claim 8, wherein the expiration time period comprises an indication of a number of seconds since an epoch from which the block of persistent storage is set to expire.

10. A method to access a block of persistent storage, the method comprising:

accessing an entry in a sparse non-deterministic block index to obtain a storage service string, wherein the entry includes a universally unique identifier and metadata associated with the block of persistent storage;

obtaining at least a portion of the storage service string from the sparse non-deterministic block index; and

forwarding the at least the portion of the storage service string to a storage device driver to submit a read request for a storage service associated with the block of persistent storage.

11. The method according to claim 10, wherein the storage service string comprises a uniform resource identifier (URI) that encodes the universally unique identifier and the metadata associated with the block of persistent storage in accordance with representational state transfer (REST) architectural style, and wherein the URI includes an indication of a host associated with a location for persistent storage accessible by the storage device driver.

12. The method according to claim 10, wherein the universally unique identifier comprises a 32-byte number that was randomly generated by a file system or application that forwarded the storage service string.

13. A system to allocate a block of persistent storage, the system comprising:

a persistent storage device;

an application that includes an index logic, wherein the index logic is configured to;

form a storage service string associated with the block of persistent storage;

create an entry in a sparse non-deterministic block index to store information associated with the storage service string, wherein the information includes universally unique identifier and metadata; and

forward the storage service string to submit an allocation request for the block of persistent storage; and

a storage device driver that includes a service logic, wherein the service logic is configured to;

receive the storage service string that is forwarded by the application; and

allocate the block of persistent storage to fulfill the allocation request, based at least, in part, on the storage service string.

14. The system according to claim 13, wherein the service logic is further configured to write data to the allocated block of persistent storage, and wherein to write the data to the allocated block of persistent storage, the service logic is configured to use a cryptographic protocol to sign at least a portion of the data to be written to the allocated block of persistent storage.

15. The system according to claim 13, wherein the metadata indicates one or more characteristics for a storage service associated with the block of persistent storage, and wherein the one or more characteristics comprises one or more of:

a size for the block of persistent storage,

an expiration time period for the block of persistent storage,

a number of allowed reads per given time period for the block of persistent storage, or

a number of allowed writes per given time period for the block of persistent storage.

16. The system according to claim 13, wherein the index logic is configured to forward the storage service string by use of hypertext transfer protocol (HTTP).

17. The system according to claim 13, wherein based at least, in part, on the storage service string, the service logic is configured to allocate the block of persistent storage from persistent storage accessible to the storage device driver.

18. The system according to claim 17, wherein the index logic is configured to forward the storage service string to the storage device driver via a first network communication link, and wherein the persistent storage is accessible to the storage device driver via a second network communication link.

19. The system according to claim 13, wherein the storage service string comprises a uniform resource identifier (URI) that encodes the universally unique identifier and the metadata in accordance with representational state transfer (REST) architectural style.

20. The system according to claim 13, wherein the sparse non-deterministic block index is available to the application via a local communication link or a network communication link.