EP3518112A1 - Speichervorrichtung und host-vorrichtung - Google Patents

Speichervorrichtung und host-vorrichtung Download PDF

Info

Publication number
EP3518112A1
EP3518112A1 EP19160700.1A EP19160700A EP3518112A1 EP 3518112 A1 EP3518112 A1 EP 3518112A1 EP 19160700 A EP19160700 A EP 19160700A EP 3518112 A1 EP3518112 A1 EP 3518112A1
Authority
EP
European Patent Office
Prior art keywords
area
data
write
command
file
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.)
Granted
Application number
EP19160700.1A
Other languages
English (en)
French (fr)
Other versions
EP3518112B1 (de
Inventor
Akihisa Fujimoto
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.)
Kioxia Corp
Original Assignee
Toshiba Memory Corp
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 Toshiba Memory Corp filed Critical Toshiba Memory Corp
Publication of EP3518112A1 publication Critical patent/EP3518112A1/de
Application granted granted Critical
Publication of EP3518112B1 publication Critical patent/EP3518112B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/0608—Saving storage space on storage systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
    • G06F12/023—Free address space management
    • G06F12/0238—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory
    • G06F12/0246—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory in block erasable memory, e.g. flash memory
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
    • G06F13/4204—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus
    • G06F13/4234—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus being a memory bus
    • 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/0658—Controller construction 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/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
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/10—Providing a specific technical effect
    • G06F2212/1016—Performance improvement
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/10—Providing a specific technical effect
    • G06F2212/1041—Resource optimization
    • G06F2212/1044—Space efficiency improvement
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/17—Embedded application
    • G06F2212/177—Smart card
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/72—Details relating to flash memory management
    • G06F2212/7202—Allocation control and policies

Definitions

  • Embodiments described herein relate generally to a memory device and a host device.
  • Memory devices such as an SDTM card are classified into a plurality of classes to facilitate matching between the performance of a memory device and that required by a host device.
  • a speed class provides a method of classifying the performance of memory devices by speed class numbers and calculating the performance of the memory devices.
  • the speed class controls the write procedure using specific commands.
  • sequential write is performed in an allocation unit (to be referred to as an AU or sequential write area hereinafter) that is the physical memory area of a memory device.
  • Data needs to be written from the start of an allocation unit. For this reason, an allocation unit in which data has been written partway cannot be used for data recording. Therefore, it is desired to provide memory device and host device capable of using an allocation unit in which data has been written partway and improving the utilization efficiency of allocation units.
  • a memory device includes a nonvolatile semiconductor memory and a control unit.
  • the nonvolatile semiconductor memory has a plurality of physical storage areas that includes a user area externally accessible and is divided into plurality of management units.
  • the control unit is configured to control the nonvolatile semiconductor memory.
  • the control unit receives a control command having a first argument to designate a sequential write area and a read command or a write command, assigns a management unit represented by an address of the read command or the write command as the sequential write area, and changes memory access control by judging whether an address of a memory access command to access the user area indicates access in the sequential write area whose size is equivalent to the management unit.
  • FIG. 1 schematically showing a memory system according to the embodiment.
  • the memory system includes a memory device 11 (to be also referred to as a card hereinafter) such as an SD card, and a host device 20.
  • a memory device 11 such as an SD card
  • SD card Secure Digital Card
  • the host device 20 and the memory device 11 are connected by SD Bus Interface 26 to communicate using commands.
  • the memory device 11 can indicate busy to host through SD Bus Interface. Busy indication means that card is executing something and prevents host from issuing a next command.
  • the memory device 11 When connected to the host device 20, the memory device 11 receives power and operates to perform processing corresponding to access from the host device 20.
  • the memory device 11 includes a controller 11a.
  • the controller 11a includes, for example, a host interface (I/F) 12, a CPU 13, a read only memory (ROM) 14, a random access memory (RAM) 15 serving as a volatile memory, a buffer 16, and a memory interface (I/F) 17. These are connected by a bus.
  • the memory interface 17 is connected to, for example, a NAND flash memory 18 and an I/O 19 serving as an extension function unit.
  • a wireless LAN device or the like can be applied to the extension function unit.
  • the host interface 12 performs interface processing between the controller 11a and the host device 20.
  • the host interface 12 includes a register 12a.
  • the register 12a stores data unique to the memory device 11 such as the size of an AU to be described later.
  • the register 12a also stores status during execution. Default setting is read out from the NAND flash memory 18 and set in the register 12a at the time of power-on.
  • the contents of the register 12a are read out by a command, for example, the status can be read by CMD13 issued by the host device 20.
  • the memory interface 17 performs interface processing between the controller 11a and the NAND flash memory 18 or I/O 19.
  • Data of the host interface 12, the RAM 15, the buffer 16, and the like can be transferred not only by data transfer of the CPU 13 but also by DMA transfer of hardware.
  • the CPU 13 controls the operation of the entire memory device 11.
  • the CPU 13 loads firmware (control program or the like) stored in the ROM 14 or firmware recorded in the NAND flash memory 18 onto the RAM 15 and executes predetermined processing. That is, the CPU 13 creates various kinds of tables and, for example, an extended register on the RAM 15 and, upon receiving a write command, a read command, or an erase command from the host device 20, accesses an area on the NAND flash memory 18 or controls data transfer processing via the buffer 16.
  • the ROM 14 stores firmware such as a control program to be used by the CPU 13. Some pieces of firmware may be implemented in the ROM 14, whereas the remaining pieces of firmware may be stored in the NAND flash memory 18, extracted to the RAM 15, and executed.
  • the RAM 15 is used as the work area of the CPU 13, and stores control programs, various kinds of tables, and extended registers.
  • the buffer 16 temporarily stores a predetermined amount of data (for example, data of one page) when data sent from the host device 20 is to be written in the NAND flash memory 18, or temporarily stores a predetermined amount of data when data read out from the NAND flash memory 18 is to be sent to the host device 20. Intervening the buffer 16 enables asynchronous control of an SD bus interface and a back end.
  • the NAND flash memory 18 includes memory cells having, for example, a stacked gate structure or memory cells having a MONOS structure.
  • the I/O 19 has the function of a peripheral device or an interface for a digital camera, a PHS, or the like.
  • a wireless LAN device is applied as the I/O 19
  • even a digital camera having no wireless communication function can perform wireless data communication with an external server or an external PC (Personal Computer).
  • the host device 20 for example, a digital camera, a PHS, or the like is applicable.
  • the host device 20 includes a host controller 21, a CPU 22, a ROM 23, a RAM 24, and, for example, a hard disk 25 (including an SSD). These are connected by a bus.
  • the CPU 22 controls the entire host device 20.
  • the ROM 23 stores firmware necessary for the operation of the CPU 22.
  • Firmware read out from a storage device e.g., HDD 25
  • the RAM 24 is used as, for example, the work area of the CPU 22.
  • Programs executable by the CPU 22 are also loaded and executed here.
  • the hard disk (HDD) 25 holds various kinds of data.
  • the host controller 21 performs interface processing for the memory device 11 in a state in which the memory device 11 is connected.
  • the host controller 21 also issues various kinds of commands to be described later in accordance with an instruction from the CPU 22.
  • the host device 20 has the memory management software which is configured to recognize a file system that formats a user area of NAND flash memory 18, stored in the hard disk 25, for example.
  • the memory management software determines whether to write data in a sequential write area or an overwrite area, based on the extension of the file name or a data length of a file which will be created.
  • FIG. 2 shows the management unit of a user area 18a usable by the user out of the areas of the NAND flash memory 18.
  • the size of each of AU1 to AUn is determined based on the physical boundaries of the NAND flash memory 18 (the boundaries are not equivalent to those managed by the file system in the user area). Multiplying the AU size by n (integer) yields the whole memory capacity of the user area 18a.
  • the information of the file system such as a file allocation table (FAT) is normally recorded in AU1 at the start. For this reason, write performance for AU1 is not guaranteed.
  • AU2 to AUn are recording areas of guaranteed performance, and are indicated as recordable areas. However, AUs to record directory entry or overwrite are excluded from performance guarantee. If the AU size is small, and the information of the file system is recorded in, for example, AU1 to AUp, AU(p+1) to AUn are recording areas of guaranteed performance.
  • each AU is divided into a plurality of recording units (to be referred to as RUs hereinafter).
  • Performance is guaranteed for sequential write of continuously writing data whose address is on RU boundary and data length is at least equal to or more than the RU size. For this reason, the host device 20 needs to execute multi-block write in a unit corresponding to an integer multiple of the RU. This is because certain data length is needed to make the effect of the pipeline operation in the card appear in the performance.
  • FIG. 2 indicates that one AU is formed from m RUs.
  • S RU be the size of the RU
  • S AU be the size of the AU
  • the number m of RUs in one AU N RU is given by S AU /S RU .
  • the worst value of average performance when sequential write is performed for an arbitrary AU is represented by a write performance information Pw of the memory device.
  • Pw is defined as the worst value of average performance of 4-MB areas obtained by dividing the AU into 4-MB areas.
  • the host device 20 can read out Pw and the AU size S AU from, for example, the register 12a of the memory device and use them for performance calculation.
  • RU size is defined as a fixed value.
  • the minimum average performance of sequential write for an area represented by an AU address and an AU size can be estimated from Pw. Since the values of Pw and AU size change between devices, the host device 20 needs to cope with this by reading out the Pw and AU size from the register 12a of the memory device.
  • the write performance of each file can be adjusted by adjusting the data write amount in the 1-sec time slot.
  • they are divisionally written as 3-MB data each in the 1-sec time slot.
  • the remaining 100 ms of the time slot can be assigned to part of time to update the FAT as a margin necessary for control on the host device side. That is, the host device can calculate and control the write performance of a plurality of files by determining the number of time slots to be assigned and time-divisionally performing write.
  • FIG. 3 shows an example of multi-file recording for the user area 18a of the NAND flash memory 18.
  • the overwrite area (OverW-Area) is assigned by a command (CMD20) "Set Over-Write Area” to be described later.
  • An area (to be referred to as a sequential write area hereinafter) to perform sequential write is assigned by a CMD20 "Set Sequential-Write AU”.
  • One sequential write area can be assigned by the CMD20 "Set Sequential-Write AU".
  • the host device 20 can divisionally write a plurality of files in the sequential write area.
  • three file entries FE1, FE2, and FE3 are created in a directory entry DIR1 of the overwrite area (OverW-Area), and a file entry FE4 is created in a directory entry DIR2.
  • File 1a is part of File 1 and is written on the RU basis while being made to match the RU boundary. For this reason, at least the performance Pw is guaranteed when writing File 1a.
  • Each of File 2 and File 3 has a size equal to or smaller than the RU and is written in a data size smaller than the RU.
  • the data exist on, for example, 64-KB boundaries smaller than the RU boundary.
  • File 4 needs to be written while guaranteeing at least the performance Pw
  • first, dummy data is written up to the RU boundary as Padding following File 3. Padding may be done by host or done by card.
  • File 4 is written while being made to match the RU boundary. That is, since the data of File 4 is written on the RU basis while being made to match the RU boundary, the performance Pw is guaranteed.
  • File 1b that is the rest of File 1 is written next to File 4.
  • File 1b is written on the RU basis while being made to match the RU boundary, at least the performance Pw is guaranteed. That is, the host device 20 manages the write performance of File 1 and File 4 by dividing them to a multiple of RU unit.
  • FAT update is executed to close File 1.
  • a FAT area and bitmap (not shown) are updated, and 512 bytes including the file entry 1 (FE1) in the DIR area are updated, thereby determining the write data partway through File 1 as the file system.
  • the host can thus read out data up to the written data of File 1 from the file system information.
  • FIG. 4 shows an example of the format of the command CMD20 applied to this embodiment.
  • S is the start bit of the command
  • T is a bit representing the transfer direction
  • index indicates the command number, which has a bit string to specify that the command is a control command such as sequential write.
  • SCC is an argument representing speed class control, which is an operation designation portion for designating the function or operation of the command.
  • SCC is formed from a plurality of bits, and the bits of "SCC” set various functions of the CMD20.
  • CRC7 indicates a cyclic redundancy check code
  • the bits of "SCC” set, for example, “Start Recording”, “Update DIR”, “Update CI”, “Set Sequential-Write AU”, “Set Over-Write Area”, “Set Top of Data Area”, and “Arrange Area”.
  • the CMD20 "Set Sequential-Write AU” is a command to assign the sequential write area. This CMD20 "Set Sequential-Write AU” is used in combination with the read command or write command, as will be described later.
  • a busy time of, for example, 1 sec is allowed as the processing time of the command.
  • the allowed busy time is suppressed to, for example, 10 ms.
  • the CMD20 "Set Over-Write Area” is a command to set the overwrite area.
  • the overwrite area is designated using the CMD20 "Set Over-Write Area” in combination with the read command or write command, and an address.
  • a busy period of, for example, 100 ms is set in the CMD20 "Set Over-Write Area”.
  • the overwrite area cannot be assigned in the sequential write area.
  • memory access control can be, for example, control of the busy time representing that the write command is being processed, control to maintain data in unwritten areas, or cache control (a method of writing data in the buffer and arranging the data written the buffer and writing it in the flash memory later, instead of directly writing the data in the NAND flash memory).
  • cache control a method of writing data in the buffer and arranging the data written the buffer and writing it in the flash memory later, instead of directly writing the data in the NAND flash memory.
  • write performance is estimated by an average of busy time.
  • a CMD20 "Set Top of Data Area” is a command to notify the card of the data area of the file system in combination with the read command.
  • the card need not analyze the file system, and can predict the position of the DIR area and bitmap.
  • the start address of the data area is designated by the CMD20 "Set Top of Data Area” and the read command.
  • a busy period of, for example, 100 ms is set in the CMD20 "Set Top of Data Area”.
  • a CMD20 "Arrange Area” is a command to permit the memory device 11 to prepare an area within a specific time, and represents completion of preparation by canceling busy of the CMD20.
  • the CMD20 "Arrange Area” is solely used, unlike the other functions of the CMD20.
  • a busy time of, for example, 1 sec is allowed and when the CMD 20 "Arrange Area” is used in data recording, the allowed busy time is suppressed to, for example, 250 ms.
  • a memory device supporting the CMD20 of this embodiment can receive a conventional command and convert its interpretation into the command of this embodiment. This makes it possible to maintain the compatibility to some extent.
  • a CMD20 "Start Recording" is a command to designate the sequential write area first. This "Start Recording" can directly be handled as "Set Sequential-Write AU”. This CMD20 can indicate a busy of 1 sec.
  • Update DIR is issued before the CMD24/25 that updates a 512-byte area that is part of the directory entry.
  • the overwrite area is not assigned as the overwrite area, at least an area including the 512-byte area from the address represented by the CMD24/25 is assigned as the overwrite area.
  • Update CI is used to write small CI (Continuation Information) data during the write of stream data such as video data.
  • "Update CI” is issued before the CMD24/25 to write part of CI data, for example, 512-byte data.
  • the next "Update CI" is written in the next 512-byte area at a high possibility.
  • a relatively large area is preferably allocated.
  • the overwrite area is not assigned as the overwrite area, at least an area including the 512-byte area from the address represented by the CMD24/25 is assigned as the overwrite area.
  • this CMD20 need not perform any processing.
  • an AU that has been used partway can be assigned as a sequential write area at the time of initialization.
  • the AU utilization efficiency can be improved.
  • the card Since area management of memory card is managed by the host device 20, the card needs not hold assigned information when card is powered off. According to this method, after power is supplied to the card, the host device 20 can re-designate areas equivalent to those before power off.
  • the sequential write area is valid until one AU has completely been written.
  • the assigned AU as the sequential write area can continue sequential write even the random writes to another area are inserted. For this reason, additional write can be performed in the free area of the sequential write area, and the AU utilization efficiency can be improved.
  • a command format to allocate the sequential write area SeqW-AU is as follows.
  • One sequential write area SeqW-AU is designated by this command format.
  • CMDxx is one of two different commands, for example, a read command (CMD17) and a multi-block write command (CMD25), and the address of CMDxx indicates the start or a midpoint of an AU. As a result, four designation methods are available.
  • the AU When reading out a 512 byte area from the start address of an AU by the CMD17, the AU is assigned as the sequential write area. Data is written from the start of the sequential write area. Read data should be discarded due to it is meaningless.
  • the AU When reading out a 512-byte area from a middle address of an AU by the CMD17, the AU is assigned as the sequential write area. Data is written from the designated address. Data recorded in the area before the designated address is preserved. Read data should be discarded due to it is meaningless.
  • the AU When writing data from the start address of an AU by the CMD25, the AU is assigned as the sequential write area. Data is written from the start of the AU, and subsequent data is written from the address immediately after the written data.
  • the AU When writing data from a middle address of an AU by the CMD25, the AU is assigned as the sequential write area. Data is written from the designated middle address of the AU, and subsequent data is written from the address immediately after the written data. Data recorded in the area before the designated address is preserved.
  • assignment of the sequential write area can be either held or canceled. Assignment is canceled even upon judging that write in the sequential write area is not sequential (overwrite has occurred). Assignment is also canceled if host assigns another area sequential write area.
  • the CMD20 "Set Over-Write Area” is a command to set an overwrite area. Random write data may be temporarily saved in the cache. However, since the whole user area can be subjected to random write, occurrence of cache flash may make the processing time very long. For this reason, the memory device 11 indicates long busy, and a phenomenon called "a petit freeze” may occur. In particular, the larger the block size (the physical data length serving as the base in determining the AU size) of the flash memory is, the longer the busy time tends to be because of the wide area to manage data. This poses an especially serious problem in a flash memory having a large block.
  • the area of overwrite is designated. This makes it possible to reduce the influence of cache flash and, even in the worst case, estimate the processing time short, and prevent the card from indicating long busy.
  • a plurality of overwrite areas can be assigned.
  • the busy time is predetermined, and time required for assignment is ensured.
  • the overwrite area is designated using the CMD20 + read/write command and an address.
  • the following two methods are usable.
  • the method (1) (described as the argument OWAS of the CMD20) is effective when designating large areas together as an overwrite area.
  • OWAS the argument of the CMD20
  • the method (2) is effective.
  • the write command may indicate a long busy.
  • the maximum busy time is set to 500 ms for the undesignated area with respect to the maximum busy time of 250 ms for the overwrite area.
  • the cache control method for the overwrite area and that for the undesignated area are different.
  • the memory device changes memory access control, for example, cache control to control different from that for areas other than the overwrite area. That is, the host device therefore designates the sequential write area and the overwrite area and performs write in the area. This allows the memory device to do efficient processing and improve total performance.
  • a command format to allocate the overwrite area is as follows.
  • One overwrite area is designated by this format.
  • the card can assign eight overwrite areas at maximum. When eight or more overwrite areas are designated, the latest eight areas are valid as overwrite areas.
  • CMDxx is, for example, a multi-block read command CMD18 or a multi-block write command CMD25, and there are two different designation methods (the command may be a single write command CMD24 or a single read command CMD17).
  • a method of designating the size by the argument of the CMD20 to be described later or a method of designating the size by the area accessed by CMDxx is usable.
  • the overwrite area is designated by a set value represented by the argument OWAS of the CMD20 or a data length written by the CMD25. In the designated overwrite area, data in an area other than the written area is preserved.
  • the overwrite area is designated by a set value represented by the argument OWAS of the CMD20 or a data length read by the CMD18. Data in the designated overwrite area is preserved.
  • assignment of the overwrite area can be either held or canceled.
  • the CMD20 "Set Top of Data Area” is a command to notify the card of the data area of the file system.
  • the host device 20 notifies the card of the start position of the data area representing the format of the file system.
  • the card can thus specify the bitmap area and FAT area of exFAT (extended FAT).
  • the host device 20 can read out a bitmap to the RAM 24 using a read command following the CMD20 "Set Top of Data Area” and form cache of the bitmap in RAM 24.
  • a recording area is defined by the write command. Hence, preparation of the recording area cannot be done without starting recording.
  • the recording area is designated by the address of the read command, thereby enabling preparation.
  • one area can be assigned as the sequential write area, and a plurality of areas can be assigned as the overwrite areas.
  • the host device 20 issues a command to permit the memory device 11 to prepare an area.
  • the memory device 11 indicates busy during the preparation according to the command, thereby notifying the host device 20 that preparation is progressing.
  • FIG. 7 shows the memory map of the NAND flash memory 18.
  • the user area 18a of the NAND flash memory 18 includes a file system area including a FAT before the start position of the data area, and includes a bitmap area within the first 4-MB area of the data area.
  • the host device 20 searches for the start address of the data area from the file system format of the memory device 11, and designates the start address of the data area by the CMD20 "Set Top of Data Area" + CMD18.
  • the memory device 11 can predict the position of directory information recorded in the file system area and the position of bitmap information within the first 4-MB area of the data area from the address designated by the CMD18.
  • the host device 20 is not necessary to set these areas as an overwrite area but can be set these areas as an overwrite area in accordance with a simpler procedure of Set Top of Data Area. These areas are not included in the count of Overwrite Area assignment.
  • Areas to be used are distinguished by the type of data and the data length. That is, the data length of a file can be predicted by the extension of the file name or file attribute. For example, a video file can be handled as long data, and a text file can be handled as short data assumed to be rewritten.
  • the extension of the file name or file attribute can be used as a means for predicting the data length or whether to overwrite even when the data length is indefinite.
  • Data associated with the file system for example, a FAT, bitmap, or directory entry can be handled as short data and is recorded in the overwrite area.
  • Rewritable short data is recorded in the overwrite area, and rewritable long data is recorded in the sequential write area.
  • the minimum unit of the sequential write area is set to 64 Kbytes (determined by the page size), and data smaller than 64 Kbytes is handled as short data.
  • the sequential write of short data is not limited to the RU basis (data size is multiple of RU Size and address is on RU boundary).
  • the performance When data is written in the RU basis, the performance is equal or higher than Pw. Although data can also be written in a unit smaller than the RU, the performance becomes lower than Pw. "Pw becomes lower" means that the busy time indicated by the memory device becomes longer.
  • the memory device For write in the sequential write area, the memory device confirms whether the address is sequential and whether the write data exists on the RU boundary, and controls the busy time depending on whether the conditions to yield the performance Pw are met. If the area is not the sequential write area, there is no restriction on the performance Pw, and therefore, another busy control is performed. That is, the memory device judges, for a command to access an AU, whether the address indicates access to the sequential write area, and changes memory access control, for example, busy time.
  • the CMD20 "Arrange Area” is solely used, unlike the other CMD20.
  • the CMD20 "Arrange Area” is a command to permit the memory device 11 to prepare an area within a specific time, and indicates completion of preparation by canceling busy of the CMD20.
  • the CMD20 "Arrange Area" is issued at the end of area designation.
  • the overwrite area can be designated any time by issuing the CMD20 "Set Over-Write Area” + CMD25 or CMD18 (step S11). After that, the CMD20 "Arrange Area” is issued to prepare an area (step S12). To arrange data cached by random writes to an overwrite area, the card needs a processing time. The processing time can be ensured by the CMD20 "Arrange Area", and the design becomes easy. In this case, the allowed busy time is suppressed to 250 ms because, for example, data recording may be progressing in a host device.
  • the card can control to make the average busy time of each write shorter than that in writing a plurality of times in an area other than the designated area. That is, the average busy time of write using the CMD20 can be controlled to be shorter than the average busy time of write that uses no CMD20.
  • FIGS. 9A and 9B show an example of a setup sequence using the CMD20.
  • FIG. 10 shows an example in which the setup sequence shown in FIG. 9B is expressed as a command sequence. In this example, one sequential write area and three overwrite areas are designated.
  • the memory device (card) is initialized (step S21).
  • the start address of a data area is designated by the CMD20 "Set Top of Data Area” + CMD18, and the card assigns the DIR area and the bitmap area as the overwrite area (step S22).
  • the sequential write area is designated by the CMD20 "Set Sequential-Write Area” + CMD17 (step S23).
  • the overwrite areas are designated by the CMD20 "Set Over-Write Area” + CMD18, the CMD20 “Set Over-Write Area” + CMD25, and the CMD20 “Set Over-Write Area” + CMD18 (steps S24, S25, and S26).
  • the CMD20 "Arrange Area” is issued, and the area in the memory device 11 is prepared during busy indication of the CMD20 "Arrange Area” (step S27).
  • the combinations of the CMD20 and the write command or read command are not limited to those shown in FIGS. 9B and 10 .
  • a necessary area can be set from the start or a middle point of an AU, as shown in FIG. 9A .
  • FIG. 11 assumes a state in which the subdirectory DIR1 exists under the root directory, and files X1, X2, and X3 are already created in the subdirectory DIR1.
  • the subdirectory DIR2 is newly created under the root directory, File 1 and File 2 are created in DIR1, and File 3 is created in DIR2.
  • FIG. 12 is a view specifically showing an example of file creation according to this embodiment shown in FIG. 11 .
  • FIG. 13 expresses the file creation shown in FIG. 12 as a command sequence.
  • the same reference numerals denote the same parts throughout FIGS. 12 and 13 .
  • FIGS. 12 and 13 show an example in which two sequential write areas SeqW-AUl and SeqW-AU2 and DIR Entry 1 and DIR Entry 2 serving as two overwrite areas are designated, and data are written in these areas.
  • the initialization sequence is executed to initialize the memory device 11 (step S41).
  • the host device 20 analyzes the format of the file system, issues the CMD20 "Set Top of Data Area" + CMD18, and designates the start address of the data area designated by the format (step S42).
  • data read out by the CMD18 can include the bitmap area.
  • the host device 20 can cache the readout bitmap in the system memory (RAM 24).
  • the host device 20 issues the CMD20 "Set Sequential-Write AU" + CMD18.
  • the memory device 11 assigns the sequential write area SeqW-AUl in the NAND flash memory 18 based on the command (step S43). Data can sequentially be written from the address position designated by the CMD18 to the end of the AU.
  • the host device 20 analyzes the format of the file system and issues the CMD20 "Set Over-Write Area" + CMD25 (step S44).
  • the already created DIR Entry 1 is thus assigned as an overwrite area by the CMD18.
  • the host device 20 then issues the CMD20 "Arrange Area" to instruct the memory device 11 to prepare an area (step S45).
  • the memory device 11 is permitted to use, for example, 1 sec as the time for area preparation.
  • file entry FE1 of File 1 is created in the DIR Entry 1, and partial data File 1a of File 1 is written in the sequential write area SeqW-AUl (steps S46 and S47).
  • all file data are written on the RU basis while being made to match the RU boundary.
  • file entry FE2 of File 2 is created in the DIR Entry 1, and partial data File 2a of File 2 is written in the sequential write area SeqW-AUl (steps S48 and S49).
  • the host device 20 analyzes the format of the file system, and sequentially issues the CMD20 "Set Over-Write Area” + CMD25 and the CMD20 "Arrange Area” (steps S50 and S51).
  • the DIR Entry 2 is thus newly assigned as an overwrite area by the CMD25.
  • step S52 the file entry FE3 of File 3 is created in the DIR Entry 2 (step S52), and partial data File 3a of File 3 is written in the sequential write area SeqW-AUl (step S53).
  • Subsequent data File 3b of File 3 is written in the sequential write area SeqW-AU1 (step S55).
  • Subsequent data File 1c of File 1 is written in the sequential write area SeqW-AU1 (step S56).
  • Subsequent data File 2b of File 2 is written in the sequential write area SeqW-AUl (step S57).
  • the host device 20 issues the CMD20 "Set Sequential-Write AU".
  • the memory device 11 newly assigns the sequential write area SeqW-AU2 in the NAND flash memory 18 based on the command (step S58).
  • step S59 subsequent data File 1d of File 1 is written in the sequential write area SeqW-AU2 (step S59).
  • the first CMD25 of step S59 represents the start address of the area SeqW-AU2, and the data File Id is written from there. This logical address (address accessed from outside) is assigned to the sequential write area SeqW-AU2.
  • the sequential write area and the overwrite areas can be designated using the arguments "Set Sequential-Write AU”, “Set Over-Write Area”, “Set Top of Data Area”, and “Arrange Area” of the CMD20, and data can be written in these areas.
  • the AU written partway can be assigned as a sequential write area at the time of initialization. For this reason, the free area in the AU can be used, and the AU utilization efficiency can be improved.
  • FIG. 14 expresses an example of file creation shown in FIG. 3 as a command sequence.
  • steps S61, S62, and S63 are the same as steps S41, S42, and S43 in FIG. 13 .
  • the memory device 11 is initialized, the start address of a data area designated by the format is designated, and the sequential write area SeqW-AU is designated.
  • the host device 20 issues the CMD20 "Set Over-Write Area” + CMD18, the CMD20 “Set Over-Write Area” + CMD18, and the CMD20 "Arrange Area” and designates the already created DIR Entry 1 and DIR Entry 2 as overwrite areas (steps S64, S65, and S66).
  • step S67 the file entry FE1 of File 1 is written in the DIR Entry 1 (step S67), and the partial data File 1a of File 1 is written in the sequential write area SeqW-AU (step S68).
  • the file entries FE2 and FE3 are then written in the DIR Entry 1 (steps S69 and S70), and File 2 and File 3 are written in the sequential write area SeqW-AU (step S70). Since the performance Pw is unnecessary upon writing File 2 and File 3, the data are written in a size smaller than the RU.
  • the memory device 11 may be configured to automatically perform Padding by analyzing the addresses and data lengths of the two memory write commands. The memory device 11 may automatically start sequential write processing from the write address of File 4.
  • the file entry FE4 is then written in the DIR Entry 2 (step S74), and File 4 is written in the sequential write area SeqW-AU (step S75).
  • step S76 the subsequent data File 1b of File 1 is written in the sequential write area SeqW-AU (step S76).
  • FAT update is executed (step S77).
  • the first write indicates updating the FAT
  • the second write indicates updating the bitmap
  • the third write indicates updating the file entry FE1.
  • the file entry FE1 is updated.
  • FIG. 15 shows the newly defined performance information (VG4, VG6, VG10, VG30) of video grades and AU size information of the video grades.
  • 4 MB is used as the basic unit, and the AU size is designated by a multiple thereof.
  • the NAND flash memory 18 stores 2-bit data in one memory cell or 3-bit data in one memory cell. Not only a memory cell having a two-dimensional structure but also a memory cell having a three-dimensional structure exists (exponentiation n, m). For this reason, necessary AU sizes can be covered by the above-described expression.
  • information of a set sequential write area or overwrite area is held in the power down mode or hibernate mode.
  • the CMD20 is extended, thereby defining new functions of "Set Sequential-Write AU", “Set Over-Write Area”, “Set Top of Data Area”, and "Arrange Area". Since the new functions include the conventional functions, the memory device that has received an existing speed class command can convert its function into the new function.
  • the memory device 11 that implements the new functions of the CMD20 implements conversion programs for the existing commands "Start Recording", “Update DIR”, and “Update CI”, and can perform processing while maintaining the compatibility upon receiving the existing speed class commands.
  • the memory device 11 when the memory device 11 receives the control command "Start Recording", it is managed as the same as "Set Sequential-Write AU". And then another sequential write area is assigned by the following sequence.
  • the memory device 11 confirms that data is written up to the end of a sequential write area for which the write of the write command is data write to be performed on the RU basis while being made to match the write boundary. If the next write command indicates write to be performed from the start of another AU on the RU basis while being made to match the write boundary, the newly written user area is assigned as the sequential write area.
  • the memory device 11 Upon receiving the control command "Update DIR" indicating the position of the file system, the memory device 11 assigns an overwrite area by the address of the subsequent write command, assigns an area in a size including the area to be written by the write command as the size of the overwrite area, and if the area has already been assigned as an overwrite area, maintains the assignment.
  • the memory device 11 Upon receiving the control command "Update CI" indicating the position to write a part of CI data during recording of the stream data, the memory device 11 assigns, as an overwrite area, an area in a certain size predicted to write CI data and including the size (512 bytes) of an area to be written by the write command, and if the area has already been assigned as an overwrite area, maintains the assignment.
  • the above-described conversion programs are implemented so that upon receiving an existing speed class command, the memory device can convert its function into the new function.
  • the embodiment of the present invention is used for, for example, a memory card.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Memory System (AREA)
EP19160700.1A 2012-10-30 2013-09-10 Speichervorrichtung und host-vorrichtung Active EP3518112B1 (de)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
JP2012238849 2012-10-30
JP2013166804A JP5976608B2 (ja) 2012-10-30 2013-08-09 メモリデバイス
PCT/JP2013/074959 WO2014069115A1 (en) 2012-10-30 2013-09-10 Memory device and host device
EP13780222.9A EP2915051B1 (de) 2012-10-30 2013-09-10 Speichervorrichtung und host-vorrichtung

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
EP13780222.9A Division EP2915051B1 (de) 2012-10-30 2013-09-10 Speichervorrichtung und host-vorrichtung
EP13780222.9A Division-Into EP2915051B1 (de) 2012-10-30 2013-09-10 Speichervorrichtung und host-vorrichtung

Publications (2)

Publication Number Publication Date
EP3518112A1 true EP3518112A1 (de) 2019-07-31
EP3518112B1 EP3518112B1 (de) 2021-11-17

Family

ID=49474661

Family Applications (2)

Application Number Title Priority Date Filing Date
EP19160700.1A Active EP3518112B1 (de) 2012-10-30 2013-09-10 Speichervorrichtung und host-vorrichtung
EP13780222.9A Active EP2915051B1 (de) 2012-10-30 2013-09-10 Speichervorrichtung und host-vorrichtung

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP13780222.9A Active EP2915051B1 (de) 2012-10-30 2013-09-10 Speichervorrichtung und host-vorrichtung

Country Status (7)

Country Link
US (5) US9983794B2 (de)
EP (2) EP3518112B1 (de)
JP (1) JP5976608B2 (de)
KR (1) KR101674335B1 (de)
CN (1) CN104798063B (de)
TW (1) TWI512463B (de)
WO (1) WO2014069115A1 (de)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3021208B1 (de) * 2014-11-14 2019-01-09 Dot Hill Systems Corporation Verfahren und vorrichtung zur verarbeitung asynchroner ströme
CN105306282B (zh) * 2015-12-07 2019-09-24 联想(北京)有限公司 设备配置方法和设备配置装置
US10140055B2 (en) * 2015-12-21 2018-11-27 Memory Technologies Llc Ensuring that memory device actions are valid using reference values
JP2018022275A (ja) 2016-08-02 2018-02-08 東芝メモリ株式会社 半導体記憶装置
KR20180032391A (ko) * 2016-09-22 2018-03-30 에스케이하이닉스 주식회사 반도체 메모리 장치
CN108008908B (zh) * 2016-10-31 2020-08-07 比亚迪股份有限公司 一种管控sd卡上数据的方法和装置
JP6889566B2 (ja) * 2017-02-13 2021-06-18 キヤノン株式会社 記録装置およびその制御方法
KR102446733B1 (ko) * 2017-11-30 2022-09-23 삼성전자주식회사 스토리지 장치 및 스토리지 장치를 포함하는 전자 장치
TWI792073B (zh) * 2017-12-28 2023-02-11 慧榮科技股份有限公司 快閃記憶體控制器、安全數位卡、使用於快閃記憶體控制器的方法以及存取安全數位卡的主機
US10866746B2 (en) * 2017-12-28 2020-12-15 Silicon Motion Inc. Memory addressing methods and associated controller, memory device and host
JP2019191909A (ja) * 2018-04-25 2019-10-31 東芝メモリ株式会社 メモリシステムおよび制御方法
JP7252821B2 (ja) * 2019-04-17 2023-04-05 キヤノン株式会社 記録装置、記録方法、プログラム、及びメモリカード
US20230409470A1 (en) * 2022-06-15 2023-12-21 Western Digital Technologies, Inc. Scratchpad cache for gaming and iot hosts

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070043924A1 (en) * 2004-06-21 2007-02-22 Takafumi Ito Method for controlling memory card and method for controlling nonvolatile semiconductor memory
US20110238933A1 (en) * 2008-12-11 2011-09-29 Akihisa Fujimoto Memory device and controlling method of the same
US20120254524A1 (en) * 2010-01-27 2012-10-04 Akihisa Fujimoto Memory device and host device

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006040264A (ja) * 2004-06-21 2006-02-09 Toshiba Corp メモリカードの制御方法および不揮発性半導体メモリの制御方法
JP4874588B2 (ja) 2004-07-12 2012-02-15 株式会社東芝 記憶デバイスおよびホスト機器
JP2006085380A (ja) * 2004-09-15 2006-03-30 Toshiba Corp ファイルストレージデバイス、プログラム、及び不揮発性半導体メモリの書込方法
US7613874B2 (en) * 2004-10-14 2009-11-03 Lg Electronics, Inc. Recording medium, and a method and apparatus for overwriting data in the same
JP4817836B2 (ja) 2004-12-27 2011-11-16 株式会社東芝 カードおよびホスト機器
US7685389B2 (en) * 2005-10-21 2010-03-23 International Business Machines Corporation Apparatus, system, and method for setting protection states of protected partitions in storage media
KR100866625B1 (ko) * 2007-02-26 2008-11-03 삼성전자주식회사 Ｍｍｃ 또는 ｓｄ 프로토콜을 사용하는 다수의 메모리장치들을 인터페이스하는 방법 및 시스템
JP5404483B2 (ja) * 2010-03-17 2014-01-29 株式会社東芝 メモリシステム
JP5066209B2 (ja) 2010-03-18 2012-11-07 株式会社東芝 コントローラ、データ記憶装置、及びプログラム
JP5728292B2 (ja) 2011-02-04 2015-06-03 株式会社東芝 メモリデバイス及びホストシステム
KR101856506B1 (ko) * 2011-09-22 2018-05-11 삼성전자주식회사 데이터 저장 장치 및 그것의 데이터 쓰기 방법
JP5832963B2 (ja) 2012-06-29 2015-12-16 株式会社東芝 メモリシステム

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070043924A1 (en) * 2004-06-21 2007-02-22 Takafumi Ito Method for controlling memory card and method for controlling nonvolatile semiconductor memory
US20110238933A1 (en) * 2008-12-11 2011-09-29 Akihisa Fujimoto Memory device and controlling method of the same
US20120254524A1 (en) * 2010-01-27 2012-10-04 Akihisa Fujimoto Memory device and host device

Also Published As

Publication number Publication date
TW201416858A (zh) 2014-05-01
US20230161475A1 (en) 2023-05-25
CN104798063B (zh) 2019-01-11
CN104798063A (zh) 2015-07-22
KR101674335B1 (ko) 2016-11-08
JP5976608B2 (ja) 2016-08-23
US20190286334A1 (en) 2019-09-19
US20180232155A1 (en) 2018-08-16
EP2915051A1 (de) 2015-09-09
US10976930B2 (en) 2021-04-13
US10353586B2 (en) 2019-07-16
TWI512463B (zh) 2015-12-11
US9983794B2 (en) 2018-05-29
EP2915051B1 (de) 2019-11-27
JP2014112351A (ja) 2014-06-19
US20210191621A1 (en) 2021-06-24
US20150234598A1 (en) 2015-08-20
EP3518112B1 (de) 2021-11-17
KR20150063125A (ko) 2015-06-08
WO2014069115A1 (en) 2014-05-08
US11573701B2 (en) 2023-02-07

Similar Documents

Publication Publication Date Title
US11573701B2 (en) Memory device and host device
US11704239B2 (en) Garbage collection method for storage medium, storage medium, and program product
US7543103B2 (en) Host apparatus
JP3942807B2 (ja) ブロックアラインメント機能付き半導体記憶装置
RU2642349C1 (ru) Способ для сохранения данных посредством устройства хранения данных и устройство хранения данных
US7822931B2 (en) File storage device, host apparatus, method for formatting nonvolatile semiconductor memory, and method of writing data in nonvolatile semiconductor memory
US20110179219A1 (en) Hybrid storage device
US7350049B1 (en) Method and apparatus for managing access to a file allocation table
JP2008242503A (ja) メモリ管理装置及び方法、並びにプログラム
CN109558456A (zh) 一种文件迁移方法、装置、设备及可读存储介质
CN107025063B (zh) 内存管理方法、内存储存装置及内存控制电路单元
JP2018160189A (ja) メモリシステム
JP6531574B2 (ja) ストレージ装置、ストレージ装置制御プログラム及びストレージ装置制御方法
KR101699779B1 (ko) 플래시 메모리의 색인 방법
CN113467722A (zh) 一种分布式存储系统的数据迁移方法及装置
JP6107341B2 (ja) データ管理プログラム，データ管理装置およびデータ管理方法
JP2020135656A (ja) ファイル管理システム
JP2008134777A (ja) ファイル割当テーブルのキャッシュ方法
CN110908592A (zh) 存储器管理方法以及存储控制器
JP2013250831A (ja) 情報処理装置および情報処理方法、並びにプログラム

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

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20190305

AC Divisional application: reference to earlier application

Ref document number: 2915051

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20200813

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 12/02 20060101AFI20210318BHEP

Ipc: G06F 13/42 20060101ALI20210318BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20210528

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: KIOXIA CORPORATION

AC Divisional application: reference to earlier application

Ref document number: 2915051

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602013080145

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1448647

Country of ref document: AT

Kind code of ref document: T

Effective date: 20211215

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20211117

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1448647

Country of ref document: AT

Kind code of ref document: T

Effective date: 20211117

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220217

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220317

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220317

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220217

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220218

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602013080145

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20220818

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20220930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220910

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220930

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220910

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220930

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230920

Year of fee payment: 11

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230928

Year of fee payment: 11

Ref country code: DE

Payment date: 20230920

Year of fee payment: 11

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20130910

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211117