US20050177698A1 - Method for partitioning memory mass storage device - Google Patents
Method for partitioning memory mass storage device Download PDFInfo
- Publication number
- US20050177698A1 US20050177698A1 US11/102,109 US10210905A US2005177698A1 US 20050177698 A1 US20050177698 A1 US 20050177698A1 US 10210905 A US10210905 A US 10210905A US 2005177698 A1 US2005177698 A1 US 2005177698A1
- Authority
- US
- United States
- Prior art keywords
- host
- storage device
- drive
- area
- controller
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- G06F21/78—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure storage of data
- G06F21/80—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure storage of data in storage media based on magnetic or optical technology, e.g. disks with sectors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/14—Protection against unauthorised use of memory or access to memory
- G06F12/1458—Protection against unauthorised use of memory or access to memory by checking the subject access rights
- G06F12/1466—Key-lock mechanism
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F2003/0697—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers device management, e.g. handlers, drivers, I/O schedulers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0662—Virtualisation aspects
- G06F3/0664—Virtualisation aspects at device level, e.g. emulation of a storage device or system
Definitions
- the present invention relates to mass storage device, and particularly to a method for partitioning a memory mass storage device.
- hard disk drives are widely used in current computer system, there are still a variety of deficiencies regarding such rotating, magnetic mass storage devices, like an inherent latency during accessing the hard disk drives, high power consumption, being unable to withstand the physical shock, and having a large weight for portable computer devices.
- a non-volatile memory mass storage device like a flash memory disk drive, is a nice choice for replacing a hard disk.
- Each memory mass storage device always comprises two portions; one is a controller part, and the other is a memory module.
- the semiconductor technology allows such a memory storage device to withstand many of the kinds of physical shock and reduce power consumption or weight.
- These flash memory storage devices are also widely used and accepted for all the current computer devices, like desktop PC, laptop, PDA, DSC, and so on.
- Each of current mass storage devices, no matter hard disk drives or memory storage devices is always configured as a mass storage drive by the host. This drive could be partitioned into a plurality of “logical” drives by the host. For example, the host just executes a “partition program” and then the partition information is written into the drive. When next time power-on, such a drive partitioned by the host will be recognized as multiple ‘logical’ drive.
- a drive is composed of a plurality of logical blocks, and the partition information is generally located on the first block, logical block address 0 (LBA 0 ). If the first block is defective or infected by the computer virus, all the logical drives indicated by the partition information may not be detected by the host. It is a risk for a drive partitioned into multiple logical drives by the host.
- the object of the present invention is to provide a method for partitioning a memory storage device into multiple drives. Such a method is performed by the controller, instead of the host.
- Each of said multiple drives is exactly a drive for the host, but not a logical drive. If the host executes a “partition program” to partition each drive and then a copy of partition information will be written into the first block of each drive. Thereby, it reduces the possibility of partition information defect or computer virus infection.
- a drive could be subdivided into a variety of areas; some are freely accessed by any end users and the others can be accessed just for the specific users passing the password identification. Thereby, the function of data protection or security could be implemented.
- FIG. 1 shows a computer system with a memory storage device.
- FIG. 2 shows a conventional method for the usage of a logical space and configuration of a memory storage device
- FIG. 3 shows a conventional structure of disk partition performed by the host.
- FIG. 4 shows that the controller partitions a logical space of a memory storage device into two drives.
- FIG. 5 shows the data structure of the information block according to the present invention.
- FIG. 6 shows that the controller partitions a logical space of a mass storage device into a public area and a security area, both areas belonging to the same drive.
- FIG. 7 shows that the security area will be accessed by the host after passing the password identification.
- FIG. 8 shows the data structure of information block according to the present invention.
- FIG. 9 shows that the controller partitions a logical space of a memory storage device into two drives, each of which includes a public area and a security area.
- the public area of each drive can be free accessed by the host.
- FIG. 10 shows that the security area of first drive will be accessed by the host after passing the password identification.
- FIG. 11 shows the data structure of the information block according to the present invention.
- FIG. 12 shows the state flow for a memory storage device with or without the memory module.
- FIG. 13 shows the state change for switching the public area and the security area.
- a memory storage device generally comprises two portions; one is the controller and the other is the memory module.
- the architecture of a memory storage device 106 consists of a controller 102 , and a memory module 104 .
- the controller 102 is coupled to host end 100 by host interface 108 and coupled to the memory module 104 by memory interface 110 .
- the task of the controller 102 is to communicate with host end 100 and manage the memory module 104 .
- the memory module 104 includes at least one memory chip, like flash memory, PROM, ROM, or EEPROM for storing data therein.
- a memory storage device is configured as a drive 204 by the host.
- a drive 204 includes a plurality of logical blocks, each of which can be addressed by the host; namely, the host can access all the logical space 200 including logical block 0 , logical block 1 , and logical block M- 1 .
- a memory chip generally is divided into a plurality of storage units, like blocks.
- the physical space 202 of the memory module includes physical block 0 , physical block 1 , . . . , and physical block N- 1 .
- the logical space 200 used by the host is always less than the physical space 202 , because some of the physical blocks may be defective or used by the controller for managing the memory module.
- One task of the controller is to create the logical space 200 for host access. Indeed, the host can not directly address the physical space 202 so that the controller must maintain the mapping relations between the logical blocks and the physical blocks.
- Such a mapping information is always called as a mapping table and can be stored in the specific physical blocks or loaded into the SRAM within the controller. If a host asks for reading a particular logical block, the controller will look up the mapping table for identifying which physical block to be accessed, transfer data from the physical block to itself, and then transfer data from itself to the host.
- a controller In the prior art as shown in FIG. 2 , a controller generally allocates all the logical space 200 to the drive 204 so that the size of the drive 204 used by the host is equal to that of the logical space 200 .
- the host In order to managing a variety of files, the host would partition the drive 204 into multiple logical drives before using these logical drives for storing data.
- a storage device like a hard disk or a memory storage device, is partitioned into 4 logical drives by the host.
- the partition structure is compatible with DOS® and the partition information, called partition table 301 , is stored at the beginning area of the logical space, logical block address 0 (LBA 0 ).
- the beginning area is called master boot record (MBR) also, in addition to partition table 301 , some information for host booting was stored therein.
- MLR master boot record
- partition table 301 point out where each partition is located.
- a partition is as a logical drive so that the host can fully use 4 logical drives after partitioning the logical space provided by the controller.
- This partition way performed by the host results in a variety of deficiencies. For example, if the partition table 301 of MBR is defective or infected by the computer virus, all the logical drives may not be detected anymore.
- the partition structure performed by the host is a open standard, so that any user using the host can easily free access all the files in any logical drives. Some important files, like system files, may be deleted by careless end users; some private, confidential documents, like your financial information, may be found by any intended users. There are no security or data protection functions for such a partition way performed by the host.
- the controller within the memory storage device has partitioned the logical space 200 into multiple areas before the host uses the memory storage device, as shown in FIG. 4 .
- Each area is allocated to each drive for use with the host.
- the logical space 200 is partitioned into two areas by the controller, the area 0 404 allocated to drive 400 and the area 1 406 allocated to drive 402 .
- the partition information is stored in a particular physical block, called information block 408 .
- FIG. 5 it shows the data structure of the information block according to the present invention.
- the memory chip information 500 records how many memory chips there are within the memory storage device and their sizes.
- the number of drives 502 is the total drives that can be used by the host. In this case, this value is 2.
- the partition information of each drive 504 includes drive 0 505 and drive 1 509 .
- the drive 0 505 in FIG. 5 includes area 0 starting address 506 , length 508 , and attribute 510 .
- the starting address 506 and the length 508 determine the range of area 0 404 .
- the attribute 510 specifies the area 0 404 access mode for the host, like read-only or full access mode.
- the drive 1 509 includes area 1 starting address 512 , length 514 , and attribute 516 .
- the function is like the foregoing descriptions.
- the starting address 512 and the length 514 determine the range of area 1 406 .
- the attribute 516 specifies the area 1 406 access mode for the host, like read-only or full access mode.
- the controller will read the information block into the SRAM within the controller after initial power-on.
- the host will ask for some basic information about the memory storage device, like the number of drives for the memory storage device and the size of each drive.
- the controller will respond to host requests.
- the area 0 404 is allocated to the drive 400 configured by the host and the area 1 406 is allocated to the drive 402 configured by the host.
- the controller partitions the total logical space of the memory storage device into multiple areas, which belong to multiple drives respectively.
- These multiple drives are all independent drives, instead of the logical drives created by the host.
- partition program When the host executes a “partition program” to partition each independent drive for creating at least one logical drive, and then a copy of partition information will be written into the first block of each independent drive; thus, each independent drive has its own partition information. Thereby, it reduces the possibility of partition information defect or computer virus infection.
- the memory storage device can increase the security function.
- the controller partitions the logical space 200 into two areas, area 0 602 and area 1 604 .
- the area 0 602 is called a public area which can be free accessed by the host, or any end users
- the area 1 604 is called a security area which can be accessed by the host or the specific end user only after passing the identification of the password for controlling the access right of the area 1 604 .
- These two areas belong to the same drive 600 used by the host, but the host only can access each of them once.
- the memory chip information 800 records how many memory chips there are within the memory storage device and their sizes.
- the number of drives 802 is the total drives that can be used by the host. In this case , this value is 1.
- the partition information of each drive 804 includes only drive 0 .
- the drive 0 805 in FIG. 8 includes public area 0 starting address & length 806 , security area 1 starting address & length 808 , password 810 , and attribute 812 .
- the 806 and 808 determine the ranges of public area 0 602 and security area 1 604 .
- the password 810 is for controlling the access right of the security area 1 604 .
- the attribute 812 specifies each area access mode for the host, like read-only or full access mode.
- the controller will read the information block into the SRAM within the controller after initial power-on. According the information block data loaded into the SRAM, the controller will respond to host requests for configuring the memory storage device.
- the number of drives is 1 and the size of the drive 600 is as that of the public area 0 602 . Accordingly, the public area 0 602 of the drive 600 can be free accessed by the host, but the security area 1 604 can not be seen by the host or any end user after the initial configuration.
- a security management program is used for managing the security functions. If a specific end user wants to access the security area 1 604 of the drive 600 , the said security management software is executed first then, the specific end user enters a password to the executed program. Finally, this security management program enables the host to send a password to the memory storage device for accessing the security area 1 604 .
- the said security management program can be stored in any public area of the memory storage device and becomes a portable tool for using the security function.
- the controller After received the password from the host, the controller compares the host input password with the password 810 loaded into the SRAM of the controller. As shown in FIG. 7 , if the host passes the password identification,.the security area 1 604 of the drive 600 can be accessed by the host or the specific end user. For those end users using this security function, some important files could be stored in the security area 1 604 to prevent a careless or an intended user from deleting or copying these private data.
- the combinations of previous two skills make it possible to partition a memory storage device into multiple drives, each with the security function.
- the controller partitions the logical space 200 into two drives and then partitioned each drive into a public area and a security area.
- FIG. 11 shows the data structure of information block for such a partition.
- the memory chip information 1100 records how many memory chips there are within the memory storage device and their sizes.
- the number of drives 1102 is the total drives that can be used by the host. In this case , this value is 2.
- the partition information of each drive 1104 includes drive 0 1105 and drive 1 1111 .
- the drive 0 1105 includes public area 0 starting address & length 1106 , security area 1 starting address & length 1108 , password 1110 , and attribute 1112 .
- the 1106 and 1108 respectively determine the ranges of public area 0 906 and security area 1 908 within drive 902 in FIG. 9 .
- the password 1110 is for controlling the access right of the security area 1 908 .
- the attribute 812 specifies the each area access mode for the host, like read-only or full access mode.
- the drive 1 1111 includes public area 2 starting address & length 1114 , security area 3 starting address & length 1116 , password 1118 , and attribute 1120 .
- the 1114 and 1116 respectively determine the ranges of public area 2 910 and security area 3 912 within drive 904 in FIG. 9 .
- the password 1118 is for controlling the access right of the security area 3 912 .
- the attribute 1120 specifies the each area access mode for the host, like read-only or full access mode.
- the controller will read the information block into the SRAM within the controller after initial power-on. According the information block data loaded into the SRAM, the controller will respond to host requests for configuring the memory storage device.
- the number of drives is 2
- the size of the drive 902 is the same as that of the public area 0 906
- the size of the drive 904 is the same as that of the public area 2 910 . Accordingly, the public area 0 906 of the drive 902 and the public area 2 910 of the drive 904 can be free accessed by the host, but the security area 1 908 of the drive 902 and the security area 3 912 of the drive 904 can not be seen by the host or any end user after the initial configuration.
- the said security management program is executed first, then, the specific end user enters a password to the executed program. Finally, this security management program enables the host to send a password to the memory storage device for accessing the security area 1 908 .
- the controller compares the host input password with the password 1110 loaded into the SRAM of the controller. As shown in FIG. 10 , if the host passes the password identification, the security area 1 908 of the drive 902 can be accessed by the host or the specific end user.
- Such a partition not only reduces the possibility of MBR defect or computer virus infection, but also realizes the security function for a memory mass storage device.
- the sizes of the security area or the public area are adjustable.
- the size of the public area can be set as zero and then only the security area exists for a particular drive.
- the memory storage device partitioned into multiple security drives can be substantially divided into two portions one is called a adapter with a controller inside and the other is a removable memory module including a plurality of memory chips.
- a adapter with a controller inside and the other is a removable memory module including a plurality of memory chips.
- Such a architecture is beneficial to the end users. If a end user wants to upgrade the capacity of the whole memory storage device, just removes the original memory module and then inserts a new, large-size memory module. Certainly, the information block data must be stored in the new memory module before insertion.
- FIG. 12 shows the controller state flow for a memory storage device with or without the memory module.
- the controller checks whether any memory module exists. If yes, go to step 1024 to read the information block into the SRAM of the controller and then determine each drive state, like drive 1 state 1206 , . . . , and drive n state 1208 .
- FIG. 13 is the continued flow chart of FIG. 12 and describes the operations for switching the public area and the security area.
- the drive m state 1300 represents any drive state.
- the default state for each drive is in public state 1304 that means the public area can be free accessed by the host command input 1302 after initial power-on.
- the public state 1304 of drive m will be transferred into the security state 1308 after the host passes the password identification.
- drive m is in the security state, it means the security area can be accessed by host command input 1310 .
- the security state will return to the public state.
- the controller will go into the state A 1210 .
- the controller always responds a no media message when the host asks for data access by the host command input 1212 .
- state A 1210 will go into the step 1204 . Accordingly, the controller will read the information block and realize the security functions as stated above.
- flash memories other than flash memories, above said embodiment is suitable for a variety of memories, such as flash memories, ROMs, PROMs, EPROMs, EEPROMs, and hard disks without departure from the scope and spirit of the present invention.
Abstract
A method for partitioning a memory mass storage device is disclosed. The partition task is performed by the controller within the memory mass storage device. Firstly, the controller partitions the logical space of the memory storage device into multiple areas, each area belonging to a particular drive. Secondly, the controller partitions the logical space of the memory storage device into a public area and a security area, both areas belonging to the same drive. Finally, the controller partitions the logical space of the memory storage device into multiple areas, which include public areas and security areas and belong to multiple drives.
Description
- The present invention relates to mass storage device, and particularly to a method for partitioning a memory mass storage device.
- Although hard disk drives are widely used in current computer system, there are still a variety of deficiencies regarding such rotating, magnetic mass storage devices, like an inherent latency during accessing the hard disk drives, high power consumption, being unable to withstand the physical shock, and having a large weight for portable computer devices.
- A non-volatile memory mass storage device, like a flash memory disk drive, is a nice choice for replacing a hard disk. Each memory mass storage device always comprises two portions; one is a controller part, and the other is a memory module. The semiconductor technology allows such a memory storage device to withstand many of the kinds of physical shock and reduce power consumption or weight. These flash memory storage devices are also widely used and accepted for all the current computer devices, like desktop PC, laptop, PDA, DSC, and so on. Each of current mass storage devices, no matter hard disk drives or memory storage devices, is always configured as a mass storage drive by the host. This drive could be partitioned into a plurality of “logical” drives by the host. For example, the host just executes a “partition program” and then the partition information is written into the drive. When next time power-on, such a drive partitioned by the host will be recognized as multiple ‘logical’ drive.
- From the host point of view, a drive is composed of a plurality of logical blocks, and the partition information is generally located on the first block, logical block address 0(LBA 0). If the first block is defective or infected by the computer virus, all the logical drives indicated by the partition information may not be detected by the host. It is a risk for a drive partitioned into multiple logical drives by the host.
- Furthermore, because the host can easily free access all the data, some important files, like system files, may be deleted by careless end users. Another aspects of this case, the right of data access is too open to meet the private, security requirements. It is another risk or inconvenience.
- Accordingly, the object of the present invention is to provide a method for partitioning a memory storage device into multiple drives. Such a method is performed by the controller, instead of the host. Each of said multiple drives is exactly a drive for the host, but not a logical drive. If the host executes a “partition program” to partition each drive and then a copy of partition information will be written into the first block of each drive. Thereby, it reduces the possibility of partition information defect or computer virus infection. Moreover, a drive could be subdivided into a variety of areas; some are freely accessed by any end users and the others can be accessed just for the specific users passing the password identification. Thereby, the function of data protection or security could be implemented. The various objects and advantages of the present invention will be more readily understood from the following detailed description when read in conjunction with the appended drawing.
-
FIG. 1 shows a computer system with a memory storage device. -
FIG. 2 shows a conventional method for the usage of a logical space and configuration of a memory storage device -
FIG. 3 shows a conventional structure of disk partition performed by the host. -
FIG. 4 shows that the controller partitions a logical space of a memory storage device into two drives. -
FIG. 5 shows the data structure of the information block according to the present invention. -
FIG. 6 shows that the controller partitions a logical space of a mass storage device into a public area and a security area, both areas belonging to the same drive. -
FIG. 7 shows that the security area will be accessed by the host after passing the password identification. -
FIG. 8 shows the data structure of information block according to the present invention. -
FIG. 9 shows that the controller partitions a logical space of a memory storage device into two drives, each of which includes a public area and a security area. The public area of each drive can be free accessed by the host. -
FIG. 10 shows that the security area of first drive will be accessed by the host after passing the password identification. -
FIG. 11 shows the data structure of the information block according to the present invention. -
FIG. 12 shows the state flow for a memory storage device with or without the memory module. -
FIG. 13 shows the state change for switching the public area and the security area. - A memory storage device generally comprises two portions; one is the controller and the other is the memory module. As shown in
FIG. 1 , the architecture of amemory storage device 106 consists of acontroller 102, and amemory module 104. Thecontroller 102 is coupled tohost end 100 byhost interface 108 and coupled to thememory module 104 bymemory interface 110. The task of thecontroller 102 is to communicate withhost end 100 and manage thememory module 104. Thememory module 104 includes at least one memory chip, like flash memory, PROM, ROM, or EEPROM for storing data therein. - As shown in
FIG. 2 , a memory storage device is configured as adrive 204 by the host. From the host point of view, such adrive 204 includes a plurality of logical blocks, each of which can be addressed by the host; namely, the host can access all thelogical space 200 includinglogical block 0,logical block 1, and logical block M-1. A memory chip generally is divided into a plurality of storage units, like blocks. AsFIG. 2 , thephysical space 202 of the memory module includesphysical block 0,physical block 1, . . . , and physical block N-1. Thelogical space 200 used by the host is always less than thephysical space 202, because some of the physical blocks may be defective or used by the controller for managing the memory module. One task of the controller is to create thelogical space 200 for host access. Indeed, the host can not directly address thephysical space 202 so that the controller must maintain the mapping relations between the logical blocks and the physical blocks. Such a mapping information is always called as a mapping table and can be stored in the specific physical blocks or loaded into the SRAM within the controller. If a host asks for reading a particular logical block, the controller will look up the mapping table for identifying which physical block to be accessed, transfer data from the physical block to itself, and then transfer data from itself to the host. - Partition performed by the host
- In the prior art as shown in
FIG. 2 , a controller generally allocates all thelogical space 200 to thedrive 204 so that the size of thedrive 204 used by the host is equal to that of thelogical space 200. In order to managing a variety of files, the host would partition thedrive 204 into multiple logical drives before using these logical drives for storing data. AsFIG. 3 , a storage device, like a hard disk or a memory storage device, is partitioned into 4 logical drives by the host. The partition structure is compatible with DOS® and the partition information, called partition table 301, is stored at the beginning area of the logical space, logical block address 0(LBA0). The beginning area is called master boot record (MBR) also, in addition to partition table 301, some information for host booting was stored therein. - The contents of partition table 301 point out where each partition is located. A partition is as a logical drive so that the host can fully use 4 logical drives after partitioning the logical space provided by the controller. This partition way performed by the host results in a variety of deficiencies. For example, if the partition table 301 of MBR is defective or infected by the computer virus, all the logical drives may not be detected anymore. Besides, the partition structure performed by the host is a open standard, so that any user using the host can easily free access all the files in any logical drives. Some important files, like system files, may be deleted by careless end users; some private, confidential documents, like your financial information, may be found by any intended users. There are no security or data protection functions for such a partition way performed by the host.
- Partition performed by the controller
- In our present invention, the controller within the memory storage device has partitioned the
logical space 200 into multiple areas before the host uses the memory storage device, as shown inFIG. 4 . Each area is allocated to each drive for use with the host. AsFIG. 4 , thelogical space 200 is partitioned into two areas by the controller, the area0 404 allocated to drive 400 and thearea1 406 allocated to drive 402. The partition information is stored in a particular physical block, calledinformation block 408. AsFIG. 5 , it shows the data structure of the information block according to the present invention. Thememory chip information 500 records how many memory chips there are within the memory storage device and their sizes. The number ofdrives 502 is the total drives that can be used by the host. In this case, this value is 2. The partition information of each drive 504 includesdrive0 505 anddrive1 509. With reference toFIG. 4 also, thedrive 0 505 inFIG. 5 includesarea0 starting address 506,length 508, andattribute 510. The startingaddress 506 and thelength 508 determine the range of area0 404. Theattribute 510 specifies the area0 404 access mode for the host, like read-only or full access mode. Thedrive1 509 includes area1 starting address 512, length 514, andattribute 516. The function is like the foregoing descriptions. The starting address 512 and the length 514 determine the range ofarea1 406. Theattribute 516 specifies thearea1 406 access mode for the host, like read-only or full access mode. Once the memory storage device is plugged into the slot attached in the host, the controller will read the information block into the SRAM within the controller after initial power-on. In order to correctly configure this memory storage device, the host will ask for some basic information about the memory storage device, like the number of drives for the memory storage device and the size of each drive. According the information block data loaded into the SRAM, the controller will respond to host requests. As a result, the area0 404 is allocated to thedrive 400 configured by the host and thearea1 406 is allocated to thedrive 402 configured by the host. Comparing with the prior art inFIG. 2 , in the present invention, the controller partitions the total logical space of the memory storage device into multiple areas, which belong to multiple drives respectively. These multiple drives are all independent drives, instead of the logical drives created by the host. When the host executes a “partition program” to partition each independent drive for creating at least one logical drive, and then a copy of partition information will be written into the first block of each independent drive; thus, each independent drive has its own partition information. Thereby, it reduces the possibility of partition information defect or computer virus infection. - A security drive
- Using the same concept of the logical space partition performed by the controller, the memory storage device can increase the security function. In another preferred embodiment of the invention as
FIG. 6 , the controller partitions thelogical space 200 into two areas,area0 602 andarea1 604. To be easily understood, thearea0 602 is called a public area which can be free accessed by the host, or any end users thearea1 604 is called a security area which can be accessed by the host or the specific end user only after passing the identification of the password for controlling the access right of thearea1 604. These two areas belong to thesame drive 600 used by the host, but the host only can access each of them once. - As
FIG. 8 , it is the data structure of the information block for such a partition. Thememory chip information 800 records how many memory chips there are within the memory storage device and their sizes. The number ofdrives 802 is the total drives that can be used by the host. In this case , this value is 1. The partition information of each drive 804 includes only drive0. With reference toFIG. 6 also, thedrive 0 805 inFIG. 8 includes public area0 starting address &length 806, security area1 starting address &length 808,password 810, andattribute 812. The 806 and 808 determine the ranges ofpublic area0 602 andsecurity area1 604. Thepassword 810 is for controlling the access right of thesecurity area1 604. Theattribute 812 specifies each area access mode for the host, like read-only or full access mode. - Once the memory storage device is plugged into the slot attached in the host, the controller will read the information block into the SRAM within the controller after initial power-on. According the information block data loaded into the SRAM, the controller will respond to host requests for configuring the memory storage device. In this case, the number of drives is 1 and the size of the
drive 600 is as that of thepublic area0 602. Accordingly, thepublic area0 602 of thedrive 600 can be free accessed by the host, but thesecurity area1 604 can not be seen by the host or any end user after the initial configuration. - A security management program is used for managing the security functions. If a specific end user wants to access the
security area1 604 of thedrive 600, the said security management software is executed first then, the specific end user enters a password to the executed program. Finally, this security management program enables the host to send a password to the memory storage device for accessing thesecurity area1 604. The said security management program can be stored in any public area of the memory storage device and becomes a portable tool for using the security function. - After received the password from the host, the controller compares the host input password with the
password 810 loaded into the SRAM of the controller. As shown inFIG. 7 , if the host passes the password identification,.thesecurity area1 604 of thedrive 600 can be accessed by the host or the specific end user. For those end users using this security function, some important files could be stored in thesecurity area1 604 to prevent a careless or an intended user from deleting or copying these private data. - Multiple drives with the security function.
- In another preferred embodiment of the invention, the combinations of previous two skills make it possible to partition a memory storage device into multiple drives, each with the security function. As
FIG. 9 , at first, the controller partitions thelogical space 200 into two drives and then partitioned each drive into a public area and a security area.FIG. 11 shows the data structure of information block for such a partition. Thememory chip information 1100 records how many memory chips there are within the memory storage device and their sizes. The number ofdrives 1102 is the total drives that can be used by the host. In this case , this value is 2. The partition information of each drive 1104 includesdrive0 1105 anddrive1 1111. Thedrive0 1105 includes public area0 starting address &length 1106, security area1 starting address &length 1108,password 1110, andattribute 1112. The 1106 and 1108 respectively determine the ranges ofpublic area0 906 andsecurity area1 908 withindrive 902 inFIG. 9 . Thepassword 1110 is for controlling the access right of thesecurity area1 908. Theattribute 812 specifies the each area access mode for the host, like read-only or full access mode. Thedrive1 1111 includes public area2 starting address &length 1114, security area3 starting address &length 1116,password 1118, andattribute 1120. The 1114 and 1116 respectively determine the ranges ofpublic area2 910 andsecurity area3 912 withindrive 904 inFIG. 9 . Thepassword 1118 is for controlling the access right of thesecurity area3 912. Theattribute 1120 specifies the each area access mode for the host, like read-only or full access mode. - Once the memory storage device is plugged into the slot attached in the host, the controller will read the information block into the SRAM within the controller after initial power-on. According the information block data loaded into the SRAM, the controller will respond to host requests for configuring the memory storage device. In this case, the number of drives is 2, the size of the
drive 902 is the same as that of thepublic area0 906, and the size of thedrive 904 is the same as that of thepublic area2 910. Accordingly, thepublic area0 906 of thedrive 902 and thepublic area2 910 of thedrive 904 can be free accessed by the host, but thesecurity area1 908 of thedrive 902 and thesecurity area3 912 of thedrive 904 can not be seen by the host or any end user after the initial configuration. - If a specific end user wants to access the
security area1 908 of thedrive 902, the said security management program is executed first, then, the specific end user enters a password to the executed program. Finally, this security management program enables the host to send a password to the memory storage device for accessing thesecurity area1 908. After received the password from the host, the controller compares the host input password with thepassword 1110 loaded into the SRAM of the controller. As shown inFIG. 10 , if the host passes the password identification, thesecurity area1 908 of thedrive 902 can be accessed by the host or the specific end user. Such a partition not only reduces the possibility of MBR defect or computer virus infection, but also realizes the security function for a memory mass storage device. - However, in the present invention, the sizes of the security area or the public area are adjustable. As required, the size of the public area can be set as zero and then only the security area exists for a particular drive.
- Removable memory module
- In our invention, the memory storage device partitioned into multiple security drives, can be substantially divided into two portions one is called a adapter with a controller inside and the other is a removable memory module including a plurality of memory chips. Such a architecture is beneficial to the end users. If a end user wants to upgrade the capacity of the whole memory storage device, just removes the original memory module and then inserts a new, large-size memory module. Certainly, the information block data must be stored in the new memory module before insertion.
-
FIG. 12 shows the controller state flow for a memory storage device with or without the memory module. Instep 1202, the controller checks whether any memory module exists. If yes, go to step 1024 to read the information block into the SRAM of the controller and then determine each drive state, likedrive 1state 1206, . . . , and driven state 1208.FIG. 13 is the continued flow chart ofFIG. 12 and describes the operations for switching the public area and the security area. Thedrive m state 1300 represents any drive state. The default state for each drive is inpublic state 1304 that means the public area can be free accessed by thehost command input 1302 after initial power-on. If the host inputs a password for accessing the security area of a particular drive m, thepublic state 1304 of drive m will be transferred into thesecurity state 1308 after the host passes the password identification. When drive m is in the security state, it means the security area can be accessed byhost command input 1310. Moreover, if the host inputs alock command 1312, the security state will return to the public state. - If there is no memory module plugged in, the controller will go into the
state A 1210. During thestate A 1210, the controller always responds a no media message when the host asks for data access by thehost command input 1212. Once the memory module is plugged into the adapter,state A 1210 will go into thestep 1204. Accordingly, the controller will read the information block and realize the security functions as stated above. - Other than flash memories, above said embodiment is suitable for a variety of memories, such as flash memories, ROMs, PROMs, EPROMs, EEPROMs, and hard disks without departure from the scope and spirit of the present invention.
- The present invention is thus described, it will be obvious that the same may be varied in many ways. Such variations are not to be regarded as a departure from the spirit and scope of the present invention, and all such modifications as would be obvious to one skilled in the art are intended to be included within the scope of the following claims.
Claims (3)
1-17. (canceled)
18. A removable memory storage device, comprising:
at least two drives;
a controller, partitioning each of the drives, wherein at least one of the drives is partitioned into a public area and a security area, wherein the security area includes an access
wherein when the removable memory storage device is electrically connected to be accessed by the host, the host executes a security management program to request an input password from a user and the controller check the input password with the access password to see whether a match occurs,
wherein when the match occurs, the host can configure and access the security area of the specific drive.
19. The removable memory storage device of claim 18 , wherein the security management program is stored in the public area.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/102,109 US20050177698A1 (en) | 2002-06-01 | 2005-04-07 | Method for partitioning memory mass storage device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/160,519 US7114051B2 (en) | 2002-06-01 | 2002-06-01 | Method for partitioning memory mass storage device |
US11/102,109 US20050177698A1 (en) | 2002-06-01 | 2005-04-07 | Method for partitioning memory mass storage device |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/160,519 Division US7114051B2 (en) | 2002-06-01 | 2002-06-01 | Method for partitioning memory mass storage device |
Publications (1)
Publication Number | Publication Date |
---|---|
US20050177698A1 true US20050177698A1 (en) | 2005-08-11 |
Family
ID=29583178
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/160,519 Expired - Lifetime US7114051B2 (en) | 2002-06-01 | 2002-06-01 | Method for partitioning memory mass storage device |
US11/102,109 Abandoned US20050177698A1 (en) | 2002-06-01 | 2005-04-07 | Method for partitioning memory mass storage device |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/160,519 Expired - Lifetime US7114051B2 (en) | 2002-06-01 | 2002-06-01 | Method for partitioning memory mass storage device |
Country Status (5)
Country | Link |
---|---|
US (2) | US7114051B2 (en) |
JP (1) | JP2004030551A (en) |
KR (1) | KR100470413B1 (en) |
CN (1) | CN100419713C (en) |
TW (1) | TWI282496B (en) |
Cited By (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060174352A1 (en) * | 2001-07-25 | 2006-08-03 | Seagate Technology Llc | Method and apparatus for providing versatile services on storage devices |
US20060176595A1 (en) * | 2005-02-08 | 2006-08-10 | Olympus Imaging Corp. | Image recording apparatus |
US20070180210A1 (en) * | 2006-01-31 | 2007-08-02 | Seagate Technology Llc | Storage device for providing flexible protected access for security applications |
US20070250915A1 (en) * | 2006-04-25 | 2007-10-25 | Seagate Technology Llc | Versatile access control system |
US20070250710A1 (en) * | 2006-04-25 | 2007-10-25 | Seagate Technology Llc | Versatile secure and non-secure messaging |
US20080098166A1 (en) * | 2006-10-19 | 2008-04-24 | Sony Corporation | Data storage device and data controlling method |
US20080276065A1 (en) * | 2007-05-03 | 2008-11-06 | Samsung Electronics Co., Ltd. | Method of partitioning storage area of recording medium and recording medium using the method, and method of accessing recording medium and recording device using the method |
US20090106517A1 (en) * | 2007-10-23 | 2009-04-23 | Asustek Computer Inc. | Data protection method |
US20090235109A1 (en) * | 2006-04-25 | 2009-09-17 | Seagate Technology Llc | Hybrid computer security clock |
US20100262759A1 (en) * | 2009-04-08 | 2010-10-14 | Google Inc. | Data storage device |
US20100262766A1 (en) * | 2009-04-08 | 2010-10-14 | Google Inc. | Garbage collection for failure prediction and repartitioning |
US20100262979A1 (en) * | 2009-04-08 | 2010-10-14 | Google Inc. | Circular command queues for communication between a host and a data storage device |
US20100287217A1 (en) * | 2009-04-08 | 2010-11-11 | Google Inc. | Host control of background garbage collection in a data storage device |
KR100990973B1 (en) * | 2007-11-14 | 2010-11-19 | 한국전력공사 | Apparatus of processing data using raw area of removable storage device |
US7925894B2 (en) | 2001-07-25 | 2011-04-12 | Seagate Technology Llc | System and method for delivering versatile security, digital rights management, and privacy services |
US20140281322A1 (en) * | 2013-03-15 | 2014-09-18 | Silicon Graphics International Corp. | Temporal Hierarchical Tiered Data Storage |
Families Citing this family (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3513147B2 (en) * | 2002-05-29 | 2004-03-31 | 株式会社ハギワラシスコム | USB storage device and its control device |
US7114051B2 (en) * | 2002-06-01 | 2006-09-26 | Solid State System Co., Ltd. | Method for partitioning memory mass storage device |
US20040088513A1 (en) * | 2002-10-30 | 2004-05-06 | Biessener David W. | Controller for partition-level security and backup |
US8041957B2 (en) * | 2003-04-08 | 2011-10-18 | Qualcomm Incorporated | Associating software with hardware using cryptography |
JP2006527878A (en) * | 2003-06-16 | 2006-12-07 | コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ | Data processing circuit having multiple memories |
US7447911B2 (en) * | 2003-11-28 | 2008-11-04 | Lightuning Tech. Inc. | Electronic identification key with portable application programs and identified by biometrics authentication |
TWI282940B (en) * | 2003-12-02 | 2007-06-21 | Aimgene Technology Co Ltd | Memory storage device with a fingerprint sensor and method for protecting the data therein |
FR2864741A1 (en) * | 2003-12-30 | 2005-07-01 | Koninkl Philips Electronics Nv | DEVICE AND METHOD FOR STORING AUDIO / VIDEO DATA IN A HOME NETWORK. |
US7478246B2 (en) * | 2004-07-29 | 2009-01-13 | International Business Machines Corporation | Method for providing a scalable trusted platform module in a hypervisor environment |
US20060026422A1 (en) * | 2004-07-29 | 2006-02-02 | International Business Machines Corporation | Method, apparatus, and product for providing a backup hardware trusted platform module in a hypervisor environment |
US20060143417A1 (en) * | 2004-12-23 | 2006-06-29 | David Poisner | Mechanism for restricting access of critical disk blocks |
TWI296787B (en) * | 2005-01-19 | 2008-05-11 | Lightuning Tech Inc | Storage device and method for protecting data stored therein |
KR100676087B1 (en) * | 2005-03-24 | 2007-02-01 | 케이비 테크놀러지 (주) | Secure data storage apparatus with USB interface, and method thereof |
TWI262696B (en) * | 2005-06-17 | 2006-09-21 | Lightuning Tech Inc | Storage device and method for protecting data stored therein |
US8799680B2 (en) * | 2005-09-15 | 2014-08-05 | Microsoft Corporation | Transactional sealed storage |
US7921303B2 (en) * | 2005-11-18 | 2011-04-05 | Qualcomm Incorporated | Mobile security system and method |
US7634629B2 (en) | 2005-12-19 | 2009-12-15 | Intel Corporation | Mechanism to control access to a storage device |
US7624283B2 (en) * | 2006-02-13 | 2009-11-24 | International Business Machines Corporation | Protocol for trusted platform module recovery through context checkpointing |
US9198025B2 (en) * | 2006-05-04 | 2015-11-24 | Sandisk Il Ltd. | High-capacity SIM storage control |
US7509441B1 (en) | 2006-06-30 | 2009-03-24 | Siliconsystems, Inc. | Systems and methods for segmenting and protecting a storage subsystem |
US7447807B1 (en) | 2006-06-30 | 2008-11-04 | Siliconsystems, Inc. | Systems and methods for storing data in segments of a storage subsystem |
US20080046997A1 (en) * | 2006-08-21 | 2008-02-21 | Guardtec Industries, Llc | Data safe box enforced by a storage device controller on a per-region basis for improved computer security |
US20080140946A1 (en) * | 2006-12-11 | 2008-06-12 | Mark Charles Davis | Apparatus, system, and method for protecting hard disk data in multiple operating system environments |
US8549236B2 (en) | 2006-12-15 | 2013-10-01 | Siliconsystems, Inc. | Storage subsystem with multiple non-volatile memory arrays to protect against data losses |
US7966355B2 (en) * | 2007-02-13 | 2011-06-21 | Modu Ltd. | Interface for extending functionality of memory cards |
JP4561759B2 (en) * | 2007-02-21 | 2010-10-13 | ソニー株式会社 | Information processing apparatus, information recording medium, information processing method, and computer program |
US7900012B2 (en) | 2007-04-13 | 2011-03-01 | Phison Electronics Corp. | Secure storage apparatus and method for controlling the same |
US20090037678A1 (en) * | 2007-07-31 | 2009-02-05 | Giles Chris M | Protected portion of partition memory for computer code |
FR2933790B1 (en) * | 2008-07-10 | 2010-09-10 | Oberthur Technologies | MANAGEMENT OF A PHYSICAL MEMORY PARTITIONED IN AN ELECTRONIC ENTITY: METHOD AND DEVICE. |
KR100956255B1 (en) * | 2008-10-10 | 2010-05-06 | 순천향대학교 산학협력단 | Method for Data Security of Mobile Storage Device |
KR101014149B1 (en) | 2008-11-13 | 2011-02-14 | (주)인디링스 | Controller for solid state disk of controlling access to memory bank |
US8825940B1 (en) | 2008-12-02 | 2014-09-02 | Siliconsystems, Inc. | Architecture for optimizing execution of storage access commands |
US9176859B2 (en) * | 2009-01-07 | 2015-11-03 | Siliconsystems, Inc. | Systems and methods for improving the performance of non-volatile memory operations |
KR101031072B1 (en) * | 2009-02-16 | 2011-04-25 | 에스티에스반도체통신 주식회사 | portable memory device |
US10079048B2 (en) * | 2009-03-24 | 2018-09-18 | Western Digital Technologies, Inc. | Adjusting access of non-volatile semiconductor memory based on access time |
CA2700012C (en) * | 2009-04-15 | 2015-06-30 | Research In Motion Limited | Keeping file systems or partitions private in a memory device |
US8775770B2 (en) | 2009-04-15 | 2014-07-08 | Blackberry Limited | Keeping file systems or partitions private in a memory device |
EP2251807A1 (en) * | 2009-05-14 | 2010-11-17 | METADAT IT-Beratungs- und Entwicklungs-GmbH | Computer system to improve the control of access to data |
US20110082989A1 (en) * | 2009-10-01 | 2011-04-07 | Solid State System Co., Ltd. | Structure and method for making a storage card |
CN101847126B (en) * | 2009-10-27 | 2012-08-22 | 深圳市朗科科技股份有限公司 | Storage equipment partitioning device and method |
US8874981B2 (en) * | 2010-05-12 | 2014-10-28 | Mediatek Inc. | Method of creating target storage layout table referenced for partitioning storage space of storage device and related electronic device and machine-readable medium |
TWI426385B (en) * | 2010-06-29 | 2014-02-11 | Genesys Logic Inc | Method and system for accessing a storage drive with a large capacity |
CN102096641A (en) * | 2010-12-13 | 2011-06-15 | 沈晖 | Double-factor shadow password protection method for mobile storage medium data safety |
KR20120140104A (en) | 2011-06-20 | 2012-12-28 | 현대자동차주식회사 | Data storing method of memory |
CN102308285B (en) | 2011-07-26 | 2013-08-28 | 华为技术有限公司 | Memory bug application of application program |
TWI486765B (en) * | 2012-06-11 | 2015-06-01 | Phison Electronics Corp | Memory management method, memory controller and memory storage device using the same |
US9858006B1 (en) * | 2015-10-13 | 2018-01-02 | Xilinx, Inc. | Context driven memory circuits |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5974517A (en) * | 1996-09-17 | 1999-10-26 | Compaq Computer Corporation | Method and system for mounting a system partition as a logical drive while an operating system is operational by modifying a partition table |
US6400823B1 (en) * | 1996-12-13 | 2002-06-04 | Compaq Computer Corporation | Securely generating a computer system password by utilizing an external encryption algorithm |
US20020157027A1 (en) * | 2001-04-24 | 2002-10-24 | International Business Machines Corporation | Method and system for providing a trusted boot source in a partition |
US6532535B1 (en) * | 1998-02-24 | 2003-03-11 | Adaptec, Inc. | Method for managing primary and secondary storage devices in an intelligent backup and restoring system |
US6601152B1 (en) * | 1999-07-09 | 2003-07-29 | Fujitsu Limited | Storage apparatus, an access control apparatus for a recording medium and an access control method for a recording medium |
US6633962B1 (en) * | 2000-03-21 | 2003-10-14 | International Business Machines Corporation | Method, system, program, and data structures for restricting host access to a storage space |
US6647481B1 (en) * | 2002-01-31 | 2003-11-11 | Western Digital Ventures, Inc. | Method for accessing data storage locations having addresses within a hidden logical address range |
US7069447B1 (en) * | 2001-05-11 | 2006-06-27 | Rodney Joe Corder | Apparatus and method for secure data storage |
US7114051B2 (en) * | 2002-06-01 | 2006-09-26 | Solid State System Co., Ltd. | Method for partitioning memory mass storage device |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5022077A (en) * | 1989-08-25 | 1991-06-04 | International Business Machines Corp. | Apparatus and method for preventing unauthorized access to BIOS in a personal computer system |
EP0602867A1 (en) * | 1992-12-17 | 1994-06-22 | NCR International, Inc. | An apparatus for securing a system platform |
JP2866376B2 (en) * | 1998-05-20 | 1999-03-08 | 株式会社日立製作所 | Disk array device |
JP2000112835A (en) * | 1998-10-01 | 2000-04-21 | Sony Corp | Memory device, data recording/reproducing device, and computer system |
US6763458B1 (en) * | 1999-09-27 | 2004-07-13 | Captaris, Inc. | System and method for installing and servicing an operating system in a computer or information appliance |
CN1340765A (en) * | 2000-08-29 | 2002-03-20 | 廖瑞民 | Method for dividing one hard disk into more partitions separated fully |
US6973517B1 (en) * | 2000-08-31 | 2005-12-06 | Hewlett-Packard Development Company, L.P. | Partition formation using microprocessors in a multiprocessor computer system |
JP3967073B2 (en) * | 2000-09-27 | 2007-08-29 | 株式会社東芝 | RAID controller |
US6636958B2 (en) * | 2001-07-17 | 2003-10-21 | International Business Machines Corporation | Appliance server with a drive partitioning scheme that accommodates application growth in size |
AU2002953325A0 (en) * | 2002-12-13 | 2003-01-09 | Executive Computing Holdings Pty Ltd | Means for providing protection for digital assets |
-
2002
- 2002-06-01 US US10/160,519 patent/US7114051B2/en not_active Expired - Lifetime
- 2002-08-02 KR KR10-2002-0045867A patent/KR100470413B1/en not_active IP Right Cessation
- 2002-08-05 JP JP2002227647A patent/JP2004030551A/en active Pending
-
2003
- 2003-05-19 TW TW092113430A patent/TWI282496B/en not_active IP Right Cessation
- 2003-05-27 CN CNB031383300A patent/CN100419713C/en not_active Expired - Fee Related
-
2005
- 2005-04-07 US US11/102,109 patent/US20050177698A1/en not_active Abandoned
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5974517A (en) * | 1996-09-17 | 1999-10-26 | Compaq Computer Corporation | Method and system for mounting a system partition as a logical drive while an operating system is operational by modifying a partition table |
US6400823B1 (en) * | 1996-12-13 | 2002-06-04 | Compaq Computer Corporation | Securely generating a computer system password by utilizing an external encryption algorithm |
US6532535B1 (en) * | 1998-02-24 | 2003-03-11 | Adaptec, Inc. | Method for managing primary and secondary storage devices in an intelligent backup and restoring system |
US6601152B1 (en) * | 1999-07-09 | 2003-07-29 | Fujitsu Limited | Storage apparatus, an access control apparatus for a recording medium and an access control method for a recording medium |
US6633962B1 (en) * | 2000-03-21 | 2003-10-14 | International Business Machines Corporation | Method, system, program, and data structures for restricting host access to a storage space |
US20020157027A1 (en) * | 2001-04-24 | 2002-10-24 | International Business Machines Corporation | Method and system for providing a trusted boot source in a partition |
US7069447B1 (en) * | 2001-05-11 | 2006-06-27 | Rodney Joe Corder | Apparatus and method for secure data storage |
US6647481B1 (en) * | 2002-01-31 | 2003-11-11 | Western Digital Ventures, Inc. | Method for accessing data storage locations having addresses within a hidden logical address range |
US7114051B2 (en) * | 2002-06-01 | 2006-09-26 | Solid State System Co., Ltd. | Method for partitioning memory mass storage device |
Cited By (48)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7925894B2 (en) | 2001-07-25 | 2011-04-12 | Seagate Technology Llc | System and method for delivering versatile security, digital rights management, and privacy services |
US20060174352A1 (en) * | 2001-07-25 | 2006-08-03 | Seagate Technology Llc | Method and apparatus for providing versatile services on storage devices |
US7545414B2 (en) * | 2005-02-08 | 2009-06-09 | Olympus Imaging Corp. | Image recording apparatus with memory partitioned and password protected for multiple users |
US20060176595A1 (en) * | 2005-02-08 | 2006-08-10 | Olympus Imaging Corp. | Image recording apparatus |
US20070180210A1 (en) * | 2006-01-31 | 2007-08-02 | Seagate Technology Llc | Storage device for providing flexible protected access for security applications |
US20070250710A1 (en) * | 2006-04-25 | 2007-10-25 | Seagate Technology Llc | Versatile secure and non-secure messaging |
US20090235109A1 (en) * | 2006-04-25 | 2009-09-17 | Seagate Technology Llc | Hybrid computer security clock |
US8429724B2 (en) | 2006-04-25 | 2013-04-23 | Seagate Technology Llc | Versatile access control system |
US8281178B2 (en) | 2006-04-25 | 2012-10-02 | Seagate Technology Llc | Hybrid computer security clock |
US8028166B2 (en) | 2006-04-25 | 2011-09-27 | Seagate Technology Llc | Versatile secure and non-secure messaging |
US20070250915A1 (en) * | 2006-04-25 | 2007-10-25 | Seagate Technology Llc | Versatile access control system |
US20080098166A1 (en) * | 2006-10-19 | 2008-04-24 | Sony Corporation | Data storage device and data controlling method |
US20080276065A1 (en) * | 2007-05-03 | 2008-11-06 | Samsung Electronics Co., Ltd. | Method of partitioning storage area of recording medium and recording medium using the method, and method of accessing recording medium and recording device using the method |
US20090106517A1 (en) * | 2007-10-23 | 2009-04-23 | Asustek Computer Inc. | Data protection method |
US8041913B2 (en) * | 2007-10-23 | 2011-10-18 | Asustek Computer Inc. | Data protection method |
KR100990973B1 (en) * | 2007-11-14 | 2010-11-19 | 한국전력공사 | Apparatus of processing data using raw area of removable storage device |
US20100287217A1 (en) * | 2009-04-08 | 2010-11-11 | Google Inc. | Host control of background garbage collection in a data storage device |
US8239713B2 (en) | 2009-04-08 | 2012-08-07 | Google Inc. | Data storage device with bad block scan command |
US20100262979A1 (en) * | 2009-04-08 | 2010-10-14 | Google Inc. | Circular command queues for communication between a host and a data storage device |
US20100262740A1 (en) * | 2009-04-08 | 2010-10-14 | Google Inc. | Multiple command queues having separate interrupts |
US20100262773A1 (en) * | 2009-04-08 | 2010-10-14 | Google Inc. | Data striping in a flash memory data storage device |
US20100262760A1 (en) * | 2009-04-08 | 2010-10-14 | Google Inc. | Command processor for a data storage device |
US20100262767A1 (en) * | 2009-04-08 | 2010-10-14 | Google Inc. | Data storage device |
US20100269015A1 (en) * | 2009-04-08 | 2010-10-21 | Google Inc. | Data storage device |
US20100262738A1 (en) * | 2009-04-08 | 2010-10-14 | Google Inc. | Command and interrupt grouping for a data storage device |
US20100262766A1 (en) * | 2009-04-08 | 2010-10-14 | Google Inc. | Garbage collection for failure prediction and repartitioning |
US20100262757A1 (en) * | 2009-04-08 | 2010-10-14 | Google Inc. | Data storage device |
US20100262761A1 (en) * | 2009-04-08 | 2010-10-14 | Google Inc. | Partitioning a flash memory data storage device |
US20100262894A1 (en) * | 2009-04-08 | 2010-10-14 | Google Inc. | Error correction for a data storage device |
US8205037B2 (en) | 2009-04-08 | 2012-06-19 | Google Inc. | Data storage device capable of recognizing and controlling multiple types of memory chips operating at different voltages |
US8239729B2 (en) | 2009-04-08 | 2012-08-07 | Google Inc. | Data storage device with copy command |
US20100262762A1 (en) * | 2009-04-08 | 2010-10-14 | Google Inc. | Raid configuration in a flash memory data storage device |
US8239724B2 (en) | 2009-04-08 | 2012-08-07 | Google Inc. | Error correction for a data storage device |
US8244962B2 (en) | 2009-04-08 | 2012-08-14 | Google Inc. | Command processor for a data storage device |
US8250271B2 (en) | 2009-04-08 | 2012-08-21 | Google Inc. | Command and interrupt grouping for a data storage device |
US20100262758A1 (en) * | 2009-04-08 | 2010-10-14 | Google Inc. | Data storage device |
US8327220B2 (en) | 2009-04-08 | 2012-12-04 | Google Inc. | Data storage device with verify on write command |
US8380909B2 (en) | 2009-04-08 | 2013-02-19 | Google Inc. | Multiple command queues having separate interrupts |
US20100262759A1 (en) * | 2009-04-08 | 2010-10-14 | Google Inc. | Data storage device |
US8433845B2 (en) | 2009-04-08 | 2013-04-30 | Google Inc. | Data storage device which serializes memory device ready/busy signals |
US8447918B2 (en) | 2009-04-08 | 2013-05-21 | Google Inc. | Garbage collection for failure prediction and repartitioning |
US8566508B2 (en) | 2009-04-08 | 2013-10-22 | Google Inc. | RAID configuration in a flash memory data storage device |
US8566507B2 (en) | 2009-04-08 | 2013-10-22 | Google Inc. | Data storage device capable of recognizing and controlling multiple types of memory chips |
US8578084B2 (en) | 2009-04-08 | 2013-11-05 | Google Inc. | Data storage device having multiple removable memory boards |
US8595572B2 (en) | 2009-04-08 | 2013-11-26 | Google Inc. | Data storage device with metadata command |
US8639871B2 (en) | 2009-04-08 | 2014-01-28 | Google Inc. | Partitioning a flash memory data storage device |
US9244842B2 (en) | 2009-04-08 | 2016-01-26 | Google Inc. | Data storage device with copy command |
US20140281322A1 (en) * | 2013-03-15 | 2014-09-18 | Silicon Graphics International Corp. | Temporal Hierarchical Tiered Data Storage |
Also Published As
Publication number | Publication date |
---|---|
KR20030093079A (en) | 2003-12-06 |
TW200307868A (en) | 2003-12-16 |
TWI282496B (en) | 2007-06-11 |
CN100419713C (en) | 2008-09-17 |
JP2004030551A (en) | 2004-01-29 |
US20030225960A1 (en) | 2003-12-04 |
US7114051B2 (en) | 2006-09-26 |
CN1461999A (en) | 2003-12-17 |
KR100470413B1 (en) | 2005-02-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7114051B2 (en) | Method for partitioning memory mass storage device | |
US7054990B1 (en) | External storage device using non-volatile semiconductor memory | |
US7539828B2 (en) | Method and system for automatically preserving persistent storage | |
US7039754B2 (en) | Detachably mounted removable data storage device | |
US8161226B2 (en) | Methods and apparatus to share a thread to reclaim memory space in a non-volatile memory file system | |
EP1960887B1 (en) | Method for flash-memory management | |
US8504763B2 (en) | Method and memory device that powers-up in a read-only mode and is switchable to a read/write mode | |
KR101376937B1 (en) | Describing and querying discrete regions of flash storage | |
US6999913B2 (en) | Emulated read-write disk drive using a protected medium | |
US8312247B2 (en) | Plural-partitioned type nonvolatile storage device and system | |
US20030046484A1 (en) | Flash management system for large page size | |
US7783854B2 (en) | System and method for expandable non-volatile storage devices | |
KR20040100849A (en) | Data storage device | |
US8380666B2 (en) | File management device and storage device for managing mapping information between a first file system and a second file system | |
CN101789019B (en) | Method for controlling removable disk under Windows | |
US6591356B2 (en) | Cluster buster | |
JP2007200314A (en) | Apparatus and method of managing hidden area | |
US20060136690A1 (en) | Storage device having independent storage areas and password protection method thereof | |
JP2005276158A (en) | Storage system, computer system and method of establishing attribute of storage area | |
US20030070035A1 (en) | Method for accessing data in a computer and the computer thereof | |
JP2000030375A (en) | Data processing system, access device, and recording media | |
CN107643987B (en) | Method for reducing DRAM (dynamic random Access memory) usage in solid state disk and solid state disk using same | |
JP2011076441A (en) | Information recording device, information recording method and information-recording program | |
US11922034B2 (en) | Dual mode storage device | |
US20080005449A1 (en) | Generalized flash memory and method thereof |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |