# US 2008/0307155 A1 · Method of Interfacing A Host Operating Through A Logical Address Space With A Direct File STorage Medium

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0307155 A1
- Document ID: US20080307155A1
- Status: Published application
- Kind: A1
- Application number: 11/760,469
- Filed: 2007-06-08
- Published: 2008-12-11
- Earliest claimed: 2007-06-08
- Assignees: SanDisk Technologies LLC
- Inventors: Alan W. Sinclair
- Web page: https://patentgrep.com/patent/US20080307155A1

## CPC

- G06F 3/061: {Improving I/O performance}
- G06F 3/0631: {by allocating resources to storage systems}
- G06F 3/0643: {Management of files}
- G06F 3/0679: {Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]}
- G06F 12/0246: {in block erasable memory, e.g. flash memory}
- G06F 2212/1016: Performance improvement
- G06F 2212/2022: Flash memory
- G06F 2212/7201: Logical to physical mapping or translation of blocks or pages
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method and system for interfacing a system operating through a logical address space with a direct file storage (DFS) medium is disclosed. The method includes receiving data associated with addresses in a logical block address (LBA) format from a host system and generating file objects manageable by the DFS medium based on a determination of the correlation of the LBA data to host file data. The memory system includes non-volatile memory using the DFS format, an interface for receiving LBA format data, and a controller configured to communicate with the host via an LBA interface and generate file objects from the LBA format data correlated to the host application files usable by the memory system.

## Claims

### Claim 1

A method of transferring data between a host system and a re-programmable non-volatile mass storage system, the method comprising:
receiving data associated with addresses in a logical block address (LBA) format at the mass storage system from the host system;
assembling a group of data within the received data from the host system based on a correlation of the group of data to an application file on the host system; and
mapping LBA addresses for the group of data to offset addresses within a data object identified by a unique filename.

### Claim 2 (depends on 1)

The method of claim 1, further comprising directly translating the group of data identified by the unique filename and offset addresses into physical addresses of blocks of memory cells.

### Claim 3 (depends on 1)

The method of claim 1, further comprising receiving correlation information from the host regarding a relation of received data to the application file.

### Claim 4 (depends on 3)

The method of claim 3, wherein receiving correlation information comprises receiving a host system file identifier from the host system.

### Claim 5 (depends on 4)

The method of claim 4, wherein the host system file identifier is received with a file tagging command from the host system.

### Claim 6 (depends on 5)

The method of claim 5, wherein the file tagging command and the host system file identifier are received prior to receiving data associated with LBA format addresses.

### Claim 7 (depends on 4)

The method of claim 4, further comprising updating a host system file identifier table comprising a mapping of the host system file identifier to the unique filename.

### Claim 8 (depends on 8)

The method of claim 8, comprising storing the host system file identifier table in volatile memory in the mass storage system.

### Claim 9 (depends on 1)

The method of claim 1, further comprising analyzing activity of a host system operating system to determine the correlation of the group of data to the application file on the host system.

### Claim 10 (depends on 9)

The method of claim 9, wherein analyzing the host system operating system activity comprises observing host operating system activity detectable at an interface of the mass storage system and, if a predetermined sequence of operating system activity is recognized, analyzing pre-data write activity to determine a correlation of LBA data to be written by the host to an application file in the host.

### Claim 11 (depends on 1)

The method of claim 1, further comprising analyzing LBA addresses or address sequences of the received data and determining the correlation based at least in part on LBA address transition information.

### Claim 12 (depends on 1)

The method of claim 1, further comprising the mass storage system analyzing preceding write operations by the host system to LBA addresses associated with directory or FAT data and determining the correlation based at least in part on write activity to the directory or FAT LBA addresses.

### Claim 13 (depends on 1)

The method of claim 1, further comprising the mass storage system analyzing LBA addresses or address sequences, and preceding write operations by the host system to LBA addresses associated with directory or FAT data, and determining the correlation based on LBA address transition information and write activity to the directory or FAT LBA addresses.

### Claim 14 (depends on 1)

The method of claim 1, further comprising assigning a file separator status to a detected transition between a sequence of read or write operations of file metadata from the host system and determining the correlation as coextensive with a sequence of data received between successive detected transitions between the sequence of read or write operations of file metadata.

### Claim 15

A method of transferring data between a host system and a re-programmable non-volatile mass storage system, the method comprising:
receiving data associated with addresses in a logical block address (LBA) format at the mass storage system from the host system;
selecting, based on information from the host system, a correlation method to determine a correlation of received data to host system application files;
determining a correlation of a group of the received data to a host system application file; and
mapping LBA addresses for the group of data to offset addresses within a data object identified by the unique filename.

### Claim 16 (depends on 15)

The method of claim 15, further comprising directly translating data represented by the unique filename and data offset into physical addresses of blocks of memory cells in the mass storage system.

### Claim 17 (depends on 15)

The method of claim 15, further comprising receiving correlation information from the host regarding a relation of received data to the host system application file.

### Claim 18 (depends on 17)

The method of claim 17, wherein receiving correlation information comprises receiving a host system file identifier from the host system.

### Claim 19 (depends on 18)

The method of claim 18, wherein the host system file identifier is received with a file tagging command from the host system.

### Claim 20 (depends on 19)

The method of claim 19, wherein the file tagging command and the host system file identifier are received prior to receiving data associated with LBA format addresses.

### Claim 21

A method of transferring data between a host system and a re-programmable non-volatile mass storage system, the method comprising:
receiving data associated with addresses in a logical block address (LBA) format at the mass storage system from the host system;
determining if there is a correlation of a group of the received data to a host system application file;
assigning a unique file name to the group of the received data if the correlation is determined and mapping LBA addresses for the group of data to the unique file name and a data offset; and
assigning the unique file name to a contiguous range of LBA addresses in the received data if the correlation is not determined and mapping the contiguous range of LBA addresses to the unique file name and a data offset.

### Claim 22

A method of transferring data between a host system and a re-programmable non-volatile mass storage system, the method comprising:
determining if the host system is configured to provide host system file identifiers prior to writing logical block address (LBA) format data, wherein the host system file identifiers indicate a correlation of subsequently transmitted LBA data to application files on the host system;
if the host system is configured to provide host system file identifiers, then:
receiving a host system file identifier;
receiving a group of data associated with addresses in a logical block address (LBA) format from the host system and with the host system file identifier;
mapping the host system file identifier to a unique file name; and
mapping LBA addresses for the received data to offset addresses in a data object identified by a unique filename; and
if the host system is not configured to provide host system file identifiers, then:
automatically correlating received LBA format data to application files on the host system without host system file identifiers;
assigning a unique filename to a group of received data determined to correlate to an application file; and
mapping LBA addresses for the received data to offset addresses in a data object identified by a unique filename.

### Claim 23 (depends on 22)

The method of claim 22, wherein automatically correlating received LBA format data further comprises analyzing activity of a host system operating system to determine the correlation of the group of data to the application file on the host system.

### Claim 24 (depends on 23)

The method of claim 23, wherein analyzing the host system operating system activity comprises observing host operating system activity detectable at an interface of the mass storage system and, if a predetermined sequence of operating system activity is recognized, analyzing pre-data write activity to determine a correlation of LBA data to be written by the host to an application file in the host.

### Claim 25 (depends on 22)

The method of claim 22, wherein automatically correlating received LBA format data further comprises analyzing LBA addresses or address sequences of the received data and determining the correlation based at least in part on LBA address transition information.

### Claim 26 (depends on 22)

The method of claim 22, wherein automatically correlating received LBA format data further comprises the mass storage system analyzing preceding write operations by the host system to LBA addresses associated with directory or FAT data and determining the correlation based at least in part on write activity to the directory or FAT LBA addresses.

### Claim 27 (depends on 22)

The method of claim 22, wherein automatically correlating received LBA format data further comprises the mass storage system analyzing LBA addresses or address sequences, and preceding write operations by the host system to LBA addresses associated with directory or FAT data, and determining the correlation based on LBA address transition information and write activity to the directory or FAT LBA addresses.

### Claim 28 (depends on 22)

The method of claim 22, wherein automatically correlating received LBA format data further comprises assigning a file separator status to a detected transition between a sequence of read or write operations of file metadata from the host system and determining the correlation as coextensive with a sequence of data received between successive detected transitions between the sequence of read or write operations of file metadata.
