# US 2019/0377682 A1 · Method for controlling near caches in distributed cache environment, and distributed cache server using the same

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0377682 A1
- Document ID: US20190377682A1
- Status: Published application
- Kind: A1
- Application number: 16/011,976
- Filed: 2018-06-19
- Published: 2019-12-12
- Earliest claimed: 2018-06-07
- Assignees: Tmaxsoft Co., Ltd.
- Applicants: Tmaxsoft. Co., Ltd.
- Inventors: Cliff Roh
- Web page: https://patentgrep.com/patent/US20190377682A1

## CPC

- G06F 12/0811: with multilevel cache hierarchies
- G06F 12/0873: Mapping of cache memory to specific storage devices or parts thereof
- G06F 12/0815: Cache consistency protocols
- G06F 12/0871: Allocation or management of cache space
- G06F 12/0893: Caches characterised by their organisation or structure
- G06F 16/24552: {Database cache management}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 12/0891: using clearing, invalidating or resetting means
- G06F 2212/1016: Performance improvement
- G06F 2212/154: Networked environment
- G06F 2212/163: Server or database system
- G06F 2212/284: being distributed
- G06F 2212/285: Redundant cache memory
- G06F 2212/314: In storage network, e.g. network attached cache
- G06F 2212/608: Details relating to cache mapping
- G06F 2212/7204: Capacity control, e.g. partitioning, end-of-life degradation
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method controlling near caches in a distributed cache environment including distributed cache servers is provided. The method includes steps of: a specific distributed cache server among the distributed cache servers, if a request signal for original cache data is obtained from a client node, transmitting replicated cache data for the original cache data to the client node, to support the client node to store and refer to the replicated cache data in its corresponding near cache storage part, and managing a reference map with a correspondence between the client node referring to the replicated cache data, and the original cache data; and if the original cache data is changed, checking the number of the client nodes referring to the replicated cache data by referring to the reference map, and invalidating the replicated cache data according to the number of the checked client nodes.

## Claims

### Claim 1

A method for controlling one or more near caches in a distributed cache environment which includes a plurality of distributed cache servers, comprising steps of:
(a) a specific distributed cache server among the plurality of distributed cache servers, if a request signal for original cache data is obtained from at least one client node, (i) transmitting replicated cache data for the original cache data to the at least one client node, to thereby support the at least one client node to store and refer to the replicated cache data in its corresponding near cache storage part, and (ii) generating or updating or supporting another device to generate or update a reference map which has mapping information between the at least one client node referring to the replicated cache data and the original cache data;
(b) the specific distributed cache server monitoring or supporting another device to monitor a changed state of the original cache data included in the reference map, to thereby check a validity of the replicated cache data; and
(c) the specific distributed cache server, if the replicated cache data is determined as not valid, checking or supporting another device to check the number of the client nodes currently referring to the replicated cache data by referring to the reference map, and invalidating or supporting another device to invalidate the replicated cache data according to the number of the checked client nodes.

### Claim 2 (depends on 1)

The method of claim 1, wherein, at the step of (c), the specific distributed cache server performs or supports another device to perform multicast-based invalidation or unicast-based invalidation according to the number of the checked client nodes.

### Claim 3 (depends on 2)

The method of claim 2, wherein the specific distributed cache server (i) performs the unicast-based invalidation if the number of the client nodes currently referring to the replicated cache data is same as or less than a preset first value and (ii) performs the multicast-based invalidation if the number of the client nodes currently referring to the replicated cache data is greater than the first value.

### Claim 4 (depends on 1)

The method of claim 1, wherein, at the step of (a), the at least one client node restricts entire storage capacity of the near cache storage part in which replicated cache data are stored or restricts the number of the replicated cache data stored in the near cache storage part.

### Claim 5 (depends on 4)

The method of claim 4, wherein the at least one client node deletes at least one selected among replicated cache data having been referred to at the oldest point of time, replicated cache data having been stored for the longest time, replicated cache data with the smallest capacity and replicated cache data with the largest capacity, in order to restrict the entire storage capacity or restrict the number of the replicated cache data.

### Claim 6 (depends on 1)

The method of claim 1, wherein, at the step of (a), the specific distributed cache server restricts the number of the client nodes, referring to the replicated cache data corresponding to the original cache data, to a preset second value.

### Claim 7 (depends on 6)

The method of claim 6, wherein, if the number of the client nodes referring to the replicated cache data exceeds the second value, the specific distributed cache server instructs particular client nodes which cause the number of the client nodes to exceed the second value to refer to the original cache data stored in the specific distributed cache server.

### Claim 8 (depends on 1)

The method of claim 1, wherein the specific distributed cache server is a distributed cache server currently storing the original cache data among the plurality of distributed cache servers.

### Claim 9 (depends on 1)

The method of claim 1, wherein, if the specific distributed cache server is determined as a distributed cache server which stores backup cache data corresponding to another original cache data stored in another distributed cache server, the specific distributed cache server (i) transmits replicated backup cache data for the backup cache data to the at least one client node in response to the request signal for said another original cache data from the at least one client node, (ii) generates or updates the reference map of the specific distributed cache server which has mapping information between the at least one client node referring to the replicated backup cache data and the backup cache data, or supports said another distributed cache server to generate or update another reference map of said another distributed cache server which has mapping information between the at least one client node referring to the replicated backup cache data and said another original cache data corresponding to the replicated backup cache data, and (iii) invalidates the replicated backup cache data in response to a change in said another original cache data.

### Claim 10

A specific distributed cache server for controlling one or more near caches in a distributed cache environment which includes a plurality of distributed cache servers, comprising:
a communication part for obtaining a request signal for original cache data from at least one client node; and
a processor for performing processes of (I) (i) transmitting replicated cache data for the original cache data to the at least one client node, to thereby support the at least one client node to store and refer to the replicated cache data in its corresponding near cache storage part, and (ii) generating or updating or supporting another device to generate or update a reference map which has mapping information between the at least one client node referring to the replicated cache data and the original cache data; (II) monitoring or supporting another device to monitor a changed state of the original cache data included in the reference map, to thereby check a validity of the replicated cache data; and (III) if the replicated cache data is determined as not valid, checking or supporting another device to check the number of the client nodes currently referring to the replicated cache data by referring to the reference map, and performing or supporting another device to invalidate the replicated cache data according to the number of the checked client nodes.

### Claim 11 (depends on 10)

The specific distributed cache server of claim 10, wherein, at the process of (III), the processor performs or supports another device to perform multicast-based invalidation or unicast-based invalidation according to the number of the checked client nodes.

### Claim 12 (depends on 11)

The specific distributed cache server of claim 11, wherein the processor (i) performs the unicast-based invalidation if the number of the client nodes currently referring to the replicated cache data is same as or less than a preset first value and (ii) performs the multicast-based invalidation if the number of the client nodes currently referring to the replicated cache data is greater than the first value.

### Claim 13 (depends on 10)

The specific distributed cache server of claim 10, wherein, at the process of (I), the at least one client node restricts entire storage capacity of the near cache storage part in which replicated cache data are stored or restricts the number of the replicated cache data stored in the near cache storage part.

### Claim 14 (depends on 13)

The specific distributed cache server of claim 13, wherein the at least one client node deletes at least one selected among replicated cache data having been referred to at the oldest point of time, replicated cache data having been stored for the longest time, replicated cache data with the smallest capacity and replicated cache data with the largest capacity, in order to restrict the entire storage capacity or restrict the number of the replicated cache data.

### Claim 15 (depends on 10)

The specific distributed cache server of claim 10, wherein, at the process of (I), the processor restricts the number of the client nodes, referring to the replicated cache data corresponding to the original cache data, to a preset second value.

### Claim 16 (depends on 15)

The specific distributed cache server of claim 15, wherein, if the number of the client nodes referring to the replicated cache data exceeds the second value, the processor instructs particular client nodes which cause the number of the client nodes to exceed the second value to refer to the original cache data stored in the specific distributed cache server.

### Claim 17 (depends on 10)

The specific distributed cache server of claim 10, wherein the specific distributed cache server is a distributed cache server currently storing the original cache data among the plurality of distributed cache servers.

### Claim 18 (depends on 10)

The specific distributed cache server of claim 10, wherein, if the specific distributed cache server is determined as a distributed cache server which stores backup cache data corresponding to another original cache data stored in another distributed cache server, the processor (i) transmits replicated backup cache data for the backup cache data to the at least one client node in response to the request signal for said another original cache data from the at least one client node, (ii) generates or updates the reference map of the specific distributed cache server which has mapping information between the at least one client node referring to the replicated backup cache data and the backup cache data, or supports said another distributed cache server to generate or update another reference map of said another distributed cache server which has mapping information between the at least one client node referring to the replicated backup cache data and said another original cache data corresponding to the replicated backup cache data, and (iii) invalidates the replicated backup cache data in response to a change in said another original cache data.
