# US 2015/0106468 A1 · Storage system and data access method

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

- Number: US 2015/0106468 A1
- Document ID: US20150106468A1
- Status: Published application
- Kind: A1
- Application number: 14/397,607
- Filed: 2013-05-16
- Published: 2015-04-16
- Earliest claimed: 2012-05-17
- Assignees: NEC Corporation
- Applicants: NEC Corporation
- Inventors: Dai Kobayashi; Masaki Kan
- Web page: https://patentgrep.com/patent/US20150106468A1

## CPC

- H04L 41/082: the condition being updates or upgrades of network functionality
- G06F 3/061: {Improving I/O performance}
- G06F 3/0635: {by changing the path, e.g. traffic rerouting, path reconfiguration}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 12/0813: with a network or matrix configuration
- G06F 12/0815: Cache consistency protocols
- G06F 12/0868: Data transfer between cache memory and other subsystems, e.g. storage devices or host systems
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- H04L 67/5683: Storage of data provided by user terminals, i.e. reverse caching
- G06F 2212/1016: Performance improvement
- G06F 2212/466: Metadata, control data
- G06F 2212/622: State-only directory, i.e. not recording identity of sharing or owning nodes
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A distributed storage system which achieves high access performance simultaneously with maintaining the flexibility of allocation of data objects is disclosed. A client terminal includes an asynchronous cache that retains an correspondence relationship between an identifier of object data and an identifier of the storage node that is to handle an access request for the object data, and an access unit that determines the storage node that is to handle the access request on the basis of the correspondence relationship stored in the asynchronous cache, and that transmits the access request to the determined storage node, wherein the storage node includes a determination unit that determines, upon receiving the access request from the client terminal, whether the access request is to be handled by itself, and notifies the client terminal of the determined result, and an update unit that updates the storage node that is to handle the access request, and wherein the asynchronous cache changes the correspondence relationship in accordance with the update, the change being made asynchronous with the update by the storage nodes.

## Claims

### Claim 1

A storage system comprising:
a client terminal; and
a plurality of storage nodes,
wherein the client terminal includes an asynchronous cache that retains an correspondence relationship between an identifier of object data and an identifier of the storage node that is to handle an access request for the object data, and an access unit that determines the storage node that is to handle the access request on the basis of the correspondence relationship stored in the asynchronous cache, and that transmits the access request to the determined storage node,
wherein the storage node includes a determination unit that determines, upon receiving the access request from the client terminal, whether the access request is to be handled by itself, and notifies the client terminal of the determined result, and an update unit that updates the storage node that is to handle the access request, and
wherein the asynchronous cache changes the correspondence relationship in accordance with the update, the change being made asynchronous with the update by the storage nodes.

### Claim 2 (depends on 1)

The storage system according to claim 1, further comprising a server apparatus that accumulates a piece of update information representing content of the update by the storage node,
wherein, when the update unit of the storage node updates the storage node that is to handle the access request, the update unit notifies the server apparatus of the update information representing content of the update, and
wherein the asynchronous cache changes the correspondence relationship in accordance with the update information accumulated in the server apparatus, the change being made asynchronous with the update by each of the storage nodes.

### Claim 3 (depends on 2)

The storage system according to claim 2, wherein the server apparatus periodically notifies the update information to the client terminal, and the asynchronous cache changes the correspondence relationship in accordance with the update information which is notified by the server apparatus.

### Claim 4 (depends on 2)

The storage system according to claim 2, wherein the server apparatus notifies the update information to the client terminal when a data amount of the update information becomes larger than or equal to a predetermined size, and the asynchronous cache changes the correspondence relationship in accordance with the update information which is notified by the server apparatus.

### Claim 5 (depends on 2)

The storage system according to claim 2, wherein the access unit requests the sever apparatus to notify the update information to the client terminal when the determination unit determines the storage node is not to handle the access request, the storage node being determined on the basis of the correspondence relationship by the access unit, and the asynchronous cache changes the correspondence relationship in accordance with the update information which is notified by the server apparatus in response to the request.

### Claim 6 (depends on 1)

The storage system according to claim 1, wherein the determination unit transfers the access request to one of the storage nodes that is to handle the access request when the access request is not to be handled by the storage node itself which includes the determination unit.

### Claim 7 (depends on 1)

The storage system according to claim 1, wherein the asynchronous cache retains an correspondence relationship between an identifier of the object data which already being moved between the storage nodes and an identifier of the storage node that is to handle the access request for the object data, and
wherein, when the access unit fails to determine any one of the storage nodes that is to handle the access request on the basis of the correspondence relationship retained by the asynchronous cache, the access unit determines one of the storage nodes that is to handle the access request on the basis of a predetermined dispersion function, and transmits the access request to the determined storage node.

### Claim 8

A data access method comprising:
retaining, by a client terminal, an correspondence relationship between an identifier of object data and an identifier of the storage node that is to handle an access request for the object data into an asynchronous cache;
determining, by the client terminal, the storage node that is to handle the access request on the basis of the correspondence relationship stored in the asynchronous cache, and transmitting, by the client terminal, the access request to the determined storage node;
determining, by the storage node which receives the access request from the client terminal, whether or not the access request is to be handled by itself, and notifying, by the storage node, the client terminal of the determined result;
updating, by the storage node, the storage node that is to handle the access request; and
changing, by the client terminal, the correspondence relationship stored in the asynchronous cache in accordance with the update, the change being made asynchronous with the update by the storage node.

### Claim 9 (depends on 8)

The data access method according to claim 8, further comprising:
accumulating, by a server apparatus, a piece of update information representing content of the update by the storage node;
when updating, by the storage node, the storage node that is to handle the access request, notifying, by the storage node, the server apparatus of the update information representing content of the update; and
changing, by the client terminal, the correspondence relationship stored in the asynchronous cache in accordance with the update information accumulated in the server apparatus, the change being made asynchronous with the update by the storage nodes.

### Claim 10 (depends on 9)

The data access method according to claim 9, further comprising: notifying, by the server apparatus, the update information to the client terminal periodically; and
changing, by the client terminal, the correspondence relationship stored in the asynchronous cache in accordance with the update information which is notified by the server apparatus.

### Claim 11 (depends on 9)

The data access method according to claim 9, further comprising:
notifying, by the server apparatus, the update information to the client terminal when a data amount of the update information becomes larger than or equal to a predetermined size; and
changing, by the client terminal, the correspondence relationship stored in the asynchronous cache in accordance with the update information which is notified by the server apparatus.

### Claim 12 (depends on 9)

The data access method according to claim 9, further comprising:
requesting, by the client terminal, the sever apparatus to notify the update information to the client terminal when the storage node, which received the access request, determines the storage node is not to handle the access request, the storage node being determined on the basis of the correspondence relationship by the client terminal; and
changing, by the client terminal, the correspondence relationship stored in the asynchronous cache in accordance with the update information which is notified by the server apparatus in response to the request.

### Claim 13 (depends on 8)

The data access method according to claim 8, further comprising:
when the access request is not to be handled by the storage node itself which received the access request, transferring, by the storage node, the access request to the storage node that is to handle the access request.

### Claim 14 (depends on 8)

The data access method according to claim 8, wherein the asynchronous cache retains an correspondence relationship between an identifier of the object data which already being moved between storage nodes and an identifier of the storage node that is to handle the access request for the object data, and
wherein, when any one of the storage nodes that is to handle the access request fails to be determined by the client terminal on the basis of the correspondence relationship retained by the asynchronous cache, one of the storage nodes that is to handle the access request is determined by the client terminal on the basis of a predetermined dispersion function, and the access request is transmitted to the determined storage node by the client terminal.
