EP1849054A1 - Data storage device - Google Patents
Data storage deviceInfo
- Publication number
- EP1849054A1 EP1849054A1 EP05807956A EP05807956A EP1849054A1 EP 1849054 A1 EP1849054 A1 EP 1849054A1 EP 05807956 A EP05807956 A EP 05807956A EP 05807956 A EP05807956 A EP 05807956A EP 1849054 A1 EP1849054 A1 EP 1849054A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- file
- type
- block
- memory
- storage device
- 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
Links
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
- G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
- G07F7/10—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means together with a coded signal, e.g. in the form of personal identification information, like personal identification number [PIN] or biometric data
- G07F7/1008—Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- G06F21/71—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information
- G06F21/77—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information in smart cards
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- G06F21/78—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure storage of data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/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; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/062—Securing storage systems
- G06F3/0622—Securing storage systems in relation to access
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
- G06F3/0661—Format or protocol conversion arrangements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0662—Virtualisation aspects
- G06F3/0664—Virtualisation aspects at device level, e.g. emulation of a storage device or system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0673—Single storage device
- G06F3/0679—Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/341—Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/351—Virtual cards
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/357—Cards having a plurality of specified features
- G06Q20/3576—Multiple memory zones on card
Definitions
- the present invention generally relates to the field of digital data storage systems.
- It relates more particularly to a data storage device comprising means for managing the security of the data contained in the device at the data file level.
- FIG. 1 thus illustrates the organization in memory of a storage device whose accesses are made through commands for reading and writing memory blocks, as seen from the host device, with according to this example , the information partition, the file allocation table, the root directory, the files 1, 2, 3, written in the different memory blocks referenced 1 to n.
- the result is the physical organization of data in memory, which allows the management and manipulation of files.
- the host device is then able to retrieve a file structure. More particularly, the operating system of the host device is in charge of managing the memory blocks thus formatted to allow applications to use a file system, for example presenting itself according to a logical tree structure where the files are stored hierarchical in a set of directories and subdirectories, as shown in Figure 2.
- the file system therefore hides the underlying physical organization of the memory used.
- Host devices, to build and organize such a file system thus access the memory through commands for reading and writing blocks. The consequence is that the storage device itself has no control over the access to the files in its memory, except to lock the access at the level of the blocks of the memory, without however having a relation with the files. .
- the management of access rights to the memory on this type of storage device is therefore carried out at the present time, at the level of all the blocks present or on a group of blocks with the necessity then to fragment the memory space into several groups of blocks having different access rights.
- the problem posed by such a management of the block type memory is that it does not allow the specificities to be taken into account.
- the type of memory in block management For example, it is known that flash memory cards support a limited number of erase / write cycles. Thus, it may be interesting to organize the file system taking into account this characteristic and thus avoiding storing information that can be frequently modified to a fixed place in the memory (case of the file allocation tables in FAT systems for example).
- flash Translation layer a software layer commonly called "Flash Translation layer". According to the English terminology, designed to virtualize the memory addresses of the memory blocks visible from outside the storage device in order to be able to store the information that can be frequently modified at different physical addresses with each write.
- Such storage devices are, however, limited in their use with host devices managing block access, as soon as possible. when it is desired to make them smarter, in particular by adding more advanced security features for the management of access rights to the data in their memory. Indeed, the management of access rights on this type of device can only be performed at the level of the blocks present in memory.
- reading and writing blocks since it allows a very fine and very flexible security control depending on the desired application. It is possible to provide as many different data access conditions as there are files in the storage device.
- the host device has no vision on the organization of the internal memory in the card and must have a suitable interface with the card, capable of implementing a file type access protocol for the card. access the data in the map.
- smart card type storage devices can not cooperate with host devices designed to manage block type memories.
- a storage device is structured for a block or type access system. file, but not for both.
- the purpose of the present invention is to reconcile the two types of memory management technology mentioned above, by proposing a storage device allowing access control to the data contained in memory at the file level, while being able to cooperate with a host device using a standard interface. according to a block type control format.
- the object of the invention is a data storage device comprising a memory space divided into memory blocks and means for managing an internal file system organizing said memory blocks for storing data in form. a file structure, said management means controlling the access to the data in the memory according to a file type control format, said device being characterized in that it comprises a protocol conversion interface between said management means file system and a host device comprising means for accessing the data in the memory of said storage device according to a block type control format.
- the protocol conversion interface comprises means for simulating, from the logical organization of the internal file system, a block - type memory image of the files accessible by said host device, said image being visible by said host device.
- the protocol conversion interface comprises means for transcribing block commands received from the host device into file type commands for the file system management means.
- the transcription means of the block type commands in file type commands comprise means for determining the type of block accessed among a system area, a file allocation table area or a file zone of the file system. internal.
- the protocol conversion interface comprises means for transmitting, on the one hand, the block type commands transcribed to the file system management means and, on the other hand, the corresponding block type responses to the file system management means. host device.
- the protocol conversion interface comprises means for constructing the block type responses according to access rights associated with the host device.
- the protocol conversion interface comprises means for modifying the data accessed by the host device as a function of the type of data accessed and / or access rights associated with the host device.
- the protocol conversion interface is in software form under the control of the file system management means.
- FIG 1 is a diagram illustrating the physical organization of data in a block-type memory and has already been described
- FIG. 2 is a diagram illustrating the logical organization of a file system and has already been described
- FIG. 3 is a diagram illustrating an exemplary architecture of a storage device according to the present invention cooperating with a host device.
- the aim of the invention is thus to coexist an internally provided file system manager of a memory card type data storage device with an external interface implementing a data access protocol based on control commands. reading and writing blocks.
- a storage device 10 comprises a memory space 20 typically divided into memory blocks for storing data.
- the storage device includes an operating system supporting a file system manager for organizing the storage blocks. memory and build a file system in memory according to a predefined structure, for example a file system type FAT 16 or FAT 32 ("File Allocation Table").
- FAT 16 or FAT 32 File Allocation Table
- the storage device With the file system manager 30, the storage device thus has its own file management means in-house, through which the device can control access to its files in memory and the access rights to the files. files, typically through "open file”, "read file” and "file write” commands.
- the management of the security of the data contained in the memory space 20 of the device is thus carried out at the level of the data files according to access rights which can be defined for each of them.
- Each file is thus associated with an access control list which stores the operations that third parties are authorized to execute on the file.
- a storage device 10 is provided to cooperate with a host device 40, in which it is for example inserted.
- the host device 40 includes its own operating system, supporting means 50 normally provided for formatting the storage space of a storage device with which it cooperates according to a defined arrangement, in order to set up a file system enabling to manage and manipulate data files in memory.
- An application 60 of the host device can then use this file system to manipulate data on the storage device.
- the setting up of a file system by the operating system of the host device 40 is based on a management of the memory blocks of the storage device.
- the host device is provided to see the storage space of the storage device as a set of blocks, as has been illustrated in FIG. 1 already described, with a view to using this memory to set up the storage device. file system through block type commands.
- the interface between the host device 20 and the storage device 10 thus implements a protocol 70 conventionally based on a block type control format for reading and writing data blocks in memory.
- Such a host device 40 should not be able to be used with the storage device 10 since it already manages its own file system, access to memory and control of data access must be performed at the file level data through file type command.
- the host device 40 does not support such a protocol.
- the storage device 10 then comprises, according to the invention, a protocol conversion interface 80, in the form of an additional software layer under the control of the software layer 30 in charge of the management of the protocol. internal file system to the storage device.
- the function of the conversion interface 80 is thus to produce an emulation of a block-type interface to host device 40 by simulating block-type access memory on the storage device, so that the storage device 10 having file-like accesses with the intended host device 40 can be used to manage block access.
- the protocol conversion interface 80 implemented in the storage device 10 thus makes it possible to simulate vis-à-vis the outside of the storage device and in particular for the host device where the storage device is inserted, an image in block memory of the files accessible by the host device, from the logical organization of the internal file system to the storage device and according to the access rights associated with the host device. Thus, only the files accessible by the host device according to its access rights will be visible by the host device in the form of memory blocks.
- the conversion interface 80 is then responsible for the transcription of the block commands received from the host device 40 into file type commands for the file management means internal to the storage device.
- the conversion interface 80 interprets the requests of the host device, which are in the form of block read / write commands, to transform them into commands for the internal file system, typically Open File / type commands. create file / read file / write file.
- the protocol conversion interface then optionally transmits a block response management means of the internal file system to the host device.
- the storage device can organize its file system taking into account the access rights associated with the host device and thus control access to the file level even when receiving block access commands.
- the storage device can also organize its file system taking into account the specificities of the type of memory used.
- the conversion interface 80 advantageously makes it possible to virtualize the addresses of the memory blocks visible from outside the storage device to store these blocks at different physical addresses each write. This aspect is particularly advantageous in the case of flash memory supporting a limited number of erase / write cycles.
- the exact implementation of the conversion interface 80 will depend on the type of file system that is to be simulated for the host device.
- the conversion interface 80 performs the following operations. On receipt of a read or write access request from a memory block received from the host device, it first determines the type of block accessed, namely whether this block belongs to a system area, to a file allocation table area or file area. To do this, the conversion interface 80 uses the information on the formatting of the memory 20 that it has via the internal file system manager 30, describing the correspondence between the memory addresses and the different zones of the memory. file system. Thus, from the address of the block accessed, the conversion interface deduces its type.
- the interface 80 will transmit a block response consisting of dynamically constructing a block of data to be sent back to the host device, or modifying it. internal file structure to reflect the change required by the host device.
- a block command received from the host device matches, according to the memory address of the block, to a data read command in the system area
- the conversion interface returns a constant block to the host device.
- a block write command corresponding to the write of data in the system area will be ignored by the conversion interface.
- the processing applied by the conversion interface then consists in constructing the data of the table from the list of internal files through file type commands sent to the internal file manager to access the corresponding data and send the table to the host device, then visible to it as a set of blocks.
- the table is further constructed from the access rights of the host device since some files may not be visible to the host device.
- a block write command received from the host device corresponding to the writing of the file allocation table will be transcribed by the conversion interface into file type commands to the internal file manager allowing an update.
- our internal file system file deletion, creation, modification).
- the conversion interface To respond to a block read command received from the host device corresponding to the reading of the actual data area of the file system, the conversion interface must determine which file is accessed from the block number and the file allocation table previously sent to the host device. The block read command is then transcribed by the interface of conversion to a read command of the relevant file portion in the internal file system of the storage device, and the interface returns the block corresponding to the host device, possibly modified according to access rights associated with the host device.
- a block write command received from the host device corresponding to the writing of the data area of the file system will be processed differently by the conversion interface depending on whether the block in question relates to a file already existing or was not allocated previously. If the data block concerns an already existing file, the conversion interface transcribes this block write command into a modification command of the internal file. If the data block was not allocated previously, however, the conversion interface transcribes the block command into a command to create a temporary file from the block. The temporary files will be re-assembled when the file allocation table is updated by the host device.
- the present invention thus allows file-level access rights management on storage devices with an internal file system that cooperate with host devices implementing accesses to the block-type memory.
- This ability to control access to memory and the use of this memory at the file level while maintaining compatibility with hosts managing block access opens many perspectives.
- an example of application of the present invention concerns the control of a storage device of the aforementioned type used by a third party.
- the third-party user might have the right to store data on the storage device, erase it, but he could only have access to a portion of the data only that he previously stored. Only the owner of the storage device with access rights will be able to recover all the stored data and may, for example, charge this service to the third party user of the storage device. Thanks to the format conversion interface provided in the storage device, this type of use is made possible without modifying the host device of the user of the storage device.
- the owner of the storage device could be a photographic printing service provider providing users with a memory card for storing their images.
- the user will insert this memory card into a digital camera type host device and will be able to use the memory to store his photos.
- each photo corresponds to a file, which can be processed and whose access can be controlled via the conversion interface implemented on the card.
- the user does not authenticate as being allowed to fully access these files, we can make sure that that the card allows access to the files for the host device only in a deliberately modified or degraded quality (reduction of format, addition of a banner on the image, etc.).
- the printing provider after authentication with the card, can recover the files in their full quality and print them for the user against payment.
- the present invention is intended to apply to all memory card formats, as long as the card manages its own file system internally.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Computer Hardware Design (AREA)
- Human Computer Interaction (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Microelectronics & Electronic Packaging (AREA)
- Software Systems (AREA)
- Accounting & Taxation (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Mathematical Physics (AREA)
- Databases & Information Systems (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Storage Device Security (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FR0500109A FR2880444B1 (en) | 2005-01-06 | 2005-01-06 | DATA STORAGE DEVICE |
PCT/EP2005/055972 WO2006072500A1 (en) | 2005-01-06 | 2005-11-15 | Data storage device |
Publications (1)
Publication Number | Publication Date |
---|---|
EP1849054A1 true EP1849054A1 (en) | 2007-10-31 |
Family
ID=34954319
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP05807956A Ceased EP1849054A1 (en) | 2005-01-06 | 2005-11-15 | Data storage device |
Country Status (5)
Country | Link |
---|---|
US (1) | US20080005531A1 (en) |
EP (1) | EP1849054A1 (en) |
JP (1) | JP4807683B2 (en) |
FR (1) | FR2880444B1 (en) |
WO (1) | WO2006072500A1 (en) |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4781033B2 (en) * | 2004-08-10 | 2011-09-28 | キヤノン株式会社 | Authentication system, processing method, program, and recording medium |
JP4575410B2 (en) * | 2007-08-29 | 2010-11-04 | 株式会社東芝 | Semiconductor memory device and operation method thereof |
US8943409B2 (en) * | 2008-12-26 | 2015-01-27 | Sandisk Il Ltd. | Storage device managing playable content |
US20100169395A1 (en) * | 2008-12-26 | 2010-07-01 | Sandisk Il Ltd. | Device and method for filtering a file system |
US8239395B2 (en) | 2008-12-26 | 2012-08-07 | Sandisk Il Ltd. | Storage device presenting to hosts only files compatible with a defined host capability |
US8166067B2 (en) * | 2008-12-26 | 2012-04-24 | Sandisk Il Ltd. | Method and apparatus for providing access to files based on user identity |
WO2011026530A1 (en) * | 2009-09-07 | 2011-03-10 | Tomtom International B.V. | Navigation apparatus and method of supporting hands-free voice communication |
MX2012004910A (en) * | 2009-10-26 | 2013-06-28 | Wearable Inc | Concurrent access to a memory pool shared between a block access device and a graph access device. |
US8321703B2 (en) | 2009-12-12 | 2012-11-27 | Microsoft Corporation | Power aware memory allocation |
DE102011106608A1 (en) * | 2011-06-16 | 2012-12-20 | Giesecke & Devrient Secure Flash Solutions Gmbh | Storage medium with access protection and method for operating such a storage medium |
TW201327161A (en) * | 2011-12-23 | 2013-07-01 | Ibm | Memory control method and computer system for performing the same |
TWI465814B (en) * | 2012-04-23 | 2014-12-21 | Au Optronics Corp | Liquid crystal display panel |
US10169149B2 (en) * | 2016-09-06 | 2019-01-01 | International Business Machines Corporation | Standard and non-standard dispersed storage network data access |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3609739B2 (en) * | 1991-11-26 | 2005-01-12 | 株式会社日立製作所 | Semiconductor memory device |
JPH07141479A (en) * | 1993-11-18 | 1995-06-02 | Toshiba Corp | Ic memory card and file control system using ic memory card |
JP3233079B2 (en) * | 1997-09-30 | 2001-11-26 | ソニー株式会社 | Data processing system and data processing method |
US6393517B1 (en) * | 1999-08-31 | 2002-05-21 | Sony Corporation | SCSI port filter driver for enhanced audio data |
EP1100001B1 (en) * | 1999-10-25 | 2003-08-13 | Sun Microsystems, Inc. | Storage system supporting file-level and block-level accesses |
WO2001041058A1 (en) * | 1999-11-30 | 2001-06-07 | Kabushiki Kaisha Toshiba | Ic card and method for managing volatile memory of the ic card |
JP2001282596A (en) * | 2000-03-30 | 2001-10-12 | Sony Corp | Method and device for managing file |
US6868417B2 (en) * | 2000-12-18 | 2005-03-15 | Spinnaker Networks, Inc. | Mechanism for handling file level and block level remote file accesses using the same server |
US6779063B2 (en) * | 2001-04-09 | 2004-08-17 | Hitachi, Ltd. | Direct access storage system having plural interfaces which permit receipt of block and file I/O requests |
US7873700B2 (en) * | 2002-08-09 | 2011-01-18 | Netapp, Inc. | Multi-protocol storage appliance that provides integrated support for file and block access protocols |
JP2004220216A (en) * | 2003-01-14 | 2004-08-05 | Hitachi Ltd | San/nas integrated storage device |
US7549044B2 (en) * | 2003-10-28 | 2009-06-16 | Dphi Acquisitions, Inc. | Block-level storage device with content security |
JP4146380B2 (en) * | 2004-03-29 | 2008-09-10 | 東芝ソリューション株式会社 | Storage system, block rearrangement control method, and program |
JP4943081B2 (en) * | 2006-07-27 | 2012-05-30 | 株式会社日立製作所 | File storage control device and method |
JP2008152695A (en) * | 2006-12-20 | 2008-07-03 | Hitachi Ltd | Storage controller for protecting object for protection by protection capability required of electronic object for protection |
-
2005
- 2005-01-06 FR FR0500109A patent/FR2880444B1/en not_active Expired - Fee Related
- 2005-11-15 EP EP05807956A patent/EP1849054A1/en not_active Ceased
- 2005-11-15 WO PCT/EP2005/055972 patent/WO2006072500A1/en active Application Filing
- 2005-11-15 US US11/794,815 patent/US20080005531A1/en not_active Abandoned
- 2005-11-15 JP JP2007549836A patent/JP4807683B2/en not_active Expired - Fee Related
Non-Patent Citations (1)
Title |
---|
See references of WO2006072500A1 * |
Also Published As
Publication number | Publication date |
---|---|
JP4807683B2 (en) | 2011-11-02 |
WO2006072500A1 (en) | 2006-07-13 |
FR2880444B1 (en) | 2007-03-09 |
FR2880444A1 (en) | 2006-07-07 |
US20080005531A1 (en) | 2008-01-03 |
JP2008527511A (en) | 2008-07-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1849054A1 (en) | Data storage device | |
EP1151384B1 (en) | Storage system comprising means managing a storage unit with anti-wear and anti-wear management of a storage unit | |
CN105431838B (en) | Streamed content and placeholder | |
US8239395B2 (en) | Storage device presenting to hosts only files compatible with a defined host capability | |
US7533133B1 (en) | Externally managed file versions | |
CN101535966A (en) | Reverse name mappings in restricted namespace environments | |
EP1977365B1 (en) | Electronic document management method | |
EP2102768A1 (en) | Method and device for managing data in a distributed environment | |
US8498622B2 (en) | Data processing system with synchronization policy | |
EP2413233B1 (en) | Android phone with an application for content display | |
CN112597102B (en) | High-efficiency mirror image file system implementation method | |
EP1728164B1 (en) | Method for the software emulation of the hard disks of a computer platform at the operating system thereof, with on-the-fly parameter-adaptive management of read and write requests | |
EP2531921B1 (en) | Management of location of stored data in a distributed storage system | |
EP3588337A1 (en) | Control of a data storage device | |
EP3903210A1 (en) | Secure, tracked communication network | |
EP0956540A1 (en) | Security access control system enabling automatic invalidation of stolen or lost electronic keys and/or transfer of authorisation to make keys | |
EP2304559B1 (en) | Method for swapping between two versions of a same application within an information processing device, and said device | |
US20050177571A1 (en) | Systems, methods, and computer-readable mediums for accessing local and remote files | |
EP3411821B1 (en) | Method for storing content, method for consulting content, method for managing content and content readers | |
WO2007104649A1 (en) | Method of operating and managing unrestricted memory in a rewritable non-volatile memory, and associated memory | |
FR2911203A1 (en) | Runtime environment managing method for e.g. personal computer, involves detecting computing event related to insertion or withdrawal of media on thin client and server of network, before initialization of runtime environment of client | |
EP2302518B1 (en) | Method and apparatus for installation of a MIFARE applicaton in a MIFARE memory | |
FR2901386A1 (en) | Magnetic/optical/electronic/electro-optic type personal external storage medium e.g. universal serial bus key, for use in computer system, has processing module including sub-module creating cache file and accessing to cache file | |
WO2007082900A1 (en) | Portable electronic device suitable for providing a dynamic content | |
FR2933790A1 (en) | MANAGEMENT OF A PHYSICAL MEMORY PARTITIONED IN AN ELECTRONIC ENTITY: METHOD AND DEVICE. |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20070806 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR |
|
17Q | First examination report despatched |
Effective date: 20080111 |
|
DAX | Request for extension of the european patent (deleted) | ||
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: GEMALTO SA |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R003 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED |
|
18R | Application refused |
Effective date: 20131107 |