System and associated method for ensuring data privacy
US-2020287874-A1 · Sep 10, 2020 · US
US11625329B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11625329-B2 |
| Application number | US-202016743729-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 15, 2020 |
| Priority date | Jan 15, 2020 |
| Publication date | Apr 11, 2023 |
| Grant date | Apr 11, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method is used in host-based caching. A host receives a request for data, and identifies a host in a plurality of hosts that owns the data.
Opening claim text (preview).
What is claimed is: 1. A method for host-based caching, the method comprising: receiving, by a host, a request for data; if the host determines the data is not in a first cache determining, by the host, a hash value corresponding to the data by searching a second cache associated with the host using an address associated with the data for the hash value, wherein the hash value corresponds to one of a plurality of hosts on which the data is stored, wherein the first cache comprises addresses and associated data and the second cache comprises addresses and hash values; applying, by the host, a mask to the hash value; and matching, by the host, the masked hash value with a bit pattern associated with a host of the plurality of hosts to identify a host that owns a dataspace portion that includes the data so as to store the data in its cache for sharing with other hosts in the plurality of hosts. 2. The method of claim 1 , wherein each host in the plurality of hosts own a unique portion of the dataspace so as to store data associated with its unique portion in its cache for sharing with other hosts. 3. The method of claim 1 , wherein matching the masked hash value with the bit pattern associated with the host comprises: determining that the host that received the request for the data owns the dataspace portion that includes the data. 4. The method of claim 3 , further comprising: retrieving, by the host, the data from it own the first cache. 5. The method of claim 1 , further comprising: requesting, by the host, the data from the host that owns the dataspace portion that includes the data. 6. The method of claim 1 wherein matching the masked hash value with the bit pattern associated with the host comprises: searching a translation table for a subset of bits from the hash value; and identifying a host associated with the subset of bits. 7. The method of claim 1 , further comprising: requesting, by the host, the data from the host that owns the dataspace portion that includes the data. 8. The method of claim 7 , wherein requesting the data from the host that owns the dataspace portion that includes the data comprises: sending, by the host, the hash value to the host that owns the dataspace portion that includes the data. 9. The method of claim 1 , further comprising: receiving, by the host, data from the dataspace portion owned by the host from another host in the plurality of the hosts; and storing, by the host, the data in a cache designated for sharing with other hosts in the plurality of hosts. 10. A system for use in host-based caching, the system comprising a processor configured to: receive a request for data; if the host determines the data is not in a first cache determine, by the host, a hash value corresponding to the data by searching a second cache associated with the host using an address associated with the data for the hash value, wherein the hash value corresponds to one of a plurality of hosts on which the data is stored, wherein the first cache comprises addresses and associated data and the second cache comprises addresses and hash values; apply, by the host, a mask to the hash value; and match the masked hash value with a bit pattern associated with a host in a plurality of hosts to identify a host that owns a dataspace portion that includes the data so as to store the data in its cache for sharing with other hosts in the plurality of hosts. 11. The system of claim 10 , wherein each host in the plurality of hosts own a unique portion of the dataspace so as to store data associated with its unique portion in its cache for sharing with other hosts. 12. The system of claim 10 , wherein the processor is further configured to: determine that the host that received the request for data owns the portion of the dataspace that includes the data. 13. The system of claim 12 , wherein the processor is further configured to: retrieve the data from the first cache. 14. The system of claim 10 , wherein the processor is further configured to: request the data from the host that owns the dataspace portion that includes the data. 15. The system of claim 10 , wherein the processor is further configured to: search a translation table for a subset of bits from the hash value; and identify a host associated with the subset of bits. 16. The system of claim 10 , wherein the processor is further configured to: request the data from the host that owns the dataspace portion that includes the data. 17. The system of claim 16 , wherein the processor is further configured to: send the hash value to the host that owns the dataspace portion that includes the data. 18. The system of claim 10 , wherein the plurality of hosts collectively own an entirety of the dataspace. 19. The system of claim 10 , wherein portions of the dataspace owned by each host are equal in size. 20. The system of claim 10 , wherein portions of the dataspace owned by each host vary in size.
Data transfer between cache memory and other subsystems, e.g. storage devices or host systems · CPC title
using tables or multilevel address translation means (G06F12/023 takes precedence; address translation in virtual memory systems G06F12/10) · CPC title
using pseudo-associative means, e.g. set-associative or hashing · CPC title
Allocation or management of cache space · CPC title
with main memory updating (G06F12/0806 takes precedence) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.