Fast file server methods and systems

• US 9,167,027 B2
• Filed: 05/16/2014
• Issued: 10/20/2015
• Est. Priority Date: 08/27/2007
• Status: Active Grant

• Current Assignee: PME IP Pty., Ltd.
• Original Assignee: PME IP Pty., Ltd.
• Inventors: Westerhoff, Malte, Stalling, Detlev
• Primary Examiner(s): BOUTAH, ALINA A
• Application Number:
  US14/279,755
• Publication Number:
  US 20140258385A1
• Time in Patent Office: 522 Days
• Field of Search: 709/203, 709/249, 709/250, 712/9, 710/7, 710/10, 710/20, 710/21
• US Class Current: 1/1
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06
• CPC Class Codes: G06F 16/183 Provision of network file services by network file servers, e.g. by using NFS, CIFS network file access protocols H04L67/1097
• CPC Class Codes: G06F 21/6209 to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
• CPC Class Codes: H04L 63/06 for supporting key management in a packet data network cryptographic mechanisms or cryptographic arrangements for key management H04L9/08
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/01 Protocols
• 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]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols

Abstract

The invention provides, in one aspect, an improved system for data access comprising a file server that is coupled to a client device or application executing thereon via one or more networks. The server comprises static storage that is organized in one or more directories, each containing, zero, one or more files. The server also comprises a file system operable, in cooperation with a file system on the client device, to provide authorized applications executing on the client device access to those directories and/or files. Fast file server (FFS) software or other functionality executing on or in connection with the server responds to requests received from the client by transferring requested data to the client device over multiple network pathways. That data can comprise, for example, directory trees, files (or portions thereof), and so forth.

Claims

1. A method for a client to receive data from a server, comprising the steps of:

executing an application on the client which sends requests to the server for access to a configuration file on one or more network interfaces identified in the configuration file and monitored by the server;

receiving access to the configuration file including the one or more network interfaces and one or more security keys from the server;

generating a request for data on the server using the one or more network interfaces;

supplying the one or more security keys to the server to access the data; and

receiving the data over one or more of the one or more networks interfaces.

2. The method of claim 1, where the data comprises any of directory trees, files, or portions thereof.

3. The method of claim 1, where the server controls access to the configuration file.

4. The method of claim 1, where the server controls access to the configuration file by way of access permissions associated with the configuration file.

5. The method of claim 1, where the one or more network interfaces specified by the configuration file are physically independent networks.

6. The method of claim 1, where the one or more security keys are used to identify the requested data transfer.

7. The method of claim 1, where receipt of the configuration file is based on access permissions associated with the configuration file.

8. A method to supply data from a server, comprising the steps of:

listening for requests to the server on one or more network interfaces identified in a configuration file, the configuration file including one or more security keys;

responding to a request for data including validating the request based on the one or more security keys; and

supplying the data to a client over the one or more network interfaces identified in the configuration file.

9. The method of claim 8, where the data comprises any of directory trees, files, or portions thereof.

10. The method of claim 8, where the server controls access to the configuration file.

11. The method of claim 8, where the server controls access to the configuration file by way of access permissions associated with the configuration file.

12. The method of claim 8, where the one or more networks interfaces specified by the configuration file are physically independent networks.

13. The method of claim 8, where the one or more security keys are used to identify the requested data transfer.

14. The method of claim 8, where the server supplies a first set of data requested by a first client device to the first client device and a second set of data requested by a second client device to the second client device.

15. A method of data transfer between a server and a client comprising:

communicating with the server to request access to a configuration file on one or more network interfaces stored in the configuration file and monitored by the server;

receiving access to the configuration file stored on the server, the configuration file including the one or more network interfaces and one or more security keys from the server, based on the server verifying access authority of the client to receive the configuration file;

communicating with the server via at least one of the one or more network interfaces;

generating a request for data from the server using at least one of the one or more network interfaces; and

receiving the requested data, where the requested data is transferred over at least one of the one or more network interfaces.

16. The method of claim 15, where the data comprises any of directory trees, files, or portions thereof.

17. The method of claim 15, where the server verifies access authority to the configuration file by way of access permissions associated with the configuration file.

18. The method of claim 15, where the one or more networks specified by the configuration file are physically independent networks.

19. The method of claim 15, where one or more security keys are present in the configuration file, where the one or more security keys are used to verify access authority for the requested data transfer.

20. The method of claim 15, where the server transfers a first set of data requested by a first client device to the first client device and a second set of data requested by a second client device to the second client device.