Network storage system for a download intensive environment

• US 8,959,199 B2
• Filed: 03/17/2009
• Issued: 02/17/2015
• Est. Priority Date: 03/18/2008
• Status: Active Grant

• Current Assignee: ReduxIO Systems Ltd. (Reduxio Systems, Inc.)
• Original Assignee: ReduxIO Systems Ltd. (Reduxio Systems, Inc.)
• Inventors: Peleg, Nir, Sagi, Or, Strasser, Amnon
• Primary Examiner(s): Mejia, Anthony
• Application Number:
  US12/405,734
• Publication Number:
  US 20090240764A1
• Time in Patent Office: 2,163 Days
• Field of Search: 709/200, 709/203, 709/224, 709/223, 709/219, 713/189, 713/165, 713/150, 726/2, 726/3, 726/28, 726/29
• US Class Current: 709/224
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 63/1408 by monitoring network traffic monitoring network traffic per se H04L43/00
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: 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]

Abstract

A network storage system for a download intensive environment is provided. The network storage comprises at least a data storage server (DSS) that includes an interface enabling connection of the DSS to a network at a location that enables at least a view of network transactions performed by a plurality of clients; a storage unit; and a system adapted to monitor the network transactions occurring on the network and identification of the network transactions as belonging to a registered client of the DSS, and storing in the storage the transactions with an identification corresponding to the registered client.

Claims

1. A data storage server (DSS), comprising:

an interface enabling connection of the DSS to a network at a location that enables at least a view of network transactions performed by a plurality of clients;

a content addressable storage (CAS); and

a system configured to monitor the network transactions occurring on the network and identify the network transactions as belonging to a registered client of the DSS, and store in the storage the transactions with an identification corresponding to the registered client, wherein the system is further configured to instruct a first client to send to a second client a digest value and a first challenge value;

instruct the second client to send to the first client an acknowledgement comprising the digest value, a first response and a second challenge;

instruct the first client to send the digest value and a second response;

instruct the second client to send the digest value, a retrieval key and a—

decryption key; and

instruct the first client to delete encrypted data corresponding to the digest value, wherein the first client has access to encrypted data of the second client enabled by the retrieval key and the decryption key.

2. The DDS of claim 1, wherein the system comprises at least a processor capable of executing appropriate sequences of instructions.

3. The DSS of claim 1, wherein the system is further configured to cause the movement of data from the storage to a backend storage (BES) pool by providing an appropriate stream address.

4. The DSS of claim 3, wherein the movement of data is responsive to a request received from the registered client.

5. The DSS of claim 1, wherein the system is further configured to receive from the registered client a stored operation including an array, wherein the array comprises a stream, a byte offset and a length.

6. The DSS of claim 5, wherein the system is further configured to send to the registered client responsive of the stored operation a retrieval key or an error code.

7. The DSS of claim 1, wherein the system is further configured to receive from the registered client a retrieve operation comprising an array, wherein the array comprises a retrieval key, an offset, a byte count and an operation.

8. The DSS of claim 6, wherein the system is further configured to send to the registered client responsive of the retrieve operation an array comprising a retrieval key and at least one of a byte count or an error code, and corresponding data.

9. The DSS of claim 1, wherein the system is further configured to receive from the registered client one or more retrieval keys for one of the purposes of:

subscribing to a data, unsubscribing to a data.

10. The DSS of claim 9, wherein the system is further configured to send to the registered client an array comprising a retrieval key and one of an acknowledgement or an error code responsive of the subscribing or the subscribing operations.

11. The DSS of claim 1, wherein the system is further configured to receive from the registered client one or more digest values for the purpose of storing or removing a digest from the storage.

12. The DSS of claim 11, wherein the system is further configured to send to the registered client an array comprising a digest value, a store status and an array of registered clients responsive of the storing or removing operation.

13. The DSS of claim 11, wherein the system is further configured to send to the registered client an array comprising a digest value and one of an acknowledgement or an error code.

14. The DSS of claim 1, wherein the system is further configured to receive from the registered client a gather operation comprising an array, wherein the array comprises a retrieval key, an offset, and a byte count.

15. The DSS of claim 14, wherein the system is further configured to send to the registered client a retrieval key or an error code responsive to receiving the gather operation.

16. A method for logging data of registered clients in a download intensive network comprising:

capturing a data packet from the download intensive network;

indexing data of the data packet with a client identification (CID) unique to the registered client, when the data packet belongs to at least one of the registered clients;

storing the data in association with the client identification in a temporary storage;

storing the data in permanent storage once all packets corresponding to the data have been received;

instructing a first client to send to a second client a digest value and a first challenge value;

instructing the second client to send to the first client an acknowledgement comprising the digest value, a first response and a second challenge;

instructing the first client to send the digest value and a second response;

causing the second client to send the digest value, a retrieval key and a decryption key; and

instructing the first client to delete encrypted data corresponding to the digest value;

wherein the first client has access to encrypted data of the second client enabled by the retrieval key and the decryption key.

17. The method of claim 16, further comprising:

waiting to receive a next data packet when data packet does not belong to at least one of the registered clients.

18. The method of claim 16, further comprising:

monitoring network transactions performed by at least the registered clients, wherein monitoring of the network transactions is performed by a data storage server (DSS) connected to the download intensive network at a location that enables the view of the network transactions.

19. The method of claim 16, further comprising:

storing data in a content addressable storage (CAS).

20. A method for controlling a data storage server (DSS) in a download intensive network comprising:

receiving a download data downloaded by a registered client;

comparing data to the registered client stored operation on a respective virtual file system of the register client;

instructing the DSS to permanently store the data on a backend storage (BES) pool by providing an appropriate stream address, when there is match;

instructing a first client to send to a second client a digest value and a first challenge value;

instructing the second client to send to the first client an acknowledgement comprising the digest value, a first response and a second challenge;

instructing the first client to send the digest value and a second response;

instructing the second client to send the digest value, a retrieval key and a decryption key; and

instructing the first client to delete encrypted data corresponding to the digest value;

wherein the first client has access to encrypted data of the second client enabled by the retrieval key and the decryption key.

21. The method of claim 20, further comprising:

waiting to receive more download data when there is no match.

22. The method of claim 20, is being performed by the registered client, the registered client being previously registered on the DSS.

23. The method of claim 20, wherein the BES is a content addressable storage (CAS).

24. A method for sharing encrypted data in a data storage server (DSS) comprising:

sending a first challenge and a digest value from a first client to a second client for the purpose of confirming that an encrypted data may be jointly accessed by the first client and the second client;

receiving from the second client the digest value, a first response responsive of the first challenge and a second challenge sent from the second client;

sending from the first client to the second client the digest value and a second response responsive of the second challenge; and

receiving from the second client the digest value, a retrieval key and a decryption key;

wherein the first client can access the encrypted data using the retrieval key and the decryption key without the need to store a duplicate copy of the encrypted data from the first client use.

25. The method of claim 24, further comprising:

terminating the method upon one of;

no acknowledgement from the first client, no acknowledgement from the second client, failure to provide a correct the first response to the first challenge, failure to provide a correct the second response to the second challenge.

26. The method of claim 24, further comprising:

storing the encrypted data in a content addressable storage (CAS).