IP Library Granted Patent US 9,934,244
Granted Patent B2
US 9,934,244 · App. 12/856,236 · Granted Apr 3, 2018

System and method for file format management

Inventors: Barrett M. Kreiner (Woodstock, GA); Jonathan L. Reeves (Roswell, GA); Ryan L. Schaub (Norcross, GA)
Assignee: AT&T INTELLECTUAL PROPERTY I, L.P.
G06F17/30179
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 9,934,244
App. No.
12/856,236
Granted
Apr 3, 2018
Kind
B2
Abstract

A method and system for managing access to file system objects enables an application to request access to a file system object via a file system transformer driver, which may extend the capabilities of a file system. The file system transformer driver may be configured to convert a data file format for the file system object to a data format requested by the application. The file system transformer driver may store the file system object in an internal data format using a file system on a storage device. The file system transformer driver may receive requests from applications via an operating system instruction.

Claims (36)

1. A method for managing a file system object, comprising:

executing, by a hardware processor, a disk operating system having a driver for accessing a hardware component;

receiving, by the hardware processor executing the disk operating system, a request for the file system object stored by the hardware component, the request associated with a software application, and the request specifying a data format used by the software application;

determining, by the hardware processor executing the disk operating system, a type of access specified by the software application in the request for the file system object stored by the hardware component;

if the type of access specified by the software application requests a write access to the file system object stored by the hardware component, then performing, by the hardware processor executing the disk operating system, a conversion that retrieves a block of data from the software application, the block of data associated with the file system object stored by the hardware component, and the conversion converting the block of data from the data format used by the software application into an internal data format used by the driver for accessing the hardware component; and

if the type of access specified by the software application requests a read access to the file system object stored by the hardware component, then performing, by the hardware processor executing the disk operating system, a different conversion that retrieves the block of data from the file system object stored by the hardware component and converts the block of data from the internal data format used by the driver to the data format used by the software application;

wherein the hardware processor differently converts the block of data according to the type of access specified by the software application.

2. The method of claim 1 , further comprising determining a file system identifier associated with the file system object.

3. The method of claim 1 , further comprising retrieving a conversion algorithm.

4. The method of claim 1 , further comprising utilizing an intermediate data format.

5. The method of claim 1 , further comprising executing a conversion driver to convert the block of data associated with the file system object.

6. A system, comprising:

a hardware processor; and

a memory device, the memory device storing instructions, the instructions when executed causing the processor to perform operations, the operations comprising:

executing a disk operating system having a driver for accessing a hardware component;

receiving a request for a file system object stored by the hardware component, the request associated with a software application, and the request specifying a data format used by the software application;

determining a type of access specified by the software application in the request for the file system object stored by the hardware component;

if the type of access specified by the software application requests a write access to the file system object stored by the hardware component, then performing a conversion that retrieves a block of data from the software application and converts the block of data from the data format used by the software application into an internal data format used by the driver for accessing the hardware component; and

if the type of access specified by the software application requests a read access to the file system object stored by the hardware component, then performing a different conversion that retrieves the block of data from the file system object stored by the hardware component and converts the block of data from the internal data format used by the driver to the data format used by the software application;

wherein the block of data associated with the file system object is differently converted according to the type of access specified by the software application.

7. The system of claim 6 , wherein the file system object is selected from a group comprising a storage partition, a file, a directory, a subdirectory, a storage volume, and an addressable storage location.

8. The system of claim 6 , further comprising a network adapter accessible by the hardware processor.

9. The system of claim 8 , wherein the operations further comprise receiving the file system object from the network adapter.

10. The system of claim 9 , wherein the operations further comprise receiving the file system object from a network file system.

11. A memory device storing instructions that when executed cause a hardware processor to perform operations, the operations comprising:

executing a disk operating system having a driver for accessing a hardware component;

receiving a request for a file system object stored by the hardware component, the request associated with a software application, and the request specifying a data format used by the software application;

determining a type of access specified by the software application in the request for the file system object stored by the hardware component;

if the type of access specified by the software application requests a write access to the file system object stored by the hardware component, then performing a conversion that retrieves a block of data from the software application and converts the block of data from the data format used by the software application into an internal data format used by the driver for accessing the hardware component; and

if the type of access specified by the software application requests a read access to the file system object stored by the hardware component, then performing a different conversion that retrieves the block of data from the file system object stored by the hardware component and converts the block of data from the internal data format used by the driver to the data format used by the software application;

wherein the block of data associated with the file system object is differently converted according to the type of access specified by the software application.

12. The memory device of claim 11 , wherein the operations further comprise interfacing with a network adapter.

13. The memory device of claim 11 , wherein the file system object is selected from a group comprising; a storage partition, a file, a directory, a subdirectory, a storage volume, and a randomly addressable storage location.

14. The memory device of claim 11 , wherein the operations further comprise receiving the request for the file system object via an operating system instruction.

15. The memory device of claim 11 , wherein the operations further comprise receiving the request for the file system object via a network connection.

16. The memory device of claim 11 , wherein the operations further comprise accessing the file system object via a network connection.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 2, 2010
From: KREINER, BARRETT M.; REEVES, JONATHAN L.; SCHAUB, RYAN L.
To: AT&T INTELLECTUAL PROPERTY I, L.P.
Reel/Frame 024932/0334 →
Continuity (1)
Related Publication 20120041964A1 · Feb 16, 2012