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 round robin system with interleaved weighted and priority arbiters to serve on-demand bandwidth of a storage system are provided. In one embodiment, a host assigns a priority and weight to each of a plurality of memory commands. The memory commands are sent to the storage system in a priority round-robin manner, in which memory commands assigned to a relatively-higher priority level are sent to the storage system before memory commands assigned to a relatively-lower priority level. Further, memory commands assigned to a given priority level are sent to the storage system in a weighted round-robin manner in accordance with their assigned weight. Other embodiments are provided.

Abstract: A round robin system with interleaved weighted and priority arbiters to serve on-demand bandwidth of a storage system are provided. In one embodiment, a host assigns a priority and weight to each of a plurality of memory commands. The memory commands are sent to the storage system in a priority round-robin manner, in which memory commands assigned to a relatively-higher priority level are sent to the storage system before memory commands assigned to a relatively-lower priority level. Further, memory commands assigned to a given priority level are sent to the storage system in a weighted round-robin manner in accordance with their assigned weight. 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 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: 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.