+

WO2000067130A1 - Systeme de gestion de fichiers - Google Patents

Systeme de gestion de fichiers Download PDF

Info

Publication number
WO2000067130A1
WO2000067130A1 PCT/JP1999/002324 JP9902324W WO0067130A1 WO 2000067130 A1 WO2000067130 A1 WO 2000067130A1 JP 9902324 W JP9902324 W JP 9902324W WO 0067130 A1 WO0067130 A1 WO 0067130A1
Authority
WO
WIPO (PCT)
Prior art keywords
recording medium
medium
management information
confidentiality
computer
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.)
Ceased
Application number
PCT/JP1999/002324
Other languages
English (en)
Japanese (ja)
Inventor
Jun Kamada
Etsuo Ono
Bintatsu Noda
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Fujitsu Ltd filed Critical Fujitsu Ltd
Priority to JP2000615902A priority Critical patent/JP3866519B2/ja
Priority to PCT/JP1999/002324 priority patent/WO2000067130A1/fr
Publication of WO2000067130A1 publication Critical patent/WO2000067130A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604—Improving or facilitating administration, e.g. storage management
    • G06F3/0607—Improving or facilitating administration, e.g. storage management by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/0638—Organizing or formatting or addressing of data
    • G06F3/0643—Management of files
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/0671—In-line storage system
    • G06F3/0673—Single storage device
    • G06F3/0674—Disk device
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
    • G11B20/00086—Circuits for prevention of unauthorised reproduction or copying, e.g. piracy

Definitions

  • the present invention relates to a storage medium format and a storage medium file management system.
  • Portable media typified by floppy disks and magneto-optical disks such as M ⁇ , which have recently attracted attention, have the feature that files can be easily exchanged between multiple computers. There is a problem that the information you want to access is easily accessed on other computers.
  • the conventional technology has a problem that, when confidentiality is not required so much, processing load is too heavy to encrypt each file, which is inconvenient in actual use.
  • the present invention based on the medium ID unique to the medium, the drive device ID unique to the drive device, the computer ID unique to the computer, etc., the storage destination of the file management information of the file on the medium (the block number on the medium) ), And encrypting management information based on these IDs provides a method that allows access to the file only on a specific medium, a specific drive, or a specific computer. I do. Disclosure of the invention
  • an object of the present invention is to provide a confidential data storage method that can access required data only by using a specific medium or a specific device.
  • the device of the present invention is a device for formatting a recording medium or accessing a file recorded on the recording medium, and reads an identifier of the recording medium or the device, and reads the identifier based on the identifier.
  • Confidentiality imparting / cancelling means for imparting confidentiality to the recording medium, or canceling confidentiality of the recording medium; and when imparting the confidentiality to the recording medium, or confidentiality of the recording medium.
  • recording medium access for accessing the recording medium when is released.
  • the method of the present invention comprises the steps of: formatting a recording medium or recording on the recording medium (A) reading an identifier of the recording medium or the device and giving the recording medium confidentiality based on the identifier, or Removing the confidentiality of the medium; and (b) accessing the recording medium when the confidentiality is given to the recording medium or when the confidentiality of the recording medium is released. It is characterized by having. According to the present invention, it is possible to impart confidentiality to a recording medium from which data is to be read or an identifier unique to the device, so that data is read from a specific recording medium. In other words, the data cannot be accessed except by reading the data overnight using a specific device.
  • the identifier is not rewritable by an ordinary method, and furthermore, it is set so that it cannot be read by an ordinary method. This makes it possible to prevent the identifier from being copied even if the contents of the recording medium are illegally copied, thereby preventing unauthorized use of the data.
  • confidentiality can be imparted to the recording medium with faster and lighter processing than the conventional method.
  • FIG. 1 is a diagram showing a typical layout of files and file management information on a medium.
  • FIG. 2 is a configuration diagram of the device according to the first embodiment of the present invention.
  • FIG. 3 is a flowchart showing the flow of the format process of FIG.
  • FIG. 4 is a configuration diagram of an apparatus according to the second embodiment of the present invention.
  • FIG. 5 is a flowchart showing the flow of processing of the file system of FIG.
  • FIG. 6 is a diagram showing a layout of a storage medium on which a logical format is performed in a format according to the first embodiment.
  • FIG. 5 is a configuration diagram of an apparatus according to a third embodiment of the present invention.
  • FIG. 8 is a flowchart showing a processing flow in the third embodiment.
  • FIG. 9 is a configuration diagram of the device according to the fourth embodiment of the present invention.
  • FIG. 10 is a flowchart showing the flow of processing in the fourth embodiment.
  • FIG. 11 is a configuration diagram of an apparatus according to a fifth embodiment of the present invention.
  • FIG. 12 is a flowchart showing the flow of processing in the fifth embodiment.
  • FIG. 13 is a configuration diagram of an apparatus according to a sixth embodiment of the present invention.
  • FIG. 14 is a flowchart showing the flow of processing in the sixth embodiment.
  • FIG. 15 is a configuration diagram of an apparatus according to the seventh embodiment of the present invention.
  • FIG. 16 is a configuration diagram of the device according to the eighth embodiment of the present invention.
  • FIG. 17 is a configuration diagram showing an apparatus according to a ninth embodiment of the present invention.
  • FIG. 18 is a configuration diagram showing an apparatus according to a tenth embodiment of the present invention.
  • FIG. 19 is a flowchart showing a processing flow according to the eleventh embodiment of the present invention.
  • FIG. 20 is a flowchart showing a processing flow according to the 12th embodiment of the present invention.
  • FIG. 21 is a flowchart showing a processing flow according to the thirteenth embodiment of the present invention.
  • FIG. 22 is a diagram showing a configuration diagram of the device according to the fourteenth embodiment of the present invention.
  • FIG. 23 is a flowchart showing a processing flow in the fourteenth embodiment of the present invention.
  • FIG. 24 is a configuration diagram showing a device configuration of the fifteenth embodiment of the present invention.
  • FIG. 25 is a flowchart showing a processing flow in the fifteenth embodiment. You.
  • FIG. 26 is a diagram illustrating an example of the encryption / decryption circuit in the fourteenth and fifteenth embodiments.
  • FIG. 27 is a diagram showing a layout on a medium logically formatted by the format according to the fourteenth embodiment.
  • FIG. 28 is a diagram showing a configuration diagram of the device according to the sixteenth embodiment of the present invention.
  • FIG. 29 is a configuration diagram of an apparatus according to a seventeenth embodiment of the present invention.
  • FIG. 30 is a diagram showing a hardware configuration required when the embodiment of the present invention is realized by a program.
  • FIG. 1 is a diagram showing a typical layout of files and file management information on a medium.
  • the section management information manages the start B N (Block Number: section start position) of the section, which is a continuous area, and its length (section length).
  • the volume management information manages which partitions constitute a volume that can be used by the user (list of used partitions), and has a link to the root directory management information in the volume. In this example, a volume is composed of one partition.
  • the root directory management information has a list of block numbers of the root directory that exists fragmented on the medium (a list of used blocks).
  • the root directory is fragmented into three.
  • the file management information has, as a list, the block numbers of the files that are fragmented on the medium.
  • the file is fragmented into three Is becoming
  • the subdirectory management information has a list of used blocks used by the subdirectory.
  • the subdirectory stores the names of the files stored in the subdirectory and the file management. Has links to information. Of course, if the subdirectory includes a lower subdirectory, the name of the lower subdirectory and a link to management information are stored.
  • management information outside the plot is placed in a fixed location.
  • the storage destinations of the partition management information and the volume management information which are management information outside the partition, are defined as a medium ID (medium identifier), a device ID (device identifier), and a computer ID ( By changing the ID according to the computer identifier, or encrypting the management information using these IDs as keys, file hair access on the medium cannot be easily performed.
  • a medium ID medium identifier
  • a device ID device identifier
  • a computer ID By changing the ID according to the computer identifier, or encrypting the management information using these IDs as keys, file hair access on the medium cannot be easily performed.
  • FIG. 2 is a configuration diagram of the device according to the first embodiment of the present invention.
  • the medium 1 has a non-rewritable medium ID 2 and a read / write area 3.
  • the drive device 4 includes a medium ID reading section 5 for reading the medium ID 2, a medium ID transfer section 6 for transferring the medium ID 2 read by the medium ID reading section 5 to the computer 11, and a readable / writable area.
  • the format 11 operating on the computer 11 includes a medium ID reading unit 7 that receives the medium ID 2 transferred from the medium ID transferring unit 6 and a medium ID 2 read by the medium ID reading unit 7. Determine the block number (block number) for storing the management information
  • There is a storage destination determining unit 8 for storing the management information in a block having the block number determined by the storage destination determining unit 8.
  • the non-rewritable medium ID 2 is recorded in a different area from the normal readable / writable area 3 on the medium 1 and at a position on the medium 1 which can be read only by a special method. This is because if the medium ID 2 is written in the same part as the normal readable / writable area 3, for example, even if write protection is performed, it will be rewritten by some method, and only the rewritten person will write the file. It will be possible to make it accessible. Therefore, if the medium ID 2 of a file that should be accessible only by the owner of the medium 1 has been rewritten, the owner will not be able to access the file, and the medium ID 2 will be changed. Only the rewritten person can access the file.
  • a malicious user can illegally access the owner's medium 1 and change the medium ID 2 so that only the user can access the file.
  • the medium ID 2 is stored in a readable area by a normal access method, the medium ID 2 is easily stolen, and confidentiality cannot be maintained.
  • the drive device 4 is specially provided with a medium ID reading unit 5 for reading the medium ID 2.
  • the medium ID 2 read by the medium ID reading unit 5 is sent to the medium ID transfer unit 6 and sent to the computer 11 to which the drive device 4 is connected.
  • the medium ID reading unit 7 of the formatter 10 operating on the computer 11 receives the medium ID 2 and sends it to the storage destination determining unit 8.
  • the storage destination determination unit 8 determines the number of the block in which the partition management information and the poly- ume management information are to be stored, using the transmitted medium ID 2 or a number corresponding to the medium ID 2 on a one-to-one basis. Then, it instructs the readable / writable area access unit 9 to write the partition management information and the volume management information.
  • the instruction from the readable / writable area access unit 9 of 0 is passed to the readable / writable area access unit 12 of the drive device 4, and the above instruction of the readable / writable area 3 on the medium 1 is given by the readable / writable area access unit 12.
  • Partition management information and volume management information are written in the block having the block number.
  • FIG. 3 is a flowchart showing the flow of the format 10 process of FIG.
  • the formatter 10 When the formatter 10 starts processing, it reads out the medium ID 2 (step S 1; for example, in the case of the figure, the medium ID is “1 2 3 4 5”).
  • the BN (block number) of the block in which the partition management information is to be stored is determined based on the medium ID2 (step S2).
  • the notation “ID% 64” indicates a remainder obtained by dividing the medium ID2 by 64.
  • the method of determining the block number (B N) for storing the block management information is not limited to the above method, and should be appropriately determined by a person skilled in the art in order to further increase confidentiality.
  • the block management information is written in the block number determined above (step S3).
  • the block number of the storage destination of the volume management information is determined in the same manner as the partition management information (step S4), and this is written in the block (step S5).
  • the storage destination block number of the volume management information is determined by adding the remainder obtained by dividing the medium ID 2 by 64 to 5 13.
  • the method of determining the storage destination block number is not limited to this method.
  • FIG. 4 is a configuration diagram of an apparatus according to the second embodiment of the present invention.
  • the medium 1 has a non-rewritable medium ID 2 and a read / write area 3.
  • the drive device 4 calculates the medium ID reading unit 5 and the read medium ID 2
  • the file system 15 on the computer 11 has a medium ID reading unit 7, a storage unit that determines the number of a block for storing management information based on the read medium ID 2, and a read destination determining unit 8, which has been determined.
  • the file system 15 performs processing in response to a medium use request from the application 16.
  • the application 16 may be a professional software, a file management tool, or various other applications. That is, all applications that have the function of accessing the medium 1 are applicable.
  • a medium ID reading section 5, a medium ID transfer section 6, a medium ID reading section 7, and a readable / writable area access section 12 have the same functions as in FIG.
  • the storage Z read destination determining unit 8 ′ does not specify the block number to store the partition management information and the volume management information, as shown in format 10 in FIG.
  • the block number storing the partition management information and the volume management information of the accessed file is calculated from the medium ID 2, and the calculated block number is used as the read / write area access unit. 9 '.
  • the readable / writable area access unit 9 ′ writes and reads a file to / from the medium 1 in accordance with a medium use request from the application 16.
  • the application 16 is a formatter 10 as shown in FIG. 2 or an application having the function, and performs a logical format together with a physical format. It also includes the task of writing information and volume management information to the medium 1.
  • FIG. 5 is a flowchart showing a processing flow of the file system 15 in FIG.
  • File system 15 is activated by media usage request from application 16 Start the mounting process (preparation of medium 1 in drive device 4 and preparation for reading data of medium 1).
  • the BN (block number) in which the partition management information is stored is determined based on the medium ID 2 (step S11).
  • a value obtained by adding the modulo 64 of the medium ID to the base value Basel (BN 5 12 if the same as in FIG. 3) is used.
  • Basel is appropriately determined by those skilled in the art using the present embodiment, and the processing form of adding the remainder obtained by dividing the medium ID by 64 to Basel should also be appropriately changed. It is.
  • the partition management information is read from the determined block number (step S12), and the storage location of the volume management information is determined in the same manner as the partition management information (step S13), and this is determined.
  • Read step S14.
  • the storage location of the volume management information is calculated by adding the value obtained by dividing the medium ID by 64 to Base 2 (5 13 in FIG. 3). The method of determining the storage destination of the file should be appropriately changed by those skilled in the art using the present embodiment.
  • FIG. 6 is a diagram illustrating a layout of a storage medium on which a logical format is performed in a format according to the first embodiment.
  • the partition management information is arranged in the block of block number 569, and the volume management information is arranged in the block of block number 570.
  • the section management information records the start position and the section length of the section, and the volume management information records a list of used sections and a link to the root directory management information.
  • the root directory stores file names and links to file management information, subdirectory names and links to subdirectory management information.
  • the method of determining the recording positions of the partition management information and the volume management information is changed, and even if the method of calculating the recording position of either the partition management information or the volume management information is known, the method of calculating the other recording position is preferable. Not understand. However, in this case, it is necessary that the recording positions of the block management information and the volume management information do not overlap.
  • FIG. 7 is a configuration diagram of an apparatus according to the third embodiment of the present invention.
  • the drive device ID on the drive device 4 ' is used without using the medium ID on the medium.
  • the ID of the drive device 4 ′ is stored in the device ID storage unit 17.
  • the device ID is written in a part of the firmware written in the ROM (not shown) of the drive device 4 ′, and can be read as needed.
  • the device ID stored in the device ID storage unit 17 is read out by the device ID transfer unit 6 and passed to the device ID reading unit 7 of the format server 1OA that operates on the computer 11. Then, the device ID is passed from the device ID reading unit 7 to the storage destination determining unit 8, and the storage location determining unit 8 determines the storage location of the partition management information / polyume management information as in the first embodiment.
  • the readable / writable area access unit 9 issues an instruction to the readable / writable area access unit 12 of the drive device 4 ′, and stores partition management information and volume management information in the readable / writable area 3 ′ of the medium 1 ′.
  • the medium 1 ′ does not need to record the medium ID, but the medium ID is recorded on the medium 1 ′ as in the first embodiment, as in an embodiment described later. If necessary, combine the device ID and media ID, and set the partition management information. When calculating the recording position of the information and the recording position of the volume management information, the medium ID and the device ID may be used.
  • FIG. 8 is a flowchart showing a processing flow in the third embodiment. In the steps shown in the figure, the same steps as those in FIG. 3 are denoted by the same step symbols.
  • step S 1 ′ the device ID is read. In the example of the figure, it is ID-1 2 3 4 5.
  • the storage location of the partition management information is determined (step S2).
  • the storage destination B N partition management information storage destination B N
  • the partition management information is stored in the storage location determined in step S2 (step S3).
  • step S4 the storage destination of the volume management information is determined.
  • the storage destination BN is obtained by adding the remainder obtained by dividing the device ID by 64 to Base2.
  • the volume management information is stored in the storage location determined in this way (step S5), and the format processing ends.
  • Basel and Base2 are values to be set arbitrarily, and the method of obtaining the storage destination BN is not limited to this embodiment.
  • FIG. 9 is a configuration diagram of the device according to the fourth embodiment of the present invention.
  • the configuration shown in the figure shows a case where the computer 11 accesses the medium 1 ′ using the application 16 and the file system 15 in the third embodiment.
  • applications 16 are conceivable, but examples include word processors, spreadsheet software, and drawing software.
  • the present invention is not limited to these, and as described above, anything may be used as long as it writes data on the medium 1 ′ and reads data from the medium 1 ′.
  • the media use request from the application 16 is sent to the readable / writable area of the file system 15A. Sent to area access unit 9 '.
  • the device ID of the drive device 4 ′ is read from the device ID storage unit 17, and is transferred by the device ID transfer unit 6 to the device ID read unit 7 of the file system 15 A operating on the computer 11. You.
  • the device ID obtained by the device ID reading unit 7 is sent to the storage Z read destination determining unit 8 ′, and the storage Z read destination determining unit 8 ′ stores or blocks the partition management information and the volume management information.
  • BN is determined.
  • the BN determined by the storage Z read destination determining unit 8 ′ is sent to the readable / writable area access unit 9 ′, and an instruction to access the medium 1 ′ is output from the readable / writable area access unit 9 ′ to the drive device 4 ′. .
  • FIG. 10 is a flowchart showing the flow of processing in the fourth embodiment.
  • the same steps as those in FIG. 5 are denoted by the same step numbers.
  • step S10 ' the device ID is read.
  • ID 12345.
  • step S11 the storage location of the partition management information is determined.
  • the method of calculating the storage destination BN is the same as in FIG.
  • step S13 the BN for storing the volume management information is determined.
  • the volume management information is read from the volume management information storage destination BN.
  • FIG. 11 is a configuration diagram of an apparatus according to a fifth embodiment of the present invention.
  • the same components as those in FIG. 7 are denoted by the same reference numerals.
  • the computer ID on the computer 11 ' is used without using the medium ID on the medium 1'.
  • the computer ID the computer 11 1 ′ is uniquely identified, such as the CPU ID, the ID assigned to dedicated hardware inserted in the expansion slot, etc. Any ID can be used.
  • the computer ID reading unit 19 stores the computer ID in the computer ID storage unit.
  • the computer ID read from c is input to the storage location determination unit 8 and is used to determine the storage location BN of the partition management information and the volume management information.
  • the storage destination BN determined by the storage destination determination unit 8 is input to the readable / writable area access unit 9 and sent to the readable / writable area access unit 12 of the drive device 4 ′′ together with an instruction to access the medium 1 ′.
  • the read / write area access unit 12 of the drive device 4 ′′ that has received the access instruction to the medium 1 ′ refers to the received storage destination BN, and writes the block indicated by the storage destination BN of the read / write area 3 ′ Partition management information ⁇ Volume Write the management information and end the logical format.
  • FIG. 12 is a flowchart showing a processing flow in the fifth embodiment.
  • the same steps as those in FIG. 3 are denoted by the same step numbers.
  • step S 1 ′′ the computer ID is read.
  • step S2 the BN of the partition management information storage destination is determined, and in step S3, the partition management information is stored.
  • the partition management information storage destination BN may be determined by adding a remainder obtained by dividing the computer ID by 64 to a predetermined value, Base 1, or by another method.
  • step S4 the BN for storing the volume management information is determined.
  • the BN is obtained by adding a remainder obtained by dividing the computer ID by 64 to a predetermined value Base2, but other methods may be used.
  • the volume management information is stored in the block having the determined storage destination BN on the medium 1 '(step S5), and the logical format is terminated.
  • FIG. 13 is a configuration diagram of an apparatus according to a sixth embodiment of the present invention.
  • the same components as those in FIGS. 9 and 11 are denoted by the same reference numerals.
  • the computer ID may be anything such as a CPU—ID or an ID provided in a dedicated hardware inserted in an expansion slot.
  • the request is received by the read / write area access unit 9 ′ of the file system 15 B.
  • the computer ID reading section 19 reads the computer ID from the computer ID storage section 18 and outputs it to the storage Z reading destination determining section 8 '.
  • the storage Z read destination determination unit 8 ′ uses a computer ID to identify the storage location of the partition management information and the policy management information on the medium 1 ′ by a predetermined method, and sends it to the readable / writable area access unit 9 ′. give.
  • the read / write area access section 9 ′ receives the input of the storage position and the medium use request from the application 16, and sends the medium 1 ′ to the read / write area access section 12 of the drive 4 ′.
  • FIG. 14 is a flowchart showing the flow of processing in the sixth embodiment.
  • the same steps as those in FIG. 5 are denoted by the same step numbers.
  • the computer ID is read in step S 10 ′ ′′.
  • the ID is set to 1 2 3 4 5.
  • step S 11 B in the storage destination of the partition management information Determine N.
  • the remainder of the computer ID divided by 64 is added to the predetermined value Base 1 to obtain the storage destination BN, but the present invention is not necessarily limited to this.
  • step S12 the partition management information is read.
  • step S13 the BN for storing the volume management information is determined.
  • the value obtained by adding the remainder obtained by dividing the computer ID by 64 to the predetermined value Base 2 is obtained, but is not necessarily limited to this.
  • the volume management information storage destination When the BN of the volume management information storage destination is specified, the volume management information is read from this storage destination on the medium 1 '(step S14). As a result, the data necessary for reading the data on the medium 1 'are prepared, so that data such as a file can be read or written in the same manner as a normal medium.
  • the data format of the medium 1 'in the third to sixth embodiments is the same as that shown in FIG.
  • FIG. 15 is a configuration diagram of an apparatus according to the seventh embodiment of the present invention.
  • an external ID is used without using a medium ID on a medium or an ID attached to another device to be used.
  • the external ID can be input to the computer 11 ', such as the ID given by the application, the ID given by the user, or the ID in the PC card inserted in the PC card slot, for example. Any ID will do.
  • the formatter 10C When formatting the medium 1 ′, the formatter 10C first obtains an external ID. This is read by the external ID reading unit 20. The read external ID is used for calculation in the storage destination determination unit 8. The storage destination determining unit 8 determines in which position of the readable / writable area 3 ′ on the medium 1 ′ the partition management information and the volume management information are to be written by a predetermined method using the external ID. Decision The stored storage destination is input to the readable / writable area access unit 9 and is passed as a part of the access instruction to the readable / writable area access unit 12 of the drive device 4 ".
  • the readable / writable area access unit of the drive device 4 '" 1 2 accesses the medium 1 ′ based on an access instruction from the readable / writable area access unit 9 of the formatter 10 C, and stores partition management information and volume management information in the determined storage position in the readable / writable area 3 ′. Write and terminate the logical format.
  • FIG. 16 is a configuration diagram of the device according to the eighth embodiment of the present invention.
  • This figure shows a case where the medium 1 'is accessed via the application 16 and the file system 15C in the seventh embodiment.
  • the medium use request of the application 16 is input to the read / write area access unit 9 'of the file system 15C.
  • the external ID is read by the external ID reading unit 20 as an output of another application or a manual input by the user.
  • the external ID is passed to the storage / readout destination determining unit 8 ', and the BN of the readable / writable area 3' in which the partition management information and the volume management information are stored is calculated.
  • the calculated BN is input to the readable / writable area access unit 9 '.
  • An instruction to access medium 1 ′ is output to access section 12.
  • the read / write area access unit 12 reads the partition management information and the partition management information stored in the read / write area 3 ′ on the medium 1 ′. Reads volume management information and reads and writes files.
  • the ID reading step is an external ID reading step.
  • FIG. 17 is a configuration diagram showing an apparatus according to a ninth embodiment of the present invention.
  • the storage position is determined by using both. Is what you want.
  • the external ID is read by the external ID reading unit 20. Then, the read external ID is input to the ID conversion unit 21.
  • the medium ID reading section 5 of the drive device 4 reads the medium ID 2 from the medium 1 and sends it to the medium ID reading section 7 of the formatter 10 ′ via the medium ID transfer section 6.
  • the medium ID reading unit 7 outputs the received medium ID 2 to the ID conversion unit 21.
  • the ID converter 21 combines the external ID and the medium ID 2 to generate a new code. For example, a new code with the external ID as the upper part of the code and the medium ID 2 as the lower part is generated.
  • This new code is sent to the storage destination determining unit 8, and the storage destination determining unit 8 determines the storage destination of the partition management information and the volume management information.
  • these storage destinations are input to the read / write area access unit 9 of the format 10D.
  • the readable / writable area access unit 9 outputs an access instruction including the storage destination information to the medium 1 to the readable / writable area access unit 12 of the drive device 4.
  • the read / write area access unit 12 of the drive device 4 accesses the read / write area 3 of the medium 1 and stores the partition management information and the volume in the storage destination determined by the storage destination determination unit 8. Stores management information. And Format the other partition and end the logical format.
  • FIG. 18 is a configuration diagram showing an apparatus according to a tenth embodiment of the present invention.
  • the medium 1 is accessed via the application 16 and the file system 15C instead of the formatter in the embodiment of FIG.
  • the readable / writable area access unit 9 waits for the input of the storage position of the partition management information and the volume management information from the storage Z read destination determination unit 8 '.
  • the medium ID reading unit 5 of the drive device 4 reads the medium ID 2 of the medium 1 and transmits the medium ID 2 to the medium ID reading unit 7 of the file system 15C via the medium ID transfer unit 6.
  • the medium ID reading unit 7 outputs this to the ID conversion unit 21.
  • the external ID reading section 20 receives the external ID and inputs the same to the ID conversion section 21 again.
  • the ID conversion unit 21 performs the same processing as that performed by the formatter 10D in the ninth embodiment on the medium ID 2 and the external ID, and generates a new code. For example, a new code is generated that has an external ID in the upper part of the code and a medium ID 2 in the lower part. This new code should be the same as used at the time of formatting. If the same code cannot be obtained, the medium 1 cannot be accessed.
  • the new code generated by the ID conversion unit 21 is input to the storage Z read destination determination unit 8 ', and the storage destination of the partition management information and the volume management information is determined.
  • the same method used for formatting is used in the storage Determine the storage destination using the same method. If the storage destination is obtained using a different method, the storage destination obtained at the time of formatting is not reproduced, and the medium 1 cannot be accessed. These things are the same also about the above-mentioned embodiment.
  • the storage destination determined by the storage / readout destination determination unit 8 ′ is input to the read / write area access unit 9 of the file system 15 C, and the medium access instruction is sent to the read / write area access unit 12 of the drive device 4.
  • Sent with The readable / writable area access unit 1 2 of the drive 4 accesses the readable / writable area 3 of the medium 1 based on the received storage destination and reads the partition management information and the volume management information, thereby enabling reading / writing of the medium 1 Writes a file to area 3 or reads a file.
  • FIG. 19 is a flowchart showing a processing flow according to the first embodiment of the present invention.
  • a selection unit for selecting one of a plurality of IDs is provided.
  • Other configurations are basically the same as those of the above-described first to eighth embodiments. Since the configuration can be realized with the same configuration, illustration and description of the device configuration are omitted.
  • step S20 information indicating the type of ID to be used is obtained from the application.
  • step S21 it is determined which ID is to be used based on the acquired information. If the medium ID is used, proceed to step S22 to read the medium ID.
  • step S23 the device ID.
  • the computer ID it is stored in the computer, for example, the ID of the processor or a dedicated board inserted in the expansion slot.
  • step S24 or step S25 one of the above IDs is read.
  • step S26 the storage destination of the partition management information BN is determined based on the read ID, and in step S27, the partition management information is stored in the storage destination on the medium.
  • step S28 based on the read ID, the storage location BN of the volume management information is determined.
  • step S29 the volume management information is stored in the storage location on the medium, and the logical format is set.
  • the BN of the storage location of the partition management information is obtained by adding the remainder obtained by dividing the read ID by 64 to 5 12, and the storage location of the volume management information is 5 13 The remainder is obtained by dividing the read ID by 64.
  • FIG. 20 is a flowchart showing a processing flow according to the 12th embodiment of the present invention.
  • step S20 information indicating which ID is to be used is obtained from the application, and in step S21, which ID is to be used is determined.
  • step S21 which ID is to be used is determined.
  • the process proceeds to step S22 to read the ID from the medium.
  • the device ID is read in step S23.
  • the selected ID is read out in step S24 or step S25.
  • step S26 the BN (position) of the storage location of the partition management information is determined (step S26), and in step S30, the partition management information is stored from the storage location on the medium.
  • step S28 the BN of the storage destination of the volume management information is determined based on the selected ID.
  • step S31 The volume management information is read from the storage destination on the medium.
  • the BN of the storage destination is determined by the same method as that used at the time of formatting.
  • FIG. 21 is a flowchart showing a processing flow according to the thirteenth embodiment of the present invention.
  • This embodiment is a diagram for explaining the operation of a tool for removing a fragment of a medium formatted in the format of the above embodiment.
  • the process for performing fragment disassembly is known as "defragmentation" included as a tool in, for example, Windows 95 or the like, which is a product of Microsoft Corporation, and thus a detailed description thereof will be omitted.
  • step S10 ID reading is performed.
  • the ID may be any of a medium ID stored in a medium, a device ID of a drive device, a computer ID given to a computer, or an external ID input from an application or a user. .
  • an arbitrary plurality of IDs may be selected and read.
  • the storage destination BN of the partition management information is determined from the read ID.
  • 5 1 2 is added to the remainder obtained by dividing the read ID by 64.
  • a plurality of read IDs may be combined to create a new code, and the storage location of the partition management information may be determined based on the new code.
  • the partition management information is read from the storage destination in step S12.
  • the BN for storing the volume management information is determined.
  • the volume management information is read from the storage destination with reference to the BN of the storage destination of the determined volume management information.
  • FIG. 22 is a diagram showing a configuration diagram of the device according to the fourteenth embodiment of the present invention.
  • the medium 1 has a non-rewritable medium ID 2 and a readable / writable area 3.
  • the drive device 4 includes a medium ID reading unit 5, a medium ID transfer unit 6, and a readable / writable area access unit 12.
  • the formatter 10 E operating on the computer 11 includes a medium ID reading unit 7, a management information encryption unit 30 that encrypts management information using the medium ID read by the medium ID reading unit 7 as a key, There is a readable / writable area access unit 9 for storing the encrypted management information.
  • the medium ID reading unit 5 of the drive device 4 reads the medium ID 2 of the medium 1 and outputs the medium ID 2 to the medium ID transfer unit 6.
  • the medium ID transfer unit 6 transmits the read medium ID to the medium ID reading unit 7 of the formatter 10E of the calculator 11.
  • the medium ID reading unit 7 outputs the received medium ID to the management information encryption Z storage destination determination unit 30.
  • the medium ID management information encryption Z storage destination determination unit 30 encrypts management information such as partition management information and volume management information using the input medium ID as a key, and calculates the storage destination BN of the management information. And outputs them to the readable / writable area access unit 9.
  • the above-mentioned encryption method may use a conventionally known DES (Data Encryption on Standard) or the like.
  • the encryption method is not particularly limited, and a code corresponding to the medium ID one-to-one is used. If you encrypt using It is not necessary to use the medium ID itself as a key.
  • the ID to be used is not limited to the medium ID, and it is also possible to use a computer ID, a drive device ID, or a combination thereof.
  • the storage location of the management information is movable by the medium ID, but the storage location of the management information may be fixed.
  • the root directory that encrypts only the management information, the management information included therein, and the file and the management information thereof may be encrypted together.
  • the root directory or file may or may not be encrypted using the media ID.
  • files are encrypted using a known encryption method, and the media ID is known to a third party. However, even when the medium 1 becomes accessible, the file may be kept confidential.
  • the readable / writable area access section 9 Upon receiving the management information storage location and the encrypted management information, the readable / writable area access section 9 transmits these to the readable / writable area access section 12 of the drive device 4 and reads / writes the read / write area of the medium 1. Record in 3. In this way, a more confidential logical format of the medium 1 can be performed.
  • FIG. 23 is a flowchart showing a processing flow in the fourteenth embodiment of the present invention.
  • the formatter 10E in FIG. 22 reads out the medium ID 2 from the medium 1 (step S40).
  • the partition management information is encrypted using the medium ID 2 as a key (step S41).
  • the storage location of the partition management information is obtained (step S42), and the encrypted partition management information is written to the storage location (step S43).
  • the volume management information is encrypted (step S44), the storage destination of the volume management information is obtained (step S45), and the encrypted management information is stored in the storage destination. (Step S46).
  • FIG. 24 is a configuration diagram showing a device configuration of the fifteenth embodiment of the present invention.
  • the medium formatted in the fourteenth embodiment is accessed, and file writing and reading are performed.
  • Medium 1 has a non-rewritable medium ID 2 and a read / write area 3.
  • the drive device 4 includes a medium ID reading unit 5, a medium ID transfer unit 6 that transfers the medium ID 2 read by the medium ID reading unit 5 to a computer, and a readable / writable area access unit 12.
  • the file system 15D on the computer 11 has a medium ID reading unit 7, a readable / writable area access unit 9, a management information decryption unit that decrypts the read management information using the medium ID 2 as a key, and a Z storage destination determination unit 30. There is. Further, the file system 15 D performs processing by inputting a medium use request from the application 16.
  • the medium use request from the application 16 is input to the readable / writable area access unit 9.
  • the medium ID 2 is read from the medium ID reading unit 5 of the drive device 4 and sent to the medium ID reading unit 7 included in the file system 15 D of the computer 11 by the medium ID transfer unit 6.
  • the medium ID reading unit 7 outputs the received medium ID 2 to the management information decryption data storage destination determination unit 30.
  • the management information decryption Z storage destination determination unit 30 determines the storage destination of the management information from the received medium ID 2 and gives the information to the readable / writable area access unit 9.
  • the readable / writable area access unit 9 issues a read command to the readable / writable area access unit 12 of the drive device 4 based on the received storage destination.
  • the encrypted management information read from the readable / writable area 3 of the medium 1 by the readable / writable area access unit 12 is decrypted into the management information via the readable / writable area access unit 9 of the file system 15D, and is stored in the Z.
  • the information is input to the destination determining unit 30 and decrypted by the management information 7 storage destination determining unit 30. Access to the medium 1 is performed based on the decrypted management information. It is.
  • the decoding process in the management information decoding Z storage destination determining unit 30 needs to correspond to the encoding process performed at the time of formatting in the 14th embodiment.
  • FIG. 25 is a flowchart showing the flow of processing in the fifteenth embodiment.
  • the file system 15 D in FIG. 24 starts mounting processing in response to a medium use request of the application 16. That is, first, the medium ID2 is read (step S40). Next, the storage location of the partition management information is obtained from the medium ID 2 (step S42), the partition management information is read from the storage location (step S50), and this is decrypted using the medium ID 2 as a key. (Step S51). Next, the storage location of the volume management information is obtained in the same manner as the partition management information (step S45), and the volume management information is read from the storage location (step S52). Decrypt (step S53).
  • the case where the storage location of the management information is determined, and the encryption and decryption are performed by reading the medium ID 2 has been described.
  • ID it is also possible to use the device ID of the drive device or the computer ID.
  • these read IDs do not have to be used as they are as encryption keys, and a plurality of IDs may be combined to generate a new code, which may be used for encryption and decryption.
  • a code corresponding to one or a plurality of IDs on a one-to-one basis may be prepared in advance, and this may be used for encryption / decryption, or may be used for determining a storage destination.
  • FIG. 26 shows an example of the encryption / decryption circuit in the fourteenth and fifteenth embodiments.
  • the encryption key used in the above encryption is input to each of the DES processing units 50-1 to 50-n.
  • the encryption key is, for example, the medium ID.
  • the encrypted data is input to the shaded portion in the figure, and is divided into 64 bits. Then, it is input to the DES processing units 50-1 to 50-n together with the encryption key. In this case, the decoding process is performed from the data E1 toward the data En. The decoded data M 1 output from the DE processing unit 50-1 is subtracted from the decoded data of E 2 output from the DE processing unit 50-2 in the exclusive OR circuit 51-1. Then, decryption data M2 is obtained.
  • FIG. 27 is a diagram showing a layout on the medium 1 logically formatted by the format 10E of the fourteenth embodiment.
  • the hatched portion is encrypted by the medium ID 2 in units of management information.
  • the management information is encrypted in the 14th embodiment, a specific area may be defined as a management information-dedicated area, and the entire area may be encrypted. This can be used when the management information storage destination is fixed.
  • the data in the section in which the root directory and the like are stored may be encrypted in the same manner as the management information.
  • By performing such encryption as described above it is possible to further enhance the confidentiality by performing encryption different from the encryption of the management information, the root directory, and the management information.
  • FIG. 28 is a diagram showing a configuration diagram of a drive device according to the sixteenth embodiment of the present invention.
  • the same components as those in FIG. 2 are denoted by the same reference numerals.
  • the computer 61 does not have to be a computer for personal or office use such as a so-called “personal computer” or “workstation”, but is mounted on a home appliance equipped with a microprocessor and flash memory for storing firmware. It may be something like a “computer for embedded devices”. Furthermore, a configuration using hardware that is connected and logically possible is also possible.
  • the drive device 60 includes a player dedicated to DVDs and music CDs, and the like. When the medium 1 is formatted, the medium ID reading unit 5 reads the medium ID 2 from the medium 1.
  • the medium ID transfer unit 6 transfers the medium ID to the medium ID reading unit 7 of the formatter 62 which operates on the computer 61 inside the drive device 60.
  • the medium ID reading unit 7 sends the received medium ID 2 to the storage destination determining unit 8.
  • the storage destination determining unit 8 determines the storage destination of the management information using the received medium ID 2, and This is transmitted to the readable / writable area access unit 9.
  • the readable / writable area access unit 9 issues an access instruction to the medium 1 to the readable / writable area access unit 12 of the drive device 60 based on the received storage destination information.
  • the read / write area access unit 12 having received the access instruction accesses the read / write area 3 of the medium 1 and stores the management information in the storage destination determined by the storage destination determination unit 8.
  • the method for determining the storage destination in the storage destination determining unit 8 is, for example, the method described in the first embodiment.
  • the ID to be used is not limited to the medium ID, and the device ID of the drive device 60 may be used.
  • the computer 61 incorporated in the drive device 60 may have an ID different from that of the drive device 60. If is attached, the computer ID may be used.
  • management information and the like may be stored after being encrypted.
  • the storage location of the management information can be a fixed position that does not depend on the read ID.
  • FIG. 29 is a configuration diagram of an apparatus according to a seventeenth embodiment of the present invention.
  • This embodiment corresponds to the sixteenth embodiment, and the meaning of the computer 61 and the drive device OA is as described above.
  • the computer 61 is a PC card having a microprocessor and a memory
  • all or a part of the functions of the drive device 60 can be executed on the PC card side. This is the same in the sixteenth embodiment.
  • the medium ID reading unit 5 of the drive device 60A reads the medium ID 2 of the medium 1 and transmits this to the medium ID transfer unit 6.
  • the medium ID transfer unit 6 inputs the received medium ID to the storage Z read destination determination unit 8 ′ via the medium ID read unit 7 included in the file system 63 of the computer 63.
  • Storage Z read destination determination unit 8 ′ determines the storage location of the management information from the received medium ID 2 and outputs it to the read / write area access unit 9 ′ of the file system 63.
  • the readable / writable area access unit 9 ′ issues an access instruction to the medium 1 to the readable / writable area access unit 12 of the drive unit 6 OA. put out.
  • the readable / writable area access unit 12 accesses the readable / writable area 3 of the medium 1, reads management information from the medium 1, and enables file access to the medium 1.
  • the ID to be used is not limited to the medium ID, and a device ID of the drive device 6OA and a computer ID of the computer 61 can be used. Also, encryption may be performed together as in the fourteenth and fifteenth embodiments.
  • the medium ID, the device ID, and the computer ID are used as the IDs.
  • the ID given to the application it is also possible to use the ID given to the application. . According to this, only the user who accesses the medium using a specific application can operate the contents of the medium.
  • FIG. 30 is a diagram illustrating a hardware configuration required when each of the above embodiments of the present invention is implemented by a program.
  • the CPU 71 exchanges data with other components via the bus 70, and executes a program for realizing each embodiment of the present invention.
  • the program is recorded on a ROM 73, an external recording device 77 such as a hard disk, or a portable recording medium 79.
  • the program stored in the portable recording medium 79 is read into the RAM 72 via the drive device 78 on which the portable recording medium 79 is mounted.
  • the program recorded in the ROM 73 or the external recording device 77 is directly read into the RAM 72.
  • CPU 71 is loaded into RAM 72 in an executable state. Execute the program.
  • the input of the ID from the user and the output of the processing result are performed by the input / output device 80.
  • the input / output device 80 includes a keyboard, a mouse, a display and the like.
  • the communication interface 74 accesses the information provider 76 via the network 75, downloads a program for realizing the embodiment of the present invention from the information provider 76 to the external recording device 77, etc. It is a network connection device that enables the CPU 71 to execute on a low-powered computer. Alternatively, the information provider 76 executes the program, and the communication interface 74 receives only the execution processing result from the information provider 76 via the network # 5. Embodiments of the invention can be implemented by remote access. Industrial applicability
  • the storage location of the management information on the medium By making the storage location of the management information on the medium movable based on information unique to the medium and the device used, even if all data on the medium is illegally copied to another medium, The storage location of the management information cannot be obtained from the information unique to the copy destination medium or device, and unauthorized access to the file can be prevented. A similar effect can be obtained by encrypting the management information using such unique information as a key.
  • the range in which a file stored on a medium can be correctly accessed can be limited according to the confidentiality level of the file.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Storage Device Security (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention porte sur une identification (2) de support non réécrivable enregistrée dans une zone spécifique d'un support (1), lue par la section de lecture ad hoc (5) d'une unité de disquette lors du formatage du support (1), puis transmise via à une section de transfert (6) à une section de lecture (7) inclue dans le dispositif de formatage (10) d'un ordinateur (11). L'identification du support est introduite dans une section de détermination de l'emplacement de stockage (8). En fonction de l'identification du support, on trouve par le calcul le numéro du bloc où s'inscriront, dans un format logique, les informations de gestion, dans une zone (3) de lecture/écriture du support (1). Le numéro du bloc est transmis à des sections d'accès (9, 12) de la zone de lecture/écriture, puis l'information de gestion est stockée dans l'emplacement déterminé de stockage de la zone (3) de lecture/écriture. On peut donc utiliser au lieu de l'identification du support, celle de l'unité de disquette (4) ou celle de l'ordinateur (11).
PCT/JP1999/002324 1999-04-30 1999-04-30 Systeme de gestion de fichiers Ceased WO2000067130A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2000615902A JP3866519B2 (ja) 1999-04-30 1999-04-30 ファイル管理システム
PCT/JP1999/002324 WO2000067130A1 (fr) 1999-04-30 1999-04-30 Systeme de gestion de fichiers

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP1999/002324 WO2000067130A1 (fr) 1999-04-30 1999-04-30 Systeme de gestion de fichiers

Publications (1)

Publication Number Publication Date
WO2000067130A1 true WO2000067130A1 (fr) 2000-11-09

Family

ID=14235610

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP1999/002324 Ceased WO2000067130A1 (fr) 1999-04-30 1999-04-30 Systeme de gestion de fichiers

Country Status (2)

Country Link
JP (1) JP3866519B2 (fr)
WO (1) WO2000067130A1 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006510958A (ja) * 2002-08-23 2006-03-30 イグジット−キューブ，インク． 暗号化オペレーティングシステム
US7035882B2 (en) 2002-08-01 2006-04-25 Hitachi, Ltd. Data storage system
US7237124B2 (en) 2002-01-18 2007-06-26 Victor Company Of Japan Limited Contents recorder/reproducer
JP2009080772A (ja) * 2007-09-27 2009-04-16 Toppan Printing Co Ltd ソフトウェア起動システム、ソフトウェア起動方法、及びソフトウェア起動プログラム
US7634447B2 (en) 2001-03-13 2009-12-15 Lg Electronics Inc. Method of recording and reproducing sample data to/from a recording medium and sample data containing recording medium
US8219823B2 (en) 2005-03-04 2012-07-10 Carter Ernst B System for and method of managing access to a system using combinations of user information
JP2012169983A (ja) * 2011-02-16 2012-09-06 Kddi Corp データ処理装置およびプログラム
US8984636B2 (en) 2005-07-29 2015-03-17 Bit9, Inc. Content extractor and analysis system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH01309120A (ja) * 1988-06-07 1989-12-13 Nec Corp 媒体保護制御方式
JPH04163768A (ja) * 1990-10-29 1992-06-09 Hitachi Ltd ディスク機密保護方式および装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH01309120A (ja) * 1988-06-07 1989-12-13 Nec Corp 媒体保護制御方式
JPH04163768A (ja) * 1990-10-29 1992-06-09 Hitachi Ltd ディスク機密保護方式および装置

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7634447B2 (en) 2001-03-13 2009-12-15 Lg Electronics Inc. Method of recording and reproducing sample data to/from a recording medium and sample data containing recording medium
US7237124B2 (en) 2002-01-18 2007-06-26 Victor Company Of Japan Limited Contents recorder/reproducer
US7035882B2 (en) 2002-08-01 2006-04-25 Hitachi, Ltd. Data storage system
US7415490B2 (en) 2002-08-01 2008-08-19 Hitachi, Ltd. Data storage system
JP4777651B2 (ja) * 2002-08-23 2011-09-21 イグジット−キューブ，インク． コンピュータシステム及びデータ保存方法
JP2006510958A (ja) * 2002-08-23 2006-03-30 イグジット−キューブ，インク． 暗号化オペレーティングシステム
US8407761B2 (en) 2002-08-23 2013-03-26 Exit-Cube, Inc. Encrypting operating system
US9098712B2 (en) 2002-08-23 2015-08-04 Exit-Cube (Hong Kong) Limited Encrypting operating system
US8219823B2 (en) 2005-03-04 2012-07-10 Carter Ernst B System for and method of managing access to a system using combinations of user information
US9449186B2 (en) 2005-03-04 2016-09-20 Encrypthentica Limited System for and method of managing access to a system using combinations of user information
US8984636B2 (en) 2005-07-29 2015-03-17 Bit9, Inc. Content extractor and analysis system
JP2009080772A (ja) * 2007-09-27 2009-04-16 Toppan Printing Co Ltd ソフトウェア起動システム、ソフトウェア起動方法、及びソフトウェア起動プログラム
JP2012169983A (ja) * 2011-02-16 2012-09-06 Kddi Corp データ処理装置およびプログラム

Also Published As

Publication number Publication date
JP3866519B2 (ja) 2007-01-10

Similar Documents

Publication Publication Date Title
US9767322B2 (en) Data transcription in a data storage device
JP4169822B2 (ja) 記憶媒体のデータ保護方法、その装置及びその記憶媒体
US8392727B2 (en) System and method for transparent disk encryption
JP3073590B2 (ja) 電子化データ保護システム、使用許諾者側装置および使用者側装置
JP4219681B2 (ja) 不揮発性メモリカード、コンパクトディスクまたはその他のメディアから記録されたオーディオ、ビデオまたはその他のコンテンツを再生するためのシステム、方法およびデバイス
WO2004051483A1 (fr) Dispositif et programme de transfert de licence
JP2004510367A (ja) 暗号化キーとしてのデータ塊アドレスによる保護
JPH0383132A (ja) ソフトウェア保護制御方式
JP2010237480A (ja) コンテンツ保護装置およびコンテンツ保護方法
JP4608931B2 (ja) 情報処理装置および方法、プログラム、並びに記録媒体
JP3866519B2 (ja) ファイル管理システム
JP2005505853A (ja) ユーザデータを読出し又は書込みするための装置及び方法
EP1770579A2 (fr) Procédé de transfert de données, appareil source de transfert de données, appareil de destination de transfert de données, support de stockage pour l'enregistrement d'un programme de transfert de données et support de stockage pour l'enregistrement d'un programme d'enregistrement de données transférées
JP2002334559A (ja) 情報記録媒体、情報管理装置および著作権保護方法
US20070283169A1 (en) Method for controlling file access on computer systems
KR100859651B1 (ko) 가변크기 데이터 저장을 위한 데이터구조를 기록한기록매체, 가변크기 데이터 저장방법, 및 가변크기 데이터저장방법을 컴퓨터에서 실행시키기 위한 프로그램을 기록한컴퓨터로 읽을 수 있는 기록매체
US9251382B2 (en) Mapping encrypted and decrypted data via key management system
JP4537772B2 (ja) ディスクシステム
JP3184189B2 (ja) 電子化データ保護システム、使用許諾者側装置、使用者側装置、使用許諾情報生成処理方法および電子化データ復号処理方法
JP2003345660A (ja) 情報処理装置、情報処理方法、およびコンテンツ入出力処理システム、コンテンツ入出力処理方法、並びにコンピュータ・プログラム
JP5539024B2 (ja) データ暗号化装置およびその制御方法
JPH10240517A (ja) ソフトウェアの複製防止方法及び装置
JP3184192B2 (ja) 電子化データ授受用記憶媒体
JP5759925B2 (ja) データ制御装置、データ制御方法、データ制御プログラム
JP3184191B2 (ja) 電子化データ保護システム、使用許諾者側装置、使用者側装置、使用許諾情報生成処理方法および電子化データ復号処理方法

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): CA CN JP KR US

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): DE FR GB IT NL

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
ENP Entry into the national phase

Ref country code: JP

Ref document number: 2000 615902

Kind code of ref document: A

Format of ref document f/p: F

122 Ep: pct application non-entry in european phase
点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载