Distributed storage service systems and architecture

• US 8,452,927 B2
• Filed: 01/24/2008
• Issued: 05/28/2013
• Est. Priority Date: 01/02/2008
• Status: Active Grant

• Current Assignee: Jpmorgan Chase Bank NA As The Agent
• Original Assignee: Sandisk Technologies Incorporated (Western Digital Corporation)
• Inventors: Nochimowski, Alain, Pomerantz, Itzhak, Rave, Micha
• Primary Examiner(s): RUTZ, JARED IAN
• Application Number:
  US12/019,573
• Publication Number:
  US 20090172217A1
• Time in Patent Office: 1,951 Days
• Field of Search: 711/154, 709/216
• US Class Current: 711/154
• CPC Class Codes: G06F 12/0246 in block erasable memory, e.g. flash memory
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0607 by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
• CPC Class Codes: G06F 3/0655 Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
• CPC Class Codes: G06F 3/0664 at device level, e.g. emulation of a storage device or system
• CPC Class Codes: G06F 3/0679 Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]

Abstract

Various methods, devices and systems are described for providing distributed storage services. A data storage device is capable of initiating a communication session with an external entity such as a local host computer (and vice versa) coupled directly to the data storage device, a remote server computer, or directly with remote data storage devices with or without intervention by a local host computer.

Claims

1. A local storage device (LSD), comprising:

a HD/LSD interface providing a communication path between a host device (HD) and the LSD, wherein the LSD does not utilize any interface to a device external to the HD other than that HD/LSD interface;

a controller in communication with the HD/LSD interface, the controller configured to;

generate a LSD logical request independent of the HD, wherein the LSD logical request is not created to serve a HD initiated process; and

send the LSD logical request to the HD over the HD/LSD interface to prompt the HD to;

utilize a network interface to provide a network link between the HD and a remote application associated with a device external to the HD and the LSD included in a network, or

provide a local communication path between the LSD and a local application other than a LSD driver that is associated with a local device external to the LSD, wherein the local communication path is not the network link and wherein the local device is in local communication with the HD;

wherein the local device is a second LSD managed by the host device;

wherein the device external to the host device and the LSD is a network device (ND); and

wherein when the network is an IP protocol based network, then the LSD and the second LSD are assigned an LSD IP address and a second LSD IP address, respectively, the host device is assigned a host device IP address, and the ND is assigned an ND IP address.

2. The LSD of claim 1, wherein the HD comprises a host device file system (HDFS) arranged to generate a block command;

and

wherein the LSD comprises at least one storage area managed at least by the HDFS, wherein the HDFS manages the at least one storage area by generating a block command that is passed to the at least one storage area by way of the HD/LSD interface.

3. The LSD of claim 2, wherein the HD comprises the LSD driver, and

wherein the LSD driver is in communication with the HDFS and is configured to facilitate the passing of the block command from the HDFS to the at least one storage area by way of the HD/LSD interface.

4. The LSD of claim 3, wherein the LSD is configured to prompt the HD by:

sending the LSD logical request to the HD in response to a poll from the HD, wherein the host device'"'"'s polling is independent of any HDFS initiated process and the LSD driver;

or

associating the LSD logical request with a LSD interrupt signal, and raising the LSD interrupt to the attention of the host device when the HD is not polling the LSD.

5. The LSD of claim 1, wherein the controller is configured to detect a set of LSD parameters operation and, as a result, generates the LSD logical request as a detection logical request.

6. The LSD of claim 5, wherein to detect the set of parameters operation, the controller is further configured to:

compare a current state of the LSD to a set of rules governing operation of the LSD.

7. The LSD of claim 6, wherein the detected parameters are selected from a group consisting of:

a data content back-up parameter, a data content parameter, a logical storage parameter, a physical storage parameter, a violation of rules parameter, and a host device IP address.

8. The LSD of claim 7, wherein the data content parameter is selected from a group consisting of:

a file size, a file type, a file name, and a file keyword,

wherein the logical storage parameter includes a remaining capacity, and a LSD IP address, and

wherein the physical storage parameter is selected from a group consisting of;

a wear level, a number of bad blocks, and a number of bit flips.

9. The LSD of claim 8, wherein the detection logical request prompts the HD to establish the network link between the LSD and the remote application, and

wherein the LSD and the remote application logically interact over the network link to perform a requested detection process without further intervention by the HD except to maintain the network link, or the detection logical request prompts the HD to establish the local communication path between the LSD and the local application,

wherein the LSD and the local application logically interact over the local communication path to perform the requested detection process without further intervention by the HD except to maintain the local communication path, and

wherein the requested detection process is selected from a group consisting of:

a content backup process, a content sharing process, an event notification process, a request for a remote instruction process, a request for usage/access right process, a registration to a remote server process, and a request to a discovery server process.

10. The LSD of claim 9, wherein the controller is further configured to associate the detection logical request with the polling by the host device, thereby prompting the host device to establish the network link between the LSD and the remote application or to establish the local communication path between the LSD and the local application.

11. The LSD of claim 9, wherein the controller is configured to associate the LSD logical request with a LSD interrupt signal, and to raise the LSD interrupt to the attention of the host device, thereby prompting the host device to establish the network link between the LSD and the remote application or to establish the local communication path between the LSD and the local application.

12. The LSD of claim 1, wherein the network interface is included in the host device.

13. A local storage device (LSD), comprising:

a HD/LSD interface providing a communication path between the LSD and a host device (HD) comprising a host device file system, wherein the LSD does not utilize any interface to a device external to the HD other than the HD/LSD interface;

at least one storage area managed by the HD, wherein the HD is configured to manage the at least one storage area by sending a block command to the at least one storage area by way of the HD/LSD interface; and

a controller in communication with the HD/LSD interface and the at least one storage area, the controller configured to;

generate a LSD logical request that is not created to serve a HD initiated process;

prompt the HD to;

utilize a network interface to provide a network link between the HD and a remote application associated with a device external to the HD and the LSD included in a network of interconnected devices, or

provide a local communication path between the LSD and a local application other than a LSD driver that is associated with a local device external to the LSD, wherein the local communication path is not the network link and wherein the local device is in local communication with the host device;

execute a requested process with the LSD logical request;

associate the LSD logical request with a LSD interrupt; and

raise the LSD interrupt to the attention of the host device, thereby prompting the host device to execute the requested process;

wherein the local device is a second LSD managed by the host device;

wherein the device external to the host device and the LSD is a network device (ND); and

wherein when the network is an IP protocol based network, then the LSD and the second LSD are assigned an LSD IP address and a second LSD IP address, respectively, the host device is assigned a host device IP address, and the ND is assigned an ND IP address.

14. A local storage device (LSD), comprising:

a HD/LSD interface providing a communication path between the LSD and a host device (HD), wherein the LSD does not utilize any interface to a device external to the HD other than that interface provided by the HD;

at least one storage area managed at least by the HD, wherein the HD is configured to manage the at least one storage area by sending a block command to the at least one storage area by way of the HD/LSD interface; and

a controller in communication with the HD/LSD interface and the at least one storage area, the controller configured to;

send a LSD logical request that is not created to serve a HD initiated process to the HD in response to the HD polling the LSD, wherein the polling by the HD is independent of any HD initiated process and wherein the LSD logical request prompts the HD to;

utilize a network interface to provide a network link between the host device and a remote application associated with a device included network of interconnected devices external to the host device and the LSD, or

provide a local communication path between the LSD and a local application other than a LSD driver that is associated with a local device external to the LSD wherein the local communication path is not the network link, wherein the local device is in local communication with the host device;

wherein the local device is a second LSD managed by the host device;

wherein the device external to the host device and the LSD is a network device (ND); and

wherein when the network is an IP protocol based network, then the LSD and the second LSD are assigned an LSD IP address and a second LSD IP address, respectively, the host device is assigned a host device IP address, and the ND is assigned an ND IP address.

15. The LSD of claim 14 wherein the second LSD is managed by the HD.