WO2003056432A1 - Dispositif de memoire et appareil d'enregistrement/reproduction faisant appel a ce dispositif - Google Patents
Dispositif de memoire et appareil d'enregistrement/reproduction faisant appel a ce dispositif Download PDFInfo
- Publication number
- WO2003056432A1 WO2003056432A1 PCT/JP2002/013257 JP0213257W WO03056432A1 WO 2003056432 A1 WO2003056432 A1 WO 2003056432A1 JP 0213257 W JP0213257 W JP 0213257W WO 03056432 A1 WO03056432 A1 WO 03056432A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- file
- data
- recorded
- entry
- directory
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
-
- 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/08—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers from or to individual record carriers, e.g. punched card, memory card, integrated circuit [IC] card or smart card
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
Definitions
- the present invention relates to a memory device having a recording medium in which data can be written only once in bit units, a recording / reproducing device using the memory device, Further, the present invention relates to a file management method for managing files recorded in a memory device.
- This type of memory device generally incorporates a nonvolatile semiconductor memory (IC memory) such as a flash memory, and stores various digital data such as still image data, moving image data, audio data, and music data in the semiconductor memory.
- IC memory nonvolatile semiconductor memory
- Flash memory is a rewritable memory that repeatedly writes and erases data. Therefore, a memory device with a built-in flash memory must use a file management system with a general hierarchical directory structure, such as MS-DOS (trademark) format, which is created on the assumption that rewritable disk media is used. Can be.
- MS-DOS trademark
- flash memory is a relatively expensive device. Therefore, write-once nonvolatile semiconductor memory such as PROM (Programmable Read Only Memory), which is provided at a lower price than flash memory, is used as a data storage device. By using them, the memory device can be manufactured at low cost.
- MS-DOS like a rewritable memory device using a flash memory
- a license type semiconductor memory As a data storage device, a license type semiconductor memory is used. A memory device cannot erase the substance of recorded data. From the viewpoint of user convenience, it is desirable that files and the like can be artificially deleted on the file management system.
- An object of the present invention is to provide a novel memory device which can solve the problems of the conventional memory device as described above, and a recording / reproducing device using the memory device.
- Another object of the present invention is to apply a physical configuration and a file management system compatible with a memory device using a rewritable recording medium to a recording medium on which data can be written only once in bit units.
- Another object of the present invention is to provide a memory device capable of erasing a file or the like on a file management system in a pseudo manner, and a recording / reproducing apparatus using the memory device.
- a memory device is a recording medium on which data can be written only once in bit units, and includes an entity data recording area in which entity data of a file is recorded, management data of the recorded file, and A recording medium having a spare area for recording the update data of the entity data is provided, and the spare area stores management data in the entity data record.
- the data is recorded in the direction opposite to the data recording direction of the recording area.
- the spare area is divided into pages, each of which is a predetermined data unit to which a management number is set, management data is recorded continuously from one of the upper and lower management numbers, and the update data is stored in the upper or lower management number Of these, the above management data is recorded continuously from the other side.
- the spare area includes, as management data, a file entry indicating a file recorded on the recording medium, a root entry indicating the highest directory in the debris directory structure, and a subdirectory in the hierarchical directory structure. Is recorded corresponding to each generated file, root directory and subdirectory, and the file entry indicates the name of the indicated file and the parent directory of the file. Information that specifies the root entry or sub-entry to be executed and information that specifies the recording location of the actual data of the file. The sub-entry contains the name of the sub-directory that is instructed and the sub-directory. A root entry or directory that points to the bird's parent directory. Information specifying the entry is included.
- a data recording area on the recording medium is replaced with an actual data recording area in which the actual data of the file is recorded.
- a spare area in which the recorded file management data and the update data of the entity data are recorded, and the management data is recorded in the entity data recording area for the spare area. Recording is performed in the direction opposite to the direction.
- the recording / reproducing apparatus is a recording medium on which data can be written only once in a bit unit, wherein an entity data recording area in which entity data of a file is recorded, management data of the recorded file, and A recording / reproducing unit that records and / or reproduces a file is provided for a memory device including a recording medium having a spare area in which update data of entity data is recorded.
- the recording / reproducing unit records management data in the spare area in a direction opposite to the data recording direction of the actual data recording area.
- FIG. 2 is a diagram showing a configuration of a memory cell of a memory card.
- FIG. 3 is a perspective view of the memory card viewed from the front side.
- FIG. 4 is a perspective view of the memory card viewed from the back side.
- FIG. 5 is a diagram for explaining a terminal structure of the memory card.
- FIG. 6 is a block diagram showing an internal circuit of the memory card.
- FIG. 7 is a diagram for explaining the interface configuration of the memory card.
- FIG. 8 shows the relationship between segments and blocks defined on the physical format of the memory card and the relationship between the physical block number and the logical address.
- C Fig. 9 shows the relationship between the physical format of the memory card and c .
- FIG. 3 is a diagram for explaining a boot area and a user area defined in FIG.
- FIG. 10 is a diagram for explaining pages defined on the physical format of the memory card.
- FIG. 11 is a diagram for explaining the spare block management number defined on the logical format of the memory card.
- FIG. 12 is a diagram for explaining an entry defined on the logical format of the memory card.
- FIGS. 13A to 13F are diagrams for explaining field images for each type of entry page.
- FIG. 14 is a diagram illustrating an example of a directory configuration of files and the like recorded on a memory card.
- FIG. 15 is a diagram showing a recorded image of an entry page when a file is recorded in the directory configuration shown in FIG.
- FIG. 16 is a diagram showing a directory configuration after an arbitrary file is deleted from the files having the directory configuration shown in FIG.
- FIG. 17 is a diagram showing a recorded image of the entry page when the file shown in FIG. 16 is deleted.
- FIG. 18 is a flowchart showing the processing order of the session closing processing.
- FIG. 19 is a diagram showing a directory structure of a file recorded in the memory card at the time of the first session closing process.
- FIG. 20 is a diagram showing a record image of the entry page after the first session closing process.
- FIG. 21 is a diagram showing a recording image of the data recording area after the first session closing process.
- FIG. 22 is a diagram showing a directory configuration of a file recorded in the small IC memory at the time of the second session closing process.
- FIG. 23 is a diagram showing a record image of the entry page after the second session closing process.
- FIG. 24 is a diagram showing a recording image of the data recording area after the second session closing process.
- FIG. 25 is a diagram showing a directory configuration of a file recorded in the small IC memory at the time of the third session closing process.
- FIG. 26 is a diagram showing a record image of the entry page after the third session closing process.
- FIG. 27 is a diagram showing a recording image of the data recording area after the third session closing process.
- BEST MODE FOR CARRYING OUT THE INVENTION an example in which the memory device according to the present invention is applied to a memory card which is a card-shaped small IC memory device will be described. Further, the present invention will be described using this memory card as an external storage medium. An example in which the present invention is applied to a data processing device to be used will be described.
- Examples of the data processing device in which the memory card to which the present invention is applied is used as an external storage medium include an information portable terminal, a desktop computer, and a notebook computer. Data, mobile phones, audio devices, home appliances, and the like.
- a data processing device using a memory card to which the present invention is applied is referred to as a host device.
- the memory card 1 includes a nonvolatile memory to which data can be written only once, that is, a write-once type semi-memory (hereinafter referred to as a write-once memory). It is built-in. As shown in FIG. 1, the memory card 1 is used in a state where it is inserted into a slot 3 provided in a host device 2. The user can freely insert and remove the memory card 1 from the insertion slot 3. Therefore, the memory card 1 inserted in one host device can be extracted and inserted in another host device. In other words, the memory device 1 can be used for exchanging data between different host devices.
- a write-once type semi-memory hereinafter referred to as a write-once memory
- the write-once memory provided inside the memory card 1 is a PROM (Programmable Read Only Memory) using a memory cell such as a diode burst type that can write data in 1-bit units. It is.
- the diode breakdown type memory cell includes Pn diodes D1 and D2 connected in series in a direction opposite to each other and between a line and a column.
- the bit retention value is inverted by breaking one pn diode with a reverse bias.
- the write-once memory applied to the memory card 1 is not limited to the diode destruction type, but may be a so-called fuse type or floating gate type PROM.
- the bit value held in each memory cell is "1" (High) in an initial state. That is, “1” is read from each memory cell when no data is written.
- "0" (Low) is written to the memory cell in the initial state
- the pn diode is destroyed and the value held in the memory cell changes to "0".
- the held value of the memory cell becomes "0” and "1” or "0” is written to the memory cell thereafter, the held value does not change and the state of "0" is maintained.
- the value held in that memory cell remains at "1".
- a conventionally proposed and used memory card uses a nonvolatile semiconductor memory called a flash memory, which can be rewritten a plurality of times, to store data.
- a flash memory Built-in as a device.
- the memory card 1 according to the present invention is formed so as to be compatible with a conventional memory card using a flash memory in an outer diameter shape, a connection terminal, a data transfer interface with a host device, and the like.
- the memory card 1 according to the present invention can be used by mounting it on a host device using a conventional memory card using a flash memory.
- the host device 2 that can use the memory card 1 according to the present invention can use a conventional memory card using a flash memory as an external storage medium. That is, the memory card according to the present invention has interface compatibility with a conventional memory card using a flash memory.
- the memory card according to the present invention will be described in detail while appropriately comparing with a conventional memory card using a flash memory.
- the conventional memory card using the flash memory and the memory card according to the present invention the conventional memory card using the flash memory and the host corresponding to the same are used.
- the host device may be referred to as Ver1
- the memory card according to the present invention and the host device corresponding thereto may be referred to as Ver2.
- a memory card 1 is formed in a substantially rectangular thin plate shape, has a longitudinal length of 5 O mm, a width of 21.4 mm, The thickness Di is set to 2.8 mm.
- the memory card 1 has one surface as a front surface 1a and the other surface as a back surface 1b.
- a connection terminal group 4 as 10 plane electrodes is provided on the back surface lb side of one end side of the memory card 1 in the longitudinal direction.
- the electrodes constituting the connection terminal group 4 are provided in parallel in the width direction of the memory card 1.
- a partition piece 5 rising vertically from the back surface 1b is provided between each of the electrodes.
- Each partition piece 5 has a connection terminal connected to each electrode. This is to prevent contact with the electrode.
- a slide switch 6 for preventing erroneous erasure is provided at the center of one end of the back surface 1 b of the memory card 1.
- the host device 2 to which the above-mentioned memory card 1 is attached is provided with a slot 3 for inserting and removing the memory card 1.
- the removal slot 3 is formed as an opening corresponding to the width and thickness of the memory card 1 on the front side of the host device 2 as shown in FIG.
- the memory card 1 inserted into the host device 2 via the slot 3 is held in the host device 2 by connecting the connection terminals of the host device 2 to each electrode constituting the connection terminal group 4 Is prevented from falling off.
- the connection terminal on the host device 2 side has 10 contacts corresponding to the electrodes constituting the connection terminal group 4 provided on the memory card 1 to be mounted.
- the memory card 1 according to the present invention is inserted into the host device 2 through the slot 3 with one end provided with the connection terminal group 4 as an insertion end and the direction of arrow X1 in FIG. .
- each electrode constituting the connection terminal group 4 is connected to each contact of the connection terminal on the host device 2 side, so that signals can be transmitted and received.
- the first terminal 4a constituting the connection terminal group 4 is a V SS terminal to which V SS (reference 0 volt voltage) is connected.
- the first terminal 4a serving as the VSS terminal connects the ground of the host device 2 and the ground of the memory card 1 so that the 0-volt reference potential of the host device 2 and that of the memory card 1 match.
- the second terminal 4 b forms a BS terminal, and a bus state signal is input from the host device 2 to the memory card 1.
- the third terminal 4 c constitutes a V CC terminal, and the power supply voltage (V CC) is supplied from the host device 2 to the memory card 1.
- the operable power supply voltage of the memory card 1 is 2.73.6 volts, and a voltage in this range is supplied.
- the fourth terminal 4d forms an SDIO terminal, and receives and inputs a serial data signal transferred between the memory card 1 and the host device 2.
- the fifth terminal 4e is a spare terminal and has no particular function assigned.
- the sixth terminal 4 f constitutes an INS terminal, and is used for insertion / removal detection for the host device 2 to determine whether the memory card 1 is inserted into the slot 3.
- the seventh terminal 4 g is a spare terminal and no function is assigned to it.
- the terminal 4h of 8 constitutes the SCLK terminal, and the master signal of serial data transferred between the memory card 1 and the host device 2 is input from the host device to the memory card. .
- the ninth terminal 4i constitutes a VCC terminal, and a power supply voltage (VCC) is supplied from the host device to the memory card.
- VCC power supply voltage
- the ninth terminal 4 i is connected to the third terminal 4 c inside the memory card 1.
- the 10th terminal 4 j is used as a VSS terminal, connects the ground of the host device 2 and the ground of the memory card 1, and matches the 0 volt reference potential between the host device 2 and the memory card 1 .
- the tenth terminal 4 j is connected inside the memory card 1 to a first terminal 4 a also used as a VSS terminal.
- the configuration of the terminals of the memory card 1 according to the present invention, the shape of the handheld device 3 (Ver 2) of the host device 2 to which the memory card 1 is mounted, and the configuration of the connection terminals use flash memory. It has the same configuration as the conventional memory card (Ver1) configuration and the host device using the conventional memory card, and has mutual mechanical compatibility.
- the memory card 1 includes an interface circuit (I / F) 12, a register circuit 13, a data buffer circuit 14, a £ ⁇ (circuit 15), a memory I / F sequence circuit 16, write-once memory 17, and oscillation control circuit 18.
- I / F interface circuit
- register circuit 13 register circuit 13
- data buffer circuit 14 data buffer circuit 14
- £ ⁇ circuit 15
- memory I / F sequence circuit 16 write-once memory 17, and oscillation control circuit 18.
- the I / F circuit 12 is a circuit that transfers data with the host device 2 using a three-wire half-duplex serial protocol.
- the register circuit 13 includes, for example, a command transferred from the host device, an internal state in the memory card 1, an address of data to be accessed, and a command when executing the command. This is a circuit for storing necessary parameters, file management information in the write-once memory 17, and the like. The information stored in the register circuit 13 is accessed from the memory I / F sequence circuit 16 or by giving a predetermined command from the host device 2.
- the data buffer circuit 14 is a memory circuit for temporarily storing data to be written to the write-once memory 17 and data read from the write-once memory 17.
- the data buffer circuit 14 has a data capacity of a predetermined data writing unit (512 bytes, which is a page size described later).
- the ECC circuit 15 adds an error correction code (ECC) to the data written to the write-once memory 17.
- ECC error correction code
- the ECC circuit 15 performs an error correction process on the read data based on the error correction code added to the data read from the write-once memory 17. For example, an error correction code is added for 3 bytes to a data unit of 512 bytes.
- the memory I / F sequence circuit 1.6 controls the exchange of data between the data buffer 14 and the write-once memory 17 according to the commands and various information stored in the register circuit 13.
- the write-once memory 17 is a semiconductor memory capable of rewriting the stored data content only once.
- the oscillation control circuit 18 generates an operation clock in the memory card 1.
- the memory card 1 configured as described above, for example, writes data, reads data, and deletes data (deletion on the file system) in accordance with various commands given from the host device 2 via the interface. Perform the operation.
- FIG. 7 shows a functional configuration diagram of an interface for performing data transmission between the memory card 1 and the host device 2 according to the present invention.
- the host device 2 includes a file manager 31, a TPC interface 32, and a serial interface 33.
- the memory card 1 has a serial interface 35, a register 37, a data buffer 38, and a memory controller 3. 9 and a memory 40.
- the file manager 31 manages files stored in the memory card 1 and files stored in other media of the host device on the operation system of the host device.
- the TPC interface 32 is a lower layer of the file manager 31.
- the TPC interface 32 accesses the register 37 and the data buffer 38 in the memory card 1 by using a command (TPC: Transfer Protocol Command) specific to the interface of the memory card 1.
- TPC Transfer Protocol Command
- the serial interfaces 33 and 35 are the lower layer of the TPC interface and are the physical layer of this interface system.
- the serial interfaces 33 and 35 transfer data according to a three-wire half-duplex serial protocol that transfers three signals of 1-bit serial data, a clock signal, and a bus state signal.
- the register 37 stores the command transferred from the host, the internal state of the memory card, the data address of the memory, various processing parameters required for executing the command, file management information in the memory, and the like.
- the data buffer 38 is a buffer area for temporarily storing data written to the memory 40 and data read from the memory 40.
- the memory controller 39 controls data exchange between the data buffer 38 and the memory 40 in accordance with commands and various information stored in the register circuit 13 to read and write data. I do.
- the memory 40 is a memory area for data, and is virtualized as a unique model through the memory controller 39.
- the host device 2 and the memory card 1 having the above configuration transfer data stored in another medium managed by the file manager 31 to the memory 40 via the serial interface. Can be.
- the data stored in the memory 40 can be transferred to another medium managed by the file manager via the serial interface.
- the data capacity that the memory card 1 can store is, for example, 16 Mbytes, 32 Mbytes, 64 Mbytes, and 128 Mbytes.
- a data unit called a block is defined, and the data storage area is physically ⁇ ? Based on the block. Is being managed.
- the data size of one block is, for example, 16 bytes. Therefore, if the memory card is 16 bytes, the total number of blocks is 10 24, and if the memory card is 32 bytes, the total number of blocks is 208, and the memory block is 64 bytes. In the case of a memory card, the total number of blocks is 4096, and in the case of a 128-byte memory card, the total number of blocks is 8192.
- This block is the same as the erase block in a conventional memory card using flash memory.
- Blocks have a valid block and a spare block.
- An effective block is a block in which the actual data of a file and the like are recorded.
- the spare block is an area where replacement data of late failure and data for file management are recorded.
- the total number of spare blocks in one memory card 1 is, for example, 31 for a 16-Mbyte memory card, 63 for a 32-byte memory card, and 64 for a 64-byte memory card.
- the number of memory cards is 127, and the number of memory cards of 128 Mbytes is 255.
- Each block has a physical block number that specifies the storage location of the block. This physical block number is set as a consecutive number from 0, regardless of the distinction between a valid block and a spare block.
- Each block records a logical address.
- This logical address is written to a predetermined area in the block. For example, a logical address is recorded in advance in a valid block at the time of factory shipment, and a logical address is not recorded in a spare block at the time of factory shipment. If a block failure occurs at a specific logical address block, a replacement is performed by writing the logical address of the defective block to an unrecorded spare block. In other words, for the effective block, along with the physical block number The logical address is also set in advance, and for the spare block, the logical address is set after shipment from the factory.
- the c- segment number which defines a group of 512 blocks as a segment, is set as a continuous number from 0.
- Each segment consists of a valid block and a spare block.
- the number of valid blocks in the 0 segment is 495, and the number of spare blocks is 15.
- the number of effective blocks in the other segments is 496, and the number of spare blocks is 16. Note that the number of effective blocks and the number of spare blocks in the 0 segment are small because there is a boot block described later.
- FIG. 8 shows the relationship between the segment and the block described above and the relationship between the physical block number and the logical address.
- the two blocks at the beginning of the 0 segment are booted.
- the boot area is an area that first reads data when the host device boots the memory card 1.
- information, attributes, and the like regarding the memory card are recorded.
- the area where this boot is recorded is called a boot area, and the other area is called a user area.
- each block is composed of 32 pages.
- the page is a unit composed of a data area of 512 bytes and an extra data area.
- the substance of the data is recorded. That is, file entity data, management data, and the like are recorded.
- the extra data area has a 1-byte (8-bit) overwrite flag area, a 1-byte management flag area, a 2-byte logical address area, and a 5-byte format-reserve area.
- a first ECC area and a second ECC area are formed in order from the top.
- the block status is recorded in the first bit, the page status in the second and third bits, the update status in the fourth bit, and the data use status in the fifth bit.
- the 6th to 8th bits are reserved areas.
- the block status indicates that the block containing the page is in a bad state Or a 1-bit identification flag indicating whether the data recorded in the block containing the page has been deleted. When the value of the block status is "0", it indicates that the block is in the bad block state or the data deleted state, and when the value is "1", it indicates that the block is accessible. I have.
- This block status is "1" in the initial state such as at the time of factory shipment.
- the block status is rewritten to "0" when the block is defective or when the data written in the block is pseudo-erased on the file management system.
- Page status is a 2-bit identification flag that indicates the state of occurrence of an uncorrectable error for each page.
- the page status is "0 0"
- the data in the page has an error that can be corrected by ECC
- the value is "0 1”
- the data in the page has ECC. Indicates that an error that cannot be corrected has occurred.
- the value is "1 1”
- the update status is a 1-bit flag indicating the update status of the block containing the page.
- the update status is "0", it indicates that data has been recorded in the block or the data is being updated in the block, and when the value is "1", This indicates a state in which no data has been recorded in that block.
- the data usage status is a 1-bit identification flag indicating that data has been recorded for the block containing the page and the block has already been used. When the data usage status is "0", it indicates that data has already been recorded for the topic. When the value is "1”, the data usage status is not yet available for the page. Indicates that no data has been recorded.
- the management flag includes a system bit indicating whether the block containing the page is a boot block, a block other than the block, a copy restriction bit for the page, an access restriction bit for the page, and the like. Have been.
- As the logical address address information of the block is recorded.
- the first ECC is a one-byte management flag, a two-byte logical address, and an error correction code for a five-byte format reserve.
- the second ECC is an error correction code for 512-byte page data.
- the physical format of the memory card 1 according to the present invention has the above configuration.
- the physical format of the memory card 1 is the same as the physical format of a conventional memory card that can be rewritten a plurality of times using a flash memory.
- the difference is that the data use status is defined in the physical format of the memory card 1 according to the above.
- the fifth bit in the overwrite flag area is the data use status, but in the conventional memory card that can be rewritten multiple times using flash memory, the overwrite flag area The 5th bit is reserved.
- the memory card 1 since the memory card 1 according to the present invention defines the data use status and the block status in the physical format as described above, data is not yet recorded in the block, and data is recorded in the block. It is possible to distinguish between three states: the state in which the data recorded in the block has been erased, and the state in which the data recorded in the block has been deleted. Therefore, even in the case of the write-once type memory card 1, the data erasure state can be managed in a pseudo manner on the file management system.
- a new data use status flag is defined in the reserved area of the conventional memory card that can record multiple times using flash memory, so that data read compatibility on physical format may be possible. it can. That is, the contents of the data use status specified only for the memory card 1 do not affect the conventional memory card.
- the information recorded in the extra data area in the page includes information indicating unique contents for each block and information indicating unique contents for each page.
- the block status, update status, data use status, and logical address are information indicating specific contents for each block.
- the page status and the management flag are information indicating contents unique to each page.
- Block status, update status The status, data use status, and logical address have the same information content for all pages in the same block. Therefore, such information may be recorded only for the 'first' page in the block.
- the memory card 1 does not have an area for recording a table for associating a physical block number with a logical address in the physical format. Therefore, when booting the memory card 1, the host device detects the logical address by accessing the first page of all blocks, and creates a table for associating the physical block number with the logical address.
- a conventional memory card using a flash memory that can be written multiple times employs an MS-DOS compatible format as a logical format.
- the MS-DOS compatible format is a file system that manages data files recorded on a recording medium in a hierarchical directory structure.
- a unit for recording and reproducing data (cluster) on a recording medium is defined when managing recorded data.
- a data recording / reproducing unit (cluster) specified by MS-DOS is a block unit.
- the write-once type memory card 1 has a unique logical format (hereinafter referred to as a write-once format) different from the MS-DOS compatible format, and an MS-DOS compatible format.
- the management of the finale will be carried out by both parties.
- the license format manages files in a hierarchical directory structure, similar to the MS_DSS compatible format.
- the host device (Ver 2) 2 according to the present invention which has enabled the use of the memory card 1 according to the present invention, records and reproduces data with respect to the memory card 1 according to the light-in format.
- a conventional host device (Ver 1) configured for the purpose of using a conventional memory card transmits data to the memory card 1 using an MS-DOS compatible format. Perform recording and playback.
- data is recorded by a host device (Ver 2) corresponding to the memory card 1, and in the MS-DOS compatible format, Do not manage data.
- the memory card 1 can perform the session closing process a plurality of times.
- a file can be added or updated in a write-once format after the session close processing has been performed L times, and the added or updated file can be updated by performing the session close processing again.
- the data can be read by a device (Ver 1) that supports this type of memory card.
- the actual data of a file is recorded in a block to which a logical address is assigned in advance, that is, an effective block.
- the actual data of the file is recorded in block units. That is, entity data of a plurality of files is recorded so as not to be mixed in one block.
- recording of file entity data starts from the first page of the block.
- the write-once format when the entity data of one file is recorded over a plurality of blocks, it is recorded in blocks of consecutive logical addresses.
- the continuous direction of the logical address is the forward direction, that is, the direction from a small value to a large value.
- each area divided into two is formed by a block in which logical addresses are continuous.
- management data called an entry page is a block to which a logical address is not allocated in advance (a block in which the value of a logical address is an initial value (OxFFFF)), that is, Record in spare block.
- OxFFFF initial value
- one entry file is created or updated, or one entry directory is created every time a root directory and a subdirectory are created. Record in block.
- the entry page has a capacity of one page. Therefore, each time a file, root directory, and sub-directory are created or updated, one page of the spare block is consumed.
- a spare block management number is set for all pages of all spare blocks. Since the number of pages in one block is 32, the total number of pages to which the spare block management number is set is 992 for a 16 Mbyte memory card, and 32 Mbytes of memory. If it is a card, it will be 204, if it is a 64 Mbyte memory card, it will be 406, and if it is a 128 Mbyte memory card, it will be 816.
- the spare block management number is calculated from the spare block with the lowest physical block number (ie, the spare block with the largest physical block number) out of all the spare blocks.
- the numbers are assigned sequentially in the direction of the spare block. For example, in the case of a 128 MB memory card 1, a spare block management number is set as follows. Spare block management number Segment number Physical block number Page number
- the entry page is recorded in the order according to the above-mentioned spare block management number. In other words, the entry page is recorded from the last spare block in the memory card 1 in the direction opposite to the recording direction of the normal entity data.
- the entry page is recorded in the spare block in which the late defective replacement data specified in the physical format is recorded. For this reason, the alternative data and entry page are recorded in the same area.Although the alternative data is specified in the physical format, it is recorded in the order according to the physical block number. The entry page is recorded in the reverse order of the physical block number. Therefore, the replacement data and the entry page are not recorded in the same physical location, and the backup block can be used effectively.
- Entry pages are classified into five types: file entries, root entries, sup- entries, session anchors, and directory markers.
- the file entry is management data indicating a file recorded on the memory card 1.
- one file entry is recorded in the spare block corresponding to that file.
- the parent pointer is a backup block management number in which the root entry or subentry, which is the entry pointing to the parent directory of the file, is recorded.
- the fragment is information indicating that the actual data of the file is recorded in two parts without being recorded in the continuous area. This fragment also indicates the start address of the subsequent recording area.
- the root entry is management data indicating the root directory.
- the root directory is the highest directory in the hierarchical directory structure.
- file management is performed in a hierarchical directory structure, only one root directory exists, and its existence does not change. Therefore, in the write-once type memory card 1, it is desirable to record one root entry in advance on the first page of the spare block management number at the time of factory shipment or the like.
- the sub-entry is management data indicating the sub-directory.
- a subdirectory is a directory other than the root directory in a hierarchical directory structure. Subdirectories can be located under the root directory or Directory. When one subdirectory is created on the memory card 1, one subdirectory is recorded in the auxiliary block corresponding to the subdirectory.
- the sub-entry describes the name of the sub-directory pointed to by the sub-entry, the date on which the sub-directory was created, and information identifying the parent directory of the sub-directory. .
- the session anchor is management data indicating that the session close processing has been performed.
- the session anchor indicates that the session close process was performed once in two pairs.
- the session close process starts, one session anchor is recorded in the spare block first, and one session anchor is recorded again in the spare block at the end of the session close process.
- information on the number of times the session close processing has been performed on the memory card 1 is described. Since the same value is recorded as the number information in the pair, the pair can be determined when the file entry is read. If the session force is recorded at the start and end of the session close process in this way, for example, if the power is turned off during the session close process and the session close fails, only one session anchor is recorded. It is possible to recognize later that the session close has failed.
- the directory marker indicates the recording position of a subdirectory entry, which is management data in MS-DS compatible format generated by performing the session closing process. This directory marker is recorded after recording the first session anchor and before recording the second session anchor when the session close processing is performed. That is, it is recorded on the page sandwiched between the paired session anchors. One directory marker is recorded for each subdirectory entry newly recorded during the session close process. However, when a subdirectory entry is recorded over a plurality of blocks, the directory marker for that block is recorded for one subdirectory entry.
- the entry page is recorded in a 152-byte data area in the page as shown in FIG.
- the description field in the entry page consists of a name field, a file attribute field, a type field, a head block pointer field, a data size field, a generation date field, a parent pointer field, a fragment field, and a spare field.
- the name field is located at the 0th to 10th bytes. If the entry page is a file entry or sub-entry, this name field describes the name of the file or sub-directory indicated by the entry page. When describing the names of files and subdirectories, they are recorded using character strings that can be used in the MS-DOS format.
- file name is a linguistic file name specified in the MS-DOS compatible format, "0" is described in the first byte of this name field, and the file name is written in the next two bytes. The data length is described, and the file name is described in the spare field. If the entry page is a root entry or directory dimmer, this name field is left blank.
- a pair identification ID indicating the number of times the memory card 1 has been subjected to session close processing is recorded in the first 0 to 1 bytes in this name field. .
- the pair identification ID is incremented from 1 to 2 to 3 in accordance with the number of times the session close process is performed on the memory card 1.
- the maximum value of the number of session close processing is 8, and only up to 8 IDs for pair identification are described. Note that even if the number of session close processes is less than 8, if there is no more space to be added to the memory card 1 itself, the pair identification ID is 256 (0XFFFF).
- the attribute field is placed in the 11th byte. If the entry page is a file entry, this attribute field describes the attribute of the file indicated by the file entry.
- the attribute field contains "0” if the file is a regular file, "1” if it is a read-only file, "2” if it is a hidden file, and "2" if it is a volume label. "3” is described.
- the attribute field is blank if the entry page is not a file entry.
- the type field is located at the 12th byte. In this type field, the type of the entry page is described. That is, information for distinguishing whether the entry page is a file entry force, a root entry force-, a sub-entry session anchor, or a directory marker is described.
- the type field contains “0” for a file entry, “1” for a root entry, “2” for a subentry, and “3” for a session entry. If it is a directory lianka, "4" is described.
- the first block pointer field is located at the 13th to 14th bytes. If the entry page is a file entry, the logical address of the first block in which the actual data of the file is stored is described in the first block pointer field. If the entry page is a root entry, the logical address of the block storing the root directory entry of the MS-DOS compatible format is described. Blank if the entry page is a sub-entry or session ancestor. If the entry page is a directory marker, the logical address of the block indicated by the directory power is described.
- the data size field is located at the 15th to 18th bytes. If the entry page is a file entry, the size of the entity data of the file indicated by the file entry is described in this data size field in byte order. In this data size field, if the entry page is a directory immersive, the 0th and 1st bytes describe the first entry among the entries recorded in the block indicated by the directory marker. In the second and third bytes, the last entry among the entries described in the block is described.
- the generation date field is placed in the 19th to 22nd bytes. If the entry page is a file entry, root entry or sub-entry, the creation time field describes the date when the file or directory was created. The description of the generation date is the same as the MS-DOS format. Entry page is in session In the case of anchor or directory power, this generation date feed will be blank.
- the parent pointer field is located at bytes 23 and 24.
- the parent pointer field describes the parent pointer if the entry page is a file entry or sub-entry.
- the parent pointer is the spare block spin number of the root entry or sub-entry pointing to the parent directory. If the entry page is a root entry, this parent pointer describes the spare block management number of its own entry.
- the fragment field is located at bytes 25 to 28.
- the fragment field contains information only if the entry page is a file entry.
- the actual data of the file is basically stored in a continuous logical address, but may be divided into two areas in exceptional cases.
- a flag indicating that the actual data of such a file is divided into two areas is described. Specifically, in the fragment field, if the actual data of the file is divided, 0 out of 4 bytes, 0 (0x0000) is described in the first byte, and the fragmentation is performed. Otherwise, other values are described in the 0th and 1st bytes.
- the logical address of the first block in which the latter half is recorded is described in the second and third bytes.
- Figures 13A to 13F show image diagrams for each entry page type.
- Figure 13A is a diagram of the fileentry.
- Fig. 13B is an image diagram of the file entry when the name of the long chain is long.
- Figure 13 (C) is an image of the root entry.
- FIG. 13D is an image diagram of a subentry.
- Figure 13E is an image diagram of the session anchor.
- Figure 13F is an image diagram of Directrianka.
- Fig. 14 shows an example of the hierarchical directory structure of the files recorded on the memory card 1, and an image of the entry page when a file with such a hierarchical directory structure is recorded on the memory card 1. See Figure 15 for an illustration. Arrows shown in Fig. 15 indicate the destinations of parent parenters described in each file entry and sub-entry. Indicates the destination.
- the write-once format used for the memory card 1 stores a root entry, a sub-entry, and a file entry in correspondence with the generated file and directory, thereby hierarchically storing the file. It can be managed in a directory structure. That is, when the memory card 1 is booted, the host device first reads all entry pages in order from the page whose spare block management number is 0. By reading all entry pages, the value of the parent pointer described in each file entry and sub-entry is detected. When the parent pointer is detected in this way, the parent-child relationship between the file and the directory recorded on the memory card 1 can be managed.
- the file entry describes the file name and file storage location information. Therefore, the host device can read the actual data of the file by referring to the file entry.
- MS—DOS compatible formats include MBR (Master Boot Record), PBR (Partition Boot Record), and FA as file management data other than entity data. There is a T (File Allocation Table), a root directory entry, and a subdirectory entry.
- the MBR is information placed at the top of the user area, and describes boot information for each partition.
- the PBR is information that is arranged in the first sector of a partition, and describes information on various processes related to each partition.
- the FAT records the connected state of clusters (blocks) handled in the user area. In this memory card 1, two FATs (FAT1, FAT2) are recorded for backup.
- the root directory entry describes the entries of each file and subdirectory located in the root directory.
- the subdirectory entry describes each file and subdirectory entry that is located in the subdirectory.
- One entry consists of two bytes, in which the file name, attribute, recording date, starting cluster (block) number, and file size (in bytes) are described.
- the MS-DOS compatible format stipulates that these management data be recorded in clusters to which logical addresses are assigned.
- the cluster is a block in the memory card 1 according to the present invention.
- the session closing process refers to the contents of the management data recorded in the license format and converts the above-mentioned MS-DOS compatible format management data to a block to which a logical address is assigned. This is a process that enables read compatibility with devices compatible with conventional memory cards by additionally recording.
- the logical address of the PBR is described in the MBR, it is not necessary to rewrite as long as the logical address of the PBR does not change.
- PBR, FAT, root directory, and subdirectory entries need to be rewritten as additional files and directory structures are added. Therefore, in the session closing process, the PBR, FAT, root directory entry, and subdirectory entry excluding the MBR are generated and recorded.
- step SI the host device 2 writes the first session anchor in the backup block management number following the last recorded entry page.
- the host device 2 describes the pair identification ID in the name field of the first session anchor.
- this pair identification ID a number indicating the number of times the session close process has been performed on the memory card 1 is described. For example, “1" is described for the first session close process, and "2" for the second session close process.
- step S2 the host device generates PBR and FAT corresponding to the current file management status based on the write-once format management data, and stores the generated PBR and FAT in the memory card 1. To record.
- connection order may be generated by analyzing the file E emissions birds in Rye DOO-once format, route entry, the service Buentori and directory Torimaka c This is because in the write-once format, the entity data that constitutes one file is basically recorded in a block of logical addresses that have been kneaded, and if the entity data is divided into two, This is because it is specified that the logical address of the latter part is described by the fragment of the file entry.
- the host device records the PBR and the FAT in an effective block, which is a block to which a logical address has been allocated in advance. Blocks PBR and F AT is recorded, c
- This Proc described in the MB R for example a logical address is one, 2 of Proc. That is, the host device records PBR and FAT for the block of the logical address indicated in the MBR at the time of the first session closing process.
- the host device records the PBR and FAT in a spare block, which is a block to which no logical address has been allocated in advance.
- the PBR and FAT are recorded in the spare block in the 0 segment.
- the host device 2 uses the block One task is set to "0", and the logical address is also recorded.
- the logical address value is the same as the logical address of the block in which the original PBR and FAT recorded during the previous session close process were recorded.
- the host device 2 sets the block status of the block in which the original PBR and FAT recorded in the previous session closing processing to "0".
- the host device 2 updates the logical address-physical block number conversion table stored therein.
- step S3 the host device generates a root directory entry and a subdirectory entry corresponding to the current file management status based on the write-once format management data, and generates the generated root directory. Record directory entries and subdirectory entries.
- the host device 2 records a root directory entry and a subdirectory entry in an effective block, which is a block to which a logical address has been allocated in advance.
- the block in which the directory entry is recorded is described in the PBR. Therefore, the host device 2 records the root directory entry for the block of the logical address indicated in the PBR at the time of the first session closing process.
- the host device 2 records the subdirectory entry in the effective block of the first segment and thereafter, while the host device 2 is a block in which the logical address is not allocated in advance during the second and subsequent session close processing. Record the root directory entry and subdirectory entries in the block.
- the host device 2 records the root directory entry in the spare block of the 0 segment in this spare block.
- the root directory entry is recorded so that the spare area is erased from the area opposite to the write-once format management data (entry page).
- the host device 2 records the sub-directory entry in the spare block of one or more segments among the spare blocks.
- the subdirectory entry created for the first time that is, the subdirectory newly created after the previous session close process, will have its subdirectory entry discussed.
- the address is recorded in an effective block, which is a block allocated in advance. This place In each case, it is recorded in the effective block after the first segment.
- the host device 2 sets the block use status of the block to "0" and records the logical address.
- the value of the logical address to be recorded shall be the same value as the logical address of the block in which the original root directory entry or sub-directory entry recorded during the previous session close processing was recorded.
- the host device 2 uses the original root directory entry or subdirectory entry recorded in the previous session closing process. Set the block status of the recorded block to "0".
- the host device 2 updates the logical address / physical block number conversion table stored therein.
- step S4 when adding or updating a subdirectory entry, the host device 2 records a directory marker for the added or updated subdirectory in step S1. Write to the backup block following the set session anchor.
- the data size of each entry constituting the root directory and sub-directory is 4 bytes (32 bits).
- the number of files and sub-directories under the root directory (that is, the number of entries) is specified to be up to 512, so the actual data capacity of the root directory entry is specified. Is at most one block (5 12 bytes x 32 pages). That is, the root directory entry always fits within one block.
- the number of files and subdirectories under the control of a subdirectory is not specified in the MS-DOS compatible format. Therefore, the size of the subdirectory entry entity data may exceed one block. In such a case, the subdirectory entry will be recorded over multiple blocks.
- the host device 2 When a subdirectory entry is recorded over a plurality of blocks, the host device 2 records a plurality of directory markers for one subdirectory. Specifically, the number of entries in the subdirectory is up to 5 12 (for one block) In the case of, one directory marker describes the logical address of the block in which the entity data of the subdirectory entry is described. If the number of entries in the subdirectory exceeds 5 12, a directory power is created for each block, and the range of the entry indicated in the block is indicated and identified.
- the page status of the page containing the directory marker recorded during the previous session closing process is set to "0" and erased.
- step S5 the host device 2 continues the directory immersion force if the directory immersion force was recorded in step S4, and if not, in step S4.
- step S1 a second session anchor is recorded.
- the host device describes the same pair identification ID as the pair identification ID recorded in the first session anchor in the second session anchor.
- the host device can convert the memory card 1 managed in the light-once format into an MS-DOS compatible format.
- the first session closing process is performed at the time of shipment from the factory, and is provided to the user.
- the root directory and the “MEMSTICK. Ind” file are recorded on the memory card 1 as shown in FIG. It is assumed that the first session close processing is performed after recording such a file.
- the "MEMSTICK. Ind” file is a file in which information indicating that this device is a write-once type memory card is described, and is generated under the root directory. Memory card 1 indicates this recording state, and the first session close processing is performed.
- Figure 20 shows the recorded image of the license format management data after the first session close process.
- the memory card 1 Before the first session close processing, the memory card 1 has a note entry and a file entry (MEM) pointing to the file MEMSTICK.ind in the page area of the spare block management numbers 0 to 1. Has been recorded.
- two session anchors (the pair identification ID is "1") are recorded in the memory area of the spare block management numbers 2 and 3 in the page area.
- Figure 21 shows the recorded image of the management data and entity data in the MS-DOS compatible format after the first session close process.
- the boot is recorded in the blocks whose physical addresses are "0" to "1".
- MBR is recorded in the block with the logical address "0" (physical block number 2)
- PBR and FAT are recorded in the block with the logical address "1" to "2” (physical block numbers 3 to 4).
- the root directory entry is recorded in the block with the logical address "3" (physical block number 5), and the entity data of "MEMSTICK. Ind” is recorded in the block with the logical address "4". I have.
- a file as shown in FIG. 22 is added to the memory card 1 after the first session closing process as described above.
- a first file Filel
- a second file File 2
- a first subdirectory Subl
- a third file File 3
- the second session close processing is performed.
- Fig. 23 shows a recorded image of the license format management data after the second session closing process.
- Figure 24 shows the recorded image of the management data and entity data in the MS-DOS compatible format after the second session close process.
- a file entry pointing to the first file is stored in the page area of the spare block management numbers 4 to 7 of the memory card 1.
- (1) and the second file A file entry ( 2 ) pointing to (File2), a subentry (1) pointing to the first subdirectory (Sub1), and a file entry ( 3 ) pointing to the second file (File3) are recorded. Is done.
- the first file (Filel), a second file I le (File2), each entity data of the third file (File 3) are respectively recorded in de Ichita recording region of 0 segment.
- the first session anchor (the ID for pair identification) is placed in the page area of the spare block management numbers 8 to 10.
- a directory mark (1) indicating a block in which a subdirectory entry that is the substance of the first subdirectory (Subl) is stored, and a second session anchor ( The ID for pair identification is "2").
- the updated PBR, FAT and root directory are recorded in the first spare block (physical block number 494-496) in the 0 segment.
- each block in which the PBR, FAT and root directory are recorded has the same logical address as the logical address of the block in which the original PBR, FAT and root directory before updating are recorded. Is recorded. Specifically, logical addresses 1 to 3 are recorded in the blocks of physical block numbers 494 to 496.
- a new sub-directory entry (1) of the first sub-directory (Subl) is created, and a 1-segment data recording area (physical block number 512, logical address) 4 9 2 block).
- the PBR, FAT, and root directory entries recorded during the first session close process are deleted. That is, the block status of the blocks with physical block numbers 3, 4, and 5 is set to "0".
- a file or the like as shown in FIG. 25 is added to the memory card 1 after the second session closing process as described above. That is, a fourth file (File4) is added under the root directory, a second subdirectory (Sub2) is added under the first subdirectory (Subl), and a second subdirectory is added. fifth append the file (File5) under I Lek tri (Sub2), and have appended sixth file (file 6) under the first subdirectories (SUBL). And then, Assume that the third session close processing is performed.
- Figure 26 shows an image of recorded write-once format management data after the third session close process.
- Fig. 27 shows the recorded image of the management data and entity data in the MS-DOS compatible format after the third session close process.
- the entity data of the sixth file (File 6) is divided into two parts, a data area of 0 segment and a data area of 1 segment, and recorded. No The logical address of the area divided by 2 is not continuous because the directory entry (1) is in the middle, and the fragment (6) is recorded as a fragment in such a case.
- the first session anchor (having ID “3” for pair identification) is placed in the page area of the spare block management numbers 15 to 17 and the 1 subdirectories directory indicating the proc which subdirectory entries are stored an entity of (sub 2) Torimaku (2), second session anchor (pair discrimination ID is "3" ) Is recorded.
- the updated PBR, FAT and root directory are recorded in the spare block (physical block numbers 497 to 499) in the 0 segment.
- the same logical address as the logical address of the block in which the original PBR, FAT and root directory before the update were recorded is recorded.
- the logical addresses 1 to 3 are recorded in the blocks of the physical block numbers 497 to 499.
- Updated first subdirectory The subdirectory entry (1) of the directory (Subl) is recorded in the first spare block (physical block number 106) in one segment.
- the same logical address as that of the block in which the original subdirectory entry (1) before the update is recorded is recorded.
- the logical address 494 is recorded in the block of the physical block number 104.
- a new sub-directory entry (1) of the second sub-directory (Subl) is newly created, and the beginning of an empty block in the data recording area of one segment (for example, Recorded in physical block number 6 13, logical address 5 93 3 block).
- the PBR, FAT, root directory entry, and subdirectory entry (1) of the first subdirectory recorded during the second session close processing are deleted. That is, the block status force S “0” of the blocks of the physical block numbers 494, 495, and 496 and the block of the physical block number 510 is set.
- a physical configuration and a file management system compatible with a memory device using a rewritable recording medium are applied to a recording medium on which data can be written only once in bit units. In addition to being able to delete files, etc. on the file management system.
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN02805380XA CN1493026B (zh) | 2001-12-25 | 2002-12-18 | 存储装置及利用此存储装置的记录再生装置 |
US10/469,209 US7039786B2 (en) | 2001-12-25 | 2002-12-18 | Memory device and recording and/or reproducing apparatus employing this memory device |
KR1020037011050A KR101033068B1 (ko) | 2001-12-25 | 2002-12-18 | 메모리 장치 및 그 메모리 장치를 이용한 기록 재생 장치 |
EP02805887A EP1460549A4 (en) | 2001-12-25 | 2002-12-18 | MEMORY DEVICE AND RECORDING / REPRODUCING APPARATUS USING THE DEVICE |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2001392453A JP2003196142A (ja) | 2001-12-25 | 2001-12-25 | ライトワンス型メモリ装置及びファイル管理方法 |
JP2001-392453 | 2001-12-25 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2003056432A1 true WO2003056432A1 (fr) | 2003-07-10 |
Family
ID=19188637
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2002/013258 WO2003056433A1 (fr) | 2001-12-25 | 2002-12-18 | Dispositif a memoire et appareil d'enregistrement/reproduction utilisant ledit dispositif |
PCT/JP2002/013256 WO2003056431A1 (fr) | 2001-12-25 | 2002-12-18 | Dispositif de memoire et appareil d'enregistrement/reproduction faisant appel a ce dispositif |
PCT/JP2002/013257 WO2003056432A1 (fr) | 2001-12-25 | 2002-12-18 | Dispositif de memoire et appareil d'enregistrement/reproduction faisant appel a ce dispositif |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2002/013258 WO2003056433A1 (fr) | 2001-12-25 | 2002-12-18 | Dispositif a memoire et appareil d'enregistrement/reproduction utilisant ledit dispositif |
PCT/JP2002/013256 WO2003056431A1 (fr) | 2001-12-25 | 2002-12-18 | Dispositif de memoire et appareil d'enregistrement/reproduction faisant appel a ce dispositif |
Country Status (7)
Country | Link |
---|---|
US (4) | US7039753B2 (ja) |
EP (3) | EP1460548B1 (ja) |
JP (1) | JP2003196142A (ja) |
KR (3) | KR101091311B1 (ja) |
CN (3) | CN100388235C (ja) |
DE (1) | DE60233971D1 (ja) |
WO (3) | WO2003056433A1 (ja) |
Families Citing this family (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1498810B1 (en) | 1999-10-21 | 2018-12-26 | Panasonic Corporation | A semiconductor memory card access apparatus, a computer-readable recording medium, an initialization method, and a semiconductor memory card |
EP1576593B1 (en) | 2002-12-24 | 2015-10-21 | LG Electronics Inc. | Dual journaling store method and storage medium thereof |
KR100483490B1 (ko) * | 2002-12-24 | 2005-04-15 | 한국전자통신연구원 | 저장 매체에 데이터를 저장하기 위한 이중 저널링저장방법 |
US7146388B2 (en) * | 2003-10-07 | 2006-12-05 | International Business Machines Corporation | Method, system, and program for archiving files |
JP2005222201A (ja) * | 2004-02-04 | 2005-08-18 | Matsushita Electric Ind Co Ltd | メモリアクセス装置、及び半導体メモリカード |
EP1736882A4 (en) * | 2004-03-31 | 2008-06-25 | Sanyo Electric Co | INFORMATION RECORDING METHOD AND INFORMATION RECORDING / REPRODUCING DEVICE |
KR100876084B1 (ko) * | 2007-02-13 | 2008-12-26 | 삼성전자주식회사 | 플래시 저장 장치로 삭제 정보를 전달할 수 있는 컴퓨팅시스템 |
KR20070092715A (ko) * | 2005-01-05 | 2007-09-13 | 톰슨 라이센싱 | 파일의 콘텐츠를 관리하는 장치 및 방법 |
KR100704628B1 (ko) | 2005-03-25 | 2007-04-09 | 삼성전자주식회사 | 다수의 스트링을 사용하여 상태 정보를 저장하는 방법 및비휘발성 저장 장치 |
US20060253643A1 (en) * | 2005-05-04 | 2006-11-09 | Delkin Devices, Inc. | Memory with isolated master boot record |
US9117128B2 (en) | 2005-12-09 | 2015-08-25 | Tego, Inc. | External access to memory on an RFID tag |
US9418263B2 (en) | 2005-12-09 | 2016-08-16 | Tego, Inc. | Operating systems for an RFID tag |
US8988223B2 (en) | 2005-12-09 | 2015-03-24 | Tego Inc. | RFID drive management facility |
US9361568B2 (en) | 2005-12-09 | 2016-06-07 | Tego, Inc. | Radio frequency identification tag with hardened memory system |
US8947233B2 (en) | 2005-12-09 | 2015-02-03 | Tego Inc. | Methods and systems of a multiple radio frequency network node RFID tag |
US9430732B2 (en) | 2014-05-08 | 2016-08-30 | Tego, Inc. | Three-dimension RFID tag with opening through structure |
US9542577B2 (en) | 2005-12-09 | 2017-01-10 | Tego, Inc. | Information RFID tagging facilities |
US7310282B2 (en) * | 2005-12-30 | 2007-12-18 | Lexmark International, Inc. | Distributed programmed memory cell overwrite protection |
US7404121B2 (en) * | 2006-01-31 | 2008-07-22 | Verigy (Singapore) Pte. Ltd. | Method and machine-readable media for inferring relationships between test results |
TW200732913A (en) * | 2006-02-24 | 2007-09-01 | Benq Corp | Memory allocation method and system |
US7600850B2 (en) * | 2006-03-01 | 2009-10-13 | Lexmark International, Inc. | Internal vent channel in ejection head assemblies and methods relating thereto |
JP2007241539A (ja) * | 2006-03-07 | 2007-09-20 | Hitachi Systems & Services Ltd | 半導体フラッシュメモリにおけるデータ管理及び制御システムと半導体フラッシュメモリ収容装置 |
EP1868328B2 (de) * | 2006-06-12 | 2017-03-01 | Siemens Aktiengesellschaft | Verfahren zum Betrieb eines Automatisierungsgerätes und Automatisierungsgerät |
US8849864B2 (en) * | 2006-10-17 | 2014-09-30 | At&T Intellectual Property I, L.P. | Digital archive systems, methods and computer program products for linking linked files |
US20080172387A1 (en) * | 2007-01-16 | 2008-07-17 | Olaf Manczak | Speeding up traversal of a file system tree |
JP4372168B2 (ja) * | 2007-02-19 | 2009-11-25 | 株式会社東芝 | 半導体メモリ情報蓄積装置とその蓄積データ処理方法 |
EP2147399B1 (en) * | 2007-05-03 | 2015-08-12 | Tego Inc. | Multiple radio frequency network node rfid tag utilizing otp memory systems |
US8527691B2 (en) * | 2007-07-31 | 2013-09-03 | Panasonic Corporation | Nonvolatile memory device and nonvolatile memory system with fast boot capability |
CN101364421B (zh) * | 2007-08-07 | 2010-08-25 | 飞利浦建兴数位科技股份有限公司 | 多媒体收纳装置 |
JP2010009205A (ja) * | 2008-06-25 | 2010-01-14 | Nikon Corp | 記録制御装置 |
JP2010009206A (ja) * | 2008-06-25 | 2010-01-14 | Nikon Corp | 記録制御装置 |
JP5540969B2 (ja) * | 2009-09-11 | 2014-07-02 | ソニー株式会社 | 不揮発性メモリ装置、メモリコントローラ、およびメモリシステム |
JP6028709B2 (ja) * | 2013-10-18 | 2016-11-16 | ソニー株式会社 | 記憶制御装置、記憶装置、情報処理システムおよびその記憶制御方法 |
US9953193B2 (en) | 2014-09-30 | 2018-04-24 | Tego, Inc. | Operating systems for an RFID tag |
US9665743B2 (en) * | 2015-02-26 | 2017-05-30 | Whitecanyon Software, Inc. | Selective storage device wiping system and method |
US9760301B2 (en) * | 2015-08-13 | 2017-09-12 | Texas Instruments Incorporated | WOM code emulation of EEPROM-type devices |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5119291A (en) | 1987-03-26 | 1992-06-02 | International Business Machines Corporation | Modular data storage directories for large-capacity data storage units wherein the index to the records in a sector is located in the next adjacent sector |
JP2001051889A (ja) * | 1999-05-31 | 2001-02-23 | Sharp Corp | 不揮発性半導体記憶装置を用いたファイルシステム |
JP2001142774A (ja) * | 1999-11-11 | 2001-05-25 | Toshiba Corp | メモリカード及び同カードに適用されるアドレス変換方法 |
JP2001325131A (ja) * | 2000-05-16 | 2001-11-22 | Ricoh Co Ltd | ファイルシステムおよびファイル記録方法 |
Family Cites Families (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US2001A (en) * | 1841-03-12 | Sawmill | ||
CA1177558A (en) * | 1982-04-15 | 1984-11-06 | Groupe Videotron Ltee. (Le) | Cable network data transmission system |
US4575827A (en) * | 1984-05-18 | 1986-03-11 | International Business Machines Corporation | Self-archiving data recording |
US4700293A (en) * | 1985-05-14 | 1987-10-13 | The United States Of America As Represented By The Secretary Of The Air Force | Maintenance port system incorporating software development package |
US4791623A (en) * | 1986-04-03 | 1988-12-13 | Optotech, Inc. | File management system for use in an optical data storage system |
FR2604280B1 (fr) * | 1986-09-19 | 1988-11-10 | Picard Michel | Procede de gestion de fichiers sur un support d'information non effacable |
JPH0471Y2 (ja) | 1987-06-30 | 1992-01-06 | ||
US5247658A (en) * | 1989-10-31 | 1993-09-21 | Microsoft Corporation | Method and system for traversing linked list record based upon write-once predetermined bit value of secondary pointers |
US5150473A (en) * | 1990-01-16 | 1992-09-22 | Dantz Development Corporation | Data storage format for addressable or sequential memory media |
CA2045799C (en) * | 1990-07-11 | 1999-03-23 | Kenneth L. Thompson | File system with read/write and read only storage |
JPH056299A (ja) * | 1990-11-16 | 1993-01-14 | Olympus Optical Co Ltd | 光カード及びそのフアイル管理方法 |
JPH04186447A (ja) * | 1990-11-21 | 1992-07-03 | Canon Inc | 情報処理装置 |
JP3229345B2 (ja) * | 1991-09-11 | 2001-11-19 | ローム株式会社 | 不揮発性icメモリ |
US6256642B1 (en) * | 1992-01-29 | 2001-07-03 | Microsoft Corporation | Method and system for file system management using a flash-erasable, programmable, read-only memory |
JP3105092B2 (ja) * | 1992-10-06 | 2000-10-30 | 株式会社東芝 | 半導体メモリ装置 |
JPH06338141A (ja) * | 1993-03-29 | 1994-12-06 | Nippon Hoso Kyokai <Nhk> | 追記型記録媒体、フォーマット装置および方法、データ読みだし装置および方法、ならびにデータ書き込み装置および方法 |
KR970008188B1 (ko) * | 1993-04-08 | 1997-05-21 | 가부시끼가이샤 히다찌세이사꾸쇼 | 플래시메모리의 제어방법 및 그것을 사용한 정보처리장치 |
WO1995011508A1 (fr) * | 1993-10-18 | 1995-04-27 | Sony Corporation | Procede de gestion d'informations, support d'enregistrement de donnees, procede d'enregistrement de donnees, procede et dispositif d'extraction d'informations |
JPH08212019A (ja) * | 1995-01-31 | 1996-08-20 | Mitsubishi Electric Corp | 半導体ディスク装置 |
EP0803815A1 (en) * | 1995-11-10 | 1997-10-29 | Sony Corporation | Information processing apparatus and method |
US5701492A (en) * | 1996-03-29 | 1997-12-23 | Canon Kabushiki Kaisha | Fail-safe flashing of EPROM |
JP3489967B2 (ja) * | 1997-06-06 | 2004-01-26 | 松下電器産業株式会社 | 半導体記憶装置及びキャッシュメモリ装置 |
JP3546654B2 (ja) * | 1997-08-07 | 2004-07-28 | 株式会社日立製作所 | 情報記録装置及び情報記録方法 |
DE19741854A1 (de) * | 1997-09-23 | 1999-03-25 | Bosch Gmbh Robert | Autoradio mit einem Handgerät |
JP3233079B2 (ja) * | 1997-09-30 | 2001-11-26 | ソニー株式会社 | データ処理システム及びデータ処理方法 |
JP3119214B2 (ja) * | 1997-09-30 | 2000-12-18 | ソニー株式会社 | 記憶装置、データ処理システム並びにデータの書き込み及び読み出し方法 |
JP4304734B2 (ja) * | 1998-04-17 | 2009-07-29 | ソニー株式会社 | 再生装置、データの再生方法及び記録媒体 |
US6643662B1 (en) * | 2000-09-21 | 2003-11-04 | International Business Machines Corporation | Split bi-directional stack in a linear memory array |
US6247096B1 (en) * | 1998-11-02 | 2001-06-12 | International Business Machines Corporation | Handling eject requests of logical volumes in a data storage subsystem |
EP1093121A1 (en) * | 1999-10-13 | 2001-04-18 | Matsushita Electric Industrial Co., Ltd. | Information recording medium, and method and apparatus for recording and reproducing information using the same |
US6377500B1 (en) | 1999-11-11 | 2002-04-23 | Kabushiki Kaisha Toshiba | Memory system with a non-volatile memory, having address translating function |
JP3785299B2 (ja) * | 2000-03-16 | 2006-06-14 | 本田技研工業株式会社 | 車両制御装置のためのメモリ書き換えシステム |
JP2001282261A (ja) * | 2000-03-30 | 2001-10-12 | Canon Inc | 音声データ設定装置及び方法、音声データ生成装置及び方法、記録媒体 |
US7051054B1 (en) | 2000-05-30 | 2006-05-23 | Dphi Acquisitions, Inc. | Method and apparatus for emulating read/write file system on a write-once storage disk |
US20030120858A1 (en) | 2000-09-15 | 2003-06-26 | Matrix Semiconductor, Inc. | Memory devices and methods for use therewith |
US6324093B1 (en) * | 2000-09-15 | 2001-11-27 | Hewlett-Packard Company | Write-once thin-film memory |
US6675276B2 (en) * | 2001-11-13 | 2004-01-06 | Eastman Kodak Company | Method for providing extensible dos-fat system structures on one-time programmable media |
-
2001
- 2001-12-25 JP JP2001392453A patent/JP2003196142A/ja active Pending
-
2002
- 2002-12-18 WO PCT/JP2002/013258 patent/WO2003056433A1/ja active Application Filing
- 2002-12-18 DE DE60233971T patent/DE60233971D1/de not_active Expired - Lifetime
- 2002-12-18 CN CNB028072170A patent/CN100388235C/zh not_active Expired - Fee Related
- 2002-12-18 KR KR1020037011049A patent/KR101091311B1/ko not_active IP Right Cessation
- 2002-12-18 EP EP02786140A patent/EP1460548B1/en not_active Expired - Fee Related
- 2002-12-18 KR KR1020037011050A patent/KR101033068B1/ko not_active IP Right Cessation
- 2002-12-18 KR KR1020037011051A patent/KR100987241B1/ko not_active IP Right Cessation
- 2002-12-18 CN CN02805380XA patent/CN1493026B/zh not_active Expired - Fee Related
- 2002-12-18 WO PCT/JP2002/013256 patent/WO2003056431A1/ja active Application Filing
- 2002-12-18 US US10/469,208 patent/US7039753B2/en not_active Expired - Fee Related
- 2002-12-18 US US10/469,209 patent/US7039786B2/en not_active Expired - Fee Related
- 2002-12-18 WO PCT/JP2002/013257 patent/WO2003056432A1/ja active Application Filing
- 2002-12-18 EP EP02786139A patent/EP1460547A4/en not_active Withdrawn
- 2002-12-18 CN CNB028054466A patent/CN100440165C/zh not_active Expired - Fee Related
- 2002-12-18 US US10/469,210 patent/US7447672B2/en not_active Expired - Fee Related
- 2002-12-18 EP EP02805887A patent/EP1460549A4/en not_active Withdrawn
-
2006
- 2006-08-24 US US11/509,505 patent/US7634613B2/en not_active Expired - Fee Related
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5119291A (en) | 1987-03-26 | 1992-06-02 | International Business Machines Corporation | Modular data storage directories for large-capacity data storage units wherein the index to the records in a sector is located in the next adjacent sector |
JP2001051889A (ja) * | 1999-05-31 | 2001-02-23 | Sharp Corp | 不揮発性半導体記憶装置を用いたファイルシステム |
JP2001142774A (ja) * | 1999-11-11 | 2001-05-25 | Toshiba Corp | メモリカード及び同カードに適用されるアドレス変換方法 |
JP2001325131A (ja) * | 2000-05-16 | 2001-11-22 | Ricoh Co Ltd | ファイルシステムおよびファイル記録方法 |
Non-Patent Citations (2)
Title |
---|
See also references of EP1460549A4 |
TADASHI MIKI ET AL.: "Tsuikigata hikari disc kanri hoshiki no kento to seino hyoka", INFORMATION PROCESSING SOCIETY OF JAPAN KENKYU HOKOKU (88-OS-41), 41-4, vol. 88, no. 81, 11 November 1988 (1988-11-11), pages 1 - 8, XP002967611 * |
Also Published As
Publication number | Publication date |
---|---|
CN1500249A (zh) | 2004-05-26 |
CN100440165C (zh) | 2008-12-03 |
CN100388235C (zh) | 2008-05-14 |
EP1460548B1 (en) | 2009-10-07 |
EP1460548A4 (en) | 2007-04-25 |
WO2003056433A1 (fr) | 2003-07-10 |
EP1460549A4 (en) | 2007-06-06 |
KR20040062875A (ko) | 2004-07-09 |
US7039753B2 (en) | 2006-05-02 |
US20040196687A1 (en) | 2004-10-07 |
US20040103240A1 (en) | 2004-05-27 |
CN1493028A (zh) | 2004-04-28 |
EP1460547A1 (en) | 2004-09-22 |
EP1460547A4 (en) | 2006-12-13 |
JP2003196142A (ja) | 2003-07-11 |
US20060282446A1 (en) | 2006-12-14 |
US7634613B2 (en) | 2009-12-15 |
CN1493026A (zh) | 2004-04-28 |
US7039786B2 (en) | 2006-05-02 |
CN1493026B (zh) | 2010-05-26 |
KR20040067856A (ko) | 2004-07-30 |
KR100987241B1 (ko) | 2010-10-12 |
US7447672B2 (en) | 2008-11-04 |
KR101033068B1 (ko) | 2011-05-06 |
EP1460548A1 (en) | 2004-09-22 |
US20040098397A1 (en) | 2004-05-20 |
DE60233971D1 (de) | 2009-11-19 |
KR101091311B1 (ko) | 2011-12-07 |
EP1460549A1 (en) | 2004-09-22 |
KR20040062440A (ko) | 2004-07-07 |
WO2003056431A1 (fr) | 2003-07-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2003056432A1 (fr) | Dispositif de memoire et appareil d'enregistrement/reproduction faisant appel a ce dispositif | |
US7039754B2 (en) | Detachably mounted removable data storage device | |
US7472251B2 (en) | Data storage apparatus detachably mounted to a host apparatus | |
KR100980309B1 (ko) | 호스트 디바이스 및 메모리 시스템 | |
US20080098161A1 (en) | Memory device and control method thereof | |
US7051251B2 (en) | Method for storing data in a write-once memory array using a write-many file system | |
JP2007018528A (ja) | メモリ装置、ファイル管理方法及び記録再生装置 | |
JP3624647B2 (ja) | 記憶装置、データ管理装置、データ管理システム、データ管理方法、ファイル管理装置、記録媒体及びファイル管理システム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 02805380.X Country of ref document: CN |
|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): CN KR US |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LU MC NL PT SE SI SK TR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2002805887 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020037011050 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10469209 Country of ref document: US |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWP | Wipo information: published in national office |
Ref document number: 1020037011050 Country of ref document: KR |
|
WWP | Wipo information: published in national office |
Ref document number: 2002805887 Country of ref document: EP |