Abstract: A system and method are disclosed for an event lock storage device. The storage device includes a user partition and an event partition (which may be associated with an event). The storage device receives data from a host device, and stores the data in the user partition. In response to receiving an indication of an event, the storage device may designate the data as part of the event partition. The event partition may include a set of access rules that is different from the user partition, such as more restrictive rules for modification or deletion of a file containing the data.

Abstract: A system and method are disclosed for an event lock storage device. The storage device includes a user partition and an event partition (which may be associated with an event). The storage device receives data from a host device, and stores the data in the user partition. In response to receiving an indication of an event, the storage device may designate the data as part of the event partition. The event partition may include a set of access rules that is different from the user partition, such as more restrictive rules for modification or deletion of a file containing the data.

Abstract: A system and method are disclosed for an event lock storage device. The storage device includes a user partition and an event partition (which may be associated with an event). The storage device receives data from a host device, and stores the data in the user partition. In response to receiving an indication of an event, the storage device may designate the data as part of the event partition. The event partition may include a set of access rules that is different from the user partition, such as more restrictive rules for modification or deletion of a file containing the data.

Abstract: A storage device with a health status check feature is disclosed. In one embodiment, the storage device keeps track of the number of erase cycles performed on the memory of the storage device. The storage device also stores a value of the predicted limit on the number of times that erase cycles can be performed on the memory. In response to a request from a host device for the health status of the memory, the storage device can provide the host device with information about how many erase cycles have been performed on the memory as compared to the predicted limit.

Abstract: A system and method are disclosed for an event lock storage device. The storage device includes a user partition and an event partition (which may be associated with an event). The storage device receives data from a host device, and stores the data in the user partition. In response to receiving an indication of an event, the storage device may designate the data as part of the event partition. The event partition may include a set of access rules that is different from the user partition, such as more restrictive rules for modification or deletion of a file containing the data.

Abstract: A storage device with a health status check feature is disclosed. In one embodiment, the storage device keeps track of the number of erase cycles performed on the memory of the storage device. The storage device also stores a value of the predicted limit on the number of times that erase cycles can be performed on the memory. In response to a request from a host device for the health status of the memory, the storage device can provide the host device with information about how many erase cycles have been performed on the memory as compared to the predicted limit.

Abstract: The embodiments of the invention include a computer-readable medium having computer-executable components comprising at least one agent having at least one sensor component, having a goal or change method component, and at least one behavior component. The at least one sensor component generates at least one event based at least in part on at least one generated value from the goal or change method component. The at least one behavior component determines whether to activate a thread of execution based at least in part on the at least one generated event from the at least one sensor component. The system complex execution threads can be generated by any operator on agents level, events level, sensors level and behaviors level.