Abstract: Systems and methods are disclosed for a self-indexing removable storage device. In certain embodiments, the removable storage device is configured to be connected to a memory reader of a host device. The removable storage device comprises storage media, a controller configured to run firmware, and a buffer. The controller is configured to, while connected to a first host device, receive a write operation from the first host device, monitor changes to the storage media caused by the write operation, and update a file index stored on the removable storage device with the monitored changes. The controller is further configured to, in response to connecting the removable storage device to a memory reader of a second host device, provide the file index to an application on the second host device, and cause the application to display files on the storage media based on the file index.

Abstract: Systems and methods are disclosed for a self-indexing removable storage device. In certain embodiments, the removable storage device is configured to be connected to a memory reader of a host device. The removable storage device comprises storage media, a controller configured to run firmware, and a buffer. The controller is configured to, while connected to a first host device, receive a write operation from the first host device, monitor changes to the storage media caused by the write operation, and update a file index stored on the removable storage device with the monitored changes. The controller is further configured to, in response to connecting the removable storage device to a memory reader of a second host device, provide the file index to an application on the second host device, and cause the application to display files on the storage media based on the file index.

Abstract: A storage system and method for executing file-based firmware commands and collecting response data are provided. In one embodiment, a storage system is provided comprising a memory and a controller. The controller is configured to: receive a request from a host in communication with the storage system to write data in a file, wherein the file is identified by a file path name; determine whether the file path name matches a predetermined file path name; in response to determining that the file path name does not match the predetermined file path name, write the data in the file; and in response to determining that the file path name matches the predetermined file path name, execute a command represented by the data. Other embodiments are provided.

Abstract: A storage system and method for executing file-based firmware commands and collecting response data are provided. In one embodiment, a storage system is provided comprising a memory and a controller. The controller is configured to: receive a request from a host in communication with the storage system to write data in a file, wherein the file is identified by a file path name; determine whether the file path name matches a predetermined file path name; in response to determining that the file path name does not match the predetermined file path name, write the data in the file; and in response to determining that the file path name matches the predetermined file path name, execute a command represented by the data. Other embodiments are provided.

Abstract: A mobile device with a unified media-centric user interface is provided. In one embodiment, the user interface contains one or more of the following features: a unified view of the home screen, navigating between various storage locations, dragging items to collection/folder, pinch and zoom feature, stats shown for each file type, storage usage view from the app, manual and automatic backup, and magic move (keeping a low-resolution version of the original files while moving). Other embodiments are possible, and each of the embodiments can be used alone or together in combination.

Abstract: A mobile device with a unified media-centric user interface is provided. In one embodiment, the user interface contains one or more of the following features: a unified view of the home screen, navigating between various storage locations, dragging items to collection/folder, pinch and zoom feature, stats shown for each file type, storage usage view from the app, manual and automatic backup, and magic move (keeping a low-resolution version of the original files while moving). Other embodiments are possible, and each of the embodiments can be used alone or together in combination.

Abstract: A mobile device with a unified media-centric user interface is provided. In one embodiment, the user interface contains one or more of the following features: a unified view of the home screen, navigating between various storage locations, dragging items to collection/folder, pinch and zoom feature, stats shown for each file type, storage usage view from the app, manual and automatic backup, and magic move (keeping a low-resolution version of the original files while moving). Other embodiments are possible, and each of the embodiments can be used alone or together in combination.

Abstract: A mobile device with a unified media-centric user interface is provided. In one embodiment, the user interface contains one or more of the following features: a unified view of the home screen, navigating between various storage locations, dragging items to collection/folder, pinch and zoom feature, stats shown for each file type, storage usage view from the app, manual and automatic backup, and magic move (keeping a low-resolution version of the original files while moving). Other embodiments are possible, and each of the embodiments can be used alone or together in combination.

Abstract: A memory system or flash card may include an algorithm for identifying and accounting for the rewrite frequency of data to be written to the card. The file system partition or file type of data may be used for monitoring rewrite frequency and predicting future rewrites. A learning algorithm that monitors rewrites may be implemented in firmware for accurate and dynamic identification of file types/partitions with the most likely rewrites. The identification of rewrites may be used to sort the data into groups (e.g. hot data=likely rewritten, and cold data=not likely to be rewritten). The hot data may stay in single level cell (SLC) update blocks longer, while the cold data can be moved to MLC blocks sooner.

Abstract: Systems and method for performing intelligent flash management are disclosed. A controller may determine if a write pattern exists between a set of writes associated with a first data chunk and a set of writes associated with a second data chunk based on whether a number of writes for first data chunk is equal to a number of writes for second data chunk; a degree to which a sequence of logical block address for the first data chunk matches the sequence of logical block addresses for the second data chunk; and a degree to which a size of each write for the first data chunk matches a size of each write for the second data chunk. The controller may then perform storage management operations based on whether or not a write pattern exists.

Abstract: A method for optimizing a boot up sequence includes, during a host idle time or during data transfer: obtaining a predicted read address from the a prediction table, prefetching from the non-volatile data store, and saving the prefetched data in memory. Also included is receiving a current read command issued by the host and if the read address matches the predicted read address, providing to the host the prefetched data saved in temporary memory, and indicating a match. If a match is not indicated, obtaining current data from the non-volatile data store corresponding to the read address of the current read command, and providing the current data to the host. If a match was not indicated, searching the data prediction table for the predicted read address that matches the read address corresponding to the current read command, and if found in the data prediction table, recording the offset value.

Abstract: A memory system or flash card may include an algorithm for identifying a pattern in a sustained or continuous write operation. In one example, a video recording device may be a host that continuously writes data to a memory card in an identifiable pattern. The pattern identification algorithm may be stored in the firmware of the memory card and used to schedule background operations during the predicted idle times in which the host is not writing data to the memory card.

Abstract: A method for optimizing a boot up sequence includes, during a host idle time or during data transfer: obtaining a predicted read address from the a prediction table, prefetching from the non-volatile data store, and saving the prefetched data in memory. Also included is receiving a current read command issued by the host and if the read address matches the predicted read address, providing to the host the prefetched data saved in temporary memory, and indicating a match. If a match is not indicated, obtaining current data from the non-volatile data store corresponding to the read address of the current read command, and providing the current data to the host. If a match was not indicated, searching the data prediction table for the predicted read address that matches the read address corresponding to the current read command, and if found in the data prediction table, recording the offset value.

Abstract: A memory system or flash card may include an algorithm for identifying and accounting for the rewrite frequency of data to be written to the card. The file system partition or file type of data may be used for monitoring rewrite frequency and predicting future rewrites. A learning algorithm that monitors rewrites may be implemented in firmware for accurate and dynamic identification of file types/partitions with the most likely rewrites. The identification of rewrites may be used to sort the data into groups (e.g. hot data=likely rewritten, and cold data=not likely to be rewritten). The hot data may stay in single level cell (SLC) update blocks longer, while the cold data can be moved to MLC blocks sooner.

Abstract: Systems and method for performing intelligent flash management are disclosed. A controller may determine if a write pattern exists between a set of writes associated with a first data chunk and a set of writes associated with a second data chunk based on whether a number of writes for first data chunk is equal to a number of writes for second data chunk; a degree to which a sequence of logical block address for the first data chunk matches the sequence of logical block addresses for the second data chunk; and a degree to which a size of each write for the first data chunk matches a size of each write for the second data chunk. The controller may then perform storage management operations based on whether or not a write pattern exists.

Abstract: A memory system or flash card may include an algorithm for identifying a pattern in a sustained or continuous write operation. In one example, a video recording device may be a host that continuously writes data to a memory card in an identifiable pattern. The pattern identification algorithm may be stored in the firmware of the memory card and used to schedule background operations during the predicted idle times in which the host is not writing data to the memory card.