IP Library Granted Patent US 11,075,978
Granted Patent B2
US 11,075,978 · App. 16/834,936 · Granted Jul 27, 2021

Fast file server methods and systems

Inventors: Malte Westerhoff (Berlin, DE); Detlev Stalling (Berlin, DE)
Assignee: PME IP PTY LTD
H04L67/06G06F16/13G06F16/183G06F21/6209H04L63/06H04L63/20H04L67/1097H04L67/34H04L67/42H04L69/14
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,075,978
App. No.
16/834,936
Granted
Jul 27, 2021
Kind
B2
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 (34)

1. A method for rendering images comprising:

a) executing on a server a fast file server software application, where the server includes a server digital data processor, a static storage, a file system, and a port communicating with one or more independent networks, where the fast file server software application generates a configuration file on the server, where the configuration file comprises an associated read permission, and specifies one or more network interfaces selected from the one or more independent networks, where the one or more network interfaces allow transfer of data between the server and a client;

b) receiving a render request at the server from the client, where the render request requests access to the configuration file;

c) validating the render request at the server with the fast file server software application comprising:

i) verifying that the client has permission to access the data; and

ii) verifying that the one or more network interfaces are available for a transfer of the data; and

d) transferring the data to the client over the one or more network interfaces.

2. The method of claim 1 , where the one or more network interfaces are physically independent networks.

3. The method of claim 1 , where the data are transmitted by a remote procedure call selected from the group consisting of Component Object Model (COM), Distributed Component Object Model (DCOM) and Common Object Request Broker Architecture (CORBA).

4. The method of claim 1 , where the one or more independent networks comprise a plurality of independent networks, where the plurality of independent networks comprise a plurality of physically independent computers, where a computer of the plurality of physically independent computers is connected to at least the plurality of physically independent computers.

5. The method of claim 1 , where the data comprise a directory tree and two or more files.

6. The method of claim 5 , where the directory tree comprises the configuration file.

7. The method of claim 5 , where the fast file server software application writes the configuration file into the directory tree.

8. The method of claim 5 , where the associated read permission is as restrictive as a read permission of any file in the directory tree.

9. The method of claim 1 , where the configuration file further comprises one or more access keys.

10. The method of claim 9 , where the one or more access keys proves that the client had read permission to access the configuration file.

11. The method of claim 9 , where the one or more access keys are randomly generated.

12. The method of claim 1 , where the configuration file further comprises one or more security keys.

13. The method of claim 12 , where the one or more security keys are used to validate a render request.

14. The method of claim 12 , where the one or more security keys are adapted to be used by the client in the data transfer.

15. The method of claim 12 , where the one or more security keys are adapted to be used by the fast file server software application in the data transfer.

16. The method of claim 12 , where the data comprise any of a directory tree, a file, and portions thereof.

17. The method of claim 16 , where the one or more security keys are used to identify the directory tree.

18. The method of claim 1 , where the configuration file further specifies at least two network interfaces.

19. The method of claim 18 , where requested data are transferred in parallel over the at least two network interfaces.

20. A method for rendering images comprising:

a) executing on a server a fast file server software application, where the server includes a server digital data processor, a static storage, a file system, and a port communicating with one or more independent networks, where the fast file server software application generates a configuration file on the server, where the configuration file comprises an associated read permission, and specifies one or more network interfaces selected from the one or more independent networks, where the one or more network interfaces allow transfer of data between the server and a client;

b) receiving a render request at the server from the client, where the render request requests access to the configuration file;

c) validating the render request at the server with the fast file server software application comprising:

i) verifying that the render request comprises one or more security keys;

ii) verifying that the security keys are valid;

iii) verifying that the client has permission to access the data; and

iv) verifying that the one or more network interfaces are available for a transfer of the data; and

d) transferring the data to the client over the one or more network interfaces.

Continuity (8)
Continuation 16036438 · Jul 16, 2018
Continuation 15679581 · Aug 17, 2017
Continuation 15384822 · Dec 20, 2016
Continuation 14878708 · Oct 8, 2015
Continuation 14279755 · May 16, 2014
Continuation 13755366 · Jan 31, 2013
Continuation 11845511 · Aug 27, 2007
Related Publication 20200228592A1 · Jul 16, 2020
Cited By (3)
US 12,316,699 US 12,340,444 US 12,369,874